Subj : moving server To : Darren Gibbs From : Mike Tripp Date : Tue Oct 10 2000 10:31 am Hello Darren. 09 Oct 00 04:44, Darren Gibbs wrote to Mike Tripp: MT>> It certainly =can= be, if the server configuration is suitably MT>> simple. My 3.11 server has been running since 1989, and I can MT>> assure you that is not using the same drives it started with. I MT>> have done this, as I described it...multiple times. DG> So, enlighten us all - how do you get NCOPY to process the bindery DG> files? Good question...I =thought= it had the API calls to handle open/close as do BINDFIX, BINDREST, NBACKUP, etc...but damned if I don't get access errors trying it now. Might not've noticed not getting a new bindery, only using SUPERVISOR and GUEST accounts (as I said, "suitably simple"). Timestamps on both NCOPY and NET$*.SYS are circa '91, and I've certainly done the drive shuffles several times since then. BINDFIX puts current stamps on the NET$*.SYS and NET$*.OLD when it runs...gave mine both '00s. Don't have any NET$*.OLD files, either...so I didn't NCOPY the ..OLDs to the new drive and BINDREST, though it would certainly accomplish the task. Never trusted NBACKUP/SBACKUP as one or both seemed to be the stars of just about every patch release in those days. Didn't come from a tape, either, as the Wangtek was yanked and tossed into a box in the garage after failing to restore 20% of its "verified" contents during the swapout from ESDI to IDE. So I'm going to guess that maybe BINDREST from the original SYS: files to the new SYS: volume might preserve the original timestamps or the server uses an old date when recreating them from scratch if not found. Will tinker with it if/when I finally get around to retiring the existing box for one that supports a bit more CPU/RAM, but there's more than a few weekends of trickling hardware down through the nodes first. Still, none of the bundled DOS utils are a substitute for real 3rd-party backup software if trying to preserve the more sophisticated stuff. ..\\ike --- GoldED/2 2.50+ * Origin: TechKnowledgy at Work (1:382/61.1) .