EMC NetWorker 9.0.x Administration Guide

EMC NetWorker 9.0.x Administration Guide
EMC® NetWorker®
Version 9.0.x
Administration Guide
302-001-764
REV 09
Copyright © 1990-2016 EMC Corporation. All rights reserved. Published in the USA.
Published October 2016
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
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.
EMC², EMC, and the EMC logo 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.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
2
EMC NetWorker 9.0.x Administration Guide
CONTENTS
Figures
15
Tables
17
Preface
21
Chapter 1
Overview
27
The NetWorker environment.......................................................................... 28
NetWorker components....................................................................28
NetWorker services....................................................................................... 30
Processes on NetWorker hosts ........................................................ 31
Stop and start the NMC server.......................................................... 33
Stop and start a NetWorker server, client, or storage node................35
NetWorker user interfaces............................................................................. 37
NMC user interface...........................................................................37
NetWorker Administration window................................................... 38
NetWorker client interface................................................................ 39
NetWorker character-based interface............................................... 39
NetWorker command-line interface.................................................. 39
Chapter 2
Getting Started
41
NetWorker Management Console interface.................................................... 42
Connecting to the Console window...................................................42
Connecting to the Administration window..................................................... 46
Opening the Administration window................................................ 46
Administration window.................................................................... 46
Editing multiple resources................................................................48
Drag-and-drop functionality............................................................. 48
Multiple library devices and slots..................................................... 50
Setting user interaction preferences.................................................50
Monitoring NetWorker server activities in the Administration window
........................................................................................................ 50
Getting started with a new installation.......................................................... 61
Common NetWorker tasks................................................................ 61
Chapter 3
Backup Storage
69
Label templates............................................................................................ 70
Using label templates...................................................................... 70
How the NetWorker server uses volume labels................................. 70
Preconfigured label templates..........................................................71
Guidelines for completing Label Template attributes........................ 71
Naming label templates................................................................... 73
Working with label templates........................................................... 74
Setting up a label template to identify volumes................................76
Media pools.................................................................................................. 76
Using media pools........................................................................... 77
EMC NetWorker 9.0.x Administration Guide
3
CONTENTS
Storage nodes...............................................................................................91
Requirements...................................................................................91
Licensing......................................................................................... 91
Storage node configuration.............................................................. 91
Configuring a dedicated storage node.............................................. 98
Troubleshooting storage nodes........................................................ 99
Disk storage devices................................................................................... 100
Example environment.................................................................... 101
Considerations for Client Direct clients...........................................101
Cloud backup devices compared to other device types.................. 103
Differences between FTDs, AFTDs, and DD Boost devices............... 104
Device target and max sessions default values and ranges............ 107
Advanced file type devices.............................................................107
DD Boost devices........................................................................... 121
CloudBoost devices....................................................................... 122
Atmos Cloud devices......................................................................128
Libraries and silos.......................................................................................133
Overview of tape device storage.....................................................133
Support for LTO-4 hardware-based encryption................................133
Linux device considerations........................................................... 133
Solaris device considerations........................................................ 134
HP-UX device considerations..........................................................134
AIX device considerations.............................................................. 138
SCSI and VTL libraries.................................................................... 138
Silo libraries...................................................................................175
NDMP libraries............................................................................... 183
NetWorker hosts with shared libraries............................................184
Dynamic drive sharing....................................................................186
File type devices..........................................................................................191
FTD capacity issues........................................................................ 191
Full FTD prevention.........................................................................192
Stand-alone devices....................................................................................192
Autodetecting and configuring a stand-alone tape drive.................192
Adding a stand-alone device manually........................................... 193
Auto Media Management for stand-alone devices.......................... 193
Mounting or unmounting a volume in a stand-alone tape drive...... 194
Labeling and mounting a volume in one operation (stand-alone tape
drive)............................................................................................. 195
Labeling volumes without mounting...............................................196
Mounting uninventoried volumes...................................................196
Labeling volumes........................................................................................ 197
Labeling or re-labeling library volumes........................................... 197
Verifying the label when a volume is unloaded...............................198
Troubleshooting devices and autochangers................................................ 198
Additional attributes in the Autochanger resource..........................198
Maintenance commands................................................................199
Autodetected SCSI jukebox option causes server to stop responding
...................................................................................................... 199
Autochanger inventory problems....................................................199
Destination component full messages............................................199
Tapes do not fill to capacity............................................................200
Tapes get stuck in drive when labeling tapes on Linux Red Hat
platform.........................................................................................200
Increasing the value of Save Mount Time-out for label operations.. 201
Server cannot access autochanger control port.............................. 201
Changing the sleep times required for TZ89 drive types..................202
4
EMC NetWorker 9.0.x Administration Guide
CONTENTS
Message displayed when CDI enabled on NDMP or file type device
...................................................................................................... 203
Verify firmware for switches and routers.........................................203
Commands issued with nsrjb on a multi-NIC host fail..................... 203
SCSI reserve/release with dynamic drive sharing........................... 203
Recovering save sets from a VTL on a different NetWorker server.... 204
Chapter 4
Data Protection Policies
205
Overview of data protection policies............................................................206
Designing data protection policies.............................................................. 207
Default data protection policies..................................................... 208
Road map for configuring a new data protection policy...................209
NetWorker resource considerations................................................210
Strategies for traditional backups.................................................. 210
Strategies for server backup and maintenance............................... 232
Strategies for cloning..................................................................... 241
Policy notifications......................................................................................263
Monitoring policy activity............................................................................ 263
Monitoring cloning......................................................................... 265
Policy log files............................................................................................. 265
Starting, stopping, and restarting data protection policies.......................... 267
Starting actions in a workflow for an individual client.................................. 267
Modifying data protection Policy resources................................................. 268
Policies.......................................................................................... 268
Workflows......................................................................................269
Protection groups...........................................................................277
Actions.......................................................................................... 278
Managing policies from the command prompt.............................................281
Creating Data Protection Policy resources from a command prompt
...................................................................................................... 282
Creating Action resources from a command prompt....................... 283
Starting, stopping, and restarting workflows from a command prompt
...................................................................................................... 283
Displaying Data Protection Policy resource configurations..............285
Troubleshooting policies............................................................................. 289
Chapter 5
Backup Options
291
Overview of resources that support backups............................................... 292
Save sets.................................................................................................... 292
The ALL save set.............................................................................293
Backup levels..............................................................................................295
Comparing backup levels............................................................... 296
Backup levels and data recovery requirements...............................297
Backup levels for the online indexes.............................................. 298
Synthetic full backups....................................................................298
Virtual synthetic full backups......................................................... 305
Backup scheduling......................................................................................308
Scheduling backup cycles..............................................................308
Considerations for scheduling backups..........................................309
Methods for scheduling backups................................................... 309
Overriding the backup schedule for a client resource..................... 311
Backup retention.........................................................................................314
Methods for setting retention......................................................... 314
Assigning a retention policy to a Client resource.............................315
EMC NetWorker 9.0.x Administration Guide
5
CONTENTS
Editing retention for a save set....................................................... 316
General backup considerations................................................................... 317
Renamed directories...................................................................... 317
Raw partitions................................................................................317
Access control lists........................................................................ 318
Client parallelism and parallel save streams.................................. 318
Maximum path and save set length................................................321
Open files...................................................................................... 321
Data deduplication........................................................................ 322
Directives....................................................................................................323
Types of directives......................................................................... 323
Format of directive statements....................................................... 323
Global directives............................................................................ 326
NetWorker User local directives......................................................329
Creating local directives................................................................. 330
Chapter 6
Backing Up Data
333
Configuring a Client resource for backups on Windows hosts ..................... 334
Windows backup considerations....................................................334
Windows file system backups........................................................ 343
Windows Bare Metal Recovery........................................................350
Creating a Client resource with the Client Backup Configuration wizard
...................................................................................................... 367
Mapped drives............................................................................... 372
Mapped drives............................................................................... 373
Configuring a Client resource for backups on UNIX hosts ............................ 373
UNIX/Linux backup considerations................................................ 373
Creating a Client resource with the Client Backup Configuration wizard
...................................................................................................... 375
Supported save set configurations for UNIX hosts.......................... 378
Configuring a Client resource for backups on Mac OS X hosts ..................... 381
Mac OS X backup considerations................................................... 381
Creating a Client resource with the Client Backup Configuration wizard
...................................................................................................... 381
Assigning directives to Mac OS X clients........................................ 384
Configuring Open Directory database backups............................... 384
Sending client data to AFTD or Data Domain devices only............................ 386
Non-ASCII files and directories.................................................................... 386
Configuring checkpoint restart backups...................................................... 386
About partial save sets...................................................................387
Partial saveset cloning and scanning............................................. 388
Checkpoint restart requirements.................................................... 388
Configuring checkpoint restart....................................................... 389
Restarting checkpoint-enabled backups.........................................390
Recovering data from partial save sets........................................... 391
Probe-based backups................................................................................. 391
Encryption and compression....................................................................... 392
Configuring encryption or compression for scheduled backups ..... 393
Configuring password protection, encryption, or compression for a
manual backup.............................................................................. 394
Compression...............................................................................................394
Configuring compression for scheduled backups........................... 394
Configuring compression for manual backups................................395
Configuring Client Direct backups................................................................395
Requirements for Client Direct backups..........................................395
6
EMC NetWorker 9.0.x Administration Guide
CONTENTS
Configuring Client Direct backups.................................................. 396
Backup command customization................................................................ 397
Creating a custom backup script.................................................... 397
Customizing backups with the pre and post commands................. 403
Client resources.......................................................................................... 403
Creating a Client resource with the Client Properties dialog box......404
Editing a Client resource................................................................ 405
Copying a Client resource...............................................................406
Changing the hostname of a client................................................. 407
Deleting a Client resource.............................................................. 408
Manual backups......................................................................................... 408
Performing a manual backup on Windows......................................408
Performing a manual backup from the command prompt............... 409
Performing a manual backup on Mac OS X..................................... 410
Troubleshooting manual backups.................................................. 410
Verifying backup data................................................................................. 410
Chapter 7
Cloning, Staging, and Archiving
413
Cloning, staging, and archiving................................................................... 414
Benefits of cloning and staging................................................................... 414
Cloning save sets and volumes................................................................... 415
Deciding when to clone.................................................................. 415
Clone retention.............................................................................. 415
Cloning requirements and considerations...................................... 416
Cloning example............................................................................ 418
Cloning with tape devices.............................................................. 418
Cloning with file type and AFTD devices..........................................420
Cloning with EMC Avamar...............................................................420
Cloning with Data Domain (DD Boost)............................................ 421
Controlling storage node selection for cloning................................421
Cloning save sets from a command prompt.................................... 424
Staging save sets........................................................................................ 428
Creating a staging resource............................................................ 429
Editing staging configurations........................................................432
Copying a Staging resource............................................................ 433
Deleting a staging policy................................................................ 433
Manual staging from the command prompt.................................... 433
Archiving data............................................................................................. 434
Storage of archived data................................................................ 435
Enabling archiving......................................................................... 436
Archiving data from Windows.........................................................437
Archiving data from UNIX............................................................... 437
Recovering archived data............................................................... 438
Troubleshooting NetWorker archiving and retrieval........................ 440
Chapter 8
Backup Data Management
443
Overview of backup data management........................................................444
Viewing volume and save set details........................................................... 444
Viewing disk volume details...........................................................444
Viewing tape volume details.......................................................... 445
Viewing save set details for a volume.............................................447
Viewing save set details from a search........................................... 448
Managing volumes......................................................................................452
Changing the volume mode............................................................452
EMC NetWorker 9.0.x Administration Guide
7
CONTENTS
Changing the volume recycle policy................................................453
Marking a tape volume as full for offsite storage............................ 453
Removing volumes from the media database and online indexes...454
Changing save set status.............................................................................455
Removing expired save sets........................................................................ 455
Save set management on tape devices...........................................456
Chapter 9
Recovery
457
Recovering data.......................................................................................... 458
NetWorker recovery overview.......................................................................458
Recovery types............................................................................................ 458
Directed recoveries........................................................................ 458
Local recoveries............................................................................. 463
Recover programs....................................................................................... 463
Using the NetWorker User program.................................................463
Using the NetWorker Recovery program..........................................464
Using the Recovery Wizard............................................................. 464
Using the recover command...........................................................469
Scanner recovery........................................................................... 469
Recovering the data.................................................................................... 470
Determining the volume for recovering cloned data........................470
Recovering access control list files................................................. 471
Browsable recovery........................................................................ 471
Save set recovery........................................................................... 483
Using the scanner program to recover data.................................... 488
VSS File Level Recovery.................................................................. 489
Recovering deduplication data.................................................................... 490
Recovering with Windows BMR....................................................................490
Overview of Windows Bare Metal Recovery (BMR)...........................490
Windows BMR Planning................................................................. 495
Performing a Windows BMR to physical or virtual computers.......... 504
Online recovery of Active Directory, DFSR, or Cluster services......... 520
Recovering file system data on Windows..................................................... 521
Recovering Windows volume mount points.................................... 521
Recovering Windows DHCP and WINS databases............................522
Recovering DFS.............................................................................. 522
Recovering data on OS-X clients.................................................................. 524
Recovering files and directories from the command prompt........... 524
Recovering files and directories by using the NetWorker Recover GUI
...................................................................................................... 524
Recovering client files on a different NetWorker server................................ 530
Recovering critical NetWorker server databases...........................................532
Prerequisites to recover the NetWorker server databases............... 533
Consider the recovery options........................................................ 536
Recovering critical NetWorker server databases............................. 536
Recovering the NMC server database...........................................................547
Chapter 10
Reporting NetWorker Datazone Activities
549
Enterprise data reporting.............................................................................550
Enabling or disabling the gathering of report data.......................... 550
Data retention and expiration policies............................................551
Restricted report views...................................................................552
Report categories........................................................................... 553
Legacy report categories................................................................ 553
8
EMC NetWorker 9.0.x Administration Guide
CONTENTS
Report modes and types................................................................ 554
Preconfigured reports.....................................................................561
Customizing and displaying report output...................................... 587
Customizing and saving reports..................................................... 590
Sharing a report............................................................................. 591
Command line reporting.................................................................592
Reporting policy status and backup job status............................................ 593
Policy completion and failure notifications.....................................593
Querying the job status.................................................................. 595
Reporting recover job status........................................................................612
Using nsrrecomp............................................................................ 612
Checkpoint-enabled backup reporting.........................................................613
View the savegroup reports for checkpoint-enabled client backups
...................................................................................................... 613
Determine the status of a checkpoint-enabled backup................... 614
SNMP traps................................................................................................. 614
Configuring NetWorker SNMP notifications.....................................615
NetWorker Notifications.............................................................................. 617
Preconfigured notifications............................................................ 617
Customizing notifications...............................................................622
Creating a custom notification........................................................625
Editing a notification...................................................................... 625
Copying a notification.................................................................... 625
Deleting a custom notification........................................................626
Configuring owner notifications......................................................626
Logging event notifications............................................................ 627
ConnectEMC................................................................................................627
Enabling ConnectEMC in NMC........................................................ 628
Enabling ConnectEMC by using nsradmin.......................................629
Report home............................................................................................... 630
Enabling the report home feature................................................... 631
Manually running a report home report.......................................... 631
Disabling the report home feature.................................................. 632
Specifying the sender email address..............................................632
Chapter 11
NetWorker Server Monitoring
635
Enterprise events monitoring.......................................................................636
Polling interval for system events................................................... 636
Enabling or disabling event capture for a host................................637
Event viewing.................................................................................637
Dismissing an event.......................................................................639
Monitoring NetWorker server activities in the Administration window.......... 639
About the Monitoring window........................................................ 640
Customizing the Monitoring window.............................................. 642
Policies/Actions pane.................................................................... 643
Sessions window........................................................................... 646
Alerts pane.................................................................................... 647
Devices pane................................................................................. 647
Operations window........................................................................ 648
Log window....................................................................................650
Recover window............................................................................. 651
Monitoring changes to the NetWorker and NMC Server resources................ 654
Disabling or enabling the Monitor RAP Attribute............................. 655
Monitoring user access to the NMC server................................................... 655
Monitoring NetWorker server activities in the log files................................. 655
EMC NetWorker 9.0.x Administration Guide
9
CONTENTS
Chapter 12
NMC Server Management
657
Enterprise................................................................................................... 658
Enterprise components.................................................................. 658
Organizing NetWorker servers........................................................ 658
Viewing the enterprise................................................................... 659
Managing various servers in the Enterprise.................................... 659
Managing folders in the enterprise.................................................661
Adding or deleting multiple servers by using a hostname file......... 663
Customizing the Console window and views................................................665
Connecting to the NMC GUI using an ssh connection................................... 666
Backing up the NetWorker environment.......................................................666
Configuring an NMC server database backup................................. 667
Performing a manual backup of the NMC server database.............. 668
Using the NMC Configuration Wizard........................................................... 669
NMC server authentication.......................................................................... 669
Configuring the NMC server to manage additional NetWorker servers
...................................................................................................... 669
Changing the authentication service hostname and port number... 670
Modifying user groups for new NetWorker Authentication Service users
...................................................................................................... 672
Adding the NMC service account to the Users user group............................ 674
Moving the NMC server................................................................................675
Migrating NMC users to the authentication service database.......................677
Updating the NetWorker User Group resources for migrated NMC users
...................................................................................................... 677
Resetting the administrator password......................................................... 678
Changing the service port used by the NMC database................................. 680
Changing the service port used by the NMC database on Linux...... 680
Changing the service port used by the NMC database on Windows.681
Changing database connection credentials................................................. 682
Updating the NMC server IP address/hostname.......................................... 683
Setting system options to improve NMC server performance....................... 683
Individual User Authentication....................................................... 685
Displaying international fonts in non-US locale environments..................... 686
NetWorker License Manager........................................................................ 686
Entering an enabler code............................................................... 686
Deleting an enabler code............................................................... 686
Entering an authorization code.......................................................687
Changing the License Manager server............................................ 687
NMC error messages and corrective actions................................................ 687
Console troubleshooting notes and tips...................................................... 691
Troubleshooting an NMC server that is not responding...................691
Unable to connect to host: Please check Security setting and daemon
logs on the NetWorker client and Console server for more information
...................................................................................................... 692
Username/password validation fails when you use the NMC New
Device wizard to configure an AFTD if storage node is UNIX............ 694
Querying large numbers of save sets in the NetWorker user interface
may cause a Java heap space error.................................................694
NMC user interface exits unexpectedly........................................... 694
Chapter 13
NetWorker Server Management
695
Setting up the server................................................................................... 696
License the NetWorker server......................................................... 696
10
EMC NetWorker 9.0.x Administration Guide
CONTENTS
Setting the Job inactivity timeout....................................................696
Modifying the retention period for jobs in the jobs database.......... 696
Viewing the migration log file...................................................................... 697
Hostname changes..................................................................................... 697
Managing the NSR task resource for nsrclientfix ......................................... 698
Parallelism and multiplexing....................................................................... 699
Parallelism.....................................................................................699
Multiplexing...................................................................................702
Managing server access.............................................................................. 703
Resource databases ................................................................................... 703
Viewing resources in the resource database...................................704
Repairing resource database corruption......................................... 704
Indexes....................................................................................................... 705
Characteristics of the online indexes..............................................705
Automated index activities.............................................................706
Checking online indexes................................................................ 706
Viewing information about the indexes.......................................... 706
Index save sets.............................................................................. 706
Querying the media database........................................................ 707
Cross-checking client file indexes.................................................. 708
Refreshing index information......................................................... 708
Client file index locations............................................................... 708
Managing the size of the online indexes.........................................710
Internationalization.....................................................................................713
Log file viewer................................................................................ 714
Display issues................................................................................714
Creating a server backup action.................................................................. 714
Creating an expire action.............................................................................718
Chapter 14
NetWorker Host Management
721
Administering the Hosts.............................................................................. 722
Controlling access to a NetWorker client......................................................722
NetWorker host management...................................................................... 722
Managing Package Manager........................................................................724
Changing the software repository location......................................725
Removing software package information from the software repository
...................................................................................................... 726
Transferring files and folders by using Package Manager................727
Windows client interface............................................................................. 730
Starting the NetWorker User program on Windows......................... 730
Toolbar buttons..............................................................................731
Browse window..............................................................................732
Connecting to a NetWorker server.................................................. 732
Editing a client NSRLA database.................................................................. 733
Chapter 15
Restricted Datazones
735
Restricted Datazones overview....................................................................736
Administrators and users of RDZ................................................................. 736
Using multiple instances of an RDZ................................................ 737
Setting up the RDZ...................................................................................... 737
Setting up an RDZ resource............................................................ 738
Setting up RDZ Users......................................................................742
Removing a resource association................................................................ 742
Backward compatibility...............................................................................743
EMC NetWorker 9.0.x Administration Guide
11
CONTENTS
Chapter 16
Block Based Backup and Recovery
745
Overview..................................................................................................... 746
Supported operating systems and configurations...........................747
Limitations.....................................................................................749
Block based backups.................................................................................. 749
Devices for block based backups................................................... 749
Installing the lgtobbb package on Linux......................................... 749
Configuring block based backups.................................................. 750
Performing block based backups................................................... 750
Verifying block based backups.......................................................753
Cloning block based backups........................................................ 753
Block based recoveries............................................................................... 754
Preparing for block based recoveries..............................................754
Performing block based recoveries.................................................754
Performing block based clone recoveries....................................... 758
Troubleshooting block based backup and recovery issues.......................... 760
Chapter 17
Networking and Connectivity
763
Name resolution and connectivity............................................................... 764
Troubleshooting name resolution and connectivity errors............................764
Verifying basic connectivity............................................................765
Verifying name resolution.............................................................. 768
Verifying the NetWorker configuration............................................ 771
Using multihomed systems......................................................................... 773
Multihomed system requirements.................................................. 773
Configuring multihomed hosts in a datazone................................. 774
NIC Teaming................................................................................................780
Using DHCP clients......................................................................................780
Chapter 18
Troubleshooting
781
Before you contact technical support.......................................................... 782
Determining the version of NetWorker software running on a client
...................................................................................................... 782
Displaying diagnostic mode attributes........................................... 783
NetWorker log files...................................................................................... 783
NetWorker server log files.............................................................. 783
NMC server log files....................................................................... 787
NetWorker client log files............................................................... 788
View log files..................................................................................791
Raw log file management............................................................... 795
Configuring logging levels.............................................................. 798
NetWorker Authentication Service logs........................................................807
NetWorker Authentication Service log files..................................... 807
Authentication Service server log file management........................ 808
CLI log file management................................................................. 809
NetWorker functionality issues.................................................................... 810
Backup and recovery......................................................................810
Backups fail to start when the daylight savings time change occurs
...................................................................................................... 813
Shut down NetWorker services prior to any significant changes to
system date................................................................................... 814
Clone ID timestamp does not reflect the time the clone was created
...................................................................................................... 814
12
EMC NetWorker 9.0.x Administration Guide
CONTENTS
Memory usage when browsing large save sets............................... 814
Memory usage and nsrjobd............................................................ 814
Media position errors encountered when auto media verify is enabled
...................................................................................................... 814
The scanner program marks a volume read-only.............................815
The scanner program requests an entry for record size................... 815
Limitations for groups containing a bootstrap................................ 815
Index recovery to a different location fails...................................... 815
Illegal characters in configurations.................................................816
Error backing up large number of clients........................................ 816
Hostname aliases.......................................................................... 816
Directory pathname restrictions..................................................... 817
Backup of a new client defaults to level full....................................817
Non-full backup of Solaris files with modified extended attributes. 817
Client file index errors.................................................................... 818
Cannot use the Console interface to stop the savegrp command.... 819
Aborting a recovery........................................................................ 819
xdr of win32 attributes failed for directory...................................... 819
Cannot create directory directory....................................................819
The All save set and duplicate drive serial numbers....................... 819
No disk label errors........................................................................ 820
Resolving copy violation errors.......................................................820
Converting sparse files to fully allocated files.................................820
Backing up large sparse files..........................................................821
Queries using the mminfo -N command are case-sensitive............. 821
Renamed directories and incremental backups.............................. 821
Resolving names for multiple network interface cards.................... 822
Libraries entering ready state......................................................... 822
Successful save sets listed as failed in the Group Backup Details
window.......................................................................................... 823
The NetWorker Server window does not appear on HP-UX...............823
NetWorker locale and code set support....................................................... 823
Enabling service mode for NetWorker.......................................................... 823
Network and server communication errors...................................................824
Unapproved server error.................................................................824
Unapproved server error during client setup...................................824
Server copy violation......................................................................824
Remote recover access rights......................................................... 825
Authentication fails due to duplicate hostnames............................825
NetWorker server takes a long time to restart................................. 825
Changing the NetWorker server address......................................... 826
Binding to server errors.................................................................. 826
New.Net and NetWorker software are incompatible........................ 827
Glossary
829
EMC NetWorker 9.0.x Administration Guide
13
CONTENTS
14
EMC NetWorker 9.0.x Administration Guide
FIGURES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
NetWorker components................................................................................................. 28
NMC GUI window........................................................................................................... 38
Associating a jnlp file with Java (TM) web Start Launcher for Mozilla Firefox................... 44
Administration window.................................................................................................. 47
Monitoring window........................................................................................................ 51
Recover window.............................................................................................................58
Labeling a volume by using a label template..................................................................70
Identifying WORM tapes in the NetWorker Console........................................................ 88
Example NetWorker disk backup configuration in a mixed backup environment...........101
Paths for CIFS AFTD......................................................................................................103
How library sharing works............................................................................................184
Dynamic Drive Sharing.................................................................................................187
Data Protection Policy..................................................................................................207
Platinum policy configuration...................................................................................... 208
Gold policy configuration.............................................................................................208
Silver policy configuration........................................................................................... 209
Bronze policy configuration......................................................................................... 209
Data protection policy example....................................................................................210
All possible workflow actions for a traditional backup..................................................216
Workflow path from a traditional backup action...........................................................216
Visual representation of a workflow............................................................................. 232
Workflow path from a server database backup action.................................................. 236
Workflow path from an NMC server backup action....................................................... 236
Visual representation of the Server Protection workflows............................................. 241
Workflow path from a clone action...............................................................................248
Visual representation of a clone workflow....................................................................253
Example of a policy with separate workflows for backup and cloning........................... 254
Workflow path from a snapshot backup action............................................................ 269
Workflow path from a probe action.............................................................................. 270
Workflow path from a server backup action................................................................. 270
Workflow path from a check connectivity action...........................................................270
Workflow path from a clone action...............................................................................270
Workflow path from a discover action.......................................................................... 271
Workflow path from a generate index action................................................................ 271
Workflow path from a VBA checkpoint discover action................................................. 271
Traditional backup workflow........................................................................................271
Incremental and cumulative incremental backup levels............................................... 298
Synthetic full backups................................................................................................. 299
Default weekly backup schedule..................................................................................308
Staggered weekly backup schedule for multiple groups of clients................................308
Default weekly schedule for a traditional backup action.............................................. 310
VSS backup process.................................................................................................... 345
Paths for CIFS AFTD......................................................................................................397
Cloning example..........................................................................................................418
Overview of archive operation......................................................................................435
A directed recovery from a remote client ..................................................................... 459
Connect to Server ....................................................................................................... 525
NetWorker Recover window......................................................................................... 526
List of clients available for a NetWorker server............................................................. 527
Search browse view..................................................................................................... 528
Versions side bar.........................................................................................................529
EMC NetWorker 9.0.x Administration Guide
15
FIGURES
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
16
Group Summary in table view...................................................................................... 555
Group Summary in Bar Chart view................................................................................556
ConnectEMC Properties in NMC................................................................................... 629
ConnectEMC resource configuration in nsradmin......................................................... 630
Monitoring window...................................................................................................... 640
Recover window...........................................................................................................652
NetWorker servers worldwide...................................................................................... 659
Copying the group DN.................................................................................................. 673
Copying the group DN.................................................................................................. 673
Add Distinguished Names window...............................................................................675
Host window................................................................................................................723
NetWorker User program..............................................................................................730
Example of the browse window....................................................................................732
Restricted Data Zones in NMC......................................................................................738
Create Restricted Data Zone in the NetWorker Administration Server window...............739
Restricted Data Zone Client Properties ........................................................................ 740
Restricted Data Zones in Device Properties window..................................................... 740
Restricted Data Zones in Create Policy window............................................................ 741
New workflow associated with RDZ group.................................................................... 741
Restricted Datazone User Configuration....................................................................... 742
Multihomed environment............................................................................................ 776
Configuring the Aliases attribute for NetWorker server Client resource......................... 777
Configuring the Aliases attribute for NetWorker storage node Client resource.............. 777
Storage nodes attribute for clients in VLAN1................................................................ 778
Aliases and Server network interface attributes for VLAN1 clients................................ 778
Storage node attribute for clients in VLAN2..................................................................779
Aliases and Server network interface attributes for VLAN2 clients................................ 779
WinPE registry key to troubleshoot recoveries.............................................................. 806
EMC NetWorker 9.0.x Administration Guide
TABLES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Revision history............................................................................................................. 21
Style conventions.......................................................................................................... 24
NetWorker server processes...........................................................................................31
NetWorker storage node processes................................................................................32
NMC server processes................................................................................................... 33
NetWorker startup commands .......................................................................................36
Windows opened from the NMC GUI...............................................................................38
Windows that are launched from the Administration window......................................... 47
Monitoring window panel ..............................................................................................52
Alerts window icons.......................................................................................................53
Devices status icons ..................................................................................................... 54
Operations window icons.............................................................................................. 55
Icons in the Log pane.....................................................................................................57
Recovery toolbar options .............................................................................................. 58
Save recover configuration job status............................................................................ 59
Find options.................................................................................................................. 60
Key label template attributes......................................................................................... 71
Examples of number sequences for volume labels......................................................... 72
Using label template components................................................................................. 73
Preconfigured media pools............................................................................................ 77
Determining which pool receives backup data............................................................... 79
NetWorker hierarchy for resolving media pool conflicts ................................................. 82
WORM supported devices ............................................................................................. 87
WORM/DLTWORM attributes ......................................................................................... 89
A comparison of cloud devices to other device types................................................... 103
Differences between disk devices ............................................................................... 104
Default values and ranges for target and max sessions attributes ............................... 107
CloudBoost appliance system requirements................................................................ 123
Determining the major number value........................................................................... 135
ioscan output when driver is configured...................................................................... 136
ioscan output when driver is not configured................................................................ 136
Tape alert severity....................................................................................................... 164
Common jbedit options............................................................................................... 166
Device settings and environment variables ................................................................. 172
StorageTek environment variables .............................................................................. 178
Library resource sleep attributes .................................................................................185
Shared Devices attributes............................................................................................190
Schedule icons............................................................................................................ 217
Schedule icons............................................................................................................ 220
Schedule icons............................................................................................................ 223
Schedule icons............................................................................................................ 228
Schedule icons............................................................................................................ 237
Save set criteria...........................................................................................................244
Schedule icons............................................................................................................ 249
Save set criteria...........................................................................................................256
Schedule icons............................................................................................................ 259
Policy status icons.......................................................................................................264
Methods to create an action........................................................................................ 278
Methods to open the Policy Action wizard....................................................................280
Resource overview.......................................................................................................292
Data in the ALL save set .............................................................................................. 293
EMC NetWorker 9.0.x Administration Guide
17
TABLES
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
18
File systems excluded from the ALL save set................................................................ 294
Special ALL save sets ..................................................................................................294
Backup levels ............................................................................................................. 295
Advantages and disadvantages of backup levels ........................................................ 296
mminfo commands for synthetic full backup validation .............................................. 304
Comparison of traditional synthetic full and virtual synthetic full backups................... 305
Requirements for virtual synthetic full backups............................................................305
mminfo commands for VSF backup validation .............................................................307
Backup schedule icons................................................................................................310
Preconfigured NetWorker schedules ........................................................................... 311
Log files for PSS troubleshooting................................................................................. 321
Preconfigured directives.............................................................................................. 326
Backup considerations for Windows features...............................................................335
VSS Save operation attribute values ........................................................................... 349
DISASTER_RECOVERY:\ components in an incremental backup....................................352
Save set configuration for a specific host .................................................................... 360
Special ALL save sets ..................................................................................................372
File systems excluded from the ALL save set................................................................ 379
Special ALL save sets ..................................................................................................379
NetWorker software requirements for checkpoint restart..............................................388
Example backup script on Windows.............................................................................399
Job control attribute selections.................................................................................... 401
List of nsrclone options and their descriptions.............................................................427
Staging criteria options................................................................................................430
Disk volumes window.................................................................................................. 444
Volume details............................................................................................................ 445
Save set details........................................................................................................... 447
Query criteria...............................................................................................................449
Save set search results view........................................................................................ 450
Query criteria...............................................................................................................451
VBA save set search results window............................................................................ 452
General recover requirements ..................................................................................... 459
Volume selection by recovery method..........................................................................470
Query criteria...............................................................................................................472
Save set status............................................................................................................ 474
Optional browsable recovery options .......................................................................... 478
Save set information....................................................................................................481
Optional save set recovery options ............................................................................. 484
Save set information....................................................................................................486
DISASTER_RECOVERY:\ components in an incremental backup....................................491
Save set configuration for a specific host .................................................................... 496
Additional recovery options......................................................................................... 519
Command line options for the nsrdr command............................................................ 545
Data retention policies.................................................................................................551
Report categories ........................................................................................................553
Legacy report categories ............................................................................................. 554
Report icons................................................................................................................ 554
Report chart formats.................................................................................................... 558
NetWorker recovery statistics parameters ................................................................... 574
Event parameters ........................................................................................................577
Host reports ................................................................................................................578
NetWorker backup statistics parameters .....................................................................579
NetWorker backup status parameters ......................................................................... 581
Cloud backup and recover parameters ........................................................................ 583
Clone report parameters ............................................................................................. 585
Date and time input formats for common locales......................................................... 589
EMC NetWorker 9.0.x Administration Guide
TABLES
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
Workflow-specific job record attributes........................................................................599
Action job record attributes......................................................................................... 602
Job details for a Workflow ........................................................................................... 609
Job details for a Workflow continued............................................................................609
Command-line options for nsrtrap ...............................................................................615
Preconfigured notifications ......................................................................................... 617
Actions ....................................................................................................................... 622
Priorities ..................................................................................................................... 624
Event Viewer messages ...............................................................................................627
NMC event information................................................................................................ 637
Event priorities ........................................................................................................... 638
Monitoring window panel ........................................................................................... 641
Policy status icons.......................................................................................................643
Alerts window icons.....................................................................................................647
Devices status icons ................................................................................................... 648
Operations window icons............................................................................................ 649
Icons in the Log pane...................................................................................................650
Recovery toolbar options ............................................................................................ 652
Save recover configuration job status.......................................................................... 653
Find options................................................................................................................ 654
Viewing the enterprise................................................................................................. 659
NMC server system options .........................................................................................683
Error messages or symptoms ...................................................................................... 687
Indexes window information........................................................................................706
Index save sets dialog box information........................................................................ 707
Backup icon details..................................................................................................... 715
Schedule icons for the expire action ........................................................................... 719
When to modify the servers file....................................................................................722
Summary pane............................................................................................................ 723
NetWorker User Groups requirements.......................................................................... 731
NetWorker User toolbar functions ............................................................................... 731
Supported backup and recovery scenarios...................................................................747
Key options for the block based recover.exe command................................................ 757
Troubleshooting block based backup and recovery issues...........................................760
Configuring multihomed hosts in NetWorker (continued)............................................. 774
NetWorker server log files............................................................................................ 783
NMC server log files..................................................................................................... 787
Client log files..............................................................................................................788
Message types ............................................................................................................793
Raw log file attributes that manage log file size........................................................... 795
Raw log file attributes that manage the log file trimming mechanism........................... 796
NetWorker Authentication Service log files...................................................................807
NetWorker Startup commands..................................................................................... 826
EMC NetWorker 9.0.x Administration Guide
19
TABLES
20
EMC NetWorker 9.0.x Administration Guide
Preface
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions that are described in this document
might not be supported by all versions of the software or hardware currently in use. The
product release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function correctly
or does not function as described in this document.
Note
This document was accurate at publication time. Go to EMC Online Support (https://
support.emc.com) to ensure that you are using the latest version of this document.
Purpose
This document describes how to configure and use EMC NetWorker.
Audience
This guide is part of the NetWorker documentation set, and is intended for use by system
administrators who are responsible for setting up and maintaining backups on a network.
Operators who monitor daily backups will also find this guide useful.
Revision history
The following table presents the revision history of this document.
Table 1 Revision history
Revision
Date
Description
01
September 24,
2015
First release of this document for EMC NetWorker 9.0.
02
December 16, 2015 Includes updates to:
03
l
"Recovering critical NetWorker server databases"
section of the Recovery chapter.
l
"Recovering with Windows BMR" section of the
Recovery chapter.
l
"Preconfigured notifications" in the NetWorker Server
Monitoring chapter.
December 30, 2015 Updated information for checkpoint restart to indicate the
feature is only supported on Linux and UNIX platforms,
and only for standard save operations.
Added step to the section "Resetting the administrator
password" in
the NMC Server Management chapter.
04
January 15, 2016
Updated the Backing up the Data chapter to include:
l
Details about how to configure a client to send data
to only AFTD and Data Domain devices.
EMC NetWorker 9.0.x Administration Guide
21
Preface
Table 1 Revision history (continued)
Revision
Date
Description
l
05
Includes updates to:
l
The Backing up Data and Recovery chapters to
include information about limitations when browsing
a large number of files on a client host.
l
The Cloning, Staging, and Archiving chapter to
include information about enabling Diagnostic mode
in the "Enabling archiving" section. Removal of the
topic "Recovering indexed archive data from a
Windows client"
l
The "Deduplication with Avamar" section in the
Backup Options chapter to clarify Avamar support.
l
The "Overview of data protection policies" section in
the Data Protection Policies chapter to clarify an
Action.
06
June 29, 2016
Updated to include information specific to the NetWorker
9.0.1 release.
07
Aug 18, 2016
Includes updates to:
08
09
22
April 22, 2016
Performance considerations for aes encryption.
EMC NetWorker 9.0.x Administration Guide
September 14,
2016
October 11, 2016
l
The "CloudBoost" section of the Backup Storage
chapter to include information about setting up and
configuring a CloudBoost device with the
remotebackup user.
l
Various updates to the "Reporting policy status and
backup job status" section in the Reporting
NetWorker Datazone Activities chapter.
l
The "Creating a Client resource with the Client Backup
Configuration wizard" section in the Backing up Data
chapter with information about how to specify the
name of a client.
Includes updates to:
l
"CloudBoost" section in the Backup Storage chapter
to clarify content.
l
"Preparing for a block based recovery" section in the
Block Based Backup and Recovery chapter with
information recovering BBB data from a CloudBoost
device.
l
"Prerequisites to recover the NetWorker server
databases" section of the recovery chapter to clarify
the need to reinstall the NetWorker server software
and OS software in a disaster recovery scenario.
Includes updates to:
Preface
Table 1 Revision history (continued)
Revision
Date
Description
l
"CloudBoost" section in the Backup Storage chapter
to include information about how to configure a
storage node for CloudBoost data.
l
Backup Options and Backing Up Data chapters to
include information about how to backup BTRFS subvolumes.
l
Data Protection Policies and Reporting NetWorker
Datazone Activities chapters to include information
about how to configure notifications on a NetWorker
Virtual Edition (NVE) appliance.
Related documentation
The NetWorker documentation set includes the following publications, available on EMC
Online Support:
l
EMC NetWorker Online Software Compatibility Guide
Provides a list of client, server, and storage node operating systems supported by the
EMC information protection software versions. You can access the guide at https://
support.emc.com. From the Support by Product pages, search for NetWorker using
"Find a Product", and then select the Install, License, and Configure link.
l
EMC NetWorker Administration Guide
Describes how to configure and maintain the NetWorker software.
l
EMC NetWorker Network Data Management Protocol (NDMP) User Guide
Describes how to use the NetWorker software to provide data protection for NDMP
filers.
l
EMC NetWorker Cluster Integration Guide
Contains information related to configuring NetWorker software on cluster servers
and clients.
l
EMC NetWorker Installation Guide
Provides information on how to install, uninstall, and update the NetWorker software
for clients, storage nodes, and servers on all supported operating systems.
l
EMC NetWorker Updating from a Previous Release Guide
Describes how to update the NetWorker software from a previously installed release.
l
EMC NetWorker Release Notes
Contains information on new features and changes, fixed problems, known
limitations, environment and system requirements for the latest NetWorker software
release.
l
EMC NetWorker Command Reference Guide
Provides reference information for NetWorker commands and options.
l
EMC NetWorker Data Domain Boost Integration Guide
Provides planning and configuration information on the use of Data Domain devices
for data deduplication backup and storage in a NetWorker environment.
l
EMC NetWorker Performance Optimization Planning Guide
Contains basic performance tuning information for NetWorker.
l
EMC NetWorker Server Disaster Recovery and Availability Best Practices Guide
Describes how to design and plan for a NetWorker disaster recovery. However, it does
not provide detailed disaster recovery instructions. The Disaster Recovery section of
EMC NetWorker 9.0.x Administration Guide
23
Preface
the NetWorker Procedure Generator (NPG) provides step-by-step disaster recovery
instructions.
l
EMC NetWorker Snapshot Management Integration Guide
Describes the ability to catalog and manage snapshot copies of production data that
are created by using mirror technologies on EMC storage arrays.
l
EMC NetWorker Snapshot Management for NAS Devices Integration Guide
Describes how to catalog and manage snapshot copies of production data that are
created by using replication technologies on NAS devices.
l
EMC NetWorker VMware Integration Guide
Provides planning and configuration information on the use of VMware in a
NetWorker environment.
l
EMC NetWorker Error Message Guide
Provides information on common NetWorker error messages.
l
EMC NetWorker Licensing Guide
Provides information about licensing NetWorker products and features.
l
EMC NetWorker REST API Getting Started Guide
Describes how to configure and use the NetWorker REST API to create programmatic
interfaces to the NetWorker server.
l
EMC NetWorker REST API Reference Guide
Provides the NetWorker REST API specification used to create programmatic
interfaces to the NetWorker server.
l
EMC NetWorker Management Console Online Help
Describes the day-to-day administration tasks performed in the NetWorker
Management Console and the NetWorker Administration window. To view the online
help, click Help in the main menu.
l
EMC NetWorker User Online Help
Describes how to use the NetWorker User program, which is the Windows client
interface, to connect to a NetWorker server to back up, recover, archive, and retrieve
files over a network.
Special notice conventions that are used in this document
EMC uses the following conventions for special notices:
NOTICE
Identifies content that warns of potential business or data loss.
Note
Contains information that is incidental, but not essential, to the topic.
Typographical conventions
EMC uses the following type style conventions in this document:
Table 2 Style conventions
Bold
Used for names of interface elements, such as names of buttons, fields,
tab names, and menu paths (what the user specifically selects or
clicks)
Italic
Used for full titles of publications that are referenced in text
Monospace
Used for:
l
24
EMC NetWorker 9.0.x Administration Guide
System code
Preface
Table 2 Style conventions (continued)
l
System output, such as an error message or script
l
Pathnames, file names, prompts, and syntax
l
Commands and options
Monospace italic
Used for variables
Monospace bold
Used for user input
[]
Square brackets enclose optional values
|
Vertical bar indicates alternate selections - the bar means “or”
{}
Braces enclose content that the user must specify, such as x or y or z
...
Ellipses indicate non-essential information that is omitted from the
example
Where to get help
EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or information about EMC products,
go to EMC Online Support at https://support.emc.com.
Technical support
Go to EMC Online Support and click Service Center. Several options for contacting EMC
Technical Support appear on the site. Note that to open a service request, you must have
a valid support agreement. Contact your EMC sales representative for details about
obtaining a valid support agreement or with questions about your account.
Online communities
Go to EMC Community Network at https://community.emc.com for peer contacts,
conversations, and content on product support and solutions. Interactively engage online
with customers, partners, and certified professionals for all EMC products.
Your comments
Your suggestions help to improve the accuracy, organization, and overall quality of the
user publications. Send your opinions of this document to
DPAD.Doc.Feedback@emc.com.
EMC NetWorker 9.0.x Administration Guide
25
Preface
26
EMC NetWorker 9.0.x Administration Guide
CHAPTER 1
Overview
This chapter contains the following topics:
l
l
l
The NetWorker environment.................................................................................. 28
NetWorker services............................................................................................... 30
NetWorker user interfaces..................................................................................... 37
Overview
27
Overview
The NetWorker environment
The EMC® NetWorker® environment provides the ability to protect an enterprise against
data loss. As the enterprise grows, so does the complexity and importance of protecting
data. The NetWorker software provides the power and flexibility to meet these
challenges.
The NetWorker software is a cross-platform, client/server application that provides the
ability to remotely manage all NetWorker servers from a web-enabled, graphical interface.
NetWorker components
Several components make up the NetWorker environment and provide the ability to
protect against data loss.
The following figure illustrates the main components in a NetWorker environment.
Figure 1 NetWorker components
NMC Server
The NetWorker Management Console (NMC) server or Console server is a Java-based web
application and database server. The NMC Server manages all NetWorker Servers and
Clients. The NMC Server also provides reporting and monitoring capabilities for all
NetWorker Servers and Clients in the environment. NMC Server relies on the NetWorker
Authentication Service for user account authentication.
28
EMC NetWorker 9.0.x Administration Guide
Overview
Datazone
A NetWorker datazone is composed of a single NetWorker Server, its clients, and storage
nodes. You can add additional datazones as backup requirements increase.
NetWorker Authentication Service
The NetWorker Authentication Service provides centralized token-based authentication to
components in a NetWorker 9.0.x environment. You can configure the NetWorker
Authentication Service to use a local user database or external identity providers (LDAP
and AD) for authentication.
NetWorker Server
The NetWorker Server provides services to back up and recover the data of any NetWorker
host in a datazone. The NetWorker Server also acts as a storage node and can control
multiple remote storage nodes.
NetWorker client
A NetWorker client is a physical computer that you install the NetWorker client software
on. The NetWorker client computer can be any computer in a datazone that contains data
you want to back up. The NMC server, NetWorker server, and NetWorker storage node
hosts are also NetWorker clients.
NetWorker client resource overview
A NetWorker client resource defines the data that you want to back up on a host. You can
create multiple client resources for a NetWorker host, and each resource defines a
different dataset.
EMC provides the NetWorker client software for a variety of operating system platforms.
Any NetWorker server can backup a NetWorker client, regardless of the platform the client
resides on. For example, you can back up a NetWorker client on a Microsoft Windows
computer to a NetWorker server on a Solaris computer.
NetWorker Storage Node
NetWorker can back up data to local devices on a NetWorker Server or remote devices on
a storage node. A storage node controls storage devices such as tape drives, disk
devices, autochangers, and silos.
The NetWorker Server is a local storage node. Use a remote storage node to offload most
of the data movement in a backup or a recovery operation from the NetWorker Server. A
remote storage node improves performance, but it requires high I/O bandwidth to
manage data transfer from local clients or network clients to target devices. The operating
system of a remote storage node can differ from the NetWorker Server.
NetWorker REST API
The NetWorker REST API is an interface that allows customer to access the NetWorker
data protection service and to build client applications that automate NetWorker
operations. The EMC NetWorker REST API Getting Started Guide describes how to use
NetWorker REST API, and the EMC NetWorker REST API Reference Guide provides a full
description of the API resources.
NetWorker components
29
Overview
EMC Licensing Solution
NetWorker 9.0.x introduces the EMC Licensing Solution, a new EMC standard for licensing
in software products. The EMC Licensing Solution uses an EMC License Server and reads
a license file to determine which products are licensed and how much storage space to
request for each datazone in the environment.
All new installations of NetWorker 9.0.x use the EMC Licensing Solution. The chapter
"EMC Licensing Solution" in the EMC NetWorker Licensing Guide provides information on
how to implement the EMC Licensing Solution for new and upgraded installations of
NetWorker 9.0.x. The "EMC Licensing Solution" chapter also describes the new EMC
License Server and the use of the license file.
Restricted datazones
Restricted datazones provide NetWorker administrators with the ability to organize a
NetWorker environment into a multi-tenancy configuration.
In a multi-tenancy configuration, each restricted datazone contains one NetWorker server
and other associated NetWorker resources. Global administrators oversee the setup and
management of several restricted data zones and assign tenant administrators with
access to a restricted datazone. A tenant administrator can only manage NetWorker
resources within an assigned restricted datazone.
Deduplication storage systems
The NetWorker software supports backup data deduplication on Data Domain® storage
systems.
The EMC NetWorker Data Domain Boost Integration Guide provides detailed information
about setting up DD Boost deduplication devices to work with NetWorker.
Virtual environments
NetWorker clients can be created for virtual machines for either traditional backup or
VMware Consolidated Backup (VCB). Additionally, the NetWorker software can
automatically discover virtual environments and changes to those environments on either
a scheduled or on-demand basis and provides a graphical view of those environments.
NetWorker services
The main services and programs for the NetWorker server are the NetWorker storage
node, NetWorker client, and NetWorker Management Console (NMC) server.
This section includes information on the NetWorker services, and how to start and stop
the services.
For more information about:
30
l
Main NetWorker services—The EMC NetWorker Command Reference Guide or the UNIX
man pages provides more information.
l
Service port requirements when configuring a firewall—The EMC NetWorker Security
Configuration Guide provides more information.
EMC NetWorker 9.0.x Administration Guide
Overview
Processes on NetWorker hosts
Each NetWorker host requires processes to provide configuration and management
support of the NetWorker software.
NetWorker authentication service
To support the NetWorker authentication service feature, one or more tomcat processes
start on the NetWorker server. The tomcat process provides the authentication service
with a database server instance, which enables the authentication service to manage
tokens and supports user database management.
NetWorker REST API
The NetWorker REST API service is deployed in the same Apache Tomcat container as
NetWorker authentication service. The NetWorker REST API uses the same set of Tomcat
processes to deliver its service.
NetWorker client
The nsrexecd process runs on a NetWorker client. This process authenticates and
manages NetWorker server remote execution requests and starts the save and savefs
processes on the client to support backup requests.
NetWorker server
The following table summarizes the processes that support the NetWorker server
software.
Table 3 NetWorker server processes
Process
Function
nsrd
l
The master service that controls other services on the NetWorker
server, clients, and storage nodes.
l
Monitors active save or recover program sessions.
l
In response to a recover session, nsrd spawns an agent process,
ansrd.
nsrmmdbd
Provides media database management services to the local nsrd and
nsrmmd services and records entries in the media database.
nsrjobd
Monitors NetWorker activity during a backup or recovery operation.
nsrindexd
Provides a method for inserting entries into the client file index that is
based on information that is passed by the save program.
nsrmmgd
nsrlogd
nsrcpd
l
Manages tape library operations.
l
Provides an RPC-based service that manages all jukebox operations
on behalf of the nsrd service.
l
The nsrd service starts only one instance of nsrmmgd on the
NetWorker server as needed.
Supports the NetWorker audit log service, which is configured to run on
the NetWorker server by default.
l
Starts automatically when a user accesses the Hosts Task window in
the NetWorker Administration interface.
Processes on NetWorker hosts
31
Overview
Table 3 NetWorker server processes (continued)
Process
Function
l
Allows users to distribute and upgrade NetWorker and module
software from a centralized software repository across a network.
nsrdispd
Handles RPC-based calls for the nsrd process, from remote third party
processes.
nsrdisp_nwbg
Started by nsrdispd to handle NMC server requests for information from
the RAP and media databases on the NetWorker server.
nsrlmc
l
Supports licensing requests.
l
For the traditional licensing model, nsrlmc requests a license from
the lgtolmd process.
l
For the CLP/ELMS licensing model, nsrlmc requests capacity and
update licenses from the ELMS server.
nsrctld
The top-level NetWorker server process that monitors, stops, and starts all
NetWorker server processes.
nsrvmwsd
Provides a web service to manage VMware VM backups that are part of
the NetWorker VMware protection feature.
tomcat7
(Windows), tomcat
(UNIX)
Tomcat web server instance for the NetWorker Authentication Service.
NetWorker storage node
The following table summarizes the services that support the NetWorker storage node
software.
Table 4 NetWorker storage node processes
Process
Function
nsrmmd
l
Provides device support, generates mount requests, multiplexes save set data
during a multi client backup, and de-multiplexes recover data. It writes the data
sent by save to storage media.
l
Forwards storage information to the nsrmmdbd process on the NetWorker server,
which the NetWorker server adds to the media database.
l
Provides an RPC-based service to manage all the device operations that the
nsrmmd process handles on behalf of the nsrd process on the NetWorker server.
l
Ensures that the necessary device operations are actually performed when
needed by nsrd.
l
Automatically run by nsrd as required.
l
Only one nsrsnmd runs on each storage node that has configured and enabled
devices.
l
Provides a uniform library interface to the NetWorker media management
daemon, nsrmmgd.
nsrsnmd
nsrlcpd
32
EMC NetWorker 9.0.x Administration Guide
Overview
Table 4 NetWorker storage node processes (continued)
Process
Function
l
Manages the library subsystem media, slot, drive, and port resources providing
control to move and access the resources within the library subsystems.
l
One nsrlcpd starts for each configured tape library.
NMC server
The following table summarizes the processes that support the NMC server software.
Table 5 NMC server processes
Process
Function
nsrexecd
Authenticates and processes the NetWorker server remote
execution requests and runs the save and savefs programs on
the client.
gstd
Known as the Generic Services Toolkit (GST), controls other
services that are provided by the NMC server.
httpd
Starts the NMC Console GUI on the client through a web
browser.
postgres
A database server that manages information pertaining to NMC
server management. For example, Console reports.
gstsnmptrapd
l
Monitors SNMP Traps on a managed Data Domain system.
l
Provides the ability to report SNMP Trap events in the NMC
Events task.
l
Started only when SNMP Trap monitoring is configured for
the Data Domain system.
Stop and start the NMC server
To complete some tasks in the NetWorker software, stop and start the NetWorker Console
service.
Stopping the NMC server on Windows
Perform the following steps as a Windows administrator to stop the NMC server service,
which also stops the postgres and httpd processes.
Procedure
1. Right-click My Computer and select Manage.
2. Expand Services and Applications and select Services.
3. Right-click EMC GST Service and select Stop.
Stop and start the NMC server
33
Overview
Note
The EMC GST Service stops the EMC GST Database Service and the EMC GST Web
Service.
Starting the NMC server on Windows
Perform the following steps as a Windows administrator to start the NMC server service,
which also starts the postgres and httpd processes.
Procedure
1. Right-click My Computer and select Manage.
2. Expand Services and Applications and select Services.
3. Verify that the NetWorker client is running.
The NetWorker Remote Exec Service should have a status of Started. If the service has
not started:
a. Right-click NetWorker Remote Exec Service.
b. Select Start.
4. Right-click EMC GST Service, then select Start.
Note
The EMC GST Service starts the EMC GST Database Service and the EMC GST Web
Service.
Stopping the NMC server on Linux
Perform the following steps as root on the NMC server to stop the NMC server process,
which also stops the postgres and httpd processes.
Procedure
1. To stop the NMC server processes, type /etc/init.d/gst stop.
2. To confirm that the gstd, httpd, and postgres process are not running, type ps ef | grep lgtonmc
Starting the NMC server processes on Linux
Perform the following steps as root on the NMC server to start the NMC process, which
also starts the postgres and httpd processes.
Procedure
1. To verify that the NetWorker client process, nsrexecd is running, type ps -ef |
grep /usr/sbin/nsr .
When the client process is running, a message similar to the following appears:
root 240 1 0 ? 0:04 /usr/sbin/nsrexecd -s mysrvr
If nsrexecd is not running, type /etc/init.d/networker start to start the
process.
2. To start the NMC server daemon, postgres, and httpd processes., type /etc/
init.d/gst start
34
EMC NetWorker 9.0.x Administration Guide
Overview
3. To confirm that the gstd, postgres, and httpd processes have started, type ps ef | grep lgtonmc.
When the processes have started, output similar to the following appears:
root 3064 1 0 10:03 ? 00:00:01 /opt/lgtonmc/bin/gstd
dbuser 3329 1 0 10:04 ? 00:00:00 /opt/lgtonmc/postgres/bin/
postgres -D /opt/lgtonmc/nmcdb/pgdata
root 3969 1 0 10:04 ? 00:00:00 /opt/lgtonmc/apache/bin/httpd
-f /opt/lgtonmc/apache/conf/httpd.conf
nobody 3970 3969 0 10:04 ? 00:00:00 /opt/lgtonmc/apache/bin/
httpd -f /opt/lgtonmc/apache/conf/httpd.conf
Stop and start a NetWorker server, client, or storage node
This section describes how to manually stop and start the services for a NetWorker
server, client, or storage node. In NetWorker 8.0 and later, new attributes have been
introduced to configure a NetWorker server to not accept any new backup or recover
sessions in preparation of a NetWorker daemon shutdown or server restart.
EMC NetWorker Security Configuration Guide provides more information around how to
prevent the NetWorker server from accepting new backup and recover sessions
Stopping a NetWorker host on Windows
Perform the following steps as a Windows administrator to stop the services on a
NetWorker server, storage node, and client.
Procedure
1. Right-click My Computer and select Manage.
2. Expand Services and Applications and select Services.
3. Right-click NetWorker Remote Exec Service and select Stop.
Note
On a NetWorker server, the NetWorker Remote Exec Service stops the NetWorker
Backup and Recovery and the NetWorker Message Queue Adaptor services. On an
NMC server, the NetWorker Remote Exec Service also stops the EMC GST Service.
Starting a NetWorker host on Windows
Perform the following steps as a Windows administrator to start the services on a
NetWorker server, storage node, and client.
Procedure
1. Right-click My Computer and select Manage.
2. Expand Services and Applications and select Services.
3. Start the appropriate service:
l
NetWorker server: Right-click the NetWorker Backup and Recover Server service
and select Start.
Stop and start a NetWorker server, client, or storage node
35
Overview
Note
The NetWorker Backup and Recover Server service also starts the NetWorker
Remote Exec Service and the NetWorker Message Queue Adaptor service.
l
NetWorker client or storage node: Right-click the NetWorker Remote Exec Service
and select Start.
Stopping a NetWorker host on UNIX
Perform the following steps as the root user to stop the NetWorker processes on a
NetWorker server, storage node, or client.
Procedure
1. To stop the NetWorker processes, type the following command from a prompt:
/etc/init.d/networker stop
2. To confirm that the NetWorker processes are not running, type the following command
from a prompt:
ps -ef | grep /usr/sbin/nsr
Starting a NetWorker host on UNIX
Perform the following steps as the root user to start the NetWorker processes on a
NetWorker server, storage node, or client.
Procedure
1. Type the appropriate startup command for the operating system, as summarized in
the following table.
Table 6 NetWorker startup commands
Operating system Startup command
Solaris, Linux
/etc/init.d/networker start
HP-UX
/sbin/init.d/networker start
AIX
/etc/rc.nsr
2. Type /etc/init.d/networker status to confirm that the NetWorker processes
that are appropriate to the NetWorker installation type have started.
Processes on NetWorker hosts on page 31 provides more information.
Stopping the NetWorker processes on Mac OS X
Perform the following steps as a Mac Administrator to stop the NetWorker processes on a
Mac OS X host.
Procedure
1. Open the Mac OS-X Terminal application utility.
2. To stop the NetWorker processes, type the following command:
launchctl unload /Library/LaunchDaemons/com.emc.NetWorker.plist
36
EMC NetWorker 9.0.x Administration Guide
Overview
Note
The launchd daemon/agent manager controls the NetWorker processes, and
NetWorker configures the processes to run continuously on the host in the
background. EMC does not recommend that you manually stop and start NetWorker
processes under normal operating conditions.
Starting the NetWorker process on Mac OS X
Perform the following steps as a Mac Administrator to start the NetWorker processes on a
Mac OS X host.
Procedure
1. Open the Mac OS X Terminal application utility.
2. Type launchctl load /Library/LaunchDaemons/com.emc.NetWorker.plist to
start the NetWorker client process.
NetWorker user interfaces
The NetWorker application consists of several user interfaces that provide the ability to
configure and use NetWorker features and functionality.
NMC user interface
The NMC server uses httpd to provide administrators with a graphical user interface to
connect to an NMC server and managed NetWorker servers. The NMC UI can be accessed
from any computer in the environment with a supported web browser and Java Runtime
Environment (JRE).
The EMC NetWorker Installation Guide provides more information about the web browser
and JRE requirements for a host that runs the NMC UI. Multiple users can use different
browser sessions on different hosts to access the NMC UI simultaneously.
NMC GUI
Use the NMC GUI to manage an NMC server and NetWorker servers.
The following figure illustrates the NMC GUI.
NetWorker user interfaces
37
Overview
Figure 2 NMC GUI window
The NMC window is the first point of access for NMC and NetWorker tasks. The following
table lists the task-based windows that can be opened from the NMC window taskbar.
Table 7 Windows opened from the NMC GUI
Button
Window
Description
Enterprise Select a NetWorker server to manage and monitor the server and its
backup clients. The Enterprise window provides the ability to open the
Administration window for a NetWorker server.
Reports
Configure and view NMC reports.
Setup
Control administrative functions:
l
User management — Add, edit, and delete NMC user accounts,
restrict user views of servers. The EMC NetWorker Security
Configuration Guide provides information about user management.
l
License management — Manage NetWorker licenses. The EMC
NetWorker Licensing Guide provides information about license
management.
NetWorker Administration window
The NetWorker Administration window provides you with the ability to manage and
configure NetWorker server resources in a GUI. The NMC UI provides you with the ability
to open up a NetWorker Administration window for each managed NetWorker server.
38
EMC NetWorker 9.0.x Administration Guide
Overview
NetWorker client interface
Manual back up, recovery, and archive operations can be performed from a client.
Manual operations are not scheduled. They are client-initiated tasks that are performed
when a user wants to back up, recover, or archive one or more files on the NetWorker host
immediately. You can schedule backup, recovery, and archive operations in the NMC GUI.
On Windows hosts only, you can use the NetWorker User GUI to perform manual back up,
recovery, and archive operations.
On UNIX and Windows hosts, you can use command line utilities to perform manual
operations:
l
Use the save command to perform a manual backup.
l
Use the recover command to perform a manual recovery.
l
Use the nsarchive command to perform a manual archive.
The EMC NetWorker Command Reference Guide or the UNIX man pages provide more
information about these commands.
NetWorker character-based interface
Use the NetWorker character-based interface (nsradmin) to perform configuration and
management tasks in the NetWorker server resource database (resdb) and the NetWorker
client resource database (nsrexec).
You can start the nsradmin interface by using this command:
nsradmin
For more information about nsradmin, the EMC NetWorker Command Reference Guide or
the UNIX man pages provides more information.
NetWorker command-line interface
Perform client and server tasks by typing commands at the prompt. The EMC NetWorker
Command Reference Guide or the UNIX man pages provides information about these
commands.
NetWorker client interface
39
Overview
40
EMC NetWorker 9.0.x Administration Guide
CHAPTER 2
Getting Started
This chapter contains the following topics:
l
l
l
NetWorker Management Console interface............................................................ 42
Connecting to the Administration window............................................................. 46
Getting started with a new installation.................................................................. 61
Getting Started
41
Getting Started
NetWorker Management Console interface
The interface for NetWorker Management Console (NMC), also called the NetWorker
Console, consists of both the Console window, and the Administration window.
Connecting to the Console window
The following sections describe how to connect to the Console window:
Before you connect
Ensure that you configure the NetWorker datazone correctly, and that the required
daemons are running on the NetWorker server and the NMC server.
l
Linux NetWorker Server—To confirm that the NetWorker daemons have started, from a
command prompt, type the /etc/init.d/networker status For a NetWorker
server, the nsrctld daemon starts. The nsrctld daemon starts other processes
that the NetWorker server requires. Output similar to the following appears when the
daemons are started:
+--o nsrctld (29021)
+--o epmd (29029)
+--o rabbitmq-server (29034)
+--o beam (29038)
+--o inet_gethost (29144)
+--o inet_gethost (29145)
+--o jsvc (29108)
+--o jsvc (29114)
+--o nsrd (29123)
+--o java (29135)
+--o nsrmmdbd (29828)
+--o nsrindexd (29842)
+--o nsrdispd (29853)
+--o nsrjobd (29860)
+--o nsrvmwsd (29968)
+--o connectemc (29131)
+--o eventservice.ru (29154)
+--o jsvc (29158)
+--o jsvc (29159)
+--o java (29838)
+--o node-linux-x64- (29885)
+--o nsrexecd (29004)
+--o nsrlogd (29899)
+--o nsrsnmd (30038)
l
Linux NMC Server:
1. Type ps -ef | /usr/sbin/nsrexecd. Output similar to the following
should appear:
root 24959 1 1 13:29 ? 00:00:00 /usr/sbin/nsrexecd
If you do not see this output, type /etc/init.d/networker start.
2. Type ps -ef | grep lgtonmc. Output similar to the following should
appear:
root 3064 1 0 10:03 ? 00:00:01 /opt/lgtonmc/bin/gstd
dbuser 3329 1 0 10:04 ? 00:00:00 /opt/lgtonmc/
postgres/bin/postgres -D /opt/lgtonmc/nmcdb/pgdata
root 3969 1 0 10:04 ? 00:00:00 /opt/lgtonmc/apache/bin/
httpd -f /opt/lgtonmc/apache/conf/httpd.conf
42
EMC NetWorker 9.0.x Administration Guide
Getting Started
nobody 3970 3969 0 10:04 ? 00:00:00 /opt/lgtonmc/
apache/bin/httpd -f /opt/lgtonmc/apache/conf/httpd.conf
l
Windows NetWorker Server:
1. Confirm that the following services are started: NetWorker Backup and Recover
Server, NetWorker Message Queue Adaptor, and NetWorker Remote Exec Service.
2. If these services are not started, start the NetWorker Backup and Recover Server
Service.
l
Windows NMC Server:
1. Confirm that the following services are started: EMC GST Database Service, EMC
GST Service, and EMC GST Web Service.
2. If these services are not started, start the EMC GST service.
Connecting to the NMC server GUI
Complete the following procedure to connect to the NMC Server GUI from an NMC client.
By default, the NetWorker Authentication Service uses the local user database for user
authentication. Specify the NetWorker Authentication Service administrator account to
log in to the NMC Server. The EMC NetWorker Security Configuration Guide describes how to
configure the NetWorker Authentication Service to use LDAP or AD for user
authentication.
Procedure
1. From a supported web browser session, type the URL of the NMC Server:
http://server_name:http_service_port
where:
l
server_name is the name of the NMC Server.
l
http_service_port is the port for the embedded HTTP server. The default HTTP port is
9000.
For example: http://houston:9000
The gconsole.jnlp file downloads to the host. When the download completes,
open the file.
2. When you use Mozilla Firefox on Windows, and the jnlp extension is not associated
with Java, you are prompted to choose the program that opens the jnlp file. Select
Java (TM) Web Start Launcher. If this application does not appear, browse
to the Java 7 folder and select the javaws.exe file.
The following figure provides an example of the file association window that appears
with the Mozilla Firefox browser.
Connecting to the Console window
43
Getting Started
Figure 3 Associating a jnlp file with Java (TM) web Start Launcher for Mozilla Firefox
3. In the Welcome page, click Start.
Note
If the Start button does not appear but you see a warning message, which states that
Java Runtime Environment cannot be detected, click the here hyperlink.
4. For Internet Explorer only, if a security warning appears, select I accept the risks and
want to run this application, then click Run.
5. In the Log in page, specify the NetWorker Authentication Service administrator
username and password, and then click OK.
6. In the Licensing Agreement page, select Accept.
7. If you did not install a support version of JRE on the host, then a prompt to install JRE
appears. Cancel the installation, install JRE, and then re-run the installation.
8. In the Welcome to the NMC Server Configuration Wizard page, click Next.
9. In the Set authentication server service account for the NMC server page, review the
setting and click Next.
10. In the Define Database Backup Server page, specify the name of the NetWorker server
that will backup the NMC server database, and then click Next.
11. In the Specify a list of managed NetWorker Servers page:
a. Specify the names of the NetWorker Server that the NMC Server will manage, one
name per line.
Note
If the NMC Server is also the NetWorker Server, specify the name of the NetWorker
Server.
b. Leave the default options Capture Events and Gather Reporting Data
enabled.
Consider the following:
44
EMC NetWorker 9.0.x Administration Guide
Getting Started
l
Enable the Capture Events option to allow the NMC Server to monitor and
record alerts for events that occur on the NetWorker Server.
l
Enable the Gather Reporting Data option to allow the NMC Server to collect
data about the NetWorker Server and generate reports.
12. Click Finish. The installation starts the default web browser and connects to the NMC
server. The NetWorker Management Console window and the Getting Started window
appear.
13. In the Enterprise window, right-click the NetWorker Server, and then select Launch
Application.
Note
If you do not specify any NetWorker Servers in the Specify a list of managed
NetWorker servers window, then the NMC Enterprise window does not display any
NetWorker Servers. To add a host, right-click Enterprise in the left navigation pane
and select New > Host. The Add New Host wizard appears.
Connecting to the NMC server after the first time
Use one of the following methods to connect to the NMC server after the initial
connection.
l
Point the browser to the same URL.
l
Double-click the NMC product name in the Java Web Start Application Manager.
l
Double-click the desktop button
Start Application Manager.
, if one was configured by using the Java Web
Connecting to the NMC GUI using an ssh connection
You can use ssh port forwarding to connect to the NMC server and generate reports, from
the NMC client.
Perform the following steps on the NMC client.
Procedure
1. Open an ssh connection from the NMC client to the NMC server with ssh tunnels for
ports 9000 and 9001.
For example:
ssh -L9000:localhost:9000 -L9001:localhost:9001 -L5432:localhost:
5432 Console_servername -N
Note
If you changed the default NMC server ports, specify the correct port numbers.
2. Use javaws to connect to the NMC server.
For example:
javaws http://localhost:9000/gconsole.jnlp
Connecting to the Console window
45
Getting Started
Connecting to the Administration window
The following sections describe how to connect to the Administration window and browse
through the interface.
Opening the Administration window
You can add and select a NetWorker server and open the Administration window.
Procedure
1. From the Console window, click Enterprise.
2. Add one or more NetWorker servers:
a. Highlight Enterprise in the navigation tree.
b. From the File menu, select New>Host.
c. Type the name of the host on which the NetWorker server is running, and click
Next.
d. Select NetWorker for the type of application to be managed.
e. Click Finish.
f. Repeat for all NetWorker servers in the network.
3. From the left pane, click a host in the Enterprise list.
4. From the right pane, click the application and select Enterprise > Launch Application,
or double-click the application. The Administration window opens as a separate
application.
Administration window
NetWorker servers are managed through the Administration window.
The following figure illustrates the NetWorker Administration window.
46
EMC NetWorker 9.0.x Administration Guide
Getting Started
Figure 4 Administration window
You can toggle between the Administration window and the NMC UI.
The following table lists the windows that can be launched from the Administration
window taskbar.
Table 8 Windows that are launched from the Administration window
Button Window
Description
Monitoring Monitor various activities that are related to the NetWorker server. For
example, you can monitor the progress of a policy and view any alerts. A
portion of the Monitoring window always appears at the bottom of the
Administration window, providing information on Log messages and
Alerts.
Protection Manage NetWorker server resources such as clients, groups, policies,
probes, and schedules.
Recover
Manage to recover configurations and schedule recover jobs for
NetWorker hosts from a centralized location on the NMC server.
Devices
Add, configure, and operate single or multiple devices, libraries, and silos
for the NetWorker server.
Media
Manage the activities and the resources that are related to backup
volumes. For example, you can mount a backup volume or create a label
template for backup volumes.
Hosts
View information about known NetWorker hosts such as the NetWorker
version, CPU type, and operating system. Manage the NetWorker client
resource database. Perform software upgrades on NetWorker hosts by
using client push.
Server
Manage NetWorker server resources such as licenses, notifications, user
groups, directives, and restricted datazones.
Administration window
47
Getting Started
Editing multiple resources
In the NMC Protection window, you can edit an attribute for multiple resources at the
same time.
For example, if you want the schedule for all clients within a group to change from the
default to “Full Every Friday”, perform the following steps:
Procedure
1. Select each client resource row in the window.
2. Place the cursor in the column you want to change (in this case, the Schedule
column).
The color of the column changes when the cursor is in the column.
3. Right-click in that column and select from the list of available options. The options
include Edit, Add to, and Remove from, depending on the column selected.
Only the columns that appear in the window can be selected for multiple resource
editing. To add a column that is not currently in view:
a. Right-click a table header and select Add Column from the drop-down.
b. Select from the list of available attributes.
Drag-and-drop functionality
Drag-and-drop functionality is available in the Console and Administration interfaces for
many tasks.
Drag-and-drop between resource types in the Console window
The drag-and-drop functionality allows multiple resources to be selected and moved from
one resource type to another.
In the Enterprise window from the Console interface, you can drag-and-drop to perform
the following actions:
48
l
Copy an individual folder in the enterprise hierarchy by selecting the folder, press and
holding the Ctrl key, and dragging the folder to a new location.
l
Move an individual folder in the enterprise hierarchy to a new location by selecting
and dragging a folder to a new location.
l
Copy an individual host node in the enterprise hierarchy by selecting and dragging
the host to a new parent folder.
l
Move an individual host node in the enterprise hierarchy by selecting and dragging
the host to a new parent folder.
l
Copy a selected number of objects in a folder to a new folder in the hierarchy tree or
folder contents table. Select an individual folder in the navigation tree to display the
contents of the folder, select the contents, while pressing Ctrl, drag the contents to a
new folder. Select a collection of folders or hosts and drag them to a new folder by
creating a copy of the selected contents in a new location.
l
Move a selected number of objects in a folder to a new folder in the hierarchy tree or
folder contents table. Select an individual folder in the navigation tree to display the
contents of the folder, select the contents, and drag the contents to a new folder.
Select a collection of folders and or hosts and drag them to a new folder by moving
the selected contents to a new location.
EMC NetWorker 9.0.x Administration Guide
Getting Started
Note
Only one object may be selected for drag-and-drop in the navigation tree.
Client and group management in the Administration window
The drag-and-drop functionality allows multiple clients or groups to be selected and
moved from one location to another. You can use drag-and-drop functionality in the
Protection window to do the following:
l
Copy selected clients to a new NetWorker group:
1. In the left navigation pane, expand the server resource, and then expand the
Groups resource.
2. Select Clients in the directory tree.
3. Drag-and-drop the client objects from the Client Summary table to a group in the
directory tree.
l
Move selected clients from one NetWorker group to another group:
1. Select a group in the directory tree.
2. Move clients from the Client Summary table to another NetWorker group.
Library operations in the Devices window
The drag-and-drop functionality allows multiple slots or devices to be managed in the
Devices window.
You can use drag-and-drop functionality to manage media from the Library window from
the Devices task, for instance:
l
Mount an individual volume onto a device by selecting a slot in the Slots table and
dragging it to a device in the Devices table.
l
Mount multiple volumes to available devices as assigned by the NetWorker server. To
mount multiple volumes, select multiple slots in the Slots table and drag them
anywhere in the Devices table.
l
Unmount a volume from a selected device and deposit it back in its designated slot
by selecting an individual device from the Devices table and dragging it anywhere in
the Slots table. The volume image displays in the corresponding slot.
l
Unmount multiple volumes from a selected device and deposit them back in their
designated slot by selecting the devices from the Devices table and dragging them
anywhere in the Slots table. The volumes display in the corresponding slots.
Copy and paste tabular information to operating system clipboard
Tabular information can be selected and moved to an operating system clipboard by
using drag-and-drop functionality. All tables support selection of multiple rows in a table
and the ability to copy and paste the data in the selected rows to the system clipboard.
Subsequently, the data in the operating system clipboard can be moved to a target
application.
Note
Drag-and-drop operations from the operating system clipboard to a table are not
supported.
Drag-and-drop functionality
49
Getting Started
Multiple library devices and slots
A single operation can be performed on multiple library devices and slots. Multiple rows
can be selected in both the Devices and Slots tables simultaneously.
In the Devices table for a library, multiple devices can be selected to perform the
following operations:
l
Unmount
l
Release device (STL only)
l
Enable/Disable
In the Slots table for a device, multiple volume operations can be performed for the
following operations:
l
Mount
l
Load without mount
l
Withdraw
l
Label
l
Inventory
l
Remove (STL only)
Setting user interaction preferences
Depending on the window button that was selected from the Console window, you can
set various user preferences such as the user interface font, font size, parallel windows,
and table settings. For the Reports window, there are ways you can enhance the viewing
of displayed reports.
Procedure
1. On the main menu, select View.
2. Set the various options available under the selected window button. You may need to
click OK, depending on the option selection.
Monitoring NetWorker server activities in the Administration window
The Monitoring window in the NetWorker Administration application enables you to
monitor the activities of an individual NetWorker server.
The Monitoring window provides the following types of activity and status information:
l
Data protection policies, workflows, and individual actions.
l
Cloning, recovering, synthetic full backups, and browsing of client file indexes.
l
Operations that are related to devices and jukeboxes.
l
Alerts and log messages.
You can also perform some management operations from the Monitoring window, for
example, starting, stopping, or restarting a data protection policy.
Procedure
1. From the NMC Console window, click Enterprise.
2. In the Enterprise view, right-click the NetWorker server and select Launch Application.
The Administration window appears.
50
EMC NetWorker 9.0.x Administration Guide
Getting Started
3. Click Monitoring to view the Monitoring window.
Figure 5 Monitoring window
About the Monitoring window
On the Administration window taskbar, select Monitoring to view the details of current
NetWorker server activities and status, such as:
l
Policies and actions.
l
Cloning, recovering, synthetic backups, checkpoint restart backups, and browsing of
client file indexes.
l
Alerts and log messages, and operations that are related to devices and jukeboxes.
While the Monitoring window is used primarily to monitor NetWorker server activities, it
can also be used to perform certain operations. These operations include starting,
stopping, or restarting a workflow.
The Monitoring window includes a docking panel that displays specific types of
information. Select the types of information you want to view from the docking panel.
A portion of the Monitoring window, which is known as the task monitoring area, is
always visible across all windows. A splitter separates the task monitoring area from the
rest of the window. You can click and move the splitter to resize the task monitoring area.
The arrow icon in the upper right corner of the Monitoring window allows you to select
which tasks you want to appear in this view.
Smaller windows appear within the Monitoring window for each window. Each smaller
window, once undocked, is a floating window and can be moved around the page to
Monitoring NetWorker server activities in the Administration window
51
Getting Started
customize the view. You can select multiple types from the panel to create multiple
floating windows that can be viewed simultaneously. The following table describes the
various types of information available in the docking panel, and the details each one
provides.
Table 9 Monitoring window panel
Window
Information provided
Policies/Actions
The Policies tab provides you with status information about all
configure policies and the associated workflows and actions.
The Actions tab provides you with status information for all
actions. Policies/Actions pane on page 643 provides more
information.
Sessions
Allows you to customize whether to display all session types, or
only certain session types. The information that is provided
depends on which session type you select. For example, if you
select Save Sessions, the window lists clients, save sets,
groups, backup level, backup start time, duration of the backup,
devices, rate, and size. Sessions pane on page 52 provides
more information.
Alerts
Lists the priority, category, time, and message of any alerts.
Alerts pane on page 53 provides more information.
Devices
Lists devices, device status, storage nodes, libraries, volumes,
pools, and related messages. Devices pane on page 54
provides more information.
Operations
Lists the status of all library and silo operations, including
nsrjb operations that are run from the command prompt. Also
lists user input, libraries, origin, operation data, operation start
time, duration of the operation, progress messages, and error
messages.
When displaying Show Details from the Operations window,
the length of time that the window is
displayed depends on the value that is typed in the Operation
Lifespan attribute on the Timers tab of
the Properties dialog box for the corresponding library. To
access library properties, click Devices
in the taskbar. By default, this pane is hidden.
Log
Lists messages that are generated by the NetWorker server,
including the priority of each message, the time the message
was generated, the source of the message, and the category.
Log pane on page 57 provides more information.
Sessions window
Use the Sessions window to view the sessions that are running on a NetWorker server.
You can change the view of this window to display these sessions:
The Sessions pane below the Policies/Actions pane provides details on individual save,
recover, clone, and synthetic full sessions by client.
52
EMC NetWorker 9.0.x Administration Guide
Getting Started
Click the tabs at the bottom of the Sessions pane to view all sessions or to limit the list of
sessions by the session type. Session types include:
l
Save
l
Recover
l
Clone
l
Browse
l
Synthetic Full/Rehydrated Sessions
l
All
To change the displayed session types go to View > Show, and select the type of sessions
to display. To display all sessions currently running on the NetWorker Server, regardless
of type, select All Sessions.
You can stop a session (backup, synthetic full backup, clone, and recovery sessions)
from the Monitoring window, even if the session was started by running the savegrp
command.
To stop a session, right-click the session in the pane, and select Stop from the dropdown.
Alerts pane
The Alerts pane displays alerts that are generated by a particular NetWorker server or
Data Domain system that has devices that are configured on the NetWorker server. The
Alerts pane includes priority, category, time, and message information.
An icon represents the priority of the alert. The following table lists and describes each
icon.
Table 10 Alerts window icons
Icon
Label
Description
Alert
Error condition detected by the NetWorker
server that should be fixed by a qualified
operator.
Critical
Severe error condition that demands immediate
attention.
Emergency
Condition exists that could cause NetWorker
software to fail unless corrected immediately.
This icon represents the highest priority.
Information
Information about the current state of the
server. This icon represents the lowest priority.
Notification
Important information.
Waiting
The NetWorker server is waiting for an operator
to perform a task, such as mounting a tape.
Warning
A non-fatal error has occurred.
When items on the Alerts pane are sorted by the Priority column, they are sorted in
alphabetical order based on the label of the icon.
Monitoring NetWorker server activities in the Administration window
53
Getting Started
Removing alerts
Remove individual alert messages from the Events tables by removing them from the
Events table. To delete a message in the Events table, right-click the message, and select
Dismiss.
Note
The alert message remains in the Log window in the NetWorker Administration program.
Devices pane
The Devices pane allows you to monitor the status of all devices, including NDMP
devices. If the NetWorker server uses shared and logical devices, the window is adjusted
dynamically to present a set of columns appropriate for the current configuration.
The Devices pane provides the following information:
l
Status of the operation.
l
Name of the device.
l
Name of the storage node that contains the device.
l
For tape devices, the name of the library that contains the device.
l
Name of the volume in the device.
l
Name of the pool that is associated with the volume.
l
Last message generated for the device.
l
Whether the operation requires user input.
For example, a labeling operation may want the user to acknowledge whether the
system should overwrite the label on a tape.
Entering user input on page 56 provides instructions on how to deal with a user
input notification.
If the current server configuration includes a shared device, a Shared Device Name
column appears on the Devices pane. The name of the shared device appears in the
Shared Device Name column. If other devices for that configuration are not shared
devices, then the Shared Device Name column is blank for those devices. Only a single
device per hardware ID can be active at any particular moment. The information for
inactive shared devices is filtered out, and as a result, only one device per hardware ID is
presented on the window at any time.
An icon represents the device status. The following table lists and describes each icon.
Table 11 Devices status icons
Icon
54
EMC NetWorker 9.0.x Administration Guide
Label
Description
Library device active
The library device is active.
Library device disabled
The library device is disabled.
Library device idle
The library device is idle.
Stand-alone device active
The stand-alone device is
active.
Getting Started
Table 11 Devices status icons (continued)
Icon
Label
Description
Stand-alone device disabled
The stand-alone device is
disabled.
Stand-alone device idle
The stand-alone device is idle.
When you sort items in the Devices pane by the Status column, NetWorker sorts the
devices in alphabetical order based on the label name of the icon.
Operations window
The Operations window displays information about device operations. It provides the
following information:
l
Status of the operation.
l
Name of the library.
l
Whether the operation requires user input.
For example, a labeling operation may want the user to acknowledge whether the
system should overwrite the label on a tape. Entering user input on page 56
provides instructions on how to deal with a user input notification.
l
The origin, or source, of the operation.
For example, the interface, nsrjb or the NetWorker server.
l
Time the operation started.
l
Type of operation.
l
Duration of the operation.
l
Status messages from the operation.
l
Any error messages.
NOTICE
Only the last error message of the operation appears in the Error Messages column.
Move the mouse pointer over the cell containing the last error message to display the
entire list of error messages.
The operation status is represented by an icon. The following table lists and describes
each of the icons.
Table 12 Operations window icons
Icon
Label
Description
Failed
The operation failed.
Queued
The operation is waiting in the queue to run.
Retry
The operation failed, but may work if you try
again.
Running
The operation is running.
Monitoring NetWorker server activities in the Administration window
55
Getting Started
Table 12 Operations window icons (continued)
Icon
Label
Description
Successful
The operation completed successfully.
User Input
The operation requires user input.
When items on the Operations window are sorted by the Status column, they are sorted
in alphabetical order based on the label of the icon.
Viewing operation details
The Operation Details dialog box opens, providing information about the completion of
the operation. The Completion Time displays the time that the operation finished. The
time that it took to complete the operation is the difference between the completion and
start times of the operation.
To save operation details to a file, click Save in the Operation Details dialog box. When
prompted, identify a name and location for the file.
Procedure
1. From the Administration window, click Monitoring.
2. Click Operations in the docking panel.
3. Right-click the operation, then select Show Details.
Stopping an operation
Certain operations can be stopped from the Operations window.
Procedure
1. From the Administration window, click Monitoring.
2. Click Operations in the docking panel.
3. Right-click the operation to stop, then select Stop.
4. Click Yes to confirm the stop.
Note
Operations that were started from a command line program, such as the nsrjb
command, cannot be stopped from the Operations window. To stop these operations,
press Ctrl-c from the window where the command was started.
Entering user input
If the system requires user input, select the labeling operation in slow/verbose mode and
the Supply User Input icon appears.
Procedure
1. Right-click the operation, then select Supply Input.
2. Confirm the requirement to supply input.
l
56
If Yes, and input is supplied, the icon in the User Input column disappears.
EMC NetWorker 9.0.x Administration Guide
Getting Started
Note
If two users try to respond to the same user input prompt, the input of the first user
takes precedence, and the second user receives an error message.
l
If No, and input is not supplied, the operation will time out and fail.
Log window
To view the most recent notification logs, click the Log window from the docking panel in
the Monitoring window. The Log window provides the priority, time, source, category, and
message for each log.
Note
If a particular log file is no longer available, check the log file on the NetWorker server.
The log files are located in NetWorker_install_path\logs directory.
An icon represents the priority of the log entry. The following table lists and describes
each icon.
Table 13 Icons in the Log pane
Icon
Label
Description
Alert
Error condition that is detected by the
NetWorker server that should be fixed by a
qualified operator.
Critical
Severe error condition that demands immediate
attention.
Emergency
Condition exists that could cause NetWorker
software to fail unless corrected immediately.
This icon represents the highest priority.
Information
Information about the current state of the
server. This icon represents the lowest priority.
Notification
Important information.
Waiting
The NetWorker server is waiting for an operator
to perform a task, such as mounting a tape.
Warning
Non-fatal error has occurred.
When you sort items on the Log pane by using the Priority column, NetWorker sorts the
icons in alphabetical order based on the name of the label.
Recover window
The Recover window displays information about recover configurations that are created
with the NMC Recovery wizard.
You can use this window to:
l
Start the NMC Recovery wizard to create recover configurations or modify saved
recover configurations.
l
Identify the status of a recover configuration that is created with the NMC Recovery
wizard.
Monitoring NetWorker server activities in the Administration window
57
Getting Started
l
Start and stop a recover job.
The Recover window is divided into five sections:
l
Toolbar—The toolbar is hidden by default. To display the recovery toolbar, select View
> Show toolbar
l
Summary
l
Configured Recovers
l
Currently Running
A splitter separates the Configured Recovers section from Currently running window. You
can click and move the splitter to resize these two windows.
The following table shows an example of the Recover window.
Figure 6 Recover window
Recover toolbar
The Recover toolbar provides you with the ability to quickly perform common recover
operations. The following table summarizes the function of each toolbar button.
Table 14 Recovery toolbar options
Button
Function
Starts the NMC Recover wizard to create recover configurations.
Displays the Properties window for the saved recover
configuration that you selected in the Configured Recover
window.
Deletes the saved recover configuration that you selected in the
Configured Recover window.
Displays online help for the Recover window.
Displays the Find window at the bottom of the Recover
window. The Find window allows you to perform keyword
searches for messages that appear in the Logs window.
58
EMC NetWorker 9.0.x Administration Guide
Getting Started
Table 14 Recovery toolbar options (continued)
Button
Function
Start the recover operation for a selected saved recover
configuration. This option is only available for a recover
configuration that has a Never run, or Failed status.
Stop in-progress recover operation that you selected in the
Currently Running window.
Note
The Recover toolbar does not appear by default. To display the Recover toolbar, select
View > Show toolbar.
Recover Summary
The Recover Summary section displays a high-level overview of recover jobs.
This section includes the following information:
l
Total Recovers—The total number of successful recover jobs.
l
Since—The number of successful recover jobs since this date.
Configured Recovers
The Configured Recovers window displays a list of saved recover configurations in a
tabular format. You can sort the information by column. The Configured Recovers table
displays the following information for each saved recover configuration:
l
Status—The job status of a saved recover configuration.
l
Name
l
Source client
l
Destination client
l
Recovery list
l
Recover type—For example, file system or BBB.
l
Comment
l
OS—The operating system of the source host.
l
Recover requestor—The Windows or UNIX account used to create the recover
configuration.
l
Start Time
l
End Time
l
Start date
Table 15 Save recover configuration job status
Icon
Description
The last recover attempt failed.
The last recover attempt completed successfully.
Monitoring NetWorker server activities in the Administration window
59
Getting Started
Table 15 Save recover configuration job status (continued)
Icon
Description
The recover job has never run.
The recover job is scheduled to run in the future.
The recover job has expired.
Currently running
The Currently Running window displays a list of in progress recover jobs in a tabular
format. You can sort the information by column. The Currently Running table displays the
following information for each job:
l
Status
l
Name
l
Source client
l
Destination client
l
Recovery list
l
Recover type—For example, file system or BBB
l
Volume
l
Comment
l
Device
l
Size
l
Total size
l
% complete
l
Rate (KB/s)
l
Start time
l
Duration
l
Currently running
Find
The Find section appears along the bottom of the Recover window, after you select the
Find button on the Recover toolbar. Find allows you to search for keywords in the
Configured Recovers window. The following table summarizes the available find options.
Table 16 Find options
60
Find option
Description
Find
Highlight the first saved recover configuration that contains the
specified keyword.
Prev
Highlight the previous saved recover configuration that contains
the specified keyword.
EMC NetWorker 9.0.x Administration Guide
Getting Started
Table 16 Find options (continued)
Find option
Description
Highlight All
Highlights each saved recover configuration that contains the
specified keyword.
Sort Selected
Sorts each highlighted recover configuration in the Configured
Recover table so that they appear at the top of the Configured
Recover table.
Match case
Make the keyword search case sensitive.
Getting started with a new installation
The following section provides basic information on how to get started with a new
installation by configuring the NetWorker datazone and starting the NetWorker
Management Console (NMC) Enterprise window and Administration window.
Common NetWorker tasks
There are several common tasks available in the NetWorker Console.
Adding a new host
You can add hosts by using the NetWorker Console.
Procedure
1. Log in to Console as a NetWorker Administrator.
2.
Click the Enterprise button
on the taskbar.
3. Right-click Enterprise in the navigation tree.
4. Select New > Host.
5. In the Host Name field, specify the IP address or DNS name of the NetWorker server
and click Next.
6. On the Select Host Type window, select NetWorker and click Next.
7. On the Manage NetWorker window, leave the default options Capture Events and
Gather Reporting Data enabled.
l
Enable the Capture Events option to allow the NMC server to monitor and record
alerts for events that occur on the NetWorker server.
l
Enable the Gather Reporting Data option to allow the NMC server to automatically
collect data about the NetWorker server and generate reports on the NMC server.
8. Click Finish.
Getting started with a new installation
61
Getting Started
Device configuration
You can configure devices to test the NetWorker software.
Configuring a stand-alone tape device
Procedure
1. Log in to the NMC GUI as an administrator of the NetWorker server.
2.
Click the Enterprise button
on the taskbar.
3. Highlight a host in the navigation tree, right-click NetWorker and select Launch
Application. The NetWorker Administration window appears.
4.
Click the Devices button
on the taskbar.
5. In the navigation tree view, right-click a host and select Scan for Devices.
The Scan for Devices window appears.
6. On the Select Target Storage Nodes window, select the storage node for the library or
click Create a new Storage Node to create a new storage node.
7. Select Start scan.
NetWorker scans for new devices and the Log pane provides the status of the scan
operation.
8. On the left pane, select Devices and then from the right pane, select the new device.
9. From the Devices menu, select Devices > Device Operations > Label.
10. In the Label window, verify the information and click OK.
Configuring a stand-alone advanced file type device
Create a device that is local to the NetWorker server to receive the backup data.
Procedure
1. Log in to the NMC GUI as an administrator of the NetWorker server.
2.
Click the Enterprise button
on the taskbar.
3. Highlight a host in the navigation tree, right-click NetWorker and select Launch
Application. The NetWorker Administration window appears.
4.
Click the Devices button
on the taskbar.
5. From the File menu, select New Device Wizard.
6. On the Select the Device Type window, select Advanced File Type Device (AFTD), then
click Next.
7. On the Select Storage Node window, leave the default values, and click Next.
8. On the Select the Device Path window, select an empty folder or create a new folder
on the NetWorker server, then click Next.
9. On the Configure Device Attributes window, specify a name for the new device in the
NetWorker Device Name field, for example: myaftd, and click Next.
10. On the Label and Mount Devices window, leave the default values and click Next.
11. In the Review the Device Configuration Settings window, review the configuration
information, and click Configure.
62
EMC NetWorker 9.0.x Administration Guide
Getting Started
12. Click Finish.
Configuring an autochanger or silo
You can configure a new library resource.
Procedure
1. Log in to the NMC GUI as an administrator of the NetWorker server.
2.
Click the Enterprise button
on the taskbar.
3. Highlight a host in the navigation tree, right-click NetWorker and select Launch
Application. The NetWorker Administration window appears.
4.
Click the Devices button
on the taskbar.
5. From the left pane, select Storage Nodes.
6. Right-click the storage node for the device and select Configure All Libraries.
7. On the Provide General Configuration Information window, leave SCSI/NDMP
selected and click Next.
8. On the Select Target Storage Nodes window, select the storage node for the library or
click Create a new Storage Node to create a new storage node.
9. Click Start Configuration.
NetWorker scans for new devices and the Log pane provides the status of the scan
operation.
10. Click Finish.
Labeling media
You can label tapes from the NMC GUI.
Procedure
1. Log in to the NMC GUI as an administrator of the NetWorker server.
2.
Click the Enterprise button
on the taskbar.
3. Highlight a host in the navigation tree, right-click NetWorker and select Launch
Application. The NetWorker Administration window appears.
4.
Click the Devices button
on the taskbar.
5. In the navigation tree view, expand Libraries and highlight a library, or select Devices.
6. In the Device list, right-click a device and select Label.
Scheduling backups
Perform scheduled backups to automatically backup client data on an ongoing basis.
Data protection policies enable you to define the client resources, schedule, and other
settings for the backup. The client resources and backup storage resources must also be
configured.
Procedure
1. Configure the backup storage resources:
a. Configure the storage node that will own the backup storage devices.
b. Configure the backup storage device.
Common NetWorker tasks
63
Getting Started
c. Create a label template for labeling volumes, or use one of the preconfigured label
templates.
d. Create media pools for sorting and storing backup data.
Backup Storage on page 69 provides more information on configuring backup
storage resources.
2. Configure one or more client resources for each client computer by using either the
Client Backup Configuration Wizard or the Client Properties dialog box.
When you configure a client resource, you specify backup settings for the client,
including:
l
The save sets for the client, which define the data to back up on the client.
l
Whether to automatically restart failed backups from a known good point, which is
called checkpoint restart.
l
Whether to bypass the storage node and send backup data directly to AFTD or DD
Boost storage devices, which is called Client Direct.
l
Directives that control how the NetWorker server processes files and directories
during the backup.
l
Probe resources for probe-based backups, where the NetWorker server probes the
client for a user-defined script before the backup starts.
l
Whether to back up each save set for the client by using multiple parallel save
streams.
l
Backup command customizations.
Client resources on page 403 provides more information on configuring client
resources.
3. Configure a data protection policy for scheduled backups:
a. Create a group to define the client resources to back up.
The type of group that you create depends on the type of backup that you are
performing:
l
Create a client group or dynamic client group for a traditional backup or a
server backup.
l
Create a VMware group to back up virtual machines or VMDKs.
l
Create a NAS device group to perform snapshot backups on NAS devices.
b. Create a policy.
Policies provide a container for the workflows, actions, and groups that support
and define the backup.
c. Within the policy, create a workflow.
Workflows define the start time for a series of actions, the order of actions in a
sequence, and the group of client resources to back up.
d. Create a backup action.
When you create a backup action, you define the following settings:
64
l
The type of backup to perform each day.
l
The destination storage node and media pool.
EMC NetWorker 9.0.x Administration Guide
Getting Started
l
The retention setting for the backup, which specifies how long to retain the
backup data.
e. (Optional) Create other actions for the workflow.
Actions that you may want to include in a backup workflow include:
l
Check connectivity to verify connectivity between the NetWorker server and the
client computer.
l
Probe to probe a NetWorker client for a user-defined script before the backup
starts.
l
Clone to automatically clone the save sets that result from the backup.
Data Protection Policies on page 205 provides more information on configuring
groups, policies, workflows, and actions.
Viewing failed backups
You can view the details for failed NetWorker backups.
Procedure
1. Log in to the NMC GUI as an administrator of the NetWorker server.
2.
Click the Enterprise button
on the taskbar.
3. Highlight a host in the navigation tree, right-click NetWorker and select Launch
Application. The NetWorker Administration window appears.
4.
Click Monitoring
.
The Monitoring window displays four windows panes. The Log pane provides a
summary of NetWorker server events. The Policies pane displays all configured
policies on the NetWorker server. To view details information about the status of the
actions in a workflow, expand the policy, right-click the workflow, and select Show
Details.
Using nsrlogin for authentication and authorization
When you configure the NetWorker Authentication Service to use LDAP/AD
authentication, you modify the External Roles attribute in the User Group resource to
assign privileges to LDAP and AD users. As a result, NetWorker command line operations
and NetWorker module operations might fail due to insufficient privileges. To resolve this
issue, use the nsrlogin command to contact the NetWorker Authentication Service and
authenticate a user. When user authentication succeeds, the NetWorker Authentication
Service issues a token to the NetWorker host for the user, which provides CLI operations
with token-based authentication until the token expires.
Before you begin
Ensure that the user that the NetWorker Authentication Service validates has the
appropriate User Group privileges to run the CLI commands.
Perform the following steps on a NetWorker client on which you initiate the CLI
commands, or the requesting host.
Procedure
1. Use the nsrlogin command to validate a user and generate a token for the user:
Common NetWorker tasks
65
Getting Started
nsrlogin [-s NetWorker_server] [-H authentication_host] [-P port]
[-t tenant] [-d logindomain] -u username [-p "password"]
where:
l
-s NetWorker_server—Specifies the name of the NetWorker server. Use this
option when you use the nsrlogin command on a NetWorker host that is not the
NetWorker server.
l
-H authentication_host—Specifies the name of the NetWorker Authentication
Service host. Use this option when you use the nsrlogin command on a
NetWorker host that is not the NetWorker server. This option is only required when
you do not use the -s option.
l
-P port—Specifies the NetWorker Authentication Service port number. Use this
option when you do not use the -s option and when the NetWorker Authentication
Service does not use the default port number 9090 for communications.
l
-t tenant— Specifies the tenant name that the NetWorker Authentication Service
should use to verify the username and password. When you omit this option,
NetWorker Authentication Service uses the Default tenant to verify the user
credentials.
l
-d logindomain—Specifies the domain name that the NetWorker Authentication
Service should use to verify the username and password with an external
authentication authority. When you omit this option, the NetWorker Authentication
Service uses the local user database to verify the user credentials.
l
-u username—Specifies the username that the NetWorker Authentication Service
should validate to generate a token.
l
-p "password"—Specifies the password that the NetWorker Authentication
Service should use to verify the username. If you do not specify the password, the
nsrlogin command prompts you to provide the password.
For example, to generate a token for user Konstantin in the idddomain domain and the
idd tenant, type the following command:
nsrlogin -s bu-idd-nwserver2 -d idddomain -u Konstantin -p
"1.Password"
Authentication succeeded.
When NetWorker Authentication Service successfully validates the user, the service
issues an authentication token to the requesting host.
2. Type the NetWorker command, at the command prompt.
If the validated user does not have the appropriate privileges to run the command, an
error message appears or the command does not return the expected result. For
example, when you try to perform an operation with a user account that does not have
the required privilege, a message similar to the following appears:
Permission denied, user must have the 'Operate NetWorker'
privilege'.
Results
The CLI command uses the authenticated token, until the token expires. By default the
token expiration period is 4800 minutes, or 8 hours. When the token expires and the user
tries to run a CLI command, the command fails with a permissions error and a message
similar to the following appears to indicate that the token has expired:
66
EMC NetWorker 9.0.x Administration Guide
Getting Started
Security token has expired
To resolve this issue, run the nsrlogin command again to generate a new
authenticated token.
Note
To revoke the user token and enable the CLI commands to use the Users attribute in the
Usergroups resources to authenticate users, use the nsrlogout command. The
nsrlogout UNIX man page and the EMC NetWorker Command Reference Guide provides
detailed information about the nsrlogout command.
Performing a manual backup
Perform a manual backup of a file or folder, to test the NetWorker installation. The
procedure to perform a manual backup is different on Windows and UNIX.
Performing a manual backup on Windows
Use the NetWorker User program to perform a manual backup Windows. The NetWorker
User program provides a graphical interface to perform manual backups.
Procedure
1. On a NetWorker client, start the NetWorker User program.
2. In the Change server window, select or type the name of the NetWorker server.
3. In the Source and Destination client windows, select the current NetWorker client.
4. Click Backup.
5. In the left pane of the Backup window, click the appropriate directory folder.
6. Select a file or directory file to back up in one of the following methods:
l
Select the directory or file and click Mark. To clear an item, click Unmark.
l
Right-click the directory or file.
When you mark a directory or file for backup, a check mark appears next to that
item.
7. Click Start.
The Backup Status window displays the progress of the backup. When the NetWorker
server has successfully finished the backup, this message appears:
Backup completion time: 2-15-07 3:27p
If the backup fails, then:
l
Review the NetWorker daemon.raw log file on both the NetWorker server and
client hosts. Use the nsr_render_log program to review the log file in a readable
format. The EMC NetWorker Command Reference Guide describes how to use the
nsr_render_log program.
The location of the daemon.raw file is different on Windows and UNIX:
l
n
On Windows, the log file appears in the C:\Program Files\EMC
NetWorker\nsr\logs directory.
n
On UNIX, the log file appears in the /nsr/logs directory.
To determine the cause, refer to the Troubleshooting chapter.
Common NetWorker tasks
67
Getting Started
l
Review the operating system log files (Application event log on a Windows client)
for more information.
Performing a manual backup on UNIX
Use the save program to perform a manual backup from the command prompt.
For example, to back up /tmp/myfile.txt to a server called jupiter, type:
save -s jupiter /tmp/myfile.txt
The UNIX man pages describe how to use the save program.
68
EMC NetWorker 9.0.x Administration Guide
CHAPTER 3
Backup Storage
This chapter contains the following topics:
l
l
l
l
l
l
l
l
l
Label templates.................................................................................................... 70
Media pools.......................................................................................................... 76
Storage nodes.......................................................................................................91
Disk storage devices........................................................................................... 100
Libraries and silos...............................................................................................133
File type devices..................................................................................................191
Stand-alone devices............................................................................................192
Labeling volumes................................................................................................ 197
Troubleshooting devices and autochangers........................................................ 198
Backup Storage
69
Backup Storage
Label templates
The NetWorker server creates a unique label for each volume by applying a label
template. This section describes how label templates and media pools are used to sort,
store, and track data on media volumes.
Using label templates
The NetWorker server selects the media pool to which a given set of data is written. A
volume is associated with a media pool by its volume label.
The contents of the volume label follow rules that are defined in a specific label template.
You then associate a label template with a specific media pool in the Media Pool
resource. If you do not associate data with a specific media pool, the NetWorker server
uses the preconfigured Default media pool and corresponding Default label template.
The following figure illustrates how a media pool configuration uses its associated label
template to label a volume. For the label template name to appear as a choice in the
Media Pool resource, you must configure a label template before configuring the
associated media pool.
Figure 7 Labeling a volume by using a label template
How the NetWorker server uses volume labels
A volume label is a unique internal code, applied by the NetWorker server, that initializes
the volume for the server to use and identifies a storage volume as part of a specific pool.
Using media pools on page 77 provides more information about pools. Labeling a
volume provides a unique name for tracking and recognizing the media, as well as
references to volume labels in the records stored in the media database. The NetWorker
server uses the media database records to determine which volumes are needed for
backing up or recovering data.
When NetWorker labels a volume, the label operation performs the following actions:
1. Verifies that the volume is unlabeled.
2. Labels the volume with the name specified in the Volume Name attribute by using
one of the following:
70
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
The next sequential label from the label template that is associated with the
chosen pool.
If a recyclable volume from the same pool is relabeled, the volume label name
and sequence number remain the same, but access to the original data on the
volume is destroyed. The volume becomes available for new data.
l
An override volume name that was entered by the user.
Preconfigured label templates
The NetWorker server contains these preconfigured label templates, which correspond to
the preconfigured media pools:
l
Default
l
Default clone
l
Archive
l
Archive clone
l
Full
l
Indexed archive
l
Indexed archive clone
l
NonFull
l
Offsite
l
PC archive
l
PC archive clone
l
Two Sided
Label templates have multiple fields separated by periods. The first field represents the
name of the NetWorker server and the final field contains a number to allow for
expansion of the media pool. The number range from 001 to 999. For example:
mars.001
jupiter.054
jupiter.archive.197
Guidelines for completing Label Template attributes
There are certain guidelines to keep in mind when completing the attributes for a Label
Template resource. The following table describes how to complete the key attributes for
this resource.
Table 17 Key label template attributes
Attribute Guidelines
Name
Keep the label name consistent with the media pool name, so that the label name
reflects how the data is organized. For example, a label template named "AcctFull"
would identify volumes that belong to a media pool called "Accounting Full."
Do not use these characters in label template names:
/\*?[]()$!^;’"’~<>&|{}:-._
Fields
A label template is made up of one or more fields. Each field, or component, provides
a layer of specificity to your organizational structure. There can be any number of
Preconfigured label templates
71
Backup Storage
Table 17 Key label template attributes (continued)
Attribute Guidelines
components, but it is best to keep the template simple with as few as necessary. The
label cannot exceed 64 characters.
You can use four types of components:
l
Range of numbers (for example, 001-999)
l
Range of lowercase letters (for example, aa-zz)
l
Range of uppercase letters (for example, AA-ZZ)
l
Character string (for example, Accounting)
Each range includes a start value, a dash (-), and an end value. The start value
and the end value must have the same number of characters. For example, use
01-99 (not 1-99) or aaa-zzz (not aa-zzz).
The order in which you enter each component of the Field attribute is important.
The NetWorker server applies each component in a left-to-right order, starting
with the first one entered.
Separator Choose the symbol to appear between component entries. Use the period, dash,
colon, or underscore to separate each component of the label template. If label
components do not have separators (for example, AA00aa), the labels can be difficult
to read.
Next
Choose the next sequence number to write on the label that the NetWorker server
places on a volume (according to the template).
l
To force a label to start the label scheme at a particular point, type a start label
value. The server continues to generate labels from that point on, according to
the rules of the template.
l
To have the NetWorker server generate the first label, leave this attribute blank.
When the NetWorker server recycles a storage volume, the volume label does not
change as long as the volume remains in the same media pool. That is, if a
storage
volume labeled "Dev.006" is recycled, it retains the volume label "Dev.006" and
does not
receive a new label with the next sequence number.
The following table lists examples of number sequences for volume labels.
Table 18 Examples of number sequences for volume labels
72
Type of components
Fields
Number sequence result
Range of numbers
001-100 001, 002, 003,...100
Character string
SalesFull SalesFull.001,...SalesFull.100 100
Range of numbers
001-100
Range of lowercase letters aa-zz
aa.00,...aa.99,
Range of numbers
ab.00,...ab.99,
EMC NetWorker 9.0.x Administration Guide
00-99
Total number of labels
100
67,600 (262 times 102)
Backup Storage
Table 18 Examples of number sequences for volume labels (continued)
Type of components
Fields
Number sequence result
Total number of labels
ac.00,...ac.99,
:
az.00...az.99,
ba.00,...ba.99
:
zz.00,...zz.99
The label template should allow for expansion of the backup media storage system. For
example, it is better to create a template for 100 tapes and not use all of them, than it is
to create a template for only 10 tapes and run out of labels. When the server reaches the
end of the template numbering sequence, it wraps to the starting value. For example,
after zz.99 (used for the 67,600th label), the next label the server uses is aa.00 for label
67,601.
Note
When the NetWorker server recycles a volume, the volume label does not change if the
volume remains in the same media pool. That is, if a volume labeled Dev.006 is recycled,
it will retain the volume label Dev.006 and will not receive a new label with the next
sequence number. The original data on the volume, however, will be overwritten by the
new data.
Naming label templates
The NetWorker server is packaged with preconfigured label templates that correspond to
the preconfigured media pools. If you choose to create the templates, you can include
any number of components in the Fields attribute. However, it is best to keep the
template simple with as few components as necessary for your organization.
For example, if you create a label template for an accounting department, you can
customize the label template in several ways, depending on the size of the storage
system and media device capabilities.
The following table illustrates several ways you can use components to organize labels.
Table 19 Using label template components
Type of organizational
structure
Components Separator Resulting volume labels
Sequential
AcctFull
period
‘001-100
Storage oriented (for example,
3 storage racks with 5 shelves
each, each shelf holding 100
tapes)
1-3
1-5
001-100
AcctFull.001
(100 total labels)
dash
1-1-001
This label is for the first tape in
rack 1 on shelf 1. (1,500 total
labels)
Naming label templates
73
Backup Storage
Table 19 Using label template components (continued)
Type of organizational
structure
Components Separator Resulting volume labels
Two-sided media (for example,
optical devices)
AcctFull
underscore AcctFull_000_a (side 1)
000-999
AcctFull_000_b (side 2)
a-b
(2,000 total labels)
Tips for labelling
Naming schemes vary from site to site. One way is to name the volumes with the name of
the NetWorker server followed by a three-digit number, for example:
jupiter.001
Consider that the simpler a convention is, the easier it can be understood by operators
and administrators.
The maximum length for a volume name is 63 characters. With advanced file type devices
(adv_file), the maximum length is 60 characters.
Each volume should have a physical (adhesive) label attached to it. Since the NetWorker
server keeps track of the backups and which volumes they are on, you can name the
volumes with any convenient name. For example, you can label your volumes 1, 2, 3, or
Monday.1, Tuesday.1, Wednesday.1. You can assign a volume any name as long as each
one is unique.
The adhesive label on the volume should match the name generated by NetWorker. For
example, if you physically label a volume mars.1, its NetWorker name should also be
mars.1.
Working with label templates
This section explains how to create, edit, copy, and delete label templates.
Creating a label template
When creating a label template, consider the labeling guidelines for the Name, Fields,
Separator, and Next components.
Procedure
1. In the Administration window, click Media.
2. In the expanded left pane, select Label Templates.
3. From the File menu, select New.
4. Enter the components for the label template:
74
l
Name: The name of the new label template.
l
Comment: Any user-defined description or explanatory remarks about the label.
l
Fields: A list of label components.
l
Separator: The character to be inserted between label components. If no symbol is
selected, the components will have no separators, such as hostarchive[001-999].
l
Next: (Optional) Enter the next label to be generated by the template.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
5. Click OK.
Editing a label template
You cannot change the name of a label template. However, to change an individual label
name, delete the existing name in the Next text box, and type a new name.
Procedure
1. In the Administration window, click Media.
2. In the expanded left pane, select Label Templates.
3. In the right pane, perform one of the following tasks:
l
To modify multiple attributes in a single configuration resource by using the Label
Template Properties window, right-click the staging configuration and select
Properties.
l
To modify a specific attribute that appears in the resource window, place the
mouse in the cell that contains the attribute that you want to change, then rightclick. The menu displays an option to edit the attribute. For example, to modify the
Comment attribute, right-click the resource in the Comment cell and select Edit
Comment.
Note
To modify a specific attribute for multiple resources, press and hold the Ctrl key,
select each resource, and then right-click in the cell that contains the attribute that
you want to change. The menu displays an option to edit the attribute.
4. Make any required changes, then click OK.
Copying a label template
Procedure
1. In the Administration window, click Media.
2. In the expanded left pane, select Label Templates.
3. In the right pane, select the label template to copy.
4. From the Edit menu, select Copy. The Create Label Template dialog box appears,
containing the same information as the label template that was copied, except Name
attribute.
5. In the Name attribute, type the name for the new label template.
6. Edit any other attributes as appropriate, and click OK.
Deleting a label template
You cannot delete a preconfigured label template or a label template that is in use.
Procedure
1. In the Administration window, click Media.
2. In the expanded left pane, select Label Templates.
3. In the right pane, select the label template to delete.
4. From the File menu, select Delete.
5. When prompted, click Yes to confirm the deletion.
Working with label templates
75
Backup Storage
Setting up a label template to identify volumes
If you are not using tapes with barcode labels, and the Match Bar Code Labels attribute is
not enabled for the Library resource, then every backup volume requires a unique label
for identification. The NetWorker server creates a unique label for each volume by
applying a label template.
Procedure
1. From the Administration window, click Media.
2. In the expanded left pane, select Label Templates.
3. From the File menu, select New.
4. In the Name attribute, type a name for the label template.
5. In the Comment attribute, type a description for the label template.
6. In the Fields attribute, type the label’s components. Place each label component on a
separate line. The template can use any or all of these components, although at least
one range component must be added:
l
Range of numbers—For example, 001-999
l
Range of lowercase letters—For example, aa-zz
l
Range of uppercase letters—For example, AA-ZZ
l
Character string—For example, Accounting
l
Ranges of numbers or letters change incrementally with each new label. For
example:
n
First label: Accounting.001
n
Second label: Accounting.002
n
Third label: Accounting.003
7. Select a Separator and click OK. If no symbol is selected, the components will have no
separators (for example, Accounting001).
8. Click OK.
Media pools
NetWorker uses media pools and volume labels to sort backup and clone data on media.
Media is a specific collection of volumes to which the NetWorker server writes data. For
example, a tape volume or a Data Domain device. A volume is identified with a unique
label based on user configurable label templates.
Media pools act as filters that tell the NetWorker server which backup volumes should
receive specific data. The NetWorker server uses media pools along with label templates
to track what data is on which specific volume. When you use a barcode-enabled tape
library, the NetWorker server uses media pools along with the volume barcode Labels to
track which data is on a specific volume.
Note
NetWorker does not use media pools for backup and clone operations to deduplication
devices.
76
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Using media pools
Action resources contain an attribute that defines the media pool to which NetWorker
should send the backup or clone data.
When a backup or clone action starts, the NetWorker server then checks if a correctly
labeled volume for that media pool is mounted on a storage device. If a correctly labeled
volume is mounted on a storage device, the NetWorker server writes data to the volume.
If there is no correctly labeled volume mounted on a storage device, the NetWorker server
generates a request to mount a volume that is labeled for the pool, and waits until an
operator or an autochanger mounts an appropriate volume.
Preconfigured media pools
NetWorker provides you with the following preconfigured media pools.
Table 20 Preconfigured media pools
Pool
name
Description
Archive
Receives archived backup data when you use the nsrarchive command and use b option to specify the pool name. NetWorker does not assign a retention policy to
an archived save set, and the save set never expires. When you enable Archive
Services on a client resource and you configure the backup action to send data to the
Archive pool, NetWorker does not write information about the archive save set to the
client file index for the client.
Archive
Clone
Receives the clone copy of archived backup data. when you use the nsrclone
command with -b option to specify the pool name. NetWorker does not assign an
expiration date to the clone copy of an archive save set. NetWorker does not write
information about the clone save set to the client file index for the client.
Default
Receives backup data in the following configurations:
Default
Clone
Indexed
Archive
l
When you select the Default pool in the Pool attribute of a backup action
resource.
l
When you use save command to run a manual backup and do not use the -b
option to specify a specific backup pool.
l
When NetWorker performs an action on a client and you define the following
configuration attributes:
n
In the Action resource, the option Client Override Behavior is set to Client
Can Override.
n
In the Client resource, you select the Default pool in the Pool attribute.
Receives clone data in the following configurations:
l
When you select the Default Clone pool in the Pool attribute of a clone action
resource.
l
When you use nsrclone command to run a manual backup and do not use the
-b option to specify a specific backup pool.
Receives archived backup data. NetWorker does not assign a retention policy to an
archived save set, and the save set never expires. When you enable Archive Services
on a client resource and you configure the backup action to send data to the Indexed
Using media pools
77
Backup Storage
Table 20 Preconfigured media pools (continued)
Pool
name
Description
Archive pool, NetWorker writes information about the archive save set to the client
file index for the client.
Indexed
Archive
Clone
Receives the clone copy of an indexed archive. NetWorker does not assign an
expiration date to the clone copy of an archive save set. NetWorker does not write
information about the clone save set to the client file index for the client.
Changes to the Client and Pool resources after migration
NetWorker uses a number of attributes that are defined in multiple resources to
determine which pool receives the data that is generated by an action task, and how
NetWorker backs up the data. The migration process preserves the values that are
defined for the attributes and introduces new attributes in the Action resource.
NetWorker provides the following attributes, which work together to determine how
NetWorker manages a backup and determines which device to use to receive the backup
data:
l
Client resource—Pools, Retention, Save set, and Level attributes on the General tab
of the Client Properties window. The migration process retains the values in these
legacy attributes.
Note
The Modify Client wizard does not display the Pools, Retention, Save set, and Level
attributes.
Action resource—Destination Pool and Retention attributes on the Specify the
Backup Options and Specify the Clone Options wizard windows. The backup levels
are defined for the action schedule on the Specify the Action Information wizard
window.
l
Pool resource—Clients, Save sets, and Retention policy attributes on the Legacy tab.
The values that appear in these attributes were defined in 8.2.x. After the migration
completes, the NetWorker 9.0.1 server retains the values and these legacy attributes
become read-only. You cannot modify the values in these fields after migration.
The Action resource includes an attribute that is called Client Override Behavior. The
value that is selected for this attribute determines which resource attribute has
precedence over the attributes in other resources that determine the same behavior. By
default, the migration process enables Legacy Backup Rules on an Action resource.
Legacy Backup Rules allow NetWorker to use the values during the pool selection criteria
process.
l
Note
By default, the NetWorker Administration window does not show the legacy attributes. To
view the legacy attributes in the Client Properties window, go to the View menu and
select Diagnostic Mode.
Pool selection criteria
EMC recommends that you use the configuration settings in an Action resource to
determine which pool received backup data. NetWorker provides you with the ability to
configure a Pool attribute in the client resource, which can override the value defined in
78
EMC NetWorker 9.0.x Administration Guide
Backup Storage
the Action resource. Additionally, the Pool resource contains 8.2.x legacy attributes that
provide you with the ability to define backup data criteria for the pool.
How and when NetWorker uses the attributes values defined in the Pool, Action, and
Client resources to determine which backup pool will receive data depends on the value
that you select in the Client Override Behavior attribute of the Action resource:
l
Client Can Override—The value in Pool attribute of the client resource takes
precedence over the Destination pool value that is defined in the Action resource.
NetWorker does not use the values that are defined in the Client, Save set, and
Levels attributes of the Pool resources when deciding which pool receives backup
data for a client.
l
Client Can Not Override—The value defined Destination Pool attribute in the Action
resource takes precedence over the value that is defined in the Pool attribute of the
Client resource. NetWorker does not use the values that are defined in the Client,
Save set, and Levels attributes of the Pool resources when deciding which pool
receives backup data for a client.
l
Legacy Backup Rules—Enabled for migrations only. NetWorker uses the values that
are defined in the Client, Save set, and Levels attributes of the pool resource to
determine which pool receives backup data from a client. The values that are defined
in the Client, Save set, and Levels of the pool resource take precedence over the
Destination Pool value that is defined in the Action resource, and the Pool value that
is defined in the Client resource.
Note
You cannot modify the legacy attributes in the migrated Pool resources.
The following table summarizes how NetWorker determines which pool receives the
backup data, which is based on the configuration of the Action, Client, and Pool resource
attributes.
Table 21 Determining which pool receives backup data
Client Override
Behavior (Action)
Destination Pool (Client)
pool (Action)
Legacy criteria
attributes (Pool)
Pool that
receives the data
Client Can Override
Defined
Defined
Defined and criteria
matches
Pool defined in
Client resource
Client Can Override
Defined
Undefined
Defined and criteria
matches
Pool defined in
Action resource
Client Cannot
Override
Defined
Defined
Defined and criteria
matches
Pool defined in
Action resource
Legacy Backup
Rules
Defined
Undefined
Defined and criteria
matches
Pool that matches
legacy criteria
Legacy Backup
Rules
Defined
Defined
Defined and criteria
matches
Pool that matches
legacy criteria
Legacy Backup
Rules
Defined
Undefined
Undefined or no
matches
Default
Using media pools
79
Backup Storage
Example 1 Client Can Override is enabled
A Protection group contains two clients, SQL_clnt and Exchange_clnt. The workflow that is
associated with the protection group contains a backup action.
l
Backup action configuration:
n
Destination Pool=App_backups
n
Schedule=Daily full backup
n
Client Override Behavior=Client Can Override
l
The Pool attribute that is defined for the SQL_clnt client resource is SQL_backups.
l
The Pool attribute for Exchange_clnt is Exchange_backups.
l
The Full level is enabled in the Levels attribute of a pool resource named Backups.
In this example, NetWorker sends the backup data for Exchange_clnt to
Exchange_backups, the pool that is defined in the backup action. NetWorker sends the
backup data for SQL_clnt to the pool defined in the client resource, SQL_backups.
Example 2 Example: Client Can Override is enabled
A Protection group contains two clients, SQL_clnt and Exchange_clnt. The workflow that is
associated with the protection group contains a backup action.
l
Backup action configuration:
n
Destination Pool=App_backups
n
Schedule=Daily full backup
n
Client Override Behavior=Client Can Override
l
The Pool attribute that is defined for the SQL_clnt client resource is SQL_backups.
l
The Pool attribute for Exchange_clnt is not defined.
l
The Full level is enabled in the Levels attribute of a pool resource named Backups.
In this example, NetWorker sends the backup data for Exchange_clnt to App_backups, the
pool that is defined in the backup action. NetWorker sends the backup data for SQL_clnt
to the pool defined in the client resource, SQL_backups.
80
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Example 3 Client Cannot Override is enabled
A Protection group contains two clients, SQL_clnt and Exchange_clnt. The workflow that is
associated with the protection group contains a backup action.
l
Backup action configuration:
n
Destination Pool=App_backups
n
Schedule=daily full backup
n
Client Override Behavior=Client Cannot Override
l
The Pool attribute that is defined for the SQL_clnt client resource is SQL_backups.
l
The Pool attribute for Exchange_clnt is Exchange_backups.
l
The Full level is enabled in the Levels attribute of a pool resource named Backups.
In this example, NetWorker sends the backup data for SQL_clnt and Exchange_clnt to
App_backups, the pool that is defined in the backup action.
Example 4 Legacy Backup Rules is enabled
A Protection group contains two clients, SQL_clnt and Exchange_clnt. The workflow that is
associated with the protection group contains a backup action.
l
Backup action configuration:
n
Destination Pool=App_backups
n
Schedule=daily full backup
n
Client Override Behavior= Legacy Backup Rules
l
The Pool attribute that is defined for the SQL_clnt client resource is SQL_backups.
l
The Pool attribute for Exchange_clnt is not defined.
l
The Full level is enabled in the Levels attribute of a pool resource named Backups.
In this example, NetWorker sends the backup data for SQL_clnt and Exchange_clnt to
Backups, the pool that matches the level Full backup criteria.
Using media pools
81
Backup Storage
Example 5 Legacy Backup Rules is enabled
A Protection group contains two clients, SQL_clnt and Exchange_clnt. The workflow that is
associated with the protection group contains a backup action.
l
Backup action configuration:
n
Destination Pool= App_backups
n
Schedule=daily full backup
n
Client Override Behavior= Legacy Backup Rules
l
The Pool attribute that is defined for the SQL_clnt client resource is SQL_backups.
l
The Pool attribute for Exchange_clnt is not defined.
l
The manual level is enabled in the Levels attribute of a pool resource named Backups.
In this example, NetWorker sends the backup data for SQL_clnt and Exchange_clnt to the
Default pool because a pool does not exist with legacy attributes that match the
configuration for the backup data.
Matching the pool criteria with Legacy Backup Rules enabled
After a migration and configuring media pools, data generated by an action might match
the criteria for more than one media pool configuration. For example, if you configure one
media pool to accept data from a client that is called mnd.emc.com, and you configure
another media pool to accept data from all full backups, NetWorker uses other criteria to
determine which pool of volumes receives the data from a full backup of the
mnd.emc.com client.
The NetWorker server uses the following media pool selection criteria:
1. Groups attribute (highest precedence)
2. Clients attribute
3. Save sets attribute
4. Levels attribute (lowest precedence)
When data matches the attributes for two media pools, for example, Client and Level, the
data is written to the media pool specified in the Client attribute. For example, in the case
where the data from the client matched the criteria for two different media pools, the data
is routed to the media pool that accepts data from the mnd.emc.com client.
The following table details the hierarchy that the NetWorker server uses to determine
media pool selection when a conflict arises. For example, the media pool criteria for
Groups takes precedence over the media pool criteria for Clients, Save sets, and Levels. If
data does not meet the criteria for any customized pool, NetWorker writes the data to the
Default media pool.
Table 22 NetWorker hierarchy for resolving media pool conflicts
Precedence Groups attribute Clients attribute Save sets attribute Levels attribute
Highest
82
x
x
x
x
x
x
x
x
EMC NetWorker 9.0.x Administration Guide
x
x
Backup Storage
Table 22 NetWorker hierarchy for resolving media pool conflicts (continued)
Precedence Groups attribute Clients attribute Save sets attribute Levels attribute
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Lowest
x
Working with media pools
This section explains how to edit, copy, delete, and create media pools.
Creating a media pool
Perform the following steps to create a new media pool.
Before you begin
Perform either of the following:
l
If the Match Bar Code Labels attribute is not used for the Library resource, create a
label template for the media pool.
l
Determine a preconfigured label template to use for the media pool.
Procedure
1. In the Administration window, click Media.
2. In the left pane, select Media Pools.
3. From the File menu, select New.
4. In the Name attribute, type a name for the media pool.
A media pool is associated with a label template. Use a name that clearly associates
the media pool with the corresponding label template.
5. In the Comment attribute, type a description of the media pool.
6. Leave the Enabled attribute selected.
7. For the Pool Type attribute, select the media pool type.
l
Backup—Select this type to configure the pool to receive backup data.
l
Backup clone—Select this option to configure the pool to receive a clone copy of
backup data.
Using media pools
83
Backup Storage
l
Archive—Select this type to configure the pool to receive archive data.
l
Archive clone—Select this option to configure the pool to receive a clone copy of
archive data.
8. In the Label Template attribute, select the matching label template.
9. In the Data Source attribute, select the backup groups that are eligible to back up to
this media pool.
10. (Optional), on the Selection Criteria tab, configure the following options:
l
Devices—Select the devices on which NetWorker can mount volumes for this pool.
l
Media type required—Select which device type NetWorker can use to label
volumes for this pool. You cannot use this attribute when you select an option in
the Media type preferred attribute.
l
Media type preferred—Select the device type that NetWorker should use first to
label a volume for this pool. You cannot use this attribute when you select an
option in the Media type required attribute.
Note
When you do not configure the Media type required or Media type preferred attribute,
you can write data across several volumes of different media types (for example,
magnetic disk and tapes), if the volumes mounted on the storage devices have the
appropriate label associated with the media pool.
11. On Configuration tab, configure the following options:
Attribute
Definition
Auto Media
Verify
Select this attribute to perform automated media verification while
data is written to a volume labeled for this media pool. Auto media
verification on page 86 provides more information.
Max
parallelism
Increase the value to define the maximum number of simultaneous
save streams that NetWorker writes to each device in the pool. The
default value for this attribute is 0, which means that the attribute
has no effect on other parallelism settings. When you set the Max
parallelism attribute to 1, a prolonged delay might occur between
the backup of save sets. To resolve this issue, increase the Max
parallelism attribute for the pool resource. However, when you
increase the pool parallelism value, the time to recover data on the
volume increases.
Note
For AFTD and DD Boost devices, the Max nsrmmd count attribute
value for a device affects the Max parallelism attribute. For
example, consider an AFTD device (AFTD_1) that has a Max
sessions attribute value of 20 and a Max nsrmmd value of 4. Now
suppose a backup pool with a Pool parallelism attribute of 1
selects AFTD_1 . The total number of save sessions that NetWorker
can start for AFTD_1 is 4, one for each nsrmmd process. Tape and
FTD devices can only spawn one nsrmmd process at a time, so if
the previous example used a tape device, then the total number of
save sessions would be 1.
84
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Attribute
Definition
Recycle from
other pools
Select this option to enable NetWorker to use expired volumes that
are labeled for other media pools in this pool that have the Recycle
to other pools attribute enabled, when the NetWorker server does
not have access to blank volumes or volumes eligible for reuse and
assigned to this pool.
Recycle to
other pools
Select this option to enable NetWorker to use expired volumes that
are labeled for this media pool in other pools that have the Recycle
from other pools attribute enabled, when the NetWorker server
does not have access to blank volumes or volumes eligible for
reuse and assigned to the other pool.
Recycle start
Defines the time to start the automatic relabel process each day.
By default this attribute is empty and the automatic relabeling of
recyclable volumes is not done. Use the format HH:MM.
Automatically relabeling volumes in a media pool on page 86
provides more information.
Recycle interval Defines the interval between two starts of the automatic relabel
processes. The default value is 24:00. Use the format HH:MM.
Max volumes to Defines the maximum number of recyclable volumes that
recycle
NetWorker can relabel during each automatic relabel process. The
default value is 200.
Recycle start
now
Select this attribute to start the automatic relabel process of
recyclable volumes for this pool immediately after you create the
pool. The default value is No.
Store index
entries
For archive pools only. Select this attribute to configure an archive
pool that creates client file index entries for the archive save sets.
Clear this option to configure an archive pool that will not create
client file index entries for the archive save sets.
Worm pool/
Create
DLTWORM
Supported WORM and DLTWORM tape drives on page 86
provides more information about how to create Worm pools.
12. Optionally, on the Restricted Data Zones tab, from the restricted datazone list, select
the restricted datazone in which to add the pool.
13. Click OK
If any of the settings for a new media pool match an existing media pool, this
message appears:
Pool(s) pool_name has overlapping selection criteria.
If this message appears, review the media pool configuration and modify any
overlapping criteria.
14. If you did not select a label template when you create the media pool, a message
appears that tells you that NetWorker creates a label template for the media pool,
click OK.
Using media pools
85
Backup Storage
Auto media verification
If the Auto Media Verify attribute is enabled, the NetWorker server verifies data written to
tape volumes from this media pool. This attribute does not apply to AFTD, file type and
Data Domain devices.
Data is verified by repositioning the tape volume to read a portion of the data previously
written to the media. The data read is compared to the original data written. This feature
does not verify the entire length of the tape.
If the data read matches the data written, verification succeeds.
Media is verified when the following occurs:
l
A volume becomes full while saving and it becomes necessary to continue on to
another volume.
l
A volume goes idle because all save sets being written to the volume are complete.
When a volume fails verification, it is marked full so that the server will not select that
volume for future saves. The volume remains full until it is recycled or a user marks it not
full. If a volume fails verification while the server is attempting to switch volumes, all save
sets writing to the volume are terminated.
Auto media verification should not be used to verify the integrity of the data written to the
entire tape. To fully verify the data written to the tape, either restore the tape contents or
clone the data.
Automatically relabeling volumes in a media pool
Automatically relabeling a recyclable volume provides the following benefits:
l
You can relabel volumes outside of the backup window without the need for a
scripted solution.
l
NetWorker has access to appendable volumes at the time of a backup or clone, which
results in faster backup and clone completion times.
Eligible volumes will not be relabeled if the volume is loaded in a device that is:
l
Disabled
l
In use by an nsrmmd process (for example, during a restore operation)
l
In read-only mode
l
Busy
When NetWorker automatically relabels a volume, message to the following appears in
the daemon.raw file on the NetWorker server:
"num_of_volumes volumes will be recycled for pool pool_name in
jukebox jukebox_name."
Supported WORM and DLTWORM tape drives
NetWorker supports write-once, read-many (WORM) tape drives and media. It is able to
recognize the WORM abilities of tape drives and the presence of WORM media in those
drives. It also supports the creation of DLTWORM (formerly DLTIce) tapes in drives that are
DLTWORM capable.
The following table describes the WORM devices that are supported by the NetWorker
software. For a complete listing of supported devices, refer to the EMC NetWorker
Hardware Compatibility Guide.
86
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Table 23 WORM supported devices
Device
Description
HP LTO Ultrium 3
and higher
Unique to HP Ultrium-3 and higher:
Quantum
SDLT600, DLT-S4,
and DLT-V4 (SCSI
and SATA)
Sony AIT-2, AIT-3,
AIT-4, and SAIT
IBM 3592
STK 9840A/B/C,
9940B, T10000
IBM LTO Ultrium 3
and higher, and
Quantum LTO
Ultrium 3 and
higher
l
Inquiry VPD page 0xb0, byte 4 bit 0 indicates WORM capable
l
Read attribute # 0x0408 bit 7 to indicate WORM media present
Any drive with product inquiry data of “*DLT*” tape drive that reports WORM
capability the way these drives do (“Quantum” not required in the vendor
inquiry data):
l
Inquiry data VPD page 0xc0, byte 2, bit 0 to indicate WORM capable
l
Read attribute # 0x0408 bit 7 to indicate WORM media present
Any drive with “Sony” in the vendor inquiry data that reports WORM
capability like these drives do:
l
Mode sense page 0x31, byte 5 bit 0 indicates WORM capable
l
Mode sense byte 4 bit 6 indicates WORM tape present
Unique to IBM 03592:
l
Mode sense page 0x24, byte 7 bit 4 indicates WORM capable
l
Mode sense page 0x23, byte 20 bit 4 indicates WORM tape present
Any drive with STK as the vendor data that reports WORM capability like
these:
l
Standard inquiry data byte 55 bit 2 indicates WORM capable
l
Request sense data byte 24 bit 1 indicates WORM tape present
These drives use the SCSI-3 method to report WORM capabilities, so there is
not a match against any of the inquiry data. Any drive that does not match
the inquiry data patterns listed above will have the SCSI-3 method applied to
them:
l
Inquiry data VPD page
0xb0, byte 4, bit 0 indicates WORM capable
l
Mode sense page
0x1d, byte 2 bit 0 indicates WORM tape present
Byte 4, bits 0,1: label restrictions include
- 00 indicates no overwriting allowed
- 01 indicates some labels can be overwritten
l
Byte 5, bits 0,1: filemark overwrite restrictions
- 0x02: any filemark at EOD can be overwritten except for the one closest
to the beginning of the tape
- 0x03: any filemark at EOD can be overwritten
The WORM and DLTWORM attributes determine whether or not the NetWorker software
will back up to a write once-read many (WORM) tape. You can apply these tape attributes
to any pool.
Using media pools
87
Backup Storage
Note
Various Quantum drive models (SDLT600, DLT-S4, and DLT-V4) have the ability to create
WORM tapes from ordinary blank DLT tapes supported by that particular drive. You
cannot recycle an existing NetWorker tape to create a DLTWORM volume without first
having bulk-erased the tape. When the DLTWORM attribute is set, labeling one of these
drives into a WORM pool causes the Quantum drive to make the current tape a WORM
tape.
Savegroups that belong to pools that have either the WORM or DLTWORM attribute set,
are considered to be WORM savegroups.
How to identify WORM media
Since WORM media cannot be reused, the tapes are uniquely identified as such so that
they are only used when required. As shown in this figure, a (W) is appended to the
volume names displayed in the Volumes window. If a volume is both read-only and
WORM, an (R) is appended to the volume name.
Figure 8 Identifying WORM tapes in the NetWorker Console
Note
Since WORM tapes can only be used once, attempting to relabel a WORM tape always
results in a write protection error. With the exception of pool selection and relabeling, the
NetWorker software treats WORM tapes exactly the same as all other types of tape.
Determining WORM and DLTWORM capability
Procedure
1. In the Administration window, click Devices.
2. Select the drive, right-click, and select Properties.
3. Click the Information tab and observe the WORM capable and DLTWORM capable
attribute settings. NetWorker automatically sets these attributes and, consequently,
they are read-only and cannot be changed.
88
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Note
The WORM capable and DLTWORM capable attributes are dimmed out when the
device in use is WORM capable but does not support DLTWORM (not a Quantum DTLtype drive).
Configuring WORM and DLTWORM support
The following table describes WORM and DLTWORM attributes.
Table 24 WORM/DLTWORM attributes
Attribute
Description
WORM pools
By default, the NetWorker software only allows WORM tapes into WORM pools.
only hold WORM Deselecting this option lets you add new (non-WORM) tapes to a WORM pool.
tape
This is useful when you need WORM functionality but do not have WORM tapes
available.
WORM tapes
only in WORM
pools
By default, NetWorker only lets you label WORM tapes into WORM pools. Clear
this option when:
You do not want to segregate WORM tapes within WORM pools.
A volume is needed to complete a group and a non-WORM tape is
unavailable.
WORM capable
This attribute indicates that this drive supports the use of WORM media.
DLTWORM
capable
This attribute indicates that this drive can create DLTWORM tapes from a blank
tape.
WORM pool
This pool should hold WORM tapes (depending on the setting of “WORM pools
only hold WORM tape” in the server).
create
DLTWORM
If selected, before the NetWorker software labels a tape in a drive capable of
creating DLTWORM volumes, NetWorker will try to convert the tape into a
DLTWORM tape. If that conversion fails, the labeling for that tape will fail. If a
tape drive in a pool where this attribute is set cannot create DLTWORM tapes,
(that is, the tape drive is not a Quantum SDLT600, DLT-S4 or DLT-V4 tape drive,
this attribute is simply ignored.
Refer to the Quantum web site for information on which tapes can be
converted to DLTWORM tapes. Not all firmware revisions for all of these
devices support WORM operation. Check the tape drives website to make
sure that your drive has up-to-date firmware.
Procedure
1. In the Administration window, click Media.
2. In the left pane, select Media Pools.
3. In the right pane, select the appropriate pool.
4. Right-click and select Properties.
5. Click the Configuration tab and select one of these WORM tape handling attributes:
l
WORM pools only hold WORM tapes
l
WORM tapes only in WORM pools
Using media pools
89
Backup Storage
6. Click OK when finished making the necessary selections.
Note
If you attempt to assign a non-WORM capable drive to a WORM pool an error message
is generated.
Editing a media pool
Perform these steps to edit an existing media pool.
Note
You cannot change the name of a media pool. Preconfigured media pools cannot be
modified.
Procedure
1. In the Administration window, click Media.
2. In the left pane, select Media Pools.
3. In the right pane, perform one of the following tasks:
l
To modify multiple attributes in a single configuration resource by using the Media
Pool Properties window, right-click the staging configuration and select
Properties.
l
To modify a specific attribute that appears in the resource window, place the
mouse in the cell that contains the attribute that you want to change, then rightclick. The menu displays an option to edit the attribute. For example, to modify the
Comment attribute, right-click the resource in the Comment cell and select Edit
Comment.
Note
To modify a specific attribute for multiple resources, press and hold the Ctrl key,
select each resource, and then right-click in the cell that contains the attribute that
you want to change. The menu displays an option to edit the attribute.
4. Make any required changes, then click OK.
Copying a media pool
Perform these steps to create a copy of a pool resource.
Procedure
1. In the Administration window, click Media.
2. In the left pane, select Media Pools.
3. In the right pane, select the media pool.
4. From the Edit menu, select Copy. The Create Media Pool dialog box appears,
containing the same information as the media pool that was copied, except for the
Name attribute.
5. In the Name attribute, type a name for the new media pool.
6. Edit any other attributes as appropriate, and click OK.
90
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Deleting a media pool
You can delete a media pool only if the media database does not contain information
about active volumes that are labeled for the media pool. You cannot delete a
preconfigured media pool.
Procedure
1. In the Administration window, click Media.
2. In the left pane, select Media Pools.
3. In the right pane, select the media pool.
4. From the File menu, select Delete.
5. When prompted, click Yes to confirm the deletion.
Storage nodes
Storage nodes (including the NetWorker server) are host computers with attached storage
devices. A storage node has the physical connection and ownership of the attached
devices, but the NetWorker server maintains the client file index and media database.
With the NetWorker software, client data can be routed directly to a storage node’s
storage devices without the data first going to the NetWorker server. A storage node may
be a client of the NetWorker server, although this is not a requirement. However, the
storage node must have the NetWorker client software installed.
From the NetWorker server, typical storage tasks can be performed, such as:
l
Mounting and labeling volumes for the storage node devices.
l
Configuring NetWorker resources associated with the storage nodes.
Only users who have the Configure NetWorker privilege can add to or change the
configuration of the NetWorker server, media devices, and libraries. The EMC NetWorker
Security Configuration Guide provides more information.
Requirements
To operate the NetWorker software with storage nodes, certain requirements must be
met.
l
On UNIX systems, this software must be installed on the storage nodes. The packages
must be installed in the following order:
1. NetWorker client software
2. NetWorker storage node software
l
On Windows systems, the Storage Node Option must be installed. The Storage Node
Option installs both the NetWorker client and storage node software.
Licensing
The EMC NetWorker Licensing Guide provides information on NetWorker licensing support
for storage nodes.
Storage node configuration
The following sections provide the procedures for configuring a NetWorker storage node.
Storage nodes
91
Backup Storage
Configuring a storage node
The storage node appears in the navigation tree.
Procedure
1. Ensure the storage node software and required enabler codes have been installed on
the host.
2. In the NetWorker server Administration interface, click the Devices view.
3. From the navigation tree, right-click Storage Nodes, and select New.
The Create Storage Node window appears, with the General tab displayed.
4. Set the Identity attributes:
a. In Name, specify the hostname of the NetWorker storage node.
b. In Type of Storage Node, select a type:
l
SCSI
l
NDMP
l
SILO (or SILO with NDMP)
Note
The silo robotic arm must not be detected by the NDMP storage node.
5. In the Status attributes, review or set the storage node status:
a. Storage node is configured indicates whether a device has already been
configured on this storage node.
b. Enabled indicates whether the storage node is available for use:
l
Yes indicates available state.
l
No indicates service or disabled state. New device operations cannot begin and
existing device operations may be canceled.
c. Ready indicates whether the storage node is ready to accept device operations.
6. Set the Device Management attributes:
a. In Max active devices, set the maximum number of devices that NetWorker may
use from this storage node in a DDS environment.
b. In AFTD allowed directories, for AFTD devices, type the pathnames of directories on
the storage host where AFTDs are allowed to be created.
c. In mmds for disabled devices, select a nsrmmd (data mover) option (see note):
l
Yes to start nsrmmd processes for disabled devices.
l
No to not start nsrmmd processes for disabled devices.
d. In Dynamic nsrmmds, for AFTD or DD Boost devices, select whether nsrmmd
processes on the storage node devices are started dynamically.
92
l
Selected (dynamic mode): NetWorker starts one nsrmmd process per device
and adds more only on demand, for example, when a device's Target sessions
is reached.
l
Unselected (static mode): NetWorker runs all available nsrmmd processes.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
In environments where unattended firewall ports must be restricted for security
reasons, the storage node settings for mmds for disabled devices and Dynamic
nsrmmds unselected (static mode) offer more control because they cause all
available nsrmmd firewall ports to be attended by running nsrmmd processes.
7. In Remote Host, if an NDMP tape library is used by this storage node, type the Remote
User name and Password. Only one user is allowed per storage node.
8. Select the Configuration tab.
9. In Scanning, set the attributes for SCSI library target devices on this storage node:
a. In Device Sharing Mode, select an option:
l
Server Default uses the NetWorker server setting for device sharing.
l
Maximal Sharing allows sharing of all devices.
l
No Sharing disables device sharing.
b. In Search all LUNs, select an option:
l
Yes for NetWorker to detect all LUNs (Iogical unit numbers). Detection can be
time consuming.
l
No (default) for NetWorker to stop searching at the first available LUN.
c. In Use persistent names, choose whether NetWorker uses persistent device names
specific to the storage host operating system when performing device discovery
and autoconfiguration operations.
d. In Skip SCSI targets, list any SCSI targets to exclude from backup operations, one
per line, if the storage node type is set to SCSI. The format is bus.target.lun where
the target and LUN fields are optional. You can exclude a maximum of 63 targets.
10. For AFTD or DD Boost devices, configure the following settings in Advanced Devices:
l
In Server network interface, type the unique network interface hostname of the
NetWorker server to be used by the storage nodes.
l
In Clone storage nodes, list by priority the hostnames of the storage nodes to be
used for the save or “write source” side of clone operations originating from this
storage node as the “read source.” The clone operation selects the first storage
node in this list that has an enabled device and a functional nsrmmd process.
If the Clone storage nodes attribute does not contain a value, then the device
operations use the value defined in the Clone storage nodes attribute for the
Storage Node resource that was created for the NetWorker server. If the Clone
storage nodes attribute for the storage node resource is empty, then device
operations use the values that are defined in Storage nodes attribute for the client
resource that was created for the NetWorker server.
In backup-to-disk environments, it is possible for a single backup volume to be
shared by multiple storage devices on different storage nodes. This can result in
an ambiguous clone write source.
11. When finished, click OK.
Modifying the timeout attribute for storage node operations
An attribute named nsrmmd Control Timeout, which is set during NetWorker server
configuration, configures the amount of time a NetWorker server waits for a storage node
request to be completed. If the timeout value is reached without completion of the
Storage node configuration
93
Backup Storage
request, the operation stops and an error message is logged. The default value assigned
to Nsrmmd Control Timeout is five minutes.
Procedure
1. In the server’s Administration interface, click the Configuration button.
2. Select View > Diagnostic Node.
3. Right-click the NetWorker server in the left pane and select Properties.
4. Select the Media tab.
5. Modify the attributes as appropriate and click OK.
Configuring timeouts for storage node remote devices
Timeouts that determine how long to wait for mount requests on a storage node remote
device before the save is redirected to another storage node are set in the Properties
window of a device.
The Storage Node Devices area of the tab includes these attributes related to storage
node timeouts:
l
Save Mount Timeout
l
Save Lockout
Save Mount Timeout and Save Lockout attributes change the timeout of a save mount
request on a remote device.
If the mount request is not satisfied within the time frame specified by the Save Mount
Timeout attribute, the storage node is locked out from receiving saved data for the time
specified by the Save Lockout attribute.
The default value for Save Mount Timeout is 30 minutes. The default value for Save
Lockout is zero, which means the device in the storage node continues to receive mount
requests for the saved data.
Note
The Save Mount Timeout applies only to the initial volume of a save request.
To modify the Save Mount Timeout and Save Lockout attributes, perform the following
steps.
Procedure
1. In the server’s Administration interface, click the Devices button.
2. Select View > Diagnostic Node.
3. Right-click the remote device and select Properties.
4. Select the Advanced tab.
5. Modify the attributes as appropriate and click OK.
Balancing the load on the storage node
The Save Session Distribution feature allows you to configure how NetWorker distributes
save sessions between the storage nodes.
Note
This feature is not available for clone and recover operations.
You can apply this feature to all NetWorker clients or to selected clients. This feature has
two options:
94
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
Max sessions—Distributes save sessions that are based on the setting in the Max
sessions attribute in storage node device resource. This is the default distribution
method.
l
Target sessions—Distributes save sessions that are based on the setting defined in
the Target session attribute in each storage node device resource.
The Target sessions option is more likely to spread the backup across multiple storage
nodes. The Max sessions option is more likely to concentrate the backup load on fewer
storage nodes.
When you select the Max sessions option, the NetWorker server distributes the save
sessions for a client among eligible storage nodes as follows:
1. Identifies the available storage nodes in the NetWorker client’s storage node affinity
list.
2. Uses an available device on the first storage node in the list that is working below its
Target sessions level.
3. When all devices on the first storage node are running at their target sessions level
but some are running below their max sessions level, then NetWorker uses the least
loaded device.
4. Continues until all available devices on all storage nodes in the client’s storage node
affinity list are in use.
When you select the Target sessions option, the NetWorker server distributes save
sessions among eligible storage nodes as follows:
1. Identifies the available storage nodes in the storage node affinity list for the client.
2. Uses an available device on the first storage node in the list that is working below its
Target sessions level.
3. When all devices on the first storage node are running at their target sessions levels,
continue to the next storage node even if some devices are running below their max
sessions level.
4. When all devices on all eligible storage nodes are running at their target sessions
level, use the least loaded device that is running below its max session value.
5. Continues to send data to the least loaded device that is running below the max
session value, until all devices on all available storage nodes are running at their max
session levels.
Be aware of the following performance considerations for storage node load balancing:
l
Depending on the configuration of the backup environment, there is a potential to
shorten the backup times by using the device Target session option rather than the
device Max session option. However, using the device Target sessions option with
the checkpoint restart feature can result in slower recovery times because a single
save set is more likely to be spread across multiple storage nodes.
l
Each NetWorker client has a storage node affinity list. The Save sessions distribution
feature can only distribute a backup session for a client to multiple storage nodes
when the client resource has two or more storage nodes in its storage node affinity
list. The storage node affinity list is specified on the Globals (2 of 2) tab in the
NetWorker Client Properties window.
Configuring the storage node affinity list for a client
Storage node affinity is a feature that determines which NetWorker servers and storage
nodes receive the data from a client. Define the storage node affinity list in the Storage
Nodes attribute of the Client resource.
For most Client resources, the default setting for the Storage Nodes attribute is
nsrserverhost, which represents NetWorker server host. To configure the NetWorker server
Storage node configuration
95
Backup Storage
to direct the data for a client to a storage node device, modify the Storage Nodes attribute
and specify the name of the storage node in the Storage Nodes attribute of the Client
resource on a line above the default nsrserverhost entry.
If you create the Client resource for a storage node after you create the remote device on
the storage node, the default setting of the Storage Nodes attribute is the storage node
and the NetWorker server.
To modify the Storage Nodes attribute for a client, perform the following steps:
Procedure
1. In the Administration window, click Protection.
2. In left navigation pane, expand Clients, right-click the appropriate client, and select
Properties.
3. On the Globals (2 of 2) tab in the Storage Nodes attribute, specify the hostname of the
storage node, and then click OK.
Results
The NetWorker software directs the client data to the first storage node in the affinity list
with an enabled device, capable of receiving the data. The NetWorker software sends
additional saves to the next storage node in the storage node affinity list that is based on
criteria that are specified in Balancing the load on the storage node on page 94.
Specifying storage node load balancing
By default, NetWorker balances client backups across storage nodes that are based on
the Max sessions attribute for each device on the storage node. If you choose to balance
storage node loads by Max sessions, you can override this setting for selected clients.
Procedure
1. On the Administration window, click the Server button.
2. From the View menu, select Diagnostic Mode.
3. Right-click the NetWorker server in the left pane, and select Properties.
4. On the General tab, select a value from the Save session distribution list:
l
If you select Target sessions, then the NetWorker server balances the backups for
all NetWorker clients across the storage nodes, based on device target session
value. The NetWorker server ignores the value that is defined in Save session
distribution attribute for each NetWorker client.
l
If you select Max sessions, then you can still override this value for selected
NetWorker client resources by setting the Save session distribution attribute in the
client resource.
5. Click OK.
Overriding the save session distribution method for selected clients
If you selected Max sessions as the Save session distribution method for the NetWorker
server, you can use the following procedure to override the setting for selected clients.
Procedure
1. On the Administration window, click the Protection button.
2. In the left navigation pane, expand Clients.
3. Right-click the appropriate client and select Properties.
4. On the Globals (1 of 2) tab, select Target sessions from the Save session distribution
list.
96
EMC NetWorker 9.0.x Administration Guide
Backup Storage
5. Click OK.
Performance considerations for storage node load balancing
Be aware of the following performance considerations for storage node load balancing:
l
Depending on how your backup environment is configured, there is a potential to
shorten backup times by using the device target session option rather than the
device maximum session option. However, using the device target sessions option
with the Checkpoint restart feature can result in slower recovery times because a
single save set is more likely to be spread across multiple storage nodes.
l
Each NetWorker client has a storage node affinity list. The Save sessions distribution
feature can only distribute a NetWorker client’s backup sessions to multiple Storage
nodes if the client has two or more storage nodes in its storage node affinity list. The
storage node affinity list is specified on the Globals (2 of 2) tab in the NetWorker
Client Properties window.
Multiplexing
Multiplexing is the ability to write multiple data streams simultaneously to the same
storage device. It is often more efficient for the NetWorker server to multiplex multiple
save sets to the same device. There are also times when limiting the number of data
streams to a particular device improves performance of the NetWorker environment.
Use the Target sessions, Max sessions, and Pool parallelism attributes to increase or
limit the number of data streams that NetWorker writes to a device.
Target sessions
Use the Target sessions attribute on the Configuration tab of the Device resource to
define the optimal number of backup sessions to assign to an active device.
Target sessions is not a hard limit; to set a hard limit for the number of sessions that a
particular device can accept, use the Max sessions attribute.
The Target sessions attribute aids in load balancing devices by determining when the
NetWorker software should write save streams to a device.
When a save session starts, the following actions occur:
l
If a device is already receiving the number of backup sessions determined by the
target sessions value, the NetWorker server uses the next underutilized device for the
backups.
l
If all available devices are receiving the number of backup sessions determined by
their target sessions value, the NetWorker server overrides the set value and uses the
device with the least activity for the next backup session.
Because it is often more efficient for the NetWorker server to multiplex multiple save sets
to the same device, rather than write each save set to a separate device, the NetWorker
server attempts to assign to each device a number of save sets, up to the value of target
sessions, before assigning a save set to another device.
NOTICE
When the NetWorker software assesses how many devices need to be involved in
multiple save streams assignments with the same storage node, the device with the
lowest target session value is used as a reference.
Max sessions
The Max sessions attribute on the Configuration tab of the Device resource defines the
maximum number of save sessions for a device. The max sessions value is never less
than the target sessions value.
Storage node configuration
97
Backup Storage
Bootstrap backup on a storage node
When the NetWorker server backup action performs a backup of the bootstrap save set,
the data writes to a device that is local to the NetWorker server. You cannot back up
bootstrap data to a remote device, but you can clone or stage the bootstrap to a remote
device. When you recover a bootstrap save set, you must recover the data from a local
device.
Staged bootstrap backups
The NetWorker server can send bootstrap backups to a disk device, such as an AFTD or
FTD device. If you stage the bootstrap backup to another device , the staging operation
completes and NetWorker reports that the staging operation is complete although the
recover space operation has not started. This report means that the staged bootstrap
backup remains on the source disk device. If you accidentally delete the staged
bootstrap data, you can use the scanner command on the source disk to scan the
bootstrap data into the media database . If the bootstrap data is not staged from the
original disk, the data on the original disk is subject to the same browse and retention
policies as any other save set backup and is subject to deletion after the retention policy
expires.
This bootstrap information also applies to NDMP devices.
Troubleshooting storage node affinity issues
If a backup fails because of a problem related to the storage node affinity, a message
similar to the following might appear:
no matching devices; check storage nodes, devices or pools
Possible causes for this error message include:
l
No enabled devices are on the storage nodes.
l
The devices do not have volumes that match the pool required by the backup
request.
l
All devices are set to read-only or are disabled.
For example, if the client has only one storage node in its Storage Node list, and all
devices on that storage node are disabled, fix the problem and then restart the backup.
Complete one of the following actions to fix the problem:
l
Enable devices on one of the storage nodes in the storage node list for the client.
l
Correct the pool restrictions for the devices in the storage node list.
l
Configure an additional storage node that has enabled devices that meet the pool
restrictions.
l
Set one of the devices to read/write.
Configuring a dedicated storage node
All devices created on storage nodes, except the devices for the NetWorker server include
the Dedicated Storage Node attribute. A dedicated storage node can only back up data
that originates from the storage node host. When you configure a storage node as a
dedicated storage node, you require a Dedicated Storage Node license.
After you create a storage node, perform the following steps to configure the storage
node as dedicated.
98
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Procedure
1. On the Administration window, click Devices.
2. In the left navigation pane, expand Storage Nodes, right-click the storage node, and
then select Properties.
3. On the Configuration tab, in the Dedicated Storage Node option, select Yes.
4. Click OK.
Troubleshooting storage nodes
This section provides troubleshooting information about storage nodes.
Storage node affinity errors
A storage node affinity problem may exist when a backup fails with an error message
similar to the following:
No matching devices; check storage nodes, devices or pools
This error message can appear for the following reasons:
l
All the devices in the storage node are disabled.
l
Each device in the storage node contains a volume that does not match the pool that
the backup request requires.
l
All the devices in the storage node are set to read-only.
To resolve this error:
l
Enable devices on one of the storage nodes.
l
Correct the pool restrictions for the devices that are listed in the Storage Nodes
attribute of the Pool resource.
l
Add another storage node that has enabled devices and meets the pool restrictions
to the Storage Nodes attribute of the Pool resource.
l
Write-enable one of the devices.
l
Adjust the Save Mount Timeout and Save Lockout attributes for in the Device
resource for the storage node.
Storage node timeout errors
If the nsrd process starts on the NetWorker server and detects that a setting for the
NSR_MMDCONTROL variable exists, a message similar to the following appears:
NSR_MMDCONTROL env variable is being ignored
use nsrmmd control timeout attribute instead
If you receive this message, perform the following steps.
1. Shut down the NetWorker services.
2. Remove the environment variable setting for NSR_MMDCONTROL.
3. Restart the NetWorker services.
4. Use NMC to connect to the NetWorker server.
5. Adjust the value of the nsrmmd Control Timeout attribute in the Storage Node
resource to the value that was assigned to the NSR_MMDCONTROL variable, or to a
value that best meets the current requirements. Modifying the timeout attribute for
storage node operations on page 93 provides more information.
Troubleshooting storage nodes
99
Backup Storage
Disk storage devices
NetWorker software supports a variety of different backup to disk (B2D) methods. These
methods all use disk files that NetWorker creates and manages as storage devices. These
devices can reside on a computer’s local disk or a network-attached disk. NetWorker
supports FTD, AFTD, DD Boost, and cloud disk device types. This section does not cover
disk-based devices that emulate other device types, such as virtual tape libraries (VTLs).
The EMC NetWorker Licensing Guide provides information about NetWorker B2D and DD
Boost licensing.
FTD
A file type device (FTD) is a basic disk device type that has been available for many years.
FTDs have limited use and support and this chapter describes them for legacy purposes
only.
AFTD
Advanced file type devices (AFTDs) support concurrent backup and restore operations
and require the NetWorker DiskBackup Option (DBO) license. AFTDs are supported for the
following configurations:
l
A local disk on a NetWorker storage node.
l
A network-attached disk device that is NFS-mountable to a NetWorker storage node
running a Linux or UNIX operating system.
l
A network-attached disk device that is CIFS-mountable to a NetWorker storage node
running on Windows.
The Client Direct feature enables NetWorker clients to back up directly to AFTDs over a
CIFS or NFS network, bypassing the storage node. For Client Direct backups, the storage
node manages the devices but does not handle the backup data unless the Client Direct
workflow is not available.
DD Boost devices
DD Boost devices reside on Data Domain storage systems that have the DD Boost
features enabled. These devices are similar to AFTDs except they store backup data in a
highly compressed and deduplicated format. The DD Boost API accesses the DD Boost
devices over a network. NetWorker can perform DD Boost backups through either the
NetWorker storage node workflow or the Client Direct file access workflow.
The Client Direct workflow enables NetWorker clients with distributed segment
processing (DSP) and network access to deduplicate their own backup data and send the
data directly to the DD Boost devices. This method bypasses the storage node and frees
up network bandwidth. The storage node manages the devices but does not handle the
backup data workflow if the Client Direct workflow is available.
If Client Direct backup is not available, NetWorker automatically routes the backup
through the storage node where it is deduplicated and sent to the DD Boost devices for
storage. Restore operations work similarly. If Client Direct is not available for a restore,
then NetWorker performs a traditional storage node recovery.
This guide does not cover DD Boost operations. The EMC NetWorker Data Domain Boost
Integration Guide provides details on DD Boost devices
Cloud devices
Cloud devices are specific to cloud storage services, such as ATMOS. NetWorker accesses
cloud services through a private network.
100
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Example environment
The following figure shows various backup-to-disk options deployed in a mixed operating
system environment.
l
Linux/UNIX Storage Node A writes its backups to either of the following:
n
The AFTD through an NFS connection to Disk Device 1.
n
The AFTD on Local Disk 1.
l
Windows Storage Node B uses a CIFS connection to back up to the NAS AFTD on Disk
Device 2.
l
Data Domain system C writes its backups to a DD Boost device on Local Disk 2.
Figure 9 Example NetWorker disk backup configuration in a mixed backup environment.
Considerations for Client Direct clients
Client Direct backups enable clients to bypass the storage node and back up directly to
storage devices. The storage node manages the devices but does not handle the backup
data. Device configuration for Client Direct clients depends on the type of storage device
and how it is connected to the storage nodes.
A Client Direct backup reduces bandwidth usage and bottlenecks at the storage node,
and provides highly efficient backup data transmission.
If a Client Direct backup is not available, a traditional storage node backup occurs
instead.
Requirements for Client Direct backups
Ensure that the environment meets the following requirements to perform Client Direct
backups:
l
NetWorker clients on UNIX/Linux or Microsoft Windows can perform non-root and
cross-platform Client Direct backups to AFTDs. The AFTD can be managed by either a
UNIX/Linux or a Windows storage node, and can be either local or mountable on the
storage node.
To perform non-root and cross-platform Client Direct backups to AFTDs, the
NetWorker server and the storage node software must be version 8.1 or later.
Example environment
101
Backup Storage
l
If an NFS server provides the AFTD storage for Client Direct backups, then the NFS
server must permit access by using the NFSv3 protocol with AUTH_SYS (AUTH_UNIX)
authentication. The NFS server also must not restrict access to clients by using only
privileged ports.
l
If you enable checkpoint restart for a client, then Client Direct backups are supported
only to AFTDs, and not to DD Boost devices. If a client is enabled for checkpoint
restart and a Client Direct backup is tried to a DD Boost device, then the backup
reverts to a traditional storage node backup instead.
For Client Direct backups to AFTDs, checkpoint restart points are made at least 15
seconds apart. Checkpoints are always made after larger files that require more than
15 seconds to back up.
l
Archive operations are not currently supported for Client Direct backups.
Configuring Client Direct backups
Procedure
1. Ensure that the clients that perform Client Direct backups have a network connection
and a remote network protocol to reach the storage device.
Windows clients can use a CIFS or NFS path, although a CIFS path generally yields
better performance. UNIX clients must use an NFS path.
2. Specify the complete path for the destination device in the Device access information
attribute on the General tab of the Device Properties dialog box for the destination
device.
Keep in mind the following points when you specify the path:
l
If the storage device is directly attached to a Windows storage node, then the
storage node uses a different path than the Client Direct clients. If the storage
device is not directly attached to any storage node, then the path is the same for
all storage nodes and Client Direct clients.
l
The device access information path should include multiple access paths to cover
local and remote use cases.
l
To specify an NFS path, use the NFS_host:/path format regardless of whether
the AFTD is local to the storage node or mountable on the storage node. Non-root
UNIX/Linux NetWorker clients require this NFS format for Client Direct access.
l
For Windows Client Direct backups, specify a CIFS path instead of an NFS path. A
CIFS path generally yields better performance.
l
If you are setting up an AFTD on a Windows storage node, specify the CIFS path
first. For example:
\\fileserver\aftd1
fileserver:/aftd1
l
If you are setting up a UNIX/Linux storage node, specify the NFS path first. For
example:
fileserver:/aftd1
\\fileserver\aftd1
The following figure shows an example set of paths for a CIFS AFTD.
102
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Figure 10 Paths for CIFS AFTD
3. If an NFS server provides the AFTD storage for Client Direct backups, then specify the
username and password that is required to access the NFS server for the AFTD in the
Remote user and Password attributes on the Configuration tab of the Device
Properties dialog box for the device.
4. Ensure that the Client direct attribute is enabled on the General tab of the Client
Properties dialog box for each Client Direct client.
Client Direct backups are enabled by default.
Select View > Diagnostic Mode in the Administration interface to access the Client
direct attribute in the Client Properties dialog box.
Cloud backup devices compared to other device types
NetWorker backup, staging, cloning, and recovery to cloud storage devices are similar to
those operations that are performed with conventional devices. However, cloud devices
also have unique features.
The following table lists the major similarities with other backup device types as well as
the unique features of a cloud storage device.
Table 25 A comparison of cloud devices to other device types
Feature
Cloud backup device AFTD device Tape device
Same volume mounted simultaneously on Yes
multiple devices
No
No
Staging source
No
Yes
No
Staging destination
Yes
Yes
Yes
Cloning
Yes
Yes
Yes
Auto mount and unmount
Yes
No
Yes *
Data transformation engine
(enables encryption and compression on
storage node)
Yes
No **
No **
* When the tape is controlled by a tape library.
** Encryption and compression can still be enabled through NetWorker client side directives.
Cloud backup devices compared to other device types
103
Backup Storage
Differences between FTDs, AFTDs, and DD Boost devices
The following table lists the functional differences between traditional file type devices
(FTDs), AFTDs, and DD Boost devices.
The EMC NetWorker Data Domain Boost Integration Guide provides details on DD Boost
devices.
Table 26 Differences between disk devices
Function or operation File type device
(FTD)
Advanced file type
device (AFTD)
Create a device
l
Device Configuration
Wizard
l
Device Property
Window
Device Property
Window
Select the media
type: file.
UNIX/Linux storage
node:
local or NFS only.
DD Boost device
l
Device
Configuration
Wizard
l
Device
Property
Window
Select media type:
adv_file.
Select media
type:
Data Domain
UNIX/Linux storage
node: local
or NFS only.
Windows storage
node: local
path only. CIFS is not
supported for
FTDs.
Windows storage
node: local or
CIFS using UNC path or
using NFS:
Remote user,
Password.
Storage location
Specified in the
Name attribute.
Specified in the Device
Access Information
attribute.
Specified in the
Device Access
Information
attribute.
Concurrent operations
No
Yes
Yes
Concurrent AFTD
recovery operation
limitations on page
120 provides
more information about
performing
concurrent recovery
operations from an
AFTD.
Reclaiming or
recovering space
104
EMC NetWorker 9.0.x Administration Guide
The nsrim program
removes both
aborted and expired
save sets, once every
24 hours, following
completion of a
savegroup (if you
l
Aborted save sets
immediately removed.
l
The nsrim program
removes expired save
sets from the media
database once every
24 hours, following
completion of a
l
Reclaims only
data that is
unique, not
required by
other existing
backups.
l
NetWorker
does not
Backup Storage
Table 26 Differences between disk devices (continued)
Function or operation File type device
(FTD)
Advanced file type
device (AFTD)
have set volume
recycle to Auto).
savegroup (if you have
set volume recycle to
Auto). NetWorker
removes space on the
AFTD as specified in
the Reclaim Space
Interval of the staging
policy.
DD Boost device
immediately
remove
aborted save
sets, but
marks them
recyclable. A
restarted save
can be
deduplicated.
Otherwise,
NetWorker
removes the
aborted save
set during the
next Recover
Space
operation.
Volume default capacity If the file type device Does not apply.
for devices
was used before
setting the Volume
Default Capacity
attribute, the data
for that file type
device must be
staged or cloned to
another device.
Does not apply.
AFTD Percentage
Capacity
Does not apply.
When file system or
volume is full
Does not apply.
l
l
Waiting
message is
displayed if no
writable volume
available or until
volume
becomes
available.
Volume marked
full and is no
longer available
for backups until
the volume
becomes
appendable.
A setting determines the
capacity that NetWorker
software should stop
writing to an AFTD: spans
from 1% to 100%.
l
Message is displayed
stating file system
requires more space.
l
The nsrim program
invoked to reclaim
space for expired save
set on AFTD.
l
Notification is sent by
email stating device is
full.
l
Device waits until
space become
available. The volume
is never marked as
full.
Backup to a DD
Boost device fails
and stops when
full.
Differences between FTDs, AFTDs, and DD Boost devices
105
Backup Storage
Table 26 Differences between disk devices (continued)
Function or operation File type device
(FTD)
Advanced file type
device (AFTD)
DD Boost device
Save set continuation
Yes
No. Save sets that start on
an AFTD must be
completed on the same
device.
No. Save sets that
start on a DD Boost
device must be
completed on the
same device.
Data format in device
EMC Open Tape
Format (OTF).
Save stream (uasm) format Deduplicated
(uses less space).
Cloning operations
Save sets are cloned
one at a time. Both
automatic and
manual cloning can
begin only after all
the save sets in a
savegroup are
backed up.
Save sets are cloned one
at a time. Automatic
cloning begins after the
save sets are backed up.
Manual cloning of a save
set can begin when it has
finished its backup.
Two simultaneous clone
operations
can be run from the
command prompt,
provided no backup,
recover, or stage
operations are running
simultaneously. The
syntax is as follows:
The EMC NetWorker
Data Domain Boost
Integration Guide
provides details for
advanced CCR
cloning and
replication with DD
Boost devices.
nsrclone -S [ssid
/cloneid1]
nsrclone -S [ssid
/cloneid2]
Client Direct backup:
the storage node
manages the devices
for the NetWorker
clients, but the clients
send their backup data
directly to the devices
via network access,
bypassing the storage
node.
No.
Yes.
Yes.
Clients send their own
backup data
directly to the storage
devices. If Client
Direct backup is not
available, a traditional
storage node backup is
performed.
Clients use DD
Boost
DSP functionality
to deduplicate
their own backup
data before
sending it directly
to the storage
devices. If Client
Direct backup is
not
available, a
traditional storage
node backup is
performed.
NetWorker archive
operations are
not supported for Client
Direct backup.
NetWorker archive
operations are not
106
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Table 26 Differences between disk devices (continued)
Function or operation File type device
(FTD)
Advanced file type
device (AFTD)
DD Boost device
supported for
Client Direct
backup.
Device target and max sessions default values and ranges
There are default values and ranges for device target and max sessions in the NetWorker
Administration interface.
The following table lists the default values for target and max sessions values.
Table 27 Default values and ranges for target and max sessions attributes
Device type
Default target
sessions
Default max
sessions
Recommended
sessions*
Range
AFTD (traditional
storage)
4
32
1 - 32
1 - 512
AFTD (including Data
Domain CIFS/NFS)
4
32
1 - 10
1 - 512
Data Domain (DD
Boost)
6
60
1 - 10
1 - 60
Cloud
1
512
Any
1 - 512
NDMP
4
512
1 - 32
1 - 512
FTD (traditional)
4
32
1 - 16
1 - 512
VTL/Tape (traditional)
4
32
1 - 16
1 - 512
VTL/Tape (Data
4
Domain / Deduplicated)
32
1-1
1 - 512
* The recommended session values are guidelines only and are subject to bandwidth, data type,
and device capabilities.
Advanced file type devices
Advanced file type devices (AFTDs) overcome the main restrictions of traditional file type
device (FTD) storage. AFTD storage is designed for large disk storage systems that use a
volume manager to dynamically extend available disk space if the disk runs out of space
during backup.
The EMC NetWorker Online Software Compatibility Guide provides a list of supported
volume managers.
Device target and max sessions default values and ranges
107
Backup Storage
Memory requirements for AFTD backups
The physical memory requirements for a NetWorker storage node and Client Direct client
depends on the peak AFTD usage.
The following is the list of physical memory requirements for AFTD:
l
Allowing for other types of devices and services on a typical storage node, a storage
node should have a minimum of 8 GB of RAM to host AFTDs.
l
AFTD clients require a minimum of 4 GB of RAM at the time of backup to ensure
optimum performance for Client Direct backups. Client Direct backups require client
access to the AFTDs on either a CIFS or NFS network.
l
Each AFTD requires an initial 24 MB of RAM on the storage node and Client Direct
client. Each AFTD save session requires an additional 24 MB. To run 10 sessions
requires 24 + 240 MB. The default max sessions of 60 sessions per AFTD requires 24
+ 1440 MB.
Required AFTD DFA device settings for Hyper-V environments
For Hyper-V environments, when creating a NetWorker AFTD DFA device on an NTFS or
ReFS volume, Microsoft requires certain settings.
If the NetWorker AFTD DFA device is created on an NTFS volume, virtual hard disk files
must be uncompressed and unencrypted. If the NetWorker AFTD DFA device is created on
an ReFS volume, virtual hard disk files must not have the integrity bit set.
Create and configure an AFTD
You can create an AFTD by using either the Device Wizard or the device properties
window.
Creating an AFTD by using the Device Wizard
If you are creating an AFTD to use the client direct feature, see Considerations for Client
Direct clients on page 101 for information about specifying network path information
when creating the AFTD.
Procedure
1. In the NMC Enterprise view, double-click the NetWorker managed application to
launch its window.
2. In the NetWorker Administration window, select the Devices view.
3. Verify that the path to the storage directory that will contain the AFTDs is allowed.
a. In the navigation tree, select Storage Nodes.
b. Right-click the storage node that you will use, and select Properties.
c. In the AFTD allowed directories list, verify or type the path of the storage directory
that will contain the AFTDs.
AFTDs can be created and accessed only by these listed paths. If this list is left
empty, there are few restrictions as to where a device path can be created.
d. Click OK.
4. In the navigation tree, right-click Devices, and select New Device Wizard.
5. In the Select the Device Type window, select AFTD and click Next.
6. In the Select Storage Node window, specify the path to the storage directory that will
contain the AFTDs.
108
EMC NetWorker 9.0.x Administration Guide
Backup Storage
a. In the Storage Node list, select the storage node that you will use.
b. If the directory for the intended AFTDs is on a different storage node or a remote
storage system, select Device storage is remote from this Storage Node and type
the Network Path of the remote host directory that will contain the devices.
For example, if the storage node is a Microsoft Windows system and you use a CIFS
AFTD on a remote storage system host, this path could be something like the
following:
\\dzone1_storhost2.lss.corp.com\share-1
This storage path is not a device. It is the directory location in which the shared
devices are to be created.
7. In Browse or Manual, select which option you will use to specify the pathnames of the
devices:
l
Browse Storage Node or network path. The next wizard step will prompt you to
browse and add the devices.
l
Manually enter local or remote device paths. Select this to skip the browse step
and manually type unique names for the devices you want to add:
n
For remote devices, type the device paths relative to the Network Path that you
specified for the storage directory. For example:
cifsaftd-1
cifsaftd-2
n
For local devices, type the absolute paths to these devices. For example:
C:\cifsaftd-1
C:\cifsaftd-2
Multiple devices for a single volume configuration on page 115 provides
details for shared volumes.
8. If the storage host is remote from the storage node, in the Authentication area, type
the appropriate Username and Password to access the storage directory.
9. Click Next.
10. If you selected the Browse option in the previous window:
a. In the Select the Device Path window, verify that the storage node shows the path
of a storage directory.
b. Add devices to the storage directory by clicking New Folder and typing unique
device names. For example:
cifsaftd-1
cifsaftd-2
c. Select the new devices to add and click Next.
11. In the Configure Device Attributes window, specify the attributes. If you added
multiple devices in the previous window, select each device individually and specify
its attributes:
a. In NetWorker Device Name, type a unique name for the AFTD device.
For example, for a device on the NetWorker server host storage node:
aftd-1
If you configure the device on a storage node host that is not the NetWorker server
host, it is a “remote device” and this attribute must be specified with rd= and a
colon (:) in the following format (for Microsoft Windows):
Advanced file type devices
109
Backup Storage
rd=remote_storagenode_hostname:device_name
For example:
rd=dzone1_storhost2:aftd-1
b. (Optional) Add a comment in the Comment field.
c. If Client Direct backup will be used, follow the details in Considerations for Client
Direct clients on page 101.
d. In Target Sessions specify the number of sessions that a nsrmmd data mover
process on the device will handle before another device on the host will take the
additional sessions. Use this setting to balance the sessions among nsrmmd
processes.
If another device is not available, then another nsrmmd process on the same
device will take the additional sessions.
Typically, set this attribute to a low value. The default value is 4 for AFTDs. It may
not be set to a value greater than 60.
e. In Max Sessions specify the maximum number sessions the device may handle. If
no additional devices are available on the host, then another available storage
host takes the additional sessions, or retries are tried until sessions become
available.
The default value is 32 for AFTDs, which typically provides best performance. It
cannot be set to a value greater than 60.
Note
The Max Sessions setting does not apply to concurrent recover sessions.
f. Click Next.
12. In the Label and Mount device window, if you select the Label and Mount option,
specify the attributes for:
l
Pool Type.
l
Pool to use.
13. In the Review the Device Configuration window, review the settings and click
Configure.
14. In the Check results window:
a. Review whether the devices were successfully completed or any messages.
b. Click Finish.
c. To go back, click Back to the appropriate wizard step.
Creating an AFTD by using the Properties window (Linux and UNIX)
Procedure
1. Create one directory for each disk (or partition) to be used for an AFTD.
AFTDs require a directory (folder) to be created in the disk file system that the
NetWorker server or storage node recognizes as the device name (and the destination
for the data).
NOTICE
Do not use a temporary directory for AFTDs. The data could be overwritten.
110
EMC NetWorker 9.0.x Administration Guide
Backup Storage
2. In the NetWorker Administration window, click the Devices view.
3. Verify that the path to the storage directory that will contain the AFTDs is allowed.
a. In the navigation tree, select Storage Nodes.
b. Right-click the storage node that you will use, and select Properties.
c. In the AFTD allowed directories list, verify or type the path of the storage directory
that will contain the AFTDs.
AFTDs can be created and accessed only by these listed paths. If this list is left
empty, there are few restrictions as to where a device path can be created.
d. Click OK.
4. In the navigation tree, right-click Devices and select New.
The Create Device window opens, with the General tab selected. The Identity area
might show a default device name in the Name field.
5. In the Identity area, set the following attributes:
a. In the Name attribute, type the name of the directory that you created for the AFTD.
For example:
aftd-1
If you configure the device on a separate storage node host that is not the
NetWorker server host, it is a remote device and this Name attribute must be
specified with rd= in the following format:
rd=remote_snode_hostname:device_name
For example:
rd=snode-1:aftd-1
b. (Optional) Add a comment in the Comment field.
c. In the Device Access Information attribute, provide complete paths to the device
directory. You can provide alternate paths for the storage node and for Client Direct
clients, for example:
For non-root or cross-platform Client Direct access:
For non-root or cross-platform Client Direct access to an AFTD, do not specify an
automounter path or a mounted path. Instead, specify the path in the host:/path
format, even if the AFTD is local to the storage node.
For example:
NFS_host:/path
where:
l
NFS_host is the hostname of the NFS file server
l
path is the NFS-mountable path that is exported by the file server
This format is required to allow Client Direct access for Windows or non-root
UNIX clients.
Advanced file type devices
111
Backup Storage
Note
Non-root Client Direct access to an NFS AFTD is supported only with the NFSv3
protocol and AUTH_SYS authentication on the NFS host. For Client Direct access
to an AFTD when the backup client is able to run as root on the AFTD host,
provide a mount point or automounter path.
Note
For example, for an NFS-mounted device:
/mnt/aftd-1
/net/storho-1/snode-1/aftd-1
where:
n
aftd-1 is the storage device directory name
n
storho-1 is the storage system hostname
n
snode-1 is the storage node hostname
The first path enables the storage node to access the device via its defined
mount point. The second path enables Client Direct clients to use the
automounter path to directly access the device, bypassing the storage
node.
d. In the Media Type field, select adv_file, for the AFTD.
Considerations for Client Direct clients on page 101 provides additional details for
Client Direct configurations.
Multiple devices for a single volume configuration on page 115 provides
additional details for shared volumes.
6. In the Status area, ensure that the Auto Media Management tape feature is not
enabled.
7. In the Cleaning area, leave the options for cleaning at their default (disabled) settings,
so that automatic cleaning is not invoked.
8. Select the Configuration tab.
9. In the Save Sessions area, set the number of concurrent save sessions (streams) and
the number of nsrmmd (data mover) processes the device may handle:
l
Target Sessions is the number of sessions that a nsrmmd process on the device
will handle before another device on the host will take the additional sessions.
Use this setting to balance the sessions among nsrmmd processes.
If another device is not available, then another nsrmmd process on the same
device will take the additional sessions.
Typically, set this attribute to a low value. The default values are 4 for AFTDs and 6
for DD Boost devices. It may not be set to a value greater than 60.
Multiple devices for a single volume configuration on page 115 provides details
on volume sharing.
l
112
Max Sessions is the maximum number sessions the device may handle. If no
additional devices are available on the host, then another available storage host
takes the additional sessions, or retries are attempted until sessions become
available.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
The default values are 32 for AFTDs and 60 for DD Boost devices, which typically
provides best performance. It cannot be set to a value greater than 60.
The Max Sessions setting does not apply to concurrent recover sessions.
l
Max nsrmmd count limits the number of nsrmmd processes that can run on the
device. Use this setting to balance the nsrmmd load among devices. The default
value is 4.
To modify this value, first adjust the sessions attributes, apply, and monitor the
effects, then update max nsrmmd count.
At least one nsrmmd process is reserved for restore or clone operations.
10. In the Local Backup area, leave Dedicated Storage Node at No (the default).
11. In the Remote Host area, if an NFS path is specified in the Device Access Information,
then type a Remote User name and Password.
The remote username is the name of the user on the NFS server. It is recommended
that you also specify the numeric user id (UID) of that user. Do this by appending a
colon (:) and the UID after the username, for example, user_name:4242.
Note
If the device username is changed after labeling, manual action may be required to
change the owner of all files and directories in the AFTD. NetWorker will try to perform
this automatically during the next operation, however the ability to do so depends on
the security configuration of the file server where the AFTD storage resides.
12. Click OK when the configuration is complete.
13. If a new password for an AFTD is provided, unmount and re-mount the device to
ensure that the change takes effect.
Creating an AFTD by using the Properties window (Windows)
You can configure an AFTD on a storage node running Microsoft Windows.
Procedure
1. Create one directory for each disk (or partition) to be used for an AFTD.
AFTDs require a directory (folder) to be created in the disk file system that the
NetWorker server or storage node recognizes as the device name (and the destination
for the data).
NOTICE
Do not use a temporary directory for AFTDs. The data could be overwritten.
2. In the NetWorker Administration window, click the Devices view.
3. Verify that the path to the storage directory that will contain the AFTDs is allowed.
a. In the navigation tree, select Storage Nodes.
b. Right-click the storage node that you will use, and select Properties.
c. In the AFTD allowed directories list, verify or type the path of the storage directory
that will contain the AFTDs.
AFTDs can be created and accessed only by these listed paths. If this list is left
empty, there are few restrictions as to where a device path can be created.
Advanced file type devices
113
Backup Storage
d. Click OK.
4. In the navigation tree, right-click Devices and select New.
The Create Device window opens, with the General tab selected. The Identity area
might show a default device name in the Name field.
5. In the Identity area, set the following attributes:
a. In the Name attribute, type the name of the directory that you created for the AFTD.
For example:
aftd-1
If you configure the device on a separate storage node host that is not the
NetWorker server host, it is a remote device and this Name attribute must be
specified with rd= in the following format:
rd=remote_snode_hostname:device_name
For example:
rd=snode-1:aftd-1
b. (Optional) Add a comment in the Comment field.
c. In the Device Access Information attribute, provide complete paths to the device
directory. You can provide alternate paths for the storage node and for Client Direct
clients, for example:
l
For an AFTD on the storage node’s local disk, which it shares via CIFS:
E:\aftd-1
\\snode-1\aftd-1
The first path enables the storage node to access the device via its local drive.
The second path enables Client Direct clients to access the device directly,
bypassing the storage node.
l
For a CIFS-mounted AFTD, specify the complete paths of the directory that is
created by using the Universal Naming Convention (UNC), for example:
\\CIFS_host\share-point-name\path
d. In the Media Type field, select adv_file, for the AFTD.
Considerations for Client Direct clients on page 101 provides additional details for
Client Direct configurations.
Multiple devices for a single volume configuration on page 115 provides
additional details for shared volumes.
6. In the Status area, ensure that the Auto Media Management tape feature is not
enabled.
7. In the Cleaning area, leave the options for cleaning at their default (disabled) settings,
so that automatic cleaning is not invoked.
8. Select the Configuration tab.
9. In the Save Sessions area, set the number of concurrent save sessions (streams) and
the number of nsrmmd (data mover) processes the device may handle:
l
114
Target Sessions is the number of sessions that a nsrmmd process on the device
will handle before another device on the host will take the additional sessions.
Use this setting to balance the sessions among nsrmmd processes.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
If another device is not available, then another nsrmmd process on the same
device will take the additional sessions.
Typically, set this attribute to a low value. The default values are 4 for AFTDs and 6
for DD Boost devices. It may not be set to a value greater than 60.
Multiple devices for a single volume configuration on page 115 provides details
on volume sharing.
l
Max Sessions is the maximum number sessions the device may handle. If no
additional devices are available on the host, then another available storage host
takes the additional sessions, or retries are attempted until sessions become
available.
The default values are 32 for AFTDs and 60 for DD Boost devices, which typically
provides best performance. It cannot be set to a value greater than 60.
The Max Sessions setting does not apply to concurrent recover sessions.
l
Max nsrmmd count limits the number of nsrmmd processes that can run on the
device. Use this setting to balance the nsrmmd load among devices. The default
value is 4.
To modify this value, first adjust the sessions attributes, apply, and monitor the
effects, then update max nsrmmd count.
At least one nsrmmd process is reserved for restore or clone operations.
10. In the Local Backup area, leave Dedicated Storage Node at No (the default).
11. In the Remote Host area, if a network path is specified in the Device Access
Information, then type a Remote User name and Password.
12. Click OK when the configuration is complete.
13. If a new password for an AFTD is provided, unmount and re-mount the device to
ensure that the change takes effect.
AFTD device target and max sessions
The default settings for AFTD target sessions and max device sessions typically provide
optimal values for AFTD performance:
l
Device target sessions is 1
l
Device max sessions is 32 to avoid disk thrashing
If required, both device target, and max session attributes can be modified to reflect
values appropriate for the environment.
Note
The Max Sessions setting does not apply to concurrent recover sessions.
Multiple devices for a single volume configuration
In some environments, a configuration of multiple devices that share a single NetWorker
storage volume can result in performance gains. For example, a read or write request can
be sent to the storage node that is closest to the requestor. However, for some use cases
and environments concurrent read/write operations to a single volume from many
storage nodes could result in disk thrashing that impacts performance.
Multiple devices can be created on separate storage nodes or on the same storage node.
Each device must be created separately, have a different name, and must correctly
specify the path to the storage volume location.
For example, if you create three devices, one on the NetWorker server host named
“dzone1” (that uses the server’s local storage node) and two remote devices (rd) on
Advanced file type devices
115
Backup Storage
remote storage nodes, the Name attributes for the three devices, each created
separately, might be specified by different aliases as follows:
aftd-1a
rd=dzone1-sn2:aftd-1b
rd=dzone1-sn3:aftd-1c
The Device Access Information for each of these aliases would specify a single directory
that must be specified as a valid complete path. For example, if a directory is named
“aftd-1” on the storage host named “storho1,” the path might be specified as follows:
l
If the storage node uses an automounter:
/net/storho1/dzone1/aftd-1
l
If the storage node uses an explicit system mountpoint, you might specify one of the
following paths:
n
/mnt/storho1/dzone1/aftd-1
n
/mnt/dzone1/aftd-1
n
storho1:/dzone/aftd-1
AFTD concurrent operations and device formats
The following operations can be performed concurrently on a single storage node with an
AFTD:
l
Multiple backups and multiple recover operations
l
Multiple backups and one manual clone operation
l
Multiple backups and one automatic or manual staging operation
It might be required to increase the server parallelism value to complete the concurrent
operations with an AFTD device when the number of simultaneous save sessions reaches
the maximum value for server parallelism.
For example, if server parallelism is set to 4, and there are 4 simultaneous saves going to
an AFTD, set the server parallelism to 5 to complete a concurrent clone/stage operation
from this AFTD while the four saves are in progress.
Note
Starting with NetWorker 8.0, multiple clone sessions can be run from a single AFTD or DD
Boost device if each clone is written to a dedicated tape device. However, the number of
clone sessions that can be run is limited by the value in the device’s max nsrmmd count
attribute. Create and configure an AFTD on page 108 provides more information.
Labeling and mounting an AFTD
If there are multiple volumes in the pool, you can select an available volume to associate
with the device.
Procedure
1. Right-click the AFTD storage device and select Label.
The Label dialog box appears.
2. In the Pools field, select the media pool to be used for the device.
A label for the storage device is generated and displays in the Volume Label field. The
label name is based on the label template for the selected pool.
It is recommended to use a pool dedicated to AFTD backup devices only.
116
EMC NetWorker 9.0.x Administration Guide
Backup Storage
NOTICE
If an existing volume is re-labeled, a warning is issued. The data previously stored on
the volume will be lost and this action cannot be undone. Mounting the volume
without labeling provides access to previous data.
3. Select Mount after labeling and click OK.
Insufficient AFTD disk space
When an AFTD runs out of disk space, the current backup is interrupted and the following
message displays:
Waiting for more available space on filesystem device-name
Immediately following the message, the action that is associated with the "Filesystem
Full — Recover adv_file Space" notification occurs. By default, the action for this
notification uses the nsrim command to delete expired save sets. If enough space is
cleared, the backup continues. If the recycle setting for the volume is manual, then the
expired save sets are not removed from the volume.
The AFTD deletes expired save sets depending on the retention policy and the recycle
setting. If sufficient storage space is not available after 10 minutes from when the expired
savesets begin deletion, the associated "Filesystem Full—Waiting for adv_file Space"
notification action occurs. By default, an email notification is sent to the root user on the
NetWorker server on UNIX and Linux, and a message is logged in the media log file in
NetWorker_install_path\logs on Windows.
When the notification is sent, and the message is logged in the media log file, the backup
stops until space is available for the backup to continue. You can create customized
notifications to change and expand how the NetWorker software behaves when an "AFTD
Filesystem Full" notification occurs. Custom notifications can also run custom scripts and
other programs to expand the capacity of existing AFTDs.
The chapter "Reporting NetWorker Datazone Activities" provides more information about
how to configure notifications.
Creating a custom notification to extend disk space
While the NetWorker default Filesystem Full — Recover adv_file Space notification works by
removing its expired save sets, a custom notification could be configured to expand disk
or file system space in other ways.
Procedure
1. In the server’s Administration interface, click Server.
2. Right-click Notifications and select New.
3. For Name, type a unique name for this custom notification, such as First adv_full
notice.
4. For Event, clear all choices except adv_file.
5. For Priority, clear all choices except Waiting.
6. For Action, specify the full path of the custom script that is configured to expand
diskspace, for example: /mybin/my_first_custom_script.
7. Click OK.
Creating a custom notification for insufficient disk space
The NetWorker default Filesystem Full — Waiting for adv_file Space notification works by
sending an email notification. A custom notification could be configured to do whatever
Advanced file type devices
117
Backup Storage
the user indicates. The wait time after the default notification is approximately 10
minutes.
Procedure
1. In the server’s Administration interface, click Server.
2. Right-click Notifications and select New.
3. For Name, type a unique name for this second custom notification, such as Second
adv_full Notice.
4. For Event, clear all choices except adv_file.
5. For Priority, clear all choices except Critical, Emergency, and Alert.
6. For Action, specify the full path of the custom script to be run, for example: /mybin/
my_second_custom_script.
7. Click OK.
AFTD load balancing
You can adjust the target and max sessions attributes per device to balance the data load
for simultaneous sessions more evenly across available devices. These parameters
specify the maximum number of save sessions to be established before the NetWorker
server attempts to assign save sessions to another device.
For AFTDs, all volumes, depending on the selection criteria (pool settings), choose the
AFTD with the least amount of data written to it, and join sessions based on the device's
target and max sessions. If the number of sessions being written to the first device
exceeds the target sessions setting, another AFTD is considered for new backup sessions
and is selected from the remaining suitable AFTDs. The AFTD that is selected will be the
AFTD with the least amount of NetWorker data written to it. The least amount of data
written is calculated in bytes (not by percentage of disk space used) and only bytes that
were written by NetWorker are counted.
To ensure that a new session always writes to the AFTD with the least amount of data
written to it, you can set each AFTD device's max sessions attribute to 1. However, setting
the max sessions attribute to 1 may not be practical. Alternatively, set the target sessions
attribute to 1. In this way, load balancing will occur on a best efforts basis.
Space management for AFTD
A configurable setting for determining at what capacity the NetWorker software should
stop writing to an AFTD spans from 1 to 100%. Setting the value to 0 or leaving the
attribute empty in the AFTD Percentage Capacity attribute is equivalent to a setting of
100%. This means that the entire capacity of the file system can be used for the AFTD
volume.
When set, the AFTD Percentage Capacity attribute is used to declare the volume full and
to calculate high/low watermarks. When the percentage capacity attribute is modified,
mount and re-mount the volume for the new settings to take effect.
The level watermark is calculated based on the percentage of restricted capacity, not on
the full capacity of the file system.
In the Console Administration interface, the AFTD Percentage Capacity displays in the
Configuration tab of the Properties window of a device, when Diagnostic Mode is
enabled.
To enable Diagnostic Mode, select View > Diagnostic Mode.
118
EMC NetWorker 9.0.x Administration Guide
Backup Storage
NOTICE
If your device uses compression or deduplication, you can still use the AFTD Percentage
Capacity attribute however, the device will be marked as having reached its threshold
prematurely. In this case, there will be more unused space on the disk than expected.
This is because the threshold limit is based on the amount of data being protected
without accounting for the effect of compression or deduplication.
AFTD operation verification
The AFTD can be deployed in varying environments with local disks, and with NFSmounted or CIFS-mapped disks. The configuration of this feature affects its operation.
Ensure that the AFTD is fully operational in the production environment before deploying
it as part of regularly scheduled operations.
As part of the validation process, test these operations:
l
Backup
l
Recover
l
Staging
l
Cloning
l
Maximum file size compatibility between the operating system and a disk device
l
Use of a volume manager to increase the file system size while the file system is in
use
l
File system behavior when the disk is full
Some versions of NFS and CIFS drop data when a file system becomes full. Be sure to use
versions of NFS, CIFS, and operating systems that fully support full file systems. On some
disk devices, the volume labeling process can take longer than expected. Labeling time
depends on the type of disk device used and does not indicate a limitation of the
NetWorker software. The upper limits of save set size depend on either the upper limits
supported by the operating system or the file size specified by the disk device’s vendor.
NOTICE
Do not edit device files and directories. This can cause unpredictable behavior and make
it impossible to recover data.
Deactivate and erase an AFTD
You can deactivate an AFTD device so it does not interfere with normal backup
operations.
Converting a device to read-only
Conversion of a device to read-only prevents the use of the device for backup operations.
The device can still be used for read operations, such as restore and clone.
Procedure
1. In the NMC window for the NetWorker server, click the Devices view and select the
Devices folder in the navigation tree.
2. In the Devices table, right-click the device to be converted to read-only, and select
Unmount.
3. Right-click this unmounted device and select Properties.
4. In the Device Properties window, select Read only, and click OK.
Advanced file type devices
119
Backup Storage
5. Right-click the device and select Mount.
Disabling a device
Disabling a device prevents further operation of the device. The device may be re-enabled
to restore old data, which is retained but not active.
Procedure
1. In the NMC window for your NetWorker server, click the Devices view and select the
Devices folder in the navigation tree.
2. In the Devices table, right-click the device to be disabled and select Unmount.
3. Right-click this unmounted device and select Enable/Disable to disable.
4. Inspect the Enabled column of the table to verify that the device is disabled.
Deleting a device
The procedure for deleting a device includes an option for also erasing the volume
(access path) that stores the device’s data. The volume can be erased only if no other
device in the system shares the volume.
Procedure
1. In the NetWorker server Device view, click Devices in the navigation tree.
2. In the Devices table, right-click the device to be removed and select Delete.
A confirmation window appears.
3. In the confirmation window:
l
To delete the device from the NetWorker configuration only, without erasing the
device’s data, click Yes.
l
To delete the device and erase the device’s data and volume access path, select
the Permanently erase all data and remove media and index information for any
selected AFTDs or Data Domain devices option, and click Yes.
Note
If the volume that you want to erase is shared by another device, then an error
message displays the name of the other device. You must delete all other devices
that share the volume until the last one remaining before you can erase the
volume.
4. If the device is mounted or the device is a member of a pool, then a second
confirmation window displays the details of the device and pool. To confirm the
device unmount, the removal of the device from the pool, and the deletion of the
device, click Yes.
Concurrent AFTD recovery operation limitations
AFTD concurrent recovery currently has the following limitations:
120
l
Not available to the Windows recover interface (winworkr). Use the recover command.
The EMC NetWorker Command Reference Guide or the recover man page provides more
information.
l
Not available to nonfile recoveries, such as NDMP and NetWorker database modules.
l
Perform concurrent recoveries from the command line by using the recover command,
either by using multiple -S options to identify multiple save sets, or running multiple
recover commands concurrently.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
When you recover data from an AFTD, NetWorker recovers the save sets concurrently. You
can recover multiple save sets to multiple clients simultaneously and you can clone save
sets from an AFTD to two different volumes simultaneously.
Changing the AFTD block size
The maximum potential block size for backups to an AFTD device can be adjusted. Larger
block sizes for backups can improve backup speed under certain conditions. This is
especially noticeable on remote AFTD devices that are not local to the storage node, for
example, AFTDs that are connected with CIFS or NFS.
Changes to the maximum potential block size value for an AFTD device take effect only
after the AFTD device is labelled. The minimum allowable block size is 128 kilobytes and
the maximum block size is 256 kilobytes.
If you have an AFTD device that is performing backups slowly, try marking the device as
read-only and create a new AFTD device with a block size between 128-256 kilobytes.
NOTICE
Changing the block size and re-labeling an existing AFTD has the potential to destroy data
if the data is not staged to another location.
Procedure
1. In the server’s Administration interface, click Devices.
2. Select View > Diagnostic Mode.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Double-click the device in the devices table and select the Advanced tab.
5. In the Device block size attribute, select a value from 128 to 256.
6. Click OK.
7. Relabel the AFTD device for the new setting take effect.
DD Boost devices
DD Boost devices are covered separately in the EMC NetWorker Data Domain Boost
Integration Guide
Creating a DD Boost device
Procedure
1. In NMC, click Devices.
2. In the left panel, right-click Devices and select New Device Wizard.
3. On the Select the Device page, select Data Domain and click Next.
4. On the Data Domain Preconfiguration Checklist page, click Next.
5. On the Specify the Data Domain Configuration Options page:
a. Under Data Domain System Name:
l
Select Create a New Data Domain System.
l
In the text box, type the IP address of the Data Domain system.
b. In the Data Domain DDBoost Username field, type the username of the Data
Domain user.
DD Boost devices
121
Backup Storage
c. In the Data Domain DDBoost Password field, type the password of the Data
Domain user.
d. Specify the required values in the other fields.
e. Click Next.
6. On the Select the Folder to Use as Devices page:
a. Click New Folder to create a folder for the device.
b. Select the newly created folder.
c. Specify the required values in the other fields.
d. Click Next.
7. On the Configure Pool Information page:
a. Under Pool Type, select one of the following pool types:
l
Backup
l
Backup Clone
b. Under Pool, perform one of the following tasks to select the pool:
l
Select Create and use a new pool, and type the pool number in the text box.
l
Select Use an existing pool, and select the pool from the drop-down list box.
c. Specify the required values in the other fields.
d. Click Next.
8. On the Select Storage Nodes and Fibre Channel Options page:
a. Select the storage node.
b. Specify the required values in the other fields.
c. Click Next.
9. On the Select SNMP Monitoring Options page, specify the required field values, and
click Next.
10. On the Review the Device Configuration Settings page, review the configuration
settings, and click Configure.
11. On the Device Configuration Results page, click Finish.
CloudBoost devices
This section describes how to configure NetWorker 9.0.1 and later to perform backup,
staging, cloning, and recovery operations to a CloudBoost 2.1 appliance. Cloud-based
data protection occurs over a TCP/IP network. You can compress and encrypt the data.
CloudBoost requirements and considerations
Before you can use the CloudBoost 2.1 Appliance to protect your data in a NetWorker
data zone, you must deploy a CloudBoost 2.1 appliance in your environment. The
NetWorker Integration Guide for CloudBoost provides more information.
To use Client Direct, the feature is only supported on 64-bit Linux NetWorker clients and
requires the following Linux package requirements:
l
122
libc 2.5 or later
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
libstdc++ 6.0.8 or later (GLIBCXX_3.4.8)
You cannot recover Block Based Backup (BBB) or NetWorker Module for Microsoft (NMM)
backup data from a CloudBoost device. To recover this data, clone the data from the
CloudBoost device to a AFTD or Data Domain device, and then recover the data from the
clone device.
CloudBoost appliance requirements
Before you deploy the CloudBoost appliance, review the following minimum and
recommended configuration requirements.
Table 28 CloudBoost appliance system requirements
Configuration
Option
Recommendations Additional information
Memory
16 GB
n/a
CPU Cores
8-16
EMC recommends 16 cores when you enable site
caching.
Hard Disk 1
41 GB
This disk contains the System and Operating
System information. The deployment process
creates the disk.
Hard Disk 2
750 GB
This disk contains the metadata. The deployment
process creates this disk with a size of 41 GB.
You must manually increase the size of the disk.
Hard Disk 3
200 GB
This disk contains the site cache. The deployment
process creates this disk. You must manually
increase the size of this disk.
Cloud best practices
Consider the topics and recommendations in this section before implementing cloud
backups.
Backups to a cloud storage device
You send backups to a cloud storage device by using media pools, in the same way you
would direct any other client backup to a device or set of devices. However, be aware of
the following recommendations:
l
Set up one or more media pools for CloudBoost devices and provide the pool with a
unique label template.
l
Do not mix CloudBoost backup devices with other types of backup devices in a media
pool.
Concurrent backup and recovery operations
You can mount a single CloudBoost appliance as multiple cloud storage devices to
support concurrent backup and recovery operations.
For example, to optimize performance you can mount the CloudBoost appliance on three
cloud storage devices: one for backup (device CL1), one for recovery (device CL2), and
one for clone operations (device CL3). There is no limit to the number of cloud storage
devices that can be mounted on a single cloud volume. Consider such an approach to
optimize backup and recovery performance.
CloudBoost devices
123
Backup Storage
Network dependencies
Cloud backups are highly dependent on the network connection that is used to access
the cloud service. Any disruption in connectivity or a slowdown in network access speed
may adversely affect cloud backups or recoveries.
Proper name resolution and internet access is required for the CloudBoost appliance. The
CloudBoost appliance documentation provides more information.
Roadmap for deploying and configuring the CloudBoost appliance
CloudBoost can be deployed as a virtual appliance, a physical appliance, and as a virtual
instance in Amazon EC2. Before you can use NetWorker to protect data in the cloud, you
must perform the following steps to configure the cloud environment.
1. Deploy the CloudBoost appliance. The EMC CloudBoost Installation Guide describes
how to deploy the appliance.
2. Register the appliance and validate the credentials. The EMC CloudBoost
Administration Guide describes how to register the appliance and validate the
credentials.
3. Create a cloud profile and configure the CloudBoost appliance on the EMC Cloud
Portal. The EMC CloudBoost Administration Guide describes how to create the profile
and configure the appliance.
4. Create a device for the CloudBoost appliance in NetWorker.
Creating a device for the CloudBoost appliance in NetWorker
Perform the following steps to configure a device to receive backup or clone data.
Procedure
1. Enable remote client mounting on the CloudBoost appliance, and define a password
for the remotebackup user account:
a. Connect to the CloudBoost appliance with the admin account.
b. Type the following command:
remote-mount-password enable password
where password is the new password for the remotebackup user.
2. Log in to the NMC GUI as an administrator of the NetWorker server.
3.
Click the Enterprise button
on the taskbar.
4. Highlight a host in the navigation tree, right-click NetWorker and select Launch
Application. The NetWorker Administration window appears.
5.
Click the Devices button
on the taskbar.
6. In the expanded left navigation pane, right-click CloudBoost Appliances and select
New Device Wizard.
7. On the Select the Device Type window, select CloudBoost, and then click Next.
8. Review the CloudBoost Preconfiguration Checklist window, and then click Next.
9. On the CloudBoost Configuration Options window, perform the following tasks:
a. In the CloudBoost appliance group box, select one of the following options:
l
124
Use an existing CloudBoost appliance—Select this option to use a CloudBoost
appliance that you have previously configured on the NetWorker server.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
Create a new CloudBoost appliance—Select this option to create a new
CloudBoost appliance. Specify a descriptive name in the field.
b. In Hostname (FQDN) field, specify the Fully Qualified Domain Name (FQDN) of the
CloudBoost appliance.
c. In the Username field, type remotebackup.
d. In the Password field, type the password for the remotebackup account, which you
defined on the CloudBoost appliance by using the remote-mount command.
e. In the Configuration Method group box, select one of the following options:
l
Browse & Select—Select this option to browse the file system on the
CloudBoost appliance and select the folder that NetWorker will use as the
target data device. When you select this option, NetWorker validates the
CloudBoost username and password that you specified.
l
Manual—Select this option to manually specify a folder in the /mnt/magfs
directory on the CloudBoost appliance that NetWorker will use as the target
data device. When you select this option, NetWorker will not validate the
CloudBoost username and password that you specified.
10. Click Next.
11. Create the NetWorker device on the CloudBoost appliance.
l
If you selected Manual in the Configuration Method box on the CloudBoost
Configuration Options window, then the Manually Specify the CloudBoost Device
Path window appears. Specify a path on the /mnt/magfs file system on which to
create the NetWorker device or use the New Folder option to create a new device
folder.
Note
The storage path that you specify must exist in the /mnt/magfs directory with
write access enabled.
l
If you selected Browse & Select in the Configuration Method box on the
CloudBoost Configuration Options window, then the Browse and Select the
CloudBoost Device Path window appears. Select or create a path on the /mnt/
magfs file system on which to create the NetWorker device or use the New Folder
option to create a new device folder.
NetWorker updates the NetWorker Device Name and Storage Path fields with the
appropriate information.
12. Click Next.
13. On the CloudBoost Pool Configuration window, perform the following steps:
a. Leave the Configure Media Pools for devices option enabled.
b. In the Devices table, select the NetWorker device for the CloudBoost Appliance.
c. In the Pool Type box, select Backup or Backup Clone.
d. In the Pool box, select Create and use a new Pool, then specify a pool name, or
select Use an existing Pool and select a pool that contains at least one CloudBoost
device.
CloudBoost devices
125
Backup Storage
Note
The pool that you select cannot contain other device types such as AFTD and DD
Boost devices.
e. Leave the Label and Mount device after creation option enabled.
14. Click Next.
15. In the Review the Device Configuration window, review the settings and click
Configure.
16. In the Check results window:
a. Review whether the devices were successfully completed or any messages.
b. Click Finish.
c. To go back, click Back to the appropriate wizard step.
Troubleshooting CloudBoost device configuration issues
This section provides information about the error messages that might appear when you
configure a NetWorker device for the CloudBoost appliance.
Cannot retrieve the version of the CloudBoost appliance
This error message appears when the NetWorker server cannot determine the version of
NetWorker running on the CloudBoost appliance. To resolve this issue, contact EMC
Support for access to the CLI and ensure that:
l
The NetWorker daemon nsrexecd is started on the appliance. Log in to an SSH
terminal with the maginatics user account and type ps -ef | grep nsr. Confirm
that the nsrexecd process appears. If the nsrexecd daemon does not appear, type
sudo service networker start to start the nsrexecd process on the appliance.
l
Forward and reverse name resolution is correctly configured for the CloudBoost
appliance and the NetWorker server host.
The selected CloudBoost appliance is unsupported for device type "CloudBoost"
This error appears when the appliance is running a 9.0 or earlier version of the NetWorker
software.
Directory not found
This error appears when the NetWorker server cannot access the file system on the
CloudBoost appliance. To resolve this issue, ensure that the /mnt/magfs folder exists
on the CloudBoost appliance and is mounted.
Unable to connect to the CloudBoost appliance: LOGON_FAILURE error
This error appears in the following scenarios:
l
The password specified for the remotebackup user is not correct.
l
The remotebackup user does not exist on the CloudBoost appliance.
l
The user credentials that were specified for the NetWorker device are not the same
credentials that were used to register the CloudBoost appliance.
Configuring a storage node for CloudBoost data
To offload resource-intensive activities from the CloudBoost appliance when backing up
several Windows hosts, configure a Linux storage node host to manage the CloudBoost
126
EMC NetWorker 9.0.x Administration Guide
Backup Storage
backup activities. You do not require a storage node when backing up Linux hosts by
using Client Direct.
Before you begin
l
Create a NetWorker device for the CloudBoost appliance that the storage node
manages.
l
Install the NetWorker storage node, client, and extended client software on the Linux
host. It is recommended that you install the NetWorker storage node on a separate
Linux server. The EMC NetWorker Installation Guide describes how to install the
NetWorker software.
l
Create a storage node resource on the NetWorker server for the storage node host.
The EMC NetWorker Administration Guide describes how to create the storage node
resource.
Note
Do not use a storage node on the CloudBoost appliance and do not create devices on
the storage node for CloudBoost.
Procedure
1.
Click the Devices button
on the taskbar.
2. Expand Devices in the left navigation pane:
a. Right-click the CloudBoost device.
b. Select Copy.
The Create Device window appears.
3. In the Create Device window, perform the following steps:
a. In the Name field, specify the hostname of the new storage node and a new device
path in the format rd=hostname:device_path.
For example, rd=nwsn01.emc.com/ms_server_backups
b. For the Device access information field, specify the hostname of the CloudBoost
appliance, and the device path that you specified in the Name field in the format
hostname/device_path.
For example, cb01.emc.com/ms_server_backups
c. Click OK.
Note
During device creation, the NetWorker software automatically creates the device
path on the CloudBoost appliance.
4. Right-click the device and select Label.
The Label window appears.
a. Select a pool from the Pool list.
b. Click OK.
CloudBoost devices
127
Backup Storage
Report information on cloud backup
Use cloud backup information to monitor backup costs and help optimize your cloud
backups.
Cloud backup information can be obtained from the following sources:
l
Cloud backup and recover reports in NMC.
l
The mminfo command
Use the mminfo -avot command to get information on how much data is
consumed in a cloud backup. The EMC NetWorker Command Reference Guide and the
UNIX man pages provide more information about how to use the mminfo command.
Cloud storage device staging
Staging with a cloud storage device works the same way as staging to a tape device. You
cannot however, use a cloud storage device as the source for a staging operation. Staging
save sets on page 428 provides more information.
Atmos Cloud devices
This section describes how to configure the NetWorker Cloud Backup Option (NCBO) to
perform backup, staging, cloning, and recovery operations to cloud configurations.
Backups to cloud occur over a TCP/IP network and can be compressed and encrypted.
NetWorker supports EMC Atmos-based cloud storage.
Cloud backup requirements and considerations
The following conditions must be met before you can backup to the cloud.
l
The NetWorker Cloud Backup Option must be licensed and enabled. The EMC
NetWorker Licensing Guide provides information about license enablers.
l
The NetWorker Cloud Backup Option is supported on Windows and Linux storage
nodes only.
l
An Atmos cloud account is set up and you have a username and password to access
the cloud account. The EMC Atmos Installation Guide and the EMC Atmos System
Management GUI Guide provides information about setting up and managing an
Atmos account.
l
If the Atmos server and the NetWorker server are separated by a firewall, TCP ports 80
and 443 must be open to allow outgoing communication from the NetWorker server
to the Atmos server. If a proxy server is configured in the environment, a firewall
exception may also need to be created to ensure unrestricted access. If these ports
are not open, device operations will fail with the following error: Atmos label
operation failed: Failed to write cloud label: Couldn't
connect to server.
For NDMP, only a Data Server Agent (DSA) is supported for cloud backups.
Cloud best practices
Consider the topics and recommendations in this section before implementing cloud
backups.
128
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Backups to a cloud storage device
You send backups to a cloud storage device by using media pools, in the same way you
would direct any other client backup to a device or set of devices. However, be aware of
the following recommendations:
l
Set up one or more media pools for CloudBoost devices and provide the pool with a
unique label template.
l
Do not mix CloudBoost backup devices with other types of backup devices in a media
pool.
Concurrent backup and recovery operations
You can mount a single CloudBoost appliance as multiple cloud storage devices to
support concurrent backup and recovery operations.
For example, to optimize performance you can mount the CloudBoost appliance on three
cloud storage devices: one for backup (device CL1), one for recovery (device CL2), and
one for clone operations (device CL3). There is no limit to the number of cloud storage
devices that can be mounted on a single cloud volume. Consider such an approach to
optimize backup and recovery performance.
Network dependencies
Cloud backups are highly dependent on the network connection that is used to access
the cloud service. Any disruption in connectivity or a slowdown in network access speed
may adversely affect cloud backups or recoveries.
Proper name resolution and internet access is required for the CloudBoost appliance. The
CloudBoost appliance documentation provides more information.
HTTPS communications with the Cloud server
NetWorker enables you to use https to securely communicate with the Cloud server.
Configure https communications when you configure the cloud device in NetWorker. You
will need to retrieve the SSL certificate for the Cloud server before you create a new
device or modify an existing cloud device. Use the nsrssltrust command on the
NetWorker server to retrieve the SSL certificate of the Cloud server and store the
certificate to a local file.
To retrieve the certificate file, type the following command:
nsrssltrust -c path\filename -u https_server
where:
path\filename is the location to store the certificate file on the NetWorker server.
https_server is the hostname of the https server.
For example:
nsrssltrust -c ./atmos1.cert -u https://accesspoint.atmosonline.com:
443
Atmos Cloud devices
129
Backup Storage
Create and label a cloud storage device
It is required to create and label cloud storage devices for use with the NetWorker
software.
Creating the cloud storage device
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Right-click Devices in the navigation tree, and select New. The Create Device window
appears, with the General tab selected, and a default device path in the Name field of
the Identity area of the window.
3. In the Name field, replace the default name with a name that uniquely identifies the
cloud storage device. If the device is configured on a remote storage node, indicate
that the storage node is remote, by including rd=hostname: in the name. For example,
if the remote storage node is neptune, then the device path might be
rd=neptune:cloud1.
Note
A cloud storage device name does not specify a path to the device. You can use any
combination of alphanumeric characters for the device name.
4. In the Comment field and the Description field, add an optional comment and
description, respectively.
5. In the Media Type field, select Atmos COS as the device type if you are using Atmos as
the cloud server.
6. In the Remote User field, type the username that is used to access the cloud server.
For an Atmos COS device, this is the token-id.
7. In the Password field, type the password that is used to access the cloud server. For
an Atmos device, this is the shared secret.
8. Select the Cloud tab to specify additional information specific to the cloud backup
device.
9. In the Server field, type the IP address or fully qualified domain name of the cloud
server.
10. Use the Parameter options to adjust network communication attributes:
a. In the Network Write Size field, specify the amount of backup data, in kilobytes, to
cache in memory before sending to the cloud. Larger write sizes typically result in
better performance but results vary depending on the underlying network
characteristics. Also be aware that larger sizes consume more memory on the
storage node for the duration of the backup or recover operation.
b. In the Number of Retries field, specify the number of times that NetWorker will
attempt to send backup or receive recover data in the event of a network failure.
c. In the Send/Receive Timeout field, specify the number of seconds that NetWorker
will wait for confirmation that network send and receive transmissions to the cloud
server have occurred successfully. If the timeout period expires, the data
transmission is considered to have failed.
l
130
Set the value of this field in conjunction with the Network Write Size field.
Larger Network Write Size values require larger Send/Receive Timeout values to
avoid failures. Optimal values for the Send/Receive Timeout field vary
depending on the network speed and bandwidth.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
The save group’s Inactivity Timeout value can potentially interact with the
Send/Receive Timeout value in unintended ways. To avoid this possibility,
ensure that the save group’s Inactivity Timeout value (default is 30 minutes) is
greater than the Send/Receive Timeout value (default is 30 seconds).
d. In the Network Failure Retry Interval field, specify the number of minutes that a
backup or recover session must wait before a failed network connection results in
an aborted backup or recover session.
11. In the Compression field, select a compression level for data that is sent to the cloud.
Faster compression speeds result in less data compression but also require less CPU
resources. The fastest compression speed, Compression Speed Fast, performs the
least amount of data compression and is selected by default.
To choose an optimal compression value, balance the potentially longer backup
window of using a slower compression speed against the potential efficiency and cost
savings of sending less backup data to the cloud.
NOTICE
If the NetWorker Cloud Back Option determines that backup data cannot be
compressed effectively, compression may not occur regardless of the setting in this
field.
12. In the Encryption field, specify whether to enable or disable encryption of data sent to
the cloud. Encryption is standard NetWorker AES 256 bit encryption and is selected by
default. If desired a NetWorker datazone pass phrase can be defined that would be
used to recover encrypted data.
If this option is selected, encryption will occur regardless of any client-side encryption
directives. The EMC NetWorker Security Configuration Guide provides more information
about encryption including how to specify a new datazone pass phrase.
NOTICE
If encryption is already enabled for the NetWorker client and encryption is enabled in
this field, backups will be slower because encryption functions will occur twice.
13. Use the Cloud network interface field if the Storage node has multiple network
interfaces. If it does, specify the IP address of the network interface that will send
backup data to the cloud.
To display the Cloud network interface field, select View > Diagnostic Mode from the
menu bar.
14.
Select Throttling and then click the Bandwidth icon
to display a dialog box where
you can adjust the maximum internet bandwidth that a cloud backup or recovery
operation can consume at any given time of the day or week. This option enables you
to prevent network congestion by limiting cloud backup and recovery activity during
peak internet usage.
a. Select New to add a bandwidth throttling policy.
b. From the Day field, select the day of week to which the policy applies.
c. Click the up and down arrows to select a time of the day to which the policy starts
and ends. Alternatively, type the times directly into the Start time and End time
fields.
Atmos Cloud devices
131
Backup Storage
d. Click the up and down arrows to select the maximum possible network bandwidth.
in megabits per second, that a backup or recovery operation can consume when
the policy is in effect. Alternatively, type the values directly in the fields.
You can create as many policies per day as required. You can also modify or delete
existing throttling policies as necessary.
15. Click OK when the configuration is complete.
Labeling and mounting the cloud storage device
If there are multiple cloud volumes, you will be able to select the volume to associate
with the cloud storage device.
Procedure
1. Select the cloud storage device, right-click and select Label. The Create new cloud
volume dialog box appears.
2. In the Pools field, select the media pool to be used for cloud storage devices.
Note
It is recommended that the media pool you select be used for cloud backup devices
only.
A label for the cloud storage device is generated and displayed in the Volume Label
field. The label name is based on the label template that was specified for the cloud
media pool.
3. Select Mount after labeling and click OK.
Report information on cloud backup
Use cloud backup information to monitor backup costs and help optimize your cloud
backups.
Cloud backup information can be obtained from the following sources:
l
Cloud backup and recover reports in NMC.
l
The mminfo command
Use the mminfo -avot command to get information on how much data is
consumed in a cloud backup. The EMC NetWorker Command Reference Guide and the
UNIX man pages provide more information about how to use the mminfo command.
Cloud storage device staging
Staging with a cloud storage device works the same way as staging to a tape device. You
cannot however, use a cloud storage device as the source for a staging operation. Staging
save sets on page 428 provides more information.
Cloud storage device cloning
Cloning with a cloud storage device works the same way as cloning with any other
advanced file type device.
132
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Libraries and silos
NetWorker supports SCSI libraries, NDMP libraries, and ACSLS silos. In a fibre channel
environment you can configure library and device sharing between storage node hosts.
Overview of tape device storage
This chapter contains information on the creation, configuration, and management of
tape devices. Tape devices may be configured as stand-alone devices or configured as
part of a traditional tape library or virtual tape library (VTL) storage system.
The libraries and devices available to a NetWorker server are listed in the Devices view of
the NetWorker Administrator window. The details and settings of a particular device can
be viewed by right-clicking the device and selecting Properties. The full range of property
attributes can be viewed by selecting View > Diagnostic Mode. A description of the
various attributes is provided by the Field Help button.
As with other Console functions, you can view and work with only those NetWorker
servers for which you have access permission.
NetWorker software supports many different types of tape libraries, also called
autochangers or jukeboxes. The general categories of libraries are SCSI, NDMP, and silo.
Support for LTO-4 hardware-based encryption
The use of LTO-4 hardware-based encryption is supported by NetWorker when controlled
by management utilities that are provided with the LTO-4 hardware, or by third-party key
management software. EMC does not test or certify these key management utilities;
however, the NetWorker application can read from and write to LTO-4 devices that use
hardware-based encryption. The use of this encryption is transparent to NetWorker.
Neither the encryption nor the key management process is managed by the NetWorker
application. This includes the ability to turn encryption on or off within NetWorker, and
the management of encryption keys.
Linux device considerations
Review this section for information about using devices on Linux hosts.
Configure Linux operating system to detect SCSI devices
Proper configuration of the SCSI subsystem is required to get full use of SCSI devices and
allow the operating system to detect SCSI devices that are attached to the computer. If
the device is configured with multiple LUNs, set the kernel parameter Probe all LUNs
of each SCSI Device to Yes.
The Linux Documentation Project website provides more information on configuring the
Linux SCSI subsystem. For information on the SCSI device, contact the manufacturer.
The inquire command and the Scan for Devices operation do not detect more than 128 tape
devices
By default, the Linux st kernel module only configures up to 128 SCSI tape devices
(/dev/nst).
When the number of SCSI tape devices exceeds the kernel value ST_MAX_TAPES, the
following error may appear in the /var/log/messages operating system log file:
Libraries and silos
133
Backup Storage
st:Too many tape devices (max. 128)
The inquire command or the Scan for Devices option in NMC only displays the
maximum number of st devices (/dev/nst) defined by the ST_MAX_TAPES value.
To resolve this issue, edit and recompile the st module of the Linux kernel to increase the
maximum number of allowable st devices that are created by the OS to exceed the
default value. The Linux documentation provides details on how to reconfigure, rebuild,
and install the kernel.
Configuration requirements for the inquire command
Depending on the specific OS requirements and the configuration of the NetWorker server
or storage node, you may need to create device files so that the inquire command can
detect all devices.
For example, on a NetWorker server with Red Hat Linux, if devices sg0 through sg15
exist, create device file sg16 by using the mknod program as follows:
mknod /dev/sg16 c 21 17
The operating system vendor documentation provides more information on creating
devices.
Solaris device considerations
Review this section for information about using devices on Solaris hosts.
Support for tape devices not supported by Solaris
If Sun Microsystems does not directly support a device for use with the operating system
on the storage node, obtain a st.conf file from the device manufacturer.
The inquire command and Solaris 10
On Solaris 10, the inquire command does not show library information after you
configure the library for NetWorker.
HP-UX device considerations
Review this section for information about using devices on HP-UX hosts.
Autochanger installation on an HP-UX system
The following sections explain how to install and configure Hewlett-Packard drivers.
Selecting SCSI addresses for the autochanger
Determine which SCSI address is assigned to each SCSI bus, and select the SCSI
addresses to be allocated to the autochanger drives and controller.
To select unused SCSI addresses for an autochanger, log in as root on the NetWorker
server or storage node, and type the ioscan -f command.
Use a SCSI address within the range of 0 to 6. The primary hard disk is usually on SCSI
address 6.
134
EMC NetWorker 9.0.x Administration Guide
Backup Storage
NOTICE
For some devices, such as the HP Model 48AL autochanger, select one SCSI address for
the entire autochanger. The 48AL uses a different SCSI logical unit number (LUN) for the
device (LUN 0) and robotics (LUN 1). The SCSI LUN appears as the last digit of the H/W
Path field in the ioscan output.
Installing the SCSI pass-through driver
The following procedure describes how to use SAM terminal mode to install a GSC, HSC,
or PCI pass-through driver.
Procedure
1. Select Kernel Config and press Enter.
2. Select Drivers and press Enter.
3. Select the SCSI_ctl driver by selecting SCTL from the list.
If the current state is in, go to step 9. Otherwise, select any unreserved name for the
device. For example, do not select a name such as /dev/null.
4. From the Actions menu, select Add Drivers to Kernel, and press Enter.
5. From the Actions menu, select Create a New Kernel, and press Enter.
A confirmation message appears.
6. Specify Yes, and press Enter.
The Creating Kernel message appears, followed by the Move Kernel message.
7. Select OK, and press Enter.
The system reboots.
8. Verify that the spt was successfully installed by typing the following command:
ioscan -kfn
9. Verify that the driver has claimed the autochanger.
If the autochanger has been claimed, CLAIMED should appear under the S/W State
header. If not, verify that the installation completed correctly.
10. If the device entry was defined by the operating system, use the OS-defined entry and
continue to verify the installation.
Determining the major number
To determine the value for majornum, type lsdev -d sctl.
The output should resemble the following example output, although the assigned
number may differ from the values in this example:
Table 29 Determining the major number value
Character Block Driver Class
HP-PB
75 -1 spt
spt
HSC or PCI 203 -1 sctl
ctl
The value for majornum is the number in the Character column.
HP-UX device considerations
135
Backup Storage
Determining the minor number
To determine the value for minornum, use the ioscan command.
The relevant lines in the ioscan output are those:
l
For the controller itself, which contains HP C6280-7000 in the Description
column.
l
For the adapter to which the controller is connected, which is the second line above
the line for the controller and contains ext_bus in the Class column.
If the schgr driver is configured on the system, it appears associated with the library.
The ioscan output line resembles:
Table 30 ioscan output when driver is configured
Class I H/W Path
Driver S/W State H/W Type Description
spt
0 10/4/4.6.0 schgr CLAIMED
DEVICE
HP C6280-7000
If the schgr driver is not configured on the system, no driver appears to be associated
with the library. The ioscan output line resembles:
Table 31 ioscan output when driver is not configured
Class
I H/W Path
Driver S/W State H/W Type Description
unknown -1 10/4/4.6.0 schgr UNCLAIMED DEVICE
HP C6280-7000
Testing the device driver and device file installation
After the device driver is installed and the device file is created, run the inquire
command to list available SCSI devices.
NOTICE
Use the inquire command with caution. Running inquire sends the SCSI inquiry
command to all devices detected on the SCSI bus. Using the inquire command during
normal operations may cause unforeseen errors and possible data loss may result.
An example of the output from this command (with the -s option) is as follows:
scsidev@0.1.0:HP C1194F 0.14 Autochanger
c0t1d0
scsidev@0.2.0:Quantum DLT4000 CC37 Tape,
scsidev@0.3.0:Quantum DLT4000 CC37 Tape,
scsidev@0.4.0:Quantum DLT4000 CC37 Tape,
scsidev@0.5.0:Quantum DLT4000 CC37 Tape,
(Jukebox), /dev/rac/
/dev/rmt/c0t2d0BESTnb
/dev/rmt/c0t3d0BESTnb
/dev/rmt/c0t4d0BESTnb
/dev/rmt/c0t5d0BESTnb
As of HP-UX 11iv3, two different addressing modes are supported: LEGACY and AGILE.
The inquire program lists devices using the B.T.L. notation for the LEGACY addressing
mode, for example:
scsidev@B.T.L.
For the AGILE addressing mode, it lists devices using the DSF notation, for example:
136
EMC NetWorker 9.0.x Administration Guide
Backup Storage
/dev/rtape/tape106_BESTnb
Inquire command does not detect tape drive
When a tape drive is attached to the HP-UX 11i V2 64-bit host and the inquire
command is run, the tape drive is not detected, even if the device is configured, labeled,
and mounted and a save was successful.
To work around this issue, identify the drive path in the /dev/rmt folder, and configure
the device with this path.
Whenever a new device is attached to the system, ensure that the cached file /tmp/
lgto_scsi_devlist is updated. Remove this temp file and then run the inquire
command, which rebuilds the file.
Errors from unsupported media in HP tape drives
Certain HP tape drives can only read 4-mm tapes of a specific length. Some, for example,
read only 60-meter tapes. To determine the type of tape that is supported, refer to the
drive’s hardware manual.
If unsupported media is used, the following error message may appear when you use the
nsrmm or nsrjb command to label the tape:
nsrmm: error, label write, No more processes (5)
The following error message may appear when you use the scanner -i command to
label the tape when unsupported media is used:
scanner: error, tape label read, No more processes (11)
scanning for valid records …
read: 0 bytes
read: 0 bytes
read: 0 bytes
Unloading tape drives on an HP-UX server or storage node
When the nsrjb -u -S command is used to unload a tape drive in an autochanger that
is attached to an HP-UX server or storage node, the unload operation ejects all tape
volumes inside the autochanger devices, and into their respective slots.
To unload a single drive to its corresponding slot, use the nsrjb -u -f device_name
command instead.
SCSI pass-through driver required for HP-UX autochangers
Review the required procedures in the EMC NetWorker Installation Guide before you run the
jbconfig program to configure an autochanger with a NetWorker server on HP-UX.
Follow the procedures to rebuild the kernel even if the SCSI pass-through driver is
installed. Then run the jbconfig program to configure the autochanger.
HP-UX device considerations
137
Backup Storage
AIX device considerations
Review this section for information about using devices on AIX hosts.
STK-9840 drives attached to AIX
If you attach an STK-9840 drive to an AIX server, use SMIT to modify the IBM tape drive
definition field to set the value of Use Extended File Mark to Yes.
LUS driver operation on AIX
When a library comes online, NetWorker obtains an exclusive lock on the library due to
the operation of the LUS driver on AIX. This lock is maintained if the library is enabled. As
a result, you cannot use diagnostic tools such as inquire and the sji utilities to
access the library during this time. To access the library using these tools, you must first
take the library offline.
SCSI and VTL libraries
SCSI libraries have automated robotic mechanisms to move tape media from a fixed
number of library slots to devices for read or write operations. The number of slots can
typically vary between 2 to 10,000 and the number of devices can be between 1 to 100 or
more.
Traditionally, libraries are physical units with mechanical robotics, however the same
functionality can also be provided by virtual tape libraries (VTLs) that emulate this
functionality. VTLs can also be configured and used as Autochangers.
The robotic controller and associated tape devices are always all controlled through a
SCSI interface which is available on one or more storage hosts.
Selecting a volume for the NetWorker server
When a backup takes place, the NetWorker server searches for a volume from the
appropriate pool to accept the data for backup.
The available volumes are as follows:
l
Mounted on stand-alone devices.
l
Available for labeling and accessible to the NetWorker server through Auto Media
Management or a library.
l
Labeled for the appropriate pool and already mounted in a device, or are available for
mounting, if a library is being used.
If two or more volumes from the appropriate pool are available, the server uses this
hierarchy to select a volume.
Procedure
1. Mounted volumes from the appropriate pool with the mode appendable are selected.
This includes newly labeled volumes. If more than one mounted volume is
appendable, the server uses this hierarchy:
a. Device availability. The server writes to the volume from the appropriate pool that
is mounted on the device with the fewest current sessions.
b. Volume label time. The server writes to the volume with the oldest label time if the
mounted volumes are appendable and session availability is not an issue.
138
EMC NetWorker 9.0.x Administration Guide
Backup Storage
2. If a library is in use and there is no mounted, appendable volume in the library, the
server determines whether there is an unmounted, appendable volume available. This
includes newly labeled volumes.
3. If multiple unmounted, appendable volumes are available, the volume with the oldest
label time is selected.
4. If no mounted volumes are appendable and Auto Media Management is enabled, a
mounted volume with the mode recyclable is selected. The server relabels and
mounts the volume.
5. If a stand-alone device is being used and Auto Media Management is not enabled, the
server sends a mount request notification.
6. If a library is in use and no unmounted, appendable volumes exist, the server
determines whether there is an unmounted, recyclable volume.
7. If Auto Media Management is not enabled, or if there are no appendable or recyclable
volumes, the server sends a mount request notification.
Managing volumes on page 452 provides information about appendable and
recyclable volumes.
Data recovery and volume selection
The NetWorker server determines which volumes are required for recovery. If the
appropriate volume is currently mounted, the recovery begins. If the volume is not
mounted and a library is used, the server attempts to locate and mount the volume in an
eligible device for appropriate media pool. Preference is given to mount the volume in a
read-only device, if one is available.
If a stand-alone device is used, or if the server cannot locate and mount the volume, the
server sends a mount request notification.
If more than one volume is needed to recover the data, the NetWorker server displays all
the volumes, in the order needed. During the recovery process, the server requests the
volumes, one at a time.
NOTICE
NetWorker will automatically unload volumes that have been placed in a jukebox device
but have never been mounted (for example, nsrjb -l -n <volume>). Any command, such as
the scanner command, that operates on volumes that have never been mounted will be
affected by this behavior. To prevent NetWorker from unloading the volume, the device
should be set to service mode while the command is being run.
Automatic volume relabeling
NetWorker has the ability to automatically relabel recyclable volumes when needed or
when scheduled.
When you enable Auto Media Management, the NetWorker server will automatically
relabel a volume when the mode is recyclable. A volume is automatically set to recyclable
when all save sets on the volume, including partial save sets that span other volumes,
are marked as recyclable. Auto Media Management on page 149 provides more
information on Auto Media Management.
Note
You can manually change the mode of a volume to recyclable. Changing the volume
mode on page 452 provides information about changing the mode of a volume.
You can configure a media pool to automatically relabel recyclable volume at a user
defined time and interval. Automatically relabeling volumes in a media pool on page 86
SCSI and VTL libraries
139
Backup Storage
provides more information about configuring the automatic relabel process for recyclable
volumes in a media pool.
Virtual tape library (VTL) configuration
During library configuration, the NetWorker software automatically attempts to detect if a
library is a VTL, and updates the read-only Virtual Jukebox attribute to Yes, or if not, to No.
VTLs that are mistakenly identified as autochangers can indicate what type of license
should be used, either autochanger or VTL.
VTL licensing
The EMC NetWorker Licensing Guide provides information about NetWorker licensing
support for a Virtual Tape Library.
Multiplex backups to Data Domain VTL devices
You can configure multiplexed backups to Data Domain VTL devices on remote, nondedicated NetWorker storage nodes. Multiplexing is the use of multiple parallel save
streams or concurrent sessions to each device. Each additional save stream (max
sessions value) to a VTL device reduces the number of devices needed by somewhat less
than one because deduplication efficiency decreases slightly.
The following prerequisites, restrictions, and considerations apply:
l
NetWorker dedicated storage nodes (DSNs) and NetWorker backup to local VTLs
cannot use this configuration.
l
If you are currently using DD OS 5.0.x, upgrade to DD OS 5.0.2 or later.
l
If you are currently using DD OS 4.x, upgrade to DD OS 4.9.3.1.
l
Multiplexing decreases deduplication efficiency on the VTLs by 4% to 8% per
additional save stream. For example, given a sufficiently large device block size, 4
parallel streams (max sessions=4) results in deduplication ratios that are 12%-24%
below the non-multiplexed rate (max sessions=1).
l
Deduplication ratios may be initially low when you increase max sessions due to
extra processing, following which efficiency improves.
l
Heavily used Data Domain systems, with 75% or more disk space already used, can
suffer impaired performance when used with multiplexing.
l
As a best practice, do not use client-side or server-side encryption during backup to
the Data Domain system.
Multiplex to Data Domain VTL prerequisites and considerations
Ensure the following prerequisites and practices.
140
l
If currently using DD OS 5.0.x, upgrade to DD OS 5.0.2 or later.
l
If currently using DD OS 4.x, upgrade to DD OS 4.9.3.1.
l
The recommended settings for VTL are: max sessions=4; target sessions=4; and
device block size=512 KB.
l
Best max sessions and device block size values depend on the environment. For
example, max sessions=2 might provide better stability and deduplication while still
meeting the backup window.
l
Deduplication efficiency on the VTLs is reduced by 4% to 8% per additional save
stream. For example, given a sufficiently large device block size, 4 parallel streams
(max sessions=4) results in deduplication ratios that are 12%-24% below the nonmultiplexed rate (max sessions=1).
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
Typically, deduplication ratios are initially low when you increase max sessions and
device block size due to re-priming and re-analysis overhead, following which
efficiency improves.
l
Heavily used Data Domain systems, with 75% or more disk space that is already
used, can suffer impaired performance when used with multiple sessions.
l
As a best practice, do not use client-side or server-side encryption during backup to
the Data Domain system.
Configuring multiplex backup to Data Domain VTL devices
Configure Data Domain VTL devices for multiple session backups as follows.
Procedure
1. Shut down backup service on the NetWorker VTL storage node, or shut down the
NetWorker server if that is possible, and verify that there is no backup activity on the
storage node.
2. Use NMC or the nsradmin command to set the sessions values for each VTL device.
The recommended values are: max sessions=4 (32 maximum); target sessions=4;
and device block size=512KB.
Optimal max sessions and device block size values depend on your environment. For
example, max sessions=2 might provide better stability and deduplication while still
meeting your backup window.
Note
If you shut down the NetWorker server in step 1, you can run the nsradmin
command with the -d resdir option. This option uses the NetWorker resource
database, resdir , without opening a network connection.
For example, on UNIX/Linux or Microsoft Windows systems, run the following
command:
nsradmin -i input_file.txt
where input_file.txt is a text file that contains the following lines that you can
customize to your own environment:
option regexp: on
. type: nsr device; media type: LTO Ultrium-3; media family: tape;
name: /dev/rmt*
update max sessions: 4; target sessions: 4; device block size:
512KB
3. Create a no intra-block multiplexing (nibmp) tag file in the NetWorker debug folder on
the NetWorker storage node.
For example, you can use the standard NetWorker installation paths for the tag file.
You can limit the tag file path to a specific pool by adding the _poolname variable as a
suffix to the tag file. The _poolname can include spaces, for example, _My Pool. On
Microsoft Windows systems, ensure the specified pathname is enclosed in quotes.
Unix/Linux system examples.
touch /nsr/debug/nibmp
touch /nsr/debug/nibmp_My Pool
Microsoft Windows system examples.
SCSI and VTL libraries
141
Backup Storage
echo > "NetWorker_install_path\nsr\debug\nibmp"
echo > "NetWorker_install_path\nsr\debug\nibmp_My Pool"
4. Restart the NetWorker services to enable the multiplexing functionality.
The technical note named NetWorker Improved Deduplication with Multiplexing to Data
Domain VTLs Technical Note, available on the EMC Online Support website, provides
more details.
Non-rewinding tape device usage (UNIX/Linux only)
Tape drives used as storage devices must be accessed by non-rewinding device files. The
NetWorker server assumes that a tape is in the same position in which it was the last
time it was accessed. If the operating system’s device driver rewinds the tape, then the
position is lost, and previously written data will be overwritten by the next backup.
The NetWorker configuration software automatically chooses the correct device
pathname for tape devices. If the user specifies the pathname, then it must be nonrewinding, and it must follow the Berkeley Software Distribution (BSD) semantic rules.
For example, /dev/rmt/0mbn, where:
l
The b satisfies the BSD semantics requirement on Solaris and HP-UX.
l
The n specifies non-rewinding behavior on Solaris, HP-UX, Linux, and HP-Tru64.
On AIX, the number following the decimal selects the BSD and non-rewinding behavior
and must be either 1 or 5 for NetWorker software (for example /dev/rmt2.1).
Note
Never change a device pathname from non-rewinding (/dev/rmt/0cbn) to rewinding
(/dev/rmt/0cb). When the pathname is changed to rewinding, the data could only be
saved, but never recovered. All but the last save are overwritten by later saves.
Pools with libraries
If the backup strategy includes both full and nonfull backups, estimate the number of
volumes needed for the full backups and assign them to the Full pool. This ensures that
the full backups are located in a consecutive range of slots in the library. This allows all of
the volumes to be removed at the same time.
Persistent binding and naming
Some operating systems provide the persistent binding option to permanently bind
logical and physical addressing so that the associations are retained. This guarantees
that the operating system always uses and creates the same symbolic path for a device is
known as persistent naming.
Proper configuration of the operating system to use persistent binding and persistent
naming resolves issues related to device ordering by forcing the operating system to
always assign the same device filename regardless of external events.
Persistent binding
Persistent binding guarantees that the operating system always uses the same SCSI
target ID for SAN devices, regardless of reboots or other events, by statically mapping a
target's WWN address to a desired SCSI address. On some operating systems, this is
done by default, while on others it has to be set manually. The operating system
documentation provides further information.
142
EMC NetWorker 9.0.x Administration Guide
Backup Storage
In most cases, persistent binding should also be set on the Host Bus Adapter (HBA) by
using the configuration utility that comes with the Fibre Channel HBA. The HBA device
driver documentation provides details.
Persistent binding is required for consistent library operations within NetWorker, because
the NetWorker server communicates with the library controller over a SCSI address that is
chosen during initial library configuration. If the SCSI address changes, the library will
become unavailable. In this case, disable the library and change the “control port”
address to reflect the new SCSI address of the library controller.
If devices have already been configured in NetWorker prior to enabling persistent binding
on the host, delete existing devices from the library resource and perform a re-scan of
devices followed by a reconfiguration of the tape library.
Persistent naming
Persistent naming is used to ensure that the operating system or device driver of a server
always creates and uses the same symbolic path for a device (referred to as device file).
After you create persistently named device files and they are present on the host, enable
the Use persistent names option when scanning for tape devices from the NetWorker
Management Console.
If devices have already been configured in NetWorker prior to enabling persistent naming
on the host, delete existing devices from the library resource and perform a re-scan of
devices followed by a reconfiguration of the tape library.
Whether to add or recycle volumes
The NetWorker server saves files on volumes marked appen (appendable). If the volumes
are marked full, they cannot receive backups. There are situations best suited to either
adding a new volume, or recycling an existing volume.
If volumes are marked full, you can:
l
Remove the full volumes and replace them with new media if the volumes are being
kept for long-term storage.
l
Change the volume mode to recyc (recyclable) if the data on the full volumes is not
needed. The NetWorker server overwrites the data with new backups, but maintains
the existing labels. Changing the volume mode on page 452 provides information
about changing the volume mode.
When all of the save sets on the volume have passed the time period specified by the
retention policy, the mode of the volume automatically changes to recyclable.
There are advantages both to recycling media and adding more media to a pool. With
recycling, the same volumes are used repeatedly, and there is no need to add new
volumes to the pool. The volumes can, however, wear out over time and exhibit a higher
failure rate.
On the other hand, if backups are to be stored for some time, then it might be necessary
to add more media to the pool instead of recycling. For example, a library might need new
volumes every three months if the company policy is to maintain the backups for a year.
In this case, new media must be added to the pool until the volumes that contain expired
or old backups can be recycled.
Configure libraries
A library resource must be created on a storage node for each library, including silos, that
you want to use with NetWorker. Because the NetWorker server is also a storage node,
this procedure applies to a NetWorker server and all storage nodes. You can configure a
SCSI and VTL libraries
143
Backup Storage
library either automatically with the Configure All Libraries wizard or manually with the
user interface.
Before you create devices, you must create the storage node that will manage the
devices. Storage nodes on page 91 provides details. When you create the new devices,
you can use NetWorker to perform a device scan, which searches for new devices across
multiple storage nodes.
NetWorker can only automatically create tape devices that have serial numbers. Use the
inquire or sn commands to determine if a device returns a serial number. UNIX man
page and the EMC NetWorker Command Reference Guide provides detailed information
about how to use the inquire and sn commands.
NetWorker can automatically configure the following library types:
l
SCSI
l
NDMP
l
ACSLS Silo
Use the jbconfig command to configure a library that contains tape devices or a
robotic arm that does not have serial numbers. Use the jbconfig command to
configure IBM tape libraries that are controlled through the use of the IBMs tape driver.
This is because the device autodetection code uses the internal lus driver to control
libraries.
Note
Before you create devices on a storage node, update the devices to the most recent
firmware and driver versions.
Autodetection of libraries and tape devices
Autodetection is a scanning process that applies only to physical tape libraries and
virtual tape libraries (VTLs). The NetWorker software automatically discovers libraries and
devices that are being used for backups and recoveries.
The maximum number of configured devices for any NetWorker server and storage node
combination is 512. The maximum number, including non-configured devices, can vary
depending on the specific server that is being administered.
The following options are available from many of the menus throughout the Devices task:
l
Configure all Libraries
l
Scan for Devices
If you start these options from the server folder instead of from the storage node folder,
then all storage nodes on the NetWorker server are automatically selected for
configuration in the wizard, or for scanning, respectively.
As with other Console functions, you can view and work with only those NetWorker
servers for which you have access permission.
NOTICE
Autodetection should not be used for devices on a Storage Area Network (SAN) while any
of the devices are in use, because this may cause the device in use to become
unresponsive. To avoid this situation, do not configure a device in multiple NetWorker
datazones.
144
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Adding a library resource
Procedure
1. In the server’s Administration interface, click Devices.
2. Open the Storage Nodes folder in the navigation tree.
3. Right-click the storage node to which the device is to be configured, and select
Configure All Libraries (which is available from many of the menus throughout the
Devices task). This opens a wizard that can configure all detected libraries, except
those explicitly excluded in the library exclusion list during configuration.
NOTICE
If Configure All Libraries is started from the server folder instead of from the Storage
Node folder, then all storage nodes on the NetWorker server are automatically
selected for configuration in the wizard.
The Configure All Libraries wizard appears. This lets you step through library
configuration, including this input (some of which is filled in by default):
l
Library type (select SCSI/NDMP).
l
An NDMP remote username and a password are required for an NDMP device that
acts as a storage node.
l
Adjust the Enable New Device option, if necessary.
l
Current server sharing policy. Use maximal sharing with Dynamic Drive Sharing
(DDS). By default, the sharing policy is displayed as “server default,” which is
maximal sharing.
l
Storage nodes to which libraries can be configured (select a storage node to see
its details). If the appropriate storage node is not listed, click Create a New
Storage Node.
l
When creating a new storage node, replace the default value in the Name field
with the fully-qualified domain name or short name of the new storage node.
l
Update storage node properties, if required.
4. After specifying the required information, click Start Configuration. The configuration
window displays a message that the Configure All Libraries process has started. The
status of the configuration activity can be viewed by the Monitoring > Log screen.
5. When the configuration is complete, click Finish to close the configuration wizard. If
problems occur during configuration, you can click the Back button on the
configuration window to adjust the settings.
Scanning for libraries and devices
Devices already known to the NetWorker server can be seen in the enterprise hierarchy in
the navigation tree. Use the Scan for Devices option described here to find devices that
are not yet known to the NetWorker server. Be aware that:
l
A storage node must be added to the hierarchy before its devices can be scanned.
l
The Scan for Devices option does not detect file type or advanced file type devices.
l
By default, the Linux kernel configures a maximum of 128 st devices by default. Refer
to The inquire command and the Scan for Devices operation do not detect more than
128 tape devices on page 133 if the Scan for Devices option does not detect more
than 128 tape devices on Linux operating systems.
SCSI and VTL libraries
145
Backup Storage
l
A specific network interface can be used between the NetWorker server and the
storage node when scanning for devices. Identifying a specific network interface for
device scan operations on page 148 provides more information.
Procedure
1. In the Console window, click Enterprise.
2. In the navigation tree, select a NetWorker server.
3. In the Name column of the Host detail table, double-click NetWorker. The NetWorker
Administration window for the selected server opens. Note that while multiple
NetWorker Administration windows can be open simultaneously, each one displays
information about only one host or server.
4. In the Administration window, click Devices.
5. In the navigation tree:
a. Right-click the server name, and select Scan for Devices.
b. Click the storage node to be scanned.
c. If the appropriate storage node is not listed, click Create a New Storage Node.
d. When creating a new storage node, replace the default value in the Name field with
the fully-qualified domain name or short name of the new storage node.
e. Fill in any required information, such as whether to scan for SCSI or NDMP devices
and whether to search all LUNs.
f. Click Start Scan. To monitor the scan activity, click Monitoring, then select the Log
tab. Any relevant status information is displayed there.
6. Return to the Devices navigation tree to view the refreshed device information
(configured and unconfigured):
l
To display SCSI and NDMP libraries available to the NetWorker server, select
Libraries in the navigation tree. Any available library or silo appears in the
Libraries detail table.
l
To display stand-alone devices available to the NetWorker server, select Devices in
the navigation tree. Any available stand-alone device appears in the Devices detail
table, along with devices available in libraries.
l
To display the libraries and devices that are available to a storage node, select the
storage node in the navigation tree. Available storage nodes appear in the table.
Double-click a storage node to see its details, along with the devices that are
available in the storage node.
Barcode labeling tips
The NetWorker server uses volume labels and barcode labels to identify volumes. Both
label types are recorded in the media database. The volume label is also recorded
internally on the media (internal volume label). The NetWorker server uses barcode labels
to inventory volumes, and uses volume labels to identify the volumes needed for backup
and recovery. A requirement to match the volume label with the barcode label can be set
in the library’s Properties window.
Follow these guidelines when using barcode labels with the NetWorker software:
l
146
When NetWorker software relabels volumes automatically, it reuses the original
volume label name. A label name can be changed only if the volume is relabeled
manually. The NetWorker software scans the barcode label during the labeling
process and updates the media database with the new volume name and its
associated barcode label.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
Do not use identical barcode labels for any of the NetWorker volumes. The use of
identical labels defeats the purpose of using barcode labels, which is to facilitate the
inventory process and ensure label accuracy.
l
Volume names must be unique on the NetWorker server. Give each volume a unique
volume label. If a second volume is labeled with an existing barcode label and the
Match Barcode Labels attribute in the library’s properties is enabled, the NetWorker
server displays an error message and does not allow the second volume to be
labeled. The error message identifies the library slots containing the two volumes
with identical labels and the barcode label.
To correct this problem, either apply a different label to one of the volumes and
restart the labeling process, or disable the Match Barcode Labels attribute in the
library’s properties while labeling the second volume.
l
It is not necessary to label existing volumes with barcode labels if they are stored in a
vault or offsite for long periods. These volumes are rarely, if ever, inventoried.
l
Before using barcode labels on existing volumes, affix the barcode labels to them.
Then, load and mount each volume individually, so that the NetWorker server can
match the barcode label with the existing volume label.
l
Record the volume label on the tape.
l
A variety of barcode labels can be purchased from third-party vendors. Choose from
among numeric labels, alphanumeric labels, or a special combination of numbers
and characters. Furthermore, barcode labels can be ordered to match a current
volume labeling scheme.
l
Use a consistent labeling scheme. If volumes are labeled with the server name and
an extension such as “001,” order a range of labels starting with “server_name.001”
and ending with “server_name.100”, or as wide a range as necessary. Instructions for
barcode labels should be provided with the library hardware documentation. Contact
the hardware manufacturer with questions about barcode labels. A consistent
labeling scheme helps better organize and track volumes. It also facilitates the
inventory process if all of the volumes, use barcode labels.
Configuring a library to use volumes with barcodes
Barcode labeling tips on page 146 provides more information.
Procedure
1. In the Administration window, click Devices.
2. Open the Libraries folder. The Libraries detail table appears.
3. Right-click the appropriate library, and select Properties. The Properties window
appears.
4. Select the Configuration tab.
5. In the Media Management area of the Configuration tab, select:
l
Bar Code Reader
l
Match Bar Code Labels
6. Click OK.
Using unmatched volume and barcode labels
Note
If unmatched volume and barcode labels are to be used, ensure that labels are attached
to the outside of the volumes.
SCSI and VTL libraries
147
Backup Storage
Procedure
1. Apply barcode labels to the volumes.
2. Place the volumes with the barcode labels in the library.
3. In the Administration window, click Devices.
4. Open the Libraries folder. The Libraries detail table appears.
5. Right-click the appropriate library, and select Properties. The Properties window
appears.
6. Select the Configuration tab.
7. In the Media Management area of the Configuration tab:
l
Select Bar Code Reader.
l
Ensure that Match Bar Code Labels is not selected.
8. Click OK. The NetWorker server uses the next available label from the label template
for the volume name. It labels the volumes and records both labels in the media
database.
9. Inventory the volumes to ensure that the NetWorker server has the most current
volume information.
10. Use Media > Volumes to match the correct volume labels to the barcode labels.
Consider making a list of the name correlations.
Note
If the barcode function is enabled, but no barcode label is affixed to the volume, an
error message indicates that a barcode label does not exist.
Identifying a specific network interface for device scan operations
If the NetWorker server has multiple network interfaces, you can specify that a specific
network interface be used for scan operations. In this case, the dvdetect (device scan)
program will use the specified network address or hostname to communicate with the
NetWorker server.
Procedure
1. In the server’s Administration interface, click the Devices button.
2. Select View > Diagnostic Mode.
3. In the left pane, click on the Storage Nodes folder.
4. In the right pane, select a storage node.
5. Right-click the storage node and select Properties.
6. Select the Configuration tab.
7. In the Server network interface field, type the network address or the unique
hostname of the network interface on the NetWorker server that is to be used.
8. Click OK.
Media Library parallelism
Use the Max parallelism attribute on the Configuration tab of the Library resource to
define the media library parallelism.
Media library parallelism allows you to define the maximum number of available devices
for inventory and label operations.
148
EMC NetWorker 9.0.x Administration Guide
Backup Storage
EMC recommends that you set the Max parallelism attribute of the Library resource to one
less than the number of devices within the library, which allows you to reserve on device
for recovery operations.
To improve the efficiency of library operations that operate on multiple volumes, use
multiple devices in parallel for these operations. However, you may wish to restrict the
number of devices that NetWorker uses for inventorying and labeling operations, to
ensure that some devices are available for other library operations.
Managing the library configuration
This section provides detailed information about managing a tape library in the
NetWorker environment.
Auto Media Management
Auto Media Management gives the NetWorker server automatic control over media that
are loaded in the storage device.
When you enable the Auto Media Management feature during device configuration, the
NetWorker server automatically:
l
Labels the volume (recognizes EDM labels and does not overwrite them).
NOTICE
If the Auto Media Managment feature is enabled, the NetWorker server considers
volumes that were labeled by a different application to be valid re-label candidates.
Once the NetWorker server re-labels the volume, the previously stored data is lost.
l
Mounts the volume.
l
Overwrites volumes that are consider to be unlabeled. The NetWorker server
considers a volume to be unlabeled under the following conditions:
l
n
Has no internal label.
n
Is labeled with information other than a NetWorker label.
n
Is labeled with a NetWorker label, but the density that is indicated on the internal
label differs from that of the device where the volume is mounted.
Recycles volumes eligible for reuse that are loaded into the device.
When you do not enable the Auto Media Management feature, the NetWorker server
ignores unlabeled volumes and does not use the volume for backup.
The Auto Media Management feature can re-label a volume that has a different density, it
is possible, inadvertently, to overwrite data that still has value. For this reason, be careful
if NetWorker volumes are shared among devices with different densities.
Existing tapes with NetWorker labels
When Auto Media Management is used with tapes that have NetWorker labels that have
not been recycled, the volumes must be removed from the media database before a
utility such as tar is used to overwrite the labels. Also ensure that the tapes have been
fully rewound before overwriting the labels. Auto Media Management can then properly
relabel the tapes.
Auto Media Management for stand-alone devices
The Auto Media Management feature can be enabled for stand-alone devices during
manual device configuration, or from the Properties window after configuration.
When Auto Media Management is enabled for a stand-alone device, the following
processes occur when a volume becomes full during a backup:
SCSI and VTL libraries
149
Backup Storage
l
A notification is sent that indicates that the server or storage node is waiting for a
writable volume. Simultaneously, the NetWorker server waits for the full, verified
volume to be unmounted.
l
The device is monitored and the software waits for another volume to be inserted into
the device.
l
After a volume is detected, a check is performed to determine whether the volume is
labeled. If so:
n
The volume is mounted into the device.
n
The NetWorker server checks to see whether the newly mounted volume is a
candidate to receive data:
1. If yes, the write operation continues.
2. If no, the NetWorker server continues to wait for a writable volume to continue
the backup.
l
If the volume is recyclable and is a member of the required pool, it is recycled the
next time a writable volume is needed.
l
If the volume is unlabeled, it is labeled when the next writable volume is needed for a
save. Note that Auto media management does not label disk type devices such as
AFTD and Data Domain.
NOTICE
If a partially full volume is unmounted, the NetWorker server automatically ejects the
volume after a few seconds. If a stand-alone device is shared between storage nodes,
then Auto Media Management should not be enabled for more than one instance of
the device. Enabling Auto Media Management for more than one instance of the
stand-alone device will tie up the device indefinitely. No data is sent to the device
and no pending message is sent.
Enabling Auto Media Management for libraries
Auto Media Management is not enabled for libraries during autoconfiguration. Auto
Media Management for a library can be set by changing the library’s properties after
configuration.
Procedure
1. In the server’s Administration window, click Devices.
2. Select the Libraries folder in the navigation tree. The Libraries detail table appears.
3. Right-click the library, and select Properties. The Properties window appears.
4. Select the Configuration tab.
5. In the Media Management area, select Auto Media Management.
6. Click OK.
Labeling volumes
The NetWorker software applies a label template to create a unique internal label for each
volume. The label corresponds to a pool and identifies the pool for the volume during
backup and other operations.
Several preconfigured label templates are supplied with the NetWorker software. You
cannot delete these preconfigured label templates. Naming label templates on page 73
provides more information.
When you label a volume, the labeling process:
150
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
Writes a label on the volume.
l
Adds the volume label to the media database.
l
Prepares tape media to have data written to it.
When you re-label tape, the data on the tape is effectively gone.
During data recovery, the server requests the volume that contains the required data,
identifying the required volume by the name with which it was labeled.
Label templates
Several preconfigured label templates are supplied with the NetWorker software. These
preconfigured label templates cannot be deleted. Naming label templates on page 73
provides more information about label templates and preconfigured label template.
Labeling or re-labeling library volumes
Labeling volumes in a library is time-consuming, so consider labeling volumes before it is
time to back up or recover files. When a volume is re-labeled, that volume is initialized
and becomes available for writing again.
Procedure
1. In the Administration window, click Devices.
2. In the left pane, select Libraries.
A list of libraries appears in the right pane.
3. Right-click the library and select Label.
Details for the selected library appear, including divided tables for devices and slots.
The Label Library Media dialog box also appears.
4. From the Target Media Pool list, select the pool for the volume.
The pool determines the label template that is used to label the volume.
5. To require manual recycling of the volume, select Allow > Manual Recycle.
With manual recycling, the volume is not automatically marked as recyclable when all
save sets expire. You must manually mark the volume as recyclable.
NOTICE
A volume that has been set to manual recycle retains that setting, even after the
volume is re-labeled. You must explicitly reset the volume to automatic recycle by
right-clicking the volume in the Media window, selecting Recycle, and then selecting
the Auto option.
6. To be prompted before the existing label is overwritten, select Prompt to overwrite
label.
7. Click OK.
The Library Operation dialog box appears, stating that the library operation has
started.
8. To track the status of the label operation, click Monitoring in the Administration
window.
9. If you selected Prompt to overwrite label, confirm the overwrite of the existing volume
label with a new label:
a. Right-click the label operation in the Monitoring window and select Supply Input.
A confirmation message appears.
SCSI and VTL libraries
151
Backup Storage
b. Click Yes.
Verifying the label when a volume is unloaded
If a SCSI reset is issued during a backup, the volume rewinds and NetWorker may
overwrite the volume label.
To detect if the label is overwritten in this circumstance, select the Verify label on eject
checkbox in the Device resource, or set the Verify label on unload setting in the Jukebox
resource to Yes. With these settings, NetWorker verifies that a volume label exists before
ejecting the volume. If the volume label cannot be read, all save sets on the volume are
marked as suspect and the volume is marked as full.
Empty slots in label operations
Slots that have been intentionally left empty (such as bad slots) are skipped during
labeling operations. The NetWorker software logs a message similar to: “Slot 5 empty,
skipping.”
Barcode labels
The option to label a library volume with a barcode is available during automatic device
configuration. This option can be set in the library’s Properties tab after configuration.
Barcode labels make volume inventory fast and efficient. They eliminate the need to
mount the volumes in a device. The library scans the external barcode labels with an
infrared light while the volumes remain in their slots. Inventorying with barcode labels
greatly reduces the time needed to locate a volume or determine the contents of a library.
Barcode labels also provide greater labeling accuracy. The labels are placed on the
volumes before the volumes are loaded and scanned in the library. Once the library has
scanned the barcode, the NetWorker server records and tracks the label in the media
database. The NetWorker server uses barcode labels only to inventory volumes. A volume
must have a label, but it need not have a barcode label.
Note
Libraries include hardware that reads barcode labels. The barcode information is then
forwarded to the NetWorker server. Problems reading barcode labels indicate hardware
problems. In the event of a barcode-related problem, consult the library’s documentation
or the hardware vendor.
Requirements for performing an inventory with barcodes
To perform an inventory by using barcodes, the following requirements must be met:
l
The library must have a barcode reader.
l
A barcode label must be present on the tape.
l
The location field within the NetWorker media database must be correct or null. To
view the location field, use the mmlocate command.
Device Service mode
Use the service mode setting to take a device offline temporarily. Service mode differs
from the disabled state in that the nsrmmd process is not stopped.
While a device is in service mode, save or recover sessions that are either in process or
pending are completed. No new sessions are assigned to the device while it is in service
mode.
Although a drive in service mode is taken out of the collection of drives that the
NetWorker software can select for automated operations, the drive is available for some
manual operations that use the nsrjb or nsrmm command with the -f option. For more
information, refer to the EMC NetWorker Command Reference Guide or the UNIX man pages.
152
EMC NetWorker 9.0.x Administration Guide
Backup Storage
The device might also go into service mode, rather than become disabled, if consecutive
errors occur in excess of the maximum consecutive error count specified for the device.
This means that if there are no hardware issues, the tape can be ejected and used in
other drives. Media handling errors on page 174 provides more information about how
to set the maximum consecutive error count.
Note
The drive must be manually reset to Enabled for the NetWorker software to use the device
again.
Setting the Service mode for a device
Procedure
1. Open the device’s Properties window.
2. On the General tab, set Status Enabled to Service.
Reconfiguring a library
Use this procedure to reconfigure a tape library.
Before you begin
To reconfigure a library or to add or remove access paths to the devices in a library, use
an account with the Configure NetWorker privilege. This includes access paths that allow
libraries to be shared.
Note
The following procedure does not support adding NDMP devices to a non-NDMP library if
both the NDMP server and the NetWorker storage node are on the same host. Instead,
use the jbedit command.
Procedure
1. Run Scan for Devices, in case a device path has been added to, or removed from, the
library since the latest scan.
2. In the server’s Administration window, click Devices.
3. Select Libraries in the navigation tree. The Libraries detail table appears.
4. In the navigation tree, right-click the entry for the library to be reconfigured, or open
the Storage Nodes folder, open the library folder, and then right-click the library entry
there.
5. Select Reconfigure Library. The Reconfigure Library window appears. Note that the
storage node name and library name cannot be changed in this window.
6. Make appropriate changes in the Configure devices on various storage nodes using
existing drive connectivity area, selecting or clearing checkboxes as necessary, or
using the buttons at the right side of the area (Check All, Clear All, Reset).
Drives that are already configured to be used by the library display check marks in the
boxes that are adjacent to their names:
l
Selecting a box adds the drive to the library.
l
Clearing a box removes the drive from the library.
l
The Reset button returns the checkboxes to the condition they had when the
Reconfigure Library window was opened.
7. Click Start Configuration to reconfigure, or Cancel to leave the window.
SCSI and VTL libraries
153
Backup Storage
8. Run Scan for Devices to refresh the navigation tree and show the reconfiguration
results.
Specifying library slots
The available slots feature controls which volumes the NetWorker server uses for backup.
The server uses all volumes in a library to perform recoveries, but the volumes that are
automatically selected for backups can be controlled by designating a range of available
slots in the library.
Perform the following steps to define the available slots in a tape library.
Procedure
1. Ensure that volumes have been placed in all the available slots of the library so that
the NetWorker server can continue uninterrupted with an automatic backup.
With two-sided media, the number of available slots is effectively doubled. For
example, with 32 optical disks labeled “jupiter.001.a” to “jupiter.032.b,” there are a
total of 64 sides, and therefore, there are 64 slots from which to choose.
2. In the server’s NetWorker Administration interface, select View > Diagnostic Mode
from the menu bar.
3. Click Devices.
4. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
5. In either the navigation tree or in the Libraries detail table, right-click the library on
which the slots are to be designated, and select Properties.
6. Select the Advanced tab of the Properties window.
7. In the Media Management Area, in the Available slots field, type a range of
contiguous slots, then click + to add the range of slots.
For example (assuming that no slots have already been configured), to designate slots
1 through 3 as available, then skip a defective slot 4, and designate slots 5 through 7
as available, type this information in the Available Slots field:
a. Type 1-3, then click + to add these slots.
b. Type 5-7, then click + to add these slots.
c. Click OK. Slot 4 will be skipped when tapes are loaded.
Reset a library
A library must be reset each time the library and the NetWorker software become out of
sync. A library reset can be done using either the Administration interface or the
command prompt.
Resetting a library in the Administration interface
To reset a library in the Administration interface:
Procedure
1. In the Administration window, click Devices.
2. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
3. Select a library in the navigation tree or double-click a library in the Libraries detail
table to open the double-paned Library Operations view.
The library’s drives are listed in the pane on the left in the Device column. The library’s
slots are listed in the pane on the right.
154
EMC NetWorker 9.0.x Administration Guide
Backup Storage
4. Right-click a library in the Device column, and select Reset. You are prompted to reset
the library.
5. Click Yes. The Library Operation window appears and displays this message:
The library operation has started.
Please see the Monitoring->Operations screen for its status.
6. Click OK.
Resetting a library from the command prompt
Use the nsrjb -HE command to reset a library from the command prompt. For example, the
library inventory must be correct after adding drives to an SJI-compliant library, such as
adding DLT7000 drives to an ETL 7/3500 device.
To make the NetWorker software aware of these new drives, run nsrjb -HE to reset the
library. The -E option reinitializes the library’s element status. Some libraries can track
whether there is media in a component in the library. This feature is known as an element
status capability.
A series of commands exists that allow direct interaction with libraries (sji commands)
and tape drives (cdi commands). These commands should only be used by the most
knowledgeable of NetWorker users, as the consequences of using them can be unknown.
For information about these commands, refer to the EMC NetWorker Command Reference
Guide or the UNIX man pages.
Deleting libraries
The library's devices remain, and can still respond to NetWorker operations (such as
monitoring, labeling, deletion, and so on) after the library definition is deleted. A deletion
of a library deletes the library, not its devices.
Procedure
1. In the server’s Administration interface, click Devices.
2. Select Libraries in the navigation tree. The Libraries detail table appears.
3. In either the navigation tree or in the Libraries detail table, right-click the entry for the
library to be deleted, and select Delete.
4. When prompted, click Yes.
This message appears:
"Are you sure you want to delete this jukebox? If so, please reattempt
deletion within a minute."
5. Click OK to confirm the deletion.
Library notifications
The NetWorker server uses notifications to send messages about NetWorker events.
Several preconfigured notifications, such as the following, provide information about
various situations:
l
Volumes in the library are 90% full
l
Library needs more volumes to continue
l
Library has a mechanical problem
l
Library device needs cleaning
SCSI and VTL libraries
155
Backup Storage
l
Cleaning cartridge needs attention.
The NetWorker software automatically mounts a required volume as long as the volume is
loaded in the library. If a recovery operation requires a volume that is not loaded in the
library, the Tape mount request 1 notification sends an alert to Monitoring > Alerts, with a
request to do something with a specific volume.
After a library problem is corrected, it might be necessary to mount a volume so the
NetWorker server can continue to back up or recover files.
Refreshing enterprise library views on request
Procedure
1. From the Console window, click Libraries.
2. In the navigation pane, select a server to update, or select the top item in the
hierarchy to update library information for all NetWorker servers.
3. Right-click the server, and select Refresh.
Changing the polling interval for enterprise library views
Enterprise library views are updated periodically without user intervention.
Procedure
1. From the Console window, click Setup.
2. From the Setup menu, select System Options.
3. In the Polling Interval for NetWorker Libraries field, type the appropriate time, in
hours.
4. Click OK.
Adding and removing media by using the library front panel
Certain media libraries allow for media to be added and removed by using the front panel
display. This operation circumvents the NetWorker server's normal procedures for adding
and removing volumes and may cause the server information to become out of sync with
the library. Normally, you should use the NetWorker server procedures for adding and
removing media, rather than the library's front panel display. This is more efficient and
guarantees that the server and the library will be in sync.
If it is necessary to use the library's front panel display to add and remove volumes.
Note
When a library is partitioned, the NetWorker software does not become aware of the
partitioning. This means that the entire physical library will be disabled, not just one
partition.
Procedure
1. In the Properties window for the Library, on the General tab, set Status Enabled to
Service.
Note
Putting the library in service mode will cancel all operations or wait for operations to
complete that cannot be canceled, and then put the library into disabled mode.
2. Once the library is in disabled mode, use the library's front panel to add and remove
tapes.
156
EMC NetWorker 9.0.x Administration Guide
Backup Storage
3. In the Properties window for the Library, on the General tab, set Status Enabled to
Enabled.
4. Inventory the library. Inventorying library volumes on page 162 has information about
inventorying libraries.
Volume mounting and unmounting
A volume must be mounted before files can be backed up. If no volume is mounted at the
start of a backup, an error message appears and requests that a volume be mounted.
Mounting or unmounting a volume in a library
Procedure
1. In the Administration window, click Devices.
2. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
3. Select a library in the navigation tree or double-click a library in the Libraries detail
table to open the double-paned library operations view. The library’s drives are listed
in the Devices column, and its slots are listed in the Slot column.
4. To mount a volume:
a. In the Devices column, select the appropriate drive.
b. In the Volume column, right-click a volume to mount, and select Mount.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
c. Click OK.
5. To unmount the volume:
a. Right-click the device or the volume in the double-paned table view of the library
and select Unmount.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
6. Click OK.
Unmounting volumes automatically (idle device timeout)
At times, a volume that is mounted in one device might be needed by another device in
the same library. For example, data being recovered by one device could span more than
one volume, and the required volume could be mounted on another device. To address
this need, a value can be defined in the Idle Device Timeout attribute for that particular
library.
The Idle Device Timeout attribute specifies the number of minutes a mounted volume can
remain idle before it is automatically unmounted from the device and returned to its slot,
where it can then be accessed by another device. For libraries, this attribute appears on
the Timers tab of a library's Properties. The default value for a library is 10 minutes.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
SCSI and VTL libraries
157
Backup Storage
2. Open the Libraries folder in the navigation tree.
3. Right-click the appropriate library in the detail table, and select Properties. The
Properties window appears.
4. Select the Timers tab.
5. Specify a value in the Idle Device Timeout attribute.
1. You can also override the library’s Idle Device Timeout attribute for a specific device in
the library.
To specify the Idle Device Timeout value for a specific device:
6. In the server’s Administration interface, click Devices.
7. Select View > Diagnostic Mode.
8. Select Devices in the navigation tree. The Devices detail table appears.
9. Right-click the device and select Properties.
10. Select the Advanced tab.
11. Specify a value in the Idle Device Timeout attribute.
The default value is 0 (zero) minutes, which means that the device never times out
and the tape must be ejected manually. However, when the value of this attribute is
set to 0, the value specified in the device library’s Idle Device Timeout attribute will
take precedence.
Mounting or unmounting a volume in a stand-alone tape drive
Procedure
1. Manually insert a volume in the stand-alone drive, or ensure that a volume is already
loaded.
In a stand-alone device, a volume that has been loaded into the drive is not
considered to be mounted until it has been explicitly mounted in the user interface or
from the command prompt.
2. In the Administration window, click Devices.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Select the device. To mount the volume, in the Devices detail table, right-click the
device, and select Mount.
5. To unmount the volume, in the Devices > detail table, right-click the device, and select
Unmount.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
6. Click OK.
Labeling and mounting a volume in one operation (stand-alone tape
drive)
When multiple storage devices are connected to the NetWorker server, the device for
labeling must first be selected from the list of available devices. Remember that labeling
158
EMC NetWorker 9.0.x Administration Guide
Backup Storage
a volume makes it impossible for the NetWorker server to recover original data from that
volume.
Procedure
1. In the Administration window, click Devices.
2. Manually insert an unlabeled or recyclable volume in the NetWorker server storage
device, or ensure that a volume of this type is already present for the NetWorker server
to access.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Right-click the stand-alone device in the detail table, and select Label. The Label
window appears:
a. Type a unique label name, or accept the default name that is associated with the
selected pool.
If the volume is unlabeled, the NetWorker server assigns the next sequential label
from the label template that is associated with the selected pool. If a recyclable
volume from the same pool is being re-labeled, then the volume label name and
sequence number remain the same. Access to the original data on the volume is
destroyed, and the volume becomes available.
b. Select a pool on the Pools menu. The NetWorker server automatically applies the
label template that is associated with the Default pool unless a different pool is
selected.
c. Select the Manual Recycle attribute if the volume should be manually recycled.
If the Manual Recycle attribute is enabled when the volume is labeled, the volume
cannot automatically be marked as recyclable according to the retention policy.
When a volume is marked as manual recycle, the NetWorker server disregards the
assigned browse and retention policies. Therefore, only an administrator can mark
the volume recyclable.
A volume that has been set to manual recycle retains that setting, even after relabeling. A Manual Recycle policy cannot be changed back to Auto Recycle by
clearing the Manual Recycle checkbox. The volume must be explicitly reset to use
auto recycle.
d. The Mount After Labeling attribute is selected by default. The NetWorker server
automatically labels the volume, and then mounts the volume into the device.
5. Click OK.
6. If the volume is recyclable, a message warns that the named volume is about to be
recycled, and asks whether to continue. Click Yes to re-label and recycle the volume.
7. After a volume is labeled and mounted in a device, the volume is available to receive
data. Since the NetWorker label is internal and machine-readable, place an adhesive
label on each volume that matches that internal volume label.
Configuring a library to use volumes with barcodes on page 147 provides information
on using barcode labels.
Note
If you are in the process of re-labeling a mounted volume and you choose not to
overwrite the existing label, the volume is left in an unmounted state. To use this
volume, mount it again.
SCSI and VTL libraries
159
Backup Storage
Labeling volumes without mounting
Volumes can be prelabeled without being mounted.
To label a volume without mounting, follow the same procedures as for labeling and
mounting in one operation, but clear the Mount After Labeling attribute in the Label
window.
Mounting uninventoried volumes
You can mount volumes that are not included in the library inventory, but are valid
(properly labelled) NetWorker volumes.
Procedure
1. In the Administration window, click Devices.
2. Select View > Diagnostic Mode on the toolbar.
3. Manually insert the volume in an empty library slot.
4. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
5. Select the library in the navigation tree in which the volume was manually inserted, or
double-click the same library in the Libraries detail table. The Libraries detail table
changes to the double-paned library operations view. The library’s drives are listed in
the Devices column, and its slots are listed in the Slot column.
6. In the Devices column, right-click the library in which the volume was manually
inserted, and select Inventory. The Inventory Library window appears.
7. Type the slot number of the volume in both the First and Last field of the Slot Range.
8. Select Operation Type: either Slow/Verbose (the default) or Fast/Silent.
l
When Slow/Verbose is selected, the Supply Input option and icon on the
Operations screen of the Monitoring window can be used to confirm the choice to
relabel a volume. The device path appears in the Device field.
l
When Fast/Silent is selected, the Supply Input option and icon are not available,
and relabeling proceeds automatically, without user input. The device path does
not appear in the Device field. Entering user input on page 56 provides details.
9. Click OK.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
The NetWorker software then inventories the specified slot.
10. Mount the inventoried volume.
NOTICE
Unlabeled tapes may not be mounted for inventorying. Unlabeled tapes can only be
mounted to be labeled. An attempt to mount an uninventoried volume by using
unlabeled media results in an I/O error. The volume will also be ejected.
Libraries with volume import and export capability
The NetWorker software supports the use of the SCSI-II import/export feature found in
many brands of library. Depending on the library model, this feature is also known as
cartridge access port (CAP), mail slot, and loading port. The import/export feature
deposits and withdraws (ejects) volumes from slots in the library. This feature enables
160
EMC NetWorker 9.0.x Administration Guide
Backup Storage
the operator to deposit and withdraw cartridges without invalidating the device inventory
list. Normally, if the operator opens the door to load or unload media, the element status
of the autoloader is invalidated, which requires the reinitialization the library. The
NetWorker server does not, however, automatically inventory the volume after a deposit
and withdrawal.
The reinitialization usually consists of the following:
l
An inventory of all slots
l
A reset of the robotic arm
l
A check to see whether each drive is working
The Deposit attribute causes a library to take the first available volume from the CAP and
place it in the first empty library slot. The Eject/Withdraw attribute moves a volume from a
slot (never from a drive) to the CAP.
Depositing a volume by using the import/export feature
Use these general instructions when working with a CAP. Specific instructions for working
with a CAP can vary, depending on the library manufacturer. For specific instructions,
refer to the library’s documentation.
Procedure
1. Ensure that volumes are available in the CAP for deposit.
2. In the Administration window, click Devices.
3. Select Libraries in the navigation tree. The Libraries detail table appears.
4. Double-click the library in which to deposit the volume. The Libraries detail table
changes to the double-paned library operations view.
5. Right-click either the device or the slot, and select Deposit. You are prompted to
deposit the volume.
6. Click Yes. The Library Operation window displays this message:
The library operation has started.
The Monitoring > Operations screen displays its status.
7. Click OK.
8. Click Monitoring to go to the Monitoring window and select the Operations tab.
9. Right-click the User Input icon for the deposit job and select Supply Input. You are
prompted to load the cartridges into the ports and type Yes to continue.
10. Click Yes.
11. Right-click the User Input icon for the deposit job and select Supply Input again. You
are prompted to continue depositing volumes.
12. Click Yes to continue depositing volumes, or No when done.
Withdrawing a volume by using the import/export feature
Note
If the library is partitioned into logical libraries and the import/export slots are shared
between the partitions, you must withdraw volumes by using the nsrjb command with
the -P option to specify the port or ports from which to withdraw volumes. Refer to the
nsrjb man page or the EMC NetWorker Command Reference Guide for more information.
SCSI and VTL libraries
161
Backup Storage
Procedure
1. Ensure that the volume to be withdrawn is in a known slot, and that the CAP has an
empty port to hold the withdrawn volume.
2. In the Administration window, click Devices.
3. Select Libraries in the navigation tree. The Libraries detail table appears.
4. Double-click the library from which the volume is to be withdrawn. The Libraries detail
table changes to the double-paned library operations view.
5. Right-click the slot that contains the volume, and select Eject/Withdraw. You are
prompted to withdraw the volume.
6. Click Yes.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
7. Click OK.
8. Select Monitoring > Log to see the result. A successful Eject/Withdraw operation ends
with a Succeeded comment in the Log.
Inventorying library volumes
When the NetWorker software labels the contents of a library, the software registers the
location of the volumes in the library slots when it assigns the volume label. This process
is called taking inventory. When the volumes in the library are inventoried, the NetWorker
software reads the label of each volume and records its slot number. If the volumes are
not moved in the library after they have been labeled, then the NetWorker server can
access the volumes because each volume label is assigned to a specific slot.
If, however, the contents of the library are changed without being labeled, or if volumes
are moved into new slots, the NetWorker software must be notified that the library now
holds a different set of labeled volumes or that the volumes are in a different order. For
example, if the library has more than one magazine, the volumes must be inventoried
each time that a magazine is removed, and another one is loaded into the library.
When the volumes in a new magazine are labeled, there is no need to inventory them.
The NetWorker software automatically records the slot number in which each newly
labeled volume is located.
The NetWorker software can use barcode labels to speed up the inventory process. If the
library supports the use of barcode labels, consider using them if large numbers of
volumes, and/or if the library contents change often. Barcode labels on page 152
provides more information on using barcode labels.
Procedure
1. In the Administration window, click Devices.
2. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
3. Select a library in the navigation tree or double-click a library in the Libraries detail
table. The Libraries detail table changes to the double-paned library operations view.
4. Right-click anywhere within the Devices pane, and select Inventory. The Inventory >
Library window appears.
5. Type the numbers of the first and last slots to be inventoried in the Slot Range area.
6. Select Operation Type: either Slow/Verbose (the default) or Fast/Silent.
162
EMC NetWorker 9.0.x Administration Guide
Backup Storage
7. Click OK.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
8. Click OK. If the volumes do not have barcode labels, the NetWorker software must
mount each volume, read its label, and unmount it. In this case, the inventory process
can take some time to complete.
Library maintenance
Periodically clean a storage library to keep it working correctly. The NetWorker server
provides automatic cleaning of devices located in libraries. The server does not support
automatic cleaning for stand-alone devices. Cleaning is an option set during
configuration.
The service mode feature allows a library to be taken offline temporarily for cleaning or
other maintenance.
Automatic tape device cleaning
Tape device cleaning is an automated, self-contained operation. It is no longer part of a
media-loading operation. Tape device cleaning is automatically triggered if one of these
conditions exist:
l
The last time the device was cleaned was a full cleaning interval ago.
l
The Cleaning Required attribute for the device is set to Yes in one of the following
ways:
n
Manually by the user.
n
Automatically by the NetWorker server, after it receives a “device needs cleaning”
notification.
When one of these conditions is met for a device, cleaning begins as soon as the device
becomes available. Loaded devices are unloaded before a cleaning operation begins.
Loading a cleaning cartridge (with the nsrjb -l cleaning cartridge command) to force a
cleaning operation is no longer supported.
Selecting a tape device manually for cleaning
NOTICE
Do not enable automated cleaning for silos in the NetWorker software. The automated
device cleaning feature cannot be used in a silo, because it depends on fixed slot
numbers. For information about how to clean devices in a silo, refer to the silo
manufacturer’s software documentation.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Open the Libraries folder in the navigation tree and select the drive that contains the
mounted volume with the block size being checked. The drive’s detail table appears.
3. Right-click the drive in the detail table, and select Properties. The Properties window
appears.
4. Select the General tab.
5. Set the Cleaning Required attribute to Yes.
SCSI and VTL libraries
163
Backup Storage
Delaying tape device cleaning
Occasionally it is necessary to set the Cleaning Delay attribute in order to allow a tape
device to sleep before attempting to unload a cleaning cartridge.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Select View > Diagnostic Mode.
3. Open the Libraries folder in the navigation tree.
4. Right-click the appropriate library in the detail table, and select Properties. The
Properties window appears.
5. Select the Timers tab.
6. Select a value in seconds for the Cleaning Delay attribute.
Tape alert
The TapeAlert feature provides, among other things, diagnostic information for devices
for which hardware cleaning is enabled. NetWorker provides the following attributes for
tape device cleaning:
l
Cleaning required
l
Cleaning interval
l
Date last cleaned
When the Common Device Interface (CDI) is enabled, TapeAlert attributes provide tape
drive status. SCSI Commands must be selected for the CDI attribute on the Configuration
tab of the relevant device’s Properties. If CDI cannot be enabled, TapeAlert is not
supported.
Devices that are capable of TapeAlert perform constant self-diagnostics and
communicate the diagnostic information via the nsrmmd program to logs that can be
viewed in the Monitoring task.
TapeAlert attributes are found in the device’s Properties, on the Volume tab. Their
respective descriptions are as follows:
l
TapeAlert Critical: Displays critical diagnostic information, such as for media or drive
failure, when user intervention is urgent and data is at risk.
l
TapeAlert Warning: Displays a message when the media or device needs servicing.
l
TapeAlert Information: Displays status information.
The following table describes the nature of the tape alert levels.
Table 32 Tape alert severity
Severity
Urgently requires user intervention Risks data loss Explanatory
Critical
X
Warning
Informative
X
X
X
X
The messages indicate tape and drive states related to tape drive read/write
management, cleaning management, or drive hardware errors.
164
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Informative messages
Informative messages indicate status information:
l
A data or cleaning tape is nearing its end of life.
l
A tape format that is not supported.
Note
When automatic cleaning is enabled, a diagnostic message to indicate that a drive
needs cleaning initiates NetWorker drive cleaning.
Warning messages
Warning messages indicate the following types of drive errors:
l
Recoverable read or write errors occurred.
l
Media is at end of life.
l
Read-only tape format is in the drive.
l
Periodic cleaning is required.
Critical messages
Critical messages are warnings that a drive might be disabled and requires immediate
attention to avoid data loss:
l
Unrecoverable read or write errors occurred.
l
Tape is marked read-only.
l
Drive require immediate cleaning.
l
Drive is predicting hardware failure.
Informative and warning messages should clear automatically by nsrmmd once the
reported issue is handled.
Critical messages about hardware errors are not cleared by nsrmmd because they might
indicate intermittent hardware problems.
Troubleshooting libraries and devices
This section provides detailed information about how to troubleshoot issues with
libraries and devices, including how to correct drive ordering issues and block size issues
between UNIX and Windows devices.
Troubleshooting autoconfiguration failure
Common symptoms of library autoconfiguration failure include the following:
l
The library is not listed in the Libraries folder in the Administration interface.
l
The library is listed, but is listed as being unconfigured.
Common causes include:
l
Device drivers are not properly installed.
l
Autodetection fails to match a detected library with its devices due to:
l
n
Out-of-date device firmware.
n
Failure of the library to return its devices’ serial numbers.
Autodetection failed to start on the storage nodes.
Procedure
1. Check Monitoring > Log for relevant messages.
SCSI and VTL libraries
165
Backup Storage
2. From the command prompt, type the following command to verify that the library
returns the serial numbers of its devices:
sn -a b.t.l.
where b.t.l. refers to the bus target LUN of the library. If the bus target LUN is not
known, run the inquire command first, to obtain this information.
Library configuration using the jbedit command
If the autoconfiguration program cannot be used, the jbedit (jukebox edit) program can
be used as a fallback means of editing library configurations. This command can be run
on a NetWorker server, storage node, or client (if the client is a storage node). It operates
without disrupting any backup or recovery operations on the library.
Running the jbedit program requires Configure NetWorker user privileges.
The jbedit program supports all direct-attached SCSI/SJI, SAN, and NDMP libraries.
The jbedit program is not intended to be a full-fledged editor of the Library resource.
The editing of Library resource attributes should be done as described in Reconfiguring a
library on page 153. The jbedit options provide selection lists that make it easy to find
drives or devices to be added or deleted.
The following table lists the most commonly used jbedit program options.
Table 33 Common jbedit options
Option Description
-a
Add a drive or device.
-d
Deletes a drive or device.
-j
Name of the autochanger to be edited.
-f
Name of the device to be added or deleted.
-E
Element address of the device to be added or deleted.
The EMC NetWorker Command Reference Guide or the UNIX man page provides a detailed
description of the jbedit command, its options, and associated diagnostic messages.
Device ordering
The NetWorker server uses logical device names assigned by the operating system when
communicating with devices. It is possible for the operating system to re-associate
logical device names with the physical addresses of the devices, generally after rebooting
the host or after plug-and-play events. This may cause device reordering, where the
physical device will have a different device filename. As a result, tape devices configured
in the NetWorker software no longer match the names of the devices as recognized by the
operating system.
If device reordering occurs, the NetWorker software is unable to use any affected drives
until the configuration is manually corrected.
The NetWorker server detects device reordering events by comparing the current serial
number of the device to the serial number of the device at configuration. If the serial
numbers do not match, the NetWorker server stops all operations on that device and an
error message will be posted, similar to the alert identified for device serial number
mismatch in the table Preconfigured notifications on page 617. CDI must be enabled for
166
EMC NetWorker 9.0.x Administration Guide
Backup Storage
this functionality. Setting the common device interface on page 173 provides more
information about enabling CDI.
Detecting device ordering issues
To determine if there is a problem with device ordering in your environment, you first
determine if the device order that appears in nsrjb output matches the device order from
the inquire and sjisn commands, then verify that the device configuration within your
NetWorker configuration conforms to this.
Procedure
1. Execute the inquire command with the -cl option to determine the device path, scsi
address, and serial number of the device.
2. Execute the sjisn command to determine the current order of the devices:
sjisn scsidev@bus.target.lun
where bus.target.lun is the SCSI address of the robotic arm returned by the inquire
command in step 1, for example, 1.2.0.
3. Match the serial numbers of the devices in the sjisn output to the device names that
correspond to these serial numbers in the inquire -cl output. This will give you the
current device order by device filename.
4. Execute the nsrjb command to determine the order of devices as configured in
NetWorker. Drive entries towards the end of the nsrjb output list the device order as
configured in NetWorker.
5. Compare the device ordering as determined in step 3 and step 4. If the device
ordering in these two steps do not match, the device ordering has changed and the
library will need to be reconfigured.
Drive ordering change corrections
After a drive ordering change has taken place and the NetWorker software is no longer
correctly communicating with devices, you can correct the problem within your NetWorker
configuration by using the NetWorker Console or the jbedit command line program.
Using NetWorker Console to correct drive ordering changes
You can correct drive ordering changes by using the NetWorker Console.
Procedure
1. Ensure that you have a current backup of the resource database.
2. Delete the library resource in the NetWorker Console. Deleting libraries on page 155
provides details.
3. Rescan the library. Scanning for libraries and devices on page 145 provides more
information.
Using the jbedit command to correct drive ordering changes
You can correct drive ordering changes by using the jbedit command.
Procedure
1. Use the jbedit command with the -d option to delete devices from the NetWorker
configuration.
2. Use the jbedit command with the -a option to add the devices again.
Library configuration using the jbedit command on page 166, or the UNIX man page
for jbedit or the EMC NetWorker Command Reference Guide provides more information
on the jbedit command.
SCSI and VTL libraries
167
Backup Storage
Clearing device ordering/serial mismatch errors from the NetWorker Console
After a device ordering error has been detected, a message is displayed in the Alerts and
Notifications windows of the NetWorker Management Console, as well as the log files.
The error message is similar to the following:
“Check system device ordering. Moving device on %s to . To correct,
scan for devices in NMC and re-enable the device.”
An Event ID for the error is also created, which will be removed along with the alert when
the problem is resolved. You can resolve the problem and clear the error message.
Procedure
1. Disable the drive.
2. Perform one of the above procedures to correct the problem.
3. Re-enable the drive, and retry the operation that was being performed prior to
receiving the error.
Results
The Alert will be removed and the event dismissed.
Tape drive number reordering (Microsoft Windows only)
If more than one tape drive is attached to the NetWorker server when both the server and
drives are shut down, restart all of the tape drives, either before or immediately after the
NetWorker server is restarted. If Windows does not locate all of its previously configured
tape drives at the time of startup, it automatically reassigns the tape registry name.
For example, assume that these three tape drives are attached to the server:
l
The first one, \\.\Tape0, is a 4 mm tape drive.
l
The second, \\.\Tape1, is an 8 mm tape drive.
l
The third, \\.\Tape2, is also an 8 mm tape drive.
If only the second and third tape drives are restarted, Windows reassigns the tape
registry numbers so that the second storage device becomes \\.\Tape0 and the third
storage device becomes \\.\Tape1. The tape registry numbers no longer match the
defined storage devices within the NetWorker software. As a result, the server
mishandles the drives and their volumes.
It might be easier to leave a nonoperational drive (device) attached to the server until a
replacement is available. If the drive is removed, the name must be deleted, and then the
new drive must be added.
To disable the drive, select No for the Enabled attribute in the device’s Properties.
Device calibration
For information about the frequency and method for calibrating the loading mechanism
for the device, refer to the library manufacturer’s documentation.
SCSI data block size issues between UNIX and Windows
Different SCSI hardware limitations exist between UNIX and Microsoft Windows operating
systems. This can lead to data block size compatibility problems (although they are less
likely to occur now than in the past, given larger Fibre-Channel capacities). For example,
with a device defined in UNIX that is physically attached to a Windows HBA, it is possible
to define a block size greater than that allowed by the Windows hardware. This could
lead to I/O errors in both write and read states on the device. In order to use both
operating systems, it is necessary to determine a block size that is acceptable to both.
168
EMC NetWorker 9.0.x Administration Guide
Backup Storage
NOTICE
In NetWorker 8.0.1 and later, the default block size for an LTO device increases from 128
KB to 256 KB. When NetWorker labels a new or used volume in an LTO device and the
Device block size attribute of the device is handler default, the label operation uses a
256 KB block size.
Determining the allowable block size
You can determine the allowable block size by checking the Properties window of a
mounted volume while in Diagnostic Mode.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Select View > Diagnostic Mode.
3. Open the Libraries folder in the navigation tree and select the drive that contains the
mounted volume with the block size being checked. The drive’s detail table appears.
4. Right-click the drive in the detail table, and select Properties. The Properties window
appears.
5. Select the Volume tab. In the Loaded Volume area, one of the displayed volume
attributes is the Volume Block Size.
6. Click OK.
Solving block-size compatibility problems
Note
It is also possible to solve problems with block-size compatibility by changing the block
size for an entire device type. The change, however, must be made on each storage node
where it is to be available. Once the block size is changed, it affects only those volumes
that are labeled after the change. Volumes can be relabeled to use the new block size,
but if they contain data that should be saved, be sure to clone the data beforehand to a
volume that already uses the new block size.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Select View > Diagnostic Mode on the menu bar.
3. Open the Libraries folder in the navigation tree and select the drive that contains the
mounted volume with the block size being checked. The drive’s detail table appears.
4. Right-click the drive in the detail table, and select Properties. The Properties window
appears.
5. Select the Advanced tab. In the Device Configuration area, the currently configured
Device Block Size value is displayed.
6. Select the appropriate Device Block Size value.
7. Click OK.
Setting the block size for a device type
Procedure
1. Change the block size:
l
On UNIX, change the block size by setting this environment variable to the greatest
common value for both systems. For example:
setenv NSR_DEV_BLOCK_SIZE_MEDIA_TYPE value
SCSI and VTL libraries
169
Backup Storage
where:
l
n
MEDIA_TYPE is the backup device type available to the NetWorker server (also
found in the Media Type attribute on the General tab of the device’s
properties). The media type syntax must be all uppercase, with underscores (_)
replacing blank spaces and hyphens. Therefore, a device displayed in the
NetWorker software as "8mm Mammoth-2" would be listed as:
8MM_MAMMOTH_2
n
value must be a multiple of 32 KB, with a minimum value of 32 KB.
On Microsoft Windows only, install a later model HBA, or upgrade to drivers that
can support up to 128 KB blocks. Windows also accepts the same environment
variable format as UNIX to set block size.
2. Restart the NetWorker server in order for changed environment variables to take
effect.
Device block size for read and write operations
The block size for a volume is defined during the label operation. The label operation
uses the value defined in the Device block size attribute for the Device or the value
defined by the appropriate block size environment variable.
The block size for both read and write operations uses the block size defined in the
volume header during the label operation rather than the device block size.
Block-size mode (UNIX/Linux only)
Ensure that the block size mode for tape devices that are used with NetWorker software is
set to variable. Otherwise, data recovery might fail. The procedure for setting the device
block size varies depending on the operating system.
The operating system’s documentation provides information about setting the tape
device block size in the operating system.
Device parameter settings
Device parameter settings can be modified for the devices the NetWorker software uses
in two ways:
l
Individually, through the NetWorker Administration interface.
l
Globally, for all devices through operating system environment variables. The
adjustment of environment variables should only be done by users who know the
server environment and performance tuning requirements. For example, an
administrator who wants to fine-tune performance by changing a certain setting for all
LTO devices on a particular NetWorker server.
The variables (and their equivalent names in the Administration interface) are described
in the following sections.
Device setting environment variables
There are several device-related environment variables available to configure devices for
the NetWorker software.
Device-related environment variables include the following:
170
l
NSR_DEV_BLOCK_SIZE_MEDIA_TYPE
l
NSR_DEV_TAPE_FILE_SIZE_MEDIA_TYPE
l
NSR_DEV_LOAD_TIME_MEDIA_TYPE
l
NSR_DEV_LOAD_POLL_INTERVAL_MEDIA_TYPE
l
NSR_DEV_LOAD_TRY_LIMIT_MEDIA_TYPE
l
NSR_DEV_DEFAULT_CAPACITY_MEDIA_TYPE
where:
EMC NetWorker 9.0.x Administration Guide
Backup Storage
MEDIA_TYPE is the backup device type available to the NetWorker server.
Note
The media type syntax must be all uppercase, with underscores (_) replacing blank
spaces and hyphens. For example, a device displayed in the NetWorker software as
“8mm Mammoth-2” would be listed as: 8MM_MAMMOTH_2
To determine the media type, right-click the device an select the General tab. The
Media Type attribute contains the media type that should be used in these
environment variables.
NSR_DEV_BLOCK_SIZE_MEDIA_TYPE
NSR_DEV_BLOCK_SIZE_MEDIA_TYPE is organized in units of kilobytes. This environment
variable will cause NetWorker to override the default block-size setting defined for the
tape drive in the operating system. The value set must be a multiple of 32, with a
minimum value of 32. Maximums are determined by platform, SCSI driver, and device.
For example:
NSR_DEV_BLOCK_SIZE_4MM_20GB=64
For information about using this environment variable to set block-size compatibility
between UNIX and Microsoft Windows. SCSI data block size issues between UNIX and
Windows on page 168 provides more information.
NSR_DEV_TAPE_FILE_SIZE_MEDIA_TYPE
NSR_DEV_TAPE_FILE_SIZE_MEDIA_TYPE is organized in units of
NSR_DEV_BLOCK_SIZE_MEDIA_TYPE and is the number of blocks written between
filemarks. These filemarks are used to locate a particular spot on the tape during
recovery, and more filemarks generally lead to faster positioning. For example:
NSR_DEV_TAPE_FILE_SIZE_TZ89=512
On UNIX and Linux platforms, the NetWorker software writes a filemark by closing and
reopening the tape device, which takes one or two seconds. If this value is too small,
throughput could be slowed and recoveries may take longer to complete.
On Microsoft Windows platforms, the NetWorker software writes asynchronous filemarks.
This setting has a minimal effect on performance.
NSR_DEV_LOAD_TIME_MEDIA_TYPE
NSR_DEV_LOAD_TIME_MEDIA_TYPE is the number of seconds that nsrmmd polls and
waits for a drive to become ready after the library inserts a tape into the device.
NSR_DEV_LOAD_POLL_INTERVAL_MEDIA_TYPE is used to set the number of seconds
nsrmmd waits between polls during load time.
If the value of NSR_DEV_LOAD_TIME_MEDIA_TYPE is too short, there could be
unnecessary load failures. If it is too long, then labeling new tapes takes longer than
necessary. The minimum allowable value is 10 seconds. The maximum value is 600
seconds. For example:
NSR_DEV_LOAD_TIME_DTL8000=300
NSR_DEV_LOAD_POLL_INTERVAL_MEDIA_TYPE
NSR_DEV_LOAD_POLL_INTERVAL_MEDIA_TYPE is the number of seconds that nsrmmd
waits between each attempt to read a newly inserted tape. The minimum allowable value
is 1 second, the maximum value is 30 seconds. For example:
NSR_DEV_LOAD_POLL_INTERVAL_DLT=10
NSR_DEV_LOAD_TRY_LIMIT_MEDIA_TYPE
NSR_DEV_LOAD_TRY_LIMIT_MEDIA_TYPE is the number of times that nsrmmd will attempt
to open a drive. The nsrmmd program will poll the drive until the limit set in
NSR_DEV_LOAD_TIME_MEDIA_TYPE is reached. After the limit is reached, it will retry until
SCSI and VTL libraries
171
Backup Storage
the NSR_DEV_LOAD_TRY_LIMIT_MEDIA_TYPE is reached. The default value and minimum
allowable value is 2, the maximum value is 120.
NSR_DEV_LOAD_TRY_LIMIT_DLT=4
NSR_DEV_DEFAULT_CAPACITY_MEDIA_TYPE
NSR_DEV_DEFAULT_CAPACITY_MEDIA_TYPE is the size of the particular tape used to base
the percent full calculation. This variable value has no effect on the actual tape capacity.
Any integer value is allowed, with a KB, MB or GB designation to indicate a range of
values. Any value less than 200 MB will be overridden by the normal default capacity.
There is no obvious maximum, with the only practical limitation being the actual storage
size. For example:
NSR_DEV_DEFAULT_CAPACITY_DTL7000=12GB
Setting device parameters in the NetWorker Administration interface
You can locate and change the device parameters in the Administration interface.
Procedure
1. In the server’s Administration interface, click Devices.
2. Select View > Diagnostic Mode.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Double-click the device in the devices table or right-click the device and select
Properties. The Properties window appears, with the General tab selected.
5. Select the Advanced tab. In the Device Configuration area, the device settings are the
first fields shown. The following table lists the fields and their corresponding
environment variables:
Results
Table 34 Device settings and environment variables
Device setting
Corresponding environment variable
Device Block Size
NSR_DEV_BLOCK_SIZE_MEDIA_TYPE
Device File Size
NSR_DEV_TAPE_FILE_SIZE_MEDIA_TYPE
Device Load Time
NSR_DEV_LOAD_TIME_MEDIA_TYPE
Device Eject Time
None
Device Poll Interval
NSR_DEV_LOAD_POLL_INTERVAL_MEDIA_TYPE
Device Min Load Tries
NSR_DEV_LOAD_TRY_LIMIT_MEDIA_TYPE
Device Default Capacity NSR_DEV_DEFAULT_CAPACITY_MEDIA_TYPE
Device Tape Flags
None
When device parameters are set in this interface, it is not necessary to stop and restart
the NetWorker server in order for the settings to take effect.
Setting device environment variables on Windows
Setting environment variables for the NetWorker software differs on Windows and UNIX
operating systems.
Environment variables on Microsoft Windows are set using the Control Panel System
applet on the NetWorker server.
172
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Procedure
1. Browse to Control Panel > System and Security > System > Advanced System Settings.
2. In the General tab click Environment Variables...
3. Click New.
4. Specify the environment variable name and value.
5. Stop and start the NetWorker Backup and Recover Server service in order for the
environment variables to take effect.
Setting device environment variables on UNIX
Setting environment variables for the NetWorker software differs on Windows and UNIX
operating systems.
On UNIX and Linux NetWorker sources the /nsr/nsrrc file before starting the
NetWorker processes.
Procedure
1. On the NetWorker server, modify the /nsr/nsrrc file. If this file does not exist,
create this file as a Bourne shell script file.
2. Add the environment variables in the following format:
ENV_VAR_NAME = value
export ENV_VAR_NAME
3. Stop and start the NetWorker server processes in order for the environment variables
to take effect.
EMC Licensing Solution
NetWorker 9.0.x introduces the EMC Licensing Solution, a new EMC standard for licensing
in software products. The EMC Licensing Solution uses an EMC License Server and reads
a license file to determine which products are licensed and how much storage space to
request for each datazone in the environment.
All new installations of NetWorker 9.0.x use the EMC Licensing Solution. The chapter
"EMC Licensing Solution" in the EMC NetWorker Licensing Guide provides information on
how to implement the EMC Licensing Solution for new and upgraded installations of
NetWorker 9.0.x. The "EMC Licensing Solution" chapter also describes the new EMC
License Server and the use of the license file.
Setting the common device interface
The common device interface (CDI) allows the NetWorker server to send commands to
tape devices. The CDI feature is not supported within an NDMP environment. CDI support
can be set in the NetWorker Administration interface.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Select View > Diagnostic Mode.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Double-click a device in the Devices table (or right-click the device and select
Properties). The Properties window appears, with the General tab selected.
5. Select the Advanced tab. In the Device Configuration area, locate the CDI settings:
l
Not Used: Disables the CDI feature and uses standard tape driver calls for tape
operations.
l
SCSI Commands: Sends explicit SCSI commands to tape devices.
SCSI and VTL libraries
173
Backup Storage
When enabled, the CDI feature:
l
Provides clearer tape status messages.
l
Informs when a tape is write protected.
l
Enables Tape Alert, which provides diagnostic information for devices.
Although the CDI feature can be disabled through selecting the Not Used option, it
can be time-consuming to disable a large number of devices.
In this situation, access the /nsr/debug directory and create a file named
cdidisable. Then restart the NetWorker server. This file does not need any content, it
just needs to exist. This disables the use of CDI for that server and all storage nodes
controlled by that server.
Note
Use of CDI does not change what is written to tape. A tape written with CDI enabled
can be read with CDI disabled. Conversely, a tape written with CDI disabled can be
read with CDI enabled. The CDI feature enables NetWorker software to collect better
diagnostic information and facilitates tape usage when enabled. Only set or disable
the CDI feature on the advice of an EMC Customer Support representative. If tape or
SCSI issues occur while the CDI feature is enabled, go to the EMC online support.
Media handling errors
The architecture of device drivers can produce media handling errors. The NetWorker
software automatically retries a failed operation such as a mount or read of a volume. The
number of times the NetWorker software retries the failed operation depends on the
value of the Max Consecutive Errors attribute, which is set in the Advanced tab of the
device’s Properties window. The default value is 20. When the device’s Max Consecutive
Errors value is reached, the device stops retrying the operation and becomes disabled.
A mount or read operation might fail for several reasons, for example:
l
Attempts to mount and read a damaged tape in a library can result in a loop of failed
actions: the device might repeatedly try to mount the tape, replace it in the slot, and
then retry the action with the same result. In this example, to bring the drive back into
use, remove the damaged tape, then reenable the device.
l
A drive that always reports a fixed number of failures before correctly mounting and
reading a tape, even if the tape is not damaged, can cause a failure loop. In this
example, ensure that the Max Consecutive Errors value is higher than the number of
times that particular drive fails before working correctly.
Re-enabling a device
Once the number of retries equals the Max Consecutive Errors value, the device becomes
disabled. After the problem that disabled the device has been fixed, the device (drive)
must be reenabled before it can be used again.
Procedure
1. When the NetWorker computer is idle, remove any volume from the disabled drive and
ensure that the drive is in good working order.
2. In the Administration window, click Devices. The Devices detail table appears.
3. Right-click the drive to be reenabled, and select Properties. The Properties window
appears.
4. In the Status area of the General tab, set Enabled to Yes.
5. Click OK.
174
EMC NetWorker 9.0.x Administration Guide
Backup Storage
1. If the disabled drive is part of a library, it might be necessary to reset the device. To do
this:
6. From the command prompt, change the path to the directory that contains the
NetWorker binaries.
7. Type this command:
nsrjb -HE
NOTICE
A device retains it enabled or disabled status in the Properties window and in the
Devices detail table regardless of whether its storage node is enabled or disabled.
Therefore, it is possible that the storage node Properties window is set to disabled
while its devices appear to be enabled in the GUI.
Silo libraries
This section describes silos and silo devices. Silos and libraries are managed similarly by
NetWorker software.
A silo tape library (STL) is a peripheral that usually contains many storage devices.
Silos libraries have a robotic controller that moves tape media between slots and
devices. Silos do not use a SCSI interface to access and control the media movements.
Media movements are controlled by a separate host that is called the silo server. The silo
server uses silo management software to manage media movement requests over the
network. The silo vendor provides the silo management software. The silo server cannot
be the same computer as the NetWorker server.
The silo can be shared among many applications, systems, and platforms. As with
libraries, silos make data and media operations more automatic. Silos can load, change,
and manage volumes, and clean the devices automatically.
NetWorker only supports silos that use the Automated Cartridge System Library Software
(ACSLS) Manager software.
NetWorker software interactions with a silo
A NetWorker server acts as a client of the silo management software, which resides on
the silo server. The NetWorker server communicates with the silo through the Silo Tape
Library Interface (STLI), which must be installed on the NetWorker server that uses the
silo.
To access the volumes and devices in a silo, the NetWorker server sends a request to the
silo management software, in the form of an STLI call. For example, to mount a volume in
a silo device, the NetWorker media service sends a request to the silo management
software to mount the volume into a particular device in the silo. The silo server responds
to the request and mounts the volume in the requested device.
The silo management software controls many of the operations that NetWorker software
controls with a library. For example, the silo management software keeps track of the slot
where each silo volume resides, and might control the deposit and withdrawal of
volumes, as well as automated cleaning of silo devices.
Naming conventions for silo devices
The silo name of the storage devices is supplied during the configuration process. The
silo name is the name that the silo management software uses to refer to the storage
Silo libraries
175
Backup Storage
device. Depending on the type of silo, the device name can take several forms. This
section describes the naming conventions of the currently supported silos.
StorageTek device naming conventions
The StorageTek (STK) silo management software uses either a program that is called
ACSLS that runs on a UNIX system, or a program that is called Library Attach that runs on
a Multiple Virtual Storage (MVS) system. These programs name devices according to a
coordinate system based on the physical location of the devices in the silo. When you
configure the silo in NetWorker, you supply the name of the silo that the silo management
software uses to refer to the storage device.
For tape drives, the name consists of four digits that are separated by commas:
l
The first digit refers to the automated cartridge system (ACS) with which the drive is
associated.
l
The second digit refers to the library storage module (LSM) in which the drive is
located.
l
The third and fourth digits refer to the panel and slot location in which the drive is
located.
A typical name for an STK drive is similar to: 1,0,1,0.
You cannot determine the drive names from the NetWorker software. Contact the silo
administrator for the drive names of the devices that the NetWorker server can use. To
connect to more than one drive, determine the SCSI IDs for each drive and correctly
match the IDs to the silo names. If the operating system device names and silo names are
accidentally swapped, NetWorker can only mount and unmount volumes. NetWorker
cannot read or write to the volumes after they are mounted. To reconfigure the device
names correctly, modify the Library resource in the Administration window and change
the order of the device names in the STL Device Names attribute.
Installing a silo
Procedure
1. Install the silo management software on the silo server.
2. If required, install the STLI library on the NetWorker server. For more information, refer
to the documentation from the silo vendor.
For example, for a NetWorker server or storage node running Windows to control an
STK silo, the libattach program must be installed.
On UNIX systems, do not install the STLI library because all the necessary software is
installed when the NetWorker software is installed.
3. Ensure that the NetWorker server is properly connected to the media devices in the
silo.
4. Add the silo. Configuring silo libraries on page 176 provides further details.
Configuring silo libraries
Procedure
1. In the server’s Administration interface, click Devices.
2. Open the Storage Nodes folder in the navigation tree.
3. Right-click the storage node to which the device is to be configured, and select
Configure All Libraries (which is available from many of the menus throughout the
Devices task). This action opens a wizard that can configure all detected libraries,
176
EMC NetWorker 9.0.x Administration Guide
Backup Storage
except those libraries that are explicitly excluded in the library exclusion list during
configuration.
Note
If Configure All Libraries is started from the server folder instead of from the Storage
Node folder, then all storage nodes on the NetWorker server are automatically
selected for configuration in the wizard.
The Configure All Libraries wizard appears, and allows the user to step through library
configuration, including the following input (some of which is filled in by default):
l
Library type (select STL Silo).
l
Adjust the Enable New Device option, if required.
l
Current server sharing policy (use maximal sharing with Dynamic Drive Sharing
[DDS]).
l
Storage nodes on which the libraries should configure. You can select a storage
node to see its details that are displayed. If the appropriate storage node is not
listed, click Create a New Storage Node.
When creating a storage node, replace the default value in the Name field with the
name of the new storage node:
a. Update storage node properties, if required.
b. Type the Silo Controller count, which sets the number of silos to be configured for
the selected storage node. The default is 1. If a silo count of greater than one is
selected, then a library name and hostname must be typed for each one.
c. Type the Hostname of the silo controller.
d. (Optional) Use the Test Silo Controller Connectivity button to see whether the
connection to a silo controller works. Use it once for each silo. If the connection to
a given silo fails, an error message appears.
4. Click Start Configuration after filling in the requested information. The Configuration
window displays a message that the Configure All Libraries process has started, and
that the configuration activity can be viewed by checking the Monitoring > Log screen
for status.
5. Click Finish on the Configuration window to close the configuration wizard. If
problems occur during configuration, then the Back button on the Configuration
window becomes active, which allows the user to return to the input screen to adjust
input.
NetWorker software with ACSLS silos
In this section, the term “ACSLS server” refers to the name of the system that is running
any one of StorageTek's library manager programs.
The ssi program is used indirectly by the nsrjb program to communicate with an ACSLS
server. The nsrjb program loads libstlstk, which handles the TCP calls to and from the ssi
program. The ssi program then handles all of communication to and from the ACSLS
server. Starting with ACSLS version 5.3, it is possible to run either a NetWorker server or
storage node on the same host that is running ACSLS.
To configure a library, the ssi and mini_el programs must be running on the system on
which library configuration is performed. The ssi and mini_el programs are generally run
as background processes, and are usually started automatically by the system.
Silo libraries
177
Backup Storage
In addition to the ssi and mini_el programs, a shared library file (usually called
libstlstk.xxx where xxx is an operating system-dependent extension) is also required. An
appropriate version of this library is installed as part of NetWorker installation.
ACSLS silos and firewalls
With ssi version 2.0, communication with the ACSLS server on a specified port number is
supported, using the -a command line option. This is part of the STK firewall
enhancement. The ACSLS version 7 must be running on the ACSLS server to use this
functionality.
The UNIX man pages for these commands, or see the EMC NetWorker Command Reference
Guide provides information on the ssi and mini_el programs.
Releasing a silo device
When a silo device is configured for use with a NetWorker server, it is possible to restrict
silo access only to the NetWorker server. These restrictions allow increased availability to
the silo for those with full access. These restrictions can be lifted by using the Release
Device feature.
Procedure
1. In the Administration window, click Devices.
2. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
3. Select a silo in the navigation tree or double-click a silo in the Libraries detail table to
open the double-paned Library Operations view. The silo’s drives are listed in the
Device column. The slots are listed in the Slot column.
4. Right-click a silo in the Slot column, and select Release Device. A window appears
and asks whether to release devices.
5. Click Yes. The Library Operation window appears and displays this message:
The library operation has started.
Please see the Monitoring->Operations screen for its status.
6. Click OK.
7. Repeat all steps for each device to be released.
Silo device cleaning
Do not enable automated cleaning for silos in the NetWorker software. The automated
device cleaning feature depends on fixed slot numbers, so it cannot be used in a silo,
which does not have fixed slot numbers. For information about how to clean devices in a
silo, refer to the ACSLS silo manufacturer’s software documentation.
Environment variables for StorageTek silos
Environment variables must be set for StorageTek silos. The following table lists the
environment variables to set.
Table 35 StorageTek environment variables
Silo model Environment variables
StorageTek
For UNIX systems:
l
CSI_HOSTNAME = name_of_ACSLS_system
The following commands should also be running on the system and can be
in the NetWorker startup script:
178
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Table 35 StorageTek environment variables (continued)
Silo model Environment variables
l
<binaries_path>/mini_el &
l
<binaries_path>/ssi &
For Windows systems:
The LibAttach Configurator program is available from StorageTek. It creates a
ssi process, and a link is available to start the mini_el process from
Start > Programs > LibAttach menu tree.
Once installed and configured, it starts on restart.
Setting environment variables for UNIX systems
Procedure
1. Create a Bourne shell script file named/nsr/nsrrc on the NetWorker server if it
does not already exist.
2. Add the variables in this format:
ENV_VAR_NAME = value
export ENV_VAR_NAME
3. Stop and start the NetWorker server daemons in order for the environment variables
to take effect.
Media management in a silo
More than one software application can use a single silo. Therefore, media management
in a silo requires extra operations to prevent the NetWorker software from overwriting
volumes used by other programs.
Silo slot numbering
In a library, the NetWorker software specifies many functions by slot number. A library
has a fixed number of slots, and NetWorker software uses the slot number to refer to a
volume’s physical location.
A silo works similarly, but a silo has a variable number of slots, starting at zero when it is
first configured, and limited by the silo license purchased. The fundamental identifier of a
silo volume is its barcode, or volser (volume serial number). The volser never changes
over the life of a particular volume.
When the nsrjb command lists the contents of a silo, it also lists a slot number. Use the
slot number to specify which volumes to mount, unmount, label, and inventory. Volumes
are not always assigned the same slot number in the silo. The slot numbers in the silo are
assigned dynamically, based on the sorted order of the barcodes that have been
allocated. If additional barcodes that fall earlier in the sort sequence are allocated later,
then the slot numbers change for all volumes that are later in the sequence.
The nsrjb UNIX man page or the EMC NetWorker Command Reference Guide provide more
information.
Silo libraries
179
Backup Storage
Silo volume mounting and unmounting
The mount and unmount operations for silos are the same as for library volumes.
Consider the following when mounting and unmounting library volumes:
l
A volume must be mounted before it can be labeled, read, or had data written on it.
The robotic mechanism mounts volumes in the devices of a silo.
l
Volumes must be unmounted before they can be inventoried in a silo or removed
from a NetWorker pool.
Volume mounting and unmounting on page 157 provides more information.
Silo volume labeling
The NetWorker labels for volumes in a silo include both a regular NetWorker volume label
(written on the media of the volume) and a silo barcode identifier. The volume label is
usually based on the volume pool’s label template. The barcode identifier is written on a
physical label on the outside of the volume, which the barcode reader in the silo can scan
during inventory. Labeling volumes on page 150 and Barcode labels on page 152 provide
instructions on how to label silo volumes.
The use of barcodes with matching barcode labels and NetWorker volume labels, are
both available for a silo. The Barcode Reader attribute must be selected, however the
Match Barcode Labels attribute is optional. When both attributes are selected, the
internal volume label that NetWorker software writes on the media of each volume will
match the barcode label on the outside of the volume. When the labels match, it is easier
to track volumes. But the NetWorker software does not require the internal and external
labels to match.
With most silo management software, unlabeled volumes can be used. The silo
management software assigns a “virtual” barcode label to those volumes. Although
volumes can be used without barcodes, it is difficult to maintain integrity, since once the
volume has been removed from the silo, the information about the virtual barcode is lost.
Any volume without an actual barcode can be reinserted into the silo under a virtual
barcode that NetWorker software (or another application) associates with some of the
data.
Using silos with volume import and export capability
NetWorker software supports the use of the import/export feature that is found in many
brands of silos. Depending on the silo model, this feature is also known as CAP, mail slot,
and loading port. The import/export feature deposits and withdraws volumes from slots
in the silo.
The import/export feature enables the operator to deposit and withdraw cartridges
without invalidating the device inventory list. If the operator opens the door to load or
unload volumes, the element status of the autoloader is invalidated, requiring the timeconsuming operation of reinitializing the silo. Note, however, that NetWorker software
does not automatically inventory the volume after a deposit.
Either the NetWorker software or the silo management software can be used to control
the import/export feature on the supported silos to deposit and withdraw volumes in a
silo. But it is often more efficient to use the silo management software, especially to
deposit or withdraw many volumes.
If the import/export feature is set to automatic mode, the silo management software
inserts volumes automatically and the NetWorker software cannot be used to insert
volumes.
To issue deposit and withdraw commands:
180
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
To add and deposit volumes, type: nsrjb -a -T tags -d
l
To remove and eject/withdraw volumes, type: nsrjb -x -T tags -w
where tags specifies the tags or barcodes of volumes in a remote silo.
NOTICE
You cannot deposit a volume from the CAP (I/O Port) using the nsrjb -d command. A
silo volume deposit requires the -T and -a options in sequence to add a volume in the
media database.
The sequence of operations is: nsrjb -d -T Barcode.
Ignore the error message that appears. nsrjb -a -T Barcode.
Barcode IDs
A list of available barcode-labeled volumes is available from the silo management
software. Refer to the silo manufacturer’s documentation for how to generate the list of
barcode IDs.
To specify a barcode identifier or template for the volumes from a command prompt, use
the -T option with the nsrjb command. The nsrjb UNIX man page or the EMC NetWorker
Command Reference Guide provides more information.
Silo volume allocation
When volumes are added, the NetWorker server is directed to the volumes it can use.
NOTICE
Because silos can be used by more than one software application, it is possible that a
different application could read or write to volumes that belong to the NetWorker
software. To prevent this from happening, most silo management software includes
methods to limit access to volumes based on the hostname of the computer on which
various programs run. The NetWorker software does not provide a method for setting up
this sort of protection. The silo management software must configure it.
The addition of a volume causes the NetWorker software to query the silo management
software to verify that the requested volume exists.
If the volume exists, the volume is allocated to the NetWorker software.
Adding a silo volume
Procedure
1. In the Administration window, click Devices.
2. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
3. Double-click a silo in the Libraries detail table to open the double-paned library
operations view. The silo’s drives are listed in the Device column, and its slots are
listed in the Slot column.
4. Right-click a silo in the Device column, and select Add. The Add Library Volumes
window appears, with the option to select either Template or List for barcode
selection.
5. Select either Template or List to enter barcode volume identifiers.
l
The Template option allows the use of wildcards in creating a list of barcode IDs.
Each entry should be on a separate line; for example, to name four tapes A01B,
A02B, A03B, and A04B, type:
A0
1-4
B
Silo libraries
181
Backup Storage
l
The List option allows the entry of barcode IDs, separately. Each entry should be
on a separate line; for example, type the name for each tape:
A01B
A02B
A03B
A04B
6. Type the appropriate volume identifiers in the Barcodes field.
7. Click OK (or Cancel, to continue adding to the list).
l
Click "+" to add an entry.
l
Click "<-" to insert above a highlighted selection.
l
Click "-" to delete an entry.
The Library Operation window displays this message:
The library operation has started.
The Monitoring > Operations screen displays its status.
8. Click OK. On return to the Library detail table, the added volumes will be shown.
Inventory silos
Taking inventory of the volumes in a silo ensures that the mapping between slot number
and volume name is correct, or reconciles the actual volumes in a silo with the volumes
listed in the NetWorker media database.
The slot number of a silo volume is not a numbered slot inside the silo, as it is in a
library. The slot number of a silo volume is the number of the volume’s position in the list
of volumes in a silo.
The tasks for inventorying volumes in a silo are the same as those for a library.
Inventorying library volumes on page 162 provides information about inventorying a
library.
The NetWorker software examines all of the volumes in the silo and compares the new list
of volumes to the NetWorker media database. Then the NetWorker software produces a
message listing any volumes located in the silo that are not in the media database.
When the NetWorker software inventories a silo, the silo’s barcode label reader reads the
barcode labels on the outside of each volume. When a barcode matches an entry in the
NetWorker media database, the volume does not need to be loaded. The inventory
proceeds rapidly. If, however, the NetWorker software reads a barcode that does not
match any of the entries in the media database, the volume must be mounted and read in
order for a proper inventory to be taken.
Troubleshooting a silo
If the particular silo model does not automatically deposit the volume, then place the
volumes in the insert area, right-click the volume, and select Deposit.
To perform the Deposit and Add operations from a command prompt:
l
On silos that require manual depositing, type nsrjb -a -T tags -d
l
On silos where the silo management software deposits volumes automatically, such
as StorageTek silos, type nsrjb -a -T tags where tags specifies the tags
or barcodes of volumes in a remote silo. The -d flag performs the
manual deposit.
NetWorker software interactions with a silo on page 175 provides more information on
STLIs.
182
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Deallocating (removing) silo volumes
When an STL volume in a silo is no longer needed, the volume can be deallocated from
the silo. Deallocation is basically the same operation as removing a volume from a
library. Although the volume cannot be loaded by the robotic mechanism, the entries in
the NetWorker media database remain intact. If the volume is allocated again, NetWorker
software can retrieve the data from it later.
Use deallocation when the silo license limits the number of usable slots, or when data is
moved offsite for safer storage. When the license limits the number of slots, it might be
possible to leave the volumes in the silo, if it is certain that the volumes will not be used
by another application. That way, the volumes can easily be added again when the data
on them must be accessible.
The allocation operation is not automatic. The volumes must be manually allocated again
and reinventoried to let the NetWorker server access the data. If the volume is to be
removed from the silo for offsite storage, it must be removed with NetWorker software
and then ejected from the silo by using the silo management software.
Procedure
1. Unmount the volume from the device. Volume mounting and unmounting on page 157
provides instructions on unmounting volumes.
2. In the Administration window, click Devices.
3. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
4. Double-click a silo in the Libraries detail table to open the double-paned library
operations view. The silo’s drives are listed in the Device column.
5. Right-click a silo in the Device column, and select Remove.
The Remove Library Volumes window appears, with the option to select either
Template or List for barcode selection.
6. Select either Template or List to enter barcode volume identifiers.
l
The Template option allows the use of wildcards in creating a list of barcode IDs.
For example, to name four tapes A01B, A02B, A03B, and A04B, type A0, 1-4, and
B.
l
The List option allows the entry of barcode IDs, separately. For example, type the
name for each tape: A01B, A02B, A03B, and A04B.
7. Type the appropriate volume identifiers in the Barcodes field.
8. Click OK.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays the silo’s status.
9. Click OK. Notice that on return to the Libraries detail table, the removed volumes are
no longer listed.
Results
NetWorker software interactions with a silo on page 175 provides information on STLs.
NDMP libraries
NDMP libraries or devices are accessed by using the NDMP protocol and are typically
used by network attached storage (NAS) systems. These devices do not allow direct
NDMP libraries
183
Backup Storage
access to control from the host operating system. Control and data movement is
performed over the network by using the NDMP protocol.
The NDMP guide provides more information.
NetWorker hosts with shared libraries
The NetWorker software permits different NetWorker hosts (a NetWorker server or storage
node) within a datazone to control individual devices within a library. This is known as
library sharing.
The presence of a SAN within the datazone is not required for library sharing.
Dynamic Drive Sharing (DDS) does not support sharing libraries across datazones.
How library sharing works
Library sharing enables one NetWorker host to control the library’s robotic arm, while
other NetWorker hosts (as well as the host controlling the robotic arm) can each control
and use specific library devices. A specific device can be controlled only by a single
NetWorker host. The following figure shows how multiple NetWorker hosts can share
library devices.
Figure 11 How library sharing works
Library task inactivity periods
Library resources include attributes that are used by older, slower libraries that specify
the number of seconds a library is inactive after certain operations (such as loading,
unloading, or ejecting a volume). For example, once a tape is loaded, the library must
read and, possibly, reposition the tape before the next operation can begin. This period
of delay is known as sleeping.
While sleeping, the library cannot receive or perform other operations. Without the sleep
period, the loading or unloading of volumes might fail.
The NetWorker software automatically configures default sleep periods. Change these
values only when troubleshooting a library’s performance, or if a NetWorker technical
support specialist requests it. Typically, the higher the sleep values specified in the
attributes, the longer it takes the library to perform the task. Be cautious when changing
these values.
The sleep attributes and their default values are shown in this table.
184
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Table 36 Library resource sleep attributes
Attribute
Description
Default
value
Load Sleep
Number of seconds that the NetWorker software waits for a
library to complete loading a cartridge.
15 seconds
Unload Sleep
Number of seconds that the NetWorker software waits for a
library to complete unloading a cartridge.
60 seconds
Eject Sleep
Number of seconds that the NetWorker software waits for an
eject operation to complete.
60 seconds
Deposit Timeout Number of seconds for a library to wait for a tape to be
deposited in the mail slot before it times out.
15 seconds
Withdraw
Timeout
Number of seconds for a library to wait for a tape to be
withdrawn from the mail slot before it times out.
15 seconds
Cleaning Delay
Number of seconds that the NetWorker software waits between 60 seconds
the completion of a drive cleaning operation and the ejection
of the cleaning cartridge from the drive.
Idle Device
Timeout
The number of minutes NetWorker allows a device with a
volume to be idle before automatically unmounting it. For
specific devices, this value can be overridden. Unmounting
volumes automatically (idle device timeout) on page 157
provides more information.
10 minutes
Port Polling
Period
Number of seconds for a library to wait before polling a mail
slot to check for the updated status.
3 seconds
Server Network Interface attribute
The Server Network Interface attributes in the Device resource are used to determine the
network address or the hostname used by the nsrmmd program to communicate with the
NetWorker server. Similarly, the Server Network Interface attribute in the Library resource
is used to determine the network address or the hostname used by the nsrlcpd
program to communicate with the NetWorker server. These attributes are displayed in the
NetWorker Console in diagnostic mode only. The Server Network Interface attributes are
only relevant if the device or library is connected to a storage node.
Note
For devices, the nsrmmd program will read the Server Network Interface value for the first
enabled device from the list of storage node devices, and each subsequent nsrmmd
started by the NetWorker server will use the same value. Therefore, the NetWorker server
will always use the same Server Network Interface value for every nsrmmd it starts or
restarts, regardless of whether or not the Server Network Interface attribute is different for
each device.
NetWorker hosts with shared libraries
185
Backup Storage
Dynamic drive sharing
Dynamic Drive Sharing (DDS) is a feature that provides NetWorker software with the
ability to recognize shared physical tape drives. DDS enables NetWorker software to
perform the following operations:
l
Skip the shared tape drives that are in use.
l
Route the backups or recoveries to other available shared tape drives.
Introduction to DDS
DDS controls application requests for tape media and allows the NetWorker server and all
storage nodes to access and share all attached devices.
A system administrator can configure DDS by setting a sharing policy for devices that are
accessible from multiple storage nodes.
There are two terms that are central to the use of DDS are drive and device. Within the
context of DDS, these terms are defined as follows:
l
Drive—The physical backup object, such as a tape drive, disk, or file.
l
Device—The access path to the physical drive.
Note
NetWorker only supports DDS in a storage area network (SAN) Fibre Channel
environment and not in a direct-connect SCSI environment.
Benefits of DDS
Enabling DDS on a NetWorker system provides these benefits:
186
l
Reduces storage costs—You can share a single tape drive among several storage
nodes. In fact, since NetWorker software uses the same open tape format for UNIX,
Windows, NetWare and Linux, you can share the same tape between different
platforms (assuming that respective save sets belong to the same pool).
l
Reduces LAN traffic—You can configure clients as SAN storage nodes that can send
save sets over the SAN to shared drives.
l
Provides fault tolerance—Within a SAN environment, you can configure hardware to
eliminate a single point of failure.
l
Provides configuration over a greater distance—You can configure a system over a
greater distance than with SCSI connections.
EMC NetWorker 9.0.x Administration Guide
Backup Storage
DDS configuration overview
The following figure illustrates the DDS process and potential device sharing
configurations. This basic configuration consists of a server, two storage nodes, and a
library with two tape drives.
Figure 12 Dynamic Drive Sharing
In this figure:
l
Storage nodes sn_1 and sn_2 are attached to the library.
l
Each storage node, on its own, has access to drive_1 and drive_2.
l
With DDS enabled, both storage nodes have access to both drives and can recognize
when a shared drive is in use.
This configuration requires two DDS licenses, one for each drive.
Note
Ensure that all applicable devices can be seen from each storage node by running the
inquire -l command locally on each storage node.
DDS block-size compatibility between UNIX and Windows
With DDS enabled, drives can be shared between storage nodes on different platforms,
such as UNIX and Microsoft Windows. For NetWorker software operations (such as
backups and recoveries) to take place successfully, ensure that the block size is
compatible between different platforms and/or hardware.
To ensure compatibility, make sure one of the following conditions is met:
l
The various storage nodes sharing a drive support the same block sizes.
l
When a tape is labeled on a drive, it is labeled with the block size defined on the
storage nodes.
Dynamic drive sharing
187
Backup Storage
Block-size incompatibility between UNIX and Windows
Incompatible block-size settings between UNIX and Microsoft Windows storage nodes
could result in any of these error scenarios:
l
A backup taken on a UNIX node might not be recoverable on a Microsoft Windows
node if the Windows node does not support large block sizes.
l
A UNIX process labels and saves data to a tape and leaves the tape mounted. A
Microsoft Windows process subsequently attempts to verify the label on this tape
and fails because the label verification is done by reading a header from the data
portion.
l
A tape on a UNIX node is labeled with a large block size. The backup is started on a
Microsoft Windows node and the Windows node attempts to write the backup by
using the default block size. Internally, the backup on Windows is written by breaking
down the big buffer of data into smaller segments of writable block sizes.
Attempting to recover a specific file on Windows in this situation fails due to
positioning errors on the tape. The data is still recoverable from the Windows side,
since the NetWorker software will switch from using file and block positioning to
reading the tape from the beginning to reach the correct position. The data might not,
however, be recoverable from the UNIX side.
Unintended Access to DDS device prevention
The Reserve/Release attribute has been added to the Device resource for tape devices to
support Reserve/Release, including the Persistent Reserve commands.
Reserve/Release is a mechanism that uses SCSI commands to attempt to prevent
unintended access to tape drives that are connected by using a shared-access
technology, such as Fibre Channel, iSCSI, or SCSI multiplexers. It is a “cooperative” and
host-based mechanism, which means that all applications should respect the
reservations and not purposely break them. Access is granted based on the host system
that reserved the device. Other applications that run on that host cannot be prevented
from accessing a reserved device.
Reserve/Release cannot prevent a malicious or badly behaved application from
accessing a reserved device. It also cannot prevent all problems caused by hardware
issues (such as SCSI resets or FC LIPs) from interrupting data access.
The basic sequence requires that a host reserve a tape drive (using specific SCSI
commands) before attempting to access the tape drive. If this “reservation” succeeds,
then the host can use the drive. If the reservation fails (usually because the device is
reserved by someone else), then the host attempting the reservation should not attempt
to use the drive. When a host has finished using a reserved drive, that host must release
the drive by using the appropriate SCSI commands.
The reservation is maintained by the drive itself. With older (called “Simple” in NetWorker
software) Reserve/Release, the reservation is based on the SCSI ID of the system that
issued the reserve command. For tape drives connected to Fibre Channel (FC) using FCSCSI bridges, the mapping between FC host and reservation is done inside the bridge,
since the initiator on the SCSI side is always the bridge itself, regardless which host
actually issued the reserve command.
For Persistent Reserve, the reservation is associated with a 64-bit “key” that is registered
by the host. Several keys can be registered with a given drive at any given time, but only
one may hold the active reservation. NetWorker software uses the “exclusive” reservation
method for Persistent Reserve. Only the host that holds the active reservation is allowed
to access the drive.
The Reserve/Release attribute does not support file type or advanced file type devices.
188
EMC NetWorker 9.0.x Administration Guide
Backup Storage
The settings that relate to Reserve/Release and Persistent Reserve are found in a device’s
Properties window, on the Advanced tab. They are visible only when diagnostic mode is
turned on.
The default setting for Reserve/Release is None. Once any other Reserve/Release setting
is selected, it works automatically, without further user intervention. The Reserve/
Release attribute is supported only on Common Device Interface (CDI) platforms, so if the
CDI attribute in a device’s Properties is set to Not Used, then Reserve/Release settings
are ignored.
For newer hardware, once a Reserve/Release setting (other than None) has been
selected, the appropriate Persistent Reserve commands are automatically issued before
a device is opened for reading or writing, and before the device is closed. With older
hardware, a SCSI-2 Reserve command is issued before opening the device, and a SCSI-2
Release command is issued after the device is closed.
Reserve/Release has these possible settings:
l
None (the default)
l
Simple
l
Persistent Reserve
l
Persistent Reserve + APTPL (Activate Persist Through Power Loss)
The Persistent Reserve Key attribute has also been added. It is used with Persistent
Reservation calls.
Restrictions for use of the SCSI Reserve/Release setting
There are restrictions for using the SCSI Reserve or Release setting.
Consider the following:
l
It is available on CDI platforms only. Consequently, since CDI is not supported within
an NDMP environment, Reserve/Release is not supported with NDMP.
l
Not all drives support persistent Reserve/Release. (All drives support at least simple
reserve release. The code automatically drops back from Persistent +APTPL or
Persistent to Simple on drives that do not support Persistent.)
l
SCSI resets can clear Simple reservations at the device.
l
Even with Reserve/Release, there is no guarantee against data loss.
l
If the operating system has its own Reserve/Release feature, that feature must be
disabled in order for the NetWorker Reserve/Release feature to work.
l
Even if all of the enterprise’s NetWorker storage nodes have this feature enabled,
then it is possible that, on the storage node where a backup operation is run, data
loss can be caused by the operating system’s utilities or by third-party programs.
DDS attributes in the device properties
Configure the attributes that DDS uses, in the Properties window for a device.
The attributes include:
l
Hardware ID
l
Shared Devices
Hardware ID attribute
The Hardware ID attribute tracks the drives that are shared between multiple hosts.
Device instances that share the same physical drive across multiple hosts have the same
hardware ID. The device autoconfiguration process automatically assigns the Hardware ID
Dynamic drive sharing
189
Backup Storage
to a device, or it is added when manually configuring a device. Users cannot edit the
Hardware ID.
You can view the Hardware ID in the Properties window for a device, on the General tab,
in the Device Sharing area.
NetWorker generates the Hardware ID when a device is scanned or configured. The
Hardware ID consists of the following components:
l
l
l
l
Hardware serial number
Device type
Worldwide part number (WWPN)
Worldwide name (WWN)
Shared Devices attribute
The Shared Devices attribute appears on the Operations tab of a device’s Properties
window when in diagnostic mode. It features values that can be used to manipulate all
shared instances of a drive simultaneously. This attribute enables or disables all devices
that share the same Hardware ID with a single action. The following table lists allowed
values and descriptions for the attribute.
Table 37 Shared Devices attributes
Value
Description
Enable All
When selected, enables all devices with the same Hardware ID.
Disable All When selected, disables all the devices with the same Hardware ID.
Done
This value is the default setting. After the server has enabled or disabled all devices
with the same Hardware ID, the attribute value is reset to Done.
You cannot configure the Shared Devices attribute with the jbconfig program.
Idle Device Timeout attribute and DDS
A tape might remain mounted in a drive after a backup completes. Other requests for the
drive from another device path must wait during this timeout period. Use the Idle Device
Timeout attribute to adjust the timeout value.
The Idle Device Timeout attribute is not specifically a DDS attribute, but is useful in
configuring shared drives. This attribute appears on the device Properties window on the
Advanced tab when displayed in Diagnostic Mode. The default value is 0 (zero) minutes,
which means that the device never times out and you must manually eject the tape.
If the device belongs to a library, you can also specify the Idle Device Timeout value for all
devices in the library. However, the library value will take effect only on those devices
whose Idle Device Timeout value is 0. The Idle Device Timeout value for a library is
located on the Timer tab of the library Properties window.
Max active devices
In a DDS environment, use the Max active devices attribute, on the General tab of the
Storage Node resource to define the maximum number of active devices for a storage
node.
This attribute sets the maximum number of devices that NetWorker may use from the
storage node in a DDS configuration. In large environments with media libraries that have
a large number of devices, storage nodes might not have the ability to optimize all the
drives in the library. The Max active devices attribute allows you to limit the number of
devices that the storage node uses at a specified time, which allows the storage node to
190
EMC NetWorker 9.0.x Administration Guide
Backup Storage
have access to all the devices in the library, but does not limit the storage node to the
number of devices it can fully optimize.
File type devices
File type devices (FTDs) are legacy devices and their use is limited. Continued support for
legacy and test purposes is maintained, however you are encouraged to use AFTD or DD
Boost devices in preference to FTD. An FTD can be configured on the NetWorker server by
creating a new Device resource in the same manner as for other storage devices.
The following conditions and restrictions apply to FTDs:
l
The upper limit of save set size on an FTD may be either:
n
The upper limits supported by the operating system
n
The file size specified by the disk device vendor
l
If multiple FTDs are configured on a system, each device must have a unique name.
l
To use multiple FTDs on the same disk, partition the disk and create only one FTD per
partition.
l
Dynamic Drive Sharing isnot supported.
l
For FTDs created on a UNIX or Linux network file system (NFS):
n
The file system used for the FTD must not be used for any other data.
n
There must be one FTD per NFS system.
n
The Volume Default Capacity attribute for the FTD must be set to a size that is less
than 100 percent of the total capacity of the file system.
NOTICE
Data loss will result if a full FTD is made appendable while a backup is pending
completion and a save set is partially written to the full FTD. In this case, the
partial save set (currently in “incomplete” state) will be overwritten.
FTD capacity issues
For FTDs, the Volume Default Capacity is a hard limit on the amount of data that can be
written to the device. The Volume Default Capacity value is an estimate of what the
volume capacity is likely to be. If the value is not set correctly, the NetWorker percentused calculation will be incorrect.
Note
By contrast, AFTDs ignore the Volume Default Capacity value to allow dynamic expansion
of disk space.
The Volume Default Capacity attribute displays on the Configuration tab of the Device
properties when Diagnostic Mode (View > Diagnostic Mode) is enabled:
l
To avoid accidentally filling an FTD, set the Volume Default Capacity attribute to
restrict the size of the device. For example, if a capacity of 100 MB is set, then the
device will be marked full when 100 MB is reached.
l
Volume Default Capacity attribute must not be set to a value of more than 4 TB.
l
If the Volume Default Capacity of a volume changes, the changes do not take effect
until the FTD is re-created, the directory contents are deleted, and the volume is
relabeled.
File type devices
191
Backup Storage
NOTICE
If the FTD is used before the Volume Default Capacity attribute is set, then the legacy
data on that FTD must be staged or cloned to another device. Otherwise, this data will
be overwritten.
Full FTD prevention
To prevent the file system from becoming full when backing up data to FTDs, policies can
be used to move the data off the disk as soon as necessary. Save sets from FTDs can be
staged or cloned to an AFTD to take advantage of advanced file type device features.
To make space for additional backups:
l
Configure a save set staging policy. Staging save sets on page 428 provides details.
l
Review and, if required, modify the retention policy of the save sets.
Stand-alone devices
A Device resource must be created for each stand-alone tape device on a storage node.
Stand-alone drives must be configured individually.
Storage nodes must have been created before devices can be configured to be used by
them. Storage nodes on page 91 provides information about storage nodes and how to
create them. Note that all scanning for devices is done at the storage node level, and can
be done across multiple storage nodes. Only devices that have serial numbers can be
autoconfigured. Use the jbconfig command to configure devices that do not have
serial numbers.
Note
Devices must be updated to the most recent firmware and drivers.
Autodetecting and configuring a stand-alone tape drive
You can configure a new stand-alone tape drive, automatically by using Scan for Devices.
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Right-click Devices in the navigation tree, and select Scan for Devices to detect
available devices. The Scan for Devices window appears.
3. Click Start Scan.
4. Check the scan status by clicking the Monitoring button and selecting the Log tab.
Then return to the Devices navigation tree.
5. Select either the Devices folder or the Storage Nodes folder in the navigation tree. All
detected drives are listed. Any still-unconfigured drives are preceded by a circular icon
that displays a wrench.
6. Right-click the stand-alone drive to be configured, and select Configure Drive. A
Configuration dialog box appears.
7. Click Yes to confirm that the drive should be configured. The new drive is
automatically configured.
192
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Adding a stand-alone device manually
Procedure
1. In the server’s NetWorker Administration interface, click Devices.
2. Right-click Devices in the navigation tree, and select New. The Create Device window
appears, with the General tab selected, and a default device path in the Name field of
the Identity area of the window.
3. Replace the default name with the path and name of the device:
a. If the device is configured on the server’s storage node, the name is the simple
device path, such as /tmp/d0 for a file type device. A tape device on Windows
would have a format similar to \\.\Tape0.
b. If the device is configured on a remote storage node, then the name must indicate
that the storage node is remote by including rd= and the name of the remote
storage node in the device path. For example, if the remote storage node is
neptune, then the device path might be rd=neptune:/tmp/d0 or
rd=neptune:\\.\Tape0.
File type devices on page 191 provides instructions and restrictions on backing up
to a file type device.
4. In the Identity area, configure the following:
a. In the Comment field, add an optional, descriptive comment.
b. In the Media Type field, select a media type.
5. In the Status area, configure the applicable checkboxes:
l
Read Only
l
Auto Media Management
6. In the Cleaning area, configure the applicable fields:
l
Cleaning Required
l
Cleaning Interval
The Date Last Cleaned is filled in automatically once a drive has been cleaned.
7. Select the Configuration tab to set attributes, such as:
l
Target Sessions
l
Max Sessions
l
Local Backup to a dedicated storage node
NDMP settings (NDMP remote username and password are required for an NDMP
device that acts as a storage node.)
8. Click OK when the configuration is complete.
Auto Media Management for stand-alone devices
The Auto Media Management feature can be enabled for stand-alone devices during
manual device configuration, or from the Properties window after configuration.
When Auto Media Management is enabled for a stand-alone device, the following
processes occur when a volume becomes full during a backup:
Adding a stand-alone device manually
193
Backup Storage
l
A notification is sent that indicates that the server or storage node is waiting for a
writable volume. Simultaneously, the NetWorker server waits for the full, verified
volume to be unmounted.
l
The device is monitored and the software waits for another volume to be inserted into
the device.
l
After a volume is detected, a check is performed to determine whether the volume is
labeled. If so:
n
The volume is mounted into the device.
n
The NetWorker server checks to see whether the newly mounted volume is a
candidate to receive data:
1. If yes, the write operation continues.
2. If no, the NetWorker server continues to wait for a writable volume to continue
the backup.
l
If the volume is recyclable and is a member of the required pool, it is recycled the
next time a writable volume is needed.
l
If the volume is unlabeled, it is labeled when the next writable volume is needed for a
save. Note that Auto media management does not label disk type devices such as
AFTD and Data Domain.
NOTICE
If a partially full volume is unmounted, the NetWorker server automatically ejects the
volume after a few seconds. If a stand-alone device is shared between storage nodes,
then Auto Media Management should not be enabled for more than one instance of
the device. Enabling Auto Media Management for more than one instance of the
stand-alone device will tie up the device indefinitely. No data is sent to the device
and no pending message is sent.
Mounting or unmounting a volume in a stand-alone tape drive
Procedure
1. Manually insert a volume in the stand-alone drive, or ensure that a volume is already
loaded.
In a stand-alone device, a volume that has been loaded into the drive is not
considered to be mounted until it has been explicitly mounted in the user interface or
from the command prompt.
2. In the Administration window, click Devices.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Select the device. To mount the volume, in the Devices detail table, right-click the
device, and select Mount.
5. To unmount the volume, in the Devices > detail table, right-click the device, and select
Unmount.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
6. Click OK.
194
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Labeling and mounting a volume in one operation (stand-alone tape drive)
When multiple storage devices are connected to the NetWorker server, the device for
labeling must first be selected from the list of available devices. Remember that labeling
a volume makes it impossible for the NetWorker server to recover original data from that
volume.
Procedure
1. In the Administration window, click Devices.
2. Manually insert an unlabeled or recyclable volume in the NetWorker server storage
device, or ensure that a volume of this type is already present for the NetWorker server
to access.
3. Select Devices in the navigation tree. The Devices detail table appears.
4. Right-click the stand-alone device in the detail table, and select Label. The Label
window appears:
a. Type a unique label name, or accept the default name that is associated with the
selected pool.
If the volume is unlabeled, the NetWorker server assigns the next sequential label
from the label template that is associated with the selected pool. If a recyclable
volume from the same pool is being re-labeled, then the volume label name and
sequence number remain the same. Access to the original data on the volume is
destroyed, and the volume becomes available.
b. Select a pool on the Pools menu. The NetWorker server automatically applies the
label template that is associated with the Default pool unless a different pool is
selected.
c. Select the Manual Recycle attribute if the volume should be manually recycled.
If the Manual Recycle attribute is enabled when the volume is labeled, the volume
cannot automatically be marked as recyclable according to the retention policy.
When a volume is marked as manual recycle, the NetWorker server disregards the
assigned browse and retention policies. Therefore, only an administrator can mark
the volume recyclable.
A volume that has been set to manual recycle retains that setting, even after relabeling. A Manual Recycle policy cannot be changed back to Auto Recycle by
clearing the Manual Recycle checkbox. The volume must be explicitly reset to use
auto recycle.
d. The Mount After Labeling attribute is selected by default. The NetWorker server
automatically labels the volume, and then mounts the volume into the device.
5. Click OK.
6. If the volume is recyclable, a message warns that the named volume is about to be
recycled, and asks whether to continue. Click Yes to re-label and recycle the volume.
7. After a volume is labeled and mounted in a device, the volume is available to receive
data. Since the NetWorker label is internal and machine-readable, place an adhesive
label on each volume that matches that internal volume label.
Configuring a library to use volumes with barcodes on page 147 provides information
on using barcode labels.
Labeling and mounting a volume in one operation (stand-alone tape drive)
195
Backup Storage
Note
If you are in the process of re-labeling a mounted volume and you choose not to
overwrite the existing label, the volume is left in an unmounted state. To use this
volume, mount it again.
Labeling volumes without mounting
Volumes can be prelabeled without being mounted.
To label a volume without mounting, follow the same procedures as for labeling and
mounting in one operation, but clear the Mount After Labeling attribute in the Label
window.
Mounting uninventoried volumes
You can mount volumes that are not included in the library inventory, but are valid
(properly labelled) NetWorker volumes.
Procedure
1. In the Administration window, click Devices.
2. Select View > Diagnostic Mode on the toolbar.
3. Manually insert the volume in an empty library slot.
4. Open the Libraries folder in the navigation tree. The Libraries detail table appears.
5. Select the library in the navigation tree in which the volume was manually inserted, or
double-click the same library in the Libraries detail table. The Libraries detail table
changes to the double-paned library operations view. The library’s drives are listed in
the Devices column, and its slots are listed in the Slot column.
6. In the Devices column, right-click the library in which the volume was manually
inserted, and select Inventory. The Inventory Library window appears.
7. Type the slot number of the volume in both the First and Last field of the Slot Range.
8. Select Operation Type: either Slow/Verbose (the default) or Fast/Silent.
l
When Slow/Verbose is selected, the Supply Input option and icon on the
Operations screen of the Monitoring window can be used to confirm the choice to
relabel a volume. The device path appears in the Device field.
l
When Fast/Silent is selected, the Supply Input option and icon are not available,
and relabeling proceeds automatically, without user input. The device path does
not appear in the Device field. Entering user input on page 56 provides details.
9. Click OK.
l
The Library Operation window displays this message:
The library operation has started.
l
The Monitoring > Operations screen displays its status.
The NetWorker software then inventories the specified slot.
10. Mount the inventoried volume.
196
EMC NetWorker 9.0.x Administration Guide
Backup Storage
NOTICE
Unlabeled tapes may not be mounted for inventorying. Unlabeled tapes can only be
mounted to be labeled. An attempt to mount an uninventoried volume by using
unlabeled media results in an I/O error. The volume will also be ejected.
Labeling volumes
The NetWorker software applies a label template to create a unique internal label for each
volume. The label corresponds to a pool and identifies the pool for the volume during
backup and other operations.
Several preconfigured label templates are supplied with the NetWorker software. You
cannot delete these preconfigured label templates. Naming label templates on page 73
provides more information.
When you label a volume, the labeling process:
l
Writes a label on the volume.
l
Adds the volume label to the media database.
l
Prepares tape media to have data written to it.
When you re-label tape, the data on the tape is effectively gone.
During data recovery, the server requests the volume that contains the required data,
identifying the required volume by the name with which it was labeled.
Labeling or re-labeling library volumes
Labeling volumes in a library is time-consuming, so consider labeling volumes before it is
time to back up or recover files. When a volume is re-labeled, that volume is initialized
and becomes available for writing again.
Procedure
1. In the Administration window, click Devices.
2. In the left pane, select Libraries.
A list of libraries appears in the right pane.
3. Right-click the library and select Label.
Details for the selected library appear, including divided tables for devices and slots.
The Label Library Media dialog box also appears.
4. From the Target Media Pool list, select the pool for the volume.
The pool determines the label template that is used to label the volume.
5. To require manual recycling of the volume, select Allow > Manual Recycle.
With manual recycling, the volume is not automatically marked as recyclable when all
save sets expire. You must manually mark the volume as recyclable.
NOTICE
A volume that has been set to manual recycle retains that setting, even after the
volume is re-labeled. You must explicitly reset the volume to automatic recycle by
right-clicking the volume in the Media window, selecting Recycle, and then selecting
the Auto option.
Labeling volumes
197
Backup Storage
6. To be prompted before the existing label is overwritten, select Prompt to overwrite
label.
7. Click OK.
The Library Operation dialog box appears, stating that the library operation has
started.
8. To track the status of the label operation, click Monitoring in the Administration
window.
9. If you selected Prompt to overwrite label, confirm the overwrite of the existing volume
label with a new label:
a. Right-click the label operation in the Monitoring window and select Supply Input.
A confirmation message appears.
b. Click Yes.
Verifying the label when a volume is unloaded
If a SCSI reset is issued during a backup, the volume rewinds and NetWorker may
overwrite the volume label.
To detect if the label is overwritten in this circumstance, select the Verify label on eject
checkbox in the Device resource, or set the Verify label on unload setting in the Jukebox
resource to Yes. With these settings, NetWorker verifies that a volume label exists before
ejecting the volume. If the volume label cannot be read, all save sets on the volume are
marked as suspect and the volume is marked as full.
Troubleshooting devices and autochangers
This section explains how to resolve problems with devices and autochangers.
NOTICE
Do not edit device files and directories, this can result in unpredictable behavior and
make it impossible to recover data.
Additional attributes in the Autochanger resource
The Autochanger resource contains attributes that provide a detailed view of the hidden
options that the nsrjb program uses. Displaying diagnostic mode attributes on page
783 provides information about how to display hidden attributes.
The EMC NetWorker Command Reference Guide and the UNIX man pages provide
information about these attributes.
NOTICE
Do not change time related attributes unless advised to do so by a Technical Support
representative.
198
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Maintenance commands
NetWorker device driver software provides maintenance commands, such as lusbinfo
and lusdebug, that you can use to diagnose problems on tape devices and
autochangers.
The EMC NetWorker Command Reference Guide or the UNIX man pages provide information
about how to use these commands.
Autodetected SCSI jukebox option causes server to stop responding
If you use the jbconfig command to create an autodetected SCSI jukebox and the
server stops responding, perform the following steps.
1. Start the jbconfig program
2. Select the option that installs an SJI jukebox.
3. Type the number that corresponds to the type of jukebox you are installing.
4. Continue with jbconfig until this message appears:
Jukebox has been added successfully.
Autochanger inventory problems
This section provides an overview of the situations that can result in an outdated
autochanger inventory of volumes and how to update the inventory. When the jukebox
inventory becomes outdated, the NetWorker software cannot use the autochanger.
The autochanger inventory can become out of date when:
l
You manually eject the media from the autochanger drive.
l
You manually remove the media is from the autochanger.
l
You open the autochanger door.
To update the inventory and enable the NetWorker software to use the autochanger
again, perform the following steps.
1. Verify that the volume is correctly installed in the autochanger and that the
autochanger door is closed.
2. Log in as root or administrator on the NetWorker server.
3. Reset the autochanger:
nsrjb -Hv
4. Inventory: the autochanger:
nsrjb -Iv
The EMC NetWorker Command Reference Guide or the UNIX man pages provide complete
details on the nsrjb command.
Destination component full messages
When you perform a manual operation on an autochanger, for example when you use the
buttons on the autochanger to unload the tape drive instead of unloading the tape drive
by using NetWorker operations, a message similar to the following may appear:
Destination component full
Maintenance commands
199
Backup Storage
To resolve the problem, use the nsrjb -H command to reset the autochanger.
Tapes do not fill to capacity
The data stored on a tapes may not always fill the tape to capacity. For example, the
NetWorker server can mark a tape with an advertised capacity of 4,000 MB full, after
writing only 3,000 MB of data.
To enable NetWorker to use the maximum tape capacity, select the highest density
device driver for the device. Additional reasons that the server appears to fill tapes
prematurely include:
l
Write errors occur during a backup. With any tape error, the NetWorker server marks
the tape as full. To prevent tape write errors, clean the tape drive regularly and use
only data-quality tapes. If cleaning the drive does not help, ensure that you perform
the following actions:
n
Confirm the configuration of the device driver.
n
Set any necessary switch settings on the tape drive, based on the manufacturer
specifications.
n
Confirm that all cables are secure.
n
Address other potential SCSI problems.
l
Space requirements for NetWorker to create file marks. The NetWorker server
periodically writes file marks to facilitate rapid recovery of data. These file marks
consume varying amounts of tape space, depending on the type of tape drive. The
number of file marks the server writes to the tape depends on how many save sets
are on the tape. Many small save sets require more file marks than a few larger ones.
l
Tape capacity differences. Two apparently identical tapes from the same vendor can
vary significantly in capacity. This can cause problems when you copy one full tape to
another, especially if the destination tape holds less data than the source tape.
l
Data compression affects the tape capacity. If you use compression on the tape drive,
you cannot predict the effect on tape capacity. A compressing drive can provide twice
the capacity of a non-compressing drive. Tape capacity can vary depending on the
type of backup data. For example, if a non-compressing drive writes 2 GB of data to a
specific tape, the compressing drive could write 10 GB, 2 GB, 5 GB, or some other
unpredictable amount of data.
l
Tape length. Verify the tape lengths, for example, a 120-meter DAT tape holds more
data than a 90-meter DAT tape.
Tapes get stuck in drive when labeling tapes on Linux Red Hat platform
When you label a tape in a DDS configuration on an RHEL NetWorker server, the tape may
become stuck in the drive and display the following error message:
unload failure-retrying 30 seconds
To resolve this issue, set the auto_lock setting attribute to “0” (Off) in the /etc/
stinit.def file for the following drive types:
200
l
Sony AIT-2 and AIT-3
l
IBM LTO Gen1
l
HP LTO Gen1
l
IBM LTO GEN2
EMC NetWorker 9.0.x Administration Guide
Backup Storage
l
IBM 3580 drive LTO-1
l
IBM 3592 J1A
l
Quantum DLT 7000
By default the auto_lock setting is set to 1 (On).
Increasing the value of Save Mount Time-out for label operations
A label operation initiated by a backup operation may take more than 30 minutes before
it fails when the Auto media management option is enabled and the label operation
encounters a corrupted tape.
The NetWorker software keeps a record of the location of the corrupted tape only for the
current backup operation, and NetWorker can attempt to use a corrupted tape for the
other backup operation, unless an operator removes the volume.
To modify the time it takes the label operation timeout, modify the Save Mount Time-out
attribute for the storage node. Configuring timeouts for storage node remote devices on
page 94 describes how to modify the attribute.
Server cannot access autochanger control port
The control port controls the autochanger loading mechanism. The autochanger hardware
installation manual contains information about how to verify the that control port is
properly connected.
If you cannot determine that the control port is working, contact the autochanger vendor
for assistance.
Modifying the control port
When a change in the control port of the robotic arm of a library occurs, NetWorker may
not be able to perform library operations, such as labeling, mounting, and unmounting,
and inventorying. You may see the error no such file or directory when
NetWorker tries to perform library operations.
To update the NetWorker server or storage node to use the new control port, perform the
following steps.
Procedure
1. Run the inquire command to determine the SCSI device address of the library arm
and to confirm that a serial number is reported.
NOTICE
Use the inquire command with caution. The inquire command sends the SCSI
inquiry command to all devices detected on the SCSI bus. If you use inquire during
normal operations, unforeseen errors and possible data loss may result.
l
If inquire reports the serial number of the arm, follow the procedure at Scanning
for libraries and devices on page 145 to scan the library for devices, then enable
the library in NMC:
a. In the Administration window, click Devices.
b. Expand the Libraries folder, then right-click the library and select Enabled/
Disable.
Increasing the value of Save Mount Time-out for label operations
201
Backup Storage
l
If inquire does not report the serial number or if the scan for devices operation
does not detect the control port change, use the nsradmin command to change
the control port:
a. Log in as root or as Windows administrator on the NetWorker host that
manages the control port.
b. At the command prompt, type nsradmin The nsradmin prompt appears.
c. To disable the library, type the following commands:
type: NSR jukebox
update enabled: no
d. When nsradmin prompts you to update the resource, type yes.
e. To update the control port, type:
update control port: scsidev@b.t.l
where b.t.l is the bus.target.lun of the library’s robotic arm (as reported by the
inquire command).
f. When nsradmin prompts you to update the resource, type yes.
g. To re-enable the library, type:
update enabled: yes
h. When nsradmin prompts you to update the resource, type yes.
i. To verify that the control port was changed and the library is now enabled, type
print at the nsradmin prompt.
Changing the sleep times required for TZ89 drive types
When you unload a volume from a TZ89 tape device you may receive an error message
similar to the following and NetWorker will repeatedly try to unload the tape:
nsrd: media info: unload retry for jukebox `COMPAQTL895' failed
- will retry again.
To resolve this issue, changes the sleep attributes in the Autochanger resource.
1. Shut down NetWorker services.
2. Shut down and restart the autochanger that contains the TZ89 drives.
3. When the autochanger is back online, restart NetWorker services. NetWorker will not
try to unload the drive again.
4. Use NMC to edit the following autochanger sleep time attributes, and use the
following values:
l
Eject Sleep: 18 secs
l
Unload Sleep: 40 secs
l
Load Sleep: 40 secs
Additional attributes in the Autochanger resource on page 198 provides
information about how to set the sleep attributes.
5. Try to unload the drive again. If the drive fails to unload, repeat this procedure and
increase the sleep times.
202
EMC NetWorker 9.0.x Administration Guide
Backup Storage
Message displayed when CDI enabled on NDMP or file type device
If you enable the CDI feature for an NDMP tape device or file type device (FTD), a message
similar to the following appears:
nsrd: media notice: The CDI attribute for device "/dev/rmt/
3cbn" has been changed to "Not used".
To avoid this message, do not enable the CDI attribute for these device types.
Verify firmware for switches and routers
Ensure that the switches or routers firmware that you use on the network was
manufactured after August 1995. Most of the switch and router vendors have significantly
improved their handling of RPC traffic since August 1995.
Commands issued with nsrjb on a multi-NIC host fail
When you run nsrjb commands to manage a jukebox on a NetWorker server or storage
node that has multiple network interface cards (NIC), the commands may fail.
To prevent this failure, add the domain name of each additional NIC to the Aliases
attribute in the Client resource for the NetWorker server or storage node. Editing a Client
resource on page 405 describes how to edit a Client resource.
SCSI reserve/release with dynamic drive sharing
When the NetWorker software uses Dynamic Drive Sharing (DDS) the operating system
tape driver might use the SCSI reserve/release feature in a manner that interferes with
the proper operations of the NetWorker software. To resolve this issue, disable the
reserve/release feature.
Solaris
The st.conf file contains a setting for each device type in use that enables or disables
the SCSI reserve/release feature. The Tape Configuration section of the st man page
provides more information. Use the most up-to-date st driver that is available for the
version of Solaris.
Edit the st.conf file only if one of the following conditions apply:
l
The NetWorker configuration includes DDS.
l
Solaris st does not support a tape drive that is configured on a Solaris host.
To determine if the Solaris st tape driver supports a tape drive, perform the following
steps:
1. Use the mt command to load a tape in the drive. For example, with the tape device
file 0cbn, the type: mt -f /dev/rmt/0cbn status
l
If the output of the mt command includes the line SCSI tape drive or appears
similar to the following, the st tape driver uses generic settings, which do not
support the tape drive:
mt -f /dev/rmt/4cbn status
Vendor 'IBM ' Product 'ULT3580-TD2 ' tape drive:
sense key(0x6)= Unit Attention residual= 0
retries= 0 file no= 0 block no= 0
Message displayed when CDI enabled on NDMP or file type device
203
Backup Storage
Tape operations may appear to work in NetWorker but you may run into problems
when you try to recover saved data.
l
If the output of the mt command appears similar to the following, the st tape
driver recognizes the drive and uses the correct internal settings to manage the
drive:
mt -f /dev/rmt/0cbn status
HP Ultrium LTO tape drive:
sense key(0x0)= No Additional Sense residual= 0
retries= 0 file no= 0 block no= 0
In this configuration, you must only edit the st.conf file when you use the drive
in a DDS configuration.
AIX
To reset the reserve/release setting on an AIX operating system, use the SMIT interface.
1. From the Devices menu, select Tapes.
2. Change the value for the RESERVE/RELEASE support attribute from No to Yes.
HP-UX
To reset the reserve/release setting on an HP-UX 11 operating system, perform the
following steps.
1. Change the st_ats_enable kernel variable to a value other than zero.
2. (Optional) Restart the computer to ensure that the operating system implements the
change.
Note
The reserve/release is a fixed setting in HP-UX 10.
Recovering save sets from a VTL on a different NetWorker server
The following procedure describes the steps that you need to perform before you can
load a tape that was in a VTL managed by one NetWorker server into a different
NetWorker server.
Before you begin
Ensure the destination VTL is the same model, has the same drive names and the same
number of drives as the original VTL.
Procedure
1. Confirm the inventory of the VTL in the destination NetWorker storage node
2. Run the inquire command to determine the Control port of the VTL on the destination
NetWorker storage node.
3. Run the sjimm command to load the tape into a drive on the destination NetWorker
server.
4. Use the mt command to ensure that the tape status is online. For example: mt -f
device_name status
When the mt comamnd reports that the tape drive is online, you can use the
scanner command to scan the save set information into the media database and
client file index of the destination NetWorker server.
204
EMC NetWorker 9.0.x Administration Guide
CHAPTER 4
Data Protection Policies
This chapter contains the following topics:
l
l
l
l
l
l
l
l
l
l
Overview of data protection policies....................................................................206
Designing data protection policies...................................................................... 207
Policy notifications..............................................................................................263
Monitoring policy activity.................................................................................... 263
Policy log files..................................................................................................... 265
Starting, stopping, and restarting data protection policies...................................267
Starting actions in a workflow for an individual client.......................................... 267
Modifying data protection Policy resources......................................................... 268
Managing policies from the command prompt.....................................................281
Troubleshooting policies..................................................................................... 289
Data Protection Policies
205
Data Protection Policies
Overview of data protection policies
Data protection policy is a concept that provides you with the ability to design a data
protection solution for the environment at the data level instead of at the host level. With
a data protection policy, each client in the environment is a backup object and not simply
a host.
Data protection policies enable you to back up and manage data in a variety of
environments, as well as to perform system maintenance tasks on the NetWorker server.
A data protection policy solution encompasses the configuration of the following key
NetWorker resources:
Policies
Policies provide you with the ability to develop a service-catalogue approach to the
configuration of a NetWorker datazone. Policies enable you to manage all data protection
tasks and the data protection lifecycle from a central location.
Policies provide an organizational container for the workflows, actions, and groups that
support and define the backup, management, and system maintenance actions that you
want to perform.
Workflows
Workflows define the start time for a series of actions, the frequency in which the actions
run, the order of actions in a sequence, and the protection group to which the workflow
applies.
A workflow can be as simple as a single action that applies to a finite list of Client
resources, or a complex chain of actions that apply to a dynamically changing list of
resources. In a workflow, some actions can be set to occur sequentially, and others can
occur concurrently.
You can create multiple workflows in a single policy. However, each workflow can belong
to only one policy. When you add multiple workflows to the same policy, you can logically
group data protection activities with similar service level provisions together, to provide
easier configuration, access, and task execution.
Protection groups
Protection groups define a set of static or dynamic Client resources or save sets to which
a workflow applies. There are also dedicated protection groups for backups in a VMware
environment or for snapshot backups on a NAS device. Review the following information
about protection groups:
l
Create one protection group for each workflow. Each group can be assigned to only
one workflow.
l
You can add the same Client resources and save sets to more than one group at a
time.
l
You can create the group before you create the workflow, or you can create the group
after you create the workflow and then assign the group to the workflow later.
Actions
Actions are the key resources in a workflow for a data protection policy and define a
specific task, for example, a backup, clone, or snapshot. NetWorker uses a work list to
the define task. A work list is composed of one or several work items. Work items include
client resources, virtual machines, save sets, or tags. You can chain multiple actions
together to occur sequentially or concurrently in a workflow. All chained actions use the
same work list.
When you configure an action, you define the days on which to perform the action, as
well as other settings specific to the action. For example, you can specify a destination
206
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
pool, a retention period, and a target storage node for the backup action, which can differ
from the subsequent action that clones the data.
You can create multiple actions for a single workflow. However, each action applies to a
single workflow and policy.
The following figure provides a high level overview of the components that make up a
data protection policy in a datazone.
Figure 13 Data Protection Policy
Designing data protection policies
Designing and developing effective data protection policies requires thoughtful analysis
of the client resources from which to back up data, the actions to perform on the data,
and the order and timing of the actions.
Data protection policies can be grouped into six main strategies:
l
Traditional backups—Includes file system backups, NDMP backups, NMDA backups,
NMM backups, and Block Based Backups. The EMC NetWorker Network Data
Management Protocol (NDMP) User Guide provides detailed information about how to
backup, clone, and recover NDMP data. The NMM and NMDA documentation provides
information about how to backup, clone, and recover application data.
l
NetWorker and NMC Server database backups and maintenance activities—Performs
NetWorker server bootstrap and NMC database backups.
l
Snapshot backups—Includes snapshot backups of supported EMC storage arrays or
appliances. You can clone data after a snapshot backup completes or concurrently.
The EMC NetWorker Snapshot Management Integration Guide describes how to
configure data protection policies for EMC storage arrays and appliances with the
NetWorker Snapshot Management feature.
l
NAS device backups—Includes file system snapshots, and NAS snapshots. You can
clone data after a snapshot backup job completes or concurrently. The EMC NetWorker
Snapshot Management Integration Guide describes how to configure data protection
policies for snapshot backups.
l
VMware backups—Includes VMware Backup Appliance (VBA) backups, VBA
checkpoint backups for disaster recovery, and Virtual Machine (VM) backups. The
EMC NetWorker VMware Integration Guide describes how to configure data protection
policies for VBA, VBA checkpoint, and VM backups and clones.
l
Cloning- You can configure data protection policies that clone backup data by
querying the media database for a list of save sets that are based on user defined
criteria.
Designing data protection policies
207
Data Protection Policies
Note
You can also clone traditional, snapshot, bootstrap, and VMware backup data
concurrently with the backup operation, or after the backup operation completes. The
Integration Guides provide detailed information about how to clone Snapshot and
VMware backup data.
Default data protection policies
NetWorker provides you with preconfigured data protection polices resources that you
can use immediately to protect your environment, modify to suit your environment, or use
an example to create new resource configurations. To use these policy resources, you
must add clients to the appropriate group resource.
Each protection policy provides an example of the EMC best practices that you should
follow when you design your data protection solution:
l
Separate file system backups from application database backups, to provide ease of
access at recovery time.
l
Stagger the start times for file system backup from the application database backups,
to prevent disk contention on the target hosts.
The default data protection policy resources mimic the requirements of a service
provider, with different policies to that are designed to provide protection based on
service level agreements.
Platinum policy
The Platinum policy provides you with an example of a data protection policy for an
environment that contains EMC storage arrays or appliances and requires backup data
redundancy. The policy contains one workflow with two actions, a snapshot backup
action, followed by a clone action.
Figure 14 Platinum policy configuration
Gold policy
The Gold policy provides an example of a data protection policy for an environment that
contains virtual machines and requires backup data redundancy. The policy contains two
workflows, one to protect Hyper-V hosts and one to protect VMware hosts. Each workflow
contains a backup action followed by a clone action.
Figure 15 Gold policy configuration
208
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Silver policy
The Silver policy provides an example of a data protection policy for an environment that
contains non-virtualized machines and requires backup data redundancy. The policy
contains two workflows, one to protect hosts file systems and one to protect database
applications. Each workflow contains a backup action followed by a clone action.
Figure 16 Silver policy configuration
Bronze policy
The Bronze policy provides an example of a data protection policy for an environment
that contains non-virtualized machines. The policy contains two workflows, one to protect
hosts file systems and one to protect database applications. Each workflow contains a
backup action.
Figure 17 Bronze policy configuration
Road map for configuring a new data protection policy
Procedure
1. Create a policy.
When you create a policy, you specify the name and notification settings for the
policy.
2. Within the policy, create a workflow for each data type.
For example, create one workflow to protect file system data and one workflow to
protect application data. When you create a workflow, you specify the name of the
workflow, the time to start the workflow, notification settings for the workflow, and the
protection group to which the workflow applies.
3. Create a protection group.
The type of group that you create depends on the types of clients and data that you
want to protect. The actions that appear for a group depend on the group type.
4. Create one or more actions for the workflow.
Road map for configuring a new data protection policy
209
Data Protection Policies
5. To define the backup data that you want to protect, configure Client resources, and
then assign the client resources to a protection group.
The following figure illustrates a policy with two different workflows. Workflow 1 performs
a probe and then a backup of the Client resources in Client group 1, and then clones the
save sets from the backups. Workflow 2 performs a backup of the Client resources in
Dynamic client group 1, and then clones the save sets from the backups.
Figure 18 Data protection policy example
NetWorker resource considerations
When you create NetWorker workflow and action resources, consider the following
recommendations:
l
The parallelism value for the action resource should not exceed 25.
l
The total number of clients in a single workflow should not exceed 100.
Strategies for traditional backups
The primary considerations for a traditional backup strategy are the groups of Client
resources, the workflows that define the series of actions that are associated with the
backup, and the schedule for the backup.
Creating a policy
Procedure
1. On the Administration window, click Protection.
2. In the expanded left pane, right-click Policies, and then select New.
The Create Policy dialog box appears.
210
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
3. On the General tab, in the Name field type a name for the policy.
The maximum number of characters for the policy name is 128.
Note
After you create a policy, the Name attribute is read-only.
4. In the Comment box, type a description for the policy.
5. From the Send Notifications list, select whether to send notifications for the policy:
l
To avoid sending notifications, select Never.
l
To send notifications with information about each successful and failed workflow
and action after all the actions in the policy complete, select On Completion.
l
To send a notification with information about each failed workflow and action after
all the actions in the policy complete, select On Failure.
6. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Windows, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
Strategies for traditional backups
211
Data Protection Policies
7. To specify the Restricted Data Zone (RDZ) for the policy, select the Restricted Data
Zones tab, and then select the RDZ from the list.
8. Click OK.
After you finish
Create the workflows and actions for the policy.
Creating a workflow in a new policy
A policy must contain one or more workflows.
Procedure
1. In the left pane of the Protection window, expand Policies, and then select the policy
that you created.
2. In the right pane of the Protection window, select Create a new workflow.
3. In the Name field, type the name of the workflow.
The maximum number of characters for the name of the group is 64.
4. In the Comment box, type a description for the workflow. The maximum number of
characters for the Comment field is 128.
5. From the Send Notifications list, select how to send notifications for the workflow:
l
To use the notification configuration that is defined in the policy resource to
determine when to send the notification, select Set at policy level.
l
To send notifications with information about each successful and failed workflow
and action, after all the actions in the workflow complete, select On Completion.
l
To send notifications with information about each failed workflow and action, after
all the actions in the workflow complete, select On Failure.
6. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
212
On Windows, type the following command:
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
7. In the Running group box, define when and how often the workflow runs.
a. To ensure that the actions contained in the workflow run when the policy or
workflow is started, in the Enabled box, leave the option selected. To prevent the
actions in the workflow from running when the policy or workflow that contains the
action is started, clear this option.
b. To ensure that the workflow starts at the time that is specified in the Start time
attribute, on the days that are defined in the action resource, in the AutoStart
Enabled box, leave the option selected. To prevent the workflow from running at
the time that is specified in the Start time attribute, clear this option.
c. To define the time to start the actions in the workflow, in the Start Time attribute,
use the spin boxes.
The default value is 9:00 P.M.
d. To define how frequently to repeat the actions that are defined in the workflow
over a 24 hour period, In the Interval attribute, use the spin boxes.
The default value is 24 hours, or once a day. When you select a value that is less
than 24 hours, the Interval End attribute appears. To define the last time to start a
workflow in a defined interval period, use the spin boxes .
e. To define the duration of time in which NetWorker can manually or automatically
restart a failed or canceled workflow, in the Restart Window attribute, use the spin
boxes.
If the restart window has elapsed, NetWorker considers the restart as a new run of
the workflow. NetWorker calculates the restart window from the start of the last
incomplete workflow. The default value is 24 hours.
For example, when you set the Start Time to 7:00 PM, the Interval to 1 hour, and the
Interval end time to 11:00 P.M., then the workflow automatically starts every hour
beginning at 7:00 P.M. and the last start time is 11:00 PM.
8. To create the workflow, click OK.
After you finish
Create the actions that will occur in the workflow, and then assign a group to the
workflow. If a workflow does not contain a group, a policy does not perform any actions.
Strategies for traditional backups
213
Data Protection Policies
Protection groups for traditional backups
Create protection groups for traditional backups, which identifies the Client resources to
back up.
You can create two types of protection groups for a traditional backup:
l
Basic client group—Defines a static list of Client resources to back up.
l
Dynamic client group—Specifies a dynamic list of Client resources to back up. A
dynamic client group automatically generates a list of Client resources that use client
tag which matches the client tag that is specified for the group.
Create multiple groups to perform different types of backups for different Client
resources, or to perform backups on different schedules. For example:
l
Create one group for backups of clients in the Accounting department, and another
group for backups of clients in the Marketing department.
l
Create one group for file system backups and one group for backups of Microsoft
Exchange data with the NetWorker Module for Microsoft.
l
Create one group for a workflow with backups actions that start at 11 p.m., and
another group for a workflow with backup actions that start at 2 a.m.
Note
A Client resource can belong to more than one group.
Creating a client group
Basic client groups define a static list of Client resources for a traditional backup, check
connectivity, or probe action.
Before you begin
Create the Client resources for the data to include in a protection group.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Groups, and then select New.
The Create Group dialog box appears, starting with the General tab.
3. In the Name attribute, type a name for the group.
The maximum number of characters for the group name is 64.
Note
After you create a group, the Name attribute is read-only.
4. From the Group Type list, leave the default selection of Clients.
5. In the Comment field, type a description of the group.
6. Select the workflow in which to assign the group from the Policy-Workflow list.
Note
You can also assign the group to a workflow when you create or edit a workflow.
7. (Optional) On the Restricted Datazones tab, to specify the Restricted Datazone (RDZ)
for the group, select the RDZ from the list.
214
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
8. Click OK.
After you finish
Create Client resources. The Client Configuration wizard and General tab on the Client
Properties dialog box properties page provide you with the ability to assign clients to a
protection group.
Creating a dynamic client group
Dynamic client groups prevent you from having to edit group settings when you add
Client resources to the NetWorker datazone. You can configure a dynamic group to
include all the clients on the NetWorker server or you can configure the dynamic group to
perform a query that generates a list of clients that is based on a matching tag value. A
tag is a string attribute that you define in a Client resource. When an action starts in a
workflow that is a member of a tagged dynamic protection group, the policy engine
dynamically generates a list of Client resources that match the tag attribute value.
Use dynamic client groups to specify a dynamic list of Client resources for a traditional
backup, probe, check connectivity, or server backup action.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Groups, and then select New.
The Create Group dialog box appears, starting with the General tab.
3. In the Name attribute, type a name for the group.
The maximum number of characters for the group name is 64.
Note
After you create a group, the Name attribute is read-only.
4. From the Group Type list, select Dynamic Clients.
5. In the Comment field, type a description of the group.
6. Select the workflow in which to assign the group from the Policy-Workflow list.
Note
You can also assign the group to a workflow when you create or edit a workflow.
7. (Optional) On the Restricted Datazones tab, to specify the Restricted Datazone (RDZ)
for the group, select the RDZ from the list.
8. Click OK.
After you finish
Create Client resources. The Client Configuration wizard and General tab on the Client
Properties dialog box properties page provide you with the ability to assign clients to a
protection group and define one or more tags.
Supported actions in traditional backup workflows
Traditional backup workflows can optionally include a probe or check connectivity action
before the backup, and a clone action either concurrently with or after the backup.
Probe
A probe action runs a user-defined script on a NetWorker client before the start of a
backup. A user-defined script is any program that passes a return code. If the return code
Strategies for traditional backups
215
Data Protection Policies
is 0 (zero), then a client backup is required. If the return code is 1, then a client backup is
not required.
Only a backup action can follow a probe action.
Check connectivity
A check connectivity action tests connectivity between clients and the NetWorker server
before a probe or backup action occurs. If the connectivity test fails, then the backup
does not occur on the client.
Traditional backup
A traditional backup is a scheduled backup of the save sets defined for the Client
resources in the assigned group. You must specify the destination storage node,
destination pool, the schedule (period and activity), and the retention period for the
backup.
Clone
A clone action creates a copy of one or more save sets. Cloning allows for secure offsite
storage, transfer of data from one location to another, and verification of backups.
You can configure a clone action to occur after a backup in a single workflow, or
simultaneously with a backup action in a single workflow. You can also use save set and
query groups to define a specific list of save sets to clone, in a separate workflow.
Actions sequences in traditional backup workflows
Workflows enable you to chain together multiple actions and run them sequentially or
concurrently.
A workflow for a traditional backup can optionally include a probe or check connectivity
action before the backup, and a clone action either concurrently with or after the backup.
The following sections provide details on supported actions that can follow the lead
action and other actions in a workflow.
All possible workflow actions for a traditional backup
The following figure illustrates the possible workflow actions that are associated with a
traditional backup.
Figure 19 All possible workflow actions for a traditional backup
Workflow path from a traditional backup action
The only action that can follow a traditional backup is a clone action.
Figure 20 Workflow path from a traditional backup action
216
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Creating a check connectivity action
A check connectivity action tests connectivity between clients and the NetWorker server,
usually before another action such as a backup occurs.
Before you begin
Create the policy and workflow that contain the action. The check connectivity action
should be the first action in the workflow.
Procedure
1. In the expanded left pane, select the workflow, and then perform one of the following
tasks in the right pane to start the Policy Action wizard:
l
If this is the first action in the workflow, select Create a new action.
l
If the workflow has other actions, right-click an empty area of the Actions pane,
and then select New.
The Specify the Action Information page appears.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
5. From the Action Type list, select Check Connectivity.
6. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
7. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
8. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
9. Click the icon on each day to specify whether to check connectivity with the client.
The following table provides details on the icons.
Table 38 Schedule icons
Icon
Label
Description
Execute Check connectivity on this day.
Strategies for traditional backups
217
Data Protection Policies
Table 38 Schedule icons (continued)
Icon
Label
Description
Skip
Do not check connectivity on this day.
To check connectivity every day, select Execute from the list, and then click Make All.
10. Click Next.
The Specify the Connectivity Options page appears.
11. Select the success criteria for the action:
l
To specify that the connectivity check is successful only if successful connectivity
is achieved with all clients in the assigned group, select the Succeed only after all
clients succeed checkbox.
l
To specify that the connectivity check is successful if connectivity is achieved with
one or more clients in the assigned group, clear the checkbox.
12. Click Next.
The Specify the Advanced Options page appears.
13. (Optional) Configure advanced options and schedule overrides.
Note
Although the Retries, Retry Delay, Inactivity Timeout, or the Send Notification options
appear, the Check Connectivity action does not support these options and ignores the
values.
14. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
Note
The Parallelism value should not exceed 25.
15. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
218
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
16. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
17. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
18. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
Select the day in the calendar, which changes the action task for the specific day.
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
19. Click Next.
The Action Configuration Summary page appears.
20. Review the settings that you specified for the action, and then click Configure.
After you finish
(Optional) Create one of the following actions to automatically occur after the check
connectivity action:
l
Probe
l
Traditional backup
Note
This option is not available for NAS snapshot backups.
l
Snapshot backup
Creating a probe action
A probe action runs a user-defined script on a NetWorker client before the start of a
backup. A user-defined script is any program that passes a return code. If the return code
is 0 (zero), then a client backup is required. If the return code is 1, then a client backup is
not required.
Before you begin
l
Create the Probe resource script on the clients that use the probe. Create a client
Probe resource on the NetWorker server, and then associate the client Probe resource
with the Client resource on the NetWorker server.
l
Create the policy and workflow that contain the action.
l
(Optional) Create a check connectivity action to precede the probe action in the
workflow. A check connectivity action is the only supported action that can precede a
probe action in a workflow.
Strategies for traditional backups
219
Data Protection Policies
Procedure
1. In the expanded left pane, select the workflow, and then perform one of the following
tasks in the right pane to start the Policy Action wizard:
l
If this is the first action in the workflow, select Create a new action.
l
If the workflow has other actions, right-click an empty area of the Actions pane,
and then select New.
The Specify the Action Information page appears.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
5. From the Action Type list, select Probe.
6. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
7. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
8. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
9. Click the icon on each day to specify whether to probe the client.
The following table provides details on the icons.
Table 39 Schedule icons
Icon
Label
Description
Execute Perform the probe on this day.
Skip
Do not perform a probe on this day.
To perform a probe every day, select Execute from the list, and then click Make All.
10. Click Next.
The Specify the Probe Options page appears.
220
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
11. Choose whether to start the subsequent backup action only after all probes succeed
by selecting or clearing the Start backup only after all probes succeed checkbox.
l
To start the backup only if all the probes associated with Client resources in the
assigned group succeed, select the checkbox.
l
To start the backup if any one of the probes are associated with a Client resource
in the assigned group succeed, clear the checkbox.
12. Click Next.
The Specify the Advanced Options page appears.
13. In the Retries box, specify the number of times that NetWorker should retry a failed
probe or backup action, before NetWorker considers the action as failed. When the
Retries value is 0, NetWorker will not retry a failed backup or probe action.
Note
The Retries option only applies to probe actions, and the backup actions for the
Traditional and Snapshot action types. When you specify a value for this option in
other actions, NetWorker ignores the values.
14. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed
backup or probe action. When the Retry Delay value is 0, NetWorker retries the failed
backup or probe action immediately.
Note
The Retry Delay option only applies to probe actions, and the backup actions for the
Traditional and Snapshot action types. When you specify a value for this option in
other actions, NetWorker ignores the values.
15. In the Inactivity Timeout field, specify the maximum number of minutes that a job run
by an action is allowed to fail to communicate back to the server.
If the job fails to respond within the timeout value, the server considers the job a
failure. If a job fails, NetWorker retries the job immediately. This ensures that no time
is lost due to failures.
Increase the timeout value if a backup consistently aborts due to inactivity. Inactivity
timeouts may occur for backups of large save sets, backups of save sets with large
sparse files, and incremental backups of many small static files.
Note
The Inactivity Timeout option only applies to probe actions, and the backup actions
for the Traditional and Snapshot action types. When you specify a value for this option
in other actions, NetWorker ignores the values.
16. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
Note
The Parallelism value should not exceed 25.
17. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
Strategies for traditional backups
221
Data Protection Policies
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
18. Leave the default selections for the Notification group box. NetWorker does not
support notifications for probe actions and ignores the values that are defined in the
attributes.
19. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
20. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
21. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
Select the day in the calendar, which changes the action task for the specific day.
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
22. Click Next.
The Action Configuration Summary page appears.
23. Review the settings that you specified for the action, and then click Configure.
Creating a traditional backup action
A traditional backup is a scheduled backup of the save sets defined for the Client
resources in the assigned group for the workflow.
Before you begin
222
l
Create the policy and workflow that contain the action.
l
(Optional) Create actions to precede the backup action in the workflow. Supported
actions that can precede a backup include:
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
n
Probe
n
Check connectivity
Procedure
1. In the expanded left pane, select the workflow, and then perform one of the following
tasks in the right pane to start the Policy Action wizard:
l
If this is the first action in the workflow, select Create a new action.
l
If the workflow has other actions, right-click an empty area of the Actions pane,
and then select New.
The Specify the Action Information page appears.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
5. From the Action Type list, select Backup.
6. From the secondary action list, select the backup type, for example, Traditional.
7. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
8. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
9. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
10. Click the icon on each day to specify the backup level to perform.
The following table provides details about the backup level that each icon represents.
Table 40 Schedule icons
Icon
Label
Description
Full
Perform a full backup on this day. Full backups include all files,
regardless of whether the files changed.
Incr
Perform an incremental backup on this day. Incremental backups
include files that have changed since the last backup of any type (full
or incremental).
Strategies for traditional backups
223
Data Protection Policies
Table 40 Schedule icons (continued)
Icon
Label
Description
Cumulative Incr Perform a cumulative incremental backup. Cumulative incremental
backups include files that have changed since the last full backup.
Logs Only
Perform a backup of only database transaction logs.
Synthetic Full
Perform a synthetic backup on this day. A synthetic full backup
includes all data that changed since the last full backup and
subsequent incremental backups to create a synthetic full backup.
Skip
Do not perform a backup on this day.
To perform the same type of backup on each day, select the backup type from the list
and click Make All.
11. Click Next.
The Specify the Backup Options page appears.
12. From the Destination Storage Node box, select the storage node with the devices on
which to store the backup data.
13. From the Destination Pool box, select the media pool in which to store the backup
data.
14. From the Retention boxes, specify the amount of time to retain the backup data.
After the retention period expires, the save set is removed from the client file index
and marked as recyclable in the media database during an expiration server
maintenance task.
15. From the Client Override Behavior box, specify how NetWorker uses certain client
configuration attributes that perform the same function as attributes in the Action
resource.
l
Client Can Override—The values in the Client resource for Schedule, Pool,
Retention policy, and the Storage Node attributes will take precedence over the
values that are defined in the equivalent Action resource attributes.
l
Client Can Not Override —The values in the Action resource for the Schedule,
Destination Pool, Destination Storage Node, and the Retention attributes take
precedence over the values that are defined in the equivalent Client resource
attributes.
l
Legacy Backup Rules—This value only appears in actions that are created by the
migration process. The updating process sets the Client Override Behavior for the
migrated backup actions to Legacy Backup Rules.
16. Click Next.
The Specify the Advanced Options page appears.
17. In the Retries box, specify the number of times that NetWorker should retry a failed
probe or backup action, before NetWorker considers the action as failed. When the
Retries value is 0, NetWorker will not retry a failed backup or probe action.
224
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Note
The Retries option only applies to probe actions, and the backup actions for the
Traditional and Snapshot action types. When you specify a value for this option in
other actions, NetWorker ignores the values.
18. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed
backup or probe action. When the Retry Delay value is 0, NetWorker retries the failed
backup or probe action immediately.
Note
The Retry Delay option only applies to probe actions, and the backup actions for the
Traditional and Snapshot action types. When you specify a value for this option in
other actions, NetWorker ignores the values.
19. In the Inactivity Timeout field, specify the maximum number of minutes that a job run
by an action is allowed to fail to communicate back to the server.
If the job fails to respond within the timeout value, the server considers the job a
failure. If a job fails, NetWorker retries the job immediately. This ensures that no time
is lost due to failures.
Increase the timeout value if a backup consistently aborts due to inactivity. Inactivity
timeouts may occur for backups of large save sets, backups of save sets with large
sparse files, and incremental backups of many small static files.
Note
The Inactivity Timeout option only applies to probe actions, and the backup actions
for the Traditional and Snapshot action types. When you specify a value for this option
in other actions, NetWorker ignores the values.
20. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
Note
The Parallelism value should not exceed 25.
21. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Strategies for traditional backups
225
Data Protection Policies
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
22. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
23. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
24. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
Select the day in the calendar, which changes the action task for the specific day.
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
25. From the Send Notifications list box, select whether to send notifications for the
action:
l
Select Set at policy level to use the notification configuration that is defined in the
Policy resource to send the notification.
l
Select On Completion to send a notification on completion of the action.
l
Select On Failure to send a notification only if the action fails to complete.
26. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
226
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
27. Click Next.
The Action Configuration Summary page appears.
28. Review the settings that you specified for the action, and then click Configure.
After you finish
(Optional) Create a clone action to automatically clone the save sets after the backup. A
clone action is the only supported action after a backup action in a workflow.
Creating a clone action
A clone action creates a copy of one or more save sets. Cloning allows for secure offsite
storage, the transfer of data from one location to another, and the verification of
backups.
Procedure
1. In the expanded left pane, select the workflow, and then perform one of the following
tasks in the right pane to start the Policy Action wizard:
l
If this is the first action in the workflow, select Create a new action.
l
If the workflow has other actions, right-click an empty area of the Actions pane,
and then select New.
The Specify the Action Information page appears.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
Strategies for traditional backups
227
Data Protection Policies
5. From the Action Type list, select Clone.
6. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
7. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
8. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
9. Click the icon on each day to specify whether to perform cloning.
The following table provides details on the icons.
Table 41 Schedule icons
Icon
Label
Description
Execute Perform cloning on this day.
Skip
Do not perform cloning on this day.
To perform cloning every day, select Execute from the list and click Make All.
10. Click Next.
The Specify the Clone Options page appears.
11. In the Data Movement group box, define the volumes and devices to which NetWorker
sends the clone data.
a. From the Destination Storage Node list, select the storage node with the devices
on which to store the cloned save sets.
b. In the Delete source save sets after clone completes, select the option to instruct
NetWorker to remove the source save set information from the client file index, and
to mark the save set as recyclable in the media database during a Server
expiration maintenance action. Clear this option to allow the source save sets to
expire based on the defined retention time.
c. From the Destination Pool list, select the target media pool for the cloned save
sets.
d. From the Retention list, specify the amount of time to retain the cloned save sets.
After the retention period expires, the save sets are marked as recyclable during an
expiration server maintenance task.
12. In the Filters group box, define the criteria that NetWorker uses to create the list of
eligible save sets to clone. The eligible save sets must match the requirements that
are defined in each filter. NetWorker provides the following filter options:
a. Time filter—Use the Time section to define the time range in which NetWorker
should inspect, when searching for eligible save sets to clone in the media
database. Use the spin boxes to specify the start of the time range and the end of
228
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
the time range. The Time filter list includes three options, which define how
NetWorker determines save set eligibility, based on the time criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes save sets whose save time is within
the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
l
Reject—The clone save set list does not include save sets whose save time is
within the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
b. Save Set filter—Use the Save Set section to instruct NetWorker to include or
exclude ProtectPoint and Snapshot save sets, when searching for eligible save
sets to clone in the media database. The Save Set filter list includes three options,
which define how NetWorker determines save set eligibility, based on the save set
criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes eligible ProtectPoint or Snapshot save
sets, when you also enable the ProtectPoint or Snapshot checkboxes.
l
Reject—The clone save set list does not include eligible ProtectPoint and
Snapshot save sets when you also enable the ProtectPoint and Snapshot
checkboxes.
c. Clients filter—Use the Client section to define a list of clients to include or exclude,
when NetWorker searches for eligible save sets to clone in the media database.
The Client list includes three options, which define how NetWorker determines
save set eligibility, based on the client criteria:
l
Do Not Filter—NetWorker inspects save sets that are associated with the clients
in the media database, to create a clone save set list that meets the filter
criteria.
l
Accept—The clone save set list includes eligible save sets for the selected
clients.
l
Reject—The clone save set list does not include eligible save sets for the
selected clients.
d. Levels filter—Use the Levels section to define a list of backup levels to include or
exclude, when NetWorker searches for eligible save sets to clone in the media
database. The Levels filter list includes three options, which define how NetWorker
determines save set eligibility, based on the level criteria:
l
Do Not Filter—NetWorker inspects save sets regardless of level in the media
database, to create a clone save set list that meets all the filter criteria.
l
Accept—The clone save set list includes eligible save sets with the selected
backup levels.
l
Reject—The clone save set list does not include eligible save sets with the
selected backup levels.
13. Click Next.
The Specify the Advanced Options page appears.
14. Configure advanced options, including notifications and schedule overrides.
Strategies for traditional backups
229
Data Protection Policies
Note
Although the Retries, Retry Delay, or the Inactivity Timeout options appear, the clone
action does not support these options and ignores the values.
15. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
Note
The Parallelism value should not exceed 25.
16. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
17. From the Send Notifications list box, select whether to send notifications for the
action:
l
Select Set at policy level to use the notification configuration that is defined in the
Policy resource to send the notification.
l
Select On Completion to send a notification on completion of the action.
l
Select On Failure to send a notification only if the action fails to complete.
18. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
230
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
19. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
20. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
21. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
Select the day in the calendar, which changes the action task for the specific day.
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
22. Click Next.
The Action Configuration Summary page appears.
23. Review the settings that you specified for the action, and then click Configure.
After you finish
(Optional) Create a clone action to automatically clone the save sets again after this
clone action. Another clone action is the only supported action after a clone action in a
workflow.
Strategies for traditional backups
231
Data Protection Policies
Visual representation of workflows
When you create actions for a workflow, a map provides a visual representation of the
actions in the second right pane of the Protection window of the Administration interface.
The following figure illustrates the visual representation of a sample workflow for a
traditional backup.
Figure 21 Visual representation of a workflow
The oval icon at the beginning of the visual representation specifies the group to which
the workflow applies, the rounded rectangle icons identify actions, and the parallelogram
icons identify the destination pool for the action.
l
Adjust the display of the visual representation by right-clicking and selecting one of
the following options:
n
Zoom In—Use to increase the size of the visual representation.
n
Zoom Out—Use to decrease the size of the visual representation.
n
Zoom Area—Use to limit the display to a single section of the visual
representation.
n
Fit Content—Use to fit the visual representation to the window area.
n
Reset—Use to reset the visual representation to the default settings.
n
Overview—To view a separate dialog box with a high-level view of the visual
representation and a legend of the icons.
l
View and edit the properties for the group, action, or destination pool by rightclicking the icon for the item and selecting Properties.
l
Create a group, action, or destination pool by right-clicking the icon for the item and
selecting New.
Strategies for server backup and maintenance
When you install or upgrade the NetWorker server, the installation or upgrade process
creates a default Server Protection policy for server backup and maintenance activities.
You can edit the default policy, workflows, groups, and actions, or create a set of policies
for server backup and maintenance.
After you install or upgrade the NMC server and then connect to the NMC GUI for the first
time, the Console Configuration wizard prompts you to configure the NetWorker server
that will backup the NMC server database.
When you define the database backup server, the Console Configuration wizard:
l
232
Creates a Client resource for the NMC server database backup. The Save set field for
the client contains the path to the database staging directory. By default, the staging
directory is in C:\Program Files\EMC NetWorker\Management
\nmcdb_stage on Windows and /opt/lgtonmc/nmcdb on Linux.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Note
The file system that contains the staging directory must have free disk space that is a
least equal to the size of the current NMC database. The section "Changing the
staging directory for NMC database backups" describes how to change the staging
directory location.
l
Creates a group called NMC server.
l
Adds the Client resource to the NMC server group.
l
Creates a workflow that is called NMC server backup in the Server Protection policy.
The workflow contains the NMC server backup action, which performs a full backup of
the NMC server database every day at 2 P.M.
l
Adds the NMC server group to the NMC server backup workflow.
Note
The NMC server database backup only supports the full and skip backup levels. If you
edit the NMC server backup action and change the levels in the backup schedule to a
different level, for example synthetic full, NetWorker performs a full backup of the
database.
Scheduling server backup and maintenance
Server backup and maintenance activities are configured in the default workflows to start
at 9 p.m. To optimize performance, ensure that the workflows start at times of minimal
backup activity or other system activity.
Protection groups for NetWorker and NMC server backup and maintenance
When you install or upgrade the NetWorker server, the installation or upgrade process
creates a default protection group for the NetWorker server workflows in the Server
Protection policy.
Server Protection group
The Server Protection group is a default protection group to back up the NetWorker server
bootstrap and client file indexes. The Server Protection group is assigned to the Server
backup workflow in the default Server Protection policy. The Server backup workflow
performs a bootstrap backup, which includes the NetWorker server resource files, media
database, NetWorker Authentication Service database, and client indexes for disaster
recovery. The group is a dynamic client group that automatically generates a list of Client
resources for the NetWorker server.
NMC server group
The NMC server group is a default protection group to back up the NMC database, which
the Console Configuration wizard prompts you to create the first time you log in to the
NMC server. The group is a client group that contains the Client resource for the NMC
server and is created during the initial login and configuration of NMC server. The NMC
server group is assigned to the NMC server backup workflow in the default Server
Protection policy.
Note
If you create custom groups for server backup and maintenance, ensure that they include
both the NetWorker server and the NMC server.
Strategies for server backup and maintenance
233
Data Protection Policies
Server Protection policy and workflows
When you install or upgrade the NetWorker server, the installation or upgrade process
creates a Server Protection policy with default workflows to support NetWorker and NMC
backup and maintenance activities.
The Server Protection policy includes the following default workflows:
Server backup
The workflow performs two actions:
l
Expiration—An expire action to mark expired save sets as recyclable.
l
Server database backup—A backup of the NetWorker server media database,
authentication service database, and the client file indexes. The data in this backup,
also called a bootstrap backup, enables you to perform a disaster recovery of the
NetWorker server.
The workflow is scheduled to start daily at 10 a.m. The workflow is assigned to the
default Server Protection group, which contains a dynamically generated list of the Client
resources for the NetWorker server.
NMC server backup
The workflow performs a traditional backup of the NMC database. The workflow is
scheduled to start a full backup daily at 2 p.m. The workflow is assigned to the default
NMC server group, which contains the NMC server.
Supported actions in a server backup workflow
The NetWorker server backup workflow supports the following action types.
Server database backup
A server database backup action performs a bootstrap backup and can also include the
client file indexes.
A bootstrap backup contains the following NetWorker server components:
l
Media database
l
Server resource files. For example, the resource (res) database and the Package
Manager database (nsrcpd)
l
NetWorker Authentication Service database
NetWorker automatically creates a server backup action in the Server Backup workflow of
the Server Protection policy. By default, a full backup of the media database, resource
files, and the NetWorker Authentication Service database occurs daily. A full backup of
the client file indexes occur on the first day of the month. An incremental backup of the
client file indexes occur on the remaining days of the month. The default retention policy
for the server database backup is one month.
Expiration
The expiration action expires save sets in the media database based on retention time of
the save set. When the retention time of the save set has been reached, NetWorker uses
the nsrim process to expire the save set. When a save set expires, the nsrim process
performs the following actions:
234
l
Removes information about the save set from the client file index.
l
If the save set data resides on an AFTD, removes the save set information from the
media database and removes the save set data from the AFTD.
l
If the save set data resides on a tape device, the nsrim process marks the save set
as recyclable in the media database. When all save sets on a tape volume have
expired, the volume is eligible for reuse.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
An expiration action is created automatically in the Server maintenance workflow of the
Server Protection policy. An expiration action only supports Execute and Skip backup
levels.
Clone
A clone action creates a copy of one or more save sets. Cloning allows for secure offsite
storage, transfer of data from one location to another, and verification of backups.
You can configure a clone action to occur after a backup in a single workflow, or
simultaneously with a backup action in a single workflow. You can also use save set and
query groups to define a specific list of save sets to clone, in a separate workflow.
Actions supported in an NMC server backup workflow
The NMC server backup workflow supports the following action types.
NMC server backup
An NMC server backup action performs a backup of the Postgres NMC database.
An NMC server backup action is created automatically in the NMC server backup workflow
of the Server Protection policy. The NMC server backup action only supports the full and
skip backup levels.
You can add the following action after the NMC server backup action:
Clone
A clone action creates a copy of one or more save sets. Cloning allows for secure offsite
storage, transfer of data from one location to another, and verification of backups.
You can configure a clone action to occur after a backup in a single workflow, or
simultaneously with a backup action in a single workflow. You can also use save set and
query groups to define a specific list of save sets to clone, in a separate workflow.
You can add the following actions before the NMC server backup action:
Probe
A probe action runs a user-defined script on a NetWorker client before the start of a
backup. A user-defined script is any program that passes a return code. If the return code
is 0 (zero), then a client backup is required. If the return code is 1, then a client backup is
not required.
Only a backup action can follow a probe action.
Check connectivity
A check connectivity action tests connectivity between clients and the NetWorker server
before a probe or backup action occurs. If the connectivity test fails, then the backup
does not occur on the client.
Actions in the server database backup and NMC server backup workflows
Workflows enable you to chain together multiple actions and run them sequentially or
concurrently.
The following sections provide details on supported actions that can follow the lead
action and other actions in a workflow.
Workflow path from a server database backup action
The Clone action is the only supported action after a server database backup action. You
cannot insert an action before a server database backup action.
Strategies for server backup and maintenance
235
Data Protection Policies
Figure 22 Workflow path from a server database backup action
Workflow path from an NMC server backup action
A clone action is the only supported action after an NMC server backup action. You
cannot insert an action before an NMC server backup action.
Figure 23 Workflow path from an NMC server backup action
Workflow path from an expiration action
The expiration action is an independent action, which means that you can add any other
action after the expiration action. EMC recommends that you do not add actions after an
expiration action in the server maintenance workflow. To use the expiration action with
other actions, create or modify a workflow.
Creating a clone action
A clone action creates a copy of one or more save sets. Cloning allows for secure offsite
storage, the transfer of data from one location to another, and the verification of
backups.
Procedure
1. In the expanded left pane, select the workflow, and then perform one of the following
tasks in the right pane to start the Policy Action wizard:
l
If this is the first action in the workflow, select Create a new action.
l
If the workflow has other actions, right-click an empty area of the Actions pane,
and then select New.
The Specify the Action Information page appears.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
5. From the Action Type list, select Clone.
6. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
7. Specify the order of the action in relation to other actions in the workflow:
l
236
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
8. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
9. Click the icon on each day to specify whether to perform cloning.
The following table provides details on the icons.
Table 42 Schedule icons
Icon
Label
Description
Execute Perform cloning on this day.
Skip
Do not perform cloning on this day.
To perform cloning every day, select Execute from the list and click Make All.
10. Click Next.
The Specify the Clone Options page appears.
11. In the Data Movement group box, define the volumes and devices to which NetWorker
sends the clone data.
a. From the Destination Storage Node list, select the storage node with the devices
on which to store the cloned save sets.
b. In the Delete source save sets after clone completes, select the option to instruct
NetWorker to remove the source save set information from the client file index, and
to mark the save set as recyclable in the media database during a Server
expiration maintenance action. Clear this option to allow the source save sets to
expire based on the defined retention time.
c. From the Destination Pool list, select the target media pool for the cloned save
sets.
d. From the Retention list, specify the amount of time to retain the cloned save sets.
After the retention period expires, the save sets are marked as recyclable during an
expiration server maintenance task.
12. In the Filters group box, define the criteria that NetWorker uses to create the list of
eligible save sets to clone. The eligible save sets must match the requirements that
are defined in each filter. NetWorker provides the following filter options:
a. Time filter—Use the Time section to define the time range in which NetWorker
should inspect, when searching for eligible save sets to clone in the media
database. Use the spin boxes to specify the start of the time range and the end of
the time range. The Time filter list includes three options, which define how
NetWorker determines save set eligibility, based on the time criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes save sets whose save time is within
the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
Strategies for server backup and maintenance
237
Data Protection Policies
l
Reject—The clone save set list does not include save sets whose save time is
within the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
b. Save Set filter—Use the Save Set section to instruct NetWorker to include or
exclude ProtectPoint and Snapshot save sets, when searching for eligible save
sets to clone in the media database. The Save Set filter list includes three options,
which define how NetWorker determines save set eligibility, based on the save set
criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes eligible ProtectPoint or Snapshot save
sets, when you also enable the ProtectPoint or Snapshot checkboxes.
l
Reject—The clone save set list does not include eligible ProtectPoint and
Snapshot save sets when you also enable the ProtectPoint and Snapshot
checkboxes.
c. Clients filter—Use the Client section to define a list of clients to include or exclude,
when NetWorker searches for eligible save sets to clone in the media database.
The Client list includes three options, which define how NetWorker determines
save set eligibility, based on the client criteria:
l
Do Not Filter—NetWorker inspects save sets that are associated with the clients
in the media database, to create a clone save set list that meets the filter
criteria.
l
Accept—The clone save set list includes eligible save sets for the selected
clients.
l
Reject—The clone save set list does not include eligible save sets for the
selected clients.
d. Levels filter—Use the Levels section to define a list of backup levels to include or
exclude, when NetWorker searches for eligible save sets to clone in the media
database. The Levels filter list includes three options, which define how NetWorker
determines save set eligibility, based on the level criteria:
l
Do Not Filter—NetWorker inspects save sets regardless of level in the media
database, to create a clone save set list that meets all the filter criteria.
l
Accept—The clone save set list includes eligible save sets with the selected
backup levels.
l
Reject—The clone save set list does not include eligible save sets with the
selected backup levels.
13. Click Next.
The Specify the Advanced Options page appears.
14. Configure advanced options, including notifications and schedule overrides.
Note
Although the Retries, Retry Delay, or the Inactivity Timeout options appear, the clone
action does not support these options and ignores the values.
15. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
238
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Note
The Parallelism value should not exceed 25.
16. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
17. From the Send Notifications list box, select whether to send notifications for the
action:
l
Select Set at policy level to use the notification configuration that is defined in the
Policy resource to send the notification.
l
Select On Completion to send a notification on completion of the action.
l
Select On Failure to send a notification only if the action fails to complete.
18. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
Strategies for server backup and maintenance
239
Data Protection Policies
l
On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
19. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
20. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
21. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
Select the day in the calendar, which changes the action task for the specific day.
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
22. Click Next.
The Action Configuration Summary page appears.
23. Review the settings that you specified for the action, and then click Configure.
After you finish
(Optional) Create a clone action to automatically clone the save sets again after this
clone action. Another clone action is the only supported action after a clone action in a
workflow.
Visual representation of workflows
When you create actions for a workflow, a map provides a visual representation of the
actions in the second right pane of the Protection window of the Administration interface.
The following figure illustrates the visual representation of the Server Protection
workflows.
240
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Figure 24 Visual representation of the Server Protection workflows
The oval icon at the beginning of the visual representation specifies the group to which
the workflow applies, the rounded rectangle icons identify actions, and the parallelogram
icons identify the destination pool for the action.
You can work directly in the visual representation of a workflow to perform the following
tasks:
l
Adjust the display of the visual representation by right-clicking and selecting one of
the following options:
n
Zoom In—Use to increase the size of the visual representation.
n
Zoom Out—Use to decrease the size of the visual representation.
n
Zoom Area—Use to limit the display to a single section of the visual
representation.
n
Fit Content—Use to fit the visual representation to the window area.
n
Reset—Use to reset the visual representation to the default settings.
n
Overview—To view a separate dialog box with a high-level view of the visual
representation and a legend of the icons.
l
View and edit the properties for the group, action, or destination pool by rightclicking the icon for the item and selecting Properties.
l
Create a group, action, or destination pool by right-clicking the icon for the item and
selecting New.
Strategies for cloning
Scheduled cloning occurs through configuration of data protection policies. You can
configure cloning to occur concurrently or after a backup, as part of a single workflow. The
decision of whether to clone data immediately after a backup or as a separate workflow
depends on specific circumstances, such as the amount of resources that are required for
the backup and recovery time objective.
You can use a clone action in one of the following ways:
l
After a backup action in a backup workflow.
l
In a separate workflow.
Strategies for cloning
241
Data Protection Policies
l
As the head action in workflow that uses a Query or Save set protection group.
Note
The Backup Data Management chapter describes how you can clone save sets manually
by using the nsrclone command.
The EMC NetWorker Cloning Integration Guide provides details on scheduling
considerations for cloning.
Road map for configuring a new cloning data protection policy
This road map provides a high level overview of how to configure a new policy for clone
operations.
Before you begin
Configure the backup policy to back up the data that is cloned.
Procedure
1. Create a group to define the data to clone.
2. Create a policy. When you create a policy, you specify the name and notification
settings for the policy.
3. Within the policy, create a workflow. When you create a workflow, you specify the
name of the workflow, the schedule for running the workflow, notification settings for
the workflow, and the protection group to which the workflow applies.
4. Create one or more clone actions for the workflow.
Protection groups for a cloning workflow
You can use two types of protection groups to clone save sets in a workflow that are
separate from backup workflows. The type of protection group that you use depends on
the way that you plan to configure the workflow.
Use a save set group or a query group to specify a list of save sets if cloning occurs as the
head action in a cloning workflow:
l
Save set group—Use a save set group in clone-only workflows where you want to
clone a specific list of save sets. Save set groups are similar to the manual clone
operations in NetWorker 8.2.x and earlier.
l
Query group—Use a query group in clone-only workflows where you want to clone
save sets on an ongoing basis, based on the save set criteria that you define. Query
groups are similar to the scheduled clone operations in NetWorker 8.2.x and earlier.
Note
To clone save sets in a backup workflow, use basic client group or a dynamic client
group. Strategies for traditional backups on page 210 provides detailed information
about how to create clone actions in a traditional backup workflow.
Create multiple protection groups to perform cloning in different ways as part of separate
workflows, or to perform cloning for different save sets on different schedules. For
example:
242
l
Create a basic client group for a workflow that performs a traditional backup of the a
client file system followed by cloning of the save sets that result from the backup.
l
Create a query group that identifies full save sets in the last two days to clone.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Creating a save set group
A save set group defines a static list of save sets for cloning or for snapshot index
generation.
Before you begin
Determine the save set ID or clone ID (ssid/clonid) of the save sets for the group by using
the Administration > Media user interface or the mminfo command.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Groups, and then select New.
The Create Group dialog box appears, starting with the General tab.
3. In the Name box, type a name for the group.
4. From the Group Type list, select Save Set ID List.
5. In the Comment box, type a description of the group.
6. (Optional) To associate the group with a workflow, from the Workflow (Policy) list,
select the workflow .
You can also assign the group to a workflow when you create or edit a workflow.
7. In the Clone specific save sets (save set ID/clone ID) box, type the save set ID/clone
ID (ssid/clonid) identifiers.
To specify multiple entries, type each value on a separate line.
8. To specify the Restricted Data Zone (RDZ) for the group, select the Restricted Data
Zones tab, and then select the RDZ from the list.
9. Click OK.
Creating a query group
A query group defines a list of save sets for cloning or snapshot index generation, based
on a list of save set criteria.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Groups, and then select New.
The Create Group dialog box appears, starting with the General tab.
3. In the Name box, type a name for the group.
4. From the Group Type list, select Save Set Query.
5. In the Comment box, type a description of the group.
6. (Optional) To associate the group with a workflow, from the Workflow (Policy) list,
select the workflow.
You can also assign the group to a workflow when you create or edit a workflow.
7. Specify one or more of the save set criteria in the following table.
Note
When you specify more than one save set criteria, the list of save sets only includes
save sets that match all the specified criteria.
Strategies for cloning
243
Data Protection Policies
Table 43 Save set criteria
Criteria
Description
Date and time range
Specify the start date and time range for the save sets.
To specify the current date and time as the end date for the
range, select Up to now.
To specify a different date and time as the end date for the
range, select Up to, and then select the date and time from the
lists.
Backup level
Limit the number of clones
In the Filter save sets by level section, next to the backup
level for the save set, select the checkbox:
l
full
l
cumulative incr
l
logs
l
incremental
l
manual
Specify the number for the limit in the Limit number of clones
list. The clone limit is the maximum number of clone instances
that can be created for the save set.
Note
The default is set to 0, and cannot be changed for NAS or Block.
Client
Next to one or more client resources that are associated with the
save set in the Client list, select the checkbox.
Policy
Next to the policy used to generate the save set in the Policy
list, select the checkbox.
Workflow
Next to the workflow used to generate the save set in the
Workflow list, select the checkbox.
Action
Next to the action used to generate the save set in the Action
list, select the checkbox.
Group
Next to the group associated with the save set in the Group list,
select the checkbox.
Pools
Next to the media pool on which the save set is stored in the
Pools list, select the checkbox.
Note
You cannot select Pools for NAS.
Name
In the Filter save sets by name box, specify the name of the
save set.
Note
You cannot use wildcards to specify the save set name.
244
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Table 43 Save set criteria (continued)
If you specify multiple criteria, the save set must match all the criteria to belong to the
group.
8. To specify the Restricted Data Zone (RDZ) for the group, select the Restricted Data
Zones tab, and then select the RDZ from the list.
9. Click OK.
Creating a policy
Procedure
1. On the Administration window, click Protection.
2. In the expanded left pane, right-click Policies, and then select New.
The Create Policy dialog box appears.
3. On the General tab, in the Name field type a name for the policy.
The maximum number of characters for the policy name is 128.
Note
After you create a policy, the Name attribute is read-only.
4. In the Comment box, type a description for the policy.
5. From the Send Notifications list, select whether to send notifications for the policy:
l
To avoid sending notifications, select Never.
l
To send notifications with information about each successful and failed workflow
and action after all the actions in the policy complete, select On Completion.
l
To send a notification with information about each failed workflow and action after
all the actions in the policy complete, select On Failure.
6. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
Strategies for cloning
245
Data Protection Policies
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Windows, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
7. To specify the Restricted Data Zone (RDZ) for the policy, select the Restricted Data
Zones tab, and then select the RDZ from the list.
8. Click OK.
After you finish
Create the workflows and actions for the policy.
Creating a workflow in a new policy
A policy must contain one or more workflows.
Procedure
1. In the left pane of the Protection window, expand Policies, and then select the policy
that you created.
2. In the right pane of the Protection window, select Create a new workflow.
3. In the Name field, type the name of the workflow.
The maximum number of characters for the name of the group is 64.
4. In the Comment box, type a description for the workflow. The maximum number of
characters for the Comment field is 128.
5. From the Send Notifications list, select how to send notifications for the workflow:
l
To use the notification configuration that is defined in the policy resource to
determine when to send the notification, select Set at policy level.
l
To send notifications with information about each successful and failed workflow
and action, after all the actions in the workflow complete, select On Completion.
l
To send notifications with information about each failed workflow and action, after
all the actions in the workflow complete, select On Failure.
6. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
246
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Windows, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
7. In the Running group box, define when and how often the workflow runs.
a. To ensure that the actions contained in the workflow run when the policy or
workflow is started, in the Enabled box, leave the option selected. To prevent the
actions in the workflow from running when the policy or workflow that contains the
action is started, clear this option.
b. To ensure that the workflow starts at the time that is specified in the Start time
attribute, on the days that are defined in the action resource, in the AutoStart
Enabled box, leave the option selected. To prevent the workflow from running at
the time that is specified in the Start time attribute, clear this option.
c. To define the time to start the actions in the workflow, in the Start Time attribute,
use the spin boxes.
The default value is 9:00 P.M.
d. To define how frequently to repeat the actions that are defined in the workflow
over a 24 hour period, In the Interval attribute, use the spin boxes.
The default value is 24 hours, or once a day. When you select a value that is less
than 24 hours, the Interval End attribute appears. To define the last time to start a
workflow in a defined interval period, use the spin boxes .
e. To define the duration of time in which NetWorker can manually or automatically
restart a failed or canceled workflow, in the Restart Window attribute, use the spin
boxes.
Strategies for cloning
247
Data Protection Policies
If the restart window has elapsed, NetWorker considers the restart as a new run of
the workflow. NetWorker calculates the restart window from the start of the last
incomplete workflow. The default value is 24 hours.
For example, when you set the Start Time to 7:00 PM, the Interval to 1 hour, and the
Interval end time to 11:00 P.M., then the workflow automatically starts every hour
beginning at 7:00 P.M. and the last start time is 11:00 PM.
8. To create the workflow, click OK.
After you finish
Create the actions that will occur in the workflow, and then assign a group to the
workflow. If a workflow does not contain a group, a policy does not perform any actions.
Workflows for scheduled cloning
A workflow can contain one or more clone actions.
Supported workflow path from a clone action
Another clone action is the only supported action after a clone action.
Figure 25 Workflow path from a clone action
Creating a clone action
A clone action creates a copy of one or more save sets. Cloning allows for secure offsite
storage, the transfer of data from one location to another, and the verification of
backups.
Procedure
1. In the expanded left pane, select the workflow, and then perform one of the following
tasks in the right pane to start the Policy Action wizard:
l
If this is the first action in the workflow, select Create a new action.
l
If the workflow has other actions, right-click an empty area of the Actions pane,
and then select New.
The Specify the Action Information page appears.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
5. From the Action Type list, select Clone.
6. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
248
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
7. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
8. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
9. Click the icon on each day to specify whether to perform cloning.
The following table provides details on the icons.
Table 44 Schedule icons
Icon
Label
Description
Execute Perform cloning on this day.
Skip
Do not perform cloning on this day.
To perform cloning every day, select Execute from the list and click Make All.
10. Click Next.
The Specify the Clone Options page appears.
11. In the Data Movement group box, define the volumes and devices to which NetWorker
sends the clone data.
a. From the Destination Storage Node list, select the storage node with the devices
on which to store the cloned save sets.
b. In the Delete source save sets after clone completes, select the option to instruct
NetWorker to remove the source save set information from the client file index, and
to mark the save set as recyclable in the media database during a Server
expiration maintenance action. Clear this option to allow the source save sets to
expire based on the defined retention time.
c. From the Destination Pool list, select the target media pool for the cloned save
sets.
d. From the Retention list, specify the amount of time to retain the cloned save sets.
After the retention period expires, the save sets are marked as recyclable during an
expiration server maintenance task.
12. In the Filters group box, define the criteria that NetWorker uses to create the list of
eligible save sets to clone. The eligible save sets must match the requirements that
are defined in each filter. NetWorker provides the following filter options:
a. Time filter—Use the Time section to define the time range in which NetWorker
should inspect, when searching for eligible save sets to clone in the media
database. Use the spin boxes to specify the start of the time range and the end of
the time range. The Time filter list includes three options, which define how
NetWorker determines save set eligibility, based on the time criteria:
Strategies for cloning
249
Data Protection Policies
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes save sets whose save time is within
the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
l
Reject—The clone save set list does not include save sets whose save time is
within the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
b. Save Set filter—Use the Save Set section to instruct NetWorker to include or
exclude ProtectPoint and Snapshot save sets, when searching for eligible save
sets to clone in the media database. The Save Set filter list includes three options,
which define how NetWorker determines save set eligibility, based on the save set
criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes eligible ProtectPoint or Snapshot save
sets, when you also enable the ProtectPoint or Snapshot checkboxes.
l
Reject—The clone save set list does not include eligible ProtectPoint and
Snapshot save sets when you also enable the ProtectPoint and Snapshot
checkboxes.
c. Clients filter—Use the Client section to define a list of clients to include or exclude,
when NetWorker searches for eligible save sets to clone in the media database.
The Client list includes three options, which define how NetWorker determines
save set eligibility, based on the client criteria:
l
Do Not Filter—NetWorker inspects save sets that are associated with the clients
in the media database, to create a clone save set list that meets the filter
criteria.
l
Accept—The clone save set list includes eligible save sets for the selected
clients.
l
Reject—The clone save set list does not include eligible save sets for the
selected clients.
d. Levels filter—Use the Levels section to define a list of backup levels to include or
exclude, when NetWorker searches for eligible save sets to clone in the media
database. The Levels filter list includes three options, which define how NetWorker
determines save set eligibility, based on the level criteria:
l
Do Not Filter—NetWorker inspects save sets regardless of level in the media
database, to create a clone save set list that meets all the filter criteria.
l
Accept—The clone save set list includes eligible save sets with the selected
backup levels.
l
Reject—The clone save set list does not include eligible save sets with the
selected backup levels.
13. Click Next.
The Specify the Advanced Options page appears.
14. Configure advanced options, including notifications and schedule overrides.
250
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Note
Although the Retries, Retry Delay, or the Inactivity Timeout options appear, the clone
action does not support these options and ignores the values.
15. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
Note
The Parallelism value should not exceed 25.
16. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
17. From the Send Notifications list box, select whether to send notifications for the
action:
l
Select Set at policy level to use the notification configuration that is defined in the
Policy resource to send the notification.
l
Select On Completion to send a notification on completion of the action.
l
Select On Failure to send a notification only if the action fails to complete.
18. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
Strategies for cloning
251
Data Protection Policies
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
19. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
20. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
21. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
Select the day in the calendar, which changes the action task for the specific day.
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
22. Click Next.
The Action Configuration Summary page appears.
23. Review the settings that you specified for the action, and then click Configure.
After you finish
(Optional) Create a clone action to automatically clone the save sets again after this
clone action. Another clone action is the only supported action after a clone action in a
workflow.
252
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Visual representation of a clone workflow
When you create actions for a workflow, a map provides a visual representation of the
actions in the second right pane of the Protection window of the Administration interface.
The following figure illustrates the visual representation of a clone workflow.
Figure 26 Visual representation of a clone workflow
The oval icon at the beginning of the visual representation specifies the group to which
the workflow applies, the rounded rectangle icons identify actions, and the parallelogram
icons identify the destination pool for the action.
You can work directly in the visual representation of a workflow to perform the following
tasks:
l
Adjust the display of the visual representation by right-clicking and selecting one of
the following options:
n
Zoom In—Use to increase the size of the visual representation.
n
Zoom Out—Use to decrease the size of the visual representation.
n
Zoom Area—Use to limit the display to a single section of the visual
representation.
n
Fit Content—Use to fit the visual representation to the window area.
n
Reset—Use to reset the visual representation to the default settings.
n
Overview—To view a separate dialog box with a high-level view of the visual
representation and a legend of the icons.
l
View and edit the properties for the group, action, or destination pool by rightclicking the icon for the item and selecting Properties.
l
Create a group, action, or destination pool by right-clicking the icon for the item and
selecting New.
Road map to add a clone workflow to an existing policy
This road map provides a high level overview of how to create a clone workflow and add
the workflow to an existing backup policy.
Before you begin
Configure the backup policy to back up the data that is cloned.
Procedure
1. Create a query or save set group to define the data to clone.
2. Add the new group to an existing policy.
3. Create a workflow in the existing policy.
4. Create one or more clone actions for the workflow.
Strategies for cloning
253
Data Protection Policies
Example: Creating a policy that has a separate workflow for cloning
The following figure provides a high level overview of the configuration of a policy that
contains two workflows, one for backups and one to clone a list of save sets.
Figure 27 Example of a policy with separate workflows for backup and cloning
Note
The amount of data and length of time that is required to complete the backup can
impact the ability to clone data when the backup and clone workflows are in the same
policy. For example, if the clone action starts before the backup action completes, there
might not be any data yet to clone, or in other cases, only the save sets that completed at
the start time of the workflow is taken into account. In both cases, NetWorker marks the
Clone Workflow as successful, but there is no guarantee that all the data from the backup
workflow was cloned.
Protection groups for a cloning workflow
You can use two types of protection groups to clone save sets in a workflow that are
separate from backup workflows. The type of protection group that you use depends on
the way that you plan to configure the workflow.
Use a save set group or a query group to specify a list of save sets if cloning occurs as the
head action in a cloning workflow:
254
l
Save set group—Use a save set group in clone-only workflows where you want to
clone a specific list of save sets. Save set groups are similar to the manual clone
operations in NetWorker 8.2.x and earlier.
l
Query group—Use a query group in clone-only workflows where you want to clone
save sets on an ongoing basis, based on the save set criteria that you define. Query
groups are similar to the scheduled clone operations in NetWorker 8.2.x and earlier.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Note
To clone save sets in a backup workflow, use basic client group or a dynamic client
group. Strategies for traditional backups on page 210 provides detailed information
about how to create clone actions in a traditional backup workflow.
Create multiple protection groups to perform cloning in different ways as part of separate
workflows, or to perform cloning for different save sets on different schedules. For
example:
l
Create a basic client group for a workflow that performs a traditional backup of the a
client file system followed by cloning of the save sets that result from the backup.
l
Create a query group that identifies full save sets in the last two days to clone.
Creating a save set group
A save set group defines a static list of save sets for cloning or for snapshot index
generation.
Before you begin
Determine the save set ID or clone ID (ssid/clonid) of the save sets for the group by using
the Administration > Media user interface or the mminfo command.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Groups, and then select New.
The Create Group dialog box appears, starting with the General tab.
3. In the Name box, type a name for the group.
4. From the Group Type list, select Save Set ID List.
5. In the Comment box, type a description of the group.
6. (Optional) To associate the group with a workflow, from the Workflow (Policy) list,
select the workflow .
You can also assign the group to a workflow when you create or edit a workflow.
7. In the Clone specific save sets (save set ID/clone ID) box, type the save set ID/clone
ID (ssid/clonid) identifiers.
To specify multiple entries, type each value on a separate line.
8. To specify the Restricted Data Zone (RDZ) for the group, select the Restricted Data
Zones tab, and then select the RDZ from the list.
9. Click OK.
Creating a query group
A query group defines a list of save sets for cloning or snapshot index generation, based
on a list of save set criteria.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Groups, and then select New.
The Create Group dialog box appears, starting with the General tab.
3. In the Name box, type a name for the group.
4. From the Group Type list, select Save Set Query.
5. In the Comment box, type a description of the group.
Strategies for cloning
255
Data Protection Policies
6. (Optional) To associate the group with a workflow, from the Workflow (Policy) list,
select the workflow.
You can also assign the group to a workflow when you create or edit a workflow.
7. Specify one or more of the save set criteria in the following table.
Note
When you specify more than one save set criteria, the list of save sets only includes
save sets that match all the specified criteria.
Table 45 Save set criteria
Criteria
Description
Date and time range
Specify the start date and time range for the save sets.
To specify the current date and time as the end date for the
range, select Up to now.
To specify a different date and time as the end date for the
range, select Up to, and then select the date and time from the
lists.
Backup level
Limit the number of clones
In the Filter save sets by level section, next to the backup
level for the save set, select the checkbox:
l
full
l
cumulative incr
l
logs
l
incremental
l
manual
Specify the number for the limit in the Limit number of clones
list. The clone limit is the maximum number of clone instances
that can be created for the save set.
Note
The default is set to 0, and cannot be changed for NAS or Block.
256
Client
Next to one or more client resources that are associated with the
save set in the Client list, select the checkbox.
Policy
Next to the policy used to generate the save set in the Policy
list, select the checkbox.
Workflow
Next to the workflow used to generate the save set in the
Workflow list, select the checkbox.
Action
Next to the action used to generate the save set in the Action
list, select the checkbox.
Group
Next to the group associated with the save set in the Group list,
select the checkbox.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Table 45 Save set criteria (continued)
Criteria
Description
Pools
Next to the media pool on which the save set is stored in the
Pools list, select the checkbox.
Note
You cannot select Pools for NAS.
Name
In the Filter save sets by name box, specify the name of the
save set.
Note
You cannot use wildcards to specify the save set name.
If you specify multiple criteria, the save set must match all the criteria to belong to the
group.
8. To specify the Restricted Data Zone (RDZ) for the group, select the Restricted Data
Zones tab, and then select the RDZ from the list.
9. Click OK.
Editing an existing policy to create a workflow and clone action
Use the Policies window to create a workflow and create the clone action.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, expand Policies, and then select the existing policy.
3. In the right pane, right-click in the workflow section and select New, and select
Properties.
The New Workflow dialog box appears.
4. In the Name field, type the name of the workflow.
The maximum number of characters for the name of the group is 64.
5. In the Comment box, type a description for the workflow. The maximum number of
characters for the Comment field is 128.
6. From the Send Notifications list, select how to send notifications for the workflow:
l
To use the notification configuration that is defined in the policy resource to
determine when to send the notification, select Set at policy level.
l
To send notifications with information about each successful and failed workflow
and action, after all the actions in the workflow complete, select On Completion.
l
To send notifications with information about each failed workflow and action, after
all the actions in the workflow complete, select On Failure.
7. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
Strategies for cloning
257
Data Protection Policies
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
On Windows, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
8. In the Running group box, define when and how often the workflow runs.
a. To ensure that the actions contained in the workflow run when the policy or
workflow is started, in the Enabled box, leave the option selected. To prevent the
actions in the workflow from running when the policy or workflow that contains the
action is started, clear this option.
b. To ensure that the workflow starts at the time that is specified in the Start time
attribute, on the days that are defined in the action resource, in the AutoStart
Enabled box, leave the option selected. To prevent the workflow from running at
the time that is specified in the Start time attribute, clear this option.
c. To define the time to start the actions in the workflow, in the Start Time attribute,
use the spin boxes.
The default value is 9:00 P.M.
d. To define how frequently to repeat the actions that are defined in the workflow
over a 24 hour period, In the Interval attribute, use the spin boxes.
The default value is 24 hours, or once a day. When you select a value that is less
than 24 hours, the Interval End attribute appears. To define the last time to start a
workflow in a defined interval period, use the spin boxes .
e. To define the duration of time in which NetWorker can manually or automatically
restart a failed or canceled workflow, in the Restart Window attribute, use the spin
boxes.
258
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
If the restart window has elapsed, NetWorker considers the restart as a new run of
the workflow. NetWorker calculates the restart window from the start of the last
incomplete workflow. The default value is 24 hours.
For example, when you set the Start Time to 7:00 PM, the Interval to 1 hour, and the
Interval end time to 11:00 P.M., then the workflow automatically starts every hour
beginning at 7:00 P.M. and the last start time is 11:00 PM.
9. In the Groups group box, specify the protection group to which the workflow applies.
To use a group, select a protection group from the Groups list. To create a protection
group, click the + button that is located to the right of the Groups list.
10. Click Add.
The Policy Action Wizard appears.
11. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
12. In the Comment field, type a description for the action.
13. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
14. From the Action type list, select Clone.
15. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
16. Select whether to use a weekly or monthly schedule for the action:
l
To specify a schedule for each day of the week, select Weekly by day.
l
To specify a schedule for each day of the month, select Monthly by day.
17. Click the icon on each day to specify whether to perform cloning.
The following table provides details on the icons.
Table 46 Schedule icons
Icon
Label
Description
Execute Perform cloning on this day.
Skip
Do not perform cloning on this day.
To perform cloning every day, select Execute from the list and click Make All.
Strategies for cloning
259
Data Protection Policies
18. Click Next.
The Specify the Clone Options page appears.
19. In the Data Movement group box, define the volumes and devices to which NetWorker
sends the clone data.
a. From the Destination Storage Node list, select the storage node with the devices
on which to store the cloned save sets.
b. In the Delete source save sets after clone completes, select the option to instruct
NetWorker to remove the source save set information from the client file index, and
to mark the save set as recyclable in the media database during a Server
expiration maintenance action. Clear this option to allow the source save sets to
expire based on the defined retention time.
c. From the Destination Pool list, select the target media pool for the cloned save
sets.
d. From the Retention list, specify the amount of time to retain the cloned save sets.
After the retention period expires, the save sets are marked as recyclable during an
expiration server maintenance task.
20. In the Filters group box, define the criteria that NetWorker uses to create the list of
eligible save sets to clone. The eligible save sets must match the requirements that
are defined in each filter. NetWorker provides the following filter options:
a. Time filter—Use the Time section to define the time range in which NetWorker
should inspect, when searching for eligible save sets to clone in the media
database. Use the spin boxes to specify the start of the time range and the end of
the time range. The Time filter list includes three options, which define how
NetWorker determines save set eligibility, based on the time criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes save sets whose save time is within
the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
l
Reject—The clone save set list does not include save sets whose save time is
within the time range that is specified by the spin boxes and meet all the other
defined filter criteria.
b. Save Set filter—Use the Save Set section to instruct NetWorker to include or
exclude ProtectPoint and Snapshot save sets, when searching for eligible save
sets to clone in the media database. The Save Set filter list includes three options,
which define how NetWorker determines save set eligibility, based on the save set
criteria:
l
Do Not Filter—NetWorker inspects the save sets in the media database to
create a clone save set list that meets the filter criteria.
l
Accept—The clone save set list includes eligible ProtectPoint or Snapshot save
sets, when you also enable the ProtectPoint or Snapshot checkboxes.
l
Reject—The clone save set list does not include eligible ProtectPoint and
Snapshot save sets when you also enable the ProtectPoint and Snapshot
checkboxes.
c. Clients filter—Use the Client section to define a list of clients to include or exclude,
when NetWorker searches for eligible save sets to clone in the media database.
The Client list includes three options, which define how NetWorker determines
save set eligibility, based on the client criteria:
260
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
Do Not Filter—NetWorker inspects save sets that are associated with the clients
in the media database, to create a clone save set list that meets the filter
criteria.
l
Accept—The clone save set list includes eligible save sets for the selected
clients.
l
Reject—The clone save set list does not include eligible save sets for the
selected clients.
d. Levels filter—Use the Levels section to define a list of backup levels to include or
exclude, when NetWorker searches for eligible save sets to clone in the media
database. The Levels filter list includes three options, which define how NetWorker
determines save set eligibility, based on the level criteria:
l
Do Not Filter—NetWorker inspects save sets regardless of level in the media
database, to create a clone save set list that meets all the filter criteria.
l
Accept—The clone save set list includes eligible save sets with the selected
backup levels.
l
Reject—The clone save set list does not include eligible save sets with the
selected backup levels.
21. Click Next.
The Specify the Advanced Options page appears.
22. Configure advanced options, including notifications and schedule overrides.
Note
Although the Retries, Retry Delay, or the Inactivity Timeout options appear, the clone
action does not support these options, and ignores the values.
23. In the Parallelism field, specify the maximum number of concurrent operations for the
action.
Note
The Parallelism value should not exceed 25.
24. From the Failure Impact list, specify what to do when a job fails:
l
To continue the workflow when there are job failures, select Continue.
l
To abort the current action if there is a failure with one of the jobs, but continue
with subsequent actions in the workflow, select Abort action.
Note
The Abort action option only applies to probe actions, and the backup actions for
the Traditional and Snapshot action types.
l
To abort the entire workflow if there is a failure with one of the jobs in the action,
select Abort workflow.
Note
If any of the actions fail in the workflow, the workflow status does not appear as
interrupted or cancelled. NetWorker reports the workflow status as failed.
Strategies for cloning
261
Data Protection Policies
25. From the Send Notifications list box, select whether to send notifications for the
action:
l
Select Set at policy level to use the notification configuration that is defined in the
Policy resource to send the notification.
l
Select On Completion to send a notification on completion of the action.
l
Select On Failure to send a notification only if the action fails to complete.
26. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
On Window, to send a notification email, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
27. From the Soft Limit list, specify the amount of time after the action starts to stop the
initiation of new activities. The default value of 0 (zero) indicates no limit.
28. From the Hard Limit list, specify the amount of time after the action starts to begin
terminating activities. The default value of 0 (zero) indicates no limit.
29. (Optional) Configure overrides for the task that is scheduled on a specific day.
To change the month on which to schedule the override, use the navigation buttons
and the month list box. To change the year, use the spin boxes. You can set an
override in the following ways:
l
262
Select the day in the calendar, which changes the action task for the specific day.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
Use the action task list to select the task, then perform one of the following steps:
n
To define an override that occurs on a specific day of the week, every week,
select Specified day, then use the drop downs. Click Add Rules based override.
n
To perform the action task on the last day of the calendar month, select Last
day of the month. Click Add Rules based override.
n
In the Override field, type an override.
Note
To remove an override, delete the entry from the Override field.
30. Click Next.
The Action Configuration Summary page appears.
31. Review the settings that you specified for the action, and then click Configure.
Policy notifications
You can define how a Data Protection Policy sends notifications in the Policy, Workflow,
and Action resources.
The following table summarizes how the notification settings in each resource work
together.
In the Policy resource, the following notification choices are available:
l
Never —Select this option when you do not want to send any notifications.
l
On Completion—Select this option when you want to send a notification on
completion of the workflows and actions in the policy.
l
On Failure—Select this option when you want to send a notification only if one or
more of the workflows in the policy fail.
In the Workflow resource, the following notification choices are available:
l
To use the notification configuration that is defined in the policy resource to send the
notification, select Set a policy level.
l
To send a notification on completion of all the actions in the workflow, select On
Completion.
l
To send a notification only if an action fails to complete, select On Failure.
In the Policy resource, the following notification choices are available:
l
To use the notification configuration that is defined in the policy resource to send the
notification, select Set a policy level.
l
To send a notification on completion of the action, select On Completion.
l
To send a notification only if the action fails to complete, select On Failure.
Monitoring policy activity
The Monitoring window in the NetWorker Administration window enables you to monitor
activities for specific policies, workflows, and actions.
Policies/Actions pane
The Policies/Actions pane at the top of the Monitoring window lists the policies on the
NetWorker server by default. Click the + (plus) sign next to a policy in the list to view the
Policy notifications
263
Data Protection Policies
workflows in the policy, and the + (plus) sign next to a workflow to view the actions for a
workflow.
The Policies pane provides the following information for each item (where applicable):
l
Overall status
The following table provides details on the status icons that may appear in the
Policies pane.
Table 47 Policy status icons
Icon
Status
Never run
Running
Succeeded
Failed
Probing
l
Most recent start time
l
Duration of the most recent run
l
Next scheduled runtime
l
Name of the assigned save set
l
Device on which the save set is stored
l
Backup level
l
Data transfer rate
l
Size of the save set
l
Messages that resulted from an action
Right-click an action in the Policies pane, and select Show Details to view details on
currently running, successfully completed, and failed activities for the action.
When you sort the items on the Policy/Actions pane by using the Status column,
NetWorker sorts the items in alphabetical order that is based on the label of the icon.
Consider the following when a policy/action is in a probing state:
l
A message is sent when the group starts and finishes the probe operation.
l
The results of the probe operation (run backup/do not run backup) are also logged.
l
Probes do not affect the final status of the group, and the group status does not
indicate the results of the probe.
l
If probing indicates that a backup should not run, then the group status reverts to its
state before the group running.
l
Check the results of the probe in the Log window to ensure that the probe indicates
that the backup can be taken.
Actions pane
To view a list of all actions, click the Actions tab at the bottom of the Policies pane. The
Policies pane becomes the Actions pane.
264
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
The Actions pane provides the following information for each action:
l
Overall status
Note
The Actions pane displays the same status icons as the Policies pane.
l
Name
l
Assigned policy
l
Assigned workflow
l
Type
l
Date and time of the most recent run
l
Duration of the most recent run
l
Percent complete, for actions that are in progress
l
Next scheduled runtime
Right-click an action in the Actions pane, and select Show Details to view details on
currently running, completed, and failed activities for the action.
Monitoring cloning
You can view the status of scheduled clone jobs in the Monitoring window. Status
information includes the last start time of the policy, workflow, or clone action, the
duration of the action, the size of the save set, and the target device, pool, and volume.
To determine whether a save set on a volume has been cloned, or is itself a clone, check
the search for the save set by using the Query Save Set tab when you select Save Sets in
the Media window.
Policy log files
The NetWorker server contains the log files for all data protection Policy resources.
Policy log directory structure
The policy-related resource log files are found in the following directory:
l
Windows:
c:\Program Files\EMC NetWorker\nsr\logs\policy_name
\workflow_name\action_name
l
Linux:
/nsr/logs/policy_name/workflow_name/action_name
where:
l
Policy_name—is the name of the Policy resource. One folder per policy.
l
Workflow_name—is the name of the workflow directory. One folder per action
sequence.
l
Action_name—is the name of the action log file within the workflow.
Workflow log files
The policy subdirectory contains raw log files for each workflow and one subdirectory for
each action.
The location and format of the log file on Linux is:
/nsr/logs/policy/policy_name/workflow_name_jobid.raw
Monitoring cloning
265
Data Protection Policies
where name_jobid is the name of the workflow and the job id of the workflow. Job id is a
value that uniquely identifies a workflow job record in the jobdb.
For example, the log file for a workflow that is called server backup, with a job id of
0010072 appears as follows:
/nsr/logs/policy/server protection/workflow_server
backup_0010072.raw
Use the job id to perform queries of the jobdb with the jobquery command. A workflow
log file can be unrendered or rendered. An unrendered log file has the file name
extension .raw. A rendered log file's extension is .log. Unrendered log files contain
internationalized messages that can be rendered into the local language. The content of
rendered log files has been localized to a single country's language.
View log files on page 791 provides more information about viewing rendered and
unrendered log files.
Action log files
NetWorker creates a workflow directory for each workflow within the policy directory. The
workflow directory contains log files for each action that is assigned to the workflow.
The location of the workflow directory on Linux is:
/nsr/logs/policy/policy_name/workflow_name
where:
l
policy_name—is the name of the policy that contains the workflow.
l
workflow_name—is the name of the workflow.
The workflow directory contains log files for each action that is assigned to the workflow.
The file name appears in the following format:
action_name_job_id.raw
where:
l
action_name—is the name of the action.
l
job_id—is the job id of the action in the jobdb.
For example, the server backup workflow has three actions: Backup, Clone, and Clone
more. There are three log files in /nsr/logs/policy/server protection/
server backup directory with the following names:
Backup_ 1408063.raw
Clone_1408080.raw
Clone more_1408200.raw
Child action log files
Some actions create child actions, for example a backup action creates a save job and a
savefs job. Each child action has a unique job record.
Each of these child jobs have a log file. When the parent action starts a child action,
NetWorker creates a directory for the action that contains the log file for child activities.
The location of the action directory on Linux is:
/nsr/logs/policy/policy_name/workflow_name/
action_name_job_id_logs
where:
266
l
policy_name— is the name of the policy that contains the workflow.
l
workflow_name— is the name of the workflow.
l
action_name—is the name of the action.
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
job_id—is the job id of the action in the jobdb.
The action directory contains log files for each child action started by the action. The file
name appears in the following format:
job_id.log
where job_id is the job id of the child action in the jobdb.
For example, an action whose log file name is Backup_1408063.raw might have a
directory that is named Backup_1408063_logs, which contains three log files:
l
1408066.log
l
1408067.log
l
1408070.log
Note
The .log files are localized to a specific country or the language of the region.
NetWorker clears the information about a job from the jobsdb and deletes the associated
log files at the interval that is defined by the Jobsdb retention in hours attribute in the
properties of the NetWorker Server resource. In NetWorker 9.0.1, the default jobsdb
retention is 72 hours.
Starting, stopping, and restarting data protection policies
The workflows in a data protection policy can run automatically, based on a schedule.
You can also manually start, stop, and restart specific workflows, in the Monitoring
window of the NetWorker Administration window.
Note
You cannot stop, restart, or start individual actions.
You can restart any failed or canceled workflow. However, the restart must happen within
the restart window that you specified for the workflow.
You can also start specific policies and workflows in the Protection window by rightclicking the policy or workflow, and selecting Start.
Procedure
1. Select the workflow, or action in the Monitoring window.
2. Right-click and select Start, Stop, or Restart.
A confirmation message appears.
3. Click Yes.
Starting actions in a workflow for an individual client
When you start a workflow, NetWorker performs all the actions in the workflow for all the
clients that are defined in the groups that are associated with the workflow. You can also
start the actions for specific clients in a workflow.
Perform the following steps to start the actions for an individual client.
Starting, stopping, and restarting data protection policies
267
Data Protection Policies
Note
You cannot start the actions for specific clients in the Server backup workflow.
Procedure
1. From the Administration window, click Monitoring.
2. In the Policies pane, expand the policy.
3. Right-click the workflow, and select Start Individual Client. The Start Workflow dialog
box appears.
4. Optionally, from the Workflow list, select a different workflow.
5. Select the checkbox next to the names of the clients on which you want to perform all
the actions in the workflow.
6. Click Start.
Modifying data protection Policy resources
This section describes how to modify existing Policy, Workflow, Group, and Action
resources.
Policies
Policies enable you to manage all data protection tasks and the data protection lifecycle
from a central location.
A policy contains one or more workflows, which define the actions that should be
performed, the order for the actions to occur, and the group of Client resources or save
sets on which to perform the actions.
Actions include backups, cloning, client/server connectivity checks, and NetWorker
server maintenance activities.
Editing a policy
You can edit the description, notification setting, and RDZ for a policy.
You cannot edit the name of a policy. To rename a policy, first delete the policy, and then
re-create it with the new name.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Policies.
3. Right-click the policy, and select Properties.
The Policy Properties dialog box appears.
4. Edit the properties for the policy. The properties are the same properties that you
specified when you created the policy.
5. Click OK.
268
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Deleting a policy
When you delete a policy, the deletion process also deletes all workflows and actions for
the policy.
Groups that are assigned to the workflows in the policy are not deleted, however. The
workflow assignment for the group is removed from the group properties. You can assign
the group to a workflow in a different policy, or delete the group.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Policies.
3. Right-click the policy, and select Delete.
A confirmation message appears.
4. Click Yes.
Note
The Policy resource remains in the Monitoring window until all the information about
the workflows and actions within the policy expire in the jobs database. The default
job expiration time is 72 hours. Modifying the retention period for jobs in the jobs
database on page 696 describes how to change the default job expiration time.
Workflows
Workflows define a list of actions to perform sequentially or concurrently, a schedule
window during which the workflow can run, and the protection group to which the
workflow applies.
A workflow can be as simple as a single action that applies to a finite list of Client
resources, or it can be a complex chain of actions that apply to a dynamically changing
list of resources, with some actions occurring sequentially and others occurring
concurrently.
You can also define notification settings for a workflow.
Supported workflow paths
Workflows enable you to chain together multiple actions and run them either sequentially
or concurrently. However, the sequence of actions in a workflow is limited by certain
logical constraints.
The following sections provide details on supported actions that can follow the lead
action in a workflow.
Workflow path from a snapshot backup action
You can perform a generate index action (to generate an index of the snapshot) or a clone
action after a snapshot backup action.
Figure 28 Workflow path from a snapshot backup action
Workflows
269
Data Protection Policies
Workflow path from a probe action
You can perform either a traditional backup or a snapshot backup after a probe action.
Figure 29 Workflow path from a probe action
Workflow path from a server backup action
A clone action is the only supported action after a server backup action.
Figure 30 Workflow path from a server backup action
Workflow path from a check connectivity action
You can perform a traditional backup, snapshot backup, or probe action after a check
connectivity action.
Figure 31 Workflow path from a check connectivity action
Workflow path from a clone action
Another clone action is the only supported action after a clone action.
Figure 32 Workflow path from a clone action
Workflow path from an expire action
The expire action must be the only action in a workflow. No other actions are supported
either before or after an expire action.
Workflow path from a discover action
You can perform a generate index or clone action after a discover action.
270
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Figure 33 Workflow path from a discover action
Workflow path from a generate index action
The only supported action after a generate index action is a clone action.
Figure 34 Workflow path from a generate index action
Workflow path from a VBA checkpoint discover action
The only supported action after a VBA checkpoint discover action is a VBA checkpoint
backup action.
Figure 35 Workflow path from a VBA checkpoint discover action
Workflow path from a VBA checkpoint backup action
VBA checkpoint backup cannot be the lead action in a workflow. You must precede the
VBA checkpoint backup action with a VBA checkpoint discover action.
Visual representation of traditional backup workflows
Figure 36 Traditional backup workflow
When you create actions for a workflow, a map provides a visual representation of the
actions in the second right pane of the Protection window of the Administration interface.
The oval icon at the beginning of the visual representation specifies the group to which
the workflow applies, the rounded rectangle icons identify actions, and the parallelogram
icons identify the destination pool for the action.
You can work directly in the visual representation of a workflow to perform the following
tasks:
l
Adjust the display of the visual representation by right-clicking and selecting one of
the following options:
n
Zoom In—Use to increase the size of the visual representation.
n
Zoom Out—Use to decrease the size of the visual representation.
n
Zoom Area—Use to limit the display to a single section of the visual
representation.
n
Fit Content—Use to fit the visual representation to the window area.
n
Reset—Use to reset the visual representation to the default settings.
Workflows
271
Data Protection Policies
n
Overview—To view a separate dialog box with a high-level view of the visual
representation and a legend of the icons.
l
View and edit the properties for the group, action, or destination pool by rightclicking the icon for the item and selecting Properties.
l
Create a group, action, or destination pool by right-clicking the icon for the item and
selecting New.
Creating a workflow in an existing policy
A policy can have one or more unique workflows.
Before you begin
l
Create a policy for the workflow.
l
(Optional but recommended) Create a group of client resources or save sets to assign
to the workflow.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Policies.
3. Select the policy for the workflow.
4. In the right pane of the window, select the Workflows tab.
5. Right-click an empty area of the Workflows tab and select New.
The New Workflow dialog box appears.
6. In the Name field, type the name of the workflow.
The maximum number of characters for the name of the group is 64.
7. In the Comment box, type a description for the workflow. The maximum number of
characters for the Comment field is 128.
8. From the Send Notifications list, select how to send notifications for the workflow:
l
To use the notification configuration that is defined in the policy resource to
determine when to send the notification, select Set at policy level.
l
To send notifications with information about each successful and failed workflow
and action, after all the actions in the workflow complete, select On Completion.
l
To send notifications with information about each failed workflow and action, after
all the actions in the workflow complete, select On Failure.
9. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
272
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
On Windows, type the following command: smtpmail -s subject -h
mailserver recipient1@mailserver recipient2@mailserver...
where:
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
10. In the Running group box, define when and how often the workflow runs.
a. To ensure that the actions contained in the workflow run when the policy or
workflow is started, in the Enabled box, leave the option selected. To prevent the
actions in the workflow from running when the policy or workflow that contains the
action is started, clear this option.
b. To ensure that the workflow starts at the time that is specified in the Start time
attribute, on the days that are defined in the action resource, in the AutoStart
Enabled box, leave the option selected. To prevent the workflow from running at
the time that is specified in the Start time attribute, clear this option.
c. To define the time to start the actions in the workflow, in the Start Time attribute,
use the spin boxes.
The default value is 9:00 P.M.
d. To define how frequently to repeat the actions that are defined in the workflow
over a 24 hour period, In the Interval attribute, use the spin boxes.
The default value is 24 hours, or once a day. When you select a value that is less
than 24 hours, the Interval End attribute appears. To define the last time to start a
workflow in a defined interval period, use the spin boxes .
e. To define the duration of time in which NetWorker can manually or automatically
restart a failed or canceled workflow, in the Restart Window attribute, use the spin
boxes.
If the restart window has elapsed, NetWorker considers the restart as a new run of
the workflow. NetWorker calculates the restart window from the start of the last
incomplete workflow. The default value is 24 hours.
For example, when you set the Start Time to 7:00 PM, the Interval to 1 hour, and the
Interval end time to 11:00 P.M., then the workflow automatically starts every hour
beginning at 7:00 P.M. and the last start time is 11:00 PM.
11. In the Groups group box, specify the protection group to which the workflow applies.
To use a group, select a protection group from the Groups list. To create a protection
group, click the + button that is located to the right of the Groups list.
12. The Actions table displays a list of actions in the workflow. To edit or delete an action
in the workflow, select the action and click Edit or Delete. To create one or more
actions for the workflow, click Add.
Workflows
273
Data Protection Policies
The Actions table organizes the information in sortable columns. Right-click in the
table to customize the attributes that appear.
13. To create the workflow, click OK.
Creating a workflow in a new policy
A policy must contain one or more workflows.
Procedure
1. In the left pane of the Protection window, expand Policies, and then select the policy
that you created.
2. In the right pane of the Protection window, select Create a new workflow.
3. In the Name field, type the name of the workflow.
The maximum number of characters for the name of the group is 64.
4. In the Comment box, type a description for the workflow. The maximum number of
characters for the Comment field is 128.
5. From the Send Notifications list, select how to send notifications for the workflow:
l
To use the notification configuration that is defined in the policy resource to
determine when to send the notification, select Set at policy level.
l
To send notifications with information about each successful and failed workflow
and action, after all the actions in the workflow complete, select On Completion.
l
To send notifications with information about each failed workflow and action, after
all the actions in the workflow complete, select On Failure.
6. In the Send notification attribute when you select the On Completion or On failure
option, the Command box appears. Use this box to configure how NetWorker sends
the notifications. You can use the nsrlog action to write the notifications to a log file
or configure an email notification.
The default notification action is to log the information to the
policy_notifications.log file. The policy_notifications.log file is
located in the /nsr/logs directory on Linux and the C:\Program Files\EMC
NetWorker\nsr\logs folder on Windows, by default. You can use the smtpmail
application on Windows or the default mailer program on Linux to send email
messages.
For example:
l
To log notifications to a file named policy_notifications.log, type the
following command:
nsrlog -f policy_notifications.log
l
On Linux, to send a notification email, type the following command:
mail -s subject recipient
l
For NetWorker Virtual Edition (NVE), to send a notification email, type the following
command:
/usr/sbin/sendmail -v recipient_email "subject_text"
l
On Windows, type the following command:
smtpmail -s subject -h mailserver recipient1@mailserver
recipient2@mailserver...
where:
274
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
n
-s subject—Includes a standard email header with the message and
specifies the subject text for that header. Without this option, the smtpmail
program assumes that the message contains a correctly formatted email
header and nothing is added.
n
-h mailserver—Specifies the hostname of the mail server to use to relay the
SMTP email message.
n
recipient1@mailserver—Is the email address of the recipient of the notification.
Multiple email recipients are separated by a space.
7. In the Running group box, define when and how often the workflow runs.
a. To ensure that the actions contained in the workflow run when the policy or
workflow is started, in the Enabled box, leave the option selected. To prevent the
actions in the workflow from running when the policy or workflow that contains the
action is started, clear this option.
b. To ensure that the workflow starts at the time that is specified in the Start time
attribute, on the days that are defined in the action resource, in the AutoStart
Enabled box, leave the option selected. To prevent the workflow from running at
the time that is specified in the Start time attribute, clear this option.
c. To define the time to start the actions in the workflow, in the Start Time attribute,
use the spin boxes.
The default value is 9:00 P.M.
d. To define how frequently to repeat the actions that are defined in the workflow
over a 24 hour period, In the Interval attribute, use the spin boxes.
The default value is 24 hours, or once a day. When you select a value that is less
than 24 hours, the Interval End attribute appears. To define the last time to start a
workflow in a defined interval period, use the spin boxes .
e. To define the duration of time in which NetWorker can manually or automatically
restart a failed or canceled workflow, in the Restart Window attribute, use the spin
boxes.
If the restart window has elapsed, NetWorker considers the restart as a new run of
the workflow. NetWorker calculates the restart window from the start of the last
incomplete workflow. The default value is 24 hours.
For example, when you set the Start Time to 7:00 PM, the Interval to 1 hour, and the
Interval end time to 11:00 P.M., then the workflow automatically starts every hour
beginning at 7:00 P.M. and the last start time is 11:00 PM.
8. To create the workflow, click OK.
After you finish
Create the actions that will occur in the workflow, and then assign a group to the
workflow. If a workflow does not contain a group, a policy does not perform any actions.
Editing a workflow
You can edit all the properties for a workflow, including the name, description, schedule,
notification settings, group, and actions.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Policies.
Workflows
275
Data Protection Policies
3. Select the policy for the workflow.
4. In the right pane of the window, select the Workflows tab.
5. In the right pane, perform one of the following tasks:
l
To modify multiple attributes in a single configuration resource by using the
Workflow Properties window, right-click the staging configuration and select
Properties.
l
To modify a specific attribute that appears in the resource window, place the
mouse in the cell that contains the attribute that you want to change, then rightclick. The menu displays an option to edit the attribute. For example, to modify the
Comment attribute, right-click the resource in the Comment cell and select Edit
Comment.
Note
To modify a specific attribute for multiple resources, press and hold the Ctrl key,
select each resource, and then right-click in the cell that contains the attribute that
you want to change. The menu displays an option to edit the attribute.
6. Edit the properties for the workflow. The properties are the same properties that you
specified when you created the workflow.
Note
When you add actions to an existing workflow that is associated with a group, you
only see the action types that are allowed in the action sequence.
7. Click OK.
Deleting a workflow
When you delete a workflow, the deletion process also deletes all actions for the
workflow.
The group that is assigned to the workflow is not deleted, however. The workflow
assignment for the group is removed from the group properties. You can assign the group
to a different workflow or delete the group.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Policies.
3. Select the policy for the workflow.
4. In the right pane of the window, select the Workflows tab.
5. Right-click the workflow, and select Delete.
A confirmation message appears.
6. Click Yes.
276
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Protection groups
Protection groups enable you to define a set of Client resources or save sets.
Assigning a protection group to a workflow
You can assign a protection group to a workflow either when you create or edit the group,
or when you create or edit the workflow.
Each workflow applies to only one protection group, and each protection group can be
assigned to only one workflow.
Procedure
l
To assign a protection group to a workflow when you create or edit the group, select
the workflow from the Workflow(Policy) list in the Create Group or Edit Group dialog
box.
l
To assign a protection group to a workflow when you create or edit the workflow,
select the group from the Groups list in the New Workflow or Workflow Properties
dialog box.
Editing a protection group
You can edit all properties for a protection group except for the group name and group
type.
To rename a protection group, first delete the group, and then re-create it with the new
name.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Groups.
3. Right-click the group, and select Properties.
The Edit Group dialog box appears.
4. Edit the properties for the protection group.
The properties are the same properties that you specified when you created the group.
To modify the clients in a protection group, perform on of the follow tasks:
l
To modify the clients in a dynamic group, in the Dynamic clients table, specify the
criteria that NetWorker uses to select clients for the group:
n
To back up all the Client resources that are configured on the NetWorker server
and have the Scheduled backup attribute enabled, select Choose all clients.
n
To generate a list of clients that is based on the value that is defined in the Tag
attribute of the Client resource, select the Clients with these tags option.
Specify the matching tag value in the Tags field and specify one tag on each
line.
Note
When you specify multiple tag values, the query uses an OR operation to match
the tags. For example, if you specify Sales and Support tag values, then the
query builds a list of clients that contain the tag Sales or Support.
l
To modify the clients in a Client group, from the Clients table, perform one of the
following actions in the Selected Clients column:
Protection groups
277
Data Protection Policies
n
To add a Client resource to the group, select the checkbox beside the name of
the Client resource.
n
To remove Client resources from the group, clear the checkbox next to the
name of the Client resource.
5. Click OK.
Deleting a protection group
Before you begin
Delete the workflow that is assigned to the protection group, or assign the workflow to a
different protection group. You cannot delete a protection group if it is assigned to a
workflow.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Groups.
3. Right-click the group, and select Delete.
A confirmation message appears.
4. Click Yes.
Actions
Actions are the key resources in a workflow for a data protection policy. An action is a
task that occurs on a work list. A work list is a list of pending work items, such a group of
Client resources or save sets.
You can chain multiple actions together to occur sequentially or concurrently in a
workflow.
Creating an action
The Policy Action wizard walks you through the steps to create an action. You can create
an action either when you are creating or editing a workflow, or as a separate process
from the workflow configuration.
Before you begin
Create the policy and workflow that contains the action.
Procedure
1. Open the Policy Action wizard by using one of the methods in the following table.
Table 48 Methods to create an action
Method
Steps
To create an action
during the workflow
configuration
Click Add in either the New Workflow dialog box or the Workflow
Properties dialog box.
To add additional
actions after the last
action in an existing
workflow
278
EMC NetWorker 9.0.x Administration Guide
a. In the Administration window, click Protection.
b. In the expanded left pane select Policies.
c. Select the policy.
Data Protection Policies
Table 48 Methods to create an action (continued)
Method
Steps
d. Select the workflow.
e. In the right pane, select the Actions tab.
f. Right-click an empty area of the Actions tab and select New.
Note
When you add actions to an existing workflow that is associated with a
group, you only see the action types that are allowed in the action
sequence.
To create the first action
in a workflow
a. In the Administration window, click Protection.
b. In the expanded left pane select Policies.
c. Select the policy.
d. Select the workflow.
e. In the right pane, select Create a new action.
To add an action before
an action in an existing
workflow
a. In the Administration window, click Protection.
b. In the expanded left pane select Policies.
c. Select the policy.
d. Select the workflow.
e. In the right pane, select the action that you want the new action to
precede and select Insert before.
Note
When you add actions to an existing workflow that is associated with a
group, you only see the action types that are allowed in the action
sequence.
2. In the Name field, type the name of the action.
The maximum number of characters for the action name is 64.
3. In the Comment field, type a description for the action.
4. To ensure that the action runs when the policy or workflow that contains the action is
started, in the Enabled box, select the option. To prevent the action from running
when the policy or workflow that contains the action is started, clear this option.
Note
When you clear the Enabled option, any action that occurs after a disabled action will
not start, even if the succeeding options are enabled.
5. From the Action Type list, select the action.
6. When you create the action as part of the workflow configuration, the workflow
appears automatically in the Workflow box and the box is grayed out.
Actions
279
Data Protection Policies
7. Specify the order of the action in relation to other actions in the workflow:
l
If the action is part of a sequence of actions in a workflow path, select the action
that should precede this action from the Previous box.
l
If the action should run concurrently with an action, select the concurrent action
from the Previous box, and then select the Concurrent checkbox.
8. The steps to go through the wizard depend on the action type that you select.
Editing an action
You can edit all the properties of an existing action.
Perform one of the following tasks to edit an action.
Procedure
l
Open the Policy Action wizard for the action by using one of the methods in the
following table.
Table 49 Methods to open the Policy Action wizard
Method
Steps
During workflow configuration
Select the action and then click Edit in either the New
Workflow dialog box or the Workflow Properties
dialog box.
From the Actions tab of the workflow
1. In the Administration window, click Protection.
2. In the expanded left pane select Policies.
3. Select the policy.
4. Select the workflow.
5. In the right pane, select the Actions tab.
6. Right-click the action, and select Properties.
From the visual representation of the
workflow
Right-click the action in the visual representation of the
workflow, and select Properties.
Edit the properties for the action, then click Configure.
l
Use the quick edit option in the Actions window of a Workflow resource. To modify a
specific attribute that appears in the resource window, place the mouse in the cell
that contains the attribute that you want to change, then right-click. The menu
displays an option to edit the attribute. For example, to modify the Comment attribute,
right-click the resource in the Comment cell and select Edit Comment.
Note
To modify a specific attribute for multiple resources, press and hold the Ctrl key,
select each resource, and then right-click in the cell that contains the attribute that
you want to change. The menu displays an option to edit the attribute.
280
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Deleting an action
You can delete an action in a workflow either when you are creating or editing a workflow,
or as a separate process from the workflow configuration.
If the action that you delete is part of a sequence of actions in a workflow, then you can
only delete the action if the removal of the action from the sequence would still result in a
valid workflow. The properties for other actions in a sequence are updated to reflect the
new sequence of actions after the deletion.
Procedure
l
To delete an action when you are creating or editing a workflow:
a. Select the action in either the New Workflow dialog box or the Workflow Properties
dialog box.
b. Click Delete.
A confirmation message appears.
c. Click Yes.
l
To delete an action as a separate process from workflow configuration:
a. In the Administration window, click Protection.
b. In the expanded left pane, select Policies.
c. Select the policy.
d. Select the workflow.
e. In the right pane, select the Actions tab.
f. Right-click the action and select Delete.
A confirmation message appears.
g. Click Yes.
Managing policies from the command prompt
The nsrpolicy command enables you to create, start, stop, and display the attribute of
policy, workflow, action, and group resources.
The nsrpolicy command requires specific privileges which are assigned based on
session authentication. NetWorker supports two types of session authentication. Tokenbased authentication, which requires you to run the nsrlogin before you run the
command and authenticates the user that runs the command against entries that are
defined in the External Roles attribute of a User Group resource. Classic authentication,
which is based on user and host information and uses the user attribute of a User Group
resource to authenticate a user. Classic authentication does not require an
authentication token to run the command. For example, if you run the command without
first running nsrlogin, NetWorker assigns the privileges to the user based on the
entries that are specified in the Users attribute of the User Group resource. When you use
nsrlogin to log in as a NetWorker Authentication Service user, NetWorker assigns the
privileges to the user based on the entries that are specified in the External Roles
attributes of the user Group resource. The EMC NetWorker Security Configuration Guide
This section provides some examples of how to manage data protection policies from a
command prompt.
Managing policies from the command prompt
281
Data Protection Policies
The UNIX man pages and the EMC NetWorker Command Reference Guide provide detailed
information about how to use the nsrpolicy command.
Creating Data Protection Policy resources from a command prompt
Use the nsrpolicy command to create Policy, Protection Group, and Workflow
resources.
Procedure
1. Optionally, use the nsrlogin command to authenticate a user and generate a token
for the nsrpolicy command.
Using nsrlogin for authentication and authorization on page 65 provides more
information.
2. Use the nsrpolicy command to create each Data Protection Policy resource.
a. To create the Policy resource, type: nsrpolicy policy create --policy_name
policy_name.
where policy_name is a unique name for the Policy resource.
b. To create a protection Group resource and add existing clients to the Group
resource, type: nsrpolicy group create client -g group_name -C
"client_name1,client_name2,client_name3..."
where:
l
group_name is a unique name of the Group resource.
l
client_name1,client_name2,client_name3... is a comma separated list of client
names to add to the group.
c. To create a workflow and associate the workflow with the new Policy and Group
resources, type: nsrpolicy workflow create --policy_name policy_name
--workflow_name workflow_name --group_name group_name
where:
l
policy_name is the name of the Policy resource.
l
group_name is the name of the Group resource.
l
workflow_name is a unique name for the Workflow resource.
3. Use the nsrpolicy display command to display the attributes for the new Data
Protection Policy resource.
l
To display a Policy resource, type: nsrpolicy action display --policy_name
policy_name
Where policy_name is the name of the Policy resource.
l
To display a Workflow resource, type: nsrpolicy action display -workflow_name workflow_name
Where workflow_name is the name of the Workflow resource.
l
To display a Group resource, type: nsrpolicy action display --group_name
group_name
282
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
Creating Action resources from a command prompt
Use the nsrpolicy action create command to create Action resources
Procedure
1. Optionally, use the nsrlogin command to authenticate a user and generate a token
for the nsrpolicy command.
2. Use the nsrpolicy action create command to create the Action resource.
For example: nsrpolicy action create action_type --policy_name
policy_name --workflow_name workflow_name -A backup_action_name [-d
preceding_action_name]
Where:
l
action_types are one of the following: check-connectivity, probe, backup
traditional, backup snapshot, clone, discover-nas-snap, index-nas-snap, serverbackup, expire, vba-checkpoint-discover, vba-checkpoint-backup.
l
policy_name is the name of an existing Policy resource that contains this action.
l
workflow_name is the name of an existing Workflow resource in the Policy resource
that contains the action.
l
action_name is a unique name for the new Action resource.
l
preceding_action_name is the name of the Action that precedes the new action in
the Workflow.
For example:
l
To create a traditional backup action and add this action to the SQL workflow in
the SQL_hosts policy resource, type: nsrpolicy action create backup
traditional --policy_name SQL_hosts --workflow_name SQL -A
SQL_backup.
l
To create a clone action and insert the clone action immediately after a backup
action created in the SQL workflow, type: nsrpolicy action create backup
traditional --policy_name policy_name SQL_hosts --workflow_name
SQL -A SQL_clone -d SQL_backup.
Starting, stopping, and restarting workflows from a command prompt
Use the nsrpolicy command to start, stop, and restart the actions in a workflow.
Starting a workflow from a command prompt
You can start all actions that are contained in one workflow in a policy, or start all actions
for one client in a workflow.
l
To start all actions in a specific workflow in a Policy resource, type the following
command: nsrpolicy start --policy_name "policy_name" -workflow_name "workflow_name"
Note
You cannot start another instance of a workflow that is already running.
l
To start all actions for a specific client in a workflow, type the following command:
nsrpolicy start --policy_name "policy_name" --workflow_name
"workflow_name" --client_list client_list
Creating Action resources from a command prompt
283
Data Protection Policies
Note
You can use this command to start actions for failed clients in a workflow that is
currently running.
where:
l
"policy_name" is the name of the Policy resource that contains the workflow that you
want to start.
l
"workflow_name" is the name of the Workflow resource that you want to start.
l
client_list is a comma-separated list of host names for the clients in the workflow
whose actions you want to start.
Stopping all actions in a workflow from a command prompt
To stop all actions in a specific workflow in a policy, type the following command:
nsrpolicy start --policy_name "policy_name" --workflow_name
"workflow_name"
where:
l
"policy_name" is the name of the Policy resource that contains the workflow that you
want to stop.
l
"workflow_name" is the name of the Workflow resource that you want to stop.
Restarting a workflow from a command prompt
To restart all actions in a workflows that a Policy resource contains, type the following
command: nsrpolicy restart --policy_name "policy_name" --workflow_name
"workflow_name"
where:
l
"policy_name" is the name of the Policy resource that contains the workflow that you
want to restart.
l
"workflow_name" is the name of the Workflow resource that you want to restart.
Running a workflow with action overrides
Before an action starts NetWorker defines how to run the action by reviewing the
attributes values of the policy, workflow, and action resources. In NetWorker 9.0.1 and
later, the nsrworkflow command line option -A enables you to override attribute
values that NetWorker uses to run the action. Actions which support override values are:
traditional and snapshot backups, probe, and clone.
Specify the -A option in the format -A "action_name cmd_line_flags", where:
l
action_name—Specifies the name of the action resource.
l
cmd_line_flags—Defines a list of command line flags and the new parameter value.
Use escaped double quotes or single quotes for action names or parameters that contain
spaces or special characters. For example: -A "\"actionname\" -l full" or -A
"'action name' -l full"
For example, to specify an override on the level of a backup action and the retention time
of the backup and clone actions in the workflow, type the following command:
nsrworkflow -p Backup -w workflow_name -A "action_name -l level -y
\"retention_period\"" -A "action_name -y \"retention_period\""
To specify a backup level override of 3 and a retention period of 3 years for the backup
and clone actions for a workflow named fs_backup_clone, an backup action named
backup and a clone action named clone, type the following command:
284
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
nsrworkflow -p Backup -w fs_backup_clone -A "backup -l 3 -y \"3 years
\"" -A "clone -y \"3 years\""
Displaying Data Protection Policy resource configurations
NetWorker stores Data Protection Policy resource configuration information in a
JavaScript Object Notation (JSON) string. Displaying the contents of the JSON string
provides you with the ability to view the hierarchical relationship between the resources .
Use the nsrpolicy policy display command to display the configuration
attributes for a Policy resource and all the Workflow and Action resources that are
associated with the Policy resource:
nsrpolicy policy display -p policy_name
where policy_name is the name of the Policy resource. Enclose Policy names that contain
spaces in quotation marks.
For example, to display the resources in the Server Protection Policy resource, type the
following command:
nsrpolicy policy display -p "Server Protection"
Output similar to the following appears
{
"policyName": "Server Protection",
"policyComment": "Default policy for server that includes
server backup and maintenance",
"policySummaryNotification": {
"policyCompletionNotificationAction": "nsrlog -f
policy_notifications.log",
"policyCompletionNotificationExecuteOn": "completion"
},
"policyWorkflows": [
{
"workflowName": "Server backup",
"synthesisRoot": [
"NSR group/Server backup",
"NSR Snapshot Policy/Server backup"
],
"workflowActions": [
{
"actionName": "Server db backup",
"actionSpecific": {
"actions": {
"actionType": "server backup",
"asbDestinationPool": "Default",
"asbDestinationStorageNode": "nsrserverhost",
"asbPerformBootstrap": true,
"asbPerformCFI": true,
"asbRetentionPeriod": "1 Months"
}
},
"actionSchedulePeriod": "month",
"actionScheduleActivity": [
"full",
"1",
"1",
Displaying Data Protection Policy resource configurations
285
Data Protection Policies
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1",
"1"
],
"actionComment": "Perform server database backup that is
required for disaster r
ecovery",
"actionCompletionNotification": {
"policyCompletionNotificationAction": "",
"policyCompletionNotificationExecuteOn": "ignore"
},
"actionConcurrent": false,
"actionDrivenBy": "",
"actionEnabled": true,
"actionFailureImpact": "continue",
"actionHardLimit": "00:00",
"actionInactivityTimeout": 30,
"actionParallelism": 0,
"actionRetries": 1,
"actionRetryDelay": 30,
"actionSoftLimit": "00:00"
},
{
"actionName": "Expiration",
"actionSpecific": {
"actions": {
"actionType": "expire"
}
},
"actionSchedulePeriod": "week",
"actionScheduleActivity": [
286
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
"exec",
"exec",
"exec",
"exec",
"exec",
"exec",
"exec"
],
"actionComment": "Expire the savesets",
"actionCompletionNotification": {
"policyCompletionNotificationAction": "",
"policyCompletionNotificationExecuteOn": "ignore"
},
"actionConcurrent": false,
"actionDrivenBy": "Server db backup",
"actionEnabled": true,
"actionFailureImpact": "continue",
"actionHardLimit": "00:00",
"actionInactivityTimeout": 30,
"actionParallelism": 0,
"actionRetries": 1,
"actionRetryDelay": 30,
"actionSoftLimit": "00:00"
}
],
"workflowAutostartEnabled": true,
"workflowComment": "Perform server backup",
"workflowCompletionNotification": {
"policyCompletionNotificationAction": "",
"policyCompletionNotificationExecuteOn": "ignore"
},
"workflowDescription": "server backup action;expire action;",
"workflowEnabled": true,
"workflowGroups": [
"Server Protection"
],
"workflowInterval": "24:00",
"workflowNextstart": "2015-06-13T10:00:00-0400",
"workflowRestartWindow": "12:00",
"workflowStarttime": "10:00"
},
{
"workflowName": "NMC server backup",
"synthesisRoot": [
"NSR group/NMC server backup",
"NSR Snapshot Policy/NMC server backup"
],
"workflowActions": [
{
"actionName": "NMC server backup",
"actionSpecific": {
"actions": {
"actionType": "backup",
"actionBackupSubtypeSpecific": {
"backupSubtypes": {
"abBackupSubtype": "traditional",
Displaying Data Protection Policy resource configurations
287
Data Protection Policies
"abtDestinationPool": "Default",
"abtEstimate": false,
"abtFileInactivityAlertThreshold": 0,
"abtFileInactivityThreshold": 0,
"abtRevertToFullWhenSyntheticFullFails": true,
"abtTimestampFormat": "none",
"abtVerifySyntheticFull": true
}
},
"abDestinationStorageNode": [
"nsrserverhost"
],
"abRetentionPeriod": "1 Months",
"abOverrideRetentionPeriod": false,
"abOverrideBackupSchedule": false,
"abClientOverridesBehavior": "clientCanOverride"
}
},
"actionSchedulePeriod": "week",
"actionScheduleActivity": [
"full",
"full",
"full",
"full",
"full",
"full",
"full"
],
"actionCompletionNotification": {
"policyCompletionNotificationAction": "",
"policyCompletionNotificationExecuteOn": "ignore"
},
"actionConcurrent": false,
"actionDrivenBy": "",
"actionEnabled": true,
"actionFailureImpact": "continue",
"actionHardLimit": "00:00",
"actionInactivityTimeout": 30,
"actionParallelism": 100,
"actionRetries": 1,
"actionRetryDelay": 30,
"actionSoftLimit": "00:00"
}
],
"workflowAutostartEnabled": true,
"workflowComment": "Perform NMC database backup",
"workflowCompletionNotification": {
"policyCompletionNotificationAction": "",
"policyCompletionNotificationExecuteOn": "ignore"
},
"workflowDescription": "Traditional Backup to pool Default,
with expiration 1 Months;",
"workflowEnabled": true,
"workflowGroups": [
"NMC server"
],
288
EMC NetWorker 9.0.x Administration Guide
Data Protection Policies
"workflowInterval": "24:00",
"workflowNextstart": "2015-06-12T14:00:00-0400",
"workflowRestartWindow": "12:00",
"workflowStarttime": "14:00"
}
]
}
Troubleshooting policies
This section provides information about issues related to the configuration and
management of policy resources.
Unable to start because the Group for this workflow is empty
This message appears when you use the Start Individual Client option to start actions for
specific clients in the Server backup workflow. NetWorker does not support the Start
Individual Client option for the Server backup workflow. To resolve this issue, start all
actions for all the clients in the workflow.
Troubleshooting policies
289
Data Protection Policies
290
EMC NetWorker 9.0.x Administration Guide
CHAPTER 5
Backup Options
This chapter contains the following topics:
l
l
l
l
l
l
l
Overview of resources that support backups....................................................... 292
Save sets............................................................................................................ 292
Backup levels......................................................................................................295
Backup scheduling..............................................................................................308
Backup retention.................................................................................................314
General backup considerations........................................................................... 317
Directives............................................................................................................ 323
Backup Options
291
Backup Options
Overview of resources that support backups
NetWorker provides you with resources that enable you to customize what data is in the
backup, when the backup occurs, and how the backup occurs.
The following table summarizes each supporting resource. Many of the resources require
planning and configuration on the NetWorker server or on the client itself before the
backup occurs.
Table 50 Resource overview
Resource
Description
Example
Backup
levels
Defines whether to back up all data on
the client, or only data that has changed.
Perform a full backup to back up all
files, regardless of whether they have
changed, or an incremental backup to
back up only files that changed since
the last backup.
Schedules
Defines the backup level to perform on
each day.
Perform a full backup on Sunday, and
an incremental backup on all other
days of the week.
Time policies Defines time periods. Use time policies
Backups for a client are maintained in
to define save set retention. Save set
the database, and can be browsed for
retention is how long the save set entries recovery for a month.
are maintained in the media database
and client file indexes.
Directives
Specifies resources that contain special
instructions that control how the
NetWorker server processes files and
directories during backup and recovery.
For example, encryption and
compression.
A directive specifies that the backup
should skip files with a .tmp
extension.
Save sets
The collection of data items that are backed up during a backup session between the
NetWorker server and a Client resource is called a save set.
A save set can consist of the following:
l
A group of files or entire file systems.
l
Application data, such as a database, or operating system settings.
You can use the predefined save sets for scheduled backups, or specify a list of save sets
to back up for a client resource in the Save set attribute on the General tab of the Client
Properties dialog box.
Predefined save sets include the DISASTER_RECOVERY:\ save set and the ALL save
set.
When you specify a list of save sets for a client resource, the following guidelines apply:
l
292
For Windows operating systems, use the same pathname case that the Windows file
system uses. Although most file systems are case-independent, the NetWorker
EMC NetWorker 9.0.x Administration Guide
Backup Options
software cross-platform indexing system is case-sensitive. Always specify the
Windows drive letter in uppercase.
l
Place multiple entries on separate lines. For example, to back up a log file directory
that is named C:\Docs\CustomerLogs, and all data that is contained in a
directory that is named D:\accounting, type the following entries:
C:\Docs\CustomerLogs
D:\accounting
l
l
For clients that use non-ASCII locales on UNIX platforms, or for Windows clients that
are configured from a UNIX host that uses non-ASCII locales, special considerations
apply when you type a path or file name in the Save set attribute:
n
Type the path or file name in the locale that was used when you created the path
or file. If using a different locale when you type a path or file name, backups fail
with a No such file or directory error message.
n
Either use the ALL save set in this situation, or log in to the client by using the
correct locale and then configure the client from that computer.
To back up a UNIX or Linux host that contains path or file names with multiple
locales, create a separate Client resource for each locale. For example, to configure a
multi-locale UNIX host with data in both Japanese and French, create two different
Client resources. One Client resource to define the save sets for the Japanese data,
and one Client resource to define the save sets for the French data.
The ALL save set
The ALL save set is the default save set when you create a Client resource.
Save sets included in the ALL save set
The following table provides a list of the save sets that are in the ALL save set for
supported operating systems.
Table 51 Data in the ALL save set
Operating
system
Windows
Files
l
DISASTER_RECOVERY:\
l
Noncritical volumes
Mac OS X
All local and mounted volumes
UNIX
l
When the backup starts, the savefs process reads the contents of
the /etc/vfstab file on Solaris clients, the /etc/fstab file on HP-UX
and Linux clients, or the /etc/filesystems file on AIX clients. The
contents of the file are compared to the currently mounted file systems and
BTRFS sub-volumes. Only currently mounted file systems and BTRFS subvolumes that are configured in these files are backed up. When NetWorker
encounters a sub-directory that has a sub-volume ID that differs from the
parent sub-volume ID, NetWorker will not backup the contents of the
subdirectory, unless you specify the save -x in the Backup command field in
the properties of the Client resource.
l
For a Solaris sparse or whole root zone client, all mounted file systems in the
sparse or whole root zone that are not normally skipped, such as NFS, are
backed up.
The ALL save set
293
Backup Options
Table 51 Data in the ALL save set (continued)
Operating
system
Files
l
ZFS file systems are backed up.
l
If the save set name includes a symbolic link, a save set recovery is not
supported.
Save sets excluded from the ALL save set
The following directories, file systems, and files are excluded from the ALL save set:
Table 52 File systems excluded from the ALL save set
l
hsfs
l
sharefs
l
dfs
l
binfmt_misc
l
nucam
l
proc
l
nfs2
l
autofs
l
usbfs
l
fdfs
l
fd
l
nfs3
l
iso9060
l
devpts
l
xx
l
cachefs
l
nfs3perf
l
udf
l
smbfs
l
none
l
lofs
l
profs
l
sysfs
l
swap
l
mntfs
l
nfs4
l
debugfs
l
tmp
l
ctfs
l
nfs
l
subfs
l
tmpfs
l
objfs
l
brfs
l
usbdevfs
l
nucfs
NOTICE
When you use the ALL save set for a backup, the NetWorker software creates a temporary
file similar to a directive under each drive. The file name uses the format drive
guid.txt and lists the files that are excluded from the backup. The file is temporary
and is automatically deleted when the backup completes.
Keywords for scheduled file system backups
You can use special keywords with the ALL save set to define the file systems to include
in a backup. The following table provides a list of the special ALL save sets and the
backup behavior.
Table 53 Special ALL save sets
Special ALL save Backup behavior
set syntax
allfile_system
l
l
294
EMC NetWorker 9.0.x Administration Guide
Only back up locally mounted file systems of a particular type, where
file_system is zfs, ntfs, btrfs, or ext3. For example:
n
all-zfs backs up all locally mounted ZFS file systems on a Solaris
host.
n
all-btrfs backs up all mounted BTRFS sub-volumes that appear
in the /etc/fstab file.
File systems such as NFS that are normally skipped are still skipped.
Backup Options
Table 53 Special ALL save sets (continued)
Special ALL save Backup behavior
set syntax
all-mounts
all-local
all-global
l
The EMC NetWorker Online Software Compatibility Guide provides a list of
the supported file system for each operating system.
l
On UNIX clients, back up all currently mounted file systems.
l
On Windows clients, the all-mounts save set is equivalent to the
ALL save set.
l
File systems such as NFS that are normally skipped are still skipped.
l
For a global zone client, the file systems in the sparse or whole root
zone on the physical host are backed up. File systems in the global zone
are skipped.
l
For a sparse or whole root zone client, the all-local save set is
equivalent to the ALL save set.
l
For a global zone client, all file systems in the global zone are backed
up. All sparse and whole root zone file systems on the physical host are
skipped.
l
For a Solaris sparse or whole root zone client, the all-global save
set is equivalent to the ALL save set.
Backup levels
You can specify the level of the backup to be performed during scheduled backups.
When you limit the frequency of full backups, you help maintain server efficiency while
still ensuring that data is protected. Different backup levels enable you to balance the
amount of time that is required to complete a backup with the number of volumes that
are required to recover from a disk failure.
The following table describes the available backup levels.
Table 54 Backup levels
Backup level
Function
Full
Results in a back up of all files, regardless of whether the files have changed.
Incremental
Results in the back up of the files that have changed since the last backup,
regardless of the level of the last backup.
Cumulative
incremental
Results in the back up of all files that have changed since the last full backup.
Logs only
Results in the back up of the transaction log for databases that are created by
a NetWorker module. For example, the NetWorker Module for Databases and
Applications, the NetWorker Module for Microsoft, or the NetWorker Module
for SAP.
Backup levels
295
Backup Options
Table 54 Backup levels (continued)
Backup level
Function
Synthetic full
Results in the back up of all data that has changed since the last full backup
and subsequent incremental backups, to create a synthetic full backup.
Skip
Skips the scheduled backup. For example, you can skip a backup on a
holiday if no one is available to change or add more media volumes.
Comparing backup levels
Evaluate the advantages and disadvantages of each backup level to develop the backup
strategy for an environment.
The following table lists key advantages and disadvantages of each backup level.
Table 55 Advantages and disadvantages of backup levels
Backup level
Advantages
Full
l
Incremental
Cumulative
incremental
Logs only
Synthetic full
Faster recovery
Disadvantages
l
Slower backups
l
High server load
l
High load on the client and
network
l
Uses more volume space
l
Faster than a full backup
l
Slow recovery
l
Low server load
l
l
Uses less volume space than a full
backup
Data can spread across multiple
volumes
l
Faster than a full backup
l
Slow recovery
l
Low server load
l
l
Uses the least amount of volume
space
Data can spread across multiple
volumes
l
Faster than a full or incremental
backup
l
Slow recovery
l
l
Low server load
Data can spread across multiple
volumes
l
Faster than a full backup
l
High load on the storage node
l
Faster recovery
l
l
Low load on the server, client, and
network
Requires at least two volume
drives
l
Uses the most volume space
l
Requires fewer volumes for
recovery
Review the following additional considerations when selecting backup levels:
296
EMC NetWorker 9.0.x Administration Guide
Backup Options
l
If you have only one stand-alone storage device and the full backup does not fit on a
single piece of media, an operator must be available to monitor the backup, and
change the media.
l
Full backups cause the online indexes to grow more rapidly than incremental or
cumulative incremental backups.
l
Cumulative incremental backups serve as checkpoints in schedules because they
collect all the files that have changed over several days, or even weeks, into a single
backup session.
l
Synthetic full backups provide the same benefits at the same cost as full backups.
The difference is that synthetic full backups are less taxing on the network and client
because a new full backup is created from a previously created full or synthetic full
backup and subsequent incremental backups.
Backup levels and data recovery requirements
The schedule and configuration of backup levels directly affects how long a recovery from
a disk failure takes and how many backup volumes are needed for the recovery.
Plan the backup levels to minimize the number of volumes or the amount of disk space
that is used to store the data. The fewer the number of volumes that are required to
recover from a disk failure, the less the time that you require to restore the data.
Note
You can also reduce the size and the time it takes to back up data by using directives. For
example, use a directive to skip certain files or file systems when performing a backup.
The following example illustrates how the backup levels affect the requirements for data
recovery.
In the following figure:
l
Day 1—A full backup is run.
l
Day 2— An incremental backup saves all files that have changed since the full
backup.
l
Day 3—Another incremental backup saves all files that have changed since Day 2.
l
Day 4—A cumulative incremental backup saves all files that have changed since the
full backup on Day 1.
Backup levels and data recovery requirements
297
Backup Options
Figure 37 Incremental and cumulative incremental backup levels
To recover all data from a disk failure on Day 4, you need the data from the full backup
from September 30 and the cumulative incremental backup on Day 4. You no longer need
the data from Day 1, 2, and 3, because the volume with the cumulative incremental
backup includes that information.
Backup levels for the online indexes
The backup of the NetWorker server online indexes (client file index and media database)
occur in a separate policy.
NetWorker automatically creates a server backup action in the Server Backup workflow of
the Server Protection policy. By default, a full backup of the media database, resource
files, and the NetWorker Authentication Service database occurs daily. A full backup of
the client file indexes occur on the first day of the month. An incremental backup of the
client file indexes occur on the remaining days of the month.
Synthetic full backups
A synthetic full backup combines a full backup and subsequent incremental backups to
form a new full backup. A synthetic full is equivalent to a traditional full backup and can
be used in all the same ways as a traditional full backup.
A synthetic full save set includes data that was backed up between the full backup and
the last incremental backup. After a synthetic full backup occurs, the next synthetic full
backup includes data that was backed up between the previous synthetic full backup,
and subsequent incremental backups.
During a traditional full backup, client data is sent over the network to the NetWorker
storage nodes, which can have a negative effect on client network performance. For
synthetic full backups, however, the NetWorker software analyzes the full backup and
subsequent incremental backups, extracts the most current versions of files, and then
streams the data into a new full backup. Synthesizing the new full backup does not
include the client machines and localizes the network traffic to the NetWorker server and
storage nodes.
Performing synthetic full backups also reduces recovery time because the data is
restored from the single synthetic full backup instead of from the last full backup and the
incremental backups that follow it.
298
EMC NetWorker 9.0.x Administration Guide
Backup Options
Synthetic full backups do not eliminate the requirement for full backups. It is
recommended to perform full backups on a monthly or quarterly basis, and limit the
number of incremental backups.
How a synthetic full backup is created
When a synthetic full backup operation starts, the NetWorker software performs an
incremental backup of the save set and then adds that to the full and incremental
backups that are already in place for the synthetic full process. Then the synthetic full
backup occurs.
The following figure illustrates how a synthetic full backup is created.
Figure 38 Synthetic full backups
In this example, the synthetic full backup operation creates the incremental backup at T4.
Then a synthetic full backup is created by combining the full backup at T1 with the
subsequent incremental backups at T2, T3, and T4 to form a synthetic full backup at T4 +
Delta. The save set at T4 + Delta is equivalent to a full backup that is taken at T4.
The T4 + Delta represents a small time change of one or two seconds from the time of T4,
since two separate save sets cannot be assigned the exact same save set time. For
example, if T4 is created at 1334389404, then T4+Delta is created at 1334389405, with
a difference of one second.
The synthetic full save set includes only files that are covered by save sets up to T4 at
1334389404. The incremental backup after the synthetic full backup at 1334389405
includes all changes since 1334389404. Note that the synthetic full backup does not
include the changes since T4, since only one save set can exist at any particular time.
After a synthetic full backup is performed, the next synthetic full backup combines the
previous synthetic full backup and subsequent incremental backups.
When to use synthetic full backups
Synthetic full backups are supported only for backups of file system data with NetWorker
8.0 and later.
Synthetic full backups provide the most benefit in the following environments:
l
The backup window is less than the amount of time it takes to perform a full backup.
l
A client is at a remote location, and data transfer over the network to the server is a
performance issue for either the network or the client.
l
Network bandwidth is limited.
l
Large backups over the network are cost-prohibitive.
Synthetic full backups include only the NetWorker server and storage node. If all the data
is on a few storage nodes, then the network overhead for creating the synthetic full
backup can be drastically reduced when compared to a traditional full backup of the
same save sets.
Synthetic full backups
299
Backup Options
NOTICE
Under most conditions, synthetic full backups can free network bandwidth and client
resources. However, a synthetic full backup might take longer to run on the storage node
than a full backup because incremental backups are combined into a synthetic full
backup. Without proper planning, synthetic full backups might affect the performance of
the storage node.
To manage resource usage, perform synthetic full operations outside of the normal
backup window. Also, synthetic full backups do not eliminate the requirement for full
backups. It is best practice to schedule and perform full backups on a monthly or
quarterly basis and limit the number of incremental backups.
Requirements for synthetic full backups
Ensure that the environment meets the requirements for synthetic full backups.
Save set requirements for synthetic full backups
All save sets participating in the construction of a synthetic full save set must meet the
following requirements:
l
Be file system save sets.
l
Retain the same client name and save set name during the incremental and full
backups that combine to form the synthetic full backup.
l
Be browsable in the online index.
l
Be created with NetWorker 8.0 or later.
Do not perform synthetic full backups with the following types of save sets:
l
NDMP, SCSI, VCB, or snapshot save sets.
l
Save sets that contain backups of raw disk file partitions.
l
Save sets that contain database systems such as Microsoft Exchange and Oracle.
l
Save sets where the backup command with save is not used.
l
The Save set attribute for the client resource contains the DISASTER RECOVERY:\
save set or the ALL save set on Windows.
When you use the ALL save set with synthetic full and virtual synthetic full backups,
the noncritical volumes save successfully. However, critical volumes including
DISASTER_RECOVERY:\ are not backed up. The nsrconsolidate() command
is unable to process the DISASTER_RECOVERY:\ save set. The client then runs a
traditional full backup for the DISASTER_RECOVERY:\ save set.
Backups that are performed during a checkpoint restart might be in a synthetic full
backup, if the other requirements for synthetic full backups are met.
For UNIX clients, include the forward slash to designate root (/) when specifying a save
set name for the client resource. Otherwise, the synthetic full backup fails. For example,
specify /tmp instead of tmp.
For Windows clients, include the backslash (\) when specifying a drive letter in a save set
name for the client resource. Otherwise, the synthetic full backup fails. For example,
specify D:\ instead of D:.
Client resource configuration requirements for synthetic full backups
Ensure that the Backup renamed directories attribute is enabled on the General tab of
the Client Properties dialog box for the Client resource. Select View Diagnostic Mode in
300
EMC NetWorker 9.0.x Administration Guide
Backup Options
the Administration interface to access the Backup renamed directories attribute in the
Client Properties dialog box.
If you configure multiple policy workflows to run concurrently, set the Parallelism
attribute to 40 for the Client resource for the NetWorker server. The Parallelism attribute
is available on the Globals (1 of 2) tab of the Client Properties dialog box. Setting the
attribute to 20 limits the number of concurrent synthetic full operations to 20. Divide the
parallelism setting by two to control the number of concurrently running synthetic full
operations. The best number of concurrent synthetic full operations depends on the
following criteria:
l
Configuration of the NetWorker server.
l
Size of the save sets and number of clients.
l
Number of nsrpolicy instances that are concurrently running.
Backup storage for synthetic full backups
Configure a Client resource for the NetWorker storage node that you use for the synthetic
full backup. A client connection license for this storage node is not used if the storage
node is not backed up.
There must be at least two available attached devices to perform a synthetic full backup:
one for reading the backup data, and one for writing the backup data to a synthetic full
backup.
You can store synthetic full backups on any device that can be used in a traditional full
backup. However, since synthetic full backups include concurrent recover and save
operations, it is strongly recommended that you direct synthetic full backups to devices
that can perform concurrent operations, such as Data Domain devices or Advanced File
Type Devices (AFTDs). Using these device types allows the NetWorker software to
automatically handle volume contention, where the same volume is required for both
reading and for writing simultaneously. These devices typically offer better performance.
You can use other devices such as tape drives, VTLs, and basic file devices as the
destination for synthetic full backups, but careful preparation is required for the backup
to succeed. The backup must be configured so that the destination volume does not
contain any of the sources save sets that are used for the synthetic full backup. Also, for
tape media, ensure that there are enough available drives to allow for concurrent
recovery of the source data and for saving the synthetic full backup. Without careful
planning, synthetic full backups to tape, VTL, or basic file devices might stall because of
volume contention.
To direct a synthetic full backup to a dedicated pool, configure a separate backup action
for synthetic full backups in the data protection policy, and select the pool as the
destination pool in the backup action for the synthetic full backup.
Scheduling considerations for synthetic full backups
A synthetic full backup is resource intensive because it concurrently performs both
recover and save operations. As a result, it is best to perform synthetic full operations
outside of the normal backup window.
You can do this by creating separate workflows in a data protection policy for synthetic
full backups. When using synthetic full backups, do not exceed the time interval of one
month between traditional full backups.
To maintain current resource usage, which is defined as the space usage in the backup
media and client file indexes, run synthetic full backups in place of traditional full
backups. Running synthetic full backups more frequently than traditional backups are
currently run results in the consumption of more space in the backup media and client
file indexes.
Synthetic full backups
301
Backup Options
For example, if a full backup occurs once a week, you can replace the full backup with an
incremental backup followed by a synthetic full backup without increasing the backup
space usage.
If you perform a full backup on Sunday and then incremental backups on Monday
through Saturday, then consider changing to the following schedule:
l
Full backup on the first Sunday of the month.
l
Incremental backups on Monday through Saturday.
l
Synthetic full backups on the second, third, fourth, and fifth Sunday of the month.
Support for directives with synthetic full backups
You can use the compressasm and aes (encryption) directives with synthetic full
backups.
When using directives with synthetic full backups, consider the following:
l
If directives were applied to save sets during the full and incremental backups that
are part of the synthetic full backup, the synthetic full backup does not remove those
directives.
l
Any directives, including the compressasm and aes directives, that were applied to
the full and incremental backups that are part of the synthetic full backup are not
applied again.
l
Do not use directives for synthetic full backups that are stored on a Data Domain
device.
l
Unsupported directives are ignored during a synthetic full backup.
Review the nsrconsolidate syntax in the EMC NetWorker Command Reference Guide or
the UNIX man pages for more information.
NOTICE
Directives do not apply to virtual synthetic full backups.
Recovery storage node selection for synthetic full backups
The storage node that is used for recovery depends on whether the required volume is
mounted.
If the required volume is already mounted, then the storage node where the volume is
mounted is used for recovering data.
If the required volume is not mounted, then the recovery storage node is selected based
on the value in the Recover storage node attribute on the Globals (2 of 2) tab of the Client
Properties dialog box for the Client resource. Select View Diagnostic Mode in the
Administration interface to access the Recover storage node attribute in the Client
Properties dialog box.
302
EMC NetWorker 9.0.x Administration Guide
Backup Options
Performing synthetic full backups
You can schedule synthetic full backups from the Administration window, or perform a
manual incremental synthetic full backup from the command prompt.
Performing scheduled synthetic full backups
Perform scheduled synthetic full backups by configuring a data protection policy with a
traditional backup action.
Procedure
1. Ensure that the environment meets the requirements that are provided in
Requirements for synthetic full backups on page 300.
2. Create a group to define the clients for the synthetic full backups:
l
Create a basic client group to specify a static list of clients.
l
Create a dynamic client group to specify a dynamic list of Client resources.
When the backup starts, the NetWorker policy engine dynamically generates a list
of Client resources that match the tags that are specified for the group.
Create separate groups for Windows clients and UNIX clients. Do not mix clients with
different operating system types in the same group.
3. Create a policy.
Policies provide a container for the workflows, actions, and groups that support and
define the backup action.
4. Create a workflow.
Workflows define the start time for a series of actions, the order of actions in a
sequence, and the group of client resources for which the action occurs.
5. Use the Policy Action wizard to create a traditional backup action with the following
settings:
l
In the schedule area of the Choose Action Type page, click the icon on each day to
specify the type of backup to perform. The following icon indicates that a synthetic
full backup will occur on the selected day:
l
On the Options page, leave the Verify synthetic full option selected to verify the
integrity of the new index entries that are created in the client file index for the
synthetic full backup.
l
On the Options page, leave the Revert to full when synthetic full fails option
selected to perform a full backup of the save set if the synthetic full backup fails.
Performing manual synthetic full backups
Run the nsrconsolidate program from the command line of the NetWorker server to
perform a manual synthetic full backup of a save set for a client.
Use the –c option to specify the client name, and the –N option to specify the save set
name, with the nsrconsolidate command. You can also use the –C option to specify
both the client and save set name together, the –S option to specify the save set ID
(instead of the save set name), and the –t and –e options to specify the start time and
end time for the save set, respectively.
The value that you specify for a save set name, client name, file name, or directory name
with nsrconsolidate for a Windows client is case-sensitive because the NetWorker
Synthetic full backups
303
Backup Options
software cross-platform indexing system is case-sensitive. A best practice is to always
specify the Windows drive letter in uppercase.
When you run multiple nsrconsolidate commands, run fewer commands that include
many save sets instead of multiple commands with fewer save sets. This strategy helps
nsrconsolidate to manage the number of concurrent synthetic full operations and
reduce resource usage. The best number of concurrent synthetic full operations depends
on the following criteria:
l
Configuration of the NetWorker server.
l
Size of the save sets and number of clients.
l
Number of nsrpolicy instances that are concurrently running.
The EMC NetWorker Command Reference Guide or the UNIX man pages provide details on
nsrconsolidate.
Validating synthetic full backups
You can validate VSF backups by using the mminfo command, the Media window of the
Administration interface, and the savegrp logs.
Validating synthetic full backups with the mminfo command
The following table lists the mminfo commands with applicable switches for validating
synthetic full backups.
Table 56 mminfo commands for synthetic full backup validation
Command with switches
Description
mminfo –aS
Shows detailed information about synthetic full
backups, including information about the save
sets used to form the synthetic full backup.
mminfo –q syntheticfull –c client -N
save_set
Queries all synthetic full save sets for the specified
client and save_set.
Validating synthetic full backups in the Media window of the Administration interface
When you search for save sets in the Media window of the Administration interface, you
can limit the save set results to synthetic full save sets by selecting the Synthetic Full
checkbox on the Query Save Set tab. Searching for save sets on page 449 provides
instructions.
Validating synthetic full backups in the backup action logs
The following excerpt from the backup action log file illustrates the type of messages
NetWorker displays when performing a synthetic full backup:
1707:97860:nsrconsolidate: Synthetic full save set hostname:/
sat-tree at savetime 1358188522 was created by using nonvirtual synthetic mode
95773:nsrrecopy: Virtual synthetic succeeded for hostname:/
test1
Synthetic full backup reporting
The backup statistics and backup status reports provide details on synthetic full
backups. A value of Synthetic in the Type column for the Save Sets Details
report or the Save Sets Details by client report indicates that the backup is a
synthetic full backup. Enterprise data reporting on page 550 provides more information.
304
EMC NetWorker 9.0.x Administration Guide
Backup Options
Virtual synthetic full backups
A virtual synthetic full (VSF) backup is the same as a synthetic full backup, except that it
is performed on a single Data Domain system.
Similar to synthetic full, VSF uses full and partial backups to create a full backup.
However, since the backup occurs on a Data Domain system using DD Boost APIs, the
backup does not require save set data to be sent over the network. The result is improved
performance over synthetic full and traditional full backups.
The following table compares traditional synthetic full and virtual synthetic full backups.
Table 57 Comparison of traditional synthetic full and virtual synthetic full backups
Traditional synthetic full
Virtual synthetic full
Data is read from and written to volumes.
Data movement is limited within the same Data
Domain system.
Read/write for all types of volumes is
supported.
Only Data Domain devices are supported, and
the source and destination volumes must
belong to the same Data Domain system.
However, the volumes can belong to different
MTrees in the same Data Domain system.
The client file index is created by nsrrecopy.
The client file index is created by
nsrconsolidate.
Client Direct support is not required.
Client Direct support is required.
Requirements for VSF backups
Ensure that the environment meets the requirements for virtual synthetic full (VSF)
backups.
The following table lists the requirements for VSF backups.
Table 58 Requirements for virtual synthetic full backups
Requirement
Details
DDOS version
Version 5.3 or later for both Data Domain systems and Data Domain
Archivers.
DD Boost version
Version 2.6 or later.
Data Domain
system
configuration
Enable the
virtual-synthetics option on the Data Domain system. To verify
that
virtual-synthetics is enabled, log in to the Data Domain system
and type the following command:
ddboost option show
Ensure that a value of
enabled appears next to the
virtual-synthetics option in the output for the command.
Virtual synthetic full backups
305
Backup Options
Table 58 Requirements for virtual synthetic full backups (continued)
Requirement
Details
NOTICE
If virtual-synthetics is disabled but all other requirements for VSF
are met, then the VSF backup fails with errors. NetWorker does not perform a
traditional synthetic full backup in this case.
Backup storage
Client resource
configuration
All constituent backups for the VSF backup must be on the same Data
Domain system. The save sets can be distributed across multiple storage
nodes and located in different MTrees on the Data Domain system.
l
Enable the Client direct attribute on the General tab of the Client
Properties dialog box for the client resource.
You must select ViewDiagnostic Mode in the Administration interface
to access the
Client direct attribute in the
Client Properties dialog box.
Device resource
configuration
l
Enable the Data Domain backup attribute on the Apps & Modules
tab of the Client Properties dialog box for the client resource.
l
To ensure optimal backup performance, configure the client to backup
10 or fewer save sets.
Specify a value in the volume location attribute for the device resource for
the Data Domain system. NetWorker updates the volume location attribute
during the device mount operation.
NOTICE
Before you update a storage node that uses Data Domain devices, unmount
each device. Once the update completes, mount each device.
NetWorker
upgrade
requirements
If you upgrade the NetWorker client to release 8.1 or later from a release
before 8.1, you must perform a full backup before you perform a VSF backup.
Otherwise, file-by-file recovery fails.
Cloning
requirements
The virtual-synthetics option must be enabled for Data Domain
systems being used for cloning VSF backups. Otherwise, cloning fails.
The EMC NetWorker Data Domain Boost Integration Guide provides details on configuring
the NetWorker environment for use with a Data Domain system.
Support for directives
Directives do not apply to VSF backups because the VSF backup is created by the Data
Domain system.
Support for concurrent operations
The volume of concurrent VSF operations that a Data Domain system can handle depends
on the model of the Data Domain system and the capacity of the NetWorker host. The
following scenarios have been tested and verified to work:
306
l
Concurrent VSF backups.
l
A VSF backup concurrent with a cloning operation.
EMC NetWorker 9.0.x Administration Guide
Backup Options
l
A VSF backup concurrent with clone-controlled replication.
Performing VSF backups
Procedure
1. Ensure that the environment meets the requirements for virtual synthetic full (VSF)
backups.
If NetWorker detects that one or more of the requirements are not met, then a
traditional synthetic full backup occurs instead.
2. Perform the backup:
l
l
For scheduled backups, select the synthetic full backup level for the backup action
in the data protection policy.
The procedure for scheduled VSF backups is the same as the procedure for
scheduled traditional synthetic full backups. Performing scheduled synthetic full
backups on page 303 provides more information on configuring a data protection
policy for a scheduled synthetic full backup.
For manual backups at the command line, use the nsrconsolidate command.
The procedure for manual VSF backups is the same as the procedure for manual
traditional synthetic full backups. Performing manual synthetic full backups on
page 303 provides more information.
Validating VSF backups
You can validate VSF backups by using the mminfo command, the Media window of the
Administration interface, and the savegrp logs.
Validating VSF backups with the mminfo command
The following table lists the mminfo commands with applicable switches for validating
VSF backups.
Table 59 mminfo commands for VSF backup validation
Command with switches
Description
mminfo –aS
Shows detailed information about synthetic full
backups, including information about the save
sets used to form the synthetic full backup.
mminfo –q syntheticfull –c client -N
save_set
Queries all synthetic full save sets for the specified
client and save_set.
Validating VSF backups in the Media window of the Administration interface
When you search for save sets in the Media window of the Administration interface, you
can limit the save set results to synthetic full and VSF save sets by selecting the Synthetic
Full checkbox on the Query Save Set tab. Searching for save sets on page 449 provides
instructions.
Validating VSF backups in the savegrp logs
The following excerpt from the policy log file illustrates the type of messages NetWorker
displays when performing VSF backups or traditional synthetic full backups, or when
performing a traditional synthetic full backup because the VSF backup requirements are
not met:
1707:97860:nsrconsolidate: Synthetic full save set hostname:/
sat-tree at savetime 1358188522 was created by using nonVirtual synthetic full backups
307
Backup Options
virtual synthetic mode
95773:nsrrecopy: Virtual synthetic succeeded for hostname:/
test1
Backup scheduling
When you schedule backups, you define the days on which backups occur and the level
of backup (full, incremental, and so on) that occurs each day.
Scheduling backup cycles
The period from one full backup to the next full backup is called a backup cycle.
For example, the default schedule for backups is a full backup on a client each Sunday,
and incremental backups on the other days of the week, as illustrated in the following
figure.
Figure 39 Default weekly backup schedule
Depending on the size of a network, you could perform full backups for all clients
simultaneously. For example, if no one works over the weekend you could schedule full
backups during this time.
Alternatively, you may need to configure backups to balance the backup load on and
increase the efficiency of a NetWorker server. Since full backups transfer large amounts
of data and typically take longer than other backup levels, you might want to stagger
them throughout the week. For example, you could configure backups so that full
backups occur for one group of clients on Sunday, for a second group of clients on
Tuesday, and a third group of clients on Thursday, as illustrated in the following figure.
Figure 40 Staggered weekly backup schedule for multiple groups of clients
308
EMC NetWorker 9.0.x Administration Guide
Backup Options
Note
Consider using a synthetic full backup in environments with a short backup window
period when you must create a full backup.
Considerations for scheduling backups
Planning schedules for backups in an environment requires careful consideration of
several factors.
For example:
l
The amount of data you must back up.
l
The number of backup media volumes to use.
l
The amount of time available to complete a backup.
l
The number of volumes that are required to recover from a disaster such as a disk
failure.
Recovery considerations
You must also determine the requirements for recovering files. For example, if users
expect to recover any version of a lost file that was backed up during a three-month
period (that is, the retention setting is three months), then you must maintain all the
backup volumes for a three-month period. However, if users expect to be able to recover
data from only the last month, you do not need to maintain as many volumes.
Considerations for large client file systems
At a moderate backup rate of 400 KB per second, a full backup for a client with 10 GB of
data takes about seven hours to complete. Performing a scheduled full backup for such
large client save sets may not be convenient because of the amount of time required.
For large client file systems, consider scheduling consider separate backups for each of
the client disk volumes. This strategy enables you to back up all the client files, but not
all at once, which is less time-consuming than a full backup of all local data at one time.
To schedule separate backups of each client disk volume, configure multiple client
resources for the client, and explicitly list one disk volume as the save set for each client
resource. Add each client resource to a different group. Then configure separate policy
workflows to back up each group on a different schedule.
NOTICE
When you create explicitly list save sets, any files or file systems not in that list are
omitted from the backup, including any new disk volumes that you add to the system.
Remember to configure backups for any new disk volumes after you add them.
Methods for scheduling backups
You can configure the backup schedule for a group of clients as part of data protection
policy settings, or you can override the policy schedules that apply to a client by
specifying a schedule for the Client resource.
Schedules for data protection policies
You specify the schedule as part of the backup action in a data protection policy. The
following figure illustrates the default weekly schedule for a traditional backup action,
with a full backup on Sunday, and incremental backups the remaining days of the week.
Considerations for scheduling backups
309
Backup Options
Figure 41 Default weekly schedule for a traditional backup action
You can also configure the schedule for a backup action on a monthly basis instead of on
a weekly basis.
Click the icon in the schedule to change the type of backup that is performed on that day.
The following table provides details on the backup type that each icon represents.
Table 60 Backup schedule icons
Icon
Label
Description
Full
Perform a full backup on this day. Full backups include all files,
regardless of whether the files changed.
Incr
Perform an incremental backup on this day. Incremental backups
include files that have changed since the last backup of any type (full
or incremental).
Cumulative Incr Perform a cumulative incremental backup. Cumulative incremental
backups include files that have changed since the last full backup.
310
Logs Only
Perform a backup of only database transaction logs.
Synthetic Full
Perform a synthetic full backup on this day. A synthetic full backup
includes all data that changed since the last full backup and
subsequent incremental backups to create a synthetic full backup.
Skip
Do not perform a backup on this day.
EMC NetWorker 9.0.x Administration Guide
Backup Options
Schedules for client resources
You can override the schedule that is specified in the data protection policies that apply
to a client resource by selecting a schedule from the Schedule attribute list on the
General tab of the Client Properties dialog box for the resource.
You must select View > Diagnostic Mode in the Administration interface to access the
Schedule attribute in the Client Properties dialog box.
Overriding the backup schedule for a client resource
You can override the backup schedule that is specified in the data protection policies
that apply to a client resource by specifying a schedule for the Client resource itself.
Procedure
1. (Optional) Create or customize the schedule that you plan to assign to the Client
resource.
2. In the Administration window, select View > Diagnostic Mode to enable diagnostic
mode view.
A check mark next to Diagnostic Mode in the View menu indicates that diagnostic
mode view is enabled.
3. In the Administration window, click Protection.
4. In the expanded left pane, select Clients.
5. In the right pane, right-click the client resource and select Modify Client Properties.
The Client Properties dialog box appears, starting with the General tab.
6. Ensure that the Scheduled Backup checkbox is selected.
When the checkbox is clear, scheduled backups do not occur for the client.
7. From the Schedule list, select the schedule to use instead of the schedule in the data
protection policies that apply to the Client resource.
8. Click OK.
Preconfigured schedules
When you override the policy backup schedule for a client resource, you can select or
customize one of the preconfigured schedules that are available when you install or
upgrade the NetWorker software.
The following table describes the preconfigured schedules.
Table 61 Preconfigured NetWorker schedules
Schedule name
NetWorker backup operation
Default
Weekly schedule that performs a full backup every Sunday and
incremental backups on all other days.
Forever Incremental
Monthly schedule that performs a synthetic full backup every day.
Full Every Day
Weekly schedule that performs a full backup every day.
Full Every Friday
Weekly schedule that performs a full backup every Friday and
incremental backups on all other days.
Full on 1st Friday of
Month
Monthly schedule that performs a full backup on the first
Friday of the month and incremental backups on all other days.
Overriding the backup schedule for a client resource
311
Backup Options
Table 61 Preconfigured NetWorker schedules (continued)
Schedule name
NetWorker backup operation
You cannot edit this schedule.
Full on 1st of Month
Monthly schedule that performs a full backup on the first calendar day
of the month, and incremental backups on all other days.
Quarterly
Monthly schedule that performs a full backup on the first day of a
quarter, a cumulative incremental backup once a week after the full
backup, and then incremental backups on all other days.
Synthetic Full
1st Friday of Month
Monthly schedule that performs a synthetic full backup on the first
Friday of every month, and incremental backups on all other days.
Synthetic Full
Every Friday
Weekly schedule that performs a synthetic full backup on every Friday
and incremental backups on all other days.
Synthetic Full
on 1st of Month
Monthly schedule that performs a synthetic full backup on the first
calendar day of the month, and incremental backups on all other days.
Synthetic Full
Quarterly
Monthly schedule that performs a synthetic full backup on the first day
of each quarter, a cumulative incremental backup once a week after the
synthetic full backup, and then incremental backups on all other days.
You can edit all preconfigured schedules except for schedules that contain overrides,
which are indicated by an asterisk next to a backup level in the schedule calendar. You
cannot delete a preconfigured schedule.
Creating a backup schedule
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Schedules.
3. From the File menu, select New.
The Create Schedule dialog box appears.
4. In the Name box, type a name for the schedule.
5. From the Period list, select Week or Month to control whether the schedule repeats on
a weekly or monthly basis.
6. (Optional) Specify a description of the schedule in the Comment box.
7. Set the backup level for each day by right-clicking the day, selecting Set Level and
then the backup level.
8. (Optional) Set the override backup level for a day by right-clicking the day, selecting
Override Level and then the backup level.
For example, to prevent a full backup from running on a holiday, override the schedule
so that the full backup runs on the day before or the day after the holiday. An asterisk
(*) next to a backup level indicates that an override has been set for that day.
312
EMC NetWorker 9.0.x Administration Guide
Backup Options
Note
If you override backup levels by using the nsradmin command line program, you can
also specify relative date values such as full first friday every 2 week.
The nsr_schedule man page or the EMC NetWorker Command Reference Guide
contain more information about overriding backup levels.
9. Click OK.
Editing a schedule
You can edit all custom schedules, and all preconfigured schedules, except for
preconfigured schedules that contain overrides. Overrides are indicated by an asterisk
next to a backup level in the schedule calendar. You can edit all schedule settings except
for the name.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Schedules.
3. In the right pane, right-click the schedule and select Properties.
The Schedule Properties dialog box appears.
4. Edit the settings for the schedule and click OK.
Copying a schedule
You can create a new backup schedule by copying an existing schedule and then editing
the copy.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Schedules.
3. In the right pane, right-click the schedule to copy and select Copy.
The Create Schedule dialog box appears with the same information as the copied
schedule except for the name.
4. In the Name box, type a name for the new schedule.
5. Edit the settings for the schedule and click OK.
Deleting a schedule
You can delete any custom schedules that you have created. You cannot delete
preconfigured schedules.
Before you begin
Ensure that the schedule has not been applied to any Client resources by verifying the
setting in the Schedule list on the General tab of the Client Properties dialog box for each
Client resource.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Schedules.
3. In the right pane, right-click the schedule and select Delete.
A confirmation message appears.
Overriding the backup schedule for a client resource
313
Backup Options
4. Click Yes.
Backup retention
The retention setting for a save set determines how long the NetWorker server maintains
save set entries in the media database and client file indexes. Until the retention period
expires, you can recover client backup data from backup storage either by browsing the
data or by recovering the entire save set.
Removing expired save sets on page 455 describes how to remove save sets from
backup storage after the retention period expires.
Methods for setting retention
You can specify retention for backup save sets and clone save sets in a variety of ways. If
you specify retention by using multiple methods, then the retention setting that applies
depends on the scenario.
Note
If you set a retention policy on February 29 of a leap year, the last day in which the policy
applied is 1 day earlier than you might expect. For example, if you set a retention policy
to 1 year on March 3, 2015, the save set will expire on March 3, 2016 as expected, which
is 366 days. If you set a retention policy to 1 year on February 29, 2016, you might expect
that the policy will expire March 1, 2017. However, the policy will actually expire on
February 28, 2017, which is 365 days. This behavior is only seen when a retention policy
is set on February 29 for one or more years.
Retention for data protection policies
You can specify retention for backup save sets and clone save sets as part of the actions
in a data protection policy. Retention settings are available for the traditional backup,
snapshot backup, VMware backup, server backup, VBA checkpoint backup, and clone
actions.
A single Client resource can belong to multiple groups. Therefore, you can assign
different retention settings for the same client and save set data by configuring different
workflows and actions. Consider the following example scenario:
l
A client belongs to both Client Group A and Client Group B.
l
Client Group A is assigned to Workflow 1, which performs a backup with a retention
setting of 1 month.
l
Client Group B is assigned to Workflow 2, which performs a backup with a retention
setting of 1 year.
In this case, backups for the client that are performed with Workflow 1 are retained for 1
month, and backups for the client that are performed with Workflow 2 are retained for 1
year.
Retention for Client resources
You can assign a retention policy to a client resource that overrides the retention period
that is specified in an Action resource, when you configure the Client Override Behavior
attribute value to Client Can Override in the Action resource. Assigning a retention policy
to a Client resource on page 315 provides more information.
Retention for Pool resources
Previous versions of NetWorker allowed you to define a value in the Retention attribute of
a Pool resource. When you update a NetWorker 8.2.x or earlier server, the update process
314
EMC NetWorker 9.0.x Administration Guide
Backup Options
retains the value that is defined in the Retention attribute of a Pool resource as a readonly value.
Order of precedence for Retention resource attributes
EMC recommends that you use the configuration settings in an Action resource to
determine which pool received backup data. NetWorker provides you with the ability to
configure a Pool attribute in the client resource, which can override the value defined in
the Action resource. Additionally, the Pool resource contains 8.2.x legacy attributes that
provide you with the ability to define backup data criteria for the pool. How and when
NetWorker uses the attributes values defined in the Pool, Action, and Client resources to
determine which backup pool will receive data depends on the value that you select in
the Client Override Behavior attribute of the Action resource:
l
Client Can Override—The value in Retention attribute of the Client resource takes
precedence over the Retention value that is defined in the Action resource.
l
Client Can Not Override—The value defined Retention attribute in the Action resource
takes precedence over the value that is defined in Retention attribute of the Client
resource and the Retention attribute of the Pool resource.
l
Legacy Backup Rules—Enabled for migrations only. NetWorker uses the values that
are defined in the Retention attribute of the Pool resource to determine which the
retention policy to assign to backup data from a client. The value that is defined in
the Retention attribute of the Pool resource take precedence over the Retention value
that is defined in the Action resource and the Retention value that is defined in the
Client resource.
Note
You cannot modify the legacy attributes in the migrated Pool resources.
Retention for manual backups
If you specify retention with a manual backup from the command prompt with save -w,
the retention setting applies to all the save sets that are in the manual backup. Specify
the retention setting by using the time and date formats that are accepted by the
nsr_getdate program. The save and nsr_getdate UNIX man page and the EMC
NetWorker Command Reference Guide provides detailed information about data formats.
If you do not specify retention for a manual backup, then retention is applied based on
the retention setting of either the Client resource or the media pool for the backup,
whichever is longer. If there are multiple Client resources for the host, then the longest
retention setting applies.
Assigning a retention policy to a Client resource
You can override the retention setting specified in the data protection policies that apply
to a Client resource by specifying a retention setting for the Client resource itself.
NetWorker provides one of the following default retention policies that you can assign to
the Client resource. Default retention policies include:
l
Day
l
Week
l
Month
l
Quarter
l
Year
l
Decade
You can also create a custom retention policy.
Assigning a retention policy to a Client resource
315
Backup Options
Procedure
1. (Optional) Create or customize the retention policy that you plan to assign to the
Client resource.
a. In the NetWorker Administration window, click Server.
b. In the expanded left pane, select Time Policies.
c. Create a policy or modify a retention Policy resource:
l
To create a policy, from the File menu, select New.
l
To modify a policy, right-click the retention policy and select Properties.
d. For a new policy only, in the Name box, type a name for the retention policy.
e. Optionally, in the Comment box, type a description of the retention policy.
f. From the Number of periods and Period lists, specify the duration of the retention
period.
g. Click OK.
2. In the NetWorker Administration window, select View > Diagnostic Mode to enable
diagnostic mode view.
A check mark next to Diagnostic Mode in the View menu indicates that diagnostic
mode view is enabled.
3. In the NetWorker Administration window, click Protection.
4. In the expanded left pane, select Clients.
5. In the right pane, right-click the client resource and select Modify Client Properties.
The Client Properties dialog box appears, starting with the General tab.
6. From the Retention policy list, select the retention policy to apply to all backups of the
client resource, regardless of the retention setting for any data protection policies that
apply to the client resource.
7. Click OK.
Editing retention for a save set
Use the nsrmm program with the -e option to edit the retention setting of a save set after
the backup has occurred.
Specify the save set ID with the -S option, and specify the updated time in quotation
marks with the -e option. The time and date format must use a format that is accepted
by the nsr_getdate program.
Use the mminfo command with the -p option to view a report on the retention times for
save sets.
The EMC NetWorker Command Reference Guide and the UNIX man pages provide more
information about nsrmm, nsr_getdate, and mminfo.
Example commands to edit retention for a save set
The following command updates the retention time for save set ID 3315861249 to
midnight on January 1, 2016:
nsrmm -S 3315861249 -e "01/01/16 23:59:59"
The following command updates the retention time for save set ID 3315861249 to two
years from the current date and time:
316
EMC NetWorker 9.0.x Administration Guide
Backup Options
nsrmm -S 3315861249 -e "2 years"
General backup considerations
Before you configure Client resources to backup data on a host, review this section for
information that applies to Windows, UNIX, and Mac OS-X hosts.
Renamed directories
When you rename a directory, a full backup is performed on all subdirectories and files of
the renamed directory.
If you then rename the directory back to its original name, then files and subdirectories of
the directory are not eligible for backup until the files or subdirectories are updated or the
next full backup occurs.
You can change this default behavior by clearing the Backup renamed directories
checkbox on the General tab of the Client Properties dialog box for a Client resource. You
must select View > Diagnostic Mode in the Administration interface to access the Backup
renamed directories attribute in the Client Properties dialog box.
When you clear the Backup renamed directories checkbox for a Client resource,
unchanged files and folders under the renamed directory are skipped during a non-full
backup. This behavior can cause unexpected results during a recovery operation. If you
try to recover data under a renamed directory from a date between the time that the
directory was renamed and the next full backup, it may appear that data is missing. For
that recovery period, any files or folders that were unchanged do not appear under the
renamed directory. Instead, they appear under the previous directory name.
You must leave the Backup renamed directories checkbox selected for clients that
perform synthetic full backups.
Raw partitions
The NetWorker software must have exclusive access to a file system to perform a raw
backup. Close as many applications as possible before doing a raw disk backup. If the
raw partition contains data that are managed by an active database management system
(DBMS), ensure that the partition is offline and the database manager is shut down. For
greater flexibility when backing up partitions that contain DBMS data, use a NetWorker
Module application.
Raw partitions on Windows
Back up raw disk partitions on Windows by specifying the raw disk partition in a save set
with the save command. Identify the raw partition as a physical drive or logical drive. For
example:
save -s NetWorker_server_name \\.\PhysicalDrive0
save -s NetWorker_server_name \\.\C:
Raw partitions on UNIX
Back up raw disk partitions on UNIX by using the rawasm directive.
Raw partitions on Linux
NetWorker can only save an unbound Linux raw device. When you back up a Linux raw
disk partition, you must specify /dev/sd or /dev/hd in the Save set attribute on the
General tab of the Client Properties dialog box for the Linux Client resource. The backup
fails if you use the /dev/raw device.
General backup considerations
317
Backup Options
Access control lists
The NetWorker software supports backup and restore of Access Control Lists (ACLs) and
extended ACLs for Linux, HP-UX, AIX, DEC, Solaris, OS X, and Windows.
When a file with an associated ACL is backed up, the ACL is backed up along with the file
data. When the file is recovered, any associated ACL is also recovered.
The ACL passthrough checkbox on the Configuration tab of the NetWorker Server
Properties dialog box controls whether to recover files with associated ACLs. Select the
checkbox to recover files with associated ACLs.
Client parallelism and parallel save streams
Client parallelism defines the number of data streams that a client can use
simultaneously during backup.
Data streams include back data streams, savefs processes, and probe jobs.
The default value is different for the NetWorker server than it is for all other client
resources:
l
For the NetWorker server client resource, the default value is 12. This higher default
value enables the server to complete a larger number of index backups during a
Server backup action.
l
For all other clients, the default value is 4.
To define client parallelism, use the Parallelism attribute of the Client resource. You can
find the parallelism attribute on the Globals(1 of 2) tab of the Client property dialog box,
in the NetWorker Administration window.
The EMC NetWorker Network Data Management Protocol (NDMP) User Guide provides more
information about recommended parallelism settings for NDMP clients.
To avoid disk contention for clients other than the NetWorker server, specify a value that
is the same as or fewer than the number of physical disks on the client that are included
in the backup.
For a Windows client with the ALL keyword save set attribute, the backup includes the
local disks, for example C: and D: drives as well as the System State and System DB. In
this example, you can keep the default parallelism setting of 4. If you define multiple
save sets on the same disk, for example, C:\users, C:\system, C:\docs and so on ,
a higher client parallelism will result in multiple save streams attempting to access the
disk at the same time.
The EMC NetWorker Performance Optimization Planning Guide provides more information
about recommended client parallelism values and performance benefits.
Enabling the parallel save streams (PSS) feature for a Client resource allows you to back
up each save set for the client by using multiple parallel save streams to one or more
destination backup devices. PSS is used for the scheduled, file-based backup of file
systems.
You can use PSS for clients with supported UNIX, Linux, and Windows operating systems.
Supported save sets for PSS include the Save Set ALL, and individual save points
including Disaster_Recovery, deduplicated, and CSV volumes (Windows only).
Checkpoint restart is not supported when you use PSS.
When you enable PSS, you can specify the maximum number of save streams that a
client can send simultaneously for one or more save set backups concurrently running by
using the Parallelism attribute in the Client Properties dialog box. The default value for
318
EMC NetWorker 9.0.x Administration Guide
Backup Options
the Parallelism attribute is different for the NetWorker server than it is for all other Client
resources:
l
For the NetWorker server Client resource, the default value is 12. This higher default
value enables the server to complete a larger number of index backups during a file
system backup of the server or other index backups.
l
For all other clients, the default value is 4.
Enabling PSS results in significant performance improvements due to save set
aggregation, where the NetWorker server starts a single save process per client with all
client save sets that are passed to the single process for various processing
optimizations, such as minimal Windows VSS snapshots and support for the following:
l
Four parallel streams are started per save set, subject to any client parallelism
limitations that might prevent all save sets from starting simultaneously
l
The ability to modify the number of parallel streams per save set by defining the new
PSS:streams_per_ss environment variable save operations attribute in the properties
of a Client resource. For example, setting PSS:streams_per_ss=2,* splits all save sets
into two parallel save streams, whereas PSS:streams_per_ss=3,/data1, 5,/data2
splits /data1 into three parallel save streams and /data2 into five parallel save
streams.
l
Automatic stream reclaiming, which dynamically increases the number of active
streams for an already running save set backup to maximize utilization of limited
client parallelism conditions
Note
EMC recommends setting parallelism to 4 or a value greater than the PSS:streams_per_ss
variable, otherwise backups may fail. The PSS:streams_per_ss values range from 1 to 8.
The EMC NetWorker Performance Optimization Planning Guide provides complete details on
PSS requirements and performance benefits.
Configuring parallel save streams
Enable parallel save streams and specify the maximum number of save streams for a
client by using the Client Properties dialog box. Note that the value specified for
parallelism as part of an action in a policy is ignored for PSS backups.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears, starting with the General tab.
4. In the Save set attribute, specify All or a list of paths, for example, on UNIX /X and /Y
or on Windows X:\ and Y:\.
5. Select the Globals (1 of 2) tab.
6. From the Parallelism list, specify the maximum number of save streams.
7. Select the Parallel save streams per save set checkbox.
8. Click OK.
Configuring parallel save streams for virtual clients
If you are backing up virtual clients, you can base the client parallelism setting on the
underlying physical host. In this way, the total number of save streams for all virtual
Client parallelism and parallel save streams
319
Backup Options
clients that reside on a physical host are limited to the value specified for the physical
host.
For example, consider an environment with ten virtual machines running on the same
physical host. Each virtual machine is a NetWorker client, and each client has a client
parallelism setting of 4. This setting can result in a total of 40 save streams occurring on
the same physical host, which would significantly slow down that system. To avoid this
situation, you can specify that the client parallelism values are to be based on the
underlying physical host. In this example, that would result in no more than four save
streams occurring for the backup of the ten virtual clients.
Procedure
1. In the Administration window, select View > Diagnostic Mode to enable diagnostic
mode view.
A check mark next to Diagnostic Mode in the View menu indicates that diagnostic
mode view is enabled.
2. Click Protection.
3. In the expanded left pane, select Clients.
4. Right-click the Client resource for the virtual client and select Modify Client
Properties.
The Client Properties dialog box appears, starting with the General tab.
5. Select the Virtual client checkbox.
6. Type the name of the underlying physical host in the Physical host box.
7. Select the Globals (1 of 2) tab.
8. From the Parallelism list, specify the maximum number of save streams.
9. Select the Physical client parallelism checkbox.
10. Select the Parallel save streams per save set checkbox.
11. Click OK.
12. Repeat these steps for all virtual NetWorker clients that share the same physical host.
Ensure that the value in the Physical host attribute is the same for all virtual
NetWorker Client resources that share the same physical host.
Troubleshooting PSS
It is recommended that you troubleshoot PSS with the guidance of EMC Customer
Support. The EMC NetWorker Performance Optimization Planning Guide provides complete
details on PSS requirements and performance benefits.
Procedure
1. Enable detailed logging for the client:
a. Specify the following value for the Backup command attribute on the Apps &
Modules tab of the Client Properties dialog box:
save -v -D7 (or D9 for more detailed logging)
b. Type the following command at the command prompt on the client computer:
touch /nsr/debug/mbsdfopen
2. In the Protection window of the Administration interface, enable the -v verbose
option for scheduled backups by selecting Policies > policy name > workflow name.
320
EMC NetWorker 9.0.x Administration Guide
Backup Options
3. Wait for the next backup to occur, or manually start a backup by using one of the
following methods:
l
In the Protection window of the Administration interface, right-click the workflow
and select Start.
l
Use the nsrpolicy command on NetWorker server:
nsrpolicy start -p "policy" -w "workflow"
where policy is the name of the policy and workflow is the name of the workflow to
start.
4. After the workflow finishes, collect the log files in the following table for EMC
Customer Support.
Table 62 Log files for PSS troubleshooting
Log file
type
Log files to collect
Client
All log files in /nsr/tmp/save-mbs-*
NetWorker
server
l
/nsr/logs/daemon.raw
l
All log files in /nsr/logs/policy/policy_name/ workflow_name/
action_name_sequence#_logs/*
For example, /nsr/logs/policy/Silver/Filesystem/
Backup_032334_logs/*
l
/nsr/tmp/savegrp.log
Maximum path and save set length
The maximum supported length in the NetWorker software for a pathname is 12 KB, and
the maximum length for a save set name is 1024 bytes. The number of characters that are
allowed by each of these limits depends on the locale.
All operating systems have an internal limit for path and file names. The limit depends on
the operating system and file system. Typically, the pathname component size is 256.
For UNIX, only the path component length is checked against the limit. As a result, it is
possible to create a path and file name that is greater than the limit supported by the
operating system, but an try to access this path fails.
Open files
Open files are a problem that all data backup applications must solve. Open files that are
not backed up correctly represent a potential data loss. They might be skipped,
improperly backed up, or locked.
NetWorker can open files that are owned by the operating system and files that are
owned by a specific application.
When you use VSS technology with NetWorker to create snapshot backups of volumes
and exact copies of files, the backup includes all open files and files that change during
the backup process.
Files owned by the operating system
Most open files that are owned by the operating system can be backed up. However,
some applications can apply operating system locks to open files. These locks prevent
Maximum path and save set length
321
Backup Options
other applications, such as NetWorker software, from writing to or reading from the open
file.
The NetWorker software normally skips locked files and returns the following message:
save: filename cannot open
Also, the operating system might return a permission denied error.
To back up locked open files, close any open files if possible. To automate this process,
create a pre- and postprocessing backup command that shuts down specific
applications, backs up the open files, and then restarts any applications after the backup
finishes.
You can also use Open File Manager to back up open files.
Files owned by a specific application
The NetWorker software cannot normally back up an open file that belongs to a specific
application, like a database. To back up these open files, use a NetWorker Module. For
example, use the NetWorker Module for SAP to back up open files in an Oracle database.
Files that change during the backup
If a file changes during a backup, the NetWorker software displays the following message
in the Monitoring window:
warning: filename changed during save
To ensure that the changed file is backed up, either rerun the scheduled backup or
perform a manual backup of the file.
NetWorker Modules can back up these types of files correctly if they are files that are
related to the database that the module is backing up.
Data deduplication
Data deduplication is a type of data compression that removes duplicate information to
reduce the amount of backup data sent to storage devices and reduce the bandwidth that
is required for the data transport. You can implement data deduplication of NetWorker
backup data by storing backups on Data Domain Boost deduplication devices.
Deduplication with DD Boost devices
The NetWorker client software includes the DD Boost library API and the distributed
segment processing (DSP) component to enable deduplication on the client. The API
enables the NetWorker software to communicate with the Data Domain system. The DSP
component reviews the data that is already stored on the Data Domain system, and adds
only unique data to storage.
DD Boost can run as many as 60 concurrent sessions (save streams) for a DD Boost
device for backup and recovery. This high throughput reduces the number of necessary
devices and the performance and maintenance impact on the Data Domain system. The
resulting performance gain provides an advantage over conventional advanced file type
device (AFTD) or virtual tape library (VTL) interfaces that do not handle these high session
rates.
To perform deduplication backups with a Data Domain system, perform the following
tasks:
322
l
Configure the Data Domain system for use with NetWorker.
l
Add the device in the NetWorker Administration interface.
l
Select Data Domain backup options for Client resources.
EMC NetWorker 9.0.x Administration Guide
Backup Options
The EMC NetWorker Data Domain Boost Integration Guide provides details on system
requirements and configuration steps.
Deduplication with Avamar
The NetWorker software installation package includes the Avamar client software.
The Avamar client software only provides support to NetWorker hosts that used an
Avamar system as a data protection target with a previous release of NetWorker. You
cannot configure new Avamar nodes in NetWorker 9.0.x.
Directives
Directives are resources that contain special instructions that control how the NetWorker
server processes files and directories during backup and recovery. Directives enable you
to customize the NetWorker software, maximize the efficiency of backups, and apply
special handling to individual files or directories.
Types of directives
There are three types of directives.
l
Global directives—Stored as resources on the NetWorker server and can be
selectively applied to individual clients by using the Directive attribute of the Client
resource.
l
NetWorker User local directive—On Windows clients only, users with local Windows
Administrator or Backup Operator privileges can create a local directive in the
NetWorker User program. A file that is named networkr.cfg on the client file
system contains the directive configuration information. NetWorker uses the directive
that is specified in the networkr.cfg during a scheduled backup, a backup that is
started with the NetWorker User application, and save operations that do not
include the -i option.
l
Local directive files—User-created files named nsr.dir (Windows) or .nsr (UNIX)
anywhere on a client file system where they have permission to create files. These
directives apply only to the immediate data within the path where the directive file is
located.
If there is a conflict between directives, global directives are enforced over local
directives. Also, NetWorker User program local directives are enforced over local directive
files (nsr.dir files) on Windows hosts.
NOTICE
If you use the Windows BMR feature, implement user-defined directives with caution.
Using such directives in directories with system state files can lead to an incomplete BMR
backup image and potentially render the BMR backup image unusable. If you create userdefined directives, test the BMR backup image to ensure that you can recover the
Windows system state correctly.
Format of directive statements
Directive statements specify the files or directories and then the action to perform on the
files and directories. A directory statement specifies the files and directories for a
directive statement, and then an ASM specification or a save environment keywords
specifies the action to perform.
A directive statement has the following format:
Directives
323
Backup Options
<<"directory_specification">>
[+] ASM: pattern
save_environment_keyword
# comment
where:
l
The directive statement does not include blank lines.
l
directory_specification is the absolute path to the highest-level directory for which the
ASM in the directive applies. The directory_specification cannot include wildcards.
Consider the following:
n
When you specify multiple directory specifications, directives that follow a
directory specification apply to that directory until the next directory specification.
n
Mount points, including nested mount points, must have their own directory
specification.
n
File and directory names are not case-sensitive for directives that are applied to
clients on Windows systems. If there is a colon (:) in the pathname, enclose the
entire path in quotation marks.
l
[+] Optional. The presence of the plus (+) sign indicates that the directive applies to
the directory defined by the absolute path and all subdirectories.
l
ASM is the ASM that specifies the action to take on one or more files in the current
directory.
l
save_environment_keyword is NetWorker keyword that controls how the current ASM
and subsequent ASMs that apply to the current directory and subdirectories are
applied in the directive statement. NetWorker supports the following
save_environment_keyword values:
l
n
forget—Instructs the NetWorker server to no longer apply inherited directives
(those directives that begin with a +). The forget keyword works only if the
corresponding directories are also explicitly specified in the NetWorker client
resource Save Set attribute.
n
ignore—Instructs the NetWorker server to ignore all directives that are applied
to the subdirectories below the current directory.
n
allow—Used in subdirectories that currently have the ignore keyword applied
to them, and overrides the ignore.
pattern is a list of file or directory names, in the current directory on which to apply
the ASM. The pattern can include multiple names that are separated by spaces, and
wildcards. Wildcards can replace a single character or string of characters. Directive
statement support the use of standard shell command interpreter file matching
patterns. You cannot specify subdirectories in the pattern.
Note
File names are case-sensitive for directives that are applied to Windows clients.
l
comment is a user-defined description of the directive statement. A hash (#) character
must precede the comment.
Note
If an ASM or pattern name includes a space, enclose the name or argument in double
quotation marks.
324
EMC NetWorker 9.0.x Administration Guide
Backup Options
The UNIX man page and the EMC NetWorker Command Reference Guide provides detailed
information about directives in the nsr and nsr_directive commands.
Directive specification examples
Review the following examples of directive specifications that include ASMs and save
environment keywords.
Using the skip directive for a Windows host
The following example directive statement skips the C:\Program Files folder on a
Windows host during a backup:
<<"C:\Program Files">>
skip
Using the skip directive for a UNIX host
The following directive statement skip all files in the /tmp directory on a UNIX host,
including hidden files:
<<./tmp>>
+skip: * .?*
Note
A space appears after the first asterisk (*) in the pattern.
Using the skip ASM and forget save environment keyword
The following example directive statement skips all *.o files in the G:\SRC directory
except those *.o files in the G:\SRC\SYS directory:
<<"G:\SRC">>
+skip: *.o
<<"G:\SRC\SYS">>
forget
This example uses the skip ASM to instruct the NetWorker server to skip all files that are
named *.o in the SRC directory and all subdirectories. It then uses the forget keyword
to instruct the server to not apply the skip ASM to the SYS subdirectory.
Both the G:\SRC and the G:\SRC\SYS directories must be explicitly specified on
separate lines in the client resource Save Set attribute.
Using the ignore save environment keyword
The following example allows directives in the HOMEDOC directory to be applied to the
preceding example for the ignore keyword:
<<HOME>>
ignore
<<HOMEDOC>>
allow
Using the allow save environment keyword
The following example directive statement overrides any local directives set in user home
directories:
<<HOME>>
ignore
Format of directive statements
325
Backup Options
Global directives
Global directives are stored as resources on the NetWorker server and can be selectively
applied to individual clients by using the Directive attribute of the Client resource.
Global directives are listed when you select Directives in the expanded left pane of the
Server window in the Administration interface. You can add, edit, copy, and delete global
directives.
Preconfigured global Directive resources
The NetWorker software includes a number of preconfigured global Directive resources.
All preconfigured Directive resources can be modified, but they cannot be deleted.
The following table lists the preconfigured directives and their descriptions.
Table 63 Preconfigured directives
Directive
resource
Description
AES
Encrypts backup data with the aes ASM, which provides 256-bit data
encryption.
Mac OS with
compression
Contains the same set of directives as the Mac OS standard directive, along with
applying the compressasm ASM to specific directories.
Mac OS
standard
Contains a set of directives that are used to back up standard Mac OS clients.
Applies these ASMs:
l
The skip ASM is applied to these files and directories:
/Desktop DB
/Desktop DF
/cores
/VM_Storage
/TheVolumeSettingsFolder
/private/var/db/netinfo
/private/var/db/openldap
/private/tmp
/.Spotlight-V100
/.hotfiles.btree
326
l
The allow save environment keyword is applied to the /nsr directory to
ensure that local directives in /nsr and subsequent subdirectories are
applied.
l
The logasm ASM is applied to the /nsr/logs and /var directories.
l
The swapasm ASM is applied to the /private/var/vm
NT standard
Is used to back up Windows clients. By default, this resource has no directives.
NT with
compression
Used to back up and compress Windows clients. It applies the compressasm
ASM to all files.
EMC NetWorker 9.0.x Administration Guide
Backup Options
Table 63 Preconfigured directives (continued)
Directive
resource
Description
UNIX standard
Contains a set of directives that are used to back up standard UNIX clients.
Applies these ASMs:
UNIX with
compression
l
The skip ASM is applied to the tmp_mnt directory.
l
The skip ASM is applied to core files on the file system.
l
The allow save environment keyword is applied to the /nsr directory to
ensure that local directives in /nsr and subsequent subdirectories are
applied.
l
The skip ASM is applied to the /tmp directory.
l
The swapasm ASM is applied to the /export/swap directory. If swap files
are located in a different directory, modify this directive to use the
appropriate directory.
l
The logasm ASM is applied to the /nsr/logs, /var, /usr/adm,
and /usr/spool directories. You can apply this ASM to other directories
as well.
l
The mailasm ASM is applied to the /usr/spool/mail and /usr/mail
directories. If email files are located in different directories, modify these
directives to use the appropriate locations.
Contains the same set of directives as the UNIX standard directive, along with
applying the compressasm ASM to all files.
This directive is only applied to save sets that contain
directories. If the save set is defined by using a file name, this
directive is not applied.
VCB directives
VCB directives are valid for backing up virtual machines using the VCB
methodology. This directive is supported in the following scenarios:
l
When file level incremental backups are performed instead of FULL image
level backups.
l
When FULL file level or incremental file level backups are performed when
the save set is ALLVMFS.
The vcb directive skips the following files and folders:
l
pagefile.sys
l
hiberfil.sys (Hibernation file)
l
WINDOWS\system folder
l
WINDOWS\System32 folder
Creating a global Directive resource
Procedure
1. In the Administration window, click Server.
2. In the expanded left pane, select Directives.
Global directives
327
Backup Options
3. From the File menu, select New.
The Create Directive dialog box appears.
4. In the Name box on the General tab, type a name for the new directive.
5. In the Comment box, type a description of the directive.
6. In the Directive attribute, type one or more directive statements.
A directive statement specifies the files and directories for a directive statement, and
then an ASM specification or a save environment keywords specifies the action to
perform. You can also include comments in a directive statement by preceding text
with a hash (#) character.
For example, the following directive statement skips the C:\TEMP folder on a
Windows system during a backup:
<<"C:\TEMP">>
skip
NOTICE
Do not leave blank lines in the directive statement.
Format of directive statements on page 323 provides more infromation about how to
create a directive statement.
7. To specify a restricted datazone (RDZ) for the directive, click the Restricted Data Zones
tab and then select the RDZ from the list.
8. Click OK.
After you finish
Apply the global directive to a Client resource by selecting the directive from the Directive
list on the General tab of the Client Properties dialog box for the Client resource.
Editing a global Directive resource
You can edit the directive statement, description, or RDZ of a global Directive resource. To
rename a global directive, delete the global directive and create a global directive with
the new name.
Procedure
1. In the Administration window, click Server.
2. In the expanded left pane, select Directives.
3. In the right pane, perform one of the following tasks:
328
l
To modify multiple attributes in a single configuration resource by using the
Directive Properties window, right-click the staging configuration and select
Properties.
l
To modify a specific attribute that appears in the resource window, place the
mouse in the cell that contains the attribute that you want to change, then rightclick. The menu displays an option to edit the attribute. For example, to modify the
Comment attribute, right-click the resource in the Comment cell and select Edit
Comment.
EMC NetWorker 9.0.x Administration Guide
Backup Options
Note
To modify a specific attribute for multiple resources, press and hold the Ctrl key,
select each resource, and then right-click in the cell that contains the attribute that
you want to change. The menu displays an option to edit the attribute.
4. Edit the settings for the global directive, then click OK.
Copying a global Directive resource
Procedure
1. In the Administration window, click Server.
2. In the expanded left pane, select Directives.
3. In the right pane, right-click the directive and select Copy.
The Create Directive dialog box appears with the settings from the original directive.
4. In the Name box, specify a name for the directive.
5. Edit the other settings for the directive as necessary.
6. Click OK.
After you finish
Apply the global directive to a Client resource by selecting the directive from the Directive
list on the General tab of the Client Properties dialog box for the Client resource.
Deleting a global Directive resource
Before you begin
l
Ensure that the global Directive resource is not a default global Directive resource.
You cannot delete global Directive resources that are available by default when you
install the NetWorker server software.
l
Ensure that the Directive resource is not selected for any Client resources.
Procedure
1. In the Administration window, click Server.
2. In the expanded left pane, select Directives.
3. In the right pane, right-click the directive and select Delete.
A confirmation message appears.
4. Click Yes.
NetWorker User local directives
On Windows clients, users with local Windows Administrator or Backup Operator
privileges can create local directives by using the NetWorker User program. These
directives are stored on the client in a file named networkr.cfg.
When you perform a manual backup from the NetWorker User program, only local
directives that were created with the NetWorker User program are enforced. Global
directives and local directive files (nsr.dir files) are not enforced. However, all local
directives are enforced when the NetWorker save command without the -i option is run
at the command prompt.
NetWorker User program local directives are also enforced during scheduled backups and
archive operations.
NetWorker User local directives
329
Backup Options
Procedure
1. Log in to the client computer as a member of either the local Windows Administrators
or Backup Operators security group.
2. Start the NetWorker User Program.
3. From the Options menu, select Local Backup Directives.
4. Set the local directive for each data item. You can clear data items to exclude them
from scheduled backups, and select items for password protection, encryption, and
compression. This applies for both manual and scheduled saves.
Note
If password protection or encryption is selected, the password must be specified first.
5. From the File menu, select Save Backup Directives to save changes.
Depending on user privileges and the operating system version, the networkr.cfg
file is created in one of the following locations:
l
If you are logged in with local Windows Administrator or Backup Operator
privileges, networkr.cfg is created in the root of the system volume (usually C:
\).
l
If you are not logged in with local Windows Administrator or Backup Operator
privileges, networkr.cfg is created in %SystemDrive%\Documents and
Settings\User_name\Application Data\EMC NetWorker.
Note
The Application Data directories are hidden by default. To view these
directories by using Windows Explorer, select Tools > Folder Options. On the View
tab of the View Options dialog box, select the Show hidden files and folders
option.
Creating local directives
Local directives are text files that are on the file system of the client. The directives apply
only to the immediate data within the path where the directive file is saved.
Procedure
1. Use a text editor to create the directive file in the directory that contains the files to
which you plan to apply the directive.
2. Create the directive statement.
A directive statement specifies the files and directories for a directive statement, and
then an ASM specification or a save environment keywords specifies the action to
perform. You can also include comments in a directive statement by preceding text
with a hash (#) character.
For example, the following directive statement skips the C:\TEMP folder on a
Windows system during a backup:
<<"C:\TEMP">>
skip
330
EMC NetWorker 9.0.x Administration Guide
Backup Options
NOTICE
Do not leave blank lines in the directive statement.
Format of directive statements on page 323 provides more infromation about how to
create a directive statement.
3. Save the local directive file.
l
On Windows, the file must be named nsr.dir. The user account that creates the
file must have the permissions to create files either within the root of the volume
or in a folder within the volume.
l
On UNIX, the file must be named .nsr.
Creating local directives
331
Backup Options
332
EMC NetWorker 9.0.x Administration Guide
CHAPTER 6
Backing Up Data
This chapter contains the following topics:
l
l
l
l
l
l
l
l
l
l
l
l
l
l
Configuring a Client resource for backups on Windows hosts ............................. 334
Configuring a Client resource for backups on UNIX hosts .................................... 373
Configuring a Client resource for backups on Mac OS X hosts ............................. 381
Sending client data to AFTD or Data Domain devices only.................................... 386
Non-ASCII files and directories............................................................................ 386
Configuring checkpoint restart backups.............................................................. 386
Probe-based backups......................................................................................... 391
Encryption and compression............................................................................... 392
Compression.......................................................................................................394
Configuring Client Direct backups........................................................................395
Backup command customization........................................................................ 397
Client resources.................................................................................................. 403
Manual backups................................................................................................. 408
Verifying backup data......................................................................................... 410
Backing Up Data
333
Backing Up Data
Configuring a Client resource for backups on Windows hosts
This section describes how to configure a Client resource to backup data on Windows
hosts.
Windows backup considerations
Use the NetWorker software to back up Window file systems. The NetWorker Module for
Microsoft (NMM) provides VSS-based backup and recovery of the Windows operating
system and Microsoft server applications such as Microsoft Exchange Server, Microsoft
SQL Server, and Microsoft SharePoint Services.
The EMC NetWorker Module for Microsoft Administration Guide provides more information
about the NMM product.
Configuring how NetWorker determines when to back up a file
You can configure NetWorker to back up a file that is based on the setting of the Archive
file attribute in the properties of a Windows file or based on the modification time.
The NetWorker software saves a file when the Archive attribute is enabled. After
NetWorker saves the file, the NetWorker software disables the Archive attribute. If you
restore the file from a backup, then the NetWorker software enables the Archive attribute
to ensure that the next backup includes the file.
To configure NetWorker to use the modification time of a file instead of the Archive
attribute, perform the following steps:
1. Browse to Control Panel > System > Advanced System Settings.
2. On the Advanced tab, click Environment Variables...
3. In the System Variables section, click New.
4. In the Variable name field, type NSR_AVOID_ARCHIVE.
5. In the Variable value field, type Yes.
6. Click OK to close the Environment Variables window, and then click OK to close the
System Properties window.
7. Log off or restart the client computer, or restart the NetWorker Remote Exec
Service to make Windows aware of the environment variable change.
Backup Operators group
The Windows Backup Operators local group provides its members the privileges
necessary to back up and recover data from a Windows computer.
Users who request backups must be in the Backup Operators or Administrators group of
the domain into which they are logged. The Backup Operators group is assigned on a
computer-by-computer basis, rather than globally by the domain. If you are having
trouble performing tasks on one NetWorker server but not another, check the Backup
Operators group on the problematic computer to ensure that you are correctly assigned.
Enabling NetWorker logging operations performed by backup operator
By default, members of the Windows Backup Operators group do not have write
permission to the <NetWorker_install_path>\logs directory.
NetWorker log operations are performed by members of the Windows Backup Operators
group.
334
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Enable NetWorker logging for Backup Operators by modifying the security settings on the
<NetWorker_install_path>\logs directory. For example:
Procedure
1. In Windows Explorer, navigate to the <NetWorker_install_path>\logs directory.
2. Right-click the <NetWorker_install_path>\logs directory icon and select
Properties.
3. On the Security tab of the Properties dialog box, add the Backup Operators group to
the list of groups and users.
4. Select the Backup Operators group and click Allow Write.
5. Click OK.
Windows backup considerations
Use the NetWorker software to backup Windows file systems. NetWorker Module for
Microsoft (NMM) provides VSS-based backup and recovery of the Windows operating
system, and Microsoft server applications, for example, Microsoft Exchange Server,
Microsoft SQL Server, and Microsoft SharePoint Services. The EMC NetWorker Module for
Microsoft Administration Guide provides more information about the NMM product.
Table 64 Backup considerations for Windows features
Windows Feature
Backup considerations
Event logs—Used for
troubleshooting hardware
problems as well as
monitoring security
conditions, and system
and application software
problems.
To back up event log files, configure a file system
backup that includes the C:\Windows\system32\winevt
\logs folder.
Encrypted File System
(EFS)—Allows NTFS files
to be stored in encrypted
format. A user without the
private key to the file
cannot access the file.
NetWorker software will not encrypt or compress a file already
encrypted by Windows. Do not use AES encryption when you backup
EFS encrypted files.
The size of a recovered event log might be smaller than
the backup size. This is a characteristic of Windows event logs
and does not cause any data loss or change of data. You can
use Microsoft Event Viewer to view the recovered, smaller log
file. NetWorker backs up all event log files when more than one
active event log is marked for backup (for example,
SecEvent.Evt and SysEvent.Evt). You can recover event logs
to a location that differs from the location at the time of the
backup. You cannot recover event logs files that were on an
NTFS partition at the time of the backup to an FAT16 or FAT32
partition.
Files can become unusable if the encryption keys
change on the domain controller. For example, when you move
the domain controller from one computer to another or the
domain controller failures.
NetWorker does not backup the encryption keys, or
keep a copy of the keys to ensure a successful recovery of
EFS encrypted files to an EFS that you reinstall after a disaster.
When recovering encrypted files to an encrypted folder
that has been removed, consider the following:
Windows backup considerations
335
Backing Up Data
Table 64 Backup considerations for Windows features (continued)
Windows Feature
Internet Information
Server (IIS)— A web server
that enables the
publication of information
on the Internet or a
corporate intranet by
using HTTP.
Backup considerations
l
If you recover the encrypted files and the encrypted folder, the
recovered folder and files are all encrypted.
l
If you recover only individual encrypted files (but do not recover
the encrypted folder that contains them) the individual recovered
files are encrypted but the re-created folder is not encrypted.
Windows documentation provides instructions on encrypting the
re-created folder.
l
Windows EFS encrypted data is backed up and recovered in its
encrypted state.
The NetWorker software uses the active metabase to back up IIS and
can restore the backup versions to the metabase location. NetWorker
supports the recover of the metabase to the default location
%SystemRoot%\system32\inetsrv\MetaBase.bin or in a
location that you specify in the registry. The Microsoft documentation
provides information about how to create a registry key that specifies
an alternate metabase location.
Sparse files— Enables a
The NetWorker software provides complete backup and recovery
program to create huge
support for sparse files.
files without actually
committing disk space for
every byte.
Windows Print Queues
NetWorker backs up and recovers print queues as a part of the file
system backup. During a recover operation, you may have to restart
the host depending on the status of the print queue at the time of the
backup.
Disk quota database
The WINDOWS ROLES AND FEATURES save set contains the disk quota
database. During a backup operation, the NetWorker software creates
temporary files to store the disk quota database settings in the root
directory of each drive on the client.
Note
To backup the disk quota database, the local system account must
have full control permissions on the local drive, otherwise a backup
fails with an error message similar to the following: Failed to
write to quota file, 0x80070005
POSIX compliance
NetWorker performs case sensitive backup and
recovery operations. During a recovery operation on a Windows
host, NetWorker may create multiple files with the same name
but different cases.
For example, you back up a file on a Windows host that is named
temp.txt. The file is later deleted and created with a new file
named Temp.txt. When you select the temp.txt file for recovery,
NetWorker will not overwrite the file that is named Temp.txt. You
will have two identical files in the directory, one named temp.txt
and the other named Temp.txt.To configure NetWorker to ignore
336
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Table 64 Backup considerations for Windows features (continued)
Windows Feature
Backup considerations
the case of a file, you can set the system environment variable
NSR_DISABLE_POSIX_CREATE=YES, which disables POSIX compliance.
Windows Dynamic Host
Configuration Protocol
(DHCP) and Windows
Internet Naming Service
(WINS) databases
The WINDOWS ROLES AND FEATURES component of the
DISASTER_RECOVERY:\ save set contains the DHCP and WINS
databases. Use Windows BMR recovery to perform an offline restore
of these databases.
Native Virtual Hard Disk
(VHD) volumes—Used as
a mounted volume on
designated hardware
without any other parent
operating system, virtual
machine, or hypervisor.
You can use a VHD
volume as a boot volume
or as a data volume.
The ALL save set does not include native VHD volumes. Configure a
separate client resource to backup native VHD volumes. Do not use
VHD volumes as critical volumes if the volume that contains the
native VHD is also a critical volume. This situation creates a conflict
during a Windows BMR backup.
Windows Content Index
Server (CIS) or Windows
Search Index— Index the
full textual contents and
property values of files
and documents that are
stored on the local
computer. The
information in the index
can be queried from the
Windows search function,
the Indexing Server query
form, or a web browser.
The WINDOWS ROLES AND FEATURES component of the
DISASTER_RECOVERY:\ save set contains the CIS or Windows Search
Index. The CIS or Windows Search is automatically regenerated on
system restart.
NetWorker performs the following actions when
performing a CIS or Windows Search backup:
l
Pauses any CIS or Windows Search catalogs. You can still query a
paused catalog, so the indexing functionality is no lost during the
CIS or Windows Search backup.
l
Backs up all catalog files.
l
Turns on the catalogs when the backup completes.
l
CIS or Windows Search deletes the catalog folder during a
backup and restores it as part of a recovery operation.
DHCP and WINS databases
The WINDOWS ROLES AND FEATURES component of the DISASTER_RECOVERY:\
save set contains the Windows Dynamic Host Configuration Protocol (DHCP) and
Windows Internet Naming Service (WINS) databases. Use Windows BMR recovery to
perform an offline restore of these databases.
The ALL save set also includes the DHCP and WINS databases because the ALL save set
automatically includes the DISASTER_RECOVERY:\ save set.
If you do not specify the ALL save set or the DISASTER_RECOVERY:\ save set in the
Save set attribute for the client, then include the databases as part of a file system
backup:
l
To back up a DHCP database, include the %SystemRoot%\System32\dhcp
directory in the Save set attribute of the Client resource for the DHCP server.
Windows backup considerations
337
Backing Up Data
l
To back up a WINS database, use the Microsoft WINS administrative tools to
configure an automated backup of the WINS database to a local drive on the WINS
server. Then specify the path to the database backup on the local drive in the Save
set attribute of the Client resource for the WINS server.
Hard links
You can back up and recover files with hard links on a Windows client. However, the hard
links of files that are created by using a Portable Operating System Interface (POSIX)
application are not preserved during recovery.
Support for hard links is disabled by default to improve performance.
Backup and recovery of hard links is disabled by default to improve performance. To
enable backup and recovery of hard links on a client, select the Hard links checkbox on
the Globals (2 of 2) tab of the Client Properties dialog box for the Client resource.
Enable diagnostic mode view by selecting View > Diagnostic Mode in the Administration
window to access the Hard links checkbox.
Microsoft DFS
You can back up and restore Microsoft Distributed File System (DFS) data.
Microsoft DFS is a Windows file system feature that enables you to create a namespace of
shared directories that are physically distributed across a network. With DFS, you can
organize a set of distributed directories logically, according to any scheme you choose, to
provide centralized access to files that reside in a variety of locations.
DFS junctions
A DFS junction is a DFS root or link:
l
A DFS root is a namespace for files and DFS links.
l
A DFS link is a connection to a shared file or folder.
DFS junctions are file system objects, not files or directories. Therefore, the NetWorker
software does not treat DFS junctions the same as files or directories for backup and
recovery. However, DFS junctions appear as files and directories in the NetWorker User
program.
DFS backups with the ALL-DFSR save set
The All-DFSR save set includes all DFS related save sets for a backup. Unlike other allinclusive save set types, ALL-DFSR is not related to any particular file system. ALLDFSR backs up all components that are defined by DFS\FRS writers. Backups fail if you
specify ALL-DFSR for a system where DFS or FRS is not installed.
The syntax for this save set is ALL-DFSR. It is not case sensitive.
The ALL-DFSR save set does not support BBB. BBB only creates backups at the volume
level, and DFSR replication folders can be a subfolder, which creates a conflict.
Synthetic full backup is not supported with ALL-DFSR.
The ALL-DFSR save set registers the corresponding writer and writer component nodes
under WINDOWS ROLES AND FEATURES. All Replication folders are restored through
these nodes.
Configuring a scheduled DFS backup
To avoid inconsistencies among the various save sets, configure a scheduled backup that
includes the DFS topology information, junctions, and destination directories.
Alternatively, you can use the ALL-DFSR save set.
338
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
NOTICE
When a DFS client resource is run for the first time, the save set sizes should be verified
to ensure that they are correct.
To configure a scheduled backup for a DFS:
Procedure
1. In the Administration screen, include the following clients in the NetWorker group that
will back up the DFS:
l
The DFS host server
l
Any computer where remote DFS destination directories reside
l
A domain controller (domain-based DFS only)
For example, you could create a NetWorker group named DFS, then make each of
the preceding clients a member of the DFS group.
2. Enter the following save sets in the Save Set attribute of the DFS host server’s client
resource:
l
The DFS root. For example, C:\MyDfsRoot.
l
DFS destination directories that reside on the DFS host. For example, D:
\MyLocalDir
Note
DFS destination directories are also be backed up if you enter the entire volume
(for example, D:\) in the Save Set attribute.
3. For clients where remote DFS destination directories reside, enter the destination
directory paths in the Save Set attribute. For example:
E:\MyRemoteDir
E:\MyOtherRemoteDir
E:\
Windows Optimized Deduplication
NetWorker supports backup of optimized data deduplication volumes and files and can
restore optimized deduplication backups to a set of eligible restore targets.
Note
Due to recovery performance issues observed with optimized backup for Windows
deduplication volumes, EMC recommends non-optimized backup. When you set the
backup to non-optimized, the deduplicated files get rehydrated in memory before they
are backed up. This type of backup requires you to enable VSS. If you disabled VSS (for
example, by specifying VSS:*=off in the Save Operations attribute), the backup will
potentially back up the chunk stores unnecessarily. To back up the deduplicated volume,
EMC recommends using block based backup (BBB) instead. If you still require optimized
backup, you can add VSS:NSR_DEDUP_NON_OPTIMIZED=no to the Save Operations
attribute to restore settings to the traditional (non-BBB) optimized backup. However, EMC
does not recommend using this setting as the recovery performance issues may result in
an unusable backup.
NetWorker supports the data deduplication feature on Windows Server 2012, Windows
Server 2012 R2, Windows Storage Server 2012, and Windows Storage Server 2012 R2.
Windows backup considerations
339
Backing Up Data
NetWorker does not support the feature on Windows 8 client computers or computers
that run the older versions of the Windows operating system. On computers that run the
Windows Server operating system, NetWorker supports the feature on volumes that use
the NTFS file system, which can be part of a fail over cluster, including CSV volumes.
By default NetWorker performs an optimized deduplication backup on an optimized
deduplication volume, unless the backup path is a subdirectory of the volume or when
you specify the non-optimized deduplication save option in the Save operations field of
the Client resource. When you define the non-optimized deduplication save option,
NetWorker will not deduplicate the backup. When the path is a subdirectory of a volume,
NetWorker does not create an optimized backup.
To back up and restore Windows Server deduplication volumes or files, you must use a
NetWorker 8.1 or later client. You can only restore deduplicated backups to computers
that run on supported versions of Windows Server that have the data deduplication role
enabled. The data deduplication role is a child role of File Services, which is a File and
Storage Services role.
Detecting Deduplication in a Backup
When a deduplication volume is backed up, you can verify the form of the data that was
backed up. This information is identified in the mminfo extended save set attributes
output. To show all extended save set attributes, use the mminfo output flag -r attrs.
Deduplication backups are indicated with *MSFT_OPTIMIZED_DEDUP_ENABLED:yes.
For more information on mminfo, refer to the EMC NetWorker Command Reference Guide or
the mminfo man pages.
Data Deduplication Backup and Restore
NetWorker supports two types of backup and four types of restores for data stored on a
deduplication volume.
Optimized full-volume backup
Optimized full-volume backups are the default backup type for Windows data
deduplication volumes. The backup type occurs when the non-optimized data
deduplication save option is not specified and the backup path is a mount point, drive
letter or full volume backup. NetWorker full, incremental, and synthetic full backups are
supported with Windows data deduplicated volumes.
The optimized data deduplication files that are part of the backup include:
l
Windows data deduplication reparse points
l
Chunk store containers and data deduplication meta data files
NetWorker backup does not differentiate whether a volume is configured for data
deduplication, except to add the media database attribute if the volume is deduplicated.
The media database attribute, *MSFT_OPTIMIZED_DEDUP_ENABLED, is set to true and is
saved as part of an optimized data deduplication volume save set.
For Windows BMR, the Windows Server 2012 and Windows Server 2012 R2 data
deduplication writer is not part of the system state. Additionally, data deduplication
volumes can be critical volumes and are supported with Windows BMR.
Unoptimized full and incremental backup
NetWorker creates an unoptimized data deduplication backup under the following
conditions:
340
l
When you specify in the save set attribute of the client resource, a backup path that is
a subdirectory of the volume, except in the case where the subdirectory is the root of
a mount point.
l
When you perform a manual backup of the client that does not make up the entire
volume.
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
l
When you specify the string VSS:NSR_DEDUP_NON_OPTIMIZED=yes in the save
operations settings of the client resource. If the save operation flag is set to yes the
data deduplication backup is not optimized. If no string is present, or if the attribute
is set to no, a normal volume level backup is performed.
To add this string:
From the NetWorker Administration console select Properties menu.
1. On the On the Client Properties text box, select the Apps & Modules tab.
2. In the Save operations field, enter the string and attribute setting and then click
OK.
In an unoptimized data deduplication backup, all files are rehydrated before the
back up is performed. The deduplication chunk store directory is not backed up.
windows dedup backups, either optimized or unoptimized, will be corrupt if they
are backed up with VSS off.
Reasons to create an unoptimized data deduplication volume backup include:
l
Support restores of a Windows Server 2012 and Windows Server 2012 R2 backups to
an earlier version of Windows Server.
l
Support restores of a Windows Server 2012 Windows Server 2012 R2 backups to a
non-Windows computer.
Full volume restore to original path on the original computer
NetWorker supports a restore to the original volume mount path on the original server. All
optimized files newer than the backup time of the restore save sets are rehydrated to
prevent data loss.
When a deduplicated CSV volume is restored, CSV ownership is moved to the cluster
node where the restore is being performed. This ensures that deduplication jobs and
data access can be disabled during the restore process. The CSV is assigned back to
original ownership when the restore is complete.
Full volume restore to original path on a different computer
NetWorker supports a restore of a data deduplication backup from one computer to the
same volume mount path on another compatible computer. Part of this type of restore
includes validation checks to ensure that Windows Server 2012 or Windows Server 2012
R2 is installed on the target computer and that the deduplication role is enabled.
You can manually reformat the volume, but this is not a requirement for NetWorker. The
restore can only take place if the volume does not have a pre-existing chunk store.
Additionally, the volume will be enabled for data deduplication after the restore is
complete.
Support for save set restore of level FULL backups
A save set restore of a FULL backup is identical to a full volume restore with the following
limitations:
l
Limited to level Full backups in order to maintain chunk store integrity.
l
Limited to volume level restores to the same path on the same computer where the
backup was performed.
l
No support for selective file restores due to insufficient information about the save
set’s restore context.
File level restore
File level restore is performed if the volume to be restored is a subset of the original
volume or if the restore is to a different volume. All files are restored in rehydrated form.
The data deduplication meta data and chunk stores are not restored. For file level
restores, the system account of the host where the restore is performed has to be a
Windows backup considerations
341
Backing Up Data
member of the NetWorker server's NetWorker Operators User Group. For example, if you
are performing a dedup file level restore on host1, add system@host1 to the group.
NOTICE
If an optimized deduplication restore is aborted, it is likely to have mismatched reparse
point and chunk store entries. This restored volume is not a valid restore. You must
restore the backup again and allow the restore process to complete.
Windows Data Deduplication Volume Best Practices
Review the following information, which describes the recommended best practices when
you backup volumes that have Windows data deduplication enabled.
l
A full backup should be performed immediately after deduplication has been enabled
on a volume.
l
Windows performs garbage collection on the chunk store of each deduplicated
volume to remove no-longer-used chunks. By default, a garbage collection job is
scheduled weekly for data deduplicated volumes. A full backup should be scheduled
to run after garbage collection, because the garbage collection job may result in many
changes in the chunk store, as a result of file deletions since the last garbage
collection job.
l
If there is significant chunk store container activity, control the size of incremental
backups by limiting the frequency of Windows deduplication optimization jobs.
l
Avoid performing extremely large file level restores. If a large percentage of a volume
is restored, it is more time efficient to restore the entire volume. Because file level
restores recover files in rehydrated form, a file level restore that includes many files
might take up more space than is available on the volume.
l
If a large file level restore is to be performed, first perform a full backup of the volume
in its current state.
l
When you choose to unoptimize many files at once from an optimized deduplication
backup, the process can take a significant period of time. The selected files restore
feature is best used to restore a moderate number of files. If most of a volume is to be
restored, a full volume restore is a preferred solution. If a small amount of data needs
to be skipped, that data can be moved to a temporary storage area, then back to its
original location after the volume level restore is completed.
Recommended Deduplication Workloads
Based on recommendations by Microsoft, the ideal workloads for data deduplication
include:
l
General file shares: Group content publication/sharing, user home folders and profile
redirection (offline files)
l
Software deployment shares: Software binaries, images, and updates
l
VHD libraries: VHD file storage for provisioning to hypervisors
For NetWorker, AFTD device directories are good candidates for deduplication. AFTD
directories contain a large number of redundant data blocks, which in general are
infrequently accessed.
Short filenames
You can back up and recover the short filenames that are automatically assigned by the
Windows filename mapping feature.
Windows filename mapping is an operating system feature in which each file or folder
with a name that does not conform to the MS-DOS 8.3 naming standard is automatically
assigned a second name that does. For example, a directory named Microsoft
Office might be assigned a second name of MICROS~2.
342
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Backup and recovery of short filenames is disabled by default to improve performance.
To enable backup and recovery of short filenames on a client, select the Short filenames
checkbox on the Globals (2 of 2) tab of the Client Properties dialog box for the client
resource.
You must enable diagnostic mode view by selecting View > Diagnostic Mode in the
Administration window to access the Short filenames checkbox.
Volume mount points
You can back up and restore data available through a volume mount point (or mount
point) on a Windows client.
Assigning a drive letter to a mount point is optional. Many disk volumes can be linked
into a single directory tree, with a single drive letter assigned to the root of the host
volume.
To include mount points in scheduled backups for a client, specify the host volume and
each mount point in the Save set attribute on the General tab of the Client Properties
dialog box for the Client resource. For example, to back up a single mount point on drive
D:\ and all its data, type D:\mount_point_name in the Save set attribute.
To include nested mount points in scheduled backups, either use the ALL save set or
specify the host volume and the full path to each mount point. For example, to back up
three nested mount points and their data on drive D:\, type the following values in the
Save set attribute:
D:\mount_point_name1
D:\mount_point_name1\mount_point_name2
D:\mount_point_name1\mount_point_name2\ mount_point_name3
To include mount points in a manual backup with the NetWorker User program, select the
checkbox next to the mount point name within the host volume entry in the Backup
window.
To perform a manual backup of nested mount points and their data, perform a separate
backup for each mount point. When you select a mount point in the Backup window, all
files, directories, and nested mount points beneath the mount point are selected by
default. Before you start the backup, clear the checkboxes next to any nested mount
points. Then perform separate backups for the nested mount points.
Windows file system backups
You can configure NetWorker to use VSS technology to backup file systems on a Windows
host. You can recover individual file system objects from a VSS backup.
Overview of VSS
If the NetWorker Module for Microsoft is installed on the client computer, information in
this chapter may be superseded by information in the NetWorker Module for Microsoft
documentation. The EMC NetWorker Module for Microsoft Administration Guide provides
more information about the NetWorker Module for Microsoft.
Volume Shadow Copy Service (VSS) is a Microsoft technology that acts as a coordinator
among all the components that create, archive, modify, back up, and restore data,
including:
l
The operating system
l
Storage hardware
l
Applications
Windows file system backups
343
Backing Up Data
l
Utility or backup programs, such as NetWorker software
VSS allows for the creation of a point-in-time snapshot, or temporary copy, of a volume.
Instead of backing up data directly from the physical file system, data is backed up from
the snapshot. In addition, VSS allows for a single, point-in-time capture of the system
state.
NetWorker uses VSS technology to create snapshot backups of volumes and exact copies
of files, including all open files. Databases and files that are open due to operator or
system activity are backed up during a volume shadow copy. In this way, files that have
changed during the backup process are copied correctly.
Shadow copy (snapshot) backups ensure that:
l
Applications can continue to write data to the volume during a backup.
l
Open files are not omitted during a backup.
l
Backups can be performed at any time, without locking out users.
Note
VSS backups do not use snapshot policies, which are required to perform snapshot
backups. The Snapshot Integration Guide documentation provides more information.
VSS and the backup process
In VSS terms, NetWorker software is a requestor — an application that needs data from
other applications or services. When a requestor needs data from an application or
service, this process occurs:
1. The requestor asks for this information from VSS.
2. VSS reviews the request for validity.
3. If the request is valid and the specified application has the requested data, the
request goes to the application-specific writer, which prepares the requested data.
Each application and service that supports VSS has its own writer, which understands
how the application or service works:
1. After the writer signals that it has prepared the data, VSS directs the writer to freeze
I/O to the selected volumes, queuing it for later processing.
2. VSS then calls a provider to capture the requested data.
3. The provider, which is either software-based or associated with particular hardware
(for example, a disk array), captures the prepared data, creating a snapshot (or
shadow copy) that exists side-by-side with the live volume. Provider support on page
345 contains more information.
The process of creating a snapshot involves interaction with the operating system. The
amount of time it takes to create a snapshot depends on a number of factors, including
the writer activity taking place at the time. Once the snapshot is created, the provider
signals VSS, which tells the writer to resume activity. I/O is released to the selected
volumes and any queued writes that arrived during the provider's work are processed.
The following figure provides a graphical representation of the VSS backup process.
344
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Figure 42 VSS backup process
This figure provides a graphical representation of the VSS backup process:
1. NetWorker software (the requestor) asks VSS to enumerate writers and gather their
metadata.
2. Writers provide an XML description of backup components and define the recover
method.
3. VSS asks which providers can support a snapshot for each of the required volumes.
4. Requestor asks VSS to createsnapshot.
5. VSS tells the writers to freeze activity.
6. VSS tells the providers to create the snapshot of the current state on disk.
VSS tells the writers to resume activity.
NetWorker software backs up data from the point-in-time snapshot that is created during
this process. Any subsequent data access is performed on the snapshot, not the live (inuse) file system. The requestor has no direct contact with the provider; the process of
taking a snapshot is seamlessly handled by VSS. Once the backup is complete, VSS
deletes the snapshot.
Provider support
By default, the NetWorker client always chooses the Windows VSS system provider for
backups. If you want to use a hardware provider or a specific software provider for a
Windows file system backups
345
Backing Up Data
particular NetWorker client, enter the following command in the NetWorker client
resource Save Operations attribute:
VSS:VSS_ALLOW_DEFAULT_PROVIDER=yes
When the previous command is specified for a NetWorker client, a backup provider is
selected based on the following default criteria as specified by Microsoft:
1. If a hardware provider that supports the given volume on the NetWorker client is
available, it is selected.
2. If no hardware provider is available, then if any software provider specific to the given
NetWorker client volume is available, it is selected.
3. If no hardware provider and no software provider specific to the volumes is available,
the Microsoft VSS system provider is selected.
Controlling VSS from NetWorker software on page 347 provides more information
about specifying VSS commands for a NetWorker client. VSS commands on page 348
provides information about other VSS commands.
NOTICE
Windows Bare Metal Recovery backups always use the Windows VSS system provider
even if the VSS:VSS_ALLOW_DEFAULT_PROVIDER=yes command is specified for the
NetWorker client resource.
Troubleshooting hardware providers
If you have specified the VSS:VSS_ALLOW_DEFAULT_PROVIDER=yes command as
described in Provider support on page 345 and the hardware provider and NetWorker are
incompatible, try one of the following workarounds:
l
Uninstall the hardware provider.
l
Migrate any data that is backed up by the NetWorker client to a disk LUN (Logical Unit
Number), such as C:\, that is not controlled by a hardware provider. In this way, the
NetWorker client will backup all data using the software provider.
Be aware that if the NetWorker Module for Microsoft is installed on the client host, then
the previously mentioned workarounds may not be required. Refer to the NetWorker
Module for Microsoft documentation for details.
The importance of writers
Writers play an important role in correctly backing up data. They provide metadata
information about what data to back up, and specific methods for correctly handling
components and applications during backup and restore. They also identify the type of
application or service that is being backed up. Writers do not play a role in backing up the
file system.
Writers are currently only available for active services or applications. If a service or
application is present on a system but is not active, information from its writer is not
available. Consequently, a writer can appear or disappear from backup to backup.
Also, NetWorker software maintains a list of supported writers in the NSRLA database of
the client computer. When backing up data, the software checks to ensure that these
conditions exist:
l
The writer that is associated with the application is present on the system and active.
l
The writer appears on the list of supported writers in the NSRLA database.
l
A user has not disabled the writer.
If these conditions are all true for a particular writer, NetWorker software defaults to
backing up data by using VSS technology. If any of the conditions are false for a
346
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
particular writer, the data that is served by that writer is excluded from the backup
operation.
List of supported writers
During a VSS backup operation, NetWorker software validates each writer against a list of
supported writers. As part of a software release, or between releases, there may be
updates to the list of supported writers. The EMC NetWorker Software Compatibility Guide
provides a list of the currently supported writers.
Controlling VSS from NetWorker software
By default, NetWorker uses VSS technology to back up a client. For VSS SYSTEM save
sets, this means NetWorker software uses VSS for most save sets and writers. For the file
system, this means the software tries to take a snapshot of each drive, but if it fails, then
it saves the file system by using the legacy method (that is, no snapshot is taken). During
a particular backup for an individual client, either the VSS method or the legacy method
is used, but not both.
There may be times when you need finer control over how NetWorker software uses VSS.
For example, if you must disable VSS. You can control VSS from the Administration
window, the NetWorker User program, or the command prompt.
Controlling VSS from the Administration window
Procedure
1. From the Administration window, click Protection.
2. Click Clients.
3. Right-click the client for which you want to control VSS, then select Properties. The
Properties dialog box appears, with the General tab displayed.
4. Click the Apps & Modules tab.
5. In the Save Operations attribute, type the command, then click OK.
l
Separate multiple commands with a semicolon (;).
l
If the Save Operations attribute is left blank, NetWorker software backs up data by
using VSS.
Notes:
l
The Save Operations attribute does not support NetWorker Module save sets. If a
NetWorker Module save set name is entered in the window, the backup fails.
l
If you enter a VSS command in the Save Operations attribute of the Administration
window, the command runs when the client backup is started as part of a save set.
l
Use the Save Operations attribute only for clients running NetWorker software release
7.2 or later. If anything is entered in this attribute for a client that is running an earlier
NetWorker software release, the backup will fail.
Control VSS from the command-prompt
You can control VSS from the command-prompt on a NetWorker client or the NMC server
by using the -o option and the Save Operations commands, but only while performing a
save, savefs, or nsrarchive operation.
For example, to completely disable VSS while backing up C:\myfile to the server jupiter,
type:
save -s jupiter -o "vss:*=off" "C:\myfile"
Although the server name is not required in the preceding command example, include
the name to ensure that the save command finds the correct server. Separate multiple
Save Operations commands with a semicolon (;).
Windows file system backups
347
Backing Up Data
The EMC NetWorker Command Reference Guide provides more information about the save,
savefs, and nsrarchive commands.
Note
If you change the VSS setting on a client by using the Local Save Operations dialog box or
the command prompt, it does not affect that client’s VSS setting on the server. Likewise,
if you change a client’s VSS setting on the server, it does not affect the Local Save
Operations setting or the command-prompt VSS setting on the client.
Globally disabling VSS
Use the nsradmin program to disable VSS for all clients globally or only for clients with a
certain Windows operating system.
To disable VSS:
Procedure
1. Log in as root or as Windows Administrator on the NetWorker server.
To disable VSS for all NetWorker clients:
a. Create an input file for the nsradmin command. The input file eliminates
interactive prompting as each client gets updated. For example, create a text file
that is named disable-vss.txt and type the following into the file:
show name; client OS type; Save operations
print type: NSR client
update Save operations: "VSS\:*=off"
print
To disable VSS only for clients on a particular Windows operating system such as
Windows NT:
b. Create an input text file. For example, create a file that is named disable-vss-nt.txt
and type the following into the file:
show name; client OS type; Save operations
print type: NSR client; client OS type: "Windows NT Server on
Intel"
update Save operations: "VSS\:*=off"
print
2. Type either of the following at the command prompt:
nsradmin -i <path>\disable-vss.txt nsradmin -i <path>\disable-vssnt.txt
where <path> is the directory location of the input file.
VSS commands
This section lists the commands and syntax that are used to control VSS.
348
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Table 65 VSS Save operation attribute values
Task
Save operations attribute
Behavior
To enable
VSS.
Blank
Leaving the attribute empty results in
NetWorker software automatically
using VSS.
To
completely
disable
VSS.
VSS:*=off
VSS backups will not occur and
backing up the following save sets for
a NetWorker client resource yields
these results:
l
DISASTER_RECOVERY:\ save set
Backup fails at the beginning of
backup operation.
l
All save set
Backups fail.
To use a
VSS:VSS_ALLOW_DEFAULT_PROVIDER=yes A backup provider is selected based
hardware
on the following default Microsoft
provider or
criteria:
a specific
If a hardware provider that supports
software
the particular volume on the
provider for
NetWorker
a NetWorker
client is available, it is selected.
client
backup.
If no hardware provider is available,
then if any software provider specific
to
the particular NetWorker client volume
is
available, it is selected.
If no hardware provider and no
software provider specific to the
volumes
is available, the Microsoft VSS system
provider is selected.
Windows Bare Metal recovery
backups always use the Windows VSS
system provider even if the
VSS:VSS_ALLOW_DEFAULT_
PROVIDER=yes command is specified
for the NetWorker client resource.
Windows Bare Metal Recovery on page
350
provides more information about
Windows
Bare Metal recovery backups.
Windows file system backups
349
Backing Up Data
Windows Bare Metal Recovery
You can configure a Windows Bare Metal Recovery (BMR) backup on a Windows host.
NetWorker Windows BMR is an automated recovery solution that uses the Windows ASR
writer and other Microsoft VSS writers to identify critical volumes and perform a full
recovery on a target host. You cannot recover individual file system objects from a
Windows BMR backup.
Terminology
The following list provides a description of typical Windows BMR backup and recovery
terminology. The road map indicates which steps you must perform before you try a
Windows BMR. recovery
This chapter uses the following terms to describe NetWorker support for Windows BMR
technology:
Bare Metal Recovery (BMR)
The operation that restores the operating system and data on a host after a
catastrophic failure, such as a hard disk failure or the corruption of critical operating
system components. A BMR is an automated process that does not require the
manual installation of an operating system. NetWorker provides an automated BMR
solution for Windows that uses the Windows ASR writer and other Microsoft VSS
writers to identify critical volumes and perform a full recovery on a disabled
computer.
Offline recovery
A restore operation that is performed from the NetWorker Windows BMR boot image.
A BMR recovery is an offline recovery. You cannot select specific files or save sets to
recover during an offline recovery. You must perform an offline recover to the same
or similar hardware.
Online recovery
A restore operation that is performed from the NetWorker User interface or recover
command. An online recovery requires you to start the computer from an installed
operating system and enables you to recover only specific files or save sets. The
topic Recovering file system data provides more information about online recoveries.
Application data
User data that an application creates, such as log files or a database. For example,
the application data of a SQL server includes databases and log files. You cannot
use Windows BMR to recover the application data. You must back up and recover
application data with NetWorker Module for Microsoft (NMM).
ASR writer
The Volume Shadow Copy Service (VSS) writer that identifies the critical data that
NetWorker must back up to perform an offline recovery.
Boot Configuration Data (BCD)
A data store that contains a description of the boot applications and boot
application settings that start the Windows operating system. To perform an offline
recovery, you must back up this ASR writer component.
Critical volume
One of the following:
350
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
l
l
Any volume that contains files for an installed service. The volume can be
mounted as an NTFS directory. Exchange 2010 is an example of an installed
service, but the Exchange database and log files are not considered critical.
Any parent volume with a mounted critical volume.
NOTICE
NetWorker considers all volumes on all dynamic disks critical if at least one of
the volumes is critical.
A Windows BMR recovery requires a current backup of all critical volumes.
Recovery
The restoration of the operating system and data for a host after a catastrophic
failure, such as a hard disk failure or the corruption of critical operating system
components. The recovery operation might be an offline recovery (Windows BMR) or
an online recovery.
NetWorker Windows BMR image
A bootable image that contains the NetWorker binaries and a wizard to control the
Windows BMR recovery process.
Non-critical volume
A volume that contains user data and does not contain installed applications that
run as a service.
System State data
All the files that belong to VSS writers with a usage type of BootableSystemState or
SystemService. You require these files to perform an offline recovery.
User data
Data that users generate, typically for the purposes of a business function. For
example, a Microsoft Word document or an Excel spreadsheet. Windows BMR does
not back up or recover user data unless the data resides on a critical volume. The
simplest way to back up all user data is to specify the keyword All in the backup save
set of the client resource. You can recover user data online at any time (on demand)
or after a Windows BMR recovery operation.
WinPE
A bootable stripped-down version of the Windows operating system. The NetWorker
Windows BMR image contains a customized WinPE with NetWorker binaries and a
wizard to control the offline recovery process. WinPE does not support writers,
except for the ASR writer. Therefore, VSS writers are not available with a NetWorker
Windows BMR.
Overview of Windows Bare Metal Recovery (BMR)
NetWorker Windows BMR is an automated recovery solution that uses the Windows ASR
writer and other Microsoft VSS writers to identify critical volumes and perform a full
recovery on a target host.
NetWorker Windows BMR supports file system backup and recovery of critical volumes.
NetWorker Module for Microsoft (NMM) supports application data backup and recovery.
Additional backup and recovery procedures are required to backup and restore
application data. The NMM documentation provides specific instructions on how to
backup and recover applications.
Windows Bare Metal Recovery
351
Backing Up Data
You can use Windows BMR to recover a backup from a physical host. You can also use
Windows BMR to recover a VMware virtual machine or VMware CD to a physical host,
VMware virtual machine, or a VMware CD.
NetWorker uses a special save set called DISASTER_RECOVERY:\, a subset of the ALL
save set, to backup all the data that is required to perform a Windows BMR. NetWorker
performs the BMR backup while the Windows operating system is active. You can recover
an offline BMR backup without first reinstalling the Windows operating system. This
action prevents problems that can occur when you restore operating system files to a
running version of Windows.
To support a NetWorker Windows BMR recovery, download the Windows BMR image from
http://support.emc.com. This image enables you to create a bootable Windows BMR ISO
that contains NetWorker binaries and a wizard, which controls the recovery process.
Note
The EMC NetWorker Online Software Compatibility Guide provides more information about
operating systems support for Windows BMR.
Components of the DISASTER_RECOVERY:\ save set
The DISASTER_RECOVERY:\ save set contains a group of component save sets that
are required to perform a Windows BMR recovery. A full backup of the
DISASTER_RECOVERY:\ save set contains the following components:
l
All critical volumes.
l
WINDOWS ROLES AND FEATURES:\ (a subset of the DISASTER RECOVERY:\
and ALL save sets).
l
System Reserved partition.
l
UEFI partition (if available).
NetWorker supports full and incremental backup levels of the DISASTER_RECOVERY:\
save set. Also, when the Windows BMR recovery operation recovers data from an
incremental backup, the recovery operation recovers all incremental backups.
The first time NetWorker performs a backup of the DISASTER_RECOVERY:\ save set,
NetWorker performs a level Full backup, regardless of the level that is defined for the
backup.
When you configure a level Incremental backup of the DISASTER_RECOVERY:\ save
set, NetWorker backs up some components of the save set at a level Full, and other
components at an Incremental level.
The following table summarizes the backup level of each save set component of the
DISASTER_RECOVERY:\ save set, when you perform an incremental backup:
Table 66 DISASTER_RECOVERY:\ components in an incremental backup
Save set
Backup level
Critical volumes
Incremental
WINDOWS ROLES AND FEATURES:\ Incremental
UEFI partitions
Full
System reserved partition
Full
During an incremental backup, the backup operation checks both the modification time
and the archive bit to determine if a file must be backed up. The backup operation
352
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
ignores the archive bit when you assign the nsr_avoid_archive variable a value of Yes on
the client host. As a result, NetWorker only uses the modification time to determine which
files to back up.
Use the environment variable nsr_avoid_archive with caution. If you use the environment
variable nsr_avoid_archive, test the BMR backup image to ensure that you can recover the
Windows system state correctly. Performing a BMR recovery to a physical computer on
page 507 provides more information on validating the BMR backup image.
A Windows BMR recovery requires a successful backup of each component save set in
the DISASTER_RECOVERY:\ save set. If one component of the save set fails, then the
backup operation fails. For a scheduled backup, NetWorker retries the
DISASTER_RECOVERY:\ backup. The number of retries that NetWorker performs is
based on the value that is defined in the client retries attribute of the protection group
that the Client resource is assigned to.
Note
In NMC Administration GUI, the Log tab of the Monitoring window, or the Save Set tab of
the Media window displays each component save set of a DISASTER_RECOVERY:\
backup.
Critical volumes
This topic describes critical volumes and the associated management tools.
NetWorker considers a volume as critical when it contains files for an installed Windows
service. NetWorker also considers the following volumes as critical and will include the
volumes in a DISASTER_RECOVERY:\ backup:
l
A non-critical volume that has a critical volume mounted on it, or a non-critical
volume that serves as a parent to a critical volume.
l
All volumes on a dynamic disk when one of the volumes critical. If one disk in a
dynamic disk pack is critical, then NetWorker must treat all disks in that pack as
critical. This can substantially increase the number of disks that NetWorker includes
in the BMR backup. EMC recommends that you do not install services on a dynamic
disk.
Note
By default, the Windows 2012 System Writer does not report Win32 Service Files as a part
of systems components. As a result, the volumes that contain Win32 Service Files are not
considered critical and the DISASTER_RECOVERY:\ save set will not include a volume that
contains files for an installed service. To configure the Windows 2012 server to report
Win32 Service Files as a part of system components, set the
ReportWin32ServicesNonSystemState registry sub key to 0. Microsoft KB article 2792088
provides more information.
A Windows BMR backup does not back up the following files on a critical volume:
l
Files listed in the FilesNotToBackup registry key
l
Files excluded by system writers
l
Files that an application VSS writer backs up. For example, Exchange databases. Use
NetWorker Module for Microsoft Applications (NMM) to backup these files.
Excluded critical volumes during a Windows BMR backup
A NetWorker Windows BMR backup excludes critical volumes based on the operating
system, disk types, configuration and installation of your computer.
Windows Bare Metal Recovery
353
Backing Up Data
Install applications with third-party services on the system disk, or a disk that already has
other services installed. To identify the disks that contain third-party services, use the
utility, list writers detailed command.
For Windows Server 2008 and 2008 R2, set the ExcludedBinaryPaths registry key to
exclude third-party services from the System Writer. This prevents the disk where the
service is installed from being classified as critical. The Microsoft support document,
System state backup error in Windows Server 2008, in Windows Vista, in Windows 7 and
in Windows Server 2008 R2: “Enumeration of the files failed”, available at http://
support.microsoft.com/kb/980794, describes the use of this registry key.
NetWorker excludes a volume from a backup when one of the following Windows
application service is installed on the host:
l
Storage Spaces volume
l
Cluster volume
l
Cluster Shared Volume
NOTICE
To ensure that you can recover all required files, perform a file system backup of any
excluded disk.
Displaying a list of the critical volumes
To view a list of the critical volumes for a NetWorker client, type the NetWorker command
save -o VSS:LCV=yes from the command line on the client host.
For example:
NetWorker_install_path\bin>save -o VSS:LCV=yes
Output similar to the following appears:
The following volumes are determined as critical by the system
state writers:
C:\ (disk num 0)
i:\mount\ (disk num 7)
The following volumes are critical because they are parents for
one or more mounted critical volumes:
i:\ (disk num 2)
The following volumes are critical because they are in the
same dynamic disk pack with one or more critical volumes:
H:\ (disk num 4,5)
i:\ (disk num 2)
WINDOWS ROLES AND FEATURES save set
The WINDOWS ROLES AND FEATURES save set was introduced in NetWorker 8.1 and
replaces the VSS SYSTEM BOOT, VSS SYSTEM FILESET and VSS SYSTEM
SERVICES save sets. The DISASTER_RECOVERY:\ save set contains the WINDOWS
ROLES AND FEATURES save set as a component save set.
The WINDOWS ROLES AND FEATURES save set contains:
l
Data that are associated with the roles and features that are installed on the
Windows server.
l
Metadata that represents the volume data which the ALL or
DISASTER_RECOVERY:\ save set backs up.
Before backing up the WINDOWS ROLES AND FEATURES save set, consider the
following:
354
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
l
Block Based Backups (BBB) do not support the WINDOWS ROLES AND FEATURES
save set.
l
You cannot restore the WINDOWS ROLES AND FEATURES save set simultaneously
with data from a file system backup. If you must recover data from both the WINDOWS
ROLES AND FEATURES backup and a file system backup, restore the file system
data first, and then restore the WINDOWS ROLES AND FEATURES data.
l
The NetWorker software automatically backs up AD as a component of the WINDOWS
ROLES AND FEATURES save sets. An AD backup or restore includes the AD log
files, database, patch files, and expiry token.
l
You can perform an online recovery of the WINDOWS ROLES AND FEATURES save
set to recover the Active Directory, DFSR, or Windows Server Failover Cluster services.
The topicOnline recovery of Active Directory, DFSR, or Cluster services on page 358
provides more information.
l
If you cancel a deduplication recovery, the state of the recovered data is not reliable
and may contain corrupted data. To ensure that the recovery is correct, restart the
deduplication recovery process.
l
The backup operation will only confirm that the VSS System Writer exists on the
target host. If the backup operation does not detect the writer, the backup of the
DISASTER_RECOVERY:\ or ALL save set fails. The backup operation does not track
and report any other missing VSS writers.
l
You can perform a component level granular restore of the WINDOWS ROLES AND
FEATURES save set with a command line recover or the NetWorker User application.
For example, you can recover the system state and replication folders separately. You
cannot use the NMC Recovery UI to perform a component level restore.
l
Do not restore the WINDOWS ROLES AND FEATURES system state multiple times
in succession without restarting the computer as required. If you do not restart the
computer, you can put the system in an unreliable operational state.
Note
The NetWorker 8.2 and later clients can only recover WINDOWS ROLES AND FEATURES
save sets. If you try to recover a VSS System State save set that was created with a
NetWorker 8.0 SP1 client or earlier, then the Windows host will not function correctly. To
recover VSS system state save sets that are created with a NetWorker 8.0 SP1 or earlier
backup, use the NetWorker 8.0 SP1 or earlier client to create a backup. EMC recommends
that you restore the WINDOWS ROLES AND FEATURES save set from a NetWorker 8.1
or later backup.
The DISASTER_RECOVERY:\ save set
The DISASTER_RECOVERY:\ save set is available for Windows clients.
The DISASTER_RECOVERY:\ save set backs up critical volumes, UEFI, the system
reserved partition, and WINDOWS ROLES AND FEATURES.
The DISASTER_RECOVERY:\ save set does not include data for clusters, Active
Directory, DFS-R, and Windows Server Failover Cluster.
Checkpoint restart is not supported for backups of the DISASTER_RECOVERY:\ save
set. If you enable checkpoint restart for a client with the DISASTER_RECOVERY:\ save
set, then the setting is quietly ignored for the DISASTER_RECOVERY:\ save set. The
save set is marked with a cb flag instead of a k flag, indicating that the checkpoint is not
considered for DISASTER_RECOVERY:\.
Windows Bare Metal Recovery
355
Backing Up Data
The DISASTER_RECOVERY:\ save set is also in the ALL save set.
UEFI Partition Support
NetWorker supports a backup and recovery of unmounted Unified Extensible Firmware
Interface () partitions on hosts that use a supported . The EMC NetWorker Online Software
Compatibility Guide provides more information about support operating systems.
The topic Performing a Windows BMR recovery to a physical computer on page 504
describes how to perform a Windows BMR of a computer that has UEFI partitions.
The following list summarizes the properties of a UEFI partition backup:
l
NetWorker can backup an unmounted partition.
l
NetWorker uses the following path pattern to backup the UEFI partitions:
\\<root>\Device\HarddiskVolume#
where # is the number of the volume.
l
The DISASTER_RECOVERY \: save set contains a backup of the UEFI partitions.
l
NetWorker always performs a level Full backup of UEFI partitions, regardless of the
backup level of the DISASTER_RECOVERY \: save set.
l
NetWorker does not index the UEFI partitions or make the UEFI partitions available for
online recoveries.
After a successful BMR restore, a host that uses UEFI might fail to start. This can occur
when the UEFI boot manager does not have a valid Boot Order entry, for example, when
you delete the Boot Order entry or restore the Windows BMR backup to different
hardware. In these situations, the operating system recreates the Boot Order entry during
a restart operation but may not use the same path.
To resolve this issue, load Boot Manager and select Boot from the File menu to correct
the Boot Order entry.
Boot Configuration Data
In earlier versions of the Windows operating system, the BOOT directory was present in
the system drive. In Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2,
Windows Server 2012, and Windows Server 2012 R2, a hidden, unmounted systemreserved partition can be present, and the Boot Configuration Data (BCD) store is on this
partition. The BCD store contains the boot configuration parameters and controls the
computer boot environment.
The NetWorker Windows client backs up the system reserved partition and the BCD store
only for Windows offline Bare Metal Recovery (BMR). During a Windows offline BMR
backup, NetWorker checks the type of operating system. If it is Windows 7, Windows 8,
Windows 8.1, Windows Server 2008 R2, Windows Server 2012 or Windows Server 2012
R2, NetWorker assigns a GUID to the partition and performs the backup of the BCD. The
BCD partition does not need to be mounted for the backup to occur. If the BCD partition is
not mounted, the backup is not indexed. The save set name is GLOBALROOT/xxxxxx/.
The BCD can only be restored as part of offline BMR. Online recovery of the BCD is not
available. Consult Microsoft documentation for using the BCDEdit tool to save copies of
BCD before making Boot Configuration Data changes.
Windows Server 2012 Cluster Shared Volumes (CSV)
NetWorker does not support Windows Server 2012 Cluster Shared Volumes () as a critical
volume. If a CSV disk is marked as a NetWorker critical disk, then the Windows BMR
backup reports a warning, and continues to perform the backup operation as if the CSV is
not on the critical list. NetWorker does not backup the CSV because a CSV cannot reside
in the same shadow copy set with a local volumes.
356
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Applications such as SQL Server and Hyper-V in a Windows Continuous Availability
scenario using CSV are not supported.
The EMC NetWorker Cluster Integration Guide provides more details.
Windows Server 2012 Storage Spaces
NetWorker Windows BMR does not support the backup and recovery of critical System
State data that are on virtual disks. A NetWorker BMR backup skips all critical volume
data that are on Storage Spaces and does not add the volume to the BMR critical volume
list.
A BMR recovery cannot recover critical volume data on Storage Spaces. If the Storage
Pool disks that compose a Storage Spaces virtual disk are not damaged, a recovery
operation to the original computer will mount the Storage Pool virtual disks after the
critical volume recovery operation completes.
NOTICE
EMC recommends that you detach the physical disks that Storage Spaces use when you
recover critical volumes, and then reattach the physical disks after recovery. A Window
BMR recovery operation can overwrite data on attached Storage Spaces disks.
The topic Windows Storage Pools considerations on page 366 describes how to perform
a Windows BMR recovery of Storage Spaces to a new computer.
NOTICE
To backup and recover data on virtual hard disks and volumes created by Storage
Spaces, use NetWorker file system backup and recovery operations.
A Windows BMR backup of a Windows 2012 host creates a file that is named
OSSR_sysinfo.xml. The file is located at [root]\EMC NetWorker\nsr\tmp. This
file captures pertinent information about the configuration of the backed up host. For
example:
l
Host information (name, boot drive, BIOS or EFI).
l
NIC cards and their parameters.
l
Disk information.
l
Storage Spaces information.
The purpose of this file is to support the manual recreation of the Storage Spaces
configuration following a BMR recovery.
Synthetic full backups
A synthetic full backup uses the most recent full and incremental backups to create a full
backup without transferring any data from the client. NetWorker performs all the work to
synthesize a full backup on the NetWorker server. A synthetic full backup gives you the
benefits of a full backup, such as a faster restore, without having to perform a full
backup.
The topic Synthetic full backups on page 298 describes the synthetic full backup feature.
When a client backup includes the DISASTER_RECOVERY:\ save set, NetWorker will
always backup volumes that are identified as critical, at a level full. NetWorker will not
create a synthetic full backup for critical volumes. The DISASTER_RECOVERY:\ save
set is included during full backups when either the ALL or DISASTER_RECOVERY:\
save set is specified in the NetWorker Client resource.
Windows Bare Metal Recovery
357
Backing Up Data
Example 6 Synthetic full backups with save set ALL
The save set attribute of the Client resource contains the ALL save set and the backup
schedule includes a synthetic full backup on Sundays. The NetWorker client host has four
volumes: two are critical, and two are non-critical.
l
C:\ and E:\ are critical volumes.
l
F:\ and G:\ are non-critical volumes.
On Sundays, NetWorker performs a backup of the following save sets:
l
C:\ — At a true level full backup level.
l
E:\ — At a true level full backup level.
l
F:\ — At a synthetic full backup level.
l
G:\ — At a synthetic full backup level.
l
DISASTER_RECOVERY:\— At a true level full backup level.
Example 7 Synthetic full backups with file system save sets
The save set attribute of the Client resource contains a list of all volumes and the backup
schedule includes a synthetic full backup on Sundays. The save set attribute does not
contain the DISASTER_RECOVERY:\ save set. The NetWorker client host has four
volumes: two are critical, and two are non-critical.
l
C:\ and E:\ are critical volumes.
l
F:\ and G:\ are non-critical volumes.
On Sundays, NetWorker performs a backup of the following save sets:
l
C:\ — At a synthetic full backup level.
l
E:\ — At a synthetic full backup level.
l
F:\ — At a synthetic full backup level.
l
G:\ — At a synthetic full backup level.
Online recovery of Active Directory, DFSR, or Cluster services
The DISASTER RECOVERY:\ save set includes the WINDOWS ROLES AND
FEATURES component save set. You can recover the WINDOWS ROLES AND
FEATURES backup in an online recovery operation, to a host that uses the same
Windows operating system instance. NetWorker 8.2 and higher support the online
recovery of the following Windows services, which the WINDOWS ROLES AND
FEATURES component contains:
Active Directory
SolVe Desktop provides procedures that describe how to recover this service.
358
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Distributed File System Replication (DFSR)
The topic, Backing Up and Restoring a Microsoft DFS, provides more information.
Cluster
SolVe Desktop provides procedures that describe how to recover this service.
NetWorker does not support the online recovery of any other Windows service that the
WINDOWS ROLES AND FEATURES save set contains. Unsupported online recovery of
WINDOWS ROLES AND FEATURES components results in an inconsistent state of the
Windows server.
NOTICE
When you perform an online recovery, you cannot mark the WINDOWS ROLES AND
FEATURES save set and use the Required Volumes option. To determine the volume that
contains the WINDOWS ROLES AND FEATURES save set that you want to restore, mark
the DISASTER RECOVERY:\ save set, then use the Required Volumes option. After you
determine the required volumes, unmark the DISASTER RECOVERY:\ save set and
mark the WINDOWS ROLES AND FEATURES save set.
Windows BMR Planning
This section provides guidelines on how to plan your Windows BMR backups.
Requirements for Windows BMR backup and restore
The BMR recovery process restores the operating system that was installed on the source
host. If you perform a BMR recovery to a different host with different hardware, after the
recovery operation and restart completes, Windows prompts you to install the required
drivers.
Before you perform a BMR recovery to a different host, ensure that you meet the following
requirements:
l
The source and target hosts use the same processor architecture.
l
The hardware on the target host is operational.
l
The target host has a minimum of 512 MB of RAM.
l
The target host startup hard disk capacity must be larger or the same size as on the
source host, regardless of the amount of space actually in use. If the disk is smaller
by a single byte, BMR fails.
Note
Verify whether the source critical volumes are part of a larger physical disk. If critical
volumes are on a larger physical disk, all target critical volumes must be large enough
to accommodate the entire underlying physical disk. Use the Windows Disk
Management utility to verify disk configuration and size.
l
The number of disks on the target host is greater than or equal to the number of disks
there were on the source host. The disk LUN numbering on the target host must
match the disk LUN numbering on the source host.
l
The RAID configuration on the target host should match the disk order of the hard
disks.
l
The disk or RAID drivers that are used on the source system are compatible with the
disk or RAID controllers in the target system. The recovery process restores the
Windows Bare Metal Recovery
359
Backing Up Data
backup to the same logical disk number that was used by the source host. You
cannot restore the operating system to another hard disk.
l
Windows BMR supports IDE, SATA, or SCSI hard disks. You can make the backup on
one type of hard disk and recover on another type of hard disk. For example, SAS to
SATA is supported.
l
The target system can access the Windows BMR image as a bootable CD/DVD volume
or from a network start location.
l
The target system has the NIC or storage device drivers installed that match the NIC.
Note
All NIC or storage device drivers must not require a restart to complete the driver
installation process. If the drivers require a restart, then the BMR recovery process
fails and prompts you to install the drivers again.
Save set configuration by host type
This section describes the attributes of save sets that are used by Windows BMR. This
information helps you select the correct save set configuration for the computer and
operating system.
The following table lists the save sets to back up, depending on the Windows host to be
protected.
Table 67 Save set configuration for a specific host
To back up this
host
A host or file server
that is not a
Microsoft Application
server
A host that is a
Microsoft Application
server. For example,
a Microsoft Exchange
Server, Microsoft SQL
Server, Hyper-V, or
Microsoft SharePoint
Server
360
EMC NetWorker 9.0.x Administration Guide
Specify these save sets in the
client resource Save Set
attribute
Considerations
l
Specify the save set All in the
NetWorker Client resource.
l
WINDOWS ROLES AND
FEATURES must be backed up.
l
By default, the save set All
includes the DISASTER
RECOVERY:\ save set and all
of the local physical drives.
l
WINDOWS ROLES AND
FEATURES save sets are
recovered in a Windows BMR
operation and are also available
for online recovery. WINDOWS
ROLES AND FEATURES save
sets should only be recovered
online as part of an Active
Directory, DFSR, or Windows
Server Failover Cluster online
recovery.
l
Specify the ALL save set in
the Save set attribute in the
NetWorker Client resource.
l
l
Use NMM to back up the
application databases. The
NMM provides details.
Use the Windows BMR Wizard to
recover the data contained in the
DISASTER RECOVERY:\ save
set.
l
Use NMM to recover the
application databases.
Backing Up Data
Best Practices for Windows BMR
The following sections outline best practices for Windows BMR.
Perform regular backups
Perform a full backup that contains the DISASTER_RECOVERY:\ save set regularly and
after any you install, remove or update any system components. For example, when you
add, change, or remove Windows roles and features, or install Windows updates and
service packs.
NetWorker will automatically back up the DISASTER_RECOVERY:\ save set when you
specify the ALL save set in the Save Set attribute of the NetWorker Client resource.
Capture disk configuration changes for Windows BMR
The NetWorker BMR recovery operation uses the Microsoft ASR writer to reconstruct a
disk configuration. The ASR writer is sensitive to the disk numbers and disk configuration
of the original host. NetWorker saves this disk information during a Windows BMR
backup and uses the disk configuration information to perform the recovery. After you
reconfigure any disk on a host, reboot the host and then perform a Windows BMR backup
to ensure that NetWorker captures the new disk configuration. Examples of a disk
reconfiguration include the addition or removal of a disk or partition.
Mixing critical and non-critical volumes on a physical disk
Windows allows you to partition a physical disk into multiple volumes. These volumes
can be either critical or non-critical, depending on the type of data that they contain.
During a Windows BMR recovery operation, the ASR writer can re-create and format a
partition, including non-critical partitions. If the ASR writer formats a non-critical
partition, the use of an online recovery is required to recover data on the non-critical
partitions. Recovering the Data describes how to perform an online recovery.
NOTICE
Do not mix critical and non-critical volumes on the same physical disk.
Considerations for NetWorker user defined directives
Use user defined directives, such as nsr.dir, with caution. When you use directives in
directories where system state and installed services data resides, the backup creates an
incomplete BMR backup image and potentially render the BMR backup image unusable.
If you create user defined directives, test the BMR backup image to ensure that you can
successfully perform a BMR Recovery. Performing a Windows BMR recovery to a physical
computer on page 507 provides more information about testing the BMR backup image.
Critical volume recommendations
Use the following practices to minimize the size of Windows BMR backups.
l
Do not store non-critical data, such as MPEG files, on critical volumes.
l
Consolidate critical volumes. For example, install services on the same disk.
l
Do not mount critical volumes on a non-critical volume.
Windows BMR limitations and considerations
Review the following Windows BMR limitations and special considerations before you
perform Windows BMR backup, clone and recovery operations.
Windows Bare Metal Recovery
361
Backing Up Data
Disk configuration limitations
This sections describes disk configuration limitations in Windows BMR.
Dynamic disks
A BMR recovery does not bring dynamic disk volumes online. After the BMR recovery
completes, use Windows Disk Manager to bring the dynamic disks back online.
NTFS and ReFS
Only NTFS and ReFS file systems are recognized as critical volumes
Although the backup of the DISASTER_RECOVERY:\ save set fails, NetWorker will
backup, the contents of the partition and the data is available for an online recovery only.
To ensure a successful backup of the DISASTER_RECOVERY:\ save set, install all
services or application on an NTFS or ReFS volume.
Critical volumes
Windows BMR only supports critical volumes on NTFS and ReFS partitions. This is a
Microsoft ASR limitation. If a critical volume is on a partition other than NTFS or ReFS, the
backup of the DISASTER_RECOVERY:\ save set fails. A message similar to the
following appears in the savegrp.log file:
Disaster Recovery: critical volume volumename identified for disaster
recovery backup has a non-NTFS file system, filesystemname. Backups
of non-NTFS critical volumes are not supported.
Note
Windows BMR does not support FAT and FAT32 file systems as critical volumes.
HP ProLiant system considerations
You cannot recover from a Windows BMR backup on an HP ProLiant system when the HP i
Provisioning Tool (IPT) 1.4 or 1.5 was used to configure an entire disk as a critical volume,
such as the system partition.
To resolve this issue, shrink the logical volume before you perform the Windows BMR
restore. The HP website contains a customer advisory that describes the issue and the
impact to Windows Bare Metal Recovery with Windows Server Backup. This advisory and
the resolution also applies to NetWorker Windows BMR critical volumes.
Note
EMC recommends that you test your BMR solution before a disaster recovery is required.
Optimized deduplication backup considerations
Review this section before you configure backups that use optimized deduplication.
l
l
l
l
l
l
362
You can recover a complete volume backup recovery to the original volume only if the
backup was performed at a level Full.
You cannot recover specific files from a level FULL or INCREMENTAL save set.
You cannot perform a full volume recovery of a non-full level save set.
You cannot recover data from an optimized and unoptimized deduplication backup
when VSS is disabled. The backups that NetWorker created are corrupt.
You cannot cancel the recovery of an optimized deduplication backup to a
deduplication volume. If the recovery process is interrupted or fails, the destination
volume becomes unusable. You must repeat the recovery process and the recovery
operation must complete successfully to prevent volume corruption.
If the optimized deduplication recovery cannot successfully complete, you can
perform a selected files restore of directories from the optimized deduplication
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
backup. This restores the directories' files to a rehydrated state, but will take
significantly more time.
Save set considerations
This topic describes limitations and considerations that relate to save sets.
Checkpoint restart backup for Windows DISASTER_RECOVERY:\ save set is not supported
The NetWorker software does not support a checkpoint restart backup for the Windows
DISASTER_RECOVERY:\ save set. When you enable the Checkpoint restart option for a
Client resource that you configure to back up the DISASTER_RECOVERY:\ save set, the
backup fails.
Including DISASTER_RECOVERY:\ in multiple save sets
When you use specify multiple save sets with the save command, you must use the -N
option to specify the symbolic name of DISASTER_RECOVERY:\ save set, and specify
the DISASTER_RECOVERY:\ as the last save set in the save set list.
For example:
save.exe -s server -N "DISASTER_RECOVERY:\\" save_set1 save_set2 ...
"DISASTER_RECOVERY:\\"
where:
save_set1 or save_set2 are unique save set names, such as a drive letter (f:\) or mount
point (n:\mountpoint).
Monitoring save operations
When you monitor Windows BMR save operations, for example, by using the NetWorker
Administration > Monitoring > Sessions window, you might notice that the number of
save sessions differ from the number of save sets that appear in the Save set attribute of
the Client resource. This is because NetWorker optimizes Windows BMR backups to
generate the correct number of Windows BMR backup sessions and save sets.
Cloning considerations
To clone a Windows BMR backup, ensure that you clone all of the critical volumes,
DISASTER_RECOVERY:\, and WINDOWS ROLES AND FEATURES save sets that were
created during the backup operation. While you can clone individual save sets, you
cannot perform a successful BMR recovery unless you recover each save set that the
backup operation created.
To ensure that you clone all of the BMR save sets, review the following information before
you start a clone operation:
l
When you use the automatic clone, you enable the Clone attribute on the group
resource that contains the BMR client. The automatic clone operation will clone all of
the required save sets after the scheduled backup operation completes.
Note
Synchronize the NetWorker server and client host clocks before the backup operation
to ensure that all of the save sets are cloned.
l
When you use the nsrclone command to perform a manual clone, ensure that you
include the ssid/cloneid for each save set. Use the mminfo or nsrinfo -v
command to report all save set back ups that occurred for the Windows client during
the save session. The Command Reference Guide provides detailed information about
using the mminfo and nsrinfo commands.
l
When you use the schedule clone function, do not filter on other attributes such as
save set name. Filter only by client name. When you enable automatic cloning for a
Windows Bare Metal Recovery
363
Backing Up Data
backup group that contains the DISASTER_RECOVERY:\ save set, synchronize the
clocks on the NetWorker server and client host clocks across the network to ensure
that NetWorker clones all save sets.
Security considerations
This section describes security issues related to planning Windows BMR backup and
recovery .
Server role considerations
This section describes considerations for Windows Server Roles in Windows BMR.
Protecting Windows server roles
Several server role components of Windows host store the data in a database. Examples
of Windows server roles with databases include:
l
Active Directory Rights Management Services (ADRMS).
l
Windows System Resource Manager (WSRM).
l
Universal Description, Discovery, and Integrations (UDDI) Services.
l
Windows Server Update Services (WSUS).
When you install the Windows server role on a host, the installation process prompts you
to store data on either an existing SQL Server installation or in a Windows Internal
Database (WID).
NetWorker uses the VSS SQL Server writer to back up the role databases that are stored
in WID but does not protect role databases, which the server role component stores in a
SQL Server. Use NMM or a third-party SQL backup product to backup and recovery the
roles databases.
Backup and recovery workflows for server roles that use WID
These are the backup and recovery workflows are as follows:
l
Perform a NetWorker Windows BMR backup, which includes all the SQL writer
components for WID. If required, backup user data on the client.
l
Perform a NetWorker Windows BMR recovery operation, which recovers all the WID
components.
After the NetWorker Windows BMR system restart, the WID service is available and
Windows server roles have access to their databases.
Saving and recovering SQL Server components with Windows BMR and NMM:
1. Perform a NetWorker Windows BMR backup. If required, backup user data on the SQL
client.
2. Use NMM or a third-party backup application to back up the SQL Server application.
3. Perform a NetWorker Windows BMR recovery operation.
After the recovery and restart operations complete, you cannot start the SQL Server
service. Also, any server roles that store data in SQL databases outside WID will not
work.
4. For non-clustered SQL servers only, ensure that the SQL group is offline.
5. Run the following setup.exe command from a command prompt with elevated
privileges, to rebuild the SQL Server:
C:\> setup /QUIET /ACTION=REBUILDDATABASE /
INSTANCENAME=Instance_name /SQLSYSADMINACCOUNTS=domain_name
\administrator
364
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Note
The SQL Server installation media contains the Setup tool.
6. Bring the SQL server services online.
7. Use NMM or a third-party backup application to recover the SQL system databases
(master, model, msdb).
8. Use NMM or a third-party backup application to recover the role databases.
9. Restart the services that require the role databases that you recovered.
NOTICE
The EMC NetWorkerModule for Microsoft Applications Application Guide provides more
information about using NMM to recover SQL databases.
Microsoft server application considerations
Use both the NMM and the NetWorker software to protect Microsoft server applications,
such as Microsoft Exchange Server, Microsoft SQL Server, Hyper-V, and Microsoft
SharePoint. The NMM software protects the application data, such as databases and log
files and the NetWorker client software protects the user data and critical disks on the
host, for the purposes of Windows BMR.
Below is a high level overview of NetWorker and NMM backup and recovery workflow for
Microsoft server applications:
1. Use NetWorker to back up critical and non-critical disks as part of a regular file
system backup.
2. Use NMM to back up application data, such as Microsoft SQL Server.
3. Use NetWorker to perform a Windows BMR backup of the critical volumes on the host.
4. Use the Windows BMR boot image to perform a BMR recovery.
5. Use the NetWorker User application to recover any non-critical disks.
6. Use NMM to recover the application data.
The EMC NetWorker Module documentation provides more information about recovering
application data.
Online recovery of Windows services considerations
This section describes limitations and considerations that are related to Windows
services.
Active Directory considerations
A Windows BMR recovery of a Domain Controller is non-authoritative by default. If you
must perform an authoritative recovery, then you must start into DSRM mode directly
from the Windows BMR wizard. The topic Performing post-recovery tasks for Active
Directory services, provides more information.
DFSR considerations
DFSR namespaces are junction mount points. The DISASTER _RECOVERY:\ and ALL
save sets do not backup DFSR namespaces, even if the DFSR shares reside on a critical
volume. To backup DFSR Shares, either use the new save set ALL-DFSR or provide the
full DFSR Share path as the save set name. The ALL-DFSR save set applies to all
supported platforms. Unlike the ALL save set, which skips the DFSR namespace because
it is a junction point, the ALL-DFSR save set backs up every namespace, along with the
associated replication folders.
The topic Recovering Windows volume mount points, provides more information about
recovering volume mount points.
Windows Bare Metal Recovery
365
Backing Up Data
MSCS considerations
Review these considerations before you perform a Windows BMR recovery on a clustered
host.
l
Before you start the Windows BMR recovery operation, ensure that you detach the
shared disks. After the Windows BMR recovery operation and the restart completes,
attach the shared disks before you perform the online recovery.
l
After an authoritative restore completes, the recovery operation does not bring the
cluster services online on the remote nodes. You must bring the services online
manually.
Windows Storage Pools considerations
When a system failure occurs which damages Storage Pools, perform the following steps
as recommended by Microsoft to perform a BMR recovery to a new host. In the case of a
complete system failure, a Storage Pool may not exist on the target host. There can only
be physical disks. Some of these disks are required to create Storage Pools.
Before beginning Windows BMR wizard, physically remove from the target recovery
computer any physical disks reserved for storage pools. This manual step is required
because the Windows BMR wizard does not have any option to exclude the disks.
To recover Storage Spaces to a new host, perform the following steps:
1. Boot the host with the Windows BMR image.
2. Recover only the critical volumes.
3. Reboot the host.
4. Attach physical disks that are reserved for Storage Pools.
5. Use Windows Server Manager or Powershell Cmdlets to configure the Storage Pools.
6. Perform a volume or file recovery of the Storage Spaces volumes.
7. Perform a volume or file recovery of other volumes on physical disks.
WinPE considerations for SAN boot devices
When you recover to a host that uses a SAN boot device, the WinPE environment requires
that you temporarily diable all but one path to the boot device. After the BMR recovery
and reboot completes you can re-enable the remaining paths.
VMware network interface card driver limitations
The Windows BMR image does not contain a driver for any of the VMware VMXNET,
VMXNET3, or the VMware Paravirtual SCSI NIC models. The Windows BMR image does
contain a driver for the e1000 NIC. When you perform a Windows BMR recovery, ensure
that the VM has at least one configured e1000 NIC, or add custom NIC drivers when you
run the NetWorker BMR wizard.
Tthe VMware Tools installation media in the \Program Files\VMware\VMware
Tools\Drivers folder on the system drive of the VM contains the VMware NIC drivers.
BCD partition limitations
NetWorker requires that the BCD partitions are online during a Windows BMR backup. If a
BCD partition is offline during a Windows BMR backup, the backup fails with an
messages similar to the following:
save: Unable to get volume information of file system.The device is
not ready. (Win32 error 0x15) with the volume offline
366
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Creating a Client resource with the Client Backup Configuration wizard
The Client Backup Configuration wizard enables you to quickly configure a client resource
with a limited set of key backup options. Follow these steps to configure a file system
backup and a BMR backup for a Windows host.
Before you begin
l
Install the NetWorker client software on the client computer.
l
Ensure that the NetWorker server host is listed in the servers file on the client
computer.
l
Ensure that the communication between the NMC server, NetWorker client, and
NetWorker server uses nsrauth strong authentication.
l
Ensure that the user who runs the wizard meets the following requirements:
l
n
Root (UNIX) or Administrator (Windows) privileges.
n
A member of a User Group on the NetWorker server that has Configure NetWorker
privileges.
Ensure that multiple wizard hosts are not trying to access the same client computer
simultaneously.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Clients, and then select New Client Wizard.
The Client Backup Configuration wizard appears, starting on the Specify the Client
Name page.
3. In the Client Name box, type the hostname of the client computer.
It is recommended that you specify the fully qualified domain name (FQDN) of the
host. For OS cluster hosts, type the FDQN of the virtual host.
For application cluster hosts, type the FQDN of the application cluster host. For
example:
l
For an Oracle cluster, type the RAC hostname.
l
For an Exchange IP DAG, type the DAG name.
The application module administrator guides provide more information.
Note
If the Client Configuration wizard cannot resolve the specified hostname, an error
message appears after you click Next.
4. Optionally, in the Comment box, type a description of the client.
If you are creating multiple client resources for the same NetWorker client host, then
use this attribute to differentiate the purpose of each resource.
5. In the Tag box, type one or more tags to identify this Client resource for the creation of
dynamic client groups for data protection policies.
Place each entry on a separate line.
6. In the Type box, select Traditional NetWorker client.
Creating a Client resource with the Client Backup Configuration wizard
367
Backing Up Data
7. Optionally, from the Group list, select a group for the Client resource.
The group to which the client belongs determines the workflow that is used to back up
the client.
Note
You can also assign the client to one or more groups after you create the Client
resource.
8. Click Next.
9. On the Specify the Backup Configuration Type window, select Filesystem, and then
click Next.
10. On the Select the NetWorker Client Properties window, configure the following
options:
Option
Description
Priority
Enables you to control the order in which the NetWorker server
contacts clients for backup. During a backup operation, the
NetWorker server contacts the client with the lowest priority value
first. If you do not specify a priority for the client resources, then the
backup order is random. The default value is 500.
While the Priority attribute specifies the order of client contact, many
variables affect the order in which clients complete their backups.
For example:
l
The backup operation on a client does not begin until the
worklists for each of the save sets on the client are complete.
l
The amount of work can vary greatly from one client to the next.
l
If a client stops responding and times out, then the backup
operation puts the client backup at the end of the backup order
list.
The only way to guarantee that the backup of one client occurs
before the backup of another client is to configure the workflows for
the clients to start at different times.
Parallelism
Specifies the maximum number of data streams that a client can
send simultaneously during a backup action.
Data streams include back data streams, savefs processes, and
probe jobs.
The default value is different for the NetWorker server than it is for all
other client resources:
l
For the NetWorker server client resource, the default value is 12.
This higher default value enables the server to complete a larger
number of index backups during a Server backup action.
l
For all other clients, the default value is 4.
To avoid disk contention for clients other than the NetWorker server,
specify a value that is the same as or fewer than the number of
physical disks on the client that are included in the backup.
368
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Option
Description
The EMC NetWorker Performance Optimization Planning Guide provides
more information about recommended client parallelism values and
performance benefits.
Remote
Access
Specifies a list of the users that have access to perform remote
access operations. For example, users that can perform a directed
recovery of backup data that originated on this host.
Data Domain
Interface
Specifies the protocol to use if you send the backup data to a Data
Domain Device. Available selections are IP, Fibre Channel, or Both.
Note
Mac OS X clients only support the IP protocol.
Block Based Enables Block Based Backups for the host. When you select this
Backup (BBB) option, you must also select the Client Direct.
This option applies to Linux only.
Note
The Block Based Backup chapter provides complete information
about how to configure a host for BBB backups.
Client Direct
Allows the client to try to directly connect to the backup storage
device, instead of connecting to a NetWorker storage node. If a direct
connection is not possible, then the backup operation connects to
the NetWorker storage node that you configure to accept data from
the client.
Parallel Save
Streams
(PSS)
Enables NetWorker to use multiple parallel save streams to backup
each save set defined for the client, to one or more destination
devices. PSS does not support Checkpoint Restart backups.
11. Click Next.
12. On the Select the File System Objects window, select the file system objects to
backup.
Note
To avoid the over consumption of memory, NetWorker limits the number of files that
you can view when you browse a directory that contain a large number of files, for
example, 200,000 files. When NetWorker determines that displaying the number of
files will exhaust memory resources, NetWorker will display a partial list of the files
and a message similar to the following appears: Expanding this directory
has stopped because the result has too many entries
CIFS, DFS, and msdos file systems do not appear as selectable file system objects.
Modifying_the save_sets defined for a Windows client on page 372 describes how to
modify the save set attribute to define backup a remote file system.
Creating a Client resource with the Client Backup Configuration wizard
369
Backing Up Data
Note
When you select all file system objects and the DISASTER_RECOVERY:\ save set,
the ALL value appears in the Save set attribute for the client resource. When you
select file system objects, enables you to perform granular recoveries of files and
directories. The DISASTER_RECOVERY:\ save set enables you to perform a BMR
restore of the Windows host. To backup Active Directory, DFSR, or Cluster Services,
ensure that you perform DISASTER_RECOVERY:\ backup.
13. On the Backup Configuration Summary window, click Create.
14. On the Client Configuration Results window, review the results of the client
configuration process, then click Finish.
Results
The Client resource appears in the Clients window pane.
Verifying a valid Windows BMR backup
After you perform a Windows BMR backup, verify that the backup exists. NetWorker
creates one save set for each critical volume backed up by the DISASTER_RECOVERY:\
save set.
You can verify that the backup exists by using the NMC console, the NetWorker User
program, or the nsrinfo program.
NOTICE
If any of the componets of the Windows BMR backup fail, then NetWorker does not create
a DISASTER_RECOVERY:\ save set and you cannot perform an offline recovery. The
backup process may backup the WINDOWS ROLES AND FEATURES save sets or critical
volumes, which NetWorker makes available for an online recovery.
Verifying that a valid backup exists by using the NMC console
Procedure
1. Use NMC to connect to the NetWorker server.
2. In the NetWorker Administration window, click Media.
3. In the left pane, click Save Sets.
4. On the right pane, on the Query Save Set tab, specify the search criteria such as the
NetWorker Client Name and a date range for the Save Time.
5. Select the Save Set List tab in the right pane to generate and display a list of save sets
that meet the search criteria.
Verifying that a valid DISASTER_RECOVERY:\ save set exists by using the
NetWorker User Program
By default, the Recovery window displays the most recent backup. To verify an older
backup select the View > Change Browse Time menu optionand specify a different backup
date and time.
Procedure
1. Start the NetWorker User program by using the winworkr command with the -s option
to connect to the NetWorker server to which the source client data is backed up:
winworkr -s server_name
370
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
If the -s option is not entered and there is only one server detected, that server is
connected automatically. If there are no servers detected, or if there is more than one
server available, the Change Server dialog box appears, enabling you to choose the
server.
2. Click Recover to open the Source Client dialog box.
3. Select the source client whose DISASTER_RECOVERY:\ save set, then click OK.
4. Select a destination client, then click OK.
5. In the Recover window, browse and locate the save set named DISASTER_RECOVERY:
\.
Verifying that a valid DISASTER_RECOVERY:\ save set exists by using the
nsrinfo program
Perform the following steps from a command prompt to query the client file index of the
Windows host to display information about the DISASTER_RECOVERY save set.
Type the following command at the command prompt:
nsrinfo -v -s server_name -N "DISASTER_RECOVERY:\\" client_name
where:
l
server_name is the name of the NetWorker server.
l
client_name is the name of the client that performed the Windows BMR backup.
Performing a NetWorker Bare Metal Recovery wizard test
Before you need to perform a Windows BMR, test the wizard to ensure that you can
complete a recovery and that you have the required drivers. This task is especially
important for 64-bit hosts that might require additional drivers. For both 64-bit and 32-bit
hosts, the wizard must use drivers that do not require a reboot.
NOTICE
After you test the wizard, you can safely exit the wizard before completing the entire
recovery process.
Procedure
1. Follow the procedures in Performing a Windows BMR to physical or virtual
computers on page 504.
Verify the following as you step through the BMR recovery wizard screens:
l
If DNS is not available, that the host can resolve the NetWorker server name by
some method, such as a local hosts file.
l
You can see the network interface that is required to communicate with the
NetWorker server. If you cannot see the network interface, use the wizard to load
the required NIC driver.
l
You can see the critical and non-critical disks for the host that is to be recovered. If
you cannot see all of the disks, use the wizard to load the required disk drivers.
2. Click Exit to safely exit the wizard.
3. Exit the command window.
Creating a Client resource with the Client Backup Configuration wizard
371
Backing Up Data
The system automatically reboots.
Modifying the save sets defined for a Windows client
You can modify an existing client to change the file system objects to backup on the
client.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
4. On the General tab, in the Save set attribute, specify the file system, directory or path
to a file. Specify one file system object on each line. You can also modify specify a
special ALL save set to backup a specific type of file system only. The following table
summarizes the available ALL save sets.
Table 68 Special ALL save sets
Special ALL save set
syntax
Backup behavior
all-file_system
Only back up locally mounted file systems of a particular type, where
file_system is the name of the file system, for example ntfs. The EMC
NetWorker Online Software Compatibility Guide provides a list of the
supported file system for each operating system.
all-mounts
On Windows clients, the all-mounts save set is equivalent to the
ALL save set. File systems that are normally skipped are still skipped.
Mapped drives
To back up mapped or CIFS drives on a Windows client for either a scheduled or a manual
backup, you must perform additional configuration steps in the Client resource.
Before you begin
l
Create a dedicated client resource for the backups of mapped drives. A common user
account must have access to each mapped drive.
l
Create a separate Client resource for backups of local drives.
l
Ensure that the Administration window is in Diagnostic Mode. To enable Diagnostic
Mode, from the View menu, select Diagnostic Mode.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
4. On the General tab, in the Save set attribute, specify the Universal Naming
Convention (UNC) path of the drive.
372
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Do not specify the drive letter. For example, to specify the accounts directory on the
jupiter server, type \\jupiter\accounts.
5. On the Apps & Modules tab, configure the following attributes:
a. In the Remote user and Password fields, specify a username and the associated
password for an account that has access to the UNC path.
b. In the Backup command box, type save -xL.
c. In the Save operations box, type VSS:*=off
Mapped drives
Backups of mapped drives on a Windows client for either a scheduled or a manual
backup require additional configuration of the Client resource.
Create a dedicated client resource for backups of mapped drives that you access with the
same username and password, and a separate Client resource for backups of local
drives.
On the General tab of the Client Properties dialog box for the Client resource that you use
to back up mapped drives, specify the Universal Naming Convention (UNC) path of the
drive in the Save set attribute. Do not specify the drive letter. For example, to specify the
accounts directory on the jupiter server, type \\jupiter\accounts.
On the Apps & Modules tab of the Client Properties dialog box for the Client resource,
specify the following settings:
l
Type the username and password for the account to access the UNC path in the
Remote user and Password boxes.
l
In the Backup command box, type the following value:
save -xL
l
In the Save operations box, type the following value:
VSS:*=off
You must select View > Diagnostic Mode in the Administration window to enable
diagnostic mode view and access the Save operations attribute.
Configuring a Client resource for backups on UNIX hosts
This section describes how to configure a Client resource to backup data on UNIX hosts.
UNIX/Linux backup considerations
The following topics provide details on considerations for backing up client data on
Solaris, Linux, HP-UX, and AIX computers.
Linux
You can install the NetWorker client, server, storage node, and NetWorker Management
Console (NMC) server software on Linux.
Backup and recovery operations are supported on the following Linux journaled file
systems:
l
ext3
l
reiserfs
Mapped drives
373
Backing Up Data
l
jfs
l
xfs
For ext3 file systems with the journal set to visible, do not back up or recover the
journal. Recovering the journal may cause the file system to become unstable. Use a
directive to ensure that the file system is excluded from a backup. Directives on page 323
provides information on directives.
Solaris
You can install NetWorker client, server, storage node, and NetWorker Management
Console (NMC) server software on the Solaris platform.
The NetWorker software supports local and global zones for a NetWorker client, server,
and a dedicated storage node. You can install and back up a NetWorker client, server, or
storage node on a computer running in a local zone. The NMC and NetWorker License
Manager can only be installed in a global zone.
Note
Extended file attribute data is in the calculation of the save set file size for Solaris clients.
As a result, the save set file size in NetWorker appears to slightly larger than expected.
NetWorker executables not found for Solaris client
On Solaris client computers, NetWorker executables are installed by default in /usr/
sbin. The search path for root on the NetWorker server must include /usr/sbin.
Otherwise, scheduled backups fail on a client with NetWorker executables in /usr/
sbin because the savefs command is not in the search path.
To solve this issue, edit the search path for root on the NetWorker server to
include /usr/sbin, even if the directory does not exist locally.
Alternatively, specify /usr/sbin in the Executable path attribute on the Globals (2 of 2)
tab of the Client Properties dialog box for the Client resource.
HP-UX
You can install NetWorker client, server, storage node, and NetWorker Management
Console (NMC) server software on the HP-UX platform.
Customized backup scripts
On HP-UX, do not use the posix shell (/bin/sh) for customized backup scripts that are
meant to be automatically started by the backup. Use the korn shell (/bin/ksh)
instead.
Symbolic link entries in the fstab file
For HP-UX operating systems, do not use symbolic link entries in the /etc/fstab file. If
you use symbolic links in the fstab file, the backup does not include the file system to
which the symbolic link points.
374
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
AIX
You can install the NetWorker client, server, storage node, and NetWorker Management
Console (NMC) server software on the AIX platform.
Note
On AIX, non-root users who are performing a recovery cannot restore group ownership
(the set-group-id-on-execution or setuid permission bit) on binaries or files.
This behavior is to be expected.
Creating a Client resource with the Client Backup Configuration wizard
The Client Backup Configuration wizard enables you to quickly configure a Client
resource with a limited set of key backup options. Follow these steps to configure a file
system backup and a UNIX host.
Before you begin
l
Install the NetWorker client software on the client computer.
l
Ensure that the NetWorker server host is listed in the servers file on the client
computer.
l
Ensure that the communication between the NMC server, NetWorker client, and
NetWorker server uses nsrauth strong authentication.
l
Ensure that the user who runs the wizard meets the following requirements:
l
n
Root (UNIX) or Administrator (Windows) privileges.
n
A member of a User Group on the NetWorker server that has Configure NetWorker
privileges.
Ensure that multiple wizard hosts are not trying to access the same client computer
simultaneously.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Clients, and then select New Client Wizard.
The Client Backup Configuration wizard appears, starting on the Specify the Client
Name page.
3. In the Client Name box, type the hostname of the client computer.
It is recommended that you specify the fully qualified domain name (FQDN) of the
host. For OS cluster hosts, type the FDQN of the virtual host.
For application cluster hosts, type the FQDN of the application cluster host. For
example:
l
For an Oracle cluster, type the RAC hostname.
l
For an Exchange IP DAG, type the DAG name.
The application module administrator guides provide more information.
Note
If the Client Configuration wizard cannot resolve the specified hostname, an error
message appears after you click Next.
Creating a Client resource with the Client Backup Configuration wizard
375
Backing Up Data
4. Optionally, in the Comment box, type a description of the client.
If you are creating multiple client resources for the same NetWorker client host, then
use this attribute to differentiate the purpose of each resource.
5. In the Tag box, type one or more tags to identify this Client resource for the creation of
dynamic client groups for data protection policies.
Place each entry on a separate line.
6. In the Type box, select Traditional NetWorker client.
7. Optionally, from the Group list, select a group for the Client resource.
The group to which the client belongs determines the workflow that is used to back up
the client.
Note
You can also assign the client to one or more groups after you create the Client
resource.
8. Click Next.
9. On the Specify the Backup Configuration Type window, select Filesystem, and then
click Next.
10. On the Select the NetWorker Client Properties window, configure the following
options:
Option
Description
Priority
Enables you to control the order in which the NetWorker server
contacts clients for backup. During a backup operation, the
NetWorker server contacts the client with the lowest priority value
first. If you do not specify a priority for the client resources, then the
backup order is random. The default value is 500.
While the Priority attribute specifies the order of client contact, many
variables affect the order in which clients complete their backups.
For example:
l
The backup operation on a client does not begin until the
worklists for each of the save sets on the client are complete.
l
The amount of work can vary greatly from one client to the next.
l
If a client stops responding and times out, then the backup
operation puts the client backup at the end of the backup order
list.
The only way to guarantee that the backup of one client occurs
before the backup of another client is to configure the workflows for
the clients to start at different times.
Parallelism
Specifies the maximum number of data streams that a client can
send simultaneously during a backup action.
Data streams include back data streams, savefs processes, and
probe jobs.
The default value is different for the NetWorker server than it is for all
other client resources:
376
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Option
Description
l
For the NetWorker server client resource, the default value is 12.
This higher default value enables the server to complete a larger
number of index backups during a Server backup action.
l
For all other clients, the default value is 4.
To avoid disk contention for clients other than the NetWorker server,
specify a value that is the same as or fewer than the number of
physical disks on the client that are included in the backup.
The EMC NetWorker Performance Optimization Planning Guide provides
more information about recommended client parallelism values and
performance benefits.
Remote
Access
Specifies a list of the users that have access to perform remote
access operations. For example, users that can perform a directed
recovery of backup data that originated on this host.
Data Domain
Interface
Specifies the protocol to use if you send the backup data to a Data
Domain Device. Available selections are IP, Fibre Channel, or Both.
Note
Mac OS X clients only support the IP protocol.
Block Based Enables Block Based Backups for the host. When you select this
Backup (BBB) option, you must also select the Client Direct.
This option applies to Linux only.
Note
The Block Based Backup chapter provides complete information
about how to configure a host for BBB backups.
Client Direct
Allows the client to try to directly connect to the backup storage
device, instead of connecting to a NetWorker storage node. If a direct
connection is not possible, then the backup operation connects to
the NetWorker storage node that you configure to accept data from
the client.
Parallel Save
Streams
(PSS)
Enables NetWorker to use multiple parallel save streams to backup
each save set defined for the client, to one or more destination
devices. PSS does not support Checkpoint Restart backups.
11. Click Next.
12. On the Select the File System Objects window, select the file system objects to
backup.
To avoid the over consumption of memory, NetWorker limits the number of files that
you can view when you browse a directory that contain a large number of files, for
example, 200,000 files. When NetWorker determines that displaying the number of
files will exhaust memory resources, NetWorker will display a partial list of the files
and a message similar to the following appears: Expanding this directory
has stopped because the result has too many entries
Creating a Client resource with the Client Backup Configuration wizard
377
Backing Up Data
Note
When you select all file system objects, the ALL value appears in the Save set
attribute for the client resource. When the backup starts, the savefs process reads
the contents of the /etc/vfstab file on Solaris clients, the /etc/fstab file on
HP-UX and Linux clients, or the /etc/filesystems file on AIX clients. The contents
of the file are compared to the currently mounted file systems and BTRFS subvolumes. Only currently mounted file systems and BTRFS sub-volumes that are
configured in these files are backed up. When NetWorker encounters a sub-directory
that has a sub-volume ID that differs from the parent sub-volume ID, NetWorker will
not backup the contents of the subdirectory, unless you specify the save -x in the
Backup command field in the properties of the Client resource. After you create the
client configuration wizard, you can modify the client resource or create a new client
resource to include the excluded file systems. Supported save set configurations for
UNIX hosts on page 378 provides more information.
When you specify the ALL save set:
l
For a Solaris sparse or whole root zone client, all mounted file systems in the
sparse or whole root zone that are not normally skipped, such as NFS, are backed
up.
l
ZFS file systems are backed up.
l
If the save set name includes a symbolic link, a save set recovery is not supported.
13. On the Backup Configuration Summary window, click Create.
14. On the Client Configuration Results window, review the results of the client
configuration process, then click Finish.
Results
The Client resource appears in the Clients window pane.
Supported save set configurations for UNIX hosts
The Client Configuration wizard does not display some types of file systems on UNIX
hosts and these save sets are not in the ALL save set.
When the backup starts, the savefs process reads the contents of the /etc/vfstab
file on Solaris clients, the /etc/fstab file on HP-UX and Linux clients, or the /etc/
filesystems file on AIX clients. The contents of the file are compared to the currently
mounted file systems and BTRFS sub-volumes. Only currently mounted file systems and
BTRFS sub-volumes that are configured in these files are backed up. When NetWorker
encounters a sub-directory that has a sub-volume ID that differs from the parent subvolume ID, NetWorker will not backup the contents of the subdirectory, unless you
specify the save -x in the Backup command field in the properties of the Client resource.
If you edit a client resource and modify the Save set attribute to include file system
objects for file systems that are not in the OS file system file, NetWorker will not back up
the file system objects.
378
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
The following file systems are excluded from the ALL save set. If you manually define the
file system or directories and files for one of these file systems in the Save set attribute of
the Client resource, the backup operation excludes the object:
Table 69 File systems excluded from the ALL save set
l
hsfs
l
sharefs
l
dfs
l
binfmt_misc
l
nucam
l
proc
l
nfs2
l
autofs
l
usbfs
l
fdfs
l
fd
l
nfs3
l
iso9060
l
devpts
l
xx
l
cachefs
l
nfs3perf
l
udf
l
smbfs
l
none
l
lofs
l
profs
l
sysfs
l
swap
l
mntfs
l
nfs4
l
debugfs
l
tmp
l
ctfs
l
nfs
l
subfs
l
tmpfs
l
objfs
l
brfs
l
usbdevfs
l
nucfs
When you specify the ALL save set:
l
For a Solaris sparse or whole root zone client, all mounted file systems in the sparse
or whole root zone that are not normally skipped, such as NFS, are backed up.
l
ZFS file systems are backed up.
l
If the save set name includes a symbolic link, a save set recovery is not supported.
Use a customized ALL save set to backup files.
Modifying the save sets defined for a UNIX client
You can modify a client to change the file system objects to backup on the client.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
4. On the General tab, in the Save set attribute, specify the file system, directory or path
to a file. Specify one file system object on each line. You can also modify specify a
special ALL save set to backup a specific type of file system only. The following table
summarizes the available ALL save sets.
Table 70 Special ALL save sets
Special ALL save Backup behavior
set syntax
allfile_system
Only back up locally mounted file systems of a particular type, where
file_system is the name of the file system. For example, the all-zfs save
set backs up all locally mounted zfs file systems on a Solaris host. File
Supported save set configurations for UNIX hosts
379
Backing Up Data
Table 70 Special ALL save sets (continued)
Special ALL save Backup behavior
set syntax
systems such as NFS that are normally skipped are still skipped. When the
backup starts, the savefs process reads the contents of the /etc/
vfstab file on Solaris clients, the /etc/fstab file on HP-UX and Linux
clients, or the /etc/filesystems file on AIX clients. The contents of the
file are compared to the currently mounted file systems and BTRFS subvolumes. Only currently mounted file systems and BTRFS sub-volumes that
are configured in these files are backed up. When NetWorker encounters a
sub-directory that has a sub-volume ID that differs from the parent subvolume ID, NetWorker will not backup the contents of the subdirectory,
unless you specify the save -x in the Backup command field in the properties
of the Client resource. The EMC NetWorker Online Software Compatibility Guide
provides a list of the supported file system for each operating system.
all-mounts
all-local
Back up all the currently mounted file systems. File
systems such as NFS that are normally skipped are still
skipped.
For a global zone client, the file systems in the sparse
or whole root zone on the physical host are backed up. File
systems in the global zone are skipped.
For a sparse or whole root zone client, the all-local
save set is equivalent to the ALL save set.
all-global
For a global zone client, all file systems in the global
zone are backed up. All sparse and whole root zone file systems
on the physical host are skipped.
For a Solaris sparse or whole root zone client, the
all-global save set is equivalent to the ALL save set.
Note
If you explicitly list a BTRFS sub-volume in the Save set field, NetWorker will back up
the files in the sub-volume, even if the sub-volume does not appear in the /etc/
fstab file. When NetWorker encounters a sub-directory that has a sub-volume ID that
differs from the parent sub-volume ID, NetWorker will not backup the contents of the
subdirectory, unless you specify the save -x in the Backup command. To back up
data in the subdirectories, perform one of the following tasks:
l
Specify save -x in the Backup command field in the client properties window.
l
Explicitly list the path of each sub-volume in the Save set field.
l
Mount each sub-volume, include the mount point in the /etc/fstab file, and
then specify ALL or all-btrfs in the Save set field.
5. Click OK.
380
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Configuring a Client resource for backups on Mac OS X hosts
This section describes how to configure a Client resource to backup data on Mac OS X
hosts.
Mac OS X backup considerations
You can configure a Mac OS X host as a NetWorker client. You can use any supported
NetWorker server on UNIX, Linux, or Windows to back up and restore an OS X host. You
cannot configure an OS X host as a NetWorker server or an NMC server.
The NetWorker client for OS X supports the following file systems:
l
HFS+ (including journaled)
l
HFS
l
UFS
The NetWorker client for OS X also backs up and recovers all file system metadata,
including:
l
Finder information
l
Resource forks
l
Extended attributes
l
Access Control Lists (ACLs)
Creating a Client resource with the Client Backup Configuration wizard
The Client Backup Configuration wizard enables you to quickly configure a Client
resource with a limited set of key backup options. Follow these steps to configure a file
system backup and an OS-X host.
Before you begin
l
Install the NetWorker client software on the client computer.
l
Ensure that the NetWorker server host is listed in the servers file on the client
computer.
l
Ensure that the communication between the NMC server, NetWorker client, and
NetWorker server uses nsrauth strong authentication.
l
Ensure that the user who runs the wizard meets the following requirements:
l
n
Root (UNIX) or Administrator (Windows) privileges.
n
A member of a User Group on the NetWorker server that has Configure NetWorker
privileges.
Ensure that multiple wizard hosts are not trying to access the same client computer
simultaneously.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, right-click Clients, and then select New Client Wizard.
The Client Backup Configuration wizard appears, starting on the Specify the Client
Name page.
3. In the Client Name box, type the hostname of the client computer.
Configuring a Client resource for backups on Mac OS X hosts
381
Backing Up Data
It is recommended that you specify the fully qualified domain name (FQDN) of the
host. For OS cluster hosts, type the FDQN of the virtual host.
For application cluster hosts, type the FQDN of the application cluster host. For
example:
l
For an Oracle cluster, type the RAC hostname.
l
For an Exchange IP DAG, type the DAG name.
The application module administrator guides provide more information.
Note
If the Client Configuration wizard cannot resolve the specified hostname, an error
message appears after you click Next.
4. Optionally, in the Comment box, type a description of the client.
If you are creating multiple client resources for the same NetWorker client host, then
use this attribute to differentiate the purpose of each resource.
5. In the Tag box, type one or more tags to identify this Client resource for the creation of
dynamic client groups for data protection policies.
Place each entry on a separate line.
6. In the Type box, select Traditional NetWorker client.
7. Optionally, from the Group list, select a group for the Client resource.
The group to which the client belongs determines the workflow that is used to back up
the client.
Note
You can also assign the client to one or more groups after you create the Client
resource.
8. Click Next.
9. On the Specify the Backup Configuration Type window, select Filesystem, and then
click Next.
10. On the Select the NetWorker Client Properties window, configure the following
options:
Option
Description
Priority
Enables you to control the order in which the NetWorker server
contacts clients for backup. During a backup operation, the
NetWorker server contacts the client with the lowest priority value
first. If you do not specify a priority for the client resources, then the
backup order is random. The default value is 500.
While the Priority attribute specifies the order of client contact, many
variables affect the order in which clients complete their backups.
For example:
382
EMC NetWorker 9.0.x Administration Guide
l
The backup operation on a client does not begin until the
worklists for each of the save sets on the client are complete.
l
The amount of work can vary greatly from one client to the next.
Backing Up Data
Option
Description
l
If a client stops responding and times out, then the backup
operation puts the client backup at the end of the backup order
list.
The only way to guarantee that the backup of one client occurs
before the backup of another client is to configure the workflows for
the clients to start at different times.
Parallelism
Specifies the maximum number of data streams that a client can
send simultaneously during a backup action.
Data streams include back data streams, savefs processes, and
probe jobs.
The default value is different for the NetWorker server than it is for all
other client resources:
l
For the NetWorker server client resource, the default value is 12.
This higher default value enables the server to complete a larger
number of index backups during a Server backup action.
l
For all other clients, the default value is 4.
To avoid disk contention for clients other than the NetWorker server,
specify a value that is the same as or fewer than the number of
physical disks on the client that are included in the backup.
The EMC NetWorker Performance Optimization Planning Guide provides
more information about recommended client parallelism values and
performance benefits.
Remote
Access
Specifies a list of the users that have access to perform remote
access operations. For example, users that can perform a directed
recovery of backup data that originated on this host.
Data Domain
Interface
Specifies the protocol to use if you send the backup data to a Data
Domain Device. Available selections are IP, Fibre Channel, or Both.
Note
Mac OS X clients only support the IP protocol.
Block Based Enables Block Based Backups for the host. When you select this
Backup (BBB) option, you must also select the Client Direct.
This option applies to Linux only.
Note
The Block Based Backup chapter provides complete information
about how to configure a host for BBB backups.
Client Direct
Allows the client to try to directly connect to the backup storage
device, instead of connecting to a NetWorker storage node. If a direct
connection is not possible, then the backup operation connects to
the NetWorker storage node that you configure to accept data from
the client.
Creating a Client resource with the Client Backup Configuration wizard
383
Backing Up Data
Option
Description
Parallel Save
Streams
(PSS)
Enables NetWorker to use multiple parallel save streams to backup
each save set defined for the client, to one or more destination
devices. PSS does not support Checkpoint Restart backups.
11. Click Next.
12. On the Select the File System Objects window, select the file system objects to
backup.
To avoid the over consumption of memory, NetWorker limits the number of files that
you can view when you browse a directory that contain a large number of files, for
example, 200,000 files. When NetWorker determines that displaying the number of
files will exhaust memory resources, NetWorker will display a partial list of the files
and a message similar to the following appears: Expanding this directory
has stopped because the result has too many entries
Note
When you select all file system objects, the ALL value appears in the Save set
attribute for the Client resource. The ALL save set includes local and mounted
volumes.
13. On the Backup Configuration Summary window, click Create.
14. On the Client Configuration Results window, review the results of the client
configuration process, then click Finish.
Results
The Client resource appears in the Clients window pane.
Assigning directives to Mac OS X clients
After you create a client resource for an OS X client, select one of the Mac OS directives to
exclude certain files and directories from the backup, and ensure a consistent state after
a recovery operation.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
4. On the General tab, in the Directive box, select one of the following directives:
l
Mac OS Standard Directives
l
Mac OS with Compression Directives
Preconfigured global Directive resources on page 326 provides more information
about the Mac OS directives.
5. Click OK.
Configuring Open Directory database backups
The Mac OS directive does not back up Open Directory database files, which contain
system configuration information that is essential for disaster recovery. To ensure
384
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
complete protection of a Mac OS X computer if a catastrophic failure occurs, create a
script file and then modify the client resource for the Mac OS X host to include the Open
Directory database files.
Customizing backups with the pre and post commands on page 403 provides more
information about the script file and the how to modify the client resource to use the
command.
Procedure
1. On the OS X host, create the script file as an executable text file.
The name of the script file must start with nsr or save. For example
nsr_opendir_backup.sh
2. Add the commands to backup open files to the script file.
Note
Open Directory database files remain available during the backup.
l
To back up LDAP directory domain for the Open Directory, type:
#slapcat -l /var/backups/networker.ldif
l
To back up Password Server database for the Open Directory when the OS-X host
uses LDAP over SSL, type:
# mkdir -p /var/backups/networker.odpdb
# mkpassdb -backupdb /var/backups/networker.odpdb
l
To back up the local NetInfo directory domain, type:
# nidump -r / . > /var/backups/networker.nidump
The following script file provides an example of how to back up the LDAP directory,
Password Server, and NetInfo databases before each scheduled save:
"/usr/sbin/slapcat -l /var/backups/networker.ldif;
/bin/mkdir -p /var/backups/networker.odpdb;
/usr/sbin/mkpassdb -backupdb /var/backups/networker.odpdb;
/usr/bin/nidump -r / . > /var/backups/networker.nidump"
3. Connect to the NetWorker server by using NMC.
4. In the Administration window, click Protection.
5. In the expanded left pane, select Clients.
6. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
7. On the Apps and Modules tab, in the Pre command attribute, specify the name of the
script file that you require NetWorker to run before a backup.
Note
Do not specify the path to the file.
8. Click OK.
Configuring Open Directory database backups
385
Backing Up Data
Sending client data to AFTD or Data Domain devices only
Use the Backup target disks attribute of the client resource to define an ordered list of
AFTD and Data Domain disk devices that will receive data for this client. When you specify
a value in this attribute, NetWorker ignores the values that you specify in the Storage
nodes attribute. This attribute does not apply to the client resource of the NetWorker
server, and applies to each instance of the client resource. You can specify devices that
are local or remote to the NetWorker server.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
4. On the Globals (2 of 2) tab, in the Backup target disks attribute, specify the name of
the AFTD or Data Domain devices that NetWorker uses to store data for this client.
Specify each device name on a separate line.
5. Click OK.
Results
NetWorker does not use the values in the Storage nodes attribute of the client resource
when selecting the device to receive data for the client.
Non-ASCII files and directories
If you create a Client resource with the Client Properties dialog box and the Save set
attribute contains non-ASCII characters, you must edit the Save operations attribute on
the Apps & Modules tab for the Client resource.
On Windows clients, specify the following value in the Save operations attribute:
I18N:mode=utf8path
On UNIX/Linux clients, specify the following value in the Save operations attribute:
I18N:mode=nativepath
You must enable diagnostic mode view by selecting View > Diagnostic Mode in the
Administration window to access the Save operations attribute in the Client Properties
dialog box.
Configuring checkpoint restart backups
The checkpoint restart feature allows a failed backup operation to restart at a known
good point, before the point of failure during the backup.
Note
Checkpoint restart is only supported on Linux and UNIX environments when performing
standard save operations; you cannot use checkpoint restart with block-based backup or
parallel save streams enabled. Checkpoint restart is not supported on Windows
platforms.
386
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
A known good point is defined as a point in the backup data stream where the data is
successfully written to the save set and that data can be located and accessed by
subsequent recovery operations. This feature allows client backups that are part of a
scheduled backup to be restarted, if they fail while running. This prevents the files and
directories that have already been backed up from being backed up again.
Backup failures occur for various reasons. The most common reasons include hardware
failures, loss of network connectivity, and primary storage software failures. If a backup
fails and checkpoint restart is enabled, then failed save sets are marked as partial
instead of as aborted. Partial save sets remain in the index, the media databases, and
media such as AFTD.
You can manually restart a failed backup, or you can configure the backup to restart
automatically. A restarted save set has a new SSID and savetime.
The NetWorker server and storage node components must remain running to manage the
client failure and to create a partial save set. If the NetWorker server or storage node
components fail during a backup, then partial save sets are not created. In this case, the
backup for the checkpoint-enabled client starts from the beginning.
If the checkpoint restart feature is not enabled, a failure that is encountered during a
scheduled backup operation might require a rerun of an entire backup tape set. This can
be costly when a limited backup window of time is available, as a significant portion of
the backup data might have been successfully transferred to tape, and the NetWorker
software cannot resume a save set from the point of interruption.
For example, when performing an 800 GB backup that requires approximately 10 hours to
complete and spans six tapes, if a failure occurs while writing to the last tape, the
previous five tapes representing 9 hours of backup time may need to be rerun. As
datasets continue to increase in size, so does the impact of backup failures.
About partial save sets
The backup sequence of partial save sets is not the same as the backup sequence for
complete backups. Each partial save set provides protection for part of the file system,
but the completeness and consistency of the coverage of the whole file system cannot be
guaranteed.
The checkpoint restart window is user-defined and can be large. If restarted hours apart,
the partial backups might provide an image of the file system that is different from the
state of the file system at any fixed point in time. The resulting file system backup is not
guaranteed to be consistent.
NetWorker performs file and directory backups in alphabetical order. If a failure occurs,
and you restart the backup, the backup operation starts alphabetically with the next file
or folder that was not backed up. NetWorker does not review files or folder that were
previously backed up for changes. If a previously backed up file or folder was edited or
added after the backup failure, NetWorker does not back up the file or directory again.
Consider the following example where a backup is interrupted while saving a directory
and restarted after the directory contents have changed:
1. A save set contains /disk1/dir with files file_a, file_c and file_d.
2. A point of interruption occurs in the backup of the save set during the back up of
file_d.
As a result, the first partial save set includes only file_a and file_c.
3. A user adds file_b to the file system.
4. The checkpoint restart is initiated for the save set.
About partial save sets
387
Backing Up Data
The second partial save set contains file_d and /disk1/dir, which includes
file_a, file_b, file_c and file_d. However, file_b is not in the save set.
Partial save sets and cloud backup devices
The Checkpoint Restart feature does not support cloud backup devices by default
because partial save sets are not retained on cloud backup devices. To keep partial save
sets when you use a cloud backup device, select the Keep Incomplete Backups attribute
on the Configuration tab of the Server Properties dialog box for the NetWorker server.
Partial saveset cloning and scanning
Partial save sets can be cloned and scanned individually. These operations must be
performed on every partial save set.
If legacy automatic cloning is enabled, all partial save sets are cloned because automatic
cloning is run as part of the scheduled backup.
Checkpoint restart requirements
Ensure that the environment meets the following requirements to support checkpoint
restart.
Server and client software requirements
Checkpoint restart requires the server and client software listed in the following table.
Table 71 NetWorker software requirements for checkpoint restart
Client
NetWorker server and client software requirements
Non-NDMP clients
NetWorker 8.0 or later
NDMP NetApp clients NetWorker 8.0 or later
NDMP Isilon clients
NetWorker 8.1 SP1 or later
Platform requirements
Checkpoint restart is only supported on Linux and UNIX environments when performing
standard save operations. You cannot use checkpoint restart with block-based backup or
parallel save streams enabled.
Checkpoint restart is not supported on Windows platforms.
Client hostname requirements
Use a consistent convention for all NetWorker client hostnames. Do not configure client
resources with both short and fully qualified domain names (FQDN).
Save set requirements
Backup of the Windows DISASTER_RECOVERY:\ save set is not supported. If a client
with a DISASTER_RECOVERY:\ save set is enabled for checkpoint restart, the backup
fails.
The checkpoint restart option is ignored for index and bootstrap save sets.
Client Direct requirements
Checkpoint restart supports Client Direct backups only to AFTD devices, and not to DD
Boost devices. If a client is enabled for checkpoint restart and a Client Direct backup is
attempted to a DD Boost device, then the backup reverts to a traditional storage node
backup instead.
388
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
For Client Direct backups to AFTDs, checkpoints are made at least 15 seconds apart.
Checkpoints are always made after larger files that require more than 15 seconds to back
up.
Performance requirements
Enabling checkpoint restart might impact backup speed, depending on the datazone
environment and configuration.
Checkpoint restart also might increase the size of the index because additional index
records are created for the valid recoverable data. These partial save sets should not be
manually removed from the index.
Configuring checkpoint restart
To allow a failed backup for a client to restart from a known good point, you must enable
checkpoint restart for the NetWorker Client resource and configure the number of
automatic retries for the backup action in the data protection policy.
When you enable checkpoint restart, you define whether to restart the backup at the
directory or file level from the point of failure.
Procedure
1. In the Administration window, click Protection.
2. From the View menu, select Diagnostic Mode.
3. In the expanded left pane, select Clients.
4. Right-click the client resource and select Properties.
The Client Properties dialog box appears.
5. On the General tab, select the Checkpoint enabled checkbox.
6. From the Checkpoint granularity list, select whether to restart the backup from the
point of failure at the directory or file level:
l
Select Directory to restart the backup at the directory level. After each directory is
saved, the data is committed to the media and index database. If a directory
contains a large number of entries, intermediate checkpoints are created.
l
Select File to restart the backup at the file level. Use this option only for save sets
with a few large files. Committing every file to the index and the media database is
time consuming. Performance degradation may occur for backups that contain
many small files.
7. Click OK on the Client Properties dialog box.
8. Configure the number of times to retry a failed backup:
a. In the expanded left pane of the NetWorker Administration window, select
Policies.
b. Select the policy.
c. In the right pane, select the Actions tab.
d. Right-click the action and select Properties.
The Policy Action wizard appears.
e. On the Advanced Options page, perform the following tasks:
a. In the Retries box, specify the number of retries that should occur if the backup
fails.
b. In the Retry Delay box, specify a delay in seconds before a failed backup is
retried.
Configuring checkpoint restart
389
Backing Up Data
c. Click Next.
f. On the Action Wizard Summary page, review the settings for the backup action,
and then click Configure .
Restarting checkpoint-enabled backups
You can configure automatic restarts of checkpoint-enabled backups by specifying the
number of retries for the backup action in the data protection policy. You can also
manually restart a checkpoint-enabled backup.
NOTICE
If you rename a save set, the checkpoint restart fails to find a match against a previous
run and the restart reverts to a complete backup. Also, do not edit retention in between
checkpoint restarts, as an expired partial save set may leave gaps in the backup set.
Automatically restarting a checkpoint-enabled backup
If the NetWorker server fails to connect to a client for a backup, the Retries attribute for
the backup specifies the number of times that the server tries the connection to the client
before the backup is considered a failure.
The Retries attribute applies to a backup regardless of whether the checkpoint restart is
enabled for the client. However, a partial save set is created when there is a failure for a
checkpoint-enabled client, and the backup is automatically restarted from the checkpoint
until the specified number of retries has been exceeded.
The automatic restart must occur within the restart window that you specify for the
workflow for the data protection policy.
Example 1
There are six clients in a group, each with three save sets. The Retries attribute for the
backup is 1. One save set fails and is checkpoint restarted immediately. The remaining
save sets in the group continue to back up. The save set fails a second time. A checkpoint
restart for the save set does not occur because the retry attempt would exceed the value
for the Retries attribute.
When all the save set backup attempts in the group complete, the backup completion
report:
l
Provides a list of the successful save sets.
l
Reports that the failed partial save set is unsuccessful.
l
Reports that the backup failed.
Example 2
There are six clients in a group, each with three save sets. The Retries attribute for the
backup is 2. One save set fails and is checkpoint restarted immediately. The remaining
save sets continue to back up. The partial save set fails a second time and is checkpoint
restarted immediately. This time, the partial save set succeeds.
When all the save set backup attempts in the group are complete, the backup completion
report:
390
l
Provides a list of the successful save sets.
l
Reports that the two partial save sets are successful.
l
Reports that the backup completed successfully.
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Manually restarting a checkpoint-enabled backup
You can manually restart the data protection policy or workflow for a failed backup. For
checkpoint-enabled clients, the backup continues from the checkpoint. For other clients,
the incomplete save sets are backed up again in full.
Procedure
1. In the Administration window, click Monitoring.
2. Right-click the policy or workflow for the failed backup, and select Restart.
A confirmation message appears.
3. Click Yes.
Recovering data from partial save sets
If there is a complete sequence of partial save sets that span the original save set, then
you can browse to and recover individual files and directories. If the sequence of partial
save sets is incomplete and does not make up the original save set, then you must
perform a save set recovery to recover the data from the partial save set.
To recover data from partial save sets that span the original save sets, perform a query for
all partial save sets, and then use either the NetWorker User program on Windows or the
recover program on UNIX to restore the data.
The steps to recover data from a single partial save set are the same as save set recovery
from a complete save set. The partial save set contains only files that were successfully
backed up. You cannot browse partial save sets.
When you perform a save set recovery of a partial NDMP save set, the recovery process
recovers all partial save sets in the checkpoint sequence. You cannot recover data in a
partial save set separately from other partial save sets in the checkpoint sequence.
Use the nsrinfo command to display the contents of a partial save set.
Probe-based backups
You can configure the NetWorker server to search or probe a NetWorker client for a userdefined script before the start of a scheduled backup operation. A user-defined script is
any program that passes a return code.
When the NetWorker server detects the script, the NetWorker server runs the script and
interprets two return codes:
l
Return code 0 indicates that a client backup is required.
l
Return code 1 indicates that a client backup is not required.
NetWorker interprets all other return codes as an error and does not perform a backup.
Procedure
1. Create the Probe resource script, and save the script in the same directory as the
NetWorker binaries on each client that uses the client probe.
The name of the probe script must begin with save or nsr.
Note
Users are responsible for creating and supporting user-defined scripts.
Recovering data from partial save sets
391
Backing Up Data
2. Create the Probe resource on the NetWorker server:
a. In the Administration interface, click Protection.
b. In the expanded left pane, right-click Probes and select New.
The Create NSR probe dialog box appears.
c. In the Name box, specify the name of the probe.
d. (Optional) In the Comment box, specify details for the probe script.
e. In the Command box, type the name and path of the probe script.
Note
The Command options box applies to NetWorker Module probes only.
f. Click OK.
3. Associate the probe with a Client resource:
a. In the expanded left pane of the Protection window, select Clients.
b. In the right pane, right-click the Client resource, and select Modify Client
Properties.
The Client Properties dialog box appears.
c. Click the Apps & Modules tab.
d. Select the probe resource from the Probe resource name list.
e. Click OK.
4. Configure a data protection policy with a workflow that includes a probe action:
a. Create a group that includes the client with the assigned probe resource.
b. Create a policy.
c. Create a workflow.
d. Create a probe action and a backup action for the workflow.
Encryption and compression
You can apply password protection and 256-bit data encryption to backup and archive
data on UNIX and Windows hosts for additional security, or you can compress backup
data to reduce network traffic and backup storage requirements.
You can apply password protection alone, encryption alone, password protection and
encryption together, or compression alone. You cannot apply password protection and
compression together or encryption and compression together.
Password protection and encryption
Encryption is supported through the use of the aes Application Specific Module (ASM)
based on the password that is defined on the UNIX or Windows host. If a password is not
defined on the host, then data is encrypted with the default password configured for the
NetWorker server.
When NetWorker uses aes to encrypt the backup data, backup times increase. The
process of encrypting the data will also increase CPU and memory usage on the backup
client. The impact to CPU and memory resources depends on a number of factors
including the load on the host, network speed, and the number of backup files. A backup
392
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
of a single large file will require less resources than a backup of a dense file system,
where NetWorker must access a large number of small-sized files.
NOTICE
You must specify the password to recover password-protected files. If the password was
configured or changed after the backup occurred, then you must provide the password
that was in effect when the file was originally backed up. Keep password changes to a
minimum.
Do not use the aes ASM for data encryption when backing up files that are encrypted by
using the Microsoft Windows Encrypting File System (EFS). The backup is reported as
successful, but recovery of the file fails and the following message is written to the
NetWorker log file:
recover: Error recovering
filename. The RPC call completed before all pipes were
processed.
When a backup includes EFS encrypted files, the files are transmitted and stored on
backup volumes in their encrypted format. When the files are recovered, they are also
recovered in their encrypted format.
Compression
Compressing data for a backup generates less network traffic. However, compression
uses computing resources, so its benefits may be limited on low-powered systems. If the
storage device also compresses data, the result may be that more data is actually written
to tape.
Configuring encryption or compression for scheduled backups
Procedure
1. (Optional) If you are applying encryption, configure a password on the UNIX or
Windows host.
To configure the password on a Windows host, select Options > Password in the
NetWorker User program, and then type the password.
2. If you are applying encryption, configure the default password on the NetWorker
server:
a. In the Administration window, click Protection.
b. In the left pane, right-click the NetWorker server, and select Properties.
The Server Properties dialog box appears, starting with the Setup tab.
c. Click the Configuration tab.
d. Type the password in the Datazone pass phrase attribute.
e. Click OK.
3. Configure a directive for the Client resource with either the aes ASM for encryption or
the compressasm ASM for compression.
You can use the Encryption global directive to apply encryption, or one of the global
directives with compression to apply compression. You can also configure a local
directive on the client computer. Directives on page 323 provides more information.
Configuring encryption or compression for scheduled backups
393
Backing Up Data
Configuring password protection, encryption, or compression for a manual backup
When you perform a manual backup on Windows with the NetWorker User program, you
can specify password protection, encryption, or compression settings when you perform
the backup.
To compress data for a manual backup on UNIX, you must use the compressasm ASM in
a local directive file.
Procedure
1. (Optional) If you are applying password protection or encryption, configure a
password on the Windows host.
a. Open the NetWorker User program.
b. Select Options > Password.
c. Type the password in the Password dialog box and click OK.
2. Open the NetWorker User program and click Backup.
3. Select the data to back up.
4. From the File menu, select Special Handling.
The Special Handling dialog box appears.
5. Select the handling method for the backup data:
l
Password Protect
l
Password Protect and Encrypt
l
Compress
6. Click OK.
7. Click Start to start the backup.
Compression
You can compress backup data to reduce network traffic and backup storage
requirements.
Compressing data for a backup generates less network traffic. However, compression
uses computing resources, so its benefits may be limited on low-powered systems. If the
storage device also compresses data, the result may be that more data is actually written
to tape.
Note
You can apply password protection alone, encryption alone, password protection and
encryption together, or compression alone. You cannot apply password protection and
compression together or encryption and compression together.
Configuring compression for scheduled backups
Configure a directive for the Client resource with the compressasm ASM for
compression.
You can use one of the global directives with compression or configure a local directive
on the client computer.
394
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Configuring compression for manual backups
The methods of configuring compression for UNIX and Windows differ.
To compress data for a manual backup on UNIX, you must use the compressasm ASM in
a local directive file.
To configure data for a manual backup on Windows, use either thecompressasm ASM in
a local directive file, or use the following procedure.
Procedure
1. Configure a password on the Windows host.
a. Open the NetWorker User program.
b. Select Options > Password.
c. Type the password in the Password dialog box and click OK.
2. Open the NetWorker User program and click Backup.
3. Select the data to back up.
4. From the File menu, select Special Handling.
The Special Handling dialog box appears.
5. Select Compress as the handling method for the backup data.
6. Click OK.
7. Click Start to start the backup.
Configuring Client Direct backups
NetWorker clients with network access to AFTD or DD Boost storage devices can bypass
the NetWorker storage node and send backup data directly to the devices. This type of
backup is called a Client Direct backup.
The storage node manages the devices for the NetWorker clients, but does not handle the
backup data.
A Client Direct backup reduces bandwidth usage and bottlenecks at the storage node,
and provides highly efficient backup data transmission.
If a Client Direct backup is not available, a traditional storage node backup occurs
instead.
Requirements for Client Direct backups
Ensure that the environment meets the following requirements to perform Client Direct
backups:
l
NetWorker clients on UNIX/Linux or Microsoft Windows can perform non-root and
cross-platform Client Direct backups to AFTDs. The AFTD can be managed by either a
UNIX/Linux or a Windows storage node, and can be either local or mountable on the
storage node.
To perform non-root and cross-platform Client Direct backups to AFTDs, the
NetWorker server and the storage node software must be version 8.1 or later.
l
If an NFS server provides the AFTD storage for Client Direct backups, then the NFS
server must permit access by using the NFSv3 protocol with AUTH_SYS (AUTH_UNIX)
authentication. The NFS server also must not restrict access to clients by using only
privileged ports.
Configuring compression for manual backups
395
Backing Up Data
l
If you enable checkpoint restart for a client, then Client Direct backups are supported
only to AFTDs, and not to DD Boost devices. If a client is enabled for checkpoint
restart and a Client Direct backup is tried to a DD Boost device, then the backup
reverts to a traditional storage node backup instead.
For Client Direct backups to AFTDs, checkpoint restart points are made at least 15
seconds apart. Checkpoints are always made after larger files that require more than
15 seconds to back up.
l
Archive operations are not currently supported for Client Direct backups.
Configuring Client Direct backups
Procedure
1. Ensure that the clients that perform Client Direct backups have a network connection
and a remote network protocol to reach the storage device.
Windows clients can use a CIFS or NFS path, although a CIFS path generally yields
better performance. UNIX clients must use an NFS path.
2. Specify the complete path for the destination device in the Device access information
attribute on the General tab of the Device Properties dialog box for the destination
device.
Keep in mind the following points when you specify the path:
l
If the storage device is directly attached to a Windows storage node, then the
storage node uses a different path than the Client Direct clients. If the storage
device is not directly attached to any storage node, then the path is the same for
all storage nodes and Client Direct clients.
l
The device access information path should include multiple access paths to cover
local and remote use cases.
l
To specify an NFS path, use the NFS_host:/path format regardless of whether
the AFTD is local to the storage node or mountable on the storage node. Non-root
UNIX/Linux NetWorker clients require this NFS format for Client Direct access.
l
For Windows Client Direct backups, specify a CIFS path instead of an NFS path. A
CIFS path generally yields better performance.
l
If you are setting up an AFTD on a Windows storage node, specify the CIFS path
first. For example:
\\fileserver\aftd1
fileserver:/aftd1
l
If you are setting up a UNIX/Linux storage node, specify the NFS path first. For
example:
fileserver:/aftd1
\\fileserver\aftd1
The following figure shows an example set of paths for a CIFS AFTD.
396
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Figure 43 Paths for CIFS AFTD
3. If an NFS server provides the AFTD storage for Client Direct backups, then specify the
username and password that is required to access the NFS server for the AFTD in the
Remote user and Password attributes on the Configuration tab of the Device
Properties dialog box for the device.
4. Ensure that the Client direct attribute is enabled on the General tab of the Client
Properties dialog box for each Client Direct client.
Client Direct backups are enabled by default.
Select View > Diagnostic Mode in the Administration interface to access the Client
direct attribute in the Client Properties dialog box.
Backup command customization
You can customize client backups by creating additional programs (scripts) that affect the
way the NetWorker server will back up client file system data.
NetWorker provides you with the following features, which enable you to customize
scheduled backups for a client:
l
Create a custom backup script that starts the save command.
l
Create a script file that performs operations before the start of a backup.
l
Create a script file that performs operations after the backup of all save sets for a
client completes.
For example, you can create a custom backup script that performs the following tasks:
1. Shuts down a mail server or database before the NetWorker server performs a
backup.
2. Prints a message such as Backup started at 3:33 A.M.
3. Starts the save command and performs a backup.
4. Prints a message such as Backup completed at 6:30 A.M.
5. Restarts the mail server or database after the backup completes.
Creating a custom backup script
Create a script that runs the save program as part of its instructions to customize
behavior of scheduled backups of a client. When NetWorker performs a back up of the
Backup command customization
397
Backing Up Data
client, NetWorker runs the customized program for each save set instead of the standard
save program.
Procedure
1. Use a text editor to create a script in the networker_installation_dir\bin
directory on Windows clients or the networker_installation_dir/bin on
LINUX or UNIX clients.
The script name must meet the following requirements:
l
Starts with save or nsr.
l
Ends with the .bat extension.
l
Contains a maximum of 64 characters.
For example, script file names that meet these criteria include
save_custom_script.bat and nsr_backup_script.bat.
2. Add commands to the script in the following order:
a. (Optional) Run a preprocessing command before each save set backup.
b. (Required) Back up the data by using the NetWorker save command. Always
specify the full path of the save command in the script.
On UNIX and Linux hosts, run the NetWorker save command with the arguments
save “$@” to enable the save command to accept the arguments that the
NetWorker savefs program would run during a regular.
c. (Optional) Run a postprocessing command after each save set backup.
Note
All commands within the script must complete successfully. Otherwise, the NetWorker
server cannot complete the remaining instructions.
3. Save and close the script file.
4. Specify the name of the backup script in the Backup command attribute for the Client
resource:
a. In the Administration window, click Protection.
b. In the expanded left pane, select Clients.
c. Right-click the Client resource, and select Modify Client Properties.
The Client Properties dialog box appears, starting with the General tab.
d. Select the Apps & Modules tab.
e. Type the name of the backup script in the Backup command box.
f. Click OK.
5. Back up the client to ensure that the new backup command works.
Results
NetWorker logs information about the backup status in separate log files, and not in the
save output. "Reporting group status and backup job status" provides more information
about how to review backup job status.
398
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Example backup script on Windows
In this example backup script for a Windows client computer, the customized backup
program runs pre-backup commands, the NetWorker save command, and then postbackup commands.
Description of the example script
The following table provides details on each type of command in the example backup
script.
Table 72 Example backup script on Windows
Command type Description
Pre-backup
Redirects the output of the net start DOS command to create a
netstart.txt file at the root of the C:\ drive, and sends all information
about started services for the current computer to this file.
save
Runs NetWorker commands that are required to start the backup process.
Post-backup
Redirects the output of the set DOS command to a set.txt file at the root of
the C:\ drive, and sends all computer system environment information to this
file.
The netstart.txt and set.txt files are placed in the C:\directory. New
information is appended to these files each time a backup is run.
Example script
@ECHO OFF
SETLOCAL
ECHO =======START BATCH FILE================
ECHO =====NetWorker PRE_BACKUP COMMAND======
ECHO =======NET START - creates netstart.txt file and
ECHO =======sends all Started Services information
ECHO =======to the file c:\netstart.txt
NET START >>C:\NETSTART.TXT
REM This command takes incoming arguments from
REM the savegrp command and handle them
REM to overcome batch file limitations:
REM
REM
REM
REM
PARSE ALL INCOMING ARGUMENTS
and pass single argument in case
more than 10 arguments are passed to this file
(ie %0-%9 is not enough).
ECHO =====NetWorker SAVE SET COMMAND=======
SHIFT
SET arg=%0
:loop
SHIFT
IF %0.==. GOTO save
SET arg=%arg% %0
GOTO loop
REM These are the save commands that run the required
REM NetWorker backup commands.
:save
Creating a custom backup script
399
Backing Up Data
REM Note: Enter correct path to your NetWorker bin
REM directory (line below is default path)
C:\PROGRA~1\nsr\bin\save.exe %arg%
ECHO
ECHO
ECHO
ECHO
=====NetWorker POST_BACKUP COMMAND====
====="SET" - creates set.txt file and sends all
=====computer system environment information to
=====C:\set.txt file========
SET >>C:\SET.TXT
ECHO ======END OF BATCH FILE====
ENDLOCAL
Monitoring details for the script
The following information appears in the Monitoring window of the Administration
interface and the backup action log file. After the backup process completes, review the
log output to verify the execution of the commands in the script.
--- Successful Save Sets --:* jupiter:c:\inetpub =======START BATCH FILE============
* jupiter:c:\inetpub ===NetWorker PRE_BACKUP COMMAND===
* jupiter:c:\inetpub=======NET START
* creates netstart.txt file and sends all started
* jupiter:c:\inetpub ======services information to
* that file c:\netstart.txt==
* jupiter:c:\inetpub ===NetWorker SAVE SET COMMAND====
* jupiter:c:\inetpub save: using `C:\Inetpub' for
* `c:\inetpub'
jupiter: c:\inetpub level=full,194 KB 00:00:02 37 files
* jupiter:c:\inetpub =====NetWorker POST_BACKUP COMMAND
* jupiter:c:\inetpub ====="SET" - creates set.txt
* file and sends all computer system
* jupiter:c:\inetpub ==== environment information
* to C:\set.txt file
* jupiter:c:\inetpub ======END OF BATCH FILE====
Example backup script on UNIX
This example script on UNIX locks a ClearCase version object base (VOB), performs the
backup, and then unlocks the VOB.
#!/bin/sh
# export the SHELL that we are going to use
SHELL=/bin/sh
export SHELL
# export the correct PATH so that all the required binaries can be
found
case $0 in
/* ) PATH=/usr/atria/bin:/bin:/usr/bin:`/bin/dirname $0`
c=`/bin/basename $0`
;;
* )PATH=/usr/atria/bin:/bin:/usr/bin:/usr/sbin
c=$0
;;
esac
export PATH
400
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
# These are the valid statuses that save reports upon completion of
the backup
statuses="
failed.
abandoned.
succeeded.
completed savetime=
"
# Perform the PRECMD (Lock VOB)
/usr/atria/bin/cleartool setview -exec "/usr/atria/bin/cleartoollock c \
‘VOB backups in progress’ -vob /cm_data/mis_dev" magic_view >
/tmp/voblock.log 2>&1
# Perform backup on client
save "$@" > /tmp/saveout$$ 2>&1
# cat out the save output
cat /tmp/saveout$$
# search for backup status in output reported by save
for i in ${statuses}; do
result=`grep "${i}" /tmp/saveout$$`
if [$? != 0]; then
echo ${result}
fi
done
# Perform the POSTCMD (Unlock VOB)
/usr/atria/bin/cleartool setview -exec "/usr/atria/bin/
cleartoolunlock -vob
/cm_data/mis_dev" \
magic_view > /tmp/vobunlock.log 2>&
# exit gracefully out of the shell script
exit 0
Controlling exit status reporting for a custom backup script
Use the Job control attribute on the Apps & Modules tab of the Client Properties dialog
box for a Client resource to control how end of job and exit status messages are
determined for a custom backup script.
To access the Job control attribute, select View > Diagnostic Mode in the Administration
interface to enable diagnostic mode view. A checkmark next to Diagnostic Mode in the
View menu indicates that diagnostic mode view is enabled.
There are three checkboxes for the Job control attribute:
l
end on job end
l
end on process exit
l
use process exit code
The following table provides details on exit status reporting depending on the selection
of one or more of the checkboxes.
Table 73 Job control attribute selections
Selections
Description
No selections
The nsrpolicy and nsrjobd programs determine the success or failure of
(default behavior) a custom script based on the completion of the save program (end of job).
The following criteria apply:
l
If the save job completion status is success, then nsrpolicy and
nsrjobd report that the custom backup job succeeded.
l
If the save job completion status is failure, then nsrpolicy and
nsrjobd report that the custom backup job failed.
Creating a custom backup script
401
Backing Up Data
Table 73 Job control attribute selections (continued)
Selections
Description
l
If no completion status is received, the custom job output is examined
for completed savetime=savetime lines. If found and the
savetime is a value other than 0 (zero), then the custom backup job
is considered to have succeeded. If the value is 0, then the custom
backup job is considered to have failed.
The exit code of the custom script process is not taken into
consideration.
end on job end
only
A backup job is considered to be ended as soon as an end job message is
received from the save command.
Select this option when you do not want to wait for the
postprocessing commands of the script to end.
end on process
exit only
A backup job is considered to be ended as soon as the started process exits.
Background processes started by the backup command could still be running
on the client.
Use this option when you want the custom script to start
background processes and you do not want savegrp or
nsrjobd to wait for the processes to complete.
use process exit Only the process exit code is used to determine the success or failure of the
job. An exit code of 0 indicates success. Otherwise, the job is reported as
code only
failed.
Use this option when you want the script postprocessing command status to
have an impact on the status of the
save backup command without having
to unset the NSR_STD_MSG_FD environment variable.
If the script invokes more than one NetWorker backup
command such as save, then you
must still unset the NSR_STD_MSG_FD environment
variable.
Both end on job
end and
end on process
exit
Both end on job
end and
Either event can trigger the end of a job.
If an end job message is received before the process exits, then the exit
status provided by the end job message is used to determine the success or
use process exit failure of the job.
code
402
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Customizing backups with the pre and post commands
Customize backup behavior by running preprocessing and postprocessing commands
only once during the client backup, instead of once for each save set.
Preprocessing and postprocessing scripts can be useful if the client is running a
database or another program that should be stopped before the client is backed up, and
then restarted after the backup has completed.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. Right-click the Client resource and select Modify Client Properties.
The Client Properties dialog box appears.
4. On the Apps and Modules tab, in the Pre command attribute, specify the name of the
script file that you require NetWorker to run before a backup.
Note
Do not specify the path to the file.
5. Optionally, in the Post command attribute, specify the name of the script file that you
require NetWorker to run after a backup of all the save sets for the client completes.
Note
Do not specify the path to the file.
6. Click OK.
Results
The customized instructions are applied the next time that the client is backed up.
Client resources
A client is both a physical computer with NetWorker client software installed on it and a
NetWorker resource that specifies a set of files and directories to be in a scheduled
backup. A Client resource also controls backup settings for the client, such as the save
sets to back up for the client, the groups to which the client belongs, and whether to
automatically restart failed backups for the client.
You can configure multiple Client resources for a single NetWorker client computer,
although clients with the same save set cannot be in the same group. You might want to
create multiple Client resources for a single client computer in the following scenarios:
l
To segregate different types of backup data, such as application data and operating
system files. For instance, to back up the accounting data on a computer on a
different schedule than the operating system files, create two client resources for the
computer: one for accounting data and another for operating system data.
l
To back up large client file systems more efficiently. For instance, you could create
separate client resources for each file system on a computer and back them up on
different schedules.
You can create a Client resource either by using the Client Backup Configuration wizard
or the Client Properties dialog box.
Customizing backups with the pre and post commands
403
Backing Up Data
You can configure NetWorker clients to use a unique network interface on the NetWorker
server and storage node for backup and recovery operations. Using multihomed
systems on page 773 provides more information.
Creating a Client resource with the Client Properties dialog box
The following procedure provides the basic steps to create a client resource for
scheduled backups. Additional configuration of the Client resource may be necessary for
clients such as VMware or NAS device clients, or to take advantage of product features
such as probe-based backups or archiving.
Before you begin
l
Install the NetWorker client software on the client computer.
l
(Optional) Configure directives to control how the NetWorker server processes files
and directories during backup and recovery. For example, you can create a directive
to skip certain directories or file types, to compress backup data, or to encrypt
backup data. Directives on page 323 provides more information.
l
(Optional) To view advanced options in the Client Properties dialog box, select View >
Diagnostic Mode in the Administration window. Advanced options are not discussed
in this procedure.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. From the File menu, select New.
The Client Properties dialog box appears, starting with the General tab.
4. In the Name box, type the hostname of the client computer.
5. (Optional) In the Comment box, type a description of the client.
If multiple Client resources are being set up for the same host, type a comment that
distinguishes the Client resources.
6. In the Tag box, type one or more tags to identify this Client resource for the creation of
dynamic client groups for data protection policies.
Place each entry on a separate line.
7. To allow a failed backup operation to restart at a known good point before the point of
failure during the backup, select the Checkpoint enabled checkbox.
Configuring checkpoint restart backups on page 386 provides more information on
the requirements for checkpoint restart.
8. From the Directive list, select a directive to control how the NetWorker server
processes files and directories during backup and recovery.
9. In the Save set box, type the name of the files or directories to back up, or click the
Browse button to browse and select file system objects.
404
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Note
To avoid the over consumption of memory, NetWorker limits the number of files that
you can view when you browse a directory that contain a large number of files, for
example, 200,000 files. When NetWorker determines that displaying the number of
files will exhaust memory resources, NetWorker will display a partial list of the files
and a message similar to the following appears: Expanding this directory
has stopped because the result has too many entries
When you manually specify the save set value, place multiple entries on separate
lines. For example, to back up a log file directory that is named C:\log and all the
data under the directory that is named D:\accounting, type the following entries:
C:\log
D:\accounting
Follow the guidelines in Mapped drives on page 373 to back up mapped drives on
Windows systems.
To back up all client data, type ALL. For Windows operating systems, the ALL save set
includes the DISASTER_RECOVERY:\ save set, which includes the WINDOWS
ROLES AND FEATURES save set.
NOTICE
Some operating systems contain files and directories that should not be backed up.
Use directives to ensure that these files and directories are not backed up.
Save sets on page 292 provides more information on defining the save sets for a
Client resource.
10. Select the other tabs in the Client Properties dialog box and configure options as
necessary.
11. Click OK.
Results
Verify that the client is enabled for scheduled backups by ensuring that a check mark
appears next to the client in the Scheduled backup column in the right pane for the
client.
Editing a Client resource
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. In the right pane, perform one of the following tasks:
l
To modify multiple attributes in a single configuration resource by using the Client
Properties window, right-click the staging configuration and select Modify Client
Properties.
l
To modify a specific attribute that appears in the resource window, place the
mouse in the cell that contains the attribute that you want to change, then rightclick. The menu displays an option to edit the attribute. For example, to modify the
Comment attribute, right-click the resource in the Comment cell and select Edit
Comment.
Editing a Client resource
405
Backing Up Data
Note
To modify a specific attribute for multiple resources, press and hold the Ctrl key,
select each resource, and then right-click in the cell that contains the attribute that
you want to change. The menu displays an option to edit the attribute.
4. Edit the attributes of the Client resource.
5. Click OK.
Client priority
The Priority attribute on the Globals (1 of 2) tab of the Client Properties dialog box for a
Client resource enables you to control the order in which the NetWorker server contacts
clients for backup.
The attribute can contain a value between 1 and 1,000. The lower the value, the higher
the priority.
You must select View > Diagnostic Mode in the Administration interface to access the
Priority attribute in the Client Properties dialog box.
During a backup operation, the NetWorker server contacts the client with the lowest
priority value first. If you do not specify a priority for the Client resources, then the backup
order is random.
While the Priority attribute specifies the order of client contact, many variables affect the
order in which clients complete their backups. For example:
l
The backup operation on a client does not begin until the worklists for each of the
save sets on the client are complete.
l
The amount of work can vary greatly from one client to the next.
l
If a client stops responding and times out, then the backup operation puts the client
backup at the end of the backup order list.
The only way to guarantee that the backup of one client occurs before the backup of
another client is to configure the data protection policies for the clients to start at
different times.
Copying a Client resource
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, select Clients.
3. In the right pane, right-click the Client resource and select Copy.
The Create Client dialog box appears with the same attributes as the original client
except for the client name.
4. Type the hostname of the client in the Name box.
5. (Optional) Edit other attributes for the Client resource.
6. Click OK.
406
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Changing the hostname of a client
To change the hostname of a client, you must delete the Client resource, rename the
directory with the client file index for the client, and then create a Client resource with the
new hostname and the original client ID.
If you create the new Client resource but do not use the client ID of the original NetWorker
host:
l
The NetWorker server considers the new hostname to be a new NetWorker host.
l
The NetWorker server assigns the new hostname a new client ID.
l
To recover data, you must perform a directed recovery from the original hostname to
the new hostname.
l
You cannot perform a browsable recovery, only a save set recovery.
Use the nsrclientfix command to analyze the media database and identify client ID
inconsistencies. To resolve client ID issues, use the nsrclientfix command to merge
information about multiple clients in the media database and resource database into one
client resource with the original client ID. The following KB articles on the EMC Support
website provide more information about using the nsrclientfix command:
l
For NetWorker server client ID issues: 000185727
l
For NetWorker client client ID issues: 000193911
Procedure
1. Record the client ID of the original Client resource:
a. Enable diagnostic mode view by selecting View > Diagnostic Mode in the
Administration window.
b. In the Administration window, click Protection.
c. In the expanded left pane, select Clients.
d. In the right pane, right-click the Client resource and select Modify Client
Properties.
The Client Properties dialog box appears.
e. Select the Globals (1 of 2) tab.
f. Record the value in the Client ID attribute.
g. Click Cancel.
2. Delete the Client resource:
a. Right-click the resource, and select Delete.
A confirmation message appears.
b. Click Yes.
3. Stop all the NetWorker services on the NetWorker server.
4. On the NetWorker server, rename the client file index directory for this client from
old_client_name.domain.com to new_client_name.domain.com.
The default location for the client file index is NetWorker_install_path\index
\client_name.domain.com on Windows and /nsr/index/
client_name.domain.com on UNIX/Linux.
Changing the hostname of a client
407
Backing Up Data
5. Restart the NetWorker services on the NetWorker server.
6. Create a Client resource with the new hostname and the original client ID.
Deleting a Client resource
When you delete a Client resource, the NetWorker server can no longer back up the client
computer. The backup history for the client remains in the client file index and media
database until the entries are removed. You can still access and recover backup data for
the client directly from the volume that contains the data by using the scanner
command.
If you create a Client resource to re-create the deleted client, specify the same hostname
for the client. The NetWorker server recalls and uses the original client ID for the
hostname.
Procedure
1. In the Administration window, click Protection.
2. In the expanded left pane, click Clients.
3. In the right pane, right-click the Client resource and select Delete.
A confirmation message appears.
4. Click Yes.
Manual backups
Manual backups enable users to make quick backups of a few files from the client host.
When you perform a client-initiated or manual backup, by default NetWorker backs up the
data to a volume assigned to the Default pool on the NetWorker server. The retention
policy that is assigned to the data is one year, and the level is manual.
Perform manual backups on Windows by using the NetWorker User program. Perform
manual backups on UNIX and Linux only from the command line.
Performing a manual backup on Windows
Before you begin
Create a local directive on the client computer to exclude local file type devices from
manual backups with the NetWorker User program:
1. Start the NetWorker User program.
2. From the Options menu, select Local Backup Directives.
3. Clear the checkbox for the local file type device.
4. From the File menu, select Save Directive.
NetWorker User local directives on page 329 provides more information on local
directives.
Note
You cannot perform data deduplication during backups with the NetWorker User program.
You must perform scheduled backups or manual backups from the command line to
perform data deduplication during the backup.
408
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
Procedure
1. In the NetWorker User program, click Backup.
The Backup window appears.
2. Select the data to back up.
To back up critical volumes, UEFI, the system reserved partition, and WINDOWS
ROLES AND FEATURES for disaster recovery purposes, select the
DISASTER_RECOVERY save set.
3. Click Start.
The Backup Status dialog box displays the progress of the backup. When the backup
finishes, a Backup completion time message appears.
If the backup fails due to a problem with VSS or a writer, an error message appears.
Use the Windows Event Viewer to examine the event logs for more information. VSS
backup error messages are also written to the NetWorker log file.
The NetWorker log file in \install_path\logs\networkr.raw contains a
record of every file that was part of an attempted manual backup from the NetWorker
User program. This file is overwritten with the next manual backup. To save the
information in the file, rename the file or export the information by using the
nsr_render_log program.
NOTICE
Certain types of corrupt files or errors on computer disk volumes are not detected.
NetWorker might back up this corrupt data. To avoid this situation, run diagnostic
programs regularly to correct disk volume errors.
Including Windows BMR in manual backups
When you use the NetWorker User program to back up a host, to ensure the backup
operation will backup all of the data on the host, select Computer in the Backup window.
If you only select the DISASTER_RECOVERY:\ save set, then the NetWorker User program
automatically selects the critical volumes and WINDOWS ROLES AND FEATURES save sets.
Note
When you use the NetWorker User program or the save command to perform a manual
backup, NetWorker performs the backup operation as a single backup stream. To multistream the backup operation, run a scheduled group backup.
Backing Up Data on page 333 provides more information about manual backups.
Performing a manual backup from the command prompt
Perform a manual backup from the command prompt by using the save command.
For example, to back up myfile to the jupiterserver, type:
save -s jupiter myfile
If you do not specify the -s option with the save command, the files are backed up to
the NetWorker server that is alphabetically listed first in the /nsr/res/servers file on
the client computer.
Performing a manual backup from the command prompt
409
Backing Up Data
The EMC NetWorker Command Reference Guide and the UNIX man pages provide
information about save.
BTRFS backups
NetWorker support BTRFS volume backups. When you specify a BTRFS volume or subvolume save set, NetWorker performs a recursive back up of the directory tree that you
specified with the save command. When NetWorker encounters a sub-directory that has
a sub-volume ID that differs from the parent sub-volume ID, NetWorker will not back up
the contents of the subdirectory, unless you specify the -x option with the save
command.
Performing a manual backup on Mac OS X
To perform a manual backup on a Mac OS X client, use the save command in a Terminal
session.
For example:
$ save "file_or_directory_to_back_up" -s NetWorker_server
If you do not specify the -s NetWorker_server option, the save command contacts the
NetWorker server that is defined in the /nsr/res/servers file. The NetWorker
Command Reference Guide provides more information about the save command.
Troubleshooting manual backups
This section describes how to troubleshoot error messages that might appear during a
manual or client-initiated backup
Could not create log file: Permission denied
This message appears when a non-root user performs a manual client direct-enabled
backup to a CloudBoost device but the user account does not have write access to
the /nsr/logs/cloudboost directory. To resolve this issue, configure the following
environment variables to define an alternate location for the log files, where the non-root
user has write access.
export CB_CACHE_LOCATION=cache_dir
export CB_LOG_DIR_LOCATION=log_dir
where:
cache_dir is the directory that stores backup cache files.
l
log_dir is the directory that stores for the backup log files.
l
Verifying backup data
You can use the NetWorker User program on Windows clients to ensure that backup data
on the NetWorker server matches the data on the local disk. This verification process
enables you to test whether you can successfully recover the data.
During the verification, the file types, file change times, file sizes, and file contents are
compared. Other system attributes, such as read-only, archive, hidden, system,
compressed, and file access control list (ACL), are not part of the verification.
The NetWorker server alerts you to any changes that have occurred to the data since the
backup. Verification also determines whether a hardware failure kept the NetWorker
server from completing a successful backup.
410
EMC NetWorker 9.0.x Administration Guide
Backing Up Data
NOTICE
This feature is not available on UNIX clients.
Procedure
1. Log in as an administrator on the Windows client computer.
2. Open the NetWorker User program.
3. From the Operation menu, select Verify Files.
4. Select the data items to verify.
5. Click Start.
6. Monitor the data verification progress in the Verify Files Status dialog box.
After the verification is complete, the Verify Status dialog box shows any data
discrepancies.
Verifying backup data
411
Backing Up Data
412
EMC NetWorker 9.0.x Administration Guide
CHAPTER 7
Cloning, Staging, and Archiving
This chapter contains the following topics:
l
l
l
l
l
Cloning, staging, and archiving........................................................................... 414
Benefits of cloning and staging........................................................................... 414
Cloning save sets and volumes........................................................................... 415
Staging save sets................................................................................................ 428
Archiving data..................................................................................................... 434
Cloning, Staging, and Archiving
413
Cloning, Staging, and Archiving
Cloning, staging, and archiving
The storage device that you use for the initial backup is often a compromise between a
number of factors, including location, availability, capacity, speed, and cost. As a result,
the backup data on the initial storage device is unlikely to be on the ideal or best storage
for the entire duration of the retention period.
NetWorker provides you with three ways to manage data for long term storage.
l
Cloning—The clone process allow you to store data securely offsite, transfer of data
from one location to another, and verification of backups. You can clone volumes and
save sets. The clone process copies existing save sets from a volume in one device to
a volume in a different device. The target volume can be the same media type or a
different media type than the original.
l
Staging—The stage process uses the clone process to transfer backup data from one
an AFTD or file type device to another medium, then removes the data from the
original location.
l
Archiving—The archive process captures files or directories as they exist at a specific
time, and writes the data to archive storage volumes. NetWorker does not
automatically recycle the archive volumes. After the archive process completes, you
can delete or groom the original files from the disk to conserve space.
Benefits of cloning and staging
Cloning and staging enables you to use storage devices more effectively by moving data
between different types of devices. You can copy the data that are stored on local tape
devices to other devices in remote locations without an impact to the initial backup
performance. You can copy backups from disk devices to tape device to facilitate offsite
or long term storage. When you move data from disk to tape, you can use the storage
capacity more effectively. When you use of a deduplicated disk, NetWorker can reclaim
the initial storage space for new backups.
NetWorker can only perform a clone operation after a successful backup, which provides
the following benefits:
414
l
Allows the backup process to complete at maximum performance without any impact
to speed due to multiple write acknowledgments, delays, or retries on one or more
devices. A clone operation limits the performance impact on a client, while providing
data protection as quickly as possible.
l
Ensures that a successful backup, that the data is valid, and that the clone operation
completes successfully.
l
Ensures that the storage requirements have been determined, and that the storage is
made available.
l
Allows you to schedule and rank the clone operation outside of the backup window,
when resources are less constrained.
l
Reduces the load on the backup infrastructure.
l
Allows you to easily start recoveries because the backup operation has already
completed.
EMC NetWorker 9.0.x Administration Guide
Cloning, Staging, and Archiving
Note
You cannot use the NetWorker software to create an instant clone by writing to two
devices simultaneously. This operation is also referred to as parallel cloning, twinning, or
inline copy. Where parallel cloning or twinning is required, consider using the NetWorker
cloning feature. Using cloning helps ensure that the initial backup completes
successfully. Additional data protection can also be implemented by using the best
devices and bandwidth available for the backup environment.
Cloning save sets and volumes
The cloning operation reads save sets from a volume within a backup or archive pool and
writes the data to a volume in a clone pool. You can clone save sets multiple times, but
NetWorker must write each clone to a separate volume.
When you clone backup data, the clone operation validate that NetWorker can read the
original backup data successfully in the media database and on the media volume, which
provides additional assurance that you can recover the data.
To schedule save set cloning, configure Data Protection Policies and a clone action. The
Data Protection Policies chapter provides detailed information about creating a clone
action. To manually clone backup save sets, archive save sets, or volumes from the
command prompt, use the nsrclone command.
Deciding when to clone
The need to clone data is normally driven by a requirement for additional protection, or
the need to move data to a specific media type or location. In both cases, the priority is to
secure the data as quickly as possible.
There is a high probability that any restore request within the first 48 hours is due to local
failure or corruption and that the original backup copy is the most likely source for that
recovery. If there is a local disaster recovery or site loss, the recovery actions and
objectives are likely to be very different. Selected systems and services are assigned
specific priorities, recovery point objective (RPO) values, and recovery time objective
(RTO) values.
Note
Do not schedule more than 30 clone sessions to start simultaneously. Scheduling 30 or
more clone sessions to occur simultaneously may result in cloning sessions that time out
or are incomplete.
Clone retention
NetWorker supports the ability to define a retention time for a clone save set that differs
from the original save set.
The following attributes determine the retention time that NetWorker assigns to the
original save set and clone save set.
l
Retention policy attribute that is defined for the Client resource.
l
Retention policy attribute that is defined for the Action resource that created the save
set.
l
Retention policy attribute that is defined for the Pool resource that contains the save
set.
Cloning save sets and volumes
415
Cloning, Staging, and Archiving
Note
This read-only attribute appears on the Configuration tab of the Pool resource, when
Diagnostic mode is enabled in the NetWorker Administration window. This is a 8.2.x
and earlier attribute, which you cannot modify.
EMC recommends that you define the retention policy for data in the Action resource. If
you define the retention policy for save sets in multiple resources, you might experience
unexpected save set expirations.
Cloning requirements and considerations
Review this section before you configure a clone action or perform a manual clone
operation.
Device requirements
NetWorker requires two or more storage devices to perform a clone operation. One device
contains the volume with the original data and one device contains the volume to which
NetWorker writes the clone data. The clone data must reside on a volume that differs from
the original volume. Each clone volume can only contain one instance of a cloned save
set, even if the clone operation did not complete successfully. For example, if you want to
create three clone copies of a save set, NetWorker must write each clone save set to a
separate volume. As a result, you would need three separate volumes.
When using a tape library with multiple devices, the NetWorker server automatically
mounts the volumes that are required to complete the clone operation. When you use
standalone tape devices, you must manually mount the volumes. A message in the Alert
tab of the Monitoring window indicates which volumes to mount.
Often businesses choose devices for the initial backup that is based on speed or cost
requirements. NetWorker supports cloning or staging data to a device type that differs
from the source data volume. A common cloning or staging scenario includes using an
AFTD for the initial backup to gain speed and versatility benefits, then to clone or stage
the data to tape devices or dedpulication devices. This scenario allows for an extended
retention period without increasing disk space requirements. The use of deduplication
can also provide efficient use of storage. Cloning to or from deduplication devices can
ensure that these devices are used effectively. If the clone operation includes save sets
from different devices, and you want all the save sets to be written to the same volume,
include only one volume in the clone target pool.
Note
EMC recommends that you do not write NDMP and non-NDMP data to the same clone
volume because the number of file marks and positioning on the device differs for both
data types.
Cloning multiplexed backups
You can clone multiplexed save sets. NetWorker writes the clone copies of multiplexed
save sets as a single contiguous data stream on the target media (demultiplexed). When
you recover from a multiplexed save set, read and recovery times increase as a result of
the time NetWorker spends reading and locating the data. The process of demultiplexing
save sets by the clone operation allowed you to read and recover data faster from a clone
save set than a backup save set.
When you clone multiplex save sets, you can only clone one save set to the same target
volume simultaneously. However, if the save sets have separate target volumes, you can
start multiple clone sessions simultaneously from the same source.
416
EMC NetWorker 9.0.x Administration Guide
Cloning, Staging, and Archiving
Save set spanning
Some devices support save set spanning across multiple volumes. When NetWorker
clones a save set, the clone copy might start on one volume but continue on one or more
additional volumes.
When using devices that support save set spanning, ensure that you:
l
Identify save sets that span multiple volumes.
l
Keep the number of continued save sets is kept to a minimum.
l
Use separate pools and larger or alternative devices.
l
l
Use the EMC Data Domain® backup-to-disk and optimized cloning feature with Data
Domain devices.
Plan ahead to ensure that the volumes are available and that they are read in the
best sequence.
Note
You can create a custom, scripted solution that uses the nsrclone command to
manage save set spanning.
Recovery scenarios
When you clone data, you provide the datazone with an alternative data recovery source ,
which helps to protect against media loss or corruption. However, if the media is located
in one of the following locations, then the second copy of the data is still vulnerable to
major disasters that can affect the entire site:
l
On the same tape library as the original data volume.
l
On a deduplication device within the same data center, in a Data Domain
environment.
l
In an onsite safe.
Sometimes, you may require more copies of a save set to ensure that all the recovery
scenarios are accommodated while maintaining the expected return on investment. This
requirement may not apply to all clients and all data, or be practical. However, consider
the reasons for cloning to ensure that the cloning strategy meets requirements and
expectations.
Changing the target device, or moving tapes to a second location after the cloning
operation completes, can provide additional protection.
Retention considerations
A Retention policy value applies to every type of save set. The retention policy value
determines the length of time that the data remains available for recovery in the
NetWorker media database and the client file index. You can specify a retention policy
value for the clone save set that differs from the value that is defined for the original save
set. When the retention policy differs for the original and clone save set, you can expire
the original save set and reclaim the space on the source AFTD but maintain the data on a
clone volume for future recoveries.
Note
The retention setting impacts the amount of disk space that is required by the NetWorker
server. The recovery procedure is likely to be different if retention has expired. The
retention setting should be equal to or greater than the client or data requirements, and
allow for the expected recovery conditions.
Cloning requirements and considerations
417
Cloning, Staging, and Archiving
Cloning example
In this example, a backup of a client with three data drives creates three save sets. These
save sets are stored on a volume that is accessible through Storage Node A. Once a
cloning action occurs, the copies of these save sets are sent to a clone pool on Storage
Node B.
In this figure:
l
A client performs a backup of three data drives to Storage Node A. NetWorker creates
three save sets, one save set for each data drive.
l
A clone operation reads the data from the volumes on Storage Node A, and then
copies the save sets to Storage Node B.
Figure 44 Cloning example
Cloning with tape devices
There are a number of reasons why tape devices are used as part of the cloning process:
418
l
In cases where tape is used as a secondary storage tier where selected data is cloned
to tape for offsite storage or for extended data retention periods. This allows disk
devices to be used for the initial backup where their speed and flexibility can be most
effectively used for fast backup and recovery performance.
l
In cases where tape is used as the primary backup media, there are still benefits in
creating clone copies, including:
n
Secondary copy at different location or for offsite storage.
n
Data validation.
EMC NetWorker 9.0.x Administration Guide
Cloning, Staging, and Archiving
n
Verification of the ability to read data from the media.
n
Added protection of multiple copies across multiple volumes.
n
De-multiplexing of multiplex backups for faster recovery.
Cloning with tape devices provides two benefits which should be considered for every
clone:
l
Unlike disk-based devices, tape devices read data in a serial format. This means that
while multiplexing is beneficial from a backup streaming perspective, this is not the
case for recovery.
l
If recovery speed is important, the use of clone copies as the source is likely to result
in faster recovery throughput.
Tape clone copies are often the preferred method to read data in a disaster recovery
situation. The ability to acquire, install, and configure a tape unit to read data is often the
first task on a disaster recovery plan.
By creating a copy of the backup on tape, you can eliminate the need for appliances such
as VTLs or disk systems to be in place. This often takes longer to acquire, install, and
configure. However, ensure that the tape copy is a full and complete copy, without the
dependence on other backups or deduplication appliances to complete the restore
operation.
Production storage node cloning of data to physical tape
This section outlines the advantages and disadvantages of cloning data to physical
tapes:
l
The NetWorker software can clone from virtual tape in the disk library through a
production storage node to a SAN-attached tape library to produce copies of save
sets. This operation is a standard NetWorker cloning procedure.
l
For the disk library, a virtual tape drive works in conjunction with a SAN-attached
target tape device to complete the cloning process.
l
Cloning from a production storage node to a second storage node can also be
performed over IP.
Note
Do not use a production storage node to perform cloning operations when the
embedded storage node cloning capability is present.
Advantages
The advantages of cloning data to physical tapes include the following:
l
Cloning can occur with the disk libraries under NetWorker control with standard
NetWorker policy support. Multiple retentions policies for different cloned copies of
data can be used.
l
Cloning can occur at the save set level.
Note
An entire save set can be cloned.
l
Copying can occur from one tape type (virtual) to another tape type (target tape
library), also known as tape conversion.
l
Copying can occur from multiple virtual tapes to a single tape, also known as tape
stacking.
Cloning with tape devices
419
Cloning, Staging, and Archiving
Disadvantages
The disadvantages of cloning data to physical tapes include the following:
l
Requires storage node licenses.
l
Requires maintenance of front-end SAN infrastructure to a target tape library as well
as the virtual tape library.
l
Consumes SAN bandwidth as data must be from virtual tape over the SAN to a target
device on the SAN.
Cloning with file type and AFTD devices
Disk backup devices such as file type devices and advanced file type devices (AFTD) are
ideal for cloning operations because they provide high speed, random access, and
flexibility.
There are differences in the cloning process for file type devices and advanced file type
devices.
l
For file type devices, scheduled and manual cloning begins only after all save sets in
a group have been backed up.
l
For AFTDs, scheduled cloning begins only after all save sets in a group have been
backed up. However, you can begin manually cloning a save set when it has finished
its backup. For example, if there are three save sets (A, B, and C) in a backup, you can
begin manually cloning Save Set A after its backup is complete and while the
backups of Save Sets B and C are in progress. You can only manually clone one save
set at a time. AFTDs allow recoveries during cloning operations (Read(source) or
Write(target)). This assumes that the recover operation is not from the active save set
and that only one clone operation is running at a time.
Often, the disk devices are used as the initial target device for backups, especially in
situations where slower clients are unable to match the speeds that are expected for
modern tape devices. In these situations, the ability to clone or stage data to tape often
provides extended retention and data protection, while maximizing the disk use and
benefits.
Data can remain on the disk devices for short periods, typically 3 to 14 days, which
allows for:
l
Adequate time for immediate and urgent restore operations to occur.
l
Plenty of time to create further copies to tape or other disk-based devices for longer
term retention.
Cloning with EMC Avamar
When you configure NetWorker with EMC Avamar® to deduplicate backup data, the
backup data is stored on an Avamar deduplication node on the Avamar server. The
metadata (hash information) is stored on a NetWorker storage node.
To clone Avamar deduplication backups:
420
l
Configure a clone action to clone the metadata. Cloning this hash metadata is highly
recommended.
l
Configure replication of the backup data from the original Avamar deduplication node
to another Avamar deduplication node. The NetWorker software does not start
replication. A replication host (an Avamar server) must be configured by EMC
Customer Support before a deduplication backup can be replicated. The EMC
NetWorker and EMC Avamar Integration Guide provides more information.
EMC NetWorker 9.0.x Administration Guide
Cloning, Staging, and Archiving
NOTICE
For disaster recovery, you must replicate the client data to another Avamar deduplication
node and clone the metadata. Both the metadata and the client data are required to
recover client backup data.
You can also output the backup data of Avamar deduplication nodes to tape volumes.
Create a second Client resource for the client