Re: [Duplicity-talk] Can one safely run multiple instances to the same target?

[enderst]

sometimes i have remote clients that will dump a lot of data to backup and will sometimes not finish the backup until after the next daily cron job starts and then i'll have another instance working the same directories/target. so being able to keep that from happening would be a great benefit.

On Fri, Mar 14, 2008 at 12:05 PM, Peter Schuller <address@hidden> wrote:

> No code is in duplicity to lock the target directory, but I am still
> somewhat surprised that it crashed.  Two running at the same time to
> different directories works OK.  I use that every day.

Hmm, my interpretation of the OP was two instances of duplicity with
the exact same target, which would definitely not be supported.

One fundamental problem is that it is not necessarily even possible to
do proper locking on all backends. But that said, duplicity could
perhaps provide a convenient method of local locking (something like
--backup-lock=/path/to/lock).

I have been using 'mkdir' locks in my scripts so far.

--
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <address@hidden>'
Key retrieval: Send an E-Mail to address@hidden
E-Mail: address@hidden Web: http://www.scode.org


_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk