...
Section | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Info |
---|
DRBD 9 가 사전에 설치 되어 있어야 하며 Internal 메타 데이타 기능을 사용할수 없습니다It is essential for DRBD9 to be installed in advance, the function of the internal meta data is not available. |
[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.
- 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 'Next' button. When add a resource from the MirrorDisk resource type name, this step will be skipped.
- Select the source server and mirror volume
메타디스크 볼륨을 선택합니다.
메타디스크 볼륨은 드라이브 레터를 붙일 수 있는 별도의 볼륨이 필요합니다. 이런 볼륨을 만들기 위해서는 아래의 경우가 준비 되어야 합니다.
드라이브레터
예 : m 디렉토리 마운트Drive letter
For example, M- Directory mount
For example, C:\vdrive - GUID 형태의 볼륨 이름
예 : Volume's name in GUID format
For example, \\?\Volume{ed8a8f02-18b3-11e6-91b4-000c29ac57f8}\ - VHD (Virtual Hard Disk)
예:For example
1. m m c:\r0_meta.vhd ## VHD + 레터 방식format of drive letter
2. C:\vdrive c:\r0_meta.vhd # # VHD + 디렉토리 마운트 방식mounting format of a directory
3. \\?\Volume{ed8a8f02-18b3-11e6-91b4-000c29ac57f8}\ c:\r0_meta.vhd # # VHD + GUID 방식GUID method - When 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 button - Click the '"Finish' " button to add the mirror disk resource
예 :
Chooses a volume of the meta disk.
The volume of the meta disk needs another seperate volume available to attach a drive letter. The followings need to be prepared for making such volume:
Note | ||
---|---|---|
| ||
메타 볼륨은 별도의 볼륨을 생성할 때 반드시 포맷을 하지 않고 RAW 상태로 만들어야 합니다. WDRBD는 기본적으로 섹터 단위로 메타 볼륨에 접근하기 때문에 NTFS와 같은 파일시스템으로 포맷을 하게되면 부트레코드(Boot Record) 영역으로의 접근이 쓰기 권한을 요구하게 되며 해당 영역이 보호를 받게 되어 일부 섹터에 대한 접근이 되지 않습니다. 또한 MFT 같은 파일시스템의 메타 영역이 생성되어 WDRBD에서 메타디스크로 사용할 수 없게 됩니다. 따라서 초기 볼륨 생성시 포맷 하지 않는 옵션을 선택하여 생성해야 합니다. |
A meta volume should be created with RAW status that the volume was not formatted, when creating a separate volume. WDRBD accesses to a meta volume as a sector unit basically, therefore, some part of a sector may not accessible because those are protected because of result from request for an authority to write against a boot record area if the volume has been formatted through the particular file system such as NTFS type. Moreover, it would not be able to use as a meta disk for WDRBD because a meta area of the file system such as MFT is made. So it is recommended choosing the option for what the volume is not formatted when creating the initial volume. |
[Figure] Mirror Disk Added
Deleting
Select resource "Resource type" → right click → delete resource.0
- Click the "Delete resource" and a confirming message about deleting resource will appear.
[Figure] Check resource view - Click the "OK" button and a confirming message about deleting the mirror configuration will appear.
[Figure] Deleting mirror disk view
Click Click the "OK
" and mirror disk is deleted.
확인을 클릭하면 모두 삭제, 취소를 클릭하면 MCCS 에 구성된 미러디스크 리소스만 삭제하게 됩니다" button to delete all, or click the "Cancel" button to delete only a DR resource of a mirrored disk configured on MCCS.
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 | the role of mirror disk is demoted to Secondary. | |
Monitoring | <소스 볼륨> <타깃 볼륨> Checks if replication is in the Primary status and data is UptoDate. <Target Volume> Checks if replication is in the Secondary status. | ||
Offline Source and target disk is not fault state but locked so that cannot access both disk. | Online | After setting the role of mirror disk to Primary. | |
Monitoring | Refer to the description of monitoring as above. | ||
Fault | Online | Refer to the above online command. | |
Offline | the role of mirror disk is demoted to Secondary. |
Attribute
Show the specified attribute of mirror disk resource.
Attribute | Description | Type | Default | Edit | Note | ||||||||||||||
Address | It is an IP address used by mirror disk. | STRING | X | ||||||||||||||||
ChkDsk | If this is set to true, it perform the check disk command when the mirror disk is taken online. Before perform this, the mirroring will be automatically paused and this will be resumed after this is completed. | BOOLEAN | false | O | |||||||||||||||
ChkDskArg | It defines check disk command option when Chkdsk is true. /F: Modifies the error in the disk. /R: Recovers the information of damaged sector. (Including /F) | STRING | /F | O | |||||||||||||||
ChkDskTimeout | It is timeout limit to complete or stop the check disk of mirror disk before attaching the disk . If value is '0', MCCS waits to complete the check disk before attaching the disk. | INTEGER | 120sec | O | |||||||||||||||
Connection | Display the status of connection between the mirror disk's nodes. | STRING | X | ||||||||||||||||
Device | This is a virtual device name used by mirror disk. | STRING | X | ||||||||||||||||
DirtyBit | There are dirty bits in the source disk. When changed block isn't transmitted to the target disk, this is marked on the block. | BOOLEAN | false | X | Connection | Display the status of connection between the mirror disk's nodes. | STRING | X | Replication | Display the status of replication between the mirror disk's nodes. | |||||||||
STRING | X | DiskState | Display the status of disk managed by the mirror disk. | STRING | X | Resource | Displays the name managed by DRBD | STRING | X | ||||||||||
GI | It is an identifier used to determine whether each household's data copied by the mirror disk is of the latest version. | STRING | X | ||||||||||||||||
| Host | MirrorDisk host name of using resource configuration. | STRING | X | |||||||||||||||
MetaDisk | It is the disk where meta data is saved. | STRING | X | Address | It is an IP address used by mirror disk. | STRING | |||||||||||||
OutOfSync | Displays whether there is a value of Out Of Sync which needs synchronization. In case it is, the value is true and it also indicates that there is data that synchronization or replication between nodes has not finished. Therefore, failover will be blocked out in case of the true value. | BOOLEAN | false | X | |||||||||||||||
Port | It is the communication port number used for mirror disk. | INTEGER | 7789 | X | Role | Display the disk role (Primary or Secondary) of the node. | STRING | X | Host | MirrorDisk host name of using resource configuration. | STRING | X | OutOfSync | 동기화가 필요한 Out Of Sync 값의 유무를 나타냅니다. Out Of Sync값이 있는 경우에는 true이며, 노드 간에 아직 복제 혹은 동기화 완료되지 않은 데이터가 존재하고 있음을 의미합니다. | BOOLEAN | false | 7788 | X | |
Protocol | It displays mirror type. A = Async mode B = Semi sync mode C = Sync mode | STRING | B | X | |||||||||||||||
Device | This is a virtual device name used by mirror disk. | Replication | Display the status of replication between the mirror disk's nodes. | STRING | X | ||||||||||||||
Resource | Displays the name managed by DRBD | STRING | X | ||||||||||||||||
각 노드의 SourceRole Level을 나타냅니다. 값이 높은 노드가 최종적으로 Primary Role을 가집니다Role | Display the disk role (Primary or Secondary) of the node. | STRING | X |
※ 속성 값은 해당 리소스를 등록할 때에 입력된 값이며, '리소스 고유 속성'에서 값을 변경하거나 확인할 수 있습니다.
...
Specified attribute values are normally entered when add the resource, This value can be edited or viewed through Specified Attribute table in the Resource Attributes tab on the detailed information panel.
Info |
---|
MCCS has function to limit input values against user's input field, and it provides function detects automatically data which is input wrong by user's mistake |