7-6 Mirror Disk
[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.
Asynchronization 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 Synchronization 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.
Synchronization 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 mirror disk resource to a group.
MCCS for linux support DRBD which is open source for Mirror disk. Therefore, DRBD 8.3.13 must be installed beforehand.
The size of disk file system that is created by mirror disk should be created with 128MB
128M space is required to store meta data that manages replication volume service. Size of meta data can be changed according to the size of the meta data.
Please refer to DRBD meta data size. (Calculation for more details.)
When use both DBRB and LVM, only DRBD ON LVM is supported and LVM In DRBD is not supported.
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 "MirrorDisk" from Resource Type lists and click the "Next" button. When add a resource from the MirrorDisk resource type name, this step will be skipped.
Enter the resource name.
Select the source server and mirror volume, and enter the mount point.
The virtual device, mirror ip and mirror port will be set automatically.
[Figure] Mirror Disk AddedAs the "Additional Settings", Mirror Type option is available and click the "OK" button. Default is "Semi-Synchronization" Mode.
[Figure] Mirror Disk Additional SettingWhen click the "OK" button, following warning message will be displayed and click the "OK" button if the informations are correct.
[Figure] Alert popup message after click OK buttonClick the "Finish" button to add the mirror disk resource
Deleting
Select resource type → right click → delete resource.
(Current online mirror disk resource cannot be deleted. So it should be taken offline before delete it.)
Click the "Delete resource" button and a confirming message about deleting resource will appear.
[Figure] Check resource viewClick the "OK" button and a confirming message about deleting the mirror configuration will appear.
[Figure] Deleting mirror disk viewClick the "OK" button and mirror disk is deleted.
State
The following table explains the state of mirror disk resource.
Mirror disk agent: Manages a mirror disk, and to use this, it is necessary to install a replication program.
State | Agent command | Description | Note |
|---|---|---|---|
Online Source disk is accessible to read/write. | Offline | It unmounts (umount) the mirror disk from the mount point and the role of mirror disk is demoted to Secondary. |
|
Monitoring | MCCS consistently handles events of the replication service. |
| |
Offline Source and target disk is not fault state but locked so that cannot access both disk. | Online | Type of operation is determined by the role of the mirror disk at the node. <Target role disk> If the mirror disk is not defined, it is processed as a failure without any operation. |
|
Monitoring | Refer to the description of monitoring as above. |
| |
Fault Fail on writing test in online state or fail on attempts to bring online. *Failover disabled state | Online | Refer to the above online command. |
|
Offline | It unmounts (umount) the mirror disk from the mount point and the role of mirror disk is demoted to Secondary. |
|