The mirror management console is provided only for the individual mirror resources managed by MCCS.
The mirror management console operates independently from the engine logic of MCCS, so during operation, it can collide with MCCS.
The mirror management console informs users of the mirror volume status and the capacity of the mirror in use. You can change the bandwidth and the mirror network addresses in it.

Table of Contents

Mirror Disk Console

Mirror disk management console

The following screen is mirror disk management console.

[Figure] Mirror disk management console

Mirror disk Status

Mirror console show mirroring status as follows.

	Figure	Description
Volume		The volume role is Source. Displays the capacity in use on the right side of the volume.
		The volume role is Target.
		The volume status is Diskless.
Status		The status is Mirroring.
		The status is Resyncing. Displays the progress for resyncing.
		The status is Paused.
		Split brain is occurred.

Mirror management command descriptions

Right click with your mouse button on the mirror set volume to see the descriptions of the mirror management commands that can be selected.

Menu	Decription
Connect	Connect communication path between two nodes for mirror disk.
Disconnect	Disconnect communication path between two nodes for mirror disk.
Forceful sync	The mirror status is changed to RESYNCING and full synchronization from source to target is initiated.

Descriptions of properties setting

[Figure] Mirror Management Screen

Attribute name	Description
Virtual device path	Shows the mounting point.
Meta device path	Shows whether a meta device is internal or external. Meta device path cannot be changed if it is online.
Resynchronization ratio	Set the resynchronization ratio. (Setting range: 0 - 640MB)
Mirror network address	IP address of mirror disk between nodes in a cluster.

Mirror IP address is able to be edited. But this can be done when mirror state is paused.

If mirror status is MIRRORING when you edit the mirror IP address, the status changed to PAUSE automatically.

Policy for recovering auto split brain

Node Priority	policy	Description
Secondary-Secondary	Toss the last primary node	Start synchronization at the node that was primary before a split brain occurred.
	Toss the first primary node	Start synchronization at the node that was second primary before a split brain occurred.
	Toss the one with small changes	Start synchronization at the node with greater changes when a split brain occurred.
	Toss the one with no changes	If only one node has changes, start synchronization on it. If the both nodes have no changes, synchronize either one. If the both node have changes, disconnect communication.
	Disconnect	Cut off a connection without auto recovery.
Primary-Secondary	Consensus	Apply the same recovery policy that is applicable when all the nodes are secondary. If auto recovery fails, disconnect communication.
	Toss secondary node	Make the secondary as a sacrifice node.
	Disconnect	Cut off a connection without auto recovery.
Primary-Primary	Disconnect	Cut off a connection without auto recovery.