Restoring Data; Restoring Asynchronous Data - IBM Storwize V7000 Unified Problem Determination Manual

5. Check that the file systems are mounted by using the lsmount -r management
6. See Checking the GPFS file system mount on each file module if any file
Note that the management GUI can become very slow when the Storwize V7000
CLI is restricted. When you log on to the management GUI, it issues a warning
that the Storwize V7000 CLI is restricted. The management GUI runs the fix
procedure to direct you to send logs to IBM. The fix procedure directs you back to
this procedure to make the file systems accessible again.
To collect the Storwize V7000 logs, select the Collect Logs option from the
navigation in the service assistant. Choose the With statesave option.
The fix procedure re-enables the control enclosure CLI, provided that IBM support
approved of this procedure.
After completing this procedure the health status indicator could still be red
because the Fibre Channel links may not have sent an event showing that they
have recovered. Refer to Connectivity issues to help you see if this is the case and
refer to Health status and recovery to help you return the health status indicator
back to green.

Restoring data

This section covers the recovery procedures that relate to restoring data.

Restoring asynchronous data

Recovering a file system with asynchronous replication requires that you configure
and start a replication relationship from the target site to the source site.
Before you begin
After the source site (site A) has failed, set the target site (Site B) as the new source
site and replicate back to Site A. To restore asynchronous data, perform the
following steps:
Procedure
1. Where the previous replication relationship was Site A replicating to Site B,
2. Start the replication that was configured in step 1 by using the startrepl
3. If the amount of data that is to be replicated back to Site A is large, multiple
286
Storwize V7000 Unified: Problem Determination Guide Version
lsnode -r
CLI command:
lsmount -r
systems are not mounted.
configure the asynchronous replication by reversing the source and target site
information. Site B replicates to Site A. See "Configuring asynchronous
replication" and transpose the source and target information.
–fullsync CLI command. See "Starting and stopping asynchronous replication"
for more information.
replications from Site B to Site A might be required. Multiple replications are
required until modifications to Site B can be suspended to perform a final
replication to Site A to enable Site A to synch up.
Note: Do not use the fullsync option for these incremental replications.