Veritas NetBackup Administrators Guide, Volume I

for UNIX and Linux

Release 6.5

12308276

Veritas NetBackup Administrators Guide, Volume I

Copyright 1993-2007 Symantec Corporation. All rights reserved. NetBackup 6.5 Symantec, the Symantec logo, and NetBackup 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. Portions of this software are derived from the RSA Data Security, Inc. MD5 MessageDigest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved. 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. THIS 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 NONINFRINGEMENT, 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 and commercial computer software documentation as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com Printed in the United States of America.

Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundled with this Veritas product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying release notes.

Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guide for license installation instructions.

Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone or email support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer email notification service.

Contents

Chapter 1

Introduction
Overview ................................................................................................................31 NetBackup administration interfaces ...............................................................34 NetBackup Administration Console setup .......................................................35 Running the Java-based Windows Display Console ...............................37 Administering remote servers ...................................................................38 Administering multiple versions of NetBackup servers ........................38 Earlier versions of the NetBackup-Java Administration Console on UNIX platforms ............................................................................38 Earlier versions of the NetBackup-Java Administration Console on Windows platforms ......................................................................38 Remote display-back from UNIX servers .........................................38 Remote display-back from Windows servers ..................................39 At the console of the server with an earlier version of NetBackup 39 Using the NetBackup Administration Console ...............................................40 NetBackup configuration wizards .............................................................41 Backup, Archive, and Restore ....................................................................42 Activity Monitor ...........................................................................................42 NetBackup Management .............................................................................42 Reports ...................................................................................................42 Policies ...................................................................................................43 Storage ...................................................................................................43 Catalog ...................................................................................................44 Host Properties .....................................................................................44 Media and Device Management .................................................................44 Device Monitor .....................................................................................45 Media ......................................................................................................45 Devices ...................................................................................................45 Credentials ............................................................................................45 Access Management ....................................................................................45 Standard and user toolbars ........................................................................46 Customizing the administration console .................................................46 Using LiveUpdate to distribute NetBackup updates ......................................46 How to configure NetBackup .............................................................................46

Chapter 2

Activity Monitor

Introduction to the Activity Monitor ............................................................... 50 Activity Monitor menu bar ......................................................................... 51 Status bar ...................................................................................................... 54 Setting Activity Monitor options .............................................................. 54 Jobs tab .................................................................................................................. 56 Parent jobs .................................................................................................... 56 Daemons tab ......................................................................................................... 58 More about daemons ................................................................................... 60 Other Symantec services ............................................................................ 61 Processes tab ........................................................................................................ 62 Monitoring NetBackup processes ............................................................. 66 Media mount errors ............................................................................................. 67 Queued media mount errors ...................................................................... 67 Canceled media mount errors .................................................................... 67 Managing the jobs database ............................................................................... 67 Retaining job information in the database .............................................. 68 Changing the default on a permanent basis .................................... 68 BPDBJOBS_OPTIONS environment variable ................................... 69 bpdbjobs debug log ...................................................................................... 70 Customizing bpdbjobs output .................................................................... 70

Chapter 3

Reports
Introduction to the Reports utility ................................................................... 72 Reports window ................................................................................................... 73 Shortcut menus ............................................................................................ 73 Reports settings ........................................................................................... 74 Date/Time range .................................................................................. 74 Client ...................................................................................................... 74 Disk pool ................................................................................................ 74 Disk type ................................................................................................ 74 Job ID ..................................................................................................... 74 Media ID ................................................................................................ 74 Media owner ......................................................................................... 75 Media server ......................................................................................... 75 Path ........................................................................................................ 75 Storage unit .......................................................................................... 75 Verbose listing ...................................................................................... 75 Volume ID ............................................................................................. 75 Volume pool .......................................................................................... 75 Run report ............................................................................................. 75 Stop report ............................................................................................ 75 NetBackup report types ...................................................................................... 76 Status of Backups report ........................................................................... 76

Client Backups report .................................................................................76 Problems report ...........................................................................................76 All Log Entries report ..................................................................................76 Images on Media report ..............................................................................76 Media Logs report ........................................................................................77 Tape Reports .................................................................................................77 Images on Tape report .......................................................................77 Tape Logs report .................................................................................77 Tape Contents report ..........................................................................77 Tape Summary report ........................................................................78 Tape Written report ............................................................................78 Tape Lists report .................................................................................78 Disk Reports ..................................................................................................79 Images on Disk report ........................................................................79 Disk Logs report ..................................................................................79 Disk Storage Unit Status report ........................................................79 Disk Pool Status report ......................................................................80 Using the Troubleshooter within reports ........................................................80

Chapter 4

Policies
Using the Policies utility .....................................................................................82 Tree and detail views ...................................................................................82 Policies menu bar .........................................................................................82 Configuring backup policies ...............................................................................82 Changing policies .................................................................................................84 Policy Attributes tab ............................................................................................87 Policy type .....................................................................................................88 Data classification ........................................................................................90 Policy storage ..............................................................................................91 Considerations before a storage destination is selected ................92 Policy volume pool .......................................................................................93 Volume pool override example ..........................................................94 Checkpoint restart for backup jobs ...........................................................95 Checkpoint frequency .........................................................................95 Checkpoint restart support ................................................................95 Checkpoint restart for restore jobs ...................................................97 Limit jobs per policy ....................................................................................97 Notes on the Limit jobs per policy attribute ....................................97 Job priority ....................................................................................................98 Media owner .................................................................................................99 Active. Go into effect at ...............................................................................99 Backup network drives ..............................................................................100 Setup example with UNC paths .......................................................100

Example using the Backup network drives attribute ...................101 Follow NFS ..................................................................................................101 Notes on Follow NFS ......................................................................... 102 Advantages of the Follow NFS attribute ........................................102 Disadvantages of the Follow NFS attribute ................................... 102 Cross mount points .................................................................................... 103 Notes on cross mount points ...........................................................103 Cases that can require separate policies ........................................104 How the Cross mount points attribute interacts with Follow NFS 104 Cross mount point examples ............................................................ 104 Compression ............................................................................................... 105 Advantages of the Compression attribute ..................................... 106 Disadvantages of the Compression attribute ................................ 106 How much compression can be expected? ..................................... 106 Encryption ..................................................................................................107 Collect disaster recovery information for IDR ......................................108 Collect disaster recovery information for Bare Metal Restore ........... 108 Collect true image restore information .................................................. 108 Collect true image restore information with move detection ............ 109 What happens during true image restores .................................... 110 Notes on true image restores and move detection ....................... 111 Allow multiple data streams .................................................................... 112 When to use multiple data streams ................................................ 113 Enable document restore .......................................................................... 115 Keyword phrase ......................................................................................... 116 Snapshot Client options ............................................................................ 116 Schedules tab ...................................................................................................... 117 Schedule Attributes tab .................................................................................... 118 Name ............................................................................................................ 118 Type of backup ........................................................................................... 119 Full backup .......................................................................................... 119 Cumulative incremental backup ..................................................... 120 Differential incremental backup ..................................................... 120 User backup ........................................................................................ 120 User archive ........................................................................................ 120 Application backup ............................................................................ 121 Automatic backup ..............................................................................121 Automatic incremental backup ....................................................... 121 Automatic cumulative incremental backup .................................. 121 Automatic differential incremental backup .................................. 121 Automatic full backup ....................................................................... 121 Automatic Vault ................................................................................. 122 Vault catalog backup ......................................................................... 122

More on incremental backups ..........................................................122 Determining files due for backup on Windows clients ................125 Determining files due for backup on UNIX clients .......................126 Synthetic backup ........................................................................................128 Calendar schedule type .............................................................................128 Retries allowed after runday ............................................................128 Frequency schedule type ..........................................................................128 Guidelines for setting backup frequency .......................................129 Backup frequency determines schedule priority ..........................130 Instant recovery .........................................................................................131 Snapshots and copy snapshots to a storage unit ..........................131 Snapshots only ...................................................................................131 Multiple copies ...........................................................................................131 Multiple copies and disk staging storage units .............................132 Multiple copies and storage lifecycle policies ...............................132 Multiple copies configuration ..........................................................133 Restoring from a specific backup copy ...........................................136 Override policy storage selection ............................................................137 Override policy volume pool ....................................................................137 Override media owner ...............................................................................137 Retention .....................................................................................................138 Guidelines for assigning retention periods ....................................138 Precautions for assigning retention periods .................................139 Changing retention periods ..............................................................140 Mixing retention levels on tape volumes .......................................140 Media multiplexing ....................................................................................141 Final destination storage unit ..................................................................141 Final destination volume pool .................................................................141 Start Window tab ...............................................................................................143 Exclude dates tab ...............................................................................................145 Calendar schedule tab .......................................................................................146 Schedule by specific dates ........................................................................146 Schedule by recurring week days ............................................................147 Schedule by recurring days of the month ..............................................148 How calendar scheduling interacts with daily windows ......................149 Automatic-backup schedule examples ...................................................151 Considerations for user schedules ..........................................................151 Planning user backup and archive schedules ................................151 Creating separate policies for user schedules ...............................152 Using a specific policy and user schedule ......................................152 Example policies ................................................................................................153 Policy planning guidelines for backups ..................................................154 Group the clients ................................................................................154

10

Gather information about clients .................................................... 154 Consider storage requirements ....................................................... 154 Consider backup schedules .............................................................. 155 Group by general attributes ............................................................. 156 Clients tab ........................................................................................................... 159 To install client software on trusting UNIX clients ............................. 160 To install software on secure UNIX clients ........................................... 162 To install software on Windows clients ................................................. 162 To configure a snapshot method ............................................................. 162 Backup Selections tab ....................................................................................... 163 Lists for different policy types ................................................................ 163 Backup selections list for standard policies .................................. 163 Backup selections list for database policies ................................... 165 Methods for faster backups ...................................................................... 166 Dividing file lists between multiple policies .................................. 166 Allowing multiple data streams ...................................................... 167 Verifying the backup selections list ........................................................ 167 Rules to indicate paths in the backup selections list ................................... 170 Path rules for Microsoft Windows clients ............................................. 170 File backups ........................................................................................ 170 Windows disk-image (Raw) backups ............................................... 171 Microsoft Windows registry backup ............................................... 172 Hard links to files (NTFS volumes or UNIX) .................................. 173 Pathname rules for UNIX clients ............................................................ 176 Notes on UNIX pathnames ............................................................... 176 Symbolic links to files or directories .............................................. 177 Hard links to directories ................................................................... 178 Hard links to files ...............................................................................178 UNIX raw partitions .......................................................................... 178 Backup and restore of extended attribute files and named data streams 180 Ramifications of backing up extended attributes or named data streams 182 Restoring extended attributes or named data streams ............... 182 Path rules for NetWare NonTarget clients ............................................ 183 Path rules for NetWare Target clients ................................................... 185 Path rules for clients running extension products .............................. 185 Backup selections list directives: General discussion .......................... 185 ALL_LOCAL_DRIVES directive ........................................................ 186 SYSTEM_STATE directive ................................................................ 186 Shadow copy components:\ directive ............................................. 187 Directives for multiple data streams .............................................. 188 Directives for specific policy types ................................................. 188

11

Backup selections list directives for multiple data streams ................189 NEW_STREAM directive and multiple data streams ...................189 ALL_LOCAL_DRIVES directive and multiple data streams .........192 UNSET, UNSET_ALL directives, and multiple data streams ......193 Excluding files from backups ...................................................................194 Files that are excluded from backups by default ..........................194 Excluding files from automatic backups ........................................195 Disaster Recovery tab ........................................................................................196 Path ..............................................................................................................197 Logon ...........................................................................................................197 Password .....................................................................................................197 Send in an email attachment ...................................................................197 Identifying critical policies ......................................................................197 Creating a Vault policy ......................................................................................199 Performing manual backups ............................................................................200 More about synthetic backups .........................................................................201 Policy considerations and synthetic backups ........................................201 Two types of synthetic backups ...............................................................203 Synthetic full backups .......................................................................203 Synthetic cumulative incremental backups ..................................204 Recommendations for synthetic backups ..............................................206 Notes on synthetic backups ......................................................................207 Displaying synthetic backups in the Activity Monitor ........................210 Logs produced during synthetic backups ...............................................210 Synthetic backups and directory and file attributes ............................211

Chapter 5

Storage units, unit groups, and lifecycle policies

Introduction to the Storage utility ..................................................................214 Using the Storage utility ...........................................................................215 Storage units .......................................................................................................216 Creating a storage unit ..............................................................................217 Changing storage unit settings ................................................................218 Deleting storage units ...............................................................................218 Media Manager storage unit considerations .........................................220 Disk storage unit considerations .............................................................222 Disk storage model .............................................................................222 Disk storage units in storage lifecycle policies .............................224 Maintaining available space on disk storage units .......................225 NDMP storage unit considerations .........................................................227 Storage unit settings .........................................................................................228 Absolute pathname to directory/volume ...............................................228 Density .........................................................................................................229 Disk pool ......................................................................................................229

12

Disk type ...................................................................................................... 229 Enable block sharing ................................................................................. 229 Enable multiplexing .................................................................................. 230 High water mark ........................................................................................ 230 Low water mark .......................................................................................... 230 Maximum concurrent write drives .........................................................231 Maximum concurrent jobs ....................................................................... 231 Using the Maximum concurrent jobs setting to control the storage unit and media server load ............................................................... 232 Maximum streams per drive .................................................................... 233 Media server ............................................................................................... 233 NDMP host ..................................................................................................235 On demand only ......................................................................................... 235 Only use the following media servers .................................................... 236 Properties button ....................................................................................... 236 Reduce fragment size ................................................................................ 238 Robot number ............................................................................................ 239 Robot type ..................................................................................................239 Staging relocation schedule (for basic disk staging only) ...................239 Storage device ............................................................................................ 239 Storage unit name ..................................................................................... 239 Storage unit type ....................................................................................... 240 Temporary staging area ........................................................................... 240 Transfer throttle ........................................................................................ 240 Use any available media server ............................................................... 240 Staging backups to initial storage, then final storage ................................. 242 Two staging methods ................................................................................ 242 Basic disk staging .............................................................................................. 244 Disk staging storage unit size and capacity considerations ............... 245 Finding the potential free space on a BasicDisk disk staging storage unit 246 Creating a basic disk staging storage unit ............................................. 247 Disk Staging Schedule dialog ................................................................... 249 Name .................................................................................................... 249 Priority of relocation jobs started from this schedule ................. 250 Final destination storage unit ..........................................................250 Final destination volume pool .........................................................250 Final destination media owner ........................................................ 250 Use alternate read server ................................................................. 251 Basic disk staging limitations .................................................................. 251 Initiating a relocation schedule manually ............................................. 251 Storage Lifecycle Policies ................................................................................. 253 Storage lifecycle overview ........................................................................ 253

13

To create a storage lifecycle policy .........................................................254 Adding storage destinations to a lifecycle policy .................................255 Writing multiple copies using a lifecycle .......................................256 Storage lifecycle policy name ...........................................................258 Duplication job priority .....................................................................258 Storage destinations ..........................................................................258 Use storage destination for: backup or duplication .....................259 Storage unit .........................................................................................259 Volume pool ........................................................................................259 Media owner ........................................................................................259 Retention type: Fixed .........................................................................260 Retention type: Staged capacity managed .....................................260 Retention type: Expire after duplication ........................................262 Alternate read server .........................................................................262 Data classification ......................................................................................262 How backup data is associated with a data classification ...........263 Creating or changing a data classification .....................................263 Optional duplication job configuration ..................................................264 MIN_KB_SIZE_PER_DUPLICATION_JOB .......................................264 MAX_KB_SIZE_PER_DUPLICATION_JOB ......................................264 MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB .......264 LIFECYCLE_PARAMETERS file example ........................................265 Using nbstlutil to administrate lifecycle operations ............................265 When to use nbstlutil ........................................................................265 Storage unit groups ...........................................................................................267 Storage unit selection criteria within a group ......................................267 Prioritized ...........................................................................................267 Failover ................................................................................................267 Round robin ........................................................................................267 Load balance .......................................................................................267 Exception to the storage unit selection criteria ............................270 Disk spanning within storage unit groups .............................................271 Creating a storage unit group ..................................................................271 Deleting a storage unit group ..................................................................273

Chapter 6

NetBackup Catalog
What is a NetBackup catalog? ..........................................................................276 Parts of the catalog ....................................................................................276 Image database ...........................................................................................277 Image files ...........................................................................................278 Image .f files ........................................................................................278 NetBackup relational database ................................................................280 Enterprise Media Manager (EMM) database ..................................281

14

Catalog protection ............................................................................................. 282 Catalog backups ......................................................................................... 282 Online, hot catalog backup method ................................................ 283 Running online, hot catalog backups concurrently with other backups 294 Notes on catalog policy schedules ................................................... 294 Offline, cold catalog backup method .............................................. 296 Recovering the catalog ..................................................................................... 317 Disaster recovery emails and the disaster recovery file .............................. 317 Archiving the catalog ........................................................................................ 318 Catalog archiving process ........................................................................ 318 Creating a catalog archiving policy ........................................................ 319 Policy name ......................................................................................... 319 Deactivate policy ................................................................................ 319 Type of backup ................................................................................... 320 Retention level setting ...................................................................... 320 Catalog archiving commands ...........................................................321 Recommendations for using catalog archiving ............................ 322 Using Vault with the catalog archiving feature ............................ 323 Browsing offline catalog archive ..................................................... 323 Extracting images from the catalog archives ................................ 323 Using the Catalog utility ................................................................................... 324 Searching for backup images ................................................................... 324 Notes on searching for an image ............................................................. 326 Messages pane ............................................................................................ 326 Verifying backup images .......................................................................... 327 Viewing job results .................................................................................... 327 Promoting a copy to a primary copy ....................................................... 328 Duplicating backup images ...................................................................... 330 Notes on multiplexed duplication ................................................... 330 Procedure for duplicating backups ................................................. 331 Jobs displayed while making multiple copies ........................................334 Importing NetBackup or Backup Exec images ......................................336 Importing expired images ................................................................ 341 Importing images from Backup Exec media .................................. 342 Host properties for Backup Exec ..................................................... 342 Considerations concerning importing Backup Exec media ......... 342 Differences between importing, browsing, and restoring Backup Exec and NetBackup images .............................................................. 343 Expiring backup images ............................................................................ 346 Catalog maintenance and performance optimization ................................. 347 Determining catalog space requirements .............................................. 347 File size considerations ..................................................................... 348

15

Backing up catalogs manually .................................................................350 How do I know if a catalog backup succeeded? .............................351 Strategies to ensure successful catalog backups ..................................352 About the binary catalog format .............................................................353 Catalog conversion utility .................................................................354 Binary catalog file limitations ..........................................................354 Moving the image catalog .........................................................................354 Indexing the catalog for faster access to backups ................................355 Compressing and uncompressing the image catalog ...........................355 Uncompressing the image catalog ..................................................357

Chapter 7

Host properties
Introduction to host properties .......................................................................360 Viewing host properties ............................................................................360 Changing host properties .................................................................................361 Interpreting the initial settings ...............................................................361 Selecting multiple hosts ............................................................................363 Required permissions ........................................................................................364 Master server, media server, and client host properties .............................364 Access Control properties .........................................................................364 Symantec Product Authentication and Authorization ................365 Symantec Product Authentication and Authorization tab within the Access Control properties ..............................................................................365 Networks list .......................................................................................366 Add button ..........................................................................................366 Remove button ...................................................................................368 Authentication Domain tab within the Access Control properties ....368 Add button ..........................................................................................369 Remove button ...................................................................................371 Authorization Service tab within the Access Control properties .......371 Host name ...........................................................................................371 Customize the port number of the authorization service ...........372 Authorization properties ..........................................................................373 User ......................................................................................................373 Host ......................................................................................................374 Domain\Group ....................................................................................374 Group/Domain type ...........................................................................374 User must be an OS administrator ..................................................374 Backup Exec Tape Reader properties ......................................................375 Add button ..........................................................................................375 GRFS advertised name ......................................................................375 Actual client name .............................................................................376 Actual path ..........................................................................................376

16

Change button .................................................................................... 376 Remove button ................................................................................... 376 Bandwidth properties ................................................................................ 377 How bandwidth limiting works ....................................................... 377 Bandwidth throttle setting for the range of IP addresses ........... 378 From IP address ................................................................................. 378 To IP address ...................................................................................... 378 Bandwidth ........................................................................................... 378 Bandwidth throttle settings list ...................................................... 378 Add button .......................................................................................... 378 Remove button ................................................................................... 379 Notes on bandwidth limits ............................................................... 379 Busy File Settings properties ................................................................... 380 For the Busy File Settings to take effect ......................................... 380 Working directory .............................................................................381 Operators email address .................................................................. 381 Process busy files ...............................................................................381 File action file list ..............................................................................381 Add button .......................................................................................... 381 Add to all button ................................................................................ 381 Remove button ................................................................................... 382 Busy file action ................................................................................... 382 Retry count ......................................................................................... 382 Clean-up properties ................................................................................... 383 Keep logs ............................................................................................. 383 Keep vault logs ................................................................................... 383 Image cleanup .................................................................................... 384 Catalog cleanup wait time ................................................................ 384 Keep true image restoration (TIR) information ............................ 384 Move restore job from incomplete state to done state ................ 385 Move backup job from incomplete state to done state ................ 385 Client Attributes properties ..................................................................... 386 Allow client browse ........................................................................... 386 Allow client restore ........................................................................... 386 Clients list ........................................................................................... 387 General tab ..................................................................................................387 Maximum data streams .................................................................... 387 Browse and restore ability ................................................................ 388 Free browse ......................................................................................... 388 Connect Options tab .................................................................................. 388 BPCD connect back ............................................................................ 389 Ports ..................................................................................................... 389 Daemon connection port .................................................................. 390

17

Windows Open File Backup tab ...............................................................391 Add and remove buttons ...................................................................391 Enable Windows Open File Backups for this client ......................392 Use Veritas Volume Snapshot Provider (VSP) ..............................392 Use Microsoft Volume Shadow Copy Service (VSS) .....................392 Individual drive snapshot .................................................................393 Global drive snapshot ........................................................................393 Abort backup on error .......................................................................394 Disable snapshot and continue ........................................................394 Client Name properties .............................................................................395 Client name .........................................................................................395 Client Settings (NetWare) properties ......................................................396 Back up migrated files .......................................................................396 Uncompress files before backing up ...............................................396 Keep status of user-directed backups, archives, and restores ....396 Client Settings (UNIX) properties ............................................................397 Locked file action ...............................................................................397 Keep status of user-directed backups, archives, and restores ....397 Reset file access time to the value before backup .........................398 Megabytes of memory to use for file compression .......................398 Use VxFS file change log for incremental backups ......................398 Default cache device path for snapshots ........................................400 Do not compress files ending with ..................................................401 Add button ..........................................................................................401 Add to all button .................................................................................401 Remove button ...................................................................................401 Client Settings (Windows) properties .....................................................402 General level logging .........................................................................402 TCP level logging ................................................................................402 Wait time before clearing archive bit .............................................403 Use change journal in incrementals ...............................................403 Incrementals based on timestamp ..................................................405 Incrementals based on archive bit ..................................................405 Time overlap .......................................................................................405 Communications buffer size ............................................................406 User directed timeouts ......................................................................406 Maximum error messages for server ..............................................406 Keep status of user-directed backups, archives, and restores ....406 Perform default search for restore ..................................................406 Data Classification properties ..................................................................407 Rank .....................................................................................................407 Name ....................................................................................................408 Description ..........................................................................................408

18

Classification ID ................................................................................. 408 Encryption properties ...............................................................................409 Encryption permissions .................................................................... 409 Enable encryption ..............................................................................410 Enable standard encryption ............................................................. 410 Client cipher ....................................................................................... 410 Use legacy DES encryption .............................................................. 410 Encryption strength .......................................................................... 410 Encryption libraries .......................................................................... 411 Encryption key file ............................................................................ 411 Exchange properties .................................................................................. 412 Snapshot verification I/O throttle .................................................. 412 Backup option for log files during full backups ............................ 413 Mailbox for message level backup and restore ............................. 413 Enable single instance backup for message attachments ........... 413 Exclude Lists properties ........................................................................... 414 Use case sensitive exclude list .........................................................414 Exclude list .......................................................................................... 414 Exceptions to the exclude list ..........................................................414 Add buttons ........................................................................................ 414 Add to all buttons ...............................................................................415 Remove buttons ................................................................................. 416 Shared fields in exclude lists ................................................................... 416 Policy ...................................................................................................416 Schedule .............................................................................................. 416 Files/Directories ................................................................................. 416 Exclude lists for specific policies or schedules ..................................... 416 Syntax rules for exclude lists ................................................................... 418 Traversing excluded directories .............................................................. 419 Fibre Transport properties ....................................................................... 422 Preferred ............................................................................................. 422 Always .................................................................................................423 Never .................................................................................................... 423 Maximum concurrent FT connections ........................................... 423 Use defaults from the master server configuration ..................... 423 Firewall properties .................................................................................... 424 Default connect options .................................................................... 424 Hosts list .............................................................................................. 426 Attributes for selected hosts ............................................................ 427 Example setup for using the vnetd port ......................................... 429 General Server properties ........................................................................ 431 Delay on multiplexed restores .........................................................431 Check the capacity of disk storage units ........................................431

19

Must use local drive ...........................................................................432 Use direct access recovery for NDMP restores .............................432 Document-level restore options ......................................................432 Media host override ...........................................................................433 Add button ..........................................................................................433 Add to all button .................................................................................433 Change button ....................................................................................433 Remove button ...................................................................................434 Global Attributes properties ....................................................................435 Job retry delay ....................................................................................435 Schedule backup attempts ................................................................435 Policy update interval .......................................................................436 Priority of restore jobs ......................................................................436 Maximum jobs per client ..................................................................436 Maximum backup copies ...................................................................437 Compress catalog interval ................................................................438 Maximum vault jobs ..........................................................................438 Administrator email address ............................................................438 Setting up email notifications ..................................................................438 Indicating email notification in the NetBackup host properties 439 Email contents ....................................................................................440 Logging properties .....................................................................................441 Types of logging .................................................................................441 Enable robust logging ........................................................................442 Global logging level ...........................................................................443 Process specific overrides .................................................................443 Debug logging levels for NetBackup services ................................444 Lotus Notes properties ..............................................................................445 Path ......................................................................................................445 INI file ..................................................................................................445 Media properties ........................................................................................446 Allow media overwrite ......................................................................446 Enable SCSI reserve ...........................................................................447 Allow multiple retentions per media ..............................................449 Allow backups to span tape media ..................................................449 Allow backups to span disk ...............................................................450 Enable standalone drive extension .................................................450 Enable job logging ..............................................................................450 Enable unrestricted media sharing for all media servers ............450 Media ID prefix (non-robotic) ...........................................................451 Media unmount delay ........................................................................451 Media request delay ...........................................................................451 NDMP Global Credentials properties ......................................................452

20

User name ........................................................................................... 453 Password and confirm password ..................................................... 453 NetWare Client properties ....................................................................... 453 Network properties .................................................................................... 454 NetBackup client service port (BPCD) ............................................ 454 NetBackup request service port (BPRD) ......................................... 454 Announce DHCP interval .................................................................. 455 Open File Backup (NetWare client) properties ..................................... 455 Enable open file backup during backups ........................................455 Port Ranges properties .............................................................................456 Use random port assignments .........................................................457 Client port window ............................................................................ 457 Client reserved port window ............................................................ 457 Server port window ........................................................................... 458 Server reserved port window ...........................................................458 Restore Failover properties ...................................................................... 459 Alternate restore failover machines list ........................................460 Add button .......................................................................................... 460 Change button .................................................................................... 461 Remove button ................................................................................... 461 Media server ....................................................................................... 461 Failover restore servers .................................................................... 461 Retention Periods properties ................................................................... 462 Value .................................................................................................... 462 Units .................................................................................................... 462 Retention periods list ........................................................................ 462 Schedules list ...................................................................................... 463 Impact report button ......................................................................... 463 Note on redefining retention periods ............................................. 464 Servers properties ..................................................................................... 465 Master server ...................................................................................... 465 Additional servers ..............................................................................465 Media servers ..................................................................................... 466 Restricting administrative privileges of media servers ............... 466 Multiple masters that share one Enterprise Media Manager host 467 SharedDisk properties ..............................................................................470 SharedDisk mount points directory ................................................ 470 SharePoint 2003 properties ..................................................................... 471 User ID .................................................................................................471 Password ............................................................................................. 471 Consistency check before backup .................................................... 471 Continue with backup if consistency check fails .......................... 472 SharePoint Hosts properties .................................................................... 472

21

Symantec Products properties .................................................................473 Timeouts properties ..................................................................................474 Client connect timeout ......................................................................474 Backup start notify timeout .............................................................474 File browse timeout ...........................................................................475 Use OS dependent timeouts .............................................................475 Media mount timeout ........................................................................475 Client read timeout ............................................................................475 Backup end notify timeout ...............................................................476 Media server connect timeout .........................................................476 Universal Settings properties ..................................................................477 Restore retries ....................................................................................477 Browse timeframe for restores ........................................................478 Last full backup ..................................................................................478 Use specified network interface ......................................................478 Use preferred group for enhanced authorization .........................479 Allow server file writes .....................................................................480 Accept connections on non reserved ports ....................................480 Enable performance data collection (Windows server only) .......481 Client sends mail ................................................................................481 Server sends mail ...............................................................................481 Client administrators email ............................................................481 UNIX Client properties ..............................................................................482 UNIX Server properties .............................................................................483 NFS access timeout ............................................................................483 VMWare Proxy Servers properties .........................................................484 VSP (Volume Snapshot Provider) properties ........................................485 VSP overview ......................................................................................485 Logging VSP messages ......................................................................487 Cache file volume list ........................................................................487 VSP volume exclude list ....................................................................488 Customize cache size .........................................................................490 Cache size ............................................................................................490 Maximum cache size ..........................................................................490 Busy file wait .......................................................................................491 Busy file timeout ................................................................................492 Using VSP with databases ................................................................492 Windows Client properties .......................................................................494

Chapter 8

Device Monitor
Changing the operating mode of a drive ........................................................495 Resetting a drive ................................................................................................496 Managing drive paths ........................................................................................497

22

Managing pending requests and actions ....................................................... 497 Pending requests for storage units .........................................................498 Resolving a pending request .................................................................... 499 Resolving a pending action ...................................................................... 500 Resubmitting a request .............................................................................500 Denying a request ...................................................................................... 501 Freezing media or downing drives .................................................................. 501 Cleaning drives ...................................................................................................502 Adding or changing a drive comment ............................................................ 504 Viewing drive details ......................................................................................... 504

Chapter 9

Media
Volume operations ............................................................................................ 507 Adding volumes ......................................................................................... 508 Adding volumes overview ................................................................ 508 About labeling NetBackup volumes ................................................ 510 Adding volumes by using the Volume Configuration Wizard .... 511 Adding volumes using a robot inventory update .......................... 511 Adding volumes using the Actions menu ......................................512 Volumes properties ........................................................................... 513 Changing volume properties .................................................................... 517 Change Volumes properties ............................................................. 518 Changing the volume pool of a volume .................................................. 519 Changing the volume group of a volume ............................................... 519 Changing the owner of a volume ............................................................. 520 Freezing and unfreezing media ............................................................... 520 Suspending and unsuspending media .................................................... 521 Labeling media ........................................................................................... 521 Label properties ................................................................................. 523 Rescanning and updating barcodes ........................................................ 523 When to rescan and update .............................................................. 523 When not to rescan and update ....................................................... 523 Rescanning/updating barcodes ....................................................... 524 Moving volumes ......................................................................................... 524 Move examples ................................................................................... 525 Moving volumes using the robot inventory update option ......... 525 Moving volumes using the Actions menu ......................................525 Move Volumes properties ................................................................. 526 Erasing media ............................................................................................. 528 Injecting and ejecting volumes ................................................................ 529 Injecting volumes ..............................................................................530 Ejecting volumes ................................................................................ 530 Media ejection timeout periods ....................................................... 532

23

Deleting volumes .......................................................................................532 Deassigning volumes .................................................................................533 Deassigning NetBackup volumes .....................................................534 Deassigning Veritas Storage Migrator volumes ............................535 Exchanging volumes ..................................................................................535 Exchanging a volume and using a new media ID ..........................535 Exchanging a volume and using the old media ID ........................536 Recycling volumes .....................................................................................537 Recycling volumes using the existing media ID ............................537 Recycling volumes using a new media ID ......................................537 Volume pool operations ....................................................................................538 Adding a new volume pool ........................................................................539 Changing the properties of a volume pool .............................................539 Volume pool properties .............................................................................540 Catalog backup pool ...........................................................................540 Description ..........................................................................................540 Maximum number of partially full media ......................................540 Pool name ............................................................................................541 Scratch pool ........................................................................................541 Deleting a volume pool ..............................................................................542 Volume group operations .................................................................................542 Moving a volume group ............................................................................542 Move volume group properties ........................................................543 Deleting a volume group ...........................................................................544 Robot inventory operations .............................................................................544 When to inventory a robot .......................................................................545 Inventory a robot .......................................................................................547 Robot Inventory dialog box ....................................................................548 Advanced options ...............................................................................548 Compare contents with volume configuration ..............................549 Device host ..........................................................................................549 Empty media access port prior to update .......................................550 Preview volume configuration changes .........................................550 Robot ....................................................................................................551 Show contents ....................................................................................551 Update volume configuration ..........................................................553 Advanced Robot Inventory Options dialog ............................................555 Media Settings tab ...................................................................................555 Label optical media (Local host only) ..............................................556 Media type ...........................................................................................556 Media that have been removed from the robot .............................559 Media that have been moved into or within the robot .................559 Use barcode rules ...............................................................................560

24

Use the following Media ID prefix .................................................. 560 Volume pool ........................................................................................ 561 Barcode Rules tab ...................................................................................... 562 Barcode tag ......................................................................................... 562 Description .......................................................................................... 563 Maximum mounts ..............................................................................563 Media type ........................................................................................... 563 Volume pool ........................................................................................ 565 Media ID Generation tab ......................................................................... 565 Barcode length ................................................................................... 566 Media ID generation rule .................................................................. 566 Robot number ..................................................................................... 566 Media Type Mappings tab ...................................................................... 566 Adding mapping entries ................................................................... 567 Default and allowable media types ................................................. 568 Using the physical inventory utility ....................................................... 572 Features of vmphyinv ....................................................................... 573 Requirements and restrictions for vmphyinv ............................... 573 When to use vmphyinv ..................................................................... 573 How vmphyinv performs a physical inventory ............................. 574 Obtains a list of drives to mount the media ................................... 574 Obtains a list of media to be mounted ............................................ 574 Mounts media and reads the tape header ......................................576 Updates the EMM database .............................................................. 577 Volume configuration update examples ................................................ 579 Example 1: Removing a volume from a robot ................................ 580 Example 2: Adding existing stand-alone volumes to a robot ...... 581 Example 3: Moving existing volumes within a robot ...................583 Example 4: Adding new volumes to a robot ................................... 584 Example 5: Adding cleaning tapes to a robot ................................ 586 Example 6: Moving existing volumes between robots ................. 587 Example 7: Adding existing volumes when barcodes are not used 587 Using WORM media .......................................................................................... 589 Supported drives ........................................................................................ 590 Managing your WORM media in NetBackup ......................................... 590 Using WORM volume pools to manage WORM media ................ 590 Using unique drive and media types to manage WORM media . 591 WORM tape limitations ............................................................................ 592

Chapter 10

Devices
Device configuration prerequisites ................................................................ 593 The device mapping file .................................................................................... 594 Configuring robots and tape drives ................................................................ 595

25

Using the Device Configuration Wizard .................................................595 Operating system changes ................................................................596 Possible EMM server host conflict ..................................................596 Devices that are partially-configured .............................................596 Starting the Device Configuration Wizard ....................................597 Adding a robot ............................................................................................597 Robot properties .................................................................................598 Robot control configuration overview ............................................602 Adding or changing a drive ......................................................................604 Adding a shared drive .......................................................................605 Configuring SCSI reserve on a drive path ......................................605 Drive properties .................................................................................607 Configuring drive name rules ..........................................................611 Robot drive number for API robots .................................................613 No rewind device ................................................................................614 Configuring server groups for media sharing ...............................................615 Server group properties ............................................................................617 Server group name .............................................................................617 Server group type ...............................................................................617 State .....................................................................................................618 Description ..........................................................................................618 Servers in group .................................................................................618 Servers not in group ..........................................................................618 Configuring and managing disk pools ............................................................618 Configuring SAN clients and Fibre Transport ..............................................619 Managing your device configuration ..............................................................619 When to perform device configuration changes ...................................619 Using the Device Configuration Wizard for changes ...........................620 Changing a robot configuration ...............................................................620 Changing the configuration of a drive ....................................................620 Changing a drive to a shared drive ..........................................................621 Deleting robots ...........................................................................................621 Deleting drives ...........................................................................................621 Performing device diagnostics .................................................................622 Running a drive diagnostic test .......................................................622 Running a robot diagnostic test .......................................................622 Printing your device configuration .........................................................623 Stopping and restarting the device daemon ..................................................624 External access to NetBackup controlled devices .................................624 Activating and deactivating media servers ...................................................625 Accessing media and devices on other hosts .................................................625 Example SERVER entries ..........................................................................626 The Enterprise Media Manager server ...........................................................626

26

Managing the EMM server ....................................................................... 626 EMM server requirements ........................................................................ 627

Chapter 11 Chapter 12

Credentials Management topics

NetBackup naming conventions ..................................................................... 631 Using wildcards in NetBackup ......................................................................... 632 To power down and reboot NetBackup servers ............................................ 633 Displaying active processes with bpps ................................................... 634 Displaying robotic processes with vmps ................................................ 635 Administering NetBackup licenses ................................................................. 635 Using the NetBackup license utility to administer licenses ....................... 638 To administer a remote master server ...........................................................639 To add a NetBackup server to a server list ............................................ 639 To choose a remote server to administer ............................................... 644 Administer a master server by using a NetBackup client ...................646 Using the Remote Administration Console ........................................... 647 If you cannot access a remote server ...................................................... 648 To administer devices on other servers .........................................................649 Using the NetBackup-Java Windows display console .................................. 651 To authorize NetBackup-Java users on Windows ................................. 651 To restrict access on Windows ................................................................ 651 Configuring the NetBackup-Java administration console .......................... 652 NetBackup-Java administration console architectural overview ...... 652 Authorizing NetBackup-Java users .........................................................654 Authorization file characteristics ...........................................................656 To configure nonroot usage ..................................................................... 658 Authorizing nonroot users for specific applications ...................658 Capabilities authorization for jbpSA .............................................. 659 Runtime configuration options ............................................................... 660 BPJAVA_PORT, VNETD_PORT ........................................................ 660 FIREWALL_IN .................................................................................... 660 FORCE_IPADDR_LOOKUP ............................................................... 662 INITIAL_MEMORY, MAX_MEMORY .............................................. 663 MEM_USE_WARNING ...................................................................... 664 NBJAVA_CLIENT_PORT_WINDOW ................................................ 664 NBJAVA_CONNECT_OPTION ..........................................................665 NBJAVA_CORBA_DEFAULT_TIMEOUT ........................................665 NBJAVA_CORBA_LONG_TIMEOUT ................................................ 665 USE_NBJAUTH_WITH_ENHAUTH ................................................ 666 Configuration options relevant to jnbSA and jbpSA ............................ 666 To log the command lines that the NetBackup interfaces use ... 666

27

To customize jnbSA and jbpSA with bp.conf entries ...................666 NetBackup-java performance improvement hints .......................................667 What it means to be running the java console locally on a UNIX platform 667 What it means to be running the console locally on a Windows platform 668 How do I run a console locally and administer a remote server? .......668 How do I enhance console performance? ...............................................668 Is the performance better when run locally or using remote display back? 670 Managing client restores ..................................................................................672 Server-directed restores ...........................................................................672 Client-redirected restores .........................................................................673 How NetBackup enforces restore restrictions ...............................673 To allow all clients to perform redirected restores ......................674 To allow a single client to perform redirected restores ...............675 To allow redirected restores of a clients files ...............................675 Redirected restore examples ............................................................676 Restoring files and access control lists ..................................................681 To restore the files that possess ACLs ............................................681 To restore files without restoring ACLs .........................................681 To improve search times by creating an image list ..............................682 Set original atime for files during restores ............................................682 Checkpoint restart for restore jobs .........................................................683 To suspend and resume a restore job ..............................................683 Limitations to checkpoint restart for restore jobs ........................683 Restoring system state ..............................................................................684 Important notes on system state .............................................................684 Goodies scripts ...................................................................................................687 Alternate server restores ..................................................................................687 Supported configurations .........................................................................687 Methods for performing alternate server restores ...............................689 Method 1: Modifying the NetBackup catalogs ...............................690 Method 2: Overriding the original server .......................................691 Method 3: Automatic failover to alternate server ........................692 Notes on alternate server restores ..................................................693 Using NetBackup with Storage Migrator .......................................................694 Set a large enough media mount timeout ..............................................694 Do not use the RESTORE_ORIGINAL_ATIME file ................................694 Do not use the following client bp.conf file settings ............................695

Appendix A

NetBackup relational database

Installation overview .........................................................................................698

28

NetBackup master server installation .................................................... 699 Relocating the NetBackup database ................................................ 699 server.conf .......................................................................................... 699 databases.conf .................................................................................... 700 vxdbms_env.csh, vxdbms_env.sh .................................................... 701 /bin ....................................................................................................... 701 /charsets .............................................................................................. 702 /data ..................................................................................................... 702 /lib ........................................................................................................ 703 /log ....................................................................................................... 703 /res ....................................................................................................... 703 /scripts .................................................................................................703 /staging ................................................................................................ 703 /tix ........................................................................................................ 703 NetBackup configuration entry ............................................................... 704 Sybase ASA server management ............................................................. 705 Clusters ........................................................................................................ 706 Post-installation tasks ...................................................................................... 707 To change the database password ...........................................................707 Moving NBDB database files after installation ..................................... 708 To add a mirrored transaction log ..........................................................709 Creating the NBDB database .................................................................... 710 Additional create_nbdb options ...................................................... 711 Backup and recovery procedures .................................................................... 712 Using the online, hot catalog backup method .......................................713 Using the offline, cold catalog backup method ............................. 714 Transaction log management .................................................................. 714 Catalog recovery ........................................................................................ 715 Additional command lines for backup and recovery of the relational databases ............................................................................................. 716 nbdb_backup ....................................................................................... 716 nbdb_restore ....................................................................................... 716 Database unloading tool ................................................................................... 716 Terminating database connections .........................................................717 Moving the NetBackup database from one host to another ....................... 719 Cluster considerations with the EMM server ........................................721

Appendix B

AdvancedDisk storage option

Licensing AdvancedDisk ................................................................................... 724 Creating an AdvancedDisk storage server ..................................................... 724 Creating an AdvancedDisk disk pool .............................................................. 726 Creating a storage unit ..................................................................................... 727 Usage recommendations .......................................................................... 730

29

Multiple storage units .......................................................................730 Maximum concurrent job setting ....................................................731 Managing disk pools ..........................................................................................731 Changing disk pool properties .................................................................731 Disk pool properties ...........................................................................732 Adding volumes to an AdvancedDisk disk pool ....................................733 Changing disk pool or volume state ........................................................734 Merging disk pools .....................................................................................735 Deleting a disk pool ...................................................................................735 Obtaining disk pool and volume status ..................................................736 Managing storage servers ................................................................................737 Viewing storage servers ............................................................................737 Deleting a storage server ..........................................................................738 Obtaining storage server status ...............................................................738 Monitoring storage capacity and usage .........................................................738 Troubleshooting AdvancedDisk ......................................................................739 Unable to access storage ...........................................................................739 Volume state changes to DOWN when volume is unmounted ...........740 Disk failure ..................................................................................................740

Appendix C

NearStore storage units

Required software, hardware, and licenses ...................................................742 Upgrade considerations ....................................................................................744 NearStore and SnapVault considerations ..............................................744 NearStore disk storage unit advantages ........................................................745 Restrictions in the current release ..................................................................746 NearStore configuration ...................................................................................747 NearStore authentication .........................................................................747 NearStore disk storage unit properties ..........................................................750 Storage unit type ........................................................................................750 On demand only .........................................................................................750 Disk type ......................................................................................................751 NearStore server ........................................................................................751 Absolute pathname to volume .................................................................751 Properties button .......................................................................................751 Enable block sharing and and file system export .................................751 Enable block sharing .........................................................................751 Enable file system export ..................................................................752 Image mode .........................................................................................752 Temporary staging area ............................................................................752 Reduce fragment size ................................................................................753 Viewing the backup image ................................................................................753 Disk consumption ..............................................................................................753

30

File system full conditions ....................................................................... 753 End of media detection on disk staging storage units ......................... 753 Using the NearStore disk storage unit for more than one purpose ... 754 Disaster recovery using volume SnapMirror on NearStore disk storage units 755 Overview of disaster recovery scenarios ............................................... 755 Initial configuration .................................................................................. 756 General failover configuration ................................................................ 757 Failover examples ...................................................................................... 758 Example 1 ............................................................................................ 758 Example 2 ............................................................................................ 761 Troubleshooting .................................................................................................764 Licensing and permissions ....................................................................... 764 Regarding disk full conditions ................................................................. 764 Regarding the file system export mode ................................................. 765

Appendix D

Exporting PureDisk data to NetBackup

Required software and licenses ............................................................... 767 In the PureDisk environment ..........................................................767 In the NetBackup environment ....................................................... 768 Requirements to restore ................................................................... 768 Exporting PureDisk data .......................................................................... 768 Create a PureDisk export policy ...................................................... 768 Create a NetBackup DataStore type policy .................................... 769 Restoring PureDisk data ........................................................................... 770 Logging information ................................................................................. 772

Index

773

Chapter

Introduction
The NetBackup Administrators Guide, Volume I describes the core NetBackup product. This manual describes NetBackup configuration optionswhat they are and how each can be used to benefit the backup needs of your environment. This manual is organized to reflect the arrangement of the NetBackup Administration Console. This chapter provides an introduction to NetBackup software, the interfaces available, and the distributed architecture of NetBackup. This chapter contains the following sections:

Overview on page 31 NetBackup administration interfaces on page 34 NetBackup Administration Console setup on page 35 Using the NetBackup Administration Console on page 40 How to configure NetBackup on page 46

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

32 Introduction Overview

The NetBackup administrator can allow users to backup, 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:

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.) NetBackup storage domain example
NetBackup master server

Figure 1-1

Media servers

SAN

Media Manager tape storage unit

BasicDisk storage unit

OpenStorage or SharedDisk disk pool

NetBackup clients

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

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

Introduction Overview

33

performance by distributing the network load. Media servers can also be referred to using the following terms:

device hosts (when tape devices are present), storage servers (when performing I/O directly to disk), or data movers (when sending data 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.

34 Introduction NetBackup administration interfaces

NetBackup administration interfaces

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

NetBackup Administration Console Start a Java-based, graphical-user interface by running the jnbSA command. The administration console is the recommended interface and is the interface referred to by most procedures and examples in this manual. For more information, see NetBackup Administration Console setup on page 35 and NetBackup-Java administration console architectural overview on page 652. Character-based, menu interfaces NetBackup management: Start a character-based, menu interface for NetBackup management by running the bpadm command. You can use the bpadm interface from any terminal (or terminal emulation window) that has a termcap or a terminfo definition. Media management: Start a character-based, menu interface for media management by running the vmadm command. You can use the vmadm interface from any terminal (or terminal emulation window) that has a termcap or a terminfo definition. Device management. Start a character-based, menu interface for device management by running the tpconfig command. You can use the tpconfig interface from any terminal (or terminal emulation window) that has a termcap or a terminfo definition. (For more information about these menu interfaces, see Menu user interfaces in the NetBackup Administrators Guide, Volume II.) Command line You can enter NetBackup commands at the system prompt or use them in scripts. For complete information on all NetBackup commands, see NetBackup Commands for UNIX and Linux. To view the commands online, use the UNIX man command.

All NetBackup administrator programs and commands require root-user privileges by default. If it is necessary to have nonroot administrators, see To configure nonroot usage on page 658. The console can be run on a Java-capable UNIX platform, then displayed back to a Windows system by using third-party X terminal emulation software.

Introduction NetBackup Administration Console setup

35

NetBackup Administration Console setup

NetBackup provides two Java-based administration consoles through which the administrator can manage NetBackup. The consoles can be run on either of the following systems:

Directly on a supported NetBackup-Java capable UNIX system by running /usr/openv/java/jnbSA & The jnbSA command is described in NetBackup Commands for UNIX and Linux. On a supported Windows system that has the NetBackup-Java Windows Display Console installed. The Windows Display Console is not automatically installed on Windows systems. Installation is available on the main NetBackup for Windows installation screen.

The startup procedures are explained in the following sections. For configuration information, see Configuring the NetBackup-Java administration console on page 652. Always set the window manager so a window becomes active only when clicked. The NetBackup-Java interfaces do not run properly with auto-focus enabled. Auto-focus causes a window to become active when the pointer moves over the window. The following are general instructions for correctly setting up the focus on a CDE (Common Desktop Environment) window manager. CDE is the preferred window manager for NetBackup-Java applications. To prepare a CDE (Common desktop environment) for NetBackup-Java interfaces 1 2 3 4 5 On the front panel in the CDE window, click the Style Manager control icon. The Style Manager toolbar appears. On the Style Manager toolbar, click the Window control icon. The Style Manager-Window dialog appears. In the Style Manager-Window dialog, click the Click In Window To Make Active button. Click OK. Click OK when asked to Restart the Workspace Manager.

To start the NetBackup-Java Administration Console on a NetBackup-Java capable UNIX system 1 Log in as root on the NetBackup client or server where you want to start the NetBackup Administration Console. The client or server must be NetBackup-Java capable.

36 Introduction NetBackup Administration Console setup

Start the console by entering:

/usr/openv/java/jnbSA &

The login screen appears. 3 Type the name of the UNIX master server host where you initially want to manage NetBackup.

Note: The NetBackup host that is specified on the login dialog and the machine where you start the NetBackup-Java console must run the same NetBackup version.

Specified host must be running same NetBackup version as machine where the console is started

Specify your user name and password, then click Login. You are logged into the NetBackup-Java application server program on the specified server. The NetBackup Administration Console appears. The console program continues to communicate through the server you specified for the remainder of the current session. Start a utility by clicking on it in the left pane. If you want to administer another NetBackup server, select File > Change Server to select a remote NetBackup server on which to make configuration changes.

5 6

Introduction NetBackup Administration Console setup

37

Note: The NetBackup Administration Console supports remote X Windows display only between same-platform systems. For example, assume you are on a Solaris system named tiger and the NetBackup-Java software is on a Solaris system named shark. Here, you can display the interface on tiger by performing rlogin to shark. Then run jnbSA -d tiger. However, if shark was an HP system, you could display jnbSA only directly on shark. In addition, the system where the console is displayed must run a version of the operating system that the console supports. Refer to the NetBackup release notes for supported versions, including any required release updates. The jnbSA command is described in NetBackup Commands for UNIX and Linux.

Running 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. See the NetBackup Installation Guide for information about how to install the Windows Display Console. The Windows Display Console can also be used 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. To start the Windows display console 1 On a Windows system where the Windows Display Console is installed and configured, select Start > Programs > Veritas NetBackup > NetBackup-Java Version 6.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. 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.

38 Introduction NetBackup Administration Console setup

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

In a site that contains multiple master servers, the systems can be configured so that one NetBackup Administrator 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.

For more information on remote administration, see To administer a remote master server on page 639.

Administering multiple versions of NetBackup servers

You can use one of the following methods to administer earlier versions of NetBackup. The order of the listed methods does not imply any preference.

Earlier versions of the NetBackup-Java Administration Console on UNIX platforms

Use the earlier versions of the NetBackup-Java Administration Console installed on the supported UNIX platform(s). The earlier versions available in a release are all of those supported in a mixed version environment with the current release. For example, all versions back to and including the last major release. In the NetBackup 6.5 release, the 6.0, the 5.0MP4 (or later), and the 5.1 console versions are available.

Earlier versions of the NetBackup-Java Administration Console on Windows platforms

Use the earlier versions of the NetBackup-Java Administration Console installed on the supported Windows platforms.

Remote display-back from UNIX servers

Use the UNIX remote display-back capabilities for UNIX servers that can run NetBackup-Java, possibly with tools such as Exceed or VNC.

Introduction NetBackup Administration Console setup

39

Remote display-back from Windows servers

Use the NetBackup Administration Console for Windows with the remote display-back capabilities on Windows NetBackup servers with tools like Windows Terminal Services or Remote Desktop.

At the console of the server with an earlier version of NetBackup

Use the relevant NetBackup-Java Administration Console from the console of the server with the earlier version of NetBackup.

40 Introduction Using the NetBackup Administration Console

Using the NetBackup Administration Console

The NetBackup Administration Console provides a graphical user interface through which the administrator can manage NetBackup. The interface can run on any NetBackup-Java capable system. Figure 1-2
Master Server The information in the NetBackup Administration Console applies to this server only. Backup, Archive, and Restore Performs the client actions for this system. Activity Monitor Displays the information about NetBackup jobs and provides some control over the jobs. NetBackup Management Contains the utilities to create and view reports, for configuring policies, storage units, catalog backups, and a utility for configuring master server, media server, and client properties. Media and Device Management Contains the utilities for managing the media and devices that NetBackup uses to store backups. Access Management Contents of node are viewable only by a Security Administrator when NetBackup access control is configured.

NetBackup Administration Console

Additional licensed utilities The nodes of other licensed utilities appear under the main NetBackup nodes.

Details pane Contains the configuration wizards and details specific to the utility that is selected.

You may also administer NetBackup through a character-based, menu interface (bpadm) or through a command line. bpadm is described in the NetBackup Administrators Guide, Volume II. NetBackup commands are described in NetBackup Commands for UNIX and Linux. The NetBackup Administration Console menus are described in the online help.

Introduction Using the NetBackup Administration Console

41

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 what NetBackup utility is selected in the left portion of the screen.

Getting Started Wizard Use the Getting Started Wizard to configure NetBackup for the first time. The wizard leads you 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 Disk Pool Configuration Wizard Volume Configuration Wizard Catalog Recovery Wizard Backup Policy and Configuration Wizard

Device Configuration Wizard Use the Device Configuration Wizard to configure NetBackup to use shared drives or to reconfigure an existing shared drive. Disk Pool Configuration Wizard Use the Disk Pool Configuration Wizard to create pools of disk volumes for backup by one or more media servers. For AdvancedDisk, you choose disk volumes directly attached to a media server. For OpenStorage, the wizard discovers disk appliances and then you choose disk volumes within the appliance. For SharedDisk, the wizard discovers disk arrays on the SAN and then you select pre-allocated logical unit numbers (LUNs). The wizard appears only if an Enterprise Disk Option license is installed. Volume Configuration Wizard Use the Volume Configuration Wizard to configure removable media to use for backups. NetBackup Catalog Backup Wizard Use the NetBackup Catalog Backup Wizard to set up catalog backups. Catalog backups are essential to recover data in the case of a server failure or crash. Backup Policy and Configuration Wizard Use the Backup Policy and Configuration Wizard to add a backup policy to your configuration. Catalog Recovery Wizard

42 Introduction Using the NetBackup Administration Console

Use the Catalog Recovery Wizard in a disaster recovery situation. Use the Catalog Recovery Wizard only if the NetBackup environment was running the policy-based online, hot catalog backup as the catalog backup type.

Backup, Archive, and Restore

Use the Backup, Archive, and Restore utility to perform backups and archives for this system, and restores for this system and other clients. Users can back up, archive, and restore files, directories, and the formatted raw partitions that reside on their own client computer. A user can restore files at any time. However, a user can back up and archive files only during the time periods that the administrator defines within a schedule for user backups. Users can view the progress and final status of the operations performed. Note: An archive is a special type of backup. During an archive, NetBackup first backs up the selected files, then deletes the files from the local disk if the backup is successful. In this manual, references to backups also apply to the backup portion of archive operations (except where otherwise noted). Documentation for the NetBackup client is available as online Help from the Backup, Archive, and Restore interface.

Activity Monitor
Use the Activity Monitor utility to monitor and control NetBackup jobs, services, processes, and drives. For more information, see Chapter 2, Activity Monitor on page 49.

NetBackup Management
This manual describes the applications and the utilities that are listed under NetBackup Management in the NetBackup Administration Console tree. The following sections describe the items that are found under NetBackup Management.

Reports
Use the Reports utility to compile information for to verify, manage, and troubleshoot NetBackup operations. For more information, see Chapter 3, Reports on page 71.

Introduction Using the NetBackup Administration Console

43

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. For more information see Chapter 4, Policies on page 81.

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

44 Introduction Using the NetBackup Administration Console

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 storage units that point to shareable disk can specify more than one media server. For more information, see Chapter 5, Storage units, unit groups, and lifecycle policies on page 213.

Catalog
Use the Catalog utility to create and configure a special type of backup NetBackup requires for its own internal databasesan offline, cold catalog backup. (An online, hot catalog backup can also be used, and is configured with a wizard or through the Policies utility.) 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.

For more information, see Chapter 6, NetBackup Catalog on page 275.

Host Properties
Use the Host Properties utility to customize NetBackup configuration options. In most instances, no changes are necessary. However, Host Properties allows the administrator to customize NetBackup to meet specific site preferences and requirements for master servers, media servers, and clients. For more information, see Chapter 7, Host properties on page 359.

Media and Device Management

The Media and Device Management utilities manage the media and the devices that NetBackup uses.

Introduction Using the NetBackup Administration Console

45

Device Monitor
Use the Device Monitor utility to manage drives, device paths, and service requests for operators. For more information, see Chapter 8, Device Monitor on page 495.

Media
Use the Media utility to add and manage removable media. For more information, see Chapter 9, Media on page 507.

Devices
Use the Devices utility to add, configure, and manage storage devices. For more information, see Chapter 10, Devices on page 593.

Credentials
Use the Credentials utility to add, remove, and manage log-in credentials for:

Disk array hosts (requires an Enterprise Disk Option license). For more information about disk array hosts and the SharedDisk disk type, see the NetBackup Shared Storage Guide. NDMP hosts (requires the Virtual Tape Option license). For more information about NDMP, see the NetBackup for NDMP Administrators Guide. Storage servers (requires an Enterprise Disk Option license). For more information about the Enterprise Disk Options, see the NetBackup Shared Storage Guide.

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

Access Management
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 Symantec 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 Introduction Using LiveUpdate to distribute NetBackup updates

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

Customizing the administration console

The View menu contains an Options selection that allows you to customize the various NetBackup utilities to suit your preferences (Activity Monitor, Device Monitor, Devices). Click the Help button on each tab for more information on the dialog box options.

Using LiveUpdate to distribute NetBackup updates

NetBackup LiveUpdate provides a cross-platform, policy-driven method to distribute NetBackup release updates to NetBackup 6.5 clients. LiveUpdate appears on the File menu. To use LiveUpdate, a NetBackup environment must include one NetBackup LiveUpdate server and one or more NetBackup clients with the Symantec LiveUpdate agent software installed. The NetBackup LiveUpdate server stores NetBackup release updates to be distributed to the clients. The Symantec LiveUpdate agent software is installed as an add-on product. For installation information, see the NetBackup Installation Guide. Release updates are distributed to clients when a LiveUpdate policy is run. The LiveUpdate policy checks the versions or release updates on each client that is listed in the policy. Then, the policy installs the NetBackup software that is available on the NetBackup LiveUpdate server. A LiveUpdate policy is considered a generic policy, and does not undergo the same pre-processing steps that are performed on backup policies. For example, the client file list is not checked.

How to configure NetBackup

The easiest way to configure NetBackup is to use the configuration wizards. Choose the Getting Started Wizard to configure NetBackup for the first time. This wizard invokes the following wizards:

Introduction How to configure NetBackup

47

Device Configuration Wizard Volume Configuration Wizard Catalog Backup Wizard Backup Policy Wizard

The wizards help you process configure the basic properties of a NetBackup environment. After you complete these wizards, your NetBackup environment should back up clients and back up your NetBackup catalog. To configure more advanced properties, you can use the NetBackup Administration Console. You also can use the Administration Console if you prefer not to use the wizards. Alternatively, you can use the wizards to configure the basic properties and then use the Administration Console to configure the more advanced properties. The following steps explain how to configure NetBackup by using the NetBackup Administration Console. Each step provides references for more information, if needed. To configure NetBackup without wizards 5 6 7 8 Start the NetBackup Administration Console. (See NetBackup administration interfaces on page 34.) Use the Devices utility to add and configure the storage devices. (See Devices on page 593.) Use the Media utility to add removable media in the NetBackup Administration Console. (See Media on page 507.) Ensure that all daemons are active on the NetBackup master server (and Enterprise Media Manager server, if the EMM server is not the master server). For more information, see Daemons tab on page 58. Configure the storage units. A storage unit is one or more storage devices of a specific type (tape or disk) that attach to a NetBackup server.

For an overview of NetBackup storage units, see Storage units, unit groups, and lifecycle policies on page 213. For instructions about how to add storage units, see Creating a storage unit on page 217.

10 Configure a NetBackup catalog backup. The NetBackup catalogs contain configuration information as well as critical information on client backups. (See NetBackup Catalog on page 275.) 11 Configure the backup policies for the clients to be backed up. (See Policies on page 81.)

48 Introduction How to configure NetBackup

12 Customize host properties to meet site preferences, if necessary. In most instances, the NetBackup defaults provide satisfactory results. (See Changing host properties on page 361.) 13 Test the configuration as follows: a If you created user-directed backup or archive schedules, test the schedules by performing a backup or archive from a client. Check the log on the client to see if the operations were successful. If the backup was successful, restore the same files. To test the automatic backup schedules, either wait until the schedules are due or run the schedules manually from the master server. After the automatic schedules have run, check the Backup Status report to ensure that the backups completed successfully for all clients.

Chapter

Activity Monitor
This chapter explains how to use the NetBackup Activity Monitor to perform various functions to monitor and troubleshoot NetBackup jobs, daemons, and processes.

Introduction to the Activity Monitor on page 50 Jobs tab on page 56 Daemons tab on page 58 Processes tab on page 62 Media mount errors on page 67 Managing the jobs database on page 67

50 Activity Monitor Introduction to the Activity Monitor

Introduction to the Activity Monitor

Use the Activity Monitor in the NetBackup Administration Console to monitor and control NetBackup jobs, daemons, and processes. As long as the Activity Monitor is active in the NetBackup-Java Administration Console, the bpjobd daemon supplies job activity status to the Activity Monitor. Updates to the Activity Monitor occur as jobs are initiated, updated, and completed. Without a refresh cycle, updates occur instantaneously. Figure 2-1 Activity Monitor

Menu bar Toolbar

Current master server

Status bar

Details pane

Tabs

Right-click in Details pane to view shortcut menu

Activity Monitor Introduction to the Activity Monitor

51

Activity Monitor menu bar

The options on the Activity Monitor menu bar are described in the online help. Note: The Filter option on the View menu is useful for displaying in Activity Monitor only those jobs with specified characteristics. For example, the jobs that were started before a specific date; jobs in the queued state; jobs with status completion codes within a specified range. To show or hide column heads 1 Open the Activity Monitor.

2 3

Click View > Column Layout. The Column Layout dialog box appears. Select the heading you want to display or hide.

Select the Show button to display the heading. Select the Hide button if you do not want to see the column head.

To change the order in which the columns appear, select the column head. Then, click the Move Up button or the Move Down button to reorder the columns. Click OK to apply the changes.

To monitor the detailed status of selected jobs 1 2 3 Open the Activity Monitor and select the Jobs tab. Select the job(s) for which you want to view details. Select Actions > Details. A Jobs Details dialog box appears for each job you selected.

52 Activity Monitor Introduction to the Activity Monitor

To delete completed jobs 1 2 3 Open the Activity Monitor and select the Jobs tab. Select the job(s) you want to delete. Select Edit > Delete. All selected jobs are deleted.

To cancel a job that has not completed 1 2 Open the Activity Monitor and select the Jobs tab. Select the job that has not completed that you would like to cancel. It may be a job that is in the Queued, Re-Queued, Active, Incomplete, or Suspended state. Select Actions > Cancel Job. All selected jobs are canceled. If the selected job is a parent job, all the children of that parent job are canceled as well. In most cases, a canceled child job cancels only that job and allows the other child jobs to continue. One exception is multiple copies created as part of a policy or storage lifecycle policy: canceling a child job cancels the parent job and all child jobs. To cancel all jobs in the jobs list that have not completed, click Actions > Cancel All Jobs.

3 4

To restart a completed job 1 2 3 Open the Activity Monitor and select the Jobs tab. Select the completed job you want to restart. Select Actions > Restart Job. All selected jobs are restarted. In this case, a new job ID is created for the job. The job details for the original job will reference the job ID of the new job.

To suspend a restore or backup job 1 2 3 Open the Activity Monitor and select the Jobs tab. Select the job you want to suspend. Select Actions > Suspend Job. All selected jobs are suspended.

Note: Only the backups and the restores that contain checkpoints can be suspended. To resume a suspended or an incomplete job 1 Open the Activity Monitor and select the Jobs tab.

Activity Monitor Introduction to the Activity Monitor

53

2 3

Select the suspended or the incomplete job you want to resume. Select Actions > Resume Job. All selected jobs are resumed.

Note: Only the backups and the restores that contain checkpoints can be suspended. To print job detail information from a list of jobs 1 1 2 Open the Activity Monitor and select the Jobs tab. Select a job to print. Hold down the Control or Shift key to select multiple jobs. If no job is selected, all jobs are printed. Select File > Print.

To export Activity Monitor data to a text file 1 Open the Activity Monitor.

2 3 4

From any Activity Monitor tab, select File > Export. Select whether to export all rows or only the rows currently selected. Enter the full path to the file where you want the job data to be written, then click Save.

If a job fails, use the Troubleshooter on the Help menu. The Troubleshooter helps explain the problem and provides the corrective actions that are based on the NetBackup status code that the job returns. To run troubleshooter within the Activity Monitor 1 2 3 Select a job in the Activity Monitor. Select the job you want to troubleshoot. Open the Troubleshooter:

Click the Troubleshoot icon. Select Help > Troubleshooter.

54 Activity Monitor Introduction to the Activity Monitor

Open the job details for a job, click the Detailed Status tab. Then click Troubleshooter. Right-click on the job. Select Troubleshooter.

The Troubleshooter dialog box appears. An explanation of the problem is displayed on the Problems tab and a recommended action appears on the Troubleshoot tab. If there is no status code entered in the Troubleshooter status code field, enter the status code of the failed job. Click Lookup to locate the troubleshooting information. You can open the Troubleshooter at any time and enter a status code.

Status bar
The status bar appears in the Jobs tab, at the top of the Activity Monitor Details pane. The status bar displays the following information:

The master server on which the jobs reside. The total number of jobs. The number of jobs in each of the job states: Active, Queued, Waiting for Retry, Suspended, Incomplete, and Done. The number of jobs currently selected. The number of NetBackup daemons that run.

The numbers always reflect the actual number of jobs, even when the filter is used.

Setting Activity Monitor options

Click View > Options and select the Activity Monitor tab to access configurable options for the Activity Monitor.

Activity Monitor Introduction to the Activity Monitor

55

Figure 2-2

Options dialog

You may choose to receive confirmation warnings as you work in the Activity Monitor:

Confirm job deletions: The user is prompted with a confirmation dialog box when a job is deleted. Confirm job cancellations: The user is prompted with a confirmation dialog box when a job is cancelled. Confirm stop daemons: The user is prompted with a confirmation dialog box when a daemon is stopped.

To discontinue further confirmations, check In the future, do not show this warning in the Warning dialog box. Set the Maximum Details Windows value to limit the number of Activity Monitor details that can be displayed at one time. Check Auto Refresh periodically to refresh data on the Daemons tab and the Processes tab and job details elapsed time. Other Jobs tab data is refreshed independently of the Auto Refresh setting. Enter the rate (in seconds) at which data is refreshed in the Daemons and the Processes tabs. Click OK to close the dialog box and apply the changes after making any changes.

56 Activity Monitor Jobs tab

Jobs tab
The Jobs tab displays all jobs that are in process or have been completed for the master server currently selected. Note: Job selection preference is given to jobs from NetBackup 6.0 media servers over media servers of previous versions.

Parent jobs
For some backup jobs, a parent job is used to perform pre- and post-processing. Parent jobs display a dash (-) in the Schedule column. A parent job runs the start and end notify scripts (PARENT_START_NOTIFY, PARENT_END_NOTIFY) from the master server: /usr/openv/netbackup/bin/ The role of the parent job is to initiate requested tasks in the form of children jobs. The tasks vary, depending on the backup environment:

Snapshot Client: The parent job creates the snapshot, initiates children jobs, and deletes the snapshot when complete. Children jobs are created if the Snapshot Client settings are configured to retain snapshots for Instant Recovery, then copy snapshots to a storage unit. (Snapshots and copy snapshots to a storage unit is selected in the policy Schedule Attributes tab.) Children jobs are not created if the Snapshot Client settings are configured to retain snapshots for Instant Recovery, but to create snapshots only. That is, the snapshot is not backed up to a storage unit, so no children jobs are generated. (Snapshots only is selected in the policy Schedule Attributes tab.) Bare Metal Restore: The parent job runs brmsavecfg, then initiates the backup as a child job. If multistreaming and BMR are used together, the parent job may start multiple children jobs. Offline, cold catalog backups: The parent job initiates the bpbackupdb as a child job. Online, hot catalog backups: The parent job for hot catalog backups works with bpdbm to initiate multiple children backup jobs: a Sybase backup, a file system backup of the master, and backups of any 5.x media servers and BMR database. Multiple copies:

Activity Monitor Jobs tab

57

A multiple copies job produces one parent job and multiple child jobs. Child jobs that are part of a multiple copies parent job cannot be restarted individually. Only the parent job (and subsequently all the children jobs) can be restarted. For setup information, see Multiple copies on page 131.

Multiple data streams: The parent job performs stream discovery and initiates children jobs. A parent job does not display a schedule in the Activity Monitor. Instead, a dash (-) is displayed for the schedule because the parent schedule is not used and the children schedules may be different. The children jobs display the ID of the parent job in the Activity Monitor. SharePoint: The parent job runs a resolver process during which children jobs are started. This process is similar to the stream discovery for multiple data streams. If multiple data streams are enabled, some children jobs may be split into multiple streams. Vault: The parent job starts the Vault profile. Then, the Vault profile starts the duplicates as jobs. The duplicates do not appear as children jobs in the Activity Monitor.

To view job details To view the details for a specific job, double-click on the job in the Jobs tab. The Job Details dialog box appears that contains detailed job information on two tabs: a Job Overview tab and a Detailed Status tab. Not all columns are displayed by default. Click View > Column Layout to show or hide columns.

58 Activity Monitor Daemons tab

Daemons tab
The Daemons tab displays the status of NetBackup daemons on the selected master server. Figure 2-3 Daemons tab in the Activity Monitor

Not all columns are displayed by default. Click View > Column Layout to show or hide columns. Table 2-1 Daemon
Adaptive Server Anywhere (NB_dbsrv)

NetBackup daemons Description

Manages the NetBackup relational database. This service must be running on the NetBackup Enterprise Media Manager server during all normal NetBackup operations. Appears if Bare Metal Restore is installed.

NetBackup Bare Metal Restore Master Server (bmrd) NetBackup Client Service (bpinetd)

Listens for connections from NetBackup servers in the network and when an authorized connection is made, starts the necessary NetBackup process to service the connection. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console. If it were stopped, the console could not display the data.

Activity Monitor Daemons tab

59

Table 2-1 Daemon

NetBackup daemons Description

Service that is used to communicate with legacy NetBackup services.

NetBackup Compatibility Service (bpcompatd) NetBackup Database Manager (bpdbm) NetBackup Device Manager (ltid)

Manages the NetBackup internal databases and catalogs. BPDBM must be running on the NetBackup master server during all normal NetBackup operations. Starts the Volume Manager (vmd), the automatic volume recognition process (avrd), and any robotic processes. Processes the requests to mount and dismount tapes in robotically controlled devices through the robotic control processes. Mounts the volumes on the tape or optical storage devices in response to user requests. Accesses and manages the database where media and device configuration information is stored (EMM_DATA.db). nbemm.exe must be running in order for jobs to run. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console. If it were stopped, the console could not display the data.

NetBackup Enterprise Media Manager (nbemm)

NetBackup Event Management Provides the communication infrastructure to pass information and events Service (nbevtmgr) between distributed NetBackup components. Runs on the same system as the NetBackup Enterprise Media Manager. NetBackup Job Manager (nbjm) Accepts the jobs that the Policy Execution Manager (nbpem) submits and acquires the necessary resources. The Job Manager then starts the job, and informs nbpem that the job is completed.

NetBackup Policy Execution Manager (nbpem)

Compiles the worklist for jobs and determines when jobs are due to run. If a policy is modified or if an image expires, nbpem is notified and the worklist is recompiled. Discovers and monitors disk storage on NetBackup media servers. Also discovers, monitors, and manages Fibre Transport (FT) connections on media servers and clients for the NetBackup SAN Client option. Runs on NetBackup media servers. Processes the requests from NetBackup clients and servers. bprd also prompts NetBackup to perform automatically scheduled backups. bprd must be running on the NetBackup master server to perform any backups or restores. Allocates the storage units, tape drives, and client reservations for jobs. nbrb works with the Enterprise Media Manager (NBEMM).

NetBackup Remote Manager and Monitor Service (nbrmms)

NetBackup Request Manager (bprd)

NetBackup Resource Broker (nbrb)

60 Activity Monitor Daemons tab

Table 2-1 Daemon

NetBackup daemons Description

Facilitates the communication between the NetBackup graphical user interface and NetBackup logic. NBSL is required to run NetBackup Operations Manager (NOM), an application that manages and monitors multiple NetBackup environments. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console. If it were stopped, the console could not display the data.

NetBackup Service Layer (nbsl)

NetBackup Service Monitor (nbsvcmon)

Monitors the NetBackup services that run on the local machine. If a service unexpectedly terminates, this service tries to restart the terminated service. If nbsvcmon determines that NetBackup is configured for a cluster, the service shuts down and the monitoring is taken over by the cluster. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console. If it were stopped, the console could not display the data.

NetBackup Status Collection Service (vmscd)

The NetBackup Enterprise Media Manager starts the NetBackup Status Collection service on the same host as the EMM server if one or more NetBackup 5.x servers are present in the configuration. vmscd maintains a persistent connection with NetBackup 5.x servers and monitors the status of drives that are attached to NetBackup 5.x servers. The NetBackup Storage Lifecycle Manager manages lifecycle operations including duplication, staging, and image expiration. Manages NetBackup Vault. NBVAULT must be running on the NetBackup Vault server during all NetBackup Vault operations. Manages the volumes (tapes) needed for backup or restore and starts local device management daemons and processes.

NetBackup Storage Lifecycle Manager (nbstserv) NetBackup Vault Manager (nbvault) NetBackup Volume Manager (vmd)

More about daemons

Stand-alone daemons: These NetBackup daemons always run and listen to accept connections. Examples include bpdbm, bprd, bpjobd, and vmd. Multiprocess stand-alone daemons: NetBackup daemons that fork a child process to handle requests. Examples include bpdbm and bprd. Single-process stand-alone daemons: NetBackup daemons that accept connections and handle requests in the same process. inetd daemons: NetBackup daemons usually launched by inetd(1m) or bpinetd. Examples include bpcd, bpjava-msvc, and vnetd.

Activity Monitor Daemons tab

61

Note: Symantec recommends that you exit all instances of the NetBackup-Java Administration Console after restarting daemons in the Activity Monitor or by using a command. Then restart the console with the jnbSA command. (The jnbSA command is described in NetBackup Commands for UNIX and Linux.)

Other Symantec services

Several services do not appear in the Activity Monitor. Table 2-2 Service Symantec services Description

Symantec Private Branch Exchange The Symantec Private Branch Exchange provides single-port access to clients outside the firewall that connect to Symantec product services. Service name: VRTSpbx. Symantec Product Authentication Service The Symantec Product Authentication Service validates, identities, and forms the basis for authorization and access control in Symantec applications. Service name: VRTSat. The Symantec Product Authorization Service provides access control in Symantec applications. Service name: VRTSaz.

Symantec Product Authorization Service

To monitor NetBackup daemons 1 2 3 Open the Activity Monitor and select the Daemons tab. Select the daemon(s) for which you want to view details. Select Actions > Details. A Daemons Details dialog box appears for each daemon you selected.

To view the details of a daemon, double-click the process in the Daemons tab. For a description of the daemon details, click Help in the Daemon Details dialog box. To start or stop a daemon 1 2 3 Open the Activity Monitor and select the Daemons tab. Select the daemon(s) you want to start or stop. Select Actions > Start Daemon or Actions > Stop Daemon.

62 Activity Monitor Processes tab

Processes tab
The Processes tab displays the NetBackup processes that run on the master server. Not all columns are displayed by default. Click View > Column Layout to show or hide columns. Table 2-3 Process
acsd

NetBackup processes Port

13702

Description
The acsd (Automated Cartridge System) daemon runs on the NetBackup media server and communicates mount and unmount requests to the host that controls the ACS robotics. The NetBackup ACS storage server interface (SSI) event logger acssel logs events. The NetBackup ACS storage server interface (SSI) acsssi communicates with the ACS library software host. acsssi processes all RPC communications from acsd or from the ACS robotic test utility that are intended for the ACS library software. The Automatic Volume Recognition process handles automatic volume recognition and label scans. The process allows NetBackup to read labeled tape and optical disk volumes and assign the associated removable media requests to drives.

acssel

acsssi

avrd

bmrd

8362 13782

The process for the NetBackup Bare Metal Restore Master Server daemon. The NetBackup Client daemon, this process issues requests to and from the master server and the media server to start programs on remote hosts. On UNIX clients, bpcd can only be run in stand-alone mode. On Windows, bpcd always runs under the supervision of bpinetd.exe. NetBackup has a specific configuration parameter for bpcd: if the port number is changed within the NetBackup configuration, the software causes the port number in the services file to be updated as well.

bpcd

bpcompatd 13721

The process for the NetBackup Compatibility daemon. The process for the NetBackup Database Manager daemon. It responds to queries that are related to the NetBackup catalog.

bpdbm

inetd

The process for the NetBackup Client daemon. It provides a listening service for connection requests.

Activity Monitor Processes tab

63

Table 2-3 Process

bpjava-msvc

NetBackup processes Port

13722

Description
The NetBackup-Java application server authentication service program. inetd starts the program during startup of the NetBackup-Java GUI applications and authenticates the user that started the NetBackup-Java GUI application. The NetBackup-Java application server user service program on NetBackup servers. bpjava-msvc starts the program upon successful login with the NetBackup-Java applications login dialog box. bpjava-susvc services all requests from the NetBackup-Java GUI applications for administration and end-user operations on the host on which the NetBackup-Java application server is running.

bpjava-susvc

bpjobd

13723

The NetBackup Jobs Database Management daemon, this process queries and updates the jobs database. The process for the NetBackup Request Manager daemon. It starts the automatic backup of clients and responds to client requests for file restores and user backups and archives.

bprd

13720

ltid 13699

The process for the Media Manager Device daemon. The VSM request daemon (database request management) for Storage Migrator. migrd handles communication for VSM-Java and commands. The NetBackup Administration Console on the Windows platform. The process for the NetBackup Enterprise Media Manager daemon. It accesses and manages the database where media and device configuration information is stored (EMM_DATA.db). nbemm.exe must be running in order for jobs to run.

migrd

NBConsole nbemm

nbEvtMgr

The process for the NetBackup Event Manager daemon. It creates and manages event channels and objects for communication among NetBackup daemon. The Event Manager daemon runs with the Enterprise Media Manager (nbemm) only on master servers.

nbfdrv64

It controls the Fibre Transport target mode drivers on the media server. It runs on media servers configured for NetBackup Fibre Transport. The Fibre Transport (FT) server process that runs on media servers configured for NetBackup Fibre Transport. It does the following for the server side of the FT connection: controls data flow, processes SCSI commands, manages data buffers, and manages the target mode driver for the host bus adaptors.

nbftsrvr

64 Activity Monitor Processes tab

Table 2-3 Process

nbjm

NetBackup processes Port Description

The process for the NetBackup Job Manager daemon. It accepts the jobs that the Policy Execution Manager (NBPEM) submits and acquires the necessary resources. The Job Manager then starts the job, and informs nbpem that the job is completed.

nbpem

The process for the NetBackup Policy Execution Manager daemon. It compiles the worklist for jobs and determines when jobs are due to run. If a policy is modified or if an image expires, NBPEM is notified and the worklist is recompiled.

nbproxy

This process that safely allows new multi-threaded NetBackup processes to use existing multi-threaded unsafe libraries. This process allocates storage units, tape drives, and client reservations for jobs. nbrb works with the Enterprise Media Manager (NBEMM). The process for the NetBackup Remote Manager and Monitor service. Enables NetBackup to remotely manage and monitor resources on a system that are used for backup (or affected by backup activity). The process for the NetBackup Service Layer daemon. nbsl facilitates the communication between the graphical user interface and NetBackup logic.

nbrb

nbrmms

nbsl

nbstserv

The process for the NetBackup Storage Lifecycle Manager. Manages storage lifecycle policy operations and schedules duplication jobs. Monitors disk capacity on capacity managed volumes and removes older images when required. The process for the NetBackup Service Monitor. Monitors the NetBackup services. When a service unexpectedly terminates, nbsvcmon attempts to restart the terminated service. If Vault is installed, the process for the NetBackup Vault Manager daemon. 10000 NDMP is the acronym for Network Data Management Protocol. NDMP servers are designed to adhere to this protocol and listen on port 10000 for NDMP clients to connect to them. The odld (Optical Disk Library) daemon runs on the host that has an optical disk library. This process receives NetBackup Device Manager requests to mount and unmount volumes and communicates these requests to the robotics through SCSI interfaces.

nbsvcmon

nbvault

ndmp

odld

13706

Activity Monitor Processes tab

65

Table 2-3 Process

oprd

NetBackup processes Port Description

The NetBackup Volume Manager (vmd) starts the oprd operator request daemon. This process receives requests to mount and unmount volumes and communicates the requests to the NetBackup Device Manager ltid. The NetBackup Device Manager communicates the requests to the robotics through SCSI interfaces. 13713 The tl4d process runs on the host that has a Tape Library 4MM. This process receives NetBackup Device Manager requests to mount and unmount volumes and communicates these requests to the robotics through SCSI interfaces. The tl8d process runs on a NetBackup media server that manages a drive in a Tape Library 8MM. This process receives NetBackup Device Manager requests to mount and unmount volumes, and sends these requests to the robotic-control process tl8cd. The tl8cd process communicates with the TL8 robotics through SCSI interfaces. To share the tape library, tl8cd runs on the NetBackup server that provides the robotic control.

tl4d

tl8d tl8cd

13705

tldd tldcd

13711

The tldd process runs on a NetBackup server that manages drive in a Tape Library DLT. This process receives NetBackup Device Manager requests to mount and unmount volumes, and sends these requests to the robotic-control process tldcd. The tldcd process communicates with the Tape Library DLT robotics through SCSI interfaces. To share the tape library, tldcd runs on the NetBackup server that provides the robotic control.

tlhd tlhcd

13717

The tlhd process runs on each NetBackup server that manages a drive in a Tape Library Half-inch. This process receives NetBackup Device Manager requests to mount and unmount volumes and sends these requests to the robotic-control process tlhcd. The tlhcd process runs on the NetBackup server that provides the robotic control and communicates with the TLH robotics through SCSI interfaces.

tlmd

13716

The tlmd Tape Library Multimedia (TLM) daemon runs on a NetBackup server. It communicates mount, unmount, and robot inventory requests to a NetBackup media server that hosts ADIC DAS/SDLC software and controls the TLM robotics. The tshd process runs on a NetBackup server that has a Tape Stacker Half-inch. The tshd process receives requests to mount and unmount volumes or for robot inventory and communicates these requests to the robotics through SCSI interfaces.

tshd

13715

66 Activity Monitor Processes tab

Table 2-3 Process

vmd

NetBackup processes Port

13701 13724

Description
The process for the NetBackup Volume Manager daemon. Veritas Network Daemon allows all socket communication to take place while connecting to a single port. Legacy NetBackup services that were introduced before NetBackup 6.0 use the vnetd port number. The Veritas Authorization Service verifies that an identity has permission to perform a specific task. The Veritas Authentication Service validates, identifies, and forms the basis for authorization and access. The Symantec Private Branch Exchange allows all socket communication to take place while connecting through a single port. NetBackup services that were introduced in NetBackup 6.0 use the veritas_pbx port number.

vnetd

vrts-auth-port

4032

vrts-at-port

2821

veritas_pbx

1556

Monitoring NetBackup processes

To view the details for a process, double-click the process in the Processes tab. For a description of the process details, click Help in the Process Details dialog box.

Activity Monitor Media mount errors

67

Media mount errors

When media is mounted for NetBackup jobs, errors can occur. Depending on the type of error that is encountered, the request queues, or it is cancelled.

Queued media mount errors

When the mount request is queued, an operator-pending action is created and is displayed in the Device Monitor. A queued mount request leads to one of the following actions:

The mount request is suspended until the condition is resolved. The operator denies the request. The media mount timeout is reached.

Canceled media mount errors

When a mount request is automatically canceled, NetBackup tries to select other media to use for backups. (Selection applies only in the case of backup requests.) Many conditions lead to a mount request being automatically canceled instead of queued. When a media mount is canceled, different media is selected so that the backup is not held up. The following conditions can lead to automatic media reselection:

The requested media is in a DOWN drive. The requested media is misplaced. The requested media is write-protected. The requested media is in a drive not accessible to the media server. The requested media is in an offline ACS LSM (Automated Cartridge System Library Storage Module). (ACS robot type only.) The requested media has an unreadable barcode. (ACS robot type only.) The requested media is in an ACS that is not accessible. (ACS robot type only.) The requested media has been otherwise determined to be unmountable.

Managing the jobs database

NetBackup uses the /usr/openv/netbackup/bin/admincmd/bpdbjobs -clean command to delete done jobs periodically.

68 Activity Monitor Managing the jobs database

By default, the bpdbjobs process deletes all the done jobs that are more than three days old. By default, the bpdbjobs process retains more recent done jobs until the three-day retention period expires. If the bprd NetBackup request daemon is active, bprd starts the bpdbjobs process automatically when it performs other cleanup tasks. The process starts the first time bprd wakes up after midnight. The automatic startups occur regardless of whether you choose to run bpdbjobs at other times by using cron or alternate methods.

Retaining job information in the database

You may want to keep jobs in the jobs database longer than the default of three days.

Changing the default on a permanent basis

To change the default values on a permanent basis, change the entries in the bp.conf file. For example, add the following entry to the bp.conf file: KEEP_JOBS_HOURS = 192 Where 192 is the number of hours that unsuccessful jobs are kept in the jobs database or Activity Monitor display. For example, to change the retention of successful jobs, add the following entry: KEEP_JOBS_SUCCESSFUL_HOURS = 192 Where 192 is the number of hours that successful jobs are kept in the jobs database or Activity Monitor display.

Notes

The default values for KEEP_JOBS_SUCCESSFUL_HOURS and KEEP_JOBS_HOURS is 78 hours. The retention period values are measured against the time the job ended. Information about successful jobs cannot be kept longer than information about unsuccessful jobs. If KEEP_JOBS_SUCCESSFUL_HOURS is greater than KEEP_JOBS_HOURS, bpdbjobs sets KEEP_JOBS_SUCCESSFUL_HOURS to equal KEEP_JOBS_HOURS. If KEEP_JOBS_SUCCESSFUL_HOURS is set to 0, bpjobd uses the KEEP_JOBS_HOURS bpdbjobs value instead for successful jobs. If the KEEP_JOBS_SUCCESSFUL_HOURS value is greater than 0 but less than KEEP_JOBS_HOURS, KEEP_JOBS_HOURS is used for unsuccessful jobs only.

Activity Monitor Managing the jobs database

69

BPDBJOBS_OPTIONS environment variable

The BPDBJOBS_OPTIONS environment variable provides a convenient method to set job retention options with a script. The bpdbjobs process determines how long to retain a job by checking for the BPDBJOBS_OPTIONS environment variable. If present, BPDBJOBS_OPTIONS overrides the bp.conf settings. The following options can be used to determine the length of time NetBackup retains jobs. The options should be entered in lower case in the BPDBJOBS_OPTIONS environmental variable:

-keep_hours hours Use with the -clean option to specify how many hours bpdbjobs keeps unsuccessful done jobs. Default: 72 hours. To keep both successful and both failed jobs longer than the default of 72 hours, keep_successful_hours must be used with keep_hours -keep_successful_hours hours Use with the -clean option to specify how many hours bpdbjobs keeps successful done jobs. The number of hours can range from 3 to 720 but must be less than or equal to keep_hours. Values outside the range are ignored. Default: 72 hours. -keep_days days Use with the -clean option to specify how many days bpdbjobs keeps done jobs. Default: 3 days. keep_successful_days days Use with the -clean option to specify how many days bpdbjobs keeps successful done jobs. Default: 3 days. This value must be less than the -keep_days value.

A script (cleanjobs) was used in the following example. The script can be copied directly from this document, then changed as needed.

The first line specifies how long to keep unsuccessful jobs (24 hours) and successful jobs (five hours). The second line specifies the path to the bpdbjobs command. The correct location of bpdbjobs must be indicated. In this example, NetBackup was installed in the default location:
setenv BPDBJOBS_OPTIONS -keep_hours 24 -keep_successful_hours 5 -clean /usr/openv/netbackup/bin/admincmd/bpdbjobs ${*}

The .bat file can be stored anywhere, as long as it is run from the appropriate directory.

70 Activity Monitor Managing the jobs database

bpdbjobs command line options

The bpdbjobs command interacts with the jobs database to delete or move done job files. The command line options supersede all other job retention instructions. The -clean option causes bpdbjobs to delete the done jobs that are older than a specified time period: bpdbjobs -clean [ -M <master servers> ] [ -keep_hours <hours> ] or [ -keep_days <days> ] [ -keep_successful_hours <hours> ] or [ -keep_successful_days <days> ] For example, the following command deletes unsuccessful jobs older than 720 hours. bpdbjobs -clean -keep_hours 720 For a complete description of the bpdbjobs command, see NetBackup Commands for UNIX and Linux.

bpdbjobs debug log

If you need detailed information on bpdbjobs activities, enable the bpdbjobs debug log by creating the following directory:
/usr/openv/netbackup/logs/bpdbjobs

Note: Before you use a debug log, read the guidelines in the Debug Logs section of the NetBackup Troubleshooting Guide for UNIX and Windows.

Customizing bpdbjobs output

To customize the output of bpdbjobs, add a BPDBJOBS_COLDEFS entry to the bp.conf file for each column you want to appear in the output. For more information on the available entries, see the NetBackup Administrators Guide, Volume II, Chapter 1.

Chapter

Reports
Use the Reports utility to generate reports on many aspects of the NetBackup environment. The reports serve to verify, manage, and troubleshoot NetBackup operations. NetBackup reports display information according to job status, client backups, and media contents. The Troubleshooter is available within the Reports utility to help analyze the cause of errors that can appear in a NetBackup report.

Introduction to the Reports utility on page 72 Reports window on page 73 NetBackup report types on page 76 Using the Troubleshooter within reports on page 80

72 Reports Introduction to the Reports utility

Introduction to the Reports utility

Expand Reports in the NetBackup Administration Console to display a description of all possible reports in the Details pane. For a description of each report type, see NetBackup report types on page 76. Figure 3-1 NetBackup Report utility

Current master server

Report descriptions

To run a report 1 In the NetBackup Administration Console, expand NetBackup Management > Reports. A list of report types appears. The report information is for the master server that is currently selected. To run a report on a different master server, click File > Change Server. For more information, see To administer a remote master server on page 639. Select the name of the report you would like to run. The right pane displays various options for running the report. Select the media servers and clients on which to run the report, then select the time period for which the report runs. Click Run Report. For a description of the report fields, see NetBackup report types on page 76.

2 3 4

Reports Reports window

73

Reports window
The Reports window contains multiple ways to view report listings and manage report data. Figure 3-2 NetBackup Reports window

Menu bar Toolbar

Report contents

Right-click in contents area to display shortcut menus

Shortcut menus
To display a list of commands that apply to a list, right-click on a report. Depending on which report is viewed, the shortcut list may include:

Column Layout: Opens the Column Layout dialog box where you can show or hide columns. (By default, all columns are not displayed.) Sort: Opens the Sort dialog box where you can specify sort criteria for the columns. Find: Opens the Find dialog box, used to find text within the report. Filter: Use the Filter option to narrow in on specific data in a table. Use the controls on the Filter dialog box to list the rows that match specified criteria. Troubleshooter: Launch the Troubleshooter to enter a status code.

74 Reports Reports window

Reports settings
Use the report settings to specify the following criteria for building a report. Not all settings are available for every report type.

Date/Time range
Specify the time period that you want the report to encompass. By default, the start time is one day before the report is run and the end time is the time the report is run. Select Earliest available to include the earliest possible data available. Select Current time to include all the data until the present. For more information, see Keep logs on page 383. The Clean-up host property, Keep logs, determines the period of time for which the information is available.

Client
Click the Client box and select All clients or select the client to which the report applies.

Disk pool
Click the Disk Pool box and select All Disk Pools or the disk pool type to which the report applies. The field is enabled only if OpenStorage, SharedDisk, or AdvancedDisk disk pools exist in the configuration.

Disk type
Click the Disk Type box and select All Disk Types or the disk storage unit type to which the report applies.

Job ID
Specify the Job ID for which you want the report.

Media ID
For media types of reports, specify the media ID or All Media. The Media Contents report requires a specific ID.

Reports Reports window

75

Media owner
Click the Media Owner box and select the owner of the media to which the report applies. The NetBackup media servers and server groups in your environment appear in the drop-down list.

Media server
Click the Media server box and select All Media Servers or the name of the media server to which the report applies. The currently selected master server and the media servers appear in the report.

Path
The Path selection appears for specific Disk Type selections. Specify the path to include in the report.

Storage unit
Click the Storage unit box and select All Storage Units or the name of the storage unit to which the report applies.

Verbose listing
Select Verbose listing to have NetBackup provide more details in the Media Summary report.

Volume ID
If the Disk Type selection for a disk report is Array Disk, the Volume ID selection appears. Select a Volume ID to include in the report.

Volume pool
For a media summary report, specify the volume pool name or All Volume Pools.

Run report
Click Run Report after youve selected the criteria for a report.

Stop report
Click Stop Report if a report is running, but you dont want to wait for it to finish.

76 Reports NetBackup report types

NetBackup report types

The following sections describe the contents of NetBackup reports.

Status of Backups report

The Status of Backups report displays status and error information about the jobs that have completed within the specified time period. If an error has occurred, a short explanation of the error is included. Click Help within the Status of Backups report window for a description of each column.

Client Backups report

The Client Backups report displays detailed information on the backups that complete within the specified time period. Click Help within the Client Backups report window for a description of each column.

Problems report
The Problems report lists the problems that the server has logged during the specified time period. The information in this report is a subset of the information that is obtained from the All Log Entries report. Click Help within the Problems report window for a description of each column.

All Log Entries report

The All Log Entries report lists all log entries for the specified time period. This report includes the information from the Problems report and Media Logs report. This report also displays the transfer rate. The transfer rate is useful to determine and predict rates and backup times for future backups. (The transfer rate does not appear for multiplexed backups.) Click Help within the All Log Entries report window for a description of each column.

Images on Media report

The Images on Media report lists the contents of the media as recorded in the NetBackup image catalog. You can generate this report for any type of media (including disk) and filter it according to client, media ID, or path.

Reports NetBackup report types

77

Note: The Images on Media report does not display information for the media that is used for NetBackup offline, cold catalog backups. Click Help within the Images on Media report window for a description of each column.

Media Logs report

The Media Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. Click Help within the Media Logs report window for a description of each column.

Tape Reports
The following sections describe the six types of tape reports:

Images on Tape report

The Images on Tape report generates the image list present on the tape storage units that are connected to the media server. The report is a subset of the Images on Media report and displays only tape-specific columns. Click Help within the Images on Tape report window for a description of each column.

Tape Logs report

The Tape Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. The report is a subset of the Media Logs report and displays only tape-specific columns. Click Help within the Tape Logs report window for a description of each column.

Tape Contents report

The Tape Contents report displays the contents of a volume as read directly from the media header and backup headers. This report lists the backup IDs (not each individual file) that are on a single volume. If a tape must be mounted, the delay is longer before the report appears. Note: The Tape Contents report does not apply to disk type storage units or NetBackup offline, cold catalog backups.

78 Reports NetBackup report types

Click Help within the Tape Contents report window for a description of each column.

Tape Summary report

The Tape Summary report summarizes active and nonactive volumes for the specified media owner according to expiration date. It also displays how many volumes are at each retention level. In verbose mode, the report displays each media ID and the expiration date. Nonactive media are those with a status of FULL, FROZEN, SUSPENDED, or IMPORTED. Other volumes are considered active. Only FROZEN expired volumes appear in the report. NetBackup deletes other expired volumes from the media catalog when backups are run. Expired, non-FROZEN volumes display if the report is run between the time the volumes expire and the time that the next backup is run. Click Help within the Tape Summary report window for a description of each column.

Tape Written report

The Tape Written report identifies the volumes that were used for backups within the specified time period. The Tape Written report does not display the volumes that were used for NetBackup offline, cold catalog backups. The report also does not display the volumes that were used for duplication if the original was created before the specified time period. Click Help within the Tape Written report window for a description of each column.

Tape Lists report

The Tape Lists report displays information for the volumes that have been allocated for backups for the selected media owner or media ID. This report does not show media for disk type storage units or for offline, cold catalog backups of the NetBackup catalogs.

For information about the backups that are saved to disk storage units, use the Images on Media report. To track the media that is used for offline, cold catalog backups, keep a hard copy record. Or, configure the Administrators E-mail Address Global Attribute host property. This host property causes NetBackup to send an email that indicates the status of each catalog backup and the media ID that was used.

Reports NetBackup report types

79

You can then print the email or save it on a disk other than the one that contains the catalogs. For more information, see Administrator email address on page 438. Click Help within the Tape Lists report window for a description of each column.

Disk Reports
The Disk Reports pertain to the information available about the images that are stored on disk media. The following sections describe the four types of tape reports:

Images on Disk report

The Images on Disk report generates a list of images that are expected to be present on the disk storage units, according to the NetBackup catalog. The report is a subset of the Images on Media report and displays only disk-specific columns. The report provides a summary of the storage unit contents. If a disk becomes bad or if a media server crashes, this report can let you know what data is lost. Click Help within the Images on Disk report window for a description of each column.

Disk Logs report

The Disk Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. The report is a subset of the Media Logs report and displays only disk-specific columns. Click Help within the Disk Logs report window for a description of each column.

Disk Storage Unit Status report

The Disk Storage Unit Status report displays the state of disk storage units in the current NetBackup configuration. For example, the total capacity and the used capacity of the disk storage unit. Storage units that reference disk pools do not display capacity values. These values are available by expanding Media and Device Management > Devices > Disk Pools. Storage units configured on 5.x media servers do not display capacity-related information. Click Help within the Disk Storage Unit Status report window for a description of each column.

80 Reports Using the Troubleshooter within reports

Disk Pool Status report

The Disk Pool Status report displays the state of disk pool storage units. This report displays only when an Enterprise Disk Option is installed. Click Help within the Disk Pool Status report window for a description of each column.

Using the Troubleshooter within reports

Use the Troubleshooter within Reports to find explanations and the corrective actions that are based on the NetBackup status code that the job returns. To run the Troubleshooter within reports 1 2 3 Run a report. Right-click a line in the report. Then, select Troubleshooter from the shortcut menu. The Troubleshooter dialog box appears, that states an explanation of the problem on the Problem tab. A recommended action appears on the Troubleshoot tab. Open the Troubleshooter at any time (Help > Troubleshooter), enter a status code, then click Lookup.

Chapter

Policies
Policies define the rules that NetBackup follows when clients are backed up. A backup policy can apply to one or more clients. Every client must be in at least one backup policy. The best approach to configure backup policies is to divide clients into groups according to the backup requirements and archive requirements. Then, create a policy for each group. This chapter contains the following sections:

Using the Policies utility on page 82 Configuring backup policies on page 82 Changing policies on page 84 Policy Attributes tab on page 87 Schedules tab on page 117 Schedule Attributes tab on page 118 Start Window tab on page 143 Exclude dates tab on page 145 Calendar schedule tab on page 146 Clients tab on page 159 Backup Selections tab on page 163 Rules to indicate paths in the backup selections list on page 170 Disaster Recovery tab on page 196 Creating a Vault policy on page 199 Performing manual backups on page 200 More about synthetic backups on page 201

82 Policies Using the Policies utility

Using the Policies utility

The Policies utility contains tools to configure and manage policies.

Tree and detail views

The center pane (All Policies), contains a hierarchical view of the policies on the master server currently under management. The Details pane displays a list of all policies with general attribute information for each policy. Double-click Summary of All Policies to expand or collapse the subnodes Attributes, Schedules, Clients, and Backup Selections. Select a subnode to display a list of all possible attributes for that node. Figure 4-1 NetBackup Policies utility

Menu bar Standard toolbar User toolbar Current master server

Tree view

Select a subnode from Summary of All Policies to display all possible node attributes in the right pane. For example, Schedules displays a list of all schedules.

Inactive policies appear in gray

Details pane

Policies menu bar

The options on the Policies menu bar are described in the online help.

Configuring backup policies

The easiest method to set up a backup policy is to use the Backup Policy Configuration Wizard. This wizard guides you through the setup process, which

Policies Configuring backup policies

83

simplifies the process as it automatically chooses the values that are good for most configurations. Note: The wizard cannot be used, however, to configure a calendar-based schedule. You can change the schedule to a calendar-based schedule after running the wizard. For more information, see Calendar schedule tab on page 146. To create a policy with the Backup Policy Configuration Wizard 1 2 In the NetBackup Administration Console, select Master Server or NetBackup Management. From the list of wizards in the Details pane, click Create a Backup Policy. Click Help on any wizard screen for assistance while running the wizard.

To create a policy without the Backup Policy Configuration Wizard 1 2 3 4 In the NetBackup Administration Console, expand NetBackup Management > Policies. Select Actions > New > Policy. Type a unique name for the new policy in the Add a New Policy dialog box. For more information, see NetBackup naming conventions on page 631. Click OK.

Note: If the schedule is to be used for a catalog archive, the policy must be named catarc. For more information on how to configure a policy to archive the catalog, see Creating a catalog archiving policy on page 319.

84 Policies Changing policies

Changing policies
Change policies only when no backup activity is expected for the affected policies and clients. Make adjustments before backups begin to ensure an orderly transition from one configuration to another. To add or change schedules in a policy 1 2 Expand NetBackup Management > Policies. Expand the policy name in the middle pane, then select Schedules.

Perform one of the following actions:

To add a schedule, select Actions > New > Schedule. The Add Schedule dialog appears. To change an existing schedule, double-click the schedule name in the Details pane. The Change Schedule dialog appears.

Complete the entries in the Attributes tab, Start Window tab, Exclude Dates tab, and Calendar Schedule tab (if displayed). Click OK. For more information, see Schedules tab on page 117.

To add or change clients in a policy 1 2 In the NetBackup Administration Console, expand NetBackup Management > Policies. Expand the policy name in the middle pane, then select Clients.

Policies Changing policies

85

Perform one of the following actions:

To add a new client, select Actions > New > Client. The Add Client dialog appears. To change an existing client, double-click the client name in the Details pane. The Change Client dialog appears.

Complete the entries in the Add Client or Change Client dialog. For more information, see To add a client to a policy on page 159.

To add or change backup selections in a policy Note: To configure a Vault policy, see To create a Vault policy on page 199. 1 2 3 In the NetBackup Administration Console, expand NetBackup Management > Policies. Expand the policy name in the middle pane, then select Backup Selections. Perform one of the following actions:

To add a new backup selection, select Actions > New > Backup Selection. The Add Backup Selection dialog appears.

To change an existing backup selection, double-click the backup selection in the Details pane.

Complete the entries in the Add Backup Selections or Change Backup Selections dialog. For information on how to specify file paths for clients, see Rules to indicate paths in the backup selections list on page 170.

86 Policies Changing policies

Add the new backup selection or make changes to an existing selection, then:

In the Add Backup Selection dialog, click Add. The new entry appears in the list. Define all new selections, then click OK. In the Change Backup Selection dialog, click OK.

To cut, copy, and paste items You can copy or cut and paste the following items:

Copy and paste entire policies Copy and paste schedules

To delete schedules, backup selections, or clients from a policy 1 2 3 4 In the NetBackup Administration Console, expand NetBackup Management > Policies. Expand the policy name in the middle pane, then select Attributes, Schedules, Backup Selections, or Clients. In the Details pane, select the item youd like to delete. Select Edit > Delete. A confirmation dialog appears. Click Yes.

Note: When a client is deleted from the client list, the NetBackup client software is not deleted or uninstalled from the client. Backups for the client can be recovered until the backups expire. Also, when a file is deleted from a backup selection list, the actual file is not deleted from the client.

Policies Policy Attributes tab

87

Policy Attributes tab

The settings on the Attributes tab determine the characteristics of all the backups that NetBackup performs according to the selected policy. The following items are a few of the attributes that are defined on the Policy Attributes tab:

Whether the selected policy is currently active or what date and time the policy goes into effect. The type of backup policy, which primarily defines the type of clients the policy backs up. The priority that NetBackup gives to the backups for the selected policy relative to other policies. The storage unit that NetBackup uses to back up the clients in the selected policy. Snapshot Client attributes, if Snapshot Client is installed.

88 Policies Policy Attributes tab

Figure 4-2

Policy Attributes tab

The following sections describe the settings on the Attributes tab. Policy attributes are configurable depending on the type of policy and the options that are installed.

Policy type
The Policy type attribute determines the purpose of the policy. Usually, the Policy type determines the type of clients that can be backed up by this policy. Not all policy types serve to back up up clients. (NBU-Catalog, for example.) Select the type of policy from the drop-down list. The Policy type of an existing policy may be changed. However, the existing schedules may become invalid for the new policy type. If the schedules become

Policies Policy Attributes tab

89

invalid, NetBackup displays an alert notice. NetBackup then either deletes the invalid schedules or changes the schedules to an equivalent type. Table 4-1 Policy type
DataStore

Policy types Description

A policy type that is reserved for use by Symantec or its partners to provide agents for new applications or databases. Use for the policies that contain only clients with the NetBackup for DB2 option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only clients with the NetBackup for Lotus Notes option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only clients with the NetBackup for MS-Exchange option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only clients with the NetBackup for MS-SQL Server option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only Windows 2000, XP, Windows Server 2003, or NetBackup 5.x NT clients. Use for hot catalog backup jobs. Allows for a catalog backup while other jobs are running. Use for the policies that contain only clients with the NetBackup for Teradata option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only clients with the NetBackup for NDMP option. This policy type is available only when the NetBackup NDMP is installed and licensed. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only NonTarget NetBackup Novell NetWare clients (this version uses a Microsoft Windows interface). Use for the policies that contain only clients with the NetBackup for Oracle option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain any combination of the following:

DB2

Lotus-Notes

MS-Exchange-Server

MS-SQL-Server

MS-Windows-NT*

NBU-Catalog NCR-Teradata

NDMP

NetWare

Oracle

Standard*

UNIX clients (including Mac OS X clients), except those covered by specific such as Oracle. NetBackup Novell NetWare clients that have the target version of NetBackup software.

Vault

Use as a policy type to schedule and run a Vault job. Available only when Vault is licensed.

Note: The following policy types apply only to UNIX clients.

90 Policies Policy Attributes tab

Table 4-1 Policy type

AFS

Policy types Description

Use for the policies that back up only AFS file systems on clients. See Using NetBackup with AFS, in the NetBackup Administrators Guide, Volume II for information on setting up these policies.

DataTools-SQLBackTrack

Use for the policies that contain only clients with the NetBackup for DataTools-SQL-BackTrack option. For information on setting up this policy type, see the guide for this option. Applies only to NetBackup Enterprise Server: Use for the policies that contain only NetBackup FlashBackup clients on UNIX. This policy is available only when the NetBackup Snapshot Client is installed. For information on setting up this policy type, see the Snapshot Client Administrators Guide.

FlashBackup

FlashBackupWindows

Applies only to NetBackup Enterprise Server: Use for the policies that contain only NetBackup FlashBackup-Windows clients on Windows. This policy is available only when the NetBackup Snapshot Client is installed. For information on setting up this policy type, see the NetBackup Snapshot Client Administrators Guide. Use for the policies that contain only clients with the NetBackup for Informix option. For information on setting up this policy type, see the guide for this option. Use to configure a policy for NetBackup for SharePoint Portal Server. Use for the policies that contain only clients with the NetBackup for SAP option. For information on setting up this policy type, see the guide for this option. Use for the policies that contain only clients with the NetBackup for Sybase option. For information on setting up this policy type, see the guide for this option.

Informix-On-BAR

MS-SharePoint SAP

Sybase

* Use the Standard or MS-Windows-NT policy to implement the following options: CheckPoint Restart for backups, Checkpoint Restart for restores, synthetic backups, or the Collect disaster recovery information for Bare Metal Restore option.

For more details on off-host backups, refer to the NetBackup Snapshot Client Administrators Guide.

Data classification
Select a Data Classification if you want the backup to go to a storage unit that stores backups of a particular classification. For example, a gold backup must go to a storage unit with a gold data classification.

Policies Policy Attributes tab

91

A Data Classification selection is optional. If no classification is indicated, the policy uses the storage units and groups that the Policy storage attribute indicates. If a data classification is selected, all the images that the policy creates are tagged with the classification ID. For more information on data classifications and lifecycles, see Data classification on page 262. For more information on creating data classifications, see Data Classification properties on page 407.

Policy storage
The Policy storage attribute specifies the storage destination for the policys data. Select the storage destination from the drop-down list. If configured, the drop-down list may contain storage units, storage lifecycle policies, and storage unit groups. If configured to do so, the selection of a storage unit or a storage lifecycle policy determines which type of disk staging is used for this policy. (See Staging backups to initial storage, then final storage on page 242.) The list includes only those lifecycles that are of the same data classification as the policy. For example, gold backup images cannot be sent to a silver storage lifecycle. Images that belong to a specific data classification cannot be sent to a storage lifecycle that does not have a classification. To select a data classification is optional. If Any Available is selected, NetBackup tries to store data on locally-attached storage units first. To force NetBackup to use only a locally-attached drive, select Must use local drive on the General Server Properties. (See Must use local drive on page 432.) If a local device is not found or if the Must use local drive attribute is not selected, NetBackup tries to find an available storage unit alphabetically. If Any Available is selected, NetBackup uses the first storage unit that meets the following requirements:

The storage unit must not be designated as On Demand Only The storage unit must have available drives The storage unit must have media available in the required volume pool

An exception is the case in which a client is also a media server with locally-attached storage units. The local storage units take precedence over the sequence that is based on alphabetical order. The storage unit that is selected on the Schedule tab, overrides the Policy storage attribute. (See Override policy storage selection on page 137.)

92 Policies Policy Attributes tab

Considerations before a storage destination is selected

If the site contains only one storage unit or if there is no storage unit preference:

Specify Any Available for the Policy storage attribute. Do not specify a storage unit at the schedule level. (See Override policy storage selection on page 137.) In this situation, do not configure all storage units to be On Demand Only. NetBackup may be unable to find an available storage unit for the backups. (See On demand only on page 235.)

If a specific storage unit is designated and the unit is unavailable, backups cannot run for those policies and the schedules that require the unit. If Any Available is selected, any Basic disk storage unit that is not assigned to a storage group is considered available for disk spanning. (See Allow backups to span disk on page 450.) To limit the storage units available to a policy, select a storage unit group that contains only the units you want the policy to use. Another method to limit the storage units available to a policy is the following: a Create a volume pool that contains the volumes that are available only to the specific storage units. (See Adding a new volume pool on page 539.) Note: If the Scratch pool option is enabled for the volume pool, any storage unit has access to the volumes in the volume pool. For this method to work, do not enable Scratch pool for the volume pool. b c In the policy, set Policy volume pool to the volume pool that is defined in the previous step. For all policies, set Policy storage attribute to Any Available.

A policy may specify a storage unit group. Make sure that one of the storage units within the group is set to On Demand Only to satisfy the policy requirement.

Concerning the Policy storage attribute and online catalog backups:

For online, hot catalog backups when a disk storage unit is indicated: increase the Maximum concurrent jobs setting on the storage unit. The increased setting ensures that the catalog backup can proceed while regular backup activity occurs.

Policies Policy Attributes tab

93

Online catalog backups must use media servers at version 6.0 or later to store catalog backup data. If the installation contains 5.x media servers hosting disk storage units, do not select Any Available for the destination Policy storage attribute. The 5.x media server may be selected and the backup would fail.

Policy volume pool

The Policy volume pool attribute specifies the default volume pool where the backups for the policy are stored. A volume pool is a group of media that is grouped together for use by a single application. The volume pool is protected from access by other applications and users. Select a volume pool name from the list of volume pools. Whenever a new volume is required, it is allocated from the volume pool indicated. The volume pool that is selected on the Schedule tab overrides the Policy volume pool setting. (See Override policy volume pool on page 137.) NetBackup creates four default volume pools:

None: The default pool for applications, other than NetBackup and Storage Migrator. DataStore: The default pool for DataStore. NetBackup: Unless otherwise specified in the policy, all backups use media from the NetBackup pool. One exception is the NBU-Catalog policy type (used for online, hot catalog backups) that selects the CatalogBackup volume pool by default. Offline, cold catalog backups use media from the NetBackup volume pool. CatalogBackup: This pool is selected by default for the NBU-Catalog policy type. It is used exclusively for online, hot catalog backups. Online, hot catalogs are directed to a single, dedicated pool to facilitate faster catalog restores.

Additional volume pools can be useful. Possible additional volume pools include the following:

A Scratch pool from which NetBackup can automatically transfer volumes when another volume pool does not have media available. An Auto volume pool, for use by automatic backups. A User volume pool, for use by user backups.

Media is assigned to the volume pools for Media Manager storage devices. Disk-type storage devices are not allocated to a volume pool. For information about how to create volume pools and how to add media to them, see Volume pool operations on page 538.

94 Policies Policy Attributes tab

Volume pool override example

Assume that you want all schedules but one to use the Backups pool. The exception is a user-archive schedule that requires the Archive pool. In the policy, set Policy volume pool to Backups. When you set up the schedules for the policy, set Override policy volume pool as follows:

For the schedules that use the Backups volume pool, clear Override policy volume pool. For the schedule that requires the Archive volume pool, select Override policy volume pool and specify Archive for the pool name.

Policies Policy Attributes tab

95

Checkpoint restart for backup jobs

The Take checkpoints every check box specifies whether NetBackup takes checkpoints during a backup job. Indicate how often the policy should take checkpoints. Checkpoints during a backup are beneficial if a backup fails. Without Take checkpoints every enabled, a failed backup restarts from the beginning of the job. By taking checkpoints periodically during the backup, NetBackup can retry a failed backup from the beginning of the last checkpoint rather than restart the entire job. Note that checkpoints cannot occur while a file is backed up. Checkpoints are saved at file boundaries, and point to the next file in the list. The Schedule backup attempts Global Attributes host property indicates the number of times that NetBackup tries a failed backup. (See Schedule backup attempts on page 435.) Policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support this policy attribute. To see if this feature is supported for a specific agent or option, refer to the manual for that agent or option. Note: Although NetWare clients can use the Standard policy type, checkpoint restart for backups is not supported on NetWare clients.

Checkpoint frequency
The checkpoint frequency indicates how often NetBackup takes a checkpoint during a backup. (Default: 15 minutes.) The administrator determines checkpoint frequency on a policy-by-policy basis. Balance more frequent checkpoints with the likelihood of time that is lost when a backup is resumed. If the frequency of checkpoints impacts performance, increase the time between checkpoints.

Checkpoint restart support

Multiple Copies: Checkpoint restart is supported for the policies that are configured to create multiple backup copies. (See Multiple copies on page 131.) The last failed copy that contains a checkpoint can be resumed if the following items are true:

A copy is configured to allow other copies to continue the job if the copy fails and subsequent checkpoints occur, and Take checkpoints every is selected for this policy.

96 Policies Policy Attributes tab

Veritas Volume Snapshot Provider (VSP): Checkpoint restart is supported for use with VSP. (See VSP (Volume Snapshot Provider) properties on page 485.) Snapshot Client: Checkpoint restart is supported for use with local or alternate client backups. However, other methods are not supported: Block Level Incremental Backups, Media Server Copy, Third-Party Copy Device, and Instant Recovery backups. Disk staging storage units (used in basic disk staging): Checkpoint restart is supported for use in Stage I of basic disk staging, during which data is backed up to disk. Checkpoint restart is unavailable in the Stage II storage unit policy of basic disk staging, during which data is relocated to another storage unit. For more information, see Staging backups to initial storage, then final storage on page 242. On Windows clients:

System State backups: No checkpoints are taken during the backup of a System State. Windows Disk-Image (raw) backups: No checkpoints are taken during a Windows disk-image backup. Single-instance Store (SIS): No checkpoints are taken for the remainder of the backup after NetBackup encounters single-instance store. When an incremental backup is resumed and completes successfully, the archive bits are cleared for the files that were backed up after the job resumed. However, the archive bits are not cleared for the files that were backed up before the resume. Since the archive bits remain, the files that were backed up before the resume are backed up again during the next incremental backup.

Synthetic backups: Checkpoint restart is not supported for use with synthetic backups in the current NetBackup release. Checkpoints are not taken for a user archive schedule. If the user archive is resumed, it restarts from the beginning. NetBackup decides when a new job should be started instead of resuming an incomplete job. NetBackup starts a new job in the following situations:

If a new job is due to run. If the time since the last incomplete backup has been longer than the shortest frequency in any schedule for the policy. If the time indicated by the Clean-up property, Move backup job from incomplete state to done state, has passed. For calendar scheduling, if another run day has arrived.

Policies Policy Attributes tab

97

Checkpoint restart for restore jobs

NetBackup automatically takes checkpoints during restore jobs by default. (See Checkpoint restart for restore jobs on page 683.) A backup that contains checkpoints does not need to be restored with a checkpointed restore job. Conversely, a restore job that contains checkpoints does not need to be restored from a checkpointed backup.

Limit jobs per policy

The Limit jobs per policy attribute limits the number of jobs that NetBackup performs concurrently when the policy is run. By default, the check box is clear, and NetBackup performs an unlimited number of backup jobs concurrently. Other resource settings can limit the number of jobs. A configuration can contain enough devices so that the number of concurrent backups affects performance. To specify a lower limit, select the check box and specify a value from 1 to 999. Figure 4-3 Limit jobs per policy attribute
Server Tape Drive 1

Client A

Client B

Tape Drive 2

Client A and Client B backups can occur concurrently and back up to different devices

Notes on the Limit jobs per policy attribute

The number of concurrent backup jobs that NetBackup can perform depends on the following:

Limit jobs per policy does not prevent concurrent jobs if the jobs are from different policies. For example, if three policies limit concurrent jobs to two, NetBackup can start two jobs from each policy. A total of six policies may be running at one time in this situation. Parent jobs do not count toward the limit. Only the children jobs count toward the Limit jobs per policy setting. The following jobs produce a parent

98 Policies Policy Attributes tab

job and children jobs: multistreamed jobs, catalog backups, Snapshot Client snapshots, or Bare Metal Restore jobs. (See Parent jobs on page 56.)

The number of storage devices available and multiplexing limits. To process more than one backup job at a time, the configuration must include one of the following:

Multiple storage units. A storage unit with enough drives to perform more than one backup at a time.

Storage units that are configured to multiplex. With removable media devices such as tape drives, the number of concurrent jobs depends on the total number of drives in the storage units. With disk storage, the storage device is defined as a file path and the available disk space determines how many paths are possible.

The server speed. Too many concurrent backups interfere with the performance of the server. The best number depends on the hardware, operating system, and applications that are running. The network load. The available bandwidth of the network determines how many backups can occur concurrently. If you encounter loading problems, consider multiple networks for backups. Or, configure the backup policy to use Compression. (See Compression on page 105.) When the client that is backed up is also a server, it is a special case. In this instance, the network load is not a factor because the network is not used. The load on the client and server, however, is still a factor. Multiplexing. If multiplexing is used, set Limit jobs per policy high enough to support the specified level of multiplexing. Lower values can limit multiplexing within a policy if jobs from different schedules exist within the policy. For example, Limit jobs per policy is set to two and an incremental backup schedule is due to run for four clients. Only two clients are backed up at one time, regardless of the multiplexing settings.

Job priority
The Job priority attribute specifies the priority that a policy has it competes with other policies for backup resources. To have a higher priority means that NetBackup assigns the first available drive to the first client in the policy with the highest priority.

Policies Policy Attributes tab

99

To set the priority, enter a number in the Job priority field (maximum 99999). The default for all policies is 0, the lowest priority possible. Any policy with a priority greater than zero has priority over the default setting.

Media owner
Active only for Media Manager type storage units or if the Policy storage attribute is Any Available. The Media Owner property specifies which media server or server group should own the media on which backup images for this policy are written. You can specify the following for Media Owner:

Any (default), allows NetBackup to choose the media owner. NetBackup chooses a media server or a server group (if one is configured). None 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. A server group. 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.

For more information about server groups and shared media, see Configuring server groups for media sharing on page 615.

Active. Go into effect at

To activate the policy, select the Active check box. The policy must be active for NetBackup to use the policy. The Go into effect at attribute specifies when the policy can begin to schedule backups. For example, if today is Monday and you enter Wednesday at 12:00 AM, the policy does not run until that time or later. Use the Go into effect at attribute to configure a series of policies in advance of when the policies need to become active. To deactivate a policy, clear the Active check box. Inactive policies appear in gray in the Administration Console. To resume backups, recheck the Active check box. Make sure that the Go into effect at date and time is set to the time that you want to resume backups. If the schedule is to be used for a catalog archive, the policy must not be active. The Active check box must be clear. For more information about how to configure a policy to archive the catalog, see Creating a catalog archiving policy on page 319.

100 Policies Policy Attributes tab

Backup network drives

The Backup network drives attribute is for use on single user systems, Win95, Win98, and ME. These operating systems are not supported with this version of NetBackup. The preferred method for backing up data from a machine other than a NetBackup client is to use UNC paths. UNC paths are more precise and indicate exactly what should be backed up. When Backup network drives or UNC paths are used, the network drives must be available to the service account that the NetBackup Client service logs into at startup. By default, the startup account is set to System. You must change this account on each Windows client that is backed up that contains data that is shared from another machine. Backup network drives must be checked when policies back up to CD ROM drives. For scheduled backups, the file list must indicate at least the first level of folders to be backed up. For example, D:\Folder1 instead of only D:\ Note: Mapped drive letters cannot be backed up. Drive letters do not appear in the Backup, Archive, and Restore console when backups are browsed.

Setup example with UNC paths

Assume that:

master1 is the NetBackup master server. win_client is a Windows NetBackup client. win_PC is a Windows computer (not necessarily a NetBackup client) and contains a shared folder named TestData.

To back up the folder TestData on win_PC through win_client, perform the following steps: 1 2 3 On the NetBackup master server, master1, create a policy for win_client. Add \\win_PC\TestData to the file list of the policy. This step is not necessary if the policy is only used for user-directed backups. On win_client, the NetBackup client: a Change the NetBackup Client Service on win_client to Start Up or Log On with the same account as the user that performs the backup. This user account must have read permissions for the share that is to be backed up. The account must have write permission to perform restores. Stop and start the NetBackup Client Service so the new account takes effect.

Policies Policy Attributes tab

101

4 5

To run a user backup, expand the Network node in the Backup, Archive, and Restore client interface to win_PC. Select TestData. Backups run as scheduled or when a manual backup is performed.

Example using the Backup network drives attribute

Assume that:

master1 is the NetBackup master server. win_client is a Windows NetBackup client. win_PC is a Windows computer (not necessarily a NetBackup client) and has a shared folder that is named share.

To back up the folder share on win_PC through win_client, perform the following steps: 1 2 On the NetBackup master server, master1, select Backup network drives in the policy to be used for the backup. On win_client, the NetBackup client: a Change the NetBackup Client Service on win_client to Start Up or Log On with the same account as the user that performs the backup. This user account must have read permissions for the share that is to be backed up. The account must have write permission to perform restores. Stop and start the NetBackup Client Service so the new account takes effect. Create a bpstart_notify.bat file that maps a drive on win_client to \\win_PC\share Enter the command: net use X: \\win_PC\share where X: is the mapped drive letter.

b c

3 4

To run a user backup, expand the Network node in the Backup, Archive, and Restore client interface to win_PC. Select TestData. Scheduled backups run as scheduled or when a manual backup is performed.

Follow NFS
The Follow NFS attribute specifies whether NetBackup is to back up or archive any NFS-mounted files that are named in the backup selection list. Or, by the user in the case of a user backup or archive. Clear the check box to prevent the backup or archive of NFS mounted files.

102 Policies Policy Attributes tab

Note: The Follow NFS attribute applies only to UNIX clients in certain policy types. NetBackup allows it to be selected in those instances only.

Notes on Follow NFS

The behavior of the Follow NFS attribute depends on the Cross mount points setting (explained later in this chapter). Follow NFS has no effect on raw partitions. The Network File Systems that are mounted in a raw partition are not backed up. Nor can you back up raw partitions from other machines that use NFS mounts to access the raw partitions. The devices are not accessible on other machines through NFS. Note: NetBackup does not support raw partition backups on unformatted partitions.

Follow NFS causes files in automounted file systems to be backed up. Automounted directories can be excluded while allowing backup of other NFS mounts. To do so, add an entry for the automounters mount directory to the exclude list on the client.

Advantages of the Follow NFS attribute

The Follow NFS setting eliminates the need to locate and log on to the systems where the files reside. If the files are mounted on the NetBackup client, you can back up, archive, and restore them by working from the NetBackup client. You must have the necessary permissions on the NFS mount. Use this capability to back up the systems that the NetBackup client software does not support.

Disadvantages of the Follow NFS attribute

Generally, do not back up NetBackup clients over NFS. Back up and archive files on the NFS server where the files physically reside. NFS backups have lower performance and sometimes encounter problems. Multiple backups can result in the following situations: if files are backed up at the host where they physically reside and by the local NFS clients that mount the files. If Follow NFS is selected, you may want to use the policy only for the files and clients that are backed up or archived over NFS.

Policies Policy Attributes tab

103

Note: If Follow NFS is not selected, the backup process reads the clients mount table and evaluates each item in the table. NetBackup resolves any links to the true path. NetBackup must resolve the links so it can accurately avoid backing up any files that reside on NFS-mounted file systems. If NetBackup cannot access a Network File System when it evaluates the mount table, it assumes that the file system is unavailable. (The default time to access the file system is five seconds.) To change the default, change the UNIX master server host property, NFS access timeout. (See NFS access timeout on page 483.)

Cross mount points

The Cross mount points attribute controls whether NetBackup crosses file system boundaries during a backup on UNIX clients.

Select Cross mount points to have NetBackup back up all files and directories in the selected path, regardless of the file system. For example, if you specify root (/) as the file path, NetBackup backs up root (/) and all files and directories under root in the tree. NetBackup specifically excludes mapped directories even if Follow NFS and Cross mount points are enabled. To back up mapped directories, include the directories in the file list. Clear Cross mount points for NetBackup to back up only the files that are in the same file system as the selected file path. Prohibit NetBackup from crossing mount points to back up root (/) without backing up all the file systems that are mounted on root. (For example, /usr and /home.) Do not cross mount points to back up a media server that uses mount points to any disk storage that contains backup images. If the policy crosses mount points, the NetBackup backup images that reside on that disk storage are backed up. The NetBackup BasicDisk disk type and the Enterprise Disk Option disk types use mount points for disk storage.

Note: The following information applies only to UNIX clients.

Notes on cross mount points

Cross mount points has no effect on UNIX raw partitions. If a raw partition is the root partition and contains mount points for other file systems, the other file systems are not backed up.

104 Policies Policy Attributes tab

Do not use Cross mount points in policies where the ALL_LOCAL_DRIVES directive is used in the backup selection list.

Cases that can require separate policies

In some cases, consider separate policies if a backup crosses mount points. For example, create a policy in which Cross mount points is not selected. The backup selection list contains only root (/). Only the root file system is backed up, and not the file systems that are mounted on it. Place other file systems in another policy or policies. To back up all the data on a client, create a policy in which Cross mount points is selected. In the backup selection list, include root (/).

How the Cross mount points attribute interacts with Follow NFS
To back up NFS-mounted files, select Follow NFS. Table 4-2 summarizes the behavior of Cross mount points and Follow NFS: Table 4-2 Cross mount point behavior Follow NFS
Disabled Enabled Disabled Enabled

Cross mount points

Disabled Disabled Enabled Enabled

Resulting behavior
No crossing of mount points (default). Back up NFS files if the file path is (or is part of) an NFS mount. Cross local mount points but not NFS mounts. Follow the specified path across mount points to back up files and directories (including NFS), regardless of the file system where they reside.

Note: NetBackup specifically excludes mapped directories even if Follow NFS and Cross mount points are enabled. To back up mapped directories, include the directories in the file list.

Cross mount point examples

The following examples assume that the client disks are partitioned as shown in Figure 4-4.

Policies Policy Attributes tab

105

Figure 4-4

Cross mount point example

/(root) /usr /home /home/njr /net /net/freddie /net/freddie/home NFS

d1

Disks on Local System

d2

d3

Disk on Remote System

Here, the client contains /, /usr, and /home in separate partitions on disk d1. Another file system named /home/njr exists on disk d2 and is mounted on /home. In addition, disk d3 contains a directory named /net/freddie/home that is NFS-mounted on /net/freddie.

Example 1
Assume that Cross mount points and Follow NFS are not selected. Assume that the backup selection list contains the following entries:
/ /usr /home

NetBackup considers only the directories and files that are in the same file system as the backup selection list entry it is processes. It does not back up /home/njr or /net/freddie/home.

Example 2
Assume that Cross mount points and Follow NFS are selected. Assume that the backup selection list contains only / . In this case, NetBackup backs up all the files and directories in the tree, including those under /home/njr and /net/freddie/home. To back up only /usr and individual files under /, leave / out of the list and separately list the files and directories you want to include. For example:
/usr /individual_files_under_root

Compression
The Compression attribute specifies that the backups use the software compression that is based on the policy. Select the check box to enable compression. (Default: no compression.)

106 Policies Policy Attributes tab

Advantages of the Compression attribute

Compression reduces the size of a backup by reducing the size of files in the backup. In turn, the smaller backup size decreases the amount of media that is required for storage. Compression also decreases the amount of data that travels over the network as well as the network load.

Disadvantages of the Compression attribute

Compression increases the overhead computing on the client and increases backup time due to the time required to compress the files. The lower transfer rate that is associated with compression on the client reduces the ability of some tape devices (notably 8mm) to stream data. The effects of the lower transfer rate causes additional wear on those devices. The savings in media and network resources, however, still make compression desirable unless total backup time or client computing resources become a problem. If total backup time is a problem, consider multiplexing. The NetBackup multiplexing feature backs up clients in parallel, reducing the total time to back them up. If compressed data is written to a storage unit that has single-instance store (SIS) capabilities, the storage unit may not be able to use data deduplication on the compressed or the encrypted data. In data deduplication, only one instance of the file is stored. Subsequent instances of the file reference the single file.

How much compression can be expected?

The degree to which a file can be compressed depends on the data type. A backup usually involves more than one type of data. Examples include stripped and unstripped binaries, ASCII, and the non-unique strings that repeat. Some data types are more favorable to compression. Note: When compression is not used, the server may receive more data than what exists on the client. The discrepancy is due to client disk fragmentation and the file headers that the client adds. (To tell how much space a file occupies, run the du command. To tell how much free disk space is available, run the df command.)

Table 4-3
Data types that compress well:

Compression specifications
Programs, ASCII files, and unstripped binaries (typically 40% of the original size).

Policies Policy Attributes tab

107

Table 4-3

Compression specifications
Files that are composed of the strings that repeat can sometimes be compressed to 1% of their original size. Stripped binaries (usually 60% of original size).

Best-case compression:

Data types that do not compress well: Worst-case compression:

Files that are already compressed become slightly larger if compressed again. On UNIX clients, if a compressed file has a unique file extension, exclude it from compression by adding it under the UNIX Client host properties. (See Do not compress files ending with on page 401.) File size has no effect on the amount of compression. However, it takes longer to compress many small files than a single large one.

Effect of file size:

Client resources that are Compression requires client computer processing unit time and as much memory as the required: administrator configures. Effect on client speed: Compression uses as much of the computer processing unit as available and affects other applications that require the computer processing unit. For fast CPUs, however, I/O rather than CPU speed is the limiting factor. NetBackup does not compress the following files:

Files that are not compressed:

Files that are equal to or less than 512 bytes, because that is the tar block size. On UNIX clients, the files that end with suffixes specified with the COMPRESS_SUFFIX =.suffix option in the bp.conf file. On UNIX clients, files with the following suffixes: .gz or GZ .hqx or .HQX .hqx.bin or .HQX.BIN .jpeg or .JPEG .jpg or .JPG .lha or .LHA .lzh .pak or .PAK .iff or .IFF .pit or .PIT .pit.bin or .PIT.BIN .scf or .SCF .sea or .SEA .sea.bin or .SEA.BIN .sit or .SIT .sit.bin or .SIT.bin .tiff or .TIFF .Y .zip or .ZIP .zom or .ZOM .zoo or .ZOO .z or .Z

.arc or .ARC .arj or .ARJ .au or .AU .cpt or .CPT .cpt.bin or .CPT.BIN .F .F3B .gif or .GIF

Encryption
The Encryption attribute determines whether the backup should be encrypted. When the server initiates the backup, it passes on the Encryption policy attribute to the client in the backup request.

108 Policies Policy Attributes tab

The client compares the Encryption policy attribute to the Encryption host properties for the client. If the encryption permissions for the client are set to REQUIRED or ALLOWED, the policy can encrypt the backups for that client. (See Encryption properties on page 409.) For additional encryption configuration information, see the NetBackup Security and Encryption Guide. Note: If encrypted data is written to a storage unit that has single-instance store (SIS) capabilities, the storage unit may not be able to use data deduplication on the compressed or the encrypted data.

Collect disaster recovery information for IDR

The Collect disaster recovery Information for Intelligent Disaster Recovery attribute specifies whether NetBackup collects the information that IDR requires to recover Windows clients. For more information, see Configuring NetBackup Policies for IDR in the NetBackup Administrators Guide, Volume II.

Collect disaster recovery information for Bare Metal Restore

The Collect disaster recovery Information for Bare Metal Restore attribute specifies whether the BMR client agent runs on each client. If the attribute is enabled, the BMR client agent runs before each backup to save the configuration information of the client. The Activity Monitor displays the activity as a job separate from the backup. Bare Metal Restore is a separately-priced option. For more information, see the Bare Metal Restore Administrators Guide for UNIX, Windows, and Linux. Only policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support this policy attribute. This attribute is enabled by default when an MS-Windows-NT or Standard policy is created on the master servers that are licensed for BMR.

Collect true image restore information

The Collect true image restore information attribute specifies whether the policy collects the information necessary to perform a true image restore. That is, to restore the directory contents to reflect what the directories had contained at the time of an incremental or a full backup. Files that were deleted before the backup are not restored.

Policies Policy Attributes tab

109

With the attribute enabled, a restore based on an incremental backup includes all files that were backed up since the last full backup. The restore also includes those files that were deleted at any time during that period. NetBackup starts to collect the true image restore information with the next full or incremental backup for the policy. The true image restore information is collected for each client regardless of whether any files were changed. NetBackup does not provide true image restores based on the time of a user backup or archive. However, NetBackup uses a user backup for a true image restore if the backup is more recent than the latest automatic full or incremental backup. To include the files that were moved, renamed, or newly installed in the directories, enable With move detection for the true image incremental backups. Note: Some options require that Collect true image restore information with move detection be enabled: - It must be enabled to create synthetic backups. (See Synthetic backup on page 128.) - It must be enabled to back up data to the NearStore disk storage units that use the File System Export option. (See Enable file system export on page 752.)

Collect true image restore information with move detection

The Collect true image restore information with move detection attribute specifies what true image incremental backups should include. Enable this attribute to include the files that were moved, renamed, or newly installed from a tar or a zip archive. (Depending on how the files were packaged and how they were installed, some newly installed files are not backed up by non-TIR incremental backups.) Without move detection, NetBackup skips the files and directories that were moved, renamed, or newly installed because their modification times are unchanged. With move detection, NetBackup compares path names and inode numbers with those from the previous full or incremental backup. If a name or an inode number is new or changed, the file or directory is backed up. Note: This attribute must be selected to create synthetic backups. The following examples show how move detection backs up the files that otherwise would not be backed up:

110 Policies Policy Attributes tab

A file named /home/pub/doc is moved to /home/spec/doc. Here, the modification time is unchanged but /home/spec/doc is new in the /home/spec/ directory and is backed up. A directory named /etc/security/dev is renamed as /etc/security/devices. Here, the modification time is unchanged but /etc/security/devices is a new directory and is backed up. A file named /home/pub/doc is installed when extracted from a UNIX tar file. Here, the modification time is before the time of the last backup but the doc is new in the /home/pub/ directory and is backed up. A file named docA is removed, then a file named docB is renamed as docA. Here, the new docA has the same name but since its inode number has changed, it is backed up.

NetBackup begins to collect the information that is required for move detection with the next full or incremental backup for the policy. This first backup after setting the attribute, always backs up all files, even if it is an incremental. Move detection consumes space on the client and the backup can fail if there is not enough disk space available.

What happens during true image restores

The following table lists the files that are backed up in the /home/abc/doc/ directory during a series of backups between 12/01/2007 and 12/04/2007. Assume that Collect true image restore information was turned on for the policy that performed the backups. Table 4-4 Day
12/01/2007 12/02/2007 12/03/2007 12/04/2007 12/04/2007

True image restore backup example Type of backup

Full Incremental Incremental User backup Incremental

Files that are backed up in /home/abc/doc

file1 file1 file1 file1 file1 file2 file2 file2 file2 file2 dirA/fileA dirA/fileA dirA/fileA dirA/fileA ------------dirB/fileB ------------------------------------------------file3 --------------------dirC/fileC ------------file4 file4

Note: Dashes ( ------ ) indicate that the file was deleted before this backup.

Assume that the 12/04/2007 version of the /home/abc/doc/ directory needs to be restored.

Policies Policy Attributes tab

111

After a regular restore, the restored directory contains all files and directories that ever existed in /home/abc/doc/ from 12/01/2007 (last full backup) through 12/04/2007:
file1 file2 dirA/fileA dirB/fileB file3 dirC/fileC file4

A true image restore of the 12/04/2007 backup creates a directory that contains only the files and directories that existed at the time of the incremental backup (12/04/2007):
file1 file2 file4

NetBackup does not restore any of the files that were deleted before the 12/04/2007 incremental backup. The restored directory does not include the dirA and dirC subdirectories, even though they were backed up on 12/04/2007 with a user backup. NetBackup did not restore these directories because they did not exist at the time of the incremental backup. The incremental backup was the reference for the true image restore.

Notes on true image restores and move detection

NetBackup collects additional information for the incremental backups that collect true image restore information. Policies that use move detection require even more space. Incremental backups are slower for a policy in which true image restore information is collected. Configure the period of time that NetBackup retains the true image restore information: set the Keep true image restoration (TIR) information property in the Clean-up properties dialog box. (See Keep true image restoration (TIR) information on page 384.) To restore a file system or disk with a true image restore, back up the directories with a policy that collects true image restore information. For true image restores, only directories can be listed and selected. In true image restore mode, the client interface does not display individual files. Refer to the online Help in the Backup, Archive, and Restore client interface for more information on true image restores.

112 Policies Policy Attributes tab

A true image restore preserves the files that are currently in the directory but were not present when the backup was completed. In the previous example, assume that you created a file named file5 after the incremental backup occurred on 12/04/2007, but before the restore. In this case, the contents of the directory after the restore is:
file1 file2 file4 file5

Allow multiple data streams

The Allow multiple data streams attribute specifies that NetBackup can divide automatic backups for each client into multiple jobs. The directives, scripts, or templates in the backup selection list specify whether each job can back up only a part of the backup selection list. Since the jobs are in separate data streams, they can occur concurrently.

The directives, scripts, or templates in the backup selection list determine the number of streams (backup jobs) that start for each client. The list also determines how the backup selection list is divided into separate streams. (See Backup selections list directives for multiple data streams on page 189.) The following settings determine the number of streams that can run concurrently:

Number of available storage units Multiplexing settings

Maximum jobs parameters For more information, see Adjusting multiple data streams on page 114. Multistreamed jobs consist of a parent job to perform stream discovery, and children jobs for each stream. In the Activity Monitor, the children jobs display the Job ID of the parent job. Parent jobs display a dash (-) in the Schedule column. Note: If this attribute is enabled, and a file system is in a clients exclude list, a NetBackup job appears in the Activity Monitor for the excluded file system. However, no files in the excluded file system are backed up by the job.

Policies Policy Attributes tab

113

When to use multiple data streams

Reduce backup time
Multiple data streams can reduce the backup time for large backups by splitting the backup into multiple streams. Use multiplexing, multiple drives, or a combination of the two to process the streams concurrently. In addition, configure the backup so each physical device on the client is backed up by a separate data stream that runs concurrently with streams from other devices. Note: For best performance, use only one data stream to back up each physical device on the client. Multiple concurrent streams from a single physical device can adversely affect backup times. The heads must move back and forth between tracks containing files for the respective streams. Figure 4-5 Multiple stream recommendations

Recommended for best performance Client Drive A Stream NetBackup Server Drive B Stream Back up each device with a separate stream that runs concurrently with streams from other devices. Then, multiplex the streams or send them to separate tapes.

Not recommended Client Drive A Stream Stream Stream Drive B Stream NetBackup Server

Multiple concurrent streams from a single device can adversely affect backup times.

Reduce retry time for backup failures

Because the backup streams are independent of one another, the use of multiple data streams can shorten the retry time in the event of a backup failure. A single failure only terminates a single stream. NetBackup can restart the failed stream without restarting the others.

114 Policies Policy Attributes tab

For example, assume the backup for a 10-gigabyte partition is split into 5 streams, each containing 2 gigabytes. If the last stream fails after writing 1.9 gigabytes (a total of 9.9 gigabytes is backed up), NetBackup retries only the last gigabyte stream. If the 10-gigabyte partition is backed up without multiple data streams and a failure occurs, the entire 10-gigabyte backup must be retried. The Schedule backup attempts property in the Global Attributes properties, applies to each stream. For example, if the Schedule backup attempts property is set to 3, NetBackup retries each stream a maximum of three times. (See Schedule backup attempts on page 435.) The Activity Monitor displays each stream as a separate job. Use the job details view to determine the files that are backed up by each of these jobs.

Reduce administrationmore backups with fewer policies

Use multiple data streams in a configuration that contains large file servers with many file systems and volumes. Multiple data streams provide more backups with fewer policies than are otherwise required.

Adjusting multiple data streams

The following two aspects of multiple data streams are adjustable:

The total number of streams. The backup selection list determines the total number of streams that are started. The NEW_STREAM directive lets you configure a fixed number of streams, or you can allow the client dynamically define the streams. For more information, see Backup selections list directives for multiple data streams on page 189.

Note: For best performance, use only one data stream to back up each physical device on the client. Multiple concurrent streams from a single physical device can adversely affect backup times. Backup times are affected because the device heads must move between tracks containing files for the respective streams.

The number of streams that can run concurrently. The following factors determine the number of streams that can run concurrently for a policy or client:

Storage unit and schedule multiplexing limit. (See Media multiplexing on page 141.) Number of the drives that are available.

Maximum concurrent jobs settings for the policy and client. Each storage unit and each schedule has a maximum multiplexing setting. The lower of the two settings is the limit for a specific schedule and storage

Policies Policy Attributes tab

115

unit. The maximum streams are limited to the sum of the multiplexing limits for all drives available in the storage unit and schedule combinations. For example, assume that two storage units have one drive in each. Multiplexing on storage unit 1 is set to 3 and multiplexing on storage unit 2 is set to 5. If multiplexing is set to 5 or greater in the schedules, then 8 streams can run concurrently. The maximum jobs settings also limit the maximum number of streams:

Maximum jobs per client (Host Properties > Master Servers > Global Attributes.) (See Maximum jobs per client on page 436.) Limit jobs per policy (policy attribute).

Maximum data streams (use Host Properties > Master Servers > Client Attributes or the bpclient command -max_jobs option). (See Maximum data streams on page 387.) The maximum job settings are interdependent as follows: If Maximum data streams is not set, the limit is either Maximum jobs per client or Limit jobs per policy, whichever is lower.

If Maximum data streams is set, NetBackup ignores Maximum jobs per client. Instead, NetBackup uses either Maximum data streams or Limit jobs per policy, whichever is lower. To specify a value for Maximum data streams with the bpclient command:

Determine if the client is in the client database on the master server by running the following command on one line: /usr/openv/netbackup/bin/admincmd/bpclient -client name -L If the client is not in the client database, run the following command on the master server on one line: /usr/openv/netbackup/bin/admincmd/bpclient -client name -add -max_jobs number If the client is in the client database, run the following command on one line: /usr/openv/netbackup/bin/admincmd/bpclient -client name -modify -max_jobs number

Enable document restore

The Enable document restore attribute is selectable for MS-SharePoint policy types. With this option enabled, users are able to restore specific files from the full backups that are based on this policy. (For example, .doc, .xls, .pdf, or .txt

116 Policies Policy Attributes tab

files on NetBackup 6.5 clients.) For more information, see the NetBackup for Microsoft SharePoint Portal Server 2003 Administrators Guide. Document-level restores can be performed only if the backup was written to a disk storage unit.

Keyword phrase
The Keyword phrase attribute is a phrase that NetBackup associates with all backups or archives based on the policy. Note: Only the Windows and UNIX client interfaces support keyword phrases. You can use the same keyword phrase for more than one policy. The same phrase for multiple policies makes it possible to link backups from related policies. For example, use the keyword phrase legal department documents, for backups of multiple clients that require separate policies, but contain similar types of data. The phrase can be a maximum of 128 characters in length. All printable characters are permitted including spaces and periods. (Default: no keyword phrase.) Clients can also specify a keyword phrase for a user backup or archive. A user keyword phrase overrides the policy phrase.

Snapshot Client options

To use the Snapshot Client options, you must install and license the Snapshot Client option. For more information see the NetBackup Snapshot Client Administrators Guide.

Policies Schedules tab

117

Schedules tab
The schedules that are defined on the Schedules tab determine when backups occur for the policy that is selected. Each schedule also includes various criteria, such as how long to retain the backups. NetBackup has two categories of schedules:

Automatic schedules back up the items that are listed in the backup selection list on all clients in the policy. The items are backed up according to the timetables that are set up in the schedules. User schedules specify the times when users can start user backups and archives from the clients. A user archive is a special type of backup that deletes the files from the user disk if the backup is successful. An archive is useful to free disk space while keeping a copy for future use. Policy Schedules tab

Figure 4-6

From the policy Schedules tab, perform the following tasks:

To create a new schedule click New. To edit a schedule, select the schedule and click Change. To delete a schedule, select the schedule and click Delete. Attributes tab: Schedule the time and frequency at which a task runs, along with other scheduled attributes. Start Window tab: Schedule the time of each day that a task runs. Exclude Dates tab: Indicate the dates that a task should not run. Calendar Schedule tab: Schedule the run days for a task by indicating specific dates, recurring weekdays, recurring days of the month. (This tab appears only when Calendar is selected as the Schedule type.)

Schedule attributes appear on four tabs:

118 Policies Schedule Attributes tab

To create or change schedules 1 2 3 4 5 6 In the NetBackup Administration Console, expand NetBackup Management > Policies. In the middle pane, double-click the policy name to which a schedule is to be added or changed. The Change Policy dialog appears. Select the Schedules tab. The tab displays the properties of existing schedules. The title bar displays the name of the current policy. Select the schedule to change and click Change. The Change Schedule dialog appears. It contains the Attributes, Start Window, and optionally, the Exclude Dates and Calendar Schedule tabs. Make the changes and click OK.

Note: For more information on how to change existing policies, see To add or change schedules in a policy on page 84.

Schedule Attributes tab

The following sections describe the settings on the Attributes tab for schedules. Schedule attributes include the backup type (different from the Policy Type), when the backup can occur, and how long the backup image is retained.

Name
Specify a name for the schedule by typing it in the Name field. For more information, see NetBackup naming conventions on page 631.

Policies Schedule Attributes tab

119

Figure 4-7

Schedule Attributes tab

The schedule name appears on screens and messages about the schedule. If the schedule is a relocation schedule, created as part of a basic disk staging storage unit, the schedule name cannot be changed. The name defaults to the name of the storage unit. For more information on basic disk staging storage units, see Staging backups to initial storage, then final storage on page 242.

Type of backup
The Type of backup specifies the type of backup that the schedule controls. Select a backup type from the drop-down list. The list displays only the backup types that apply to the policy being configured. If the schedule is a relocation schedule, created as part of a basic disk staging storage unit, no backup type selection is needed. The following sections describe the various backup types.

Full backup
A full backup backs up all of the files that are specified in the backup selections list for the policy. The files are backed up, regardless of when the files were last modified or backed up. Full backups occur automatically according to schedule criteria. If you run incremental backups, you must also schedule a full backup to perform a complete restore. If you configure a policy for a raw partition backup (formatted partitions only), select Full Backup.

120 Policies Schedule Attributes tab

Cumulative incremental backup

A cumulative incremental backup backs up the files that are specified in the backup selections list that have changed since the last full backup. All files are backed up if no previous backup has been done. Cumulative incremental backups occur automatically according to schedule criteria. A complete restore requires the last full backup and the last cumulative incremental backup. For more information on incremental backups, see More on incremental backups on page 122. Note: Do not combine differential incremental backups and cumulative incremental backups within the same Windows policy when the incremental backups are based on archive bit (default). For more information, see Time overlap on page 405.

Differential incremental backup

A differential incremental backup backs up the files that have changed since the last successful incremental (differential or cumulative) or full backup. All files are backed up if no previous backup has been done. Differential incremental backups occur automatically according to schedule criteria. A complete restore requires the last full backup, the last cumulative incremental, and all differential incremental backups that have occurred since the last full backup.

User backup
A user initiates a user backup through the Backup, Archive, and Restore client interface. A user backup backs up all files that the user specifies. Users can start backups only during the times that are allowed on the schedule Start Window tab. If the schedule is to be used for a catalog archive, User Backup must be selected for the backup type. For more information on how to configure a policy to archive the catalog, see Creating a catalog archiving policy on page 319.

User archive
A user initiates a user archive through the Backup, Archive, and Restore client interface. A user archive backup first backs up the files that the user indicates. Then it deletes the files from the local disk if the backup is successful. Archive backups free local disk space while retaining a copy for future use. The copy is kept until the retention period expires. Users can start archives only during the times that are specified in the schedule Start Window tab.

Policies Schedule Attributes tab

121

Caution: The NetBackup administrator should make sure that a full backup of the client exists before a user is allowed to archive files from the client.

Application backup
An application backup is a backup type that applies to all database agent clients. For more information on how to configure schedules for this type of backup, see the NetBackup guide that came with the product.

Automatic backup
An automatic backup is a backup type for all database agent clients, except NetBackup for Informix and Oracle. For more information on how to configure schedules for this type of backup, see the NetBackup guide for the database product.

Automatic incremental backup

An automatic incremental backup applies only to NetBackup for Informix clients. For more information on how to configure schedules for this type of backup, see the NetBackup for Informix Administrators Guide.

Automatic cumulative incremental backup

An automatic cumulative incremental backup applies only to NetBackup for Oracle clients. For more information on how to configure schedules for this type of backup, see the NetBackup for Oracle Administrators Guide.

Automatic differential incremental backup

An automatic differential incremental backup applies only to NetBackup for Oracle clients. For more information on how to configure schedules for this type of backup, see the NetBackup for Oracle Administrators Guide.

Automatic full backup

An automatic full backup applies only to NetBackup for Informix and for Oracle clients. For more information on how to configure schedules for this type of backup, see the NetBackup for Informix Administrators Guide or the NetBackup for Oracle Administrators Guide.

122 Policies Schedule Attributes tab

Automatic Vault
An automatic Vault session applies only to Vault policies. The option does not run a backup, but instead runs the command that is specified in the Vault policys backup selections list. In this way it starts an automatic, scheduled vault session or vault eject operation. Available only when Vault is licensed. For more information on how to configure a Vault policy, see Creating a Vault policy on page 199.

Vault catalog backup

Use when the schedule is for a catalog backup policy to be used by Vault. Available only when Vault is licensed. If the schedule is a Vault Catalog Backup type, one of two schedule attribute combinations must be configured or the schedule cannot be saved:

Check and configure Multiple copies, or Check Override policy storage selection, Override policy volume pool and specify the Retention.

Note: The selected storage unit selection should not be Any Available.

More on incremental backups

The following examples show how data is included in a series of full and incremental backups.

Full and differential incremental example

A differential incremental backup backs up data that has changed since the last full or differential incremental backup. The following figure shows how data is included in a series of full and differential incremental backups between January 1 and January 4.
Jan 1 Full backup Diff. incremental Diff. incremental Diff. incremental Recovery = Jan 1 (full) + Jan 2 (incr) + Jan 3 (incr) + Jan 4 (incr) Jan 2 Jan 3 Jan 4 disk fails

The January 1 full backup includes all files and directories in the policy backup selections list. The subsequent differential incremental backups include only

Policies Schedule Attributes tab

123

the data that changed since the last full or differential incremental backup. If the disk fails sometime on January 4 (after the backup), the full backup and all three of the incremental backups are required for the recovery.

Full and cumulative incremental example

A cumulative incremental backup backs up data that has changed since the last full backup. The following example shows how data is included in a series of full and cumulative incremental backups between January 1 and January 4. The January 1 full backup includes all files and directories in the policy backup selections list. Each of the cumulative incremental backups include the data that has changed since the last full backup. If the disk fails sometime on January 4 (after the backup), the full backup and the last cumulative incremental backup are required for the recovery.
Jan 1 Full backup Cum. incremental Cumulative incremental Cumulative incremental Recovery = Jan 1 (full) + Jan 4 (cumulative incremental) Jan 2 Jan 3 Jan 4 disk fails

Table 4-5 Type

Differential

Retention requirements for differential and cumulative incremental backups Retention requirement
Longer

Comments
To restore all files requires the last full backup and all the differential incremental backups that have occurred since the last full backup. Therefore, all the differentials must be kept until the next full backup occurs. Each cumulative incremental backup contains all the changes that have occurred since the last full backup. Therefore, a complete restore requires only the most recent cumulative incremental in addition to the full backup.

Cumulative

Shorter

Table 4-6 Type

Differential

Relative backup and restore times for differential and cumulative incremental backups Backup time
Shorter

Restore time
Longer

Comments
Less data in each backup, but all differential incremental backups are required since the last full backup for a restore. This results in a longer restore time.

124 Policies Schedule Attributes tab

Table 4-6 Type

Cumulative

Relative backup and restore times for differential and cumulative incremental backups Backup time
Longer

Restore time
Shorter

Comments
More data in each backup, but only the last cumulative incremental is required for a complete restore (in addition to the full).

A combination of cumulative and differential incremental backups can be used together to get the advantages of both methods. For example, assume a set of schedules with the following backup frequencies and retention periods (notice that the differential incremental backups occur more often.) Table 4-7 Backup type
Full Cumulative incremental Differential incremental

Example frequencies and retention periods Frequency

6 days 2 days 1 day

Retention period
2 weeks 4 days 2 days

The following set of schedules result in the following series of backups:

Day 1
Full

Day 2
Differential

Day 3
Cumulative

Day 4
Differential

Day 5
Cumulative

Day 6
Differential

Day 7
Full

Day 8
Differential

Notes about example:

Every other day a differential incremental backup occurs, which usually has a minimum backup time. On alternate days, a cumulative incremental backup occurs, which requires more time than the differential backup, but not as much time as a full backup. The differential backup can now be expired. To recover all files may require (at most), two incremental backups in addition to the most recent full backup. The combination of backups usually means less restore time than if all differential incremental backups were used. The full backups can be done less often if the amount of data being backed up by the incremental backups is small.

Policies Schedule Attributes tab

125

Determining files due for backup on Windows clients

On Windows clients, NetBackup performs the incremental backups of files that are based on the Perform incrementals based on archive bit setting. This setting is found in the Backup, Archive, and Restore client interface, under File > NetBackup Client Properties, on the General tab. If Perform incrementals based on archive bit is enabled, incremental backups for this client are based on the state of the archive bit of each file. The operating system sets the bit whenever a file is changed and it remains set until cleared by NetBackup. The conditions under which NetBackup clears the bit depend on the type of backup being performed.

For a full backup, NetBackup backs up files regardless of the state of their archive bit. After a full backup, the archive bit is always cleared. For a differential incremental backup, NetBackup backs up the files that have the archive bit set and have therefore been changed. When the client receives a response from the server that indicates that the backup was successful (or partially successful) the archive bits are cleared. The clear archive bit allows the next differential incremental to back up only the files that have changed since the previous full or differential incremental backup. For a cumulative incremental backup, NetBackup backs up the files that have the archive bit set. However, NetBackup does not clear the archive bits after the backup. Without a clear archive bit, the next cumulative incremental backup backs up changed files and the files that were in the cumulative incremental backup.

If Perform incrementals based on archive bit is disabled, NetBackup includes a file in an incremental backup only if the datetime stamp of the file has been changed since the last backup. The datetime stamp indicates when the file was last backed up.

For a full backup, NetBackup backs up files regardless of the datetime stamp. For a differential incremental backup, NetBackup compares the datetime stamp of the file against the last full or incremental backup. For a cumulative incremental backup, NetBackup compares the datetime stamp of the file against the last full backup.

If files are installed or copied from another computer, the new files retain the datetime stamp of the originals. If the original date is before the last backup date, the new files are not be backed up until the next full backup.

126 Policies Schedule Attributes tab

Determining files due for backup on UNIX clients

Incremental backups on UNIX clients look at all files and directories to determine if a backup is due based on a reference date. (That is, back up all the files that have changed since date_x). UNIX files and directories have three times that are associated with them:

mtime: The file modification time. The file system updates the mtime for a file or directory each time the file is modified. An application can save the mtime of the file before modifying it. The application then resets it with the utime(2) system call. atime: The file access time. The file system updates the atime for a file or directory each time the file is accessed (read or write). An application can save the atime of the file before accessing it. The application then resets it with the utime(2) system call. ctime: The inode change time. The ctime for a file or directory is updated each time the file or directorys inode is changed. (For example, changes due to permissions, ownership, and link-counts changes.) The ctime for a file or directory cannot be saved before and reset after a change. The ctime of a file or directory is changed when the mtime and atime (changed with the utime(2) system call) is reset.

UNIX man pages contain a definition of these attributes. When NetBackup reads the data for a file that is included in a backup, it does not affect the file modification time. It does affect the access time of the file. For this reason, NetBackup saves the atime and mtime of the file before it reads the file. Then NetBackup resets the atime and mtime with the utime(2) system call. NetBackup does not cause problems for storage migration products or the administrator scripts that use file access times (atime) as criteria for their operations. While this benefit is obvious, a side effect is that it does update the ctime of the file. Customers can configure NetBackup so that it does not reset the access time of the file after it reads a file. Customers can choose to have NetBackup use the ctime and the mtime of the file, to determine what files to include in an incremental backup. Normally, these two options are used together, but there may be some sites that want to use one without the other. By default, NetBackup uses only the mtime of the file to determine what files and directories to back up. When a file is moved from one location to another, the ctime of the file changes, but the mtime remains unchanged. If NetBackup uses only the mtime to determine the files that are due during an incremental backup, it does not detect these moved files. For sites where using the mtime might create a problem, use the ctime to determine files due to be included in an incremental

Policies Schedule Attributes tab

127

backup. The ctime is used if the bp.conf file contains the USE_CTIME_FOR_INCREMENTALS and DO_NOT_RESET_FILE_ACCESS_TIME entries. When a directory is moved from one location to another, the ctime of the directory changes, but the mtime remains unchanged. Neither the mtime nor the ctime are changed for the files or directories within the moved directory. No reliable method using file timestamps can determine that files within a moved directory need to be included in an incremental backup. In either case, these moved files and directories are included in subsequent full backups.

128 Policies Schedule Attributes tab

Synthetic backup
A synthetic full or synthetic cumulative incremental backup is a backup assembled from previous backups. The backups include one previous, traditional full backup, and subsequent differential backups and/or a cumulative incremental backup. (A traditional full backup means a non-synthesized, full backup.) A client can then use the synthesized backup to restore files and directories in the same way that a client restores from a traditional backup. Synthetic backups can be written to tape or to disk storage units, or a combination of both. For more information on synthetic backups, see More about synthetic backups on page 201.

Calendar schedule type

Calendar-based schedules allow administrators to select specific days to run a policy. Select the Calendar schedule attribute for the Calendar Schedule tab to appear in the Change Schedule dialog. For more information, see Calendar schedule tab on page 146. A calendar-based relocation schedule determines the days that images are swept from the disk staging storage unit to the final destination storage unit. (A relocation schedule is created as part of a basic disk staging storage unit configuration.) Note: A policy can contain more than one schedule. Symantec recommends, however, that calendar-based and frequency-based schedule types are not mixed within the same policy. Under some conditions, schedule types that are combined in one policy can cause unexpected results. For details on how calendar-based scheduling works with time windows, see How calendar scheduling interacts with daily windows on page 149.

Retries allowed after runday

Enable Retries allowed after runday to have NetBackup attempt to complete this schedule until the backup is successful. With this attribute enabled, the schedule attempts to do run, even after a specified run day.

Frequency schedule type

Use the Frequency attribute to specify how much time must elapse between the successful completion of a scheduled task and the next attempt.

Policies Schedule Attributes tab

129

For example, assume that a schedule is set up for a full backup with a frequency of one week. If NetBackup successfully completes a full backup for all clients on Monday, it does not attempt another backup for this schedule until the following Monday. A frequency-based relocation schedule determines how often images are swept from the basic disk staging storage unit to the final destination storage unit. (A relocation schedule is created as part of a basic disk staging storage unit configuration.) To set the frequency, select a frequency value from the drop-down list. Select a Frequency of hours, days, or weeks. Note: Frequency does not apply to user schedules because the user can perform a backup or archive whenever the time window is open.

Note: A policy can contain more than one schedule. Symantec recommends, however, that calendar-based and frequency-based schedule types are not mixed within the same policy. Under some conditions, schedule types that are combined in one policy can cause unexpected results.

Guidelines for setting backup frequency

To determine backup frequency, consider how often data changes. For example, determine if files change several times a day, daily, weekly, or monthly. Typically, sites perform daily backups to preserve daily work. Daily backups ensure that only one days work is lost in case of a disk failure. More frequent backups are necessary when data changes many times during the day and these changes are important and difficult to reconstruct. Daily backups are usually incremental backups that record the changes since the last incremental or full backup. Incremental backups conserve resources because they use less storage and take less time to perform than full backups. Full backups usually occur less frequently than incremental backups but should occur often enough to avoid accumulating consecutive incremental backups. A large number of incremental backups between full backups increases the time it takes to restore a file. The time increases because of the effort that is required to merge the incremental backups when files and directories upon restore. Consider the following when setting the frequency for full backups:

Extend the time between full backups for the files that seldom change. A longer frequency uses fewer system resources. It also does not significantly increase recovery time because the incremental backups between full backups are smaller.

130 Policies Schedule Attributes tab

Shorter the time between full backups for the files that change frequently. A shorter frequency decreases restore time. A shorter time between full backups can also use fewer resources: it reduces the cumulative effect of the longer incremental backups that are necessary to keep up with frequent changes in the files.

To achieve the most efficient use of resources, ensure that most of the files in a given policy change at about the same rate. For example, assume that half of the files in a policy selection list change frequently enough to require a full backup every week. However, the remaining files seldom change and require monthly full backups only. If all the files are in the same policy, full backups are performed weekly on all the files. This wastes system resources because half the files need full backups only once a month. A better approach is to divide the backups into two policies, each with the appropriate backup schedule, or to use synthetic backups.

Backup frequency determines schedule priority

If more than one automatic schedule is due for a client within a policy, the backup frequency determines the schedule that NetBackup uses:

Jobs from the schedule with the lower frequency (longer period between backups) always have higher priority. For example, a schedule with a backup frequency of one year has priority over a schedule with a backup frequency of one month. If NetBackup encounters a backup policy with two schedules (one full, one incremental) that are each due to run:

if each is within the defined time window, and

if each is configured with the same frequency value, the schedule that is first alphabetically runs first. For example, NetBackup prioritizes the following three schedules in the following order: 1 2 3 monthly_full (frequency is one month) weekly_full (frequency is two weeks) daily_incremental (frequency is one week)

If all three schedules are due for a client, NetBackup adds the job for the monthly full to the worklist and skips the other two. How NetBackup prioritizes each backup job that it adds to its worklist is explained in Chapter 3 of the NetBackup Administrators Guide, Volume II.

Policies Schedule Attributes tab

131

Instant recovery
The Instant recovery options are available under the following conditions:

The Snapshot Client option is licensed and installed. Refer to the NetBackup Snapshot Client Administrators Guide. Perform snapshot backups is selected. Retain snapshots for Instant Recovery is selected.

Snapshots and copy snapshots to a storage unit

When this attribute is enabled, the snapshot persists on the client volume with a backup copy made to the storage unit on the media server.

Snapshots only
With this attribute is enabled, the snapshot is not backed up to tape or to other storage. NetBackup creates a snapshot on disk only. This option is required for the NAS_Snapshot method. The snapshot is created on the same device as the one that contains the original data if it uses VxFS_Checkpoint method or is vxvm space-optimized. In this case, another policy can be used to back up the data to a separate device. With this attribute enabled, transaction logs are not be truncated at the end of the backup.

Multiple copies
With the Multiple copies attribute enabled, NetBackup can create up to four copies of a backup simultaneously. The storage units must be on the same media server with sufficient resources available for each copy. For example, to create four copies simultaneously in a Media Manager storage unit, the unit needs four tape drives. (This option is sometimes referred to as Inline Copy.) The Maximum backup copies property specifies the total number of backup copies that may exist in the NetBackup catalog (2 through 10). NetBackup creates the number of copies that is specified under Multiple copies, or the number that the Maximum backup copies property specifies, whichever is fewer. For more information, see Maximum backup copies on page 437. To create more than four copies, additional copies may be created at a later time using duplication. The storage units that are used for multiple copies must be configured to allow a sufficient number of concurrent jobs to support the concurrent copies. (The pertinent storage unit settings are Maximum concurrent jobs and Maximum concurrent write drives.)

132 Policies Schedule Attributes tab

If multiple original images are created simultaneously, the backup time that is required may be longer than for one copy. Also, if both Media Manager and disk storage units are specified, the duration of disk write operations match that of slower removable media write operations. Note: The Multiple copies option does not support the following storage types: third-party copies or optical devices. Also, Multiple copies does not support the storage units that use a QIC (quarter-inch cartridge) drive type.

Multiple copies and disk staging storage units

Multiple copies can also be configured for a relocation schedule, created as part of basic disk staging storage unit configuration. The Maximum backup copies Global host property must be set to include an additional copy beyond the number of copies to be created in the Multiple Copies dialog. For example, to create four copies in the Multiple Copies dialog, the Maximum backup copies property must be set to five or more. Since NetBackup eventually relocates a backup from the initial, temporary staging storage unit to a final destination, NetBackup considers this to be one copy. NetBackup automatically counts this copy against the Maximum backup copies value.

Multiple copies and storage lifecycle policies

If the schedule is configured to create multiple copies, NetBackup does not permit any of the destinations to be a lifecycle. For example, one backup job cannot send one copy of the original backup to a lifecycle and another copy of the backup to another location (storage unit, storage unit group, or a lifecycle).

Policies Schedule Attributes tab

133

Multiple copies configuration

To configure a schedule to create multiple copies 1 Expand NetBackup Management > Policies. Double-click an existing policy or select Edit > New to create a new policy.

2 3 4

Select the Schedules tab. Double-click an existing schedule or click New to create a new schedule. In the Attributes tab, select Multiple copies, then click Configure. The Configure Multiple Copies dialog appears. Note: The Multiple Copies option may not be enabled for selection. It may be disabled if the destination for this policy is a storage lifecycle policy. (The destination selection is on the policy Attributes tab.) If the lifecycle has multiple destinations configured, that implies a multiple copies operation. NetBackup does not allow the two methods for created multiple copies to be enabled at the same time.

In the Copies field, specify the number of copies to create simultaneously. The maximum is four, or the number of copies that the Maximum backup

134 Policies Schedule Attributes tab

copies setting specifies, whichever is fewer. For more information, see Maximum backup copies on page 437.

Copy 1 is the primary copy. If Copy 1 fails, the first successful copy is the primary copy. Note: To configure multiple copies as part of a relocation schedule for a basic disk staging storage unit, set the Maximum backup copies Global host property to include an additional copy beyond the number of copies to be created in the Multiple Copies dialog. For example, to create four copies in the Multiple Copies dialog, the Maximum backup copies property must be set to five or more. For more information, see Multiple copies and disk staging storage units on page 132. 6 7 Specify the priority that the duplication job has compared to other jobs in the queue (0 to 99999). Specify the storage unit where each copy is stored. Select Any_Available to allow NetBackup to select the storage unit at runtime. If a Media Manager storage unit contains multiple drives, the storage unit can be used for both the original image and the copies. Specify the volume pool where each copy is stored. Select the retention level for each copy. For more information, see Retention on page 138.

8 9

10 Select what should happen to the copy in the event that the copy does not complete. Select whether the entire job should fail (fail all copies), or whether the remaining copies should continue. If a copy is configured to allow other copies to continue, and if Checkpoint restart is selected for this policy, only the last failed copy that contains a checkpoint can be resumed. 11 For tape media, specify who should own the media onto which NetBackup writes the images:

Policies Schedule Attributes tab

135

Any lets NetBackup choose the media owner, either a media server or server group. None specifies that the media server that writes to the media owns the media. No media server is specified explicitly, but you want a media server to own the media. A server group. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written. All media server groups configured in the NetBackup environment appear in the drop-down list.

Note: These settings do not affect images residing on disk. Images on shared disk are not owned by any one media server. Any media server with access to the shared pool of disk can access the images. 12 Click OK, until the policy is saved. To configure a basic disk staging relocation schedule to create multiple copies 1 Expand NetBackup Management > Storage Units.

Double-click an existing basic disk staging storage unit, or Select Actions > New > New Storage Unit to create a new basic disk staging storage unit. To create a new basic disk staging storage unit, select the Temporary staging area checkbox and configure the other storage unit selections.

2 3

Click the Staging Schedule button. The Disk Staging dialog appears. In the Attributes tab, specify the priority that NetBackup should assign to the duplication jobs have compared to other jobs in the queue. Range: 0 (default) to 99999 (highest priority). Select a schedule type and schedule when the policy should run. Select whether to use an alternate read server by checking Use alternate read server. The alternate server that is indicated is allowed to read a backup image originally written by a different media server. Select Multiple copies, then click Configure. The Configure Multiple Copies dialog appears. In the Copies field, specify the number of copies to create simultaneously. Copy 1 is the primary copy. If Copy 1 fails, the first successful copy is the primary copy. The Maximum backup copies Global host property must include an additional copy beyond the number of copies indicated in the Copies field.

4 5

6 7

136 Policies Schedule Attributes tab

For example, to create four copies in the Multiple Copies dialog, the Maximum backup copies property must be set to five or more. For more information, see Multiple copies and disk staging storage units on page 132. 8 Specify the storage unit where each copy is stored. If a Media Manager storage unit has multiple drives, it can be used for both the source and the destination. Specify the volume pool where each copy is stored.

10 Select the retention level for each copy. For more information, see Retention on page 138. 11 Select what should happen in the event that the copy does not complete. Select whether the entire job should fail, or whether the remaining copies should continue. Click OK. If:

a copy is configured to allow other copies to continue, and

Checkpoint restart is selected for this policy, then only the last failed copy that contains a checkpoint can be resumed. 12 For tape media, specify who should own the media onto which NetBackup writes the images:

Any lets NetBackup choose the media owner, either a media server or server group. None specifies that the media server that writes to the media owns the media. No media server is specified explicitly, but you want a media server to own the media. A server group. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written. All media server groups configured in the NetBackup environment appear in the drop-down list.

Note: These settings do not affect images residing on disk. Images on shared disk are not owned by any one media server. Any media server with access to the shared pool of disk can access the images.

Restoring from a specific backup copy

Usually NetBackup restores from the primary copy of an image. However, it is possible to restore from a specific backup copy other than the primary copy. To do so, use the bprestore command. See the Backup, Archive, and Restore online help or the NetBackup Commands for UNIX and Linux.

Policies Schedule Attributes tab

137

Override policy storage selection

The Override policy storage selection attribute specifies whether to use the policy storage unit or the storage lifecycle policy as specified in the policys Attributes tab. Or, whether to use a different, specified storage unit or storage lifecycle for this schedule.

Click the check box to override the Policy storage selection that is indicated in the Attributes tab. Choose the storage unit or lifecycle from the drop-down list of previously configured storage units and lifecycle policies. If the list is empty, no storage units or lifecycles have been configured. If a data classification is indicated for the policy, only those storage lifecycles with the same data classification are displayed. For more information, see Data classification on page 90. To use only the policy storage selection that is indicated by the Policy storage setting in the Attributes tab, do not enable the check box. For more information, see Policy storage on page 91.

Note: Storage lifecycle policies cannot be selected within the multiple copies configuration dialog.

Override policy volume pool

The Override policy volume pool attribute specifies whether to use the policy volume pool or another volume pool for this schedule.

To override the volume pool that the Policy Volume Pool General Attribute specifies, select the check box. Choose the volume pool from the list of previously configured volume pools. To use the policy volume pool, do not select the check box. NetBackup uses the volume pool that is specified in the Policy volume pool General Attribute. If no policy volume pool is specified, NetBackup uses NetBackup as the default. If the policy is for a NetBackup catalog, NBU-Catalog policies use CatalogBackup.

Override media owner

The Override media owner attribute applies to tape media only and specifies whether to use the policy media owner or another owner for this schedule. The rules for shared disk media are more flexible, so override settings are not needed. Specify one of the following:

138 Policies Schedule Attributes tab

Any lets NetBackup choose the media owner. NetBackup chooses a media server or a server group (if one is configured). None 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. 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.

To override the media owner that the Media Owner General Attribute specifies, select the check box. Choose the media owner from the drop-down list To use the policy media owner, do not select the check box. NetBackup uses the media owner that is specified in the Media Owner General Attribute.

Retention
The Retention attribute specifies how long NetBackup retains the backups. To set the retention period, select a time period (or level) from the drop-down list. When the retention period expires, NetBackup deletes information about the expired backup. Once the backup expires, the files in the backup are unavailable for restores. For example, if the retention is two weeks, data can be restored from a backup that this schedule performs for only two weeks after the backup. If a policy is configured to back up to a lifecycle, the Retention attribute in the schedule is not followed. The retention indicated in the lifecycle is followed instead. (See Adding storage destinations to a lifecycle policy on page 255.)

Guidelines for assigning retention periods

The retention period for data depends on how likely the need is to restore information from media after a certain period of time. Some data (financial records, for example) have legal requirements that determine the retention level. Other data (preliminary documents, for example) can probably be expired when the final version is complete. A backups retention also depends on what needs to be recovered from the backup. For example, if day-to-day changes are critical, keep all the incremental backups in addition to the full backups for as long as the data is needed. If incremental backups only track work in progress toward monthly reports, expire the incremental backups sooner. Rely on the full backups for long term recovery. Establish some guidelines that apply to most of the data to determine retention periods. Note the files or the directories that have retention requirements outside of these guidelines. Plan to create separate policies for the data that falls

Policies Schedule Attributes tab

139

outside of the retention requirement guidelines. For example, place the files and directories with longer retention requirements in a separate. Schedule longer retention times for the separate policies without keeping all policies for the longer retention period. Another consideration for data retention is off-site storage of the backup media. Off-site storage protects against the disasters that occur at the primary site. Set the retention period to infinite for the backups that must be kept for more than one year.

One method to implement off-site disaster recovery is to use the duplication feature to make a second copy for off-site storage. Another approach is to send monthly or weekly full backups to an off-site storage facility. To restore the data, request the media from the facility. (Note that a total directory or disk restore with incremental backups requires the last full backup plus all incremental backups.) Consider configuring an extra set of schedules to create the backups to use as duplicates for off-site storage.

Ensure that adequate retention periods are configured, regardless of the method that is used for off-site storage. Use the NetBackup import feature to retrieve expired backups.

Precautions for assigning retention periods

Full backups: Always specify a time period that is longer than the frequency setting for the schedule. (The frequency is how often the backup runs). For example, if the frequency for a full backup is one week, specify a retention period of two to four weeks. Two to four weeks provides enough of a margin to ensure that the current full backup does not expire before the next full backup occurs. Cumulative incremental backups: Always specify a time period that is longer than the frequency setting for the schedule. For example, if the frequency setting is one day, specify a retention period of one week. One week provides enough of a margin to ensure that the current cumulative-incremental backup does not expire before the next successful one occurs. A complete restore requires the previous full backup plus the most recent cumulative-incremental backup. Differential incremental backups: Always specify a time period that is longer than the period between full backups. For example, if full backups occur weekly, save the incremental backups for two weeks. A complete restore requires the previous full backup plus all subsequent incremental backups.

140 Policies Schedule Attributes tab

NetBackup does not track backups after the retention period expires. Assign an adequate retention period as recovering files after the retention period expires is difficult or impossible. Within a policy, assign a longer retention period to full backups than to incremental backups. It may not be possible to restore all the files if the full backup expires before the incremental backups. Archive schedules normally use an infinite retention period. For WORM (write once, read many) optical platters, or tape, set the retention to infinite. If infinite is unacceptable because of NetBackup database space limitations, set the retention period to match the length of time that the data is to be retained. For the retention periods that are less than infinite, delete the WORM media from the Media Manager configuration upon expiration. If not deleted, Media Manager reallocates the media for future backups. (The media is reallocated, even though WORM can be written only once.)

Changing retention periods

Set the default retention periods by selecting NetBackup Management > Host Properties > Master Server > Double-click on master server > Servers > Retention Periods. For more information, see Retention Periods properties on page 462. The retention periods are indexed to different levels. For example, the default retention period for level 0 is one week. NetBackup also uses the level to determine the volume to use to store a backup. For more information, see Mixing retention levels on tape volumes on page 140.

Mixing retention levels on tape volumes

By default, NetBackup stores each backup on a tape volume that contains existing backups at the same retention level. If a backup has a retention level of 2, NetBackup stores it on a tape volume with other backups at retention level 2. When NetBackup encounters a backup with a different retention level, it switches to an appropriate volume. Because tape volumes remain assigned to NetBackup until all the backups on the tape have expired, this approach results in more efficient use of media. One small backup with an infinite retention would prevent a volume from being reused, even if all other backups on the volume have expired. To mix retention levels on volumes, select Allow multiple retentions per media on the Media host properties.

Policies Schedule Attributes tab

141

If you keep only one retention level on each volume, do not use any more retention levels than necessary. Multiple retention levels increase the number of required volumes. For more information, see Media properties on page 446. Note: Retention levels may be mixed on disk volumes with no restrictions.

Media multiplexing
The Media multiplexing attribute specifies the number of jobs from the schedule that NetBackup can multiplex onto any one drive. Multiplexing sends concurrent backup jobs from one or several clients to a single drive and multiplexes the backups onto the media. Specify a number from 1 through 32, where 1 specifies no multiplexing. For more information on how to configure multiplexed backups and the ramifications of multiplexing, see Chapter 3 in the NetBackup Administrators Guide, Volume II. Note: Some policy or some schedule types do not support media multiplexing. The option cannot be selected in those instances.

Final destination storage unit

If the schedule is a relocation schedule, a Final destination storage unit must be indicated. (A relocation schedule is created as part of a basic disk staging storage unit configuration.) A Final destination storage unit is the name of the storage unit where the images are swept to from the disk storage unit. For more information on basic disk staging storage units, see Staging backups to initial storage, then final storage on page 242.

Final destination volume pool

If the schedule is a relocation schedule, a Final destination volume pool must be indicated. (A relocation schedule is created as part of a basic disk staging storage unit configuration.) A Final destination volume pool is the volume pool where images are swept from the volume pool on the basic disk staging storage unit. For more information on basic disk staging storage units, see Staging backups to initial storage, then final storage on page 242.

142 Policies Schedule Attributes tab

Note: The relocation schedule that was created for the basic disk staging storage unit is not listed under Schedules in the NetBackup Administration Console when Policies is selected.

Policies Start Window tab

143

Start Window tab

The Start Window tab provides controls for setting time periods during which NetBackup can start backups, archives, or basic disk staging relocation when using this schedule. Time periods are referred to as time windows. Configure time windows so that they satisfy the requirements necessary to complete a task or job. For example, create a different window for the backups that open each day for a specific amount of time, or keep the window open all week. To create a schedule window 1 2 Click the Start Window tab. To indicate the beginning of the time window during which backups can start: Click the arrow to the right of Modify day and select the first day that the window is open. Then, click the up and down arrows to the right of Start time to select the time the window opens.

Time window

Indicate how long the time window remains open by setting a duration time or by choosing an End day and End time:

To indicate the duration of the time window: Once the opening (or the start) of the window is selected, click the up and down arrows to the right of Duration (days, hours, minutes). To indicate the close (or the end) of the time window:

144 Policies Start Window tab

Click the arrow to the right of End day and select the last day in the time window. Then, click the up and down arrows to the right of End time to select when the time window ends. Time windows show as bars in the schedule display. 4 If necessary, click a time window to perform actions by the following Start Window buttons:

Delete: Deletes the selected time window. Clear: Removes all time windows from the schedule display. Duplicate: Replicates the time window for the entire week. Undo: Erases the last action.

Click another tab to make additional selections, or click Add or OK to add the schedule as it is to the Schedule tab.

Duration example
The following figure represents the effect of schedule duration on two full backup schedules. The start time for schedule B begins shortly after the end time for previous schedule A. Both schedules have three clients with backups due.

Client A1 Client A2

Client A3 starts within the Schedule A window but doesnt complete until after the Schedule B start time. Client A3 Client B1 Client B2 Client B3 is unable to start because the window has closed. Client B3

Schedule A Start Time End Time Start Time

Schedule B End Time

The backup for client A3 in Schedule A does not finish until after the Schedule B window has opened. Schedule A does not leave enough time for the Schedule B backups. Client B3 must wait until the next time NetBackup runs Schedule B. Client A3 illustrates that if a backup starts, it runs to completion even if the window closes while the backup is running.

Policies Exclude dates tab

145

Exclude dates tab

Use the Exclude Dates tab to exclude specific dates from a schedule. The Exclude Dates tab displays a 3-month calendar. Use the controls at the top of the calendar to change the month or year. To exclude a date from the policy schedule 1 2 Select the Exclude Dates tab. Use one of the following methods to indicate a date:

Click the date on the calendar to be excluded.

Click New. Enter the month, day, and year in the Date selection dialog. Click OK. The date appears in the Exclude Dates list. 3 After the dates are selected, select another tab to make changes or click OK to close the dialog.

146 Policies Calendar schedule tab

Calendar schedule tab

The Calendar Schedule tab appears when Calendar is selected as the Schedule type on the Attributes tab of the Schedule dialog. Calendar-based schedules provide several run day options for determining when a task runs. Figure 4-8 Calendar selection in the Policy Attributes tab

Select Calendar on the Attributes tab to enable the Calendar Schedule tab

The Calendar Schedule tab displays a 3-month calendar. Use the controls at the top of the calendar to change the month or year.

Schedule by specific dates

A task can run on specific dates rather than follow a recurring schedule, and specific dates can be added to a recurring schedule. Use the Specific dates run day option to schedule specific dates for a task to run.

Policies Calendar schedule tab

147

To schedule a task on specific dates 1 In the Calendar Schedule tab, select Specific Dates.

Use one of the following methods to indicate a date:

Click the date in the calendar.

Click New. Enter the month, day, and year in the Date Selection dialog. Click OK. The date appears in the Specific Dates list. 3 4 To remove a date, select it in the calendar schedule list and click Delete. After the dates are selected, select another tab to make changes or click OK to save and close the dialog.

Schedule by recurring week days

The Recurring Week Days option presents a matrix of days and weeks to schedule a task. The matrix is not a calendar. A check mark on a day indicates that the task is scheduled to run on that day of that week each month. For example, schedule a task to run on the first and the third Thursday of every month. Or, schedule a task that runs the last week in every month.

148 Policies Calendar schedule tab

To schedule a recurring weekly task 1 In the Calendar Schedule tab, select Recurring Week Days.

Matrix

2 3 4 5 6

If necessary, click Deselect All to remove existing selections from the matrix. Click a check box in the matrix to select the day. Or, click a check box to clear it. Click the name of the day column header to select or clear the corresponding day for each week of the month. Click a row number to select or clear the entire week. Click the check box for the appropriate day in the Last row to schedule a task for the last week of each month. The task is scheduled, regardless of the number of weeks in the month. After the dates are selected, select another tab to make changes or click OK to save and close the dialog.

Schedule by recurring days of the month

The Recurring Days of the Month option presents a matrix to schedule a task for certain days of the month. A task can be scheduled to occur on the last day of the month, regardless of the actual date.

Policies Calendar schedule tab

149

To schedule a recurring monthly task 1 In the Calendar Schedule tab, select Recurring Days of the Month.

Matrix

2 3 4 5 6

If necessary, click Deselect All to remove existing selections from the matrix. To select all of the days in every month, click Select All. Select the button for each day to be included in the run schedule. Click the button again to deselect the day. Select the Last Day check box to run the schedule on the last day of the month, regardless of the date. After the dates are selected, select another tab to make changes or click OK to save and close the dialog.

How calendar scheduling interacts with daily windows

Daily windows are taken into account, even when calendar-based schedules are used. Windows that span midnight become two separate windows for calendar schedules. After the policy is created, the initial backups may appear as though two backups have run within the same window. If the calendar schedule indicates that today is a run day, the backup runs once during any window that is open. For example:

150 Policies Calendar schedule tab

A new backup policy is created on Monday afternoon. The windows are configured to be open from 6 p.m. until 6 a.m., Sunday through Saturday.

In the Calendar Schedule tab, the schedule is set up to run on every week day, Monday through Saturday.

3 4

No backups from the policy exist yet because it is a new policy. Since today (Monday) is a run day, a job runs as soon as the window opens at 6 p.m. At midnight, it is a new day (Tuesday) and a window is open (until 6 a.m.) so the job is due and runs again. The backups continue to run soon after midnight from that time forward.

Notice how the backup runs before midnight, then again immediately after midnight. Both jobs are valid since both have different run days and windows are open at both times (6 a.m. through 6 p.m. every day of the week). Windows that span midnight become two separate windows for calendar schedules.

Policies Calendar schedule tab

151

To run jobs at 6 p.m. instead of midnight, use a frequency of one day instead of recurring days in the Calendar Schedule tab.

Automatic-backup schedule examples

Backups can be scheduled to occur automatically on every day of the week or only on specific days. A different backup window can be specified for each day. The days that are chosen for backups depends on how you want to distribute the backup load. For example, to have all backups occur on Saturday, create a backup window only for Saturday. Leave these values blank for other days. The best times for automatic backups are usually nights and weekends, when client and network activity is lowest. Otherwise, the backups can adversely affect client and network performance and take longer to complete. For details on how calendar-based scheduling works with backup windows, see How calendar scheduling interacts with daily windows on page 149. For examples of automatic schedule configuration, click the Help button in the Schedule dialog. Then, click the link Automatic-backup schedule examples.

Considerations for user schedules

In order for users to perform backups and archives, you must create a schedule that allows user backups. A user backup schedule may be included in a policy that contains automatic backup schedules. Restores can be performed at any time and are not scheduled. Caution: An archive is different from a backup. During an archive, NetBackup first backs up the selected files, then deletes the files from the local disk if the backup is successful. In this manual, references to backups also apply to the backup portion of archive operations unless otherwise noted.

Planning user backup and archive schedules

To plan schedules for user backups and archives, consider the following:

What are the most convenient times for users to perform backups? If possible, do not permit user backups and archives when automatic backups are running. If an automatic backup is running when a user submits a backup or archive, NetBackup usually queues the user job. The job is not queued if there is a limiting setting. (For example, the Limit Jobs per Policy policy attribute or the Maximum Jobs per Client Global Attributes host property.)

152 Policies Calendar schedule tab

If the automatic backup continues to run, the user job misses the backup window. User jobs delay automatic backups and can cause backups to miss the backup window. See Limit jobs per policy on page 97 and Maximum jobs per client on page 436.

Which storage unit should be used for user backups? Use a different storage unit to eliminate conflicts with automatic backups. Which volume pool should be used for user backups? Use a different volume pool if you want to manage the media separate from the automatic backup media.

Caution: If the retention period expires for a backup, it can be difficult or impossible to restore the archives or backups.

How long should an archive be kept? Consider setting the retention period for archives to infinite, since the disk copy of the files is deleted. For more information, see Retention on page 138.

Creating separate policies for user schedules

User backup and archive schedules do not need to be in a policy separate from automatic backup schedules. If you create separate policies for user backups or archives, the considerations are similar to those for automatic backups. In user backup schedules, however, no backup selection list is necessary because users select the objects before they start the backup or archive.

Using a specific policy and user schedule

To use a specific policy or schedule for user backups or archives, perform the following on the client:

On Microsoft Windows clients, start the Backup, Archive, and Restore client interface. Click File > NetBackup Client Properties and select the Backups tab. Specify the backup policy and backup schedule. On NetWare target clients, specify the policy and schedule with backup_policy and backup_sched entries in the bp.ini file. (See the NetBackup NetWare users guide). On UNIX clients, specify the policy and schedule with BPARCHIVE_POLICY, BPARCHIVE_SCHED, BPBACKUP_POLICY, or BPBACKUP_SCHED options in the bp.conf file.

Policies Example policies

153

Example policies
The following tables show the clients, backup selection list, and schedules of two example backup policies. Policy 1 specifies that files in /usr and /home be backed up for the clients mars, jupiter, and neptune. This policy has daily and weekly automatic schedules, and a user backup schedule. All backups go to 8mm tape. Example Policy 1 Clients
mars jupiter neptune

Backup Selection List

/usr /home

Schedules
Daily Incremental Backups

Run every day between 6 p.m. and 6 a.m. Store on 8mm tape. Keep 14 days. Run Mondays every week between 6 p.m. and 6 a.m. Store on 8mm tape. Keep one month. User can run any day between 8 a.m. and 5 p.m. Store on 8mm tape. Keep one year.

Weekly Fulls Backups

User Backups

Policy 2 contains different scheduling requirements: the policy contains the monthly full backups that are written to DLT tape. Example Policy 2 Clients
pluto mercury

Backup Selection List

/usr /home

Schedules
Daily Incremental Backups

Run every day between 6 p.m. and 6 a.m. Store on 8mm tape. Keep 14 days. Run Tuesdays every week between 6 p.m. and 6 a.m. Store on 8mm tape. Keep one month. Run Sundays every month between 6 p.m. and 6 a.m. Store on DLT tape. Keep one year.

Weekly Fulls Backups

Monthly Full Backups

154 Policies Example policies

Policy planning guidelines for backups

Policies can meet the needs of a wide variety of clients in a single NetBackup configuration. To take the best advantage of the capabilities of policies, plan your policies before starting configuration. The following procedure provides guidelines for planning.

Group the clients

Divide clients into groups according to the types of work the clients perform. Clients that are used for similar tasks generally have much in common regarding the backup requirements. For example, most clients in an engineering department create the same types of files at similar levels of importance. In some instances, you can create a single policy for each group of clients. In other cases, you need to subdivide the clients and include them in the separate policies that are based on their backup requirements. In this example, assume that the clients are in the same work group. Initially, well try to cover all of the clients in the same backup policy.

Gather information about clients

Gather information about each client. Include information relevant to the backups such as the names of the clients and the number of files and file sizes each generates. In this example, mercury is a file server that contains a large amount of data. To avoid long backup times, include mercury in policy S1 and the workstations in another policy (WS1). Later, we may find that we need more than one policy for mercury. The current backup policies are as follows: Policy
S1 WS1

Clients
mercury mars jupiter neptune

Consider storage requirements

Create backup policies to accommodate special storage requirements. The storage unit and volume pool settings apply to all files that are backed up by the policy. If files have special storage requirements, create separate policies for the files, even if other factors are the same, such as schedules. In this example, a separate policy (S2) is used for

Policies Example policies

155

/h002/devexp and /h002/desdoc on mercury. Those files are sent to DLT tape. Other files on mercury go on 8mm tape. If it is necessary to keep backups for some files on separate media, create a policy that specifies a unique volume pool for those backups. Then, add the media for that volume pool.

Policy
S1

Clients
mercury

Files
/usr /h001 /h002/projects /h002/devexp /h002/desdoc

Storage
8mm

S2

mercury mercury

DLT

Consider backup schedules

Create additional backup policies if one set of schedules does not accommodate all clients and files. Consider the following factors to create schedules in a policy:

Best times for backups to occur. To back up different clients on different schedules, create more policies. For example, create different policies for night-shift and day-shift clients. In our example, we can back up all clients during the same hours so additional policies are not necessary. How frequently the files change. If some files change infrequently compared to other files, back up the files on a different schedule. To use a different schedule, create another policy that has an appropriate schedule and then include the files and clients in that policy. In our example, the root (/) file system on mercury is in a different policy (S3). The root(/) file system on the workstations is also in a separate policy (WS2). How long backups need to be kept. Each schedule has a retention setting that determines how long NetBackup keeps the files that are backed up by the schedule. Because the schedule backs up all the files in the backup selection list, all files should have similar retention requirements. Do not include the files whose full backups must be retained forever, together in a policy where full backups are retained for only four weeks.

156 Policies Example policies

In the example, /h002/desdoc on mercury is in a different policy (S4). /h002/desdoc requires full backups every 12 weeks and those backups must be retained much longer than the other files on mercury.

Policy Clients
S1 mercury

File selections

Frequency of Change
high

Storage
8mm

Frequency of Automatic Backups

/usr /h001 /h002/projects /h002/devexp

Daily incremental backups Weekly full backups Full backups every 4 weeks Daily incremental backups Weekly full backups Full backups every 4 weeks Daily incremental backups Full backups every 4 weeks Daily incremental backups Weekly full backups Full backups every 4 weeks Full backups every 12 weeks Daily incremental backups Weekly full backups Full backups every 4 weeks

S2

mercury

high

DLT

S3

mercury

low

8mm

S4

mercury

/h002/desdoc

high

DLT

WS1

mars jupiter neptune

/usr /people /usr /home /usr /people /var / / /

high

8mm

WS2

mars jupiter neptune

low

8mm

Daily incremental backups Full backups every 4 weeks

Group by general attributes

Create separate policies for the clients that require different general attribute settings than other clients. General attributes include the following:

Policy Type. You must use the correct policy type for each client. For example, include Windows XP and Windows 2000 clients in a MS-Windows-NT policy. For more information, see Policy type on page 88. Follow NFS. Select this attribute if a UNIX client has NFS mounted files to be backed up. Consider placing these clients in a separate policy so problems

Policies Example policies

157

with NFS do not affect the other clients. For more information, see Follow NFS on page 101.

Cross Mount Points. Select this attribute if you want NetBackup to cross mount points on UNIX or Windows clients in the policy. For more information, see Cross mount points on page 103. Backup Network Drives. Select this attribute to back up the files that the client stores on network drives (applies only to MS-Windows-NT policies). For more information, see Backup network drives on page 100. Compression. Set this attribute if you want a client to compress its backups before sending them to the server. Note that the time to compress can increase backup time and make it unsuitable to use for all clients. For more information, see Compression on page 105. Job Priority. Use this attribute to control the order in which NetBackup starts the backups. The clients with the higher priority are backed up first. For more information, see Job priority on page 98. In our example, no extra policies are required because of general attribute settings.

Maximize multiplexed backups

Create separate policies as necessary to maximize the benefits of multiplexed backups. To maximize drive use, use multiplexing for the slower clients that produce small backups. The higher-performance clients that produce long backups are likely to use drives fully and not benefit from multiplexing.

Evaluate backup times

Evaluate total backup times for each schedule and further subdivide policies to reduce backup times to an acceptable level. For example, if the backup of /usr, /h001, and /h002/projects on mercury takes too much time, create a new policy for /h002/projects. Policy S5 has the same requirements as S1. Back up /h002/projects separately to reduce backup time. In addition to reducing the backup time for each policy, separate policies can reduce the total backup time for the server mercury. NetBackup processes files within a backup selection list serially, in the order they appear in the backup selection list. However, separate policies are processed in parallel if enough drives are available and the maximum jobs attributes are set to allow it. The Multiplexing and Allow Multiple Data Streams options also allow backup policies to be processed in parallel.

158 Policies Example policies

See Allow multiple data streams on page 112 in this guide and Using multiple NetBackup master servers in Chapter 1 of the NetBackup Administrators Guide, Volume II.

Policy
S1

Clients
mercury

File selections

Frequency of Change
high

Storage
8mm

Frequency of Automatic Backups

/usr /h001

Daily incremental backups Cumulative incremental backups Full backups every 4 weeks Daily incremental backups Cumulative incremental backups Full backups every 4 weeks Daily incremental backups Cumulative incremental backups Daily incremental backups Weekly full backups Full backups every 4 weeks Full backups every 12 weeks Daily incremental backups Weekly full backups Full backups every 4 weeks Daily incremental backups Weekly full backups Full backups every 4 weeks

S2

mercury

/h002/devexp

high

DLT

S3

mercury

low

8mm

S4

mercury

/h002/desdoc

high

DLT

S5

mercury

/h002/projects

high

8mm

WS1

mars jupiter neptune

/usr /home /usr /home /usr /home /var / / /

high

8mm

WS2

mars jupiter neptune

low

8mm

Daily Incr 4 Weeks Full

Policies Clients tab

159

Clients tab
The Clients tab contains a list of clients to be backed up (or acted upon) by the selected policy. A client must be included in the list of at least one backup policy to be backed up. A client can be placed in more than one backup policy can be useful. For example, place the client name in two policies to back up different sets of files on the client according to different policy rules. NetBackup software can be installed on UNIX client machines from the Clients tab. Note: The Clients tab does not appear for Vault or Catalog policy types. To add a client to a policy 1 In the NetBackup Administration Console, expand NetBackup Management > Policies.

2 3

Double-click the policy in the middle pane. Select the Clients tab and click New. The Add Client dialog appears. Observe the following rules for assigning client names:

Use a name by which the server knows the client (one that you can use on the server to ping or telnet to the client). If the client is in multiple policies, use the same name in each policy. If the network configuration has multiple domains, use a more qualified name. For example, use mars.bdev.null.com or mars.bdev rather than only mars. Add only clients with the hardware and the operating systems that this policy supports.

Click the Hardware and operating system list box, then select the entry in the list.

160 Policies Clients tab

Add only clients with the hardware and the operating systems that this policy supports. For example, do not add a Novell NetWare client to an MS-Windows-NT policy. If you add a client to more than one policy, designate the same hardware and operating system in each of the policies. Note: If the hardware and the operating system you want is not in the list, associated client software is not installed on the server. Check the /usr/openv/netbackup/client directory for the directories and software that corresponds to the client you want to install. If the directories or software are not there, rerun the installation script on the server and choose the option to install client software. (See the NetBackup installation guide that came with your software.) 5 Click OK. To add another client, click Add. Click Close to cancel the changes that you have not yet added and close the Add Client dialog.

To install client software on trusting UNIX clients

Install client software on trusting UNIX clients by using the NetBackup Administration Console on a UNIX server. The following are prerequisites to installation:

You can install the client software only from a UNIX NetBackup server. The server must be the server that was specified in the login dialog when the interface was started. This server must also be the master where you currently manage backup policies and clients must be in a policy on this master. Each client to be installed must have an entry for the current master server in its /.rhosts file. If these entries exist, the clients are referred to as trusting clients. The /.rhosts entries for the master server are not required for correct operation of NetBackup and you can remove them after installing the client software.

To install UNIX client software 1 In the NetBackup Administration Console, expand NetBackup Management > Policies. If you want to install client software, you cannot use the File > Change Server command to get to another master server. The master server must be the server that you specified in the login dialog.

Policies Clients tab

161

Select the master server name at the top of the All Policies middle pane.

3 4

Click Actions > Install UNIX Client Software. The Install UNIX Client Software dialog appears. In the Dont install these clients box, select the clients you want to install and click the right arrows. The clients are moved to the Install these clients field.

Click the Install Client Software button to start the installation. Client software installation can take a minute or more per client. NetBackup writes messages in the Progress box as the installation proceeds. If the installation fails on a client, NetBackup notifies you but keeps the client in the policy. You cannot stop the installation once it has started.

162 Policies Clients tab

During installation, NetBackup does the following:

Copies the client software from the /usr/openv/netbackup/client directory on the server to the /usr/openv/netbackup directory on the client.

Adds the required entries to the clients /etc/services and inetd.conf files. To install client software to a different location on the client, first create a directory where you want the software to reside. Then create /usr/openv/netbackup as a link to that directory before installing software.

When the install is complete, click Close.

To install software on secure UNIX clients

A secure UNIX client is a client that does not contain an entry for the NetBackup master server in its /.rhosts file. You can install software on clients by using a script or locally on the client from the CD-ROM. For instructions, see the NetBackup Installation Guide for UNIX.

To install software on Windows clients

To install NetBackup Windows client software, see the NetBackup Installation Guide for Windows.

To configure a snapshot method

The options to configure a snapshot backup method are available only when the Snapshot Client option is licensed on a UNIX or Windows server. For information on how to configure snapshots, see the NetBackup Snapshot Client Administrators Guide.

Policies Backup Selections tab

163

Backup Selections tab

The Backup Selections tab lists the files, directories, directives, scripts, and the templates that are backed up with this policy. NetBackup uses the same backup selection list for all of the clients that are backed up according to the policy. Every file on the list does not need to exist on all of the clients. NetBackup backs up the files that it finds that are on the backup selections list. Each client, however, must contain at least one of the files in the backup selections list or the client backup fails with a status 71. The policy backup selections list does not apply to user backups or archives. For user backups and archives, users select the objects to back up before they start the operation.

Lists for different policy types

A backup selection list may contain different information, depending on the policy type. For example:

Standard, Exchange, and Lotus Notes policy types list paths and directives. See Backup selections list for standard policies on page 163. Depending on the database type, the backup selection list for database policies contains different types of objects. See Backup selections list for database policies on page 165.

For Exchange and Lotus Notes, the list contains paths and directives. For MS-SQL-Server, Informix-On-BAR, SAP, and Sybase, the list contains the scripts that define and control the database backup, including how the client uses multiple streams. For Oracle and DB2, the list contains scripts and templates.

Vault policy types list only Vault commands in the backup selections list. For more information, see Creating a Vault policy on page 199.

Backup selections list for standard policies

Standard, Exchange, and Lotus Notes policy types list paths and directives in the backup selection list.

164 Policies Backup Selections tab

To add or change backup selections for a standard, Exchange, or Lotus Notes policy 1 In the NetBackup Administration window, expand NetBackup Management > Policies.

2 3 4 5

Double-click the policy where you want to change the backup selections list. The Change Policy dialog appears. Click the Backup Selections tab. To add an entry, click New. The Add Backup Selections dialog appears. Select a path or directive:

Type the name of the path in the Pathname or Directive field. For file path information, see Pathname rules for UNIX clients on page 176 and Path rules for Microsoft Windows clients on page 170. Click the drop-down arrow and select a directive in the Pathname or Directive field. Click Add to include the path or directive to the list.

Click to select a directive

For information on the benefits of directives, see Backup selections list directives: General discussion on page 185. If the Allow Multiple Data Streams general policy attribute is enabled, see Backup selections list directives for multiple data streams on page 189. For separately-priced options, also see the NetBackup guide for the option. Note: Paths may contain up to 1023 characters. 6 To rearrange the selections in the selection list:

Click Insert to add an entry before the entry currently selected.

Policies Backup Selections tab

165

To delete an entry, select the entry and click Delete. To rename an entry, select it and click Change. The Change Backup Selection dialog appears. Make your changes and press OK.

To verify that the entries on the selections list are accurate, see Verifying the backup selections list on page 167.

Backup selections list for database policies

The type of database determines whether the selections list contains paths, directives, or scripts. To create or change backup selections containing scripts for a database policy 1 2 3 4 In the NetBackup Administration window, expand NetBackup Management > Policies. Double-click the database policy in the Console tree where you want to change the backup selections lists. The Change Policy dialog appears. Click the Backup Selections tab. To add an entry, click New. The Add Backup Selections dialog appears. Enter a script into the text box, then click Add to add the script to the selection list. Shell scripts require that the full path be specified. Be sure that the shell scripts that are listed are installed on each of the clients that are specified on the Client tab. Click OK to add the items to the Backup Selections list.

To add templates or scripts to the backup selections list 1 2 3 4 5 In the NetBackup Administration window, expand NetBackup Management > Policies. Double-click the policy where you want to add or change templates or scripts. The Change Policy dialog appears. Click the Selections tab. To add an entry, click New. To insert an entry within the current list, select an item and click Insert. The Add Backup Selection dialog appears. Specify the backup selections:

Templates: For Oracle policies: From the Template set list, choose a template set by operation.

166 Policies Backup Selections tab

For both Oracle and DB2 policies: Choose the correct template from the drop-down Script or template list, or type the name of a template. Templates are stored in a known location on the master server and do not need to be installed on each client in the Clients list. Enter only the template file name, without a path. For example: weekly_full_backup.tpl

Shell scripts: Specify the full path to list scripts. Be sure that the scripts that are listed are installed on each client in the Client list. Specifying an Oracle script example: install_path/netbackup/ext/db_ext/oracle/samples/rman /cold_database_backup.sh Specifying a DB2 script example: /myscripts/db2_backup.sh

6 7

To change the order of the backup selections, select one and click Up or Down. Click OK to add the selection to the selection list.

Methods for faster backups

The following sections describe methods for reducing client backup times.

Dividing file lists between multiple policies

Selection list entries are processed serially for each client and in the order that they appear in the backup selections. A client can be added to multiple policies, to divide the clients files among the different backup selections lists. multiple policies can reduce the backup time for that client because the files can be backed up in parallel. Multiple clients can be backed up in parallel if:

Multiple storage devices are available (or if the policies are multiplexed). The Maximum Jobs per Client Global host property, and the Limit Jobs per Policy policy attributes are set to allow it.

Note: Understand disk and controller I/O limitations before configuring including a client in multiple policies. For example, if two file systems overload the client when backed up in parallel, place both file systems in the same policy. Schedule the file systems at different times or set Maximum Jobs per Client to 1.

Policies Backup Selections tab

167

Allowing multiple data streams

Another method to reduce backup time is to select Allow Multiple Data Streams for a policy. Then, add NEW_STREAMS directives to the backup selections list. For example:
NEW_STREAM file_a file_b file_c NEW_STREAM file_d file_e file_f

The example produces two concurrent data streams. The first data string contains file_a, file_b, and file_c. The second data stream contains file_d, file_e, and file_f. For more information, see Allow multiple data streams on page 112. Note: For best performance, use only one data stream to back up each physical device on the client. Multiple concurrent streams from a single physical device can cause longer backup times. The tape heads must move back and forth between tracks containing files for the respective streams. A directive instructs NetBackup to perform specific actions to process the files in the backup selections list.

Verifying the backup selections list

Verify a backup selections list to make sure that the file paths are correct for the clients in the policy. To verify a backup selections list 1 Check all entries against the file path rules for the clients in the policy. If the list includes directives, verify that the syntax for the directives is correct. For more information, see Rules to indicate paths in the backup selections list on page 170. Run a set of backups. Then, check the Problems report or the All Log Entries report for warning messages. The backup status code does not always indicate errors on the backup selection list. NetBackup does not require all paths in the backup selections list to be present on all clients, so the error would not be reflected. Run the check_coverage script to create a File System Backup Coverage Report. The script is located in /usr/openv/netbackup/bin/goodies.

168 Policies Backup Selections tab

The script can reveal mistakes in the selections list that make it impossible for NetBackup to find the files. This results in files being skipped in the backup. If a path is not found, NetBackup logs a trivial (TRV) or warning (WRN) message. However, the job may end the backup with a status code 0 (successful). Usually, to report files missing from the backup selections list is not helpful, since not all files are expected to be present on every client. However, check the logs or use the check_coverage script to ensure that files are not missed due to bad or missing backup selections list entries. The following examples show the log messages that appear when files on a client are not found. For information on check_coverage, see the comments in the script.

Example 1: Regular expressions or wildcards

Assume that the backup selections list contains a regular expression: /home1[0123456789] NetBackup backs up /home10 through /home19 if both exit. If they are not present, the Problems report or the All Log Entries report displays a message similar to the following:
02/02/06 20:02:33 windows freddie from client freddie: TRV - Found no matching file system for /home1[0123456789]

Example 2: Path not present on all clients or wrong path specified

Assume that the backup selections list contains a path named /worklist that is not present on all clients. NetBackup backs up /worklist on the clients where it exists. For other clients, the Problems report or the All Log Entries report displays a message similar to the following:
02/02/06 21:46:56 carrot freddie from client freddie: TRV - cannot process path /worklist: No such file or directory. Skipping

This message occurs if /worklist is not the correct path name. For example, if the directory name is /worklists but /worklist was typed. Note: If the paths seem correct and the message continues to appear, ensure that no trailing spaces appear in the paths.

Example 3: Symbolic link

Assume the backup selections list names a symbolic link. NetBackup does not follow symbolic links and provides a message in the Problems report or the All Log Entries report:
02/02/04 21:46:47 carrot freddie from client freddie: WRN - /src is only being backed up as a symbolic link

Policies Backup Selections tab

169

You must resolve the symbolic link if you do not intend to back up the symbolic link itself.

170 Policies Rules to indicate paths in the backup selections list

Rules to indicate paths in the backup selections list

The following sections discuss rules for specifying paths for each type of NetBackup client:

Pathname rules for UNIX clients on page 176. Path rules for Microsoft Windows clients on page 170. Path rules for NetWare NonTarget clients on page 183. Path rules for NetWare Target clients on page 185. Path rules for clients running extension products on page 185.

Path rules for Microsoft Windows clients

The following sections describe the conventions that are used to specify backups for Windows clients.

File backups
Microsoft Windows path conventions, UNIX path conventions, or a combination of the two can be used in the backup selections list.

Using Microsoft Windows conventions

Enter one path per line. Begin all paths with the drive letter followed by a colon (:) and a backslash (\). Note: The drive letter is case-insensitive, however, the path is case-sensitive. For example, c:\Worklists\Admin\ To specify an entire volume, append a backslash (\) to the entry to ensure that all data is protected on that volume: Correct entry: c:\ Incorrect entry: c:

Precede each component in the path with a backslash. If the last component in the path is a directory, follow it with a backslash (\) as well. The trailing backslash is not required but serves as a reminder that the path is to a directory instead of a file: c:\users\net1\ If the last component is a file, include the file extension and omit the backslash from the end of the name: c:\special\list.txt

Policies Rules to indicate paths in the backup selections list

171

Allowable wildcard characters are the same as those allowed in Windows paths: * ? For more information, see Using wildcards in NetBackup on page 632. To back up all local drives except for those that use removable media, specify: :\ or *:\ or ALL_LOCAL_DRIVES The following drives are not backed up: floppy disks, CD-ROMs, and any drives that are located on remote systems but mounted on a system through the network. By default, NetBackup does not back up the files that are described in Files that are excluded from backups by default on page 194. Exclude specific files from backups by creating an exclusion list on the client. For more information, see Excluding files from automatic backups on page 195.
c:\ d:\workfiles\ e:\Special\status c:\tests\*.exe

The following backup selection list uses Microsoft Windows conventions:

UNIX conventions that are permitted on Windows

You can use UNIX conventions in the backup selection list for Windows clients. UNIX conventions are similar to those for Microsoft Windows, with the following exceptions:

Begin each line with a forward slash (/). Omit the colon (:) after the drive letter. Specify / to back up all local drives except for those that are removable.
/c/ /d/workfiles/ /e/Special/status /c/tests/*.exe

The following example uses UNIX conventions:

Windows disk-image (Raw) backups

On Windows clients, you can back up a logical disk drive as a disk image. That is, NetBackup backs up the entire logical drive on a bit-by-bit basis rather than by directories and files. Select Full backup as the backup type to perform a disk-image backup.

172 Policies Rules to indicate paths in the backup selections list

To specify a disk-image backup, add the logical name for the drive to the policy backup selection list. The format in the following example backs up drive C.
\\.\c:

Disk-images can be included in the same backup selection list with other backups:
\\.\c: d:\workfiles\ e:\Special\status HKEY_LOCAL_MACHINE:\

To restore the backup, the user first chooses Select for restore > Restore from Normal backup. When the backups are listed, the disk image appears as a file with the same name that was specified in the backup selection list. In this example:
\\.\c:

Select the disk image source, then enter the destination in the following format:
\\.\drive:

Where drive is the location where the partition is to be restored.

Notes on disk-image backups

NetBackup first attempts to use Windows Open File Backup methods. If that fails, NetBackup locks the logical drive, which ensures that no changes occur during the backup. If there are open files on the logical drive, a disk-image backup is not performed. Before a disk image is backed up or restored, all applications that use a handle to the partition must be shut down. It the applications are not shut down, the operation fails. Examples of such applications are Windows Explorer or Norton Antivirus. Ensure that no active COW (Copy On Write) snapshots are in progress. If there is an active COW snapshot, the snapshot process itself has a handle open to the volume. NetBackup does not support raw partition backups on unformatted partitions.

Microsoft Windows registry backup

Backup for disaster recovery
To ensure a successful recovery in case of a disk failure, always back up the entire registry. That is, back up the directory that contains the entire registry. On most Windows systems, this directory is located at:
%systemroot%\system32\config

Where %systemroot% is the directory where Windows is installed.

Policies Rules to indicate paths in the backup selections list

173

For example, if Windows 2000 is installed in the c:\winnt directory, include any of the following paths to accomplish the backup:

c:\winnt\system32\config (backs up the entire config directory) c:\ (backs up the entire C drive) ALL_LOCAL_DRIVES System_State:\ (applies to Windows 2000/XP) Shadow Copy Components:\

For Windows 2003 systems, enter:

Caution: To recover the registry, do not include individual registry files or HKEY entries in the selection list thats used to back up the entire registry. If you use a NetBackup exclude list for a client, do not exclude any registry files from your backups. To restore the registry in the case of a disk failure, see the Disaster Recovery chapter in the NetBackup Troubleshooting Guide for UNIX and Windows.

Back up individual HKEYs (do not use for disaster recovery)

Do not include HKEY entries in the same policy backup selection list that is used to back up the entire registry. However, to restore individual keys within the registry, create a separate policy, then specify the specific HKEYs in the backup selection list for that policy. The following is an example HKEY entry for a policy backup selection list:
HKEY_LOCAL_MACHINE:\

Remember, you cannot perform a disaster recovery by restoring HKEYs. In addition, backups and restores are slower than if the entire registry was backed up.

Hard links to files (NTFS volumes or UNIX)

A hard link is a directory entry for a file. Every file can be considered to have at least one hard link. On NTFS volumes or on UNIX systems, each file can have multiple hard links. Therefore, a single file can appear in many directories (or even in the same directory with different names). A Volume Serial Number (VSN) and a File Index indicates the actual file, unique on the volume. Collectively, the VSN and File Index are referred to as the file ID. During a backup, if the backup selection list includes hard-linked files, the data is backed up only once. NetBackup uses the first file name reference that is found in the directory structure. If a subsequent file name reference is found, the reference is backed up as a link to the name of the first file. To back up

174 Policies Rules to indicate paths in the backup selections list

subsequent references means that only one backup copy of the data is created, regardless of the number of multiple hard links. If all hard-link references are restored, the hard-linked files continue to point to the same ID as the other files to which they are linked. However, if all the hard links are not restored, you can encounter anomalies as shown in the following examples.

Example 1
Assume that three hard links point to the same data. 1 During a backup of Link2 and Link3, Link2 is encountered first and backed up. Then Link3 is backed up as a link to Link2. The three files are all hard-linked to the same data.
Link1 Link2 Link3

Data

The original copies of Link2 and Link3 are backed up to tape, then deleted. Only Link1 is left on the disk.
On Disk On Tape

Link1

Link2

Link3

Data

Data

During a subsequent restore, Link2 and Link3 are restored. The restored files, however, do not point to the same file ID as Link1. Instead, they are assigned a new file ID or inode number and the data is written to a new place on the disk. The data in the new location is an exact copy of what is in Link1. The duplication occurs because the backup does not associate Link2 and L3 with Link1.
Link1 Link2 Link3

Data

Data

Policies Rules to indicate paths in the backup selections list

175

Example 2
Assume that you attempt to restore only Link3. Here, NetBackup cannot link Link3 to Link2 because Link2 does not exist. The restore can complete only if it can link to Link2. A secondary restore request to the NetBackup server automatically restores Link2, which contains the data. Link2 can now be successfully restored.

176 Policies Rules to indicate paths in the backup selections list

Pathname rules for UNIX clients

The following sections describe the conventions that are used to specify backups for UNIX clients.

Enter one pathname per line. NetBackup supports a maximum path length of 1023 characters for UNIX clients. Begin all pathnames with a forward slash (/). The following wildcard characters are allowed:
* ? [ ] { }

For more information, see Using wildcards in NetBackup on page 632.

If a backup selection list entry contains trailing spaces and a matching entry is not found, NetBackup deletes the spaces and checks again. If a match is not found, NetBackup skips the entry and logs a message in the Problems report or the All Log Entries report:
TRV - cannot process path pathname: No such file or directory. Skipping TRV - Found no matching file system for pathname

Notes on UNIX pathnames

Pathnames that cross mount points or that the client mounts through NFS can affect the backup configuration. Read about the Follow NFS and Cross mount points attributes before you create a backup selection list. For more information, see Follow NFS on page 101 and Cross mount points on page 103. NetBackup can back up operating system, kernel, and boot files. NetBackup cannot, however, create bootable tapes. Consult your system documentation to create a bootable tape. By default, NetBackup does not back up the files that are described in Files that are excluded from backups by default on page 194. Exclude specific files from backups by creating an exclusion list on the client. For more information, see Excluding files from automatic backups on page 195. The Busy file settings host properties for UNIX clients offers alternatives for handling busy and locked files. For more information, see Busy File Settings properties on page 380.

Policies Rules to indicate paths in the backup selections list

177

On Solaris, HP-UX, AIX, Linux Red Hat 4 (and later), Linux SuSE SLE 9 (and later), and MAC 10.4 (and later) platforms, NetBackup backs up access control lists (ACLs). NetBackup can back up and restore Sun PC NetLink files. On IRIX 6.x and TRU64 Alpha platforms, NetBackup backs up extended file attributes. On IRIX platforms, NetBackup backs up and restores extended attributes attached to XFS file system objects. On TRU64 OSF/1 platforms, NetBackup backs up and restores extended attributes attached to files on AdvFS and UFS file systems. By default, NetBackup backs up and restores Solaris 9 and 10 extended attribute files. The FlashBackup single file restore program (sfr) does not restore extended attribute files. By default, NetBackup backs up and restores named data streams for VxFS 4.0 (Solaris SPARC) and VxFS 5.0 (Solaris SPARC, HP, and AIX). The FlashBackup single file restore program (sfr) does not restore extended attribute files. For more information, see Backup and restore of extended attribute files and named data streams on page 180. On Hewlett-Packard and Solaris SPARC platforms, NetBackup backs up VxFS extent attributes.

Symbolic links to files or directories

For symbolic or soft links, include the pathname to the source file in the backup selections list to back up the actual data. If a file is a symbolic link to another file, NetBackup backs up only the link, not the file to which the link points. To back up only the link prevents multiple backups of the source file. Symbolic links are restored only as a symbolic link to the source file. Therefore, you must restore the source file along with the link to get the data. Note: If NetBackup restores a symbolic link as root, NetBackup changes the owner and group to the original owner and group. When NetBackup restores a symbolic link as a nonroot user, the owner and group is set to the owner and the group of the person who performs the restore. Resetting the owner and group does not cause problems. When the UNIX system checks permissions, NetBackup uses the owner and group of the file to which the symbolic link points.

178 Policies Rules to indicate paths in the backup selections list

Hard links to directories

On most UNIX systems, only the root user can create a hard link to a directory. Some systems do not permit hard links and many vendors recommend that these links be avoided. NetBackup does not back up and restore hard-linked directories in the same manner as files:

During a backup, if NetBackup encounters hard-linked directories, the directories are backed up once for each hard link. During a restore, NetBackup restores multiple copies of the hard-linked directory contents if the directories do not already exist on the disk. If the directories exist on disk, NetBackup restores the contents multiple times to the same disk location.

Hard links to files

A hard link differs from a symbolic link in that a hard link is not a pointer to another file. A hard link is two directory entries that point to the same inode number. If the backup selection list includes hard-linked files, the data is backed up only once during a backup. NetBackup uses the first file name reference that is found in the directory structure. If a subsequent file name reference is found, it is backed up as a link to the name of the first file. Backup up only the link means that only one backup copy of the data is created, regardless of the number of hard links. Any hard link to the data works. For more information and examples, see Hard links to files (NTFS volumes or UNIX) on page 173.

UNIX raw partitions

Caution: Save a copy of the partition table before performing raw partition backups so that you retain the copy for reference before to a restore. To restore the raw partition, a device file must exist and the partition must be the same size as when it was backed up. Otherwise, the results of the restore are unpredictable.

Notes on UNIX raw partition backups

Use raw partition backups only if you can ensure that the files have not changed in any way during the backup. Or, in the case of a database, if you can restore the database to a consistent state by using transaction log files.

Policies Rules to indicate paths in the backup selections list

179

Do not perform backup archives of raw partitions on any client. An archive backs up the raw partition, then deletes the device file associated with the raw partition. The file system does not recover the space that the raw partition uses. Before backing up file systems as raw partitions, unmount the file system. Unmounting the file system allows buffered changes to be written to the disk. Also, it prevents the possibility that the file system would change during the backup. Use the bpstart_notify and the bpend_notify scripts to unmount and remount the backed-up file systems. The Cross mount points policy attribute has no effect on raw partitions. If the root partition is backed up as a raw partition and contains mount points to other systems, the file systems are not backed up. The other file systems are not backed up, even Cross mount points selected. For more information, see Cross mount points on page 103. The same is true for the Follow NFS policy attribute. NFS file systems that are mounted in a raw partition are not backed up. Nor can you back up raw partitions from other machines by using NFS mounts to access the raw partitions. The devices are not accessible on other machines through NFS. For more information, see Follow NFS on page 101. Specify the logical partition names for any disks that disk volume managers manage. (For example, Veritas Volume Manager (VxVm). For clients in a FlashBackup policy, refer to the NetBackup Snapshot Client Administrators Guide for the differences between Standard and FlashBackup policies.

When to use raw partition backups

If there are no file systems to back up and the disks are used in raw mode, back up the disk partitions as raw partitions. For example, databases are sometimes used in raw mode. Use bpstart_notify and bpend_notify scripts to provide the necessary pre- and post-processing of databases when they are backed up as raw partitions. You can also perform a raw partition backup of a disk partition used for file systems. A disadvantage of this method is that you must restore the entire partition to recover a single file (unless FlashBackup is in use). To avoid overwriting the entire partition, use the redirected restore feature to restore the raw partition to another raw partition of the same size. Then, copy individual files to the original file system. Raw partition backups are also useful for backing up entire disks. Since the file system overhead is bypassed, a raw partition backup is usually faster. The size of the raw partition backup is the size of the entire disk, regardless of whether the entire disk is used.

180 Policies Rules to indicate paths in the backup selections list

Specifying UNIX raw partitions in the backup selection list

To specify a UNIX raw partition in the policy backup selection list, enter the full path name of the device file. For example, on a Solaris system enter:
/devices/sbus@1,f8000000/esp@0,800000/sd@2,0:1h

Caution: Do not specify wildcards (such as /dev/rsd*) in pathnames for raw partition backups. Doing so can prevent the successful restore of entire devices, if there is overlap between the memory partitions for different device files. You can include raw partitions in the same backup selection list as other backups. For example: /home /usr /etc /devices/sbus@1,f8000000/esp@0,800000/sd@2,0:1h Note: NetBackup does not distinguish between full and incremental backups when it backs up a raw partition. The entire partition is backed up in both cases. Raw partition backups occur only if the absolute pathname in the backup selection list is a block or character special device file. You can specify either block or character special device files. Character special device files are often faster because character devices avoid the use of the buffer cache for accessed disk data. Test both a block and character special device file to ensure the optimum backup speed for your platform. Ensure that you specify the actual block- or character-device files. Sometimes these are links to the actual device files. If a link is specified, only the link is backed up. If the device files are reached while backing up /dev, NetBackup backs up only the inode files for the device, not the device itself.

Selecting a schedule backup type for a UNIX raw partition

To perform a raw partition backup, select Full backup for the Type of Backup from the Schedules tab. Any other backup type does not work for backing up raw partitions. For more information,see Type of backup on page 119.

Backup and restore of extended attribute files and named data streams
NetBackup can back up and restore the following file attributes:

Extended attribute files of the Solaris UNIX File System (UFS) and temporary file system (TMPFS)

Policies Rules to indicate paths in the backup selections list

181

Named data streams of the VxFS file system

NetBackup backs up extended attribute files and named data streams as part of normal file system backups. Extended attribute files and named data streams are normal files contained in a hidden attribute directory that relate to a particular base file. The hidden directory is stored within the file system, but can be accessed only by the base file to which it is related. To view which files have extended attributes on Solaris 9 (or greater) systems, enter: ls -@ Neither extended attribute files nor named data streams can be backed up or restored individually. Rather, the files are backed up and restored all at once along with the base file. Figure 4-9
File 1

Example of base file and extended attribute directory and files

File 1 is a base file on a Solaris or VxFS client Extended attributes backed up and restored as a group along with the base file

Hidden attribute directory for File 1 Extended attribute file 1 Extended attribute file 2 Extended attribute file 3 Extended attribute file 4

NetBackup client, media server, and master server versions

To back up or restore named data streams and extended attributes, the client, media server, and master server must run the following versions:

NetBackup clients must run:

HP 11.23 running VxFS 4.1 or greater. Note: Access control lists (ACLs) are not backed up unless running VxFS 5.0 or greater. AIX running VxFS 4.0 or greater. Note: ACLs are not backed up unless running VxFS 5.0 or greater. Solaris SPARC 8, 9, 10 running VxFS 5.0 or greater Solaris SPARC 9, 10 running VxFS 4.0 or greater

A NetBackup media server: Restores: Only NetBackup media servers at 5.0 or later can restore VxFS named data streams and Solaris extended attributes. Backups: A NetBackup media server of any version can successfully back up named data streams and Solaris extended attributes.

182 Policies Rules to indicate paths in the backup selections list

A NetBackup master server: A NetBackup master server of any version can back up and restore named data streams and Solaris extended attributes.

Ramifications of backing up extended attributes or named data streams

The presence of a large number of extended attribute files or named data streams may cause some degradation in backup and restore speed. The speed is affected since the base file and all associated files are backed up. The speed is especially affected in the case of incremental backups, during which NetBackup checks the mtime or ctime of each file individually.

Restoring extended attributes or named data streams

Restored attribute files and named data streams may replace existing files if Overwrite existing files is selected in the Backup, Archive, and Restore client interface. In the following example, File 1 is to be restored. Base file 1 currently possesses four extended attribute files.
File 1 Extended attribute file 1 Base file 1 Extended attribute file 2 Extended attribute file 3 Extended attribute file 4

The user restores File 1 from a backup that was created when File 1 possessed only three extended attribute files.
File 1 backup Extended attribute file 1 backup Extended attribute file 2 backup Extended attribute file 3 backup

Policies Rules to indicate paths in the backup selections list

183

Since Overwrite existing files is selected as a restore option, when the user restores File 1, extended attribute files 1, 2, and 3 are overwritten. Extended attribute file 4 remains and is not overwritten.
Restored file 1 Restored extended attribute file 1 Restored extended attribute file 2 Restored extended attribute file 3 Extended attribute file 4

If an attempt is made to restore:

the extended attribute files to any non-Solaris 9 client (or greater), or named data streams to any non-VxFS 4.0 client,

an error message appears in the Restore Monitor to inform the user that the extended attributes or named data streams are not restored. NetBackup then continues with the restore job. To disable the restore of extended attribute files and named data streams To disable the restore of extended attribute files and named data streams, add an empty file named IGNORE_XATTR to the client in the following directory: /usr/openv/netbackup/ The addition affects only Solaris 9 or VxFS 4.0 clients. File IGNORE_XATTR was formerly known as IGNORE_XATTR_SOLARIS. Note: Only the modified GNU tar that is supplied with NetBackup is able to restore the extended attributes or named data streams to a client. For more information, see Reading Backup Images with tar in NetBackup Administrators Guide, Volume II.

Note: Extended attributes and named data streams cannot be compressed.

Path rules for NetWare NonTarget clients

For NetWare systems that are running the NonTarget version of NetBackup client software, specify the paths in the following form: /SMDR/TSA/TS/resources/directory/file

184 Policies Rules to indicate paths in the backup selections list

Where:

SMDR (Storage Management Data Requestor) is the name of the NetWare file server that is running the SMDR.NLM that is used for backups. (NLM means NetWare-loadable module.) TSA (Target Service Agent) is a NetWare software module that prepares the data for backup or restore by the SMDR. The type of TSA that is used depends on the data. For example, NetWare file systems and DOS workstations each have TSAs. TS is the Target Service, which is the NetWare entity that contains the data that the selected TSA handles. For example, in the case of the DOS TSA (tsasms.com) it is a DOS workstation. In the case of a NetWare file system TSA, it is the system with the NetWare file systems to be backed up. resources are the specific resources on the target service. For example, it can be NetWare file systems such as BINDERY, SYS, and USER. directory/file is the directory and file that are in the resource (if it is a path to a specific file). Give the server access to each path or the scheduled backup fails. To provide this access, use the Allowed scheduled access command on the Backup menu in the NetBackup interface on the NetWare client. For more information, see the NetBackup for Novell NetWare Client Administrators Guide. Enter one path per line. Begin all paths with a forward slash (/). Precede each component in the path with a forward slash. If the last component in the path is a directory, follow it with a forward slash (/). The trailing slash is not required but is a reminder that the path points to a directory instead of a file.
/TILE/TILE.NetWare File System/TILE/SYS/DOC/

Observe the following rules for paths:

If the last component is a file, include the file extension and omit the slash from the end of the name.
/TILE/TILE.NetWare File System/TILE/SYS/DOC/TEST.TXT

All components in a path must show upper and lower case letters as they appear in the actual path on the client. Wildcard usage is the same as for Windows clients. For more information, see Using wildcards in NetBackup on page 632. To back up all NetBackup for NetWare clients that are in the policy, enter only one forward slash (/) on a line:

Policies Rules to indicate paths in the backup selections list

185

To back up an entire NetBackup for NetWare client, enter a forward slash (/) followed by the client name and another forward slash:
/TILE/

The following example backs up SYS, BINDERY, and USER file systems under the file system TSA on a client that is named tile:
/TILE/TILE.NetWare File System/TILE/SYS/ /TILE/TILE.NetWare File System/TILE/BINDERY/ /TILE/TILE.NetWare File System/TILE/USER/

Note that the Allowed scheduled access command on the NetBackup NetWare client Backup menu must also specify access to these paths. See the NetBackup for Novell NetWare Client Administrator's Guide.

Path rules for NetWare Target clients

For NetWare clients that are running the Target version of NetBackup client software, use the following format for the paths: /target/ Where target is the name of a target that is defined on the NetBackup for NetWare client. For more information, see the NetBackup Administrators Guide for Novell NetWare Clients.

Enter one target per line. Begin all target names with a forward slash (/). All target names must be in upper case. Wildcard usage is the same as for Windows clients. For more information, see Using wildcards in NetBackup on page 632.
/NETWARE/ /SYSTEM/ /BINDERY/

The following example backs up the targets: NETWARE, SYSTEM, and BINDERY:

Path rules for clients running extension products

Path rules for the NetBackup clients that are running separately-priced options are covered in the NetBackup guide for the product. (For example, Snapshot Client or NetBackup for MS-Exchange.)

Backup selections list directives: General discussion

The backup selections list can contain the directives that signal NetBackup to perform specific actions when it processes the files in the selections list.

186 Policies Rules to indicate paths in the backup selections list

The available directives depend on the policy type and whether the Allow multiple data streams attribute is enabled for the policy. The following example is a backup selections list that contains the NEW_STREAM directive. The example is from an MS-Windows-NT policy with Allow multiple data streams enabled:
NEW_STREAM D:\Program Files NEW_STREAM C:\Winnt

The NEW_STREAM directive is discussed in Backup selections list directives for multiple data streams on page 189.

ALL_LOCAL_DRIVES directive
Use the ALL_LOCAL_DRIVES directive to back up all local drives except for those drives that use removable media. The ALL_LOCAL_DRIVES directive applies to the following policy types:

Standard (except for NetWare target clients) MS-Windows-NT NetWare (NonTarget clients only) However, ALL_LOCAL_DRIVES is not allowed for NetWare policy types if Allow multiple data streams is also used. For more information, see ALL_LOCAL_DRIVES directive and multiple data streams on page 192.

For information on files and the directories that NetBackup automatically excludes from backup, see Files that are excluded from backups by default on page 194.

SYSTEM_STATE directive
The System_State:\ directive is a valid directive only to back up Windows 2000/XP machines. If the machine is not Windows 2000/XP or a Windows 2003 Server, the System_State:\ directive does not have any effect. Windows 2003 Server machines recognize the System_State:\ directive and behave as if following the Shadow Copy Components:\ directive. A message informs the user that this directive translation has occurred. If the machine is Windows 2000/XP, the list of items that are backed up can include the following:

Active Directory COM+ Class Database Cluster Database IIS Database

Policies Rules to indicate paths in the backup selections list

187

Registry Boot Files and Protected Files SYSVOL Certificate Server

On Windows 2000 machines, the registry is backed up in the process of regular file system backups. The files that comprise the registry can be found in the following location: %SystemRoot%\SYSTEM32\Config At a minimum, the following files are backed up as part of the registry:

DEFAULT SAM SOFTWARE SECURITY SYSTEM

Shadow copy components:\ directive

The Shadow Copy Components:\ directive affects Windows 2003 Server machines that use the Volume Shadow Copy components. The Shadow Copy Components:\ directive specifies that all of the Volume Shadow Copy component writers get backed up. This directive ensures that all of the necessary components are backed up. The Volume Shadow Copy components include the following:

System State writers, which can include:

System Files COM+ Class Registration Database SYSVOL Active Directory Cluster Quorum Certificate Services Registry Internet Information Services Removable Storage Manager Event Logs Windows Internet Name Service

System Service writers, which can include:

188 Policies Rules to indicate paths in the backup selections list

Windows Management Instrumentation Remote Storage Dynamic Host Configuration Protocol Terminal Server Licensing Background Intelligent Transfer Service

User Data writers, which include any items that are not required by the machine to operate. For example, Active Directory Application Mode. Other Data writers, a category that is intended for future NetBackup releases.

Directives for multiple data streams

If the Allow multiple data streams general attribute is set for a policy, the following directives can be used in the backup selections list:

NEW_STREAM ALL_LOCAL_DRIVES UNSET UNSET_ALL

For usage rules, see Backup selections list directives for multiple data streams on page 189.

Directives for specific policy types

Some directives apply only to specific policy types and can appear only in backup selections lists for those policies. NetBackup passes policy-specific directives to the clients along with the backup selections list. The clients then perform the appropriate action according to the directive. The following policy types have their own backup selections list directives:

AFS FlashBackup NDMP Lotus-Notes MS-Exchange-Server

For example, the following directives can appear only in the backup selections list of an AFS policy: CREATE_BACKUP_VOLUMES SKIP_SMALL_VOLUMES

Policies Rules to indicate paths in the backup selections list

189

Except for AFS, these policy types can be used when their associated separately-priced option is installed. For information on other policy types and associated backup selections list directives, see the NetBackup guide for the option. Caution: Include policy-specific directives only in backup selections lists for the policies that support the directives or errors can occur.

Backup selections list directives for multiple data streams

If the Allow multiple data streams attribute is enabled for the policy, the following directives can be used to control how NetBackup creates backup streams:

NEW_STREAM ALL_LOCAL_DRIVES UNSET and UNSET_ALL

Note: For best performance, use only one data stream to back up each physical device on the client. Multiple concurrent streams from a single physical device can adversely affect backup times. The heads must move back and forth between tracks containing files for the respective streams.

NEW_STREAM directive and multiple data streams

The NEW_STREAM directive is recognized only if Allow multiple data streams is set for the policy. NEW_STREAM directives are ignored if Allow multiple data streams is not set. If this directive is used in a backup selections list, the first instance of it must be on the first line. If it appears on the first line, it can also appear elsewhere in the list. The presence of NEW_STREAM on the first line of the backup selections list determines how the backup is performed: in administrator-defined streaming or in the auto-discovery streaming mode.

Administrator-defined streaming mode

If NEW_STREAM is the first line of the backup selections list, the backup is performed in the administrator-defined streaming mode. The following actions occur:

190 Policies Rules to indicate paths in the backup selections list

The backup is split into a separate stream at each point in the backup selections list where the NEW_STREAM directive occurs. All file paths between NEW_STREAM directives belong to the same stream. The start of a new stream (a NEW_STREAM directive) defines the end of the previous stream. The last stream in the backup selections list is terminated by the end of the backup selections list.

Note: In the following examples, assume that each stream is from a separate physical device on the client. Multiple concurrent streams from a single physical device can adversely affect backup times. The backup time is longer if the heads must move back and forth between tracks containing files for the respective streams. For example, consider the following backup selections list:
NEW_STREAM /usr /lib NEW_STREAM /home /bin

This backup selection list contains two data streams:

The NEW_STREAM at the top of the list invokes administrator-defined streaming and starts the first stream. This stream backs up /usr and /lib. The second NEW_STREAM starts a second data stream that backs up /home and /bin.

If a backup selections list entry is added to a stream, the entry is not backed up until the schedule is due for the policy. If the next backup due is an incremental, only the files that have changed are backed up. To ensure that a new entry gets a full backup the first time, add it to a new stream. NetBackup performs a full backup of new streams that are added to the backup selections list. In the previous example, assume you add /var after /bin If an incremental backup is due that night, only changed files in /var are backed up. Add a NEW_STREAM directive before /var, to perform a full backup of all files in /var, regardless of when the files were last changed.

Policies Rules to indicate paths in the backup selections list

191

Auto-discovery streaming mode

Auto-discovery streaming mode is invoked if NEW_STREAM is not the first line of the backup selections list. The list must contain either the ALL_LOCAL_DRIVES directive or wildcards. In this mode, the backup selections list is sent to the client, which preprocesses the list and splits the backup into streams as follows:

If the backup selections list contains the ALL_LOCAL_DRIVES directive, NetBackup backs up the entire client. However, NetBackup splits each drive volume (Windows) or file system (UNIX) into its own backup stream. For more information, see ALL_LOCAL_DRIVES directive and multiple data streams on page 192. If wildcards are used, the expansion of the wildcards results in one stream per wildcard expansion. Wildcard usage is the same as for Windows clients. For more information, see Using wildcards in NetBackup on page 632.

If the backup selections list contains neither the ALL_LOCAL_DRIVES directive nor wildcards, the auto-discovery mode is not used. In this case, the server preprocesses rather than the client. In this case, each file path in the backup selections list becomes a separate stream. Auto-discovery streaming mode applies to:

Standard and MS-Windows-NT policy types, except for NetWare clients. Clients that are running NetBackup 3.2 or later.

Before the backup begins, the client uses auto-discovery to preprocess the backup selections list to determine how many streams are required. The first backup that a policy performs preprocesses the backup selections list. However, preprocessing does not necessarily occur before every backup. Whether or not it occurs depends on the preprocess interval.

Setting the preprocess interval for auto-discovery

The preprocess interval applies only to auto-discovery mode and specifies how often preprocessing occurs. When a schedule is due and auto-discovery is used, NetBackup checks whether the previous preprocessing session occurred within the preprocess interval:

If yes, NetBackup does not run preprocessing on the client. If no, NetBackup preprocesses the client and makes required changes to the streams.

If necessary, you can change the interval by using the bpconfig command. The default is four hours and is a good value for most of the sites that run daily backups. If the interval is too long or too short, the following can occur:

Too long of an interval can result in new streams not being added early enough and the potential of missed backups. For example, assume the

192 Policies Rules to indicate paths in the backup selections list

preprocess interval is set to four hours and a schedule has a frequency of less than four hours. A new stream may be omitted from the next backup because the preprocessing interval has not expired when the backup is due.

Too short of an interval can cause preprocessing to occur often enough to increase scheduling time to an unacceptable level. A short interval is most likely to be a problem when the server must contact a large number of clients for preprocessing.

The form of the bpconfig command to use for changing the interval is: /usr/openv/netbackup/bin/admincmd/bpconfig [-prep hours] For more information on the bpconfig command, see NetBackup Commands for UNIX and Linux.

ALL_LOCAL_DRIVES directive and multiple data streams

The ALL_LOCAL_DRIVES directive applies only to Standard (except for NetWare target clients), MS-Windows-NT, and NetWare policies. The clients must run NetBackup 3.2 or later software. If this directive is used, this directive must be the only entry in the backup selections list for the policy. That is, no other files or directives can be listed. The action that ALL_LOCAL_DRIVES causes depends on whether Allow multiple data streams is enabled for the policy.

If Allow multiple data streams is enabled, the ALL_LOCAL_DRIVES directive applies only to Standard (except for NetWare clients) or MS-Windows-NT policy types. NetBackup backs up the entire client, then splits the data from each drive (Windows) or file system (UNIX) into its own backup stream. NetBackup periodically preprocesses the client to make necessary changes to the streams. For more information, see Setting the preprocess interval for auto-discovery on page 191. If Allow multiple data streams is not enabled, NetBackup backs up the entire client and includes all drives and file systems in the same stream.

Caution: Do not select Cross mount points for policies where you use the ALL_LOCAL_DRIVES directive.

ALL_LOCAL_DRIVES example 1
Assume that Allow multiple data streams is enabled in the auto-discovery mode. Assume that the client is a Windows system with two drive volumes, C:\ and D:\. The backup selections list contains: ALL_LOCAL_DRIVES

Policies Rules to indicate paths in the backup selections list

193

For this backup selections list, NetBackup generates:

One stream for C:\ One stream for D:\

For a UNIX client, NetBackup generates a stream for each file system. SYSTEM_STATE is also backed up because SYSTEM_STATE is included in the ALL_LOCAL_DRIVES directive.

ALL_LOCAL_DRIVES example 2
Assume that Allow multiple data streams is not enabled. Assume that the client is a Windows system with two drive volumes, C:\ and D:\. The backup selections list contains: ALL_LOCAL_DRIVES Here, NetBackup backs up the entire client in one data stream that contains the data from both C:\ and D:\. SYSTEM_STATE is also backed up because SYSTEM_STATE is included in the ALL_LOCAL_DRIVES directive.

UNSET, UNSET_ALL directives, and multiple data streams

All policy-specific directives that are passed to a client in a stream are passed in all subsequent streams. The UNSET and UNSET_ALL directives change this behavior. These directives are recognized only if the Allow multiple data streams option is set for the policy. For more information, see Directives for specific policy types on page 188.

UNSET
The UNSET directive interrupts a policy-specific directive so it is not passed with any additional streams. The directive that was unset can be defined again later in the backup selections list to be included in the current and the later streams.

UNSET_ALL
UNSET_ALL has the same effect as UNSET but unsets all policy-specific directives in the backup selections list that have been defined up to this point.

UNSET example
In the following backup selections list, the set command is a client-specific directive that is passed to the first and all subsequent streams.
NEW_STREAM set destpath=/etc/home /tmp /use NEW_STREAM

194 Policies Rules to indicate paths in the backup selections list

/export NEW_STREAM /var

For the set command to be passed to the first two streams only, use UNSET or UNSET_ALL at the beginning of the third stream. At this location, it prevents SET from being passed to the last stream.
NEW_STREAM set destpath=/etc/home /tmp /use NEW_STREAM /export NEW_STREAM UNSET_ALL [or UNSET set destpath=/etc/home] /var

Excluding files from backups

By default, a number of files and file states are not backed up by NetBackup. You can also exclude specific files from automatic backups by specifying the files or directories in an exclude list on the client.

Files that are excluded from backups by default

By default, NetBackup does not back up the following files:

NFS files or directories. To back up NFS files, enable Follow NFS. Files or directories in a different file system. To backup up files in a different file system, enable Cross mount points. Files or directories with path lengths longer than 1023 characters. Files or directories in which the operating system does not return inode information (the lstat system call fails). Directories that NetBackup cannot access (the cd command cannot access). On the disks that Storage Migrator manages; on migrated files or directories where Storage Migrator does not return inode information (mig_stat fails). Note that NetBackup Server does not support Storage Migrator. Socket special files. (Named pipes are backed up, however.) Locked files when locked by an application that currently has the file open. Busy files. If a file is open, NetBackup backs up the last saved version of the file.

NetBackup automatically excludes the following file system types on most platforms:

Policies Rules to indicate paths in the backup selections list

195

cdrom (all UNIX platforms) cachets (AIX, Solaris, SGI, UnixWare) devpts (Linux) mntfs (Solaris) proc (UNIX platforms; does not exclude automatically for AIX, so /proc must be added manually to the exclude list. If /proc is not added manually, partially successful backups may result with the ALL_LOCAL_DRIVES directive on AIX) tmpfs (Linux) usbdevfs (Linux)

Excluding files from automatic backups

On most NetBackup clients, you can exclude specific files from automatic backups by specifying the files in an exclude list on the client. You can also create an include list to add a file(s) specifically that would be excluded. The include list is useful to exclude an entire directory except for one file, for example. Note: Exclude and include lists do not apply to user backups and archives. The method for specifying files in the exclude and include lists depends on the type of client:

On Microsoft Windows clients, specify exclude and include lists in the Backup, Archive, and Restore client interface: Start Backup, Archive, and Restore and click File > NetBackup Client Properties. Go to the Exclude list or Include list tab. For further instructions, see the NetBackup users guide for the client. The Exclude list or the Include list can also be specified through the NetBackup Administration Console on the master server. For more information, see Exclude Lists properties on page 414. On NetWare target clients, the exclude and include lists are specified when the targets are added. See the NetBackup users guide for the client. On UNIX clients, you create the exclude and include lists in the following files on the client: /usr/openv/netbackup/exclude_list /usr/openv/netbackup/include_list

196 Policies Disaster Recovery tab

Disaster Recovery tab

The Disaster Recovery tab appears for those policies that are based on the Catalog Backup policy type (NBU-Catalog). The Disaster Recovery tab contains options for configuring disaster recovery protection methods for the catalog data. Caution: Do not save the disaster recovery information to the local machine. Symantec recommends that the image file be saved to a network share or a removable device. Figure 4-10 Disaster Recovery tab

Note: Vault protects the disaster recovery data by sending the data to the Vault site as an email attachment of the Vault report email. The separately-priced Vault option must be installed.

Policies Disaster Recovery tab

197

Path
The path to the directory where the disaster recovery information is saved. Specify a local directory or NFS share.

Logon
The logon and password information that is required to access the NFS share.

Password
The password that is required to log on to the share. Note: Logon and password fields are enabled: - When the path begins with \\ , which indicates a UNC share path. - When NetBackup does not have write access to the location that the user specifies.

Send in an email attachment

Symantec recommends that the disaster recovery report be sent to at least one email address. The email address where the information is sent. To send the information to more than one address, separate email addresses with a comma: email1,email2 To ensure that the system is set up to send mail, see Setting up email notifications on page 438.

Identifying critical policies

A policy that is listed on the Critical Policies list is considered crucial to the recovery of a site in the event of a disaster. The NetBackup Disaster Recovery report lists all of the media that is used for backups of critical policies, including the most recent full backup. The NetBackup Disaster Recovery wizard warns you if any media for critical policies are not available. Note: Critical policies should use only incremental or full backup schedules. The Disaster Recovery report lists only the media for incremental and full backup schedules.

198 Policies Disaster Recovery tab

Note: When NetBackup is running with Vault, Vault includes the disaster recovery data in the Vault Recovery Report.

Policies Creating a Vault policy

199

Creating a Vault policy

A Vault policy differs from other policies in the following respects:

You must specify Vault as the policy type. You do not specify clients for Vault policies, therefore the Clients tab does not appear. Specify a Vault command in the backup selections list instead of a file(s).

To create a Vault policy 1 2 3 4 5 In the NetBackup Administration Console, expand NetBackup Management > Policies. Select Actions > New > Policy. Type a unique name for the new policy in the Add a New Policy dialog. Click OK. On the Attributes tab, select Vault as the policy type. On the Schedules tab, click New to create a new schedule. The type of backup defaults to Automatic. Complete the schedule. Note: The Clients tab does not appear for Vault policy types. 6 On the Backup Selections tab, enter one of two Vault commands:

Use vltrun to specify the robot, vault name, and profile for the job. The vltrun command accomplishes all the steps necessary to select, copy, and eject media. If the vault profile name is unique, use the following format: vltrun profile_name If the vault profile name is not unique, use the following format: vltrun robot_number/vault_name/profile_name

Use the vlteject command to eject media or to generate reports for completed Vault sessions. For example: vlteject -eject -report [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] Both commands are located in the following directory: /usr/openv/netbackup/bin/ For more information on Vault names, profile names, and command usage, see the Vault Administrators Guide.

Click OK.

200 Policies Performing manual backups

Performing manual backups

A manual backup is user-initiated and based on a policy. A manual backup is useful in the following situations:

To test a configuration. To back up a client that missed the regular backup. To back up a client before installing new software to preserve the old configuration. To preserve records before a special event such as a company split or merger. To back up quarterly or yearly financial information.

In some cases, it may be useful to create a policy and schedule that you use only for manual backups. Create a policy for manual backups only by creating a policy with a single schedule that has no backup window. Without a backup window, the policy can never run automatically. To perform a manual backup 1 2 In the NetBackup Administration Console, expand NetBackup Management > Policies. Select the policy name in the middle pane. Select Actions > Manual Backup. (The Active. Go into effect at option must be enabled to perform a manual backup.) The Manual Backup dialog appears. For more information, see Active. Go into effect at on page 99.

Note: If the Go into effect property is set for a future date and time, the backup does not run. 3 In the Manual Backup dialog, select the schedule and the clients that you want to back up. If you do not select any schedules, NetBackup uses the schedule with the highest retention level. If you do not select any clients, NetBackup backs up all clients. User schedules do not appear in the schedules list. A user schedule cannot be manually backed up because they do not have a backup selection list (the user selects the files). Click OK to start the backup.

Policies More about synthetic backups

201

More about synthetic backups

Synthetic backups can be written to tape storage units or disk storage units, or a combination of the two. The following sections describe how synthetic backups can be used in your NetBackup configuration.

Processing takes place on master and media server(s) instead of client

During a traditional full backup, all files are copied from the client to a master server or a media server. The files are copied even though those files may not have changed since the last incremental backup. When NetBackup creates a synthetic full backup, NetBackup detects whether new or changed files have been copied to the media server during the last incremental backup. The client does not need to be running to combine the full backups and the incremental backups on the media server to form a new, full backup. The new, full synthetic backup is an accurate representation of the clients file system at the time of the most recent full backup.

Reduces the network traffic

Network traffic is reduced because files are transferred over the network only once. After the backup images are combined into a synthetic backup, the tapes or disk that contain the component images can be recycled or reclaimed. Synthetic backups can reduce the number of tapes or disk space in use.

Supports disk environments

Synthetic backups can be created in the environments that are comprised exclusively of disk storage units.

Uses drives more effectively

Synthetic backups can be written to tape storage units or disk storage units, or a combination of both. If the backups use tape, the backups can be synthesized when drives are not generally in use. For example, if backups occur primarily at night, the drives can synthesize full backups during the day.

Policy considerations and synthetic backups

Selecting the synthetic backup option
The Synthetic Backup option is available under the following conditions:

The policy type must be either Standard or MS-Windows-NT. The Collect True Image Restore Information With Move Detection option must be selected on the Policy Attributes tab. For more information, see Collect true image restore information with move detection on page 109.

202 Policies More about synthetic backups

The schedule that is created for a synthetic backup must have Synthetic Backup selected. The master servers, media servers, and clients must all have NetBackup version 5.0 or later installed to synthesize backups. One of the following must be available:

Disk storage unit(s) with adequate space available. Tape library(s) with multiple drives to read and write. For more information, see Disk storage unit considerations and Tape storage unit considerations on page 207. A combination of disk storage unit(s) and tape library(s).

Schedules to include in a policy for synthetic backups

A policy for synthetic backups must contain at least three types of schedules:

At least one traditional, full backup must be run successfully to create a full image. The synthetic backup jobs fails if there is not at least one previous full image. Schedule(s) for incremental backups. Incremental backups are necessary to capture the changes in the file system since the last full or incremental backup. The synthetic backup job receives a status code of 1 for a policy that contains full or incremental synthetic backup schedules, but no incremental backup schedules. The synthetic backup synthesizes all of the incremental backups to create a new full or cumulative backup image. Therefore, the synthetic backup is only as current as the last incremental backup.

Note: To configure a synthetic cumulative backup for any clients that are archive bit-based (default), use only differential incremental backups for the traditional, non-synthesized backups.

One full and/or one cumulative backup schedule with the Synthetic Backup option selected.

Adding clients to a policy for synthetic backups

After clients are added to a synthetic backup policy, run a traditional, full backup of the policy. A traditional backup is necessary before a synthetic backup can be created. Since Collect True Image Restore Information With Move Detection is required for synthetic backups, all of the clients in the policy must support TIR.

Policies More about synthetic backups

203

Two types of synthetic backups

Two types of synthetic backup images can be created: synthetic full and cumulative synthetic. The images that are used to create the synthetic image are known as component images. For instance, the component images in a synthetic full are the previous full image and the subsequent incremental images.

Synthetic full backups

The following figure illustrates the creation of synthetic full backups (B, C, D) from an existing full backup (A). It also shows the incremental backups between full backups. Figure 4-11
Traditional full backup to disk (Sunday)

Creation of synthetic full backups

Synthetic full backup to disk (Sunday)

Incremental backups to disk (Mon-Sat)

Sundays Synthetic full Backup

Synthetic full backup (Sunday)

Incremental backups (Mon-Sat)

Synthetic full backup (Sunday) Sundays synthetic full backup

Incremental backups (Mon-Sat)

The traditional full backup (A) and the incremental backups are created in the traditional manner: data is scanned, then copied from the clients file system to the backup media. The synthetic backups do not interact with the client system at all, but are instead synthesized on the media server.

204 Policies More about synthetic backups

For a discussion of synthetic cumulative incremental backups, see Synthetic cumulative incremental backups on page 204.

Synthetic full backup usage example

1 Create a Standard or MS-Windows-NT policy for the clients (5.0 or later) you want to back up. Include the following schedules:

A schedule for one full, traditional backup to run at least once. A schedule for daily (Monday through Saturday) differential incremental backups. A schedule for weekly full, synthetic backups.

2 3

Make sure that the traditional full backup runs. If the backup does not complete, run the backup manually. Per schedule, run daily, differential incremental backups for the clients throughout the week. The last incremental backup for the week runs on Saturday. Per schedule, run synthetic full backups for the clients on subsequent Sundays.

Note: The synthetic full backups in this scenario are only as current as the Saturday incremental backup.

Synthetic cumulative incremental backups

The scenario to create a synthetic, cumulative incremental backup is similar to the scenario to create a synthetic full backup. Remember, a cumulative incremental backup includes all changes since the last full backup. If a cumulative incremental backup exists that is newer than the last full backup, a synthetic cumulative backup image is produced by consolidating the following component backup images:

All differential incremental backups that were taken since the last cumulative backup. The last cumulative incremental backup. If no cumulative incremental backup is available, only the differential incremental backups are used for the synthetic image.

The following figure illustrates the creation of synthetic cumulative incremental backups (A, B, C) from the latest cumulative incremental backup. It also shows the subsequent differential incremental backups.

Policies More about synthetic backups

205

Figure 4-12

Creation of synthetic cumulative backups

Synthetic cumulative incremental backup to tape (Sunday) A

Cumulative and differential incremental backups to disk (Mon-Sat)

Sundays synthetic cumulative Incremental backup A B

Synthetic cumulative incremental backup (Sunday)

Incremental backups (Mon-Sat)

Sundays synthetic cumulative incremental backup B

Synthetic cumulative incremental backup (Sunday)

Incremental backups (Mon-Sat)

Synthetic cumulative backup usage example

1 Create a Standard or MS-Windows-NT policy for the clients (5.0 or later) you want to back up. Include the following schedules:

A schedule for one full, traditional backup to run at least once. A schedule for daily (Monday through Saturday) differential incremental backups. A schedule for weekly cumulative incremental synthetic backups.

2 3 4

Make certain that the traditional full backup runs. If the backup does not complete, run the backup manually. Per schedule, run daily differential incremental backups for the clients throughout the week. The last incremental for the week runs on Saturday. Per schedule, run synthetic cumulative incremental backups for the clients on subsequent Sundays.

206 Policies More about synthetic backups

Note: The synthetic cumulative backups in this scenario are only as current as the Saturday incremental backup.

Recommendations for synthetic backups

Scenario in which synthesized backups are beneficial
The synthetic full backup is a scalable solution for backing up remote offices with manageable data volumes and low levels of daily change. If the clients experience a high rate of change daily, the incremental backups are too large. In this case, a synthetic backup is no more helpful than a traditional full backup.

Refrain from multiplexing backups that will be synthesized

Do not synthesize multiplexed backups because it is inefficient. To synthesize multiplexed client images requires multiple passes over the source mediaone per client.

Synthesized backups and multistreaming

Performance issues occur if multiple streams are selected for synthesized backups. The issues are similar to those encountered while multiplexing synthesized backups problems. Back up to disk whenever possible to improve multiple stream performance issues.

Reducing the gap between the last incremental backup and the synthesized backup
Since a synthetic backup does not involve direct contact with the client, a synthetic backup is only as current as the last incremental backup. If there is a concern to reduce a potential gap in backup coverage, run an incremental backup before the synthetic backup. Note: Only frequency-based schedules allow an incremental backup and a synthetic backup to run on the same day. Calendar-based schedules are dependant on one another. If a daily incremental schedule runs earlier in the day, the synthetic cumulative backup does not run later that same day (00:00:0023:59:59). For more information, see Frequency schedule type on page 128 and Calendar schedule type on page 128.

Disk storage unit considerations

Disk-based images are more efficient for synthesizing. For example, NetBackup processes the newest component images first in a synthesized backup, followed

Policies More about synthetic backups

207

by sequentially older images. When two or more component images have been written to the same tape, the tape movement may be somewhat inefficient compared to disk-based images.

Tape storage unit considerations

For tape backups, separate tapes are required. The tape for the synthetic image must be different from the tape where the component images reside. The maximum drive usage applies only to the drive that is needed for writing the synthetic backup. If any of the component images reside on tape, an additional drive is needed for reading. If a single tape drive device is used to generate synthetic images, component images should be placed in a hard drive location first. In that way, a synthetic image can be generated with the single tape drive device.

Notes on synthetic backups

Test findings regarding synthetic backups

The time it takes to run a synthetic full backup does not increase significantly over time. Synthetic full backups are generated more quickly when built from disk-based incremental backups. If the synthetic full backup is also generated on disk, the run time is even faster. The disk copy can then be duplicated to tape.

Test findings regarding restores from synthetic backups

The time that is required to perform a restore from a synthetic backup does not increase significantly over time. The restore times for both a complete synthetic backup and for a single file is the same. It is the same whether the restore is from a traditional backup or from a synthetic backup. The restore time of a single directory may increase over time when sourced from synthetic backups. The restore time depends on the pattern of file changes within the directory. Contrast a traditional full backup, which stores the files in file system order, with a synthetic full backup, which stores the files in last-file-accessed order. The synthetic full contains the newest files at the front of the media and the unchanged files at the end. Over time, the processing order introduces the potential for fragmentation of a single directory across the synthetic full image.

208 Policies More about synthetic backups

Note that this scenario is limited to single directory restores. Single file restores and full image restores from synthetic fulls are equal or better than from traditional full backups, as noted in previous bullets.

General notes

Synthetic backups are supported on all media server platforms and tier one master server platforms. The option to create multiple copies is not allowed for synthetic backups. Synthetic backups are not supported if any of the component images are encrypted. A user-generated backup cannot be used to generate a synthetic image. A backup that is generated from a User Backup schedule or a User Archive schedule cannot be used as one of the components of a synthetic backup.

Synthetic backup jobs create two sets of catalog files

When a synthetic backup job is run, two sets of catalog files are created: an image file and one or more .f files. 1 The first set is named with the timestamp of the most recent incremental + 1. This set represents the actual synthetic backup image, which is as recent as the most recent incremental. The second set is named with the current timestamp. This set is used to mark the time the synthetic backup job was run. It does not contain any file data.

Do not manually remove any of these catalog files. The catalog files are automatically expired after the retention period as specified in the schedule for the policy. The two sets of catalogs have the same expiration times. For more information, see Retention on page 138.

Policies More about synthetic backups

209

For example:
Catalog after incremental backup jobs run: XDisk_1064417510_INCR XDisk_1064417510_INCR.f XDisk_1064420508_INCR XDisk_1064420508_INCR.f XDisk_1064421708_INCR XDisk_1064421708_INCR.f

After the synthetic backup job runs: XDisk_1064421709_FULL First set: XDisk_1064421709_FULL.f Second set: XDisk_1064424108_FULL

Synthetic full backup image Current time

Timestamp differences
The catalog for a synthetic image usually has a timestamp one second later than the most recent incremental component image. The timestamp may be more than one second later if there were possible image name conflicts.

True image restore and synthesized backups

Since the Collect true Image restore information with move detection policy property must be enabled for synthetic backups, all clients that are included in the policy must support TIR. For more information, see Collect true image restore information with move detection on page 109. The Keep true image restoration (TIR) information property indicates how long TIR information in the image catalog is kept before it is pruned (removed). This property is located in the master server Clean-Up host properties. However, if a synthetic full and/or synthetic cumulative schedule has been defined in the policy, the TIR information is pruned from the component images until a subsequent traditional or synthetic full or cumulative backup image has been generated successfully. Consider a situation where Keep true image restoration (TIR) information host specifies that TIR information is pruned from the catalog after two days. On the third day the TIR information is pruned only if a traditional or synthetic full backup image has been generated. If the TIR information has been pruned from a component image and you accidentally expire the most recent synthetic image, rerun the synthetic backup job to restore automatically the TIR information to the catalog. In case the TIR information cannot be restored due to bad, missing, or vaulted media, the

210 Policies More about synthetic backups

synthetic backup job fails with error code 136 (TIR info was pruned from the image file). If the problem is correctable, run the synthetic backup again. For more information, see Keep true image restoration (TIR) information on page 384.

Checkpoint restart and synthesized backups

If Checkpoint Restart is indicated for the policy, the backups that are produced with the synthetic backup schedule are not checkpointed. This option is enabled if Take checkpoints on the policy Attributes tab is enabled. If Take checkpoints is enabled for a synthetic backup, the property has no effect.

Change journal and synthesized backups

If the Windows client host property, Use Change Journal in Incrementals, is enabled, the property has no effect when the client is backed up using the synthetic backup schedule. For more information, see Use change journal in incrementals on page 403.

Displaying synthetic backups in the Activity Monitor

A synthetic job is distinguished from a traditional full backup by the notation that is indicated in the Data Movement field of the Activity Monitor. Synthetic jobs display Synthetic as the Data Movement type while traditional backups display Standard.

Logs produced during synthetic backups

When a synthetic backup is scheduled, NetBackup starts the bpsynth program to manage the synthetic backup process. bpsynth plans how the synthetic backup is built from the previous backup images. If needed, bpsynth then schedules the tape drive resources that are needed for the synthetic backup. If the required resources are not available, the job fails with a status code that indicates that a resource is needed. If the resources can be obtained eventually but not immediately, the synthetic job waits until the resources become available. This could happen if a drive is used by a backup or a restore, or by another synthetic backup job. bpsynth passes information to programs bptm and bpdm to cause tape and disk images to be read or written. Catalog information is managed using bpdbm. Each of these programs has a debug log file in the logs directory. If problems occur with synthetic backups, the following debug logs are required to diagnose the problem:

On the master server: bpsynth, bpdbm, and the log files located in /usr/openv/logs as described in the NetBackup Troubleshooting Guide.

Policies More about synthetic backups

211

On the media server(s): bptm (if any tape images), bpdm (if any disk images), bpcd Note that several media servers may be involved if the component images are on different nodes.

However, bpsynth is used for each stream or client. This can be inefficient with tape images since bpsynth needs a tape drive to write the new image. Also, bpsynth may use the same component image volumes. One may have to complete before the next one proceeds.

Synthetic backups and directory and file attributes

For a synthetic backup to include directory and the file attribute changes, the change must first be picked up by a component incremental backup. (For example, changes like access control lists (ACLs)

UNIX: Changing an objects ACL changes the ctime (inode change time) for the object but not the mtime (data modification time). Since mtime triggers incremental backups, the ACL change is not reflected in an incremental backup, and therefore not in a synthetic full backup. To include ACL changes in backups, enter USE_CTIME_FOR_INCREMENTALS in the bp.conf file on each UNIX client. For more information, see USE_CTIME_FOR_INCREMENTALS in the NetBackup Administrators Guide, Volume II. Windows: For each Windows client, enable Incrementals: Based on Archive Bit. This property is found under NetBackup Management > Host Properties > Clients > Selected client(s) > Windows Client. For more information, see Incrementals based on archive bit on page 405.

212 Policies More about synthetic backups

Chapter

Storage units, unit groups, and lifecycle policies

The data that is generated from a backup job or another type of job is recorded in storage. A storage destination can be a single tape or disk volume, a named group of storage units, or a storage lifecycle policy. A NetBackup administrator must define storage destinations with the Storage utility before a backup job or another type of job can be run. This chapter describes how to use the NetBackup Storage utility to create and manage storage destinations. This chapter contains the following sections:

Introduction to the Storage utility on page 214 Storage units on page 216 Storage unit settings on page 228 Staging backups to initial storage, then final storage on page 242 Basic disk staging on page 244 Storage Lifecycle Policies on page 253 Storage unit groups on page 267

214 Storage units, unit groups, and lifecycle policies Introduction to the Storage utility

Introduction to the Storage utility

The Storage utility contains subnodes to define three different storage configurations. The primary storage destination is a storage unit, since storage units can be included as part of a storage unit group or a storage lifecycle policy. The following items describe Storage Units, Storage Unit Groups, and Storage Lifecycle Policies:

Storage units A storage unit is a label that NetBackup associates with physical storage. The label may identify a robot, a path to a volume, or a disk pool. (See Storage units on page 216.) Storage unit groups Storage unit groups allow you to identify multiple storage units as a group. How the storage units are selected within the group is determined when the group is created. (See Storage unit groups on page 267.) Storage Lifecycle Policies Storage lifecycle policies allow you to apply the same behavior to all the backup images in the lifecycle. (See Storage Lifecycle Policies on page 253.)

Storage units, unit groups, and lifecycle policies Introduction to the Storage utility

215

Using the Storage utility

Expand Storage, then Storage Units, Storage Unit Groups, or Storage Lifecycle Policies to display the storage destinations that have been created for the selected server. To display the storage configuration for another NetBackup master server, see To administer a remote master server on page 639. Figure 5-1 Storage Unit node of the Storage utility
Create a new storage unit Copy a storage unit

Current master server

Initiate a data management job when using basic disk staging Create a new storage unit group Right-click an object to display a shortcut menu

Storage Lifecycle Policies appear if the appropriate option is licensed

216 Storage units, unit groups, and lifecycle policies Storage units

Storage units
A storage unit is a label that NetBackup associates with physical storage. The label may identify a robot, a path to a volume, or a disk pool. The creation of any storage unit type consists of the following general steps: 1 2 3 4 Name the storage unit. A configured storage unit indicates to NetBackup the existence of underlying physical storage. Choose the storage unit type: Media Manager, disk, or NDMP. (See Figure 5-2 on page 217.) Select a media server. The selection indicates that the media server(s) have permission to write to the storage unit. Indicate the destination where the data is written.

For Media Manager storage units: Data is written to tape robots, stand-alone tape drives, and optical disk devices. For disk storage: NetBackup permits an unlimited number of disk storage units. Disk storage may be one of the following types:

AdvancedDisk storage units: The destination is a disk pool. BasicDisk storage units: The destination is a path to a volume on a host. NearStore storage units: The destination is a NearStore volume on a storage server. OpenStorage storage units: The destination is a disk pool. PureDisk storage unit: The destination is a disk pool. SharedDisk storage units: The destination is a disk pool. SnapVault storage: The destination is a SnapVault server.

For NDMP storage: The NDMP protocol to is used to perform backups and recoveries. The destination is an NDMP host.

Storage units, unit groups, and lifecycle policies Storage units

217

Figure 5-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 (Virtual Tape Option) BasicDisk Points to a directory

Disk

PureDisk Points to a disk pool (PureDisk Storage Option) SnapVault Points to a SnapVault server (SnapVault option) NearStore Points to a NearStore volume on a storage server (OpenStorage Disk Option) SharedDisk Points to a disk pool (Flexible Disk 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)

Creating a storage unit

The following sections describe different methods to create a storage unit. To create a storage unit with the Device Configuration Wizard 1 2 In the NetBackup Administration Console tree, select the Master Server or Media and Device Management. From the list of wizards in the Details pane, click Configure Storage Devices and follow the wizard instructions. For help while running the wizard, click the Help button in the wizard screen.

To create a storage unit from the Actions menu 1 2 In the NetBackup Administration Console, select NetBackup Management > Storage. Storage unit information appears in the Details pane. Click Actions > New > Storage Unit. The New Storage Unit dialog box appears.

218 Storage units, unit groups, and lifecycle policies Storage units

3 4

Complete the fields on the New Storage Unit dialog box. The options are described in Storage unit settings on page 228. Click OK to add the storage unit to the configuration.

To create a storage unit by copying an existing storage unit 1 2 3 4 In the NetBackup Administration Console, select NetBackup Management > Storage. Storage unit information appears in the Details pane. Select a storage unit in the Details pane. Click Actions > Copy Storage Unit. The Copy Storage Unit dialog box appears. Complete the fields in the Copy Storage Unit dialog box. The options are described in Storage unit settings on page 228.

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 3 In the NetBackup Administration Console, select NetBackup Management > Storage. Storage unit information appears in the Details pane. Double-click the storage unit you want to change from those listed in the Details pane. Complete the fields on the Change Storage Unit dialog box. The options are described in Storage unit settings on page 228.

Deleting storage units

To delete a storage unit from a NetBackup configuration means to delete the label that NetBackup associates with the physical storage. To delete a storage unit does not prevent files from being restored that were written to that storage unit, provided that the storage has not been physically removed and the backup image has not expired. To delete a BasicDisk or Media Manager storage unit 1 Use the Catalog utility to expire any images that exist on the storage unit. This removes the image from the NetBackup catalog. (See Expiring backup images on page 346.)

Do not manually remove images from the BasicDisk or Media Manager storage unit.

Storage units, unit groups, and lifecycle policies Storage units

219

Once the images have been expired, they cannot be restored unless the images are imported. (See Importing NetBackup or Backup Exec images on page 336.) NetBackup automatically deletes any image fragments from a disk storage unit or a disk pool. This generally occurs within seconds of expiring an image. However, to make sure that all of the fragments have been deleted, check the directory on the storage unit to make sure that it is empty.

2 3 4 5 6 7

Select the Storage utility, then Storage Units. In the Details 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.

To delete a storage unit that references a disk pool If a storage unit points to disk pool, the storage unit can be deleted witout impacting the disk pool.

220 Storage units, unit groups, and lifecycle policies Storage units

Media Manager storage unit considerations

To create a storage unit of a tape robot, a stand-alone tape drive, or an optical disk device, select Media Manager as the Storage unit type. Media Manager storage unit settings are listed alphabetically in Storage unit settings on page 228. Figure 5-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 is displayed 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.

Storage units, unit groups, and lifecycle policies Storage units

221

Note: NetBackup Media Manager can manage media for other applications, such as Storage Migrator. (A tape that is assigned to Storage Migrator uses a different format and would not be usable for NetBackup backup data.)

Notes on adding a Media Manager storage unit

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

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 on page 231.) 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 identical densities must be in the same storage unit. If a server contains 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) daemon. 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.

222 Storage units, unit groups, and lifecycle policies Storage units

Disk storage unit considerations

NetBackup permits the creation of an unlimited number of disk storage units. See Figure 5-2 on page 217 for a list of available types. Settings are listed alphabetically in Storage unit settings on page 228. Not all settings are available on each disk storage unit type. Note: Symantec recommends that quotas are not imposed 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.)

Disk storage model

NetBackup 6.5 provides a new model for disk storage. This model uses new logical entities, uses existing entities to provide new capabilities, and uses new terminology. All of the disk types except BasicDisk use the new model for disk storage. Those disk types are collectively known as the Enterprise Disk Options. 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 Enterprise Disk Option, the storage server is either: a host that is part of a storage appliance or filer or it is 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.

The following sections describe the disk storage unit types.

Storage units, unit groups, and lifecycle policies Storage units

223

BasicDisk
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. 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 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 server functions as both a data mover and a storage server.

NearStore
A NearStore disk type storage unit is used to store images on Network Attached Storage (NAS) from Network Appliance. NearStore appears as a selection only when the OpenStorage Disk Option is licensed. For NearStore, the NetBackup media servers function as the data movers. The NearStore host is the storage server. Note: NearStore storage units cannot be used as part of a storage unit group or used in a Storage Lifecycle Policy.

OpenStorage
An OpenStorage disk type storage unit is used for disk storage on an intelligent disk appliance. 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 disk appliance is integrated into NetBackup through an API. The storage vendor partners with Symantec to integrate the appliance into NetBackup. For OpenStorage, the NetBackup media servers function as the data movers. The disk appliance is the storage server

224 Storage units, unit groups, and lifecycle policies Storage units

PureDisk
A PureDisk disk type storage unit is used to store images on PureDisk storage devices. The storage unit can be shared by multiple NetBackup media servers. PureDisk appears as a selection only when the PureDisk Storage Option is licensed. For PureDisk, the NetBackup media servers function as the data movers. The PureDisk Linux servers function as the storage servers. Note: PureDisk storage units cannot be used as part of a storage unit group.

SharedDisk
A SharedDisk disk type storage unit is used to store images on a disk array that multiple NetBackup media servers share. The SharedDisk selection is available only when the Flexible Disk Option is licensed. For SharedDisk, the NetBackup media servers function as both the data movers and the storage servers.

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.

Disk storage units in storage lifecycle policies

Another new feature in this release is the option to create storage lifecycle policies. Storage lifecycle policies are discussed on page 253, but mentioned here to show how storage units can interact with a lifecycle. The following figure is one example of how policies can interact with volumes in a disk pool, referenced by a storage unit. Two policies have been created:

Policy_gold has a gold classification. It is configured to use Lifecycle_Gold, which has a gold data classification. Policy_silver has a silver classification. It is configured to use Any Available storage unit. That means it can use any available storage unit or any lifecycle that has a silver classification.

Two storage units are available:

Storage units, unit groups, and lifecycle policies Storage units

225

DSU_1 is a destination in Lifecycle_Gold and references DiskPool_A. DSU_2 is not in a lifecycle. It references DiskPool_A.

DiskPool_A contains three disk volumes. Both gold and silver images can be written to any disk volume in the pool. Figure 5-4
Policy_Gold The data classification for this policy is gold. The policy is configured to write to Lifecycle_Gold. Lifecycle_Gold Lifecycle_Gold contains DSU_1 as a backup destination. DSU_1 DSU_1 references DiskPool_A. DSU_2 Policy_Silver writes to DSU_2. DSU_2 references DiskPool_A.

Lifecycles and disk storage units referencing disk pools

Policy_Silver The data classification for this policy is silver. The policy is configured to write to Any available storage unit.

DiskPool_A

Disk volume Gold image

Disk volume Gold image Silver image

Disk volume Gold image Gold image Silver image

Both policies may write to any volume in the disk pool. The volumes may contain images with different data classifications.

Maintaining available space on disk storage units

Disk storage units can be managed so that they do not become entirely full and cause backups to fail. The following list describes how space can be created for more images on a disk storage unit:

Add new disk space. Set the High water mark to a value that best works with the size of backup images in the environment.

To maintain space on basic disk staging storage units:

226 Storage units, unit groups, and lifecycle policies Storage units

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. Upon NetBackup installation or upgrade, the nb_updatedssu script runs. The script deletes .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 may not be deleted upon installation or upgrade. In that case, run the script again: /usr/openv/netbackup/bin/goodies/nb_updatedssu To determine the potential free space on a disk staging storage unit, see Finding the potential free space on a BasicDisk disk staging storage unit on page 246. The NetBackup General Server host property Check the capacity of disk storage units 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 Check the capacity of disk storage units on page 431.)

Storage units, unit groups, and lifecycle policies Storage units

227

NDMP storage unit considerations

The Virtual Tape Option must be installed on the NDMP hosts to use the hosts as storage units. Media Manager controls NDMP storage units but the units attach to NDMP hosts. NDMP storage unit settings are listed alphabetically in Storage unit settings on page 228. Figure 5-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.

228 Storage units, unit groups, and lifecycle policies Storage unit settings

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

Absolute pathname to directory or Absolute pathname to volume is available for storage units that are not based on disk pools. For example, BasicDisk storage units. The setting specifies the absolute path to a file system or a volume available for disk backups. Enter the path directly in the field, then click Add. Use any location on the disk, providing that sufficient space is available. To display properties about the directory or volume, click the Properties button. (See Properties button on page 236.) Do not configure multiple BasicDisk storage units to use the same volume or file system. Not only do the storage units compete for space, but different Low water marks can cause unexpected behaviors. If the BasicDisk storage unit is used as a disk staging storage unit, Symantec recommends dedicating a disk partition or file system to it. This allows the disk staging space management logic to operate successfully. Or, consider defining AdvancedDisk storage units, which use disk pools composed of disk volumes that are dedicated file systems for disk backup. Use platform-specific file path separators (/ and \) and colon (:) within a drive specification. For additional Windows separators, see NetBackup naming conventions on page 631.

Directory can exist on the root file system or system disk

Enable this BasicDisk storage unit setting to allow the directory that is created in the Absolute pathname to directory field to exist on:

the root file system (UNIX) or a system drive (Windows).

When this setting is enabled, the directory is created automatically. Caution: With this setting enabled, the root file system may fill up. A job fails under the following conditions:

If the checkbox is clear, and if the directory already exists on the root file system.

Storage units, unit groups, and lifecycle policies Storage unit settings

229

If the checkbox is clear, and the requested directory is to be created on the root file system.

Density
The Storage device selection determines the media Density. This setting appears for Media Manager and NDMP storage units only.

Disk pool
A Disk pool is selected for any disk storage unit with an Enterprise Disk Option licensed. Select the disk pool that contains the storage for this storage unit. For AdvancedDisk and SharedDisk, all NetBackup disk pools appear in the Disk pool list. For OpenStorage, only the disk pools for that OpenStorage vendors appliance appear in the list. For PureDisk, only the disk pools for the PureDisk Storage Pool Authority (SPA) appear in the list. SharedDisk only: To change the disk pool properties, click Properties. For information about how to create a disk pool, see the NetBackup Shared Storage Guide.

Disk type
A Disk type is selected for a disk storage unit. A disk storage unit may be one of the following types:

AdvancedDisk (NetBackup Flexible Disk Option needed) BasicDisk NearStore (OpenStorage Disk Option needed) OpenStorage (vendor name) (NetBackup OpenStorage Disk Option needed) PureDisk (PureDisk Storage Option needed) SharedDisk (NetBackup Flexible Disk Option needed) SnapVault (NetBackup Snapshot Client option needed). For information on SnapVault storage units, see the NetBackup Snapshot Client Administrators Guide.

Enable block sharing

The Enable block sharing setting is available to some disk storage types. The Enable block sharing setting allows the data blocks that have not changed from one backup to the next to be shared. To share data blocks can significantly save disk space in the storage unit.

230 Storage units, unit groups, and lifecycle policies Storage unit settings

Enable multiplexing
The Enable multiplexing setting allows multiple backups to multiplex onto a single drive in a storage unit.

High water mark

The High water mark setting is a threshold that, when reached, signals to NetBackup that the disk storage unit should be considered full. Default: 98%. As the disk storage capacity grows closer to the High water mark, NetBackup reduces the number of jobs that can write to the storage unit. NetBackup does not assign new jobs to a storage unit that is considered full. Once the capacity of the storage unit is less than the High water mark, NetBackup assigns jobs to the storage unit. As the capacity of the unit reaches the High water mark, NetBackup reduces the number of jobs that are allowed to write to the unit. Try to prevent the situation where multiple jobs write to a storage unit at one time and fill it to capacity. Once the storage unit is full, none of the jobs can complete and all the jobs fail due to a disk full condition. To reduce the number of jobs that are allowed to write to the storage unit, decrease the Maximum concurrent jobs setting. For more information, see Maximum concurrent jobs on page 231. The high water mark does not apply to storage units that are used for basic disk staging. For more information about this type of staging, see Basic disk staging on page 244.

Low water mark

When a disk storage unit becomes full, expired images are deleted to free space until the Low water mark is met. (Default: 80%.) On storage units used for disk staging, NetBackup may copy expired images to a final destination storage unit to create space. The Low water mark setting cannot be greater than the High water mark setting. Note: Basic disk staging storage units may already be configured on a media server of a previous release. Upon upgrade, the disk storage units are set with the Low water mark at 100%. To make the best use of upgraded storage units, adjust the level. For disk storage units that reference disk pools, the low water mark applies to the disk pool. For more information, see Disk pool properties on page 732 and the NetBackup Shared Storage Guide.

Storage units, unit groups, and lifecycle policies Storage unit settings

231

Maximum concurrent write drives

The Maximum concurrent write drives setting specifies the number of tape drives that NetBackup can use at one time for jobs to this storage unit. The number of tape drives available is limited to the maximum number of tape drives in the storage device. If a job contains multiple copies, each copy applies toward the Maximum concurrent write drives count. Select one number for a:

storage unit that contains only stand-alone tape drives. Specify a number that is less than or equal to the number of tape drives that are in the storage unit. robot. Specify a number that is less than or equal to the number of tape drives that attach to the NetBackup media server for the storage unit.

Assume you have two stand-alone drives of the same density and specify 1. Both tape drives are available to NetBackup but only one drive can be used for backups. The other tape drive is available for restores and other non-backup operations. (For example, to import, to verify, and to duplicate backups.) Caution: To specify a Maximum concurrent write drives setting of 0 disables the storage unit.

Maximum concurrent jobs

The Maximum concurrent jobs setting specifies the maximum number of jobs that NetBackup can send to a disk storage unit at one time. (Default: 1 job. The job count can range from 0 to 256.) This setting corresponds to the Maximum concurrent write drives setting for a Media Manager storage unit. If three backup jobs are ready to be sent to the storage unit and Maximum concurrent jobs is set to two, the first two jobs start and the third job waits. If a job contains multiple copies, each copy applies toward the Maximum concurrent jobs count. Caution: To specify a Maximum concurrent jobs setting of 0 disables the storage unit.

232 Storage units, unit groups, and lifecycle policies Storage unit settings

Using the Maximum concurrent jobs setting to control the storage unit and media server load
Maximum concurrent jobs can be used to balance the load between disk storage units. A higher value (more concurrent jobs) means that the disk may be busier than if the value was set for fewer jobs. The media server load balancing logic considers all storage units and all activity. A storage unit may indicate three media servers. If Maximum concurrent jobs is set to three and two of the media servers are busy or down, the third media server is assigned all three jobs. The Maximum concurrent jobs setting depends on the available disk space and the servers ability to run multiple backup processes. Where disk pools are used, the setting also depends on the number of media servers in the storage unit. If multiple storage units reference the same disk pool, the actual number of concurrent jobs accessing the pool is the sum of the Maximum concurrent jobs settings on all of the disk storage units. The setting applies to the storage unit and not to the disk pool. Therefore, the job load is automatically spread across the media servers indicated by the storage unit configuration. Note: Increase the Maximum concurrent jobs setting if the storage unit is used for online, hot catalog backups as well as non-catalog backups. Increase the setting to ensure that the catalog backup can proceed while regular backup activity occurs. Where disk pools are used, increase the setting if more than one server is in the storage unit.

Impact when two disk storage units reference one disk pool
The following example shows how the Maximum concurrent jobs settings are combined when two disk storage units share one disk pool. For example, in Figure 5-6: DSU_1 is configured:

to use MediaServer_A. to have a Maximum concurrent jobs setting of two.

to reference SharedDisk_pool. DSU_2 is configured:

to use MediaServer_B. to have a Maximum concurrent jobs setting of three. to reference SharedDisk_pool.

Both storage unit reference the same SharedDisk disk pool. Combined, the storage units have a Maximum concurrent jobs setting of five. However, only two jobs can run concurrently on MediaServer_A; three on MediaServer_B.

Storage units, unit groups, and lifecycle policies Storage unit settings

233

Figure 5-6

Impact when disk storage units use one disk pool but different media servers
Maximum concurrent jobs setting: 2 MediaServer_A selected to move data to the pool DSU_2 Maximum concurrent jobs setting: 3 MediaServer_B selected to move data to the pool

DSU_1

MediaServer_A

MediaServer_B

The maximum concurrent jobs that can use the disk pool is 5. SharedDisk_pool

If the storage units were configured to use both media servers, the media servers could run five concurrent jobs: two from DSU_1 and three from DSU_2.

Maximum streams per drive

The Maximum streams per drive setting determines the maximum number of concurrent, multiple client backups that NetBackup can multiplex onto a single drive. The range is from 2 to 32.

Media server
The following setting applies only to NetBackup Enterprise Server. The Media server setting specifies one of the following:

The NetBackup media server where the drives in the storage unit attach. The NetBackup media server that controls the disk storage unit. The NetBackup media servers that can access the servers responsible for data movement to and from the disk pool.

To make this storage unit available to any media server (default), select Any Available. NetBackup selects the media server dynamically at the time the policy is run.

Concerning BasicDisk storage: To configure a disk storage unit, select a single media server. Concerning AdvancedDisk storage units The Media server setting specifies the NetBackup media server that can move data to and from the disk pool.

234 Storage units, unit groups, and lifecycle policies Storage unit settings

Only the media server that is configured as the storage server appears in the media servers list. The disk storage must be directly attached to the media server that is configured as the storage server. NetBackup selects a media server when the policy runs.

Concerning NDMP storage: To configure an NDMP storage unit, the Media server setting specifies the name of the media server that is to back up the NDMP host. Only those media servers that can talk to the specified NDMP storage device are displayed in the drop-down menu. An NDMP host can be authenticated on multiple media servers. Select Any Available to have NetBackup select the media server and storage unit at the time the policy is run. Concerning OpenStorage storage units The Media server setting specifies the NetBackup media servers that can move data to the storage server. To allow any media server in the media server list to access the storage (default), select Use Any Available Media Server. To restrict the media servers that can access the storage, select Only Use The Following Media Servers. Then select the media servers that are allowed to access the storage. The following is required on each media server that accesses the storage:

The vendors software plug-in is installed.

Login credentials to the storage server are configured. Only the media servers on which storage server credentials are configured appear in the media servers list. If a server does not appear, verify that the software plug-in is installed and that login credentials are configured for that media server. Note: Run the tpconfig command line utility directly on the media server to configure and verify credentials. NetBackup selects a media server when the policy runs. Media servers are configured as data movers when the storage server login credentials are entered in NetBackup.

Concerning SharedDisk storage units The Media server setting specifies the NetBackup media servers that can move data to the storage server. To allow any media server in the list to access the storage (default), select Use Any Available Media Server.

Storage units, unit groups, and lifecycle policies Storage unit settings

235

To restrict the media servers that can access the storage, select Only Use The Following Media Servers. Then select the media servers that are allowed to access the storage. The following is required on each media server that accesses the storage:

The SharedDisk software plug-in (installed automatically with NetBackup).

Login credentials to the disk array are configured on the media server. If the array contains multiple, separately named processing units (storage processors), you must enter the credentials for each unit. NetBackup selects a media server when the policy runs.

Concerning PureDisk storage units To allow any media server in the list to access the storage (default), select Use Any Available Media Server. To restrict the media servers that can access the storage, select Only Use The Following Media Servers. Then select the media servers that are allowed to access the storage. The following is required on each media server that accesses the storage:

The PureDisk software plug-in is installed.

Login credentials to the PureDisk server are configured on the media server. NetBackup selects a media server when the policy runs. See the Veritas NetBackup PureDisk Remote Office Edition Administrators Guide for the media server requirements.

NDMP host
The NDMP host setting specifies the NDMP tape server that is used to write data to tape. Select the host name from the drop-down menu.

On demand only
The On demand only setting specifies whether the storage unit is available exclusively on demand. That is, only when a policy or schedule is explicitly configured to use this storage unit. Clear the On demand only check box to make the storage unit available to any policy or schedule. For SnapVault and NearStore storage units, On demand only is selected by default and cannot be changed.

236 Storage units, unit groups, and lifecycle policies Storage unit settings

Caution: If On demand only is selected for all storage units, be sure to designate a specific storage unit for each policy or schedule. Otherwise, NetBackup is unable to find a storage unit to use.

Only use the following media servers

To restrict the media servers that NetBackup can use to access the storage, select Only Use The Following Media Servers. Then select the media servers that are allowed to access the storage. For AdvancedDisk storage:

The required software plug-in is installed automatically with NetBackup. Only the media server that is configured as the storage server appears in the media servers list. A software plug-in must be installed on each media server. The software plug-in is provided by the storage vendor. Login credentials to the storage server must be configured on the media server. Only the media servers that are configured as data movers for the OpenStorage implementation appear in the media server list. (For OpenStorage, NetBackup media servers function as data movers.) If a media server does not appear in the list, verify that the software plug-in is installed and that logon credentials are created. The required software plug-in is installed automatically with NetBackup. Login credentials to the disk array must be configured on the media server. Only the media servers on which disk array login credentials are configured appear in the media servers list. If a server does not appear, verify that the software plug-in is installed and that login credentials are configured for that media server. See the Veritas NetBackup PureDisk Remote Office Edition Administrators Guide for the media server requirements.

For OpenStorage storage:

For SharedDisk storage:

Concerning PureDisk storage units

Properties button
Click Properties to display information about the volume or the disk pool:

Storage units, unit groups, and lifecycle policies Storage unit settings

237

Available storage or Available The Available storage value reflects the space that remains for storage on a disk storage unit. The following equation determines the Available (or free) space: Free space on a volume = Capacity of volume - Used capacity The df command may report a value for the available space that is slightly different from the actual free space value displayed as a result of the nbdevquery command: nbdevquery -listdv -stype server_type -dp disk_pool The available space that the df command reports does not include the space that the operating system reserves. Since NetBackup runs as root, the nbdevquery command includes the reserved space in the available space equation. Capacity The Capacity value reflects the total amount of space that the disk storage unit or pool contains, both used and unused. Disk pool comments Comment that are associated with the disk pool. High water mark The high water mark for the disk pool applies to both the individual disk volumes in the pool and the disk pool:

Individual volumes. When a disk volume reaches the high water mark, NetBackup writes the data to another disk volume in the pool. Disk pool. When all volumes are at the high water mark, the disk pool is full. When a disk pool approaches the high water mark, NetBackup reduces the number of jobs that are allowed to write to the pool. NetBackup does not assign new jobs to a storage unit in which the disk poll is full. (Default: 99%.)

Low water mark The low water mark for the disk pool. When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit. The low water mark setting cannot be greater than the high water mark setting. Name The name of the disk pool. Number of volumes The number of disk volumes in the disk pool. % full The percentage of storage that is currently in use on the volume.

238 Storage units, unit groups, and lifecycle policies Storage unit settings

The df command may report a percentage used (Use%) value that is different from the % full value. (See the preceding Available Storage topic for a description of why the values appear differently.)

Raw size The raw, unformatted size of the storage in the disk pool. Usable size The amount of usable storage in the disk pools.

Reduce fragment size

The Reduce fragment size setting specifies the largest fragment size that NetBackup can create to store backups.

For Media Manager storage units: The default maximum fragment size for a Media Manager storage unit is 1000 terabytes. To specify a maximum fragment size other than the default, place a check in the Reduce fragment size check box. Then enter a value from 50 megabytes to 1,048,575 megabytes. Fragmenting multiplexed tape backups can expedite restores. Fragments allow NetBackup to skip to the specific fragment before searching for a file. Generally, NetBackup starts at the beginning of the multiplexed backup and reads tar headers until it finds the file. For disk storage units: The default maximum fragment size for a disk storage unit is 524,287 megabytes. To specify a maximum fragment size other than the default, enter a value from 20 megabytes to 524,287 megabytes. Backups to disk are usually fragmented to ensure that the backup does not exceed the maximum size that the file system allows. The Reduce fragment size setting is intended primarily for storing large backup images on a disk type storage unit. Backups may be fragmented on disk to increase performance when the images that Storage Migrator has migrated are restored. For example, a restore is faster if a 500-megabyte backup is stored in 100-megabyte fragments. Storage Migrator needs to retrieve only the specific fragment with the file rather than the entire 500 megabytes.

Note: OpenStorage vendors may have special requirements for the maximum fragment size. Consult the vendor's documentation for guidance. If an error occurs in a backup, the entire backup is discarded. The backup restarts from the beginning, not from the fragment where the error occurred. (An exception is for backups where checkpoint restart is enabled. In that case,

Storage units, unit groups, and lifecycle policies Storage unit settings

239

fragments before and including the last checkpoint are retained; the fragments after the last checkpoint are discarded.) Note: Basic disk staging units with different maximum fragment sizes may already be configured on a media server from a previous release. Upon upgrade, the disk storage units are not automatically increased to the new default of 524,287 megabytes. To make the best use of upgraded storage units, increase the fragment size on the upgraded storage units.

Robot number
The Storage device selection determines the Robot number. It is the same robot number used in the Media Manager configuration. For more information on robot numbers, see Robot number on page 601.

Robot type
The Robot type and indicates the type of robot (if any) that the storage unit contains. The Robot type is determined by the Storage device setting. For the specific vendor types and models that correspond to each robot type, see the Supported Peripherals section of the NetBackup Release Notes.

Staging relocation schedule (for basic disk staging only)

Click the Staging schedule button to configure the relocation schedule for this storage unit. A schedule is what makes the disk storage unit into a basic disk staging storage unit. During the relocation schedule, the backup image is duplicated from the temporary staging area to the final destination storage unit. For more information about basic disk staging, see Temporary staging area on page 240 and Basic disk staging on page 244.

Storage device
The Storage device list contains all possible storage devices available. Storage units can be created for the listed devices only.

Storage unit name

Type a unique Storage unit name for the new storage unit. The name could describe the type of storage. The Storage unit name is the name used to specify a storage unit for policies and schedules. For more information, see NetBackup naming conventions on page 631.

240 Storage units, unit groups, and lifecycle policies Storage unit settings

The storage unit name cannot be changed after creation. The Storage unit name is inaccessible in a Change Storage Unit operation.

Storage unit type

The Storage unit type setting specifies the type of storage that this storage unit uses:

Disk: see Disk storage unit considerations on page 222. Media Manager: see Media Manager storage unit considerations on page 220. NDMP: see NDMP storage unit considerations on page 227.

Temporary staging area

If the storage unit is to be used as a temporary staging area, click the temporary staging checkbox. Then, configure the staging schedule. For more information, see Staging relocation schedule (for basic disk staging only) on page 239. The Staging column in the Storage units details pane indicates whether or not the unit is used as a temporary staging area for basic disk staging. For more information about basic disk staging, see Temporary staging area on page 240 and Basic disk staging on page 244.

Transfer throttle
The Transfer throttle setting appears for SnapVault storage units only. This setting makes it possible to limit the amount of network bandwidth that is used for the SnapVault transfer. (In case bandwidth needs to be reserved for other applications.) Zero (default) means no network bandwidth limit for the SnapVault transfer: SnapVault uses all available bandwidth. (Range: 0 to 9999999.) A value greater than 0 indicates a transfer speed for SnapVault in kilobytes per second. For example, a value of 1 sets a transfer speed limit for SnapVault of 1 kilobyte per second, which is a very slow transfer rate.

Use any available media server

To allow any media server in the media server list to access the storage (default), select Use Any Available Media Server. For AdvancedDisk storage:

The required software plug-in is installed automatically with NetBackup.

Storage units, unit groups, and lifecycle policies Storage unit settings

241

Only the media servers that are configured as storage servers appear in the media servers list. A software plug-in must be installed on each media server. The software plug-in is provided by the storage vendor. Login credentials to the storage server must be configured on the media server. Only the media servers on which storage server login credentials are configured appear in the media servers list. If a server does not appear, verify that the software plug-in is installed and that login credentials are configured for that media server. The required software plug-in is installed automatically with NetBackup. Login credentials to the disk array must be configured on the media server. Only the media servers that are configured as data movers for the OpenStorage implementation appear in the media server list. (For OpenStorage, NetBackup media servers function as data movers.) If a media server does not appear in the list, verify that the software plug-in is installed and that logon credentials are created. See the Veritas NetBackup PureDisk Remote Office Edition Administrators Guide for the media server requirements.

For OpenStorage storage:

For SharedDisk storage:

For PureDisk storage:

242 Storage units, unit groups, and lifecycle policies Staging backups to initial storage, then final storage

Staging backups to initial storage, then final storage

Staging backups is the process in which a backup is written to a storage unit, then duplicated to a second storage unit. Eligible backups are deleted on the initial storage unit when space is needed for more backups. This two-stage process allows a NetBackup environment to leverage the advantages of disk-based backups for recovery in the short term. Staging also meets the following objectives:

Staging allows for faster restores from disk. Staging allows the backups to run when tape drives are scarce. Staging allows data to be streamed to tape without image multiplexing.

Two staging methods

NetBackup offers two methods to stage backups:

Basic disk staging Basic disk staging consists of two stages. First, data is stored on the initial storage unit (disk staging storage unit). Then, per a configurable relocation schedule, data is copied to the final location. Having the images on the final destination storage unit allows the space to be freed on the disk staging storage unit when it is needed. For more information, see Basic disk staging on page 244. The following storage unit types are available for basic disk staging: BasicDisk, NearStore, and tape. Staging using Storage Lifecycle Policies Staged backups that are configured within the Storage Lifecycle Policies utility also consist of two stages: Data on the staging storage unit is copied to a final destination, however, the data is not copied per a specific schedule. Instead, the administrator can configure the data to remain on the storage unit until either a fixed rention period is met, or until the disk needs additional space, or until the data is duplicated to the final location. No BasicDisk, SnapVault, or disk staging storage units can be used as destinations in a lifecycle. For more information, see Storage Lifecycle Policies on page 253.

The staging method that is used is determined in the policy Attributes tab. The Policy storage selection determines whether the backup goes to a storage unit or a lifecycle.

Storage units, unit groups, and lifecycle policies Staging backups to initial storage, then final storage

243

Note: Symantec recommends that a disk partition or file system be dedicated to any disk storage unit that is used for staging. Dedicated space allows the disk staging space management logic to operate successfully.

244 Storage units, unit groups, and lifecycle policies Basic disk staging

Basic disk staging

The basic disk staging method is conducted in two stages:

Stage I: Clients are backed up by a policy. The Policy storage selection in the policy indicates a storage unit that has a relocation schedule configured. The schedule is configured in the New or Change Storage unit dialog by clicking Staging Schedule. Stage II: Images are copied from the Stage I disk staging storage unit to the Stage II storage unit. The relocation schedule on the disk staging storage unit determines when the images are copied to the final destination. Having the images on the final destination storage unit allows the space to be freed on the disk staging storage unit when it is needed.

The image continues to exist on both the disk staging storage unit and the final destination storage units until the image expires or until space is needed on the disk staging storage unit. Figure 5-7
Client

Stage I and II of basic disk staging

Disk staging storage unit Final destination storage unit

A policy backs up client data to a disk staging storage unit Stage I

The relocation schedule on the disk staging storage unit copies data to the final destination storage unit Stage II

When the relocation schedule runs, NetBackup creates a data management job. The job looks for any data that can be copied from the disk staging storage unit to the final destination. The Job Details in the Activity Monitor identify the job as one associated with basic disk staging. The Job Details list Disk Staging in the jobs Data Movement field. When NetBackup detects a disk staging storage unit that is full, it pauses the backup. Then, NetBackup finds the oldest images on the storage unit that have been successfully copied onto the final destination. NetBackup expires the images on the disk staging storage unit to create space.

Storage units, unit groups, and lifecycle policies Basic disk staging

245

Disk staging storage unit size and capacity considerations

To take advantage of basic disk staging requires that the NetBackup administrator understand the life expectancy of the image on the Stage I storage unit. The size and use of the file system of the Stage I storage unit directly impacts the life expectancy of the image before it is copied to the Stage II storage unit. Symantec recommends a dedicated file system for each disk staging storage unit. Consider the following example: A NetBackup administrator wants incremental backups to be available on disk for one week. Incremental backups are done Monday through Saturday, with full backups done on Sunday. The full backups are sent directly to tape, and do not use basic disk staging. Each nights total incremental backups are sent to a disk staging storage unit and average from 300MB to 500MB. Occasionally a backup is 700MB. Each following day the relocation schedule runs on the disk staging storage unit and copies the previous nights incremental backups to the final destination, a Media Manager (tape) storage unit.

Minimum disk size for a basic disk staging storage unit

The minimum disk size is the smallest size that is required for the successful operation of the disk staging logic. The minimum size must be greater than or equal to the largest combined size of the backups that are placed on the storage unit between runs of the disk staging schedule. (In our example, the disk images remain on the disk for one week.) In this example, the relocation schedule runs nightly, and the largest nightly backup is 700MB. Symantec recommends that you double this value to allow for any problems that may occur when the relocation schedule runs. To double the value gives the administrator an extra schedule cycle (one day) to correct any problems. To determine the minimum size for the storage unit in this example, use the following formula: Minimum size = Max data per cycle * (1 cycle + 1 cycle for safety) For example: 1.4GB = 700MB * (1+1)

Average disk size for a basic disk staging storage unit

The average disk size represents a good compromise between the minimum and the maximum sizes. In this example, the average nightly backup is 400MB and the NetBackup administrator wants to keep the images for one week.

246 Storage units, unit groups, and lifecycle policies Basic disk staging

To determine the average size for the storage unit in this example, use the following formula: Average size = Average data per cycle * (number of cycles to keep data + 1 cycle for safety) 2.8GB = 400MB * (6 + 1)

Maximum disk size for a basic disk staging storage unit

The maximum disk size is the recommended size needed to accommodate a certain level of service. In this example, the level of service is that disk images remain on disk for one week. To determine the maximum size for the storage unit in this example, use the following formula: Maximum Size = Max data per cycle * (# of cycles to keep data + 1 cycle for safety) For example: 4.9 GB = 700MB * (6 + 1)

Finding the potential free space on a BasicDisk disk staging storage unit
Potential free space is the amount of space on a disk staging storage unit that NetBackup could free if extra space on the volume was needed. The space is the total size of the images that are eligible for expiration plus the images ready to be deleted on the volume. To find the potential free space on a BasicDisk storage unit, use the bpstulist and the nbdevquery commands. Note that the name of the storage unit and disk pools are case-sensitive. Run bpstulist -label to find the disk pool name. In the case of BasicDisk storage units, the name of the disk pool is the same as the name of the BasicDisk storage unit. In the following example, the name of the storage unit is NameBasic:
bpstulist -label basic NameBasic 0 server1 0 -1 -1 1 0 "C:\" 1 1 524288 *NULL* 0 1 0 98 80 0 NameBasic server1

Run the nbdevquery command to display the status for the disk pool, including the potential free space. Use the following options, where: -stype server_type Specifies the vendor-specific string that identifies the storage server type. For a BasicDisk storage unit, enter BasicDisk. -dp Specifies the disk pool name. For a basic disk type, the disk pool name is the name of the BasicDisk storage unit.

Storage units, unit groups, and lifecycle policies Basic disk staging

247

nbdevquery -listdv -stype BasicDisk -dp NameBasic -D

The value is listed as potential_free_space.

Disk Volume Dump name : id : diskpool : disk_media_id : total_capacity : free_space : potential_free_space: committed_space : precommitted_space : nbu_state : sts_state : flags : num_read_mounts : max_read_mounts : num_write_mounts : max_write_mounts : system_tag :

<Internal_16> <C:\> <NameBasic::server1::BasicDisk> <@aaaaf> 0 0 0 0 0 2 0 0x6 0 0 1 1 <Generic disk volume>

Creating a basic disk staging storage unit

To create a basic disk staging storage unit 1 In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units. Storage unit information appears in the Details pane. Click Actions > New > Storage Unit. The New Storage Unit dialog box appears. Complete the New Storage Unit dialog box:

2 3

Name the storage unit. For more information, see Storage unit name on page 239. Select Disk as the Storage unit type. Select the Disk type of disk storage unit that is to be a disk staging storage unit. Select a media server. For more information, see Media server on page 233. Enter the absolute path to the directory to be used for storage. For more information, see Absolute pathname to directory/volume on page 228.

248 Storage units, unit groups, and lifecycle policies Basic disk staging

Select whether this directory can reside on the root file system or system disk. For more information, see Directory can exist on the root file system or system disk on page 228. Enter the maximum concurrent jobs that are allowed to write to this storage unit at one time. For more information, see Maximum concurrent jobs on page 231. Enter a Low water mark value. For more information, see Low water mark on page 230. The High water mark does not apply to basic disk staging. For more information, see High water mark on page 230. Check the Enable temporary staging area option. Once the option is enabled, the Staging Schedule button becomes enabled. Click the Staging Schedule button. The Disk Staging dialog box appears.

Complete the Disk Staging dialog box. The dialog box is similar to the scheduling dialog box used to configure policies. The differences appear on the Attributes tab:

The schedule name defaults to the storage unit name. Select the priority that the relocation jobs that are started from this schedule have compared to other types of jobs. For more information, see Priority of relocation jobs started from this schedule on page 250. Select whether to create Multiple Copies. With the Multiple copies attribute enabled, NetBackup can create up to four copies of a backup simultaneously. For more information, see Multiple copies on page 131. Note: For disk staging storage units, the Maximum backup copies Global host property must include an additional copy beyond the number of copies that are indicated in the Copies field.

Select a storage unit to contain the images from this storage unit upon relocation. For more information, see Final destination storage unit on page 250. Select a volume pool to contain the images from this storage unit upon relocation. For more information, see Final destination volume pool on page 250. Select a media owner to own the images from this storage unit upon relocation. For more information, see Final destination media owner on page 250.

Storage units, unit groups, and lifecycle policies Basic disk staging

249

Select whether to use an alternate server for the images from this storage unit upon relocation. For more information, see Use alternate read server on page 251.

5 6

Click OK to accept the disk staging schedule. Click OK to add the storage unit.

Disk Staging Schedule dialog

Click the Staging Schedule button to display the Disk Staging dialog box. The dialog is similar to the scheduling dialog box that appears when a policy is configured. The schedule that is created for the disk staging storage unit is not listed under Schedules in the NetBackup Administration Console when Policies is selected. Figure 5-8 Disk Staging Schedule for a basic disk staging storage unit

The differences appear on the Attributes tab, as described in the following sections:

Name
The schedule name for a disk staging schedule automatically defaults to the name of the storage unit.

250 Storage units, unit groups, and lifecycle policies Basic disk staging

Priority of relocation jobs started from this schedule

This attribute specifies the priority that NetBackup assigns to relocation jobs for this policy. Range: 0 (default) to 99999 (highest priority).

Final destination storage unit

The Final destination storage unit is where the images reside after a relocation job copies them. To copy images to tape, NetBackup uses all of the drives available in the Final destination storage unit. However, the Maximum concurrent write drives setting for that storage unit must be set to reflect the number of drives. The setting determines how many duplication jobs can be launched to handle the relocation job. For more information, see Maximum concurrent write drives on page 231. NetBackup continues to free space until the Low water mark is reached. For more information, see Low water mark on page 230.

Final destination volume pool

The Final destination volume pool is the volume pool where the images reside after a relocation job copies them. The Final destination volume pool is selectable:

If the Final destination storage unit is a Media Manager storage unit (tape), or If Any Available is indicated for the Final destination storage unit.

Final destination media owner

The Final destination media owner is the media owner where the images reside after a relocation job copies them. Specify one the following:

Any lets NetBackup choose the media owner. NetBackup chooses a media server or a server group (if one is configured). None 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. 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.

Storage units, unit groups, and lifecycle policies Basic disk staging

251

Use alternate read server

The Alternate Read Server attribute applies to NetBackup Enterprise Server only. An alternate read server is a server allowed to read a backup image originally written by a different media server. The path to the disk or directory must be identical for each media server that is to access the disk. If the backup image is on tape, the media servers must share the same tape library or the operator must find the media. If the backup image is on a robot that is not shared or a stand-alone drive, the media must be moved to the new location. An administrator must move the media, inventory the media in the new robot, and execute bpmedia -oldserver -newserver or assign a failover media server. To avoid sending data over the network during duplication, specify an alternate read server that is:

Connected to the storage device that contains the original backups (the source volumes). Connected to the storage device that contains the final destination storage units.

If the final destination storage unit is not connected to the alternate read server, data is sent over the network.

Basic disk staging limitations

The basic disk staging method does not support the backup images that span disk storage units. To avoid spanning storage units: do not use Checkpoint restart on a backup policy that writes to a storage unit group that contains multiple disk staging storage units. For more information, see Checkpoint restart for backup jobs on page 95.

Initiating a relocation schedule manually

A relocation schedule may be started manually to copy images to the final destination before the schedule is due to run. To initiate a relocation schedule 1 In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units. Storage unit information appears in the Details pane. Select a basic disk staging storage unit in the Details pane.

252 Storage units, unit groups, and lifecycle policies Basic disk staging

Select Actions > Manual Relocation to Final Destination to initiate the schedule.

If the relocation schedule finds data that can be copied, NetBackup creates a job to copy the data to the final destination storage unit. The image then exists both storage units until the disk staging (Stage I) storage unit becomes full and the oldest images are deleted. For more information, see Maintaining available space on disk storage units on page 225.

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

253

Storage Lifecycle Policies

A storage lifecycle policy is a storage plan for a set of backups. A lifecycle policy is configured within the Storage Lifecycle Policies utility Essentially, a lifecycle is a list of destinations where copies of the backup images are stored, along with the prescribed retention period for each copy. After a lifecycle is configured, the lifecycle process works to create copies of the images on each destination. NetBackup retries the copies as necessary, to ensure that all copies are created. A storage lifecycle policy can also be set up to provide staging behavior. Lifecycles offer the opportunity for users to assign a classification to the data at the policy level. A data classification represents a set of backup requirements, which makes it easier to configure backups for data with different requirements. For example, email data and financial data.

Storage lifecycle overview

A storage lifecycle can simplify data management by applying a prescribed behavior to all the backup images that are included in the storage lifecycle. This process allows the NetBackup administrator to leverage the advantages of disk-based backups in the near term. It also preserves the advantages of tape-based backups for long term storage. A storage lifecycle operation consists of three steps: 1 A backup is written to all destinations in the lifecycle. This process can occur if the NetBackup administrator has set up a lifecycle policy that contains at least one backup destination. The policy that writes the data must indicate that the backup data is to go to a lifecycle policy.

This selection determines whether the destination is a backup destination or a duplication destination

NetBackup automatically copies the image to all duplication destinations in the lifecycle. The backup is retained on the backup destination until the retention period is met. Duplication destinations are optional, and can provide another method for disk staging.

254 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

The retention type that is selected for the destinations determines how long the backup resides on the destination. Eventually, NetBackup deletes the backup from the destinations to create more disk space.

To create a storage lifecycle policy

A storage lifecycle can be selected within a backup policy similarly to how a storage unit is selected in a policy. If a storage lifecycle is selected, the images that the policy creates are written to all the destinations that are defined in the storage lifecycle. To create a storage lifecycle policy 1 2 In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Lifecycle Policies. Click Actions > New > Storage Lifecycle Policy. The New Storage Lifecycle Policy dialog box appears.

Complete the New Storage Lifecycle Policy dialog box:

Indicate a Storage lifecycle policy name: Name the storage lifecycle. Indicate a Data classification: Select a data classification. (Optional.) (See Data classification on page 262.) Indicate a Duplication job priority: Select the priority that duplication jobs have in relationship to all other jobs. In duplication jobs, NetBackup duplicates data from a backup

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

255

destination to a duplication destination within a lifecycle. (See Duplication job priority on page 258.)

Indicate the Storage destinations: Click the Add button to add storage destinations to the lifecycle. (See Storage destinations on page 258.)

Click OK to create the storage lifecycle. After they are created, data classifications cannot be deleted.

Adding storage destinations to a lifecycle policy

A lifecycle must contain each of the following items:

At least one backup destination At least one destination of a fixed retention type

Note: A duplication destination does not need to be included in a lifecycle if staging behavior is not the objective. The lifecycle may be used to create multiple copies. To add a storage destination to a lifecycle policy 1 2 Open the New Storage Lifecycle Policy dialog box or the Change Storage Lifecycle Policy dialog box. Click Add. The New Destination dialog box appears.

Every lifecycle must contain at least one destination of a fixed retention type Depends on high and low watermark settings Use only for backup destinations

Complete the New Destination dialog box:

256 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

Select whether images are to be written to the destination as part of the backup operation or as part of the duplication operation. (During the duplication operation, backups are duplicated to secondary storage.) (See Use storage destination for: backup or duplication on page 259.) Indicate the Storage unit or storage unit group where the backups are to be written. No BasicDisk, SnapVault, or disk staging storage units can be used as destinations in a lifecycle. (See Storage unit on page 259.) Indicate the Volume pool where the backups (or copies) are to be written. (See Volume pool on page 259.) Indicate the Media owner if the storage unit is a Media Manager type and server groups are configured. Specify a Media owner to allow only those media servers in the group to write to the media on which backup images for this policy are written. (See Media owner on page 259.) Indicate the retention type for the destination:

Fixed retention type. (See Retention type: Fixed on page 260.) Staged capacity managed. (See Retention type: Staged capacity managed on page 260.) Expire after duplication. (For backup destinations only.) (See Retention type: Expire after duplication on page 262.) If a policy is configured to back up to a lifecycle, the retention that is indicated in the lifecycle is followed. The Retention attribute in the schedule is not followed.

Indicate an Alternate read server. (See Alternate read server on page 262.)

Click OK to create the storage destination.

Writing multiple copies using a lifecycle

NetBackup writes backups to all destinations in the storage destination list. Therefore, if a storage lifecycle policy contains multiple destinations, a multiple copies operation is implied. (Limit: four backup storage destinations.) The backup destinations must meet the criteria for multiple copies: the backups must go to the same media server. Note: The number of destinations that are added to the lifecycle cannot exceed the Maximum Backup Copies setting in the Global host properties. The lifecycle cannot be saved until the destinations is decreased, or until the Maximum Backup Copies is increased.

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

257

Use only one method to create multiple copies

NetBackup permits only one method to create multiple copies. If a storage lifecycle policy contains more than one backup destination, the Multiple copies option is disabled in the schedules configuration within the backup policy. Or, if a policy setup includes multiple copies, the policy cannot select a lifecycle as a storage destination. (See Multiple copies on page 131.)

Ensuring successful copies using lifecycles

The process to create copies as part of a lifecycle is different from the process to create copies as set up in a policys configuration. The policys Configure Multiple Copies dialog box includes the option to Fail all copies. That option means that if one copy fails, the remaining copies can be set to either continue or to fail. However, in a storage lifecycle policy, all copies must be completed. A lifecycle initially tries three times to create a copy. If no copy is created, NetBackup continues to try, but less frequently. The successful completion of copies is important because a lifecycle does not allow a copy to be expired before all copies are completed to each destination in the lifecycle. Expiration is necessary to free up space on the storage unit for new backups. NetBackup changes the retention period of an image to Infinite until all copies are created. After all copies are complete, the retention returns to the level as set in the policy that writes to the storage destination. To complete successful backups in the lifecycle, a backup destination may duplicate a backup onto another backup destination. Consider the following example: A lifecycle contains two backup destinations (BU_1, BU_2) and three duplication destinations. The backup to BU_1 is successful, but the backup to BU_2 is not successful. To fulfill the backup on BU_2, a duplication job is created from BU_1 to BU_2. The duplication job is in addition to the jobs that are run for the three duplication destinations. Note: Duplication jobs can be controlled using the nbstlutil command. For more information, see Using nbstlutil to administrate lifecycle operations on page 265.

Copy order determined by destination order

The order in which the destinations appear in a lifecycle determines the copy number of the backup. For example, in the following figure, a lifecycle is configured to create three copies:

Two copies to two different backup destinations One copy to a duplication destination

258 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

To make sure that copy 1 is written to disk, enter the disk type destination before the tape destination. Figure 5-9 Order of destinations determines copy order

Copy 1 on disk Copy 2 on tape Copy 3 on disk

Storage lifecycle policy name

The Storage lifecycle policy name describes the storage lifecycle. The name can be modified.

Duplication job priority

The Duplication job priority setting is the priority that duplication jobs have in relationship to all other jobs. In duplication jobs, NetBackup duplicates data from a backup destination to a duplication destination within a lifecycle. Range: 0 (default) to 99999 (highest priority). For example, the Duplication job priority for a policy with a gold data classification may be set higher than for a policy with a silver data classification. The priority of the backup job is set in the backup policy on the Attributes tab. (See Job priority on page 98.)

Storage destinations
The storage destination list contains all the destinations (storage units and storage unit groups) that the storage lifecycle can use. The list includes the storage that is used for the original backups as well as storage that is used for duplication at a later time.

Storage lifecycle errors

An error dialog is displayed if any of the following conditions are not met:

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

259

All configured backup destinations for the storage lifecycle must be on the same media server. One of the destinations must be of a fixed retention type. There must be at least one valid backup destination in the destination list.

Use storage destination for: backup or duplication

Select whether images are to be written to the destination as part of the backup operation or as part of the duplication operation. (During the duplication operation, backups are duplicated to secondary storage.) If a storage lifecycle contains multiple backup destinations, a multiple copies operation is implied. (See Writing multiple copies using a lifecycle on page 256.)

Storage unit
Indicate the storage unit where the backups are to be written. The following destinations can be selected:

Any available Media Manager storage units (tape) Disk storage units (no BasicDisk, SnapVault, or disk staging storage units) Storage unit groups (may contain no BasicDisk, SnapVault, or disk staging storage units). A storage lifecycle policy can point to a storage unit group that contains a BasicDisk storage unit. However, NetBackup does not select BasicDisk storage units from a storage group for a lifecycle policy.

Note: The storage destination list cannot contain other storage lifecycles. Storage units or storage unit groups may appear in more than one lifecycle. Storage units or storage unit groups may be used in a storage lifecycle while also being used as stand-alone units.

Volume pool
The Volume pool option is enabled for tape storage units.

Media owner
A Media owner can be selected. A Media owner is a group of NetBackup servers that are used for a common purpose. (See Configuring server groups for media sharing on page 615.)

260 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

Retention type: Fixed

A Fixed retention type means that the backup data is retained for a specific length of time before the backups are expired. When the retention period is reached, NetBackup deletes information about the expired backup. The files in the backup then become unavailable for restore. Note: Every lifecycle must contain at least one destination with a fixed retention period. The destination can be a backup or a duplication destination. The images are not deleted if all copies have not completed. For example, the administrator selects a fixed retention for a tape device to keep images on tape for two days. If the images have not been duplicated to all of the destinations in the lifecycle after two days, the images are not expired. The image remains on the tape device until all copies have been created. (Or, until the administrator uses nbstlutil utility to intervene.)

Retention period
The Retention period specifies exactly how long NetBackup retains the backups before the backups are expired. To set the retention period, select a time period (or level) from the drop-down list.

Retention type: Staged capacity managed

A Staged capacity managed storage destination means that NetBackup automatically manages the space on the (disk) destination. (This option is not available to tape storage units since tape capacity is considered to be infinite.) The High water mark and Low water mark settings on the disk storage unit or disk pool determine how the space is managed. (See High water mark on page 230 and Low water mark on page 230.) If space is needed for new images, expired backup copies are removed from the storage destination when the storage unit reaches the high water mark. NetBackup removes backup images on the storage destination until the low water mark is reached. It searches for images to remove in the following order:

Any Backup images that have passed the Desired cache period setting. Data classifications: Images that belong to a data classification with a lower rank are deleted before those that belong to a data classification with a higher rank. (See Data Classification properties on page 407.)

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

261

Note: If more space is needed, any images that are not past the Desired cache period may be deleted. However, an image is never deleted if it has not been duplicated to all destinations in the lifecycle, even if the image is past its retention period. For more information, see Writing multiple copies using a lifecycle on page 256. To see exactly when the storage destination reaches the low water mark value is difficult. A backup can occur at the same time as the expiration process occurs. After the backup is complete, the low water mark may be slightly greater than its lowest possible value.

Desired cache period

The retention period for a staged capacity managed storage destination is not assured as it is for a fixed retention period. The Desired cache period becomes a target that NetBackup tries to maintain. If the space is not required, the backup data could remain on the storage destination longer than the Desired cache period indicates.

Mixing retention types on the same volume within a disk storage destination
Symantec does not recommend allowing capacity-managed images and fixed-retention images to be written to the same volume in a disk storage unit. The volume may fill with fixed-retention images and not allow the space management logic to operate as expected. Keep the following points in mind when configuring lifecycle destinations or selecting the storage location for a policy:

All lifecycles that write to a volume in a disk storage unit should write images of the same retention type: fixed or capacity-managed. Do not write images both to a volume in a disk storage unit within a lifecycle and to the same volume (by the storage unit) directly from a policy. Mark all disk storage units that are used with lifecycles as On demand only. Check any storage unit groups to make sure that fixed and capacity-managed images cannot be written to the same volume in a disk storage unit.

Capacity managed retention and the storage units that use Single instance store
Staged capacity managed is selectable for any disk storage unit that is allowed in a lifecycle. However, for the disk types that support single-instance store (SIS), Staged capacity managed functions to various degrees. In order for Staged capacity managed to operate, NetBackup must know how much space a

262 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

backup image uses. With SIS enabled on the storage unit, NetBackup cannot know exactly how much space a particular backup image occupies. The following storage unit configurations use SIS:

PureDisk storage units NearStore storage units that have either the Enable file system export option enabled or the Enable block sharing option enabled. Some OpenStorage storage units, depending on the vendor characteristics.

Retention type: Expire after duplication

The Expire after duplication retention applies only to backup destinations, not duplication destinations. When data is staged to a tape device, two retention options are available:

Staged capacity managed Expire after duplication

Alternate read server

An Alternate read server specifies the name of the server that is allowed to read a backup image originally written by a different media server. An Alternate read server can be specified for both backup and duplication destinations. However, to use an Alternate Read Server as part of a duplication operation, the name of the alternate server must be specified in the backup destination configuration.

Data classification
The Data classification allows the NetBackup administrator to classify data based on relative importance. A classification represents a set of backup requirements. When data must meet different backup requirements, consider assigning different classifications. For example, email backup data may be assigned to the silver data classification and financial backup data backup may be assigned to the platinum classification. The financial data is assigned to the higher classification of platinum because backups of the financial data are consider more important. The Data classification defines the level of data that the storage lifecycle is allowed to process. The Data classification drop-down menu contains all of the defined classifications. To select a classification is optional. One data classification can be assigned to each storage lifecycle policy and applies to all destinations in the lifecycle. A storage lifecycle is not required to have a data classification.

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

263

If a data classification is selected, the storage lifecycle stores only those images from the policies that are set up for that classification. If no classification is indicated, the storage lifecycle accepts images of any classification or no classification.

How backup data is associated with a data classification

A data classification is assigned in the backup policy to associate backup data with a data classification. Data from the policy can be stored only in a storage lifecycle policy with the same data classification assigned to it. Figure 5-10 Data classification assignment in the policy

If a classification is indicated, the Policy storage selection must contain a lifecycle with that assigned classification

After data is backed up to a storage lifecycle policy with an assigned classification, the data is managed according to the storage lifecycle configuration. The storage lifecycle defines what happens to the data from the initial backup until the last copy of the image has expired. If a classification is selected, all the images that the policy creates are tagged with that classification ID.

Creating or changing a data classification

NetBackup contains four default data classifications. The name, the description, and the rank of each can be changed in the Data Classification host properties. (In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Data Classifications.) New data classifications can also be created. However, data classifications cannot be deleted. (See Data Classification properties on page 407.)

264 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

Optional duplication job configuration

An optional configuration file can be created to assist the lifecycle to run duplication jobs more efficiently. To prevent the lifecycle from running numerous small duplication jobs in frequent succession, NetBackup accumulates lists of similar images into a batch. Then, each batch of images is copied as a set in one duplication job, instead of one image at a time. The NetBackup administrator can change how large the batch files can become, or how frequently batch jobs are requested. To do so, the administrator creates and changes the default parameters in the LIFECYCLE_PARAMETERS file. One or all of the parameters can appear in any order in the LIFECYCLE_PARAMETERS file. If the file is not present in the following directory, NetBackup uses the default parameters: /usr/openv/netbackup/db/config

MIN_KB_SIZE_PER_DUPLICATION_JOB
The MIN_KB_SIZE_PER_DUPLICATION_JOB parameter default is 8 gigabytes. This parameter indicates the total size that the image batch can reach before a duplication job is run for the batch. The lifecycle looks for completed images to be added to a batch every five minutes. The lifecycle does not request a duplication job until either:

the total size of the images in a batch reaches the minimum size as indicated by MIN_KB_SIZE_PER_DUPLICATION_JOB, or the MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB time has passed. This parameter determines the maximum time between batch requests.

MAX_KB_SIZE_PER_DUPLICATION_JOB
The MAX_KB_SIZE_PER_DUPLICATION_JOB parameter default is 25 gigabytes. This parameter determines how large the image batch can grow. When the size reaches the size as indicated by this parameter, no more images are added to the batch.

MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB
The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB parameter default is 30 minutes. If the minimum batch size is not reached by the time indicated, the lifecycle requests a duplication job, regardless of the size.

Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

265

LIFECYCLE_PARAMETERS file example

The following is an example of the contents and syntax for a LIFECYCLE_PARAMETERS file, using the default values:
MIN_KB_SIZE_PER_DUPLICATION_JOB 8192 MAX_KB_SIZE_PER_DUPLICATION_JOB 25600 MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB 30

Using nbstlutil to administrate lifecycle operations

The NetBackup storage lifecycle utility command (nbstlutil) gives administrators the ability to intervene between pending storage lifecycle operations. Specifically, the nbstlutil command can be used to cancel, inactivate, or activate pending duplication jobs. A duplication job copies data from a backup destination to a duplication destination. nbstlutil cannot affect the jobs that are currently running. Use the Activity Monitor to intervene in the jobs that are running. The command is found in the following location: /usr/openv/netbackup/bin/admincmd/nbstlutil Use nbstlutil to perform the following administrative actions:

List the contents of the EMM database. The tables about the lifecycle-processed images can be printed. Support may request this information to troubleshoot a lifecycle problem. Cancel pending duplication operations on the selected image copies. When a duplication job is canceled, NetBackup considers the job complete and does not try to run another duplication job. Inactivate (or suspend) pending and future lifecycle operations on selected image copies. NetBackup retains the image information so that processing can resume. Activate (or resume) suspended lifecycle operations on selected image copies.

See NetBackup Commands for UNIX and Linux for a description of all the options available for nbstlutil.

When to use nbstlutil

NetBackup starts a duplication session every five minutes to copy data from a backup destination to a duplication destination. If a duplication job fails, the next three duplication sessions retry the job if necessary. If the job fails all three times, the job is retried every 24 hours until it succeeds.

266 Storage units, unit groups, and lifecycle policies Storage Lifecycle Policies

Use the nbstlutil command in the case of a hardware problem that may require more than 15 minutes to resolve. That is, the problem may take longer to resolve than three duplication sessions five minutes apart. For example, a duplication job fails because the library doesnt contain enough blank tapes. It may take longer than 15 minutes to place additional blank tapes into the tape library. The administrator may not want to wait 24 hours for the next duplication session. The nbstlutil command can be used to inactivate the lifecycle while tapes are added. When ready, the lifecycle can be activated and duplication jobs would begin.

Storage units, unit groups, and lifecycle policies Storage unit groups

267

Storage unit groups

Storage unit groups allow you to identify specific storage units as a group. A storage unit group name can be specified in a policy in the same way that individual storage units can be specified. When a storage unit group is used in a policy, only the storage units that are specified in the group are candidates for the backup.

Storage unit selection criteria within a group

The storage unit selection criteria determines the order that storage units are selected when they are included in a group. Choose from one of the following selection criteria.

Prioritized
NetBackup chooses the first storage unit in the list that is not busy, down, or out of media. Also, the storage unit must not have reached the maximum concurrent jobs setting. When one of the specified conditions occurs, the next storage unit in the list is examined until NetBackup finds an available storage unit. If one is not available or if one does not have enough available space, the job fails and is not queued. (Default.)

Failover
NetBackup chooses the first storage unit in the list that is not down, out of media, or full. If a storage unit is only busy, the policy waits to write to it. The other storage units are used as failovers. NetBackup queues a job to wait for the first storage unit if the maximum concurrent jobs setting is reached.

Round robin
NetBackup chooses the least recently selected storage unit in the list as each new job is started. If a storage unit is not available, or if no unit has available space, the job fails and is not queued. NetBackup does not continue to select the same storage unit.

Load balance
The Load balance option allows NetBackup to select storage units based on a capacity-managed approach. NetBackup avoids sending jobs to busy media servers. The selection is based on the following factors:

268 Storage units, unit groups, and lifecycle policies Storage unit groups

The rank of the media server. NetBackup considers the number of processes that are running on each CPU along with the memory thresholds on each server to determine the rank of a media server. If the free memory drops below a determined threshold, or if the number of running processes per CPU rises above a determined threshold, then the overall rank of the media server drops. The number of jobs on the media server. NetBackup considers the number of scheduled jobs on each media server. Whether the media server has enough disk space to accommodate the estimated size of the image NetBackup estimates the size of any new or current jobs on each media server and determines whether the jobs will fit on a given volume. NetBackup estimates the amount of space that the job may require, based on previous backup history. If no history is available, the high water mark for the storage unit serves as a guide.

2 3

When is the Load balance option available?

Load balance cannot be selected for a storage unit group that includes a BasicDisk storage unit. Also, a BasicDisk storage unit cannot be included in an existing storage unit group with Load balance enabled.

Storage units, unit groups, and lifecycle policies Storage unit groups

269

Figure 5-11

The Load balance option cannot be selected for a storage unit group that contains a BasicDisk storage unit

Note: Symantec recommends selecting Load balance for disk staging storage units within a storage unit group.

Other methods to distribute the backup workload

The Load balance option is based on the media server load and requires a license. The following list are methods to distribute the backup workload based on settings that do not require additional licenses:

To adjust the backup load on a media server:

Change the Limit jobs per policy policy attribute for one or more of the policies that are sent to a media server. To decrease Limit jobs per policy reduces the workload on a media server on a specific network segment. Reconfigure policies or schedules to use storage units on other media servers. See Limit jobs per policy on page 97.

270 Storage units, unit groups, and lifecycle policies Storage unit groups

Consider changing the Bandwidth host properties on one or more clients. See Bandwidth properties on page 377.

To distribute the backup load on media servers during peak periods: Reconfigure policy schedules so that they write to storage units on the media servers that can handle the load. (This assumes that master servers and media servers are on separate hosts.) To adjust the backup load on client Change the Maximum jobs per client global attribute. For example, to increase Maximum jobs per client increases the number of concurrent jobs that any one client can process and therefore increases the load..For more information, see Maximum jobs per client on page 436. To reduce the time to back up clients Increase the number of jobs that clients can perform concurrently, or use multiplexing. Another possibility is to increase the number of jobs that the media server can perform concurrently for the policies that back up the clients. To give preference to a policy Increase the Limit jobs per policy attribute for the preferred policy relative to other policies. Or, increase the priority for the policy. For more information, see Limit jobs per policy on page 97. To adjust the load between fast and slow networks Increase the Limit jobs per policy and Maximum jobs per client for policies and clients in a faster network. Decrease these numbers for slower networks. Another solution is to use NetBackups bandwidth limiting. For more information, see Limit jobs per policy on page 97 and Maximum jobs per client on page 436. To maximize the use of devices Use multiplexing. Allow as many concurrent jobs per storage unit, policy, and client as possible without causing server, client, or network performance problems. To prevent backups from monopolizing tape devices

Place some drives in a down state or limit the number that are used concurrently in a specific storage unit. For example, if there are four drives in a robot, allow only two to be used concurrently. Do not place all devices under Media Manager control.

Exception to the storage unit selection criteria

The only exception to the order option indicated is in the case of a client that is also a media server with locally connected storage units. The locally available

Storage units, unit groups, and lifecycle policies Storage unit groups

271

storage units take precedence over the defined sequence of storage units in the group. You may have set up a storage unit to be On demand only. If the unit is in a storage unit group that a policy requires, the On demand only option is satisfied and the device is used. For more information, see Policy storage on page 91.

Disk spanning within storage unit groups

A backup may span storage units if a disk full condition is detected. Backups may span from one BasicDisk storage unit to another BasicDisk storage unit if the storage units are in the same storage unit group. The storage units must also share the same media server. For more information, see Allow backups to span disk on page 450.

Creating a storage unit group

To create a storage unit group 1 2 3 In the NetBackup Administration Console, expand NetBackup Management > Storage. Right-click Storage Unit Groups and select New. The New Storage Unit Group dialog box appears. Enter a storage unit group name for the new storage unit group.

272 Storage units, unit groups, and lifecycle policies Storage unit groups

For more information, see NetBackup naming conventions on page 631.

Note: The storage unit group name is case-sensitive. 4 Add to or remove storage units from the group: a b c To add storage units to the group, select the storage units from the Storage units not in the group list. Click Add. To remove storage units from the group, select the storage units from the Storage units in group list. Click Remove. Storage units are listed in order of priority: The units at the top of the list having the highest priority in the group. To change the priority of a storage unit, select the storage unit and click Increase Priority or Decrease Priority.

Storage units, unit groups, and lifecycle policies Storage unit groups

273

Note: SnapVault, NearStore, and PureDisk storage units cannot be included in storage unit groups. 5 Choose how storage units are to be selected within the group:

Prioritized. Choose the first storage unit in the list that is not busy, down, or out of media. (See page 267.) Failover. Choose the first storage unit in the list that is not down or out of media. (See page 267.) Round Robin. Choose the least recently selected storage unit in the list. (See page 267.) Load Balance. (See page 267.) Symantec recommends the Load Balance criteria for disk staging storage units within a storage unit group.

Click OK.

Deleting a storage unit group

To delete a storage unit group 1 2 In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Unit Groups. Select the storage unit group you want to delete from those listed in the Details pane. Hold down the Control or Shift key to select multiple storage units. Select Edit > Delete. A confirmation dialog box appears. Click OK.

3 4

274 Storage units, unit groups, and lifecycle policies Storage unit groups

Chapter

NetBackup Catalog
This chapter describes the role that the catalog plays in a NetBackup environment. This includes how to configure a catalog back up and perform a catalog recovery. The various functions that an administrator can perform in the Catalog utility are also explained.

What is a NetBackup catalog? on page 276 Catalog protection on page 282 Recovering the catalog on page 317 Disaster recovery emails and the disaster recovery file on page 317 Archiving the catalog on page 318 Using the Catalog utility on page 324 Catalog maintenance and performance optimization on page 347

276 NetBackup Catalog What is a NetBackup catalog?

What is a NetBackup catalog?

NetBackup catalogs are the internal databases that contain information about NetBackup backups and configuration. Backup information includes records of the files that have been backed up and the media on which the files are stored. The catalogs also contain information about the media and the storage devices. Since NetBackup requires the catalog information to restore backups, configure a catalog backup before using NetBackup for regular client backups. Then, schedule the catalog backups to occur on a regular basis thereafter. Without regular catalog backups, you risk losing regular backups if there is a problem with the disk that contains the catalogs.

Parts of the catalog

The NetBackup catalog resides on the disk of the NetBackup master server. The catalog consists of the following parts:

Image database: The image database contains information about what has been backed up. It is by far the largest part of the catalog. For more information, see Image database on page 277. NetBackup data that is stored in relational databases: The data includes media and volume data describing media usage and volume information, which is used during the backups. For more information, see NetBackup relational database on page 280. NetBackup configuration files: The configuration files include flat files concerning policy and schedule information.

NetBackup Catalog What is a NetBackup catalog?

277

Figure 6-1

Catalog configuration (default)

/usr/openv/

/db/data

/netbackup/db

/netbackup/vault

/var License key and authentication information

/var/global

NBDB.db EMM_DATA.db EMM_INDEX.db NBDB.log BMRDB.db BMRDB.log BMR_DATA.db BMR_INDEX.db vxdbms.conf Relational database files /client_1 /Master /client_n /Media_server Image database /class /class_ template /client /config /failure_history /media /error /images /jobs /vault

server.conf databases.conf

Configuration files

Image database
The image database (/usr/openv/netbackup/db/images) contains subdirectories for each client that is backed up by NetBackup, including the master server and any media servers. The image database contains:

Image files (files that store only backup set summary information) Image .f files (files that store the detailed information of each file backup)

The image database is the largest part of the NetBackup catalog. It consumes about 99% of the total space that is required for the NetBackup catalog. While most of the subdirectories are relatively small in the NetBackup catalogs, /images can grow to several tens, or even hundreds of gigabytes. The image database on the master server may grow too large to fit on a single tape. The database growth is an important consideration for offline, cold catalog backups. Image database growth depends on the number of clients, policy schedules, and the amount of data that is backed up.

278 NetBackup Catalog What is a NetBackup catalog?

To determine catalog space requirements, see Determining catalog space requirements on page 347. If the image catalog becomes too large for the current location, consider moving it to a file system or disk partition that contains more space. For more information, see Moving the image catalog on page 354. The image database component of the NetBackup catalog uses the .f files in binary format for Windows, Solaris, HP_UX, Compaq Tru64 UNIX, AIX, and Linux platforms. The catalog conversion utility (cat_convert) can be used to upgrade an image database to the binary format. (See Catalog conversion utility on page 354.)

Image files
Each image file is an ASCII file, generally less than 1 kilobyte in size. An image file contains only backup set summary information. For example, the backup ID, the backup type, the expiration date, fragment information, and disaster recovery information.

Image .f files
The binary catalog may contain one or more image .f files. This type of file is also referred to as a files-file. The image .f file may be large because it contains the detailed backup selection list for each file backup. Generally, image files range in size from 1 kilobyte to 10 gigabytes. The file layout determines whether the catalog contains one .f file or many .f files. NetBackup configures the file layout automatically, based on the size of the binary catalog. NetBackup uses one of two layouts: single file layout or multiple file layout.

Image .f file single file layout

NetBackup stores file information in a single image.f file if the information for the catalog is less than 4 megabytes. When the backup file of one catalog backup is less than 4 megabytes, NetBackup stores the information in a single image.f file. The image.f file is always greater than or equal to 72 bytes, but less than 4 megabytes. The following is an example of an .f file in a single file layout:
-rw------- 1 root other 979483 Aug 29 12:23 test_1030638194_FULL .f

Image .f file multiple file layout

When the file information for one catalog backup is greater than 4 megabytes, the information is stored in multiple .f files: one main image .f file plus nine additional .f files.

NetBackup Catalog What is a NetBackup catalog?

279

Separating the additional .f files from the image .f file and storing the files in the catstore directory improves performance while writing to the catalog. The main image.f file is always exactly 72 bytes.
-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw1 1 1 1 1 1 1 1 1 1 root root root root root root root root root root other other other other other other other other other other 72 804 1489728 0 1280176 192 0 9112680 2111864 11 Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug 30 30 30 30 30 30 30 30 30 30 00:40 test_1030680524_INCR.f 00:08 catstore/test_1030680524_INCR.f-list 00:39 catstore/test_1030680524_INCR.f_imgDir0 00:40 catstore/test_1030680524_INCR.f_imgExtraObj0 00:39 catstore/test_1030680524_INCR.f_imgFile0 00:40 catstore/test_1030680524_INCR.f_imgHeader0 00:40 catstore/test_1030680524_INCR.f_imgNDMP0 00:39 catstore/test_1030680524_INCR.f_imgRecord0 00:39 catstore/test_1030680524_INCR.f_imgStrings0 00:40 catstore/test_1030680524_INCR.f_imgUserGroupNames0

280 NetBackup Catalog What is a NetBackup catalog?

NetBackup relational database

NetBackup installs Sybase Adaptive Server Anywhere 9.0.1 during the master server installation as a private, non-shared server for the NetBackup database (NBDB). The same installation of Sybase ASA is used for the optionally-licensed product, Bare Metal Restore (BMR) database (BMRDB). The following describes the components:

Bare Metal Restore (BMR) database: The BMRDB database contains the information that the NetBackup Bare Metal Restore option manages. The BMR database is created during the BMR installation process. NetBackup database (NBDB): Also known as the Enterprise Media Manager (EMM) database, the NBDB contains information about volumes and the robots and drives that are in NetBackup storage units. For more information, see Enterprise Media Manager (EMM) database on page 281.

As part of the catalog backup, the database and the configuration files for the NBDB and the BMRDB databases are protected:

Database files:

/usr/openv/db/data/NBDB.db /usr/openv/db/data/EMM_DATA.db /usr/openv/db/data/EMM_INDEX.db /usr/openv/db/data/NBDB.log /usr/openv/db/data/BMRDB.db (if BMR is installed) /usr/openv/db/data/BMRDB.log (if BMR is installed) /usr/openv/db/data/BMR_DATA.db (if BMR is installed) /usr/openv/db/data/BMR_INDEX.db (if BMR is installed)

Configuration files:

/usr/openv/db/data/vxdbms.conf /usr/openv/var/global/server.conf /usr/openv/var/global/databases.conf

Note: The catalog backup process copies this data to /usr/openv/db/staging and backs up the copy. For information about how the catalog uses Sybase ASA, see Appendix A, NetBackup relational database on page 697.

NetBackup Catalog What is a NetBackup catalog?

281

Enterprise Media Manager (EMM) database

The Enterprise Media Manager (EMM) database contains information about media and the robots and drives that are in NetBackup storage units. The NetBackup Resource Broker queries the EMM database to allocate storage units, drives (including drive paths), and media. The host on which the EMM database resides is called the EMM server. The EMM database contains the following information:

Device attributes Robotic library and stand-alone drive residence attributes NDMP attributes Barcode rule attributes Volume pool attributes Tape and optical disk volume attributes Media attributes Storage unit attributes Storage unit group attributes Hosts with assigned tape drives Media and device errors Disk pool and disk volume attributes Storage server attributes Login credentials for storage servers, disk arrays, and NDMP hosts Fibre Transport attributes

282 NetBackup Catalog Catalog protection

Catalog protection
In order for NetBackup to restore any file, NetBackup needs information from the catalog to determine where the backup for the file is located. Without a catalog, NetBackup cannot restore data. Because the catalog plays an integral part in a NetBackup environment, a particular type of backup--a catalog backup--protects the catalog. A catalog backup backs up catalog-specific data as well as produces disaster recovery information. As additional protection for the catalog, you may consider archiving the catalog as well. (See Archiving the catalog on page 318.) Note: The Recommended Backup Practices, section in Chapter 7 of the NetBackup Troubleshooting Guide provides helpful setup information to aid in disaster recovery. Since the catalog plays a critical role in the NetBackup environment, much of the information concentrates on catalog considerations.

Catalog backups
A catalog backup is configured separately from regular client backups by using the Catalog Backup Wizard. The catalog can be stored on a variety of media. Note: Configure a catalog backup before you run any regular backups.

Note: If portions of the catalog are relocated, note the changes so that subsequent catalog backups are aware of the locations of all the catalog components. In the event that a catalog recovery is needed, the same alterations must be implemented before the recovery of the catalog. Choose the catalog backup method that works best for your environment:

Online, hot catalog backup (recommended method) This type of catalog backup is for active environments in which continual backup activity occurs. It is considered an online, hot method because it can be performed while regular backup activity occurs. This type of catalog is policy-based and can span more than one tape. It also allows for incremental backups, which can significantly reduce catalog backup times for large catalogs.

NetBackup Catalog Catalog protection

283

Online, hot catalog backups use media from the CatalogBackup volume pool only. For more information, see Online, hot catalog backup method on page 283.

Offline, cold catalog backup This type of catalog backup is for environments in which periods of no backup activity exist. It is considered an offline, cold backup because it should not be run when regular backup activity occurs. For Sybase ASA, the databases (NBDB and BMRDB) are shut down during the backup. This type of catalog backup must fit on a single tape. Offline, cold catalog backups use media from the NetBackup volume pool only. For more information, see Offline, cold catalog backup method on page 296.

Online, hot catalog backup method

The online catalog is policy-based, which means that it has all of the scheduling flexibility of a regular backup policy. The online catalog is designed for active environments in which continual backup activity occurs and the catalog size is large. The online, hot catalog backup:

Can back up the catalog while continual client backups are in progress. Can span multiple tapes for a catalog backup. Allows for a flexible pool of catalog tapes. Can perform a full or an incremental catalog backup. Can restore the catalog to a different location. Can run scheduled catalog backups. Offers a wizard to automate the catalog recovery process or a guided command line tool. Appends to existing data on tape. Can be duplicated. By using the Catalog Backup Wizard. See To configure an online, hot catalog backup using the catalog backup wizard on page 284. By using the Backup Policy Configuration Wizard. See To configure an online, hot catalog backup using the backup policy wizard on page 292. By selecting the NBU-Catalog type when creating a backup policy.

Configure an online catalog backup using one of the following methods:

284 NetBackup Catalog Catalog protection

See To configure an online, hot catalog backup using the policy utility on page 293. To configure an online, hot catalog backup using the catalog backup wizard Note: Online, hot catalog policies (policy type NBU-Catalog) write only to media in the CatalogBackup volume pool. This procedure assumes that a storage device is configured and media is available in the CatalogBackup volume pool. For more information, see Adding volumes on page 508. 1 Launch the NetBackup Catalog Backup Wizard by clicking Configure the Catalog Backup in the right pane. The wizard is visible when either Master Server or NetBackup Management is selected in the left pane. Click Help within any wizard screen for more information on the wizard settings. Click Next on the Welcome screen. On the Catalog Backup Method screen, select to configure an online, hot catalog backup.

2 3

Click Next.

NetBackup Catalog Catalog protection

285

On the Catalog Backup Policy screen, select a policy from the list of existing catalog backup policies.

Or, to create a new catalog backup policy, select Create a new catalog backup policy. Click Next to launch the Policy Name and Type screen of the Backup Policy wizard. Enter the policy name. Notice that NBU-Catalog is automatically selected as the policy type. Type a unique name for the new policy in the Add a New Policy dialog box. For more information, see NetBackup naming conventions on page 631.

286 NetBackup Catalog Catalog protection

Click OK.

Select the backup type. (User Backup does not apply for NBU-Catalog policies.)

NetBackup Catalog Catalog protection

287

Select the rotation schedule.

The selection After each backup session refers to a period when no regular backup policy is running. By default, a frequency-based schedule is selected. A frequency-based schedule ensures that the catalog backup has an opportunity to run in busy environments where backup jobs are running. Note: If online, hot catalog backups are scheduled to run concurrently with other backup types on the master server, see Running online, hot catalog backups concurrently with other backups on page 294. 10 In the Start Window screen, define a window of time during which the catalog backup can start. The scheduled windows (Off hours, Working hours,

288 NetBackup Catalog Catalog protection

All day) are preset in the wizard, but can be customized using the Policies utility.

User Window selections are disabled, as regular users (those who are not NetBackup administrators) cannot start catalog backups. 11 Select where each disaster recovery image file can be saved on disk. The image file contains the disaster recovery information.

NetBackup Catalog Catalog protection

289

Note: Symantec recommends that you save the image file to a network share or a removable device. Do not save the disaster recovery information to the local machine. Enter the path to the directory where the disaster recovery information can be saved. Specify an NFS share. If necessary, enter the logon and password information to access the NFS share. Note: If the logon information is not valid, NetBackup returns a message. The message requests that the user either reenter the logon and password information or clear the alternate location option to continue. Logon and password fields are enabled: - If the path begins with \\ which indicates a UNC share path. - If NetBackup does not have write access to the location that the user has specified. 12 Symantec recommends that the NetBackup environment be configured to send the disaster recovery information to a NetBackup administrator. This backup-specific information is sent after every catalog backup.

To send the information to more than one administrator, separate multiple email addresses using a comma: [email protected],[email protected]

290 NetBackup Catalog Catalog protection

Make sure that email notification is enabled in your environment. For more information on the email and the attached disaster recovery file, see Disaster recovery emails and the disaster recovery file on page 317. Also, see Send in an email attachment on page 197. Note: The disaster recovery email is not sent to the address that is specified in the Global Attributes property. The Administrators email Address specifies the addresses where NetBackup sends notifications of scheduled backups or administrator-directed manual backups. 13 The last screen of the policy wizard lets you know that once the policy is created, you can make changes in NetBackup Management > Policies.

Click Finish to create the policy.

NetBackup Catalog Catalog protection

291

14 The Catalog Backup Wizard resumes, with the new policy listed.

15 Click Next to finish the Catalog Backup Wizard. 16 The final Catalog Backup Wizard screen displays the total number of catalog backup policies for this master server.

17 Click Finish to complete the wizard.

292 NetBackup Catalog Catalog protection

To configure an online, hot catalog backup using the backup policy wizard Using the Backup Policy Wizard to create an online, hot catalog backup policy is similar to using the Catalog Backup Wizard. Note: Online, hot catalog policies (policy type NBU-Catalog) write only to media in the CatalogBackup volume pool. This procedure assumes that a storage device is configured and media is available in the CatalogBackup volume pool. For more information, see Adding volumes on page 508. 1 Launch the Backup Policy Configuration Wizard by clicking Create a Backup Policy in the right pane. The wizard is visible when either Master Server or NetBackup Management is selected in the left pane. Click Help within any wizard screen for more information on the wizard settings. Click Next on the Welcome screen. Enter the policy name and select NBU-Catalog as the policy type. Click OK. (See NetBackup naming conventions on page 631.) Select the backup type. (User Backup does not apply for NBU-Catalog policies.) Select the rotation schedule. For NBU-Catalog policy types that run incremental backups, Every backup session end means a period when no regular backup policy is running. In the Start Window screen, define a window of time during which the catalog backup can start. The windows are preset in the wizard, but can be customized using the Policies utility. User Window selections are disabled because regular users (those who are not NetBackup administrators) cannot start catalog backups. Select where each disaster recovery image file can be saved on disk. Note: Symantec recommends that the image file be saved to a network share or a removable device. Do not save the disaster recovery information to the local machine. Disk Information

2 3 4 5

Path to the disk: For UNIX master servers, specify a local directory or NFS share. For Windows master servers, specify a local directory or UNC path (CIFS Windows share). Logon information that is used to:

Access the NFS share for UNIX master servers.

NetBackup Catalog Catalog protection

293

Access the Windows share for Windows master servers.

Note: If the logon information is not valid, NetBackup returns a message. The message requests that the user either reenter the logon and password information and clear the alternate location option to continue. Logon and password fields are enabled: - If the path begins with \\ which indicates a UNC share path. - If NetBackup does not have write access to the location that the user has specified. 8 Symantec suggests having the disaster recovery information e-mailed to an NetBackup administrator in your organization. The disaster recovery information is sent after every catalog backup. Click Finish to complete the wizard.

To configure an online, hot catalog backup using the policy utility 1 2 3 4 In the NetBackup Administration Console, expand NetBackup Management >Policies. Select Actions > New > Policy. Type a unique name for the new policy in the Add a New Policy dialog box. Click OK. (See NetBackup naming conventions on page 631.) The following fields on the Attributes tab apply to online, hot catalog backups. For information about other fields on this tab, see Policy Attributes tab on page 87. Policy Type: Select NBU-Catalog as the policy type. Policy storage: For disk storage units, increase the Maximum Concurrent Jobs setting to ensure that the catalog backup can proceed during regular backup activity. Note: Online catalog backups must use media servers at version 6.0 or later to store catalog backup data. If your installation contains 5.x and 6.0 media servers, do not select Any Available for the destination Policy Storage Unit, since it is possible that the 5.x media server could be selected. Policy volume pool: NetBackup automatically creates a CatalogBackup volume pool that is selected by default only for NBU-Catalog policy types. Offline, cold catalog backups use media from the NetBackup volume pool. 5 Set up a schedule for an online catalog backup. For information on the Schedules tab settings, see Schedules tab on page 117.

294 NetBackup Catalog Catalog protection

See the following sections for additional information regarding online catalog backup schedules: Running online, hot catalog backups concurrently with other backups and Notes on catalog policy schedules. Note: The Clients tab does not apply to the NBU-Catalog policy and is not displayed. 6 The Disaster Recovery tab appears for NBU-Catalog policies only. The tab contains information regarding the location of data crucial to disaster recovery:

The path to the directory where the disaster recover information can be saved. The logon and password information to the share. The email address(es) where disaster recovery reports can be sent.

A critical policy list, which contains the names of policies that back up critical data. Media that contains critical policy backups is listed on the NetBackup Disaster Recovery Report that is generated when the online catalog backup is run. For information on the Disaster Recovery tab settings, see Disaster Recovery tab on page 196.

Running online, hot catalog backups concurrently with other backups

Online, hot catalog backups may be scheduled to run concurrently with other backup types for the master server. Make the following adjustments to ensure that the catalog backup can proceed while regular backup activity occurs:

Set the Maximum Jobs per Client value to greater than one. The property is found in the Global Attributes host properties for the master server. (See Global Attributes properties on page 435.) Increase the Maximum Concurrent Jobs setting on the storage unit where the backups are sent. (See Maximum concurrent jobs on page 231.)

Notes on catalog policy schedules

The following schedules are supported in the online, hot catalog backup policy type:

Full Differential incremental (depends on a full schedule) Cumulative incremental

NetBackup Catalog Catalog protection

295

Session-based differential incremental Session-based cumulative incremental

Symantec recommends that only one catalog backup policy be configured. Online catalog backups must use media servers at version 6.0 or later to store catalog backup data. If the installation contains 5.x and 6.0 media servers hosting disk storage units, do not select Any Available as the destination Policy storage. If Any Available is selected, a 5.x media server could possibly be selected. The incremental schedule depends on a full schedule. The least frequent schedule runs if many schedules are due at the same time. There can be more than one session-based incremental schedule in one catalog backup policy:

If one is cumulative and the other is differential, the cumulative runs when the backup session ends. If both are cumulative or both are differential, the first schedule that is found runs when the backup session ends.

The queued scheduled catalog backup is skipped if a catalog backup job from the same policy is running. Session end means that no jobs are running. (This calculation does not include catalog backup jobs.) The Vault catalog backup is run whenever triggered from Vault, regardless of whether a catalog backup job is running from the same policy. When an online catalog backup is run, it generates three jobs: a parent job, a child job for NetBackup relational database tables, and a child job for catalog images and configuration data. The child jobs contain the actual backed up data. Both child jobs should be considered to duplicate, verify, or expire the backup. Note: Additional child catalog jobs are created for 5.x media servers and the BMR database if a remote EMM server is configured.

How catalog incrementals and standard backups interact

A hot catalog backup policy can include both full and incremental catalog backups. However, incremental catalog backups differ from incremental standard backups. Hot catalog backups use both mtime and ctime to identify changed data. Standard incremental backups use only mtime to identify changed data.

296 NetBackup Catalog Catalog protection

Because of this difference, running a standard policy type backup that includes the /usr/openv/netbackup/db/images/ directory can adversely affect incremental hot catalog backups. When standard backups run, they reset the file access time (atime). In turn, this changes the ctime for files and directories. If an incremental catalog backup runs, it sees that the ctime has changed and unnecessarily backs up the files; files that may not have changed since the last catalog backup. To avoid additional processing during hot catalog backups, Symantec recommends the following:

If incremental hot catalog backups are configured, exclude the NetBackup /usr/openv/netbackup/db/images/ directory from standard backups. To exclude that directory, create a /usr/openv/netbackup/exclude_list file on the master server. Cold catalog backups also change the ctime. Do not configure both cold catalog backups and incremental hot catalog backups to run in a NetBackup configuration.

Offline, cold catalog backup method

The offline, cold catalog backup can be used in NetBackup environments with catalogs small enough to fit onto a single tape. This type of catalog backup is for environments in which periods of no backup activity exist. Configure an offline catalog backup using one of the following methods:

By using the Catalog Backup Wizard. For more information, see To configure an offline, cold catalog backup using the catalog backup wizard on page 298. By selecting Actions > Configure offline NetBackup Catalog Backup. For more information, see To configure an offline, cold catalog backup using the Actions menu on page 305.

The offline, cold catalog backup is suitable in many installations. However, this catalog backup differs from the online, hot catalog backup in a number of ways. The following items are the same limitations that existed in previous NetBackup releases. They are provided here for purposes of comparison. The offline, cold catalog backup:

Cannot back up the catalog while any job or any catalog operation is running. Cannot span tapes. Is not tracked like a regular backup. Since online, hot catalog backups are run as jobs by a policy, the online, hot catalog backup job is included in the catalog.

NetBackup Catalog Catalog protection

297

Cannot be duplicated as regular backups and online, hot catalog backups can be duplicated. Cannot be written to media and given an expiration date. Cannot be an incremental backup. Overwrites any data on a tape. This type of catalog backup starts at the beginning of the tape and does not append to existing data on the tape.

298 NetBackup Catalog Catalog protection

To configure an offline, cold catalog backup using the catalog backup wizard Note: Offline, cold catalog policies write only to media in the NetBackup volume pool. This procedure assumes that a storage device is configured and media is available in the CatalogBackup volume pool. For more information, see Adding volumes on page 508. 1 Launch the NetBackup Catalog Backup Wizard by clicking Configure the Catalog Backup in the right pane. The wizard is visible when either Master Server or NetBackup Management is selected in the left pane. The wizard is also available using the following methods:

Select the Catalog utility, then select Actions > Configure Offline NetBackup Catalog Backup.

Right-click the Catalog utility in the left pane and select Configure Offline NetBackup Catalog Backup. Click Help within any wizard screen for more information on the wizard settings.

Click Next on the Welcome screen.

On the Catalog Backup Method screen, select to configure an offline, cold catalog backup. Click Next.

NetBackup Catalog Catalog protection

299

Specify the media server where the catalog backups are to be sent.

Select the media servers that should be backed up in this catalog backup.

NetBackup displays where catalog files have been located.

300 NetBackup Catalog Catalog protection

Indicate where the catalog files are located.

The catalog paths on the master server are added automatically during installation. Generally, no action is required other than to ensure that the directories are listed. Verify that the catalogs of the master server and each media server are included. Verify that the path names are correct and are in the correct format. The NETBACKUP_RELATIONAL_DATABASE_FILES directive automatically includes the database files in the /usr/openv/db/data/ directory, as well as vxdbms.conf, server.conf, and databases.conf. (If the files have been relocated to different directories using nbdb_move, the locations are automatically determined and the files are included.) If NetBackup Access Control (NBAC) is used in the NetBackup configuration, add the following directives for each host in the NBAC domain: [host:]nbat [host:]nbaz Note: For UNIX master servers, do not include the NetBackup master server configuration file in the offline catalog backup file list. (/usr/openv/netbackup/bp.conf) If bp.conf is included in the list, it must not be recovered until all other catalog recovery is completed. If NetBackup cannot find or follow a path, the entire catalog backup fails. Notes Regarding the Catalog File Locations List

If you have moved the location of the catalog on the master server, the new location must be specified.

NetBackup Catalog Catalog protection

301

On media servers, paths to the catalog are not automatically added during installation and must be added to this list. If /usr/openv/netbackup/db/images is a symbolic link to another file system, you must specify the true location of the images directory here. Symbolic links do not apply to Windows. The entire catalog backup fails if the final component in a UNIX path is a symbolic link. While NetBackup follows links at other points in the path, NetBackup does not follow a link when it is the final component. If any other part of a listed path is a symbolic link, NetBackup saves the actual path during the backup. The files that are associated with the NetBackup relational databases are automatically included in the catalog backup and dont need to be listed here. (NBDB and BMRDB.) The paths are dynamically generated during the backup since the locations of these files can change.

If both removable media and disk is configured, the Media Type for the Destination screen displays. Specify removable media or disk for the backup. For this example, well select Removable Media.

Select a destination volume from the drop-down list to store the catalog backup. Note: Note the media ID of the volume that was selected to know which volume contains catalog backups.

302 NetBackup Catalog Catalog protection

10 You may prefer to back up the catalog to two different locations. The catalog backup alternates for each catalog backup.

Alternate destinations adds protection in the event that a disk or tape that contains a catalog backup is lost. NetBackup always backs up to the media that was not used for the previous catalog backup. 11 Specify whether the alternate destination for the catalog backup is to removable media or to disk. For this example, well select Disk.

NetBackup Catalog Catalog protection

303

12 Enter the path to the alternate destination for the catalog backup.

The path can point to:

A directory on a disk that is attached to the master server. NetBackup creates the directory if it does not exist. An NFS-mounted file system or a link to an NFS-mounted file system that grants write access to the root user.

A shared directory on another computer. This shared directory must be available to the service account that the NetBackup Client service logs into at startup. In addition to the platform-specific file path separators (/ and \) and colon (:) within a drive specification on Windows, follow the NetBackup naming conventions. (For more information, see NetBackup naming conventions on page 631.)

304 NetBackup Catalog Catalog protection

13 The frequency of catalog backups is configurable. Choose one of the following options:

After each session of scheduled, user, or manual backups Consider this option if you plan to send catalog backups to a robot, a tape stacker, a second stand-alone tape drive, or to disk. After each session of scheduled backups Consider this option if you plan to send catalog backups to a robot, a tape stacker, a second stand-alone tape drive, or to disk. Also, consider this option if there is only one scheduled backup session per day or night. This schedule type requires that no jobs are running in order for the catalog backup to run. Caution: Do not use this schedule in NetBackup environments in which continual backup activity occurs because the catalog backup might never have an opportunity to run. Only when manually initiated Consider this option to run multiple backup sessions in a single day or night. Be certain to perform a manual catalog backup once a day or after a series of backups. Caution: Back up the catalogs often. If catalog backup files are lost, the changes that were made between the last catalog backup and the time of the disk crash are lost.

NetBackup Catalog Catalog protection

305

14 The final wizard screen displays the total number of catalog backup policies that are configured for this master server. Click Finish to complete the wizard.

To configure an offline, cold catalog backup using the Actions menu Note: Offline, cold catalog policies write only to media in the NetBackup volume pool. This procedure assumes that a storage device is configured and media is available in the CatalogBackup volume pool. For more information, see Adding volumes on page 508. 1 2 In the NetBackup Administration Console, expand NetBackup Management > Catalog. With the Catalog utility in focus, select Actions > Configure Offline NetBackup Catalog Backup. The Catalog Backup Configuration dialog box appears containing four tabs: Intro, Attributes, Schedule, Files. Specify the properties on each tab of the dialog box:

Catalog intro tab on page 306 Catalog attributes tab on page 307 Catalog schedule tab on page 311 Catalog files tab on page 312

Click OK.

306 NetBackup Catalog Catalog protection

Catalog intro tab

The Catalog Intro tab informs users as to how many online, hot catalog backup policies are configured. The tab also tells whether or not an offline, cold backup is scheduled.

The tab reminds the users that another type of catalog backup is available that might serve their needs better: the online, hot catalog backup. (See Catalog backups on page 282.)

NetBackup Catalog Catalog protection

307

Catalog attributes tab

The Attributes tab contains general attributes for NetBackup catalog backups.

Media Server The following setting applies only to NetBackup Enterprise Server: The Media Server setting specifies the name of the media server to which catalog backups are sent. This defaults to the master server where you are running the NetBackup Administration Console. To choose a server, select one from the drop-down menu. The list shows all servers that have a storage unit that is defined on the current master server. If you back up the catalogs to a media server, modify the NetBackup catalog backup paths on the master server using the Catalog Files tab. (See Catalog files tab on page 312.) Ensure that the media server is named in the bp.conf file on the master server. On NetBackup Server, Media Server cannot be changed and is the NetBackup server where the catalogs reside. Last Media Used The Last Media Used setting shows the media ID (for Removable Media) or the absolute path (for disk) that contains the last NetBackup catalog backup. The value in this field is the value that you specified for either Media 1 or Media 2. These are the media that NetBackup alternates between for catalog backups. Media 1 and Media 2 Areas

308 NetBackup Catalog Catalog protection

The Media 1 and Media 2 Areas setting specifies the media to use for the catalog backups. You do not have to assign both Media 1 and Media 2. If you do assign both, NetBackup alternates between the media. Media Type The Media Type setting specifies the media type. Select one from the drop-down menu:

None: No media is assigned Disk: A directory on a disk drive Removable Media: A volume that is in a robot or drive under control of Media Manager

Depending on the storage devices that are available, Symantec recommends the following choices for Media Type: 1 2 3 If you use a robot or a tape stacker, choose Removable Media to select the automated device. If you use a stand-alone storage device for catalog backups, choose Removable Media and use the stand-alone device. If you use only one stand-alone drive (no robot or tape stacker), the most convenient method is to choose Disk for the media type. Send the catalog backups to a hard drive. The hard drive that you use for the catalog backup must be different than the hard drive where the catalogs reside. By default, the catalogs are stored in the following locations: /usr/openv/netbackup/db /usr/openv/var/global /usr/openv/db/data If you choose to back up the catalog to disk, the destination of the catalog backup must be on a different drive.

Caution: The safest way to protect your data is to save all backups to removable media. Move a full set of the media to off-site storage on a regular basis. A backup that is written only to disk shares the same risks as the computers being backed up. A natural disaster is more likely to destroy both the primary data and the backups if the backups are written only to disk. If the disks holding the catalogs and the catalog backup are both destroyed, recovering your business data is much more difficult. Assuming the backups are on tape, recovering without the catalog backup means manually importing all of the backup tapes to rebuild the catalogs. Importing consumes the time that you may not want to spend when you need to resume business activities.

NetBackup Catalog Catalog protection

309

If you have only one stand-alone drive (no robot or tape stacker) and inadequate space on a different hard drive, choose Removable Media. In this situation, you must back up the catalogs to the same tape drive as the backups of your business data. To back up to single tape drive involves swapping tapes in and out of the drive each time the catalogs are backed up. Swapping tapes is inconvenient, but it is required because NetBackup does not place catalog backups and the backups of business data on the same tape.

Media ID If youve chosen Removable Media, specify a valid media ID. The volume that is specified must be configured under Media in the same manner as other NetBackup volumes. The media ID must appear under Media and Device Management > Media. The volume must also meet the following requirements:

The volume must be in the NetBackup volume pool. To verify, look under Media and ensure that the Volume Pool column for the media ID displays NetBackup. The volume cannot be currently assigned to NetBackup for backups because NetBackup does not mix catalog backups and regular backups on the same media. To locate an available volume, expand Media and Device Management > Media. Find a volume where the Time Assigned column is empty and the Status column is 0. Once a catalog backup occurs, the Time Assigned and the Status column for the volume updates.

Note: If a column does not appear, size the columns by right-clicking in the pane and selecting Columns from the shortcut menu. The Last Written information under Media 1 and Media 2 indicates when the volume that is specified in the Media ID field was last used. The value is never if the volume has never been used for NetBackup catalog backups. Note: If the media ID for a volume that was used for catalog backups is deleted, then added back, NetBackup changes the Last Written date and time. However, the contents of the volume itself are not altered until the next time the volume is used for a backup. The Allocated information under Media 1 and Media 2 indicate when the media was allocated for NetBackup catalog backups. Notes on the Media ID

310 NetBackup Catalog Catalog protection

To delete the media for Media 1 or Media 2, set the Media Type value to None. Do not use backspace to leave the Media ID box blank. If you delete a volume from the catalog backup configuration, Media Manager makes the volume available for reassignment. Reassigning the volume can cause problems if, for example, you temporarily back up the catalog to a different volume. You must manually track the media that is used for catalog backups. NetBackup does not keep a record of catalog backup media in its catalogs as it does with other backup media. If NetBackup tracks catalog backup media in the catalog, and the disk containing the catalogs crashes, the record is lost with the catalogs. A convenient way to track the media is to indicate an email address in the Global Attributes properties. NetBackup sends an email that includes the status of each catalog backup and the media ID that was used. Print the email or save it on a disk other than the disk containing the catalogs. (See Global Attributes properties on page 435.) If the catalogs are intact, you can also find these media IDs in the Media Manager volume listing. The Status column shows 1 for these volumes. However, these IDs do not appear in the NetBackup media reports.

Pathname (Disk Media Type) For disk media, the Pathname is the path to the directory where you want to store the catalog backup. Type the path in the field. For example:
/nb/dbbackup

The path can be any of the following:

A directory on a disk that is attached to the master server. NetBackup creates the directory if it does not exist. An NFS-mounted file system or a link to an NFS-mounted file system that grants write access to the root user. Always back up to a physical disk different from the disk containing the catalogs. For example, if your computer has two physical disks and the catalogs are on the first disk, back up the catalogs to the second disk. If you back up the catalogs to the same disk and that disk fails, both the catalogs and the backups are lost. In that case, restoring data for the NetBackup clients is difficult or impossible. By default, the catalogs are stored in the following locations, so the destination of your catalog backup must be on a different disk: /usr/openv/netbackup/db /usr/openv/var/global /usr/openv/db/data

When the catalogs are backed up to disk, observe the following precautions:

NetBackup Catalog Catalog protection

311

Ensure that the disk has adequate space for the catalogs. If the disk fills up, the catalog backups fail. Ensure that the path is a directory rather than a file. If the path is a file, an error occurs when the backup is done (not when you specify the path). The following rule applies to the path you specify: In addition to the platform-specific file path separators (/ and \) and colon (:) within a drive specification on Windows, follow the NetBackup naming conventions. (See NetBackup naming conventions on page 631.)

Catalog schedule tab

The Catalog Schedule tab contains selections concerning when you want to back up the catalogs.

Caution: Back up the catalogs often. If catalog backup files are lost, the changes that were made between the last catalog backup and the time of the disk crash are lost.

After each session of scheduled, user, or manual backups Backs up the catalogs after any session that results in the creation of at least one successful backup or archive. After each session of scheduled backups Backs up the catalogs after any automatic backup session that results in at least one successful backup of a client. A backup does not occur after a manual backup or a user backup or archive.

312 NetBackup Catalog Catalog protection

This schedule type requires that no jobs are running in order for the catalog backup to run. Caution: Do not use this schedule in NetBackup environments in which continual backup activity occurs. It could mean that the catalog backup would never have an opportunity to run.

Only when manually initiated Does not automatically back up the catalogs. If you elect to back up catalogs manually, select NetBackup Management > Catalog. Right-click Catalog and select Back up NetBackup Catalog.

Caution: If you elect to back up catalogs manually, be certain to do so once a day or after every series of backups.

Catalog files tab

The Catalog Files tab contains the absolute paths to the catalog files to be backed up.

Click to navigate to a directory or file

The catalog paths on the master server are added automatically during installation. Generally, no action is required other than to ensure that the directories are listed. In the case of NetBackup Enterprise Server, the master server and media servers may reside on different machines. Therefore, the paths to the NetBackup database on the media servers are not automatically added during installation. You must add the paths to the file list. The NETBACKUP_RELATIONAL_DATABASE_FILES directive automatically includes the database files in the /usr/openv/db/data/ directory, as well as vxdbms.conf, server.conf, and databases.conf. (If the files have been relocated to different directories using nbdb_move, the locations are determined automatically and are included.)

NetBackup Catalog Catalog protection

313

Note: The file names in the Catalog Files Location list are case-sensitive. The catalog backup fails if the entries are typed without regard to case. On the Files tab:

To add a path, click New and type the path in the Catalog File Locations list. The path format depends on whether the catalog is on a master server or a remote media server. It also depends on whether the backup is sent to the master server or to a remote media server. To change a path, select the path and click Change. Edit the path. Click outside the edit box to escape the edit box. To delete a path, select the path to delete and click Delete.

314 NetBackup Catalog Catalog protection

Notes regarding the Catalog file locations list

If NetBackup Access Control (NBAC) is used in the NetBackup configuration, add the following directives for each host in the NBAC domain: [host:]nbat [host:]nbaz Note: For UNIX master servers, do not include the NetBackup master server configuration file in the offline catalog backup file list. (/usr/openv/netbackup/bp.conf) If bp.conf is included in the list, it must not be recovered until all other catalog recovery is completed.

Make sure that the list does not contain invalid paths. Do so especially if you have moved the catalog files, have deleted old paths, or have added new paths to the catalog backup configuration. If NetBackup cannot find or follow a path, the entire catalog backup fails. On UNIX systems, if /usr/openv/netbackup/db/images is a symbolic link to another file system, you must specify the true location of the images directory here. Symbolic links do not apply to Windows. The entire catalog backup fails if the final component in a UNIX path is a symbolic link. While NetBackup follows links at other points in the path, NetBackup does not follow a link when a link is the final component. If any other part of a listed path is a symbolic link, NetBackup saves the actual path during the backup. The files that are associated with the NetBackup relational databases are automatically included in the catalog backup and dont need to be listed here. (NBDB and BMRDB.) The paths are dynamically generated during the backup since the locations of these files can change.

Absolute pathnames for catalogs on the master server

The catalog paths on the master server are added automatically during installation. Unless you back up the catalogs to a media server, generally no action is required other than to ensure that the directories are listed. The files in the following directory contain NetBackup scheduling information, error logs, and all information about the files that are backed up from client workstations:
/usr/openv/netbackup/db

The files in the following directory contain license key and authentication information:
/usr/openv/var

NetBackup Catalog Catalog protection

315

Absolute paths for catalogs on media servers

If you back up the catalog files that are on media servers, prefix each path with the name of the media server: media_server_name:catalog_backup_path The paths that you must add depend on the version of NetBackup that was installed on the media server.

For UNIX media servers running NetBackup versions earlier than 6.0, add the following two paths:

media_server_name:/usr/openv/netbackup/db/media The files in this directory contain information about the files that were backed up or archived from client workstations. media_server_name:/usr/openv/volmgr/database The files in this directory contain information about the media and devices being used in the configuration.

For UNIX media servers running NetBackup version 5.x, also include the following path: media_server_name:/usr/openv/var

For example, to add the paths for a UNIX NetBackup 5.x media server named elk, create the following entries:
elk:/usr/openv/netbackup/db/media elk:/usr/openv/volmgr/database elk:/usr/openv/var

Media server backups

The critical media and device data on media servers is stored in the NetBackup relational database (NBDB) on the EMM server. The EMM server is generally the master server. No paths should be added for the media servers of the current version to be included in the cold catalog backup.

Paths for Windows NetBackup media servers

To back up the catalog on a Windows NetBackup media server, prefix each path name with the name of the media server: media_server_name:catalog_backup_path For example, to add the catalog files of a Windows NetBackup 5.x media server (mars), create the following entries. Install_path is the directory where NetBackup is installed:
mars:C:Install_path\NetBackup\db mars:C:Install_path\Volmgr\database mars:C:Install_path\NetBackup\var

The files in the db directory contain NetBackup error logs and all information about the files that are backed up from client workstations.

316 NetBackup Catalog Catalog protection

The files in the database directory contain information about the media and the devices that are used in the configuration. Note: Remember to use the backslash (\) in the paths for a Windows NetBackup server.

NetBackup Catalog Recovering the catalog

317

Recovering the catalog

The method to use to recover the catalog in a disaster recovery situation depends on the method that was used to back up the catalog. Catalog recovery from online, hot catalog backups and offline, cold catalog backups are discussed in the NetBackup Troubleshooting Guide.

Disaster recovery emails and the disaster recovery file

The Catalog Backup Wizard asks whether youd like the disaster recovery information to be sent to an email address. (Only in the case of configuring an online, hot catalog backup.) If the online catalog backup is configured using the Policy utility, this information appears on the Disaster Recovery tab. (See Disaster Recovery tab on page 196.) The disaster recovery email and the accompanying attachment that is sent contain important items for a successful catalog recovery:

A list of the media that contains the catalog backup A list of critical policies. Instructions for recovering the catalog The image file included as an attachment. If a catalog backup policy included both full and incremental backups, the attached image file may be a full or an incremental catalog backup. Recovering from an incremental catalog backup completely recovers the entire catalog if Automatically recover the entire NetBackup catalog is selected on the wizard screen. The entire catalog is recovered because the incremental catalog backup references information from the last full backup. You do not need to recover the last full catalog backup before you recover the subsequent incremental backups.

318 NetBackup Catalog Archiving the catalog

Archiving the catalog

The catalog archiving feature helps users tackle the problems that large amounts of catalog data can pose: large catalogs require a greater amount of disk space and can be time-consuming to back up. Catalog archiving reduces the size of online catalog data by relocating the large catalog .f files to secondary storage. NetBackup administration continues to require regularly scheduled catalog backups, but the backups are faster without the large amount of online catalog data. Catalog archiving is available on both UNIX and Windows platforms. Note: When you consider whether to archive the .f files, note that additional time is required to mount the tape and perform the restore.

Catalog archiving process

The following section describes the steps to archive a catalog. Catalog archiving operations must be performed when NetBackup is in an inactive state (no jobs are running). 1 Create a policy named catarc to reflect that the purpose of the schedule is for catalog archiving. (See Creating a catalog archiving policy on page 319.) Run bpcatlist to display images available for archiving. Note: Running bpcatlist alone does not modify any catalog images. Only when the bpcatlist output is piped to bpcatarc and bpcatrm are the images modified and the image .f files removed. To determine what images have been previously archived run: /usr/openv/netbackup/bin/admincmd/bpcatlist -online /usr/openv/netbackup/bin/admincmd/bpcatlist -offline Note: The command returns a message of No entity was found if catalog archiving was not performed previously. 3 Once the bpcatlist output correctly lists all the images to be archived, pipe the output through bpcatarc and bpcatrm. For example: bpcatlist -client all -before Jan 1 2006 | bpcatarc | bpcatrm

NetBackup Catalog Archiving the catalog

319

The command waits until the backup completes successfully before the command returns the prompt. An error is reported if the catalog archive fails. The Activity Monitor displays a Job ID for the job. The File List for the job (double-click the job in the Activity Monitor) displays a list of image files that have been processed. When the job completes with a status 0, bpcatrm removes the corresponding .f files. If the job fails, no catalog .f files are removed. 4 To restore the catalog archive: a b Use bpcatlist to list the files that need to be restored. Once bpcatlist displays the proper files to restore, run bpcatres to restore the actual files. To restore all the archived files from Step 2, run the following command: bpcatlist -client all -before Jan 1 2006 | bpcatres This command restores all the catalog archive files before Jan 1, 2006.

For more information on the archiving commands, see Catalog archiving commands on page 321.

Creating a catalog archiving policy

The catalog archiving feature requires the presence of a policy named catarc before the catalog archiving commands can run properly. The policy can be reused for catalog archiving.

Policy name
Create a new policy that is named catarc. The catarc policy waits until bpcatarc can activate it. Users do not run this policy. Instead, bpcatarc activates this special policy to perform a catalog backup job, then deactivates the policy after the job is done.

Deactivate policy
The catalog archive policy must be deactivated. On the Attributes tab, clear the Active field.

320 NetBackup Catalog Archiving the catalog

Type of backup
The type of backup that is indicated for the catalog archive policy must be User Backup. The backup type is set in the Change Schedule dialog box on the Attributes tab.

Retention level setting

Set the retention level of the catalog archive for a time at least as long as the longest retention period of the backups being archived. Note: Data can be lost if the retention level of the catalog archive is not long enough. The retention level should be at least as long as the longest retention period of the backups being archived. You may find it useful to set up, then designate a special retention level for catalog archive images.

Policy name must be titled: catarc

Policy schedule must be User Backup type Set to a period of at least as long as the longest retention period of backups being archived

Schedule
A schedule is required for catarc. The schedule for catarc must include in its window the time bpcatarc command is run. If bpcatarc is run outside of the schedule that is indicated in catarc, the operation fails.

NetBackup Catalog Archiving the catalog

321

Files
On the Files tab, browse to the directory where catalog backup images are placed: /usr/openv/netbackup/db/images

Clients
On the Clients tab, enter the name of the master server.

Catalog archiving commands

The catalog archiving feature relies on three commands to designate a list of catalog .f files, then archive the files. A fourth command, bpcatres, is used to restore the files if necessary.

Create a catalog list with bpcatlist

The bpcatlist command queries the catalog data. Then, bpcatlist lists the portions of the catalog that are based on selected parameters. For example, date, client, policy, schedule name, backup ID, the age of the backup image, or the date range of the backup image. bpcatlist outputs the formatted image summary information of matched images to standard output. The other catalog archiving commands, bpcatarc, bpcatrm, and bpcatres, all depend on input from bpcatlist by a piped command. For example, to archive (backup and delete) all of the .f files created before January 1, 2006, the following would be entered: # bpcatlist -client all -before Jan 1 2006 | bpcatarc | bpcatrm bpcatlist is also used to provide status information. For each catalog, it lists the following information:

Backup ID (Backupid) Backup date (Backup Date) Catalog archive ID (Catarcid). After an .f file is successfully backed up, a catalog archive ID is entered into the catarcid field in the image file. This field is zero if the image has never been archived. Archived status (S), indicating if the catalog has not been archived (1) or has been archived (2) Compressed status (C), indicating if the catalog is not compressed (0) or compressed (1) Catalog file name (Files file)

The following is an example of the bpcatlist output, showing all of the backups for client alpha since October 23:

322 NetBackup Catalog Archiving the catalog

# bpcatlist -client alpha -since Backupid Backup Date alpha_0972380832 Oct 24 10:47:12 alpha_0972336776 Oct 23 22:32:56 alpha_0972327197 Oct 23 19:53:17

Oct 23 ...Catarcid S 2000 ... 973187218 1 2000 ... 973187218 1 2000 ... 973187218 1 C 0 0 0 Files file alpha_0972380832_UBAK.f alpha_0972336776_FULL.f alpha_0972327197_UBAK.f

For detailed information on bpcatlist, see bpcatlist in NetBackup Commands for UNIX and Linux.

Back up the catalog with bpcatarc

The bpcatarc command reads the output from bpcatlist and backs up the selected list of .f files. After an.f file is successfully backed up, a catalog archive ID is entered into the catarcid field in the image file. For archiving of the.f files to proceed, a policy by the name of catarc is required. The policy is based on a User Backup type schedule. The schedule for catarc must include in its window the time bpcatarc command is run. (See Creating a catalog archiving policy on page 319.)

Remove the catalog with bpcatrm

The bpcatrm command reads the output from bpcatlist or bpcatarc. If the image file has valid catarcid entries, bpcatrm deletes selected image.f files from the online catalog. bpcatrm does not remove an .f file unless the file has been previously backed up using the catarc policy.

Restore the catalog with bpcatres

The bpcatres command reads the output from bpcatlist and restores selected archived.f files to the catalog. For example: # bpcatlist -client all -before Jan 1 2007 | bpcatres

Recommendations for using catalog archiving

Perform catalog archiving operations when NetBackup is in an inactive state (no jobs are running). To ensure that catalog backup images are not on the same tapes as user backups, create a separate media pool for catalog archives. You may find it useful to set up, then designate, a special retention level for catalog archive images. To specify retention levels, go to Host Properties > Master Server > Retention Periods or see Retention Periods properties on page 462.

NetBackup Catalog Archiving the catalog

323

Using Vault with the catalog archiving feature

Since the catalog archiving feature uses a regular User Backup schedule in the catarc policy, the files are duplicated and vaulted similarly to other backups.

Browsing offline catalog archive

If a user tries to browse an offline catalog, the user receives an error message that states that the catalog image.f file has been archived. The catalog archiving feature is for NetBackup administrators only. Use the bplist command to determine if a catalog.f file is archived.

Extracting images from the catalog archives

The situation may arise in which a storage provider needs to extract all of a specific clients records. The storage provider can extract the customer images from the catalog archive by creating separate archives that are based on client name. To extract images from the catalog archives based on a specific client 1 2 3 4 Create a volume pool for the client. Create a catalog archiving policy. Indicate the volume pool for that client in the Attributes tab. Run bpcatlist so only the.f files from that client are listed. For example: bpcatlist -client clientname | bpcatarc | bpcatrm If you do not want to write more images to the clients volume pool, change the volume pool before you run another archiving catalog.

324 NetBackup Catalog Using the Catalog utility

Using the Catalog utility

Use the Catalog utility to create and configure catalog backups. Catalog backups are required for NetBackup to protect NetBackup internal databases. The catalogs contain setup information as well as critical information about client backups. The catalog backups are tracked separately from other backups to ensure recovery in case of a server crash. The Catalog utility is also used to perform other operations on catalog information. For example:

Search for backup images to verify the contents of media with what is recorded in the NetBackup catalog. Duplicate a backup image. Promote a backup image from a copy to the primary backup copy. Expire backup images. Import expired backup images or images from another NetBackup server.

Current master server Possible actions to perform Set search criteria, including specific media and date range

Right-click Catalog to display menu

Search results

Messages pane

Searching for backup images

Use the Catalog utility to search for a backup image. You may want to search for a backup image to perform the following actions:

Verify the backup contents with what is recorded in the NetBackup catalog.

NetBackup Catalog Using the Catalog utility

325

Duplicate the backup image to create up to 10 copies. Promote a copy of a backup to be the primary backup copy. Expire backup images. Import expired backup images or images from another NetBackup server.

NetBackup uses the specific search criteria to build a list of backups from which you can make your selections.

Specify Verify, Duplicate, or Import, depending on what you want to do

Search for backup images using the criteria that is described in the following table: Table 6-1 Search criteria
Action

Search criteria for backup images Description

Select the action that was used to create the image: Verify, Duplicate, Import.

Media ID

The media ID for the volume. Type a media ID in the box or select one from the scroll-down list. To search on all media, select <All>. The host name of the media server that produced the originals. Type a host name in the box or select one from the scroll-down list. To search through all hosts, select All Media Hosts.

Media Host

Disk type

The type of the disk storage unit on which to search for backup images.

326 NetBackup Catalog Using the Catalog utility

Table 6-1 Search criteria

Disk pool Volume ID NearStore Server

Search criteria for backup images (continued) Description

The name of the disk pool on which to search for backup images. The ID of the disk volume in the disk pool on which to search for backup images. The name of the NearStore server to search for images. Type a server name in the box or select one from the scroll-down list. To search through all NearStore servers, select All NearStore Servers. To search for an image on a disk storage unit, enter the path to search or select All to search all of the disk storage on the specified server. Appears if the disk type is BasicDisk or NearStore. The range of dates and times that includes all the backups for which you want to search. The Global Attributes property Policy Update Interval determines the default range. (See Global Attributes properties on page 435.) The source you want to search. From the scroll-down list, select either Primary or the copy number. The policy under which the selected backups were performed. Type a policy name in the box or select one from the scroll-down list. To search through all policies, select All Policies.

Path

Date/time range

Copies

Policy Name

Client (host name) The host name of the client that produced the originals. Type a client name in the box or select one from the scroll-down list. To search through all hosts, select All Clients. Type of backup The type of schedule that created the backup. Type a schedule type in the box or select one from the scroll-down list. To search through all schedule types, select All Backup Types.

Notes on searching for an image

When you search for specific kinds of images, note the following:

Verification image: Backups that have fragments on another volume are included, as they exist in part on the specified volume. Import image: If a backup begins on a media ID that was not processed by the first step of To initiate an import phase I on page 336, the backup is not imported. If a backup ends on a media ID that was not processed by the first step of To initiate an import phase I on page 336, the imported backup is incomplete.

Messages pane
The Messages pane displays messages about a task running as a background process. The pane is displayed only if there in an informative message or error

NetBackup Catalog Using the Catalog utility

327

message for the task. If the task completes normally, the pane is not displayed. The Messages pane can be maximized, minimized, or closed.

Verifying backup images

NetBackup can verify the contents of a backup by reading the volume and comparing its contents to what is recorded in the NetBackup catalog. This operation does not compare the data on the volume to the contents of the client disk. However, the operation does read each block in the image to verify that the volume is readable. (However, data corruption within a block could be possible.) NetBackup verifies only one backup at a time and tries to minimize media mounts and positioning time. To verify backup images 1 2 3 In the NetBackup Administration Console, expand NetBackup Management > Catalog. Set up the search criteria for the image you want to verify. Click Search Now. Select the image you want to verify and select Actions > Verify. The Confirm Verify dialog box may appear. To display information on each file that NetBackup verifies, select Log all files found in verified image(s). Click the Results tab, then select the verification job to view the job results.

Viewing job results

The results of verify, duplicate, or import jobs appear in the Results tab. The top portion of the dialog box displays all existing log files. To view a log file, select the name of the log from the list. The log file currently displayed appears in the bottom portion of the Results dialog box. If an operation is in progress, the log file display is refreshed as the operation proceeds. To view or delete a log file 1 2 3 4 In the NetBackup Administration Console, expand NetBackup Management > Catalog. Click the Results tab. Select a log file. Select View > Full View to display the entire log file in a screen editor. Select Edit > Delete to delete the log.

328 NetBackup Catalog Using the Catalog utility

You can also right-click the log file and select an action from the scroll-down menu.

Promoting a copy to a primary copy

Each backup is assigned a primary copy. NetBackup uses the primary copy to satisfy restore requests. The first backup image that is created successfully by a NetBackup policy is the primary backup. If the primary copy is unavailable and a duplicate copy exists, select a copy of the backup and set it to be the primary copy. NetBackup restores from the primary backup, and Vault duplicates from the primary backup. If your Vault profile performs duplication, you can designate one of the duplicates as the primary. In most circumstances, the copy remaining in the robot is the primary backup. When a primary backup expires, the next backup (if it exists) is promoted to primary automatically. To promote a backup copy to a primary copy 1 2 In the NetBackup Administration Console, expand NetBackup Management > Catalog. Set up the search criteria for the image you want to promote to a primary copy. Be sure that youve indicated a copy in the Copies field and not Primary Copy. Click Search Now. (See Searching for backup images on page 324.) Select the image you want to promote. Click Actions > Set Primary Copy. After the image is promoted to the primary copy, the Primary Status column immediately reads Yes.

3 4

To promote a copy to a primary copy for many backups You can also promote a copy to be a primary copy for many backups using the bpchangeprimary command. For example, the following command promotes all copies on media belonging to the volume pool, SUN, created after August 8, 2007, to be the primary copy: bpchangeprimary -pool SUN -sd 08/01/2007 The following command promotes copy 2 of all backups of client_a, created after January 1, 2007, to be the primary copy: bpchangeprimary -copy 2 -cl client_a -sd 01/01/2007

NetBackup Catalog Using the Catalog utility

329

For more information on bpchangeprimary, see NetBackup Commands for UNIX and Linux.

Primary Copy status indicates that the image is now the primary copy

To promote a backup copy to a primary copy using bpduplicate 1 Enter the following command:
/usr/openv/netbackup/bin/admincmd/bpduplicate -npc pcopy -backupid bid

Where: pcopy is the copy number of the new primary copy. bid is the backup identifier as shown in the Images on Media report. To find the volume that contains the duplicate backup, use the Images on Media report. Specify the backup ID that is known (and also the client name if possible to reduce the search time). The report shows information about both copies. (See Images on Media report on page 76.) The bpduplicate command writes all output to the NetBackup logs so nothing appears in the command window. After the duplicate copy is promoted to the primary copy, use the client interface on the client to restore files from the backup. For instructions, see the online help in the Backup, Archive, and Restore client interface.

330 NetBackup Catalog Using the Catalog utility

Duplicating backup images

NetBackup can create up to 10 copies of unexpired backups. Indicate the number of backup copies in Host Properties > Master Servers > Global Attributes > Maximum backup copies. (See Global Attributes properties on page 435.) Note: An alternative to taking time to duplicate backups is to create up to four copies simultaneously at backup time. (This option is sometimes referred to as Inline Copy.) (See Multiple copies on page 131.) NetBackup does not verify in advance whether the storage units and the drives that are required for the duplicate operation are available for use. NetBackup verifies that the destination storage units exist. The storage units must be connected to the same media server. The following lists describe the scenarios that present candidates for duplication and scenarios in which duplication is not possible: Table 6-2 Backup duplication scenarios Not possible to duplicate backups:

Possible to duplicate backups:

from one storage unit to another. from one media density to another. from one server to another. from multiplex to nonmultiplex format.

while the backup is created (unless making multiple copies concurrently). when the backup has expired. by using NetBackup to schedule duplications automatically (unless you use a Vault policy to schedule duplication) of offline NetBackup catalogs. when it is a multiplexed duplicate of the following: FlashBackup NDMP backup Backups from disk type storage units Backups to disk type storage units Nonmultiplexed backups

from multiplex format and retain the multiplex format on the duplicate. The duplicate can contain all or any subset of the backups that were included in the original multiplexed group. The duplicate is created with a single pass of the tape. (A multiplexed group is a set of backups that were multiplexed together during a single session.)

Note: Do not duplicate images while an offline, cold catalog backup is running. This results in the catalog backup not having information about the duplication.

Notes on multiplexed duplication

When multiplexed backups are duplicated, the multiplex settings of the destination storage unit and the original schedule are ignored. However, if multiple multiplexed groups are duplicated, the grouping within each

NetBackup Catalog Using the Catalog utility

331

multiplexed group is maintained. This means that the duplicated groups have a multiplexing factor that is no greater than the factor that was used during the original backup.

When backups in a multiplexed group are duplicated to a storage unit, the duplicated group is identical as well. However, the storage unit must have the same characteristics as the unit where the backup was originally performed. The following items are exceptions:

If EOM (end of media) is encountered on either the source or the destination media. If any of the fragments are zero length in the source backups, the fragments are removed during duplication. A fragment of zero length occurs if many multiplexed backups start at the same time.

Procedure for duplicating backups

NetBackup can create up to 10 copies of unexpired backups. To duplicate backup images 1 2 3 In the NetBackup Administration Console, expand NetBackup Management > Catalog. Set up the search criteria for the image you want to duplicate. Click Search Now. Right-click the image(s) you want to duplicate and select Duplicate from the shortcut menu. The Setup Duplication Variables dialog box appears. Note: If you duplicate an online, hot catalog backup, select all child jobs that were used to create the catalog backup. All jobs must be duplicated to duplicate the catalog backup.

332 NetBackup Catalog Using the Catalog utility

Specify the number of copies you would like created. If there are enough drives available, the copies are created simultaneously. Otherwise, the system may require operator intervention if four copies are to be created using only two drives, for example. The primary copy is the copy from which restores are done. Normally, the original backup is the primary copy. If you want one of the duplicated copies to become the primary copy, check the appropriate check box, otherwise leave the fields blank. When the primary expires, a different copy automatically becomes primary. (The copy that is chosen is the one with the smallest copy number. If the primary is copy 1, copy 2 becomes primary when it expires. If the primary is copy 5, copy 1 becomes primary when it expires.) Specify the storage unit where each copy is stored. If a storage unit has multiple drives, it can be used for both the source and destination.

NetBackup Catalog Using the Catalog utility

333

Note: The ability to make multiple copies concurrently (sometimes referred to as Inline Copy) is not supported on the following storage types: NDMP, third-party copies, or optical devices. This ability is not supported on any storage units that use a QIC (quarter-inch cartridge) drive type. 7 Specify the volume pool where each copy is stored. The volume pool selections are based on the policy type setting that was used for the query:

If the policy type was set to query for All Policy Types (default), all volume pools are included in the drop-down list. Both catalog and non-catalog volume pools are included. If the policy type was set to query for NBU-Catalog, only catalog volume pools are included in the drop-down list.

If the policy type was set to query for a policy type other than NBU-Catalog or All Policy Types, only non-catalog volume pools are included in the drop-down list. NetBackup does not verify that the media ID selected for the duplicate copy is not the same as the media ID of the volume that contains the original backup. Because of this potential deadlock, specify a different volume pool to ensure a different volume is used.

Select the retention level for the copy, or select No change. The duplicate copy shares many attributes of the primary copy, including backup ID. Other attributes apply only to the primary. (For example, elapsed time.) NetBackup uses the primary copy to satisfy restore requests.

If No Change is selected for the retention period, the expiration date is the same for the duplicate and the source copies. You can use the bpexpdate command to change the expiration date of the duplicate. If a retention period is indicated, the expiration date for the copy is the backup date plus the retention period. For example, if a backup was created on November 14, 2007 and its retention period is one week, the new copys expiration date is November 21, 2007.

Specify whether the remaining copies should continue or fail if the specified copy fails. Any lets NetBackup choose the media owner, either a media server or server group. None specifies that the media server that writes to the media owns the media. No media server is specified explicitly, but you want a media server to own the media.

10 Specify who should own the media onto which you are duplicating images:

334 NetBackup Catalog Using the Catalog utility

A server group. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written. All media server groups configured in your NetBackup environment appear in the drop-down list.

11 If the selection includes multiplexed backups and the backups are to remain multiplexed in the duplicate, check Preserve Multiplexing. If you do not duplicate all the backups in a multiplexed group, the duplicate contains a different layout of fragments. (A multiplexed group is a set of backups that were multiplexed together during a single session.) By default, duplication is done serially and attempts to minimize media mounts and postitioning time. Only one backup is processed at a time. If Preserved Multiplexing is enabled, NetBackup first duplicates all backups that cannot be multiplex duplicated before the multiplexed backups are duplicated. The Preserve Multiplexing setting does not apply when the destination is a disk storage unit. However, if the source is a tape and the destination is a disk storage unit, selecting Preserve Multiplexing ensures that the tape is read in one pass. 12 Click OK to start duplicating. 13 Click the Results tab, then select the duplication job to view the job results. (See Viewing job results on page 327.)

Jobs displayed while making multiple copies

When multiple copies are made concurrently, a parent job is displayed, plus a job for each copy. The parent job displays the overall status, whereas the copy jobs display the status of a single copy. Viewing the status of individual jobs allows you to troubleshoot jobs individually. For example, if one copy fails but the other copy is successful, or if each copy fails for different reasons. If at least one copy is successful, the status of the parent job is successful. Use the Parent Job ID filter to display the parent Job ID. Use the Copy filter to display the copy number for a particular copy. The following example shows a backup that contains two copies. The parent job is 19, copy 1 is job 20, and copy 2 is job 21. Copy 1 finished successfully, but copy 2 failed with a 800 status (disk volume cannot be used for more than one copy in

NetBackup Catalog Using the Catalog utility

335

the same job). Since at least one copy successfully completed, the parent job displays a successful (0) status.

Copy 1 was successful, but Copy 2 failed

The parent job was successful because at least one copy was successful

336 NetBackup Catalog Using the Catalog utility

Importing NetBackup or Backup Exec images

NetBackup can import backups that have expired, backups from another NetBackup server, or backups written by Backup Exec for Windows. (Supports Backup Exec versions 7.0 through 9.1.) During an import operation, NetBackup recreates NetBackup catalog entries for the backups on the imported volume. The import capability is useful for moving volumes from one site to another and for recreating NetBackup catalog entries. NetBackup supports the capability to import and restore the following Backup Exec backup types. Please refer to the specific NetBackup manuals for details on the support for each backup type.

Windows UNIX NetWare Exchange SQL

NetBackup does not support reading Backup Exec media that written by Backup Exec for NetWare. An image is imported in two phases. (A Backup Exec media import requires one additional step): Note: To import Backup Exec media, run the vmphyinv physical inventory utility to update the Backup Exec media GUID in the NetBackup Media Manager database. The command needs to be run only once after creating the media IDs in the NetBackup Media Manager database. For information about using vmphyinv, See Using the physical inventory utility on page 572.

Phase I: NetBackup creates a list of expired catalog entries for the backups on the imported volume. No actual import occurs in Phase I. Phase II: Images are selected for importing from the list of expired images that was created in Phase I. For information about using vmphyinv, See Using the physical inventory utility on page 572.

To initiate an import phase I Phase I of the import process creates a list of expired images from which to select to import in Phase II. No import occurs in Phase I.

NetBackup Catalog Using the Catalog utility

337

To import Backup Exec media, run the vmphyinv physical inventory utility to update the Backup Exec media GUID in the NetBackup Media Manager database. The command needs to be run only once after creating the media IDs in the NetBackup Media Manager database. For information about using vmphyinv, See Using the physical inventory utility on page 572. To import the images from tape, make the media accessible to the media server so the images can be imported. In the NetBackup Administration Console, expand NetBackup Management > Catalog. Select Actions > Initiate Import. The Initialize Import dialog box appears.

2 3 4

The Master Server field indicates the master server where the images are imported. In the Media Server field, specify the name of the host that contains the volume to import. This media server becomes the media owner. Indicate the location of the image. Under Image type, select whether the images to be imported are located on tape or on disk. If images are on tape:

In the Media ID field, type the Media ID of the volume that contains the backups to import. Check whether or not the images to import are password-protected Backup Exec images.

338 NetBackup Catalog Using the Catalog utility

If images are on disk:

In the Disk type field, select the type of the disk storage unit on which to search for backup images. The disk types depend on which NetBackup options are licensed. If the disk type references a disk pool, enter or select the disk pool and the disk volume ID. For a BasicDisk type, enter the path to the images in the field provided. For a NearStore disk type, select or enter the name of the NearStore server and the NearStore volume.

Notes:

If Backup Exec media is password-protected, the job fails without a correct password. The logs indicate that either no password or an incorrect password, was provided. If the media is not password-protected and the user provides a password, the password is ignored. To import Backup Exec media if the password contains non-ASCII characters:

Use the NetBackup Administration Console on Windows. (The NetBackup-Java Administration Console cannot be used.) Use the bpimport command.

To import an online, hot catalog backup, import all of the child jobs that were used to create the catalog backup.

NetBackup Catalog Using the Catalog utility

339

Click OK. The Confirm Initiate Import dialog box appears.

5 6

Click OK to begin reading the catalog information from the source volume. Click on the Catalog Results tab to see NetBackup look at each image on the tape. NetBackup determines whether or not each image has expired and can be imported. The job also displays in Activity Monitor as an Import type. Select the import job log to view the job results.

Note: In this phase, each tape must be mounted and read. It may take some time to read the catalog and build the list of images. To import backup images phase II 1 In the NetBackup Administration Console, expand NetBackup Management > Catalog.

Note: If you import any backups that consist of fragments on multiple tapes, run the Initiate Import (Import Phase I) first. Phase I reads the catalog to determine all the tapes that contain fragments. After Phase I, start the Import (Phase II). If Phase II is run before Phase I, the import fails with a message. For example, Unexpected EOF or Import of backup id failed, fragments are not consecutive.

340 NetBackup Catalog Using the Catalog utility

Set up the search criteria to find images available to import by setting the search action to Import. Be sure to select a date range that includes the images you want to import.

Select Import to search for imported images

Select the date range that includes the images to import

Images eligible for importing appear as a result

Select the image(s) you want to import and select Actions > Import. The Confirm Import dialog box appears.

NetBackup Catalog Using the Catalog utility

341

To view the log, click the Results tab, then select the import job log.

Importing expired images

The expiration date for the imported items is the current date plus the retention period. For example, if a backup is imported on November 14, 2007 and its retention period is one week, the new expiration date is November 21, 2007.

Notes about importing backup images

NetBackup can import any disk images that were written by NetBackup 6.0 or later. You cannot import a backup if an unexpired copy of it already exists on the server. NetBackup does not direct backups to imported volumes. If you import an online, hot catalog backup, import all the child jobs that were used to create the catalog backup. All jobs must be imported to import the catalog backup. To import a volume with the same media ID as an existing volume on a server, use the following example. In the example, we want to import a volume with media ID A00001. A volume with media ID A00001 already exists on the server. a b Duplicate the existing volume on the server to another media ID (for example, B00001). Remove information about media ID A00001 from the NetBackup catalog by running the following command:

342 NetBackup Catalog Using the Catalog utility

/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m media_ID

Delete media ID A00001 from Media Manager on the server.

d Add the other A00001 to Media Manager on the server. To avoid this problem in the future, use unique prefix characters for media IDs on all servers.

Importing images from Backup Exec media

Clients must be at NetBackup 5.0 or later to restore the Backup Exec images. Backup Exec images cannot be restored to clients on any platforms that were not supported by NetBackup versions before 5.0.

Host properties for Backup Exec

The Backup Exec UNIX agent identifies itself to the Backup Exec server using a GRFS-advertised name. The advertised name may not have been the same as the real machine name and path. NetBackup must know what the advertised name is, along with the actual client name and path to create accurate.f file paths. Set the GRFS Advertised Name, Actual Client, and Actual Path properties in the Backup Exec Tape Reader host properties. If no entries are indicated, NetBackup assumes that the advertised name is the real machine name and the advertised path is the real path. For more information, see Backup Exec Tape Reader properties on page 375.

Considerations concerning importing Backup Exec media

The following items should be taken into consideration when importing Backup Exec media:

UNIX data cannot be restored to Windows systems; Windows data to UNIX systems; Windows data to NetWare systems; or UNIX data to NetWare systems. Importing from Backup Exec media does not convert or migrate Backup Exec job history, job schedules, or job descriptions to NetBackup. Importing from Backup Exec media does not convert Backup Exec application setup or configuration information to NetBackup. Intelligent Disaster Recovery (IDR) operations using the NetBackup IDR wizard and Backup Exec media is not supported. The operations include both local and remote IDR restores. Any Backup Exec backups that were created with the Intelligent Image Option cannot be restored.

NetBackup Catalog Using the Catalog utility

343

If Backup Exec hardlink backups are redirected and restored to partitions or drives other than the source partition or drive, the hardlinks are not restored. The progress log may indicate that the hardlinks are restored successfully, but that is not the case.

Differences between importing, browsing, and restoring Backup Exec and NetBackup images
The following sections describe differences between Backup Exec and NetBackup when importing, browsing, and restoring images:

Running vmphyinv
To import Backup Exec media requires vmphyinv to update the Backup Exec media GUID in the NetBackup Media Manager database. Create the media IDs in the NetBackup Media Manager database, run the command, then perform Phase I and Phase II import operations. For information about using vmphyinv, See Using the physical inventory utility on page 572.

Importing and restoring QIC media

Backup Exec Quarter Inch Cartridge (QIC) media that was written in tape block sizes more than 512 bytes, must be imported and restored using a NetBackup Windows media server. A NetBackup UNIX media server cannot import and restore the media in this case.

Spanned media: Importing differences

To import a Backup Exec backup that spans multiple media, run a Phase I import on the first media of the spanned backup set. Then, run a Phase I import on the remaining media of the spanned backup set in any order. The Backup Exec import process differs from the NetBackup import process. In that NetBackup import process, Phase I can be run in any order in case the image spans multiple media.

SQL: Browsing and restoring differences

Backup Exec SQL images are browsed, then restored using the NetBackup Backup, Archive, and Restore client interface. NetBackup SQL images are browsed, then restored using the NetBackup SQL interface.

File level objects: Browsing and restoring differences

When a user selects a Backup Exec file to restore, the directory where that file is located is restored.

344 NetBackup Catalog Using the Catalog utility

When a user selects a NetBackup file to restore, only the single file is restored.

NetWare: Restoring differences

NetBackup does not support restoring Backup Exec NetWare non-SMS backups that were created using the NetWare redirector. Storage Management Services (SMS) software allows data to be stored and retrieved on NetWare servers independent of the file system the data is maintained in.

NTFS hard links, NTFS SIS files, and Exchange SIS mail messages: restoring

When Backup Exec NTFS images are restored, any directory named SIS Common Store is restored. The directory named SIS Common Store is restored whether or not it is the actual NTFS single instance storage common store directory. The directory is restored even if the file was not specifically selected for restore. Under some circumstances, additional objects are sent to the client, even though the objects were not selected for restore. The items are sent to the client when restoring objects from any backups that contain NTFS hardlinks, NTFS SIS files, or Exchange SIS mail messages. These additional objects are skipped by the client and are not restored. The job is considered partially successful because some objects (though not selected by the user), are skipped. When NTFS hard links, NTFS SIS files, or Exchange SIS mailboxes are redirected for restore:

All or some of the files should be redirected to any location on the source drive, Or: All files should be redirected to a single location on a different drive. For example, if the following hard link or SIS files are backed up: C:\hard_links\one.txt C:\hard_links\two.txt C:\hard_links\three.txt Upon restore, either the files can be redirected to any location on C:\, or all the files must be redirected to a different drive. The following combination would be unsuccessful: C:\hard_links\one.txt to a location on C:\ C:\hard_links\two.txt to a location on D:\ If all the files are to be redirected to a different drive, specify that C:\ be replaced with D:\in the redirection paths.

NetBackup Catalog Using the Catalog utility

345

Unsuccessful: The redirection paths specify that C:\hard_links be replaced with D:\hard_links. Successful: The redirection paths specify that C:\hard_links be replaced with C:\redir_hard_links.

346 NetBackup Catalog Using the Catalog utility

Expiring backup images

To expire a backup image means to force the retention period to expire. When the retention period expires, NetBackup deletes information about the backup. The files in the backups are unavailable for restores without first re-importing. To expire a backup image 1 2 In the NetBackup Administration Console, expand NetBackup Management > Catalog. Set up the search criteria for the image you want to expire, as explained in the table, Search criteria for backup images on page 325. Click Search Now. Select the image you want to expire and select Actions > Expire. A message appears that announces that once the backups are expired, they cannot be used for restores. Select Yes to begin to expire the images.

3 4

NetBackup Catalog Catalog maintenance and performance optimization

347

Catalog maintenance and performance optimization

Determining catalog space requirements
NetBackup requires disk space to store its error logs and information about the files it backs up. The disk space that NetBackup needs varies according to the following factors:

Number of files to be backed up Frequency of full and incremental backups Number of user backups and archives Retention period of backups Average length of full path of files File information (such as owner permissions) Average amount of error log information existing at any given time Whether you have enabled the database compression option.

To estimate the disk space that is required for a catalog backup 1 Estimate the maximum number of files that each schedule for each policy backs up during a single backup of all its clients. Example reference table for catalog requirements shows that a full backup for policy S1 includes 64,000 files. Determine the frequency and the retention period of the full and the incremental backups for each policy. Use the information from steps 1 and 2 to calculate the maximum number of files that exist at any given time. For example: Assume that you schedule full backups to occur every seven days. The full backups have a retention period of four weeks. Differential incremental backups are scheduled to run daily and have a retention period of one week. The number of file paths you must allow space for is four times the number of files in a full backup. Add to that number one weeks worth of incrementals. The following formula expresses the maximum number of files that can exist for each type of backup (daily or weekly, for example): Files per Backup x Backups per Retention Period = Max Files For example:

2 3

348 NetBackup Catalog Catalog maintenance and performance optimization

A daily differential incremental schedule backs up 1200 files and the retention period for the backup is seven days. Given this information, the maximum number of files that can exist at one time are the following: 1200 x 7 days = 8400 A weekly full backup schedule backs up 3000 files and the retention period is four weeks. The maximum number of files that can exist at one time are the following: 3000 x 4 weeks = 12,000 Obtain the total for a server by adding the maximum files for all the schedules together. Add the separate totals to get the maximum number of files that can exist at one time. For example, 20,400. Note: For the policies that collect true image restore information, an incremental backup collects catalog information on all files (as if it were a full backup). This changes the calculation in the example: the incremental changes from 1200 x 7 = 8400 to 3000 x 7 = 21,000. After 12,000 is added for the full backups, the total for the two schedules is 33,000 rather than 20,400. 4 Obtain the number of bytes by multiplying the number of files by the average length of the files full paths and file information. If you are unsure of the average length of a files full path, use 100. Using the results from the examples in step 3 yields: (8400 x 150) + (12,000 x 150) =3060000 bytes (or about 2988 kilobytes) Add between 10 megabytes to 15 megabytes to the total sum that was calculated in step 4. The additional megabytes account for the average space that is required for the error logs. Increase the value if you anticipate problems. Allocate space so all the data remains in a single partition.

File size considerations

Some UNIX systems have a large file support flag. Turn ON the flag to enable large file support. For example, AIX disables large file support by default, so the file size limit is 2GB. For UNIX systems, set the file size limit for the root user account to unlimited to support large file support.

Example: Estimating required catalog backup space

Table 6-3 on page 349 shows backup schedules, retention times, and number of files for a group of example policies. Calculate the maximum number of files

NetBackup Catalog Catalog maintenance and performance optimization

349

that each policy can generate by using the information in Table 6-3. Substitute the information into the following formula: Files per Backup x Backups per Retention Period = Max Files The following steps demonstrate the equation for policy S1: 1 Apply the following formula to policy S1: Max Files equals:
(Files per Incremental x Backups per Retention Period) + (Files per Monthly Full Backups x Backups per Retention Period)

Substitute values from the following table: 1000 files x 30 + 64,000 files x 12 = 798,000 files Perform steps 1 and 2 for each policy. Add the results to show that the total number of files for all policies is: 4,829,600 files Multiply the total number of files by the bytes in the average path length and statistics (100 for this example). The total amount of disk space that is required for file paths is: 460.59 megabytes (1,048,576 bytes in a megabyte) Add 15 megabytes for error logs to result in a final uncompressed catalog space requirement of: 475.59 megabytes

Table 6-3 Policy

S1

Example reference table for catalog requirements Schedule

Daily Monthly

Backup type
Incremental Full Incremental Full Incremental Full Full

Retention
1 month 1 year 1 month 1 year 1 week 1 month 1 year

Number of files
1000 64,000 1000 70,000 10,000 114,000 114,000

S2

Daily Monthly

S3

Daily Weekly Monthly

350 NetBackup Catalog Catalog maintenance and performance optimization

Table 6-3 Policy

S4

Example reference table for catalog requirements (continued) Schedule

Daily Weekly Monthly Quarterly

Backup type
Incremental Full Full Full Incremental Full Incremental Full Full

Retention
1 week 1 month 3 months Infinite 1 month 1 year 1 week 1 month 1 year

Number of files
200 2000 2000 2000 200 5600 7000 70,000 70,000

WS1

Daily Monthly

WS2

Daily Weekly Monthly

Backing up catalogs manually

Catalog backups typically run automatically because they are configured to do so using one of the catalog backup methods (online, hot or offline, cold). However, a catalog backup can be started manually. A manual catalog backup is useful in the following situations:

To perform an emergency backup. For example, if the system is schedule to be moved and you cannot wait for the next scheduled catalog backup. If there is only one stand-alone drive and the stand-alone drive is used for catalog backups. In this situation, automatic backups are not convenient. The catalog backup tape must be inserted before each catalog backup and removed when the backup is done. (The tape swap is necessary because NetBackup does not mix catalog and regular backups on the same tape.)

For directions on how to start each catalog method, see To perform a manual online, hot catalog backup and To perform a manual offline, cold catalog backup on page 351. To perform a manual online, hot catalog backup 1 2 3 In the NetBackup Administration Console, expand NetBackup Management > Policies. Select the catalog backup policy you want to run. Select Actions > Manual Backup. For more information, see Performing manual backups on page 200.

NetBackup Catalog Catalog maintenance and performance optimization

351

Note: You can also run the bpbackup command from the command line to perform an online, hot catalog backup. See NetBackup Commands for UNIX and Linux for more information on bpbackup. To perform a manual offline, cold catalog backup 1 2 In the NetBackup Administration Console, expand NetBackup Management > Catalog. Select Actions > Perform offline backup of the NetBackup catalogBackup NetBackup Catalog to start the backup. The Backup NetBackup Catalog dialog box appears. The backup is saved to the least recently used of Media 1 and Media 2.

Select the master server for which you want to create a catalog backup and click OK.

Note: If the volume for the catalog backup is not in a drive, a mount request occurs. All catalog backups must wait for the mount before they can proceed. For a scheduled catalog backup, all other backups must wait until the catalog backup is complete.

Note: You can also run the bpbackupdb command from the command line to perform an offline, cold catalog backup. See NetBackup Commands for UNIX and Linux for more information on bpbackup.

How do I know if a catalog backup succeeded?

The All Log Entries, Problems, and Media Log reports, available from the Reports utility, provide information on NetBackup catalog backups. In addition, you can use:

352 NetBackup Catalog Catalog maintenance and performance optimization

Email: An email message is sent to the address indicated in the Disaster Recovery settings for an online catalog backup. This email can be configured with the mail_dr_info script. For more information, see Disaster recovery emails and the disaster recovery file on page 317. The dbbackup_notify script can be used to send an email for offline catalog backups. See the NetBackup Administrators Guide, Volume II for more information on setting up this script.

Strategies to ensure successful catalog backups

Use only the methods that are described in this chapter to back up the catalogs. The methods that are described here are the only operations that can track all relevant NetBackup activities and ensure consistency between the catalog files. Back up the catalogs often. If catalog backup files are lost, the changes that were made between the last catalog backup and the time of the disk crash are lost. Never manually compress the catalogs or NetBackup may be unable to restore the catalogs using bprecover. If you back up your catalogs to disk (not recommended), always back up to a different disk than where the catalog files reside. If you back up the catalog to the disk where the actual catalog resides, both catalog backups are lost if the backup disk fails. Recovering the catalog is much more difficult. Also, ensure that the disk has enough space for the catalogs. Backups to a full disk fail. The NetBackup binary image catalog is more sensitive to the location of the catalog. Catalog backups that are stored on a remote file system may have critical performance issues. NetBackup does not support saving catalogs to a remote file system such as NFS or CIFS. If you use media servers, alter the NetBackup catalog configuration manually to include the catalogs on the media servers. You must manually track the media that is used for catalog backups. NetBackup does not keep a record of catalog backup media in its catalogs as it does with other backup media. A convenient way to track the media is to indicate an email address in the Global Attributes properties. NetBackup sends an email that includes the status of each catalog backup and the media ID that was used. Print the

Considerations to run offline, cold catalog backups:

NetBackup Catalog Catalog maintenance and performance optimization

353

email or save it on a disk other than the disk that contains the catalogs. For more information, see Global Attributes properties on page 435.

If you send catalog backups to a robot, a tape stacker, a second stand-alone tape drive, or to disk, choose either of the two automatic backups: After each session of scheduled, user, or manual backups or After each session of scheduled backups If you use a single, stand-alone tape drive to back up both catalog and regular business data, choose either:

After each session of scheduled backups if you run only one backup session per day or night, or

Only when manually initiated if you run multiple backup sessions in a single day or night. Because NetBackup does not place catalog and regular backups on the same tape, both methods require you to swap tapes. Use the following general procedure for creating catalog backups if you have only one stand-alone drive:

a b c

Insert the tape that is configured for catalog backups. Manually start the backup. For more information, see Backing up catalogs manually on page 350. When the backup is complete, remove the tape and store it in a safe place.

Caution: The catalog backup tape must be removed when the backup is finished or regular backups cannot proceed. NetBackup does not mix catalog and regular backups on the same tape.

About the binary catalog format

The catalog in a binary file format has several advantages over the catalog in a text format:

The catalog is more compact. The binary representations of numbers, dates, and other information, takes up less disk space than the text representations. The catalog is much faster to browse and search, especially for large file sizes. The catalog supports alternate backup methods without requiring post-processing, which improves catalog performance for alternate backup methods.

354 NetBackup Catalog Catalog maintenance and performance optimization

Catalog conversion utility

NetBackup offers a catalog format conversion utility that the cat_convert command launches. This utility converts ASCII image.f files in the image database of NetBackup versions 3.4, 4.0V or 4.5, to the binary format. Upon installation, NetBackup does not convert existing ASCII catalogs to the binary catalog format. However, any new catalogs that are created in binary. The cat_convert command is described in NetBackup Commands for UNIX and Linux.

Binary catalog file limitations

The following points describe size the limitations that are associated with the binary catalog:

The maximum number of files that can be backed up per image: (231) 1 files = 2,147,483,647 files = 7FFFFFFF files The maximum number of different user IDs and group IDs (combined): (231) 1 IDs = 2,147,483,647 IDs = 7FFFFFFF IDs

Moving the image catalog

An image catalog may become too large for its current location. Consider moving the image catalog to a file system or disk partition that contains more available space. Note: NetBackup does not support saving the catalog to a remote file system. Therefore, Symantec advises against moving the image catalog to a remote file system such as NFS or CIFS. To move the image catalog 1 2 3 4 5 Check that no backups are in progress by running: /usr/openv/netbackup/bin/bpps Stop bprd by running: /usr/openv/netbackup/bin/admincmd/bprdreq -terminate Stop bpdbm by running: /usr/openv/netbackup/bin/bpdbm -terminate Create the directory in the new file system. For example: mkdir /disk3/netbackup/db/images Move the image catalog to the new location in the other file system.

NetBackup Catalog Catalog maintenance and performance optimization

355

6 7

Create a symbolic link from /usr/openv/netbackup/db/images to the new location in the other file system. Add the new image-catalog path to the list that is included in NetBackup catalog backups.

Caution: Be certain to add the path for the image catalog and not the link name. Without the path, NetBackup cannot back up the new location. In this example, the path is /disk3/netbackup/db/images.

Indexing the catalog for faster access to backups

If the NetBackup environment contains a large number of backups, consider indexing the catalogs to reduce the time that is required to restore files. To index the catalog means to create indexes of the files that are recorded in the NetBackup image catalog. NetBackup uses the indexes to go directly to the catalog entry for a file. Without indexing, NetBackup must start searching for a file at the beginning of the catalog entries. To index image header files, run the following command: bpimage -create_image_list [-client name] Run this command to create the following index files in each client image directory: IMAGE_FILES IMAGE_INFO IMAGE_LIST To stop image header indexing for a client, remove these files.

Compressing and uncompressing the image catalog

The image catalog has information about all client backups and is accessed when a user lists or restores files. NetBackup allows you to compress all portions

356 NetBackup Catalog Catalog maintenance and performance optimization

of the catalog or only older portions of the catalog. No method selectively compresses image-catalog files other than by age.

Control image-catalog compression by setting the Global Attributes property, Compress Catalog Interval. Use this property to specify how old the backup information must be before it is compressed. Specify the number of days to defer compression information, thus users who restore files from recent backups are unaffected. By default, Compress Catalog Interval is set to 0 and image compression is not enabled. For more information, see Global Attributes properties on page 435. Caution: Symantec discourages manually compressing or decompressing catalog backups using bpimage -[de]compress or any other method. Manually compressing or decompressing a catalog backup while any backup (regular or catalog) is running results in inconsistent image-catalog entries. When users list and restore files, the results could be incorrect. If you choose to compress the image catalog, NetBackup uses the compress command on the server to perform compression after each backup session. It does not make a difference to NetBackup if the backup session was successful. The operation occurs while NetBackup expires backups and before it runs the session_notify script and the backup of the NetBackup catalogs.

NetBackup Catalog Catalog maintenance and performance optimization

357

The time to perform compression depends on the server speed and the number and size of the files being compressed. Files are compressed serially, and temporary working space is required in the same partition. When numerous compressed image-catalog files must be processed, the backup session is extended until compression is complete. The additional backup time is especially noticeable the first time you perform the compression. To minimize the impact of the initial sessions, consider compressing the files in stages. For example, begin by compressing the records for the backups older than 120 days. Continue to reduce the number of days over a period of time until you reach a comfortable setting. Compressing the image catalog can accomplish two objectives:

To reduce greatly the disk space that is consumed. To reduce the amount of media that is required to back up the catalog.

The amount of space that is reclaimed varies with the types of backups you perform. Full backups result in a larger percentage of catalog compression than incremental backups. Normally, more data is duplicated in a catalog file for a full backup. Using catalog compression, a reduction of 80% is possible. This reduction in disk space and media requirements is achieved at the expense of performance when a user lists or restores files. Since the information is uncompressed at each reference, performance degradation is in direct proportion to the number and size of compressed files that are referenced. If the restore requires numerous catalog files to be uncompressed, you may need to increase the time-out value that is associated with list requests. Change the time-out value by changing the LIST_FILES_TIMEOUT option in the bp.conf file of the client.

Uncompressing the image catalog

You may find it necessary to uncompress all records temporarily that are associated with an individual client. Uncompress the records if you anticipate large or numerous restore requests, for example. Perform the following steps as root on the master server: To uncompress the NetBackup catalog 1 2 3 Verify that the partition where the image catalog resides has enough space to uncompress the clients image records. Stop the request daemon, bprd, by running: /usr/openv/netbackup/bin/admincmd/bprdreq -terminate Make sure that bpdbm is running: /usr/openv/netbackup/bin/bpps

358 NetBackup Catalog Catalog maintenance and performance optimization

Expand Host Properties > Master Servers. Open the properties of a host. On the Global Attributes properties, clear the Compress Catalog Interval check box. For more information, see Global Attributes properties on page 435. Set the Compress Catalog Interval Global Attributes property to 0. Change your working directory to /usr/openv/netbackup/bin and run the command: admincmd/bpimage -decompress -client name Restart the request daemon, bprd, by running: /usr/openv/netbackup/bin/initbprd Perform the file restorations from the client. Set the Compress Catalog After Global Attributes property to its previous value. The records that were uncompressed for this client are compressed after the next backup schedule.

5 6

7 8 9

Chapter

Host properties
This chapter describes the NetBackup property settings and explains how each can be changed for one or more servers or clients. This chapter contains the following sections:

Introduction to host properties on page 360 Changing host properties on page 361 Required permissions on page 364 Master server, media server, and client host properties on page 364

360 Host properties Introduction to host properties

Introduction to host properties

Use the host property dialog boxes in the NetBackup Administration Console to customize NetBackup to meet site preferences. In most instances, however, the NetBackup defaults provide satisfactory results. The Host Properties nodes in the Administration Console tree and the Details pane contain the following information: Figure 7-1 Host Properties utility

Menu bar Standard toolbar

Current master server User toolbar Right-click in the Details pane to view the shortcut menu

Details pane

The options on the Host Properties menu bar are described in the online help.

Viewing host properties

The NetBackup Administration Console displays properties for NetBackup master servers, media servers, and clients under Host Properties. To view master server, media server, or client properties 1 2 In the NetBackup Administration Console, expand NetBackup Management > Host Properties. Select Master Servers, Media Servers, or Clients.

Host properties Changing host properties

361

In the Details pane, click the server or client to view the version and platform. Then, double-click to view the properties. To see the properties of a different master server, click File > Change Server.

To export the properties of a host 1 2 3 Expand Master Servers, Media Servers, or Clients. Select one or more hosts. Click File > Export. The Save As dialog box appears. Enter the full path name and click Save.

Changing host properties

The NetBackup properties can be changed to customize NetBackup to meet specific site preferences and requirements. In most instances, the NetBackup defaults provide satisfactory results. Host properties can be set for a single host or for multiple hosts all at one time. The NetBackup Administration Console is one way to change the host properties. Another method is to first use the bpgetconfig command to obtain a list of configuration entries in the bp.conf file. Then, use bpsetconfig to change the entries. The commands are described in NetBackup Commands for UNIX and Linux.

Interpreting the initial settings

The dialog boxes use specific conventions regarding multiple host selections. If the focus is on a setting that is set differently between the multiple selected hosts, the following statement appears at the bottom of the dialog box: This value is different on the selected hosts. This notice is especially helpful regarding differences in text field settings.

Check box states

The host property check boxes may appear in one of the following three 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.

362 Host properties Changing host properties

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 has not been 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.

States of multiple hosts

If a dialog box contains a Selected Host (or similarly named) combo box, all controls on the dialog box 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) combo box, settings of all the selected hosts are combined to arrive at a value that is displayed to the user.

Note: In a clustered enviroment, host properties must be made on each node of the cluster separately.

Radio button states

None of the buttons in a radio button group appear selected when multiple hosts are selected. Leaving it in that state keeps the hosts untouched. Selecting any one from the group updates the setting on all selected hosts.

Number spinner states

A number spinner appears blank when multiple hosts are selected. Leaving it blank keeps the setting untouched on the selected hosts. Changing the value updates the setting on all selected hosts.

Multiple hosts of differing operating systems

If the selected hosts are of various operating systems, none of the operating system-specific information appears. For example, if two clients are selected, Linux client apricot and Windows 2000 client grapefruit, neither the Windows Client node nor the UNIX Client node will appear in the Host Properties tree, or any of the sub-nodes. If all the selected hosts are running the same operating systems, the corresponding node and sub-node will appear.

Host properties Changing host properties

363

At any time you can choose from the following options:

Click Defaults to set all the fields on 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 changes made since the last time changes were applied. Click Apply to save changes to all of the properties for the selected host(s). To make sure that NetBackup uses a changed setting, restart the all daemons and utilities (including the NetBackup Administration Console) to ensure that the new configuration values are used.

Click Help for information on the properties that appear on the current dialog box.

Selecting multiple hosts

You may select more than one host to change properties on multiple hosts at the same time. To simultaneously change the properties on multiple hosts 1 2 3 Expand NetBackup Management > Host Properties > Master Servers, Media Servers, or Clients. Select a host. Hold down the Shift key, then select another host. With multiple hosts still selected, click Actions > Properties. The Properties dialog box displays the names of the selected hosts that will be affected by subsequent host property changes. Host selection
Number of hosts selected

Figure 7-2

364 Host properties Required permissions

The following information about each selected host is displayed:

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

Required permissions
To change the properties on other hosts, the NetBackup server where you logged on using the NetBackup Administration Console must be in the Servers list on the other system. 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. For more information, see To add a NetBackup server to a server list on page 639. Note: All updates to a destination host (unless it is the same as the host you logged on to using the NetBackup Administration Console) will fail if the target host has placed a check box in Allow server file writes on the Universal Settings properties. For more information, see Universal Settings properties on page 477.

Master server, media server, and client host properties

The following sections describe all of the property dialog boxes that can appear for master servers, media servers, and all supported clients. The description explains whether the dialog box is available on master servers, media servers, or clients. The dialog boxes are arranged alphabetically.

Access Control properties

The Access Control properties apply to currently selected master servers, media servers, and clients.

Host properties Master server, media server, and client host properties

365

Symantec Product Authentication and Authorization

The Symantec Product Authentication and Authorization selection determines whether the local system uses access control and how the system uses it.

Required: Select Required if the local system should accept requests only from remote systems using Symantec authentication and authorization. Connections from remote systems not using Symantec authentication and authorization are rejected. Consider selecting Required if all systems are at NetBackup 5.0 or later and maximum security is required. Prohibit: Select Prohibit if the local system should reject connections from any remote system using Symantec authentication and authorization. Consider selecting Prohibit if the network is closed and maximum performance is required. Automatic: Select Automatic if the local system should negotiate with the remote system on whether to use Symantec authentication and authorization. Consider selecting Automatic if the network contains mixed versions of NetBackup.

Symantec Product Authentication and Authorization tab within the Access Control properties
The Symantec Product Authentication and Authorization tab contains a list of networks that are allowed or (not allowed) to use Symantec authentication and authorization with the local system.

366 Host properties Master server, media server, and client host properties

Figure 7-3

Access Control host properties dialog box

Networks list
The Networks list indicates whether specific networks can or cannot use Symantec authentication and authorization with the local system. The names on the list are relevant only if Symantec Product Authentication and Authorization is set to Automatic or Required. If a media server or client does not define a Symantec authentication and authorization network, it uses the networks of its master server. Note: Symantec recommends setting the master server Symantec Product Authentication and Authorization property to Automatic until the clients are configured for Access Control. Then, change the Symantec Product Authentication and Authorization property on the master server to Required.

Add button
To add a network to the Network list, click Add. The Add Network dialog box displays.

Host properties Master server, media server, and client host properties

367

Figure 7-4

Add Network dialog box

The dialog box contains the following properties:

Host/Domain
Indicate whether the network to be added is a Host name or a Domain name.

Host Name/IP
If the network is a host, enter the one of the following:

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

Domain Name/IP
If the network is a domain name, enter one of the following:

A dot followed by the Internet domain name of the remote systems. (.domain) The network of the remote system, followed by a dot. (10.0.0.)

Bit count
Select Bit count to indicate that the mask is based on bit count. Select from between 1 and 32.

368 Host properties Master server, media server, and client host properties

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 Subnet mask to enter a subnet mask in the same the format as the IP address.

Attributes of the selected network setting

The Symantec Product Authentication and Authorization selection determines whether or not the network uses Symantec authentication and authorization.

Required: Select Required if the local system should accept requests only from remote systems using Symantec authentication and authorization. Connections from remote systems not using Symantec authentication and authorization are rejected. Consider selecting Required if all systems are at NetBackup 5.0 or later and maximum security is required. Prohibit: Select Prohibit if the local system should reject connections from any remote system using Symantec authentication and authorization. Consider selecting Prohibit if the network is closed and maximum performance is required. Automatic: Select Automatic if the local system should negotiate with the remote system on whether to use Symantec authentication and authorization. Consider selecting Automatic if the network contains mixed versions of NetBackup.

Remove button
To delete a network, select the network name, then click Remove.

Authentication Domain tab within the Access Control properties

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

Host properties Master server, media server, and client host properties

369

Figure 7-5

Authentication Domain host properties dialog box

If a media server or client does not define an authentication domain, it uses the authentication domains of its master server.

Add button
To add an authentication domain to the domain list, click Add. The Add Authentication Domain dialog box displays. The dialog box contains the following properties:

370 Host properties Master server, media server, and client host properties

Figure 7-6

Add Authentication Domain dialog box

Domain
An Internet or Windows domain name.

Authentication mechanism
Indicate the authentication mechanism: NIS: The Network Information Service, version 1. NIS+: The Network Information Service, version 2. PASSWD: The local UNIX password file on the specified broker. VXPD: A VxSS Private Database. WINDOWS: A Windows Active Directory or Primary Domain Controller. Note: If the authentication domain is UNIX , enter the fully qualified domain name of the host that performs the authentication.

Broker
The operating system of the broker machine supports the domain type of the authentication service. Indicate the host name or the IP address of the authentication broker.

Customize the port number of service

Indicate the port number of the authentication broker (optional).

Host properties Master server, media server, and client host properties

371

Description
Include a description of the domain (optional).

Remove button
To delete an authorization domain, select the name, then click Remove.

Authorization Service tab within the Access Control properties

The Authorization Service is the authorization service used by the local NetBackup server. The Authorization Service tab does not appear as a property for clients. Figure 7-7 Authorization Service host properties dialog box

Note: Define a host to perform authorization if configuring this tab for a media server using Access Control.

Host name
Enter the host name or IP address of the authorization service.

372 Host properties Master server, media server, and client host properties

Customize the port number of the authorization service

To use a nonstandard port number, select Customize the port number and enter the port number of the authorization service.

Host properties Master server, media server, and client host properties

373

Authorization properties
The Authorization properties apply to currently selected master servers and media servers. Figure 7-8 Authorization host properties dialog box

Click Add to add an authorized user, or click Change to change the configuration of an existing authorized user. The New User or Change User dialog box appears. Figure 7-9 New User dialog box

User
In the User text box, type the name that identifies this user to NetBackup. To indicate any user, enter a single asterisk: *

374 Host properties Master server, media server, and client host properties

Host
In the Host text box, type the name of the remote NetBackup Administration Console host from which this user can use NetBackup. To indicate all hosts, enter a single asterisk: *

Domain\Group
In the Domain\Group text box, type the Windows domain and group name in the form domain\group. Or, type the UNIX local group name or the UNIX netgroup name. Or, enter * to indicate for all groups.

Group/Domain type
Select whether this user is authorized to use NetBackup in a Local group or a Network group.

User must be an OS administrator

A checkmark in the User must be an OS administrator check box indicates that the user must be a system administrator of the host from which they connect.

Host properties Master server, media server, and client host properties

375

Backup Exec Tape Reader properties

The Backup Exec Tape Reader properties apply to currently selected master servers. Figure 7-10 Backup Exec Tape Reader host properties dialog box

The Backup Exec Tape Reader option enables NetBackup to read the media that Backup Exec writes. Media is read by using a two-phase import process. For more informations, see Importing images from Backup Exec media on page 342.

Add button
Click Add to enter a GRFS mapping. The Add a GRFS Mapping dialog box appears, that contains the fields that are described in the following sections.

GRFS advertised name

To set the correct client name and paths in Backup Exec UNIX images .f file paths, the master server must be mapped 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

376 Host properties Master server, media server, and client host properties

where ADVERTISED_HOST_NAME is the advertised host name and advertised_path is the advertised path. The ADVERTISED_HOST_NAME should usually be entered in capitals. The GRFS advertised name is the name that the Backup Exec UNIX agent used to identify itself to the Backup Exec server. The advertised name may not have been the same as the real machine name and path. A Backup Exec service had mapped the advertised name to the actual machine name and path, then backed up the advertised name and path. When NetBackup imports Backup Exec UNIX backups, the mapping service is not present, so 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 machine name. NetBackup assumes that the advertised path is the same as the real path.

Actual client name

The Actual client name maps the advertised name to the real machine name.

Actual path
The Actual path maps the advertised path to the real path.

Change button
Click Change to change the selected GRFS entry.

Remove button
Click Remove to remove the selected GRFS entry.

Host properties Master server, media server, and client host properties

377

Bandwidth properties
The Bandwidth properties apply to currently selected master servers. Figure 7-11 Bandwidth host properties dialog box

Bandwidth properties specify limits for the network bandwidth that one or more NetBackup clients of the selected server use. The actual limiting occurs on the client side of the backup connection. By default, the bandwidth is not limited. The bandwidth limits only restrict bandwidth during backups.

How bandwidth limiting works

When a backup starts, NetBackup reads the bandwidth limit configuration then determines the appropriate bandwidth value and passes it to the client. NetBackup computes the bandwidth limit that is based on the current set of active backups on the subnet and the new backup that starts. Backups that start later are not considered. 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. As the number of active backups increase or decrease on a subnet, NetBackup dynamically adjusts the bandwidth limits on that subnet. If additional backups

378 Host properties Master server, media server, and client host properties

are started, the NetBackup server instructs the other NetBackup clients that run on that subnet to decrease their bandwidth setting. Similarly, bandwidth per client is increased if the number of clients decreases. Changes to the bandwidth value occur on a periodic basis rather than as backups stop and start. The periodic changes reduce the number of bandwidth value changes that are required.

Bandwidth throttle setting for the range of IP addresses

This area lists the clients in the range of added IP addresses.

From IP address
The From IP address field specifies the beginning of the IP address range of the clients and networks to which the entry applies. An example is 10.1.1.2

To IP address
The To IP address field specifies the end of the IP address range of the clients and networks to which the entry applies. An example is 10.1.1.9

Bandwidth
The Bandwidth field 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.

Bandwidth throttle settings list

The bandwidth throttle settings list indicates the clients in the range of IP addresses that were added.

Add button
Click the Add button to prepare an entry using the From, To, and Bandwidth fields and add it to the bandwidth table. An entry is added for each of the selected clients.

Host properties Master server, media server, and client host properties

379

Figure 7-12

Add Bandwidth Settings dialog box

Remove button
Click the Remove button to remove a selected entry from the bandwidth table.

Notes on bandwidth limits

NetBackup does not currently support bandwidth limits on the following clients:

NetBackup for Oracle clients NetBackup for DataTools SQL-BackTrack clients NetBackup for Microsoft SQL-Server clients

Bandwidth limits have no effect on a local backup (where the server is also a client and data does not go over the network). 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. 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.

380 Host properties Master server, media server, and client host properties

Busy File Settings properties

The Busy File Settings properties apply to currently selected UNIX clients. The Busy File properties define what occurs when NetBackup encounters a busy file during a backup of a UNIX client. Figure 7-13 Busy File Settings host properties dialog box

For the Busy File Settings to take effect

For the settings in the Busy File Settings host properties to take effect, perform the following steps:

Copy the bpend_notify_busy script: /usr/openv/netbackup/bin/goodies/bpend_notify_busy to the path: /usr/openv/netbackup/bin/bpend_notify Set the file access permissions to allow group and other to execute 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.

Host properties Master server, media server, and client host properties

381

For example, a policy name of AAA_busy_files is selected ahead of B_policy.

Working directory
The Working directory property 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.

Operators email address

The Operators e-mail address property specifies the recipient of the busy-file notification message when the action is set to Send e-mail. 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.

Process busy files

Enable Process busy files for NetBackup to process busy files 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. For more informations, see Busy file processing (UNIX clients only) on page 105 in NetBackup Administrators Guide, Volume II.

File action file list

The File action list 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.

Add button
Click Add to add a new file entry. Enter the file and path directly, or browse to select a file.

Add to all button

Click Add to all to add a new file entry for all of the clients currently selected. Enter the file and path directly, or browse to select a file.

382 Host properties Master server, media server, and client host properties

Remove button
Select the file or directory and click Remove to remove the file from the file action list.

Busy file action

The Busy file action property directs the action that NetBackup performs on busy files 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 e-mail: Directs NetBackup to mail a busy file notification message to the user that is specified in the Operators E-mail address field in this dialog box. Retry the backup: Directs NetBackup to retry the backup on the specified busy file. The Retry count value determines the number of times NetBackup tries a backup. Ignore: Directs NetBackup to exclude 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.

Retry count
The Retry count property specifies the number of times to try the backup. Default retry count: 1.

Host properties Master server, media server, and client host properties

383

Clean-up properties
Clean-up properties apply to the length of time to retain various logs and incomplete jobs. Figure 7-14 Clean-up host properties dialog box

Keep logs
The Keep logs property 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. Keep logs 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. Specify how many days youd like 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. Default: 28 days.

Keep vault logs

The Keep vault logs property is enabled if Vault is installed, and specifies the amount of time that the Vault session directories are kept. Session directories are found in the following location:

384 Host properties Master server, media server, and client host properties

install_path\netbackup\vault\sessions\vaultname\sidxxxx
where xxxx is the session number. This directory contains vault log files, temporary working files, and report files.

Image cleanup
The Image cleanup property 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.

Catalog cleanup wait time

The Catalog cleanup wait time property 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.

Keep true image restoration (TIR) information

The Keep true image restoration (TIR) information property specifies the number of days to keep true image restore information on disk. After the specified number of days, the images are pruned (removed). This applies to all policies for which NetBackup collects true image restore information. Default: 1 day. When NetBackup performs a true image backup, it stores two images on the backup media:

Backed up files True image restore information

NetBackup also stores the true image restore information on disk in the /usr/openv/netbackup/db/images directory. NetBackup retains the information for the number of days this property specifies. To keep the information on disk speeds up restores. If a user requests a true image restore after the information has been 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.

Host properties Master server, media server, and client host properties

385

Move restore job from incomplete state to done state

This property 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. For more informations, see Universal Settings properties on page 477 and Checkpoint restart for restore jobs on page 683.

Move backup job from incomplete state to done state

This property 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. Minimum setting: 1 hour. Maximum setting: 72 hours. Default: 3 hours. When an active job has an error, the job goes into an Incomplete state. In the Incomplete state, the administrator may 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.

386 Host properties Master server, media server, and client host properties

Client Attributes properties

Client Attributes properties apply to clients of currently selected master servers. Client Attributes contains three subtabs:

General Tab Connect Options tab on page 388 Windows Open File Backup tab on page 391 General tab of Client Attributes host properties dialog box

Figure 7-15

Allow client browse

The Allow client browse property allows all clients to browse files for restoring. This attribute is overridden if the Browse and restore ability on the General tab is set to Deny both for a particular client(s).

Allow client restore

The Allow client restore property allows all clients to restore files. This attribute is overridden if the Browse and restore ability on the General tab is set to Allow browse only or Deny both.

Host properties Master server, media server, and client host properties

387

Clients list
The Clients list is a list of clients in the client database on the currently selected master server(s). A client must be in the client database before you are able to change the client properties in the Client Attributes dialog box. The client database consists of directories and files in the following directory:
/usr/openv/NetBackup/db/client

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. You can also create, update, list, and delete client entries by using the bpclient command that is located in the following directory:
/usr/openv/netbackup/bin/admincmd

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. For more information, see Client name on page 395. Note: Use the bpclient command to add clients to the client database if dynamic addressing (DHCP) is in use. (See Dynamic host name and IP addressing on page 99 in the NetBackup Administrators Guide, Volume II for instructions.)

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

Remove button
Select a client in the Clients list and click Remove to delete the selected client from the client database.

General tab
The following sections describe the properties on the General tab within Client Attributes. For more information about the Windows Open File Backup properties, see Windows Open File Backup tab on page 391.

Maximum data streams

The Maximum data streams property 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.)

388 Host properties Master server, media server, and client host properties

To change the setting, select Maximum data streams. Then scroll to or enter a value up to 99. Maximum data streams interacts with the Maximum jobs per client and Limit jobs per policy as follows: For more information see Maximum jobs per client on page 436 and Limit jobs per policy on page 97.

If Maximum data streams is not set, the limit is either Maximum jobs per client or Limit jobs per policy, whichever is lower. If Maximum data streams is set, NetBackup ignores Maximum jobs per client. NetBackup uses either Maximum data streams or Limit jobs per policy, whichever is lower.

Browse and restore ability

The Browse and restore ability property specifies 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 attribute settings, select Use global settings. (See Allow client browse on page 386 and Allow client restore on page 386.). 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
The Free Browse property applies to the privileges that are allowed to a non-root user that is logged into the client. The Free browse property specifies whether the clients can list and restore from scheduled backups. (This setting does not affect user backups and archives.) Root users are able to list and restore from scheduled backups as well as user backups regardless of the Free browse setting.

Connect Options tab

The properties in the Connect Options tab describe how a NetBackup server connects to NetBackup clients.

Host properties Master server, media server, and client host properties

389

Figure 7-16

Connect Options tab of Client Attributes host properties dialog box

BPCD connect back

Use default connect options: Use the value that is defined in the Firewall host properties of the clients NetBackup server. For more information, see Default connect options on page 424. 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.

Ports

Use default connect options: Use the value that is defined in the Firewall host properties of the clients NetBackup server. For more information, see Default connect options on page 424. Reserved port: Use a reserved port number. Non-reserved port: Use a non-reserved port number.

390 Host properties Master server, media server, and client host properties

Daemon connection port

Use default connect options: Use the value that is defined in the Firewall host properties of the clients NetBackup server. For more information, see Default connect options on page 424. Automatic: Connect to the daemons on the server using vnetd if possible. If the daemons cannot use vnetd, the connection is made using the daemons legacy port number. VNETD only: Connect to the daemons on the server using only vnetd. If the firewall rules prevent a server connection using the legacy port number, check this option. Daemon port only: Connect to the daemons on the server using only the legacy port number.

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.

Host properties Master server, media server, and client host properties

391

Windows Open File Backup tab

Windows Open File Backup properties apply to selected Windows master servers. The properties appear as a tab on the Client Attributes dialog box. Figure 7-17 Windows Open File Backup tab of Client Attributes host properties dialog box

The Windows Open File Backup properties 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. 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.

Add and remove buttons

Click Add to add NetBackup clients (5.0 or later) only if you want to change the Windows Open File Backup defaults. By default, no clients are listed and the server uses the following Windows Open File Backup defaults for all Windows NetBackup clients (5.0 or later):

Windows Open File Backup is enabled on the client. The snapshot provider for the client is VSP.

392 Host properties Master server, media server, and client host properties

Snapshots are taken of individual drives (Individual drive snapshot) as opposed to all drives at once (Global drive snapshot). Upon error, the snapshot is aborted (Abort backup on error).

To delete a client from the list, select the client, then click Delete. To make changes to the default settings, add the client name to the client list. Select the client name in the client list, then make changes to the clients Windows Open File Backup configuration settings.

Enable Windows Open File Backups for this client

The Enable Windows Open File Backups for this client property specifies that Windows Open File Backups be used for selected clients. Add clients to the list only if you want to change the default property settings. (Default: Windows Open File Backup is enabled for all Windows NetBackup clients, 5.0 or later.)

Using the Snapshot Client option with this property

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.

Use Veritas Volume Snapshot Provider (VSP)

The Use Veritas Volume Snapshot Provider (VSP) property specifies that Volume Snapshot Provider (VSP) be used as the snapshot provider for selected clients. The default is VSP. VSP is configured for each client using the VSP tab for the client. (The tab is found under Host Properties > Clients > Selected client(s) > Windows Client > VSP). For more information, see VSP (Volume Snapshot Provider) properties on page 485. VSP can be used for Windows NT/2000/XP/Server 2003 clients. By default, all NetBackup clients (5.0 or later) use VSP as the Windows Open File Backup snapshot provider.

Use Microsoft Volume Shadow Copy Service (VSS)

The Use Microsoft Volume Shadow Copy Service (VSS) property specifies that VSS be used to create volume snapshots of volumes and logical drives for

Host properties Master server, media server, and client host properties

393

selected clients. VSS can be used for Windows Server 2003 clients only. Configure VSS through the Microsofts VSS configuration dialog boxes.

Individual drive snapshot

The Individual drive snapshot property specifies that the snapshot should be of an individual drive (default). When this property is enabled, snapshot creation and file backup is done sequentially on a per volume basis. For example, assume that drives C and D are to be backed up. If Individual drive snapshot is selected, NetBackup performs the following actions for the backup job: 1 2 NetBackup takes a snapshot of drive C, backs it up, and discards the snapshot. NetBackup 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. (For example, if one volume in the volume set cannot meet the VSP quiet time requirements.) Individual drive snapshot is enabled by default for all non multi-streamed backups using the Windows Open File Backup option.

Global drive snapshot

The Global drive snapshot property specifies that the snapshot is of a global drive. All the volumes that require snapshots for the backup job (or stream group for multi-streamed backups) are taken at one time. For example, assume that drives C and D are to be backed up. In this situation, NetBackup performs the following actions: 1 2 3 NetBackup takes a snapshot of C and D. NetBackup backs up C, then backs up D. NetBackup 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.

394 Host properties Master server, media server, and client host properties

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

Abort backup on error

The Abort backup on error property specifies that a backup aborts if it fails for a snapshot-related issue after the snapshot is created and while the backup is using the snapshot to back up open or active files on the file system. The most common reason for a problem after the snapshot has been created and is in use by a backup, is the cache storage having filled to capacity. If Abort on error 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 has been successfully created and is in use by a backup job.

Disable snapshot and continue

The Disable snapshot and continue property 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.

Host properties Master server, media server, and client host properties

395

Client Name properties

The Client Name properties apply to a single, currently selected client. Figure 7-18 Client Name host properties dialog box

Client name
The host that is specified in the Client name field is the NetBackup client name for the selected client. The Client name is the name by which the client is known to NetBackup. 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, the client cannot browse for its own backups. For more information, see Client Attributes properties on page 386. 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.

396 Host properties Master server, media server, and client host properties

Client Settings (NetWare) properties

The Client Settings properties apply to currently selected NetWare clients.

Back up migrated files

The Back up migrated files property 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.

Uncompress files before backing up

The Uncompress files before backing up 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.

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

The Keep status of user-directed backups, archives, and restores property specifies how long the system keeps progress reports before it automatically deletes the reports. Default: 3 days.

Host properties Master server, media server, and client host properties

397

Client Settings (UNIX) properties

The UNIX Client Settings apply to currently selected UNIX clients. Figure 7-19 Client Settings (UNIX) host properties dialog box

Locked file action

The Locked file action property determines what happens when NetBackup tries to back up a file with mandatory file locking enabled in its file mode.

Wait: By default, NetBackup waits for files to become unlocked. If the wait exceeds the Client read timeout host property, configured on the master server, the backup fails with a status 41. For more information, see Client read timeout on page 475. 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

The Keep status of user-directed backups, archives, and restores property specifies the number of days to keep progress reports before deleting them. Default: 3 days. Minimum: 0. Maximum: 9,999 days.

398 Host properties Master server, media server, and client host properties

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 to the value before backup

The Reset file access time property 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. DO NOT use this option or USE_CTIME_FOR_INCREMENTALS if you are running Storage Migrator on the system. Setting these options causes the atime for files to be updated every time they are backed up. An updated atime makes it appear as if the files are frequently used and prevents Storage Migrator from selecting the files for migration.

Megabytes of memory to use for file compression

Note: This option has a reasonable default and should be changed only if problems are encountered. The Megabytes of memory to use for file compression property 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 1/2 the actual physical memory on a machine to avoid excessive swapping. Default: 0.

Use VxFS file change log for incremental backups

The Use VxFS file change log for incremental backups property determines if NetBackup uses the File Change Log on VxFS clients. This feature is supported on all platforms and versions where 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.

Host properties Master server, media server, and client host properties

399

Linux running VxFS 4.1 or greater

Default: off. The File Change Log (FCL) tracks changes to files and directories in a file system. Changes may 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. 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 time stamp for each backup. The following platforms and versions are supported:

Recommended use
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. Note: The VxFS mount point must be specified in the policy backup selections list for this property to take effect. For more information, see Backup Selections tab on page 163

Conditions for use

In order for the Use VxFS file change log feature to work:

The Use VxFS file change log property must be enabled for every client that wants NetBackup to take advantage of the FCL. The FCL must be enabled on the VxFS client. See the Veritas File System Administrators Guide for information about how to enable the FCL on the VxFS client. The Use VxFS file change log property must be enabled on the client(s) in time for the first full backup. Subsequent incremental backups need this full backup to stay synchronized.

400 Host properties Master server, media server, and client host properties

The VxFS mount point must be specified 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. For more information, see Cross mount points on page 103.

Note: If the policy has Collect true image restore information or Collect true image restore information with move detection enabled, the Use VxFS file change log property on the client is ignored.

Activity Monitor messages

The Activity Monitor displays messages that note when the file change log is used during a backup: Using VxFS File Change Log for backup of pathname The Activity Monitor also notes when full and incremental backups are not synchronized.

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 any errors are encountered while processing the FCL, NetBackup switches to the normal files system scan. If this switch occurs, it is displayed in the Activity Monitor.

VxFS administration
Additional VxFS commands are available to administrate the FCL. The commands are documented in the Veritas File System Administrators Guide.

Default cache device path for snapshots

The Default cache device path for snapshots property identifies a raw partition available to the copy-on-write process. This raw partition is used when either nbu_snap or VxFS_Snapshot are selected as the snapshot method. The partition must exist on all the clients that are included in the policy. For additional information, see the NetBackup Snapshot Client Administrators Guide.

Host properties Master server, media server, and client host properties

401

Do not compress files ending with

The Do not compress files ending with list specifies a list of file extensions. During a backup, NetBackup does not compress files with these extensions because the file can 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 button
Use the Add button to add 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 the dialog box.

Add to all button

Use the Add to All button to add 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.

Remove button
Click the Remove button to remove 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. Then, click the button.

402 Host properties Master server, media server, and client host properties

Client Settings (Windows) properties

The Windows Client properties apply to currently selected Windows clients. Figure 7-20 Client Settings (Windows) host properties dialog box

General level logging

The General level logging property enables logs for bpinetd, bpbkar, tar, and nbwin. The higher the level, the more information is written. Default: 0.

TCP level logging

The TCP level logging property enables logs for TCP. Scroll to one of the following available log levels: 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.

Host properties Master server, media server, and client host properties

403

Wait time before clearing archive bit

The Wait time before clearing archive bit property specifies how long the client waits before the archive bits for a differential 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 in incrementals

NetBackup offers support for the Microsoft change journal to enhance performance of incremental backups on Windows 2000/XP/Server 2003 systems. By enabling the Use change journal in incrementals check box, NetBackup can provide faster incremental backups for NTFS 5 (and later) volumes that store large numberspossibly millionsof files. Use change journal in incrementals is available only when a valid tracker database exists on the applicable volumes. Default: Not enabled. When this property is enabled, the Incrementals are based on timestamp property is automatically enabled. The Microsoft change journal is a disk file that records and retains the most recent changes to an NTFS volume. By monitoring the change journal, NetBackup can determine which file system objects have changed and when. This information is used to shorten the discovery process that NetBackup performs during an incremental backup by making a file system scan unnecessary.

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:

If the NTFS volume contains more than 1,000,000 files and folders and the number of changed objects between incremental backups is few (less than 100,000), the volume is a good candidate for enabling NetBackup change journal support. 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

Unsuitable candidates for enabling NetBackup change journal support:

404 Host properties Master server, media server, and client host properties

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

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. After Use change journal in incrementals is selected, the NetBackup client service must be restarted on the target system. A full backup of the target system must be completed under change journal monitoring to enable change journal-based incremental backups. 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. For more information, see Checkpoint restart for restore jobs on page 683. Support for change journal is not offered with several NetBackup options or Symantec products. If Use change journal in incrementals is enabled, it has no effect while using the following options or products:

True Image Restore (TIR) For more information, see Collect true image restore information on page 108. True Image Restore with Move Detection For more information, see Collect true image restore information with move detection on page 109. Synthetic backups For more information, see Synthetic backup on page 128. Intelligent Disaster Recovery (IDR) For more information, see the NetBackup Administrators Guide, Volume II.

Host properties Master server, media server, and client host properties

405

Bare Metal Restore (BMR) For more information, see the NetBackup Bare Metal Restore Administrators Guide.

Incrementals based on timestamp

The Incrementals based on timestamp property specifies that files are selected for the backups that are based on the date that the file was last modified. When Use change journal in incrementals is selected, Incrementals based on timestamp is automatically selected.

Incrementals based on archive bit

The Incrementals based on archive bit property 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 bits property indicates. A cumulative-incremental or user backup has no effect on the archive bit. For more information, see Wait time before clearing archive bit on page 403. Disable this property to include a file in an incremental backup only if the datetime stamp for the file has been changed since the last backup. For a differential-incremental backup, NetBackup compares the datetime 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 (default).

Time overlap
The Time overlap property specifies the number of minutes to add to the date range for incremental backups when using date-based backups. This value compensates for differences in the speed of the clock between the NetBackup client and server. Default: 60 minutes.

406 Host properties Master server, media server, and client host properties

This value is used during incremental backups when using the archive bit and when examining the create time on folders. This comparison is done for archive bit-based backups as well as date-based backups.

Communications buffer size

The Communications buffer size property specifies the size (in kilobytes) of the TCP/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. Default: 16 kilobytes.

User directed timeouts

The User directed timeouts property 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. Default: 60 seconds.

Maximum error messages for server

The Maximum error messages for server property 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. Default: 10.

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

The Keep status of user-directed backups, archives, and restores property specifies how many days the system keeps progress reports before NetBackup automatically deletes them. Default: 3 days.

Perform default search for restore

The Perform default search for restore property instructs NetBackup to search the default range of backup images automatically. The backed up folders and files within the range are displayed 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. Default: option is enabled.

Host properties Master server, media server, and client host properties

407

Data Classification properties

Data classifications must be configured before Storage Lifecycle Policies can be configured. For more information, see Storage Lifecycle Policies on page 253. Figure 7-21 Data Classification host properties dialog box

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

Rank
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 buttons to change rank and move the classification up or down in the list. To create a new data classification, click New. The New dialog displays. 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.

408 Host properties Master server, media server, and client host properties

Name
NetBackup provides four 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)

Data classification names can be modified.

Description
Enter a meaningful description for the data classification. Descriptions can be modified.

Classification ID
The 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 becomes associated with a backup image by setting the Data Classification attribute in the policy dialog. The ID is written into the image header. The storage lifecycles use the ID to identify the images that are associated with classification. For more information, see Data classification on page 90. ID values may 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. To create or change a data classification

To create a new data classification, click New. Modify the name and description in the Change dialog box. Add a name and description in the New Data Classification dialog box. A new classification appears at the bottom of the list. Use the Move Up and Move Down buttons to move the classification level up or down in the list. To change an item, select a line and click Change. Modify the name and description in the Change Data Classification dialog box.

Host properties Master server, media server, and client host properties

409

Encryption properties
The Encryption properties control encryption on the currently selected client. Figure 7-22 Encryption host properties dialog box

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. For more specific information on the Encryption option, see the NetBackup Security and Encryption Guide.

Encryption permissions
The Encryption permissions property indicates the encryption setting on the selected NetBackup client as determined by the master server. If it is necessary to change this property, select one of the following options:

Not allowed: Specifies that the client does not permit encrypted backups. If the server requests an encrypted backup, the backup job ends due to error.

410 Host properties Master server, media server, and client host properties

Allowed: 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. Required: Specifies that the client requires encrypted backups. If the server requests an unencrypted backup, the backup job ends due to error.

Enable encryption
Select the Enable encryption property if the NetBackup Encryption option is used on the selected client.

Enable standard encryption

The Enable standard encryption property pertains to the 128-bit and the 256-bit options of NetBackup Encryption. If the selected client runs NetBackup 5.1 and 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.

Use legacy DES encryption

The Use legacy DES encryption property pertains to the 40-bit and the 56-bit Data Encryption Standard (DES) NetBackup encryption packages. If the selected client is running a version of NetBackup earlier than 5.1, Use legacy DES encryption is automatically selected.

Encryption strength
The Encryption strength property 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.

Host properties Master server, media server, and client host properties

411

Encryption libraries
The Encryption libraries property specifies the folder that contains the encryption libraries on NetBackup clients. The default setting is generally sufficient. The following is the default location:

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.

Encryption key file

The Encryption key file property specifies the file that contains the encryption keys on NetBackup clients. The following is the default location:

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.

412 Host properties Master server, media server, and client host properties

Exchange properties
The Exchange properties apply to currently selected Windows clients. Figure 7-23 Exchange host properties dialog box

The Exchange properties specify the mailbox to associate with the NetBackup Client Service account. Specify a mailbox only if the NetBackup client and NetBackup Microsoft Exchange Server agent software are installed on the Microsoft Exchange Server. The NetBackup Client Service account must be associated with a valid Exchange mailbox for NetBackup to access the mailboxes and folders during backups and restores. Create a unique mailbox name for the NetBackup Client service account. If a mailbox is not created for the NetBackup Client service, use any existing mailbox on the Microsoft Exchange Server. The NetBackup Client service account must have granted logon rights to the mailbox. For more information on the mailbox settings, see the NetBackup for Microsoft Exchange Server Administrators Guide.

Snapshot verification I/O throttle

NetBackup runs the checksum integrity verification after a snapshot is complete. Adjust the inputs and outputs rate of the verification by adjusting the value of the Snapshot verification I/O throttle option. Specify the number of

Host properties Master server, media server, and client host properties

413

inputs and outputs to process for each second-long pause. (Applicable to Exchange 2003 SP2 or later.) The value is used during snapshot validation by the Exchange command ESEUTIL /pXXX where XXX is the value of Snapshot verification I/O throttle. ESEUTIL defines the /p setting as a forced second-long pause after every XXX I/Os to limit the I/O rate during database verification. See the Microsoft Exchange documentation regarding the ESEUTIL command for details.

Backup option for log files during full backups

The Backup option for log files during full backups property allows all of the transaction logs generated by Exchange to be backed up. Logs can be backed up in either a full or a user-directed type backup. This property controls which log files are backed up during the backup of an Exchange database:

Back up only uncommitted log files (Default.) The only log files that are backed up are those from the most current full backup. With this property selected for backups, users are unable to roll forward from previous backups through the most current. Back up all log files (including committed log files) All log files are backed up. With this property selected, users are able to roll through previous full backups.

Mailbox for message level backup and restore

Specifies the mailbox for the NetBackup Client service account. The mailbox can be one of the following:

An Exchange mailbox name A fully qualified name of the form /O=org_name/OU=site_name/CN=server_name/CN=mailbox_name A mailbox alias

Enable single instance backup for message attachments

Microsoft Exchange Server uses single-instance storage (SIS) to store mail messages. SIS allows the database to keep one copy of a message attachment that is sent to multiple users on the same server. To perform SIS backups, check Enable single instance backup for message attachments on the client where Exchange server is installed.

414 Host properties Master server, media server, and client host properties

Exclude Lists properties

Use the Exclude Lists properties to create and to modify the exclude lists for Windows clients. An exclude list names policies, schedules, files, and the directories to be excluded from automatic backups. Note: Exclude Lists properties apply only to Windows clients. On NetWare target clients, specify the exclude list when the targets are added. (For more information, see the NetBackup users guide for the client.) NetWare NonTarget clients do not support exclude lists. For UNIX clients, see Excluding files from automatic backups on page 195.

Use case sensitive exclude list

The Use case sensitive exclude list property indicates that the files and directories to exclude are case sensitive.

Exclude list
The Exclude list displays the policies that contain schedule, file, and directory exclusions.

Exceptions to the exclude list

The Exceptions to the exclude list displays policies, schedules, files, and the 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.

Add buttons
The Add button performs different functions, depending on whether it is used from the Exclude list or from the Exceptions to the exclude list.

From the exclude list

Click Add to exclude 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.

Host properties Master server, media server, and client host properties

415

Figure 7-24

Add to Exclude List dialog box

When the policies on the Exclude list run, the files and directories that are specified on the list are backed up.

From the exceptions list

Click Add to create 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 buttons

The Add to All button is enabled only under the following conditions:

More than one client is selected for configuration and, a list item is selected that has not been configured on the selected hosts. (Rather, a grayed-out list item is selected.)

Add to All performs different functions, depending on whether it is used from the Exclude list or from the Exceptions to the exclude list.

From the exclude list

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.

From the exceptions list

Click the Add to All button to add 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.

416 Host properties Master server, media server, and client host properties

Remove buttons
Remove performs different functions, depending on whether it is used from the Exclude list or from the Exceptions to the exclude list.

From the exclude list

Click Remove to remove the selected policy, schedule, or file from the Exclude list. The item is included in the backup.

From the exceptions list

Click Remove to remove the selected policy, schedule, or file from the Exceptions list. The item is excluded from the backup.

Shared fields in exclude lists

Both the Add to exclude list dialog box and the Add exceptions to exclude list dialog box contain the following fields:

Policy
In the Policy field, enter the policy name that contains the files and the directories 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>.

Schedule
In the Schedule field, enter the schedule name that is associated with the files and the directories 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>.

Files/Directories
In the Files/Directories field, enter the full path to the file(s) and the directories to exclude or make exceptions for.

Exclude lists for specific policies or schedules

To create an exclude or include list for a specific policy 1 2 In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Clients. Double-click on a client. To add an entry to the exclude list:

Host properties Master server, media server, and client host properties

417

a b

Under the Exclude List, click Add. The Add to Exclude List dialog box appears. 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.

e 3

To add an exception to the exclude list: a b Under the Exceptions to the Exclude List, click Add. The Add Exceptions to the Exclude List dialog box appears. 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.

e 4

Click Apply to accept the changes. Click OK to accept the changes and close the host properties dialog box.

Which list is used if there is more than one?

If there is more than one exclude or include list for a client, NetBackup uses only the most specific one. For example, assume a client has three 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.

418 Host properties Master server, media server, and client host properties

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

Syntax rules for exclude lists

Note: 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 before proceeding. The following syntax rules apply to exclude lists:

Only one pattern per line is allowed. NetBackup recognizes standard wildcard use, as described in Using wildcards in NetBackup on page 632. 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, 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 is equivalent to prefixing the file pattern with
\ \*\ \*\*\ \*\*\*\

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

Host properties Master server, media server, and client host properties

419

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 that begin with a pound sign (#) are ignored.

Windows client example exclude list

Assume that an exclude list 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. 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 may 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 named silk:

The backup policy backup selection list for silk indicates ALL_LOCAL_DRIVES. When a scheduled backup runs, the entire client is backed up. The entire client would also be backed up if the backup selection list

420 Host properties Master server, media server, and client host properties

consisted 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 Windows client silk 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 would be traversed.

Host properties Master server, media server, and client host properties

421

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

The backup selection list for client hagar consists of the following: / The exclude list for UNIX client hagar consists of the following: / The include list of UNIX client hagar 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.

422 Host properties Master server, media server, and client host properties

Fibre Transport properties

The Fibre Transport master server properties apply to the SAN clients whose preferences have not been set explicitly. The Fibre Transport media server property applies to the SAN clients for selected media servers. 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 Shared Storage Guide. Figure 7-25 Master server Fibre Transport host properties

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

Host properties Master server, media server, and client host properties

423

For the global property that is specified on the master server, the default is Preferred.

Always
The Always property specifies that NetBackup should always use an FT pipe always 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

Media server property only. The Maximum concurrent FT connections 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

Client property only. The Use defaults from the master server configuration property specifies to use the properties that are configured on the master server.

424 Host properties Master server, media server, and client host properties

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 386.) Figure 7-26 Firewall host properties dialog box

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.

Default connect options

By default, the firewall settings are configured to require the fewest possible ports to be open. These properties correspond to the DEFAULT_CONNECT_OPTIONS entry in the bp.conf file.

Host properties Master server, media server, and client host properties

425

Figure 7-27

Default Connect Options dialog box

To change any of the Default connect options, click Change. The Default Connect Options dialog box appears that contains the following properties:

BPCD connect back

The BPCD connect back property specifies how daemons are to connect back to the NetBackup Client daemon (BPCD):

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. Take the example of when 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.

Ports
Select whether the server is connected to by a reserved or non-reserved port number:

Use reserved ports: 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. This property is located on the Universal Settings dialog box under Host Properties > Master Servers or Host Properties > Media Servers. For more information, see Accept connections on non reserved ports on page 480.

426 Host properties Master server, media server, and client host properties

Daemon connection port

The Daemon connection port setting determines which of the following methods is used when it connects to the server:

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. (Automatic is the default.) 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 only the traditional port number.

To change the default connect options for the selected server, click Change. 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.

Hosts list
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 button
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 button

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

Remove button
Select a host name in the list, then click Remove to remove the host from the list.

Host properties Master server, media server, and client host properties

427

Attributes for selected hosts

Connect options can be configured for individual servers. These properties correspond to the CONNECT_OPTIONS entry in the bp.conf file.

BPCD connect back

The BPCD connect back property specifies how daemons are to connect back to the NetBackup Client daemon (BPCD):

Use default connect options: Use the method that are specified under Default connect options. (Use default connect options is the default for BPCD connect back.) 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. Take the example of when 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.

Ports
Select whether a reserved or non-reserved port number should be used to connect to the server:

Use default connect options: Use the method that are specified under Default attributes. (Use default is the default.) Reserved port: Connect to the server by a reserved port number. Non reserved port: 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. This property is located on the Universal Settings dialog box under Host Properties > Master Servers or Host Properties > Media Servers. For more information, see Accept connections on non reserved ports on page 480.

Daemon connection port

Select the Daemon connection port method to use to connect to the server:

Use default connect options: Use the method that is specified under Default attributes. (Use default is the default.) Automatic

428 Host properties Master server, media server, and client host properties

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. (Automatic is the default.)

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.

Note: Both servers and clients must have NetBackup version 4.5 or later installed for vnetd to work. To set up vnetd between a server and a client 1 In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Client Attributes. In the client list, select the client you want to change. Under BPCD connect back, select VNETD port. Click OK.

2 3 4

Or, add the client to the client database by running the bpclient command, that is located in /usr/openv/netbackup/bin/admincmd To set up vnetd between servers 1 In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Firewall. In the host list, select the host you want to change. Under BPCD connect back, select VNETD port. Click OK.

2 3 4

Host properties Master server, media server, and client host properties

429

Or, add a CONNECT_OPTIONS entry to /usr/openv/netbackup/bp.conf for each server as described in CONNECT_OPTIONS on page 43 in the NetBackup Administrators Guide, Volume II. To enable logging for vnetd Create a vnetd directory in the following location: On Windows: install_path\NetBackup\logs\vnetd On UNIX: /usr/openv/logs/vnetd

Example setup for using the vnetd port

The following is a sample configuration to use the vnetd port for bprd, bpdbm, bpjobd, bpvmd, and the robotic daemons on master and media servers. The example uses the Use connect back bpcd connections:

Change in the configuration file setup:

Add the following configuration option to the vm.conf file on the machines that may connect to vmd or the robotic daemons on hostname: CONNECT_OPTIONS = hostname x y z Where: x is 0 or 1 and is ignored for vm.conf. y is 0 or 1 and is ignored for vm.conf. z is 0 for automatic connections. A vnetd connection is tried first when selected. If that fails, a traditional connection is tried. 1 = vnetd-only connections. 2 = Traditional connections (default)

Change in the host properties:

In the Firewall properties for the master server, add an entry in the host list for each remote media server. (Host Properties > Master Servers > Selected master server > Firewall.) Under BPCD connect back, select VNETD port. Choose Automatic for the Daemon connection port. In the Firewall properties for each media server, add an entry for each remote server. (Host Properties > Media Servers > Selected media server > Firewall.) Under BPCD connect back, select VNETD port. Choose Automatic for the Daemon connection port. In the Firewall properties for each Client, add an entry for the Master server. (Host Properties > Clients > Selected client > Firewall.) Choose Automatic for the Daemon connection port.

430 Host properties Master server, media server, and client host properties

In the Client Attributes properties for the Master server, add an entry for each remote client. (Host Properties > Master Servers > Selected master server > Client Attributes.) Under BPCD connect back, select VNETD port.

Host properties Master server, media server, and client host properties

431

General Server properties

The General Server properties apply to selected master and media servers. Figure 7-28 General Server host properties dialog box

Delay on multiplexed restores

The Delay on multiplexed restores property applies to multiplexed restores. It specifies how long the server waits for additional restore requests of multiplexed images on the same tape. All of the restore requests are received within the delay period are included in the same restore operation (one pass of the tape). Default: delay of 30 seconds.

Check the capacity of disk storage units

The Check the capacity of disk storage units property determines how often NetBackup checks disk storage units for available capacity. If the frequency is too often, checks are made more often than necessary and system resources are wasted. If the frequency is not often enough, too much time elapses and backup jobs are delayed. Default: 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.

432 Host properties Master server, media server, and client host properties

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 the client is also a media server or a master server and Must use local drive is checked, a local drive is used for backups. If all drives are down, another may 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 greatly reduce the time it takes to restore files. DAR allows 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 the Direct access recovery for NDMP restores 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.

Document-level restore options

The Document-level restore options concern the use of SharePoint 2003 to restore specific files. (For example, .doc, .xls, .pdf, or .txt files on NetBackup 6.5 clients.) Document-level restores can be performed only if the backup was written to a disk storage unit. Click the Configure button to configure images to be duplicated from a tape to a disk storage unit.

Automatically duplicate images from tape to disk

To duplicate the images from tape to a disk storage unit, enable this option. From the Destination disk storage unit drop-down menu, select a disk storage unit to contain the duplicated images. Select a retention level for the duplicated images on the disk storage unit. For more information, see Retention on page 138. Note: To perform document-level restores, the MS-SharePoint policy that backs up the images must have the Enable document restore Policy attribute enabled. For more information, see Enable document restore on page 115.

Host properties Master server, media server, and client host properties

433

Media host override

Specific servers can be specified in the Media host override 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 are some examples of when to use this capability:

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.

Add button
Click Add to add a host to the Media host override list. The Add Media Override Settings dialog box contains the following fields: Figure 7-29 Add Media Override settings dialog box

Original backup server: Server where data was backed up originally. Restore server: Server that is to process future restore requests.

Add to all button

Click Add to All to add a host to the Media host override list for all of the hosts currently selected.

Change button
To change an entry in the Media host override list, select a host name, then click Change.

434 Host properties Master server, media server, and client host properties

Remove button
Select the host in the Media host override list and click Remove to remove the host from the list. To force restores to go to a specific server 1 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 Manager service 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.

Host properties Master server, media server, and client host properties

435

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 7-30 Global Attributes host properties dialog box

Job retry delay

The Job retry delay property specifies how often NetBackup retries a job. Default: 10 minutes. Maximum: 60 minutes; minimum: 1 minute.

Schedule backup attempts

Note: This attribute does not apply to user backups and archives. The Schedule backup attempts property specifies the number of times that NetBackup tries to complete a scheduled backup job during the specified time period. Schedule backup attempts allows you to limit the number of tries if a client or drive is down or media is unavailable. If the backup window closes before the retry starts, the job fails with a status code 196. Default: 2 tries in 12 hours.

436 Host properties Master server, media server, and client host properties

Policy update interval

The Policy update interval property specifies the number of minutes to wait after changing a policy before that policy is processed. The interval allows the NetBackup administrator time to make multiple changes to the policy. Default: 10 minutes. Maximum: 1440 minutes; minimum: 1 minute.

Priority of restore jobs

The Priority of restore jobs property determines if restore jobs have priority over other types of jobs in contention for drives. The higher the value, the more priority restore jobs have. Default: 99999. Note: Multiplexed backup jobs are unaffected by the restore priority setting.

Maximum jobs per client

The Maximum jobs per client property specifies the maximum number of backup and archive jobs that NetBackup clients can perform concurrently. Default: 1 job. NetBackup can process concurrent backup jobs from different policies on the same client only if:

More than one storage unit available, or, one of the available storage units can perform more than one backup at a time. Maximum jobs per client
Client

Figure 7-31

Files that are on the same client but in different policies, can be backed up concurrently to different storage devices.

/home

Policy A

Tape Drive 1

/usr

Policy B Server

Tape Drive 2

You can specify any number of concurrent jobs within the following constraints:

Number of storage devices. 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

Host properties Master server, media server, and client host properties

437

it has drives. A disk storage unit is a directory on disk so the maximum number of jobs depends on system capabilities.

Server and client speed. 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.) 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).

Network loading. 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 backup 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.

Note: If online, hot catalog backups are scheduled to occur concurrently with other backups 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.

Maximum backup copies

The Maximum backup copies property specifies the total number of backup copies that may exist in the NetBackup catalog (2 through 10). NetBackup creates one of the following, whichever is smaller:

the number of copies that are specified under Multiple copies, or the number of copies that are specified as the Maximum backup copies property.

For more information about how to create multiple copies, see Multiple copies on page 131.

438 Host properties Master server, media server, and client host properties

Note: When configuring multiple copies for a relocation schedule, created as part of a disk staging storage unit the Maximum backup copies property must be set to include an additional copy beyond the number of copies to be created in the Multiple Copies dialog. For example, to create four copies in the Multiple Copies dialog, the Maximum Backup Copies property must be set to five or more.

Compress catalog interval

The Compress catalog interval property specifies how long NetBackup waits after a backup before it compresses the image catalog file.

Maximum vault jobs

The Maximum vault jobs 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. If the active vault jobs limit is reached, subsequent vault jobs are queued and their status is shown as Queued in the Activity Monitor. If a duplication job or eject job waits, its status is shown as Active in the Activity Monitor.

Administrator email address

The Administrator email address property specifies the address(es) where NetBackup sends notifications of scheduled backups or administrator-directed manual backups. The notification of offline, cold catalog backups includes the media ID that was used. To send the information to more than one administrator, separate multiple email addresses using a comma:

[email protected],[email protected]
Note: Disaster recovery information that is created during online, hot catalog backups is not sent to the addresses indicated here. DR information is sent to the address indicated on the Disaster Recovery tab in the catalog backup policy. .For more information, see Disaster Recovery tab on page 193.

Setting up email notifications

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

Host properties Master server, media server, and client host properties

439

NetBackup uses the mail transfer agent sendmail to send email notifications. If it is not installed, install it from sendmail.org and configure your environment accordingly so that it functions correctly. NetBackup can send notification to specified email addresses about backups on all client or specific clients. 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 host properties be configured with email addresses. (See Indicating email notification in the NetBackup host properties on page 439.)

Indicating email notification in the NetBackup host properties

Both methods work independently. If both methods are configured, the NetBackup global administrator receives emails about any failures and the NetBackup client administrator(s) receives emails about the clients where the client administrators email address is specified. To send messages only about backups with a non-zero status 1 2 3 4 5 Open the NetBackup Administration Console on the master server. Expand NetBackup Management > Host Properties > Master Server. Open the properties of the master server. 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 Client administrators email on page 481. Enable the Server sends mail option and click Apply.

To send messages to the global administrator about backups with a non-zero status 1 Open the NetBackup Administration Console on the master server.

440 Host properties Master server, media server, and client host properties

2 3 4 5

Expand NetBackup Management > Host Properties > Master Server. Open the host properties of the master server. Select 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] To send messages about all backups from a client 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 administrator after both successful and failed backups. 1 2 3 4 5 Open the NetBackup Administration Console on the master server. Expand NetBackup Management > Host Properties > Clients. Open the host properties for a client. Multiple clients can also be selected. 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 Client administrators email on page 481. Enable the Client sends mail option and click Apply.

Email contents
The following represents the contents of a notification email:
Backup on client hostname by root was partially successful. File list --------C:\Documents and Settings

Host properties Master server, media server, and client host properties

441

Logging properties
The Logging properties apply to currently selected master servers, media servers, and clients. The available properties differ between master servers, media servers, and clients. Figure 7-32 Logging host properties dialog box

Types of logging
The Logging properties contain the processes that continue to use legacy logging as well as processes that use unified logging.

Introducing unified logging

In unified logging, log file names and messages are created in a format that is standardized across all Symantec products. Some NetBackup processes on the server use unified logging. The unified logs are written to /usr/openv/logs (UNIX) and to install_path\NetBackup\logs (Windows). No subdirectories are necessary for the processes that use unified logging. The logging method for unified logging differs from the logging method for the processes that use legacy logging.

442 Host properties Master server, media server, and client host properties

For details on both unified and legacy logging, refer to the Using Logs and Reports chapter of the NetBackup Troubleshooting Guide. To control the size and number of unified logs, use the vxlogcfg and the vxlogmgr commands, as described in the NetBackup Troubleshooting Guide.

Legacy logging
For those processes that use legacy logging, you 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:

/usr/openv/netbackup/logs/process_name (UNIX)

install_path\NetBackup\logs\process_name (Windows)
/usr/openv/volmgr/debug (UNIX)

Create the Media Manager legacy log directories in:

install_path\Volmgr\debug (Windows)

For more information about legacy logs, see the NetBackup Troubleshooting Guide.

Enable robust logging

A check in the Enable robust logging checkbox indicates that when a log file grows to the maximum size, the log file is closed. Once 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 Enable robust logging is enabled: The log files for bprd, bpbkar, bpbrm, bpcd, bpdbm, bptm, and bpdm are named using the following convention: MMDDYY_NNNNN.log where NNNNN is an incrementing counter from 00001 - 99999 If Enable robust logging is disabled: A single log file is produced each day: MMDDYY.log Whether Robust Logging is selected or not, the log file is pruned 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 Robust Logging.

Host properties Master server, media server, and client host properties

443

Global logging level

The Global logging level 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. A value of 0 sets logging to minimum (default) and a value of 5 sets it to maximum. Caution: 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.

Process specific overrides

The following services use legacy logging. All services require that you first create a log directory in: /usr/openv/netbackup/logs/process_name

BPBRM logging level

If you want to override the Global logging level, select a logging level for bpbrm: 0 (minimum) through 5 (maximum).

BPTM logging level

If you want to override the Global logging level, select a logging level for bptm: 0 (minimum) through 5 (maximum).

BPDM logging level

If you want to override the Global logging level, select a logging level for bpdm: 0 (minimum) through 5 (maximum).

BPRD logging level

If you want to override the Global logging level, select a logging level for bprd: 0 (minimum) through 5 (maximum).

BPDBM logging level

If you want to override the Global logging level, select a logging level for bpdbm: 0 (minimum) through 5 (maximum).

444 Host properties Master server, media server, and client host properties

Vault logging level

If you want to override the Global logging level, select a logging level for bpvault: 0 (minimum) through 5 (maximum).

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: /usr/openv/logs To change the debug levels, use the vxlogcfg command. Please refer to the NetBackup Troubleshooting Guide for more information. The following sections describe the services that use unified logging.

Policy Execution Manager

If you want to override the Global logging level, select a logging level for the Policy Execution Manager (NBPEM): 0 (minimum) through 5 (maximum). Select No logging to produce no log for this service at all. The Policy Execution Manager compiles a worklist for jobs and determines when jobs are due to run. This property appears for EMM servers. This property does not appear for NetBackup hosts earlier than 6.0.

Job Manager
If you want to override the Global logging level, select a logging level for the Job Manager (NBJM): 0 (minimum) through 5 (maximum). Select No logging to produce no log for this service at all. The Job Manager accepts the jobs that the Policy Execution Manager (NBPEM) submits and acquires the necessary resources. This property appears for EMM servers. This property does not appear for NetBackup hosts earlier than 6.0.

Resource Broker
If you want to override the Global logging level, select a logging level for the Resource Broker (NBRB): 0 (minimum) through 5 (maximum). Select No logging to produce no log for this service at all. The Resource Broker makes the allocations for storage units, tape drives, client reservations. This property does not appears for NetBackup hosts earlier than 6.0.

Host properties Master server, media server, and client host properties

445

Lotus Notes properties

The Lotus Notes properties apply to currently selected clients running NetBackup for Lotus Notes. Figure 7-33 Lotus Notes host properties dialog box

The following topics explain the settings. For more information, see the NetBackup for Lotus Notes Administrators Guide.

Path
In the Path field, specify the path where the Lotus Notes program files reside on the client. NetBackup must know where these files are to perform backup and restore operations. The value in this box overrides the Lotus registry key, if both are defined.

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

446 Host properties Master server, media server, and client host properties

Media properties
The Media properties apply to selected master servers and media servers. Media properties control how NetBackup manages media. Figure 7-34 Media host properties dialog box

Allow media overwrite

The Allow media overwrite property overrides NetBackups 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. The following media formats on removable media can be selected to be overwritten:

ANSI: When ANSI is enabled, ANSI labeled media can be overwritten. AOS/VS: When AOS/VS is enabled, AOS/VS media can be overwritten. (Data General AOS/VS backup format.) CPIO: When CPIO is enabled, CPIO media can be overwritten. DBR: When DBR is enabled, DBR media can be overwritten. (The DBR backup format is no longer used.)

Host properties Master server, media server, and client host properties

447

RS-MTF1: Remote Storage MTF1 media format. When MTF1 is enabled, Remote Storage MTF1 media format can be overwritten. TAR: When TAR is enabled, TAR media can be overwritten. MTF: 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. BE-MTF1: When BE-MTF1 is enabled, Backup Exec MTF media can be overwritten.

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

If the volume is in the NetBackup media catalog and has been 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 NetBackup catalog, the backup is aborted and an error is logged. 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.

Enable SCSI reserve

The Enable SCSI reserve 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.

448 Host properties Master server, media server, and client host properties

SCSI reservations provide protection for NetBackup Shared Storage Option environments or any other multiple-initiator environment in which drives are shared. The following are the protection options:

SCSI persistent reserve. This 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. SPC-2 SCSI reserve. (The default option.) This option 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. No protection. 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.

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. For more information, see Configuring SCSI reserve on a drive path on page 605. Caution: 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.

Recommended use
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. Alternatively, the new SCSI persistent reserve method may be more effective in either of the following environments because it provides device status detection and correction:

You operate NetBackup media servers 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, usually you must reset the drive because the reservation owner is inoperative.)

Host properties Master server, media server, and client host properties

449

You want very high drive 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, you should thoroughly analyze your environment to ensure that all of your hardware supports SCSI persistent reserve correctly. Symantec recommends that you carefully consider all of the following factors before you use SCSI persistent reserve:

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 you use bridges in your environment, you should not use SCSI persistent reserve. If you have parallel SCSI buses, you should carefully consider the use of SCSI persistent reserve. Usually, parallel drives are not shared, so SCSI persistent reserve protection is not required. Also, parallel drives are usually on a bridge, and bridges do not support SCSI persistent reserve correctly. Therefore, if you use parallel SCSI buses in your environment, you should not use SCSI persistent reserve. You may have to configure your operating system tape drivers extensively to use SCSI persistent reserve. For example, if your tape drives do not support SPC-3 Compatible Reservation Handling (CRH), you must ensure that your operating system does not issue SPC-2 reserve and release commands.

If any of your hardware does not support SCSI persistent reserve, Symantec recommends that you do not use SCSI persistent reserve.

Allow multiple retentions per media

The Allow multiple retentions per media setting allows NetBackup to mix retention levels on tape volumes. It applies to media in both robotic drives and nonrobotic drives. By default, the check box is clear and each volume can contain backups of only a single retention level.

Allow backups to span tape media

The Allow backups to span tape media property, when checked, allows backups to span to multiple tape media. This property allows NetBackup to select another volume to begin the next fragment. The resulting backup has data fragments on more than one volume. By default, Allow backups to span tape media is checked and backups are allowed to span media.

450 Host properties Master server, media server, and client host properties

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.

Allow backups to span disk

The Allow backups to span disk property allows backups to span disk volumes when one disk volume becomes full. By default, this property is enabled. 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, AdvancedDisk, or SharedDisk volume spanning to another volume in the disk pool.

Notes on disk spanning

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. For more information on the storage unit multiplexing setting, see Enable multiplexing on page 230. 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

Check the Enable standalone drive extension property to allow NetBackup to use whatever labeled or unlabeled media is found in a nonrobotic drive. By default, stand-alone drive extensions are enabled.

Enable job logging

Check the Enable job logging property to allow the logging of the job information that the NetBackup Activity Monitor uses. By default, job logging occurs.

Enable unrestricted media sharing for all media servers

The Enable unrestricted media sharing for all media servers property controls media sharing, as follows:

Host properties Master server, media server, and client host properties

451

To allow all NetBackup media servers and NDMP hosts in your NetBackup environment to share media for writing, select this property. Do not configure server groups for media sharing. To restrict media sharing to specific server groups, clear this property, then configure media server groups and backup policies to use media sharing. To disable media sharing, clear this property and do not configure media server groups.

By default, media sharing is disabled. (The property is cleared and no server groups are configured.) For more information, see Configuring server groups for media sharing on page 615.

Media ID prefix (non-robotic)

The Media ID prefix (non-robotic) property specifies the media ID prefix to use in media IDs when unlabeled media is found 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. (Default: 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

The Media request delay 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 the dismount of one media and the mounting of another. Default: 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

452 Host properties Master server, media server, and client host properties

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 only once at 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, then waits 30 seconds and checks for ready the last time. If the delay had been 50 seconds (a short delay is not recommended), NetBackup would have checked only once, at the end of 50 seconds.

NDMP Global Credentials properties

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

To access the Add NDMP Host dialog, add a NDMP host under Media and Device Management > Credentials > NDMP Hosts.

Host properties Master server, media server, and client host properties

453

Figure 7-36

Add NDMP Host dialog box

Select on NDMP host for NDMP Global Credentials to apply

User name
The user name under which NetBackup accesses the NDMP server. This user must have permission to run NDMP commands.

Password and confirm password

Enter and re-enter the password.

NetWare Client properties

The Netware Client properties define NetBackup properties of NetWare clients. Netware Client properties include:

Client Settings (NetWare) properties on page 396 Open File Backup (NetWare client) properties on page 455

454 Host properties Master server, media server, and client host properties

Network properties
The Network properties apply to currently selected Windows clients. Figure 7-37 Network host properties dialog box

Under Network properties, set the properties that define requirements for communications between clients and the master server.

NetBackup client service port (BPCD)

The NetBackup client service port (BPCD) property applies to Microsoft Windows clients. The property specifies the port that the NetBackup client uses to communicate with the NetBackup server. Default: 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.

NetBackup request service port (BPRD)

The NetBackup request service port (BPRD) property applies to Microsoft Windows clients. The property specifies the port for the client to use when it sends requests to the NetBackup request service (bprd process) on the NetBackup server. Default: 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.

Host properties Master server, media server, and client host properties

455

Announce DHCP interval

The Announce DHCP interval property applies to Microsoft Windows clients. The property specifies how many minutes the client waits before it announces that a different IP address will 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.

Open File Backup (NetWare client) properties

The Open File Backup properties define Open File Backup properties on Netware clients.

Enable open file backup during backups

Check the Enable open file backup during backups check box to enable open transaction management.

456 Host properties Master server, media server, and client host properties

Port Ranges properties

The Port Ranges properties apply to selected master servers, media servers, and clients. Figure 7-38 Port Ranges host properties dialog box

NetBackup communicates between computers by using a combination of registered and dynamically allocated ports.

Registered 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 daemon (bpcd) is 13782. These ports are specified in a system configuration file: /etc/services Media Manager services include tape library control daemons, which accept connections from daemons on other servers that share the same library. See the services file on the media server to determine the ports that are required for a specific library. Dynamically-allocated 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 configure the following for dynamically-allocated ports:

Host properties Master server, media server, and client host properties

457

Whether NetBackup selects a port number at random or starts at the top of the range and uses the first one available. Whether connections to bpcd on a client use reserved or non-reserved ports.

Use random port assignments

The Use random port assignments property specifies how NetBackup communicates with NetBackup on other computers. This property specifies that NetBackup randomly chooses a port 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. By default, Use random port assignments is selected, and ports are randomly chosen. If this property is not selected, NetBackup chooses numbers sequentially. 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 port 5000 is free). If 5000 is in use, port 4999 is chosen.

Client port window

The Client port window property specifies the range of non-reserved ports on this computer that are used to connect to NetBackup on other computers. This setting applies when connecting to NetBackup on a computer that is configured to accept non-reserved ports. (See Allow non reserved ports on the Universal Settings dialog box.) To let the operating system determine the non-reserved port to use, enable Use OS selected non reserved port.

Client reserved port window

The Client reserved port window property specifies the range of reserved ports on this computer that are used for connecting to NetBackup on other computers. This setting applies when connecting to NetBackup on a computer that is configured to accept only reserved ports. (See Allow non reserved ports on the Universal Settings dialog box.) Default range: 512 through 1023. To let the operating system determine the non-reserved port to use, enable Use OS selected non reserved port.

458 Host properties Master server, media server, and client host properties

Server port window

The Server port window property specifies the range of non-reserved ports on which this computer accepts connections from NetBackup on other computers. This setting applies when connecting to a client configured to accept only non-reserved ports. (See Accept connections on non reserved ports on the Universal Settings dialog box.) Server port window does not appear in a client configuration. Default range: 1024 through 5000. To let the operating system determine the non-reserved port to use, enable Use OS selected non reserved port.

Server reserved port window

The Server reserved port window setting specifies the range of local reserved ports on which this computer accepts connections from NetBackup on other computers. This setting applies when connecting to a client configured to accept only reserved ports. (See Allow non reserved ports on the Universal Settings dialog box.) Server reserved port window does not appear in a client configuration. Default range: 512 through 1023. To let the operating system determine the non-reserved port to use, enable Use OS selected non reserved port.

Host properties Master server, media server, and client host properties

459

Restore Failover properties

The Restore Failover properties apply to selected master servers. Figure 7-39 Restore Failover host properties dialog box

The Restore Failover properties 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 for a restore. The automatic failover does not require administrator intervention. By default, NetBackup does not perform automatic failover. 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.

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:

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

460 Host properties Master server, media server, and client host properties

The media server is up and bpcd is running but bptm has problems. (For example, if vmd is down or bptm cannot find the required tape.)

Alternate restore failover machines list

The Media server column displays the NetBackup media servers that have failover protection for restores. The Failover restore server column displays the servers that provide the failover protection. NetBackup searches from top to bottom in the Failover restore server column until it finds another server that can perform the restore. 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.

Add button
To include a NetBackup media server in the Alternate restore failover machines list, click Add. To add or change a media server to the alternate restore failover machine list 1 To add an entry, click Add. The Add Failover Servers dialog box appears. To change an entry, click Change. The Change Failover Servers dialog box appears.

2 3

In the Media server field, specify the media server for failover protection. In the Failover restore servers field, specify the media server(s) to try if the server that is designated in the Server field is unavailable. Separate the names of multiple servers with a single space. Click Add to add the name to the list. The dialog box remains open for another entry. Click OK if an entry was changed. Click Close to close the dialog box. Click Apply to accept the Restore Failover property changes. Click OK to close the host properties dialog box.

Host properties Master server, media server, and client host properties

461

Stop and restart the NetBackup Request daemon on the master server where the configuration was changed.

For more information on failover, see Method 3: Automatic failover to alternate server on page 692.

Change button
To change an entry in the Alternate restore failover machines list, select a media server, then click Change.

Remove button
To remove a NetBackup media server from the Alternate restore failover machines list, select the media server to be removed, then click Remove.

Media server
Browse to a media server for which to configure a failover restore server(s).

Failover restore servers

Browse to another media server to serve as the failover server. Separate multiple server names with a single space.

462 Host properties Master server, media server, and client host properties

Retention Periods properties

The Retention Periods properties apply to selected master servers. Figure 7-40 Retention Periods host properties dialog box

The Retention period that is specified in a policy determines how long NetBackup retains the backups or archives created according to that schedule.The Retention period in a policy determines how long NetBackup retains the backups or archives created according to that schedule. Select from 25 levels of retention. The Retention Period properties define the length of time that is associated with each level.

Value
The Value specifies the retention level setting.

Units
The Units property specifies the units of time for the retention period. The list includes the special units, Infinite and Expires immediately.

Retention periods list

The dialog box contains a listing of the current definitions for the 25 possible levels of retention (0 through 24). The Schedule count column indicates how

Host properties Master server, media server, and client host properties

463

many schedules currently use each level. If the retention period is changed for a level, it affects all schedules that use that level.

Schedules list
The dialog box contains a list of the schedules that use the currently selected retention level, and the policy to which each schedule belongs.

Impact report button

Click Impact Report to display a summary of how changes affect existing schedules. The list displays all schedules in which the retention period is shorter than the frequency period. To change a retention period 1 In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Retention Periods. Select the retention level that you want to change.

Note: Level 9 cannot be changed and remains at a setting of infinite. The dialog box displays the names of all schedules that use the selected retention level as well as the policy to which each schedule belongs. 3 4 Type the new retention period in the Value box. Select the units of measure (days, weeks, months, years, infinite, or expires immediately).

Note: After Units or Value is changed, an asterisk (*) appears in the Changes Pending column to indicate that the period was changed. NetBackup does not change the actual configuration until Apply or OK is clicked. 5 Click Impact Report. The policy impact list displays the schedules where the new retention period is less than the frequency period. To prevent schedules from being listed, redefine the retention period for the schedules or change the retention or frequency for the schedule. To discard your changes, click Cancel. To save your changes and update the configuration, click one of the following:

6 7

464 Host properties Master server, media server, and client host properties

Apply: Saves the changes and leaves the dialog box open to make further changes. OK: Saves the changes since Apply was last clicked. OK also closes the dialog box.

To save the changes, click OK.

Note on redefining retention periods

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, it can result in backups with different retention periods being stored on the same volume. For example, if the retention period for level 3 is changed from 1 month to 6 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 about the same value. However, before a major change is made to a retention period, suspend the volumes that were previously used for that retention level. To suspend the volumes, use the following steps: 1 2 Use the NetBackup Media List report to determine which volumes are currently at the level to be suspended. Use the bpmedia command to suspend the volumes. bpmedia -suspend -m media_ID

Host properties Master server, media server, and client host properties

465

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. Figure 7-41 Servers host properties dialog box

Master server
The Master server property specifies the master server for the selected host. (The name of the selected host appears in the title bar.)

Additional servers
The Additional Servers list contains 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 add a server, click Add and select a server. To delete a server, select a server from the list, then click Remove.

466 Host properties Master server, media server, and client host properties

To change the master server, select another server from the list, then click Make Master.

To configure access to a remote server, add to the server list the name of the host seeking access. For more information, see To administer a remote master server on page 639.

Media servers
The Media servers list specifies that the listed machines are media servers only. Machines that are listed as media servers can back up and restore clients, but have limited administrative privileges.

To add a new media server, click Add and select a server. Run nbemmcmd -addhost to add a media server to the Enterprise Media Manager (EMM) database of existing master server. To delete a media server, select a media server from the list, then click Remove.

Restricting administrative privileges of media servers

The servers in the Media servers list are media servers only. (Host Properties > Master Server or Media Servers > Servers.) Machines that are listed as media servers can back up and restore clients, but have limited administrative privileges. Figure 7-42 Media Server list in Servers host properties dialog box

Administrative scope of media servers is limited

Host properties Master server, media server, and client host properties

467

Consider a configuration that consists of master server oak and two media serverselm and pine. Set up oak as the master server and elm and pine as media servers. If a machine is defined as both a master server and a media server, the master server entry takes precedence. A server that is listed as both a master and a media server has consequences. It allows a media server system administrator to be a NetBackup administrator on other master servers. Figure 7-43 Server that are listed as both media server and master server

A machine that is listed as both an additional server and a media server has full administrative privileges

Multiple masters that share one Enterprise Media Manager host

Multiple master servers can share one 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 EMM host. Access can be set using the Host Properties or configured in the bp.conf file.

A shared EMM database located on a master server

In the following example, three master servers share one EMM database that is located on one of the servers (meadow). The bp.conf server entries on each master server would read as described in the following table:

468 Host properties Master server, media server, and client host properties

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

Havarti
SERVER = havarti SERVER = meadow

Study
SERVER = study SERVER = meadow

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

SERVER entries:

The first SERVER entry must be the name of the master server. The following master servers also need to be listed: In order for the NetBackup Administration Console to administer other servers, the servers must be listed. (File > Change Server.) If the EMM database is on another master server, that server needs to be listed. The table shows how meadow is listed on havarti and study.

The EMMSERVER entry must be present on all master servers that share the EMM host. The table shows how meadow is listed as the EMMSERVER on havarti, study, as well as on meadow.

Host properties Master server, media server, and client host properties

469

A shared EMM database located on a media server

If the master server is changed on a media server, the EMM database also needs to be updated. 1 To modify the master server:

Select a server from the list. Click Make Master.

The server then appears as the new master.

To update the EMM database, after changing the master server for a media server, run: /usr/openv/netbackup/bin/admincmd/nbemmcmd -updatehost

470 Host properties Master server, media server, and client host properties

SharedDisk properties
The SharedDisk master server properties specify the SharedDisk storage option properties for your NetBackup configuration. Figure 7-44 SharedDisk host properties dialog box

SharedDisk mount points directory

The SharedDisk mount points directory specifies the directory on each storage server (that is, media server) where NetBackup mounts the volumes on the disk array. The mount point must be the same on all NetBackup media servers that access the array. The default mount point directory is nbshareddisk. If you back up a media server that uses mount points to any disk storage that contains backup images, do not cross mount points. (The policy Cross mount points attribute specifies whether to cross mount points.) If the policy crosses mount points, the NetBackup backup images that reside on that disk storage are backed up. The NetBackup BasicDisk disk type and the Enterprise Disk Option disk types use mount points for disk storage.

Host properties Master server, media server, and client host properties

471

SharePoint 2003 properties

The SharePoint 2003 properties apply to currently selected Windows 2003 clients to protect SharePoint 2003 installations. Figure 7-45 SharePoint 2003 host properties dialog box

User ID
Specify the user id for the account to use to log on to SharePoint (DOMAIN\user name).

Password
Specify the password for the account.

Consistency check before backup

Select what kind of consistency checks to perform on the SQL Server databases before NetBackup begins a backup operation. These checks are performed for both server- and user-directed backups. None: No consistency check is performed. Full check, excluding indexes: Select this property 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

472 Host properties Master server, media server, and client host properties

index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Fullcheck, including indexes: Include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only): Select this property to perform a low overhead check of the physical consistency of the SQL Server 2000 database. This property checks the integrity of the physical structure of the page and of record headers. It also checks the consistency between the pages object ID and index ID and the allocation structures.

Continue with backup if consistency check fails

Select whether or not the backup should continue if the consistency check fails.

SharePoint Hosts properties

Special configuration is required to allow NetBackup to restore SQL databases to the correct hosts in a farm. In the SharePoint Hosts properties, add each host in the farm. Figure 7-46 SharePoint Hosts host properties dialog box

Use the Add button to add a host that is authorized to run restores on SharePoint component hosts. Provide the name of the Farm front-end host and the name of the Farm component host in the farm.

Host properties Master server, media server, and client host properties

473

Symantec Products properties

The Symantec Products properties apply to currently selected master servers. Figure 7-47 Symantec Products host properties dialog box

The Symantec Products properties include the subnode, Backup Exec Tape Reader properties on page 375.

474 Host properties Master server, media server, and client host properties

Timeouts properties
The Timeouts properties apply to selected master servers, media servers, and clients. Figure 7-48 Timeouts host properties dialog box

Client connect timeout

The Client connect timeout property specifies the number of seconds the server waits before timing out when it connects to a client. Default: 300 seconds.

Backup start notify timeout

The Backup start notify timeout property specifies the number of seconds the server waits for the bpstart_notify script on a client to complete. Default: 300 seconds. Note: If this timeout is changed, verify that Client read timeout is set to the same or higher value.

Host properties Master server, media server, and client host properties

475

File browse timeout

The File browse timeout property specifies how 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 File browse timeout is exceeded, the user receives a socket read failed error even if the server is processing the request.

Use OS dependent timeouts

The Use OS dependent timeouts property specifies that the client waits for the timeout period as determined by the operating system when it lists files:

Windows client: 300 seconds UNIX client: 1800 seconds

Media mount timeout

The Media mount timeout property specifies how long NetBackup waits for the requested media to be mounted, positioned, and ready on backups, restores, and duplications. The Media mount timeout property appears only as a master server property. Use this timeout to eliminate excessive waiting time during manual media mounts. (For example, when robotic media is out of the robot or if off site.) While restoring backups or any archives that were written to a disk that Storage Migrator manages, the media mount timeout value is in effect during the caching of potentially migrated files. Allow adequate time to cache the entire disk file if it is part of a large disk image that Storage Migrator has migrated to tape.

Client read timeout

The Client read timeout property specifies the number of seconds to use for the client-read timeout on a NetBackup master, remote media server, or database-extension client (such as NetBackup for Oracle). Default: 300 seconds. 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 because database backup utilities frequently start several backup jobs at the same time, slowing the central processing unit. The sequence on a database-extension client is as follows:

476 Host properties Master server, media server, and client host properties

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.

Note: For database-extension clients, Symantec suggests that the Client read timeout be set to a value greater than 5 minutes. 15 minutes is adequate for many installations. For other clients, change Client read timeout only if problems are encountered.

Backup end notify timeout

The Backup end notify timeout property specifies the number of seconds that the server waits for the bpend_notify script on a client to complete. Default: 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

The Media server connect timeout property specifies the number of seconds that the master server waits before timing out when connecting to a remote media server. Default: 30 seconds.

Host properties Master server, media server, and client host properties

477

Universal Settings properties

The Universal Settings properties apply to selected master servers, media servers, and clients. Figure 7-49 Universal Settings host properties dialog box

Restore retries
The Restore retries setting specifies the number of attempts a client may try to restore after a failure. (Default: 0; the client does not attempt to retry a restore. The client may try up to 3 times.) Change Restore retries only if problems are encountered. A checkpointed job is retried from the start of the last checkpointed file rather than at the beginning of the job. If a job fails after the maximum number of retries, the job goes into the incomplete state. The job remains in the incomplete state as determined by the Move restore job from incomplete state to done state property. Checkpoint Restart for restores allows a NetBackup administrator to resume a failed restore job from the Activity Monitor. For more information, see Move restore job from incomplete state to done state on page 385.

478 Host properties Master server, media server, and client host properties

Browse timeframe for restores

The Browse timeframe for restores property 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 checkbox, then 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

The Last full backup property indicates whether NetBackup include 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. (Default: enabled.)

Use specified network interface

The Use specified network interface property specifies the network interface that NetBackup uses to connect to another NetBackup client or server. A NetBackup client or server can have more than one network interface. To force NetBackup connections to be made on a specific network interface, use this entry to specify the network host name of that interface. By default, the operating system determines the one to use.

Example 1 - client with multiple network interfaces.

Assume a NetBackup client with two network interfaces:

One network interface is for the regular network. The host name for the regular interface is fred. One network interface is for the backup network. The host name for the backup interface is fred_nb.

The NetBackup client name setting on both the client and server is fred_nb. When client fred starts a backup, restore, or list operation, the request goes out on the fred_nb interface and over the backup network. The operation assumes that fred and the network are set up to do so. If this configuration is not in place, fred can send out the request on the fred interface and over the regular network. The server receives the request from client fred_nb with host name fred and refuses it because the host and the client names do not match.

Host properties Master server, media server, and client host properties

479

One solution is to set Use specified network interface on fred to fred_nb. All backup, restore, and list requests use the fred_nb interface. The server receives requests from client fred_nb with host name fred_nb and everything works as intended. Another solution is to set up the master server to allow redirected restores for client fred. Redirected restores allow the server to accept the request, but leaves NetBackup traffic on the regular network.

Example 2 - server with multiple network interfaces.

Assume a NetBackup server with two network interfaces:

One network interface is for the regular network. The host name for the regular interface is barney. One network interface is for the backup network The host name for the backup interface is barney_nb

The server list on all NetBackup servers and clients have an entry for barney_nb. When barney connects to a client for a backup, the request goes out on the barney_nb interface and over the backup network. The operation assumes that barney and the network are set up to do so. If this configuration is not in place, barney can send out the request on the barney interface and over the regular network. The client now receives the request from barney rather than barney_nb and refuses it as coming from an invalid server. One solution is to set Use specified network interface on barney to barney_nb. Now, when barney connects to a client, the connection is always through the barney_nb interface and everything works as intended. Another solution is to add an entry for barney to the server list on the client. The client now accepts requests from barney, but NetBackup traffic continues on the regular network.

Use preferred group for enhanced authorization

The Use preferred group for enhanced authorization property specifies the domain group name that this computer passes to the server when NetBackup-user authorization is used. However, NetBackup encourages the use of Symantec Product Authentication and Authorization for NetBackup Access Control (NBAC) instead of legacy security implementations. For information about the Use preferred group for enhanced authorization property, see the NetBackup 6.0 documentation. For information on Symantec Product Authentication and Authorization, see the NetBackup Security and Encryption Guide.

480 Host properties Master server, media server, and client host properties

Allow server file writes

The Allow server file writes property 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. Once the Allow server file writes property is applied, it can be cleared only by modifying the client configuration. Default: server writes are allowed.

Logging the status of a redirected restore

When performing a redirected restore, no progress log is produced if the requesting server is not included in the server list for the server that performs the 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. Consider the following solutions:

To produce a progress log, add the requesting server to the server list: log into the requesting server. In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Servers. Add the restoring server to the server list. Log in to the restoring server. Check the Activity Monitor to determine the success of the restore operation.

Accept connections on non reserved ports

The Accept connections on non reserved ports property specifies whether the NetBackup client service (bpcd) can accept remote connections from nonprivileged ports. (Nonprivileged ports have port numbers 1024 or greater.) (Default: enabled.) If this property is enabled, the server that connects to the host must also be configured to use non-reserved ports for the client. Select Accept connections from non reserved ports on the server properties Client attributes tab. For more information, see Maximum data streams on page 387. If the property is disabled (unchecked), bpcd requires remote connections to come from privileged ports. (Privileged ports have port numbers less than 1024.) Accept connections on non reserved ports is useful when NetBackup clients and servers are on opposite sides of a firewall. When disabled, the source ports for connections to bpcd use reserved ports as well.

Host properties Master server, media server, and client host properties

481

Enable performance data collection (Windows server only)

The Enable performance data collection property specifies whether NetBackup updates disk and tape performance object counters. (Applies only to Windows master and media servers. The NetBackup performance counters can be viewed using the Windows Performance Monitor utility (perfmon). (Default: enabled.)

Client sends mail

The Client sends mail property specifies whether the client sends an email to the address that is specified in the Universal Settings properties. If the client cannot send email, select Server sends mail. (Default: enabled.)

Server sends mail

The Server sends mail setting 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. (Default: disabled.)

Client administrators email

The Client administrator's email property 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. To ensure that the system is set up to send mail, see Setting up email notifications on page 438.

482 Host properties Master server, media server, and client host properties

UNIX Client properties

The UNIX Client properties define NetBackup properties of UNIX clients. Figure 7-50 UNIX Client host properties dialog box

UNIX Client properties include:

Client Settings (UNIX) properties on page 397 Busy File Settings properties on page 380 Lotus Notes properties on page 445

Host properties Master server, media server, and client host properties

483

UNIX Server properties

The UNIX Server properties apply to selected UNIX master servers. Figure 7-51 UNIX Server host properties dialog box

NFS access timeout

The NFS access timeout property specifies how long the backup waits to process the mount table before it considers an NFS file system unavailable. Default: 5 seconds.

484 Host properties Master server, media server, and client host properties

VMWare Proxy Servers properties

The VMWare Proxy Servers properties appear if the Snapshot Client license is installed. The properties apply to currently selected master servers. Figure 7-52 VMWare Proxy Servers host properties dialog box

Click Add to add a server to the Proxy Server list. To delete a server from the list, select the server and click Delete. A VMWare proxy server is a server on the same SAN as a VMware ESX server that can access the snapshot of the VMware Virtual Machine and provide access to the files for third-party backup vendors. For more information, see the NetBackup Snapshot Client Administrators Guide.

Host properties Master server, media server, and client host properties

485

VSP (Volume Snapshot Provider) properties

The VSP properties apply to currently selected supported Windows clients. Figure 7-53 Volume Snapshot Provider host properties dialog box

In order for the properties in this dialog box to affect client(s), VSP must be selected as the snapshot provider for the client(s). VSP is the default Windows snapshot provider. Snapshots are a point-in-time view of a source volume. NetBackup uses snapshots to access busy or active files during a backup job. To make VSP the snapshot provider for a Windows client, select: NetBackup Management > Host Properties > Master Servers > Select master server for the client > Client Attributes > Windows Open File Backup tab > Use Veritas Volume Snapshot Provider (VSP). For more informations, see Client Attributes properties on page 386.

VSP overview
NetBackup uses VSP to back up open and active files on Windows 2000, Windows XP, and Windows Server 2003 (32- and 64-bit) clients. For VSP to back up open and active files, VSP first captures a snapshot of each volume to be

486 Host properties Master server, media server, and client host properties

backed up. A virtual drive is created that represents a static copy of the volume at a point-in-time. A corresponding VSP cache file is also created. NetBackup backs up files using the virtual drive instead of the actual drive. For each volume snapshot, a VSP cache file is created to maintain the integrity of the snapshot. The cache file stores the original data that reflects the changes that occurred during the backup. The cache file is created along with the volume snapshot. VSP is similar to OTM (used in previous releases) in that VSP creates volume snapshots using a caching mechanism. However, consider the following points when using VSP:

VSP uses a cache file for each volume that requires a snapshot, while OTM uses only one cache for all snapshots. Using VSP, a snapshot of a volume cannot be created if the volume already contains a VSP cache file. Using VSP, a cache file cannot be placed on a volume that has had a snapshot taken. Or, a cache file cannot be placed on a volume that is in the process of having a snapshot taken of it. Only when the snapshot for the volume has been destroyed can it be used as a location for a VSP cache file. All VSP cache files are placed at the root level of a volume and are removed when its VSP snapshot has been destroyed. VSP cannot be used to perform hot database backups. For more informations, see Using VSP with databases on page 492.

Stepping through the backup process with VSP

The following steps describe the sequence of events during a backup using VSP: 1 Before the backup begins, NetBackup uses VSP to create snapshots for the backup job. NetBackup waits for a quiet period to occur when no writes are performed on the drives that contain data to be backed up. This wait is required to ensure that the file system is in a consistent state. The Busy file timeout property defines the length of the quiet period. If a quiet period of sufficient length does not occur within the Busy file timeout period, the backup proceeds without VSP. If a quiet period of sufficient length is detected, NetBackup performs the actions necessary to record the VSP snapshot. The backup begins and NetBackup starts to read the data from the client. If an application requests a read or write during the backup, VSP reads or writes the disk. VSP may read or write its cache as necessary to maintain the snapshot and provide accurate data to the application.

2 3

Host properties Master server, media server, and client host properties

487

Once the backup completes, NetBackup attempts to destroy the VSP volume snapshots that were created for the backup job. It attempts to destroy the VSP snapshots while deleting the VSP cache files for the volume snapshots.

Logging VSP messages

VSP snapshot activity is logged in the bpfis debug log. To enable VSP logging, create the bpfis directory in the following location (default): C:\Program Files\VERITAS\NetBackup\Logs\ If you want, specify a different location during client installation. To create detailed log information, set the Global logging level to a higher value in the master server host property Logging dialog box. (Host Properties > Master Servers > Selected master server > Logging.) Eventually, the bpfis directory can require extensive disk space. Delete the directory when the troubleshooting is complete and reset the Global logging level to a lower value. For more informations, see Global logging level on page 443.

Cache file volume list

The Cache file volume list serves as a list of preferred locations for NetBackup to place VSP cache files. List volumes as drive letters, separated by commas and spaces. For example: C, D, E All backup jobs that require VSP snapshots place the VSP cache files in a volume that is listed in the Cache file volume list. If multiple volumes are listed, the volume with the most free disk space at backup time is the preferred location. If no volumes are listed, NetBackup determines the best location for VSP cache files. The cache files are placed on a listed volume unless NetBackup determines that the volumes are undesirable as cache file locations. NetBackup may make this determination, even if a location is user-specified. A location is undesirable if a volume in the list is also targeted as a snapshot. Because VSP does not allow snapshots of the volumes that contain active cache files, NetBackup does not allow other VSP cache files to be placed in the volume. Assume that a job backs up the C and D volumes and needs to create VSP volume snapshots for the volumes. The Cache file volume list points to the C volume as the preferred location for all backups to place the VSP cache files: 1 2 NetBackup uses VSP to create VSP snapshots for the C and D volumes. NetBackup places the VSP cache files for the C and D snapshots in the C and D volumes. The C volume cannot be used as a preferred location for VSP snapshots since it is having a VSP snapshot created for it.

488 Host properties Master server, media server, and client host properties

Subsequent backups cannot use C as a VSP cache file location until the VSP volume snapshots that are created in step 2 have been destroyed.

VSP volume exclude list

The VSP volume exclude list contains the volumes that are excluded from snapping by VSP during backups. The volumes in the list will never contain VSP cache files. Volumes in the VSP volume exclude list are excluded from VSP activity and are backed up without snapshot protection. List volumes as drive letters, separated by commas and spaces. For example: C, D, E

Ramifications of the precedence of the volume list over the exclude list
The volumes in the Cache file volume list have precedence over the volumes that are listed in the VSP volume exclude list. The Cache file volume list overrides the VSP volume exclude list if both lists contain the same volume. For example, C:\ is specified in the Cache file volume list and in the VSP volume exclude list. The user prefers the C:\ volume as the location for VSP cache files, yet would not like VSP to snap or place cache files on the volume. Because the Cache file volume list takes precedence over the VSP volume exclude list, NetBackup places cache files in C:\ even though it is listed in the VSP volume exclude list. NetBackup does not create snapshots for C:\ until C:\ is removed from the VSP volume exclude list.

Using the cache file volume list and VSP volume exclude list for multiple simultaneous backup jobs or multiple groups of multistreamed jobs
NetBackup allows a scheduled backup to be broken into several backup streams that can run simultaneously to increase performance. For more information, see Allow multiple data streams on page 112. If a backup policy is configured to allow multiple data streams, a scheduled client backup can be divided into multiple data streams. Each file list directive in the policy forms a separate backup job (stream) that runs concurrently with other streams to help complete the scheduled backup. All backup jobs (streams) in a policy are grouped into an entity that is called a stream group. All backups that are part of a stream group share their VSP volume snapshots between backup jobs in the stream group. Additionally, multiple backup jobs could also run concurrently on a single client even if a backup policy is configured not to allow multiple data streams. For both types of backups, use the Cache file volume list and VSP volume exclude list to make sure that VSP snapshot creation is successful. To run these backups, Symantec recommends that a volume be listed in both the Cache file volume list and the VSP volume exclude list. This volume is effectively used as

Host properties Master server, media server, and client host properties

489

the volume for all VSP cache files. However, VSP snapshots are not created for it. All backups for the volume do not have VSP snapshots enabled.

Example 1: Running multiple simultaneous backups with VSP

Assume that two backup jobs run simultaneously. Both jobs back up the C and D volumes on a client that contains only volumes C and D: 1 Place either the C or D volume in the Cache file volume list and the VSP volume exclude list. For this example, the D volume has been placed in the Cache file volume list and the VSP volume exclude list. Both backup jobs are run simultaneously, both backing up the C and D drives. Snapshots of the C drive are created successfully for both backup jobs while their cache files were placed in the D drive. Since the D drive was listed in both the Cache file volume list and the VSP volume exclude list, VSP cache files for the C drive for both backup jobs were placed in the D drive. Both backup jobs also backed up the D drive without VSP.

2 3

If the D drive was not listed in the Cache file volume list and the VSP volume exclude list, VSP would not have been enabled for the C and D drives for both backup jobs.

Example 2: Running multiple groups of multistreamed backups simultaneously with VSP

Assume two multistreamed policies contain the following file lists: Policy 1: C:\ Dir1 D:\ Dir2 Policy 2: C:\ Dir3 D:\ Dir4 When both policies are run simultaneously, two groups of multistreamed backup jobs run. (Each group runs a backup job for each file list item.). Both groups of multistreamed jobs back up the C and D volumes on a client that contains only volumes C and D: 1 Place either the C or D volume in the Cache file volume list and the VSP volume exclude list. For this example, the D volume has been placed in the Cache file volume list and the VSP volume exclude list. Both policies are run simultaneously. Two groups of multistreamed jobs both run at the same time and back up the C and D drive contents. Snapshots of the C drive are created successfully for both groups of multistreamed jobs while their cache files were placed in the D drive. Since

2 3

490 Host properties Master server, media server, and client host properties

the D drive was listed in both the Cache file volume list and the VSP volume exclude list, VSP cache files for the C drive for both groups of multistreamed jobs were placed in the D drive. Both groups of multistreamed jobs also backed up the D drive without VSP. If the D drive was not listed in the Cache file volume list and the VSP volume exclude list, VSP would not have been enabled for the C and D drives for both groups of multistreamed jobs.

Customize cache size

The Customize cache size property enables a number of properties that help you set specific cache size characteristics for your backup configuration. If the Customize cache size property is not enabled, NetBackup will automatically size VSP cache files for the client. By default, the Customize cache size property is disabled to allow NetBackup to calculate cache file sizes for VSP snapshots. However, if the cache file sizes need to be configured manually, the Customize cache size property can be disabled. The VSP cache file sizes can be adjusted manually.

Cache size in % of disk space

The Cache size in % of disk space property specifies that the Cache size and Maximum cache size properties use percentage of disk space as the form of measurement.

Cache size in megabytes

The Cache size in megabytes property specifies that the Cache size and Maximum cache size properties use megabytes as the form of measurement.

Cache size
The Cache size property specifies the initial size of the VSP cache file that is allowed for snapshots.

Maximum cache size

The Maximum cache size indicates how large the VSP cache file may grow to hold snapshots. This property is only applicable when the VSP cache file is placed on a volume that is not to be snapped. When the VSP cache file is placed on a volume that is not to be snapped, the cache file size begins at 0 megabytes. It can grow to the size indicated by the Maximum cache size. The Maximum cache size is the percentage of free disk space on the cache file volume, based on the value that is specified in Maximum cache size. If the form of measurement is Cache size in MB, the Maximum cache size is calculated in megabytes.

Host properties Master server, media server, and client host properties

491

If the Customize cache size property is disabled, NetBackup determines the Maximum cache size for the VSP snapshot if the cache file is placed in a volume that is not to be snapped. The following items are VSP best practices to configure VSP cache sizes:

Disable Customize cache size to allow NetBackup to determine cache file sizes for VSP snapshots. NetBackup allocates as much cache space as possible when it creates VSP snapshots. In most cases, when NetBackup sizes cache files, it avoids VSP snapshot errors. In some cases, VSP snapshot errors could occur, even if Customize cache size is disabled. It depends on the data that is backed up and the I/O activity of the backup client. If snapshot errors occur when Customize cache size is disabled, increase the Cache size and Maximum cache size to fit the clients installation. The recommended setting for the Cache size is 30% of the used disk space of the snapshot volume. The cache file size is the Cache size value if the VSP cache file is placed in the same volume as what is snapshot. Otherwise, it is ignored. The recommended setting for Maximum cache size is 95% of free disk space of the cache file volume. The cache file begins at 0 MB and grows until the Maximum cache size is reached if the cache file is placed on a volume other than the snapshot volume. Otherwise, it is ignored. Use caution to configure the cache file sizes manually. The sizes are used regardless of the sizes of the volumes that are backed up. If there is not enough space that is allocated, the backup job could fail with a VSP error.

VSP and interaction with virus scanners

Virus scanners can cause VSP snapshots to be intermittently deleted and their cache files to fail after NetBackup backup jobs complete successfully. NetBackup offers the following features to allow users to exclude VSP snapshots and cache files from virus scanning activity:

VSP cache files are created in VSP cache file directories named NBU_VSP_Cache. For example, D:\ NBU_VSP_Cache Exclude directories are created from virus scanning activity if VSP snapshot deletion failures occur. The directories are named NBU_VSP_Cache. VSP cache files are named with a .VSP extension. Exclude files with .VSP extensions from virus scanning activity if VSP snapshot deletion failures occur.

Busy file wait

The Busy file wait property specifies how long VSP waits for a quiet period (quiesce wait time) before a snapshot is created. A quiet period is a time during

492 Host properties Master server, media server, and client host properties

which no file write-activity occurs on the drive being snapped using VSP. (Default: 5 seconds.) A value less than 5 seconds is not recommended because the data that is backed up as a result of a low setting may become corrupted.

Busy file timeout

The Busy file timeout property specifies how long VSP should wait for a quiet period to occur. If this time expires, the backup proceeds without VSP. (Default: 300 seconds.)

Using VSP with databases

Consider the following information regarding using VSP (Volume Snapshot Provider) to back up and restore databases. Some database vendors provide a formal application program interface specifically designed for use with backup products. Symantec works with many database vendors to ensure that these interfaces are stable, efficient, and reliable when used with NetBackup and NetBackup database extension features. Many of these APIs were jointly developed to ensure that data is protected and can be restored when needed. Oracle, Microsoft (SQL Server, Exchange), IBM (Lotus Notes, DB2), NCR (Teradata), Sybase, and Informix are examples of the database vendors that provide an API for use with backup products. Symantec recommends using the NetBackup database extension features when a backup API is available and when a database needs to be backed up in a hot mode.

Databases with an API

Hot backups are performed on active databases. Use a formal API to create a confident backup and the ability to perform a successful restore. Symantec does not recommend using VSP for hot backups of these databases. Cold or inactive backups of these databases may be possible with VSP, but success varies with each database vendor. Contact the specific database vendor to identify the recommended method for database backup where data reliability is ensured. Database programs recover from a point-in-time restore differently. If the data does not conform to the backup specification that is designed into the database product, the integrity of the database is questionable.

Databases without an API

For the databases that do not have a backup and restore API, use VSP to back up the databases when they are inactive (cold). For databases with no Veritas database extension product, shut down the database and perform a file system level or cold backup. If the databases cannot be backed up cold and the only option is a hot backup, set Busy file wait to 5 seconds. If the file system does not achieve a quiescent or

Host properties Master server, media server, and client host properties

493

an inactive state, NetBackup does not perform the VSP snapshot. NetBackup does not fail the backup when a quiescent state is not achieved. Instead, NetBackup continues the backup as if VSP is not in use. The result is that NetBackup skips open, active, or locked files. The backup job ends with an exit status code 1. Status code 1 indicates that the backup job was completed but not all files were successfully backed up. If VSP is used to back up database environments, first back up the data and make sure that the backup exited with a Status 0. Then, restore the database and confirm the integrity of the data and the functionality of the database. Using VSP to back up active databases without using a formal API presents risk. Customers should contact the database supplier to ensure support of database backups using point-in-time technology. Also, significant back up and restore testing should be performed to assure database availability and reliability.

494 Host properties Master server, media server, and client host properties

Windows Client properties

The Windows Client properties define NetBackup properties for Microsoft Windows clients. Figure 7-54 Windows Client host properties dialog box

Windows Client properties include:

Client Settings (Windows) properties on page 402 Exclude Lists properties on page 414 VSP (Volume Snapshot Provider) properties on page 485 Network properties on page 454 Lotus Notes properties on page 445 Exchange properties on page 412

Chapter

Device Monitor
Use Media and Device Management > Device Monitor to manage tape drives, device paths, and service requests for operators. For more information, see the following:

Changing the operating mode of a drive on page 495 Resetting a drive on page 496 Managing drive paths on page 497 Managing pending requests and actions on page 497 Freezing media or downing drives on page 501 Cleaning drives on page 502 Adding or changing a drive comment on page 504 Viewing drive details on page 504

Changing the operating mode of a drive

Usually, you do not have to change the operating mode of a drive. NetBackup sets the drive state (UP in AVR mode, the default mode) when you add drives to your configuration. Other operating mode settings are used for special purposes. To change the mode of a drive 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive Status pane, select a drive or select multiple drives.

2 3

496 Device Monitor Resetting a drive

From the Actions menu, choose the command for the new drive operating mode. Up Drive, Operator control applies only to stand-alone drives. If the drive is configured with multiple device paths or is a shared drive (Shared Storage Option), a dialog box appears. The dialog box contains a list of all device paths to the drive. Select the path to change. To change multiple paths, select multiple paths.

Resetting a drive
Resetting a drive changes the state of the drive. Usually, you reset a drive when its state is unknown, which can occur 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 an SCSI reservation exists on the drive, a reset operation from that host that owns the reservation may help the SCSI reservation. If the drive is:

In use by NetBackup, the reset action fails. Not in use by NetBackup, NetBackup attempts to unload the drive and set its runtime attributes to default values.

Note: A drive reset does not perform any SCSI bus or SCSI device resets. To reset a drive 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive status pane, select a drive or select multiple drives. Select Actions > Reset Drive.

2 3 4

If the drive is in use by NetBackup and cannot be reset, you can restart the NetBackup Job Manager, which should free up the drive. 1 2 Determine which job controls the drive (that is, which job writes to or reads from the drive). In the NetBackup Administration Console, select NetBackup Management > Activity Monitor.

Device Monitor Managing drive paths

497

3 4

From the Jobs tab, cancel the job. Restart the NetBackup Job Manager using the Activity Monitor. Caution: When you restart the NetBackup Job Manager, it cancels all NetBackup jobs in progress.

Managing drive paths

A Drive Paths pane in the NetBackup Administration Console Device Monitor 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)

You can change the operating mode of a drive path or reset a drive path. To manage drive paths 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive Paths pane, select a path or select multiple paths. From the Actions menu, choose a command for the path action, as follows:

2 3 4

Up Path Down Path Reset Path

Managing pending requests and actions

If a tape mount requires a specific volume, the request is displayed in the Pending Requests pane of the Device Monitor window. For example, if NetBackup requires a specific volume for a restore operation, NetBackup loads or requests the volume. The Pending Requests pane appears only if requests await action or when NetBackup acts on a request. After all requests have been resolved (automatically by NetBackup or manually by operator intervention), the Pending Requests pane disappears. If NetBackup cannot service a media-specific mount request automatically, it changes the request or action to a pending state, as follows:

498 Device Monitor Managing pending requests and actions

Pending requests. When NetBackup cannot move a required volume into a tape drive automatically, NetBackup sets the request status to pending. Operator assistance is required to complete the request, and NetBackup displays the request in the Pending Requests pane. NetBackup assigns pending status to a mount request when it cannot determine which:

Stand-alone drive to use for a job. Drive in a robot is in AVR mode.

Pending actions. A tape mount requests becomes a pending action when the mount operation encounters problems, and the tape cannot be mounted. Operator assistance is required to complete the request, and NetBackup displays an action request in the Pending Requests pane. Pending actions usually occur with drives in robotic libraries. Resolving a pending request Resolving a pending action Resubmitting a request Denying a request

The following are the actions you can perform on pending requests and actions:

Pending requests for storage units

The following tape mount requests do not appear in the Device Monitor Pending Requests pane:

For backups When a tape is required as the target of a duplication operation

Such requests are for resources in a storage unit and therefore are not for a specific volume. If the storage unit is not available, NetBackup tries to select another storage unit that has a working robot. If NetBackup cannot find a storage unit for the job, NetBackup queues the job (a Queued state is displayed in the Activity Monitor). If a robot must be operated in manual mode, you can configure NetBackup so that storage unit mount requests are displayed in the Device Monitor. To do so, set the robot to operate in Pend If Robot Down (PIRD) mode by using the tpconfig command. Pending requests appear in the Device Monitor, and you can assign these mount requests to drives manually. NetBackup does not assign a mount request for one storage unit to the drives of another storage unit automatically. Also, you cannot reassign the mount request to another storage unit. For more information about the tpconfig command, see NetBackup Commands for UNIX and Linux.

Device Monitor Managing pending requests and actions

499

Resolving a pending request

A pending request is a request for a tape mount that NetBackup cannot service automatically. Operator assistance is required to complete the request To resolve a pending request, first insert the requested volume in a drive that matches the density of the volume that was requested. Second, use the NetBackup Administration Console to assign the request to that drive. ACS robots only: If a request is pending because the Library Storage Module (LSM) in which the media resides is offline, no operator action is required. NetBackup retries such requests hourly until the LSM is online. NetBackup reports the LSM offline status in the Job Details dialog box. Open the Job Details dialog box from the Jobs tab in the Activity Monitor. To assign a pending request to a drive 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Pending Requests pane, select the request. Also, note the contents of the following columns of the request:

2 3

Density to determine the recording density that is required. External Media ID to determine the ID of the volume that is required. Mode to determine whether the volume should be write-enabled.

4 5 6 7 8 9

In the Drive Status pane, find a drive type that matches the density for the pending request. Verify that the drive is up and not assigned to another request. Select the drive. NetBackup Enterprise Server only: Ensure that the drive and the pending request are on the same host. If necessary, get the media, write-enable it, and insert it into the drive. Wait for the drive to become ready, as explained in the vendors drive equipment manual.

10 Select Actions > Assign Request. 11 Verify that the request was removed from the Pending Requests pane. 12 In the Drive status pane, verify that:

The job request ID appears in the Request ID column for the drive

500 Device Monitor Managing pending requests and actions

The User column is not blank

Resolving a pending action

When a tape mount request encounters problems and the tape cannot be mounted, NetBackup changes the mount request to a pending action. Operator assistance is required to complete the request, and NetBackup displays an action request in the Pending Requests pane. Pending actions usually occur with drives in robotic libraries. For pending actions, NetBackup determines the cause of the problem and issues instruction to the operator to resolve the action. A pending action is similar to a pending request. A media icon identifies a pending action; the icon appears to the left of the request ID. The icon includes a human hand, which depicts that a manual action is required. To resolve a pending action 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Pending Requests pane, select the pending action. Select Actions > Display Pending Action (or double-click on the pending action). A message box that describes the problem and a list of possible corrective actions appears. The message box also shows other information, such as user name, recorded media ID, external media IDs, and drive number. Click OK after viewing the corrective actions. Correct the error condition and either resubmit the request or deny the request.

2 3 4

5 6

Resubmitting a request
After you correct the problem or problems with a pending action, you can resubmit the request. If the problem is a volume missing from a robot, first locate the volume, insert it into the robot, and then update the volume configuration. Usually, a missing volume was removed from a robot and then requested by NetBackup. For more information, see Inventory a robot on page 547.

Device Monitor Freezing media or downing drives

501

To resubmit a request 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Pending Requests pane, select the request. Select Actions > Resubmit Request. The pending action message is removed from the Pending Requests pane and the operation proceeds.

2 3 4

Denying a request
Some situations may require you to deny requests for service. For example, when a drive is not available, you cannot find the volume, or the user is not authorized to use the volume. When you deny a request, NetBackup sends an appropriate status message to the user. To deny a request 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Pending Requests pane, select the request. Select Actions > Deny Request.

2 3 4

The request is removed from the Pending Requests pane.

Freezing media or downing drives

If repeated read or write failures occur on the media in a tape drive or on the drive itself, NetBackup freezes the media or downs a device automatically. 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. Repeated write failures are usually the cause for setting a volume to the FROZEN state or a device to DOWN. A volume is also set to FROZEN if the write failure makes future attempts at tape positioning unreliable. Common reasons for write failures are dirty write heads or old media.

502 Device Monitor Cleaning drives

The following are the default values for the error thresholds:

The media error threshold is 2 (that is, NetBackup freezes media on the third media error in 12 hours). The drive error threshold is 2 (that is, NetBackup downs a drive on the third drive error in 12 hours). The time window for errors is 12 hours.

You can use the NetBackup nbemmcmd command with the -media_error_threshold, -drive_error_threshold, and -time_window options to change the default values. For more information about nbemmcmd, see NetBackup Commands for UNIX and Linux. To reverse a freeze action

Use the bpmedia command to unfreeze the volume.

To reverse a down action

Use the NetBackup Device Monitor to set the device to Up.

Cleaning drives
You can perform an operator-initiated cleaning of a drive regardless of the cleaning frequency or accumulated mount time of the drive. You can clean a stand-alone drive or a robotic drive if appropriate cleaning media are added to the EMM database. You can also use the Device Monitor to:

Reset the mount time of the drive. You should reset the mount time to zero after you perform a manual cleaning. Set the cleaning freqency. Automatic, frequency based drive cleaning is configured when you add a drive to NetBackup. If you use the Device Monitor to set the cleaning frequency, NetBackup updates the cleaning frequency value for the drive.

For more information, see Drive cleaning overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II To clean a drive 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab.

Device Monitor Cleaning drives

503

3 4

In the Drive Status pane, select the drive to clean. From the Actions menu, select Clean Now. NetBackup initiates drive cleaning regardless of the cleaning frequency or accumulated mount time. Clean Now 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.

Shared drive (Shared Storage Option): In the list of hosts that share the drive, you can choose only one host on which the function applies. The Clean Now function may take several minutes to complete, so the cleaning information in the Drive Details dialog may not be updated immediately. To reset the mount time 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive Status pane, select a drive. From the Actions menu, select Reset Mount Time. The mount time for the selected drive is set to zero.

2 3 4

Shared drive (Shared Storage OptionShared Storage Option): In the list of hosts that share the drive, you can choose only one host on which the function applies. To set cleaning frequency 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive Status pane, select a drive. From the Actions menu, select Set Cleaning Frequency. Enter a time (hours) or use the arrow controls to select the number of mount hours between each drive cleaning. Cleaning Frequency is not available for the robots that do not support frequency-based cleaning. This function is not available for shared drives.

2 3 4 5

The drive cleaning interval is displayed in the Drive Details dialog (Actions > Drive Details).

504 Device Monitor Adding or changing a drive comment

Adding or changing a drive comment

You can add a comment that describes how a drive is used or change an existing comment. Drive comments appear in the Drive Status pane. To add or change a drive comment 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive status pane, select a drive or select multiple drives. Select Actions > Change Drive Comment. The dialog shows the current comment (if any is currently configured). For a shared drive (Shared Storage Option), 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. Enter a comment or change the current drive comment. For a list of allowable characters, see NetBackup naming conventions on page 631. Click OK.

2 3 4 5

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. To obtain drive details 1 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed, the Device Monitor pane includes both a Drives tab and a Disk Pools. If necessary, select the Drives tab. In the Drive Status pane, select a drive. Select Actions > Drive Details. The following applies only to NetBackup Enterprise Server.

2 3 4

Device Monitor Viewing drive details

505

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.

506 Device Monitor Viewing drive details

Chapter

Media
Use Media and Device Management > Media to add and manage media (tape volumes) to NetBackup. The media can already reside in a storage devices, or you can add them to your storages devices when you add them to NetBackup. For information about how to manage media in NetBackup and the logical entities that help you manage volumes, see the following:

Volume operations on page 507 Volume pool operations on page 538 Volume group operations on page 542

For information about how to inventory robots and how to update the NetBackup volume configuration with media changes in the robots, see the following:

Robot inventory operations on page 544

If you have volumes without barcodes to manage, see Using the physical inventory utility on page 572. If you have WORM media, see Using WORM media on page 589. To import Backup Exec volumes, see Importing NetBackup or Backup Exec images on page 336.

Volume operations
Volumes are units of data storage or cleaning capability on removable media (tapes or optical platters). NetBackup assigns IDs and other attributes to the media. NetBackup uses the attributes to track and manage the media. Attributes include the media ID, robot host, robot type, robot number, and slot location. Volume information is stored in the EMM database. The following are operations you can perform on volumes:

Adding volumes on page 508

508 Media Volume operations

Changing volume properties on page 517 Changing the volume pool of a volume on page 519 Changing the volume group of a volume on page 519 Changing the owner of a volume on page 520 Freezing and unfreezing media on page 520 Suspending and unsuspending media on page 521 Labeling media on page 521 Rescanning and updating barcodes on page 523 Moving volumes on page 524 Erasing media on page 528 Injecting and ejecting volumes on page 529 Deleting volumes on page 532 Deassigning volumes on page 533 Exchanging volumes on page 535 Recycling volumes on page 537

Adding volumes
Several methods exist to add new volumes to NetBackup, as follows:

Adding volumes by using the Volume Configuration Wizard on page 511 Adding volumes using a robot inventory update on page 511 Adding volumes using the Actions menu on page 512 Adding volumes overview on page 508 About labeling NetBackup volumes on page 510

To help you determine which method to use, review the following information:

Note: When you add a new volume, a volume expiration date is not assigned.

Adding volumes overview

Which method you use to add volumes can depend on where they reside and how they are used:

Robotic volumes on page 509 Stand-alone volumes on page 509

Media Volume operations

509

NetBackup catalog backup volumes on page 510 About labeling NetBackup volumes on page 510

Robotic volumes
Robotic volumes are volumes located in a robot. The easiest way to add robotic volumes is to use the Volume Configuration Wizard. However, you can use the other methods.

Stand-alone volumes
Stand-alone volumes are volumes located in a drive that is not in a robot. To determine a method for adding stand-alone volumes, review the following:

The easiest way to add stand-alone volumes is to use the Volume Configuration Wizard. NetBackup assigns media IDs and labels the volumes automatically. Because NetBackup does not label volumes until it uses them, you can add a range of volumes. Then, when NetBackup requests one of the volumes, you can insert it into the stand-alone drive and NetBackup labels it. You can also add volumes by inserting the media into a stand-alone drive and by using Media and Device Management in the NetBackup Adminstration Console. NetBackup assigns media IDs and labels the volumes automatically. NetBackup uses the volume if a volume of that type is required for a backup. The DISABLE_STANDALONE_DRIVE_EXTENSIONS option of the nbemmcmd command can turn off NetBackups automatic use of stand-alone volumes. For more information, see NetBackup Commands for UNIX and Linux. You can add additional stand-alone volumes to the NetBackup configuration even though they do not reside in the drive. The additional volumes are available for use if the volume in the drive becomes full or unusable. First, use the NetBackup bplabel command to label the volume and assign a media ID. Second, follow the instructions in Adding volumes using the Actions menu on page 512. For more information, see NetBackup Commands for UNIX and Linux. Even if you use NetBackups assignment capabilities to add stand-alone volumes, you may prevent out of media errors by adding extra stand-alone volumes manually. For example, if a volume in a stand-alone drive is full or unusable because of errors, NetBackup ejects (logically) the volume. If you added another stand-alone volume, NetBackup requests that volume and does not generate an error.

510 Media Volume operations

NetBackup catalog backup volumes

To add NetBackup catalog backups, you can use any of the methods. Ensure that you assign them to the volume pool you use for catalog backups. After you add volumes, use the NetBackup Catalog Backup wizard to configure a catalog backup policy.

About labeling NetBackup volumes

When NetBackup labels media, it writes a record on the media; the record (or label) includes the NetBackup media ID. Normally, NetBackup controls the labeling of its volumes and in most cases performs this operation automatically as follows:

If a volume in a robot has not been labeled, NetBackup labels it the first time it is used for a backup. A volume is labeled unless it was last used for NetBackup catalog backups or it contains data from another recognized application. Recognized applications include Symantec Backup Exec and Veritas Storage Migrator. To label such media, see Labeling media on page 521. NetBackup uses a default prefix of the letter A when it assigns media IDs to volumes without barcodes (for example, A00001). To change this default, use the MEDIA_ID_PREFIX configuration option in the vm.conf file. If the robot supports barcodes, by default NetBackup generates media IDs for new volumes. The last six characters of the barcode are used for the ID. To change this default action, you can specify and select specific characters using Media ID generation rules (see Media ID Generation tab on page 565). To change this default action, you can specify and select specific characters by using Media ID generation rules (see Media ID Generation tab on page 565). An optical disk platter must be formatted, have an external media ID, and have a volume label before you can use it with NetBackup. Use the Media portion of the NetBackup Administration Console orvmadm. If you prefer to assign specific media IDs, label them by using the NetBackup bplabel command and then add them using the manual update procedure.

Prelabeling media
It may be beneficial to prelabel media for the following reasons:

A successful label operation validates that the media is usable, compatible, and is not write-protected. The recorded label may assist with media management if:

Media Volume operations

511

The media is misplaced, The barcode label or external label is gone or damaged, You use the physical inventory utility (vmphyinv) to manage media.

Adding volumes by using the Volume Configuration Wizard

Use this wizard to do the following:

Inventory robots. An inventory operation:

Identifes media in a robot (including new media in an existing robot) Adds that media to the NetBackup configuration

Add volumes for stand-alone drives. Update the Enterprise Media Manager (EMM) database.

After the wizard configures media, each media has a unique media ID in the EMM database. The wizard uses the default media type for the drive to create the media type. Review the limitations in the wizard help before you configure volumes. To start the Volume Configuration Wizard

In the NetBackup Administration Console, select Media and Device Management > Configure Volumes.

Adding volumes using a robot inventory update

A robot inventory update generates media IDs for new volumes as follows:

If the robot supports barcodes and the new volumes have readable barcode labels, NetBackup generates media IDs based on one of the following:

The last six characters of the barcodes ( the default method). New volumes are assigned a media type, volume pool, maximum number of mounts (or maximum cleanings), and description. For more information, see Barcode Rules tab on page 562. The characters that you specify if you use media ID naming rules.

If the robot does not support barcodes or the volumes do not have readable barcodes, media IDs are based on a prefix that you specify.

For procedures, see Robot inventory operations on page 544. To add volumes using a robot inventory update 1 2 Insert the volume(s) into the robotic library. In the NetBackup Administration Console, select Media and Device Management > Media > Robots.

512 Media Volume operations

3 4 5 6 7 8

Select the robotic library where you inserted the volume. Select Actions > Inventory Robot. In the Inventory Robot dialog, select Update volume configuration. For more options, click Advanced Options. To clear any previous display in the Results section, click Clear Results. Click Start to start the update.

Adding volumes using the Actions menu

Note: Symantec recommends using the Volume Configuration Wizard or a robot inventory to add volumes. To add volumes using the Actions menu 1 2 3 4 For new volumes in a robotic library, insert them into the proper slots. In the NetBackup Administration Console, select Media and Device Management > Media. Select Actions > New > Volumes. In the Add Volumes dialog, specify the attributes for the volumes. For descriptions of the properties, see Volumes properties on page 513. Note: 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. The Apply button adds the volume without closing the dialog or refreshing the display. You can add another volume by modifying the dialog contents and then click Apply or OK. If the robot has a barcode reader, NetBackup does the following:

Adds the volume to the EMM database using the specified media ID. Reads the barcode of each new volume. Adds the barcodes as attributes in the EMM database.

Media Volume operations

513

Volumes properties
The following sections describe the properties you can configure when you add volumes.

Device host
NetBackup Enterprise Server only. Specifies the name of the device host where the robot is defined.

First media ID
Appears only if the number of volumes or platters is more than one. When you add a range of volumes, specifies the ID of the first volume in the range of volumes. Media IDs can be from 1 to 6 characters in length. Use the same pattern that you chose in the Media ID naming style box. Using the pattern, NetBackup names the remaining volumes by incrementing the digits. For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

First slot number

To add new volumes in a robot, you must specify the first slot number to use for the range of volumes. NetBackup assigns the remainder of the slot numbers sequentially.

514 Media Volume operations

Note: You cannot enter slot information for volumes in an API robot. The robot vendor tracks the slot locations for API robot types.

Label optical media

Before using optical volumes for backups, they must be formatted and labeled. NetBackup labels media when you add it. If you need to format your optical media, refer to the tpformat command in NetBackup Commands for UNIX and Linux. The following are the label options:

Yes, but do not overwrite old labels (the default) Yes, overwrite as needed No

Maximum mounts/maximum cleanings

For a backup volume, specify the maximum number of times NetBackup should mount the volumes. 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 your vendor documentation for information on the expected life of the volume. For a cleaning tape, specify the number of cleanings that can be performed. The number must be greater than zero. For more information, see Drive cleaning overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II

Media ID naming style

Appears only if the number of volumes or platters is more than one. Select 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 barcode on the media. For API robots, NetBackup supports barcodes from 1 to 6 characters. Therefore, you must obtain a list of the barcodes before you add the volumes. You can obtain this information through a robotic inventory or from the robot vendors software.

Media Volume operations

515

For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

Media ID
Specifies 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 barcode on the media (for API robots, NetBackup supports barcodes from 1 to 6 characters). Therefore, you must obtain a list of the barcodes before you add the volumes. You can obtain this information through a robotic inventory or from the robot vendors software. For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

Media type
For optical disk volumes that are supported on UNIX and Linux only. Media type specifies the media type for the volume to add.

Media description
Enter a description of the media, up to 25 character maximum. For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

Number of volumes / Number of platters

Specifies the number of volumes to add. For a robotic library, enough slots must exist for the volumes.

Partner ID
Optical media only. Specify a partner ID for optical media. The partner ID is media ID of the volume on the other side of the optical platter.

Robot
Specifies the robotic library to add the volumes to. To add volumes to a different robot, select a robot from the list. The list shows robots on the selected host that can contain volumes of the selected media type. To add volumes to a stand-alone drive, select Standalone.

Volume group
The volume group shows the location of the volume. The location can be either the robot in which the volume resides, stand-alone, or off-site if you use the NetBackup Vault option.

516 Media Volume operations

If you specified a robot, you can 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):

Stand-alone volumes are not assigned to a volume group. NetBackup generates a name for robotic volumes 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.

Rules for assigning volume groups The following are the rules for assigning volumes to 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 NetBackup generate a name. The only way to clear a volume group name is to move the volume to stand-alone 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 stand-alone volume group. All members of a group must be in the same robotic library or be stand-alone. That is, you cannot add a group (or part of a group) to a robotic library if it already exists in another robotic library.

For more information, see Volume pool and volume group overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II

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.

Volume pool
The pool to which the volume or volumes should be assigned. You can 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.

Media Volume operations

517

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. For more information, see Volume pool and volume group overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II

Changing volume properties

You can change some of the properties of a volume, including the volume pool. To change volume attributes 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes pane, select a volume or volumes. Select Edit > Change. In the Change Volumes dialog, change the attributes for the volume. For descriptions of the properties, see Change Volumes properties on page 518.

518 Media Volume operations

Change Volumes properties

The following sections describe the volume properties you can change.

Description
Specifies how the selected volumes are used or any other relevant information about the volumes. For information about the characters you can use in a name, see NetBackup naming conventions on page 629.

Expiration date
Does not apply to cleaning tapes. Specifies the age of the volume and is 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. When you add a new volume, a default expiration date is not added. 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.

Media Volume operations

519

Maximum mounts
Does not apply to cleaning tapes. 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 your vendor documentation for information on the expected life of the volume.

Number of cleanings remaining

Cleaning tapes only. Specifies 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.

Volume pool
Does not apply to cleaning tapes. The pool to which the volume or volumes should be assigned. You can 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.

For more information, see Volume pool and volume group overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II

Changing the volume pool of a volume

A volume pool is a property you can change by using the Change Volumes dialog box. For procedures, see Changing volume properties on page 517.

Changing the volume group of a volume

The volume group shows the location of the volume. The location can be either the robot in which the volume resides, stand-alone, or off-site if you use the NetBackup Vault option.

520 Media Volume operations

If you move a volume physically to a different robot, you must change the group of the volume to reflect the move. To change the volume group 1 2 3 4 5 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes list, select the volumes that you want to change the volume group assignment for. Select Actions > 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 tree pane.

Changing the owner of a volume

The media owner defines who can write to the volume. The volume must be assigned and owned (that is, it must contain valid backup images) before you can change the owner. To change the owner of a volume 1 2 3 4 5 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes list, select the volume that you want to change. Select Actions > Change Media Owner. In the Media Owner field, select the new owner, either a media server or server group. Click OK.

For more information about server groups, see Configuring server groups for media sharing on page 615.

Freezing and unfreezing 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.

Media Volume operations

521

A frozen volume is available for restores. If the backups have expired, you must import the backups first. To freeze or unfreeze media 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes list, select the volume that you want to freeze or unfreeze. Select Actions > Freeze or Actions > Unfreeze. In the dialog box, click OK.

Suspending and unsuspending media

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, you must import the backups first. To suspend or unsuspend media 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes list, select the volume that you want to freeze or unfreeze. Select Actions > Suspend or Actions > Unsuspend. In the dialog box, click OK.

Labeling media
When NetBackup labels media, it writes a record on the media; the record (or label) includes the NetBackup media ID. Normally, NetBackup controls the labeling of its volumes and in most cases performs this operation automatically. However, media are not labelled automatically if:

They were last used for NetBackup catalog backups. They contain data from a recognized non-NetBackup application and NetBackup is configured to prohibit media overwrite for that media type. If NetBackup has not assigned them If they contain no valid NetBackup images

You can label these media manually as follows:

522 Media Volume operations

If a volume has valid NetBackup images, you can deassign the volume so you can label it. For more information, see Deassigning volumes on page 533. If you want to label media and assign specific media IDs (rather than allow NetBackup to assign IDs), use the bplabel command. Caution: If you label a volume, NetBackup cannot restore or import the data that was on the media after you label it.

Caution: For many types of drives, you may not be able to cancel a label job from the Activity Monitor. For more information, see About labeling NetBackup volumes on page 510. To label media 1 2 3 4 5 6 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes pane, select a volume or the volumes that you want to label. If you select multiple volumes, they all must reside in the same robot. Select Actions > Label. In the Label dialog, specify the properties for the label operation. For descriptions of the properties, see Label properties on page 523. Click OK. In the warning dialog, 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.

Media Volume operations

523

Label properties
The following sections describe the properties you can specify for a label operation.

Media server
The name of the media server that controls the drive to write the label.

Verify label before performing operation

Select this option to verify that the media in the drive is the media expected. To overwrite any existing labels on the media, do not select Verify media label before performing operation. 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.

Rescanning and updating barcodes

Use Rescan/Update Barcodes to read the barcodes on volumes in robotic libraries and to update the EMM database with the contents of the robotic library. Note: Rescan/Update Barcodes does not apply to volumes in API robot types.

When to rescan and update

Use Rescan/Update Barcodes only to add the barcodes that are not in the EMM database. For example, if you add a new volume to your configuration but do not insert the tape into the robotic library at that time, NetBackup does not add the barcode to the database. You can use this command to add the barcode after you insert the tape into the robotic library.

When not to rescan and update

Do not use Rescan/Update Barcodes to correct the reports that show a media ID in the wrong slot. To correct that problem, you must do one of the following:

Logically move the volume by selecting a volume and by using Actions > Move. Logically move the volume by using an Update volume configuration operation. See Update volume configuration on page 553. Physically move the volume into the correct slot.

524 Media Volume operations

To obtain an inventory of the robot without updating the barcode information in the database, select Show contents in the Robot Inventory dialog. See Show contents on page 551 for more information.

Rescanning/updating barcodes
To check barcodes and update the EMM database 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Media > Robots. Select the robotic library that contains the volumes that you want to scan and update. In the Volumes pane, select the volumes. Select Actions > Rescan/Update Barcodes. A dialog appears that shows the volumes you selected for the rescan operation. Click Start to continue or Close to quit. If you select Start, the results of the update are displayed in the output section of the dialog.

Moving volumes
When you move volumes in or out of a robotic library or from one robot to another, you must move the volumes physically and logically:

Physically move volumes by inserting or by removing them. For some robot types, you can 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, you must do the following:

Move the volumes to stand-alone as an intermediate step Move the volumes to the new robotic library Move single volumes Move multiple volumes Combinations of single and multiple volumes Move volume groups

You can perform the following types of logical moves:

You cannot move volumes to an invalid location (for example, move DLT media to an 8-mm robot).

Media Volume operations

525

Symantec recommends that you perform moves by selecting and by moving only one type of media at a time to a single destination.

Move examples
The following are several examples of when to move volumes logically:

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, and then configure a new volume for the empty slot or move an existing volume into that slot. You can 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 using the robot inventory update option

Use the following procedure:

To move volumes within a robot. The robot must have a barcode reader and the volumes must have readable barcodes. To remove volumes from a robot. You can use this procedure even if the volumes do not have barcodes or if the robot does not have a reader.

To move volumes using a robot inventory update 1 2 3 4 Physically move the volumes to their new location. Select Actions > Inventory Robot. In the Robot Inventory dialog, select Update volume configuration. Select other options as appropriate. For more information, see Robot inventory operations on page 544.

Moving volumes using the Actions menu

If you move a volume to a robotic library that has a barcode reader, NetBackup updates the EMM database with the correct barcode. To move volumes using the Actions menu 1 Physically move the volumes to their new location.

526 Media Volume operations

2 3 4 5

In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes pane, select the volumes that you want to move. Select Actions > Move. In the Move Volumes dialog, specify the properties for the move. For descriptions of the properties, see Move Volumes properties on page 526. Note: If you move a single volume, the dialog entries show the current location of the volume.

Move Volumes properties

The following sections show the properties you can configure in the Move Volumes dialog.

Device host
Specifies the name of the device host where the robot is defined. For single volumes, the current location of the volume is displayed. NetBackup Enterprise Server only: To select a robot on another device host, select from the list of device hosts shown.

Media Volume operations

527

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.

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. For single volumes, the current location of the volume is displayed.

Volume group
Enter or select the volume group to assign to the volumes. If you leave the volume group blank:

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. The new volume group must be for the type of volumes as you are moving. 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 groupm 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 a it) to a robotic library.

The following are the rules for moving volumes between groups:

Volume is in a robotic library

To inject a volume into a robotic library, select Volume is in a robotic library.

528 Media Volume operations

You can select a robot (see Robot) and the slot number for the volume (see First slot number). 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 shows the media IDs of the volumes that you selected to move. If you selected one side of an optical disk platter, that side is shown but both sides are moved.

Erasing media
Caution: If you erase media, NetBackup cannot restore or import the data on the media. You can erase the data on volumes as follows:

If NetBackup has not assigned them If they contain no valid NetBackup images

After the media is erased, NetBackup writes a label on the media. If a volume has valid NetBackup images, you can deassign the volume so you can label it. For more information, see Deassigning volumes on page 533. The following are the erase options:

SCSI long erase rewinds the media and the data is overwritten with a known data pattern. An SCSI long erase is also called a secure erase because it erases the recorded data completely. Caution: A long erase is a time-consuming operation and can take as long as 2 hours to 3 hours. For example, it takes about 45 minutes to erase a 4-mm tape on a stand-alone 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 may 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.

Media Volume operations

529

Note: NetBackup does not support erase functions on NDMP drives. To erase media 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Media. In the volumes pane, select a volume or volumes that you want to erase. If you selected multiple volumes, they must all be in the same robot For a short erase, select Actions > Quick Erase. For a long erase, select Actions > Long Erase. In the erase dialog, specify the name of the media server 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. Click OK. A dialog warns you that this action is irreversible. Click OK if you are certain you want to start the erase action. A dialog reminds you to use the Activity Monitor to view the progress and status of the action. 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. Use the Activity Monitor to view the status of the action.

5 6

Caution: For many types of drives, you may not be able to cancel a label or erase media job from the Activity Monitor.

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 front-panel inject and 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 your library to understand the media access port functionality. Libraries such as the ones noted may not be fully compatible with the inject and eject features of NetBackup unless properly handled. Other libraries may not be compatible at all.

530 Media Volume operations

See the following related topics for more information:

Injecting volumes on page 530 Ejecting volumes on page 530 Media ejection timeout periods on page 532

Injecting volumes
Inject volumes into the robots that have media access ports by loading the volumes in the MAP and then inventory the robot. Select Empty media access port prior to update on the Robot Inventory dialog box. 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 have been 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 have media access ports. For instructions, see Update volume configuration on page 553.

Ejecting volumes
You can eject single or multiple volumes. You cannot eject multiple volumes if they reside in multiple robots. Operator intervention is only required if the robotic library does not have a media access port large enough to eject all of the selected volumes. For these robot types, NetBackup prompts an operator to remove the media from the media access port so the eject operation can continue. For more information about eject, see Media ejection timeout periods on page 532. To eject volumes 1 2 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes pane, select one or more volumes that you want to eject.

Media Volume operations

531

Select Actions > Eject Volumes From Robot.

The Eject Volumes dialog box has two tabs, described as follows.

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 two classes of errors can occur:

For serious errors, the Eject button is not active; you must correct the error before you can eject the media. For other errors, the Errors tab shows an explanation of the error. You may continue the eject action (select Eject) or exit (select Close) depending on the type of error.

5 6

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

532 Media Volume operations

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. The following table shows the ejection timeout periods for robots. Robot types
Automated Cartridge System (ACS) Tape Library Multimedia (TLM) Tape Library 8MM (TL8) Tape Library DLT (TLD) Tape Library Half-inch (TLH) None. The robot allows an unlimited Applies only to period to remove media. NetBackup Enterprise Server. 30 minutes.

Timeout period
One week

Note
Applies only to NetBackup Enterprise Server.

Caution: If media is not removed and a timeout condition occurs, the media is returned to (injected into) the robot. You should inventory the robot and then eject the media that was returned to the robot. Some robots do not have 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.

Deleting volumes
You can delete volumes from the NetBackup configuration. 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.

Media Volume operations

533

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. NetBackup and Storage Migrator volumes have an extra safeguard against accidental deletion. You cannot delete such volumes if they are still assigned. To deassign a volume, see Deassigning volumes on page 533. To delete a volume group, see Deleting a volume group on page 544. To delete volumes 1 2 In the NetBackup Administration Console, select Media and Device Management > Media. In the Volumes pane, select the volumes that you want to delete. Note: You cannot delete any assigned volumes until any application (NetBackup or Storage Migrator) using them deassigns them. 3 4 Select Edit > Delete. In the Delete Volumes dialog, click OK. Note: If you selected only one side of an optical platter, the volume on other side is also deleted. 5 Remove the deleted volumes from the storage device.

Deassigning volumes
An assigned volume is one that is reserved for exclusive use by NetBackup or Veritas Storage Migrator (but not both). A volume is set to the assigned state when either applications first starts using it to store data. The time of the assignment appears in the Time Assigned column for the volume in the Volumes pane. When a volume is assigned, you cannot delete it or change its volume pool. A volume remains assigned until NetBackup or Storage Migrator deassigns it. 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 when you stop using it for catalog backups.

534 Media Volume operations

To determine which application currently uses a volume, check the Application column of the Volumes pane.

Deassigning NetBackup volumes

Caution: Symantec recommends that you do not deassign NetBackup volumes manually. If you do, be certain that the volumes do not have any important data. If you are uncertain, copy the images to another volume before you deassign the volume. The procedure depends on whether the volume is a data backup volume or catalog backup volume. See the following two sections for instructions.

Deassigning NetBackup regular backup volumes

NetBackup deassigns a regular backup volume when the retention period for all backups on the volume expire. You can expire the backups on a volume by using the bpexpdate command on the master server. 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. If you expire the backup images on a volume, NetBackup does not erase those images. You can still use the data on the volume by importing the backups into NetBackup (if the volume has not been overwritten). To import backup images, see Importing expired images on page 341 or Importing images from Backup Exec media on page 342. You can expire backups regardless of the volume state (Frozen, Suspended, and so on). The bpexpdate command is located in the following directory:

install_path\NetBackup\bin\admincmd (Windows)
/usr/openv/netbackup/bin/admincmd (UNIX)

The following is the format of the bpexpdate command:

bpexpdate -d 0 -m media id [-host hname]

media id is the media ID to be expired. hname is the name of the NetBackup media server (or SAN media server) where the media ID was written. NetBackup Enterprise Server only: specify hname only if your configuration uses master servers and media servers. The following example assumes only one NetBackup server exists and expires all the backups on media ID ABC001:
bpexpdate -d 0 -m ABC001

Media Volume operations

535

Deassigning NetBackup catalog backup volumes

NetBackup tracks catalog backup volumes separately from regular backup volumes. To deassign these volumes, specify the CatalogBackup volume pool. NetBackup can reuse the volume, you can delete it, or you can change its volume pool.

Deassigning Veritas Storage Migrator volumes

If a volume is assigned to Veritas Storage Migrator, you must wait for Storage Migrator to deassign it. Storage Migrator deassigns a volume when the images are no longer required. If you try to deassign Storage Migrator volumes manually, data may be lost. For more information on how Storage Migrator manages its volumes, see the Storage Migrator System Administrators Guide for UNIX.

Exchanging volumes
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 allowable number of mounts. Old (past the expiration date). Unusable (for example, because of repeated media errors).

The following are procedures for exchanging volumes, depending on whether you want to reuse the old media ID or not.

Exchanging a volume and using a new media ID

Use this procedure when:

The volume contains current and valid NetBackup images. You require slots in the robotic library for additional backups, duplications, vault functions, or other purposes.

To exchange a volume and use a new media ID 1 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. See Moving volumes on page 524.

536 Media Volume operations

Add a new volume or move an existing volume in as a replacement for the volume you removed. 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). See Adding volumes on page 508. Physically replace the old volume. Do not delete the volume entry for that media ID in case you need to retrieve the data on the volume.

Exchanging a volume and using the old media ID

This procedure allows you to 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. Caution: If you exchange a media ID for a volume that has unexpired backup images, serious operational problems and a possible data loss may occur. To exchange a volume and use the old media ID 1 Delete the volume entry and physically remove the old volume from the storage device. See Deleting volumes on page 532. Physically add the new volume to the storage device. Logically add the new volume to the NetBackup volume configuration and specify the same attributes as the old volume, including the old media ID. See Adding volumes on page 508. Set a new expiration date for this volume. See Changing volume properties on page 517. Optionally, relabel the volume. Although you do not have to relabel the volume, the relabel 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. See Labeling media on page 521.

2 3

4 5

Media Volume operations

537

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

Recycling volumes using the existing media ID

NetBackup recycles a volume and return it to the volume rotation when the when the last valid image expires. To recycle a volume that contains unexpired backup images, you must deassign the volume. For procedures, see Deassigning volumes on page 533.

Recycling volumes 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 barcodes on the volume. 1 2 3 4 5 Physically remove the volume from the storage device. If the volume is in a robotic library, move it to stand-alone. See Moving volumes on page 524. Record the current number of mounts and expiration date for the volume. Delete the volume entry. See Deleting volumes on page 532. Add a new volume entry and physically add the volume to the storage device. See Adding volumes on page 508. Set the maximum mounts to a value that is equal to or less than the value calculated as follows: value = (number of mounts that the manufacturer recommends) - (the value that you recorded in step 3) Because NetBackup sets the mount value to zero for new volume entries, you must adjust the value to account for previous mounts. Set the number of mounts to the value you recorded in step 3 by using the following command:

538 Media Volume pool operations

/usr/openv/volmgr/bin/vmchange -m media_id -n number_of_mounts 8 Set the expiration date to the value you recorded in step 3. See Changing volume properties on page 517.

Volume pool operations

NetBackup groups volumes that are used for the same purpose into volume pools. A volume pool protects them from access by unauthorized users, groups, or applications. When you add media to NetBackup, you assign them to one of the volume pools (or assign them as stand-alone volumes, without a pool assignment). During installation, NetBackup creates the following volume pools:

NetBackup. The default pool to which all backup images are written (unless you specify otherwise). DataStore, for DataStore use. CatalogBackup, for NetBackup catalog backups. None, for the volumes that are not assigned to a pool. On UNIX media servers, NetBackup also creates a pool for Veritas Storage Migrator volumes.

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 add 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. See Scratch pool on page 541. The following are volume pool operations:

Adding a new volume pool on page 539 Changing the properties of a volume pool on page 539 Deleting a volume pool on page 542

For more information, see Volume pool and volume group overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II For more information about WORM media, see Using WORM volume pools to manage WORM media on page 590.

Media Volume pool operations

539

Adding a new volume pool

Use the following 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, select Media and Device Management > Media. Select Actions > New > Volume Pool. In the Add a New Volume Pool dialog, specify the attributes for the volume pool. For descriptions of the properties, see Volume pool properties on page 540.

Changing the properties of a volume pool

Use the following 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 3 4 In the NetBackup Administration Console, select Media and Device Management > Media > Volume Pools. Select a pool from the pools in the Volume Pools list. Select Edit > Change. In the Change Volume Pool dialog, change the attributes for the volume pool. For descriptions of the properties, see Volume pool properties on page 540.

540 Media Volume pool operations

Volume pool properties

The following sections describe the properties you can configure for volume pools, either when you add a new pool or change an existing one.

Catalog backup pool

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-Catalog policies. A dedicated catalog volume pool facilitates quicker catalog restore times. Multiple catalog backup volume pools are permitted.

Description
A brief description of the pool.

Maximum number of partially full media

Does not apply to the None pool, catalog backup pools, or scratch volume pools. Enter or specify the number of partially full media to allow in the volume pool. The default value is zero, which does not limit the number of full media that are allowed in the pool. NetBackup writes data only to the number of partially full media. When the number of partially full media is reached, NetBackup queues backup jobs until media becomes available. If a media becomes full, NetBackup assigns another media for use if one is available in the pool or in a scratch pool.

Media Volume pool operations

541

Frozen, suspended, and imported media do not count against Maximum number of partially full media. Therefore, if you unfreeze or unsuspend the media that are partially full, you may exceed the Maximum number of partially full media value. Also, if you lower the Maximum number of partially full media value, you may exceed the limit. If you exceed the Maximum number of partially full media value, NetBackup uses all of the partially full media until the limit is reached. This option lets you maximize your media usage. NetBackup writes data to the media until they are full, assigns other media to which it writes data until they are full, and so on. This option also lets you control how many drives are used for backup jobs. For example, if you have 10 drives and want to reserve two for restore operations, set the Maximum number of partially full media to 8. If all of the media is in one pool, NetBackup uses only 8 drives to write backup data. NetBackup can use the two other drives for restore operations even while backups occur. For more information about server groups, see Configuring server groups for media sharing on page 615.

Pool name
The name for the new volume pool. Volume pool names are case sensitive, 20 character maximum. For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

Scratch pool
Select this option to use the pool as a scratch pool. A scratch pool is a special volume pool from which NetBackup can transfer volumes to another volume pool when that pool has no volumes available. When the images on a volume expire, NetBackup returns it to the scratch volume pool if it was assigned from the scratch pool. There can be only one scratch pool configured. You cannot add a scratch pool if one exists. You cannot change the NetBackup or DataStore pools to be scractch volume pools. Symantec recommends that you use a descriptive name for the pool name and use scratch pool in the description. You should 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 your existing volume pools are allocated for use.

542 Media Volume group operations

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 HSM volume pool (for Veritas Storage Migrator) The DataStore volume pool

To delete a volume pool 1 2 In the NetBackup Administration Console, select 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. Select Edit > Delete. Answer the confirmation dialog.

Volume group operations

The volume group shows the location of the volume. The location can be either the robot in which the volume resides, stand-alone, or off-site if you use the NetBackup Vault option. The following are the volume group operations you can perform:

Moving a volume group on page 542 Deleting a volume group on page 544

Moving a volume group

You can move a volume group as follows:

From a robotic library to stand-alone From stand-alone to a robotic library

Moving a volume group changes only the residence information in the EMM database. You must move the volumes physically to their new locations.

Media Volume group operations

543

To move a volume group 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Media. In the tree pane, select the volume group that you want to move. Select Actions > Move. In the Move Volume Group dialog, specify the properties for the move. You can only specify the properties that apply for the move type. See Move volume group properties on page 543.

After you move the volume group logically, physically move the volumes to their new locations.

Move volume group properties

The following sections describe the properties you can set when you move a volume group.

Destination
Displays the destination for the move:

If you move the volume group from a robotic library, Standalone is selected as the destination. If you move the volume group from stand-alone, Robot is selected as the destination

Device host
NetBackup Enterprise Server only.

544 Media Robot inventory operations

The device host that controls the robotic library.

Robot
The destination robotic library.

Volume group
The volume group to move. Displays --- when you move stand-alone volumes.

Deleting a volume group

You can delete a volume group. However, To delete a volume group 1 2 In the NetBackup Administration Console, select Media and Device Management > Media. In the volumes list, verify that all of the volumes in the group are unassigned. You cannot delete the group until these volumes are deassigned by the application. If the Time Assigned column contains a value, the volume is assigned. To deassign a volume, see Deassigning volumes on page 533. Select a volume group in the tree pane. Select Edit > Delete. In the confirmation dialog box, confirm the action. Remove the deleted volumes from the storage device.

3 4 5 6

Robot inventory operations

Robot inventory does the following:

Queries robots about their media Provides reports about that media Optionally, updates the NetBackup volume configuration (that is, the EMM database) to match the results of the inventory

To inventory robotic libraries that have barcode readers and contain barcoded media, see Inventory a robot on page 547. The robotic inventory information is used to track the location of media. To inventory the robots without barcode readers or the media without readable barcodes, see Using the physical inventory utility on page 572.

Media Robot inventory operations

545

For more information, see the following:

When to inventory a robot on page 545 Robot Inventory dialog box on page 548 Using the physical inventory utility on page 572 Volume configuration update examples on page 579

When to inventory a robot

Uise the following information to determine when to inventory a robot and which options to use for the inventory. An inventory is a logcal operation. After you physically add, move, or remove volumes in a robot, use a robot inventory to update the NetBackup volume configuration. Table 9-1 Action Robot inventory criteria Inventory option to use

Add new volumes to a robot (a new For any robot NetBackup supports, use the Update volume is one that does not have a volume configuration option. NetBackup media ID) The update creates media IDs (based on barcodes or a prefix that you specify). Determine if volumes have been moved physically within a robot For robots with barcode readers and that contain media with barcodes, use the Compare contents with volume configuration option. Use the Show contents option to determine the media in a robot and possibly their barcode numbers. Use the Preview volume configuration changes option, which compares the contents of the robot with the NetBackup volume configuration information. After you examine the results, you can use the Update volume configuration option to update the volume configuration if necessary.

Determine the contents of a robot

Determine whether new media have barcodes before you add them to NetBackup

546 Media Robot inventory operations

Table 9-1 Action

Robot inventory criteria Inventory option to use

If the robot supports barcodes and the volume has a readable barcode, 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. You must specify the volume group to assign the volume to. If the robot does not support barcodes or the volumes do not have readable barcodes, do one of the following procedures:

Insert existing volumes into a robot (an existing volume is one that already has a NetBackup media ID)

Moving volumes on page 524 Using the physical inventory utility on page 572

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 barcodes and the volume has a readable barcode, use the Update volume configuration option. NetBackup updates the residence information to show the new robotic or stand-alone location. If the robotic library supports barcodes and the volume has a readable barcode, use the Update volume configuration option. NetBackup updates the NetBackup volume configuration information. If the robots do not support barcodes or the volumes do not have readable barcodes, do one of the following procedures:

Move existing volumes from one robot to another (an existing volume is one that already has a NetBackup media ID)

Moving volumes on page 524 Using the physical inventory utility on page 572

For either operation, you must perform two separate updates:

First move the volumes to stand-alone Then move the volumes to the new robot

If you do not do both updates, NetBackup cannot update the entries and writes an Update failed error. See Example 6: Moving existing volumes between robots on page 587.

Media Robot inventory operations

547

Table 9-1 Action

Robot inventory criteria Inventory option to use

If the robot supports barcodes and the volume has a readable barcode, use the Update volume configuration option. NetBackup updates the residence information to show the new slot location. If the robot does not support barcodes or the volumes do not have readable barcodes, do one of the following procedures:

Move existing volumes within a robot (an existing volume is one that already has a NetBackup media ID)

Moving volumes on page 524 Using the physical inventory utility on page 572

See Example 7: Adding existing volumes when barcodes are not used. Remove existing volumes from a robot (an existing volume is one that already has a NetBackup media ID) For any robot NetBackup supports, use the Update volume configuration option to update the NetBackup volume configuration information.

Inventory a robot
The following are the robot inventory options you can select using the NetBackup Administration Console:

Show contents. Displays the media in the selected robotic library; does not check or change the EMM database. 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. Preview volume configuration 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. Update volume configuration. Compares the contents of a robotic library with the contents of the EMM database. If differences exist, NetBackup updates the database to match the contents of the robot.

For examples of different volume configuration updates, see Volume configuration update examples on page 579. To inventory the robots without barcode readers or the media without readable barcodes, see Using the physical inventory utility on page 572.

548 Media Robot inventory operations

To inventory a robot 1 2 3 In the NetBackup Administration Console, select Media and Device Management > Media > Robots. Select the robot you want to inventory. Select Actions > Inventory Robot. In the Robot Inventory dialog, Device host contains the name of the host that controls the robot and Robot contains the selected robot. Specify the options for the inventory. For information about the options you can specify, see Robot Inventory dialog box on page 548. Click Start to begin the inventory.

Robot Inventory dialog box

The following are the options you can configure for a robot inventory.

Advanced options
Active if you select Update volume configuration or Preview volume configuration changes.

Media Robot inventory operations

549

Opens the Advanced Robot Inventory Options dialog, from which you can configure more options. See Advanced Robot Inventory Options dialog on page 555. For most configurations, the default settings work well. You should only change the settings if your configuration has special hardware or usage requirements.

Compare contents with volume configuration

Inventories the selected robot and compares its contents with the contents of the EMM database. This option does not change the database. If the robot can read barcodes, the barcodes on the media are compared to the barcodes in the EMM database. If the robotic library cannot read barcodes, the results show only whether a slot contains a volume. For API robots, the media ID and media type in the EMM database are compared to the information received from the vendors robotic library software. If the results show that the EMM database does not match the contents of the robotic library, do one of the following:

Physically move the volume. Update the EMM database by using Actions > Move or by using the Update volume configuration option.

The following figure shows a sample compare report. Figure 9-1 Compare contents report (API robot)

Device host
The host that controls the robot. In NetBackup Enterprise Server, you can specify the device host.

550 Media Robot inventory operations

Empty media access port prior to update

Empty media access port prior to update 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. Note: If you ejected volumes from the robot by using NetBackup, 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.

Preview volume configuration changes

Previews the update without changing the EMM database. You can review the changes before you update the volume configuration. This option lets you ensure that all new media have barcodes before you add them to the EMM database. Caution: 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 changes that occur between the preview and the update. Changes can be to the state of the robot, to the EMM database, to the barcode rules, to the media type mappings, and so on. Figure 9-2 Update volume configuration results (not an API robot)

Media Robot inventory operations

551

Robot
The robot to inventory.

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 are displayed depend on the robot type, as follows: Type of robot
Robot has a barcode reader and the robot contains media with barcodes. Robot does not have a barcode reader or robot does not contain media with barcodes. API robot.

Report contents
Shows if each slot has media and lists the barcode for the media. Shows if each slot has media.

Shows a list of volumes in the robot.

Note: If a volume is mounted in a drive, the inventory report lists the slot that it was in before it was moved to the drive. For robots other than API robots that have a barcode reader, the results include the barcode from each volume.

How contents for API robots are generated

The results of the inventory operation depend on the robot type. The following figure shows results for an ACS robot. The results for other API robots are similar.

552 Media Robot inventory operations

Figure 9-3

Show contents report (API robot)

ACS robots
NetBackup Enterprise Server topic. The results, received from ACS library software, shows:

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

TLH robots
NetBackup Enterprise Server topic. The results, received from the Automated Tape Library (ATL) library manager, show:

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

TLM robots
NetBackup Enterprise Server topic.

Media Robot inventory operations

553

The results, received from the DAS/SDLC server, shows

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 the mapping between the DAS/SDLC media type and the corresponding Media Manager media type (without considering optional barcode rules).

Update volume configuration

Inventories the selected robot and compares its contents with the contents of the EMM database. If differences exist, NetBackup updates the database to match the contents of the robot. 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. For more information, see Advanced Robot Inventory Options dialog on page 555. For API robots, the update returns an error if the volume serial number or the media ID contain unsupported characters. For robots without barcode readers or for volumes without readable barcodes, the new media IDs are based on a media ID prefix that you specify. You should consider using the vmphyinv physical inventory utility to add the media. The vmphyinv physical inventory utility inventories nonbarcoded tape libraries as follows:

Mounts each tape Reads the tape header Identifies the tape in each slot Updates the NetBackup volume configuration

For more information, see Using the physical inventory utility on page 572.

Determining robot capabilities before you update the volume configuration

Before you update the volume configuration, determine the following:

If the robotic library supports barcodes If any new volume inserted into the library has readable barcodes.

Check the barcode capabilities of the robotic library and the volume by comparing the robot contents with the NetBackup volume configuration.

554 Media Robot inventory operations

See Compare contents with volume configuration on page 549. If the robotic library does not support barcodes or the volume does not have readable barcodes, save the results of the compare operation. The results can help you determine a media ID prefix if you use the Advanced Options Media Settings tab to assign a prefix.

Example update volume configuration reports

The following figure shows example results for a robotic library that is not an API robot. Note: You can select a device host only with NetBackup Enterprise Server. The following figure shows example results for an ACS robot. Results for other API robots are similar to this report. Figure 9-4 Update volume configuration report (API robot)

Media Robot inventory operations

555

Advanced Robot Inventory Options dialog

The advanced robot inventory update options allow you to do the operations that are shown in the following table: Advanced operation
Assign media settings for new and existing media. Create barcode rules. Create media ID generation rules. Map media for API robots. If you do not map media, default media types are used.

For more information

See Media Settings tab on page 555. See Barcode Rules tab on page 562. See Media ID Generation tab on page 565. See Media Type Mappings tab on page 566.

Media Settings tab

Use the Media Settings tab of the Advanced Robot Inventory Options dialog box to do the following:

Specify the volume group for existing media Specify media options for new media

556 Media Robot inventory operations

Label optical media (Local host only)

Label optical media (local host only) is enabled only if you selected an optical robot to inventory. The media is labeled only if the robot is attached to the host you specified when you logged into the NetBackup Java Administration Console. The following are the label options:

Yes, but do not overwrite old labels Yes, overwrite as needed No

Note: The media is labeled, but is not formatted.

Media type
Media type is always set to DEFAULT for API robots. For instructions for specifying media types for API robots, see Media Type Mappings tab on page 566. Specifies the type for new media that are added to a robot. The list includes the media types that are valid for the robot.

Specifying media type when not using barcode rules

The following are the choices:

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. NetBackup Enterprise Server only: If the drives are not configured on the robot control host and the drives are not the default media type for the robot, select a specific type.

Media Robot inventory operations

557

The following table shows the default media types for robots when drives are not configured on the robot control host: Table 9-2 Robot type
Optical Disk Library (ODL)

Default media types for non-API robots Default media type

Rewritable optical disk. Also supports write-once read-many (WORM) operations.

Tape Library 4MM (TL4) Tape Library 8MM (TL8)

4MM cartridge tape. 8MM cartridge tape. Also supports 8MM cartridge tape 2 and 8MM 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 8MM cartridge tape, 8MM cartridge tape 2, 8MM cartridge tape 3 DTF cartridge tape 1/4-inch cartridge tape

Tape Stacker Half-inch (TSH)

1/2-inch cartridge. Also supports 1/2-inch cartridge tape 2 and 1/2-inch cartridge tape 3.

Specifying media type when using barcode rules

The following are the choices:

DEFAULT. To let barcode rules determine the media type that is assigned, select DEFAULT. Each media type to be added should have a barcode rule. For example, assume you want to add DLT and half-inch cartridges to a TLD robot with a single update operation. First create separate barcode rules for DLT and half-inch cartridges and then select the specific media types when you create the barcode rules. Finally, select DEFAULT on the Media Settings tab. The correct media type is assigned to each media.

558 Media Robot inventory operations

Note: If you choose DEFAULT on the Media Settings tab and DEFAULT in the barcode rule, NetBackup assigns the default media type for the robot.

To use a media type other than the default, select a specific media type from the list. You can use one barcode rule to add media of different types, 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 barcode rule media type when you create the barcode rule. You can perform one update for DLT and another for half-inch cartridge, and the one barcode rule assigns the correct media type. If you specify any value other than DEFAULT on the Media Settings tab, the barcode rule media type must be the same as the media or be DEFAULT. If not, the barcode rule does not match the media (except for cleaning media). The following table shows some example combinations of media types on the Media Settings tab and barcode rule media types for a TLD (non-API) robot and the results when the media are added to the volume configuration: Media type on Media Settings tab
DLT HCART DLT DLT DLT_CLN DLT_CLN DLT_CLN DLT DEFAULT DEFAULT DEFAULT DEFAULT

Barcode rule media type

DEFAULT DEFAULT DLT DLT_CLN DLT DLT_CLN DEFAULT 8MM, 4MM, and so on DEFAULT DLT DLT_CLN 8MM, 4MM, and so on

Rule matches?
Yes Yes Yes Yes No Yes Yes No Yes Yes Yes No

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

Media Robot inventory operations

559

The fourth row in the table shows how both cleaning cartridges and regular volumes are added using one update operation. The following conditions all must be true:

The media type on the Media Settings tab is for regular media (DLT, in this example). The barcode matches a barcode tag.

The media type for the barcode rule is cleaning media (DLT_CLN). For another example, see Example 5: Adding cleaning tapes to a robot on page 586. 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 barcode rule. In the seventh, you specify the cleaning media on the Media Settings tab and specify default when you configure the barcode rule. For more information about barcode rules, see Barcode Rules tab on page 562.

Media that have been removed from the robot

Specifies the volume group to assign to the media that are removed from the robot. The list always contains the following choices:

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. NO VOLUME GROUP. The media are not assigned to a volume group.

Other choices may be available, depending on the setting of the Media type field; If the Media type is:

DEFAULT, the list includes the volume groups that are valid for the robots default media type. Other than DEFAULT, the list 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 from the list. For more information about media types, see Media type on page 556.

Media that have been moved into or within the robot

Specifies the volume group to assign to existing media that you have inserted into the robot (or moved to a new location within the robot).

560 Media Robot inventory operations

The list always contains the following choices:

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 choices may be available, depending on the setting of the Media type field; If the Media type is:

DEFAULT, the list includes the volume groups that are valid for the robots default media type. Other than DEFAULT, the list 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 from the list. Tip: 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 have been moved into or within the robot, the new update fails: volumes of different media types cannot have the same volume group. For more information about media types, see Media type on page 556.

Use barcode rules

Specifies whether or not to use barcode rules to assign attributes for new media. To enable barcode rule support for API robots, you must add an API_BARCODE_RULES entry to the vm.conf file. For more information about barcode rules, see Barcode Rules tab on page 562.

Use the following Media ID prefix

If the robot supports barcodes and the volume has readable barcodes, a prefix is not required because NetBackup creates media IDs automatically. You should specify a Media ID prefix for any new media if either of the following conditions exist:

The robot does not support barcodes. The volume that was inserted does not have readable barcodes. DEFAULT. If you select DEFAULT, NetBackup:

The following are the choices in the pick list:

Media Robot inventory operations

561

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.

Other prefixes if they are configured in the vm.conf file.

To specify a media ID prefix 1 2 Click Browse. In the Media ID Prefix dialog, do one of the following:

Click Specify the media ID prefix for current session only and then enter a new value for the prefix in the text box. The prefix you enter is used only for the current operation. It is not added to the vm.conf file. 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. Click Choose from the media ID prefix list (stored in vm.conf file). and then click on one of the prefixes in the prefix window. Optionally, you can add a new prefix to the list. First enter a prefix in the text box and then click Add.

Click OK to return to the Media Settings tab. About labeling NetBackup volumes on page 510 vm.conf options for media servers in the NetBackup Administrators Guide for UNIX and Linux, Volume II

for more information, see the following:

Volume pool
Specifies the volume pool for the new media. The actions depend on whether you use barcode rules to assign media attributes. The following are the choices:

DEFAULT. If you select DEFAULT and are:

Using barcode rules, the barcode rules determine the volume pool to which new volumes are assigned. Not using barcode rules, NetBackup assigns data tapes to the NetBackup pool but does not assign cleaning tapes to a volume pool.

A specify volume pool. If you use barcode rules, this volume pool setting always overrides the rule.

562 Media Robot inventory operations

Barcode Rules tab

Use the Barcode Rules tab of the Advanced Robot Inventory Options dialog box to configure rules for assigning attributes to new volumes added to a robot. These rules are used when you specify Use barcode rules on the Media Settings tab. To add a rule, click New and then configure the rule in the dialog box. To change a rule, select the rule, click Change, and then change the rule in the Change Barcode Rule dialog box. You cannot change the barcode tag of a barcode rule. You must first delete the old rule and then add a rule with a new barcode tag. To delete a rule, select the rule, click Delete, and then click OK in the confirmation dialog. You can select and delete multiple rules with one operation. For more information about barcodes, see Barcode overview in the NetBackup Administrators Guide for UNIX and Linux, Volume II

Barcode tag
The barcode tag is a unique string of characters from the barcode that identifies the type of media. For example, you can use DLT as the barcode tag for a barcode rule if:

You use DLT on your barcodes to identify DLT tapes DLT is not used on any other barcodes in the robot

Similarly, if you use CLND for DLT cleaning media, you can use CLND as the barcode tag for the rule for DLT cleaning media.

Media Robot inventory operations

563

The barcode tag can have from 1 to 16 characters but cannot contain any spaces. The following are special barcode rules that can match special characters in the barcode tags:

NONE. Matches when rules are used and the volume has an unreadable barcode or the robot does not support barcodes. DEFAULT. For volumes with barcodes, this tag matches when none of the other barcode 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 barcode tag of a barcode rule. You must first delete the old rule and then add a rule with a new barcode tag. Use the Media Settings tab to set up the criteria for a robot update. See Media Settings tab on page 555.

Description
A description of the barcode rule. You can enter from 1 to 25 characters.

Maximum mounts
The maximum number of mounts (or cleanings) that are allowed for the volume. For data volumes, a value of 0 means the volume can be mounted an unlimited number of times. For cleaning tapes, 0 means the cleaning tape is not used. To avoid a value of 0 for cleaning tapes, use barcodes for your cleaning media that cannot be confused with barcodes for data media.

Media type
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 barcode rule. If you specify any value other than DEFAULT on the Media Settings tab, the barcode rule media type must be the same as the media or be DEFAULT. If not, the barcode rule does not match the media (except for cleaning media). For more information, see Specifying media type when using barcode rules on page 557.

564 Media Robot inventory operations

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.

Barcode rule media type for API robots

A barcode rule is used only if the barcode rule media type is compatible with the media type on the Media Type Mappings tab. If you specify DEFAULT, NetBackup uses the media type you select on the Media Type Mappings tab. If you do not specify a media type on the Media Type Mappings tab, NetBackup uses the default media type for the robot. To enable barcode rule support for API robots, you must add an API_BARCODE_RULES entry to the vm.conf file. Note: If a barcode rule contains media types that are incompatible with vendor media types, the robot inventory update may add media with media types inconsistent with the vendor media types. Avoid this problem by grouping barcode rules by media type.

Barcode rule media type for non-API robots

NetBackup uses barcode rule only if the media type in the rule is compatible with the media type you select on the Media Settings tab. Select the media type for non-API robots as explained in the following table: If you want the media type for the barcode rule to match Select the following media type for the barcode rule Media type NetBackup uses
The media type that you select on the Media Settings tab. If you also select DEFAULT on the Media Settings tab, the Media Manager default media type for the robot is used. Only when you select a specific media type or you select DEFAULT on the Media Settings tab The same media type The media type that you select for the barcode rule.

Any media type that you select DEFAULT on the Media Settings tab

Media Robot inventory operations

565

Volume pool
Specifies the volume pool for the new media. If you use a barcode rule and the Media Settings tab Volume pool field is set to:

DEFAULT, the volume is assigned to the pool you specify in this Volume pool setting. A specific volume pool, the Volume pool setting on the Media Settings tab overrides this Volume pool setting.

Media ID Generation tab

To use media ID generation rules, the robot must support barcodes and the robot cannot be an API robot. Media ID generation rules lets you override the default media ID naming method. The default method uses the last six characters of the barcode label from the tape. You can control how NetBackup creates media IDs by defining the rules that specify which characters of a barcode label to use for the media ID. To add a rule, click New and then configure the rule in the dialog box. To change a rule, select the rule, click Change and then change the rule in the Change Media ID Generation Rule dialog. You cannot change the robot number or barcode length of a rule. To change those properties, you must first delete the old rule and then add a rule. To delete a rule, select the rule, click Delete, and then click OK in the confirmation dialog. You can select and delete multiple rules with one operation.

566 Media Robot inventory operations

Barcode length
The number of characters in the barcode for tapes in the robot.

Media ID generation rule

A rule consists of a maximum of six fields delimited by colons. Numbers define the positions of the characters in the barcode that are to be extracted. For example, 2 in a field extracts the second character (from the left) of the barcode. Numbers can be specified in any order. The characters prefixed by the pound sign (#) in a field result in that character being inserted in that position in the generated ID. Any alphanumeric characters that are specified must be valid for a media ID. The following table shows some examples of rules and the resulting media IDs. You can 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. Barcode on tape
032945L1 032945L1 032945L1 543106L1 543106L1

Media ID generation rule

1:2:3:4:5:6 3:4:5:6:7 #N:2:3:4:5:6 #9:2:3:4 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.

Media Type Mappings tab

This tab is available only for API robots. API robots are ACS, TLH, or TLM robot types on NetBackup Enterprise Server. Use the Media Type Mappings tab to map the default media types for an API robot to one of the NetBackup media types for that robot vendor. Changes apply only to the current volume configuration update. The mappings that are displayed are only for the robot type that has been selected for inventory. The update operation also uses any robot-specific media mappings in the vm.conf file. If the vm.conf file does not exist or does not contain media

Media Robot inventory operations

567

mapping entries for that robot type and media type, NetBackup uses the default media types and any mappings on the Media Type Mappings tab. See Adding mapping entries on page 567. To change media type mappings 1 2 3 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, select a Media Manager media type from the list of allowable choices. Click OK.

To reset the mappings to the default, click Reset to Defaults.

Adding mapping entries

The default media type mappings tab 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 running the NetBackup Administration Console. For more information about vm.conf file ACS mapping entries, see ACS_mediatype in the vm.conf options for media servers section of the NetBackup Administrators Guide for UNIX and Linux, Volume II

568 Media Robot inventory operations

The following table shows some examples of robot-specific media mappings: vm.conf entry
ACS_3490E = HCART2

Result

Robot default without a vm.conf entry

Maps the ACS 3490E to HCART the HCART2 media type. Maps ACS DLTIV to the DLT for all ACS DLT media types, DLT2 media type. including DLTIV Maps the TLH 3490E to HCART the HCART2 media type.

ACS_DLTIV = DLT2

TLH_3490E = HCART2

Default and allowable media types

The default media types on the Media Type Mappings tab are media types provided by each robot vendor. Table 9-3 through Table 9-5 contain the default and allowable media types for the API robots:

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, you must first add the allowable mapping entries to the vm.conf file.

For example, Table 9-3 shows that for ACS robots you cannot specify either of the following map entries in the configuration file:
ACS_DD3A = DLT ACS_DD3A = HCART4

Table 9-3 ACS media type

3480 3490E DD3A DD3B DD3C DD3D

Default and allowable media types for ACS robots Default Media Manager media type
1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART)

Allowable media types through mappings

HCART, HCART2, HCART3 HCART, HCART2, HCART3

1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge cleaning tape 2 (HC2_CLN) HC_CLN, HC2_CLN, HC3_CLN

Media Robot inventory operations

569

Table 9-3 ACS media type

DLTIII DLTIIIXT DLTIV EECART JLABEL KLABEL LTO_100G LTO_10GB LTO_200G LTO_35GB LTO_400G LTO_400W LTO_50GB LTO_800G LTO_800W LTO_CLN1

Default and allowable media types for ACS robots (continued) Default Media Manager media type
Digital Linear Tape (DLT) Digital Linear Tape (DLT) Digital Linear Tape (DLT) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART2) 1/2-inch cartridge (HCART)

Allowable media types through mappings

DLT, DLT2, DLT3 DLT, DLT2, DLT3 DLT, DLT2, DLT3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3

1/2-inch cartridge tape 3 (HCART3) HCART, HCART2, HCART3 1/2-inch cartridge tape 3 (HCART3) HCART, HCART2, HCART3 1/2-inch cartridge (HCART) 1/2-inch cartridge tape (HCART) 1/2-inch cartridge tape (HCART) 1/2-inch cartridge cleaning tape (HC_CLN) 1/2-inch cartridge cleaning tape (HC_CLN) 1/2-inch cartridge cleaning tape (HC_CLN) 1/2-inch cartridge cleaning tape (HC_CLN) Digital Linear Tape 3 (DLT3) Digital Linear Tape (DLT) Digital Linear Tape (DLT) Digital Linear Tape 2 (DLT2) Digital Linear Tape (DLT) HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HC_CLN, HC2_CLN, HC3_CLN

LTO_CLN2

HC_CLN, HC2_CLN, HC3_CLN

LTO_CLN3

HC_CLN, HC2_CLN, HC3_CLN

LTO_CLNU

HC_CLN, HC2_CLN, HC3_CLN

SDLT SDLT_2 SDLT_4 SDLT_S1 SDLT_S2

DLT, DLT2, DLT3 DLT, DLT2, DLT3 DLT, DLT2, DLT3 DLT, DLT2, DLT3 DLT, DLT2, DLT3

570 Media Robot inventory operations

Table 9-3 ACS media type

SDLT_S3 SDLT_S4 STK1R STK1U

Default and allowable media types for ACS robots (continued) Default Media Manager media type
Digital Linear Tape (DLT) Digital Linear Tape (DLT) 1/2-inch cartridge (HCART) 1/2-inch cartridge cleaning tape (HC_CLN) 1/2-inch cartridge cleaning tape (HC_CLN)

Allowable media types through mappings

DLT, DLT2, DLT3 DLT, DLT2, DLT3 HCART, HCART2, HCART3 HC_CLN, HC2_CLN, HC3_CLN

STK1Y

HC_CLN, HC2_CLN, HC3_CLN

STK2P STK2W

1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge cleaning tape 2 (HC2_CLN) 1/2-inch cartridge tape 3(HCART3) 1/2-inch cartridge tape 3(HCART3) 1/2-inch cartridge tape 3(HCART3) HC_CLN, HC2_CLN, HC3_CLN

T10000CT T10000T1 T10000TS UNKNOWN (for unknown ACS media types)

HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3

1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3, HC_CLN, HC2_CLN, HC3_CLN, DLT, DLT2, DLT3, DLT_CLN, DLT2_CLN, DLT3_CLN 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3, HC_CLN, HC2_CLN, HC3_CLN, DLT, DLT2, DLT3, DLT_CLN, DLT2_CLN, DLT3_CLN

VIRTUAL

Table 9-4 TLH media type

3480 3490E 3590J 3590K

Default and allowable media types for TLH robots Default Media Manager media type
1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART) 1/2-inch cartridge (HCART)

Allowable media types through mappings

HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3 HCART, HCART2, HCART3

Media Robot inventory operations

571

Table 9-4 TLH media type

3592JA 3592JB 3592JX 3592JJ 3592JR 3592JW UNKNOWN (for unknown TLH media types)

Default and allowable media types for TLH robots (continued) Default Media Manager media type Allowable media types through mappings

1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3 1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3

Table 9-5 TLM media type

3480 OD_THICK

Default and allowable media types for TLM robots Default Media Manager media type
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)

Allowable media types through mappings

HCART, HCART2, HCART3 NONE

DECDLT 8MM 4MM 3590 DTF SONY_AIT LTO

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)

DLT, DLT2, DLT3 8MM, 8MM2, 8MM3 4MM HCART, HCART2, HCART3 DTF 8MM, 8MM2, 8MM3 HCART, HCART2, HCART3

572 Media Robot inventory operations

Table 9-5 TLM media type

UNKNOWN (for unknown TLM media types)

Default and allowable media types for TLM robots (continued) Default Media Manager media type Allowable media types through mappings

1/2-inch cartridge tape 2 (HCART2) HCART, HCART2, HCART3, DLT, DLT2, DLT3, 8MM, 8MM2, 8MM3

Note: The following TLM media types are not supported: OD_THIN, D2, VHS, CD, TRAVAN, BETACAM, AUDIO_TAPE, BETACAMCL, DVCM, and DVCL.

Note: API robots: If a barcode rule contains media types that are incompatible with vendor media types, the robot inventory update may add media with media types inconsistent with the vendor media types. Avoid this problem by grouping barcode rules by media type.

Using the physical inventory utility

For the robots without barcode readers or that contain media without barcodes, the inventory reports only the presence of media in a robotic library. More detailed information is required to perform automated media management. You should use the the vmphyinv utility to inventory such robots. The vmphyinv physical inventory utility inventories nonbarcoded tape libraries as follows:

Mounts each tape Reads the tape header Identifies the tape in each slot Updates the NetBackup volume configuration

For the complete syntax of the vmphyinv command, see vmphyinv in NetBackup Commands for UNIX and Linux. For more information, see the following:

Features of vmphyinv on page 573 Requirements and restrictions for vmphyinv on page 573 When to use vmphyinv on page 573 How vmphyinv performs a physical inventory on page 574

Media Robot inventory operations

573

Features of vmphyinv
The vmphyinv utility has the following features:

Can be invoked from any master server, media server, or SAN media server. Can be used with barcoded tape libraries because it verifies the contents of the media. Recognizes NetBackup, Backup Exec, and Veritas Storage Migrator (VSM) tape formats. Supports remote administration. You do not need to invoke 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 SCSI-based robot types (except optical disk libraries). Can be used to inventory a single media in a stand-alone drive. Use the -u or -n option to specify the drive; the drive must contain media and it must be ready.

Requirements and restrictions for vmphyinv

The vmphyinv utility has the following requirements and restrictions:

It cannot distinguish between the volume records based on the application type. When you move the media from robotic drives to stand-alone drives, you cannot specify a new volume group for the media. It does not support the optical disk library (ODL) robot type.

When to use vmphyinv

Use the vmphyinv utility to update the EMM database for NetBackup, Backup Exec, and Veritas Storage Migrator media. You can use vmphyinv in the following typical cases:

You want to inventory a robot that does not have a barcode reader or that contains nonbarcoded 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.

574 Media Robot inventory operations

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. vmphyinv 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. You can inventory the robot or inventory a subset of media in the robot by using options in vmphyinv.

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 Obtains a list of media to be mounted Mounts media and reads the tape header Updates the EMM database

Obtains a list of drives to mount the media

The list of drives vmphyinv uses to mount the media is obtained from the EMM database. The drives do not have 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.

Obtains a list of media to be mounted

You can specify the following vmphyinv options for the media to be mounted:

NetBackup robot number (-rn robot_number). vmphyinv 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, you can specify a subset of the media by using filter options. Some filter options are volume pool, volume group, or slot

Media Robot inventory operations

575

range. To use these options, NetBackup volume records must exist. The following are some examples: Options specified
-rn 4 -pn bear

Media inventoried
Only media in robot 4 and in the volume pool bear. Media in robot 2 and in the volume group moon. Only media in robot 1 and slot range 2 to 4.

-rn 2 -v moon -rn 1 -rc1 2 -number 3

-rn 5 -pn NetBackup -v mars -rc1 2 Only media in robot 5, slot range 2 to 7, in -number 6 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. 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, you can 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, you should specify the density carefully. If you specify the incorrect density, vmphyinv cannot complete the mount and permanent drive failure can occur. The following table shows some examples: Options specified
-rn 1 -slot_range 2 10 -d dlt -rn 0 -slot_list 3:4:5 -d 8mm -rn 2 -slot_range 2 4 -slot_list 5:6:7 -d dlt

Media inventoried
Media in slot range 2 to 10 in robot 1. Media in slots 3, 4, and 5 in robot 0. Media in slots 2, 3, 4, 5, 6, and 7 in robot 2.

576 Media Robot inventory operations

Mounts 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 Veritas Storage Migrator and Symantec Backup Exec.

Note: The default mount timeout is 15 minutes. You can specify a different mount time by using the -mount_timeout option.

Media that is not recognized

If the media is not NetBackup media, Backup Exec media, or Veritas Storage Migrator 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.

Cleaning media
If the following conditions are all true, vmphyinv does not attempt to mount the media. 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 used the slot range or list option, and the EMM database does not contains a volume record that corresponds to the cleaning media.

Media Robot inventory operations

577

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.

Updates the EMM database

After all the media are mounted and the tape headers are read, vmphyinv displays a list of recommended changes. You can accept or reject the changes. If you accept the changes, vmphyinv updates the EMM database.

Using the verbose option

You can 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, and so on. (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.

Update criteria
For valid media types, vmphyinv:

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 or Veritas Storage Migrator 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.

578 Media Robot inventory operations

Updating 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 the media ID. If the media ID does not exist, vmphyinv creates a new NetBackup volume record that corresponds to the NetBackup media.

Updating Backup Exec media

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 a 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 BackupExec pool. If the BackupExec pool does not exist, vmphyinv creates it.

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.

Updating Veritas Storage Migrator media

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 a 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 Veritas Storage Migrator media. The vmphyinv utility 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:

Media Robot inventory operations

579

In the NetBackup record, updates the ADAMM_GUID field with the GUID. Also updates the Description field with the Veritas Storage Migrator cartridge label in the tape header. Changes the volume pool of the unassigned NetBackup records that are associated with Veritas Storage Migrator media to the StorageMigrator pool. If the StorageMigrator pool does not exist, it is created.

Note: If a MEDIA_ID_PREFIX entry is not specified in the vm.conf file, NetBackup uses RS as the default prefix for Veritas Storage Migrator media. The Storage Migrator database is not updated.

Error cases
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 barcode of an existing volume record needs to be changed.

Volume configuration update examples

The following examples show only the relevant volume attributes. See the following for examples of different types of volume configuration updates:

Example 1: Removing a volume from a robot on page 580 Example 2: Adding existing stand-alone volumes to a robot on page 581 Example 3: Moving existing volumes within a robot on page 583 Example 4: Adding new volumes to a robot on page 584 Example 5: Adding cleaning tapes to a robot on page 586 Example 6: Moving existing volumes between robots on page 587 Example 7: Adding existing volumes when barcodes are not used on page 587

580 Media Robot inventory operations

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 barcodes. 1 The following are the attributes for media ID 800001.
media ID media type barcode media description volume pool robot type volume group max mounts allowed 800001 8MM cartridge tape TL800001 tl8 backup volume 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, and then execute 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 barcode media description volume pool robot type volume group max mounts allowed 800001 8MM cartridge tape TL800001 tl8 backup volume NetBackup NONE - Not Robotic NONROB_8MM 0 (unlimited)

Media Robot inventory operations

581

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

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 barcode to a robotic library that supports barcodes (TL8). Note: When you move volumes from one robot to another robot, you must do two separate updates. For procedures, see Example 6: Moving existing volumes between robots on page 587. 1 The following are the volume attributes for media ID 800021, which has a readable barcode and already exists as a stand-alone volume.
media ID media type barcode media description volume pool robot type volume group max mounts allowed 800021 8MM cartridge tape TL800021 8MM stand-alone 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, and then execute the update.
media type volume group use barcode rules volume pool DEFAULT EXB220 YES (selected) NetBackup

582 Media Robot inventory operations

Assume that the barcode rules in the following table exist: Barcode tag
CLND CLN8 TL8 DLT TS <NONE> <DEFAULT>

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 barcode other barcodes

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 barcode media description volume pool robot type robot number robot slot robot host volume group max mounts allowed 800021 8MM cartridge tape TL800021 8MM stand-alone NONE TL8 - Tape Library 8MM 0 1 shark EXB220 0 (unlimited)

The barcode matches the barcode 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, barcode rules are ignored.

Media Robot inventory operations

583

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.

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 barcodes and the volume has a readable barcode. Caution: To move volumes within a robotic library, use Update volume configuration only if the robotic library supports barcodes and the volumes have readable barcodes. Otherwise, NetBackup cannot properly recognize the move. 1 The following are the attributes for media ID 800002, which currently resides in slot 1 of the robotic library.
media ID media type barcode media description volume pool robot type robot number robot slot robot host volume group max mounts allowed 800002 8MM cartridge tape TL800002 tl8 backup NetBackup TL8 - Tape Library 8MM 0 1 shark EXB220 0 (unlimited)

Assume that you move the volume to empty slot 10, specify the following on the Media Settings tab, and then execute the update.
media type volume group use barcode rules volume pool DEFAULT EXB220 NO (not selected) DEFAULT

584 Media Robot inventory operations

The resulting volume attributes are:

media ID media type barcode media description volume pool robot type robot number robot slot robot host volume group max mounts allowed 800002 8MM cartridge tape TL800002 tl8 backup 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.

Example 4: Adding new volumes to a robot

The following is an example of how to add new volumes with barcodes to a robot that supports barcodes. Assume the following:

The new volume is an 8MM tape with a readable barcode 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. You specify the following on the Media Settings tab and execute the update.
Media type Volume group Use barcode rules Volume pool DEFAULT EXB2220 YES (selected) DEFAULT

Media Robot inventory operations

585

Assume that the barcode rules in the following table exist: Barcode tag
CLND CLN8 TL8 DLT TS <NONE>

Media type
DLT_CLN 8MM_CLN 8MM DLT 8MM DEFAULT

Volume pool
None None NetBackup d_pool None None

Max mounts/ Description cleanings

30 20 0 200 0 0 dlt cleaning 8mm cleaning tl8 backup dlt backup 8mm no pool no barcode

The barcode on the media matches the barcode rule named TL8 and the resulting volume attributes for the new volume are as follows:
Media ID Media type Barcode Media description Volume pool Robot type Robot number Robot slot Robot host Volume group Maximum mounts allowed 800002 8MM cartridge tape TL800002 tl8 backup NetBackup TL8 - Tape Library 8MM 0 1 shark EXB220 0 (unlimited)

No media ID generation rules exist. Therefore, the media ID is from the last six characters of the barcode. 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 max mounts allowed are from the barcode rule. If barcode rules (or barcodes) had not been used, the media description, volume pool, and max mounts allowed would be set to the following defaults:

586 Media Robot inventory operations

Media description: added by NetBackup Volume pool: NetBackup for data tapes or None for cleaning tapes Max mounts: 0 (unlimited)

Note: If the robot does not support barcodes or the barcode is unreadable, you must specify a Media ID prefix on the Media Settings tab. Alternatively, you can specify DEFAULT for the media ID. If you do not, NetBackup does not add new media IDs.

Example 5: Adding cleaning tapes to a robot

A special case exists when you add cleaning tapes. For example, assume you are updating a TLD robot. 1 The tapes you inserted include regular tapes with barcodes that range from DLT00000 to DLT00010 and a cleaning tape with a barcode of CLN001. Assume that the barcode rules in the following table exist: Barcode tag
CLN DL <NONE>

Media type
DLT_CLN DLT DEFAULT

Volume pool
None d_pool None

Max mounts/ cleanings

30 200 0

Description
dlt cleaning dlt backup no barcode

You specify the following on the Media Settings tab and then execute the update.
media type volume group use barcode rules DLT STK7430 YES (selected)

The barcodes on the regular tapes match the DL barcode rule. The media type of the DL barcode rule matches the Media type on the Media Settings tab. The tapes are added as DLT. The cleaning tape matches the CLN barcode 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.

Media Robot inventory operations

587

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 barcode on the volume matches a barcode tag (CLN in this example).

The media type for the barcode 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 barcode rule (DLT_CLN in this example).

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, you must perform two separate 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. Caution: This procedure assumes that robot 2 is able to read barcodes and the volume has readable barcodes. If not, the problem in Example 7: Adding existing volumes when barcodes are not used on page 587 occurs. 1 2 3 Remove the volume from robot 1. Insert the volume in robot 2. Perform an Update volume configuration on robot 1. This updates the volume attributes to show the volume as stand-alone. Perform an Update volume configuration on robot 2. This updates the configuration to show the volume in robot 2.

Example 7: Adding existing volumes when barcodes are not used

Caution: 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 barcodes.

588 Media Robot inventory operations

The following are the attributes for media ID 400021, which already exists as a stand-alone volume.
media ID media type barcode media description volume pool robot type volume group max mounts allowed 400021 4MM cartridge tape ----------4MM stand-alone None NONE - Not Robotic NONROB_4MM 0 (unlimited)

Assume that you insert the volume into the robot, specify the following on the Media Settings tab, and then execute the update.
media type volume group media ID prefix volume pool DEFAULT 00_000_TL4 C4 DEFAULT

The resulting volume attributes are:

media ID media type barcode media description volume pool robot type robot number robot slot robot host volume group max mounts allowed C40000 4MM cartridge tape ----------Added by NetBackup NetBackup TL4 - Tape Library 4MM 0 1 shark 00_000_TL4 0 (unlimited)

Media Using WORM media

589

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 have readable barcodes or the robot does not support barcodes. Without a barcode, NetBackup cannot identify the volume and assumes 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, you should use the physical inventory utility. See Using the physical inventory utility.

Using WORM media

WORM (Write-Once-Read-Many) media is used to protect key data from unwanted modification or to meet compliance regulations. The NetBackup QIC/WORM tape format is used for WORM media. This format allows NetBackup to append images to WORM tape as can be done with standard tape. NetBackup requires an SCSI pass-through drive 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. NetBackup uses SCSI commands to query drives. SCSI pass-through paths are provided on the server platforms NetBackup supports. Setting up SCSI pass-through paths may require special operating system configuration changes. For details, see the NetBackup Device Configuration Guide. Tape error recovery is disabled when using WORM media. NetBackup has job resume logic, which tries to resume a job that has been interrupted (for example, 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.

590 Media Using WORM media

Supported drives
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, you must modify the st.conf file. For information about how to configure nonstandard tape drives and how to edit the st.conf file, see the NetBackup Device Configuration Guide.

Managing your WORM media in NetBackup

To ensure that data that is intended for WORM media is written on WORM media, two methods exist in NetBackup. For more information, see the following.

Using WORM volume pools to manage WORM media on page 590 Using unique drive and media types to manage WORM media on page 591

Using WORM volume pools to manage WORM media

You can dedicate volume pools for your WORM media. This method allows a WORM-capable tape drive to back up and restore standard and WORM media. Create a new volume pool and specify WORM (upper-case letters) as the first four characters of the pool name. See Adding a new volume pool on page 539. 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:
/usr/openv/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.

Media Using WORM media

591

If the drive contains Quantum media that has never been used or has had all of its NetBackup images expired, NetBackup uses the media.

Using a 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, you should 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 does the following:

Moves 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 has been frozen. The opposite also is true. If a standard volume pool runs out of media and the scratch pool contains WORM media, standard backups may fail because appropriate media is unavailable.

Using 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 is moved from the scratch volume pool into the WORM pool. NetBackup determines whether the media is configured as standard or WORM media. For a standard media, NetBackup reads the tape label, verifies the media is unused or all images are expired, and 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.

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, you can 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 backup and restores with a specific type of media, optimal drive usage may not be achieved. For example, the

592 Media Using WORM media

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, you should 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:
/usr/openv/netbackup/db/config/DISABLE_WORM_POOLCHECK

Using the Quantum drive

Because Quantum drives use only a single media type, this method for managing your WORM media is unnecessary.

WORM tape limitations

The following are the current limitations when using 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 checkpoint. Symantec recommends that you use checkpoint and restart for backups. WORM tape is not supported with NetWare media servers.

Chapter

10

Devices
Use Media and Device Management > Devices to add, configure, and manage storage devices in NetBackup. To add and configure storage devices, see the following:

Device configuration prerequisites on page 593 The device mapping file on page 594 Configuring robots and tape drives on page 595 Configuring server groups for media sharing on page 615 Configuring and managing disk pools on page 618 Configuring SAN clients and Fibre Transport on page 619 NearStore configuration on page 747 Managing your device configuration on page 619

To manage your devices, see the following:

For more information about configuring and managing storage devices, see the following:

Stopping and restarting the device daemon on page 624 Activating and deactivating media servers on page 625 Accessing media and devices on other hosts on page 625 The Enterprise Media Manager server on page 626

Device configuration prerequisites

Before you configure storage devices in NetBackup, ensure that the following prerequisites are accomplished:

594 Devices The device mapping file

The storage devices must be attached to the system and recognized by the operating system before you begin NetBackup device configuration. 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 support NetBackup server software. If the host on which you configure devices is not the Enterprise Media Manager server, add it to the NetBackup additional servers list. 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 was not running, use the nbemmcmd -addhost command to add the host.

The device mapping file

NetBackup uses a file to determine which protocols and settings to use to communicate with storage devices. The Device Configuration Wizard also uses it during device discovery and configuration. In some cases, you can add support for new or upgraded devices without waiting for a release update from Symantec. To do so, download an updated device mapping file from the Symantec support Web site and configure NetBackup to use the updated file. Refer to the README file that is supplied with the device mapping file for additional instructions. Note: The contents of this file do not indicate support for any of the devices, only the ability to recognize and automatically configure them. To obtain the current device mapping file 1 Find the latest external types file for your devices on the Symantec support Web site. The following is the address for the site:
http://entsupport.symantec.com

The files that you download are named similarly to the following files: Mappings_6_nnnnnn.TAR and Mappings_6_nnnnnn.ZIP. 2 Download the latest external types file to the following location on the system that hosts the EMM server:

/usr/openv/var/global (UNIX)

install_path\netbackup\var\global (Windows)

Use the tpext command to update the EMM database with the new version of the device mapping file; no command-line parameters are required. The tpext command resides in the following directory:

Devices Configuring robots and tape drives

595

/usr/openv/volmgr/bin (UNIX)

install_path\volmgr\bin (Windows)

Stop and restart the Media Manager Device daemon. For procedures, see Stopping and restarting the device daemon on page 539.

Configuring robots and tape drives

Several methods exist for adding and for configuring storage devices, as follows:.

Using the Device Configuration Wizard on page 595. Symantec recommends that you use the Device Configuration Wizard to add and configure devices. Using options in the NetBackup Administration Console. If you use this method, first add the robot and then add the drives that are in the robot. For procedures, see the following:

Adding a robot on page 597 Adding or changing a drive on page 604 Adding a shared drive on page 605

When you configure devices, you can stop and restart ltid. This action also stops and restarts any robotic processes. For information about controlling ltid manually, see Stopping and restarting the device daemon on page 539. For device configuration examples, see the NetBackup Device Configuration Guide.

Using the Device Configuration Wizard

Caution: The Device Configuration Wizard stops and starts the daemons and services. Therefore, ensure that backups are not active when you use the wizard. Symantec recommends that you use the Device Configuration Wizard to add and configure the following types of devices:

Robots, including those attached to NDMP hosts Drives, including those attached to NDMP hosts Shared drives ( for NetBackup Shared Storage Option configurations only) Storage servers that control disk storage

596 Devices Configuring robots and tape drives

This wizard uses device discovery to add and configure devices automatically. To perform these tasks, this wizard uses device serialization. Device serialization is a feature in the storage devices that allows devices to be identified and configured programmatically. This wizard also uses the device mapping file during device discovery and configuration. See The device mapping file on page 462. In some cases, the wizard may leave some devices partially configured. See Devices that are partially-configured on page 596.

Operating system changes

To discover devices, NetBackup issues SCSI pass-through commands to the devices in an environment. The server platforms that NetBackup supports may require special operating system configuration changes. Changes may include those needed for device discovery. For more information, see the appropriate operating system chapter of the NetBackup Device Configuration Guide.

Possible EMM server host conflict

The following topic applies only to NetBackup Enterprise Server environments that include NetBackup 5.x media servers. When you scan devices, the wizard may detect an EMM server conflict. This conflict occurs when the NetBackup hosts you select to scan do not agree on which host stores device information. For more information, see The Enterprise Media Manager server on page 541.

Devices that are partially-configured

Some devices may be partially configured only, such as an unsupported robotic library or drive. If you deselect a discovered device from the tree view in the wizard, the device path is disabled. For NetBackup 5.x device hosts, partially-configured drives are shown as PCD and partially-configured robots as PCR in the Drives list. If you have partially-configured drives, ensure that you have downloaded the most recent device mapping file from the Symantec support Web site. See The device mapping file on page 462.

Devices Configuring robots and tape drives

597

Starting the Device Configuration Wizard

Start the wizard from the Media and Device Management window of the NetBackup Administration Console or from the Getting Started wizard. Be sure to review the limitations of the wizard before you configure devices. To start the Device Configuration Wizard 1 2 In the NetBackup Administration Console, select Media and Device Management. Click Configure Storage Devices.

Adding a robot
Note: Symantec recommends that you use the Device Configuration Wizard to add storage devices. For more information, see Using the Device Configuration Wizard on page 595. Use the following procedures to add a robot manually. When you add a robot and drives, first add the robot as explained in the following procedure and then add the drives. To add a drive, see Adding or changing a drive on page 604. To add a robot 1 2 3 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Actions > New > Robot. In the Add a New Robot dialog, specify the properties for the robot. The properties you can configure depend on robot type, host type, and robot controls selections you make in the dialog. For descriptions of the properties, see Robot properties on page 598.

598 Devices Configuring robots and tape drives

Robot properties
The following sections describe the robot properties you can configure. The properties you can configure depend on robot type, host type, and robot control selections you make in the dialog.

ACSLS host
ACSLS Host applies only to NetBackup Enterprise Server. Specify 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) For an example, see the NetBackup Device Configuration Guide. STK Library Station Storagenet 6000 Storage Domain Manager (SN6000).

Devices Configuring robots and tape drives

599

This STK hardware serves as a proxy to another ACS library software component (such as, ACSLS). Note: STK LibAttach software must also be installed, if the device host that has drives under ACS robotic control is a Windows server. Obtain the appropriate LibAttach software from STK. See the Symantec support Web site for the latest compatibility information. For an overview of ACS robots, see the NetBackup Device Configuration Guide.

DAS server
NetBackup Enterprise Server only. To specify the DAS server for TLM robots that are controlled by an ADIC DAS/SDLC server, enter the name of the DAS/SDLC server. This server is an OS/2 workstation near or within the robot cabinet or a Windows server near the ADIC Scalar library. For an overview of TLM robots, see the NetBackup Device Configuration Guide.

Device host
Device Host applies only to NetBackup Enterprise Server. Specifies the host to which the device is attached.

Library name
TLH robot on NetBackup Enterprise Server only. For UNIX device hosts (except AIX), enter the library name that is configured on the UNIX host. For Windows devices hosts:

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.

For an overview of TLH robots, see the NetBackup Device Configuration Guide.

LMCP device file

NetBackup Enterprise Server on AIX device host only. To specify the LMCP file for TLH robot types, enter the name of the Library Manager Control Point device file name. Use the same name that is configured on the AIX device host.

600 Devices Configuring robots and tape drives

NDMP host name

To specify the host, enter the name of the NDMP host to which the robot is attached.

Port, Bus, Target, and LUN

Windows host only. To specify the SCSI coordinates for the device, enter the Port, Bus, Target, and LUN.

Robot control host

NetBackup Enterprise Server only. Specifies the host that controls the robot. To specify the robot control host for TL8, TLD, or TLH robots, enter the name of the host on which the robot information is defined. For more information about robot control, see Robot control configuration overview on page 602.

Robot control is attached to an NDMP host

NetBackup Enterprise Server only. Specifies that an NDMP host controls the robot. For this type of robot control, you specify the following items:

Robot device path on page 601 NDMP host name on page 600 SCSI coordinates (Windows host) on page 602

Robot control is handled by a remote host

NetBackup Enterprise Server only. Specifies that a host other than the device host controls the robot. For this type of robot control, you can configure the following attributes (based on the robot type and device host platform that you selected):

Robot control host on page 600 DAS server on page 599 ACSLS host on page 598

Robot device
Windows device host only. To specify the robot device, click Browse and then select a robot from the list that appears in the Devices dialog.

Devices Configuring robots and tape drives

601

If the browse operation does not find attached robots, an error dialog appears.

Robotic device file

UNIX device host only. Specifies the device file 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. 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. For information about how to add device files, see the NetBackup Device Configuration Guide.

Robot device path

To specify the robot device path, enter the name of the robotic device that is attached to the NDMP host.

Robot is controlled locally by this device host

Specifies that the host to which the robot is attached controls the robot. For this type of robot control, configure the following fields (depending on the robot type and device host type):

Robotic device file on page 601 Robot device on page 600 LMCP device file on page 599 Library name on page 599

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

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

602 Devices Configuring robots and tape drives

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. For an example, see the NetBackup Device Configuration Guide.

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

SCSI coordinates (Windows host)

The device attributes on Windows system cannot change during NetBackup operation. To specify the SCSI coordinates, enter the Port, Bus, Target, and LUN for the robotic device.

Robot control configuration overview

In the Robot control section you specify the type of control for the robot. Depending on the robot type and the type of media server, various combinations of the robot control buttons are available in the dialog. The following table provides an overview of robot control configuration. The first column indicates the robot control button that is valid for a particular robot type and server platform. The last column shows the configuration information that is required. Table 10-1 Robot control
Local

Robot control configuration overview Robot Type Supported media server platform Information required for configuration

ODL

AIX, Solaris SPARC and HP-UX Robotic device file (except HPIA64), UNIX Windows Robotic device file Robot device or Port, Bus, Target, and LUN

Local Local

TL4, TL8, TLD TL4, TL8, and TLD TLH

Local

All (except Solaris Opteron, HP Library name IA64, AIX, and Linux, and Linux64) AIX LMCP device file

Local

TLH

Devices Configuring robots and tape drives

603

Table 10-1 Robot control

Local

Robot control configuration overview (continued) Robot Type Supported media server platform
AIX, Solaris, Linux, and Linux64 All All All (except Solaris Opteron, Linux64) All (except Linux64 and HP IA64) Windows, AIX, Solaris SPARC, HP-UX (except HP IA64), and Linux (except Linux64)

Information required for configuration

Robotic device file

TSH

Remote Remote Remote

ACS TL8, TLD TLH

ACSLS host Robot control host Robot control host

Remote

TLM

DAS/SDLC server

NDMP

ACS, TL8, TLD, and TLH

NDMP host name and robot device

Library sharing example

The following example applies only to NetBackup Enterprise Server. Figure 10-1 shows library sharing with two servers using two drives in a TL8 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. When you add this robot to the device configuration on eel, select Robot is controlled locally by this device host. When you add the robot to the device configuration on shark, select Robot control is handled by a remote host.

604 Devices Configuring robots and tape drives

Figure 10-1

Robot control host example

TL8 robot (ADIC Scalar 100)

Control

TL8 Robotic Control

Drive 1

Drive 2

eel EMM Database

shark

Adding or changing a drive

Note: Symantec recommends that you use the Device Configuration Wizard to add storage devices. For more information, see Using the Device Configuration Wizard on page 595. Use the following procedures to add or change a tape or optical drive manually. To add a shared drive, see Adding a shared drive on page 605. To configure SCSI reserve on a drive path, see Configuring SCSI reserve on a drive path on page 605. To add a drive 1 2 In the NetBackup Administration Console, select Media and Device Management > Devices. Select one of the following, depending on the type of drive:

Actions > New > Tape Drive Actions > New > Optical Drive

Specify the properties of the drive. The properties depend on the drive type and host server type. For descriptions of the properties, see Drive properties on page 607.

To change a drive 1 In the NetBackup Administration Console, expand Media and Device Management > Devices > Drives.

Devices Configuring robots and tape drives

605

2 3

In the details pane, right-click on the drive you want to change and select Change from the shortcut menu. In the Change Drive or Change Optical Drive dialog box, change the properties of the drive . The properties depend on the drive type and host server type. For descriptions of the properties, see Drive properties on page 607.

Adding a shared drive

Symantec recommends that you use the Device Configuration Wizard to add storage devices. The Device Configuration Wizard is the easiest method for adding shared drives in a Shared Storage Option configuration. For instructions, see Using the Device Configuration Wizard on page 595. Alternatively, you can use the tpconfig command to add shared drives. The tpconfig command does not use device serialization, which can increase the chance for configuration errors. Use the tpconfig command as follows:

tpconfig command line interface. Use the -path <drivepath> option with the -add -drpath command when you define multi-path drives. Use the -add -drive command when you define shared drives. If you add a drive on multiple hosts, it becomes a shared drive. For more information, see NetBackup Commands for UNIX and Linux. tpconfig interactive mode. On UNIX servers, you can use the tpconfig command in interactive mode. If you use tpconfig, ensure all hosts that share a drive use the same case-sensitive name for the drive. For more information about using tpconfig in interactive mode, see Using the tpconfig device configuration utility in the NetBackup Administrators Guide for UNIX and Linux, Volume II.

If you use the tpconfig command, you cannot use diagnostic tools available on UNIX servers, such as device management reports. For information about the NetBackup Shared Storage Option, see the NetBackup Shared Storage Guide.

Configuring SCSI reserve on a drive path

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 is used to configure the protection for each media server. To configure the SCSI reserve host property, see Enable SCSI reserve on page 447 (host property)

606 Devices Configuring robots and tape drives

For each drive path, you can override the media server setting. The following are the options for the Override SCSI Reserve settings drive path attribute:

Server Default. Use the SCSI reserve protection setting configured for the media server. 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 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.

To configure SCSI reserve when adding a drive 1 2 In the Add a New Drive dialog box, click Add. In the Add Path dialog box, choose one of the Override SCSI Reserve settings when you configure the path properties.

To configure SCSI reserve when changing drive properties 1 2 3

In the Change Drive dialog box, select the drive path. Click Change. In the Change Path dialog box, choose one of the Override SCSI Reserve settings. How NetBackup reserves drives in the NetBackup Administrators Guide for UNIX and Linux, Volume II

Devices Configuring robots and tape drives

607

Drive properties
You specify properties when you add a drive or change the properties of a drive. The properties you can specify depend on drive type, server platforms, or NetBackup server types.

Cleaning frequency
Applies to tape drive only. NetBackup does not support drive cleaning in some robot types. For more information, see Robot attributes in the NetBackup Device Configiration Guide. If you want to set up 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 drive is in a robotic library that supports drive cleaning If a cleaning cartridge is defined in that robotic library

608 Devices Configuring robots and tape drives

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

The mount time is reset after the driveis cleaned. If you do not specify a cleaning frequency, you can still use automated drive cleaning with the TapeAlert feature if the following are true:

The drive supports TapeAlert. You configured a cleaning volume for the robot. The host platform, robot type, and drive support drive cleaning. 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

You also can clean drives from the Device Monitor. For more information about drive cleaning, see Drive cleaning overview and Using TapeAlert in the NetBackup Administrators Guide for UNIX and Linux, Volume II

Data/device path
Optical drives on UNIX servers only. The path to the device file for the optical drive. 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. NetBackup uses character-mode device files. If you use NDMP drives, see the NetBackup for NDMP Administrators Guide for configuration information. For more information about device paths, see No rewind device on page 614.

Device host
Optical drive only. NetBackup Enterprise Server only. Specifies the device host for the drive.

Drive status
Applies to tape drive only. When you add a drive, the default drive status is UP, which means the drive is available. When a drive is UP, the default mode is AVR (Automatic Volume Recognition). Exception: optical drives on an HP9000-800 systems are in OPR (operator control) mode when they are UP.

Devices Configuring robots and tape drives

609

To change the drive status, click UP or DOWN. You can also change the drive status using the commands on the Actions menu in Device Monitor.

Drive is in a robotic library

Specifies that the drive is in a robot. If the drive is a stand-alone drive (not in a robot, do not select this option. If you select this option, you must configure the Robotic library and Robot drive number fields.

Drive name
The name that identifies the drive. Each drive name must be unique. Descriptive names are recommended. Drive names are limited to 48 characters. Enter a name for the drive. Alternatively, use drive name rules to create a unique drive name. For information about how to configure rules for naming drives, see Configuring drive name rules on page 611. For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

Drive type
Tape drive only. Specifies the type of drive. If the drive writes WORM media, see Using WORM media on page 589 for more information.

Host and path information list

For tape drives, use the host and path information list 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 1 2 Click Add. In the Add Path dialog box, configure the properties for the drive path. The properties you can specify depend on drive type, server platform, or NetBackup server type.

To change a drive path 1 2 Select the drive path. Click Change.

610 Devices Configuring robots and tape drives

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.

For more information about device paths, see No rewind device on page 614. To configure SCSI reserve, see Configuring SCSI reserve on a drive path on page 605.

Robot drive number

Note: Robot drive number does not apply when you add drives to API robots. See Robot drive number for API robots on page 613. 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. See Correlating device files to physical drives when adding drives in the NetBackup Administrators Guide for UNIX and Linux, Volume II NetBackup does not detect incorrect drive number assignment during configuration; however, an error occurs when NetBackup tries to mount media on the drive.

Robotic library
The robot that controls the drive. This dialog allows you to select any configured robot that can control the drive.

Serial number
This read-only field shows the serial number of the drive.

Use drive name seed

Adding a drive only. Select to use drive name rules to assign names to drives automatically. To configure drive name rules, click Configure. For information about how to configure rules for naming drives, see Configuring drive name rules on page 611.

Devices Configuring robots and tape drives

611

Volume header device path

Optical drives on UNIX servers only. The path to the volume header device file for the optical drive. Enter the path to the volume header device file on the specified host. Volume header 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.

Configuring drive name rules

Use the Configure Drive Name Rules dialog box to configure rules for naming drives automatically. The Device Configuration Wizard uses the rules for naming drives. You can use the rules to name drives when you add them to your configuration manually.

Drive name rules overview

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 first one that you add is named QUANTUM.DLT8000.000, the second one QUANTUM.DLT8000.001, and so on. You can update the global drive name rule. You can create local drive name rules for specific device hosts (each device host can have its own rule). Local 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 Robot number Robot type Drive position Drive position information varies depending on the robot type. Drive position information can be ACS coordinates, TLM/TLH vendor drive name, or the robot drive number. Drive type Serial number

612 Devices Configuring robots and tape drives

Vendor ID Product ID Index

A Custom Text field is also available which accepts any of the allowable drive name characters. For information about the characters you can use in a name, see NetBackup naming conventions on page 631.

How to configure drive name rules

Use the following procedure to configure drive name rules. To configure drive name rules 1 1 In the New Tape Drive dialog, click Configure. In the Add a New Drive dialog, click Configure. Alternatively, if you use the Device Configuration Wizard, click Configure Drive Name Rules in the Device Hosts screen. In the Configure Drive Name Rules dialog, 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 your rule. To add your 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.

Devices Configuring robots and tape drives

613

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

Robot drive number for API robots

The following topic applies to NetBackup Enterprise Server. Robot drive number does not apply when you add drives to the following types of API robots:

ACS robots (Automated Cartridge System). See ACS on page 614 for more information. TLH robots (Tape Library Half-inch). See TLH on page 614 for more information. TLM robots (Tape Library Multimedia). See TLM on page 614 for more information.

614 Devices Configuring robots and tape drives

ACS
To specify a drive in an ACS robot 1 Determine the physical location of the drive within the robot. You must know the physical drive in the robot that the device file you specified earlier represents. You establish this correlation during installation. Select ACS. In the dialog enter the following information: For
ACS Number

2 3

Enter
The index (in ACS library software terms) that identifies the robot that has this drive. The Library Storage Module that has this drive. The robot panel where this drive is located. The physical number of the drive (in ACS library software terms).

LSM Number Panel Number Drive Number

TLH
To specify a drive in a TLH (Tape library half-inch) robot 1 2 Select TLH. In the dialog, enter the IBM device number of the drive within the robot.

TLM
To specify a drive in a TLM (Tape library multimedia) robot 1 2 Select TLM. In the dialog, enter the DAS/SDLC drive name of the drive within the robot.

No rewind device
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.

Devices Configuring server groups for media sharing

615

Configuring server groups for media sharing

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. You can configure server groups that can share media. 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. 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. Media sharing provides the following benefits:

Increases media utilization by reducing the number of partially full media. Reduces media-related expenses because fewer media are required and fewer media are vaulted (NetBackup Vault option). Reduces administrative overhead because you inject fewer scratch media into the robotic library. Increases media life because media 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. Ensure the appropriate connectivity between and among the media servers and robots and drives.

To configure media sharing, you must do the following:

616 Devices Configuring server groups for media sharing

Optionally, configure NetBackup for media sharing by setting the master server Enable Unrestricted Media Sharing for All Media Servers host property. For more information, see Media properties on page 446. Optionally, configure the volume pools to use for media sharing by setting the Maximum number of partially full media property for those pools. For more information, see Adding a new volume pool on page 539 or Changing the properties of a volume pool on page 539. Create the media sharing groups as described in this section. If you allow unrestricted allow media sharing in your NetBackup environment, you do not have to create media sharing groups. Unrestricted media sharing is set by using the master server Enable Unrestricted Media Sharing for All Media Servers host property. Configure backup policies that use the volume pools and media sharing groups by setting the Policy Volume Pool and Media Owner properties of the backup policies. For more information, see Policy Attributes tab on page 87.

To change the owner of a volume, see Changing the owner of a volume on page 520. To create a server group 1 2 3 In the NetBackup Administration Console, select Media and Device Management > Devices > Server Groups. Select Actions > New Server Group. In the New Server Group dialog box, enter or select the appropriate information. 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. For descriptions of the fields, see Server group properties on page 617.

Devices Configuring server groups for media sharing

617

Server group properties

For server group properties, see the following:

Server group name

The name of the server group. You cannot change the name of an existing server group.

Server group type

The type of server group. For a media sharing group, select Media Sharing. A media sharing group is a server group that shares media for write purposes. A media sharing group can contain the following:

NetBackup master server

618 Devices Configuring and managing disk pools

NetBackup media servers NDMP tape servers Virtual host names of NetBackup media servers in a cluster

Other server group types (NOM and Alternate Restore) are reserved for future use.

State
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
A description of the media server group.

Servers in group
The servers (and their type) that belong to the group. To remove a server from the group, select it in the Servers in Group window and click Remove.

Servers not in group

The servers (and their type) that do not belong to the group. To add a server to the group, select it in the Servers Not in Group window and click Add.

Configuring and managing disk pools

A NetBackup disk pool is a logical entity that NetBackup recognizes as disk storage. You can configure disk pools if you install an Enterprise Disk Option license key. For more information, see the following:

For AdvancedDisk, see Creating an AdvancedDisk disk pool on page 726. For OpenStorage and SharedDisk, see the NetBackup Shared Storage Guide or the NetBackup Administration Console help. For PureDisk, see the Veritas NetBackup PureDisk Remote Office Edition Administrators Guide.

Devices Configuring SAN clients and Fibre Transport

619

Configuring SAN clients and Fibre Transport

A NetBackup SAN client is a computer that has critical data that requires high bandwith for backups. It connects to a NetBackup media server over Fibre Channel. A SAN client backs up its own data. NetBackup Fibre Transport is a method of data transfer that uses Fibre Channel and a subset of the SCSI command protocol for data movement over a SAN rather than TCP/IP over a LAN. The NetBackup Fibre Transport service is activate on both the SAN clients and the NetBackup media servers that connect to the storage. For more information about how to configure and use SAN clients and NetBackup Fibre Transport, see the NetBackup Shared Storage Guide.

Managing your device configuration

The following topics explain how to manage the robots and drives in your configuration:

When to perform device configuration changes on page 619 Using the Device Configuration Wizard for changes on page 620 Changing a robot configuration on page 620 Changing the configuration of a drive on page 620 Changing a drive to a shared drive on page 621 Deleting robots on page 621 Deleting drives on page 621 Performing device diagnostics on page 622 Printing your device configuration on page 623

Also see Making changes to your hardware configuration in the NetBackup Administrators Guide for UNIX and Linux, Volume II

When to perform device configuration changes

Do not change your device configuration during backup or restore activity. When you perform some of the following device configuration tasks, you can stop and restart ltid. This action also stops and restarts any robotic processes. ltid is the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows servers. If your configuration changes are

620 Devices Managing your device configuration

complete and you are not in a production environment, answer yes to the stop and restart prompt. Caution: If you stop and restart ltid, any backups, archives, or restores also are stopped.

Using the Device Configuration Wizard for changes

You should update your configuration for all storage-related changes. For example, if you add a new robot or drive, add a new SCSI adapter in a host, and so on. If you run the Device Configuration Wizard in an environment that is already configured, it updates your device configuration.

Changing a robot configuration

To change configuration information for a robot 1 2 3 4 5 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Robots in the tree pane. Select the robotic library you want to change from the Robots pane on the right. Click Edit > Change. In the Change Robot dialog, change the attributes as necessary. For descriptions of the properties, see Robot properties on page 598.

Changing the configuration of a drive

To change configuration information for a drive 1 2 3 4 5 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Drives in the tree pane. Select the drive you want to change from the Drives pane on the right. Click Edit > Change. In the change drive dialog, change the attributes as necessary. For descriptions of the properties, see Drive properties on page 607.

Devices Managing your device configuration

621

Changing a drive to a shared drive

You can 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, select 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, click Add. In the Add Path dialog, configure the properties for the hosts and paths that share the drive.

Deleting robots
Note: Any drives that are configured as residing in a robot that you delete are changed to stand-alone drives. Any media in the deleted robot is also moved to stand-alone. To delete a robot 1 2 3 4 5 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Robots in the tree pane. Select the robotic library you want to delete from the Robots pane. Select Edit > Delete. Answer the delete confirmation dialog.

Deleting drives
To delete a drive 1 In the NetBackup Administration Console, select Media and Device Management > Devices.

622 Devices Managing your device configuration

2 3 4 5

Select Drives in the tree pane. Select the drive or drives that you want to delete from the pane on the right. Select Edit > Delete. Answer the delete confirmation dialog.

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.

Running a drive diagnostic test

Use the following procedure to run a diagnostic test on a drive. To run a drive diagnostic test 1 2 3 4 5 6 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Actions > Drive Diagnostics. In the Drive Diagnostics dialog, 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 prelabelled 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.

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. Complete the requested operation task and then click Continue to resume the test. If you click Details for a test step that requires intervention, you can resume the test by clicking Continue from the Test Details dialog.

Running a robot diagnostic test

Use this procedure to run diagnostic tests on TLD or TL8 robotic libraries. Diagnostic testing is not supported for API-attached robotic tape libraries and other types of SCSI-attached libraries.

Devices Managing your device configuration

623

Ensure that the library to be tested is properly configured for use with NetBackup. Testing is conducted using the existing NetBackup robotic control daemons or processes. To run a robot diagnostic test 1 2 3 4 5 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Actions > Robot Diagnostics. In the Robot Diagnostics dialog box, select the media server that is the Device Host for the robot that you want to test. Select the robot that you want to diagnose in the Robot Name box. Click Start to start the diagnostic tests.

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. Complete the requested operation task and then click Continue to resume the test. If you click Details for a test step that requires intervention, you can resume the test by clicking Continue from the Test Details dialog.

Printing your device configuration

To print your current device configuration 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Devices. In the tree pane select Drives, Robots, Hosts, NDMP Hosts, or Topology. Click in the pane on the right. Select File > Print.

To print your current device configuration using tpconfig The following example uses tpconfig to list the device configuration and redirect the output to the file named devconf.txt, which can then be printed: tpconfig -dl > devconf.txt Note: The tpconfig -d or -l option may truncate drive names. Use tpconfig -dl to obtain the full drive name.

624 Devices Stopping and restarting the device daemon

Stopping and restarting the device daemon

The Media Manager Device daemon (ltid) processes requests to mount and unmount tapes in robotically controlled devices through the robotic control processes. If you stop and restart the device daemon, it stops and restarts the Volume Manager (vmd), the automatic volume recognition process (avrd), and any robotic processes. Caution: If you stop and restart the device daemon, any backups, archives, or restores that are in progress fail. To start/stop the Media Manager Device Daemon 1 2 3 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Actions > Stop/Restart Media Manager Device Daemon. Select a device host (NetBackup Enterprise Server only). If the device host is a Backup Exec server, it does not appear in the list. The dialog box shows the current status of the daemon. Select the action to perform. Select whether to eject media from a stand-alone drive and whether to enable debug logging. The eject operationis a logical one. Click OK or Apply. By using Apply, you can select device hosts and actions for more than one device host before clicking OK to close the dialog.

4 5

External access to NetBackup controlled devices

The Media Manager device daemon ltid restricts access to drives that are in an UP state by changing the permissions of the device files for those drives. The permissions are changed to 0600 when ltid starts and back to their original settings when ltid is terminated. The permission also are returned to their original settings when a drives state is changed to DOWN). Do not modify the permissions of these device files when ltid is active. The NetBackup avrd daemon periodically attempts to rewind and read data from media in the drives that are UP and are not currently assigned in NetBackup. To ensure reliable operation, do not use UNIX tape and drive commands on the drives that are UP and controlled by ltid. Users can use the NetBackup tpreq

Devices Activating and deactivating media servers

625

and tpunmount commands and the drive_mount_notify and drive_unmount_notify scripts on those drives. To use UNIX commands on a drive, the drive must be down and ltid must not be running.

Activating and deactivating media servers

When you activate a media server, NetBackup can use it for backup and resotre jobs. When you deactivate a media server, backup jobs cannot send it data (the drive is offline. For example, you may deactivate a media server to perform maintenance. When a media server is deactivated:

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.

To activate or deactivate a host 1 2 3 In the NetBackup Administration Console, select Media and Device Management > Media Servers. From the Media Servers pane, select the media server to activate or deactivate. Select Actions > Activate or Deactivate.

Accessing media and devices on other hosts

For NetBackup to access media and device management functionality on a remote host, you may need to add a SERVER entry to the vm.conf file on the remote host. SERVER entries are used for security as shown in the following table. You can add entries that allow only specific hosts to access those capabilities remotely. If the vm.conf file on a remote host contains
No SERVER entries

Then
A host can mange media and devices on the remote host if it is is added to the bp.conf file of the server you logged into. You do not need to add a SERVER entry to the vm.conf file. You must add a SERVER entry for the host on which the NetBackup Administration Console is running (the server you logged into).

Any SERVER entries

626 Devices The Enterprise Media Manager server

Example SERVER entries

Assume that you have three hosts named eel, yak, and shark. You want to centralize device management on host shark and also permit each host to manage its own devices.

The vm.conf file on shark contains the following: SERVER = shark The vm.conf file on shark does not require any additional SERVER entries, because all device management for shark are performed from shark. The vm.conf file on eel contains the following, which allows eel to manage its own devices and permits shark to access them.: SERVER = eel SERVER = shark The vm.conf file on yak contains the following, which allows yak to manage its own devices and permits shark to access them: SERVER = yak SERVER = shark

The Enterprise Media Manager server

The Enterprise Media Manager (EMM) server is a NetBackup host that manages device and media information. The Enterprise Media Manager service runs on the EMM server, and the EMM database resides on the EMM server. A NetBackup master server can have only one EMM server. However, an EMM server can manage device and media information for more than one NetBackup master server. An EMM domain comprises all of the master and the media servers for which it manages device and media information. For information about the EMM database, see Enterprise Media Manager (EMM) database on page 281.

Managing the EMM server

The following topics explain the commands that are used to manage the EMM server. To remove a device host from the database NetBackup Enterprise Server only. 1 In the NetBackup Administration Console, select Media and Device Management > Devices.

Devices The Enterprise Media Manager server

627

Select Actions > Enterprise Media Manager Database > Remove Device Host.

To synchronize the database This procedure updates the device database on NetBackup 5.x servers to be consistent with the device configurations in the EMM server. Usually, you do not have to synchronize the EMM database with device databases on a back-level media server. However, if you have problems after recent configuration changes to your local device hosts, you should synchronize. 1 2 In the NetBackup Administration Console, select Media and Device Management > Devices. Select Actions > Enterprise Media Manager Database > Synchronize Enterprise Media Manager Database.

EMM server requirements

The following are the NetBackup requirements for using the EMM server:

The EMM server must be installed on a system that hosts a NetBackup master or media server. Symantec recommends that you install the EMM server on the same system as a NetBackup master server. If the EMM domain contains more than one NetBackup master server, each master server must be allowed access to the EMM server. Use the Servers host property on the EMM server to allow access. The hosts for all devices and media that are managed by a NetBackup master server must use the same EMM server. Users cannot share devices or volumes between EMM domains. Media IDs must be unique within an EMM domain. Barcodes must be unique within an EMM domain. Drive names must be unique within an EMM domain. Robot numbers must be unique within an EMM domain. Host names must be consistent within an EMM domain. Do not use a fully qualified name and an unqualified name to refer to the same host. Do not use a physical name and a virtual host name to refer to the same host.

628 Devices The Enterprise Media Manager server

Note: Beginning with release 6.0, NetBackup allocates drives before it starts jobs on a media server. Therefore, NetBackup 6.0 and later may pre-empt drive selections on NetBackup 5.x media servers. To optimize resource allocation in your environment, you should update all media servers to release 6.0 or later.

Chapter

11

Credentials
Credentials appears only if a feature that requires external credentials is licensed. Use Media and Device Management > Credentials to add, remove, and manage log-in credentials for:

Disk array hosts. For disk array host credentials, see the SharedDisk section of the NetBackup Shared Storage Guide. NDMP hosts. For NDMP host credentials, see the NetBackup for NDMP Administrators Guide. Storage servers. For OpenStorage server credentials, see the OpenStorage section of the NetBackup Shared Storage Guide.

630 Credentials

Chapter

12

Management topics
This chapter contains the topics that are related to the administration and management of NetBackup.

NetBackup naming conventions on page 631 Using wildcards in NetBackup on page 632 To power down and reboot NetBackup servers on page 633 Using the NetBackup license utility to administer licenses on page 638 To administer a remote master server on page 639 To administer devices on other servers on page 649 Using the NetBackup-Java Windows display console on page 651 Configuring the NetBackup-Java administration console on page 652 NetBackup-java performance improvement hints on page 667 Managing client restores on page 672 Goodies scripts on page 687 Alternate server restores on page 687 Using NetBackup with Storage Migrator on page 694

NetBackup naming conventions

The following set of characters can be used in user-defined names, such as storage units and policies. These characters are used for foreign languages as well.

Alphabetic (A-Z a-z) (names are case-sensitive) Numeric (0-9) Period (.)

632 Management topics Using wildcards in NetBackup

Plus (+) Minus (-) Underscore (_)

Do not use a minus as the first character. Spaces are only allowed in a comment for a drive.

Using wildcards in NetBackup

NetBackup recognizes the following wildcard characters in areas where wildcards can be used. (For example, paths in the backup selections list and exclude file lists.) Table 12-1 * Wildcard use in NetBackup

Wildcard for zero or more characters. For example: r* refers to all files that begin with r r*.doc refers to all files that begin with r and end with .doc. To back up all files that end in .conf, specify: /etc/*.conf

Wildcard for any single character (A through Z; 0 through 9). For example: file? refers to file2, file3, file4 file?? refers to file12, file28, file89 To back up all files named log01_03, log02_03, and so on, specify: c:\system\log??_03

[ ]

Use a pair of square brackets to indicate any single character or range of characters separated with a dash. For example: file[2-4] refers to file2, file3, file4 file[24] refers to file2, file4 *[2-4] refers to file2, file3, file4, name2, name3, name4

{ }

Use a pair of curly brackets to indicate multiple file name patterns. Separate the patterns by commas only; no spaces are permitted. A match is made for any or all entries. For example: {*1.doc,*.pdf} refers to file1.doc, file1.pdf, file2.pdf

To use wildcard characters literally, precede the character with a backslash (\).

Management topics To power down and reboot NetBackup servers

633

A backslash (\) acts as an escape character only when it precedes a special or a wildcard character. NetBackup normally interprets a backslash literally because a backslash is a legal character to use in paths. Assume the brackets in the following are to be used literally: C:\abc\fun[ny]name In the exclude list, for example, precede the brackets with a backslash: C:\abc\fun\[ny\]name

To power down and reboot NetBackup servers

To close down and restart NetBackup servers, use the following recommended procedures. To power down a server 1 2 In the NetBackup Administration Console, click Activity Monitor, then select the Jobs tab to make sure no backups or restores are running. Use the NetBackup Administration Console or the command line to stop the NetBackup Request daemon, bprd. Stop bprd to stop additional backup and restore activity and to allows current activity to end gracefully:

In the NetBackup Administration Console, click Activity Monitor, then select the Processes tab. Right-click the request daemon (bord) and select Stop Daemon. From the command line, run: /usr/openv/netbackup/bin/admincmd/bprdreq -terminate

Note: bprdreq does not run on a media server. 3 Run the system shutdown command. Note: The installation process copies the appropriate startup and shutdown script from /usr/openv/netbackup/bin/goodies to /init.d and creates links to it from the appropriate /rc directory. Use system startup scripts to begin the Media Manager and NetBackup daemons when the system boots up. Use shutdown scripts to terminate the daemons at system shutdown. See the NetBackup Installation Guide for instructions on how to edit the script. 4 Power down the server.

To shut down all NetBackup daemons From a command line, enter:

634 Management topics To power down and reboot NetBackup servers

/usr/openv/netbackup/bin/bp.kill_all To start up all NetBackup daemons From a command line, enter: /usr/openv/netbackup/bin/bp.start_all To reboot a NetBackup master server 1 2 3 Restart the system. Ensure that bprd, bpdbm, and vmd are up by running the following script: /usr/openv/netbackup/bin/bpps -a Start all NetBackup daemons: /usr/openv/netbackup/bin/bp.start_all

To reboot a NetBackup media server 1 2 Restart the system. Start ltid if it is not already running: From the NetBackup Administration Console: a b Click Activity Monitor, then select the Processes tab. Right-click ltid and select Start Daemon. From the command line, run: /usr/openv/volmgr/bin/ltid

Displaying active processes with bpps

NetBackup provides the bpps script that determines which NetBackup processes are active on a UNIX system. bpps is located in the following directory:
/usr/openv/netbackup/bin/bpps

The following is example output:

root root 310 0.0 306 0.0 0.0 0.0 176 276 0 ? 0 ? IW Oct 19 IW Oct 19 15:04 /usr/openv/netbackup/bin/bpdbm 2:37 /usr/openv/netbackup/bin/bprd

Prevent bpps from displaying processes you do not want to check by adding the processes to an exclude list. Refer to comments within the script for more information. To display both NetBackup and Media Manager options, run:
/usr/openv/netbackup/bin/bpps -a

Management topics Administering NetBackup licenses

635

Displaying robotic processes with vmps

The vmps script shows the Media Manager daemons and robotic processes that are active on a UNIX system. You can execute this script using the following command:
/usr/openv/volmgr/bin/vmps

In the following sample display, the second column contains the process IDs for the processes.
root root root root root 303 305 306 307 310 0.0 0.0 0.0 0.0 0.0 0.2 0.0 0.0 0.0 0.0 136 156 104 68 116 264 0 0 56 0 ? ? ? ? ? S IW IW S IW Feb Feb Feb Feb Feb 11 4:32 ltid -v 11 0:54 vmd -v 11 0:15 tl8d -v 11 12:16 avrd 11 0:07 tl8cd -v

Status for the nbemm command is not shown in the output of vmps. The nbemm status is shown in the output of the bpps script.

Administering NetBackup licenses

The license key for each system is entered when the software is installed. The license can be modified later to add separately-priced options. Note: Restart the NetBackup Administration Console after any license updates. To access license keys for a NetBackup server 1 To view the license keys of the current server: In the NetBackup Administration Console, click Help > License Keys. To view the license keys of another server: Click File > Change Server, then select another server. Click Help > License Keys. Select the license details to view:

Summary of active 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. Summary of active capacity-based licensed features: 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 1 terabyte = 1,099,511,627,776 bytes.

636 Management topics Administering NetBackup licenses

The OpenStorage Disk Option, the PureDisk Storage Option, and the Virtual Tape Option do not display all values at this time.

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

each license key, the server where the key is registered, when the key was registered, the features that the key provides, and whether the feature is active or inactive.

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

Add a new license Delete a license View the properties of one license Export the license list

To add new license keys 1 2 In the NetBackup License Keys dialog box, click New. In the Add a New License Key dialog box, enter the license key and click Add. The new license key appears in the license list.

Note: Restart all the NetBackup utilities (including NetBackup-Java Administration Console) after deleting the license keys. To print license key lists 1 In the NetBackup License Keys dialog box, select the license key you want to print. If no selection is made, all licenses are printed. The printed information includes:

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

Management topics Administering NetBackup licenses

637

2 3

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

To delete license keys 1 2 3 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 Delete. A confirmation dialog box appears. Click Yes to delete all the features that are associated with the key. The license key cannot be restored. If the key appears in the list more than one time, to delete one instance deletes all other instances of the key from the list.

Note: Restart all the NetBackup utilities (including NetBackup-Java Administration Console) after deleting the license keys. To view the properties of a license key In the NetBackup License Keys dialog box, select one license and click Properties. To export license keys 1 2 In the NetBackup License Keys dialog box, click Export. The Export File Name dialog box appears. Enter the path and file name where youd like 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

638 Management topics Using the NetBackup license utility to administer licenses

Using the NetBackup license utility to administer licenses

To start the NetBackup license key utility Run /usr/openv/netbackup/bin/admincmd/get_license_key command. The License Key Utility menu appears:
License Key Utility ------------------A) Add a License Key D) Delete a License Key F) List Active License Keys L) List Registered License Keys H) Help q) Quit License Key Utility

At the prompt, enter one of the following menu selections, then press Enter:

Type A to add a new license key, then type the license key at the prompt. Type D to delete a license from the list, then type the license key at the prompt. Type F to list only the licenses that are currently active. Expired licenses do not appear in this listing. Specify a local or a remote host. Type L to list all registered licensesactive or inactive. Specify a local or a remote host. Type H for help on the License Key Utility. Type q to quit the utility.

Management topics To administer a remote master server

639

To administer a remote master server

If the site has multiple master servers, you can configure the systems so multiple servers can be accessed from one NetBackup Administrator Console. To access remote servers:

First, make the remote server accessible to the local server. For more information, see the following section, To add a NetBackup server to a server list on page 639. Second, indicate the remote server you want to administer. See To choose a remote server to administer on page 644.

To add a NetBackup server to a server list

For a local host to administer a remote server, the name of the local host must appear in the server list of the remote server. For example, assume server grape wants to administer host apricot remotely.
grape Server grape wants to administer host apricot

apricot

640 Management topics To administer a remote master server

Grape selects File > Change Server and types apricot as the host name.
grape

If grape is not listed on the server list of apricot, grape receives an error message after trying to change servers to apricot. Assume that apricot is an authorized NetBackup server. A message appears that indicates server grape is invalid because it does not appear on the server list of apricot.

To add grape to the server list of apricot, follow the steps in To add a server to a UNIX server list. For other reasons why a remote server may be inaccessible, see If you cannot access a remote server on page 648. Note: To log in to a remote master server through the log in dialog box, the name of the local host does not need to appear in the server list of the remote server. This method to log in to a remote host is explained in To indicate a remote system upon log in on page 645.

Management topics To administer a remote master server

641

To add a server to a UNIX server list 1 Access the server properties of the destination host using one of the following methods:

Log in to apricot from grape (provided the user name has sufficient privileges), or log in at apricot

Start the NetBackup-Java Administration Console (jnbSA) on the local server (grape). Indicate destination host apricot on the log in dialog box. The jnbSA command is described in NetBackup Commands for UNIX and Linux. Start the NetBackup-Java Windows Display Console on a Windows system. Indicate destination host apricot on the log in dialog box. Physically go to the destination host and start jnbSA. Physically go to the destination host (apricot) and start jnbSA. Indicate apricot on the log in dialog box.

In the NetBackup Administration Console, expand Host Properties > Master Servers.

642 Management topics To administer a remote master server

Double-click the server name (apricot) to view the properties.

Host properties of apricot

Currently, apricot allows remote access by two additional servers: apple and banana

Select Servers to display the server list. The Additional Servers list contains, as the dialog box explains, Servers that can access the currently selected host. Since the Additional Servers list does not include server grape, apricot considers grape to be an invalid server. To add a server to the server list, click Add. The New Server dialog box appears. Type the server name (grape) in the field and click Add to add the server to the list. Click Close to close the dialog box without adding a server to the list.

5 6

Management topics To administer a remote master server

643

Restart all daemons and utilities on the server where the host properties were changed to ensure that the new configuration values are used. Restart the NetBackup Administration Console as well.

Apricot now includes grape among the servers to which it allows remote access

Note: The bp.conf file on every UNIX server contains SERVER and possibly MEDIA_SERVER entries. The server list in the properties dialog box represents these entries. Hosts that are listed as media servers have limited administrative privileges. To add a server to a Windows server list 1 2 3 4 Go to the destination host and start the NetBackup Administration Console. Expand Host Properties > Master Server. Double-click the server name to view the properties. Select the Servers tab to display the server list. The server list contains, as the dialog box explains, Servers that can access the currently selected host. To add a server to the Additional Server List, click Add. Enter the server name in the New Server dialog box. Click Add or Close. Restart all services on the server where the change was made to ensure that the new configuration values are used. Restart the NetBackup Administration Console as well.

5 6 7

644 Management topics To administer a remote master server

To choose a remote server to administer

Indicate a remote server using one of the following methods:

Select the File > Change Server menu command. Specify the remote server in the host name field to start the NetBackup-Java console.

To use the change server command to administer a remote server 1 Start the NetBackup Administration Console on a NetBackup-Java capable machine:

Any NetBackup master server

NetBackup-Java capable UNIX client or server

Log in and run jnbSA: /usr/openv/java/jnbSA 2 3 4 5 In the NetBackup Administration Console log in screen, specify the local server to manage. Click Login. Select Master Server in the left pane (tree view) of the NetBackup Administration Console. Select File > Change Server.

Type or select the host name and click OK.

Management topics To administer a remote master server

645

Note: If the user has the necessary permissions on both machines, the user can transition from Master A to Master B without setting up trust relationships. If the users identity has administrative privileges on Master B but is different from the users identity on Master A, the user is required to reauthenticate. Reauthenticate from the NetBackup Administration Console by using File > Login as New User... for Windows. Or, close and reopen the NetBackup-Java Administration Console. To indicate a remote system upon log in 1 2 Log in to the NetBackup client or server where you want to start the NetBackup Administration Console. Start the NetBackup Administration Console on the local system:

For example, to start the console on a Solaris system named tiger: Log in on tiger and run the following command line:

Any NetBackup master server tiger NetBackup-Java capable UNIX client or server shark

bear Windows system with Windows Display Console installed

/usr/openv/java/jnbSA

To start the console on a Windows system named bear: From the Windows desktop, select Start > Programs > Veritas NetBackup > NetBackup-Java Version 6.5. (The system must have the Windows Display Console installed.) The log in screen appears. In the Host name field, type the name of the remote NetBackup server you want to manage.

646 Management topics To administer a remote master server

In this example, shark.

Type in the name of the remote server youd like to administer

Type in the user name and password for an authorized NetBackup administrator (for example: root), then click Login. This process logs you in to the NetBackup-Java application server program on the specified server. The NetBackup Administration Console appears. The console program continues to communicate through the server you specified for the remainder of the current session.

Administer a master server by using a NetBackup client

The NetBackup Administration Console on a client is useful to administer a NetBackup server remotely. (No NetBackup server software is installed.) Run the NetBackup Administration Console on a client under the following conditions:

On a Windows client if the NetBackup-Java Windows Display Console is installed. On a UNIX client if the client is NetBackup-Java capable.

Management topics To administer a remote master server

647

Using the Remote Administration Console

You can install the Remote Administration Console on a Windows machine to remotely manage a Windows or UNIX server. No license is required to install the Remote Administration Console. After the Remote Administration Console installation, the Administration Console and the client software is installed. The presence of the client software enables the machine to be backed up like any other client. No master or media server software is installed. Figure 12-1 Remote Administration Console selection on installation screen

Click here to install the Remote Administration Console and client software. No server software is installed.

In Figure 12-2, the administrator can use the administration console on console1 to add a comment for a drive on media_server1. The administrator can manage NetBackup on master_server1 or media_server1 from any of the systems. Console1 must be listed in the server list on master_server1 but does not need to be listed on media_server1 because it is a media server.

648 Management topics To administer a remote master server

Figure 12-2

Remote administration example

console1 Windows 2000 NetBackup Remote Administration Console Server list: master_server1 media_server1

master_server1 Windows 2000 bp.conf file SERVER=master_server1 Master server

media_server1 UNIX Media server Server list: master_server1 media_server1 console1

Start the Remote Administration Console, then select File > Change Server to change to a NetBackup server.

If you cannot access a remote server

To administer a server from another master server make sure that the following conditions are true:

The destination server is operational. NetBackup daemons are running on both hosts. The network connection is valid. The user has administrative privileges on the destination host. The current host is listed in the server list of the destination host. For more information, see To add a NetBackup server to a server list on page 639. The host does not need to be listed if the host is a media server or a client. Or, if only media and device management or monitoring is to take place. To ensure that all appropriate NetBackup processes use the new server entry, stop and restart the following processes:

The NetBackup Database Manager and NetBackup Request Manager services on the remote server if it is Windows. The NetBackup Database Manager (bpdbm) and NetBackup Request Manager (bprd) on the remote server if it is UNIX.

Authentication is set up correctly, if used.

Management topics To administer devices on other servers

649

For problems changing servers to configure media or devices or monitor devices, verify that the NetBackup Volume Manager is running on that server. If you cannot access devices on the remote host, it may be necessary to add a SERVER entry to the vm.conf file on that host. See the NetBackup Administrators Guide, Volume II for instructions.

To administer devices on other servers

NetBackup Enterprise Server only. The NetBackup Administration Console on the master server is the central management console for NetBackup servers, NetBackup clients, and storage devices in your environment. You can configure and manage the storage devices on all of the media servers in your NetBackup environment from an Administration Console connected to the master server. Alternatively, you can administer the devices on a specific media server from an Administration Console connected to that media server. To do so, change to or log into the media server by using one of the following methods:

Select the File > Change Server menu command in an existing instance of the Administration Console and change to the media server. Start the NetBackup Administration Console on the media server. Specify the remote server in the host name field and start the NetBackup-Java console.

For instructions, see To choose a remote server to administer on page 644. For device discovery, configuration, and management to occur, the following must be true:

The devices must be configured correctly in the operating system of the media server host. The media server must be in the additional servers list on the NetBackup master server and the EMM server. Normally, the EMM server resides on the same machine as the NetBackup master server. The EMM server must be up and running, both when you install the media server software and when you configure the devices.

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.

650 Management topics To administer devices on other servers

The following procedure assumes that all other steps to add a media server are accomplished. For the procedures, see Adding a media server in the NetBackup Administrators Guide, Volume II. To register a media server 1 2 Start the EMM service on the EMM server. On the EMM server host, run the following command (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

Note: To avoid problems with NetBackup, ensure that the host name you use in NetBackup matches the host name in your TCP/IP configuration. For more information about nbemmcmd, see NetBackup Commands for UNIX and Linux.

Management topics Using the NetBackup-Java Windows display console

651

Using the NetBackup-Java Windows display console

This section describes how to restrict use of the NetBackup-Java Windows Display Console. It describes the following methods:

How to authorize NetBackup-Java users on a Windows system. How to restrict access to NetBackup-Java applications on a Windows system. How to authorize users to use a subset of the NetBackup-Java administrator applications.

To authorize NetBackup-Java users on Windows

To use the NetBackup-Java Windows Display Console, first log in to the NetBackup-Java application server. The application server is on the NetBackup host where you want to perform NetBackup administration or user operations. To log in to the application server, log in to the dialog box that appears when the console is started. (Either the Windows Display Console or the NetBackup Administration Console on a UNIX system.) Provide a valid user name and password for the system that is specified in the NetBackup host field of the log in dialog box. The user name for Windows must be of the form: domainname\username domainname specifies the domain of the NetBackup host. The domain is not required if the NetBackup host is not a member of a domain. The NetBackup-Java application server authenticates the user name and password by using standard Windows authentication capabilities for the specified computer. If NetBackup Access Control is not configured for the users, by default the NetBackup-Java application server provides authorization data. The authorization data allows all users that are members of the administrator group for the hosts domain to use all the NetBackup-Java applications. Other users are allowed to access only Backup, Archive, and Restore. To restrict access to NetBackup-Java or some of its applications, create a nbjava_install_path\java\auth.conf authorization file. For more information, see To restrict access on Windows on page 651 and Configuring the NetBackup-Java administration console on page 652.

To restrict access on Windows

To restrict access to one or more of the NetBackup-Java applications, create the following file on the Windows system: nbjava_install_path\java\auth.conf

652 Management topics Configuring the NetBackup-Java administration console

Add an entry in auth.conf for each user that accesses NetBackup-Java applications. The existence of this file, along with the entries it contains, prohibits unlisted users from accessing NetBackup-Java applications on the Windows system. The following is a sample auth.conf file on a Windows system:
mydomain\Administrator ADMIN=ALL JBP=ALL mydomain\joe ADMIN=ALL JBP=ALL * ADMIN=JBP JBP=ENDUSER+BU+ARC

For more information, see Authorizing NetBackup-Java users on page 654.

Configuring the NetBackup-Java administration console

The following topics contain information about the NetBackup-Java Administration Console. On Windows systems, the console is also referred to as the NetBackup-Java Windows Display Console.

NetBackup-Java administration console architectural overview

The NetBackup-Java Administration Console is a distributed application that consists of two separate system processes:

The NetBackup Administration Console graphical user interface

Available on UNIX by running jnbSA Available on Windows by installing the NetBackup-Java Windows Display Console

The application server (bpjava processes)

These processes may be run on two physically different NetBackup hosts. This distributed application architecture holds true for the UNIX Backup, Archive, and Restore client graphical user interface (jbpSA) as well. The administrator first starts the NetBackup-Java Administration Console interface. Use one of two methods:

Run the jnbSA command on UNIX Select Start >Veritas NetBackup > NetBackup-Java Version 6.5 on a Windows system on which the Windows Display Console is installed

Then, the administrator logs in to the application server on the host that is specified in the login dialog box.

Management topics Configuring the NetBackup-Java administration console

653

Note: The host that is specified in the login dialog box and the system that runs the NetBackup Administration Console must run the same NetBackup version. The application server of the host that is specified in the NetBackup Administration Console login dialog box authenticates the login credentials of the user. The credentials are authenticated by using standard UNIX user account data and associated APIs. The login credentials must be valid on the host that is specified in the login dialog box. Figure 12-3 NetBackup login dialog box

Application server

User name and password must be valid on application server

The server that is usually the object of all administrative tasks is the host specified in the NetBackup Administration Console login dialog box. An exception is the use of the File > Change Server capability in the NetBackup Administration Console. The Change Server capability allows administration of a remote server (a server other than the one specified in the NetBackup Administration Console login dialog box). Figure 12-4 Change Server dialog box

Remote server

Regardless of the which server is administered, all administrative tasks that are performed in the NetBackup Administration Console make requests of the

654 Management topics Configuring the NetBackup-Java administration console

application server. All tasks are run on the application server host, whether the server is remote or whether the server is specified on the login dialog box. However, regardless of which NetBackup authorization method is configured, authorization for tasks in the Administration Console is specific to the server being administered. For example, NetBackup-Java authorization capabilities are in use on Host_A. Use Change Server to change to Host_B. The permissions are honored as configured in the auth.conf on Host_B. For successful administration of a remote server, the application server host must be included in the server list of the remote server. For more information, see To add a NetBackup server to a server list on page 639. Figure 12-5 Host properties server list

In earlier releases, this context (to change to a remote server from the application server) also applied to the enhanced authentication and authorization capabilities. NetBackup encourages the use of Symantec Product Authentication and Authorization for NetBackup Access Control (NBAC) instead of legacy security implementations. For information about how enhanced authorization and authentication applies in this context, see the NetBackup 6.0 documentation.

Authorizing NetBackup-Java users

NetBackup offers access control through the Access Management utility in the NetBackup Administration Console. For instructions on how to install the necessary components to use Access Management, see the NetBackup Security and Encryption Guide.

Management topics Configuring the NetBackup-Java administration console

655

If NetBackup Access Control is not configured, you may still authorize users of the NetBackup-Java administration console for specific applications. For more information, see USE_NBJAUTH_WITH_ENHAUTH on page 666. NetBackup Access Control, when configured as described, always takes precedence over the capabilities authorization of NetBackup-Java as described in To configure nonroot usage on page 658. When NetBackup Access Control is configured, but a user is not authorized as a NetBackup administrator, the capabilities allowed to this user in the Backup, Archive, and Restore (jbpSA) application are those specified for the user in the auth.conf file resident on the host specified in the NetBackup-Java login dialog box. Users of the NetBackup-Java interfaces must log in to the NetBackup-Java application server that is on the NetBackup host where they want to perform administrator or user operations. The /usr/openv/java/auth.conf file contains the authorization data for accessing NetBackup-Java applications. This file exists only on NetBackup-Java capable machines where the NetBackup-Java interface software is installed. The default auth.conf file provides the following authorizations:

On NetBackup servers: Administration capabilities for the root user and user backup and restore capabilities for all other users. On NetBackup clients: User backup and restore capabilities for all users.

On all other UNIX NetBackup systems, the file does not exist but the NetBackup-Java application server provides the same default authorization. To change these defaults on other UNIX systems, you must create the /usr/openv/java/auth.conf file. To perform remote administration or user operations with jbpSA a user must have valid accounts on the NetBackup UNIX server or client machine. Note: Nonroot or non-administrator users can be authorized to administer Windows NetBackup servers remotely from the NetBackup-Java Console. Do so by setting up authorization in the auth.conf file on the Windows server. The auth.conf file must contain entries for the UNIX user names that are used in the login dialog box of the NetBackup-Java Console. The auth.conf file must reside in install_path\VERITAS\java on each Windows server you want to provide nonroot administration capability. Without an auth.conf file, the user has the same privileges on the remote server as on the server that is specified in the login screen. User privileges are the same if auth.conf does not contain an entry for the user name even though host authorization between the two is configured. (SERVER entries in the configuration of each.)

656 Management topics Configuring the NetBackup-Java administration console

Authorization file characteristics

The released version of the UNIX /usr/openv/java/auth.conf file is installed on all NetBackup-Java capable hosts and contains only the following entries:
root ADMIN=ALL JBP=ALL * ADMIN=JBP JBP=ENDUSER+BU+ARC

The first field of each entry is the user name that is granted access to the rights that the entry specifies. In the released version, the first field allows root users to use all of the NetBackup-Java applications. An asterisk in the first field indicates that any user name is accepted and the user is allowed to use the applications as specified. If the auth.conf file exists, it must have an entry for each user. Or, the auth.conf file must have an entry that contains an asterisk (*) in the username field; users without entries cannot access any NetBackup-Java applications. Any entries that designate specific user names must precede a line that contains an asterisk in the username field.

Note: The asterisk specification cannot be used to authorize all users for any administrator capabilities. Each user must be authorized by using individual entries in the auth.conf file. To deny all capabilities to a specific user, add a line that indicates the user before a line that starts with an asterisk. For example:
mydomain\ray ADMIN= JBP= * ADMIN=JBP JBP=ENDUSER+BU+ARC

The remaining fields specify the access rights.

The ADMIN keyword specifies the applications that the user can access. ADMIN=ALL allows access to all NetBackup-Java applications and the related administrator-related capabilities. To allow the use of only specific applications, see Authorizing nonroot users for specific applications on page 658. The JBP keyword specifies what the user can do with the Backup, Archive, and Restore client application (jbpSA). JBP=ALL allows access to all Backup, Archive, and Restore capabilities, including those for administration. To allow only a subset of those capabilities, see Capabilities authorization for jbpSA on page 659. An asterisk in the first field indicates that any user name is accepted and the user is allowed to use the applications as specified. The second line of the released version contains an asterisk in the first field. The

Management topics Configuring the NetBackup-Java administration console

657

asterisk means that NetBackup-Java validates any user name for access to the Backup, Archive, and Restore client application (jbpSA). JBP=ENDUSER+BU+ARC allows end users to back up, archive, and restore files only. The user name and password that is entered in the login screen must be valid on the machine that is specified in the host field. (True for starting the NetBackup-Java administration console or the Backup, Archive, and Restore application (jbpSA).) The NetBackup-Java application server authenticates the user name and password by using the system password file data for the specified machine. The password must be the same password that was used upon login at that machine. For example, assume you log in with the following information:
username = joe password = access

Here you must use the same user name and password to log into NetBackup-Java. Note: The NetBackup-Java login box accepts passwords greater than eight characters. However, only the first eight are significant upon login to a NetBackup-Java application server on a UNIX system. You can log in to the NetBackup-Java application server under a different user name than the name used to log in to the operating system. For example, if you log in to the operating system with a user name of joe, you could subsequently log in to jnbSA as root. Upon exit, some application state information is automatically saved in the directory of joe $HOME/.java/.userPrefs/vrts directory. (For example, table column order.) The information is restored the next time you log in to the operating system under account joe and initiate the NetBackup-Java application. This login method of is useful if there is more than one administrator because it saves the state information for each administrator. Note: NetBackup-Java creates a users $HOME/.java/.userPrefs/vrts directory the first time an application is exited. Only NetBackup-Java applications use the .java/.userPrefs/vrts directory. If the user name is not valid as determined by the contents of the auth.conf file, an error message appears. All applications are inaccessible to the user:
No authorization entry exists in the auth.conf file for username name_specified_in_login_dialog. None of the NB-Java applications are available to you.

To summarize, two types of entries are contained in the auth.conf file:

658 Management topics Configuring the NetBackup-Java administration console

The defaults allow anyone with any valid user name to use the Backup, Archive, and Restore client application (jbpSA).Only root users can access the administrator applications and the administrator capabilities in jbpSA. Specify entries for valid user names.

Note: The validated user name is the account the user can back up, archive or restore files from or to. The Backup, Archive, and Restore application (jbpSA) relies on system file permissions when to browse directories and files to back up or restore.

To configure nonroot usage

Authorizing nonroot users for specific applications
Nonroot users can be authorized for a subset of the NetBackup-Java administrator applications. To authorize users for a subset of the NetBackup-Java administrator applications, use the following identifiers for the ADMIN keyword in the auth.conf file: Table 12-2 Abbreviation
ALL

auth.conf ADMIN identifiers for administrator applications Description

Indicates that the user has administrative privileges for all of the applications that are listed in this table. Activity Monitor Bare Metal Restore Backup Policy Management Backup, Archive, and Restore Catalog Device Monitor Host Properties Media Management Reports Storage Unit Management Vault Management

AM BMR BPM BAR or JBP CAT DM HPD MM REP SUM VLT

Management topics Configuring the NetBackup-Java administration console

659

For example, to give a user (user1) access only to the Device Monitor and Activity Monitor, add the following entry to the auth.conf file:
user1 ADMIN=DM+AM

In order for a nonroot user to modify the files that the NetBackup-Java Administration Console uses, run the nonroot_admin_nbjava script. The script changes permissions on the following files:
/usr/openv/java/auth.conf /usr/openv/java/Debug.properties /usr/openv/java/nbj.conf

Note: nonroot_admin_nbjava is located in /usr/openv/java/nonroot_admin_nbjava.

Capabilities authorization for jbpSA

Capabilities authorization in the Backup, Archive, and Restore interface enables certain parts of the user interface to allow one to perform certain tasks. Not all tasks can be performed successfully without some additional configuration. The following require additional configuration and are documented elsewhere:

Redirected restores. For more information, see Managing client restores on page 672. User backups or archives require a policy schedule of these types and the task to be submitted within the time window of the schedule.

To authorize users for a subset of Backup, Archive, and Restore capabilities, use the following identifiers for the JBP keyword in the auth.conf file:

ENDUSER - Allows users to perform restore tasks from true image, archive, or regular backups plus redirected restores. BU - Allows users to perform backup tasks. ARC - Allows users to perform archive tasks. The capability to perform backups (BU) is required to allow archive tasks. RAWPART - Allows users to perform raw partition restores. ALL - Allows users to perform all actions, including server-directed restores. (Restores to a client that is different from the client that is logged into.) Server-directed restores can only be performed from a NetBackup master server.

For example, to allow a user (user1) to restore but not backup up or archive files:
user1 ADMIN=JBP JBP=ENDUSER

660 Management topics Configuring the NetBackup-Java administration console

Runtime configuration options

On UNIX systems, file /usr/openv/java/nbj.conf contains configuration options for the NetBackup-Java Administration Console. Enter one option per line, following the same syntax rules as exist for the bp.conf file. On Windows systems, the analogous file containing configuration options for the NetBackup-Java Windows Display Console is nbjava_install_path\java\setconf.bat nbj.conf and setconf.bat contain commands for each of the configuration options that are described in the following sections. To make changes, change the value after the equal sign in the relevant set command.

BPJAVA_PORT, VNETD_PORT
The following ports are the configured ports for the bpjava-msvc and vnetd daemon processes. These ports are registered with the Internet Assigned Numbers Authority (IANA). Table 12-3 Port
bpjava-msvc vnetd

Port Numbers Process and Registered Default Port Number

BPJAVA_PORT=13722 VNETD_PORT=13724

Symantec recommends that these ports are not changed. If changes are necessary, make the change on all NetBackup hosts in the relevant NetBackup cluster as described in the NetBackup Installation Guide. The value must be set in the corresponding nbj.conf (UNIX) or setconf.bat (Windows) configuration option.

FIREWALL_IN
The FIREWALL_IN configuration option provides a method to use a Java Administration Console that is outside of a trusted network to administer the NetBackup master servers that are within a trusted network. This option uses the following format. On UNIX:
FIREWALL_IN= HOST1:PORT1=HOST2:PORT2[;...;HOSTn:PORTn=HOSTm:PORTm]

On Windows:
SET FIREWALL_IN= HOST1:PORT1=HOST2:PORT2;IP_ADDR1:PORT3=IP_ADDR2:PORT4 SET FIREWALL_IN >> "%NBJDIR%"\nbjconf

Management topics Configuring the NetBackup-Java administration console

661

Where HOST is a host name or an IP address. This configuration option provides a way to allow administrators to bypass the firewall using one of the following methods:

Enter the port number of the bpjava service in the trusted internal network. Then, map the private interface where the bpjava service runs to a public interface that can be reached from outside the firewall. Set up a secure shell (SSH) tunnel from the local host to the system inside the firewall.

Example
In the following example:

Master server NBUMaster.symc.com is in a trusted network, behind a firewall. The IP address of NBUMaster.symc.com is 10.221.12.55. The NetBackup Java Administration Console is installed on localhost. SSH tunnels exist from localhost to NBUMaster.symc.com as follows:
bpjava-msvc port (default 13722) localhost:port1 vnetd port (default 13724) pbx port (default 1556) localhost:port2 localhost:12345

Where localhhost is the host name and port1 is the IP port.

Make relevant changes for connections to bpjava-msvc and vnetd as described in BPJAVA_PORT, VNETD_PORT on page 660. On UNIX systems, add the following line to the nbj.conf file:
FIREWALL_IN=NBUMaster.symc.com:1556=localhost:12345;10.221.12.55:12345=localhost:12345

The entry indicates that

The connection to NBUMaster.symc.com:1556 is to be redirected to localhost:12345. The connection to 10.221.12.55:1556 is to be redirected to localhost:12345.

On Windows systems, use setconf.bat to add the option:

SET FIREWALL_IN= NBUMaster.symc.com:1556=localhost:12345;10.221.12.55:12345=localhost:12345 SET FIREWALL_IN >> "%NBJDIR%"\nbjconf

662 Management topics Configuring the NetBackup-Java administration console

Note: The same options are used if NBUMaster.symc.com has a public interface (NBUMasterpub.symc.com) that can be reached from the Internet. In this case, the administrator would replace localhost with NBUMasterPub.synm.com.

FORCE_IPADDR_LOOKUP
The FORCE_IPADDR_LOOKUP configuration option specifies whether NetBackup performs an IP address lookup to determine if two host name strings are indeed the same host. This option uses the following format:
FORCE_IPADDR_LOOKUP = [ 0 | 1 ]

Where: 0 = Indicates that no IP address lookup is performed to determine if two host name strings are indeed the same host. They are considered to be the same host if the host name strings compare equally. Or, if a short name compares equally to the short name of a partially or fully qualified host name. 1 = Indicates that an IP address lookup is performed if the two host name strings do not match. The lookup determines if they have the same host. The default is to perform an IP address lookup if necessary to resolve the comparison. The IP address lookup is not performed if the host name strings compare equally. Note: Use a value of 1 for this option if you have the same host name in two different domains. For example, eagle.abc.xyz and eagle.def.xyz or using host name aliases. Many places in the NetBackup Administration Console compare host names to determine if the two are indeed the same host. For example, when using the File > Change Server command. The IP address lookup can consume time and result in slower response time. However, accurate comparisons are important. No IP address lookup is necessary if the host name is specified consistently in the NetBackup Administration Console login dialog box. It must match how the host names are configured in NetBackup. Host names are identified in the server list that is found in the Servers host properties. On UNIX systems, the host names also appear in the bp.conf file. Using host names eagle and hawk, the following describes how this option works:

FORCE_IPADDR_LOOKUP = 0 Comparisons of the following result in no IP address lookup. The hosts are considered to be the same host: eagle and eagle

Management topics Configuring the NetBackup-Java administration console

663

eagle.abc.def and eagle.abc.def eagle.abc and eagle.abc.def eagle and eagle.abc.def eagle and eagle.anything The hosts are considered to be different for any comparisons of short, partially, or fully qualified host names of eagle and hawk regardless of aliases.

FORCE_IPADDR_LOOKUP = 1 Comparisons of the following result in no IP address lookup. The hosts are considered to be the same host: eagle and eagle eagle.abc and eagle.abc eagle.abc.def and eagle.abc.def In addition to all comparisons of eagle and hawk, the following result in an IP address lookup. The comparison determines if the hosts are indeed the same host. eagle.abc and eagle.abc.def eagle and eagle.abc.def eagle and eagle.anything

INITIAL_MEMORY, MAX_MEMORY
Both INITIAL_MEMORY and MAX_MEMORY allow configuration of memory usage for the Java Virtual Machine (JVM). Symantec recommends that the NetBackup-Java Administration Console, the NetBackup-Java Windows Display Console, or the NetBackup, Archive, and Restore user interface be run on a system that contains at least 1 gigabyte of physical memory. Make sure that 256 megabytes of memory is available to the application. INITIAL_MEMORY specifies how much memory is allocated for the heap when the JVM starts. The value probably does not require changing. The default is sufficient for quickest initialization of jnbSA, the NetBackup-Java Windows Display Console, or jbpSA on a system with the recommended amount of memory. On UNIX systems, the initial memory allocation can also be specified as part of the jnbSA or jbpSA command. For example:
jnbSA -ms 36M

Default = 36M (megabytes). MAX_MEMORY specifies the maximum heap size that the JVM uses for dynamically allocated objects and arrays. If the amount of data is large, consider

664 Management topics Configuring the NetBackup-Java administration console

specifying the maximum heap size. For example, a large number of jobs in the Activity Monitor. On UNIX systems, the maximum memory allocation can also be specified as part of the jnbSA or jbpSA command. For example:
jnbSA -mx 512M

Default = 256M (megabytes).

MEM_USE_WARNING
The MEM_USE_WARNING configuration option specifies the percent of memory used compared to MAX_MEMORY, at which time a warning dialog is displayed to the user. Default = 80%. This option uses the following format:
MEM_USE_WARNING=80

NBJAVA_CLIENT_PORT_WINDOW
The NBJAVA_CLIENT_PORT_WINDOW configuration option specifies the range of non-reserved ports on this computer to use for connecting to the NetBackup-Java application server. Or, to connect to the bpjobd daemon from the NetBackup-Java Administration Consoles Activity Monitor. This option uses the following format:
NBJAVA_CLIENT_PORT_WINDOW = n m

Where:

n indicates the first in a range of non-reserved ports that are used for connecting to the bpjava processes on the NetBackup-Java application server. Or, for connecting to the bpjobd daemon or Windows service from theActivity Monitor of the NetBackup-Java Administration Console. If n is set to 0, the operating system determines the non-reserved port to use (default). m indicates the last in a range of non-reserved ports that are used for connecting to the NetBackup-Java Administration Console/NetBackup-Java Windows Display Console. If n and m are set to 0, the operating system determines the non-reserved port to use (default).

The minimum acceptable range for each user is 120. Each additional concurrent user requires an additional 120. For example, the entry for three concurrent users might look as follows:
NBJAVA_CLIENT_PORT_WINDOW = 5000 5360

If the range is not set wide enough, jnbSA exits with an error message that states an invalid value has occurred during initialization.

Management topics Configuring the NetBackup-Java administration console

665

Note: Performance is somewhat reduced with the use of NBJAVA_CLIENT_PORT_WINDOW.

NBJAVA_CONNECT_OPTION
The NBJAVA_CONNECT_OPTION configuration option specifies how the NetBackup-Java application server is connected to. It may be done using the vnetd daemon (VNETD_PORT) or directly using the application servers port (BPJAVA_PORT). The option also specifies the callback method that the server or the client uses when it communicates with the NetBackup-Java consoles (jnbSA, jbpSA). The default for NBJAVA_CONNECT_OPTION requires only that the vnetd port be accessible through any firewall.
NBJAVA_CONNECT_OPTION = [ 0 | 1 ]

Where: 0 = Indicates a direct connection to the application server and the traditional callback method. 1 = Indicates a connection to the application server using vnetd and the no callback method (default).

NBJAVA_CORBA_DEFAULT_TIMEOUT
The NBJAVA_CORBA_DEFAULT_TIMEOUT configuration entry specifies the default timeout that is used for most CORBA operations that are performed by the Java Administration Console. This option is present by default and uses the following format:
NBJAVA_CORBA_DEFAULT_TIMEOUT=60

The default is 60 seconds.

NBJAVA_CORBA_LONG_TIMEOUT
The NBJAVA_CORBA_LONG_TIMEOUT configuration entry specifies the timeout value that is used by the following areas in the Java Administration Console:

Device configuration wizard Disk Pool configuration wizard Disk Pool Inventory
NBJAVA_CORBA_LONG_TIMEOUT=1800

This option is present by default and uses the following format: The default is 1800 seconds.

666 Management topics Configuring the NetBackup-Java administration console

USE_NBJAUTH_WITH_ENHAUTH
NetBackup encourages the use of Symantec Product Authentication and Authorization for NetBackup Access Control (NBAC) instead of legacy security implementations. For information about the USE_NBJAUTH_WITH_ENHAUTH configuration option, see the NetBackup 6.0 documentation. For information on Symantec Product Authentication and Authorization, see the NetBackup Security and Encryption Guide.

Configuration options relevant to jnbSA and jbpSA

Several configuration options are available to administrators when using the NetBackup-Java Administration Console or the NetBackup, Archive, and Restore user interface.

To log the command lines that the NetBackup interfaces use

You may find it helpful to see which command lines the NetBackup-Java Administration Console or the NetBackup, Archive, and Restore user interface uses. Use option -lc to log to a log file the command lines that jnbSA or jbpSA uses. No value is necessary. For example: /usr/openv/java/jbpSA -lc Note: jnbSA and jbpSA dont always use the command lines to retrieve or update data. The interfaces have some protocols that instruct the application server to perform tasks using NetBackup and Media Manager APIs.

To customize jnbSA and jbpSA with bp.conf entries

The INITIAL_BROWSE_SEARCH_LIMIT and KEEP_LOGS_DAYS options in the /usr/openv/netbackup/bp.conf file allow the administrator and users to customize the following aspects of jbpSA operation:

INITIAL_BROWSE_SEARCH_LIMIT limits the start date of the search for restores and can improve performance when large numbers of backups are done. KEEP_LOGS_DAYS specifies how long job and progress log files are kept that the NetBackup-Java Backup, Archive, and Restore application (jbpSA) generates. The files are written into the following directories: /usr/openv/netbackup/logs/user_ops/_username_/jobs /usr/openv/netbackup/logs/user_ops/_username_/logs

Management topics NetBackup-java performance improvement hints

667

A directory exists for each user that uses the NetBackup-Java applications. The default is three days. This option also controls how long the NetBackup-Java GUI log files are kept in /usr/openv/netbackup/logs/user_ops/nbjlogs.

NetBackup-java performance improvement hints

The most important factor to consider when faced with performance issues while using the following interfaces, is the platform on which the console is running.

NetBackup-Java Administration Console NetBackup-Java Windows Display Console NetBackup Backup, Archive, and Restore user interface

Regardless of the platform, you can run the Administration Console from the following locations:

Run it locally on a desktop host (on supported Windows and UNIX platforms), or Run it remotely and display it back to a desktop host (from supported UNIX platforms)

To provide the best performance, the recommended method for using these consoles is to run the consoles locally on a desktop host. When the consoles are run locally, they do not exhibit the font and the display issues that can be present in some remote display-back configurations.

What it means to be running the java console locally on a UNIX platform

On supported UNIX platforms, the console is run locally if jnbSA or jbpSA is entered on the same host on which the console is displayed. That is, your display environment variable is set to the host on which the jnbSA or jbpSA commands were entered. Improvements in the Java technology have made remote X-display back potentially viable on some platforms. However, problems continue with certain controls in the consoles. For example, incorrect combo box operations, sluggish scrolling, and display problems in tables with many rows. More serious issues have also occurred. Consoles can abort and hang because of a Java Virtual Machine (JVM) failure when run in this mode on some platforms. These JVM failures are most often seen on the AIX platform. Therefore, Symantec cannot recommend running the consoles in a remote X-display back configuration.

668 Management topics NetBackup-java performance improvement hints

What it means to be running the console locally on a Windows platform

On Windows platforms, start the Windows Display Console locally by selecting Start >Veritas NetBackup > NetBackup-Java Version 6.5. (Or by selecting the equivalent desktop shortcut.) This Start menu item or shortcut appears if you install the optional NetBackup-Java Windows Display Console available on the main NetBackup for Windows installation screen.

How do I run a console locally and administer a remote server?

The NetBackup Administration Console and the Backup, Archive, and Restore user console are distributed applications. Both consist of two major and separate system processes that can run on different machines. For example:

The NetBackup Administration Console on one machine, and the consoles application server - bpjava processes on another machine.

The NetBackup Administration Console does not have to run on a NetBackup server host. However, the application server must run on this host in order for you to be able to administer NetBackup. For more information, see NetBackup-Java administration console architectural overview on page 652. Although the NetBackup-Java Administration Console does not run on all NetBackup-supported platforms, the application server for the console does run on all supported platforms. The distributed application architecture enables direct administration of all NetBackup platforms, even though the consoles themselves run only on a subset of the NetBackup-supported platforms. To log into the NetBackup-Java Administration Console, specify a host name. The host name is the machine where the application server (bpjava) runs. (For example, a NetBackup master server.) All requests or updates that are initiated in the console are sent to its application server that runs on this host.

How do I enhance console performance?

Performance of the NetBackup-Java applications depends on the environment where the applications are running, including available resources and network throughput. The NetBackup-Java default configuration, specifically the INITIAL_MEMORY and MAX_MEMORY configuration options, assumes sufficient memory resources on the machine where the console is running. For example, where the jnbSA command is executed or the NetBackup-Java Windows Display Console is started. Following are guidelines for improving performance:

Management topics NetBackup-java performance improvement hints

669

Consider the network communication speed and the amount of data being transferred. Consider the amount of work being performed on the relevant machines. Run NetBackup-Java on a machine that has a low level of activity. For example, there can be large differences in response time when other memory-intensive applications are running on the machine. (For example, Web browsers.) Multiple instances of NetBackup-Java on the same machine have the same effect. Run NetBackup-Java on a 1 gigabyte machine that has at least 256 MB of RAM available to the application. In some instances, the application does not initiate due to insufficient memory. A number of messages identify these failures in the xterm window where the jnbSA command was run. Or, the messages appear in the application log file. Possible messages include the following:
Error occurred during initialization of VM Could not reserve enough space for object heap Out of Memory

For more information, refer to the bp.conf options INITIAL_MEMORY, MAX_MEMORY on page 663.

Consider the amount of physical memory on the relevant machines. Possibly add memory on the host being administered (the consoles application server host). Consider increasing the swap space to relevant machines:

The console host (the host where the console is started)

The host being administered Increase the amount of swap space available to the system where you are running the applications can increase performance. Especially if there is a great deal of other activity on the machine. More swap space can alleviate hangs or other problems that relate to insufficient memory for the applications.

Consider additional or faster CPUs to relevant machines:

The console host (the host where the console is started) The host being administered

To save startup time, allow NetBackup-Java to run (iconified) rather than exit and restart. Startup of the Java virtual machine can take longer than other applications. Consider limiting the amount of NetBackup data that is retained for long periods of time to only that which is necessary. For example, do not retain successfully completed jobs for more than a few hours.

670 Management topics NetBackup-java performance improvement hints

For more information, see Managing the jobs database on page 67.

Is the performance better when run locally or using remote display back?
Performance depends on the following:

the speed of the network the console and the application server machine resources the workloads on the console the application server hosts the amount of NetBackup data. (Data is the number of jobs in the Activity Monitor or number of NetBackup policies.)

The console may perform better if started on the consoles application server host, then displayed back to the desktop host. However, Symantec is not aware of a situation where that configuration produces better console performance. As previously mentioned, the configuration is not recommended due to problems unrelated to performance issues. Consider the following scenarios to determine what would provide the best performance for your configuration.

Scenario 1
Assume no deficiency in either the console hosts resources or the application server hosts resources. Assume that the amount of NetBackup configuration data being transferred to the console host far exceeds the X-Windows pixel display data. That is, the actual console screen being sent from the remote host. Unfortunately, the only way to determine the viability of this situation is to try it. Network capabilities and the proximity of the two hosts influences each NetBackup configuration.

Scenario 2
Assume that the available resources of the application server host far exceed that of the console host. Assume that the console host has a very limited CPU and memory as compared to the NetBackup master server being administered. (The console host is the machine on which the console is started.) If the console is run on the master server and displayed back to the desktop host, performance may be enhanced. If the desktop host is a Windows machine, X-terminal emulation or remote display tools such as Exceed and VNC are required.

Management topics NetBackup-java performance improvement hints

671

These scenarios address the performance aspect of using the NetBackup-Java console. There may be other reasons that require you to display back remotely to your desktop, however, it is not recommended. Review the Release Notes for additional issues of relevance to the NetBackup-Java Administration Console and Backup, Archive, and Restore client console. Table 12-4 File
/usr/openv/java/auth.conf /usr/openv/netbackup/bp.conf /usr/openv/java/nbj.conf

Files Containing Configuration Entries Description

Authorization options. Configuration options (server and client). Configuration options for the NetBackup-Java Console Configuration options for media and device management. Configuration options for user (on client).

/usr/openv/volmgr/vm.conf

$HOME/bp.conf

672 Management topics Managing client restores

Managing client restores

The topics in this section concern aspects of how to manage restores for NetBackup clients.

Server-directed restores on page 672 Client-redirected restores on page 673 Restoring files and access control lists on page 681 To improve search times by creating an image list on page 682 Set original atime for files during restores on page 682 Checkpoint restart for restore jobs on page 683 Restoring system state on page 684

Find related topics in Chapter 5, Reference Topics, in the NetBackup Administrators Guide, Volume II. Incorrectly specified host names are often a factor in file restore problems.

Server-directed restores
By default, NetBackup clients are configured to allow NetBackup administrators on a master server to direct restores to any client. To prevent server-directed restores, configure the client accordingly:

Windows clients: Open the Backup, Archive, and Restore interface on the client. Select File > NetBackup Client Properties > General tab > Clear the Allow server-directed restores checkbox. UNIX clients: Add DISALLOW_SERVER_FILE_WRITES to the following file on the client: /usr/openv/netbackup/bp.conf

Note: On UNIX systems, the redirected restores can incorrectly set UIDs or GIDs that are too long. The UIDs and GIDs of files that are restored from one platform to another may be represented with more bits on the source system than on the destination system. If the UID/GID name in question is not common to both systems, the original UID/GID could be invalid on the destination system. In this case, the UID/GID is replaced with the UID/GID of the user that performs the restore. When performing a redirected restore, no progress log is produced if the bp.conf file of the requesting server does not contain an entry for the server

Management topics Managing client restores

673

that performs the 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 bp.conf file (or the server list), the restoring server has no access to write the log files to the requesting server. Consider the following solutions:

To produce a progress log, add the requesting server to the server list: log into the requesting server. In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Servers. Add the restoring server to the server list. Log in to the restoring server. Check the Activity Monitor to determine the success of the restore operation.

Note: To restore a UNIX backup that contains soft and hard links, the Backup, Archive, and Restore client interface must be run from a UNIX machine. Only the Java version of the client interface contains the Rename hard links and Rename soft links restore options. Windows users can install the Windows display console to access the Java version of the Backup, Archive, and Restore interface from a Windows machine. (See Running the Java-based Windows Display Console on page 37.)

Client-redirected restores
The Backup, Archive, and Restore client interface contains options for allowing clients to restore the files that were backed up by other clients. The operation is called a redirected restore.

How NetBackup enforces restore restrictions

By default, NetBackup permits only the client that backs up files to restore those files. NetBackup ensures that the client name of the requesting client matches the peer name that was used to connect to the NetBackup server. Unless clients share an IP address, the peer name is equivalent to the clients host name. (Clients may share an IP address due to the use of a gateway and token ring combination, or multiple connections.) When a client connects through a gateway, the gateway can use its own peer name to make the connection. The NetBackup client name is normally the clients short host name, such as client1 rather than a longer form such as client1.null.com. The client name is found in the following locations:

674 Management topics Managing client restores

Windows clients (including NetWare NonTarget):

Open Backup, Archive, and Restore and select File > Specify NetBackup Machines and Policy Type. The client name that is selected as Source Client for Restores is the source of the backups to be restored.

On NetWare target clients: Specify the client name in the bp.ini file. UNIX clients:

Open Backup, Archive, and Restore and select the client name as the Source client for restore.

To allow all clients to perform redirected restores

The NetBackup administrator can allow clients to perform redirected restores. That is, allow all clients to restore the backups that belong to other clients. Place an empty No.Restrictions file on the NetBackup master server where the policy that backed up the other clients resides.

Management topics Managing client restores

675

Note: The information within this section applies to restores made using the command line, not the Backup, Archive, and Restore client interface. Create an altnames directory in the following location, then place the empty file inside of the directory:
/usr/openv/netbackup/db/altnames/No.Restrictions

The NetBackup client name setting on the requesting client must match the name of the client for which the backup was created. The peer name of the requesting client does not need to match the NetBackup client name setting. Caution: The /usr/openv/netbackup/db/altnames directory can present a potential breach of security. Users that are permitted to restore files from other clients may also have local permission to create the files that are found in the backup.

To allow a single client to perform redirected restores

The NetBackup administrator can permit a single client to restore the backups that belong to other clients. Create a peername file on the NetBackup master server where the policy that backed up the other client(s) resides. Note: The information within this section applies to restores made using the command line, not the Backup, Archive, and Restore client interface. Create an altnames directory in the following location, then place the empty file inside of the directory:
/usr/openv/netbackup/db/altnames/peername

Where peername is the client to possess restore privileges. In this case, the requesting client (peername) can access the files that are backed up by another client. The NetBackup client name setting on peername must match the name of the other client.

To allow redirected restores of a clients files

The NetBackup administrator can permit a single client to restore the backups that belong to another client. Create a peername file on the NetBackup master server of the requesting client as described here. Note: The information within this section applies to restores made using the command line, not the Backup, Archive, and Restore client interface.

676 Management topics Managing client restores

Create an altnames directory in the following location, then place the peername file inside of the directory:
/usr/openv/netbackup/db/altnames/peername

Where peername is the client to possess restore privileges. Add to the peername file the names of the client(s) whose files the requesting client wants to restore. The requesting client can restore the files that were backed up by another client if:

The names of the other clients appear in the peername file, and the NetBackup client name of the requesting client is changed to match the name of the client whose files the requesting client wants to restore.

Redirected restore examples

This section provides some example configurations that allow clients to restore the files that were backed up by other clients. These methods may be required when a client connects through a gateway or has multiple Ethernet connections. In all cases, the requesting client must have access to an image database directory on the master server (/usr/openv/netbackup/db/images/client_name). Or, the requesting client must be a member of an existing NetBackup policy. Caution: Not all file system types on all machines support the same features. Problems may be encountered when a file is restored from one file system type to another. For example, the S51K file system on SCO machines does not support symbolic links nor does it support names greater than 14 characters long. You may want to restore a file to a machine that doesnt support all the features of the machine from which the restore was performed. In this case, all files may not be recovered. In the following examples:

client1 is the client that requests the restore. client2 is the client that created the backups that the requesting client wants to restore.

Note: The information within this section applies to restores made using the command line, not the Backup, Archive, and Restore client interface.

Management topics Managing client restores

677

Note: You must be a root user for any of the steps that must be performed on the NetBackup server. You may also have to be a root user to make the changes on the client.

Example 1: Redirected client restore

Assume you must restore files to client1 that were backed up from client2. The client1 and client2 names are those specified by the NetBackup client name setting on the clients. In the nominal case, follow these steps to perform the restore: 1 Log in as root on the NetBackup server. Perform one of the following actions:

Edit /usr/openv/netbackup/db/altnames/client1 so it includes the name of client2. Or, Run the touch command on the following file: /usr/openv/netbackup/db/altnames/No.Restrictions

Caution: The No.Restrictions file allows any client to restore files from client2. 2 3 4 Log in on client1 and change the NetBackup client name to client2. Restore the file. Undo the changes that were made on the server and client.

Example 2: Redirected client restore using the altnames file

This example explains how altnames provides restore capabilities to clients that dont use their own host name when they connect to the NetBackup server. By default, the NetBackup client name of the requesting client must match the peer name that is used in the connection to the NetBackup server. When the NetBackup client name is the host name for the client and matches the peer name (normal case), this requirement is met. However, problems arise when clients connect to multiple ethernet or connect to the NetBackup server through a gateway. Consider the configuration in the following figure:

678 Management topics Managing client restores

Figure 12-6

Example restore from token ring client

client1 NetBackup server client2 Token Ring TCP Gateway

client3

In this example, restore requests from client1, client2, and client3 are routed through the TCP gateway. Because the gateway uses its own peer name rather than the client host names for connection to the NetBackup server, NetBackup refuses the requests. Clients cannot restore even their own files. Perform the following stops to correct the situation: 1 Determine the peer name of the gateway: a Attempt a restore from the client in question. In this example, the request fails with an error message similar to the following: client is not validated to use the server Examine the NetBackup problems report and identify the peer name that is used on the request. Entries in the report may be similar to the following: 01/29/07 08:25:03 bpserver - request from invalid server or client client1.dvlp.null.com In this example, the peer name is client1.dvlp.null.com.

Run the touch command on the following file:

/usr/openv/netbackup/db/altnames/peername

In our example, the file is:

/usr/openv/netbackup/db/altnames/client1.dvlp.null.com

Edit the peername file so that it includes the client names. For example, if you leave the file
/usr/openv/netbackup/db/altnames/client1.dvlp.null.com

empty, client1, client2, and client3 can all access the backups that correspond to their NetBackup client name setting. For more information, see To allow a single client to perform redirected restores on page 675. If you add the names client2 and client3 to the file, you give these two clients access to NetBackup file restores, but exclude client1.

Management topics Managing client restores

679

For more information, see To allow redirected restores of a clients files on page 675. Note that this example requires no changes on the clients. 4 Restore the files.

Example 3: Troubleshoot redirected client restore using the altnames file

If you cannot restore files with a redirected client restore using the altnames file, troubleshoot the situation: 1 On the NetBackup master server, add the VERBOSE entry and a logging level to the bp.conf file. For example:
VERBOSE = 3

2 3

Create the debug log directory for bprd by running:

mkdir /usr/openv/netbackup/logs/bprd

On the NetBackup server, stop the NetBackup request daemon, bprd, and restart it in verbose mode by running:
/usr/openv/netbackup/bin/admincmd/bprdreq -terminate /usr/openv/netbackup/bin/bprd -verbose

Restart bprd to ensure that bprd logs information regarding client requests. 4 5 On client1, attempt the file restore. On the NetBackup server, identify the peer name connection that client1 used. Examine the failure as logged in the All Log Entries report or examine the bard debug log:
/usr/openv/netbackup/logs/bprd/log.date

to identify the failing name combination. 6 Perform one of the following on the NetBackup server:

Enter the following commands mudir -p /usr/openv/netbackup/db/altnames touch /usr/openv/netbackup/db/altnames/No.Restrictions These commands allow any client access to client2 backups by changing its NetBackup client name setting to specify the client2. Run the touch command on the following file: /usr/openv/netbackup/db/altnames/peername The command allows client1 access to any client2 backups by changing its NetBackup client name setting to specify client2. Add client2 to the /usr/openv/netbackup/db/altnames/peername file. The

680 Management topics Managing client restores

addition to the peername file allows client1 access to the backups that were created on client2 only. 7 8 9 On client1, change the NetBackup client name setting in the user interface to match what is specified on client2. Restore the files to client1. Perform the following:

Delete the VERBOSE entry from the /usr/openv/netbackup/bp.conf file on the master server. Delete /usr/openv/netbackup/logs/bprd and the contents. Delete /usr/openv/netbackup/db/altnames/peer.or.hostname (if existent) Delete /usr/openv/netbackup/db/altnames/No.Restrictions (if existent) On client1, restore the NetBackup client name setting to its original value.

10 To return the configuration to what it was before the restore:

Management topics Managing client restores

681

Restoring files and access control lists

An access control list (ACL) is a table that conveys the access rights users have to a file or directory. Each file or directory can have a security attribute that extends or restricts users access.

To restore the files that possess ACLs

By default, the NetBackup-modified GNU tar (/usr/openv/netbackup/bin/tar) restores ACLs along with file and directory data. However, in some situations the ACLs cannot be restored to the file data:

Where the restore is cross-platform. (Examples: an AIX ACL restored to a Solaris client; a Windows ACL restored to an HP client.) When a tar other than the NetBackup modified tar is used to restore files.

In these instances, NetBackup stores the ACL information in a series of generated files in the root directory using the following naming form: .SeCuRiTy.nnnn These files can be deleted or can be read and the ACLs regenerated by hand. See Chapter 5, Reference Topics, in the NetBackup Administrators Guide, Volume II. This section lists other files that NetBackup generates due to cross-platform restores.

To restore files without restoring ACLs

The NetBackup client interface on Windows is available to administrators to restore data without restoring the ACLs. Both the destination client and the source of the backup must be Windows systems. To restore files without restoring ACLs, the following conditions must be met:

The policy that backed up the client is of policy type MS-Windows-NT. An administrator performs the restore and is logged into a NetBackup server (Windows or UNIX). The option is set at the server, using the client interface. The option is unavailable on stand-alone clients (clients that do not contain the NetBackup server software). The destination client and the source of the backup must both be systems running Windows 2000, Windows XP, or Windows Server 2003. The option is disabled on UNIX clients.

To restore files without restoring ACLs 1 Log in to the NetBackup server as administrator. Open the Backup, Archive, and Restore client interface.

682 Management topics Managing client restores

2 3 4 5

From the client interface, initiate a restore. Select the files to be restored, then select Actions > Start Restore of Marked Files. The Restore Marked Files dialog box appears. Place a check in the Restore without access-control attributes check box. Make any other selections for the restore job and click Start Restore.

To improve search times by creating an image list

Create an image list to improve searching in many small backup images. Run the following command on the master server while logged in as root. Enter the following as one line: /usr/openv/netbackup/bin/admincmd/bpimage -create_image_list -client name Where name is the name of the client with small backup images. The command creates files in the following location: /usr/openv/netbackup/db/images/clientname IMAGE_LIST: List of images for this client IMAGE_INFO: Information about the images for this client IMAGE_FILES: The file information for small images Do not edit these files. The files contain offsets and byte counts that are used to seek and read the image information. The files require 35 to 40% more space in the client directory. The files improve search performance only if thousands of small backup images for a client exist.

Set original atime for files during restores

By default, during a restore NetBackup sets the atime for each file to the current time. You can elect to have NetBackup set the atime for each restored file to the value the file had when it was backed up. To do so, create the following file on the client. /usr/openv/netbackup/RESTORE_ORIGINAL_ATIME Note: If Veritas Storage Migrator is in use, do not create the RESTORE_ORIGINAL_ATIME file. If this file is present, restored files may be migrated immediately because of the older atime.

Management topics Managing client restores

683

Checkpoint restart for restore jobs

Checkpoint Restart for restore jobs saves time by providing the mechanism for NetBackup to resume a failed restore job. The job resumes automatically from the start of the file last checkpointed rather than from the beginning of the entire restore job. The checkpoints are taken once every minute during a restore job. Checkpoint Restart for restore jobs is enabled by default and requires no additional configuration. Two host properties impact Checkpoint Restart for restore jobs:

Master server host property Clean-up > Move Restore Job from Incomplete State to Done State For more information, see Clean-up properties on page 383. Master server host property Universal > Restore Retries For more information, see Universal Settings properties on page 477.

To suspend and resume a restore job

A NetBackup administrator can choose to suspend a checkpointed restore job and resume the job at a later time. For example, while running a restore job for several hours, the administrator receives a request for a second restore. The request is of a higher priority and requires the resources in use by the first job. The administrator can suspend the first job, start the second restore job and let it complete. Then, resume the first job from the Activity Monitor and let the job complete. Note: If a checkpointed restore that has no end date is suspended, then resumed, and a new backup occurs before the resume is initiated, the files from the new backup are included in the restore. For example, a user makes a restore request of a directory, then that restore is suspended. The request is resumed the next day, after another backup of the directory has been performed. The files that are restored are from the latest backup.

Limitations to checkpoint restart for restore jobs

Limitations to Checkpoint Restart for restore jobs include the following:

The restore restarts at the beginning of the last checkpointed file only, not within the file. Checkpoint Restart for restore jobs works only on the files that are backed up using Standard or MS-Windows-NT policy types.

684 Management topics Managing client restores

Note: Although NetWare clients use the Standard policy type, Checkpoint Restart for restores is not supported on NetWare clients.

Third Party Copy and the Media Server Copy images that use Standard policy types are supported. However, they cannot be suspended or resumed if the backup image has changed blocks. Flashbackup is not supported.

Restoring system state

On all hosts running Windows 2000 or later, the System State includes the registry, the COM+ Class Registration database, and boot and system files. For Windows 2000 servers, the Certificate Services database is included if the server operates as a certificate server. If the server is a domain controller, the data also includes the Active Directory services database and the SYSVOL directory. Note: The best recovery procedure depends on many hardware and software variables that pertain to your server and its environment. A complete Windows recovery procedure is beyond the scope of this manual; you may need to contact Microsoft or refer to your Microsoft documentation.

Important notes on system state

Read the following notes carefully before you restore the System State:

The System State should be restored in its entirety. Do not restore selected files. Although incremental backups of the System State can be configured, NetBackup always performs a full backup. Therefore, only the most recent backup of the System State must be restored. For Windows 2000 systems, Service Pack 2 is required. Do not redirect a System State restore. System State is computer-specific and to restore it to an alternate computer can result in an unusable system. Do not cancel a System State restore operation. To cancel the operation may leave the system unusable. To restore the System State to a domain controller, the Active Directory must not be running. Refer to the following procedure for directions on how to restore the Active Directory.

Management topics Managing client restores

685

To restore the system state 1 To restore the Active Directory, restart the system, then press F8 during the boot process. F8 brings up a startup options menu. Press F8 upon restart if the system to which you are to restore is a Windows domain controller. Otherwise, begin with step 4. From the startup options, select Directory Services Restore Mode and continue the boot process. Ensure that the NetBackup Client Service, inetd, has started. Use the Activity Monitor or the Services application in the Windows Control Panel. Start the Backup, Archive, and Restore client interface. Click Select for Restore, and place a checkmark next to System State.

2 3 4

5 6

From the Actions menu, choose Start Restore of Marked Files. From the Restore Marked Files dialog, select Restore everything to its original location and Overwrite the existing file.

Caution: Do not redirect the System State restore to a different host. System State is computer-specific. To restore it to a different computer can result in an unusable system. 7 8 Click Start Restore. Your network may contain more than one domain controller. To replicate Active Directory to other domain controllers, perform an authoritative restore of the Active Directory after the NetBackup restore job completes. To perform an authoritative restore of the Active Directory: run the Microsoft ntdsutil utility after you have restored the System State data

686 Management topics Managing client restores

but before the server is restarted. An authoritative restore ensures that the data is replicated to all of the servers. For more information about an authoritative restore and the ntdsutil utility, refer to your Microsoft documentation. 9 Reboot your system before performing subsequent restore operations. If you have booted into Directory Services Restore Mode on a domain controller, reboot into normal mode when the restore is complete.

Management topics Goodies scripts

687

Goodies scripts
The /usr/openv/netbackup/bin/goodies directory contains sample shell scripts to modify. Use some scripts with the cron utility to create periodic mailings of the information that relates to NetBackup. To ensure that other can run the new scripts, run: chmod 755 script_name Where script_name is the name of the script. The scripts in the goodies directory are not supported but are intended as examples to customize.

Alternate server restores

This section explains how to restore files by using a NetBackup server other than the one that was used to write the backup. This type of restore operation is called an alternate server restore or server independent restore. It allows easier access to data for restores in master and media server clusters and provides better failover and disaster recovery capabilities. NetBackups architecture allows storage devices to be located on multiple servers (either separate storage devices or a shared robot). The NetBackup image catalog on the master server contains an entry that defines the server (master or media server) to which each backup was written. Information specific to the backup media is contained within the master server image catalog (in the attribute file for each backup). The information is also contained in the Enterprise Media Manager (EMM) database, generally located on the master server. To restore data through a device on another server is more involved than other restores. Use the methods that are described in this section to restore the backups. Although the methods do not require you to expire and import backup images, in some instances it is useful. The topics described in this section are also pertinent in the case of restoring from a backup copy. If youve created multiple copies of a backup, it is possible to restore from a specific backup copy other than the primary copy. To do so, use the bprestore command. See the Backup, Archive, and Restore online help or the NetBackup Commands for UNIX and Linux.

Supported configurations
The next two figures show configurations where NetBackup supports alternate server restores. All methods require that the server that is used for the restore

688 Management topics Alternate server restores

be in the same cluster as the server that performed the original backup. The server must also share the same Enterprise Media Manager database. Figure 12-7 NetBackup servers that share robotic peripherals
Robot NetBackup Image Catalog Enterprise Media Manager database Master Server Control Drive 2 Drive 1 Media Server 1 Drive 3

Media Server 2

The following assumptions were made in Figure 12-7:

A single, shared Enterprise Media Manager database exists on the NetBackup master server. The NetBackup master server is available at time of restore. Robotic control is on a NetBackup server that is available at the time of the restore.

Management topics Alternate server restores

689

Figure 12-8
Robot 1

NetBackup servers with separate non-shared peripherals

Robot 2 Control Control

Drive 1

Drive 1

Drive 2

Media server 1

NetBackup image catalog Stand-alone drive Enterprise Media Manager database Master server Drive 1

Media server 2 Note: Media servers 1 and 2 may be off-site.

The following assumptions were made in Figure 12-8:

The media is made physically accessible through an available NetBackup server. The Enterprise Media Manager database is updated to reflect this move. A single, shared Enterprise Media Manager database exists on the NetBackup master server. The NetBackup master server is available at time of restore Robotic control (if applicable) is on a NetBackup server that is available at the time of the restore.

Methods for performing alternate server restores

The method that NetBackup administrators can use to perform alternate server restores depends on the configuration and the situation. The method can include one or more of the following:

Method 1: Modifying the NetBackup catalogs on page 690 Method 2: Overriding the original server on page 691 Method 3: Automatic failover to alternate server on page 692

690 Management topics Alternate server restores

Method 1: Modifying the NetBackup catalogs

This method changes the contents of NetBackup catalogs and thus requires administrator intervention. Use this method only when the server reassignment is permanent. Some examples of when to use this method:

Media is moved to an off-site location, where a media server exists. A robot has been moved from one server to another. Two (or more) servers share a robot, each with connected drives. One of the servers is to be disconnected or replaced. Two (or more) servers each have their own robots. One of the servers robots has run out of media capacity for future backups, while plenty of empty slots exist on another servers robot.

The actual steps that are used vary depending on whether the original server is still available. To modify catalogs when the server that wrote the media is available 1 If necessary, physically move the media. Then, update the Enterprise Media Manager database by using move volume options in the Media Manager administration utilities. Update the NetBackup image catalog on the master server. Update the NetBackup media catalogs on both the original NetBackup server (oldserver) and the destination NetBackup server (newserver). Use the following command, which can be run from any one of the NetBackup servers. The admincmd command must be entered on one line.

As root on a UNIX NetBackup server: cd /usr/openv/netbackup/bin/admincmd bpmedia -movedb -m media_id -newserver hostname -oldserver hostname As administrator on a Windows NetBackup server: cd install_path\NetBackup\bin\admincmd bpmedia.exe -movedb -m media_id -newserver hostname -oldserver hostname

To modify catalogs when the server that wrote the media is not available 1 If necessary, physically move the media. Then, update the Enterprise Media Manager database by using the move volume options in the Media and Device Management window. Update only the NetBackup image catalog on the master server. Use the following commands from the NetBackup master server. The admincmd command must be entered on one line.

Management topics Alternate server restores

691

As root on a UNIX NetBackup server: cd /usr/openv/netbackup/bin/admincmd bpimage -id media_id -newserver hostname -oldserver hostname As administrator on a Windows NetBackup server: cd install_path\NetBackup\bin\admincmd bpimage.exe -id media_id -newserver hostname -oldserver hostname

Method 2: Overriding the original server

NetBackup allows the administrator to force restores to a specific server, regardless of where the files were backed up. For example, if files were backed up on server A, a restore request can be forced to use server B. Examples of when to use this method:

Two (or more) servers share a robot, each with connected drives. A restore is requested while one of the servers is either temporarily unavailable or is busy doing backups. A server has been removed from the NetBackup configuration, and is no longer available.

To enable overriding of the original server for restores 1 In the NetBackup Administration console, open the General Server host properties dialog. For more information, see General Server properties on page 431. Add an entry in the Media Host Override list, that lists the original backup server and the restore server. Click OK.

To override the original server for restores manually To revert to the original configuration for future restores, delete the changes that were made in step 2. 1 2 If necessary, physically move the media and update the Enterprise Media Manager database Media Manager volume database to reflect the move. Modify the NetBackup configuration on the master server:

Using the NetBackup Administration Console: Open the General Server host properties dialog of the master server. Add an entry in the Media Host Override list, that lists the original backup server and the restore server. Click OK. By modifying the bp.conf file on a UNIX NetBackup server:

692 Management topics Alternate server restores

As root add the following entry to the /usr/openv/netbackup/bp.conf file: FORCE_RESTORE_MEDIA_SERVER = fromhost tohost The fromhost is the server that wrote the original backup and the tohost is the server to use for the restore. 3 Stop and restart the NetBackup Request daemon on the master server.

Note: The override applies to all storage units on the original server. This means that restores for any storage unit on fromhost go to tohost.

Method 3: Automatic failover to alternate server

NetBackup allows the administrator to configure automatic restore failover to an alternate server, if the original server is temporarily inaccessible. Once it is configured, this method does not require administrator intervention. For more information, see Restore Failover properties on page 459. Some examples of when to use this method are:

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

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

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

Note: The failover uses only the failover hosts that are listed in the NetBackup configuration. (See the following procedure.) By default, the list is empty and NetBackup does not perform the automatic failover. To enable automatic failover to an alternate server 1 Modify the NetBackup configuration on the master server:

Using the NetBackup Administration Console:

Management topics Alternate server restores

693

Open the Restore Failover host properties dialog of the master server. Add an entry in the Alternate Restore Failover Machines list, that lists the media server and failover restore server(s).

By modifying the bp.conf file on a UNIX NetBackup server: As root, add the following entry to the /usr/openv/netbackup/bp.conf file: FAILOVER_RESTORE_MEDIA_SERVERS = failed_host host1 host2 ... hostN where: failed_host is the server that is not operational. host1 ... hostN are the servers that provide failover capabilities. When automatic failover is necessary for a given server, NetBackup searches through the relevant FAILOVER_RESTORE_MEDIA_SERVERS list. NetBackup looks from left to right for the first server that is eligible to perform the restore.

Note: There can be multiple FAILOVER_RESTORE_MEDIA_SERVERS entries and each entry can have multiple servers. However, a NetBackup server can be a failed_host in only one entry. 2 Stop and restart the NetBackup Request daemon on the master server.

Notes on alternate server restores

Expiring and importing media
Even with the alternate server restore capabilities, it may be necessary to expire media and then import it.

Identifying media spanning groups

An alternate server restore operation can include media IDs that contain backup images that span media. It may be necessary to identify the media IDs that contain fragments of the spanned images. The group of related media is called a media spanning group. To identify the media in a specific media spanning group, run the following command as root on the NetBackup master server: cd /usr/openv/netbackup/bin/admincmd bpimmedia -spangroups -U -mediaid media_id To display all media in all spanning groups, omit -mediaid media_id from the command.

694 Management topics Using NetBackup with Storage Migrator

Using NetBackup with Storage Migrator

Symantec recommends Storage Migrator for UNIX (VSM) as a storage migration solution. NetBackup can back up files from a disk type storage unit that contains VSM-managed file systems. When a file is migrated, the data is copied to secondary storage. The data can then be deleted (or purged) from the disk storage unit because it is copied elsewhere. The files can then be recalled (or cached) from secondary storage should the files be needed locally. NetBackup backs up the files that Storage Migrator has purged in the following order:

For user backups by nonroot users, NetBackup first caches the files, then backs up the files. For scheduled backups and user backups by a root user, NetBackup backs up only the migration information for the files. Because the data is already resident on secondary storage, NetBackup neither backs up the data nor caches it.

Caution: NetBackup does not set the Storage Migrator obsoletion date for a file. Make sure that the migrated copies are retained for at least as long as the backups. Restores are not possible unless the copies are retained. When NetBackup restores purged files, Storage Migrator considers the restored files to be purged, with a file slice value of zero. If files have been selected for migration and not yet copied to secondary storage, NetBackup backs them up. A bparchive back up and remove operation always caches a purge file.

Set a large enough media mount timeout

The Media Mount Timeout property is in effect during the caching of the migrated backups when NetBackup restores files to a Storage Migrator-managed disk storage unit. This property is located under Host Properties > Master Server > Timeouts > Media Mount Timeout. If the file to be restored is part of a backup that has migrated to tape, the Media Mount Timeout must last long enough to cache the entire disk file.

Do not use the RESTORE_ORIGINAL_ATIME file

Do not create the /usr/openv/netbackup/RESTORE_ORIGINAL_ATIME on any clients that are running Storage Migrator or restored files may be immediately migrated because of the older atime.

Management topics Using NetBackup with Storage Migrator

695

For more information, see Set original atime for files during restores on page 682. Note: If you use another migration product, make sure that it provides adequate and full recoverability of the disk-resident data. Make sure that it has transparent access to the disk files at the application level.

Do not use the following client bp.conf file settings

Ensure that the bp.conf file on a client using Storage Migrator does not have entries for either of the following:

DO_NOT_RESET_FILE_ACCESS_TIME USE_CTIME_FOR_INCREMENTALS

These entries cause the atime for files to be updated each time the files are backed up. The updated atime of the files appear as if the files are frequently used and stops Storage Migrator from selecting the files for migration.

696 Management topics Using NetBackup with Storage Migrator

Appendix

NetBackup relational database

This appendix contains the information that describes the proper installation and operation of the Sybase Adaptive Server Anywhere (ASA) relational database management system. Generally, the implementation of Sybase ASA in the NetBackup catalog is transparent. However, this appendix is for the administrators that are concerned with the following aspects of the RDBMS that NetBackup uses:

Installation overview on page 698 Post-installation tasks on page 707 Backup and recovery procedures on page 712 Database unloading tool on page 716 Moving the NetBackup database from one host to another on page 719

NetBackup installs Sybase ASA 9.0.1 during the master server installation as a private, non-shared server for the NetBackup database (NBDB). The NetBackup database, NBDB, contains the Enterprise Media Manager (EMM) data as well as other NetBackup data that NetBackup services use. The same installation of Sybase ASA is used for the optionally-licensed product, Bare Metal Restore (BMR) and its associated database (BMRDB). The BMR database is created during the BMR installation process.

698 Installation overview

Installation overview
By default, the NetBackup relational database (NBDB) is installed on the master server. The master server is also the default location for the Enterprise Media Manager (EMM) server. Since EMM is the primary user of NBDB, the NetBackup database always resides on the same machine as the Enterprise Media Manager. For performance reasons, the EMM server and the relational database can be moved to another server. The following steps are performed automatically during installation, but can be performed independently after installation. 1 As part of the NetBackup master server installation, the Sybase ASA 9.0.1 server is created. The server parameters are set in the server.conf file:
/usr/openv/var/global/server.conf

The contents of the server.conf file are described in server.conf on page 699. 2 The following entry sets the database location. It is added to the bp.conf file:
VxDBMS_NB_DATA = /usr/openv/db/data

NetBackup configuration entry on page 704. 3 The VxDBMS configuration file for NetBackup is created. This file requires the read and write permissions of root:
/usr/openv/db/data/vxdbms.conf

4 5 6

The NetBackup database is created:

/usr/openv/db/data/NBDB.db

DBA password is set for the NetBackup database in vxdbms.conf:

VXDBMS_NB_PASSWORD = encrypted_password

A minimum of four additional database files are created with contiguous space pre-allocated: The NetBackup system database file (mentioned in step 4):
/usr/openv/db/data/NBDB.db

The EMM database files:

/usr/openv/db/data/EMM_DATA.db /usr/openv/db/data/EMM_INDEX.db

The NetBackup transaction log, necessary for recovering the database:

/usr/openv/db/data/NBDB.log

The Sybase ASA accounts and schema are created for each of the NetBackup components that make use of the NetBackup database. (For example, EMM_MAIN.) The following command initializes the EMM data:
/usr/openv/volmgr/bin/tpext

699 Installation overview

NetBackup master server installation

Sybase ASA is installed in the following directories:

/usr/openv/var/global The files in /global can be shared within a cluster. /usr/openv/db

The contents of each directory are examined in the following sections.

Relocating the NetBackup database

The NetBackup database, NBDB, and its associated files, is created on the master server by default. For performance reasons, NBDB can be moved to another host. NBDB must always be on the same host as the EMM server. The NBDB database files can be moved from their default location in /usr/openv/db/data. (See Moving NBDB database files after installation on page 708.) Note: If Bare Metal Restore is installed, BMRDB must be located on the master server.

server.conf
Caution: Symantec recommends that this file not be edited without assistance from Technical Support. NetBackup may not start if server.conf is edited. /usr/openv/var/global/server.conf is read when the ASA daemon is started. The ASA daemon gets all configuration information from this file:
-n NB_server_name -x tcpip(LocalOnly=YES;ServerPort=13785) DBA -gl DBA -ti 0 -c 25M -ch 500M -cl 25M -gn 10 /usr/openv/db//log/server.log -ud -gp 4096 -ct+ -gd DBA -gk -o

-n NB_server_name Where server_name indicates the name of the Sybase ASA server. Each Sybase server has a unique name. Use the same name that was used during installation. If a fully qualified name was used at that time, use a fully qualified name here. Caution: If this name is changed, the Enterprise Media Manager cannot connect to the database.

700 Installation overview

-x tcpip(LocalOnly=YES;ServerPort=13785) Indicates what kind of connections are allowed in addition to shared memory: local TCP/IP connections using port 13785. -gp 4096 Indicates the maximum page size (in bytes) for the database. This parameter is given during database creation. -ct+ Indicates that character set translation is used. UTF8 encoding is used. -gd DBA -gk DBA -gl DBA Indicates that the DBA user is the account used to start, stop, load, and unload data. -ti 0 Indicates the client idle time that is allowed before shutdown. By default, no idle time is allowed, which prevents the database from shutting down. -c 25M Indicates the initial memory that is reserved for caching database pages and other server information. (May be changed for performance reasons.) -ch 500M Indicates the maximum cache size, as a limit to automatic cache growth (May be changed for performance reasons.) -cl 25M Indicates the minimum cache size, as a limit to automatic cache resizing. (The size may be changed for performance reasons.) -gn 10 Indicates the number of requests the database server can handle at one time. This parameter limits the number of threads upon startup. (May be changed for performance reasons.) -o /usr/openv/db/log/server.log Indicates the location of server output messages. (The messages include start and stop events, checkpoints, error conditions, cache changing size.) This log is not managed, but growth is slow. -ud Indicates that the server should run as a daemon.

databases.conf
The /usr/openv/var/global/databases.conf configuration file contains the locations of the main database files and the database names for automatic startup when the ASA daemon is started. For example, if NBDB and BMRDB are

701 Installation overview

both located on the master server in the default locations, databases.conf contains:
"/usr/openv/db/data/NBDB.db" -n NBDB "/usr/openv/db/data/BMRDB.db" -n BMRDB

vxdbms_env.csh, vxdbms_env.sh
The scripts vxdbms_env.csh and vxdbms_env.sh set up the ASA environment:

/usr/openv/db/vxdbms_env.csh /usr/openv/db/vxdbms_env.sh

Other scripts and commands use vxdbms_env.csh and vxdbms_env.sh.

/bin
/usr/openv/db/bin contains all ASA commands and NetBackup-specific commands:

create_nbdb Used during installation and upgrades to create and upgrade the NetBackup database, NBDB. nbdb_admin Among other things, use nbdb_admin to change the DBA and NetBackup account passwords, or to start and stop individual databases. nbdb_backup Use to make an online or an offline backup of the ASA database files to a file system directory. nbdb_move Use to change the location of the ASA database files from the default location. nbdb_ping Displays the status of the ASA database. nbdb_restore Use to recover from an online or an offline backup in a file system directory that was created using nbdb_backup. nbdb_unload Use to create a dump of all or part of the NBDB database or the BMRDB database schema and data. nbdbms_start_server Use to start and stop the ASA daemon.

702 Installation overview

nbdb_upgrade Used internally to upgrade the NetBackup and BMR databases.

Note: Commands are described in NetBackup Command for UNIX and in the online help.

/charsets
/usr/openv/db/charsets contains ASA-specific information.

/data
/usr/openv/db/data is the default location of the database, NBDB:

NBDB.db Main NetBackup database file; considered a dbspace. EMM_DATA.db An additional dbspace that contains EMM data. EMM_INDEX.db Enhances the EMM database performance. NBDB.log The transaction log for the NetBackup database, necessary for recovery. NBDB.log is automatically truncated after a successful full or incremental online, hot or offline, cold catalog backup of the ASA database. vxdbms.conf Contains the configuration information specific to the Sybase ASA installation:
VXDBMS_NB_SERVER = NB_server_name VXDBMS_NB_PORT = 13785 VXDBMS_NB_DATABASE = NBDB VXDBMS_BMR_DATABASE = BMRDB VXDBMS_NB_DATA = /usr/openv/db/data VXDBMS_NB_INDEX = /usr/openv/db/data VXDBMS_NB_TLOG = /usr/openv/db/data VXDBMS_NB_PASSWORD = encrypted_password

The encrypted password that is used to log into both the DBA accounts for NBDB and BMRDB, and other data accounts is stored in vxdbms.conf. Note: The password is set to a default upon installation (nbusql). Symantec recommends that the password is changed after installation. (See To change the database password on page 707.)

703 Installation overview

If BMR is installed, the directory also contains: BMRDB.db, BMRDB.log (transaction log for BMR), BMR_DATA.db, BMR_INDEX.db

/lib
/usr/openv/db/lib contains all the ASA shared libraries. The directory also includes ODBC libraries, used to connect to NBDB and BMRDB.

/log
/usr/openv/db/log contains the ASA server log file server.log that contains only Sybase logs.

/res
/usr/openv/db/res contains ASA-specific information.

/scripts
/usr/openv/db/scripts contains the ASA SQL scripts that are used to create the database. The directory also contains NetBackup SQL scripts that are used to create the EMM and other schemas. Caution: Do not edit the scripts that are located in /usr/openv/db/scripts.

/staging
/usr/openv/db/staging is used as a temporary staging area during online, hot catalog backup and recovery.

/tix
/usr/openv/db/tix contains ASA-specific information.

704 Installation overview

NetBackup configuration entry

The bp.conf entry, VXDBMS_NB_DATA, is a required entry and is created upon installation. The entry indicates the path to the directory where NBDB.db, BMRDB.db, and the vxdbms.conf file are located. In /usr/openv/netbackup/bp.conf: VXDBMS_NB_DATA = /usr/openv/db/data

705 Installation overview

Sybase ASA server management

Upon startup, the Sybase ASA 9.0.1 server uses the ASA (Adaptive Server Anywhere) daemon to set the server parameters in the server.conf file. Then, the ASA daemon starts the databases that are indicated in the databases.conf file. To start and stop the ASA daemon Use one of the following methods.

Select NB_dbsrv in the Activity Monitor in the NetBackup Administration Console. From the command line:

/usr/openv/netbackup/bin/bp.kill_all | bp.start_all The ASA daemon is included in the stop command or the start command, which starts and stops all NetBackup daemons. /usr/openv/db/bin/nbdbms_start_server ndbms_start_server starts the ASA server if no option is specified. /usr/openv/db/bin/nbdbms_start_server -stop -f Stops the server; -f forces a shutdown with active connections. /usr/openv/db/bin/nbdbms_start_server -stat The -stat option tells whether the server is up or down: Adaptive Server Anywhere Server Ping Utility Version 9.0.1.1965 Ping server successful. /usr/openv/db/bin/nbdbms_start_server -h Use -h to display usage information about the nbdbms_start_server.

To start or stop individual databases The individual databases can be started or stopped, while leaving the ASA daemon to continue running:

nbdb_admin [-start | -stop] Starts or stops NBDB without shutting down the ASA server. To see whether the database is up, enter: nbdb_ping nbdb_admin [-start | -stop BMRDB] Starts or stops BMRDB without shutting down the ASA server. To see whether the BMRDB database is up, enter: nbdb_ping -dbn BMRDB

706 Installation overview

Clusters
Sybase ASA is supported in a clustered environment. Sybase ASA failover is included with the NetBackup server failover solution. The software is installed on all machines in the cluster, but the database files are created on a shared disk. To facilitate the shared files, database and configuration files are installed on a shared drive: Configuration files are stored in /usr/openv/var/global.

707 Post-installation tasks

Post-installation tasks
All tasks are optional and performed at the command line:

Change the database password (description follows) Move NBDB and BMRDB database files (possibly to tune performance) (see Moving NBDB database files after installation on page 708) Add a mirrored transaction log (see To add a mirrored transaction log on page 709) Recreate NBDB (Creating the NBDB database on page 710)

To change the database password

The DBA and application password may be changed at any time. The password is encrypted using AES-128-CFB and stored in the vxdbms.conf file. The permissions on vxdbms.conf allow only root to read or write to the file. Note: Do not change the password after installation. The default password that is set during installation is nbusql. This password is used for NBDB and BMRDB and for all DBA and application accounts. (For example, EMM_MAIN.) To change the database password 1 2 Log on to the server as root. Run the following command: /usr/openv/db/bin/nbdb_admin -dba new_password The vxdbms.conf file is updated with the new, encrypted string.

708 Post-installation tasks

Moving NBDB database files after installation

The nbdb_move command allows the administrator to change the location of the database files or split the database files into multiple directories. Doing so may improve performance in the case of large databases. This command moves both NBDB and BMRDB, if present. nbdb_move is located in the following directory: /usr/openv/db/bin/nbdb_move The nbdb_move command can be run at any time because it does not drop, then recreate the database. Thus, all data is preserved. Note: Back up NBDB and BMRDB using the catalog backup method of choice both before and after running nbdb_move. To move the NBDB database and BMRDB database files 1 2 3 4 Perform a catalog backup. Shut down all NetBackup daemons: /usr/openv/netbackup/bin/bp.kill_all Start the ASA daemon: /usr/openv/netbackup/bin/nbdbms_start_stop start Move the existing data, index, and transaction log files: /usr/openv/db/bin/nbdb_move -data data_directory -index index_directory -tlog log_directory Or, if a mirrored transaction log is in use: /usr/openv/db/bin/nbdb_move -data data_directory -index index_directory -tlog log_directory -mlog log_mirror_directory Start all NetBackup daemons: /usr/openv/netbackup/bin/bp.start_all Perform a catalog backup using the configured method.

5 6

709 Post-installation tasks

To add a mirrored transaction log

The transaction logs NBDB.log and BMRDB.log are critical files used to recover the ASA databases. For extra protection, a mirrored transaction log can be used. This mirrored log should be created in a different directory from the original log. To create a mirrored transaction log 1 2 3 4 Perform a catalog backup. Shut down all NetBackup daemons: /usr/openv/netbackup/bin/bp.kill_all Start the ASA daemon: /usr/openv/netbackup/bin/nbdbms_start_stop start To create the mirrored transaction log only, enter: /usr/openv/db/bin/nbdb_move -mlog log_mirror_directory To move the existing data, index, transaction log files, and create the mirrored transaction log, enter: /usr/openv/db/bin/nbdb_move -data data_directory -index index_directory -tlog log_directory -mlog log_mirror_directory Start up all NetBackup daemons: /usr/openv/netbackup/bin/bp.start_all Perform a catalog backup.

5 6

710 Post-installation tasks

Creating the NBDB database

The NBDB database is created automatically during NetBackup installation. However, it may be necessary during certain catalog recovery situations to create it manually using the create_nbdb command. create_nbdb is located in the following directory: /usr/openv/db/bin/create_nbdb Caution: To recreate the database manually is not recommended in most situations.

Caution: If the NBDB.db database already exists, to run create_nbdb does not overwrite it. If you want to move the database, move it using the nbdb_move command. To create the NBDB database manually 1 2 3 4 5 Shut down all NetBackup daemons: /usr/openv/netbackup/bin/bp.kill_all Start the ASA daemon: /usr/openv/netbackup/bin/nbdbms_start_stop start Run the following command: /usr/openv/db/bin/create_nbdb Start up all NetBackup daemons: /usr/openv/netbackup/bin/bp.start_all The new NBDB database is empty and does not contain the EMM data that is loaded during a normal installation. Make sure that you have the most current support for new devices before the data is repopulated. New devices are added approximately every two months. Note: This procedure differs from releases before NetBackup 6.0. a b Obtain the external_types.txt mapping file from http://entsupport.symantec.com. Place external_types.txt in /usr/openv/var/global The new file replaces the current external_types.txt file.

711 Post-installation tasks

Repopulate the EMM data by running the tpext utility. tpext updates the EMM database with new versions of device mappings and external attribute files. /usr/openv/volmgr/bin/tpext During regular installation, tpext is run automatically.

Caution: If the create_nbdb command is used to create a database manually, the tpext utility must also be run. tpext loads EMM data into the database.

Additional create_nbdb options

Besides using the create_nbdb command to create the NBDB database, it can also be used to perform the following actions. In each command, NB_server_name matches the name in server.conf. For more information, see server.conf on page 699.

Drop the existing NBDB database and recreate it in the default location: create_nbdb -drop The -drop option instructs NetBackup to drop the existing NBDB database. The location of the current NBDB data directory is retrieved automatically from the bp.conf file. Drop the existing NBDB database and do not recreate: create_nbdb -drop_only Drop the existing NBDB database and recreate it in the directories as specified: create_nbdb -drop -data data_directory -index index_directory -tlog log_directory [-mlog log_mirror_directory] If the NBDB database files were moved from the default location using nbdb_move, use this command to recreate them in the same location. Specify current_data_directory.

Caution: If the location of NBDB.db has changed from the default, BMRDB.db must also be recreated. The BMRDB.db files must reside in the same location as the NetBackup database files.

712 Backup and recovery procedures

Backup and recovery procedures

NetBackup catalogs are backed up using one of two methods:

Online, hot catalog backup (recommended method) The online, hot catalog is considered an online, hot method because it can be performed while regular backup activity takes place. Benefits of the online, hot catalog method include:

This method runs per a policy and is virtually transparent to the customer. The policy can be set up using either the Catalog Backup wizard or the Policy wizard. Either wizard automatically includes all the necessary catalog files, to include the database files (NBDB and BMRDB), and any catalog configuration files (vxdbms.conf, server.conf, databases.conf.) This method allows the administrator to recover either the entire catalog or pieces of the catalog. (For example, the databases separately from the image catalog.)

This method offers the incremental backup. For Sybase ASA, the incremental backup means a backup of the transaction log only. Transaction logs are managed automatically, truncated after each successful backup. For more information, see Online, hot catalog backup method on page 283.

Offline, cold catalog backup This type of catalog backup is considered an offline, cold backup because it should not be run when regular backup activity takes place. For Sybase ASA, the databases (NBDB and BMRDB) are shut down during the catalog backup. For more information, see Offline, cold catalog backup method on page 296. The default for the NetBackup environments that upgrade to 6.5 is to remain with the offline, cold catalog backup method. A hot catalog backup would need to be configured.

713 Backup and recovery procedures

Using the online, hot catalog backup method

Normally, a hot, online catalog backup consists of one parent job and two or more child jobs. Events for these jobs appears in the dbm log. An overview of the hot catalog backup process consists of the following steps: 1 A temporary copy of database files is made to a staging directory: /usr/openv/db/staging Once the copy is made, NetBackup can back up the catalog files. A child job backs up files in a single stream:

Configuration files (server.conf, database.conf, vxdbms.conf) Database files:

NBDB.db NBDB.log EMM_DATA.db

EMM_INDEX.db If BMR has been installed:

BMRDB.db BMRDB.log BMR_DATA.db BMR_INDEX.db

A second child job begins the image catalog backup. Note: The backup of any 5.x media server displays as a separate job. Note: If BMR is installed and a remote EMM server is in use, the backup of the EMM server displays as a separate job.

Transaction logs are truncated after a successful full or incremental backup. If the transaction logs are manually changed or deleted, there could be a hole in the recovery. The child job for the relational database backup is normally run on the master server. The master server is the default location for NBDB and the required location for BMRDB. If NBDB has been moved to a media server, the child job runs on the media server. In this case, additional logging for the job appears in the admin log on the media server. If NBDB has been moved to a media server, and BMRDB is installed on the master server, two child jobs exist for the relational database backup

714 Backup and recovery procedures

portion of the online, hot catalog backup. One on the media server for NBDB and one on the master server for BMRDB.

Using the offline, cold catalog backup method

The NetBackup relational database files are included during an offline, cold catalog backup. An overview of the cold catalog backup process consists of the following steps: 1 The ASA databases are queried for the location of the database files associated with the database. In the case of NBDB, the following files are dynamically located:

NBDB.db NBDB.log EMM_DATA.db

EMM_INDEX.db In the case of BMRDB, the following files are dynamically located:

BMRDB.db BMRDB.log BMR_DATA.db

BMR_INDEX db If these files have been moved (using nbdb_move) from the default location (/usr/openv/db/data), the locations are determined automatically. 2 3 4 The databases NBDB and BMRDB are shut down (if BMRDB exists). The Sybase ASA daemon continues to run. The relational database files as identified in step 1, as well as the image catalog files, are backed up. If the backup is successful, the transaction logs are truncated and the databases are restarted. If the backup was not successful, the databases are restarted without truncating the transaction logs.

If NBDB has been moved to a media server, the offline, cold catalog backup includes the database files on the media server. The back up shuts downand starts up the database remotely. Additional logs appear in the admin log on the media server.

Transaction log management

The transaction log for the NetBackup database, necessary for recovering the database, is automatically truncated after a successful catalog backup. (Applies

715 Backup and recovery procedures

to both online, hot or offline, cold catalog backups.) The transaction log, NBDB.log, is located by default in: /usr/openv/db/data/NBDB.log The transaction log continues to grow until it becomes truncated. The online, hot or offline, cold catalog backups must run frequently enough so that the transaction log doesnt grow to fill the file system. In addition to the default transaction log, a mirrored transaction log can be created for additional protection of NBDB using: /usr/openv/db/bin/nbdb_move -mlog mirrored_log_directory The log is called: mirrored_log_directory/NBDB.m.log The directory for the mirrored log should not be the same as the directory for the default transaction log. Ideally, the mirrored log should be located on a file system on a different physical disk drive. If BMR is installed, a transaction log for BMRDB is also created by default in: /usr/openv/db/data/BMRDB.log with an optional mirrored log in: mirrored_log_directory/BMRDB.m.log The BMRDB transaction logs are backed up and truncated during the catalog backup along with the NBDB transaction logs. Caution: If a catalog backup is not run, the logs wont be truncated. Truncation must be managed in this manner as it is critical to recovery of the database.

Catalog recovery
The method that is used to recover the catalog in a disaster recovery situation depends on the method that is used to back up the catalog. Recovery scenarios include:

A full recovery form a complete disaster: Using the Disaster Recovery wizard, the databases are restored along with the image catalog to a consistent state. A recovery of the database files only: Using bprecover, the relational database files and configuration files can be restored and recovered from either an online, hot or offline, cold catalog backup.

Catalog recovery scenarios and procedures are discussed in the NetBackup Troubleshooting Guide.

716 Database unloading tool

Additional command lines for backup and recovery of the relational databases
The recommended method to protect the relational databases is to use the catalog backup and recovery interfaces. In addition, a temporary backup of the NBDB database and the BMRDB database can be made to a directory. Use the backup for extra protection before database administration activities such as to move or to reorganize the database files.

nbdb_backup
Use nbdb_backup to make either an online or an offline copy of the NBDB database files and the BMRDB database files in a directory. The transaction log wont be truncated using nbdb_backup. Transaction logs are managed only by using the catalog backup. /usr/openv/db/bin/nbdb_backup [-dbn database_name][-online | -offline] destination_directory -dbn database_name only backs up the specified database (NBDB or BMRDB). -offline shuts down the database and access to the database. Connections to the database are refused at this time. The ASA daemon does not shut down. Caution: The transaction logs are not truncated using nbdb_backup. A catalog backup must be run to truncate the logs.

nbdb_restore
Use nbdb_restore to recover from a database backup that was made using nbdb_backup. /usr/openv/db/bin/nbdb_restore -recover source_directory These commands are logged in the admin directory.

Database unloading tool

The nbdb_unload command line utility can be used to dump the entire NetBackup or Bare Metal Restore databases, or individual tables (one .dat file is created for each table), or schema. The utility can be used to create a copy of the ASA database that may be requested in some customer support situations. There should be no active connections to the database when nbdb_unload is run.

717 Database unloading tool

For more information, see the following section, Terminating database connections. A reload.sql script is generated when ndb_unload is run. The script contains all the code that is required to recreate the database. Symantec Technical Support uses this script and the associated files to assist in support cases. /usr/openv/db/bin/nbdb_unload [-dbn database_name] [-t table_list] [-s] destination_directory Where:

-dbn database_name database_name is NBDB (default) or BMRDB. -t table_list Must list the owner of the table, then the table name. For EMM, the account EMM_MAIN owns all tables. nbdb_unload -t EMM_MAIN.EMM_Device, EMM_MAIN.EMM_Density -s Schema only is dumped; no data.

destination_directory Specify the location where dump is created.

Terminating database connections

To eliminate concurrency problems, terminate all active connections to the database by shutting down NetBackup before running nbdb_unload. To terminate connections 5 6 7 8 9 Shut down all NetBackup daemons: /usr/openv/netbackup/bin/bp.kill_all Start the ASA daemon: /usr/openv/netbackup/bin/nbdbms_start_stop start Start only the database server by using /usr/openv/netbackup/bin/nbdbms_start_stop start Run nbdb_unload, and indicate the outputs (database name, table lists, or schema only) and the destination directory. Shut down the database server by using /usr/openv/netbackup/bin nbdbms_start_stop stop.

10 Stop the ASA daemon: /usr/openv/netbackup/bin/nbdbms_start_stop stop

718 Database unloading tool

11 Start up all NetBackup daemons: /usr/openv/netbackup/bin/bp.start_all Caution: Symantec does not recommend using reload.sql to make a copy of the relational databases in a production environment. Either nbdb_backup should be used to make a physical copy, or nbdb_move should be used to relocate the database files.

719 Moving the NetBackup database from one host to another

Moving the NetBackup database from one host to another

The NetBackup database, NBDB, must always reside on the same host as the EMM server. If NBDB is moved, the EMM server must also be moved. The Bare Metal Restore database, BMRDB, must always reside on the master server. So, if NBDB and EMM server are moved to a media server from a master server, BMRDB must remain on the master server. Use the following procedure to move the NetBackup database (NBDB) from host A to host B. This procedure also reconfigures NetBackup so that the new database host becomes the EMM server. If you move the NetBackup database and the EMM server to a different host in a cluster environment, see Cluster considerations with the EMM server on page 721. 1 2 Perform a catalog backup. If NetBackup is currently installed on B: a b c d Shut down all NetBackup daemons on B: /usr/openv/netbackup/bin/bp.kill_all Change the EMMServer entry in the bp.conf file from A to B on B. Start the Sybase ASA server on B: /usr/openv/netbackup/bin/nbdbms_start_stop start

Create NBDB and associated files in the default location (/usr/openv/db/data) on B: /usr/openv/db/bin/create_nbdb Or, if NetBackup has not been installed on B: Install NetBackup on B, identifying B as the EMM server during installation. Set the database password on host B to match the password on A if the password has been changed from the default: /usr/openv/db/bn/nbdb_admin -dba password Shut down NetBackup on A, B, and on all master servers and media servers that use host A as the EMM server: /usr/openv/netbackup/bin/bp.kill_all Copy the following catalog files from their location on A to the final location on B:

Note: The final location on B does not need to be the same as the original location on A.

720 Moving the NetBackup database from one host to another

Note: Do not copy vxdbms.conf. NBDB.db EMM_DATA.db EMM_INDEX.db NBDB.log NBDB.m.log (optional) If the database files on A and B are in the default location and server A is also a UNIX server, go to step 11. (The default location is /usr/openv/db/data.) 6 Change databases.conf on A and B so that the databases dont start automatically when the server is started: /usr/openv/db/bin/nbdb_admin -auto_start NONE Start the Sybase ASA server on B: /usr/openv/netbackup/bin/nbdbms_start_stop start To update the catalog with the location of the database files on B: nbdb_move -data dataDirectoryB -index indexDirectoryB -tlog tlogDirectoryB [-mlog mlogDirectoryB] -config_only Stop the Sybase ASA server on B: /usr/openv/netbackup/bin/nbdbms_start_stop stop

7 8

10 On B: for any database files copied to non-default locations in step 5, go to the default directory on B and delete the appropriate database files. EMM_DATA.db EMM_INDEX.db NBDB.db NBDB.log NBDB.m.log (optional) 11 Change the EMMSERVER entry in the bp.conf file from A to B on all master servers and media servers that had used A as the EMM server. 12 On A, delete the database files and configuration files: EMM_DATA.db EMM_INDEX.db NBDB.db NBDB.log NBDB.m.log (optional) 13 On A:

If BMRDB does not exist on A, delete the following configuration files:

721 Moving the NetBackup database from one host to another

dataDirectoryA/vxdbms.conf /usr/openv/var/global/databases.conf /usr/openv/var/global/server.conf Remove the VXDBMS_NB_DATA entry from the bp.conf file.

If BMRDB exists on A, execute the following command on A so that BMRDB starts automatically when the server is started: /usr/openv/db/bin/nbdb_admin -auto_start BMRDB

14 Start NetBackup on B: /usr/openv/netbackup/bin/bp.start_all 15 Start NetBackup on all master servers and media servers that use B as the EMM server: /usr/openv/netbackup/bin/bp.start_all 16 Perform a full catalog backup.

Cluster considerations with the EMM server

If you move the NetBackup database and the EMM server to or from a UNIX cluster, update the *_NBU_RSP configuration file. Add or remove the EMM server name as appropriate. The *_NBU_RSP configuration file resides in the following directory:
/usr/openv/netbackup/cluster/cluster_type/

The directory name and the prefix of the file name depend on the cluster type.

722 Moving the NetBackup database from one host to another

Appendix

AdvancedDisk storage option

The NetBackup AdvancedDisk storage option lets you use disk storage directly attached to a NetBackup media server. NetBackup aggregates the disks into pools of storage you can use for backups. NetBackup manages the storage as logical entities (disk pools). Figure B-1 Media server and disks
NetBackup media server

Directly-attached disks

The NetBackup AdvancedDisk storage option provides the following benefits:

The option is easy to deploy and use. NetBackup discovers the storage and uses familiar NetBackup storage units and backup policies to use the storage. Allows multiple file systems to be used in a single storage unit. Storage unit capacity can be increased by adding disks. Only add what you need, when you need it, then update the NetBackup disk pools. Logical units of storage span physical boundaries, so you do not have to create new NetBackup storage units or change the backup policies. Reduces level of administrator attention through automatic policies that distribute job load and intelligently manage capacity so that jobs do not fail because of out of space conditions.

The terms that are used in AdvancedDisk include:

724 Licensing AdvancedDisk

Data mover: An entity that moves data between the primary storage (the NetBackup client) and the storage server. In AdvancedDisk, NetBackup media servers function as data movers. 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. In AdvancedDisk, NetBackup media servers function as both storage servers and data movers. Disk volume: A logical unit of disk storage. Disk pool: A collection of disk volumes that are administered as an entity.

Licensing AdvancedDisk
No special installation is required for the NetBackup components of AdvancedDisk. However:

The NetBackup master server and all NetBackup media servers that use the feature must be at NetBackup 6.5 or later. You must activate the feature by entering the Flexible Disk Option license key on the NetBackup master server.

You may have one license key that activates NetBackup and all of your add-on products. Alternatively, you may have a separate license key for NetBackup and for each add-on product such as AdvancedDisk. If you remove the Flexible Disk Option license key or if it expires:

You cannot create the disk pools or the storage units that reference AdvancedDisk disk pools. NetBackup jobs that attempt to use the disk pools or the storage units that are based on disk pools fail. The error message indicates that the feature is not licensed. NetBackup does not delete the disk pools or the storage units that reference the disk pools. You can use them again if you enter a valid license key.

Creating an AdvancedDisk storage server

A storage server is an entity that mounts the storage and writes data to and reads data from the disk storage. For AdvancedDisk, one NetBackup media server functions as both a storage server and a data mover. (A data mover moves data to be protected from primary storage to the storage server.) Create in this context means to configure as a

725 Creating an AdvancedDisk storage server

storage server the NetBackup media server host in which the disks are installed. The storage server owns exclusive access to the storage. Figure B-2 Combined storage server and data mover

NetBackup media server functions as both storage server and data mover

NetBackup clients

To determine if a media server is configured as a storage server already

Run the following nbdevquery command on the NetBackup master server:

/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs

The command lists all storage servers already configured. By default, NetBackup configures all media servers as BasicDisk storage servers. Therefore, all media servers in your environment appear as BasicDisk servers, as in the following example:
/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs V6.5 tree.symantecs.org BasicDisk 5 V6.5 flower.symantecs.org BasicDisk 5 V6.5 water.symantecs.org BasicDisk 5

If the media server does not appear in the command output as an AdvancedDisk storage server, configure the media server as a storage server. To configure an AdvancedDisk storage server in NetBackup

Run the following nbdevconfig command on the NetBackup master server or the media server:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server storage_server -stype AdvancedDisk [-st storage_type] -media_server media_server

The following are the options and arguments:

-storage_server storage_server is the name of the NetBackup media server that has a file system mount on the storage. -stype AdvancedDisk value specifies the storage server type. -st storage_type is a numeric value that specifies the server properties. For AdvancedDisk, the default is 5 (direct attached, formatted disk). Required only if you want to use a value other than the default.

726 Creating an AdvancedDisk disk pool

The value is obtained by adding together the numeric values of the following properties. Whether the disk is formatted and how it is attached are mutually exclusive and complementary.

1 - formatted disk. The disk is formatted as part of the vendor-specific preparation; NetBackup does not format the disk. 2 - raw disk. The disk is not formatted; NetBackup formats the disk. 4 - direct attached. Direct attached means that the storage server and media server are the same NetBackup host. 8 - network attached. Network attached means the storage server is physically distinct from the NetBackup media server. It does not imply LAN data movement nor does it preclude Fibre Channel as the transport for data movement.

-media_server media_server is the name of the NetBackup media server that performs the operation. Use the same name as the storage server name.

Creating an AdvancedDisk disk pool

An AdvancedDisk disk pool represents disk volumes in the underlying disk storage. NetBackup aggregates the disk volumes into pools of storage you can use for backups. If necessary, backup images span disk volumes in a disk pool. Backup images do not span across multiple disk pools. Figure B-3 Disk pools

vol1
Disk volumes

AdvDiskPool _Gold

vol2 vol3
AdvDiskPool _Silver

A disk pool is the storage destination of a NetBackup storage unit. NetBackup assumes exclusive ownership of the disk resources that comprise the disk pool. If you share those resources with other users, NetBackup cannot manage disk pool capacity or storage lifecycle policies correctly. When you create a disk pool, you specify:

The storage server.

727 Creating a storage unit

The disk volumes to include in the pool. The disk pool properties. Properties include the name, the high water mark, the low water mark, and a comment that describes the disk pool. Symantec recommends that disk pool names be unique across your enterprise. For more information, see Disk pool properties on page 732.

When NetBackup sends backup data to a disk pool, NetBackup selects disk volumes based on available capacity and predicted size of the backup. NetBackup tries to write backup data to a single volume. If necessary, backup images span disk volumes in a disk pool. Backup images do not span across multiple disk pools. You must first configure the media server as a storage server. For procedures, see Creating an AdvancedDisk storage server on page 724. To create an AdvancedDisk disk pool 1 2 In the NetBackup Administration Console tree, select Media and Device Management. From the list of wizards in the Details pane, click Configure Disk Pool and follow the wizard instructions. For help, see the wizard help.

Creating a storage unit

Create one or more storage units that reference the disk pool. The Disk Pool Configuration Wizard lets you create a storage unit; therefore, you may have created a storage unit when you created a disk pool. To determine if storage units exist for the disk pool, see the NetBackup Management > Storage > Storage Units window of the Administration Console. For disk pool storage unit recommendations, see Usage recommendations on page 730. To create a storage unit from the Actions menu 1 In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units.

728 Creating a storage unit

Click Actions > New > Storage Unit.

Complete the fields in the New Storage Unit dialog box.

The following are the configuration options for a disk pool storage unit. Storage unit name Enter a unique storage unit name for the new storage unit. The name can describe the type of storage. The storage unit name is the name used to specify a storage unit for policies and schedules. The storage unit name cannot be changed after creation. Storage unit type Select Disk as the storage unit type. Disk type Select AdvancedDisk. Disk pool Select the disk pool that contains the storage for this storage unit. All disk pools of the specified Disk type appear in the Disk pool list. If no disk pools are configured, no disk pools appear in the list.

729 Creating a storage unit

Media server The Media server setting specifies the NetBackup media server that moves data to and from the storage server. Only the NetBackup media server that is configured as the storage server can move data to and from the disk pool. NetBackup selects the media server to use when the policy runs. Maximum concurrent jobs The Maximum concurrent jobs setting specifies the maximum number of jobs that NetBackup can send to a disk storage unit at one time. (Default: 1 job. The job count can range from 0 to 256.) This setting corresponds to the Maximum concurrent write drives setting for a Media Manager storage unit. NetBackup queues jobs until the storage unit is available. If three backup jobs are ready to be sent to the storage unit and Maximum concurrent jobs is set to two, the first two jobs start and the third job waits. If a job contains multiple copies, each copy applies toward the Maximum concurrent jobs count. The number to enter depends on the available disk space and the server's ability to run multiple backup processes. You can use maximum concurrent jobs to balance the load between disk storage units. A higher number of concurrent jobs means that the disk can be busier than if the number is lower. Caution: A Maximum concurrent jobs setting of 0 disables the storage unit. For information about how NetBackup balances storage unit and media server load, see Maximum concurrent jobs in NetBackup Administrators Guide for UNIX and Linux, Volume I. Maximum fragment size Specify the largest fragment size that NetBackup can create to store backups. The default maximum fragment size for a disk storage unit is 524,287 megabytes. To specify a maximum fragment size other than the default, enter a value from 20 megabytes to 524,287 megabytes. Backups to disk are usually fragmented to ensure that the backup does not exceed the maximum size that the file system allows. If an error occurs in a backup, the entire backup is discarded. The backup restarts from the beginning, not from the fragment where the error occurred. (An exception is for backups for which checkpoint and restart is enabled. In that case, fragments before and including the last checkpoint are retained; the fragments after the last checkpoint are discarded.)

730 Creating a storage unit

Usage recommendations
For usage recommendations, see the following:

Multiple storage units

You can use multiple storage units for one disk pool to separate your backup traffic and still write all data to the same disk pool. You do not need to partition the storage because all storage units use the same pool of storage. Example 1 For example, if you use the NetBackup Fibre Transport option, you can separate the NetBackup SAN client traffic from the regular NetBackup client traffic in your environment:

Define a storage unit (such as STU-FT). Select the disk pool. Select Only use the following media servers. Select the FT media servers that connect to the SAN clients. Create a backup policy for the SAN clients and select the STU-FT storage unit. Define another storage unit (such as STU-LAN). Select the same disk pool. Select Only use the following media servers. Select the media servers with LAN connectivity to the regular clients. Create a backup policy for the regular clients and select the STU-LAN storage unit.

This scenario assumes that the SAN clients are a small subset of your client base. It also assumes that the media servers with LAN connectivity to the regular clients also have SAN connectivity to the storage. Example 2 Even without a SAN, you can separate your backup traffic similarly and still write all of the data to the same disk pool. For example, you can send the backups from your most important clients to a media server that is dedicated for the most important backups:

Define a storage unit (such as STU-CRITICAL). Select the disk pool. Select Only use the following media servers. Select one (or a subset) of the media servers. Create a backup policy for the critical clients and select the STU-CRITICAL storage unit. Define another storage unit (such as STU-NORMAL). Select the same disk pool. Select Only use the following media servers. Select a different subset of the media servers.

731 Managing disk pools

Create a backup policy for the regular clients and select the STU-NORMAL storage unit.

Maximum concurrent job setting

You can use the multiple concurrent jobs settings on storage units to assign backup priority for important clients. For example, two storage units use the same set of media servers. One of the storage units has a higher concurrent job setting than the other. More client backups occur for the storage unit with the higher concurrent job setting.

Managing disk pools

The following subsections describe how to manage disk pools.

Changing disk pool properties

You can change the high and the low water marks of a disk pool and change the comment that is associated with the disk pool. To change disk pool properties 1 2 3 In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools. Select the disk pool you want to change in the details pane. Click Edit > Change.

732 Managing disk pools

In the Change Disk Pool dialog box, change properties.

Disk pool properties

The following are the disk pool properties:

The disk pool name. The storage server name. The storage server is the same as the NetBackup media server to which the storage is attached. The disk volumes that comprise the disk pool. The total amount of space available in the disk pool. The total raw, unformatted size of the storage in the disk pool. A comment that is associated with the disk pool. The high water mark for the disk pool. (The default is 98%.)

733 Managing disk pools

The high water mark is a threshold that indicates the storage is full. It applies to both the individual disk volumes in the pool and the disk pool, as follows:

Individual volumes. When a disk volume reaches the high water mark, NetBackup writes the data to another disk volume in the pool. Disk pool. When all volumes are at the high water mark, the disk pool is full. When a disk pool approaches the high water mark, NetBackup reduces the number of jobs that are allowed to write to the pool. NetBackup does not assign new jobs to a storage unit in which the disk pool is full.

The low water mark for the disk pool. (The default is 80%.) When the capacity of the disk pool returns to the low water mark, NetBackup again assigns jobs to the storage unit. Capacity is regained as backup images expire. The low water mark setting cannot be greater than or equal to the high water mark setting.

Adding volumes to an AdvancedDisk disk pool

You can expand a disk pools capacity by adding disk volumes to the disk pool. The names of the new volumes must differ from the names of the volumes in the current disk pool. (By default, NetBackup automatically increases disk pool capacity if the capacity of the underlying disk volumes increases. Similarly, NetBackup decreases the capacity of a disk pool if the underlying disk volume capacity decreases.) The NetBackup storage units that use the disk pool automatically use the additional storage capacity. You do not have to change the storage units. Note: Be careful when you add volumes to a disk pool. For data integrity, NetBackup does not allow volumes to be deleted from a disk pool. Because backup images may span disk volumes, a volume may contain valid image fragments. To remove a disk volume, you must delete all valid backup images and then delete the disk pool. To add volumes to an AdvancedDisk disk pool 1 2 Create a disk pool from the new disk volumes on the storage server. For procedures, see Creating an AdvancedDisk disk pool on page 726. Change the state of the two disk pools to DOWN. The following is the command syntax:

734 Managing disk pools

/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name -state DOWN

If backup jobs are assigned to a disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete. 3 Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge.
/usr/openv/netbackup/bin/admincmd/nbdevconfig mergedps -stype AdvancedDisk -primarydp disk_pool_name -secondarydp disk_pool_name

Change the state of the primary disk pool to UP. The following is the command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig/nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name -state UP

Changing disk pool or volume state

Pool and volume states are UP or DOWN. You can change the state of a disk pool or volume. To change the state to DOWN, the disk pool must not be busy. If backup jobs are assigned to the disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete. Note: For data integrity, NetBackup does not allow volumes to be deleted from a disk pool. Because backup images may span disk volumes, a volume may contain valid image fragments. To remove a disk volume, you must delete all valid backup images and then delete the disk pool. To change the disk pool state by using the Device Monitor 1 2 3 4 In the NetBackup Administration Console, select Media and Device Management > Device Monitor. Select the Disk Pools tab. Select the disk pool. Select either Actions > Up or Actions > Down.

To change the disk volume state 1 Determine the name of the disk volume. The following command lists all volumes in the specified disk pool:
/usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype AdvancedDisk -dp disk_pool_name

735 Managing disk pools

Change the disk volume state; the following is the command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name dv vol_name -state state

state is UP or DOWN. NetBackup jobs still read from and write to a disk pool that has a downed volume, but the downed volume is unavailable.

Merging disk pools

You can merge existing AdvancedDisk disk pools. NetBackup updates the catalog records to show the correct location of the backup images in those disk pools. Prerequisites:

The volumes in the two disk pools must have unique names. If the secondary disk pool is referenced by storage units, you must delete those storage units.

To merge disk pools 1 Change the state of each disk pool to DOWN; the following is the command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig/nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name -state DOWN

If backup jobs are assigned to a disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete. 2 Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge.
/usr/openv/netbackup/bin/admincmd/nbdevconfig mergedps stype AdvancedDisk -primarydp disk_pool_name -secondarydp disk_pool_name

Change the state of the primary disk pool to UP. The following is the command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name -state UP

Deleting a disk pool

If you delete a disk pool, NetBackup removes it from your configuration. If a disk pool is the storage destination of a storage unit, you must first delete the storage unit.

736 Managing disk pools

Caution: Do not delete a disk pool that contains unexpired NetBackup images; if you do, data loss may occur. To delete a disk pool 1 2 3 4 In the NetBackup Administration Console tree, select Media and Device Management > Devices > Disk Pools. Select a disk pool Click Edit > Delete. In the Delete Disk Pool dialog box, verify that the disk pool is the one you want to delete and then click OK.

Obtaining disk pool and volume status

Use the NetBackup nbdevquery command to obtain the status of NetBackup disk pools and volumes in those disk pools. For more information, see NetBackup Commands for UNIX and Linux. Table B-1 Option
-dv disk_volume

nbdevquery disk pool options Description

Used with -listdv, it shows the properties of the specified disk volume. Produces the parsable output, one line of output per disk volume with no headers. The first field indicates the version of the output as an aid to create scripts. By default, nbdevquery uses the -l option. Shows all disk pools. To show the properties of a specific disk pool, also use the -dp disk_volume option.

-l

-listdp

-listdv

Shows a summary of all disk volumes. To show the properties of a specific disk volume, also use the -dv disk_volume option.

737 Managing storage servers

Table B-1 Option

nbdevquery disk pool options Description

Use this option with the following two options:

-stype server_type

With -listdp, shows all disk pools of the specified storage type. With -listdv, shows all disk pools of the specified storage type and their disk volumes.

Use AdvancedDisk for the server_type argument.

-U -D

Produces an output format that is more human-readable. Produces an output format that provides more information than the -U option but has less formatting.

Managing storage servers

For AdvancedDisk, the NetBackup media server to which the storage is attached functions as both a storage server and a data mover. The storage server owns exclusive access to the storage.

Viewing storage servers

To view a list of storage servers already configured, use the nbdevquery command. To view configured storage servers

Run the following nbdevquery command on the NetBackup master server:

/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs

The command lists all storage servers already configured. By default, NetBackup configures all media servers as BasicDisk storage servers. Therefore, all media servers in your environment appear as BasicDisk servers, as in the following example:
/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs V6.5 tree.symantecs.org BasicDisk 5 V6.5 flower.symantecs.org BasicDisk 5 V6.5 water.symantecs.org BasicDisk 5

If the media server does not appear in the command output as an AdvancedDisk storage server, configure the media server as a storage server.

738 Monitoring storage capacity and usage

Deleting a storage server

If you delete a storage server, NetBackup removes it from your configuration. However, the media server is not deleted from your configuration. (An AdvancedDisk storage server is also a NetBackup media server.) To delete the media server, use the NetBackup nbemmcmd command. If a disk pool is configured from the disk volumes that the storage server manages, the storage server cannot be deleted. Caution: Do not delete a storage server if its storage contains unexpired NetBackup images; if you do, data loss may occur. To delete a storage server

Use the following command:

/usr/openv/netbackup/bin/admincmd/nbdevconfig -deletests -storage_server storage_server_name -stype AdvancedDisk

Obtaining storage server status

The NetBackup nbdevquery command lets you obtain the status of storage servers. Table B-2 Option
-liststs -storage_server server_name -stype server_type

nbdevquery storage server options Description

Shows all storage servers. Shows the information about the specified storage server. Must be used with the -liststs option. Use this option with the following two options:

With -liststs, shows all storage servers of the specified storage type. With -storage_server, shows all storage servers that are at the specified host.

Use AdvancedDisk for the storage server type (-stype).

For usage information, see NetBackup Commands for UNIX and Linux.

Monitoring storage capacity and usage

To monitor storage capacity and usage, see:

739 Troubleshooting AdvancedDisk

The NetBackup Disk Pool status report. For more information, see Disk Reports on page 79. Media and Device Management > Devices > Disk Pools. The NetBackup License Keys dialog box. Open the dialog box by selecting Help > License Keys in the NetBackup Administration Console. Display the summary by clicking Summary of active capacity-based license features. The summary displays the storage capacity for which you are licensed and the capacity used. It does not display the amount of physical storage space.

The NetBackup Operations Manager also provides information about storage capacity and usage. For more information, see the NetBackup Operations Manager Guide.

Troubleshooting AdvancedDisk
The following may help you troubleshoot AdvancedDisk.

Unable to access storage

If NetBackup cannot access the storage, one possible cause is that the storage server was created with the incorrect nbdevconfig storage type (-st) value. For example, an AdvancedDisk storage server -st value is 5 (formatted disk, directly attached). For AdvancedDisk, values other than 5 are incorrect. To determine the configured value, use the following nbdevquery command:
/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs -stype AdvancedDisk -U

The following output shows an incorrect value for AdvancedDisk:

Storage Server : halo Storage Server Type : AdvancedDisk Storage Type : Formatted Disk, Network Attached

To resolve an incorrect storage type problem 1 2 3 4 5 Delete all disk pools that use the storage server. Delete the storage server. Reconfigure the storage server. Recreate the disk pools. If necessary, specify the new disk pools in the storage units. If you recreated the disk pools with the same names as the ones you deleted, this step is not necessary.

740 Troubleshooting AdvancedDisk

Volume state changes to DOWN when volume is unmounted

If a volume becomes unmounted, NetBackup changes the volume state to DOWN. NetBackup jobs that require that volume fail. To determine the volume state, use the following nbdevquery command to display the disk volumes and their states:
/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs -listdv -stype AdvancedDisk -U

The following output shows that a volume named /mnt/nbu is DOWN.

Disk Pool Name Disk Type Disk Volume Name Status Flag : : : : : AdvDiskPool_Bronze AdvancedDisk /mnt/nbu DOWN AdminUp

To change the volume state to UP

Mount the filesystem

After a brief period of time, the volume state changes to UP. No further action is required.

Disk failure
If recovery mechanisms do not protect a disk that fails, the backup images on that disk are lost. Operating system read and write errors may occur for the volume that represents the disk. NetBackup cannot use that volume because of the errors, and NetBackup jobs may fail. To prevent NetBackup from trying to read from or write to the disk, you must change the volume state to DOWN in NetBackup. If the volume represents other disks that still function, those disks are not available because the volume state is DOWN. You may be able to read from the volume by mounting it manually, in which case you may be able to recover image fragments from any disks that did not fail. If you replace a failed disk, you can use the same mount point for the replacement disk. Change the volume state to UP, and NetBackup uses that volume again. Any valid backup images on that volume are available for restores.

Appendix

NearStore storage units

This document contains information about how to administer Network Appliance (NetApp) NearStoreTM disk storage units using NetBackup 6.5. This feature is also known as the SnapVault for NetBackup solution. The NearStore disk storage unit features introduced in this version are available on all supported media server platforms. This document contains the following sections:

Required software, hardware, and licenses on page 742 Upgrade considerations on page 744 NearStore disk storage unit advantages on page 745 Restrictions in the current release on page 746 NearStore configuration on page 747 NearStore disk storage unit properties on page 750 Viewing the backup image on page 753 Disk consumption on page 753 Disaster recovery using volume SnapMirror on NearStore disk storage units on page 755 Troubleshooting on page 764

For general disk storage unit setup information, see Chapter 5 in this guide. See the Data ONTAP System Administrators Guide for more information about any NetApp commands referenced. Terms used in this document include: Data ONTAP: The NetApp storage operating system provides unified data management for both block and file serving environments. file system export mode: In the file system export mode, backups become user-mountable when exported as CIFS or NFS file systems. This mode is in effect when both the Enable file system export setting and the Enable block

742 Required software, hardware, and licenses

sharing setting are enabled. NetApp also refers to this mode as context-aware SIS. The file system export mode adds functionality to the space optimized image mode by enabling a file system export of the backup image. Mount the backup image as a file system, drag-and-drop or copy files to restore location. image mode: This mode is in effect when neither Enable block sharing or Enable file system export are selected in the storage unit dialog box. In the image mode, the disk storage unit acts much like a BasicDisk storage unit in how data is stored. qtree (quota tree): A subdirectory in a NearStore volume that acts as a virtual subvolume with special attributes, primarily quotas and permissions. snapshot: A read-only, point-in-time copy of the entire file volume. A snapshot captures file modifications without duplicating file contents. SnapVault: Allows exports of snapshot copies to another NetApp system, providing an incremental block-level backup solution. space optimized image mode: The space optimized image mode is in effect when the Enable block sharing setting is enabled in the NearStore disk storage unit dialog. This mode makes use of single-instance store (SIS) without the additional requirement of managing snapshots. NetApp also refers to this mode as context independent SIS or advanced single instance store. To use this mode, the nearstore_asis1 license must be turned on for each volume. WAFL (Write Anywhere File Layout): The file system used in all NetApp storage servers. WAFL supports snapshot creation.

Required software, hardware, and licenses

To configure a NearStore disk storage unit, the following hardware and software (and accompanying licenses) must be in place and configured:

NetBackup Enterprise on the master server and media server, with the OpenStorage Disk Option license installed. NetBackup client software 5.0 or later. A NetApp NearStore server running Data ONTAP 7.2 or later, with the following software installed:

A SnapVaultTM secondary license (enabled) A NetApp nearstore_option license (required when a NetApp FAS device, such as a FAS3050, is used)

To configure the storage unit to use the space optimized image mode (Enable block sharing enabled) the nearstore_asis1 license must be turned on for each volume on the filer.

743 Required software, hardware, and licenses

744 Upgrade considerations

Upgrade considerations
To use the file system export mode or the space optimized image mode, both NetBackup 6.0 MP4 and ONTAP 7.2 (or later) are required. However, if the new functionality is not needed, the following version combinations are supported:

NetBackup 6.0 MP4 and ONTAP 7.1 NetBackup 6.0 and ONTAP 7.2

NearStore and SnapVault considerations

NearStore disk storage units and SnapVault storage units cannot share volumes NearStore and SnapVault storage units cannot share the same volume. To prepare a volume to support NearStore storage units:

Disable any incremental backups to the secondary qtrees that were originally scheduled for the volume. Release existing SnapVault relationships. Use the NetApp snapvault -stop command to stop all backups and delete the qtrees and configurations on a volume. Disable any existing WAFL snapshots on the volume. This includes the default WAFL snapshot schedule that is automatically configured when the volume is created.

Clean up configured qtrees Qtree entries in the SnapVault configuration database are not deleted when a volume is destroyed. Make sure to delete the qtree entry in the configured database. Manage NearStore SnapVault snapshot schedules Use the snapvault snap sched command to display the currently configured SnapVault snapshot schedule. The command allows you to view the basenames of all snapshot sets for all SnapVault volumes on the filer. Note: Volumes configured for NetBackup NearStore disk storage units do not support the snapvault snap sched command. Any attempt to run the snapvault snap sched command on a NetBackup NearStore volume will fail. Use the snapvault snap unsched command to turn off the SnapVault schedule for a set of snapshots and stop the snapshot process for the SnapVault secondary storage system.

745 NearStore disk storage unit advantages

Note: The snapvault snap unsched command does not end the SnapVault relationships between the secondary system qtrees and their platform source drives or directories. To do so, run the snapvault stop command for each qtree configured or existing on the volume to be used as a NearStore disk storage unit.

Perform initial full backups for client and policy pairs For every client and policy pair, a full backup must be performed to a NearStore disk storage unit before an incremental of any type can be performed.

NearStore disk storage unit advantages

Backup data reduction NearStore avoids duplicating disk blocks by comparing blocks in the most recent backup with the preceding backup image. Incremental backups do not consume disk space unless blocks in the new backup image differ from blocks in the active file system. As a result, multiple backups to the same volume store only uncommon blocks, and blocks that are common continue to share. Space savings are based on a per-client basis and only for files with identical names. Use the Data ONTAP snapvault status -b command to view data on the space savings. For example:
gabe*> snapvault status -b Snapvault secondary is ON. Volume actual used -------------image_size_vol 1471MB 1174MB

saved ----297MB

%saved -----20%

ratio ----1.25:1

Tar image retained for interoperability The NetBackup tar image is preserved in a WAFL qtree to support NetBackup administrative functions such as file restoration, duplication, disk staging, import from disk, and twinning to another storage unit. No NetBackup administrator necessary to perform user restores Backups to NearStore disk storage unit with the file system export option enabled do not require a NetBackup administrator to perform restore. File system export allows the NetApp storage system to present a normal CIFS or NFS file system to users to perform simple file restores.

746 Restrictions in the current release

Restrictions in the current release

A NearStore requires an Ethernet connection because data is transferred over a TCP/IP socket. Gigabit Ethernet (GbE) is preferred. A NearStore disk storage unit does not support the checkpoint restart feature. This restriction will be removed in future NetBackup releases. A NearStore disk storage unit does not support backups based on the following policy configurations: In space optimized In file system image mode export mode
Yes No No No

Backup policy configuration

NetBackup for Microsoft SQL Server NetBackup for Microsoft SQL Server (multistreamed) NetBackup for Sybase NetBackup for Sybase (multistreamed) NetBackup for Oracle proxy block level incremental NetBackup for Oracle proxy block level incremental (multistreamed)

In Image mode
Yes No

Yes No

No No

Yes No

Yes

No

Yes

No

No

No

A NearStore disk storage unit with the file system export option enabled does not support user backups. NetBackup does not collect True Image Restore information for user backups, and the file system export mode requires that TIR information be collected. For more information, see Collect true image restore information on page 108. A NearStore disk storage unit with the file system export option enabled does not support hot catalog backups. Hot catalog backups rely, in part, on the user backup process that does not collect TIR information. NearStore disk storage units cannot be included in storage unit groups. NearStore disk storage units cannot operate in conjunction with the clustering functionality in ONTAP 7.2 or earlier. Clustering is turned on by default on some filers. To allow NearStore functionality, remove the clustering license and reboot the filer.

747 NearStore configuration

NearStore disk storage units offer partial support for basic disk staging: In space optimized image mode
No Yes

Basic disk staging storage unit configuration

Stage I disk staging storage unit Stage II disk staging storage unit(final destination)

In file system export mode

No Yes

In image mode
Yes Yes

NearStore configuration
To make the SnapVault storage unit available for backups, add, enable, and configure SnapVault on the secondary filer. Run the following commands on the secondary filer: To configure SnapVault on the secondary filer 1 2 3 Add the secondary SnapVault license: license add sv_secondary_license Enable SnapVault: options snapvault.enable on Grant access to the primary filer and to the media servers authorized to access the NearStore system by entering the following command: options snapvault.access host=nbu_media_server1, nbu_media_server2...

NearStore authentication
A NearStore user name and password must be configured in NetBackup before the storage unit is created. NearStore authentication information is stored in the NetBackup Enterprise Media Manager (EMM) database. Note: A NetBackup NDMP license is not required to create a NearStore disk storage unit. However, to use the NetBackup Administration Console to enable NearStore credentials instead of tpconfig, NDMP must be enabled. To authenticate the NetBackup media server 1 2 In the NetBackup Administration Console, select Media and Device Management > Devices > NDMP Hosts. From the Actions menu, select New > New NDMP Host. The Media and Device Management dialog box appears.

748 NearStore configuration

3 4

In the dialog box, provide the name of the secondary host. Click OK. Specify the credentials on the NDMP host. Use global credentials or credentials specific to this host.

Credentials can also be configured using the tpconfig command. To create a root NearStore user name and password tpconfig -add -snap_vault_filer -nh hostname -user_id root_ID [-password root_password] Note: It is important to avoid using root as an NDMP password because root is not encrypted, and could compromise the integrity of your storage system. To create a non-root NearStore user name and password Administrators can create user accounts on the NearStore to perform backups and restores. The following procedure describes a method to send a users encrypted password over the network. 1 2 Log onto the Nearstore. To create a new user, enter the following command: useradmin user add userID -g groupID Enter a password when prompted. To receive the encrypted version of the password, enter: ndmpd password userID where userID is the name of the user just added. Record the password. Log out of the NearStore. Enter the following tpconfig command: tpconfig -add -user_id username -nh nearstore_name -snap_vault_filer -password encrypted_password The encrypted password is passed across the network.

4 5 6

To verify that the NearStore credentials have been entered into the NetBackup EMM database Once the tpconfig command is run, ensure that the media server is authenticated by running the following command: nbemmcmd -listhosts -list_snap_vault_filers -machinename media_server_name For example:

749 NearStore configuration

C:\Program Files\VERITAS\NetBackup\bin\admincmd> nbemmcmd -listhosts -list_snap_vault_filers -machinename entry NBEMMCMD, Version:6.0CA(20050628) The following hosts were found: ndmp mmnetapp.xxx.yyy.com Command completed successfully.

750 NearStore disk storage unit properties

NearStore disk storage unit properties

The properties that are specific to NearStore storage units are described in the following sections. The entries in this dialog are case-sensitive. Figure C-1 Creating a new NearStore disk storage unit

Space optimized image mode

File system export mode If neither option is enabled, the storage unit uses image mode (which acts much like a BasicDisk storage unit)

Displays only those volumes that are available to the NearStore disk storage unit

Storage unit type

For a NearStore storage unit, select Disk as the Storage unit type.

On demand only
A NearStore disk storage unit can only be used on demand. On demand only cannot be deselected.

751 NearStore disk storage unit properties

Disk type
Depending on what is licensed, there are a number of disk types available from which to choose. To configure a NearStore storage unit, select NearStore.

NearStore server
The NearStore server drop-down list contains all NearStore hosts configured and authenticated for the selected media server and available to NetBackup.

Absolute pathname to volume

The Absolute pathname to volume drop-down list contains all the volumes in the selected NearStore that are capable of serving as NetBackup disk storage units. The list displays only FlexVol volumes. For example, WORM volumes are filtered out. Initially, every volume requires a full backup. All subsequent backups are incremental.

Properties button
Click the Properties button to display:

Volume capacity: The total capacity of the volumes on the NearStore unit. Available space: The storage currently available for use on the NearStore unit. % Full: The storage that is currently in use on the NearStore unit.

Enable block sharing and and file system export

How the data is stored differs depending on whether the Enable block sharing setting or the Enable file system export setting is selected. Each setting permits the storage unit to store data in one of three modes: the space optimized image mode, the file system export mode, or the image mode.

Enable block sharing

The Enable block sharing setting allows data blocks that have not changed from one backup to the next to be shared. Sharing data blocks can save disk space significantly in the storage unit. If only the Enable block sharing setting is enabled, the NearStore is using the space optimized image mode. The space optimized image mode makes use of single-instance store (SIS) without the additional requirement of managing

752 NearStore disk storage unit properties

snapshots. This mode is especially useful for database backups, since an exported file system of a database backup is not useful in that case.

Enable file system export

If both the Enable file system export and the Enable block sharing settings are enabled, the backups are created using the file system export mode. In the file system export mode, backups become user-mountable when exported as CIFS or NFS file systems. This means that a user mount the backup image with CIFS or NFS and simply copy the files using native tools (for example, Windows Explorer). Be sure to enable Collect true image restore information with move detection on policies that write to FSE-enabled NearStore disk storage units. This policy attribute must be enabled or the backups will fail.

Ramifications of using file system export

Backups that use the file system export mode use snapshots to tie images together. The space that is consumed by a snapshot is unavailable for reuse until every image in the snapshot expires and is deleted. Because of this behavior, configure policies so that the images in the NearStore storage unit do not become inter-related. For example, do not combine schedules with dissimilar backup frequencies or retention periods within the same policy. In this way, policy combinations that performed well for NetBackup 6.0 with ONTAP 7.1 may need adjusting after upgrading. Note: The 7.2 ONTAP kernel enforces a limit of 255 snapshots per volume and 200 volumes per NearStore.

Image mode
To select Enable temporary staging area (used for basic disk staging), both Enable block sharing and Enable file system export must not be selected. In this way, the NearStore is storing the backup using the image mode. Using this mode, the clients tar stream is passed to the NearStore without additional information. Since the ONTAP kernel cannot read NetBackups tar format, only basic NetBackup operations can be performed, not SIS.

Temporary staging area

To select Enable temporary staging area, both Enable block sharing and Enable file system export must be deselected. As previously stated, when the NearStore is in image mode, it acts much like a BasicDisk storage unit in how data is stored.

753 Viewing the backup image

Reduce fragment size

NearStore uses the Reduce fragment size setting differently than other storage units. NetBackup writes to a NearStore by laying out the data in one large image, and not dividing the data into fragments.

Viewing the backup image

Use the bpstsinfo command to look for images on the NearStore, as well as to look at server and logical storage unit (LSU) attributes. The bpstsinfo command is described in NetBackup Commands for UNIX and Linux. and in NetBackup Commands for Windows.

Disk consumption
Snapshot creation consumes a large amount of disk space. NetBackup prepares for this space requirement by reserving 20% of the disk space on the volume to be used exclusively for the snapshot, and not for the active file system. If the snapshots exceed the reserved amount, space is consumed as needed from the active file system. The active file system cannot, however, consume disk space reserved for snapshots.

File system full conditions

Whenever snapshots consume more than 100% of the reserved space, the active file system is in danger of becoming full. Under these conditions, backups fail until administrative action is taken. Administrative action could include:

Expiring images through NetBackup. This can be accomplished through the Catalog utility. Lowering the retention level for images so that images are expired sooner.

End of media detection on disk staging storage units

To permit End of Media detection on NearStore disk staging storage units, backup performance is diminished when a NearStore volume is within 4 gigabytes of being full.

754 Disk consumption

Using the NearStore disk storage unit for more than one purpose
The volume properties of the NearStore storage unit display a value for the storage available on the volume. A volume designated for NearStore storage should be used exclusively for NetBackup. (See NearStore disk storage units and SnapVault storage units cannot share volumes on page 744.)

755 Disaster recovery using volume SnapMirror on NearStore disk storage units

Disaster recovery using volume SnapMirror on NearStore disk storage units

NetBackup and NetApp volume SnapMirror technology can be used to provide a disaster recovery solution for NearStore disk storage units. The volume SnapMirror feature can be used to replicate a NearStore disk storage unit from one NearStore to a second NearStore to provide failover support in a disaster recovery situation. Note: Disaster recovery planning should always include NetBackup catalog backup and restore procedures. For information about catalog backups and restores in a disaster recover situation, see the NetBackup Troubleshooting Guide.

Overview of disaster recovery scenarios

The examples in this section are based on the following representative environment:

Two media servers back up to volumes on a NearStore disk storage unit (NearStoreA).

mediaserver1 backs up to volume1 on NearStoreA mediaserver2 backs up to volume2 on NearStoreA.

NearStoreA contains volumes that are replicated using SnapMirror, to NearStoreB.

756 Disaster recovery using volume SnapMirror on NearStore disk storage units

Figure C-2

Example NearStore configuration

Mediaserver1

Mediaserver2

Vol NearStoreA disk storage unit 1

Vol 2

NearStoreA fails over to NearStoreB

SnapMirror relationship

Vol 1

Vol NearStoreB 2 disk storage unit

There are two basic disaster recovery scenarios for the voulmes on NearStore A:

The volumes on NearStoreA are unrecoverable. If the volumes on NearStoreA have been destroyed and cannot be recovered, the SnapMirror relationship must be manually broken, making the replicated volumes on NearStoreB read- and write-enabled. For each replicated volume on each media server, an entry is added in the NetBackup bp.conf file (UNIX) or registry (Windows) that instructs NetBackup to redirect restores, verifications, and deletions to the replicated copy. The bpstsinfo command provides a check to identify any images that were not replicated before the failure. After the failover, storage units must be altered so that future backups go to volumes on the failover NearStore. The volumes on NearStoreA are recoverable. If the volumes have not been destroyed but were temporarily unavailable, all data backed up to NearStoreB, while NearStoreA was unavailable, can be transferred back to NearStoreA. NetBackup can then be reconfigured to direct restores, verifications, deletions, and backups to NearStoreA again.

Initial configuration
As in any NetBackup environment, configure NearStore storage units, create NetBackup backup policies, and configure catalog backups.

757 Disaster recovery using volume SnapMirror on NearStore disk storage units

On NearStoreB, configure a SnapMirror relationship for each volume to be replicated from NearStoreA. Configure a SnapMirror schedule with a relatively small time period to minimize any data mismatches between the source and destination in the case of a disaster. See the NetApp Online Backup and Recovery Guide for information on how to configure SnapMirror relationships and schedules.

General failover configuration

If NearStoreA becomes unavailable, break the SnapMirror relationship to use NearStoreB as the new NearStore disk storage unit. The following steps describe how to position NearStoreB so that it handles all future backups and restores. (Example 1 on page 758 and Example 2 on page 761 provide more specific details.) 1 2 Break the SnapMirror relationship between the volumes. Issue a snapmirror break command on the replicated volumes on NearStoreB. Allow NearStoreB to restore images that had been backed up to NearStoreA. Add an entry for each replicated volume:

On each UNIX media server: Add a NEARSTORE_FAILOVER_SERVER entry to the /usr/openv/netbackup/bp.conf file. On each Windows media server: Use the bpgetconfig command to obtain a list of configuration entries, then use bpsetconfig to add the NEARSTORE_FAILOVER_SERVER entry to the registry. If added correctly, the entry should appear in the following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\ ConcurrentVersion\Config

Use the bpstsinfo -comparedbandstu command to compare the contents of the NetBackup catalog with the list of images reported from the NearStore. Because the SnapMirror replication is performed asynchronously, there is a small chance that images may not have been fully replicated before the NearStoreA went down. bpstsinfo -comparedbandstu creates a list of images that the catalog thinks are on NearStoreA and compares that list to the images that NearStoreB reports it contains. Any image is listed that is not present both in the catalog and on NearStoreB. Also listed is the image location, whether the image is in the catalog only or on media only. The list identifies any discrepancy to the administrator so the appropriate action can be taken.

758 Disaster recovery using volume SnapMirror on NearStore disk storage units

4 5

For future backups to be successful, all NetBackup NearStore disk storage units must have the name NearStoreA changed to NearStoreB. If the catalog had been backed up to NearStoreB and the disaster necessitates a catalog recovery, see the NetBackup Troubleshooting Guide for more information. Note: Catalog backups to NearStore disk storage units are restricted to those that do not have the File System Export option enabled.

Failover examples
The examples in the following sections are based on the environment in the Figure C-2 on page 756.

Example 1
NearStoreA is unavailable, and NearStoreB is configured as the new NearStore disk storage unit. Figure C-3 NearStoreB as the new disk storage unit

Mediaserver1

Mediaserver2

Vol NearStoreA disk storage unit 1

Vol 2

Vol 1

Vol NearStoreB 2 disk storage unit

To enable NearStoreB, use the following steps: 1 Break the SnapMirror relationship between the volumes. Issue a snapmirror break command on the replicated volumes on NearStoreB.
NearStoreB> snapmirror break volume1 NearStoreB> snapmirror break volume2

Change the configuration for each volume that was being failed over.

On each UNIX media server:

759 Disaster recovery using volume SnapMirror on NearStore disk storage units

Add a NEARSTORE_FAILOVER_SERVER entry to the bp.conf file for each volume that was being failed over. The following entry is for mediaserver1:
NEARSTORE_FAILOVER_SERVER = NearStoreA:/vol/volume1 NearStoreB:/vol/volume1

The following entry is for mediaserver2:

NEARSTORE_FAILOVER_SERVER = NearStoreA:/vol/volume2 NearStoreB:/vol/volume2

On each Windows media server: Use the bpsetconfig to add the NEARSTORE_FAILOVER_SERVER entry to the registry (type Multi-String Value). If added correctly, the entry should appear in the following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\ ConcurrentVersion\Config

The following entry is for mediaserver1:

NearStoreA:/vol/volume1 NearStoreB:/vol/volume1

The following entry is for mediaserver2:

NearStoreA:/vol/volume2 NearStoreB:/vol/volume2

On each media server, run the bpstsinfo -comparedbandstu command. The command displays differences between the contents on the catalog, and contents on the disk storage unit. The following is the command for mediaserver1:
/usr/openv/netbackup/bin/admincmd/bpstsinfo -comparedbandstu -oldservervolume NearStoreA:/vol/volume1 -servername NearStoreB -serverprefix ntap: -lsuname /vol/volume1

The following is the command for mediaserver2:

/usr/openv/netbackup/bin/admincmd/bpstsinfo -comparedbandstu -oldservervolume NearStoreA:/vol/volume2 -servername NearStoreB -serverprefix ntap: -lsuname /vol/volume2

No discrepancies If no discrepancies exist between the images in the catalog and the images on the NearStore volume, no images are listed in the output. The output contains only debug logging:

STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12 10:48:37: opening module /usr/openv/lib/libstspibasicdiskMT.so STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12 10:48:38: opening module /usr/openv/lib/libstspinearstoreMT.so Nearstore disk subtype

With discrepancies The output contains additional information if mismatches are found. A mismatch can exist if, for example, one image did not get replicated to NearStoreB before NearStoreA went down.

STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12 10:39:37: opening module /usr/openv/lib/libstspibasicdiskMT.so

760 Disaster recovery using volume SnapMirror on NearStore disk storage units

Nearstore disk subtype ONLY IN CATALOG imagename:mediaserver1_1157990060 policy:powerpoint_backup copy_num:1 frag_num:0 is_header:TRUE resume_num:0 ONLY IN CATALOG imagename: mediaserver1_1157990060 policy: powerpoint_backup copy_num:1 frag_num:1 is_header:FALSE resume_num:0

Note: Two images are listed but they represent only one backup. There are separate files for the header and the actual backup data. If this backup had been enabled for True Image Restore, there would have been three images printed out. To tell if the images are part of the same backup, look at the imagename field. In the example, both listings have the same image name, which indicates that theyre part of the same backup. The entries for this image must be removed from the NetBackup catalog either by using the NetBackup Administration Console or by running bpexpdate. To remove the entry from the catalog using bpexpdate, enter:
/usr/openv/netbackup/bin/admincmd/bpexpdate -backupid mediaserver1_1157990060 -d 0

If the original volumes on NearStoreA are never expected to recover, manually delete the snapshot copies used by the SnapMirror transfer on volumes volume1 and volume2. (Do this if, for example, it is never expected that the volume will be SnapMirror resynced.) Issue snapmirror status l on the destination volume on NearStoreB: NearStoreB> snapmirror status l vsmtest1 The following is the output:
NearStoreB> snapmirror status -l volume1 Snapmirror is on. Source: Destination: Status: Progress: State: Lag: Mirror Timestamp: Base Snapshot: Current Transfer Type: Current Transfer Error: Contents: Last Transfer Type: Last Transfer Size: Last Transfer Duration: Last Transfer From: NearStoreA:volume1 NearStoreB:volume1 Idle Broken-off 00:05:28 Fri Sep 29 10:39:28 PDT 2006 NearStoreB(0101178726)_volume1.2 Replica Resync 72 KB 00:00:03 NearStoreA:volume1

Delete the base snapshot copy associated with the volume:

761 Disaster recovery using volume SnapMirror on NearStore disk storage units

NearStoreB> snap delete volume1 NearStoreB(0101178726)_volume1.2

Repeat this procedure for volume2 as well. 5 6 Remove any SnapMirror schedules added in the snapmirror.conf file for these volumes. Reconfigure the disk storage units that were originally configured to the volumes on NearStoreA. Point the disk storage units to the disk storage units on NearStoreB using the following command:
/usr/openv/netbackup/bin/admincmd/bpsturep -label <storage unit label> -nh NearStoreB

Example 2
NearStoreA is taken down for maintenance and NearStoreB is configured as the new NearStore disk storage unit. The administrator performs the steps outlined in Example 1 on page 758, to enable NearStoreB as the new temporary disk storage unit. When NearStoreA is back online the administrator wants to use it again as the disk storage unit. All data backed up to NearStoreB while NearStoreA was unavailable must be transferred to NearStoreA before re-enabling NearStoreA as the disk storage unit. Follow these steps to transfer data from NearStoreB to NearStoreA and use it as the disk storage unit for NetBackup: 1 Resync the volume(s) from NearStoreB back to NearStoreA.
NearStoreA> snapmirror resync -S NearStoreB:volume1 volume1 NearStoreA> snapmirror resync -S NearStoreB:volume2 volume2

Issue snapmirror release commands for both volumes on NearStoreA, as NearStoreA is no longer the replica source.
NearStoreA> snapmirror release volume1 NearStoreB:volume1 NearStoreA> snapmirror release volume2 NearStoreB:volume2

Delete the base snapshots on NearStoreB. The snapshots that were originally used by SnapMirror while transferring data from NearStoreA to NearStoreB are no longer needed. To delete the snapshots, see step 4 on page 760. Confirm that the relationships are intact by issuing SnapMirror updates on NearStoreA:
NearStoreA> snapmirror update -S NearStoreB:volume1 volume1 NearStoreA> snapmirror update -S NearStoreB:volume2 volume2

Break the replicated relationship on NearStoreA:

NearStoreA> snapmirror break volume1 NearStoreA> snapmirror break volume2

Resync the volumes from NearStoreA to NearStoreB.

762 Disaster recovery using volume SnapMirror on NearStore disk storage units

NearStoreB> snapmirror resync -S NearStoreA:volume1 volume1 NearStoreB> snapmirror resync -S NearStoreA:volume2 volume2

To resync the volumes may return a message similar to the following, and fail the resync operation:
The resync base snapshot will be: NearStoreA(0101179629)_volume1.4 These older snapshots have already been deleted from the source and will be deleted from the destination: NearStoreB(0101178726)_volume1.20699 NearStoreB(0101178726)_volume1.20698 Are you sure you want to resync the volume? y Wed Sep 27 12:30:24 PDT [snapmirror.dst.resync.success:notice]: SnapMirror resync of volume1 to NearStoreA:volume1 successful. Transfer started. Monitor progress with 'snapmirror status' or the snapmirror log. NearStoreB> Wed Sep 27 12:30:26 PDT [snapmirror.dst.snapDelErr:error]: Snapshot NearStoreB(0101178726)_volume1.20699 in destination volume volume1 is in use, cannot delete. Wed Sep 27 12:30:27 PDT [snapmirror.dst.err:error]: SnapMirror destination transfer from NearStoreA:volume1 to volume1 : snapmirror transfer failed to complete.

If such a case occurs, use the following steps to resolve this issue: a The SnapMirror resync operation replicated the volume, so break the replica by issuing a snapmirror break:
NearStoreB> snapmirror break volume1

Manually delete the snapshot copy in question:

NearStoreB> snap delete volume1 NearStoreB(0101178726)_volume1.20699

Retry the resync operation attempted in step 3 on page 749. You may need to repeat these steps until no more snapshot copies are causing problems with the resync operation. Issue snapmirror release commands for both volumes on NearStoreB, as NearStoreB is no longer the replica source. Delete the base snapshots on NearStoreA. The snapshots were originally used by SnapMirror while transferring data from NearStoreB to NearStoreA and are no longer needed. Confirm that the relationships are intact by issuing SnapMirror updates on NearStoreB.

Repeat steps 2 through 4, on NearStoreB:

Change the configuration for each volume to redirect access of backups made to NearStoreB to NearStoreA.

On each UNIX media server:

763 Disaster recovery using volume SnapMirror on NearStore disk storage units

Change the bp.conf entry for each volume to redirect access of backups made to NearStoreB to NearStoreA. (Any entries entered in the bp.conf file while following Example 2 on page 761, to redirect from NearStoreA to NearStoreB should be removed.) The following entry is for mediaserver1:
NEARSTORE_FAILOVER_SERVER = NearStoreB:/vol/volume1 NearStoreA:/vol/volume1

The following entry is for mediaserver2:

NEARSTORE_FAILOVER_SERVER = NearStoreB:/vol/volume2 NearStoreA:/vol/volume2

On each Windows media server: Use the bpsetconfig command to add the NEARSTORE_FAILOVER_SERVER entry to the registry (type Multi-String Value). If added correctly, the entry should appear in the following registry location:

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\ ConcurrentVersion\Config

The value for mediaserver1 is:

NearStoreB:/vol/volume1 NearStoreA:/vol/volume1

The value for mediaserver2 is:

NearStoreB:/vol/volume2 NearStoreA:/vol/volume2

Reconfigure the disk storage units that were originally configured to the volumes on NearStoreB. Point the disk storage units to the disk storage units on NearStoreA using the following command:
/usr/openv/netbackup/bin/admincmd/bpsturep -label <storage unit label> -nh NearStoreA

764 Troubleshooting

Troubleshooting
Logs can be found in the following locations:

By default (if not creating multiple copies): /usr/openv/netbackup/logs/bpdm If creating multiple copies: /usr/openv/netbackup/logs/bptm

All other logging is similar to a standard backup, producing, for example, progress logs. Logs contain more information about the interaction with NearStore. On the NearStore, the root volume contains a NetBackup-specific log file that details the protocol between NetBackup and the NearStore. ONTAP debug logs are found in the following location: /vol/vol0/etc/logs/nbu_snapvault

Licensing and permissions

Make sure that the permissions on the disk storage unit are set so that data can be written to the volume. If permissions are Read Only, NetBackup cannot write to it. Make sure that the SnapVault license has been added and is turned on. Make sure the tpconfig command is used to add the NearStore user ID and password into the EMM global database. For more information, see To authenticate the NetBackup media server on page 747. If the maximum number of transfers allowed to a single NearStore is exceeded, the ONTAP kernel reports the following error: inf Wed Jul 6 07:28:27 CDT [10.80.106.36:58645] Maximum active transfers reached.

The maximum number of concurrent backup and/or restore connections is 128.

Regarding disk full conditions

If jobs are failing to write to the NearStore, make sure that the space reserved for snapshots on the NearStore is not completely full. When the reserved space is full, NetBackup uses the active file system space as needed. In the case of a disk full condition on the NearStore, make sure that there are no WAFL snapshots consuming disk space unnecessarily.

765 Troubleshooting

Regarding the file system export mode

Snapshots are used to ensure the integrity of the exported file system. A snapshot is made up of one or more images in a group. Before a snapshot can be reclaimed (or deleted), all the images it contains must be deleted. The snapshots must be deleted to keep the NearStore file system synchronized with the last NetBackup catalog image.

Use bpstsinfo -imagegrouplist to determine what image groups are contained within a snapshot. Use bpstsinfo -deleteimage to delete the images within the a snapshot.

A File System Export-enabled NearStore storage unit may generate a return code of 1 (partially successful) even if all the data was backed up successfully. This may occur if the last backup to that client and policy pair did not generate a return code of 0 due to incorrect True Image Restore information. In the Activity Monitor, the Job Details for the job note that additional files may have been exported on the NearStore that were not in the most recent client backup:
9/27/2006 5:20:34 PM - Error bpdm(pid=2328) The backup was successful but the exported filesystem on the storage host gabe may display files that are no longer present on the client filesystem. (STS_EEFSCHK) 9/27/2006 5:20:38 PM - Warning bpbrm(pid=2412) The filesystem exposed by the nearstore DSU may not be up to date. Check the Nearstore's nbu_snapvault log for details

766 Troubleshooting

Appendix

Exporting PureDisk data to NetBackup

NetBackup allows the export of PureDisk backups of Files and Folders data selections to NetBackup. NetBackup can then create copies of the data in NetBackup file format on NetBackup-supported media for possible disaster recovery purposes.

Required software and licenses

To allow PureDisk backup data to be exported to NetBackup, the following software and licenses must be installed.

In the PureDisk environment

To export data selections from the PureDisk environment, the following software is required:

PureDisk 6.1 MP1 (or later) on one or more nodes. This version contains the NetBackup export engine (nbu service). See the Veritas NetBackup PureDisk Remote Office Edition Administrators Guide for complete information on PureDisk hardware and software requirements.

Run add_NBU_onNode.sh to add the new NetBackup export engine. See Configuring the PureDisk node in the PureDisk Administrators Guide. If NetBackup was in the topology file when install_newStoragePool.sh was run, it is not necessary to run add_NBU_onNode.sh. Enable the export engine by selecting Activate NetBackup export engine in the Topology tab. See Activating a new component or service in the PureDisk Administrators Guide.

768

NetBackup 6.0 MP5 client software.

In the NetBackup environment

The NetBackup master and media server(s) where the PureDisk data is to be exported must contain NetBackup Enterprise 6.5 server software.

NetBackup 6.5 or 6.0 MP5 server software. The NetBackup DataStore license to provide the DataStore policy type selection.

Requirements to restore
To restore data selections from NetBackup, the following software is required:

NetBackup 6.0 MP5 client software NetBackup 6.5 or 6.0 MP5 server software.

Exporting PureDisk data

To export PureDisk backup data to NetBackup requires the creation of two active policies:

An export policy in PureDisk. A DataStore type policy in NetBackup.

The policies can be created in any order. The export takes place when the PureDisk policy runs.

Create a PureDisk export policy

See the Veritas NetBackup PureDisk Remote Office Edition Administrators Guide, version 6.1.2, for information on creating an export policy. As part of the policy creation, note that a NetBackup policy name is entered on the Parameters tab in the export policy. This is the NetBackup DataStore type policy configured for the PureDisk export. See Create a NetBackup DataStore type policy on page 769.

Enter the name of the DataStore policy (see step 3 below)

769

If no NetBackup policy name is entered, NetBackup tries to determine which policy to use. The PureDisk policy determines when the export runs. The NetBackup policy must be set up for the export to work.

Create a NetBackup DataStore type policy

Create a DataStore type policy in the NetBackup Administration Console. To configure a NetBackup policy for a PureDisk backup data export 1 2 3 4 Open the NetBackup Administration Console. Select the master server that controls the media server that will perform the export. Select the Policies utility, then Actions > New > New Policy. The Add a New Policy dialog appears. Enter a name for the policy. This name is entered in the Parameters tab in the PureDisk export policy. Complete the tabs in the Add New Policy dialog.

Attributes tab
Select the DataStore policy type

The policy must be active for the export to work

Select DataStore as the policy type. (The DataStore policy type selection appears if the DataStore license key is installed.) The compression and multiple data streams attributes are not supported for export because they are not supported upon restore. To run multiple streams, multiple export agents are required.

Schedules tab

770

By default, a DataStore policy type uses an Application Backup schedule. The start window for an Application Backup type is open every day for 24 hours. Note: The default schedule can be adjusted or a new schedule can be created, but the start windows must coincide with the PureDisk Export policy start window.

Clients tab

In the Clients tab, add the name of the PureDisk export agent(s). (Multiple PureDisk export agents can indicate the same NetBackup DataStore policy. Add the export agents in the Clients tab as needed.) Do not include the name of the originating PureDisk clients.

Backup Selections tab No entries are required on the Backup Selections tab.

Save and close the policy.

Restoring PureDisk data

Use the NetBackup client interface, Backup, Archive, and Restore, to restore the PureDisk export data to a PureDisk export agent. The system to which the data selections are restored must contain the NetBackup 6.0 MP5 client software and the NetBackup engineering binary to support the export engine. After the data is restored to the export agent, use a network transfer method to move the files to individual PureDisk clients. To restore PureDisk export data 1 2 3 Open the NetBackup Backup, Archive, and Restore interface on the export agent. Select File > Specify NetBackup Machines and Policy Types. In the Specify NetBackup Machines and Policy Types dialog, select the PureDisk-Export policy type to display the export data available for restore.

771

Although the NetBackup job runs as a DataStore policy type, the job is cataloged as a PureDisk-Export policy type under the name of the PureDisk agent.
Select the NetBackup server where the PureDisk backup data was exported to.

Select the PureDisk agent where the data was exported from. To restore the data, the agent must contain NetBackup client software.

Select PureDisk-Export as the policy type

4 5

Select a backup to restore from the NetBackup History. Restore the files to the selected client as you would restore from a user-directed backup.

Restore support
NetBackup can restore only what PureDisk supports as part of its backups. For example, PureDisk does not provide access control list (ACL) support beyond UNIX file or directory permissions, so NetBackup cannot restore ACLs. See the PureDisk documentation for complete details. Additional comments on restores:

While Windows and UNIX security information can be restored, one limitation exists regarding restores to an alternate client for UNIX files: NetBackup backs up both the user ID and user name, but PureDisk backs up only the user ID. In non-PureDisk export backups, during a restore to an alternate client, a user name can map to a different user ID. NetBackup performs a search for the user name and changes the user ID appropriately. For PureDisk export backups this ability is lost, since the user name is not available. Files that are restored could belong to a different user. Windows files can be restored to UNIX systems and UNIX files can be restored to Windows systems. However, security information is lost when restoring Windows file to UNIX.

772

Logging information
Standard debugging techniques apply to both PureDisk and NetBackup portion. The VxBSA debug log is written to the pdexport directory.

Index

Symbols
.ds files 226 .f files in catalog 278 .SeCuRiTy.nnnn files 681

A
Absolute pathname to directory/volume storage unit setting 228 to volume storage unit setting 751 Accept connections on non reserved ports property 480 Access Control authorizing users 651 host properties Authentication domain tab 368 Authorization service tab 371 Networks list 366 Symantec Product authentication and authorization 365 NetBackup 654 access control lists (ACLs) 177, 681 Activity Monitor bpdbjobs command 70 BPDBJOBS_OPTIONS environmental variable 69 canceling uncompleted jobs 52 deleting completed jobs 52 detailed job status 51, 61 disabling job logging 450 killing jobs 52 monitoring jobs 51 restarting a completed job 52 resuming suspended jobs 52 saving job data to a file 53 set column heads to view 51 suspending a job 52 using the Troubleshooter 53 Actual client property (Backup Exec Tape Reader) 376 Actual path property (Backup Exec Tape Reader) 376

Adaptive Server Anywhere (NB_dbsrv) 58 administering remote systems 645 administrator e-mail address property 78, 438 nonroot 658 AdvancedDisk disk storage units 223 AFS policy type 90 All log entries report 76, 383, 384 ALL_LOCAL_DRIVES directive 186 Allow backups to span tape media property 449 Allow client browse property 386 restore property 386 Allow media overwrite property 446 Allow multiple data streams directives 189 set policy attribute 112 when to use 113 Allow multiple retentions per media property 140, 449 Allow server file writes property 364, 480 Alternate restore failover machines host properties 460 Always property in Fibre Transport host properties 423 Announce DHCP interval property 455 ANSI format, allow overwrite 446 AOS/VS format, allow overwrite 446 API robots 527, 555, 566 application backups 121 archive bit 120, 202, 403, 405 assigned volumes 533 assigning tape requests 499 atime 682, 694 auth.conf file capabilities identifiers 659 description 656 entries for specific applications 658 overview 655 Authentication NetBackup Access Control 45 service 61

774

Authorization host properties DomainGroup 374 Group/Domain 374 Host 374 User 373 User must be an OS administrator 374 NetBackup Access Control 45 preferred group 479 Service 61 auto-discovery streaming mode 191 Automated Cartridge System drive information 614 automatic backups 121 cumulative incremental backups 121 differential incremental backups 121 full backups 121 Vault policy type 122 Volume Recognition service (avrd) 62 automounted directories 102 avrd (Automatic Volume Recognition process) 62

B
backlevel administration consoles 38 Backup end notify timeout property 476 Backup Exec QIC media 343 Backup Exec Tape Reader host properties Actual client 376 Actual path 376 GRFS advertised name 375 Backup migrated files property 396 Backup start notify timeout property 474 Backup status report 383, 384 backups activating policy 99 application 121 archive 120 automatic 121 cumulative incremental 120, 121 differential incremental 120, 121 full 121 Vault 122 Client backups report 76 clients using Storage Migrator 694 deactivating policy 99 duplicating 330

frequency effect on priority 130 guidelines for setting 129 setting 129 full 119 importing 336 network drives 100 NFS mounted files 87, 101 off-site storage 139 policy management window 82 raw partitions on Windows 96, 171 registry on Windows clients 172 selections list, verifying 167 Status of Backups report 76 types of 119 user directed schedules 151 type of backup 120 verifying 327 windows duration, examples 144 specifying 143 Bandwidth host properties Bandwidth 378 Bandwidth throttle setting for the range of IP addresses 378 Bandwith 378 Bandwith throttle settings list 378 From IP address 378 To IP address 378 barcodes 523, 562, 563 Bare Metal Restore (BMR) 56, 58, 108, 280, 405, 697 Bare Metal Restore daemon 62 basic disk staging and NearStore disk storage units 747 creating a storage unit 247 Final destination media owner 250 Final destination storage unit 250 Final destination volume pool 250 priority of duplication jobs 135 relocation schedule 119, 239, 249 schedule 249 storage units selection within a storage unit group 273 size recommendations 245 using checkpoint restart 96 Use alternate read server 135 Use alternate read server attribute 135, 251

775

BasicDisk storage units 223, 259 BE-MTF1 format, allow overwrite 447 Block level incremental backups 96 BMR database 280 BMRD (Bare Metal Restore process) 62 BMRD (NetBackup Bare Metal Restore Master Server) 58 BMRDB.db configuration entry 704 in catalog 280 relocating 699 bp.conf file configuring to use ctime 126 customizing jnbSA and jbpSA 666 entries for Activity Monitor 68 indicating database location 698 NetBackup-Java Administration Console configuration entries 660 obtaining list of entries 361 when master servers share EMM databse 467 BPARCHIVE_POLICY 152 BPARCHIVE_SCHED 152 bpbackup command 351 BPBACKUP_POLICY 152 BPBACKUP_SCHED 152 bpbackupdb command 351 BPBRM logging property 443 bpcatarc command 322 bpcatlist command 321 bpcatres command 322 bpcatrm command 322 BPCD connect-back property 425, 427 bpcd daemon 62 BPCD port setting on client 454 bpchangeprimary command 328 BPCOMPATD (NetBackup Compatibility Service) 59 bpcompatd process 62 bpconfig command 192 bpdbjobs adding entries to bp.conf file 68 command 70 debug log 70 BPDBJOBS_OPTIONS environmental variable 69 BPDBM NetBackup Database Manager, description 59 BPDBM logging property 443 bpdbm process 62 BPDM logging property 443 bpend 476

bpexpdate command 333, 534 bpfis directory for VSP logging messages 487 bpgetconfig command 361 BPINETD (NetBackup Client Service) 58 BPJAVA_PORT 660 bpjava-msvc service 63 bpjava-susvc service 63 bpjobd process 63 bpps script 634 BPRD logging property 443 NetBackup Request Manager, description 59 port setting on client 454 process 63 bpsetconfig command 361 bpstart 474 bpsynth log 210 BPTM logging property 443 Browse and restore ability property 388 buffer size 406 Busy action property 382 Busy file host properties Busy file action 382 File action file list 381 Operators email Address 381 Process busy files 381 Retry count 382 Working directory 381

C
cachefs file systems, excluding from backup 195 calendar scheduling how it interacts with daily windows 149 using 146 canceling uncompleted jobs 52 capacity-based licenses 635 catalog archiving bpcatarc command 322 bpcatlist command 321 bpcatres command 322 bpcatrm command 322 deactiving policy for 99 catalog backups archiving 318 bpcatarc 322 bpcatlist 321 bpcatres 322 bpcatrm 322

776

catarc policy 319 deactivate policy 319 extracting images 323 overview 318 retention level setting 320 type of backup indicated 320 compressing image catalog 355 configuration 296 disk path 310 file paths media server 315 Windows master 314 image files 278 last media used 307 manual backup 350 media ID 309 server 307 type 308 moving client images 354 multiple file layout 278 offline, cold method 56 online, hot method 283 parent and child jobs 56 schedules for 92, 232, 287, 294, 437 volume pool 93 overview 276 policy type 196 setting schedules 311 single file layout 278 space required 347 uncompressing 357 Catalogbackup volume pool 93 catarc schedule 83 CDE (Common Desktop Environment) 35 cdrom file system, excluding from backup 195 change journal 404 and synthetic backups 210 determining if enabling is useful 403 using in incremental backups 403 changing media description 518 robot configuration 620 volume expiration date 518 volume group name 520, 521 volume pool attributes 539 volume pool for a volume 519 volume properties 517 character device 608

Check the capacity of disk storage units property 226, 431 checkpoint restart and synthetic backups 210 Move job from incomplete state to done state property 385 Move Restore Job from Incomplete Sate to Done State 683 restore retries 683 resuming a restore job 683 suspending a restore job 683 cipher types for NetBackup encryption 410 cleaning drives 502 frequency 607 tape change cleanings allowed 519 set count 514 Clean-up host properties Catalog cleanup wait time 384 Image cleanup 384 Keep logs 383 Keep true image restoration information 384 Keep vault logs 383 Move backup job from incomplete state to done state 96, 385 Move job from incomplete state to done state 385 Client administrators e-mail property 481 Client attributes host properties Allow client browse 386 Allow client restore 386 Browse and restore ability 388 Clients list 387 Free browse 388 Maximum data streams 387 Client backups report 76 Client cipher property 410 Client connect timeout property 474 Client name property 395 Client port window property 457 Client read timeout property 397, 475 Client reserved port window property 457 Client sends mail setting 481 clients BPCD port 454

777

BPRD port 454 choosing policy type 88 database 387 deleting from policy 86 DHCP interval property 455 exclude and include lists 419 exclude file list 195, 414 installing 160, 162 list property 387 maximum jobs 436 moving image catalog 354 name 673 peername 673 secure 162 setting host names 159 trusting clients 160 clustering 362, 706 cold catalog backups (see catalog backups) Collect disaster recovery information for Bare Metal Restore 108 Collect true image restoration (TIR) with move detection property 202 collecting disaster recovery information 103, 108 column heads, selecting to view 51 Communications buffer size property 406 Compress catalog interval property 356, 438 compression, by software advantages 106 disadvantages 106 specifications 106 concurrent jobs on client 436 per policy 97 configuring drives and robots 595 media 508 storage devices 595 CONNECT_OPTIONS 427 Consistency check before backup host property 471 control path, robotic 601 copies, third-party 333 Copy on write snapshots 172 copy, primary 333 cpio format, allow overwrite 446 create media ID generation rules 555 critical policies, identifying 197 cross mount points effect with UNIX raw partitions 103 examples 104

interaction with Follow NFS policy attribute 104 policy attribute 179 separate policies for 104 setting 103 ctime 182 cumulative incremental backups 120, 123, 405

D
Daemon connection port property 426, 427 Daemon port only property (for selection of ports) 428 daemons check with vmps 635 checking processes 634 tlmd 65 tshd 65 vmscd 60 Daily windows setting 149 data deduplication 106, 108 movers 222, 224 streams 189 Data Classifications in storage lifecycle policies 253, 262, 263 selection in policy 90, 91, 137 database manager process (bpdbm) 62 database-extension clients, adding file paths for 185 databases, NetBackup (see catalog backups) DataStore policy type 89 volume pool 93 datetime stamp 125 DB2 policy type 89, 122 DBR format, allow overwrite 446 deassign volumes 533 Default cache device path for Snapshots property 400 Default mount point property 470 DEFAULT_CONNECT_OPTIONS 424 Delay on multiplexed restores property 431 deleting drive 621 storage unit groups 273 storage units 218, 219 volume group 544 volume pools 542 volumes 532

778

Density storage unit setting 229 denying requests 501 description, for new volume 515 detailed job status 51, 61 device character 608 configuration wizard 596, 605, 620 discovery 596 file permission 624 file, robotic 601 mapping file 594 no rewind 614 volume header 611 Device Configuration Wizard 217 device host for move volume 526 for new volume 513 Device Monitor 67 add drive comment 504 assigning requests 499 display pending requests 497 resubmit request 501 devpts file system, excluding from backup 195 DHCP setting on client 455 differential incremental backups 120, 405 Direct Access Recovery (DAR) 432 Directory can exist on the root file system or system disk setting 228 DISABLE_STANDALONE_DRIVE_EXTENSIONS 50 9 disaster recovery collect information for 103, 108 file, sending 197, 289, 317 information 438 sending e-mails 197, 289, 317 tab 196 disk consumption 753 logs report 79 pool status report 80 pools 222 spanning 92, 271, 450 staging storage units selection within a storage unit group 269 storage model 222 storage unit status report 79 storage units 240 Disk pool storage unit setting 229 Disk type storage unit setting 229, 728, 751

disk-image backups 96, 171 Do not compress files ending with property 401 DO_NOT_RESET_FILE_ACCESS_TIME 695 document-level restores 115, 432 down a device 501 drive access permission 624 add comment 504 adding 604 changing operating mode 495 character device 608 cleaning 502, 503, 607 configuration, changing 620 drive status 608 no rewind device 614 performing diagnostics 622 robot drive number 610 robot library, controlling drive 610 servicing requests 498 TLH information 614 TLM information 614 type 609 volume header device 611 duplicate backups becoming a primary copy 332 creating 330 restoring from 328 duration of backup window, examples 144

E
E-mail address for administrator of this client 481 disaster recovery 197 send from client 481 send from server 481 EMM database 281 empty media access port prior to update 550 Enable block sharing storage unit setting 229, 751 Enable document restore attribute 115 Enable encryption property 410 Enable file system export storage unit setting 752 Enable job logging property 450 Enable multiplexing storage unit setting 230 Enable Open file backup during backups property 455 Enable performance data collection property 481 Enable SCSI reserve property 447 Enable single instance backup for message attachments property 413

779

Enable standalone drive extensions property 450 Enable standard encryption property 410 Encryption host properties Client cipher 410 Enable encryption 410 Enable standard encryption 410 Encryption key file 411 Encryption libraries 411 Encryption permissions 409 Encryption strength 410 UselLegacy DES encryption 410 use with synthetic backups 208 Enterprise Disk Options 222 Enterprise Media Manager (EMM) 59, 220, 280, 281, 434, 466, 687, 688, 689, 690, 691, 697 erasing media 528 errors, media mount 67 escape character on UNIX 633 Exceptions to the exclude list host property 414 Exchange host properties Enable single instance backup for message attachments 413 Mailbox for message level backup and restore 413 exclude dates from schedule 145 files and directories from backup 414 exclude files list on client 419 overview 195 Windows example 419 Exclude list host properties Exceptions to the exclude list 414 Use case sensitive exclude list 414 Expire after duplication retention type for storage lifecycle policy 262 expired media 541 export host properties 361 license key 637 extended attribute files disabling the restore of 183 Solaris 9 177 external_types.txt 710

F
fail all copies, multiple copies 134 failover media server to alternate media server(s) 459 storage unit selection in group 267 Fibre Transport host properties Always 423 Maximum concurrent fibre transport connections 423 Never 423 Preferred 422 Use defaults from the master server configuration 423 File browse timeout property 475 File change log, using in VxFS 398 file lists disk image on Windows 171 extension clients 185 links on UNIX 178 NetWare clients nontarget 183 target 185 raw partitions 171, 178 standard clients 176 UNIX files not backed up 171, 176, 194 Windows clients 170 File system backup coverage report 167 file systems 103 files .SeCuRiTy.nnnn 681 /.rhosts 160 catalog space requirements 347 excluding from backup 414 for catalog backup 312 goodies scripts 687 linked, UNIX 177 NFS mounted 87, 101 No.restrictions 674 NOTES.INI 445 peername 675 redirected restores 676 restrictions on restores 673 filters, applying 51 Final destination media owner 250 storage unit 250 volume pool 250 Firewalls

780

host properties BPCD connect-back 427 Daemon connection port 426, 427 Default connect options 425 Hosts list 426 Ports 425, 427 using vnetd with 425, 427 first slot number add volumes 513 for move volumes 527 fixed retention type for storage lifecycle policy 260 FlashBackup 90, 177, 179 Flexible Disk Option 223, 224, 229, 253 Follow NFS 179 Follow NFS mounts notes on use with cross mount points 102 with raw partitions 102 Follow NFS setting 101, 102, 104 FORCE_IPADDR_LOOKUP 662 Free browse property 388 From IP address property 378 full backups 119, 121, 203

goodies directory 687 GRFS advertised name property 375

H
hard links NTFS volumes 173 UNIX directories 178 High water mark storage unit setting 230 HKEYS, backing up 173 host deactivate 625 device 32 properties changing in a clustered environment 362 exporting 361 permission to change 364 hot catalog backups (see catalog backups)

I
IBM device number 614 images changing primary copy 328 duplicating 330 expiring with bpexpdate 534 moving client catalog 354 on disk report 79 on media report 76 on tape report 77 restoring from duplicate 328 verifying 327 importing backups 336 include files list 195 list, on client 419 Incrementals based on archive bit property 405 timestamp property 405 inetd client process 62 Informix policy type 90 INI file, for Lotus Notes 445 Initial browse search limit property 478 INITIAL_BROWSE_SEARCH_LIMIT 666 INITIAL_MEMORY 663, 668 inject volume into robot multiple volumes 550 robot inventory 530 Inline copy option 131, 330, 333, 334 installing client software

G
General level logging property 402 General server host properties Check the capacity of disk storage units 226, 431 Delay on multiplexed restores 431 Document-level restore options 432 Media host override 433 Must use local drive 432 Use direct access recovery for NDMP restores 432 Global attributes host properties Administrators e-mail address 438 Compress catalog interval 438 Job retry delay 435 Maximum backup copies 437 Maximum jobs per client 151, 436 Policy update interval 436 Priority of restore jobs 436 Schedule backup attempts 435 global device database host conflict 596 Global logging level property 443

781

on PC clients 162 on secure clients 162 on trusting clients 160 Instant Recovery Advanced backup method 96 Backups to disk only setting 131 Intelligent Disaster Recovery (IDR) 103, 108 Internet Assigned Numbers Authority (IANA) 456, 660 inventory and compare robot contents 549

L
label media tapes 510 new media 521 optical media 556 library sharing 603 license keys accessing 635 deleting 637 export 637 printing 636 using the NetBackup License Key utility 638 viewing the properties of one key 637 LIFECYCLE_PARAMETERS file 264 Limit jobs per policy setting 97, 151 links UNIX hard-linked directories 178 UNIX symbolic 177 Load Balance storage unit selection in group 267 Locked file action property 397 logging bpsynth 210 deleting after a set time 383, 384 enabled for debug 443 legacy 442 unified 441 logical storage unit (LSU) attributes 753 long erase 529 Lotus Notes host properties INI file 445 Path 445 policy type 89 properties 445 Low water mark storage unit setting 228, 230 ltid (NetBackup Device Manager) 59, 63

J
Java auth.conf file 656 authorizing users 655 directory 657 interface 34 jbp.conf file 666 jbpSA configuration options 666 jnb.conf file 666 jnbSA configuration options 666 performance improvment hints 668 Virtual Machine (JVM) 663 jnbSA 34, 35, 61, 652 Job Manager logging property 444 Job retry delay property 435 jobs Concurrent per disk storage unit 231 filters, specifying 51 maximum per client 436 per policy 97 priority for policy 98 viewing in the Activity Monitor 56 JVM (Java Virtual Machine) 663

K
Keep logs property 74, 383, 384 Keep status of user-directed backups, archives, and restores property 396, 397, 406 Keep true image restoration information property 384 Keep vault logs property 383 KEEP_LOGS_DAYS 666 keyword phrase 116 killing jobs 52

M
Mac OS X 89 mail notifications administrator E-mail address 481 Disaster Recovery attachment, sending 197 email address for administrator 438 Windows nbmail.cmd script 438 Mailbox for message level backup and restore property 413 manual backups NetBackup catalogs 350

782

policy for 200 mapping file (external_types.txt) 710 master servers, rebooting 634 MAX_KB_SIZE_PER_DUPLICATION_JOB 264 MAX_MEMORY 663, 668 MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATIO N_JOB 264 maximum backup copies property 437 concurrent FT connections property 423 concurrent jobs storage unit setting 231 concurrent write drives storage unit setting 131, 231 data streams property 387 error messages for server property 406 jobs per client 436 jobs per policy 97 mounts add volume 514 streams per drive storage unit setting 233 vault jobs property 438 media 1 and media 2, catalog backup 308 active 78 freeze 520 host override property 433 host properties Allow backups to span disk 450 Allow backups to span tape media 449 Allow media overwrite 446 Allow multiple retentions per media 449 Enable job logging 450 Enable SCSI reserve/release 447, 448 Enable standalone drive extensions 450 Media ID prefix (non-robotic) 451 Media request delay 451 Media unmount delay 451 ID for catalog backup 309 ID prefix (non-robotic) property 451 last used for catalog backup 307 log entries report 77, 383, 384 mount errors, canceled 67 errors, queued 67 timeout for Storage Migrator 694 mount timeout property 475 nonactive 78 pools (see volume pools) recycling 537

replacing 535 request delay property 451 server connect timeout property 476 suspend 521 type for catalog backup 308 type for new volume 515 type when not an API robot 556 unfreeze 520 unmount delay property 451 unsuspend 521 media ID generation rules 566 prefix for update robot 560 Media server copy advanced backup method 96 Media server storage unit setting 233, 729 media servers adding a media server to the Alternate restore failover machine list 460 rebooting 634 registering with the EMM server 649 Restore failover host properties 459 Megabytes of memory property 398 MEM_USE_WARNING 664 Microsoft Volume Shadow Copy Service (VSS) 392 MIN_KB_SIZE_PER_DUPLICATION_JOB 264 mntfs file system, excluding from backup 195 monitoring NetBackup processes 66 monthly backups, scheduling 148 mount points 103 requests, pending 497 move backup job from incomplete state to done state property 96, 385 detection 109 job from incomplete state to done state property 385 Restore Job from Incomplete State to Done State 683 restore job from incomplete state to done state property 385 volume group 542 volumes logical move 524 overview 524 physical move 524 update volume configuration 525 MS SharePoint Portal Server 2003 115 MS-Exchange policy type 89

783

MS-SharePoint policy type 90 MS-SQL-Server policy type 89 MS-Windows-NT policy type 89 MTF format, allow overwrite 447 mtime 182 multiple copies fail all copies 134 parent and child jobs 57 setting 131 using checkpoint restart 95 multiple data streams 189 allowing 113, 114 parent and child jobs 57 tuning 114 multiple file layout for NetBackup catalogs 278 multiplexing (MPX) and synthetic backups 206 set for schedule 141 use with Enable block sharing 230 multistreaming and synthetic backups 206 Must use local drive property 432

N
named data streams, disabling the restore of 183 naming conventions 631 nb_updatedssu script 226 NBDB.db configuration entry 704 in catalog 280 installation overview 698 relocating 699 NBEMM (NetBackup Enterprise Media Manager) 59, 63 nbemmcmd command 469 nbEvtMgr process 63 nbftsrvr process 63 nbj.conf 660 NBJAVA_CLIENT_PORT_WINDOW 664 NBJAVA_CONNECT_OPTION 665 NBJAVA_CORBA_DEFAULT_TIMEOUT 665 NBJAVA_CORBA_LONG_TIMEOUT 665 NBJM (NetBackup Job Manager) 64, 444 nbmail.cmd script 438 NBPEM (NetBackup Policy Execution Manager) 59, 64, 444 nbproxy process 64 NBRB (NetBackup Resource Broker) 59, 444 nbrb process 64 NBRMMS (NetBackup Remote Management and

Monitor Service) 59, 64 NBSL (NetBackup Service Layer) 60 nbsl process 64 nbstlutil (lifecycle utility) command 265 nbstserv process 64 nbsvcmon process 64 NBU-Catalog policy type 196 NBVAULT (NetBackup Vault Manager) 60, 64 NCR-Teradata policy type 89 NDMP Direct Access Recovery for restores 432 drives 432 global credentials 452 host storage unit setting 235 hosts 452, 595 policy type 89 storage 333 storage units 227, 240 NearStore disk storage units 223, 235, 273 server storage unit setting 751 storage units 744 authenticating media servers 747 disk consumption 753 properties 750 SnapVault schedules 744 storage units disk type 746 NetBackup client service 454 request service port (BPRD) 454 volume pools 542 NetBackup Access Control (NBAC) authorizing NetBackup-Java users 654 use of 479, 666 NetBackup Client Service (BPINETD) 58 NetBackup Compatibility Service (BPCOMPATD) 59 NetBackup Database Manager (BPDBM) 59 NetBackup Device Manager (ltid) 59 NetBackup for MS-Exchange 185 NetBackup Job Manager (NBJM) 59, 444 NetBackup Monitor Service 60 NetBackup Operations Manager (NOM) 60 NetBackup Policy Execution Manager (NBPEM) 59, 444 NetBackup Remote Management and Monitor Service (NBRMMS) 59 NetBackup Request Manager (BPRD) 59 NetBackup Request Service Port (BPRD) property 454

784

NetBackup Resource Broker (NBRB) 59, 444 NetBackup Service Layer (NBSL) 60, 63 NetBackup Storage Lifecycle Manager 60 NetBackup support Web site 594 NetBackup Vault Manager (NBVAULT) 60 NetBackup Volume Manager (VMD) 60 NetBackup volume pool 93 NETBACKUP_RELATIONAL_DATABASE_FILES directive 300, 312 NetBackup-Java, set up for 35 NetWare client host properties Back up migrated files 396 Keep status of user-directed backups, archives, and restores 396 Uncompress files before backing up 396 target and nontarget 414 NetWare policy type 89 network drives, backing up 100 host properties Announce DHCP interval 455 NetBackup client service port (BPCD) 454 NetBackup request service port (BPRD) 454 Network Appliance (NetApp) 741 Network Attached Storage (NAS) 224, 227 Never property in Fibre Transport host properties 423 NEW_STREAM, file list directive 189 NFS (Network File System) Follow NFS policy attribute 101, 102, 104 NFS access timeout property 483 no disk spanning 450 no rewind device 614 NOM (NetBackup Operations Manager) 60 non reserved ports 480 nonactive media 78 none of the files in the file list exist (NetBackup status message) 163 None volume pool 93 nonroot administration for specific applications 658

OpenStorage disk storage unit 223, 723 operating mode of drive, changing 495 Operators email address property 381 optical devices 132, 333 volumes 514, 515, 528 Oracle policy type 89 Override policy storage selection setting 137 volume pool setting 137 Overwrite existing files 182

P
parent jobs 56, 112 in Activity Monitor Jobs tab 56 Limit jobs per policy setting 97 parent_end_notify script 56 parent_start_notify script 56 parent_end_notify script 56 parent_start_notify script 56 partially-configured devices 596 path separators 228 setting (Lotus Notes) 445 pathname catalog backup to disk 310 rules for policy file list 170 PBX (Symantec Private Branch Exchange) 66 PC NetLink files 177 peername files 675 of client 673 pending actions notation 498, 500 overview 498, 500 resolving 500 Perform default search for restore property 406 incrementals based on archive bit 125 permissions for device access 624 to change NetBackup properties 364 physical inventory utility 572 policies activating 99 changing properties 83, 84, 85, 86 configuration wizard 82 creating policy for Vault 199 deactivating 99

O
obsoletion date 694 On demand only storage unit setting 235, 271, 750 Open file backup properties 455 OpenStorage Disk Option 223, 229, 253, 742

785

example 153 overview 81 planning 154 setting priority 98 user schedules 151 volume pool setting 93 Policy Execution Manager Logging property 444 Policy storage policy attribute 91, 293, 295 policy type AFS 90 DataStore 89 DB2 89 FlashBackup 90 FlashBackup Windows 90 Informix 90 Lotus-Notes 89 MS-Exchange 89 MS-SharePoint 90 MS-SQL-Server 89 MS-Windows-NT 89 NBU-Catalog 89 NCR-Teradata 89 NDMP 89 NetWare 89 Oracle 89 SAP 90 SQL-BackTrack 90 Standard 89 Sybase 90 Vault 89 Vault Catalog Backup 122 Policy update interval property 326, 436 Port Ranges host properties Client port window 457 Client reserved port window 457 Server port window 458 Server reserved port window 458 Use OS selected non reserved port 457, 458 Use random port Assignments 457 ports allowing operating system to select non reserved port 457, 458 non reserved 480 power down NetBackup servers 633 Preferred property in Fibre Transport host properties 422

prelabel media 510, 521 preprocess interval 191 preview volume configuration update 550 primary copy becoming a 332 changing 328 definition 333 promoting to 328 print device configuration 623 job list information 53 license key 636 Prioritized storage unit selection in group 267 priority of a job 98 of duplication jobs 135 of relocation jobs started from this schedule setting 250 of restore jobs property 436 Private Branch Exchange 61, 66 Problems report 76, 383, 384 proc file system, excluding from backups 195 Process busy files property 381 processes check with vmps 635 monitoring 66 show active 634 properties changing on multiple hosts 363 exporting 361 overview 361 viewing 360 PureDisk Storage Option 224, 229 Storage Pool Authority (SPA) 229

Q
quick erase 529 Quiescent wait time 491 quotas on file systems 222

R
random ports, setting on server 457 raw partitions 103 backing up 96, 119, 171 backups on UNIX 178, 179 Follow NFS policy attribute 102 restoring 172

786

rebooting NetBackup servers 634 recommended method of configuring devices 595 recycle media 537 redirected restores 179, 673 Reduce fragment size storage unit setting 238, 753 registry, backup/restore 172, 173 relocation schedule 119, 129, 135, 141 remote device management 649 systems, administering 645 Remote Administration Console 647 replace media 535 reports All log entries report 76 Client backups report 76 description of utility in Administration Console 72 Disk logs report 79 Disk pool status report 80 Disk storage unit status report 79 Images on disk report 79 Images on media report 76 Images on tape report 77 Media log entries report 77 Problems report 76 running a report 72 settings for building a report 74 Status of backups report 76 Tape contents report 77 Tape lists report 78 Tape logs report 77 Tape summary report 78 Tape written report 78 using the Troubleshooter 80 requests assigning 499 denying 501 display pending 498 overview 498 resubmitting 501 reset file access time property 398 mount time 503 residence, update volume configuration 546 Resource Broker logging property 444 restarting jobs 52 Restore Failover host properties Alternate restore failover machines

list 460 Restore job resuming 683 suspending 683 Restore retries interaction with checkpoint restart 683 property 477 restores alternate server 687 directed from the server 672 from a specifc backup copy 136, 687 raw partition 172 redirected 459, 673, 675 reducing search time 355 registry on Windows clients 173 server independent 687 symbolic links on UNIX 177 System State 684 resuming suspended jobs 52 retention levels default 140 for archiving catalogs 320 retention periods caution for setting 152 changing 463 expiration 152 expiring backups with bpexpdate 534 guidelines for setting 138 lifecycle and policy-based 138, 256 mixing on tape volumes 140, 449 precautions for setting 140 redefining 462 setting 138 user schedule 152 Retention type in lifecycle Expire after duplication 262 Fixed 260 Staged capacity managed 260 Retries allowed after runday policy setting 128 Retry count property 382 retry restores, setting 477 robot barcode update 523 compare contents 549 control host 600 destination for move volume 527 device file 601 device host 599 drive number 610

787

for new volume 515, 527 inventory 511, 551 library 610 number 601 number storage unit setting 239 performing diagnostics 622 type 602 type storage unit setting 239 Robust logging 442 Round Robin storage unit selection in group 267 RS-MTF1 format, allow overwrite 447

SCSI Long Erase 528 pass-through command 589, 596 persistent reserve 448 drive path override 606 Quick Erase 528 reserve, configuring 447 reserve/release drive path override 606 SeCuRiTy.nnnn files 681 sendmail 439 server administration, backlevel 38 alternate server restores 687 directed restore 672 -directed restores 659 EMM server 280, 281 host properties 465 independent restores 459, 687 list definition 465 port window property 458 power down 633 rebooting 633 reserved port window property 458 sends mail property 481 SERVER, vm.conf entry 625 setconf.bat file 660 Shadow Copy Components directive 173, 187 using 392 shared drives configuration wizards 595 drive operating mode 496, 497, 503 SharedDisk host properties Default mount point 470 storage units 224 SharePoint 2003 57, 115, 471 SharePoint Hosts host properties Farm component-end host 472 Farm front-end host 472 show robot contents 551 shut down NetBackup daemons 633 single file layout for NetBackup catalogs 278 restore program, FlashBackup 177 Single-Instance Storage (SIS) 96, 106, 108, 261, 413, 742, 752

S
SAP policy type 90 Schedule backup attempts property 114, 435 schedules adding to policy 118 backups on specific dates 146 catalog backup 311 examples of automatic 151 excluding dates 145 frequency 129 how calendar scheduling interacts with daily windows 149 monthly backups 148 naming 118 not combining calendar-based and frequencybased 128, 129 overview 117 priority 130 retention level defaults 140 retention periods guidelines 138 setting 138 setting backup times 143 specify multiplexing 141 storage unit/lifecycle policy 137 type of backup 119 user backup or archive 151 volume pool 137 weekly backups 147 scratch pool, adding 541 volume pool 93 scripts 56 bpdbjobs example 69 bpps 634 goodies 687 vmps 635

788

slot number add volume 513 for move volumes 527 Snapshot Client 56, 90, 96, 116, 131, 185, 224, 229, 392, 484 SnapVault storage units 224, 235, 240, 259, 273, 744 Solaris 9 extended attributes 177 SPC-2 SCSI reserve 448 SQL-BackTrack policy type 90 Staged capacity managed retention type for storage lifecycle policy 260 staging schedule storage unit setting 239 using BasicDisk storage unit 228 using Storage Lifecycle Policies 253 Standard policy type 89 start up NetBackup daemons 634 status codes, NetBackup 71 163 Status of backups report 76 Storage device storage unit setting 239 storage devices, steps for attaching 595 Storage Lifecycle Policies 137, 253 and the Multiple copies configuration dialog 137 copy number 257 Data classification 262 duplication jobs configuration 264 mixed retention types in the same volume 261 optional LIFECYCLE_PARAMETERS configuration 264 retention type 138, 256 storage destinations 255, 259 using nbstlutil to administrate lifecycle operations 265 writing multiple copies 256 Storage Migrator 93, 221, 238, 694 storage servers 222 storage unit groups 271, 273 name setting 239 selection within a storage unit group 273 type setting 240 storage units AdvancedDisk disk type 223 available storage property of volume 237 BasicDisk type 223 capacity property of volume 237

changing server to manage 639 creating 217, 218 creating a basic disk staging unit 247 creation overview 216 deleting 218, 219 disk pool comment property 237 disk storage units 222 for policy 91 for schedule 137 high water mark property of volume 237 low water mark property of volume 237 maintaining space on disk storage units 225 Media Manager type 220 name property 237 naming conventions 631 NDMP disk type 227 NearStore 273, 746 NearStore disk type 223, 235, 273 number of volumes property 237 OpenStorage disk type 223 optical devices 132, 333 percent full property on volume 237 PureDisk disk type 224, 273 QIC drive type 132, 333 raw size property on volume 238 SharedDisk disk type 224 SnapVault disk type 224, 235, 273 storage lifecycle policies 224 usable size property of volume 238 vendor-specific 223 subnets and bandwidth limiting 377 Sun PC NetLink 177 suspend backups and restores 52, 53, 683 media 501 Sybase Adaptive Server Anywhere (ASA) default password 702 in NetBackup installation 280 management of 705 starting/stopping ASA service 705 use in NetBackup 697 Sybase policy type 90 Symantec Private Branch Exchange 61, 66 Symantec Product Authentication and Authorization 45, 61 Symantec products properties 473 Symantec support Web site 594 symbolic links included in backup selection list 167

789

UNIX 177 synthetic backups and encryption 208 component images 203 cumulative incremental 204 full 203 logs produced during 210 no NetBackup change journal support 404 recommendations for running 206 schedules 128 using Checkpoint Restart 96 System State backups 96 directive 186 restoring 684

T
tape assigning requests 499 contents report 77 library half-inch (TLH) 614 multimedia (TLM) 614 lists report 78 logs report 77 Stacker Half-inch (TSH) daemon 65 summary report 78 written report 78 TapeAlert 608 tar format, allow overwrite 447 TCP level logging property 402 temporary staging area 135, 230, 239, 240, 752 third-party copies 333 Third-Party Copy Device Advanced Backup method 96 Time overlap property 405 Timeouts host properties Backup end notify timeout 476 Backup start notify timeout 474 Client connect timeout 474 Client read timeout 475 File browse timeout 475 Media mount timeout 475 Media server connect timeout 476 Use OS dependent timeouts 475 tlmd daemon 65 tmpfs file system, excluding from backup 195 To IP address property 378

tpconfig menus 605 tpext utility 711 Transfer throttle storage unit setting 240 traversing directories to back up a file 419 Troubleshooter using in Activity Monitor 53 using in Reports application 80 True Image Restoration (TIR) configuration 108 Error code 136 209 length of time to keep information 384 move detection 109 no NetBackup change journal support 404 pruning information 209 with Move Detection 209 with move detection 404 tshd daemon 65

U
uncompress files before backing up property 396 NetBackup catalogs 357 unified logging 441 Universal host properties Allow server file writes 480 Use preferred group for enhanced authorization 479 settings properties 477 UNIX client host properties Add to all 401 Do not compress files ending with 401 Do not reset file access time 398 Keep status of user-directed backups, archives, and restores 397 Megabytes of memory 398 primary node in tree 482 UNIX server properties 483 UNSET, file list directive 193 UNSET_ALL, file list directive 193 unsupported characters 553 update and rescan barcodes 523 robot procedure 553 volume configuration 545, 547 usbdevfs file system, excluding from backup 195 Use alternate read server 135, 251 Use case sensitive exclude list host property 414

790

Use change journal in incrementals property 403 Use defaults from the master server configuration property 423 Use Direct Access Recovery for NDMP restores property 432 Use legacy DES encryption property 410 Use non reserved ports property 425, 427 Use OS dependent timeouts property 475 Use preferred group for enhanced authorization property 479 Use random port assignments properties 457 Use reserved ports property 425, 427 Use specified network interface property 478 Use VxFS file change log for Incremenatal backups property 398 USE_CTIME_FOR_INCREMENTALS 695 USE_NBJAUTH_WITH_ENHAUTH 666 user access to devices 624 archive backups 120 backups 120 schedules planning 151 User directed timeouts property 406

V
Vault backup type 122 catalog archiving 323 designating duplicate as the primary 328 disaster recovery data 198 Logging property 444 Maximum vault jobs host property 438 parent and child jobs 57 policy creating 199 type 89 Recovery Report 198 vendor-specific storage units 223 verifying backup images 327 selections list 167 veritas_pbx (Symantec Private Branch Exchange) 66 view properties of a license key 637 Virtual Tape Option 45, 227 vm.conf file adding SERVER entries 625 VMD (NetBackup Volume Manager) 60

vmd process 66 vmps script 635 vmscd daemon 60 VMWare Proxy Servers host properties 484 vnetd Only property (for selection of ports) 428 Veritas Network Daemon 425, 427 VNETD_PORT 660 Volume Configuration wizard 511 volume group changing name 520, 521 deleting 544 for move volume 527 moving 542 volume is in a robotic library for move volume 527 for new volume 516 Volume Manager (VxVM) 179 volume pools add volume 516 adding 539 CatalogBackup 93 changing attributes 539 changing for a volume 519 DataStore 93 DataStore pool 516, 519 deleting 542 for schedule 137 indicating one for use by a policy 93 NetBackup 93 None 93 overview 538 scratch 93 Volume Shadow Copy Service (VSS) 186, 187, 392 Volume Snapshot Provider (VSP) backups using Checkpoint restart 96 directory for logging messages 487 properties 485 using with databases volumes adding 508 allocation 93 assigned 533 assignments 93 changing 517 cleaning count 519 deleting (see deleting) description for new volume 515

791

for move volume 528 header device 611 maximum mounts allowed 514 moving 524 moving, actions menu 525 recycling 537 replacing 535 scratch 93 VRTSat (Symantec Product Authentication Service) 61 VRTSaz (Symantec Product Authorization Service) 61 VRTSpbx (Symantec Private Branch Exchange) 61 VSP (see Veritas Volume Snapshot Provider) VxFS 4.0, named data streams 180 file change log 398 vxlogcfg command 442 vxlogmgr command 442

W
WAFL qtree cleaning up 744 Wait time before clearing archive bit property 403 weekly backups, scheduling 147 wildcard characters in exclude files lists 632 UNIX escape character 633 file paths 176 Windows clients 171 Windows client host properties Communications buffer size 406 General level logging 402 Incrementals based on archive bit 405 Incrementals based on timestamp 405 Keep status of user-directed backups, archives, and restores 406 Maximum error messages for server 406 Perform default search for restore 406 TCP level logging 402 Timeout overlap 405 Use change journal in incrementals 403 User directed timeouts 406 Wait time before clearing archive bit 403 Windows Disk-Image (raw) backups 96, 171 Windows Display Console 37, 645, 651 Windows Open File Backups

host properties Abort backup on error 394 Disable snapshot and contine 394 Enable Windows Open File backups for this client 392 Global drive snapshot 393 Individual drive snapshot 393 Use Microsoft Volume Shadow Copy Service (VSS) 392 Use Veritas Volume Snapshot Provider (VSP) 392 Windows Terminal Services 39 wizards backup policy 82 catalog backup 296 Device Configuration 217, 596 device configuration 620 shared drive configuration 605 Working directory property 381 WORM media retention period caution 140

792