Chapter 8: Using the Synchronous Mirroring Premium Feature
145
primary volume during the link interruption are copied to the secondary volume.
After the resynchronization starts, the mirrored pair transitions from an
Unsynchronized status to a Synchronization in Progress status.
The primary controller also marks the mirrored pair as unsynchronized when a
volume error on the secondary side prevents the remote write from completing. For
example, an offline secondary volume or a failed secondary volume can cause the
remote mirror to become unsynchronized. When the volume error is corrected (the
secondary volume is placed online or recovered to an Optimal status), then
synchronization is required. The mirrored pair then transitions to a Synchronization in
Progress status.
Resynchronization
Data replication between the primary volume and the secondary volume in a mirror
relationship is managed by the controllers and is transparent to host machines and
applications. When the controller owner of the primary volume receives a write
request from a host, the controller first logs information about the write to a mirror
repository volume. The controller then writes the data to the primary volume. The
controller then initiates a write operation to copy the affected data to the secondary
volume on the remote storage array.
If a link interruption or a volume error prevents communication with the secondary
storage array, the controller owner of the primary volume transitions the mirrored pair
into an Unsynchronized status. The controller owner then sends an I/O completion to
the host sending the write request. The host can continue to issue write requests to the
primary volume, but remote writes to the secondary volume do not take place.
When connectivity is restored between the controller owner of the primary volume
and the controller owner of the secondary volume, the volumes must be
resynchronized by copying the blocks of data that changed during the interruption to
the secondary volume. Only the blocks of data that have changed on the primary
volume during the link interruption are copied to the secondary volume.
ATTENTION Possible loss of data access
– Any communication disruptions
between the primary storage array and the secondary storage array while
resynchronization is underway could result in a mix of new data and old data on the
secondary volume. This condition would render the data unusable in a disaster
recovery situation.
Creating a
Synchronous
Mirroring Pair
Before you create any mirror relationships, volumes must exist at both the primary
site and the secondary site. The volume that resides on the local storage array is the
primary volume. Similarly, the volume that resides on the remote storage array is the
secondary volume. If neither the primary volume nor the secondary volume exist, you
must create these volumes. Keep these guidelines in mind when you create the
secondary volume:
Summary of Contents for InfiniteStorage 4000 Series
Page 34: ...22 ExitStatus ...
Page 48: ...36 Adding Comments to a Script File ...
Page 110: ...98 Starting Stopping and Resuming a Snapshot Legacy Rollback ...
Page 168: ...156 Interaction with Other Premium Features ...
Page 182: ...170 Interaction with Other Premium Features ...
Page 192: ...180 SSD Cache Management Tasks ...
Page 216: ...204 RecoveryOperations ...
Page 218: ...206 Show Storage Array ...
Page 219: ...Appendix A Examples of Information Returned by the Show Commands 207 ...
Page 220: ...208 Show Storage Array ...
Page 221: ...Appendix A Examples of Information Returned by the Show Commands 209 ...
Page 222: ...210 Show Storage Array ...
Page 223: ...Appendix A Examples of Information Returned by the Show Commands 211 ...
Page 224: ...212 Show Storage Array ...
Page 225: ...Appendix A Examples of Information Returned by the Show Commands 213 ...
Page 226: ...214 Show Storage Array ...
Page 227: ...Appendix A Examples of Information Returned by the Show Commands 215 ...
Page 228: ...216 Show Storage Array ...
Page 229: ...Appendix A Examples of Information Returned by the Show Commands 217 ...
Page 230: ...218 Show Storage Array ...
Page 231: ...Appendix A Examples of Information Returned by the Show Commands 219 ...
Page 233: ...Appendix A Examples of Information Returned by the Show Commands 221 ...
Page 234: ...222 Show Controller NVSRAM ...
Page 253: ...Appendix A Examples of Information Returned by the Show Commands 241 ...
Page 254: ...242 ShowDrive ...
Page 255: ...Appendix A Examples of Information Returned by the Show Commands 243 ...
Page 256: ...244 ShowDrive ...
Page 257: ...Appendix A Examples of Information Returned by the Show Commands 245 ...
Page 258: ...246 ShowDrive ...
Page 268: ...256 ConfigurationUtility ...
Page 275: ......
Page 276: ...Copyright 2012 NetApp Inc All rights reserved ...