Contents

Dell NetWorker 18.1 Software Administration Guide PDF

1 of 894
1 of 894

Summary of Content for Dell NetWorker 18.1 Software Administration Guide PDF

Dell EMC NetWorker Version 18.1

Administration Guide 302-004-416

REV 05

Copyright 1990-2018 Dell Inc. or its subsidiaries. All rights reserved.

Published December, 2018

Dell 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. DELL 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 DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.

Published in the USA.

Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com

2 NetWorker 18.1 Administration Guide

15

17

21

Overview 27 The NetWorker environment...................................................................... 28

NetWorker Components................................................................28 NetWorker services....................................................................................30

Processes on NetWorker hosts ..................................................... 31 Stop and start the NMC Server..................................................... 34 Stop and start a NetWorker Server, Client, or Storage Node........ 36

NetWorker user interfaces......................................................................... 39 NMC user interface....................................................................... 39 NetWorker Administration window................................................ 40 NetWorker client interface............................................................ 40 NetWorker character-based interface............................................41 NetWorker command-line interface............................................... 41 Introduction to the NetWorker Management Web UI..................... 41

Getting Started 43 NetWorker Management Console interface................................................44

Connecting to the Console window............................................... 44 Connecting to the Administration window.................................................. 49

Opening the Administration window.............................................. 49 Administration window.................................................................. 50 Editing multiple resources.............................................................. 51 Drag-and-drop functionality...........................................................51 Multiple library devices and slots................................................... 53 Setting user interaction preferences............................................. 53 Monitoring NetWorker Server activities in the Administration window.......................................................................................... 54

Getting started with a new installation....................................................... 64 Common NetWorker tasks.............................................................64

Backup Target 73 Label templates.......................................................................................... 74

Using label templates.....................................................................74 How the NetWorker server uses volume labels.............................. 74 Preconfigured label templates....................................................... 75 Guidelines for completing Label Template attributes..................... 75 Naming label templates..................................................................78 Working with label templates.........................................................79 Setting up a label template to identify volumes............................. 80

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

CONTENTS

NetWorker 18.1 Administration Guide 3

Media pools.................................................................................................81 Using media pools.......................................................................... 81

Storage nodes............................................................................................ 97 Requirements................................................................................ 97 Licensing....................................................................................... 97 Storage node configuration........................................................... 98 Storage Node Options..................................................................104 Configuring a dedicated storage node..........................................105 Troubleshooting storage nodes.................................................... 105

Disk storage devices................................................................................. 106 Example environment................................................................... 107 Considerations for Client Direct clients........................................ 108 Differences between FTDs, AFTDs, and DD Boost devices........... 110 Device target and max sessions default values and ranges............112 Advanced file type devices............................................................113 DD Boost and Cloud Tier devices..................................................128

Libraries and silos......................................................................................129 Overview of tape device storage.................................................. 129 Support for LTO-4 hardware-based encryption........................... 129 Linux device considerations..........................................................129 Solaris device considerations........................................................ 131 HP-UX device considerations....................................................... 131 AIX device considerations.............................................................134 SCSI and VTL libraries..................................................................134 Silo libraries.................................................................................. 173 NDMP libraries............................................................................. 182 NetWorker hosts with shared libraries..........................................182 Dynamic drive sharing.................................................................. 184

File type devices....................................................................................... 189 FTD capacity issues..................................................................... 190 Full FTD prevention...................................................................... 190

Stand-alone devices..................................................................................190 Autodetecting and configuring a stand-alone tape drive............... 191 Adding a stand-alone device manually...........................................191 Auto Media Management for stand-alone devices........................192 Mounting or unmounting a volume in a stand-alone tape drive..... 193 Labeling and mounting a volume in one operation (stand-alone tape drive)........................................................................................... 193 Labeling volumes without mounting............................................. 194 Mounting uninventoried volumes..................................................195

Labeling volumes.......................................................................................196 Labeling or re-labeling library volumes..........................................196 Verifying the label when a volume is unloaded.............................. 197

Troubleshooting devices and autochangers...............................................197 Additional attributes in the Autochanger resource........................197 Maintenance commands...............................................................197 Autodetected SCSI jukebox option causes server to stop responding................................................................................... 198 Autochanger inventory problems..................................................198 Destination component full messages.......................................... 198 Tapes do not fill to capacity......................................................... 199 Tapes get stuck in drive when labeling tapes on Linux Red Hat platform....................................................................................... 199 Increasing the value of Save Mount Time-out for label operations.... 200 Server cannot access autochanger control port.......................... 200

CONTENTS

4 NetWorker 18.1 Administration Guide

Changing the sleep times required for TZ89 drive types.............. 201 Message displayed when CDI enabled on NDMP or file type device.. 202 Verify firmware for switches and routers.....................................202 Commands issued with nsrjb on a multi-NIC host fail.................. 202 SCSI reserve/release with dynamic drive sharing........................202 Recovering save sets from a VTL on a different NetWorker server... 203

Data Protection Policies 205 Overview of data protection policies........................................................ 206 Designing data protection policies............................................................ 207

Default data protection policies................................................... 208 Overview of configuring a new data protection policy................. 209 NetWorker resource considerations............................................. 210 Strategies for traditional backups................................................ 210 Strategies for server backup and maintenance............................ 236 Strategies for cloning................................................................... 241

Policy Notifications.................................................................................. 266 Monitoring policy activity......................................................................... 267

Monitoring cloning.......................................................................268 Policy log files.......................................................................................... 269 Starting, stopping, and restarting workflows in NMC................................271 Starting actions in a workflow for an individual client................................ 271 Modifying data protection Policy resources..............................................272

Policies........................................................................................ 272 Workflows....................................................................................273 Protection groups........................................................................ 281 Actions........................................................................................ 282

Managing policies from the command prompt.......................................... 285 Creating Data Protection Policy resources from a command prompt .................................................................................................... 286 Creating Action resources from a command prompt....................287 Starting, stopping, and restarting workflows from a command prompt.........................................................................................288 Displaying Data Protection Policy resource configurations..........290

Troubleshooting policies........................................................................... 293

Backup Options 297 Overview of resources that support backups........................................... 298 Save sets..................................................................................................298

The ALL save set......................................................................... 299 Backup levels............................................................................................ 301

Comparing backup levels............................................................. 302 Backup levels and data recovery requirements............................ 303 Backup levels for the online indexes............................................ 304 Synthetic full backups................................................................. 304 Virtual synthetic full backups........................................................ 311

Backup scheduling.................................................................................... 314 Scheduling backup cycles.............................................................314 Considerations for scheduling backups........................................ 315 Methods for scheduling backups.................................................. 317

Backup retention...................................................................................... 322 Methods for setting retention......................................................323

Chapter 4

Chapter 5

CONTENTS

NetWorker 18.1 Administration Guide 5

Assigning a retention policy to a Client resource..........................324 Editing retention for a save set....................................................325

General backup considerations................................................................. 326 Renamed directories....................................................................326 Raw partitions............................................................................. 326 Access control lists...................................................................... 327 Client parallelism and parallel save streams..................................327 Maximum path and save set length..............................................330 Open files..................................................................................... 331 Data deduplication........................................................................331

Directives................................................................................................. 332 Types of directives...................................................................... 332 Format of directive statements................................................... 333 Global directives.......................................................................... 337 NetWorker User local directives...................................................341 Creating local directives.............................................................. 342

Backing Up Data 345 Configuring a Client resource for backups on Windows hosts ..................346

Windows backup considerations.................................................. 346 Windows file system backups...................................................... 357 Windows Bare Metal Recovery.................................................... 363 Creating a Client resource with the Client Backup Configuration wizard.......................................................................................... 381 Mapped drives............................................................................. 387

Configuring a Client resource for backups on UNIX hosts ....................... 388 UNIX/Linux backup considerations..............................................388 Creating a Client resource with the Client Backup Configuration wizard..........................................................................................389 Supported save set configurations for UNIX hosts...................... 393

Configuring a Client resource for backups on Mac OS X hosts ................396 Mac OS X backup considerations................................................ 396 Creating a Client resource with the Client Backup Configuration wizard..........................................................................................396 Assigning directives to Mac OS X clients.....................................400 Configuring Open Directory database backups............................400

Sending client data to AFTD or Data Domain devices only........................ 401 Non-ASCII files and directories.................................................................402 Configuring checkpoint restart backups................................................... 402

About partial save sets................................................................ 403 Partial saveset cloning and scanning............................................403 Checkpoint restart requirements................................................. 403 Configuring checkpoint restart.................................................... 404 Restarting checkpoint-enabled backups......................................405 Recovering data from partial save sets........................................406

Probe-based backups............................................................................... 407 Encryption................................................................................................408

AES Encryption........................................................................... 408 In-flight encryption...................................................................... 410

Compression..............................................................................................411 Configuring compression for scheduled backups.......................... 411 Configuring compression for manual backups............................... 411

Configuring Client Direct backups.............................................................412 Requirements for Client Direct backups....................................... 412 Configuring Client Direct backups................................................ 413

Chapter 6

CONTENTS

6 NetWorker 18.1 Administration Guide

Backup command customization............................................................... 414 Creating a custom backup script.................................................. 414 Customizing backups with the pre and post commands...............420

Client resources........................................................................................ 421 Create a Client resource with the Client Properties dialog box.... 422 Editing a Client resource..............................................................423 Copying a Client resource............................................................424 Changing the hostname of a client.............................................. 425 Deleting a Client resource............................................................426

Manual backups........................................................................................426 Performing a manual backup on Windows....................................426 Performing a manual backup from the command prompt.............427 Performing a manual backup on Mac OS X.................................. 428 Troubleshooting manual backups.................................................428

Verifying backup data...............................................................................428

Cloning, Staging, and Archiving 431 Cloning, staging, and archiving................................................................. 432 Benefits of cloning and staging.................................................................432 Cloning save sets and volumes................................................................. 433

Deciding when to clone................................................................433 Clone retention............................................................................433 Cloning requirements and considerations.................................... 434 Cloning example.......................................................................... 436 Cloning with tape devices............................................................ 436 Cloning with file type and AFTD devices......................................438 Cloning with Avamar....................................................................439 Cloning with Data Domain (DD Boost).........................................439 Controlling storage node selection for cloning............................. 439 Recover Pipe to Save ................................................................. 443 Cloning save sets from a command prompt................................. 444

Staging save sets..................................................................................... 448 Staging bootstrap backups.......................................................... 449 Creating a staging resource.........................................................449 Editing staging configurations..................................................... 452 Copying a Staging resource.........................................................452 Deleting a staging policy.............................................................. 453 Manual staging from the command prompt................................. 453 Common NetWorker staging commands and issues.....................454

Archiving data.......................................................................................... 455 Storage of archived data............................................................. 456 Enabling archiving........................................................................457 Archiving data from Windows...................................................... 457 Archiving data from UNIX............................................................458 Recovering archived data............................................................ 458 Troubleshooting NetWorker archiving and retrieval.....................460

Backup Data Management 463 Overview of backup data management.....................................................464 Viewing volume and save set details......................................................... 464

Viewing disk volume details......................................................... 464 Viewing tape volume details.........................................................466 Viewing save set details for a volume...........................................467 Viewing save set details from a search......................................... 471

Chapter 7

Chapter 8

CONTENTS

NetWorker 18.1 Administration Guide 7

Managing volumes.................................................................................... 475 Changing the volume mode..........................................................475 Changing the volume recycle policy.............................................476 Marking a tape volume as full for offsite storage......................... 476 Removing volumes from the media database and online indexes..477

Changing save set status..........................................................................478 Changing the save set retention time....................................................... 478 Removing expired save sets......................................................................479

Save set management on tape devices........................................480

Recovery 481 Recovering data....................................................................................... 482 Recovery roadmap....................................................................................482 Planning and preparing to recovering data............................................... 483

Gathering key information........................................................... 483 Prerequisites for recovering a NetWorker client or storage node.... 484 Downloading the NetWorker software and documentation..........484 Reinstalling the NetWorker storage node.................................... 484 Optional, resetting the autochanger............................................ 485

NetWorker recovery overview..................................................................485 Recovery types........................................................................................ 486

Directed recoveries..................................................................... 486 Local recoveries.......................................................................... 490

Recover programs.................................................................................... 490 Using the NetWorker User program............................................. 491 Using the NetWorker Recovery program......................................491 Using the Recovery Wizard.......................................................... 491 Using the recover command........................................................ 497 Scanner recovery.........................................................................497

Recovering the data................................................................................. 497 Determining the volume for recovering cloned data.....................497 Recovering access control list files..............................................499 Browsable recovery..................................................................... 499 Save set recovery........................................................................ 512 Using the scanner program to recover data..................................517 VSS File Level Recovery.............................................................. 519

Recovering deduplication data.................................................................. 519 vProxy recovery in NMC...........................................................................519

Entering management credentials for the Data Domain resource (instant recovery and User mode file-level restore only)..............519 Domain user setup for file-level recovery in the NMC Recovery wizard.......................................................................................... 521 Recovering a virtual machine using the NMC Recovery wizard... 522

NMC function to collect vProxy log bundle information........................... 540 Recovering file system data on Windows.................................................. 541

Recovering Windows volume mount points.................................. 541 Recovering Windows DHCP and WINS databases....................... 542 Recovering DFS...........................................................................542

Recovering data on OS-X clients..............................................................544 Recovering files and directories from the command prompt........544 Recovering files and directories by using the NetWorker Recover GUI.............................................................................................. 544

Recovering client files on a different NetWorker server........................... 550 Recover the NMC Server database.......................................................... 552

Chapter 9

CONTENTS

8 NetWorker 18.1 Administration Guide

Prepare for an NMC Server recovery.......................................... 552 Recovering the NMC Server........................................................552

Special recoveries on Windows hosts 555 Special windows recoveries Restoring a Windows Domain Controller host.... 556

Active Directory restore information........................................... 556 Selecting a restore method......................................................... 556 Performing a non-authoritative AD restore on Windows Server 2008, 2008 R2, 2012 and 2012 R2............................................... 557 Performing an authoritative AD restore on Windows Server 2008, 2008 R2, 2012 and 2012 R2......................................................... 557

Recovering with Windows BMR............................................................... 558 Overview of Windows Bare Metal Recovery (BMR).................... 558 Requirements for Windows BMR backup and restore..................563 Windows BMR limitations and considerations..............................564 Performing a Windows BMR to physical or virtual computers...... 571 Online recovery of Active Directory, DFSR, or Cluster services...588

Reporting NetWorker Datazone Activities 589 Enterprise data reporting......................................................................... 590

Enabling or disabling the gathering of report data....................... 590 Data retention and expiration policies.......................................... 591 Restricted report views............................................................... 592 Report categories........................................................................593 Legacy report categories.............................................................593 Report modes and types..............................................................594 Preconfigured reports..................................................................601 Customizing and displaying report output....................................627 Customizing and saving reports...................................................630 Sharing a report...........................................................................632 Command line reporting...............................................................633

Reporting policy status and backup job status..........................................634 Policy completion and failure notifications...................................634 Querying the job status............................................................... 635

Reporting recover job status.................................................................... 654 Using nsrrecomp......................................................................... 654

Checkpoint-enabled backup reporting......................................................655 View the policy reports for checkpoint-enabled client backups... 655 Determine the status of a checkpoint-enabled backup................ 655

SNMP traps............................................................................................. 656 Configuring NetWorker SNMP notifications................................656

NetWorker Notifications.......................................................................... 659 Preconfigured notifications......................................................... 659 Customizing notifications............................................................ 664 Creating a custom notification.....................................................668 Editing a notification....................................................................668 Copying a notification..................................................................669 Deleting a custom notification..................................................... 669 Configuring owner notifications...................................................669 Logging event notifications..........................................................670 Breakthrough logging .................................................................. 671

Front-end Capacity Estimation..................................................................671 Configuring EMC Secure Remote Services (ESRS).....................672

Chapter 10

Chapter 11

CONTENTS

NetWorker 18.1 Administration Guide 9

Troubleshooting ESRS.................................................................674

NetWorker Server Monitoring 675 Enterprise events monitoring....................................................................676

Polling interval for system events................................................ 676 Enabling or disabling event capture for a host..............................677 Event viewing.............................................................................. 677 Dismissing an event..................................................................... 679

Monitoring NetWorker Server activities in the Administration window..... 679 About the Monitoring window..................................................... 680 Customizing the Monitoring window............................................682 Policies/Actions pane.................................................................. 683 Sessions window......................................................................... 686 Alerts pane.................................................................................. 687 Devices pane............................................................................... 687 Operations window......................................................................688 Log window................................................................................. 690 Recover window...........................................................................691

Monitoring changes to the NetWorker and NMC Server resources..........694 Disabling or enabling the Monitor RAP Attribute......................... 695

Monitoring user access to the NMC server.............................................. 695 Monitoring NetWorker server activities in the log files............................. 695

NMC Server Management 697 Enterprise.................................................................................................698

Enterprise components................................................................698 Organizing NetWorker servers.................................................... 698 Viewing the enterprise.................................................................699 Managing various servers in the Enterprise................................. 699 Managing folders in the enterprise............................................... 701 Adding or deleting multiple servers by using a hostname file........703

Customizing the Console window and views.............................................705 Using the NMC filters...............................................................................706 Connecting to the NMC GUI using an ssh connection.............................. 708 Backing up the NetWorker environment...................................................709

Configuring an NMC server database backup.............................. 709 Performing a manual backup of the NMC server database............711

Using the NMC Configuration Wizard........................................................ 711 NMC server authentication........................................................................711

Configuring the NMC server to manage additional NetWorker servers......................................................................................... 712 Changing the NetWorker Authentication Service hostname and port number......................................................................................... 713 Modifying user groups for new NetWorker Authentication Service users.............................................................................................714

Adding the NMC service account to the Users user group........................ 717 Enabling two factor authentication for AD and LDAP users.......................718 Moving the NMC Server........................................................................... 719 Migrating NMC users to the authentication service database...................720

Updating the NetWorker User Group resources for migrated NMC users.............................................................................................721

Resetting the administrator password...................................................... 722 Changing the service port used by the NMC database............................. 724

Changing the service port used by the NMC database on Linux.. 724

Chapter 12

Chapter 13

CONTENTS

10 NetWorker 18.1 Administration Guide

Changing the service port used by the NMC database on Windows.. 725

Changing database connection credentials...............................................726 Updating the NMC server IP address/hostname...................................... 726 Setting system options to improve NMC server performance...................727

Individual User Authentication..................................................... 729 Displaying international fonts in non-US locale environments................... 730 NetWorker License Manager.................................................................... 730

Entering an enabler code............................................................. 730 Deleting an enabler code..............................................................730 Entering an authorization code.....................................................731 Changing the License Manager server..........................................731

NMC error messages and corrective actions.............................................731 Console troubleshooting notes and tips.................................................... 736

Troubleshooting an NMC server that is not responding............... 736 Unable to connect to host: Please check Security setting and daemon logs on the NetWorker client and Console server for more information.................................................................................. 737 Username/password validation fails when you use the NMC New Device wizard to configure an AFTD if storage node is UNIX....... 738 Querying large numbers of save sets in the NetWorker user interface may cause a Java heap space error...............................738 NMC user interface exits unexpectedly....................................... 738 Label and Mount devices page is not displayed in NMC device configuration wizard.................................................................... 739

NetWorker Server Management 741 Setting up the server................................................................................ 742

License the NetWorker Server.....................................................742 Setting the Job inactivity timeout................................................742 Modifying the retention period for jobs in the jobs database........742

Viewing the migration log file....................................................................743 Hostname changes................................................................................... 743 Managing the NSR task resource for nsrclientfix .....................................744 Parallelism and multiplexing...................................................................... 745

Parallelism................................................................................... 745 Multiplexing................................................................................. 748

Managing server access........................................................................... 749 Resource databases .................................................................................750

Viewing resources in the resource database................................ 750 Repairing resource database corruption...................................... 750

Indexes......................................................................................................751 Characteristics of the online indexes............................................751 Automated index activities...........................................................752 Checking online indexes...............................................................752 Viewing information about the indexes........................................ 752 Index save sets............................................................................ 753 Querying the media database.......................................................754 Cross-checking client file indexes................................................754 Refreshing index information....................................................... 755 Client file index locations............................................................. 755 Managing the size of the online indexes.......................................757

Internationalization................................................................................... 760 Log file viewer............................................................................. 760 Display issues............................................................................... 761

Chapter 14

CONTENTS

NetWorker 18.1 Administration Guide 11

Creating a Server Backup action............................................................... 761 Creating an expire action..........................................................................765

NetWorker Host Management 769 Controlling access to a NetWorker client..................................................770 NetWorker host management...................................................................770 Windows client interface...........................................................................772

Starting the NetWorker User program on Windows..................... 773 Toolbar buttons............................................................................774 Browse window............................................................................774 Connecting to a NetWorker server.............................................. 775

Editing a client NSRLA database...............................................................775

Restricted Datazones 777 Restricted Datazones overview................................................................ 778 Administrators and users of RDZ.............................................................. 778

Using multiple instances of an RDZ..............................................779 Setting up the RDZ................................................................................... 779

Setting up RDZ Users.................................................................. 780 Setting up an RDZ resource......................................................... 781

Removing a resource association..............................................................785 Backward compatibility.............................................................................785

Block Based Backup and Recovery 787 Overview.................................................................................................. 788

Supported operating systems and configurations........................ 789 Limitations....................................................................................791

Block based backups................................................................................. 791 Devices for block based backups..................................................791 Installing the lgtobbb package on Linux....................................... 792 Configuring block based backups.................................................792 Performing block based backups................................................. 794 Verifying block based backups..................................................... 797 Cloning block based backups....................................................... 797

Block based recoveries............................................................................. 797 Preparing for block based recoveries........................................... 797 Performing block based recoveries.............................................. 798 Performing block based clone recoveries..................................... 801

Troubleshooting block based backup and recovery issues........................ 804

Networking and Connectivity 807 Name resolution and connectivity............................................................ 808 Troubleshooting name resolution and connectivity errors........................ 809

Verifying basic connectivity......................................................... 810 Verifying name resolution.............................................................812 Verifying the NetWorker configuration........................................ 816

Using multihomed systems........................................................................818 Multihomed system requirements................................................ 818 Configuring multihomed hosts in a datazone................................ 818

NIC Teaming.............................................................................................824 Using DHCP clients.................................................................................. 825

Chapter 15

Chapter 16

Chapter 17

Chapter 18

CONTENTS

12 NetWorker 18.1 Administration Guide

Cloud Supportability 827 CloudBoost appliance as the back up target............................................. 828 Support for Azure Stack...........................................................................828 Cloud service provider support matrix for NetWorker.............................. 828

Troubleshooting 831 Before you contact technical support.......................................................832

Determining the version of NetWorker software running on a client.. 832 Displaying diagnostic mode attributes......................................... 833

