Via:         UK.AC.LE; 11 JAN 93 15:19:02 GMT
X-Mailer:    ELM [version 2.3 PL0 (LUT)]
Newsgroups: bit.listserv.novell
Date:         Mon, 11 Jan 1993 15:18:15 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "A.G. Lowe-Norris" <agl1@LE.AC.UK>
Subject:      Re: Bindery transfer
              92 2:51 pm

Hi all,

        A new way to copy binderies?
        ----------------------------

        A while back Matthew Dokman wrote the following:

> >         I would like to transfer all of the bindery information of some
> > 1,400+ users from one file server to another, without recreating the user
 id's
> > I cannot use MAKEUSER because all users have established passwords that I
> > can't reproduce. This new file server is a central hub for the system we
 have,
> > which consists of 3 file servers and a CD-ROM tower. This would enable me to
> > route the users from the central, or "home" file server, to the service they
> > desire, which could be on any one of the mentioned devices.
> >
> >         My question is, what is the best way to transfer the info, including
> > mail directories but no home directories, without any fancy commercial
> > programs for which you pay a lot of money?  If it is possible to back it up
> > on tape and restore, or do an ncopy, what are the file names, and where do
>  they
> > reside? And also, what are the consequences for a very few users that
 already
> > have IDs with same login names on the "home" file server?
> >


Richard Letts (SALFORD.UK) proposed the following:


> 1. run bindfix (twice) on the source server
> 2. copy the net$????.old files to sys:SYSTEM on the new server
> 3. copy their filestore over
> 4. run bind rest on the new server
> 5. down the new server
> 6. bring it back up
> 7. run bind fix on the new server
> 8. down it again
> 9. bring it back up
>
> 5-9 are probably not necessary, but we got into the habit when moving our
> users from 2 (two) servers to 20 (twenty) new ones.
>

I use a far faster approach which has worked for us.

We have a server here, CC1, with 5000+ users in the bindery. We had a new
server to install and wished to copy the bindery. First I installed everything
for NW3.11 on the new server CC-MAC as normal. Second, using John Baird's
BINDCLOS function I closed the bindery on CC-MAC. I FLAGged the 3 files:

        NET$OBJ.SYS
        NET$PROP.SYS
        NET$VAL.SYS

as -T -H -Sy. Then I renamed the 3 files as *.BAK. Then I closed the bindery
on CC1 and flagged the three large bindery files as before. I copied these to
CC-MAC and finally flagged them back to +T +H +Sy. Using John Baird's BINDOPEN
on both servers brought the new bindery into effect immediately.


In addition to this, we use the NNS and this is locked into the bindery. For
anyone who has NNS installed, I can tell you we removed our NNS from the
bindery in a matter of about 10 mins or so without having any conflicts,
forced password resets, or random password creations at all. Anyone who is
interested give me a shout and I will explain it, but there are only a few of
us who really use it so I won't bore the others.

It was a simple matter to create the mail directories, (they have the same ids
in both binderies), and any user directories as needed. GRANTing rights then
followed and that was it.


Does anyone else do it this way?


Alistair.

-------------------------------------------------------------------------------
| Alistair G. Lowe-Norris, Systems Programmer         UK: agl1@uk.ac.leicester|
| Computer Centre, Leicester University,          Non-UK: agl1@leicester.ac.uk|
| University Road, Leicester LE1. 7RH., U.K.                                  |
|                                                                             |
| UK       Tel: (0533) 522250     Fax: (0533) 525027                          |
| Non-UK   Tel: +44 (533) 522250  Fax: +44 (533) 525027                       |
-------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU