ক্লাউড ব্যাকআপ

Premium plugin (addon backup-cloud; the panel lists it as Cloud Backup). A backup that stays on the server it came from is lost when the server is. Cloud Backups copies every finished backup to a second place: Amazon S3 or any S3 compatible service, an FTP or FTPS server, an SFTP server, or Google Drive. It keeps the newest copies and deletes the older ones.

How it works

The panel makes backups as usual: the scheduled ones from Backup → Backup Configuration and the ones customers make themselves. The plugin watches the list of finished backups. Every five minutes, from the panel cron, it sends each backup that a destination does not have yet, five at a time per destination, and stops after about four minutes so the cron is not blocked. A backup that fails three times is left alone until you look at it.

The cron must be running. See The panel cron.

Cloud Backup Destinations

Backup → Cloud Backup Destinations (root). The page has a table of destinations and a form.

The Destinations table shows: Name, Kind, Where (bucket and endpoint, or host, port and folder), Keep, Sent, Waiting and the Status (On or Off), with these buttons on each row:

• Test - connects and checks the place: it lists the bucket, opens the FTP folder, or logs in over SFTP, and reports what worked.
• Send Now - sends the waiting backups without waiting for the cron.
• Edit, Switch off or Switch on, and Delete. Deleting removes the destination and its log, not the files already uploaded.

Add a destination has a Name, a Kind and the fields of that kind, then two common fields: Keep the newest (how many uploads to keep there; 0 keeps everything) and Status. Secrets are never shown again; leave a password box empty when editing to keep the saved one.

Use a bucket or an account made only for backups. For S3, a key that may write, list and delete in that bucket only is enough.

The transfer log

Transfers (the link on the page) lists each upload: When, Destination, File, Size, Result and Message. A failure shows the reason, for example a wrong key or a full disk at the other end.

Retention

After each upload the plugin deletes the oldest copies beyond Keep the newest from that destination. The count is per destination, over all accounts. If you back up 20 accounts daily and want a week, set Keep to 140. Set the destination's own lifecycle rules too, if the service has them.

Getting a backup back

The plugin copies backups out; it does not pull them in. To restore, download the file from your bucket, FTP or Drive and put it on the server (into data/backups/<user>/, or into the account's home), then use Backup → Backup Restoration in the Host Manager. See Services, backups and server settings. Test a restore once, so you know it works before you need it.

Good to know

• Backups can be large. Check the bandwidth the destination allows, and the time: a 20 GB backup over a slow link may not finish inside one cron run and is retried.
• Credentials are stored in the panel database. Keep the database and its backups private.
• Deleting a destination does not delete uploaded files.
• S3 and Google Drive use PHP curl. SFTP needs the PHP ssh2 extension (php-ssh2), which install.sh does not install; the destination says so when it is missing. FTP needs the ftp extension.