NetWorker log files...................................................................................834 NetWorker Server log files.......................................................... 834 NMC server log files.................................................................... 837 NetWorker Client log files............................................................838 View log files............................................................................... 840 Raw log file management.............................................................844 Configuring logging levels............................................................848

NetWorker Authentication Service logs....................................................857 NetWorker Authentication Service log files................................. 857 NetWorker Authentication Service server log file management...858 CLI log file management.............................................................. 859

NetWorker functionality issues.................................................................860 Backup and recovery................................................................... 860 Backups fail to start when the daylight savings time change occurs.. 863 Shut down NetWorker services prior to any significant changes to system date.................................................................................863 Clone ID timestamp does not reflect the time the clone was created .................................................................................................... 863 Memory usage when browsing large save sets............................ 863 Memory usage and nsrjobd..........................................................864 Media position errors encountered when auto media verify is enabled........................................................................................864 The scanner program marks a volume read-only..........................864 The scanner program requests an entry for record size...............864 Limitations for groups containing a bootstrap..............................864 Index recovery to a different location fails...................................865 Illegal characters in configurations.............................................. 865 Inaccessible object exception error when launching NMC with Java 9..................................................................................................865 Error backing up large number of clients..................................... 865 Hostname aliases.........................................................................866 Directory pathname restrictions.................................................. 866 Backup of a new client defaults to level full................................. 867 Non-full backup of Solaris files with modified extended attributes.... 867 Client file index errors..................................................................867 Aborting a recovery..................................................................... 868 xdr of win32 attributes failed for directory.................................. 868 Cannot create directory directory............................................... 869 The All save set and duplicate drive serial numbers..................... 869 No disk label errors......................................................................869 Resolving copy violation errors.................................................... 869 Converting sparse files to fully allocated files.............................. 870 Backing up large sparse files........................................................870

Chapter 19

Chapter 20

CONTENTS

NetWorker 18.1 Administration Guide 13

Queries using the mminfo -N command are case-sensitive..........870 Renamed directories and incremental backups.............................871 Resolving names for multiple network interface cards..................871 Libraries entering ready state...................................................... 872 Successful save sets listed as failed in the Group Backup Details window........................................................................................ 872 The NetWorker Server window does not appear on HP-UX.........872 Backup fails with Win32 error 0x2............................................... 872 Error displaying workflow details................................................. 872 Back up of All Save Sets takes a long time to complete..............873 GSS-API authentication error ..................................................... 873

NetWorker locale and code set support....................................................874 Enabling service mode for NetWorker...................................................... 874 No privileges to view NetWorker server from NMC.................................. 874 Network and server communication errors............................................... 874

Unapproved server error..............................................................875 Unapproved server error during client setup................................875 Server copy violation................................................................... 875 Remote recover access rights..................................................... 876 NetWorker server takes a long time to restart.............................876 Changing the NetWorker server address..................................... 876 Binding to server errors............................................................... 877 New.Net and NetWorker software are incompatible.................... 877

879Glossary

CONTENTS

14 NetWorker 18.1 Administration Guide

NetWorker components............................................................................................. 28 Stopping the NetWorker Remote Exec Service.......................................................... 37 NMC GUI window.......................................................................................................39 Associating a jnlp file with Java (TM) web Start Launcher for Mozilla Firefox............46 Welcome to the NMC Server Configuration Wizard page........................................... 47 Set authentication server service account for the NMC Server page......................... 47 Specify a list of managed NetWorker servers page.................................................... 48 Administration window............................................................................................... 50 Monitoring window.....................................................................................................54 Recover window..........................................................................................................61 Labeling a volume by using a label template................................................................74 Identifying WORM tapes in the NetWorker Console...................................................94 Example NetWorker disk backup configuration in a mixed backup environment........108 Paths for CIFS AFTD.................................................................................................109 How library sharing works......................................................................................... 182 Dynamic Drive Sharing.............................................................................................. 185 Data Protection Policy..............................................................................................207 Platinum policy configuration................................................................................... 208 Data protection policy example................................................................................. 210 Replication using AMS.............................................................................................. 216 Workflow path from a traditional backup action........................................................ 217 Visual representation of a workflow..........................................................................235 Workflow path from a server database backup action.............................................. 240 Workflow path from an NMC server backup action.................................................. 240 Visual representation of the Server Protection workflows........................................ 241 Replication using AMS..............................................................................................242 Workflow path from a clone action...........................................................................250 Visual representation of a clone workflow................................................................ 255 Example of a policy with separate workflows for backup and cloning....................... 256 Workflow path from a snapshot backup action......................................................... 273 Workflow path from a probe action.......................................................................... 273 Workflow path from a server backup action..............................................................274 Workflow path from a check connectivity action...................................................... 274 Workflow path from a clone action........................................................................... 274 Workflow path from a discover action...................................................................... 274 Workflow path from a generate index action............................................................ 275 Workflow path from a VBA checkpoint discover action............................................ 275 Traditional backup workflow..................................................................................... 275 Incremental and cumulative incremental backup levels.............................................304 Synthetic full backups.............................................................................................. 305 Default weekly backup schedule................................................................................315 Staggered weekly backup schedule for multiple groups of clients.............................315 Default weekly schedule for a traditional backup action............................................ 317 The Force Backup Level attribute............................................................................. 319 VSS backup process.................................................................................................358 Paths for CIFS AFTD.................................................................................................414 Cloning example....................................................................................................... 436 Overview of archive operation..................................................................................455 Volume Save Sets window........................................................................................470 Change Expiration window........................................................................................479 Recovery roadmap....................................................................................................482 A directed recovery from a remote client .................................................................487 NSR Data Domain Properties................................................................................... 520

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 52 53

FIGURES

NetWorker 18.1 Administration Guide 15

Virtual machine recovery in the NMC Recovery wizard............................................ 523 Select the Virtual Machine to Recover..................................................................... 524 Select the Target Backup (individual virtual machine)..............................................525 Select the Target Backup (multiple virtual machines).............................................. 525 Select the Virtual Machine Recovery method...........................................................525 Choose Disks to Revert............................................................................................ 527 Select Alternate Recovery Sources.......................................................................... 528 Configure the Instant Recovery................................................................................529 Configure the virtual machine recovery.....................................................................531 Configure the Virtual Disk Recovery......................................................................... 532 Configure the Emergency Recovery......................................................................... 534 Select Alternate Recovery Sources for file level recovery........................................ 536 Mount the save set for file level recovery................................................................. 537 Select the files and folders to recover...................................................................... 538 Connect to Server ................................................................................................... 545 NetWorker Recover window.....................................................................................546 List of clients available for a NetWorker server.........................................................547 Search browse view................................................................................................. 548 Versions side bar...................................................................................................... 549 Group Summary in table view...................................................................................595 Group Summary in Bar Chart view........................................................................... 596 ESRS Properties.......................................................................................................672 Monitoring window...................................................................................................680 Recover window....................................................................................................... 692 NetWorker servers worldwide.................................................................................. 699 Using filters to search and view policies................................................................... 706 Copying the group DN...............................................................................................716 Copying the group DN...............................................................................................716 Add Distinguished Names window............................................................................. 718 Hosts window............................................................................................................ 771 NetWorker User program..........................................................................................773 Example of the browse window.................................................................................775 Restricted Data Zones in NMC................................................................................. 780 Restricted Datazone User Configuration................................................................... 781 Create Restricted Data Zone in the NetWorker Administration Server window........ 782 Restricted Data Zone Client Properties ................................................................... 783 Restricted Data Zones in Device Properties window.................................................784 Restricted Data Zones in Create Policy window........................................................784 New workflow associated with RDZ group............................................................... 785 Multihomed environment.......................................................................................... 821 Configuring the Aliases attribute for NetWorker Server Client resource.................. 822 Configuring the Aliases attribute for NetWorker Storage Node Client resource....... 822 Storage Nodes attribute for clients in VLAN1........................................................... 823 Aliases and Server network interface attributes for VLAN1 clients........................... 823 Storage Nodes attribute for clients in VLAN2...........................................................824 Aliases and Server network interface attributes for VLAN2 clients...........................824 Azure stack backup and disaster recovery................................................................828 WinPE registry key to troubleshoot recoveries.........................................................856

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

FIGURES

16 NetWorker 18.1 Administration Guide

Revision history...........................................................................................................21 Style conventions....................................................................................................... 23 NetWorker Server processes...................................................................................... 31 NetWorker Storage Node processes.......................................................................... 33 NMC Server processes...............................................................................................34 NetWorker startup commands ...................................................................................38 Windows opened from the NMC GUI..........................................................................40 Supported operations in the NetWorker Management Web UI....................................41 Windows that are launched from the Administration window..................................... 50 Monitoring window panel ...........................................................................................55 Alerts window icons....................................................................................................57 Devices status icons .................................................................................................. 58 Operations window icons............................................................................................59 Icons in the Log pane..................................................................................................60 Recovery toolbar options ...........................................................................................62 Save recover configuration job status........................................................................ 63 Find options................................................................................................................64 Key label template attributes...................................................................................... 75 Examples of number sequences for volume labels.......................................................77 Using label template components............................................................................... 78 Preconfigured media pools......................................................................................... 82 Determining which pool receives backup data............................................................ 85 NetWorker hierarchy for resolving media pool conflicts .............................................87 WORM supported devices ......................................................................................... 92 WORM/DLTWORM attributes .................................................................................. 94 Differences between disk devices ............................................................................. 110 Default values and ranges for target and max sessions attributes ............................. 112 Determining the major number value......................................................................... 132 ioscan output when driver is configured.................................................................... 132 ioscan output when driver is not configured..............................................................133 Tape alert severity.................................................................................................... 162 Common jbedit options............................................................................................. 163 Device settings and environment variables ............................................................... 170 StorageTek environment variables ........................................................................... 176 Library resource sleep attributes .............................................................................. 183 Shared Devices attributes......................................................................................... 188 Schedule icons.......................................................................................................... 218 Schedule icons.......................................................................................................... 221 Schedule icons......................................................................................................... 225 Schedule icons.......................................................................................................... 231 nsrcloneconfig file details......................................................................................... 243 Save set criteria....................................................................................................... 245 Schedule icons.......................................................................................................... 251 Save set criteria....................................................................................................... 258 Schedule icons......................................................................................................... 262 Policy status icons.................................................................................................... 267 Methods to create an action.....................................................................................283 Methods to open the Policy Action wizard............................................................... 284 Resource overview................................................................................................... 298 Data in the ALL save set .......................................................................................... 299 File systems excluded from the ALL save set........................................................... 300 Special ALL save sets ...............................................................................................301 Backup levels ...........................................................................................................302

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 52 53

TABLES

NetWorker 18.1 Administration Guide 17

Advantages and disadvantages of backup levels ......................................................302 mminfo commands for synthetic full backup validation ............................................ 310 Comparison of traditional synthetic full and virtual synthetic full backups................. 311 Requirements for virtual synthetic full backups......................................................... 311 mminfo commands for VSF backup validation .......................................................... 314 Scheduled backup level icons.................................................................................... 317 Preconfigured NetWorker schedules ........................................................................319 Log files for PSS troubleshooting............................................................................. 330 Supported wildcards in directives.............................................................................335 Preconfigured directives...........................................................................................337 Backup considerations for Windows features........................................................... 347 VSS Save operation attribute values ........................................................................362 DISASTER_RECOVERY:\ components in an incremental backup.............................366 Save set configuration for a specific host ................................................................ 374 Special ALL save sets .............................................................................................. 387 File systems excluded from the ALL save set............................................................394 Special ALL save sets .............................................................................................. 394 NetWorker software requirements for checkpoint restart........................................403 Example backup script on Windows.......................................................................... 416 NetWorker Server Versions.......................................................................................418 Job control attribute selections.................................................................................419 List of nsrclone options and their descriptions..........................................................446 Staging criteria options............................................................................................ 450 Disk volumes window................................................................................................464 Volume details.......................................................................................................... 466 Save Set details........................................................................................................468 Query criteria............................................................................................................ 471 Save set search results view.....................................................................................473 Query criteria............................................................................................................473 VBA save set search results window.........................................................................474 General recover requirements ..................................................................................487 Volume selection by recovery method...................................................................... 498 Query criteria........................................................................................................... 500 Save set status.........................................................................................................502 Optional browsable recovery options .......................................................................506 Save set information................................................................................................. 510 Optional save set recovery options .......................................................................... 513 Save set information................................................................................................. 515 DISASTER_RECOVERY:\ components in an incremental backup.............................559 Additional recovery options...................................................................................... 586 Data retention policies.............................................................................................. 591 Report categories ....................................................................................................593 Legacy report categories .........................................................................................594 Report icons............................................................................................................. 594 Report chart formats................................................................................................598 NetWorker recovery statistics parameters ...............................................................615 Event parameters .....................................................................................................618 Host reports .............................................................................................................619 NetWorker backup statistics parameters .................................................................620 NetWorker backup status parameters ..................................................................... 623 Clone report parameters ..........................................................................................625 Date and time input formats for common locales......................................................629 Workflow-specific job record attributes................................................................... 639 Action job record attributes......................................................................................643 Job details for a Workflow ........................................................................................651 Job details for a Workflow continued........................................................................ 651

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 108 109

TABLES

18 NetWorker 18.1 Administration Guide

Command-line options for nsrtrap ........................................................................... 657 Preconfigured notifications ..................................................................................... 659 Actions .................................................................................................................... 665 Priorities .................................................................................................................. 667 Event Viewer messages ........................................................................................... 670 NMC event information............................................................................................ 677 Event priorities ........................................................................................................ 678 Monitoring window panel ......................................................................................... 681 Policy status icons....................................................................................................683 Alerts window icons..................................................................................................687 Devices status icons ................................................................................................ 688 Operations window icons..........................................................................................689 Icons in the Log pane................................................................................................ 691 Recovery toolbar options .........................................................................................692 Save recover configuration job status...................................................................... 693 Find options..............................................................................................................694 Viewing the enterprise..............................................................................................699 NMC windows with filtering capability......................................................................707 NMC server system options .....................................................................................727 Error messages or symptoms ................................................................................... 731 Indexes window information..................................................................................... 752 Index save sets dialog box information......................................................................753 Schedule icons for the expire action ........................................................................ 766 When to modify the servers file................................................................................ 770 Summary pane...........................................................................................................771 NetWorker User Groups requirements......................................................................773 NetWorker User toolbar functions ........................................................................... 774 Supported backup and recovery scenarios............................................................... 789 Key options for the block based recover.exe command.............................................801 Troubleshooting block based backup and recovery issues........................................ 804 Configuring multihomed hosts in NetWorker (continued)......................................... 818 NetWorker Server log files....................................................................................... 834 NMC server log files................................................................................................. 837 Client log files...........................................................................................................838 Message types .........................................................................................................842 Raw log file attributes that manage log file size........................................................845 Raw log file attributes that manage the log file trimming mechanism....................... 846 NetWorker Authentication Service log files.............................................................. 857 NetWorker Startup commands................................................................................. 877

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

TABLES

NetWorker 18.1 Administration Guide 19

TABLES

20 NetWorker 18.1 Administration Guide

Preface

As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in this document, contact a technical support professional.

Note

This document was accurate at publication time. To ensure that you are using the latest version of this document, go to the Support website at https:// support.emc.com.

Purpose This document describes how to configure and use 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

05 February 15 A note has been added to the topic "Configuring block based backups".

04 December 12, 2018 The following changes are done:

l A new topic titled Storage Node Options is included.

l Editorial fixes are done to the topic title Using the nslookup command.

03 August 20, 2018 Updated the "Restricted Data Zones" chapter.

02 July 18, 2018 Updated the section "Creating a query group" to correct the description of the "Limit the number of clones" save set criteria.

01 July 07, 2018 First release of this document for NetWorker 18.1.

Related documentation The NetWorker documentation set includes the following publications, available on the Support website:

l NetWorker Online Software Compatibility Matrix

NetWorker 18.1 Administration Guide 21

Provides compatibility information, including specific software and hardware configurations that NetWorker supports. To access the matrix, go to http:// compatibilityguide.emc.com:8080/CompGuideApp/.

l NetWorker Administration Guide Describes how to configure and maintain the NetWorker software.

l NetWorker Network Data Management Protocol (NDMP) User Guide Describes how to use the NetWorker software to provide data protection for NDMP filers.

l NetWorker Cluster Integration Guide Contains information related to configuring NetWorker software on cluster servers and clients.

l 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 NetWorker Updating from a Previous Release Guide Describes how to update the NetWorker software from a previously installed release.

l 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 NetWorker Command Reference Guide Provides reference information for NetWorker commands and options.

l 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 NetWorker Performance Optimization Planning Guide Contains basic performance tuning information for NetWorker.

l NetWorker Server Disaster Recovery and Availability Best Practices Guide Describes how to design, plan for, and perform a step-by-step NetWorker disaster recovery.

l 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 storage arrays.

l NetWorkerSnapshot 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 NetWorker Security Configuration Guide Provides an overview of security configuration settings available in NetWorker, secure deployment, and physical security controls needed to ensure the secure operation of the product.

l NetWorker VMware Integration Guide Provides planning and configuration information on the use of VMware in a NetWorker environment.

l NetWorker Error Message Guide Provides information on common NetWorker error messages.

l NetWorker Licensing Guide Provides information about licensing NetWorker products and features.

Preface

22 NetWorker 18.1 Administration Guide

l 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 NetWorker REST API Reference Guide Provides the NetWorker REST API specification used to create programmatic interfaces to the NetWorker server.

l NetWorker 18.1 with CloudBoost 18.1 Integration Guide Describes the integration of NetWorker with CloudBoost.

l NetWorker 18.1 with CloudBoost 18.1 Security Configuration Guide Provides an overview of security configuration settings available in NetWorker and Cloud Boost, secure deployment, and physical security controls needed to ensure the secure operation of the product.

l 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 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 The following conventions are used 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 The following type style conventions are used in this document:

Table 2 Style conventions

Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area with title, table label, and window.

Italic Used for full titles of publications that are referenced in text.

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, file name extensions, prompts, and syntax

l Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

Preface

NetWorker 18.1 Administration Guide 23

Table 2 Style conventions (continued)

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means or for the alternate selections.

{ } Braces enclose content that the user must specify, such as x, y, or z.

... Ellipses indicate non-essential information that is omitted from the example.

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation

l https://support.emc.com

l https://community.emc.com

Where to get support The Support website at https://support.emc.com provides access to licensing information, product documentation, advisories, and downloads, as well as how-to and troubleshooting information. This information may enable you to resolve a product issue before you contact Support.

To access a product specific Support page:

1. Go to https://support.emc.com/products.

2. In the Find a Product by Name box, type a product name, and then select the product from the list that appears.

3. Click .

4. (Optional) To add the product to My Saved Products, in the product specific page, click Add to My Saved Products.

Knowledgebase The Knowledgebase contains applicable solutions that you can search for by solution number, for example, 123456, or by keyword.

To search the Knowledgebase:

1. Go to https://support.emc.com.

2. Click Advanced Search. The screen refreshes and filter options appear.

3. In the Search Support or Find Service Request by Number box, type a solution number or keywords.

4. (Optional) To limit the search to specific products, type a product name in the Scope by product box, and then select the product from the list that appears.

5. In the Scope by resource list box, select Knowledgebase. The Knowledgebase Advanced Search panel appears.

6. (Optional) Specify other filters or advanced options.

7. Click .

Live chat To participate in a live interactive chat with a support agent:

1. Go to https://support.emc.com.

Preface

24 NetWorker 18.1 Administration Guide

2. Click Chat with Support.

Service requests To obtain in-depth help from Licensing, submit a service request. To submit a service request:

1. Go to https://support.emc.com.

2. Click Create a Service Request.

Note

To create a service request, you must have a valid support agreement. Contact a sales representative for details about obtaining a valid support agreement or with questions about an account. If you know the service request number, then directly enter the service request number in the Service Request field to get the valid details.

To review an open service request:

1. Go to https://support.emc.com.

2. Click Manage service requests.

Online communities Go to the 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 products.

How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to DPAD.Doc.Feedback@emc.com.

Preface

NetWorker 18.1 Administration Guide 25

Preface

26 NetWorker 18.1 Administration Guide

CHAPTER 1

Overview

This chapter contains the following topics:

l The NetWorker environment..............................................................................28 l NetWorker services........................................................................................... 30 l NetWorker user interfaces.................................................................................39

Overview 27

The NetWorker environment The 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 application and database server. The NMC Server manages all NetWorker Servers and

Overview

28 NetWorker 18.1 Administration Guide

Clients. The NMC Server provides reporting and monitoring capabilities for all NetWorker Servers and Clients in the environment. The NMC Server relies on the NetWorker Authentication Service for user account authentication.

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.2.x environment. You can configure the NetWorker Authentication Service to use a local user database or external identity providers (LDAP, LDAPS, and AD) for authentication.

NetWorker Server The NetWorker Server is a collection of processes and programs that are installed on a host that performs NetWorker services. The NetWorker Server also acts as a storage node and can control multiple remote storage nodes.

NetWorker client A NetWorker client is a physical or virtual computer on which 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.

The NetWorker client software is available 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 Linux 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 NetWorker REST API Getting Started Guide describes how

Overview

NetWorker Components 29

to use NetWorker REST API, and the NetWorker REST API Reference Guide provides a full description of the API resources.

Dell EMC Licensing Solution NetWorker 9.0.x and later servers use the Dell EMC Licensing Solution.

The Dell EMC Licensing Solution is a licensing standard that stores all licensing information for the environment in one license file, which is stored on both the NetWorker server and, if using a served license, the License Server.

All new installations of NetWorker use the Dell EMC Licensing Solution. The chapter "Dell EMC Licensing Solution" in the NetWorker Licensing Guide provides information on how to implement the Dell EMC Licensing Solution for new and upgraded installations of the NetWorker software. The "Dell EMC Licensing Solution" chapter also describes the Dell EMC Licensing 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 NetWorker Data Domain Boost Integration Guide provides detailed information about setting up DD Boost deduplication devices to work with NetWorker.

Virtual environments The NetWorker Vmware Integration Guide provides more information on the virtual environment solutions from Networker.

NetWorker services The main services and programs for the NetWorker Server are the NetWorker Storage Node, NetWorker Client, and the 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:

l Main NetWorker servicesThe NetWorker Command Reference Guide or the UNIX man pages provides more information.

l Service port requirements when configuring a firewallThe NetWorker Security Configuration Guide provides more information.

Overview

30 NetWorker 18.1 Administration Guide

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

nsrctld The top-level NetWorker Server process that monitors, stops, and starts all NetWorker Server processes.

nsrd l NetWorker save and recovery daemon.

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 l NetWorker save and recover media management database service daemon.

l 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 an indexing service to read, write, and remove index entries.

Overview

Processes on NetWorker hosts 31

Table 3 NetWorker Server processes (continued)

Process Function

