Subj : Re: moving server
To   : Mike Tripp
From : Darren Gibbs
Date : Thu Oct 12 2000 09:41 pm

 DG>> So, enlighten us all - how do you get NCOPY to process the
 DG>> bindery files?

 MT> Good question...I =thought= it had the API calls to handle open/close
 MT> as do BINDFIX, BINDREST, NBACKUP, etc...but damned if I don't get
 MT> access errors trying it now. Might not've noticed not getting a new
 MT> bindery, only using SUPERVISOR and GUEST accounts (as I said,
 MT> "suitably simple").  Timestamps on both NCOPY and NET$*.SYS are circa
 MT> '91, and I've certainly done the drive shuffles several times since
 MT> then.

There's your answer.

Shuffling the drive will NOT copy the bindery {and sometimes certain other 
locked files}. However, once you fire up the drive in another server, it'll go 
"Oh shit, no binderies, I'll create new ones" - and does so.

If you run accounts without passwords, and only use guest and supervisor, you'd 
never notice.

 MT> BINDFIX puts current stamps on the NET$*.SYS and NET$*.OLD when it
 MT> runs...gave mine both '00s.  Don't have any NET$*.OLD files,
 MT> either...so I didn't NCOPY the .OLDs to the new drive and BINDREST,
 MT> though it would certainly accomplish the task.

That's another method, coupled with the above - however, I didn't want to 
explain it to the original poster because he pretty obviously didn't have much 
experience, and I didn't want to make life harder for him. :-)

 MT> Never trusted
 MT> NBACKUP/SBACKUP as one or both seemed to be the stars of just about
 MT> every patch release in those days.  Didn't come from a tape, either,
 MT> as the Wangtek was yanked and tossed into a box in the garage after
 MT> failing to restore 20% of its "verified" contents during the swapout
 MT> from ESDI to IDE.

Pfffft. I've never used either of those wonderful "products", and I never will.

 MT> So I'm going to guess that maybe BINDREST from the original SYS:
 MT> files
 MT> to the new SYS: volume might preserve the original timestamps or the
 MT> server uses an old date when recreating them from scratch if not
 MT> found.  Will tinker with it if/when I finally get around to retiring
 MT> the existing box for one that supports a bit more CPU/RAM, but there's
 MT> more than a few weekends of trickling hardware down through the nodes
 MT> first.

It's possible, but hardly worth bothering with - *I* know how to move SYS 
volumes - several ways, in fact - I just didn't want to explain them to someone 
who appeared a lot less technically experienced because most of them are kinda 
complex.

 MT> Still, none of the bundled DOS utils are a substitute for real
 MT> 3rd-party backup software if trying to preserve the more sophisticated
 MT> stuff.

No argument at all there.

DaZZa

--- GoldED/2 3.00.Beta5+
 * Origin: WOW BBS - Coming Soon! Netware for the Nintendo! (3:712/888)

.