Migrate CMS Nodes to new ESXI Server.

[Meddane]

Scenario:

 I elaborate the following procedure:

1. Check the database status on all servers using the database cluster status command.
2. Take a backup on all servers using the backup snapshot <backup_filename> command.
3. Disconnect the slaves CMS2 and CMS3 and the callbridge node CMS4 from the old primary using the database cluster remove command.
4. Check again the database status to confirm (On the old primary).
5. Shutdown CMS1 and CMS2.
6. Remove CMS1 and CMS2 on Cisco Meeting Management.
7. Deploy a new VM with the same network settings as the primary CMS1. Copy the backup file using SFTP.  Restore the backup using the backup rollback <backup_filename> command. Reboot
8. Deploy a new VM with the same network settings as the slave CMS2. Copy the backup file using SFTP.  Restore the backup using the backup rollback <backup_filename>. Reboot CMS1 and CMS2. After reboot.
9. Add new CMS1 and CMS2 to Cisco Meeting Management.
10. Join all slaves CMS2 and CMS3 to the new primary CMS1 using the database cluster join <Database_primary_IPaddress> command.
11. Connect CallBridge node CMS4 to the new primary CMS1 using the database cluster connect <Database_primary_IPaddress> command.
12. Verify the database status on all node using the database cluster status command.