> My management is cautious about backups (having been burned by
> database corruption in the past). So I need to be able to do at least
> some of my backups simply by turning Subversion off (no writes to the
> repository internals), then copy the repository data, then turn it
> back on. We'll also use svnadmin hotcopy, but not exclusively.
>
> Somewhere I got the impression that checkouts and updates create
> temporary transactions as the mechanism for getting a consistent
> view. Am I confused?
>
> To put it differently, what do I need to do to ensure that NO writes
> will take place in the repository?
>
> 1. Set the access controls to forbid writes? (Svnserve, V1.2.3)
> 2. Set the access controls to forbid all access?
> 3. Stop the server entirely? (A bit messy -- it's set up to use
> xinetd right now...)
> 4. Something else?
>
> Also... does svnserve write any temporary files for caching or the
> like? If yes, how do I get it to stop doing that?
>
> Thanks,
> paul
>
>
This is what we do for backup ...
a) overnight filesystem backup ... with FSFS type repos, however, it is
error prone if there is somehow any inconsistency with in the repos itself.
b) overnight "svnadmin dump" for each repository. this also provides us a
simple check that repos is healthy if we can dump all revisions.
c) weekly restore "svnadmin load" for all repos onto a test server for last
known backup ... to confirm that backup & restore both processes conform to
our BCP requirement.
during a & b above, SVN server (using apache & mod_dav_svn) is still
operational (albeit tad slower!). If yours are BDB backend repos then (a)
may not be a reliable option, but (b) should work irrespective if repos are
live or offline.
YMMV, regards
Shirish
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 6 23:30:56 2006