A few days ago we added a new feature that allows you to select where backups are stored. The new site setting is called
backup_location and currently supports “Local” and “Amazon S3”.
The setting defaults to “Local” unless you previously set
enable_s3_backups to automatically upload backups to S3.
What has changed?
Up until now backups were always stored on the server’s local disk – uploading backups to S3 was just an additional, optional step at the end of the backup process. With the new setting you can choose to store backups either locally or on S3. Local storage will be used only for temporary files during backups and restores if you select S3.
Also, the Backups tab now works the same for every backup location.
There’s no need to login into Amazon S3 anymore in order to upload, download or delete a backup. You can even restore a backup directly from S3.
The good news is that it should be a lot easier to add new backup locations from within a plugin than it was before. Do you want to give it a try?
In the meantime you can take a look at How to sync your backups to cloud storage (alternative method).
Is there a Howto topic?
Yes, there is. Configure automatic backups for Discourse