- Notes, cautions, and warnings
- Preface
- Introduction
- Disaster recovery
- High availability
- Data migration
- SRDF I/O operations
- SRDF write operations
- SRDF read operations
- SRDF/A resilience and performance features
- Management tools
- More information
If all SRDF links are lost for more time than link limbo or Transmit Idle can manage:
These tracks are owed to the secondary array once the links are restored.
When the links are restored, normal SRDF recovery procedures are followed:
Data on non-consistency exempt devices on the secondary array is always dependent-write consistent in SRDF/A active/consistent state, even when all SRDF links fail. Starting a resynchronization process compromises the dependent-write consistency until the resynchronization is fully complete and two cycle switches have occurred.
For this reason, it is important to use TimeFinder to create a gold copy of the dependent-write consistent image on the secondary array.