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

subversion repository backup

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

Hello All,

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?
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?
3. svnadmin hotcopy: There are two ways to do it (incremental and full
copy). I prefer to use full copy.
    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)?

Any insight into this would be really helpful!!

Thanks
Vinay

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

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

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.