Webex Migration & Upgrade 1.5 to 2.0

Question

Hello,
We have an old UCS for Webex components. It has Esxi 5.1 Webex Meeting server 1.5, &  vCenter Server on it .
We have got new UCS box. We installed Esxi 5.5, Webex Meeting Server 2.0 ( using cisco-webex-meetings-server-2.0.1.107.B-AE.ova file) & vCenter Server on it.
We don't have central storage.
We need to migrate database from Webex 1.5 to Webex 2.0.
I have gone through webex administration guide, it says it has to be under same vCenter to migrate database Attaching an Existing VMDK File to a New Virtual Machine
In my case i have different vCenter Server for both CWMS & i dont have shared/central storage.
How should i proceed to migrate the database from version 1.5 to 2.0 or how can i bring both Webex Servers under same vCentre ?
Second question, Is the CWMS upgrade ova file same as installation file cisco-webex-meetings-server-2.0.1.107.B-AE.ova or its different ?
Regards,

Answer 1

Hi,
Are you planning an upgrade on the same hardware or a different hardware (not sure if your system is related at all to the anis_cisco's system)?
If you are going to use new/different hardware for CWMS 2.0 setup, you will have to use Manual Upgrade process. 
If you are using the same hardware where your CWMS 1.5 resides, then you can do either Automatic or Manual upgrade. If you plan to do Manual Upgrade, then on the Original 1.5 System you should go to Upgrade > Major Upgrade process which will back the system up, put it in Maintenance Mode, and then ask you to gracefully power off all the VMs (Power > Shut Down Guest in vCenter). Once your 1.5 system is down, you deploy all CWMS 2.0 VMs like a brand new system and follow the instructions noted here: http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Administration_Guide/Administration_Guide_chapter_01010.html#reference_33BF1FFC8C334EACA4CBA2D880E3F206   Pay special attention to STEP 7 and instruction on how to configure the VM so they don't start after deployment. You would use all the same network parameters and hostnames as the original system (and since your original 1.5 system is powered off, there is no IP/hostname conflicts). Finally, once all the VMs are deployed before you power them on, you perform copying of VMDK file per instructions included in the link above and then you power ON all the VMs and your 2.0 system will come up and all the data should be there.
If you are going to use the same hardware and opt for the Automatic upgrade, then you need to ensure you follow all the prerequisites listed here (disk space, NTP settings, vCenter being accessible via FQDN and not only IP address, assign dedicated temporary IP address and hostname for 2.0 Admin Upgrade VM, and if you have IRP in DMZ, make sure that this new IP address and hostname is allowed the same access rules as the 1.5 Admin VM IP address and hostname have, finally, make sure that vSwitch configuration on ESXi host is Standard vSwitch and not Distributed vSwitch; please make sure to read all prerequisites before you start):
http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Administration_Guide/Administration_Guide_chapter_01010.html#concept_9552D5BDF2464C0DB4DA8EA250910651
Per instructions, you will see that while your CWMS 1.5 system is up and running, you will deploy 2.0 Admin Upgrade VM on the same ESXi host where primary 1.5 Admin VM is located. During the deployment you will assign the temporary IP and hostname to this new 2.0 Admin Upgrade VM. Your 1.5 system should be up and running through most of the deployment process, as your 2.0 Admin Upgrade VM will have to access this system (the wizard will guide you). Once all the information is pulled from 1.5 system, the upgrade process will notify you at what point you should put 1.5 system in maintenance and power off the VMs. At that time, the system will deploy all the 2.0 VMs automatically and copy the data. At the first full boot process of 2.0 system, all the original IP addresses and hostnames will be pulled to the new system, and temporary IP/hostname will be discarded. At this time, your 1.5 system is down, and your 2.0 system is up and hence there is no IP conflicts. In the end, once you verified your 2.0 system is fine and upgrade is completed successfully, you can delete 1.5 system. If something goes wrong during the upgrade process, all you need to do is power down 2.0 VMs, and power on 1.5 VMs and the system will come back up as it was before the upgrade. There are no alterations being done to the original system, so you mustn't take any snapshots on the original system before the upgrade. Just let it be.
I hope you will find this advice useful, but still make sure to read the official guide for detailed steps.
Kind regards,
-Dejan