1. NetWorker Management Console
Product Overview
July 2005

2. Agenda Architecture System Requirements Installation Migration
Intermission
Console “Tour”
New Keystone Features
Console Features
Troubleshooting

3. Console Development Team
Manager: Michael Sevy
alias: nmc-eng
Sukarna Grandhi
Skip Hanson
Chris Hawkins (UI Designer)
Barry Herman
Shern Jauhal
Dharmesh Patel
Lena Protasov
Michael Pyle
Richard Reitmeyer
Susan Stevens (Graphics Artist)
Yan-Qing Wu

4. Terminology Control Zone Data Zone Console Server Console Client
Console server and its managed nodes
Data Zone
A NW server, its clients and storage nodes
Console Server
Host where Console is installed
Platforms: Windows & Solaris
Console Client
Downloaded Java app via IE or Netscape
Managed Node
NW server managed by Console
Platforms: Windows, Linux, UNIX

5. Console and Admin Windows
Console Window
Events
Enterprise
Libraries
Reports
Setup
Launches
NW Admin
(nw-serv1)
NW Admin
(nw-serv2)
. . .

6. Architecture – Process Interaction
Console Client
NW server
loads 2
Console Server
http 1
nsrd
splash.html
Welcome …
browser
RPC
gstd
nsrmmdbd
Web start 3
RPC 4
app
nsrexecd
nsrjobsd

7. Architecture GSTD License Information Database Interface
Tcl Interface
License Information
User Management
Database Interface
Host Management
nsr Interface
GSTD
Data Collection
NW Server
NW Server
NW Server
NW Client
iAnywhere
LLM (optional)
TclHTTPd DB

8. System Requirements Console Server
Windows 2000/ bit
Solaris 7, 8, 9 & 10
Linux
RedHat Advanced Svr 2.1, Enterprise Svr 3 and 4
SuSE Enterprise Svr 8 and 9
NetWorker 7.3 client must be installed on Console server
JRE (w/ WebStart)
Optional: LLM 7.0 or later
NetWorker versions supported by Console
NetWorker 7.0 (and above) on Linux, UNIX and Windows
Console Client
AIX
Mozilla 1.8
Netscape 4.7.2
HP/UX
Mozilla 1.6
Linux
Mozilla 1.4
Solaris 8 & 9
Netscape 6.2.3
Solaris 10
Mozilla 1.7
Windows2003 Enterprise or Datacenter Edition
IE 6.x
Windows XP, 2000, or 2003 (32-bit)
IE 5.5 or 6.x
Netscape or 7.x

9. Is a Web-deployed Java Application
Console Client
Is a Web-deployed Java Application
Delivered to the Client by Java Web Start
Ensures latest version is downloaded from Console server
Then behaves as a regular desktop application
Can be Launched from:
The desktop
Java Web Start Application Manager
Web browser, but not needed to run

10. Installation Information
Package locations
/usr/src/ARCHIVE/nw/7.3 (Unix path)
\\archive\archive\nw\7.3 (Windows path)
Package Names (the standard NW pkgs)
nw_win_x86.exe
nw_solaris_64.tar.gz
nw_linux_x86_64.tar.gz
Default Install locations
C:\Program Files\Legato\Management\GST (Windows)
/opt/LGTOnmc (Solaris)
/opt/lgtonmc (Linux)
Note on Size
The Windows package is a combination of core NetWorker & NetWorker Management Console and requires several hundred MB of free disk space

11. Windows Installation of NMC
Select to have NMC installed
LLM is optional

12. Windows Installation of NMC
Once the install of NetWorker is complete, the NetWorker Management Console install will begin (as shown in the next slide)

13. Windows Installation of NMC
Begin installation of NetWorker Management Console

14. Windows Installation of NMC
Note space requirements for NMC installation

15. Windows Installation of NMC
The database can be installed in a different location from the server binaries
9000 and 9001 are the default port numbers for clients to connect to the Console server

16. Windows Installation of NMC
Like NetWorker, you can keep or overwrite an existing “database”
Upgrade steps involve “uninstalling” (and keeping the database), then reinstalling the new version of software

17. Windows Installation of NMC
Remember Console server location. You must list the server name and the port number (i.e )
You can launch directly after install completes

18. NMC Product Directories

19. Setup of NMC Client on Unix
The browser runs a javascript routine to detect the required version of Java Web Start. If not available, the following info is displayed. There is some variation among the different platforms.
Download the JRE from the Console server
CD to dir and Run the self-extracting binary
Sometimes the JRE is detected, but there is a problem with the way the browser associates the jnlp app with its handler -- the following instructions are then available.
Add this line to the .mime.types file
type=application/x-java-jnlp-file desc="Java Web Start" exts="jnlp“
Add this line to the .mailcap file
application/x-java-jnlp-file; /usr/local/j2re1.4.2/javaws/javaws %s

