Keep local backups

[TJM]

There should be an option to keep backups locally. Still send them to dumper.io of course, but basically just don't delete the local file until it has reached a certain age, or keep a certain number of backups. (I would offer both capabilities).

This would mean that Dumper would be able to provide local and offsite backups, without taxing the database twice.

[kenn]

Interesting idea, but that introduces new problems.

• Security. Dump files are only protected by file permission. Maybe dump encryption would mitigate the issue.
• Pruning. You say "Just don't delete the local file until it has reached a certain age" but for Dumper configuration has to be controlled over the web UI, and probably it's best to synchronize the behavior with the remote backups for the user's mental model / expectation, which means a new set of API. It's actually not easy to do that reliably.
• Reliable pruning is much more critical on local because there's this fatal "disk full" error, which doesn't exist on S3. Theoretically, if your database is 25% of the size of the disk, you can't keep 4 copies of them, and what should we do then? etc. There won't be an unobtrusive solution without asking the user for a decision. Probably leaving only the last backup locally (and delete everything else) would be a good start.

[TJM]

Good points... I was going to make that part of the configuration be in the initializer or whatever. Leaving the last backup local would allow someone to hook in after the backup runs (successfully) and "do something" with the file if they want to.