I was previously asked by a customer "What is the best way to move a VMM SQL database to another server?". The customer also advised that they had attempted to research the scenario, but were not able to find any documentation/blogs. So without "official" guidance I worked with the customer to create a Migration Task List. Following the items on the list we successfully moved their VMM DB between the SQL servers, "Hooray!!" . Unfortunately I am unable to personally assist everyone that has to do this, which is why I have put this article together, to highlight the steps we performed and hopefully help anyone else faced with a similar task:
The final task list included 22 steps, split into 3 sections (Prerequisites, Implementation and Testing). The majority of the steps involved were environmentally specific and will not apply to all setups. So here are the generic tasks that we had to complete in order to achieve a successful DB move:
- Ensure you have a recent backup of the VMM Management servers – In our case the customer used LUN Cloning technology to achieve this.
- Backup the VMM DB, using SQL Management Studio
- Ensure the relevant permissions are configured, as per the VMM Installation Prerequisites (http://technet.microsoft.com/en-us/library/gg610592.aspx)
- Restore the backed up DB to the destination SQL Server – if you have HA VMM Management servers, you are required to clear the HAVMMNAME and HAVMMNodes entries in the restored DB (see for details: http://blogs.technet.com/b/virtual-mite/archive/2014/02/13/reinstalling-clustered-scvmm-management-server-using-existing-sql-database.aspx)
(If you have a standalone VMM Management server perform Steps 4 and 6)
- Take the VMM cluster resource offline – In Failover Cluster Manager select the SCVMM highly available role and "Take Offline"
- Stop the System Center Virtual Machine Manager service on the active node – This will stop VMM users logging into the console whilst maintenance is performed
- Uninstall SCVMM from passive node(s) & reboot
- Uninstall SCVMM from active node & reboot – During the uninstallation wizard select "Retain the database", as a precaution
- Delete DNS and WINS entries, for the VMM Cluster Name
- Install VMM on the first node, pointing to the restored DB on the destination SQL Server. After completion, install the latest rollup patches
- Install VMM on the other node(s). After complete install the latest rollup patches
- Login to the VMM Console and confirm all Resources/Infrastructure Servers/VM Templates/Profiles…are available, as they were when using the original source SQL Server
(Each VMM environment/IT Admin may have their own testing plan to confirm functionality)
The above steps will also apply, in most cases, when upgrading your VMM installation. However, you will need to perform additional tasks (example: upgrading the Vmmagent version on the hosts) to complete a successful upgrade.