Hello,   Yes that plan will work just fine.   You'll add the new PS4000 to the same group, put it in a new pool.   Depending on the FW revision of the existing array, it's a great time to upgrade the new member to the latest firmware.  Once the raidset is built move it into the same pool as the existing member.  Let the migration of data start and monitor it to make sure it's moving well.   Adding a new member and migrating data can stress switches that are not well suited for iSCSI.  If all is going well, move the original array to the pool you created for the new member.   Once all the data is off, upgrade that array firmware, if needed, then remove it from the group.  (Right mouse over member and "Delete Member")    Now you can re-run setup on that original member.   Configure it with a new Group and Member name in the same subnet as the original group.    Configure replication between them, and run your initial replication locally.   Once you're ready to move it, pause replication.  Shutdown the replication unit.  Reinstall it and re-ip it for the new subnet.  Change the IP in the replication partner on the source side to match.   Resume replication.   Regards,  -don 
hi there, My company has recently bought a 2nd equallogic PS4000 (with faster drives). The idea is that this replaces our current PS4000. The plan was:- 1. to install the new PS4000 in head office and migrate all data from the "old" PS4000 onto the new PS4000. 2. Remove the old PS4000 and take it to a branch office and setup replication between the 2 SANs for backup\DR purposes. I was wondering if this sounds like a good plan? With regards to step 2 are you able to take an initial "seed" replica before I take the server off to the new site. Cheers, Al
migrating to a new equallogic and then replicating across