Problem: I need to migrate our VCenter that hosts VMWare View Linked Clone Desktops to new hardware. I am not really finding a procedure for this. I can only find a procedure for migrating Composer (including RSA Keys) to new hardware. Is it possible to migrated a VCenter to different hardware when View Linked Clones are involved?
Environment:
VMware View Connection Servers 5.1.1
View Agents 5.1.1
VCenter Server 5.0.0 and Composer 3.0 (installed on same server) - Database for both is on a separate SQL 2008 Server
All Servers both old and new are Windows 2008 R2 (x64)
Possible Solution:
Is the below possible?
1. Disable Provisioning and Migrate Composer to new hardware per the instructions in the Upgrade Guide (migrating the RSA keys with it),
2. Ensure that View Composer is still able to provision new desktops, etc after Composer has been migrated.
3. Shutdown the old VCenter Server.
3a. Backup SQL Databases
4. Name the new VCenter Server with the same name (and same IP) as the old VCenter server.
5. Install VCenter 5.0 on the new server and point to the old VCenter Server's SQL database.
6. After all the above is complete and verified as working...upgrade new VCenter Server to 5.1.0a (at a later date)
My first train of thought is that you are very much correct in your processes. I would also say for you to look at the View 5.1 upgrade guide. This includes some steps and warnings about how to upgrade the composer. These same "pre" steps would need to be applied before you disconnect\stop the composer. The largest aspect being disabling refreshes, recomposes, and previsioning. During my test upgrade I missed changing the pool setting that made the machines refresh on disconnect..lol . Once the composer is no longer going to be utilized you should be in the clear as far as live environment interruptions.
I would then detach the databases from the SQL server and make a copy of the files for the VCDB and ViewCompDB (depending on how they were named). Then just move those files to the new server and attach them to the new SQL install. After that in theory it should just be a few software install steps and ODBC setups away from having it moved. I would also be sure to reattach the original databases so that you can return to that setup if anything goes wrong.
Once that is done I would just name the new server with the same name and IP of your old one as you said. I have not done this type of "upgrade" but based on what experience I have had with cleaning up our SQL install\file placement and upgrading to View 5.1 I would expect that this process would work out. The biggest thing I would stress is to be sure you can fall back to your old setup if anything goes a stray. I would also possible watchout for needing to re-add the Composer or vCenter to View Manager when done.
Anyway just my rambling thoughts on this topic. Please let me know if you find any of it useful or just way off, and good luck with your upgrade.
The below is what I ended up doing (in a test environment) to migrate the VCenter 5.0 Server to new hardware. Ran through the procedure twice and it worked just fine. I could still recompose/refresh Virtual Desktops. I also had no problem accessing my Virtual Desktops. Hope this procedure helps someone else.
Migrate View VCenter 5.0 to new hardware
Rename and Re-IP new VCenter Server with same name and IP as the old VCenter Server
Migrate RSA Keys to New VCenter Server
Install VCenter Server 5.0 (same version as old VCenter Server)
Restore ADAM Database per: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&e...
Enable Provisioning in View Administrator (shouldn’t have to change anything here)
In the new VCenter Server, In Customization Specification Manager, Edit the one you use for View Composer. You will get an error indicating “The public key in the specification does not match the VCenter public key. Click OK to open the Customization Specification Wizard, reenter the password and continue the import”.
Thank you for the write up. I am glad to hear you had success with the move.