- This topic has 1 reply, 2 voices, and was last updated June 10, 2020 by Contara T.
Swapan SJune 10, 2020 11:59:10 AM
Hello team,We are going to implement Zerto for a Swedish client and we would be migration around 1200+ VMs, (vSphere 6.7, with ESXi 6.0) to target. Target will be having vSphere 6.7 and ESXi 6.7.We are in Wave Planning state, so before preparing runbook/starting the migration, we have few queries, that we would like to get clarified. Please find the questions below:1. Can we migrate Desktop version like windows 7/8 /10 can using Zerto?2. Can Citrix VDIs be migrated using Zerto?3. Can we do Windows clusted server migration in case of Physical and Virtual RDMs? Requesting you to provide us step by step documentation for different cluster migration approaches.4. Can we do SQL Cluster servers’ migration for both the nodes using Zerto? Requesting you to provide step by step documentation.Thanks in advance for your help.Regards,Swapan SettContara TJune 10, 2020 09:48:04 PM
Contara from Zerto Support.
1. Can we migrate Desktop versions like windows 7/8 /10 can using Zerto?
The Zerto Interoperability Matrix doesn’t mention about OS 7/8 or /10.
2. Can Citrix VDIs be migrated using Zerto?
We do support Citrix. However, we don’t have the best practices documentation specified for Citrix. If you attempting to protect Citrix VDA/VDI environment, the VMs are replicated in their entirety. Zerto doesn’t have any direct integration into any VDI platforms, so the VMs would be recovered as like any other VM in the hypervisor or cloud management inventory
3. Can we do Windows cluster server migration in the case of Physical and Virtual RDMs? Requesting you to provide us step by step documentation for different cluster migration approaches.
This information is derived from SQLBestPractices:
Zerto is often used for two purposes, protect the server from disaster or migrate between sites.
To protect the MSCS server from disaster(only 1 server will be recovered):
1, We only support to protect the active node of an active-passive cluster
2, Create a VPG to protect the active node, all shared RDMs must be protected to RDMs at the recovery site
3, Whenever the node’s rule changes, you should make the protected VM active node again and run Force sync against the VPG
4, When a disaster happens(consider you lost the source site), failover the VPG, then you have one node at the recovery site
5, Install a new windows server and assemble it with the recovered node to be cluster again
To migrate MSCS servers(both servers will be migrated):
1, Create a VPG to protect the active node, all shared RDMs must be protected to RDMs at the recovery site
2, Break the cluster (stop relevant services and detach all shared RDMs from the passive node)
3, Create a second VPG to protect the passive node
4, Failover the two VPGs then you have two servers at the recovery site
5, Attach shared RDMs to recovered passive node
6, Login to the guest OS to reassemble the cluster
4. Can we do SQL Cluster servers’ migration for both the nodes using Zerto? Requesting you to provide step by step documentation.
You can check the third party link: