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

v For each node entry, make a note of the value of following properties;
IO_group_id, canister_id, enclosure_serial_number.
v Use the CLI sainfo lsservicenodes command and the adata to determine which
node canisters previously belonged in each IO group.
Restoring the system configuration should be performed via one of the nodes
previously in IO group zero. For example, property name="IO_group_id"
value="0" . The remaining enclosures should be added, as required, in the
appropriate order based on the previous IO_group_id of its node canisters.
Note: It is not currently possible to determine which canister within the identified
enclosure was previously used for cluster creation. Typically the restoration should
be performed via canister 1.
The Storwize V7000 analyzes the backup configuration data file and the system 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, drives, the Ethernet network, and the
SAN fabric.

Backing up the system configuration using the CLI

You can back up your configuration data using the command-line interface (CLI).
Before you begin
Before you back up your configuration data, the following prerequisites must be
met:
v No independent operations that change the configuration can be running while
the backup command is running.
v No object name can begin with an underscore character (_).
About this task
The backup feature of the svcconfig CLI command is designed to back up
information about your system configuration, such as volumes, local Metro Mirror
information, local Global Mirror information, managed disk (MDisk) groups, and
nodes. All other data that you wrote to the volumes is not backed up. Any
application that uses the volumes on the system as storage, must back up its
application data using the appropriate backup methods.
You must regularly back up your configuration data and your application data to
avoid data loss. It is recommended that this is performed after any significant
changes in configuration have been made to the system. Note that the system
automatically creates a backup of the configuration data each day at 1AM. This is
known as a cron backup and is written to /dumps/svc.config.cron.xml_<serial#>
on the configuration node. A manual backup can be generated at any time using
the instructions in this task. If a severe failure occurs, both the configuration of the
system and application data may be lost. The backup of the configuration data can
be used to restore the system configuration to the exact state it was in before the
failure. In some cases it may be possible to automatically recover the application
data. This can be attempted via the <Recover System Procedure> also known as a
Tier 3 (T3) procedure. Restoring the system configuration without attempting to
recover the application data is performed via the <Restoring the System
Chapter 7. Recovery procedures
79