[Box Backup] lazy and snapshot together, file formats and files changing often

[Sean Van Couwenberghe]

Chris, thank you for asking our opinions.

I wold say that a "snapshot" is typically understood to be a full, current 
image of the backup schema. In that case, I would think that a "snapshot" 
would be a full backup of all files at the time of the bakcup, and a "lazy 
mode" backup would be using the current setup of only backup up changes as 
noted in the original e-mail below. It would be nice to have a system set 
to "lazy mode" and be able to run a manual, or schedule for periodic 
occurrance, full "snapshot" backup.

While I'll find this software useful, what I'll be waiting for is having the 
ability to make backups where I or the end user could choose to backup a 
different snapshot, if available, to help protect against corrupted data in 
the latest lazy mode backup.

I'm thinking that this could either be done through a full snapshot as noted 
above, or having the system be able to differentiate between different lazy 
mode backups, basically picking which "change" level to restore from. I hope 
that makes sense, and I do understand that having either of these options 
enabled would take more storage space.

Just my vote/opinion.
-- 
Sean Van Couwenberghe
Vanco Computing
(707) 578-5802
(888) 908-2626
www.vancocomputing.net


On Friday 20 June 2008 10:33, Chris Wilson wrote:
> Hi all,
>
> On Fri, 16 May 2008, Louis-Dominique Dubeau wrote:
> > On Fri, 2008-05-16 at 23:17 +0100, Chris Wilson wrote:
> > > Snapshot mode does not force all files to be backed up. The same rules
> > > about MinimumFileAge, MaxUploadWait, etc. are still observed. You could
> > > argue that this is a bug.
> >
> > I would say it is strange.  I would definitely expect bbackupctl sync to
> > force a all files to be backed up.
>
> (Louis, sorry for the delay in replying to this)
>
> What do other users think? Straw poll, should "bbackupctl sync" or
> "force-sync" force all files to be backed up, ignoring the MinimumFileAge
> and MaxUploadWait, or should it continue to behave as at present,
> honouring those limits?
>
> In the latter case, who wants a new bbackupctl command to override that
> behaviour?
>
> Cheers, Chris.