Lab Guide
Lab Guide
Month 2013
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC
Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge,
AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated
Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip,
Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON,
ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence,
Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct Matrix Architecture,
DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer,
EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony,
Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover,
Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor,
MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath,
PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo,
SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF,
StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX,
TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual
Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist,
WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and where information lives, are registered
trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
© Copyright 2013 EMC Corporation. All rights reserved. Published in the USA.
LAB EXERCISE 2-1: INSTALL NETWORKER AND NMC SOFTWARE ON LINUX ............................14
LAB EXERCISE 2-2: INSTALL NETWORKER AND NMC SOFTWARE ON WINDOWS ....................21
LAB EXERCISE 2-3: INSTALL NETWORKER CLIENT SOFTWARE ON WINDOWS..........................26
LAB EXERCISE 3-1: CONNECT TO THE CONSOLE SERVER FROM THE WINDOWS HOST ...............30
LAB EXERCISE 3-2: CUSTOMIZE THE NETWORKER MANAGEMENT CONSOLE SERVER ...............32
LAB 7: MANAGE THE MEDIA DATABASE AND CLIENT FILE INDEXES ...................... 99
LAB EXERCISE 13-1: RECOVER THE BOOTSTRAP AND CFI SAVE SETS.................................. 150
Purpose: The lab exercises contained in this guide give you an opportunity to
reinforce the information you are learning in the course. The lab
exercises are designed to be run in a test lab environment on the
NetWorker training lab system as described below. Some of the lab
exercises may make changes to the system. For this reason, do not
attempt to run the lab exercises on a production system.
Lab Environment: You will be using a Virtual Data Center (VDC) environment in Lab
Manager to perform the EMC NetWorker Installation, Configuration
and Administration course lab exercises.
Each student works in their own VDC configuration, accessed with an
assigned VDC/Lab Manager username and password. The NetWorker
Installation, Configuration and Administration Lab Manager
configuration consists of these 5 virtual machines:
nwwindows - This will be your primary Windows workstation for
the labs.
nwlinux – This is your Linux host for the labs.
dc - This is a domain controller and DNS for your configuration.
winclient – This will be your Windows client.
vtl – Virtual Tape Library
Additionally there is a physical Data Domain system that will be used
for some labs. The username and login information for this system
will be provided in the labs that require it.
Important The labs contain tasks and the solutions to those tasks. Many
screenshots are presented which contain information showing how to
perform a task. However, the actual information in the screenshot
may or may not exactly reflect your particular lab environment. Thus,
you should not simply type what you see in a screenshot and
assume that it will work. Always consider the task that is being
performed and determine for your lab environment whether the
steps shown to perform the task are applicable.
Step Action
1 Follow these steps to log into the EMC NetWorker ICA VDC lab environment.
Log in to a Windows classroom computer with the login information provided by your instructor.
3 Log in to the Virtual Data Center with the user name and password provided to you by the
instructor.
6 At the Lab Manager login screen, enter the Lab Manager Login User name and Password assigned
to you by your instructor. Then, click Login.
7 You will be working in the NetWorker 8.1 ICA configuration for all the labs for this course. To get
your own personal copy of the configuration, clone the configuration to your Lab Manager
workspace.
In the left pane of the Lab Manager screen, click Library. Next, right-click the NetWorker 8.1 ICA
configuration and select Clone to Workspace.
Result: When the clone operation completes, you see a clone copy of the NetWorker 8.1 ICA lab
configuration in your workspace on the right side of the screen with 5 small console windows as
shown here. The status of each window and the configuration is Undeployed.
10 To be able to use the configuration, it must first be deployed. Highlight the Clone (1) of
NetWorker 8.1 ICA configuration and select Deploy with defaults.
11 After the status of the configuration changes to Deployed, highlight the arrow next to the Clone (1)
of NetWorker 8.1 ICA configuration and select Show Consoles.
12 Alternatively, to see just one console window at a time, click in the small console view of the virtual
machine that you want to work in.
Result: Only the console window for that machine is displayed for you to work on that machine.
When you wish to work on another virtual machine, click Configuration in the upper left of the
screen and choose another virtual machine console. You can also view a console with Remote
Desktop by clicking the Remote Desktop button.
Note: For best performance, it is recommended that you perform all labs from a remote desktop
session on the nwwindows.emc.edu server. From there you can log in to all other servers.
14 To work on a virtual machine, click inside its console window, or for best performance launch a
Remote Desktop session.
15 To send a Ctrl-Alt-Delete sequence to one of the Windows machines if using the console, right-click
or mouse over the arrow next to the machine name in the tab and select Ctrl-Alt-Delete.
16 When prompted to log onto or unlock a Windows virtual machine (nwwindows or winclient), enter
the following information in the login screen:
User name: Administrator
Password: student
17 When prompted to log onto or unlock the Linux virtual machine (nwlinux), best performance can
be achieved by initiating a putty session from the nwwindows server. Alternatively you can click in
the console window for the machine and enter the following information:
User name: root
Password: student
18 To bring up a terminal window on the nwlinux host, right-click the Terminal icon and select Open.
19 You can access the Linux host from the Windows host nwwindows with PuTTY for command line
access or with remote desktop for GUI access.
21 When you are finished with your Lab Manager configuration for the day, just logout of Lab
Manager. (There's no need to undeploy the virtual machines until you are finished with all the labs
at the end of the class.)
To log out of Lab Manager, click Logout in the upper right corner of the Lab Manager screen.
Purpose: In this lab you install NetWorker Server and NetWorker Management Console
software on either nwwindows or nwlinux. This host will be used for
configuration and administration of NetWorker during the remainder of the
class. You then configure the host you didn’t choose (either nwwindows or
nwlinux) as a NetWorker storage node. The storage node will be used in a
later lab. In the last section of this lab, you install NetWorker client software
on the Windows client, winclient.
Lab Environment: In the Virtual Data Center (VDC) environment, two host computers in the VDC
are assigned to you as potential NetWorker servers: one is a Linux host
(nwlinux) and the other is a Windows 2008 system (nwwindows). You decide
which host to use as the NetWorker and Console server. This host is referred
to as Host A in the diagram. The other host will be a remote storage node.
This host is referred to as Host B in the diagram.
NetWorker
Server
Storage Storage
Robotics Node Node Robotics
NetWorker
Client Mgmt Client
Console Srv
Host A Host B
You decide: If your Windows host, nwwindows, is Host A, then your Linux
host, nwlinux, is Host B. If your Linux host, nwlinux, is Host A, then your
Windows host, nwwindows, is Host B.
Lab 2 Instructions: If you decide to install the NetWorker Server and NetWorker Management
Console on the Linux host, nwlinux, perform Lab 2-1.
If you decide to install the NetWorker Server and NetWorker Management
Console on the Windows host, nwwindows, perform Lab 2-2.
Purpose: In this lab you install the NetWorker server and NetWorker Management
Console server software on the Linux host, nwlinux. This host will be used
for configuration and administration of NetWorker during the remainder of
the class. You configure your Windows host, nwwindows, as a client and
remote NetWorker storage node. The storage node is used in a later lab.
Lab Environment:
NetWorker
Server
Storage Storage
Robotics Node Node Robotics
NetWorker
Client Mgmt Client
Console Srv
Linux Windows
Step Action
1 Open a remote desktop session and log in to the Windows host, nwwindows with user
administrator password student. Then, open a PuTTY session to nwlinux using the PuTTY icon on
the desktop.
2 Change directory to the location of the EMC NetWorker software. Unzip and untar the software
file.
Result: The directory /software/linux_x86_64 contains the rpm files for the Linux
installation.
3 To install the NetWorker server, install the following rpm files in this order:
4 To install the man pages and the NetWorker Management Console software on this machine,
install the following rpm files:
lgtoman, lgtonmc
In the terminal type:
rpm -ivh lgtoman* lgtonmc*
5 To complete the NetWorker Management Console installation, run the nmc_config script.
Accept all default values.
6 After all the specified packages are successfully installed, start all the NetWorker processes.
/etc/init.d/networker start
/etc/init.d/gst start
7
During installation of the NetWorker server software, several entries are appended to
/etc/syslog.conf. Send a HUP signal to syslogd so that it will reread its configuration file.
Step Action
1
Verify that all the required NetWorker and Console server processes are running:
nsrd nsrexecd
nsrmmdbd gstd
nsrindexd httpd
nsrjobd dbsrv12
2 Stop all the NetWorker daemons. Verify they are no longer running.
nsr_shutdown
ps -ef | grep nsr
/etc/init.d/networker start
4 Stop all the Console server daemons and verify they are no longer running.
/etc/init.d/gst stop
ps -eaf | egrep 'gst|dbsrv|httpd'
6 Change directory to /opt. You should see the directory containing the Console server software,
lgtonmc.
cd /opt
ls -al
Change directory to the location of the Console server database lgto_gstdb and list the
contents.
cd /opt/lgtonmc/lgto_gstdb
ls -al
Change directory to /nsr and list the contents. Among the other NetWorker directories, you
should see the directories for the NetWorker control data: index, mm and res.
cd /nsr
ls -al
In this lab, you install the NetWorker storage node software on the nwwindows machine.
Step Action
1 If not already there, log in to the Windows host, nwwindows.emc.edu, using the administrator
account, password student if you have not already done so.
In the Internet Explorer window that opens, click Install EMC NetWorker 8.1 Software
4 Install NetWorker, providing all the information specified below when prompted:
1. Click Run to run the software; click Run again.
2. Select a language for the installation.
3. Do NOT configure the Windows firewall.
4. Install Storage Node software. This also installs the client software.
5. Use the default installation directory.
6. When prompted for NetWorker servers that are allowed to back up your host, do not
specify any.
Warning: This is insecure but avoids possible backup failures in later Lab Exercises!
7. Do not run the Change Journal Manager after installation (uncheck the option).
5 Close the Thank you for selecting EMC NetWorker Internet Explorer window.
Go to Lab 2-3
Purpose: In this lab you install the NetWorker server and NetWorker Management
Console server software on the Windows host, nwwindows. This host is
used for configuration and administration of NetWorker during the
remainder of the class. You will configure your Linux host, nwlinux, as a
remote NetWorker storage node. The storage node is used in a later lab.
Lab Environment:
NetWorker
Server
Storage Storage
Robotics Node Node Robotics
NetWorker
Client Mgmt Client
Console Srv
Windows Linux
Step Action
1 Log in to the Windows host, nwwindows, using the administrator account, password student.
2
Browse to the C:\software\nw81_win_x64\win_x64 folder.
4 Use the following information for the NetWorker Management Console part of the installation:
Use the default installation directories.
Use the default port numbers for the Web Server and the Client Service.
Do not launch the Console client after installation (uncheck the option).
5 Do NOT run the Change Journal Manager after NetWorker server installation.
Step Action
1 On nwwindows, open the Services window and verify that the following services are running:
NetWorker Backup and Recover Server
NetWorker Remote Exec Service
EMC GST Service
EMC GST Web Service
Note: Services are viewed using Start > All Programs > Administrative Tools >Services, or by typing
services.msc in the Start > Run box.
2 Right-click the NetWorker Remote Exec Service and select Stop from the menu.
Note that the other services depend on this service and therefore will be stopped as well.
Right-click NetWorker Remote Exec Service and select Start from the menu.
Right-click NetWorker Backup and Recover Server and select Start.
Right-click EMC GST Service and select Start.
4 Open the Task Manager and verify that all required NetWorker and Console processes are running.
Right-click the task bar at the bottom of the screen, select Task Manager and go to the Processes
tab. Check the box at the bottom of the window entitled Show processes from all users.
Dbsrv12
gstd
httpd
nsrd
nsrexecd
nsrindexd
nsrjobd
nsrlogd
nsrmmdbd
nsrsnmd
Step Action
1 Log in to the Linux host, nwlinux, via the PuTTY link on the desktop with the following:
Username: Root
Password: Student
Type:
cd /software
tar xzvf nw81_linux*
cd linux_x86_64
Result: The directory /software/linux_x86_64 contains the rpm files for the Linux
installation.
3 To install the NetWorker storage node, the following rpm files must be installed in the following
order:
Purpose: In this lab you install NetWorker client software on your Windows client
machine, winclient.
Step Action
1 Start a remote desktop session using the link on the desktop and log in to the Windows host,
winclient.emc.edu using the following:
Username: Administrator
Password: Student
Install NetWorker, providing all the information specified below when prompted:
5 Enter the server names of the servers you selected for each client:
<Networker_Server> ____________________________________
<Storage_Node> ___________________________________
<Client> _____________________________________
End of Lab 2
Note: For all of the labs in this course you will be connecting to the console server from the Windows server,
nwwindows.
Step Action
From nwwindows, connect to the Console server by opening Internet Explorer on that host and
browsing to the following URL:
http://console_server:9000
Replace console_server with the host name of your Console server, either nwlinux.emc.edu or
nwwindows.emc.edu.
2 Click Start to launch the Console client. Answer yes to any security questions.
The first time you log in to NetWorker Management Console, the Console Configuration Wizard
starts.
It will be used in the next lab to initially configure portions of your NetWorker environment.
Note: Whenever the Console server is used in the remaining labs for this course, start it from the
Windows host, nwwindows.emc.edu.
Step Action
1 The first time you log in to the NetWorker Management Console, the Console Configuration
Wizard starts and displays a welcome screen.
Note: If the wizard is not currently running, start it from the Console Setup window. Select Setup >
Configuration Wizard. Also, the wizard can be rerun at any time.
Click Next.
2 Set the password for the NetWorker Administrator user account to: networker
Confirm the password.
Click Next.
3 Specify the fully qualified name of your NetWorker server in the NetWorker Server field.
Note: Ensure that the client name matches the NetWorker Server name exactly and that the FQDN
is used for both.
Click Next.
4 Enter the FQDN of your NetWorker server in the NetWorker Servers field.
5 The NetWorker Management Console interface is opened and the Getting Started window is
displayed.
Uncheck the box at the bottom of the window so that this window is not displayed every time the
Console interface is started.
6 The NetWorker Console window is displayed with the Enterprise button open.
7 In the Console Enterprise window, click the name of your NetWorker server (either nwwindows or
nwlinux) in the left pane. Then, click Launch NetWorker Administration.
You can also right-click NetWorker in the right pane and select Launch Application.
Note: Diagnostic mode is needed to see many of the NetWorker resource attributes that we will
be using in the following labs.
From the Console Setup tab, select System Options from the Setup pull-down menu.
Purpose: In this lab, you perform various backups of the NetWorker client,
winclient.emc.edu.
Step Action
1 Start NetWorker Administration from a remote desktop session to the nwwindows.emc.edu host.
2 A pool is a NetWorker resource that represents a set of volumes. To separate our disk backup data
from data stored on other media later in the course, we’ll create a pool for our disk devices.
From the Media tab, right-click Media Pools in the left pane and select New.
3 Type Disk1 for Name. Leave the Label template field blank and check Default for Groups.
Click OK. An error box displays telling you that no label template was selected. Click OK to
acknowledge the error box, and click OK again on the Media Pool Creation window again. This
automatically creates and applies a label template with the same name of the Media Pool.
4 Create a resource for the Windows host, winclient, using the Client Backup Configuration wizard.
From the Configuration tab, right-click Clients in the left pane and select New Client Wizard.
6 An AFTD is a NetWorker disk device that supports concurrent backup and restore operations. An
AFTD uses a directory within a file system as its volume. We will label this device into the pool,
Disk1. A directory on the NetWorker server has already been created for you to use for the AFTD.
From the Devices tab, right-click Devices in the left pane and select New Device Wizard.
Click Next.
Select Next, and accept all default settings to use the NetWorker server as the storage node.
9 On the Select Device Path screen select the folder to use based on which server you chose as your
NetWorker server:
Use default values for the other attributes, clicking next to continue.
Step Action
1 Change the Save set attribute of the client resources to prevent the entire disks from being backed
up. Change only the client resources that currently have a save set of All.
From NetWorker Administration on nwwindows.emc.edu, open the Configuration tab and highlight
the Clients node in the left pane.
Right-click your NetWorker server in the Clients list and click Modify Client Properties.
Note: Make sure to select the NetWorker server's client resource that has a save set of All.
2 For the Save set attribute, replace All with the following save set by typing it in the Save Set
window.
3 Modify the save set attribute for winclient.emc.edu. Right-click winclient.emc.edu in the Clients list
and click Modify Client Properties.
For the Save set attribute, replace All with the following save sets:
Winclient
C:\WUTemp\inf
C:\WUTemp\Common Files
C:\WUTemp\Java
Note: Ensure that you have three separate save sets listed. If using the save set browse wizard, it
may consolidate the save sets to just C:\WUTemp if all subfolders are selected. If this happens
change the save set to ensure you have three separate save sets listed.
4 You should now see the client resources with the modified Save set attributes.
Note: Do NOT use, copy, or modify the NetWorker client resource with “NMCASA” in the save set
name until specifically directed to do so in later labs.
6 From the Monitoring tab, right-click the Default group and select Start, to start a backup of the
Default group.
7 Review the save group details for the Default group after the backup has completed.
8 Perform another backup of the Default group and abort the group after at least one of the save set
finishes. Use Show Details to determine the save set status.
To stop the group, use the same menu used to start the group.
9 Double-click the group to view the details of the group and verify that not all save sets were backed
up successfully.
10 Right-click the Default group and select Restart. When prompted select yes and allow the group to
complete.
11 Right-click the group and select Show Details to verify that the group completed successfully.
Note: Only the save sets that had not completed successfully when the group was stopped were run.
Save sets that had already completed prior to stopping the group were not rerun.
Step Action
At the command prompt, run savegrp –p Default for a preview of the backup of the Default
group.
Note: Group names are case sensitive.
2 Next use the savegrp command to perform a full backup of the Default group.
Note: While the backup is running, you can monitor it from the Monitoring window of the
NetWorker Administration console. Additionally, you can add a –v to the savegerp command to
increase the level of verbosity.
Step Action
1 Configure all the resources needed to perform the backups requested in the following scenario as
detailed in the next pages.
2 Perform a backup of all groups using any method you want. Monitor their progress and verify they
finish without error. If any problem occurs, attempt to diagnose and correct the problem, and
perform a restart of the group(s) that failed.
3 Verify that all groups have their Autostart attribute set to Enabled so they will back up
automatically during the remainder of the week.
You will be backing up two hosts. The first host will be your NetWorker server. You will have two client resources
for this host, in addition to the client resource with the NMC save set. You will modify the existing client resource
for your NetWorker server. The second host will be your Windows client (winclient.emc.edu).
Finally, a third client resource will be created for your NetWorker storage node.
Using the following backup requirements, create or modify resources to configure the data zone. Before actually
doing the configuration, use Table 4-4 on the following page to summarize all the resources that need to be
created/configured.
Client
Name
Save sets
Group
Schedule
Browse
Policy
Retention
Policy
Save sets
C:\WUTemp
C:\Program Files\EMC
C:\WINDOWS\Help /etc
(Windows NW NetWorker
Server)
Save sets
Schedule Full on Monday *** Full on 1st and 15th *** Full on 3rd Friday ***
( '***' - designates a resource that must be created prior to configuring the client resource)
Action
All resources are configured using the Configuration and Media tabs in the NetWorker Administration interface.
Note: The names listed below for groups, schedules, and policies were selected as representative names for the
resources. You may choose different names if you desire, however, it is important that you remember which of
your chosen names relate to the names used in the labs. The lab guide will always reference the resources by the
representative names below.
Group: NSRBackup
From the Configuration tab right-click Groups in the left pane and select New.
Create Group window > Setup tab:
Name: NSRBackup
Start time: 9:00
Autostart: Enabled
Group: 11PM
Right-click Groups in the left pane and select New.
Create Group window > Setup tab:
Name: 11PM
Start time: 23:00
Autostart: Enabled
Pool: Disk1
From the Media tab, select Media Pools and double-click the Disk1 pool to open its properties.
In the Data Source field, select the two newly created groups so that all groups are selected for this pool.
Click OK.
Click OK.
Click OK.
From the list of schedules, right-click your newly created schedule and uncheck the option show schedule as
calendar
Right-click Full on 3rd Friday schedule and select properties to make the following changes:
Schedule Properties window:
Action: incr incr incr incr 1 incr incr
Override: full third Friday every month
Click OK.
Note: The method for schedule creation shown in this step is particularly useful for the creation of complex
schedules that need to repeat over consecutive years. Any option supported by nsr_get_date can be used in the
override section
Click OK.
Click OK.
Click OK.
Click Create.
Step Action
1 Backups run manually from the NetWorker client are considered a level M or Manual level backup
and are treated differently than scheduled backups.
To ensure these backups go to a pool other than Default, a new pool is created and configured
specifically for manual backups.
From the Device tab, right-click Devices and launch the New Device Wizard
2 Use the following options to create the new device in the wizard:
Device Configuration Wizard Options:
Device Type: Advanced File Type Device (AFTD)
Storage Node: Accept default selection of NetWorker Server
Device Path: Choose the folder pre-created for you based on your NetWorker server
Linux NetWorker Server: /backupdev/adv_filedev2
Windows NetWorker Server: E:\Adv_filedev2
Label and Mount Device after creation: uncheck the box Label and Mount device after
creation.
When presented with the summary page, click Configure, and Finish to complete creation of the
device and close the wizard.
Click OK.
Click OK again to acknowledge the error box, and click OK again on the Media Pool Creation
window.
Result: This automatically creates and applies a label template with the name of the Media Pool.
4 On the Devices tab select Devices from the tree on the left.
Right-click the newly created device and choose label.
Pools: Manual
Click OK.
5 Using the Winclient link on the desktop, log in to the Windows client, winclient.emc.edu, with the
following credentials:
User: WINCLIENT\administrator
Password: student
Start > All Programs > EMC NetWorker > NetWorker User
6 If the Change Server dialog box is presented, enter the fully qualified name of your NetWorker
server.
NetWorker User – Change Server
Server: FQDN of NetWorker Server
Check the Box: Save as Default Server
Click OK.
8 Navigate to C:\WUTemp and mark the Common Files and Java folders for backup.
9 Navigate into the C:\WUTemp\Common Files folder and unmark the System folder.
10 From NetWorker User, start the backup by clicking the green start icon.
When the backup completes, this window can be used to validate that no files were backed up
from the C:\WUTemp\Common Files\System folder which you excluded from the backup.
14 Verify that the most recent backup was written to the same volume as the first.
Notice the save set name from this backup in comparison to the save set name from the previous
backup.
15 Perform another backup, this time select the C:\WUTemp\Common Files and
C:\Windows\Fonts folders.
Compress all the files being backed up by selecting Special Handling from the File menu.
Special Handling
Options: Compress
Click OK.
Initiate the backup and monitor its progress in the Backup Status window.
16 Once again, look at the contents of the volume to verify that the save set was backed up
successfully.
Identify the save set from this backup and notice the difference in save set names between the
three backups.
Can you explain why the names of each of the three save sets you backed up are different?
Note: The name of a save set created by a client-initiated backup is set to the lowest directory in the
directory structure which contains all files in the backup.
Compress the C:\WUTemp\Common Files folder by selecting the Common Files folder for backup.
Next right-click the folder and select Compress from the menu.
18 Encrypt the C:\WINDOWS\Fonts folder. In order to do this, you first must set a password.
To set the password, click the Options menu and select Password.
Click OK.
19 Encrypt the C:\WUTemp\Fonts folder by selecting the Fonts folder for backup. Next right-click
the folder and select Encrypt from the menu.
20 Initiate the backup and validate its successful completion in the Backup Status window.
Step Action
Background: This lab is designed to simulate a common real world scenario often encountered in
backup environments.
Scenario: In this scenario, you have a database instance with two databases that are running on
your winclient.emc.edu server. Backups of the databases are going to be performed using a
NetWorker module and for the sake of this lab we will pretend that the module backups have
already been configured.
Overview: For this lab, you need to configure filesystem backups of the database directories.
Because we don’t want to backup data already protected by the simulated NetWorker module, you
need to exclude backing up the .dbf (database) files in each of the two database directories. You will
use NetWorker directives to skip the two database files while still backing up all of the other files in
those directories.
1 From the Configuration tab, right-click Groups and select New to create a new group with the
following options:
Create Group
Setup Tab
Name: DirTest
Advanced Tab
Level: full
Uncheck: Force incremental Box
Click OK.
Click OK.
3 Create a new client resource for winclient.emc.edu accepting the defaults for everything but the
following properties:
Group: DirTest
Click configure, and Finish to complete creation of the new client instance.
Note: This backup included the .dbf files because you have not yet created directives to exclude
them. This backup will be used as a baseline to compare consecutive backups against.
From the Configuration tab, right-click Directives and select New. Create a new directive using with
the following properties:
Create Directive
General Tab
Name: Skip Databases
Directive: <<”C:\oradata\DB1”>>
skip: *.dbf
<<”C:\oradata\DB2”>>
skip: *.dbf
Click OK.
Note: Be sure that the directive text is entered exactly as displayed and on separate lines.
Click OK.
7 From the Monitoring tab, run another backup of the DirTest group.
In the DirTest Details window click the Start Time attribute and select the previously run backup of
this group.
Note the size difference of the C:\oradata save set from the previous backup.
Note: You should see a significant size difference indicating that the two .dbf files in the DB1 and
DB2 directories have been skipped. If the size is the same for both backups, repeat the previous
steps to configure your directive and ensure that it is typed correctly and properly applied to the
correct client.
9 You can further validate that only the two .dbf files were skipped by using the Recovery Wizard.
Click the Recovery tab and select the green plus symbol to open the recovery wizard.
Click Next to move to the Select Data To Recover section. By default the most recent backup is
selected and is browsable using the tree structure on the left side of the window.
Expand the directory structure out until you see the DB1 and DB2 directories. Click on DB1, and
note that only one file is displayed on the right. Repeat the process for the DB2 directory.
Click the blue arrow on the left side of the date box once to change to the backup performed prior
to configuring the directives.
Notice that after changing to the first backup, the .dbf files are listed in both the DB1 and DB2
directories. This validates that the files were included in the backup prior to configuring the
directives and skipped by backups run after applying them.
12 Return to the Configuration tab and delete only the client instance of winclient.emc.edu belonging
to the DirTest group. It will not be used for any other labs.
On the Configuration tab, right-click the DirTest group under Groups and delete it.
Click Yes when prompted if you are sure you want to delete this group.
End of Lab 4
Purpose: In this lab, you will configure a label template resource for a pool and then
configure a pool resource.
Step Action
1 From the Media tab, create a new label template by right-clicking Label Templates, and selecting
New.
2 Before creating your new media pool for the NSRBackup group to use, you must first clear the
NSRBackup group from the Disk1 pool.
From the Media tab select Media Pools and double-click the Disk1 pool and make the following
changes:
Media Pool Properties – Disk1
Basic Tab
Groups: Un-check NSRBackup
Click OK.
3 From the Media tab, right-click Media Pools and create a New media pool with the following
properties:
Create Media Pool
Basic Tab
Name: NSRBackup
Groups: Check the NSRBackup box
Label Template: NSRBackup
Click OK to save.
4 From the Devices tab re-label the device currently in the Manual pool into your newly created
NSRBackup pool.
Right-click your <servername>_aftd2 device and select label.
Click OK and then click Yes to confirm you want to overwrite the existing data on the volume.
Note: Ensure that the Disk1 pool is NOT selected on the properties of the client in the NSRBackup
group. If it is, it will override the pool settings and send data to the Disk1 pool. The pool entry of
the client should be blank.
6 While the backup runs, note that the save sessions are writing to the device labeled in the
NSRBackup pool.
7 To verify the save sets reside on the volume from the NSRBackup pool, from the Media tab, select
Disk Volumes, and double-click the nsrbackup.01 volume to validate the contents of the volume.
Click ok.
End of Lab 5
Purpose: In this lab, you configure a storage node resource, an advanced file type
device, and a dedicated autochanger controlled by the storage node.
Step Action
1 From the Devices tab, right-click the Storage Nodes folder and create a New storage node
resource with the following properties:
Create Storage Node
General Tab
Name: FQDN of your Storage Node
Note: Your storage node is the VM that you loaded the client and storage node
software on. If you NetWorker server is Windows, it will be the Linux server.
Configuration Tab
Search all luns: Yes
Use persistent names: Yes
Click OK.
Step Action
1 From the Devices tab, right-click Devices and use the New Device Wizard to create a new AFTD with
the following properties:
Device Configuration Wizard
Device Type: Advanced File Type Device (AFTD)
Storage Node: Name of your Storage Node
Device Path:
Linux Storage Node: /backupdev/adv_filedev1
Windows Storage Node: E:\adv_filedev1
Device Name: <storage node short name>_aftd1
Pool: Disk1
2 From the Configuration tab, modify the two clients in the 11PM group to use the newly created
storage node by changing the following property:
Client Properties
Globals (2 of 2) Tab
Storage Nodes: <FQDN of storage node>
nsrserverhost
Click OK and repeat the process to edit the other client in the 11PM group.
3 From the Configuration tab, edit the properties of the 11PM group to make the following changes:
Group Properties – 11PM
Advanced Tab
Level: Full
Force Incremental: Un-check the box
Click OK.
Note: Not all save sets are sent to the storage node. Index save sets are backed up from the
NetWorker server and will not be directed to this device.
5 From the Media tab, select Disk Volumes, and double-click the Disk1.002 volume to validate the
save sets from the backup reside on the volume.
In order to facilitate client direct backups a CIFS share has already been created on your Windows server for
the E:\Adv_filedev1 device. This has been preconfigured to save time in the labs, however this would be
required if performing this outside of the lab.
Step Action
1
From the Devices tab, edit the properties of your nwwindows_aftd1 device and make the following
additions:
Device Properties – nwwindows_aftd1
General Tab
Device Access Information: \\nwwindows.emc.edu\Adv_filedev1
Configuration Tab
Remote User: administrator
Password: student
Click OK.
2 From the Configuration tab, validate the client winclient.emc.edu will use nwwindows.emc.edu as
it’s storage node:
Client Properties – winclient.emc.edu
Globals (2 of 2) Tab
Storage Nodes: nwwindows.emc.edu (If Linux NetWorker server)
nsrserverhost (If Windows NetWorker server)
Click OK.
Note: If you chose to use a Linux NetWorker server, then the storage node attribute for
winclient.emc.edu, should contain nwwindows.emc.edu. If instead you are using a Windows
NetWorker server, the storage node attribute should contain only the keyword nsrserverhost.
When the backup has completed, open the Details window for the 11PM group and double-click the
C:\WUTemp save set.
In the pop-up windows that is displayed note the message stating Successfully established DFA
session with adv_file device. This indicates that a Client Direct backup has been performed.
Note: If you do not see the DFA message, validate the pathname to the share is typed exactly as
written in the lab guide and that you correctly entered the username and password.
NetWorker
Server
Storage Storage
Robotics Node Node Robotics
NetWorker
Client Mgmt Client
Console Srv
Host A Host B
1 From a command prompt on the NetWorker server and storage node, type the command inquire.
Note: if an autochanger and four tape drives are not detected, power off and power on the VM VTL
in you lab manager configuration.
2 From the Devices tab in the Administration interface, right-click the Storage Nodes in the left pane
and select Configure all libraries.
3 In the Provide General Configuration Information window, leave all selections at their default
values.
Click Next.
4 In the Select Target Storage Nodes window, make the following selections for both storage nodes:
Configure All Libraries
Select Target Storage Nodes
Configure: Select the check box for both storage nodes
Search all LUNs: Yes
Use Persistent Names: Yes
5 Monitor the Log window in the lower left corner of the NetWorker Administration GUI until the
message is displayed that both jukeboxes have been enabled and are ready.
6 From the Devices tab, expand the + symbol next to Libraries to view the two libraries you just
configured.
Click each of the two libraries to see the configuration and inventory of each library.
7 Right-click each library resource and edit the properties to make the following change:
Library Properties
Configuration Tab
Auto media management: Check the box
8 From the Configuration tab, right-click groups and create a new group with the following options:
Create Group
Setup Tab
Name: LibTest
Advanced Tab
Level: full
Force incremental: Unchecked
Click OK.
9 From the Configuration tab modify the client instance for your storage node to make the following
changes:
Client Properties - <Storage Node Client>
General Tab
Group: Ensure only the LibTest group is selected
Click OK.
10 From the Media tab, right-click Media Pools and create a New media pool with the following
options:
Create Media Pool
Basic Tab
Name: LibTest
Groups: LibTest
Click OK, click OK to acknowledge all pop-ups, and finally click OK again to allow NetWorker to
automatically create a label for this pool.
11 From the Configuration tab, edit the properties of the client resource for your storage node and
validate that the following property is configured:
Client Properties - <storage node client>
Globals (2 of 2)
Storage Nodes: <FQDN of Storage Node>
Click OK.
12 From the Devices tab, select one of the tape libraries you have configured. Right-click one of the
tape volumes and select Label.
Click OK.
13 From the Monitoring tab start a backup of the LibTest group and validate that data is sent to the
newly configured tape devices.
Note: You may receive an error stating that one or more of the tapes already contains a valid
NetWorker label. These errors can be disregarded and the volumes associated with them can be
relabeled without issue. This merely indicates that NetWorker has identified that these tapes were
used in a NetWorker environment previously and by default does not automatically re-label them in
case you need the data on them.
End of Lab 6
Purpose: In this lab, you will use the NetWorker Administration GUI to display the
contents of volumes, review client file indexes, and search for save sets.
Step Action
1 From the Media tab select Indexes on the left and determine the total size of the client file index
(CFI) for the winclient.emc.edu server.
2 Display a list of all save sets for winclient.emc.edu by double-clicking on the winclient.emc.edu
entry in the Indexes box on the right side of the Media tab.
3 Identify the save set that has been backed up the least often. (Hint: Cycle = Backup)
4 Click the save set that was identified in the previous step.
5 In the Index Save Sets window that you already have open, select the C:\WUTemp save set for
winclient.emc.edu.
Remove the oldest backup of this save set by clicking the Remove Oldest Cycle button.
Click Yes to confirm you are sure you want to remove the oldest cycle for the save set C:\WUTemp.
Note the number of SSID’s now listed for the C:\WUTemp Save Set.
Click OK.
6 From the Media tab click Save Sets from the tree on the left side. This opens the Query Save Set
window on the right side.
7 Using the Query Save Set tool, generate a list of all save sets in the Disk1 pool since the start of class
by entering the following options:
Query Parameters
Pool: Disk1
Save Time From: Select the first day of class
Save Time To: Select tomorrow
Leave all other fields blank, and select Save Set List to run the query and see the results.
Verify that only save sets in the Disk1 pool are reported by looking at the Pool heading.
Step Action
1 From the Media tab select Disk Volumes on the left and double-click the Disk1.001 volume to
display the save sets on that volume.
Click on one of the C:\WUTemp save sets and note the SSID.
SSID: ____________________
2 With the SSID identified in the previous step selected, click the change status button to bring up the
Change Save Set Status pop-up and make the following change:
Change Save Set Status
Status: Suspect
Click OK.
3 In the Volume Save Sets window, select the previously identified save set and change the status back
to normal.
Click OK.
4 From the Media tab, select Tape Volumes to display a list of currently labeled tapes.
Set the mode of any of the volumes to read-only by right-clicking on one of the volumes and
selecting Change Mode.
In the change mode dialog box enter the following options:
Change Mode
Select Mode: Read Only
Click OK.
5 Look at the volume you just changed in the Tape Volumes window.
What changes do you see in the Name and Mode of the volume?
6 Change the mode of the volume back to Appendable and again note the changes in the Name and
Mode of the volume.
7 From the Media tab, select Tape Volumes and select a volume from the Tape Volumes window that
has an expiration date and data written to it.
Right-click the selected volume and click Recycle to bring up the Recycled Dialog Box and make the
following change:
Recycle
Select Recycling Policy: Manual
Click OK, and note the change in the Expiration field of the volume you just modified.
8
Change the Recycle Policy of the volume back to Auto.
9 From the Media tab, select tape volumes on the left, and right-click an individual volume of your
choice. Select the Set Location option and enter the following information:
Set Location
Volume: Offsite
Click OK and note the Location field for the volume in the Tape Volumes window.\
10 From the Devices tab, select the tape library that contains the volume you modified in the previous
step. Inventory the volume in the library by right-clicking on it in the Library window and selecting
Inventory
11 Return to the Media tab, select Tape Volumes and validate that the location of the tape has been
changed automatically from offsite to the name of the tape library.
12 From the Media tab select a tape volume that is located in the tape library attached to the
NetWorker server.
Note: Location should NOT have “rd=” in the name.
Right-click the volume selected and delete it. Enter the following information in the dialog box:
Delete
Selection: File and Media Index Entries
Click OK, then click OK again to confirm you want to delete the volume from the database.
Notice the volume has been removed from the list of volumes, and is displayed in the library as <not
in media index>.
13 From the Devices tab, select the Local Library and right-click the tape volume you just deleted.
Select Load Without Mount from the pop-up menu.
Monitor the load operation and write down the name of the device that the tape was loaded into.
14 Open a command prompt on your NetWorker server and run the following command to scan the
volume you recently deleted back in to the database.
Command Prompt – NetWorker Server
Type: scanner –im <device_name>
Note: <device_name> should be replaced with the name of the device you loaded the tape into.
15 Return to the Media tab and select Tape Volumes to display the list of tape volumes in the media
database.
What do you notice about the name and mode of this volume?
Purpose: In this lab, you perform browsable and save set recoveries using the
NetWorker Recovery Wizard
Step Action
1 From the Recover tab select the green “+” symbol to launch the NetWorker Recovery Wizard.
2 In the Recovery Configuration wizard, create a new recovery configuration by entering the
following information:
Recover Configuration
Select the Recovery Hosts
Name: Select winclient.emc.edu
Click Next.
3 In the Select the Data to Recover dialog box, select the C:\WUTemp\Java folder in the folder
selection tree.
Click Next.
4 In the Select the Recovery Options window enter the following options:
Recovery Configuration
Select the Recovery Options
File Path for Recovery: New destination path
Recovery path box: C:\recover
Click Next.
On the Obtain the Volume Information window, leave the default options.
Click Next.
Click Run Recovery, and monitor the Recovery Results screen until the recovery is completed.
Click Finish.
Step Action
1 From the Recover tab select the green “+” symbol to launch the NetWorker Recovery Wizard.
2 In the Recovery Configuration wizard, create a new recovery configuration by entering the
following information:
Recover Configuration
Select the Recovery Hosts
Name: Select winclient.emc.edu
Click Next.
3 In the Select the Data to Recover window, enter the following options:
Recover Configuration
Select the Data to Recover
Click: Save Set Recover
Click Query, to populate the Save Set Name and Save Set Instances windows.
4 In the Save Set Name field select the C:\WUTemp\inf save set.
In the Save Set Instances field, select the most recent instance and mark the box next to it.
Click Next.
5 In the Select the Recovery Options window select the following options:
Recover Configuration
Select the Recovery Options
File Path for Recovery: Original path
Duplicate File Options: Rename the recovered file
Click Next.
Leave the default options on the Obtain the Volume Information page.
Click Next.
Click Run Recovery, and monitor the Recovery Results screen until the recovery is completed.
Review the Recovery Log and determine how the files were renamed.
Hint: What change was made to the filename when the file was renamed?
Click Finish.
Step Action
1 From the Recover tab select the green “+” symbol to launch the NetWorker Recovery Wizard.
2 In the Recovery Configuration wizard, create a new recovery configuration by entering the
following information:
Recover Configuration
Select the Recovery Hosts
Name: Select winclient.emc.edu
Click Next.
3 In the Select the Data to Recover dialog box, select the C:\WUTemp\Common Files folder in the
folder selection tree.
Click Next.
4 In the Select the Recovery Options window enter the following options:
Recovery Configuration
Select the Recovery Options
File Path for Recovery: New destination path
Recovery path box: C:\recover
Click Next.
On the Obtain the Volume Information window, leave the default options.
Click Next.
Note: When selecting the recovery time, select today, then click ok to acknowledge the error and
then manually enter the time box to display a time 10 minutes from now.
Click Schedule Recovery, and note that a new recovery session is created under Configured
Recovers.
6 Wait until after the scheduled time and validate that the recovery completes successfully. You
should see the NSR recover task complete in the log.
Additionally, once completed the ScheduledRecovery task should have a green check mark next to
it.
End of Lab 8
Purpose: In this lab, you will configure resources for cloning and staging, and use
them to perform cloning and staging operations.
Step Action
1 From the Configuration tab, Right-click Clones on the left and create a New clone resource.
Continue to Step 2.
Continue to Step 3.
3 In the Create Clone window select the Save Set Filters tab and enter the following:
Create Clone
Save Set Filters Tab
Groups: 11PM
Clients: winclient.emc.edu
Pools: Disk1
Filter save sets by level: Full
Include save sets from the previous: 2 Days
Click Preview Save Set Selection to see a list of save sets that will be cloned.
Monitor your NetWorker server during the time the clone is scheduled to run.
Note: Alternatively, you can right-click the clone job from the Monitoring tab to initiate it manually
instead of waiting for it to run.
4 When the clone job runs, monitor the clone job activity on the monitoring tab.
The Log window should show messages indicating the start of the scheduled clone.
The Clones window (opened by clicking the Clones tab in the upper window of the Monitoring tab)
should show the clone operation running.
The Clone Sessions window (opened by clicking the Clone Sessions tab in the sessions window)
should display the clone operations in progress.
5 Verify that the save sets were successfully cloned, by switching to the Media tab and viewing the
contents of the tape volume in the Default Clone pool.
Step Action
1 From the Monitoring tab of the NetWorker Administration GUI Perform a backup of the 11PM
group.
2 From the Configuration tab right-click Staging and create a New staging resource with the
following properties:
Create Staging
General Tab
Name: Stage1
Enabled: Yes
Devices: Select 1 of the 3 AFTD’s
Destination Pool: Default Clone
Save Set Selection: oldest save set
Max storage period: 1 Hour
Recover space interval: 3 Minutes
File system check interval: 2 Minutes
Click OK.
4 On the Monitoring tab, watch for staging to occur over the next few minutes.
The Log window should display messages indicating the staging session is starting and has finished.
5 Once the staging has completed, return to the Configuration tab and delete the staging policy that
you created.
End of Lab 9
Purpose: In this lab, you will perform several tasks relating to the management and
administration of the NetWorker Server.
Step Action
1 From the Setup tab in the NetWorker Management Console right-click Users and create a New
Console user with the following properties:
Create User
Identity Tab
User Name: John
Password: password1
Permissions Tab
Managed Hosts:
Windows NetWorker Server: nwwindows.emc.edu
Linux NetWorker Server: nwlinux.emc.edu
Click OK.
2 From the Configuration tab right-click the name of your NetWorker server in the top of the tree and
select Properties. Make the following additions:
NetWorker Server Properties
Setup Tab
Administrator: append user=John,host=<FQDN of NetWorker Server>
Click OK.
5 From the Setup tab, attempt to create a new console user named Sally.
Attempt to create another Console user named Sally. Why are you not able to?
Note: Only users with the role of Console Security Administrator are allowed to create, modify, or delete a
Console user.
6 While still logged in as John, launch the NetWorker Administration GUI for your NetWorker server.
Click OK.
12 From the Reports tab, expand the NetWorker Backup Statistics folder and select the Group
Summary report.
Select the View Report tab to run the report with the default parameters.
Right-click anywhere on the report and select Chart to change the report format.
13 From the Reports tab run the Server Summary report with the default parameters.
14 Run the Level Summary report and configure it to show only full and inc save sets backed up by the
NetWorker server as part of the 11pm group within the last week.
15 Right-click the report you just ran and select Save As. Save the repot as Full and Inc Summary.
Right-click the report you created and select Share to share it with all console users.
16 View the default output generated by the Save Set Details by Server over Time report.
Drill down through all the reports until you see details about each individual save set backed up for
the Default group on a single day.
Go back to the Daily Summary by right-clicking on the report and selecting the Back button.
17 Right-click the report and export it as an HTML file named report.html in the C:\ directory.
18 Modify the Console database by selecting the Reports pull-down menu and selecting Data
Retention.
Click OK.
19 From the Configuration tab in NetWorker Administration select Clients and modify the properties of
your NetWorker server client that is currently not part of any group.
Note: The save set for this client should contain NMCASA: If the client selected does not contain this
save set select the correct client.
Click OK.
20 From the Monitoring tab, run another backup of the 11PM group.
21 View the Details of the 11PM group and validate that the console backup completes successfully.
Step Action
1 On your NetWorker server view the contents of the following NetWorker log files:
o messages
o summary
If your NetWorker server is on Linux, these log files will be empty as these messages will be logged
to syslog or emailed the root user on the system, depending on the particular notification. This
behavior varies from Windows based NetWorker servers where these messages are logged in the
displayed files.
2 View the contents of the NetWorker daemon.raw log file between yesterday and today. (Adjust
the times in order to view some log messages.)
For example,
cd /opt/lgtonmc/logs
nsr_render_log -B -50 gstd.raw
4 From the Configuration tab, select User Groups. In the User Groups window right-click and create
a New user group with the following properties:
Create User Group
General Tab
Name: NWOperators
Users: user=wilma,host=*
user=fred,host=<networker_server_name>
Privileges: Operate NetWorker
Monitor NetWorker
Operate Devices and Jukeboxes
Recover Local data
Backup Local data
Click OK.
5 From the Configuration tab, select Notifications. Make a copy of the Savegroup completion
notification.
Click OK.
7 When the backup completes, view the contents of the savegroup2.log created by your new
notification.
8 From the Configuration tab edit the properties of the winclient.emc.edu client in the 11PM group
and make the following changes:
Client Properties – winclient.emc.edu
Globals (2 of 2)
Owner notification:
Windows: nsrlog –f “C:\winclient.log”
Linux: /bin/mail -s "Winclient Backed up" root
10 Validate that the client notification occurred by checking for the file on the NetWorker server if the
NetWorker server is on Windows, or checking the mail on the Linux NetWorker server by typing
the command mail.
Linux: Type mail and note the message was sent showing backup completion.
11 From a command prompt or Windows explorer view the contents of the RAP log. Note the entries
for the objects created.
End of Lab 11
Purpose: In this lab, you perform a recovery of the NetWorker media and resource
databases and a client CFI.
Step Action
Simulate a Disaster
mminfo -B
Write down the following information pertaining to the bootstrap save set.
SSID: ___________________________
Volume Name: ____________________
File Number: _____________________
Note: This information is typically obtained from the bootstrap notification via email or log
depending on how you have it configured. This lab illustrated an alternative way to retrieve it in
case the bootstrap report is not available.
5 Notice that the directories you renamed were recreated. However, the media database and CFIs are
now empty and the resource database contains only the preconfigured resources created during
installation.
Log in to the NetWorker Management Console and validate that your custom configuration is no
longer there.
6 From the Devices tab configure the local AFTD device that had the nsrbackup.01 volume mounted in
it before the “Disaster”.
Note: Do not label your AFTD’s as this erases all data on them.
8 When prompted to recover client file indexes, select Yes to all clients.
While this is running, log in to the NetWorker Management Console and look for any alerts.
11 From the Media tab of the NetWorker Administration GUI select Indexes and note that the client
file indexes have been rebuilt.
End of Lab 13