application commands
metrocluster configure
Suggest changes
PDFs
Configure MetroCluster and start DR mirroring for the node and its DR group
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The metrocluster configure command creates a MetroCluster configuration on either all the nodes in both MetroCluster clusters or solely on nodes in a DR group. The command configures a HA partner, DR partner, and a DR auxiliary partner for the nodes and also starts NVRAM mirroring between the configured DR partner nodes.
In MetroCluster, a DR group is a group of four nodes, two in each of the MetroCluster clusters:
-
In the local cluster, a node and its HA partner,
-
In the peer cluster, a node and its HA partner. These nodes are DR partners to the nodes in the local cluster.
In a two node MetroCluster configuration, a DR group is a group of two nodes, one in each of the MetroCluster clusters.
There can be several DR groups in the MetroCluster configuration. MetroCluster provides synchronous DR protection to all data sets belonging to nodes within a properly configured DR group.
Without the -node parameter, the metrocluster configure command configures all the DR groups in both the MetroCluster clusters.
With the `-node`mynode parameter, the command configures both the mynode node and its HA partner node from the local cluster, and its DR partner and DR auxiliary partner from the peer cluster.
Before running the metrocluster configure command, the aggregates and Vservers on each node must be prepared for the MetroCluster configuration. Each node should have:
-
At least one non-root, mirrored aggregate of size greater than 10GB. This non-root aggregate should not have any volumes in it.
-
No other non-root aggregates. Any other non-root, unmirrored aggregates and volumes should be deleted.
-
No Vservers other than Vservers of type "node" or "admin." Any Vservers that are not of type "node" or "admin" should be deleted.
-
A mirrored and healthy root aggregate.
After the command is successful all nodes in the local and remote clusters will have HA, DR, and DR auxiliary partners and NVRAM mirroring between the DR partners will be turned on. The same conditions apply before running the metrocluster configure command, except that only one DR group is configured.-node`mynode`
For a MetroCluster over IP configuration, the metrocluster configuration-settings commands must be completed before using the metrocluster configure command. The commands required to be completed are:
Parameters
[-node-name {<nodename>|local}]- Node to Configure-
This optional parameter specifies the name of a single node in the local cluster. The command creates MetroCluster configuration on the local node specified by this parameter and the three other nodes belonging to the same DR group.
[-refresh {true|false}]- Refresh Configuration (privilege: advanced)-
This optional parameter specifies if the node partner configuration steps should be done again. Not specifying this parameter will cause the MetroCluster configuration to continue using the current node partner information.
[-allow-with-one-aggregate {true|false}]- Override the Two Data Aggregates Requirement (privilege: advanced)-
This optional parameter specifies if MetroCluster configuration should be allowed with only one data aggregate in each cluster. This option has no effect if two or more aggregates are present.
Examples
The following example shows the creation of the MetroCluster configuration for a single DR group:
clusA::> metrocluster show
Cluster Configuration State Mode
------------------------------ ---------------------- ------------------------
Local: clusA not-configured -
Remote: clusB not-configured -
clusA::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- ------------------ -------------- --------- --------------------
- clusA clusA-01 ready to configure
- -
clusA-02 ready to configure
- -
clusA-03 ready to configure
- -
clusA-04 ready to configure
- -
4 entries were displayed.
clusA::> metrocluster configure -node clusA-01
[Job 45] Job succeeded: Configure is successful
clusA::> metrocluster show
Cluster Configuration State Mode
------------------------------ ---------------------- ------------------------
Local: clusA partially-configured normal
Remote: clusB partially-configured normal
clusA::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- ------------------ -------------- --------- --------------------
- clusA clusA-03 ready to configure
- -
clusA-04 ready to configure
- -
1 clusA clusA-01 configured enabled normal
clusA-02 configured enabled normal
clusB clusB-01 configured enabled normal
clusB-02 configured enabled normal
6 entries were displayed.
The following example shows the creation of the MetroCluster configuration for all DR groups:
clusA::> metrocluster show
Cluster Configuration State Mode
------------------------------ ---------------------- ------------------------
Local: clusA not-configured -
Remote: clusB not-configured -
clusA::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- ------------------ -------------- --------- --------------------
- clusA clusA-01 ready to configure
- -
clusA-02 ready to configure
- -
clusA-03 ready to configure
- -
clusA-04 ready to configure
- -
4 entries were displayed.
clusA::> metrocluster configure
[Job 45] Job succeeded: Configure is successful
clusA::> metrocluster show
Cluster Configuration State Mode
------------------------------ ---------------------- ------------------------
Local: clusA configured normal
Remote: clusB configured normal
clusA::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- ------------------ -------------- --------- --------------------
1 clusA clusA-01 configured enabled normal
clusA-02 configured enabled normal
clusB clusB-01 configured enabled normal
clusB-02 configured enabled normal
2 clusA clusA-03 configured enabled normal
clusA-04 configured enabled normal
clusB clusB-03 configured enabled normal
clusB-04 configured enabled normal
8 entries were displayed.