Backups

In Seravo's WP service, backups are automatically taken every night and kept for 30 days. Backups can be found on the server in the  /data/backups directory. The current backup status of the site can be checked with the command wp-backup-status. From the WordPress Dashboard, backups can be viewed from Tools -> Backups.

Backups include all files under the  /data/wordpress directory and the database, so practically the entire WordPress site is backed up regularly. For example, the files under the /tmp directory are deleted at regular intervals for security reasons.

If you want a file or directory not to be backed up, you can add the path to that file or directory to the file  /data/backups/exclude.filelist which uses the rdiff-backup syntax, i.e. one path per line.

Backups of staging environments

NOTE! We take automatic backups on production sites, but there are no automatic backups of staging environments. If you have a staging environment, please make sure that you save the site's history in version control (e.g. Git) or take a manual backup (wp-backup) before making any bigger changes.

Making Backups on your own

You can take a backup of your site manually directly in the WordPress Dashboard from Tools -> Backups and "Create a backup". The backup can also be taken manually by running the wp-backup command on the server. You can also backup just the database with the wp db export command.

If necessary, you can also make a downloadable copy of your site for example with the All-in-One WP Migration plugin. See here for more detailed instructions.

We do not recommend installing your own backup plugins for your WordPress site, as backups are already automatically included in all our service plans. See here to find out which plugins we do not recommend using in our service. Site owners own backup solutions on the site needlessly consume the Plans available disk space while the backups made by Seravo are excluded from the disk space calculations. Furthermore the site owner is responsible of the management of their own backups as well as deleting them if a site user requests their data to be deleted according to the GDPR. Less plugins also means less chances to the site to break and a smaller attack-vector for malicious parties.

However if you want or have the need to, you can build a system that extracts the backups made by Seravo to your own server somewhere outside the websites server. This can be done for example by using SSH or SFTP connection.