MetroCluster release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
Assigning pool 1 drives on the surviving site (MetroCluster IP configurations)
Contributors
Suggest changes
-
PDF of this doc site
-
Install a fabric-attached MetroCluster
-
Cable a fabric-attached MetroCluster configuration
-
Plan and install a MetroCluster configuration with array LUNs
-
-
Install a MetroCluster IP configuration
-
Install a stretch MetroCluster configuration
-
Maintain the MetroCluster components
-
Transition from MetroCluster FC to MetroCluster IP
-
Upgrade, refresh, or expand the MetroCluster configuration
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
If drives have been replaced at the disaster site and the system is not configured for ADP, at the surviving site you need to manually assign remote drives located at the disaster site to the surviving nodes' pool 1. You must identify the number of drives to assign.
About this task
For ADP systems, the drives are assigned automatically.
Step
-
On the surviving site, assign the first node's pool 1 (remote) drives:
storage disk assign -n number-of-replacement disks -p 1 0m*This command assigns the newly added and unowned drives on the disaster site.
The following command assigns 22 drives:
cluster_B::> storage disk assign -n 22 -p 1 0m*
