The only was to that lun became read/write is promoting it, so it will become a primary image.
If you do it with the link fractured, you will have a new MV instance with a primary image, even it has the exact same name it is a new instance.
In this situation you have on your source array a instance with a primary image that has a secondary image that does not existe anymore and o the target array you have another instance with a primary image that does not have a secondary image.
In order to start the sync again, you have to clear both MV instance than add the secondary image to the original primary image.
As Tien pointed out, taking a snapshot of the secondary image and presenting that is a very common (and arguably preferable) technique with the use case of the OP. Instead of presenting the secondary image itself, the primary image remains protected and continues to synchronize with the secondary image which is not the case in the scenario described above where the secondary image is promoted (and/or mirror is fractured). Refreshing the data then is simply a matter of taking and mounting a new snapshot.
The only requirement, and an assumption Tien and I are making, is that you have a (full) SnapView license to active the sessions and present the snapshots. For the record, even though MirrorView/A utilizes SnapView technology underneath for the asynchronous copies, this does not expose the snapshot (and clone) features on the secondary array.
pdubey2
1 Rookie
•
49 Posts
0
November 18th, 2010 04:00
Did u find answer to your question ??
pozzebom_ezequi
24 Posts
0
December 2nd, 2010 05:00
The secondary image is never in read/write mode.
The only was to that lun became read/write is promoting it, so it will become a primary image.
If you do it with the link fractured, you will have a new MV instance with a primary image, even it has the exact same name it is a new instance.
In this situation you have on your source array a instance with a primary image that has a secondary image that does not existe anymore and o the target array you have another instance with a primary image that does not have a secondary image.
In order to start the sync again, you have to clear both MV instance than add the secondary image to the original primary image.
Tien Bui
13 Posts
0
January 7th, 2011 02:00
Work Around: In the MV/A mode you can actulaly snap the Secondary LUNs and then mount the snapshots to the Secondary hosts for Backup/Testing/Dev...
You can find the detail document in Powerlink: "EMC Bussiness Continuity for Microsoft SQL Server 2008 Enabled by EMC CLariion and MirrorView/A"
Hope this help...
chrisimes
24 Posts
0
January 13th, 2011 21:00
As Tien pointed out, taking a snapshot of the secondary image and presenting that is a very common (and arguably preferable) technique with the use case of the OP. Instead of presenting the secondary image itself, the primary image remains protected and continues to synchronize with the secondary image which is not the case in the scenario described above where the secondary image is promoted (and/or mirror is fractured). Refreshing the data then is simply a matter of taking and mounting a new snapshot.
The only requirement, and an assumption Tien and I are making, is that you have a (full) SnapView license to active the sessions and present the snapshots. For the record, even though MirrorView/A utilizes SnapView technology underneath for the asynchronous copies, this does not expose the snapshot (and clone) features on the secondary array.