Yes 32 synchronous replications is the current maximum allowed. Synchronous Replication writes volume data across two different storage pools in the same group, and yes this is hardware independent.  There is a small performance hit with SyncRep (becase each write has to be sent to both pools/volumes) but typically spindle speed is negligible in this equation (PS6100 SAS is either 7.2, 10 or 15K disks syncing with 7.2K sata disks in the PS6500). You didn’t mention how you wanted to migrate from the old PS group to the new PS group, but this can be done in several ways; backup/restore; create a new datastore in the new PS group, present the datastore(s) to your ESX servers, and then move your VMs to it; or use the standard replication (then promote the replication to a volume).   If you are looking to sync the existing volumes to the new PS group, then the standard replication method might be a workable solution for you (replicate, then promote the replica to a volume when the time comes). Of the three, moving the VM is the least disruptive with minimal downtime (copy VM files to the new datastore created in the new group). -joe
Hi all, I have a question or two around SyncRep, and the potential limitations around it. I understand there is a limitation of 32 volumes that can be "Syncrepped"? Is this correct? Also, can I SyncRep volumes between dissimilar hardware, e.g. a PS6100 and a PS6500? The idea is to eventually move our existing Data Center from one location to another, basically procuring new hardware and building the shell on the new site, Site B (including a vitual and physical environment), then replicating the data from Site A to Site B, and once done, firing up Site B and shutting down Site A. That's the idea, at least :-) Thanks a mill!
SyncRep