The nsrd service starts one nsrindexd process on the NetWorker server. The nsrindexd process spawns an additional

helper nsrindexd process for each index session.

NetWorker uses index sessions to read, write, or delete index entries, for example, when NetWorker saves an index, or when a user performs a file-level or browsable recover. When the read or write operation completes, the helper nsrindexd process closes.

nsrmmgd 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.

nsrlogd Supports the NetWorker audit log service, which is configured to run on the NetWorker Server by default.

nsrcpd l Starts automatically when a user

accesses the Hosts Task window in the NetWorker Administration interface.

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.

nsrvmwsd Provides a web service to manage VMware VM backups that are part of the NetWorker VMware protection feature.

Overview

32 NetWorker 18.1 Administration Guide

Table 3 NetWorker Server processes (continued)

Process Function

tomcat7 (Windows), tomcat (UNIX) Tomcat web server instance for the NetWorker Authentication Service.

nsrexecd Authenticates and processes the NetWorker Server remote execution requests and runs the save and savefs programs on the client.

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.

nsrsnmd 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.

nsrlcpd l Provides a uniform library interface to the NetWorker media management daemon, nsrmmgd.

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.

Overview

Processes on NetWorker hosts 33

Table 4 NetWorker Storage Node processes (continued)

Process Function

nsrexecd Authenticates and processes the NetWorker Server remote execution requests and runs the save and savefs programs on the client.

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, first stop the NetWorker Console service and then 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 then select Manage.

2. Expand Services and Applications, and then select Services.

3. Right-click EMC GST Service and select Stop.

Overview

34 NetWorker 18.1 Administration Guide

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 then select Manage.

2. Expand Services and Applications, and then select Services.

3. Verify that the NetWorker Client service 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:

a. On sysVinit enabled Linux machines, type /etc/init.d/gst stop b. On systemd enabled Linux machines, type systemctl stop gst

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.

Overview

Stop and start the NMC Server 35

2. To start the NMC Server daemon, postgres, and httpd processes., type /etc/init.d/gst start

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. Attributes exist that allow you to configure a NetWorker Server to not accept any new backup or recover sessions in preparation of a NetWorker daemon shutdown or server restart.

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 then select Manage.

2. Expand Services and Applications, and then select Services.

3. Right-click NetWorker Remote Exec Service, and then 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.

The following figure shows how to stop the NetWorker Remote Exec Service service.

Overview

36 NetWorker 18.1 Administration Guide

Figure 2 Stopping the NetWorker Remote Exec 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 then select Manage.

2. Expand Services and Applications, and then select Services.

3. Start the appropriate service:

l NetWorker server: Right-click the NetWorker Backup and Recover Server service and select Start.

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:

a. On sysVinit enabled Linux machines, type /etc/init.d/networker stop b. On systemd enabled Linux machines, type systemctl stop networker

2. To confirm that the NetWorker processes are not running, type the following command from a prompt:

Overview

Stop and start a NetWorker Server, Client, or Storage Node 37

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 For systemd enabled Linux machines - systemctl start networker

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:

sudo launchctl unload /Library/LaunchDaemons/ com.xyz.NetWorker.plist

Note

The launchd daemon/agent manager controls the NetWorker processes, and NetWorker configures the processes to run continuously on the host in the background. It is not recommended 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.

Overview

38 NetWorker 18.1 Administration Guide

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 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.

Figure 3 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.

Overview

NetWorker user interfaces 39

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 NetWorker Security Configuration Guide provides information about user management.

l License management Manage NetWorker licenses. The 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.

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:

Overview

40 NetWorker 18.1 Administration Guide

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 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 typing this command:

nsradmin

For more information about nsradmin, the 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 NetWorker Command Reference Guide or the UNIX man pages provides information about these commands.

Introduction to the NetWorker Management Web UI The NetWorker Management Web UI, introduced in NetWorker 18.1, is a web-based management interface that provides support for the following NetWorker VMware- integrated operations:

l Managing VMware vCenter servers

l Managing VMware Proxies

l Installing the vCenter Plugin

l Recovering virtual machines

l Monitoring recovery operations

The following table provides more information on the functionality available in the NetWorker Management Web UI.

Table 8 Supported operations in the NetWorker Management Web UI

Operation Description

Protection VMware vCenter servers

l Manage vCenter servers.

l Refresh and view the vCenter inventory.

l View properties of entities in the vCenter Inventory tree.

VMware vProxies

l Manage vproxies.

l Monitor progress of vProxy registration.

Overview

NetWorker character-based interface 41

Table 8 Supported operations in the NetWorker Management Web UI (continued)

Operation Description

Recovery Recover virtual machines. Supports both image-level and file-level recovery.

Monitoring l View and monitor the progress of virtual machine recovery; includes the list of completed and currently running recover jobs.

l View recover logs.

You can log in to the NetWorker Management Web UI by using the NetWorker credentials for authentication.

The NetWorker VMware Integration Guide provides more information on how to use the NetWorker Management Web UI to perform the supported tasks.

The NetWorker Installation Guide provides more information on how to install the NetWorker Management Web UI.

Supported browsers The NetWorker Management Web UI supports the following browsers:

l Microsoft Internet Explorer 11

l Google Chrome

l Microsoft Edge

l Mozilla Firefox

Overview

42 NetWorker 18.1 Administration Guide

CHAPTER 2

Getting Started

This chapter contains the following topics:

l NetWorker Management Console interface....................................................... 44 l Connecting to the Administration window..........................................................49 l Getting started with a new installation...............................................................64

Getting Started 43

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.

Note

To start NMC, you must use 64-bit Java. NMC will fail to start if Java 32-bit is used.

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 ServerConfirm that the NetWorker daemons have started, by typing the command below, based on the initialization system running on your Linux machine : /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 example 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 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 example 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:

Getting Started

44 NetWorker 18.1 Administration Guide

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

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, NetWorker Server Service, and NetWorker Server Web Service.

2. If these services are not started, start the NetWorker Server 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 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. Optional, associate the jnlp file with a program.

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. In the dialog box that appears, select Open with, and then select Java (TM) Web Start Launcher. If this application does not appear, browse to the Java folder and select the javaws.exe file. The following figure provides an example of the file association dialog box that appears with the Mozilla Firefox browser.

Getting Started

Connecting to the Console window 45

Figure 4 Associating a jnlp file with Java (TM) web Start Launcher for Mozilla Firefox

3. On the Welcome page, click Start.

Note

If the Start button does not appear but you see a warning message that 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, and then click Run.

5. On the Log in page, specify the NetWorker Authentication Service administrator username and password, and then click OK.

6. On the Licensing Agreement page, select Accept.

7. On the Welcome to the NMC Server Configuration Wizard page, click Next.

The following figures shows the Welcome to the NMC Server Configuration Wizard page.

Getting Started

46 NetWorker 18.1 Administration Guide

Figure 5 Welcome to the NMC Server Configuration Wizard page

8. On the Set authentication server service account for the NMC server page, review the setting and click Next.

The following figure shows the Set authentication server service account for the NMC server page. Figure 6 Set authentication server service account for the NMC Server page

9. On the Specify a list of managed NetWorker Servers page:

a. Specify the names of the NetWorker Servers 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.

Getting Started

Connecting to the Console window 47

b. Leave the default Capture Events and Gather Reporting Data options enabled.

Consider the following options:

l To allow the NMC Server to monitor and record alerts for events that occur on the NetWorker Server, select Capture Events.

l To allow the NMC Server to collect data about the NetWorker Server and generate reports, select Gather Reporting Data.

The following figure shows the Specify a list of managed NetWorker servers page. Figure 7 Specify a list of managed NetWorker servers page

10. Click Finish. The installation starts the default web browser and connects to the NMC server. The NetWorker Management Console and Getting Started windows appear.

11. 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 page, the NMC Enterprise window does not display any NetWorker Servers. To add a host, in the left navigation pane, right-click Enterprise, and then click 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.

Getting Started

48 NetWorker 18.1 Administration Guide

l

Double-click the desktop button , if one was configured by using the Java Web Start Application Manager.

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 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.

Getting Started

Connecting to the Administration window 49

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.

Figure 8 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 9 Windows that are launched from the Administration window

Butt on

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. Provide the ability to monitor, start, stop, and restart data protection policies.

Recover Manage 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.

Getting Started

50 NetWorker 18.1 Administration Guide

Table 9 Windows that are launched from the Administration window (continued)

Butt on

Window Description

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 Package Manager.

Server Manage NetWorker Server resources such as licenses, notifications, user groups, directives, and restricted datazones.

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:

Getting Started

Editing multiple resources 51

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.

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.

Getting Started

52 NetWorker 18.1 Administration Guide

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.

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.

Getting Started

Multiple library devices and slots 53

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 then select Launch Application.

The Administration window appears.

3. To view the Monitoring window, click Monitoring.

Figure 9 Monitoring window

Getting Started

54 NetWorker 18.1 Administration Guide

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 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 10 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 683 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 window on page 56 provides more information.

Alerts Lists the priority, category, time, and message of any alerts. Alerts pane on page 56 provides more information.

Devices Lists devices, device status, storage nodes, libraries, volumes, pools, and related messages. Devices pane on page 57 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.

Getting Started

Monitoring NetWorker Server activities in the Administration window 55

Table 10 Monitoring window panel (continued)

Window Information provided

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 window on page 60 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.

To view all sessions or to limit the list of sessions by the session type, click the tabs at the bottom of the Sessions pane. 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 list box.

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.

Getting Started

56 NetWorker 18.1 Administration Guide

Table 11 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.

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.

Getting Started

Monitoring NetWorker Server activities in the Administration window 57

Entering user input on page 60 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 12 Devices status icons

Icon 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.

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 60 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.

Getting Started

58 NetWorker 18.1 Administration Guide

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 13 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.

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.

Getting Started

Monitoring NetWorker Server activities in the Administration window 59

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 If Yes, and input is supplied, the icon in the User Input column disappears.

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 14 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.

Getting Started

60 NetWorker 18.1 Administration Guide

Table 14 Icons in the Log pane (continued)

Icon Label Description

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 NetWorker Management Console (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.

l Start and stop a recover job.

The Recover window is divided into five sections:

l ToolbarThe 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 10 Recover window

Getting Started

Monitoring NetWorker Server activities in the Administration window 61

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 15 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.

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 RecoversThe total number of successful recover jobs.

l SinceThe 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 StatusThe job status of a saved recover configuration.

l Name

l Source client

l Destination client

Getting Started

62 NetWorker 18.1 Administration Guide

l Recovery list

l Recover typeFor example, file system or BBB.

l Comment

l OSThe operating system of the source host.

l Recover requestorThe Windows or UNIX account used to create the recover configuration.

l Start Time

l End Time

l Start date

Table 16 Save recover configuration job status

Icon Description

The last recover attempt failed.

The last recover attempt completed successfully.

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 typeFor 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

Getting Started

Monitoring NetWorker Server activities in the Administration window 63

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 17 Find options

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.

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.

Getting Started

64 NetWorker 18.1 Administration Guide

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.

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. On the taskbar, click the Enterprise icon .

3. In the navigation tree, highlight a host:

a. Right-click NetWorker.

b. Select Launch Application. The NetWorker Administration window appears.

4. On the taskbar, click the Devices button .

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, perform either of the following steps:

l Select the storage node for the library.

l Click Create a new Storage Node.

7. Select Start scan.

NetWorker scans for new devices. 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. On the taskbar, click the Enterprise icon .

3. In the navigation tree, highlight a host:

a. Right-click NetWorker.

b. Select Launch Application. The NetWorker Administration window appears.

4. On the taskbar, click the Devices button .

5. From the File menu, select New Device Wizard.

Getting Started

Common NetWorker tasks 65

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.

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. On the taskbar, click the Enterprise icon .

3. In the navigation tree, highlight a host:

a. Right-click NetWorker.

b. Select Launch Application. The NetWorker Administration window appears.

4. On the taskbar, click the Devices button .

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, perform either of the following steps:

l Select the storage node for the library.

l Click Create a new Storage Node.

9. Click Start Configuration.

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. On the taskbar, click the Enterprise icon .

3. In the navigation tree, highlight a host:

a. Right-click NetWorker.

Getting Started

66 NetWorker 18.1 Administration Guide

b. Select Launch Application. The NetWorker Administration window appears.

4. On the taskbar, click the Devices button .

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.

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 Target on page 73 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 421 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:

Getting Started

Common NetWorker tasks 67

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:

l The type of backup to perform each day.

l The destination storage node and media pool.

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. On the taskbar, click the Enterprise icon .

3. In the navigation tree, highlight a host:

a. Right-click NetWorker.

b. 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

Getting Started

68 NetWorker 18.1 Administration Guide

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. To validate a user and generate a token for the user, use the nsrlogin command:

nsrlogin [-s NetWorker_server] [-H authentication_host] [-P port] [-t tenant] [-d logindomain] -u username [-p "password"]

where:

l -s NetWorker_serverSpecifies 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_hostSpecifies 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 portSpecifies 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 logindomainSpecifies 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 usernameSpecifies 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

Getting Started

Common NetWorker tasks 69

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 the NetWorker Authentication Service successfully validates the user, the service issues an authentication token to the requesting host.

2. At the command prompt, type the NetWorker command.

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 480 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:

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 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.

Getting Started

70 NetWorker 18.1 Administration Guide

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 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:

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.

l To determine the cause, refer to the Troubleshooting chapter.

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.

Getting Started

Common NetWorker tasks 71

Getting Started

72 NetWorker 18.1 Administration Guide

CHAPTER 3

Backup Target

This chapter contains the following topics:

l Label templates.................................................................................................. 74 l Media pools........................................................................................................ 81 l Storage nodes....................................................................................................97 l Disk storage devices......................................................................................... 106 l Libraries and silos............................................................................................. 129 l File type devices............................................................................................... 189 l Stand-alone devices......................................................................................... 190 l Labeling volumes.............................................................................................. 196 l Troubleshooting devices and autochangers...................................................... 197

Backup Target 73

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 11 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 81 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.

Backup Target

74 NetWorker 18.1 Administration Guide

2. Labels the volume with the name specified in the Volume Name attribute by using one of the following:

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 Archive

l Archive clone

l Data Domain Default

l Data Domain Default Clone

l DD Cloud Tier Default Clone

l Default

l Default 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 18 Key label template attributes

Attribute Guidelines

Name Keep the label name consistent with the media pool name, so that the label name

Backup Target

Preconfigured label templates 75

Table 18 Key label template attributes (continued)

Attribute Guidelines

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 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).

Backup Target

76 NetWorker 18.1 Administration Guide

Table 18 Key label template attributes (continued)

Attribute Guidelines

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 19 Examples of number sequences for volume labels

Type of components

Fields Number sequence result

Total number of labels

Range of numbers 001-100 001, 002, 003,...100 100

Character string

Range of numbers

SalesFull

001-100

SalesFull. 001,...SalesFull.100

100

Range of lowercase letters

Range of numbers

aa-zz

00-99

aa.00,...aa.99,

ab.00,...ab.99,

ac.00,...ac.99,

:

az.00...az.99,

ba.00,...ba.99

:

zz.00,...zz.99

67,600 (262 times 102)

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.

Backup Target

Guidelines for completing Label Template attributes 77

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 20 Using label template components

Type of organizational structure

Components Separator Resulting volume labels

Sequential AcctFull

001-100

period AcctFull.001

(100 total labels)

Storage oriented (for example, 3 storage racks with 5 shelves each, each shelf holding 100 tapes)

1-3

1-5

001-100

dash 1-1-001

This label is for the first tape in rack 1 on shelf 1. (1,500 total labels)

Two-sided media (for example, optical devices)

AcctFull

000-999

a-b

underscore AcctFull_000_a (side 1)

AcctFull_000_b (side 2)

(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.

Backup Target

78 NetWorker 18.1 Administration Guide

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:

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.

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 right-click. The menu displays an option to edit the attribute. For

Backup Target

Working with label templates 79

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.

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 labels 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:

Backup Target

80 NetWorker 18.1 Administration Guide

l Range of numbersFor example, 001-999

l Range of lowercase lettersFor example, aa-zz

l Range of uppercase lettersFor example, AA-ZZ

l Character stringFor 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.

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.

Backup Target

Media pools 81

Preconfigured media pools NetWorker provides you with the following preconfigured media pools.

Table 21 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:

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.

Data Domain Default Receives backup data to DD Boost devices only. NetWorker Data Domain Boost Integration Guide provides more information about how to use NetWorker with DD Boost devices.

Data Domain Default Clone Receives clone data to DD Boost devices only. NetWorker Data Domain Boost Integration Guide

Backup Target

82 NetWorker 18.1 Administration Guide

Table 21 Preconfigured media pools (continued)

Pool name Description

provides more information about how to use NetWorker with DD Boost devices.

DD Cloud Tier Default Clone Receives clone data on DD Cloud Tier devices only. NetWorker Data Domain Boost Integration Guide provides more information about how to use NetWorker with DD Cloud Tier devices.

Default Clone 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.

Indexed Archive 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 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 resourcePools, 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.

Backup Target

Using media pools 83

l Action resourceDestination 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 resourceClients, Save sets, and Retention policy attributes on the Legacy tab. The values that appear in these attributes were defined in NetWorker 8.1.x and 8.2.x. After the migration completes, the NetWorker 9.2.x 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.

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

It is recommended 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 OverrideThe 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 OverrideThe 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 RulesEnabled 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.

Backup Target

84 NetWorker 18.1 Administration Guide

Table 22 Determining which pool receives backup data

Client Override Behavior (Action)

Destination pool (Action)

Pool (Client)

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

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

Backup Target

Using media pools 85

Example 2 Example: Client Can Override is enabled (continued)

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.

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.

Example 5 Legacy Backup Rules is enabled

Backup Target

86 NetWorker 18.1 Administration Guide

Example 5 Legacy Backup Rules is enabled (continued)

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.corp.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.corp.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.corp.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 23 NetWorker hierarchy for resolving media pool conflicts

Precedence Groups attribute

Clients attribute

Save sets attribute

Levels attribute

Highest x x x x

Backup Target

Using media pools 87

Table 23 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

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.

Backup Target

88 NetWorker 18.1 Administration Guide

l BackupSelect this type to configure the pool to receive backup data.

l Backup cloneSelect this option to configure the pool to receive a clone copy of backup data.

l ArchiveSelect this type to configure the pool to receive archive data.

l Archive cloneSelect 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 DevicesSelect the devices on which NetWorker can mount volumes for this pool.

l Media type requiredSelect 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 preferredSelect 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 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.

Backup Target

Using media pools 89

Attribute Definition

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.

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 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 recycle

Defines the maximum number of recyclable volumes that 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 provides more information about how to create Worm pools.

Backup Target

90 NetWorker 18.1 Administration Guide

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.

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

Backup Target

Using media pools 91

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 NetWorker Hardware Compatibility Guide.

Table 24 WORM supported devices

Device Description

HP LTO Ultrium 3 and higher Unique to HP 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

Quantum SDLT600, DLT-S4, and DLT-V4 (SCSI and SATA)

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

Sony AIT-2, AIT-3, AIT-4, and SAIT

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

IBM 3592 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

STK 9840A/B/C, 9940B, T10000

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

Backup Target

92 NetWorker 18.1 Administration Guide

Table 24 WORM supported devices (continued)

Device Description

IBM LTO Ultrium 3 and higher, and Quantum LTO Ultrium 3 and higher

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.

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

Backup Target

Using media pools 93

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 12 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.

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 DTL-type drive).

Configuring WORM and DLTWORM support The following table describes WORM and DLTWORM attributes.

Table 25 WORM/DLTWORM attributes

Attribute Description

WORM pools only hold WORM tape By default, the NetWorker software only allows WORM tapes into WORM pools. Deselecting this option lets you add new (non-WORM) tapes to a WORM pool. This is

Backup Target

94 NetWorker 18.1 Administration Guide

Table 25 WORM/DLTWORM attributes (continued)

Attribute Description

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

Backup Target

Using media pools 95

l WORM tapes only in WORM pools

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 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.

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.

Backup Target

96 NetWorker 18.1 Administration Guide

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 nodes 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 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 NetWorker Licensing Guide provides information on NetWorker licensing support for storage nodes.

Backup Target

Storage nodes 97

Storage node configuration The following sections provide the procedures for configuring a NetWorker storage node.

Configuring the Linux host as a storage node Configure a storage node host to manage the data protection activities on a host that is not the NetWorker server.

Procedure

1. Ensure that 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 SCSI.

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 the nsrmmd (data mover) option:

l To start nsrmmd processes for disabled devices, select Yes.

l To not start nsrmmd processes for disabled devices, select No.

d. In Dynamic nsrmmds, for AFTD or DD Boost devices, select whether nsrmmd processes on the storage node devices are started dynamically.

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. In environments where unattended firewall ports must be restricted for security reasons, the storage node settings for mmds for disabled

Backup Target

98 NetWorker 18.1 Administration Guide

devices and Dynamic nsrmmds unselected (static mode) offer more control. These storage node settings cause all available nsrmmd firewall ports to be attended by running nsrmmd processes.

7. Select the Configuration tab.

8. 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 For NetWorker to detect all LUNs (Iogical unit numbers), select Yes. Detection can be time consuming.

l For NetWorker to stop searching at the first available LUN, select No, the default setting.

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 field:

l If the storage node type is set to SCSI, list any SCSI targets to exclude from backup operations, one per line.

l The format is bus.target.lun where the target and LUN fields are optional.

l You can exclude a maximum of 63 targets.

9. 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.

n If the Clone storage nodes attribute does not contain a value, then the device operations use the value that is defined in the Clone storage nodes attribute for the Storage Node resource that was created for the NetWorker server.

n 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.

10. Click OK.

Backup Target

Storage node configuration 99

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 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 servers 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 servers 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.

Backup Target

100 NetWorker 18.1 Administration Guide

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:

l Max sessionsDistributes save sessions that are based on the setting in the Max sessions option in the storage node device resource. This is the default distribution method. The Max sessions option is more likely to concentrate the backup load on fewer storage nodes.

l Target sessionsDistributes save sessions that are based on the setting defined in the Target sessions option in each storage node device resource. The Target sessions option is more likely to spread the backup across multiple 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 clients 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 clients 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.

Note 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 sessions option rather than the device Max sessions 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 It is recommended to use the default values for Max sessions as lowering these values can impact performance.

Backup Target

Storage node configuration 101

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 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 NetWorker 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 101.

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.

Backup Target

102 NetWorker 18.1 Administration Guide

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.

5. Click OK.

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

Backup Target

Storage node configuration 103

less than the target sessions value. It is recommended to use the default values for Max sessions as lowering these values can impact performance.

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.

Staging bootstrap backups

You can direct bootstrap backups to a disk device such as an AFTD or FTD device.

However, if you stage a bootstrap backup to a volume on another device, NetWorker reports the staging operation as complete although the recover space operation has not started, and the bootstrap remains on the original device. Therefore, if the staged bootstrap is accidentally deleted, you can recover the bootstrap from the original disk. The NetWorker Server Disaster Recovery and Availability Best Practices Guide describes how to recover a bootstrap from the original disk.

Also, if the bootstrap data is not staged from the original disk, the data on the original disk is subject to the same retention policies as any other save set backup and is, therefore, deleted after the retention policy has expired.

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.

Storage Node Options Storage node options secures the environment by restricting unattended firewall ports.

If Dynamic nsrmmds is selected, then the NetWorker adds devices only on demand. Dynamic mode can improve bandwidth and performance, but the firewall ports may be

Backup Target

104 NetWorker 18.1 Administration Guide

left unattended by running processes. If Dynamic nsrmmds is set to No, then the NetWorker starts all available nsrmmd processes. Static mode along with the mmds for disabled devices option provides greater control on the nsrmmd firewall ports. They ports are attended by running processes.

MMDS for Disabled Devices

Dynamic nsrmmds

Functionality

No No This is a static configuration. The number of ports that are to be open is equal to the number of disk devices on the storage node, that is, the max nsrmmd count.

Yes No This is a static configuration. The number of ports that are to be open is equal to the number of disk devices on the storage node, that is, the number of nsrmmds. In this configuration, the ports are not utilized efficiently. A few of them remain unused. When the disabled devices are re-enabled, then all the open ports might be used.

Yes/No Yes This is a dynamic configuration. This configuration ensures that the nsrmmds are started on demand by the server.

Note

You must ensure that the sum of storage node devices nsrmmds count should not exceed 655.

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.

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

Backup Target

Configuring a dedicated storage node 105

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 100 provides more information.

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 computers local disk or a network-attached disk. NetWorker supports FTD, AFTD, and DD Boost device types. This section does not cover disk-based devices that emulate other device types, such as virtual tape libraries (VTLs).

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:

Backup Target

106 NetWorker 18.1 Administration Guide

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 NetWorker Data Domain Boost Integration Guide provides details on DD Boost devices

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.

Backup Target

Example environment 107

Figure 13 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.

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.

Backup Target

108 NetWorker 18.1 Administration Guide

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.

Figure 14 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

Backup Target

Considerations for Client Direct clients 109

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.

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 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)

DD Boost device

Create a device l Device Property Window

Select the media type: file.

UNIX/Linux storage node: local or NFS only.

Windows storage node: local path only. CIFS is not supported for FTDs.

l Device Configuration Wizard

l Device Property Window

Select media type: adv_file.

UNIX/Linux storage node: local or NFS only.

Windows storage node: local or CIFS using UNC path or using NFS: Remote user, Password.

l Device Configuration Wizard

l Device Property Window

Select media type: Data Domain

Storage location l Specified in the Name attribute.

l Specified in the Device Access Information attribute.

l Specified in the Device Access Information attribute.

Concurrent save set operations

Concurrent AFTD recovery operation limitations on page 127 provides more information about performing concurrent recovery operations from an AFTD.

l No. l Yes. l Yes.

Backup Target

110 NetWorker 18.1 Administration Guide

Table 26 Differences between disk devices (continued)

Function or operation File type device (FTD) Advanced file type device (AFTD)

DD Boost device

Reclaiming or recovering space

l The nsrim program

removes both aborted and expired save sets, once every 24 hours, by the Expiration action, at the time defined in the Server backup workflow (if you have set volume recycle to Auto).

.

l Aborted save sets immediately removed.

l The nsrim program

removes expired save sets from the media database once every 24 hours, by the Expiration action, at the time defined in the Server backup workflow (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.

l Reclaims only data that is unique, not required by other existing backups.

l NetWorker does not 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 for devices

l If the file type device was used before setting the Volume Default Capacity attribute, the data for that file type device must be staged or cloned to another device.

l Does not apply. l Does not apply.

AFTD Percentage Capacity l Does not apply. l A setting determines the capacity that NetWorker software should stop writing to an AFTD: spans from 1% to 100%.

l Does not apply.

When file system or volume is full

l Waiting message is displayed if no writable volume available or until volume becomes available.

l Volume marked full and is no longer available for backups until the volume becomes appendable.

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.

l Backup to a DD Boost device fails and stops when full.

Save set continuation l Yes. l No. Save sets that start on an AFTD must be

l No. Save sets that start on a DD Boost device

Backup Target

Differences between FTDs, AFTDs, and DD Boost devices 111

Table 26 Differences between disk devices (continued)

Function or operation File type device (FTD) Advanced file type device (AFTD)

DD Boost device

completed on the same device.

must be completed on the same device.

Data format in device l Open Tape Format (OTF).

l Save stream (uasm) format (uses less space).

l Deduplicated

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.

l No. l 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.

NetWorker archive operations are not supported for Client Direct backup.

l Yes.

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.

Device target and max sessions default values and ranges There are default values and ranges for device target and max sessions in the NMC NetWorker Administration window.

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

Recommende d sessions*

Range

AFTD (traditional storage)

4 32 1 - 32 1 - 1024

AFTD (including Data Domain CIFS/NFS)

4 32 1 - 10 1 - 1024

CloudBoost 10 80 1 - 10 1 - 200

Data Domain (DD Boost)

20 60 1 - 10 1 - 120

DD Cloud Tier 20 60 1 - 10 1 - 120

Backup Target

112 NetWorker 18.1 Administration Guide

Table 27 Default values and ranges for target and max sessions attributes (continued)

Device type Default target sessions

Default max sessions

Recommende d sessions*

Range

NDMP 4 512 1 - 32 1 - 1024

FTD (traditional) 4 32 1 - 16 1 - 1024

ProtectPoint 20 120 1 - 10 1 - 1024

VTL/Tape (traditional)

4 32 1 - 16 1 - 512

VTL/Tape (Data Domain / Deduplicated)

4 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 NetWorker Online Software Compatibility Matrix provides a list of supported volume managers.

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 (VHD/VHDx) files must be uncompressed and unencrypted. If the NetWorker AFTD DFA device is created on an ReFS volume, virtual hard disk (VHD/VHDx) files must not have the integrity bit set.

Backup Target

Advanced file type devices 113

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 108 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.

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:

Backup Target

114 NetWorker 18.1 Administration Guide

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 121 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):

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 108.

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.

Backup Target

Advanced file type devices 115

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. On the Review the Device Configuration page:

a. Review the settings.

b. Click Configure.

14. On the Check results page:

a. Review whether the devices were successfully configured or if any messages appeared.

b. Click Finish.

c. To change any of the settings, click Back to the correct wizard page.

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.

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.

Backup Target

116 NetWorker 18.1 Administration Guide

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.

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:

Backup Target

Advanced file type devices 117

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 108 provides additional details for Client Direct configurations.

Multiple devices for a single volume configuration on page 121 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 121 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).

Backup Target

118 NetWorker 18.1 Administration Guide

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.

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:

Backup Target

Advanced file type devices 119

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 nodes 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 108 provides additional details for Client Direct configurations.

Multiple devices for a single volume configuration on page 121 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.

Backup Target

120 NetWorker 18.1 Administration Guide

Multiple devices for a single volume configuration on page 121 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 servers local storage node) and two remote devices (rd) on remote storage nodes, the Name attributes for the three devices, each created separately, might be specified by different aliases as follows:

Backup Target

Advanced file type devices 121

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 devices max nsrmmd count attribute. Create and configure an AFTD on page 114 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 then 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 that is dedicated to AFTD backup devices only.

Backup Target

122 NetWorker 18.1 Administration Guide

NOTICE

If an existing volume is re-labeled, a warning is issued. The data that is previously stored on the volume is lost and this action cannot be undone. Mounting the volume without labeling provides access to previous data.

3. Select Mount after labeling and then 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 FullWaiting 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 servers Administration interface, click Server.

2. Right-click Notifications and select New.

3. In the Name field, type a unique name for this custom notification.

For example: First adv_full notice.

4. In the Event field, clear all choices except adv_file.

5. In the Priority field, clear all choices except Waiting.

6. In the Action field, type the full path of the custom script that is configured to expand disk space.

For example: /mybin/my_first_custom_script.

Backup Target

Advanced file type devices 123

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 the user indicates. The wait time after the default notification is approximately 10 minutes.

Procedure

1. In the servers Administration interface, click Server.

2. Right-click Notifications and select New.

3. In the Name field, type a unique name for this second custom notification.

For example: Second adv_full Notice.

4. In theEvent field, clear all choices except adv_file.

5. In the Priority field, clear all choices except Critical, Emergency, and Alert.

6. In theAction field, type 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.

Backup Target

124 NetWorker 18.1 Administration Guide

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.

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 NFS- mounted 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 devices 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.

Backup Target

Advanced file type devices 125

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.

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 devices 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 devices data, click Yes.

l To delete the device and erase the devices 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.

Backup Target

126 NetWorker 18.1 Administration Guide

Concurrent AFTD recovery operation limitations AFTD concurrent recovery currently has the following limitations:

l Not available to the Windows recover interface (winworkr). Use the recover command. The 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.

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 servers 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.

Backup Target

Advanced file type devices 127

DD Boost and Cloud Tier devices DD Boost and Cloud Tier devices are covered separately in the 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.

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.

Backup Target

128 NetWorker 18.1 Administration Guide

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.

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 NetWorker supports the use of LTO-4 hardware-based encryption, 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. 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. The NetWorker application does not perform encryption or manage the key management process. For example, NetWorker does not provide the ability to turn encryption on or off or manage the 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

Backup Target

Libraries and silos 129

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:

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.

Backup Target

130 NetWorker 18.1 Administration Guide

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.

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.

Backup Target

Solaris device considerations 131

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 28 Determining the major number value

Character HP-PB HSC or PCI

Block 75 -1 203 -1

Driver spt sctl

Class spt ctl

The value for majornum is the number in the Character column.

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 29 ioscan output when driver is configured

Class spt

I 0

H/W Path 10/4/4.6.0

Driver schgr

S/W State CLAIMED

H/W Type DEVICE

Description 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:

Backup Target

132 NetWorker 18.1 Administration Guide

Table 30 ioscan output when driver is not configured

Class unknown

I -1

H/W Path 10/4/4.6.0

Driver schgr

S/W State UNCLAIMED

H/W Type DEVICE

Description 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 (Jukebox), /dev/rac/ c0t1d0 scsidev@0.2.0:Quantum DLT4000 CC37 Tape, /dev/rmt/c0t2d0BESTnb scsidev@0.3.0:Quantum DLT4000 CC37 Tape, /dev/rmt/c0t3d0BESTnb scsidev@0.4.0:Quantum DLT4000 CC37 Tape, /dev/rmt/c0t4d0BESTnb scsidev@0.5.0:Quantum DLT4000 CC37 Tape, /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:

/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 drives 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)

Backup Target

HP-UX device considerations 133

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 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 NetWorker Installation Guide autochanger.

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.

Backup Target

134 NetWorker 18.1 Administration Guide

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.

l A volume in a jukebox device has priority over volume in a disk or tape device.

l A volume in a local disk device has priority over a volume in a local tape device.

l If two local disk are available, then the device less data sessions will have priority.

l if two local tapes devices have available volumes, then NetWorker will use the volume with the earliest label date.

l If two jukebox are available, then NetWorker will select the volume with the earliest label date..

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 ). 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 145 provides more information on Auto Media Management.

Backup Target

SCSI and VTL libraries 135

Note

You can manually change the mode of a volume to recyclable. Changing the volume mode on page 475 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 91 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 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, non- dedicated 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 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.

l If currently using DD OS 5.0.x, upgrade to DD OS 5.7 or later.

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

Backup Target

136 NetWorker 18.1 Administration Guide

(max sessions=4) results in deduplication ratios that are 12%-24% below the non- multiplexed rate (max sessions=1).

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 as follows:

l Max sessions=4 (32 maximum)

l Target sessions=4

l Device block size=512KB

Optimal 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.

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 the 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 that the specified pathname is enclosed in quotes.

Backup Target

SCSI and VTL libraries 137

Unix/Linux system examples.

touch /nsr/debug/nibmp touch /nsr/debug/nibmp_My Pool

Microsoft Windows system examples.

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 that is named , available on the 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 systems 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 non- rewinding, 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.

Backup Target

138 NetWorker 18.1 Administration Guide

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.

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 475 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

Backup Target

SCSI and VTL libraries 139

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 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 97 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 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 750. 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.

Backup Target

140 NetWorker 18.1 Administration Guide

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.

Adding a library resource

Procedure

1. In the servers 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.

Backup Target

SCSI and VTL libraries 141

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 130 if the Scan for Devices option does not detect more than 128 tape devices on Linux operating systems.

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 144 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.

Backup Target

142 NetWorker 18.1 Administration Guide

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 librarys Properties window.

Follow these guidelines when using barcode labels with the NetWorker software:

l 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.

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 librarys 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 librarys 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 143 provides more information.

Procedure

1. In the Administration window, click Devices.

2. Open the Libraries folder. The Libraries detail table appears.

Backup Target

SCSI and VTL libraries 143

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.

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 servers Administration interface, click the Devices button.

Backup Target

144 NetWorker 18.1 Administration Guide

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

To define the media library parallelism, use the Max parallelism attribute on the Configuration tab of the Library resource .

Media library parallelism allows you to define the maximum number of available devices for inventory and label operations.

It is recommended 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 want 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 Management 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:

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.

l Recycles volumes eligible for reuse that are loaded into the device.

Backup Target

SCSI and VTL libraries 145

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:

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.

Backup Target

146 NetWorker 18.1 Administration Guide

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 librarys properties after configuration.

Procedure

1. In the servers 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 78 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.

Label templates Several preconfigured label templates are supplied with the NetWorker software. These preconfigured label templates cannot be deleted. Naming label templates on page 78 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.

Backup Target

SCSI and VTL libraries 147

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.

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 librarys 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.

Backup Target

148 NetWorker 18.1 Administration Guide

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 librarys 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 NetWorker Command Reference Guideor the UNIX man pages.

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 172 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 devices 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.

Backup Target

SCSI and VTL libraries 149

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 servers 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.

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 servers NetWorker Administration interface, select View > Diagnostic Mode from the menu bar.

3. Click Devices.

Backup Target

150 NetWorker 18.1 Administration Guide

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 librarys drives are listed in the pane on the left in the Device column. The librarys slots are listed in the pane on the right.

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 librarys 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

Backup Target

SCSI and VTL libraries 151

knowledgeable of NetWorker users, as the consequences of using them can be unknown. For information about these commands, refer to the 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 servers 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 re-attempt 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

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.

Backup Target

152 NetWorker 18.1 Administration Guide

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.

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 159 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.

Backup Target

SCSI and VTL libraries 153

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 librarys 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 servers NetWorker Administration interface, click Devices.

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.

Backup Target

154 NetWorker 18.1 Administration Guide

4. Select the Timers tab.

5. Specify a value in the Idle Device Timeout attribute.

1. You can also override the librarys 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 servers 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 librarys 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 a volume makes it impossible for the NetWorker server to recover original data from that volume.

Procedure

1. In the Administration window, click Devices.

Backup Target

SCSI and VTL libraries 155

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 re-labeling. 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 143 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.

Backup Target

156 NetWorker 18.1 Administration Guide

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 librarys 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 60 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.

Backup Target

SCSI and VTL libraries 157

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 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 librarys 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 then 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.

Backup Target

158 NetWorker 18.1 Administration Guide

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 -P command to specify the ports from which to withdraw thevolumes. The nsrjb man page or NetWorker Command Reference Guide the for more information.

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 NetWorker Command Reference Guide 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 the status.

7. Click OK.

8. To review the result, select Monitoring > Log. 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 148 provides more information on using barcode labels.

Backup Target

SCSI and VTL libraries 159

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.

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.

Backup Target

160 NetWorker 18.1 Administration Guide

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 manufacturers software documentation.

Procedure

1. In the servers 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 drives 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.

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 servers 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 devices 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.

The following TapeAlert attributes are found in the devices Properties, on the Volume tab.

Backup Target

SCSI and VTL libraries 161

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 31 Tape alert severity

Severity Urgently requires user intervention

Risks data loss Explanatory

Critical X X

Warning X X

Informative X

The messages indicate tape and drive states related to tape drive read/write management, cleaning management, or drive hardware errors.

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.

Backup Target

162 NetWorker 18.1 Administration Guide

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:

n Out-of-date device firmware.

n Failure of the library to return its devices serial numbers.

l Autodetection failed to start on the storage nodes.

Procedure

1. Check Monitoring > Log for relevant messages.

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 149. 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 32 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.

Backup Target

SCSI and VTL libraries 163

Table 32 Common jbedit options (continued)

Option Description

-f Name of the device to be added or deleted.

-E Element address of the device to be added or deleted.

The 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 659. CDI must be enabled for this functionality. Setting the common device interface on page 171 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.

Backup Target

164 NetWorker 18.1 Administration Guide

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 152 provides details.

3. Rescan the library. Scanning for libraries and devices on page 142 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 163, or the UNIX man page for jbedit or the NetWorker Command Reference Guide provides more information about the jbedit command.

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

Backup Target

SCSI and VTL libraries 165

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 devices Properties.

Device calibration For information about the frequency and method for calibrating the loading mechanism for the device, refer to the library manufacturers 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.

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 servers 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 drives 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.

Backup Target

166 NetWorker 18.1 Administration Guide

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 servers 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 drives 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

where:

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 devices 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.

l 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.

Backup Target

SCSI and VTL libraries 167

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 systems 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:

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:

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

Backup Target

168 NetWorker 18.1 Administration Guide

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 166 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 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

Backup Target

SCSI and VTL libraries 169

Setting device parameters in the NetWorker Administration interface You can locate and change the device parameters in the Administration interface.

Procedure

1. In the servers 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 33 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_TY PE

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.

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.

Backup Target

170 NetWorker 18.1 Administration Guide

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.

Setting the common device interface Common device interface (CDI) allows the NetWorker server to send commands to tape devices. The CDI feature is not supported within an NDMP environment. You can set CDI support in the NetWorker Administration interface.

Procedure

1. In the servers 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.

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 you can disable the CDI feature by selecting the Not Used option, it can be time-consuming to disable CDI on a large number of devices.

In this situation, create an empty file named /nsr/debug directory and create an empty file that is named cdidisable. Then restart the NetWorker server. The presence of this file disables the use of CDI for that server and all the storage nodes that are controlled by that server.

Backup Target

SCSI and VTL libraries 171

Note

Use of CDI does not change what is written to tape. A tape that is written with CDI enabled can be read with CDI disabled. Conversely, a tape that is 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 Customer Service representative. If tape or SCSI issues occur while the CDI feature is enabled, contact Customer Service.

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 devices Properties window. The default value is 20. When the devices 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.

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

Backup Target

172 NetWorker 18.1 Administration Guide

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 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

Backup Target

Silo libraries 173

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 174 provides further details.

Configuring silo libraries Procedure

1. In the servers 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, except those libraries that are explicitly excluded in the library exclusion list during configuration.

Backup Target

174 NetWorker 18.1 Administration Guide

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.

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

Backup Target

Silo libraries 175

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 or later must be running on the ACSLS server to use this functionality.

The UNIX man pages for these commands, or see the NetWorker Command Reference Guide, which 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 silos 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 manufacturers 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 34 StorageTek environment variables

Silo model Environment variables

StorageTek For UNIX systems:

l CSI_HOSTNAME = name_of_ACSLS_system

Backup Target

176 NetWorker 18.1 Administration Guide

Table 34 StorageTek environment variables (continued)

Silo model Environment variables

The following commands should also be running on the system and can be in the NetWorker startup script:

l /mini_el &

l /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 volumes 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.

Backup Target

Silo libraries 177

The nsrjb UNIX man page or the NetWorker Command Reference Guide provide more information.

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 153 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 pools 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 147 and Barcode labels on page 148 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 time- consuming 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.

Backup Target

178 NetWorker 18.1 Administration Guide

To issue deposit and withdraw commands:

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:

n nsrjb -d -T Barcode n Ignore the error message that appears.

n nsrjb -a -T Barcode

Barcode IDs

A list of available barcode-labeled volumes is available from the silo management software. Refer to the silo manufacturers 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 UNIX man page and the NetWorker Command Reference Guide provides detailed information about the nsrjb command.

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 silos 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.

Backup Target

Silo libraries 179

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

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 the status.

8. Click OK.

The Library detail table displays the added volumes.

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 volumes 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 159 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 silos 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:

Backup Target

180 NetWorker 18.1 Administration Guide

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:

n tags specifies the tags or barcodes of volumes in a remote silo.

n -d performs the manual deposit.

NetWorker software interactions with a silo on page 173 provides more information on STLIs.

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 153 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 silos 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.

Backup Target

Silo libraries 181

l The Library Operation window displays this message:

The library operation has started.

l The Monitoring > Operations screen displays the silos 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 173 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 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 librarys 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 15 How library sharing works

Backup Target

182 NetWorker 18.1 Administration Guide

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 librarys 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.

Table 35 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 the completion of a drive cleaning operation and the ejection of the cleaning cartridge from the drive.

60 seconds

Idle Device Timeout The number of minutes NetWorker allows a device with a volume to be idle before automatically unmounting it. For specific

10 minutes

Backup Target

NetWorker hosts with shared libraries 183

Table 35 Library resource sleep attributes (continued)

Attribute Description Default value

devices, this value can be overridden. Unmounting volumes automatically (idle device timeout) on page 154 provides more information.

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.

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 DriveThe physical backup object, such as a tape drive, disk, or file.

l DeviceThe access path to the physical drive.

Backup Target

184 NetWorker 18.1 Administration Guide

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:

l Reduces storage costsYou 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 trafficYou can configure clients as SAN storage nodes that can send save sets over the SAN to shared drives.

l Provides fault toleranceWithin a SAN environment, you can configure hardware to eliminate a single point of failure.

l Provides configuration over a greater distanceYou can configure a system over a greater distance than with SCSI connections.

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 16 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.

Backup Target

Dynamic drive sharing 185

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 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.

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

Backup Target

186 NetWorker 18.1 Administration Guide

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 FC-SCSI 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.

The settings that relate to Reserve/Release and Persistent Reserve are found in a devices 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 devices 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.

Backup Target

Dynamic drive sharing 187

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 enterprises 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 systems 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 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 Hardware serial number

l Device type

l Worldwide part number (WWPN)

l Worldwide name (WWN)

Shared Devices attribute

The Shared Devices attribute appears on the Operations tab of a devices 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 36 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.

Backup Target

188 NetWorker 18.1 Administration Guide

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 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 is not 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.

Backup Target

File type devices 189

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 percent-used 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.

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 448 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 97 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

Backup Target

190 NetWorker 18.1 Administration Guide

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 servers 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.

Adding a stand-alone device manually Procedure

1. In the servers 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 servers 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 189 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.

