Chapter 02 - Installing NetWorker and NMC

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.
Chapter 2 – Installing NetWorker and NMC
Upon completion of this chapter, you will be able to:

y Prepare to install EMC NetWorker
y Describe the NetWorker installation process
y Install the NetWorker software
y Install NetWorker Management Console
y Verify successful installation
y Start and stop the NetWorker daemons/services
© 2006 EMC Corporation. All rights reserved. Installing NetWorker and NMC - 1
In this chapter you learn how to install both NetWorker and Management Console software.
Installation of the software in a Microsoft Windows environment will be described. Although
the method of installation is different for other operating systems, the questions asked and
information entered is essentially the same for any installation.
In addition to the installation process, this chapter describes how to manually start and stop the
core NetWorker daemons/services.
Installing NetWorker and NMC, Page 2-1

Installing
NetWorker Server
Software

Preparing to Install EMC NetWorker
y Review the NetWorker 7.x documentation.
y Identify the host roles for your environment.
y Verify that your hosts meet the system requirements.
Before installing EMC NetWorker 7.x software, perform the tasks listed in the slide.
The following pages explain these tasks in more detail.

NetWorker 7.x Documentation
y NetWorker 7.x documentation includes:

– EMC NetWorker Release 7.3 Release Notes (UNIX/Linux, Windows)
– EMC NetWorker Release 7.3 Installation Guide (Platform-specific)
– EMC NetWorker Release 7.3 Multiplatform Version Administration Guide
y Current documentation is available at software.emc.com.
y Documentation is also available on the documentation

CD provided with the product.
Review the EMC NetWorker Release 7.3 Release Notes and the EMC NetWorker Release 7.3
Installation Guide before installing the NetWorker software.
The Release Notes contains important configuration tips, installation and upgrade notes, and the
latest software patch information. There are separate release supplements for UNIX/Linux and
for Microsoft Windows.
The Installation Guide provides step-by-step instructions for installing NetWorker. Separate
installation guides are provided for most supported UNIX operating systems and for Microsoft
Windows.
The EMC NetWorker Release 7.3 Multiplatform Version Administration Guide contains detailed
information about all aspects of NetWorker 7.3 administration.
Note: The above mentioned documentation is provided on the EMC Legato Documentation
CD provided with the product Media Kit or at software.emc.com. Also, refer to the
compatibility guides, available at software.emc.com, to check software and hardware
compatibility. There is both an EMC Legato Hardware Compatibility Guide and an
EMC Legato Software Compatibility Guide.

Identifying Host Roles
NetWorker Server
NetWorker
Server Install on this host:
Storage Node
1. The client software
2. The storage node
Node software Node
Install on this host:
1. The client software
Client 2. The storage node software Client

3. The server software
Install on this host:

