Removing Everpure Cloud Dedicated on AWS

Everpure Cloud Dedicated for AWS
Audience
Public
Technology Integrations
Amazon Web Services (AWS)
Source Type
Documentation

Note:

Pure Support only: For version 5.3.0.aws0, 5.3.0.aws1, 5.3.0.aws2, Everpure Cloud Dedicated can only be removed (terminated) by Everpure Technical Services to ensure all the resources in the stack are cleanly removed. Please contact Everpure Technical Services for Everpure Cloud Dedicated instance removals.Manual Deactivation Workflow | Everpure Cloud Dedicated for Azure

For version 6.1+, 6.2+, and 6.3+

For version 6.1+, 6.2+, and 6.3+, customers can perform Everpure Cloud Dedicated deletion without Pure Support involvement.

Note:

Do not manually delete the Everpure Cloud Dedicated stack in CloudFormation. To properly terminate and remove an Everpure Cloud Dedicated instance, run the two CLI commands provided below. The proper steps will ensure that the Everpure Cloud Dedicated instance removal is reflected accurately and accounted for in the Evergreen//one (formerly known as Pure-as-a-Service) subscription on Pure1.

Prerequisites:

  • All Everpure Cloud Dedicated volumes and snapshots must be deleted and eradicated prior to termination of an Everpure Cloud Dedicated instance. This includes Protection Group snapshots.
  • All connected arrays and targets must be disconnected from any type of Purity replication.
  • Everpure Cloud Dedicated instance must be able to phone home. This ensures the Everpure Cloud Dedicated instance is properly de-registered in the Pure-as-a-Service subscription.
  • Check and disable termination protection for the Everpure Cloud Dedicated CloudFormation stack:

    Once the prerequisite array state has been achieved, the following steps will terminate and remove the Everpure Cloud Dedicated instance.

  • Using SSH, log into the Everpure Cloud Dedicated instance management port.

    Note: See the Viewing Everpure Cloud Dedicated Network Interfaces section for the management port IP address.

  • Run the following command:

purearray factory-reset-token create

Note:

Example


purearray factory-reset-token create
Name               Token
MyCloudBlockStore  4109498
  1. A token will be provided in the output. Make a note of the token value.
  2. Run the following command with the token from the previous command.

purearray erase --factory-reset-token <token> --eradicate-all-data

This allows the Everpure Cloud Dedicated instance to communicate with Pure1 prior to deleting itself.

Note:

Example


purearray erase --factory-reset-token 4109498 --eradicate-all-data
Name
MyCloudBlockStoreBlockStore
(Optional) The previous command triggers the Everpure Cloud Dedicated CloudFormation deletion process. It is important to note that removal of the S3 bucket is not included in this process. Therefore, once the Everpure Cloud Dedicated CloudFormation delete process completes, you next have to delete the S3 bucket associated with it manually.

For version 6.4+

In version 6.4, Pure has introduced auto-on SafeModeâ„¢ protection for volumes on a new array. This would prevent removing all the objects protected by default in the array. Therefore, customers can only perform Everpure Cloud Dedicated deletion with Everpure Technical Services involvement.

The screenshot below shows the Default Protection Groups under Protection > Array.

You can see that the default protection group pgroup-auto is ratcheted.

Note:

Do not manually delete the Everpure Cloud Dedicated stack in CloudFormation. To properly terminate and remove a Everpure Cloud Dedicated instance, follow the steps below.

Prerequisites before requesting Pure support:

  • All Everpure Cloud Dedicated volumes and snapshots must be deleted and eradicated prior to termination of an Everpure Cloud Dedicated instance. This includes Protection Group snapshots. Note: you won't be able to eradicate snapshots under the default pgourp-auto or destroy the protection group itself.
  • All connected arrays and targets must be disconnected from any type of Purity replication.
  • Everpure Cloud Dedicated instance must be able to phone home. This ensures the Everpure Cloud Dedicated instance is properly de-registered in the Pure-as-a-Service subscription.
  • Check and disable termination protection for the Everpure Cloud Dedicated CloudFormation stack.
  • The last step is to enable Remote Assist.

    Once the prerequisite array state has been achieved, request Pure Support and ask for decommissioning the array.

After a customer request support to engage in removing/decommissioning the Everpure Cloud Dedicated array. The following commands have to be executed:
  • Disable SafeMode from the default protection group. 
    purepgroup retention-lock unlock pgroup-auto
  • Remove the protection group from the Default Protection. 
    purearray default-protection set "" --pgroup ""
  • Destroy the protection group. 
    purepgroup destroy pgroup-auto
  • Eradicate the protection group. 
    purepgroup eradicate pgroup-auto
  • Create factory reset token. 
    purearray factory-reset-token create
  • Run the erase command with the token from the previous command. 
    purearray erase --factory-reset-token <token> --eradicate-all-data