Backing Up The Cluster Configuration Using The Cli - IBM Storwize V7000 Troubleshooting And Maintenance Manual

Table of Contents

Advertisement

v No independent operations that change the cluster configuration can be running while the backup
command is running.
v No object name can begin with an underscore character (_).
Note:
v The default object names for controllers, I/O groups, and managed disks (MDisks) do not restore
correctly if the ID of the object is different from what is recorded in the current cluster configuration
data file.
v All other objects with default names are renamed during the restore process. The new names appear in
the format name_r where name is the name of the object in your cluster.
Before you restore your cluster configuration data, the following prerequisites must be met:
v You have the Security Administrator role associated with your user name and password.
v You have a copy of your backup cluster configuration files on a server that is accessible to the cluster.
v You have a backup copy of your application data that is ready to load on your cluster after the restore
configuration operation is complete.
v You know the current license settings for your cluster.
v You have not removed any hardware since the last backup of your cluster configuration. If you had to
replace a faulty node, the new node must use the same worldwide node name (WWNN) as the faulty
node that it replaced.
Note: You can add new hardware, but you must not remove any hardware because the removal can
cause the restore process to fail.
v No zoning changes have been made on the Fibre Channel fabric which would prevent communication
between the Storwize V7000 and other nodes or storage controllers which are present in the
configuration.
The restore must be performed to a single node cluster. You can restore the configuration using any node
as the configuration node. However, if you do not use the node that was the configuration node when
the cluster was first created, the unique identifier (UID) of the volumes that are within the I/O groups
can change. This can affect IBM Tivoli
Manager, and any other programs that record this information.
The Storwize V7000 analyzes the backup configuration data file and the cluster to verify that the required
disk controller system nodes are available.
Before you begin, hardware recovery must be complete. The following hardware must be operational:
hosts, Storwize V7000, disk controller systems, disks, the Ethernet network, and the SAN fabric.

Backing up the cluster configuration using the CLI

You can back up your cluster configuration data using the command-line interface (CLI).
Before you back up your cluster configuration data, the following prerequisites must be met:
v No independent operations that change the cluster configuration can be running while the backup
command is running.
v No object name can begin with an underscore character (_).
v All objects must have non-default names, that is, names that are not assigned by the Storwize V7000.
Note:
– The default object names for controllers, I/O groups, and managed disks (MDisks) do not restore
correctly if the ID of the object is different from what is recorded in the current cluster configuration
data file.
®
Storage Productivity Center for Fabric, VERITAS Volume
Chapter 6. Recovery procedures
57

Advertisement

Table of Contents
loading

Table of Contents