Backup facility

[peacog]

The entire system should be backed up regularly to an independently hosted server – such that in the event of server failure or catastrophic data loss the system can be retrieved in a relatively up-to-date status.

[beagaliana]

Hello @peacog ! we might be interested in using backupninja

Backupninja allows you to coordinate system backup by dropping a few simple configuration files into /etc/backup.d/. Most programs you might use for making backups don't have their own configuration file format. Backupninja provides a centralized way to configure and coordinate many different backup utilities.

Duplicity can be used for backing up (it supports SFTP) along with backupninja.

Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server.

Here's an example of the duplicity configuration file that can be set for backupninja: https://0xacab.org/liberate/backupninja/-/blob/master/examples/example.dup

[beagaliana]

Hi @LeScruf ! we're implementing a backup facility using backupninja as described in the comment above. We're currently backing up Drupal files and databases too. Is there any special requirements that should be taken into account? Any protocol of preference or any other thing that might come to your mind. Thanks!

[LeScruf]

Hi @beagaliana, I can't immediately think of anything out of hand. However, we need to figure out a way of using free cloud storage to make sure that there is at least a weekly back-up (which can be perhaps overwritten on a specific cycle) of the local backup ninja. (assuming we are using the free version) ie. running a separate chron script to copy the localhost backup.ninja archive to cloud storage (e.g. a free dropbox or Google Drive account) - with a tested protocol for how to restore a cloud-based archive to the localhost (in the event that the localhost archive is lost). Is that possible? Thanks!