steve mookie kongSo a couple of things.
@[email protected] just brought up a new instance because the hosting provider he is using had some issues with the hypervisor that his instance was running on. Also I think I may have taken down his new #gotosocial instance with a boost of his message. I'm sorry buddy 😥
I have been running #snac over the last month and a bit (and it also powered a few of my previous instances). The nice thing about snac is that it doesn't use a database of any kind. Everything is stored as files on the filesystem and there's heavy use of hard links to make things work. The benefits of this? No risk of database corruption. And, here's the big one, backups are done by creating a tarball of the instance's running directory. No fuss, no muss.
I agree that monthly backups aren't good enough, I do a hybrid four hour + weekly backup. I do it using mod + date. Here's a sample. I run the script every four hours and it creates a tarball based on a mod of the week number -- I have it set at four to keep a total of four weeks and then rotate. This tarball gets backed up off the VPS every four hours.
The VPS hosting provider that I use also offers seven image backup slots to be used daily, weekly or monthly. I have it set for weekly.
Oh, and lastly, while I am not running a backup instance (too much work), this account is my secondary account if anything were to happen to my instance: @[email protected]
#fediverse #snacadmin #sysadmin
@[email protected] just brought up a new instance because the hosting provider he is using had some issues with the hypervisor that his instance was running on. Also I think I may have taken down his new #gotosocial instance with a boost of his message. I'm sorry buddy 😥
I have been running #snac over the last month and a bit (and it also powered a few of my previous instances). The nice thing about snac is that it doesn't use a database of any kind. Everything is stored as files on the filesystem and there's heavy use of hard links to make things work. The benefits of this? No risk of database corruption. And, here's the big one, backups are done by creating a tarball of the instance's running directory. No fuss, no muss.
I agree that monthly backups aren't good enough, I do a hybrid four hour + weekly backup. I do it using mod + date. Here's a sample. I run the script every four hours and it creates a tarball based on a mod of the week number -- I have it set at four to keep a total of four weeks and then rotate. This tarball gets backed up off the VPS every four hours.
The VPS hosting provider that I use also offers seven image backup slots to be used daily, weekly or monthly. I have it set for weekly.
Oh, and lastly, while I am not running a backup instance (too much work), this account is my secondary account if anything were to happen to my instance: @[email protected]
#fediverse #snacadmin #sysadmin
amilatled