20. Additional Install Considerations
Linux
Use rpm to install the lgtonmc package
Users must run the “config.sh” script once installation is complete. The script is found in the /opt/lgtonmc/etc dir (by default). This is required because the Linux install is not interactive.
Solaris
Use pkgadd is used to install the LGTOnmc package
nsraddadmin
This must be run on any NetWorker server that does not have a local Console server
The syntax is: nsraddadmin –u

21. Console Migration
Migrating from to Keystone is not supported. (If customers have this environment, they are to upgrade to 3.0, then install the Keystone version of Console)
Workflow is to “uninstall” Console and leave the database. Install the new version and select the “keep the database” option
No upgrade enabler is required for Console from 3.1 to the Keystone version
Customers who have a licensed version of Console 3.1 do not need to enter the new “advanced” report license

22. Intermission

23. Current Product Features
Centralized Enterprise Hierarchy
Logical map of NetWorker servers
Centralized Managed Events
View & sort NetWorker error messages - by priority, server, …
Annotations & Notes can be added to events
Centralized Reporting
Consolidated status for all NetWorker savegrps
Centralized Administration
Provides cross-platform consistency

24. Current Product Features (cont)
Logging NetWorker user activities (aka auditing)
Console client respects locale settings for date and time
International character set support
Interface for managing Legato License Manager and bulk licenses
Console access control: restricting user “views” to NetWorker servers

25. New Keystone Features/Enhancements in NMC
Expand console platforms
Console Server
Linux
Console Client
Linux, AIX, HP-UX
I18N Conversion
New Drive Utilization Report
OEM Re-branding
New “look” (icons & layout)
User preferences
Improved “column” management
Integrate with NetWorker Install
Monitor Retrospect servers
Initial configuration wizard for NMC Launch NetWorker saveset configuration wizard
Incremental backups (new “module” for ASA)
Reduce (eliminate) LLM Dependency
Support concurrent tape library operations*
Device Configuration GUI*
Manual Cloning*
Save set Query of Media DB*
Improved monitoring*
Launch NetWorker client applications*
*new admin feature

26. Console Client – Splash Screen & Login Dialog

27. EULA Prompt
New for Keystone
First time a user connects to Console, the EULA is displayed
The acknowledgement is stored in the Console database. It can be reset in a future version of Console to have it displayed again
Legal has stated that as long as someone, somewhere in an enterprise has accepted the EULA, it is binding

28. Administrator can “hide” this help in future
Getting Started Page
Administrator can “hide” this help in future

29. Elements of Console Windows
Task Bar
Menu Bar
Tool Bar
Details Pane
Navigation Pane

30. Elements of Console Windows
Task Bar
Separate tasks user performs. Drives how the rest of screen drawn.
Menu Bar
Changes depending upon task. A “task specific” menu item will appear. This menu item can be accessed via a right-mouse click.
Tool Bar
Task specific. Some actions will behave differently depending upon the object selected in the navigation or details pane.
Navigation Pane
Classic “tree view” organization. Not all task areas have a navigation pane.
Details Pane
Where details, results or messages are displayed. Generally, the details pane consists of a table.

31. Navigation between Console and Admin
Console Window
NW Admin Window
Groups
Arch Reqs
Devices
Alerts
Sessions
Log
Server, group & client resources
Library and Device Config/Ops
Label Tapes Pools Volumes Indexes Saveset Query

32. Standard Console features

33. Standard Console features (cont)
“Default” table columns are the ones predefined by Console (however, there is, currently, no way to “reset” back to the default set of columns)
All table columns can be sorted, reordered and resized
User preferences are saved in the Console database (therefore, they “follow” the user, not the machine)
Preferences are different for Console and Admin sessions
Online Help is screen “context” sensitive (new for Keystone)
All help content is single-sourced, i.e. printed docs and online help are the same (new for Keystone)

34. Setup Task
Task renamed for Keystone. Use to be “Software Administration” in Console 3.1
Allows administrator to manage user accounts
Provides access to the EMC Legato License Manager
System Options
Configuration Wizard

35. Setup Task: User Management

36. Setup Task: User Management
Restricting a User’s Views affects:
Managed Events
Only events from allows servers
Enterprise
Only see allowed servers
Libraries
Only see devices controlled by allowed servers
Reports
Only allowed servers are available

37. Setup Task: Options

38. Setup Task: License Management

39. Enterprise Task
Task renamed for Keystone. Use to be “Enterprise Hierarchy” in Console 3.1
Provides enterprise wide view of all servers being managed by Console
Allows user to “logically” group servers or organize their environment
Users can change the “features” for the server being managed (i.e. choose to collect event or reporting data, or none at all)
Users can launch the “managed” application from this task area (i.e. launch NW Admin)

40. Enterprise Task

