...
[Figure] Mirroring Configuration
Mirror Mode
Mirror mode employs both asynchronous and synchronous mirroring schemes. Understanding the advantages and disadvantages between synchronous and asynchronous mirroring is essential to the correct operation of this.
Async mode
With asynchronous mirroring, each write is captured and a copy of this is made. That copy is queued to be transmitted to the target system as soon as the network will allow it. Meanwhile, the original write request is committed to the underlying storage device and control is immediately returned to the application that initiated the write. At any given time, there may be write transactions waiting in the queue to be sent to the target machine. But it is important to understand that these writes reach the target volume in time order, so the integrity of the data on the target volume is always a valid snapshot of the source volume at some point in time. Should the source system fail, it is possible that the target system did not receive all of the writes that were queued up, but the data that has made it to the target volume is valid and usable.
Semi-sync mode
With semi-synchronous mirroring, each write is captured and transmitted to the target system. Local write completes in the source as soon as the replication packet has reached the target. Normally, no writes are lost in case of failover , but this may can be lost when both nodes are failed simultaneously.
Sync mode
With synchronous mirroring, each write is captured and transmitted to the target system to be written on the target volume at the same time that the write is committed to the underlying storage device on the source system. Once both the local and target writes are complete, the write request is acknowledged as complete and control is returned to the application that initiated the write. With synchronous mirroring, each write is intercepted and transmitted to the target system to be written on the target volume at the same time that the write is committed to the underlying storage device on the source system. Once both the local and target writes are complete, the write request is acknowledged as complete and control is returned to the application that initiated the write.
Adding
Add the shared disk DR resource to a group.
- When add a resource from a group name, select a group → right click → "Add Resource". Or select "Edit(E)" from the main menu bar → select "Add Resource". Or select "Add Resource" icon from the tool bar.
- Select "SharedDisk DR" from Resource Type lists and click the "Next" button.
Enter the resource name and select mirror volume of shared disk in the cluster.
[Figure] Shared Disk DR Resource AddedTo check configuration information on a remote host which has not been clustered, Click the "More Information" button.
[Figure] Shared Disk DR Additional Setting- The DR resource of the shared disk is added after clicking the "Finish" button.
Deleting
| Info |
|---|
How to explained in this section indicates deleting the monitoring item on MCCS, it is not available to delete configuration of the SDR(Shared DR) or MDR(Mirrored DR) which is being replicated by DRBD. |
...
- Click the "Delete resource" button and a confirming message about deleting resource will appear.
[Figure] Resource confirm screen - Click the "OK" button and mirror disk is deleted. The deleted resource will immediately disappear from the management web console.
State
The following table explains the state of shared disk DR resource.
| State | Agent command | Description | Note |
|---|---|---|---|
Online Source(Primary) disk is accessible to read/write. | Offline | Changes the current replication state to the Secondary. ※ It indicates that the replication configuration is downed. | |
| Monitoring | <Source Volume> Checks if the replication state is Primary and if the data state is UptoDate. <Target Volume> Checks if the replication state is Secondary. ※ It indicates that the replication configuration is downed. | ||
Offline Almost all of states are shown as offline state except for online or error. | Online | Changes the current replication state to the Primary. ※ It indicates that the replication configuration is upped. | |
| Monitoring | Refer to the description of monitoring as above. | ||
Fault | Online | Refer to the above online command. | |
| Offline | Refer to the Description of the Offline above. |
Attribute
Show the specified attribute of mirror disk resource.
...