The process of a demotion of a target pod is another way to say that you are ending an ActiveDR test. The implication is that the source pod is still promoted and in-use.
You can verify this by examining your pod replica link state. The current pod being view (activeDRpodB) is promoted, and also the target for the replication:
Prior to demotion you should verify two things:
-
Are there additional volumes in the target pod as compared to the source pod? If so, it is possible someone accidentally provisioned a new volume into the target pod while it was demoted. Verify the "additional" volume usage prior to demotion.
The simplest way to ensure the pod is not actively serving I/O is to check the performance statistics.
Navigate to Analysis -> Performance -> Pods, then select the target pod.
If there is detectable I/O move to the Volumes tab and search for volumes with the pod name:
Investigate the volumes with active I/O and determine if they should be terminated or moved out of the target pod.
Once the pod has been cleared...
...it is time to verify that no unexpected volumes are in the pod. Once the pod is promoted, it not only makes the replicated objects available, but also allows new objects to be created within the pod.
If a user provisions a new volume into that pod, the volume will be removed entirely once the pod has been demoted, as a promoted target pod is seen as only having temporary changes that do not need to persist.
A simple way to ensure you do not accidentally remove a volume, check that the volume count in the source pod is the same as the target pod. In the source pod, look at the volumes box and in the upper right hand corner there will be a count of volumes:
This is showing two volumes.
In the target pod, it has the same.
Once you have confirmed that no unexpected volumes are in the pod, you can proceed to demote:
If it is determined that after the pod is demoted that some data from the point-in-time immediately prior to demotion is needed, the contents of the pod at that time is protected temporarily in an "undo" pod. This undo pod is kept in the "destroyed pods" area for a period designated by the eradication timer which defaults to 24 hours, but can be increased upon request to Everpure support.
This undo pod can be copied to a new pod so the contents can be used/manipulated.