Recover system procedure
The recover system procedure recovers the entire storage system if the data has
been lost from all control enclosure node canisters. The procedure re-creates the
storage system by using saved configuration data. The recovery might not be able
to restore all volume data. This procedure is also known as Tier 3 (T3) recovery.
After you perform the storage system recovery procedure, contact IBM support.
They can assist you with recovering the file modules so that access to the file
systems can be restored.
Attention:
Perform service actions only when directed by the fix procedures. If
used inappropriately, service actions can cause loss of access to data or even data
loss. Before attempting to recover a storage system, investigate the cause of the
failure and attempt to resolve those issues by using other fix procedures. Read and
understand all of the instructions before performing any action.
Attention:
Do not attempt the recovery procedure unless the following conditions
are met:
v
All hardware errors are fixed.
v
All node canisters have candidate status.
v
All node canisters must be at the same level of software that the storage system
had before the system failure. If any node canisters were modified or replaced,
use the service assistant to verify the levels of software, and where necessary, to
upgrade or downgrade the level of software.
The system recovery procedure is one of several tasks that must be performed. The
following list is an overview of the tasks and the order in which they must be
performed:
1.
Preparing for system recovery
a.
Review the information regarding when to run the recover system
procedure
b.
Fix your hardware errors
c.
Remove the system information for node canisters with error code 550 or
error code 578 by using the service assistant.
2.
Performing the system recovery. After you prepared the system for recovery
and met all the pre-conditions, run the system recovery.
Note:
Run the procedure on one system in a fabric at a time. Do not perform
the procedure on different node canisters in the same system. This restriction
also applies to remote systems.
3.
Performing actions to get your environment operational
v
Recovering from offline VDisks (volumes) by using the CLI
v
Checking your system, for example, to ensure that all mapped volumes can
access the host.
When to run the recover system procedure
A recover procedure must be attempted only after a complete and thorough
investigation of the cause of the system failure. Attempt to resolve those issues by
using other service procedures.
240
Storwize V7000 Unified: Problem Determination Guide Version
|
|
|
|
|
|
Summary of Contents for Storwize V7000
Page 6: ...vi Storwize V7000 Unified Problem Determination Guide Version...
Page 8: ...viii Storwize V7000 Unified Problem Determination Guide Version...
Page 10: ...x Storwize V7000 Unified Problem Determination Guide Version...
Page 18: ...xviii Storwize V7000 Unified Problem Determination Guide Version...
Page 24: ...xxiv Storwize V7000 Unified Problem Determination Guide Version...
Page 32: ...8 Storwize V7000 Unified Problem Determination Guide Version...
Page 274: ...250 Storwize V7000 Unified Problem Determination Guide Version...
Page 278: ...254 Storwize V7000 Unified Problem Determination Guide Version...
Page 296: ...272 Storwize V7000 Unified Problem Determination Guide Version...
Page 306: ...282 Storwize V7000 Unified Problem Determination Guide Version...
Page 312: ...288 Storwize V7000 Unified Problem Determination Guide Version...
Page 313: ......
Page 314: ...Printed in USA GA32 1057 04...