Olivier Fourdan wrote:
> Hello,
>
> I'm currently evaluating Subvsersion and I have a couple of questions
> that I could not find an answer myself:
>
> 1) Does migrating the repository data from an architecture to another
> one requires any special procedure ? For example, what if someone
> hosts his repository on a Win32 (or MacOS X) system and later wants to
> migrate to a Linux or UNIX server for hosting his data under subversion.
berkeley db databases are not portable between architectures, so you
would need to either manually db_dump and db_restore, or do an 'svnadmin
dump' and 'svnadmin load' to migrate.
> 2) Does upgrading Subversion requires (or will require in a near
> future) any special procedure for the existing repositories ?
> Basically, if someone uses Subversion right now, does a migration is
> to be planned when Subversion 1.0 comes out, for example ?
in the event of a non-backwards compatable change in the berkeley db
database schema, you can do an svnadmin dump and load to upgrade. this
will likely happen at least once more before 1.0.
> 3) Backuping the server data (Berkely DB) requires a shutdown of the
> database or the backup can be performed with Subversion being running
> and accessed ?
you can do a hot backup, see hot-backup.py in the subversion tarball.
> 4) How does Subversion scale ? Can it support (or will it support)
> huge trees ?
some people are using it with quite large trees, but there are certainly
still issues to resolve. it depends what you're doing with it. if you
try it with a very large tree and run into issues, we'd love to hear
about them.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 21 18:53:34 2003