André,
you can run as much SVN instances as you like on one single machine. You just need to set the port numbers to be different. If you don't like that, you could e. g. use the free "VMware Server" to run both machines on the same machine but in different server VMs: They have different IPs but default ports then.
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D
QUIPSY QUALITY GmbH
________________________________
Von: Fritsch, Andre (EXT) [mailto:andre.fritsch@siemens.com]
Gesendet: Mi 08.03.2006 09:41
An: Markus Karg
Betreff: AW: AW: Upgrade SVN from 1.0 to 1.3 need help!
Markus,
this seemes to be the only solution. But therefore a second server is needed, isn´t it? Or is can i run two svn instances on one server?
Best regards,
André
___________________________________________________
SIEMENS Siemens Business Services GmbH & Co OHG
Human Resources Management
Heinz-Nixdorf-Ring 1
D-33106 Paderborn
André Fritsch Telefon +49(5251)8 2 55 96
HR - Services Fax +49(5251)8 2 52 09
SBS D SOL HRM D N mailto:andre.fritsch@siemens.com <mailto:andre.fritsch@siemens.com>
PDB HN
___________________________________________________
________________________________
Von: Markus Karg [mailto:markus.karg@quipsy.de]
Gesendet: Mittwoch, 8. März 2006 09:22
An: Fritsch, Andre (EXT); Ryan Schmidt
Cc: users@subversion.tigris.org
Betreff: AW: AW: Upgrade SVN from 1.0 to 1.3 need help!
André,
we had similar problems when moving from VSS to SVN: A complete port needed several days. So we set up SVN step-by-step: We have written a batch that is pulling one project from VSS, pushing it into SVN. Every project leader was given access to that batch (plus a short documentation how to use it). Then they had full control when to move their project. This worked very well. Maybe this kind of organization is a solution for your project leaders, too.
Markus
________________________________
Von: Fritsch, Andre (EXT) [mailto:andre.fritsch@siemens.com]
Gesendet: Mi 08.03.2006 09:02
An: Ryan Schmidt
Cc: users@subversion.tigris.org
Betreff: AW: Upgrade SVN from 1.0 to 1.3 need help!
Thanks for your help!
The repositories i look after have a size of about 12 GB seperated in several projects. When i dump and report all projects it will take a lot of time. If i seperate do it per project i will have to run 2 svn instances seperatly, because the dump and import lasts longer than from 5pm to 8 am (the time our developers are at home). For this reason i hoped that there would be possibility to get the upgrad done quicker.
Gruß,
André
___________________________________________________
SIEMENS Siemens Business Services GmbH & Co OHG
Human Resources Management
Heinz-Nixdorf-Ring 1
D-33106 Paderborn
André Fritsch Telefon +49(5251)8 2 55 96
HR - Services Fax +49(5251)8 2 52 09
SBS D SOL HRM D N mailto:andre.fritsch@siemens.com
PDB HN
___________________________________________________
-----Ursprüngliche Nachricht-----
Von: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Gesendet: Dienstag, 7. März 2006 16:13
An: Fritsch, Andre (EXT)
Cc: users@subversion.tigris.org
Betreff: Re: Upgrade SVN from 1.0 to 1.3 need help!
On Mar 7, 2006, at 14:51, Fritsch, Andre (EXT) wrote:
> I am an admin to a running svn 1.0 installation on red hat enterprise
> linux. Now some developers aked me for an upgrade to svn 1.3.
> As i am no svn pro and have not found good upgrade instructions i
> wonder how i can do a save upgrade from 1.0 to 1.3?
1.0 is quite old, so you should do this upgrade carefully.
The best idea would be to "dump" your current repository to a textfile with "svnadmin dump" using your current v1.0 svnadmin program. Then "load" that with "svnadmin load" into a new repository created with svnadmin v1.3. See:
http://subversion.tigris.org/faq.html#dumpload
Note that since Subversion 1.1 you have the choice of two different repository backends: BerkeleyDB ("BDB"), which is what you're using now, and the newer "FSFS" storage mechanism which became the default as of Subversion 1.2. I generally recommend FSFS, as it's usually less problematic than BDB, except that there's a problem with FSFS and revisions larger than 2GB until the next version of APR comes out. So if you have such large commits, or expect to have them, you may want to stick with BDB.
http://subversion.tigris.org/issues/show_bug.cgi?id=2453
Received on Wed Mar 8 09:45:32 2006