On Wed, Jan 18, 2006 at 02:19:08PM -0500, Paul Koning wrote:
> >>>>> "Jacob" == Jacob Atzen <jacob@aub.dk> writes:
> Jacob> Your wish has been granted:
>
> Jacob> <http://svn.collab.net/repos/svn/trunk/notes/fsfs>
>
> Thanks, that's helpful. It doesn't answer the specific question I
> mentioned, though it answers several others.
>
> Summarizing what I learned:
>
> 1. If an FSFS repository is logically read-only, it is also read-only
> at the file system level.
>
> 2. "svnadmin hotcopy" does "the right thing" for FSFS.
>
> 3. If I use simple file system copy, and changes are being made, then
> that will NOT do the right thing, for two reasons.
>
> a. Any pending transactions will have their transaction files
> copied and those will not be cleaned up.
>
> b. If a commit is happening during the copy, I can end up with
> a missing file problem ("current" points to data that isn't
> in the copy). That is described as "easily repaired" but
> no procedure is given for repairing it, and "svnadmin recover"
> in particular doesn't do that.
The final paragraph of the forementioned text describes what exactly is
needed to perform a coldbackup:
So, if you are using standard backup tools to make backups of a
FSFS repository, configure the software to copy the "current"
file before the numbered revision files, if possible, and
configure it not to copy the "transactions" directory.
An example of how to do this with rsync is available at:
<http://snarfed.org/space/backup+subversion+fsfs+with+rsync>
I hope this answers your question.
--
Cheers,
- Jacob Atzen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 19 02:51:33 2006