Tuesday, September 28, 2004, 6:50:39 AM, Juan Luis Serradilla Amarilla wrote:
> Lukas Ruf wrote:
>
>>>Kenji Chan <adslbqmr@tpg.com.au> [2004-09-28 09:12]:
>>>
>>>The safe and easy way that I would do is write a simple script that
>>>'zip' the whole repo into a zipped file like 20040929_repo.zip
>>>
>>>
>>>
>>
>>If you know for sure that there is no access while zipping you could.
>>Do not forget to stop your web-server (if running).
>>
>>I run
>> svnadmin dump <repos> | bzip2 -9 -> <repos>.`date +%Y%m%d-%H%M`.bz2
>>frequently.
>>
>>wbr,
>>Lukas
>>
>>
> Should I stop my web server before doing "svnadmin dump"???
No. You only need to stop your web server if you're going to run
'svnadmin recover' on your repository. What you do need to do is run
'svnadmin dump' as the same user as the web server.
> For my backups, now I run "hot-backup" (hot-backup.py), and it's great.
> I don't need to stop my web server, and I get a new clean repository,
> with the same content, ready to use. For example, backing up my svn
> repositories, from /SVN to /SVNbackups is very easy:
>
> #!/bin/bash
> for i in PERSONAL MNCS
> do
> hot-backup /SVN/${i} /SVNbackups
> done
>
> I get new clean repositories under /SVNbackups. They are identified by
> the repository name (root directory) and the version number:
>
> MNCS-61/
> PERSONAL-48/
I had about 20 repositories I helped maintain, and I also used the
hot-backup script. It works great.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 28 13:27:09 2004