Hello,

We are currently running VSS 6.0a on an old piece of hardware running WinNT. That server is going away. We have a newer server running Win2003 Std. that will host VSS moving forward. I need to migrate our existing VSS over to it.

I am by no means a VSS expert - mostly just a user, but now with Admin rights (this got dumped on me). Also, our office is closing next year, so I really don't see the need to upgrade to the newest version of VSS and deal with users not understanding this or that on the interface, or getting upset about the GUI changes. We'd really just rather move the data off of NT and onto Win2003, and let the company decide later if they want to upgrade VSS versions or move to different source control software.

Also, we have about 5 different "databases" in use on our VSS - one for Engineering, one for TechComm, one for QA, etc. Each has their own .ini file and stuff in a subfolder under that.

That said, I have a few questions about this:

1) I assume VSS 6.0d runs on Win2003 just fine. Is this so, or am I just stupid for not upgrading VSS versions? Unless it's a big "must upgrade", I'm inclined to stick with 6.0 for the reasons above.

2) Exactly how do I do the migration? Install VSS 6.0d in some fashion on the Win2003 server....? Then what? Copy files?

All your help is greatly appreciated, as I am somewhat dreading this migration.

Thanks!
Eric

I just went through this myself, Eric, and someone replied to my post about it. The migration was a success. All you have to do is copy the entire VSS folder from one server to the other one - meaning, copy ALL files and folders in the VSS directory to the new location. Then, you just have the clients point to the new VSS location.

I upgraded from 6.0 to 2005, and it worked just fine. It's a logical assumption, I think, that it'd be more than fine for a 6.0 to 6.0 migration too.

Good luck.

Skugga

I just went through this myself, Eric, and someone replied to my post about it. The migration was a success. All you have to do is copy the entire VSS folder from one server to the other one - meaning, copy ALL files and folders in the VSS directory to the new location. Then, you just have the clients point to the new VSS location.

I upgraded from 6.0 to 2005, and it worked just fine. It's a logical assumption, I think, that it'd be more than fine for a 6.0 to 6.0 migration too.

Good luck.

Skugga

Oops, I just posted after you. :)

I was checking out your thread, and hoped it would be as easy for VSS 6. That's good to know - I will try and give that a shot and just see what happens. So if I understand correctly, you just copy that whole VSS folder over. Maybe install VSS client on that server as well (for Admin purposes). Then the end-users just need to point their already existing clients to the new databases, eh?

Cool deal.

Ok, good to know. I'll give it a shot soon and hope things work ok. Thanks!

My posts in here are going in an odd order - hmm, probably because I keep replying to myself. :)

Ok, I've moved files and hooked up to the new location of the VSS DB from my client successfully, so all appears to be going well, thanks!

Follow up question though - how the heck to I install the Admin piece on the server itself? I installed the client using a Netsetup.exe located in the VSS folder on the old server. No clue about the Admin piece - it was done so long ago here, no one ever documented it. *sigh* Hmm....

Turns out, I just had to install a different (Enterprise) version of Visual Studio, only picking VSS stuff, and I got my Admin tool. All is well.

That migration wasn't so bad after all.

I am in the process of moving VSS from one server to the next and Iam a little confused, so I have a couple of questions.

1. Do I need to install VSS on the new server?

2. How do I tell Visual Studio to use the new location instead of the old one?

Step by step instructions would be most helpful.

I have been fighting with this and I can't find too much documentation on it.

Please help!

Thanks in advance,

Jason

1. Technically, no. The reason you want to is so you don't have to run admin tools like Analyze over the network.
2. I would just re-run Open From Source Control.
   

This may seem odd but can you Post the entire instructions for me please? I did as above and I screwed up somewhere. Here's what I did

1. Installed VSS 6.0d on the new server at D:\Apps\VSSDB

2. Copied the VSSDB from old server to the new server.

Do I need to mess with any .ini files or anything?

When I tried the Open From Source Control, the project configuration wasn't the same as the old, meaning some forms were excluded from the Project and I had to re-include them.

Thanks again in advance,

Jason