From: CACHO@ITESO.BITNET
Newsgroups: bit.listserv.novell
Subject: Re: various topics
Date: 16 Oct 92 17:44:20 GMT
Reply-To: Novell LAN Interest Group <NOVELL@SUVM.BITNET>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL11]
              "Michael_Kessler.H

>
> Sorry if these are FAQ, but the red books do not seem to provide too many
> answers.
>
> 1.  I have been building the Novell network under my own account, having
> given myself supervisor equivalent rights.  Recently I noticed that all the
> directories that I created in APPS and other public directories belong to
> me rather than to the (anonymous) supervisor or to the system itself.
> Could this create problems in the future; should I go back and recreate all
> those directories (oh what joy!) as the SUPERVISOR?

  It will do not harm to you or the system.  We have a setup like yours, and
  never had a problem related to this.

> 2. In volume information, I came across the following chart which really
> makes no sense, given that I have at most two accounts with two three-word
> files in the INSTRUCT volume (I count a total of three directories: USERS
> and the two accounts under USERS, and three files including the VOL$LOG.ERR
> file in the root):
>
>                      SYS                 ADMIN              INSTRUCT
>                   Total   Free        Total    Free      Total      Free
> Kilobytes       307,200  259,360    512,000  503,124    456,192   454,332
> Directories       6,080    1,595      4,384      440        256       177
>
> Is this normal or is there something wrong?  If the latter, where would I
> find the answer to the problem?  Why should INSTRUCT be limited to 256
> directories compared to the number in the other volumes and claim that 79
> are used up?

  Don't worry, create another directory and you will see a lot more of total
  directories, netware manages it this way, when you create a directory, it
  assigns it a number of entries, and if you create a lot of directories, you
  have a lot of entries, with three directories, you don't already need
  much free entries for the directory places.  I think files count as directory
  entries too, (please correct me if i'm wrong)
>
> 3. The backup system I will be using is external to the network, and
> therefore will not backup the Bindery.  Moreover, I was told during the
> Novell System Manager course that backing up the Bindery and hoping to
> restore it through a backup system was a questionable enterprise--only some
> backup systems could do that reliably.  On the other hand, no other
> solution was given.  Nor does the red book indicate if it is possible to
> backup the bindery on diskette (say every month or less), so that it could
> be restored to full value once a system has been restored at a basic level.
> I've had one crash, and do not look forward to another.  Is it possible to
> backup the bindery to diskette?  If so, how?
  We have experimented with NBACKUP.EXE which comes in your public directory,
  and stored our bindery, later we restored it (with nbackup.exe) in another
  hard disk, it recovered the bindery, but one word of caution, the name of
  the server MUST remain the same if you want your bindery back, and the
  supervisor account gets the password which is stored in the files, so, if
  you don't remember it, change it after restore, and before logging out!
  + Note: nbackup does not backup NAME SPACE volumes.  It is not a problem
    here, we don't use them.
>
> Thanks,
> Michael_Kessler@HUM.SFSU.EDU
>
--
  Hector Gonzalez, Iteso University.
  Guadalajara, Mexico.
  Cacho@iteso
  Cacho@itesocci.gdl.iteso.mx