Of course that sometimes doesn't work out.  For some reason adding
drives to all servers works fine from the GUI but if I use the same
command an options from command line it will often (not always)
complain.   This was really frustrating for me some time back when I
wrote a script during installation of several media servers only to have
it fail on adding the drives to some of the servers.   Veritas (now
Symantec) support was no help.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Paul
Keating
Sent: Friday, June 30, 2006 1:36 PM
To: Veritas List
Subject: Re: [Veritas-bu] CLI or GUI

If you run jnbSA on unix with the command log option, you will get a log
file with the appropriate CLI to do whatever task you are doing in the
GUI.
Dunno if you can do that with the windows GUI.

ie, I have a regular restore of an exchange SG to a standby server
scheduled via cron.
I needed to change the directory on the client where Netbackup puts the
logs (C:\temp by default)
Started up jnbSA with logging on, started a restore from the GUI,
specified an alternate directory for the log files and grep'ed the
"altername path" name out of the log to get the switch.

Pretty neat, actually.

Paul

-- 


> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu 
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Jeff Lightner
> Sent: June 30, 2006 1:19 PM
> To: Keith W; Veritas List
> Subject: Re: [Veritas-bu] CLI or GUI
> 
> 
> For activity monitoring you can't beat the GUI.
> 
> For newbies (and tasks done infrequently) the GUI is nice as it often
> lets you figure out what to do from its menu selections.
> 
> For experienced users the CLI is more flexible because you 
> can give the
> flags you want to commands and can also do certain things 
> more quickly.
> Also knowing the CLI lets you script things.  A good example 
> is downing,
> upping or resetting drives.  I original learned how to do that via the
> GUI device monitor but found it incredibly slow.   With the 
> command line
> I was able to script it so I could bounce a drive on the 
> master and all
> media servers in less time than it took to just shutdown a 
> single drive
> on all servers.