Backup Target

Autodetecting and configuring a stand-alone tape drive 191

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:

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.

Backup Target

192 NetWorker 18.1 Administration Guide

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.

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

Backup Target

Mounting or unmounting a volume in a stand-alone tape drive 193

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 re-labeling. 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 143 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.

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.

Backup Target

194 NetWorker 18.1 Administration Guide

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 librarys 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 60 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.

Backup Target

Mounting uninventoried volumes 195

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 78 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.

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.

Backup Target

196 NetWorker 18.1 Administration Guide

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 833 provides information about how to display hidden attributes.

The UNIX man page and the NetWorker Command Reference Guide provides detailed information about these attributes.

NOTICE

Do not change time related attributes unless advised to do so by a Technical Support representative.

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 UNIX man page and the NetWorker Command Reference Guide provides detailed information about how to use these commands.

Backup Target

Verifying the label when a volume is unloaded 197

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 UNIX man page and the NetWorker Command Reference Guide provides detailed information about 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 To resolve the problem, use the nsrjb -H command to reset the autochanger.

Backup Target

198 NetWorker 18.1 Administration Guide

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:

l Sony AIT-2 and AIT-3

l IBM LTO Gen1

l HP LTO Gen1

l IBM LTO GEN2

Backup Target

Tapes do not fill to capacity 199

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 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 that the control port is correctly 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 142 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.

Backup Target

200 NetWorker 18.1 Administration Guide

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 librarys 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 197 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.

Backup Target

Changing the sleep times required for TZ89 drive types 201

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 423 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:

Backup Target

202 NetWorker 18.1 Administration Guide

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 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.

Backup Target

Recovering save sets from a VTL on a different NetWorker server 203

4. Use the mt command to ensure that the tape status is online. For example: mt - f device_name status When the mt command 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.

Backup Target

204 NetWorker 18.1 Administration Guide

CHAPTER 4

Data Protection Policies

This chapter contains the following topics:

l Overview of data protection policies................................................................206 l Designing data protection policies....................................................................207 l Policy Notifications.......................................................................................... 266 l Monitoring policy activity................................................................................. 267 l Policy log files.................................................................................................. 269 l Starting, stopping, and restarting workflows in NMC....................................... 271 l Starting actions in a workflow for an individual client........................................271 l Modifying data protection Policy resources..................................................... 272 l Managing policies from the command prompt..................................................285 l Troubleshooting policies...................................................................................293

Data Protection Policies 205

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-catalog 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, clone, 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 define the 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.

Data Protection Policies

206 NetWorker 18.1 Administration Guide

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 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 17 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 backupsIncludes file system backups, NDMP backups, NMDA backups, NMM backups, and Block Based Backups. The 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 backupsIncludes snapshot backups of supported storage arrays or appliances. You can clone snapshot data currently with the backup operation, or after the snapshot backup completes. The 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 backupsIncludes file system snapshots, and NAS snapshots. You can clone data after a snapshot backup job completes or concurrently. The NetWorker Snapshot Management Integration Guide describes how to configure data protection policies for snapshot backups.

l VMware backupsIncludes NetWorker VMware Protection with the vProxy appliance (NVP), VMware Backup Appliance (VBA) backups, VBA checkpoint backups for disaster recovery, and virtual machine backups. The NetWorker VMware Integration Guide describes how to configure data protection policies for NVP, VBA, VBA checkpoint, and virtual machine backups and clones.

Data Protection Policies

Designing data protection policies 207

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.

Note

n 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.

n The NetWorker data protection policy applies to scheduled backups only, and it does not apply to manual backups. Some NetWorker module backups might appear to be scheduled backups that are initiated by a policy backup action, but they are manual backups because they are initiated or converted by a database or application. The NetWorker Module for Databases and Applications Administration Guide and the NetWorker Module for SAP Administration Guide provides additional details.

Default data protection policies NetWorker provides you with preconfigured data protection policies that you can use immediately to protect the environment, modify to suit the environment, or use an example to create resources and configurations. To use these preconfigured data protection policies, you must add clients to the appropriate group resource.

Note

NetWorker also includes a preconfigured Server Protection policy to protect the NetWorker and NMC server databases.

Platinum policy The Platinum policy provides an example of a data protection policy for an environment that contains supported storage arrays or storage appliances and requires backup data redundancy. The policy contains one workflow with two actions, a snapshot backup action, followed by a clone action.

Figure 18 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.

Silver policy The Silver policy provides an example of a data protection policy for an environment that contains machines where file systems or applications are running and requires backup data redundancy.

Bronze policy The Bronze policy provides an example of a data protection policy for an environment that contains machines where file systems or applications are running.

Data Protection Policies

208 NetWorker 18.1 Administration Guide

Overview of configuring a new data protection policy The following steps are an overview of the tasks to complete, to create and configure a data protection policy.

Procedure

1. Create a policy resource.

When you create a policy, you specify the name and notification settings for the policy.

2. Within the policy, create a workflow resource 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 resource.

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 action resources for the workflow resource.

5. Configure client resources, to define the backup data that you want to protect, and then assign the client resources to a protection group.

Example 6 Example of a data protection policy with 2 workflows

The following figure illustrates a policy with two different workflows. Workflow 1 performs a probe action, then a backup of the client resources in Client group 1, and then a clone of the save sets from the backups. Workflow 2 performs a backup of the client resources in Dynamic client group 1, and then a clone of the save sets from the backup.

Data Protection Policies

Overview of configuring a new data protection policy 209

Example 6 Example of a data protection policy with 2 workflows (continued)

Figure 19 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. In 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.

Data Protection Policies

210 NetWorker 18.1 Administration Guide

4. In the Comment field, 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 the policy completes all the actions, select On Completion.

l To send a notification with information about each failed workflow and action, after the policy completes all the actions, select On Failure.

6. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

To send email messages or the smtpmail application on Windows, use the default mailer program on Linux:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, 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 subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs 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.

Data Protection Policies

Strategies for traditional backups 211

After you finish

Create the workflows and actions for the policy.

Create a workflow in a new policy Procedure

1. In the Administration window, click Protection.

2. In the left pane, expand Policies, and then select the policy that you created.

3. In the right pane, select Create a new workflow.

4. In the Name field, type the name of the workflow.

The maximum number of allowed characters for the Name field is 64. This name cannot contain spaces or special characters such as + or %.

5. In the Comment box, type a description for the workflow.

The maximum number of allowed 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 specify when to send a notification, select Set at policy level.

l To send notifications with information about each successful and failed workflow and action, after the workflow completes all the actions, select On Completion.

l To send notifications with information about each failed workflow and action, after the workflow completes all the actions, select On Failure.

7. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages, or use the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, 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...

Data Protection Policies

212 NetWorker 18.1 Administration Guide

where:

n -s subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

8. In the Running section, perform the following steps to specify when and how often the workflow runs:

a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, 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 starts, clear this option.

b. To start the workflow 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 starting at the time that is specified in the Start time attribute, clear this option.

c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.

The default value is 9:00 PM.

d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for this attribute in order for incremental transaction log backup of SQL databases to occur.

The default Interval attribute 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 specify the last start time in a defined interval period, use the spin boxes.

e. To specify 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, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow automatically starts every hour beginning at 7:00 PM. and the last start time is 11:00 PM.

9. 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.

Data Protection Policies

Strategies for traditional backups 213

Protection groups for traditional backups A protection groups for traditional backups identifies the client resources to back up.

Traditional backups support the following types of protection groups:

l Basic client groupA static list of client resources to back up.

l Dynamic client groupA dynamic list of client resources to back up. A dynamic client group automatically generates a list of the client resources that use a 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 basic client group

Use basic client groups to specify a static list of client resources for a traditional backup, a check connectivity action, or a probe action.

Before you begin

Create the policy and workflow resources in which to add the protection group to.

Procedure

1. In the Administration window, click Protection.

2. In the expanded left pane, right-click Groups and select New from the drop- down, or right-click an existing group and select Edit from the drop-down.

The Create Group or Edit Group dialog box appears, with the General tab selected.

3. In the Name attribute, type a name for the group.

The maximum number of characters for the group name is 64. This name cannot contain spaces or special characters such as + or %.

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. From the Policy-Workflow list, select the workflow that you want to assign the group to.

Data Protection Policies

214 NetWorker 18.1 Administration Guide

Note

You can also assign the group to a workflow when you create or edit a workflow.

7. (Optional) To specify the Restricted Datazone (RDZ) for the group, on the Restricted Datazones tab, select the RDZ from the list.

8. Click OK.

After you finish

Create Client resources. Assign clients to a protection group, by using the Client Configuration wizard or the General tab on the Client Properties page.

Creating a dynamic client group

Dynamic client groups automatically include 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 client 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 value.

Use dynamic client groups to specify a dynamic list of Client resources for a traditional backup, a probe action, a check connectivity action, or a server backup action.

Procedure

1. In the Administration window, click Protection.

2. In the expanded left pane, right-click Groups and select New from the drop- down, or right-click an existing group and select Edit from the drop-down.

The Create Group or Edit Group dialog box appears, with the General tab selected.

3. In the Name attribute, type a name for the group.

The maximum number of characters for the group name is 64. This name cannot contain spaces or special characters such as + or %.

Note

After you create a group, the Name attribute is read-only.

4. From the Group Type list, select Dynamic Clients. For steps 5 to 8, follow the instructions given in Creating a client group.

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 is 0 (zero), then a client backup is required. If the return code is 1, then a client backup is not required.

Data Protection Policies

Strategies for traditional backups 215

Only a backup action can follow a probe action.

Check connectivity A check connectivity action tests the connectivity between the clients and the NetWorker server before the start of a probe or backup action occurs. If the connectivity test fails, then the probe action and backup action does not start for 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 enables secure offsite storage, the transfer of data from one location to another, and the verification of backups.

You can configure a clone action to occur after a backup in a single workflow, or concurrently with a backup action in a single workflow. You can use save set and query groups to define a specific list of save sets to clone, in a separate workflow.

Note

The clone action clones the scheduled backup save sets only, and it does not clone the manual backup save sets. Some NetWorker module backups might appear to be scheduled backups that are initiated by a policy backup action, but they are manual backups because they are initiated or converted by a database or application. The NetWorker Module for Databases and Applications Administration Guide and the NetWorker Module for SAP Administration Guide provides more details.

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 supported actions 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 20 Replication using AMS

Workflow path from a traditional backup action The only action that can follow a traditional backup is a clone action.

Data Protection Policies

216 NetWorker 18.1 Administration Guide

Figure 21 Workflow path from a traditional backup action

Creating a check connectivity action

A check connectivity action tests the connectivity between the clients and the NetWorker server, usually before another action such as a backup occurs.

Before you begin

Create the policy and the 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 policy's workflow, and then perform one of the following tasks in the right pane to start the Policy Action wizard:

l If the action 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 Policy Action wizard opens on the Specify the Action Information page.

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, actions that occurs after a disabled action do not start, even if the subsequent options are enabled.

5. From the Action Type list, select Check Connectivity.

6. If you create the action as part of the workflow configuration, the workflow appears automatically in the Workflow box and the box is dimmed.

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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, and then select the Concurrent checkbox.

8. Specify 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. Specify the days to check connectivity with the client:

l To check connectivity on a specific day, click the Execute icon on the day.

Data Protection Policies

Strategies for traditional backups 217

l To skip a connectivity check on a specific day, click the Skip icon on the day.

l To check connectivity every day, select Execute from the list, and then click Make All.

The following table provides details about the icons.

Table 37 Schedule icons

Icon Label Description

Execute Check connectivity on this day.

Skip Do not check connectivity on this day.

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 the connectivity test is successful for 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 the connectivity test is successful for 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. This is applicable if multiple rollover is implemented at an action level.

For Direct-NDMP backups, set the parallelism value to the number of available NDMP drives.

If you set the parallelism attribute to a higher value, there will not be enough drives to support all the queued backup save sets. Large save sets might fail due to the inactivity timeout limit.

When NDMP groups back up simultaneously, divide the number of drives by the number of groups. Use this value for each of the parallelism attributes.

Setting the parallelism value for the group overrides the parallelism value that is defined for the NDMP clients.

15. From the Failure Impact list, specify what to do when a job fails:

Data Protection Policies

218 NetWorker 18.1 Administration Guide

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 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.

16. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0 (zero) indicates no amount of time.

17. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero) indicates no amount of time.

18. (Optional) In Start Time specify the time to start the action.

Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:

l DisabledDo not enforce an action start time. The action will start at the time defined by the workflow.

l AbsoluteStart the action at the time specified by the values in the spin boxes.

l RelativeStart the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.

19. (Optional) Configure overrides for the task that is scheduled on a specific day.

To specify the month, use the navigation buttons and the month list box. To specify 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, and 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, and then use the lists. Click Add Rules based override.

n To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules based override.

Data Protection Policies

Strategies for traditional backups 219

Note

n You can edit or add the rules in the Override field.

n To remove an override, delete the entry from the Override field.

20. Click Next.

The Action Configuration Summary page appears.

21. 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 NetWorker clients that use the probe. Create a client probe resource on the NetWorker server. 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.

Procedure

1. In the expanded left pane, select the policy's workflow, and then perform one of the following tasks in the right pane to start the Policy Action wizard:

l If the action 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 Policy Action wizard opens on the Specify the Action Information page.

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

Data Protection Policies

220 NetWorker 18.1 Administration Guide

from running when the policy or workflow that contains the action is started, clear this option.

Note

When you clear the Enabled option, actions that occurs after a disabled action do not start, even if the subsequent options are enabled.

5. From the Action Type list, select Probe.

6. If you create the action as part of the workflow configuration, the workflow appears automatically in the Workflow box and the box is dimmed.

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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, and then select the Concurrent checkbox.

8. Specify 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. Specify the days to probe the client:

l To perform a probe action on a specific day, click the Execute icon on the day.

l To skip a probe action, click the Skip icon on the day.

l To perform a probe action every day, select Execute from the list, and then click Make All.

The following table provides details on the icons.

Table 38 Schedule icons

Icon Label Description

Execute Perform the probe on this day.

Skip Do not perform a probe on this day.

10. Click Next.

The Specify the Probe Options page appears.

11. Specify when to start the subsequent backup action:

l To start the backup only if all the probes associated with client resources in the assigned group succeed, select the Start backup only after all probes succeed checkbox.

l To start the backup if any of the probes are associated with a client resource in the assigned group succeed, clear the Start backup only after all probes succeed checkbox.

12. Click Next.

The Specify the Advanced Options page appears.

Data Protection Policies

Strategies for traditional backups 221

13. In the Retries field, 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 does not retry a failed probe or backup action.

Note

The Retries option applies to probe actions, and the backup actions for the Traditional and Snapshot action types. If you specify a value for this option for other actions, NetWorker ignores the values.

14. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed probe or backup action. When the Retry Delay value is 0, NetWorker retries the failed probe or backup action immediately.

Note

The Retry Delay option 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 can try to respond to the server.

If the job does not respond within the specified time, the server considers the job a failure and NetWorker retries the job immediately to ensures that no time is lost due to failures.

Increase the timeout value if a backup consistently stops due to inactivity. Inactivity might 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 applies to probe actions, and the backup actions for the Traditional and Snapshot action types. If you specify a value for this option in other actions, NetWorker ignores the value.

16. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is implemented at an action level.

For Direct-NDMP backups, set the parallelism value to the number of available NDMP drives.

If you set the parallelism attribute to a higher value, there will not be enough drives to support all the queued backup save sets. Large save sets might fail due to the inactivity timeout limit.

When NDMP groups back up simultaneously, divide the number of drives by the number of groups. Use this value for each of the parallelism attributes.

Setting the parallelism value for the group overrides the parallelism value that is defined for the NDMP clients.

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.

Data Protection Policies

222 NetWorker 18.1 Administration Guide

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 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. Do not change the default selections for the Notification group box. NetWorker does not support notifications for probe actions and ignores and specified values.

19. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0 (zero) indicates no amount of time.

20. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero) indicates no amount of time.

21. (Optional) In Start Time specify the time to start the action.

Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:

l DisabledDo not enforce an action start time. The action will start at the time defined by the workflow.

l AbsoluteStart the action at the time specified by the values in the spin boxes.

l RelativeStart the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.

22. (Optional) Configure overrides for the task that is scheduled on a specific day.

To specify the month, use the navigation buttons and the month list box. To specify 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, and 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, and then use the lists. Click Add Rules based override.

n To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules based override.

Data Protection Policies

Strategies for traditional backups 223

Note

n You can edit or add the rules in the Override field.

n To remove an override, delete the entry from the Override field.

23. Click Next.

The Action Configuration Summary page appears.

24. 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

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:

n Probe

n Check connectivity

Procedure

1. In the expanded left pane, select the policy's workflow, and then perform one of the following tasks in the right pane to start the Policy Action wizard:

l If the action 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 Policy Action wizard opens on the Specify the Action Information page.

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, actions that occurs after a disabled action do not start, even if the subsequent 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. (Optional) From the Force Backup Level list select a backup level.

For workflows that have more than one scheduled backup within a 24-hour period, use the Force Backup Level attribute to allow more than one backup to occur at two different backup levels in a 24-hour period. When you select a backup level in the Force Backup Level attribute, the first backup is performed

Data Protection Policies

224 NetWorker 18.1 Administration Guide

at the scheduled backup level. Each subsequent occurrence of the backup action in the next 24 hours occurs at the level defined in the Force Backup Level attribute. For example, if the level defined by the schedule is Full and the Force Backup Level attribute is set to Incr, the first backup started by the action occurs at a level full and subsequent backups, within 24 hours of the start of the full backup are incremental. By default this option is cleared, which means that if the action runs multiple backup operations in a 24 period, all the backups occur at the scheduled backup level.

8. If you create the action as part of the workflow configuration, the workflow appears automatically in the Workflow box and the box is dimmed.

9. 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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, and then select the Concurrent checkbox.

10. Specify 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.

11. To specify the backup level to perform, click the icon on each day.

The following table provides details about the backup level that each icon represents.

Table 39 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.

Logs Only Perform a backup of only database transaction logs.

Incremental Synthetic Full

Perform an incremental synthetic backup on this day. An incremental synthetic full backup includes all data that changed since the last full

Data Protection Policies

Strategies for traditional backups 225

Table 39 Schedule icons (continued)

Icon Label Description

Note

Not supported for NDMP.

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.

NetWorker does not support the use of synthetic full backup levels for NDMP data.

Celerra, Isilon, VNX, Unity, and NetApp filers with NDMP version 4 or later support token-based backups (TBB) to perform NDMP full and incremental backups. NetWorker supports the same number of incremental levels that the NAS vendor supports. Celerra, Isilon, and NetApp documentation provide the maximum number of incremental levels that the TBB incremental backup can support.

When you configure TBB after you update the NetWorker server from 7.6 SP1 or earlier, the first incremental backup does not occur until after one complete full backup.

Filers that do not support TBB, do not support incremental backups. If you select the level Incr, the NetWorker server performs a full backup.

Verify that the NAS storage vendor supports NDMP incremental backups before you use this feature.

12. Click Next.

The Specify the Backup Options page appears.

13. From the Destination Storage Node box, select the storage node with the devices on which to store the backup data.

14. From the Destination Pool box, select the media pool in which to store the backup data.

15. 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.

When you define the retention policy an NDMP client, consider the amount of disk space that is required for the client file index. NDMP clients with several thousands of small files have significantly larger client file indexes on the NetWorker server than a non-NDMP client. A long retention policy for an NDMP client increases disk space requirements on the file system that contains the client file indexes.

16. 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:

Data Protection Policies

226 NetWorker 18.1 Administration Guide

l Client Can OverrideThe values in the Client resource for Schedule, Pool, Retention policy, and the Storage Node attributes take precedence over the values that are defined in the equivalent Action resource attributes.

Note

If the NetWorker policy action schedule is set to the Skip backup level, the Client can Override option is not honored. For NetWorker to consider the Client can Override option, change the action schedule to a different level.

l Client Can Not OverrideThe 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 RulesThis 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.

17. Click Next.

The Specify the Advanced Options page appears.

18. In the Retries field, 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 does not retry a failed probe or backup action.

Note

The Retries option applies to probe actions, and the backup actions for the Traditional and Snapshot action types. If you specify a value for this option for other actions, NetWorker ignores the values.

19. In the Retry Delay field, specify a delay in seconds to wait before retrying a failed probe or backup action. When the Retry Delay value is 0, NetWorker retries the failed probe or backup action immediately.

Note

The Retry Delay option 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 Inactivity Timeout field, specify the maximum number of minutes that a job run by an action can try to respond to the server.

If the job does not respond within the specified time, the server considers the job a failure and NetWorker retries the job immediately to ensures that no time is lost due to failures.

Increase the timeout value if a backup consistently stops due to inactivity. Inactivity might occur for backups of large save sets, backups of save sets with large sparse files, and incremental backups of many small static files.

Data Protection Policies

Strategies for traditional backups 227

Note

The Inactivity Timeout option applies to probe actions, and the backup actions for the Traditional and Snapshot action types. If you specify a value for this option in other actions, NetWorker ignores the value.

21. In the Parallelism field, specify the maximum number of concurrent operations for the action. This is applicable if multiple rollover is implemented at an action level.

For Direct-NDMP backups, set the parallelism value to the number of available NDMP drives.

If you set the parallelism attribute to a higher value, there will not be enough drives to support all the queued backup save sets. Large save sets might fail due to the inactivity timeout limit.

When NDMP groups back up simultaneously, divide the number of drives by the number of groups. Use this value for each of the parallelism attributes.

Setting the parallelism value for the group overrides the parallelism value that is defined for the NDMP clients.

22. 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 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.

23. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0 (zero) indicates no amount of time.

24. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero) indicates no amount of time.

25. (Optional) In Start Time specify the time to start the action.

Use the spin boxes to set the hour and minute values, and select one of the following options from the drop-down list:

l DisabledDo not enforce an action start time. The action will start at the time defined by the workflow.

l AbsoluteStart the action at the time specified by the values in the spin boxes.

Data Protection Policies

228 NetWorker 18.1 Administration Guide

l RelativeStart the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.

26. (Optional) Configure overrides for the task that is scheduled on a specific day.

To specify the month, use the navigation buttons and the month list box. To specify 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, and 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, and then use the lists. Click Add Rules based override.

n To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules based override.

Note

n You can edit or add the rules in the Override field.

n To remove an override, delete the entry from the Override field.

27. From the Send Notifications list box, select whether to send notifications for the action:

l To use the notification configuration that is defined in the Policy resource to send the notification, select Set at 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.

28. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, type the

following command:

Data Protection Policies

Strategies for traditional backups 229

/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 subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

29. Click Next.

The Action Configuration Summary page appears.

30. 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 policy's workflow, and then perform one of the following tasks in the right pane to start the Policy Action wizard:

