Take a DigitalOcean Droplet snapshot from the WHMCS client area
Create a manual snapshot before a server change when you need a recovery point for its main disk. PD DigitalOcean Droplets exposes this through the service’s Snapshots page when your offering includes an allowance.
Check what the snapshot covers
A Droplet snapshot covers the main server disk. Attached additional storage is separate and is not included in this module’s Droplet snapshot. Plan backups for data on that extra volume independently.
DigitalOcean documents Droplet and volume snapshots as separate resource operations. If an application is writing data, use its normal consistency/backup process before relying on an infrastructure snapshot for recovery.
Check the allowance
Your hosting team enables Client: Snapshots and sets the allowance for the offering. The number purchased at checkout takes precedence over the product’s Included snapshots default. 0 means none included when no purchased allowance applies.
Take the recovery point
- Your customer signs in to the WHMCS client area and opens the correct service.
- Open Snapshots and check the number used against the available allowance.
- Choose Take snapshot, read the confirmation and submit once.
- Watch the operation state and Activity rather than issuing another request while it is working.
- Confirm the new snapshot is available, and record its name/time and the change it precedes.
A requested snapshot is not yet a usable completed recovery point. If the allowance is full, review existing recovery needs before deleting an older copy.
Remember retention and cost
Manual snapshots taken by the customer remain on the operator’s DigitalOcean account after the service is cancelled or terminated. They can continue to incur provider storage charges. Cancellation of the server is not a snapshot-deletion instruction.
Your hosting team should agree snapshot retention with the customer before cancellation and review the copies still kept in its own DigitalOcean account. Do not delete the only needed recovery point merely to clear an allowance message.
For recovery, use the rebuild and snapshot restore guide. If taking the snapshot fails, keep the original request time, allowance and exact error; compare the current snapshot/operation state before deciding whether another request is appropriate.
See the PD DigitalOcean Droplets WHMCS guide for related tasks, or explore the module.