Subj : Re: moving server To : Mike Tripp From : Darren Gibbs Date : Wed Oct 18 2000 09:37 pm DG>> Shuffling the drive will NOT copy the bindery {and sometimes DG>> certain other locked files}. MT> Like the transaction tracking logs... I do remember on separate MT> occasions either kissing them off altogether or going through the MT> disable/copy/enable routine. Yeah, those were specifically the others I was thinking about. DG>> However, once you fire up the drive in another DG>> server, it'll go "Oh shit, no binderies, I'll create new ones" - DG>> and does so. MT> So is this where the old timestamps come from? Are they touched with MT> some date that is significant to somebody somewhere at Novell when MT> created from scratch? I originally suspected that might happen even MT> after downing/re-upping the server with the BINDFIXed versions. I believe they're timestamped with Novell's creation date, regardless of when they are actually made. DG>> It's possible, but hardly worth bothering with - *I* know how to DG>> move SYS volumes - several ways, in fact - I just didn't want to DG>> explain them to someone who appeared a lot less technically DG>> experienced because most of them are kinda complex. MT> Howzabout explaining any to me provided they don't involve a third MT> volume or a 3rd-party software purchase? Only lurk here to keep from MT> forgetting more about Netware than I ever knew. To know something new MT> would be a bonus. ;) The simpliest way is to do the following. 1) Run bindfix 2) Run bindfix (yes, run it again) 3) Use ncopy to transfer files to new volume. 4) Restart on new volume 5) Run bindrest. Of course, this can cause mondo problems with file and trustee assignments - because when the server starts up and sees no matching entries in the (new, before bindrest) bindaries, it removes the rights. Not a problem if you don't have any special trustee assignments, but... :-) Alternatives include mirroring the drives {even if they're different sizes} and then using partition magic to expand the Netware partition to max out the disk space, then adding the free space to the existing volume segment using install. If you're transferring to an identical disk, you can even be sneaky and boot to Linux and use dd to copy the drive. But that's only valid if the disk is exactly the same size - otherwise it won't work properly. DaZZa --- GoldED/2 3.00.Beta5+ * Origin: WOW BBS - Coming Soon! Netware for the Nintendo! (3:712/888) .