l If the action 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 Policy Action wizard opens on the Specify the Action Information page.

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, actions that occurs after a disabled action do not start, even if the subsequent options are enabled.

5. From the Action Type list, select Clone.

Data Protection Policies

230 NetWorker 18.1 Administration Guide

6. If you create the action as part of the workflow configuration, the workflow appears automatically in the Workflow box and the box is dimmed.

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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, and then select the Concurrent checkbox.

8. Specify 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. Specify the days to perform cloning:

l To clone on a specific day, click the Execute icon on the day.

l To skip a clone on a specific day, click the Skip icon on the day.

l To check connectivity every day, select Execute from the list, and then click Make All.

The following table provides details on the icons.

Table 40 Schedule icons

Icon Label Description

Execute Perform cloning on this day.

Skip Do not perform cloning on this day.

10. Click Next.

The Specify the Clone Options page appears.

11. In the Data Movement section, define the volumes and devices to which NetWorker sends the cloned 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 box, select the option to instruct NetWorker to move the data from the source volume to the destination volume after clone operation completes. This is equivalent to staging the save sets.

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 section, 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:

Data Protection Policies

Strategies for traditional backups 231

a. Time filterIn the Time section, specify the time range in which NetWorker searches for eligible save sets to clone in the media database. Use the spin boxes to specify the start time and the end time. The Time filter list includes the following options to define how NetWorker determines save set eligibility, based on the time criteria:

l Do Not FilterNetWorker inspects the save sets in the media database to create a clone save set list that meets the time filter criteria.

l AcceptThe clone save set list includes save sets that are saved within the time range and meet all the other defined filter criteria.

l RejectThe clone save set list does not include save sets that are saved within the time range and meet all the other defined filter criteria.

b. Save Set filterIn the Save Set section, specify whether to include or exclude ProtectPoint and Snapshot save sets, when NetWorker searches for eligible save sets to clone in the media database. The Save Set filter list includes to the following options define how NetWorker determines save set eligibility, based on the save set filter criteria:

l Do Not FilterNetWorker inspects the save sets in the media database to create a clone save set list that meets the save set filter criteria.

l AcceptThe clone save set list includes eligible ProtectPoint save sets or Snapshot save sets, when you also enable the ProtectPoint checkbox or Snapshot checkbox.

l RejectThe clone save set list does not include eligible ProtectPoint save sets and Snapshot save sets when you also enable the ProtectPoint checkbox or Snapshot checkbox.

Note

For NAS device, only Snapshot save set is applicable.

c. Clients filterIn the Client section, specify a list of clients to include or exclude, when NetWorker searches for eligible save sets to clone in the media database. The Client filter list includes the following options, which define how NetWorker determines save set eligibility, based on the client filter criteria:

l Do Not FilterNetWorker inspects the save sets that are associated with the clients in the media database, to create a clone save set list that meets the client filter criteria.

l AcceptThe clone save set list includes eligible save sets for the selected clients.

l RejectThe clone save set list does not include eligible save sets for the selected clients.

d. Levels filterIn the Levels section, specify 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 the following options define how NetWorker determines save set eligibility, based on the level filter criteria:

l Do Not FilterNetWorker inspects the save sets regardless of the level in the media database, to create a clone save set list that meets all the level filter criteria.

l AcceptThe clone save set list includes eligible save sets with the selected backup levels.

Data Protection Policies

232 NetWorker 18.1 Administration Guide

l RejectThe clone save set list does not include eligible save sets with the selected backup levels.

Note

For NAS device, only full backup level is applicable.

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. This is applicable if multiple rollover is implemented at an action level.

For Direct-NDMP backups, set the parallelism value to the number of available NDMP drives.

If you set the parallelism attribute to a higher value, there will not be enough drives to support all the queued backup save sets. Large save sets might fail due to the inactivity timeout limit.

When NDMP groups back up simultaneously, divide the number of drives by the number of groups. Use this value for each of the parallelism attributes.

Setting the parallelism value for the group overrides the parallelism value that is defined for the NDMP clients.

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 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 To use the notification configuration that is defined in the Policy resource to send the notification, select Set at policy level.

Data Protection Policies

Strategies for traditional backups 233

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.

18. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, 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 subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

19. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0 (zero) indicates no amount of time.

20. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero) indicates no amount of time.

21. (Optional) In the Start Time option, specify the time to start the action.

Use the spin boxes to set the hour and minute values, and select one of the following options from the list box:

l DisabledDo not enforce an action start time. The action will start at the time defined by the workflow.

Data Protection Policies

234 NetWorker 18.1 Administration Guide

l AbsoluteStart the action at the time specified by the values in the spin boxes.

l RelativeStart the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.

22. (Optional) Configure overrides for the task that is scheduled on a specific day.

To specify the month, use the navigation buttons and the month list box. To specify 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, and 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, and then use the lists. Click Add Rules based override.

n To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules based override.

Note

n You can edit or add the rules in the Override field.

n To remove an override, delete the entry from the Override field.

23. Click Next.

The Action Configuration Summary page appears.

24. 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 After you create actions for a workflow, in the Administration interface, you can see a map provides a visual representation of the actions on the right side of the Protection window.

The following figure illustrates the visual representation of a sample workflow for a traditional backup.

Figure 22 Visual representation of a workflow

The oval icon specifies the group to which the workflow applies. The rounded rectangle icons identify actions. The parallelogram icons identify the destination pool for the action.

Data Protection Policies

Strategies for traditional backups 235

l You can adjust the display of the visual representation by right-clicking and selecting one of the following options:

n Zoom InIncrease the size of the visual representation.

n Zoom OutDecrease the size of the visual representation.

n Zoom AreaLimit the display to a single section of the visual representation.

n Fit ContentFit the visual representation to the window area.

n ResetReset the visual representation to the default settings.

n OverviewView a separate dialog box with a high-level view of the visual representation and a legend of the icons.

l You can view and edit the properties for the group, action, or destination pool by right-clicking the icon for the item, and then select Properties.

l You can create a group, action, or destination pool by right-clicking the icon for the item, and then select 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 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_stage on Linux.

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.

cst folder is not listed as save set under Server Protection - NMC server backup for linux servers. Only /nsr/nmc/nmcdb_stage is listed under backed up save set. Backup of cst folder is taken internally, which can be verified in Recovery Wizard after the Server Protection policy backup is succeeded.

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.

Data Protection Policies

236 NetWorker 18.1 Administration Guide

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.

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 ExpirationAn expire action to mark expired save sets as recyclable.

l Server database backupA 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.

Data Protection Policies

Strategies for server backup and maintenance 237

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:

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.

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 enables secure offsite storage, the transfer of data from one location to another, and the verification of backups.

You can configure a clone action to occur after a backup in a single workflow, or concurrently with a backup action in a single workflow. You can use save set and query groups to define a specific list of save sets to clone, in a separate workflow.

Data Protection Policies

238 NetWorker 18.1 Administration Guide

Note

The clone action clones the scheduled backup save sets only, and it does not clone the manual backup save sets. Some NetWorker module backups might appear to be scheduled backups that are initiated by a policy backup action, but they are manual backups because they are initiated or converted by a database or application. The NetWorker Module for Databases and Applications Administration Guide and the NetWorker Module for SAP Administration Guide provides more details.

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 enables secure offsite storage, the transfer of data from one location to another, and the verification of backups.

You can configure a clone action to occur after a backup in a single workflow, or concurrently with a backup action in a single workflow. You can use save set and query groups to define a specific list of save sets to clone, in a separate workflow.

Note

The clone action clones the scheduled backup save sets only, and it does not clone the manual backup save sets. Some NetWorker module backups might appear to be scheduled backups that are initiated by a policy backup action, but they are manual backups because they are initiated or converted by a database or application. The NetWorker Module for Databases and Applications Administration Guide and the NetWorker Module for SAP Administration Guide provides more details.

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 the connectivity between the clients and the NetWorker server before the start of a probe or backup action occurs. If the connectivity test fails, then the probe action and backup action does not start for the client.

Data Protection Policies

Strategies for server backup and maintenance 239

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 supported actions 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.

Figure 23 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 24 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. It is recommended 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.

Visual representation of workflows After you create actions for a workflow, in the Administration interface, you can see a map provides a visual representation of the actions on the right side of the Protection window.

The following figure illustrates the visual representation of the Server Protection workflows.

Data Protection Policies

240 NetWorker 18.1 Administration Guide

Figure 25 Visual representation of the Server Protection workflows

The oval icon specifies the group to which the workflow applies. The rounded rectangle icons identify actions. 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 You can adjust the display of the visual representation by right-clicking and selecting one of the following options:

n Zoom InIncrease the size of the visual representation.

n Zoom OutDecrease the size of the visual representation.

n Zoom AreaLimit the display to a single section of the visual representation.

n Fit ContentFit the visual representation to the window area.

n ResetReset the visual representation to the default settings.

n OverviewView a separate dialog box with a high-level view of the visual representation and a legend of the icons.

l You can view and edit the properties for the group, action, or destination pool by right-clicking the icon for the item, and then select Properties.

l You can create a group, action, or destination pool by right-clicking the icon for the item, and then select New.

Strategies for cloning You can use scheduled cloning or action based (automatic) cloning to manage your data.

l Scheduled cloningYou can have a policy, and a workflow followed by a clone action. The workflow is associated with a dynamic group. In other words, a Query or Save set protection group.

l Action based (automatic) cloningYou can have a policy, and a workflow followed by a backup and a clone action. The clone action can be configured as concurrent or sequential.

n SequentialWhen the backup action configured for a policy or workflow is triggered, backup copies are created in the selected backup pool. However, the

Data Protection Policies

Strategies for cloning 241

clone action is triggered only after backup copies are created for all the selected save sets. For example, If there are save sets numbered 1 to 100, backup copies are created in order. The clone action is triggered only after the backup copy is created for save set 100.

Note

Sequential cloning is the preferred cloning method.

n ConcurrentWhen the backup action configured for a policy or workflow is triggered, backup copies are created in the selected backup pool. The clone action is triggered even if only a single back up copy is created from the selected save sets. For example, If there are save sets numbered 1 to 100, backup copies are created in order. The clone action for save set 1 is triggered as soon as the backup copy for save set 1 is created. However, for performance optimization, clones for save sets are triggered in batches.

You can also use automated multi-streaming (AMS) when cloning your data to speed up the replication process.

If you are replicating save sets between two Data Domain devices on different machines, replication using NetWorker takes longer because each save set uses a single stream. The use of automated multi-streaming (AMS) splits up large files (files larger than 3.5 GiB) into multiple smaller 2 GiB slices, replicates those slices individually, and recreates the original large file on the destination DDR using those slices.

The following diagram illustrates replication using AMS.

Figure 26 Replication using AMS

AMS is supported only if:

l Both the source and destination Data Domain systems support the virtual synthetic capability (DDOS 5.5 and later)

l The save set file being copied is large enough for the use of AMS to provide an improvement over normal replication

Enable AMS, if the underlying bandwidth between two DDRs is 10Gbps. Because the use of AMS creates multiple streams, there must be enough bandwidth between the two DDRs being used for the clone workflow.

The nsrcloneconfig file enables you to add debug flags, control cloning sessions, and use the AMS functionality. It must be manually created under the /nsr/debug folder.

By default, AMS is disabled. To enable AMS, ensure that the ams_enabled flag is set to Yes.

The following table describes the nsrcloneconfig file details and their default values.

Data Protection Policies

242 NetWorker 18.1 Administration Guide

Table 41 nsrcloneconfig file details

Settings Default value

Description

ams_enabled Yes Enables or disables AMS support. The value can be Yes or No.

ams_slice_size_factor 31 Allows you to change the slice size factor value. The slice size factor corresponds to the size of the slices desired, specified by a number of bits. For example, if the slice size factor is 28, the desired slice size is 2^28, or 256 MiB. The default value is 31, meaning the desired slice size is 2^31, or 2 GiB. The default value of 31 provides the best performance during chopping and joining.

ams_preferred_slice_count 0 Allows you to change the preferred slice count. There is no maximum value.

ams_min_concurrent_slice_count 1 Allows you to increase the minimum number of concurrent file copies. If the specified value is less than the default minimum value, the default value is used.

ams_max_concurrent_slice_count 20 Allows you to decrease the maximum number of concurrent file copies. If the specified value exceeds the default maximum value, the default value is used.

ams_force_multithreaded No Force AMS to use threads even when the DDRs support multi-file copies. Because the multi-file workflow is faster, this is only useful for explicitly testing the multithreaded workflow. The value can be Yes or No.

Debug 9

Note

The Backup Data Management chapter describes how you can clone save sets manually by using the nsrclone command.

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.

Data Protection Policies

Strategies for cloning 243

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 groupUse 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 groupUse 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 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. In this case, concurrent cloning can be enabled.

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 field, type a name for the group.

4. From the Group Type list, select Save Set ID List.

5. In the Comment field, type a description of the group.

6. (Optional) To associate the group with a workflow, from the Workflow (Policy) list, select the workflow.

Data Protection Policies

244 NetWorker 18.1 Administration Guide

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) field, 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 field, type a name for the group.

4. From the Group Type list, select Save Set Query.

5. In the Comment field, 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.

Table 42 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 time period, select Up to.

Backup level In the Filter save sets by level section, next to the backup level for

the save set, select the full checkbox.

Note

Only the full backup level is applicable for network-attached storage (NAS) devices.

Data Protection Policies

Strategies for cloning 245

Table 42 Save set criteria (continued)

Criteria Description

Limit the number of clones

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. By default, the value is set to 1, and cannot be changed for NAS or Block.

Note

When this criteria is set to 1, which is the default value, you may experience volume outage issues with Data Domain and advanced file type devices.

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 field, 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.

Creating a policy

Procedure

1. In 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.

Data Protection Policies

246 NetWorker 18.1 Administration Guide

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 field, 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 the policy completes all the actions, select On Completion.

l To send a notification with information about each failed workflow and action, after the policy completes all the actions, select On Failure.

6. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

To send email messages or the smtpmail application on Windows, use the default mailer program on Linux:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, 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 subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

Data Protection Policies

Strategies for cloning 247

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.

Create a workflow in a new policy

Procedure

1. In the Administration window, click Protection.

2. In the left pane, expand Policies, and then select the policy that you created.

3. In the right pane, select Create a new workflow.

4. In the Name field, type the name of the workflow.

The maximum number of allowed characters for the Name field is 64. This name cannot contain spaces or special characters such as + or %.

5. In the Comment box, type a description for the workflow.

The maximum number of allowed 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 specify when to send a notification, select Set at policy level.

l To send notifications with information about each successful and failed workflow and action, after the workflow completes all the actions, select On Completion.

l To send notifications with information about each failed workflow and action, after the workflow completes all the actions, select On Failure.

7. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages, or use the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, type the

following command:

/usr/sbin/sendmail -v recipient_email "subject_text"

Data Protection Policies

248 NetWorker 18.1 Administration Guide

l On Windows, type the following command:

smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...

where:

n -s subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

8. In the Running section, perform the following steps to specify when and how often the workflow runs:

a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, 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 starts, clear this option.

b. To start the workflow 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 starting at the time that is specified in the Start time attribute, clear this option.

c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.

The default value is 9:00 PM.

d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for this attribute in order for incremental transaction log backup of SQL databases to occur.

The default Interval attribute 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 specify the last start time in a defined interval period, use the spin boxes.

e. To specify 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, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow automatically starts every hour beginning at 7:00 PM. and the last start time is 11:00 PM.

9. To create the workflow, click OK.

Data Protection Policies

Strategies for cloning 249

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 27 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 policy's workflow, and then perform one of the following tasks in the right pane to start the Policy Action wizard:

l If the action 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 Policy Action wizard opens on the Specify the Action Information page.

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, actions that occurs after a disabled action do not start, even if the subsequent options are enabled.

5. From the Action Type list, select Clone.

6. If you create the action as part of the workflow configuration, the workflow appears automatically in the Workflow box and the box is dimmed.

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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, and then select the Concurrent checkbox.

Data Protection Policies

250 NetWorker 18.1 Administration Guide

8. Specify 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. Specify the days to perform cloning:

l To clone on a specific day, click the Execute icon on the day.

l To skip a clone on a specific day, click the Skip icon on the day.

l To check connectivity every day, select Execute from the list, and then click Make All.

The following table provides details on the icons.

Table 43 Schedule icons

Icon Label Description

Execute Perform cloning on this day.

Skip Do not perform cloning on this day.

10. Click Next.

The Specify the Clone Options page appears.

11. In the Data Movement section, define the volumes and devices to which NetWorker sends the cloned 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 box, select the option to instruct NetWorker to move the data from the source volume to the destination volume after clone operation completes. This is equivalent to staging the save sets.

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 section, 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 filterIn the Time section, specify the time range in which NetWorker searches for eligible save sets to clone in the media database. Use the spin boxes to specify the start time and the end time. The Time filter list includes the following options to define how NetWorker determines save set eligibility, based on the time criteria:

l Do Not FilterNetWorker inspects the save sets in the media database to create a clone save set list that meets the time filter criteria.

Data Protection Policies

Strategies for cloning 251

l AcceptThe clone save set list includes save sets that are saved within the time range and meet all the other defined filter criteria.

l RejectThe clone save set list does not include save sets that are saved within the time range and meet all the other defined filter criteria.

b. Save Set filterIn the Save Set section, specify whether to include or exclude ProtectPoint and Snapshot save sets, when NetWorker searches for eligible save sets to clone in the media database. The Save Set filter list includes to the following options define how NetWorker determines save set eligibility, based on the save set filter criteria:

l Do Not FilterNetWorker inspects the save sets in the media database to create a clone save set list that meets the save set filter criteria.

l AcceptThe clone save set list includes eligible ProtectPoint save sets or Snapshot save sets, when you also enable the ProtectPoint checkbox or Snapshot checkbox.

l RejectThe clone save set list does not include eligible ProtectPoint save sets and Snapshot save sets when you also enable the ProtectPoint checkbox or Snapshot checkbox.

Note

For NAS device, only Snapshot save set is applicable.

c. Clients filterIn the Client section, specify a list of clients to include or exclude, when NetWorker searches for eligible save sets to clone in the media database. The Client filter list includes the following options, which define how NetWorker determines save set eligibility, based on the client filter criteria:

l Do Not FilterNetWorker inspects the save sets that are associated with the clients in the media database, to create a clone save set list that meets the client filter criteria.

l AcceptThe clone save set list includes eligible save sets for the selected clients.

l RejectThe clone save set list does not include eligible save sets for the selected clients.

d. Levels filterIn the Levels section, specify 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 the following options define how NetWorker determines save set eligibility, based on the level filter criteria:

l Do Not FilterNetWorker inspects the save sets regardless of the level in the media database, to create a clone save set list that meets all the level filter criteria.

l AcceptThe clone save set list includes eligible save sets with the selected backup levels.

l RejectThe clone save set list does not include eligible save sets with the selected backup levels.

Note

For NAS device, only full backup level is applicable.

Data Protection Policies

252 NetWorker 18.1 Administration Guide

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. This is applicable if multiple rollover is implemented at an action level.

For Direct-NDMP backups, set the parallelism value to the number of available NDMP drives.

If you set the parallelism attribute to a higher value, there will not be enough drives to support all the queued backup save sets. Large save sets might fail due to the inactivity timeout limit.

When NDMP groups back up simultaneously, divide the number of drives by the number of groups. Use this value for each of the parallelism attributes.

Setting the parallelism value for the group overrides the parallelism value that is defined for the NDMP clients.

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 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 To use the notification configuration that is defined in the Policy resource to send the notification, select Set at 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.

18. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

Data Protection Policies

Strategies for cloning 253

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, 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 subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

19. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0 (zero) indicates no amount of time.

20. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero) indicates no amount of time.

21. (Optional) In the Start Time option, specify the time to start the action.

Use the spin boxes to set the hour and minute values, and select one of the following options from the list box:

l DisabledDo not enforce an action start time. The action will start at the time defined by the workflow.

l AbsoluteStart the action at the time specified by the values in the spin boxes.

l RelativeStart the action after the period of time defined in the spin boxes has elapsed after the start of the workflow.

22. (Optional) Configure overrides for the task that is scheduled on a specific day.

Data Protection Policies

254 NetWorker 18.1 Administration Guide

To specify the month, use the navigation buttons and the month list box. To specify 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, and 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, and then use the lists. Click Add Rules based override.

n To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules based override.

Note

n You can edit or add the rules in the Override field.

n To remove an override, delete the entry from the Override field.

23. Click Next.

The Action Configuration Summary page appears.

24. 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 a clone workflow

After you create actions for a workflow, in the Administration interface, you can see a map provides a visual representation of the actions on the right side of the Protection window.

The following figure illustrates the visual representation of a clone workflow.

Figure 28 Visual representation of a clone workflow

The oval icon specifies the group to which the workflow applies. The rounded rectangle icons identify actions. 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 You can adjust the display of the visual representation by right-clicking and selecting one of the following options:

n Zoom InIncrease the size of the visual representation.

n Zoom OutDecrease the size of the visual representation.

n Zoom AreaLimit the display to a single section of the visual representation.

Data Protection Policies

Strategies for cloning 255

n Fit ContentFit the visual representation to the window area.

n ResetReset the visual representation to the default settings.

n OverviewView a separate dialog box with a high-level view of the visual representation and a legend of the icons.

l You can view and edit the properties for the group, action, or destination pool by right-clicking the icon for the item, and then select Properties.

l You can create a group, action, or destination pool by right-clicking the icon for the item, and then select 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.

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 29 Example of a policy with separate workflows for backup and cloning

Data Protection Policies

256 NetWorker 18.1 Administration Guide

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:

l Save set groupUse 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 groupUse 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 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. In this case, concurrent cloning can be enabled.

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 field, type a name for the group.

Data Protection Policies

Strategies for cloning 257

4. From the Group Type list, select Save Set ID List.

5. In the Comment field, 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) field, 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 field, type a name for the group.

4. From the Group Type list, select Save Set Query.

5. In the Comment field, 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.

Table 44 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 time period, select Up to.

Backup level In the Filter save sets by level section, next to the backup level for

the save set, select the full checkbox.

Data Protection Policies

258 NetWorker 18.1 Administration Guide

Table 44 Save set criteria (continued)

Criteria Description

Note

Only the full backup level is applicable for network-attached storage (NAS) devices.

Limit the number of clones

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. By default, the value is set to 1, and cannot be changed for NAS or Block.

Note

When this criteria is set to 1, which is the default value, you may experience volume outage issues with Data Domain and advanced file type devices.

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 field, 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.

Data Protection Policies

Strategies for cloning 259

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 allowed characters for the Name field is 64. This name cannot contain spaces or special characters such as + or %.

5. In the Comment box, type a description for the workflow.

The maximum number of allowed 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 specify when to send a notification, select Set at policy level.

