Decommissioning the service

Everpure Cloud Azure Native

Audience
Public
Source Type
Documentation

Decommissioning should be approached as an ordered teardown of the full deployment rather than as a single delete action. Before starting, the workload should be fully migrated away or shut down as appropriate, and all remaining host-side dependencies should be removed.

A typical decommissioning sequence is:

  • Unmount the volumes in the guest operating system

  • Delete the volumes from the Volume Group

  • Delete the Volume Group

  • Delete the Storage Pool

  • Delete the top-level service resource

These steps should be completed in this order. Deleting resources out of sequence can leave dependent objects behind and may prevent higher-level resources from being removed cleanly. For example, if volumes are not removed first, later deletion of the Storage Pool may be blocked.

Important: When using the Platform Console, ensure all of the resources that were created and managed there are also deleted before decommissioning the service. You can find more details on management of Azure / Platform Console resources in Managing Resources across Interfaces.

If decommissioning is being performed at the end of a trial or proof of concept, all resources should be removed before the end of the evaluation period to avoid continued charges.