Symantec NetBackup Administrator's Guide, Volume I

Windows

Release 7.5

21220058

Symantec NetBackup Administrator's Guide, Volume I

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: 7.5 PN: 21220058

Legal Notice
Copyright 2012 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com Printed in the United States of America. 10 9 8 7 6 5 4 3 2 1

Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs support offerings include the following:

A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services

For information about Symantecs support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:

Product release level

Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description:

Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes

Licensing and registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/

Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues:

Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals

Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America [email protected] [email protected] [email protected]

Contents

Technical Support ............................................................................................... 4

Section 1
Chapter 1

About NetBackup

....................................................... 29

Introducing NetBackup interfaces ................................... 31

About NetBackup ......................................................................... NetBackup documentation ............................................................. About NetBackup administration interfaces ...................................... About running the Windows-based NetBackup Administration Console .......................................................................... Starting the Java-based Windows Display Console ........................ Administering remote servers and servers of different versions ......................................................................... About using the NetBackup Administration Console ........................... Standard and user toolbars ...................................................... About customizing the NetBackup Administration Console ............ NetBackup configuration wizards ................................................... Activity Monitor utility ................................................................. NetBackup Management utilities .................................................... Media and Device Management utilities ........................................... Running the Troubleshooter .......................................................... Access Management utility ............................................................ 31 33 33 35 35 36 38 39 40 40 41 42 44 44 45

Chapter 2

Administering NetBackup licenses .................................. 47

About administering NetBackup licenses .......................................... Accessing license keys for a NetBackup server ............................. Adding new license keys .......................................................... Printing license key lists .......................................................... Deleting license keys .............................................................. Viewing license key properties ................................................. Exporting license keys ............................................................ 47 48 49 50 50 51 51

Contents

Section 2
Chapter 3

Configuring hosts ........................................................ 53

Configuring Host Properties ............................................. 55
About the NetBackup Host Properties .............................................. 57 Viewing host properties .......................................................... 59 Changing the host properties on multiple hosts at the same time ............................................................................... 60 Property states for multiple hosts ............................................. 61 Exporting host properties ........................................................ 62 Standard host property dialog box options .................................. 63 Access Control properties .............................................................. 63 Authentication Domain tab ...................................................... 64 Authorization Service tab ........................................................ 66 Network Attributes tab ............................................................ 67 Active Directory host properties ..................................................... 69 Backup Exec Tape Reader properties ............................................... 71 Bandwidth properties ................................................................... 73 Bandwidth limit usage considerations and restrictions .................. 74 Add Bandwidth Settings dialog box for Bandwidth properties ....................................................................... 75 Busy File Settings properties .......................................................... 75 Activating the Busy File Settings in host properties ...................... 76 Clean-up properties ...................................................................... 77 Client Name properties ................................................................. 80 Client Attributes properties ........................................................... 81 Add Client dialog box .............................................................. 83 General tab of the Client Attributes properties ............................ 83 Connect Options tab of the Client Attributes properties ................. 87 Windows Open File Backup tab of the Client Attributes properties ....................................................................... 89 Back-level and upgraded clients that use Windows Open File Backup ........................................................................... 93 Client Settings properties for NetWare clients ................................... 94 Client Settings (UNIX) properties .................................................... 95 VxFS file change log for incremental backups property ................. 97 Client Settings properties for Windows clients .................................. 99 How to determine if change journal support is useful in your NetBackup environment .................................................. 103 Guidelines for enabling NetBackup change journal support .......... 104 Cloud Storage properties ............................................................. 104 Credential Access properties ........................................................ 108 Data Classification properties ....................................................... 109

Contents

Creating a Data Classification ................................................. Default Job Priorities properties .................................................... Understanding the Job Priority setting ..................................... Distributed application restore mapping properties ......................... Encryption properties ................................................................. Enterprise Vault properties .......................................................... Enterprise Vault Hosts properties .................................................. Exchange properties ................................................................... Exclude Lists properties ............................................................... About the Add to exclude list and Add to exceptions list dialog boxes ........................................................................... Syntax rules for exclude lists .................................................. Traversing excluded directories .............................................. Fibre Transport properties ........................................................... Firewall properties ..................................................................... Enabling logging for vnetd ..................................................... General Server properties ............................................................ Forcing restores to use a specific server .................................... Global Attributes properties ......................................................... About constraints on the number of concurrent jobs ................... Setting up email notifications about backups ............................. Configuring the nbmail.cmd script .......................................... Sending email notifications to the administrator about unsuccessful backups ...................................................... Sending messages to the global administrator about unsuccessful backups ........................................................................ Sending messages to the administrator about successful and unsuccessful backups ...................................................... Installing and testing the email utility ...................................... Logging properties ...................................................................... Login Banner Configuration properties ........................................... Removing login banner screen and text .................................... Enabling the Auto log off timeout option .................................. Lotus Notes properties ................................................................ Media properties ........................................................................ Results when media overwrites are not permitted ...................... Recommended use for Enable SCSI reserve property ................... NDMP Global Credentials properties .............................................. NetWare Client properties ............................................................ Network properties ..................................................................... Network Settings Properties ......................................................... Reverse Host Name Lookup property ....................................... IP Address Family Support property ........................................

110 111 112 114 115 118 119 120 122 125 127 129 129 131 134 135 137 138 141 142 143 145 145 146 147 148 154 157 157 158 161 166 167 168 169 170 171 172 174

10

Contents

Port Ranges properties ................................................................ Registered ports and dynamically-allocated ports ....................... Preferred Network properties ....................................................... Add or Change Preferred Network Settings dialog box ................. How NetBackup uses the directives to determine which network to use ........................................................................... Configurations to use IPv6 networks ........................................ Configurations to use IPv4 networks ........................................ Order of directive processing in the Preferred Network properties ..................................................................... Order of directives can affect processing .................................. bptestnetconn utility to display Preferred Network information ................................................................... Configuration to prohibit using a specified address ..................... Configuration that uses the same specification for both the network and the interfaceless constrictive ........................ Configuration that uses the same specification for both the network and the interfacemore constrictive ...................... Configuration that limits the addresses, but allows any interfaces ...................................................................... Resilient Network properties ........................................................ Resilient connection resource usage ........................................ Specifying resilient connections .............................................. Resource Limit properties ............................................................ Restore Failover properties .......................................................... Assigning an alternate media server as a failover restore server ........................................................................... Retention Periods properties ........................................................ Changing a retention period ................................................... Determining retention periods for volumes ............................... Retention Periods with end dates beyond 2038, excluding Infinity ......................................................................... Servers properties ...................................................................... Adding a server to a servers list .............................................. Removing a server from a server list ........................................ Switching to another master server in the Servers properties dialog box ..................................................................... About sharing one Enterprise Media Manager (EMM) database across multiple master servers .......................................... SharedDisk properties ................................................................. SharePoint properties ................................................................. Consistency check options for SharePoint Server ....................... Symantec Products properties ......................................................

175 176 176 178 180 183 184 185 186 186 188 188 189 190 190 193 193 194 196 198 199 200 201 202 202 205 206 206 207 208 208 210 210

Contents

11

Throttle Bandwidth properties ...................................................... Add Bandwidth Settings dialog box for Throttle Bandwidth properties ..................................................................... Timeouts properties .................................................................... Universal Settings properties ....................................................... Logging the status of a redirected restore ................................. UNIX Client properties ................................................................ UNIX Server properties ............................................................... VMware Access Hosts properties ................................................... VSP (Volume Snapshot Provider) properties .................................... Windows Client properties ........................................................... Configuration options not found in the Host Properties ..................... AUTO_ADD_ALL_ALIASES_FOR_CLIENT ................................. LIST_FS_IMAGE_HEADERS ...................................................

210 211 212 214 216 217 218 218 219 220 220 221 221

Chapter 4

Configuring server groups ............................................... 223

About server groups .................................................................... Configuring a server group ........................................................... Server group properties ......................................................... Deleting a server group ............................................................... 223 224 226 226

Chapter 5 Chapter 6

Configuring host credentials ........................................... 227

About configuring credentials ....................................................... 227

Managing media servers .................................................. 229

Activating or deactivating a media server ....................................... Adding a media server ................................................................. About decommissioning a media server .......................................... About decommissioning limitations ......................................... Before you decommission a media server .................................. Post decommission recommendations ...................................... Decommission actions ........................................................... Previewing references to a media server ......................................... Decommissioning a media server .................................................. Registering a media server ........................................................... Deleting all devices from a media server ......................................... Removing a device host from the EMM database .............................. 229 230 231 232 233 233 234 237 238 240 240 242

12

Contents

Section 3
Chapter 7

Configuring storage .................................................. 243

Configuring robots and tape drives ............................... 245
About NetBackup robot types ....................................................... Device configuration prerequisites ................................................ About the device mapping files ..................................................... Downloading the device mapping files ............................................ About configuring robots and tape drives ........................................ About device discovery ................................................................ About device serialization ...................................................... About adding devices without discovery ................................... About robot control .................................................................... Library sharing example ........................................................ Configuring robots and tape drives ................................................ Configuring robots and tape drives by using the wizard ............... Adding a robot ..................................................................... Robot configuration options ................................................... Adding a tape drive ............................................................... Adding a shared tape drive ..................................................... Tape drive configuration options ............................................. About drive name rules ......................................................... Configuring drive name rules ................................................. Adding a tape drive path ........................................................ Correlating tape drives and SCSI addresses on Windows hosts ............................................................................ Updating the device configuration by using the wizard ...................... Managing robots ........................................................................ Changing robot properties ..................................................... Configuring a robot to operate in manual mode .......................... Deleting a robot ................................................................... Moving a robot and its media to a new media server .................... Managing tape drives .................................................................. Changing a drive comment ..................................................... About downed drives ............................................................. Changing a drive operating mode ............................................ Changing a tape drive path ..................................................... Changing a drive path operating mode ..................................... Changing tape drive properties ............................................... Changing a tape drive to a shared drive .................................... Cleaning a tape drive from the Device Monitor ........................... Deleting a drive .................................................................... Resetting a drive .................................................................. 246 247 247 248 248 249 250 250 251 252 252 253 253 254 258 260 260 263 264 266 268 269 269 270 270 270 271 272 273 273 274 274 274 275 276 276 277 277

Contents

13

Resetting the mount time ....................................................... Setting drive cleaning frequency ............................................. Viewing drive details ............................................................. Performing device diagnostics ...................................................... About device diagnostic tests .................................................. Running a robot diagnostic test ............................................... Running a tape drive diagnostic test ........................................ Managing a diagnostic test step that requires operator intervention .................................................................. Obtaining detailed information for a diagnostic test step ............. Verifying the device configuration ................................................. About automatic path correction ................................................... Enabling automatic path correction ............................................... Replacing a device ...................................................................... Updating device firmware ............................................................ About the NetBackup Device Manager ............................................ Stopping and restarting the Device Manager ...................................

278 278 279 280 280 280 282 283 283 283 284 284 285 286 287 287

Chapter 8

Configuring tape media

................................................... 289 289 290 291 292 293 295 296 296 297 297 298 301 302 302 302 303 303 306 306 307 307 309 311

About tape volumes .................................................................... NetBackup media types ............................................................... Alternate NetBackup media types ............................................ About WORM media ................................................................... How to use WORM media in NetBackup .................................... About adding volumes ................................................................. About adding robotic volumes ................................................. About adding stand-alone volumes .......................................... Adding volumes by using the wizard .............................................. Adding volumes by using the Actions menu ..................................... Add volume properties .......................................................... Managing volumes ...................................................................... Changing the group of a volume .............................................. About rules for moving volumes between groups ........................ Changing the owner of a volume ............................................. Changing the pool of a volume ................................................ Changing volume properties ................................................... About assigning volumes ....................................................... About deassigning volumes .................................................... Deleting a volume ................................................................. Erasing a volume .................................................................. About exchanging a volume .................................................... About frozen media ..............................................................

14

Contents

Freezing or unfreezing a volume ............................................. About injecting and ejecting volumes ....................................... Injecting volumes into robots ................................................. Ejecting volumes .................................................................. About rescanning and updating bar codes ................................. Rescanning and updating bar codes ......................................... About labeling NetBackup volumes .......................................... Labeling a volume ................................................................. About moving volumes .......................................................... Moving volumes by using the robot inventory update option .......................................................................... Moving volumes by using the Actions menu .............................. About recycling a volume ....................................................... Suspending or unsuspending volumes ...................................... About volume pools .................................................................... About scratch volume pools .................................................... Adding a volume pool .................................................................. Volume pool properties ......................................................... Managing volume pools ............................................................... Changing the properties of a volume pool ................................. Deleting a volume pool .......................................................... About volume groups .................................................................. About media sharing ................................................................... Configuring unrestricted media sharing ......................................... Configuring media sharing with a server group ................................

311 312 312 312 315 316 317 317 318 319 320 322 324 324 325 326 326 327 327 328 328 329 330 330

Chapter 9

Inventorying robots ........................................................... 333

About robot inventory ................................................................. When to inventory a robot ........................................................... About showing a robot's contents .................................................. About inventory results for API robots ..................................... Showing the media in a robot ........................................................ About comparing a robot's contents with the volume configuration ....................................................................... Comparing media in a robot with the volume configuration ................ About updating the volume configuration ....................................... Volume update prerequisites .................................................. About previewing volume configuration changes ....................... Updating the volume configuration with a robot's contents ................ Robot inventory options .............................................................. Configuring media settings .......................................................... Media settings - existing media ............................................... 334 335 337 338 340 341 342 343 344 345 345 348 349 350

Contents

15

Media settings - new media .................................................... About bar codes ......................................................................... About bar code advantages ..................................................... About bar code best practices ................................................. About bar code rules ............................................................. About media ID generation rules ............................................. Configuring bar code rules ........................................................... Bar code rules settings .......................................................... Configuring media ID generation rules ........................................... Media ID generation options ................................................... Configuring media type mappings ................................................. About adding media type mapping entries ................................ Default and allowable media types ........................................... About the vmphyinv physical inventory utility ................................ How vmphyinv performs a physical inventory ........................... Example volume configuration updates .......................................... Volume Configuration Example 1: Removing a volume from a robot ............................................................................ Volume Configuration Example 2: Adding existing stand-alone volumes to a robot .......................................................... Volume Configuration Example 3: Moving existing volumes within a robot ................................................................ Volume Configuration Example 4: Adding new volumes to a robot ............................................................................ Volume Configuration Example 5: Adding cleaning tapes to a robot ............................................................................ Volume Configuration Example 6: Moving existing volumes between robots .............................................................. Volume Configuration Example 7: Adding existing volumes when bar codes are not used .....................................................

352 356 357 357 358 360 361 362 363 364 366 367 368 373 375 381 382 383 385 386 388 389 390

Chapter 10

Configuring disk storage .................................................. 393

Configuring BasicDisk storage ...................................................... 393 About configuring disk pool storage ............................................... 393 About SharedDisk support in NetBackup 7.0 and later ....................... 394

Chapter 11

Configuring storage units ................................................ 397

About the Storage utility .............................................................. Using the Storage utility ........................................................ Creating a storage unit ................................................................ Creating a storage unit by copying a storage unit ....................... Changing storage unit settings ................................................ 397 398 399 401 402

16

Contents

Deleting storage units ........................................................... Media Manager storage unit considerations .............................. Disk storage unit considerations ............................................. NDMP storage unit considerations ........................................... About storage unit settings .......................................................... Absolute pathname to directory or absolute pathname to volume setting for storage units ................................................... Density storage unit setting ................................................... Disk pool storage unit setting ................................................. Disk type storage unit setting ................................................. Enable block sharing storage unit setting .................................. Enable multiplexing storage unit setting ................................... High water mark storage unit setting ....................................... Low water mark storage unit setting ........................................ Maximum concurrent write drives storage unit setting ................ Maximum concurrent jobs storage unit setting .......................... Maximum streams per drive storage unit setting ........................ Media server storage unit setting ............................................ NDMP host storage unit setting .............................................. On demand only storage unit setting ........................................ Only use the following media servers storage unit setting ............ Properties option in the Change Storage Units dialog box ............ Reduce fragment size storage unit setting ................................. Robot number storage unit setting ........................................... Robot type storage unit setting ............................................... Staging schedule option in Change Storage Units dialog .............. Storage device setting for storage units .................................... Storage unit name setting ...................................................... Storage unit type setting ........................................................ Enable temporary staging area storage unit setting .................... Transfer throttle storage unit setting ....................................... Use any available media server storage unit setting ....................

402 403 405 411 413 413 414 414 414 415 415 415 416 416 417 419 419 422 422 423 424 425 426 426 427 427 427 427 428 428 428

Chapter 12

Staging backups

................................................................ 431 431 432 433 434 435 436 438

About staging backups ................................................................ About the two staging methods ..................................................... About basic disk staging .............................................................. Creating a basic disk staging storage unit ........................................ Creating a schedule for a basic disk staging storage unit .............. Configuring multiple copies in a relocation schedule ......................... Disk staging storage unit size and capacity ......................................

Contents

17

Finding potential free space on a BasicDisk disk staging storage unit .................................................................................... Disk Staging Schedule dialog box .................................................. Basic disk staging limitations ....................................................... Initiating a relocation schedule manually .......................................

440 441 444 444

Chapter 13

Configuring storage unit groups .................................... 447

About storage unit groups ............................................................ Creating storage unit groups for backups ........................................ Creating storage unit groups for snapshots ..................................... Deleting a storage unit group ........................................................ Storage unit selection criteria within a group .................................. Media server load balancing ................................................... Other load balancing methods ................................................ Exception to the storage unit selection criteria .......................... About disk spanning within storage unit groups ............................... 447 448 449 451 452 453 454 455 455

Chapter 14

Configuring storage lifecycle policies ........................... 457

About storage lifecycle policies ..................................................... Creating a storage lifecycle policy .................................................. Storage lifecycle policy validation dialog box ............................. Storage lifecycle policy Validation Report tab ............................ Deleting a storage lifecycle policy .................................................. Storage Lifecycle Policy dialog box settings ..................................... Hierarchical view of storage operations in the Storage lifecycle policy dialog box ........................................................................... Creating a hierarchical operation list in an SLP .......................... Adding a non-hierarchical operation to an SLP .......................... Modifying the hierarchy of operations in an SLP ........................ Removing an operation from the storage operation list ............... Adding a storage operation to a storage lifecycle policy ..................... New or Change Storage Operation dialog box settings ................. Backup operation ................................................................. Backup From Snapshot operation ............................................ Duplication operation ........................................................... Import operation .................................................................. Index From Snapshot operation .............................................. Replication operation ............................................................ Snapshot operation ............................................................... Operation types in a storage lifecycle policy .............................. Retention types for storage lifecycle policy operations ................ Retention type mixing for storage operations ............................ 457 458 459 460 461 462 464 466 466 467 468 468 471 473 475 476 478 479 482 483 490 491 496

18

Contents

About writing multiple copies using a storage lifecycle policy ............. How the order of the operations determines the copy order .......... About ensuring successful copies using lifecycles ....................... About storage lifecycle policy versions ........................................... Storage lifecycle changes and versioning .................................. When changes to storage lifecycle policies become effective ....................................................................... Deleting old storage lifecycle policy versions ............................. LIFECYCLE_PARAMETERS file for optional SLP-managed job configuration ....................................................................... About batch creation logic in Storage Lifecycle Manager .............. Lifecycle operation administration using the nbstlutil command .........

496 497 497 498 499 500 501 502 508 509

Section 4
Chapter 15

Configuring backups ................................................ 511

Creating policies for backups and snapshots .............. 513
About the Policies utility .............................................................. Using the Policies utility .............................................................. Planning for policies ................................................................... Example of one client in multiple policies ................................. Policy attributes that affect how clients are grouped in policies ......................................................................... About Microsoft DSFR backups ............................................... Creating a policy using the Policy Configuration Wizard .................... Creating a policy without using the Policy Configuration Wizard ........ Adding or changing schedules in a policy ........................................ Changing multiple policies at one time .......................................... Copying or moving policy items to another policy or server ............... Deleting schedules, backup selections, or clients from a policy ............ Policy Attributes tab ................................................................... Policy type (policy attribute) ................................................... Data classifications (policy attribute) ....................................... Policy storage (policy attribute) ............................................... Policy volume pool (policy attribute) ........................................ Take checkpoints every __ minutes (policy attribute) .................. Limit jobs per policy (policy attribute) ...................................... Job priority (policy attribute) .................................................. Media Owner (policy attribute) ................................................ Go into effect at (policy attribute) ............................................ Follow NFS (policy attribute) .................................................. Backup Network Drives (policy attribute) .................................. Cross mount points (policy attribute) ....................................... 514 514 516 519 520 521 524 525 526 526 528 529 529 530 534 535 538 540 544 545 546 546 547 548 550

Contents

19

Compression (policy attribute) ................................................ Encryption (policy attribute) ................................................... Collect disaster recovery information for Bare Metal Restore (policy attribute) ............................................................ Collect true image restore information (policy attribute) with and without move detection ............................................. Allow multiple data streams (policy attribute) ............................ Disable client-side deduplication (policy attribute) ...................... Enable granular recovery (policy attribute) ............................... Use accelerator (policy attribute) ............................................. Keyword phrase (policy attribute) ............................................ Enable indexing for search (policy attribute) .............................. Snapshot Client (policy attributes) ........................................... Microsoft Exchange (policy attributes) ..................................... Schedules tab ............................................................................ Schedule Attributes tab ............................................................... Name (schedule attribute) ...................................................... Type of backup (schedule attribute) ......................................... Synthetic backup (schedule attribute) ...................................... Accelerator forced rescan (schedule attribute) ........................... Enable indexing for search (schedule attribute) .......................... Calendar (schedule attribute) .................................................. Frequency (schedule attribute) ................................................ Instant Recovery (schedule attribute) ....................................... Multiple copies (schedule attribute) ......................................... Override policy storage (schedule attribute) .............................. Override policy volume pool (schedule attribute) ........................ Override media owner (schedule attribute) ................................ Retention (schedule attribute) ................................................. Media multiplexing (schedule attribute) .................................... Start Window tab ....................................................................... Adding, changing, or deleting a time window in a schedule .......... Example of schedule duration ................................................. Excluding dates from a policy schedule ........................................... Calendar Schedule tab ................................................................. Scheduling by specific dates ................................................... Scheduling by recurring days of the week ................................. Scheduling by recurring days of the month ............................... How NetBackup determines which schedule to run next .................... About schedule windows that span midnight ................................... How open schedules affect calendar-based and frequency-based schedules ............................................................................

554 556 556 556 560 564 564 565 577 577 579 579 579 580 580 580 589 590 590 591 591 593 595 600 601 601 602 605 612 612 615 616 617 617 617 619 620 622 623

20

Contents

Creating an open schedule in the NetBackup Administration Console ........................................................................ Runtime considerations that affect backup frequency ................. About the Clients tab ................................................................... Adding or changing clients in a policy ...................................... Browse for Hyper-V virtual machines ....................................... Backup Selections tab .................................................................. Adding backup selections to a policy ........................................ Verifying the Backup Selections list ......................................... How to reduce backup time .................................................... Pathname rules for Windows client backups .............................. Pathname rules for Windows disk image (raw) backups ............... Pathname rules for Windows registry backups ........................... About hard links to files and directories ................................... Pathname rules for UNIX client backups ................................... Pathname rules for NetWare NonTarget clients ......................... Pathname rules for NetWare Target clients ............................... Pathname rules for the clients that run extension products .......... About the directives on the Backup Selections list ...................... Files that are excluded from backups by default ......................... About excluding files from automatic backups ........................... Files that are excluded by Microsoft Windows Backup ................. VMware Policy tab ...................................................................... Hyper-V Policies tab ................................................................... Disaster Recovery tab .................................................................. Adding policies to the Critical Policies list of a catalog backup policy ........................................................................... Creating a Vault policy ................................................................ Performing manual backups ......................................................... Active Directory granular backups and recovery .............................. System requirements for Active Directory granular NetBackup backups and recovery ...................................................... Creating a policy that allows Active Directory granular restores ........................................................................ Restoring Active Directory objects ........................................... Troubleshooting granular restore issues ...................................

626 627 627 628 630 631 632 634 636 637 639 641 642 644 651 653 653 653 664 665 666 666 668 669 672 672 674 675 675 676 677 679

Chapter 16

Synthetic backups ............................................................. 683

About synthetic backups .............................................................. Recommendations for synthetic backups and restores ....................... Synthetic full backups ................................................................. Synthetic cumulative incremental backups ..................................... 683 684 686 688

Contents

21

Schedules that must appear in a policy for synthetic backups ............. Adding clients to a policy for synthetic backups ............................... Change journal and synthesized backups ........................................ True image restore and synthesized backups ................................... Displaying synthetic backups in the Activity Monitor ........................ Logs produced during synthetic backups ......................................... Synthetic backups and directory and file attributes .......................... Using the multiple copy synthetic backups method ........................... Configuring multiple copy synthetic backups ............................ Configuration variables ......................................................... Configuration examples ......................................................... Optimized synthetic backups using OpenStorage ............................. Optimized synthetic backups for deduplication ................................

690 690 691 691 691 692 692 693 694 695 696 697 697

Chapter 17

Protecting the NetBackup catalog ................................. 699

About the NetBackup catalog ........................................................ About the catalog upon upgrade to NetBackup 7.5 ............................ Using the cat_import and cat_export commands ........................ Parts of the NetBackup catalog ..................................................... About the NetBackup image database ....................................... About the NetBackup relational database .................................. Protecting the NetBackup catalog .................................................. About catalog backups ........................................................... Recovering the catalog ................................................................ Disaster recovery emails and the disaster recovery file ...................... Archiving the catalog .................................................................. Creating a catalog archiving policy .......................................... Catalog archiving commands .................................................. When to catalog archive ........................................................ Extracting images from the catalog archives ............................. Estimating catalog space requirements .......................................... NetBackup file size considerations ........................................... About the binary catalog format .............................................. Moving the image catalog ...................................................... About image catalog compression ............................................ 699 700 700 701 702 704 707 708 719 719 719 721 722 723 723 724 726 726 727 728

Chapter 18

About the NetBackup relational database ................... 733

About the NetBackup relational database (NBDB) installation ............. About NetBackup master server installed directories and files ............................................................................. About the NetBackup configuration entry ................................. Sybase SQL Anywhere server management ............................... 733 736 742 743

22

Contents

Sybase SQL Anywhere and clustered environments .................... Using the NetBackup Database Administration utility ....................... About the General tab of the NetBackup Database Administration utility ........................................................................... About the Tools tab of the NetBackup Database Administration utility ........................................................................... Post-installation tasks ................................................................. Changing the database password ............................................. Moving NBDB database files after installation ........................... Adding a mirrored transaction log ........................................... Creating the NBDB database manually ...................................... About backup and recovery procedures .......................................... Database transaction log ........................................................ About catalog recovery .......................................................... Commands for backing up and recovering the relational databases ...................................................................... About the catalog backup process ............................................ Unloading the NetBackup database ................................................ Terminating database connections ................................................ Moving the NetBackup database from one host to another ................. Moving the EMM server to a Windows cluster .................................. Removing the EMM server from a Windows cluster ..........................

743 744 745 752 762 762 763 764 765 767 767 768 768 769 771 772 772 773 774

Chapter 19

Managing backup images ................................................ 775

About the Catalog utility .............................................................. About searching for backup images ............................................... Verifying backup images .............................................................. Viewing job results ..................................................................... Promoting a copy to a primary copy ............................................... Duplicating backup images ........................................................... About multiplexed duplication considerations ........................... Jobs that appear while making multiple copies ........................... Expiring backup images ............................................................... About importing backup images .................................................... Importing backup images, Phase I ........................................... Importing backup images, Phase II .......................................... About importing expired images ............................................. Initiating an import without the Import Wizard ......................... About importing Backup Exec media ........................................ Differences between importing, browsing, and restoring Backup Exec and NetBackup images ............................................. 775 776 778 779 779 781 786 787 788 789 789 791 792 792 794 797

Contents

23

Section 5
Chapter 20

Configuring replication .......................................... 801

About NetBackup replication .......................................... 803
About NetBackup replication ........................................................ About NetBackup Auto Image Replication ....................................... Auto Image Replication setup overview .................................... About the domain relationship ............................................... Configuring a target for MSDP replication ................................ About the replication topology for Auto Image Replication .......... Viewing the replication topology for Auto Image Replication .................................................................... About the storage lifecycle policies required for Auto Image Replication ................................................................... One-to-many Auto Image Replication model ............................. Cascading Auto Image Replication model .................................. How to resolve volume changes for Auto Image Replication ......... About restoring from a backup at a target master domain ............ Reporting on Auto Image Replication jobs ................................ About Replication Director ........................................................... 803 804 805 807 808 810 811 816 820 820 823 826 827 828

Section 6
Chapter 21

Monitoring and reporting ...................................... 831

Monitoring NetBackup activity ....................................... 833
About the Activity Monitor .......................................................... Activity Monitor topology ............................................................ About filtering topology objects .............................................. About the Jobs tab ...................................................................... Viewing job details ................................................................ Showing or hiding column heads ............................................. Monitoring the detailed status of a selected job .......................... Deleting completed jobs ......................................................... Canceling a job that has not completed ..................................... Restarting a completed job ..................................................... Suspending restore or backup jobs ........................................... Resuming suspended or incomplete jobs ................................... Printing job list information ................................................... Printing job detail information ................................................ Copying Activity Monitor text to a file ...................................... Changing the Job Priority dynamically from the Activity Monitor ........................................................................ About the Services tab ................................................................. 833 835 836 836 838 838 839 839 839 840 840 840 841 841 842 842 843

24

Contents

Types of services .................................................................. Using the nbrbutil utility to configure the NetBackup Resource Broker .......................................................................... Starting or stopping a service ................................................. Monitoring NetBackup services ............................................... About the Processes tab ............................................................... Monitoring NetBackup processes in the Process Details dialog box .............................................................................. About the Drives tab ................................................................... Monitoring NetBackup tape drives .......................................... Cleaning tape drives from the Activity Monitor .......................... About the jobs database ............................................................... About changing the default values ........................................... About the BPDBJOBS_OPTIONS environment variable ................ bpdbjobs command line options .............................................. Enabling the bpdbjobs debug log ............................................. About the Device Monitor ............................................................ About media mount errors ........................................................... About pending requests and actions ............................................... About pending requests for storage units .................................. Managing pending requests and actions ......................................... Resolving a pending request ................................................... Resolving a pending action ..................................................... Resubmitting a request .......................................................... Denying a request .................................................................

847 847 852 852 853 858 861 862 863 863 864 864 866 866 867 867 868 868 869 869 870 871 871

Chapter 22

Auditing NetBackup operations ..................................... 873

About NetBackup auditing ........................................................... Viewing the current audit settings ................................................. Configuring auditing on a NetBackup master server .......................... Audit alert notification for audit failures ........................................ User identity in the audit report .................................................... Auditing host property changes .................................................... Using the command line -reason or -r option ................................... Viewing the audit report .............................................................. nbaudit log behavior ................................................................... Retaining and backing up audit trail records .................................... 873 876 877 878 879 880 880 881 885 885

Chapter 23

Reporting in NetBackup ................................................... 887

About the Reports utility ............................................................. 888 Running a report ........................................................................ 889 Copying report text to another document ........................................ 889

Contents

25

Saving or exporting a report ......................................................... Printing a report ........................................................................ Status of Backups report ............................................................. Client Backups report ................................................................. Problems report ......................................................................... All Log Entries report .................................................................. Images on Media report ............................................................... Media Logs report ....................................................................... Images on Tape report ................................................................. Tape Logs report ........................................................................ Tape Contents report .................................................................. Tape Summary report ................................................................. Tape Written report .................................................................... Tape Lists report ........................................................................ Images on Disk report ................................................................. Disk Logs report ......................................................................... Disk Storage Unit Status report ..................................................... Disk Pool Status report ................................................................

890 890 891 891 891 891 892 892 892 892 892 892 893 893 893 894 894 894

Section 7
Chapter 24

Administering NetBackup ..................................... 895

Management topics ........................................................... 897
NetBackup naming conventions .................................................... Wildcard use in NetBackup ........................................................... How to administer devices on other servers ..................................... How to access media and devices on other hosts ............................... About the Enterprise Media Manager ............................................. About Enterprise Media Manager domain requirements .............. About sharing an EMM server ................................................. 897 898 900 901 902 902 903

Chapter 25

Accessing a remote server ............................................... 905

Accessing remote servers ............................................................. About adding a NetBackup server to a server list .............................. Adding a server to a remote server list ..................................... About choosing a remote server to administer ................................. Using the change server command to administer a remote server ........................................................................... Indicating a remote system upon login ..................................... About using the Remote Administration Console .............................. About using the Java Windows Administration Console ..................... 905 906 907 909 910 910 912 913

26

Contents

About running the NetBackup Administration Console on a NetBackup client ................................................................................. 913 About troubleshooting remote server administration ........................ 914

Chapter 26

Using the NetBackup-Java administration console ........................................................................... 915

About the NetBackup-Java Administration Console ........................... About authorizing NetBackup-Java users ........................................ Authorization file (auth.conf) characteristics ................................... About authorizing nonroot users for specific applications .................. About authorizing specific tasks in jbpSA ....................................... About authorizing NetBackup-Java users on Windows ....................... Restricting access to NetBackup-Java applications on Windows .......... Runtime configuration options for NetBackup-Java and Java Windows Administration Console ......................................................... FIREWALL_IN ..................................................................... FORCE_IPADDR_LOOKUP ...................................................... INITIAL_MEMORY, MAX_MEMORY ......................................... MEM_USE_WARNING ........................................................... NBJAVA_CLIENT_PORT_WINDOW .......................................... NBJAVA_CORBA_DEFAULT_TIMEOUT .................................... NBJAVA_CORBA_LONG_TIMEOUT .......................................... PBX_PORT .......................................................................... VNETD_PORT ...................................................................... About logging the command lines that the NetBackup interfaces use ..................................................................................... About customizing jnbSA and jbpSA with bp.conf entries .................. About improving NetBackup-Java performance ................................ About running the Java console locally ..................................... About running a console locally and administering a remote server ........................................................................... About enhancing console performance ..................................... About determining better performance when console is run locally or uses remote display back .................................... NetBackup-Java performance scenario 1 ................................... NetBackup-Java performance scenario 2 ................................... About adjusting time zones in the NetBackup-Java console ................ Adjusting the time zone in the NetBackup-Java console ............... Configuring a custom time zone in the NetBackup-Java console ......................................................................... 915 918 919 921 922 923 924 924 925 926 928 928 928 929 929 930 930 930 931 931 932 932 933 934 934 935 935 936 937

Contents

27

Chapter 27

Alternate server restores ................................................. 939

About alternate server restores ..................................................... About supported configurations for alternate server restores ............. About performing alternate server restores ..................................... About modifying the NetBackup catalogs .................................. Overriding the original server for restores ................................ About enabling automatic failover to an alternate server ............. Expiring and importing media for alternate server restores .......... 939 940 941 942 943 945 946

Chapter 28

Managing client restores ................................................. 949

About server-directed restores ...................................................... About client-redirected restores .................................................... About restore restrictions ...................................................... About allowing all clients to perform redirected restores ............. About allowing a single client to perform redirected restores ........................................................................ About allowing redirected restores of a clients files .................... Examples of redirected restores .............................................. About restoring the files that have Access Control Lists (ACLs) ........... Restoring files without restoring ACLs ..................................... About restoring the System State .................................................. Restoring the System State .................................................... 949 950 950 951 952 952 953 957 958 958 959

Chapter 29

Powering down and rebooting NetBackup servers ............................................................................ 961

Powering down and rebooting NetBackup servers ............................. Shutting down and starting up all NetBackup services on Windows ............................................................................. Rebooting a NetBackup server ...................................................... Rebooting a NetBackup media server ............................................. 961 962 962 962

Chapter 30

About Granular Recovery Technology ........................... 965

About installing and configuring Network File System (NFS) for Active Directory Granular Recovery .................................................. About configuring Services for Network File System (NFS) on the Windows 2008 and Windows 2008 R2 NetBackup media server and NetBackup clients ........................................................... Enabling Services for Network File System (NFS) on Windows 2008 or Windows 2008 R2 ................................................ Disabling the Client for NFS on the media server ........................ 965

966 967 971

28

Contents

Disabling the Server for NFS .................................................. About configuring Services for Network File System (NFS) on the Windows 2003 R2 SP2 NetBackup media server and NetBackup clients ................................................................................ Installing Services for NFS on the Windows 2003 R2 SP2 media server ........................................................................... Installing Services for NFS on Active Directory domain controllers or ADAM/LDS hosts with Windows 2003 R2 SP2 .............................................................................. Configuring a UNIX or Linux media server and Windows clients for backups and restores that use Granular Recovery Technology ......................................................................... Configuring a different network port for NBFSD .............................. Configuring the log on account for the NetBackup Client Service for NetBackup for Active Directory on Windows .............................

972

974 975

978

981 981 982

Index ................................................................................................................... 983

Section

About NetBackup

Chapter 1. Introducing NetBackup interfaces Chapter 2. Administering NetBackup licenses

30

Chapter

Introducing NetBackup interfaces

This chapter includes the following topics:

About NetBackup NetBackup documentation About NetBackup administration interfaces About using the NetBackup Administration Console NetBackup configuration wizards Activity Monitor utility NetBackup Management utilities Media and Device Management utilities Running the Troubleshooter Access Management utility

About NetBackup
NetBackup provides a complete, flexible data protection solution for a variety of platforms. The platforms include Microsoft Windows, UNIX, Linux, and NetWare systems. NetBackup administrators can set up periodic or calendar-based schedules to perform automatic, unattended backups for clients across a network. An administrator can carefully schedule backups to achieve systematic and complete backups over a period of time, and optimize network traffic during off-peak hours.

32

Introducing NetBackup interfaces About NetBackup

The backups can be full or incremental. Full backups back up all client files. Incremental backups back up only the files that have changed since the last backup. The NetBackup administrator can allow users to back up, restore, or archive the files from their computer. (An archive operation backs up a file, then deletes it from the local disk if the backup is successful.) NetBackup includes both the server and the client software as follows:

Server software resides on the computer that manages the storage devices. Client software resides on computer(s) that contain data to back up. (Servers also contain client software and can be backed up.)

Figure 1-1 shows an example of a NetBackup storage domain. Figure 1-1 NetBackup storage domain example
NetBackup master server

Media servers

SAN

Media Manager tape BasicDisk storage unit storage unit

OpenStorage disk pool

NetBackup clients

NetBackup accommodates multiple servers that work together under the administrative control of one NetBackup master server in the following ways:

The master server manages backups, archives, and restores. The master server is responsible for media and device selection for NetBackup. Typically, the master server contains the NetBackup catalog. The catalog contains the internal

Introducing NetBackup interfaces NetBackup documentation

33

databases that contain information about NetBackup backups and configuration.

Media servers provide additional storage by allowing NetBackup to use the storage devices that are attached to them. Media servers can also increase performance by distributing the network load. Media servers can also be referred to by using the following terms:

Device hosts (when tape devices are present) Storage servers (when I/O is directly to disk) Data movers (when data is sent to independent, external disk devices like OpenStorage appliances)

During a backup or archive, the client sends backup data across the network to a NetBackup server. The NetBackup server manages the type of storage that is specified in the backup policy. During a restore, users can browse, then select the files and directories to recover. NetBackup finds the selected files and directories and restores them to the disk on the client.

NetBackup documentation
NetBackup documentation is part of the NetBackup media kit and can be found in a directory on the installation DVD for each release platform. The documents are in Adobe Portable Document Format (PDF), viewable with the Adobe Acrobat Reader. Download the reader from http://www.adobe.com. Symantec assumes no responsibility for the installation and use of the reader. For a complete list of NetBackup technical documents, see the Related Documents appendix in the NetBackup Release Notes. The Symantec support Web site contains links to the most recent documentation plus a list of helpful how-to and product alert topics. http://www.symantec.com/business/support/index?page=landing&key=15143

About NetBackup administration interfaces

The NetBackup administrator has a choice of several interfaces to use to administer NetBackup. All the interfaces have similar capabilities. The best choice depends on personal preference and the workstation that is available to the administrator.

34

Introducing NetBackup interfaces About NetBackup administration interfaces

Table 1-1

NetBackup administration interfaces

NetBackup On Windows: Administration Select NetBackup Administration Console from the Start menu. Console Or, install and use the Java Windows Administration Console. The Java Windows Administration Console is not automatically installed on the system. Installation is available on the main NetBackup for Windows Servers installation screen. On UNIX: The NetBackup Administration Console is the recommended interface and is the interface referred to by most procedures and examples in the documentation. Start the Java-based, graphical user interface by running the jnbSA command.

Note: To log in to any NetBackup Administration Console, your login credentials must be
authenticated from the connecting master or media server. This is true whether or not NetBackup Access Control (NBAC) is in use. Remote Administration Console You can install the Remote Administration Console on a Windows computer to administer or manage any remote NetBackup serverWindows or UNIX. No license is required to install the Remote Administration Console. See Figure 1-2 See About using the Remote Administration Console on page 912. Command line Enter NetBackup commands at the system prompt or use them in scripts. All NetBackup administrator programs and commands require root or administrator user privileges by default. For complete information on all NetBackup commands, see the NetBackup Commands Reference Guide.

Introducing NetBackup interfaces About NetBackup administration interfaces

35

Figure 1-2

NetBackup installation window

About running the Windows-based NetBackup Administration Console

The NetBackup Administration Console is installed with the NetBackup server software. The NetBackup Administration Console is the starting point for administering NetBackup. The left pane in the console contains a node for each major area of NetBackup administration. Click a node to display the information that is related to that node in the Details pane on the right. The menus contain commands relevant to the selected node. Note: If there is more than one NetBackup server, the NetBackup Administration Console can be run on more than one server at one time. However, if more than one administrator makes changes to the configuration, the results are unpredictable.

Starting the Java-based Windows Display Console

The NetBackup-Java Windows Display Console is provided with NetBackup software. Use the Windows Display Console to administer UNIX NetBackup servers where a Java-capable UNIX system is not available.

36

Introducing NetBackup interfaces About NetBackup administration interfaces

See the NetBackup Installation Guide for information about how to install the Windows Display Console. You can also use the Windows Display Console to administer a NetBackup UNIX or Windows server. Or, use a point-to-point (PPP) connection between the display console and other servers to perform remote administration. The following procedure describes how to start the Windows display console. To start the Windows display console

On a Windows system where the Windows Display Console is installed and configured, select Start>Programs>SymantecNetBackup>NetBackup-Java Version 7.5. The login screen for the NetBackup Administration Console displays the host name. Log into another server by typing the name of another host in the Host name field. Or, select a host name from the drop-down list. In the login screen, type your user name and password. To log into a Windows server, enter both the domain of the server and the user name as follows:
domain_name\user_name

The domain_name specifies the domain of the NetBackup host. If the host is not a member of a domain, the domain_name is not required.

Click Login to log into the NetBackup-Java application server program on the specified server. The interface program continues to communicate through the server that is specified in the login screen for the remainder of the current session. The default host is the last host that was successfully logged into. The drop-down list contains the names of other hosts that have been logged into.

Administering remote servers and servers of different versions

In a site that contains multiple master servers, you can configure the systems so that one NetBackup Administration Console can access remote servers. Indicate a remote server by using one of the following methods:

Use the File > Change Server menu command. Use the NetBackup-Java Administration Console. Indicate a remote system upon NetBackup login.

Note: To log in to any NetBackup Administration Console, your login credentials must be authenticated from the connecting master or media server. This is true whether or not NetBackup Access Control (NBAC) is in use.

Introducing NetBackup interfaces About NetBackup administration interfaces

37

The NetBackup Administration Console on Windows and the NetBackup-Java Administration Console on UNIX are backward-compatible in the following situations:

From the console of an x.x.x (double-dot) or x.x.x.x (triple-dot) release to the console of any release that shares the fist and second digits. For example, a NetBackup 7.0.1 console can administer a NetBackup 7.0 master server. However, a NetBackup 7.1 console (a single-dot release) cannot administer a 7.0 or 7.0.1 master server because the second digits are not the same. Figure 1-3 shows examples of each. The NetBackup-Java Administration Console on UNIX offers an exception when the -r option is used with the jnbSA command to start the console. The -r option lets a x.x NetBackup-Java Administration Console connect to another UNIX master server that is several versions earlier, regardless of whether the second digit is the same. For example, a 7.5 NetBackup-Java Administration Console can connect to a NetBackup master server at 7.1, 7.0, 6.5, or 6.0. Figure 1-4 shows examples of back-level console support. Use the -r option to launch the console on the UNIX system as follows:
./jnbSA -r release_version

For example, to connect to a 7.0 master server from a 7.5 NetBackup-Java Administration Console, enter the following on the 7.5 master server to start the 7.0 console:
./jnbSA -r 7.0

If no -r option is specified, the default is the current NetBackup version. Figure 1-3 Examples of supported and unsupported back-level console configurations
7.0.1 No 7.0 7.5 7.1.0.1 Yes 7.1 7.1.0.3 No 7.0

7.0.1 Yes

Figure 1-4

Examples of additional NetBackup-Java Administration Console back-level support using the jnbSA -r option
7.1 Yes

7.5 Yes 6.0

6.5

38

Introducing NetBackup interfaces About using the NetBackup Administration Console

See the NetBackup Installation Guide for information about installing earlier versions of the NetBackup-Java Administration Console.

About using the NetBackup Administration Console

The NetBackup Administration Console provides a Windows-based interface through which the administrator can manage NetBackup. Figure 1-5 NetBackup Administration Console

1 2 3

5 6 7

Introducing NetBackup interfaces About using the NetBackup Administration Console

39

Table 1-2

NetBackup Administration Console

Number Description
1 The name of the currently selected master server. The information in the NetBackup Administration Console applies to this server only. 2 Activity Monitor Displays the NetBackup job information. The Activity Monitor provides the control over the jobs, services, processes, and drives. 3 NetBackup Management Contains the utilities to create and view reports, to configure policies, storage units, catalog backups, and a utility for configuring host properties. 4 Media and Device Management Contains the utilities for managing the media and devices that NetBackup uses to store backups. 5 Access Management Use to define user groups and grant permissions to these groups. The contents are viewable only by a Security Administrator when NetBackup Access Control (NBAC) is configured. For more information about NetBackup Access Control, see the NetBackup Security and Encryption Guide. 6 7 Additional licensed utilities appear under the main NetBackup nodes. The Details pane contains the configuration wizards and details specific to the utility that is selected.

Command prompts are used to perform some operations. NetBackup commands are described in the NetBackup Commands Reference Guide. The NetBackup Administration Console menus are described in the online Help.

Standard and user toolbars

Upon opening the NetBackup Administration Console, a standard toolbar appears by default. When certain utilities are selected, a user toolbar appears. The buttons on the toolbar provide shortcuts for menu commands. Slowly drag the pointer over a button to display a button description label. To display or hide the standard NetBackup toolbar, click View > Toolbar.

40

Introducing NetBackup interfaces NetBackup configuration wizards

About customizing the NetBackup Administration Console

The View menu contains options to customize the NetBackup Administration Console. For example, the Options selection opens a series of tabs that contains various configuration options for the different utilities. Select the Administration Console tab to configure the Auto log off timeout option. Use this option of automatically log a user out of the NetBackup Administration Console after a period of inactivity. Click the Help button for more information about the dialog box options.

NetBackup configuration wizards

The easiest way to configure NetBackup is to use the configuration wizards. The wizard selection varies in the Details pane on the right, depending on which NetBackup utility is selected in the left portion of the screen. The wizards help configure the basic properties of a NetBackup environment. After completing these basic wizards, you should be able to back up clients and perform a back up the NetBackup catalog. Table 1-3 Wizard
Getting Started Wizard

Configuration wizards

Description
Configures NetBackup for the first time. The wizard leads the user through the necessary steps to a working NetBackup configuration. The Getting Started Wizard is comprised of the following wizards, which can also be run separately, outside of the Getting Started Wizard:

Device Configuration Wizard Volume Configuration Wizard Catalog Recovery Wizard Policy Configuration Wizard

Configure more advanced properties through the NetBackup Administration Console. You also can use the NetBackup Administration Console if you prefer not to use the wizards.

Note: Do not use the Getting Started Wizard to configure policies for Replication
Director. Device Configuration Wizard Click Configure Disk Storage Servers to configure NetBackup to use robotic tape libraries and tape drives.

Introducing NetBackup interfaces Activity Monitor utility

41

Table 1-3 Wizard

Storage Server Configuration Wizard

Configuration wizards (continued)

Description
Click Configure Disk Storage Servers to create the servers that manage disk storage. The wizard appears if an Enterprise Disk Option license or NetBackup Deduplication Option license is installed.

Cloud Storage Server Configuration Wizard Disk Pool Configuration Wizard

Click Configure Cloud Storage Servers to add or configure a cloud provider. For more information, see the NetBackup Cloud Administrator's Guide. Click Configure Disk Pool to create pools of disk volumes for backup by one or more media servers. The wizard appears if an Enterprise Disk Option license or NetBackup Deduplication Option license is installed.

Volume Configuration Wizard Catalog Recovery Wizard

Click Configure Volumes to configure removable media to use for backups. Click Configure the Catalog Backup to set up catalog backups. Catalog backups are essential to recover data in the case of a server failure or crash. Click Create a Policy to set up one of the policy types:

Policy Configuration Wizard

A policy to back up file systems, databases, or applications. A policy to create snapshots. A policy for to protect VMware or Hyper-V virtual machines. A policy to back up NDMP hosts.

Note: Do not use the Policy Configuration Wizard to configure policies for
Replication Director. Import Images Wizard Click Import Images to import NetBackup images in a two-part process. See About importing backup images on page 789. Catalog Recovery Wizard Click Recover the Catalog to recover a catalog backup in a disaster recovery situation. For more information about NetBackup disaster recovery, see the NetBackup Troubleshooting Guide.

Activity Monitor utility

Use the Activity Monitor utility to monitor and control NetBackup jobs, services, processes, and drives. See About the Activity Monitor on page 833.

42

Introducing NetBackup interfaces NetBackup Management utilities

NetBackup Management utilities

The following topics describe the utilities that are found under the NetBackup Management node in the NetBackup Administration Console tree:

Reports Use the Reports utility to compile information for to verify, manage, and troubleshoot NetBackup operations. See About the Reports utility on page 888. Policies Use the Policies utility to create and specify the backup policies that define the rules for backing up a group of clients. For example, the backup policy specifies when automatic backups occur for the clients that are specified in the policy. The backup policy also specifies whether users can perform their own backups and when. The administrator can define any number of backup policies, each of which can apply to one or more clients. A NetBackup client must belong to at least one backup policy to be backed up. See About the Policies utility on page 514. Storage Use the Storage utility to display storage unit information and manage NetBackup storage units. A storage unit can be part of a storage unit group as well as part of a storage lifecycle policy, both of which are configured within the Storage utility. Storage units simplify administration because once defined, the NetBackup policy points to a storage unit rather than to the individual devices it contains. For example, if a storage unit contains two drives and one is busy, NetBackup can use the other drive without administrator intervention. The media can be one of the following:

Removable (such as tape in a robot or a stand-alone drive). The devices in a removable-media storage unit must attach to a NetBackup master or media server and be under control of the NetBackup Media Manager component. The administrator first configures the drives, robots, and media in NetBackup, then defines the storage units. During a backup, NetBackup sends data to the storage unit that the backup policy specifies. During a backup, Media Manager picks a device to which the NetBackup client sends data. Disk (such as a file directory within a file system or a collection of disk volumes, either independent file systems or in an appliance). The administrator specifies the directory, volume, or disk pool during the storage unit setup. For BasicDisk, NetBackup sends the data to that directory

Introducing NetBackup interfaces NetBackup Management utilities

43

during backups. For the Enterprise Disk Options, NetBackup sends the data to the storage server (the host that writes to the storage). Media Manager is not involved. For disk pool storage, the administrator first defines the storage server and (depending on the disk type) its logon credentials. Depending on disk type, the administrator may have to define logon credentials for the storage itself. The administrator also selects the disk volumes that comprise the disk pool. To create a storage unit, the administrator selects a disk pool and (depending on the disk type) selects the media server(s) to move the data. Note: Only the storage units that point to shareable disk can specify more than one media server. See About the Storage utility on page 397.

Catalog Use the Catalog utility to create and configure a catalog backup, which is a special type of backup that NetBackup requires for its own internal databases. These databases, called catalogs, are located on the NetBackup master and media server (default location). The catalogs contain information on every client backup. Catalog backups are tracked separately from other backups to ensure recovery in case of a server crash. The Catalog utility is also used for the following actions:

To duplicate a backup image To promote a backup image from a copy to the primary backup copy To manually expire backup images To import expired backup images or images from another NetBackup server

To search for a backup image to verify the contents of the media with what is recorded in the NetBackup catalog See About the Catalog utility on page 775.

Host Properties Use the Host Properties utility to customize NetBackup configuration options. In most instances, no changes are necessary. However, Host Properties lets the administrator customize NetBackup to meet specific site preferences and requirements for master servers, media servers, and clients. See About the NetBackup Host Properties on page 57.

44

Introducing NetBackup interfaces Media and Device Management utilities

Media and Device Management utilities

The following topics describe the utilities that are found under Media and Device Management utilities in the NetBackup Administration Console tree. Table 1-4 Utility
Device Monitor Media Devices Credentials

Media and device management utilities

Description
Manages drives, device paths, and service requests for operators. Adds and manages removable media. Adds, configures, and manages storage devices. Adds, removes, and manages log on credentials for the following:

NDMP hosts (requires the NetBackup for NDMP license). Storage servers (requires a NetBackup Deduplication Option or an Enterprise Disk Option license).

Credentials appears only if one of the previously mentioned license keys is installed.

Running the Troubleshooter

When a NetBackup job returns a status code, use the Troubleshooter to find a description of the problem and a recommended solution. The Troubleshooter is particularly useful for understanding the status of a job in the Activity Monitor or in the Reports utility. To run the Troubleshooter

In the NetBackup Administration Console, do one of the following:

To understand the status of In the left pane, click Activity Monitor. a job in the Activity Monitor In the right pane, select the Jobs tab at the bottom of the pane. Select a job from the list. To understand the status of a job in a report In the left pane, expand NetBackup Management > Reports. In the left pane, click the name of the report you want to run. For some reports, you must first expand a report group, and then click the name of the report. In the right pane, click Run Report.

Select a job from the list that is generated.

Introducing NetBackup interfaces Access Management utility

45

To look up a status code

Go to step 2.

Click Help > Troubleshooter. The dialog box that appears describes the status code on the Problem tab. Possible solutions can be found on the Troubleshoot tab. The Symantec Support tab displays the Web address of Symantec Support or the URL to a technote that addresses the specific error code.

If no explanation appears, enter a status code and click Lookup. The Troubleshooter provides assistance for NetBackup codes only. Assistance with Media and Device Management codes is available by using NetBackup online Help and searching for the particular status code.

See Viewing job details on page 838. See About the Jobs tab on page 836.

Access Management utility

NetBackup administrators can protect a NetBackup configuration by defining who may access NetBackup and what functions a user group can perform. This access control is configured by using the Access Management utility. Access Management is enabled when NetBackup Product Authentication and Authorization and NetBackup Access Control (NBAC) is installed and configured. For installation and configuration information, see Access Management in the NetBackup Security and Encryption Guide.

46

Introducing NetBackup interfaces Access Management utility

Chapter

Administering NetBackup licenses

This chapter includes the following topics:

About administering NetBackup licenses

About administering NetBackup licenses

License keys are added when the software is installed. Licenses can be added later in the License Key dialog box for separately-priced options. Note: Perform a manual hot catalog backup after updating license keys. An immediate, manual catalog backup prevents stale keys from being restored in case a catalog restore is necessary before the next scheduled catalog backup. See Backing up NetBackup catalogs manually on page 715. A NetBackup capacity licensing utility is now available, which reports on the total amount of data that is protected by NetBackup. For more information see the NetBackup Administrator's Guide, Volume II. Perform the following tasks from the NetBackup License Keys dialog box:

Add a new license. See Adding new license keys on page 49. Print a license. See Printing license key lists on page 50. Delete a license. See Deleting license keys on page 50.

48

Administering NetBackup licenses About administering NetBackup licenses

View the properties of one license. See Viewing license key properties on page 51. Export the license list. See Exporting license keys on page 51.

Restart the NetBackup Administration Console after any license updates.

Accessing license keys for a NetBackup server

Use the following procedure to access license keys for a NetBackup server. To access license keys for a NetBackup server

To view the license keys of the current server: In the NetBackup Administration Console, in the toolbar, click Help > License Keys. To view the license keys of another server: In the NetBackup Administration Console, in the toolbar, click File > Change Server, select another server, and click OK. In the toolbar, click Help > License Keys in the remote server.

Select the license details to view as follows:

Summary of active licensed features Summary of active capacity-based licensed features Displays a summary of the active features that are licensed on this server. This view lists each feature and the number of instances of the feature that are licensed. Displays the storage capacity for which the NetBackup environment is licensed and the capacity in use. The summary also notes whether the license is in compliance. The summary does not display the amount of physical storage space. All capacity values are calculated based on the definition that one terabyte = 1,099,511,627,776 bytes. The OpenStorage Disk Option, the PureDisk Storage Option, and the Virtual Tape Option do not display all values at this time.

Administering NetBackup licenses About administering NetBackup licenses

49

All registered license keys details

Displays the details of the license keys that are registered on this server. The view lists the following:

Each license key The server where the key is registered When the key was registered, The features that the key provides

Perform the following tasks from the NetBackup License Keys dialog box:

Add a new license. See To add new license keys on page 49. Print a license. See To print license key lists on page 50. Delete a license. See To delete license keys on page 51. View the properties of one license. See Viewing license key properties on page 51. Export the license list. See To export license keys on page 51.

Adding new license keys

Use the following procedure to add new license keys. To add new license keys

To add a license to the current server: In the NetBackup Administration Console, in the toolbar, click Help > License Keys. To add a license to another server: In the NetBackup Administration Console, in the toolbar, click File > Change Server, then select another server and click OK. Click Help > License Keys in the remote server.

In the NetBackup License Keys dialog box, click the New button.

50

Administering NetBackup licenses About administering NetBackup licenses

3 4

In the Add a new License Key dialog box, enter the license key and click Add. Perform a manual catalog backup after updating license keys. An immediate, manual catalog backup prevents stale keys from being restored in case a catalog restore is necessary before the next scheduled catalog backup. See Backing up NetBackup catalogs manually on page 715.

Printing license key lists

Use the following procedure to print license key lists. To print license key lists

In the NetBackup Administration Console, in the toolbar, click Help > License Keys. In the NetBackup License Keys dialog box, select the license key you want to print. If no selection is made, all licenses print. The printed information includes the following:

License key Name of the host Date the key was added Name of the product Number of instances Name of the feature Whether or not the license is valid Expiration date for the license

2 3

In the NetBackup License Keys dialog box, click the Print button. Make the print selections and click OK.

Deleting license keys

Use the following procedure to delete license keys.

Administering NetBackup licenses About administering NetBackup licenses

51

To delete license keys

In the NetBackup Administration Console, in the toolbar, click Help > License Keys. In the NetBackup License Keys dialog box, select the license key you want to delete from the license key list. If the key has more than one feature, all the features are listed in the dialog box. In the NetBackup License Keys dialog box, click the Delete button. Click OK to delete the key and all features that are associated with the key. If the key appears in the list more than one time, deleting one instance deletes all other instances of the key from the list.

2 3

Viewing license key properties

Use the following procedure to view the properties of a license key. To view the properties of a license key

In the NetBackup Administration Console, in the toolbar, click Help > License Keys. In the NetBackup License Keys dialog box, select one license and click the Properties button.

Exporting license keys

Use the following procedure to export license keys. To export license keys

1 2 3

In the NetBackup Administration Console, in the toolbar, click Help > License Keys. In the NetBackup License Keys dialog box, click the Export button. In the Save As dialog box, enter the path and the file name where you want the key properties of all licenses to be exported. Click Save. The exported file contains a list of each license key, along with the:

Name of the host Date the license was added Name of the product Number of instances Name of the feature Whether or not the license is valid Expiration date for the license

52

Administering NetBackup licenses About administering NetBackup licenses

Section

Configuring hosts

Chapter 3. Configuring Host Properties Chapter 4. Configuring server groups Chapter 5. Configuring host credentials Chapter 6. Managing media servers

54

Chapter

Configuring Host Properties

This chapter includes the following topics:

About the NetBackup Host Properties Access Control properties Active Directory host properties Backup Exec Tape Reader properties Bandwidth properties Busy File Settings properties Clean-up properties Client Name properties Client Attributes properties Client Settings properties for NetWare clients Client Settings (UNIX) properties Client Settings properties for Windows clients Cloud Storage properties Credential Access properties Data Classification properties Default Job Priorities properties Distributed application restore mapping properties Encryption properties

56

Configuring Host Properties

Enterprise Vault properties Enterprise Vault Hosts properties Exchange properties Exclude Lists properties Fibre Transport properties Firewall properties General Server properties Global Attributes properties Logging properties Login Banner Configuration properties Lotus Notes properties Media properties NDMP Global Credentials properties NetWare Client properties Network properties Network Settings Properties Port Ranges properties Preferred Network properties Resilient Network properties Resource Limit properties Restore Failover properties Retention Periods properties Servers properties SharedDisk properties SharePoint properties Symantec Products properties Throttle Bandwidth properties

Configuring Host Properties About the NetBackup Host Properties

57

Timeouts properties Universal Settings properties UNIX Client properties UNIX Server properties VMware Access Hosts properties VSP (Volume Snapshot Provider) properties Windows Client properties Configuration options not found in the Host Properties

About the NetBackup Host Properties

The Host Properties and configuration options let an administrator customize NetBackup to meet specific site preferences and requirements. In most instances, however, the NetBackup defaults provide satisfactory results. Figure 3-1 shows the Host Properties in the NetBackup Administration Console. Figure 3-1
1 2 3 4

Host Properties utility

58

Configuring Host Properties About the NetBackup Host Properties

Table 3-1

Host Properties utility

Number Description
1 2 The menu toolbar. The standard NetBackup toolbar. See Standard and user toolbars on page 39. 3 4 The name of the currently selected master server. The user toolbar is specific to the Host Properties utility. By default, the Host Properties user toolbar includes the following buttons: Select a host in the right pane and click Properties to view the properties of that host. Select a host in the right pane and click Connect to connect to that host.

Click Configure media server to name a media server and view its properties. Click Configure Client to name a client and view its properties. Click Configure Indexing Server to name an indexing server and view its properties.

You can select which buttons appear on the user toolbar. See Standard and user toolbars on page 39. 5 Right-click in the right pane to view the shortcut menu.

Generally, these options are configured in the NetBackupAdministrationConsole, under Host Properties. However, some options cannot be configured by using the NetBackup Administration Console. See Configuration options not found in the Host Properties on page 220. An administrator can use one of the following methods to change the defaults: Table 3-2 Configuration method
Host Properties

NetBackup Host Properties configuration methods

Description
To navigate to the various properties, select NetBackup Management > Host Properties. Depending on the host to be configured, select Master Servers, Media Servers, or Clients. See About the NetBackup Host Properties on page 57.

In the Windows registry

Use the bpgetconfig command to obtain a list of configuration entries, and then use bpsetconfig to change the entries in the registry.

Configuring Host Properties About the NetBackup Host Properties

59

Table 3-2 Configuration method

vm.conf file

NetBackup Host Properties configuration methods (continued)

Description
The vm.conf file contains configuration entries for media and device management. See the NetBackup Administrator's Guide, Volume II for more information.

On clients

Administrators can specify configuration options. See the NetBackup Backup, Archive, and Restore Getting Started Guide.

To change the properties of another client or server, the NetBackup server where you logged on using the NetBackup Administration Console must be in the Servers list on the other system. See Servers properties on page 202. For example, if you logged on to server_1 using the NetBackup Administration Console and want to change a setting on client_2, client_2 must include server_1 in its Servers list. Note: All updates to a destination host fail if Allow server file writes is not enabled on the destination host. This property is located in the Universal Settings properties. See Universal Settings properties on page 214. See About adding a NetBackup server to a server list on page 906.

Viewing host properties

The NetBackupAdministrationConsole displays properties for NetBackup master servers, media servers, and clients under Host Properties. Use the following procedure to view master server, media server, or client properties.

60

Configuring Host Properties About the NetBackup Host Properties

To view master server, media server, or client properties

In the NetBackup Administration Console, expand NetBackup Management > Host Properties.

2 3

Select Master Server, Media Server, or Clients. In the right pane, double-click the server or client to view the properties.

Changing the host properties on multiple hosts at the same time

You can select more than one host and change multiple hosts at one time. Use the following procedure to change properties on multiple hosts at the same time. To simultaneously change the properties on multiple hosts

1 2 3 4

In the NetBackup Administration Console, expand NetBackup Management > Host Properties. Select Master Server, Media Server, or Clients. In the right pane, select a host. Hold down the Shift key and select another host. With multiple hosts still selected, click Actions > Properties. The properties dialog box displays the names of the selected hosts that are affected by subsequent host property changes.

Configuring Host Properties About the NetBackup Host Properties

61

Number of hosts selected

The following information about each selected host appears:

Server or client name Operating system Type of computer in the configuration Identifier IP address

5 6

Make changes as necessary. Click OK to save the changes for all hosts and to close the dialog box.

Property states for multiple hosts

The Host Properties dialog boxes use the following conventions regarding multiple host selections:
Title of dialog box If a dialog box contains a Selected Host (or similarly named) box, all controls reflect the values for the host currently selected in the Selected Host box. If a dialog box does not contain a Selected Host (or similarly named) box, settings of all the selected hosts are combined to arrive at a value that is displayed to the user. Option selection When multiple hosts are selected, no options appear selected. Selecting any option updates the setting on all selected hosts. To leave each host configured independently, do not select any option while multiple hosts are selected. When multiple hosts are selected, number spinners appear blank. Selecting any value updates the setting on all selected hosts. To leave each host configured independently, do not select any option while multiple hosts are selected.

Number spinners

62

Configuring Host Properties About the NetBackup Host Properties

Check box states

The host property check boxes may appear in one of the following states: Selected (checked) if the attribute has been set the same for all selected hosts. To set the property on all selected hosts, select the check box. Clear (unchecked) if the property has been set the same for all selected hosts. To clear the property on all selected hosts, clear the check box. Gray check if the property is set differently on the selected hosts. To leave the property unchanged, set the box to a gray check.

Edit field states

If the property contains a text field for specifying a value, the field may be in one of the following states: The field may contain a value if the property has the same value for all selected hosts. The field may be empty or indicate <<Multiple Entries>> if the property was not set the same for all selected hosts. When the cursor is moved to such a field, a small notice appears at the bottom of the dialog box noting that the value is different on the selected hosts.

Note: In a clustered environment, host properties must be made on each node of the cluster separately. If the selected hosts are of various operating systems, none of the operating system-specific information appears. For example, select a Linux client and a Windows 2008 client. Neither the Windows Client properties nor the UNIX Client properties appear in the Host Properties. If all the selected hosts are of the same operating system, the corresponding properties node appears. If the property contains a text field for specifying a value, choose from the following options:

To set the property to the same value for all selected hosts, check the associated option and type the value in the field. To leave the property unchanged, uncheck the associated option. The field changes to gray.

Exporting host properties

Use the following procedure to export the properties of a host.

Configuring Host Properties Access Control properties

63

To export the properties of a host

1 2 3 4

In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers, Media Servers, or Clients. Select a host. If you want to select multiple hosts, hold down the Shift key and select another host. Click File > Export. In the Export Data dialog box, enter the full path name or browse to the directory and click Save.

Standard host property dialog box options

The following options are available in every host property dialog box.
Default Click Default to set all the properties in the current dialog box to the default values. Click OK to apply all changes since Apply was last clicked. OK also closes the dialog box. Click Cancel to cancel the changes that were made since the last time changes were applied. Click Apply to save changes to all of the properties for the selected host(s). However, to apply changes click OK. Help Click Help for information on the properties that appear in the current dialog box.

OK

Cancel

Apply

Access Control properties

Use the Access Control host properties in the NetBackup Administration Console to configure NetBackup Authentication and Authorization. The properties apply to currently selected master servers, media servers, and clients. The following tabs may display:

Authentication Domain tab See Authentication Domain tab on page 64. Authorization Service tab See Authorization Service tab on page 66. Network Attributes

64

Configuring Host Properties Access Control properties

See Network Attributes tab on page 67. The tabs that display depend on whether the host that is selected is a master server, a media server, or a client. The NetBackup Product Authentication and Authorization property displays, regardless of which tab is selected. It determines whether the local system uses access control and how the system uses it. The NetBackup Product Authentication and Authorization property contains the following options. Table 3-3 NetBackup Product Authentication and Authorization property options

Option
Required

Description
Specifies that the local system should accept requests only from the remote systems that use NetBackup authentication and authorization. Connections from the remote systems that do not use NetBackup authentication and authorization are rejected. Select Required if all systems are at NetBackup 5.0 or later and maximum security is required. Specifies that the local system should reject connections from any remote system that uses NetBackup authentication and authorization. Select Prohibited if the network is closed and maximum performance is required. Specifies that the local system should negotiate with the remote system about whether to use NetBackup authentication and authorization. Select Automatic if the network contains mixed versions of NetBackup.

Prohibited

Automatic

For more information about controlling access to NetBackup, see the NetBackup Security and Encryption Guide.

Authentication Domain tab

The Authentication Domain tab contains the properties that determine which authentication broker a computer uses. A master server that uses NetBackup authentication and authorization must have at least one authentication domain entry.

Configuring Host Properties Access Control properties

65

Figure 3-2

Authentication Domain tab

If a media server or client does not define an authentication domain, it uses the authentication domains of its master server. The Authentication Domain tab on the Access Control dialog box contains the following properties. Table 3-4 Property
Available Brokers

Authentication Domain tab properties Description

Select a broker, then click Find to list all of the available authentication domains. List of available authentication domains. Select the authentication domain(s) that this host can use and click Add. List of the authentication domains selected for the host to use. Select the authentication domain(s) that you no longer want to use and click Remove.

Available Authentication Domains list Add button

Selected Authentication Domains list

Remove button

66

Configuring Host Properties Access Control properties

Authorization Service tab

The Authorization Service tab refers to the authorization service that the local NetBackup server uses. The Authorization Service tab does not appear as a property for clients. Figure 3-3 Authorization Service tab

The Authorization Service tab contains the following properties, which you can configure for a master or a media server. Table 3-5 Option
Host name Customize the port number of the authorization service

Authorization Service property options Description

Specifies the host name or IP address of the authorization service. Specifies a nonstandard port number. Select Customize the port number and enter the port number of the authorization service.

Note: Define a host to perform authorization if you configure this tab for a media server to use access control.

Configuring Host Properties Access Control properties

67

Network Attributes tab

The Network Attributes tab contains a list of networks that are allowed (or not allowed) to use NetBackup authentication and authorization with the local system. Figure 3-4 Network Attributes tab

The Network Attributes tab on the Access Control dialog box contains the following properties:
Networks The Networks property indicates whether specific networks can or cannot use NetBackup authentication and authorization with the local system. The names on the list are relevant only if the NetBackup Product Authentication and Authorization property in the Access Control dialog box is set to Automatic or Required. Symantec recommends setting the master server NetBackup Product Authentication and Authorization property to Automatic until the clients are configured for access control. Then, change the NetBackup Product Authentication and Authorization property on the master server to Required. If a media server or client does not define a NetBackup Authentication and Authorization network, it uses the networks of its master server. Click Add to add a network to the Network list. Click Add to All to add a network to all currently selected hosts in the Network list. Select a network name and click Remove to remove a network from the Network list.

68

Configuring Host Properties Access Control properties

NetBackup Product Authentication and Authorization property

The NetBackup Product Authentication and Authorization property in this tab determines whether the selected network uses access control and how the network uses it. See Access Control properties on page 63.

Add Network dialog box

The Add Network dialog box contains the following properties. Table 3-6 Property
Host/ Domain Host Details

Add Network dialog box properties

Description
Indicates whether the network to be added is a Host name or a Domain name. Specifies that if the network is a host, one of the following items must be entered:

The host name of the remote system. (host.domain.com) The IP address of the remote system. (10.0.0.29)

Domain Details

Domain Name/IP Enter a dot followed by the Internet domain name of the remote systems. (.domain) or the network of the remote system, followed by a dot. (10.0.0.) If the domain is specified by IP, select one of the following items: Bit count Indicates that the mask is based on bit count. Select from between 1 and 32. For example: Mask 192.168.10.10/16 has the same meaning as subnet mask 192.168.20.20:255:255:0.0

Subnet mask Select to enter a subnet mask in the same format as the IP address.

Configuring Host Properties Active Directory host properties

69

Figure 3-5

Add Network dialog box

Active Directory host properties

The Active Directory properties in the NetBackup Administration Console apply to the backup of currently selected Windows Server 2008 clients. The Active Directory properties determine how the backups that allow Active Directory granular restores are performed. See Creating a policy that allows Active Directory granular restores on page 676.

70

Configuring Host Properties Active Directory host properties

Figure 3-6

Active Directory dialog box

The Active Directory dialog box contains the following properties. Table 3-7 Property Active Directory dialog box properties Description

Perform consistency check before backup Checks snapshots for data corruption. Applies only to snapshots when using Microsoft Volume Shadow Copy that the Microsoft Volume Shadow Copy Services (VSS) performs. Service snapshot provider If corrupt data is found and this option is not selected, the job fails. See Windows Open File Backup tab of the Client Attributes properties on page 89. Continue with backup if consistency check fails Continues the backup job even if the consistency check fails. It may be preferable for the job to continue, even if the consistency check fails. For example, a backup of the database in its current state may be better than no backup at all. Or, it may be preferable for the backup of a large database to continue if it encounters only a small problem.

Configuring Host Properties Backup Exec Tape Reader properties

71

Backup Exec Tape Reader properties

The Backup Exec Tape Reader properties in the NetBackup Administration Console let NetBackup read the media that Backup Exec writes. Media is read by using a two-phase import process. The Backup Exec Tape Reader properties apply to currently selected master servers. Note: The Backup Exec Tape Reader functionality will not be supported in the next major NetBackup release. Figure 3-7 Backup Exec Reader dialog box

The Backup Exec Tape Reader dialog box contains the following properties.

72

Configuring Host Properties Backup Exec Tape Reader properties

Table 3-8 Property

GRFS advertised name

Backup Exec Tape Reader dialog box properties

Description
Specifies the name that the Backup Exec UNIX agent uses to identify itself to the Backup Exec server. The advertised name may not be the same as the real computer name and path. To set the correct client name and paths in Backup Exec UNIX images .f file paths, map the master server between the GRFS advertised name (generic file system name) and the actual client name and path. The GRFS advertised name uses the following format: ADVERTISED_HOST_NAME/advertised_path where ADVERTISED_HOST_NAME is the advertised host name and advertised_path is the advertised path. Enter the ADVERTISED_HOST_NAME in capital letters. A Backup Exec service maps the advertised name to the actual computer name and path, and then backs up the advertised name and path. When NetBackup imports Backup Exec UNIX backups, the mapping service is not present; therefore the names and paths must be indicated. If the host properties do not list any entries, NetBackup assumes that the advertised name is the same as the real computer name. NetBackup assumes that the advertised path is the same as the real path.

Actual client name

Maps the advertised name to the real computer name. If the host properties do not list any entries, NetBackup assumes that the advertised name is the same as the real computer name. NetBackup assumes that the advertised path is the same as the real path.

Actual path

Maps the advertised path to the real path. If the host properties do not list any entries, NetBackup assumes that the advertised name is the same as the real computer name. NetBackup assumes that the advertised path is the same as the real path.

Add Change

Adds a GRFS entry. In the Backup Exec Tape Reader properties, click Add. Changes a selected GRFS entry. Select an entry in the Backup Exec Tape Reader properties list and click Change. Removes a GRFS entry. Select an entry in the Backup Exec Tape Reader properties list and click Remove.

Remove

See About importing backup images on page 789.

Configuring Host Properties Bandwidth properties

73

Bandwidth properties
Use the Bandwidth properties to specify network bandwidth limits for the NetBackup clients of the selected server. Note: The Bandwidth properties apply only to IPv4 networks. Use the Throttle Bandwidth properties to limit IPv6 networks. See Throttle Bandwidth properties on page 210. The actual limiting occurs on the client side of the backup connection. The bandwidth limits only restrict bandwidth during backups. By default, the bandwidth is not limited. The Bandwidth properties apply to currently selected master servers. Figure 3-8 Bandwidth dialog box

To manage entries in the Bandwidth dialog box, select one of the following buttons.
Add Change Adds an entry to the bandwidth table for each of the selected clients. Changes an entry to the bandwidth table for each of the selected clients. Removes the selected entry from the bandwidth table.

Remove

74

Configuring Host Properties Bandwidth properties

When a backup starts, NetBackup reads the bandwidth limit configuration as configured in the Bandwidth host properties. NetBackup then determines the appropriate bandwidth value and passes it to the client. NetBackup computes the bandwidth for each new job based on the number of jobs that are currently running for the IP range. The bandwidth value that is assigned to the job at start time remains the same until the job is completed.NetBackup does not include local backups in its calculations. The NetBackup client software enforces the bandwidth limit. Before a buffer is written to the network, client software calculates the current value for kilobytes per second and adjusts its transfer rate if necessary.

Bandwidth limit usage considerations and restrictions

Some usage restrictions apply to the bandwidth limit settings in the Bandwidth dialog box. The following table lists the restrictions and describes specific behaviors that you may need to consider. Table 3-9 Bandwidth limit usage considerations and restrictions Bandwidth limit behavior or restrictions

Client or operation

NetBackup for Microsoft SQL-Server clients Bandwidth limits are not supported NetBackup for Oracle clients NetBackup for DataTools SQL-BackTrack clients local backups Bandwidth limits are not supported Bandwidth limits are not supported

If a server is also a client and data does not go over the network, bandwidth limits have no effect on local backups. Bandwidth limits restrict maximum network usage and do not imply required bandwidth. For example, if you set the bandwidth limit for a client to 500 kilobytes per second, the client can use up to that limit. It does not mean, however, that the client requires 500 kilobytes per second.

Setting required bandwidth

Distributing the workload of active backups You cannot use bandwidth limits to distribute the backup workload of active backups by having NetBackup pick the most available network segment. NetBackup does not pick the next client to run based on any configured bandwidth limits.

Configuring Host Properties Busy File Settings properties

75

Add Bandwidth Settings dialog box for Bandwidth properties

The Add Bandwidth Settings and the Change Bandwidth Settings dialog boxes contain the following properties.
Bandwidth (KB/Sec) Specifies the bandwidth limitation in kilobytes per second. A value of 0 disables the limits for an individual client or the range of IP addresses covered by the entry. For example, a value of 200 indicates 200 kilobytes per second.

Busy File Settings properties

The Busy File Settings properties in the NetBackup Administration Console apply to currently selected UNIX clients. The Busy File Settings properties define what occurs when NetBackup encounters a busy file during a backup of a UNIX client. Figure 3-9 Busy File Settings dialog box

The Busy File Settings dialog box contains the following properties.

76

Configuring Host Properties Busy File Settings properties

Table 3-10 Property

Working directory

Busy File Settings dialog box properties

Description
Specifies the path to the busy-files working directory. On a UNIX client, the value in the users $HOME/bp.conf file takes precedence if it exists. By default, NetBackup creates the busy_files directory in the /usr/openv/netbackup directory. Specifies the recipient of the busy-file notification message when the action is set to Send email. By default, the mail recipient is the administrator. On a UNIX client, the value in the users $HOME/bp.conf file takes precedence if it exists. By default, BUSY_FILE_NOTIFY_USER is not in any bp.conf file and the mail recipient is root. Enables busy files to be processed according to the host property settings. NetBackup follows the Busy File Settings if it determines that a file is changing during a backup. By default, Process busy files is not enabled and NetBackup does not process the busy files. Specifies the absolute path and file name of the busy file. The metacharacters *, ?, [], [ ] can be used for pattern matching of file names or parts of file names. Adds a new file entry. Enter the file and path directly, or browse to select a file. Adds a new file entry for all of the clients currently selected. Enter the file and path directly, or browse to select a file. Removes the selected file from the file action list. The following options specify which action to take when busy-file processing is enabled. On a UNIX client, the value in the users $HOME/bp.conf file takes precedence if it exists. Send email sends a busy sends a busy file notification message to the user that is specified in Operators email address. Retry the backup retries the backup on the specified busy file. The Retry count value determines the number of times NetBackup tries a backup. Ignore excludes the busy file from busy file processing. The file is backed up, then a log entry that indicates it was busy appears in the All Log Entries report.

Operator's email address

Process busy files

File action file list

Add Add to All

Remove Busy file action

Retry count

Specifies the number of times to try the backup. The default retry count is 1.

Activating the Busy File Settings in host properties

To activate the settings in the Busy File Settings host properties, use the following procedure.

Configuring Host Properties Clean-up properties

77

To activate Busy File Settings

Copy the bpend_notify_busy script:

/usr/openv/netbackup/bin/goodies/bpend_notify_busy

to the path:
/usr/openv/netbackup/bin/bpend_notify

2 3

Set the file access permissions to allow group and others to run bpend_notify. Configure a policy with a user backup schedule for the busy file backups. This policy services the backup requests that the repeat option in the actions file generates. The policy name is significant. By default, NetBackup alphabetically searches (uppercase characters first) for the first available policy with a user backup schedule and an open backup window. For example, a policy name of AAA_busy_files is selected ahead of B_policy.

Clean-up properties
The Clean-up properties in the NetBackup Administration Console refer to the retention of various logs and incomplete jobs. The Clean-up properties apply to currently selected master servers.

78

Configuring Host Properties Clean-up properties

Figure 3-10

Clean-up dialog box

The Clean-up dialog box contains the following properties. Table 3-11 Property
Keep logs

Clean-up dialog box properties Description

Specifies how many days you want to keep the logs in case you need the logs to evaluate failures. For example, if you check the backups every day, you can delete the logs sooner than if you check the backups once a month. However, the logs can consume a large amount of disk space, so do not keep the logs any longer than necessary. The default is 28 days. Specifies the length of time, in days, that the master server keeps its error catalog, job catalog, and debug log information. NetBackup derives the Backup Status, Problems, All Log Entries, and Media Log reports from the error catalog. Also limits the time period that these reports can cover. When this time expires, NetBackup also deletes these logs (that exist) on UNIX media servers and UNIX clients.

Configuring Host Properties Clean-up properties

79

Table 3-11 Property

Keep vault logs

Clean-up dialog box properties (continued) Description

If Vault is installed, the Keep vault logs option is enabled. It specifies the amount of time that the Vault session directories are kept. Session directories are found in the following location: install_path\netbackup\vault\sessions\vaultname\ session_x where x is the session number. This directory contains vault log files, temporary working files, and report files.

Image cleanup

Specifies the maximum interval that can elapse before an image cleanup is run. Image cleanup is run after every successful backup session (that is, a session in which at least one backup runs successfully). If a backup session exceeds this maximum interval, an image cleanup is initiated. Specifies the minimum interval that can elapse before an image cleanup is run. Image cleanup is not run after a successful backup session until this minimum interval has elapsed since the previous image cleanup. Specifies the number of days to keep true image restore information on disk. After the specified number of days, the images are pruned (removed). Applies to all policies for which NetBackup collects true image restore information. The default is one day. When NetBackup performs a true image backup, it stores the following images on the backup media:

Catalog cleanup wait time

Keep true image restoration information

Backed up files True image restore information

NetBackup also stores the true image restore information on disk in the install_path\NetBackup\db\images directory. NetBackup retains the information for the number of days that this property specifies. Keeping the information on disk speeds up restores. If a user requests a true image restore after the information was deleted from disk, NetBackup retrieves the required information from the media. The only noticeable difference to the user is a slight increase in total restore time. NetBackup deletes the additional information from disk again after one day.

80

Configuring Host Properties Client Name properties

Table 3-11 Property

Move restore job from incomplete state to done state

Clean-up dialog box properties (continued) Description

Indicates the number of days that a failed restore job can remain in an Incomplete state. After that time, the Activity Monitor shows the job as Done. The default is 7 days. The maximum setting is 365 days. If Checkpoint Restart for restores is used, the Restore retries property allows a failed restore job to be retried automatically. See Universal Settings properties on page 214. See Checkpoint restart for restore jobs on page 542.

Move backup job from incomplete state to done state

Indicates the maximum number of hours that a failed backup job can remain in an incomplete state. After that time, the Activity Monitor shows the job as Done. The minimum setting is one hour. The maximum setting is 72 hours. The default is three hours. When an active job has an error, the job goes into an Incomplete state. In the Incomplete state, the administrator can correct the condition that caused the error. If an Incomplete job does not complete successfully and is moved to the Done state, the job retains the error status.

Note: A resumed job reuses the same job ID, but a restarted job receives a
new job ID. The job details indicate that the job was resumed or restarted.

Note: This property does not apply to suspended jobs. Suspended jobs must
be resumed manually before the retention period of the job is met and the image expires. If a suspended job is resumed after the retention period is met, the job fails and is moved to the Done state.

Client Name properties

The Client name property in the NetBackup Administration Console specifies the NetBackup client name for the selected client. The name must match the name the policy uses to back up the client. The only exception is for a redirected restore, where the name must match that of the client whose files are to be restored. The client name is initially set during installation. The name that is entered here must also match the client name in the Client Attributes dialog box for the master server. If it does not match, the client cannot browse for its own backups. Note: Using an IPv6 address as a client name in a policy can cause backups to fail. Specify a hostname instead of an IPv6 address.

Configuring Host Properties Client Attributes properties

81

See Client Attributes properties on page 81. Figure 3-11 Client Name dialog box

If the value is not specified, NetBackup uses the name that is set in the following locations:

For a Windows client In the Network application from the Control Panel. For a UNIX client The name that is set by using the hostname command. The name can also be added to a $HOME/bp.conf file on a UNIX client. However, the name is normally added in this manner only for redirected restores. The value in the $HOME/bp.conf file takes precedence if it exists.

Client Attributes properties

In the NetBackup Administration Console, the Client Attributes properties apply to the clients of currently selected master servers. The Global client attributes property applies to all clients, unless overridden as described in the following table.

82

Configuring Host Properties Client Attributes properties

Table 3-12 Attribute

Allow client browse

Global client attributes group box Description

Allows all clients to browse files for restoring. This attribute is overridden if the Browse and restore ability option on the General tab is set to Deny both for a particular client(s). Allows all clients to restore files. This attribute is overridden if the Browse and restore ability option on the General tab is set to Allow browse only or Deny both. Specifies the list of clients in the client database on the currently selected master server(s). A client must be in the client database before you can change the client properties in the Client Attributes dialog box. The client database consists of directories and files in the following directory: If a client is not listed in the Clients list, click Add to add clients. To remove a client from the Clients list, select the client, then click Remove. If a client is not listed in the Clients list, click Add to display the Add Client dialog box and add a client to the client database. Type a client name in the text box or click the browse button (...) and select a client. See Add Client dialog box on page 83. The name that is entered here must match the Client Name property for the specific client. If it does not, the client cannot browse its own backups. See Client Name properties on page 80. Use the bpclient command to add clients to the client database if dynamic addressing (DHCP) is in use. Additional information about dynamic host names and IP addressing is available in the NetBackup Administrators Guide, Volume II.

Allow client restore

Clients

General tab

Specifies how to configure the selected Windows master servers (clients). See General tab of the Client Attributes properties on page 83.

Connect Options tab

Specifies how to configure the connection between a NetBackup server and a NetBackup client. See Connect Options tab of the Client Attributes properties on page 87.

Windows Open File Backup tab

Specifies whether a client uses Windows Open File Backup. Also, specifies whether Volume Snapshot Provider or Volume Shadow Copy Service is used as the snapshot provider. See Windows Open File Backup tab of the Client Attributes properties on page 89.

Configuring Host Properties Client Attributes properties

83

Add Client dialog box

To add a client to the database, enter the name of a client, or browse to find a client. The Add Client dialog box contains the following properties.
Enter client name Specifies the name of the client to be added to the database. Type the name of the client to add. Finds the list of current clients and displays them in the Browse for computer window. Select the client to add to the database and click Add. Adds the specified client to the client database (client name displays in the Clients window). Closes the Add Client dialog box. Displays more information about how to add a client.

... (browse)

Add

Close Help

General tab of the Client Attributes properties

The properties on the General tab apply to selected Windows master servers. The tab appears on the Client Attributes dialog box. Figure 3-12 General tab of Client Attributes dialog box

84

Configuring Host Properties Client Attributes properties

The General tab contains the following properties. Table 3-13 Property
Offline Until:

General tab properties Description

Makes the specified clients in the General tab unavailable for backups. By default, clients are online and included in the policies in which they are listed. When Offline Until: is selected for a client, no jobs are scheduled for that client. Since the client is not part of any job, no backup status will be listed for the client. After enabling the Offline Until: option, indicate the date and time when the clients are to be online again. The default setting is infinity, or approximately January 18, 2038, depending on the locale setting. See Retention Periods with end dates beyond 2038, excluding Infinity on page 202.

Note: Changes to this property do not appear in the audit report.

See About NetBackup auditing on page 873. The ability to take clients offline is useful in a number of situations. See Offline option usage considerations and restrictions on page 85. Maximum data streams Specifies the maximum number of jobs that are allowed at one time for each selected client. (This value applies to the number of jobs on the client, even if multistreaming is not used.) To change the setting, select Maximum data streams. Then scroll to or enter a value up to 99. The Maximum data streams property interacts with Maximum jobs per client and Limit jobs per policy as follows: If the Maximum data streams property is not set, the limit is either the one indicated by the Maximum jobs per client property or the Limit jobs per policy property, whichever is lower. If the Maximum data streams property is set, NetBackup ignores the Maximum jobs per client property. NetBackup uses either Maximum data streams or Limit jobs per policy, whichever is lower. See Global Attributes properties on page 138. See Limit jobs per policy (policy attribute) on page 544.

Configuring Host Properties Client Attributes properties

85

Table 3-13 Property

Browse and restore ability

General tab properties (continued) Description

Specifies the client permissions to list and restore backups and archives. Select the client(s) in the General tab of the Client Attributes dialog box and choose a Browse and restore ability property. To use the Global client attributes settings, select Use global settings. To allow users on the selected clients to both browse and restore, select Allow both. To allow users on the selected clients to browse but not restore, select Allow browse only. To prevent users on the selected clients from the ability to browse or restore, select Deny both.

Free browse

This property applies to the privileges that are allowed to a non-Windows administrator who is logged into the client. This property also applies to the users that do not have backup and restore privileges. Specifies whether the clients can list and restore from scheduled backups. (This setting does not affect user backups and archives.) Windows administrators can list and restore from scheduled backups as well as user backups regardless of the Free browse setting.

Deduplication

Specifies the deduplication action for clients if you use one of the following NetBackup deduplication options:

NetBackup Deduplication Option PureDisk Deduplication Option

For a description of the client direct deduplication options and their actions: See Where deduplication should occur on page 86.

Offline option usage considerations and restrictions

The ability to take clients offline is useful in a number of situations. For example, in the event of planned outages or maintenance, client systems can be taken offline to avoid the unnecessary errors that administrators would then need to investigate. This option can also be used to anticipate new clients in the system; listing them in policies but configuring them as offline until they are in place and ready to be used. The following actions can be performed if a client is offline.

86

Configuring Host Properties Client Attributes properties

Table 3-14 Type of job or operation

Offline option actions Action or restriction

Offline clients continue to be included in any job. Job retries continue as normal.

A client is offline and the job is already in progress A client is offline and job retries were started before the client was taken offline Any duplication job that is associated with a storage lifecycle policy and an offline client LiveUpdate jobs for offline clients Restore jobs

Continues to run until complete.

Continues to run until complete. Can be run for offline clients.

The user attempts a manual backup for an offline client The backup fails with a status code 1000, Client is offline. The user can either wait until the client is brought online again or bring the client online manually. Use either the NetBackup Administration Console or the bpclient command to do so before resubmitting the manual job. Archive backups Administrators restarting or resuming jobs Not allowed for offline clients. Not allowed for offline clients.

Caution: If the master server is offline, hot catalog backups cannot run.

Where deduplication should occur

The Deduplication property specifies the deduplication action for clients if you use either the NetBackup Deduplication Option or the PureDisk Deduplication Option. The following table describes the client direct deduplication options. Table 3-15 Option
Always use the media server (the default)

Client direct deduplication options Description

Always deduplicates the data on the media server. The default. Jobs fail if one of the following are true: The NetBackup Deduplication Engine on the deduplication storage server is inactive. The PureDisk storage pool is inactive.

Configuring Host Properties Client Attributes properties

87

Table 3-15 Option

Client direct deduplication options (continued) Description

Prefer to use client-side deduplication Deduplicates data on the client and then send it directly to the storage server. NetBackup first determines if the client direct library on the storage server is active. If it is active, the client deduplicates the backup data and sends it directly to the storage server, bypassing media server processing. If it is not active, the client sends the backup data to a deduplication media server. The deduplication media server deduplicates the data. Always use client-side deduplication Always deduplicates the backup data on the client and then send it directly to the storage server. If a job fails, NetBackup does not retry the job.

You can override the Prefer to use client-side deduplication or Always use client-side deduplication host property in the backup policies. See Disable client-side deduplication (policy attribute) on page 564. More information about client deduplication is available. See the NetBackup Deduplication Guide.

Connect Options tab of the Client Attributes properties

The properties in the Connect Options tab describe how a NetBackup server connects to NetBackup client tabs. The tab appears on the Client Attributes dialog box.

88

Configuring Host Properties Client Attributes properties

Figure 3-13

Connect Options tab of Client Attributes dialog box

The Connect Options tab contains the following options. Table 3-16 Property
BPCD connect back

Connect Options tab properties

Description
Specifies how daemons are to connect back to the NetBackup Client daemon (BPCD) and contains the following options: Use default connect options Uses the value that is defined in the Firewall host properties of the clients NetBackup server. See Firewall properties on page 131. Random port NetBackup randomly chooses a free port in the allowed range to perform the legacy connect-back method. VNETD port NetBackup uses the vnetd port number for the connect-back method.

Configuring Host Properties Client Attributes properties

89

Table 3-16 Property

Ports

Connect Options tab properties (continued)

Description
Specifies the method that the selected clients should use to connect to the server and contains the following options: Use default connect options Uses the value that is defined in the Firewall host properties of the clients NetBackup server. See Firewall properties on page 131. Reserved port Uses a reserved port number. Non-reserved port Uses a non-reserved port number.

Daemon connection port

Specifies the method that the selected clients should use to connect to the server and contains the following options. Use default connect options Uses the value that is defined in the Firewall host properties of the clients NetBackup server. Automatic Connects to the daemons on the server using vnetd if possible. If the daemons cannot use vnetd, the connection is made by using the daemons legacy port number. VNETD only Connects to the daemons on the server by using only vnetd. If the firewall rules prevent a server connection using the legacy port number, check this option. When selected, the BPCD connect back setting is not applicable. In addition, the Ports setting uses Non-reserved port, regardless of the value selected. Daemon port only Connects to the daemons on the server by using only the legacy port number. This option only affects connections to NetBackup 7.0 and earlier. For connections to NetBackup 7.0.1 and later, the veritas_pbx port is used.

See Resilient Network properties on page 190.

Windows Open File Backup tab of the Client Attributes properties

The Windows Open File Backup properties in the NetBackup Administration Console specify whether a client uses Windows Open File Backup. The properties also specify whether Volume Snapshot Provider or Volume Shadow Copy Service is used as the snapshot provider.

90

Configuring Host Properties Client Attributes properties

Snapshots are a point-in-time view of a source volume. NetBackup uses snapshots to access busy or active files during a backup job. Without a snapshot provider, active files are not accessible for backup. Figure 3-14 Windows Open File Backup tab of Client Attributes dialog box

The Windows Open File Backup tab contains the following options. Table 3-17 Property
Add

Windows Open File Backup tab properties

Description
Adds the NetBackup clients only if you want to change the default settings on the Windows Open File Backup tab. By default, no clients are listed in the Client Attributes dialog box. The server uses the following Windows Open File Backup defaults for all Windows clients:

Windows Open File Backup is enabled on the client.

Microsoft Volume Shadow Copy Service (VSS) is used for NetBackup 7.0 clients. See Back-level and upgraded clients that use Windows Open File Backup on page 93. Snapshots are taken of individual drives (Individual drive snapshot) as opposed to all drives at once (Global drive snapshot). Upon error, the snapshot is terminated (Abort backup on error). Remove Deletes a client from the list by selecting the client and then clicking Delete.

Configuring Host Properties Client Attributes properties

91

Table 3-17 Property Description

Windows Open File Backup tab properties (continued)

Enable Windows Open Specifies that Windows Open File Backups be used for the selected clients. Adds the clients File Backups to the list only if you want to change the default property settings. For Microsoft Distributed File System Replication (DFSR) servers, select Enable Windows Open File Backups. The Snapshot Provider must be Volume Shadow Copy Service. See About Microsoft DSFR backups on page 521. This option functions independently from the Perform Snapshot backups policy option that is available when the Snapshot Client is licensed. If a client is included in a policy that has the Perform Snapshot backups policy option disabled and you do not want snapshots, the Enable Windows Open File Backups for this client property must be disabled as well for the client. If both options are not disabled, a snapshot is created, though that may not be the intention of the administrator. For more information, see the NetBackup Snapshot Client Administrators Guide. Snapshot Provider Selects the snapshot provider for the selected clients: Use Veritas Volume Snapshot Provider (VSP) This option specifies that Veritas VSP be used as the snapshot provider. VSP is required for Windows 2000 clients and can also be used on 6.x Windows 2003 clients. Use Microsoft Volume Shadow Copy Service (VSS) This option specifies that Microsoft VSS be used to create volume snapshots of volumes and logical drives for the selected clients. In 7.0, Microsoft VSS should be selected for all Windows clients, as VSP is not available. VSS is available for all supported Windows clients, XP SP2 and later. Configure VSS through the Microsoft VSS configuration dialog boxes. For information about how to do Active Directory granular restores when using VSS, see the following topic: See Active Directory host properties on page 69. For Microsoft Distributed File System Replication (DFSR) servers, select Use Microsoft Volume Shadow Copy Service (VSS). See About Microsoft DSFR backups on page 521.

92

Configuring Host Properties Client Attributes properties

Table 3-17 Property

Snapshot usage

Windows Open File Backup tab properties (continued)

Description
Selects how snapshots are made for the selected clients:

Individual drive snapshot Specifies that the snapshot should be of an individual drive (default). When this property is enabled, snapshot creation and file backup are done sequentially on a per volume basis. For example, assume that drives C and D are to be backed up.

If the Individual drive snapshot property is selected, NetBackup takes a snapshot of drive C, backs it up, and discards the snapshot. It then takes a snapshot of drive D, backs it up, and discards the snapshot. Volume snapshots are enabled on only one drive at a time, depending on which drive is to be backed up. This mode is useful when relationships do not have to be maintained between files on the different drives. Use this configuration if snapshot creation fails when all volumes for the backup are snapshot at once when the Global drive snapshot property is enabled. Individual drive snapshot is enabled by default for all non-multistreamed backups by using the Windows Open File Backup option. Global drive snapshot Specifies that the snapshot is of a global drive. All the volumes that require snapshots for the backup job (or stream group for multistreamed backups) are taken at one time. For example, assume that drives C and D are to be backed up. In this situation, NetBackup takes a snapshot of C and D. Then NetBackup backs up Cand backs up D. NetBackup then discards the C and D snapshots. This property maintains file consistency between files in different volumes. The backup uses the same snapshot that is taken at a point in time for all volumes in the backup.

Note: The Individual drive snapshot property and the Global drive snapshot property
only apply to non-multistreamed backups that use Windows Open File Backup. All multistreamed backup jobs share the same volumes snapshots for the volumes in the multistreamed policy. The volume snapshots are taken in a global fashion.

Configuring Host Properties Client Attributes properties

93

Table 3-17 Property Description

Windows Open File Backup tab properties (continued)

Snapshot error control Selects the processing instructions that NetBackup should follow if it encounters an error during processing: Abort backup on error Specifies that a backup aborts if it fails for a snapshot-related issue after the snapshot is created and while the backup uses the snapshot to back up open or active files on the file system. The most common reason for a problem after the snapshot is created and is in use by a backup, is that the cache storage is full. If the Abort backup on error property is checked (default), the backup job aborts with a snapshot error status if the backup detects a snapshot issue. This property does not apply to successful snapshot creation. The backup job continues regardless of whether a snapshot was successfully created for the backup job. The Abort backup on error property applies only to the snapshot errors that occur after the snapshot is successfully created and is in use by a backup job. Disable snapshot and continue Specifies that if the snapshot becomes invalid during a backup, the volume snapshots for the backup are destroyed. The backup continues with Windows open file backups disabled. Regarding the file that had a problem during a backupit may be that the file was not backed up by the backup job. The file may not be able to be restored.

Note: Volume snapshots typically become invalid during the course of a backup because
insufficient cache storage was allocated for the volume snapshot. Reconfigure the cache storage configuration of the Windows Open File Backup snapshot provider to a configuration that best suits your clients installation.

Back-level and upgraded clients that use Windows Open File Backup
The following table shows the expected Open File Backup behavior based on the client version and the Snapshot Provider setting. Table 3-18 Client version
6.x

Snapshot Provider behavior for clients in a 7.x environment Behavior

Veritas VSP is used for Open File Backup.

Snapshot Provider setting

Veritas VSP (6.5 default setting)

6.x 6.x

Veritas VSP Windows VSS

Veritas VSP is used for Open File Backup. Windows VSS is used for Open File Backup.

94

Configuring Host Properties Client Settings properties for NetWare clients

Table 3-18

Snapshot Provider behavior for clients in a 7.x environment (continued) Behavior

Using VSS for Open File Backup is a new default behavior in 7.x.

Client version
7.x

Snapshot Provider setting

Windows VSS (7.0 default setting)

7.x

Veritas VSP

Even if Veritas VSP is indicated, Windows VSS is used for Open File Backup. For upgraded clients: For 6.x clients that used VSP and have been upgraded to 7.0: VSP settings are ignored and VSS snapshots are automatically implemented. For 6.x VSS users: You no longer need to create a Client Attribute entry to enable VSS. VSS is the only snapshot provider available to the NetBackup 7.0 Windows client.

7.x

Windows VSS

Windows VSS is used for Open File Backup.

Client Settings properties for NetWare clients

The Client Settings properties apply to currently selected NetWare clients. The Client Settings properties dialog box for NetWare clients includes the following options. Table 3-19 Option
Back up migrated files

NetWare Client Settings properties

Description
Specifies that the files in secondary storage be moved back to primary storage and backed up. If the property is not selected, only the metadata for the file is backed up and the file is not moved back to primary storage. The metadata is the information still in the primary storage that marks where the file would be. Metadata includes any information that is needed to retrieve the file from secondary storage. The property specifies that compressed files are uncompressed before backing up. Uncompression is useful if the file is restored to a version of NetWare that does not support compression. If the option is not selected (default), the file is backed up in its compressed state.

Uncompress files before backing up

Configuring Host Properties Client Settings (UNIX) properties

95

Table 3-19 Option

Keep status of user-directed backups, archives, and restores

NetWare Client Settings properties (continued)

Description
Specifies how long the system keeps progress reports before it automatically deletes the reports. The default is three days.

Client Settings (UNIX) properties

The UNIX Client Settings properties in the NetBackup Administration Console apply to currently selected UNIX clients. Figure 3-15 Client Settings (UNIX) dialog box

The UNIX Client Settings dialog box contains the following properties.

96

Configuring Host Properties Client Settings (UNIX) properties

Table 3-20 Property

Locked file action

UNIX Client Settings dialog box properties Description

Determines what happens when NetBackup tries to back up a file with mandatory file locking enabled in its file mode. Select one of the following options: Wait By default, NetBackup waits for files to become unlocked. If the wait exceeds the Client read timeout host property that is configured on the master server, the backup fails with a status 41. See Timeouts properties on page 212. Skip NetBackup skips the files that currently have mandatory locking set by another process. A message is logged if it was necessary to skip a file.

Keep status of user-directed backups, archives, and restores

Specifies the number of days to keep progress reports before the reports are deleted. The default is three days. The minimum is 0. The maximum is 9,999 days. Logs for user-directed operations are stored on the client system in the following directory: install_path\NetBackup\logs\user_ops\ loginID\logs

Reset file access time

Specifies that the access time (atime) time for a file displays the backup time. By default, NetBackup preserves the access time by resetting it to the value it had before the backup.

Note: This setting affects the software and the administration scripts that
examine a files access time. Megabytes of memory to use for file compression Specifies the amount of memory available on the client when files are compressed during backup. If you select compression, the client software uses this value to determine how much space to request for the compression tables. The more memory that is available to compress code, the greater the compression and the greater the percentage of machine resources that are used. If other processes also need memory, use a maximum value of half the actual physical memory on a machine to avoid excessive swapping. The default is 0. This default is reasonable; change it only if problems are encountered. Use VxFS file change log for incremental backups Determines if NetBackup uses the File Change Log on VxFS clients. The default is off. See VxFS file change log for incremental backups property on page 97.

Configuring Host Properties Client Settings (UNIX) properties

97

Table 3-20 Property

Default cache device path for snapshots

UNIX Client Settings dialog box properties (continued) Description

For additional information, see the NetBackup Snapshot Client Administrators Guide.

Do not compress files ending with Specifies a list of file extensions. During a backup, NetBackup does not list compress files with these extensions because the file may already be in a compressed format. Do not use wildcards to specify these extensions. For example, .A1 is allowed, but not .A* or .A[1-9] Files that are already compressed become slightly larger if compressed again. If compressed files with a unique file extension already exist on a UNIX client, exclude it from compression by adding it to this list. Add Adds file endings to the list of file endings that you do not want to compress. Click Add, then type the file extension in the File Endings dialog box. Use commas or spaces to separate file endings if more than one is added. Click Add to add the ending to the list, then click Close to close the dialog box. Adds a file extension that you do not want to compress, to the lists of all clients. To add the file extension to the lists of all clients, select it in the list on the Client Settings host property, then click Add to All. Removes a file extension from the list. To remove a name, either type it in the box or click the browse button (...) and select a file ending. Use commas or spaces to separate names.

Add to All

Remove

VxFS file change log for incremental backups property

The Use VxFS file change log for incremental backups property is supported on all platforms and versions where VxFS file systems support FCL. The following VxFS file systems support FCL:

Solaris SPARC platform running VxFS 4.1 or greater AIX running VxFS 5.0 or greater. HP 11.23 running VxFS 5.0 or greater. Linux running VxFS 4.1 or greater

The File Change Log (FCL) tracks changes to files and directories in a file system. Changes can include files created, links and unlinks, files renamed, data that is appended, data that is overwritten, data that is truncated, extended attribute modifications, holes punched, and file property updates.

98

Configuring Host Properties Client Settings (UNIX) properties

NetBackup can use the FCL to determine which files to select for incremental backups, which can potentially save unnecessary file system processing time. The FCL information that is stored on each client includes the backup type, the FCL offset, and the timestamp for each backup. The advantages of this property depend largely on the number of file system changes relative to the file system size. The performance impact of incremental backups ranges from many times faster or slower, depending on file system size and use patterns. For example, enable this property for a client on a very large file system that experiences relatively few changes. The incremental backups for the client may complete sooner since the policy needs to read only the FCL to determine what needs to be backed up on the client. If a file experiences many changes or multiple changes to many files, the time saving benefit may not be as great. See Backup Selections tab on page 631. The following items must be in place for the Use VxFS file change log for incremental backups property to work:

Enable the Use VxFS file change log for incremental backups property for every client that wants NetBackup to take advantage of the FCL. Enable the FCL on the VxFS client. See the Veritas File System Administrators Guide for information about how to enable the FCL on the VxFS client. Enable the Use VxFS file change log for incremental backups property on the client(s) in time for the first full backup. Subsequent incremental backups need this full backup to stay synchronized. Specify the VxFS mount point in the policy backup selections list in some manner:

By specifying ALL_LOCAL_DRIVES. By specifying the actual VxFS mount point. By specifying a directory at a higher level than the VxFS mount point, provided that Cross mount points is enabled. See Cross mount points (policy attribute) on page 550.

If the policy has Collect true image restore information or Collect true image restore information with move detection enabled, it ignores the Use VxFS file change log for incremental backups property on the client. The following table describes additional options that are available on the VxFS file change log feature.

Configuring Host Properties Client Settings properties for Windows clients

99

Table 3-21 Option

VxFS file change log feature options Description

Displays any messages that note when the file change log is used during a backup as follows: Using VxFS File Change Log for backup of pathname Also notes when full and incremental backups are not synchronized.

Activity Monitor messages

Keeping the data files synchronized with the FCL

The data files must be in sync with the FCL for this property to work. To keep the data files synchronized with the FCL, do not turn the FCL on the VxFS client off and on.

Note: If NetBackup encounters any errors as it processes

the FCL, it switches to the normal files system scan. If this switch occurs, it appears in the Activity Monitor. VxFS administration Additional VxFS commands are available to administrate the FCL in the Veritas File System Administrators Guide.

Client Settings properties for Windows clients

The Windows Client Settings properties apply to currently selected Windows clients.

100

Configuring Host Properties Client Settings properties for Windows clients

Figure 3-16

Windows Client Settings dialog box

The Client Settings dialog box for Windows clients contains the following properties. Table 3-22 Property
General level

Windows Client Settings properties

Description
Enables logs for bpinetd, bpbkar, tar, and nbwin. The higher the level, the more information is written. The default is 0. Enables logs for TCP. Scroll to one of the following available log levels:

TCP level

0 No extra logging (default) 1 Log basic TCP/IP functions 2 Log all TCP/IP functions, including all read and write requests 3 Log contents of each read or write buffer

Note: Setting the TCP level to 2 or 3 can cause the status reports to be very
large. It can also slow a backup or restore operation.

Configuring Host Properties Client Settings properties for Windows clients

101

Table 3-22 Property

Windows Client Settings properties (continued)

Description

Wait time before clearing archive Specifies how long the client waits before the archive bits for a differential bit incremental backup are cleared. The minimum allowable value is 300 (default). The client waits for acknowledgment from the server that the backup was successful. If the server does not reply within this time period, the archive bits are not cleared. This option applies only to differential-incremental backups. Cumulative-incremental backups do not clear the archive bit. Use change journal

Note: The Use Change Journal option applies to Windows clients only.
The Use Change Journal option allows the accelerator to identify data changes on Windows clients at a faster rate. With this option, the accelerator identifies changes by means of the client's NTFS change journal. When this option is not enabled, the accelerator must read through the client's file system to locate changed data. This option works together with the Use accelerator policy attribute and the Accelerator forced rescan schedule attribute. See Use accelerator (policy attribute) on page 565. See Accelerator forced rescan (schedule attribute) on page 590.

Incrementalsbasedontimestamp Specifies that files are selected for the backups that are based on the date that the file was last modified. When Use change journal is selected, Incrementals based on timestamp is automatically selected.

102

Configuring Host Properties Client Settings properties for Windows clients

Table 3-22 Property

Incrementals based on archive bit

Windows Client Settings properties (continued)

Description
Specifies that NetBackup include files in an incremental backup only if the archive bit of the file is set. The system sets this bit whenever a file is changed and it normally remains set until NetBackup clears it. A full backup always clears the archive bit. A differential-incremental backup clears the archive bit if the file is successfully backed up. The differential-incremental backup must occur within the number of seconds that the Wait time before clearing archive bit property indicates. A cumulative-incremental or user backup has no effect on the archive bit. Disable this property to include a file in an incremental backup only if the date and time stamp for the file has changed since the last backup. For a differential-incremental backup, NetBackup compares the date/time stamp to the last full or incremental backup. For a cumulative-incremental backup, NetBackup compares the timestamp to the last full backup. If you install or copy files from another computer, the new files retain the date timestamp of the originals. If the original date is before the last backup date on this computer, then the new files are not backed up until the next full backup.

Note: Symantec recommends that you do not combine differential incremental

backups and cumulative incremental backups within the same Windows policy when the incremental backups are based on archive bit. Time overlap Specifies the number of minutes to add to the date range for incremental backups when you use date-based backups. This value compensates for differences in the speed of the clock between the NetBackup client and server. The default is 60 minutes. This value is used during incremental backups when you use the archive bit and when you examine the create time on folders. This comparison is done for archive bit-based backups as well as date-based backups. Communications buffer size Specifies the size (in kilobytes) of the TCP and IP buffers used to transfer data between the NetBackup server and client. For example, specify 10 for a buffer size of 10 kilobytes. The minimum allowable value is 2, with no maximum allowable value. The default is 16 kilobytes. Specifies the seconds that are allowed between when a user requests a backup or restore and when the operation begins. The operation fails if it does not begin within this time period. This property has no minimum value or maximum value. The default is 60 seconds.

User directed timeouts

Configuring Host Properties Client Settings properties for Windows clients

103

Table 3-22 Property

Maximum error messages for server

Windows Client Settings properties (continued)

Description
Defines how many times a NetBackup client can send the same error message to a NetBackup server. For example, if the archive bits cannot be reset on a file, this property limits how many times the message appears in the server logs. The default is 10. Specifies how many days the system keeps progress reports before NetBackup automatically deletes them. The default is 3 days. Instructs NetBackup to search the default range of backup images automatically. The backed up folders and files within the range appear whenever a restore window is opened. Clear the Perform default search for restore check box to disable the initial search. With the property disabled, the NetBackup Restore window does not display any files or folders upon opening. The default is that the option is enabled.

Keep status of user-directed backups, archives, and restores Perform default search for restore

How to determine if change journal support is useful in your NetBackup environment

Using NetBackup support for the change journal is beneficial only where the volumes are large and relatively static. Suitable candidates for enabling NetBackup change journal support are as follows:

If the NTFS volume contains more than 1,000,000 files and folders and the number of changed objects between incremental backups is small (less than 100,000), the volume is a good candidate for enabling NetBackup change journal support.

Unsuitable candidates for enabling NetBackup change journal support are as follows:

Support for the change journal is intended to reduce scan times for incremental backups by using the information that is gathered from the change journal on a volume. Therefore, to enable NetBackup change journal support is not recommended if the file system on the volume contains relatively few files and folders. (For example, hundreds of thousands of files and folders.) The normal file system scan is suitable under such conditions. If the total number of changes on a volume exceeds from 10% to 20% of the total objects, the volume is not a good candidate for enabling NetBackup change journal support. Be aware that virus scanning software can interfere with the use of the change journal. Some real-time virus scanners intercept a file open for read, scan for

104

Configuring Host Properties Cloud Storage properties

viruses, then reset the access time. This results in the creation of a change journal entry for every scanned file.

Guidelines for enabling NetBackup change journal support

The following items are guidelines to consider for enabling NetBackup change journal support:

A NetBackup client using change journal support must belong to only one policy. To use one policy avoids the confusion that multiple backup settings causes. Multiple backup settings can cause conflicted update sequence number (USN) information in the permanent record. Change journal support is not offered for user-directed backups. The USN stamps for full and incremental backups in the permanent record do not change. NetBackup support for change journal works with checkpoint restart for restores. See Checkpoint restart for restore jobs on page 542. Support for change journal is not offered with several NetBackup options or Symantec products. If Use change journal is enabled, it has no effect while you use the following options or products:

True image restore (TIR) or True image restore with Move Detection See Collect true image restore information (policy attribute) with and without move detection on page 556. Synthetic backups See About synthetic backups on page 683. Bare Metal Restore (BMR) For more information, see the NetBackup Bare Metal Restore Administrators Guide.

See How to determine if change journal support is useful in your NetBackup environment on page 103.

Cloud Storage properties

The Cloud Storage properties apply to currently selected media servers. The Cloud Storage properties contain information about metering, bandwidth throttling, and network connections.

Configuring Host Properties Cloud Storage properties

105

For more information about NetBackup Cloud Storage, see the NetBackup Cloud Administrator's Guide. Figure 3-17 Cloud Storage dialog box

The Cloud Storage dialog box contains the following properties. Table 3-23 Property Cloud Storage dialog box properties Description

Key Management The name of your sites KMS server. If you have not configured KMS, Server (KMS) this displays as <kms_server_name>. Name MeteringInterval Determines how often information is gathered for reporting purposes. OpsCenter uses the information that is collected to create reports. The value is set in seconds. The default setting is 300 seconds (5 minutes). If you set this value to zero, metering is disabled. Total Available Bandwidth Use this value to specify the speed of your connection to the cloud. The value is specified in kilobytes per second. The default value is 104857600 KB/sec.

106

Configuring Host Properties Cloud Storage properties

Table 3-23 Property

Cloud Storage dialog box properties (continued) Description

Samplinginterval The time, in seconds, between measurements of bandwidth usage. The larger this value, the less often NetBackup checks to determine the bandwidth in use. Maximum connections This value determines the maximum number of connections that are allowed for the cloud provider.

Click Advanced Settings to specify additional settings for throttling. The Advanced Throttling Configuration dialog box contains the following properties. Figure 3-18 Advanced Throttling Configuration dialog box

Table 3-24 Property

Read bandwidth

Advanced Throttling Configuration dialog box settings Description

The read bandwidth value determines the size of the data packs transmitted from the cloud during each restore job. An increase in the value may increase performance when large amounts of contiguous data are accessed. If there is insufficient bandwidth to transmit the specified amount of data within a few minutes, restore failures may occur due to timeouts. Consider the total load of simultaneous jobs on multiple media servers when you calculate the required bandwidth.

Configuring Host Properties Cloud Storage properties

107

Table 3-24 Property

Write bandwidth

Advanced Throttling Configuration dialog box settings (continued) Description

The write bandwidth value determines the size of the data packs transmitted from the local computer to the cloud during each backup job. An increase in the value may increase performance when large amounts of contiguous data are accessed. If there is insufficient bandwidth to transmit the specified amount of data within a few minutes, restore failures may occur due to timeouts. Consider the total load of simultaneous jobs on multiple media servers when you calculate the required bandwidth.

Work time

Use this field to specify the time interval that is considered work time for the cloud connection. Specify a start and end time in 24-hour format. For example, 2:00 P.M. is 14:00. Indicate how much bandwidth the cloud connection can use in the Allocated bandwidth field. This determines how much of the available bandwidth is used for cloud operations in this time window. The value is expressed as a percentage or in kilobytes per second.

Off time

Use this field to specify the time interval that is considered off time for the cloud connection. Specify a start and end time in 24-hour format. For example, 2:00 P.M. is 14:00. Indicate how much bandwidth the cloud connection can use in the Allocated bandwidth field. This determines how much of the available bandwidth is used for cloud operations in this time window. The value is expressed as a percentage or in kilobytes per second.

Weekend

Specify the start and stop time for the weekend. Indicate how much bandwidth the cloud connection can use in the Allocated bandwidth field. This determines how much of the available bandwidth is used for cloud operations in this time window. The value is expressed as a percentage or in kilobytes per second.

108

Configuring Host Properties Credential Access properties

Credential Access properties

Certain NetBackup hosts that are not named as clients in a policy must be enabled to access NDMP or disk array credentials. Use the Credential Access properties dialog box to enter the names of those NetBackup hosts. Figure 3-19 Credential Access dialog box

The Credential Access dialog box contains the following properties. Table 3-25 Property
NDMP Clients list

Credential Access dialog box properties

Description
To add an NDMP client to the NDMP Clients list, click Add. Enter the names of the NDMP hosts that are not named as clients in a policy. To add a Disk Client to the DISK Clients list, click Add. Enter the names of the NetBackup hosts that meet all of the following criteria: The host must be designated in a policy as the Off-host backup host in an alternate client backup. The host that is designated as the Off-host backup computer must not be named as a client on the Clients tab in any NetBackup policy. The policy for the off-host backup must be configured to use one of the disk array snapshot methods for the EMC CLARiiON, HP EVA, or IBM disk arrays.

Disk clients list

Note: The credentials for the disk array or NDMP host are specified under Media
and Device Management > Credentials.

Note: Off-host alternate client backup is a feature of NetBackup Snapshot Client,

which requires a separate license. The NetBackup for NDMP feature requires the NetBackup for NDMP license.

Configuring Host Properties Data Classification properties

109

Data Classification properties

The Data Classification properties apply to currently selected master and media servers. Data classifications must be configured in the Data Classification host properties before storage life cycle policies can be configured. See Data classifications (policy attribute) on page 534. Figure 3-20 Data Classification dialog box

The Data Classification dialog box contains the following properties.

110

Configuring Host Properties Data Classification properties

Table 3-26 Property

Rank column

Data Classification dialog box properties

Description
The Rank column displays the rank of the data classifications. The order of the data classifications determines the rank of the classification in relationship to the others in the list. The lowest numbered rank has the highest priority. Use the Move Up and Move Down options to move the classification up or down in the list. To create a new data classification, click New. New data classifications are added to bottom of the list. To increase the rank of a data classification, select a line and click Move Up. To decrease the rank of a data classification, select a line and click Move Down.

Name column

The Name column displays the data classification name. While data classifications cannot be deleted, the data classification names can be modified. NetBackup provides the following data classifications by default:

Platinum (highest rank by default) Gold (second highest rank by default) Silver (third highest rank by default) Bronze (lowest rank by default)

Description column

In the Description column, enter a meaningful description for the data classification. Descriptions can be modified. The Data Classification ID is the GUID value that identifies the data classification and is generated when a new data classification is added and the host property is saved. A data classification ID becomes associated with a backup image by setting the Data Classification attribute in the policy dialog box. The ID is written into the image header. The storage lifecycle policies use the ID to identify the images that are associated with classification. ID values can exist in image headers indefinitely, so data classifications cannot be deleted. The name, description, and rank can change without changing the identity of the data classification.

Data Classification ID

Note: Data classifications cannot be deleted. However, the name, description, and the rank can be changed. The classification ID remains the same.

Creating a Data Classification

Use the following procedures to create or change a data classification.

Configuring Host Properties Default Job Priorities properties

111

To create a data classification

1 2 3 4 5

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties. In the left pane, click Data Classification. Click New. Add the name and description in the New Data Classification dialog box. Click OK to save the classification and close the dialog box. Note: Data classifications cannot be deleted.

Select a line in the Data Classification host properties and use the Move Up and Move Down options to move the classification level up or down in the list.

Default Job Priorities properties

The Default Job Priorities host properties let administrators configure the default job priority for different job types. The Default Job Priorities host properties list 18 job types and the configurable default priority for each. Figure 3-21 Default Job Priorities dialog box

The job priority can be set for individual jobs in the following utilities:

112

Configuring Host Properties Default Job Priorities properties

In the Jobs tab of the Activity Monitor for queued or active jobs. See Changing the Job Priority dynamically from the Activity Monitor on page 842. In the Catalog utility for verify, duplicate, and import jobs. In the Reports utility for a Media Contents report job. In the Backup, Archive, and Restore client interface for restore jobs.

The Default Job Priorities dialog box contains the following properties. Table 3-27 Property Description Default Job Priorities dialog box properties

Job Type and Job Priority list This listing includes 18 job types and the current configurable priority for each. Job Priority The Job Priority value specifies the priority that a job has as it competes with other jobs for backup resources. The value can range from 0 to 99999. The higher the number, the greater the priority of the job. A new priority setting affects all the policies that are created after the host property has been changed. A higher priority does not guarantee that a job receives resources before a job with a lower priority. NetBackup evaluates jobs with a higher priority before those with a lower priority. However, the following factors can cause a job with a lower priority to run before a job with a higher priority: To maximize drive use, a low priority job may run first if it can use a drive that is currently loaded. A job with a higher priority that requires that the drive be unloaded would wait. If a low priority job can join a multiplexed group, it may run first. The job with a higher priority may wait if it is not able to join the multiplexed group. If the NetBackup Resource Broker (nbrb) receives a job request during an evaluation cycle, it does not consider the job until the next cycle, regardless of the job priority.

Understanding the Job Priority setting

NetBackup uses the Job Priority setting as a guide. Requests with a higher priority do not always receive resources before a request with a lower priority. The NetBackup Resource Broker (NBRB) maintains resource requests for jobs in a queue. NBRB evaluates the requests sequentially and sorts them based on the following criteria:

Configuring Host Properties Default Job Priorities properties

113

The request's first priority. The requests second priority. The birth time (when the Resource Broker receives the request).

The first priority is weighted more heavily than the second priority, and the second priority is weighted more heavily than the birth time. Because a request with a higher priority is listed in the queue before a request with a lower priority, the request with a higher priority is evaluated first. Even though the chances are greater that the higher priority request receives resources first, it is not always definite. The following scenarios present situations in which a request with a lower priority may receive resources before a request with a higher priority:

A higher priority job needs to unload the media in a drive because the retention level (or the media pool) of the loaded media is not what the job requires. A lower priority job can use the media that is already loaded in the drive. To maximize drive utilization, the Resource Broker gives the loaded media and drive pair to the job with the lower priority. A higher priority job is not eligible to join an existing multiplexing group but a lower priority job is eligible to join the multiplexing group. To continue spinning the drive at the maximum rate, the lower priority job joins the multiplexing group and runs. The Resource Broker receives resource requests for jobs and places the requests in a queue before processing them. New resource requests are sorted and evaluated every 5 minutes. Some external events (a new resource request or a resource release, for example) can also trigger an evaluation. If the Resource Broker receives a request of any priority while it processes requests in an evaluation cycle, the request is not evaluated until the next evaluation cycle starts.

114

Configuring Host Properties Distributed application restore mapping properties

Distributed application restore mapping properties

Figure 3-22 Distributed Application Restore Mapping dialog box

Some applications, such as SharePoint and Exchange, distribute and replicate data across multiple hosts. Special configuration is required to allow NetBackup to restore databases to the correct hosts in a SharePoint farm. For Exchange, this configuration is required for an Exchange Database Availability (DAG), cluster, or private network or for an off-host backup. In the Distributed application restore mapping properties, add each host in the environment. The Distributed Application Restore Mapping dialog box contains the following properties.

Configuring Host Properties Encryption properties

115

Table 3-28 Property

Add

Distributed Application Restore Mapping dialog box properties

Description
Adds a host that is authorized to run restores on SharePoint component hosts or Exchange hosts.You must provide the name of the Application host and the name of the Component host in the SharePoint farm. Or for Exchange provide the host names in the DAG, cluster, or private network, or the hosts that perform the off-host backups.

Note: For restores to be successful in an Exchange 2010 DAG environment, you must
add the CAS server to the list. Change Remove Changes the application host or component host of the currently selected mapping. Removes the currently selected mapping.

For more information, see the following: NetBackup for Microsoft SharePoint Server Administrator's Guide. NetBackup for Microsoft Exchange Server Administrator's Guide.

Encryption properties
The Encryption properties control encryption on the currently selected client. Multiple clients can be selected and configured at one time only if all selected clients are running the same version of NetBackup. If not, the Encryption properties dialog box is hidden. The separately-priced NetBackup Encryption option must be installed on the client for these settings (other than Allowed) to take effect. More information is available in the NetBackup Security and Encryption Guide.

116

Configuring Host Properties Encryption properties

Figure 3-23

Encryption dialog box

The Encryption permissions property indicates the encryption setting on the selected NetBackup client as determined by the master server. Table 3-29 Property
Not allowed

Encryption permissions selections Description

Specifies that the client does not permit encrypted backups. If the server requests an encrypted backup, the backup job ends due to error. Specifies that the client allows either encrypted or unencrypted backups. Allowed is the default setting for a client that has not been configured for encryption. Specifies that the client requires encrypted backups. If the server requests an unencrypted backup, the backup job ends due to error.

Allowed

Required

Select the Enable encryption property if the NetBackup Encryption option is used on the selected client. After Enable Encryption is selected, choose from the properties in Table 3-30.

Configuring Host Properties Encryption properties

117

Table 3-30 Property

Enable standard encryption

Encryption dialog box properties Description

Pertains to the 128-bit and the 256-bit options of NetBackup Encryption. If the selected client does not use Legacy encryption, Enable standard encryption is automatically selected.

Client Cipher

The following cipher types are available: BF-CFB, DES-EDE-CFB, AES-256-CFB, and AES-128-CFB. AES-128-CFB is the default. More information on the ciphers file is found in the NetBackup Security and Encryption Guide.

Enable legacy DES encryption

Pertains to the 40-bit and the 56-bit data encryption standard (DES) NetBackup encryption packages. Defines the encryption strength on the NetBackup client when Legacy encryption is used: DES_40 Specifies the 40-bit DES encryption. DES_40 is the default value for a client that has not been configured for encryption. DES_56 Specifies the 56-bit DES encryption.

Encryption strength

Encryption libraries

Specify the folder that contains the encryption libraries on NetBackup clients. The default location is as follows:

On Windows systems install_path\netbackup\bin\ Where install_path is the directory where NetBackup is installed and by default is C:\Program Files\VERITAS.

On UNIX systems /usr/openv/lib

If it is necessary to change the setting, specify the new name.

118

Configuring Host Properties Enterprise Vault properties

Table 3-30 Property

Encryption key file

Encryption dialog box properties (continued) Description

Specify the file that contains the encryption keys on NetBackup clients. The default location is as follows:

On Windows systems install_path\NetBackup\bin\keyfile.dat Where install_path is the folder where NetBackup is installed and by default is C:\Program Files\VERITAS.

On UNIX systems /usr/openv/netbackup/keyfile

If it is necessary to change the setting, specify the new name.

Enterprise Vault properties

The Enterprise Vault properties apply to currently selected clients. To perform backups and restores, NetBackup must know the user name and password for the account that is used to log on to the Enterprise Vault Server and to interact with the Enterprise Vault SQL database. The user must set the logon account for every NetBackup client that runs backup and restore operations for Enterprise Vault components.

Configuring Host Properties Enterprise Vault Hosts properties

119

Figure 3-24

Enterprise Vault dialog box

The Enterprise Vault dialog box contains the following properties. Table 3-31 Property
User Name

Enterprise Vault dialog box properties

Description
Specify the user ID for the account that is used to log on to Enterprise Vault (DOMAIN\user name). Specify the password for the account.

Password

Consistency check before backup Select what kind of consistency checks to perform on the SQL Server databases before NetBackup begins a backup operation.

Enterprise Vault Hosts properties

The Enterprise Vault Hosts properties apply to currently selected master servers. Special configuration is required to allow NetBackup to restore SQL databases to the correct hosts in an Enterprise Vault farm. In the Enterprise Vault Hosts

120

Configuring Host Properties Exchange properties

master server properties, specify a source and a destination host. By doing so, you specify a source host that can run restores on the destination host. Figure 3-25 Enterprise Vault Hosts master server properties

The Enterprise Vault Hosts dialog box contains the following properties. Table 3-32 Option
Add

Enterprise Vault Hosts dialog box properties

Description
Adds the source and the destination hosts within the Enterprise Vault configuration. You must provide the name of the Source host and the name of the Destination host. Changes the source host and the destination host, an entry that you select from the Enterprise Vault Hosts field.

Change

Exchange properties
The Exchange properties apply to the currently selected Windows clients. For clustered or replicated environments, configure the same settings for all nodes. If you change the attributes for the virtual server name, only the active node is updated.

Configuring Host Properties Exchange properties

121

For complete information on these options, see the NetBackup for Microsoft Exchange Server Administrator's Guide . Figure 3-26 Exchange dialog box

The Exchange dialog box contains the following properties. Table 3-33 Property Exchange dialog box properties

Description

Snapshot verification I/O throttle For snapshot backups, specify the number of I/Os to process for each 1-second pause. This option applies to Exchange 2003 SP2 and to Exchange 2007 if the Exchange Management Console is not installed on the alternate client.

122

Configuring Host Properties Exclude Lists properties

Table 3-33 Property

Exchange dialog box properties (continued)

Description

Backup option for log files during Choose which logs to include with snapshot backups: full backups Back up only uncommitted log files Select this option to back up only the log files that are uncommitted. This option is not recommended for Exchange 2010 DAG or Exchange 2007 CCR environments. Back up all log files (including committed log files)

Note: As of NetBackup 7.0, the default option is now Back up all log files
(including committed log files). If you previously changed this setting for a client, your selection remains the same. For new installations of NetBackup, the default is Back up all log files (including committed log files). For upgrade installations where you did not change this setting for a client, the default is changed to Back up all log files (including committed log files) Truncate log after successful Instant Recovery backup Enable this option to delete transaction logs after a successful Instant Recovery backup. By default, transaction logs are not deleted for a full Instant Recovery backup that is snapshot only.

Exchange granular restore proxy You can specify a different Windows system to act as a proxy for the source host client. Use a proxy if you do not want to affect the source client or if it is not available. This situation applies when you duplicate a GRT-enabled backup image from a disk storage unit to a tape storage unit or when you use the bplist command. Mailbox for message level backup As of NetBackup 7.0, this setting no longer needs to be configured. and restore Enable single instance backup for Enable this option to back up the data that is stored on a Single Instance Store message attachments (SIS) volume. This feature only applies to Exchange Server 2007 and earlier versions. Perform consistency check before backup with Microsoft Volume Shadow Copy Service (VSS) Disable this option if you do not want to perform a consistency check during an Exchange 2010 DAG backup. If you check Continue with backup if consistency check fails, NetBackup continues to perform the backup even if the consistency check fails.

Exclude Lists properties

Use the Exclude Lists properties to create and to modify the exclude lists for Windows clients. An exclude list names the files and directories to be excluded from backups of the selected Windows clients.

Configuring Host Properties Exclude Lists properties

123

For UNIX clients, use the bpgetconfig and bpsetconfig commands to gather and modify the exclude list files from the /usr/openv/netbackup directory on each client. Figure 3-27 Exclude Lists dialog box

Exclude Lists properties apply only to Windows clients. On NetWare target clients, specify the exclude list when the targets are added. NetWare NonTarget clients do not support exclude lists. For more information, see the NetBackup users guide for the client. If more than one exclude or include list exists for a client, NetBackup uses only the most specific one. For example, assume that a client has the following exclude lists:

An exclude list for a policy and schedule. An exclude list for a policy. An exclude list for the entire client. This list does not specify a policy or schedule.

In this example, NetBackup uses the first exclude list (for policy and schedule) because it is the most specific.

124

Configuring Host Properties Exclude Lists properties

Exclude and include lists that are set up for specific policies and schedules, are not used to determine if an entire drive is to be excluded when NetBackup determines if a backup job should be started. Normally, this is not a problem. However, if a policy uses multistreaming, a drive which is excluded for a specific policy and schedule will have backup jobs started for it. Since no data will have needed to be backed up, this job reports an error status when it completes. To avoid the situation, base the exclude list on the client and not on a policy and schedule. The Exclude Lists dialog box contains the following properties. Table 3-34 Property
Use case sensitive exclude list property Exclude list

Excludes Lists dialog box properties

Description
Indicates that the files and directories to exclude are case-sensitive.

Displays the policies that contain schedule, file, and directory exclusions as follows: Add Excludes a file from being backed up by a policy. The exclusion is configured in the Add to exclude list dialog box, then added to the Exclude list. When the policies in this list are run, the files and directories that are specified on the list are backed up. Add to all Adds the selected list item to all currently selected clients. The item is excluded from the backup list on all selected clients. Add to all is enabled only when more than one client is selected for configuration and a list item is selected was not configured on the selected hosts. (Rather, an unavailable list item is selected.) Click Add to All to add the selected list item to all currently selected clients. The item is excluded from the backup list on all selected clients. Remove Removes the selected policy, schedule, or file from the Exclude list. The item is included in the backup.

Configuring Host Properties Exclude Lists properties

125

Table 3-34 Property

Exceptions to exclude list

Excludes Lists dialog box properties (continued)

Description
Displays the policies, schedules, files, and directories that are excepted from the Exclude list. When the policies on the Exceptions to the exclude list run, the files and directories on the list are backed up. The list is useful to exclude all files in a directory but one. Options include the following: Add Creates an exception to the Exclude list. The exception is configured in the Add exceptions to exclude list dialog box, then added to the Exceptions to the exclude list. When the policies on the Exceptions to the exclude list run, the items on the exceptions list are backed up. Effectively, you add files back into the backup list of a policy. Add to all Adds the selected list item to the Exceptions to the exclude list of all currently selected clients. When the policies on the exclude list run, the items on the exceptions list are backed up on all selected clients. Remove Removes the selected policy, schedule, or file from the Exceptions list. The item is excluded from the backup.

About the Add to exclude list and Add to exceptions list dialog boxes
The Add to Exclude List dialog box and the Add Exceptions to Exclude List dialog box contain the following fields: Table 3-35 Field
Policy

Add to Exclude dialog box Description

The policy name that contains the files and the directories that you want to exclude or make exceptions for. You can also select the policy name from the drop-down menu. To exclude or make exceptions for the backup of specific files or directories from all policies, select <All Policies>. The schedule name that is associated with the files and the directories that you want to exclude or make exceptions for. You can also select the schedule name from the drop-down menu. To exclude or make exceptions for the backups of specific files or directories from all schedules, select <All Schedules>.

Schedule

126

Configuring Host Properties Exclude Lists properties

Table 3-35 Field

Files/Directories

Add to Exclude dialog box (continued) Description

The full path to the file(s) and the directories that you want to exclude or make exceptions for.

Figure 3-28

Add to Exclude List properties

Adding an entry to an exclude list

Use the following procedure to add an entry to an exclude list for a policy: To add an entry to the exclude list

1 2 3

In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Clients. Double-click on a client. Under the Exclude List, click Add. In the Policy field, select a policy name from the drop-down menu or enter the name of a policy. Select All Policies to exclude these items from all policies. In the Schedule field, select a schedule name from the drop-down menu or enter the name of a schedule. Select All Schedules to exclude the specified files and directories from all schedules in the policy. In the Files/Directories field, enter the files or directories to be excluded from the backups that are based on the selected policy and schedule. Click Add to add the specified files and directories to the exclude list. Click Apply to accept the changes. Click OK to accept the changes and close the host properties dialog box.

5 6 7

Adding an exception to the exclude list

Use the following procedure to add an exception to the exclude list for a policy:

Configuring Host Properties Exclude Lists properties

127

To add an exception to the exclude list

1 2 3

In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Clients. Double-click on a client. Under the Exceptions to the Exclude List, click Add. In the Policy field, select a policy name from the drop-down menu or enter the name of a policy. Select All Policies to add these items back into all policies. (In other words, these items are to be excluded from the exclude list.) In the Schedule field, select a schedule name from the drop-down menu or enter the name of a schedule. Select All Schedules to add these items back into the schedules. In the Files/Directories field, enter the files or directories to be added back into the backups that are based on the selected policy and schedule. Click Add to add the specified files and directories to the Exceptions to the Exclude List. Click Apply to accept the changes. Click OK to accept the changes and close the host properties dialog box.

5 6 7

Syntax rules for exclude lists

Symantec suggests that you always specify automounted directories and CD-ROM file systems in the exclude list. Otherwise, if the directories are not mounted at the time of a backup, NetBackup must wait for a timeout. The following syntax rules apply to exclude lists:

Only one pattern per line is allowed. NetBackup recognizes standard wildcard use. See Wildcard use in NetBackup on page 898. See NetBackup naming conventions on page 897. Spaces are considered legal characters. Do not include extra spaces unless they are part of the file name. For example, if you want to exclude a file named C:\testfile (with no extra space character at the end) and your exclude list entry is C:\testfile (with an extra space character at the end) NetBackup cannot find the file until you delete the extra space from the end of the file name.

End a file path with \ to exclude only directories with that path name (for example, C:\users\test\). If the pattern does not end in \ (for example,

128

Configuring Host Properties Exclude Lists properties

C:\users\test), NetBackup excludes both files and directories with that path

name.

To exclude all files with a given name, regardless of their directory path, enter the name. For example:
test

rather than
C:\test

This example is equivalent to prefixing the file pattern with

\ \*\ \*\*\ \*\*\*\

and so on. The following syntax rules apply only to UNIX clients:

Do not use patterns with links in the names. For example, assume /home is a link to /usr/home and /home/doc is in the exclude list. The file is still backed up in this case because the actual directory path, /usr/home/doc, does not match the exclude list entry, /home/doc. Blank lines or lines which begin with a pound sign (#) are ignored.

Windows client exclude list example

Assume that an exclude list in the Exclude Lists host properties contains the following entries:
C:\users\doe\john C:\users\doe\abc\ C:\users\*\test C:\*\temp core

Given the exclude list example, the following files, and directories are excluded from automatic backups:

The file or directory named C:\users\doe\john. The directory C:\users\doe\abc\ (because the exclude entry ends with \). All files or directories named test that are two levels beneath users on drive C.

Configuring Host Properties Fibre Transport properties

129

All files or directories named temp that are two levels beneath the root directory on drive C. All files or directories named core at any level and on any drive.

Traversing excluded directories

An exclude list can indicate a directory for exclusion, while the client uses an include list to override the exclude list. NetBackup traverses the excluded directories if necessary, to satisfy the clients include list. Assume the following settings for a Windows client:

The backup policy backup selection list indicates ALL_LOCAL_DRIVES. When a scheduled backup runs, the entire client is backed up. The entire client is also backed up if the backup selection list consists of only: / The exclude list on the client consists of only: * An exclude list of * indicates that all files are excluded from the backup. However, since the include list on the Windows client includes the following file: C:\WINNT, the excluded directories are traversed to back up C:\WINNT. If the include list did not contain any entry, no directories are traversed.

In another example, assume the following settings for a UNIX client:

The backup selection list for the client consists of the following: / The exclude list for the UNIX client consists of the following: / The include list of the UNIX client consists of the following directories:
/data1 /data2 /data3

Because the include list specifies full paths and the exclude list excludes everything, NetBackup replaces the backup selection list with the clients include list.

Fibre Transport properties

The Fibre Transport master server properties apply to the SAN clients whose preferences have not been set explicitly. The Fibre Transport properties apply only when the SAN Client license is installed. The Fibre Transport media server property applies to the SAN clients for selected media servers.

130

Configuring Host Properties Fibre Transport properties

The Fibre Transport client properties apply to the selected SAN clients. The defaults for clients are the property settings of the master server. An FT device is the target mode driver on a NetBackup FT media server. An FT pipe is the logical connection that carries backup and restore data between an FT media server and a SAN client. For more information about NetBackup Fibre Transport, see the NetBackup SAN Client and Fibre Transport Guide. Figure 3-29 Master server Fibre Transport host properties

The master server Fibre Transport dialog box contains the following properties. Table 3-36 Property
Preferred

Fibre Transport dialog box properties

Description
The Preferred property specifies to use an FT pipe if an FT device is available within the configured wait period in minutes. If an FT device is not available after the wait period elapses, NetBackup uses a LAN connection for the operation. If you select this option, also specify the wait period for backups and for restores. For the global property that is specified on the master server, the default is Preferred.

Configuring Host Properties Firewall properties

131

Table 3-36 Property

Always

Fibre Transport dialog box properties (continued)

Description
The Always property specifies that NetBackup should always use an FT pipe for backups and restores of SAN clients. NetBackup waits until an FT device is available before it begins the operation. However, an FT device must be active and available. If no FT device exists, NetBackup uses the LAN. An FT device may not exist because none is active, none have been configured, or the SAN Client license expired.

Never

The Never property specifies that NetBackup should never use an FT pipe for backups and restores of SAN clients. NetBackup uses a LAN connection for the backups and restores. If you specify Never for the master server, Fibre Transport is disabled in the NetBackup environment. If you select Never, you can configure FT usage on a per-client basis. If you specify Never for a media server, Fibre Transport is disabled for the media server. If you specify Never for a SAN client, Fibre Transport is disabled for the client.

Maximum concurrent FT connections

This property applies to the media properties only. This property specifies the number of FT connections to allow to a media server. The default is four times the number of HBA target ports (maximum of 16).

Use defaults from the master server configuration

This property applies to the client properties only. This property specifies that the client follow the properties as they are configured on the master server.

Firewall properties
The Firewall properties describe how the selected master and media servers are connected to by other hosts. Servers are added to the host list of the Firewall properties. To configure port usage for clients, see the Client Attributes properties. See Client Attributes properties on page 81.

132

Configuring Host Properties Firewall properties

Figure 3-30

Firewall dialog box

The Firewall dialog box contains the following properties. Table 3-37 Property
Default connect options

Firewall dialog box properties

Description
By default, NetBackup selects firewall-friendly connect options under Default connect options. However, the default options can be set differently for individual servers under Attributes for selected Hosts. By default, the firewall settings are configured to require the fewest possible ports to be open. To change the default connect options for the selected server, click Change. Click Change to change the Default connect options. Change the Firewall properties in the Default Connect Options dialog box.

Note: If VNETD only is selected as the Daemon connection port, the BPCD connect
back setting is not applicable. If VNETD only is selected as the Daemon connection port, Use non-reserved ports is always used regardless of the value of the Ports setting.

Configuring Host Properties Firewall properties

133

Table 3-37 Property

Hosts list

Firewall dialog box properties (continued)

Description
To change the default connect options for any server, add the server to the host list. Servers do not automatically appear on the list. Add option Click Add to add a host entry to the host list. A host must be listed before it can be selected for configuration. Add to all option Click Add to All to add the listed hosts (along with the specified properties) to all hosts that are selected for host property configuration. (That is, the hosts that are selected upon opening the Host Properties.) Remove option Select a host name in the list, then click Remove to remove the host from the list.

Attributes for selected hosts Connect options can be configured for individual servers. BPCD connect back This property specifies how daemons are to connect back to the NetBackup Client daemon (BPCD) as follows: Use default connect options (An option for individual hosts) Use the methods that are specified under Default connect options. Random port NetBackup randomly chooses a free port in the allowed range to perform the traditional connect-back method. VNETD port This method requires no connect-back. The Veritas Network Daemon (vnetd) was designed to enhance firewall efficiency with NetBackup during server-to-server and server-to-client communications. The server initiates all bpcd socket connections. Consider the example in which bpbrm on a media server initially connects with bpcd on a client. The situation does not pose a firewall problem because bpbrm uses the well-known bpcd port.

134

Configuring Host Properties Firewall properties

Table 3-37 Property

Ports

Firewall dialog box properties (continued)

Description
Select whether a reserved or non-reserved port number should be used to connect to the server: Use default connect options (An option for individual hosts) Use the methods that are specified under Default attributes. Reserved port Connect to the server by a reserved port number. Use non-reserved ports Connect to the server by a non-reserved port number. If this property is selected, also enable Accept connections from non-reserved ports for the selected server in the Universal Settings properties. See Universal Settings properties on page 214.

Daemon connection port

This option only affects connections to NetBackup 7.0 and earlier. For connections to NetBackup 7.0.1 and later, the veritas_pbx port is used. If configuring connections for NetBackup 7.0 and earlier, select the Daemon connection port method to use to connect to the server: Use default connect options (An option for individual hosts) Use the methods that are specified under Default connect options. Automatic The daemons on the server are connected to by vnetd if possible. If it is not possible to use vnetd, the daemons traditional port number makes the connection.

VNETD only

The daemons on the server are connected to by vnetd only. Select this property if your firewall rules prevent connections to the server by the traditional port number. Daemon port only The daemons on the server are connected to by the traditional port number only.

Note: If vnetd only is selected as the Daemon connection port, the BPCD connect
back setting is not applicable. If vnetd only is selected as the Daemon connection port, Non-reserved port is always used regardless of the value of the Ports setting. Defaults Set property settings back to the defaults.

Enabling logging for vnetd

Use the following procedure to enable logging for vnetd. To enable logging for vnetd

Create a vnetd directory in the following location:

Configuring Host Properties General Server properties

135

On Windows: install_path\NetBackup\logs\vnetd Or, double-click mklogdir.bat in the install_path\NetBackup\logs\ directory to populate the logs directory with log subdirectories, including one for vnetd.

On UNIX: /usr/openv/logs/vnetd

General Server properties

The General Server properties apply to selected master and media servers. Figure 3-31 General Server dialog box

The General Server dialog box contains the following properties. Table 3-38 Property
Delay on multiplexed restores

General Server dialog box properties

Description
This property specifies how long the server waits for additional restore requests of multiplexed images on the same tape. All of the restore requests that are received within the delay period are included in the same restore operation (one pass of the tape). The default is a delay of 30 seconds.

136

Configuring Host Properties General Server properties

Table 3-38 Property

General Server dialog box properties (continued)

Description

Check the capacity of disk storage This property determines how often NetBackup checks disk storage units for units every available capacity. If checks occur too frequently, then system resources are wasted. If checks do not occur often enough, too much time elapses and backup jobs are delayed. The default is 300 seconds (5 minutes).

Note: This property applies to the disk storage units of 6.0 media servers only.
Subsequent releases use internal methods to monitor disk space more frequently. Must use local drive This property appears for master servers only, but applies to all media servers as well. This property does not apply to NDMP drives. If a client is also a media server or a master server and Must use local drive is checked, a local drive is used to back up the client. If all drives are down, another can be used. This property increases performance because backups are done locally rather than sent across the network. For example, in a SAN environment a storage unit can be created for each SAN media server. Then, the media server clients may be mixed with other clients in a policy that uses ANY AVAILABLE storage unit. When a backup starts for a client that is a SAN media server, the backups go to the SAN connected drives on that server. Use direct access recovery for NDMP restores By default, NetBackup for NDMP is configured to use Direct Access Recovery (DAR) during NDMP restores. DAR can reduce the time it takes to restore files by allowing the NDMP host to position the tape to the exact location of the requested file(s). Only the data that is needed for those files is read. Clear this check box to disable DAR on all NDMP restores. Without DAR, NetBackup reads the entire backup image, even if only a single restore file is needed. Enable message-level cataloging when duplicating Exchange images that use Granular Recovery Technology This option performs message-level cataloging when you duplicate Exchange backup images that use Granular Recovery Technology (GRT) from disk to tape. To perform duplication more quickly, you can disable this option. However, then users are not able to browse for individual items on the image that was duplicated to tape. See the NetBackup for Exchange Adminstrator's Guide.

Configuring Host Properties General Server properties

137

Table 3-38 Property

Media host override list

General Server dialog box properties (continued)

Description
Specific servers can be specified in this list as servers to perform restores, regardless of where the files were backed up. (Both servers must be in the same master and media server cluster.) For example, if files were backed up on media server A, a restore request can be forced to use media server B. The following items describe situations in which the capability to specify servers is useful: Two (or more) servers share a robot and each have connected drives. A restore is requested while one of the servers is either temporarily unavailable or is busy doing backups. A media server was removed from the NetBackup configuration, and is no longer available.

To add a host to the Media host override list, click Add. Click Add to All to add a host to the list for all of the hosts currently selected. To change an entry in the list, select a host name, then click Change. Configure the following options in the Add Media Override settings or Change Media Override settings dialog box: Original backup server Type the name of the server where data was backed up originally. Restore server Type the name of the server that is to process future restore requests.

Defaults

Sets all properties back to the default settings.

Forcing restores to use a specific server

Use the following procedure to force restores to use a specific server.

138

Configuring Host Properties Global Attributes properties

To force restores to use a specific server

If necessary, physically move the media to the host to answer the restore requests, then update the Enterprise Media Manager database to reflect the move. Modify the NetBackup configuration on the master server. Add the original backup media server and the restore server to the Media host override list in the General Server host properties. Stop and restart the NetBackup Request Daemon (bprd) on the master server. This process applies to all storage units on the original backup server. Restores for any storage unit on the Original backup server go to the server that is listed as the Restore server. To revert to the original configuration for future restores, delete the line from the Media host override list.

Global Attributes properties

The Global Attributes properties apply to currently selected master servers. The Global Attributes properties affect all operations for all policies and clients. The default values are adequate for most installations but can be changed. Figure 3-32 Global Attributes dialog box

The Global Attributes dialog box contains the following properties.

Configuring Host Properties Global Attributes properties

139

Table 3-39 Property

Job retry delay

Global Attributes dialog box properties

Description
This property specifies how often NetBackup retries a job. The default is 10 minutes. The maximum is 60 minutes; the minimum is 1 minute. NetBackup considers the failure history of a policy to determine whether or not to run a scheduled backup job. The Schedule backup attempts property sets the timeframe for NetBackup to examine. This property determines the following characteristics for each policy: How many preceding hours NetBackup examines to determine whether to allow another backup attempt (retry). By default, NetBackup examines the past 12 hours. How many times a backup can be retried within that timeframe. By default, NetBackup allows two attempts. Attempts include the scheduled backups that start automatically or the scheduled backups that are user-initiated.

Schedule backup attempts

Consider the following example scenario using the default setting 2 tries every 12 hours:

Policy_A runs at 6:00 P.M.; Schedule_1 fails. Policy_A is user-initiated at 8:00 P.M.; Schedule_2 fails.

At 11:00 P.M., NetBackup looks at the previous 12 hours. NetBackup sees one attempt at 6:00 P.M. and one attempt at 8:00 P.M. The Schedule backup attempts setting of two has been met so NetBackup does not try again. At 6:30 A.M. the next morning, NetBackup looks at the previous 12 hours. NetBackup sees only one attempt at 8:00 P.M. The Schedule backup attempts setting of two has not been met so NetBackup tries again. If a schedule window is not open at this time, NetBackup waits until a window is open.

Note: This attribute does not apply to user backups and archives.
Policy update interval This property specifies how long NetBackup waits to process a policy after a policy is changed. The interval allows the NetBackup administrator time to make multiple changes to the policy. The default is 10 minutes. The maximum is 1440 minutes; the minimum is 1 minute. This property specifies the maximum number of backup and archive jobs that NetBackup clients can perform concurrently. The default is one job. NetBackup can process concurrent backup jobs from different policies on the same client only in the following situations:

Maximum jobs per client

More than one storage unit available One of the available storage units can perform more than one backup at a time.

See About constraints on the number of concurrent jobs on page 141.

140

Configuring Host Properties Global Attributes properties

Table 3-39 Property

Maximum backup copies

Global Attributes dialog box properties (continued)

Description
The Maximum backup copies property specifies the total number of copies of a backup image that can exist at the same time within a single master server domain. The number of copies can range from 2 to 10. (Default: 5) Multiple copies of a backup image can be created by using any of the following methods:

Configure a backup job to create multiple copies. See Multiple copies (schedule attribute) on page 595. Configure multiple copies as part of a Vault duplication job. See Creating a Vault policy on page 672. Configure multiple copies as part of a disk staging storage unit duplication job. See Configuring multiple copies in a relocation schedule on page 436. Configure a storage lifecycle policy that contains multiple duplication or replication operations. See Hierarchical view of storage operations in the Storage lifecycle policy dialog box on page 464. Use the bpduplicate command line to create multiple copies. Run a duplication operation from the Catalog node in the NetBackup Administration Console. See Duplicating backup images on page 781.

The Maximum backup copies property limits the number of coexisting copies of an image that can be created by any of the above operations. For example, consider the situation in which the maximum number of copies is reached, but eventually one or more of those copies expires. If at least one copy of the image still exists to be used as a source copy, then any of the above duplication operations can create more copies again, to take the place of the expired copies.

Note: If a copy of a backup image is sent to a different master server domain, none
of the copies at the remote domain count against the Maximum backup copies limit. Copies of backup images can be sent to a different NetBackup domain by using Auto Image Replication. See About NetBackup Auto Image Replication on page 804. Compress catalog interval This property specifies how long NetBackup waits after a backup before it compresses the image catalog file. This property specifies the maximum number of vault jobs that are allowed to be active on the master server. The greater the maximum number of vault jobs, the more system resources are used. See About the Jobs tab on page 836.

Maximum vault jobs

Configuring Host Properties Global Attributes properties

141

Table 3-39 Property

Administrator email address property

Global Attributes dialog box properties (continued)

Description
This property specifies the address(es) where NetBackup sends notifications of scheduled backups or administrator-directed manual backups. To send the information to more than one administrator, separate multiple email addresses by using a comma, as follows: [email protected],[email protected] Disaster recovery information that is created during online, hot catalog backups is not sent to the addresses indicated here. Disaster recovery information is sent to the address that is indicated on the Disaster Recovery tab in the catalog backup policy. See Disaster Recovery tab on page 669.

About constraints on the number of concurrent jobs

Specify any number of concurrent jobs within the following constraints. Table 3-40 Constraint
Number of storage devices

Constraints on concurrent jobs

Description
NetBackup can perform concurrent backups to separate storage units or to drives within a storage unit. For example, a single Media Manager storage unit supports as many concurrent backups as it has drives. A disk storage unit is a directory on disk, so the maximum number of jobs depends on system capabilities. Too many concurrent backups on an individual client interfere with the performance of the client. The best setting depends on the hardware, operating system, and applications that are running. The Maximum jobs per client property applies to all clients in all policies. To accommodate weaker clients (ones that can handle only a small number of jobs concurrently), consider using one of the following approaches: Set the Maximum data streams property for those weaker client(s) appropriately. (This property is found under Host Properties > Master Server > Client Attributes > General tab.) See General tab of the Client Attributes properties on page 83. Use the Limit jobs per policy policy setting in a client-specific policy. (A client-specific policy is one in which all clients share this characteristic). See Limit jobs per policy (policy attribute) on page 544.

Server and client speed

142

Configuring Host Properties Global Attributes properties

Table 3-40 Constraint

Network loading

Constraints on concurrent jobs (continued)

Description
The available bandwidth of the network affects how many backups can occur concurrently. Two Exabyte 8500, 8mm tape drives can create up to a 900-kilobyte-per-second network load. Depending on other factors, the load might be too much for a single Ethernet. For loading problems, consider backups over multiple networks or compression. A special case exists to back up a client that is also a server. Network loading is not a factor because the network is not used. Client and server loading, however, is still a factor.

Figure 3-33
Client /home

Maximum jobs per client

Policy A

Tape Drive 1

/usr

Policy B Server

Tape Drive 2

Note: Online, hot catalog backups can run concurrently with other backups. To do so, for the master server, set the Maximum jobs per client value to greater than two. The higher setting ensures that the catalog backup can proceed while the regular backup activity occurs.

Setting up email notifications about backups

Email notifications can be sent to the client's administrator or to the global administrator, specifying that a backup was successful or unsuccessful. The following represents the contents of a notification email:
Backup on client hostname by root was partially successful. File list --------C:\Documents and Settings

Before notification emails about backups are sent, the computing environment must be configured correctly.

Configuring Host Properties Global Attributes properties

143

NetBackup can send notification to specified email addresses about backups on all client or specific clients. To set up email notifications about backups, choose one or both of the following notification methods:

Send emails about failed backups only. Send a message to the email address(es) of the NetBackup administrator(s) about any backup that ends in a non-zero status. (Server sends mail host property is enabled in Universal Settings.) Send emails about successful and failed backups. Send a message to the local administrator(s) of each client about successful and unsuccessful backups. (Client sends mail host property is enabled in Universal Settings.)

Both methods require that the nbmail.cmd script be configured. Both methods require that the host properties be configured with email addresses:

See Sending email notifications to the administrator about unsuccessful backups on page 145. See Sending messages to the global administrator about unsuccessful backups on page 145. See Sending messages to the administrator about successful and unsuccessful backups on page 146.

Windows systems require that an application to transfer messages using the Simple Mail Transfer Protocol be installed to accept script parameters. UNIX platforms have an SMTP transfer method built into the system. See Installing and testing the email utility on page 147. See About constraints on the number of concurrent jobs on page 141.

Configuring the nbmail.cmd script

To receive email notifications about backups, the nbmail.com script must be configured for Windows. Use the following procedure to configure the nbmail.cmd script. To configure the nbmail.cmd script

1 2

On a NetBackup master server, locate

install_path\VERITAS\NetBackup\bin\goodies\nbmail.cmd.

If configuring the script on the client, copy nbmail.cmd from a master server to the client. By default, nbmail.cmd does not send email.

144

Configuring Host Properties Global Attributes properties

Use a text editor to open nbmail.cmd. Create a backup copy of nbmail.cmd before modifying it. In some text editors, using the word wrap option can create extra line feeds in the script and render it non-functional. The following options are used in the script:
-s -t -i The subject line of the email Indicates who receives the email. The originator of the email, though it is not necessarily known to the email server. The default (-i NetBackup) shows that the email is from NetBackup. The name of the SMTP server that is configured to accept and relay emails. Suppresses all output to the screen.

-server

-q

Most of the lines are informational in nbmail.cmd. Locate the following lines in the script:

@REM @REM @REM @REM

@IF "%~4"=="" ( blat %3 -s %2 -t %1 -i NetBackup -server SERVER_1 -q ) ELSE ( blat %3 -s %2 -t %1 -i NetBackup -server SERVER_1 -q -attach %4

@REM )

Adjust the fives lines as follows:

Remove @REM from each of the five lines to activate the necessary sections for BLAT to run. Replace SERVER_1 with the name of the email server. For example:

@IF "%~4"=="" ( blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q ) ELSE ( blat %3 -s %2 -t %1 -i NetBackup -server emailserver.company.com -q -attach %4 )

Save nbmail.cmd.

See About constraints on the number of concurrent jobs on page 141.

Configuring Host Properties Global Attributes properties

145

Sending email notifications to the administrator about unsuccessful backups

Use the following procedure to send email notifications to a client's administrator only if the backups have a non-zero status. To send email notifications to the administrator for backups with a non-zero status

On the server, install and configure a mail client. See Installing and testing the email utility on page 147.

On the server, edit the nbmail.cmd script. See Configuring the nbmail.cmd script on page 143.

3 4 5 6

On the master server, in the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers. In the right pane, double-click the master server you want to modify. In the properties dialog box, in the left pane, click Universal Settings. In the Client administrators email field, enter the email address of the administrator to receive the notification emails. (Separate multiple addresses with commas.) See Universal Settings properties on page 214.

Enable the Server sends mail option and click Apply.

Sending messages to the global administrator about unsuccessful backups

Use the following procedure to send messages to the global administrator about backups with a non-zero status. To send messages to the global administrator about backups with a non-zero status

On the server, install and configure a mail client. See Installing and testing the email utility on page 147.

On the server, edit the nbmail.cmd script. See Configuring the nbmail.cmd script on page 143.

3 4 5

On the master server, open the NetBackup Administration Console. In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Server. In the right pane, double-click the master server you want to modify.

146

Configuring Host Properties Global Attributes properties

6 7 8

Open the host properties of the master server. In the properties dialog box, in the left pane, click Global Attributes. In the Administrators email address field, enter the email address of the administrator to receive the notification emails. (Separate multiple addresses with commas.) Click Apply. The global administrators email address can also be changed by using the bpconfig command on the master server:
Install_Path\NetBackup\bin\admincmd\bpconfig -ma email_address

For example:
C:\Program Files\VERITAS\NetBackup\bin\admincmd\bpconfig -ma [email protected]

Sending messages to the administrator about successful and unsuccessful backups

An alternative to sending all emails through the master server is to send emails through each client. An email can be sent to each client's administrator after all backups. To send email notifications for all backups from a client

On the client, install and configure a mail client. See Installing and testing the email utility on page 147.

On the client, edit the nbmail.cmd script. See Configuring the nbmail.cmd script on page 143.

3 4 5 6 7

On the master server, open the NetBackup Administration Console. In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Clients. In the right pane, double-click the client you want to modify. Multiple clients can also be selected. In the properties dialog box, in the left pane, select Universal Settings. In the Client administrators email field, enter the email address of the administrator to receive the notification emails. (Separate multiple addresses with commas.) See Universal Settings properties on page 214.

Enable the Client sends mail option and click Apply.

Configuring Host Properties Global Attributes properties

147

Installing and testing the email utility

BLAT is the most common application is used for email notification. It is a mail client in the public domain. BLAT is used as an example in the following discussions. Use the following procedure to install and configure the email utility. To install and configure the email utility

1 2 3 4

Download the .ZIP file from the BLAT download page, currently: www.blat.net Extract the files to a directory. Copy the blat.exe file to the Windows System32 directory. From a command prompt, run the following command:
blat -install emailserver.company.com [email protected]

Where: emailserver.company.com is the hostname or IP address of the email server that sends the email notifications. [email protected] is the primary account to send the emails from the specified server.

Test the email utility, following the To test the email utility procedure.

Use the following procedure to test the email utility. To test the email utility

1 2

Create a test text file that contains a message. For example, create
C:\testfile.txt

From a command prompt, run:

blat C:\testfile.txt -s test_subject -to [email protected]

A correct setup sends the contents of testfile.txt to the email address specified.

Use the following list to troubleshoot problems if NetBackup notification does not work correctly:

Make sure that the BLAT command is not commented out in the nbmail.cmd script. Make sure that the path to blat.exe is specified in nbmail.cmd if the command is not in the \system32 directory.

148

Configuring Host Properties Logging properties

Make sure that BLAT syntax has not changed in the later versions of BLAT. Check the readme for the version of BLAT running on the system. The BLAT command may need the -ti n timeout parameter if the system experiences delays. (n represents seconds.) The BLAT binary must not be corrupt or incompatible with the email system. Download the latest version. Configure the email addresses correctly in the host properties. The email account that is specified must be a valid on the email server. If the email server requires authentication for SMTP, make sure that the account that is used for the NetBackup client process is authorized. The default account is the local system.

Logging properties
The Logging properties apply to the master servers, media servers, and clients that are currently selected. The available properties differ between master servers, media servers, and clients. The Logging properties contain the processes that continue to use legacy logging as well as processes that use unified logging.

Configuring Host Properties Logging properties

149

Table 3-41 Type

Unified logging

Logging types

Description
Unified logging creates log file names and messages in a format that is standardized across Symantec products. Some NetBackup processes on the server use unified logging. Unified logging writes the logs into subdirectories in the following locations:

UNIX: /usr/openv/logs Windows: install_path\NetBackup\logs

Unlike legacy logging, subdirectories for the processes that use unified logging are created automatically.

Note: Do not save logs to a remote file system such as NFS or CIFS. Logs that are stored
remotely and then grow large can cause critical performance issues. If Enable robust Logging is enabled, NetBackup uses the settings in the nblog.conf file as the unified logging settings. The maximum size of a log file is set by using the NetBackup command vxlogcfg with parameters NumberOfLogFiles and MaxLogFileSizeKB.

Note: Do not edit the nblog.conf file manually.

See the NetBackup Troubleshooting Guide for more information on controlling the log file size. If a NetBackup environment uses scripts depending on the MMDDYY.log naming convention, either update the scripts or uncheck Enable robust Logging.

150

Configuring Host Properties Logging properties

Table 3-41 Type

Legacy logging

Logging types (continued)

Description
For those processes that use legacy logging, administrators must first create a log directory for each process to be logged. A logging level selection on the Logging properties page does not enable logging. Create the NetBackup legacy log directories in the following locations:

UNIX: /usr/openv/netbackup/logs/process_name Windows: install_path\NetBackup\logs\process_name

Note: Do not save logs to a remote file system such as NFS or CIFS. Logs that are stored
remotely and then grow large can cause critical performance issues. On a Windows server, you can create all of the NetBackup debug log directories at one time by double-clicking mklogdir.bat in the following directory: install_path\NetBackup\logs\ Create the Media Manager legacy log directories in the following locations:

UNIX: /usr/openv/volmgr/debug Windows: install_path\Volmgr\debug

For details on both unified and legacy logging, see the NetBackup Troubleshooting Guide.

Configuring Host Properties Logging properties

151

Figure 3-34

Logging dialog box

The Logging dialog box contains the following properties.

152

Configuring Host Properties Logging properties

Table 3-42 Property

Enable robust logging

Logging dialog box properties

Description
A check in the Enable robust logging check box indicates that when a log file grows to the maximum size, the log file is closed. When the log file is closed, a new log file is opened. If the new log file causes the maximum number of log files in the directory to be exceeded, the oldest log file is deleted. See the NetBackup Troubleshooting Guide for more information about controlling the log file size. If this property is enabled, the following processes produce log files:

bprd bpbkar bpbrm bpcd bpdbm bptm bpdm

The logs are named using the following convention: MMDDYY_NNNNN.log where NNNNN is an incrementing counter from 00001 - 99999 If the Enable robust logging property is disabled, a single log file is produced each day: MMDDYY.log Whether Enable robust logging is selected or not, the log file is pruned by using KEEP_LOGS_DAYS and DAYS_TO_KEEP_LOGS settings.

Note: If a NetBackup environment uses scripts depending on the MMDDYY.log naming

convention, either update the scripts or disable the Enable robust logging option. Global logging level This property is used for debugging purposes. The logging levels control the amount of information that the NetBackup server writes to logs. Six levels are supported. Select from between 0 (minimum logging level) through 5 (maximum logging level).

Note: Use the default setting of 0 unless advised otherwise by Symantec Technical
Support. Other settings can cause the logs to accumulate large amounts of information. Some NetBackup processes allow individual control over the amount of information the process writes to logs. For those processes, specify a different logging level other than the Global logging level.

Configuring Host Properties Logging properties

153

Table 3-42 Property

Process specific overrides

Logging dialog box properties (continued)

Description
The services that are listed under Process specific overrides use legacy logging. These services require that you first create a log directory in the following location:

UNIX: /usr/openv/netbackup/logs/process_name Windows: install_path\NetBackup\logs\process_name

Table 3-43 lists and describes the processes that use legacy logging. Debug logging levels for NetBackup services The Logging properties page offers configurable debug levels for the services that use unified logging. Each service creates a log automatically in the following directories:

UNIX: /usr/openv/logs Windows: install_path\NetBackup\logs

You can also use the vxlogcfg command to change debug levels. Table 3-44 lists and describes the services that use unified logging.

Table 3-43 Service

Process specific overrides Description

The NetBackup backup and restore manager. The NetBackup tape manager. The NetBackup disk manager. The NetBackup database manager. Select a logging level for bpvault. The NetBackup request daemon or manager.

BPBRM logging level BPTM logging level BPDM logging level BPDBM logging level Vault logging level BPRD logging level

154

Configuring Host Properties Login Banner Configuration properties

Table 3-44 Service

Debug logging levels for NetBackup services Description

This property appears for EMM servers. NBPEM creates Policy/Client tasks and determines when jobs are due to run. If a policy is modified or if an image expires, NBPEM is notified and the appropriate Policy/Client tasks are updated. This property appears for EMM servers. NBJM accepts the jobs that the Policy Execution Manager submits and acquires the necessary resources. NBRB makes the allocations for storage units, tape drives, client reservations.

Policy Execution Manager

Job Manager

Resource Broker

Login Banner Configuration properties

Use the Login Banner Configuration properties to configure a banner screen that appears each time a user logs into the NetBackup Administration Console or the Backup, Archive, and Restore client console. The Login Banner Configuration properties can be configured to make it mandatory for the user to acknowledge the login banner screen before the user can access the console. A different login banner can be configured for any master server, media server, or client. Figure 3-35 shows example banner text for a media server.

Configuring Host Properties Login Banner Configuration properties

155

Figure 3-35

Login Banner Configuration dialog box

The first time that the NetBackup Administration Console is launched, the Login Banner Configuration properties are not configured so no banner appears to the user. The Login Banner Configuration host properties must be configured in order for the banner to appear. The user can change the server once they log into the console. (On the File menu, click Change Server.) If the banner is configured for the remote server, the banner appears on the remote server as well. Note: The banner is not available on NetBackup versions earlier than 6.5.4. If a user changes to a host that is at NetBackup version 6.5.3 or earlier, no banner appears. If a user opens a new console or window from the existing console, the banner does not appear for the new window. (On the File menu, click the New Console option or the New Window from Here option.) Table 3-45 Property
Login Banner Heading

Login Banner Configuration dialog box properties Description

Enter the text that is to appear in the banner.

156

Configuring Host Properties Login Banner Configuration properties

Table 3-45 Property

Text of login banner Show Agree and Disagree buttons on the login banner

Login Banner Configuration dialog box properties (continued) Description

Enter the text for the banner message. The maximum is 29,000 characters. Configure this option when approval is necessary to use the NetBackup Administration Console or the Backup, Archive, and Restore client console. Specific approval may be required due to a legal agreement at the company in which the NetBackup environment resides. If this option is enabled, users are required to click the Agree option and then click OK before the console opens. The agreement is meant only for the user that reads and agrees to the message. If the user chooses the Disagree option, the screen is closed.

Figure 3-36

Login Banner with agreement option enabled

Configuring Host Properties Login Banner Configuration properties

157

Figure 3-37

Login Banner without agreement option

Removing login banner screen and text

To remove the banner and the text that appears after a user logs into NetBackup, use the following procedure: To remove the login banner screen and text

1 2 3 4 5 6

In the NetBackup Administration Console, expand NetBackup Management > Host Properties. Depending on the host that displays the login banner, select Master Servers, Media Servers, or Clients). In the right pane, double-click the host name to display the properties. In the properties dialog box, in the left pane, click the Login Banner Configuration host properties. Clear the Login Banner Heading text and the login banner text. Click OK to save the changes.

Enabling the Auto log off timeout option

A related option, but one not configured in the Login Banner Configuration host properties, is the Auto log off timeout option. The Auto log off timeout option allows NetBackup to automatically log a user out of the NetBackup Administration Console after a period of inactivity. The session

158

Configuring Host Properties Lotus Notes properties

must be inactive for the configurable number of minutes, hours, or days before the logoff. To enable the Auto log off timeout option

1 2 3

Select View > Options. Then select the Administration Console tab. Check the Auto log off timeout option. Select the duration after which the user is logged off from an inactive session. The minimum logoff duration is 10 minutes and the maximum is two days. Five minutes before the timeout value is reached, NetBackup warns that the session is to expire in five minutes.

If the logoff warning appears, the user can choose one of the following options:

Ignore If the user selects this option (or does not respond to the warning), a dialog box displays the time that remains before the session ends. Countdown warnings display every minute until the timeout value is reached. When the session ends, the user is logged out of the NetBackup Administration Console or the Backup, Archive, and Restore client console. Extend If the user selects this option, the session continues and the timeout extends by the logoff timeout value. If the user begins to work at the console again, the logoff is canceled until the console is left idle again. Log off If the user selects this option, the session ends and NetBackup logs off the user immediately.

Lotus Notes properties

The Lotus Notes properties apply to the clients that are currently selected and that run NetBackup for Lotus Notes. For more information, see the NetBackup for Lotus Notes Administrators Guide.

Configuring Host Properties Lotus Notes properties

159

Figure 3-38

Lotus Notes dialog box

The following properties can be configured in the NetBackup Administration Console, the bp.conf or the Windows registry. For UNIX or Linux servers: If you have multiple installations of Domino server, the values in the client properties or the bp.conf only apply to one installation. For other installations, specify the installation path and location of the notes.ini file with the LOTUS_INSTALL_PATH and NOTES_INI_PATH directives in the backup policy. Table 3-46 Client host properties Lotus Notes client host properties Description

Windows registry and bp.conf entries

Maximum LOTUS_NOTES_LOGCACHESIZE The maximum number of logs that can be prefetched in a single number of restore job during recovery. Specify a value greater than 1. In the Windows registry, this value logs to restore is a DWORD value. If this value is less than or equal to 1, NetBackup does not gather transaction logs during recovery. One transaction log extent per job is restored to the Domino servers log directory. LOTUS_NOTES_LOGCACHESIZE = 3

160

Configuring Host Properties Lotus Notes properties

Table 3-46 Client host properties

Lotus Notes client host properties (continued) Description

Windows registry and bp.conf entries

Transaction LOTUS_NOTES_LOGCACHEPATH Specify a path where NetBackup can temporarily store the log cache path prefetched transaction logs during recovery. In the Windows registry, this value For example: is a string value.

UNIX: /tmp/logcache Windows: D:\LogCache

If you do not specify a path, during recovery NetBackup restores the logs to the Domino server's transaction log directory. Note the following before specifying the Transaction log cache path:

If the specified path does not exist then it is created during restore. The restore job fails with a Status 5 error if the user does not have write permission for the folder. Transaction logs are restored to the original location, the Domino transaction log directory, if a path is not specified. If the value of Maximum number of logs to restore is less than or equal to 1 then this path is ignored. The logs are not prefetched; one transaction log per job is restored to the Domino Servers log directory. If there is not sufficient space to restore the specified number of logs, NetBackup tries to restore only the number of logs that can be accommodated.

INI path

LOTUS_NOTES_INI

Enter the NOTES.INI file that is associated with the server used to back up and restore the Lotus database. Use this setting to In the Windows registry, this value specify the correct .INI file to back up and restore from Domino is a string value. partitioned servers. Specifying the .INI file for non-partitioned servers is not necessary. Specify the absolute path to the NOTES.INI file:

Windows: If the notes.ini file is not located in the default directory, indicate its location in the INI path box. For example: D:\Lotus\Domino\notes.ini UNIX: If the notes.ini is not located in the directory that is specified in the Path, indicate its location here. For example: /db/notesdata/notes.ini Include the directory and the notes.ini file name.

Configuring Host Properties Media properties

161

Table 3-46 Client host properties

Path

Lotus Notes client host properties (continued) Description

Windows registry and bp.conf entries

LOTUS_NOTES_PATH

Specify the path where the Lotus Notes program files reside on the client. NetBackup must know where these files are to In the Windows registry, this value perform backup and restore operations. The value in this box is a string value. overrides the Lotus registry key, if both are defined. Specify the path where the Lotus Notes program files reside on the client:

Windows: Specify the path for Lotus program directory (where nserver.exe resides). For example: D:\Lotus\Domino UNIX: Specify a path that includes the Domino data directory, the Lotus program directory, and the Lotus resource directory. For example: /export/home/notesdata:/opt/lotus/notes/latest /sunspa:/opt/lotus/notes/latest/sunspa/res/C

The Path value overrides the Lotus registry value, if both are defined.

Media properties
The Media properties apply to the master servers and media servers that are currently selected. Media properties control how NetBackup manages media.

162

Configuring Host Properties Media properties

Figure 3-39

Media dialog box

The Media dialog box contains the following properties.

Configuring Host Properties Media properties

163

Table 3-47 Property

Allow media overwrite property

Media dialog box properties

Description
This property overrides the NetBackup overwrite protection for specific media types. Normally, NetBackup does not overwrite certain media types. To disable overwrite protection, place a check in the check box of one or more of the listed media formats. For example, place a check in the CPIO check box to permit NetBackup to overwrite the cpio format. By default, NetBackup does not overwrite any of the formats on removable media, and logs an error if an overwrite attempt occurs. This format recognition requires that the first variable length block on a media be less than or equal to 32 kilobytes. The following media formats on removable media can be selected to be overwritten:

When ANSI is enabled, ANSI labeled media can be overwritten.

When AOS/VS is enabled, AOS/VS media can be overwritten. (Data General AOS/VS backup format.) When CPIO is enabled, CPIO media can be overwritten. When DBR is enabled, DBR media can be overwritten. (The DBR backup format is no longer used.) Remote Storage MTF1 media format. When MTF1 is enabled, Remote Storage MTF1 media format can be overwritten. When TAR is enabled, TAR media can be overwritten.

When MTF is enabled, MTF media can be overwritten. With only MTF checked, all other MTF formats can be overwritten. (The exception is Backup Exec MTF (BE-MTF1) and Remote Storage MTF (RS-MTF1) media formats, which are not overwritten. When BE-MTF1 is enabled, Backup Exec MTF media can be overwritten.

See Results when media overwrites are not permitted on page 166.

164

Configuring Host Properties Media properties

Table 3-47 Property

Enable SCSI reserve

Media dialog box properties (continued)

Description
This property allows exclusive access protection for tape drives. With access protection, other host bus adaptors cannot issue commands to control the drives during the reservation. SCSI reservations provide protection for NetBackup Shared Storage Option environments or any other multiple-initiator environment in which drives are shared. The protection setting configures access protection for all tape drives from the media server on which the option is configured. You can override the media server setting for any drive path from that media server. See Recommended use for Enable SCSI reserve property on page 167. See Drive path options on page 266. The following are the protection options: The SCSI persistent reserve option provides SCSI persistent reserve protection for SCSI devices. The devices must conform to the SCSI Primary Commands - 3 (SPC-3) standard. SCSI persistent reserve is valid for NetBackup 6.5 and later servers only. If you enable SCSI persistent reserve, NetBackup does not send persistent reserve commands to NetBackup media servers earlier than release 6.5. The SPC-2 SCSI reserve option (default) provides SPC-2 SCSI reserve protection for SCSI devices. The devices must conform to the reserve and release management method in the SCSI Primary Commands - 2 standard. To operate NetBackup without tape drive access protection, clear the Enable SCSI reserve property. If unchecked, other HBAs can send the commands that may cause a loss of data to tape drives.

Note: Ensure that all of your hardware processes SCSI persistent reserve commands
correctly. All of your hardware includes Fibre Channel bridges. If the hardware does not process SCSI persistent reserve commands correctly and NetBackup is configured to use SCSI persistent reserve, no protection may exist. Allow multiple retentions per media This property allows NetBackup to mix retention levels on tape volumes. It applies to media in both robotic drives and nonrobotic drives. The default is that the check box is clear and each volume can contain backups of only a single retention level.

Allow backups to span tape This property, when checked, allows backups to span to multiple tape media. This media property allows NetBackup to select another volume to begin the next fragment. The resulting backup has data fragments on more than one volume. The default is that Allow backups to span tape media is checked and backups are allowed to span media. If the end of media is encountered and this property is not selected, the media is set to FULL and the operation terminates abnormally. This action applies to both robotic drives and nonrobotic drives.

Configuring Host Properties Media properties

165

Table 3-47 Property Description

Media dialog box properties (continued)

Allow backups to span disk This property allows backups to span disk volumes when one disk volume becomes full. The default is that this property is enabled. The Allow backups to span disk property does not apply to AdvancedDisk or OpenStorage storage units. Backups span disk volumes within disk pools automatically. The following destinations support disk spanning: A BasicDisk storage unit spanning to a BasicDisk storage unit. The units must be within a storage unit group. An OpenStorage or AdvancedDisk volume spanning to another volume in the disk pool.

For disk spanning to occur, the following conditions must be met:

The storage units must share the same media server.

The multiplexing level on spanning storage units should be the same. If there are any differences, the level on the target unit can be higher. See Enable multiplexing storage unit setting on page 415. A disk staging storage unit cannot span to another storage unit. Also, a disk staging storage unit is not eligible as a target for disk spanning. Disk spanning is not supported on NFS. Enable standalone drive extension This property allows NetBackup to use whatever labeled or unlabeled media is found in a nonrobotic drive. The default is that the Enable standalone drive extension property is enabled. This property allows the logging of the job information. This logging is the same information that the NetBackup Activity Monitor uses. The default is that job logging occurs.

Enable job logging

Enable unrestricted media This property controls media sharing, as follows: sharing for all media servers Enable this property to allow all NetBackup media servers and NDMP hosts in the NetBackup environment to share media for writing. Do not configure server groups for media sharing. Clear this property to restrict media sharing to specific server groups. Then configure media server groups and backup policies to use media sharing. Clear this property to disable media sharing. Do not configure media server groups. The default is that media sharing is disabled. (The property is cleared and no server groups are configured.) See About server groups on page 223.

166

Configuring Host Properties Media properties

Table 3-47 Property

Media ID prefix (non-robotic)

Media dialog box properties (continued)

Description
This property specifies the media ID prefix to use in media IDs when the unlabeled media is in nonrobotic drives. The prefix must be one to three alpha-numeric characters. NetBackup appends numeric characters. By default, NetBackup uses A and assigns media IDs such as A00000, A00001, and so on. For example, if FEB is specified, NetBackup appends the remaining numeric characters. The assigned media IDs become FEB000, FEB001, and so on. (Note that this numbering does not work with the Configure Volumes wizard).

Media unmount delay

To specify a Media unmount delay property indicates that the unloading of media is delayed after the requested operation is complete. Media unmount delay applies only to user operations, to include backups and restores of database agent clients, such as those running NetBackup for Oracle. The delay reduces unnecessary media unmounts and the positioning of media in cases where the media is requested again a short time later. The delay can range from 0 seconds to 1800 seconds. The default is 180 seconds. If you specify 0, the media unmount occurs immediately upon completion of the requested operation. Values greater than 1800 are set to 1800.

Media request delay

This property specifies how long NetBackup waits for media in nonrobotic drives. A configurable delay is useful if a gravity feed stacker is used on a nonrobotic drive. A delay often exists between dismounting one media and mounting another. The default is 0 seconds. During the delay period, NetBackup checks every 60 seconds to see if the drive is ready. If the drive is ready, NetBackup uses it. Otherwise, NetBackup waits another 60 seconds and checks again. If the total delay is not a multiple of 60, the last wait is the remainder. If the delay is less than 60 seconds, NetBackup checks after the end of the delay. For example, set the delay to 150 seconds. NetBackup waits 60 seconds, checks for ready, waits 60 seconds, checks for ready, waits 30 seconds, and checks for ready the last time. If the delay was 50 seconds (a short delay is not recommended), NetBackup checks after 50 seconds.

Results when media overwrites are not permitted

If media contains one of the protected formats and media overwrites are not permitted, NetBackup takes the following actions:
If the volume has not been previously assigned for a backup

Sets the volumes state to FROZEN Selects a different volume Logs an error

Configuring Host Properties Media properties

167

If the volume is in the NetBackup media catalog and was previously selected for backups

Sets the volumes state to SUSPENDED Aborts the requested backup Logs an error

If the volume is mounted for a backup of the The backup is aborted and an error is logged. NetBackup catalog The error indicates the volume cannot be overwritten. If the volume is mounted to restore files or list the media contents NetBackup aborts the request and logs an error. The error indicates that the volume does not have a NetBackup format.

Recommended use for Enable SCSI reserve property

All tape drive and bridge vendors support the SPC-2 SCSI reserve and release method. NetBackup has used SPC-2 SCSI reserve since NetBackup 3.4.3, and it is the default tape drive reservation method in NetBackup. SPC-2 SCSI reserve is effective for most NetBackup environments. The SCSI persistent reserve method provides device status and correction and may be more effective in the following environments:

Where NetBackup media servers operate in a cluster environment. NetBackup can recover and use a reserved drive after a failover (if NetBackup owns the reservation). (With SPC-2 SCSI reserve, the drive must usually be reset because the reservation owner is inoperative.) Where the drive has high availability. NetBackup can resolve NetBackup drive reservation conflicts and maintain high drive availability. (SPC-2 SCSI reserve provides no method for drive status detection.)

However, the SCSI persistent reserve method is not supported or not supported correctly by all device vendors. Therefore, thoroughly analyze the environment to ensure that all of the hardware supports SCSI persistent reserve correctly. Symantec recommends careful consideration of all of the following factors before Enable SCSI reserve is used:

Only a limited number of tape drive vendors support SCSI persistent reserve. SCSI persistent reserve is not supported or not supported correctly by all Fibre Channel bridge vendors. Incorrect support in a bridge means no access protection. Therefore, if the environment uses bridges, do not use SCSI persistent reserve. If parallel SCSI buses are used, carefully consider the use of SCSI persistent reserve. Usually, parallel drives are not shared, so SCSI persistent reserve

168

Configuring Host Properties NDMP Global Credentials properties

protection is not required. Also, parallel drives are usually on a bridge, and bridges do not support SCSI persistent reserve correctly. Therefore, if the environment uses parallel SCSI buses, do not use SCSI persistent reserve.

The operating system tape drivers may require extensive configuration to use SCSI persistent reserve. For example, if the tape drives do not support SPC-3 Compatible Reservation Handling (CRH), ensure that the operating system does not issue SPC-2 reserve and release commands.

If any of the hardware does not support SCSI persistent reserve, Symantec recommends that SCSI persistent reserve is not used.

NDMP Global Credentials properties

The credentials that are entered for NDMP Global Credentials can apply to any NDMP host in the configuration. However, the Use global NDMP credentials for this NDMP host option must be selected in the Add NDMP Host dialog box for the NDMP host. Figure 3-40 NDMP Global Credentials dialog box

The NDMP Global Credentials properties dialog box contains the following properties.

Configuring Host Properties NetWare Client properties

169

Table 3-48 Property

User name

NDMP Global Credentials dialog box properties

Description
The user name under which NetBackup accesses the NDMP server. This user must have permission to run NDMP commands. Enter the password. Re-enter the password.

Password Confirm password

To access the Add NDMP Host dialog box, add an NDMP host under Media and Device Management > Credentials > NDMP Hosts. Figure 3-41 shows the Add NDMP Host dialog box. In the Credentials section, select Use global NDMP credentials for this NDMP host so that the NDMP Global Credentials apply to that host. Figure 3-41 Add NDMP Host dialog box

For NDMP Global Credentials to apply, this must be selected on the NDMP host as well

NetWare Client properties

The Netware Client properties define NetBackup properties of NetWare clients. Netware Client properties include the Client Settings for NetWare clients as a subnode:

170

Configuring Host Properties Network properties

See Client Settings properties for NetWare clients on page 94.

Network properties
Use the Network properties to set the properties that define requirements for communications between clients and the master server. The Network properties apply to currently selected Windows clients. Figure 3-42 Network dialog box

The Network dialog box contains the following properties. Table 3-49 Property
NetBackup client service port (BPCD)

Network dialog box properties

Description
This property specifies the port that the NetBackup client uses to communicate with the NetBackup server. The default is 13782.

Note: If you change this port number, remember that it must be the same for all
NetBackup servers and clients that communicate with one another.

Configuring Host Properties Network Settings Properties

171

Table 3-49 Property Description

Network dialog box properties (continued)

NetBackup request service This property specifies the port for the client to use when it sends requests to the port (BPRD) NetBackup request service (bprd process) on the NetBackup server. The default is 13720.

Note: If you change this port number, remember that it must be the same for all
NetBackup servers and clients that communicate with one another. Announce DHCP interval This property specifies how many minutes the client waits before it announces that a different IP address is to be used. The announcement occurs only if the specified time period has elapsed and the address has changed since the last time the client announced it.

Network Settings Properties

The Network Settings host properties apply to master servers, media servers, and clients. Figure 3-43 Network Settings dialog box

The Network Settings dialog box contains properties for Reverse Host Name Lookup and IP Address Family Support.

172

Configuring Host Properties Network Settings Properties

Reverse Host Name Lookup property

The domain name system (DNS) reverse host name lookup is used to determine what host and domain name a given IP address indicates. Some administrators cannot or do not want to configure the DNS server for reverse host name lookup. For these environments, NetBackup offers the Reverse Host Name Lookup property to allow, restrict, or prohibit reverse host name lookup. Administrators can configure the Reverse Host Name Lookup property for each host. Table 3-50 Property
Allowed setting

Reverse Host Name Lookup property settings

Description
The Allowed property indicates that the host requires reverse host name lookup to work to determine that the connection comes from a recognizable server. By default, the host resolves the IP address of the connecting server to a host name by performing a reverse lookup. If the conversion of the IP address to host name fails, the connection fails. Otherwise, it compares the host name to the list of known server host names. If the comparison fails, the host rejects the server and the connection fails.

Restricted setting

The Restricted property indicates that the NetBackup host first attempts to perform reverse host name lookup. If the NetBackup host successfully resolves the IP address of the connecting server to a host name (reverse lookup is successful), it compares the host name to the list of known server host names. If the resolution of the IP address to a host name fails (reverse lookup fails), based on the Restricted setting, the host converts the host names of the known server list to IP addresses (using a forward lookup). The host compares the IP address of the connecting server to the list of known server IP addresses. If the comparison fails, the host rejects the connection from server and the connection fails.

Prohibited setting

The Prohibited property indicates that the NetBackup host does not try reverse host name lookup at all. The host resolves the host names of the known server list to IP addresses using forward lookups. The NetBackup host then compares the IP address of the connecting server to the list of known server IP addresses. If the comparison fails, the NetBackup host rejects the connection from the server and the connection fails.

Configuring Host Properties Network Settings Properties

173

Reverse Host Name Lookup changes outside of the Administration Console

In some cases, a master server may not be able to view the host properties of a media server or client in the NetBackup Administration Console. The NetBackup customer's DNS reverse host name lookup configuration may be one possible reason why the host properties may not be visible. In this case, since changing the NetBackup Reverse Host Name Lookup host property involves being able to view the host properties, youll need to use another method to change it. Add the REVERSE_NAME_LOOKUP entry to the bp.conf file (UNIX) or to the Windows registry. The REVERSE_NAME_LOOKUP entry uses the following format:
REVERSE_NAME_LOOKUP = ALLOWED | RESTRICTED | PROHIBITED

For example:
REVERSE_NAME_LOOKUP = PROHIBITED

The values of ALLOWED, RESTRICTED, and PROHIBITED represent the same meaning as the values in the Network Settings host properties.

Setting the REVERSE_NAME_LOOKUP property on UNIX hosts

To set the Reverse Host Name Lookup property on a UNIX system outside of the NetBackup Administration Console, manually add the REVERSE_NAME_LOOKUP entry to the bp.conf file on the master server, media server, or client. To set the REVERSE_NAME_LOOKUP property on UNIX hosts, use one of the following methods:

On master and media servers Use the bpsetconfig command to add the entry. The bpsetconfig command is described in the NetBackup Commands Reference Guide. On UNIX clients Edit the bp.conf directly to add the entry.

Setting the REVERSE_NAME_LOOKUP property on Windows hosts

On master and media servers, the bpsetconfig command is available to add the REVERSE_NAME_LOOKUP entry to the registry. The bpsetconfig command is described in the NetBackup Commands Reference Guide. To set the Reverse Host Name Lookup property on a Windows client, add the REVERSE_NAME_LOOKUP entry to the registry using the following method.

174

Configuring Host Properties Network Settings Properties

To set the Reverse Host Name Lookup property on a Windows client

1 2

From the command line, run regedit to open the registry editor. Navigate to the following key directory:
My Computer/HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\ NetBackup\CurrentVersion\Config

3 4 5 6

On the Edit menu, click New > String Value. Name the String Value: REVERSE_NAME_LOOKUP. Give REVERSE_NAME_LOOKUP the value data of either PROHIBITED, RESTRICTED, or ALLOWED. Click OK and close the registry editor .

IP Address Family Support property

On hosts that use both IPv4 and IPv6 addresses, use the IP Address Family Support property to indicate which address family to use:

IPv4 only (Default) Both IPv4 and IPv6

Upon installation or upgrade to NetBackup version 7.1, NetBackup defaults to IPv4. If any of the master servers do not support IPv4, NetBackup uses the configuration that supports both IPv4 and IPv6. While the IP Address Family Support property controls how hostnames are resolved to IP addresses, the Preferred Network properties control how NetBackup uses the addresses.

Configuring Host Properties Port Ranges properties

175

See Preferred Network properties on page 176.

Port Ranges properties

Use the Port Ranges properties in the NetBackup Administration Console to determine how hosts connect to one another. These properties apply to selected master servers, media servers, and clients. Figure 3-44 Port Ranges dialog box

The Port Ranges dialog box contains the following properties. Table 3-51 Property
Use random port assignments

Port Ranges dialog box properties

Description
Specifies how the selected computer chooses a port when it communicates with NetBackup on other computers. Enable this property to let NetBackup randomly select ports from those that are free in the allowed range. For example, if the range is from 1023 through 5000, it chooses randomly from the numbers in this range. If this property is not enabled, NetBackup chooses numbers sequentially, not randomly. NetBackup starts with the highest number that is available in the allowed range. For example, if the range is from 1023 through 5000, NetBackup chooses 5000. If 5000 is in use, port 4999 is chosen. This property is enabled by default.

176

Configuring Host Properties Preferred Network properties

Table 3-51 Property

Client port window

Port Ranges dialog box properties (continued)

Description
Lets the administrator define the range of non-reserved ports on the selected computer. NetBackup can use any available port within this range to communicate with NetBackup on another computer. Lets the operating system determine which non-reserved port to use.

Use OS selected non reserved port

Client reserved port window This property no longer applies to NetBackup 7.0.1 and later. For information about this property, refer to documentation from a previous release. Server port window This property no longer applies to NetBackup 7.0.1 and later. For information about this property, refer to documentation from a previous release. This property no longer applies NetBackup 7.0.1 and later. For information about this property, refer to documentation from a previous release.

Server reserved port window

Registered ports and dynamically-allocated ports

NetBackup communicates between computers by using a combination of registered ports and dynamically-allocated ports.
Registered ports These ports are registered with the Internet Assigned Numbers Authority (IANA) and are permanently assigned to specific NetBackup services. For example, the port for the NetBackup client service (bpcd) is 13782. The following system configuration file can be used to override the default port numbers for each port: %systemroot%\system32\drivers\etc\services

Dynamically-allocated ports These ports are assigned as needed, from configurable ranges in the Port Ranges host properties for NetBackup servers and clients. In addition to the range of numbers, you can specify whether NetBackup selects a port number at random or starts at the top of the range and uses the first one available.

Preferred Network properties

Use the Preferred Network properties in the NetBackup Administration Console to specify to NetBackup which networks or interfaces to use for outgoing

Configuring Host Properties Preferred Network properties

177

NetBackup traffic from the selected hosts. These properties apply to currently selected master servers, media servers, and clients. The Preferred Network properties are useful in NetBackup environments that include multihomed hoststhe hosts that are connected to two or more networks, or hosts that have two or more network addresses. The properties are especially helpful to administrators who must configure an environment that includes both Internet Protocol version 6 (IPv6) and IPv4 address families. The Preferred Network properties compare to the Use specified network interface property in the Universal Settings properties. However, the Use specified network interface property can be used to specify only a single interface for NetBackup to use for outbound calls. The Preferred Network properties were introduced so that administrators can give more elaborate and constrictive instructions that apply to multiple individual networks, or a range of networks. For example, an administrator can configure a host to use any network except one. Note: Do not inadvertently configure hosts so that they cannot communicate with any other host. Use the bptestnetconn utility to determine whether the hosts can communicate as you intend. See bptestnetconn utility to display Preferred Network information on page 186. Figure 3-45 Preferred Network dialog box

The Preferred Network dialog box contains a list of networks and the directive that has been configured for each.

178

Configuring Host Properties Preferred Network properties

Table 3-52 Property

List of network specifications for NetBackup communications

Preferred Network dialog box properties

Description
The list of preferred networks contains the following information: The Target column lists the networks (or hostnames or IP addresses) that have been given specific directives. If a network is not specifically listed as a target, or if a range of addresses does not include the target, NetBackup considers the target to be available for selection. Note that if the same network considerations apply for all of the hosts, the list of directives can be identical across all hosts in the NetBackup environment. If a directive contains an address that does not apply to a particular host, that host ignores it. For example, an IPv4-only host ignores IPv6 directives, and IPv6-only hosts ignore IPv4 directives. This lets the administrator use the same Preferred Network configurations for all the hosts in the NetBackup environment. The Specified as column indicates the directive for the network: Match, Prohibited, or Only. The Source column lists source binding information to use to filter addresses. The Source property is an optional configuration property.

Ordering arrows

Select a network in the list, then click the up or down arrow to change the order of the network in the list. The order can affect which network NetBackup selects. See Order of directive processing in the Preferred Network properties on page 185.

Add

Click Add to add a network to the Preferred Network properties. The directive for the network is configured in the Add Preferred Network Settings dialog box. See Table 3-53 on page 179.

Add to all Change

The Add to all button is active when multiple servers are selected. Select a network in the list, then click Change to change the Preferred Network properties. The directive is changed in the Change Preferred Network Settings dialog box. See Add or Change Preferred Network Settings dialog box on page 178.

Remove

Select a network in the list, then click Remove to remove the network from the list of preferred networks.

Add or Change Preferred Network Settings dialog box

The Add Preferred Network Settings dialog box contains the following properties.

Configuring Host Properties Preferred Network properties

179

Table 3-53 Property

Target

Add or Change Preferred Network Settings dialog box properties

Description
Enter a network address or a hostname:

If an address is specified as the network, it is usually considered a remote or target address. NetBackup recognizes the following wildcard entries as addresses: 0.0.0.0

Matches any IPv4 address. 0::0 Matches any IPv6 address. 0/0< />

Matches the address of any family. If a hostname is specified as the network, then the address that is used is the first returned by the DNS resolver.

Note: Do not use the following malformed entries as wildcards: 0/32, 0/64, or 0/128. The left
side of the slash must be a legitimate IP address. However, 0/0 may be used, as listed. Match The Match directive indicates that the specified network, address, or hostname is preferred for communication with the selected host. The Match directive does not reject other networks, addresses, or hostnames from being selected, even if they do not match. (The Only directive rejects unsuitable targets if they do not match.) The Match directive is useful following a Prohibited or a Only directive. When used with other directives, Match indicates to NetBackup to stop rule processing because a suitable match has been found. The Match directive can be used with the Source property to indicate source binding. Prohibited Use the Prohibited directive to exclude or prevent the specified network, address, or hostname from being considered. In a list of DNS addresses, addresses in these networks are avoided. The Only directive indicates that the specified network, address, or hostname that is used for communication with the selected host must be in the specified network. Use the Only directive to prevent any network from being considered other than those specified as Only. This directive replaces the REQUIRED_NETWORK entry in the bp.conf file or registry. The Only directive can be used with the Source property to indicate source binding.

Only

180

Configuring Host Properties Preferred Network properties

Table 3-53

Add or Change Preferred Network Settings dialog box properties (continued)

Property
Source

Description
Use this property with the Match or the Only directives to describe the local hostname, IP addresses, or networks that may be used for source binding. NetBackup matches the desired source interfaces, (backup networks, for example) with the target addresses described by the Source property. The corresponding bp.conf or registry entry for this property is PREFERRED_NETWORK. This property replaces the REQUIRED_INTERFACE entry.

How NetBackup uses the directives to determine which network to use

Each host has an internal table of preferred network rules that NetBackup consults before it selects a network interface to use for communication with another host. The table includes every interface-IP address combination available to the selected host. Based on the Preferred NetBackup directives, the table indicates to NetBackup whether or not the host is allowed to use a given network. This topic uses the example of two multihomed servers (Server_A and Server_B) as shown in Figure 3-46. Server A is considering which addresses it can use to access Server_B, given the Preferred Network directives configured on Server_A. When Preferred Network directives are used to place restrictions on targets, they are added from the perspective of the server making the connection. The directives on Server_A affect its preferences as to which Server_B addresses it can use.

Configuring Host Properties Preferred Network properties

181

Figure 3-46

Multihomed servers example

Server_A Directives on Server_A indicate what interfaces it can use to access Server_B

Backup interface 2001:db8:0:11d::1efc Production interface 10.81.73.147 2001:db8:0:1f0::1efc

Backup interface 2001:db8:0:11e::1efc 2001:db8:0:11c::1efc Server_B Backup interface 10.96.73.253

Figure 3-47 shows a table for Server_B. Server_B has multiple network interfaces, some of which have multiple IP addresses. In the table, yes indicates that NetBackup can use the network-IP combination as a source. In this example, no directives have been created for the host. Since no networks are listed in the Preferred Network properties, any network-IP combinations can be used for communication. Note: The following topic shows the bptestnetconn output for this example configuration: See Figure 3-54 on page 187.

182

Configuring Host Properties Preferred Network properties

Figure 3-47

From Server_A's perspective: Available IP addresses on Server_B when no directives are indicated on Server_A
IP addresses IPv4 IPv6 Yes --Yes Yes Yes ---

2001:0db8:0:1f0::1efc Network interfaces 10.80.73.147 2001:0db8:0:11c::1efc 2001:0db8:0:11d::1efc 2001:0db8:0:11e::1efc 10.96.73.253

--Yes ------Yes

Figure 3-48 shows a table for the same host (Server_B). Now, the Preferred Network properties are configured so that all IPv4 addresses are excluded from selection consideration by NetBackup. All NetBackup traffic is to use only IPv6 addresses. Figure 3-48 From Server_A's perspective: Available IP addresses on Server_B when directives to use IPv6 addresses only are indicated on Server_A
IP addresses IPv4 2001:0db8:0:1f0::1efc Network interfaces 10.80.73.147 2001:0db8:0:11c::1efc 2001:0db8:0:11d::1efc 2001:0db8:0:11e::1efc 10.96.73.253 --No ------No IPv6 Yes --Yes Yes Yes ---

The following topics describe various configurations:

See Configurations to use IPv6 networks on page 183. See Configurations to use IPv4 networks on page 184. See Configuration to prohibit using a specified address on page 188. See Configuration that uses the same specification for both the network and the interfaceless constrictive on page 188.

Configuring Host Properties Preferred Network properties

183

See Configuration that uses the same specification for both the network and the interfacemore constrictive on page 189. See Configuration that limits the addresses, but allows any interfaces on page 190.

Configurations to use IPv6 networks

The following Preferred Network configurations instruct NetBackup to use only IPv6 addresses as targets in outbound calls for the currently selected hosts. The configurations satisfy a topology where all backup traffic uses an IPv6 network and other traffic uses other networks. One configuration uses the Prohibited directive (Figure 3-49) and one configuration uses the Match directive (Figure 3-50). The more efficient method to specify one address family, (IPv6, in this case), is to prohibit IPv4. The behavior of the Match directive is not as exclusive as Prohibited. In this case, Match may not necessarily exclude other address families. Figure 3-49 uses the Prohibited directive with a wildcard to indicate to NetBackup to not consider using any IPv4 addresses. In this situation, NetBackup must use an IPv6 address. Note: The default configuration is for NetBackup to use only IPv4 addresses. Creating a directive that prohibits all IPv4 addresses renders the server mute unless you have IPv6 addresses and have them enabled. See IP Address Family Support property on page 174. Figure 3-49 Prohibit IPv4 addresses as targets

Figure 3-50 uses the Match directive with a wildcard to indicate to NetBackup to consider only IPv6 addresses. In this case, NetBackup tries to use an IPv6 address, but may consider IPv4 addresses if necessary.

184

Configuring Host Properties Preferred Network properties

Figure 3-50

Match IPv6 addresses as targets

Figure 3-51 shows another configuration that allows NetBackup to choose from multiple IPv6 networks. Given the multihomed example configuration, the directive indicates the following:

Four IPv6 networks, from fec0:0:0:fe04 to fec0:0:0:fe07, are described as targets. For all addresses in these networks, a source binding address that is derived from the IP addresses of hostname host_fred is used.

See How NetBackup uses the directives to determine which network to use on page 180. Figure 3-51 Indicating a range of IPv6 networks

Configurations to use IPv4 networks

The following Preferred Network configurations instruct NetBackup to use only IPv4 addresses as targets in outbound calls for the currently selected hosts. The configurations satisfy a topology where all backup traffic uses an IPv4 network and other traffic uses other networks. One configuration uses the Prohibited directive (Figure 3-52) and one configuration uses the Match directive (Figure 3-53).

Configuring Host Properties Preferred Network properties

185

The more efficient method to specify one address family, (IPv4, in this case), is to prohibit IPv6. The behavior of the Match directive is not as exclusive as Prohibited. In this case, Match may not necessarily exclude other address families. Figure 3-52 uses the Prohibited directive with a wildcard to indicate to NetBackup to not consider using any IPv6 addresses. In this situation, NetBackup must use an IPv4 address. Figure 3-52 Prohibit IPv6 addresses as targets

Figure 3-53 uses the Match directive with a wildcard to indicate to NetBackup to consider only IPv4 addresses. In this case, NetBackup tries to use an IPv4 address, but may consider IPv6 addresses if necessary. Figure 3-53 Match IPv4 addresses as targets

Order of directive processing in the Preferred Network properties

NetBackup sorts all directives into decreasing order by subnet size so that the more specific network specifications, such as complete hostnames or IP addresses, match first. (For example, a /24 subnet matches before a /16 subnet.) In this way, NetBackup can honor host-specific overrides. If NetBackup considers the directives of multiple networks to be equal in specificity (a tie), NetBackup looks at the order in which the networks are listed. See Order of directives can affect processing on page 186.

186

Configuring Host Properties Preferred Network properties

NetBackup processes each resolved address in the network list according to specific rules. Directives that contain addresses that do not apply to the host are ignored. Table 3-54 describes how NetBackup determines whether an address can be used for communication. Table 3-54 Step
1

Order of directive processing Target is selected or processing continues

NetBackup considers the target

If the target is not a match for the directive, and ...then the target is treated as Prohibited, and processing stops for that target. if the directive is an Only directive... NetBackup considers the next target.

If the target is a match for the directive, and if the directive is a Prohibited directive...

...then the target is treated as Prohibited and processing stops for that target. NetBackup considers the next target.

If the target is not a match...

...then the processing continues. NetBackup considers the next directive in the list.

If the target is a match...

...then the directive is either Only or Match and further directive processing stops. An Only match is treated like a Match in terms of source binding computation. If no rules ever match, then the target is allowed, and no source binding is enforced.

Order of directives can affect processing

The order of the networks in the list can affect which network NetBackup selects for communication for the selected hosts. The strongest filters are Prohibited and Only. Use the up or down arrows to the right of the list to change the order of the networks.

bptestnetconn utility to display Preferred Network information

The bptestnetconn utility is available to administrators to test and analyze host connections. Use the preferred network option (--prefnet) to display information about the preferred network configuration along with the forward lookup information of a host on the server list.

Configuring Host Properties Preferred Network properties

187

The bptestnetconn command is described in the NetBackup Commands Reference Guide. Figure 3-54 shows the bptestnetconn output when run on Server_A, for Server_B. That is, bptestnetconn is run from Server_A's perspective. Based on the directives configured on Server_A, for Server_B, bptestnetconn shows the available IP addresses on Server_B. In this example, no directives are configured on Server_A. Figure 3-54 bptestnetconn for Server_B with no directives listed

[root@Server_A netbackup]# bptestnetconn -f --prefnet -H Server_B --------------------------------------------------------------------FL: Server_B -> 10.81.73.147 : 11 ms SRC: ANY FL: Server_B -> 10.96.73.253 : 11 ms SRC: ANY FL: Server_B -> 2001:db8:0:11d::1efc : 11 ms SRC: ANY FL: Server_B -> 2001:db8:0:11e::1efc : 11 ms SRC: ANY FL: Server_B -> 2001:d8b:0:1f0::1efc : 11 ms SRC: ANY FL: Server_B -> 2001:db8:0:11c::1efc : 11 ms SRC: ANY --------------------------------------------------------------------Total elapsed time: 0 sec Host for which lookup is performed List of networks available to Server_B Any source is available to use for a connection

The following directive is added to the Preferred Networks properties on Server_B:

In the bp.conf file or the registry, the directive appears as follows:

PREFERRED_NETWORK = 2001:0db8:0:11c::/62 ONLY

This directive provides NetBackup with the information to filter the addresses and choose to communicate with only those that match the :11c, :11d, :11e, and :11f networks. The addresses that do not match the Only directive are prohibited, as shown in the bptestnetconn output. Figure 3-55 shows the bptestnetconn output for Server_B, given this directive.

188

Configuring Host Properties Preferred Network properties

Figure 3-55

bptestnetconn for Server_B with directive

[root@Server_A netbackup]# bptestnetconn -f --prefnet -H Server_B --------------------------------------------------------------------FL: Server_B -> 10.81.73.147 : 11 ms TGT PROHIBITED FL: Server_B -> 10.96.73.253 : 11 ms TGT PROHIBITED FL: Server_B -> 2001:db8:0:11d::1efc : 11 ms SRC: ANY FL: Server_B -> 2001:db8:0:11e::1efc : 11 ms SRC: ANY FL: Server_B -> 2001:d8b:0:1f0::1efc : 11 ms TGT PROHIBITED FL: Server_B -> 2001:db8:0:11c::1efc : 11 ms SRC: ANY --------------------------------------------------------------------Total elapsed time: 0 sec List of networks available to Server_B Directives make some targets unavailable to Server_B

Configuration to prohibit using a specified address

Figure 3-56 shows a configuration that prohibits NetBackup from using the specified address. Figure 3-56 Prohibited target example

Configuration that uses the same specification for both the network and the interfaceless constrictive
Figure 3-57 shows a configuration that uses the same specification for both the network and the interface. For all target addresses in the specified network, a source binding in the same network is selected. This directive is considered generic since the identical directive applies to all NetBackup hosts on the network. The closest preferred source address that matches a remote address is used for source binding. A production network outside this range can then be Prohibited, thereby preferring these addresses from both a remote and source binding perspective.

Configuring Host Properties Preferred Network properties

189

Additional Match directives may be used to indicate additional backup networks that are allowed. Figure 3-57 Match network selection with the source

Configuration that uses the same specification for both the network and the interfacemore constrictive
Figure 3-58 also uses the same specification for both target and source binding, however this example is more restrictive. With the Only property specified, this configuration does not allow multiple backup networks to be specified. Figure 3-58 Only network selection with the same source binding address

A host with the Only directive configured considers only those target addresses in the 192.168.100.0 subnet. Additionally, source binding to the local interface must be done on the 192.168.100.0 subnet. On hosts that have a 192.168.100.0 interface but no :1b0 interface, source binding to the :1f0 interface is the default of the operating system.

190

Configuring Host Properties Resilient Network properties

Configuration that limits the addresses, but allows any interfaces

Figure 3-59 shows a configuration that allows only addresses that start with the specified prefix to be considered. No source binding is specified, so any interface may be used. Figure 3-59 Limiting the addresses, without any source binding

Resilient Network properties

The Resilient Network properties appear for the master server, for media servers, and for clients. For media servers and clients, the Resilient Network properties are read only. When a job runs, the master server updates the media server and the client with the current properties. The Resilient Network properties let you configure NetBackup to use resilient network connections. A resilient connection allows backup and restore traffic between a client and NetBackup media servers to function effectively in high-latency, low-bandwidth networks such as WANs. The use case that benefits the most from a resilient connection is a client in a remote office that backs up its own data (client-side deduplication). The data travels across a wide area network (WAN) to media servers in a central datacenter. NetBackup monitors the socket connections between the remote client and the NetBackup media server. If possible, NetBackup re-establishes dropped connections and resynchronizes the data stream. NetBackup also overcomes latency issues to maintain an unbroken data stream. A resilient connection can survive network interruptions of up to 80 seconds. A resilient connection may survive interruptions longer than 80 seconds. The NetBackup Remote Network Transport Service manages the connection between the computers. The Remote Network Transport Service runs on the master server, the client, and the media server that processes the backup or restore job. If the connection is interrupted or fails, the services attempt to re-establish a connection and synchronize the data. More information about the Remote Network Transport Service is available.

Configuring Host Properties Resilient Network properties

191

Resilient connections apply between clients and NetBackup media servers, which includes master servers when they function as media servers. Resilient connections do not apply to master servers or media servers if they function as clients and back up data to a media server. Resilient connections can apply to all of the clients or to a subset of clients. Note: If a client is in a different subdomain than the server, add the fully qualified domain name of the server to the clients hosts file. For example, india.symantecs.org is a different subdomain than china.symantecs.org. When a backup or restore job for a client starts, NetBackup searches the Resilient Network list from top to bottom looking for the client. If NetBackup finds the client, NetBackup updates the resilient network setting of the client and the media server that runs the job. NetBackup then uses a resilient connection. Figure 3-60 Master server Resilient Network host properties

See About the Services tab on page 843. Table 3-55 describes the Resilient Network properties.

192

Configuring Host Properties Resilient Network properties

Table 3-55 Property

Host Name or IP Address

Resilient Network dialog box properties

Description
The Host Name or IP Address of the host. The address can also be a range of IP addresses so you can configure more than one client at once. You can mix IPv4 addresses and ranges with IPv6 addresses and subnets. If you specify the host by name, Symantec recommends that you use the fully qualified domain name. Use the arrow buttons on the right side of the pane to move up or move down an item in the list of resilient networks.

Resiliency

Resiliency is either ON or OFF.

Note: The order is significant for the items in the list of resilient networks. If a client is in the list more than once, the first match determines its resilient connection status. For example, suppose you add a client and specify the client IP address and specify On for Resiliency. Suppose also that you add a range of IP addresses as Off, and the client IP address is within that range. If the client IP address appears before the address range, the client connection is resilient. Conversely, if the IP range appears first, the client connection is not resilient. The resilient status of each client also appears as follows:

In the NetBackup Administration Console, select NetBackup Management > Policies in the left pane and then select a policy. In the right pane, a Resiliency column shows the status for each client in the policy. In the NetBackup Administration Console, select NetBackup Management > Host Properties > Clients in the left pane. In the right pane, a Resiliency column shows the status for each client.

Other NetBackup properties control the order in which NetBackup uses network addresses. See Preferred Network properties on page 176. The NetBackup resilient connections use the SOCKS protocol version 5. Resilient connection traffic is not encrypted. Symantec recommends that you encrypt your backups. For deduplication backups, use the deduplication-based encryption. For other backups, use policy-based encryption. Resilient connections apply to backup connections. Therefore, no additional network ports or firewall ports must be opened.

Configuring Host Properties Resilient Network properties

193

Resilient connection resource usage

Resilient connections consume more resources than regular connections, as follows:

More socket connections are required per data stream. Three socket connections are required to accommodate the Remote Network Transport Service that runs on both the media server and the client. Only one socket connection is required for a non-resilient connection. More sockets are open on media servers and clients. Three open sockets are required rather than one for a non-resilient connection. The increased number of open sockets may cause issues on busy media servers. More processes run on media servers and clients. Usually, only one more process per host runs even if multiple connections exist. The processing that is required to maintain a resilient connection may reduce performance slightly.

Specifying resilient connections

Use the following procedure to specify resilient connections for NetBackup clients. See Resilient Network properties on page 190. Alternatively, you can use the resilient_clients goodies script to specify resilient connections for clients:
install_path\Veritas\NetBackup\bin\goodies\resilient_clients

To specify resilient connections

1 2 3 4 5

In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers in the left pane. In the right pane, select the host or hosts on which to specify properties. Click Actions > Properties. In the properties dialog box left pane, select Resilient Network. In the Resilient Network dialog box, use the following buttons to manage resiliency:
Add Opens a dialog box in which you can add a host or an address range. If you specify the host by name, Symantec recommends that you use the fully qualified domain name.

194

Configuring Host Properties Resource Limit properties

Add To All

If you select multiple hosts in the NetBackup Administration Console, the entries in the Resilient Network list may appear in different colors, as follows: The entries that appear in black type are configured on all of the hosts. The entries that appear in gray type are configured on some of the hosts only.

For the entries that are configured on some of the hosts only, you can add them to all of the hosts. To do so, select them and click Add To All. Change Opens a dialog box in which you can change the resiliency settings of the select items. Remove the select host or address range. A confirmation dialog box does not appear. Move the selected item or items up or down. The order of the items in the list is significant. See Resilient Network properties on page 190.

Remove

Resource Limit properties

The Resource Limit properties in the NetBackup Administration Console control the number of simultaneous backups that can be performed on a VMware resource type. These settings apply to all policies for the currently selected master server. Note: The Resource Limit dialog applies only to policies that use automatic selection of virtual machines (the policy's Query Builder). If you select virtual machines manually on the Browse for Virtual Machines dialog box, the Resource Limit properties have no effect.

Configuring Host Properties Resource Limit properties

195

Figure 3-61

Resource Limit dialog box

The Resource Limit dialog box contains the following properties. Table 3-56 Property
vCenter

Resource Limit dialog box properties Description

The maximum number of simultaneous backups per vCenter server. The maximum number of simultaneous snapshot operations (create or delete) per vCenter. The maximum number of simultaneous backups per VMware cluster. The maximum number of simultaneous backups per ESX server. The maximum number of simultaneous backups per VMX datastore. The maximum number of simultaneous backups per Datastore.

snapshot

Cluster

ESXserver VMXDatastore

Datastore

196

Configuring Host Properties Restore Failover properties

Table 3-56 Property

DatastoreFolder

Resource Limit dialog box properties (continued) Description

The maximum number of simultaneous backups per datastore folder. The maximum number of simultaneous backups per datastore type.

DatastoreType

VMXDatastoreNFSHost The maximum number of simultaneous backups per NFS host of the VMX datastore. DatastoreNFSHost The maximum number of simultaneous backups per NFS host of the datastore. The maximum number of simultaneous backups per datastore cluster.

DatastoreCluster

For example, a Resource Limit of four for Datastore means that NetBackup policies can perform no more than four simultaneous backups on any particular datastore.

Restore Failover properties

The Restore Failover properties in the NetBackup Administration Console control how NetBackup performs automatic failover to a NetBackup media server. A failover server may be necessary if the regular media server is temporarily inaccessible to perform a restore operation. The automatic failover does not require administrator intervention. By default, NetBackup does not perform automatic failover. These properties apply to currently selected master servers.

Configuring Host Properties Restore Failover properties

197

Figure 3-62

Restore Failover dialog box

The Restore Failover dialog box contains the following properties. Table 3-57 Property
Media server

Restore Failover dialog box properties Description

Displays the NetBackup media servers that have failover protection for restores. Displays the servers that provide the failover protection. NetBackup searches from top to bottom in the column until it finds another server that can perform the restore.

Failover restore server

A NetBackup media server can appear only once in the Media server column but can be a failover server for multiple other media servers. The protected server and the failover server must both be in the same master and media server cluster. The following situations describe examples of when to use the restore failover capability:

Two or more media servers share a robot and each has connected drives. When a restore is requested, one of the servers is temporarily inaccessible. Two or more media servers have stand alone drives of the same type. When a restore is requested, one of the servers is temporarily inaccessible.

198

Configuring Host Properties Restore Failover properties

In these instances, inaccessible means that the connection between bprd on the master server and bptm on the media server (through bpcd) fails. Possible reasons for the failure are as follows:

The media server is down. The media server is up but bpcd does not respond. (For example, if the connection is refused or access is denied.) The media server is up and bpcd is running, but bptm has problems. (For example, bptm cannot find the required tape.)

Assigning an alternate media server as a failover restore server

You can assign another media server to act as a failover restore server for your media server. If your media server is unavailable during a restore, the failover restore server takes its place. To assign an alternate media server as a failover restore server

1 2 3 4 5 6

In the NetBackup Administration Console, in the left panel, expand NetBackup Management > Host Properties > Master Servers. In the right pane, double-click on the master server you want to modify. In the properties dialog box, in the left pane, click Restore Failover. Click Add. In the Media server field, specify the media server for failover protection. In the Failover restore servers field, specify the media servers to try if the server that is designated in the Media server field is unavailable. Separate the names of multiple servers with a single space. Click Add. The dialog box remains open for another entry. Click Close. From the Restore Failover dialog box, click Apply to accept the changes.

7 8 9

Before the change takes effect, you must stop and restart the NetBackup Request daemon on the master server where the configuration was changed. See About enabling automatic failover to an alternate server on page 945.

Configuring Host Properties Retention Periods properties

199

Retention Periods properties

Use the Retention Periods properties in the NetBackup Administraton Console to define a duration for each retention level. You can select from 25 retention levels. In a policy, the retention period determines how long NetBackup retains the backups or the archives that are created according to the schedule. These properties apply to selected master servers. Figure 3-63 Retention Periods dialog box

By default, NetBackup stores each backup on a volume that already contains backups at the same retention level. However, NetBackup does not check the retention period that is defined for that level. When the retention period for a level is redefined, some backups that share the same volume may have different retention periods. For example, if the retention level 3 is changed from one month to six months, NetBackup stores future level 3 backups on the same volumes. That is, the backups are placed on the volumes with the level 3 backups that have a retention period of one month. No problem exists if the new and the old retention periods are of similar values. However, before a major change is made to a retention period, suspend the volumes that were previously used for that retention level.

200

Configuring Host Properties Retention Periods properties

See Determining retention periods for volumes on page 201. The Retention Periods dialog box contains the following properties. Table 3-58 Property
Value Units

Retention Periods dialog box properties

Description
Assigns a number to the retention level setting. Specifies the units of time for the retention period. The list includes hours as the smallest unit of granularity and the special units, Infinite, and Expires immediately. The retention level number (0 through 24). A list of the current definitions for the 25 possible levels of retention. By default, levels 9 through 24 are set to infinite. Retention level 9 is the only level that cannot be changed and remains at infinite. See Retention Periods with end dates beyond 2038, excluding Infinity on page 202. With the default, there is no difference between a retention level of 12 and a retention level of 20, for example. The Schedule Count column indicates how many schedules currently use each level. If the retention period is changed for a level, it affects all schedules that use that level. The Changes Pending column uses an asterisk (*) to indicate that the period has been changed and not applied. NetBackup does not change the actual configuration until the administrator accepts or applies the changes.

Retention Level Retention Period

Schedule Count Schedules using this retention level Impact Report

Lists the number of schedules that use the currently selected retention level. Displays a list of the current policy names and schedule names that use the retention level. Displays a summary of how changes affect existing schedules. The list displays all schedules in which the retention period is shorter than the frequency period.

Changing a retention period

Use the following procedure to change a retention period. To change a retention period

1 2 3

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties > Master Servers. In the right pane, double-click on the master server you want to modify. In the properties dialog box, in the left pane, click Retention Periods.

Configuring Host Properties Retention Periods properties

201

Select the retention level to change. By default, levels 9 through 24 are set to infinite. If the levels are left at the default, there is no difference between a retention level of 12 and a retention level of 20. Level 9 cannot be changed and remains at a setting of infinite. See Retention Periods with end dates beyond 2038, excluding Infinity on page 202. The policy impact list now displays the names of all schedules that use the selected retention level. It also lists the policy to which each schedule belongs.

5 6

Type the new retention period in the Value box. From the Units drop-down list, select a unit of measure (days, weeks, months, years, Infinite, or Expires immediately). After you change the value or unit of measure, an asterisk (*) appears in the Changes Pending column to indicate that the period was changed. NetBackup does not change the actual configuration until the administrator accepts or applies the changes.

Click Impact Report. The policy impact list displays the policies and the schedule names where the new retention period is less than the frequency period. To prevent a potential gap in backup coverage, redefine the retention period for the schedules or change the retention or frequency for the schedule.

Do one of the following:

To discard your changes, click Cancel. To save your changes and leave the dialog box open to make further changes, click Apply. To save your changes and close the dialog box, click OK.

Determining retention periods for volumes

Use the following procedure to determine retention periods for volumes. To determine retention periods for volumes

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media In the right pane, find the volume on the list and examine the value in the Retention Period column.

202

Configuring Host Properties Servers properties

To see all volumes that have the same retention period, click the Retention Period column header to sort the volumes by retention period. This column heading is hidden by default.

Retention Periods with end dates beyond 2038, excluding Infinity

Due to UNIX epoch time and the year 2038 problem, any retention end date that exceeds January 19, 2038 is automatically set to expire on January 19, 2038, regardless of whether the expiration end date is reached. This issue does not apply to retention levels for which the retention period is set to Infinity. NetBackup never expires media with a retention set to Infinity unless instructed to do so by the NetBackup administrator.

Servers properties
The Servers properties display the NetBackup server list on selected master servers, media servers, and clients. The server list displays the NetBackup servers that each host recognizes. The Servers dialog box contains the following tabs and properties: Table 3-59 Property
Master Server

Servers dialog box properties

Description
Specifies the master server for the selected host. (The name of the selected host appears in the title bar.) This tab (Figure 3-64) lists the additional servers that can access the server that is specified as Master server. During installation, NetBackup sets the master server to the name of the system where the server software is installed. NetBackup uses the master server value to validate server access to the client. The master server value is also used to determine which server the client must connect to so that files can be listed and restored. To configure access to a remote server, add to the server list the name of the host seeking access. See Accessing remote servers on page 905.

Additional Servers tab

Configuring Host Properties Servers properties

203

Table 3-59 Property

Media Servers tab

Servers dialog box properties (continued)

Description
This tab (Figure 3-65) lists the hosts that are media servers only. Hosts that are listed as media servers can back up and restore clients, but have limited administrative privileges. If a server appears only on the Media servers tab, the server is a media server. Media servers can back up and restore clients, but they have limited administrative privileges. A server that appears on the Media servers tab and the Additional servers tab may introduce unintended consequences. A computer that is defined as both a master server and a media server gives the administrator of the media server full master server privileges. By listing the media server in both places, you may inadvertently give the media server administrator more privileges than intended.

OpsCenter Servers tab

This tab (Figure 3-66) lists the Symantec OpsCenter servers that can access the currently selected master server. To add a server to the list, ensure that the NetBackup server can reach the OpsCenter server. For more information, see the Symantec OpsCenter Administrator's Guide.

Figure 3-64

Additional servers tab in the Servers dialog box

204

Configuring Host Properties Servers properties

Figure 3-65

Media servers tab in the Servers dialog box

Configuring Host Properties Servers properties

205

Figure 3-66

OpsCenter servers tab in the Servers dialog box

See Adding a server to a remote server list on page 907.

Adding a server to a servers list

Depending on the tab that is selected, you can add a master server, media server, client, or OpsCenter server to the server list in the Additional servers tab, the Media servers tab, or the OpsCenter servers tab. All tabs appear in the Servers properties dialog box. To add a server to a list

1 2 3 4 5

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties. Depending on the host to be configured, select Master Servers, Media Servers, or Clients. In the right pane, double-click the master server, media server, or client you want to modify. In the properties dialog box, in the left pane, click Servers. Select the tab that contains the server list that you want to modify.

206

Configuring Host Properties Servers properties

Click Add. To add multiple hosts, select more than one media server or client in step 2 and click Apply To All in step 5. However, you can add only one master server to the list at a time.

7 8 9

In the Add a New Server Entry dialog box, type the name of the new server. Click Add. The dialog box remains open for another entry. Click Close.

Note: If you add a media server, run nbemmcmd -addhost to add the media server to the Enterprise Media Manager (EMM) database of the existing master server. See About sharing one Enterprise Media Manager (EMM) database across multiple master servers on page 207.

Removing a server from a server list

You can remove a master server or a media server from the Additional servers list. You can also remove a media server from the Media servers list. To change the Master Server

1 2 3 4 5 6

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties. Depending on the host to be configured, select Master Servers, Media Servers, or Clients. In the right pane, double-click the master server, media server, or client you want to modify. In the properties dialog box, in the left pane, click Servers. Select a server from the Additional servers list, the Media servers list, or the OpsCenter servers list. Click Remove.

Switching to another master server in the Servers properties dialog box

You can switch to view the properties of another master server in the Servers properties dialog box.

Configuring Host Properties Servers properties

207

To switch the master server in the Servers properties dialog box

1 2 3 4 5 6

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties. Depending on the host to be configured, select Master Servers, Media Servers, or Clients. In the details pane, double-click the master server, media server, or client you want to modify. In the dialog box, click Servers. From the Additional servers list, select a server. Click Make Master.

About sharing one Enterprise Media Manager (EMM) database across multiple master servers
Multiple master servers can share one Enterprise Media Manager (EMM) database that is located on a single host. The host that contains the EMM database can be either a master server or a media server. The Servers host properties must be set up to allow multiple master servers to access the host that contains the EMM database. Use the bpgetconfig command to obtain a list of configuration entries. Then, use the bpsetconfig command to change the entries as needed. For information about these commands, see NetBackup Commands Reference Guide. The following table shows example registry entries from three master servers (Meadow, Havarti, and Study) that share one EMM database. One of the servers (Meadow) hosts the EMM database. Table 3-60 Example registry entries from three master servers that share an EMM database Havarti
SERVER = havarti SERVER = meadow

Meadow
SERVER = meadow SERVER = havarti SERVER = study CLIENT_NAME = meadow EMMSERVER = meadow

Study
SERVER = study SERVER = meadow

CLIENT_NAME = havarti CLIENT_NAME = study EMMSERVER = meadow EMMSERVER = meadow

208

Configuring Host Properties SharedDisk properties

Use the following conventions when making entries like those in the example:

The first SERVER entry must be the name of the master server. The table shows that the first SERVER entry matches the name of each master server. The host server must have a SERVER entry for each server that shares the EMM database. This entry allows the NetBackup Administration Console to administer the other servers. The table shows Havarti and Study listed under Meadow. See About choosing a remote server to administer on page 909. If the EMM database is hosted on another master server, that server must be listed. The table shows Meadow listed under Havarti and Study. The CLIENT_NAME entry must match the name of the master server. The EMMSERVER entry must be present on all master servers that share the EMM host. The table shows Meadow listed as the EMMSERVER for all three servers.

If you assign the media server to a different master, the Enterprise Media Manager database also needs to be updated. To update the EMM database, run the following command: See Switching to another master server in the Servers properties dialog box on page 206.
/usr/openv/netbackup/bin/admincmd/nbemmcmd -updatehost

SharedDisk properties
The SharedDisk properties specify the SharedDisk storage option properties for a NetBackup configuration. These properties apply to currently selected master servers. See About SharedDisk support in NetBackup 7.0 and later on page 394.

SharePoint properties
The SharePoint properties apply to currently selected Windows clients to protect SharePoint Server installations.

Configuring Host Properties SharePoint properties

209

Figure 3-67

SharePoint dialog box

The SharePoint dialog box contains the following properties. Table 3-61 Property
Domain\User

SharePoint dialog box properties Description

Specifies the domain and the user name for the account you want to use to log on to SharePoint (DOMAIN\user name). Specifies the password for the account. Specifies the consistency checks to perform on the SQL Server databases before NetBackup begins a backup operation. These checks are performed for both server-directed and user-directed backups. If you choose to perform a consistency check, you can select Continue with backup if consistency check fails. NetBackup then continues to perform the backup if the consistency check fails.

Password Consistency check before backup

For complete information on these options, see the NetBackup for Microsoft SharePoint Server Administrators Guide .

210

Configuring Host Properties Symantec Products properties

Consistency check options for SharePoint Server

The following consistency checks can be performed before a SharePoint Server backup. Table 3-62 Option
None Full check, excluding indexes

Consistency check options

Description
Do not perform consistency checking. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the non-clustered index pages is not checked. Include indexes in the consistency check. Any errors are logged.

Full check, including indexes Physical check only (SQL 2000 only)

Only applicable for SQL 2000.

Symantec Products properties

The Symantec Products properties encompass properties for other Symantec products. The Symantec Products properties include the subnode, Backup Exec Tape Reader properties. See Backup Exec Tape Reader properties on page 71.

Throttle Bandwidth properties

Use the Throttle Bandwidth properties to specify a limit for the network bandwidth or transfer rate that NetBackup clients use on a network. The actual limiting occurs on the client side of the backup connection. These properties limit only backups. Restores are unaffected. The default is that the bandwidth is not limited. The Throttle Bandwidth properties are similar to the Bandwidth host properties, but offer greater flexibility in IPv6 environments.

Configuring Host Properties Throttle Bandwidth properties

211

Figure 3-68

Throttle Bandwidth dialog box

To manage entries in the Throttle Bandwidth dialog box, select one of the following buttons:
Add Add a network or host to the Network or Host list using the Add Bandwidth Settings dialog box. Change the selected network or host property using the Change Bandwidth Settings dialog box. Removes the selected network or host from the Network or Host list.

Change

Remove

Add Bandwidth Settings dialog box for Throttle Bandwidth properties

The Add Bandwidth Settings and the Change Bandwidth Settings dialog boxes contain the following properties.
Network or Host The network or host to which the throttle applies.

212

Configuring Host Properties Timeouts properties

Bandwidth (KB/Sec)

The bandwidth or the transfer rate in kilobyte per second for the network or host indicated. A value of zero disables throttling IPv6 addresses.

Timeouts properties
The Timeouts properties apply to selected master servers, media servers, and clients. Figure 3-69 Timeouts dialog box

The Timeouts dialog box contains the following properties. Table 3-63 Property
Client connect timeout

Timeouts dialog box properties

Description
Specifies the number of seconds the server waits before it times out when it connects to a client. The default is 300 seconds.

Backup start notify timeout Specifies the number of seconds the server waits for the bpstart_notify script on a client to complete. The default is 300 seconds.

Note: If this timeout is changed, verify that Client read timeout is set to the same
or higher value.

Configuring Host Properties Timeouts properties

213

Table 3-63 Property

File browse timeout

Timeouts dialog box properties (continued)

Description
Specifies how long the client can wait for a response from the NetBackup master server while it lists files.

Note: If it exists, the value in a UNIX clients $HOME/bp.conf file takes precedence
to the property here. If the limit is exceeded, the user receives a socket read failed error. The timeout can be exceeded even while the server processes the request. Use OS dependent timeouts Specifies that the client waits for the timeout period as determined by the operating system when it lists files, as follows:

Windows client: 300 seconds UNIX client: 1800 seconds

Media mount timeout

Specifies how long NetBackup waits for the requested media to be mounted, positioned, and ready on backups, restores, and duplications. This property applies to currently selected master servers. Use this timeout to eliminate excessive waiting time during manual media mounts. (For example, when robotic media is out of the robot or is off site.)

Client read timeout

Specifies the number of seconds to use for the client-read timeout. This timeout can apply to a NetBackup master, remote media server, or database-extension client (such as NetBackup for Oracle). The default is 300 seconds. If the server does not get a response from a client within the Client read timeout period, the backup or restore operation, for example, fails. The client-read timeout on a database-extension client is a special case. Clients can initially require more time to get ready than other clients. More time is required because database backup utilities frequently start several backup jobs at the same time, slowing the central processing unit.

Note: For database-extension clients, Symantec suggests that the Client read timeout
be set to a value greater than 5 minutes. 15 minutes are adequate for many installations. For other clients, change this property only if the client encounters problems. The sequence on a database-extension client is as follows: NetBackup on the database-extension client reads the clients client-read timeout to find the initial value. If the option is not set, the standard 5-minute default is used. When the database-extension API receives the servers value, it uses it as the client-read timeout.

See Client Settings (UNIX) properties on page 95.

214

Configuring Host Properties Universal Settings properties

Table 3-63 Property

Backup end notify timeout

Timeouts dialog box properties (continued)

Description
Specifies the number of seconds that the server waits for the bpend_notify script on a client to complete. The default is 300 seconds.

Note: If this timeout is changed, verify that Client read timeout is set to the same
or higher value. Media server connect timeout Specifies the number of seconds that the master server waits before it times out when it connects to a remote media server. The default is 30 seconds.

Universal Settings properties

Use the Universal Settings properties in the NetBackup Administration Console to configure basic backup and restore settings. These properties apply to selected master servers, media servers, and clients. Figure 3-70 Universal Settings dialog box

The Universal Settings dialog box contains the following options.

Configuring Host Properties Universal Settings properties

215

Table 3-64 Property

Restore retries

Universal Settings dialog box properties

Description
Specifies the number of attempts a client has to restore after a failure. (The default is 0; the client does not attempt to retry a restore. The client can try up to three times.) Change Restore retries only if problems are encountered. If a job fails after the maximum number of retries, the job goes into an incomplete state. The job remains in the incomplete state as determined by the Move restore job from incomplete state to done state property. See Clean-up properties on page 77. A checkpointed job is retried from the start of the last checkpointed file rather than at the beginning of the job. Checkpoint restart for restore jobs allows a NetBackup administrator to resume a failed restore job from the Activity Monitor. See Take checkpoints every __ minutes (policy attribute) on page 540.

Browse timeframe for restores

Specifies how long ago NetBackup searches for files to restore. For example, to limit the browse range to one week before the current date, clear the Last full backup check box and specify 7. This limit is specified on the master server and applies to all NetBackup clients. A limit can be specified on an individual client to reduce the size of the Search window. The client setting cannot make the browse window larger. By default, NetBackup includes files from the time of the last-full backup through the latest backup for the client. If the client belongs to more than one policy, then the browse starts with the earliest of the set of last-full backups.

Last full backup

Indicates whether NetBackup includes all backups since the last successful full backup in its browse range. This property must be disabled to enter a value for the Browse timeframe for restores property. The default is that this property is enabled. Specifies whether a NetBackup server can create or modify files on the NetBackup client. For example, enable this property to prevent server-directed restores and remote changes to the client properties. After the Allow server file writes property is applied, it can be cleared only by modifying the client configuration. The default is that server writes are allowed.

Allow server file writes

Accept connections on nonreserved ports

Specifies whether the NetBackup client service (bpcd) can accept remote connections from non-reserved ports. (Non-reserved ports have port numbers of 1024 or greater.) The default is that this property is enabled. This property no longer applies. For information about this property, refer to NetBackup 6.5 documentation.

216

Configuring Host Properties Universal Settings properties

Table 3-64 Property Description

Universal Settings dialog box properties (continued)

Enable performance data Specifies whether NetBackup updates disk and tape performance object counters. collection (Windows server (Applies only to Windows master and media servers. Use the Windows Performance only) Monitor utility (perfmon) to view the NetBackup performance counters. The default is that this property is enabled. See the NetBackup Administration Guide, Volume II for more information about using the System Monitor with NetBackup. Client sends mail Specifies whether the client sends an email to the address that is specified in the Universal Settings properties. If the client cannot send email, use Server sends mail. The default is that this property is enabled. Specifies whether the server sends an email to the address that is specified in the Global Attributes properties. Enable this property if the client cannot send mail and you want an email notification. The default is that this property is disabled. See Global Attributes properties on page 138. Client administrators email Specifies the email address of the administrator on the client. This address is where NetBackup sends backup status reports for the client. By default, no email is sent. To enter multiple addresses or email aliases, separate entries with commas.

Server sends mail

Logging the status of a redirected restore

A redirected restore may not produce a progress log. The name of the requesting server must appear in the server list for the server that performs the restore. Otherwise, no progress log is produced for a redirected restore.(A progress log is an entry in the Task Progress tab of the Backup, Archive, and Restore client interface.) Without the entry in the server list, the restoring server has no access to write the log files to the requesting server. Add the requesting server to the server list and log into the requesting server. To produce a progress log

1 2

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties > Master Servers. In the right pane, double-click the master server you want to modify. In the properties dialog box, in the left pane, click Servers.

Configuring Host Properties UNIX Client properties

217

Perform one of the following actions:

To add the restoring server to the Additional servers list To add the restoring server to the Media servers list From the Media servers list, click Add.

From the Additional servers list, click Add.

4 5 6 7

In the Add a New Server Entry dialog box, type the name of the new server. Click Add. The dialog box remains open for another entry. Click Close. Log on to the restoring server. Check the Activity Monitor to determine the success of the restore operation. See About the Jobs tab on page 836.

UNIX Client properties

Use the UNIX Client properties in the NetBackup Administration Console to define properties of UNIX clients. Figure 3-71 UNIX Client dialog box

218

Configuring Host Properties UNIX Server properties

See Client Settings (UNIX) properties on page 95. See Busy File Settings properties on page 75. See Lotus Notes properties on page 158.

UNIX Server properties

Use the UNIX Server properties in the NetBackup Adminstration Console to change the NFS access timeout property. This property specifies how long the backup waits to process the mount table before it considers an NFS file system unavailable. The default is 5 seconds. These properties apply to selected UNIX master servers. Figure 3-72 UNIX Server dialog box

See Follow NFS (policy attribute) on page 547.

VMware Access Hosts properties

Use the VMware backup hosts properties in the NetBackup Adminstration Console to add or remove VMware backup hosts. These properties appear when the NetBackup Enterprise Client license is installed. These properties apply to currently selected master servers.

Configuring Host Properties VSP (Volume Snapshot Provider) properties

219

Figure 3-73

VMware Access Hosts dialog box

You can add servers to and remove servers from the backup hosts list. A VMware backup host is a server on the same SAN as a VMware ESX server. The VMware ESX server must be able to access the snapshot of the VMware virtual machine. A backup host can provide access to the files for third-party backup vendors. For more information, see the NetBackup for VMware Administrators Guide.

VSP (Volume Snapshot Provider) properties

Use the Volume Snapshot Provider properties in the NetBackup Administration Console to change the way NetBackup manages snapshots. These properties are displayed when the selected client is running NetBackup 6.x. The VSP properties do not appear for 7.x clients. See the following topic for information about selecting VSP for backlevel and upgraded clients: See Back-level and upgraded clients that use Windows Open File Backup on page 93. For information about VSP settings, see the 6.5 NetBackup Administrator's Guide, Volume I.

220

Configuring Host Properties Windows Client properties

Windows Client properties

Use the Windows Client properties in the NetBackup Administration Console to define NetBackup properties for Microsoft Windows clients. Figure 3-74 Windows Client dialog box

Windows Client properties include specific host properties for configuring Windows clients.

Configuration options not found in the Host Properties

To change the default value for an option that is not found in the Host Properties, first use the bpgetconfig command to obtain a list of configuration entries. Then use bpsetconfig to change the entries as needed. For information about bpgetconfig and bpsetconfig, see the NetBackup Commands Reference Guide. The followingNetBackup administration options cannot be configured by using the NetBackup Administration Console.

Configuring Host Properties Configuration options not found in the Host Properties

221

AUTO_ADD_ALL_ALIASES_FOR_CLIENT

See AUTO_ADD_ALL_ALIASES_FOR_CLIENT on page 221. See LIST_FS_IMAGE_HEADERS on page 221. See the NetBackup Administrator's Guide, Volume II.

LIST_FS_IMAGE_HEADERS

vm.conf file (media and device configuration options)

AUTO_ADD_ALL_ALIASES_FOR_CLIENT
This entry allows client aliases to be automatically added to the NetBackup database when bpdbm detects a new client in a backup policy. Table 3-65 Usage
Where to use How to use

AUTO_ADD_ALL_ALIASES_FOR_CLIENT information

Description
On a UNIX or Windows master server. By default, AUTO_ADD_ALL_ALIASES_FOR_CLIENT does not appear in the registry. When not present, AUTO_ADD_ALL_ALIASES_FOR_CLIENT = YES The following entry prohibits bpdbm from adding a client alias automatically. AUTO_ADD_ALL_ALIASES_FOR_CLIENT = NO

Example

LIST_FS_IMAGE_HEADERS
This entry controls whether or not bpdbm looks for legacy image headers when the bplist and bpimagelist commands are run. Table 3-66 Usage
Where to use How to use

LIST_FS_IMAGE_HEADERS information

Description
On a UNIX or Windows master server. Immediately after NetBackup 7.5 is installed, LIST_FS_IMAGE_HEADERS does not appear in the bp.conf file or registry. After a catalog cleanup job runs and successfully migrates all legacy image headers, LIST_FS_IMAGE_HEADERS = NO is added to the bp.conf file or registry. If the entry is changed to YES, the next catalog cleanup job migrates any legacy images that are located in the db/images directory. After all of the image headers are migrated, the entry once again changes to NO.

222

Configuring Host Properties Configuration options not found in the Host Properties

Table 3-66 Usage

Example

LIST_FS_IMAGE_HEADERS information (continued)

Description
After a catalog cleanup job runs, the entry appears in the bp.conf file or registry. LIST_FS_IMAGE_HEADERS = NO

Equivalent Administration Console property

No equivalent exists in the NetBackup Administration Console host properties.

Chapter

Configuring server groups

This chapter includes the following topics:

About server groups Configuring a server group Deleting a server group

About server groups

A server group is a group of NetBackup servers that are used for a common purpose. A media sharing group is a server group that shares media for write purposes (backups). A media sharing group can contain the following:

NetBackup master server NetBackup media servers NDMP tape servers Virtual host names of NetBackup media servers in a cluster

Servers can be in more than one group. All members of a server group must have the same NetBackup master server. Only NetBackup 6.5 and later systems can be in server groups. See About media sharing on page 329. See Configuring media sharing with a server group on page 330.

224

Configuring server groups Configuring a server group

Configuring a server group

Use the following procedure to configure a server group. Note: NetBackup allows a server group name to be the same as the name of a media server. However, Symantec recommends that you do not use the same name for a server group and a media server. It may be confusing to use the same name for a media server and a media server group.

Configuring server groups Configuring a server group

225

To configure a server group

1 2

In the NetBackup Administration Console, expand Media and Device Management > Devices > Server Groups. In the Actions menu, select New > New Server Groups.

In the Add Server Group Details dialog box, enter or select the appropriate information. See Server group properties on page 226. To add a server to the group, select it in the Servers Not in Group window and click Add. To remove a server from the group, select it in the Servers in Group window and click Remove.

226

Configuring server groups Deleting a server group

Server group properties

The following table describes server group properties that include the following options. Table 4-1 Property Description Server group properties

Server group name Specifies the name of the server group. You cannot change the name of an existing server group. Symantec recommends that server group names be unique. That is, do not use the same name for a server group that you use for a host such as a media server. If you do, you may not be able to determine easily if a tape is restricted to a specific media server or to a specific media server group. Server group type Specifies the type of server group. See About server groups on page 223. Other server group types (such as Alternate Restore) are reserved for future use. State Specifies the state of the server group:

Active. The server group is available for use. Inactive. The server group is not available for use.

To change the state, select the new state from the dropdown box. Description Servers in group Servers not in group Describes the media server group. Specifies the servers (and the server type) that belong to the group. Specifies the servers (and the server type) that do not belong to the group.

Deleting a server group

Use the following procedure to delete a server group. To delete a server group

1 2 3 4

In the NetBackup Administration Console, select Media and Device Management > Devices > Server Groups. Select the group to delete. Select Edit > Delete. Click OK.

Chapter

Configuring host credentials

This chapter includes the following topics:

About configuring credentials

About configuring credentials

Credentials appears only if a feature that requires external credentials is licensed. Use Media and Device Management > Credentials to manage log on credentials for the following:

NetBackup Deduplication Engine credentials. Create the credentials when you configure the storage server. See the NetBackup Deduplication Guide. NDMP hosts. See the NetBackup for NDMP Administrators Guide. OpenStorage storage servers. Configure the credentials when you configure the storage server. See the NetBackup OpenStorage Solutions Guide for Disk.

228

Configuring host credentials About configuring credentials

Chapter

Managing media servers

This chapter includes the following topics:

Activating or deactivating a media server Adding a media server About decommissioning a media server Previewing references to a media server Decommissioning a media server Registering a media server Deleting all devices from a media server Removing a device host from the EMM database

Activating or deactivating a media server

When you activate a media server, NetBackup can use it for backup and restore jobs. For example, you can deactivate a media server to perform maintenance. When a media server is deactivated, NetBackup does not send job requests to it. When you deactivate a media server, the following things occur:

Current jobs are allowed to complete. No new jobs are scheduled for the host. If the host is part of a shared drive configuration, it does not scan drives.

230

Managing media servers Adding a media server

To activate or deactivate a media server

1 2 3

In the NetBackup Administration Console, expand Media and Device Management > Media Servers. From the Media Servers pane, select the media server to activate or deactivate. On the Actions menu, select Activate or Actions > Deactivate.

Adding a media server

The following table describes an overview of how to add a media server to an existing NetBackup environment. Note: The NetBackup Enterprise Media Manager service must be active when a media server is added, devices and volumes are configured, and clients are backed up or restored. Table 6-1 Procedure
On the new media server host, attach the devices and install any software that is required to drive the storage devices. On the new media server host, prepare the hosts operating system.

Adding a media server Section

See the vendors documentation.

See the NetBackup Device Configuration Guide.

On the master server, add the new media server to the additional servers list of See Servers properties the master server. Also, add the new media server to the additional servers list on page 202. of the clients that the new media server backs up. If the EMM server resides on a host other than the master server, add the new media server to the additional servers list on that host. If the new media server is part of a server group, add it to the additional servers list on all media servers in the group. To avoid problems with NetBackup, ensure that the host name used in NetBackup matches the host name in the TCP/IP configuration. Restart the NetBackup services on the master server, the EMM server, and the media servers where a new server name was added. Install the NetBackup media server software. See Starting or stopping a service on page 852. See the NetBackup Installation Guide. See Configuring robots and tape drives on page 252.

On the master server, configure the robots and drives that are attached to the media server.

Managing media servers About decommissioning a media server

231

Table 6-1 Procedure

Adding a media server (continued) Section

See About adding volumes on page 295.

On the master server, configure the volumes.

On the master server, add storage units to the media server. Always specify the See Creating a storage unit media server as the media server for the storage unit. on page 399. The Device Configuration Wizard can create storage units when you configure robots and drives. Therefore, if you created storage units already, skip this step. On the master server, configure the NetBackup policies and schedules to use the See About the Policies utility storage units that are configured on the media server. on page 514. Test the configuration by performing a user backup or a manual backup that uses See Performing manual a schedule that specifies a storage unit on the media server. backups on page 674.

About decommissioning a media server

New with this release is a command to decommission a media server, nbdecommission. The command launches a text-based wizard that guides you through the decommission process. The wizard removes the references to a media server from a NetBackup domain. (You may have to remove some references manually; the wizard provides instructions to do so in most cases.) Note: If you have installed an indexing server on the media server that you want to decommission, you must first decommission the indexing server. See the NetBackup Search Administrator's Guide for instructions to decommission an indexing server. The nbdecommission command helps in the following scenarios:

You add a new media server and new storage to your environment. You direct all backup jobs that went to the old server to the new server. After all of the backup images on the old server expire, you run nbdecommission to retire the old server. You replace an old server with a new server and keep the same storage. You want to access all of the old server storage and backup images from the new server. The old server fails, and you need to replace it with a new server.

232

Managing media servers About decommissioning a media server

You also can use the wizard if you try to decommission a media server manually and references to it still remain. The wizard may clean up any references that remain. Throughout this documentation, the media server to be decommissioned is referred to as the old server. Warning: Be careful when you use the nbdecommission command. Because the command may expire images, data loss may occur. Therefore, you should completely understand what the command does before you use it. Symantec recommends that you first preview all of the references to a media server before you decommission it. See Previewing references to a media server on page 237.

About decommissioning limitations

The following are the limitations of the nbdecommission command:

Does not decommission media servers at release levels earlier than 6.0. Does not decommission clustered media servers. Those include NetBackup failover media servers or application clusters. Does not process the media server deduplication pools. Does not update the vm.conf files on the NetBackup servers in your environment. Therefore, the old server may remain in the vm.conf files on the NetBackup servers. Does not update the configuration files on the clients. Therefore, the old server may remain in the server lists on the clients. If you replace an old server with a new server, the new server is not added to the client server lists. Does not process the NetBackup Vault profiles. If NetBackup Vault profiles exist that refer to the storage units on the old server, update the Vault profiles manually. Does not notify you about orphaned resources. Does not restart the daemons and services on other servers that the decommissioning affects. Requires that you shut down all daemons and services on the old server after it is decommissioned. Requires that you reconfigure devices on the new server manually (if required).

Managing media servers About decommissioning a media server

233

Requires that you know which jobs are running on the old server. You must kill them or let them run to completion before you run the decommission process. The -list_ref option only reports on the references that it removes explicitly. The command removes some items implicitly and it does not report them. For example, host aliases and host credentials are removed but not reported. Requires that you move any media ID generation rules that exist on the old server. You must move them manually to the media server that performs robot inventory. Moves the old server to an Administrative Pause state so that no new jobs are started. However, NetBackup still can start backup and restore jobs for basic disk; they obtain resources differently than do jobs for other storage destinations. Also, the nbdecommission command may clear the Administrative Pause to expire images (depending on your responses to the wizard). Jobs may start during this period.

Before you decommission a media server

Before you decommission a media server, Symantec recommends that you do the following:

Preview the actions of the nbdecommission command. See Previewing references to a media server on page 237. Analyze the output of the preview operation to ensure that the command captures all references to the old server. If it did not, make a list of the items that the command does not cover and fix them manually later.

Back up the NetBackup catalog before you begin. You can use it to return your environment to the pre-decommission state if something goes wrong or you have to abort the decommission. Run the command during a maintenance window when the load on the NetBackup environment is minimal.

Post decommission recommendations

After you run the nbdecommission command, the following actions are recommended:

Follow all of the instructions the command provides. The command may provide instructions for performing the actions that it cannot perform. For example, it may provide instructions to cancel the backup jobs that are active on the old server.

234

Managing media servers About decommissioning a media server

Move the physical storage (if needed) and then reconfigure and reinventory those devices. Examine the vm.conf files on all of the NetBackup servers in your environment. Remove references to the old server and add references to the new server where necessary. Remove the old server from the server lists on the clients and add the new server where necessary. The nbdecommission command outputs a list of clients that refer to old server. Verify that the old server was removed correctly. Examine the various logical components (backup policies, storage units, and so on) to make sure that the old server references have been removed. Back up the NetBackup catalog as soon as possible.

Decommission actions
The nbdecommission command deletes the configuration for the old server from the EMM database, the NetBackup image catalog, and configuration files on servers. The following table shows the actions it performs for the components that reference the media server. The table is organized in the order in which the command processes the component. Table 6-2 Component Action
nbdecommission command actions

Storage unit - Tape Deletes the following tape storage units: Those in which the Storage device attribute specifies a robot for which the old server is the robot control host. Those in which the Media server attribute specifies the old server.

Those in which the Media server attribute specifies Any Available and the old server is the only server that can access the storage unit.

Tape drive

Deletes the tape drive path for each tape drive that is attached to the old server. If the path on the old server is the only path, it also deletes the tape drive. If a path to a drive exists on more than one media server, the tape drive may become unusable. You may have to connect the tape drive to a different media server and then reconfigure it in NetBackup. For example, if the old server is a scan host for a shared drive, NetBackup cannot use the drive if no other host can scan.

Managing media servers About decommissioning a media server

235

Table 6-2 Component

Robotic library

nbdecommission command actions (continued)

Action
Deletes all of the robotic libraries that are attached to the old server. If the old server is the robot control host for a shared library, the drives and media become stand-alone and unusable. You must reconfigure and re-inventory the library.

Tape media

Specifies if you want to expire the following tape media or move them to another media server:

Those assigned to the old server.

Those owned by a media sharing group in which the old server is the only member of the group. Those that have no specific Media owner and the last write host is same as the old server. Storage unit BasicDisk Deletes the storage unit if no images exist on it. If images exist, the wizard lets you choose one of the following options:

Expire the images and delete the storage unit. Move the images to the new server. The wizard also updates the Media server field in the storage unit. The BasicDisk storage must be shared, and the same disk path must be available on the new server.

Storage unit Nearstore

Deletes the storage unit if no images exist on it. If images exist, the wizard lets you choose one of the following options:

Expire the images and delete the storage unit. Move the images to a new server. The wizard also transfers the credentials to the new server and updates the Media server field in the storage unit.

Storage unit SnapVault

Deletes the storage unit if no images exist on it. If images exist, the wizard lets you choose one of the following options:

Expire the images and delete the storage unit. Move the images to a new server. The wizard also transfers the credentials to the new server and updates the Media server field in the storage unit.

236

Managing media servers About decommissioning a media server

Table 6-2 Component Action

nbdecommission command actions (continued)

Storage unit Specifies that if more than one media server can access the disk pool that is the destination of AdvancedDisk and the storage unit, it does the following: SharedDisk Removes the old server from the Media Servers list of the storage unit.

Deletes the old server as a storage server.

If the old server is the only server that can access the disk pool, the wizard lets you choose to do one of the following: Move the storage and images to the new server and delete the old server as a storage server. The disk volumes must be available on the new server at the same path as the old server. Expire the images (if any), delete any storage units that reference the disk pool, delete the disk pool, and delete the storage server. (A reference is when the disk pool appears in the Disk pool setting of a storage unit.)

Storage unit OpenStorage

Specifies that if more than one media server can access the disk pool that is the destination of the storage unit, it does the following:

Removes the old server from the Media Servers list of the storage unit. Deletes the media server as an OpenStorage storage server.

If the old server is the only server that can access the disk pool, the wizard lets you choose to do one of the following: Transfer the credentials to the new server and update the Media server field in the storage unit if required. Expire the images (if any), delete any storage units that reference the disk pool, and delete the disk pool. (A reference is when the disk pool appears in the Disk pool setting of a storage unit.)

Storage unit group Specifies that if the nbdecommission command deletes all of the storage units in a storage unit group, it also deletes the storage unit group. Deleting the storage unit group also may affect backup policies and storage lifecycle policies. See Backup policy and schedule and Storage lifecycle policy in this table. Backup policy and Deactivates any backup policy in which the storage destination (directly or indirectly) is a schedule storage unit that the command deletes. Specifically, deactivates any backup policy that meets any of the following conditions:

The destination is a storage unit that the nbdecommission command deleted. The destination is a storage unit group that contains only one storage unit and the nbdecommission command deleted that storage unit. The destination is a storage lifecycle policy and the nbdecommission command deleted the storage unit that is a Backup operation of the storage lifecycle policy.

Managing media servers Previewing references to a media server

237

Table 6-2 Component

Storage lifecycle policy

nbdecommission command actions (continued)

Action
Specifies that for each storage lifecycle policy in which one or more operations uses a storage unit that the command deleted, it does the following:

If images under the SLP control are in-process or yet to be processed, displays the commands to cancel the SLP jobs and then exits. After you cancel the jobs (or wait until the jobs complete), rerun the nbdecommission command to continue with the decommissioning. If all of the images under SLP control are processed, deactivates the storage lifecycle policy. If a deleted storage unit was used by a Backup or Snapshot operation, deactivates all backup policies with the storage lifecycle policy as the destination.

Fibre Transport media server

Displays the commands necessary to delete the old server as an FT media server and then exits. After you delete the old server as an FT media server, rerun the nbdecommission command to continue with the decommissioning. On UNIX NetBackup servers, removes the old server from the following bp.conf file entries:

bp.conf file

SERVER MEDIA_SERVER CLIENT_NAME BROWSER

On UNIX master servers, also removes the old server from the FORCE_RESTORE_MEDIA_SERVER and FAILOVER_RESTORE_MEDIA_SERVERS entries. Windows registry On Windows NetBackup servers, removes the old server from the following registry keys:

SERVER MEDIA_SERVER CLIENT_NAME BROWSER

On Windows master servers, also removes the old server from the FORCE_RESTORE_MEDIA_SERVER and FAILOVER_RESTORE_MEDIA_SERVERS keys. Clients Lists the clients on which the old server appears in their server lists. You must remove the references to the old server manually.

Previewing references to a media server

Use the following procedure to preview the associations and references to a media server that you want to decommission. Symantec recommends that you preview the references to a media server before you decommission it. The old server does not have to be up and responsive.

238

Managing media servers Decommissioning a media server

See About decommissioning a media server on page 231. See Decommissioning a media server on page 238. The nbdecommission command resides in the following directories:

UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Veritas\NetBackup\bin\admincmd

To preview references to a media server

Run the nbdecommission command on the master server or on a media server. The following is the command syntax:
nbdecommission -list_ref -oldserver OldServer > file.txt

Replace OldServer with the name of the host to be decommissioned. Replace file with a name that denotes its contents or purpose.

Analyze the output of the preview operation to ensure that the command captures all references to the old server. If it did not, make a list of the items that the command does not cover and fix them manually later.

Decommissioning a media server

Use the nbdecommission text-based wizard to decommission a media server. The wizard guides you through the decommission process. Your path through the wizard depends on how you respond to the wizard prompts. Depending on your environment and how you respond to prompts, the wizard may advise you to perform an action and then exit. To continue in the wizard, you must run the wizard again after you perform the advised action. You may have to exit and rerun the wizard several times. Note: If you have installed an indexing server on the media server that you want to decommission, you must first decommission the indexing server. See the NetBackup Search Administrator's Guide for instructions to decommission an indexing server. If active jobs exist on the media server, you must cancel them before the command can begin to decommission the media server. Alternatively, you can wait until they finish. The OldServer does not have to be up and responsive. Symantec recommends that you preview the media server references before you decommission a media server.

Managing media servers Decommissioning a media server

239

See About decommissioning a media server on page 231. See Previewing references to a media server on page 237. The nbdecommission command resides in the following directories:

UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\Veritas\NetBackup\bin\admincmd

The nbdecommission command logs to the standard NetBackup administrator commands log directory. To replace an old media server with a new media server

Run the nbdecommission command on the master server or on a media server that is not the object of this operation. The following is the command syntax:
nbdecommission -oldserver OldServer [-newserver NewServer] [-file decom_ops.txt]

Replace OldServer with the name of the host to be decommissioned.

-newserver is optional. If you specify a new server, the new server becomes

the default media server for the replacement operations. If you do not specify a new server, the wizard prompts you for the new server for each storage type that contains valid backup images. This method is useful if you want to move backup images to different media servers. For example, you can move backup images from tape storage to one media server and backup images from disk storage to another media server.
-file is optional. It writes the command operations to the specified file.

Replace decom_ops.txt with a name that denotes its purpose or contents. Symantec recommends that you use the -file option to maintain a record of the command operations.

Follow the prompts and perform the requested actions. For example, the command may make changes on the master server and on multiple media servers. You may be required to restart the NetBackup services on those servers so that the changes take effect.

To decommission a media server

Run the following command on the master server or on a media server that is not the object of this operation. The OldServer does not have to be up and responsive.
nbdecommission -oldserver OldServer

Replace OldServer with the name of the host to be decommissioned.

Follow the prompts and perform the requested actions.

240

Managing media servers Registering a media server

Registering a media server

If the EMM server is not running when you install a media server, the media server is not registered. You cannot discover, configure, and manage the devices of that media server. You must register the media server with the EMM server. To register a media server

1 2

Start the EMM service on the EMM server. On the EMM server host, run the following command (for the hostname, use the host name of the media server):
nbemmcmd -addhost -machinename hostname -machinetype media -masterserver server_name -operatingsystem os_type-netbackupversion level.major_level.minor_level

To avoid problems with NetBackup, ensure that the host name that is used in NetBackup matches the host name in the TCP/IP configuration. Information about nbemmcmd command usage is available. See the NetBackup Commands Reference Guide.

Deleting all devices from a media server

You can delete all devices from a media server. The media server can be up, down, or failed and unrecoverable. All devices include robots, drives, and disk pools. Two procedures exist: one to delete all robots and drives and the other to delete disk pools. To delete all robots and drives from a media server

Enter the following command on the master server:

install_path\NetBackup\bin\admincmd\nbemmcmd -deletealldevices -machinename server_name -machinetype media

Replace server_name with the name of the media server.

Managing media servers Deleting all devices from a media server

241

To delete disk pools from a media server

If the media server has disk pools configured, remove the media server from the storage units that use those disk pools. For each storage unit, run the following command on the master server:
install_path\NetBackup\bin\admincmd\bpsturep -label storage_unit_label -delhost host_name

Replace storage_unit_label with the name of the storage unit and host_name with the name of the media server.

If the media server is the only storage server for the disk pools, change the state of the disk pools to DOWN. To do so, enter the following command on the master server for each disk pool:
install_path\NetBackup\bin\admincmd\nbdev config -changestate -stype server_type -dp disk_pool_name -state DOWN

Replace server_type with the type of storage server: AdvancedDisk, PureDisk, or the vendor string that identifies the OpenStorage server type. Replace disk_pool_name with the name of the disk pool.

For each disk pool, do the following:

Remove the media server from disk pool access by entering the following command on the master server:
install_path\NetBackup\bin\admincmd\nbdevconfig -changedp -dp -disk_pool_name stype server_type -del_storage_servers storage_server

Replace disk_pool_name with the name of the disk pool. Replace server_type with the type of storage server: AdvancedDisk, PureDisk, or the vendor string that identifies the OpenStorage server type. Replace storage_server with the name of the media server.

If the disk pool is on disk storage available only to the media server and is no longer required, delete the disk pool as follows:
install_path\NetBackup\bin\admincmd\nbdevconfig -deletedp -dp disk_pool_name -stype server_type

You cannot delete a disk pool that has unexpired backup images. You must first expire the images and delete the image fragments, as follows:

Expire the image as follows:

install_path\NetBackup\bin\admincmd\bpexpdate -dp disk_pool_name -stype server_type -nodelete

Determine the media IDs in the disk pool as follows:

242

Managing media servers Removing a device host from the EMM database

install_path\NetBackup\bin\admincmd\bpimmedia -dp disk_pool_name -stype server_type -nodelete

Delete each media ID in the disk pool as follows:

install_path\NetBackup\bin\nbdelete -dt disk_type -media_id name

Removing a device host from the EMM database

The following applies only to NetBackup Enterprise Server. To remove a device host from the EMM database

1 2 3 4

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Devices > Media Servers. Select the host. On the Actions menu, select Enterprise Media Manager Database > Remove Device Host. Click Yes in the confirmation dialog box.

Section

Configuring storage

Chapter 7. Configuring robots and tape drives Chapter 8. Configuring tape media Chapter 9. Inventorying robots Chapter 10. Configuring disk storage Chapter 11. Configuring storage units Chapter 12. Staging backups Chapter 13. Configuring storage unit groups Chapter 14. Configuring storage lifecycle policies

244

Chapter

Configuring robots and tape drives

This chapter includes the following topics:

About NetBackup robot types Device configuration prerequisites About the device mapping files Downloading the device mapping files About configuring robots and tape drives About device discovery About robot control Configuring robots and tape drives Updating the device configuration by using the wizard Managing robots Managing tape drives Performing device diagnostics Verifying the device configuration About automatic path correction Enabling automatic path correction Replacing a device

246

Configuring robots and tape drives About NetBackup robot types

Updating device firmware About the NetBackup Device Manager Stopping and restarting the Device Manager

About NetBackup robot types

A robot is a peripheral device that mounts and unmounts media in tape drives. NetBackup uses robotic control software to communicate with the robot firmware. NetBackup classifies robots according to one or more of the following characteristics:

The communication method the robotic control software uses; SCSI and API are the two main methods. The physical characteristics of the robot. Library usually refers to a larger robot, in terms of slot capacity or number of drives. Stacker usually refers to a robot with one drive and low media capacity (6 - 12 media slots). The media type commonly used by that class of robots. HCART (1/2-inch cartridge tape) and 8 mm are examples of media types.

The following table lists the NetBackup robot types, with drive and slot limits for each type. To determine which robot type applies to the model of robot that you use, see the Symantec support Web site at the following URL:
http://entsupport.symantec.com

Table 7-1 Robot type

ACS

NetBackup robot types Drive limits

1680

Description
Automated Cartridge System

Slot limits
No limit

Note
API control. Drive limit determined by ACS library software host. SCSI control. SCSI control. SCSI control. API control. API control.

TL4 TL8 TLD TLH TLM

Tape library 4mm Tape library 8mm Tape library DLT Tape library Half-inch Tape library Multimedia

2 No limit No limit 256 250

15 16000 32000 No limit No limit

Configuring robots and tape drives Device configuration prerequisites

247

Device configuration prerequisites

Before you configure storage devices in NetBackup, ensure that the following prerequisites are accomplished:

The storage devices must be attached to the computer and recognized by the operating system. The server platforms that NetBackup supports may require operating system configuration changes to allow device discovery. The NetBackup Device Configuration Guide provides information about how to configure device drivers for the systems that NetBackup supports. If the host on which you configure devices in NetBackup is not the Enterprise Media Manager server, add it to the NetBackup additional servers list. See Servers properties on page 202. NetBackup hosts are added automatically to the list of additional servers if the EMM server is running when the host is installed. If the EMM server is not running, use the nbemmcmd -addhost command to add the host. See the NetBackup Commands Reference Guide.

About the device mapping files

NetBackup uses several files to determine which protocols and settings to use to communicate with storage devices. NetBackup also uses the files during device discovery and configuration. The device mapping files are available for download from the Symantec support site. The download packages contain the following files:

external_robotics.txt external_types.txt Readme.txt

In some cases, you can add support for new or upgraded devices without waiting for a release update from Symantec. To do so, download the current device mapping files package from the Symantec support Web site and configure NetBackup to use that file. For instructions, see the Readme.txt file that is supplied with the device mapping file package. Note: The contents of the device mapping files do not indicate support for any of the devices, only the ability to recognize and automatically configure them. See Downloading the device mapping files on page 248.

248

Configuring robots and tape drives Downloading the device mapping files

See About device discovery on page 249.

Downloading the device mapping files

Use the following procedure to download the current device mapping files and update the NetBackup Enterprise Media Manager database with their information. See About the device mapping files on page 247. To download the current device mapping files

Open the following location in your Web browser:

http://entsupport.symantec.com

In the Knowledge Base Search box, enter the following string (include the quotation marks) and then press Enter:
"device mappings package"

3 4 5

Select the package for your NetBackup release level and operating system. Download the archive file, either a .tar or .zip depending on operating system. Follow the instructions in the Readme.txt file to update the device mappings. The Readme.txt file contains instructions for both Windows and UNIX operating systems.

About configuring robots and tape drives

You can configure robots and tape drives in NetBackup as follows:
Device Configuration Wizard Symantec recommends that you use the Device Configuration Wizard to add, configure, and update the following types of devices in NetBackup:

Robots, including those attached to NDMP hosts Tape drives, including those attached to NDMP hosts Shared drives (for NetBackup Shared Storage Option configurations only)

The wizard discovers the devices that are attached to the media servers and helps you configure them. See About device discovery on page 249. See Configuring robots and tape drives by using the wizard on page 253.

Configuring robots and tape drives About device discovery

249

Manually

Alternatively, you can add robots and drives manually as follows:

Use menu options in the NetBackup Administration Console. See Adding a robot on page 253. See Adding a tape drive on page 258. Use NetBackup commands. See NetBackup Commands Reference Guide.

Manual methods do not use device discovery. If you add a robot and drives, first add the robot and then add the drives that are in the robot.

Device configuration examples are available. See the NetBackup Device Configuration Guide.

About device discovery

Device discovery is an exploratory method that determines which peripheral devices a host can detect. Detection depends on physical attachment (SCSI, Fibre Channel, and so on) and device state (on and responding or off and not responding). Detection also depends on host operating system device-layer configuration. The goal of device discovery is to provide information to enable fully or partially automatic configuration of peripherals for use with NetBackup. Device discovery provides data that correlates the devices that are interconnected across multiple hosts or multiple host bus adapters on the same host. To discover devices, NetBackup issues SCSI pass-through commands through operating system device files (on UNIX) or APIs (on Windows). The storage devices must be attached to the computer and recognized by the operating system. A pass-through path to a device must exist. The operating systems that NetBackup supports may require configuration changes to allow device discovery. The NetBackup Device Configuration Guide provides information about how to configure device drivers for the systems that NetBackup supports. NetBackup can discover the following types of devices:

SCSI-based robotic libraries (such as changers, autoloaders, and stackers) SCSI-based tape drives Native parallel SCSI, Fibre Channel Protocol (FCP) and FC-AL (loop) connections SCSI over IP (reported)

250

Configuring robots and tape drives About device discovery

API type robots, such as ACS, TLM, and TLH robots NDMP devices that run NDMP version 3 or later

See Enabling automatic path correction on page 284.

About device serialization

Device serialization is a firmware feature that allows device identification and configuration. A unique serial number identifies a device. NetBackup determines device relationships by comparing serial numbers from multiple sources that refer to the same device. If both a robotic library and a drive fully support serialization, NetBackup can determine the drive's position (or address) in the robotic library. Most robots and drives support device serialization. If a device supports serialization, the following actions occur when NetBackup queries the device:

Each robot and each drive return a unique serial number. Each robot also returns the number of drives and the serial number for each of the drives in the robot. NetBackup uses the information to determine the correct drive number for each drive in the robot.

If a device does not support serialization, ask the vendor for a new firmware revision that returns serial numbers. Even with the proper firmware, some devices require the vendor to perform other actions to enable serialization for the device. If you know that the devices do not support serialization, make sure that you follow the maximum configuration limits that the devices allow. You also must coordinate the drives to their device files or SCSI addresses so you can configure them correctly. See Correlating tape drives and SCSI addresses on Windows hosts on page 268. The more devices in the configuration that do not support serialization, the greater the chance of configuration problems by using the Device Configuration Wizard.

About adding devices without discovery

NetBackup supports some devices that cannot be discovered automatically. NetBackup also supports some devices that require user intervention during the discovery process. To add and configure those devices, select NetBackup Administration Console > Media and Device Management or use the tpconfig command.

Configuring robots and tape drives About robot control

251

For the devices that NetBackup cannot discover or that do not have serial numbers, automatic device path correction is limited.

About robot control

When you add a robot to NetBackup manually, you must configure how the robot is controlled. The New Robot dialog box includes a section named Robot control, in which you configure the control options. See Robot control (robot configuration options) on page 255. Table 7-2 lists the information that is required to configure the three robot control types (local, NDMP, and remote). The information that is required depends on the robot type and the media server type. Table 7-2 Robot type
ACS

Robot control information Media server type

Windows, AIX, Solaris SPARC, HP-UX (except HP IA64), and Linux (except Linux64) All UNIX Windows UNIX Windows Windows, AIX, Solaris SPARC, HP-UX (except HP IA64), and Linux (except Linux64) All UNIX Windows Windows, AIX, Solaris SPARC, HP-UX (except HP IA64), and Linux (except Linux64) All

Robot control
NDMP

Information required for configuration

NDMP host name and robot device

ACS TL4 TL4 TL8 TL8 TL8

Remote Local Local Local Local NDMP

ACSLS host Robotic device file Robot device or SCSI coordinates Robotic device file Robot device or SCSI coordinates NDMP host name and robot device

TL8 TLD TLD TLD

Remote Local Local NDMP

Robot control host Robotic device file Robot device or SCSI coordinates NDMP host name and robot device

TLD

Remote

Robot control host

252

Configuring robots and tape drives Configuring robots and tape drives

Table 7-2 Robot type

TLH

Robot control information (continued) Media server type

All (except Solaris Opteron, HP IA64, AIX, Linux, and Linux64) AIX Windows, AIX, Solaris SPARC, HP-UX (except HP IA64), and Linux (except Linux64) All (except Solaris Opteron, Linux64)

Robot control
Local

Information required for configuration

Library name

TLH TLH

Local NDMP

LMCP device file NDMP host name and robot device

TLH

Remote

Robot control host

TLM

All (except Linux64 and HP IA64) Remote

DAS/SDLC server

Library sharing example

Figure 7-1 shows library sharing with two servers using two drives in a TLD robot. The robotic control for the robot is on the host that is named eel. One drive in the robot is connected to eel and the other is connected to the host shark. Host eel is the robot control host. To configure this robot on host eel, select Robot is controlled locally by this device host. To configure this robot on host shark, select Robot control is handled by a remote host. Then, enter eel for the Robot control host. Figure 7-1
eel

Robot control host example

shark

TLD Robotic Control

Drive 1

Drive 2

TLD robot (HP EML E-Series)

Configuring robots and tape drives

Symantec recommends that you use the NetBackup Device Configuration Wizard to configure robots and drives. However, you can add robots and drives manually.

Configuring robots and tape drives Configuring robots and tape drives

253

Configuring robots and tape drives by using the wizard

Symantec recommends that you use the Device Configuration Wizard to configure robots and drives. The wizard configures a robot, its drives, and a storage unit. To configure robots and drives by using the wizard

1 2

In the NetBackup Administration Console, in the left pane, click Media and Device Management. In the right pane, click the Configure Storage Devices and follow the wizard instructions. The properties you can configure depend on the robot type, the host type, and the robot control.

Adding a robot
When you add a robot manually, you must specify how the robot is controlled. See About NetBackup robot types on page 246. See About robot control on page 251. After you add a robot, you should add the robot's drives. See Adding a tape drive on page 258. Note: Symantec recommends that you use the Device Configuration Wizard to add and update tape storage devices. To add a robot using the Actions menu

1 2

In the NetBackup Administration Console, expand Media and Device Management > Devices. On the Actions menu, select New > New Robot.

254

Configuring robots and tape drives Configuring robots and tape drives

In the Add Robot dialog box, specify the properties for the robot. The properties you can configure depend on the robot type, the host type, and the robot control. See Robot configuration options on page 254.

4 5

After you specify properties, click OK. If the device changes are complete, select Yes on the Restart Device Manager dialog box. If you intend to make other changes, click No; you can restart the Device Manager after you make the final change. If you restart the Device manager, any backups, archives, or restores that are in progress also may be stopped.

Robot configuration options

The following topics describe the robot properties that you can configure. The properties that you can configure depend on the robot type, host type, and robot control selections that you make in the dialog box.

Configuring robots and tape drives Configuring robots and tape drives

255

Device host (robot configuration option)

Specifies the host to which the device is attached.

Robot type (robot configuration option)

Specifies the type of robot. To locate the robot type to use for specific vendors and models, see the Symantec support Web site:
http://entsupport.symantec.com

Robot number (robot configuration option)

Specifies a unique, logical identification number for the robotic library. This number identifies the robotic library in displays (for example, TLD (21)) and is also used when you add media for the robot. For NetBackup Enterprise Server environments, do the following:

Robot numbers must be unique for all robots on all hosts in the configuration, regardless of the robot type or the host that controls them. For example, if you have two robots, use different robot numbers even if different hosts control them. If you add a robot that is controlled by a remote device host, use the same robot number for that robot on all device hosts. If the robot has its robotic control and drives on different hosts, specify the same robot number in all references to that library. That is, use the same robot number on the hosts with the drives as you do on the host that has the robotic control. A Tape Library DLT robot is one that allows separate robotic control and drive hosts. Examples are available. See the NetBackup Device Configuration Guide.

Robot control (robot configuration options)

The Robot control section of the dialog box specifies the type of control for the robot. The options that you configure depend on the robot type and the media server type. Table 7-3 Property Description Robot configuration properties

Robot control is Specifies that an NDMP host controls the robot. attached to an NDMP You must configure other options (depending on the robot type and device host type). host

256

Configuring robots and tape drives Configuring robots and tape drives

Table 7-3 Property Description

Robot configuration properties (continued)

Robot is controlled Specifies that the host to which the robot is attached controls the robot. locally by this device You must configure other options (depending on the robot type and device host type). host Robot control is handled by a remote host ACSLS host Specifies that a host other than the device host controls the robot. You must configure other options (based on the selected robot type and device host platform). Specifies the name of the Sun StorageTek ACSLS host; the ACS library software resides ACSLS host. On some UNIX server platforms, this host can also be a media server or EMM server. The ACS library software component can be any of the following: Automated Cartridge System Library Software (ACSLS) Examples are available. See the NetBackup Device Configuration Guide. STK Library Station

Storagenet 6000 Storage Domain Manager (SN6000). This STK hardware serves as a proxy to another ACS library software component (such as ACSLS).

Note: If the device host that has drives under ACS robotic control is a Windows server, STK
LibAttach software must also be installed. Obtain the appropriate LibAttach software from STK. See the Symantec support Web site for the latest compatibility information. An overview of ACS robots is available. See the NetBackup Device Configuration Guide. DAS server Specifies the name of the ADIC DAS/SDLC server that controls TLM robots. This server is an OS/2 workstation near or within the robot cabinet or a Windows server near the ADIC Scalar library. An overview of TLM robots is available. See the NetBackup Device Configuration Guide.

Configuring robots and tape drives Configuring robots and tape drives

257

Table 7-3 Property

Library name

Robot configuration properties (continued)

Description
The following applies only to a TLH robot on NetBackup Enterprise Server only. For UNIX device hosts (except AIX), specifies the library name that is configured on the UNIX host. For Windows devices hosts, do the following:

Determine the library name by viewing the C:\winnt\ibmatl.conf file. For example, in the following example entry in that file, 3494AH is the library name: 3494AH 176.123.154.141 ibmpc1

Enter the library name.

An overview of TLH robots is available. See the NetBackup Device Configuration Guide. LMCP device file Applies to NetBackup Enterprise Server on an AIX device host only. Specifies the name of the Library Manager Control Point device file name for TLH robot types. Use the same name that is configured on the AIX device host. NDMP host name Robot control host Specifies the name of the NDMP host to which the robot is attached. Specifies the host that controls the robot. The name of the host on which the robot information is defined for TL8, TLD, or TLH robots. Robot device The following applies to a Windows device host only. Specifies the name of the robot device. Click Browse and then select a robot from the list that appears in the Devices dialog box. If the discovery operation fails to discover a robot, click More in the Devices dialog box. Enter either the Port, Bus, Target, and LUN numbers or the device name in the next dialog box. If the browse operation fails for any other reason, a dialog box appears that lets you enter the information. You can find Port, Bus, Target, and LUN numbers by using Windows management tools. If the browse operation does not find attached robots, an error dialog box appears.

258

Configuring robots and tape drives Configuring robots and tape drives

Table 7-3 Property

Robotic device file

Robot configuration properties (continued)

Description
UNIX device host only. Specifies the device file that is used for SCSI connections. The device files are located in the /dev directory tree on the device host. To specify the robotic device file, click Browse and then select a robotic device file from the list that appears in the Devices dialog box. If the browse operation fails to show all of the attached robots, click More. Enter the path of the device file in the robotic device file field. If the browse operation fails to show all of the attached robots, click Other Device. Enter the path of the device file in the next dialog box. If the browse operation does not find attached robots, an error dialog box appears. Information about how to add device files is available. See the NetBackup Device Configuration Guide.

Robot device path

NDMP host only. Specifies the name of the robotic device that is attached to the NDMP host.

Port, Bus, Target, LUN Windows systems only. The Port, Bus, Target, and LUN are the SCSI coordinates for the robotic device. To specify the SCSI coordinates of the device, enter the Port, Bus, Target, and LUN.

Adding a tape drive

Use the following procedures to add a tape drive manually. Note: Symantec recommends that you use the Device Configuration Wizard to add and update tape storage devices.

Configuring robots and tape drives Configuring robots and tape drives

259

To add a drive using the Actions menu

1 2

In the NetBackup Administration Console, expand Media and Device Management > Devices. On the Actions menu, select New > New Tape Drive.

For the drive name, do one of the following:

Enter a name for the drive in the Drive name field. See Drive name (tape drive configuration option) on page 260. Select Use drive name seed. This option uses rules to name the drive automatically. See About drive name rules on page 263. See Configuring drive name rules on page 264.

To configure the host and path information, click Add in the Host and path information area of the dialog box. See Host and path information (tape drive configuration options) on page 261.

In the Drive information area of the dialog box, configure the drive properties. The properties depend on the drive type and host server type. See Drive information (tape drive configuration options) on page 261.

260

Configuring robots and tape drives Configuring robots and tape drives

6 7

After you configure all of the properties, click OK. If the device changes are complete, select Yes on the Restart Device Manager dialog box. If you intend to make other changes, click No; you can restart the Device Manager after you make the final change. If you restart the device manager, any backups, archives, or restores that are in progress also may be stopped. The initial drive status is UP, so the drive is available as soon as you restart the Device Manager. To change the status of the drive, select Device Monitor.

Adding a shared tape drive

Symantec recommends that you use the Device Configuration Wizard to add, configure, and update shared drives. The NetBackupDeviceConfigurationWizard is the easiest method for adding shared drives in a Shared Storage Option configuration. See the NetBackup Administrator's Guide, Volume II.

Tape drive configuration options

You can specify properties when you add a tape drive or change the properties of a drive. The properties that you can specify depend on the drive type, server platforms, or NetBackup server types.

Drive name (tape drive configuration option)

Specifies the name of the drive. Each drive name must be unique. Symantec recommends that you use descriptive names. Drive names are limited to 48 characters. Alternatively, use the drive name seed to create a unique drive name.

Use drive name seed (tape drive configuration option)

Adds a drive only. Select to use drive name rules to assign names to drives automatically. To configure drive name rules, click Configure. See About drive name rules on page 263. See Configuring drive name rules on page 264.

Configuring robots and tape drives Configuring robots and tape drives

261

Host and path information (tape drive configuration options)

Use the Host and path information group box to add or change paths to the drive. You can specify multiple paths to the same physical device. If you specify multiple paths for a drive, it becomes a shared drive. To add a drive path, click Add. To change a drive path, click Change. To delete a drive path, click Remove. See About SCSI reserve on drive paths on page 266. See Drive path options on page 266.

Drive information (tape drive configuration options)

The Drive information group box includes drive properties. The properties that you can specify depend on the drive type, server platforms, and NetBackup server types. Table 7-4 describes the tape drive configuration options. Table 7-4 Option
Drive type

Tape drive configuration options

Description
Specifies the type of drive. The following are the valid drive types:

4MM (4mm cartridge) 8MM (8mm cartridge) 8MM2 (8mm cartridge 2) 8MM3 (8mm cartridge 3) DLT (DLT cartridge) DLT2 (DLT cartridge 2) DLT3 (DLT cartridge 3) DTF (DTF cartridge) HCART (1/2-inch cartridge) HCART2 (1/2-inch cartridge 2) HCART3 (1/2-inch cartridge 3) QSCSI (1/4-inch cartridge)

Drive is in a robotic library

Specifies that the drive is in a robot. If the drive is a stand-alone drive (it is not in a robot), do not select this option. If you select this option, configure the Robotic library and Robot drive number fields.

262

Configuring robots and tape drives Configuring robots and tape drives

Table 7-4 Option Description

Tape drive configuration options (continued)

Cleaning Frequency Specifies the frequency-based cleaning for the drive. NetBackup does not support drive cleaning in some robot types. If you want to configure a frequency-based cleaning schedule for the drive, set the number of mount hours between each drive cleaning. When you add a drive or reset the mount time to zero, NetBackup records the amount of time that volumes have been mounted in that drive. The default frequency is zero. When the accumulated mount time exceeds the time you specify for cleaning frequency, drive cleaning occurs if the following are true:

If the drive is in a robotic library that supports drive cleaning If a cleaning cartridge is defined in that robotic library If the cleaning cartridge is compatible with the drive that needs to be cleaned If the cleaning cartridge has a nonzero number of cleanings that remain

NetBackup resets the mount time when the drive is cleaned. Drives can also be cleaned from the Device Monitor. If you do not specify a cleaning frequency, you can still use automated drive cleaning with the TapeAlert feature. Information about TapeAlert drive cleaning is available. See the NetBackup Administrator's Guide for Windows, Volume II. Serial Number Robotic library A read-only field that shows the serial number of the drive. Specifies a robot that controls the drive. You can select any configured robot that can control the drive.

Robot drive number Specifies the physical location in the robot of the drive. When you add more than one drive to a robot, you can add the physical drives in any order. For example, you can add drive 2 before drive 1. The correct robot drive number is critical to the proper mounting and utilization of media. You must determine which logical device name (Windows) or the device file (UNIX) identifies which physical drive in the robot. You should correlate the drive serial number with drive serial number information from the robot. You must determine which physical drive in the robot is identified by the logical device name. See Correlating tape drives and SCSI addresses on Windows hosts on page 268. NetBackup does not detect incorrect drive number assignment during configuration; however, an error occurs when NetBackup tries to mount media on the drive.

Note: The Robot drive number property does not apply when you add drives to API robots.
API robots are ACS, TLH, and TLM type in NetBackup.

Configuring robots and tape drives Configuring robots and tape drives

263

Table 7-4 Option

ACS, LSM, Panel, Drive

Tape drive configuration options (continued)

Description
Specify the drive locations within an ACS robot. The following information applies only to the ACS robot drive. The ACS property specifies the physical location of the drive within the robot. During installation, the correlation between the physical drive in the robot and the device file you specified earlier represents. You establish this correlation during installation. The drive location properties are as follows: ACS Number - specifies the index (in ACS library software terms) that identifies the robot that has this drive. LSM Number - specifies the Library Storage Module that has this drive.

Panel Number - specifies the robot panel where this drive is located. Drive Number - specifies the physical number of the drive (in ACS library software terms).

IBM device number

Specifies the IBM device number of the drive within the robot. This property applies only to the TLH robot drive. Specifies the DAS/SDLC drive name of the drive within the robot. This property applies only to the TLM robot drive.

DAS drive name

About drive name rules

The drive name rules define the rules NetBackup uses to name drives. The default, global drive name rule creates names in the following format: vendor ID.product ID.index If you use the default global rule when you add Quantum DLT8000 drives, the drives are named as follows: The first one that you add is named QUANTUM.DLT8000.000, the second one QUANTUM.DLT8000.001, and so on. You can change the default, global drive name rule. You also can create drive name rules for specific device hosts (each device host can have its own rule). Host-specific rules override the global rule for the devices that are attached to the specified host. Only one global rule can exist; it is used for all connected device hosts. The global rule is used for the drive name unless a host-specific rule or local rule is specified. Drive names are limited to 48 characters. Use any of the following drive attributes as part of a drive name rule:

Host name

264

Configuring robots and tape drives Configuring robots and tape drives

Robot number Robot type Drive position Drive position information varies depending on the robot type. Drive position information can be ACS coordinates, TLM or TLH vendor drive name, or the robot drive number. Drive type Serial number Vendor ID Product ID Index

A Custom Text field is also available which accepts any of the allowable drive name characters. See Configuring drive name rules on page 264.

Configuring drive name rules

Use the following procedure to configure the drive name rules.

Configuring robots and tape drives Configuring robots and tape drives

265

To configure drive name rules

In the NetBackup Administration Console, expand Media and Device Management > Drives. Expand the Actions > New > New Tape Drive menu. See Adding a tape drive on page 258.

In the New Tape Drive dialog box, click Configure. Alternatively, if you use the NetBackup Device Configuration Wizard, click Configure Drive Name Rules in the Device Hosts screen.

In the Configure Drive Name Rules dialog box, configure the rules for naming drives:

To change the global rule, select Global Rule. To create a local rule, select the check box for the device host. Select the fields from which to create the drive name from the list of available fields. Click Add>> to make a field part of the rule. To add own text to the drive name rule, enter the text in the Custom Text field and click the Add button. Use the Move Up and Move Down buttons to change the order of the fields that are defined for the rule. Click Create Rule to finalize the rule.

266

Configuring robots and tape drives Configuring robots and tape drives

If you use <host name> in the rule and the drive is a shared drive, the name of the first host that discovers the drive is used as the host name. The name for a shared drive must be identical on all servers that share the drive.

Adding a tape drive path

Usually, you add a tape drive path when you add a drive to NetBackup. Use the following procedure to add a drive path. To add a tape drive path

In the NetBackup Administration Console, expand Media and Device Management > Devices > Drives. In the Actions menu, select New > New Tape Drive. In the New Tape Drive dialog box, click Add. In the Add Path dialog box, configure the properties for the drive path. The properties that you can specify depend on drive type, server platform, or NetBackup server type. See About SCSI reserve on drive paths on page 266. See Drive path options on page 266.

About SCSI reserve on drive paths

NetBackup lets you configure exclusive access protection to tape drives so that other host bus adaptors (HBAs) cannot control the drives during the reservation. The Enable SCSI Reserve host property configures the protection for each media server. See Media properties on page 161. More information about how NetBackup reserves drives is available. See the NetBackup Administrators Guide, Volume II.

Drive path options

The following table describes the options to add a drive path. Table 7-5 Option
Host name Enable host path

Add drive path options

Description
Specifies the device host for the drive. Specifies that the path is active and that NetBackup can use it for backups and restores.

Configuring robots and tape drives Configuring robots and tape drives

267

Table 7-5 Option

NDMP host

Add drive path options (continued)

Description
Specifies the NDMP host for the device (if an NDMP host is configured in your NetBackup environment). Additional information is available about NDMP drives. See the NetBackup for NDMP Administrators Guide.

Override SCSI Reserve Specifies the SCSI reserve override setting for the drive path. settings Server Default. Use the SCSI reserve protection setting configured for the media server. If the setting for the media server is no protection, other HBAs can send the commands that can cause a loss of data to the tape drives. SPC-2 SCSI Reserve. This option provides SCSI reserve and release protection for SCSI devices that conform to the reserve and release management method that is defined in the SCSI Primary Commands - 2 (SPC-2) standard. SCSI Persistent Reserve. This option provides SCSI persistent reserve in and persistent reserve out protection for SCSI devices that conform to the SCSI Primary Commands 3 (SPC-3) standard. Global SCSI reserve properties are configured in the Media host properties. See Media properties on page 161. Port, Bus, Target, and LUN This path is for a Network Attached Storage Device To specify the SCSI coordinates of the device, enter the Port, Bus, Target, and LUN. The device attributes on Windows systems cannot change during a NetBackup operation. Specifies that the path is for a network attached storage (NAS) device.

About no rewind device files

UNIX servers only. Although both rewind and no rewind on close device files are usually available, NetBackup requires only the no rewind device file. A no rewind device remains at its current position on a close operation. On some versions of UNIX, the device file name may be preceded or followed by the letter n. Device files are in the /dev directory on the UNIX host. If the entries do not exist, create them as explained in the NetBackup Device Configuration Guide.

268

Configuring robots and tape drives Configuring robots and tape drives

Correlating tape drives and SCSI addresses on Windows hosts

If your tape drives do not support device serialization, you may have to determine which logical device name or SCSI address matches the physical drive. You also may have to do so if you add the tape drives manually. To correlate tape drives and SCSI addresses on Windows hosts

1 2

Note the SCSI target of the drive. Correlate the SCSI target to the drive address by using the robots interface panel. Alternatively, examine the indicators on the rear panel of the tape drive. Determine the physical drive address (for example, number) by checking labels on the robot. Configure the robot in NetBackup and then add the drives. When you add the drives, ensure that you assign the correct drive address to each set of SCSI coordinates. Optionally, use the appropriate NetBackup robotic test utility to verify the configuration. Information about the robotic test utilities is available. See the NetBackup Troubleshooting Guide.

3 4

To verify the device correlation Windows

1 2

Stop the NetBackup Device Manager (ltid). Restart ltid, which starts the Automatic Volume Recognition process (avrd). Stop and restart ltid to ensure that the current device configuration has been activated. The following point applies only to NetBackup Enterprise Server. If robotic control is not local to this host, also start the remote robotic control daemon.

3 4

Use the robotic test utility to mount a tape on a drive. Use the NetBackup Device Monitor to verify that the tape was mounted on the correct robot drive.

Windows device correlation example

Assume a TLD robot includes three drives at the following SCSI addresses:
Drive 1 5,0,0,0

Configuring robots and tape drives Updating the device configuration by using the wizard

269

Drive 2 Drive 3

5,0,1,0 5,0,2,0

Also assume that you requested that the tape be mounted on drive 1. If the SCSI coordinates for the drive are configured correctly, the Administration Console Device Monitor shows that the tape is mounted on drive 1. If the Device Monitor shows that the tape is mounted on a different drive, the SCSI coordinates for that drive are not correctly configured. For example, if the Device Monitor shows the tape mounted on drive 2, the SCSI coordinates for drive 1 are incorrect. Replace the drive 1 SCSI coordinates (5,0,0,0) with the correct SCSI coordinates (5,0,1,0) for drive 2. You also know that the SCSI coordinates for drive 2 are incorrect. Possibly, the SCSI coordinates were swapped during configuration. Use the robotic test utility to unload and unmount the tape from drive 1. Repeat the test for each drive. The following point applies only to NetBackup Enterprise Server. If the data path to the drive where the tape was mounted is not on the host with direct robotic control, you may have to unload the drive with a command from another host or from the drives front panel.

Updating the device configuration by using the wizard

Symantec recommends that you use the Device Configuration Wizard to update the NetBackup device configuration when hardware changes occur. Update the configuration for all storage device changes. For example, if you add or delete a robot or drive or add a new SCSI adapter in a host, update the configuration. Do not update the device configuration during backup or restore activity. To update the device configuration by using the wizard

1 2

In the NetBackup Administration Console, select Media and Device Management > Devices. From the list of wizards in the Details pane, click Configure Storage Devices and follow the wizard instructions.

Managing robots
You can perform various tasks to manage your robots.

270

Configuring robots and tape drives Managing robots

Changing robot properties

Use the following procedure to change the configuration information for a robot. To change robot properties

1 2 3 4

In the NetBackup Administration Console, expand Media and Device Management > Devices > Robots. In the Robots pane, select the robotic library you want to change. Click Edit > Change. In the Change Robot dialog box, change the properties as necessary. The properties that you can change depend on the robot type, the host type, and the robot control. See Robot configuration options on page 254.

If the device changes are complete, select Yes on the Restart Device Manager dialog box. If you intend to make other changes, click No; you can restart the Device Manager after you make the final change. If you restart the Device manager, any backups, archives, or restores that are in progress also may be stopped.

Configuring a robot to operate in manual mode

You can configure NetBackup so that storage unit mount requests are displayed in the Device Monitor if the robot or drive is down. Pending requests appear in the Device Monitor, and you can assign these mount requests to drives manually. See About pending requests for storage units on page 868. To configure a robot so that storage unit mount requests appear in the Device Monitor

Set the robot to operate in Pend If Robot Down (PIRD) mode by using the following command:
installpath\Volmgr\bin\tpconfig -update -robot robot_number -pird yes

Deleting a robot
Use the following procedure to delete a robot or robots when the media server is up and running. Any drives that are configured as residing in a robot that you delete are changed to standalone drives.

Configuring robots and tape drives Managing robots

271

Any media in the deleted robot is also moved to standalone. If the media is no longer usable or valid, delete it from the NetBackup configuration. See Deleting a volume on page 307. If the media server is down or the host has failed and cannot be recovered, you can delete its robots by using a different procedure. See Deleting all devices from a media server on page 240. To delete a robot

1 2 3 4 5

In the NetBackup Administration Console, expand Media and Device Management > Devices. Select Robots in the tree pane. In the Robots pane, select the robot or robots you want to delete. On the Edit menu, select Delete. At the prompt, click Yes.

Moving a robot and its media to a new media server

Use the following process to move a robot and its media from one server (the old_server) to a different media server (the new_server). Table 7-6 Task
Determine which tapes on the old_server contain NetBackup images that have not expired.

Move a robot and media to a new server overview Procedure

Run the following bpmedialist command: bpmedialist -mlist -l -h old_server The -l option produces one line of output per tape.

Move the tapes in the robot that is attached to the old_server to non-robotic status (standalone).

See Moving volumes by using the Actions menu on page 320.

272

Configuring robots and tape drives Managing tape drives

Table 7-6 Task

Move a robot and media to a new server overview (continued) Procedure

Move the media logically from the old_server If both the old_server and the new_server are at NetBackup 6.0 or to the new_server. later, run the following command: bpmedia -movedb -allvolumes -oldserver old_server -newserver new_server If either server runs a NetBackup version earlier than 6.0, run the following command for each volume that has active images: bpmedia -movedb -ev media_ID -oldserver old_server -newserver new_server For the media that has active images, see the bpmedialist command output from the first step of this process. Configure NetBackup so that restore requests See Forcing restores to use a specific server on page 137. are directed to the new_server. Shut down both the old_server and the new_server. Disconnect the robot from the old_server. See the vendor's documentation.

See the vendor's documentation.

Connect the robot to the new_server. Verify See the vendor's documentation. that the operating system on the new media server recognizes the robots. Use the NetBackup Device Configuration Wizard to add the robots and drives to the media servers. Create the appropriate NetBackup storage units. See Configuring robots and tape drives by using the wizard on page 253.

See Creating a storage unit on page 399.

Inventory the robots that are attached to the See Updating the volume configuration with a robot's contents new_server. The inventory updates the on page 345. location of all tapes in the robot.

Managing tape drives

You can perform various tasks to manage tape drives.

Configuring robots and tape drives Managing tape drives

273

Changing a drive comment

You can change the comment associated with a drive. Drive comments appear in the Drive Status pane. To change a drive comment

1 2 3 4 5

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Status pane, select a drive or select multiple drives. On the Actions menu, select Change Drive Comment. The dialog box shows the current comment (if any is currently configured). (Shared Storage Option.) For a shared drive, select the host and the device path to the selected drive that you want to change. You can change the comment for any or all of the host and the device paths. Add a comment or change the current drive comment. See NetBackup naming conventions on page 897.

Click OK.

About downed drives

NetBackup downs a drive automatically when there are read or write errors that surpass the threshold within the time window. The default drive error threshold is 2. That is, NetBackup downs a drive on the third drive error in the default time window (12 hours). Common reasons for write failures are dirty write heads or old media. The reason for the action is logged in the NetBackup error catalog (view the Media Logs report or the All Log Entries report). If NetBackup downs a device, it is logged in the system log. You can use the NetBackup nbemmcmd command with the --drive_error_threshold and -time_window options to change the default values. Additional information about nbemmcmd is available. See NetBackup Commands Reference Guide. To reverse a down action, in the NetBackup Administration Console, expand Media and Device Management > Device Monitor to set the device to Up. See Changing a drive operating mode on page 274.

274

Configuring robots and tape drives Managing tape drives

Changing a drive operating mode

Usually you do not need to change the operating mode of a drive. When you add a drive, NetBackup sets the drive state to UP in Automatic Volume Recognition (AVR) mode. Other operating mode settings are used for special purposes. The drive operating mode is displayed and changed in the Device Monitor window. To change the mode of a drive

1 2 3 4

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Status pane, select a drive or select multiple drives. From the Actions menu, choose the command for the new drive operating mode. Note that Up Drive, Operator control applies only to standalone drives.

If the drive is configured with multiple device paths or is a shared drive (Shared Storage Option), a dialog box appears that contains a list of all device paths to the drive. Select the path or paths to change. Click OK.

Changing a tape drive path

Use the following procedure to change a drive path. See Changing a drive path operating mode on page 274. To change a drive path

In the NetBackup Administration Console, expand Media and Device Management > Devices > Drives. Double-click on the drive that you want to change. In the Change Tape Drive dialog box, select the drive path. In the Change Path dialog box, configure the properties for the drive path. The properties you can change depend on drive type, server platform, or NetBackup server type. See About SCSI reserve on drive paths on page 266. See Drive path options on page 266.

Changing a drive path operating mode

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. In the right pane of the Device Monitor dialog

Configuring robots and tape drives Managing tape drives

275

box, the Drive Paths pane shows path information for drives if one of the following is true:

Multiple (redundant) paths to a drive are configured Any drives are configured as shared drives (Shared Storage Option)

To change a drive path operating mode

1 2 3 4

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Paths pane, select a path or select multiple paths. On the Actions menu, choose a command for the path action, as follows:

Up Path Down Path Reset Path

Changing tape drive properties

Use the following procedure to change the configuration information for a drive. To change drive properties

1 2 3 4

In the NetBackup Administration Console, expand Media and Device Management > Devices > Drives. In the details pane, select the drive you want to change. Click Edit > Change. In the Change Tape Drive dialog box, change the properties of the drive. The properties depend on the drive type and host server type. See Tape drive configuration options on page 260.

5 6

After you change the properties, click OK. If the device changes are complete, select Yes on the Restart Device Manager dialog box. If you intend to make other changes, click No; you can restart the Device Manager after you make the final change. If you restart the Device Manager, any backups, archives, or restores that are in progress also may be stopped. The initial drive status is UP, so the drive is available as soon as you restart the Device Manager.

276

Configuring robots and tape drives Managing tape drives

Changing a tape drive to a shared drive

Change a drive to a shared drive by adding paths to a currently configured drive. To configure and use a shared drive, a Shared Storage Option license is required on each master server and media server. To change a drive to a shared drive

1 2 3 4 5 6

In the NetBackup Administration Console, expand Media and Device Management > Devices. Select Drives in the tree pane. Select the drive you want to change in the Drives pane. Click Edit > Change. In the Change Tape Drive dialog box, click Add. In the Add Path dialog box, configure the properties for the hosts and paths that share the drive.

Cleaning a tape drive from the Device Monitor

When you add a drive to NetBackup, you configure the automatic, frequency-based cleaning interval. Also, you can perform an operator-initiated cleaning of a drive regardless of the cleaning frequency or accumulated mount time of the drive. However, appropriate cleaning media must be added to NetBackup. After you clean a drive, reset the mount time. See Resetting the mount time on page 278. See the NetBackup Administrators Guide, Volume II. Drive cleaning functions can also be performed from the Activity Monitor. See Cleaning tape drives from the Activity Monitor on page 863. To clean a tape drive

1 2 3

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If a license that activates disk based features is installed, select the Drives tab. In the Drive Status pane, select the drive to clean.

Configuring robots and tape drives Managing tape drives

277

On the Actions menu, expand Drive Cleaning > Clean Now. NetBackup initiates drive cleaning regardless of the cleaning frequency or accumulated mount time. The Clean Now option resets the mount time to zero, but the cleaning frequency value remains the same. If the drive is a stand-alone drive and it contains a cleaning tape, NetBackup issues a mount request.

For a shared drive (Shared Storage Option), do the following: In the list of hosts that share the drive, choose only one host on which the function applies. The Clean Now function can take several minutes to complete, so the cleaning information in the Drive Details dialog box may not be updated immediately.

Deleting a drive
Use the following procedure to delete a drive or drives when the media server is up and running. If the media server is down or the host has failed and cannot be recovered, you can delete its drives by using a different procedure. See Deleting all devices from a media server on page 240. To delete a drive

1 2 3 4 5

In the NetBackup Administration Console, expand Media and Device Management > Devices. Select Drives in the tree pane. Select the drive or drives that you want to delete from the Drives pane. On the Edit menu, select Delete. At the prompt, click Yes.

Resetting a drive
Resetting a drive changes the state of the drive. Usually you reset a drive when its state is unknown, which occurs if an application other than NetBackup uses the drive. When you reset the drive, it returns to a known state before use with NetBackup. If a SCSI reservation exists on the drive, a reset operation from the host that owns the reservation can help the SCSI reservation. If the drive is in use by NetBackup, the reset action fails. If the drive is not in use by NetBackup, NetBackup tries to unload the drive and set its run-time attributes to default values.

278

Configuring robots and tape drives Managing tape drives

Note that a drive reset does not perform any SCSI bus or SCSI device resets. Use the following procedure to reset a drive. To reset a drive

1 2 3 4 5 6

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Status pane, select a drive or select multiple drives. Select Actions > Reset Drive. If the drive is in use by NetBackup and cannot be reset, restart the NetBackup Job Manager to free up the drive. Determine which job controls the drive (that is, which job writes to or reads from the drive). In the NetBackup Administration Console, click on Activity Monitor. In the right pane of the Activity Monitor dialog box, select the Jobs tab and cancel the job. In the Activity Monitor, restart the NetBackup Job Manager, which cancels all NetBackup jobs in progress.

Resetting the mount time

You can reset the mount time of the drive. Reset the mount time to zero after you perform a manual cleaning. To reset the mount time

1 2 3 4 5

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Status pane, select a drive. Select Actions > Drive Cleaning > Reset Mount Time. The mount time for the selected drive is set to zero. If you use the Shared drive (Shared Storage Option), do the following: In the list of hosts that share the drive, choose only one host on which the function applies.

Setting drive cleaning frequency

When you add a drive to NetBackup, you configure the automatic, frequency-based cleaning interval. In the NetBackup Administration Console, expand Media and

Configuring robots and tape drives Managing tape drives

279

Device Management > Device Monitor to change the cleaning frequency that was configured when you added the drive. To set the cleaning frequency

1 2 3 4 5

In the NetBackup Administration Console, expand Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Status pane, select a drive. On the Actions menu, expand Drive Cleaning > Set Cleaning Frequency. Enter a time (hours) or use the arrow controls to select the number of mount hours between drive cleaning. The Cleaning Frequency option is not available for the drives that do not support frequency-based cleaning. This function is not available for shared drives. The drive cleaning interval appears in the Drive Details dialog box (Actions > Drive Details).

Viewing drive details

You can obtain detailed information about drives (or shared drives), such as drive cleaning, drive properties, drive status, host, and robotic library information. Use the following procedure to view the drive details. To view the drive details

1 2 3 4 5

In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, select the Drives tab. In the Drive Status pane, select a drive. Select Actions > Drive Details. The following applies only to NetBackup Enterprise Server: If you use the Shared drive for shared drives, you can view the drive control mode and drive index for each host that shares a drive. You also can view a list of hosts that share a drive.

280

Configuring robots and tape drives Performing device diagnostics

Performing device diagnostics

Diagnostic functions let you run and manage drive and robot diagnostic tests. Diagnostics are executed in an ordered sequence to verify the functionality of hardware devices. These tests can help you to troubleshoot drive or robot problems.

About device diagnostic tests

NetBackup diagnostic functions let you run and manage diagnostic tests. Diagnostics are performed in an ordered sequence to verify the functionality of hardware devices. These tests can help you to troubleshoot and drive problems.

Running a robot diagnostic test

Use this procedure to run diagnostic tests on TLD or TL8 robotic libraries. Ensure that the library to be tested is properly configured for use with NetBackup. The existing NetBackup robotic control daemons or processes are used for the test. Note: NetBackup does not support diagnostic tests for API-attached robotic tape libraries and other types of SCSI-attached libraries.

Configuring robots and tape drives Performing device diagnostics

281

To run a robot diagnostic test

1 2

In the NetBackup Administration Console, expand Media and Device Management > Devices. On the Actions menu, select Robot Diagnostics.

3 4 5

In the Robot Diagnostics dialog box, select the media server that is the Device Host for the robot that you want to test. In the Robot Name field, select the robot that you want to diagnose. Click Start to start the diagnostic tests. The Results window shows results of each step in the test. Operator intervention is required if the State column of the Results window contains Waiting. For example, a test step may prompt you to load a new tape into a drive before the test can continue.

If operator intervention is required, select the test step in the Results window and click Details to determine what you must do. Complete the requested operation task and then click Continue in the Test Details dialog box to resume the test

282

Configuring robots and tape drives Performing device diagnostics

To stop a test and change the device

Click Stop. The test ends after it performs any necessary clean-up work and updates the test records to reflect that the test run has been stopped.

2 3

In the Device Host and the Robot Name boxes, select the host and the robot that you want to test. Click Start to restart the diagnostic test.

Running a tape drive diagnostic test

NetBackup diagnostic functions let you run and manage diagnostic tests. Diagnostics are performed in an ordered sequence to verify the functionality of hardware devices. These tests can help you to troubleshoot drive problems. To run a tape drive diagnostic test

1 2 3 4 5

In the NetBackup Administration Console, expand Media and Device Management > Devices. On the Actions menu, select Drive Diagnostics. In the Drive Diagnostics dialog box, select the media server that contains the drive that you want to test in the Device Host box. In the Drive Name box, select the drive. Click Start to start the diagnostic tests. For robotic drives, the test media is loaded automatically. For a stand-alone drive, insert the prelabeled test tape that is shown in the Step Information column of the Results window. The Results window shows results of each step in the test.

If operator intervention is required, the State column of the Results window displays Waiting. For example, a test step may require that you to load a new tape into a drive before the test can continue. Complete the intervention and then click Continue. Select the test step in the Results window and click Details to determine what you must do. Complete the requested operation task and then click Continue in the Test Details dialog box to resume the test

Configuring robots and tape drives Verifying the device configuration

283

To stop a test and change the device

Click Stop. The test ends after it performs any necessary clean-up work and updates the test records to reflect that the test run has been stopped.

2 3

In the Device Host and the Drive boxes, select the host and the drive that you want to test. Click Start to restart the diagnostic test.

Managing a diagnostic test step that requires operator intervention

Operator intervention is required if the Status column of the Results display contains Waiting. For example, a test step may prompt for a new tape to be loaded into a drive before the test continues. To manage a diagnostic step

1 2

Complete the requested operations task. Click Continue to resume the test. If you clicked Details for a test step that requires operator intervention, you can click Continue from the Test Details dialog box.

Obtaining detailed information for a diagnostic test step

You can get information for a test step at any time during the test. To obtain detailed information for a diagnostic test step

1 2

Select a test step in the Results display. Click Details. A dialog box appears that displays information for the step. The information includes a brief explanation of the checks that are performed by a specific step and the instructions that are associated with any step that requires manual intervention. For example, a step may prompt for a new tape to be loaded into a tape drive before the diagnostic session continues.

Click Close to return to the Device Diagnostics dialog box.

Verifying the device configuration

Verify the device configuration by running the Device Configuration Wizard. However, some details of a device configuration cannot be validated without attempting tape mounts. Use the NetBackup robtest utility to mount tapes and validate the configuration.

284

Configuring robots and tape drives About automatic path correction

To verify robots and drives by using the wizard

1 2

In the NetBackup Administration Console, expand Media and Device Management > Devices. From the list of wizards in the Details pane, click Configure Storage Devices and follow the wizard instructions.

About automatic path correction

NetBackup automatic path correction recognizes if you change a device because the serial number of the new device is different than the serial number of the old device. NetBackup updates the device configuration automatically. NetBackup recognizes device changes as follows:

When the Device Manager (ltid) performs automatic path correction. When the Windows Plug-n-Play feature performs serial number checks.

By default, Windows and Linux systems are configured for automatic path correction. On other operating systems, you must enable it. See Enabling automatic path correction on page 284. In some circumstances, NetBackup may be unable to determine the correct serial number in a small number of tape drives and robotic libraries. For example, NetBackup may configure serialized devices as unserialized or configure a device with the wrong serial number. If so, a device may be unusable (such as the tape drive may be downed). To resolve such a problem, do one of the following actions:

Configure the new device by using the NetBackup Device Configuration Wizard. See Configuring robots and tape drives by using the wizard on page 253. The server operating system must recognize the device before you can configure it in NetBackup. Device configuration can require remapping, rediscovery, and possibly a restart of the operating system. See the NetBackup Device Configuration Guide. Disable the automated device discovery by using the vm.conf file AUTO_PATH_CORRECTION option.

Enabling automatic path correction

You can configure NetBackup to automatic device path correction. To do so, use the following procedure.

Configuring robots and tape drives Replacing a device

285

See About automatic path correction on page 284. To configure automatic path correction

Use a text editor to open the following file:

install_path\VERITAS\Volmgr\vm.conf

Add the following AUTO_PATH_CORRECTION entry to the file:

AUTO_PATH_CORRECTION = YES

If it already exists but is set to NO, change the value to YES.

Save the file and exit the text editor.

Replacing a device
Table 7-7 describes the process to replace a device on a single host. Table 7-8 describes the process to replace a shared device. Table 7-7 Task To replace a device on a single host Instructions

If the device is a drive, change the drive state See Changing a drive operating mode to DOWN. on page 274. Replace the device. Specify the same SCSI ID for the new device as the old device. See the vendor's documentation.

If the device is a drive, change the drive state See Changing a drive operating mode to UP. on page 274. If either of the following are true, configure See Configuring robots and tape drives by the new device by using the NetBackup using the wizard on page 253. Device Configuration Wizard: You replaced a drive with a different drive type. You replaced a serialized drive with an unserialized drive.

Table 7-8 Task

To replace a shared device Instructions

If the device is a drive, change the drive state See Changing a drive operating mode to DOWN. on page 274.

286

Configuring robots and tape drives Updating device firmware

Table 7-8 Task

To replace a shared device (continued) Instructions

See the vendor's documentation.

Replace the device. Specify the same SCSI ID for the new device as the old device.

Produce a list of new and missing hardware. The following command scans for new hardware and produces a report that shows the new and the replaced hardware: install_path\Veritas\Volmgr\bin\tpautoconf -report_disc Ensure that all servers that share the new See Starting or stopping a service device are up and that all NetBackup services on page 852. are active. Read the serial number from the new device If the device is a robot, run the following and update the EMM database. command: install_path\Veritas\Volmgr\bin\tpautoconf -replace_robot robot_number -path robot_path If the device is a drive, run the following commands: install_path\Veritas\Volmgr\bin\tpautoconf -replace_drive drive_name -path path_name If the new device is an unserialized drive, run the NetBackup Device Configuration Wizard on all servers that share the drive. If the new device is a robot, run the NetBackup Device Configuration Wizard on the server that is the robot control host. If the device is a drive, change the drive state See Changing a drive operating mode to UP. on page 274. See Configuring robots and tape drives by using the wizard on page 253.

Updating device firmware

By default, NetBackup recognizes if you update the firmware of a device. The following table describes an overview of how to update device firmware.

Configuring robots and tape drives About the NetBackup Device Manager

287

Table 7-9 Task

How to update device firmware Instructions

See Changing a drive operating mode on page 274.

If the device is a drive, change the drive state to DOWN. Update the firmware.

See the vendor's documentation.

If the device is a drive, See Changing a drive operating mode on page 274. change the drive state to UP.

About the NetBackup Device Manager

The NetBackup Device Manager processes requests to mount and unmount tapes in robotically controlled devices through the robotic control processes. If you stop and restart the Device Manager (ltid.exe), it stops and restarts the Volume Manager (vmd.exe), the automatic volume recognition process (avrd.exe), and any robotic processes. Note: If you stop and restart the Device Manager, any backups, archives, or restores that are in progress may fail. See Stopping and restarting the Device Manager on page 287.

Stopping and restarting the Device Manager

Use the following procedure to stop and restart the NetBackup Device Manager. When you make device configuration changes, NetBackup asks if you want to restart the Device Manager. To start or stop the Device Manager Service

1 2 3 4

In the NetBackup Administration Console, expand Media and Device Management > Devices. On the Actions menu, select Stop/Restart Device Manager Service Select a device host. Select the action to perform.

288

Configuring robots and tape drives Stopping and restarting the Device Manager

Click Apply or OK. By using Apply, you can select device hosts and actions for more than one device host.

Click OK to close the dialog box.

Chapter

Configuring tape media

This chapter includes the following topics:

About tape volumes NetBackup media types About WORM media About adding volumes Adding volumes by using the wizard Adding volumes by using the Actions menu Managing volumes About volume pools Adding a volume pool Managing volume pools About volume groups About media sharing Configuring unrestricted media sharing Configuring media sharing with a server group

About tape volumes

A tape volume is a data storage tape or a cleaning tape. NetBackup assigns attributes to each volume and uses them to track and manage the volumes. Attributes include the media ID, robot host, robot type, robot number, and slot location.

290

Configuring tape media NetBackup media types

Volume information is stored in the EMM database. See About the Enterprise Media Manager (EMM) database on page 706. NetBackup uses two volume types, as follows:
Robotic volumes Stand-alone volumes Volumes that are located in a robot. Volumes that are in or are allocated for the drives that are not in a robot.

Catalog backup volumes are not a special type in NetBackup. They are the data storage volumes that you assign to the CatalogBackup volume pool. To add NetBackup catalog backups, use any of the add volume methods. Ensure that you assign them to the volume pool you use for catalog backups. After adding volumes, use the NetBackup Catalog Backup wizard to configure a catalog backup policy. See About the NetBackup catalog on page 699. WORM media can be used with NetBackup. See About WORM media on page 292.

NetBackup media types

NetBackup uses media types to differentiate the media that have different physical characteristics. Each media type may represent a specific physical media type; for example, NetBackup media type of 8MM, 8MM2, or 8MM3 can represent Sony AIT media. The NetBackup media types are also known as Media Manager media types. Table 8-1 describes the NetBackup media types. Table 8-1 Media type
4MM 4MM_CLN 8MM 8MM_CLN 8MM2 8MM2_CLN

NetBackup media types Description

4MM cartridge tape 4MM cleaning tape 8MM cartridge tape 8MM cleaning tape 8MM cartridge tape 2 8MM cleaning tape 2

Configuring tape media NetBackup media types

291

Table 8-1 Media type

8MM3 8MM3_CLN DLT DLT_CLN DLT2 DLT2_CLN DLT3 DLT3_CLN DTF DTF_CLN HCART HCART2 HCART3 HC_CLN HC2_CLN HC3_CLN QCART

NetBackup media types (continued) Description

8MM cartridge tape 3 8MM cleaning tape 3 DLT cartridge tape DLT cleaning tape DLT cartridge tape 2 DLT cleaning tape 2 DLT cartridge tape 3 DLT cleaning tape 3 DTF cartridge tape DTF cleaning tape 1/2 inch cartridge tape 1/2 inch cartridge tape 2 1/2 inch cartridge tape 3 1/2 inch cleaning tape 1/2 inch cleaning tape 2 1/2 inch cleaning tape 3 1/4 inch cartridge tape

NetBackup writes media in a format that allows the position to be verified before appending new backups. See Media formats in the NetBackup Administrators Guide, Volume II.

Alternate NetBackup media types

Alternate media types let you define more than one type of tape in the same library. You can use the alternate types to differentiate between different physical cartridges. The following are examples of alternate media types:

8MM, 8MM2, 8MM3

292

Configuring tape media About WORM media

DLT, DLT2, DLT3 HCART, HCART2, HCART3

For example, if a robot has DLT4000 and DLT7000 drives, you can specify the following media types:

DLT media type for the DLT4000 tapes DLT2 media type for the DLT7000 tapes

NetBackup then does not load a tape that was written in a DLT4000 drive into a DLT7000 drive and vice versa. You must use the appropriate default media type when you configure the drives. (When you configure drives in NetBackup, you specify the default media type to use in each drive type.) In a robot, all of the volumes (of a specific vendor media type) must be the same NetBackup media type. For example, for a TLH robot that contains 3490E media, you can assign either NetBackup HCART, HCART2, or HCART3 media type to that media. You cannot assign HCART to some of the media and HCART2 (or HCART3) to other of the media.

About WORM media

You can use WORM (Write-Once-Read-Many) media to protect key data from unwanted modification or to meet compliance regulations. NetBackup uses the QIC/WORM tape format for WORM media. This format lets NetBackup append images to WORM tape. See "Media Formats" in the NetBackup Administrators Guide, Volume II. Tape error recovery is disabled for WORM media. NetBackup has job resume logic, which tries to resume a job that has been interrupted (such as an interruption on the Fibre Channel ). However, NetBackup fails a job that uses WORM media and then retries the failed job. Symantec recommends that you use checkpoint and restart for backups. The bplabel command labels only LTO-3 WORM tapes. All other WORM media cannot be labeled because the label cannot be overwritten when the media is used. The following are the limitations for WORM tape:

Third-party copy backups are not supported with WORM media. NetBackup does not support resume logic with WORM tape. NetBackup fails a job that uses WORM media and then retries the failed job. Alternatively, if checkpoint and restart are used, NetBackup restarts the job from the last

Configuring tape media About WORM media

293

checkpoint. Symantec recommends that you use checkpoint and restart for backups.

WORM tape is not supported with NetWare media servers.

How to use WORM media in NetBackup

Two methods exist to ensure that data that is intended for WORM media is written on WORM media. See About using volume pools to manage WORM media on page 293. See About using unique drive and media types to manage WORM media on page 295.

Supported WORM drives

NetBackup requires a SCSI pass-through driver to use WORM tape drives. NetBackup queries the drive to verify that drive is WORM-capable and that the media in the drive is WORM media. SCSI pass-through paths are provided on the server platforms NetBackup supports. SCSI pass-through paths may require special operating system configuration changes. See the NetBackup Device Configuration Guide. For information about the drives that NetBackup supports for WORM media, see the NetBackup Hardware Compatibility List on the Symantec support Web site:
http://entsupport.symantec.com

All of the vendors except Quantum require the use of special WORM media. Quantum lets NetBackup convert standard tape media to WORM media. To use Quantum drives for WORM media on Solaris systems, modify the st.conf file. Information is available about how to configure nonstandard tape drives and how to edit the st.conf file. See the NetBackup Device Configuration Guide.

About using volume pools to manage WORM media

You can dedicate volume pools for the WORM media. This method lets a WORM-capable tape drive back up and restore standard and WORM media. Create a new volume pool and specify WORM (uppercase letters) as the first four characters of the pool name. See Adding a volume pool on page 326.

294

Configuring tape media About WORM media

NetBackup compares the first four characters of the volume pool name to determine if it is a volume pool that contains WORM media. The first four characters must be WORM. To disable the volume pool name verification, create the following touch file on the media server of the WORM drive:
install_path\netbackup\db\config\DISABLE_WORM_POOLCHECK

Note the following cases:

If the drive contains WORM media and the media is in a WORM volume pool, NetBackup writes the media as WORM. If the drive contains WORM media and the media is not in a WORM volume pool, NetBackup freezes the media. If the drive contains standard media and the media is in a WORM volume pool, NetBackup freezes the media. If the drive contains Quantum media that has never been used or all of its NetBackup images have expired, NetBackup uses the media.

About using a WORM scratch pool

For all supported WORM-capable drives (except the Quantum drive), the scratch pool must only contain one type of media. Symantec recommends that you add the most commonly used media to the scratch pool. For example, if most NetBackup jobs use standard media, put standard media in the scratch pool. If the scratch pool contains standard media, ensure that the WORM volume pool does not run out of media to complete backup jobs. If the WORM volume pool runs out of media, NetBackup performs the following actions:

Moves the standard media from the scratch pool into the WORM pool. Loads the standard media into a WORM-capable drive. Freezes the media.

NetBackup repeats this process until all of the standard media in the scratch pool is frozen. The opposite also is true. If a standard volume pool runs out of media and the scratch pool contains WORM media, standard backups can fail because appropriate media are unavailable.

Configuring tape media About adding volumes

295

About WORM media and the Quantum drive

When you use the Quantum drive, only one kind of media can be used as either standard media or WORM media. If a WORM volume pool runs out of media, media are moved from the scratch volume pool into the WORM pool. NetBackup determines whether the media are configured as standard or WORM media. For a standard media volume, NetBackup reads the tape label and verifies that the media is unused or that all images are expired. NetBackup also verifies that the media is not currently assigned to a server. After verification, NetBackup configures the media as WORM media and continues with the NetBackup job.

About using unique drive and media types to manage WORM media
You can assign a different drive and media type to all WORM drives and media. For example, configure standard drives and media as HCART and WORM-capable drives and media as HCART2. This method lets you add both types of media in the scratch pool because NetBackup selects the correct media type for the drive type. However, because each drive is limited to backups and restores with a specific type of media, optimal drive usage may not be achieved. For example, the WORM-capable drives cannot be used for backups with standard media even if no WORM backups are in progress. If you do not use WORM volume pools to manage WORM media, disable the WORM volume pool name verification. To disable the volume pool name verification, create the following touch file on the media server of the WORM drive:
install_path\netbackup\db\config\DISABLE_WORM_POOLCHECK

Because Quantum drives use only a single media type, this method for managing the WORM media is unnecessary.

About adding volumes

Adding volumes is a logical operation that assigns NetBackup attributes to physical media. The media can reside in storage devices already, or you can add them to the storage devices when you add them to NetBackup. How you add volumes depends on the type of volume: robotic or stand-alone.

296

Configuring tape media About adding volumes

About adding robotic volumes

Robotic volumes are the volumes that are located in a robotic tape library. Table 8-2 Method
The Volume Configuration Wizard

Methods for adding robotic volumes Description

See Adding volumes by using the wizard on page 297. See Updating the volume configuration with a robot's contents on page 345. See Adding volumes by using the Actions menu on page 297. See NetBackup Commands Reference Guide.

Robot inventory

The Actions menu

NetBackup commands

About adding stand-alone volumes

Stand-alone volumes are the volumes that reside in the drives that are not in a robot or are allocated for stand-alone drives. Because NetBackup does not label volumes until it uses them, you can add volumes even though they do not reside in a drive. The additional volumes are available for use if the volume in a drive becomes full or unusable. For example, if a volume in a stand-alone drive is full or unusable because of errors, NetBackup ejects (logically) the volume. If you add other stand-alone volumes, NetBackup requests that volume; NetBackup does not generate an out of media error. The easiest way to add stand-alone volumes is to use the Volume Configuration Wizard. Then, when NetBackup requests one of the volumes, insert it into the stand-alone drive and NetBackup labels it. The DISABLE_STANDALONE_DRIVE_EXTENSIONS option of the nbemmcmd command can turn off the automatic use of stand-alone volumes. Table 8-3 Method Methods for adding stand-alone volumes Description

The Volume Configuration Wizard See Adding volumes by using the wizard on page 297. The Actions menu See Adding volumes by using the Actions menu on page 297. See NetBackup Commands Reference Guide.

NetBackup commands

Configuring tape media Adding volumes by using the wizard

297

Adding volumes by using the wizard

The easiest way to add volumes is to use the Volume Configuration Wizard. NetBackup assigns media IDs and labels the volumes automatically. To configure volumes by using the wizard

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Devices. From the list of wizards in the right pane, click Configure Volumes and follow the wizard instructions.

Adding volumes by using the Actions menu

Symantec recommends that you use the Volume Configuration Wizard or the robot inventory option to add volumes. Be careful when you specify properties. You cannot change some properties later, such as the media ID or type. If you specify them incorrectly, you must delete the volume and add it again. To add volumes by using the Actions menu

1 2 3

For new volumes in a robotic library, insert them into the proper slots. In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. On the Actions menu, select New > New Volumes.

298

Configuring tape media Adding volumes by using the Actions menu

In the Add Volumes dialog box, specify the attributes for the volumes. See Add volume properties on page 298.

Click Apply or OK. If the robot has a bar code reader, NetBackup performs the following actions:

Adds the volume to the EMM database using the specified media ID. Reads the bar code of each new volume. Adds the bar codes as attributes in the EMM database. The Apply option adds the volume without closing the dialog box or refreshing the display. You can then add more volumes.

Add volume properties

Table 8-4 describes the properties to configure when you add volumes. The topics are arranged alphabetically. Table 8-4 Property
Device host First media ID

Volume properties when adding volumes Description

The name of the host to which the robot is attached. This property appears only if the number of volumes is more than one. The ID of the first volume in the range of volumes. Media IDs can be from 1 to 6 characters in length. Valid only when you add a range of volumes. Use the same pattern that you chose in the Media ID naming style box. NetBackup uses the pattern to name the remaining volumes by incrementing the digits. NetBackup allows specific characters in names. See NetBackup naming conventions on page 897.

First slot number

The number of the first slot in the robot in which the range of volumes resides. NetBackup assigns the remainder of the slot numbers sequentially.

Note: You cannot enter slot information for volumes in an

API robot. The robot vendor tracks the slot locations for API robot types.

Configuring tape media Adding volumes by using the Actions menu

299

Table 8-4 Property

Volume properties when adding volumes (continued) Description

The maximum number of times NetBackup should mount the volume or use the cleaning tape. When a volume reaches the mount limit, the volume can be read, but not written. Zero (0) indicates unlimited mounts. If you enter a value larger than 99999, NetBackup may display it as 0 although it uses the actual value. For example, the output of the vmrule command displays 0 for values larger than 99999. To determine the maximum mount limit to use, consult the vendor documentation for information on the expected life of the volume.

Maximum cleanings

Media description

A description of the media, up to 25 character maximum. NetBackup allows specific characters in names. See NetBackup naming conventions on page 897.

Media ID

This property appears only if the number of volumes is one. The ID for the new volume. Media IDs can be from 1 to 6 characters in length. Media IDs for an API robot must match the bar code on the media (for API robots, NetBackup supports bar codes from 1 to 6 characters). Therefore, obtain a list of the bar codes before you add the volumes. Obtain this information through a robotic inventory or from the robot vendors software. NetBackup allows specific characters in names. See NetBackup naming conventions on page 897.

300

Configuring tape media Adding volumes by using the Actions menu

Table 8-4 Property

Volume properties when adding volumes (continued) Description

This property appears only if the number of volumes is more than one. The style to use to name the range of volumes. Media IDs can be from 1 to 6 characters in length. Using the pattern, NetBackup names the remaining volumes by incrementing the digits. NetBackup media IDs for an API robot must match the bar code on the media. For API robots, NetBackup supports bar codes from 1 to 6 characters. Therefore, obtain a list of the bar codes before you add the volumes. Obtain this information through a robotic inventory or from the robot vendors software. NetBackup allows specific characters in names. See NetBackup naming conventions on page 897.

Media ID naming style

Media type

The media type for the volume to add. Select the type from the drop-down list. See NetBackup media types on page 290.

Number of volumes

The number of volumes to add. For a robotic library, enough slots must exist for the volumes. The robotic library to add the volumes to. To add volumes for a different robot, select a robot from the drop-down list . The list shows robots on the selected host that can contain volumes of the selected media type. To find a robot that does not appear in the Robot box, click Find Robots to open the Find Robot dialog box. To add volumes to a stand-alone drive, select Standalone.

Robot

Configuring tape media Managing volumes

301

Table 8-4 Property

Volume group

Volume properties when adding volumes (continued) Description

If you specified a robot, select from a volume group already configured for that robot. Alternatively, enter the name for a volume group; if it does not exist, NetBackup creates it and adds the volume to it. If you do not specify a volume group (you leave the volume group blank), the following occurs:

Stand-alone volumes are not assigned to a volume group. NetBackup generates a name for robotic volumes by using the robot number and type. For example, if the robot is a TL8 and has a robot number of 50, the group name is 000_00050_TL8.

See About volume groups on page 328. Volume is in a robotic library To specify that the volume is in a robot, select Volume is in a robotic library. If the volume is a stand-alone volume, do not select this option. The pool to which the volume or volumes should be assigned. Select a volume pool you created or one of the following standard NetBackup pools:

Volume pool

None. NetBackup is the default pool name for NetBackup. DataStore is the default pool name for DataStore. CatalogBackup is the default pool name used for NetBackup hot, online catalog backups of policy type NBU-Catalog.

When the images on a volume expire, NetBackup returns it to the scratch volume pool if it was allocated from the scratch pool. See About volume pools on page 324.

Managing volumes
The following sections describe the procedures to manage volumes.

302

Configuring tape media Managing volumes

Changing the group of a volume

If you move a volume physically to a different robot, change the group of the volume to reflect the move. See About rules for moving volumes between groups on page 302. To change the group of a volume

1 2 3 4 5

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select the volumes that you want to change the volume group assignment for. On the Actions menu, select Change Volume Group. In the New volume group name field, enter the name of the new volume group or select a name from the list of volume groups. Click OK. The name change is reflected in the volume list entry for the selected volumes. If you specified a new volume group (which creates a new volume group), the group appears under Volume Groups in the left pane.

About rules for moving volumes between groups

The following are the rules for moving volumes between groups:

The target volume group must contain the same type of media as the source volume group. If the target volume group is empty: The successive volumes that you add to it must match the type of media that you first add to it. All volumes in a robotic library must belong to a volume group. If you do not specify a group, NetBackup generates a new volume group name by using the robot number and type. More than one volume group can share the same location. For example, a robotic library can contain volumes from more than one volume group and you can have more than one stand-alone volume group. All members of a group must be in the same robotic library or be stand-alone. That is, if volume group already exists in another robotic library, you cannot add it (or part of it) to a robotic library.

Changing the owner of a volume

You can change the media server or server group that owns the volume. See About server groups on page 223.

Configuring tape media Managing volumes

303

See About media sharing on page 329. To change the owner of a volume

1 2 3 4

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the Volumes list, select the volume that you want to change. On the Actions menu, select Change Media Owner. In the Media Owner field, select one of the following:
Any (default) Allows NetBackup to choose the media owner. NetBackup chooses a media server or a server group (if one is configured). Specifies that the media server that writes the image to the media owns the media. No media server is specified explicitly, but you want a media server to own the media. Specify a server group. A server group allows only those servers in the group to write to the media on which backup images for this policy are written. All server groups that are configured in the NetBackup environment appear in the drop-down list.

None

A server group

Click OK.

Changing the pool of a volume

Change the Volume pool property in the Change Volumes dialog box. See Changing volume properties on page 303.

Changing volume properties

You can change some of the properties of a volume, including the volume pool. To change volume properties

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select a volume or volumes.

304

Configuring tape media Managing volumes

On the Edit menu, select Change.

In the Change Volumes dialog box, change the properties for the volume. See Change volume properties on page 304.

Click OK.

Change volume properties

Table 8-5 describes the volume properties that you can change. Table 8-5 Property
Description

Volume properties when changing volumes

Description
A description of the media, up to 25 character maximum. NetBackup allows specific characters in names as described in the following topic: See NetBackup naming conventions on page 897.

Configuring tape media Managing volumes

305

Table 8-5 Property

Expiration date

Volume properties when changing volumes (continued)

Description
The following does not apply to cleaning tapes. The date after which the volume is too old to be reliable. When the expiration date has passed, NetBackup reads data on the volume but does not mount and write to the volume. You should exchange it for a new volume. See About exchanging a volume on page 309. When you add a new volume, NetBackup does not set an expiration date. The expiration date is not the same as the retention period for the backup data on the volume. You specify data retention periods in the backup policies.

Maximum mounts

The following topic does not apply to cleaning tapes. The Maximum mounts property specifies the number of times that the selected volumes can be mounted. When the limit is reached, NetBackup reads data on the volume but does not mount and write to the volume. A value of zero (the default) is the same as Unlimited. To help determine the maximum mount limit, consult the vendor documentation for information on the expected life of the volume.

Number of cleanings remaining

The number of cleanings that are allowed for a cleaning tape. This number is decremented with each cleaning and when it is zero, NetBackup stops using the tape. You then must change the cleaning tape or increase the number of cleanings that remain. Additional information about drive cleaning is available. See the NetBackup Administrators Guide, Volume II.

Volume pool

The following topic does not apply to cleaning tapes. The pool to which the volume or volumes should be assigned. Select a volume pool you created or one of the following standard NetBackup pools:

None. NetBackup is the default pool name for NetBackup. DataStore is the default pool name for DataStore. CatalogBackup is the default pool name used for NetBackup hot, online catalog backups of policy type NBU-Catalog.

When the images on a volume expire, NetBackup returns it to the scratch volume pool if it was allocated from the scratch pool. See About volume pools on page 324.

306

Configuring tape media Managing volumes

About assigning volumes

An assigned volume is one that is reserved for exclusive use by NetBackup. A volume is set to the assigned state when either application writes data on it for the first time. The time of the assignment appears in the Time Assigned column for the volume in the NetBackup Administration Console Volumes pane. When a volume is assigned, you cannot delete it or change its volume pool. A volume remains assigned until NetBackup deassigns it. To determine which application currently uses a volume, see the Application column of the right pane, labeled Volumes. See About deassigning volumes on page 306.

About deassigning volumes

NetBackup deassigns a volume only when the data is no longer required, as follows:

For regular backup volumes, when the retention period has expired for all the backups on the volume. For catalog backup volumes, when you stop using the volume for catalog backups.

To deassign a volume, you expire the images on the volume. After you expire a volume, NetBackup deassigns it and does not track the backups that are on it. NetBackup can reuse the volume, you can delete it, or you can change its volume pool. See Expiring backup images on page 788. You can expire backup images regardless of the volume state (Frozen, Suspended, and so on). NetBackup does not erase images on expired volumes. You can still use the data on the volume by importing the images into NetBackup (if the volume has not been overwritten). See About importing backup images on page 789. Note: Symantec recommends that you do not deassign NetBackup volumes. If you do, be certain that the volumes do not contain any important data. If you are uncertain, copy the images to another volume before you deassign the volume. See About assigning volumes on page 306.

Configuring tape media Managing volumes

307

Deleting a volume
You can delete volumes from the NetBackup configuration. Note: You cannot delete a volume if it is still assigned. For example, if any of the following situations apply, you may want to delete the volume:

A volume is no longer used and you want to recycle it by relabeling it with a different media ID. A volume is unusable because of repeated media errors. A volume is past its expiration date or has too many mounts, and you want to replace it with a new volume. A volume is lost and you want to remove it from the EMM database.

After a volume is deleted, you can discard it or add it back under the same or a different media ID. Before you delete and reuse or discard a volume, ensure that it does not have any important data. You cannot delete NetBackup volumes if they are assigned. See About deassigning volumes on page 306. To delete volumes

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select the volume or volumes that you want to delete. You cannot delete a volume if it is still assigned.

3 4 5

On the Edit menu, select Delete. In the Delete Volumes dialog box, click OK. Remove the deleted volume or volumes from the storage device.

Erasing a volume
You can erase the data on a volume if the following are true:

The volume is not assigned. The volume contains no valid NetBackup images.

After NetBackup erases the media, NetBackup writes a label on the media.

308

Configuring tape media Managing volumes

If you erase media, NetBackup cannot restore or import the data on the media. If a volume contains valid NetBackup images, deassign the volume so NetBackup can label it. See About deassigning volumes on page 306. Table 8-6 Type of erase
SCSI long erase

Types of erase Description

Rewinds the media and the data is overwritten with a known data pattern. A SCSI long erase is also called a secure erase because it erases the recorded data completely.

Note: A long erase is a time-consuming operation and can take as

long as two hours to three hours. For example, it takes about 45 minutes to erase a 4-mm tape on a standalone drive SCSI quick erase Rewinds the media and an erase gap is recorded on the media. The format of this gap is drive dependent. It can be an end-of-data (EOD) mark or a recorded pattern that the drive does not recognize as data. Some drives do not support a quick erase (such as QUANTUM DLT7000). For the drives that do not support a quick erase, the new tape header that is written acts as an application-specific quick erase.

Note: NetBackup does not support erase functions on NDMP drives. To erase a volume

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select a volume or volumes that you want to erase. If you select multiple volumes, they must all be in the same robot

3 4

Select either Actions > Quick Erase or Actions > Long Erase. In the erase dialog box, specify the name of the media server to initiate the erase operation. To overwrite any existing labels on the media, do not select Verify media label before performing operation.

Configuring tape media Managing volumes

309

Click OK. A dialog box warns you that this action is irreversible.

Click OK if you are certain you want to start the erase action. A dialog box reminds you to use the Activity Monitor to view the progress and status of the action. (For many types of drives, you may not be able to cancel a label or erase media job from the Activity Monitor.) Click OK. If you selected Verify media label before performing operation and the actual volume label does not match the expected label, the media is not erased.

About exchanging a volume

You should exchange a volume (replace one volume with another volume) if a volume meets any of the following conditions:

Full (in this case, to exchange a volume means to remove the volume from a robotic tape library). Past the maximum number of mounts. Old (past the expiration date). Unusable (for example, because of repeated media errors).

Depending on whether you want to reuse the old media ID or not, follow one of the exchange volumes processes in the following subsections.

Exchanging a volume and using a new media ID

Use this procedure when the following are true:

The volume contains current and valid NetBackup images. You require slots in the robotic library for additional backups, duplications, vault functions, or other purposes. Exchange a volume and using a new media ID Instructions
See About moving volumes on page 318.

Table 8-7 Step

Step 1

Task
Move the volume to another location If the volume is in a robotic library, remove it from the robotic library and move it to a stand-alone group.

310

Configuring tape media Managing volumes

Table 8-7 Step

Step 2

Exchange a volume and using a new media ID (continued) Instructions

Task

Add a new volume or move an existing volume in as a replacement See About adding volumes for the volume you removed. on page 295. If you add a new volume, specify a new media ID. Specify the same values for the other attributes as the removed volume (such as robotic residence, volume pool, and the media type).

Step 3

Physically replace the old volume. Do not delete the old volume in case you need to retrieve the data on the volume.

Beyond the scope of the NetBackup documentation.

Exchanging a volume and using the old media ID

You can exchange a volume and reuse the same media ID, which may be convenient in some instances. Reuse a media ID only if all data on the old volume is not required and you recycle or discard the volume. Warning: If you exchange a media ID for a volume that has unexpired backup images, serious operational problems and data loss may occur. Table 8-8 Step
Step 1 Step 2

Exchange a volume and use the old media ID Instructions

See Deleting a volume on page 307.

Task
Delete the volume.

Remove the old volume from the storage device. Physically add See About injecting and ejecting the new volume to the storage device. volumes on page 312. Add the new volume to the NetBackup volume configuration and See About adding volumes specify the same attributes as the old volume, including the old on page 295. media ID. Set a new expiration date for the volume. See Changing volume properties on page 303.

Step 3

Step 4

Step 5

Optionally, label the volume. Although you do not have to label See Labeling a volume on page 317. the volume, the label process puts the media in a known state. The external media label matches the recorded media label, and the mode is known to be compatible with the drives in the robotic library.

Configuring tape media Managing volumes

311

About frozen media

A frozen volume is unavailable for future backups. A frozen volume never expires, even after the retention period ends for all backups on the media. The media ID is never deleted from the NetBackup media catalog, and it remains assigned to NetBackup. A frozen volume is available for restores. If the backups have expired, you must import the backups first. See About importing backup images on page 789. NetBackup freezes media automatically when read or write errors surpass the threshold within the time window. The default media error threshold is 2. That is, NetBackup freezes media on the third media error in the default time window (12 hours). NetBackup also freezes a volume if a write failure makes future attempts at positioning the tape unreliable. Common reasons for write failures are dirty write heads or old media. The reason for the action is logged in the NetBackup error catalog (view the Media Logs report or the All Log Entries report). You can use the NetBackup nbemmcmd command with the -media_error_threshold and -time_window options to change the default values. Additional information about nbemmcmd is available. See NetBackup Commands Reference Guide. To reverse a freeze action, use the bpmedia command to unfreeze the volume. See Freezing or unfreezing a volume on page 311.

Freezing or unfreezing a volume

NetBackup freezes volumes under circumstances. You can freeze or unfreeze a volume manually. To freeze or unfreeze media

1 2 3 4

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select the volume that you want to freeze or unfreeze. On the Actions menu, select Freeze or Unfreeze. In the dialog box, click OK.

312

Configuring tape media Managing volumes

About injecting and ejecting volumes

Media access port (MAP) functionality differs between robotic libraries. For many libraries, NetBackup opens and closes the MAP as needed. However, some libraries have the front-panel inject and the eject functions that conflict with NetBackups use of the media access port. And for other libraries, NetBackup requires front-panel interaction by an operator when using the media access port. Read the operator manual for the library to understand the media access port functionality. Some libraries may not be fully compatible with the inject and eject features of NetBackup unless properly handled. Other libraries may not be compatible at all.

Injecting volumes into robots

You can inject volumes into the robots that contain media access ports. Any volumes to be injected must be in the media access port before the operation begins. If no volumes are in the port, you are not prompted to place volumes in the media access port and the update operation continues. Each volume in the MAP is moved into the robotic library. If the MAP contains multiple volumes, they are moved to empty slots in the robotic library until the media access port is empty or all the slots are full. After the volume or volumes are moved, NetBackup updates the volume configuration. Some robots report only that media access ports are possible. Therefore, Empty media access port prior to update may be available for some robots that do not contain media access ports. Inject volumes into the robots that contain media access ports

1 2

Load the volumes in the MAP. Inventory the robot See Updating the volume configuration with a robot's contents on page 345.

Select Empty media access port prior to update on the Robot Inventory dialog box.

Ejecting volumes
Eject single or multiple volumes. Volumes that reside in multiple robots can be ejected. Multiple eject dialog boxes appear for each robot type.

Configuring tape media Managing volumes

313

Operator intervention is required only if the media access port is too small to contain all of the selected volumes. For these robot types, you are prompted to remove the media from the media access port so the eject can continue with the remaining volumes. See Media ejection timeout periods on page 314. To eject volumes

1 2 3

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select one or more volumes that you want to eject. On the Actions menu, select Eject Volumes From Robot. Depending on the robot type, one of the following dialog boxes appears:

Eject Volume (singular) Eject Volumes (plural)

If the Eject Volume (singular) dialog box appears, click OK to eject the volumes.

If you select multiple volumes, operator action is required to remove each volume after each eject (a dialog box prompts you to remove volumes).

If the Eject Volumes (plural) dialog box appears, continue by reading the following:

After NetBackup completes prechecks for the eject, the Media tab of the Eject Volumes dialog box shows the volumes that you selected to eject. If no errors occur, the Errors tab is empty. If an error occurs or a hardware limitation exists, the eject may not be possible; if so, the Errors tab is opened. The following classes of errors can occur:

For serious errors, the Eject option is not active. Correct the error to eject the media.

314

Configuring tape media Managing volumes

For other errors, the Errors tab shows an explanation of the error. Either continue the eject action (Eject) or exit (Close) depending on the type of error.

6 7

ACS and TLM robots only: In the Eject Volumes dialog box, select the media access port to use for the eject. In the Eject Volumes dialog box, click Eject to eject the volumes. The robotic library may not contain a media access port large enough to eject all of the selected volumes. For most robot types, you are prompted to remove the media from the media access port so the eject can continue with the remaining volumes.

Media ejection timeout periods

The media ejection period (the amount of time before an error condition occurs) varies depending on the capability of each robot. Table 8-9 shows the ejection timeout periods for robots.

Configuring tape media Managing volumes

315

Table 8-9 Robot types

Media ejection timeout periods Timeout period

Applies only to NetBackup Enterprise Server: One week Automated Cartridge System (ACS) Tape Library Multimedia (TLM) Tape Library 8MM (TL8) Tape Library DLT (TLD) Applies only to NetBackup Enterprise Server: None. The robot allows an unlimited amount of time to remove media. Tape Library Half-inch (TLH) 30 minutes.

Note: If the media is not removed and a timeout condition occurs, the media is returned to (injected into) the robot. Inventory the robot and eject the media that was returned to the robot. Some robots do not contain media access ports. For these robots, the operator must remove the volumes from the robot manually. Note: After you add or remove media manually, use NetBackup to inventory the robot.

About rescanning and updating bar codes

You can rescan the media in a robot and then update NetBackup with the bar codes of that media. You should rescan and update only in certain circumstances. Note: Rescan and update bar codes does not apply to volumes in API robot types.

316

Configuring tape media Managing volumes

When not to rescan and update bar codes

Do not rescan and update to correct the reports that show a media ID in the wrong slot. To correct that problem, perform one of the following actions: Logically move the volume by selecting a volume and then on the Actions menu select Move. Logically move the volume by updating the volume configuration. See Updating the volume configuration with a robot's contents on page 345. Physically move the volume into the correct slot.

To obtain an inventory of the robot without updating the bar code information in the database, inventory the robot and use the show contents option. See Showing the media in a robot on page 340. When to rescan and update bar codes Rescan and update bar codes only to add the bar codes that are not in the EMM database. For example: if you add a new volume but do not insert the tape into the robot, NetBackup does not add the bar code to the database. Use this command to add the bar code after you insert the tape into the robotic library.

See About bar codes on page 356.

Rescanning and updating bar codes

Use the following procedure to rescan the media in a robot and update NetBackup with the bar codes. Note: Rescan and update bar codes does not apply to volumes in API robot types. See About rescanning and updating bar codes on page 315. To rescan bar codes and update the EMM database

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media > Robots. Select the robotic library that contains the volumes that you want to scan and update.

Configuring tape media Managing volumes

317

3 4

In the right pane, in the Volumes list, select the volumes. On the Actions menu, select Rescan/Update Barcodes. The rescan begins immediately.

About labeling NetBackup volumes

When NetBackup labels a volume, it writes a record on the magnetic tape of the volume; the record (or label) includes the NetBackup media ID. Normally, NetBackup controls the labeling of its volumes. In most cases, NetBackup labels a volume the first time it is used for a backup. The volume label depends on whether or not the media has a bar code, as follows:

If the robot supports bar codes and the media has bar codes, NetBackup uses the last six characters of the bar code for the media ID. To change this default action, specify and select specific characters by using Media ID generation rules. See Configuring media ID generation rules on page 363. For volumes without bar codes, by default NetBackup uses a prefix of the letter A when it assigns a media ID to a volume (for example, A00001). To change the default prefix, use the MEDIA_ID_PREFIX configuration option in the vm.conf file. See the NetBackup Administrators Guide, Volume II.

Media is not labeled automatically in the following situations:

They were last used for NetBackup catalog backups. Do not label catalog backup volumes unless they are no longer used for catalog backups. They contain data from a recognized non-NetBackup application and NetBackup is configured to prohibit media overwrite for that media type.

To label these media types, the following must be true:

NetBackup has not assigned the media The media contains no valid NetBackup images

Labeling a volume
If a volume contains valid NetBackup images, deassign the volume so that it can be labeled. See About deassigning volumes on page 306.

318

Configuring tape media Managing volumes

If you want to label media and assign specific media IDs (rather than allow NetBackup to assign IDs), use the bplabel command. Note: If you label a volume, NetBackup cannot restore or import the data that was on the media after you label it.

Note: For many types of drives, you may not be able to cancel a label job from the Activity Monitor. See About labeling NetBackup volumes on page 317. To label a volume

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select a volume or the volumes that you want to label. If you select multiple volumes, they all must be in the same robot.

3 4

On the Actions menu, select Label. In the Label dialog box, specify the following properties for the label operation.
Media server Enter tname of the media server that controls the drive to write the label. Select this option to verify that the media in the drive is the expected media. To overwrite any existing labels on the media, do not select Verifymedialabelbeforeperformingoperation.

Verify label before performing operation

5 6

Click OK. In the warning dialog box, click OK. If you selected Verify media label before performing operation and the actual volume label does not match the expected label, the media is not relabeled.

About moving volumes

When you move volumes in or out of a robotic library or from one robot to another, move the volumes physically and logically, as follows:

Configuring tape media Managing volumes

319

Physically move volumes by inserting or by removing them. For some robot types, use the NetBackup inject and eject options. Logically move volumes using NetBackup, which updates the EMM database to show the volume at the new location.

When you move volumes from one robotic library to another robotic library, perform the following actions:

Move the volumes to stand alone as an intermediate step. Move the volumes to the new robotic library.

The following types of logical moves are available:

Move single volumes. Move multiple volumes. Move combinations of single and multiple volumes. Move volume groups.

You cannot move volumes to an invalid location (for example, move DLT media to an 8-mm robot). Symantec recommends that you perform moves by selecting and by moving only one type of media at a time to a single destination. The following are several examples of when to move volumes logically:

When a volume is full in a robotic library and no slots are available for new volumes in the robotic library. Move the full volume to stand alone, remove it from the robot, then configure a new volume for the empty slot or move an existing volume into that slot. Use the same process to replace a defective volume. Moving volumes from a robotic library to an off-site location or from an off-site location into a robotic library. When you move tapes to an off-site location, move them to stand alone. Moving volumes from one robotic library to another (for example, if a library is down). Changing the volume group for a volume or volumes.

Moving volumes by using the robot inventory update option

Use this procedure for the following:

To move volumes within a robot. The robot must have a bar code reader and the volumes must contain readable bar codes.

320

Configuring tape media Managing volumes

To remove volumes from a robot. Use this procedure even if the volumes do not contain bar codes or if the robot does not have a reader.

To move volumes by using a robot inventory update

1 2 3 4

Physically move the volumes to their new location. On the Actions menu, select Inventory Robot. In the Robot Inventory dialog box, select Update volume configuration. Select other options as appropriate. See About robot inventory on page 334.

Moving volumes by using the Actions menu

If you move a volume to a robotic library that has a bar code reader, NetBackup updates the EMM database with the correct bar code. To move volumes by using the Actions menu

1 2 3 4

Physically move the volumes to their new location. In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. In the right pane, in the Volumes list, select the volumes that you want to move. On the Actions menu, select Move. If you selected volumes of different media types or volume residences, a Move Volumes dialog box appears for each residence and each media type. See Multiple Move Volumes dialog boxes may appear on page 320.

In the Move Volumes dialog box, specify the properties for the move.

Multiple Move Volumes dialog boxes may appear

If you selected volumes of different media types or volume residences, a Move Volumes dialog box appears for each residence and each media type. For example, you select two full volumes to move out of a robotic library and two stand-alone volumes to move in as replacements. A dialog box appears for the two full volumes and another dialog box for the two replacement volumes. In this example, complete both move dialog boxes to perform the move (complete the move for the volumes that are full first).

Configuring tape media Managing volumes

321

Note: These multiple Move Volumes dialog boxes may appear on top of each other and need to be repositioned. Figure 8-1 and Figure 8-2 show examples of moving multiple types or residences. Figure 8-1 Move volumes to stand alone

Figure 8-2

Move volumes to the robot

Move volumes properties

Table 8-10 describes the properties to configure in the Move Volumes dialog box. Table 8-10 Property Description Move volumes properties

First slot number For volumes in a robotic library, specify the first slot number to be used in the destination robotic library. By default, this box shows the slot number where the volume currently resides. NetBackup assigns the remainder of the slot numbers sequentially.

Note: You cannot enter slot information for volumes in an API robot. The robot vendor tracks
the slot locations for these robot types.

322

Configuring tape media Managing volumes

Table 8-10 Property

Device host

Move volumes properties (continued)

Description
The Device host specifies the name of the device host where the robot is defined. For single volumes, the current location of the volume appears. NetBackup Enterprise Serve only: To select a robot on another device host, select from the list of device hosts shown.

Find Robots

Use Find Robots to find a robot that does not appear in the Robot box (for example, a new robot). Robot specifies the new robotic library for the volumes. You can specify a different robot as the destination or Standalone. The list shows the robot type, number, and control host for any robot that already has at least one volume in the EMM database.

Robot

Volume group

Enter or select the volume group to assign to the volumes. If you leave the volume group blank, the following occurs:

Stand-alone volumes are not assigned a volume group. Robotic volumes are assigned to a new volume group; NetBackup generates the name by using the robot number and type. For example, if the robot is a TL8 and has a robot number of 50, the group name is 000_00050_TL8.

See About rules for moving volumes between groups on page 302. Volume is in a robotic library To inject a volume into a robotic library, select Volume is in a robotic library. Select a robot and the slot number for the volume. To eject a volume from a robot, clear Volume is in a robotic library. Volumes to move The Volumes to move section of the dialog box shows the media IDs of the volumes that you selected to move.

About recycling a volume

If you recycle a volume, you can use either the existing media ID or a new media ID. Caution: Recycle a volume only if all NetBackup data on the volume is no longer needed or if the volume is damaged and unusable. Otherwise, you may encounter serious operational problems and a possible loss of data.

Configuring tape media Managing volumes

323

Recycling a volume and using the existing media ID

NetBackup recycles a volume and returns it to the volume rotation when the last valid image on the volume expires. To recycle a volume that contains unexpired backup images, you must deassign the volume. See About deassigning volumes on page 306.

Recycling a volume and using a new media ID

Recycle a volume if it is a duplicate of another volume with the same media ID. Also recycle a volume if you change how you name volumes and you want to match the bar codes on the volume. Table 8-11 Step
Step 1

Recycling a volume and using a new media ID Description

See Ejecting volumes on page 312.

Action
Physically remove the volume from the storage device.

Step 2

If the volume is in a robotic library, move it to stand See About moving volumes on page 318. alone. Record the current number of mounts and expiration See the values in the Media (Media and Device date for the volume. Management > Media in the NetBackup Administration Console). Delete the volume entry. Add a new volume entry. See Deleting a volume on page 307. See Adding volumes by using the Actions menu on page 297. Because NetBackup sets the mount value to zero for new volume entries, you must adjust the value to account for previous mounts. Set the maximum mounts to a value that is equal to or less than the following value: The number of mounts that the manufacturer recommends minus the value that you recorded earlier.

Step 3

Step 4 Step 5

Step 6

Physically add the volume to the storage device.

See Injecting volumes into robots on page 312.

324

Configuring tape media About volume pools

Table 8-11 Step

Step 7

Recycling a volume and using a new media ID (continued) Description

Set the number of mounts to the value you recorded earlier by using the following command: install_path\Volmgr\bin\vmchange -m media_id -n number_of_mounts

Action
Configure the number of mounts

Step 8

Set the expiration date to the value you recorded earlier.

See Changing volume properties on page 303.

Suspending or unsuspending volumes

You cannot use a suspended volume for backups until retention periods for all backups on it have expired. At that time, NetBackup deletes the suspended volume from the NetBackup media catalog and unassigns it from NetBackup. A suspended volume is available for restores. If the backups have expired, import the backups first. To suspend or unsuspend media

1 2 3 4

In the NetBackup Administration Console, in the left pane, select Media and Device Management > Media. In the right pane, in the Volumes list, select the volume or volumes that you want to suspend or unsuspend. On the Actions menu, select Suspend or Unsuspend. In the dialog box, click OK.

About volume pools

A volume pool identifies a set of volumes by usage. Volume pools protect volumes from access by unauthorized users, groups, or applications. When you add media to NetBackup, you assign them to a volume pool (or assign them as standalone volumes, without a pool assignment). By default, NetBackup creates the following volume pools:
NetBackup The default pool to which all backup images are written (unless you specify otherwise). For DataStore use. For NetBackup catalog backups.

DataStore CatalogBackup

Configuring tape media About volume pools

325

None

For the volumes that are not assigned to a pool.

You can add other volume pools. For example, you can add a volume pool for each storage application you use. Then, as you add volumes to use with an application, you assign them to that applications volume pool. You can also move volumes between pools. You also can configure a scratch pool from which NetBackup can transfer volumes when a volume pool has no volumes available. The volume pool concept is relevant only for NetBackup storage units and does not apply to disk storage units. Examples of volume pool usage are available. See the NetBackup Administrators Guide, Volume II.

About scratch volume pools

The scratch pool is an optional pool that contains the media that NetBackup can allocate to other pools as needed. If you configure a scratch pool, NetBackup moves volumes from that scratch pool to other pools that do not have volumes available. Only one scratch pool is allowed. You cannot add a scratch pool if one exists. You cannot change the NetBackup or DataStore pools to be scratch volume pools. If you create a scratch pool, be aware of the following conditions:

If the scratch pool contains assigned volumes, these volumes remain in the scratch pool. NetBackup does not move assigned volumes to other pools as it does with unassigned volumes. NetBackup does not assign volumes while they are in a scratch pool. For example if a NetBackup policy or schedule specifies the scratch pool, all requests for those volumes are denied. NetBackup returns expired media to the scratch volume pool automatically (media that is returned must have been originally in the same scratch pool). To use NetBackup to manage the allocation of volumes to volume pools, do the following:

Create volume pools as required, but do not add any volumes to the pools. Define a scratch pool and add all of the volumes to it. NetBackup moves volumes to the other pools as volumes are needed.

326

Configuring tape media Adding a volume pool

Adding a volume pool

Use this procedure to add a new volume pool. After you add a new pool, add volumes to it by adding new volumes to NetBackup or by changing the pool of existing volumes. To add a volume pool

1 2 3

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media. On the Actions menu, select New > New Volume Pool. In the New Volume Pool dialog box, specify the attributes for the volume pool. See Volume pool properties on page 326.

Volume pool properties

You can specify various properties for a volume pool. The following are the properties you can configure for volume pools, either when you add a new pool or change an existing one. Table 8-12 Property
Catalog backup pool

Volume pool properties Description

Select this option to use this volume pool for hot, online backups of the NetBackup catalog. This check box creates a dedicated catalog backup pool to be used for NBU-Catalogg policies. A dedicated catalog volume pool facilitates quicker catalog restore times. Multiple catalog backup volume pools are allowed.

Description

Provides a brief description of the volume pool.

Configuring tape media Managing volume pools

327

Table 8-12 Property

Volume pool properties (continued) Description

Does not apply to the None pool, catalog backup pools, or scratch volume pools. Specifies the number of partially full media to allow in the volume pool for each of the unique combinations of the following in that pool:

Maximum number of partially full media

Robot Drive type Retention level

The default value is zero, which does not limit the number of full media that are allowed in the pool. Pool name The Pool name is the name for the new volume pool. Volume pool names are case-sensitive and can be up to 20 characters. Specifies that the pool should be a scratch pool. Symantec recommends that you use a descriptive name for the pool and use the term scratch pool in the description. Add sufficient type and quantity of media to the scratch pool to service all scratch media requests that can occur. NetBackup requests scratch media when media in the existing volume pools are allocated for use.

Scratch pool

Managing volume pools

The following sections describe the operations you can perform to manage volume pools.

Changing the properties of a volume pool

Use this procedure to change the properties of a volume pool. The properties you can change include the pool type (scratch pool or catalog backup pool). To change a volume pool

1 2

In the NetBackup Administration Console, in the left pane, select Media and Device Management > Media > Volume Pools. Select a pool in the Volume Pools list.

328

Configuring tape media About volume groups

3 4

Select Edit > Change. In the Change Volume Pool dialog box, change the attributes for the volume pool. See Volume pool properties on page 326.

Deleting a volume pool

You cannot delete any of the following pools:

A volume pool that contains volumes The NetBackup volume pool The None volume pool The default CatalogBackup volume pool The DataStore volume pool

To delete a volume pool

1 2 3

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media > Volume Pools. Select a volume pool from the pools in the Volume Pools list. Ensure that the volume pool is empty. If the pool is not empty, change the pool name for any volumes in the pool. If the volumes are not needed, delete them. On the Edit > menu, select Delete. Click Yes or No in the confirmation dialog box.

4 5

About volume groups

A volume group identifies a set of volumes that reside at the same physical location. The location can be either the robot in which the volumes reside, standalone storage, or off-site storage if you use the NetBackup Vault option. When you add media to NetBackup, NetBackup assigns all volumes in a robot to that robot's volume group. Alternatively, you can assign the media to a different group. Volume groups are convenient for tracking the location of volumes, such as the case when a volume is moved off site. Volume groups let you perform operations on a set of volumes by specifying the group name rather than each individual media ID of each volume. Operations include moves between a robotic library and a standalone location or deletions from NetBackup.

Configuring tape media About media sharing

329

If you move a volume physically, you also must move it logically. A logical move means to change the volume attributes to show the new location. The following are the rules for assigning volume groups:

All volumes in a group must be the same media type. However, a media type and its corresponding cleaning media type are allowed in the same volume group (such as DLT and DLT_CLN). All volumes in a robotic library must belong to a volume group. You cannot add volumes to a robotic library without specifying a group or having Media Manager generate a name for the group. The only way to clear a volume group name is to move the volume to standalone and not specify a volume group. More than one volume group can share the same location. For example, a robotic library can contain volumes from more than one volume group and you can have more than one standalone volume group. All volumes in a group must be in the same robotic library or be standalone. That is, you cannot add a group (or part of a group) to a robotic library if it already exists in another robotic library.

Examples of volume group usage are available. See the NetBackup Administrators Guide, Volume II.

About media sharing

Media sharing allows media servers to share media for write purposes (backups). Media sharing provides the following benefits:

Increases the utilization of media by reducing the number of partially full media. Reduces media-related expenses because fewer tape volumes are required and fewer tape volumes are vaulted (NetBackup Vault option). Reduces administrative overhead because you inject fewer scratch media into the robotic library. Increases the media life because tapes are mounted fewer times. Media are not repositioned and unmounted between write operations from different media servers. Reducing media mounts requires appropriate hardware connectivity between the media servers that share media and the drives that can write to that media. Appropriate hardware connectivity may include Fibre Channel hubs or switches, SCSI multiplexors, or SCSI-to-fibre bridges.

330

Configuring tape media Configuring unrestricted media sharing

You can configure the following media sharing:

Unrestricted media sharing. See Configuring unrestricted media sharing on page 330. Media media sharing with server groups. See Configuring media sharing with a server group on page 330.\

Note: The access control feature of Sun StorageTeck ACSLS controlled robots is not compatible with media sharing. Media sharing restricts volume access by the requesting hosts IP address. Use caution when you implement media sharing in an ACSLS environment.

Configuring unrestricted media sharing

Unrestricted media sharing means that all NetBackup media servers and NDMP hosts in your NetBackup environment can share media for writing. Note: Do not use unrestricted media sharing and media sharing server groups. If you use both, NetBackup behavior is undefined. To configure unrestricted media sharing

1 2 3 4

In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Host Properties > Master Servers. In the right pane, double-click the master server. Select Media Select Enable Unrestricted Media Sharing for All Media Servers. If you allow unrestricted allow media sharing in your NetBackup environment, you do not need to create media sharing groups.

Click OK.

Configuring media sharing with a server group

Media sharing with a server group restricts the sharing to members of the group. See About server groups on page 223. Table 8-13 outlines the process for configuring media sharing with a server group.

Configuring tape media Configuring media sharing with a server group

331

Table 8-13 Step

Step 1

Configuring media sharing with a server group process overview Description

Beyond the scope of the NetBackup documentation.

Action
Ensure the appropriate connectivity between and among the media servers and robots and drives.

Step 2

Configure the media sharing server See Configuring a server group group. on page 224. Optionally, configure the volume pools for media sharing. Set the Maximum number of partially full media property for those pools. See Adding a volume pool on page 326. See Changing the properties of a volume pool on page 327.

Step 3

Step 4

Configure the backup policies that Set the Policy Volume Pool and Media use the volume pools and media Owner properties of the backup policies. sharing groups. See Creating a policy using the Policy Configuration Wizard on page 524.

332

Configuring tape media Configuring media sharing with a server group

Chapter

Inventorying robots
This chapter includes the following topics:

About robot inventory When to inventory a robot About showing a robot's contents Showing the media in a robot About comparing a robot's contents with the volume configuration Comparing media in a robot with the volume configuration About updating the volume configuration Updating the volume configuration with a robot's contents Robot inventory options Configuring media settings About bar codes Configuring bar code rules Configuring media ID generation rules Configuring media type mappings About the vmphyinv physical inventory utility Example volume configuration updates

334

Inventorying robots About robot inventory

About robot inventory

Robot inventory is a logical operation that verifies the presence of media. (Robot inventory does not inventory the data on the media.) After you physically add, remove, or move volumes in a robot, use a robot inventory to update the NetBackup volume configuration. Table 9-1 describes the NetBackup Administration Console robot inventory options for the robotic libraries that contain bar code readers and contain bar coded media. Table 9-1 Inventory option
Show contents

Robot inventory options Description

Displays the media in the selected robotic library; does not check or change the EMM database. See About showing a robot's contents on page 337. For the robotic libraries without bar code readers (or that contain media without bar codes), you can only show the contents of a robot. However, more detailed information is required to perform automated media management. Use the vmphyinv physical inventory utility to inventory such robots. See About the vmphyinv physical inventory utility on page 373.

Compare contents with volume configuration

Compares the contents of a robotic library with the contents of the EMM database but does not change the database. See About comparing a robot's contents with the volume configuration on page 341.

Preview changes

Compares the contents of a robotic library with the contents of the EMM database. If differences exist, NetBackup recommends changes to the NetBackup volume configuration. See About previewing volume configuration changes on page 345.

Inventorying robots When to inventory a robot

335

Table 9-1 Inventory option

Robot inventory options (continued) Description

Update volume configuration Updates the database to match the contents of the robot. If the robot contents are the same as the EMM database, no changes occur. See About updating the volume configuration on page 343.

When to inventory a robot

Table 9-2 describes the criteria to use to determine when to inventory a robot and which options to use for the inventory. Table 9-2 Action
To determine the contents of a robot

Robot inventory criteria Inventory option to use

Use the Show contents option to determine the media in a robot and possibly their bar code numbers. See Showing the media in a robot on page 340.

To determine if volumes were For robots with bar code readers and robots that contain moved physically within a robot media with bar codes, use the Compare contents with volume configuration option. See Comparing media in a robot with the volume configuration on page 342. To add new volumes to a robot (a For any robot NetBackup supports, use the Update new volume is one that does not volume configuration option. have a NetBackup media ID) The update creates media IDs (based on bar codes or a prefix that you specify). See Updating the volume configuration with a robot's contents on page 345. To determine whether new media Use the Preview changes option, which compares the have bar codes before you add contents of the robot with the NetBackup volume them to NetBackup configuration information. After you examine the results, use the Update volume configuration option to update the volume configuration if necessary. See Updating the volume configuration with a robot's contents on page 345.

336

Inventorying robots When to inventory a robot

Table 9-2 Action

Robot inventory criteria (continued) Inventory option to use

If the robot supports bar codes and the volume has a readable bar code, use the Update volume configuration option. NetBackup updates the residence information to show the new robotic location. NetBackup also updates the robot host, robot type, robot number, and slot location. Specify the volume group to which the volume is assigned. See Updating the volume configuration with a robot's contents on page 345. If the robot does not support bar codes or the volumes do not contain readable bar codes, move the volumes or use the physical inventory utility. See About moving volumes on page 318. See About the vmphyinv physical inventory utility on page 373.

To insert existing volumes into a robot (an existing volume is one that already has a NetBackup media ID)

To move existing volumes between robotic and stand-alone (an existing volume is one that already has a NetBackup media ID)

If the robotic library supports bar codes and the volume has a readable bar code, use the Update volume configuration option. NetBackup updates the residence information to show the new robotic or stand-alone location. See Updating the volume configuration with a robot's contents on page 345.

To move existing volumes within a robot (an existing volume is one that already has a NetBackup media ID)

If the robot supports bar codes and the volume has a readable bar code, use the Update volume configuration option. NetBackup updates the residence information to show the new slot location. See Updating the volume configuration with a robot's contents on page 345. If the robot does not support bar codes or if the volumes do not contain readable bar codes, move the volumes or use the physical inventory utility. See About moving volumes on page 318. See About the vmphyinv physical inventory utility on page 373. See Volume Configuration Example 7: Adding existing volumes when bar codes are not used on page 390.

Inventorying robots About showing a robot's contents

337

Table 9-2 Action

Robot inventory criteria (continued) Inventory option to use

If the robotic library supports bar codes and the volume has a readable bar code, use the Update volume configuration option. NetBackup updates the NetBackup volume configuration information. See Updating the volume configuration with a robot's contents on page 345. If the robots do not support bar codes or the volumes do not contain readable bar codes, move the volumes or use the physical inventory utility. See About moving volumes on page 318. See About the vmphyinv physical inventory utility on page 373. For either operation, perform the following updates:

To move existing volumes from one robot to another (an existing volume is one that already has a NetBackup media ID)

First move the volumes to stand alone Then move the volumes to the new robot

If you do not perform both updates, NetBackup cannot update the entries and writes an "Update failed" error. See Volume Configuration Example 6: Moving existing volumes between robots on page 389. To remove existing volumes from For any robot NetBackup supports, use the Update a robot (an existing volume is one volume configuration option to update the NetBackup that already has a NetBackup volume configuration information. media ID) See Updating the volume configuration with a robot's contents on page 345.

About showing a robot's contents

Show contents inventories the selected robotic library and generates a report. This operation does not check or change the EMM database. Use this option to determine the contents of a robot. The contents that appear depend on the robot type. Table 9-3 describes the report contents.

338

Inventorying robots About showing a robot's contents

Table 9-3 Robot and media

Show contents description Report contents

Shows if each slot has media and lists the bar code for the media. Shows if each slot has media.

The robot has a bar code reader and the robot contains media with bar codes. The robot does not have a bar code reader or the robot contains media without bar codes. API robot.

Shows a list of the volumes in the robot. See About inventory results for API robots on page 338.

Figure 9-1 is an example of the report. Figure 9-1 Show contents report

See Showing the media in a robot on page 340.

About inventory results for API robots

Table 9-4 describes the contents of the robot inventory for the API robots.

Inventorying robots About showing a robot's contents

339

Table 9-4 Robot type

ACS

API robot report contents Report contents

The results, received from ACS library software, show the following: The ACS library software volume ID. The NetBackup media ID corresponds to the ACS library software volume ID. The ACS media type.

The NetBackup Media Manager media type. The mapping between the ACS library software media type and the corresponding NetBackup Media Manager media type (without considering optional bar code rules).

TLH

The results, received from the Automated Tape Library (ATL) library manager, show the following: The volume serial number (volser). The Media Manager media ID corresponds to the ATL volser. The ATL media type.

The Media Manager media type. The mapping between the ATL media type and the corresponding Media Manager media type (without considering optional bar code rules).

TLM

The results, received from the DAS/SDLC server, show the following: The volume serial number (volser). The Media Manager media ID corresponds to the DAS/SDLC volser. The DAS/SDLC media type

The Media Manager media type. The mapping between the DAS/SDLC media type and the corresponding Media Manager media type (without considering optional bar code rules).

Figure 9-2 shows the results for an ACS robot; the results for other API robots are similar.

340

Inventorying robots Showing the media in a robot

Figure 9-2

Show contents report (API robot)

Showing the media in a robot

Use the following procedure to show the media that is in a robot. See About robot inventory on page 334. See Robot inventory options on page 348. To show the media in a robot

1 2

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media > Robots. Select the robot you want to inventory.

Inventorying robots About comparing a robot's contents with the volume configuration

341

On the Actions menu, select Inventory Robot.

4 5

In the Robot Inventory dialog box, select Show contents. Click Start to begin the inventory.

About comparing a robot's contents with the volume configuration

Compare contents with volume configuration compares the contents of a robotic library with the contents of the EMM database. Regardless of the result, the database is not changed. Table 9-5 Robot and media
The robot can read bar codes

Compare contents description Report contents

The report shows the differences between the robot and the EMM database

342

Inventorying robots Comparing media in a robot with the volume configuration

Table 9-5 Robot and media

Compare contents description (continued) Report contents

The report shows only whether a slot contains a volume If the media cave bar codes, this operation is useful for determining if volumes have been physically moved within a robot.

The robot cannot read bar codes

For API robots

The media ID and media type in the EMM database are compared to the information that is received from the vendors robotic library software.

If the results show that the EMM database does not match the contents of the robotic library, perform the following actions:

Physically move the volume. Update the EMM database. Use Actions > Move or use the Update volume configuration option.

See About updating the volume configuration on page 343. Figure 9-3 shows a sample compare report. Figure 9-3 Compare contents report (API robot)

See Comparing media in a robot with the volume configuration on page 342.

Comparing media in a robot with the volume configuration

Use the following procedure to compare the media in a robot with the EMM database.

Inventorying robots About updating the volume configuration

343

See About robot inventory on page 334. See Robot inventory options on page 348. To compare media in a robot with the volume configuration

1 2 3

In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media > Robots. Select the robot you want to inventory. On the Actions menu, select Inventory Robot.

4 5

In the Robot Inventory dialog box, select Compare contents with volume configuration. Click Start to begin the inventory.

About updating the volume configuration

Update volume configuration updates the database to match the contents of the robot. If the robot contents are the same as the EMM database, no changes occur.

344

Inventorying robots About updating the volume configuration

For a new volume (one that does not have a NetBackup media ID), the update creates a media ID. The media ID depends on the rules that are specified on the Advanced Robot Inventory Options dialog box. See Robot inventory options on page 348. For API robots, the update returns an error if the volume serial number or the media ID contain unsupported characters. For robots without bar code readers, the new media IDs are based on a media ID prefix that you specify. Similarly, for volumes without readable bar codes, the new media IDs are based on a media ID prefix that you specify Figure 9-4 is an example for an ACS robot. Results for other API robots are similar. Robot inventory update returns an error if it encounters unsupported characters in the volume serial number or media identifier from API robots. See Volume update prerequisites on page 344. Figure 9-4 Update volume configuration for API robot report

See Updating the volume configuration with a robot's contents on page 345.

Volume update prerequisites

The following are the robot prerequisites and media prerequisites for updating the volume configuration:

The robotic library must read bar codes. Volumes in the library must have readable bar codes.

You can check the bar code capabilities of the robotic library and the volumes by comparing the robot contents with the NetBackup volume configuration. See Comparing media in a robot with the volume configuration on page 342.

Inventorying robots Updating the volume configuration with a robot's contents

345

If the robotic library does not support bar codes or the volumes do not have readable bar codes, save the results of the compare operation. The results can help you determine a media ID prefix if you use the Media Settings tab of the Advanced Options dialog box to assign a prefix.

About previewing volume configuration changes

Use this option to preview the changes before you update the EMM database. This option lets ensure that all new media have bar codes before you add them to the EMM database. If you select Preview changes and any recommended changes are found, a dialog box asks if you want to accept the recommended changes. If you click Yes, you do not need to perform a separate Update volume configuration operation. Note: If you preview the configuration changes first and then update the EMM database, the update results may not match the results of the preview operation. Possible causes may be the changes that occur between the preview and the update. Changes can be to the state of the robot, to the EMM database, to the bar code rules, and so on. Figure 9-5 Preview volume configuration changes (non-API robot)

See Updating the volume configuration with a robot's contents on page 345.

Updating the volume configuration with a robot's contents

Use the procedure in this topic to update the EMM database with the contents of a robot. See About robot inventory on page 334.

346

Inventorying robots Updating the volume configuration with a robot's contents

You can change the default settings and rules that NetBackup uses to name and assign attributes to new media. For most configurations, the default settings work well. Change the settings only if the configuration has special hardware or usage requirements. Table 9-6 shows the rules you can configure. Table 9-6 What
Media settings Bar code rules Media ID generation rules

Attributes for new media Where

See Configuring media settings on page 349. See Configuring bar code rules on page 361. See Configuring media ID generation rules on page 363. See Configuring media type mappings on page 366.

Map media for API robots

To update the volume configuration with a robot's contents

1 2 3

If necessary, insert new volume(s) into the robotic library. In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Media > Robots. Select the robot you want to inventory.

Inventorying robots Updating the volume configuration with a robot's contents

347

On the Actions menu, select Inventory Robot.

5 6

In the Robot Inventory dialog box, select Update volume configuration. By default, Preview changes is selected. To update without previewing changes, clear Preview changes. Note: If you preview the configuration changes first, then update the EMM database, the update results may not match the results of the preview operation. Possible causes may be the changes that occur between the preview and the update. Changes can be to the state of the robot, to the EMM database, to the bar code rules, and so on.

To change the default settings and rules that NetBackup uses to name and assign attributes to new media, click Advanced Options. Table 9-6 shows the settings and rules you can configure.

Click Start to begin the inventory.

348

Inventorying robots Robot inventory options

Robot inventory options

The following robot inventory options are available by using the NetBackup Administration Console:
Advanced options The Advanced Options option is active if Update volume configuration is selected. It opens the Advanced Robot Inventory Options dialog box, from which you can configure more options. See Configuring media settings on page 349. See Configuring bar code rules on page 361. See Configuring media ID generation rules on page 363. See Configuring media type mappings on page 366. For most configurations, the default settings work well. Change the settings only if the configuration has special hardware or usage requirements. Device host The Device host option is the host that controls the robot. In NetBackup Enterprise Server, specify the device host. The Empty media access port prior to update operation is active only for the robots that support that function. To inject volumes in the robots media access port into the robot before you begin the update, select Empty media access port prior to update. The volumes to be injected must be in the media access port before the operation begins. If you select Empty media access port prior to update and the MAP is empty, you are not prompted to place volumes in the media access port.

Empty media access port prior to update

Note: If you use NetBackup to eject volumes from the robot, remove
the volumes from the media access port before you begin an inject operation. Otherwise, if the inject port and eject port are the same, the ejected volumes may be injected back into the robotic library. Robot Use the Robot option to select a robot to inventory. If you selected a robot in the NetBackup Administration Console, that robot appears in this field. Show contents Displays the media in the selected robotic library; does not check or change the EMM database. See About showing a robot's contents on page 337.

Inventorying robots Configuring media settings

349

Compare contents Compares the contents of a robotic library with the contents of the with volume EMM database but does not change the database. configuration See About comparing a robot's contents with the volume configuration on page 341. Preview changes Compares the contents of a robotic library with the contents of the EMM database. If differences exist, NetBackup recommends changes to the NetBackup volume configuration. See About previewing volume configuration changes on page 345. Update volume configuration Updates the database to match the contents of the robot. If the robot contents are the same as the EMM database, no changes occur. See About updating the volume configuration on page 343.

Configuring media settings

Use the Media Settings tab of the Advanced Robot Inventory Options dialog box to perform the following actions:

For existing media, specify the volume group For new media, specify the media settings

350

Inventorying robots Configuring media settings

To configure media settings

1 2

In the Robot Inventory dialog box, click Advanced Options. In the Advanced Robot Inventory Options dialog box, click the Media Settings tab.

Configure the settings. See Media settings - existing media on page 350. See Media settings - new media on page 352.

Click OK.

Media settings - existing media

For the media that already exists in your volume configuration, you can specify the volume group for two conditions: if the media are removed from the robot or if the media are moved into or within the robot.

Media that have been removed from the robot The volume group to assign to the media that are removed from the robot. The list contains the following selections:

Inventorying robots Configuring media settings

351

AUTO GENERATE NetBackup automatically generates a new volume group. DEFAULT If there is an existing group with a compatible residence for the volume, the volume is added to that group. If a suitable volume group does not exist, NetBackup generates a new volume group name. The media are not assigned to a volume group.

NO VOLUME GROUP

Other selections may be available, depending on the setting of the Media type field as follows:
DEFAULT The selection includes the volume groups that are valid for the robots default media type. The selection includes the volume groups that are valid for the specified media type. To specify a volume group other than DEFAULT, enter a volume group name or select one from the list.

Other than DEFAULT

Media that have been moved into or within the robot The volume group to assign to the existing media that you have inserted into the robot (or moved to a new location within the robot). The list contains the following selections:
AUTO GENERATE NetBackup automatically generates a new volume group. DEFAULT If there is an existing group with a compatible residence for the volume, the volume is added to that group. If a suitable volume group does not exist, NetBackup generates a new volume group name.

Other selections may be available, depending on the setting of the Media type field as follows:
DEFAULT The selection includes the volume groups that are valid for the robots default media type. The selection includes the volume groups that are valid for the specified media type. To specify a volume group other than DEFAULT, enter a volume group name or select one from the list.

Other than DEFAULT

352

Inventorying robots Configuring media settings

If the robotic library contains multiple media types, Symantec recommends a DEFAULT setting. If you specify a volume group and volumes of different media types were moved into or within the robot, the new update fails. Volumes of different media types cannot have the same volume group. See Media settings - media type on page 353.

Media settings - new media

For new media in the robot to add to your volume configuration, specify the attributes for the new media.

Media settings - use the following Media ID prefix

If the robot supports bar codes and the volume has readable bar codes, a prefix is not required because NetBackup creates media IDs automatically. If either of the following conditions exist, specify a media ID prefix for any new media :

The robot does not support bar codes. The volume that was inserted does not have readable bar codes.

You can either select from a list or enter a prefix. The list contains the following selections:
DEFAULT If DEFAULT is selected, NetBackup performs the following actions:

Assigns the last MEDIA_ID_PREFIX entry as the default prefix if MEDIA_ID_PREFIX entries are defined in the vm.conf file. Uses the letter A if no MEDIA_ID_PREFIX entries are defined.

NOT USED

If NOT USED is selected, the operation succeeds only if the robot supports bar codes and the volume has readable bar codes. NOT USED can be useful if you use bar coded volumes and want updates to fail when unreadable or missing bar codes are encountered. If MEDIA_ID_PREFIX entries are defined in the vm.conf file, they appear in the list.

Other prefixes

To specify a prefix that is not in the list, enter the new prefix in the list box. NetBackup uses the prefix only for the current operation. You can specify a prefix of one to five alphanumeric characters. NetBackup assigns the remaining numeric characters to create six characters. For example, if the prefix is NETB, the media IDs are: NETB00, NETB01, and so on.

Inventorying robots Configuring media settings

353

Information about the vm.conf file is available. See the NetBackup Administrators Guide, Volume II.

Media settings - use bar code rules

Specifies whether or not to use bar code rules to assign attributes for new media. To enable bar code rule support for API robots, add an API_BARCODE_RULES entry to the vm.conf file. See About bar codes on page 356. See Configuring bar code rules on page 361. Information about the vm.conf file is available. See the NetBackup Administrators Guide, Volume II.

Media settings - media type

Specifies the type for the new media that are added to a robot. The list includes the media types that are valid for the robot. Note: For API robots, the Media type is always set to DEFAULT. To specify a media type for API robots, use the Media Type Mappings tab of the dialog box. See Configuring media type mappings on page 366.

Media type when using bar code rules

If you use bar code rules, choose one of the following:
DEFAULT NetBackup uses the bar code rules to determine the media type that is assigned. Each media type to be added should have a bar code rule. For example, assume that you want to add DLT and half-inch cartridges to a TLD robot with a single update operation. First create separate bar code rules for DLT and half-inch cartridges and then select the specific media types when you create the bar code rules. Finally, select DEFAULT on the Media Settings tab. The correct media type is assigned to each media. If you choose DEFAULT on the Media Settings tab and DEFAULT in the bar code rule, NetBackup assigns the default media type for the robot.

354

Inventorying robots Configuring media settings

A specific media You can use a single bar code rule to add media of different types, type from the list. such as DLT and half-inch cartridges (HCART) to a TLD robot. First, select a specific media type on the Media Settings tab. Second, select DEFAULT for the bar code rule media type when you create the bar code rule. You can perform one update for DLT and another for half-inch cartridge, and the bar code rule assigns the correct media type. If you specify a value other than DEFAULT, the bar code rule media type must be the same as the media or be DEFAULT. If not, the bar code rule does not match the media (except for cleaning media). Table 9-7 shows some combinations of media types on the Media Settings tab and bar code rule media types for a TLD (non-API) robot. It also shows the results when the media are added to the volume configuration.

Table 9-7 Media type on Media Settings tab

DLT HCART DLT DLT DLT_CLN DLT_CLN DLT_CLN DLT DEFAULT DEFAULT DEFAULT DEFAULT

Example media type and bar code rule combinations Bar code rule media Rule matches? type
DEFAULT DEFAULT DLT DLT_CLN DLT DLT_CLN DEFAULT Yes Yes Yes Yes No Yes Yes

Media type added to volume configuration

DLT HCART DLT DLT_CLN DLT_CLN DLT_CLN DLT_CLN DLT DLT DLT DLT_CLN Depends on robot type

8MM, 4MM, and so on No DEFAULT DLT DLT_CLN 8 MM, 4 MM, and so on Yes Yes Yes No

The fourth row in the table shows how both cleaning cartridges and regular volumes are added using one update operation.

Inventorying robots Configuring media settings

355

All the following conditions must be true:

The media type on the Media Settings tab is for regular media (DLT, in this example). The bar code matches a bar code tag. The media type for the bar code rule is cleaning media (DLT_CLN).

Another example is available: See Volume Configuration Example 5: Adding cleaning tapes to a robot on page 388. The sixth row and seventh row in the table show how to add only a cleaning tape. In the sixth row, you specify the cleaning media type on the Media Settings tab and in the bar code rule. In the seventh, specify the cleaning media on the Media Settings tab and specify default when you configure the bar code rule. See Configuring bar code rules on page 361.

Media type when not using bar code rules

Choose one of the following if bar code rules are not used:
DEFAULT NetBackup uses the media type that is configured for the drives if:

The drives in the robot are configured on the robot control host All drives the same type At least one drive is configured on the robot control host

If the drives are not the same type, NetBackup uses the default media type for the robot. A specific media type If the robot supports multiple media types and you do not want to use the default media type, select a specific type. The following applies only to NetBackup Enterprise Server. Select a specific media type if: the drives are not configured on the robot control host and the drives are not the default media type for the robot.

Table 9-8 shows the default media types for robots when drives are not configured on the robot control host: Table 9-8 Robot type Default media types for non-API robots Default media type

Tape Library 4 MM 4 MM cartridge tape. (TL4)

356

Inventorying robots About bar codes

Table 9-8 Robot type

Default media types for non-API robots (continued) Default media type

Tape Library 8 MM 8 MM cartridge tape. (TL8) Also supports 8 MM cartridge tape 2 and 8 MM cartridge tape 3. Tape Library DLT (TLD) DLT cartridge tape. Also supports the following:

DLT cartridge tape 2 and 3, 1/2-inch cartridge tape 1/2-inch cartridge tape 2, 1/2-inch cartridge tape 3

8 MM cartridge tape, 8 MM cartridge tape 2, 8 MM cartridge tape 3 DTF cartridge tape

1/4-inch cartridge tape

Media settings - volume pool

The volume pool for the new media. The actions depend on whether you use bar code rules to assign media attributes, as follows:
DEFAULT DEFAULT. If you select DEFAULT and: Use bar code rules, the bar code rules determine the volume pool to which new volumes are assigned Do not use bar code rules, NetBackup assigns data tapes to the NetBackup pool but does not assign cleaning tapes to a volume pool

A specific volume pool.

If you use bar code rules, this volume pool setting always overrides the rule.

About bar codes

When a robotic library has a bar code reader, it scans the media for bar codes and saves the results. The results associate the slot number and the bar code with the media in that slot. NetBackup obtains bar code and slot information from the robotic library. In the robots that have bar code readers, NetBackup verifies the bar code to ensure that the robot loads the correct volume. If the bar code on the volume does not match the bar code in the EMM database, NetBackup does one of the following:

Inventorying robots About bar codes

357

Assigns the request a pending status (for media-specific jobs such as a restore) Uses another volume (for backup or duplicate jobs)

If a requested volume is not in a robot, a pending request message appears in the NetBackup Administration Console Device Monitor. The operator must find the volume and do one of the following:

Check the Device Monitor to find a suitable drive and mount the requested volume in that drive. Move the volume into the robot, update the volume configuration to reflect the correct location for the media, and resubmit the request.

If the volume is labeled, the automatic volume recognition daemon reads the label and the drive is assigned to the request. If the volume is unlabeled and not associated with a robot, the operator manually assigns the drive to the request.

About bar code advantages

NetBackup functions well whether or not bar codes are used. However, Symantec suggests using media with bar codes in the robots that can read bar codes. Bar codes offer the following advantages:

Automatic media ID assignment When you add new media to a robot, NetBackup is able to assign media IDs according to specified criteria. More accurate tracking of volume location A robot inventory update can determine which volumes are in a robot. Increased performance Not using bar codes can adversely affect performance for some robots. A robot that reads bar codes performs a scan each time it moves a tape. The robot stores the correct bar code in memory or verifies a previously saved bar code. However, if a tape does not have a bar code, the robot retries the scan multiple times, degrading performance.

About bar code best practices

Consider the following practices when you select bar codes for volumes:

Bar codes usually appear on the labels that are attached to the outside of tape volumes. The maximum bar code length that NetBackup supports depends on the type of robot. See the NetBackup Device Configuration Guide.

358

Inventorying robots About bar codes

Always follow the robotic library vendors recommendations when purchasing bar code labels for use with NetBackup. Ensure that the bar codes have the correct number of characters. Bar codes can represent any combination of alpha and numeric characters, but different robots support different lengths of bar codes. See the robot vendors documentation to determine the requirements for a specific robot type. Use bar codes without spaces (at the beginning, at the end, or between any characters). Otherwise, the robot or NetBackup may not read them correctly. Volumes in an API robot have a real or a logical bar code. This volume identifier is used as the NetBackup media ID. This volume identifier is the volume serial number in ACS, TLH, and TLM robots. For API robots, the bar code for a volume must be identical to the NetBackup media ID. Match bar codes to media IDs by getting custom labels in the same series as the media IDs. For example, to match a set of media IDs from AA0000 to ZZ9999, get bar code labels in that series. When a robotic library can contain more than one media type, assign specific characters in the bar code to different media types. Do so by using media ID generation rules. Also, use bar codes to differentiate between data tapes and cleaning tapes or to differentiate between volume pools.

About bar code rules

A bar code rule specifies criteria for assigning attributes to new robotic volumes. NetBackup assigns these attributes by using the bar code for the volume that the robotic library provides and your bar code rules. In NetBackup, you choose whether to use bar code rules when you set up the robot inventory update operation. The bar code rules are stored on the EMM server. Note: NetBackup does not use bar code rules if a volume already uses a bar code.

About NetBackup actions for bar codes

When a robot inventory update operation uses NetBackup bar code rules and a new bar code is detected in the robot, NetBackup does the following:

Inventorying robots About bar codes

359

Searches the list of rules (from first to last) for a rule that matches the new bar code. If the bar code matches a rule, verifies that the media type in the rule is compatible with the media type specified for the update. If the media types match, assigns the attributes in the rule to the volume. The attributes include the media type, volume pool, maximum number of mounts (or number of cleanings), and description.

Example bar code rules

Table 9-9 shows some example bar code rules. Rules are sorted first according to the number of characters in the bar code tag and then by the order added. Two exceptions are the <NONE> and <DEFAULT> rules, which are always located at the end of the list. Table 9-9 Bar code tag
0080

Example bar code rules Media type

8MM

Volume pool
b_pool

Max mounts and cleanings

55

Description
New 008 volumes DLT backup DLT cleaning 8-mm cleaning 8-mm backup 8-mm no pool No bar code Other bar codes

DLT CLD CLT TL8 TL <NONE> <DEFAULT>

DLT DLT_CLN 8MM_CLN 8MM 8MM DEFAULT DEFAULT

d_pool None None t_pool None None NetBackup

200 30 20 0 0 0 0

Assume that you select the following media settings (update options) for the update operation for a new 8-mm volume in a TL8 robot: Media type = 8MM Volume group = 00_000_TL8 Use bar code rules = YES Volume pool = DEFAULT

360

Inventorying robots About bar codes

If a new volume in this robotic library has a bar code of TL800001, NetBackup uses the rule with the bar code tag of TL8. NetBackup assigns the following attributes to the volume:

Media ID = 800001 (last six characters of bar code) Volume group = 00_000_TL8 Volume pool = t_pool Maximum mounts = 0 (no maximum)

If a new volume has a bar code of TL000001, NetBackup uses the rule with the bar code tag of TL. NetBackup assigns the following attributes to the volume:

Media ID = 000001 (last six characters of bar code) Volume group = 00_000_TL8 Volume pool = None Maximum mounts = 0 (no maximum)

About media ID generation rules

Use media ID generation rules to override the default media ID naming method NetBackup uses. The default method uses the last six characters of the bar code the robot provides to generate the media ID. Note: To use media ID generation rules, the robot must support bar codes and the robot cannot be an API robot. Media ID generation rules are saved in the Media Manager configuration file (vm.conf). For example, two eight-character bar codes are S00006L1 and 000006L1. Without any media ID generation rules NetBackup uses the last six characters of the bar code to generate media IDs. In this example, the same media ID for the two bar codes is created (0006L1). Use a rule to control how NetBackup creates media IDs by specifying which characters of a bar code are used in the media ID. Or, specify that alphanumeric characters are to be inserted into the ID. Define multiple rules to accommodate the robots and the bar code lengths. Define rules to specific robots and for each bar code format that has different numbers or characters in the bar code. Multiple rules allow flexibility for the robots that support multiple media types.

Inventorying robots Configuring bar code rules

361

Configuring bar code rules

Use the Barcode Rules tab of the Advanced Robot Inventory Options dialog box to configure rules for assigning attributes to the new volumes that are added to a robot. NetBackup assigns bar codes when you select Use bar code rules on the Media Settings tab. To enable bar code rule support for API robots, add an API_BARCODE_RULES entry to the vm.conf file. See About bar codes on page 356. To configure bar code rules

1 2

In the Robot Inventory dialog box, click Advanced Options. In the Advanced Robot Inventory Options dialog box, click the Barcode Rules tab.

To add a rule, click New and then configure the rule in the dialog box. See Bar code rules settings on page 362.

362

Inventorying robots Configuring bar code rules

To change a rule, select the rule, click Change, and then change the rule in the dialog box. You can select and change multiple rules with one operation. The Change Barcode Rule dialog box appears for each rule that you selected for change. You cannot change the bar code tag of a bar code rule. You first must delete the old rule and then add a rule with a new bar code tag. See Bar code rules settings on page 362.

To delete a rule, select the rule, click Delete, and click OK in the confirmation dialog box. You can select and delete multiple rules with one operation.

Bar code rules settings

See Table 9-10 on page 362. describes the settings you can configure for bar code rules. NetBackup uses these rules to assign bar codes to new media. Table 9-10 Bar code rule setting
Barcode tag

Bar code rule settings

Description
A unique string of bar code characters that identifies the type of media. For example, use DLT as the bar code tag for a bar code rule if the following is true:

You use DLT on the bar codes to identify DLT tapes DLT is not used on any other bar codes in the robot

Similarly, if you use CLND for DLT cleaning media, use CLND as the bar code tag for the rule for DLT cleaning media. The bar code tag can have from 1 to 16 characters but cannot contain spaces. The following are the special bar code rules that can match special characters in the bar code tags: NONE Matches when rules are used and the volume has an unreadable bar code or the robot does not support bar codes. DEFAULT For volumes with bar codes, this tag matches when none of the other bar code tags match. However, the following must be compatible: the media type in the DEFAULT rule and the media type on the Media Settings tab.

You cannot change the bar code tag of a bar code rule. Instead, first delete the old rule, then add a rule with a new bar code tag. Use the Media Settings tab to set up the criteria for a robot update. See Configuring media settings on page 349.

Inventorying robots Configuring media ID generation rules

363

Table 9-10 Bar code rule setting

Description Maximum mounts

Bar code rule settings (continued)

Description
A description of the bar code rule. Enter from 1 to 25 characters. The maximum number of mounts (or cleanings) that are allowed for the volume. For data volumes, a value of zero means the volume can be mounted an unlimited number of times. For cleaning tapes, zero means that the cleaning tape is not used. Symantec recommends that you use bar codes for the cleaning media that cannot be confused with bar codes for data media. Doing so can avoid a value of 0 for cleaning tapes.

Media type option

The media type to assign to the media. The media type that is specified on the Media Settings tab always overrides the media type of the bar code rule. If you specify a value other than DEFAULT on the Media Settings tab, the bar code rule media type must be the same as the media or be DEFAULT. If not, the bar code rule does not match the media (except for cleaning media). See Media type when using bar code rules on page 353.

Note: When a media type is selected, the maximum mounts value may revert to the
default value for the specified media type. For example, it may revert to 0 for unlimited when you select a non-cleaning media type. See NetBackup media types on page 290. Volume pool The volume pool for the new media. The actions depend on whether you use bar code rules to assign media attributes. Select from the following:

DEFAULT

If DEFAULT is selected, NetBackup performs the following actions: If you use bar code rules, the bar code rules determine the volume pool to which new volumes are assigned. If you do not use bar code rules, NetBackup assigns data tapes to the NetBackup pool but does not assign cleaning tapes to a volume pool. A specific volume pool This volume pool setting always overrides any bar code rules.

Configuring media ID generation rules

For non-API robots only.

364

Inventorying robots Configuring media ID generation rules

To use media ID generation rules, the robot must support bar codes and the robot cannot be an API robot. See About media ID generation rules on page 360. To configure media ID generation rules

1 2

In the Robot Inventory dialog box, click Advanced Options. In the Advanced Robot Inventory Options dialog box, click the Media ID Generation tab.

To add a rule, click New and then configure the rule in the dialog box. See Media ID generation options on page 364.

To change a rule, select the rule, click Change, and then change the rule in the dialog box. You cannot change the robot number or bar code length of a rule. To change those properties, first delete the old rule and then add a rule. You can select and change multiple rules with one operation. A separate change rule dialog box appears for each rule that you selected for change.

To delete a rule, select the rule, click Delete, and click OK in the confirmation dialog box. You can select and delete multiple rules with one operation.

Media ID generation options

NetBackup uses rules to generate the IDs for media in robots. The default rule uses the last six characters of the bar code label from the tape.

Inventorying robots Configuring media ID generation rules

365

You can configure media ID generation rules to override the default rule. Control how NetBackup creates media IDs by defining the rules that specify which characters of a bar code label to use for the media ID. The following subsections describe the media ID generation rule options. The following list describes the media ID generation rule options:

Bar code length The Barcode length is the number of characters in the bar code for tapes in the robot. You cannot change the bar code length of a rule. Rather, first delete the rule and then add a new rule. Media ID generation rule A Media ID generation rule consists of a maximum of six colon-separate fields. Numbers define the positions of the characters in the bar code that are to be extracted. For example, the number 2 in a field extracts the second character (from the left) of the bar code. You can specify numbers in any order. To insert a specific character in a generated media idea, precede the character by a pound sign (#). Any alphanumeric characters that are specified must be valid for a media ID. Use rules to create media IDs of many formats. However, it may be difficult to manage media if the label on the media and the generated media ID are different. The table shows some examples of rules and the resulting media IDs. Bar Media ID generation rule code on tape
032945L1 1:2:3:4:5:6 032945L1 3:4:5:6:7 032945L1 #N:2:3:4:5:6 543106L1 #9:2:3:4 543106L1 1:2:3:4:#P

Generated media ID

032945 2945L N32945 9431 5431P

Robot number The number of the robot to which the rule applies. You cannot change the robot number of a rule. Rather, first delete the rule and then add a new rule.

366

Inventorying robots Configuring media type mappings

Configuring media type mappings

Applies to API robots only. For API robots, NetBackup contains default mappings from a vendor's media types to NetBackup media types. API robots are ACS, TLH, or TLM robot types. You can change the default mappings. Changes apply only to the current volume configuration update. You also can add media type mappings. See About adding media type mapping entries on page 367. See Default and allowable media types on page 368. See NetBackup media types on page 290. Note: You can write a bar code rule that contains the media types that are incompatible with vendor media types. However, the robot inventory update may assign NetBackup media types that are inconsistent with the vendor media types. Avoid this problem by grouping bar code rules by media type. Use the following procedure to change media type mappings.

Inventorying robots Configuring media type mappings

367

To configure media type mappings

1 2

In the Robot Inventory dialog box, click Advanced Options. In the Advanced Robot Inventory Options dialog box, click the Media Type Mappings tab.

The mappings that appear are only for the robot type that was selected for inventory. The tab shows the default mappings and any mappings you add.

3 4 5

Select the row that contains the robot-vendor media type mapping that you want to change and click Change Mapping. In the Change Media Mapping dialog box, select a Media Manager media type from the list of allowed selections. Click OK. To reset the mappings to the default, click Reset to Defaults.

About adding media type mapping entries

Applies to API robots only.

368

Inventorying robots Configuring media type mappings

The default media type mappings may not provide the wanted mappings. If not, add robot-specific media mappings to the vm.conf file on the host on which you are run the NetBackup Administration Console. Information about how to do so is available. See the NetBackup Administrators Guide, Volume II. Table 9-11 vm.conf entry
ACS_3490E = HCART2

Examples of robot-specific media mappings Result

Maps the ACS 3490E to the HCART2 media type.

Robot default without a vm.conf entry

HCART

ACS_DLTIV = DLT2

Maps ACS DLTIV to the DLT2 DLT for all ACS DLT media media type. types, including DLTIV Maps the TLH 3490E to the HCART2 media type. HCART

TLH_3490E = HCART2

Default and allowable media types

Applies to API robots only. The default media types on the Media Type Mappings tab are the media types provided by each robot vendor. The following tables contain the default and allowable media types for the API robots as follows:

The second column of each table shows the default media type. The third column shows the media types to which you can map the defaults. To do so, first add the allowable mapping entries to the vm.conf file. Some map entries are not allowed. For example, you cannot specify either of the following map entries for ACS robots:
ACS_DD3A = DLT ACS_DD3A = HCART4

Table 9-12 shows the default media types and the allowable media types for ACS robots.

Inventorying robots Configuring media type mappings

369

Table 9-12 ACS media type

3480 3490E DD3A

Default and allowable media types for ACS robots Default media type Allowable media types through mappings

1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3

DD3B

HCART, HCART2, HCART3

DD3C

HCART, HCART2, HCART3

DD3D

1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape 2 (HC2_CLN) HC3_CLN Digital Linear Tape (DLT) Digital Linear Tape (DLT) Digital Linear Tape (DLT) DLT, DLT2, DLT3 DLT, DLT2, DLT3 DLT, DLT2, DLT3

DLTIII DLTIIIXT DLTIV EECART JLABEL KLABEL LTO_100G LTO_10GB LTO_200G

1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge (HCART2) HCART, HCART2, HCART3

LTO_35GB LTO_400G

1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge tape 3 (HCART3) 1/2-inch cartridge tape 3 (HCART3) HCART, HCART2, HCART3

LTO_400W

HCART, HCART2, HCART3

LTO_50GB LTO_800G

1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge tape (HCART) HCART, HCART2, HCART3

370

Inventorying robots Configuring media type mappings

Table 9-12 ACS media type

LTO_800W

Default and allowable media types for ACS robots (continued) Default media type
1/2-inch cartridge tape (HCART)

Allowable media types through mappings

HCART, HCART2, HCART3

LTO_CLN1

1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape (HC_CLN) HC3_CLN 1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape (HC_CLN) HC3_CLN 1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape (HC_CLN) HC3_CLN 1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape (HC_CLN) HC3_CLN Digital Linear Tape 3 (DLT3) DLT, DLT2, DLT3 Digital Linear Tape (DLT) Digital Linear Tape (DLT) DLT, DLT2, DLT3 DLT, DLT2, DLT3

LTO_CLN2

LTO_CLN3

LTO_CLNU

SDLT SDLT_2 SDLT_4 SDLT_S1 SDLT_S2 SDLT_S3 SDLT_S4 STK1R STK1U

Digital Linear Tape 2 (DLT2) DLT, DLT2, DLT3 Digital Linear Tape (DLT) Digital Linear Tape (DLT) Digital Linear Tape (DLT) DLT, DLT2, DLT3 DLT, DLT2, DLT3 DLT, DLT2, DLT3

1/2-inch cartridge (HCART) HCART, HCART2, HCART3 1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape (HC_CLN) HC3_CLN 1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape (HC_CLN) HC3_CLN 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3

STK1Y

STK2P

STK2W

1/2-inch cartridge cleaning HC_CLN, HC2_CLN, tape 2 (HC2_CLN) HC3_CLN 1/2-inch cartridge tape 3 (HCART3) HCART, HCART2, HCART3

T10000CT

Inventorying robots Configuring media type mappings

371

Table 9-12 ACS media type

T10000T1

Default and allowable media types for ACS robots (continued) Default media type
1/2-inch cartridge tape 3 (HCART3) 1/2-inch cartridge tape 3 (HCART3) 1/2-inch cartridge tape 2 (HCART2)

Allowable media types through mappings

HCART, HCART2, HCART3

T10000TS

HCART, HCART2, HCART3

UNKNOWN (for unknown ACS media types)

HCART, HCART2, HCART3, HC_CLN, HC2_CLN, HC3_CLN, DLT, DLT2, DLT3, DLT_CLN, DLT2_CLN, DLT3_CLN HCART, HCART2, HCART3, HC_CLN, HC2_CLN, HC3_CLN, DLT, DLT2, DLT3, DLT_CLN, DLT2_CLN, DLT3_CLN

VIRTUAL

1/2-inch cartridge tape 2 (HCART2)

Table 9-13 shows the default and allowable media types for TLH robots. Table 9-13 TLH media type
3480 3490E 3590J 3590K 3592JA

Default and allowable media types for TLH robots Default Media Manager media Allowable media types through type mappings
1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3

3592JB

HCART, HCART2, HCART3

3592JX

HCART, HCART2, HCART3

3592JJ

HCART, HCART2, HCART3

372

Inventorying robots Configuring media type mappings

Table 9-13 TLH media type

3592JR

Default and allowable media types for TLH robots (continued) Default Media Manager media Allowable media types through type mappings
1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3

3592JW

HCART, HCART2, HCART3

UNKNOWN (for unknown TLH media types)

HCART, HCART2, HCART3

Table 9-14 shows the default and allowable media types for TLM robots. Table 9-14 Default and allowable media types for TLM robots Allowable media types through mappings
HCART, HCART2, HCART3 NONE

TLM media type Default media type

3480 OD_THICK 1/2-inch cartridge (HCART) NONE (OD_THICK is translated to media type REWR_OPT for robot contents reports. OD_THICK is ignored for all other robotic inventory operations) DECDLT 8MM 4MM 3590 DTF SONY_AIT LTO UNKNOWN (for unknown TLM media types) Digital Linear Tape (DLT) 8mm cartridge (8MM) 4mm cartridge (4MM) 1/2-inch cartridge (HCART) DTF cartridge (DTF) 8mm cartridge (8MM) 1/2-inch cartridge (HCART) 1/2-inch cartridge tape 2 (HCART2)

DLT, DLT2, DLT3 8MM, 8MM2, 8MM3 4MM HCART, HCART2, HCART3 DTF 8MM, 8MM2, 8MM3 HCART, HCART2, HCART3 HCART, HCART2, HCART3, DLT, DLT2, DLT3, 8MM, 8MM2, 8MM3

Inventorying robots About the vmphyinv physical inventory utility

373

Note: The following TLM media types are not supported: OD_THIN, D2, VHS, CD, TRAVAN, BETACAM, AUDIO_TAPE, BETACAMCL, DVCM, and DVCL.

About the vmphyinv physical inventory utility

For the following robotic libraries, the NetBackup Administration Console reports only the presence of media:

For the robots without bar code readers For the robots that contain media without bar codes

More detailed information is required to perform automated media management. For such robots, use the vmphyinv physical inventory utility. The vmphyinv physical inventory utility inventories nonbar coded tape libraries by performing the following actions:

Mounts each tape Reads the tape header Identifies the tape in each slot Updates the NetBackup volume configuration Use the vmphyinv -verbose option to display more information about the suggested changes. The -verbose option shows the number of drives available, the contents of each tape, if the media is a catalog tape. (The media format column of the summary contains NetBackup database for NetBackup catalog tapes.) This verbose information is written to stderr. To save the information, redirect stderr to a file.

vmphyinv is a command-line utility. Additional information about the syntax of

the vmphyinv command is available. See NetBackup Commands Reference Guide.

374

Inventorying robots About the vmphyinv physical inventory utility

Table 9-15
vmphyinv features

vmphyinv featues, requirements, restrictions, and when to use

The vmphyinv utility has the following features:

Can be run from any master server, media server, or SAN media server. Can be used with bar coded tape libraries because it verifies the contents of the media. Recognizes the NetBackup and the Backup Exec tape formats. Supports the remote administration. You do not need to run vmphyinv from the host to which the drives are attached. Tries to use multiple drives in a robot even if the drives are attached to different hosts. Works with shared drives (NetBackup Shared Storage Option). Supports all supported SCSI-based robot types. Can be used to inventory a single media in a standalone drive. Use the -u option or the -n option to specify the drive; the drive must contain media and it must be ready.

vmphyinv requirements and The vmphyinv utility has the following requirements and restrictions restrictions: It cannot distinguish between the volume records based on the application type. When you move the media from robotic drives to standalone drives, you cannot specify a new volume group for the media.

Inventorying robots About the vmphyinv physical inventory utility

375

Table 9-15

vmphyinv featues, requirements, restrictions, and when to use (continued)

Use vmphyinv to update the EMM database for NetBackup and Backup Exec media in the following cases: You want to inventory a robot that does not have a bar code reader or that contains nonbar coded media. You insert new media into a robotic library and no NetBackup volume records correspond to the media. Use the slot range or list option of vmphyinv to perform the inventory operation. You do not need to add volume records to the EMM database. You insert some media that have unknown media IDs or globally unique identifiers (GUIDs) into a robot. For example, you insert 10 media from a different tape library in slots 11 to 20. You do not know the IDs on the tapes. Use the slot range or list option of vmphyinv to perform the inventory operation. The vmphyinv utility mounts the media, reads the tape header, determines the media ID, and adds media records to the EMM database. Some of the media are misplaced and the EMM database does not reflect the correct physical location of these media. Inventory the robot or inventory a subset of media in the robot by using options in vmphyinv.

When to use vmphyinv

See How vmphyinv performs a physical inventory on page 375.

How vmphyinv performs a physical inventory

For a physical inventory, the vmphyinv utility performs the following sequence of operations:

Obtains a list of drives to mount the media See About the vmphyinv list of drives on page 376. Obtains a list of media to mount See About the media vmphyinv mounts on page 376. Mounts the media and reads the tape headers See How vmphyinv mounts the media and reads the tape header on page 377. Updates the EMM database See How vmphyinv updates the EMM database on page 378.

376

Inventorying robots About the vmphyinv physical inventory utility

About the vmphyinv list of drives

The list of drives the vmphyinv utility uses to mount the media is obtained from the EMM database. The drives do not need to be configured locally. You cannot specify which drives to use. However, you can specify the maximum number of drives to use, which lets you reserve drives for NetBackup backup or restore operations. Specify the number of drives by using the -drv_cnt drive_count option.

About the media vmphyinv mounts

The vmphyinv command accepts several options for the media to be mounted, as follows:

NetBackup robot number (-rn robot_number). The vmphyinv utility obtains a list of volume records for that robot and inventories each of the media in the list. To use this option, the NetBackup configuration must contain a volume record that corresponds to the robot number in the EMM database for the robot.

NetBackup robot number with filter options. If you do not want to inventory all of the media in a robot, specify a subset of the media by using filter options. Some filter options are volume pool, volume group, or slot range. To use these options, NetBackup volume records must exist. The following are some filter examples.
vmphyinv -rn 4 -pn bear Mounts the media only in robot 4 and in the volume pool bear. Mounts the media in robot 2 and in the volume group moon.

vmphyinv -rn 2 -v moon

vmphyinv -rn 1 -rc1 2 -number Mounts the media in robot 1 and slot range 2 to 4. 3 vmphyinv -rn 5 -pn NetBackup -v mars -rc1 2 -number 6 Mounts the media in robot 5, slot range 2 to 7, in volume group mars, and in the NetBackup volume pool.

NetBackup robot number and a list of media that belong to a specific robot. For example, if the -rn robot_number and -ml A00001:A00002:A00003 options are specified, only the three specified media are inventoried. If any of these media do not belong to the specified robot, the media are skipped and are not inventoried. To use this option, NetBackup volume records must exist.

Inventorying robots About the vmphyinv physical inventory utility

377

NetBackup robot number and a slot range or list. Sometimes, media from a different robot or some other source are moved to a robot and the media ID on the tape is unknown. In these cases, specify a slot range option or list option. With these options, the NetBackup volume record does not need to exist in the EMM database. However, you must specify the density (using the -d option). Note: For a robot that supports multiple media types, specify the density carefully. If you specify the incorrect density, vmphyinv cannot complete the mount and permanent drive failure can occur. The following are some filter examples.
vmphyinv -rn 1 -slot_range 2 10 Mounts the media in slot range 2 to 10 in robot 1. -d dlt vmphyinv -rn 0 -slot_list 3:4:5 Mounts the media in slots 3, 4, and 5 in robot 0. -d 8mm vmphyinv -rn 2 -slot_range 2 4 -slot_list 5:6:7 -d dlt Mounts the media in slots 2, 3, 4, 5, 6, and 7 in robot 2.

How vmphyinv mounts the media and reads the tape header
The following sequence of operations explains the mount process:

The vmphyinv utility contacts the NetBackup Volume Manager, vmd, on the

local host or remote host depending on where the drive is attached.

The NetBackup Volume Manager starts a process, oprd.

The vmphyinv utility communicates with oprd and sends the mount request

to oprd. After oprd receives the request, it issues a mount request to ltid.

The vmphyinv utility reads the tape header to determine the recorded media

ID or globally unique identifier (GUID). GUID is an identifier used by Symantec Backup Exec. Note: The default mount timeout is 15 minutes. Specify a different mount time by using the -mount_timeout option.

See About media that vmphyinv does not recognize on page 378. See How vmphyinv processes cleaning media on page 378.

378

Inventorying robots About the vmphyinv physical inventory utility

About media that vmphyinv does not recognize

If the media is not NetBackup media or Backup Exec media, the media is unmounted and the next media is mounted. vmphyinv does not generate a new record in the EMM database. To generate volume records for that media, use the vmupdate command.

How vmphyinv processes cleaning media

If the following conditions are all true, vmphyinv does not try to mount the media and the next media in the list is mounted:

You do not specify the vmphyinv slot range or list option. The robot contains cleaning media. The media type is specified as cleaning media in the volume record (such as 4mm_clean or dlt_clean).

If the robot contains cleaning media and any of the following conditions are true, vmphyinv tries to determine if the media is cleaning media:

You use the slot range or list option and the media type of volume record in the EMM database is not a cleaning media type. You use the slot range or list option, and the EMM database does not contains a volume record that corresponds to the cleaning media. You do not use the slot range or list option, and the EMM database does not contain a volume record that corresponds to the cleaning media.

The vmphyinv utility tries to determine if the media is cleaning media. It uses the SCSI parameters (sense keys, tape alert flags, and physical (SCSI) media types) returned by the robot. If vmphyinv cannot determine if the media is cleaning media, it tries to mount the media until the mount request times out. Note: NetBackup may not detect the presence of cleaning media for all drives. Some drives report the presence of cleaning media in a manner NetBackup cannot read.

How vmphyinv updates the EMM database

After all the media are mounted and the tape headers are read, vmphyinv displays a list of recommended changes. Accept or reject the changes. If you accept the changes, vmphyinv updates the EMM database.

Inventorying robots About the vmphyinv physical inventory utility

379

Table 9-16 Criteria or action

vmphyinv criteria and actions Description

For valid media types, vmphyinv performs the following actions: Changes the residence fields and description fields of any NetBackup media record if those fields do not match the media header. The description field is changed only if the media is Symantec Backup Exec media. Conditionally changes the media type of an unassigned NetBackup volume record. The media type is changed only if the new media type belongs to the same family of media types as the old media type. For example, the media type DLT can only be changed to DLT2 or DLT3. Never changes the volume pool, media type, and ADAMM_GUID of an assigned record. Never unassigns an assigned NetBackup volume.

The vmphyinv update criteria

How vmphyinv updates NetBackup media

The vmphyinv utility searches the EMM database. It checks if the media ID from the tape is present in the media ID field of any record in the EMM database. If the media ID exists, vmphyinv updates the NetBackup volume record that corresponds to the media ID. If the media ID does not exist, vmphyinv creates a new NetBackup volume record that corresponds to the NetBackup media.

380

Inventorying robots About the vmphyinv physical inventory utility

Table 9-16 Criteria or action

vmphyinv criteria and actions (continued) Description

The vmphyinv utility searches the EMM database. It checks if the media GUID from the tape is present in the ADAMM_GUID field of any record in the EMM database. If the media GUID exists, vmphyinv updates the NetBackup record that contains the GUID. If a media GUID does not exist, vmphyinv creates a new NetBackup record that corresponds to the Backup Exec media. vmphyinv may use an existing NetBackup volume record if the record does not correspond to any media in the tape library. For each NetBackup volume record, vmphyinv does the following: In the NetBackup record, updates the ADAMM_GUID field with the GUID and the Description field with the Backup Exec cartridge label in the tape header. Adds the media ID of the NetBackup record to the EMM database (if not already present). Each record is assigned to NetBackup (if not already assigned) and its state is set to Frozen in the EMM database. Changes the volume pool of the unassigned NetBackup volume records that are associated with Backup Exec media to the Backup Exec pool. If the Backup Exec pool does not exist, vmphyinv creates it.

How vmphyinv updates Backup Exec media

Note: If a MEDIA_ID_PREFIX entry is not specified in

the vm.conf file, NetBackup uses BE as the default prefix for Backup Exec media.

Inventorying robots Example volume configuration updates

381

Table 9-16 Criteria or action

vmphyinv criteria and actions (continued) Description

The vmphyinv utility may not be able to update the EMM database correctly in the following cases. These cases are reported as errors. If any of the following cases are encountered, you must intervene to continue: Duplicate media IDs are found. Two or more media in the same robot have the same media ID. A NetBackup volume record that belongs to a different robot is found. It contains the same media ID as the media ID read from the tape header. The media type, media GUID, or volume pool of an assigned volume record needs to be changed. The bar code of an existing volume record needs to be changed.

vmphyinv error cases

Example volume configuration updates

The following examples show different types of volume configuration updates. The examples include only the relevant volume attributes. See Volume Configuration Example 1: Removing a volume from a robot on page 382. See Volume Configuration Example 2: Adding existing stand-alone volumes to a robot on page 383. See Volume Configuration Example 3: Moving existing volumes within a robot on page 385. See Volume Configuration Example 4: Adding new volumes to a robot on page 386. See Volume Configuration Example 5: Adding cleaning tapes to a robot on page 388. See Volume Configuration Example 6: Moving existing volumes between robots on page 389. See Volume Configuration Example 7: Adding existing volumes when bar codes are not used on page 390.

382

Inventorying robots Example volume configuration updates

Volume Configuration Example 1: Removing a volume from a robot

The following is an example of how to remove a volume from a robotic library. It does not matter whether the robot supports bar codes. The following are the attributes for media ID 800001:
media ID media type bar code 800001 8MM cartridge tape TL800001

media description tl8 backup volume volume pool robot type volume group max mounts allowed NetBackup TL8 - Tape Library 8MM EXB220 0 (unlimited)

Assume that you remove the volume from the robotic library, specify the following on the Media Settings tab, then run the update:
media type volume group volume pool DEFAULT NONROB_8MM DEFAULT

The resulting volume attributes for media ID 800001 are as follows:

media ID media type bar code 800001 8MM cartridge tape TL800001

media description tl8 backup volume volume pool robot type volume group NetBackup NONE - Not Robotic NONROB_8MM

Inventorying robots Example volume configuration updates

383

max mounts allowed

0 (unlimited)

The new residence information in the EMM database shows a stand-alone location in the volume group. The volume group is specified on the Media Settings tab. The media type and volume pool remain unchanged. The results are the same for a volume that does not have a bar code.

Volume Configuration Example 2: Adding existing stand-alone volumes to a robot

The following is an example of how to add a stand-alone volume that has a bar code to a robotic library that supports bar codes (TL8). When you move volumes from one robot to another robot, perform separate updates. See Volume Configuration Example 6: Moving existing volumes between robots on page 389. The following are the volume attributes for media ID 800021, which has a readable bar code and already exists as a stand-alone volume:
media ID media type bar code 800021 8MM cartridge tape TL800021

media description 8MM stand-alone volume pool robot type volume group max mounts allowed None None (stand-alone) NONROB_8MM 0 (unlimited)

Assume that you insert the volume into a TL8 robot, specify the following on the Media Settings tab, then run the update:
media type volume group DEFAULT EXB220

384

Inventorying robots Example volume configuration updates

use bar code rules YES (selected) volume pool NetBackup

Assume that the bar code rules in Table 9-17 exist. Table 9-17 bar code tag
CLND CLN8 TL8 DLT TS <NONE> <DEFAULT>

Example bar code rules Media type

DLT_CLN 8MM_CLN 8MM DLT 8MM DEFAULT DEFAULT

Volume pool
None None NetBackup d_pool None None NetBackup

Max mounts/ cleanings

30 20 0 200 0 0 0

Description
dlt cleaning 8mm cleaning tl8 backup dlt backup 8mm no pool no bar code other bar codes

NetBackup recognizes that the media ID exists and changes the EMM database to reflect the new robotic location. NetBackup does not create a new media ID. The volume attributes for media ID 800021 are as follows:
media ID media type bar code 800021 8MM cartridge tape TL800021

media description 8MM stand-alone volume pool robot type robot number robot slot robot host volume group NONE TL8 - Tape Library 8MM 0 1 shark EXB220

Inventorying robots Example volume configuration updates

385

max mounts allowed

0 (unlimited)

The bar code matches the bar code of an existing stand-alone volume in the configuration. Therefore, NetBackup updates the residence information in the EMM database to reflect the new robotic location. Because the volume is not new, bar code rules are ignored. The only setting used on the Media Settings tab is the volume group for added or moved volumes. The media type setting was not used because this example was for a single existing volume that already had a media type.

Volume Configuration Example 3: Moving existing volumes within a robot

The following is an example of how to move a volume from one slot to another slot within the same robot. The robot supports bar codes and the volume has a readable bar code. Note: To move volumes within a robotic library, use Update volume configuration only if the robotic library supports bar codes and the volumes have readable bar codes. Otherwise, NetBackup cannot properly recognize the move. The following are the attributes for media ID 800002, which currently resides in slot 1 of the robotic library:
media ID media type bar code 800002 8MM cartridge tape TL800002

media description tl8 backup volume pool robot type robot number robot slot robot host volume group NetBackup TL8 - Tape Library 8MM 0 1 shark EXB220

386

Inventorying robots Example volume configuration updates

max mounts allowed

0 (unlimited)

Assume that you move the volume to empty slot 10, specify the following on the Media Settings tab, then run the update.
media type volume group DEFAULT EXB220

use bar code rules NO (not selected) volume pool DEFAULT

The resulting volume attributes are the following:

media ID media type bar code 800002 8MM cartridge tape TL800002

media description tl8 backup volume pool robot type robot number robot slot robot host volume group max mounts allowed NetBackup TL8 - Tape Library 8MM 0 10 shark EXB220 0 (unlimited)

The updated volume attributes show the new slot number, but all other information is unchanged.

Volume Configuration Example 4: Adding new volumes to a robot

The following is an example of how to add new volumes with bar codes to a robot that supports bar codes. Assume the following:

Inventorying robots Example volume configuration updates

387

The new volume is an 8MM tape with a readable bar code of TL800002. No media generation rules are defined. The drives in the robot all have a drive type of 8MM or no drives are configured on the robot control host.

Specify the following on the Media Settings tab and run the update:
Media type Volume group DEFAULT EXB2220

Use bar code rules YES (selected) Volume pool DEFAULT

Table 9-18 contains the example bar code rules. Table 9-18 Bar code tag
CLND CLN8 TL8 DLT TS <NONE>

Example bar code rules Media type

DLT_CLN 8MM_CLN 8MM DLT 8MM DEFAULT

Volume pool
None None NetBackup d_pool None None

Max mounts/ cleanings

30 20 0 200 0 0

Description
dlt cleaning 8mm cleaning tl8 backup dlt backup 8mm no pool no bar code

The bar code on the media matches the bar code rule named TL8 and the resulting volume attributes for the new volume are as follows:
Media ID Media type Bar code 800002 8MM cartridge tape TL800002

Media description tl8 backup Volume pool Robot type NetBackup TL8 - Tape Library 8MM

388

Inventorying robots Example volume configuration updates

Robot number Robot slot Robot host Volume group

0 1 shark EXB220

Maximummounts 0 (unlimited) allowed

No media ID generation rules exist. Therefore, the media ID is from the last six characters of the bar code. The new residence information in the EMM database shows the robot host, robot type, robot number, slot, and host. The volume group is from the Media Settings tab. The volume pool and the max mounts allowed are from the bar code rule. If bar code rules (or bar codes) are not used, the media description, volume pool, and max mounts allowed are set to the following defaults:
Media description Added by NetBackup Volume pool Max mounts NetBackup for data tapes or None for cleaning tapes 0 (unlimited)

Note: If the robot does not support bar codes or the bar code is unreadable, specify a Media ID prefix on the Media Settings tab. Alternatively, specify DEFAULT for the media ID. If you do not, NetBackup does not add new media IDs.

Volume Configuration Example 5: Adding cleaning tapes to a robot

A special case exists when you add cleaning tapes. For example, assume that you update a TLD robot. The tapes you inserted include regular tapes with bar codes that range from DLT00000 to DLT00010 and a cleaning tape with a bar code of CLN001. Table 9-19 contains the example bar code rules: Table 9-19 Bar code tag
CLN

Example bar code rules Media type

DLT_CLN

Volume pool
None

Max mounts/ cleanings

30

Description
dlt cleaning

Inventorying robots Example volume configuration updates

389

Table 9-19 Bar code tag

DL <NONE>

Example bar code rules (continued) Media type

DLT DEFAULT

Volume pool
d_pool None

Max mounts/ cleanings

200 0

Description
dlt backup no bar code

Specify the following on the Media Settings tab, then run the update.
media type volume group DLT STK7430

use bar code rules YES (selected)

The bar codes on the regular tapes match the DL bar code rule. The media type of the DL bar code rule matches the Media type on the Media Settings tab. The tapes are added as DLT. The cleaning tape matches the CLN bar code rule. NetBackup recognizes that DLT_CLN is the cleaning tape for DLT. NetBackup adds the cleaning tape CLN001 as DLT_CLN type media along with the regular volumes. This example shows NetBackups ability to add cleaning cartridges along with regular volumes when you use Update volume configuration. If the volumes you insert include a cleaning tape, NetBackup adds the volumes correctly if the following are true:

The Media type on the Media Settings tab is the regular media (DLT in this example). The bar code on the volume matches a bar code tag (CLN in this example). The media type for the bar code rule is the correct cleaning media (DLT_CLN in this example).

To add only cleaning media, specify the cleaning media type on the Media Settings tab and in the bar code rule (DLT_CLN in this example).

Volume Configuration Example 6: Moving existing volumes between robots

When you move volumes from one robot to another and the volumes in both robots are in the same EMM database, perform two separate updates.

390

Inventorying robots Example volume configuration updates

These updates move the volumes to stand alone, as an intermediate step, and then to the new robot. Otherwise, NetBackup is unable to update the entries and you receive an "Update request failed" error. This example assumes that robot 2 is able to read bar codes and the volume has readable bar codes. If not, NetBackup cannot manage the volumes. See Volume Configuration Example 7: Adding existing volumes when bar codes are not used on page 390. To move existing volumes between robots, use the following process:

Remove the volume from robot 1 and insert the volume in robot 2. Perform an Update volume configuration on robot 1. This action updates the volume attributes to show the volume as stand-alone. Perform an Update volume configuration on robot 2. This action updates the configuration to show the volume in robot 2.

Volume Configuration Example 7: Adding existing volumes when bar codes are not used
This example is not recommended and is included only to illustrate the undesirable results. The following is an example of how to add an existing stand-alone volume to a TL4 robot. A TL4 robot supports media inventory (detects media presence), but not bar codes. The following are the attributes for media ID 400021, which already exists as a stand-alone volume:
media ID media type bar code 400021 4MM cartridge tape -----------

media description 4MM stand-alone volume pool robot type volume group max mounts allowed None NONE - Not Robotic NONROB_4MM 0 (unlimited)

Inventorying robots Example volume configuration updates

391

Assume that you insert the volume into the robot, specify the following on the Media Settings tab, and run the update:
media type volume group media ID prefix volume pool DEFAULT 00_000_TL4 C4 DEFAULT

The resulting volume attributes are as follows:

media ID media type bar code C40000 4MM cartridge tape -----------

media description Added by NetBackup volume pool robot type robot number robot slot robot host volume group max mounts allowed NetBackup TL4 - Tape Library 4MM 0 1 shark 00_000_TL4 0 (unlimited)

Note that NetBackup assigned a new media ID to the volume (C40000). This undesired result occurs if you use Update volume configuration and the volumes do not contain readable bar codes or the robot does not support bar codes. Without a bar code, NetBackup cannot identify the volume and assumes that it is new. The media ID C40000 is generated from the media ID prefix specified on the Media Settings tab. The old media ID (400021) remains in the configuration. The information for the new media ID (C40000) shows the robotic location, which includes the robot host, robot type, number, slot, and host. The volume group and volume pool are configured according to the Media Settings tab selections. The maximum mounts allowed is set to the default (0). For this situation, use the physical inventory utility.

392

Inventorying robots Example volume configuration updates

See About the vmphyinv physical inventory utility on page 373.

Chapter

10

Configuring disk storage

This chapter includes the following topics:

Configuring BasicDisk storage About configuring disk pool storage About SharedDisk support in NetBackup 7.0 and later

Configuring BasicDisk storage

A BasicDisk type storage unit consists of a directory on locally-attached disk or network-attached disk that is exposed as a file system to a NetBackup media server. NetBackup stores backup data in the specified directory. No special configuration is required for BasicDisk storage. The directory is specified when the storage unit is configured. See Creating a storage unit on page 399.

About configuring disk pool storage

You can configure disk pools if you license a NetBackup feature that uses disk pools. For more information, see the NetBackup online Help or the following guides:

The NetBackup AdvancedDisk Storage Solutions Guide. The NetBackup Cloud Administrator's Guide. The NetBackup Deduplication Guide. The NetBackup OpenStorage Solutions Guide for Disk. The NetBackup Replication Director Solutions Guide.

394

Configuring disk storage About SharedDisk support in NetBackup 7.0 and later

About SharedDisk support in NetBackup 7.0 and later

The SharedDisk option is not supported beginning with the NetBackup 7.0 release. You can use a NetBackup 7.0 or later master server to configure, manage, and operate SharedDisk on NetBackup 6.5 media servers. For information about using SharedDisk, see the documentation for your NetBackup 6.5 release. With these changes, the following behavior is to be expected in NetBackup 7.0:

All configuration attempts to a SharedDisk storage server on a 7.0 or later media server fail with a storage server not found error. All read or write requests to a SharedDisk disk pool use 6.5 media servers only. If no 6.5 media servers are available, the requests fail. If you upgrade a 6.5 SharedDisk media server to 7.0 or later, NetBackup marks the storage servers as DOWN. It no longer functions as a SharedDisk storage server. To ensure that the media server is not considered for SharedDisk jobs, do one of the following: Restart the Enterprise Media Manager service after the upgrade or remove the storage server from all disk pools and then delete it. You can delete the SharedDisk disk pools and the SharedDisk storage servers that reside on 7.0 and later media servers. However, all delete operations on images fail. To delete images, do the following:

Expire the images and delete them from the catalog by using one of the following bpexpdate commands:
bpexpdate -backupid backupid -d 0 -nodelete

With this command, NetBackup does not run an image cleanup job. You can use NetBackup Management > Catalog to determine the backupid.
bpexpdate -backupid backupid -d 0 -force

With this command, NetBackup attempts an image cleanup job. It fails with error 174; you can ignore the error. You can use NetBackup Management > Catalog to determine the backupid.
bpexpdate -stype SharedDisk

With this command, NetBackup attempts an image cleanup job. It fails with error 174; you can ignore the error.

Delete the fragments of the expired images by using the following command:
nbdelete -allvolumes -force

Configuring disk storage About SharedDisk support in NetBackup 7.0 and later

395

Note: Symantec recommends that you use solutions other that SharedDisk. The AdvancedDisk storage option is another solution.

396

Configuring disk storage About SharedDisk support in NetBackup 7.0 and later

Chapter

11

Configuring storage units

This chapter includes the following topics:

About the Storage utility Creating a storage unit About storage unit settings

About the Storage utility

The data that is generated from a NetBackup job is recorded into a type of storage that NetBackup recognizes. NetBackup recognizes the following storage configurations, all of which are configured in the Storage utility:

Storage units A storage unit is a label that NetBackup associates with physical storage. The label can identify a robot, a path to a volume, or a disk pool. Storage units can be included as part of a storage unit group or a storage lifecycle policy. See Creating a storage unit on page 399. Storage unit groups Storage unit groups let you identify multiple storage units as belonging to a single group. The NetBackup administrator configures how the storage units are selected within the group when a backup or a snapshot job runs. See About storage unit groups on page 447. Storage lifecycle policies Storage lifecycle policies let the administrator create a storage plan for all of the data in a backup or snapshot. See About storage lifecycle policies on page 457.

398

Configuring storage units About the Storage utility

A NetBackup administrator must define storage with the Storage utility before a backup or a snapshot job can run successfully.

Using the Storage utility

To use the storage utility

In the NetBackup Administration Console, expand Storage > Storage Units, Storage Unit Groups, or Storage Lifecycle Policies. The storage destinations that were created for the selected server are displayed in the right pane.

The storage configuration can be displayed for other master servers. See Accessing remote servers on page 905. Figure 11-1 Storage Unit node of the Storage utility

2 3 4 5 6 7

Table 11-1

Storage Unit utility

Number Description
1 2 Currently selected master server. Click to create a new storage unit. See About storage unit settings on page 413. 3 Click to create a new storage unit group. See Creating storage unit groups for backups on page 448.

Configuring storage units Creating a storage unit

399

Table 11-1

Storage Unit utility (continued)

Number Description
4 Click to copy a storage unit. See Creating a storage unit by copying a storage unit on page 401. 5 Click to initiate a data management job when using basic disk staging. See About basic disk staging on page 433. 6 Click to create a new storage lifecycle policy. See Creating a storage lifecycle policy on page 458. 7 Right-click in the right pane to view the shortcut menu.

Creating a storage unit

A storage unit is a label that NetBackup associates with physical storage. The label can identify a robot, a path to a volume, or a disk pool. Storage unit creation is part of several other wizards. However, a storage unit can be created directly from the Storage utility in the NetBackup Administration Console. To create a storage unit

1 2 3

In the NetBackup Administration Console, select the Storage utility. Select Actions > New > New Storage Unit. Enter a Storage unit name. See NetBackup naming conventions on page 897.

4 5

Select the Storage unit type. The selection specifies the type of storage that the storage unit uses: Media Manager, Disk, or NDMP. For disk storage units:

Select a disk type from the Disk type drop-down menu. The Disk type identifies the type of storage unit destination:
AdvancedDisk storage units BasicDisk storage units The destination is a disk pool.

The destination is a path to a volume on a host.

NDMP storage The destination is an NDMP host. The NDMP protocol is used to perform backups and recoveries.

400

Configuring storage units Creating a storage unit

OpenStorage storage units PureDisk storage unit SharedDisk storage units

The destination is a disk pool.

The destination is a disk pool.

The destination is a disk pool. See About SharedDisk support in NetBackup 7.0 and later on page 394. The destination is a SnapVault server.

SnapVault storage

Select a media server in the Media server drop-down menu. The selection indicates that the media server has permission to write to the storage unit. Absolutepathnametodirectory or Absolutepathnametovolumesetting. See Absolute pathname to directory or absolute pathname to volume setting for storage units on page 413. Maximum concurrent jobs See Maximum concurrent jobs storage unit setting on page 417. Reduce fragment size See Reduce fragment size storage unit setting on page 425. High water mark See High water mark storage unit setting on page 415. Low water mark See Low water mark storage unit setting on page 416. Enable block sharing See Enable block sharing storage unit setting on page 415. Enable Temporary staging area See Enable temporary staging area storage unit setting on page 428.

For Media Manager storage units, data is written to tape robots and stand-alone tape drives:.

Select a storage device from the Storage Device drop-down menu. Select a media server in the Media server drop-down menu. The selection indicates that the media server has permission to write to the storage unit. Maximum concurrent write drives

Configuring storage units Creating a storage unit

401

See Maximum concurrent write drives storage unit setting on page 416.

Enable multiplexing See Enable multiplexing storage unit setting on page 415. Reduce fragment size See Reduce fragment size storage unit setting on page 425.

Click OK to save the storage unit configuration.

Figure 11-2 shows the different storage unit types and the option that needs to be installed, if necessary. Figure 11-2 Storage unit types
Storage unit Storage unit types: Media Manager Points to a robot or a stand-alone drive NDMP Points to an NDMP host (NDMP Option) BasicDisk Points to a directory PureDisk Points to a disk pool (NetBackup Deduplication Option and PureDisk Storage Option) SnapVault Points to a SnapVault server (SnapVault option) OpenStorage (vendor name) Points to a disk pool (an intelligent appliance on a SAN) (OpenStorage Disk Option) AdvancedDisk Points to a disk pool (storage directly attached to a media server) (Flexible Disk Option) Disk

Creating a storage unit by copying a storage unit

The following procedure describes how to create a storage unit by copying a storage unit. To create a storage unit by copying an existing storage unit

1 2 3

In the NetBackup Administration Console, select NetBackup Management > Storage. In the right pane, select a storage unit. Click Actions > Copy Storage Unit.

402

Configuring storage units Creating a storage unit

Type a unique name for the new storage unit. For example, describe the type of storage. Use this name to specify a storage unit for policies and schedules. See NetBackup naming conventions on page 897.

Complete the fields in the Copy Storage Unit dialog box. See About storage unit settings on page 413.

Changing storage unit settings

Symantec suggests that changes be made only during periods when no backup activity is expected for the policies that use the affected storage units. To change storage unit settings

1 2

In the NetBackup Administration Console, select NetBackup Management > Storage. In the right pane, double-click the storage unit you want to change. Hold down the Control or Shift key to select multiple storage units.

Complete the fields on the Change Storage Unit dialog box. See About storage unit settings on page 413.

Deleting storage units

To delete a storage unit from a NetBackup configuration means to delete the label that NetBackup associates with the physical storage. Deleting a storage unit does not prevent files from being restored that were written to that storage unit, provided that the storage was not physically removed and the backup image has not expired. To delete a BasicDisk or Media Manager storage unit

Use the Catalog utility to expire any images that exist on the storage unit. This action removes the image from the NetBackup catalog. See Expiring backup images on page 788.

Do not manually remove images from the BasicDisk or Media Manager storage unit. Once the images are expired, they cannot be restored unless the images are imported. See About importing backup images on page 789.

NetBackup automatically deletes any image fragments from a disk storage unit or a disk pool. This deletion generally occurs within seconds of expiring

Configuring storage units Creating a storage unit

403

an image. However, to make sure that all of the fragments are deleted, check the directory on the storage unit to make sure that it is empty.

2 3 4 5 6 7

Select Storage >Storage Units. In the right pane, select the storage unit you want to delete. Hold down the Control or Shift key to select multiple storage units. Select Edit > Delete. In the confirmation dialog box, select the storage units to delete. Click OK. Modify any policy that uses a deleted storage unit to use another storage unit. If a storage unit points to disk pool, the storage unit can be deleted without affecting the disk pool.

Media Manager storage unit considerations

To create a storage unit of a tape robot or a stand-alone tape drive, select Media Manager as the Storage unit type. See About storage unit settings on page 413.

404

Configuring storage units Creating a storage unit

Figure 11-3

Media Manager storage unit settings

When NetBackup sends a job to a Media Manager storage unit, it requests resources from the Enterprise Media Manager (EMM). Then NetBackup requests that Media Manager mount the volume in a drive. If a stand-alone drive does not contain media or if a required volume is not available to a robot, a mount request appears in the Pending Requests pane of the Device Monitor. An operator can then find the volume, mount it manually, and assign it to the drive. Take the following items into consideration when adding a Media Manager storage unit:

Where to add the storage unit depends on which version of NetBackup is in use.

Configuring storage units Creating a storage unit

405

If using NetBackup Enterprise Server, add the storage unit to the master server. Specify the media server where the drives attach. If using NetBackup Server, add the storage unit to the master server where the drives attach. The robotic control must also attach to that server.

The number of storage units that you must create for a robot depends on the robots drive configuration.

Drives with identical densities must share the same storage unit on the same media server. If a robot contains two drives of the same density on the same media server, add only a single storage unit for the robot. Set the Maximum concurrent write drives setting to 2. See Maximum concurrent write drives storage unit setting on page 416. Drives with different densities must be in separate storage units. Consider an STK SL500 library that is configured as a Tape Library DLT (TLD). It can have both half-inch cartridge and DLT drives. Here, you must define a separate storage unit for each density. Applies only to NetBackup Enterprise Server. If a robots drives and robotic control attach to different NetBackup servers, specify the server where the drives attach as the media server. Always specify the same robot number for the drives as is used for the robotic control.

Stand-alone drives with the same density must be in the same storage unit. For example, if a server has two 1/4-inch qscsi drives, add a storage unit with Maximum concurrent write drives set to 2. Media and device selection logic chooses the drive to use when NetBackup sends a backup to this storage unit. The logic is part of the Enterprise Media Management (nbemm) service. Stand-alone drives with different densities must be in different storage units. A robot and a stand-alone drive cannot be in the same storage unit.

Disk storage unit considerations

NetBackup permits the creation of an unlimited number of disk storage units. Table 11-2 describes the different disk types that NetBackup can use as disk media.

406

Configuring storage units Creating a storage unit

Table 11-2 Type of disk storage unit

BasicDisk

Disk media descriptions

Description
A BasicDisk type storage unit consists of a directory on a locally-attached disk or a network-attached disk that is exposed as a file system to a NetBackup media server. NetBackup stores backup data in the specified directory. Notes about the BasicDisk type storage unit:

Do not include the same volume or file system in multiple BasicDisk storage units. BasicDisk storage units cannot be used in a storage lifecycle policy.

AdvancedDisk

An AdvancedDisk disk type storage unit is used for a dedicated disk that is directly attached to a NetBackup media server. An AdvancedDisk selection is available only when the Flexible Disk Option is licensed. NetBackup assumes exclusive ownership of the disk resources that comprise an AdvancedDisk disk pool. If the resources are shared with other users, NetBackup cannot manage disk pool capacity or storage lifecycle policies correctly. For AdvancedDisk, the NetBackup media servers function as both data movers and storage servers. See the NetBackup AdvancedDisk Storage Solutions Guide.

OpenStorage

An OpenStorage disk type storage unit is used for disk storage, usually provided by a third part vendor. The actual name of the disk type depends on the vendor. An OpenStorage selection is available only when the OpenStorage Disk Option is licensed. The storage is integrated into NetBackup through an API. The storage vendor partners with Symantec to integrate the storage into NetBackup. The storage host is the storage server. The NetBackup media servers function as the data movers. The storage vendor's plug-in must be installed on each media server that functions as a data mover. The logon credentials to the storage server must be configured on each media server. See the NetBackup OpenStorage Solutions Guide for Disk.

Configuring storage units Creating a storage unit

407

Table 11-2 Type of disk storage unit

PureDisk

Disk media descriptions (continued)

Description
A PureDisk disk type storage unit is used for deduplicated data for the following storage destinations: Media Server Deduplication Pool. NetBackup deduplicates the data and hosts the storage. Requires the NetBackup Deduplication Option license key. See the NetBackup Deduplication Guide. PureDisk storage pool. PureDisk hosts the storage. Therefore, a PureDisk environment must be configured. See the NetBackup PureDisk Getting Started Guide

PureDisk storage pools are exposed to NetBackup through one of the following options: NetBackup Deduplication Option. Requires PureDisk 6.6 or later to host the storage. PureDisk Deduplication Option (PDDO). Requires the PureDisk Storage Option license key. Requires PureDisk 6.5 or later. See the NetBackup PureDisk Deduplication Option Guide. Symantec provides a recommendation about using storage unit groups for deduplication. PureDisk appears as a selection when the NetBackup Deduplication Option or the PureDisk Storage Option is licensed. SnapVault A SnapVault storage unit is used to store images on Network Attached Storage (NAS). The SnapVault selection is available only when the NetBackup Snapshot Client option is licensed. SnapVault storage units cannot be used in a storage unit group or as part of a staging operation. For SnapVault, the NetBackup media servers function as the data movers. The SnapVault host is the storage server.

Not all settings are available on each disk storage unit type. See About storage unit settings on page 413. Note: Symantec recommends that you do not impose quotas on any file systems that NetBackup uses for disk storage units. Some NetBackup features may not work properly when file systems have quotas in place. (For example, the capacity-managed retention selection in lifecycles and staging to storage units.)

408

Configuring storage units Creating a storage unit

About the disk storage model

The NetBackup model for disk storage accommodates all Enterprise Disk Options. That is, it is the model for all disk types except for the BasicDisk type. The following items describe components of the disk storage model:

Data mover An entity that moves data between the primary storage (the NetBackup client) and the storage server. NetBackup media servers function as data movers. Depending on the Enterprise Disk Option, a NetBackup media server also may function as a storage server. Storage server An entity that writes data to and reads data from the disk storage. A storage server is the entity that has a mount on the file system on the storage. Depending on the NetBackup option, the storage server is one of the following:

A computer that hosts the storage A NetBackup media server

Disk pool A collection of disk volumes that are administered as an entity. NetBackup aggregates the disk volumes into pools of storage (a disk pool) you can use for backups. A disk pool is a storage type in NetBackup. When you create a storage unit, you select the disk type and then you select a specific disk pool.

Configuring credentials for CIFS and disk storage units

For Common Internet File System (CIFS) storage with AdvancedDisk and BasicDisk storage units, two NetBackup services on Windows computers require matching credentials. The following NetBackup services on Windows media servers to which the CIFS storage is attached must use the same credentials:

NetBackup Client Service The NetBackup Client Service is either bpcd.exe or bpinetd.exe, depending on NetBackup release level. Regardless of the binary file name, the service requires the credentials. NetBackup Remote Manager and Monitor Service The NetBackup Remote Manager and Monitor Service binary file name is nbrmms.exe.

Configuring storage units Creating a storage unit

409

The credentials must be valid Windows credentials that allow read and write access to the storage. Configure the credentials on the media server or media servers that have a file system mount on the CIFS storage. If credentials are not configured, NetBackup marks all CIFS AdvancedDisk and BasicDisk storage units that use the UNC naming convention as DOWN. To configure service credentials

1 2 3 4 5 6 7 8

In Windows, open the Services dialog box. How you open Services depends on the Windows version. Double-click the service name to open the Properties dialog box for the service. In the General tab, select the service that requires additional credentials. Click Stop to stop the service. Select the Log On tab. Select This account and then enter the credentials. Click Apply. Select the General tab. Click Start to start the service. Repeat the steps 2 to 7 for each service that requires additional credentials.

Disk storage units in storage lifecycle policies

Figure 11-4 is an example of how storage lifecycle policies can interact with volumes in a disk pool that a storage unit references. Two backup policies are created as follows:

A backup policy named Policy_gold has a gold classification. For storage, it is configured to use an SLP named Lifecycle_Gold, which has a gold data classification. A backup policy named Policy_silver has a silver classification. For storage, it is configured to use Any Available. That means it can use any available storage unit or any SLP that has a silver classification.

Two storage units are available to both backup policies as follows:

DSU_1 is an operation in Lifecycle_Gold and references DiskPool_A. DSU_2 is not in an SLP and references DiskPool_A.

DiskPool_A contains three disk volumes. Both the gold and the silver images can be written to any disk volume in the pool.

410

Configuring storage units Creating a storage unit

Figure 11-4
Backup policy Policy_Gold The data classification for this backup policy is gold. The policy is configured to write to Lifecycle_Gold. SLP Lifecycle_Gold

Storage lifecycle policies and disk storage units referencing disk pools
Backup policy Policy_Silver The data classification for this backup policy is silver. The policy is configured to write to any available storage unit.

Lifecycle_Gold contains a backup operation that writes to storage unit DSU_1. Storage unit DSU_2 Storage unit DSU_1 DSU_1 references DiskPool_A. Policy_Silver writes to DSU_2. DSU_2 references DiskPool_A.

DiskPool_A

Disk volume Gold image

Disk volume Gold image Silver image

Disk volume Gold image

Both backup policies may write to any volume in the disk pool that matches the data classification of the policy.

In this way, a single disk pool may contain images Gold image with different data Silver image classifications.

See About storage lifecycle policies on page 457.

Maintaining available disk space on disk storage units

Disk storage units can be managed so that they do not become entirely full and cause backups to fail. Create space for more images on a disk storage unit in the following ways:

Add new disk space. Set the High water mark to a value that best works with the size of backup images in the environment. See High water mark storage unit setting on page 415.

Maintain space on basic disk staging storage units in the following ways:

Increase the frequency of the relocation schedule. Or, add resources so that all images can be copied to a final destination storage unit in a timely manner. Run the nb_updatedssu script.

Configuring storage units Creating a storage unit

411

Upon NetBackup installation or upgrade, the nb_updatedssu script runs. The script deletes the .ds files that were used in previous releases as pointers to relocated data. Relocated data is tracked differently in the current release and the .ds files are no longer necessary. Under some circumstances, a .ds file cannot be deleted upon installation or upgrade. In that case, run the script again:
install_path\netbackup\bin\goodies\nb_updatedssu

Determine the potential free space. See Finding potential free space on a BasicDisk disk staging storage unit on page 440. Monitor disk space by enabling the Check the capacity of disk storage units host property. This General Server host property determines how often NetBackup checks 6.0 disk storage units for available capacity. Subsequent releases use internal methods to monitor disk space more frequently. See General Server properties on page 135.

NDMP storage unit considerations

The NetBackup for NDMP license must be installed on the media server to use the hosts as storage units. Media Manager controls NDMP storage units but the units attach to NDMP hosts. See About storage unit settings on page 413.

412

Configuring storage units Creating a storage unit

Figure 11-5

NDMP storage unit settings

Create NDMP storage units for drives directly attached to NAS filers. Any drive that is attached to a NetBackup media server is considered a Media Manager storage unit, even if used for NDMP backups. Note: Remote NDMP storage units may already be configured on a media server from a previous release. Upon upgrade of the media server, those storage units are automatically converted to Media Manager storage units. See the NetBackup for NDMP Administrators Guide for more information.

Configuring storage units About storage unit settings

413

About storage unit settings

The following topics describe the settings that appear for all types of storage units. The settings are listed alphabetically. Each setting does not appear for each storage unit type.

Absolute pathname to directory or absolute pathname to volume setting for storage units
Absolute pathname to directory or Absolute pathname to volume is available for any storage unit that is not based on disk pools. The setting specifies the absolute path to a file system or a volume available for backups to disk. Enter the path directly in the field, then click Add. Use any location on the disk, providing that sufficient space is available. Use platform-specific file path separators (/ and \) and colon (:) within a drive specification. The Properties button displays properties for the directory or volume. See Properties option in the Change Storage Units dialog box on page 424. Do not configure multiple BasicDisk sto