HivePod backups

Back up a pod’s important folders and bring them back on a new pod. Backups are taken with the hivepod CLI; automated backups in the console are coming soon.

What a backup contains

• /home/hivepod/data and /home/hivepod/projects,
• the pod’s settings: OS, size, environment variables and startup command.

Anything outside those two folders isn’t backed up.

Create a backup

hivepod backup create web1 --name before-upgrade

The pod can be running, stopped or suspended. Without --name, the backup is named after the pod and the time.

List backups

hivepod backup list          # all backups
hivepod backup list web1     # one pod

Restore to a new pod

A restore always creates a new pod with the same OS, size and settings. Give it a new name:

hivepod backup restore 3f2a9c1b web1-restored

You can change the subdomain or size with --subdomain and --size (or --cpu, --ram, --disk). The new pod counts toward your plan.

Delete a backup

hivepod backup rm 3f2a9c1b

Backups of deleted pods

Deleting a pod keeps its backups for 7 days. Until then you can restore them into a new pod; after that they are deleted automatically.

hivepod backup list --deleted              # backups of deleted pods, and the date each is kept until
hivepod backup restore 3f2a9c1b web1-again # restore one into a new pod
hivepod backup rm 3f2a9c1b                 # or delete it now

In the console, the HivePods page lists them under Backups of deleted HivePods, with Restore to new HivePod and Delete now.

Kept backups no longer belong to a pod, so they don’t count toward a new pod’s 3-backup limit. They are deleted on schedule even if your account is paused for running out of credit.

Limits

• Up to 3 backups per pod, each up to 20 GB.
• Full-machine pods (Windows, FreeBSD) can’t be backed up.
• A deleted pod’s backups are kept for 7 days, then deleted automatically.