HP Storage Mirroring V5.1 Software - Manual (Page 76)

10 - 14
Blocking target paths
You can block writing to the paths on the target that contain the copy of the replication set data. This
keeps the data from being changed outside of Storage Mirroring processing. To block the replication
set data paths on the target, right-click the connection on the right pane of the Management Console
and select Block Target Path(s). To unblock the paths, right-click the connection and deselect
Block Target Path(s).
Disconnecting a connection
To disconnect a Storage Mirroring connection, right-click the connection on the right pane of the
Management Console and select Disconnect. The source and target will be disconnected.
NOTE: If you are going to use failover, any target paths that are blocked will automatically be
unblocked during the failover process so that users can modify data on the target after
failover. During a restoration, the paths are automatically blocked again. If you failover
and failback without performing a restoration, the target paths will remain unblocked.
You can manually block or unblock the target paths by right-clicking on a connection.
Do not block your target paths if you are using Full-Server Failover because system state
data will not be able to be written to the target.
If you are archiving files, the target paths will automatically be blocked. Do not disable
the blocked target paths to ensure proper archiving functionality.
NOTE: If a connection is disconnected and the target is monitoring the source for failover, you
will be prompted if you would like to continue monitoring for a failure. If you select Yes,
the Storage Mirroring connection will be disconnected, but the target will continue
monitoring the source. To make modifications to the failure monitoring, you will need to
use the Failover Control Center. If you select No, the Storage Mirroring connection will
be disconnected, and the source will no longer be monitored for failure by the target.
If a connection is disconnected while large amounts of data still remain in queue, the
Management Console may become unresponsive while the data is being flushed. The
Management Console will respond when all of the data has been flushed from the queue.