No -- the backup tools just get the highest current version number,
and back up to that. Then when they're done, they see if any higher
versions have appeared, and back them up too, and so on, until either
there is no new version, or the tool decides to quit anyway.
Locking is the fs's job, there's no doubt about that. The fs read
functionality Does The Right Thing.
"Jonathan S. Shapiro" <email@example.com> writes:
> What you say is true. The problem is that it requires the backup tools to
> collaborate with the locking discipline, and they do not know anything about
> it. I think this is a problem that may want some thought.
> > Why don't you want people to check in changes while you back things up?
> > If you're worried about the repository being in an inconsistent state,
> > don't be. Berkeley DB provides easy ways to make this work.
Received on Sat Oct 21 14:36:12 2006