Console
1. The client software On this host,
Client install only the
2. The Console server client software.
Client software
Console Server NetWorker Client
Before installing the software and configuring NetWorker, determine the appropriate host role
for each system in your environment. Four different host roles exist in a NetWorker
environment.
NetWorker Client: This is any host that has data to be backed up. These typically are the data
servers in an IT environment.
NetWorker Storage Node: This is a host that manages one or more backup devices. The
backup devices may be standalone devices or reside in an
autochanger. The backup devices may be either directly attached
to the host or controlled via a storage area network (SAN).
NetWorker Server: This host manages an entire data zone, and contains all NetWorker
configuration and tracking information.
NetWorker Management Console Server: This host provides access to all NetWorker servers
and is used for configuring, managing, and
monitoring all data zones in an enterprise.
The slide shows an example of a NetWorker environment. It also shows what software is
installed on each type of host.
Every host has NetWorker client software installed. Hosts that control backup devices also have
storage node software installed. The NetWorker server has server software installed in addition
to client and storage node software. The Console server has at least the console server software
and the NetWorker client software installed.
Verifying System Requirements
Disk Space
Platform soprano See the
See the Installation Guide for disk
Software OS space requirements for
Compatibility Disk your platform.
Guide at
Network
software.emc.com. Note: NetWorker Servers
Hostname
Resolution
require space for CFI’s,
Media DB, and Resource
Network Connectivity files.
bongo# ping soprano
Hostname Resolution
bongo# nslookup soprano
Before installing NetWorker software, verify that your system meets the following requirements.
Platform Compatibility
You can install NetWorker 7.x on any supported platform. See the EMC Legato Software
Compatibility Guide for supported OS and platforms.
Disk Space Requirements
Verify that your system has enough disk space for the software which varies in size by platform.
Note that NetWorker servers require additional disk space to store the Client File Indexes, Media
Database, and Resource Database. The amount of disk space varies based on the amount of
backed up data tracked by the NetWorker server (specifically the number of files) and the size of
the configuration.
Hostname Resolution
NetWorker hosts require that TCP/IP network name and address resolution match exactly
between hosts to assure their identity for security. DNS must properly resolve short name, long
name and reverse lookups. Host files, WINS, NIS, and NIS+ can also be used, if desired.
Additionally, TCP/IP hostnames of all Windows hosts must be identical to their Windows
computer names.
Network Connectivity
During backups and recoveries, there is considerable RPC communication between NetWorker
hosts. All hosts communicating with one another should at least be able to ping one another.
NetWorker Installation Methods
OS Installation/Uninstallation Method
AIX smitty, smit, installp
HP Tru64 setld
Solaris pkgadd, pkgrm
HP/UX swinstall, swremove
Linux rpm
IRIX swmgr, inst, tardist
Windows Microsoft Native software management tool - msiexec
setup.exe (install)
Control Panel -> Add or Remove Programs (uninstall)
See the Installation Guide for specific installation instructions for each OS.
See the UNIX manual page or Windows help (/?) for individual utility usage.
NetWorker is installed and uninstalled using native operating system utilities such as setld on
Tru64 or pkgadd/pkgrm on Solaris. Other than the utility or interface used for installation,
the process of installing NetWorker is generally the same on each operating system.

Installing NetWorker – Microsoft Windows
2
Upon executing setup.exe, a task selection window is displayed. The three selections allow
you to install NetWorker, install the Console server, or close the selection window.
NetWorker must be installed before the Console server.
The task selection window remains open during installation of both NetWorker and Console.
To close it, click Quit.
To begin the installation of NetWorker, click Install NetWorker. The InstallShield Wizard
starts and opens a Welcome to NetWorker Installation window. Click Next to continue.

Installing NetWorker – Microsoft Windows (cont.)
Default selection
3
In the Customer Information window that is opened, you can enter name and organization
information. The dotted red line in the slide simply means that this task is optional. Click Next
to continue.
The Installation Type and Location window is displayed. Using the default installation type of
Client, the host will be installed as a NetWorker client. Selecting Storage Node results in both
client and storage node software being installed on the host. In the example above, Server and
Client is selected and will result in NetWorker client, storage node, and server software being
installed.
If this host is to be configured as a Legato License Manager in addition to its NetWorker role,
click the checkbox that is provided. For more information on the license manager, see the web-
based Implementing EMC LEGATO License Manager course.
By default, all NetWorker software is installed under C:\Program Files\Legato\nsr.
This location is usually sufficient for NetWorker clients and storage nodes because the folder is
relatively small. For NetWorker servers however, since they store the media database and the
client file indexes (CFIs) which can become extremely large, the Change button can be used to
select a filesystem with sufficient free space.
Click Next to continue.
Note: For Solaris hosts, the default installation directory is /var/nsr. A symbolic link
named /nsr is automatically created and points to the actual installation directory.

6
Default
selection
5
When installing a NetWorker server, the License Agreement window opens. You must accept
the terms of the agreement or you will not be allowed to continue to the next window.
After carefully reading every single word of the license agreement, accept the terms of the
agreement and click Next.
The Ready to Install window displays a summary of the information provided up to this point. If
it is accurate, click Install. If any information is incorrect, the Back button can be used to
return to a previous window to make the appropriate correction.
Note: The License Agreement window is only displayed when installing a NetWorker server.

