Open decibelhertz opened 11 years ago
Thanks for the feedback, I think it's a nice idea, I will try to implement this in the next version (planned soon), I keep you updated in this thread.
Don't hesitate if you have any other idea/feedback,
Thanks !
The rotating backup stuff is great, however Glacier can also be treated as a cost-effective upload-once-download-maybe safety backup for some data. E.G. raw data whose derived products are of actual interest, but need to be preserved for reference in case something in the derived product(s) needs to be reevaluated down the road.
So, while I can add this to my own scripts, and/or use the API, it might be nice to be able to delete the source data, directly in bakthat's command-line, once its successfully been copied to S3 or Glacier. E.G.
bakthat backup -d glacier --delete-source myfile
. Some sort of stern warning could accompanybakthat backup -h
.By similar logic, since the data saved on Glacier may need to be download, manipulated, then re-uploaded -- and having multiple copies may be expensive/confusing -- it may be useful to delete-upon-restore, too. E.G.
backthat restore -d glacier --delete-source myfile.20130401235446.tgz