Backing Up And Restoring The System Configuration - IBM Storwize V7000 Unified Problem Determination Manual

v Parity arrays will likely be syncing to restore parity; they do not have
v Because there is no redundancy in this process, bad blocks may have been
v Parity arrays could be marked as corrupt. This indicates that the extent of lost
v Raid-6 arrays that were actually degraded prior the system recovery may require
Be aware of the following differences regarding the recovered configuration:
v FlashCopy mappings are restored as "idle_or_copied" with 0% progress. Both
v The management ID is different. Any scripts or associated programs that refer to
v Any FlashCopy mappings that were not in the "idle_or_copied" state with 100%
v Intersystem remote copy partnerships and relationships are not restored and
v Consistency groups are not restored and must be re-created manually.
v Intrasystem remote copy relationships are restored if all dependencies were
v The system time zone might not have been restored.
v The GPFS cluster quorum state held on the control enclosure might not have
Before using the block volumes that are accessed by the SAN or with iSCSI,
perform the following tasks:
v Start the block host systems.
v Manual actions might be necessary on the hosts to trigger them to rescan for
v Verify that all mapped volumes can be accessed by the hosts.
v Run file system consistency checks on the block hosts.
v Run the application consistency checks.
Before using the file volumes that are used by GPFS on the file modules to provide
Network Attached Storage (NAS), perform the following task:
v Contact IBM support for assistance with recovering the GPFS quorum state so

Backing up and restoring the system configuration

You can back up and restore the configuration data for the system after
preliminary tasks are completed.
Configuration data for the system provides information about your block system
and the objects that are defined in it. The backup and restore functions of the
svcconfig command can back up and restore only your configuration data for the
264
Storwize V7000 Unified: Problem Determination Guide Version
redundancy when this operation proceeds.
created where data is not accessible.
data is wider than in-flight IO, and in order to bring the array online, the data
loss must be acknowledged.
a full restore from backup. For this reason, it is important to have at least a
capacity match spare available.
volumes must have been restored to their original I/O groups.
the system-management ID of the clustered system must be changed.
progress at the point of disaster have inconsistent data on their target disks.
These mappings must be restarted.
must be re-created manually.
successfully restored to their original I/O groups.
been restored.
devices. You can perform this task by disconnecting and reconnecting the Fibre
Channel cables to each host bus adapter (HBA) port.
that access to files as NAS can be restored.