7
No modifications are made to the system until the Installing NetWorker window is displayed, at
which point files are automatically installed into the location previously chosen. A status bar
provides information about the installation as it proceeds.
While the software is being installed, the NetWorker Server Selection window opens. In it you
specify which NetWorker server(s) are allowed to back up this host. To select a NetWorker
server, enter its host name and click Add. For security reasons it is best not to leave the
Selected Servers field blank.
To select a NetWorker server, you can also click Update List which causes the local subnet to
be searched for all NetWorker servers. A server from the resulting list can be highlighted and
the Æ button used to add the host to the list of selected servers.
Important: The list of selected servers is placed in the file …\nsr\res\servers. If

this file contains no host names, ALL NETWORKER HOSTS are allowed to
request a backup of this host. The servers file can be manually edited. After
editing it, you must restart the NetWorker Remote Exec Service (nsrexecd)
for the change to take effect.
Click Next to close the NetWorker Server Selection window and allow the operation of the
Installing NetWorker window to continue. Upon completion of the installation, this window
closes automatically.

This window remains

open during the entire
installation and should
still be open.
Selected
by default
The host has now

been installed as a
NetWorker Server
9
Next, the NetWorker Setup Complete window opens automatically. By default, NetWorker
Change Journal Manager is configured to run when the Finish button is clicked.
Normally, NetWorker uses a file’s modification time to determine whether the file should be
backed up during level and incremental backups. The Change Journal Manager is a Microsoft
feature which keeps track of additional changes to a file, such as a file attribute change.
If you leave the box checked in the NetWorker Setup Complete window and click Finish, the
Change Journal Manager will be started, allowing you to choose which filesystems will use the
Change Journal Manager. When NetWorker performs a non-full backup on the selected
filesystems, it queries the Change Journal Manager for a list of files to back up instead of
manually traversing the filesystem to determine which files need to be backed up.
Deselecting the Change Journal checkbox and clicking Finish closes the window, leaving only
the original NetWorker task selection window open.
At this point, the host has now been installed as a NetWorker server. If the host is also going to
perform the function of the Console server, continue with installing the Console server software;
otherwise, click Quit on the NetWorker task selection window to end the installation.

Installing
NetWorker Management
Console Server
Software

Installing Console Server
2
NetWorker Management Console server, commonly referred to as “Console server” or simply

“Console”, must be installed to manage and monitor NetWorker servers. It is best to install it on
only one computer in the network to take full advantage of the Console’s consolidated reporting
feature.
Console server can be installed on any host on which the NetWorker 7.3 (or later) version of the
client software has been installed, including a storage node or NetWorker server.
Since a NetWorker 7.3 server has just been installed, click Install NetWorker Management
Console to install the Console server software.
A welcome window appears. Click Next to continue.

Installing Console Server (cont.)
If JRE is not installed, it

can be installed after
this window.
4
3
The Customer Information window is displayed. This is identical to the one displayed during the
NetWorker installation. Enter your name and organization, if desired, and click Next. The
Product Setup window appears.
At this point in the setup, if the Java Runtime Environment version 1.4.2 (JRE 1.4.2) is not
installed, another window is displayed, asking if you want to install the software. This window
is not shown above, but will be discussed shortly.
By default, Console software is installed in C:\Program Files\Legato\Management.
Thus, it is at the same level in the filesystem hierarchy as the NetWorker nsr directory. To
specify a different installation directory, click Change. Console software does not have to be
installed in the same location as the NetWorker software.
GST stands for Generic Services Toolkit. The GST Server software manages all the Console
functionality. As discussed in the overview chapter, the EMC Legato GST Service is
responsible for starting the three daemon processes associated with the Console server, gstd,
gsttclsh, and dbsrv9.
Click Next after deciding on the installation directory.
Note: On a Solaris host, the default installation directory for the Console software is
/opt. During installation, a LGTOnmc directory is created under this directory.

6
In the previous window, you specified the directory in which to install the Console software. In
the Configuration Options window you specify the location of the Console server database. Use
the Change button to select a directory other than ...\Management\lgto_gstdb. The
Console database does not have to be placed in the same directory as the Console software,
although that is the default location.
In this window, you can also change the RPC port numbers used by the Console web server
(gsttclsh) and the master Console server process (gstd). These ports are 9000 and 9001,
respectively, and should not be changed unless there is sufficient cause, such as another process
already using one or both of the ports.
Clicking Next will open a summary window entitled Product Configuration. Verify that all
information is accurate and click Next to continue with the installation. Click Back to return to a
previous screen to make changes.
Note: On a Solaris host, the Console server database is installed in /lgto_gstdb by default.
This location can be changed.

