Restore the option to backup databases to S3
We used to be able to use unmanaged backups to backup our databases to S3. That option is now gone and all our unmanaged backups get backed up to /var/cloud66/backups on the local server where the database resides. That's like backing up my computer and then putting that backed up data on the same computer that I was trying to back up.... hm... what?
It seems like you are giving us two choices: managed and unmanaged, but in reality there's only one choice because the other one doesn't even make sense. I strongly urge you guys to bring the old behaviour back.
-
Roman Wollenburg commented
We recently composed a small docker container which uses Percona's great xtrabackup tool to do live-backups of our MySQL-databases (dockerized or standalone): It performs the backup, compresses it (with gzip, bzip2 or xc), encrypts it with pgp and uploads it to S3, rsyncs it to some other host or moves the file to another location (glusterfs-mount for example). After that, it exits. Feel free to give it a try if you want: https://gitlab.com/bichinger/docker-percona-xtrabackup, we're also open to suggestions. Also, you can use server tasks to move the backup files to a glusterfs mount if you install an additional GlusterFS host.
But after all, using the managed backup service gives you the best security with the least hassle and you don't have to setup/maintain/pay for additional server or S3 fees.