We continue billing for stopped Virtual Machines only for reserved resources: SSD and HDD disks (based on their size), external IP addresses, personal VLANs, and reserved PCI-Express devices (available only for GPU servers). vCPU and RAM are not billed when the machine is stopped.
To avoid charges for an inactive Virtual Machine, you must either delete it or archive it (Shelve).
If you have a Volume-backed Virtual Machine, after deletion the associated Volume will remain in the Volumes section. This Volume contains all your data and can be used later to recreate the exact same Virtual Machine. If you do not plan to reuse this Volume, you should delete it manually — otherwise, it will continue to incur storage charges.
Important: Before deleting a Volume-backed Virtual Machine, make sure to stop it using the Stop command in the Actions dropdown menu. Failure to do so may affect the integrity and usability of the Volume.
Note: You can deploy only one Virtual Machine from a single Volume. If you need to create multiple Virtual Machines from the same source, create a Volume Snapshot instead. From one Snapshot, you can launch any number of Virtual Machines.
If you have a Local Virtual Machine, create a Snapshot before deletion. When you need to use the Virtual Machineagain, simply redeploy it from that Snapshot.
Alternatively, you can use the Shelve option in the Actions menu. Shelve archives the server and releases compute resources, so you are no longer charged for CPU, RAM, or disk usage. You will only be billed for the storage of the server’s Snapshot (or Volume) and its IP address. A Snapshot is created automatically when you use Shelve.
Note: While the server is in the shelved_offloaded state, you cannot detach the Volume from it. To resume operation, select Unshelve from the Actions menu.
Costs for Snapshot and Volume storage are available on the Pricing page.