ViPR Controller : Decommission ViPR Controller
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
Considerations before decommissioning ViPR Controller:
ViPR Controller is an integrated component of an EHC environment and cannot be decommissioned in an active EHC environment.
Follow ViPR SRM best practices to stop polling, if the ViPR Controller Plugin is used in ViPR SRM.
Discontinue use of vRO workflows that leverage ViPR controller
As provisioning to ViPR Controller managed elements outside of ViPR Controller is not supported, it is not recommended to do a phased approach to decommissioning ViPR Controller.
After ViPR Controller is decommissioned, individual element managers can be used for element management.
After ViPR is decommissioned, all zones, masks, volume, exports, file shares, etc will remain unchanged in the physical ViPR controller managed environment.
Consider using native ViPR backup utilities, take a final backup of ViPR Controller and copy backup to a secure location.
Decommissioning ViPR Controller :
After the above considerations are taken into account the ViPR Controller VMs can be shutdown and removed.
Ensure no tasks/orders are running
Stop the ViPR Controller vApp that hosts the ViPR Controller Virtual Machines
Delete ViPR Controller Virtual Machines and vApp
Article Properties
Article Number: 000020138
Article Type: How To
Last Modified: 20 Nov 2020
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.