For #2 it’s easier,
imho, to accomplish this using Windows tools. As part of my modified
silent install script I have an .ini file that imports whatever settings I want
to the Windows registry. It runs at the tail end of the install so I know
everything going into production is configured correctly.
So if you wanted to set the
buffer size to 1024 (little high, no?)…
Contents of .ini file:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
Buffer_Size = REG_DWORD 1024
Execute:
Regini filename.ini
Dig through the registry and
the rest of the settings are there as well.
Date: Thu, 16 Jul 2009
09:10:42 -0400 (EDT)
From: Justin Piszcz
<jpiszcz AT lucidpixels DOT com>
Subject: [Veritas-bu]
Question in regards to command-line add/config
of Windows
Clients
To:
veritas-bu AT mailman.eng.auburn DOT edu
Message-ID:
<alpine.DEB.2.00.0907160905550.1116 AT p34.internal DOT lan>
Content-Type: TEXT/PLAIN;
format=flowed; charset=US-ASCII
Hello all,
For a UNIX(Standard) Client,
it is relatively simply to automate a
policy/client addition.
For a Windows client, is it
possible to automate the following steps via
the command-line?
1. Host Properties ->
Master Server
a. Client
attributes -> Add the Windows client here.
b. Set
the Windows Open File Backup options and apply them.
c. There
is a DEBUG option in jnbSA I believe that will record all of
the commands performed by jnbSA, does anyone recall how to do this?
2. Connect to the client
(bpsetconfig)
a. Set
timeouts to the standards that you have in your environment.
b. Under
the Windows Client -> Client Settings
1. Set the Communications buffer size to 1024 kilobytes
I guess the next step I need
to find out is how to enable debugging for
jnbSA so it prints out all
commands-- this should get me the answers I
need unless someone has done
this already?
Justin.