Here's a strategy I use, although I wasn't thinking of ransomware at the time.
I have a script which first does a 'tarsnap --dry-run', and parses the summary
output from that. It checks the 'Total Size' and 'Compressed Size' of the new
data, and will skip making a real-backup if that size
On Wed, Jul 12, 2017 at 12:57:07PM -0700, Graham Percival wrote:
> This could be wrapped into the "Receiving emails from making backups" tip:
> http://www.tarsnap.com/tips.html#receive-mail
... and I just noticed some debug code in that script that I forgot to remove
before publishing it. Sorry!
On Wed, Jul 12, 2017 at 09:36:39AM -0400, Rob Hoelz wrote:
> I just started using tarsnap, and I was wondering if there exists an
> option (or the potential interest in developing an option) to put a cap
> on an archive size.
Not exactly what you're looking for, but it would be easy to add a
On 07/12/17 06:36, Rob Hoelz wrote:
> I just started using tarsnap, and I was wondering if there exists an
> option (or the potential interest in developing an option) to put a cap
> on an archive size. The reason I ask is on the off chance another
> tarsnap user or I gets bitten by ransomware
> I just started using tarsnap, and I was wondering if there exists an
> option (or the potential interest in developing an option) to put a cap
> on an archive size.
[ ... ]
> The closest thing I could find is the --maxbw option; is there a
> corresponding option for archive size that I'm not
Actually, re-reading your message, I now think I misunderstood, and you want to
limit the size of the individual virtual archive, rather than the literal size
of
data-transfered?
J.
Hello fellow tarsnap users!
I just started using tarsnap, and I was wondering if there exists an
option (or the potential interest in developing an option) to put a cap
on an archive size. The reason I ask is on the off chance another
tarsnap user or I gets bitten by ransomware and it encrypts
