[Veritas-bu] Novell Client Installation Issues: Summary

First, thank you to all that responded. There are many things that the 
documentation is completely lacking, and this is one of those areas.

We note that many of the older Novell clients had some installation 
quirks that made the information we saw about target installs necessary. 
With our issue, using the FP6 client, the install is actually much 
easier and intuitive than previously.


The two files, after installation, that needed tweeking, were the HOSTS 
and BP.INI. The BP.INI is straightforware, and is entirely created by 
the initial configuration after installing the client. This is for the 
target method, however, and the non-target method apparently uses the 
BP.INI a little differently. The non-target method is administered 
through a Windows interface and the policy on
the server must be of type NetWare (the type is Standard for the target 
method).
This would segregate users who choose to use the target method from 
those who
use the non-target method. The servers are case sensitive in the BP.INI,
apparently, and the same may be true of the hosts file, too, though I 
havn't
tested this.

Despite all the discussion about whether certain .nlm's are installed, 
the new
installer seems to do the right thing. With the older installation 
procedure,
there was a bunch of copying required, which seems bogus to me. We 
didn't have
to do any of that.

After running the installer, the initial configuration is done by running
BPSTART->'Main Menu'->'NetBackup Configuration...'. The first time the user
does this the BP.INI is automatically generated. There are four main 
items in
the 'NetBackup Configuration...' menu, and we stepped through the first 
three
(thought we may have done all four), I think, to get the client 
configured. See
p. 31 in the NBU 5.0 NetWare Admin Guide to see what this menu looks like.

Creating and configuring a target: BPSTART->'Main Menu'->'Target
Configuration...'->'Add New Target...' P. 53 in the NBU 5.0 NetWare 
Admin Guide
steps through this process. The user is prompted for several things, 
including
an admin user name and password.  For the target method, each target 
gets its own .tgt config file in
SYS:\VERITAS\NBUCLT\NETBACK\TGTS (the non-target method puts this data 
in the
BP.INI).

Oh, and I forgot to mention earlier that the policy file list, for the 
target
method at least, can not contain ALL_LOCAL_DRIVES. It must have a list 
of the
targets to back up. I imagine then, for example, that you could have 20 
targets
defined on the client, but if only two are listed in the policy file 
list, then
only those two will back up. This may mean that we will have to have a 
separate
policy for each target method client. The policy file list is configured
differently for non-target method clients, and we may be ale to use
ALL_LOCAL_DRIVES. If we're going to back up a number of
NetWare machines, we might consider requiring them to use the non-target 
method
for this reason.