Backups in the form of database dumps of our relational databases happen every day (usually between 12 AM and 1 AM CET/CEST). The backups will be created on the database replica server to prevent load impacts on the primary instance.
Afterwards the dumps will be copied to our backup server via
rsync and will be kept there for 30 days. Every database hosted by us gets at least this backup strategy.
Additionally and upon request we can provide Point-In-Time-Recoverability for dedicated databases. For our shared PostgreSQL cluster PITR is available by default. Restore Points are available up to 7 days in the past.
We do not backup Redis data but let it write its data to disk in certain intervals determined by amount of data changed and a time interval. Writing data to disk is not a backup. It's not copied anywhere. It's not incremental. It's not rotated. Disk persistence in Redis is needed for replication.
For your deployments the directory
/gluster/shared/www.acme.com/ will be backed up. It is copied via
rsync to our backup machine and will be rotated 7 times, so we can roll back to a state between 7 and 8 days.
If you need any further directories to be backed up or need a longer retention time you can contact us. Please mind that you could also copy the data to
/gluster/shared/www.acme.com/ and symlink it yourself.
Backup restore test and monitoring
We frequently check that our backup is working as expected and we are able to restore backups:
- every week a few backup dumps are randomly selected and are restored to a local database by an operations engineer
- every week we verify that new files are included in the filesystem backups
- additionally we monitor if the sync for the filesystem backup runs every day
- we get notified if backup jobs fail
- there is a continuous monitoring if PITR backup is receiving new data
- once a month we also restore a PITR backup