The Inside Microsoft Dynamics GP blog
started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here
The seventeenth Feature of the Day covered is Azure Backups.
The SQL backup and restore windows in Dynamics GP 2013 R2 have been enhanced to allow backups to be stored on Azure. I’ve noticed the same problem that MIcrosoft have with backups; namely that people will make a backup of the SQL databases and then leave them on the same server. This is pointless from a disaster recovery point of view as if something happens to the server you have lost both the database and the backups.
But, as of 2013 R2 the backups can be transferred to Azure storage. The Company Backup window (
) has been enhanced to allow Azure to be selected as the backup location and a path specified:
Continue reading “MDGP 2013 R2 Feature of the Day: Azure Backups”
Backing up the a Microsoft Dynamics GP company to test is, unfortunately, not as simple as backing up one database and restoring it to the Test one. There are two scripts which need to be run after doing so; the first changed the INTERID and Company Name and the second changes the database owner to dynsa.
At my last company, we decided to make this process as easy as possible for clients, so we started creating a SQL Agent Job which would do the backup, restore and run the scripts with minimal effort or could even run on a scheduled basis. The basic purpose was to give the client a test or training system which was always, or could very quickly be, up to date. Continue reading “Copy Microsoft Dynamics GP Live Company To Test Automatically”