This post is more than 5 years old
16 Posts
0
1024
November 10th, 2015 06:00
MirrorView Fracture
Hello all
I'm not sure of the difference between the following 2 statements. It seems to me that the result is the same, can anyone clarify please
With MirrorView/S, writes continue to the primary image but are not replicated to the secondary
during a fracture. Replication can resume when the user issues a synchronize command.
With MirrorView/A, the current updates stop during a fracture, and no further updates start until a
synchronize request is issued. The last consistent copy remains in place on the secondary image if
the mirror is to be updated.
No Events found!
Rainer_EMC
4 Operator
•
8.6K Posts
0
November 10th, 2015 13:00
One is for MirrorView sync and one for MirrorView async – which work differently.
See the MirrorView knowledgebook for more details
dynamox
9 Legend
•
20.4K Posts
1
November 10th, 2015 11:00
they are indeed strangely worded sentences. When you fracture MirrorView pairs (/S or /A), updates to secondary image stop. When you are ready to resume you simply synchronize them again (incremental sync).
FX2newuser123
16 Posts
0
November 10th, 2015 12:00
I believe I understand now.
https://www.emc.com/collateral/hardware/white-papers/h2417-mirrorview-know-cx-series-flare-wp-ldv.pdf
Its the difference between MV/S fracture log use and MV/A transfer bitmap & Gold copy