Re: SourceSafe question

From: Atreju (someone_at_who.hates.junkmail)
Date: 08/08/04


Date: Sun, 08 Aug 2004 15:37:57 GMT

On Sun, 8 Aug 2004 07:30:26 -0500, "Ralph"
<nt_consulting32@hotmail.com> wrote:

>
>"Atreju" <someone@who.hates.junkmail> wrote in message
>news:4obbh05d2i1qcc20asirgp1to2culvr566@4ax.com...
>> I know in a company I used to work for, the head developer had me
>> install VSS Server and he connected to it to develop.
>>
>> As I understand it you can have it keep every single change of your
>> code in history so you can always fall back on older code.
>>
>> My question: Does the local-install of Source Safe do this as well?
>> All I could tell from a local install is that it controls access to
>> code, so it is "checked in" and out to avoid simultaneous modification
>> and saving of code. But does it have the capability to keep all the
>> code's history, or is this something only available in VSS server?
>>
>> TIA
>>
>>
>> ---Atreju---
>
>To amplify on Michael's comments.
>
>There is little practical difference between a Local VSS database and a
>Server VSS database, beyond the Server version's ability to manage
>concurrency and multiple users. In fact you can even 'share' your local
>database with someone else across the net. (Though, not advised for heavy
>use.)
>
>So you are going to be the adminstrator? A couple pieces of advice.
>1) Backup the server database often. Do a complete backup. Do not use or
>depend on any 'incremental' backups the net administrators are using.

Every single byte of my data is backed up regularly on a nightly
backup to DDS. I have a 2-week cycle so at any time I have 2 weeks old
backup. In addition I have dual-drives for every data volume.

Thanks!

>2) Setup a regular analyze and clean routine.
>3) Go online and make sure you have the latest 'n greatest Analyze,
>utilities, and SP.
>http://msdn.microsoft.com/ssafe/default.asp.
>4) Never panic. Even when a VSS database becomes corrupted - it is usually
>not as screwed up as you might believe on first look. <g>
>
>hth
>-ralph
>

---Atreju---



Relevant Pages

  • Re: SBS 2003 Backup failing
    ... I understand that you encounter error 800423f4 when trying to backup SBS ... volume by using the Volume Shadow Copy service in Windows Server 2003 ... I've re-registered the VSS DLLs. ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup Freezing Server
    ... backup some other data. ... I've also been googling for anything related to VSS and general ... I've been backing up all the files from another server, ... I'd also install this patch. ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup Freezing Server
    ... All the sbs updates are on: ... problem started when the server was still at Windows Server 2003 SP1. ... chance to run a backup with them in place. ... I've also been googling for anything related to VSS and general ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup Freezing Server
    ... I installed the hotfix you linked to, but the server still froze during ... system state backup. ... Could there be an issue with AD & VSS? ... see if you still get the freeze during backup. ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup Freezing Server
    ... problem started when the server was still at Windows Server 2003 SP1. ... chance to run a backup with them in place. ... I've also been googling for anything related to VSS and general ... Get the server to freeze and see if you can tell ...
    (microsoft.public.windows.server.sbs)