On Thu, Jul 23, 2009 at 16:01, Neil Aggarwal<neil_at_jammconsulting.com> wrote:
> Ben:
>
>> If rsync happens to run while the repo is being comitted to, it might
>> grab in inconsistent state. hotcopy is smart enough about the
>> internals of svn to avoid this.
>
> I assume hotcopy makes a full backup of the repo, not
> incremental. Is that correct?
It looks that way. The documentation I found in svn book isn't exactly
very detailed. I also poked briefly at hot-backup.py [1] but it
doesn't look incremental either.
If I were in your position, I think I'd do something like this:
(1) I'd keep a read-only mirror (ideally off-site) using svnsync as my
backup of the repository contents.
(2) I'd use a conventional approach (rsync or tar+gz+netcat) to backup
hook scripts and configuration daily.
(3) I'd post this scheme to the mailing list hoping that someone would
smack me if this were a bad plan.
> Using hotcopy seems it would take a lot of bandwidth
> to transfer the data to a remote server if the repo
> is sizable.
>
> Thanks,
> Neil
>
> --
> Neil Aggarwal, (281)846-8957, www.JAMMConsulting.com
> Will your e-commerce site go offline if you have
> a DB server failure, fiber cut, flood, fire, or other disaster?
> If so, ask about our geographically redundant database system.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2374830
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2374849
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-23 17:04:06 CEST