7
After all the necessary information is entered, click Install in the Ready to Install the Program
window to commence installation of the Console server software.
When installation of the software starts, a window entitled Installing NetWorker Management
Console opens. A status bar provides information about the installation as it proceeds.

10
9
Upon successful installation of the software, the Installing NetWorker Management Console
window closes and the final window, NetWorker Management Console Setup Completed,
appears.
As a final step, if you leave the check box selected and click Finish, a connection is made to the
Console server via your default browser.

Java Runtime Environment
y Required on Console
server to support
command-line reporting.
y Installed as part of the
Console installation on
Microsoft Windows.
y JRE 1.5 or newer IS
NOT supported.
During installation of the Console server, the installation program checks whether a supported
version of the Java Runtime Environment (JRE) is already installed on the host. If it is not
installed, you are asked if you want it installed. A supported version of JRE comes bundled as
part of the EMC NetWorker Management Console software.
If you select the option to have JRE installed (as shown in the slide), JRE will be automatically
installed and then the Console server installation continues.
Note: It is not required that JRE be installed on the Console server. It is only required to
generate reports from the command-line.

Accessing the Console Server

Data Zone Data Zone
leg-win1
Server Server
NMC Server
Node Node
Client
Client Client Client Client Client Client
Console Client Console Client

y Internet Explorer / Netscape Windows UNIX y Netscape / Mozilla
y Java Runtime Environment y Java Runtime Environment
Using a supported web browser, you can access the Console server from any host running a
supported operating system. The supported operating systems and browsers are listed on the
following page.
The URL (Uniform Resource Locator) used to connect to the Console server is:
http://console_server:9000
console_server is the host name of the console server. Port 9000 on the Console server is
where the gsttclsh process is listening.
The host on which the browser is run is called the Console Client. Although the Console client
is commonly a NetWorker host or the Console server itself, it does not have to be.
A supported version of JRE must be installed on the Console client. During the initial HTTP
connection to the Console server, if it is determined that the Console client does not have an
appropriate version of JRE installed, you will be notified and given the opportunity to have a
JRE automatically downloaded from the Console server and installed on the Console client.
Note: On some UNIX platforms, when connecting to the Console server, you may receive an
error message stating that a supported version of JRE is not installed, even when a
supported version is installed. To avoid the problem, append /gconsole.jnlp to
the URL specified above:
http://console_server:9000/gconsole.jnlp

NMC Client – Platform and Browser Requirements
The table above shows the operating systems and web browsers required for a Console client.
Additionally, JRE 1.4.2 or newer is required, although JRE 1.5 is not supported.

NetWorker and Console Installation - UNIX
To install a NetWorker client:

y LGTOclnt, LGTOman
To install a NetWorker storage

node:
y LGTOclnt, LGTOman, LGTOnode
To install a NetWorker server:

y LGTOclnt, LGTOman,
LGTOnode, LGTOserv
Solaris
To install a Console server: Example
1. JRE 1.4.2 (optional)
2. LGTOclnt, LGTOman, LGTOnmc
There are installation guides specific to each supported UNIX/Linux operating system, which
provide the details for installing NetWorker and NMC.
The slide shows the EMC NetWorker software packages available for installation on a Solaris
host. To install NetWorker, run pkgadd and specify the number(s) corresponding to the
packages to be installed.
When installing a Console server, if you want to be able to generate reports from the command
line, install the JRE software before installing the NetWorker software. JRE is installed by
executing the shell archive script (“shar” file) provided with the NetWorker software.
Executing the shell archive results in JRE being installed in a subdirectory of the current
directory. You will be asked to supply this pathname during installation of the Console server
software (LGTOnmc). Following the JRE installation, pkgadd is used to install the NMC
server software.
Note: Installation of the manual pages (LGTOman) is optional for all UNIX NetWorker and
NMC hosts.

Stopping and Starting

NetWorker
and
NMC Server
Processes

