Deleting a virtual server

Hyper Protect Virtual Servers is deprecated. As of 18 August 2024, you can’t create new instances, and access to free instances will be removed. Existing premium plan instances are supported until 31 January 2025. Any instances that still exist on that date will be deleted.

You can use the Hyper Protect Virtual Servers UI or the CLI to delete virtual servers. Deleted servers that belong to paid plans can also be restored before the reclamation period expires.

Deleting a virtual server in the UI

Go to the Resource list (see Retrieving virtual server information) to delete a virtual server.
Select the instance from the Services list and apply the Delete from its action list.

Figure 1. Deleting a virtual server instance

Deleting a virtual server from the CLI

To delete Hyper Protect Virtual Servers from the CLI:

Make sure you know the Cloud resource name (CRN) of the server you want to delete. To find the CRN, run:
```
ibmcloud hpvs instances
```
To delete the server, run the following command:
```
ibmcloud hpvs instance-delete CRN --force
```

Where CRN is Cloud resource name of the server you want to delete. Use --force to force the deletion of the Hyper Protect Virtual Servers instance without showing a confirmation prompt.

You can find more information and example output here.

What happens during the reclamation period

When you delete a virtual server from the resource list, the server isn't deleted immediately, it's stopped and marked for deletion, and a reclamation period of seven days starts. The server is deleted after the reclamation period ends. During this seven-day reclamation period, you can restore the virtual server, or manually trigger a deletion from resource reclamations. Resource reclamations lists the Hyper Protect Virtual Servers that are marked for deletion together with the time (Target time) when the actual deletion is triggered.

Deleting servers that belong to the free plan

The free plan servers expire 30 days after they are created. When a server expires, it's immediately deleted at the backend. The server is also deleted at the backend if it expires during the seven-day reclamation period. Even though the server is deleted at the backend, it's still displayed in the resource list or in the resource reclamations as if it still exists.

If the server has expired, you can remove the entry from the resource list and either:

Wait for the target time to trigger deletion for you, or
Manually trigger the deletion from the resource reclamations.

If an expired server is restored, only the entry within the resource list is restored, not the server itself.

Restoring servers that belong to paid plans

Servers that belong to a paid plans do not expire, and that's why they can be restored during the reclamation period. If a server is restored, the timeframe for which the server was within the resource reclamations is billed to your account.

After the server is deleted, only metadata, which isn't considered to be personal data is kept for 6 months. Make sure you back up important data for future use because you can't recover data after the virtual server has been deleted.