Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Source Safe / August 2007

Tip: Looking for answers? Try searching our database.

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

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jimworkemail@googlemail.com - 17 Aug 2007 15:54 GMT
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?
DaveR - 19 Aug 2007 14:18 GMT
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
[quoted text clipped - 3 lines]
>  I don't understand the instructions in this article at all what do
> you suggest?
Jimworkemail@googlemail.com - 20 Aug 2007 00:20 GMT
> 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.
[quoted text clipped - 46 lines]
>
> - Show quoted text -

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

Cheers,

Jim.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.