duplicity-team team mailing list archive

[Peter Schuller <peter.schuller@xxxxxxxxxxxx>]

> This is the first message on the new list.  I've merged everything we
> had ready and it tests OK.  Not sure if you get a message when that
> happens, so heads up.  Let me know.

I've gotten mail-outs though I'm not sure how obvious it was what
actually got merged. I'll have to re-check, probably just me.

> I've run it and I don't think we introduced any errors.  Please check it
> out.  I'm still new to bzr used this way, so I may have screwed one of
> them up.

Will do.

> I'm still working on the collections problem, the bogus orphaned sig
> chains.  Looks like I'll have it soon.
> 
> On to another point, we could go back to having the archive dir
> optional, but I would still need persistence for the partial sig and
> manifest files.  What do you think?  Are we getting too much push back
> on this new "feature"?

Well, from a user-centric stand-point I think I would prefer to have
it be optional until the default behavior (with no directory
specified) is a bit friendlier. I'm not sure how clear it is to users
why things fail mysteriously because a backup failed, in their script
that does ten distinct backups that would now accidentally share an
archive dir. I'm not sure how much work it would be to make it
optional (I haven't reviewed the changes as a whole).

Once the --name stuff is done it feels safer to have it on by default
I think.

On that topic, while I didn't get around to it this weekend (due to
social events) I should get somewhere soon, if parsing out the backend
URL doesn't turn out to be too problematic (will see if I can avoid
adding an interface and implementing it for each backend).

Actually, thinking a bit more... The requirement of the
checkpoint/restart is that the source filesystem has not changed,
right? Are the results from the file system actually changing
different than what would happen if the original backup had simply
been, say, paused for an extended period of time?

The reason I ask is that I realized that most people, even though in
reality it's not such a great idea, do backups on live file systems,
particularly (for obvious reasons) on platforms where file system
snapshots are not trivially attainable. If the results of accidentally
doing a restart on a live file system are much worse than a regular
pause, it can be considered a bit dangerous to enable
checkpoint/restart at all except when explicitly enabled by the user.

--
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@xxxxxxxxxxxx>'
Key retrieval: Send an E-Mail to getpgpkey@xxxxxxxxx
E-Mail: peter.schuller@xxxxxxxxxxxx Web: http://www.scode.org

Attachment: pgpzhwv9WG4wy.pgp
Description: PGP signature