How to move a Repository and its associated folder to a new server

[Big George <jb...@gmail.com>]

Hello,
I have two PCs:
- PC1, IP: 192.168.8.16, Windows XP
- PC2, IP: 192.168.8.40, Windows Server 2003

In PC1 I have installed:

- Subversion for Win32, version 1.6.0.

- TortoiseSVN 1.6.16 for Win32

- Folder with scripts to control versions:
D:\Scripts_DB
(This folder contains many sub-folders and text files. Those text
files are successfully controlled by Subversion. If I modify some text
file, immediately I update and commit with Tortoise)

- URL of Repository that contains D:\Scripts_DB:
svn://192.168.8.16/logs_scripts_bd/Scripts_DB

- Repository is in:
C:\Subversion\svn_Repos

In PC2 I have installed:
- VisualSVN Server 2.1.11 for Win32
- TortoiseSVN 1.6.16 for Win32
- I imported successfully Repository from PC1 to PC2
- I copied folder from \\PC1\D:\Scripts_DB to \\PC2\D:\other_path
\Scripts_DB

What I try to do is to move my Repository and folder D:\Scripts_DB
(with all its changes ) from PC1 to PC2.

Now in PC2, I have:
- Repository is in: C:\Repositories\Scripts_DB
- In VisualSVN I can see Repository: Scripts_DB
- I got folder: D:\other_path\Scripts_DB with all files and sub-folder
included

Question:
How do I configure Repository in PC2, so I can see all record changes
of my text files stored in D:\other_path\Scripts_DB, such as I do it
in PC1.

Re: How to move a Repository and its associated folder to a new server

[Daniel Shahaf <d....@daniel.shahaf.name>]

Ulrich Eckhardt wrote on Fri, Oct 28, 2011 at 08:42:30 +0200:
> Am 27.10.2011 23:56, schrieb Big George:
> >What I try to do is to move my Repository and folder D:\Scripts_DB
> >(with all its changes ) from PC1 to PC2.
> 
> There are two things involved for moving the repo:
> 1. Moving the repo itself
> A simple file-system copy would do the job.

This method may not work in the general case.  (Specifically, the
on-disk format of BDB databases depends on the architecture.)

Re: How to move a Repository and its associated folder to a new server

[Ulrich Eckhardt <ul...@dominolaser.com>]

Am 27.10.2011 23:56, schrieb Big George:
> In PC1 I have installed:
> - Subversion for Win32, version 1.6.0.
> - TortoiseSVN 1.6.16 for Win32

Consider upgrading the Subversion installation to the latest 1.6, 
several bugfixes have been made there.


> What I try to do is to move my Repository and folder D:\Scripts_DB
> (with all its changes ) from PC1 to PC2.

There are two things involved for moving the repo:
1. Moving the repo itself
A simple file-system copy would do the job.
2. Tell your working copy
Your working copies know which repository (URL) they were checked out 
from. You need to "relocate" these to point at the new repository 
position ("svn switch --relocate ..").

The working copies themselves can be moved or copied as you like, no 
special precaution necessary, provided you stay on the same operating 
system family.

BTW: Do you have a backup strategy? Seriously, consider the case that 
PC1 was gone due to hardware failure. How do you recover from this case? 
The point is that moving the repository allows some shortcuts to make it 
quicker, but a backup allows you to restore it and the rest of your 
infrastructure from scratch.

Good luck!

Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************