The resource status message reflects the role and state of the RDF pair. For example, the resource status and status message of Faulted Split, is reported when the RDF pair is in a Split state.
The RDF pair state is mapped to the associated resource status as described in the following table.
Table 2–2 Mapping From the RDF Pair State to the Resource Status
Condition |
Resource Status |
Status Message |
---|---|---|
The RDF pair state is Invalid and the pair state is not Incorrect Role. |
Faulted |
Invalid state |
The RDF pair state is Partitioned and the pair state is not Incorrect Role, or Invalid. |
Faulted |
Partitioned |
The RDF pair state is Suspended and the pair state is not Incorrect Role, Invalid, or Partitioned. |
Faulted |
Suspended |
The RDF pair state is SyncInProg and the pair state is not Incorrect Role, Invalid, Partitioned, or Suspended. |
Degraded |
SyncInProg |
The RDF pair state is R1 UpdInProg and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended, or SyncInProg. |
Faulted |
R1 UpdInProg |
The RDF pair state is Split and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended,SyncInProg, or R1 UpdInProg. |
Faulted |
Split |
The RDF pair state is Failed over and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended,SyncInProg, R1 UpdInProg, or Split. |
Faulted |
Failed over |
The RDF pair state is R1 Updated and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended,SyncInProg, R1 UpdInProg, Split, or Failed over. |
Faulted |
Replicating with role change |
The RDF pair state is Synchronized. |
Online |
Replicating |
The state of the RDF pair determines the availability of consistent data in the partnership. When the state of the RDF resource on the primary or secondary cluster is Degraded or Faulted, the data volumes might not be synchronized even if the application can still write data from the primary volume to the secondary volume. The RDF pair will be in a Partitioned state and the invalid entries will be logged as the data is written to the primary volume. Manual recovery operations are required to resolve the error and resynchronize the data.