Removing Everpure Cloud Dedicated Instance

Note:

To properly terminate and remove a 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 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 able to phone home. This ensures the Everpure Cloud Dedicated instance is properly de-registered in the Pure-as-a-Service subscription.
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 the Everpure Cloud Dedicated IP Addresses in the Azure Portal 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

A token will be provided in the output. Make a note of the token value.
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
MyCloudBlockStore

Important: Wait about 5 minutes and proceed delete the Everpure Cloud Dedicated managed application.

Note: Everpure Cloud Dedicated manage application deletion takes about 10-15 minutes to completely remove all the underlying resources.

For new arrays deployed with 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 involvement.

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

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

Prerequisites before requesting Pure support:

All Everpure Cloud Dedicated volumes and snapshots must be deleted and eradicated prior to termination of a 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.
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.

Note: After a customer request support to engage in removing/decommissioning the CBS 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