Verifying the Installation - Files
Default directory
Default directory
Windows Default directory
Solaris
To verify the NetWorker and Console installations, go to the installation directory and verify its
contents.
In Windows, the default installation directory is C:\Program Files\Legato. This
directory contains both binaries and NetWorker databases. Shown above, the Management and
nsr subdirectories exist and have appropriate contents.
In Solaris, the default installation directory is /var/nsr. A symbolic link, /nsr, is created,
pointing to the actual installation directory. Thus, you can always go to /nsr to access the
NetWorker files.
In Solaris, the pkginfo command is also useful in verifying the success of the installation.

Verifying the Installation - Processes
Console Server
Windows
NetWorker Server
Solaris
During a Windows installation, NetWorker and Console server processes are started
automatically. The Windows Task Manager can be used to verify they are running.
On most UNIX platforms, starting the processes during installation is optional. You can use a
command such as ps, prstat, or top to verify the appropriate daemon processes are running.

Starting and Stopping NetWorker – MS Windows
You should stop the NetWorker server

and Console server services when
stopping the NetWorker client service.
Conversely, starting the service of
either server will automatically start
the NetWorker Remote Exec Service.
To start the NetWorker services on a Windows NetWorker server:

1. Start the NetWorker Remote Exec Service (nsrexecd).
2. Start the NetWorker Backup and Recover Server (nsrd, nsrmmdbd, nsrindexd,
nsrmmd, nsrjobd).
3. Start the NetWorker Power Monitor (if applicable) (nsrpm).
To stop the NetWorker services:
1. Stop the NetWorker Remote Exec Service. Since the NetWorker Backup and Recover
Server and EMC Legato GST Service are dependent services, Windows will ask if you
also want to stop these services.
2. Click Yes to stop both services.
3. If desired, stop the NetWorker Power Monitor service and/or the NetWorker Host
Agent service.
To start the Console server service:
1. Start the NetWorker Remote Exec Service (nsrexecd).
2. Start the EMC Legato GST Service (gstd, gsttclsh, dbsrv9).

Starting and Stopping NetWorker – UNIX

y To start the NetWorker daemons: Solaris example
# /etc/init.d/networker start
OR
# nsrexecd
# nsrd (Only on a NetWorker server)
y To stop all NetWorker processes:

# nsr_shutdown
OR
# /etc/init.d/networker stop
y To start/stop Console daemons:

# /etc/init.d/gst start OR # gstd
# /etc/init.d/gst stop
In most flavors of UNIX, system processes are started via run-control scripts executed at system
startup. When installing a NetWorker host, a run-control script named networker is installed
in the appropriate system directory, usually a subdirectory of /etc.
The networker script can be executed manually, using a start argument, to start the
NetWorker daemons. When the stop argument is used, all NetWorker daemons, as well as any
other running NetWorker processes, are stopped.
The NetWorker installation process installs a program named nsr_shutdown on all UNIX
hosts. It is the recommended method of gracefully shutting down all NetWorker processes.
When the Console server is installed on a UNIX host, a run-control script named gst is placed
in the same location as the networker script. Use an argument of start to start the Console
server daemons and an argument of stop to stop the Console server daemons.

NetWorker 7.3 nsr_shutdown Functionality

y The 7.3 nsr_shutdown makes use of run files to determine
which processes to shut down and in what order they need to
be shut down.
y Run files are created under /nsr/run by each NetWorker
service or parent process: nsrd, nsrexecd, savegrp, etc.
y Three pieces of information are gathered from a run file:
– The process name. e.g. - nsrexecd
– The process ID of the process
/nsr/run/nsrexecd.12345
– Prerequisite processes to shut down.
nsrd
savegrp
Example run file
Prior to NetWorker 7.3, nsr_shutdown sent SIGTERM signals to a hard-coded list of

NetWorker processes. If a process failed to terminate, nsr_shutdown would wait 5 seconds
and then issue another SIGTERM signal. It would send up to ten SIGTERM signals before
finally issuing a SIGKILL signal to all remaining NetWorker processes.
In NetWorker 7.3, nsr_shutdown uses run files, located in /nsr/run, to determine what
NetWorker processes should be terminated and in what order they should be brought down.
The name of a run file specifies a process name and process ID (PID). The contents of a run file
is a list of processes to be terminated before terminating the process referred to by the file name.
For example, in the slide, before terminating the nsrexecd process, which has a PID of 12345,
nsr_shutdown will terminate the nsrd and savegrp processes.
Note: If the run files are accidentally removed, nsr_shutdown will not be able to shut
down NetWorker, and it will be necessary to use a UNIX utility such as kill or
pkill to terminate the processes manually.