l To send notifications with information about each successful and failed workflow and action, after the workflow completes all the actions, select On Completion.

l To send notifications with information about each failed workflow and action, after the workflow completes all the actions, select On Failure.

7. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, 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:

Data Protection Policies

260 NetWorker 18.1 Administration Guide

n -s subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

8. In the Running section, perform the following steps to specify when and how often the workflow runs:

a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, 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 starts, clear this option.

b. To start the workflow 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 starting at the time that is specified in the Start time attribute, clear this option.

c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.

The default value is 9:00 PM.

d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for this attribute in order for incremental transaction log backup of SQL databases to occur.

The default Interval attribute 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 specify the last start time in a defined interval period, use the spin boxes.

e. To specify 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, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow automatically starts every hour beginning at 7:00 PM. 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.

Data Protection Policies

Strategies for cloning 261

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, actions that occurs after a disabled action do not start, even if the subsequent 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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, and then select the Concurrent checkbox.

16. Specify 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. Specify the days to perform cloning:

l To clone on a specific day, click the Execute icon on the day.

l To skip a clone on a specific day, click the Skip icon on the day.

l To check connectivity every day, select Execute from the list, and then click Make All.

The following table provides details on the icons.

Table 45 Schedule icons

Icon Label Description

Execute Perform cloning on this day.

Skip Do not perform cloning on this day.

18. Click Next.

The Specify the Clone Options page appears.

19. In the Data Movement section, define the volumes and devices to which NetWorker sends the cloned 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 box, select the option to instruct NetWorker to move the data from the source volume to

Data Protection Policies

262 NetWorker 18.1 Administration Guide

the destination volume after clone operation completes. This is equivalent to staging the save sets.

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 section, 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 filterIn the Time section, specify the time range in which NetWorker searches for eligible save sets to clone in the media database. Use the spin boxes to specify the start time and the end time. The Time filter list includes the following options to define how NetWorker determines save set eligibility, based on the time criteria:

l Do Not FilterNetWorker inspects the save sets in the media database to create a clone save set list that meets the time filter criteria.

l AcceptThe clone save set list includes save sets that are saved within the time range and meet all the other defined filter criteria.

l RejectThe clone save set list does not include save sets that are saved within the time range and meet all the other defined filter criteria.

b. Save Set filterIn the Save Set section, specify whether to include or exclude ProtectPoint and Snapshot save sets, when NetWorker searches for eligible save sets to clone in the media database. The Save Set filter list includes to the following options define how NetWorker determines save set eligibility, based on the save set filter criteria:

l Do Not FilterNetWorker inspects the save sets in the media database to create a clone save set list that meets the save set filter criteria.

l AcceptThe clone save set list includes eligible ProtectPoint save sets or Snapshot save sets, when you also enable the ProtectPoint checkbox or Snapshot checkbox.

l RejectThe clone save set list does not include eligible ProtectPoint save sets and Snapshot save sets when you also enable the ProtectPoint checkbox or Snapshot checkbox.

Note

For NAS device, only Snapshot save set is applicable.

c. Clients filterIn the Client section, specify a list of clients to include or exclude, when NetWorker searches for eligible save sets to clone in the media database. The Client filter list includes the following options, which define how NetWorker determines save set eligibility, based on the client filter criteria:

l Do Not FilterNetWorker inspects the save sets that are associated with the clients in the media database, to create a clone save set list that meets the client filter criteria.

l AcceptThe clone save set list includes eligible save sets for the selected clients.

Data Protection Policies

Strategies for cloning 263

l RejectThe clone save set list does not include eligible save sets for the selected clients.

d. Levels filterIn the Levels section, specify 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 the following options define how NetWorker determines save set eligibility, based on the level filter criteria:

l Do Not FilterNetWorker inspects the save sets regardless of the level in the media database, to create a clone save set list that meets all the level filter criteria.

l AcceptThe clone save set list includes eligible save sets with the selected backup levels.

l RejectThe clone save set list does not include eligible save sets with the selected backup levels.

Note

For NAS device, only full backup level is applicable.

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. This is applicable if multiple rollover is implemented at an action level.

For Direct-NDMP backups, set the parallelism value to the number of available NDMP drives.

If you set the parallelism attribute to a higher value, there will not be enough drives to support all the queued backup save sets. Large save sets might fail due to the inactivity timeout limit.

When NDMP groups back up simultaneously, divide the number of drives by the number of groups. Use this value for each of the parallelism attributes.

Setting the parallelism value for the group overrides the parallelism value that is defined for the NDMP clients.

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 applies to probe actions, and the backup actions for the Traditional and Snapshot action types.

Data Protection Policies

264 NetWorker 18.1 Administration Guide

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.

25. From the Send Notifications list box, select whether to send notifications for the action:

l To use the notification configuration that is defined in the Policy resource to send the notification, select Set at 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.

26. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, 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 subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

27. From the Soft Limit list, select the amount of time after the action starts to stop the initiation of new activities. The default value of 0 (zero) indicates no amount of time.

Data Protection Policies

Strategies for cloning 265

28. From the Hard Limit list, select the amount of time after the action starts to begin terminating activities. The default value of 0 (zero) indicates no amount of time.

29. (Optional) Configure overrides for the task that is scheduled on a specific day.

To specify the month, use the navigation buttons and the month list box. To specify 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, and 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, and then use the lists. Click Add Rules based override.

n To define an override that occurs on the last day of the calendar month, select Last day of the month. Click Add Rules based override.

Note

n You can edit or add the rules in the Override field.

n 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 CompletionSelect this option when you want to send a notification on completion of the workflows and actions in the policy.

l On FailureSelect this option when you want to send a notification only if one or more of the workflows in the policy fail.

When you configure a notification at the policy level, NetWorker applies the notification to all workflows and actions in the policy that are not configured to send out notifications.

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 workflow notification on completion of all the actions in the workflow, select On Completion.

Data Protection Policies

266 NetWorker 18.1 Administration Guide

l To send a workflow notification only if an action fails to complete, select On Failure.

When you configure a notification at the workflow level, the setting overrides what you defined at the policy level.

In the Action 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.

When you configure a notification at the action level, the setting overrides what you defined at the policy level. If you configured the Workflow resource to send out notifications, you will receive workflow notifications in addition to action notifications.

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 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 46 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

Data Protection Policies

Monitoring policy activity 267

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.

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.

Data Protection Policies

268 NetWorker 18.1 Administration Guide

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_nameis the name of the Policy resource. One folder per policy.

l Workflow_nameis the name of the workflow directory. One folder per action sequence.

l Action_nameis 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 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 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_nameis the name of the policy that contains the workflow.

l workflow_nameis 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

Data Protection Policies

Policy log files 269

where:

l action_nameis the name of the action.

l job_idis 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:

l policy_name is the name of the policy that contains the workflow.

l workflow_name is the name of the workflow.

l action_nameis the name of the action.

l job_idis 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.

Data Protection Policies

270 NetWorker 18.1 Administration Guide

Starting, stopping, and restarting workflows in NMC The workflows in a policy can run automatically, based on a schedule. You can also manually start, stop, and restart specific workflows by using the the NMC NetWorker Administration Monitoring window.

You can restart any failed or canceled workflow. Note, however, that the restart must occur within the restart window that you specified for the workflow. Additionally, for a VMware backup, if you cancel a workflow from NetWorker Administration and then want to restart the backup, ensure that you restart the workflow from the NetWorker Administration window. If a workflow that was started from NetWorker Administration is restarted from the vSphere Web Client, the backup fails.

Procedure

1. In the Monitoring window, select the workflow or actions.

2. Right-click and then select Start, Stop, or Restart.

A confirmation message appears.

Note

You cannot stop, restart, or start individual actions.

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.

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.

Data Protection Policies

Starting, stopping, and restarting workflows in NMC 271

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.

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.

Data Protection Policies

272 NetWorker 18.1 Administration Guide

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 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 30 Workflow path from a snapshot backup action

Workflow path from a probe action You can perform either a traditional backup or a snapshot backup after a probe action.

Figure 31 Workflow path from a probe action

Data Protection Policies

Workflows 273

Workflow path from a server backup action A clone action is the only supported action after a server backup action.

Figure 32 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 33 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 34 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.

Figure 35 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.

Data Protection Policies

274 NetWorker 18.1 Administration Guide

Figure 36 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 37 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 38 Traditional backup workflow

After you create actions for a workflow, in the Administration interface, you can see a map provides a visual representation of the actions on the right side of the Protection window.

The oval icon specifies the group to which the workflow applies. The rounded rectangle icons identify actions. 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 You can adjust the display of the visual representation by right-clicking and selecting one of the following options:

n Zoom InIncrease the size of the visual representation.

n Zoom OutDecrease the size of the visual representation.

n Zoom AreaLimit the display to a single section of the visual representation.

n Fit ContentFit the visual representation to the window area.

n ResetReset the visual representation to the default settings.

n OverviewView a separate dialog box with a high-level view of the visual representation and a legend of the icons.

l You can view and edit the properties for the group, action, or destination pool by right-clicking the icon for the item, and then select Properties.

l You can create a group, action, or destination pool by right-clicking the icon for the item, and then select New.

Data Protection Policies

Workflows 275

Create a workflow in an existing policy A policy can contain 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 allowed characters for the Name field is 64. This name cannot contain spaces or special characters such as + or %.

7. In the Comment box, type a description for the workflow.

The maximum number of allowed 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 specify when to send a notification, select Set at policy level.

l To send notifications with information about each successful and failed workflow and action, after the workflow completes all the actions, select On Completion.

l To send notifications with information about each failed workflow and action, after the workflow completes all the actions, select On Failure.

9. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages or the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient

Data Protection Policies

276 NetWorker 18.1 Administration Guide

l On Windows, type the following command: smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver... where:

n -s subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

10. In the Running section, perform the following steps to specify when and how often the workflow runs:

a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, 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 starts, clear this option.

b. To start the workflow 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 starting at the time that is specified in the Start time attribute, clear this option.

c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.

The default value is 9:00 PM.

d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for this attribute in order for incremental transaction log backup of SQL databases to occur.

The default Interval attribute 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 specify the last start time in a defined interval period, use the spin boxes.

e. To specify 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, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow automatically starts every hour beginning at 7:00 PM. 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.

Data Protection Policies

Workflows 277

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.

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.

Create a workflow in a new policy Procedure

1. In the Administration window, click Protection.

2. In the left pane, expand Policies, and then select the policy that you created.

3. In the right pane, select Create a new workflow.

4. In the Name field, type the name of the workflow.

The maximum number of allowed characters for the Name field is 64. This name cannot contain spaces or special characters such as + or %.

5. In the Comment box, type a description for the workflow.

The maximum number of allowed 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 specify when to send a notification, select Set at policy level.

l To send notifications with information about each successful and failed workflow and action, after the workflow completes all the actions, select On Completion.

l To send notifications with information about each failed workflow and action, after the workflow completes all the actions, select On Failure.

7. In the Send notification attribute, when you select the On Completion option or On failure option, the Command box appears. Use this box to configure how NetWorker sends the notifications. You can use the nsrlog command to send the notifications to a log file or you can send an email notification.

The default notification action is to send the information to the policy_notifications.log file. By default, the policy_notifications.log file is located in the /nsr/logs directory on Linux and in the C:\Program Files\EMC NetWorker\nsr\logs folder on Windows.

Use the default mailer program on Linux to send email messages, or use the smtpmail application on Windows:

l To send notifications to a file, type the following command, where policy_notifications.log is the name of the file:

nsrlog -f policy_notifications.log l On Linux, to send an email notification, type the following command:

mail -s subject recipient l For NetWorker Virtual Edition (NVE), to send an email notification, type the

following command:

/usr/sbin/sendmail -v recipient_email "subject_text"

Data Protection Policies

278 NetWorker 18.1 Administration Guide

l On Windows, type the following command:

smtpmail -s subject -h mailserver recipient1@mailserver recipient2@mailserver...

where:

n -s subjectIncludes 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 mailserverSpecifies the hostname of the mail server to use to relay the SMTP email message.

n recipient1@mailserverIs the email address of the recipient of the notification. Multiple email recipients are separated by a space.

8. In the Running section, perform the following steps to specify when and how often the workflow runs:

a. To ensure that the actions that are contained in the workflow run when the policy or workflow starts, 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 starts, clear this option.

b. To start the workflow 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 starting at the time that is specified in the Start time attribute, clear this option.

c. To specify the time to start the actions in the workflow, in the Start Time attribute, use the spin boxes.

The default value is 9:00 PM.

d. To specify how frequently to run the actions that are defined in the workflow over a 24-hour period, use the Interval attribute spin boxes. If you are performing transaction log backup as part of application-consistent protection, you must specify a value for this attribute in order for incremental transaction log backup of SQL databases to occur.

The default Interval attribute 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 specify the last start time in a defined interval period, use the spin boxes.

e. To specify 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, if the Start Time is 7:00 PM, the Interval is 1 hour, and the Interval End is 11:00 PM., then the workflow automatically starts every hour beginning at 7:00 PM. and the last start time is 11:00 PM.

9. To create the workflow, click OK.

Data Protection Policies

Workflows 279

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.

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 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.

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.

Data Protection Policies

280 NetWorker 18.1 Administration Guide

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.

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.

Data Protection Policies

Protection groups 281

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:

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.

Data Protection Policies

282 NetWorker 18.1 Administration Guide

Table 47 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

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 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.

Data Protection Policies

Actions 283

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, actions that occurs after a disabled action do not start, even if the subsequent options are enabled.

5. From the Action Type list, select the action.

6. If you create the action as part of the workflow configuration, the workflow appears automatically in the Workflow box and the box is dimmed.

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, in the Previous box, select the action that should precede this action.

l If the action should run concurrently with an action, in the Previous box, select the concurrent action, 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 48 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.

Data Protection Policies

284 NetWorker 18.1 Administration Guide

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.

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. Token-based 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

Data Protection Policies

Managing policies from the command prompt 285

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 NetWorker Security Configuration Guide provides more information about privileges

This section provides some examples of how to manage data protection policies from a command prompt.

The UNIX man pages and the 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, Workflow and action 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 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

Data Protection Policies

286 NetWorker 18.1 Administration Guide

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

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 [-M "start_time"] [-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, server-backup, 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 start_time is the time to start the action, in one of the following formats:

n -M "hh:mm"To start the action at a specific time. For example, to create a new action in an existing workflow that starts at 11:15 PM, type -M "23:15"

n -M "+hh:mm"To start the action after period of time has elapsed since the start of the workflow. For example, to create a new action that starts 3 hours after the start of a workflow, type -M "+3:00"

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.

Data Protection Policies

Creating Action resources from a command prompt 287

l To create a new action in an existing workflow that starts at 11:15 PM, type the following command:

nsrpolicy action create backup traditional -p policy_name -w workflow_name -A action_name -M "23:25"

l To create a new action that starts 3 hours after the start of a workflow, type:

nsrpolicy action create backup traditional -p policy_name -w workflow_name -A action_name -M "+3:00"

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

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 stop --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:

Data Protection Policies

288 NetWorker 18.1 Administration Guide

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. 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_nameSpecifies the name of the action resource.

l cmd_line_flagsDefines 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 "\"action name\" -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:

nsrworkflow -p Backup -w fs_backup_clone -A "backup -l 3 -y \"3 years \"" -A "clone -y \"3 years\""

Running an adhoc workflow outside of the backup schedule The nsrworkflow -a flag, which allows you to override a backup schedule and run an adhoc backup.

The following list describes workflow changes in adhoc mode:

l The action start time setting for all actions in a workflow (if set) is ignored.

l The action schedule activity of 'skip' is converted to the default schedule activity for the action. This conversion to the default action allows adhoc execution of workflows on days where the schedule is configured to level 'skip'. You can use the -A option to specify a different schedule activity if the action supports it. The following list describes the default schedule activity for various actions:

n Database-level backup actions: 'incr'

n Server-level backup actions: '1' (cumulative incremental)

n All other actions: 'exec'

Note

There are different backup-level override flags for file-level backups and virtual machine backups:

l For virtual machine backups, the backup-level override flag is -L.

l For file-level backups, the backup-level override flag is -l.

Data Protection Policies

Starting, stopping, and restarting workflows from a command prompt 289

The following example commands use the nsrworkflow -a flag, the -A flag to specify the schedule activity, and the backup-level override flag:

l File-level backup: nsrworkflow -p "FILE Backup" -w "2-Weekly 1800" -c "networkerclient1.emc.com,networkerclient2.emc.com" -A "'backup' -l full" -a

l Virtual machine backup: nsrworkflow -p "VM Backup" -w "2-Weekly VMCluster1" -c "vm:client1,vm:client2" -A "'backup' -L full" -a

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,

Data Protection Policies

290 NetWorker 18.1 Administration Guide

"asbPerformCFI": true, "asbRetentionPeriod": "1 Months" } }, "actionSchedulePeriod": "month", "actionScheduleActivity": [ "full", "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","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": [ "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" } ],

Data Protection Policies

Displaying Data Protection Policy resource configurations 291

"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", "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"

Data Protection Policies

292 NetWorker 18.1 Administration Guide

}, "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" ], "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.

Remote system error - Cannot assign requested address This message appears intermittently when a single workflow has more 2000 save sets and the backup and clone operations occur concurrently. In this scenario the number RPC connections that the configuration requires exceeds the available number of RPC ports. To resolve this issue, split the workflow with a large number of save sets into multiple workflows, up to a maximum of 2000 save sets in each workflow and stagger the workgroup start times by 30 minutes.

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.

Running actions from the command line NetWorker 9.2.x and later provide you with the ability to run actions from a command line for debugging purposes only.

Data Protection Policies

Troubleshooting policies 293

To debug an action, use the action binary, for example, nsrworkflow, nsrpolicy, savegrp, or nsrnassnap_index with the following options:

l --policy_nameSpecifies the name of the policy that contains the action. This option is required.

l --workflow_nameSpecifies the name of the workflow that contains the action. This option is not required when a policy only contains one workflow.

l --action_nameSpecifies the name of the action. This option is not required when a workflow only contains one action.

l -Z action_typeRequired for the savegrp binary. Specifies the action type of the action. Supported values are backup:traditional, backup:snapshot and probe. If you do not specify this option, savegrp defaults to the backup:traditional action type.

l --driven_by_actionSpecifies the source of the input work items for an action, for example a list of backup save set. Sources include one of the following options:

n jobidSpecifies the jobid of the driving action.

n stdinInstructs the action binary to read the items from stdin.

n file:absolute_path_to_fileInstructs the action binary to read the items from a file.

Note

This option is only required when the action is not the first action in a workflow.

Example 7 Debugging an action by using stdin

In the following example, a backup of the save set /baz failed for host foo.com. The name of traditional backup action for the save set is backup. A workflow named traditional1, which is in a policy named Backup contains the action.

To troubleshoot the backup action, perform the following steps:

1. Connect to the NetWorker Server with an administrator account.

2. From a command prompt, start the nsradmin program:

nsradmin 3. From the nsradmin prompt, define the attributes that nsradmin will display for

a resource, for example, the resource name and the save set value, by typing the following command:

show name; save set 4. Enable nsradmin to display the hidden resource ID attribute for the NetWorker

resources:

option resource id 5. Display a list of client resources, by typing the following command:

p type: nsr client 6. From the output, record the resource identifier that appears for the client

resource that contains the save set associated with the action that you want to debug. For example, output similar to the following appears:

Data Protection Policies

294 NetWorker 18.1 Administration Guide

Example 7 Debugging an action by using stdin (continued)

name:foo.com; saveset:/baz; resourceidentifier: 70.0.77.10.0.0.0.0.208.36.124.87.128.222.109.22(1);

name:foo.com; saveset:/foo,/bar; resourceidentifier: 93.0.89.114.0.0.0.0.55.25.124.87.128.222.109.22;(9)

Note

The resource ID does not include the brackets or the number contained within the brackets.

7. Use the savegrp command and the resource ID to start the action:

echo resource_ID|savegrp --policy_name=policy_name -- workflow_name=workflow_name --action_name=action_name -v -- driven_by_action=stdin

For example:

echo 93.0.89.114.0.0.0.0.55.25.124.87.128.222.109.22|savegrp -- policy_name=Backup -- workflow_name=traditional1 --action_name=backup -v -- driven_by_action=stdin

Data Protection Policies

Troubleshooting policies 295

Data Protection Policies

296 NetWorker 18.1 Administration Guide

CHAPTER 5

Backup Options

This chapter contains the following topics:

l Overview of resources that support backups................................................... 298 l Save sets......................................................................................................... 298 l Backup levels....................................................................................................301 l Backup scheduling............................................................................................ 314 l Backup retention..............................................................................................322 l General backup considerations.........................................................................326 l Directives.........................................................................................................332

Backup Options 297

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 49 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 to define save set retention. Save set retention is how long the save set entries are maintained in the media database and client file indexes.

Backups for a client are maintained in the database, and can be browsed for recovery for a month.

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.

Backup Options

298 NetWorker 18.1 Administration Guide

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 For Windows operating systems, use the same pathname case that the Windows file system uses. Although most file systems are case-independent, the NetWorker 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 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.

l 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 50 Data in the ALL save set

Operating system Files

Windows 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

Backup Options

The ALL save set 299

Table 50 Data in the ALL save set (continued)

Operating system Files

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.

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.

Save sets excluded from the ALL save set The following directories, file systems, and files are excluded from the ALL save set:

Table 51 File systems excluded from the ALL save set

l hsfs l proc l fd l cachefs l lofs l mntfs l ctfs l objfs

l sharefs l nfs2 l nfs3 l nfs3perf l profs l nfs4 l nfs l brfs

l dfs l autofs l iso9060 l udf l sysfs l debugfs l subfs l usbdevfs

l binfmt_mi sc

l usbfs l devpts l smbfs l swap l tmp l tmpfs l nucfs

l nucam l fdfs l xx l none

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.

Backup Options

300 NetWorker 18.1 Administration Guide

Table 52 Special ALL save sets

Special ALL save set syntax Backup behavior

all-file_system l 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.

l File systems such as NFS that are normally skipped are still skipped.

l The NetWorker Online Software Compatibility Matrix provides a list of the supported file system for each operating system.

all-mounts 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.

all-local 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.

all-global 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

Backup Options

Backup levels 301

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 53 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.

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 54 Advantages and disadvantages of backup levels

Backup level Advantages Disadvantages

Full l Faster recovery l Slower backups

l High server load

l High load on the client and network

l Uses more volume space

Incremental l Faster than a full backup

l Low server load

l Uses less volume space than a full backup

l Slow recovery

l Data can spread across multiple volumes

Cumulative incremental l Faster than a full backup

l Low server load

l Slow recovery

Backup Options

302 NetWorker 18.1 Administration Guide

Table 54 Advantages and disadvantages of backup levels (continued)

Backup level Advantages Disadvantages

l Uses the least amount of volume space

