While IdlingDisconnected , if a write I/O is received that causes the loss of synchronization (synchronized attribute transitions from true  to false ) and the relationship was not stopped (either through a user stop or a persistent error), an event is raised to notify you of the condition. This same event also is raised when this condition occurs for the ConsistentSynchronized  state. 

When the relationship or Consistency Group becomes connected again, the relationship becomes InconsistentCopying  automatically unless either of the following conditions are true: 

GLYPH<SM590000> The relationship was InconsistentStopped  when it became disconnected. 

GLYPH<SM590000> The user issued a stop  command while disconnected. 

In either case, the relationship or Consistency Group becomes InconsistentStopped . 

## ConsistentDisconnected 

ConsistentDisconnected  is a disconnected state. The target volumes in this half of the relationship or Consistency Group are all in the auxiliary role, and accept read I/O but not write I/O. 

This state is entered from ConsistentSynchronized  or ConsistentStopped  when the auxiliary side of a relationship becomes disconnected. 

In this state, the relationship or Consistency Group displays an attribute of FreezeTime, which is the point when Consistency was frozen. When it is entered from ConsistentStopped , it retains the time that it had in that state. When it is entered from ConsistentSynchronized , the FreezeTime shows the last time at which the relationship or Consistency Group was known to be consistent. This time corresponds to the time of the last successful heartbeat to the other system. 

A stop  command with the -access  flag set to true  transitions the relationship or Consistency Group to the IdlingDisconnected  state. This state allows write I/O to be performed to the auxiliary volume and is used as part of a DR scenario. 

When the relationship or Consistency Group becomes connected again, the relationship or Consistency Group becomes ConsistentSynchronized  only if this action does not lead to a loss of consistency. The following conditions must be true: 

GLYPH<SM590000> The relationship was ConsistentSynchronized  when it became disconnected. 

GLYPH<SM590000> No writes received successful completion at the master while disconnected. 

Otherwise, the relationship becomes ConsistentStopped . The FreezeTime setting is retained. 

## Empty 

This state applies only to Consistency Groups. It is the state of a Consistency Group that has no relationships and no other state information to show. It is entered when a Consistency Group is first created. It is exited when the first relationship is added to the Consistency Group, at which point the state of the relationship becomes the state of the Consistency Group. 

