Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

[Figure] Mirroring Configuration



Replication Mode

Replication option 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.

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 mirror disk DR resource to a group.

...

  1. 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.
     
  2. Select 'MirrorDisk DR' from Resource Type lists and click 'Next' button. When add a resource from the mirror disk DR resource type name, this step will be skipped.

  3. Select the mirror volume and MCCS will renew the information.

    If you skip enter resource name, this will given 'Mirror_value' which value is selected driver letter.(Ex: Mirror_G)

    Warning

    미러 디스크 DR로 사용될 드라이브 문자 는 양쪽 서버와 DR서버는 같은 드라이브 문자로 되어있어야 합니다.
    [Drive characters in the SAN environment (shared disk) are also displayed in the list. So, make sure you select the accurate drive characters.]
    Data will be copied to the target node and DR node from the source node.
    Be careful when you select the drive character where data exists.
    If you try to add the existing mirror volume, <mirrored> will be added to the volume letter.

        


    [Figure] Mirror Disk DR Resource Added

       

  4. 미러주소와 DR 미러 주소를 선택합니다. 


  5. <동기화 모드> 선택합니다.

    동기화 모드는 한 번 선택하면 변경할 수 없으므로 주의해서 선택해야 합니다.
    왼쪽 콤보 박스는 Cluster내에 미러 라인에 대한 동기화 모드이고, 오른쪽 콤보 박스는 DR 미러 라인에 대한 동기화 모드 입니다.

    Sync mode : Response is slow but there is no data loss involved.
    Async mode : Relatively faster than the synch mode but it can suffer from data loss.


  6. As 'Additional Settings', Check Disk option is available.

    Info

    <Check Disk Option>

    Set the check disk command option. For more details on the function, refer to MSDN.


    [Figure] check disk option

     

  7. When click OK button, following popup message appear.
    Confirm selected server as source.
    If you select wrong sever, clock cancel button.
     
    [Figure] Alert popup message after click OK button  

  8. Click the 'Finish' button to add the mirror disk DR resource.
    You can immediately check the result in the management web console.

 

Deleting

 

Select resource type → right click → delete resource.

...

  1. Click "Delete resource" and a confirming message about deleting resource will appear.

    [Figure] check resource view    

  2. Click "OK" and a confirming message about deleting redundancy program of mirror configuration will. 

    [Figure] Delete physical mirror disk view   

  3. Click "OK" and redundancy program is deleted. Click "Cancle" and only mirror disk DR is deleted. 
    The deleted resource will immediately disappear from the management web console.

 


 


 

상태

 

다음 테이블은 DR 쪽 상태와는 상관없이 클러스터내의 미러 상태와 사용자 명령에 의해 발생되는 MCCS 리소스의 상태 변화에 대한 설명입니다.
The command assumes that it is generated by a user.

...

StatusAgent commandDescriptionNote

Online

In this status, you can access the source volume and perform a writing test properly.

Offline

Regardless of the mirror role, the LOCKVOLUME command is used to lock the volume.
If the mirror volume is not defined, the LOCKVOLUME command is ignored and regarded as a failure.

 
Monitoring

The monitoring process is also determined by the mirror volume status and roles.
The kernel driver of copying program records an event in the system event log when the mirror volume status is changed.
The MCCS event monitor is registered as an event receiver when starting the MCCS service. When a system event occurs, it will be automatically informed and it will detect the mirror volume status and role changes.
Once the status and the role are determined, a disk writing test is performed to finalize the resource status.

<Source volume>
If the writing test is successful, it is regarded as the online state.

<Target volume>
1. If the writing test failed on the disk, it is regarded as the offline state.
2. If a user unlocks the target volume while the mirror disk is online, an agent will automatically lock it again.
 Thus, the target volume of the node with the online mirror disk cannot be unlocked.
3. If the mirror volume is not defined,  it is regarded as the offline state.

 

Offline

Except for the online and trouble states, it is always offline.

Online

Type of operation is determined by the role of the mirror volume at the start node.

<Source volume>
1. Allow them to unlock and write to the volume.
2. Unlocking is done by 'UNLOCKVOLUME' of the copying program. The write function is executed after changing the MountReadOnly in registry value of the copying program to 0. After writing is available, the value is changed back to 1.

<Target volume>
1. An attempt to go online at the node where the mirror role is the target failed if the mirror status is not "Mirroring".
2. If the mirror volume is fully synchronized, you can change the mirror role. Such a process is determined by the node status (A).
3. If you cannot connect to mirror driver of node A, use the DELETEMIRROR command to delete the existing mirror volume. After that, switch the target and the source, and use the CREATEMIRROR command to create the reverse mirror volume.
When creating the mirror, if you set the option to 0x1, they are not all synchronized.
4. If you cannot connect the mirror driver of node A, use the DELETELOCALMIRRORONLY command to delete the mirror configuration of node B only. After that, use the CREATEMIRROR command to configure the reverse mirror volume.
Now, node A does not respond. The 0x2 option is added so that it does not wait until the target mirror volume is created.
If the final volume is locked, unlock it and change the MountReadOnly option to 0. After writing, change it back to 1.
If the mirror volume is not defined, it is processed as a failure without any operation.

 
Monitoring

Refer to the description of monitoring as above.

 

Trouble

If a writing test failed online, or an attempt to go online is failed, the trouble state is displayed.

*Failover deactivation state
When a mirror network communication failure, target node or target disk failure occurs, the mirror state is changed from 'MIRRORING' to other, such as 'MIRROR_PAUSED'.
If the mirror status is not 'MIRRORING', a failover will take place and it can cause data losses or damages.
To prevent this problem, an agent deactivates the failover mode if the mirror status is not "MIRRORING".
If the failover mode is deactivated, no failover will take place even if manual failover or troubles occur.
If mirror network communication failures are recovered, and communication resumes, it will automatically perform RESYNC. When the mirror status is changed to MIRRORING, the failover mode will be also automatically activated.

Online

Refer to the above online command.

 
Offline

Regardless of the mirror role, the LOCKVOLUME command is used to lock the volume.
If the mirror volume is not defined, the LOCKVOLUME command is ignored and regarded as a failure.

 

 

 

 

 

 

Attribute

 

Show the unique attribute of resource.

...