Thank you adrian for nice reply.
I will try svnsync first and let you know if i face any issue .
Regards
Irfan.
On Tue, Mar 3, 2009 at 8:12 PM, Adrian Marsh <Adrian.Marsh_at_ubiquisys.com>wrote:
> Hi Irf,
>
>
>
> This is simple to answer:
>
>
>
> File copy technique: Bad, bad, bad, because on a busy system, the
> repository may be updated/changes **whilst** the O/S is copying files.
> For a non-busy system, it **might** be ok. If its just you, on your own,
> no other users accessing it.
>
>
>
> Svn hotcopy: This is the technique to use for backing up the entire
> repository, each and everytime. Great for really small repositories. Try
> doing it for 20+gb ones once or more a day, and you’ll see it takes ages.
> Add in an additional backup system (eg tape), and you’ll see yourself
> backing up 20+gb of files on every tape backup (as every file will change
> during the copy)
>
>
>
> Svnsync: The way to go for large repos. The downside, only the
> repository data itself is backed up. Hooks, config files, auth files etc,
> aren’t included. Do these another way and you’re ok.
>
>
>
> Heres how I backup our svn server:
>
>
>
> Server1: a Windows PC, with Backupexec, is a backup for server2
>
> Server2: A linux machine, just doing svn
>
>
>
> - Once a week, I use mondoarchive to dump the entire server2 to a
> NAS as an .iso. But I understand this might not give the best SVN database
> copy. This is an emergency recover thing, not specific to svn.
>
> - Every 3 hours, a different server (server 1), uses svnsync to
> poll the master svn server (server 2), and copy any changes over. Only the
> changes transfer.
>
> - Once a night, server 1 has a Diff dump to tape. Once a week,
> server 1 has its entire Filesystem dumped to tape, along with the NAS .iso
> too. This is ok, as the svn filesystem on server 1 isnt in active use at
> this time.
>
> - Once a week, a copy of the tapes is made for offsite.
>
>
>
> Benefits for me: server 2 is a reasonably recent copy of the important
> bits of server 1. The update times between the two are minimal. The tape
> diff backups each night are minimal too. Any files I miss in the svnsync
> are included by the entire filesystem dumps.
>
>
>
> I already had the two servers and BackupExec, so cost was minimal for me. I
> also needed offsite backup in case of Fire.
>
>
>
> Adrian
>
>
> ------------------------------
>
> *From:* Irfan Sayed [mailto:irfu.sayed_at_gmail.com]
> *Sent:* 03 March 2009 12:30
> *To:* users_at_subversion.tigris.org
> *Subject:* Re: Subversion repository backup.
>
>
>
> I have gone through the entire description and found that svn provides
> "svnadmin hotcopy" tool to backup the svn data. But what i am doubting is
> that what this tool give more advantage over the normal file system's copy
> utility.
>
>
>
> Can somebody list out the advantages of using svn command to take the
> backup over normal file systems copy utility.
>
>
>
> Please help
>
>
>
> Regaeds
>
> Irf.
>
>
>
>
>
> On 3/2/09, *Irfan Sayed* <irfu.sayed_at_gmail.com> wrote:
>
> Thanks Andy.
>
>
>
> Regards
>
> Irfan.
>
>
>
>
>
> On 2/27/09, *Irfan Sayed* <irfu.sayed_at_gmail.com> wrote:
>
> Hi All,
>
>
>
> I need to take the backup of subversion repository.
>
> Can you please let me know what is the best way to achieve this.
>
>
>
> Regards
>
> Irfan
>
>
>
>
>
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1265005
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-04 08:17:53 CET