NetWorker 9 IM Lab Guide - v7
NetWorker 9 IM Lab Guide - v7
February 2016
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 2016 EMC Corporation. All rights reserved. Published in the USA.
LAB 2-1: INSTALL NETWORKER AND NMC SOFTWARE ON WINDOWS HOST ........ 16
LAB 2-1 PART 1: INSTALL NETWORKER SERVER AND NMC ON A WINDOWS HOST .................17
LAB 2-1 PART 2: VERIFY SUCCESSFUL INSTALLATION ON THE WINDOWS HOST .......................24
LAB 2-2: START NMC AND PERFORM INITIAL NMC CONFIGURATION .................. 26
LAB 2-2: START NMC AND PERFORM INITIAL NMC CONFIGURATION ..................................27
LAB 2-3 PART 1: INSTALL NETWORKER CLIENT SOFTWARE ON A WINDOWS HOST .................35
LAB 2-3 PART 2: INSTALL NETWORKER STORAGE NODE ON A LINUX HOST ...........................37
LAB 6: MANAGE NETWORKER MEDIA DATABASE AND CLIENT FILE INDEX ........ 157
LAB 10-1: GENERATE REPORT AND CREATE CUSTOM REPORT ......................................... 216
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 in 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 to
perform the NetWorker Implementation and Management course
lab exercises.
Each student works in their own VDC configuration, accessed with
an assigned VDC username and password. The NetWorker
Implementation and Management lab configuration consists of
these 5 virtual machines:
nw – A NetWorker server running Windows Server 2012 R2
linux-sn – A NetWorker storage node running RedHat Linux 6.3
ad – A Windows domain controller and DNS server
win-client – A NetWorker client running Windows Server 2012
R2
ddve – A Data Domain system
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 NetWorker IM 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 (VDC) with the user name and password provided to you by the
instructor.
If you receive a prompt to install Citrix Receiver, proceed with the install.
5 If you receive a Citrix Receiver – Security Warning message, select Permit Use.
6 At the EMC Education Services login screen, re-enter your assigned login user name and password as
used in step 3.
Click Login.
7 You will be working in the NetWorker 9 IM vApp for all the labs for this course. To get your
own personal copy of the vApp, copy the vApp to your environment.
8 In Select vApp Template, select the NetWorker 9 IM vApp and then click Next.
9 In Select Name and Location, use a name of your choice like <your name>-NetWorker 9 IM
in the Name field.
Click Next.
11 Once the vApp creating operation has completed, click the green Start icon.
Click in the small blue console of the virtual machine that you want to work on. This opens a console
window. For the next lab, click in the small console of the nw host.
14 To send a Ctrl-Alt-Delete sequence to a Windows virtual machine, click the small keyboard icon in the
upper right corner of the console window.
15 To log in to a Windows virtual machine, click in the console window and enter the following
information in the login page:
Username: EMC\Administrator
Password: student
16 If you see a large blue box with a prompt asking if you want to find PCs, devices, …, click anywhere in
the window outside of the blue box.
17 When prompted to log in to another Windows virtual machine, you can open a Remote Desktop
Connection and log in to the other Windows host.
18 When prompted to log in to the Linux virtual machine (linux-sn), initiate a PuTTY session from a
Windows host.
Note: For best performance, please log in to a Windows host through a Remote Desktop Connection
and log in to a Linux host through a PuTTY session.
20 When you are finished with your vApp for the day, just logout of vCloud Director. (There's no need to
stop the vApp until you are finished with all the labs at the end of the class.)
To log out of vCloud Director, click Logout in the upper right corner of the vCloud Director screen.
Purpose: In this lab, you install NetWorker server and NetWorker Management
Console software on the host nw. This host will be used for configuration
and administration of NetWorker during the remainder of the class. You
then perform Initial NMC configuration. In the last section of this lab, you
install NetWorker client software and storage node software.
Lab Environment: In this exercise, you will be using the following virtual machines:
nw – A NetWorker server running Windows Server 2012 R2
linux-sn – A NetWorker storage node running RedHat Linux 6.3
ad – A Windows domain controller and DNS server
win-client – A NetWorker client running Windows Server 2012 R2
Purpose: In this lab, you install the NetWorker server and NetWorker Management
Console server software on the Windows host, nw. This host is used for
configuration and administration of NetWorker during the remainder of
the class.
Step Action
1 Check out and deploy the NetWorker 9 IM vApp following the instructions in the previous lab.
Username: EMC\Administrator
Password: student
2
On the nw.emc.edu server, right-click the Window icon in the left corner of the task bar and
select Run.
Type:
\\AD\Download
Click OK.
NetWorker9\NW 9.0\nw90_win_x64\win_x64\networkr
Double-click: NetWorker-9.0.0.x
Note: The NetWorker version that you deploy may be different from what is displayed here.
Click Next.
Click Next.
Click Next.
If you see a message advising you to update the JRE version, click OK.
8 In the Configure NetWorker Authentication Service Keystore window, type a password for the
keystore file:
Click Next.
9 In the Configure NetWorker Authentication Service window, type an initial password for the
authentication service:
Click Next.
Click Next.
Click Next.
Click Install.
14 In the Complete the Setup window, review the result. Note the installation and setup log location.
Step Action
1 On the nw.emc.edu host, move your mouse to the lower left corner of the screen and click the
Window icon to access the Start menu. Then, click Windows PowerShell.
Note: From the Start view, click Desktop to bring up the traditional desktop view.
2 To verify that the appropriate NetWorker services are started, run these two commands from
Windows PowerShell.
get-service nsr*
get-service gst*
Purpose: In this lab, you start NetWorker Management Console (NMC) and perform
initial NMC configuration tasks.
Step Action
Access the Start menu by clicking the Windows icon in the lower left of the screen: .
Click the down arrow to display the Apps on this host .
Note: If you see this Unable to detect Java Runtime Environment warning message, click here to
start NetWorker Management Console.
Notes:
If you receive a prompt that the Java version is out of date, click Later.
If you receive a Java security warning, choose to run anyway.
4 In the NetWorker Management Console Login window, type the login information:
Click OK.
Click Accept.
Click Next.
7 In the Set authentication server service account for the NMC server window:
Click Next.
8 In the Define Database Backup Server window, type the NetWorker server name:
Click Next.
9 In the Specify a list of managed NetWorker servers window, specify a list of NetWorker servers
that this NetWorker Management Console will manage:
Click Finish.
In the Enterprise window, expand the tree in the left pane to display the name of the NetWorker
server. You may need to drag the vertical pane divider to the right to display the tree on the left.
10 Click the name of the NetWorker server, nw.emc.edu, in the left pane. Then, click Launch
NetWorker Administration in the right pane.
Or
You can right-click the server name, nw.emc.edu, in the left pane and select Launch Application.
11 From the menu bar of NetWorker Administration, select View > Diagnostic Mode.
Note: Diagnostic mode is needed to see some of the NetWorker resource attributes that we will
be using in the following labs.
Purpose: In this lab, you install NetWorker client software on the Windows client
machine, win-client, and NetWorker client and NetWorker storage node
software on the Linux host, linux-sn.
Step Action
1 Log in to the NetWorker Windows client, win-client, with the following credentials:
Username: EMC\Administrator
Password: student
2 From the Windows desktop on win-client, right-click the Windows icon and select Run.
Type:
\\AD\Download
Click OK.
Double-click lgtoclnt-9.0.0.x
Note: The NetWorker version that you deploy may be different from what is displayed here.
4 Install NetWorker client software, providing all the information specified below when prompted:
Click Install and Finish to complete the NetWorker client software installation.
Step Action
Username: root
Password: student
3 Change to the /software directory and untar the NetWorker software. Type:
cd /software
tar -xzvf nw90_linux_x86_64.tar.gz
cd linux_x86_64
Result: The directory /software/linux_x86_64 contains the rpm files for the Linux installation.
Note: The NetWorker version that you deploy may be different from what is displayed here.
5 Start the NetWorker client process and verify that it is running by typing:
/etc/init.d/networker start
ps -ef | grep nsr
Purpose: In this lab, you install and configure License server software on the
NetWorker server, nw.emc.edu.
Step Action
1 On the NetWorker server, nw.emc.edu, right-click the Windows icon and select Run.
Type:
\\AD\Download
Double-click EMC_LicenseServer_3.4.0_x64
Click Next.
Click Next.
Click Next.
11 To configure the EMC License server service, start LMTOOLS from the desktop.
15 Select Start/Stop/Reread.
The bottom of the dialog box should display: Server Start Successful.
16 Close LMTOOLS.
18 Click Server.
Select the NetWorker server, nw.emc.edu, from the left pane and click Server Properties in the
right pane.
Click Licensing.
Click OK.
21 Select the NetWorker server, nw.emc.edu, from the left pane and click Server Properties.
Click Licensing.
End of lab
Purpose: In this lab, you create a NetWorker label template, a pool and a backup
device in preparation for running backups in the next lab.
Step Action
1 If not already open, start NetWorker Management Console from the NetWorker server,
nw.emc.edu. Then, launch NetWorker Administration.
Name: BRSBackup
Fields: brsbackup
001-100
Separator: “.”
3 Next, create a media pool. From the Media window, right-click Media Pools and select New. Enter
the following:
Name: BRSBackup
Pool type: Backup
Label template: BRSBackup
Select and right-click Devices in the left pane and then select New Device Wizard.
Click Next.
Click Next.
Click Next.
Click Next.
9 In the Label and Mount Devices window, specify the following attributes:
Click Next.
Click Configure.
Click Finish.
End of lab
Purpose: In this lab, you perform a scheduled backup of the NetWorker client, win-
client.emc.edu.
Step Action
2 In the Enterprise window, select nw.emc.edu and click Launch NetWorker Administration.
3 Create a client by clicking Protection. Then, right-click Clients and select New Client Wizard.
Click Next.
Click Next.
Click Next.
Clear DISASTER_RECOVERY:.
Click Next.
8 In the Client Configuration Summary window, review the client configuration information.
9 Create a protection group. From the Protection window, right-click Groups and select New.
Click OK.
Click OK.
13 Create a workflow in the newly created policy. With the Standard Filesystem policy selected, click
Create a new Workflow.
15 Create a backup action in the Specify the Action Information window by specifying the following
attributes:
Name: BRS_backup
Action Type: backup
Backup Subtype: traditional
Click Next.
16 In the Specify the Backup Options window, specify the following attributes:
Click Next.
Click Next.
Click Configure.
19 The New Workflow window of the Windows Backup workflow shows that the BRS_backup action is
added successfully.
Click OK.
20 Review the Standard Filesystem Policy, Windows Backup Workflow and Workflow virtual
representation.
Step Action
1 Click Monitoring.
4 After the backup completes successfully, right-click the Windows Backup workflow and select Show
Details.
5 Review the results of the BRS_backup action by selecting it and clicking Show Details or Show Action
Logs.
Step Action
Click OK.
Click OK.
5 With the Multiple Actions policy selected, click Create a new Workflow.
7 In the Specify the Action Information window, specify the following attributes:
Click Next.
8 In the Specify the Connectivity Options window, accept the default setting.
Click Next.
10 Click Add again in the Actions section to add a second action to the Advanced Workflow workflow.
11 In the Specify the Action Information window, specify the following attributes:
Name: backup
Action Type: backup
For the demonstration purpose, make this backup action as a Full level backup everyday:
Select: Full
Click Make All
Click Next.
Click Next.
14 In the New Workflow window for the Advanced Workflow workflow the backup and check
connectivity actions are added successfully.
Click OK.
15 Review the Multiple Actions policy, Advanced Workflow workflow, backup and check connectivity
actions and the workflow virtual representation.
16 Click Monitoring. Right-click the Multiple Actions policy and click Start.
Step Action
1 In NetWorker Administration, click Protection. Right-click Clients and select New Client Wizard.
Click Next.
Click Next.
Click Next.
Expand C: and the Documents folder. Select all NetWorker 9.0_xxxx.pdf files for backup.
Click Next.
Click Create.
Click Finish.
Click OK.
Name: Tag
Click OK.
13 In the Specify the Action Information window, specify the following attributes:
For the demonstration purpose, make this backup action as Full level backup everyday:
Select: Full
Click Make All
Click Next.
14 In the Specify the Backup Options window, specify the following attributes:
Click Next.
Click Next.
Click Configure.
17 In the New Workflow window for the Tag Backup workflow, notice that the backup action is added
successfully.
Click OK.
18 From the Monitoring window, right-click the Tag policy and click Start.
Step Action
1 From the Protection window, click Policies and then select and expand the Multiple Actions policy.
2 To configure a notification, double-click the check connectivity action in the right pane.
3 In the Specify the Advanced Options window, specify the following attributes:
4 You can also start backup policies from the Protection window.
From the Protection window, expand Policies. Right-click the Multiple Actions policy and click Start.
5 Navigate to the completion.log file in C:\ and open it with Windows Notepad.
The completion.log notification is created by the nsrlog command after the check connectivity and
backup actions complete successfully.
Background: The Lab 4-3 Part 4 is designed to simulate a real world scenario often encountered in backup
environments.
Scenario: In this scenario, you have an Oracle database instance with two databases that are running on your win-
client.emc.edu virtual machine. 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 file system backups of the database directories. Because we don’t want
to back up the database that is already protected by the simulated NetWorker module, you need to exclude backing up
the database files (.dbf) 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.
Step Action
1 From the Protection window, right-click Clients and then select New Client Wizard.
Click Next.
Click Next.
Click Next.
5 In the Select File System Objects window, select ONLY the following folder:
C:\oradata
Clear DISASTER_RECOVERY:.
Click Next.
Click Create.
Click Finish.
Name: DirTest
Group Type: Clients
Clients: win-client.emc.edu (** Select the client instance with C:\oradata as Save set)
Click OK.
Name: DirTest
Click OK.
Name: DirTest
Groups: DirTest
13 In the Specify the Action Information page, specify the following attributes:
Name: backup
Action Type: backup
Backup Subtype: traditional
For the demonstration purpose, make this backup action as Full level backup everyday:
Select: Full
Click Make All
Click Next.
14 In the Specify the Backup Options window, specify the following attributes:
Click Next.
Click Next.
Click Configure and then click OK to close the New Workflow window.
17 From the Protection window, expand Policies. Right-click the DirTest policy and click Start.
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.
Click OK.
Note: Be sure that the directive text is entered exactly as displayed here and on separate lines.
Copying and pasting from the lab guide will result in failure.
Right-click the win-client.emc.edu client instance with the C:\oradata save set and select Modify
Client Properties.
Click OK.
Click the Media tab and then select Save Sets from the left pane.
Note: You should see a significant size difference between these two backups 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.
End of lab
Purpose: In this lab, you configure and manage various NetWorker backup devices.
Step Action
General tab:
Name: linux-sn.emc.edu
Configuration tab:
Search all luns: Yes
Use persistent names: Yes
Click OK.
Step Action
1 From the Devices window, right-click Devices and select New Device Wizard.
Click Next.
Click Next.
Click Next.
Click Next.
6 In the Label and Mount Devices window, specify the following attributes:
Click Next.
8 A remote AFTD device (linux-sn_aftd1) has been created on the remote storage node (linux-
sn.emc.edu).
A disk volume (brsbackup.002) has been created and mounted on the remote AFTD device.
Step Action
1 From the Protection window, right-click Clients and select New Client Wizard.
Click Next.
Click Next.
Click Next.
Click Next.
Click Create.
Click Finish.
Click OK.
Click OK.
11 With the Remote Backup policy selected, click Create a new Workflow.
13 In the Specify the Action Information window, specify the following attributes:
Name: backup
Action Type: backup
Backup Subtype: traditional
For the demonstration purpose, make this backup action as Full level backup everyday:
Select: Full
Click Make All
Click Next.
Click the pencil icon to specify linux-sn.emc.edu as the destination storage node:
Click Next.
Click Next.
Click Configure.
Click OK.
18 From the Protection window, expand Policies, right-click the Remote Backup policy and click Start.
From the Monitoring window, monitor the Remote Backup policy backup progress.
19 Click the Media icon, select Disk Volumes, and double-click the brsbackup.002 volume to validate
that the save sets from the backup reside on the volume.
Step Action
1 For lab demonstration purposes, let’s create a separate backup pool for the NetWorker client direct
backup.
From the Media window, create a new label template by right-clicking Label Templates and selecting
New.
3 Right-click Media Pools and select New to create a media pool with the following properties:
4 A local disk (D:\AFTD2) will be used for Client Direct backups. This local disk needs to be set up as a
shareable device before it can be configured as an AFTD device for Client Direct backup.
On the NetWorker backup server, nw.emc.edu, click File Explorer and select D:
Right-click the AFTD2 folder and select Share with > Specific people.
5 Select Everyone from the list of people to share with and then click Add.
Click Share.
Click Done.
6 From the Devices window, right-click Devices and select New Device Wizard.
Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Right-click the AFTD_2 device from the right pane and select Unmount.
14 After the clientdirect.001 volume is unmounted, right-click the AFTD_2 device and select
Enable/Disable to disable it temporarily.
Click OK.
Step Action
1 By default, Client Direct is selected and enabled when a NetWorker client resource is created by the
NetWorker Client Wizard.
You can verify that Client Direct is enabled by double-clicking a client resource.
Click OK.
Click OK.
6 With the Client Direct policy selected, click Create a new Workflow.
8 In the Specify the Action Information window, specify the following attributes:
Name: backup
Action Type: backup
Backup Subtype: traditional
For the demonstration purpose, make this backup action as Full level backup everyday:
Select: Full
Click: Make All
Click Next.
9 In the Specify the Backup Options window, specify the following attributes:
Click Next.
Click Next.
Click Configure.
Click OK.
13 Expand Policies and right-click the Client Direct policy. Click Start.
From the Monitoring window, monitor the Client Direct policy backup progress.
Then, navigate to: policy > Client Direct > Client Direct > backup_xxxxxx_logs
Open the text document that was created last – in this case, 128008.
The message “Successfully established Client direct save session” indicates a Client Direct backup
was performed.
Step Action
1 Log in to the NetWorker backup server, nw.emc.edu, and open the Configure DataDomain folder
from the desktop.
3 From NetWorker Administration, open the Devices window. Right-click Data Domain Systems and
select New Device Wizard.
Click Next.
Click Next.
DD Boost Credentials
DDBoost user name: sysadmin
DDBoost password: emc123
Configuration Method
Select: Browse and Select
Click Next.
Click New Folder and type ddve_dev1 for the folder name, and then press Enter.
Click Next.
Pool Type
Select: Backup
Pool
Select: Create and use a new Pool
Type: ddbackup
Click Next.
Click Next.
Click Next.
Click Configure and validate that all tasks are completed successfully.
12 In the Devices window, expand the Data Domain Systems and click ddve.emc.edu
Note: NetWorker is now able to monitor and report on the Data Domain system.
Step Action
1 From the Protection window, right-click Clients and select New Client Wizard.
Click Next.
Click Next.
Click Next.
5 In the Select File System Objects window, select ONLY the following two folders:
C:\Documents
C:\oradata
Clear DISASTER_RECOVERY:.
Click Next.
6 In the Client Configuration Summary window, review the client configuration information.
Name: DD Backup
Group Type: Clients
Clients:
win-client.emc.edu (select the client instance with C:\Documents and C:\oradata save sets)
Click OK.
Name: DD Backup
Click OK.
Name: DD Backup
Groups: DD Backup
13 In the Specify the Action Information window, specify the following attributes:
Name: backup
Action Type: backup
Backup Subtype: traditional
For the demonstration purpose, make this backup action as Full level backup everyday:
Select: Full
Click Make All
Click Next.
14 In the Specify the Backup Options window, specify the following attributes:
Click Next.
Click Next.
Click Configure.
Click OK.
18 Open the Protection window. Right-click the DD Backup policy and click Start.
From the Monitoring window, monitor the progress of the DD Backup policy backup.
End of lab.
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
From the Media window, select Client Indexes from the left pane.
Select the win-client.emc.edu client indexes and check the Size of the client file index (CFI).
Now, right-click the win-client.emc.edu client indexes from the right pane and select Show Save Sets
Select : C:\oradata
Identify the number of SSIDs listed for the C:\oradata save set and the backup times.
3 Remove the oldest backup of this save set by clicking the Remove Oldest Cycle button.
4 Click Yes to confirm that you want to remove the oldest cycle for the save set C:\oradata.
Note the number of SSID now listed for the C:\oradata save set.
Click OK.
Now, check the size of the win-client.emc.edu client file index (CFI).
Select Save Sets from the left pane of the Media window.
Leave all other fields blank, and then select Save Set List to run the query and see the results.
Verify that only save sets in the Client Direct pool are listed by looking at the Pool heading.
Step Action
From the Devices window, select Devices in the left pane. Right-click AFTD_1 in the right pane and
select Unmount
From the Media window, select Disk Volumes in the left pane.
Right-click the brsbackup.001 volume in the right pane and select Show Save Sets to display the
save sets on that volume.
3 In the Volume Save Sets window, select one of the C:\oradata save sets and note the Status.
In the Change Save Set Status dialog box make the following change:
Select: Suspect
Click OK.
5 Notice that the Status of the C:\oradata save set now shows suspect.
6 In the Volume Save Sets window, select the previously identified save set and change the status
back to Normal.
Click OK.
From the Media window, select Disk Volumes to display a list of currently labeled volumes.
Set the mode of a volume to Read-Only by right-clicking the brsbackup.001 volume and selecting
Change Mode.
Click OK.
8 Notice the brsbackup.001 volume you just changed in the Disk Volumes window.
9 Change the mode of the volume back to Appendable and again note the changes in the Name and
Mode of the volume.
Select Disk Volumes and then select the brsbackup.001 volume. Note the Expiration date of the
volume.
Select: Manual
Click OK.
11 Note the change in the Expiration field of the volume you just modified.
In the Devices window, select Devices from the left pane. Right-click AFTD_1 in the right pane and
select Mount
End of lab
Purpose: In this lab, you perform browsable and save set recoveries using the
NetWorker Recovery Wizard.
Step Action
1 Click Recover to open the Recover window. Select Recover > New Recover.
2 In the Select the Recovery Hosts window, specify the following attributes:
Name: win-client.emc.edu
Click Next.
Click Browse.
Click Versions.
4 In the Select Versions window, select the most recent backup instance.
Select New destination path and type C:\recover1 for the destination path.
Click Next and then OK to acknowledge that the folder will be created.
Click Next.
Click Finish.
9 Navigate to C:\recover1 on win-client.emc.edu and verify that the files were recovered.
Step Action
Name: win-client.emc.edu
Click Next.
Select: Last
Select: 1 Week(s)
Click Query.
In Save Set Instances, select the most recent backup instance and Mark the box next to it.
Click Next.
Select New destination path and type C:\recover2 for the destination path.
Click Next and then OK to acknowledge that the folder will be created.
Click Finish.
8 Navigate to C:\recover2 on win-client.emc.edu and verify that the files were recovered.
Step Action
Name: win-client.emc.edu
Select: Recover to the same host
Click Next.
Click Browse.
Click Versions.
4 In the Select Versions window, select the most recent backup instance.
Select New destination path and type C:\recover3 for the destination path.
Click Next and then OK to acknowledge that the folder will be created.
Click Next.
Note: When specifying the recovery time, select today’s date, then click OK to acknowledge the
error and then manually enter the time to display a time 10 minutes from now. Press Enter after
you enter the date and time, then the Schedule Recovery option will become available.
8 Note the newly created Scheduled Recovery session is created under Configured Recovers.
9 Wait until the scheduled time and validate that the recovery completes successfully.
In the Recover window, under the Configured Recovers section note that Scheduled Recovery is
started at your specified time.
10 Navigate to C:\recover3 on win-client.emc.edu and verify that the files were recovered.
End of lab
Purpose: In this lab, you will configure resources for cloning and staging, and use
them to perform cloning and staging operations.
Step Action
1 In the Devices window, right-click Data Domain Systems and select New Device Wizard.
Click Next.
Click Next.
DD Boost Credentials
DDBoost user name: sysadmin
DDBoost password: emc123
Configuration Method
Select: Browse and Select
Click Next.
Click New Folder and enter ddve_dev2 for the folder name. Press Enter.
Click Next.
Pool Type
Select: Backup Clone
Pool
Select: Create and use a new Pool
Type: DD Clone
Click Next.
Click Next.
Click Next.
Click Configure and validate that all tasks are completed successfully.
10 In the Devices window, expand Data Domain Systems and click ddve.emc.edu.
Step Action
Click OK.
Click OK.
3 With the Backup and Clone policy selected, click Create a new Workflow.
4 In the Specify the Action Information window, specify the following attributes:
Name: backup
Action Type: backup
Backup Subtype: traditional
For the demonstration purpose, make this backup action as Full level backup everyday:
Select: Full
Click: Make All
Click Next.
Click Next.
Click Next.
Click Configure.
8 In the New Workflow window for the Backup and Clone workflow:
Name: clone
Action Type: clone
Click Next.
10 In the Specify the Clone Options window, specify the following attributes:
Click Next.
Click Next.
Click Configure.
13 In the New Workflow window for the Backup and Clone workflow:
Click OK.
From the Monitoring window, monitor the progress of the Backup and Clone policy backup and
clone.
Step Action
Click OK.
3 From the Monitoring window, watch for staging to occur over the next few minutes.
Note that the clone operation is running in the Clone Sessions pane and activity with the devices is
displayed in the Devices pane.
Note: This is identified as clone sessions however the log shows that save sets are deleted after
the clone operation which is the difference between a clone and a staging operation.
4 Once the stage operation has completed, delete the BRS Staging stage policy.
End of lab
Purpose: In this lab, you perform several tasks relating to security features of
NetWorker.
Step Action
C:\> cd \
C:\> regconfig.bat
To save time, the C:\ldapconfig.bat file contains the command and will be run instead of
typing the command. Upon running, the command will be displayed for review before it is
executed.
On the NetWorker server, nw.emc.edu, open a Command Prompt and type the following
commands:
cd \
ldapconfig.bat
Validate your authc configuration by querying the Active Directory server using the
authc_mgmt command to display the users in the emc.edu domain.
4 Return to the Setup window in the NetWorker Management Console and select NMC
Roles.
6 Now, we will assign the NMC role to the external user group.
cn=networker_admins,cn=users,dc=emc,dc=edu
Click OK.
7 To authorize the external group to perform tasks on the NetWorker server, assign the
external group to a user group on the NetWorker server.
8 In the User Group Properties window, add the networker_admins group to the External
roles box. Type:
cn=networker_admins,cn=Users,dc=emc,dc=edu
Click OK.
Then, launch NetWorker Management Console and log in with the following domain user
account:
Click OK.
11 Launch NetWorker Administration and open the Protection window. Validate that you
can create a resource in NetWorker Administration.
Step Action
3 Click Permissions.
Managed Hosts:
ddve.emc.edu
nw.emc.edu
Click OK.
From the Protection window, select and right-click the name of the NetWorker server, nw.emc.edu,
from the top of the tree and select Properties.
General tab:
Administrator: append user=John,host=nw.emc.edu
Click OK.
6 Close both the NetWorker Administration and NetWorker Management Console windows.
Note: The New option is not available. Only users with the role of Console Security Administrator are
allowed to create, modify, or delete a Console user.
10 Open the Protection window and create a new Group with the following properties:
Name: Test_John
Group Type: Clients
Clients:
linux-sn.emc.edu
Click OK.
An error message displays indicating that the console user, John, does not have the proper
permission.
Groups: Administrators
NMC Role: Console Security Administrator
Click OK.
Step Action
On your NetWorker server, view the contents of the following NetWorker log files located in the
Program Files > EMC NetWorker > nsr > logs directory:
messages
summary
View the contents of the NetWorker daemon.raw log file with the nsr_render_log command.
Then, type the following command to view entries starting with yesterday:
End of lab
Purpose: In this lab, you create and export NetWorker Management Console
reports.
Step Action
2 Note all the drill down reports and their sequences in the Drill Down Sequence section.
Double-click any policy in the Policy Name column to display the next drill down sequence report.
Double-click the month in the Month column to display the next drill down sequence report.
5 This is the Daily Summary report. You see a summary of activity for each day in the month.
Double-click any day in the Date column to display the next report in the drill down sequence.
6 In the Client Summary report, double-click win-client to display the Save Set Details report.
Right-click anywhere in the report and select Back to display the previous report until you reach the
Policy Summary report again.
7 Right-click anywhere on the Policy Summary report and select Chart to change the report format.
From Reports > Policy Statistics, select the Save Set Details report.
Click Configure.
Result: The custom Documents on DD report is saved under Save Set Details.
13 To export a report:
Right-click anywhere on the Save Set Details report and select Export. Export the report as an
HTML file named MyReport.html in the C:\ directory.
End of lab
Purpose: In this lab, you perform a recovery of the NetWorker media and resource
databases and a client CFI.
Step Action
1 On the NetWorker server, launch NetWorker Management Console and log in as Administrator.
Open the Setup window. Select Setup > Set Database Backup Server from the menu bar.
Click OK.
4 Create a Data Domain device in a pool that will be dedicated to NetWorker server and NMC backups.
From the Devices window, click Devices in the left pane and select New Device Wizard.
Right-click the NMC server backup action in the right pane and then select Properties.
Right-click the Server db backup action in the right pane and then select Properties.
10 Start the Server Protection policy and monitor the backup processes.
11 Validate the NetWorker bootstrap and Console databases are backed up successfully.
From the Media window, select Save Sets > Save Set List.
Step Action
1 To simulate a disaster:
Enter the following mminfo command to identify the NetWorker bootstrap information.
mminfo -B
Write down the following information pertaining to the bootstrap save set.
SSID: ___________________________
Volume Name: ____________________
Note: This information can also be obtained from the notification and log messages that are
created for a server backup.
3 After the services are stopped, simulate a disaster by renaming the following directories under
C:\Program Files\EMC NetWorker\nsr:
Rename: mm to mm.orig
Rename: res to res.orig
Rename: index to index.orig
Note: If one or more services fail to start, wait 20 seconds or so and then try again.
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 NMC as administrator. Launch NetWorker Administration and validate that your custom
configuration is no longer there.
From the Devices window, create a Data Domain device with the name ddve.emc.edu_ddve_dev3.
This is the name of the device that had the ServerBackup.001 volume mounted in it before the
“Disaster”. Refer to Lab 12-1, Step 4 but clear Label and Mount device after creation.
Important: DO NOT LABEL the device as you will erase all data on it. DO NOT SELECT Label and
Mount device after creation.
Type Y.
Type Y to continue.
11 Monitor the nsrdr recovery process and validate that it completes successfully.
12 Log in to NetWorker Management Console and launch NetWorker Administration. Validate that all
your custom configurations are recovered.
13 From the Media window, select Client Indexes and note that the client file indexes have been
rebuilt.
Step Action
The disk volume ServerBackup.001 will be used for this lab exercise.
2 From the Devices window, click Devices. Identify the ServerBackup.001 volume mounted on the
ddve.emc.edu_ddve_dev3 device.
Click OK and then click Yes to confirm the deletion of the volume from the database.
6 Notice the ServerBackup.001 volume has been removed from the list of disk volumes.
Run the following command to scan the volume you recently deleted back in to the database.
Note: If the screen doesn’t refresh automatically, click a different tab and click back.
Step Action
1 Close both the NetWorker Administration and NetWorker Management Console windows.
2 On the NetWorker backup server, shut down the NetWorker Management Console server service.
3 Simulate a disaster by deleting the NMC database files/folder (\pgdata\ and gstd_db.conf) in this
directory:
Validate that the NMC database files/folder (\pgdata\ and gstd_db.conf) are recovered.
7 Start the EMC GST Service. Log in to NetWorker Management Console and verify that your custom
configurations are recovered.