nsr_shutdown – NetWorker 7.3 Syntax
nsr_shutdown [ -flq ] [ -t timeout ] [ process … ]
Option Description
Force shut down using SIGKILL after attempting
-f
graceful shutdown for 120 seconds (default).
List currently running NetWorker daemons and
-l
their children.
-q Shut down quietly without diagnostic messages.
Attempt to gracefully shut down all listed
-t timeout NetWorker processes for timeout seconds instead
of the default 120 seconds.
The slides describes several of the options available with the NetWorker 7.3 nsr_shutdown
command.
nsr_shutdown is also able to shut down individual processes:
# nsr_shutdown savegrp
# nsr_shutdown nsrd

Removing NetWorker Software

NetWorker Host
<…\nsr>
Server
index res mm bin logs ... tmp
Node
Client
bongo
Partial Uninstall:
Removes software only:
executables, libraries, etc …
Complete Uninstall: Check this box for a

Removes software and NetWorker complete uninstall
Control Data (…\nsr)
On a Windows host, use Add or Remove Programs from the Control Panel to remove
NetWorker and NetWorker Management Console software.
On a UNIX host, use the operating system’s software removal utility, such as pkgrm in Solaris,
to remove the software.
In either case, the default behavior during removal is to perform a partial uninstall. This leaves
the NetWorker control data installed. To perform a complete uninstall on a Windows host,
check the appropriate check box, as shown above. On a UNIX host, the directory containing the
NetWorker control data must be manually removed using a utility such as rm. Remember to
remove the symbolic link /nsr.
Important: Updating NetWorker software to a newer release normally requires a partial

uninstall followed by the installation of the new software. This results in the
resource information, media database, and client file indexes being retained.
When performing a software update, always read the Installation Guide to
determine what method of software removal is required.

Console Client – Installing JRE
A 1.4.2 or newer release of the Java Runtime Environment must be installed on the Console
client. When connecting to the Console server via the Console client’s web browser, you are
notified if an appropriate version of JRE is not installed.
During a Windows installation, you are presented with a link that when clicked will
automatically download the JRE software from the Console server to the Console client and
initiate an installation procedure. After installation, you must close and restart the browser.
During a UNIX installation, you are presented with a link that allows you to download a JRE
shell archive to a local directory. After downloading the archive, exit the browser and install
JRE. You may be asked to perform additional installation steps; these will be explained in the
browser window. After installing JRE, close and restart the browser.

Updating the Administrator List: nsraddadmin

nsraddadmin –u “user=username,host=hostname”
This is a NetWorker server
The Console server is running

Microsoft Windows
y Run on NetWorker server

y Grants a user on the Console server permission to
administer NetWorker (modify resources, label volumes, etc.)
y For a UNIX Console server:
– Specify the root user and the Console administrator user
y For a Windows Console server:
– Specify the SYSTEM user and the Console administrator user
New in NetWorker 7.3, the nsraddadmin command is run on the NetWorker server to give a
user on the Console server the required privileges to administer NetWorker. Until this command is
executed, the Console server can only be used to view the NetWorker configuration; you cannot
change anything.
For a UNIX Console server, you must grant privileges to both the root user (owner of the gstd
process) and one or more Console servers accounts. Initially the administrator user account is the
only user account configured on the Console server. To grant administrative privileges, execute
the following commands on the NetWorker server.
nsraddadmin –u “user=root, host=console_server”
nsraddadmin –u “user=administrator,host=console_server”
“console_server” is the host name of the Console server.
For a Windows Console server, you must grant privileges to both the SYSTEM user (owner of the
gstd service) and the Console server’s administrator account.
nsraddadmin –u “user=SYSTEM, host=console_server”
nsraddadmin –u “user=administrator, host=console_server”
Note: nsraddadmin updates the Administrators attribute of the NetWorker Server resource
which is discussed in Chapter 11, Configuring the NetWorker Server.
If the NetWorker server is also the Console server, the necessary entries are
automatically added to the Administrators list when the Console server software is
installed.
Lab 2-1
Lab 2-1: Install a NetWorker Server and a

