Migrating ZCM to new ZCM without a ZCC
Viewed 30 times
- Old ZCM – the ZCM you wish to retire
- New ZCM – the ZCM you wish to keep
Follow these steps on the old ZCM:
In the Old ZCM, examine the properties of the Service Profiles in use. Record the SLA metrics needed such as retention, journal thresholds, etc.
In the ZORG in the Old ZCM, tick the box Custom Profile.
In the existing VPGs which reference the ZORG in the Old ZCM, edit the VPG and select No Zorg under the replication settings and then.
Replace the VMs’ Service Profile SLA with equivalent settings under Custom Profile. You may want to confirm using VM Settings tab in Replication, that all VMs in the VPG reflect the change.
Step through the Replication, Storage, Recovery and NICs tabs to ensure that the infrastructure for recovery are still in place.
Save the VPG with the updated settings and ensure the VPG maintains a steady RPO and does not enter any type of Error State. You will see some alarms saying the VPG has configured values that are outside of what is configured in the ZORG.
Repeat for all other VPGs in this ZORG and the second ZORG.
Once all VPGs have been updated, then go to each ZORG tab in the Old ZCM and select vCD Cloud Resources and delete all the configured vCD Resources
Delete the ZORGs in the Old ZCM
Remove the ZVM site from the Old ZCM
At this point you will only perform on the New ZCM:
Create matching Service Profiles that have the same details as the old Service Profiles from Old ZCM
Add in the Site to the New ZCM
Create a new ZORG for each customer
Bind the correct vCD cloud resources
Tick Custom Profiles in ZORG Settings
Refresh the ZVM windows for source and target ZVMs that are part of this VPG
Edit the Settings of the VPG and select the correct ZORG and the newly-created Service Profile, and ensure to update VM Settings such that each VM in the VPG is updated to use the newly-created Service Profile. Also examine each of the Replication, Storage, Recovery and NICs tabs to ensure the VPG’s infrastructure resources are consistent with what values they’ve always had
The VPG should be now update to Protecting status with no alarms
Repeat for the other VPGs