http://support.microsoft.com/kb/176909/   

Guys I understand VSS as well as I undersand ancient Greek, In both
cases I've never used it, never had need to use it, the only
difference is I know have been thrown into the deep end and asked to
migrate it to a new server as the current server is near over flowing
point.
 I don't understand the instructions in this article at all what do
you suggest?

date: Fri, 17 Aug 2007 07:54:17 -0700   author:   unknown

Re: http://support.microsoft.com/kb/176909/   

VSS is basically a big file system that's accessible over the network
by sharing the root directory (e.g. c:\vss) using network shares.
Under the root directory, you'll find 2 directories and 2 files that
make up VSS. These are:

data
users
srcsafe.ini
users.txt

To move the database, perform the following steps:

1. Copy these items to a directory on your new server (e.g. d:
\newvss), preserving the subdirectory structures within the data & sub-
directories. I'd suggest using a command line tool like 'robocopy'
from the Win2K/2K3/XP resource kit to do it - robocopy is a more
efficient/flexible tool than the standard Windows xcopy command. Make
sure users who'll be accessing VSS have Full Control permissions at
the NTFS file level.

2. Network share the directory you've copied them to  (d:\newvss).
Make sure that the users who'll be accessing VSS have 'Full Control'
permissions at the network share level.

3. In the VSS admin tool, verify that any settings such as VSS Logging
files are set to correct files/directory locations on the new server.
I know this sounds like a nebulous statement but there's a lot of
settings on the Admin Tool options/settings menu - you'll have to
click through each tab on the dialog box to check them.

4. Delete/make readonly the original network share to take the
database offline. I'm assuming users don't have direct access to the
original server (e.g. Term Server/RDP) to access VSS by the physical
file system here.

That's basically it - after you've copied it, you should be OK.

Dave Riches.

On Aug 17, 10:54 am, Jimworkem...@googlemail.com wrote:
> Guys I understand VSS as well as I undersand ancient Greek, In both
> cases I've never used it, never had need to use it, the only
> difference is I know have been thrown into the deep end and asked to
> migrate it to a new server as the current server is near over flowing
> point.
>  I don't understand the instructions in this article at all what do
> you suggest?

date: Sun, 19 Aug 2007 13:18:22 -0000   author:   DaveR

Re: http://support.microsoft.com/kb/176909/   

On 19 Aug, 14:18, DaveR  wrote:
> VSS is basically a big file system that's accessible over the network
> by sharing the root directory (e.g. c:\vss) using network shares.
> Under the root directory, you'll find 2 directories and 2 files that
> make up VSS. These are:
>
> data
> users
> srcsafe.ini
> users.txt
>
> To move the database, perform the following steps:
>
> 1. Copy these items to a directory on your new server (e.g. d:
> \newvss), preserving the subdirectory structures within the data & sub-
> directories. I'd suggest using a command line tool like 'robocopy'
> from the Win2K/2K3/XP resource kit to do it - robocopy is a more
> efficient/flexible tool than the standard Windows xcopy command. Make
> sure users who'll be accessing VSS have Full Control permissions at
> the NTFS file level.
>
> 2. Network share the directory you've copied them to  (d:\newvss).
> Make sure that the users who'll be accessing VSS have 'Full Control'
> permissions at the network share level.
>
> 3. In the VSS admin tool, verify that any settings such as VSS Logging
> files are set to correct files/directory locations on the new server.
> I know this sounds like a nebulous statement but there's a lot of
> settings on the Admin Tool options/settings menu - you'll have to
> click through each tab on the dialog box to check them.
>
> 4. Delete/make readonly the original network share to take the
> database offline. I'm assuming users don't have direct access to the
> original server (e.g. Term Server/RDP) to access VSS by the physical
> file system here.
>
> That's basically it - after you've copied it, you should be OK.
>
> Dave Riches.
>
> On Aug 17, 10:54 am, Jimworkem...@googlemail.com wrote:
>
>
>
> > Guys I understand VSS as well as I undersand ancient Greek, In both
> > cases I've never used it, never had need to use it, the only
> > difference is I know have been thrown into the deep end and asked to
> > migrate it to a new server as the current server is near over flowing
> > point.
> >  I don't understand the instructions in this article at all what do
> > you suggest?- Hide quoted text -
>
> - Show quoted text -

MANY THANKS YOU SAVED ME A LOT OF TIME AND EFFORT DAVE!!!

Cheers,

Jim.

date: Sun, 19 Aug 2007 16:20:01 -0700   author:   unknown