HP 418800-B21 HP StorageWorks Replication Solutions Manager 4.0.1 user guide ( - Page 143
Mirrorclones - synchronized
UPC - 882780564640
View all HP 418800-B21 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 143 highlights
IMPORTANT: When using jobs you must explicitly ensure that write caches are flushed. Method GUI action Job Flush implementation Write cache setting after replication The replication manager automatically sets the source disk to write-though mode and ensures the flush is completed before starting the fracture. You must include job commands to set the source disk to write-through mode and wait for the flush to complete before starting the fracture. When the fracture is completed, the controller software automatically sets the source disk and mirrorclone to write-back mode. If you want the source disks or mirrorclones to be in write-through mode, you must explicitly set them. Fracture for disk group failure In the unusual event that a source virtual disk with a mirrorclone experiences a disk group failure, the mirrorclone is automatically fractured by the array. After the failure is corrected, the source can be restored from the fractured mirrorclone. The mirrorclone feature is controller software version dependent. See controller software features - local replication. Mirrorclones - synchronized Mirrorclone replication establishes and maintains a copy of an original virtual disk, via a local replication link. See virtual disk types. source ===========> mirrorclone local link (synchronized) When first created (and whenever resynchronized by an action or command), a mirrorclone is said to be synchronized. In a synchronized state, the mirrorclone is automatically updated whenever its source virtual disk is updated. See also mirrorclone states and fractured mirrorclones. Task summary for synchronized mirrorclones Synchronized mirrorclones Deleting No. The disk must first be fractured and detached, then deleted. Detaching No. The disk must first be fractured, then detached. Fracturing Yes. Presenting Yes. The disk can immediately be presented to hosts for I/O. Replicating - snapclones No. The disk must first be fractured, then presented. Replicating - snapshots No. The disk must first be fractured, then replicated. Restoring No. The disk must first be fractured, then used to restore. Resynchronizing Not applicable. See also general mirrorclone guidelines and mirrorclone FAQ. Benefits of separate disk groups Mirrorclones created in a separate disk group than their source provide the following benefits: HP StorageWorks Replication Solutions Manager 4.0.1 143