Happy Friday! In the scenario you have described, I would strongly suggest you go with Case 1 according to EMC Best Practices. Each source SP should have access to each SP on the target system.
In the event of a path failure, you should be able to resume the SANcopy session if there are other paths available. If not, repair the failed path and resume the session.
I found this San Copy Zoning guide - this should help - this was from an example using three array - I've attached the document - it's old, but still valid - see pages 8 and 9 .
Please verify the initiators again, If you are using mirror view initiators for SAN copy, it will get failed.. check in source array - san copy connection and make sure all are registered and logged in
As I have told that there is no port issue( neither log in issue ) on the array side ,, I would say this is the design for SAN copy .
One Path would be chosen per session , but if that path fails during session , session would be resumed and starts when failed path is fixed. ( There is no trespass or some kind act to keep session going from Array side upon path failure ,,, )
This is SAN copy , if this is MV, MV try to keep session going ( trespass occurs) ,,, this is the difference between Data Migration and Data Backup ( protection ... ) would`t it? ... ( San copy is migration solution and work with other Array as well that is the reason for this as well )
chrismahon
1 Rookie
•
18 Posts
916
0
Posted February 12th, 2016 07:00
Hi Ayas,
Happy Friday! In the scenario you have described, I would strongly suggest you go with Case 1 according to EMC Best Practices. Each source SP should have access to each SP on the target system.
In the event of a path failure, you should be able to resume the SANcopy session if there are other paths available. If not, repair the failed path and resume the session.
Thanks,
Chris