June 1st, 2020 at 9:14 PM
I'm gonna guess you're using DigitalOcean or similar? If so, we just moved to DO, been happy so far, though we've had a few hiccups. Otherwise we've been happy.
We're looking into a solution for the exact same thing as a matter of fact. I generally do file backups manually once every month or so (we're a forum, the only thing that really changes regularly on the files is the avatars and attachments.
) The database is something I back up about every two days or so, and we've had to do it manually. I've got about 100 of them sitting on my computer right now, and they add up quick.
I will say that, although host-made backups are great, they can screw you over if your host goes under or your account gets suspended. I've heard of this happening all too many times. Perhaps host-made backups are good for daily backups, but at least every couple weeks an offsite backup should be made in the event that a worst-case scenario happens. Having your backups and your data on the same host or company can be a disaster if they decide to suspend you because of a phony abuse report from some bad actors, or if an act of God takes down the datacenter.
So yea, we're pretty much looking into solving the exact same problem. In the past, I used shell scripts to do this sort of thing for a fairly large corporate company that was running on AWS. We had about 12 EC2 and RDS instances combined, and it worked very well on keeping everything in sync. We actually were using shell scripts for files only, but I don't see any reason that something of this sort couldn't be done for databases too. Cron can run them automatically and use SSH/SCP to automatically move them to offsite locations.
I'll be sure to share whatever I come up with. By then you might have a solution that works even better.
We're looking into a solution for the exact same thing as a matter of fact. I generally do file backups manually once every month or so (we're a forum, the only thing that really changes regularly on the files is the avatars and attachments.
) The database is something I back up about every two days or so, and we've had to do it manually. I've got about 100 of them sitting on my computer right now, and they add up quick. I will say that, although host-made backups are great, they can screw you over if your host goes under or your account gets suspended. I've heard of this happening all too many times. Perhaps host-made backups are good for daily backups, but at least every couple weeks an offsite backup should be made in the event that a worst-case scenario happens. Having your backups and your data on the same host or company can be a disaster if they decide to suspend you because of a phony abuse report from some bad actors, or if an act of God takes down the datacenter.
So yea, we're pretty much looking into solving the exact same problem. In the past, I used shell scripts to do this sort of thing for a fairly large corporate company that was running on AWS. We had about 12 EC2 and RDS instances combined, and it worked very well on keeping everything in sync. We actually were using shell scripts for files only, but I don't see any reason that something of this sort couldn't be done for databases too. Cron can run them automatically and use SSH/SCP to automatically move them to offsite locations.
I'll be sure to share whatever I come up with. By then you might have a solution that works even better.
