[Box Backup-dev] Box Backup 0.20 redesign

[Chris Wilson]

Hi Gary,

On Sat, 13 Jan 2007, G. wrote:

>> * Commit snapshot T
>
> Would that mean that a partial backup could not be performed? Either the 
> entire (new) snapshot gets prepared by the client and uploaded to the 
> server, or nothing gets uploaded at all?
>
> I am asking since, in the future, I would like to see the bbackupd 
> ability to define multiple, independent backups sets, with, say, a small 
> file backup set performed frequently, but a large file backup set 
> performed rarely (tons of time and resources).

That is not ruled out. Whether or not the client writes all changed files 
into the snapshot is entirely up to it. It's free to leave some files for 
later, as it does now if the file has been modified too recently.

I have a related question - how about resuming interrupted backups? Is it 
possible or sensible for the client to pick up a snapshot in progress from 
where it left off, to avoid the need to re-upload any files which have not 
changed since that snapshot started?

rdiff-backup does not have that ability, and it really bugs me sometimes 
when a backup craps out at the last minute (e.g. permissions on some file 
in /var) and I have to run the whole 8-hour backup again (rdiff-backup is 
also very very slow).

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