Have a look at: https://www.youtube.com/watch?v=soCH_rCvLGA

Byron Grossnickle is showing quickly how best to migrate from existing Global Mirror Change Volume [GMCV] Replication, to the new Policy Based Replication - Disaster Recovery [PBR-DR]. 

Thank you for the reply.  I have looked the video.
The video shows how to migrate the existing GMCV to PBR on the same partnership.
Unfortunately, this is not my customer's request.

My customer wants to keep the GMCV between the FS7200A and FS7200B.  
They have no plan to change the GMCV setting during the data migration to FS7600A.
They want to copy the FS7200A GMCV primary volume to the new FS7600A without terminating GMCV.

Question, again:
Can we setup PBR for the migration from FS7200A to FS7600A without stopping the current GMCV?
I mean ... we want to run PBR  and production GMCV simultaneously on the same rc primary vdisk like below:
FS7200A vdiskA  -- GMCV --> FS7200B vdiskA  (for current DR solution. No changes allowed))
FS7200A vdiskA  -- PBR  --> FS7600A vdiskA  (data copy to new FS7600A for migration)

Best regards, Eiichiro

Have a look at: https://www.youtube.com/watch?v=soCH_rCvLGA

Byron Grossnickle is showing quickly how best to migrate from existing Global Mirror Change Volume [GMCV] Replication, to the new Policy Based Replication - Disaster Recovery [PBR-DR]. 

Thank you for the reply.  I have looked the video.
The video shows how to migrate the existing GMCV to PBR on the same partnership.
Unfortunately, this is not my customer's request.

My customer wants to keep the GMCV between the FS7200A and FS7200B.  
They have no plan to change the GMCV setting during the data migration to FS7600A.
They want to copy the FS7200A GMCV primary volume to the new FS7600A without terminating GMCV.

Question, again:
Can we setup PBR for the migration from FS7200A to FS7600A without stopping the current GMCV?
I mean ... we want to run PBR  and production GMCV simultaneously on the same rc primary vdisk like below:
FS7200A vdiskA  -- GMCV --> FS7200B vdiskA  (for current DR solution. No changes allowed))
FS7200A vdiskA  -- PBR  --> FS7600A vdiskA  (data copy to new FS7600A for migration)

Best regards, Eiichiro

Have a look at: https://www.youtube.com/watch?v=soCH_rCvLGA

Byron Grossnickle is showing quickly how best to migrate from existing Global Mirror Change Volume [GMCV] Replication, to the new Policy Based Replication - Disaster Recovery [PBR-DR]. 

Thanks for your efforts, Guido. I had already shared the same link and provided the information, though. Have you ever used this non-disruptive migration method? 

Thanks for your efforts, Guido. I had already shared the same link and provided the information, though. Have you ever used this non-disruptive migration method? 

I have used it several times on several operating systems, and there is no need to shut down the server. Non-disruptive volume migration synchronizes the UUID to the target volume and uses a multipath algorithm (active path on the source site and ghost path on the target site). When you switch directions, the target site becomes the active path and the old source site becomes the ghost path. You can then remove the mapping from the old source site without affecting the server, and Voila! it works like a charm!

Thanks for your efforts, Guido. I had already shared the same link and provided the information, though. Have you ever used this non-disruptive migration method? 

I have used it several times on several operating systems, and there is no need to shut down the server. Non-disruptive volume migration synchronizes the UUID to the target volume and uses a multipath algorithm (active path on the source site and ghost path on the target site). When you switch directions, the target site becomes the active path and the old source site becomes the ghost path. You can then remove the mapping from the old source site without affecting the server, and Voila! it works like a charm!

Thanks for your efforts, Guido. I had already shared the same link and provided the information, though. Have you ever used this non-disruptive migration method?