Skip to content
ployzdocs

Restore a volume

A volume with a mirror has restore points: the copies the mirror took on each deploy and every 15 minutes. Restoring one makes a new volume with that point's files and moves your service onto it. The original volume stays until you delete it.

Restore works on managed volumes in Ployz Cloud, once every server that can hold managed volumes runs Ployz 0.2.5 or newer. Until then the points list without Restore. A volume without a mirror has no points; add one under Placement in the volume's Settings tab, see Move a volume.

In Ployz Cloud

Section titled “In Ployz Cloud”

Open the volume and pick Backups. Each point shows when it was taken and the server that holds it, newest first. A mirror keeps only its latest point, so the list has one point per mirror.

Restore on a point stages the restore. It counts in the bottom bar and Details like any other change. Nothing runs on click. Details shows the new volume, named after the original and the point's time, for example pg-data-1027, and says in red what you give up: "Changes after 10:27 are not in pg-data-1027". To drop the restore, discard it in Details.

Deploy runs it before your services. Ployz copies the point to the original's server, makes it the new volume, and starts your service on it. The original keeps its data and its mirror; it shows as not mounted. Delete it from its Settings tab when you no longer need it.

Good to know

Section titled “Good to know”
  • A point is volume data, not a database point in time. It holds the files as the mirror last copied them. A database may need to recover on first start, as after a power cut. For a clean dump, see Back up a database.
  • One restore per volume at a time. Restore is greyed out while the volume's placement deploys.
  • The new volume needs its own room. It has the original's size limit. When the original's server cannot fit a second copy, the deploy fails and says how much space is missing.
  • The original's server must answer for the copy to run. If the point's mirror is gone by then, the deploy fails and names the point.
  • S3 backups are not here yet. The Backups tab says so. Keep your own copies off your servers meanwhile.