In version 6.6.6 of Everpure Cloud Dedicated for Azure, a new feature allows customers to upgrade to a new version of Purity without needing to contact Everpure support. The upgrade process is seamless and can be performed via the Everpure CLI or REST API. This KB article will guide you through the steps to set up an Everpure Cloud Dedicated array for Customer-Driven Upgrades (CDUs) and the process for executing an upgrade.
There are a few important notes and caveats to be aware of for CDUs:
-
Beginning with Purity version 6.6.6, the methodology described here is the supported upgrade path for all Everpure Cloud Dedicaed Purity upgrades.
-
Customers can request that their upgrade be executed by Everpure support as before via opening a case with Everpure Technical Services.
-
If a Purity upgrade being driven by the customer experiences a failure on Everpure Cloud Dedicated, automatic rollback is not supported via CDU. In the event this occurs, please open a case with Everpure Technical Services for assistance.
-
Customer-Driven Upgrades are NOT supported with ActiveCluster. If you are using ActiveCluster in your Everpure Cloud Dedicated setup, please reach out to Everpure support for assistance.
reconfigure_paz.py script without EE/ENG approval. Please open a ES JIRA, input your analysis then escalate to request approval from the Escalation Engineering and Everpure Cloud Dedicated Engineering teams to use the script.