IBM Storwize V7000 Maintenance Manual page 92

|
|
|
76
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide
d. Continue to follow the on-screen instructions to add the control enclosures.
Decline the offer to configure storage for the new enclosures when asked if
you want to do so.
7. From the management GUI, click Access > Users to set up your system and
configure an SSH key for the superuser. This allows access to the CLI.
8. Using the command-line interface, issue the following command to log on to
the system:
plink -i ssh_private_key_file superuser@cluster_ip
where ssh_private_key_file is the name of the SSH private key file for the
superuser and cluster_ip is the IP address or DNS name of the system for
which you want to restore the configuration.
Note: Because the RSA host key has changed, a warning message might
display when you connect to the system using SSH.
9. Identify the configuration backup file that you want to restore from.
The file can be either a local copy of the configuration backup XML file that
you saved when backing up the configuration or an up-to-date file on one of
the nodes.
Configuration data is automatically backed up daily at 01:00 system time on
the configuration node.
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
to check for backup files on both nodes:
a. From the management GUI, click Settings > Support.
b. Click Show full log listing.
c. Find the file name that begins with svc.config.cron.xml.
d. Double-click the file to download the file to your computer.
10. Issue the following CLI command to remove all of the existing backup and
restore configuration files that are located on your configuration node in the
/tmp directory:
svcconfig clear -all
11. 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 system, rename the file to svc.config.backup.xml. From your
desktop, issue the following command to copy the file back on to the system.
pscp -i ssh_private_key_file
full_path_to_identified_svc.config.backup.xml
superuser@cluster_ip:/tmp/
12. Issue the following CLI command to compare the current 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 CMMVC6200W 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.
13. Issue the following command to copy the log file to another server that is
accessible to the system: