It's always a good idea to dump the repository as an additional backup. When upgrading, mostly you can still access old repositories. SOMETIMES they will be silently upgraded in someways - this will not matter if you never access the repo with file:// (or using any older clients/servers). Sometimes there is an svnserve upgrade command. In general, you'll probably get the best performance by reloading from a dump.
You should read the release notes for details. Note: the the dump format does NOT save the options set in the 'conf' directory (if using svnserve). Nor will it save any apache specific configurations. As an extra backup, I usually zip (or tar bzip2) the svn repository directories. On Wed, Mar 30, 2011 at 06:36, KM <info...@yahoo.com> wrote: > I have svn 1.4.3 running on a solaris 8 server. I want to either upgrade > this particular server to solaris 10, or move the entire thing to a new > solaris 10 server, and also to upgrade subversion to the latest stable > version (along with all of the dependencies of course... apache etc.) > > If I decide to use the same server I am now - what's the best thing to do > ... upgrade the OS and then all of the packages and dump and load the > repository? > > If I am moving - I assume I would set up the OS and packages on the new > server including the new svn - then can I dump the repository and then load > it on the new server - or just move the repository over and do the same? > > Unfortunately I upgraded to 1.4.3 a while back and haven't worked on this > in quite some time. I apologize for stupid questions. I want this as easy > as possible. > > Also has anyone ever used the webstack/glassfish SW and set it up for svn. > Since I also use Mantis - the php would also be taken care of at the same > time this way.... just curious. > > Thanks in advance for any advice. > KM >