l Data can spread across multiple volumes

Logs only l Faster than a full or incremental backup

l Low server load

l Slow recovery

l Data can spread across multiple volumes

Synthetic full l Faster than a full backup

l Faster recovery

l Low load on the server, client, and network

l Requires fewer volumes for recovery

l High load on the storage node

l Requires at least two volume drives

l Uses the most volume space

Review the following additional considerations when selecting backup levels:

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 1A full backup is run. l Day 2 An incremental backup saves all files that have changed since the full

backup.

Backup Options

Backup levels and data recovery requirements 303

l Day 3Another incremental backup saves all files that have changed since Day 2.

l Day 4A cumulative incremental backup saves all files that have changed since the full backup on Day 1.

Figure 39 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.

Backup Options

304 NetWorker 18.1 Administration Guide

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.

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 40 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.

Backup Options

Synthetic full backups 305

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.

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.

Backup Options

306 NetWorker 18.1 Administration Guide

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 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.

Backup Options

Synthetic full backups 307

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.

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.

The UNIX man page and the NetWorker Command Reference Guide provides detailed information about the nsrconsolidate command.

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

Backup Options

308 NetWorker 18.1 Administration Guide

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.

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 306.

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

Backup Options

Synthetic full backups 309

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 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 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 55 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 471 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 non- virtual synthetic mode 95773:nsrrecopy: Virtual synthetic succeeded for hostname:/ test1

Backup Options

310 NetWorker 18.1 Administration Guide

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 590 provides more information.

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 56 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 57 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

Backup Options

Virtual synthetic full backups 311

Table 57 Requirements for virtual synthetic full backups (continued)

Requirement Details

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.

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 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.

Client resource configuration 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.

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.

Device resource configuration 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.

Backup Options

312 NetWorker 18.1 Administration Guide

Table 57 Requirements for virtual synthetic full backups (continued)

Requirement Details

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 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:

l Concurrent VSF backups.

l A VSF backup concurrent with a cloning operation.

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 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 309 provides more information on configuring a data protection policy for a scheduled synthetic full backup.

l For manual backups at the command line, use the nsrconsolidate command.

Backup Options

Virtual synthetic full backups 313

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 309 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 58 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 471 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 non- 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.

Backup Options

314 NetWorker 18.1 Administration Guide

Figure 41 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 42 Staggered weekly backup schedule for multiple groups of clients

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.

Backup Options

Considerations for scheduling backups 315

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.

Backup Options

316 NetWorker 18.1 Administration Guide

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 configure schedule overrides.

Schedules and backup levels assigned to an action You specify the schedule and backup level as part of the backup action. The following figure illustrates the default weekly schedule for a traditional backup action, with a full backup on Sunday, and incremental backups on the remaining days of the week.

Figure 43 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 backup level that is performed on that day. The following table provides details about the backup level that each icon represents.

Table 59 Scheduled backup level 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

Backup Options

Methods for scheduling backups 317

Table 59 Scheduled backup level icons (continued)

Icon Label Description

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.

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.

Configuring multiple backup levels for frequently scheduled backups Use the Force Backup Level attribute in the Specify the Action Information window of the Action wizard to override the backup levels of a Traditional backup action that occurs multiple times in a 24 hour period.

For workflows that have more than one scheduled backup within a 24-hour period, use the Force Backup Level attribute to allow more than one backup to occur at two different backup levels in a 24-hour period. When you select a backup level in the Force Backup Level attribute, the first backup is performed at the scheduled backup level. Each subsequent occurrence of the backup action in the next 24 hours occurs at the level defined in the Force Backup Level attribute. For example, if the level defined by the schedule is Full and the Force Backup Level attribute is set to Incr, the first backup started by the action occurs at a level full and subsequent backups, within 24 hours of the start of the full backup are incremental. By default this option is cleared, which means that if the action runs multiple backup operations in a 24 period, all the backups occur at the scheduled backup level.

The following figure provides an example of the Force Backup Level attribute in the Specify the Action Information window, with the Cumulative Incr option selected.

Backup Options

318 NetWorker 18.1 Administration Guide

Figure 44 The Force Backup Level attribute

Defining a schedule for a client NetWorker allows you to override the backup level for a schedule traditional backup action by configuring a schedule for a client.

NetWorker provides you with preconfigured schedules that you can assign to a client. Review the following sections for information about preconfigured schedules, how to modify a schedule, and how to assign a schedule to a client resource.

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 60 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.

Backup Options

Methods for scheduling backups 319

Table 60 Preconfigured NetWorker schedules (continued)

Schedule name NetWorker backup operation

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.

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.

Managing the schedule resource

Review this section for information about how to create, edit, copy, and delete schedule resources.

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.

Backup Options

320 NetWorker 18.1 Administration Guide

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.

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 UNIX man page and the NetWorker Command Reference Guide provides detailed 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.

Backup Options

Methods for scheduling backups 321

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.

4. Click Yes.

Configuring a client to override the schedule assigned to an action

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. Enable Client determines level.

9. Click OK.

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 479 describes how to remove save sets from backup storage after the retention period expires.

Backup Options

322 NetWorker 18.1 Administration Guide

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 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 retains the value that is defined in the Retention attribute of a Pool resource as a read-only value.

Order of precedence for Retention resource attributes It is recommended 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:

Backup Options

Methods for setting retention 323

l Client Can OverrideThe 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 OverrideThe 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 RulesEnabled 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 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.

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:

Backup Options

324 NetWorker 18.1 Administration Guide

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 UNIX man page and the NetWorker Command Reference Guide provides detailed information about the nsrmm, nsr_getdate, and mminfo commands.

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:

nsrmm -S 3315861249 -e "2 years"

Backup Options

Editing retention for a save set 325

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 -o VSS:*=off \\.\e: save -s NetWorker_server_name -o VSS:*=off \\.\PhysicalDrive0

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.

Backup Options

326 NetWorker 18.1 Administration Guide

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 backup 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 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 results in multiple save streams attempting to access the disk at the same time.

The 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. You can use PSS to perform the scheduled file level backup of file systems, and block based backups.

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. The default value

Backup Options

Access control lists 327

for 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

It is recommended that you set the client parallelism value to be a multiple of the PSS:streams_per_ss parameter default value 4 or its largest defined value when configured. For example, a multiple of 4 is 8, 12, or 16.

If the client parallelism is less than the PSS:streams_per_ss default 4 or the lowest configured value, the backup fails displaying an error message.

The PSS:streams_per_ss values range from 1 to 8. If you specify an invalid value, the backup proceeds with the default value 4, and a warning message displays stating that that the entire PSS:streams_per_ss parameter is ignored.

The 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:\.

Backup Options

328 NetWorker 18.1 Administration Guide

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 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 Customer Service. The NetWorker Performance Optimization Planning Guide provides complete details on PSS requirements and performance benefits.

Backup Options

Client parallelism and parallel save streams 329

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 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.

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 Customer Service.

Table 61 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.

Backup Options

330 NetWorker 18.1 Administration Guide

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 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

Backup Options

Open files 331

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:

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.

The 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.2.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 directivesStored 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 directiveOn 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.

Backup Options

332 NetWorker 18.1 Administration Guide

l Local directive filesUser-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 user-defined 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 directive statement specifies the following items:

l The directory for a directive statement.

l The action to perform, specified using either of the following:

n An ASM specification with a pattern list of child file or directory names, which could include wildcards.

n A save environment keyword specifies the action to perform.

A directive statement is written in the following format:

<< "directory_specification" >> [+] ASM: pattern save_environment_keyword # comment

where:

l The directive statement does not contain blank lines.

l directory_specification is the absolute path to the highest-level directory for which the ASM in the directive applies.

l [+] is optional. The presence of the plus (+) sign indicates that the directive recursively 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 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 statements support the use of standard shell command interpreter file matching patterns. You cannot specify lower-level subdirectories in the pattern. That is, the pattern must not contain the Unix "/" or Windows "\" directory separator.

Backup Options

Format of directive statements 333

Note

File names are case-insensitive for directives that are applied to Windows clients.

l save_environment_keyword is a 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.

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.

The UNIX man page and the NetWorker Command Reference Guide provides detailed information about directives in the nsr and nsr_directive commands.

Defining directory specifications A directory specification is the absolute path to the highest-level directory for which the ASM in the directive applies.

Consider the following information before you define a directory specification.

Defining directory specifications using wildcards You can use wildcards in the directory specification to avoid maintaining multiple directives for specific directory paths in both the NetWorker server and the NetWorker client directive files.

To use wildcards in a directory specification, you must type an asterisk before the directory path. For example:

l UNIX: << */directory_specification/ >> l Windows: << "*\directory_specification\" >> This asterisk does not do any matching and only enables the use of any following wildcards in the directory specification.

Consider the following examples for using wildcards:

l The following UNIX directive skips backing up the tmp folder data for each user whose name starts with letters A, B, C, or D: << */*/users/[A-D]*/tmp/ >> +skip: *

l The following Windows directive compresses the tmp folder data for each user whose name starts with letters A, B, C, or D: << "*C:\*\users\[A-D]*\tmp\" >> +compressasm: *

Note

l Do not use symbolic links with wildcard directives. You must fully specify the full directory path name that will contain the wildcards.

l Do not use wildcards in Windows VSS source volume directory mount names.

Defining multiple directory specifications

l Directives that follow a directory specification apply the ASM action to that directory until the next directory specification.

Backup Options

334 NetWorker 18.1 Administration Guide

l Directory specifications that do not contain wildcards take precedence over directory specifications that contain wildcards. For example, when a directive encounters a directory that matches a wildcard directory specification and a non- wildcard directory specification, the directive will only apply the action defined in the ASM of the non-wildcard directory specification of the directory.

Defining mount points in the directory specification Directory mount names of Windows VSS source volumes cannot contain wildcards. For example, you cannot create a directory specification in the format << "*?:\data\* \" >> . You must specify each drive letter, for example << "C:\data\*\" >>, and create a separate directory specification for it.

Defining a directory specification for a Windows client system

l File and directory names are case-insensitive.

l If there is a colon (:) in the pathname, enclose the entire path in quotation marks.

Using wildcards in directive statements NetWorker supports wildcards in directive statements.

In a directive statement, you can use wildcard characters in both the directory and path list specifications.

The following table describes the supported wildcard characters and their descriptions.

Table 62 Supported wildcards in directives

Wildcard Name Description

* Asterisk Matches any sequence of characters.

? Question mark Matches any single character.

[ and ] Square brackets Forms an expression. Represents any of the characters enclosed within the square brackets. For example, the following directory specification includes all user folders beginning with A or D: << */*/users/[AD]*/tmp/ >> You can use exclamation marks and hyphens within expressions.

! Exclamation Must be used directly after the opening square bracket in an expression, for example, [!...]. Matches any single character except for the characters typed after the !. For example, to match any single character except a, b, and c, type: [!abc]

- Hyphen When a hyphen is used between two characters within square brackets, it indicates a range inclusive of those two characters. For example, the following directory specification includes all user folders beginning with A, B, C, or D: << */*/users/[A-D]*/tmp/ >>

Backup Options

Format of directive statements 335

Note

Wildcards directives are applied only by the save process in the scheduled backup workflow. When you skip unwanted mount points using directory specification wildcard directives with the save set keyword All, save processes still run for the unwanted mount points. However, the save processes only log messages that the contents of the mount points were skipped. For example: << */ TestFileSystem[5-9]?/ >> +skip: *.

Directive specification with ASMs and save environment keywords A directive specification specifies the action to perform in a directive statement.

Save environment keywords Save environment keywords control how the current ASM and subsequent ASMs applied to the directory and subdirectories are applied in the directive statement.

NetWorker supports the following save_environment_keyword values:

l forgetInstructs 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.

l ignoreInstructs the NetWorker Server to ignore all directives that are applied to the subdirectories below the current directory.

l allowUsed in subdirectories that currently have the ignore keyword applied to them, and overrides the ignore.

The UNIX man page and the NetWorker Command Reference Guide provides detailed information about directives in the nsr and nsr_directive commands.

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 example directive statement skips 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

Backup Options

336 NetWorker 18.1 Administration Guide

<< "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

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:

Backup Options

Global directives 337

Table 63 Preconfigured directives (continued)

Directive resource Description

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 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.

UNIX standard Contains a set of directives that are used to back up standard UNIX clients. Applies these ASMs:

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

Backup Options

338 NetWorker 18.1 Administration Guide

Table 63 Preconfigured directives (continued)

Directive resource Description

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.

UNIX with compression 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.

Backup Options

Global directives 339

2. In the expanded left pane, select Directives.

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 provides more information 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:

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 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.

Backup Options

340 NetWorker 18.1 Administration Guide

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.

Backup Options

NetWorker User local directives 341

NetWorker User program local directives are also enforced during scheduled backups and archive operations.

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:

Backup Options

342 NetWorker 18.1 Administration Guide

<<"C:\TEMP">> skip

NOTICE

Do not leave blank lines in the directive statement.

Format of directive statements provides more information 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.

Backup Options

Creating local directives 343

Backup Options

344 NetWorker 18.1 Administration Guide

CHAPTER 6

Backing Up Data

This chapter contains the following topics:

l Configuring a Client resource for backups on Windows hosts ......................... 346 l Configuring a Client resource for backups on UNIX hosts ............................... 388 l Configuring a Client resource for backups on Mac OS X hosts ....................... 396 l Sending client data to AFTD or Data Domain devices only................................ 401 l Non-ASCII files and directories........................................................................ 402 l Configuring checkpoint restart backups...........................................................402 l Probe-based backups.......................................................................................407 l Encryption....................................................................................................... 408 l Compression..................................................................................................... 411 l Configuring Client Direct backups.................................................................... 412 l Backup command customization.......................................................................414 l Client resources................................................................................................421 l Manual backups............................................................................................... 426 l Verifying backup data.......................................................................................428

Backing Up Data 345

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 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.

Backing Up Data

346 NetWorker 18.1 Administration Guide

Enabling NetWorker logging operations performed by backup operator

By default, members of the Windows Backup Operators group do not have write permission to the \logs directory.

NetWorker log operations are performed by members of the Windows Backup Operators group.

Enable NetWorker logging for Backup Operators by modifying the security settings on the \logs directory. For example:

Procedure

1. In Windows Explorer, navigate to the \logs directory.

2. Right-click the \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 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 logsUsed 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.

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

Backing Up Data

Windows backup considerations 347

Table 64 Backup considerations for Windows features (continued)

Windows Feature Backup considerations

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.

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 will not encrypt or compress a file already encrypted by Windows. Do not use AES encryption when you backup EFS encrypted files.

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:

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.

Internet Information Server (IIS) A web server that enables the publication of information on the Internet or a corporate intranet by using HTTP.

NetWorker 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%

Backing Up Data

348 NetWorker 18.1 Administration Guide

Table 64 Backup considerations for Windows features (continued)

Windows Feature Backup considerations

\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 program to create huge files without actually committing disk space for every byte.

NetWorker provides complete backup and recovery support for sparse files.

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, NetWorker 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

the case of a file, you can set the system environment variable

Backing Up Data

Windows backup considerations 349

Table 64 Backup considerations for Windows features (continued)

Windows Feature Backup considerations

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:

Backing Up Data

350 NetWorker 18.1 Administration Guide

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.

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 all-inclusive save set types, ALL-DFSR is not related to any particular file system. ALL-DFSR 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.

Backing Up Data

Windows backup considerations 351

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.

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 servers 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. However, due to recovery performance issues observed with optimized backup for Windows deduplication volumes, it is recommended that you use non-optimized backup, which is enabled by default.

When the backup is set to non-optimized, NetWorker will not deduplicate the backup. Instead, 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 might back up the chunk stores unnecessarily. To back up the deduplicated volume, it is recommended to use 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)

Backing Up Data

352 NetWorker 18.1 Administration Guide

optimized backup. However, it is not recommended that you use this setting because recovery performance issues might result in an unusable backup. Note also that even when optimized deduplication backup is enabled, NetWorker will not perform an optimized backup when the backup path is a subdirectory of the volume, or the non- optimized deduplication save option is specified in the Save operations field of the Client resource.

NetWorker supports the data deduplication feature on Windows Server 2012, Windows Server 2012 R2, Windows Storage Server 2012, and Windows Storage Server 2012 R2. 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.

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.

The UNIX man page and the NetWorker Command Reference Guide provides detailed information about the mminfo command.

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:

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.

Backing Up Data

Windows backup considerations 353

l When you perform a manual backup of the client that does not make up the entire volume.

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, perform the following steps:

1. From the NetWorker Administration window, select the Protection menu.

2. In the left navigation pane, select Clients, right-click the client, and then select Modify Client Properties.

3. On the client Properties text box, select the Apps & Modules tab.

4. 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.

Backing Up Data

354 NetWorker 18.1 Administration Guide

l No support for selective file restores due to insufficient information about the save sets 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 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

Backing Up Data

Windows backup considerations 355

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.

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.

Backing Up Data

356 NetWorker 18.1 Administration Guide

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 might be superseded by information in the NetWorker Module for Microsoft documentation. The 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

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 NetWorker Snapshot Management 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:

Backing Up Data

Windows file system backups 357

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 359 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.

Figure 45 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.

Backing Up Data

358 NetWorker 18.1 Administration Guide

Figure 45 VSS backup process (continued)

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 (in-use) 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 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 360 provides more information about specifying VSS commands for a NetWorker client. VSS commands on page 362 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 359 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

Backing Up Data

Windows file system backups 359

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 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 NetWorker Online Software Compatibility Matrix 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.

Backing Up Data

360 NetWorker 18.1 Administration Guide

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 (;).

The 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 clients VSS setting on the server. Likewise, if you change a clients 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 for all NetWorker clients, perform the following steps:

Procedure

1. Log in as root or as Windows Administrator on the NetWorker server.

2. Create an input file for the nsradmin command. The input file eliminates interactive prompting as each client gets updated.

3. Run the nsradmin command and specify the input file.

4. Create an input text file. For example, create a file that is named disable-vss- nt.txt and type the following into the file:

5. Type the following at the command prompt:

nsradmin -i \disable-vss.txt nsradmin -i \disable- vss-nt.txt where is the directory location of the input file.

Example 8 Example: Disable VSS for all NetWorker clientsExample: Disable VSS for all Windows NetWorker clients

Backing Up Data

Windows file system backups 361

Example 8 Example: Disable VSS for all NetWorker clientsExample: Disable VSS for all Windows NetWorker clients (continued)

1. Create a text file that is named disable-vss.txt , and then type the following into the file:

show name; client OS type; Save operations print type: NSR client update Save operations: "VSS\:*=off" print

2. Type the following command at the command prompt:

nsradmin -i \disable-vss.txt

where is the directory location of the input file.

1. Create a text file that is named disable-vss-nt.txt , and then 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 the following command at the command prompt:

nsradmin -i \disable-vss-nt.txt

where is the directory location of the input file.

VSS commands

This section lists the commands and syntax that are used to control VSS.

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

Backing Up Data

362 NetWorker 18.1 Administration Guide

Table 65 VSS Save operation attribute values (continued)

Task Save operations attribute Behavior

Backups fail.

To use a hardware provider or a specific software provider for a NetWorker client backup.

VSS:VSS_ALLOW_DEFAULT _PROVIDER=yes

A backup provider is selected based on the following default Microsoft criteria:

If a hardware provider that supports the particular volume on the NetWorker client is available, it is selected.

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 363 provides more information about Windows Bare Metal recovery backups.

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

Backing Up Data

Windows Bare Metal Recovery 363

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:

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.

l Any parent volume with a mounted critical volume.

Backing Up Data

364 NetWorker 18.1 Administration Guide

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) Bare Metal Recovery (BMR) is data recovery and restoration where the backed up data is available in a form that allows you to restore a system from bare metal, that is, without any requirements as to previously installed software or operating system. Typically, the backed up data includes the necessary operating system, applications, and data components to rebuild or restore the backed up system to an entirely separate piece of hardware. The hardware receiving the restore should have a similar configuration as that of the hardware that was the source of the backup. The basic BMR is the process of bringing up a server after a disaster and ensuring that the system recovers with the operating system, the applications, and the data as they were at the time of the failure.

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.

Backing Up Data

Windows Bare Metal Recovery 365

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.

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 Online Support website. 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 NetWorker Online Software Compatibility Matrix 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

Backing Up Data

366 NetWorker 18.1 Administration Guide

Table 66 DISASTER_RECOVERY:\ components in an incremental backup (continued)

Save set Backup level

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 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 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. It is recommended 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.

Backing Up Data

Windows Bare Metal Recovery 367

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.

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

Backing Up Data

368 NetWorker 18.1 Administration Guide

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:

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 topic Online recovery of Active Directory, DFSR, or Cluster service 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 only confirms 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. It is recommended that you restore the WINDOWS ROLES AND FEATURES save set from a NetWorker 8.1 or later backup.

Backing Up Data

Windows Bare Metal Recovery 369

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:\.

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 NetWorker Online Software Compatibility Matrix provides more information about support operating systems.

The topic Performing a Windows BMR recovery to a physical computer 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:

\\ \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 system-reserved 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,

Backing Up Data

370 NetWorker 18.1 Administration Guide

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.

Applications such as SQL Server and Hyper-V in a Windows Continuous Availability scenario using CSV are not supported.

The 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

It is recommended 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 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 that are 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 in the [root]\EMC NetWorker\nsr\tmp directory. 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.

Backing Up Data

Windows Bare Metal Recovery 371

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 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.

Example 9 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 10 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.

Backing Up Data

372 NetWorker 18.1 Administration Guide

Example 10 Synthetic full backups with file system save sets (continued)

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.

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.

Backing Up Data

Windows Bare Metal Recovery 373

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 must be compatible with the disk or RAID controllers in the target system. The recovery process restores the 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

Specify these save sets in the client resource Save Set attribute

Considerations

A host or file server that is not a Microsoft Application server

l Specify the save set All in the NetWorker Client resource.

l By default, the save set All includes the DISASTER

l WINDOWS ROLES AND FEATURES must be backed up.

l WINDOWS ROLES AND FEATURES save sets are

recovered in a Windows BMR

Backing Up Data

374 NetWorker 18.1 Administration Guide

Table 67 Save set configuration for a specific host (continued)

To back up this host

Specify these save sets in the client resource Save Set attribute

Considerations

RECOVERY:\ save set and all of

the local physical drives.

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.

A host that is a Microsoft Application server. For example, a Microsoft Exchange Server, Microsoft SQL Server, Hyper-V, or Microsoft SharePoint Server

l Specify the ALL save set in the

Save set attribute in the NetWorker Client resource.

l Use NMM to back up the application databases. The NMM provides details.

l Use the Windows BMR Wizard to recover the data contained in the DISASTER RECOVERY:\ save set.

l Use NMM to recover the application databases.

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.

Backing Up Data

Windows Bare Metal Recovery 375

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,