Best Practice with replacing a whole Server of a Cluster

[danielweeber]

Just one additional question: After this procedure the tasks are named "incorrectly". Any way to fix this w/o interrupting?
(You have to create the new tasks on one server, because one server is source to both luns.)

Redo everything but leave source on one of each servers? Will the targets recognize the existing data with the metadata on the lun and NOT resync everything?

[To-M]

If you are adding a new server with new Volume Group and Logical Volumes then your will need to delete the tasks and re-create new tasks for the new volumes for that newer server and mark the volumes for Destination mode with the same size. When your start the new tasks then it will need to re-sync the date to the new volumes.

[danielweeber]

Hi Todd,

yeah. I meant after adding the new tasks which you need for sure the tasks are named, esp, "mirror0" and "mirror1" and the server which hasn't been replaced and "mirror0_reverse" and "mirror1_reverse" on the new one which has been replaced.

Typically, in a active/active scenario, you create one task with one volume as source on one server, and one task on the other server with the other volume as source.
So on one server its tasks mirror0 and mirror1_reverse and on the other server its mirror0_reverse and mirror1