IBM Storwize V7000 Troubleshooting And Maintenance Manual page 76

To restore your cluster configuration data, follow these steps:
1. The node must be available as a candidate node before you can run this recovery procedure. You
must remove error code 550 or 578 to put the node in candidate status.
2. Use the USB key to initialize the system.
4
3. From the management GUI, click User Management → Users to set up your system and configure an
4
4 SSH key for superuser. This allows access to the CLI.
4. Using the command-line interface, issue the following command to log on to the cluster:
plink -l admin ssh_private_key_file admin@cluster_ip
4 where ssh_private_key_file is the name of the SSH private key file for superuser and cluster_ip is the
IP address or DNS name of the cluster for which you want to restore the cluster configuration.
4
Note: Because the RSA host key has changed, a warning message might display when you connect
to the cluster using SSH.
5. Identify the configuration backup file that you want to restore from.
4
4 Configuration data is automatically backed up daily at 01:00 system time.
4 Attention: You must copy the required backup file to another computer before you continue. To
save a copy of the data, perform the following steps:
4
a. From the management GUI, click Troubleshooting → Support.
4
4 b. Click Show full log listing.
4 c. Find the file name that begins with svc.config.cron.xml.
4 d. Double-click the file to download the file to your computer.
6. Issue the following CLI command to remove all of the existing backup and restore cluster
configuration files that are located on your configuration node in the /tmp directory:
svcconfig clear -all
7. The XML files contain a date and time that can be used to identify the most recent backup. After you
identify the backup XML file that is to be used when you restore the cluster, rename the file to
svc.config.backup.xml. From your desktop, issue the following command to copy the file back on to
the cluster.
pscp -i ssh_private_key_file
full path to identified svc.config.backup.xml
admin@cluster_ip:/tmp/
8. Issue the following CLI command to compare the current cluster configuration with the backup
configuration data file:
svcconfig restore -prepare
This CLI command creates a log file in the /tmp directory of the configuration node. The name of the
log file is svc.config.restore.prepare.log.
Note: It can take up to a minute for each 256-MDisk batch to be discovered. If you receive error
message CMMVC6119E for an MDisk after you enter this command, all the managed disks (MDisks)
might not have been discovered yet. Allow a suitable time to elapse and try the svcconfig restore
-prepare command again.
9. Issue the following command to copy the log file to another server that is accessible to the cluster:
pscp -i ssh_private_key_file
admin@cluster_ip:/tmp/svc.config.restore.prepare.log
full_path_for_where_to_copy_log_files
10. Open the log file from the server where the copy is now stored.
11. Check the log file for errors.
v If there are errors, correct the condition that caused the errors and reissue the command. You must
correct all errors before you can proceed to step 12 on page 61.
v If you need assistance, contact the IBM Support Center.
60
Storwize V7000 Version 6.1.0: Troubleshooting, Recovery, and Maintenance Guide