v You have the Security Administrator role associated with your user name and
password.
v You have a copy of your backup configuration files on a server that is accessible
to the system.
v You have a backup copy of your application data that is ready to load on your
system after the restore configuration operation is complete.
v You know the current license settings for your system.
v You did not remove any hardware since the last backup of your configuration.
v No zoning changes were made on the Fibre Channel fabric which would prevent
communication between the Storwize V7000 Unified and any storage controllers
which are present in the configuration.
v For configurations with more than one I/O group, if a new system is created on
which the configuration data is to be restored, the I/O groups for the other
control enclosures must be added.
Use the following steps to determine how to achieve an ideal T4 recovery:
v Open the appropriate svc.config.backup.xml (or svc.config.cron.xml) file with a
suitable text editor or browser and navigate to the node section of the file.
v For each node entry, make a note of the value of the following properties:
IO_group_id, canister_id, enclosure_serial_number .
v Use the CLI sainfo lsservicenodes command and the data to determine which
node canisters previously belonged in each I/O 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.
Before you begin, hardware recovery must be complete. The following hardware
must be operational: hosts, Storwize V7000 Unified enclosures, internal flash drives
and expansion enclosures (if applicable), the Ethernet network, the SAN fabric, and
any external storage systems (if applicable).
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, storage pools, and nodes. All other
390 Storwize V7000 Unified: Problem Determination Guide 2073-720
To Next Page
Loading...
Need help?
General
