[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Directory changes when mid-backup?
From: |
Phil |
Subject: |
Re: [Duplicity-talk] Directory changes when mid-backup? |
Date: |
Wed, 04 Nov 2020 11:52:11 +0000 |
User-agent: |
mu4e 1.2.0; emacs 26.3 |
Thanks Oliver - this largely answers my question.
For deletes (where read locking isn't a thing) - will duplicity just
ignore any files that are deleted in-between file directory structure
retrieval and access time for actual archiving (rather than error because an
expected file is now missing)?
(I'm assuming that the directory structure is snapshot up-front before any
archiving starts, otherwise I imagine constant re-interrogating of the
filesystem would lead to a whole host of race conditions in very
actively written-to directories - eg if a new large-enough file was written
every n seconds the backup
might never end!)
Oliver Dunk writes:
> Hi Phil,
>
> I asked a similar question a few months ago which might interest you:
> https://lists.nongnu.org/archive/html/duplicity-talk/2020-06/msg00003.html
>
> On 3 Nov 2020, at 11:18, Phil via Duplicity-talk <duplicity-talk@nongnu.org>
> wrote:
>
> Hi,
>
> I've been using duplicity for a while to backup daily changing
> directories of logs and results.
>
> I have always done this in the dead of night and locked the processes
> which would usually write to the parent directory being backed up for the
> duration of the backup.
>
> However there is now a requirement to add to (and potentially even
> modify) this directory 24/7. I've done a few tests and running
> duplicity on a directory whilst that directory is being written to
> doesn't seem to fail.
>
> My question is - is backing up a potentially change directory supported?
>
> Does duplicity initially snapshot the directory structure - so it will
> ignore any new files or directories created whilst it is running? How
> does it handle files potentially being changed or deleted during the
> backup - if at all?
>
> It strikes me that adding files shouldn't really be a problem (they will
> simply be ignored until the next incremental backup) - but deleting or
> modifying files mid-backup may be difficult to handle.
>
> Any advice welcome!
>
> Thanks,
> Phil.
>
> _______________________________________________
> Duplicity-talk mailing list
> Duplicity-talk@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk