[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: subversion repository backup

From: vinay i <vinay.indresh_at_gmail.com>
Date: Fri, 12 Dec 2008 16:50:03 +0530

Thanks Ryan.
>>>Where do you see that? AFAIK there is only "svnadmin hotcopy" which
(always) creates a complete copy of the repository.
Sorry. I meant to say svnadmin hotcopy and svnadmin dump incremental.

>>>I didn't understand your concern about a staging area for rsync.
probably rsync'ing to a staging area first to avoid problems with the link
between main server and backup dying during the rsync

-Vinay

On Fri, Dec 12, 2008 at 4:35 PM, Ryan Schmidt <
subversion-2008c_at_ryandesign.com> wrote:

> On Dec 12, 2008, at 04:46, vinay i wrote:
>
> I am using fsync to back my subversion repository. This is not the ideal
>> way to make a backup and I faced some issues probably because the files were
>> copied in the wrong order.
>>
>> Subversion book talks about "svnsync" and "svnadmin hotcopy" for
>> repository backup. I have a few queries regarding this:
>>
>> 1. svnsync: This only syncs the revisions. How do I sync all other
>> configuration files,hooks and files which reside inside the repository
>> directory?
>>
>
> You could use rsync or any other means to transfer those files.
>
> 2. svnsync: The advice is to maintain a "mirror copy" which has only read
>> permissions. But we have scenarios when we need to make commits on the back
>> up repository. (We used to do the same with CVS repository. When the primary
>> repository was restored we committed the changes again on the primary
>> repository). Hence, can I have a mirror copy which has write permissions.
>> Will there be any side effects?
>>
>
> The mirror must be read-only. However you can configure a write-through
> proxy so that write requests (e.g. commits) to the mirror's URL get
> transparently sent through to the master instead.
>
> 3. svnadmin hotcopy: There are two ways to do it (incremental and full
>> copy). I prefer to use full copy.
>>
>
> Where do you see that? AFAIK there is only "svnadmin hotcopy" which
> (always) creates a complete copy of the repository.
>
> We use the same path for the repository on the main and backup server.
>> a. Can I run a svnadmin copy directly to create a copy on the backup
>> server?
>> b. Should I do a hotcopy on the local server and then do a rsync to the
>> backup server. Will there be any issues when rsync happens (should I use a
>> staging area to rsync and then copy to the desired location)?
>>
>
> svnadmin hotcopy, like all other svnadmin commands, needs direct filesystem
> access to the repository. It cannot operate over the Subversion protocols
> like http:// or svn://. So that probably means (b). I didn't understand
> your concern about a staging area for rsync.
>
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=983350

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-12 12:20:57 CET

This is an archived mail posted to the Subversion Users mailing list.