Restoring The Cluster Configuration - IBM Storwize V7000 Troubleshooting And Maintenance Manual

scp -P 22 admin@your_cluster:/tmp/svc.config.backup.*
/offclusterstorage/
where your_cluster is the name of your cluster and offclusterstorage is the location where you want to
store the backup files.
You must copy these files to a location outside of your cluster because the /tmp directory on this node
becomes inaccessible if the configuration node changes. The configuration node might change in
response to an error recovery action or to a user maintenance activity.
Tip: To maintain controlled access to your cluster configuration data, copy the backup files to a
location that is password protected.
8. Ensure that the copies of the backup files are stored in the location that you specified in step 7 on
page 58.
You can rename the backup files to include the configuration node name either at the start or end of the
file names so that you can easily identify these files when you are ready to restore your configuration.
Issue the following command to rename the backup files that are stored on a Linux or IBM AIX
mv /offclusterstorage/svc.config.backup.xml
/offclusterstorage/svc.config.backup.xml_myconfignode
where offclusterstorage is the name of the directory where the backup files are stored and myconfignode is
the name of your configuration node.
To rename the backup files that are stored on a Windows host, right-click the name of the file and select
Rename.

Restoring the cluster configuration

You can restore your cluster configuration data using the command-line interface (CLI).
4 This procedure is also known as a Tier 4 (T4) cluster recovery procedure. You must complete the cluster
recovery procedure before you follow these steps. The cluster recovery procedure works only when all
4
node canisters are in candidate status. If there are any node canisters that display error code 550 or error
4
4 code 578, you must remove their cluster data.
Attention: This procedure is designed to restore information about your cluster configuration, such as
volumes, local Metro Mirror information, local Global Mirror information, storage pools, and nodes. All
the data that you have written to the volumes is not restored. To restore the data on the volumes, you
must restore application data from any application that uses the volumes on the cluster as storage
separately. Therefore, you must have a backup of this data before you follow the cluster configuration
recovery process.
You must regularly back up your cluster configuration data and your application data to avoid data loss.
If a cluster is lost after a severe failure occurs, both cluster configuration and application data is lost. You
must reinstate the cluster to the exact state it was in before the failure, and then recover the application
data.
Following this procedure without a backup copy of application data will result in data loss. If you do not
have a backup copy of application data, contact the IBM Support Center. The IBM Support Center has an
alternative procedure that can restore the cluster while preserving most of the application data.
Important: There are two phases during the restore process: prepare and execute. You must not change
the fabric or cluster between these two phases.
If you do not understand the instructions to run the CLI commands, refer to the command-line interface
4
reference information.
4
®
host:
Chapter 6. Recovery procedures
59