[Box Backup] FeatureRequest: Mass Deletion Protection

Chris Wilson boxbackup at fluffy.co.uk
Sat Aug 9 14:59:59 BST 2008


Hi Torsten,

On Fri, 8 Aug 2008, Torsten wrote:

> Changing delete time to "never delete" is not what i want. This would
> prevent bb to delete the directory on the store if it is not activated
> in bbackupd.conf anymore.
> 
> What i want is that: If the location is activated in bbackupd.conf and
> it is not accessible in local directory - then bb should not stop
> syncing and printing errors. It should print a warning to the logs and
> then start syncing the next location. It should not mark the directory
> as deleted. Do you think anybody else would need this? I hope you can
> understand my english ...

I think we are actually talking about the same thing. 
DeleteRedundantLocationsAfter already exists in trunk, and only applies to 
locations, and only if they are not found on the client's local disk. That 
sounds like the same case that you describe.

Changing the value of DeleteRedundantLocationsAfter should change the time 
until the location is deleted on the server, which I think is what you're 
trying to avoid happening. Setting it to some enormous value would 
probably already achieve what you want to do, without patching.

I'd hate to add another way to do exactly the same thing in a different 
place in the code. Could you try this setting in bbackupd without the 
patch, and see if it does what you want to do with this patch? if so, then 
the patch might not be necessary.

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | We are GNU : free your mind & your software |



More information about the Boxbackup mailing list