|Article Number: 499498
||Article Version: 3
||Article Type: Break Fix
VPLEX VS1,VPLEX VS2,VPLEX VS6,VPLEX Metro,VPLEX GeoSynchrony 5.4 Service Pack 1,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 1,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 3,VPLEX GeoSynchrony 5.4 Service Pack 1 Patch 4
The official SolVe Desktop procedure to shutdown or restart a VPLEX cluster will result in IO disruption on RecoverPoint-enabled distributed consistency-groups for MetroPoint configurations until IO is manually resumed in the applicable consistency-groups.
Normal RecoverPoint configurations (non-MetroPoint) will not have IO disruption.
The procedure Phase 1, Task number 16, asks to identify and take note of the RecoverPoint enabled distributed consistency-groups (if applicable) with detach rule configured as winner for the cluster that is going to be shutdown / restarted (i.e. cluster-1-winner if cluster-1 is going to be shutdown / restarted).
If RecoverPoint is enabled on a distributed consistency-group, you cannot modify the group’s detach-rule, hence if you shutdown or restart the cluster that is configured as the winner for those consistency-group, the distributed devices within the consistency-group will be suspended in MetroPoint configurations until it is manually resumed in the cluster that will remain up. The procedure’s Phase 1 Task 21 asks to manually resume these suspended RecoverPoint enabled consistency-groups on the cluster that will remain online with the “choose-winner” CLI command once you have shutdown the winning cluster.
This means it’s expected to experience IO disruption on the distributed devices within the RecoverPoint enabled distributed consistency-groups for the time frame between shutting down the winning cluster and manually resuming then in the cluster that remains online.
Depending on the host type, this time frame might be enough for them to consider they permanently lost access to those volumes, entering a state where a reboot is necessary to recover access to them even after manually resuming IO on the VPLEX cluster that remains online.
Follow the official SolVe Desktop procedure
For MetroPoint configurations, currently you should plan your maintenance considering that there will be IO disruption in all volumes within RecoverPoint enabled distributed consisdency-groups, and act accordingly from host side to prevent unplanned outages or issues.
Engineering is working on alternative steps to prevent IO disruption on MetroPoint, which will be added to this KB article and the official VPLEX cluster shutdown or restart SolVe Desktop procedure when available.
Engineering will also add more Clarification and clear steps for the VPLEX cluster shutdown or restart procedure with RecoverPoint in the official SolVe Desktop procedure.