Unplanned Transfer to New Server (v 3.1.7)

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
baronej
Posts: 9
Joined: Thu Oct 07, 2004 9:51 am
Location: Alexandria, VA

Unplanned Transfer to New Server (v 3.1.7)

Post by baronej » Sun Feb 19, 2006 10:50 am

I am using Vault as a single user.

The PC that I the Vault service/repository ("Machine A") broke unexpectedly, and I need to get set up on another machine ("Machine B"). To complicate things:

1. I've been using Machine B to check out stuff from the repository via the VS 2005 IDE.

2. The state of the project is (1) some items are checked out from the repository and (2) some items have been checked out "disconnected" via the IDE since Machine A broke (I was hoping that Machine A would be fixed quickly, but it won't be...).

3. The backup I have is from a point in time before Machine A broke, so I don't the various checkouts, in the project.

What I would like to do:
1. Set up the existing db backup I have on Machine B, install the Vault service on it, and to use it as the temporary repository.

2. Get the changes I've made to my project (Machine B) reflected in the repository. I understand that I can't recover check-in/check-out history, etc. All I want to do is to get the change in state of my VB 2005 solution as it now exists on Machine B into the repository as a single transaction.

What I'm thinking might work is:
1. Restore the db backup I have
2. Somethow get newly installed Vault service set up to work with it. I'm not quite sure how that works. My understanding is that when I run the service install, I'm allowed to point to an existing sgvault db, instead of creating a new one. Is that the case??
3. Get a list of the changes I've made since the backup (I've done this)
4. Make a copy of the solution (so that I have all the new info)
5. Remove the original solution
6. Do a get solution from source control (via the IDE), and allow Vault to recreate it as of the last backup.
7. Check out the various files affected, and redo changes (i.e., coping contents from the copy created in step #4 above).
8. Once I'm done, check everything back in.

Is this a workable plan, or is there an easier way?

TIA,
John Barone[/list][/list]

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Sun Feb 19, 2006 5:55 pm

To get Vault to work with your database, restore the database first to your new SQL Server location. Then run the Vault installer, which will detect the database and upgrade it and recreate the database user, etc. If Vault is already installed, then uninstall it before you restore the backup of your database.

Then proceed with the rest of your steps.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply