VPS snapshots and recovery

Open the server’s Snapshots tab to review the controls and allowance available to your service. Any extra snapshot subscription has its own price and renewal settings.

Create a recovery point

Before a major change, save application exports and create a snapshot if available. For databases, use their supported backup procedure: a disk snapshot taken during writes may require recovery and is not a substitute for a verified database export.

Wait until the snapshot finishes and confirm it appears in the list. Keep an independent copy of important files away from the server.

Restore

Read the restore confirmation carefully. Restoration rolls the server back and loses changes made after that recovery point. Plan downtime and copy out any newer data you still need first.

Afterward, check boot, network access, applications and database health before reopening the service to users.

Delete or cancel

Deleting a snapshot removes that recovery point. Cancelling extra snapshot storage can affect retention; read the date and retention notice shown in the panel and export important data beforehand. Server cancellation is separate from cancelling a backup add-on.