In Otto v3 it was possible to set how many offsite backups to keep. The script schedule kept a single daily backup.
In Otto v4 I can’t see how to set the number of backups to keep in the S3 bucket. If I wan’t to retain more than 1 remote backup, but only keep the last 1 locally on the server is that still possible?
Hi Gabe,
Yes it is possible. The big difference between Otto 3 and OttoFMS in this area is that OttoFMS uses the backup schedule itself for most of the configuration. OttoFMS respects the retention setting of the Backup schedule itself. You can set it to what ever you want there.
OttoFMS now only has to deal with moving files to an offsite location. It doesn’t have to deal with the backup configuration itself. It just watches for a backup schedule to complete and then pushes it offsite.
Make sense?
Todd
Thanks @toddgeist, that makes sense.
The use case for me is that because I keep a large number of daily backup on AWS without having to keep these files local on the server. Keeping 180 days of backups local on server would require a huge amount of local storage.
Storage in S3 is much cheeper than on server storage. Also local snapshots of the server would be much larger. I think being able to meep more versions ‘offsite’ from the server rather than ‘local’ is a very useful feature.
For me it would be great if you were able to reinstate this functionality.
Even if there was an option for Otto to just push new backups to S3 without removing them. Then I could then manage the retention within S3.
Sorry Gabe, not sure I was clear.
The functionality is there. It works just as you want and expect.
Just set the retention on the FileMaker server backup schedule itself. If you set it to keep 2, 2 backups will be kept locally. All of them will be kept in AWS, since OttoFMS doesn’t delete backups that have been sent.
Does that help?
Todd
Ahh, yeah. That makes sense, thank you.
