Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Hi Bo, Thanks for the comments! I agree, it's not necessary to backup working copies if developers are consistent in committing or checkpointing changes back to the repository on a regular basis. I was concerned about the repository itself and how moving critical data from the standard file server onto a stand alone PC reduces the consistency and ease of administration of the backup and file system solution. By the way, I meant to say "fork", instead of "exec"... Oops! Thanks, David. "Bo Berglund" <bo.berglund at telia.com> wrote in message news:mh1omu0qui33kqt9bha001ft5brm8scuiv at 4ax.com... > I think that if the developers commit their stuff regularly (when they > leave at night) then there is really no need for a workstation backup > to be done. I assume that your repository on the W2000 box *will* be > backed up nightly of course. > This is how I have been running my shop for 18 months now with 5-8 > developers using CVS. No problems so far, but I use the CVSMailer > program to monitor activity so I can see when a lazy developer does > not commit so I can tell him. > A side effect of having the sandbox locally is that all compiles and > builds speed up something wonderful. No time to go for coffee or smoke > during a build anymore... > > If you are really not wanting developers to commit daily changes > (why?) then you could set up a backup task on each workstation to run > at night. You could use the backup that is shipped with W2000 and > WinXP and target a file on the samba server or another Windows server) > as the volume to backup to. This will create a backup file on the > server which can in turn be backed up to tape. This way you will get > all backups you need. Of course the developers must leave the > workstations switched on nightly for this scheme to work. > > /Bo > > > On Tue, 27 Aug 2002 15:55:33 -0700, "David McAvoy" > <David.McAvoy at PerComm.com> wrote: > > >Hi (Tony, Bo), > > > >Thanks for the info... By the way, how do you manage backing up files on > >distributed > >PC's? That's why having the repository and its working copies on a file > >server is > >desirable in this case. > > > >Also, I discovered that other applications such as emacs have no problem > >deleting files > >called ",Makefile," etc. from the Samba drive, so it appears that Samba is > >not > >necessarily the problem in this case, although with my limited resources I > >can only test on > >Samba shares and regular Windows 2K shares (which work). Also, if one uses > >a file > >name such as ",Makefile," in the PC shell one must use quotes to escape it, > >otherwise it > >is rejected as an invalid file name. > > > >Please don't take my comment above as indicating that I don't > >understand/value > >your comments about file locking and such. I appreciate your comments on > >the > >matter and will move the repository to the service machine. However, this > >will probably > >cause a lot of backup issues! > > > >I did read your previous comments regarding this issue and unfortunately I > >thought you > >were referring to the instance in which "exec", style of access was used to > >obtain access > >to a repository shared to the users computer. I didn't realize that you > >were referring > >to the NT service accessed through the "sspi" or other mechanism. I suppose > >this means > >that the service is serving CVS commands from users in a multi-threaded > >manner? > > > >By the way Tony, did you notice you are sending three replies to everything? > > > >Thanks for the help everyone, > > David. > > > > > >"Tony Hoyle" <tmh at nothing-on.tv> wrote in message > >news:3D6BDEDD.8010404 at nothing-on.tv... > >> David McAvoy wrote: > >> > Hi, > >> > > >> > I use CVS NT with repository on SAMBDA drive, however naming conversion > >> > causes issues with ,Makefile, etc. RCS file locks when CVS NT server > >tries > >> > to > >> > delete them from repository. > >> > >> Do not do this. > >> > >> > Does anyone have any suggestions regarding an smb.conf file that might > >allow > >> > the > >> > samba server to work with files of this type? > >> > >> Don't do it. It won't work. Use a server talking to its own local > >> drive instead. > >> > >> Tony > >> > > > > > /Bo > (Bo Berglund, developer in Sweden)