Overview

A backup is only useful if you can restore from it. This article covers the common ways to recover data on ALYPOD Cloud: restoring a Pod from a snapshot, pulling files back from a Storage Box with rsync, and downloading objects from S3. Work from a calm, known-good state and always test before overwriting production.

Before you begin

• The backup source: a snapshot, a Storage Box, or an S3 bucket.
• Credentials for the destination and source.
• Enough free disk space to hold the restored data.
• If possible, a maintenance window or a clone target so you do not overwrite live data.

Steps

Restore from a Pod snapshot

1. Open the ALYPOD Console → Compute → CPU Pods and select the Pod.
2. Open the Backups / Snapshots tab and pick a restore point.
3. Choose Restore to roll the disk back, or Clone to new Pod to inspect the data first. Cloning is the safer option.

Restore files from a Storage Box

1. List available backup sets:

bash ssh [email protected] "ls -la /backup/server1"

1. Dry-run the restore first to see what will change:

bash rsync -avn [email protected]:/backup/server1/var/www/ /var/www/

1. Perform the restore (drop -n):

bash rsync -av [email protected]:/backup/server1/var/www/ /var/www/

1. Fix ownership if you restored as root into a service directory:

bash chown -R www-data:www-data /var/www/html

Restore from S3

bash aws --endpoint-url "$S3_ENDPOINT" \ s3 cp s3://my-server-backups/server1/db.sql.gz ./db.sql.gz gunzip db.sql.gz

Troubleshooting

• Problem: Restored files have wrong permissions. Solution: rsync -a preserves them; if you used a plain copy, re-apply ownership and mode explicitly.
• Problem: Database will not start after a file restore. Solution: Stop the service before restoring its data directory, then start it and run integrity checks.
• Problem: You overwrote newer data. Solution: Always restore into a staging directory or clone first, verify, then swap into place.

Related articles

• [Using snapshots for quick recovery]
• [Backing up your server with rsync]
• [Backup best practices (the 3-2-1 rule)]