Thanks guys, i'm new to upgrade using your way. which is safer using
svnadmin dump/load or svnadmin upgrade/verify or svnadmin hotcopy
given my situation where users can afford downtime.
Please check if my process is correct:
- remove svn 1.3 and all its dependencies.
- install svn 1.6
- backup my repository
- svnadmin upgrade /path/to/repository
- svnadmin verify /path/to/repository
After the steps above, is my repository now usable for 1.6? any other
steps so i could tweak my repository for best performance?
or without going svnadmin upgrade and verify, i just run svnadmin
hotcopy /path/to/old_repo_svn_1.3 /path/to/new_repo gives me an error.
how can i handle this safely.
svn01:/srv/svn # svnadmin hotcopy /srv/svn/test_repos /srv/svn/new_repos
svnadmin: Can't open file '/srv/svn/test_repos/db/fsfs.conf': No such
file or directory
Thanks guys for your help.
West
On Sun, Jul 4, 2010 at 2:11 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Ryan Schmidt wrote on Sat, 3 Jul 2010 at 20:26 -0000:
>> > what difference and advantage bet. linear and sharded?
>>
>> It's explained here, a bit:
>>
>> http://svnbook.red-bean.com/en/1.5/svn.reposadmin.maint.html#svn.reposadmin.maint.tk.fsfsreshard
>>
>> (You don't need the fsfs-reshard script mentioned there; that was just the only place I found a description of a sharded repository in my quick search.)
>>
>>
>
> The canonical definition is in the "Filesystem format options" section
> of <http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure>.
>
> Daniel
> (don't edit the 'format' file by hand, though)
>
Received on 2010-07-04 17:12:56 CEST