Console Server

Chapter 2 - Summary
In this chapter you learned how to:

y Prepare to install EMC NetWorker
y Describe the NetWorker installation process
y Install the NetWorker software
y Install NetWorker Management Console
y Verify successful installation
y Start and stop the NetWorker daemons/services
These are the key points covered in this chapter. Please take a moment to review them.

9 Check Your Knowledge – Part 1

1. What are three system requirements that you should
verify before installing NetWorker software.
2. When installing the NetWorker server software, what

other NetWorker software should be installed first?
3. During the installation of which piece of NetWorker
software are you asked for the location of /nsr?
4. What are two things that can be done to verify
successful installation of NetWorker?
5. What NetWorker software must be installed on a
Console server?

9 Check Your Knowledge – Part 2

6. Which release(s) of the Java Runtime Environment are
supported on the Console server?
7. How is the JRE installation performed on a Console
client?
8. What is the default port used by the Console web
server, gsttclsh?
9. Describe the difference between a partial and a
complete uninstall.
10. What file contains a list of NetWorker servers allowed
to back up a NetWorker client? On what host is this file
located?

Chapter 02 - Installing NetWorker and NMC

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Chapter 02 - Installing NetWorker and NMC

Diunggah oleh

Hak Cipta:

Format Tersedia

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.

Chapter 2 – Installing NetWorker and NMC

Upon completion of this chapter, you will be able to:

Installing NetWorker and NMC, Page 2-1

Installing NetWorker and NMC, Page 2-2

Preparing to Install EMC NetWorker

y Review the NetWorker 7.x documentation.

y Identify the host roles for your environment.

y Verify that your hosts meet the system requirements.

Installing NetWorker and NMC, Page 2-3

NetWorker 7.x Documentation

y NetWorker 7.x documentation includes:

y Current documentation is available at software.emc.com.

y Documentation is also available on the documentation

Installing NetWorker and NMC, Page 2-4

Identifying Host Roles

Client 2. The storage node software Client

Install on this host:

Console Server NetWorker Client

Verifying System Requirements

NetWorker Installation Methods

Installing NetWorker and NMC, Page 2-7

Installing NetWorker – Microsoft Windows

Installing NetWorker and NMC, Page 2-8

Installing NetWorker – Microsoft Windows (cont.)

Installing NetWorker and NMC, Page 2-9

Installing NetWorker – Microsoft Windows (cont.)

Installing NetWorker and NMC, Page 2-10

Installing NetWorker – Microsoft Windows (cont.)

Important: The list of selected servers is placed in the file …\nsr\res\servers. If

Installing NetWorker and NMC, Page 2-11

Installing NetWorker – Microsoft Windows (cont.)

This window remains

The host has now

Installing NetWorker and NMC, Page 2-12

Installing NetWorker and NMC, Page 2-13

Installing Console Server

NetWorker Management Console server, commonly referred to as “Console server” or simply

Installing NetWorker and NMC, Page 2-14

Installing Console Server (cont.)

If JRE is not installed, it

Installing NetWorker and NMC, Page 2-15

Installing Console Server (cont.)

Installing NetWorker and NMC, Page 2-16

Installing Console Server (cont.)

Installing NetWorker and NMC, Page 2-17

Installing Console Server (cont.)

Installing NetWorker and NMC, Page 2-18

Java Runtime Environment

Installing NetWorker and NMC, Page 2-19

Accessing the Console Server

Console Client Console Client

Installing NetWorker and NMC, Page 2-20

NMC Client – Platform and Browser Requirements

Installing NetWorker and NMC, Page 2-21

NetWorker and Console Installation - UNIX

To install a NetWorker client:

To install a NetWorker storage

To install a NetWorker server:

Installing NetWorker and NMC, Page 2-22

Stopping and Starting

Installing NetWorker and NMC, Page 2-23

Verifying the Installation - Files