> I haven't received any feedback on this. If anybody can offer advice then I
> would really appreciate it as this is something that I wished to carry out
> tomorrow.
If you're running svnserve via a service, stop the service before running
the upgrade, likewise, if you're running it from the command line,
make sure it's closed so folks don't try and commit/update half-way
through your upgrade. Likewise for the apache service if you're using
the apache mod.
Sometimes I run into issues with file in use warnings during upgrades,
which (I think) is because the libraries in Subversion get used by
other applications (e.g. TortoiseSVN), which (I guess) is because the
Subversion environment path is chosen first (higher on the list?),
or the library is already loaded into memory, or something like that,
I've never been able to nail it down. Regardless, closing all other
applications down seems to solve the problem, and it happens on
my dev box testing new version of svn far more often than on our
Subversion server.
My normal approach is:
- Make sure last nights full dump and verify are ok
- Stop cruise control.net service
- Stop svnserve service
- Do a dump if required (or i'm feeling paranoid:)
- Upgrade
- Do a load if required
- Verify repositories
- Start svnserve service
- Start cruise control.net service
Obviously, replace cruise control.net service with any other dependencies
you have on Subversion.
As Ryan said, no dump/load cycle is required, so it's pretty painless.
hope that helps,
si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 29 06:42:52 2007