41. Task renamed for Keystone. Use to be “Managed Events” in Console 3.1
Events Task
Task renamed for Keystone. Use to be “Managed Events” in Console 3.1
Provides enterprise wide view of all events from Console, NetWorker or Retrospect servers
Monitoring Retrospect servers is new for Keystone
Users can launch the application specific administration tool/interface (i.e. launches NW Admin)

42. Events Task

43. Task renamed for Keystone. Use to be “Device Central” in Console 3.1
Libraries Task
Task renamed for Keystone. Use to be “Device Central” in Console 3.1
Provides a cross-server view of libraries throughout the enterprise
User can administer libraries from a central location
Library information is
Automatically updated after servers have been added or deleted from the Enterprise task
Polled periodically (according to the polling period defined in the system options)
Updated on request (when the user executes the refresh operation)

44. Libraries Task

45. Libraries Task

46. Reports Task
Creates and displays reports based on data collected from managed hosts
Basic and advanced reports (New for Keystone)
Users who upgrade from 3.1 do not need to enter the advanced report enabler
Reports can be saved for scheduling outside Console, shared with other users, printed, exported into various formats, or displayed as charts (most reports).

47. Reporting: Unlicensed Reports

48. Reporting: basics
Enter Parameters

49. Reporting: basics (cont)
Generate report

50. Reporting: basics (cont)
Chart Mode
Chart Type

51. Reporting: New Drive Utilization Report
Default “view” is chart mode, as opposed to table mode
Only supports data from Keystone servers
Drive information collected only pertains to “scheduled” save processes.

52. Reporting: New Drive Utilization Report (cont.)

53. Reporting: New Drive Utilization Report (cont.)

54. Reporting: New Drive Utilization Report (cont.)

55. Reporting: Custom Reports
Created by saving report config under a user-specified name
What is saved:
Config parameters
Report orientation (landscape or portrait)
View type (table or chart)
Chart type (bar, pie, plot, or stacking bar)
Chart selector values
Custom report displayed in Reporting tree under canned report
Custom report admin:
Update, rename & delete
Sharing private reports
Hide other user’s reports

56. Reporting: Custom Reports (cont.)

57. Command Line Reporting
Allows integration of reports into external scheduler
Installs and Runs on Console server
Supports canned and custom reports

58. Command Line Reporting Syntax
gstclreport [-h] -r reportname -u username [-P password] [-a chartselector]
[-c chartype] [-f filename] [-n fontfamily] [-o orientation] [-v viewtype]
[-x exporttype] [-C argument1] … [-C argumentN]
where:
-h Prints this help message
-r reportname The full path of the report to run like "/Reports/Users/User List"
-u username Logs into GST server with given name
-P password Logs into GST server with given password
-a chartselector The set of Y axis to display in a chart
-c chartype The chart type: [bar | pie | plot | "stacking bar"]
-f filename The name of the export file
-n fontfamily A font family to override the default
-o orientation The orientation [portrait | landscape]
-v viewtype The view type [table | chart]
-x exporttype The type of export [ pdf | postscript | html | csv | print]
-C <argumentN> Any report argument like “Server Name” or “Backup Type”

59. Command Line Reporting Example
gstclreport -u administrator -P administrator
-r "/Reports/NetWorker Statistics/Save Set Summary"
-v chart -c bar -o landscape
-x pdf -f "D:\Reports\summary2.pdf"
-C "Server Name" "opakapaka, nesca"
-C "Backup Type" FILE
-C "Group Name" Default
-C "Client Name" "yacht, zeus, troppo, pa-server"
-C Level full
-C "Save Set Name" "c:"
-C "Save Time" "01/01/03 12:00:00 AM" "4 days"

60. Troubleshooting: NMC Server
Review log files
on Windows: C:\Program Files\Legato\Management\GST\logs
on Solaris: /opt/LGTObgst/logs
Start gstd with -Dn, where n = 1 through 6 (a lot of output above 2)
Debug level can be changed from the System Options (Setup task)
Environment variables
GST_MAXLOGSIZE
GST_MAXLOGVERS
GST_DEBUG

61. Troubleshooting: Server Directories
The logs directory
The DB directory

62. Troubleshooting: NMC Client
Enable the output of client log messages:
Open the Java Web Start Application Manager
Go to File->Preferences->Advanced
Check "Show Java Console" to display Java Console window when the client is running.
Check "Log Output" if you would like the info in a file.

63. Troubleshooting: Client Debug Level
Set the debug level of the client by:
Pressing CTRL, SHIFT & right mouse button in any details pane (right side of screen)
In the menu, select required debug level
Output to Java Console (see previous slide)

64. Troubleshooting: Opening an Incident
Open incident in DDTS and assign it to nwcon user
Contact development team:
When reporting problems, include:
Console server & client platforms, including patches & service packs
Platform & version of NW servers
Console log files, core files, or Dr. Watson files
Java Console output