Re: how does tigris do server updates?

On 7/20/07, Brian Krusic <brian@krusic.com> wrote:

> While u r correct about serving dbs regardless version as thats what
> we do on some of our repos now, there are benefits to upgrading so I
> disagree with you.
>
> A repo we had in 1.2.3 was 50GB at the time. We converted to 1.4 and
> it shrank to 38GB.
>
> So yes, we do need to convert.
>
> With offices in geographically diverse regions, the leaner and meaner
> our dbs are, the better.

You missed my point, as I did mention that in my message.

1. Not every release has made changes in the repository. For
example, 1.5 changes the repository but there is no need to dump/load,
the changes will happen automatically.

2. When there is something like a space reduction (which I cannot
imagine happening again), you still do not need to base your upgrade
decision on this issue. You could have upgraded the repository to 1.4
and then re-loaded the repository when you had an acceptable window of
downtime.

The bottom line is that tigris handles this issue by trying to avoid it.

Something else to keep in mind is that as of 1.4, we now have the
svnsync tool. This is great for doing a migration. You can create a
new fsfs repository using the new release, and then use svnsync to
migrate from the old live repository to this one. Once the sync is
finished, just want for your next downtime window, do one final sync,
then shutdown the server and move in the new repository and restart.
Or better, would be to just change the server to be serving from the
new location. If you use this approach just make sure the new
repository you create has the same UUID as the master.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org