Veritas Netbackup 6 5 System Administration Guide Volume I for Windows(1) | Backup | Computer Data Storage

Veritas NetBackup™ Administrator’s Guide, Volume I

for Windows

Release 6.5

12308280

Veritas NetBackup Administrator’s 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 NON­ INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be “commercial computer software” 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.
Windows is a registered trademark of Microsoft Corporation.

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
Running the Windows-based NetBackup Administration Console ......35
Running the Java-based Windows Display Console ...............................36
Administering remote servers ...................................................................36
Using the NetBackup Administration Console ...............................................38
NetBackup configuration wizards .............................................................39
Activity Monitor ...........................................................................................40
NetBackup Management .............................................................................40
Reports ...................................................................................................40
Policies ...................................................................................................40
Storage ...................................................................................................40
Catalog ...................................................................................................41
Host Properties .....................................................................................42
Media and Device Management .................................................................42
Device Monitor .....................................................................................42
Media ......................................................................................................42
Devices ...................................................................................................42
Credentials ............................................................................................43
Access Management ....................................................................................43
Standard and user toolbars ........................................................................43
Customizing the administration console .................................................43
Using LiveUpdate to distribute NetBackup updates ......................................44
How to configure NetBackup .............................................................................44
Online documents ................................................................................................46

Chapter 2

Activity Monitor
Introduction to the Activity Monitor ................................................................48
Activity Monitor menu bar .........................................................................49
Status bar ......................................................................................................52
Activity Monitor topology ..................................................................................52
Topology connections .................................................................................53
Selecting topology objects ..........................................................................54
Jobs tab ..................................................................................................................55

6

Parent jobs .................................................................................................... 55
Services tab ........................................................................................................... 57
More about services ..................................................................................... 60
Other Symantec services ............................................................................ 60
Processes tab ........................................................................................................ 62
Monitoring NetBackup processes ............................................................. 66
Drives tab .............................................................................................................. 67
Drive cleaning functions .................................................................... 67
Media mount errors ............................................................................................. 69
Queued media mount errors ...................................................................... 69
Canceled media mount errors .................................................................... 69
Managing the jobs database ............................................................................... 69
Retaining job information in the database .............................................. 70
Changing the default on a permanent basis .................................... 70
BPDBJOBS_OPTIONS environment variable ................................... 71
bpdbjobs debug log ...................................................................................... 72

Chapter 3

Reports
Introduction to the Reports utility ................................................................... 74
Reports window ................................................................................................... 75
Shortcut menus ............................................................................................ 75
Reports settings ........................................................................................... 76
Date/Time range .................................................................................. 76
Client ...................................................................................................... 76
Disk pool ................................................................................................ 76
Disk type ................................................................................................ 77
Job ID ..................................................................................................... 77
Media ID ................................................................................................ 77
Media owner ......................................................................................... 77
Media server ......................................................................................... 77
Path ........................................................................................................ 77
Storage unit .......................................................................................... 77
Verbose listing ...................................................................................... 77
Volume ID ............................................................................................. 77
Volume pool .......................................................................................... 78
Run report ............................................................................................. 78
Stop report ............................................................................................ 78
NetBackup report types ...................................................................................... 79
Status of Backups report ........................................................................... 79
Client Backups report ................................................................................. 79
Problems report .......................................................................................... 79
All Log Entries report .................................................................................. 79
Images on Media report .............................................................................. 79

7

Media Logs report ........................................................................................80
Tape Reports .................................................................................................80
Images on Tape report .......................................................................80
Tape Logs report .................................................................................80
Tape Contents report ..........................................................................80
Tape Summary report ........................................................................81
Tape Written report ............................................................................81
Tape Lists report .................................................................................81
Disk Reports ..................................................................................................82
Images on Disk report ........................................................................82
Disk Logs report ..................................................................................82
Disk Storage Unit Status report ........................................................82
Disk Pool Status report ......................................................................83
Using the Troubleshooter within reports ........................................................83

Chapter 4

Policies
Using the Policies utility .....................................................................................86
Tree and detail views ...................................................................................86
Policies menu bar .........................................................................................87
Configuring backup policies ...............................................................................87
Changing policies .................................................................................................88
Using the composite change dialog ...................................................91
Policy Attributes tab ............................................................................................93
Policy type .....................................................................................................94
Data classification ........................................................................................96
Policy storage ..............................................................................................97
Considerations before a storage destination is selected ................98
Policy volume pool .......................................................................................99
Volume pool override example ........................................................100
Checkpoint restart for backup jobs .........................................................101
Checkpoint frequency .......................................................................101
Checkpoint restart support ..............................................................101
Checkpoint restart for restore jobs .................................................103
Limit jobs per policy ..................................................................................103
Notes on the Limit jobs per policy attribute ..................................103
Job priority ..................................................................................................104
Media owner ...............................................................................................105
Active. Go into effect at .............................................................................105
Backup network drives ..............................................................................106
Setup example with UNC paths .......................................................106
Example using the Backup network drives attribute ...................107
Follow NFS ..................................................................................................107
Notes on Follow NFS ..........................................................................108

8

Advantages of the Follow NFS attribute ........................................108
Disadvantages of the Follow NFS attribute ................................... 108
Cross mount points .................................................................................... 109
Notes on cross mount points ...........................................................109
Cases that can require separate policies ........................................110
How the Cross mount points attribute interacts with Follow NFS 110
Cross mount point examples ............................................................ 110
Compression ............................................................................................... 111
Advantages of the Compression attribute ..................................... 112
Disadvantages of the Compression attribute ................................ 112
How much compression can be expected? ..................................... 112
Encryption ..................................................................................................113
Collect disaster recovery information for IDR ......................................114
Collect disaster recovery information for Bare Metal Restore ........... 114
Collect true image restore information .................................................. 114
Collect true image restore information with move detection ............ 115
What happens during true image restores .................................... 116
Notes on true image restores and move detection ....................... 117
Allow multiple data streams .................................................................... 118
When to use multiple data streams ................................................ 118
Enable document restore .......................................................................... 121
Keyword phrase ......................................................................................... 121
Snapshot Client options ............................................................................ 121
Schedules tab ...................................................................................................... 123
Schedule Attributes tab .................................................................................... 124
Name ............................................................................................................ 124
Type of backup ........................................................................................... 125
Full backup .......................................................................................... 125
Cumulative incremental backup ..................................................... 126
Differential incremental backup ..................................................... 126
User backup ........................................................................................ 126
User archive ........................................................................................ 126
Application backup ............................................................................ 127
Automatic backup ..............................................................................127
Automatic incremental backup ....................................................... 127
Automatic cumulative incremental backup .................................. 127
Automatic differential incremental backup .................................. 127
Automatic full backup ....................................................................... 127
Automatic Vault ................................................................................. 128
Vault catalog backup ......................................................................... 128
More on incremental backups .........................................................128
Determining files due for backup on Windows clients ................ 131
Determining files due for backup on UNIX clients ....................... 132

9

Synthetic backup ........................................................................................134
Calendar schedule type .............................................................................134
Retries allowed after runday ............................................................134
Frequency schedule type ..........................................................................134
Guidelines for setting backup frequency .......................................135
Backup frequency determines schedule priority ..........................136
Instant recovery .........................................................................................137
Snapshots and copy snapshots to a storage unit ..........................137
Snapshots only ...................................................................................137
Multiple copies ...........................................................................................137
Multiple copies and disk staging storage units .............................138
Multiple copies and storage lifecycle policies ...............................138
Multiple copies configuration ..........................................................139
Restoring from a specific backup copy ...........................................142
Override policy storage selection ............................................................143
Override policy volume pool ....................................................................143
Override media owner ...............................................................................143
Retention .....................................................................................................144
Guidelines for assigning retention periods ....................................144
Precautions for assigning retention periods .................................145
Changing retention periods ..............................................................146
Mixing retention levels on tape volumes .......................................146
Media multiplexing ....................................................................................147
Final destination storage unit ..................................................................147
Final destination volume pool .................................................................147
Start Window tab ...............................................................................................148
Exclude dates tab ...............................................................................................151
Calendar schedule tab .......................................................................................152
Schedule by specific dates ........................................................................152
Schedule by recurring week days ............................................................153
Schedule by recurring days of the month ..............................................154
How calendar scheduling interacts with daily windows ......................155
Automatic-backup schedule examples ...................................................157
Considerations for user schedules ..........................................................157
Planning user backup and archive schedules ................................157
Creating separate policies for user schedules ...............................158
Using a specific policy and user schedule ......................................158
Example policies ................................................................................................159
Policy planning guidelines for backups ..................................................160
Group the clients ................................................................................160
Gather information about clients ....................................................160
Consider storage requirements .......................................................160
Consider backup schedules ...............................................................161

10

Group by general attributes ............................................................. 162
Clients tab ........................................................................................................... 165
Backup Selections tab ....................................................................................... 167
Lists for different policy types ................................................................ 167
Backup selections list for standard policies .................................. 167
Backup selections list for database policies ................................... 169
Methods for faster backups ...................................................................... 171
Dividing file lists between multiple policies .................................. 171
Allowing multiple data streams ...................................................... 171
Verifying the backup selections list ........................................................ 172
Rules to indicate paths in the backup selections list ................................... 174
Path rules for Microsoft Windows clients ............................................. 174
File backups ........................................................................................ 174
Windows disk-image (Raw) backups ............................................... 175
Microsoft Windows registry backup ............................................... 177
Hard links to files (NTFS volumes or UNIX) .................................. 178
Path rules for NetWare NonTarget clients ............................................ 179
Path rules for NetWare Target clients ................................................... 181
Path rules for clients running extension products .............................. 181
Backup selections list directives: General discussion .......................... 181
ALL_LOCAL_DRIVES directive ........................................................ 182
SYSTEM_STATE directive ................................................................ 182
Shadow copy components:\ directive ............................................. 183
Directives for multiple data streams .............................................. 184
Directives for specific policy types ................................................. 184
Backup selections list directives for multiple data streams ............... 185
NEW_STREAM directive and multiple data streams ...................185
ALL_LOCAL_DRIVES directive and multiple data streams ........ 188
UNSET, UNSET_ALL directives, and multiple data streams ...... 189
Excluding files from backups ................................................................... 190
Files that are excluded from backups by default .......................... 190
Excluding files from automatic backups ........................................191
Windows excluded files .................................................................... 191
Disaster Recovery tab ....................................................................................... 193
Path .............................................................................................................. 194
Logon ........................................................................................................... 194
Password ..................................................................................................... 194
Send in an email attachment ................................................................... 194
Identifying critical policies ...................................................................... 195
Creating a Vault policy ..................................................................................... 196
Performing manual backups ............................................................................ 197
More about synthetic backups ......................................................................... 198
Policy considerations and synthetic backups .......................................198

11

Two types of synthetic backups ...............................................................200
Synthetic full backups .......................................................................200
Synthetic cumulative incremental backups ..................................201
Recommendations for synthetic backups ..............................................203
Notes on synthetic backups ......................................................................204
Displaying synthetic backups in the Activity Monitor ........................207
Logs produced during synthetic backups ...............................................207
Synthetic backups and directory and file attributes ............................208

Chapter 5

Storage units, unit groups, and lifecycle policies
Introduction to the Storage utility ..................................................................210
Using the Storage utility ...........................................................................211
Storage units .......................................................................................................212
Creating a storage unit ..............................................................................213
Changing storage unit settings ................................................................214
Deleting storage units ...............................................................................214
Media Manager storage unit considerations .........................................216
Disk storage unit considerations .............................................................218
Disk storage model .............................................................................218
Disk storage units in storage lifecycle policies .............................220
Maintaining available space on disk storage units .......................221
NDMP storage unit considerations .........................................................223
Storage unit settings .........................................................................................224
Absolute pathname to directory/volume ...............................................224
Density .........................................................................................................225
Disk pool ......................................................................................................225
Disk type ......................................................................................................225
Enable block sharing .................................................................................225
Enable multiplexing ...................................................................................226
High water mark ........................................................................................226
Low water mark ..........................................................................................226
Maximum concurrent write drives .........................................................227
Maximum concurrent jobs .......................................................................227
Using the Maximum concurrent jobs setting to control the storage unit
and media server load ...............................................................228
Maximum streams per drive ....................................................................229
Media server ...............................................................................................229
NDMP host ..................................................................................................231
On demand only .........................................................................................231
Only use the following media servers .....................................................232
Properties button .......................................................................................232
Reduce fragment size ................................................................................234
Robot number ............................................................................................235

12

Robot type ..................................................................................................235
Staging relocation schedule (for basic disk staging only) ...................235
Storage device ............................................................................................ 235
Storage unit name ..................................................................................... 235
Storage unit type ....................................................................................... 236
Temporary staging area ........................................................................... 236
Transfer throttle ........................................................................................ 236
Use any available media server ............................................................... 236
Staging backups to initial storage, then final storage ................................. 238
Two staging methods ................................................................................ 238
Basic disk staging .............................................................................................. 240
Disk staging storage unit size and capacity considerations ............... 241
Finding the potential free space on a BasicDisk disk staging storage unit
242
Creating a basic disk staging storage unit ............................................. 243
Disk Staging Schedule dialog ................................................................... 245
Name .................................................................................................... 245
Priority of relocation jobs started from this schedule ................. 246
Final destination storage unit ..........................................................246
Final destination volume pool .........................................................246
Final destination media owner ........................................................ 246
Use alternate read server ................................................................. 247
Basic disk staging limitations .................................................................. 247
Initiating a relocation schedule manually ............................................. 247
Storage Lifecycle Policies ................................................................................. 249
Storage lifecycle overview ........................................................................ 249
To create a storage lifecycle policy .........................................................250
Adding storage destinations to a lifecycle policy ................................. 251
Writing multiple copies using a lifecycle .......................................252
Storage lifecycle policy name ..........................................................254
Duplication job priority .................................................................... 254
Storage destinations .......................................................................... 254
Use storage destination for: backup or duplication ..................... 255
Storage unit ........................................................................................ 255
Volume pool ........................................................................................ 255
Media owner ....................................................................................... 255
Retention type: Fixed ........................................................................ 256
Retention type: Staged capacity managed ..................................... 256
Retention type: Expire after duplication ........................................258
Alternate read server ........................................................................ 258
Data classification ..................................................................................... 258
How backup data is associated with a data classification ........... 259
Creating or changing a data classification .................................... 259

13

Optional duplication job configuration ..................................................260
MIN_KB_SIZE_PER_DUPLICATION_JOB .......................................260
MAX_KB_SIZE_PER_DUPLICATION_JOB ......................................260
MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB .......260
LIFECYCLE_PARAMETERS file example ........................................261
Using nbstlutil to administrate lifecycle operations ............................261
When to use nbstlutil ........................................................................261
Storage unit groups ...........................................................................................263
Storage unit selection criteria within a group ......................................263
Prioritized ...........................................................................................263
Failover ................................................................................................263
Round robin ........................................................................................263
Load balance .......................................................................................263
Exception to the storage unit selection criteria ............................266
Disk spanning within storage unit groups .............................................267
Creating a storage unit group ..................................................................267
Deleting a storage unit group ..................................................................269

Chapter 6

NetBackup Catalog
What is a NetBackup catalog? ..........................................................................272
Parts of the catalog ....................................................................................272
Image database ...........................................................................................273
Image files ...........................................................................................274
Image .f files ........................................................................................274
NetBackup relational database ................................................................276
Enterprise Media Manager (EMM) database ..................................277
Catalog protection .............................................................................................278
Catalog backups ..........................................................................................278
Online, hot catalog backup method .................................................279
Running online, hot catalog backups concurrently with other backups
290
Notes on catalog policy schedules ...................................................290
Offline, cold catalog backup method ...............................................291
Recovering the catalog ......................................................................................310
Disaster recovery emails and the disaster recovery file ..............................310
Archiving the catalog ........................................................................................311
Catalog archiving process .........................................................................311
Creating a catalog archiving policy .........................................................312
Policy name .........................................................................................312
Deactivate policy ................................................................................313
Type of backup ...................................................................................313
Retention level setting ......................................................................313
Catalog archiving commands ...........................................................314

14

Recommendations for using catalog archiving ............................ 316
Using Vault with the catalog archiving feature ............................ 316
Browsing offline catalog archive ..................................................... 316
Extracting images from the catalog archives ................................ 316
Using the Catalog utility ................................................................................... 318
Searching for backup images ................................................................... 318
Notes on searching for an image ............................................................. 320
Verifying backup images .......................................................................... 320
Viewing job results .................................................................................... 321
Promoting a copy to a primary copy ....................................................... 322
Duplicating backup images ...................................................................... 324
Notes on multiplexed duplication ................................................... 324
Procedure for duplicating backups ................................................. 325
Jobs displayed while making multiple copies ........................................329
Importing NetBackup or Backup Exec images ......................................330
Importing expired images ................................................................ 336
Importing images from Backup Exec media .................................. 337
Host properties for Backup Exec ..................................................... 337
Considerations concerning importing Backup Exec media ......... 337
Differences between importing, browsing, and restoring Backup Exec
and NetBackup images .............................................................. 338
Expiring backup images ............................................................................ 341
Catalog maintenance and performance optimization ................................. 342
Determining catalog space requirements .............................................. 342
File size considerations ..................................................................... 343
Backing up catalogs manually ................................................................. 345
How do I know if a catalog backup succeeded? ............................. 346
Strategies to ensure successful catalog backups .................................. 347
About the binary catalog format ............................................................. 348
Catalog conversion utility ................................................................ 348
Binary catalog file limitations .........................................................349
Moving the image catalog ........................................................................ 349
Indexing the catalog for faster access to backups ................................ 350
Compressing and uncompressing the image catalog ........................... 351
Uncompressing the image catalog .................................................. 353

Chapter 7

Host properties
Introduction to host properties ....................................................................... 356
Viewing host properties ............................................................................ 356
Changing host properties ................................................................................. 357
Interpreting the initial settings ............................................................... 358
Selecting multiple hosts ........................................................................... 359
Required permissions ....................................................................................... 360

15

Master server, media server, and client host properties .............................361
Access Control properties .........................................................................361
Symantec Product Authentication and Authorization ................361
Symantec Product Authentication and Authorization tab within the Access
Control properties ..............................................................................362
Networks list .......................................................................................362
Add button ..........................................................................................363
Remove button ...................................................................................364
Authentication Domain tab within the Access Control properties ....364
Add button ..........................................................................................365
Remove button ...................................................................................367
Authorization Service tab within the Access Control properties .......367
Host name ...........................................................................................367
Customize the port number of the authorization service ...........368
Authorization properties ..........................................................................369
User ......................................................................................................369
Domain\Group ....................................................................................370
Host ......................................................................................................370
Group/Domain type ...........................................................................370
User must be an OS administrator ..................................................370
Backup Exec Tape Reader properties ......................................................371
Add button ..........................................................................................371
GRFS advertised name ......................................................................371
Actual client name .............................................................................372
Actual path ..........................................................................................372
Change button ....................................................................................372
Remove button ...................................................................................372
Bandwidth properties ................................................................................373
How bandwidth limiting works ........................................................373
Bandwidth throttle setting for the range of IP addresses ...........374
From IP address ..................................................................................374
To IP address .......................................................................................374
Bandwidth ...........................................................................................374
Bandwidth throttle settings list .......................................................374
Add button ..........................................................................................374
Remove button ...................................................................................375
Notes on bandwidth limits ................................................................375
Busy File Settings properties ...................................................................376
For the Busy File Settings to take effect .........................................376
Working directory ..............................................................................377
Operator’s email address ..................................................................377
Process busy files ...............................................................................377
File action file list ...............................................................................377

............................................................ 383 General tab ..................................383 Maximum data streams ................................ 389 Abort backup on error ............ 391 Client Settings (NetWare) properties ............. 393 ...................................................393 Locked file action ........................................................................... 384 Browse and restore ability ..... and restores .......................................................... 380 Keep true image restoration (TIR) information ............................................................. 387 Add and remove buttons .................. 379 Keep logs ...................................................................................... 382 Allow client browse ......................................................... and restores .................................................................................................................................................. 392 Client Settings (UNIX) properties .....................................................................393 Keep status of user-directed backups.... 392 Back up migrated files ... 384 Free browse ....................................................................... 378 Clean-up properties ............................. 378 Busy file action .............. 388 Use Veritas Volume Snapshot Provider (VSP) ................................................................................................................................................................................................................16 Add button .................................................... 392 Uncompress files before backing up ................................................................................................................................... 390 Client Name properties ....................... 379 Image cleanup . 380 Move restore job from incomplete state to done state ................................. 387 Enable Windows Open File Backups for this client .......................391 Client name ......................... 381 Client Attributes properties .............................................................................................................................. 382 Allow client restore ....................................... 382 Clients list ......................... archives.......................................................................... 379 Keep vault logs ............................................... 388 Use Microsoft Volume Shadow Copy Service (VSS) ................... 389 Global drive snapshot .............................................................................................. 378 Retry count ............................................ 385 BPCD connect back ......................................................... 377 Remove button ...................................................................................................................................................... 384 Connect Options tab ..................................................................................................................................................... 381 Move backup job from incomplete state to done state .......................................................................................................... 380 Catalog cleanup wait time .............................................. 386 Windows Open File Backup tab ................................................................................................................................ 377 Add to all button ................................ 385 Ports ............. 385 Daemon connection port ......................................................................... 392 Keep status of user-directed backups................................ 390 Disable snapshot and continue ...................................................................................................... archives............. 388 Individual drive snapshot .....................................

...............404 Description ...................................................................................394 Use VxFS file change log for incremental backups ......................................397 Add to all button ...........................406 Encryption libraries ...........................................410 ....................................................................................................................................................409 Exclude Lists properties .................................................... archives...................................401 Incrementals based on archive bit ....404 Encryption properties ..........403 Rank ...396 Do not compress files ending with ..............................409 Mailbox for message level backup and restore ...............408 Backup option for log files during full backups .............................402 Perform default search for restore .........................................................................................................................................................................................................................................................408 Snapshot verification I/O throttle ................405 Enable encryption .....................398 Wait time before clearing archive bit ....................................................................398 General level logging .........402 Maximum error messages for server ........397 Add button ......407 Encryption key file ..........................................................................................................410 Use case sensitive exclude list .........................................................................................................17 Reset file access time to the value before backup .....................................................................................................402 User directed timeouts .....................................................................................................................394 Megabytes of memory to use for file compression ...........................................................................406 Encryption strength ..........................................................................403 Name .........................................................405 Encryption permissions .......................................................402 Keep status of user-directed backups.......................................................................................................................................................................................................402 Data Classification properties ..................................................................406 Use legacy DES encryption ........410 Exclude list .........398 TCP level logging ..................................................................397 Remove button ..........................................406 Client cipher ................................................................................................401 Time overlap ...404 Classification ID .......................409 Enable single instance backup for message attachments ................................... and restores .................................................................397 Client Settings (Windows) properties ...........................................................................................399 Use change journal in incrementals .....394 Default cache device path for snapshots ....................................................................................................406 Enable standard encryption ...................399 Incrementals based on timestamp .......................................................401 Communications buffer size ................................................407 Exchange properties .................................................................................................................................

..................................................................................................................................................................... 422 Attributes for selected hosts .......................... 419 Firewall properties ................... 428 Use direct access recovery for NDMP restores .................. 419 Maximum concurrent FT connections ........................................................................ 420 Hosts list . 428 Document-level restore options ................................................................................... 434 Maximum vault ......................................................................................................................................................................................................................434 ............................... 432 Maximum jobs per client ......................................................................................................................................................................................................................................................................411 Remove buttons . 430 Global Attributes properties ........... 418 Preferred ................................................................................................................. 429 Add button .........................................................................................................................................427 Must use local drive ...................... 423 Example setup for using the vnetd port ........................................................................ 412 Shared fields in exclude lists .................................................................................................................................................................................419 Never .................. 414 Traversing excluded directories ................. 427 Delay on multiplexed restores ......... 432 Maximum backup copies ................................................................................................................... 434 Administrator email address ..............................412 Schedule ............... 429 Change button ....................................................................................................................................................................................................................................................................................................................................................... 431 Policy update interval ................ 413 Exclude lists for specific policies or schedules ......... 416 Fibre Transport properties ............. 411 Add to all buttons ......................................................... 425 General Server properties ............................. 429 Add to all button ........................................... 428 Media host override ............................................................................................................................................................ 413 Syntax rules for exclude lists . 431 Job retry delay ................................................................... 419 Use defaults from the master server configuration ........................................................................................................................................................................................................................... 412 Files/Directories ......................... 420 Default connect options ....411 Add buttons .............................................. 432 Priority of restore jobs ................................................................................ 412 Policy ............................. 433 Compress catalog interval ........................................... 429 Remove button ......................................................427 Check the capacity of disk storage units .................................................18 Exceptions to the exclude list ... 431 Schedule backup attempts ......................... 418 Always ...............................................................................

.........................454 NetBackup client service port (BPCD) .......434 Configuring the nbmail.............................445 Media properties ......................................................458 ...................................................................................455 Open File Backup (NetWare client) properties ....................................................................453 Password and confirm password ...............................................................................................................................................................................................................445 INI file ...............................440 Enable robust logging ....453 Network properties ......457 Server port window ........435 Installing the email utility ........................cmd script ......................455 Port Ranges properties .........................451 Media request delay ..............................................................................................450 Media ID prefix (non-robotic) .....................................................................................................................................450 Enable unrestricted media sharing for all media servers ............................446 Enable SCSI reserve .........................................................443 Lotus Notes properties .................................................................................450 Enable job logging ...............................446 Allow media overwrite ...................................449 Allow backups to span disk .........................................................................................................................................................................................................................441 Global logging level ...................................................................453 NetWare Client properties ....................457 Client port window ....19 Setting up email notifications .........................................447 Allow multiple retentions per media ..................................................456 Use random port assignments .....................................................................................................................................................................................................452 User name ........................................................................................................................436 Indicating email notification in the NetBackup host properties 437 Email contents ...............................451 NDMP Global Credentials properties .439 Logging properties ..................449 Allow backups to span tape media .....................................................................................................................................438 Troubleshooting the notification ........................................................458 Server reserved port window ...............................................................................457 Client reserved port window ...........451 Media unmount delay ...445 Path .............450 Enable standalone drive extension ................................................................................................442 Debug logging levels for NetBackup services .............................................................................454 Announce DHCP interval ...................................................................................................................................................................................................................................................................................................455 Enable open file backup during backups ..................440 Types of logging ......................................................................................454 NetBackup request service port (BPRD) ..............................................442 Process specific overrides .....

................................................................................... 479 Last full backup .................................................................................................................................................. 461 Media server ............................. 473 SharePoint Hosts properties ............................................20 Restore Failover properties ........................... 465 Master server ................................................................................................................................................................. 473 Symantec Products properties ....................................................................................................................................... 464 Servers properties ............................................. 461 Remove button ................................................................................................................................................................................................................................... 460 Change button ............................................ 471 SharePoint 2003 properties ................................................................. 463 Impact report button ........................................ 479 ...................... 462 Units ........................................... 462 Retention periods list .......................... 476 Backup end notify timeout ........................................................... 472 User ID ........................................................................ 476 Use OS dependent timeouts ....................................................................................................................................... 472 Continue with backup if consistency check fails .................. 461 Retention Periods properties .......... 477 Media server connect timeout ....................................................................................... 475 Client connect timeout ................................................................................................................................................................................................................................................ 462 Schedules list ........ 476 Media mount timeout .................................................................................................................................. 462 Value ................................................................................................................................................................................................................... 475 File browse timeout ............................. 466 Restricting administrative privileges of media servers ............................................................................ 459 Alternate restore failover machines list .................................................................................471 SharedDisk mount points directory .................................................................... 479 Use specified network interface .................... 478 Restore retries ............................................................................................................................................... 463 Note on redefining retention periods ....................................................................................................472 Password ....................... 475 Backup start notify timeout ..................................................... 476 Client read timeout .............................477 Universal Settings properties ........... 465 Additional servers ....................460 Add button ....................................................................................................... 472 Consistency check before backup ........... 461 Failover restore servers ........................465 Media servers ............ 474 Timeouts properties ........................ 466 Multiple masters that share one Enterprise Media Manager host 468 SharedDisk properties .............................. 478 Browse timeframe for restores .....

..............499 Pending requests for storage units ..................................................485 VSP (Volume Snapshot Provider) properties ....................................................................................................................500 Resolving a pending request ...................................................481 Enable performance data collection (Windows server only) ................................486 VSP overview ......................................................................................506 Chapter 9 Media Volume operations ...............................................................................................................................502 Denying a request ...................502 Resubmitting a request ................................488 VSP volume exclude list .....................................................480 Allow server file writes ...................................................................499 Managing pending requests and actions ....................495 Chapter 8 Device Monitor Changing the operating mode of a drive ...............................21 Use preferred group for enhanced authorization ................481 Client administrator’s email .................................................................................................................................................................484 VMWare Proxy Servers properties ............................................498 Managing drive paths ............504 Adding or changing a drive comment ..........491 Maximum cache size ..............................................501 Resolving a pending action .............................................................483 UNIX Server properties ................503 Cleaning drives ......................................................................................................................................................................................481 Accept connections on non reserved ports ..............................................................................................................................................................484 NFS access timeout ..........................................497 Resetting a drive ...............................................506 Viewing drive details .............................................................................................510 ...............489 Customize cache size ...............481 Server sends mail .............................................492 Busy file timeout ..................................................................................491 Cache size ............................................................................................................488 Cache file volume list ..........................................................................................................................................................509 Adding volumes ...............................481 Client sends mail .............486 Logging VSP messages ..............................................................................................................................................................482 UNIX Client properties ............................................................................................................493 Windows Client properties ................................................491 Busy file wait .........493 Using VSP with databases ...................................................................................................................................................................................................................................................................................503 Freezing media or downing drives .........................

................................. 510 About labeling NetBackup volumes ............................................................................................ 539 Recycling volumes using the existing media ID ........................... 535 Deassigning NetBackup volumes ................................... 522 Label properties ...................................................................................................................................... 537 Exchanging a volume and using the old media ID .... 540 Changing the properties of a volume pool ..................................... 524 When to rescan and update ................................................ 515 Changing volume properties .......................................................531 Ejecting volumes ........................................................................ 528 Erasing media ........ 522 Labeling media .............. 518 Change Volumes properties .................. 538 Recycling volumes ...... 519 Changing the volume pool of a volume ........ 529 Injecting and ejecting volumes .................................................................................................................... 523 Rescanning and updating barcodes .............................. 531 Injecting volumes .................................................................................................................................................................................................................................................... 532 Media ejection timeout periods ....... 524 Rescanning/updating barcodes .................. 525 Move examples ..................... 534 Deassigning volumes ................ 526 Moving volumes using the Actions menu .............................................................. 525 Moving volumes ...................................................................................................................................................................................................... 527 Multiple Move Volumes dialog boxes ......................................................................................... 540 Adding a new volume pool ......................... 520 Changing the owner of a volume ............................................................................................................................................. 524 When not to rescan and update ................................................................................................................................................... 521 Suspending and unsuspending media ...........539 Volume pool operations ................................. 520 Changing the volume group of a volume ...... 537 Exchanging volumes ............................................................. 537 Exchanging a volume and using a new media ID .............................................22 Adding volumes overview .................................................... 534 Deleting volumes ............................................................................................................................................. 539 Recycling volumes using a new media ID .............................. 536 Deassigning Veritas Storage Migrator volumes ................................ 512 Adding volumes by using the Volume Configuration Wizard ....................................................................................... 513 Adding volumes using a robot inventory update .....................................................526 Move Volumes properties ........................ 513 Adding volumes using the Actions menu ..514 Volumes properties .................... 521 Freezing and unfreezing media ............................................................................................................................................................................ 541 ......... 525 Moving volumes using the robot inventory update option ..

..............543 Deleting a volume pool ........................................................................................................................................................544 When to inventory a robot ................................................56 3 Media type ..........23 Volume pool properties ......................................549 Device host .......................549 Empty media access port prior to update .......................................................543 Volume group operations ..............561 Barcode tag ...............................560 Use barcode rules ......................................................................555 Media Settings tab ...............................................................................................................................................................................542 Maximum number of partially full media ......541 Catalog backup ..542 Pool name ..............................................................................542 Description ....................................................................................................544 Robot inventory operations .............................................................559 Media that have been moved into or within the robot .......563 Volume pool ..................566 Robot number ....................................................................................................................................551 Update volume configuration ................................................................................................................................560 Volume pool .......................................572 ...............56 5 Media ID generation rule ....56 7 Default and allowable media types .....................................................................................................................................................................................................................56 4 Media ID Generation tab .......................................................................................................................................................56 1 Barcode Rules tab ...............................................556 Media that have been removed from the robot ...................................................542 Scratch pool ...................................551 Show contents .........................................................................................553 Advanced Robot Inventory Options dialog ...547 Robot Inventory dialog box ..............544 Deleting a volume group ......................549 Compare contents with volume configuration ............................................545 Inventory a robot .......................................................................................................................................................................................................................................555 Media type ...................................................................................................................................................................................................................................................................................550 Preview changes .....566 Adding mapping entries ..................................................................................................................................................................................550 Robot .........563 Max mounts ...........................................................................................................548 Advanced options ..........................................................................................................................................................................566 Media Type Mappings tab .....560 Use the following Media ID prefix .....................................................565 Barcode length ..........................................568 Using the physical inventory utility ..............................................................................................56 2 Description ............................................................................

..................................... 590 Using WORM volume pools to manage WORM media ..................................... 579 Example 1: Removing a volume from a robot ..........576 Updates the EMM database ........ 573 When to use vmphyinv ........................................................ 587 Example 7: Adding existing volumes when barcodes are not used 587 Using WORM media ............................................................606 Drive properties ..................... 595 Operating system changes ................................ 573 Requirements and restrictions for vmphyinv .................................................................... 590 Managing your WORM media in NetBackup ............. 574 Obtains a list of drives to mount the media .......... 593 The device mapping file ....................................................... 596 Devices that are partially-configured ............................ 597 Adding a robot ........................ 589 Supported drives ......................... 607 Configuring drive name rules ....................................... 584 Example 5: Adding cleaning tapes to a robot ...................................... 614 ..............................24 Features of vmphyinv ................................................................................................. 586 Example 6: Moving existing volumes between robots ................................................................... 581 Example 3: Moving existing volumes within a robot ................. 591 WORM tape limitations .............. 596 Starting the Device Configuration Wizard ...................................................... 573 How vmphyinv performs a physical inventory ..................610 Robot drive number for API robots ............................................ 602 Adding or changing a drive ............................................................................................................................................................................................. 590 Using unique drive and media types to manage WORM media .......................................................... 574 Obtains a list of media to be mounted ............... 594 Configuring robots and tape drives .......................................................................... 597 Robot properties ................ 577 Volume configuration update examples .................................................................................................................................583 Example 4: Adding new volumes to a robot .................................................................................................... 605 Configuring SCSI reserve on a drive path ............................................................................................................................................................................................................................................. 595 Using the Device Configuration Wizard ............ 580 Example 2: Adding existing stand-alone volumes to a robot ......................................................................... 574 Mounts media and reads the tape header ......................................... 598 Robot control configuration overview ............. 592 Chapter 10 Devices Device configuration prerequisites ............................................ 613 No rewind device .................................. 604 Adding a shared drive ......................... 596 Possible EMM server host conflict ....................................... 614 Configuring server groups for media sharing ...........................................

....................................629 Using wildcards in NetBackup .................................620 Deleting drives ...................619 Changing a robot configuration ..................................617 Configuring and managing disk pools ..........631 Administering NetBackup licenses .............................................................................643 If you cannot access a remote server ..............................617 Description ..........................................................................625 Managing the EMM server ...632 To administer a remote master server ....................................................................................616 Server group name .....................................................................................................................617 State .............................................................................624 The Enterprise Media Manager server .............................................................................................................................618 Managing your device configuration ..635 To add a NetBackup server to a server list .......................................623 Accessing media and devices on other hosts .................................................635 To choose a remote server to administer ................................618 When to perform device configuration changes .................................................................617 Servers not in group .................................................................................................................................................................645 .....620 Deleting robots ................................................................................................................................................................622 Printing your device configuration ........................................621 Running a drive diagnostic test ...619 Changing a drive to a shared drive ....................................................................................................................................................................619 Changing the configuration of a drive ......630 To power down and reboot NetBackup servers .................................................................................................644 To administer devices on other servers .............................................621 Running a robot diagnostic test ..................616 Server group type ......................626 Chapter 11 Chapter 12 Credentials Management topics NetBackup naming conventions .............................................................................................................617 Configuring SAN clients and Fibre Transport ..................................................................................................................................................622 Stopping and restarting the Device Manager ...............................................................................625 EMM server requirements .........................................................................624 Example SERVER entries .....621 Performing device diagnostics .................................639 Administer a master server by using a NetBackup client ....................................619 Using the Device Configuration Wizard for changes ..............................................................................617 Servers in group ...............25 Server group properties ..........623 Activating and deactivating media servers ..................................................................................................................................................................642 Using the Remote Administration Console ........................

...........661 NBJAVA_CORBA_LONG_TIMEOUT ........................ 661 Configuration options relevant to jnbSA and jbpSA ...............................................................654 Capabilities authorization for jbpSA ............... 655 BPJAVA_PORT..................................................................................... 657 INITIAL_MEMORY........................................................................ 670 To allow redirected restores of a client’s files ......... 655 Runtime configuration options .....................conf entries ...................... 647 To authorize NetBackup-Java users on Windows ..................................... VNETD_PORT ......... 648 NetBackup-Java administration console architectural overview ................... 668 To allow all clients to perform redirected restores .......... 669 To allow a single client to perform redirected restores ......... 648 Authorizing NetBackup-Java users .......................................................................650 Authorization file characteristics ................................................................... 661 USE_NBJAUTH_WITH_ENHAUTH .................................... 656 FIREWALL_IN .. 670 Redirected restore examples ..................... 660 NBJAVA_CONNECT_OPTION ....... 660 NBJAVA_CLIENT_PORT_WINDOW .............................. 664 Is the performance better when run locally or using remote display back? 665 Managing client restores .................................. 675 To restore the files that possess ACLs ............................................................660 NBJAVA_CORBA_DEFAULT_TIMEOUT ......................................................... MAX_MEMORY ...........662 What it means to be running the java console locally on a UNIX platform 663 What it means to be running the console locally on a Windows platform 663 How do I run a console locally and administer a remote server? .......................... 667 Server-directed restores .................................................... 647 To restrict access on Windows .................................................... 662 To customize jnbSA and jbpSA with bp................................................................... 675 ............. 668 How NetBackup enforces restore restrictions ...................................... 656 FORCE_IPADDR_LOOKUP ......................... 671 Restoring files and access control lists ............................................................................. 664 How do I enhance console performance? ............................................................................651 To configure nonroot usage ..........................................................................................................26 Using the NetBackup-Java Windows display console ....................................................................................... 659 MEM_USE_WARNING ...................................................... 662 To log the command lines that the NetBackup interfaces use ....................662 NetBackup-java performance improvement hints ................................................................ 654 Authorizing nonroot users for specific applications .......................................................... 667 Client-redirected restores ........................................... 648 Configuring the NetBackup-Java administration console ...

.........................................................................................................677 Important notes on system state ..............................................27 To restore files without restoring ACLs ....................................................694 Sybase ASA server management ..676 To suspend and resume a restore job .......................................................................................................................................683 Method 3: Automatic failover to alternate server ........692 \log .............................695 Post-installation tasks ....689 server...................................................................................680 Supported configurations ..........................693 \shared ......................................................................684 Notes on alternate server restores .........................696 To change the database password ..............................................................................................................693 \scripts .........................................................................704 .............................................................678 Alternate server restores .700 Backup and recovery procedures ........................................................702 Using the online...............699 Additional create_nbdb options .....................conf .....................................690 registration................................................................................682 Method 1: Modifying the NetBackup catalogs ............................................................................689 databases.................................................................691 \bin .............689 Relocating the NetBackup database ...............................................................693 NetBackup configuration entry .............................................................................................................................................676 Checkpoint restart for restore jobs ....................693 \WIN32 .................................693 \staging ...........................................688 NetBackup master server installation ..................................................................................................................conf ...........................................693 \java ...692 \data .............................................................................................................................696 Moving NBDB database files after installation ........................................................ hot catalog backup method ....................................................................................................................................................................................................................686 Appendix A NetBackup relational database Installation overview ......................................................703 Using the offline...............................................682 Method 2: Overriding the original server .......................................677 Restoring system state .................................................................................................................................................................................................dat .....................................................................695 Clusters ..............680 Methods for performing alternate server restores ..........................677 Limitations to checkpoint restart for restore jobs .........698 Creating the NBDB database .......................................................691 \charsets .........697 To add a mirrored transaction log ............................................................................................. cold catalog backup method ..................................................................675 To improve search times by creating an image list ................

....... 709 Cluster considerations with the EMM server ........................................................................... 729 Viewing storage servers ........................................................................................................................28 Transaction log management ............................................................................................. 722 Maximum concurrent job setting ......................... 725 Changing disk pool or volume state .......... 724 Adding volumes to an AdvancedDisk disk pool ..711 Moving the EMM server to a Windows cluster .exe ................... 726 Merging disk pools ..................... 727 Deleting a disk pool ........................exe ................ 716 Creating an AdvancedDisk disk pool ....................................................................................................................................................................................................................................................................731 Troubleshooting AdvancedDisk ........................ 734 Upgrade considerations ........................................................................................................................................................................................... 706 Terminating database connections ..................... 722 Multiple storage units ....... 706 nbdb_restore........................................................ 704 Catalog recovery ......................................... 731 Unable to access storage ....................................... 712 Appendix B AdvancedDisk storage option Licensing AdvancedDisk ..................... 731 Volume state changes to DOWN when volume is unmounted ....................................................................................................... 723 Changing disk pool properties ............ 728 Obtaining disk pool and volume status ..................................................................................................... 728 Managing storage servers .................. 705 Additional command lines for backup and recovery of the relational databases ...................................................... and licenses .................................................................................................................................................................................................................................................................. 719 Usage recommendations ....................................................................................................................................... 730 Monitoring storage capacity and usage .........732 Appendix C NearStore storage units Required software....................................................................707 Moving the NetBackup database from one host to another ..................................................................................... 736 ............ 729 Deleting a storage server ................................. 723 Disk pool properties ......................... 706 Database unloading tool ......................................................... 716 Creating an AdvancedDisk storage server ........................... 711 Moving the EMM server from a Windows cluster ...... 732 Disk failure ......................... 706 nbdb_backup.................................. hardware........................................................................................................................................................................................................... 723 Managing disk pools ...................................... 730 Obtaining storage server status ......................................... 718 Creating a storage unit ..........

...............................................................................................743 NearStore server ........................................................................................................................743 Properties button .....................743 Enable block sharing and and file system export ....................749 Failover examples ..................................................................................................736 NearStore disk storage unit advantages .....745 File system full conditions ..........................................................759 In the PureDisk environment .............................................742 On demand only ................................................................................756 Regarding disk full conditions .........................................................................................................................................................................................................................................743 Enable file system export ....29 NearStore and SnapVault considerations ..................742 Disk type ....................................................................................................................................................................................................................................750 Example 1 ....743 Absolute pathname to volume .......................750 Example 2 ...............................747 Initial configuration ........................................................................................................................................756 Regarding the file system export mode ........760 Exporting PureDisk data ....................................................................................744 Temporary staging area ......................745 End of media detection on disk staging storage units ....................................742 Storage unit type .......................................................................................................745 Disk consumption ................................................................................................760 Requirements to restore .........................757 Appendix D Exporting PureDisk data to NetBackup Required software and licenses .......................................................................................738 NearStore configuration ..............................................737 Restrictions in the current release .............739 NearStore authentication ........................................................................748 General failover configuration ...............................744 Reduce fragment size .............................................................................................................759 In the NetBackup environment .......................744 Image mode ........760 .....................................................................................................................................................................760 Create a PureDisk export policy ..................................739 NearStore disk storage unit properties ............................................................745 Using the NearStore disk storage unit for more than one purpose ..........................................................753 Troubleshooting .........................................................................................................745 Viewing the backup image .................................743 Enable block sharing .........................................746 Disaster recovery using volume SnapMirror on NearStore disk storage units 747 Overview of disaster recovery scenarios ...................................................................................................................................................................................................................................756 Licensing and permissions .........

............ 761 Restoring PureDisk data .......30 Create a NetBackup DataStore type policy ................................. 764 Index 765 ............................................................................................................................. 762 Logging information ................

Full backups back up all client files. the interfaces available. Linux. and optimize network traffic during off-peak hours. NetBackup administrators can set up periodic or calendar-based schedules to perform automatic. and the distributed architecture of NetBackup. flexible data protection solution for a variety of platforms. This chapter contains the following sections: ■ ■ ■ ■ ■ “Overview” on page 31 “NetBackup administration interfaces” on page 34 “Using the NetBackup Administration Console” on page 38 “How to configure NetBackup” on page 44 “Online documents” on page 46 Overview NetBackup provides a complete. This manual describes NetBackup configuration options—what they are and how each can be used to benefit the backup needs of your environment. Incremental backups back up only the files that have changed since the last backup. This manual is organized to reflect the arrangement of the NetBackup Administration Console. unattended backups for clients across a network. and NetWare systems. The platforms include Microsoft Windows. . This chapter provides an introduction to NetBackup software. The backups can be full or incremental.Chapter 1 Introduction The NetBackup Administrator’s Guide. UNIX. Volume I describes the core NetBackup product. An administrator can carefully schedule backups to achieve systematic and complete backups over a period of time.

then deletes it from the local disk if the backup is successful. Media servers provide additional storage by allowing NetBackup to use the storage devices that are attached to them. The master server is responsible for media and device selection for NetBackup. and restores. The catalog contains the internal databases that contain information about NetBackup backups and configuration.32 Introduction Overview The NetBackup administrator can allow users to backup. the master server contains the NetBackup catalog. restore. Typically.) 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.) 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. Media servers can also increase ■ . or archive the files from their computer. (An archive operation backs up a file. archives.

NetBackup finds the selected files and directories and restores them to the disk on the client. storage servers (when performing I/O directly to disk). external disk devices like OpenStorage appliances). users can browse. the client sends backup data across the network to a NetBackup server.Introduction Overview 33 performance by distributing the network load. During a restore. Media servers can also be referred to using the following terms: ■ ■ ■ device hosts (when tape devices are present). During a backup or archive. The NetBackup server manages the type of storage that is specified in the backup policy. then select the files and directories to recover. . or data movers (when sending data to independent.

NetBackup-Java Console for both Windows and UNIX. The NetBackup-Java Windows Display Console is not automatically installed on the system. Installation is available on the main NetBackup for Windows installation screen. see “Using the Remote Administration Console” on page 643. Java Administration Console installation selection during installation Figure 1-2 The console can be run on a Java-capable UNIX platform.34 Introduction NetBackup administration interfaces NetBackup administration interfaces NetBackup provides two graphical-user interfaces through which the administrator can manage NetBackup: ■ ■ NetBackup Administration Console for Windows. No license is required to install the Remote Administration Console. For more information. You can install the Remote Administration Console on a Windows machine to administer or manage any remote NetBackup server—Windows or UNIX. then displayed back to a Windows system by using third-party X terminal emulation software. .

The NetBackup Administration Console is the starting point for administering NetBackup. if more than one administrator makes changes to the configuration. . the NetBackup Administration Console can be run on more than one server at one time. Note: If there is more than one NetBackup server. However.Introduction NetBackup administration interfaces 35 Figure 1-3 Remote Administration Console selection during installation Running the Windows-based NetBackup Administration Console The NetBackup Administration Console is installed with the NetBackup server software. The menus contain commands relevant to the selected node. Go to Start > Programs > Veritas NetBackup > NetBackup Administration Console. To start the NetBackup Administration Console 1 2 Log on to the Windows server or workstation as a member of the user group that is authorized for NetBackup administration. The NetBackup Administration Console appears. Click a node to display the information that is related to that node in the Details pane on the right. the results are unpredictable. The left pane in the console contains a node for each major area of NetBackup administration.

Indicate a remote server by using one of the following methods: ■ ■ Use the File > Change Server menu command.5. The login screen for the NetBackup Administration Console displays the host name. Administering remote servers In a site that contains multiple master servers. use a point-to-point (PPP) connection between the display console and other servers to perform remote administration. See the NetBackup Installation Guide for information about how to install the Windows Display Console. select Start > Programs > Veritas NetBackup > NetBackup-Java Version 6. To start the Windows display console 1 On a Windows system where the Windows Display Console is installed and configured. Use the NetBackup-Java Administration Console. 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. Or. Click Login to log into the NetBackup-Java application server program on the specified server. The interface program continues to communicate through the server that is specified in the login screen for the remainder of the current session. The Windows Display Console can also be used to administer a NetBackup UNIX or Windows server. 2 3 4 Note: The default host is the last host that was successfully logged into. the systems can be configured so that one NetBackup Administrator Console can access remote servers. . The drop-down list contains the names of other hosts that have been logged into. Use the Windows Display Console to administer UNIX NetBackup servers where a Java-capable UNIX system is not available. select a host name from the drop-down list. Type your user name and password. Or. Indicate a remote system upon NetBackup login. Log into another server by typing the name of another host in the Host name field.36 Introduction NetBackup administration interfaces Running the Java-based Windows Display Console The NetBackup-Java Windows Display Console is provided with NetBackup software. the domain_name is not required. To log into a Windows server. If the host is not a member of a domain.

.Introduction NetBackup administration interfaces 37 For more information on remote administration. see “To administer a remote master server” on page 635.

Details pane Contains the configuration wizards and details specific to the utility that is selected. Media and Device Management Contains the utilities for managing the media and devices that NetBackup uses to store backups. storage units. to configure policies. The NetBackup Administration Console menus are described in the online help. All NetBackup commands are described in NetBackup Commands for Windows. Provides some control over the jobs.38 Introduction Using the NetBackup Administration Console Using the NetBackup Administration Console The NetBackup Administration Console provides a Windows-based interface through which the administrator can manage NetBackup. catalog backups. and client properties. media server. NetBackup Management Contains the utilities to create and view reports. NetBackup Administration Console Additional licensed utilities The nodes of other licensed utilities appear under the main NetBackup nodes. and a utility for configuring master server. . Access Management Contents of node are viewable only by a Security Administrator when NetBackup access control is configured. Activity Monitor Displays the NetBackup job information. Command prompts are used to perform some operations. Figure 1-4 Master Server The information in the NetBackup Administration Console applies to this server only.

Import Images Wizard ■ ■ ■ ■ ■ . For SharedDisk. the wizard discovers disk appliances and then you choose disk volumes within the appliance. The Getting Started Wizard is comprised of the following wizards. Disk Pool Configuration Wizard Use the Disk Pool Configuration Wizard to create pools of disk volumes for backup by one or more media servers. The wizard appears only if an Enterprise Disk Option license is installed. For AdvancedDisk. The wizard leads you through the necessary steps to a working NetBackup configuration. Backup Policy and Configuration Wizard Use the Backup Policy and Configuration Wizard to add a backup policy to your configuration. Volume Configuration Wizard Use the Volume Configuration Wizard to configure removable media to use for backups. 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. Catalog backups are essential to recover data in the case of a server failure or crash. you choose disk volumes directly attached to a media server. which can also be run separately. the wizard discovers disk arrays on the SAN and then you select pre-allocated logical unit numbers (LUNs). NetBackup Catalog Backup Wizard Use the NetBackup Catalog Backup Wizard to set up catalog backups. depending on what NetBackup utility is selected in the left portion of the screen. The wizard selection varies in the Details pane on the right. For OpenStorage. ■ Getting Started Wizard Use the Getting Started Wizard to configure NetBackup for the first time.Introduction Using the NetBackup Administration Console 39 NetBackup configuration wizards The easiest way to configure NetBackup is to use the configuration wizards.

40 Introduction Using the NetBackup Administration Console Use the Import Images Wizard to import NetBackup images in a two-part process. For example. services. Reports Use the Reports utility to compile information for to verify. processes. and troubleshoot NetBackup operations. both of which are configured within the Storage utility. hot catalog backup as the catalog backup type. “Activity Monitor” on page 47. see Chapter 3. see Chapter 2. NetBackup Management This manual describes the applications and the utilities that are listed under NetBackup Management in the NetBackup Administration Console tree. “Policies” on page 85. the backup policy specifies when automatic backups occur for the clients that are specified in the policy. The following sections describe the items that are found under NetBackup Management. and drives. A NetBackup client must belong to at least one backup policy to be backed up. manage. The backup policy also specifies whether users can perform their own backups and when. The administrator can define any number of backup policies. Use the Catalog Recovery Wizard only if the NetBackup environment was running the policy-based online. Policies Use the Policies utility to create and specify the backup policies that define the rules for backing up a group of clients. each of which can apply to one or more clients. For more information. For more information. ■ Catalog Recovery Wizard Use the Catalog Recovery Wizard in a disaster recovery situation. A storage unit can be part of a storage unit group as well as part of a storage lifecycle policy. For more information see Chapter 4. Activity Monitor Use the Activity Monitor utility to monitor and control NetBackup jobs. “Reports” on page 73. . Storage Use the Storage utility to display storage unit information and manage NetBackup storage units.

The administrator also selects the disk volumes that comprise the disk pool. or disk pool during the storage unit setup. For disk pool storage. NetBackup sends data to the storage unit that the backup policy specifies. Depending on disk type. hot catalog backup can also be used. For example. The media can be one of the following: ■ Removable (such as tape in a robot or a stand-alone drive). The administrator first configures the drives. During a backup. To create a storage unit. The administrator specifies the directory. and is configured with a wizard or through the Policies utility. the administrator selects a disk pool and (depending on the disk type) selects the media server(s) to move the data. either independent file systems or in an appliance). For the Enterprise Disk Options. NetBackup sends the data to that directory during backups. Disk (such as a file directory within a file system or a collection of disk volumes. Catalog Use the Catalog utility to create and configure a special type of backup NetBackup requires for its own internal databases—an offline. see Chapter 5. the administrator may have to define logon credentials for the storage itself. Media Manager is not involved. unit groups. NetBackup can use the other drive without administrator intervention. if a storage unit contains two drives and one is busy. 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. Note: Only storage units that point to shareable disk can specify more than one media server. cold catalog backup. and lifecycle policies” on page 209. the NetBackup policy points to a storage unit rather than to the individual devices it contains. NetBackup sends the data to the storage server (the host that writes to the storage).) These databases. called catalogs. “Storage units. During a backup. the administrator first defines the storage server and (depending on the disk type) its logon credentials. then defines the storage units. For BasicDisk. The catalogs contain information on every client . robots. ■ For more information.Introduction Using the NetBackup Administration Console 41 Storage units simplify administration because once defined. are located on the NetBackup master and media server (default location). volume. (An online. Media Manager picks a device to which the NetBackup client sends data. and media in NetBackup.

to manually expire backup images. For more information. “Device Monitor” on page 497. The Catalog utility is also used for the following actions: ■ ■ ■ ■ ■ to duplicate a backup image. Devices Use the Devices utility to add. “NetBackup Catalog” on page 271. Catalog backups are tracked separately from other backups to ensure recovery in case of a server crash. see Chapter 8. Media Use the Media utility to add and manage removable media.42 Introduction Using the NetBackup Administration Console backup. no changes are necessary. and manage storage devices. However. see Chapter 6. . device paths. to search for a backup image to verify the contents of the media with what is recorded in the NetBackup catalog. and service requests for operators. see Chapter 10. and clients. to promote a backup image from a copy to the primary backup copy. “Host properties” on page 355. For more information. Device Monitor Use the Device Monitor utility to manage drives. configure. For more information. For more information. “Media” on page 509. Media and Device Management The Media and Device Management utilities manage the media and the devices that NetBackup uses. Host Properties allows the administrator to customize NetBackup to meet specific site preferences and requirements for master servers. For more information. see Chapter 9. media servers. to import expired backup images or images from another NetBackup server. see Chapter 7. In most instances. Host Properties Use the Host Properties utility to customize NetBackup configuration options. “Devices” on page 593.

When certain utilities are selected. see the NetBackup Shared Storage Guide. See the online help for more information on Customize. Access Management NetBackup administrators can protect a NetBackup configuration by defining who may access NetBackup and what functions a user group can perform. . and manage log-in credentials for: ■ Disk array hosts (requires an Enterprise Disk Option license). Storage servers (requires an Enterprise Disk Option license). For more information about NDMP. see the NetBackup for NDMP Administrator’s Guide. Standard and user toolbars Upon opening the NetBackup Administration Console. the Customize command opens a dialog box with options to add more toolbars or buttons to existing toolbars. a standard toolbar appears by default.Introduction Using the NetBackup Administration Console 43 Credentials Use the Credentials utility to add. NDMP hosts (requires the Virtual Tape Option license). For example. Slowly drag the pointer over a button to display a button description label. ■ ■ Credentials appears only if one of the previously mentioned license keys is installed. The buttons on the toolbar provide shortcuts for menu commands. Access Management is enabled when Symantec Product Authentication and Authorization and NetBackup Access Control (NBAC) is installed and configured. For installation and configuration information. Customizing the administration console The View menu contains options for customizing the window to suit your preferences. see the NetBackup Shared Storage Guide. see Access Management in the NetBackup Security and Encryption Guide. For more information about the Enterprise Disk Options. and other commands on the View menu. For more information about disk array hosts and the SharedDisk disk type. Options. a user toolbar appears. This access control is configured by using the Access Management utility. remove.

44 Introduction Using LiveUpdate to distribute NetBackup updates Using LiveUpdate to distribute NetBackup updates NetBackup LiveUpdate provides a cross-platform. The LiveUpdate policy checks the versions or release updates on each client that is listed in the policy. a NetBackup environment must include one NetBackup LiveUpdate server and one or more NetBackup clients with the Symantec LiveUpdate agent software installed. you can use the wizards to configure the basic properties and then use the Administration Console to configure the more advanced properties. How to configure NetBackup The easiest way to configure NetBackup is to use the configuration wizards. the client file list is not checked. After you complete these wizards. and does not undergo the same pre-processing steps that are performed on backup policies. A LiveUpdate policy is considered a generic policy. Alternatively. This wizard invokes the following wizards: ■ ■ ■ ■ 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. the policy installs the NetBackup software that is available on the NetBackup LiveUpdate server. A NetBackup LiveUpdate server is specified during the NetBackup master server installation. see the NetBackup Installation Guide. To configure more advanced properties. Choose the Getting Started Wizard to configure NetBackup for the first time. . The Symantec LiveUpdate agent is installed when any NetBackup client. master server. The NetBackup LiveUpdate server stores NetBackup release updates to be distributed to the clients. To use LiveUpdate. you can use the NetBackup Administration Console. your NetBackup environment should back up clients and back up your NetBackup catalog. LiveUpdate appears on the File menu. policy-driven method to distribute NetBackup release updates to NetBackup 6. or administration console is installed. Release updates are distributed to clients when a LiveUpdate policy is run. media server.5 clients. You also can use the Administration Console if you prefer not to use the wizards. For installation information. For example. Then.

Check the log on the client to see if the operations were successful. either wait until the schedules are due or run the schedules manually from the master server. if necessary. (See “NetBackup administration interfaces” on page 34. A storage unit is one or more storage devices of a specific type (tape or disk) that attach to a NetBackup server. The NetBackup catalogs contain configuration information as well as critical information on client backups. if needed. b .) Use the Media utility to add removable media in the NetBackup Administration Console. (See “Policies” on page 85. restore the same files. (See “Changing host properties” on page 357. (See “Devices” on page 593. check the Backup Status report to ensure that the backups completed successfully for all clients.) 13 Test the configuration as follows: a If you created user-directed backup or archive schedules.) Use the Devices utility to add and configure the storage devices. see “Creating a storage unit” on page 213. To configure NetBackup without wizards 5 6 7 8 Start the NetBackup Administration Console. In most instances. If the backup was successful.) Ensure that all services are active on the NetBackup master server (and Enterprise Media Manager server.) Configure the storage units. (See “NetBackup Catalog” on page 271. ■ 9 For an overview of NetBackup storage units.) 12 Customize host properties to meet site preferences. unit groups. see “Storage units. if the EMM server is not the master server).) 11 Configure the backup policies for the clients to be backed up. For instructions about how to add storage units. (See “Media” on page 509.(See “Services tab” on page 57. After the automatic schedules have run. the NetBackup defaults provide satisfactory results.Introduction How to configure NetBackup 45 The following steps explain how to configure NetBackup by using the NetBackup Administration Console. and lifecycle policies” on page 209. test the schedules by performing a backup or archive from a client. Each step provides references for more information. ■ 10 Configure a NetBackup catalog backup. To test the automatic backup schedules.

see the Related Documents appendix in the NetBackup Release Notes. These online documents are in Adobe® Portable Document Format (PDF). you must use the Adobe Acrobat Reader. For a complete list of NetBackup technical documents. You can download the reader from: http://www.46 Introduction Online documents For instructions about how to perform a manual backup of a NetBackup policy. To view PDF documents. Contact your NetBackup administrator to obtain the location of this CD or to have the files installed on your computer. .com Symantec assumes no responsibility for the installation and use of the reader. see “Performing manual backups” on page 197.adobe. Online documents NetBackup documents are delivered on a documentation CD that is included with the NetBackup media kit.

services. and drives. processes. ■ ■ ■ ■ ■ ■ ■ ■ “Introduction to the Activity Monitor” on page 48 “Activity Monitor topology” on page 52 “Jobs tab” on page 55 “Services tab” on page 57 “Processes tab” on page 62 “Drives tab” on page 67 “Media mount errors” on page 69 “Managing the jobs database” on page 69 .Chapter 2 Activity Monitor This chapter explains how to use the NetBackup Activity Monitor to perform various functions to monitor and troubleshoot NetBackup jobs.

processes.48 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. Figure 2-1 Menu bar Standard toolbar Current master server User toolbar Activity Monitor Topology Status bar Details pane Four tabs Right-click in the Details pane to view the shortcut menu Click ? to display help for the topology view . and drives. services.

Select Actions > Details. Select the job(s) for which you want to view details. Then. ■ ■ Select the Show Column button to display the heading. the jobs that were started before a specific date. To delete completed jobs 1 2 Open the Activity Monitor and select the Jobs tab. For example. select the column head. The Set Column Layout dialog box appears. . A Jobs Details dialog box appears for each job you selected. 4 To change the order in which the columns appear. Click OK to apply the changes. The following sections describe the common Activity Monitor operations that use the menu options: To show or hide column heads 1 Open the Activity Monitor. Select the Hide Column button if you do not want to see the column head. click the Move Up button or the Move Down button to reorder the columns. Note: The Filter option on the View menu is useful for displaying in Activity Monitor only those jobs with specified characteristics. jobs with status completion codes within a specified range. jobs in the queued state. Select the job(s) you want to delete. 5 To monitor the detailed status of selected jobs 1 2 3 Open the Activity Monitor and select the Jobs tab.Activity Monitor Introduction to the Activity Monitor 49 Activity Monitor menu bar The options on the Activity Monitor menu bar are described in the online help. Select the heading you want to display or hide. 2 3 Click View > Columns > Layout.

. Select Actions > Resume Job. To cancel all jobs in the jobs list that have not completed. Select Actions > Cancel Job. All selected jobs are suspended. all the children of that parent job are canceled as well. If the selected job is a parent job. Active. or Suspended state. To cancel a job that has not completed 1 2 Open the Activity Monitor and select the Jobs tab. Re-Queued. It may be a job that is in the Queued. The job details for the original job will reference the job ID of the new job. All selected jobs are resumed. Select Actions > Restart Job. All selected jobs are canceled. Select the job you want to suspend. 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. 3 4 5 To restart a completed job 1 2 3 Open the Activity Monitor and select the Jobs tab. To resume a suspended or an incomplete job 1 2 3 Open the Activity Monitor and select the Jobs tab. Incomplete. Select the Done job you want to restart. Select the job that has not completed that you would like to cancel. click Actions > Cancel All Jobs. All selected jobs are restarted. To suspend a restore or backup job 1 2 3 Open the Activity Monitor and select the Jobs tab. Select Actions > Suspend Job. In this case. a new job ID is created for the job. Note: Only the backups and the restores that contain checkpoints can be suspended. In most cases. a canceled child job cancels only that job and allows the other child jobs to continue.50 Activity Monitor Introduction to the Activity Monitor 3 Select Edit > Delete. Select the suspended or the incomplete job you want to resume. All selected jobs are deleted.

In the Job Details dialog box.Activity Monitor Introduction to the Activity Monitor 51 Note: Only the backups and the restores that contain checkpoints can be suspended. The Troubleshooter helps explain the problem and provides the corrective actions that are based on the NetBackup status code that the job returns. If no job is selected. an Excel document). Select File > Print. To print job detail information from a single job 1 2 3 Open the Activity Monitor and select the Jobs tab. use the Troubleshooter on the Help menu. all jobs are printed. Hold down the Control or Shift key to select multiple jobs. Job detail printout Figure 2-2 To copy Activity Monitor text to another document 1 2 3 Open the Activity Monitor and select a job. click Print. Paste the selected text into the file (for example. Select Edit > Copy. If a job fails. . Select a job to print. Double-click on a job to open it. then select a printer and set the printer options. To print job detail information from a list of jobs 1 1 2 Open the Activity Monitor and select the Jobs tab.

Activity Monitor topology The Activity Monitor topology view displays the state and configuration of the entire NetBackup system being administered. and Done. If there is no status code entered in the Troubleshooter status code field. An explanation of the problem is displayed on the Problems tab and a recommended action appears on the Troubleshoot tab.52 Activity Monitor Activity Monitor topology To run troubleshooter within the Activity Monitor 1 2 Select a job in the Activity Monitor. depending on which tab is currently selected: ■ ■ ■ The master server on which the jobs reside. Waiting for Retry. Open the job details for a job. even when the filter is used. enter the status code of the failed job. The number of jobs in each of the job states: Active. Status bar The status bar appears at the top of the Activity Monitor list and displays the following information. Incomplete. If a device host . You can open the Troubleshooter at any time and enter a status code. ■ ■ ■ The numbers always reflect the actual number of jobs. 3 The Troubleshooter dialog box appears. The Activity Monitor displays only robots and the drives that have storage units configured. The number of jobs currently selected. The number of drives and the state of each (Active. The total number of jobs. Down). Then click Troubleshooter. Queued. Open the Troubleshooter: ■ ■ ■ Click the Troubleshooter icon. Click Lookup to locate the troubleshooting information. The number of NetBackup services that run. Suspended. Select Help > Troubleshooter. click the Detailed Status tab.

and drive state status. media servers. job failures. the services that are down. Master server Media server The topology view shows master servers. The view displays backup and restore activity. The following figures represent some of the icons you may see in the Activity Monitor. and NetBackup storage unit devices. the device host is not displayed in the Activity Monitor either. clients.Activity Monitor Activity Monitor topology 53 has no configured devices. and job failures Topology connections The topology view displays the physical and the logical connections between devices. restore. . For more information. click the ? in the topology view. Backup on client Restore on client Client with a failed job Failed backup or restore on client Master server backup Host backup and restore Media server with services down Master server with backup.

54 Activity Monitor Activity Monitor topology Lines appear between a drive in use and the server that uses it. lines appear between a media server and a device that runs a job for the server. Drives that are physically located in a robot display directly beneath the robot. Select an object to highlight the connecting lines from the object to all other objects to which it is connected. . Robot arm Robot media Shared drive Robots and drives are represented as connected to a media server. You cannot select the topology objects that are not alike. Select an Activity Monitor tab to select different views of your configuration. To select multiple objects of the same type. For example. Selecting topology objects To select an object in the topology pane is one method to filter the contents of the Activity Monitor list. press the Ctrl key and select another object. For example. media. click a server to highlight all attached robots. and drives configured to the server. Stand-alone drives are represented as individual drive objects.

Parent jobs display a dash (-) in the Schedule column. Parent jobs For some backup jobs. cold catalog backups: The parent job initiates the bpbackupdb as a child job. Note: Job selection preference is given to jobs from NetBackup 6.) Children jobs are not created if the Snapshot Client settings are configured to retain snapshots for Instant Recovery. then initiates the backup as a child job. Children jobs are created if the Snapshot Client settings are configured to retain snapshots for Instant Recovery. (Snapshots and copy snapshots to a storage unit is selected in the policy Schedule Attributes tab.and post-processing. If multistreaming and BMR are used together. and deletes the snapshot when complete. (Snapshots only is selected in the policy Schedule Attributes tab. hot catalog backups: The parent job for hot catalog backups works with bpdbm to initiate multiple children backup jobs: a Sybase backup.) Bare Metal Restore: The parent job runs brmsavecfg. a file system backup of the master. depending on the backup environment: ■ Snapshot Client: The parent job creates the snapshot. Offline. the snapshot is not backed up to a storage unit. a parent job is used to perform pre. Online.x media servers and BMR database. That is. and backups of any 5. the parent job may start multiple children jobs. initiates children jobs. Multiple copies: ■ ■ ■ ■ . The tasks vary. PARENT_END_NOTIFY) from the master server: Install_path\VERITAS\NetBackup\bin The role of the parent job is to initiate requested tasks in the form of children jobs.Activity Monitor Jobs tab 55 Jobs tab The Jobs tab displays all jobs that are in process or have been completed for the master server currently selected. so no children jobs are generated. but to create snapshots only. A parent job runs the start and end notify scripts (PARENT_START_NOTIFY.0 media servers over media servers of previous versions. then copy snapshots to a storage unit.

If multiple data streams are enabled. . Only the parent job (and subsequently all the children jobs) can be restarted. some children jobs may be split into multiple streams. SharePoint: The parent job runs a resolver process during which children jobs are started. ■ Multiple data streams: The parent job performs stream discovery and initiates children jobs.56 Activity Monitor Jobs tab A multiple copies job produces one parent job and multiple child jobs. The children jobs display the ID of the parent job in the Activity Monitor. The duplicates do not appear as children jobs in the Activity Monitor. Child jobs that are part of a multiple copies parent job cannot be restarted individually. Then. The Job Details dialog box appears that contains detailed job information on two tabs: a Job Overview tab and a Detailed Status tab. For setup information. the Vault profile starts the duplicates as jobs. Instead. a dash (-) is displayed for the schedule because the parent schedule is not used and the children schedules may be different. see “Multiple copies” on page 137. A parent job does not display a schedule in the Activity Monitor. double-click on the job in the Jobs tab. Click View > Columns > Layout to show or hide columns. This process is similar to the stream discovery for multiple data streams. Not all columns are displayed by default. Vault: The parent job starts the Vault profile. ■ ■ To view job details To view the details for a specific job.

Not all columns are displayed by default. Click View > Columns > Layout to show or hide columns. NetBackup Bare Metal Restore Master Server (bmrd. the other machine must be running on a Microsoft platform. This service must be running on the NetBackup Enterprise Media Manager server during all normal NetBackup operations. The user must be authenticated on the Microsoft platform. Appears if Bare Metal Restore is installed. Table 2-1 Service NetBackup services Description Adaptive Server Anywhere ­ dbsrv9.Activity Monitor Services tab 57 Services tab The Services tab displays the status of NetBackup services on the master server and all media servers that the selected master server uses. Figure 2-3 Services tab in the Activity Monitor Note: To see any services or processes on another machine.exe) .exe Manages the NetBackup relational database.

Manages the NetBackup internal databases and catalogs. The log notes that the account name is invalid.58 Activity Monitor Services tab Table 2-1 Service NetBackup services Description NetBackup Client Service (bpinetd. If it were stopped.exe) NetBackup Device Manager (ltid. and any robotic processes. When NetBackup tries to contact the Client Service.exe) Listens for connections from NetBackup servers in the network and when an authorized connection is made. Runs on the same system as the NetBackup Enterprise Media Manager.exe) NetBackup Database Manager (bpdbm. starts the necessary NetBackup process to service the connection. the console could not display the data. Starts the Volume Manager (vmd). If it were stopped.exe) Service that is used to communicate with legacy NetBackup services.db). a message displays that states the service didn’t start because of improper login information. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console. Processes the requests to mount and dismount tapes in robotically controlled devices through the robotic control processes. Accesses and manages the database where media and device configuration information is stored (EMM_DATA. . NetBackup Compatibility Service (bpcompatd. does not exist. NetBackup Enterprise Media Manager (nbemm. Note: The Client Service must be run as either an Administrator or Local System account.exe) Provides the communication infrastructure to pass information and events between distributed NetBackup components. the console could not display the data.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. nbemm. The event is recorded in the Windows System event log.exe) NetBackup Event Managert Service (nbevtmgr. BPDBM must be running on the NetBackup master server during all normal NetBackup operations. or that the password is invalid. Mounts the volumes on the tape or optical storage devices in response to user requests. the automatic volume recognition process (avrd). Problems arise if the Client Service login account differs from the user that is logged on to use NetBackup.

nbrb works with the Enterprise Media Manager (NBEMM). tape drives. NetBackup Remote Manager and Monitor Service (nbrmms. If a policy is modified or if an image expires.exe) NetBackup Request Manager (bprd.exe) Accepts the jobs that the Policy Execution Manager (nbpem. and client reservations for jobs.exe) NetBackup Service Layer (nbsl.x servers and monitors the status of drives that are attached to NetBackup 5. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console.exe) NetBackup Service Monitor (nbsvcmon.x servers.x servers are present in the configuration.exe) NetBackup Resource Broker (nbrb. Runs on NetBackup media servers. NBSL is required to run NetBackup Operations Manager (NOM). Facilitates the communication between the NetBackup graphical user interface and NetBackup logic. The Job Manager then starts the job. If it were stopped.exe) Compiles the worklist for jobs and determines when jobs are due to run.exe) Monitors the NetBackup services that run on the local machine. If nbsvcmon determines that NetBackup is configured for a cluster. . and informs nbpem. bprd must be running on the NetBackup master server to perform any backups or restores. an application that manages and monitors multiple NetBackup environments. Processes the requests from NetBackup clients and servers. Discovers and monitors disk storage on NetBackup media servers.Activity Monitor Services tab 59 Table 2-1 Service NetBackup services Description NetBackup Job Manager (nbjm.exe) submits and acquires the necessary resources. this service tries to restart the terminated service. bprd also prompts NetBackup to perform automatically scheduled backups. If a service unexpectedly terminates. nbpem is notified and the worklist is recompiled. NetBackup Status Collection Service (vmscd. the console could not display the data. This service cannot be stopped from the Activity Monitor because it receives data that is displayed in the Administration Console. the console could not display the data.exe) 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.exe that the job is completed. and manages Fibre Transport (FT) connections on media servers and clients for the NetBackup SAN Client option. Also discovers. NetBackup Policy Execution Manager (nbpem. Allocates the storage units. the service shuts down and the monitoring is taken over by the cluster. If it were stopped. vmscd maintains a persistent connection with NetBackup 5. monitors.

Service name: VRTSpbx. Multiprocess stand-alone services: NetBackup services that “fork” a child process to handle requests.exe) clients outside the firewall that connect to Symantec product services. and forms the basis for authorization and access control in Symantec applications. Manages the volumes (tapes) needed for backup or restore and starts local device management daemons and processes. and vmd.exe) NetBackup Volume Manager (vmd. More about services Stand-alone services: These NetBackup services always run and listen to accept connections. identities. bprd. bpjobd.exe) The NetBackup Storage Lifecycle Manager manages lifecycle operations including duplication. NetBackup Vault Manager (nbvault. NBVAULT must be running on the NetBackup Vault server during all NetBackup Vault operations. inetd services: NetBackup services usually launched by inetd(1m) or bpinetd. Single-process stand-alone services: NetBackup services that accept connections and handle requests in the same process. Examples include bpcd. Service name: VRTSat. Examples include bpdbm and bprd. bpjava-msvc. Examples include bpdbm. Other Symantec services Several services do not appear in the Activity Monitor. and image expiration.exe) Manages NetBackup Vault.60 Activity Monitor Services tab Table 2-1 Service NetBackup services Description NetBackup Storage Lifecycle Manager (nbstserv.exe) The Symantec Product Authentication Service validates. Table 2-2 Service Symantec services Description Symantec Private Branch Exchange The Symantec Private Branch Exchange provides single-port access to (pbx_exchange. Symantec Product Authentication Service (vxat. . and vnetd. staging.

Double-click a service from the service list to view a detailed status. To view the details of a service. click Help in the Service Details dialog box. Select Actions > Stop Selected or Actions > Start Selected. For a description of the service details.exe) To monitor NetBackup services 1 2 Open the Activity Monitor and select the Services tab.Activity Monitor Services tab 61 Table 2-2 Service Symantec services Description The Symantec Product Authorization Service provides access control in Symantec applications. Note: To start or stop services requires the necessary permissions on the system where the service is running. double-click the process in the Services tab. . To view the status of the previous service or the next service. click the up or down arrow. To start or stop a service 1 2 3 Open the Activity Monitor and select the Services tab. Service name: VRTSaz. A Service Details dialog box appears for the service you selected. Symantec Product Authorization Service (vxazd. Select the service(s) you want to start or stop.

62 Activity Monitor Processes tab Processes tab The Processes tab displays the NetBackup processes that run on the master server. The NetBackup Client daemon. On Windows. the software causes the port number in the services file to be updated as well. the system must be a Microsoft platform and the user must be authenticated on the Microsoft platform. The process for the NetBackup Database Manager service. NetBackup has a specific configuration parameter for bpcd: if the port number is changed within the NetBackup configuration. Not all columns are displayed by default. The process allows NetBackup to read labeled tape and optical disk volumes and assign the associated removable media requests to drives. Note: To view services on another system. avrd bmrd 8362 13782 The process for the NetBackup Bare Metal Restore Master Server service. The Automatic Volume Recognition process handles automatic volume recognition and label scans. It provides a listening service for connection requests. this process issues requests to and from the master server and the media server to start programs on remote hosts. On UNIX clients.exe. 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. bpdbm bpinetd The process for the NetBackup Client service. . bpcd can only be run in stand-alone mode. bpcd bpcompatd 13721 The process for the NetBackup Compatibility service. bpcd always runs under the supervision of bpinetd. It responds to queries that are related to the NetBackup catalog. Click View > Columns > Layout to show or hide columns.

The NetBackup Administration Console on the Windows platform. the software causes the port number in the services file to be updated as well. migrd NBConsole nbemm nbEvtMgr The process for the NetBackup Event Manager service. nbfdrv64 It controls the Fibre Transport target mode drivers on the media server. It accesses and manages the database where media and device configuration information is stored (EMM_DATA. It creates and manages event channels and objects for communication among NetBackup daemon. The VSM request daemon (database request management) for Storage Migrator. It runs on media servers configured for NetBackup Fibre Transport. this process queries and updates the jobs database. The process for the NetBackup Enterprise Media Manager service. bpjava-susvc bpjobd 13723 The NetBackup Jobs Database Management daemon. The NetBackup-Java application server user service program on NetBackup servers. . 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. The process for the NetBackup Request Manager service. nbemm. It starts the automatic backup of clients and responds to client requests for file restores and user backups and archives. bpinetd starts the program during startup of the NetBackup-Java GUI applications and authenticates the user that started the NetBackup-Java GUI application.db). bprd 13720 ltid 13699 The process for the NetBackup Device Manager service. bpjava-msvc starts the program upon successful login with the NetBackup-Java applications login dialog box. The Event Manager daemon runs with the Enterprise Media Manager (nbemm) only on master servers. migrd handles communication for VSM-Java and commands.Activity Monitor Processes tab 63 Table 2-3 Process bpjava-msvc NetBackup processes Port 13722 Description The NetBackup-Java application server authentication service program.exe must be running in order for jobs to run. NetBackup has a specific configuration parameter for bprd: if the port number is changed within the NetBackup configuration.

manages data buffers. Manages storage lifecycle policy operations and schedules duplication jobs. NDMP servers are designed to adhere to this protocol and listen on port 10000 for NDMP clients to connect to them. the process for the NetBackup Vault Manager service. nbsvcmon attempts to restart the terminated service. nbsl facilitates the communication between the graphical user interface and NetBackup logic. This process allocates storage units. The process for the NetBackup Remote Manager and Monitor service. nbrb nbrmms nbsl nbstserv The process for the NetBackup Storage Lifecycle Manager. The process for the NetBackup Service Layer service. It compiles the worklist for jobs and determines when jobs are due to run. nbjm nbpem The process for the NetBackup Policy Execution Manager service. If Vault is installed. The Job Manager then starts the job. It accepts the jobs that the Policy Execution Manager (NBPEM) submits and acquires the necessary resources. and client reservations for jobs. and informs nbpem that the job is completed. The process for the NetBackup Service Monitor. Enables NetBackup to remotely manage and monitor resources on a system that are used for backup (or affected by backup activity). 10000 NDMP is the acronym for Network Data Management Protocol. nbsvcmon nbvault ndmp . When a service unexpectedly terminates. nbproxy This process that safely allows new multi-threaded NetBackup processes to use existing multi-threaded unsafe libraries. If a policy is modified or if an image expires. The process for the NetBackup Job Manager service. NBPEM is notified and the worklist is recompiled. tape drives. Monitors the NetBackup services. It does the following for the server side of the FT connection: controls data flow.64 Activity Monitor Processes tab Table 2-3 Process nbftsrvr NetBackup processes Port Description The Fibre Transport (FT) server process that runs on media servers configured for NetBackup Fibre Transport. processes SCSI commands. and manages the target mode driver for the host bus adaptors. nbrb works with the Enterprise Media Manager (NBEMM). Monitors disk capacity on capacity managed volumes and removes older images when required.

tlhd tlhcd 13717 The tlhd process runs on each NetBackup server that manages a drive in a Tape Library Half-inch. 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. tlmd 13716 The tlmd Tape Library Multimedia (TLM) daemon runs on a NetBackup server. The tl8d process runs on a NetBackup media server that manages a drive in a Tape Library 8MM. . and sends these requests to the robotic-control process tldcd.Activity Monitor Processes tab 65 Table 2-3 Process odld NetBackup processes Port 13706 Description The odld (Optical Disk Library) daemon runs on the host that has an optical disk library. The NetBackup Volume Manager (vmd) starts the oprd operator request daemon. unmount. This process receives NetBackup Device Manager requests to mount and unmount volumes and communicates these requests to the robotics through SCSI interfaces. This process receives requests to mount and unmount volumes and communicates the requests to the NetBackup Device Manager ltid. tl8cd runs on the NetBackup server that provides the robotic control. and sends these requests to the robotic-control process tl8cd. The NetBackup Device Manager communicates the requests to the robotics through SCSI interfaces. and robot inventory requests to a NetBackup media server that hosts ADIC DAS/SDLC software and controls the TLM robotics. The tlhcd process runs on the NetBackup server that provides the robotic control and communicates with the TLH robotics through SCSI interfaces. tldcd runs on the NetBackup server that provides the robotic control. The tldcd process communicates with the Tape Library DLT robotics through SCSI interfaces. This process receives NetBackup Device Manager requests to mount and unmount volumes. It communicates mount. This process receives NetBackup Device Manager requests to mount and unmount volumes and communicates these requests to the robotics through SCSI interfaces. This process receives NetBackup Device Manager requests to mount and unmount volumes and sends these requests to the robotic-control process tlhcd. The tl8cd process communicates with the TL8 robotics through SCSI interfaces. oprd tl4d 13713 The tl4d process runs on the host that has a Tape Library 4MM. To share the tape library. To share the tape library.

. and forms the basis for authorization and access. NetBackup services that were introduced in NetBackup 6. The Veritas Authentication Service validates. click Help in the Process Details dialog box.0 use the vnetd port number. For a description of the process details. Veritas Network Daemon allows all socket communication to take place while connecting to a single port. The tshd process receives requests to mount and unmount volumes or for robot inventory and communicates these requests to the robotics through SCSI interfaces. The Symantec Private Branch Exchange allows all socket communication to take place while connecting through a single port. The Veritas Authorization Service verifies that an identity has permission to perform a specific task.0 use the veritas_pbx port number. double-click the process in the Processes tab. vmd 13701 13724 vnetd vrts-auth-port 4032 vrts-at-port 2821 veritas_pbx 1556 Monitoring NetBackup processes To view the details for a process.66 Activity Monitor Processes tab Table 2-3 Process tshd NetBackup processes Port 13715 Description The tshd process runs on a NetBackup server that has a Tape Stacker Half-inch. Legacy NetBackup services that were introduced before NetBackup 6. The process for the NetBackup Volume Manager service. identifies.

see “Cleaning drives” on page 504. or if there are multiple paths to a drive configured. Drives pane Drives Paths pane The Drives Paths pane displays if a drive is configured as a shared drive. Drive cleaning functions For instructions on how to add and specify a cleaning tape as the media type. The Drive Paths pane lists path information for drives. .Activity Monitor Drives tab 67 Drives tab The Drives tab displays the status of NetBackup drives on the master server being monitored. Note: Drive cleaning functions can also be performed from the Device Monitor.

■ Clean Now: Start an operator-initiated cleaning of the selected drive. Then. Reset Mount Time: Reset the mount time for the selected drive to zero. ■ ■ 4 Updated drive cleaning information is presented in the Drive Details dialog box. Select Actions > Drive Cleaning. Use Reset Mount Time to reset the mount time after doing a manual cleaning of a drive. it must contain a cleaning tape for a mount request to be issued. Clean Now resets the mount time to zero. .68 Activity Monitor Drives tab To perform drive cleaning functions 1 2 3 In the NetBackup Administration Console. Set Cleaning Frequency: Set the number of mount hours between drive cleanings. but the cleaning frequency value remains the same. Select the drive that you want to clean. regardless of the cleaning frequency or accumulated mount time. If the drive is a stand-alone drive. select the Drives tab in the Details pane. select Activity Monitor.

The requested media is in an offline ACS LSM (Automated Cartridge System Library Storage Module). When a media mount is canceled. The following conditions can lead to automatic media reselection: ■ ■ ■ ■ ■ The requested media is in a DOWN drive.Activity Monitor Media mount errors 69 Media mount errors When media is mounted for NetBackup jobs. A queued mount request leads to one of the following actions: ■ ■ ■ The mount request is suspended until the condition is resolved. Queued media mount errors When the mount request is queued. or it is cancelled. . Depending on the type of error that is encountered. The requested media is in a drive not accessible to the media server. (Selection applies only in the case of backup requests. (ACS robot type only. the request queues. NetBackup tries to select other media to use for backups. The operator denies the request.) The requested media has an unreadable barcode. The media mount timeout is reached. Canceled media mount errors When a mount request is automatically canceled.) The requested media has been otherwise determined to be unmountable. an operator-pending action is created and is displayed in the Device Monitor.) Many conditions lead to a mount request being automatically canceled instead of queued. (ACS robot type only. different media is selected so that the backup is not held up. ■ ■ ■ Managing the jobs database NetBackup uses the install_path\NetBackup\bin\admincmd\bpdbjobs -clean command to delete done jobs periodically. errors can occur. The requested media is misplaced.) The requested media is in an ACS that is not accessible. The requested media is write-protected. (ACS robot type only.

If the KEEP_JOBS_SUCCESSFUL_HOURS value is greater than 0 but less ■ ■ ■ . The retention period values are measured against the time the job ended. For example: install_path\VERITAS\NetBackup\bin\admincmd\ echo KEEP_JOBS_HOURS = 192 | bpsetconfig Where 192 is the number of hours that unsuccessful jobs are kept in the jobs database or Activity Monitor display. Retaining job information in the database You may want to keep jobs in the jobs database longer than the default of three days. For example. The process starts the first time bprd wakes up after midnight. run: echo KEEP_JOBS_SUCCESSFUL_HOURS = 192 | bpsetconfig 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. use the following method to add new registry key(s) to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\ CurrentVersion\Config To add the key(s) safely. the bpdbjobs process retains more recent done jobs until the three-day retention period expires. If KEEP_JOBS_SUCCESSFUL_HOURS is set to 0. If the bprd NetBackup request daemon is active. bpjobd uses the KEEP_JOBS_HOURS bpdbjobs value instead for successful jobs. The automatic startups occur regardless of whether you choose to run bpdbjobs at other times by using cron or alternate methods. bpdbjobs sets KEEP_JOBS_SUCCESSFUL_HOURS to equal KEEP_JOBS_HOURS. Information about successful jobs cannot be kept longer than information about unsuccessful jobs. If KEEP_JOBS_SUCCESSFUL_HOURS is greater than KEEP_JOBS_HOURS.70 Activity Monitor Managing the jobs database By default. bprd starts the bpdbjobs process automatically when it performs other cleanup tasks. run the following commands. By default. the bpdbjobs process deletes all the done jobs that are more than three days old. Changing the default on a permanent basis To change the default values on a permanent basis.

Default: 3 days. The number of hours can range from 3 to 720 but must be less than or equal to keep_hours. BPDBJOBS_OPTIONS environment variable The BPDBJOBS_OPTIONS environment variable provides a convenient method to set job retention options with a script. If present. NetBackup was installed in the default location: set BPDBJOBS_OPTIONS= -keep_hours 24 -keep_successful_hours 5 C:\progra~1\VERITAS\NetBackup\bin\admincmd\bpdbjobs -clean ■ The .bat) was used in the following example. Default: 72 hours. keep_successful_days days Use with the -clean option to specify how many days bpdbjobs keeps successful done jobs. as long as it is run from the appropriate directory. Default: 72 hours. KEEP_JOBS_HOURS is used for unsuccessful jobs only. The bpdbjobs process determines how long to retain a job by checking for the BPDBJOBS_OPTIONS environment variable. In this example. 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. The following options can be used to determine the length of time NetBackup retains jobs.bat file can be stored anywhere. 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 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. Default: 3 days.Activity Monitor Managing the jobs database 71 than KEEP_JOBS_HOURS. BPDBJOBS_OPTIONS overrides the registry key settings. This value must be less than the -keep_days value. then changed as needed.bat file. To keep both successful and both failed jobs longer than the default of 72 hours. -keep_days days Use with the -clean option to specify how many days bpdbjobs keeps done jobs. ■ ■ ■ A batch file (cleanjobs. The correct location of bpdbjobs must be indicated in the . The script can be copied directly from this document. Values outside the range are ignored.

72 Activity Monitor Managing the jobs database In the following example.bat in C:\Program Files\VERITAS\NetBackup. bpdbjobs debug log If you need detailed information on bpdbjobs activities. The following is a screen capture of cleanjobs. enable the bpdbjobs debug log by creating the following directory: install_path\NetBackup\logs\bpdbjobs Note: Before you use a debug log. bpdbjobs -clean -keep_hours 720 For a complete description of the bpdbjobs command. read the guidelines in the Debug Logs section of the NetBackup Troubleshooting Guide for UNIX and Windows. . the administrator has created and stored cleanjobs. The command line options supersede all other job retention instructions. see NetBackup Commands for Windows. 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.bat being run: bpdbjobs command line options The bpdbjobs command interacts with the jobs database to delete or move done job files. the following command deletes unsuccessful jobs older than 720 hours.

The reports serve to verify. client backups. NetBackup reports display information according to job status. ■ ■ ■ ■ “Introduction to the Reports utility” on page 74 “Reports window” on page 75 “NetBackup report types” on page 79 “Using the Troubleshooter within reports” on page 83 . manage. and troubleshoot NetBackup operations.Chapter 3 Reports Use the Reports utility to generate reports on many aspects of the NetBackup environment. The Troubleshooter is available within the Reports utility to help analyze the cause of errors that can appear in a NetBackup report. and media contents.

click File > Change Server. Select the media servers and clients on which to run the report. 2 3 4 . Figure 3-1 NetBackup Reports utility Current master server Report descriptions To run a report 1 In the NetBackup Administration Console. expand NetBackup Management > Reports. For a description of the report fields. For more information. Click Run Report. For a description of each report type. A list of report types appears.74 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. The report information is for the master server that is currently selected. then select the time period for which the report runs. see “NetBackup report types” on page 79. see “To administer a remote master server” on page 635. see “NetBackup report types” on page 79. To run a report on a different master server. Double-click the name of the report you would like to run.

The Troubleshooter is available only when a line in a report is selected that displays a NetBackup status code. Figure 3-2 NetBackup Reports window Menu bar Standard Toolbar User 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. ■ . Depending on which report is viewed. see “Using the Troubleshooter within reports” on page 83. right-click on a report.Reports Reports window 75 Reports window The Reports window contains multiple ways to view report listings and manage report data. For more information. Troubleshooter: Launches the Troubleshooter. the shortcut list may include: ■ Font: Use to change the typeface and point size of the display text in the report pane.

Keep logs. click Set Defaults. the start time is one day before the report is run and the end time is the time the report is run. Date/Time range Specify the time period that you want the report to encompass. Even Size. Settings: Options to reload settings from default. For more information. Columns: Opens a submenu that contains commands for changing the order and size of columns. see “Keep logs” on page 379. The Clean-up host property. See the online help for information on how to use the Filter dialog box. Filter: Use the Filter option to narrow in on specific data in a table. . To set the date and time for all reports. Sort: Use to specify sort criteria for the columns. Client Click the Client box and select All clients or select the client to which the report applies. Fixed Size. Includes: Layout options. and Size to Data. Select Earliest available to include the earliest possible data available. save the current settings as the default settings. Not all settings are available for every report type. Find: Use to find text within the report. ■ ■ ■ ■ ■ ■ Reports settings Use the report settings to specify the following criteria for building a report. Disk pool Click the Disk Pool box and select All Disk Pools or the disk pool type to which the report applies.76 Reports Reports window ■ Print: Opens the system Print dialog box to print the contents of the generated report. Clear Filter: Clears the filter if a filter is currently in effect. Select Current time to include all the data until the present. By default. Proportional Size. The field is enabled only if OpenStorage. SharedDisk. or save settings on exit. Use the controls on the Filter dialog box to list the rows that match specified criteria. determines the period of time for which the information is available. or AdvancedDisk disk pools exist in the configuration.

The currently selected master server and the media servers appear in the report. Specify the path to include in the report. Path The Path selection appears for specific Disk Type selections. Volume ID If the Disk Type selection for a disk report is Array Disk. Job ID Specify the Job ID for which you want the report. Verbose listing Select Verbose listing to have NetBackup provide more details in the Media Summary 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. The NetBackup media servers and server groups in your environment appear in the drop-down list.Reports Reports window 77 Disk type Click the Disk Type box and select All Disk Types or the disk storage unit type to which the report applies. Media owner Click the Media Owner box and select the owner of the media to which the report applies. Select a Volume ID to include in the report. The Media Contents report requires a specific ID. . specify the media ID or All Media. 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 Volume ID selection appears. Media ID For media types of reports.

specify the volume pool name or All Volume Pools. .78 Reports Reports window Volume pool For a media summary report. Stop report Click Stop Report if a report is running. Run report Click Run Report after you’ve selected the criteria for a report. but you don’t want to wait for it to finish.

Images on Media report The Images on Media report lists the contents of the media as recorded in the NetBackup image catalog. This report includes the information from the Problems report and Media Logs report. The transfer rate is useful to determine and predict rates and backup times for future backups.Reports NetBackup report types 79 NetBackup report types The following sections describe the contents of NetBackup reports. media ID. (The transfer rate does not appear for multiplexed backups. If an error has occurred. All Log Entries report The All Log Entries report lists all log entries for the specified time period. a short explanation of the error is included. This report also displays the transfer rate. Click Help within the Status of Backups report window for a description of each column. 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. Click Help within the Problems report window for a description of each column. or path.) Click Help within the All Log Entries 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. You can generate this report for any type of media (including disk) and filter it according to client.

Click Help within the Images on Media report window for a description of each column. 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. Click Help within the Media Logs report window for a description of each column. If a tape must be mounted. The report is a subset of the Images on Media report and displays only tape-specific columns. Tape Contents report The Tape Contents report displays the contents of a volume as read directly from the media header and backup headers. cold catalog backups. 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. Note: The Tape Contents report does not apply to disk type storage units or NetBackup offline. cold catalog backups. . This report lists the backup IDs (not each individual file) that are on a single volume. Click Help within the Images on Tape 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. Tape Logs report The Tape Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. the delay is longer before the report appears.80 Reports NetBackup report types Note: The Images on Media report does not display information for the media that is used for NetBackup offline.

NetBackup deletes other expired volumes from the media catalog when backups are run. Click Help within the Tape Written report window for a description of each column. It also displays how many volumes are at each retention level. Only FROZEN expired volumes appear in the report. ■ . 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. ■ For information about the backups that are saved to disk storage units. In verbose mode. cold catalog backups of the NetBackup catalogs. the report displays each media ID and the expiration date. FROZEN.Reports NetBackup report types 81 Click Help within the Tape Contents report window for a description of each column. cold catalog backups. SUSPENDED. Or. Click Help within the Tape Summary report window for a description of each column. The report also does not display the volumes that were used for duplication if the original was created before the specified time period. Other volumes are considered active. This host property causes NetBackup to send an email that indicates the status of each catalog backup and the media ID that was used. or IMPORTED. The Tape Written report does not display the volumes that were used for NetBackup offline. Tape Summary report The Tape Summary report summarizes active and nonactive volumes for the specified media owner according to expiration date. Tape Written report The Tape Written report identifies the volumes that were used for backups within the specified time period. use the Images on Media report. keep a hard copy record. Expired. cold catalog backups. This report does not show media for disk type storage units or for offline. non-FROZEN volumes display if the report is run between the time the volumes expire and the time that the next backup is run. configure the Administrator’s E-mail Address Global Attribute host property. To track the media that is used for offline. Nonactive media are those with a status of FULL.

the total capacity and the used capacity of the disk storage unit.x media servers do not display capacity-related information. Storage units that reference disk pools do not display capacity values. Disk Storage Unit Status report The Disk Storage Unit Status report displays the state of disk storage units in the current NetBackup configuration. For more information. The report provides a summary of the storage unit contents. see “Administrator email address” on page 434. according to the NetBackup catalog. If a disk becomes bad or if a media server crashes. The report is a subset of the Images on Media report and displays only disk-specific columns.82 Reports NetBackup report types You can then print the email or save it on a disk other than the one that contains the catalogs. Click Help within the Tape Lists report window for a description of each column. Click Help within the Images on Disk report window for a description of each column. this report can let you know what data is lost. These values are available by expanding Media and Device Management > Devices > Disk Pools. Click Help within the Disk Storage Unit Status 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. Click Help within the Disk Logs report window for a description of each column. . For example. Disk Reports The Disk Reports pertain to the information available about the images that are stored on disk media. The report is a subset of the Media Logs report and displays only disk-specific columns. Storage units configured on 5. 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.

enter a status code.Reports Using the Troubleshooter within reports 83 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. A recommended action appears on the Troubleshoot tab. Then. then click Lookup. The Troubleshooter dialog box appears. To run the Troubleshooter within reports 1 2 3 Run a report. Click Help within the Disk Pool Status report window for a description of each column. that states an explanation of the problem on the Problem tab. Open the Troubleshooter at any time (Help > Troubleshooter). . Right-click a line in the report. select Troubleshooter from the shortcut menu. 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.

84 Reports Using the Troubleshooter within reports .

A backup policy can apply to one or more clients. create a policy for each group. This chapter contains the following sections: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ “Using the Policies utility” on page 86 “Configuring backup policies” on page 87 “Changing policies” on page 88 “Policy Attributes tab” on page 93 “Schedules tab” on page 123 and “Schedule Attributes tab” on page 124 “Start Window tab” on page 148 “Exclude dates tab” on page 151 “Calendar schedule tab” on page 152 “Example policies” on page 159 “Clients tab” on page 165 “Backup Selections tab” on page 167 “Rules to indicate paths in the backup selections list” on page 174 “Disaster Recovery tab” on page 193 “Creating a Vault policy” on page 196 “Performing manual backups” on page 197 “More about synthetic backups” on page 198 . Every client must be in at least one backup policy. Then.Chapter 4 Policies Policies define the rules that NetBackup follows when clients are backed up. The best approach to configure backup policies is to divide clients into groups according to the backup requirements and archive requirements.

Tree and detail views The left pane contains a hierarchical view of the policies on the master server currently under management. select that policy in the left pane. Clients. A summary of all polices appears in the Details pane. click Summary of All Policies. To display the general attributes for a specific policy.86 Policies Using the Policies utility Using the Policies utility The Policies utility contains tools to configure and manage policies. Schedules. subdivided into panes displaying Polices. and Selections. Double-click on a policy to display the attributes in tabs. To display information about all policies on the current master server. Figure 4-1 Menu bar Standard toolbar Current master server User toolbar NetBackup Policy utility Inactive policies appear in gray Tree view in left pane Details panes . The Details pane is a detailed view that displays the information that pertains to the policy that is selected. The Details pane shows the general attributes for that policy only. available for editing.

For more information on how to configure a policy to archive the catalog. To create a policy without the Backup Policy Configuration Wizard 1 2 3 4 In the NetBackup Administration Console. click Create a Backup Policy. see “NetBackup naming conventions” on page 629. which simplifies the process as it automatically chooses the values that are good for most configurations. to configure a calendar-based schedule. Configuring backup policies The easiest method to set up a backup policy is to use the Backup Policy Configuration Wizard. Select Actions > New > New Policy. Click Help on any wizard screen for assistance while running the wizard. You can change the schedule to a calendar-based schedule after running the wizard. Note: The wizard cannot be used. Click OK.Policies Configuring backup policies 87 Policies menu bar The options on the Policies menu bar are described in the online help. expand NetBackup Management > Policies. For more information. the policy must be named catarc. . select Master Server or NetBackup Management. To create a policy with the Backup Policy Configuration Wizard 1 2 In the NetBackup Administration Console. For more information. see “Calendar schedule tab” on page 152. however. Type a unique name for the new policy in the Add a New Policy dialog box. From the list of wizards in the Details pane. see “Creating a catalog archiving policy” on page 312. This wizard guides you through the setup process. Note: If the schedule is to be used for a catalog archive.

For more information. Perform one of the following actions: ■ To add a schedule. select Actions > New > New Schedule. click OK. and Calendar Schedule tab (if displayed). Exclude Dates tab. For more information. To add or change schedules in a policy 1 2 3 Expand NetBackup Management > Policies. To add or change backup selections in a policy Note: To configure a Vault policy. 5 To add or change clients in a policy 1 2 3 In the NetBackup Administration Console. Click OK. Select the policy name in the left pane. Make adjustments before backups begin to ensure an orderly transition from one configuration to another. Perform one of the following actions: ■ To add a new client. select Actions > New > New Client. Select the policy name in the left pane. To add more schedules. . If this schedule is the last schedule. expand NetBackup Management > Policies. ■ 4 Complete the entries in the Add New Client or Change Client dialog. see “Schedules tab” on page 123. Start Window tab. double-click the client name in the Details pane. The Add New Client dialog appears. double-click the schedule name in the Details pane. To change an existing schedule.88 Policies Changing policies Changing policies Change policies only when no backup activity is expected for the affected policies and clients. see “To create a Vault policy” on page 196. click Add and repeat the previous step. expand NetBackup Management > Policies. 1 In the NetBackup Administration Console. ■ 4 Complete the entries in the Attributes tab. see “To add a client to a policy” on page 165. The Add New Schedule dialog appears. To change an existing client.

To change an existing backup selection. ■ 4 Complete the entries in the New Backup Selections or Change Backup Selections dialog. Both the Copy and Cut commands copy the selected items to the clipboard. cut. The new entry appears in the list. and paste Schedules. copy. When the clipboard contains an entire policy: ■ ■ The following is a general procedure (variations are possible): 1 2 3 4 . and paste items You can copy or cut and paste the following items: ■ ■ ■ Copy and paste (not cut) attributes Copy and paste (not cut) entire policies Copy. Define all new selections. select Actions > New > New Backup Selection. The New Backup Selection dialog appears. Select Edit > Copy or Edit > Cut. then click OK. In the NetBackup Administration Console. and Clients If you select a policy and paste the policy. see “Rules to indicate paths in the backup selections list” on page 174. clients. In the Details pane. For information on how to specify file paths for clients. only that type of information is pasted (for example. select the policy from which you want to copy or move items. click OK. In the left pane. files). ■ To cut.Policies Changing policies 89 2 3 Select the policy name in the left pane. double-click the backup selection in the Details pane. expand NetBackup Management > Policies. the contents of the clipboard is pasted into the selected policy. or schedules). In the Change Backup Selection dialog. select the policy where you want to paste or move the items. select the item (backup selections. Backup Selections. When the clipboard contains a single type of item paste it into a policy or into the same type of item within a policy. click Add. In the left pane. If you paste to a single type of item within a policy. then: ■ 5 In the New Backup Selection dialog. Perform one of the following actions: ■ To add a new backup selection. Add the new backup selection or make changes to an existing selection.

schedules. select a storage unit and volume pool at the destination server. Edit > Clipboard. For the configuration to work. The action is indicated in a dialog. To move policy information from one server to another 1 2 3 Copy the policy information to the clipboard. the schedules are deleted or renamed.) To change multiple policies 1 In the NetBackup Administration Console. 6 On the Edit menu. click Paste. Copy the entire policy or part of a policy. click the pane where you want to paste the contents of the clipboard: attributes. clients. Paste the policy information in the Policies node. (For example. backup selections. Note: Any items with the same name are replaced with the contents of the clipboard after pasting. you must complete the rest of the configuration on the destination server. The Details pane displays the attributes. expand NetBackup Management > Policies > Summary of All Policies. schedules. If there are any schedules that do not match the policy type. Change to the destination server. and clients in all policies. or backup selections. To view the contents of the clipboard.90 Policies Changing policies 5 In the Details pane. .

Select Edit > Change. The text field is clear if the property does not have the same value for all selected machines. Clear the check box to clear the property on all selected machines. if the property is clear on all selected machines. Using the composite change dialog The following topics explain how to interpret and change policy settings when multiple policies are selected. Set (or leave) the box to a gray check to leave the property unchanged. “Using the composite change dialog” on page 91. ■ Gray check. Any change is applied to the field for every selected policy. the check box displays in one of the following states: ■ Checked. if the property is set differently on the selected machines. . To change the selection: ■ ■ ■ Select the check box to set the property on all selected machines. At any time.Policies Changing policies 91 2 3 In the Details pane. ■ If the property is a text field in which to specify a value: ■ The text field displays a value if the property has the same value for all selected machines. ■ Clear. click Cancel to cancel changes or click OK to apply all changes and close the dialog. hold down the Shift key and select the items you want to change. ■ ■ If the property is a check box and not a value. if the attribute is specified for all selected machines. See the following section.

the actual file is not deleted from the client. Select the policy name in the left pane. Backups for the client can be recovered until the backups expire. backup selections. when a file is deleted from a backup selection list. In the Details pane. Also. expand NetBackup Management > Policies. Select Edit > Delete. or clients from a policy 1 2 3 4 In the NetBackup Administration Console. Note: When a client is deleted from the client list. the NetBackup client software is not deleted or uninstalled from the client.92 Policies Changing policies To delete schedules. Click Yes. select the item you’d like to delete. . A confirmation dialog appears.

The type of backup policy. The priority that NetBackup gives to the backups for the selected policy relative to other policies. Snapshot Client attributes.Policies Policy Attributes tab 93 Policy Attributes tab The settings on the Attributes tab determine the characteristics of all the backups that NetBackup performs according to the selected policy. which primarily defines the type of clients the policy backs up. 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. ■ ■ ■ ■ . if Snapshot Client is installed. The storage unit that NetBackup uses to back up the clients in the selected policy.

) Select the type of policy from the drop-down list. (NBU-Catalog.94 Policies Policy Attributes tab Figure 4-2 Policy Attributes tab The following sections describe the settings on the Attributes tab. If the schedules become . Policy type The Policy type attribute determines the purpose of the policy. However. The Policy type of an existing policy may be changed. the existing schedules may become invalid for the new policy type. for example. Not all policy types serve to back up up clients. Policy attributes are configurable depending on the type of policy and the options that are installed. Usually. the Policy type determines the type of clients that can be backed up by this policy.

For information on setting up this policy type. Use for the policies that contain only clients with the NetBackup for NDMP option.x NT clients. Allows for a catalog backup while other jobs are running. Vault Use as a policy type to schedule and run a Vault job. Use for the policies that contain only clients with the NetBackup for Lotus Notes option. see the guide for this option.Policies Policy Attributes tab 95 invalid. This policy type is available only when the NetBackup NDMP is installed and licensed. Note: The following policy types apply only to UNIX clients. XP. see the guide for this option. Use for the policies that contain only clients with the NetBackup for MS-SQL Server option. Use for the policies that contain only clients with the NetBackup for DB2 option. NetBackup Novell NetWare clients that have the target version of NetBackup software. 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). NetBackup then either deletes the invalid schedules or changes the schedules to an equivalent type. see the guide for this option. Use for the policies that contain only Windows 2000. 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. For information on setting up this policy type. except those covered by specific such as Oracle. Use for the policies that contain only NonTarget NetBackup Novell NetWare clients (this version uses a Microsoft Windows interface). NetBackup displays an alert notice. Use for the policies that contain only clients with the NetBackup for Oracle option. see the guide for this option. For information on setting up this policy type. see the guide for this option. Windows Server 2003. Use for hot catalog backup jobs. For information on setting up this policy type. For information on setting up this policy type. . For information on setting up this policy type. Use for the policies that contain only clients with the NetBackup for MS-Exchange option. Available only when Vault is licensed. For information on setting up this policy type. or NetBackup 5. Use for the policies that contain only clients with the NetBackup for Teradata option. see the guide for this option.

or the Collect disaster recovery information for Bare Metal Restore 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.” in the NetBackup Administrator’s Guide. DataTools-SQLBackTrack Use for the policies that contain only clients with the NetBackup for DataTools-SQL-BackTrack option. a gold backup must go to a storage unit with a gold data classification. Use for the policies that contain only clients with the NetBackup for Informix option. see the NetBackup Snapshot Client Administrator’s Guide. . see the Snapshot Client Administrator’s Guide. see the guide for this option. Applies only to NetBackup Enterprise Server: Use for the policies that contain only NetBackup FlashBackup clients on UNIX. For information on setting up this policy type. Use for the policies that contain only clients with the NetBackup for SAP option.96 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. Checkpoint Restart for restores. 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 information on setting up this policy type. This policy is available only when the NetBackup Snapshot Client is installed. For more details on off-host backups. For information on setting up this policy type. Use for the policies that contain only clients with the NetBackup for Sybase option. For information on setting up this policy type. For example. see the guide for this option. see the guide for this option. synthetic backups. This policy is available only when the NetBackup Snapshot Client is installed. see the guide for this option. See “Using NetBackup with AFS. Use to configure a policy for NetBackup for SharePoint Portal Server. Volume II for information on setting up these policies. FlashBackup FlashBackupWindows Applies only to NetBackup Enterprise Server: Use for the policies that contain only NetBackup FlashBackup-Windows clients on Windows. For information on setting up this policy type. refer to the NetBackup Snapshot Client Administrator’s Guide. For information on setting up this policy type.

For more information on creating data classifications. gold backup images cannot be sent to a silver storage lifecycle. and storage unit groups. If configured. Policy storage The Policy storage attribute specifies the storage destination for the policy’s data. NetBackup tries to store data on locally-attached storage units first.) . see “Data classification” on page 258. The local storage units take precedence over the sequence that is based on alphabetical order. (See “Must use local drive” on page 428. storage lifecycle policies. Images that belong to a specific data classification cannot be sent to a storage lifecycle that does not have a classification. For more information on data classifications and lifecycles. select Must use local drive on the General Server Properties. If configured to do so. For example. Select the storage destination from the drop-down list. see “Data Classification properties” on page 403. If Any Available is selected. the policy uses the storage units and groups that the Policy storage attribute indicates. all the images that the policy creates are tagged with the classification ID.) The list includes only those lifecycles that are of the same data classification as the policy.Policies Policy Attributes tab 97 A Data Classification selection is optional. the selection of a storage unit or a storage lifecycle policy determines which type of disk staging is used for this policy. The storage unit that is selected on the Schedule tab. (See “Override policy storage selection” on page 143. (See “Staging backups to initial storage. overrides the Policy storage attribute.) If a local device is not found or if the Must use local drive attribute is not selected. To select a data classification is optional. If Any Available is selected. To force NetBackup to use only a locally-attached drive. If no classification is indicated. NetBackup tries to find an available storage unit alphabetically. the drop-down list may contain storage units. 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. then final storage” on page 238. If a data classification is selected.

.) Note: If the Scratch pool option is enabled for the volume pool. Do not specify a storage unit at the schedule level.) To limit the storage units available to a policy. 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.98 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 enable Scratch pool for the volume pool. Make sure that one of the storage units within the group is set to On Demand Only to satisfy the policy requirement. do not configure all storage units to be On Demand Only. The increased setting ensures that the catalog backup can proceed while regular backup activity occurs. (See “On demand only” on page 231. Concerning the Policy storage attribute and online catalog backups: ■ For online. (See “Adding a new volume pool” on page 540. 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. For this method to work. hot catalog backups when a disk storage unit is indicated: increase the Maximum concurrent jobs setting on the storage unit. backups cannot run for those policies and the schedules that require the unit. ■ ■ ■ A policy may specify a storage unit group.) In this situation. set Policy volume pool to the volume pool that is defined in the previous step. (See “Override policy storage selection” on page 143.) ■ ■ If a specific storage unit is designated and the unit is unavailable. set Policy storage attribute to Any Available. select a storage unit group that contains only the units you want the policy to use. b c In the policy. For all policies. NetBackup may be unable to find an available storage unit for the backups. If Any Available is selected. any storage unit has access to the volumes in the volume pool.

do not select Any Available for the destination Policy storage attribute. The volume pool that is selected on the Schedule tab overrides the Policy volume pool setting. ■ ■ Media is assigned to the volume pools for Media Manager storage devices.) NetBackup creates four default volume pools: ■ None: The default pool for applications. hot catalog backups) that selects the CatalogBackup volume pool by default. hot catalog backups. see “Volume pool operations” on page 540. all backups use media from the NetBackup pool.0 or later to store catalog backup data. cold catalog backups use media from the NetBackup volume pool. For information about how to create volume pools and how to add media to them. If the installation contains 5. dedicated pool to facilitate faster catalog restores.x media server may be selected and the backup would fail. it is allocated from the volume pool indicated. other than NetBackup and Storage Migrator. for use by user backups. (See “Override policy volume pool” on page 143. The 5. ■ ■ ■ Additional volume pools can be useful.x media servers hosting disk storage units. It is used exclusively for online. 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. A User volume pool. . Select a volume pool name from the list of volume pools. DataStore: The default pool for DataStore. The volume pool is protected from access by other applications and users. hot catalogs are directed to a single. Whenever a new volume is required. for use by automatic backups. NetBackup: Unless otherwise specified in the policy.Policies Policy Attributes tab 99 ■ Online catalog backups must use media servers at version 6. One exception is the NBU-Catalog policy type (used for online. Offline. An Auto volume pool. Disk-type storage devices are not allocated to a volume pool. Policy volume pool The Policy volume pool attribute specifies the default volume pool where the backups for the policy are stored. Online. A volume pool is a group of media that is grouped together for use by a single application. CatalogBackup: This pool is selected by default for the NBU-Catalog policy type.

set Override policy volume pool as follows: ■ For the schedules that use the Backups volume pool. clear Override policy volume pool.100 Policies Policy Attributes tab Volume pool override example Assume that you want all schedules but one to use the Backups pool. In the policy. When you set up the schedules for the policy. The exception is a user-archive schedule that requires the Archive pool. set Policy volume pool to Backups. ■ . select Override policy volume pool and specify Archive for the pool name. For the schedule that requires the Archive volume pool.

To see if this feature is supported for a specific agent or option. By taking checkpoints periodically during the backup. Note: Although NetWare clients can use the Standard policy type. (See “Schedule backup attempts” on page 431. The Schedule backup attempts Global Attributes host property indicates the number of times that NetBackup tries a failed backup. Note that checkpoints cannot occur while a file is backed up. ■ . (See “Multiple copies” on page 137. increase the time between checkpoints. Checkpoints are saved at file boundaries. checkpoint restart for backups is not supported on NetWare clients. a failed backup restarts from the beginning of the job. Without Take checkpoints every enabled. Checkpoints during a backup are beneficial if a backup fails. Checkpoint frequency The checkpoint frequency indicates how often NetBackup takes a checkpoint during a backup. If the frequency of checkpoints impacts performance. Indicate how often the policy should take checkpoints.) Policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support this policy attribute.) 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. (Default: 15 minutes.Policies Policy Attributes tab 101 Checkpoint restart for backup jobs The Take checkpoints every check box specifies whether NetBackup takes checkpoints during a backup job. Checkpoint restart support ■ Multiple Copies: Checkpoint restart is supported for the policies that are configured to create multiple backup copies.) The administrator determines checkpoint frequency on a policy-by-policy basis. refer to the manual for that agent or option. and point to the next file in the list. Balance more frequent checkpoints with the likelihood of time that is lost when a backup is resumed. and Take checkpoints every is selected for this policy. NetBackup can retry a failed backup from the beginning of the last checkpoint rather than restart the entire job.

Media Server Copy.102 Policies Policy Attributes tab ■ Veritas Volume Snapshot Provider (VSP): Checkpoint restart is supported for use with VSP. Windows Disk-Image (raw) backups: No checkpoints are taken during a Windows disk-image backup. ■ ■ ■ ■ Synthetic backups: Checkpoint restart is not supported for use with synthetic backups in the current NetBackup release. If the time indicated by the Clean-up property. the files that were backed up before the resume are backed up again during the next incremental backup. Disk staging storage units (used in basic disk staging): Checkpoint restart is supported for use in Stage I of basic disk staging. NetBackup starts a new job in the following situations: ■ ■ ■ ■ If a new job is due to run. However. For more information. Since the archive bits remain. NetBackup decides when a new job should be started instead of resuming an incomplete job. other methods are not supported: Block Level Incremental Backups. Checkpoint restart is unavailable in the Stage II storage unit policy of basic disk staging. ■ ■ . Third-Party Copy Device. it restarts from the beginning. during which data is backed up to disk. during which data is relocated to another storage unit. Single-instance Store (SIS): No checkpoints are taken for the remainder of the backup after NetBackup encounters single-instance store. the archive bits are not cleared for the files that were backed up before the resume.) Snapshot Client: Checkpoint restart is supported for use with local or alternate client backups. see “Staging backups to initial storage. If the user archive is resumed. For calendar scheduling. Move backup job from incomplete state to done state. However. If the time since the last incomplete backup has been longer than the shortest frequency in any schedule for the policy. (See “VSP (Volume Snapshot Provider) properties” on page 486. On Windows clients: ■ ■ ■ ■ System State backups: No checkpoints are taken during the backup of a System State. the archive bits are cleared for the files that were backed up after the job resumed. has passed. if another run day has arrived. Checkpoints are not taken for a user archive schedule. When an incremental backup is resumed and completes successfully. then final storage” on page 238. and Instant Recovery backups.

Parent jobs do not count toward the limit. a restore job that contains checkpoints does not need to be restored from a checkpointed backup. if three policies limit concurrent jobs to two. Limit jobs per policy The Limit jobs per policy attribute limits the number of jobs that NetBackup performs concurrently when the policy is run. Other resource settings can limit the number of jobs. Conversely. select the check box and specify a value from 1 to 999.) A backup that contains checkpoints does not need to be restored with a checkpointed restore job.Policies Policy Attributes tab 103 Checkpoint restart for restore jobs NetBackup automatically takes checkpoints during restore jobs by default. the check box is clear. By default. 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. The following jobs produce a parent ■ . (See “Checkpoint restart for restore jobs” on page 676. A configuration can contain enough devices so that the number of concurrent backups affects performance. To specify a lower limit. and NetBackup performs an unlimited number of backup jobs concurrently. Only the children jobs count toward the Limit jobs per policy setting. For example. NetBackup can start two jobs from each policy. A total of six policies may be running at one time in this situation.

The load on the client and server. and applications that are running.) When the client that is backed up is also a server. is still a factor. the configuration must include one of the following: ■ ■ Multiple storage units. Storage units that are configured to multiplex. With disk storage. Lower values can limit multiplexing within a policy if jobs from different schedules exist within the policy. operating system. With removable media devices such as tape drives. regardless of the multiplexing settings. The network load. or Bare Metal Restore jobs. To process more than one backup job at a time.) ■ The number of storage devices available and multiplexing limits. . (See “Compression” on page 111. Or. Limit jobs per policy is set to two and an incremental backup schedule is due to run for four clients. A storage unit with enough drives to perform more than one backup at a time. consider multiple networks for backups. Snapshot Client snapshots. it is a special case.104 Policies Policy Attributes tab job and children jobs: multistreamed jobs. catalog backups. (See “Parent jobs” on page 55. In this instance. To have a higher priority means that NetBackup assigns the first available drive to the first client in the policy with the highest priority. however. Only two clients are backed up at one time. Multiplexing. The available bandwidth of the network determines how many backups can occur concurrently. set Limit jobs per policy high enough to support the specified level of multiplexing. ■ ■ The server speed. the network load is not a factor because the network is not used. If you encounter loading problems. If multiplexing is used. For example. ■ ■ Job priority The Job priority attribute specifies the priority that a policy has it competes with other policies for backup resources. Too many concurrent backups interfere with the performance of the server. the number of concurrent jobs depends on the total number of drives in the storage units. The best number depends on the hardware. the storage device is defined as a file path and the available disk space determines how many paths are possible. configure the backup policy to use Compression.

Make sure that the Go into effect at date and time is set to the time that you want to resume backups. No media server is specified explicitly. . A server group. The Go into effect at attribute specifies when the policy can begin to schedule backups. The Media Owner property specifies which media server or server group should own the media on which backup images for this policy are written. but you want a media server to own the media. Any policy with a priority greater than zero has priority over the default setting. allows NetBackup to choose the media owner. To resume backups. For more information about how to configure a policy to archive the catalog. NetBackup chooses a media server or a server group (if one is configured). see “Creating a catalog archiving policy” on page 312. The default for all policies is 0. Go into effect at To activate the policy. All server groups that are configured in the NetBackup environment appear in the drop-down list. recheck the Active check box. if today is Monday and you enter Wednesday at 12:00 AM. clear the Active check box. A server group allows only those servers in the group to write to the media on which backup images for this policy are written. Inactive policies appear in gray in the Administration Console. Use the Go into effect at attribute to configure a series of policies in advance of when the policies need to become active. select the Active check box. ■ ■ For more information about server groups and shared media. the policy must not be active. To deactivate a policy. The Active check box must be clear. the lowest priority possible. None specifies that the media server that writes the image to the media owns the media. If the schedule is to be used for a catalog archive. enter a number in the Job priority field (maximum 99999).Policies Policy Attributes tab 105 To set the priority. The policy must be active for NetBackup to use the policy. see “Configuring server groups for media sharing” on page 614 Active. the policy does not run until that time or later. Specify a server group. For example. You can specify the following for Media Owner: ■ Any (default). Media owner Active only for Media Manager type storage units or if the Policy storage attribute is Any Available.

b . UNC paths are more precise and indicate exactly what should be backed up. perform the following steps: 1 2 3 On the NetBackup master server.106 Policies Policy Attributes tab Backup network drives The Backup network drives attribute is for use on single user systems. master1. and Restore console when backups are browsed. Archive. On win_client. The preferred method for backing up data from a machine other than a NetBackup client is to use UNC paths. Setup example with UNC paths Assume that: ■ ■ ■ master1 is the NetBackup master server. For scheduled backups. By default. 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. Stop and start the NetBackup Client Service so the new account takes effect. This user account must have read permissions for the share that is to be backed up. For example. win_PC is a Windows computer (not necessarily a NetBackup client) and contains a shared folder named TestData. Win98. Win95. the file list must indicate at least the first level of folders to be backed up. When Backup network drives or UNC paths are used. Drive letters do not appear in the Backup. the network drives must be available to the service account that the NetBackup Client service logs into at startup. The account must have write permission to perform restores. Backup network drives must be checked when policies back up to CD ROM drives. 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. create a policy for win_client. win_client is a Windows NetBackup client. the startup account is set to System. and ME. These operating systems are not supported with this version of NetBackup. To back up the folder TestData on win_PC through win_client. D:\Folder1 instead of only D:\ Note: Mapped drive letters cannot be backed up. You must change this account on each Windows client that is backed up that contains data that is shared from another machine.

On win_client. The account must have write permission to perform restores. win_client is a Windows NetBackup client. Or. expand the Network node in the Backup. This user account must have read permissions for the share that is to be backed up. b c 3 4 To run a user backup. Select TestData. 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. perform the following steps: 1 2 On the NetBackup master server. Select TestData. expand the Network node in the Backup. To back up the folder share on win_PC through win_client. Scheduled backups run as scheduled or when a manual backup is performed. Archive. Archive. select Backup network drives in the policy to be used for the backup. Example using the Backup network drives attribute Assume that: ■ ■ ■ master1 is the NetBackup master server. master1. . Stop and start the NetBackup Client Service so the new account takes effect. and Restore client interface to win_PC. Clear the check box to prevent the backup or archive of NFS mounted files.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. and Restore client interface to win_PC. by the user in the case of a user backup or archive. 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. win_PC is a Windows computer (not necessarily a NetBackup client) and has a shared folder that is named share. Create a bpstart_notify. Backups run as scheduled or when a manual backup is performed.Policies Policy Attributes tab 107 4 5 To run a user backup.

Use this capability to back up the systems that the NetBackup client software does not support. Note: NetBackup does not support raw partition backups on unformatted partitions. To do so. 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. NFS backups have lower performance and sometimes encounter problems. Nor can you back up raw partitions from other machines that use NFS mounts to access the raw partitions. add an entry for the automounter’s mount directory to the exclude list on the client. archive. Notes on Follow NFS ■ The behavior of the Follow NFS attribute depends on the Cross mount points setting (explained later in this chapter). If the files are mounted on the NetBackup client. you can back up. and restore them by working from the NetBackup client. you may want to use the policy only for the files and clients that are backed up or archived over NFS. Follow NFS has no effect on raw partitions. 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. Disadvantages of the Follow NFS attribute Generally. Automounted directories can be excluded while allowing backup of other NFS mounts. . If Follow NFS is selected. The devices are not accessible on other machines through NFS. do not back up NetBackup clients over NFS.108 Policies Policy Attributes tab Note: The Follow NFS attribute applies only to UNIX clients in certain policy types. Back up and archive files on the NFS server where the files physically reside. ■ ■ Follow NFS causes files in automounted file systems to be backed up. You must have the necessary permissions on the NFS mount. The Network File Systems that are mounted in a raw partition are not backed up. NetBackup allows it to be selected in those instances only.

) Do not cross mount points to back up a media server that uses mount points to any disk storage that contains backup images. If a raw partition is the root partition and contains mount points for other file systems. include the directories in the file list. ■ ■ Note: The following information applies only to UNIX clients. change the UNIX master server host property. if you specify root (/) as the file path. NetBackup backs up root (/) and all files and directories under root in the tree. The NetBackup BasicDisk disk type and the Enterprise Disk Option disk types use mount points for disk storage. NetBackup must resolve the links so it can accurately avoid backing up any files that reside on NFS-mounted file systems. (The default time to access the file system is five seconds. NetBackup resolves any links to the true path. . If the policy crosses mount points.Policies Policy Attributes tab 109 Note: If Follow NFS is not selected. To back up mapped directories. NetBackup specifically excludes mapped directories even if Follow NFS and Cross mount points are enabled. Prohibit NetBackup from crossing mount points to back up root (/) without backing up all the file systems that are mounted on root. Notes on cross mount points ■ Cross mount points has no effect on UNIX raw partitions. the other file systems are not backed up.) To change the default. Clear Cross mount points for NetBackup to back up only the files that are in the same file system as the selected file path. the backup process reads the client’s mount table and evaluates each item in the table. /usr and /home. If NetBackup cannot access a Network File System when it evaluates the mount table.) Cross mount points The Cross mount points attribute controls whether NetBackup crosses file system boundaries during a backup on UNIX clients. (For example. the NetBackup backup images that reside on that disk storage are backed up. it assumes that the file system is unavailable. (See “NFS access timeout” on page 484. For example. NFS access timeout. regardless of the file system. ■ Select Cross mount points to have NetBackup back up all files and directories in the selected path.

include root (/). Cases that can require separate policies In some cases. consider separate policies if a backup crosses mount points. . Place other file systems in another policy or policies.110 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. Cross mount point examples The following examples assume that the client disks are partitioned as shown in Figure 4-4. How the Cross mount points attribute interacts with Follow NFS To back up NFS-mounted files. Cross local mount points but not NFS mounts. For example. create a policy in which Cross mount points is not selected. and not the file systems that are mounted on it. In the backup selection list. Follow the specified path across mount points to back up files and directories (including NFS). select Follow NFS. include the directories in the file list. Only the root file system is backed up. regardless of the file system where they reside. The backup selection list contains only root (/). Back up NFS files if the file path is (or is part of) an NFS mount. To back up all the data on a client. create a policy in which Cross mount points is selected. To back up mapped directories. 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). Note: NetBackup specifically excludes mapped directories even if Follow NFS and Cross mount points are enabled.

Example 1 Assume that Cross mount points and Follow NFS are not selected. leave / out of the list and separately list the files and directories you want to include. and /home in separate partitions on disk d1. To back up only /usr and individual files under /.Policies Policy Attributes tab 111 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. In addition. the client contains /. Assume that the backup selection list contains only / . Another file system named /home/njr exists on disk d2 and is mounted on /home. (Default: no compression. In this case. Example 2 Assume that Cross mount points and Follow NFS are selected. Select the check box to enable compression. including those under /home/njr and /net/freddie/home. It does not back up /home/njr or /net/freddie/home. 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.) . 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. disk d3 contains a directory named /net/freddie/home that is NFS-mounted on /net/freddie. /usr. NetBackup backs up all the files and directories in the tree.

Examples include stripped and unstripped binaries. Compression also decreases the amount of data that travels over the network as well as the network load. The effects of the lower transfer rate causes additional wear on those devices. 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. ASCII. The discrepancy is due to client disk fragmentation and the file headers that the client adds. the storage unit may not be able to use data deduplication on the compressed or the encrypted data. reducing the total time to back them up. and the non-unique strings that repeat. the server may receive more data than what exists on the client. (To tell how much space a file occupies. If total backup time is a problem. run the df command. To tell how much free disk space is available. If compressed data is written to a storage unit that has single-instance store (SIS) capabilities. . A backup usually involves more than one type of data. In data deduplication.112 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. Note: When compression is not used. In turn. only one instance of the file is stored. consider multiplexing. ASCII files. the smaller backup size decreases the amount of media that is required for storage. The savings in media and network resources. How much compression can be expected? The degree to which a file can be compressed depends on the data type. and unstripped binaries (typically 40% of the original size).) Table 4-3 Data types that compress well: Compression specifications Programs. The lower transfer rate that is associated with compression on the client reduces the ability of some tape devices (notably 8mm) to stream data. still make compression desirable unless total backup time or client computing resources become a problem. The NetBackup multiplexing feature backs up clients in parallel. Subsequent instances of the file reference the single file. run the du command. however. Some data types are more favorable to compression.

).F .SIT.AU .arj or .TIFF .pit. however.Z .jpg or .bin or .cpt or . However. (See “Do not compress files ending with” on page 397.zom or . Effect of file size: Client resources that are Compression requires client computer processing unit time and as much memory as the required: administrator configures.iff or .pak or .tiff or .lha or .ARJ .sea.CPT. For fast CPUs.ZIP .SIT .hqx or . . When the server initiates the backup.LHA .conf file.bin or .sea or .SEA . because that is the tar block size.jpeg or .BIN . File size has no effect on the amount of compression.sit or . I/O rather than CPU speed is the limiting factor. On UNIX clients.Policies Policy Attributes tab 113 Table 4-3 Compression specifications Files that are composed of the strings that repeat can sometimes be compressed to 1% of their original size. if a compressed file has a unique file extension.CPT .au or .JPG .PIT.IFF . it takes longer to compress many small files than a single large one.bin or . On UNIX clients. Best-case compression: Data types that do not compress well: Worst-case compression: Files that are already compressed become slightly larger if compressed again.ZOO .ZOM .arc or .ARC . 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.gif or .F3B .BIN .Y .suffix option in the bp. files with the following suffixes: . exclude it from compression by adding it under the UNIX Client host properties.BIN .bin or .lzh .scf or . On UNIX clients.hqx.gz or GZ .z or .SEA.GIF Encryption The Encryption attribute determines whether the backup should be encrypted. NetBackup does not compress the following files: ■ ■ ■ Files that are not compressed: Files that are equal to or less than 512 bytes.cpt.BIN .JPEG . the files that end with suffixes specified with the COMPRESS_SUFFIX =.bin .sit.HQX.zoo or . it passes on the Encryption policy attribute to the client in the backup request.zip or .SCF . Stripped binaries (usually 60% of original size).PIT .HQX .pit or .bin or .PAK .

If the attribute is enabled. Only policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support this policy attribute. see the NetBackup Security and Encryption Guide. 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. and Linux.114 Policies Policy Attributes tab The client compares the Encryption policy attribute to the Encryption host properties for the client. Bare Metal Restore is a separately-priced option. For more information. to restore the directory contents to reflect what the directories had contained at the time of an incremental or a full backup. 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. Files that were deleted before the backup are not restored. Note: If encrypted data is written to a storage unit that has single-instance store (SIS) capabilities. For more information. 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. the policy can encrypt the backups for that client. The Activity Monitor displays the activity as a job separate from the backup. Windows. Volume II. If the encryption permissions for the client are set to REQUIRED or ALLOWED. the storage unit may not be able to use data deduplication on the compressed or the encrypted data. the BMR client agent runs before each backup to save the configuration information of the client. (See “Encryption properties” on page 405. see “Configuring NetBackup Policies for IDR” in the NetBackup Administrator’s Guide. 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. see the Bare Metal Restore Administrator’s Guide for UNIX. That is. .) For additional encryption configuration information.

or newly installed from a tar or a zip archive. The following examples show how move detection backs up the files that otherwise would not be backed up: . (Depending on how the files were packaged and how they were installed. Note: This attribute must be selected to create synthetic backups.) Without move detection. NetBackup starts to collect the true image restore information with the next full or incremental backup for the policy.Policies Policy Attributes tab 115 With the attribute enabled.) . NetBackup does not provide true image restores based on the time of a user backup or archive. Enable this attribute to include the files that were moved. enable With move detection for the true image incremental backups. (See “Synthetic backup” on page 134. The restore also includes those files that were deleted at any time during that period. If a name or an inode number is new or changed. Note: Some options require that Collect true image restore information with move detection be enabled: . renamed. some newly installed files are not backed up by non-TIR incremental backups. NetBackup compares path names and inode numbers with those from the previous full or incremental backup. renamed. or newly installed because their modification times are unchanged. NetBackup skips the files and directories that were moved. NetBackup uses a user backup for a true image restore if the backup is more recent than the latest automatic full or incremental backup. the file or directory is backed up. a restore based on an incremental backup includes all files that were backed up since the last full backup. The true image restore information is collected for each client regardless of whether any files were changed. To include the files that were moved.) 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. However. or newly installed in the directories.It must be enabled to create synthetic backups. (See “Enable file system export” on page 744. With move detection. renamed.It must be enabled to back up data to the NearStore disk storage units that use the File System Export option.

Move detection consumes space on the client and the backup can fail if there is not enough disk space available. ■ NetBackup begins to collect the information that is required for move detection with the next full or incremental backup for the policy. the archive bit is unchanged but C:\security\devices\ is a new directory and is backed up. Assume that Collect true image restore information was turned on for the policy that performed the backups. ■ A regular restore creates a directory that contains all files and directories that ever existed in C:\user\doc from 12/01/2007 through 12/04/2007. A directory named C:\security\dev\ is renamed as C:\security\devices\. Here. This first backup after setting the attribute. (The date of the last full backup is 12/01/2007): file1 file2 dirA\fileA dirB\fileB . always backs up all files. What happens during true image restores The following table lists the files that are backed up in the C:\home\abc\doc directory during a series of backups between 12/01/2007 and 12/04/2007. the archive bit is unchanged but C:\spec\doc is new in the C:\spec\ directory and is backed up.) indicate that the file was deleted before this backup. 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 C:\user\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 ( -----.116 Policies Policy Attributes tab ■ A file named C:\pub\doc is moved to or installed in C:\spec\doc. Assume that the 12/04/2007 version of the C:\user\doc directory needs to be restored. even if it is an incremental. Here.

Notes on true image restores and move detection ■ NetBackup collects additional information for the incremental backups that collect true image restore information. assume that you created a file named file5 after the incremental backup occurred on 12/04/2007. back up the directories with a policy that collects true image restore information. Incremental backups are slower for a policy in which true image restore information is collected. only directories can be listed and selected. and Restore client interface for more information on true image restores. the contents of the directory after the restore is: file1 file2 file4 ■ ■ ■ ■ ■ . In the previous example. For true image restores. The incremental backup was the reference for the true image restore. In this case. The restored directory does not include the dirA and dirC subdirectories. In true image restore mode.) To restore a file system or disk with a true image restore. Archive. 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. but before the restore. Policies that use move detection require even more space.Policies Policy Attributes tab 117 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. 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. the client interface does not display individual files. Refer to the online Help in the Backup. (See “Keep true image restoration (TIR) information” on page 380. A true image restore preserves the files that are currently in the directory but were not present when the backup was completed.

In addition. However. multiple drives. Note: If this attribute is enabled. Parent jobs display a dash (-) in the Schedule column.) 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. or templates in the backup selection list specify whether each job can back up only a part of the backup selection list. the children jobs display the Job ID of the parent job. and children jobs for each stream. In the Activity Monitor. scripts. or a combination of the two to process the streams concurrently. 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. . scripts. a NetBackup job appears in the Activity Monitor for the excluded file system. ■ The directives. 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. and a file system is in a client’s exclude list. Use multiplexing. The list also determines how the backup selection list is divided into separate streams. see “Adjusting multiple data streams” on page 120. or templates in the backup selection list determine the number of streams (backup jobs) that start for each client. they can occur concurrently. Multistreamed jobs consist of a parent job to perform stream discovery.118 Policies Policy Attributes tab file5 Allow multiple data streams The Allow multiple data streams attribute specifies that NetBackup can divide automatic backups for each client into multiple jobs. (See “Backup selections list directives for multiple data streams” on page 185. The directives. no files in the excluded file system are backed up by the job. Since the jobs are in separate data streams.

the entire 10-gigabyte backup must be retried.Policies Policy Attributes tab 119 Note: For best performance. A single failure only terminates a single stream.) . applies to each stream. the use of multiple data streams can shorten the retry time in the event of a backup failure. assume the backup for a 10-gigabyte partition is split into 5 streams. use only one data stream to back up each physical device on the client. Reduce retry time for backup failures Because the backup streams are independent of one another. If the 10-gigabyte partition is backed up without multiple data streams and a failure occurs. NetBackup retries each stream a maximum of three times. The Schedule backup attempts property in the Global Attributes properties. Then.9 gigabytes (a total of 9. The heads must move back and forth between tracks containing files for the respective streams. For example. Drive B Stream 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. multiplex the streams or send them to separate tapes. if the Schedule backup attempts property is set to 3. NetBackup can restart the failed stream without restarting the others. Figure 4-5 Multiple stream recommendations Recommended for best performance Client Drive A Stream NetBackup Server Back up each device with a separate stream that runs concurrently with streams from other devices. (See “Schedule backup attempts” on page 431. If the last stream fails after writing 1. each containing 2 gigabytes. For example. NetBackup retries only the last gigabyte stream.9 gigabytes is backed up). Multiple concurrent streams from a single physical device can adversely affect backup times.

■ The number of streams that can run concurrently. Note: For best performance. use only one data stream to back up each physical device on the client. For more information. ■ ■ Maximum concurrent jobs settings for the policy and client. For example. Each storage unit and each schedule has a maximum multiplexing setting. then 8 streams can run concurrently. Use the job details view to determine the files that are backed up by each of these jobs.) Number of the drives that are available. The maximum jobs settings also limit the maximum number of streams: ■ Maximum jobs per client (Host Properties > Master Server > Global Attributes.) . (See “Media multiplexing” on page 147. The backup selection list determines the total number of streams that are started.120 Policies Policy Attributes tab The Activity Monitor displays each stream as a separate job. Reduce administration—more 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.) (See “Maximum jobs per client” on page 432. Multiple concurrent streams from a single physical device can adversely affect backup times. assume that two storage units have one drive in each. The lower of the two settings is the limit for a specific schedule and storage unit. The following factors determine the number of streams that can run concurrently for a policy or client: ■ Storage unit and schedule multiplexing limit. Multiplexing on storage unit 1 is set to 3 and multiplexing on storage unit 2 is set to 5. Adjusting multiple data streams The following two aspects of multiple data streams are adjustable: ■ The total number of streams. see “Backup selections list directives for multiple data streams” on page 185. Backup times are affected because the device heads must move between tracks containing files for the respective streams. The NEW_STREAM directive lets you configure a fixed number of streams. The maximum streams are limited to the sum of the multiplexing limits for all drives available in the storage unit and schedule combinations. or you can allow the client dynamically define the streams. If multiplexing is set to 5 or greater in the schedules.

Policies Policy Attributes tab

121

■ ■

Limit jobs per policy (policy attribute).

Maximum data streams (Host Properties > Master Server > Client Attributes. (See “Maximum data streams” on page 384.) 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.

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 files on NetBackup 6.5 clients.) For more information, see the NetBackup for Microsoft SharePoint Portal Server 2003 Administrator’s 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.

122 Policies Policy Attributes tab

For more information see the NetBackup Snapshot Client Administrator’s Guide.

Policies Schedules tab

123

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

■ ■ ■

124 Policies Schedule Attributes tab

To create or change schedules 1 2 3 4 5 6 7 In the NetBackup Administration Console, expand NetBackup Management > Policies. 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 Schedules tab. The tab displays the Start Window and properties of existing schedules. The title bar displays the name of the current policy. Select the schedule to change and click Properties. The Change Schedule dialog appears. It contains the Attributes, Start Window, and Exclude Dates tab. 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 88.

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

Policies Schedule Attributes tab

125

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

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.

126 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 128. 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 401.

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

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

127

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 Administrator’s 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 Administrator’s 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 Administrator’s 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 Administrator’s Guide or the NetBackup for Oracle Administrator’s Guide.

128 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 policy’s 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 196.

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

129

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.

130 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

131

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.

132 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 directory’s 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

133

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.

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

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

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

135

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 day’s 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.

the remaining files seldom change and require monthly full backups only. For example. This wastes system resources because half the files need full backups only once a month. full backups are performed weekly on all the files. one incremental) that are each due to run: ■ ■ ■ if each is within the defined time window. For example. a schedule with a backup frequency of one year has priority over a schedule with a backup frequency of one month. A shorter frequency decreases restore time. Volume II. ensure that most of the files in a given policy change at about the same rate. assume that half of the files in a policy selection list change frequently enough to require a full backup every week. or to use synthetic backups. How NetBackup prioritizes each backup job that it adds to its worklist is explained in Chapter 2 of the NetBackup Administrator’s Guide. However. . To achieve the most efficient use of resources. If all the files are in the same 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. and if each is configured with the same frequency value.136 Policies Schedule Attributes tab ■ Shorter the time between full backups for the files that change frequently. 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. 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. For example. A better approach is to divide the backups into two policies. If NetBackup encounters a backup policy with two schedules (one full. NetBackup adds the job for the monthly full to the worklist and skips the other two. each with the appropriate backup schedule. the schedule that is first alphabetically runs first. Backup frequency determines schedule priority If more than one automatic schedule is due for a client within a policy.

Perform snapshot backups is selected. Refer to the NetBackup Snapshot Client Administrator’s Guide.Policies Schedule Attributes tab 137 Instant recovery The Instant recovery options are available under the following conditions: ■ The Snapshot Client option is licensed and installed. additional copies may be created at a later time using duplication. NetBackup creates the number of copies that is specified under Multiple copies. In this case. For example. (This option is sometimes referred to as Inline Copy. NetBackup creates a snapshot on disk only. or the number that the Maximum backup copies property specifies. the snapshot is not backed up to tape or to other storage. 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. Multiple copies With the Multiple copies attribute enabled. This option is required for the NAS_Snapshot method. To create more than four copies. 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. NetBackup can create up to four copies of a backup simultaneously. With this attribute enabled.) .) The Maximum backup copies property specifies the total number of backup copies that may exist in the NetBackup catalog (2 through 10). Retain snapshots for Instant Recovery is selected. (The pertinent storage unit settings are Maximum concurrent jobs and Maximum concurrent write drives. see “Maximum backup copies” on page 433. the unit needs four tape drives. transaction logs are not be truncated at the end of the backup. Snapshots only With this attribute is enabled. the snapshot persists on the client volume with a backup copy made to the storage unit on the media server. The storage units must be on the same media server with sufficient resources available for each copy. another policy can be used to back up the data to a separate device. to create four copies simultaneously in a Media Manager storage unit. whichever is fewer. For more information. ■ ■ Snapshots and copy snapshots to a storage unit When this attribute is enabled.

Also. For example. NetBackup does not permit any of the destinations to be a lifecycle. 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. to create four copies in the Multiple Copies dialog. NetBackup considers this to be one copy. . the duration of disk write operations match that of slower removable media write operations. created as part of basic disk staging storage unit configuration. 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. temporary staging storage unit to a final destination. Multiple copies and disk staging storage units Multiple copies can also be configured for a relocation schedule. Also. NetBackup automatically counts this copy against the Maximum backup copies value. if both Media Manager and disk storage units are specified. Multiple copies and storage lifecycle policies If the schedule is configured to create multiple copies. Since NetBackup eventually relocates a backup from the initial. Multiple copies does not support the storage units that use a QIC (quarter-inch cartridge) drive type. storage unit group. For example. the backup time that is required may be longer than for one copy.138 Policies Schedule Attributes tab If multiple original images are created simultaneously. or a lifecycle). the Maximum backup copies property must be set to five or more. Note: The Multiple copies option does not support the following storage types: third-party copies or optical devices.

It may be disabled if the destination for this policy is a storage lifecycle policy. NetBackup does not allow the two methods for created multiple copies to be enabled at the same time. The Configure Multiple Copies dialog appears. 5 In the Copies field.Policies Schedule Attributes tab 139 Multiple copies configuration To configure a schedule to create multiple copies 1 Expand NetBackup Management > Policies. select Multiple copies. Note: The Multiple Copies option may not be enabled for selection. that implies a multiple copies operation. Double-click an existing policy or select Actions > New > New Policy to create a new policy. specify the number of copies to create simultaneously. The maximum is four.) If the lifecycle has multiple destinations configured. 2 3 4 Select the Schedules tab. Double-click an existing schedule or click New to create a new schedule. then click Configure. or the number of copies that the Maximum backup . (The destination selection is on the policy Attributes tab. In the Attributes tab.

If a copy is configured to allow other copies to continue. If a Media Manager storage unit contains multiple drives. whichever is fewer. see “Retention” on page 144. and if Checkpoint restart is selected for this policy. Select whether the entire job should fail (fail all copies). to create four copies in the Multiple Copies dialog. the storage unit can be used for both the original image and the copies. 6 7 Specify the priority that the duplication job has compared to other jobs in the queue (0 to 99999). Select the retention level for each copy. For more information. 8 9 10 Select what should happen to the copy in the event that the copy does not complete. Specify the volume pool where each copy is stored. For more information. Select Any Available to allow NetBackup to select the storage unit at runtime. Specify the storage unit where each copy is stored. For more information. specify who should own the media onto which NetBackup writes the images: . Copy 1 is the primary copy. 11 For tape media. Note: To configure multiple copies as part of a relocation schedule for a basic disk staging storage unit.140 Policies Schedule Attributes tab copies setting specifies. the first successful copy is the primary copy. 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. If Copy 1 fails. only the last failed copy that contains a checkpoint can be resumed. or whether the remaining copies should continue. see “Maximum backup copies” on page 433. the Maximum backup copies property must be set to five or more. see “Multiple copies and disk staging storage units” on page 138.

2 3 Click the Staging Schedule button. A server group. the first successful copy is the primary copy. see “Staging backups to initial storage. but you want a media server to own the media. 12 Click OK. In the Copies field. To configure a basic disk staging relocation schedule to create multiple copies 1 Expand NetBackup Management > Storage Units. then final storage” on page 238. specify the priority that NetBackup should assign to the duplication jobs have compared to other jobs in the queue. select the Temporary staging area checkbox and configure the other storage unit selections. specify the number of copies to create simultaneously. The alternate server that is indicated is allowed to read a backup image originally written by a different media server. 4 5 6 7 . None specifies that the media server that writes to the media owns the media. Select whether to use an alternate read server by checking Use alternate read server. The Configure Multiple Copies dialog appears. Any media server with access to the shared pool of disk can access the images. Select Multiple copies.Policies Schedule Attributes tab 141 ■ Any lets NetBackup choose the media owner. To create a new basic disk staging storage unit. No media server is specified explicitly. Select a schedule type and schedule when the policy should run. For more information on basic disk staging storage units. All media server groups configured in the NetBackup environment appear in the drop-down list. Copy 1 is the primary copy. In the Attributes tab. 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. Range: 0 (default) to 99999 (highest priority). Images on shared disk are not owned by any one media server. until the policy is saved. The Disk Staging dialog appears. ■ ■ Note: These settings do not affect images residing on disk. If Copy 1 fails. then click Configure. either a media server or server group. or Select Actions > New > New Storage Unit to create a new basic disk staging storage unit. ■ ■ Double-click an existing basic disk staging storage unit.

For example. If a Media Manager storage unit has multiple drives. or whether the remaining copies should continue. 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. either a media server or server group. 9 10 Select the retention level for each copy. Restoring from a specific backup copy Usually NetBackup restores from the primary copy of an image. see “Retention” on page 144. 11 Select what should happen in the event that the copy does not complete. If: ■ ■ a copy is configured to allow other copies to continue. For more information. Select whether the entire job should fail. However. see “Multiple copies and disk staging storage units” on page 138. Click OK. it can be used for both the source and the destination. None specifies that the media server that writes to the media owns the media. the Maximum backup copies property must be set to five or more. then only the last failed copy that contains a checkpoint can be resumed. but you want a media server to own the media. it is possible to restore from a specific backup copy other than the primary copy. Images on shared disk are not owned by any one media server. ■ ■ Note: These settings do not affect images residing on disk. to create four copies in the Multiple Copies dialog. Specify the volume pool where each copy is stored. No media server is specified explicitly.142 Policies Schedule Attributes tab The Maximum backup copies Global host property must include an additional copy beyond the number of copies indicated in the Copies field. To . specify who should own the media onto which NetBackup writes the images: ■ Any lets NetBackup choose the media owner. and Checkpoint restart is selected for this policy. 12 For tape media. All media server groups configured in the NetBackup environment appear in the drop-down list. A server group. 8 Specify the storage unit where each copy is stored. Any media server with access to the shared pool of disk can access the images. For more information.

only those storage lifecycles with the same data classification are displayed. If no policy volume pool is specified. 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 policy’s Attributes tab. Choose the storage unit or lifecycle from the drop-down list of previously configured storage units and lifecycle policies. and Restore online help or the NetBackup Commands for Windows. NetBackup uses the volume pool that is specified in the Policy volume pool General Attribute. If the policy is for a NetBackup catalog. no storage units or lifecycles have been configured. use the bprestore command. ■ 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. do not select the check box. NetBackup uses NetBackup as the default. See the Backup. select the check box. For more information. ■ Note: Storage lifecycle policies cannot be selected within the multiple copies configuration dialog. Or. see “Policy storage” on page 97. ■ To override the volume pool that the Policy Volume Pool General Attribute specifies. If the list is empty. see “Data classification” on page 90. specified storage unit or storage lifecycle for this schedule. NBU-Catalog policies use CatalogBackup. 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. For more information. The . Archive. Choose the volume pool from the list of previously configured volume pools. ■ Click the check box to override the Policy storage selection that is indicated in the Attributes tab. If a data classification is indicated for the policy. To use only the policy storage selection that is indicated by the Policy storage setting in the Attributes tab.Policies Schedule Attributes tab 143 do so. do not enable the check box. whether to use a different. To use the policy volume pool.

but you want a media server to own the media. All server groups that are configured in the NetBackup environment appear in the drop-down list. Other data (preliminary documents. if the retention is two weeks. The retention indicated in the lifecycle is followed instead.) 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. Specify one of the following: ■ Any lets NetBackup choose the media owner. select a time period (or level) from the drop-down list. When the retention period expires. data can be restored from a backup that this schedule performs for only two weeks after the backup. For example. the files in the backup are unavailable for restores. select the check box. if day-to-day changes are critical. A server group allows only those servers in the group to write to the media on which backup images for this policy are written. If a policy is configured to back up to a lifecycle. Retention The Retention attribute specifies how long NetBackup retains the backups. Choose the media owner from the drop-down list To use the policy media owner. To set the retention period. do not select the check box. NetBackup chooses a media server or a server group (if one is configured). A server group. ■ ■ To override the media owner that the Media Owner General Attribute specifies. If incremental backups only track work in progress toward monthly reports. for example) have legal requirements that determine the retention level. Some data (financial records. for example) can probably be expired when the final version is complete. (See “Adding storage destinations to a lifecycle policy” on page 251. A backup’s retention also depends on what needs to be recovered from the backup. so override settings are not needed. keep all the incremental backups in addition to the full backups for as long as the data is needed. . the Retention attribute in the schedule is not followed.144 Policies Schedule Attributes tab rules for shared disk media are more flexible. None specifies that the media server that writes the image to the media owns the media. No media server is specified explicitly. For example. NetBackup deletes information about the expired backup. NetBackup uses the media owner that is specified in the Media Owner General Attribute. Once the backup expires.

place the files and directories with longer retention requirements in a separate. Plan to create separate policies for the data that falls outside of the retention requirement guidelines. (Note that a total directory or disk restore with incremental backups requires the last full backup plus all incremental backups. ■ One method to implement off-site disaster recovery is to use the duplication feature to make a second copy for off-site storage. A complete restore requires the previous full backup plus the most recent cumulative-incremental backup. . Use the NetBackup import feature to retrieve expired backups. Note the files or the directories that have retention requirements outside of these guidelines. ■ ■ Ensure that adequate retention periods are configured. One week provides enough of a margin to ensure that the current cumulative-incremental backup does not expire before the next successful one occurs. For example. For example. Another consideration for data retention is off-site storage of the backup media. request the media from the facility. Off-site storage protects against the disasters that occur at the primary site. 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. if the frequency setting is one day. (The frequency is how often the backup runs). Cumulative incremental backups: Always specify a time period that is longer than the frequency setting for the schedule. Precautions for assigning retention periods Full backups: Always specify a time period that is longer than the frequency setting for the schedule. Schedule longer retention times for the separate policies without keeping all policies for the longer retention period.Policies Schedule Attributes tab 145 expire the incremental backups sooner. For example. specify a retention period of one week.) Consider configuring an extra set of schedules to create the backups to use as duplicates for off-site storage. if the frequency for a full backup is one week. To restore the data. regardless of the method that is used for off-site storage. Another approach is to send monthly or weekly full backups to an off-site storage facility. Rely on the full backups for long term recovery. Establish some guidelines that apply to most of the data to determine retention periods. specify a retention period of two to four weeks. Set the retention period to infinite for the backups that must be kept for more than one year.

If you keep only one retention level on each volume. NetBackup also uses the level to determine the volume to use to store a backup. select Allow multiple retentions per media on the Media host properties. NetBackup stores each backup on a tape volume that contains existing backups at the same retention level. For example. When NetBackup encounters a backup with a different retention level. do not use any more retention levels than necessary. ■ NetBackup does not track backups after the retention period expires. For more information. even if all other backups on the volume have expired. One small backup with an infinite retention would prevent a volume from being reused. see “Mixing retention levels on tape volumes” on page 146. The retention periods are indexed to different levels.146 Policies Schedule Attributes tab Differential incremental backups: Always specify a time period that is longer than the period between full backups. this approach results in more efficient use of media. assign a longer retention period to full backups than to incremental backups. Note: Retention levels may be mixed on disk volumes with no restrictions. save the incremental backups for two weeks. see “Media properties” on page 446. To mix retention levels on volumes. If a backup has a retention level of 2. Multiple retention levels increase the number of required volumes. A complete restore requires the previous full backup plus all subsequent incremental backups. it switches to an appropriate volume. Assign an adequate retention period as recovering files after the retention period expires is difficult or impossible. . ■ ■ Changing retention periods Set the default retention periods by selecting NetBackup Management > Host Properties > Master Server > Double-click on master server > Servers > Retention Periods. the default retention period for level 0 is one week. Archive schedules normally use an infinite retention period. For example. It may not be possible to restore all the files if the full backup expires before the incremental backups. Within a policy. see “Retention Periods properties” on page 462. For more information. For more information. if full backups occur weekly. Because tape volumes remain assigned to NetBackup until all the backups on the tape have expired. Mixing retention levels on tape volumes By default. NetBackup stores it on a tape volume with other backups at retention level 2.

then final storage” on page 238. For more information on basic disk staging storage units. Volume II.) A Final destination volume pool is the volume pool where images are swept from the volume pool on the basic disk staging storage unit. The option cannot be selected in those instances. Multiplexing sends concurrent backup jobs from one or several clients to a single drive and multiplexes the backups onto the media. (A relocation schedule is created as part of a basic disk staging storage unit configuration. Final destination volume pool If the schedule is a relocation schedule. 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. see Chapter 3 in the NetBackup Administrator’s Guide.Policies Schedule Attributes tab 147 Media multiplexing The Media multiplexing attribute specifies the number of jobs from the schedule that NetBackup can multiplex onto any one drive. Note: Some policy or some schedule types do not support media multiplexing. then final storage” on page 238. a Final destination storage unit must be indicated. a Final destination volume pool must be indicated. Final destination storage unit If the schedule is a relocation schedule. (A relocation schedule is created as part of a basic disk staging storage unit configuration. For more information on how to configure multiplexed backups and the ramifications of multiplexing. For more information on basic disk staging storage units.) A Final destination storage unit is the name of the storage unit where the images are swept to from the disk storage unit. see “Staging backups to initial storage. . where 1 specifies no multiplexing. Specify a number from 1 through 32. see “Staging backups to initial storage.

Move the cursor and the value changes. Release the button. a resolution of 10 minutes allows time window adjustments by 10-minute increments. Configure time windows so that they satisfy the requirements necessary to complete a task or job. The time is displayed based on a 24-hour clock. The Time at cursor field reflects the day and time that corresponds to the current position of the cursor. archives. press the left mouse button.148 Policies Start Window tab Start Window tab The Start Window tab provides controls for setting time periods during which NetBackup can start backups. 2 When the cursor is over the chosen start time. To create a schedule window 1 Position the cursor over the day and time that the time window is to open. ■ The Modify Day and Start Time fields display the day and time the time window opens. 1 am is 01:00 and 11 pm is 23:00. Drag the cursor to the day and time when the window is to close. create a different window for the backups that open each day for a specific amount of time. 12 pm is 00:00. For example. Time periods are referred to as time windows. change the value in the Resolution field. . For example. or keep the window open all week. Time window Current cursor position To set the resolution for start or end time settings. or basic disk staging relocation when using this schedule. For example.

Both schedules have three clients with backups due. Be sure to specify enough time to allow all clients in the policy to complete a backup. all backups may not have a chance to start. ■ Duration example The following figure represents the effect of schedule duration on two full backup schedules. Client A1 Client A2 Client A3 starts within the Schedule A window but doesn’t complete until after the Schedule B start time. 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. for example. (Delays due to unavailable devices. Schedule A does not leave enough time for the Schedule B backups. To create time windows on successive days 1 2 Move the cursor over the chosen start time. Client A3 illustrates that if a backup starts. Consider allowing extra time in the schedule in case the schedule starts late due to factors outside of NetBackup. . The Duration indicates the scope of the time window that is based on the start time and the end date and times.) Otherwise. The start time for schedule B begins shortly after the end time for previous schedule A.Policies Start Window tab 149 ■ The End Day and End Time fields display the time the time window closes. Client B3 must wait until the next time NetBackup runs Schedule B. Drag the cursor to the time that the first time window is to close. it runs to completion even if the window closes while the backup is running. Press the Shift key and the left mouse button. Client A3 Client B1 Client B2 Client B3 is unable to start because the window has closed.

Press the Ctrl key and drag to copy the window to another day. Position the cursor over the center of the selected window so the cursor changes to crossed arrows. . To move a time window 1 2 3 Select the time window. Click Delete. and drag the cursor down to duplicate the window on successive days. Note: If blank days immediately following the selected window. To copy a time window to another day 1 2 Click on an existing time window to select it. To delete all time windows Click Clear. Position the cursor over the end of the window that is to change. To delete a time window 1 2 Select the time window. Press the left mouse button and drag the time window to the chosen location within the schedule area. To change a time window 1 2 3 Select the time window. click Duplicate to duplicate the selected time window on those days. Press the left mouse button and drag the time window to the chosen length.150 Policies Start Window tab 3 Keep the buttons pressed. The cursor changes to a two-headed arrow. Duplication stops when it reaches a day that already contains a defined schedule.

Use the controls at the top of the calendar to change the month or year. Enter the month.Policies Exclude dates tab 151 Exclude dates tab Use the Exclude Dates tab to exclude specific dates from a schedule. The Exclude Dates tab displays a 3-month calendar. 3 After the dates are selected. and year in the Date selection dialog. Click OK. To exclude a date from the policy schedule 1 Select the Exclude Dates tab. 2 Use one of the following methods to indicate a date: ■ ■ Click the date on the calendar to be excluded. select another tab to make changes or click OK to close the dialog. . Click New. The date appears in the Exclude Dates list. day.

152 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. and specific dates can be added to a recurring schedule. 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 Specific dates run day option to schedule specific dates for a task to run. Schedule by specific dates A task can run on specific dates rather than follow a recurring schedule. Calendar-based schedules provide several run day options for determining when a task runs. . Use the controls at the top of the calendar to change the month or year.

and year in the Date Selection dialog. After the dates are selected. The date appears in the Specific Dates list.Policies Calendar schedule tab 153 To schedule a task on specific dates 1 In the Calendar Schedule tab. A check mark on a day indicates that the task is scheduled to run on that day of that week each month. Click New. The matrix is not a calendar. select another tab to make changes or click OK to save and close the dialog. select Specific Dates. schedule a task to run on the first and the third Thursday of every month. Or. Schedule by recurring week days The Recurring Week Days option presents a matrix of days and weeks to schedule a task. day. Enter the month. schedule a task that runs the last week in every month. Click OK. . select it in the calendar schedule list and click Delete. For example. 2 Use one of the following methods to indicate a date: ■ ■ Click the date in the calendar. 3 4 To remove a date.

regardless of the actual date. Click the name of the day column header to select or clear the corresponding day for each week of the month. select another tab to make changes or click OK to save and close the dialog. click Deselect All to remove existing selections from the matrix. click a check box to clear it. Matrix 2 3 4 5 6 If necessary. regardless of the number of weeks in the month. After the dates are selected. Or. 7 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. 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. select Recurring Week Days. Click a check box in the matrix to select the day.154 Policies Calendar schedule tab To schedule a recurring weekly task 1 In the Calendar Schedule tab. . The task is scheduled.

After the dates are selected. Select the Last Day check box to run the schedule on the last day of the month. After the policy is created. How calendar scheduling interacts with daily windows Daily windows are taken into account. Select the button for each day to be included in the run schedule. For example: . Windows that span midnight become two separate windows for calendar schedules.Policies Calendar schedule tab 155 To schedule a recurring monthly task 1 In the Calendar Schedule tab. click Select All. To select all of the days in every month. select another tab to make changes or click OK to save and close the dialog. the initial backups may appear as though two backups have run within the same window. click Deselect All to remove existing selections from the matrix. even when calendar-based schedules are used. the backup runs once during any window that is open. Click the button again to deselect the day. Matrix 2 3 4 5 6 If necessary. If the calendar schedule indicates that today is a run day. select Recurring Days of the Month. regardless of the date.

The windows are configured to be open from 6 p. Monday through Saturday. a job runs as soon as the window opens at 6 p. 3 4 No backups from the policy exist yet because it is a new policy.. the schedule is set up to run on every week day.m. The backups continue to run soon after midnight from that time forward.) so the job is due and runs again. it is a new day (Tuesday) and a window is open (until 6 a. At midnight. 2 In the Calendar Schedule tab. every day of the week).m.m. Sunday through Saturday. Notice how the backup runs before midnight. Since today (Monday) is a run day. then again immediately after midnight. through 6 p.m.m. .156 Policies Calendar schedule tab 1 A new backup policy is created on Monday afternoon. until 6 a.m. Both jobs are valid since both have different run days and windows are open at both times (6 a. Windows that span midnight become two separate windows for calendar schedules.

NetBackup usually queues the user job. The days that are chosen for backups depends on how you want to distribute the backup load. Leave these values blank for other days. click the Help button in the Schedule dialog. Planning user backup and archive schedules To plan schedules for user backups and archives.Policies Calendar schedule tab 157 To run jobs at 6 p. consider the following: ■ What are the most convenient times for users to perform backups? If possible. 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. For details on how calendar-based scheduling works with backup windows. The job is not queued if there is a limiting setting. A user backup schedule may be included in a policy that contains automatic backup schedules. For examples of automatic schedule configuration. The best times for automatic backups are usually nights and weekends. to have all backups occur on Saturday. use a frequency of one day instead of recurring days in the Calendar Schedule tab. references to backups also apply to the backup portion of archive operations unless otherwise noted. Then. During an archive. instead of midnight. Otherwise.” Considerations for user schedules In order for users to perform backups and archives. Restores can be performed at any time and are not scheduled. when client and network activity is lowest. then deletes the files from the local disk if the backup is successful.) . click the link “Automatic-backup schedule examples. In this manual. NetBackup first backs up the selected files. the backups can adversely affect client and network performance and take longer to complete. the Limit Jobs per Policy policy attribute or the Maximum Jobs per Client Global Attributes host property. you must create a schedule that allows user backups.m. see “How calendar scheduling interacts with daily windows” on page 155. Caution: An archive is different from a backup. 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. For example. (For example. create a backup window only for Saturday.

see “Retention” on page 144. ■ Caution: If the retention period expires for a backup. (See the NetBackup NetWare user’s guide). On UNIX clients. Using a specific policy and user schedule To use a specific policy or schedule for user backups or archives. Click File > NetBackup Client Properties and select the Backups tab. If you create separate policies for user backups or archives. User jobs delay automatic backups and can cause backups to miss the backup window. perform the following on the client: ■ On Microsoft Windows clients. it can be difficult or impossible to restore the archives or backups. In user backup schedules. since the disk copy of the files is deleted. specify the policy and schedule with BPARCHIVE_POLICY. See “Limit jobs per policy” on page 103 and “Maximum jobs per client” on page 436. On NetWare target clients. For more information. 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. no backup selection list is necessary because users select the objects before they start the backup or archive. ■ Which storage unit should be used for user backups? Use a different storage unit to eliminate conflicts with automatic backups. ■ How long should an archive be kept? Consider setting the retention period for archives to infinite. specify the policy and schedule with backup_policy and backup_sched entries in the bp. BPARCHIVE_SCHED. Archive. however.158 Policies Calendar schedule tab If the automatic backup continues to run. Specify the backup policy and backup schedule.ini file. the user job misses the backup window. the considerations are similar to those for automatic backups. Creating separate policies for user schedules User backup and archive schedules do not need to be in a policy separate from automatic backup schedules. BPBACKUP_POLICY. ■ ■ .conf file. start the Backup. and Restore client interface. or BPBACKUP_SCHED options in the bp.

This policy has daily and weekly automatic schedules. Store on 8mm tape.m. Run Mondays every week between 6 p. and 6 a. backup selection list. Keep one month. User can run any day between 8 a.m.m.m. and 6 a. All backups go to 8mm tape.m. and schedules of two example backup policies.m. Keep one year. Store on 8mm tape. and 6 a. Example Policy 2 Clients pluto mercury Backup Selection List C:\ D:\Docs Schedules Daily Incremental Backups ■ ■ ■ Run every day between 6 p. and 6 a. and neptune.m. Store on 8mm tape. Store on 8mm tape. Keep one month.m. Policy 1 specifies that files in C:\ and D:\Docs be backed up for the clients mars.m. and 5 p. Store on DLT tape.m. jupiter. Weekly Fulls Backups ■ ■ ■ Monthly Full Backups ■ ■ ■ . Example Policy 1 Clients mars jupiter neptune Backup Selection List C:\ D:\Docs Schedules Daily Incremental Backups ■ ■ ■ Run every day between 6 p.Policies Example policies 159 Example policies The following tables show the clients. Keep 14 days.m. Keep 14 days. Run Tuesdays every week between 6 p. Weekly Fulls Backups ■ ■ ■ User Backups ■ ■ ■ Policy 2 contains different scheduling requirements: the policy contains the monthly full backups that are written to DLT tape. and 6 a. and a user backup schedule.m. Store on 8mm tape. Run Sundays every month between 6 p. Keep one year.

The storage unit and volume pool settings apply to all files that are backed up by the policy. In this example.160 Policies Example policies Policy planning guidelines for backups Policies can meet the needs of a wide variety of clients in a single NetBackup configuration. we may find that we need more than one policy for mercury. Later. For example. mercury is a file server that contains a large amount of data. 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. The following procedure provides guidelines for planning. In this example. Initially. In other cases. In some instances. 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. most clients in an engineering department create the same types of files at similar levels of importance. plan your policies before starting configuration. include mercury in policy S1 and the workstations in another policy (WS1). Clients that are used for similar tasks generally have much in common regarding the backup requirements. even if other factors are the same. create separate policies for the files. In this example. a separate policy (S2) is used for . assume that the clients are in the same work group. you need to subdivide the clients and include them in the separate policies that are based on their backup requirements. To avoid long backup times. you can create a single policy for each group of clients. If files have special storage requirements. Group the clients Divide clients into groups according to the types of work the clients perform. To take the best advantage of the capabilities of policies. such as schedules. we’ll try to cover all of the clients in the same backup policy.

Other files on mercury go on 8mm tape. If some files change infrequently compared to other files. If it is necessary to keep backups for some files on separate media. Consider the following factors to create schedules in a policy: ■ Best times for backups to occur. together in a policy where full backups are retained for only four weeks. add the media for that volume pool. How long backups need to be kept.Policies Example policies 161 D:\h002\DevExp and D:\h002\DesDoc on mercury. create a policy that specifies a unique volume pool for those backups. Each schedule has a retention setting that determines how long NetBackup keeps the files that are backed up by the schedule. all files should have similar retention requirements. C:\ on mercury is in a different policy (S3). The C:\ drive on the workstations is also in a separate policy (WS2). back up the files on a different schedule. create more policies. In our example. Because the schedule backs up all the files in the backup selection list. we can back up all clients during the same hours so additional policies are not necessary. Those files are sent to DLT tape. ■ ■ . create different policies for night-shift and day-shift clients. To use a different schedule. In our example. Then. To back up different clients on different schedules. Policy S1 Clients mercury Files C:\ D:\User D:\h001 E:\h002\Projects E:\h002\DevExp E:\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. For example. How frequently the files change. create another policy that has an appropriate schedule and then include the files and clients in that policy. Do not include the files whose full backups must be retained forever.

include Windows XP and Windows 2000 clients in a MS-Windows-NT policy. see “Policy type” on page 94. For more information. You must use the correct policy type for each client. Policy Clients S1 mercury File selections Frequency of Change high Storage 8mm Frequency of Automatic Backups ■ ■ ■ D:\User D:\h001 E:\h002\Projects E:\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 C:\ low 8mm ■ ■ S4 mercury E:\h002\DesDoc high DLT ■ ■ ■ ■ WS1 mars jupiter neptune D:\User D:\Programs D:\User D:\Programs D:\User D:\Programs D:\Util C:\ C:\ C:\ 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. Select this attribute if a UNIX client has NFS mounted files to be backed up. Follow NFS. For example. Consider placing these clients in a separate policy so problems ■ .162 Policies Example policies In the example. E:\h002\DesDoc requires full backups every 12 weeks and those backups must be retained much longer than the other files on mercury. General attributes include the following: ■ Policy Type. E:\h002\DesDoc on mercury is in a different policy (S4).

see “Follow NFS” on page 107. ■ Backup Network Drives. create a new policy for E:\h002\Projects. For more information. Select this attribute to back up the files that the client stores on network drives (applies only to MS-Windows-NT policies). However.Policies Example policies 163 with NFS do not affect the other clients. use multiplexing for the slower clients that produce small backups. Evaluate backup times Evaluate total backup times for each schedule and further subdivide policies to reduce backup times to an acceptable level. Job Priority. For example. The Multiplexing and Allow Multiple Data Streams options also allow backup policies to be processed in parallel. In our example. Compression. For more information. NetBackup processes files within a backup selection list serially. if the backup of D:\User. see “Compression” on page 111. Note that the time to compress can increase backup time and make it unsuitable to use for all clients. and E:\h002\Projects on mercury takes too much time. Back up E:\h002\Projects separately to reduce backup time. Use this attribute to control the order in which NetBackup starts the backups. in the order they appear in the backup selection list. The higher-performance clients that produce long backups are likely to use drives fully and not benefit from multiplexing. see “Job priority” on page 104. ■ ■ Maximize multiplexed backups Create separate policies as necessary to maximize the benefits of multiplexed backups. separate policies can reduce the total backup time for the server mercury. For more information. In addition to reducing the backup time for each policy. To maximize drive use. Policy S5 has the same requirements as S1. no extra policies are required because of general attribute settings. The clients with the higher priority are backed up first. D:\h001. see “Backup network drives” on page 106. . Set this attribute if you want a client to compress its backups before sending them to the server. For more information. separate policies are processed in parallel if enough drives are available and the maximum jobs attributes are set to allow it.

Volume II.164 Policies Example policies See “Allow multiple data streams” on page 118 in this guide and ”Using multiple NetBackup master servers” in Chapter 3 of the NetBackup Administrator’s Guide. Policy S1 Clients File selections Frequency of Change high Storage 8mm Frequency of Automatic Backups ■ ■ ■ mercury D:\User D:\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 E:\h002\DevExp high DLT ■ ■ ■ S3 mercury C:\ low 8mm ■ ■ S4 mercury E:\h002\DesDoc high DLT ■ ■ ■ ■ S5 mercury D:\h002\Projects high 8mm ■ ■ ■ WS1 mars jupiter neptune D:\User D:\Programs D:\User D:\Programs D:\User D:\Programs D:\Util C:\ C:\ C:\ high 8mm ■ ■ ■ WS2 mars jupiter neptune low 8mm ■ ■ Daily Incr 4 Weeks Full .

Policies Clients tab

165

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

In the right pane, double-click the policy you want to change. Select the Clients tab and click New. In the highlighted field, type the name of the client or browse to find and select the client. Press Enter. In the Client Name field, type the name of the client. 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.

■ ■

166 Policies Clients tab

Add only clients with the hardware and the operating systems that this policy supports.

6

If the Detect operating system checkbox is not selected, you are asked to choose the hardware and the operating system. Add only clients with the hardware and the operating systems that the policy will supports. For example, do not add a Novell NetWare client to an MS-Windows-NT policy. Click OK to close the Change Policy dialog or select another tab. To add another client, click New. Click Cancel to cancel the changes that you have not yet added and close the dialog.

7

Policies Backup Selections tab

167

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 167. 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 169.
■ ■

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

Backup selections list for standard policies
Standard, Exchange, and Lotus Notes policy types list paths and directives in the backup selection list.

168 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

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, at the end of the list, click under the last entry in the backup selections list, then click New. An edit box appears.

Click to browse for files or folders Click to select from a list of directives

Edit box

5

Select a path or directive:

Click the folder icon to browse to a remote folder to select a path. For file path information, see “Path rules for Microsoft Windows clients” on page 174. Click the directives icon to browse to a directive.

Policies Backup Selections tab

169

The Select Directive dialog appears. Click the arrow next to the Directive field and select a directive. Click OK to include the directive to the backup selections list on the Selections tab.

If you use many directives, you might want to add the entire set of directives. Then, edit the backup selections list to move and delete directives as required

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

To move an entry, select the entry, then use the Up and Down buttons, mouse, or keyboard to move an entry. To delete an entry, select the entry and click Delete. To rename an entry, select it and click Rename. An edit box opens around the entry to modify it.

■ ■

8

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

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 In the NetBackup Administration window, expand NetBackup Management > Policies.

170 Policies Backup Selections tab

2 3

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, at the end of the list, click under the last entry in the backup selections list, then click New. An edit box appears. Add the backup selections:

4

Enter a script into the text box. Scripts require that the full path be specified. Be sure that the scripts that are listed are installed on each of the clients that are specified on the Client tab. Click the folder icon to browse to a remote folder to specify script paths for a client.

5

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 Backup Selections tab. To add an entry, click New. An edit box appears. Add the backup selections:

Templates:

Type only the template file name, for example,
weekly_full_backup.tpl, or,
Click the Template button. For Oracle policies, choose Oracle_RMAN or Oracle_XML_Export from the Template set list. Then, choose a template name in that set from the Template list. You can also add all available templates by clicking Add all templates to the backup selections list. Use the full path of the client and the file name for the script you want to include. Or, Click Browse to locate the script in the client Browse window. Click OK to add the selection. Be sure that the shell scripts that are listed are installed on each of the clients that are specified in the Clients tab.

Scripts:

6

To change the order of the backup selections, select one and click Up or Down.

Policies Backup Selections tab

171

7

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 client’s 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.

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

172 Policies Backup Selections tab

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 174. 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 install_path\NetBackup\bin\goodies. 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.

2

3

Example log messages
The following examples show the log message that appear when files on a client are not found. For information on check_coverage, see the comments in the script. Assume that the backup selections list contains the path c:\worklist that is not present on all clients. NetBackup backs up C:\worklist on the clients

Policies Backup Selections tab

173

where it exists. For other clients, the Problems report or the All Log Entries report shows a message similar to the following:
9/1/06 8:28:17 AM carrot freddie Info from client freddie: TRV -
object not found for file system backup: C:\worklist

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

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

“Path rules for Microsoft Windows clients” on page 174. “Path rules for NetWare NonTarget clients” on page 179. “Path rules for NetWare Target clients” on page 181. “Path rules for clients running extension products” on page 181.

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

175

Allowable wildcard characters are the same as those allowed in Windows paths: * ? For more information, see “Using wildcards in NetBackup” on page 630. 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 190. Exclude specific files from backups by creating an exclusion list on the client. For more information, see “Excluding files from automatic backups” on page 191.
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.

176 Policies Rules to indicate paths in the backup selections list

Figure 4-9

Disk-image backups

Must select Full backup as backup type

Logical drive name in the backup selection list

Select Full backup as the backup type to perform a disk-image backup. 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.

Policies Rules to indicate paths in the backup selections list

177

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. 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 that’s 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.

178 Policies Rules to indicate paths in the backup selections list

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

Policies Rules to indicate paths in the backup selections list

179

2

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

3

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

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.

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

it is the system with the NetWare file systems to be backed up.180 Policies Rules to indicate paths in the backup selections list depends on the data. and USER. For more information. include the file extension and omit the slash from the end of the name. ■ TS is the Target Service.com) it is a DOS workstation.TXT ■ All components in a path must show upper and lower case letters as they appear in the actual path on the client.For more information. resources are the specific resources on the target service. SYS. NetWare file systems and DOS workstations each have TSAs. ■ ■ directory/file is the directory and file that are in the resource (if it is a path to a specific file). BINDERY. Precede each component in the path with a forward slash. follow it with a forward slash (/). Enter one path per line. For example. Give the server access to each path or the scheduled backup fails. in the case of the DOS TSA (tsasms. see “Using wildcards in NetBackup” on page 630. For example. Begin all paths with a forward slash (/). use the Allowed scheduled access command on the Backup menu in the NetBackup interface on the NetWare client. For example. enter a forward slash (/) followed by the client name and another forward slash: /TILE/ The following example backs up SYS. To provide this access. see the NetBackup for Novell NetWare Client Administrator’s Guide.NetWare File System/TILE/SYS/DOC/ Observe the following rules for paths: ■ ■ ■ ■ If the last component is a file. and USER file systems under the file system TSA on a client that is named tile: . In the case of a NetWare file system TSA. To back up all NetBackup for NetWare clients that are in the policy. The trailing slash is not required but is a reminder that the path points to a directory instead of a file. If the last component in the path is a directory.NetWare File System/TILE/SYS/DOC/TEST. which is the NetWare entity that contains the data that the selected TSA handles. /TILE/TILE. it can be NetWare file systems such as BINDERY. enter only one forward slash (/) on a line: / ■ ■ ■ To back up an entire NetBackup for NetWare client. Wildcard usage is the same as for Windows clients. /TILE/TILE.

see “Using wildcards in NetBackup” on page 630. The example is from an MS-Windows-NT policy with Allow multiple data streams enabled: NEW_STREAM D:\Program Files NEW_STREAM . /NETWARE/ /SYSTEM/ /BINDERY/ The following example backs up the targets: NETWARE. Begin all target names with a forward slash (/). see the NetBackup Administrator’s Guide for Novell NetWare Clients. Path rules for NetWare Target clients For NetWare clients that are running the Target version of NetBackup client software. ■ ■ ■ ■ Enter one target per line. See the NetBackup for Novell NetWare Client Administrator's Guide. The following example is a backup selections list that contains the NEW_STREAM directive.NetWare File System/TILE/SYS/ /TILE/TILE. 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. Wildcard usage is the same as for Windows clients. Snapshot Client or NetBackup for MS-Exchange. 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. SYSTEM. (For example.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. All target names must be in upper case. The available directives depend on the policy type and whether the Allow multiple data streams attribute is enabled for the policy. For more information.) 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.Policies Rules to indicate paths in the backup selections list 181 /TILE/TILE.NetWare File System/TILE/BINDERY/ /TILE/TILE. For more information.

SYSTEM_STATE directive The System_State:\ directive is a valid directive only to back up Windows 2000/XP machines. see “Files that are excluded from backups by default” on page 190. Windows 2003 Server machines recognize the System_State:\ directive and behave as if following the Shadow Copy Components:\ directive. ALL_LOCAL_DRIVES directive Use the ALL_LOCAL_DRIVES directive to back up all local drives except for those drives that use removable media. 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 188. For information on files and the directories that NetBackup automatically excludes from backup. If the machine is not Windows 2000/XP or a Windows 2003 Server. 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. the System_State:\ directive does not have any effect. A message informs the user that this directive translation has occurred. If the machine is Windows 2000/XP.182 Policies Rules to indicate paths in the backup selections list C:\Winnt The NEW_STREAM directive is discussed in “Backup selections list directives for multiple data streams” on page 185. the list of items that are backed up can include the following: ■ ■ ■ ■ ■ ■ ■ ■ Active Directory COM+ Class Database Cluster Database IIS Database Registry Boot Files and Protected Files SYSVOL Certificate Server .

The files that comprise the registry can be found in the following location: %SystemRoot%\SYSTEM32\Config At a minimum. the registry is backed up in the process of regular file system backups. This directive ensures that all of the necessary components are backed up. which can include: ■ ■ ■ ■ ■ ■ ■ . 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 Windows Management Instrumentation Remote Storage Dynamic Host Configuration Protocol Terminal Server Licensing ■ System Service writers. The Volume Shadow Copy components include the following: ■ System State writers. 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.Policies Rules to indicate paths in the backup selections list 183 On Windows 2000 machines. The Shadow Copy Components:\ directive specifies that all of the Volume Shadow Copy component writers get backed up.

■ Directives for multiple data streams If the Allow multiple data streams general attribute is set for a policy. Volume II. The following policy types have their own backup selections list directives: ■ ■ ■ ■ ■ AFS FlashBackup NDMP Lotus-Notes MS-Exchange-Server For example. see the NetBackup guide for the option. NetBackup passes policy-specific directives to the clients along with the backup selections list. Directives for specific policy types Some directives apply only to specific policy types and can appear only in backup selections lists for those policies.184 Policies Rules to indicate paths in the backup selections list ■ Background Intelligent Transfer Service ■ User Data writers. which include any items that are not required by the machine to operate. Active Directory Application Mode. a category that is intended for future NetBackup releases. the following directives can appear only in the backup selections list of an AFS policy: CREATE_BACKUP_VOLUMES SKIP_SMALL_VOLUMES Except for AFS. . Other Data writers. see the NetBackup Administrator’s Guide. For information on other policy types and associated backup selections list directives. see “Backup selections list directives for multiple data streams” on page 185. these policy types can be used when their associated separately-priced option is installed. For information about AFS directives. For example. the following directives can be used in the backup selections list: ■ ■ ■ ■ NEW_STREAM ALL_LOCAL_DRIVES UNSET UNSET_ALL For usage rules. The clients then perform the appropriate action according to the directive.

If this directive is used in a backup selections list. it can also appear elsewhere in the list. NEW_STREAM directive and multiple data streams The NEW_STREAM directive is recognized only if Allow multiple data streams is set for the policy. ■ ■ . the backup is performed in the administrator-defined streaming mode. If it appears on the first line. All file paths between NEW_STREAM directives belong to the same stream. 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. The start of a new stream (a NEW_STREAM directive) defines the end of the previous stream. use only one data stream to back up each physical device on the client. The heads must move back and forth between tracks containing files for the respective streams. Administrator-defined streaming mode If NEW_STREAM is the first line of the backup selections 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. the first instance of it must be on the first line. NEW_STREAM directives are ignored if Allow multiple data streams is not set. Multiple concurrent streams from a single physical device can adversely affect backup times. The following actions occur: ■ The backup is split into a separate stream at each point in the backup selections list where the NEW_STREAM directive occurs.Policies Rules to indicate paths in the backup selections list 185 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.

only the files that have changed are backed up. Auto-discovery streaming mode Auto-discovery streaming mode is invoked if NEW_STREAM is not the first line of the backup selections list. the backup selections list is sent to the client.186 Policies Rules to indicate paths in the backup selections list ■ The last stream in the backup selections list is terminated by the end of the backup selections list. regardless of when the files were last changed. assume you add D:\Utilities after D:\Datafiles If an incremental backup is due that night. If the next backup due is an incremental. This stream backs up D:\Program Files and C:\Winnt. For example. To ensure that a new entry gets a full backup the first time. The second NEW_STREAM starts a second data stream that backs up C:\users and D:\DataFiles. 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. only changed files in D:\Utilities are backed up. NetBackup performs a full backup of new streams that are added to the backup selections list. ■ If a backup selections list entry is added to a stream. Add a NEW_STREAM directive before D:\Utilities. The backup time is longer if the heads must move back and forth between tracks containing files for the respective streams. which preprocesses the list and splits the backup into streams as follows: . add it to a new stream. In the previous example. to perform a full backup of all files in D:\Utilities. In this mode. consider the following backup selections list: NEW_STREAM D:\Program Files C:\Winnt NEW_STREAM C:\users D:\DataFiles This backup selections list contains two data streams: ■ The NEW_STREAM at the top of the list invokes administrator-defined streaming and starts the first data stream. Note: In the following examples. the entry is not backed up until the schedule is due for the policy. The list must contain either the ALL_LOCAL_DRIVES directive or wildcards.

Before the backup begins. NetBackup preprocesses the client and makes required changes to the streams. However. Too short of an interval can cause preprocessing to occur often enough to increase scheduling time to an unacceptable level. When a schedule is due and auto-discovery is used.Policies Rules to indicate paths in the backup selections list 187 ■ If the backup selections list contains the ALL_LOCAL_DRIVES directive. A short interval is most ■ . Clients that are running NetBackup 3. If necessary. each file path in the backup selections list becomes a separate stream. the auto-discovery mode is not used. Wildcard usage is the same as for Windows clients. If wildcards are used. Setting the preprocess interval for auto-discovery The preprocess interval applies only to auto-discovery mode and specifies how often preprocessing occurs. For example. The default is four hours and is a good value for most of the sites that run daily backups. However. Whether or not it occurs depends on the preprocess interval. preprocessing does not necessarily occur before every backup. except for NetWare clients. A new stream may be omitted from the next backup because the preprocessing interval has not expired when the backup is due. NetBackup splits each drive volume (Windows) or file system (UNIX) into its own backup stream. Auto-discovery streaming mode applies to: ■ ■ Standard and MS-Windows-NT policy types. In this case. 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. The first backup that a policy performs preprocesses the backup selections list. In this case. assume the preprocess interval is set to four hours and a schedule has a frequency of less than four hours. you can change the interval by using the bpconfig command.2 or later. see “Using wildcards in NetBackup” on page 630. the server preprocesses rather than the client. NetBackup backs up the entire client. ■ If the backup selections list contains neither the ALL_LOCAL_DRIVES directive nor wildcards. see “ALL_LOCAL_DRIVES directive and multiple data streams” on page 188. NetBackup does not run preprocessing on the client. NetBackup checks whether the previous preprocessing session occurred within the preprocess interval: ■ ■ If yes. the expansion of the wildcards results in one stream per wildcard expansion. If no. For more information. If the interval is too long or too short. the client uses auto-discovery to preprocess the backup selections list to determine how many streams are required. For more information.

ALL_LOCAL_DRIVES directive and multiple data streams The ALL_LOCAL_DRIVES directive applies only to Standard (except for NetWare target clients). NetBackup periodically preprocesses the client to make necessary changes to the streams. . For more information. NetBackup generates a stream for each file system. MS-Windows-NT. see “Setting the preprocess interval for auto-discovery” on page 187. NetBackup backs up the entire client. the ALL_LOCAL_DRIVES directive applies only to Standard (except for NetWare clients) or MS-Windows-NT policy types. then splits the data from each drive (Windows) or file system (UNIX) into its own backup stream. If this directive is used. That is. ■ Caution: Do not select Cross mount points for policies where you use the ALL_LOCAL_DRIVES directive. ■ If Allow multiple data streams is enabled. Assume that the client is a Windows system with two drive volumes. NetBackup generates: ■ ■ One stream for C:\ One stream for D:\ For a UNIX client. NetBackup backs up the entire client and includes all drives and file systems in the same stream. The backup selections list contains: ALL_LOCAL_DRIVES For this backup selections list. The clients must run NetBackup 3. this directive must be the only entry in the backup selections list for the policy. The action that ALL_LOCAL_DRIVES causes depends on whether Allow multiple data streams is enabled for the policy.188 Policies Rules to indicate paths in the backup selections list 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: install_path\NetBackup\bin\admincmd\bpconfig [-prep hours] For more information on the bpconfig command. C:\ and D:\. and NetWare policies. see NetBackup Commands for Windows.2 or later software. ALL_LOCAL_DRIVES example 1 Assume that Allow multiple data streams is enabled in the auto-discovery mode. If Allow multiple data streams is not enabled. no other files or directives can be listed.

. the set command is a client-specific directive that is passed to the first and all subsequent streams. SYSTEM_STATE is also backed up because SYSTEM_STATE is included in the ALL_LOCAL_DRIVES directive. UNSET. 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. 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. use UNSET or UNSET_ALL at the beginning of the third stream. see “Directives for specific policy types” on page 184. NEW_STREAM set destpath=/etc/home /tmp /use NEW_STREAM /export NEW_STREAM /var For the set command to be passed to the first two streams only. The backup selections list contains: ALL_LOCAL_DRIVES Here. For more information. At this location. The UNSET and UNSET_ALL directives change this behavior. and multiple data streams All policy-specific directives that are passed to a client in a stream are passed in all subsequent streams. These directives are recognized only if the Allow multiple data streams option is set for the policy. UNSET The UNSET directive interrupts a policy-specific directive so it is not passed with any additional streams. C:\ and D:\. UNSET example In the following backup selections list. NetBackup backs up the entire client in one data stream that contains the data from both C:\ and D:\. UNSET_ALL directives. 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.Policies Rules to indicate paths in the backup selections list 189 SYSTEM_STATE is also backed up because SYSTEM_STATE is included in the ALL_LOCAL_DRIVES directive. it prevents SET from being passed to the last stream.

Solaris. If a file is open. enable Follow NFS. SGI.190 Policies Rules to indicate paths in the backup selections list 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. Files that are excluded from backups by default By default. NetBackup backs up the last saved version of the file. on migrated files or directories where Storage Migrator does not return inode information (mig_stat fails). NetBackup does not back up the following files: ■ ■ NFS files or directories. Files or directories with path lengths longer than 1023 characters. Files or directories in a different file system. (Named pipes are backed up. Directories that NetBackup cannot access (the cd command cannot access).) Locked files when locked by an application that currently has the file open. On the disks that Storage Migrator manages. a number of files and file states are not backed up by NetBackup. Note that NetBackup Server does not support Storage Migrator. enable Cross mount points. however. UnixWare) devpts (Linux) mntfs (Solaris) . ■ ■ ■ ■ ■ ■ ■ NetBackup automatically excludes the following file system types on most platforms: ■ ■ ■ ■ cdrom (all UNIX platforms) cachets (AIX. To back up NFS files. You can also exclude specific files from automatic backups by specifying the files or directories in an exclude list on the client. Files or directories in which the operating system does not return inode information (the lstat system call fails). Busy files. Socket special files. To backup up files in a different file system.

On NetWare target clients. which can be backed up by a user-directed operation). for example. see “Exclude Lists properties” on page 410. For more information. and Restore client interface: Start Backup. If /proc is not added manually. Archive. this list is known as the FilesNotToBackup list. See the NetBackup user’s guide for the client. You can also create an include list to add a file(s) specifically that would be excluded. Go to the Exclude list or Include list tab. and Restore and click File > NetBackup Client Properties. see the NetBackup user’s guide for the client. you can exclude specific files from automatic backups by specifying the files in an exclude list on the client. In Windows. Those items also are excluded from user-directed backups (unlike items in a NetBackup exclude list. 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. The Exclude list or Include list can also be specified through the NetBackup Administration Console on the master server. Note: Exclude and include lists do not apply to user backups and archives. specify exclude and include lists in the Backup. For UNIX clients. the exclude and include lists are specified when the targets are added. For further instructions. see “Exclude and Include Lists on UNIX Clients” in Chapter 5 of the NetBackup Administrator’s Guide. The include list is useful to exclude an entire directory except for one file. does not exclude automatically for AIX. so /proc must be added manually to the exclude list. ■ ■ Windows excluded files Windows 2000 and later releases maintain a list of files and folders that are excluded when you back up files using Microsoft Windows Backup. The method for specifying files in the exclude and include lists depends on the type of client: ■ On Microsoft Windows clients.Policies Rules to indicate paths in the backup selections list 191 ■ proc (UNIX platforms. . Volume II. Archive. NetBackup excludes those files and directories from automatic backups even if they are not in the NetBackup exclude list for the client.

. NetBackup does not restore the registry keys that are listed in the Windows KeysNotToRestore list.192 Policies Rules to indicate paths in the backup selections list Windows 2000 and later releases also maintain a list of registry keys not to restore.

The separately-priced Vault option must be installed. Symantec recommends that the image file be saved to a network share or a removable device. .Policies Disaster Recovery tab 193 Disaster Recovery tab The Disaster Recovery tab appears for those policies that are based on the Catalog Backup policy type (NBU-Catalog). Caution: Do not save the disaster recovery information to the local machine. The Disaster Recovery tab contains options for configuring disaster recovery protection methods for the catalog data. 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.

If mail_dr_info. separate email addresses with a comma: email1.cmd. Logon The logon and password information that is required to access the Windows share. Password The password that is required to log on to the share.cmd is not configured. Specify a local directory or UNC path (CIFS Windows share).cmd is not configured.194 Policies Disaster Recovery tab Path The path to the directory where the disaster recovery information is saved. To send the information to more than one address. and message to nbmail. Send in an email attachment Symantec recommends that the disaster recovery report be sent to at least one email address. NetBackup administrators can set up the script to send the disaster recovery information to alternate locations. Note: Logon and password fields are enabled when NetBackup does not have write access to the location that is specified. the disaster recovery report is sent to the administrator(s) that are indicated in the Disaster Recovery tab by nbmail.cmd or mail_dr_info.email2 To ensure that the system is set up to send mail. NetBackup performs the notification by passing the email addresses.cmd or mail_dr_info. The nbmail. the disaster recovery report is sent to the administrator(s) that are indicated in the Disaster Recovery tab. and Install_path\NetBackup\bin\nbmail. see “Setting up email notifications” on page 434. The email address where the information is sent. See the comments in the script for configuration instructions. In addition specify the email address(es) in the Disaster Recovery tab. 2 . The scripts use the mail program that is specified in the script to send email to the user.cmd script must be configured (Install_path\NetBackup\bin\).cmd. 1 If Install_path\NetBackup\bin\mail_dr_info. subject.cmd is configured.

Note: When NetBackup is running with Vault. including the most recent full backup. neither nbmail.cmd is configured to send email. Note: Critical policies should use only incremental or full backup schedules. The NetBackup Disaster Recovery report lists all of the media that is used for backups of critical policies.Policies Disaster Recovery tab 195 3 If neither file is configured. . NetBackup attempts to use Microsoft internal imapi services. Note: By default. 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 wizard warns you if any media for critical policies are not available.cmd nor mail_dr_info. The Disaster Recovery report lists only the media for incremental and full backup schedules. Vault includes the disaster recovery data in the Vault Recovery Report.

For example: vlteject -eject -report [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] Both commands are located in the following directory: install_path\netbackup\bin For more information on Vault names.196 Policies Creating a Vault policy Creating a Vault policy A Vault policy differs from other policies in the following respects: ■ ■ You must specify Vault as the policy type. enter one of two Vault commands: ■ Use vltrun to specify the robot. On the Schedules tab. click New to create a new schedule. 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. Click OK. ■ To create a Vault policy 1 2 3 4 5 In the NetBackup Administration Console. and command usage. see the Vault Administrator’s Guide. therefore the Clients tab does not appear. The vltrun command accomplishes all the steps necessary to select. ■ 7 Click OK. Complete the schedule. Note: The Clients tab does not appear for Vault policy types. expand NetBackup Management > Policies. vault name. . Select Actions > New > New Policy. and profile for the job. If the vault profile name is unique. select Vault as the policy type. The type of backup defaults to Automatic. copy. Type a unique name for the new policy in the Add a New Policy dialog. and eject media. 6 On the Backup Selections tab. On the Attributes tab. use the following format: vltrun profile_name If the vault profile name is not unique. profile names. You do not specify clients for Vault policies. Specify a Vault command in the backup selections list instead of a file(s).

3 In the Manual Backup dialog. A user schedule cannot be manually backed up because they do not have a backup selection list (the user selects the files). If you do not select any schedules. see “Active. NetBackup uses the schedule with the highest retention level. Without a backup window. Select Actions > Manual Backup. For more information.) The Manual Backup dialog appears. Click OK to start the backup. To back up quarterly or yearly financial information. Create a policy for manual backups only by creating a policy with a single schedule that has no backup window. 4 . Note: If the Go into effect property is set for a future date and time. the backup does not run. To back up a client that missed the regular backup. To back up a client before installing new software to preserve the old configuration. Go into effect at option must be enabled to perform a manual backup. Go into effect at” on page 105. it may be useful to create a policy and schedule that you use only for manual backups. the policy can never run automatically.Policies Performing manual backups 197 Performing manual backups A manual backup is user-initiated and based on a policy. If you do not select any clients. User schedules do not appear in the schedules list. (The Active. Select the policy name in the left pane. ■ ■ In some cases. select the schedule and the clients that you want to back up. A manual backup is useful in the following situations: ■ ■ ■ To test a configuration. To perform a manual backup 1 2 In the NetBackup Administration Console. To preserve records before a special event such as a company split or merger. expand NetBackup Management > Policies. NetBackup backs up all clients.

198 Policies More about synthetic backups More about synthetic backups Synthetic backups can be written to tape storage units or disk storage units. see “Collect true image restore information with move detection” on page 115. the drives can synthesize full backups during the day. Supports disk environments Synthetic backups can be created in the environments that are comprised exclusively of disk storage units. After the backup images are combined into a synthetic backup. NetBackup detects whether new or changed files have been copied to the media server during the last incremental backup. full synthetic backup is an accurate representation of the clients’ file system at the time of the most recent full backup. The Collect True Image Restore Information With Move Detection option must be selected on the Policy Attributes tab. full backup. If the backups use tape. 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. Reduces the network traffic Network traffic is reduced because files are transferred over the network only once. Uses drives more effectively Synthetic backups can be written to tape storage units or disk storage units. The new. For more information. if backups occur primarily at night. the backups can be synthesized when drives are not generally in use. or a combination of the two. or a combination of both. For example. 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. When NetBackup creates a synthetic full backup. . The files are copied even though those files may not have changed since the last incremental backup. The following sections describe how synthetic backups can be used in your NetBackup configuration. all files are copied from the client to a master server or a media server. Processing takes place on master and media server(s) instead of client During a traditional full 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.

A combination of disk storage unit(s) and tape library(s). The synthetic backup synthesizes all of the incremental backups to create a new full or cumulative backup image. the synthetic backup is only as current as the last incremental backup. use only differential incremental backups for the traditional. The synthetic backup job receives a status code of 1 for a policy that contains full or incremental synthetic backup schedules. A traditional backup is necessary before a synthetic backup can be created. non-synthesized backups. run a traditional. The synthetic backup jobs fails if there is not at least one previous full image. Since Collect True Image Restore Information With Move Detection is required for synthetic backups. but no incremental backup schedules. media servers. see “Disk storage unit considerations” and “Tape storage unit considerations” on page 204. For more information.Policies More about synthetic backups 199 ■ The schedule that is created for a synthetic backup must have Synthetic Backup selected. ■ Note: To configure a synthetic cumulative backup for any clients that are archive bit-based (default). Tape library(s) with multiple drives to read and write. Schedule(s) for incremental backups.0 or later installed to synthesize backups. full backup must be run successfully to create a full image. and clients must all have NetBackup version 5. all of the clients in the policy must support TIR. ■ One full and/or one cumulative backup schedule with the Synthetic Backup option selected. . Incremental backups are necessary to capture the changes in the file system since the last full or incremental backup. One of the following must be available: ■ ■ ■ ■ Disk storage unit(s) with adequate space available. Therefore. full backup of the policy. Adding clients to a policy for synthetic backups After clients are added to a synthetic backup policy. The master servers. ■ 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.

The synthetic backups do not interact with the client system at all. then copied from the client’s file system to the backup media. Figure 4-11 Traditional full backup to disk (Sunday) Creation of synthetic full backups Synthetic full backup to disk (Sunday) A B Incremental backups to disk (Mon-Sat) Sunday’s Synthetic full Backup Synthetic full backup (Sunday) B C Incremental backups (Mon-Sat) Synthetic full backup (Sunday) Sunday’s synthetic full backup C D Incremental backups (Mon-Sat) The traditional full backup (A) and the incremental backups are created in the traditional manner: data is scanned. Synthetic full backups The following figure illustrates the creation of synthetic full backups (B. The images that are used to create the synthetic image are known as component images. D) from an existing full backup (A).200 Policies More about synthetic backups Two types of synthetic backups Two types of synthetic backup images can be created: synthetic full and cumulative synthetic. It also shows the incremental backups between full backups. . the component images in a synthetic full are the previous full image and the subsequent incremental images. For instance. C. but are instead synthesized on the media server.

Policies More about synthetic backups 201 For a discussion of synthetic cumulative incremental backups. run daily. Per schedule. A schedule for daily (Monday through Saturday) differential incremental backups. Synthetic full backup usage example 1 Create a Standard or MS-Windows-NT policy for the clients (5. differential incremental backups for the clients throughout the week. only the differential incremental backups are used for the synthetic image. If no cumulative incremental backup is available. 4 Note: The synthetic full backups in this scenario are only as current as the Saturday incremental backup. ■ 2 3 Make sure that the traditional full backup runs. see “Synthetic cumulative incremental backups” on page 201. The last cumulative incremental backup. C) from the latest cumulative incremental backup. B. It also shows the subsequent differential incremental backups. . If a cumulative incremental backup exists that is newer than the last full backup. A schedule for weekly full. ■ The following figure illustrates the creation of synthetic cumulative incremental backups (A. traditional backup to run at least once. a cumulative incremental backup includes all changes since the last full backup. Remember. Synthetic cumulative incremental backups The scenario to create a synthetic. Include the following schedules: ■ ■ A schedule for one full. run synthetic full backups for the clients on subsequent Sundays. If the backup does not complete. Per schedule. synthetic backups.0 or later) you want to back up. 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 incremental backup for the week runs on Saturday. cumulative incremental backup is similar to the scenario to create a synthetic full backup. run the backup manually.

If the backup does not complete. run the backup manually. .0 or later) you want to back up. run daily differential incremental backups for the clients throughout the week. ■ 2 3 4 Make certain that the traditional full backup runs. Per schedule. A schedule for weekly cumulative incremental synthetic backups. A schedule for daily (Monday through Saturday) differential incremental backups. The last incremental for the week runs on Saturday. Include the following schedules: ■ ■ A schedule for one full. run synthetic cumulative incremental backups for the clients on subsequent Sundays. traditional backup to run at least once.202 Policies More about synthetic backups 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) Sunday’s synthetic cumulative Incremental backup A B Synthetic cumulative incremental backup (Sunday) Incremental backups (Mon-Sat) Sunday’s synthetic cumulative incremental backup B Synthetic cumulative incremental backup (Sunday) C Incremental backups (Mon-Sat) Synthetic cumulative backup usage example 1 Create a Standard or MS-Windows-NT policy for the clients (5. Per schedule.

For more information. run an incremental backup before the synthetic 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. In this case. The issues are similar to those encountered while multiplexing synthesized backups problems. Calendar-based schedules are dependant on one another. If a daily incremental schedule runs earlier in the day. If the clients experience a high rate of change daily. the synthetic cumulative backup does not run later that same day (00:00:00–23:59:59). To synthesize multiplexed client images requires multiple passes over the source media—one per client. For example.Policies More about synthetic backups 203 Note: The synthetic cumulative backups in this scenario are only as current as the Saturday incremental backup. NetBackup processes the newest component images first in a synthesized backup. Disk storage unit considerations Disk-based images are more efficient for synthesizing. followed . Synthesized backups and multistreaming Performance issues occur if multiple streams are selected for synthesized backups. Note: Only frequency-based schedules allow an incremental backup and a synthetic backup to run on the same day. Refrain from multiplexing backups that will be synthesized Do not synthesize multiplexed backups because it is inefficient. a synthetic backup is no more helpful than a traditional full backup. a synthetic backup is only as current as the last incremental backup. Reducing the gap between the last incremental backup and the synthesized backup Since a synthetic backup does not involve direct contact with the client. the incremental backups are too large. see “Frequency schedule type” on page 134 and “Calendar schedule type” on page 134. Back up to disk whenever possible to improve multiple stream performance issues. If there is a concern to reduce a potential gap in backup coverage.

It is the same whether the restore is from a traditional backup or from a synthetic backup. ■ ■ . If a single tape drive device is used to generate synthetic images. with a synthetic full backup. an additional drive is needed for reading. the tape movement may be somewhat inefficient compared to disk-based images. which stores the files in last-file-accessed order. The tape for the synthetic image must be different from the tape where the component images reside. the run time is even faster. the processing order introduces the potential for fragmentation of a single directory across the synthetic full image. Contrast a traditional full backup. The restore time of a single directory may increase over time when sourced from synthetic backups. 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. If the synthetic full backup is also generated on disk. In that way. which stores the files in file system order. The disk copy can then be duplicated to tape. The restore time depends on the pattern of file changes within the directory. The restore times for both a complete synthetic backup and for a single file is the same. Tape storage unit considerations ■ For tape backups.204 Policies More about synthetic backups by sequentially older images. ■ 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. Synthetic full backups are generated more quickly when built from disk-based incremental backups. a synthetic image can be generated with the single tape drive device. separate tapes are required. component images should be placed in a hard drive location first. The synthetic full contains the newest files at the front of the media and the unchanged files at the end. ■ ■ 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. When two or more component images have been written to the same tape. Over time.

The catalog files are automatically expired after the retention period as specified in the schedule for the policy. which is as recent as the most recent incremental. A user-generated backup cannot be used to generate a synthetic image. two sets of catalog files are created: an image file and one or more .f files. The two sets of catalogs have the same expiration times. 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. This set represents the actual synthetic backup image. The second set is named with the current timestamp. For more information. Synthetic backups are not supported if any of the component images are encrypted. This set is used to mark the time the synthetic backup job was run. 1 The first set is named with the timestamp of the most recent incremental + 1.Policies More about synthetic backups 205 Note that this scenario is limited to single directory restores. see “Retention” on page 144. Single file restores and full image restores from synthetic fulls are equal or better than from traditional full backups. . It does not contain any file data. The option to create multiple copies is not allowed for synthetic backups. General notes ■ Synthetic backups are supported on all media server platforms and tier one master server platforms. as noted in previous bullets. 2 Do not manually remove any of these catalog files. ■ ■ ■ Synthetic backup jobs create two sets of catalog files When a synthetic backup job is run.

all clients that are included in the policy must support TIR. For more information. rerun the synthetic backup job to restore automatically the TIR information to the catalog. Consider a situation where Keep true image restoration (TIR) information host specifies that TIR information is pruned from the catalog after two days. the TIR information is pruned from the component images until a subsequent traditional or synthetic full or cumulative backup image has been generated successfully. The Keep true image restoration (TIR) information property indicates how long TIR information in the image catalog is kept before it is pruned (removed). In case the TIR information cannot be restored due to bad. or vaulted media. This property is located in the master server Clean-Up host properties. the .f After the synthetic backup job runs: XDisk_1064421709_FULL First set: XDisk_1064421709_FULL. see “Collect true image restore information with move detection” on page 115. True image restore and synthesized backups Since the Collect true Image restore information with move detection policy property must be enabled for synthetic backups.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. If the TIR information has been pruned from a component image and you accidentally expire the most recent synthetic image.206 Policies More about synthetic backups For example: Catalog after incremental backup jobs run: XDisk_1064417510_INCR XDisk_1064417510_INCR. if a synthetic full and/or synthetic cumulative schedule has been defined in the policy. On the third day the TIR information is pruned only if a traditional or synthetic full backup image has been generated. The timestamp may be more than one second later if there were possible image name conflicts.f XDisk_1064420508_INCR XDisk_1064420508_INCR. missing.f XDisk_1064421708_INCR XDisk_1064421708_INCR. However.

see “Keep true image restoration (TIR) information” on page 380. This option is enabled if Take checkpoints on the policy Attributes tab is enabled. If the required resources are not available.Policies More about synthetic backups 207 synthetic backup job fails with error code 136 (TIR info was pruned from the image file). If needed. Each of these programs has a debug log file in the logs directory. Catalog information is managed using bpdbm. For more information. NetBackup starts the bpsynth program to manage the synthetic backup process. Change journal and synthesized backups If the Windows client host property. Checkpoint restart and synthesized backups If Checkpoint Restart is indicated for the policy. or by another synthetic backup job. Logs produced during synthetic backups When a synthetic backup is scheduled. the backups that are produced with the synthetic backup schedule are not checkpointed. If problems occur with synthetic backups. Synthetic jobs display Synthetic as the Data Movement type while traditional backups display Standard. bpsynth then schedules the tape drive resources that are needed for the synthetic backup. Use Change Journal in Incrementals. For more information. run the synthetic backup again. This could happen if a drive is used by a backup or a restore. If the resources can be obtained eventually but not immediately. the following debug logs are required to diagnose the problem: . the property has no effect. If Take checkpoints is enabled for a synthetic backup. If the problem is correctable. the synthetic job waits until the resources become available. is enabled. bpsynth passes information to programs bptm and bpdm to cause tape and disk images to be read or written. see “Use change journal in incrementals” on page 399. 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. bpsynth plans how the synthetic backup is built from the previous backup images. the property has no effect when the client is backed up using the synthetic backup schedule. the job fails with a status code that indicates that a resource is needed.

This property is found under NetBackup Management > Host Properties > Clients > Selected client(s) > Windows Client. Synthetic backups and directory and file attributes For a synthetic backup to include directory and the file attribute changes. ■ However. For more information. On the media server(s): bptm (if any tape images). (For example. see “Incrementals based on archive bit” on page 401. To include ACL changes in backups. bpdbm.conf file on each UNIX client. This can be inefficient with tape images since bpsynth needs a tape drive to write the new image. enter USE_CTIME_FOR_INCREMENTALS in the bp. changes like access control lists (ACLs) ■ UNIX: Changing an object’s ACL changes the ctime (inode change time) for the object but not the mtime (data modification time). bpcd Note that several media servers may be involved if the component images are on different nodes. bpsynth may use the same component image volumes. bpdm (if any disk images).208 Policies More about synthetic backups ■ On the master server: bpsynth. the ACL change is not reflected in an incremental backup. and therefore not in a synthetic full backup. enable Incrementals: Based on Archive Bit. Windows: For each Windows client. One may have to complete before the next one proceeds. ■ . bpsynth is used for each stream or client. Also. Since mtime triggers incremental backups. and the log files located in install_path:\Program Files\VERITAS\NetBackup\logs as described in the NetBackup Troubleshooting Guide. the change must first be picked up by a component incremental backup.

or a storage lifecycle policy. a named group of storage units. This chapter describes how to use the NetBackup Storage utility to create and manage storage destinations. then final storage” on page 238 “Basic disk staging” on page 240 “Storage Lifecycle Policies” on page 249 “Storage unit groups” on page 263 . and lifecycle policies The data that is generated from a backup job or another type of job is recorded in storage. This chapter contains the following sections: ■ ■ ■ ■ ■ ■ ■ “Introduction to the Storage utility” on page 210 “Storage units” on page 212 “Storage unit settings” on page 224 “Staging backups to initial storage. A storage destination can be a single tape or disk volume.Chapter 5 Storage units. unit groups. A NetBackup administrator must define storage destinations with the Storage utility before a backup job or another type of job can be run.

(See “Storage Lifecycle Policies” on page 249. or a disk pool. and lifecycle policies Introduction to the Storage utility Introduction to the Storage utility The Storage utility contains subnodes to define three different storage configurations. How the storage units are selected within the group is determined when the group is created.) ■ ■ . a path to a volume. The following items describe Storage Units. (See “Storage units” on page 212. The label may identify a robot. unit groups. The primary storage destination is a storage unit.) Storage Lifecycle Policies Storage lifecycle policies allow you to apply the same behavior to all the backup images in the lifecycle. since storage units can be included as part of a storage unit group or a storage lifecycle policy.210 Storage units. Storage Unit Groups. and Storage Lifecycle Policies: ■ Storage units A storage unit is a label that NetBackup associates with physical storage. (See “Storage unit groups” on page 263.) Storage unit groups Storage unit groups allow you to identify multiple storage units as a group.

or Storage Lifecycle Policies to display the storage destinations that have been created for the selected server.Storage units. To display the storage configuration for another NetBackup master server. see “To administer a remote master server” on page 635. then Storage Units. 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 . unit groups. and lifecycle policies Introduction to the Storage utility 211 Using the Storage utility Expand Storage. Storage Unit Groups.

PureDisk storage unit: The destination is a disk pool. stand-alone tape drives. Choose the storage unit type: Media Manager. ■ For Media Manager storage units: Data is written to tape robots. unit groups. A configured storage unit indicates to NetBackup the existence of underlying physical storage. ■ ■ ■ ■ ■ ■ For NDMP storage: The NDMP protocol to is used to perform backups and recoveries. The selection indicates that the media server(s) have permission to write to the storage unit.212 Storage units. Indicate the destination where the data is written. or NDMP. . OpenStorage storage units: The destination is a disk pool. disk. a path to a volume. The creation of any storage unit type consists of the following general steps: 1 2 3 4 Name the storage unit. SharedDisk storage units: The destination is a disk pool. (See Figure 5-2 on page 213. SnapVault storage: The destination is a SnapVault server. BasicDisk storage units: The destination is a path to a volume on a host. and lifecycle policies Storage units Storage units A storage unit is a label that NetBackup associates with physical storage. The destination is an NDMP host. or a disk pool. NearStore storage units: The destination is a NearStore volume on a storage server. 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. The label may identify a robot.) Select a media server. and optical disk devices.

unit groups. Complete the fields on the New Storage Unit dialog box. select NetBackup Management > Storage. click Configure Storage Devices and follow the wizard instructions. To create a storage unit with the Device Configuration Wizard 1 2 In the NetBackup Administration Console tree. From the list of wizards in the Details pane. For help while running the wizard. and lifecycle policies Storage units 213 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. Storage unit information appears in the Details pane. click the Help button in the wizard screen. The options are described in “Storage unit settings” on page 224.Storage units. select the Master Server or Media and Device Management. Click OK to add the storage unit to the configuration. To create a storage unit from the Actions menu 1 2 3 In the NetBackup Administration Console. .

The options are described in “Storage unit settings” on page 224. describe the type of storage. For more information. The Copy a Storage Unit dialog box appears. To delete a storage unit does not prevent files from being restored that were written to that storage unit. Select a storage unit in the Details pane. select NetBackup Management > Storage. Double-click the storage unit you want to change from those listed in the Details pane. Storage unit information appears in the Details pane. provided that the storage has not been physically removed and the backup image has not expired. 3 4 Click Actions > Copy Storage Unit. For example. . select NetBackup Management > Storage. see “NetBackup naming conventions” on page 629. 3 Deleting storage units To delete a storage unit from a NetBackup configuration means to delete the label that NetBackup associates with the physical storage. Complete the fields in the Copy Storage Unit dialog box. Type a unique name for the new storage unit. Hold down the Control or Shift key to select multiple storage units.214 Storage units. Storage unit information appears in the Details pane. The options are described in “Storage unit settings” on page 224. 5 Changing storage unit settings Symantec suggests that changes be made only during periods when no backup activity is expected for the policies that use the affected storage units. To change storage unit settings 1 2 In the NetBackup Administration Console. and lifecycle policies Storage units To create a storage unit by copying an existing storage unit 1 2 In the NetBackup Administration Console. unit groups. Complete the fields on the Change Storage Unit dialog box.

the storage unit can be deleted witout impacting the disk pool. then Storage Units. This generally occurs within seconds of expiring an image. Hold down the Control or Shift key to select multiple storage units. . select the storage unit you want to delete. Click OK.) NetBackup automatically deletes any image fragments from a disk storage unit or a disk pool.) ■ Do not manually remove images from the BasicDisk or Media Manager storage unit. ■ 2 3 4 5 6 7 Select the Storage utility. select the storage units to delete. check the directory on the storage unit to make sure that it is empty. to make sure that all of the fragments have been deleted. (See “Expiring backup images” on page 341. unit groups. Modify any policy that uses a deleted storage unit to use another storage unit. they cannot be restored unless the images are imported.Storage units. Once the images have been expired. In the Details pane. and lifecycle policies Storage units 215 To delete a BasicDisk or Media Manager storage unit 1 Use the Catalog utility to expire any images that exist on the storage unit. (See “Importing NetBackup or Backup Exec images” on page 330. However. Select Edit > Delete. To delete a storage unit that references a disk pool If a storage unit points to disk pool. In the confirmation dialog box. This removes the image from the NetBackup catalog.

Then NetBackup requests that Media Manager mount the volume in a drive. Figure 5-3 Media Manager storage unit settings When NetBackup sends a job to a Media Manager storage unit. unit groups. and lifecycle policies Storage units Media Manager storage unit considerations To create a storage unit of a tape robot. it requests resources from the Enterprise Media Manager (EMM). select Media Manager as the Storage unit type. Media Manager storage unit settings are listed alphabetically in “Storage unit settings” on page 224. or an optical disk device. a stand-alone tape drive. An operator can then find the volume. mount it manually. .216 Storage units. and assign it to the drive. a mount request is displayed in the Pending Requests pane of the Device Monitor. If a stand-alone drive does not contain media or if a required volume is not available to a robot.

Applies only to NetBackup Enterprise Server: If a robot’s drives and robotic control attach to different NetBackup servers. It can have both half-inch cartridge and DLT drives. specify the server where the drives attach as the media server. Specify the media server where the drives attach. (See “Maximum concurrent write drives” on page 227. ■ ■ ■ Stand-alone drives with the same density must be in the same storage unit. For example. (A tape that is assigned to Storage Migrator uses a different format and would not be usable for NetBackup backup data. The logic is part of the Enterprise Media Management (nbemm) service. If using NetBackup Server: Add the storage unit to the master server where the drives attach. you must define a separate storage unit for each density. The robotic control must also attach to that server. add a storage unit with Maximum concurrent write drives set to 2.) Drives with different densities must be in separate storage units. if a server has two 1/4-inch qscsi drives. Always specify the same robot number for the drives as is used for the robotic control. ■ ■ . A robot and a stand-alone drive cannot be in the same storage unit. Stand-alone drives with different densities must be in different storage units. and lifecycle policies Storage units 217 Note: NetBackup Media Manager can manage media for other applications. Consider an STK SL500 library that is configured as a Tape Library DLT (TLD). Set the Maximum concurrent write drives setting to 2. If a robot contains two drives of the same density on the same media server.) Notes on adding a Media Manager storage unit ■ If using NetBackup Enterprise Server: Add the storage unit to the master server. unit groups. Media and device selection logic chooses the drive to use when NetBackup sends a backup to this storage unit. add only a single storage unit for the robot. The number of storage units that you must create for a robot depends on the robot’s drive configuration as follows: ■ ■ Drives with identical densities must share the same storage unit on the same media server. Here. such as Storage Migrator.Storage units.

This model uses new logical entities. A disk pool is a storage type in NetBackup. and lifecycle policies Storage units Disk storage unit considerations NetBackup permits the creation of an unlimited number of disk storage units. NetBackup aggregates the disk volumes into pools of storage (a disk pool) you can use for backups. ■ ■ The following sections describe the disk storage unit types.5 provides a new model for disk storage. Note: Symantec recommends that quotas are not imposed on any file systems that NetBackup uses for disk storage units. you select the disk type and then you select a specific disk pool.218 Storage units. When you create a storage unit. 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. a NetBackup media server also may function as a storage server.) Disk storage model NetBackup 6. A storage server is the entity that has a mount on the file system on the storage. (For example. unit groups. Settings are listed alphabetically in “Storage unit settings” on page 224. Not all settings are available on each disk storage unit type. Storage server: An entity that writes data to and reads data from the disk storage. the storage server is either: a host that is part of a storage appliance or filer or it is a NetBackup media server. Depending on the Enterprise Disk Option. See Figure 5-2 on page 213 for a list of available types. and uses new terminology. Disk pool: A collection of disk volumes that are administered as an entity. uses existing entities to provide new capabilities. . Depending on the Enterprise Disk Option. the capacity managed retention selection in lifecycles and staging to storage units. Some NetBackup features may not work properly when file systems have quotas in place. 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 NearStore host is the storage server. OpenStorage An OpenStorage disk type storage unit is used for disk storage on an intelligent disk appliance. An OpenStorage selection is available only when the OpenStorage Disk Option is licensed. If the resources are shared with other users. and lifecycle policies Storage units 219 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. For NearStore. BasicDisk storage units cannot be used in a storage lifecycle policy. NetBackup assumes exclusive ownership of the disk resources that comprise an AdvancedDisk disk pool. the NetBackup media server functions as both a data mover and a storage server. unit groups. The storage vendor partners with Symantec to integrate the appliance into NetBackup. For OpenStorage. NearStore appears as a selection only when the OpenStorage Disk Option is licensed. Notes about the BasicDisk type storage unit: ■ Do not include the same volume or file system in multiple BasicDisk storage units. NetBackup cannot manage disk pool capacity or storage lifecycle policies correctly. the NetBackup media servers function as the data movers. The disk appliance is the storage server . An AdvancedDisk selection is available only when the Flexible Disk Option is licensed. For AdvancedDisk. NearStore A NearStore disk type storage unit is used to store images on Network Attached Storage (NAS) from Network Appliance.Storage units. the NetBackup media servers function as the data movers. ■ AdvancedDisk An AdvancedDisk disk type storage unit is used for dedicated disk that is directly attached to a NetBackup media server. NetBackup stores backup data in the specified directory. The actual name of the disk type depends on the vendor. Note: NearStore storage units cannot be used as part of a storage unit group or used in a Storage Lifecycle Policy. The disk appliance is integrated into NetBackup through an API.

which has a gold data classification. SnapVault A SnapVault storage unit is used to store images on Network Attached Storage (NAS). PureDisk appears as a selection only when the PureDisk Storage Option is licensed. For SharedDisk. For PureDisk. unit groups. SnapVault storage units cannot be used in a storage unit group or as part of a staging operation. It is configured to use Lifecycle_Gold.220 Storage units. referenced by a storage unit. It is configured to use Any Available storage unit. the NetBackup media servers function as both the data movers and the storage servers. The SnapVault host is the storage server. That means it can use any available storage unit or any lifecycle that has a silver classification. The following figure is one example of how policies can interact with volumes in a disk pool. the NetBackup media servers function as the data movers. Policy_silver has a silver classification. the NetBackup media servers function as the data movers. The SnapVault selection is available only when the NetBackup Snapshot Client option is licensed. Two policies have been created: ■ Policy_gold has a gold classification. ■ Two storage units are available: . and lifecycle policies Storage units PureDisk A PureDisk disk type storage unit is used to store images on PureDisk storage devices. The SharedDisk selection is available only when the Flexible Disk Option is licensed. Disk storage units in storage lifecycle policies Another new feature in this release is the option to create storage lifecycle policies. but are mentioned here to show how storage units can interact with a lifecycle. The storage unit can be shared by multiple NetBackup media servers. Note: PureDisk storage units cannot be used as part of a storage unit group. Storage lifecycle policies are discussed on page 249. For SnapVault. SharedDisk A SharedDisk disk type storage unit is used to store images on a disk array that multiple NetBackup media servers share. The PureDisk Linux servers function as the storage servers.

It references DiskPool_A. and lifecycle policies Storage units 221 ■ ■ DSU_1 is a destination in Lifecycle_Gold and references DiskPool_A. The volumes may contain images with different data classifications. Figure 5-4 Policy_Gold The data classification for this policy is gold. DSU_1 DSU_1 references DiskPool_A. To maintain space on basic disk staging storage units: . Set the High water mark to a value that best works with the size of backup images in the environment. The following list describes how space can be created for more images on a disk storage unit: ■ ■ Add new disk space. DSU_2 Policy_Silver writes to DSU_2. The policy is configured to write to Lifecycle_Gold. unit groups. 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.Storage units. DSU_2 references DiskPool_A. DSU_2 is not in a lifecycle. DiskPool_A contains three disk volumes. The policy is configured to write to Any available storage unit. Lifecycle_Gold Lifecycle_Gold contains DSU_1 as a backup destination. Both gold and silver images can be written to any disk volume in the pool. Lifecycles and disk storage units referencing disk pools Policy_Silver The data classification for this policy is silver. 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 NetBackup General Server host property Check the capacity of disk storage units property determines how often NetBackup checks 6.ds file may not be deleted upon installation or upgrade. The script deletes . run the script again: install_path\netbackup\bin\goodies\nb_updatedssu To determine the potential free space on a disk staging storage unit.ds files that were used in previous releases as pointers to relocated data. a . 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. Under some circumstances. Subsequent releases use internal methods to monitor disk space more frequently. Relocated data is tracked differently in the current release and the . In that case. unit groups. the nb_updatedssu script runs. see “Finding the potential free space on a BasicDisk disk staging storage unit” on page 242. (See “Check the capacity of disk storage units” on page 427.222 Storage units.ds files are no longer necessary.) ■ ■ ■ .0 disk storage units for available capacity. Upon NetBackup installation or upgrade.

even if used for NDMP backups. Upon upgrade of the media server. Any drive that is attached to a NetBackup media server is considered a Media Manager storage unit. those storage units are automatically converted to Media Manager storage units. Figure 5-5 NDMP storage unit settings Create NDMP storage units for drives directly attached to NAS filers. See the NetBackup for NDMP Administrator’s Guide for more information.Storage units. and lifecycle policies Storage units 223 NDMP storage unit considerations The Virtual Tape Option must be installed on the NDMP hosts to use the hosts as storage units. . Note: Remote NDMP storage units may already be configured on a media server from a previous release. unit groups. 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 224.

This allows the disk staging space management logic to operate successfully. the system drive may fill up. To display properties about the directory or volume. If a storage unit is configured on C: drive and this option is not enabled. For example. but different Low water marks can cause unexpected behaviors. Use any location on the disk. BasicDisk storage units. The setting specifies the absolute path to a file system or a volume available for disk backups. click the Properties button. backups fail with error code 12. consider defining AdvancedDisk storage units.) Do not configure multiple BasicDisk storage units to use the same volume or file system. Or. For additional Windows separators. Not only do the storage units compete for space. (See “Properties button” on page 232. When this setting is enabled. Enter the path directly in the field. Caution: With this setting enabled. the directory is created automatically. and lifecycle policies Storage unit settings Storage unit settings The following topics describe the settings that appear for all types of storage units. see “NetBackup naming conventions” on page 629.224 Storage units. which use disk pools composed of disk volumes that are dedicated file systems for disk backup. 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. then click Add. The settings are listed alphabetically. If the BasicDisk storage unit is used as a disk staging storage unit. Symantec recommends dedicating a disk partition or file system to it. unit groups. A job fails under the following conditions: . providing that sufficient space is available. 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). Use platform-specific file path separators (/ and \) and colon (:) within a drive specification. Each setting does not appear for each storage unit type.

For information on SnapVault storage units. The Enable block sharing setting allows the data blocks that have not changed from . and lifecycle policies Storage unit settings 225 ■ ■ If the checkbox is clear. For AdvancedDisk and SharedDisk. For information about how to create a disk pool. 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). Disk type A Disk type is selected for a disk storage unit. see the NetBackup Shared Storage Guide. For PureDisk. and if the directory already exists on a system drive. For OpenStorage. Select the disk pool that contains the storage for this storage unit. This setting appears for Media Manager and NDMP storage units only. all NetBackup disk pools appear in the Disk pool list. Density The Storage device selection determines the media Density. only the disk pools for that OpenStorage vendor’s appliance appear in the list. Enable block sharing The Enable block sharing setting is available to some disk storage types. unit groups. If the checkbox is clear. Disk pool A Disk pool is selected for any disk storage unit with an Enterprise Disk Option licensed. click Properties.Storage units. only the disk pools for the PureDisk Storage Pool Authority (SPA) appear in the list. and the requested directory is to be created on a system drive. see the NetBackup Snapshot Client Administrator’s Guide. SharedDisk only: To change the disk pool properties.

Upon upgrade. and lifecycle policies Storage unit settings one backup to the next to be shared. when reached. Note: Basic disk staging storage units may already be configured on a media server of a previous release. NetBackup reduces the number of jobs that can write to the storage unit. see “Basic disk staging” on page 240. (Default: 80%. unit groups. The Low water mark setting cannot be greater than the High water mark setting.) On storage units used for disk staging. Once the storage unit is full. To share data blocks can significantly save disk space in the storage unit. Once the capacity of the storage unit is less than the High water mark. As the disk storage capacity grows closer to the High water mark. For more information about this type of staging. For more information. NetBackup may copy expired images to a final destination storage unit to create space. see “Maximum concurrent jobs” on page 227. NetBackup reduces the number of jobs that are allowed to write to the unit. none of the jobs can complete and all the jobs fail due to a disk full condition. High water mark The High water mark setting is a threshold that. Try to prevent the situation where multiple jobs write to a storage unit at one time and fill it to capacity. expired images are deleted to free space until the Low water mark is met. signals to NetBackup that the disk storage unit should be considered full. . Default: 98%. decrease the Maximum concurrent jobs setting. As the capacity of the unit reaches the High water mark. To reduce the number of jobs that are allowed to write to the storage unit. Enable multiplexing The Enable multiplexing setting allows multiple backups to multiplex onto a single drive in a storage unit. NetBackup does not assign new jobs to a storage unit that is considered full. the disk storage units are set with the Low water mark at 100%. adjust the level. Low water mark When a disk storage unit becomes full. NetBackup assigns jobs to the storage unit.226 Storage units. To make the best use of upgraded storage units. The high water mark does not apply to storage units that are used for basic disk staging.

Both tape drives are available to NetBackup but only one drive can be used for backups. 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. to verify. each copy applies toward the Maximum concurrent write drives count. . ■ Assume you have two stand-alone drives of the same density and specify 1.Storage units.) Caution: To specify a Maximum concurrent write drives setting of 0 disables the storage unit. (Default: 1 job. the first two jobs start and the third job waits. For more information. The job count can range from 0 to 256. (For example. Specify a number that is less than or equal to the number of tape drives that are in the storage unit. each copy applies toward the Maximum concurrent jobs count. unit groups. The other tape drive is available for restores and other non-backup operations. the low water mark applies to the disk pool.) This setting corresponds to the Maximum concurrent write drives setting for a Media Manager storage unit. The number of tape drives available is limited to the maximum number of tape drives in the storage device. robot. If a job contains multiple copies. If a job contains multiple copies. see “Disk pool properties” on page 732 and the NetBackup Shared Storage Guide. Select one number for a: ■ storage unit that contains only stand-alone tape drives. and lifecycle policies Storage unit settings 227 For disk storage units that reference disk pools. 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. Caution: To specify a Maximum concurrent jobs setting of 0 disables the storage unit. and to duplicate backups. to import. If three backup jobs are ready to be sent to the storage unit and Maximum concurrent jobs is set to two. 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.

only two jobs can run concurrently on MediaServer_A. unit groups. If Maximum concurrent jobs is set to three and two of the media servers are busy or down. to reference SharedDisk_pool. the storage units have a Maximum concurrent jobs setting of five. Where disk pools are used. However. . 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. Combined. to have a Maximum concurrent jobs setting of two. three on MediaServer_B. the third media server is assigned all three jobs. For example.228 Storage units. If multiple storage units reference the same disk pool. 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. to reference SharedDisk_pool. the setting also depends on the number of media servers in the storage unit. in Figure 5-6: DSU_1 is configured: ■ ■ ■ to use MediaServer_A. The media server load balancing logic considers all storage units and all activity. The Maximum concurrent jobs setting depends on the available disk space and the server’s ability to run multiple backup processes. Both storage unit reference the same SharedDisk disk pool. A storage unit may indicate three media servers. increase the setting if more than one server is in the storage unit. Increase the setting to ensure that the catalog backup can proceed while regular backup activity occurs. the job load is automatically spread across the media servers indicated by the storage unit configuration. Where disk pools are used. A higher value (more concurrent jobs) means that the disk may be busier than if the value was set for fewer jobs. hot catalog backups as well as non-catalog backups. DSU_2 is configured: ■ ■ ■ to use MediaServer_B. to have a Maximum concurrent jobs setting of three. 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. The setting applies to the storage unit and not to the disk pool. Therefore. Note: Increase the Maximum concurrent jobs setting if the storage unit is used for online.

The range is from 2 to 32. To make this storage unit available to any media server (default). NetBackup selects the media server dynamically at the time the policy is run. The NetBackup media servers that can access the servers responsible for data movement to and from the disk pool.Storage units. Media server The following setting applies only to NetBackup Enterprise Server. multiple client backups that NetBackup can multiplex onto a single drive. select <Any Available>. unit groups. The Media server setting specifies one of the following: ■ ■ ■ The NetBackup media server where the drives in the storage unit attach. ■ . select a single media server. ■ Concerning BasicDisk storage: To configure a disk storage unit. Concerning AdvancedDisk storage units The Media server setting specifies the NetBackup media server that can move data to and from the disk pool. Maximum streams per drive The Maximum streams per drive setting determines the maximum number of concurrent. the media servers could run five concurrent jobs: two from DSU_1 and three from DSU_2. The NetBackup media server that controls the disk storage unit. and lifecycle policies Storage unit settings 229 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.

verify that the software plug-in is installed and that login credentials are configured for that media server. the Media server setting specifies the name of the media server that is to back up the NDMP host. ■ Concerning SharedDisk storage units The Media server setting specifies the NetBackup media servers that can move data to the storage server. The disk storage must be directly attached to the media server that is configured as the storage server. and lifecycle policies Storage unit settings Only the media server that is configured as the storage server appears in the media servers list. To allow any media server in the disk pool to access the storage (default). Only those media servers that can talk to the specified NDMP storage device are displayed in the drop-down menu. Only the media servers on which storage server credentials are configured appear in the media servers list. ■ Concerning NDMP storage: To configure an NDMP storage unit. select <Use Any Available Media Server>. Select <Any Available> to have NetBackup select the media server and storage unit at the time the policy is run. Media servers are configured as data movers when the storage server login credentials are entered in NetBackup. Login credentials to the storage server are configured. Note: Run the tpconfig command line utility directly on the media server to configure and verify credentials. 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 vendor’s software plug-in is installed. select <Only Use The Following Media Servers>. Concerning OpenStorage storage units The Media server setting specifies the NetBackup media servers that can move data to the storage server. NetBackup selects a media server when the policy runs. select <Use Any Available Media Server>.230 Storage units. unit groups. . To restrict the media servers that can access the storage. If a server does not appear. To allow any media server in the media server list to access the storage (default). An NDMP host can be authenticated on multiple media servers. NetBackup selects a media server when the policy runs.

Then select the media servers that are allowed to access the storage. NetBackup selects a media server when the policy runs. The following is required on each media server that accesses the storage: ■ The SharedDisk software plug-in (installed automatically with NetBackup). separately named processing units (storage processors). On demand only The On demand only setting specifies whether the storage unit is available exclusively on demand. only when a policy or schedule is explicitly configured to use this storage unit. Login credentials to the PureDisk server are configured on the media server. That is. ■ ■ Concerning PureDisk storage units To allow any media server in the disk pool to access the storage (default). select <Only Use The Following Media Servers>. you must enter the credentials for each unit. select <Use Any Available Media Server>. Select the host name from the drop-down menu or click Add to add a host. To restrict the media servers that can access the storage. The following is required on each media server that accesses the storage: ■ ■ The PureDisk software plug-in is installed. On demand only is selected by default and cannot be changed. NetBackup selects a media server when the policy runs. See the Veritas NetBackup PureDisk Remote Office Edition Administrator’s Guide for the media server requirements. Then select the media servers that are allowed to access the storage. Clear the On demand only check box to make the storage unit available to any policy or schedule. and lifecycle policies Storage unit settings 231 To restrict the media servers that can access the storage. For SnapVault and NearStore storage units. . Login credentials to the disk array are configured on the media server.Storage units. select <Only Use The Following Media Servers>. NDMP host The NDMP host setting specifies the NDMP tape server that is used to write data to tape. unit groups. If the array contains multiple.

Login credentials to the storage server must be configured on the media server. verify that the software plug-in is installed and that logon credentials are created. (For OpenStorage.) If a media server does not appear in the list. NetBackup media servers function as data movers. select <Only Use The Following Media Servers>. Login credentials to the disk array must be configured on the media server. Otherwise. The software plug-in is provided by the storage vendor. unit groups. 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. NetBackup is unable to find a storage unit to use. Only the media servers that are configured as data movers for the OpenStorage implementation appear in the media server list. be sure to designate a specific storage unit for each policy or schedule. See the Veritas NetBackup PureDisk Remote Office Edition Administrator’s 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: . A software plug-in must be installed on each media server. Only the media servers on which disk array login credentials are configured appear in the media servers list. For AdvancedDisk storage: ■ ■ The required software plug-in is installed automatically with NetBackup. Only use the following media servers To restrict the media servers that NetBackup can use to access the storage. Then select the media servers that are allowed to access the storage.232 Storage units. and lifecycle policies Storage unit settings Caution: If On demand only is selected for all storage units. If a server does not appear. Only the media server that is configured as the storage server appears in the media servers list.

The following equation determines the Available (or free) space: Free space on a volume = Capacity of volume . 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.) ■ ■ Low water mark The low water mark for the disk pool.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. the nbdevquery command includes the reserved space in the available space equation. (Default: 99%. and lifecycle policies Storage unit settings 233 ■ Available storage or Available The Available storage value reflects the space that remains for storage on a disk storage unit. The low water mark setting cannot be greater than the high water mark setting. When a disk volume reaches the high water mark.Storage units. Disk pool. Name The name of the disk pool. When a disk pool approaches the high water mark. % full The percentage of storage that is currently in use on the volume. Number of volumes The number of disk volumes in the disk pool. Disk pool comments Comment that are associated with the disk pool. When all volumes are at the high water mark. NetBackup writes the data to another disk volume in the pool. Capacity The Capacity value reflects the total amount of space that the disk storage unit or pool contains. the disk pool is full. NetBackup again assigns jobs to the storage unit. ■ ■ ■ . NetBackup does not assign new jobs to a storage unit in which the disk poll is full. both used and unused. NetBackup reduces the number of jobs that are allowed to write to the pool. unit groups. When the capacity of the disk pool returns to the low water mark. Since NetBackup runs as root.

Backups to disk are usually fragmented to ensure that the backup does not exceed the maximum size that the file system allows.) ■ Raw size The raw. In that case. a restore is faster if a 500-megabyte backup is stored in 100-megabyte fragments. Then enter a value from 50 megabytes to 1. (An exception is for backups where checkpoint restart is enabled. ■ Note: OpenStorage vendors may have special requirements for the maximum fragment size. Backups may be fragmented on disk to increase performance when the images that Storage Migrator has migrated are restored.575 megabytes. the entire backup is discarded.234 Storage units. enter a value from 20 megabytes to 524.048. unit groups.287 megabytes. If an error occurs in a backup. Generally. and lifecycle policies Storage unit settings The df command may report a percentage used (Use%) value that is different from the % full value. For example. Consult the vendor's documentation for guidance. place a check in the Reduce fragment size check box. . To specify a maximum fragment size other than the default. NetBackup starts at the beginning of the multiplexed backup and reads tar headers until it finds the file. not from the fragment where the error occurred.287 megabytes. To specify a maximum fragment size other than the default. Storage Migrator needs to retrieve only the specific fragment with the file rather than the entire 500 megabytes. Fragmenting multiplexed tape backups can expedite restores. The Reduce fragment size setting is intended primarily for storing large backup images on a disk type storage unit. The backup restarts from the beginning. (See the preceding Available Storage topic for a description of why the values appear differently. ■ Reduce fragment size The Reduce fragment size setting specifies the largest fragment size that NetBackup can create to store backups. unformatted size of the storage in the disk pool. Usable size The amount of usable storage in the disk pools. For disk storage units: The default maximum fragment size for a disk storage unit is 524. ■ For Media Manager storage units: The default maximum fragment size for a Media Manager storage unit is 1000 terabytes. Fragments allow NetBackup to skip to the specific fragment before searching for a file.

. The Storage unit name is the name used to specify a storage unit for policies and schedules. and lifecycle policies Storage unit settings 235 fragments before and including the last checkpoint are retained. It is the same robot number used in the Media Manager configuration. For the specific vendor types and models that correspond to each robot type. see “NetBackup naming conventions” on page 629. Storage device The Storage device list contains all possible storage devices available. unit groups. Storage unit name Type a unique Storage unit name for the new storage unit. Upon upgrade. see “Temporary staging area” on page 236 and “Basic disk staging” on page 240. Robot type The Robot type and indicates the type of robot (if any) that the storage unit contains. see the Supported Peripherals section of the NetBackup Release Notes. Robot number The Storage device selection determines the Robot number. To make the best use of upgraded storage units. For more information on robot numbers.287 megabytes. the disk storage units are not automatically increased to the new default of 524. Staging relocation schedule (for basic disk staging only) Click the Staging schedule button to configure the relocation schedule for this storage unit. For more information. increase the fragment size on the upgraded storage units. The name could describe the type of storage. the backup image is duplicated from the temporary staging area to the final destination storage unit. The Robot type is determined by the Storage device setting. During the relocation schedule. the fragments after the last checkpoint are discarded. A schedule is what makes the disk storage unit into a basic disk staging storage unit. see “Robot number” on page 601. For more information about basic disk staging.Storage units.) Note: Basic disk staging units with different maximum fragment sizes may already be configured on a media server from a previous release. Storage units can be created for the listed devices only.

Transfer throttle The Transfer throttle setting appears for SnapVault storage units only. which is a very slow transfer rate. select <Use Any Available Media Server>. and lifecycle policies Storage unit settings The storage unit name cannot be changed after creation. . unit groups. ■ Temporary staging area If the storage unit is to be used as a temporary staging area. For example. (In case bandwidth needs to be reserved for other applications. click the temporary staging checkbox. Media Manager: see “Media Manager storage unit considerations” on page 216.236 Storage units. see “Staging relocation schedule (for basic disk staging only)” on page 235. For more information. The Storage unit name is inaccessible in a Change Storage Unit operation. NDMP: see “NDMP storage unit considerations” on page 223.) A value greater than 0 indicates a transfer speed for SnapVault in kilobytes per second. (Range: 0 to 9999999. configure the staging schedule. For more information about basic disk staging. a value of 1 sets a transfer speed limit for SnapVault of 1 kilobyte per second. see “Temporary staging area” on page 236 and “Basic disk staging” on page 240.) Zero (default) means no network bandwidth limit for the SnapVault transfer: SnapVault uses all available bandwidth. Then. 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. Use any available media server To allow any media server in the media server list to access the storage (default). This setting makes it possible to limit the amount of network bandwidth that is used for the SnapVault transfer. 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 218. For AdvancedDisk storage: ■ The required software plug-in is installed automatically with NetBackup.

Login credentials to the disk array must be configured on the media server. and lifecycle policies Storage unit settings 237 ■ Only the media servers that are configured as storage servers appear in the media servers list. Login credentials to the storage server must be configured on the media server. NetBackup media servers function as data movers. The software plug-in is provided by the storage vendor.) If a media server does not appear in the list. (For OpenStorage. verify that the software plug-in is installed and that logon credentials are created. Only the media servers that are configured as data movers for the OpenStorage implementation appear in the media server list. verify that the software plug-in is installed and that login credentials are configured for that media server. A software plug-in must be installed on each media server. unit groups. The required software plug-in is installed automatically with NetBackup. See the Veritas NetBackup PureDisk Remote Office Edition Administrator’s Guide for the media server requirements. If a server does not appear. For OpenStorage storage: ■ ■ ■ For SharedDisk storage: ■ ■ ■ For PureDisk storage: ■ . Only the media servers on which storage server login credentials are configured appear in the media servers list.Storage units.

then final storage Staging backups is the process in which a backup is written to a storage unit. Staging allows the backups to run when tape drives are scarce. then duplicated to a second storage unit. or until the disk needs additional space. 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 data is not copied per a specific schedule. the administrator can configure the data to remain on the storage unit until either a fixed rention period is met. SnapVault. First. No BasicDisk. however. data is copied to the final location. 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. and tape. . data is stored on the initial storage unit (disk staging storage unit). see “Basic disk staging” on page 240. or until the data is duplicated to the final location. This two-stage process allows a NetBackup environment to leverage the advantages of disk-based backups for recovery in the short term. NearStore. Then. Instead. The Policy storage unit/lifecycle selection determines whether the backup goes to a storage unit or a lifecycle. then final storage Staging backups to initial storage. Two staging methods NetBackup offers two methods to stage backups: ■ Basic disk staging Basic disk staging consists of two stages. Staging allows data to be streamed to tape without image multiplexing. per a configurable relocation schedule.238 Storage units. and lifecycle policies Staging backups to initial storage. The following storage unit types are available for basic disk staging: BasicDisk. For more information. Staging also meets the following objectives: ■ ■ ■ Staging allows for faster restores from disk. ■ The staging method that is used is determined in the policy Attributes tab. see “Storage Lifecycle Policies” on page 249. unit groups. or disk staging storage units can be used as destinations in a lifecycle. For more information. Eligible backups are deleted on the initial storage unit when space is needed for more backups.

Storage units. and lifecycle policies Staging backups to initial storage. . unit groups. then final storage 239 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.

The relocation schedule on the disk staging storage unit determines when the images are copied to the final destination. 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. 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 Policy storage selection in the policy indicates a storage unit that has a relocation schedule configured. The Job Details in the Activity Monitor identify the job as one associated with basic disk staging. Then. The schedule is configured in the New or Change Storage unit dialog by clicking Staging Schedule. The job looks for any data that can be copied from the disk staging storage unit to the final destination.240 Storage units. 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 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. unit groups. NetBackup expires the images on the disk staging storage unit to create space. . The Job Details list Disk Staging in the job’s Data Movement field. When NetBackup detects a disk staging storage unit that is full. Stage II: Images are copied from the Stage I disk staging storage unit to the Stage II storage unit. it pauses the backup. NetBackup finds the oldest images on the storage unit that have been successfully copied onto the final destination.

■ 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. with full backups done on Sunday. (In our example. the disk images remain on the disk for one week. Incremental backups are done Monday through Saturday. To determine the minimum size for the storage unit in this example. The full backups are sent directly to tape. the average nightly backup is 400MB and the NetBackup administrator wants to keep the images for one week.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. 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. use the following formula: Minimum size = Max data per cycle * (1 cycle + 1 cycle for safety) For example: 1. 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. the relocation schedule runs nightly. To double the value gives the administrator an extra schedule cycle (one day) to correct any problems. and lifecycle policies Basic disk staging 241 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. Consider the following example: A NetBackup administrator wants incremental backups to be available on disk for one week. unit groups. Symantec recommends that you double this value to allow for any problems that may occur when the relocation schedule runs. Symantec recommends a dedicated file system for each disk staging storage unit. a Media Manager (tape) storage unit.) In this example. . and the largest nightly backup is 700MB.Storage units. Occasionally a backup is 700MB. Each following day the relocation schedule runs on the disk staging storage unit and copies the previous night’s incremental backups to the final destination. Each night’s total incremental backups are sent to a disk staging storage unit and average from 300MB to 500MB. and do not use basic disk staging. In this example.

To find the potential free space on a BasicDisk storage unit. -dp Specifies the disk pool name. the disk pool name is the name of the BasicDisk storage unit. In the case of BasicDisk storage units.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.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. and lifecycle policies Basic disk staging To determine the average size for the storage unit in this 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. Use the following options. To determine the maximum 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. For a basic disk type. The space is the total size of the images that are eligible for expiration plus the images ready to be deleted on the volume.242 Storage units. . use the bpstulist and the nbdevquery commands. Note that the name of the storage unit and disk pools are case-sensitive. including the potential free space. unit groups. use the following formula: Maximum Size = Max data per cycle * (# of cycles to keep data + 1 cycle for safety) For example: 4. the name of the disk pool is the same as the name of the BasicDisk storage unit. In the following example. the level of service is that disk images remain on disk for one week. where: -stype server_type Specifies the vendor-specific string that identifies the storage server type. In this example. enter BasicDisk. For a BasicDisk storage unit. Run bpstulist -label to find the disk pool name.

Enter the absolute path to the directory to be used for storage. Select a media server. Click Actions > New > New Storage Unit. Storage unit information appears in the Details pane. Select Disk as the Storage unit type. Complete the New Storage Unit dialog box: ■ 2 3 Name the storage unit. see “Storage unit name” on page 235. For more information. and lifecycle policies Basic disk staging 243 nbdevquery -listdv -stype BasicDisk -dp NameBasic -D The value is listed as potential_free_space. unit groups.Storage units. select NetBackup Management > Storage > Storage Units. For more information. 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 the Disk type of disk storage unit that is to be a disk staging storage unit. see “Media server” on page 229. For more information. see “Absolute pathname to directory/volume” on page 224. The New Storage Unit dialog box appears.

■ ■ Select a storage unit to contain the images from this storage unit upon relocation. see “High water mark” on page 226. see “Priority of relocation jobs started from this schedule” on page 246.244 Storage units. NetBackup can create up to four copies of a backup simultaneously. Select a volume pool to contain the images from this storage unit upon relocation. the Maximum backup copies Global host property must include an additional copy beyond the number of copies that are indicated in the Copies field. For more information. Select whether to create Multiple Copies. For more information. ■ ■ ■ 4 Complete the Disk Staging Schedule dialog box. see “Multiple copies” on page 137. The Disk Staging Schedule dialog box appears. unit groups. Enter a Low water mark value. For more information. and lifecycle policies Basic disk staging ■ Select whether this directory can reside on the root file system or system disk. With the Multiple copies attribute enabled. For more information. For more information. Enter the maximum concurrent jobs that are allowed to write to this storage unit at one time. Note: For disk staging storage units. Once the option is enabled. For more information. Check the Enable temporary staging area option. see “Low water mark” on page 226. Select a media owner to own the images from this storage unit upon relocation. The High water mark does not apply to basic disk staging. Select the priority that the relocation jobs that are started from this schedule have compared to other types of jobs. For more information. see “Final destination storage unit” on page 246. see “Final destination volume pool” on page 246. see “Directory can exist on the root file system or system disk” on page 224. The differences appear on the Attributes tab: ■ ■ The schedule name defaults to the storage unit name. For more information. see “Final destination media owner” on page 246. The dialog box is similar to the scheduling dialog box used to configure policies. ■ ■ . the Staging Schedule button becomes enabled. Click the Staging Schedule button. see “Maximum concurrent jobs” on page 227. For more information.

see “Use alternate read server” on page 247. . and lifecycle policies Basic disk staging 245 ■ Select whether to use an alternate server for the images from this storage unit upon relocation. The dialog is similar to the scheduling dialog box that appears when a policy is configured. unit groups. Figure 5-8 Disk Staging Schedule for a basic disk staging storage unit The differences appear on the Attributes tab.Storage units. as described in the following sections: Name The schedule name for a disk staging schedule automatically defaults to the name of the storage unit. 5 6 Click OK to accept the disk staging schedule. 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. Click OK to add the storage unit. For more information. Disk Staging Schedule dialog Click the Staging Schedule button to display the Disk Staging Schedule dialog box.

Range: 0 (default) to 99999 (highest priority). For more information. ■ Final destination media owner The Final destination media owner is the media owner where the images reside after a relocation job copies them. NetBackup uses all of the drives available in the Final destination storage unit.246 Storage units. see “Low water mark” on page 226. 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. However. 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. For more information. To copy images to tape. Final destination volume pool The Final destination volume pool is the volume pool where the images reside after a relocation job copies them. Final destination storage unit The Final destination storage unit is where the images reside after a relocation job copies them. see “Maximum concurrent write drives” on page 227. A server group. The setting determines how many duplication jobs can be launched to handle the relocation job. ■ ■ . NetBackup chooses a media server or a server group (if one is configured). Specify one the following: ■ Any lets NetBackup choose the media owner. but you want a media server to own the media. NetBackup continues to free space until the Low water mark is reached. No media server is specified explicitly. A server group allows only those servers in the group to write to the media on which backup images for this policy are written. All server groups that are configured in the NetBackup environment appear in the drop-down list. None specifies that the media server that writes the image to the media owns the media. unit groups. the Maximum concurrent write drives setting for that storage unit must be set to reflect the number of drives.

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. The path to the disk or directory must be identical for each media server that is to access the disk. specify an alternate read server that is: ■ Connected to the storage device that contains the original backups (the source volumes). see “Checkpoint restart for backup jobs” on page 101. inventory the media in the new robot. Storage unit information appears in the Details pane. An alternate read server is a server allowed to read a backup image originally written by a different media server. To avoid sending data over the network during duplication. An administrator must move the media. and lifecycle policies Basic disk staging 247 Use alternate read server The Alternate Read Server attribute applies to NetBackup Enterprise Server only. To initiate a relocation schedule 1 In the NetBackup Administration Console. Basic disk staging limitations The basic disk staging method does not support the backup images that span disk storage units. If the backup image is on a robot that is not shared or a stand-alone drive. Select a basic disk staging storage unit in the Details pane. select NetBackup Management > Storage > 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. Connected to the storage device that contains the final destination storage units. the media must be moved to the new location.Storage units. unit groups. the media servers must share the same tape library or the operator must find the media. For more information. 2 . and execute bpmedia -oldserver -newserver or assign a failover media server. If the backup image is on tape. data is sent over the network. ■ If the final destination storage unit is not connected to the alternate read server.

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. and lifecycle policies Basic disk staging 3 Select Actions > Manual Relocation to initiate the schedule.248 Storage units. . unit groups. see “Maintaining available space on disk storage units” on page 221. If the relocation schedule finds data that can be copied. For more information.

the lifecycle process works to create copies of the images on each destination. The policy that writes the data must indicate that the backup data is to go to a lifecycle policy. along with the prescribed retention period for each copy. A lifecycle policy is configured within the Storage Lifecycle Policies utility Essentially. It also preserves the advantages of tape-based backups for long term storage. 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. and lifecycle policies Storage Lifecycle Policies 249 Storage Lifecycle Policies A storage lifecycle policy is a storage plan for a set of backups. A data classification represents a set of backup requirements. email data and financial data. Duplication destinations are optional. NetBackup retries the copies as necessary.Storage units. This process can occur if the NetBackup administrator has set up a lifecycle policy that contains at least one backup destination. to ensure that all copies are created. a lifecycle is a list of destinations where copies of the backup images are stored. This selection determines whether the destination is a backup destination or a duplication destination 2 NetBackup automatically copies the image to all duplication destinations in the lifecycle. . unit groups. Lifecycles offer the opportunity for users to assign a classification to the data at the policy level. A storage lifecycle policy can also be set up to provide staging behavior. After a lifecycle is configured. The backup is retained on the backup destination until the retention period is met. For example. which makes it easier to configure backups for data with different requirements. A storage lifecycle operation consists of three steps: 1 A backup is written to all destinations in the lifecycle. and can provide another method for disk staging. This process allows the NetBackup administrator to leverage the advantages of disk-based backups in the near term.

Eventually.250 Storage units.) Indicate a Duplication job priority: Select the priority that duplication jobs have in relationship to all other jobs. unit groups. and lifecycle policies Storage Lifecycle Policies 3 The retention type that is selected for the destinations determines how long the backup resides on the destination. The New Storage Lifecycle Policy dialog box appears. select NetBackup Management > Storage > Storage Lifecycle Policies. 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. 3 Complete the New Storage Lifecycle Policy dialog box: ■ ■ Indicate a Storage lifecycle policy name: Name the storage lifecycle. Click Actions > New > New Storage Lifecycle Policy. (Optional. the images that the policy creates are written to all the destinations that are defined in the storage lifecycle.) (See “Data classification” on page 258. Indicate a Data classification: Select a data classification. In duplication jobs. NetBackup duplicates data from a backup ■ . NetBackup deletes the backup from the destinations to create more disk space. If a storage lifecycle is selected. To create a storage lifecycle policy 1 2 In the NetBackup Administration Console.

) 4 Click OK to create the storage lifecycle.) ■ Indicate the Storage destinations: Click the Add button to add storage destinations to the lifecycle. 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. and lifecycle policies Storage Lifecycle Policies 251 destination to a duplication destination within a lifecycle. (See “Storage destinations” on page 254. 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. (See “Duplication job priority” on page 254. After they are created.Storage units. The lifecycle may be used to create multiple copies. data classifications cannot be deleted. 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 3 Complete the New Destination dialog box: . The New Destination dialog box appears. Click Add. unit groups.

The lifecycle cannot be saved until the destinations is decreased. (During the duplication operation. or disk staging storage units can be used as destinations in a lifecycle. if a storage lifecycle policy contains multiple destinations.252 Storage units.) Indicate the Storage unit or storage unit group where the backups are to be written. or until the Maximum Backup Copies is increased. Writing multiple copies using a lifecycle NetBackup writes backups to all destinations in the storage destination list. the retention that is indicated in the lifecycle is followed. (See “Alternate read server” on page 258.) Indicate the Media owner if the storage unit is a Media Manager type and server groups are configured. unit groups.) Staged capacity managed.) If a policy is configured to back up to a lifecycle. SnapVault. No BasicDisk. 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. a multiple copies operation is implied. . (See “Retention type: Staged capacity managed” on page 256. (See “Media owner” on page 255.) Expire after duplication. (See “Storage unit” on page 255. (See “Retention type: Fixed” on page 256. backups are duplicated to secondary storage. Note: The number of destinations that are added to the lifecycle cannot exceed the Maximum Backup Copies setting in the Global host properties.) (See “Use storage destination for: backup or duplication” on page 255. (For backup destinations only. Therefore. The Retention attribute in the schedule is not followed. (Limit: four backup storage destinations. (See “Volume pool” on page 255.) 4 Click OK to create the storage destination.) Indicate the Volume pool where the backups (or copies) are to be written.) The backup destinations must meet the criteria for multiple copies: the backups must go to the same media server. 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.) Indicate the retention type for the destination: ■ ■ ■ ■ ■ ■ Fixed retention type. ■ ■ Indicate an Alternate read server.) (See “Retention type: Expire after duplication” on page 258.

Or. but less frequently. After all copies are complete. Copy order determined by destination order The order in which the destinations appear in a lifecycle determines the copy number of the backup.Storage units. For more information. To fulfill the backup on BU_2. but the backup to BU_2 is not successful. if a policy setup includes multiple copies. The policy’s Configure Multiple Copies dialog box includes the option to Fail all copies. However. the remaining copies can be set to either continue or to fail. unit groups. the Multiple copies option is disabled in the schedules configuration within the backup policy. NetBackup changes the retention period of an image to Infinite until all copies are created. the retention returns to the level as set in the policy that writes to the storage destination. all copies must be completed. (See “Multiple copies” on page 137. If a storage lifecycle policy contains more than one backup destination. To complete successful backups in the lifecycle. a duplication job is created from BU_1 to BU_2. NetBackup continues to try. in a storage lifecycle policy. the policy cannot select a lifecycle as a storage destination. Consider the following example: A lifecycle contains two backup destinations (BU_1. in the following figure. The duplication job is in addition to the jobs that are run for the three duplication destinations. Expiration is necessary to free up space on the storage unit for new backups. a backup destination may duplicate a backup onto another backup destination. The backup to BU_1 is successful. BU_2) and three duplication destinations. 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.) 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 policy’s configuration. If no copy is created. a lifecycle is configured to create three copies: ■ ■ Two copies to two different backup destinations One copy to a duplication destination . see “Using nbstlutil to administrate lifecycle operations” on page 261. For example. Note: Duplication jobs can be controlled using the nbstlutil command. and lifecycle policies Storage Lifecycle Policies 253 Use only one method to create multiple copies NetBackup permits only one method to create multiple copies. A lifecycle initially tries three times to create a copy. That option means that if one copy fails.

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. 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. and lifecycle policies Storage Lifecycle Policies To make sure that copy 1 is written to disk. 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. unit groups. enter the disk type destination before the tape destination. Range: 0 (default) to 99999 (highest priority).254 Storage units. NetBackup duplicates data from a backup destination to a duplication destination within a lifecycle. In duplication jobs. Storage lifecycle errors An error dialog is displayed if any of the following conditions are not met: . 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. For example. (See “Job priority” on page 104.) Storage destinations The storage destination list contains all the destinations (storage units and storage unit groups) that the storage lifecycle can use.

A storage lifecycle policy can point to a storage unit group that contains a BasicDisk storage unit.) If a storage lifecycle contains multiple backup destinations. Volume pool The Volume pool option is enabled for tape storage units.) . or disk staging storage units). Media owner A Media owner can be selected. and lifecycle policies Storage Lifecycle Policies 255 ■ All configured backup destinations for the storage lifecycle must be on the same media server. SnapVault. A Media owner is a group of NetBackup servers that are used for a common purpose. unit groups. 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. One of the destinations must be of a fixed retention type. a multiple copies operation is implied. Storage units or storage unit groups may appear in more than one lifecycle. Note: The storage destination list cannot contain other storage lifecycles. However. (See “Configuring server groups for media sharing” on page 614. backups are duplicated to secondary storage.) Storage unit Indicate the storage unit where the backups are to be written. ■ ■ 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. NetBackup does not select BasicDisk storage units from a storage group for a lifecycle policy. There must be at least one valid backup destination in the destination list. (See “Writing multiple copies using a lifecycle” on page 252. (During the duplication operation. Storage units or storage unit groups may be used in a storage lifecycle while also being used as stand-alone units.Storage units.

When the retention period is reached. (Or. For example. 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. expired backup copies are removed from the storage destination when the storage unit reaches the high water mark. The image remains on the tape device until all copies have been created. (This option is not available to tape storage units since tape capacity is considered to be infinite. 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. select a time period (or level) from the drop-down list.) The High water mark and Low water mark settings on the disk storage unit or disk pool determine how the space is managed.) Retention period The Retention period specifies exactly how long NetBackup retains the backups before the backups are expired. until the administrator uses nbstlutil utility to intervene. (See “High water mark” on page 226 and “Low water mark” on page 226. The images are not deleted if all copies have not completed. unit groups. Note: Every lifecycle must contain at least one destination with a fixed retention period.) If space is needed for new images. The files in the backup then become unavailable for restore. (See “Data Classification properties” on page 403. the images are not expired. NetBackup deletes information about the expired backup. If the images have not been duplicated to all of the destinations in the lifecycle after two days. The destination can be a backup or a duplication destination. NetBackup removes backup images on the storage destination until the low water mark is reached. To set the retention period. Retention type: Staged capacity managed A Staged capacity managed storage destination means that NetBackup automatically manages the space on the (disk) destination. the administrator selects a fixed retention for a tape device to keep images on tape for two days. It searches for images to remove in the following order: ■ ■ Any Backup images that have passed the Desired cache period setting.) .256 Storage units.

The Desired cache period becomes a target that NetBackup tries to maintain. After the backup is complete. For more information. Desired cache period The retention period for a staged capacity managed storage destination is not assured as it is for a fixed retention period. A backup can occur at the same time as the expiration process occurs. for the disk types that support single-instance store (SIS). NetBackup must know how much space a . 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. The volume may fill with fixed-retention images and not allow the space management logic to operate as expected. the low water mark may be slightly greater than its lowest possible value. unit groups. 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. even if the image is past its retention period. the backup data could remain on the storage destination longer than the Desired cache period indicates. If the space is not required. In order for Staged capacity managed to operate. see “Writing multiple copies using a lifecycle” on page 252. However. Mark all disk storage units that are used with lifecycles as On demand only.Storage units. an image is never deleted if it has not been duplicated to all destinations in the lifecycle. 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. Staged capacity managed functions to various degrees. any images that are not past the Desired cache period may be deleted. and lifecycle policies Storage Lifecycle Policies 257 Note: If more space is needed. However. ■ ■ ■ 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. To see exactly when the storage destination reaches the low water mark value is difficult. 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.

258 Storage units. email backup data may be assigned to the silver data classification and financial backup data backup may be assigned to the platinum classification. 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. unit groups. Data classification The Data classification allows the NetBackup administrator to classify data based on relative importance. Some OpenStorage storage units. The Data classification defines the level of data that the storage lifecycle is allowed to process. A storage lifecycle is not required to have a data classification. not duplication destinations. An Alternate read server can be specified for both backup and duplication destinations. The Data classification drop-down menu contains all of the defined classifications. depending on the vendor characteristics. ■ Retention type: Expire after duplication The Expire after duplication retention applies only to backup destinations. However. the name of the alternate server must be specified in the backup destination configuration. NetBackup cannot know exactly how much space a particular backup image occupies. For example. When data is staged to a tape device. To select a classification is optional. to use an Alternate Read Server as part of a duplication operation. With SIS enabled on the storage unit. . One data classification can be assigned to each storage lifecycle policy and applies to all destinations in the lifecycle. and lifecycle policies Storage Lifecycle Policies backup image uses. When data must meet different backup requirements. consider assigning different classifications. A classification represents a set of backup requirements. The financial data is assigned to the higher classification of platinum because backups of the financial data are consider more important. 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.

Data from the policy can be stored only in a storage lifecycle policy with the same data classification assigned to it. the description. unit groups.Storage units. However. The storage lifecycle defines what happens to the data from the initial backup until the last copy of the image has expired. If no classification is indicated. the data is managed according to the storage lifecycle configuration. all the images that the policy creates are tagged with that classification ID. the storage lifecycle accepts images of any classification or no classification. data classifications cannot be deleted.) . 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. The name. (In the NetBackup Administration Console. and lifecycle policies Storage Lifecycle Policies 259 If a data classification is selected. and the rank of each can be changed in the Data Classification host properties. Figure 5-10 Data classification assignment in the policy If a classification is indicated. If a classification is selected. 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. (See “Data Classification properties” on page 403. expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Data Classifications. the storage lifecycle stores only those images from the policies that are set up for that classification. Creating or changing a data classification NetBackup contains four default data classifications.) New data classifications can also be created.

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. ■ MAX_KB_SIZE_PER_DUPLICATION_JOB The MAX_KB_SIZE_PER_DUPLICATION_JOB parameter default is 25 gigabytes. This parameter indicates the total size that the image batch can reach before a duplication job is run for the batch. If the file is not present in the following directory. The NetBackup administrator can change how large the batch files can become. NetBackup uses the default parameters: install_path\NetBackup\db\config MIN_KB_SIZE_PER_DUPLICATION_JOB The MIN_KB_SIZE_PER_DUPLICATION_JOB parameter default is 8 gigabytes. One or all of the parameters can appear in any order in the LIFECYCLE_PARAMETERS file. NetBackup accumulates lists of similar images into a batch. Then. each batch of images is copied as a set in one duplication job. This parameter determines the maximum time between batch requests. When the size reaches the size as indicated by this parameter. the lifecycle requests a duplication job. To do so. regardless of the size. The lifecycle looks for completed images to be added to a batch every five minutes. unit groups. . no more images are added to the batch. or the MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB time has passed. If the minimum batch size is not reached by the time indicated.260 Storage units. This parameter determines how large the image batch can grow. or how frequently batch jobs are requested. MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB parameter default is 30 minutes. the administrator creates and changes the default parameters in the LIFECYCLE_PARAMETERS file. To prevent the lifecycle from running numerous small duplication jobs in frequent succession. instead of one image at a time. 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.

When to use nbstlutil NetBackup starts a duplication session every five minutes to copy data from a backup destination to a duplication destination. unit groups. If a duplication job fails. and lifecycle policies Storage Lifecycle Policies 261 LIFECYCLE_PARAMETERS file example The following is an example of the contents and syntax for a LIFECYCLE_PARAMETERS file. NetBackup retains the image information so that processing can resume.Storage units. If the job fails all three times. The command is found in the following location: install_path\NetBackup\bin\admincmd\nbstlutil Use nbstlutil to perform the following administrative actions: ■ List the contents of the EMM database. Inactivate (or suspend) pending and future lifecycle operations on selected image copies. Cancel pending duplication operations on the selected image copies. nbstlutil cannot affect the jobs that are currently running. the next three duplication sessions retry the job if necessary. A duplication job copies data from a backup destination to a duplication destination. . ■ ■ ■ See NetBackup Commands for Windows for a description of all the options available for nbstlutil. inactivate. the job is retried every 24 hours until it succeeds. the nbstlutil command can be used to cancel. Activate (or resume) suspended lifecycle operations on selected image copies. Use the Activity Monitor to intervene in the jobs that are running. Support may request this information to troubleshoot a lifecycle problem. NetBackup considers the job complete and does not try to run another duplication job. When a duplication job is canceled. The tables about the lifecycle-processed images can be printed. Specifically. or activate pending duplication jobs. 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.

That is. The nbstlutil command can be used to inactivate the lifecycle while tapes are added. .262 Storage units. the problem may take longer to resolve than three duplication sessions five minutes apart. a duplication job fails because the library doesn’t contain enough blank tapes. When ready. For example. 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. unit groups. The administrator may not want to wait 24 hours for the next duplication session. the lifecycle can be activated and duplication jobs would begin. It may take longer than 15 minutes to place additional blank tapes into the tape library.

the storage unit must not have reached the maximum concurrent jobs setting. out of media. When a storage unit group is used in a policy. Also. or if no unit has available space. The selection is based on the following factors: . down. A storage unit group name can be specified in a policy in the same way that individual storage units can be specified. When one of the specified conditions occurs. (Default. 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. the job fails and is not queued. the policy waits to write to it. Prioritized NetBackup chooses the first storage unit in the list that is not busy. unit groups.Storage units. NetBackup queues a job to wait for the first storage unit if the maximum concurrent jobs setting is reached. the next storage unit in the list is examined until NetBackup finds an available storage unit. NetBackup does not continue to select the same storage unit. Round robin NetBackup chooses the least recently selected storage unit in the list as each new job is started. NetBackup avoids sending jobs to busy media servers. If one is not available or if one does not have enough available space. The other storage units are used as failovers. and lifecycle policies Storage unit groups 263 Storage unit groups Storage unit groups allow you to identify specific storage units as a group. only the storage units that are specified in the group are candidates for the backup. Choose from one of the following selection criteria. the job fails and is not queued. or full. or out of media.) Failover NetBackup chooses the first storage unit in the list that is not down. If a storage unit is not available. If a storage unit is only busy. Load balance The Load balance option allows NetBackup to select storage units based on a capacity-managed approach.

a BasicDisk storage unit cannot be included in an existing storage unit group with Load balance enabled. Also.264 Storage units. 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. If the free memory drops below a determined threshold. 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 no history is available. then the overall rank of the media server drops. and lifecycle policies Storage unit groups 1 The rank of the media server. or if the number of running processes per CPU rises above a determined threshold. unit groups. the high water mark for the storage unit serves as a guide. NetBackup estimates the amount of space that the job may require. . The number of jobs on the media server. NetBackup considers the number of scheduled jobs on each media server. based on previous backup history. 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.

To decrease Limit jobs per policy reduces the workload on a media server on a specific network segment. unit groups. Other methods to distribute the backup workload The Load balance option is based on the media server load and requires a license. ■ . See “Limit jobs per policy” on page 103.Storage units. and lifecycle policies Storage unit groups 265 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. 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. Reconfigure policies or schedules to use storage units on other media servers.

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. (This assumes that master servers and media servers are on separate hosts. see “Maximum jobs per client” on page 432. Another solution is to use NetBackup’s bandwidth limiting. see “Limit jobs per policy” on page 103. if there are four drives in a robot. Another possibility is to increase the number of jobs that the media server can perform concurrently for the policies that back up the clients. For example. For more information.266 Storage units. To maximize the use of devices Use multiplexing.) To adjust the backup load on client Change the Maximum jobs per client global attribute. Or. allow only two to be used concurrently. For more information. To give preference to a policy Increase the Limit jobs per policy attribute for the preferred policy relative to other policies. and lifecycle policies Storage unit groups ■ Consider changing the Bandwidth host properties on one or more clients. unit groups. To reduce the time to back up clients Increase the number of jobs that clients can perform concurrently. and client as possible without causing server. increase the priority for the policy. Allow as many concurrent jobs per storage unit. ■ 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. client. to increase Maximum jobs per client increases the number of concurrent jobs that any one client can process and therefore increases the load. Decrease these numbers for slower networks. For example. or network performance problems. see “Limit jobs per policy” on page 103 and “Maximum jobs per client” on page 432. The locally available . or use multiplexing. For more information. ■ 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. policy. 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. Do not place all devices under Media Manager control.

Enter a storage unit group name for the new storage unit group. the On demand only option is satisfied and the device is used. The storage units must also share the same media server. The New Storage Unit Group dialog box appears.Storage units. For more information. expand NetBackup Management > Storage. Disk spanning within storage unit groups A backup may span storage units if a disk full condition is detected. and lifecycle policies Storage unit groups 267 storage units take precedence over the defined sequence of storage units in the group. If the unit is in a storage unit group that a policy requires. see “Policy storage” on page 97. For more information. You may have set up a storage unit to be On demand only. Right-click Storage Unit Groups and select New Storage Unit Group. 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. . Backups may span from one BasicDisk storage unit to another BasicDisk storage unit if the storage units are in the same storage unit group. unit groups.

268 Storage units. select the storage unit and click Move Up or Move Down. Storage units are listed in order of priority: The units at the top of the list having the highest priority in the group. Note: The storage unit group name is case-sensitive. To change the priority of a storage unit. and lifecycle policies Storage unit groups For more information. unit groups. select the storage units from the Storage units not in group list. Click Add. To remove storage units from the group. . Click Remove. 4 Add to or remove storage units from the group: a b c To add storage units to the group. see “NetBackup naming conventions” on page 629. select the storage units from the Storage units in group list.

) Failover. select NetBackup Management > Storage > Storage Unit Groups. (See page 263. Click OK. Hold down the Control or Shift key to select multiple storage units.) Load Balance. 5 Choose how storage units are to be selected within the group: ■ Prioritized.Storage units.) Symantec recommends the Load Balance criteria for disk staging storage units within a storage unit group. Choose the first storage unit in the list that is not busy. Select the storage unit group you want to delete from those listed in the Details pane. or out of media. Select Edit > Delete. 3 4 .) Round Robin. ■ ■ ■ 6 Click OK. (See page 269. and PureDisk storage units cannot be included in storage unit groups. (See page 263. unit groups. and lifecycle policies Storage unit groups 269 Note: SnapVault. (See page 263. NearStore. Choose the least recently selected storage unit in the list. down. Choose the first storage unit in the list that is not down or out of media. Deleting a storage unit group To delete a storage unit group 1 2 In the NetBackup Administration Console. A confirmation dialog box appears.

and lifecycle policies Storage unit groups .270 Storage units. unit groups.

Chapter 6 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. ■ ■ ■ ■ ■ ■ ■ “What is a NetBackup catalog?” on page 272 “Catalog protection” on page 278 “Recovering the catalog” on page 310 “Disaster recovery emails and the disaster recovery file” on page 310 “Archiving the catalog” on page 311 “Using the Catalog utility” on page 318 “Catalog maintenance and performance optimization” on page 342 Note: For information on how to configure catalog backups in cluster environments. . The various functions that an administrator can perform in the Catalog utility are also explained. refer to the NetBackup High Availability Guide.

It is by far the largest part of the catalog. For more information. which is used during the backups. schedule the catalog backups to occur on a regular basis thereafter. ■ ■ .272 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. For more information. see “Image database” on page 273. The catalog consists of the following parts: ■ Image database: The image database contains information about what has been backed up. you risk losing regular backups if there is a problem with the disk that contains the catalogs. Since NetBackup requires the catalog information to restore backups. Parts of the catalog The NetBackup catalog resides on the disk of the NetBackup master server. The catalogs also contain information about the media and the storage devices. configure a catalog backup before using NetBackup for regular client backups. Without regular catalog backups. NetBackup data that is stored in relational databases: The data includes media and volume data describing media usage and volume information. NetBackup configuration files: The configuration files include flat files concerning policy and schedule information. see “NetBackup relational database” on page 276. Then.

While most of the subdirectories are relatively small in the NetBackup catalogs. or even hundreds of gigabytes.conf Configuration files Relational database files \client_1 \Media_server Image database \Master \client_n \class \config \error \failure_history \images \ jobs \media \scripts License key and authentication information \class_template Image database The image database (Program Files\VERITAS\Netbackup\db\images) contains subdirectories for each client that is backed up by NetBackup. The image database on the master server may grow too large to fit on a single tape.db BMRDB. The image database contains: ■ ■ Image files (files that store only backup set summary information) Image . The database growth is an important consideration for offline.db NBDB. including the master server and any media servers.NetBackup Catalog What is a NetBackup catalog? 273 Figure 6-1 Catalog configuration (default) Install_path\VERITAS\ \NetbackupDB \Netbackup\db \Netbackup\vault \Netbackup\var \conf server.db BMR_INDEX. \images can grow to several tens. . It consumes about 99% of the total space that is required for the NetBackup catalog.db vxdbms.conf databases.db EMM_DATA.log BMRDB.log BMR_DATA.f files (files that store the detailed information of each file backup) The image database is the largest part of the NetBackup catalog. cold catalog backups.db EMM_INDEX.conf \data NBDB.

NetBackup configures the file layout automatically. the backup type.f file if the information for the catalog is less than 4 megabytes. For example. and Linux platforms. the information is stored in multiple . The image . fragment information. the backup ID. based on the size of the binary catalog. The image. Image . policy schedules. Image . . Compaq Tru64 UNIX. Generally. The file layout determines whether the catalog contains one . HP_UX. If the image catalog becomes too large for the current location. and the amount of data that is backed up.f files. For more information. generally less than 1 kilobyte in size. NetBackup stores the information in a single image. To determine catalog space requirements. The catalog conversion utility (cat_convert) can be used to upgrade an image database to the binary format. the expiration date. An image file contains only backup set summary information.f file is always greater than or equal to 72 bytes.274 NetBackup Catalog What is a NetBackup catalog? Image database growth depends on the number of clients. but less than 4 megabytes. Solaris.) Image files Each image file is an ASCII file. Image .f file plus nine additional .f files.f file multiple file layout When the file information for one catalog backup is greater than 4 megabytes.f files The binary catalog may contain one or more image . When the backup file of one catalog backup is less than 4 megabytes. (See “Catalog conversion utility” on page 348. see “Moving the image catalog” on page 349. image files range in size from 1 kilobyte to 10 gigabytes. and disaster recovery information.f files: one main image .f file single file layout NetBackup stores file information in a single image.f files in binary format for Windows.f files. The image database component of the NetBackup catalog uses the .f file. consider moving it to a file system or disk partition that contains more space. NetBackup uses one of two layouts: single file layout or multiple file layout. This type of file is also referred to as a files-file.f file may be large because it contains the detailed backup selection list for each file backup. AIX. see “Determining catalog space requirements” on page 342.f file or many .

f file and storing the files in the catstore directory improves performance while writing to the catalog.NetBackup Catalog What is a NetBackup catalog? 275 Separating the additional .f_imgDir0 00:40 catstore/test_1030680524_INCR.f_imgFile0 00:40 catstore/test_1030680524_INCR. -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_imgHeader0 00:40 catstore/test_1030680524_INCR.f files from the image . The main image.f_imgNDMP0 00:39 catstore/test_1030680524_INCR.f_imgRecord0 00:39 catstore/test_1030680524_INCR.f_imgExtraObj0 00:39 catstore/test_1030680524_INCR.f 00:08 catstore/test_1030680524_INCR.f_imgStrings0 00:40 catstore/test_1030680524_INCR.f file is always exactly 72 bytes.f_imgUserGroupNames0 .f-list 00:39 catstore/test_1030680524_INCR.

see “Enterprise Media Manager (EMM) database” on page 277.276 NetBackup Catalog What is a NetBackup catalog? NetBackup relational database NetBackup installs Sybase Adaptive Server Anywhere 9.conf Install_path\VERITAS\NetBackupDB\conf\databases. the database and the configuration files for the NBDB and the BMRDB databases are protected: ■ Database files: ■ ■ ■ ■ ■ Install_path\VERITAS\NetBackupDB\data\NBDB.conf Install_path\VERITAS\NetBackupDB\conf\server.1 during the master server installation as a private.0.db Install_path\VERITAS\NetBackupDB\data\EMM_INDEX. Bare Metal Restore (BMR) database (BMRDB). non-shared server for the NetBackup database (NBDB). 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 NBDB contains information about volumes and the robots and drives that are in NetBackup storage units.log (if BMR is installed) Install_path\VERITAS\NetBackupDB\data\BMR_DATA.db Install_path\VERITAS\NetBackupDB\data\EMM_DATA.db (if BMR is installed) Install_path\VERITAS\NetBackupDB\data\BMR_INDEX.db (if BMR is installed) ■ ■ ■ ■ Configuration files: ■ ■ ■ Install_path\VERITAS\NetBackupDB\data\vxdbms.conf Note: The catalog backup process copies this data to Install_path\VERITAS\NetBackupDB\staging and backs up the copy. ■ As part of the catalog backup.db Install_path\VERITAS\NetBackupDB\data\NBDB.log Install_path\VERITAS\NetBackupDB\data\BMRDB. The same installation of Sybase ASA is used for the optionally-licensed product. NetBackup database (NBDB): Also known as the Enterprise Media Manager (EMM) database. . The BMR database is created during the BMR installation process.db (if BMR is installed) Install_path\VERITAS\NetBackupDB\data\BMRDB. For more information.

NetBackup Catalog What is a NetBackup catalog? 277 For information about how the catalog uses Sybase ASA. and NDMP hosts Fibre Transport attributes . disk arrays. The NetBackup Resource Broker queries the EMM database to allocate storage units. and media. The host on which the EMM database resides is called the EMM server. 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. drives (including drive paths). see Appendix A. “NetBackup relational database” on page 687. 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.

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

279

Online, hot catalog backups use media from the CatalogBackup volume pool only. For more information, see “Online, hot catalog backup method” on page 279.

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

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 280. By using the Backup Policy Configuration Wizard. See “To configure an online, hot catalog backup using the backup policy wizard” on page 288. By selecting the NBU-Catalog type when creating a backup policy.

■ ■

Configure an online catalog backup using one of the following methods:

280 NetBackup Catalog Catalog protection

See “To configure an online, hot catalog backup using the policy utility” on page 289. 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 510. 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

4

Click Next.

NetBackup Catalog Catalog protection

281

5

On the Catalog Backup Policy screen, select a policy from the list of existing catalog backup policies.

6

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

7

282 NetBackup Catalog Catalog protection

Click OK.

8

Select the backup type. (User Backup does not apply for NBU-Catalog policies.)

NetBackup Catalog Catalog protection

283

9

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 290. 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, All day) are preset in the wizard, but can be customized using the Policies utility. 11 In the Start Window screen, define a window of time during which the catalog backup can start. The scheduled windows (Off hours, Working hours,

284 NetBackup Catalog Catalog protection

All day, Custom) 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. 12 Select where each disaster recovery image file can be saved on disk. The image file contains the disaster recovery information.

NetBackup Catalog Catalog protection

285

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 a UNC path (CIFS Windows share).
If necessary, enter the logon and password information to access the
Windows 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. 13 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: email1@domain.com,email2@domain.com

286 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 310. Also, see “Send in an email attachment” on page 194. Note: The disaster recovery email is not sent to the address that is specified in the Global Attributes property. The Administrator’s email Address specifies the addresses where NetBackup sends notifications of scheduled backups or administrator-directed manual backups. 14 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

287

15 The Catalog Backup Wizard resumes, with the new policy listed.

16 Click Next to finish the Catalog Backup Wizard. 17 The final Catalog Backup Wizard screen displays the total number of catalog backup policies for this master server.

18 Click Finish to complete the wizard.

288 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 510. 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 629.) 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

6

7

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

289

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.

9

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 629.) 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 93. 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 123.

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

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 431.) Increase the Maximum Concurrent Jobs setting on the storage unit where the backups are sent. (See “Maximum concurrent jobs” on page 227.)

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

291

■ ■

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.

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:

292 NetBackup Catalog
Catalog protection

By using the Catalog Backup Wizard. For more information, see “To configure an offline, cold catalog backup using the catalog backup wizard” on page 293. 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 298.

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

■ ■

■ ■ ■

cold catalog backup. Click Help within any wizard screen for more information on the wizard settings.NetBackup Catalog Catalog protection 293 To configure an offline. 3 On the Catalog Backup Method screen. 1 Launch the NetBackup Catalog Backup Wizard by clicking Configure the Catalog Backup in the right pane. Right-click the Catalog utility in the left pane and select Configure Offline NetBackup Catalog Backup. For more information. This procedure assumes that a storage device is configured and media is available in the CatalogBackup volume pool. Click Next. see “Adding volumes” on page 510. ■ 2 Click Next on the Welcome screen. cold catalog backup using the catalog backup wizard Note: Offline. The wizard is visible when either Master Server or NetBackup Management is selected in the left pane. cold catalog policies write only to media in the NetBackup volume pool. The wizard is also available using the following methods: ■ Select the Catalog utility. then select Actions > Configure Offline NetBackup Catalog Backup. select to configure an offline. .

If NetBackup cannot find or follow a path. The catalog paths on the master server are added automatically during installation.294 NetBackup Catalog Catalog protection 4 Indicate where the catalog files are located. (/usr/openv/netbackup/bp. and databases.conf. Generally.) If NetBackup Access Control (NBAC) is used in the NetBackup configuration. do not include the NetBackup master server configuration file in the offline catalog backup file list. the entire catalog backup fails. no action is required other than to ensure that the directories are listed. as well as vxdbms. add the following directives for each host in the NBAC domain: [host:]nbat [host:]nbaz Note: For UNIX master servers.conf is included in the list. (If the files have been relocated to different directories using nbdb_move.conf) If bp. Verify that the catalogs of the master server and each media server are included.conf.conf. it must not be recovered until all other catalog recovery is completed. The NETBACKUP_RELATIONAL_DATABASE_FILES directive automatically includes the database files in the Install_path\VERITAS\NetBackupDB\data\ directory. server. Verify that the path names are correct and are in the correct format. . the locations are automatically determined and the files are included.

The files that are associated with the NetBackup relational databases are automatically included in the catalog backup and don’t need to be listed here. the Media Type for the Destination screen displays. Specify removable media or disk for the backup. . For information on how to configure catalog backups in cluster environments. 6 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. For this example. paths to the catalog are not automatically added during installation and must be added to this list.) The paths are dynamically generated during the backup since the locations of these files can change. we’ll select Removable Media. (NBDB and BMRDB. refer to the NetBackup High Availability Guide. Notes Regarding the Absolute Pathname List ■ If you have moved the location of the catalog on the master server.NetBackup Catalog Catalog protection 295 If NetBackup is installed in a cluster environment. ■ ■ 5 If both removable media and disk is configured. verify that the NetBackup Catalog Backup entries are correct. On media servers. the new location must be specified.

we’ll select Disk. 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. 8 9 Specify whether the alternate destination for the catalog backup is to removable media or to disk. Alternate destinations adds protection in the event that a disk or tape that contains a catalog backup is lost.296 NetBackup Catalog Catalog protection 7 You may prefer to back up the catalog to two different locations. . For this example. The catalog backup alternates for each catalog backup. NetBackup creates the directory if it does not exist. NetBackup always backs up to the media that was not used for the previous catalog backup.

This shared directory must be available to the service account that the NetBackup Client service logs into at startup. start the Services application in the Control Panel. To specify another account. or to disk. Choose one of the following options: After each session of scheduled. or to disk. This schedule type requires that no jobs are running in order for the catalog backup to run. ■ A shared directory on another computer.) 10 The frequency of catalog backups is configurable. see “NetBackup naming conventions” on page 629. a second stand-alone tape drive. consider this option if there is only one scheduled backup session per day or night. After each session of scheduled backups Consider this option if you plan to send catalog backups to a robot. and specify the account. user. click the Startup button. a second stand-alone tape drive. the startup account is set to System.NetBackup Catalog Catalog protection 297 ■ An NFS-mounted file system or a link to an NFS-mounted file system that grants write access to the root user. follow the NetBackup naming conventions. By default. or manual backups Consider this option if you plan to send catalog backups to a robot. . In addition to the platform-specific file path separators (/ and \) and colon (:) within a drive specification on Windows. a tape stacker. a tape stacker. Also. (For more information. Then select the NetBackup Client service.

To configure an offline. cold catalog backup using the Actions menu Note: Offline. the changes that were made between the last catalog backup and the time of the disk crash are lost. see “Adding volumes” on page 510. Only when manually initiated Consider this option to run multiple backup sessions in a single day or night. expand NetBackup Management > Catalog.298 NetBackup Catalog Catalog protection 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. Caution: Back up the catalogs often. Click Finish to complete the wizard. cold catalog policies write only to media in the NetBackup volume pool. If catalog backup files are lost. 1 In the NetBackup Administration Console. For more information. 11 The final wizard screen displays the total number of catalog backup policies that are configured for this master server. Be certain to perform a manual catalog backup once a day or after a series of backups. . This procedure assumes that a storage device is configured and media is available in the CatalogBackup volume pool.

hot catalog backup.NetBackup Catalog Catalog protection 299 2 With the Catalog utility in focus. cold backup is scheduled. select Actions > Configure Offline NetBackup Catalog Backup. The NetBackup Catalog Backup dialog box appears containing four tabs: Intro. Schedule. The tab also tells whether or not an offline.) . Attributes. The tab reminds the users that another type of catalog backup is available that might serve their needs better: the online. (See “Catalog backups” on page 278. Specify the properties on each tab of the dialog box: ■ ■ ■ ■ 3 “Catalog intro tab” on page 299 “Catalog attributes tab” on page 300 “Catalog schedule tab” on page 305 “Catalog files tab” on page 306 4 Click OK. hot catalog backup policies are configured. Files. Catalog intro tab The Catalog Intro tab informs users as to how many online.

Media Server cannot be changed and is the NetBackup server where the catalogs reside.) Ensure that the media server list entry appears on the master server at the time that the NetBackup Request Manager and NetBackup Database Manager services are started. If you back up the catalogs to a media server. The list shows all servers that have a storage unit that is defined on the current master server. Media 1 and Media 2 Areas . 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. On NetBackup Server.300 NetBackup Catalog Catalog protection 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. modify the NetBackup catalog backup paths on the master server using the Catalog Files tab. (See “Catalog files tab” on page 306. select one from the drop-down menu. These are the media that NetBackup alternates between for catalog backups.

The hard drive that you use for the catalog backup must be different than the hard drive where the catalogs reside. choose Removable Media to select the automated device.NetBackup Catalog Catalog protection 301 The Media 1 and Media 2 Areas setting specifies the media to use for the catalog backups. If you do assign both. Symantec recommends the following choices for Media Type: 1 2 3 If you use a robot or a tape stacker. You do not have to assign both Media 1 and Media 2. If you use a stand-alone storage device for catalog backups. the destination of the catalog backup must be on a different drive. choose Removable Media and use the stand-alone device. By default. NetBackup alternates between the media. . Send the catalog backups to a hard drive. the catalogs are stored in the following locations: Install_path\NetBackup\db Install_path\NetBackup\var\global Install_path\NetBackupDB\data Where the default Install_path is C:\Program Files\VERITAS If you choose to back up the catalog to disk. If you use only one stand-alone drive (no robot or tape stacker). 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. Media Type The Media Type setting specifies the media type. the most convenient method is to choose Disk for the media type.

Importing consumes the time that you may not want to spend when you need to resume business activities. ■ Note: If a column does not appear. The volume cannot be currently assigned to NetBackup for backups because NetBackup does not mix catalog backups and regular backups on the same media. If the disks holding the catalogs and the catalog backup are both destroyed. Swapping tapes is inconvenient. the Time Assigned and the Status column for the volume updates. To back up to single tape drive involves swapping tapes in and out of the drive each time the catalogs are backed up. The volume must also meet the following requirements: ■ The volume must be in the NetBackup volume pool. Media ID If you’ve chosen Removable Media. select Columns > Layout. A natural disaster is more likely to destroy both the primary data and the backups if the backups are written only to disk. In the Set Column Layout dialog box. recovering without the catalog backup means manually importing all of the backup tapes to rebuild the catalogs. recovering your business data is much more difficult. expand Media and Device Management > Media. Once a catalog backup occurs. In this situation. look under Media and ensure that the Volume Pool column for the media ID displays NetBackup. The volume that is specified must be configured under Media in the same manner as other NetBackup volumes. Move a full set of the media to off-site storage on a regular basis. 4 If you have only one stand-alone drive (no robot or tape stacker) and inadequate space on a different hard drive. you must back up the catalogs to the same tape drive as the backups of your business data. right-click in the pane and from the shortcut menu. To locate an available volume. but it is required because NetBackup does not place catalog backups and the backups of business data on the same tape. Assuming the backups are on tape. choose Removable Media. The media ID must appear under Media and Device Management > Media.302 NetBackup Catalog Catalog protection Caution: The safest way to protect your data is to save all backups to removable media. set the specific column to Show. Find a volume where the Time Assigned column is empty and the Status column is 0. A backup that is written only to disk shares the same risks as the computers being backed up. specify a valid media ID. To verify. .

the contents of the volume itself are not altered until the next time the volume is used for a backup. Reassigning the volume can cause problems if. 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. NetBackup sends an email that includes the status of each catalog backup and the media ID that was used. Pathname (Disk Media Type) . If you delete a volume from the catalog backup configuration. A convenient way to track the media is to indicate an email address in the Global Attributes properties. The Status column shows 1 for these volumes. Click the Density box to list the densities that Media Manager supports and select the density. If NetBackup tracks catalog backup media in the catalog. However. you temporarily back up the catalog to a different volume. Do not use backspace to leave the Media ID box blank. Caution: An offline. then added back. The value is never if the volume has never been used for NetBackup catalog backups. All the backup data must fit on one tape. Therefore. set the Media Type value to None. you can also find these media IDs in the Media Manager volume listing. and the disk containing the catalogs crashes. NetBackup changes the Last Written date and time. Media Manager makes the volume available for reassignment. ■ ■ Media Density Specifies the media density for Removable Media type media. The Allocated information under Media 1 and Media 2 indicate when the media was allocated for NetBackup catalog backups. cold catalog backup cannot span a tape volume. for example. choose a media density that can hold all the data to be backed up. these IDs do not appear in the NetBackup media reports.) If the catalogs are intact. Notes on the Media ID ■ To delete the media for Media 1 or Media 2. the record is lost with the catalogs. However. Print the email or save it on a disk other than the disk containing the catalogs. (See “Global Attributes properties” on page 431. Note: If the media ID for a volume that was used for catalog backups is deleted.NetBackup Catalog Catalog protection 303 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.

(See “NetBackup naming conventions” on page 629. Type the path in the field. and specify the account. Then select the NetBackup Client service. In that case. Ensure that the path is a directory rather than a file. an error occurs when the backup is done (not when you specify the path). the catalog backups fail. For example. click the Startup button. the catalogs are stored in the following locations. observe the following precautions: ■ ■ ■ ■ . By default. NetBackup creates the directory if it does not exist. Always back up to a physical disk different from the disk containing the catalogs. the startup account is set to System. follow the NetBackup naming conventions. If the path is a file. For example: C:\dbbackup The path can be any of the following: ■ A directory on a disk that is attached to the master server. the Pathname is the path to the directory where you want to store the catalog backup. An NFS-mounted file system or a link to an NFS-mounted file system that grants write access to the root user. if your computer has two physical disks and the catalogs are on the first disk. To specify another account. If the disk fills up.304 NetBackup Catalog Catalog protection For disk media.) ■ ■ When the catalogs are backed up to disk. both the catalogs and the backups are lost. This shared directory must be available to the service account that the NetBackup Client service logs into at startup. so the destination of your catalog backup must be on a different disk: Install_path\NetBackup\db Install_path\VERITAS\NetBackup\var\global Install_path\VERITAS\NetBackupDB\data Where the default Install_path is C:\Program Files\VERITAS Ensure that the disk has adequate space for the catalogs. By default. A shared directory on another computer. back up the catalogs to the second disk. start the Services application in the Control Panel. If you back up the catalogs to the same disk and that disk fails. 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. restoring data for the NetBackup clients is difficult or impossible.

If catalog backup files are lost. ■ Caution: Do not use this schedule in NetBackup environments in which continual backup activity occurs. ■ Only when manually initiated . 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. Caution: Back up the catalogs often. or manual backups Backs up the catalogs after any session that results in the creation of at least one successful backup or archive. the changes that were made between the last catalog backup and the time of the disk crash are lost. A backup does not occur after a manual backup or a user backup or archive.NetBackup Catalog Catalog protection 305 Catalog schedule tab The Catalog Schedule tab contains selections concerning when you want to back up the catalogs. This schedule type requires that no jobs are running in order for the catalog backup to run. user. It could mean that the catalog backup would never have an opportunity to run. ■ After each session of scheduled.

conf. as well as vxdbms. be certain to do so once a day or after every series of backups. Right-click Catalog and select Back up NetBackup Catalog.conf. Click to navigate to a directory or file The catalog paths on the master server are added automatically during installation. no action is required other than to ensure that the directories are listed. If you elect to back up catalogs manually.conf. You must add the paths to the file list. The NETBACKUP_RELATIONAL_DATABASE_FILES directive automatically includes the database files in the Install_path\VERITAS\NetBackupDB\data\ directory. and databases. In the case of NetBackup Enterprise Server. the locations are determined automatically and are included. Therefore. select NetBackup Management > Catalog. Generally. Caution: If you elect to back up catalogs manually. Catalog files tab The Catalog Files tab contains the absolute paths to the catalog files to be backed up. (If the files have been relocated to different directories using nbdb_move.) On the Files tab: .306 NetBackup Catalog Catalog protection Does not automatically back up the catalogs. server. the paths to the NetBackup database on the media servers are not automatically added during installation. the master server and media servers may reside on different machines.

Edit the path.NetBackup Catalog Catalog protection 307 ■ To add a path. To change a path. click New and type the path in the Absolute Pathname list. select the path to delete and click Delete. It also depends on whether the backup is sent to the master server or to a remote media server. select the path and click Change. The path format depends on whether the catalog is on a master server or a remote media server. To delete a path. ■ ■ . Click outside the edit box to escape the edit box.

(/usr/openv/netbackup/bp. the entire catalog backup fails. ■ Absolute pathnames for catalogs on the master server The catalog paths on the master server are added automatically during installation.308 NetBackup Catalog Catalog protection Notes regarding the Absolute pathname list ■ If NetBackup Access Control (NBAC) is used in the NetBackup configuration.) The paths are dynamically generated during the backup since the locations of these files can change.conf is included in the list. prefix each path with the name of the media server: media_server_name:catalog_backup_path For example.conf) If bp. If NetBackup cannot find or follow a path. do not include the NetBackup master server configuration file in the offline catalog backup file list. The files that are associated with the NetBackup relational databases are automatically included in the catalog backup and don’t need to be listed here. and all information about the files that are backed up from client workstations: Install_path\NetBackup\db The files in the following directory contain license key and authentication information: Install_path\NetBackup\var Absolute paths for catalogs on media servers If you back up the catalog files that are on media servers. add the following directives for each host in the NBAC domain: [host:]nbat [host:]nbaz Note: For UNIX master servers. it must not be recovered until all other catalog recovery is completed. or have added new paths to the catalog backup configuration. error logs. Unless you back up the catalogs to a media server. generally no action is required other than to ensure that the directories are listed. have deleted old paths. ■ Make sure that the list does not contain invalid paths. to add the catalog files of a Windows NetBackup media server (mars) to the default installation path. (NBDB and BMRDB. Do so especially if you have moved the catalog files. The files in the following directory contain NetBackup scheduling information. add the following paths: mars:C:\Program Files\VERITAS\NetBackup\db mars:C:\Program Files\VERITAS\Volmgr\database mars:C:\Program Files\VERITAS\NetBackup\var .

No paths should be added for the media servers of the current version to be included in the cold catalog backup.NetBackup Catalog Catalog protection 309 The paths that you must add depend on the version of NetBackup that was installed on the media server. 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.

310 NetBackup Catalog Recovering the catalog 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.cmd script.) 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.cmd script in the Install_path\VERITAS\NetBackup\bin directory. Disaster recovery emails and the disaster recovery file The Catalog Backup Wizard asks whether you’d like the disaster recovery information to be sent to an email address.cmd script for use instructions. this information appears on the Disaster Recovery tab. hot catalog backups and offline. . Catalog recovery from online. the attached image file may be a full or an incremental catalog backup. The entire catalog is recovered because the incremental catalog backup references information from the last full backup. This script is similar to the nbmail. See the comments in the nbmail. Instructions for recovering the catalog The image file included as an attachment. hot catalog backup.) If the online catalog backup is configured using the Policy utility. You do not need to recover the last full catalog backup before you recover the subsequent incremental backups. (Only in the case of configuring an online. If a catalog backup policy included both full and incremental backups. Recovering from an incremental catalog backup completely recovers the entire catalog if Automatically recover the entire NetBackup catalog is selected on the wizard screen. cold catalog backups are discussed in the NetBackup Troubleshooting Guide. (See “Disaster Recovery tab” on page 193. You may tailor the disaster recovery email process by providing the mail_dr_info.

Catalog archiving operations must be performed when NetBackup is in an inactive state (no jobs are running). Catalog archiving is available on both UNIX and Windows platforms. NetBackup administration continues to require regularly scheduled catalog backups. For example: 2 .) Run bpcatlist to display images available for archiving. run: Install_path\VERITAS\NetBackup\bin\admincmd\bpcatlist -offline Note: The command returns a message of No entity was found if catalog archiving was not performed previously. pipe the output through bpcatarc and bpcatrm.NetBackup Catalog Archiving the catalog 311 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. (See “Creating a catalog archiving policy” on page 312. To determine what images have been previously archived run: Install_path\VERITAS\NetBackup\bin\admincmd\bpcatlist -online To determine what images have been previously archived.f files to secondary storage.f files removed. 3 Once the bpcatlist output correctly lists all the images to be archived. Note: Running bpcatlist alone does not modify any catalog images. 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.f files. Note: When you consider whether to archive the . but the backups are faster without the large amount of online catalog data. Only when the bpcatlist output is piped to bpcatarc and bpcatrm are the images modified and the image . Catalog archiving reduces the size of online catalog data by relocating the large catalog . 1 Create a policy named catarc to reflect that the purpose of the schedule is for catalog archiving.

Instead. bpcatarc activates this special policy to perform a catalog backup job. The policy can be reused for catalog archiving. 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. . If the job fails.f files are removed. The catarc policy waits until bpcatarc can activate it. run the following command: bpcatlist -client all -before Jan 1 2006 | bpcatres This command restores all the catalog archive files before Jan 1.312 NetBackup Catalog Archiving the catalog bpcatlist -client all -before Jan 1 2006 | bpcatarc | bpcatrm The command waits until the backup completes successfully before the command returns the prompt. For more information on the archiving commands. The File List for the job (double-click the job in the Activity Monitor) displays a list of image files that have been processed.f files. The Activity Monitor displays a Job ID for the job. no catalog . see “Catalog archiving commands” on page 314. then deactivates the policy after the job is done. An error is reported if the catalog archive fails. When the job completes with a status 0. run bpcatres to restore the actual files. To restore all the archived files from Step 2. 2006. bpcatrm removes the corresponding . 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. Policy name Create a new policy that is named catarc. Users do not run this policy.

. Type of backup The type of backup that is indicated for the catalog archive policy must be User Backup. On the Attributes tab. 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.NetBackup Catalog Archiving the catalog 313 Deactivate policy The catalog archive policy must be deactivated. clear the Active field. 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.

browse to the directory where catalog backup images are placed: Install_path\NetBackup\db\images Clients On the Clients tab.314 NetBackup Catalog Archiving the catalog You may find it useful to set up.f files. date. Then. Create a catalog list with bpcatlist The bpcatlist command queries the catalog data. For example. The schedule for catarc must include in its window the time bpcatarc command is run. then archive the files. enter the name of the master server. 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 operation fails. If bpcatarc is run outside of the schedule that is indicated in catarc. Catalog archiving commands The catalog archiving feature relies on three commands to designate a list of catalog . A fourth command. Files On the Files tab. is used to restore the files if necessary. bpcatlist lists the portions of the catalog that are based on selected parameters. bpcatres.

all depend on input from bpcatlist by a piped command..f files to proceed. the age of the backup image. 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.f alpha_0972327197_UBAK. The schedule for catarc must include in its window the time bpcatarc command is run.NetBackup Catalog Archiving the catalog 315 client. The other catalog archiving commands.f file is successfully backed up.Catarcid 2000 .f files created before January 1. and bpcatres..f For detailed information on bpcatlist. see bpcatlist in NetBackup Commands for Windows. indicating if the catalog has not been archived (1) or has been archived (2) Compressed status (C). 973187218 2000 . For example. After an. 973187218 2000 . 2006.f files. After an . For each catalog. it lists the following information: ■ ■ ■ Backup ID (Backupid) Backup date (Backup Date) Catalog archive ID (Catarcid). policy.f file is successfully backed up. The policy is based on a User Backup type schedule. or the date range of the backup image.. a catalog archive ID is entered into the catarcid field in the image file. a catalog archive ID is entered into the catarcid field in the image file. backup ID..) . (See “Creating a catalog archiving policy” on page 312. This field is zero if the image has never been archived.. Back up the catalog with bpcatarc The bpcatarc command reads the output from bpcatlist and backs up the selected list of ... bpcatrm.. the following would be entered: Install_path\VERITAS\NetBackup\bin\admincmd\bpcatlist -client all -before Jan 1 2006 | bpcatarc | bpcatrm bpcatlist is also used to provide status information. For archiving of the. to archive (backup and delete) all of the .f alpha_0972336776_FULL. bpcatarc. Archived status (S). bpcatlist outputs the formatted image summary information of matched images to standard output. schedule name. showing all of the backups for client alpha since October 23: # 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 . 973187218 S 1 1 1 C 0 0 0 Files file alpha_0972380832_UBAK. a policy by the name of catarc is required.

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 client’s records. a special retention level for catalog archive images. If the image file has valid catarcid entries.f file unless the file has been previously backed up using the catarc policy. The catalog archiving feature is for NetBackup administrators only. The storage provider can extract the customer images from the catalog archive by creating separate archives that are based on client name. the user receives an error message that states that the catalog image.f file has been archived. bpcatrm deletes selected image.f files from the online catalog. To specify retention levels. Use the bplist command to determine if a catalog. . You may find it useful to set up. create a separate media pool for catalog archives.f files to the catalog. Browsing offline catalog archive If a user tries to browse an offline catalog. bpcatrm does not remove an . To ensure that catalog backup images are not on the same tapes as user backups. Restore the catalog with bpcatres The bpcatres command reads the output from bpcatlist and restores selected archived. go to Host Properties > Master Server > Retention Periods or see “Retention Periods properties” on page 462. ■ ■ Using Vault with the catalog archiving feature Since the catalog archiving feature uses a regular User Backup schedule in the catarc policy. For example: Install_path\VERITAS\NetBackup\bin\admincmd\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).316 NetBackup Catalog Archiving the catalog Remove the catalog with bpcatrm The bpcatrm command reads the output from bpcatlist or bpcatarc. then designate. the files are duplicated and vaulted similarly to other backups.

Run bpcatlist so only the.f files from that client are listed. Indicate the volume pool for that client in the Attributes tab. 4 . For example: Install_path\VERITAS\NetBackup\bin\admincmd\bpcatlist -client clientname | bpcatarc | bpcatrm If you do not want to write more images to the client’s volume pool. change the volume pool before you run another archiving catalog.NetBackup Catalog Archiving the catalog 317 To extract images from the catalog archives based on a specific client 1 2 3 Create a volume pool for the client. Create a catalog archiving policy.

. Catalog backups are required for NetBackup to protect NetBackup internal databases. The Catalog utility is also used to perform other operations on catalog information. Expire backup images. For example: ■ Search for backup images to verify the contents of media with what is recorded in the NetBackup catalog. The catalog backups are tracked separately from other backups to ensure recovery in case of a server crash. Duplicate 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. The catalogs contain setup information as well as critical information about client backups. including specific media and date range Right-click Catalog to display menu Search results Searching for backup images Use the Catalog utility to search for a backup image.318 NetBackup Catalog Using the Catalog utility Using the Catalog utility Use the Catalog utility to create and configure catalog backups. ■ ■ ■ ■ Current master server Possible actions to perform Set search criteria. Import expired backup images or images from another NetBackup server. Promote a backup image from a copy to the primary backup copy.

Specify Verify. Expire backup images. To search on all media. Media ID The media ID for the volume. Type a media server name in the box or select one from the scroll-down list. Type a media ID in the box or select one from the scroll-down list. NetBackup uses the specific search criteria to build a list of backups from which you can make your selections. Import expired backup images or images from another NetBackup server. The type of the disk storage unit on which to search for backup images. Duplicate. or Import.NetBackup Catalog Using the Catalog utility 319 ■ ■ ■ ■ Duplicate the backup image to create up to 10 copies. To search through all media servers. The ID of the disk volume in the disk pool on which to search for backup images. Promote a copy of a backup to be the primary backup copy. Import. Duplicate. select All Media Servers. 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. select <All>. Media Server The name of the media server that produced the originals. The name of the disk pool on which to search for backup images. Disk type Disk pool Volume ID .

The range of dates and times that includes all the backups for which you want to search. data corruption within a block could be . Type a server name in the box or select one from the scroll-down list. Path Date/time range Copies Policy Client (host name) The host name of the client that produced the originals. select All Clients. The policy under which the selected backups were performed. To search through all policies. (See “Global Attributes properties” on page 431.320 NetBackup Catalog Using the Catalog utility Table 6-1 Search criteria NearStore Server Search criteria for backup images (continued) Description The name of the NearStore server to search for images. To search for an image on a disk storage unit. the operation does read each block in the image to verify that the volume is readable. This operation does not compare the data on the volume to the contents of the client disk. as they exist in part on the specified volume. Type of backup The type of schedule that created the backup. select All NearStore Servers. enter the path to search or select All to search all of the disk storage on the specified server. the imported backup is incomplete. Notes on searching for an image When you search for specific kinds of images. From the scroll-down list. Import image: If a backup begins on a media ID that was not processed by the first step of “To import backup images using the import images wizard– phase I” on page 330. select either Primary or the copy number. To search through all NearStore servers. note the following: ■ Verification image: Backups that have fragments on another volume are included. ■ 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. Type a schedule type in the box or select one from the scroll-down list. The Global Attributes property Policy Update Interval determines the default range. select All Backup Types. select All Policies. the backup is not imported. If a backup ends on a media ID that was not processed by the first step of “To import backup images using the import images wizard– phase I” on page 330. To search through all hosts.) The source you want to search. Type a client name in the box or select one from the scroll-down list. (However. However. Appears if the disk type is BasicDisk or NearStore. To search through all schedule types. Type a policy name in the box or select one from the scroll-down list.

Click the Results tab. the log file display is refreshed as the operation proceeds. then select the verification job to view the job results. select Enable full logging. Set up the search criteria for the image you want to verify. The Confirm Verify dialog box may appear.NetBackup Catalog Using the Catalog utility 321 possible. To verify backup images 1 2 3 In the NetBackup Administration Console. expand NetBackup Management > Catalog. If an operation is in progress. expand NetBackup Management > Catalog. To view or delete a log file 1 In the NetBackup Administration Console. . or import jobs appear in the Results tab.) NetBackup verifies only one backup at a time and tries to minimize media mounts and positioning time. To view a log file. The log file currently displayed appears in the bottom portion of the Results dialog box. Select the image you want to verify and select Actions > Verify. 4 Viewing job results The results of verify. select the name of the log from the list. Click Search Now. duplicate. To display information on each file that NetBackup verifies. The top portion of the dialog box displays all existing log files.

and Vault duplicates from the primary backup. . You can also right-click the log file and select an action from the scroll-down menu. you can designate one of the duplicates as the primary. the copy remaining in the robot is the primary backup. 3 Primary Copy status indicates that the image is now the primary copy 4 Click Actions > Set Primary Copy. To promote a backup copy to a primary copy 1 2 In the NetBackup Administration Console. Set up the search criteria for the image you want to promote to a primary copy.322 NetBackup Catalog Using the Catalog utility 2 3 4 Click the Results tab. In most circumstances. If your Vault profile performs duplication. If the primary copy is unavailable and a duplicate copy exists. NetBackup restores from the primary backup. NetBackup uses the primary copy to satisfy restore requests. Be sure that you’ve indicated a copy in the Copies field and not Primary Copy. (See “Searching for backup images” on page 318. expand NetBackup Management > Catalog. the next backup (if it exists) is promoted to primary automatically. When a primary backup expires. Click Search Now. Select a log file. Select Edit > Delete to delete the log. Select View > Full View to display the entire log file in a screen editor.) Select the image you want to promote. Promoting a copy to a primary copy Each backup is assigned a primary copy. select a copy of the backup and set it to be the primary copy. The first backup image that is created successfully by a NetBackup policy is the primary backup.

use the client interface on the client to restore files from the backup. To promote a backup copy to a primary copy using bpduplicate 1 Enter the following command: -npc pcopy Install_path\VERITAS\NetBackup\bin\admincmd\bpduplicate -backupid bid Where: Install_path is the directory where NetBackup is installed. the Primary Status column immediately reads Yes. For example. the following command promotes all copies on media belonging to the volume pool. 2007. pcopy is the copy number of the new primary copy. created after August 8. The report shows information about both copies. and Restore client interface. see NetBackup Commands for Windows. (See “Images on Media report” on page 79.NetBackup Catalog Using the Catalog utility 323 After the image is promoted to the primary copy. Specify the backup ID that is known (and also the client name if possible to reduce the search time). bid is the backup identifier as shown in the Images on Media report. After the duplicate copy is promoted to the primary copy. SUN. to be the primary copy: bpchangeprimary -pool SUN -sd 08/01/2007 The following command promotes copy 2 of all backups of client_a. To find the volume that contains the duplicate backup. 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. Archive. to be the primary copy: bpchangeprimary -copy 2 -cl client_a -sd 01/01/2007 For more information on bpchangeprimary.) The bpduplicate command writes all output to the NetBackup logs so nothing appears in the command window. see the online help in the Backup. 2007. use the Images on Media report. For instructions. created after January 1. .

cold catalog backup is running. Indicate the number of backup copies in Host Properties > Master Servers > Global Attributes > Maximum backup copies. 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. while the backup is created (unless making multiple copies concurrently). if multiple multiplexed groups are duplicated. The ■ duplicate is created with a single pass of the tape. from one server to another.) NetBackup does not verify in advance whether the storage units and the drives that are required for the duplicate operation are available for use. The storage units must be connected to the same media server.) Note: Do not duplicate images while an offline. when the backup has expired. (See “Global Attributes properties” on page 431. However. the multiplex settings of the destination storage unit and the original schedule are ignored. Notes on multiplexed duplication ■ When multiplexed backups are duplicated.) (See “Multiple copies” on page 137. This results in the catalog backup not having information about the duplication. from multiplex to nonmultiplex format. 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. (This option is sometimes referred to as Inline Copy. from one media density to another. NetBackup verifies that the destination storage units exist.324 NetBackup Catalog Using the Catalog utility Duplicating backup images NetBackup can create up to 10 copies of unexpired backups. by using NetBackup to schedule duplications automatically (unless you use a Vault policy to schedule duplication) of offline NetBackup catalogs. the grouping within each .) Note: An alternative to taking time to duplicate backups is to create up to four copies simultaneously at backup time. (A multiplexed group is a set of backups that were multiplexed together during a single session.

■ When backups in a multiplexed group are duplicated to a storage unit. However. The Setup Duplication Variables dialog box appears. Click Search Now. expand NetBackup Management > Catalog. ■ Procedure for duplicating backups NetBackup can create up to 10 copies of unexpired backups. The following items are exceptions: ■ If EOM (end of media) is encountered on either the source or the destination media. the duplicated group is identical as well. A fragment of zero length occurs if many multiplexed backups start at the same time. the storage unit must have the same characteristics as the unit where the backup was originally performed. If any of the fragments are zero length in the source backups.NetBackup Catalog Using the Catalog utility 325 multiplexed group is maintained. . Right-click the image(s) you want to duplicate and select Duplicate from the shortcut menu. the fragments are removed during duplication. This means that the duplicated groups have a multiplexing factor that is no greater than the factor that was used during the original backup. To duplicate backup images 1 2 3 In the NetBackup Administration Console. Set up the search criteria for the image you want to duplicate.

. All jobs must be duplicated to duplicate the catalog backup. hot catalog backup. select all child jobs that were used to create the catalog backup.326 NetBackup Catalog Using the Catalog utility Note: If you duplicate an online.

NetBackup Catalog Using the Catalog utility 327 4 Specify the number of copies you would like created. When the primary expires. only catalog volume pools are included in the drop-down list. the copies are created simultaneously. all volume pools are included in the drop-down list. Normally. If you want one of the duplicated copies to become the primary copy. check the appropriate check box. otherwise leave the fields blank. 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).) Specify the storage unit where each copy is stored. it can be used for both the source and destination. for example. copy 2 becomes primary when it expires. This ability is not supported on any storage units that use a QIC (quarter-inch cartridge) drive type. third-party copies. or optical devices. If the primary is copy 5. Both catalog and non-catalog volume pools are included. Otherwise. a different copy automatically becomes primary. copy 1 becomes primary when it expires. 5 The primary copy is the copy from which restores are done. the original backup is the primary copy. ■ . If a storage unit has multiple drives. If there are enough drives available. If the policy type was set to query for NBU-Catalog. 6 Note: The ability to make multiple copies concurrently (sometimes referred to as Inline Copy) is not supported on the following storage types: NDMP. the system may require operator intervention if four copies are to be created using only two drives. If the primary is copy 1. 7 Specify the volume pool where each copy is stored. (The copy that is chosen is the one with the smallest copy number.

) NetBackup uses the primary copy to satisfy restore requests. For example. 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. Only one backup is processed at a time.328 NetBackup Catalog Using the Catalog utility If the policy type was set to query for a policy type other than NBU-Catalog or All Policy Types. Because of this potential deadlock. . or select No change. A server group. No media server is specified explicitly.) By default. 2007 and its retention period is one week. including backup ID. ■ 9 Specify whether the remaining copies should continue or fail if the specified copy fails. only non-catalog volume pools are included in the drop-down list. (For example. either a media server or server group. ■ 8 Select the retention level for the copy. All media server groups configured in your NetBackup environment appear in the drop-down list. If you do not duplicate all the backups in a multiplexed group. 2007. the expiration date is the same for the duplicate and the source copies. Other attributes apply only to the primary. check Preserve Multiplexing. If a retention period is indicated. NetBackup first duplicates all backups that cannot be multiplex duplicated before the multiplexed backups are duplicated. You can use the bpexpdate command to change the expiration date of the duplicate. The duplicate copy shares many attributes of the primary copy. duplication is done serially and attempts to minimize media mounts and postitioning time. None specifies that the media server that writes to the media owns the media. if a backup was created on November 14. ■ If No Change is selected for the retention period. the new copy’s expiration date is November 21. If Preserved Multiplexing is enabled. but you want a media server to own the media. specify a different volume pool to ensure a different volume is used. the duplicate contains a different layout of fragments. 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. elapsed time. Any lets NetBackup choose the media owner. the expiration date for the copy is the backup date plus the retention period. (A multiplexed group is a set of backups that were multiplexed together during a single session. 10 Specify who should own the media onto which you are duplicating images: ■ ■ ■ 11 If the selection includes multiplexed backups and the backups are to remain multiplexed in the duplicate.

or if each copy fails for different reasons. Viewing the status of individual jobs allows you to troubleshoot jobs individually. the parent job displays a successful (0) status. and copy 2 is job 21. (See “Viewing job results” on page 321.NetBackup Catalog Using the Catalog utility 329 The Preserve Multiplexing setting does not apply when the destination is a disk storage unit. If at least one copy is successful.) Jobs displayed while making multiple copies When multiple copies are made concurrently. but copy 2 failed with a 800 status (disk volume cannot be used for more than one copy in the same job). selecting Preserve Multiplexing ensures that the tape is read in one pass. then select the duplication job to view the job results. Since at least one copy successfully completed. The parent job is 19. Use the Copy filter to display the copy number for a particular copy. copy 1 is job 20. For example. Use the Parent Job ID filter to display the parent Job ID. Copy 1 finished successfully. 13 Click the Results tab. The parent job displays the overall status. a parent job is displayed. However. whereas the copy jobs display the status of a single copy. the status of the parent job is successful. Copy 1 was successful. if one copy fails but the other copy is successful. if the source is a tape and the destination is a disk storage unit. but Copy 2 failed The parent job was successful because at least one copy was successful . plus a job for each copy. The following example shows a backup that contains two copies. 12 Click OK to start duplicating.

NetBackup recreates NetBackup catalog entries for the backups on the imported volume. Phase II: Images are selected for importing from the list of expired images that was created in Phase I. An image is imported in two phases. See “Using the physical inventory utility” on page 572. 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. (Supports Backup Exec versions 7. NetBackup supports the capability to import and restore the following Backup Exec backup types. run the vmphyinv physical inventory utility to update the Backup Exec media GUID in the NetBackup Media Manager database. (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 import capability is useful for moving volumes from one site to another and for recreating NetBackup catalog entries. No actual import occurs in Phase I. or backups written by Backup Exec for Windows. For information about using vmphyinv.330 NetBackup Catalog Using the Catalog utility Importing NetBackup or Backup Exec images NetBackup can import backups that have expired.1. The command needs to be run only once after creating the media IDs in the NetBackup Media Manager database. ■ Phase I: NetBackup creates a list of expired catalog entries for the backups on the imported volume.) During an import operation. backups from another NetBackup server. ■ To import backup images using the import images wizard– phase I 1 If you import Backup Exec media. . The command needs to be run only once after creating the media IDs in the NetBackup Media Manager database.0 through 9.

■ 8 Click Finish. To import Backup Exec media if the password contains non-ASCII characters: ■ Use the NetBackup Administration Console on Windows. Click Next. 2 3 4 5 6 7 Add the media IDs that contain the Media Manager backups to the server where the backups will be imported. see “Viewing job results” on page 321. see “To import backup images – phase II” on page 334. 1 To import Backup Exec media. run the vmphyinv physical inventory utility to update the Backup Exec media GUID in the NetBackup Media Manager database.NetBackup Catalog Using the Catalog utility 331 For information about using vmphyinv. The wizard explains the 2-step import process. Click Next. Or. No import occurs in Phase I. To complete the import. the job fails without a correct password. Select Import Images in the right pane to launch the wizard. was provided. 9 To initiate an import without the import wizard – phase I Phase I of the import process creates a list of expired images from which to select to import in Phase II. Click Next. For information about using vmphyinv. The wizard explains how to check the progress as the media host reads the media. enter the path from which the images are to be imported. the password is ignored. . See “Using the physical inventory utility” on page 572. If the media is not password-protected and the user provides a password. (The NetBackup-Java Administration Console cannot be used. The command needs to be run only once after creating the media IDs in the NetBackup Media Manager database. See “Using the physical inventory utility” on page 572. Type the name of the host that contains the volume to import.) Use the bpimport command. This wizard takes you through Phase I. If Backup Exec media is password-protected. Select whether the images to import are on tape or disk. This media server becomes the media owner. For more information. Import Images is available when Master Server or NetBackup Management is selected. The logs indicate that either no password or an incorrect password. Depending on whether the import is from tape or disk: Type the Media ID of the volume that contains the backups to import.

This media server becomes the media owner. ■ Enable Use Import Images Wizard to have the Import wizard guide you through Phase I of the import process. In the Media Server field. make the media accessible to the media server so the images can be imported. The Initialize Import dialog box appears. Under Image type. type the Media ID of the volume that contains the backups to import. If images are on tape: ■ ■ ■ In the Media ID field. Indicate the location of the image. In the NetBackup Administration Console. Select Actions > Initiate Import. specify the name of the host that contains the volume to import. expand NetBackup Management > Catalog. Validate the Backup Exec password by retyping the password in the field provided. Check whether or not the images to import are password-protected Backup Exec images. ■ .332 NetBackup Catalog Using the Catalog utility 2 3 4 To import the images from tape. select whether the images to be imported are located on tape or on disk.

the password is ignored. The logs indicate that either no password or an incorrect password. (The NetBackup-Java Administration Console cannot be used. The Catalog dialog box appears. For a BasicDisk type. import all of the child jobs that were used to create the catalog backup. If the disk type references a disk pool. If the media is not password-protected and the user provides a password. was provided. select or enter the name of the NearStore server and the NearStore volume. ■ ■ To import an online. Click OK. For a NearStore disk type. select the type of the disk storage unit on which to search for backup images. enter or browse to the path to the images in the field provided. hot catalog backup. the job fails without a correct password.NetBackup Catalog Using the Catalog utility 333 If images are on disk: ■ In the Disk type field. . The disk types depend on which NetBackup options are licensed. enter or select the disk pool and the disk volume ID. To import Backup Exec media if the password contains non-ASCII characters: ■ Use the NetBackup Administration Console on Windows. ■ ■ ■ Notes: ■ If Backup Exec media is password-protected.) Use the bpimport command.

334 NetBackup Catalog Using the Catalog utility 5 Click OK to begin reading the catalog information from the source volume. Unexpected EOF or Import of backup id failed. 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. fragments are not consecutive. the import fails with a message. run the Initiate Import (Import Phase I) first. 6 Click on the Catalog Results tab to see NetBackup look at each image on the tape. Note: If you import any backups that consist of fragments on multiple tapes. If Phase II is run before Phase I. start the Import (Phase II). each tape must be mounted and read. The job also displays in Activity Monitor as an Import type. . expand NetBackup Management > Catalog. For example. NetBackup determines whether or not each image has expired and can be imported. Note: In this phase. Select the import job log to view the job results. After Phase I. Phase I reads the catalog to determine all the tapes that contain fragments.

. Be sure to select a date range that includes the images you want to import. The Confirm Import dialog box appears.NetBackup Catalog Using the Catalog utility 335 2 Set up the search criteria to find images available to import by setting the search action 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 3 Select the image(s) you want to import and select Actions > Import.

Notes about importing backup images ■ NetBackup can import any disk images that were written by NetBackup 6. For example. we want to import a volume with media ID A00001. If you import an online. In the example. A volume with media ID A00001 already exists on the server. 2007 and its retention period is one week.0 or later. To import a volume with the same media ID as an existing volume on a server. You cannot import a backup if an unexpired copy of it already exists on the server. 2007. the new expiration date is November 21. use the following example. click the Results tab. All jobs must be imported to import the catalog backup. Importing expired images The expiration date for the imported items is the current date plus the retention period. if a backup is imported on November 14. import all the child jobs that were used to create the catalog backup. NetBackup does not direct backups to imported volumes. Remove information about media ID A00001 from the NetBackup catalog by running the following command: ■ ■ ■ ■ . hot catalog backup. then select the import job log. a b Duplicate the existing volume on the server to another media ID (for example. B00001).336 NetBackup Catalog Using the Catalog utility 4 To view the log.

For more information. Windows data to NetWare systems. along with the actual client name and path to create accurate. Importing from Backup Exec media does not convert or migrate Backup Exec job history. To avoid this problem in the future. NetBackup must know what the advertised name is. Actual Client. see “Backup Exec Tape Reader properties” on page 371. d Add the other A00001 to Media Manager on the server. or job descriptions to NetBackup. Host properties for Backup Exec The Backup Exec UNIX agent identifies itself to the Backup Exec server using a GRFS-advertised name. ■ ■ ■ ■ .0. 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. The advertised name may not have been the same as the real machine name and path. 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. Any Backup Exec backups that were created with the Intelligent Image Option cannot be restored. or UNIX data to NetWare systems.f file paths. If no entries are indicated. The operations include both local and remote IDR restores. Backup Exec images cannot be restored to clients on any platforms that were not supported by NetBackup versions before 5. and Actual Path properties in the Backup Exec Tape Reader host properties.0 or later to restore the Backup Exec images. Set the GRFS Advertised Name.NetBackup Catalog Using the Catalog utility 337 Install_path\VERITAS\NetBackup\bin\admincmd\bpexpdate mediaID -d 0 -m c Delete media ID A00001 from Media Manager on the server. NetBackup assumes that the advertised name is the real machine name and the advertised path is the real path. Importing images from Backup Exec media Clients must be at NetBackup 5. use unique prefix characters for media IDs on all servers. job schedules.

See “Using the physical inventory utility” on page 572. and Restore client interface. run the command. then restored using the NetBackup Backup. run a Phase I import on the first media of the spanned backup set. 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. SQL: Browsing and restoring differences Backup Exec SQL images are browsed. For information about using vmphyinv. Phase I can be run in any order in case the image spans multiple media. A NetBackup UNIX media server cannot import and restore the media in this case. the hardlinks are not restored. File level objects: Browsing and restoring differences When a user selects a Backup Exec file to restore. Spanned media: Importing differences To import a Backup Exec backup that spans multiple media. then perform Phase I and Phase II import operations. browsing. then restored using the NetBackup SQL interface. Create the media IDs in the NetBackup Media Manager database. must be imported and restored using a NetBackup Windows media server. The Backup Exec import process differs from the NetBackup import process. Then. Archive. Importing and restoring QIC media Backup Exec Quarter Inch Cartridge (QIC) media that was written in tape block sizes more than 512 bytes.338 NetBackup Catalog Using the Catalog utility ■ If Backup Exec hardlink backups are redirected and restored to partitions or drives other than the source partition or drive. and restoring Backup Exec and NetBackup images The following sections describe differences between Backup Exec and NetBackup when importing. but that is not the case. Differences between importing. The progress log may indicate that the hardlinks are restored successfully. In that NetBackup import process. . browsing. the directory where that file is located is restored. run a Phase I import on the remaining media of the spanned backup set in any order. NetBackup SQL images are browsed.

or all the files must be redirected to a different drive. The directory is restored even if the file was not specifically selected for restore. only the single file is restored.txt C:\hard_links\two.txt to a location on D:\ If all the files are to be redirected to a different drive. if the following hard link or SIS files are backed up: C:\hard_links\one. 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. NetWare: Restoring differences NetBackup does not support restoring Backup Exec NetWare non-SMS backups that were created using the NetWare redirector. 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). even though the objects were not selected for restore. Under some circumstances. are skipped. or Exchange SIS mail messages. NTFS SIS files. NTFS SIS files. either the files can be redirected to any location on C:\. ■ .txt C:\hard_links\three.NetBackup Catalog Using the Catalog utility 339 When a user selects a NetBackup file to restore. and Exchange SIS mail messages: restoring ■ When Backup Exec NTFS images are restored. specify that C:\ be replaced with D:\in the redirection paths. additional objects are sent to the client. When NTFS hard links. The directory named SIS Common Store is restored whether or not it is the actual NTFS single instance storage common store directory. The items are sent to the client when restoring objects from any backups that contain NTFS hardlinks. The following combination would be unsuccessful: C:\hard_links\one.txt to a location on C:\ C:\hard_links\two. any directory named SIS Common Store is restored.txt Upon restore. For example. NTFS hard links. 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 SIS files.

■ . Successful: The redirection paths specify that C:\hard_links be replaced with C:\redir_hard_links.340 NetBackup Catalog Using the Catalog utility ■ Unsuccessful: The redirection paths specify that C:\hard_links be replaced with D:\hard_links.

as explained in the table. Select the image you want to expire and select Actions > Expire.NetBackup Catalog Using the Catalog utility 341 Expiring backup images To expire a backup image means to force the retention period to expire. To expire a backup image 1 2 In the NetBackup Administration Console. When the retention period expires. Select Yes to begin to expire the images. “Search criteria for backup images” on page 319. Click Search Now. NetBackup deletes information about the backup. expand NetBackup Management > Catalog. The files in the backups are unavailable for restores without first re-importing. 3 4 . they cannot be used for restores. A message appears that announces that once the backups are expired. Set up the search criteria for the image you want to expire.

The number of file paths you must allow space for is four times the number of files in a full backup. for example): Files per Backup x Backups per Retention Period = Max Files For example: A daily differential incremental schedule backs up 1200 files and the retention period for the backup is seven days. Differential incremental backups are scheduled to run daily and have a retention period of one week. The full backups have a retention period of four weeks. Given this information. The following formula expresses the maximum number of files that can exist for each type of backup (daily or weekly.342 NetBackup Catalog Catalog maintenance and performance optimization 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. “Example reference table for catalog requirements” on page 344 shows that a full backup for policy S1 includes 64. Add to that number one week’s worth of incrementals. Determine the frequency and the retention period of the full and the incremental backups for each policy. For example: Assume that you schedule full backups to occur every seven days. 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 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. Use the information from steps 1 and 2 to calculate the maximum number of files that exist at any given time.000 files. the maximum number of files that can exist at one time are the following: 2 3 .

000 rather than 20. 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: . The additional megabytes account for the average space that is required for the error logs.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. For example. Increase the value if you anticipate problems.000.400. ■ Example: Estimating required catalog backup space Table 6-3 on page 344 shows backup schedules. For example. Calculate the maximum number of files that each policy can generate by using the information in Table 6-3. Using the results from the examples in step 3 yields: (8400 x 150) + (12. This changes the calculation in the example: the incremental changes from 1200 x 7 = 8400 to 3000 x 7 = 21. 4 Obtain the number of bytes by multiplying the number of files by the average length of the file’s full paths and file information.NetBackup Catalog Catalog maintenance and performance optimization 343 1200 x 7 days = 8400 A weekly full backup schedule backs up 3000 files and the retention period is four weeks. set the file size limit for the root user account to unlimited to support large file support.000 is added for the full backups. Note: For the policies that collect true image restore information. so the file size limit is 2GB. 20. the total for the two schedules is 33. The maximum number of files that can exist at one time are the following: 3000 x 4 weeks = 12. After 12. retention times. If you are unsure of the average length of a file’s full path. 5 6 File size considerations ■ Some UNIX systems have a large file support flag. and number of files for a group of example policies.400. use 100. an incremental backup collects catalog information on all files (as if it were a full backup). AIX disables large file support by default. Allocate space so all the data remains in a single partition. Add the separate totals to get the maximum number of files that can exist at one time. Turn ON the flag to enable large file support. For UNIX systems.000 Obtain the total for a server by adding the maximum files for all the schedules together.

59 megabytes (1.829.576 bytes in a megabyte) Add 15 megabytes for error logs to result in a final uncompressed catalog space requirement of: 475.000 114.000 114.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 Incremental Full Full Full Incremental Full Retention 1 month 1 year 1 month 1 year 1 week 1 month 1 year 1 week 1 month 3 months Infinite 1 month 1 year Number of files 1000 64.000 10.344 NetBackup Catalog Catalog maintenance and performance optimization 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) 2 Substitute values from the following table: 1000 files x 30 + 64.000 200 2000 2000 2000 200 5600 S2 Daily Monthly S3 Daily Weekly Monthly S4 Daily Weekly Monthly Quarterly WS1 Daily Monthly . Add the results to show that the total number of files for all policies is: 4.000 1000 70.600 files Multiply the total number of files by the bytes in the average path length and statistics (100 for this example).000 files Perform steps 1 and 2 for each policy.048.000 files x 12 = 798. The total amount of disk space that is required for file paths is: 460.

To perform a manual offline. To perform a manual online.000 Backing up catalogs manually Catalog backups typically run automatically because they are configured to do so using one of the catalog backup methods (online. Select the catalog backup policy you want to run. see “Performing manual backups” on page 197.NetBackup Catalog Catalog maintenance and performance optimization 345 Table 6-3 Policy WS2 Example reference table for catalog requirements (continued) Schedule Daily Weekly Monthly Backup type Incremental Full Full Retention 1 week 1 month 1 year Number of files 7000 70. expand NetBackup Management > Policies. hot catalog backup 1 2 3 In the NetBackup Administration Console. . Note: You can also run the bpbackup command from the command line to perform an online. cold catalog backup” on page 345.) ■ For directions on how to start each catalog method. cold catalog backup 1 In the NetBackup Administration Console.000 70. In this situation. automatic backups are not convenient. Select Actions > Manual Backup. hot catalog backup” and “To perform a manual offline. See NetBackup Commands for Windows for more information on bpbackup. For example. cold). a catalog backup can be started manually. hot or offline. The catalog backup tape must be inserted before each catalog backup and removed when the backup is done. If there is only one stand-alone drive and the stand-alone drive is used for catalog backups. hot catalog backup. (The tape swap is necessary because NetBackup does not mix catalog and regular backups on the same tape. if the system is schedule to be moved and you cannot wait for the next scheduled catalog backup. However. see “To perform a manual online. For more information. expand NetBackup Management > Catalog. A manual catalog backup is useful in the following situations: ■ To perform an emergency backup.

Volume II for more information on setting up this script. Note: If the volume for the catalog backup is not in a drive. In addition. ■ . This email can be configured with the mail_dr_info. see “Disaster recovery emails and the disaster recovery file” on page 310. provide information on NetBackup catalog backups. available from the Reports utility. 3 Click Yes to continue the backup.346 NetBackup Catalog Catalog maintenance and performance optimization 2 Select Actions > Perform offline backup of the NetBackup catalogBackup NetBackup Catalog to start the backup. For more information. See NetBackup Commands for Windows for more information on bpbackup. and Media Log reports. The Backup NetBackup Catalog dialog box appears. a mount request occurs. How do I know if a catalog backup succeeded? The All Log Entries. Problems. 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. The backup is saved to the least recently used of Media 1 and Media 2. cold catalog backup.cmd script. Note: You can also run the bpbackupdb command from the command line to perform an offline. See the NetBackup Administrator’s Guide. The dbbackup_notify script can be used to send an email for offline catalog backups. you can use: ■ Email: An email message is sent to the address indicated in the Disaster Recovery settings for an online catalog backup.

If you back up your catalogs to disk (not recommended). NetBackup does not keep a record of catalog backup media in its catalogs as it does with other backup media. You must manually track the media that is used for catalog backups. Do not use methods other than NTFS compression to compress the catalogs or NetBackup may not be able to read them. If you back up the catalog to the disk where the actual catalog resides. Backups to a full disk fail. alter the NetBackup catalog configuration manually to include the catalogs on the media servers. 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. see “Global Attributes properties” on page 431. If you send catalog backups to a robot. Recovering the catalog is much more difficult. NetBackup sends an email that includes the status of each catalog backup and the media ID that was used. Never manually compress the catalogs or NetBackup may be unable to restore the catalogs using bprecover. NetBackup does not support saving catalogs to a remote file system such as NFS or CIFS. The NetBackup binary image catalog is more sensitive to the location of the catalog. choose either of the two automatic backups: After each session of scheduled. the changes that were made between the last catalog backup and the time of the disk crash are lost. ensure that the disk has enough space for the catalogs. For more information.NetBackup Catalog Catalog maintenance and performance optimization 347 Strategies to ensure successful catalog backups ■ Use only the methods that are described in this chapter to back up the catalogs. If you use media servers. or manual backups or After each session of scheduled backups ■ ■ ■ ■ ■ Considerations to run offline. Catalog backups that are stored on a remote file system may have critical performance issues. Also. If catalog backup files are lost. a second stand-alone tape drive. both catalog backups are lost if the backup disk fails. user. a tape stacker. cold catalog backups: ■ ■ ■ . Print the email or save it on a disk other than the disk that contains the catalogs. A convenient way to track the media is to indicate an email address in the Global Attributes properties. or to disk. always back up to a different disk than where the catalog files reside.

remove the tape and store it in a safe place.0V or 4. which improves catalog performance for alternate backup methods. 4. NetBackup does not mix catalog and regular backups on the same tape. For more information. The catalog supports alternate backup methods without requiring post-processing. 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. especially for large file sizes.4. takes up less disk space than the text representations. stand-alone tape drive to back up both catalog and regular business data. Caution: The catalog backup tape must be removed when the backup is finished or regular backups cannot proceed. The catalog is much faster to browse and search. ■ ■ Catalog conversion utility NetBackup offers a catalog format conversion utility that the cat_convert command launches. 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.f files in the image database of NetBackup versions 3. This utility converts ASCII image. Because NetBackup does not place catalog and regular backups on the same tape. dates. When the backup is complete. Manually start the backup. both methods require you to swap tapes.348 NetBackup Catalog Catalog maintenance and performance optimization ■ If you use a single. . or Only when manually initiated if you run multiple backup sessions in a single day or night. see “Backing up catalogs manually” on page 345. The binary representations of numbers. choose either: ■ After each session of scheduled backups if you run only one backup session per day or night.5. to the binary format. and other information.

Check the Jobs tab in the Activity Monitor and ensure that no backups or restores are running for the client. NetBackup does not convert existing ASCII catalogs to the binary catalog format. The database should not be modified while this procedure is performed. For example. the path to the image catalog is: 2 3 4 . Note: NetBackup does not support saving the catalog to a remote file system.647 files = 7FFFFFFF files The maximum number of different user IDs and group IDs (combined): (231) – 1 IDs = 2.147.147. These services are stopped to prevent jobs from starting. either wait for them to end or stop them by using the Jobs tab in the Activity Monitor.NetBackup Catalog Catalog maintenance and performance optimization 349 Upon installation.483.647 IDs = 7FFFFFFF IDs ■ Moving the image catalog An image catalog may become too large for its current location. Backup the catalogs ensures that you can recover image information in case something is accidentally lost during the move. To move the image catalog 1 Back up the NetBackup catalogs. any new catalogs that are created in binary. Consider moving the image catalog to a file system or disk partition that contains more available space. However. Use the Services tab in Activity Monitor to stop the Request Manager and Database Manager services. 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. Create a file named ALTPATH in the image catalog directory. Therefore. If jobs are running. Symantec advises against moving the image catalog to a remote file system such as NFS or CIFS.483. if NetBackup is installed in the default location and the client name is mars. The cat_convert command is described in NetBackup Commands for Windows.

For example. specify the path to the directory where you intend to move the client’s image information. To index image header files. Without indexing. Indexing the catalog for faster access to backups If the NetBackup environment contains a large number of backups. NetBackup uses the indexes to go directly to the catalog entry for a file. run the following command: . For example: E:\NetBackup\alternate_db\images\client_name The path is the only entry in the ALTPATH file. if the images are currently in C:\Program Files\VERITAS\NetBackup\db\images\mars and the ALTPATH file specifies E:\NetBackup\alternate_db\images\mars then move all files and directories (except the ALTPATH file) to E:\NetBackup\alternate_db\images\mars Add the new image directory to the NetBackup catalog backup configuration. NetBackup must start searching for a file at the beginning of the catalog entries.350 NetBackup Catalog Catalog maintenance and performance optimization C:\Program Files\VERITAS\NetBackup\db\images\mars\ALTPATH 5 Create the directory to which you intend to move the image information. In the example. Move all files and directories (except the ALTPATH file) that are in the current client directory to the new directory. see “Catalog files tab” on page 306. Backups and restores can now resume for the client. To index the catalog means to create indexes of the files that are recorded in the NetBackup image catalog. For more information. consider indexing the catalogs to reduce the time that is required to restore files. you would add E:\NetBackup\alternate_db\images\mars 6 7 8 Caution: Failure to add the alternate image directory to the catalog backup configuration can result in loss of backup data if there is a disk failure. For example: E:\NetBackup\alternate_db\images\client_name On the first line of the ALTPATH file. 9 Start the NetBackup Request Manager and NetBackup Database Manager services by using the Services tab in the Activity Monitor.

NetBackup Catalog Catalog maintenance and performance optimization 351 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. Compress Catalog Interval. 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. remove these files. Use this property to specify how old the backup information must be before it is compressed. NetBackup allows you to compress all portions of the catalog or only older portions of the catalog. For more information. Specify the number of days to defer compression information. . see “Global Attributes properties” on page 431. By default. No method selectively compresses image-catalog files other than by age. thus users who restore files from recent backups are unaffected. Control image-catalog compression by setting the Global Attributes property. Compress Catalog Interval is set to 0 and image compression is not enabled.

To reduce the amount of media that is required to back up the catalog. a reduction of 80% is possible. The catalog must be in an NTFS partition for compression to occur. Full backups result in a larger percentage of catalog compression than incremental backups. begin by compressing the records for the backups older than 120 days. Since the information is uncompressed at each reference. Manually compressing or decompressing a catalog backup while any backup (regular or catalog) is running results in inconsistent image-catalog entries. If you choose to compress the image catalog. consider compressing the files in stages. more data is duplicated in a catalog file for a full backup.352 NetBackup Catalog Catalog maintenance and performance optimization Caution: Symantec discourages manually compressing or decompressing catalog backups using bpimage -[de]compress or any other method. the results could be incorrect. It does not make a difference to NetBackup if the backup session was successful. For example. Change the . This reduction in disk space and media requirements is achieved at the expense of performance when a user lists or restores files. When numerous compressed image-catalog files must be processed. To minimize the impact of the initial sessions. the backup session is extended until compression is complete. Compressing the image catalog can accomplish two objectives: ■ ■ To reduce greatly the disk space that is consumed. Using catalog compression. performance degradation is in direct proportion to the number and size of compressed files that are referenced. The amount of space that is reclaimed varies with the types of backups you perform. If the restore requires numerous catalog files to be uncompressed. Continue to reduce the number of days over a period of time until you reach a comfortable setting. Normally. When users list and restore files. you may need to increase the time-out value that is associated with list requests. NetBackup uses NTFS compression on the server to perform compression after each backup session. The additional backup time is especially noticeable the first time you perform the compression. The operation occurs while NetBackup expires backups and before is runs the session_notify script and the backup of the NetBackup catalogs.

for example. Select the Global Attributes properties. see “Global Attributes properties” on page 431. To uncompress the NetBackup catalog 1 Verify that the partition where the image catalog resides contains enough space to accommodate the uncompressed catalog. expand NetBackup Management > Host Properties > Master Server. Use the Activity Monitor or the Services application in the Windows Control Panel. Change to the following directory: install_path\veritas\netbackup\bin\admincmd Run one of the followings commands. In the NetBackup Administration Console.NetBackup Catalog Catalog maintenance and performance optimization 353 time-out value by changing the List Files Timeout General property setting on the client. (See “Determining catalog space requirements” on page 342. 2 3 4 5 6 . Double-click the host to be uncompressed. Open a command prompt. bprd. Verify that the NetBackup Database Manager. For more information. Click OK to save the host property change. Clear the Compress Catalog Interval check box. Uncompressing the image catalog You may find it necessary to uncompress all records temporarily that are associated with an individual client. bpdbm. is running.) Stop the NetBackup Request Manager service. Uncompress the records if you anticipate large or numerous restore requests.

. bprd.354 NetBackup Catalog Catalog maintenance and performance optimization To decompress the records for a specific client. enter: bpimage -decompress -client_name To decompress the records for all clients. enter: bpimage -decompress -allclients 7 Restart the NetBackup Request Manager service.

Chapter 7 Host properties This chapter describes the NetBackup property settings and explains how each can be changed for one or more servers or clients. and client host properties” on page 361 . This chapter contains the following sections: ■ ■ ■ ■ “Introduction to host properties” on page 356 “Changing host properties” on page 357 “Required permissions” on page 360 “Master server. media server.

and clients under Host Properties. 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 Details pane Right-click in the Details pane to view the shortcut menu The options on the Host Properties menu bar are described in the online help. . In most instances. however. media server. Viewing host properties The NetBackup Administration Console displays properties for NetBackup master server. the NetBackup defaults provide satisfactory results.356 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.

The NetBackup Administration Console is one way to change the host properties. . use bpsetconfig to change the entries. Select one or more hosts. click File > Change Server. Click File > Export. In the Details pane. or client properties 1 In the NetBackup Administration Console. Enter the full path name or browse to the directory and click Save. Changing host properties The NetBackup properties can be changed to customize NetBackup to meet specific site preferences and requirements. Media Servers. To export the properties of a host 1 2 3 Expand Master Servers. The Export Data dialog box appears. The commands are described in NetBackup Commands for Windows. the NetBackup defaults provide satisfactory results. Host properties can be set for a single host or for multiple hosts all at one time. media server. expand NetBackup Management > Host Properties.Host properties Changing host properties 357 To view master server. In most instances. To see the properties of a different master server. Another method is to first use the bpgetconfig command to obtain a list of configuration entries. double-click the server or client to view the properties. or Clients. Then. 2 3 Select Master Server. Media Server. or Clients.

■ ■ Edit field states If the property contains a text field for specifying a value. Radio button states None of the buttons in a radio button group appear selected when multiple hosts are selected. select the check box. ■ Note: In a clustered enviroment. Clear (unchecked) if the property has been set the same for all selected hosts. To set the property on all selected hosts. Gray check if the property is set differently on the selected hosts. host properties must be made on each node of the cluster separately. 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.358 Host properties Changing host properties Interpreting the initial settings The dialog boxes use specific conventions regarding multiple host selections. set the box to a gray check. If a dialog box does not contain a Selected Host (or similarly named) combo box. The field may be empty or indicate <<Multiple Entries>> if the property has not been set the same for all selected hosts. Leaving it in that state keeps the hosts untouched. clear the check box. . settings of all the selected hosts are combined to arrive at a value that is displayed to the user. To leave the property unchanged. ■ States of multiple hosts ■ If a dialog box contains a Selected Host (or similarly named) combo box. To clear the property on all selected hosts. a small notice appears at the bottom of the dialog box noting that the value is different on the selected hosts. When the cursor is moved to such a field. all controls on the dialog box reflect the values for the host currently selected in the Selected Host box. 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. Selecting any one from the group updates the setting on all selected hosts.

■ At any time you can choose from the following options: ■ Click Default to set all the fields on the current dialog box to the default values. For example. ■ ■ ■ ■ Selecting multiple hosts You may select more than one host to change properties on multiple hosts at the same time. OK also closes the dialog box. Click Cancel to cancel changes made since the last time changes were applied. . The field changes to gray. or any of the sub-nodes. select the associated check box and type the value in the field. Linux client apricot and Windows 2000 client grapefruit. the corresponding node and sub-node will appear. Multiple hosts of differing operating systems If the selected hosts are of various operating systems. clear the associated check box. Changing the value updates the setting on all selected hosts. Click Apply to save changes to all of the properties for the selected host(s). To make sure that NetBackup uses a changed setting. The changes are applied after clicking OK. none of the operating system-specific information appears.Host properties Changing host properties 359 Number spinner states A number spinner appears blank when multiple hosts are selected. Leaving it blank keeps the setting untouched on the selected hosts. If all the selected hosts are running the same operating systems. Click OK to apply all changes since Apply was last clicked. To leave the property unchanged. restart the application (including the NetBackup Administration Console) to ensure that the new configuration values are used. If the property contains a text field for specifying a value. Click Help for information on the properties that appear on the current dialog box. neither the Windows Client node nor the UNIX Client node will appear in the Host Properties tree. if two clients are selected. choose from the following options: ■ To set the property to the same value for all selected hosts.

or Clients. Hold down the Shift key. . click Actions > Properties. With multiple hosts still selected. then select another host. Select a host. For more information. The Properties dialog box displays the names of the selected hosts that will be affected by subsequent host property changes. see “To add a NetBackup server to a server list” on page 635. Host selection Number of hosts selected Figure 7-2 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.360 Host properties Required permissions To simultaneously change the properties on multiple hosts 1 2 3 Expand NetBackup Management > Host Properties > Master Servers. Media Servers. 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 example.

0 or later and maximum security is required. ■ Required: Select Required if the local system should accept requests only from remote systems using Symantec authentication and authorization. media servers. 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. and client host properties The following sections describe all of the property dialog boxes that can appear for master servers. and all supported clients. Master server. media servers. Consider selecting Automatic if the network contains mixed versions of NetBackup. Consider selecting Required if all systems are at NetBackup 5. and client host properties 361 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. Prohibited: Select Prohibited if the local system should reject connections from any remote system using Symantec authentication and authorization. Consider selecting Prohibited if the network is closed and maximum performance is required. ■ ■ . media server. media server. and clients.Host properties Master server. media servers. Access Control properties The Access Control properties apply to currently selected master servers. For more information. see “Universal Settings properties” on page 478. The description explains whether the dialog box is available on master servers. The dialog boxes are arranged alphabetically. Automatic: Select Automatic if the local system should negotiate with the remote system on whether to use Symantec authentication and authorization. Connections from remote systems not using Symantec authentication and authorization are rejected. or clients.

The names on the list are relevant only if Symantec Product Authentication and Authorization is set to Automatic or Required.362 Host properties Master server. change the Symantec Product Authentication and Authorization property on the master server to Required. Note: Symantec recommends setting the master server Symantec Product Authentication and Authorization property to Automatic until the clients are configured for Access Control. . media server. 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. it uses the networks of its master server. If a media server or client does not define a Symantec authentication and authorization network. Then. and client host properties 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.

0. enter the one of the following: ■ ■ The host name of the remote system.0.Host properties Master server.com) The IP address of the remote system. (10. (10.0. click Add.29) Domain Name/IP If the network is a domain name.) ■ . (host. (. 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. followed by a dot. Host Name/IP If the network is a host.domain) The network of the remote system. media server.0.domain. and client host properties 363 Add button To add a network to the Network list. enter one of the following: ■ A dot followed by the Internet domain name of the remote systems. The Add Network dialog box displays.

10. then click Remove. media server. Authentication Domain tab within the Access Control properties The Authentication Domain tab contains the properties that determines which authentication broker a machine uses.168. select the network name.0 Subnet mask Select Subnet mask to enter a subnet mask in the same the format as the IP address. 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. Prohibited: Select Prohibited if the local system should reject connections from any remote system using Symantec authentication and authorization.168. Connections from remote systems not using Symantec authentication and authorization are rejected.0 or later and maximum security is required.364 Host properties Master server. A master server that uses Symantec authentication and authorization must have at least one authentication domain entry. and client host properties Bit count Select Bit count to indicate that the mask is based on bit count. Attributes of the selected network setting The Symantec Product Authentication and Authorization selection determines whether or not the network uses Symantec authentication and authorization. Consider selecting Prohibited if the network is closed and maximum performance is required.20:255:255:0.20. Select from between 1 and 32. For example: Mask 192. ■ ■ Remove button To delete a network. Consider selecting Required if all systems are at NetBackup 5. . ■ Required: Select Required if the local system should accept requests only from remote systems using Symantec authentication and authorization.10/16 has the same meaning as subnet mask 192.

Add button To add an authentication domain to the domain list. it uses the authentication domains of its master server. media server. and client host properties 365 Figure 7-5 Authentication Domain host properties dialog box If a media server or client does not define an authentication domain. The Add Authentication Domain dialog box displays. click Add. The dialog box contains the following properties: .Host properties Master server.

VXPD: A VxSS Private Database. . version 2. Customize the port number of service Indicate the port number of the authentication broker (optional). WINDOWS: A Windows Active Directory or Primary Domain Controller. Note: If the authentication domain is UNIX . Authentication mechanism Indicate the authentication mechanism: NIS: The Network Information Service. NIS+: The Network Information Service. and client host properties Figure 7-6 Add Authentication Domain dialog box Domain An Internet or Windows domain name.366 Host properties Master server. enter the fully qualified domain name of the host that performs the authentication. media server. PASSWD: The local UNIX password file on the specified broker. Broker The operating system of the broker machine supports the domain type of the authentication service. version 1. Indicate the host name or the IP address of the authentication broker.

then click Remove. The Authorization Service tab does not appear as a property for clients. Host name Enter the host name or IP address of the authorization service. 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. media server. Remove button To delete an authorization domain. and client host properties 367 Description Include a description of the domain (optional). . select the name. Authorization Service tab within the Access Control properties The Authorization Service is the authorization service used by the local NetBackup server.Host properties Master server.

. and client host properties Customize the port number of the authorization service To use a nonstandard port number. media server.368 Host properties Master server. select Customize the port number and enter the port number of the authorization service.

type the name that identifies this user to NetBackup. and client host properties 369 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. The New User or Change User dialog box appears. Figure 7-9 New User dialog box User In the User text box.Host properties Master server. enter a single asterisk: * . To indicate any user. media server. or click Change to change the configuration of an existing authorized user.

media server.370 Host properties Master server. . To indicate all groups. enter a single asterisk: * Group/Domain type Select whether this user is authorized to use NetBackup in a Local group or a Network group. and client host properties Domain\Group In the Domain\Group text box. type the UNIX local group name or the UNIX netgroup name. To indicate all hosts. 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. type the name of the remote NetBackup Administration Console host from which this user can use NetBackup. type the Windows domain or group name in the form domain\group. enter a single asterisk: * Host In the Host text box. Or.

f file paths. 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. The Add a GRFS Mapping dialog box appears.Host properties Master server. Media is read by using a two-phase import process. Add button Click Add to enter a GRFS mapping. the master server must be mapped between the GRFS advertised name (generic file system name) and the actual client name and path. see “Importing images from Backup Exec media” on page 337. The GRFS advertised name uses the following format: ADVERTISED_HOST_NAME/advertised_path . media server. and client host properties 371 Backup Exec Tape Reader properties The Backup Exec Tape Reader properties apply to currently selected master servers. GRFS advertised name To set the correct client name and paths in Backup Exec UNIX images . For more information. that contains the fields that are described in the following sections.

372 Host properties Master server. The ADVERTISED_HOST_NAME should usually be entered in capitals. NetBackup assumes that the advertised path is the same as the real path. NetBackup assumes that the advertised name is the same as the real machine name. A Backup Exec service had mapped the advertised name to the actual machine name and path. then backed up the advertised name and path. Remove button Click Remove to remove the selected GRFS entry. When NetBackup imports Backup Exec UNIX backups. and client host properties where ADVERTISED_HOST_NAME is the advertised host name and advertised_path is the advertised path. media server. Change button Click Change to change the selected GRFS entry. the mapping service is not present. If the host properties do not list any entries. Actual client name The Actual client name maps the advertised name to the real machine name. The advertised name may not have been the same as the real machine name and path. . Actual path The Actual path maps the advertised path to the real path. The GRFS advertised name is the name that the Backup Exec UNIX agent used to identify itself to the Backup Exec server. so the names and paths must be indicated.

The actual limiting occurs on the client side of the backup connection.Host properties Master server. client software calculates the current value for kilobytes per second and adjusts its transfer rate if necessary. and client host properties 373 Bandwidth properties The Bandwidth properties apply to currently selected master servers. the bandwidth is not limited. The bandwidth limits only restrict bandwidth during backups. NetBackup does not include local backups in its calculations. NetBackup dynamically adjusts the bandwidth limits on that subnet. media server. If additional backups . Backups that start later are not considered. By default. 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. How bandwidth limiting works When a backup starts. As the number of active backups increase or decrease on a subnet. Before a buffer is written to the network. 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 NetBackup client software enforces the bandwidth limit.

bandwidth per client is increased if the number of clients decreases. The periodic changes reduce the number of bandwidth value changes that are required.374 Host properties Master server.1. Add button Click the Add button to prepare an entry using the From. Bandwidth throttle setting for the range of IP addresses This area lists the clients in the range of added IP addresses. Bandwidth throttle settings list The bandwidth throttle settings list indicates the clients in the range of IP addresses that were added. An example is 10.1. Similarly. and client host properties are started. 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 entry is added for each of the selected clients. An example is 10.1. A value of 0 disables the limits for an individual client or the range of IP addresses covered by the entry. media server. a value of 200 indicates 200 kilobytes per second. For example. and Bandwidth fields and add it to the bandwidth table. To.9 Bandwidth The Bandwidth field specifies the bandwidth limitation in kilobytes per second. .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. Changes to the bandwidth value occur on a periodic basis rather than as backups stop and start. the NetBackup server instructs the other NetBackup clients that run on that subnet to decrease their bandwidth setting.1.

■ ■ ■ . Bandwidth limits restrict maximum network usage and do not imply required bandwidth.Host properties Master server. media server. For example. It does not mean. if you set the bandwidth limit for a client to 500 kilobytes per second. Notes on bandwidth limits ■ NetBackup does not currently support bandwidth limits on 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). however. and client host properties 375 Figure 7-12 Add Bandwidth Settings dialog box Remove button Click the Remove button to remove a selected entry from the bandwidth table. the client can use up to that limit. NetBackup does not pick the next client to run based on any configured bandwidth limits. You cannot use bandwidth limits to distribute the backup workload of active backups by having NetBackup pick the most available network segment. that the client requires 500 kilobytes per second.

media server. This policy services the backup requests that the repeat option in the actions file generates. NetBackup alphabetically searches (uppercase characters first) for the first available policy with a user backup schedule and an open backup window. The policy name is significant: by default. Configure a policy with a user backup schedule for the busy file backups. 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. 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. ■ . 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.376 Host properties Master server.

Operator’s email address The Operator’s e-mail address property specifies the recipient of the busy-file notification message when the action is set to Send e-mail. or browse to select a file. By default. The metacharacters *.Host properties Master server. Working directory The Working directory property specifies the path to the busy-files working directory. and client host properties 377 For example. . Process busy files Enable Process busy files for NetBackup to process busy files according to the host property settings. By default. By default. On a UNIX client. Enter the file and path directly.conf file takes precedence if it exists. BUSY_FILE_NOTIFY_USER is not in any bp. Enter the file and path directly.] can be used for pattern matching of file names or parts of file names. By default. the mail recipient is the administrator. NetBackup follows the Busy File Settings if it determines that a file is changing during a backup. [ . On a UNIX client. Add to all button Click Add to all to add a new file entry for all of the clients currently selected. []. Process busy files is not enabled and NetBackup does not process the busy files. Add button Click Add to add a new file entry. the value in the user’s $HOME/bp. media server.conf file and the mail recipient is root. ?. File action file list The File action list specifies the absolute path and file name of the busy file.conf file takes precedence if it exists. a policy name of AAA_busy_files is selected ahead of B_policy. the value in the user’s $HOME/bp. NetBackup creates the busy_files directory in the /usr/openv/netbackup directory. or browse to select a file.

378 Host properties Master server. ■ Send e-mail: Directs NetBackup to mail a busy file notification message to the user that is specified in the Operator’s E-mail address field in this dialog box. Busy file action The Busy file action property directs the action that NetBackup performs on busy files when busy-file processing is enabled.conf file takes precedence if it exists. media server. the value in the user’s $HOME/bp. 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. Default retry count: 1. then a log entry that indicates it was busy appears in the All Log Entries report. and client host properties Remove button Select the file or directory and click Remove to remove the file from the file action list. The file is backed up. ■ ■ Retry count The Retry count property specifies the number of times to try the backup. Ignore: Directs NetBackup to exclude the busy file from busy file processing. On a UNIX client.

Keep vault logs The Keep vault logs property is enabled if Vault is installed. NetBackup derives the Backup Status. Figure 7-14 Clean-up host properties dialog box Keep logs The Keep logs property specifies the length of time. if you check the backups every day you can delete the logs sooner than if you check the backups once a month. so do not keep the logs any longer than necessary. Default: 28 days. All Log Entries. job catalog. Problems. However. When this time expires. Specify how many days you’d like to keep the logs in case you need the logs to evaluate failures. the logs can consume a large amount of disk space. For example. that the master server keeps its error catalog. in days. NetBackup also deletes these logs (that exist) on UNIX media servers and UNIX clients. media server.Host properties Master server. and client host properties 379 Clean-up properties Clean-up properties apply to the length of time to retain various logs and incomplete jobs. Keep logs limits the time period that these reports can cover. Session directories are found in the following location: . and specifies the amount of time that the Vault session directories are kept. and Media Log reports from the error catalog. and debug log information.

380 Host properties Master server. NetBackup deletes the additional information from disk again after one day. If a backup session exceeds this maximum interval. If a user requests a true image restore after the information has been deleted from disk. NetBackup retains the information for the number of days this property specifies. To keep the information on disk speeds up restores. and report files. temporary working files. Image cleanup is not run after a successful backup session until this minimum interval has elapsed since the previous image cleanup. NetBackup retrieves the required information from the media. Default: 1 day. and client host properties install_path\netbackup\vault\sessions\vaultname\sidxxxx where xxxx is the session number. an image cleanup is initiated. media server. This applies to all policies for which NetBackup collects true image restore information. The only noticeable difference to the user is a slight increase in total restore time. . Image cleanup is run after every successful backup session (that is. 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. Catalog cleanup wait time The Catalog cleanup wait time property specifies the minimum interval that can elapse before an image cleanup is run. When NetBackup performs a true image backup. the images are pruned (removed). After the specified number of days. This directory contains vault log files. 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 install_path\NetBackup\db\images directory. Image cleanup The Image cleanup property specifies the maximum interval that can elapse before an image cleanup is run. a session in which at least one backup runs successfully).

the Activity Monitor shows the job as Done. and client host properties 381 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. In the Incomplete state. Note: A resumed job reuses the same job ID. If Checkpoint Restart for restores is used. Maximum setting: 72 hours. see “Universal Settings properties” on page 478 and “Checkpoint restart for restore jobs” on page 676. For more information. media server.Host properties Master server. 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 maximum setting is 365 days. Minimum setting: 1 hour. . the Restore retries property allows a failed restore job to be retried automatically. If an Incomplete job does not complete successfully and is moved to the Done state. but a restarted job receives a new job ID. the job retains the error status. After that time. the Activity Monitor shows the job as Done. the job goes into an Incomplete state. The default is 7 days. Default: 3 hours. the administrator may correct the condition that caused the error. When an active job has an error. The job details indicate that the job was resumed or restarted.

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 Deny both for a particular client(s). media server. Client Attributes contains three subtabs: ■ ■ ■ General Tab “Connect Options tab” on page 385 “Windows Open File Backup tab” on page 387 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. and client host properties Client Attributes properties Client Attributes properties apply to clients of currently selected master servers. This attribute is overridden if the Browse and restore ability on the General tab is set to Allow browse only or Deny both.382 Host properties Master server. .

see “Client name” on page 391. the client cannot browse its own backups. see “Windows Open File Backup tab” on page 387. A client must be in the client database before you are able to change the client properties in the Client Attributes dialog box.) and select a client. Type a client name in the text box or click the browse button (.Host properties Master server. For more information about the Windows Open File Backup properties.. To remove a client from the Clients list. The name that is entered here must match the Client Name property for the specific client. Note: Use the bpclient command to add clients to the client database if dynamic addressing (DHCP) is in use. select the client. If it does not.) Add button Click Add to display the Add Client dialog box and add a client to the client database. media server. General tab The following sections describe the properties on the General tab within Client Attributes. The client database consists of directories and files in the following directory: Install_path\NetBackup\db\client If a client is not listed in the Clients list. . then click Remove.. (See “Dynamic host name and IP addressing” on page 45 in the NetBackup Administrator’s Guide. For more information. Figure 7-16 Add Client dialog box Remove button Select a client in the Clients list and click Remove to delete the selected client from the client database. and client host properties 383 Clients list The Clients list is a list of clients in the client database on the currently selected master server(s). Volume II for instructions. click Add to add clients.

the limit is either Maximum jobs per client or Limit jobs per policy. To allow users on the selected clients to browse but not restore. ■ If Maximum data streams is not set. (This value applies to the number of jobs on the client. If Maximum data streams is set. (This setting does not affect user backups and archives. ■ ■ ■ Free browse The Free browse property applies to the privileges that are allowed to a non-Windows administrator that is logged into the client. select Allow browse only. ■ To use the Global client attribute settings. 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 432 and “Limit jobs per policy” on page 103.) To allow users on the selected clients to both browse and restore. select Deny both. media server. select Allow both. (See “Allow client browse” on page 382 and “Allow client restore” on page 382. and client host properties Maximum data streams The Maximum data streams property specifies the maximum number of jobs that are allowed at one time for each selected client.384 Host properties Master server. The Free browse property specifies whether the clients can list and restore from scheduled backups. Select the client(s) in the General tab of the Client Attributes dialog box and choose a Browse and restore ability property. Then scroll to or enter a value up to 99. ■ Browse and restore ability The Browse and restore ability property specifies client permissions to list and restore backups and archives. whichever is lower. select Maximum data streams. This property also applies to the users that do not have backup and restore privileges. NetBackup uses either Maximum data streams or Limit jobs per policy. . NetBackup ignores Maximum jobs per client.) To change the setting. To prevent users on the selected clients from the ability to browse or restore. select Use global settings. whichever is lower. even if multistreaming is not used.) Windows administrators are able to list and restore from scheduled backups as well as user backups regardless of the Free browse setting.

For more information. Reserved port: Use a reserved port number.Host properties Master server. media server. Non-reserved port: Use a non-reserved port number. ■ ■ . For more information. see “Default connect options” on page 420. and client host properties 385 Connect Options tab The properties in the Connect Options tab describe how a NetBackup server connects to NetBackup clients. Random port: NetBackup randomly chooses a free port in the allowed range to perform the legacy connect-back method. ■ ■ Ports ■ Use default connect options: Use the value that is defined in the Firewall host properties of the client’s NetBackup server. VNETD port: NetBackup uses the vnetd port number for the connect-back method. see “Default connect options” on page 420. Figure 7-17 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 client’s NetBackup server.

386 Host properties Master server. media server. Daemon port only: Connect to the daemons on the server using only the legacy port number. check this option. If vnetd only is selected as the Daemon connection port. the connection is made using the daemon’s legacy port number. VNETD only: Connect to the daemons on the server using only vnetd. . For more information. see “Default connect options” on page 420. Non-reserved port is always used regardless of the value of the Ports setting. the BPCD connect back setting is not applicable. If the firewall rules prevent a server connection using the legacy port number. Automatic: Connect to the daemons on the server using vnetd if possible. and client host properties Daemon connection port ■ Use default connect options: Use the value that is defined in the Firewall host properties of the client’s NetBackup server. ■ ■ ■ Note: If vnetd only is selected as the Daemon connection port. If the daemons cannot use vnetd.

By default. Figure 7-18 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. media server.Host properties Master server.0 or later): ■ ■ Windows Open File Backup is enabled on the client. Add and remove buttons Click Add to add NetBackup clients (5. Snapshots are a point-in-time view of a source volume. The properties appear as a tab on the Client Attributes dialog box. no clients are listed and the server uses the following Windows Open File Backup defaults for all Windows NetBackup clients (5. . NetBackup uses snapshots to access busy or active files during a backup job.0 or later) only if you want to change the Windows Open File Backup defaults. active files are not accessible for backup. The snapshot provider for the client is VSP. The properties also specify whether Volume Snapshot Provider or Volume Shadow Copy Service is used as the snapshot provider. and client host properties 387 Windows Open File Backup tab Windows Open File Backup properties apply to selected Windows master servers. Without a snapshot provider.

To make changes to the default settings. (The tab is found under Host Properties > Clients > Selected client(s) > Windows Client > VSP). For more information. then click Delete.0 or later. see “VSP (Volume Snapshot Provider) properties” on page 486. 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. VSP is configured for each client using the VSP tab for the client.) 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. select the client. and you do not want snapshots. 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 . then make changes to the client’s 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. see the NetBackup Snapshot Client Administrator’s Guide. For more information. Upon error. If a client is included in a policy that has the Perform Snapshot backups policy option disabled. (Default: Windows Open File Backup is enabled for all Windows NetBackup clients. ■ To delete a client from the list. media server. By default. VSP can be used for Windows NT/2000/XP/Server 2003 clients.388 Host properties Master server. If both options are not disabled. Select the client name in the client list. a snapshot is created. the snapshot is aborted (Abort backup on error).0 or later) use VSP as the Windows Open File Backup snapshot provider. and client host properties ■ Snapshots are taken of individual drives (Individual drive snapshot) as opposed to all drives at once (Global drive snapshot). all NetBackup clients (5. 5. add the client name to the client list. The default is VSP. though that may not be the intention of the administrator. the Enable Windows Open File Backups for this client property must be disabled as well for the client.

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. NetBackup backs up C. 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. . NetBackup performs the following actions for the backup job: 1 2 NetBackup takes a snapshot of drive C. This mode is useful when relationships do not have to be maintained between files on the different drives. and client host properties 389 selected clients. depending on which drive is to be backed up. backs it up. All the volumes that require snapshots for the backup job (or stream group for multi-streamed backups) are taken at one time. Configure VSS through the Microsoft’s VSS configuration dialog boxes. snapshot creation and file backup is done sequentially on a per volume basis. NetBackup discards the C and D snapshots. VSS can be used for Windows Server 2003 clients only. For example.) Individual drive snapshot is enabled by default for all non multi-streamed backups using the Windows Open File Backup option. (For example. In this situation.Host properties Master server. then backs up D. NetBackup performs the following actions: 1 2 3 NetBackup takes a snapshot of C and D. If Individual drive snapshot is selected. if one volume in the volume set cannot meet the VSP quiet time requirements. media server. Global drive snapshot The Global drive snapshot property specifies that the snapshot is of a global drive. assume that drives C and D are to be backed up. and discards the snapshot. For example. Volume snapshots are enabled on only one drive at a time. backs it up. NetBackup takes a snapshot of drive D. When this property is enabled. Individual drive snapshot The Individual drive snapshot property specifies that the snapshot should be of an individual drive (default). and discards the snapshot. assume that drives C and D are to be backed up.

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. The volume snapshots are taken in a global fashion. If Abort on error is checked (default). Regarding the file that had a problem during a backup—it may be that the file was not backed up by the backup job. The most common reason for a problem after the snapshot has been created and is in use by a backup. media server. Disable snapshot and continue The Disable snapshot and continue property specifies that if the snapshot becomes invalid during a backup. Reconfigure the cache storage configuration of the Windows Open File Backup snapshot provider to a configuration that best suits your client’s installation. 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. The backup continues with Windows open file backups disabled. All multi-streamed backup jobs share the same volumes snapshots for the volumes in the multi-streamed policy. 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 backup job continues regardless of whether a snapshot was successfully created for the backup job. the volume snapshots for the backup are destroyed. Note: Volume snapshots typically become invalid during the course of a backup because insufficient cache storage was allocated for the volume snapshot. . The file may not be able to be restored.390 Host properties Master server. This property does not apply to successful snapshot creation. the backup job aborts with a snapshot error status if the backup detects a snapshot issue. is the cache storage having filled to capacity.

The only exception is for a redirected restore. The client name is initially set during installation. media server. . The name that is entered here must also match the client name in the Client Attributes dialog box for the master server. The value in the $HOME/bp. The name can also be added to a $HOME/bp. the name is normally added in this manner only for redirected restores. The Client name is the name by which the client is known to NetBackup. the client cannot browse for its own backups.conf file takes precedence if it exists. where the name must match that of the client whose files are to be restored. The name must match the name the policy uses to back up the client.Host properties Master server. NetBackup uses the name that is set in the following locations: ■ ■ For a Windows client: In the Network application from the Control Panel. However. see “Client Attributes properties” on page 382. and client host properties 391 Client Name properties The Client Name properties apply to a single. For more information. If the value is not specified. If it does not.conf file on a UNIX client. Figure 7-19 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. currently selected client. For a UNIX client: The name that is set by using the hostname command.

media server. The metadata is the information still in the primary storage that marks where the file would be. and client host properties Client Settings (NetWare) properties The Client Settings properties apply to currently selected NetWare clients. Metadata includes any information that is needed to retrieve the file from secondary storage. Keep status of user-directed backups. and restores property specifies how long the system keeps progress reports before it automatically deletes the reports. If the property is not selected.392 Host properties Master server. . Uncompression is useful if the file is restored to a version of NetWare that does not support compression. archives. the file is backed up in its compressed state. archives. 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 option is not selected (default). only the metadata for the file is backed up and the file is not moved back to primary storage. Uncompress files before backing up The Uncompress files before backing up property specifies that compressed files are uncompressed before backing up. Default: 3 days. and restores The Keep status of user-directed backups.

Minimum: 0. and client host properties 393 Client Settings (UNIX) properties The UNIX Client Settings apply to currently selected UNIX clients. Skip: NetBackup skips the files that currently have mandatory locking set by another process.Host properties Master server. . archives. Maximum: 9. the backup fails with a status 41. see “Client read timeout” on page 476.999 days. and restores property specifies the number of days to keep progress reports before deleting them. If the wait exceeds the Client read timeout host property. A message is logged if it was necessary to skip a file. ■ Wait: By default. ■ Keep status of user-directed backups. archives. For more information. Figure 7-20 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. NetBackup waits for files to become unlocked. Default: 3 days. media server. configured on the master server. and restores The Keep status of user-directed backups.

This feature is supported on all platforms and versions where VxFS file systems support FCL: ■ ■ ■ Solaris SPARC platform running VxFS 4. Default: 0. the client software uses this value to determine how much space to request for the compression tables. 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. HP 11. Note: This setting affects the software and the administration scripts that examine a file’s access time. An updated atime makes it appear as if the files are frequently used and prevents Storage Migrator from selecting the files for migration. 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.394 Host properties Master server. The more memory that is available to compress code. Setting these options causes the atime for files to be updated every time they are backed up. .1 or greater AIX running VxFS 5.23 running VxFS 5. use a maximum value of 1/2 the actual physical memory on a machine to avoid excessive swapping. If other processes also need memory. If you select compression. NetBackup preserves the access time by resetting it to the value it had before the backup. Megabytes of memory to use for file compression Note: This option has a reasonable default and should be changed only if problems are encountered.0 or greater. By default. 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. the greater the compression and the greater the percentage of machine resources that are used. media server. DO NOT use this option or USE_CTIME_FOR_INCREMENTALS if you are running Storage Migrator on the system.0 or greater.

If a file experiences many changes.1 or greater Default: off. or multiple changes to many files. see “Backup Selections tab” on page 167. holes punched. For more information. See the Veritas File System Administrator’s Guide for information about how to enable the FCL on the VxFS client.Host properties Master server. The Use VxFS file change log property must be enabled on the client(s) in time for the first full backup. ■ ■ . The FCL must be enabled on the VxFS client. 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. and client host properties 395 ■ Linux running VxFS 4. Subsequent incremental backups need this full backup to stay synchronized. files renamed. the FCL offset. data that is truncated. extended attribute modifications. Changes may include files created. enable this property for a client on a very large file system that experiences relatively few changes. and the time stamp for each backup. data that is overwritten. media server. The FCL information that is stored on each client includes the backup type. links and unlinks. and file property updates. 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 time saving benefit may not be as great. 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 File Change Log (FCL) tracks changes to files and directories in a file system. data that is appended. For example. The performance impact of incremental backups ranges from many times faster or slower. Note: The VxFS mount point must be specified in the policy backup selections list for this property to take effect. depending on file system size and use patterns. NetBackup can use the FCL to determine which files to select for incremental backups. which can potentially save unnecessary file system processing time.

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. 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. The partition must exist on all the clients that are included in the policy. To keep the data files synchronized with the FCL. By specifying a directory at a higher level than the VxFS mount point. Note: If any errors are encountered while processing the FCL. 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. VxFS administration Additional VxFS commands are available to administrate the FCL. If this switch occurs. the Use VxFS file change log property on the client is ignored. . The commands are documented in the Veritas File System Administrator’s Guide.396 Host properties Master server. do not turn the FCL on the VxFS client off and on. see “Cross mount points” on page 109. Keeping the data files synchronized with the FCL The data files must be in sync with the FCL for this property to work. it is displayed in the Activity Monitor. Note: If the policy has Collect true image restore information or Collect true image restore information with move detection enabled. This raw partition is used when either nbu_snap or VxFS_Snapshot are selected as the snapshot method. For more information. provided that Cross mount points is enabled. By specifying the actual VxFS mount point. For additional information. see the NetBackup Snapshot Client Administrator’s Guide. NetBackup switches to the normal files system scan.

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

Scroll to one of the following available log levels: 0 No extra logging (default). and nbwin. TCP level logging The TCP level logging property enables logs for TCP. 1 Log basic TCP/IP functions. Figure 7-21 Client Settings (Windows) host properties dialog box General level logging The General level logging property enables logs for bpinetd. The higher the level. It can also slow a backup or restore operation. 2 Log all TCP/IP functions.398 Host properties Master server. tar. the more information is written. Default: 0. media server. and client host properties Client Settings (Windows) properties The Windows Client properties apply to currently selected Windows clients. . Note: Setting the TCP level to 2 or 3 can cause the status reports to be very large. 3 Log contents of each read or write buffer. including all read and write requests. bpbkar.

000). By enabling the Use change journal in incrementals check box. 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. the volume is a good candidate for enabling NetBackup change journal support. 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: ■ . media server. When this property is enabled. NetBackup can provide faster incremental backups for NTFS 5 (and later) volumes that store large numbers—possibly millions—of files. The Microsoft change journal is a disk file that records and retains the most recent changes to an NTFS volume. Default: Not enabled. This option applies only to differential-incremental backups. and client host properties 399 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.000. The client waits for acknowledgment from the server that the backup was successful. Use change journal in incrementals is available only when a valid tracker database exists on the applicable volumes. 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.Host properties Master server. The minimum allowable value is 300 (default). By monitoring the change journal. 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. the Incrementals are based on timestamp property is automatically enabled. Therefore. Suitable candidates for enabling NetBackup change journal support: ■ If the NTFS volume contains more than 1. This information is used to shorten the discovery process that NetBackup performs during an incremental backup by making a file system scan unnecessary. NetBackup can determine which file system objects have changed and when. the archive bits are not cleared. If the server does not reply within this time period. Cumulative-incremental backups do not clear the archive bit.000 files and folders and the number of changed objects between incremental backups is few (less than 100.

the volume is not a good candidate for enabling NetBackup change journal support. Volume II. see “Synthetic backup” on page 134. After Use change journal in incrementals is selected. see “Checkpoint restart for restore jobs” on page 676. Change journal support is not offered for user-directed backups. it has no effect while using the following options or products: ■ ■ ■ ■ ■ True Image Restore (TIR) For more information. Be aware that virus scanning software can interfere with the use of the change journal. and client host properties relatively few files and folders. ■ If the total number of changes on a volume exceeds from 10 to 20% of the total objects. Support for change journal is not offered with several NetBackup options or Symantec products. True Image Restore with Move Detection For more information. ■ ■ ■ . The USN stamps for full and incremental backups in the permanent record do not change. Synthetic backups For more information. scan for viruses. (For example. media server. see “Collect true image restore information” on page 114. then reset the access time. see “Collect true image restore information with move detection” on page 115. hundreds of thousands of files and folders. A full backup of the target system must be completed under change journal monitoring to enable change journal-based incremental backups. NetBackup support for change journal works with Checkpoint Restart for restores. For more information. Some real-time virus scanners intercept a file open for read. ■ Guidelines for enabling NetBackup change journal support ■ A NetBackup client using change journal support must belong to only one policy. Multiple backup settings can cause conflicted update sequence number (USN) information in the permanent record. the NetBackup client service must be restarted on the target system. Intelligent Disaster Recovery (IDR) For more information. To use one policy avoids the confusion that multiple backup settings causes. This results in the creation of a change journal entry for every scanned file. If Use change journal in incrementals is enabled.400 Host properties Master server. see the NetBackup Administrator’s Guide.) The normal file system scan is suitable under such conditions.

then the new files are not backed up until the next full backup. see “Wait time before clearing archive bit” on page 399. 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). .Host properties Master server. 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 cumulative-incremental backup. media server. 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. Incrementals based on timestamp is automatically selected. A differential-incremental backup clears the archive bit if the file is successfully backed up. For a differential-incremental backup. Default: 60 minutes. A cumulative-incremental or user backup has no effect on the archive bit. and client host properties 401 ■ Bare Metal Restore (BMR) For more information. A full backup always clears the archive bit. NetBackup compares the datetime stamp to the last full or incremental backup. For more information. 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. NetBackup compares the timestamp to the last full backup. The system sets this bit whenever a file is changed and it normally remains set until NetBackup clears it. 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. If you install or copy files from another computer. If the original date is before the last backup date on this computer. see the NetBackup Bare Metal Restore Administrator’s Guide. The differential-incremental backup must occur within the number of seconds that the Wait time before clearing archive bits property indicates. This value compensates for differences in the speed of the clock between the NetBackup client and server. the new files retain the date timestamp of the originals.

For example. The backed up folders and files within the range are displayed whenever a restore window is opened. 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. and restores property specifies how many days the system keeps progress reports before NetBackup automatically deletes them. if the archive bits cannot be reset on a file. Default: 3 days. For example. 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. With the property disabled. . archives. The operation fails if it does not begin within this time period. This property has no minimum value or maximum value. Default: 10. Perform default search for restore The Perform default search for restore property instructs NetBackup to search the default range of backup images automatically. this property limits how many times the message appears in the server logs. media server. Default: 16 kilobytes. 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. and restores The Keep status of user-directed backups. Clear the Perform default search for restore check box to disable the initial search. Default: 60 seconds. Default: option is enabled.402 Host properties Master server. with no maximum allowable value. the NetBackup Restore window does not display any files or folders upon opening. archives. and client host properties This value is used during incremental backups when using the archive bit and when examining the create time on folders. specify 10 for a buffer size of 10 kilobytes. The minimum allowable value is 2. Keep status of user-directed backups. This comparison is done for archive bit-based backups as well as date-based backups.

However. select a line and click Move Down. To increase the rank of a data classification. To create a new data classification. description. select a line and click Move Up. For more information. . see “Storage Lifecycle Policies” on page 249. click New. and client host properties 403 Data Classification properties Data classifications must be configured before Storage Lifecycle Policies can be configured. To decrease the rank of a data classification. New data classifications are added to bottom of the list.Host properties Master server. the name. Figure 7-22 Data Classification host properties dialog box Note: Data classifications cannot be deleted. Use the Move Up and Move Down buttons to change rank and move the classification up or down in the list. The classification ID remains the same. and the rank can be changed. The New dialog displays. Rank The order of the data classifications determines the rank of the classification in relationship to the others in the list. media server. The lowest numbered rank has the highest priority.

and rank can change without changing the identity of the data classification. Modify the name and description in the Change Data Classification dialog box. For more information. A new classification appears at the bottom of the list. see “Data classification” on page 96. click New. so data classifications cannot be deleted. 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. select a line and click Change. 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. The name. To create or change a data classification ■ To create a new data classification. The storage lifecycles use the ID to identify the images that are associated with classification.404 Host properties Master server. ■ . Description Enter a meaningful description for the data classification. Descriptions can be modified. Add a name and description in the New Data Classification dialog box. A data classification becomes associated with a backup image by setting the Data Classification attribute in the policy dialog. Use the Move Up and Move Down buttons to move the classification level up or down in the list. Modify the name and description in the Change dialog box. ID values may exist in image headers indefinitely. The ID is written into the image header. To change an item. media server. description.

the backup job ends due to error. select one of the following options: ■ Not allowed: Specifies that the client does not permit encrypted backups. For more specific information on the Encryption option. and client host properties 405 Encryption properties The Encryption properties control encryption on the currently selected client. media server. If the server requests an encrypted backup. the Encryption properties dialog box is hidden. . Encryption permissions The Encryption permissions property indicates the encryption setting on the selected NetBackup client as determined by the master server.Host properties Master server. If it is necessary to change this property. see the NetBackup Security and Encryption Guide. Figure 7-23 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 separately-priced NetBackup Encryption option must be installed on the client for these settings (other than Allowed) to take effect.

Enable standard encryption is automatically selected. Use legacy DES encryption is automatically selected. DES_40 is the default value for a client that has not been configured for encryption. ■ Enable encryption Select the Enable encryption property if the NetBackup Encryption option is used on the selected client. AES-256-CFB. ■ . Client cipher The following cipher types are available: BF-CFB. If the server requests an unencrypted backup. If the selected client is running a version of NetBackup earlier than 5. Required: Specifies that the client requires encrypted backups. and AES-128-CFB.1. DES-EDE-CFB. AES-128-CFB is the default. 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 runs NetBackup 5. Allowed is the default setting for a client that has not been configured for encryption. Enable standard encryption The Enable standard encryption property pertains to the 128-bit and the 256-bit options of NetBackup Encryption. 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_56: Specifies the 56-bit DES encryption. the backup job ends due to error.406 Host properties Master server. More information on the ciphers file is found in the NetBackup Security and Encryption Guide. media server. and client host properties ■ Allowed: Specifies that the client allows either encrypted or unencrypted backups.1 and does not use Legacy encryption.

specify the new name. Encryption key file The Encryption key file property specifies the file that contains the encryption keys on NetBackup clients. The default setting is generally sufficient. specify the new name.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. and client host properties 407 Encryption libraries The Encryption libraries property specifies the folder that contains the encryption libraries on NetBackup clients. 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. The following is the default location: ■ On Windows systems: install_path\NetBackup\bin\keyfile. media server. .Host properties Master server. On UNIX systems: /usr/openv/lib ■ If it is necessary to change the setting.

The NetBackup Client service account must have granted logon rights to the mailbox. use any existing mailbox on the Microsoft Exchange Server. Specify the number of . Create a unique mailbox name for the NetBackup Client service account. If a mailbox is not created for the NetBackup Client service. 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. Figure 7-24 Exchange host properties dialog box The Exchange properties specify the mailbox to associate with the NetBackup Client Service account. see the NetBackup for Microsoft Exchange Server Administrator’s Guide. and client host properties Exchange properties The Exchange properties apply to currently selected Windows clients.408 Host properties Master server. Adjust the inputs and outputs rate of the verification by adjusting the value of the Snapshot verification I/O throttle option. For more information on the mailbox settings. Specify a mailbox only if the NetBackup client and NetBackup Microsoft Exchange Server agent software are installed on the Microsoft Exchange Server. Snapshot verification I/O throttle NetBackup runs the checksum integrity verification after a snapshot is complete. media server.

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. ■ Mailbox for message level backup and restore Specifies the mailbox for the NetBackup Client service account. SIS allows the database to keep one copy of a message attachment that is sent to multiple users on the same server. 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.) The only log files that are backed up are those from the most current full backup.) The value is used during snapshot validation by the Exchange command ESEUTIL /pXXX where XXX is the value of Snapshot verification I/O throttle. (Applicable to Exchange 2003 SP2 or later. 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. This property controls which log files are backed up during the backup of an Exchange database: ■ Back up only uncommitted log files (Default. Logs can be backed up in either a full or a user-directed type backup. See the Microsoft Exchange documentation regarding the ESEUTIL command for details. With this property selected for backups. To perform SIS backups. Back up all log files (including committed log files) All log files are backed up. With this property selected. . check Enable single instance backup for message attachments on the client where Exchange server is installed. users are unable to roll forward from previous backups through the most current. and client host properties 409 inputs and outputs to process for each second-long pause.Host properties Master server. users are able to roll through previous full backups. media server.

and the directories to be excluded from automatic backups.) NetWare NonTarget clients do not support exclude lists. Use case sensitive exclude list The Use case sensitive exclude list property indicates that the files and directories to exclude are case sensitive. (For more information. specify the exclude list when the targets are added. An exclude list names policies. schedules.410 Host properties Master server. media server. Volume I. Figure 7-25 Exclude Lists host properties dialog box Note: Exclude Lists properties apply only to Windows clients. . and client host properties Exclude Lists properties Use the Exclude Lists properties to create and to modify the exclude lists for Windows clients. files. On NetWare target clients. Exclude list The Exclude list displays the policies that contain schedule. file. To create an exclude list for UNIX clients. and directory exclusions. see Chapter 3 in the NetBackup Administrator’s Guide for UNIX. see the NetBackup user’s guide for the client.

From the exceptions list Click Add to create an exception to the Exclude list. and client host properties 411 Exceptions to the exclude list The Exceptions to the exclude list displays policies. schedules. 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. the items on the exceptions list are backed up. and the directories that are excepted from the Exclude list. media server. The exception is configured in the Add exceptions to exclude list dialog box. you add files back into the backup list of a policy. files. The list is useful to exclude all files in a directory but one. Effectively. the files and directories on the list are backed up. When the policies on the Exceptions to the exclude list run. 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. then added to the Exceptions to the exclude list.Host properties Master server. Add buttons The Add button performs different functions. the files and directories that are specified on the list are backed up. The exclusion is configured in the Add to exclude list dialog box. then added to the Exclude list. . When the policies on the Exceptions to the exclude list run. Figure 7-26 Add to Exclude List dialog box When the policies on the Exclude list run.

and client host properties ■ a list item is selected that has not been configured on the selected hosts. From the exclude list Click Add to All to add the selected list item to all currently selected clients. depending on whether it is used from the Exclude list or from the Exceptions to the exclude list. The item is excluded from the backup. From the exclude list Click Remove to remove the selected policy. The item is included in the backup. The item is excluded from the backup list on all selected clients. When the policies on the exclude list run. To exclude or make exceptions for . a grayed-out list item is selected. depending on whether it is used from the Exclude list or from the Exceptions to the exclude list. You can also select the schedule name from the drop-down menu. 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 schedule name that is associated with the files and the directories to exclude or make exceptions for.) Add to All performs different functions. Schedule In the Schedule field. 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. the items on the exceptions list are backed up on all selected clients.412 Host properties Master server. media server. or file from the Exclude list. To exclude or make exceptions for the backup of specific files or directories from all policies. Remove buttons Remove performs different functions. enter the policy name that contains the files and the directories to exclude or make exceptions for. or file from the Exceptions list. select <All Policies>. (Rather. From the exceptions list Click Remove to remove the selected policy. schedule. schedule. You can also select the policy name from the drop-down menu.

expand NetBackup Management > Host Properties > Clients. Select All Policies to exclude these items from all policies. To add an entry to the exclude list: a b Under the Exclude List. The Add Exceptions to the Exclude List dialog box appears. select <All Schedules>. select a policy name from the drop-down menu or enter the name of a policy.Host properties Master server. click Add. c d e 3 To add an exception to the exclude list: a b Under the Exceptions to the Exclude List. Select All Schedules to add these items back into the schedules. select a schedule name from the drop-down menu or enter the name of a schedule. select a policy name from the drop-down menu or enter the name of a policy. In the Policy field. Click Add to add the specified files and directories to the exclude list.) In the Schedule field. enter the full path to the file(s) and the directories to exclude or make exceptions for. In the Policy field. c . 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. Double-click on a client. In the Schedule field. In the Files/Directories field. click Add. Select All Policies to add these items back into all policies. The Add to Exclude List dialog box appears. (In other words. media server. Files/Directories 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. 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. these items are to be excluded from the exclude list. and client host properties 413 the backups of specific files or directories from all schedules.

if the directories are not mounted at the time of a backup. For example. and client host properties d In the Files/Directories field. NetBackup uses only the most specific one. e 4 Click Apply to accept the changes. Click Add to add the specified files and directories to the Exceptions to the Exclude List. enter the files or directories to be added back into the backups that are based on the selected policy and schedule. ■ .414 Host properties Master server. Click OK to accept the changes and close the host properties dialog box. NetBackup must wait for a timeout before proceeding. 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. An exclude list for the entire client. An exclude list for a policy. assume a client has three exclude lists: ■ ■ ■ An exclude list for a policy and schedule. This list does not specify a policy or schedule. The following syntax rules apply to exclude lists: ■ ■ Only one pattern per line is allowed. Syntax rules for exclude lists Note: Symantec suggests that you always specify automounted directories and CD-ROM file systems in the exclude list. Otherwise. Do not include extra spaces unless they are part of the file name. Spaces are considered legal characters. NetBackup uses the first exclude list (for policy and schedule) because it is the most specific. as described in “NetBackup naming conventions” on page 629. NetBackup recognizes standard wildcard use. For example. media server. In this example. Which list is used if there is more than one? If there is more than one exclude or include list for a client.

For example. The file is still backed up in this case because the actual directory path. The directory C:\users\doe\abc\ (because the exclude entry ends with \). The following syntax rules apply only to UNIX clients: ■ Do not use patterns with links in the names. For example: test rather than C:\test This is equivalent to prefixing the file pattern with \ \*\ \*\*\ \*\*\*\ ■ and so on. C:\users\test\). /usr/home/doc. enter the name. regardless of their directory path. To exclude all files with a given name. C:\users\test). 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. ■ 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. assume /home is a link to /usr/home and /home/doc is in the exclude list. media server. /home/doc. If the pattern does not end in \ (for example. does not match the exclude list entry. ■ ■ ■ .Host properties Master server. All files or directories named core at any level and on any drive. NetBackup excludes both files and directories with that path name. the following files and directories are excluded from automatic backups: ■ ■ The file or directory named C:\users\doe\john. Blank lines or lines that begin with a pound sign (#) are ignored. and client host properties 415 ■ End a file path with \ to exclude only directories with that path name (for example.

media server. while the client uses an include list to override the exclude list. since the include list on Windows client silk includes the following file: C:\WINNT the excluded directories are traversed to back up C:\WINNT. When a scheduled backup runs. . to satisfy the client’s include list. Assume the following settings for a Windows client named silk: ■ The backup policy backup selection list for silk indicates ALL_LOCAL_DRIVES.416 Host properties Master server. the entire client is backed up. NetBackup traverses the excluded directories if necessary. The entire client would also be backed up if the backup selection list 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. and client host properties Traversing excluded directories An exclude list may indicate a directory for exclusion.

media server. NetBackup replaces the backup selection list with the client’s include list. . 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. In another example. no directories would be traversed.Host properties Master server. and client host properties 417 If the include list did not contain any entry.

also specify the wait period for backups and for restores. If an FT device is not available after the wait period elapses. The Fibre Transport media server property applies to the SAN clients for selected media servers. The defaults for clients are the property settings of the master server. If you select this option. The Fibre Transport client properties apply to the selected SAN clients.418 Host properties Master server. Figure 7-27 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. media server. For more information about NetBackup Fibre Transport. see the NetBackup Shared Storage Guide. NetBackup uses a LAN connection for the operation. 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. 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.

The Use defaults from the master server configuration property specifies to use the properties that are configured on the master server. The default is four times the number of HBA target ports (maximum of 16). Always The Always property specifies that NetBackup should always use an FT pipe always for backups and restores of SAN clients. an FT device must be active and available. Fibre Transport is disabled for the client.Host properties Master server. If you specify Never for a SAN client. Fibre Transport is disabled in the NetBackup environment. and client host properties 419 For the global property that is specified on the master server. However. Use defaults from the master server configuration Client property only. or the SAN Client license expired. media server. An FT device may not exist because none is active. Maximum concurrent FT connections Media server property only. . NetBackup uses the LAN. If you select Never. none have been configured. If no FT device exists. the default is Preferred. you can configure FT usage on a per-client basis. The Maximum concurrent FT connections property specifies the number of FT connections to allow to a media server. NetBackup uses a LAN connection for the backups and restores. Never The Never property specifies that NetBackup should never use an FT pipe for backups and restores of SAN clients. Fibre Transport is disabled for the media server. NetBackup waits until an FT device is available before it begins the operation. If you specify Never for the master server. If you specify Never for a 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. However. . (See “Client Attributes properties” on page 382.420 Host properties Master server. NetBackup selects firewall-friendly connect options under Default connect options. the default options can be set differently for individual servers under Attributes for selected Hosts. Servers are added to the host list of the Firewall properties. Default connect options By default. To configure port usage for clients.) Figure 7-28 Firewall host properties dialog box By default. media server. the firewall settings are configured to require the fewest possible ports to be open. see the Client Attributes properties.

click Change. also enable Accept connection on non reserved Ports for the selected server. ■ 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. The server initiates all bpcd socket connections. The situation does not pose a firewall problem because bpbrm uses the well-known bpcd port. This property is located on the Universal Settings dialog box under Host Properties > Master Server or Host Properties > Media Servers. media server. The Veritas Network Daemon (vnetd) was designed to enhance firewall efficiency with NetBackup during server-to-server and server-to-client communications. 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. see “Accept connections on non reserved ports” on page 481. For more information. and client host properties 421 Figure 7-29 Default Connect Options dialog box To change any of the Default connect options. . Take the example of when bpbrm on a media server initially connects with bpcd on a client. If this property is selected. Use non reserved ports: Connect to the server by a non-reserved port number.Host properties Master server.

Add button Click Add.422 Host properties Master server. Use non reserved ports is always used regardless of the value of the Ports setting. A host must be listed before it can be selected for configuration.) Remove button Select a host name in the list.. the daemon’s traditional port number makes the connection. Select this property if your firewall rules prevent connections to the server by the traditional port number. the BPCD connect back setting is not applicable. Hosts list To change the default connect options for any server.. . then click Remove to remove the host from the list. (That is. to add a host entry to the host list. click Change. Note: If vnetd only is selected as the Daemon connection port.) VNETD Only The daemons on the server are connected to by vnetd only. add the server to the host list. If vnetd only is selected as the Daemon connection port. 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. (Automatic is the default. Servers do not automatically appear on the list. media server. the hosts that are selected upon opening Host Properties. If it is not possible to use vnetd. Daemon port only The daemons on the server are connected to by only the traditional port number. 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. ■ ■ To change the default connect options for the selected server.

) VNETD only ■ ■ . ■ ■ 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. the daemon’s traditional port number makes the connection.Host properties Master server. The situation does not pose a firewall problem because bpbrm uses the well-known bpcd port. see “Accept connections on non reserved ports” on page 481. The Veritas Network Daemon (vnetd) was designed to enhance firewall efficiency with NetBackup during server-to-server and server-to-client communications. (Use default connect options is the default for BPCD connect back. If this property is selected. (Automatic is the default. VNETD port: This method requires no connect-back.) Reserved port: Connect to the server by a reserved port number.) Automatic The daemons on the server are connected to by vnetd if possible. ■ ■ 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. Take the example of when bpbrm on a media server initially connects with bpcd on a client. (Use default is the default. For more information.) Random port: NetBackup randomly chooses a free port in the allowed range to perform the traditional connect-back method. The server initiates all bpcd socket connections. also enable Accept connection on non reserved ports for the selected server. media server. (Use default is the default. If it is not possible to use vnetd. Non reserved port: Connect to the server by a non-reserved port number. 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. and client host properties 423 Attributes for selected hosts Connect options can be configured for individual servers.

Note: If vnetd only is selected as the Daemon connection port.424 Host properties Master server. Under BPCD connect back. and client host properties The daemons on the server are connected to by vnetd only. the BPCD connect back setting is not applicable. that is located in \Install_path\VERITAS\NetBackup\bin\admincmd. If vnetd only is selected as the Daemon connection port. In the host list. Click OK. media server. expand NetBackup Management > Host Properties > Master Servers > Double-click on master server > Client Attributes. select VNETD port. Under BPCD connect back.5 or later installed for vnetd to work. add the client to the client database by running the bpclient. 2 3 4 To enable logging for vnetd Create a vnetd directory in the following location: On Windows: install_path\NetBackup\logs\vnetd . Non reserved port is always used regardless of the value of the Ports setting. select the client you want to change.exe command. Click OK. In the client list. 2 3 4 Or. To set up vnetd between a server and a client 1 In the NetBackup Administration Console. select the host you want to change. Note: Both servers and clients must have NetBackup version 4. 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. ■ Daemon port only The daemons on the server are connected to by the traditional port number only. Select this property if your firewall rules prevent connections to the server by the traditional port number. select VNETD port.

Choose Automatic for the Daemon connection port. select VNETD port. add an entry for each remote server. select VNETD port. and client host properties 425 On UNIX: /usr/openv/logs/vnetd Or. A vnetd connection is tried first when selected. The example uses the Use connect back bpcd connections: Change in the configuration file setup: Add the following configuration option to the vm.) Under BPCD connect back. Choose Automatic for the Daemon connection port. (Host Properties > Master Servers > Selected master server > Client Attributes. add an entry for the Master server. 2 = Traditional connections (default) Change in the host properties: ■ In the Firewall properties for the master server. a traditional connection is tried.) Under BPCD connect back. z is 0 for automatic connections. (Host Properties > Media Servers > Selected media server > Firewall. add an entry for each remote client.) Choose Automatic for the Daemon connection port.conf. media server.bat in the install_path\NetBackup\logs\ directory to populate the logs directory with log subdirectories. and the robotic daemons on master and media servers. (Host Properties > Master Servers > Selected master server > Firewall.) ■ ■ ■ . bpdbm. add an entry in the host list for each remote media server. Example setup for using the vnetd port The following is a sample configuration to use the vnetd port for bprd. If that fails. (Host Properties > Clients > Selected client > Firewall.conf. 1 = vnetd-only connections.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. including one for vnetd. In the Firewall properties for each media server. In the Client Attributes properties for the Master server. bpvmd. y is 0 or 1 and is ignored for vm. double-click mklogdir. In the Firewall properties for each Client. bpjobd.Host properties Master server.

. media server. and client host properties Under BPCD connect back. select VNETD port.426 Host properties Master server.

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. Figure 7-30 General Server host properties dialog box Delay on multiplexed restores The Delay on multiplexed restores property applies to multiplexed restores. media server. All of the restore requests are received within the delay period are included in the same restore operation (one pass of the tape). If the frequency is not often enough.0 media servers only. checks are made more often than necessary and system resources are wasted. Default: delay of 30 seconds. Note: This property applies to the disk storage units of 6. Default: 300 seconds (5 minutes). and client host properties 427 General Server properties The General Server properties apply to selected master and media servers. too much time elapses and backup jobs are delayed. It specifies how long the server waits for additional restore requests of multiplexed images on the same tape.Host properties Master server. If the frequency is too often. Subsequent releases use internal methods to monitor disk space more frequently. .

a local drive is used for backups. If all drives are down.428 Host properties Master server. Then. another may be used. but applies to all media servers as well. . Clear the Direct access recovery for NDMP restores check box to disable DAR on all NDMP restores. Automatically duplicate images from tape to disk To duplicate the images from tape to a disk storage unit. This property does not apply to NDMP drives. enable this option. the media server clients may be mixed with other clients in a policy that uses ANY AVAILABLE storage unit. or . If the client is also a media server or a master server and Must use local drive is checked. see “Retention” on page 144. and client host properties Must use local drive This property appears for master servers only. Note: To perform document-level restores. even if only a single restore file is needed. Without DAR. For example. 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. Only the data that is needed for those files is read.doc. select a disk storage unit to contain the duplicated images. the backups go to the SAN connected drives on that server. This property increases performance because backups are done locally rather than sent across the network. When a backup starts for a client that is a SAN media server. . Use direct access recovery for NDMP restores By default.5 clients. the MS-SharePoint policy that backs up the images must have the Enable document restore Policy attribute enabled. Click the Configure button to configure images to be duplicated from a tape to a disk storage unit. Select a retention level for the duplicated images on the disk storage unit. For more information. Document-level restore options The Document-level restore options concern the use of SharePoint 2003 to restore specific files. For more information. DAR allows the NDMP host to position the tape to the exact location of the requested file(s).pdf. From the Destination disk storage unit drop-down menu.txt files on NetBackup 6. NetBackup reads the entire backup image. (For example.xls.) Document-level restores can be performed only if the backup was written to a disk storage unit. media server. . . in a SAN environment a storage unit can be created for each SAN media server. see “Enable document restore” on page 121.

if files were backed up on media server A. . A media server was removed from the NetBackup configuration. 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. Restore server: Server that is to process future restore requests. Change button To change an entry in the Media host override list. select a host name. The Add Media Override Settings dialog box contains the following fields: Figure 7-31 Add Media Override settings dialog box ■ ■ Original backup server: Server where data was backed up originally. ■ Add button Click Add to add a host to the Media host override list. A restore is requested while one of the servers is either temporarily unavailable or is busy doing backups. and client host properties 429 Media host override Specific servers can be specified in the Media host override list as servers to perform restores.Host properties Master server. and is no longer available. media server. then click Change. 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. (Both servers must be in the same master and media server cluster.) For example. regardless of where the files were backed up.

media server. To revert to the original configuration for future restores. Modify the NetBackup configuration on the master server. physically move the media to the host to answer the restore requests. 2 3 . Stop and restart the NetBackup Request Manager service on the master server. Restores for any storage unit on the Original backup server go to the server that is listed as the Restore server. Add the original backup media server and the restore server to the Media host override list in the General Server host properties. This process applies to all storage units on the original backup server. then update the Enterprise Media Manager database to reflect the move. 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. delete the line from the Media host override list.430 Host properties Master server. To force restores to go to a specific server 1 If necessary.

Schedule backup attempts Note: This attribute does not apply to user backups and archives. Schedule backup attempts allows you to limit the number of tries if a client or drive is down or media is unavailable. media server. If the backup window closes before the retry starts. . Default: 2 tries in 12 hours. the job fails with a status code 196. Default: 10 minutes. The Schedule backup attempts property specifies the number of times that NetBackup tries to complete a scheduled backup job during the specified time period. The default values are adequate for most installations but can be changed. and client host properties 431 Global Attributes properties The Global Attributes properties apply to currently selected master servers. minimum: 1 minute. The Global Attributes properties affect all operations for all policies and clients. Figure 7-32 Global Attributes host properties dialog box Job retry delay The Job retry delay property specifies how often NetBackup retries a job. Maximum: 60 minutes.Host properties Master server.

minimum: 1 minute. NetBackup can perform concurrent backups to separate storage units or to drives within a storage unit.432 Host properties Master server. Default: 1 job. For example. or. 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. Maximum: 1440 minutes. The higher the value. NetBackup can process concurrent backup jobs from different policies on the same client only if: ■ ■ More than one storage unit available. the more priority restore jobs have. /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. one of the available storage units can perform more than one backup at a time. 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. Default: 10 minutes. media server. Default: 99999. can be backed up concurrently to different storage devices. 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. Maximum jobs per client Client Figure 7-33 Files that are on the same client but in different policies. a single Media Manager storage unit supports as many concurrent backups as . Note: Multiplexed backup jobs are unaffected by the restore priority setting. The interval allows the NetBackup administrator time to make multiple changes to the policy.

The best setting depends on the hardware. however. A disk storage unit is a directory on disk so the maximum number of jobs depends on system capabilities. Too many concurrent backups on an individual client interfere with the performance of the client. Depending on other factors.Host properties Master server. . Network loading is not a factor because the network is not used. is still a factor.) Use the Limit jobs per policy policy setting in a client-specific policy. Two exabyte 8500. and client host properties 433 it has drives. consider backups over multiple networks or compression. A special case exists to backup a client that is also a server. ■ ■ Network loading. NetBackup creates one of the following. operating system. see “Multiple copies” on page 137. or the number of copies that are specified as the Maximum backup copies property. whichever is smaller: ■ ■ the number of copies that are specified under Multiple copies. set the Maximum jobs per client value to greater than two. Note: If online. To accommodate weaker clients (ones that can handle only a small number of jobs concurrently). The Maximum jobs per client property applies to all clients in all policies. Client and server loading. the load might be too much for a single Ethernet. consider using one of the following approaches: ■ Set the Maximum data streams property for those weaker client(s) appropriately. and applications that are running. The available bandwidth of the network affects how many backups can occur concurrently. media server. 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). For more information about how to create multiple copies. hot catalog backups are scheduled to occur concurrently with other backups for the master server. For loading problems. (A client-specific policy is one in which all clients share this characteristic). (This property is found under Host Properties > Master Server > Client Attributes > General tab. ■ Server and client speed. 8mm tape drives can create up to a 900-kilobyte-per-second network load.

Administrator email address The Administrator email address property specifies the address(es) where NetBackup sends notifications of scheduled backups or administrator-directed manual backups. and client host properties Note: When configuring multiple copies for a relocation schedule. hot catalog backups is not sent to the addresses indicated here. .com. its status is shown as Active in the Activity Monitor.com Note: Disaster recovery information that is created during online. DR information is sent to the address indicated on the Disaster Recovery tab in the catalog backup policy. the Maximum Backup Copies property must be set to five or more. media server. The notification of offline. Compress catalog interval The Compress catalog interval property specifies how long NetBackup waits after a backup before it compresses the image catalog file. the more system resources are used. separate multiple email addresses using a comma: useraccount1@company. If the active vault jobs limit is reached. For example. cold catalog backups includes the media ID that was used. For more information. the computing environment must be configured correctly. see “Disaster Recovery tab” on page 193. If a duplication job or eject job waits. 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. Setting up email notifications Before notification emails are sent.useraccount2@company. subsequent vault jobs are queued and their status is shown as Queued in the Activity Monitor. The greater the maximum number of vault jobs. to create four copies in the Multiple Copies dialog. Maximum vault The Maximum vault property specifies the maximum number of vault jobs that are allowed to be active on the master server.434 Host properties Master server. To send the information to more than one administrator.

Locate the following lines in the script: @IF "%~4"=="" ( blat %3 -s %2 -t %1 -i NetBackup -server WARTHOG -q ) ELSE ( blat %3 -s %2 -t %1 -i NetBackup -server WARTHOG -q -attach %4 ) 3 Adjust the fives lines specified in step 2: .cmd script be configured. Note: In some text editors.) ■ Both methods require that the NBMAIL.Host properties Master server.) Windows systems require that an application to transfer messages using the Simple Mail Transfer Protocol be installed in order to accept script parameters.cmd script Locate install_path\VERITAS\NetBackup\bin\nbmail.) Both methods require that the host properties be configured with email addresses. and client host properties 435 NetBackup can send notification to specified email addresses about backups on all client or specific clients.cmd script” on page 435. (See “Configuring the nbmail. UNIX platforms have a SMTP transfer method built into the system.cmd does not send email. 1 Use a text editor to open nbmail. 2 @REM @REM @REM @REM @REM Most of the lines in nbmail.cmd on a NetBackup master server. copy nbmail.) Send emails about successful and failed backups: Send a message to the local administrator(s) of each client about successful and unsuccessful backups. Choose one or both of the following notification methods: ■ Send emails about failed backups only: Send a message to the email address(es) of the NetBackup administrator(s) about any backup that ends in a non-zero status. By default.) Configuring the nbmail. using the word wrap option can create extra line feeds in the script and render it non-functional.cmd. media server.cmd are informational. If configuring the script on the client. (Client sends mail host property is enabled in Universal Settings. Create a backup copy of nbmail. (Server sends mail host property is enabled in Universal Settings.cmd from a master server to the client. nbmail.cmd before modifying it. (See “Installing the email utility” on page 147. (See “Indicating email notification in the NetBackup host properties” on page 437.

. media server.company. and client host properties ■ Remove @REM from each of the five lines shown above.com -q -attach %4 ) ■ Save nbmail. The default (–i NetBackup) shows that the email is from NetBackup.436 Host properties Master server.company. Suppresses all output to the screen. Nbmail.company. Copy the blat.cmd. Replace WARTHOG with the name of the email server. The name of the SMTP server that is configured to accept and relay emails.ZIP file from the BLAT download page (currently www.company. To install and configure the email utility 1 2 3 4 Download the . though it is not necessarily known to the email server. From a command prompt.com is the hostname or IP address of the email server that will send the email notifications.exe file to the Windows System32 directory.com -q ) ELSE ( blat %3 -s %2 -t %1 -i NetBackup -server emailserver.cmd options Description The subject line of the email Indicates who will receive the email. BLAT is used as an example in the following discussions. Table 7-1 Option -s -t -i -server -q Installing the email utility The most common application used for email notification is BLAT. a public domain mail client. This activates the sections needed for BLAT to run.blat.com is the primary account to send the emails from the specified server.com Where: emailserver. useraccount@company. The originator of the email. Extract the files to a directory. run the following command: blat -install emailserver.com useraccount@company. For example: ■ @IF "%~4"=="" ( blat %3 -s %2 -t %1 -i NetBackup -server emailserver.net).

Open the properties of the master server. In the Client administrator’s email field.txt -s test_subject -to useraccount@company. and client host properties 437 To test the blat installation 1 2 Create a test text file that contains a message.Host properties Master server. Expand NetBackup Management > Host Properties > Master Server.txt to the email address specified. Enable the Server sends mail option and click Apply. Select Universal Settings. To send messages only about backups with a non-zero status 1 2 3 4 5 6 7 Install and configure a mail client on the server as described in “Installing the email utility” on page 147. If both methods are configured.cmd script” on page 435. Edit the nbmail. Expand NetBackup Management > Host Properties > Master Server.com A correct setup sends the contents of testfile.) See “Client administrator’s email” on page 482. enter the email address of the administrator to receive the notification emails.cmd script on the server as described “Configuring the nbmail. Open the NetBackup Administration Console on the master server. 8 To send messages to the global administrator about backups with a non-zero status 1 2 3 4 Install and configure a mail client on the server as described in “Installing the email utility” on page 147. run: blat C:\testfile. Open the NetBackup Administration Console on the master server.txt From a command prompt. the NetBackup global administrator receives emails about any failures and the NetBackup client administrator(s) receives emails about the clients where the client administrator’s email address is specified. create C:\testfile. Edit the nbmail. (Separate multiple addresses with commas. media server. Indicating email notification in the NetBackup host properties Both methods work independently. For example. .cmd script” on page 435.cmd script on the server as described “Configuring the nbmail.

cmd script” on page 435. Multiple clients can also be selected. (Separate multiple addresses with commas. In the Client administrator’s email field. An email can be sent to each client administrator after both successful and failed backups. enter the email address of the administrator to receive the notification emails. Open the NetBackup Administration Console on the master server. In the Administrator’s email address field. Select Global Attributes.) Click Apply. 8 Email contents The following represents the contents of a notification email: Backup on client hostname by root was partially successful. The global administrator’s 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 name@company.) See “Client administrator’s email” on page 482. File list --------C:\Documents and Settings . media server.438 Host properties Master server. Enable the Client sends mail option and click Apply.com 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. and client host properties 5 6 7 Open the host properties of the master server. Open the host properties for a client. enter the email address of the administrator to receive the notification emails. 1 2 3 4 5 6 7 Install and configure a mail client on the client as described in “Installing the email utility” on page 147. Expand NetBackup Management > Host Properties > Clients. Select Universal Settings. (Separate multiple addresses with commas.cmd script on the server as described “Configuring the nbmail. Edit the nbmail.

■ ■ ■ ■ ■ ■ ■ . Download the latest version.cmd script. make sure that the account used for the NetBackup client process is authorized. Make sure that the path to blat. Configure the email addresses are correctly in the host properties. ■ Make sure that the BLAT command is not commented out in the nbmail. For more information. media server.) The BLAT binary must not be corrupt or incompatible with the email system. Make sure that BLAT syntax has not changed in the later versions of BLAT. If the email server requires authentication for SMTP. and client host properties 439 Troubleshooting the notification Use the following list to troubleshoot problems if NetBackup notification is not working correctly. The email account specified must be a valid on the email server.exe is specified in nbmail. see “Installing the email utility” on page 147. The default account is the local system. Check the README for the version of blat running on the system. (n represents seconds.Host properties Master server.cmd if the command is not in the \system32 directory. The BLAT command may need the -ti n timeout parameter if the system experiences delays.

The unified logs are written to /usr/openv/logs (UNIX) and to install_path\NetBackup\logs (Windows). The logging method for unified logging differs from the logging method for the processes that use legacy logging. log file names and messages are created in a format that is standardized across all Symantec products. No subdirectories are necessary for the processes that use unified logging. and clients. Figure 7-34 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. media server. . and clients. The available properties differ between master servers. and client host properties Logging properties The Logging properties apply to currently selected master servers. media servers. Introducing unified logging In unified logging.440 Host properties Master server. Some NetBackup processes on the server use unified logging. media servers.

bpdbm. media server. bptm. bpbrm. See the NetBackup Troubleshooting Guide for more information about controlling the log file size. use the vxlogcfg and the vxlogmgr commands.99999 If Enable robust logging is disabled: A single log file is produced each day: MMDDYY. To control the size and number of unified logs. a new log file is opened. If the new log file causes the maximum number of log files in the directory to be exceeded. Once the log file is closed. Enable robust logging A check in the Enable robust logging checkbox indicates that when a log file grows to the maximum size. as described in the NetBackup Troubleshooting Guide.Host properties Master server.bat in the following directory: install_path\NetBackup\logs\ Create the Media Manager legacy log directories in: ■ ■ /usr/openv/volmgr/debug (UNIX) install_path\Volmgr\debug (Windows) For more information about legacy logs. . bpbkar. A logging level selection on the Logging properties page does not enable logging. you must first create a log directory for each process to be logged. and client host properties 441 For details on both unified and legacy logging. bpcd. the log file is pruned using KEEP_LOGS_DAYS and DAYS_TO_KEEP_LOGS settings. refer to the “Using Logs and Reports” chapter of the NetBackup Troubleshooting Guide. you can create all of the NetBackup debug log directories at one time by double-clicking mklogdir. and bpdm are named using the following convention: MMDDYY_NNNNN. Legacy logging For those processes that use legacy logging. see the NetBackup Troubleshooting Guide. Create the NetBackup legacy log directories in: ■ ■ /usr/openv/netbackup/logs/process_name (UNIX) install_path\NetBackup\logs\process_name (Windows) On a Windows server. If Enable robust logging is enabled: The log files for bprd. the oldest log file is deleted.log Whether Robust Logging is selected or not.log where NNNNN is an incrementing counter from 00001 . the log file is closed.

All services require that you first create a log directory in: install_path\NetBackup\logs\process_name BPBRM logging level If you want to override the Global logging level. and client host properties Note: If a NetBackup environment uses scripts depending on the MMDDYY. media server. select a logging level for bprd: 0 (minimum) through 5 (maximum). . BPDM logging level If you want to override the Global logging level. Process specific overrides The following services use legacy logging. Other settings can cause the logs to accumulate large amounts of information. BPRD logging level If you want to override the Global logging level. select a logging level for bptm: 0 (minimum) through 5 (maximum). Six levels are supported. specify a different logging level other than the Global logging level. Caution: Use the default setting of 0 unless advised otherwise by Symantec Technical Support. either update the scripts or disable Robust Logging. select a logging level for bpbrm: 0 (minimum) through 5 (maximum). the logging levels control the amount of information that the NetBackup server writes to logs.log naming convention. Some NetBackup processes allow individual control over the amount of information the process writes to logs. A value of 0 sets logging to minimum (default) and a value of 5 sets it to maximum.442 Host properties Master server. For those processes. BPTM logging level If you want to override the Global logging level. Global logging level The Global logging level property is used for debugging purposes. select a logging level for bpdm: 0 (minimum) through 5 (maximum).

select a logging level for bpvault: 0 (minimum) through 5 (maximum). Select No logging to produce no log for this service at all.0. The Job Manager accepts the jobs that the Policy Execution Manager (NBPEM. select a logging level for the Job Manager (NBJM. The Policy Execution Manager compiles a worklist for jobs and determines when jobs are due to run.exe): 0 (minimum) through 5 (maximum). This property appears for EMM servers. This property does not appears for NetBackup hosts earlier than 6. select a logging level for bpdbm: 0 (minimum) through 5 (maximum).exe): 0 (minimum) through 5 (maximum).exe): 0 (minimum) through 5 (maximum). select a logging level for the Policy Execution Manager (NBPEM. Vault logging level If you want to override the Global logging level. This property does not appear for NetBackup hosts earlier than 6. and client host properties 443 BPDBM logging level If you want to override the Global logging level. Select No logging to produce no log for this service at all. media server. This property does not appear for NetBackup hosts earlier than 6. tape drives. Policy Execution Manager If you want to override the Global logging level. use the vxlogcfg command. The Resource Broker makes the allocations for storage units.exe) submits and acquires the necessary resources. client reservations. This property appears for EMM servers. Debug logging levels for NetBackup services The Logging properties page offers configurable debug levels for the services that use unified logging. Please refer to the NetBackup Troubleshooting Guide for more information. select a logging level for the Resource Broker (NBRB. Select No logging to produce no log for this service at all. Job Manager If you want to override the Global logging level.0.0.Host properties Master server. The following sections describe the services that use unified logging. Resource Broker If you want to override the Global logging level. . Each service creates a log automatically in: install_path\NetBackup\logs To change the debug levels.

444 Host properties Master server. media server. and client host properties .

media server. For more information. NetBackup must know where these files are to perform backup and restore operations. Figure 7-35 Lotus Notes host properties dialog box The following topics explain the settings.INI file for non-partitioned servers is not necessary.INI file to back up and restore from Domino partitioned servers. INI file In the INI field.Host properties Master server.INI file. . specify the absolute path to the NOTES. Use this setting to specify the correct . The value in this box overrides the Lotus registry key.INI file that is associated with the server used to back up and restore the Lotus database. and client host properties 445 Lotus Notes properties The Lotus Notes properties apply to currently selected clients running NetBackup for Lotus Notes. see the NetBackup for Lotus Notes Administrator’s Guide. specify the path where the Lotus Notes program files reside on the client. Path In the Path field. if both are defined. Enter the NOTES. Specifying the .

) CPIO: When CPIO is enabled. DBR media can be overwritten.446 Host properties Master server. (Data General AOS/VS backup format. NetBackup does not overwrite certain media types. place a check in the check box of one or more of the listed media formats. Figure 7-36 Media host properties dialog box Allow media overwrite The Allow media overwrite property overrides NetBackup’s overwrite protection for specific media types.) ■ ■ . To disable overwrite protection. DBR: When DBR is enabled. CPIO media can be overwritten. and client host properties Media properties The Media properties apply to selected master servers and media servers. Media properties control how NetBackup manages media. AOS/VS: When AOS/VS is enabled. For example. ANSI labeled media can be overwritten. AOS/VS media can be overwritten. The following media formats on removable media can be selected to be overwritten: ■ ■ ANSI: When ANSI is enabled. place a check in the CPIO check box to permit NetBackup to overwrite the cpio format. (The DBR backup format is no longer used. media server. Normally.

the backup is aborted and an error is logged. This format recognition requires that the first variable length block on a media be less than or equal to 32 kilobytes.Host properties Master server. If the volume is mounted to restore files or list the media contents. media server. The error indicates that the volume does not have a NetBackup format. The error indicates the volume cannot be overwritten. . ■ ■ ■ By default. other host bus adaptors cannot issue commands to control the drives during the reservation. and client host properties 447 ■ RS-MTF1: Remote Storage MTF1 media format. When MTF1 is enabled. (The exception is Backup Exec MTF (BE-MTF1) and Remote Storage MTF (RS-MTF1) media formats. MTF media can be overwritten. NetBackup does not overwrite any of the formats on removable media. Backup Exec MTF media can be overwritten. TAR media can be overwritten. NetBackup takes the following actions: ■ If the volume has not been previously assigned for a backup ■ ■ ■ Sets the volume’s 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 volume’s state to SUSPENDED Aborts the requested backup Logs an error ■ If the volume is mounted for a backup of the NetBackup catalog. TAR: When TAR is enabled. With access protection. all other MTF formats can be overwritten. Remote Storage MTF1 media format can be overwritten. which are not overwritten. ■ Enable SCSI reserve The Enable SCSI reserve property allows exclusive access protection for tape drives. and logs an error if an overwrite attempt occurs. BE-MTF1: When BE-MTF1 is enabled. If media contains one of the protected formats and media overwrites are not permitted. NetBackup aborts the request and logs an error. With only MTF checked. MTF: When MTF is enabled.

If the hardware does not process SCSI persistent reserve commands correctly and NetBackup is configured to use SCSI persistent reserve.) . Caution: Ensure that all of your hardware processes SCSI persistent reserve commands correctly. media server. SPC-2 SCSI reserve is effective for most NetBackup environments. You can override the media server setting for any drive path from that media server. NetBackup can recover and use a reserved drive after a failover (if NetBackup owns the reservation).3. SCSI persistent reserve is valid for NetBackup 6.) This option provides SPC-2 SCSI reserve protection for SCSI devices. No protection. Alternatively. ■ ■ The protection setting configures access protection for all tape drives from the media server on which the option is configured. NetBackup does not send persistent reserve commands to NetBackup media servers earlier than release 6. If unchecked. The devices must conform to the reserve and release management method in the SCSI Primary Commands . The devices must conform to the SCSI Primary Commands . For more information. All of your hardware includes fibre-channel bridges. no protection may exist. NetBackup has used SPC-2 SCSI reserve since NetBackup 3. (The default option. 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. 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.5. To operate NetBackup without tape drive access protection.5 and later servers only. other HBAs can send the commands that may cause a loss of data to tape drives. The following are the protection options: ■ SCSI persistent reserve.448 Host properties Master server. If you enable SCSI persistent reserve.3 (SPC-3) standard. clear the Enable SCSI reserve property.4. see “Configuring SCSI reserve on a drive path” on page 606. and it is the default tape drive reservation method in NetBackup. This option provides SCSI persistent reserve protection for SCSI devices. Recommended use All tape drive and bridge vendors support the SPC-2 SCSI reserve and release method. usually you must reset the drive because the reservation owner is inoperative. (With SPC-2 SCSI reserve. SPC-2 SCSI reserve.2 standard.

you must ensure that your operating system does not issue SPC-2 reserve and release commands. It applies to media in both robotic drives and nonrobotic drives. Therefore. and client host properties 449 ■ You want very high drive availability. the check box is clear and each volume can contain backups of only a single retention level. ■ ■ ■ If any of your hardware does not support SCSI persistent reserve. Allow backups to span tape media The Allow backups to span tape media property. if you use parallel SCSI buses in your environment. 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. NetBackup can resolve NetBackup drive reservation conflicts and maintain high drive availability. if your tape drives do not support SPC-3 Compatible Reservation Handling (CRH). Also. For example. SCSI persistent reserve is not supported or not supported correctly by all fibre channel bridge vendors. parallel drives are not shared. The resulting backup has data fragments on more than one volume. if you use bridges in your environment.) However. you should not use SCSI persistent reserve. This property allows NetBackup to select another volume to begin the next fragment. . so SCSI persistent reserve protection is not required. You may have to configure your operating system tape drivers extensively to use SCSI persistent reserve.Host properties Master server. allows backups to span to multiple tape media. By default. parallel drives are usually on a bridge. Incorrect support in a bridge means no access protection. media server. Usually. (SPC-2 SCSI reserve provides no method for drive status detection. Allow multiple retentions per media The Allow multiple retentions per media setting allows NetBackup to mix retention levels on tape volumes. the SCSI persistent reserve method is not supported or not supported correctly by all device vendors. By default. and bridges do not support SCSI persistent reserve correctly. you should not use SCSI persistent reserve. you should thoroughly analyze your environment to ensure that all of your hardware supports SCSI persistent reserve correctly. when checked. If you have parallel SCSI buses. you should carefully consider the use of SCSI persistent reserve. Allow backups to span tape media is checked and backups are allowed to span media. Therefore. Symantec recommends that you do not use SCSI persistent reserve. Therefore.

stand-alone drive extensions are enabled. By default. Also. The multiplexing level on spanning storage units should be the same. a disk staging storage unit is not eligible as a target for disk spanning. For more information on the storage unit multiplexing setting. see “Enable multiplexing” on page 226 A disk staging storage unit cannot span to another storage unit. media server. An OpenStorage. Enable job logging Check the Enable job logging property to allow the logging of the job information that the NetBackup Activity Monitor uses. The units must be within a storage unit group. ■ ■ 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. and client host properties If the end of media is encountered and this property is not selected. this property is enabled. job logging occurs. Allow backups to span disk The Allow backups to span disk property allows backups to span disk volumes when one disk volume becomes full. This action applies to both robotic drives and nonrobotic drives. ■ Notes on disk spanning For disk spanning to occur. the media is set to FULL and the operation terminates abnormally. Disk spanning is not supported on NFS. or SharedDisk volume spanning to another volume in the disk pool. the following conditions must be met: ■ ■ The storage units must share the same media server. AdvancedDisk. Enable unrestricted media sharing for all media servers The Enable unrestricted media sharing for all media servers property controls media sharing. If there are any differences. The following destinations support disk spanning: ■ A BasicDisk storage unit spanning to a BasicDisk storage unit. By default.450 Host properties Master server. as follows: . the level on the target unit can be higher.

For example. such as those running NetBackup for Oracle. and so on. A00001. A configurable delay is useful if a gravity feed stacker is used on a nonrobotic drive. Media unmount delay applies only to user operations. Media request delay The Media request delay property specifies how long NetBackup waits for media in nonrobotic drives. media server.) For more information. The delay can range from 0 seconds to 1800 seconds. if FEB is specified. FEB001. (Default: 180 seconds. ■ ■ By default. The prefix must be one to three alpha-numeric characters.Host properties Master server. (Note that this numbering does not work with the Configure Volumes wizard). Otherwise. If the drive is ready. NetBackup uses A and assigns media IDs such as A00000. During the delay period. clear this property. The assigned media IDs become FEB000. (The property is cleared and no server groups are configured. To disable media sharing. and client host properties 451 ■ To allow all NetBackup media servers and NDMP hosts in your NetBackup environment to share media for writing. media sharing is disabled. to include backups and restores of database agent clients. Media unmount delay To specify a Media unmount delay property indicates that the unloading of media is delayed after the requested operation is complete. clear this property and do not configure media server groups.) If you specify 0. NetBackup checks every 60 seconds to see if the drive is ready. To restrict media sharing to specific server groups. Values greater than 1800 are set to 1800. The delay reduces unnecessary media unmounts and the positioning of media in cases where the media is requested again a short time later. see “Configuring server groups for media sharing” on page 614. Default: 0 seconds. Do not configure server groups for media sharing. NetBackup uses it. and so on. By default. NetBackup appends the remaining numeric characters. NetBackup waits . NetBackup appends numeric characters. A delay often exists between the dismount of one media and the mounting of another. the media unmount occurs immediately upon completion of the requested operation. 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. then configure media server groups and backup policies to use media sharing. select this property.

and client host properties another 60 seconds and checks again. at the end of 50 seconds. If the delay is less than 60 seconds. NetBackup checks only once at the end of the delay. If the total delay is not a multiple of 60. However. Use global NDMP credentials for this NDMP host must be selected in the Add NDMP Host dialog for the NDMP host. the last wait is the remainder. NetBackup waits 60 seconds. add a NDMP host under Media and Device Management > Credentials > NDMP Hosts. waits 60 seconds. checks for ready. set the delay to 150 seconds. NDMP Global Credentials properties The credentials that are entered for NDMP Global Credentials can apply to any NDMP host in the configuration. checks for ready. .452 Host properties Master server. NetBackup would have checked only once. If the delay had been 50 seconds (a short delay is not recommended). Figure 7-37 NDMP Global Credentials host properties dialog box To access the Add NDMP Host dialog. For example. then waits 30 seconds and checks for ready the last time. media server.

NetWare Client properties The Netware Client properties define NetBackup properties of NetWare clients. Password and confirm password Enter and re-enter the password. Netware Client properties include: ■ ■ “Client Settings (NetWare) properties” on page 392 “Open File Backup (NetWare client) properties” on page 455 . and client host properties 453 Figure 7-38 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. media server. This user must have permission to run NDMP commands.Host properties Master server.

Default: 13782. Note: If you change this port number. 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. Figure 7-39 Network host properties dialog box Under Network properties. and client host properties Network properties The Network properties apply to currently selected Windows clients. set the properties that define requirements for communications between clients and the master server. remember that it must be the same for all NetBackup servers and clients that communicate with one another. NetBackup client service port (BPCD) The NetBackup client service port (BPCD) property applies to Microsoft Windows clients.454 Host properties Master server. The property specifies the port that the NetBackup client uses to communicate with the NetBackup server. Note: If you change this port number. . NetBackup request service port (BPRD) The NetBackup request service port (BPRD) property applies to Microsoft Windows clients. remember that it must be the same for all NetBackup servers and clients that communicate with one another. media server.

media server.Host properties Master 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. 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. The announcement occurs only if the specified time period has elapsed and the address has changed since the last time the client announced it.

which accept connections from daemons on other servers that share the same library. Dynamically-allocated ports are assigned as needed. See the services file on the media server to determine the ports that are required for a specific library. and client host properties Port Ranges properties The Port Ranges properties apply to selected master servers. media server. and clients. Figure 7-40 Port Ranges host properties dialog box NetBackup communicates between computers by using a combination of registered and dynamically allocated ports.456 Host properties Master server. media servers. from configurable ranges in the Port Ranges host properties for NetBackup servers and clients. These ports are specified in a system configuration file: %systemroot%\system32\drivers\etc\services Media Manager services include tape library control daemons. In addition to the range of numbers. you can configure the following for dynamically-allocated ports: ■ . the port for the NetBackup client service (bpcd) is 13782. ■ Registered ports are registered with the Internet Assigned Numbers Authority (IANA) and are permanently assigned to specific NetBackup services. For example.

By default. (See Allow non reserved ports on the Universal Settings dialog box. 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. ■ Use random port assignments The Use random port assignments property specifies how NetBackup communicates with NetBackup on other computers. media server.) Default range: 512 through 1023. Whether connections to bpcd on a client use reserved or non-reserved ports. enable Use OS selected non reserved port. Use random port assignments is selected. port 4999 is chosen. NetBackup chooses numbers sequentially. 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. If this property is not selected. if the range is from 1023 through 5000. This setting applies when connecting to NetBackup on a computer that is configured to accept only reserved ports.) To let the operating system determine the non-reserved port to use. NetBackup starts with the highest number that is available in the allowed range. To let the operating system determine the non-reserved port to use. For example. (See Allow non reserved ports on the Universal Settings dialog box. For example. This property specifies that NetBackup randomly chooses a port from those that are free in the allowed range. enable Use OS selected non reserved port. This setting applies when connecting to NetBackup on a computer that is configured to accept non-reserved ports. if the range is from 1023 through 5000. NetBackup chooses 5000 (if port 5000 is free). 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. it chooses randomly from the numbers in this range.Host properties Master server. . If 5000 is in use. and ports are randomly chosen.

Default range: 1024 through 5000.) Server reserved port window does not appear in a client configuration. This setting applies when connecting to a client configured to accept only non-reserved ports. Default range: 512 through 1023. 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. enable Use OS selected non reserved port. enable Use OS selected non reserved port. (See Allow non reserved ports on the Universal Settings dialog box. (See Accept connections on non reserved ports on the Universal Settings dialog box. . media server.) Server port window does not appear in a client configuration. This setting applies when connecting to a client configured to accept only reserved ports. 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.458 Host properties Master server. To let the operating system determine the non-reserved port to use. To let the operating system determine the non-reserved port to use.

(For example.) . one of the servers is temporarily inaccessible. The automatic failover does not require administrator intervention. and client host properties 459 Restore Failover properties The Restore Failover properties apply to selected master servers. media server. A failover server may be necessary if the regular media server is temporarily inaccessible for a restore.Host properties Master server. 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. Possible reasons for the failure are: ■ ■ The media server is down. When a restore is requested. By default. Figure 7-41 Restore Failover host properties dialog box The Restore Failover properties control how NetBackup performs automatic failover to a NetBackup media server. ■ In these instances. Examples of when to use the restore failover capability: ■ Two or more media servers share a robot and each has connected drives. inaccessible means that the connection between bprd on the master server and bptm on the media server (through bpcd) fails. if the connection is refused or access is denied. The media server is up but bpcd does not respond. NetBackup does not perform automatic failover.

Click Add to add the name to the list.460 Host properties Master server. if vmd is down or bptm cannot find the required tape. click Change. To change an entry. In the Failover restore servers field. Separate the names of multiple servers with a single space. The Add Failover Servers dialog box appears. 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. To add or change a media server to the alternate restore failover machine list 1 To add an entry. 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. Click OK to close the host properties dialog box.) Alternate restore failover machines list The Media server column displays the NetBackup media servers that have failover protection for restores. The Change Failover Servers dialog box appears. and client host properties ■ The media server is up and bpcd is running but bptm has problems. specify the media server for failover protection. click Add. 2 3 In the Media server field. The dialog box remains open for another entry. specify the media server(s) to try if the server that is designated in the Server field is unavailable. media server. Click Apply to accept the Restore Failover property changes. Click Close to close the dialog box. 4 5 . The Failover restore server column displays the servers that provide the failover protection. (For example. Click OK if an entry was changed.

Media server Browse to a media server for which to configure a failover restore server(s). Separate multiple server names with a single space. and client host properties 461 6 Stop and restart the NetBackup Request daemon on the master server where the configuration was changed. see “Method 3: Automatic failover to alternate server” on page 684. select the media server to be removed. select a media server. Failover restore servers Browse to another media server to serve as the failover server. Change button To change an entry in the Alternate restore failover machines list. . media server. For more information on failover. then click Change.Host properties Master server. Remove button To remove a NetBackup media server from the Alternate restore failover machines list. then click Remove.

Retention periods list The dialog box contains a listing of the current definitions for the 25 possible levels of retention (0 through 24). The list also includes the special unit. Value The Value specifies the retention level setting. Figure 7-42 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. media server. Select from 25 levels of retention. The Schedule count column indicates how .The Retention period in a policy determines how long NetBackup retains the backups or archives created according to that schedule. and client host properties Retention Periods properties The Retention Periods properties apply to selected master servers.462 Host properties Master server. Units The Units property specifies the units of time for the retention period. Infinite. The Retention Period properties define the length of time that is associated with each level.

If the retention period is changed for a level. To discard your changes. weeks. Note: After Units or Value is changed. 2 Note: Level 9 cannot be changed and remains at a setting of infinite. The policy impact list displays the schedules where the new retention period is less than the frequency period. It also lists the policy to which each schedule belongs.Host properties Master server. 5 Click Impact Report. an asterisk (*) appears in the Changes Pending column to indicate that the period was changed. The list displays all schedules in which the retention period is shorter than the frequency period. years. Select the units of measure (days. The policy impact list now displays the names of all schedules that use the selected retention level. 6 . months. Select the retention level that you want to change. To change a retention period 1 In the NetBackup Administration Console. it affects all schedules that use that level. NetBackup does not change the actual configuration until Apply or OK is clicked. or expires immediately). and the policy to which each schedule belongs. Schedules list The dialog box contains a list of the schedules that use the currently selected retention level. To prevent schedules from being listed. media server. and client host properties 463 many schedules currently use each level. redefine the retention period for the schedules or change the retention or frequency for the schedule. Impact report button Click Impact Report to display a summary of how changes affect existing schedules. expand NetBackup Management > Host Properties > Master Server > Double-click on master server > Retention Periods. click Cancel. infinite. 3 4 Type the new retention period in the Value box.

To suspend the volumes. click OK. ■ 8 To save the changes. click one of the following: ■ Apply: Saves the changes and leaves the dialog box open to make further changes. However. That is. suspend the volumes that were previously used for that retention level. before a major change is made to a retention period. Note on redefining retention periods By default. media server. if the retention period for level 3 is changed from 1 month to 6 months. Use the bpmedia command to suspend the volumes.464 Host properties Master server. use the following steps: 1 2 Use the NetBackup Media List report to determine which volumes are currently at the level to be suspended. OK: Saves the changes since Apply was last clicked. When the retention period for a level is redefined. NetBackup does not check the retention period that is defined for that level. NetBackup stores each backup on a volume that already contains backups at the same retention level. it can result in backups with different retention periods being stored on the same volume. the backups are placed on the volumes with the level 3 backups that have a retention period of one month. However. and client host properties 7 To save your changes and update the configuration. bpmedia -suspend -m media_ID . For example. OK also closes the dialog box. No problem exists if the new and the old retention periods are of about the same value. NetBackup stores future level 3 backups on the same volumes.

and client host properties 465 Servers properties The Servers properties display the NetBackup server list on selected master servers.) Additional servers The Additional Servers list contains the additional servers that can access the server that is specified as Master server. During installation. media servers. The server list displays the NetBackup servers that each host recognizes. click Add and select a server. media server. The master server value is also used to determine which server the client must connect to so that files can be listed and restored.Host properties Master server. To delete a server. Figure 7-43 Servers host properties dialog box Master server The Master server property specifies the master server for the selected host. then click Remove. . NetBackup sets the master server to the name of the system where the server software is installed. and clients. NetBackup uses the master server value to validate server access to the client. (The name of the selected host appears in the title bar. select a server from the list. ■ ■ To add a server.

To delete a media server. exit all NetBackup administrator interface programs. (Host Properties > Master Server or Media Servers > Servers. Run nbemmcmd -addhost to add a media server to the Enterprise Media Manager (EMM) database of existing master server. click Add and select a server. select another server from the list. but have limited administrative privileges. Machines that are listed as media servers can back up and restore clients. see “To administer a remote master server” on page 635. ■ Note: If you change the server list on the master server.) Machines that are listed as media servers can back up and restore clients.466 Host properties Master server. select a media server from the list. stop and restart both the NetBackup request service and NetBackup Database Manager service on that server This ensures that the change is recognized. then click Remove. ■ To add a new media server. Restricting administrative privileges of media servers The servers in the Media servers list are media servers only. For more information. media server. . To configure access to a remote server. and client host properties ■ To change the master server. but have limited administrative privileges. Then. Media servers The Media servers list specifies that the listed machines are media servers only. add to the server list the name of the host seeking access. then click Make Master.

Host properties Master server. the master server entry takes precedence. media server. A server that is listed as both a master and a media server has consequences. and client host properties 467 Figure 7-44 Media Server list in Servers host properties dialog box Administrative scope of media servers is limited Consider a configuration that consists of master server oak and two media servers—elm 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. It allows a media server system administrator to be a NetBackup administrator on other master servers. .

A shared EMM database located on a master server In the following example. and client host properties Figure 7-45 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. three master servers share one EMM database that is located on one of the servers (meadow).468 Host properties Master server. The Servers host properties must be set up to allow multiple master servers to access the EMM host. The host that contains the EMM database can be either a master server or a media server. media server. The bp.conf server entries on each master server would read as described in the following table: 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 .

. The table shows how meadow is listed on havarti and study. media server. (File > Change Server. and client host properties 469 SERVER entries: ■ The first SERVER entry must be the name of the master server.) If the EMM database is on another master server. study. The following master servers also need to be listed: In order for the NetBackup Administration Console to administer other servers.Host properties Master server. The table shows how meadow is listed as the EMMSERVER on havarti. ■ ■ The EMMSERVER entry must be present on all master servers that share the EMM host. that server needs to be listed. the servers must be listed. as well as on meadow.

Click Make Master. media server. the EMM database also needs to be updated. after changing the master server for a media server.470 Host properties Master server. 1 To modify the master server: Select a server from the list. run: install_path\VERITAS\NetBackup\bin\admincmd\nbemmcmd -updatehost . The server then appears as the new master. and client host properties A shared EMM database located on a media server If the master server is changed on a media server. 2 To update the EMM database.

media server. The NetBackup BasicDisk disk type and the Enterprise Disk Option disk types use mount points for disk storage. media server) where NetBackup mounts the volumes on the disk array. . the NetBackup backup images that reside on that disk storage are backed up. Figure 7-46 SharedDisk host properties dialog box SharedDisk mount points directory The SharedDisk mount points directory specifies the directory on each storage server (that is. and client host properties 471 SharedDisk properties The SharedDisk master server properties specify the SharedDisk storage option properties for your NetBackup configuration. do not cross mount points. (The policy Cross mount points attribute specifies whether to cross mount points. 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.Host properties Master server. The mount point must be the same on all NetBackup media servers that access the array.) If the policy crosses mount points.

Figure 7-47 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). Consistency check before backup Select what kind of consistency checks to perform on the SQL Server databases before NetBackup begins a backup operation.and user-directed backups. Only the data pages and clustered . None: No consistency check is performed. the consistency check runs significantly faster but is not as thorough. These checks are performed for both server. excluding indexes: Select this property to exclude indexes from the consistency check. and client host properties SharePoint 2003 properties The SharePoint 2003 properties apply to currently selected Windows 2003 clients to protect SharePoint 2003 installations.472 Host properties Master server. Password Specify the password for the account. Full check. If indexes are not checked. media server.

Host properties Master server. Figure 7-48 SharePoint Hosts host properties dialog box Use the Add button to add a host that is authorized to run restores on SharePoint component hosts. It also checks the consistency between the pages’ object ID and index ID and the allocation structures. Any errors are logged. SharePoint Hosts properties Special configuration is required to allow NetBackup to restore SQL databases to the correct hosts in a farm. This property checks the integrity of the physical structure of the page and of record headers. including indexes: Include indexes in the consistency check. media server. In the SharePoint Hosts properties. 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. and client host properties 473 index pages for each user table are included in the consistency check. add each host in the farm. Fullcheck. Continue with backup if consistency check fails Select whether or not the backup should continue if the consistency check fails. Provide the name of the Farm front-end host and the name of the Farm component host in the farm. . The consistency of the nonclustered index pages is not checked.

media server. and client host properties Symantec Products properties The Symantec Products properties apply to currently selected master servers. “Backup Exec Tape Reader properties” on page 371. . Figure 7-49 Symantec Products host properties dialog box The Symantec Products properties include the subnode.474 Host properties Master server.

Host properties Master server. . media server. Default: 300 seconds. media servers. and client host properties 475 Timeouts properties The Timeouts properties apply to selected master servers. Figure 7-50 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. and clients. 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. Note: If this timeout is changed. verify that Client read timeout is set to the same or higher value. Default: 300 seconds.

and ready on backups. remote media server. 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. Default: 300 seconds. (For example. The client-read timeout on a database-extension client is a special case. the media mount timeout value is in effect during the caching of potentially migrated files. and client host properties 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. and duplications. when robotic media is out of the robot or if off site. The Media mount timeout property appears only as a master server property.476 Host properties Master server. or database-extension client (such as NetBackup for Oracle). the value in a UNIX client’s $HOME/bp. media server. If File browse timeout is exceeded. Use this timeout to eliminate excessive waiting time during manual media mounts.) While restoring backups or any archives that were written to a disk that Storage Migrator manages. 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. The sequence on a database-extension client is as follows: . restores. positioned. the user receives a socket read failed error even if the server is processing the request.conf file takes precedence to the property here. 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. Note: If it exists. Client read timeout The Client read timeout property specifies the number of seconds to use for the client-read timeout on a NetBackup master.

.read timeout. Note: If this timeout is changed.Host properties Master server. it uses it as the client. Symantec suggests that the Client read timeout be set to a value greater than 5 minutes. For other clients. and client host properties 477 ■ NetBackup on the database-extension client reads the client’s client-read timeout to find the initial value. media server. When the database-extension API receives the server’s value. change Client read timeout only if problems are encountered. If the option is not set. Default: 300 seconds. the standard 5-minute default is used. 15 minutes is adequate for many installations. Default: 30 seconds. 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. verify that Client read timeout is set to the same or higher value. 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. ■ Note: For database-extension clients.

the client does not attempt to retry a restore. (Default: 0. The job remains in the incomplete state as determined by the Move restore job from incomplete state to done state property. the job goes into the incomplete state. A checkpointed job is retried from the start of the last checkpointed file rather than at the beginning of the job. media servers. media server. and client host properties Universal Settings properties The Universal Settings properties apply to selected master servers.) Change Restore retries only if problems are encountered. If a job fails after the maximum number of retries. The client may try up to 3 times.478 Host properties Master server. Figure 7-51 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. 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 381. and clients. .

NetBackup includes files from the time of the last-full backup through the latest backup for the client. the request goes out on the fred_nb interface and over the backup network. The host name for the regular interface is fred. use this entry to specify the network host name of that interface. When client fred starts a backup.) 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. clear the Last full backup checkbox.Host properties Master server. fred can send out the request on the fred interface and over the regular network.client with multiple network interfaces. A NetBackup client or server can have more than one network interface. Example 1 . to limit the browse range to one week before the current date. To force NetBackup connections to be made on a specific network interface. or list operation. This limit is specified on the master server and applies to all NetBackup clients. Last full backup The Last full backup property indicates whether NetBackup include all backups since the last successful full backup in its browse range. media server. If the client belongs to more than one policy. 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. This property must be disabled to enter a value for the Browse timeframe for restores property. The operation assumes that fred and the network are set up to do so. By default. One network interface is for the backup network. . Assume a NetBackup client with two network interfaces: ■ One network interface is for the regular network. A limit can be specified on an individual client to reduce the size of the search window. the operating system determines the one to use. and client host properties 479 Browse timeframe for restores The Browse timeframe for restores property specifies how long ago NetBackup searches for files to restore. restore. The host name for the backup interface is fred_nb. (Default: enabled. If this configuration is not in place. For example. The client setting cannot make the browse window larger. ■ The NetBackup client name setting on both the client and server is fred_nb. then specify 7. By default. then the browse starts with the earliest of the set of last-full backups.

when barney connects to a client.480 Host properties Master server.server with multiple network interfaces. Redirected restores allow the server to accept the request. Example 2 . see the NetBackup Security and Encryption Guide. When barney connects to a client for a backup. . The client now receives the request from barney rather than barney_nb and refuses it as coming from an invalid server. Another solution is to set up the master server to allow redirected restores for client fred. 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. 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. If this configuration is not in place. Now. The operation assumes that barney and the network are set up to do so. media server. However. barney can send out the request on the barney interface and over the regular network. The host name for the regular interface is barney.0 documentation. the request goes out on the barney_nb interface and over the backup network. see the NetBackup 6. One solution is to set Use specified network interface on barney to barney_nb. For information on Symantec Product Authentication and Authorization. and client host properties One solution is to set Use specified network interface on fred to fred_nb. For information about the Use preferred group for enhanced authorization property. The client now accepts requests from barney. restore. All backup. but NetBackup traffic continues on the regular network. Assume a NetBackup server with two network interfaces: ■ One network interface is for the regular network. NetBackup encourages the use of Symantec Product Authentication and Authorization for NetBackup Access Control (NBAC) instead of legacy security implementations. but leaves NetBackup traffic on the regular network. the connection is always through the barney_nb interface and everything works as intended. The server receives requests from client fred_nb with host name fred_nb and everything works as intended. Another solution is to add an entry for barney to the server list on the client. and list requests use the fred_nb interface.

bpcd requires remote connections to come from privileged ports. enable this property to prevent server-directed restores and remote changes to the client properties. Volume II. When disabled. (Nonprivileged ports have port numbers 1024 or greater. Once the Allow server file writes property is applied. Select Connect on non reserved port on the server properties Client attributes tab. the source ports for connections to bpcd use reserved ports as well. For example. (Default: enabled. it can be cleared only by modifying the client configuration. If the client cannot send email. (Applies only to Windows master and media servers. Enable performance data collection (Windows server only) The Enable performance data collection property specifies whether NetBackup updates disk and tape performance object counters. the server that connects to the host must also be configured to use non-reserved ports for the client. For more information.Host properties Master server. see Chapter 5 in the NetBackup Administrator’s Guide.) For more information. (Privileged ports have port numbers less than 1024. 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. and client host properties 481 Allow server file writes The Allow server file writes property specifies whether a NetBackup server can create or modify files on the NetBackup client. media server. Default: server writes are allowed.) If this property is enabled. 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. If the property is disabled (unchecked).) (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.) Accept connections on non reserved ports is useful when NetBackup clients and servers are on opposite sides of a firewall. The NetBackup performance counters can be viewed using the Windows Performance Monitor utility (perfmon). Enable this . (Default: enabled. see “Maximum data streams” on page 384. select Server sends mail.

and client host properties property if the client cannot send mail and you want an email notification.) Client administrator’s email The Client administrator's email property specifies the email address of the administrator on the client. separate entries with commas. To ensure that the system is set up to send mail.482 Host properties Master server. To enter multiple addresses or email aliases. (Default: disabled. By default. This address is where NetBackup sends backup status reports for the client. see “Setting up email notifications” on page 434. no email is sent. media server. .

Figure 7-52 UNIX Client host properties dialog box UNIX Client properties include: ■ ■ ■ “Client Settings (UNIX) properties” on page 393 “Busy File Settings properties” on page 376 “Lotus Notes properties” on page 445 . and client host properties 483 UNIX Client properties The UNIX Client properties define NetBackup properties of UNIX clients.Host properties Master server. media server.

Figure 7-53 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. media server.484 Host properties Master server. and client host properties UNIX Server properties The UNIX Server properties apply to selected UNIX master servers. . Default: 5 seconds.

To delete a server from the list. Figure 7-54 VMWare Proxy Servers host properties dialog box Click Add to add a server to the Proxy Server list.Host properties Master server. For more information. select the server and click Delete. and client host properties 485 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. see the NetBackup Snapshot Client Administrator’s Guide. media server. 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 VSP to back up open and active files. For more information. media server. To make VSP the snapshot provider for a Windows client. VSP must be selected as the snapshot provider for the client(s). VSP overview NetBackup uses VSP to back up open and active files on Windows 2000. see “Client Attributes properties” on page 382. and client host properties VSP (Volume Snapshot Provider) properties The VSP properties apply to currently selected supported Windows clients. Windows XP. 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). and Windows Server 2003 (32. VSP first captures a snapshot of each volume to be . NetBackup uses snapshots to access busy or active files during a backup job. Figure 7-55 Volume Snapshot Provider host properties dialog box In order for the properties in this dialog box to affect client(s). Snapshots are a point-in-time view of a source volume.and 64-bit) clients.486 Host properties Master server. VSP is the default Windows snapshot provider.

and client host properties 487 backed up. ■ ■ ■ ■ 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. The backup begins and NetBackup starts to read the data from the client. If an application requests a read or write during the backup. media server. a snapshot of a volume cannot be created if the volume already contains a VSP cache file. If a quiet period of sufficient length does not occur within the Busy file timeout period. All VSP cache files are placed at the root level of a volume and are removed when its VSP snapshot has been destroyed. However. 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. If a quiet period of sufficient length is detected. a cache file cannot be placed on a volume that has had a snapshot taken. a cache file cannot be placed on a volume that is in the process of having a snapshot taken of it. the backup proceeds without VSP. The Busy file timeout property defines the length of the quiet period.Host properties Master server. 2 3 . Only when the snapshot for the volume has been destroyed can it be used as a location for a VSP cache file. This wait is required to ensure that the file system is in a consistent state. Using VSP. VSP may read or write its cache as necessary to maintain the snapshot and provide accurate data to the application. 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. For more informations. NetBackup uses VSP to create snapshots for the backup job. 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. For each volume snapshot. The cache file is created along with the volume snapshot. VSP cannot be used to perform hot database backups. NetBackup backs up files using the virtual drive instead of the actual drive. Or. NetBackup performs the actions necessary to record the VSP snapshot. NetBackup waits for a quiet period to occur when no writes are performed on the drives that contain data to be backed up. Using VSP. VSP reads or writes the disk. see “Using VSP with databases” on page 493. VSP is similar to OTM (used in previous releases) in that VSP creates volume snapshots using a caching mechanism.

NetBackup does not allow other VSP cache files to be placed in the volume. If no volumes are listed. media server. specify a different location during client installation. NetBackup determines the best location for VSP cache files. Assume that a job backs up the C and D volumes and needs to create VSP volume snapshots for the volumes. For more informations. Logging VSP messages VSP snapshot activity is logged in the bpfis debug log. 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. and client host properties 4 Once the backup completes. NetBackup attempts to destroy the VSP volume snapshots that were created for the backup job. List volumes as drive letters. separated by commas and spaces. D. . The cache files are placed on a listed volume unless NetBackup determines that the volumes are undesirable as cache file locations. the volume with the most free disk space at backup time is the preferred location. Cache file volume list The Cache file volume list serves as a list of preferred locations for NetBackup to place VSP cache files. Delete the directory when the troubleshooting is complete and reset the Global logging level to a lower value. To enable VSP logging. NetBackup may make this determination. The C volume cannot be used as a preferred location for VSP snapshots since it is having a VSP snapshot created for it. create the bpfis directory in the following location (default): C:\Program Files\VERITAS\NetBackup\Logs\ If you want. the bpfis directory can require extensive disk space. (Host Properties > Master Servers > Selected master server > Logging. If multiple volumes are listed.) Eventually.488 Host properties Master server. To create detailed log information. Because VSP does not allow snapshots of the volumes that contain active cache files. set the Global logging level to a higher value in the master server host property Logging dialog box. NetBackup places the VSP cache files for the C and D snapshots in the C and D volumes. It attempts to destroy the VSP snapshots while deleting the VSP cache files for the volume snapshots. A location is undesirable if a volume in the list is also targeted as a snapshot. For example: C. even if a location is user-specified. 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. see “Global logging level” on page 442.

see “Allow multiple data streams” on page 118. List volumes as drive letters. 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. 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 example. All backup jobs (streams) in a policy are grouped into an entity that is called a stream group. Symantec recommends that a volume be listed in both the Cache file volume list and the VSP volume exclude list. a scheduled client backup can be divided into multiple data streams. For example: C. The user prefers the C:\ volume as the location for VSP cache files. The Cache file volume list overrides the VSP volume exclude list if both lists contain the same volume. To run these backups. NetBackup does not create snapshots for C:\ until C:\ is removed from the VSP volume exclude list. VSP volume exclude list The VSP volume exclude list contains the volumes that are excluded from snapping by VSP during backups. and client host properties 489 3 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. If a backup policy is configured to allow multiple data streams.Host properties Master server. Additionally. Volumes in the VSP volume exclude list are excluded from VSP activity and are backed up without snapshot protection. 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. Because the Cache file volume list takes precedence over the VSP volume exclude list. separated by commas and spaces. 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. For more information. All backups that are part of a stream group share their VSP volume snapshots between backup jobs in the stream group. This volume is effectively used as . NetBackup places cache files in C:\ even though it is listed in the VSP volume exclude list. The volumes in the list will never contain VSP cache files. C:\ is specified in the Cache file volume list and in the VSP volume exclude list. media server. yet would not like VSP to snap or place cache files on the volume. 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.

VSP would not have been enabled for the C and D drives for both backup jobs. the D volume has been placed in the Cache file volume list and the VSP volume exclude list. 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. Example 1: Running multiple simultaneous backups with VSP Assume that two backup jobs run simultaneously. 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.). Since 2 3 . VSP snapshots are not created for it. Snapshots of the C drive are created successfully for both backup jobs while their cache files were placed in the D drive. (Each group runs a backup job for each file list item. For this example. For this example. Since the D drive was listed in both the Cache file volume list and the VSP volume exclude list.490 Host properties Master server. 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. the D volume has been placed in the Cache file volume list and the VSP volume exclude list. media server. and client host properties the volume for all VSP cache files. 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. 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. However. Both backup jobs are run simultaneously. All backups for the volume do not have VSP snapshots enabled. VSP cache files for the C drive for both backup jobs were placed in the D drive. both backing up the C and D drives. Snapshots of the C drive are created successfully for both groups of multistreamed jobs while their cache files were placed in the D drive. two groups of multistreamed backup jobs run.

If the form of measurement is Cache size in MB. It can grow to the size indicated by the Maximum cache size. VSP would not have been enabled for the C and D drives for both groups of multistreamed jobs. NetBackup will automatically size VSP cache files for the client. the Maximum cache size is calculated in megabytes. based on the value that is specified in Maximum cache size. Cache size The Cache size property specifies the initial size of the VSP cache file that is allowed for snapshots. the cache file size begins at 0 megabytes. If the D drive was not listed in the Cache file volume list and the VSP volume exclude list. By default. The Maximum cache size is the percentage of free disk space on the cache file volume. and client host properties 491 the D drive was listed in both the Cache file volume list and the VSP volume exclude list. The VSP cache file sizes can be adjusted manually. the Customize the cache sizes property is disabled to allow NetBackup to calculate cache file sizes for VSP snapshots. the Customize the cache sizes property can be disabled. VSP cache files for the C drive for both groups of multistreamed jobs were placed in the D drive. media server. When the VSP cache file is placed on a volume that is not to be snapped. Both groups of multistreamed jobs also backed up the D drive without VSP. Customize cache size The Customize the cache sizes property enables a number of properties that help you set specific cache size characteristics for your backup configuration. If the Customize the cache sizes property is not enabled.Host properties Master server. . Maximum cache size The Maximum cache size indicates how large the VSP cache file may grow to hold snapshots. if the cache file sizes need to be configured 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. This property is only applicable when the VSP cache file is placed on a volume that is not to be snapped. 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. However.

For example. 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. it is ignored. VSP cache files are named with a . ■ 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. NetBackup allocates as much cache space as possible when it creates VSP snapshots. The sizes are used regardless of the sizes of the volumes that are backed up. The recommended setting for Maximum cache size is 95% of free disk space of the cache file volume. 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. If snapshot errors occur when Customize the cache sizes is disabled. A quiet period is a time during . If there is not enough space that is allocated. The recommended setting for the Cache size is 30% of the used disk space of the snapshot volume. it is ignored. Otherwise.VSP extension. 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. Use caution to configure the cache file sizes manually. Exclude files with .492 Host properties Master server. increase Cache size and Maximum cache size to fit the client’s installation. VSP snapshot errors occur. and client host properties If the Customize the cache sizes property is disabled (checkbox is clear). when NetBackup sizes cache files. In most cases. Otherwise. 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. media server. It depends on the data that is backed up and the I/O activity of the backup client. even if Customize the cache sizes is disabled. In some cases. The following items are VSP best practices to configure VSP cache sizes: ■ Disable Customize the cache sizes to allow NetBackup to determine cache file sizes for VSP snapshots. The directories are named NBU_VSP_Cache. The cache file size is the Cache size value if the VSP cache file is placed in the same volume as what is snapshot.VSP extensions from virus scanning activity if VSP snapshot deletion failures occur. D:\ NBU_VSP_Cache Exclude directories are created from virus scanning activity if VSP snapshot deletion failures occur. it avoids VSP snapshot errors.

Sybase. Cold or inactive backups of these databases may be possible with VSP. Databases with an API Hot backups are performed on active databases. and client host properties 493 which no file write-activity occurs on the drive being snapped using VSP. IBM (Lotus Notes.) 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. shut down the database and perform a file system level or cold backup. the backup proceeds without VSP. If this time expires. Microsoft (SQL Server. Oracle. use VSP to back up the databases when they are inactive (cold). media server. For databases with no Veritas database extension product. Exchange). efficient. If the data does not conform to the backup specification that is designed into the database product. If the file system does not achieve a quiescent or . Busy file timeout The Busy file timeout property specifies how long VSP should wait for a quiet period to occur. and Informix are examples of the database vendors that provide an API for use with backup products. Databases without an API For the databases that do not have a backup and restore API. Database programs recover from a point-in-time restore differently. DB2). set Busy file wait to 5 seconds. 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.Host properties Master server. Use a formal API to create a confident backup and the ability to perform a successful restore. If the databases cannot be backed up cold and the only option is a hot backup. Symantec does not recommend using VSP for hot backups of these databases. Contact the specific database vendor to identify the recommended method for database backup where data reliability is ensured.) Using VSP with databases Consider the following information regarding using VSP (Volume Snapshot Provider) to back up and restore databases. Many of these APIs were jointly developed to ensure that data is protected and can be restored when needed. the integrity of the database is questionable. and reliable when used with NetBackup and NetBackup database extension features. (Default: 5 seconds. (Default: 300 seconds. NCR (Teradata). Symantec works with many database vendors to ensure that these interfaces are stable. Some database vendors provide a formal application program interface specifically designed for use with backup products. but success varies with each database vendor.

first back up the data and make sure that the backup exited with a Status 0. . Using VSP to back up active databases without using a formal API presents risk. NetBackup continues the backup as if VSP is not in use. restore the database and confirm the integrity of the data and the functionality of the database. Customers should contact the database supplier to ensure support of database backups using point-in-time technology. NetBackup does not perform the VSP snapshot. and client host properties an inactive state. media server. significant back up and restore testing should be performed to assure database availability and reliability. Also. The backup job ends with an exit status code 1. NetBackup does not fail the backup when a quiescent state is not achieved. Status code 1 indicates that the backup job was completed but not all files were successfully backed up. Then. The result is that NetBackup skips open. Instead.494 Host properties Master server. or locked files. active. If VSP is used to back up database environments.

and client host properties 495 Windows Client properties The Windows Client properties define NetBackup properties for Microsoft Windows clients.Host properties Master server. Figure 7-56 Windows Client host properties dialog box Windows Client properties include: ■ ■ ■ ■ ■ ■ “Client Settings (Windows) properties” on page 398 “Exclude Lists properties” on page 410 “VSP (Volume Snapshot Provider) properties” on page 486 “Network properties” on page 454 “Lotus Notes properties” on page 445 “Exchange properties” on page 408 . media server.

and client host properties . media server.496 Host properties Master server.

see the following: ■ ■ ■ ■ ■ ■ ■ ■ “Changing the operating mode of a drive” on page 497 “Resetting a drive” on page 498 “Managing drive paths” on page 499 “Managing pending requests and actions” on page 499 “Freezing media or downing drives” on page 503 “Cleaning drives” on page 504 “Adding or changing a drive comment” on page 506 “Viewing drive details” on page 506 Changing the operating mode of a drive Usually. you do not have to change the operating mode of a drive. select Media and Device Management > Device Monitor. the Device Monitor pane includes both a Drives tab and a Disk Pools. If an Enterprise Disk Option license is installed. select the Drives tab. To change the mode of a drive 1 In the NetBackup Administration Console. select a drive or select multiple drives. If necessary. In the Drive Status pane. 2 3 .Chapter 8 Device Monitor Use Media and Device Management > Device Monitor to manage tape drives. NetBackup sets the drive state (UP in AVR mode. device paths. For more information. and service requests for operators. the default mode) when you add drives to your configuration. Other operating mode settings are used for special purposes.

498 Device Monitor Resetting a drive 4 From the Actions menu. Not in use by NetBackup. select the Drives tab. you reset a drive when its state is unknown. which can occur if an application other than NetBackup uses the drive. the reset action fails. In the NetBackup Administration Console. Note: A drive reset does not perform any SCSI bus or SCSI device resets. If an SCSI reservation exists on the drive. If necessary. When you reset the drive. you can restart the NetBackup Job Manager. If the drive is configured with multiple device paths or is a shared drive (Shared Storage Option). Select Actions > Reset Drive. Select the path to change. a dialog box appears. choose the command for the new drive operating mode. Up Drive. select Media and Device Management > Device Monitor. the Device Monitor pane includes both a Drives tab and a Disk Pools. If an Enterprise Disk Option license is installed. 5 Resetting a drive Resetting a drive changes the state of the drive. select a drive or select multiple drives. To change multiple paths. 2 3 4 If the drive is in use by NetBackup and cannot be reset. a reset operation from that host that owns the reservation may help the SCSI reservation. . In the Drive status pane. Operator control applies only to stand-alone drives. The dialog box contains a list of all device paths to the drive. select multiple paths. which should free up the drive. it returns to a known state before use with NetBackup. To reset a drive 1 In the NetBackup Administration Console. 1 2 Determine which job controls the drive (that is. If the drive is: ■ ■ In use by NetBackup. NetBackup attempts to unload the drive and set its runtime attributes to default values. Usually. select NetBackup Management > Activity Monitor. which job writes to or reads from the drive).

cancel the job. Caution: When you restart the NetBackup Job Manager. the Pending Requests pane disappears. If NetBackup cannot service a media-specific mount request automatically. as follows: . it cancels all NetBackup jobs in progress. For example. In the Drive Paths pane. the Device Monitor pane includes both a Drives tab and a Disk Pools. To manage drive paths 1 In the NetBackup Administration Console. select Media and Device Management > Device Monitor. If necessary. NetBackup loads or requests the volume. select a path or select multiple paths. select the Drives tab. Restart the NetBackup Job Manager using the Activity Monitor. From the Actions menu. 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. the request is displayed in the Pending Requests pane of the Device Monitor window. as follows: ■ ■ ■ 2 3 4 Up Path Down Path Reset Path Managing pending requests and actions If a tape mount requires a specific volume. If an Enterprise Disk Option license is installed. if NetBackup requires a specific volume for a restore operation. After all requests have been resolved (automatically by NetBackup or manually by operator intervention). choose a command for the path action.Device Monitor Managing drive paths 499 3 4 From the Jobs tab. The Pending Requests pane appears only if requests await action or when NetBackup acts on a request. it changes the request or action to a pending state.

A tape mount requests becomes a pending action when the mount operation encounters problems. To do so. If a robot must be operated in manual mode. NetBackup sets the request status to pending. you cannot reassign the mount request to another storage unit. . Also. Pending requests appear in the Device Monitor. and the tape cannot be mounted. Pending actions usually occur with drives in robotic libraries. NetBackup assigns pending status to a mount request when it cannot determine which: ■ ■ Stand-alone drive to use for a job. If the storage unit is not available. and NetBackup displays an action request in the Pending Requests pane.500 Device Monitor Managing pending requests and actions ■ Pending requests. see NetBackup Commands for Windows. and you can assign these mount requests to drives manually. Drive in a robot is in AVR mode. and NetBackup displays the request in the Pending Requests pane. NetBackup tries to select another storage unit that has a working robot. When NetBackup cannot move a required volume into a tape drive automatically. For more information about the tpconfig command. set the robot to operate in Pend If Robot Down (PIRD) mode by using the tpconfig command. you can configure NetBackup so that storage unit mount requests are displayed in the Device Monitor. NetBackup queues the job (a Queued state is displayed in the Activity Monitor). 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. ■ Pending actions. Operator assistance is required to complete the request. Operator assistance is required to complete the request. NetBackup does not assign a mount request for one storage unit to the drives of another storage unit automatically. If NetBackup cannot find a storage unit for the job.

ACS robots only: If a request is pending because the Library Storage Module (LSM) in which the media resides is offline. NetBackup reports the LSM offline status in the Job Details dialog box. NetBackup Enterprise Server only: Ensure that the drive and the pending request are on the same host. External Media ID to determine the ID of the volume that is required. Also. no operator action is required. 4 5 6 7 8 9 In the Drive Status pane. . write-enable it. select the Drives tab. first insert the requested volume in a drive that matches the density of the volume that was requested. Open the Job Details dialog box from the Jobs tab in the Activity Monitor. the Device Monitor pane includes both a Drives tab and a Disk Pools. In the Pending Requests pane. and insert it into the drive. note the contents of the following columns of the request: ■ ■ ■ 2 3 Density to determine the recording density that is required. NetBackup Enterprise Server only: If the drive and the request are on the same host. use the NetBackup Administration Console to assign the request to that drive. as explained in the vendor’s drive equipment manual. and then drop it on the wanted drive. drag it to the Drive Status pane. Operator assistance is required to complete the request To resolve a pending request. you can use drag and drop to assign the request to a drive. select the request.Device Monitor Managing pending requests and actions 501 Resolving a pending request A pending request is a request for a tape mount that NetBackup cannot service automatically. NetBackup retries such requests hourly until the LSM is online. Wait for the drive to become ready. Select the drive. Verify that the drive is up and not assigned to another request. Select the request in the Pending Requests pane. Second. 10 Select Actions > Assign Request. To assign a pending request to a drive 1 In the NetBackup Administration Console. If necessary. Mode to determine whether the volume should be write-enabled. If an Enterprise Disk Option license is installed. find a drive type that matches the density for the pending request. If necessary. select Media and Device Management > Device Monitor. get the media.

insert it into the robot. If the problem is a volume missing from a robot. .502 Device Monitor Managing pending requests and actions 11 Verify that the request was removed from the Pending Requests pane. An asterisk identifies a pending action. 12 In the Drive status pane. you can resubmit the request. recorded media ID. NetBackup changes the mount request to a pending action. If necessary. A pending action is similar to a pending request. To resolve a pending action 1 In the NetBackup Administration Console. Click OK after viewing the corrective actions. and drive number. In the Pending Requests pane. A message box that describes the problem and a list of possible corrective actions appears. For pending actions. verify that: ■ ■ The job request ID appears in the Request ID column for the drive The User column is not blank Resolving a pending action When a tape mount request encounters problems and the tape cannot be mounted. Usually. Select Actions > Display Pending Action. and then update the volume configuration. the Device Monitor pane includes both a Drives tab and a Disk Pools. select the Drives tab. such as user name. external media IDs. and NetBackup displays an action request in the Pending Requests pane. Operator assistance is required to complete the request. the asterisk appears to the left of the request ID. Pending actions usually occur with drives in robotic libraries. Correct the error condition and either resubmit the request or deny the request. select the pending action. NetBackup determines the cause of the problem and issues instruction to the operator to resolve the action. The message box also shows other information. first locate the volume. select Media and Device Management > Device Monitor. If an Enterprise Disk Option license is installed. 2 3 4 5 6 Resubmitting a request After you correct the problem or problems with a pending action. a missing volume was removed from a robot and then requested by NetBackup.

select the Drives tab. it is logged in the system log. If NetBackup downs a device. For example. The pending action message is removed from the Pending Requests pane and the operation proceeds. Select Actions > Deny Request. In the Pending Requests pane. when a drive is not available. NetBackup freezes the media or downs a device automatically. 2 3 4 Denying a request Some situations may require you to deny requests for service. 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. Repeated write failures are usually the cause for setting a volume to the FROZEN state or a device to DOWN. If necessary. When you deny a request. A volume is also set to FROZEN if the write failure . In the Pending Requests pane. select the request. If necessary. select the Drives tab. the Device Monitor pane includes both a Drives tab and a Disk Pools. Select Actions > Resubmit Request. or the user is not authorized to use the volume. To deny a request 1 In the NetBackup Administration Console. NetBackup sends an appropriate status message to the user. see “Inventory a robot” on page 547. select the request. you cannot find the volume.Device Monitor Freezing media or downing drives 503 For more information. If an Enterprise Disk Option license is installed. If an Enterprise Disk Option license is installed. To resubmit a request 1 In the NetBackup Administration Console. select Media and Device Management > Device Monitor. The reason for the action is logged in the NetBackup error catalog (view the Media Logs report or the All Log Entries report). the Device Monitor pane includes both a Drives tab and a Disk Pools. select Media and Device Management > Device Monitor.

NetBackup downs a drive on the third drive error in 12 hours). and -time_window options to change the default values. ■ For more information. . ■ ■ You can use the NetBackup nbemmcmd command with the -media_error_threshold. You can also use the Device Monitor to: ■ Reset the mount time of the drive. frequency based drive cleaning is configured when you add a drive to NetBackup. Set the cleaning freqency. NetBackup freezes media on the third media error in 12 hours). You should reset the mount time to zero after you perform a manual cleaning. The drive error threshold is 2 (that is. Automatic. To reverse a freeze action ◆ Use the bpmedia command to unfreeze the volume. see “Drive cleaning overview” in the NetBackup Administrator’s Guide for Windows.504 Device Monitor Cleaning drives makes future attempts at tape positioning unreliable. Volume II To clean a drive 1 In the NetBackup Administration Console. see NetBackup Commands for Windows. You can clean a stand-alone drive or a robotic drive if appropriate cleaning media are added to the EMM database. select Media and Device Management > Device Monitor. NetBackup updates the cleaning frequency value for the drive. If you use the Device Monitor to set the cleaning frequency. Common reasons for write failures are dirty write heads or old media. The following are the default values for the error thresholds: ■ The media error threshold is 2 (that is. -drive_error_threshold. Cleaning drives You can perform an operator-initiated cleaning of a drive regardless of the cleaning frequency or accumulated mount time of the drive. The time window for errors is 12 hours. For more information nbemmcmd. To reverse a down action ◆ Use the NetBackup Device Monitor to set the device to Up.

select Set Cleaning Frequency. In the Drive Status pane. To set cleaning frequency 1 In the NetBackup Administration Console. select a drive. select the Drives tab. If an Enterprise Disk Option license is installed. select Reset Mount Time. The mount time for the selected drive is set to zero. select Media and Device Management > Device Monitor. you can choose only one host on which the function applies. If an Enterprise Disk Option license is installed. the Device Monitor pane includes both a Drives tab and a Disk Pools. From the Actions menu. From the Actions menu. Shared drive (Shared Storage Option): In the list of hosts that share the drive. Enter a time (hours) or use the arrow controls to select the number of mount hours between each drive cleaning. select Media and Device Management > Device Monitor. select a drive. 2 3 4 5 . select the Drives tab.Device Monitor Cleaning drives 505 If an Enterprise Disk Option license is installed. From the Actions menu. Clean Now resets the mount time to zero. To reset the mount time 1 In the NetBackup Administration Console. but the cleaning frequency value remains the same. In the Drive Status pane. the Device Monitor pane includes both a Drives tab and a Disk Pools. If the drive is a stand-alone drive and it contains a cleaning tape. If necessary. The Clean Now function may take several minutes to complete. 2 3 4 If necessary. If necessary. In the Drive Status pane. NetBackup issues a mount request. NetBackup initiates drive cleaning regardless of the cleaning frequency or accumulated mount time. so the cleaning information in the Drive Details dialog may not be updated immediately. you can choose only one host on which the function applies. select the Drives tab. select the drive to clean. the Device Monitor pane includes both a Drives tab and a Disk Pools. 2 3 4 Shared drive (Shared Storage OptionShared Storage Option): In the list of hosts that share the drive. select Clean Now.

select the Drives tab. Adding or changing a drive comment You can add a comment that describes how a drive is used or change an existing comment. select Media and Device Management > Device Monitor. Select Actions > Change Drive Comment. the Device Monitor pane includes both a Drives tab and a Disk Pools. If an Enterprise Disk Option license is installed. drive status. In the Drive status pane. select Media and Device Management > Device Monitor. host. If an Enterprise Disk Option license is installed. see “NetBackup naming conventions” on page 629. To obtain drive details 1 In the NetBackup Administration Console. select the host and the device path to the selected drive that you want to change. such as drive cleaning. the Device Monitor pane includes both a Drives tab and a Disk Pools. The drive cleaning interval is displayed in the Drive Details dialog (Actions > Drive Details). . drive properties. This function is not available for shared drives. To add or change a drive comment 1 In the NetBackup Administration Console. The dialog shows the current comment (if any is currently configured). For a shared drive (Shared Storage Option).506 Device Monitor Adding or changing a drive comment Cleaning Frequency is not available for the robots that do not support frequency-based cleaning. Enter a comment or change the current drive comment. select a drive or select multiple drives. 2 3 4 5 6 7 Viewing drive details You can obtain detailed information about drives (or shared drives). If necessary. For a list of allowable characters. You can change the comment for any or all of the host and the device paths. and robotic library information. Drive comments appear in the Drive Status pane. Click OK.

select a drive. In the Drive Status pane. select the Drives tab. The following applies only to NetBackup Enterprise Server. For shared drives. You also can view a list of hosts that share a drive. . Select Actions > Drive Details.Device Monitor Viewing drive details 507 2 3 4 If necessary. you can view the drive control mode and drive index for each host that shares a drive.

508 Device Monitor Viewing drive details .

Attributes include the media ID. and slot location. 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. robot type. or you can add them to your storages devices when you add them to NetBackup. The media can already reside in a storage devices. see “Using the physical inventory utility” on page 572. The following are operations you can perform on volumes: ■ “Adding volumes” on page 510 . see Importing NetBackup or Backup Exec images. see “Using WORM media” on page 589. Volume information is stored in the EMM database. see the following: ■ “Robot inventory operations” on page 544 If you have volumes without barcodes to manage. robot host. For information about how to manage media in NetBackup and the logical entities that help you manage volumes. If you have WORM media. To import Backup Exec volumes. robot number.Chapter 9 Media Use Media and Device Management > Media to add and manage media (tape volumes) to NetBackup. see the following: ■ ■ ■ “Volume operations” on page 509 “Volume pool operations” on page 540 “Volume group operations” on page 544 For information about how to inventory robots and how to update the NetBackup volume configuration with media changes in the robots. NetBackup uses the attributes to track and manage the media.

as follows: ■ ■ ■ “Adding volumes by using the Volume Configuration Wizard” on page 513 “Adding volumes using a robot inventory update” on page 513 “Adding volumes using the Actions menu” on page 514 “Adding volumes overview” on page 510 “About labeling NetBackup volumes” on page 512 To help you determine which method to use. review the following information: ■ ■ Note: When you add a new volume. 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 511 “Stand-alone volumes” on page 511 .510 Media Volume operations ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ “Changing volume properties” on page 518 “Changing the volume pool of a volume” on page 520 “Changing the volume group of a volume” on page 520 “Changing the owner of a volume” on page 521 “Freezing and unfreezing media” on page 521 “Suspending and unsuspending media” on page 522 “Labeling media” on page 522 “Rescanning and updating barcodes” on page 524 “Moving volumes” on page 525 “Erasing media” on page 529 “Injecting and ejecting volumes” on page 531 “Deleting volumes” on page 534 “Deassigning volumes” on page 535 “Exchanging volumes” on page 537 “Recycling volumes” on page 539 Adding volumes Several methods exist to add new volumes to NetBackup. a volume expiration date is not assigned.

Stand-alone volumes Stand-alone volumes are volumes located in a drive that is not in a robot. NetBackup uses the volume if a volume of that type is required for a backup. For more information. see NetBackup Commands for Windows. when NetBackup requests one of the volumes. Even if you use NetBackup’s assignment capabilities to add stand-alone volumes. if a volume in a stand-alone drive is full or unusable because of errors. you can add a range of volumes. follow the instructions in “Adding volumes using the Actions menu” on page 514. you may prevent out of media errors by adding extra stand-alone volumes manually. ■ ■ . For more information. review the following: ■ The easiest way to add stand-alone volumes is to use the Volume Configuration Wizard. For example. The DISABLE_STANDALONE_DRIVE_EXTENSIONS option of the nbemmcmd command can turn off NetBackup’s automatic use of stand-alone volumes. If you added another stand-alone volume. you can insert it into the stand-alone drive and NetBackup labels it. You can add additional stand-alone volumes to the NetBackup configuration even though they do not reside in the drive. However. The easiest way to add robotic volumes is to use the Volume Configuration Wizard. Because NetBackup does not label volumes until it uses them. see NetBackup Commands for Windows. The additional volumes are available for use if the volume in the drive becomes full or unusable.Media Volume operations 511 ■ ■ “NetBackup catalog backup volumes” on page 512 “About labeling NetBackup volumes” on page 512 Robotic volumes Robotic volumes are volumes located in a robot. NetBackup ejects (logically) the volume. 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. you can use the other methods. Second. use the NetBackup bplabel command to label the volume and assign a media ID. NetBackup requests that volume and does not generate an error. First. To determine a method for adding stand-alone volumes. NetBackup assigns media IDs and labels the volumes automatically. Then.

see “Labeling media” on page 522. Normally. To label such media. Ensure that you assign them to the volume pool you use for catalog backups. . To change this default action. A volume is labeled unless it was last used for NetBackup catalog backups or it contains data from another recognized application.512 Media Volume operations NetBackup catalog backup volumes To add NetBackup catalog backups. it writes a record on the media. compatible. by default NetBackup generates media IDs for new volumes. After you add volumes. NetBackup labels it the first time it is used for a backup. If the robot supports barcodes. If you prefer to assign specific media IDs. you can specify and select specific characters by using Media ID generation rules (see “Media ID Generation tab” on page 565). 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. Recognized applications include Symantec Backup Exec and Veritas Storage Migrator. NetBackup uses a default prefix of the letter A when it assigns media IDs to volumes without barcodes (for example. ■ ■ ■ Prelabeling media It may be beneficial to prelabel media for the following reasons: ■ A successful label operation validates that the media is usable. The barcode label or external label is gone or damaged.conf file. To change this default. To change this default action. and is not write-protected. About labeling NetBackup volumes When NetBackup labels media. you can use any of the methods. A00001). use the MEDIA_ID_PREFIX configuration option in the vm. You use the physical inventory utility (vmphyinv) to manage media. The last six characters of the barcode are used for the ID. the record (or label) includes the NetBackup media ID. you can specify and select specific characters using Media ID generation rules (see “Media ID Generation tab” on page 565). The recorded label may assist with media management if: ■ ■ ■ ■ The media is misplaced. use the NetBackup Catalog Backup wizard to configure a catalog backup policy. label them by using the NetBackup bplabel command and then add them using the manual update procedure.

Select the robotic library where you inserted the volume. . NetBackup generates media IDs based on one of the following: ■ The last six characters of the barcodes ( the default method). To add volumes using a robot inventory update 1 2 3 4 5 Insert the volume(s) into the robotic library. The characters that you specify if you use media ID naming rules. Select Actions > Inventory Robot. select Media and Device Management > Media > Robots.Media Volume operations 513 Adding volumes by using the Volume Configuration Wizard Use this wizard to do the following: ■ Inventory robots. select Update volume configuration. volume pool. New volumes are assigned a media type. and description. For procedures. maximum number of mounts (or maximum cleanings). The wizard uses the default media type for the drive to create the media type. media IDs are based on a prefix that you specify. After the wizard configures media. Update the Enterprise Media Manager (EMM) database. Review the limitations in the wizard help before you 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. see “Robot inventory operations” on page 544. ■ ■ If the robot does not support barcodes or the volumes do not have readable barcodes. To start the Volume Configuration Wizard ◆ In the NetBackup Administration Console. each media has a unique media ID in the EMM database. select Media and Device Management > Configure Volumes. In the NetBackup Administration Console. 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. In the Inventory Robot dialog. For more information. see “Barcode Rules tab” on page 561.

For descriptions of the properties. You can add another volume by modifying the dialog contents and then click Apply or OK. Adding volumes using the Actions menu Note: Symantec recommends using the Volume Configuration Wizard or a robot inventory to add volumes. see “Volumes properties” on page 515. insert them into the proper slots. In the NetBackup Administration Console. Reads the barcode of each new volume. you must delete the volume and add it again. Note: Be careful when you specify properties. Adds the barcodes as attributes in the EMM database. The Apply button adds the volume without closing the dialog or refreshing the display. In the Add Volumes dialog. . To add volumes using the Actions menu 1 2 3 4 For new volumes in a robotic library. NetBackup does the following: ■ ■ ■ Adds the volume to the EMM database using the specified media ID. You cannot change some properties later. click Clear Results. specify the attributes for the volumes. such as the media ID or type. To clear any previous display in the Results section. Select Actions > New > New Volumes. select Media and Device Management > Media. click Advanced Options. If the robot has a barcode reader.514 Media Volume operations 6 7 8 For more options. Click Start to start the update. If you specify them incorrectly.

Using the pattern. from which you can find a robot that does not appear in the Robot box. First slot number To add new volumes in a robot. see “NetBackup naming conventions” on page 629. NetBackup assigns the remainder of the slot numbers sequentially. The robot vendor tracks the slot locations for API robot types. Media IDs can be from 1 to 6 characters in length. Use this option to add a new robot. Use the same pattern that you chose in the Media ID naming style box. you must specify the first slot number to use for the range of volumes. Find robots Use Find Robots to open the Find Robot dialog. specifies the ID of the first volume in the range of volumes. When you add a range of volumes. Note: You cannot enter slot information for volumes in an API robot.Media Volume operations 515 Volumes properties The following sections describe the properties you can configure when you add volumes. . NetBackup names the remaining volumes by incrementing the digits. For information about the characters you can use in a name. First media ID Appears only if the number of volumes is more than one.

516 Media Volume operations Maximum mounts/maximum cleanings For a backup volume. Therefore. Media type For optical disk volumes that are supported on UNIX and Linux only. NetBackup supports barcodes from 1 to 6 characters. consult your vendor documentation for information on the expected life of the volume. To determine the maximum mount limit to use. The number must be greater than zero. Media IDs can be from 1 to 6 characters in length. For example. you must obtain a list of the barcodes before you add the volumes. When a volume reaches the mount limit. Media IDs for an API robot must match the barcode on the media (for API robots. Using the pattern. For more information. If you enter a value larger than 99999. but not written. NetBackup may display it as 0 although it uses the actual value. For API robots. Zero (0) indicates unlimited mounts. see “NetBackup naming conventions” on page 629. Therefore. see “Drive cleaning overview” in the NetBackup Administrator’s Guide for Windows. You can obtain this information through a robotic inventory or from the robot vendor’s software. NetBackup media IDs for an API robot must match the barcode on the media. You can obtain this information through a robotic inventory or from the robot vendor’s software. see “NetBackup naming conventions” on page 629. specify the number of cleanings that can be performed. Media type specifies the media type for the volume to add. you must obtain a list of the barcodes before you add the volumes. Media ID Specifies the ID for the new volume. NetBackup names the remaining volumes by incrementing the digits. Select the style to use to name the range of volumes. Media IDs can be from 1 to 6 characters in length. For a cleaning tape. the output of the vmrule command displays 0 for values larger than 99999. . NetBackup supports barcodes from 1 to 6 characters). For information about the characters you can use in a name. specify the maximum number of times NetBackup should mount the volumes. Volume II Media ID naming style Appears only if the number of volumes is more than one. For information about the characters you can use in a name. the volume can be read.

select Standalone. up to 25 character maximum. ■ ■ . The only way to clear a volume group name is to move the volume to stand-alone and not specify a volume group. a media type and its corresponding cleaning media type are allowed in the same volume group (such as DLT and DLT_CLN). You cannot add volumes to a robotic library without specifying a group or having NetBackup generate a name. if it does not exist. Alternatively. or off-site if you use the NetBackup Vault option. select a robot from the list. The location can be either the robot in which the volume resides. To add volumes to a different robot. For example.Media Volume operations 517 Media description Enter a description of the media. Robot Specifies the robotic library to add the volumes to. If you do not specify a volume group (you leave the volume group blank): ■ ■ Stand-alone volumes are not assigned to a volume group. The list shows robots on the selected host that can contain volumes of the selected media type. you can select from a volume group already configured for that robot. To add volumes to a stand-alone drive. However. Number of volumes Specifies the number of volumes to add. 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. For information about the characters you can use in a name. stand-alone. NetBackup generates a name for robotic volumes using the robot number and type. enough slots must exist for the volumes. see “NetBackup naming conventions” on page 629. For a robotic library. enter the name for a volume group. Volume group The volume group shows the location of the volume. If you specified a robot. if the robot is a TL8 and has a robot number of 50. NetBackup creates it and adds the volume to it. the group name is 000_00050_TL8. All volumes in a robotic library must belong to a volume group.

DataStore is the default pool name for DataStore. In the Change Volumes dialog. you cannot add a group (or part of a group) to a robotic library if it already exists in another robotic library. When the images on a volume expire. For example. see “Volume pool and volume group overview” in the NetBackup Administrator’s Guide for Windows. To change volume attributes 1 2 3 4 In the NetBackup Administration Console. select a volume or volumes. see “Change Volumes properties” on page 519. You can select a volume pool you created or one of the following standard NetBackup pools: ■ ■ ■ ■ None. Select Edit > Change. For descriptions of the properties. That is. select Media and Device Management > Media. All members of a group must be in the same robotic library or be stand-alone. including the volume pool. . In the Volumes pane. CatalogBackup is the default pool name used for NetBackup hot. For more information. NetBackup is the default pool name for NetBackup. Volume II Changing volume properties You can change some of the properties of a volume.518 Media Volume operations ■ More than one volume group can share the same location. see “Volume pool and volume group overview” in the NetBackup Administrator’s Guide for Windows. change the attributes for the volume. a robotic library can contain volumes from more than one volume group and you can have more than one stand-alone volume group. ■ For more information. Volume II Volume pool The pool to which the volume or volumes should be assigned. online catalog backups of policy type NBU-Catalog. NetBackup returns it to the scratch volume pool if it was allocated from the scratch pool.

. When you add a new volume.Media Volume operations 519 Change Volumes properties The following sections describe the volume properties you can change. When the expiration date has passed. The expiration date is not the same as the retention period for the backup data on the volume. When the limit is reached. NetBackup reads data on the volume but does not mount and write to the volume. consult your vendor documentation for information on the expected life of the volume. NetBackup reads data on the volume but does not mount and write to the volume. 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. Maximum mounts Does not apply to cleaning tapes. To help determine the maximum mount limit. You specify data retention periods in the backup policies. A value of zero (the default) is the same as Unlimited. a default expiration date is not added. The number of times that the selected volumes can be mounted.

CatalogBackup is the default pool name used for NetBackup hot. see “Volume pool and volume group overview” in the NetBackup Administrator’s Guide for Windows. see “Changing volume properties” on page 518. For information about the characters you can use in a name. NetBackup stops using the tape. Number of cleanings remaining Cleaning tapes only. DataStore is the default pool name for DataStore. If you move a volume physically to a different robot. you must change the group of the volume to reflect the move. stand-alone. For more information. For procedures. online catalog backups of policy type NBU-Catalog. You can select a volume pool you created or one of the following standard NetBackup pools: ■ ■ ■ ■ None. You then must change the cleaning tape or increase the number of cleanings that remain. . 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. Volume pool Does not apply to cleaning tapes. see “NetBackup naming conventions” on page 629. or off-site if you use the NetBackup Vault option. This number is decremented with each cleaning and when it is zero. The pool to which the volume or volumes should be assigned.520 Media Volume operations Media description Specifies how the selected volumes are used or any other relevant information about the volumes. Changing the volume group of a volume The volume group shows the location of the volume. Specifies the number of cleanings that are allowed for a cleaning tape. NetBackup is the default pool name for NetBackup. The location can be either the robot in which the volume resides.

In the Media Owner field. and it remains assigned to NetBackup. If the backups have expired. Select Actions > Change Volume Group. Click OK. If you specified a new volume group (which creates a new volume group). In the Volumes list. The name change is reflected in the volume list entry for the selected volumes. The volume must be assigned and owned (that is. select the volumes that you want to change the volume group assignment for. enter the name of the new volume group or select a name from the list of volume groups. see “Configuring server groups for media sharing” on page 614. Changing the owner of a volume The media owner defines who can write to the volume. For more information about server groups. Click OK.Media Volume operations 521 To change the volume group 1 2 3 4 5 In the NetBackup Administration Console. either a media server or server group. . select the new owner. In the Volumes list. A frozen volume is available for restores. The media ID is never deleted from the NetBackup media catalog. select Media and Device Management > Media. Select Actions > Change Media Owner. select the volume that you want to change. Freezing and unfreezing media A frozen volume is unavailable for future backups. it must contain valid backup images) before you can change the owner. select Media and Device Management > Media. To change the owner of a volume 1 2 3 4 5 In the NetBackup Administration Console. A frozen volume never expires. you must import the backups first. In the New volume group name field. even after the retention period ends for all backups on the media. the group appears under Volume Groups in the tree pane.

They contain data from a recognized non-NetBackup application and NetBackup is configured to prohibit media overwrite for that media type. see “Deassigning volumes” on page 535. If the backups have expired. In the Volumes list. For more information. select the volume that you want to freeze or unfreeze.522 Media Volume operations To freeze or unfreeze media 1 2 3 4 In the NetBackup Administration Console. However. At that time. media are not labelled automatically if: ■ ■ They were last used for NetBackup catalog backups. you can deassign the volume so you can label it. NetBackup deletes the suspended volume from the NetBackup media catalog and unassigns it from NetBackup. select Media and Device Management > Media. Select Actions > Freeze or Actions > Unfreeze. To suspend or unsuspend media 1 2 3 4 In the NetBackup Administration Console. NetBackup controls the labeling of its volumes and in most cases performs this operation automatically. Normally. you must import the backups first. . In the dialog box. Select Actions > Suspend or Actions > Unsuspend. Suspending and unsuspending media You cannot use a suspended volume for backups until retention periods for all backups on it have expired. click OK. select the volume that you want to freeze or unfreeze. select Media and Device Management > Media. the record (or label) includes the NetBackup media ID. it writes a record on the media. click OK. Labeling media When NetBackup labels media. In the Volumes list. A suspended volume is available for restores. If NetBackup has not assigned them If they contain no valid NetBackup images You can label these media manually as follows: ■ ■ If a volume has valid NetBackup images. In the dialog box.

In the Label dialog. Label properties The following sections describe the properties you can specify for a label operation.Media Volume operations 523 If you want to label media and assign specific media IDs (rather than allow NetBackup to assign IDs). they all must reside in the same robot. To label media 1 2 3 4 5 6 In the NetBackup Administration Console. Select Actions > Label. . the media is not relabeled. you may not be able to cancel a label job from the Activity Monitor. NetBackup cannot restore or import the data that was on the media after you label it. click OK. If you selected Verify media label before performing operation and the actual volume label does not match the expected label. If you select multiple volumes. see “About labeling NetBackup volumes” on page 512. specify the properties for the label operation. Caution: If you label a volume. select a volume or the volumes that you want to label. Caution: For many types of drives. In the Volumes pane. In the warning dialog. use the bplabel command. For descriptions of the properties. see “Label properties” on page 523. For more information. select Media and Device Management > Media. Click OK.

If you selected Verify media label before performing operation and the actual volume label does not match the expected label. To correct that problem. NetBackup does not add the barcode to the database. you must do one of the following: ■ Logically move the volume by selecting a volume and by using Actions > Move. Verify label before performing operation Select this option to verify that the media in the drive is the media expected. 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. For example. the media is not relabeled. Physically move the volume into the correct slot. 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. You can use this command to add the barcode after you insert the tape into the robotic library. do not select Verify media label before performing operation. if you add a new volume to your configuration but do not insert the tape into the robotic library at that time. See “Show contents” on page 551 for more information. When to rescan and update Use Rescan/Update Barcodes only to add the barcodes that are not in the EMM database. Note: Rescan/Update Barcodes does not apply to volumes in API robot types. To overwrite any existing labels on the media. ■ ■ To obtain an inventory of the robotic library without updating the barcode information in the database. . select Show contents in the Robot Inventory dialog.524 Media Volume operations Media server The name of the media server that controls the drive to write the label. See “Update volume configuration” on page 553. Logically move the volume by using an Update volume configuration operation.

move DLT media to an 8-mm robot).Media Volume operations 525 Rescanning/updating barcodes To check barcodes and update the EMM database 1 2 3 4 In the NetBackup Administration Console. 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. For some robot types. Moving volumes When you move volumes in or out of a robotic library or from one robot to another. which updates the EMM database to show the volume at the new location. you must move the volumes physically and logically: ■ Physically move volumes by inserting or by removing them. Symantec recommends that you perform moves by selecting and by moving only one type of media at a time to a single destination. A dialog appears with the results of the update. In the Volumes pane. you can use the NetBackup inject and eject options. select the volumes. Select the robotic library that contains the volumes that you want to scan and update. ■ When you move volumes from one robotic library to another robotic library. Select Actions > Rescan/Update Barcodes. select Media and Device Management > Media > Robots. Move examples The following are several examples of when to move volumes logically: . Logically move volumes using NetBackup.

Moving volumes from one robotic library to another (for example. Select Actions > Inventory Robot. and then configure a new volume for the empty slot or move an existing volume into that slot. move them to stand-alone. 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. NetBackup updates the EMM database with the correct barcode. The robot must have a barcode reader and the volumes must have readable barcodes. select Media and Device Management > Media. In the Volumes pane. see “Robot inventory operations” on page 544. if a library is down). To remove volumes from a robot. ■ To move volumes using a robot inventory update 1 2 3 4 Physically move the volumes to their new location. In the NetBackup Administration Console. . select the volumes that you want to move. To move volumes using the Actions menu 1 2 3 4 Physically move the volumes to their new location. select Update volume configuration. In the Robot Inventory dialog. Select Actions > Move. Select other options as appropriate. Moving volumes using the Actions menu If you move a volume to a robotic library that has a barcode reader. remove it from the robot. You can use the same process to replace a defective volume. For more information. You can use this procedure even if the volumes do not have barcodes or if the robot does not have a reader. Moving volumes from a robotic library to an off-site location or from an off-site location into a robotic library.526 Media Volume operations ■ 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. When you move tapes to an off-site location.

a Move Volumes dialog appears for each residence and each media type. For descriptions of the properties. specify the properties for the move. a new robot). You can specify a different robot as the destination or Standalone. specify the first slot number to be used in the destination robotic library. . The robot vendor tracks the slot locations for these robot types. see “Move Volumes properties” on page 527. 5 In the Move Volumes dialog. For more information. First slot number For volumes in a robotic library. Robot Robot specifies the new robotic library for the volumes. By default. Move Volumes properties The following sections show the properties you can configure in the Move Volumes dialog. Note: You cannot enter slot information for volumes in an API robot. this box shows the slot number where the volume currently resides.Media Volume operations 527 If you selected volumes of different media types or volume residences. see “Multiple Move Volumes dialog boxes” on page 528. NetBackup assigns the remainder of the slot numbers sequentially. Find Robots Use Find Robots to find a robot that does does not appear in the Robot box (for example.

if the robot is a TL8 and has a robot number of 50. if volume group already exists in another robotic library. The following are the rules for moving volumes between groups: ■ ■ ■ ■ Volumes to move The Volumes to move section of the dialog shows the media IDs of the volumes that you selected to move. you select two full volumes to move out of a robotic library and two stand-alone volumes to move in as replacements. For example. The new volume group must be for the type of volumes as you are moving. number. a Move Volumes dialog appears for each residence and each media type. If you selected one side of an optical disk platter. That is. NetBackup generates the name by using the robot number and type. the group name is 000_00050_TL8. If you leave the volume group blank: ■ ■ Stand-alone volumes are not assigned a volume group. More than one volume group can share the same location. Multiple Move Volumes dialog boxes If you selected volumes of different media types or volume residences. For example. If you do not specify a group. In this example. you cannot add it (or part of a it) to a robotic library. Volume group Enter or select the volume group to assign to the volumes. . NetBackup generates a new volume group name by using the robot number and type. Robotic volumes are assigned to a new volume group. and control host for any robot that already has at least one volume in the EMM database. a robotic library can contain volumes from more than one volume groupm and you can have more than one stand-alone volume group. For example. you must complete both move dialogs to execute the move (complete the move for the volumes that are full first). All volumes in a robotic library must belong to a volume group.528 Media Volume operations The list shows the robot type. All members of a group must be in the same robotic library or be stand-alone. A dialog box appears for the two full volumes and another dialog for the two replacement volumes. that side is shown but both sides are moved.

NetBackup cannot restore or import the data on the media. .Media Volume operations 529 Note: These multiple Move Volumes dialogs may appear on top of each other and need to be repositioned. The following is an example of a move of multiple types or residences: Figure 9-1 Move volumes to stand-alone Figure 9-2 Move volumes to the robot Erasing media Caution: If you erase 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.

Click OK. Click OK if you are certain you want to start the erase action. If you selected multiple volumes. specify the name of the media server the name of the media server to initiate the erase operation. 5 6 . select a volume or volumes that you want to erase. see “Deassigning volumes” on page 535. The format of this gap is drive dependent. Some drives do not support a quick erase (such as QUANTUM DLT7000). the new tape header that is written acts as an application-specific quick erase. select Media and Device Management > Media. Caution: A long erase is a time-consuming operation and can take as long as 2 hours to 3 hours. do not select Verify media label before performing operation. In the volumes pane. An SCSI long erase is also called a secure erase because it erases the recorded data completely. A dialog warns you that this action is irreversible. For a long erase. Note: NetBackup does not support erase functions on NDMP drives. they must all be in the same robot For a short erase. select Actions > Long Erase. To overwrite any existing labels on the media. For more information. For the drives that do not support a quick erase. For example. A dialog reminds you to use the Activity Monitor to view the progress and status of the action. It may be an end-of-data (EOD) mark or a recorded pattern that the drive does not recognize as data. select Actions > Quick Erase. Click OK. The following are the erase options: ■ SCSI long erase rewinds the media and the data is overwritten with a known data pattern. To erase media 1 2 3 4 In the NetBackup Administration Console. 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. you can deassign the volume so you can label it. In the erase dialog.530 Media Volume operations If a volume has valid NetBackup images.

Select Empty media access port prior to update on the Robot Inventory dialog box. Other libraries may not be compatible at all. If the MAP contains multiple volumes. some libraries have front-panel inject and eject functions that conflict with NetBackup’s use of the media access port. Injecting and ejecting volumes Media access port (MAP) functionality differs between robotic libraries. you are not prompted to place volumes in the media access port and the update operation continues. For many libraries. Use the Activity Monitor to view the status of the action. However. Read the operator manual for your library to understand the media access port functionality. . NetBackup opens and closes the MAP as needed. See the following related topics for more information: ■ ■ ■ “Injecting volumes” on page 531 “Ejecting volumes” on page 532 “Media ejection timeout periods” on page 534 Injecting volumes Inject volumes into the robots that have media access ports by loading the volumes in the MAP and then inventory the robot. Libraries such as the ones noted may not be fully compatible with the inject and eject features of NetBackup unless properly handled. Each volume in the MAP is moved into the robotic library. the media is not erased.Media Volume operations 531 If you selected Verify media label before performing operation and the actual volume label does not match the expected label. you may not be able to cancel a label or erase media job from the Activity Monitor. If no volumes are in the port. And for other libraries. NetBackup updates the volume configuration. Any volumes to be injected must be in the media access port before the operation begins. NetBackup requires front-panel interaction by an operator when using the media access port. Caution: For many types of drives. 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.

select Media and Device Management > Media. For more information about eject. 4 If the Eject Volume (singular) dialog box appears.532 Media Volume operations Some robots report only that media access ports are possible. For other supported robot types. you are prompted to remove the media from the media access port so the eject can continue with the remaining volumes. see “Update volume configuration” on page 553. For instructions. see “Media ejection timeout periods” on page 534. To eject multiple volumes from ODL robot type and TSH robot type. the selected volumes are ejected one volume at a time. Empty media access port prior to update may be available for some robots that do not have media access ports. In the Volumes pane. An operator must remove each volume and respond to NetBackup prompts. Ejecting volumes You can eject single or multiple volumes. select one or more volumes that you want to eject. either the Eject Volume (singular) or Eject Volumes (plural) dialog box appears. multiple eject dialogs appears for each robot type. Depending on the robot type. click OK to eject the volumes. You can eject the volumes that reside in multiple robots. If you do. operator intervention is required only if the media access port is too small to contain all of the selected volumes. Therefore. To eject volumes 1 2 3 In the NetBackup Administration Console. . Select Actions > Eject Volumes From Robot. For these robot types.

the Errors tab shows an explanation of the error.Media Volume operations 533 If you selected multiple volumes. For other errors. For most robot types. you must correct the error before you can eject the media. if so. You may continue the eject action (select Eject) or exit (select Close) depending on the type of error. operator action is required to remove each volume after each eject (a dialog box prompts you to remove volumes). continue with the following: ■ After NetBackup completes prechecks for the eject. the Errors tab is opened. the eject may not be possible. The following two classes of errors can occur: ■ ■ For serious errors. The robotic library may not have a media access port large enough to eject all of the selected volumes. select the media access port to use for the eject. If an error occurs or a hardware limitation exists. ■ 6 7 ACS and TLM robots only: In the Eject Volumes dialog box. If no errors occur. you are prompted to remove the media from the media access port so the eject can continue with the remaining volumes. 5 If the Eject Volumes (plural) dialog box appears. the Media tab of the Eject Volumes dialog box shows the volumes that you selected to eject. . the Errors tab is empty. click Eject to eject the volumes. In the Eject Volumes dialog box. the Eject button is not active.

NetBackup Enterprise Server. ■ ■ ■ . Robot types Automated Cartridge System (ACS) Tape Library Multimedia (TLM) Tape Library 8MM (TL8) Tape Library DLT (TLD) Tape Library Half-inch (TLH) None. Caution: If media is not removed and a timeout condition occurs. The robot allows an unlimited Applies only to period to remove media. Note: After you add or remove media manually. Deleting volumes You can delete volumes from the NetBackup configuration. the operator must remove the volumes from the robot manually. use NetBackup to inventory the robot. 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. Timeout period One week Note Applies only to NetBackup Enterprise Server. the media is returned to (injected into) the robot. A volume is unusable because of repeated media errors. For example.534 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. 30 minutes. Some robots do not have media access ports. and you want to replace it with a new volume. A volume is past its expiration date or has too many mounts. A volume is lost and you want to remove it from the EMM database. For these robots. if any of the following situations apply. You should inventory the robot and then eject the media that was returned to the robot. The following table shows the ejection timeout periods for robots.

see “Deassigning volumes” on page 535. Note: You cannot delete any assigned volumes until any application (NetBackup or Storage Migrator) using them deassigns them. To deassign a volume. the volume on other side is also deleted. when when you stop using it for catalog backups. you cannot delete it or change its volume pool. To delete volumes 1 2 In the NetBackup Administration Console. To delete a volume group. NetBackup and Storage Migrator volumes have an extra safeguard against accidental deletion. A volume is set to the assigned state when either applications first starts using it to store data. A volume remains assigned until NetBackup or Storage Migrator deassigns it. When a volume is assigned. NetBackup deassigns a volume only when the data is no longer required. 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). For catalog backup volumes. ensure that it does not have any important data. You cannot delete such volumes if they are still assigned.Media Volume operations 535 After a volume is deleted. In the Volumes pane. Note: If you selected only one side of an optical platter. when the retention period has expired for all the backups on the volume. 3 4 Select Edit > Delete. you can discard it or add it back under the same or a different media ID. click OK. see “Deleting a volume group” on page 544. select the volumes that you want to delete. In the Delete Volumes dialog. Before you delete and reuse or discard a volume. The time of the assignment appears in the Time Assigned column for the volume in the Volumes pane. ■ . as follows: ■ For regular backup volumes. select Media and Device Management > Media.

The procedure depends on whether the volume is a data backup volume or catalog backup volume. You can still use the data on the volume by importing the backups into NetBackup (if the volume has not been overwritten). After you expire a volume. be certain that the volumes do not have any important data. and so on). The following example assumes only one NetBackup server exists and expires all the backups on media ID ABC001: bpexpdate -d 0 -m ABC001 . You can expire backups regardless of the volume state (Frozen. see “Importing expired images” on page 336 or “Importing images from Backup Exec media” on page 337. To import backup images. NetBackup can reuse the volume. NetBackup deassigns it and does not track the backups that are on it. If you do. See the following two sections for instructions. you can delete it. Suspended. or you can change its volume pool. NetBackup Enterprise Server only: specify hname only if your configuration uses master servers and media servers. Deassigning NetBackup regular backup volumes NetBackup deassigns a regular backup volume when the retention period for all backups on the volume expire.536 Media Volume operations To determine which application currently uses a volume. If you are uncertain. check the Application column of the Volumes pane. Deassigning NetBackup volumes Caution: Symantec recommends that you do not deassign NetBackup volumes manually. You can expire the backups on a volume by using the bpexpdate command on the master server. NetBackup does not erase those images. 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. If you expire the backup images on a volume. copy the images to another volume before you deassign the volume.

Media Volume operations 537 Deassigning NetBackup catalog backup volumes NetBackup tracks catalog backup volumes separately from regular backup volumes. Exchanging a volume and using a new media ID Use this procedure when: ■ ■ The volume contains current and valid NetBackup images. If you try to deassign Storage Migrator volumes manually. data may be lost. Past the maximum allowable number of mounts. 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. depending on whether you want to reuse the old media ID or not. you can delete it. For more information on how Storage Migrator manages its volumes. 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. Old (past the expiration date). . You require slots in the robotic library for additional backups. See “Moving volumes” on page 525. Storage Migrator deassigns a volume when the images are no longer required. to exchange a volume means to remove the volume from a robotic tape library). duplications. specify the CatalogBackup volume pool. Deassigning Veritas Storage Migrator volumes If a volume is assigned to Veritas Storage Migrator. Unusable (for example. you must wait for Storage Migrator to deassign it. or other purposes. see the Storage Migrator System Administrator’s Guide for UNIX. ■ ■ ■ The following are procedures for exchanging volumes. because of repeated media errors). remove it from the robotic library and move it to a stand-alone group. vault functions. or you can change its volume pool. To deassign these volumes. NetBackup can reuse the volume.

the relabel process puts the media in a known state. See “Adding volumes” on page 510. and the mode is known to be compatible with the drives in the robotic library. serious operational problems and a possible data loss may occur. Physically add the new volume to the storage device. 3 Exchanging a volume and using the old media ID This procedure allows you to reuse the same media ID. The external media label matches the recorded media label. Reuse a media ID only if all data on the old volume is not required and you recycle or discard the volume. specify a new media ID. See “Changing volume properties” on page 518. See “Adding volumes” on page 510. 2 3 4 5 . Set a new expiration date for this volume. 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. volume pool. If you add a new volume. and the media type). See “Deleting volumes” on page 534. including the old media ID. See “Labeling media” on page 522. Do not delete the volume entry for that media ID in case you need to retrieve the data on the volume. Optionally. Physically replace the old volume. Caution: If you exchange a media ID for a volume that has unexpired backup images. Logically add the new volume to the NetBackup volume configuration and specify the same attributes as the old volume. relabel the volume. which may be convenient in some instances.538 Media Volume operations 2 Add a new volume or move an existing volume in as a replacement for the volume you removed. Specify the same values for the other attributes as the removed volume (such as robotic residence. Although you do not have to relabel the volume.

6 7 . move it to stand-alone. Delete the volume entry. If the volume is in a robotic library. you must adjust the value to account for previous mounts. See “Adding volumes” on page 510. Record the current number of mounts and expiration date for the volume. 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. Recycling volumes using a new media ID Recycle a volume if it is a duplicate of another volume with the same media ID. you must deassign the volume. 1 2 3 4 5 Physically remove the volume from the storage device. Set the expiration date to the value you recorded in step 3. you can use either the existing media ID or a new media ID. For procedures. Otherwise. 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) . Add a new volume entry and physically add the volume to the storage device. See “Changing volume properties” on page 518. you may encounter serious operational problems and a possible loss of data.(the value that you recorded in step 3) Because NetBackup sets the mount value to zero for new volume entries. See “Deleting volumes” on page 534. Caution: Recycle a volume only if all NetBackup data on the volume is no longer needed or if the volume is damaged and unusable. Also recycle a volume if you change how you name volumes and you want to match the barcodes on the volume.Media Volume operations 539 Recycling volumes If you recycle a volume. see “Deassigning volumes” on page 535. To recycle a volume that contains unexpired backup images. See “Moving volumes” on page 525.

The default pool to which all backup images are written (unless you specify otherwise). You also can configure a scratch pool from which NetBackup can transfer volumes when a volume pool has no volumes available. You can also move volumes between pools. Adding a new volume pool Use the following procedure to add a new volume pool. groups. add volumes to it by adding new volumes to NetBackup or by changing the pool of existing volumes. without a pool assignment). ■ ■ ■ You can add other volume pools. . see “Volume pool and volume group overview” in the NetBackup Administrator’s Guide for Windows. as you add volumes to use with an application. you can add a volume pool for each storage application you use. for the volumes that are not assigned to a pool. CatalogBackup. see “Using WORM volume pools to manage WORM media” on page 590. you add them to that application’s volume pool. A volume pool protects them from access by unauthorized users. None. See “Scratch pool” on page 543. you assign them to one of the volume pools (or assign them as stand-alone volumes. When you add media to NetBackup. Volume II For more information about WORM media. select Media and Device Management > Media. The following are volume pool operations: ■ ■ ■ “Adding a new volume pool” on page 540 “Changing the properties of a volume pool” on page 541 “Deleting a volume pool” on page 543 For more information. for DataStore use. for NetBackup catalog backups. Then. DataStore. After you add a new pool. NetBackup creates the following volume pools: ■ NetBackup.540 Media Volume pool operations Volume pool operations NetBackup groups volumes that are used for the same purpose into volume pools. or applications. For example. To add a volume pool 1 In the NetBackup Administration Console. During installation.

either when you add a new pool or change an existing one. see “Volume pool properties” on page 541. In the New Volume Pool dialog. For descriptions of the properties. To change a volume pool 1 2 3 4 In the NetBackup Administration Console. change the attributes for the volume pool. For descriptions of the properties. specify the attributes for the volume pool. Select a pool from the pools in the Volume Pools list. The properties you can change include the pool type (scratch pool or catalog backup pool). see “Volume pool properties” on page 541. .Media Volume pool operations 541 2 3 Select Actions > New > New Volume Pool. Volume pool properties The following sections describe the properties you can configure for volume pools. Changing the properties of a volume pool Use the following procedure to change the properties of a volume pool. select Media and Device Management > Media > Volume Pools. In the Change Volume Pool dialog. Select Edit > Change.

This check box creates a dedicated catalog backup pool to be used for NBU-Catalog policies. if you lower the Maximum number of partially full media value. you may exceed the Maximum number of partially full media value. and so on. Also. suspended. Frozen. Description A brief description of the pool. NetBackup queues backup jobs until media becomes available. Volume pool names are case sensitive. For example. if you have 10 drives and want to reserve two for restore operations. This option lets you maximize your media usage. you may exceed the limit. If all of the media is in one pool. NetBackup uses all of the partially full media until the limit is reached. if you unfreeze or unsuspend the media that are partially full. see “Configuring server groups for media sharing” on page 614. Maximum number of partially full media Does not apply to the None pool. NetBackup writes data to the media until they are full. A dedicated catalog volume pool facilitates quicker catalog restore times. NetBackup can use the two other drives for restore operations even while backups occur. which does not limit the number of full media that are allowed in the pool. or scratch volume pools. 20 character maximum. assigns other media to which it writes data until they are full. If you exceed the Maximum number of partially full media value. set the Maximum number of partially full media to 8.542 Media Volume pool operations Catalog backup Select this option to use this volume pool for hot. and imported media do not count against Maximum number of partially full media. NetBackup writes data only to the number of partially full media. NetBackup uses only 8 drives to write backup data. Pool name The name for the new volume pool. Multiple catalog backup volume pools are permitted. This option also lets you control how many drives are used for backup jobs. If a media becomes full. The default value is zero. . NetBackup assigns another media for use if one is available in the pool or in a scratch pool. online backups of the NetBackup catalog. catalog backup pools. When the number of partially full media is reached. Enter or specify the number of partially full media to allow in the volume pool. For more information about server groups. Therefore.

Ensure that the volume pool is empty. delete them. 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. 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.Media Volume pool operations 543 For information about the characters you can use in a name. Answer the confirmation dialog. There can be only one scratch pool configured. Select Edit > Delete. see “NetBackup naming conventions” on page 629. select Media and Device Management > Media > Volume Pools. 3 . change the pool name for any volumes in the pool. 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. 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. If the pool is not empty. Select a volume pool from the pools in the Volume Pools list. NetBackup returns it to the scratch volume pool if it was assigned from the scratch pool. Scratch pool Select this option to use the pool as a scratch pool. If the volumes are not needed.

The following are the volume group operations you can perform: ■ “Deleting a volume group” on page 544 Deleting a volume group You can delete a volume group. If the Time Assigned column contains a value. The robotic inventory information is used to track the location of media. the volume is assigned. You cannot delete the group until these volumes are deassigned by the application. see the following: . In the volumes list. Select Edit > Delete. For more information. Select a volume group in the tree pane. 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. select Media and Device Management > Media. The location can be either the robot in which the volume resides. In the confirmation dialog box.544 Media Volume group operations Volume group operations The volume group shows the location of the volume. confirm the action. To inventory the robots without barcode readers or the media without readable barcodes. see “Using the physical inventory utility” on page 572. Remove the deleted volumes from the storage device. verify that all of the volumes in the group are unassigned. However. see “Deassigning volumes” on page 535. stand-alone. updates the NetBackup volume configuration (that is. or off-site if you use the NetBackup Vault option. To delete a volume group 1 2 In the NetBackup Administration Console. 3 4 5 6 Robot inventory operations Robot inventory does the following: ■ ■ ■ Queries robots about their media Provides reports about that media Optionally. To deassign a volume.

use a robot inventory to update the NetBackup volume configuration. Determine the contents of a robot Determine whether new media have barcodes before you add them to NetBackup . move. you can use the Update volume configuration option to update the volume configuration if necessary. NetBackup media ID) The update creates media IDs (based on barcodes or a prefix that you specify). or remove volumes in a robot. An inventory is a logcal operation. Use the Preview changes option. which compares the contents of the robot with the NetBackup volume configuration information.Media Robot inventory operations 545 ■ ■ ■ ■ “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. use the Compare contents with volume configuration option. Table 9-1 Action Robot inventory criteria Inventory option to use Add new volumes to a robot (a new For any robot NetBackup supports. After you physically add. After you examine the results. Use the Show contents option to determine the media in a robot and possibly their barcode numbers. Determine if volumes have been moved physically within a robot For robots with barcode readers and that contain media with barcodes. use the Update volume is one that does not have a volume configuration option.

If the robotic library supports barcodes and the volume has a readable barcode. NetBackup updates the NetBackup volume configuration information. 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 525 “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. You must specify the volume group to assign the volume to. use the Update volume configuration option. NetBackup cannot update the entries and writes an “Update failed” error. See “Example 6: Moving existing volumes between robots” on page 587. use the Update volume configuration option. robot number. and slot location. use the Update volume configuration option. NetBackup also updates the robot host. NetBackup updates the residence information to show the new robotic or stand-alone location. If the robot does not support barcodes or the volumes do not have readable barcodes. NetBackup updates the residence information to show the new robotic location. robot type. . If the robots do not support barcodes or the volumes do not have readable barcodes.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. 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. 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 525 “Using the physical inventory utility” on page 572 For either operation.

see “Volume configuration update examples” on page 579. If differences exist. NetBackup updates the residence information to show the new slot location. Displays the media in the selected robotic library. To inventory the robots without barcode readers or the media without readable barcodes. If the robot does not support barcodes or the volumes do not have readable barcodes. If differences exist. Compares the contents of a robotic library with the contents of the EMM database. NetBackup recommends changes to the NetBackup volume configuration. Compares the contents of a robotic library with the contents of the EMM database but does not change the database. Compare contents with volume configuration. see “Using the physical inventory utility” on page 572. does not check or change the EMM database. use the Update volume configuration option to update the NetBackup volume configuration information. Preview volume configuration changes. ■ ■ ■ For examples of different volume configuration updates. NetBackup updates the database to match the contents of the robot. . Update volume configuration.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. Inventory a robot The following are the robot inventory options you can select using the NetBackup Administration Console: ■ Show contents. 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 525 “Using the physical inventory utility” on page 572 See Example 7: Adding existing volumes when barcodes are not used. Compares the contents of a robotic library with the contents of the EMM database. 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.

4 5 Robot Inventory dialog box The following are the options you can configure for a robot inventory. Click Start to begin the inventory. select Media and Device Management > Media > Robots.548 Media Robot inventory operations To inventory a robot 1 2 3 In the NetBackup Administration Console. Select Actions > Inventory Robot. . For information about the options you can specify. Device host contains the name of the host that controls the robot and Robot contains the selected robot. Select the robot you want to inventory. Specify the options for the inventory. In the Robot Inventory dialog. see “Robot Inventory dialog box” on page 548.

For most configurations. Figure 9-3 Compare contents report (API robot) Device host The host that controls the robot. the results show only whether a slot contains a volume. If the robot can read barcodes. For API robots. you can specify the device host. from which you can configure more options. See “Advanced Robot Inventory Options dialog” on page 555. . In NetBackup Enterprise Server. This option does not change the database. Compare contents with volume configuration Inventories the selected robot and compares its contents with the contents of the EMM database.Media Robot inventory operations 549 Advanced options Active if you select Update volume configuration. You should only change the settings if your configuration has special hardware or usage requirements. The following figure shows a sample compare report. If the robotic library cannot read barcodes. do one of the following: ■ ■ Physically move the volume. the default settings work well. Opens the Advanced Robot Inventory Options dialog. Update the EMM database by using Actions > Move or by using the Update volume configuration option. If the results show that the EMM database does not match the contents of the robotic library. the media ID and media type in the EMM database are compared to the information received from the vendor’s robotic library software. the barcodes on the media are compared to the barcodes in the EMM database.

the ejected volumes may be injected back into the robotic library. The volumes to be injected must be in the media access port before the operation begins. you are not prompted to place volumes in the media access port. To inject volumes in the robot’s media access port into the robot before you begin the update. If you select Empty media access port prior to update and the MAP is empty. Preview changes Previews the update without changing the EMM database. Possible causes may be changes that occur between the preview and the update. . If you select Preview changes and any recommended changes are found. Otherwise. Note: If you ejected volumes from the robot by using NetBackup. If you click Yes. This option lets you ensure that all new media have barcodes before you add them to the EMM database. Changes can be to the state of the robot. to the media type mappings. the update results may not match the results of the preview operation. you do not have to perform a separate Update volume configuration operation. remove the volumes from the media access port before you begin an inject operation. You can review the changes before you update the volume configuration. to the barcode rules. select Empty media access port prior to update. if the inject port and eject port are the same. a dialog box asks if you want to accept the recommended changes. and so on. Caution: If you preview the configuration changes first and then update the EMM database. to the EMM database.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.

. Shows if each slot has media. Show contents Inventories the selected robotic library and generates a report. this operation does not check or change the EMM database. the results include the barcode from each volume. The results for other API robots are similar. The contents that are displayed depend on the robot type. Robot does not have a barcode reader or robot does not contain media with barcodes. Shows a list of volumes in the robot. Use this option to determine the contents of a robot. as follows: Type of robot Robot has a barcode reader and the robot contains media with barcodes. API robot. 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.Media Robot inventory operations 551 Figure 9-4 Update volume configuration results (not an API robot) Robot The robot to inventory. Report contents Shows if each slot has media and lists the barcode for the media. For robots other than API robots that have a barcode reader.

The ACS media type. The mapping between the ATL media type and the corresponding Media Manager media type (without considering optional barcode rules). The NetBackup Media Manager media type. show: ■ The volume serial number (volser). The mapping between the ACS library software media type and the corresponding NetBackup Media Manager media type (without considering optional barcode rules). ■ ■ ■ TLM robots NetBackup Enterprise Server topic. received from ACS library software. The Media Manager media type. The results. ■ ■ ■ TLH robots NetBackup Enterprise Server topic. The ATL media type. The NetBackup media ID corresponds to the ACS library software volume ID. shows: ■ The ACS library software volume ID. The Media Manager media ID corresponds to the ATL volser. . The results. received from the Automated Tape Library (ATL) library manager.552 Media Robot inventory operations Figure 9-5 Show contents report (API robot) ACS robots NetBackup Enterprise Server topic.

For robots without barcode readers or for volumes without readable barcodes. If differences exist. For a new volume (one that does not have a NetBackup media ID). see “Advanced Robot Inventory Options dialog” on page 555. see “Using the physical inventory utility” on page 572. NetBackup updates the database to match the contents of the robot. Check the barcode capabilities of the robotic library and the volume by comparing the robot contents with the NetBackup volume configuration. For API robots. The the mapping between the DAS/SDLC media type and the corresponding Media Manager media type (without considering optional barcode rules). You should consider using the vmphyinv physical inventory utility to add the media. ■ ■ ■ Update volume configuration Inventories the selected robot and compares its contents with the contents of the EMM database. the update returns an error if the volume serial number or the media ID contain unsupported characters. received from the DAS/SDLC server. determine the following: ■ ■ If the robotic library supports barcodes If any new volume inserted into the library has readable barcodes. the new media IDs are based on a media ID prefix that you specify.Media Robot inventory operations 553 The results. shows ■ The volume serial number (volser). Determining robot capabilities before you update the volume configuration Before you update the volume configuration. the update creates a media ID. The DAS/SDLC media type The Media Manager media type. . The media ID depends on the rules that are specified on the Advanced Robot Inventory Options dialog. For more information. 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. The Media Manager media ID corresponds to the DAS/SDLC volser.

Figure 9-6 Update volume configuration report (API robot) . Example update volume configuration reports The following figure shows example results for a robotic library that is not an API robot. save the results of the compare operation. If the robotic library does not support barcodes or the volume does not have readable barcodes. Results for other API robots are similar to this report. Note: You can select a device host only with NetBackup Enterprise Server.554 Media Robot inventory operations See “Compare contents with volume configuration” on page 549. The following figure shows example results for an ACS robot. The results can help you determine a media ID prefix if you use the Advanced Options Media Settings tab to assign a prefix.

Create barcode rules. If you do not map media. For more information See “Media Settings tab” on page 555. Map media for API robots. Create media ID generation rules. See “Barcode Rules tab” on page 561. See “Media Type Mappings tab” on page 566.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. default media types are used. See “Media ID Generation tab” on page 565. 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 .

see “Media Type Mappings tab” on page 566. 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. Specifying media type when not using barcode rules The following are the choices: ■ DEFAULT. For instructions for specifying media types for API robots. .556 Media Robot inventory operations ■ Specify media options for new media Media type Media type is always set to DEFAULT for API robots. Specifies the type for new media that are added to a robot. The list includes the media types that are valid for the robot.

Media Robot inventory operations 557 ■ A specific media type. Tape Library 4MM (TL4) Tape Library 8MM (TL8) 4MM cartridge tape. 1/2-inch cartridge tape 3 8MM cartridge tape. Also supports 1/2-inch cartridge tape 2 and 1/2-inch cartridge tape 3. For example. 8MM cartridge tape. 1/2-inch cartridge tape 1/2-inch cartridge tape 2. To let barcode rules determine the media type that is assigned. Each media type to be added should have a barcode rule. select DEFAULT. 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. 8MM cartridge tape 2. Specifying media type when using barcode rules The following are the choices: ■ DEFAULT. select a specific type. If the robot supports multiple media types and you do not want to use the default media type. assume you want to add DLT and half-inch cartridges to a TLD robot with a single update operation. Tape Library DLT (TLD) DLT cartridge tape. Also supports write-once read-many (WORM) operations. 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. First create separate barcode rules for DLT and half-inch cartridges and then select the specific media types when you . Also supports 8MM cartridge tape 2 and 8MM cartridge tape 3. select a specific type. 8MM cartridge tape 3 DTF cartridge tape 1/4-inch cartridge tape Tape Stacker Half-inch (TSH) 1/2-inch cartridge. Also supports the following: ■ ■ ■ ■ ■ DLT cartridge tape 2 and 3.

select a specific media type on the Media Settings tab. 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 Barcode rule media type DEFAULT DEFAULT DLT DLT_CLN DLT DLT_CLN DEFAULT 8MM. NetBackup assigns the default media type for the robot. Finally. select DEFAULT on the Media Settings tab.558 Media Robot inventory operations create the barcode rules. the barcode rule media type must be the same as the media or be DEFAULT. ■ To use a media type other than the default. select DEFAULT for the barcode rule media type when you create the barcode rule. select a specific media type from the list. the barcode rule does not match the media (except for cleaning media). You can perform one update for DLT and another for half-inch cartridge. If you specify any value other than DEFAULT on the Media Settings tab. Second. First. Note: If you choose DEFAULT on the Media Settings tab and DEFAULT in the barcode rule. and the one barcode rule assigns the correct media type. 4MM. You can use one barcode rule to add media of different types. The correct media type is assigned to each media. If not. such as DLT and half-inch cartridges (HCART) to a TLD robot. and so on DEFAULT DLT DLT_CLN Rule matches? Yes Yes Yes Yes No Yes Yes No Yes Yes Yes Media type added to volume configuration DLT HCART DLT DLT_CLN DLT_CLN DLT_CLN DLT_CLN DLT DLT DLT DLT_CLN .

NetBackup generates a new volume group name. 4MM. For another example. ■ ■ The media type for the barcode rule is cleaning media (DLT_CLN). ■ Other choices may be available. NetBackup automatically generates a new volume group. In the seventh. DEFAULT. depending on the setting of the Media type field. you specify the cleaning media on the Media Settings tab and specify default when you configure the barcode rule. The list always contains the following choices: ■ ■ AUTO GENERATE. The barcode matches a barcode tag. see “Example 5: Adding cleaning tapes to a robot” on page 586. The media are not assigned to a volume group. in this example). If the Media type is: ■ DEFAULT. the volume is added to that group. you specify the cleaning media type on the Media Settings tab and in the barcode rule. NO VOLUME GROUP. For more information about barcode rules. In the sixth row. ■ . If there is an existing group with a compatible residence for the volume. The sixth row and seventh row in the table show how to add only a cleaning tape. The following conditions all must be true: ■ The media type on the Media Settings tab is for regular media (DLT. the list includes the volume groups that are valid for the specified media type.Media Robot inventory operations 559 Media type on Media Settings tab DEFAULT Barcode rule media type 8MM. If a suitable volume group does not exist. Other than DEFAULT. and so on Rule matches? No Media type added to volume configuration Depends on robot type The fourth row in the table shows how both cleaning cartridges and regular volumes are added using one update operation. 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 includes the volume groups that are valid for the robot’s default media type. see “Barcode Rules tab” on page 561.

you must add an API_BARCODE_RULES entry to the vm. If there is an existing group with a compatible residence for the volume. NetBackup generates a new volume group name. Symantec recommends a DEFAULT setting. For more information about media types.560 Media Robot inventory operations To specify a volume group other than DEFAULT. If the Media type is: ■ DEFAULT. a prefix is not required because NetBackup creates media IDs automatically. the new update fails: volumes of different media types cannot have the same volume group. . 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). enter a volume group name or select from the list. If you specify a volume group and volumes of different media types have been moved into or within the robot. For more information about media types. To enable barcode rule support for API robots. enter a volume group name or select from the list. Tip: If the robotic library contains multiple media types. For more information about barcode rules. the list includes the volume groups that are valid for the robot’s default media type. the list includes the volume groups that are valid for the specified media type. see “Media type” on page 556. depending on the setting of the Media type field. Use the following Media ID prefix If the robot supports barcodes and the volume has readable barcodes. If a suitable volume group does not exist.conf file. DEFAULT. Use barcode rules Specifies whether or not to use barcode rules to assign attributes for new media. Other choices may be available. The list always contains the following choices: ■ ■ AUTO GENERATE. see “Barcode Rules tab” on page 561. see “Media type” on page 556. ■ To specify a volume group other than DEFAULT. the volume is added to that group. Other than DEFAULT. NetBackup automatically generates a new volume group.

conf file. 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. this volume pool setting always overrides the rule. ■ ■ A specify volume pool. If you select DEFAULT and are: ■ Using barcode rules.Media Robot inventory operations 561 You should specify a Media ID prefix for any new media if either of the following conditions exist: ■ ■ The robot does not support barcodes. see the following: ■ ■ “About labeling NetBackup volumes” on page 512 “vm. Other prefixes if they are configured in the vm.conf file. The following are the choices: ■ DEFAULT. . If you select NOT USED. Volume II Volume pool Specifies the volume pool for the new media. The actions depend on whether you use barcode rules to assign media attributes. DEFAULT. The volume that was inserted does not have readable barcodes. NOT USED may be useful if you use barcoded volumes and want updates to fail when unreadable or missing barcodes are encountered. ■ ■ NOT USED.conf options for media servers” in the NetBackup Administrator’s Guide for Windows. ■ To specify a media ID prefix for more information. Uses the letter A if no MEDIA_ID_PREFIX entries are defined. NetBackup assigns data tapes to the NetBackup pool but does not assign cleaning tapes to a volume pool. If you select DEFAULT. If you use barcode rules. NetBackup: ■ The following are the choices in the pick list: ■ Assigns the last MEDIA_ID_PREFIX entry as the default prefix if MEDIA_ID_PREFIX entries are defined in the vm. Not using barcode rules. the operation succeeds only if the robot supports barcodes and the volume has readable barcodes. the barcode rules determine the volume pool to which new volumes are assigned.

You can select and delete multiple rules with one operation. and then change the rule in the Change Barcode Rule dialog box. The barcode tag can have from 1 to 16 characters but cannot contain any spaces. You can select and change multiple rules with one operation. and then click OK in the confirmation dialog. For more information about barcodes. . see “Barcode overview” in the NetBackup Administrator’s Guide for Windows. select the rule. Volume II Barcode tag The barcode tag is a unique string of characters from the barcode that identifies the type of media.562 Media Robot inventory operations These rules are used when you specify Use barcode rules on the Media Settings tab. You must first delete the old rule and then add a rule with a new barcode tag. the Change Barcode Rule dialog appears for each rule that you selected for change. To change a rule. 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. you can use CLND as the barcode tag for the rule for DLT cleaning media. click Change. To delete a rule. select the rule. click New and then configure the rule in the dialog box. if you use CLND for DLT cleaning media. click Delete. You cannot change the barcode tag of a barcode rule. For example. To add a rule.

. For example. see “Specifying media type when using barcode rules” on page 557. 0 means the cleaning tape is not used. Description A description of the barcode rule. DEFAULT. Note: When a media type is selected. If you specify any value other than DEFAULT on the Media Settings tab. it may revert to 0 for unlimited when you select a non-cleaning media type. The media type that is specified on the Media Settings tab always overrides the media type of the barcode rule.Media Robot inventory operations 563 The following are special barcode rules that can match special characters in the barcode tags: ■ NONE. However. You can enter from 1 to 25 characters. this tag matches when none of the other barcode tags match. the maximum mounts value may revert to the default value for the specified media type. use barcodes for your cleaning media that cannot be confused with barcodes for data media. You must first delete the old rule and then add a rule with a new barcode tag. the barcode rule media type must be the same as the media or be DEFAULT. Media type The media type to assign to the media. Use the Media Settings tab to set up the criteria for a robot update. See “Media Settings tab” on page 555. For cleaning tapes. For volumes with barcodes. Matches when rules are used and the volume has an unreadable barcode or the robot does not support barcodes. the barcode rule does not match the media (except for cleaning media). For data volumes. a value of 0 means the volume can be mounted an unlimited number of times. Max mounts The maximum number of mounts (or cleanings) that are allowed for the volume. the following must be compatible: the media type in the DEFAULT rule and the media type on the Media Settings tab. For more information. ■ You cannot change the barcode tag of a barcode rule. If not. To avoid a value of 0 for cleaning tapes.

the volume is assigned to the pool you specify in this Volume pool setting. NetBackup uses the default media type for the robot. If you specify DEFAULT. the robot inventory update may add media with media types inconsistent with the vendor media types.564 Media Robot inventory operations 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. . Avoid this problem by grouping barcode rules by media type. If you use a barcode rule and the Media Settings tab Volume pool field is set to: ■ DEFAULT. you must add an API_BARCODE_RULES entry to the vm. Note: If a barcode rule contains media types that are incompatible with vendor media types. 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. 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 Volume pool Specifies the volume pool for the new media. If you do not specify a media type on the Media Type Mappings tab. If you also select DEFAULT on the Media Settings tab. NetBackup uses the media type you select on the Media Type Mappings tab. To enable barcode rule support for API robots. the Media Manager default media type for the robot is used. 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.conf file.

To add a rule. 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 change a rule. and then click OK in the confirmation dialog. The Change Media ID Generation Rule dialog appears for each rule that you selected for change. select the rule. Media ID Generation tab To use media ID generation rules. . the robot must support barcodes and the robot cannot be an API robot. The default method uses the last six characters of the barcode label from the tape. Media ID generation rules lets you override the default media ID naming method. To change those properties. Barcode length The number of characters in the barcode for tapes in the robot. You can select and delete multiple rules with one operation. you must first delete the old rule and then add a rule. You cannot change the robot number or barcode length of a rule. To delete a rule. You can select and change multiple rules with one operation. click New and then configure the rule in the dialog box.Media Robot inventory operations 565 ■ A specific volume pool. click Change and then change the rule in the Change Media ID Generation Rule dialog. click Delete. the Volume pool setting on the Media Settings tab overrides this Volume pool setting. select the rule.

Numbers can be specified in any order. Any alphanumeric characters that are specified must be valid for a media ID. The characters prefixed by the pound sign (#) in a field result in that character being inserted in that position in the generated ID. 2 in a field extracts the second character (from the left) of the barcode. However. See “Adding mapping entries” on page 567. or TLM robot types on NetBackup Enterprise Server. For example. API robots are ACS. 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. the tab shows only the default media types. The mappings that are displayed are only for the robot type that has been selected for inventory.566 Media Robot inventory operations Media ID generation rule A rule consists of a maximum of six fields delimited by colons. The following table shows some examples of rules and the resulting media IDs. . it may be difficult to manage media if the label on the media and the generated media ID are different. TLH. Changes apply only to the current volume configuration update. 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.conf file does not exist or does not contain media mapping entries for that robot type and media type. You can use rules to create media IDs of many formats. Media Type Mappings tab This tab is available only for API robots. Numbers define the positions of the characters in the barcode that are to be extracted. The tab also shows any robot-specific media mappings you have added to the Media Manager configuration file If the vm.

select a Media Manager media type from the list of allowable choices.Media Robot inventory operations 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.conf file ACS mapping entries. If not. see “ACS_mediatype” in the “vm. click Reset to Defaults. add robot-specific media mappings to the vm.conf file on the host on which you are running the NetBackup Administration Console. Adding mapping entries The default media type mappings tab may not provide the wanted mappings.conf options for media servers” section of the NetBackup Administrator’s Guide for Windows. In the Change Media Mapping dialog. For more information about vm. To reset the mappings to the default. Click OK. Volume II .

you must first add the allowable mapping entries to the vm. HCART2. HCART2. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART.conf entry Maps the ACS 3490E to HCART the HCART2 media type.conf file. For example. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. The third column shows the media types to which you can map the defaults. 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.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. HCART2. HCART2. 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. To do so. HC3_CLN . HCART3 HCART. 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. DLT2 media type. including DLTIV Maps the TLH 3490E to HCART the HCART2 media type. HCART3 1/2-inch cartridge cleaning tape 2 (HC2_CLN) HC_CLN. HCART2. HC2_CLN. Maps ACS DLTIV to the DLT for all ACS DLT media types.

DLT2. DLT3 DLT. HCART2. HCART3 HCART. DLT3 HCART. HCART2. HC3_CLN SDLT SDLT_2 SDLT_4 SDLT_S1 SDLT_S2 DLT. DLT3 DLT. 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. DLT2.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. HCART2. DLT3 DLT. DLT2. HCART2. DLT3 . HCART2. HC3_CLN LTO_CLNU HC_CLN. HCART3 HCART. HCART3 HCART. HCART3 HCART. HCART2. DLT2. HC2_CLN. HC3_CLN LTO_CLN2 HC_CLN. HCART3 HC_CLN. HCART3 HCART. HCART2. HCART2. DLT2. HC2_CLN. HCART3 1/2-inch cartridge tape 3 (HCART3) HCART. HCART3 HCART. HCART2. DLT2. DLT2. HCART2. HCART3 HCART. DLT2. HC3_CLN LTO_CLN3 HC_CLN. HCART2. HCART3 HCART. HCART2. HC2_CLN. DLT3 DLT. DLT3 DLT. HC2_CLN. DLT3 DLT. HCART3 1/2-inch cartridge tape 3 (HCART3) HCART.

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. HCART2. HCART2. HCART3 HCART. DLT2. HC_CLN. HCART2. DLT_CLN. DLT3 HCART. HCART3 HCART. HC_CLN. HCART3 HCART. DLT2. DLT. DLT2_CLN. HCART3. HC3_CLN. HC3_CLN STK2P STK2W 1/2-inch cartridge tape 2 (HCART2) HCART. HC3_CLN STK1Y HC_CLN. HCART2. 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. DLT3. DLT2. HC3_CLN T10000CT T10000T1 T10000TS UNKNOWN (for unknown ACS media types) HCART. HCART2. HCART2. HCART3 HCART. HCART3. DLT_CLN. HCART2. HCART3 HCART. HC2_CLN. HCART3 . DLT2. HCART2. DLT2_CLN. HC2_CLN. HCART2. DLT3. DLT3_CLN 1/2-inch cartridge tape 2 (HCART2) HCART. DLT. HC2_CLN. 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. HC2_CLN. HCART2. HCART2. HCART3 HC_CLN. HC3_CLN. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. DLT3 DLT.

HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. HCART3 . 8MM2. HCART2. HCART2. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. OD_THICK is ignored for all other robotic inventory operations) Allowable media types through mappings HCART. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. 8MM2. HCART2.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. 8MM3 HCART. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. 8MM3 4MM 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. HCART3 1/2-inch cartridge tape 2 (HCART2) HCART. DLT3 8MM. HCART2. HCART2. HCART2. HCART2. DLT2. HCART2. HCART3 DTF 8MM. 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.

DVCM. CD. 8MM2. the inventory reports only the presence of media in a robotic library. Using the physical inventory utility For the robots without barcode readers or that contain media without barcodes. BETACAM. 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 . BETACAMCL. DLT2. TRAVAN. HCART2. 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. and DVCL. 8MM3 Note: The following TLM media types are not supported: OD_THIN. DLT3. For more information. VHS. More detailed information is required to perform automated media management. see vmphyinv in NetBackup Commands for Windows. Avoid this problem by grouping barcode rules by media type. AUDIO_TAPE.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. DLT. Note: API robots: If a barcode rule contains media types that are incompatible with vendor media types. D2. HCART3. the robot inventory update may add media with media types inconsistent with the vendor media types. 8MM.

or SAN media server. you cannot specify a new volume group for the media. ■ ■ When to use vmphyinv Use the vmphyinv utility to update the EMM database for NetBackup. It does not support the optical disk library (ODL) robot type. 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. When you move the media from robotic drives to stand-alone drives. You do not need to invoke vmphyinv from the host to which the drives are attached. Use the -u or -n option to specify the drive. Use the slot range or list option of vmphyinv to perform the inventory operation. You insert new media into a robotic library and no NetBackup volume records correspond to the media. Recognizes NetBackup. ■ ■ ■ ■ ■ ■ 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. Can be used to inventory a single media in a stand-alone drive. Works with shared drives (NetBackup Shared Storage Option). Backup Exec. Supports remote administration. media server. You do not need to add volume records to the EMM database. Supports all SCSI-based robot types (except optical disk libraries). and Veritas Storage Migrator media. ■ .Media Robot inventory operations 573 Features of vmphyinv The vmphyinv utility has the following features: ■ ■ Can be invoked from any master server. Backup Exec. and Veritas Storage Migrator (VSM) tape formats. Tries to use multiple drives in a robot even if the drives are attached to different hosts. the drive must contain media and it must be ready. Can be used with barcoded tape libraries because it verifies the contents of the media.

However. you can specify the maximum number of drives to use. determines the media ID. You do not know the IDs on the tapes. or slot ■ . For example. You cannot specify which drives to use. you insert 10 media from a different tape library in slots 11 to 20. ■ How vmphyinv performs a physical inventory For a physical inventory. If you do not want to inventory all of the media in a robot. and adds media records to the EMM database. volume group. vmphyinv mounts the media. You can inventory the robot or inventory a subset of media in the robot by using options in vmphyinv. Use the slot range or list option of vmphyinv to perform the inventory operation. 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. To use this option.574 Media Robot inventory operations ■ You insert some media that have unknown media IDs or globally unique identifiers (GUIDs) into a robot. Some of the media are misplaced and the EMM database does not reflect the correct physical location of these media. vmphyinv obtains a list of volume records for that robot and inventories each of the media in the list. Specify the number of drives by using the -drv_cnt drive_count option. NetBackup robot number with filter options. reads the tape header. you can specify a subset of the media by using filter options. the NetBackup configuration must contain a volume record that corresponds to the robot number in the EMM database for the robot. Some filter options are volume pool. The drives do not have to be configured locally. which lets you reserve drives for NetBackup backup or restore operations. 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).

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. the media are skipped and are not inventoried. media from a different robot or some other source are moved to a robot and the media ID on the tape is unknown. in -number 6 volume group mars. and in the NetBackup volume pool. NetBackup volume records must exist. you should specify the density carefully. To use these options. -rn 2 -v moon -rn 1 -rc1 2 -number 3 -rn 5 -pn NetBackup -v mars -rc1 2 Only media in robot 5. Media in slots 2. For example. you must specify the density (using the -d option). and 5 in robot 0. the NetBackup volume record does not need to exist in the EMM database. and 7 in robot 2. In these cases. if the -rn robot_number and -ml A00001:A00002:A00003 options are specified. Only media in robot 1 and slot range 2 to 4. NetBackup volume records must exist. vmphyinv cannot complete the mount and permanent drive failure can occur. Media in slots 3. 5. Note: For a robot that supports multiple media types. If any of these media do not belong to the specified robot. you can specify a slot range option or list option. . However. NetBackup robot number and a slot range or list. only the three specified media are inventoried. Sometimes. ■ NetBackup robot number and a list of media that belong to a specific robot. 3. 4. Media in robot 2 and in the volume group moon. 6. To use this option. If you specify the incorrect density.Media Robot inventory operations 575 range. With these options. slot range 2 to 7. 4. The following are some examples: Options specified -rn 4 -pn bear Media inventoried Only media in robot 4 and in the volume pool bear.

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. ■ ■ ■ Note: The default mount timeout is 15 minutes. The vmphyinv utility reads the tape header to determine the recorded media ID or globally unique identifier (GUID). The media type is specified as cleaning media in the volume record (such as 4mm_clean or dlt_clean). it issues a mount request to ltid. Cleaning media If the following conditions are all true. 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. on the local host or remote host depending on where the drive is attached. GUID is an identifier used by Veritas Storage Migrator and Symantec Backup Exec. vmphyinv does not generate a new record in the EMM database. and the EMM database does not contains a volume record that corresponds to the cleaning media. Media that is not recognized If the media is not NetBackup media. oprd. use the vmupdate command. The NetBackup Volume Manager starts a process. You use the slot range or list option. vmd. vmphyinv does not attempt to mount the media. Backup Exec media. You can specify a different mount time by using the -mount_timeout option. The vmphyinv utility communicates with oprd and sends the mount request to oprd. To generate volume records for that media. 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. After oprd receives the request. the media is unmounted and the next media is mounted. The robot contains cleaning media. ■ ■ ■ You do not specify the vmphyinv slot range or list option. The next media in the list is mounted. or Veritas Storage Migrator media. If the robot contains cleaning media and any of the following conditions are true.

(The media format column of the summary contains NetBackup database for NetBackup catalog tapes. The media type is changed only if the new media type belongs to the same family of media types as the old media type. and so on. ■ ■ ■ . Never changes the volume pool. Never unassigns an assigned NetBackup volume. If vmphyinv cannot determine if the media is cleaning media. You can accept or reject the changes. vmphyinv updates the EMM database.) This verbose information is written to stderr. it tries to mount the media until the mount request times out. tape alert flags. media type. 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. To save the information. Updates the EMM database After all the media are mounted and the tape headers are read. if the media is a catalog tape. Update criteria For valid media types. the contents of each tape. the media type DLT can only be changed to DLT2 or DLT3. vmphyinv: ■ Changes the residence fields and description fields of any NetBackup media record if those fields do not match the media header. Conditionally changes the media type of an unassigned NetBackup volume record. If you accept the changes. For example. Note: NetBackup may not detect the presence of cleaning media for all drives. vmphyinv displays a list of recommended changes. It uses the SCSI parameters (sense keys. redirect stderr to a file. and ADAMM_GUID of an assigned record. The description field is changed only if the media is Symantec Backup Exec or Veritas Storage Migrator media. and physical (SCSI) media types) returned by the robot. Some drives report the presence of cleaning media in a manner NetBackup cannot read.Media Robot inventory operations 577 The vmphyinv utility tries to determine if the media is cleaning media.

vmphyinv creates a new NetBackup record that corresponds to the Backup Exec media. If the media ID does not exist. If the BackupExec pool does not exist. vmphyinv does the following: ■ In the NetBackup record. vmphyinv creates a new NetBackup volume record that corresponds to the NetBackup media. For each NetBackup volume record. If a media GUID does not exist. Updating Veritas Storage Migrator media The vmphyinv utility searches the EMM database. vmphyinv may use an existing NetBackup volume record if the record does not correspond to any media in the tape library. If a media GUID does not exist. It checks if the media ID from the tape is present in the media ID field of any record in the EMM database. vmphyinv updates the NetBackup volume record that corresponds to the the media ID. It checks if the media GUID from the tape is present in the ADAMM_GUID field of any record in the EMM database. The vmphyinv utility may use an existing NetBackup volume record if the record does not correspond to any media in the tape library. If the media ID exists. vmphyinv creates it. If a media GUID exists. vmphyinv updates the NetBackup record that contains the GUID. Changes the volume pool of the unassigned NetBackup volume records that are associated with Backup Exec media to the BackupExec pool. Each record is assigned to NetBackup (if not already assigned) and its state is set to Frozen in the EMM database.conf file. If a media GUID exists. vmphyinv does the following: . updates the ADAMM_GUID field with the GUID and the Description field with the Backup Exec cartridge label in the tape header. Updating Backup Exec media The vmphyinv utility searches the EMM database. vmphyinv creates a new NetBackup record that corresponds to the Veritas Storage Migrator media. Adds the media ID of the NetBackup record to the EMM database (if not already present). ■ ■ Note: If a MEDIA_ID_PREFIX entry is not specified in the vm. For each NetBackup volume record. It checks if the media GUID from the tape is present in the ADAMM_GUID field of any record in the EMM database. NetBackup uses BE as the default prefix for Backup Exec media. vmphyinv updates the NetBackup record that contains the GUID.578 Media Robot inventory operations Updating NetBackup media The vmphyinv utility searches the EMM database.

The barcode of an existing volume record needs to be changed. If the StorageMigrator pool does not exist. Also updates the Description field with the Veritas Storage Migrator cartridge label in the tape header. The Storage Migrator database is not updated. ■ Duplicate media IDs are found. it is created. you must intervene to continue.Media Robot inventory operations 579 ■ In the NetBackup record. updates the ADAMM_GUID field with the GUID. It contains the same media ID as the media ID read from the tape header. ■ 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. A NetBackup volume record that belongs to a different robot is found. 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 . Changes the volume pool of the unassigned NetBackup records that are associated with Veritas Storage Migrator media to the StorageMigrator pool. These cases are reported as errors. media GUID. The media type. or volume pool of an assigned volume record needs to be changed. Error cases The vmphyinv utility may not be able to update the EMM database correctly in the following cases. ■ ■ ■ Volume configuration update examples The following examples show only the relevant volume attributes. If any of the following cases are encountered. Two or more media in the same robot have the same media ID.

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. media type volume group volume pool DEFAULT NONROB_8MM DEFAULT 3 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 . specify the following on the Media Settings tab. 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) 2 Assume that you remove the volume from the robotic library. It does not matter whether the robot supports barcodes.Not Robotic NONROB_8MM 0 (unlimited) . 1 The following are the attributes for media ID 800001. and then execute the update.

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) 2 Assume that you insert the volume into a TL8 robot. which has a readable barcode and already exists as a stand-alone volume. The media type and volume pool remain unchanged. see “Example 6: Moving existing volumes between robots” on page 587. The volume group is specified on the Media Settings tab. media type volume group use barcode rules volume pool DEFAULT EXB220 YES (selected) NetBackup . 1 The following are the volume attributes for media ID 800021. specify the following on the Media Settings tab. 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). and then execute the update.Media Robot inventory operations 581 The new residence information in the EMM database shows a stand-alone location in the volume group. The results are the same for a volume that does not have a barcode. you must do two separate updates. For procedures. Note: When you move volumes from one robot to another robot.

Therefore. barcode rules are ignored. . NetBackup updates the residence information in the EMM database to reflect the new robotic location.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 3 NetBackup recognizes that the media ID exists and changes the EMM database to reflect the new robotic location.Tape Library 8MM 0 1 shark EXB220 0 (unlimited) The barcode matches the barcode of an existing stand-alone volume in the configuration. Because the volume is not new. 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 . NetBackup does not create a new media ID.

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. 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 . media type volume group use barcode rules volume pool DEFAULT EXB220 NO (not selected) DEFAULT . specify the following on the Media Settings tab.Media Robot inventory operations 583 The only setting used on the Media Settings tab is the volume group for added or moved volumes.Tape Library 8MM 0 1 shark EXB220 0 (unlimited) 2 Assume that you move the volume to empty slot 10. NetBackup cannot properly recognize the move. which currently resides in slot 1 of the robotic library. 1 The following are the attributes for media ID 800002. and then execute the update. The media type setting was not used because this example was for a single existing volume that already had a media type. Otherwise. 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. The robot supports barcodes and the volume has a readable barcode.

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.584 Media Robot inventory operations 3 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 . Assume the following: ■ ■ ■ The new volume is an 8MM tape with a readable barcode of TL800002. 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.Tape Library 8MM 0 10 shark EXB220 0 (unlimited) The updated volume attributes show the new slot number. Media type Volume group Use barcode rules Volume pool DEFAULT EXB2220 YES (selected) DEFAULT 1 . but all other information is unchanged. No media generation rules are defined.

slot. robot type. and host. The volume pool and max mounts allowed are from the barcode rule. The new residence information in the EMM database shows the robot host. If barcode rules (or barcodes) had not been used. the media ID is from the last six characters of the barcode.Tape Library 8MM 0 1 shark EXB220 0 (unlimited) No media ID generation rules exist. the media description. and max mounts allowed would be set to the following defaults: .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 2 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 . Therefore. The volume group is from the Media Settings tab. robot number. volume pool.

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. NetBackup recognizes that DLT_CLN is the cleaning tape for DLT. Example 5: Adding cleaning tapes to a robot A special case exists when you add cleaning tapes. NetBackup does not add new media IDs. you must specify a Media ID prefix on the Media Settings tab. assume you are updating a TLD robot. Alternatively. NetBackup adds the cleaning tape CLN001 as DLT_CLN type media along with the regular volumes. For example. 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. If you do not. The media type of the DL barcode rule matches the Media type on the Media Settings tab. The tapes are added as DLT. This example shows NetBackup’s ability to add cleaning cartridges along with regular volumes when you use Update volume configuration. The cleaning tape matches the CLN barcode rule. . 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 2 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) 3 The barcodes on the regular tapes match the DL barcode rule. you can specify DEFAULT for the media ID.

■ The media type for the barcode rule is the correct cleaning media (DLT_CLN in this example). A TL4 robot supports media inventory (detects media presence). NetBackup is unable to update the entries and you receive an “Update request failed” error. and then to the new robot. Otherwise. Perform an Update volume configuration on robot 1. Caution: This procedure assumes that robot 2 is able to read barcodes and the volume has readable barcodes.Media Robot inventory operations 587 If the volumes you insert include a cleaning tape. To add only cleaning media. If not. . These updates move the volumes to stand-alone. Perform an Update volume configuration on robot 2. specify the cleaning media type on the Media Settings tab and in the barcode rule (DLT_CLN in this example). you must perform two separate updates. 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). as an intermediate step. 1 2 3 Remove the volume from robot 1. This updates the configuration to show the volume in robot 2. the problem in “Example 7: Adding existing volumes when barcodes are not used” on page 587 occurs. 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. The barcode on the volume matches a barcode tag (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. Insert the volume in robot 2. This updates the volume attributes to show the volume as stand-alone. but not barcodes.

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 . specify the following on the Media Settings tab.588 Media Robot inventory operations 1 The following are the attributes for media ID 400021. which already exists as a stand-alone volume.Not Robotic NONROB_4MM 0 (unlimited) 2 Assume that you insert the volume into the robot. media type volume group media ID prefix volume pool DEFAULT 00_000_TL4 C4 DEFAULT 3 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 . and then execute the update.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). Symantec recommends that you use checkpoint and restart for backups. For this situation. number. . However. Using WORM media WORM (Write-Once-Read-Many) media is used to protect key data from unwanted modification or to meet compliance regulations. NetBackup cannot identify the volume and assumes it is new. The information for the new media ID (C40000) shows the robotic location. SCSI pass-through paths are provided on the server platforms NetBackup supports. The media ID C40000 is generated from the media ID prefix specified on the Media Settings tab. NetBackup fails a job that uses WORM media and then retries the failed job. and host. NetBackup requires an SCSI pass-through drive to use WORM tape drives. see the NetBackup Device Configuration Guide. Without a barcode. The NetBackup QIC/WORM tape format is used for WORM media. NetBackup has job resume logic. which tries to resume a job that has been interrupted (for example. The old media ID (400021) remains in the configuration. Tape error recovery is disabled when using WORM media. The bplabel command labels only LTO-3 WORM tapes. See Using the physical inventory utility. Setting up SCSI pass-through paths may require special operating system configuration changes. The volume group and volume pool are configured according to the Media Settings tab selections. an interruption on the fibre channel). This format allows NetBackup to append images to WORM tape as can be done with standard tape. For details. slot. you should use the physical inventory utility. The maximum mounts allowed is set to the default (0). NetBackup uses SCSI commands to query drives. 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. NetBackup queries the drive to verify that drive is WORM-capable and that the media in the drive is WORM media. All other WORM media cannot be labeled because the label cannot be overwritten when the media is used. robot type. which includes the robot host.

symantec. For more information. To disable the volume pool name verification. two methods exist in NetBackup. If the drive contains WORM media and the media is not in a WORM volume pool. NetBackup writes the media as WORM. The first four characters must be WORM. To use Quantum drives for WORM media on Solaris systems. ■ ■ “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. Managing your WORM media in NetBackup To ensure that data that is intended for WORM media is written on WORM media. see the NetBackup Hardware Compatibility List on the Symantec support Web site: http://entsupport. NetBackup compares the first four characters of the volume pool name to determine if it is a volume pool that contains WORM media. Quantum lets NetBackup convert standard tape media to WORM media. If the drive contains standard media and the media is in a WORM volume pool. NetBackup freezes the media. For information about how to configure nonstandard tape drives and how to edit the st. Create a new volume pool and specify WORM (upper-case letters) as the first four characters of the pool name. see the NetBackup Device Configuration Guide. NetBackup freezes the media. see the following. ■ ■ .com All of the vendors. require the use of special WORM media.590 Media Using WORM media Supported drives For information about the drives that NetBackup supports for WORM media. except Quantum. This method allows a WORM-capable tape drive to back up and restore standard and WORM media. create the following touch file on the media server of the WORM drive: install_path\netbackup\db\config\DISABLE_WORM_POOLCHECK Note the following cases: ■ If the drive contains WORM media and the media is in a WORM volume pool. See “Adding a new volume pool” on page 540.conf file. you must modify the st.conf file.

put standard media in the scratch pool. For example. media is moved from the scratch volume pool into the WORM pool. you should ensure that the WORM volume pool does not run out of media to complete backup jobs. and verifies that the media is not currently assigned to a server. only one kind of media can be used as either standard media or WORM media. If a standard volume pool runs out of media and the scratch pool contains WORM media. For example. Using the Quantum drive When you use the Quantum drive. However. Symantec recommends that you add the most commonly used media to the scratch pool. If a WORM volume pool runs out of media. If the scratch pool contains standard media. verifies the media is unused or all images are expired. The opposite also is true. the . For example.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. because each drive is limited to backup and restores with a specific type of media. Using a scratch pool For all supported WORM-capable drives (except the Quantum drive). NetBackup configures the media as WORM media and continues with the NetBackup job. the scratch pool must only contain one type of media. 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. if most NetBackup jobs use standard media. After verification. NetBackup uses the media. This method lets you add both types of media in the scratch pool because NetBackup selects the correct media type for the drive type. optimal drive usage may not be achieved. NetBackup reads the tape label. For a standard media. standard backups may fail because appropriate media is unavailable. you can configure standard drives and media as HCART and WORM-capable drives and media as HCART2. If the WORM volume pool runs out of media. NetBackup determines whether the media is configured as standard or WORM 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.

NetBackup does not support resume logic with WORM tape. create the following touch file on the media server of the WORM drive: install_path\netbackup\db\config\DISABLE_WORM_POOLCHECK Using the Quantum drive Because Quantum drives use only a single media type. NetBackup restarts the job from the last checkpoint. WORM tape limitations The following are the current limitations when using WORM tape. you should disable the WORM volume pool name verification. WORM tape is not supported with NetWare media servers. ■ . To disable the volume pool name verification. If you do not use WORM volume pools to manage WORM media. NetBackup fails a job that uses WORM media and then retries the failed job. ■ ■ Third-party copy backups are not supported with WORM media. Alternatively. this method for managing your WORM media is unnecessary. if checkpoint and restart are used.592 Media Using WORM media WORM-capable drives cannot be used for backups with standard media even if no WORM backups are in progress. Symantec recommends that you use checkpoint and restart for backups.

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 614 “Configuring and managing disk pools” on page 617 “Configuring SAN clients and Fibre Transport” on page 618 “NearStore configuration” on page 739 “Managing your device configuration” on page 618 To manage your devices. To add and configure storage devices.Chapter 10 Devices Use Media and Device Management > Devices to add. see the following: ■ ■ ■ ■ “Stopping and restarting the Device Manager” on page 623 “Activating and deactivating media servers” on page 623 “Accessing media and devices on other hosts” on page 624 “The Enterprise Media Manager server” on page 625 Device configuration prerequisites Before you configure storage devices in NetBackup. see the following: ■ For more information about configuring and managing storage devices. and manage storage devices in NetBackup. configure. ensure that the following prerequisites are accomplished: .

download an updated device mapping file from the Symantec support Web site and configure NetBackup to use the updated file. The server platforms that NetBackup supports may require operating system configuration changes to allow device discovery. Note: The contents of this file do not indicate support for any of the devices. 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) 3 Use the tpext command to update the EMM database with the new version of the device mapping file. If the host on which you configure devices is not the Enterprise Media Manager server.TAR and Mappings_6_nnnnnn.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 Device Configuration Wizard also uses it during device discovery and configuration. NetBackup hosts are added automatically to the list of additional servers if the EMM server is running when the host is installed. no command-line parameters are required. add it to the NetBackup additional servers list. If the EMM server was not running. To do so. Refer to the README file that is supplied with the device mapping file for additional instructions.ZIP.com The files that you download are named similarly to the following files: Mappings_6_nnnnnn. you can add support for new or upgraded devices without waiting for a release update from Symantec. In some cases.symantec. use the nbemmcmd -addhost command to add the host. The following is the address for the site: http://entsupport. The tpext command resides in the following directory: . The NetBackup Device Configuration Guide provides information about how to configure device drivers for the systems that support NetBackup server software. To obtain the current device mapping file 1 Find the latest external types file for your devices on the Symantec support Web site. ■ The device mapping file NetBackup uses a file to determine which protocols and settings to use to communicate with storage devices. only the ability to recognize and automatically configure them.

■ “Using the Device Configuration Wizard” on page 595. Configuring robots and tape drives Several methods exist for adding and for configuring storage devices. For procedures. For device configuration examples. This action also stops and restarts any robotic processes. Using options in the NetBackup Administration Console. Therefore. ensure that backups are not active when you use the wizard. 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 . 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. see “Stopping and restarting the Device Manager” on page 463. Symantec recommends that you use the Device Configuration Wizard to add and configure the following types of devices: ■ ■ ■ ■ Robots. Using the Device Configuration Wizard Caution: The Device Configuration Wizard stops and starts the daemons and services. you can stop and restart ltid. For information about controlling ltid manually. Symantec recommends that you use the Device Configuration Wizard to add and configure devices.Devices Configuring robots and tape drives 595 ■ ■ /usr/openv/volmgr/bin (UNIX) install_path\volmgr\bin (Windows) 4 Stop and restart the NetBackup Device Manager. For procedures. see the NetBackup Device Configuration Guide. If you use this method. first add the robot and then add the drives that are in the robot. see “Stopping and restarting the Device Manager” on page 463. as follows:.

.x device hosts. 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. This conflict occurs when the NetBackup hosts you select to scan do not agree on which host stores device information.596 Devices Configuring robots and tape drives This wizard uses device discovery to add and configure devices automatically. See “The device mapping file” on page 386. partially-configured drives are shown as PCD and partially-configured robots as PCR in the Drives list.x media servers. When you scan devices. such as an unsupported robotic library or drive. see the appropriate operating system chapter of the NetBackup Device Configuration Guide. Devices that are partially-configured Some devices may be partially configured only. See “Devices that are partially-configured” on page 596. Changes may include those needed for device discovery. For more information. If you deselect a discovered device from the tree view in the wizard. the wizard may detect an EMM server conflict. Operating system changes To discover devices. this wizard uses device serialization. If you have partially-configured drives. For more information. For NetBackup 5. NetBackup issues SCSI pass-through commands to the devices in an environment. the device path is disabled. see “The Enterprise Media Manager server” on page 465. See “The device mapping file” on page 386. Possible EMM server host conflict The following topic applies only to NetBackup Enterprise Server environments that include NetBackup 5. In some cases. the wizard may leave some devices partially configured. The server platforms that NetBackup supports may require special operating system configuration changes. To perform these tasks. ensure that you have downloaded the most recent device mapping file from the Symantec support Web site.

Use the following procedures to add a robot manually. click OK. In the Add Robot dialog. see “Using the Device Configuration Wizard” on page 595. 4 5 . specify the properties for the robot. The properties you can configure depend on robot type. answer yes to stop and restarts the NetBackup Device Manager and any robotic processes. Select Actions > New > New Robot. To add a drive. After you specify properties. and robot controls selections you make in the dialog. host type. Adding a robot Note: Symantec recommends that you use the Device Configuration Wizard to add storage devices. To start the Device Configuration Wizard 1 2 In the NetBackup Administration Console. see “Adding or changing a drive” on page 604. Note: Any backups. For more information.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. When you add a robot and drives. select Media and Device Management. For descriptions of the properties. Click Configure Storage Devices. see “Robot properties” on page 598. At the stop and restart the NetBackup Device Manager prompt. Be sure to review the limitations of the wizard before you configure devices. or restores that are in progress also may be stopped. select Media and Device Management > Devices. archives. first add the robot as explained in the following procedure and then add the drives. To add a robot 1 2 3 In the NetBackup Administration Console.

ACSLS host ACSLS Host applies only to NetBackup Enterprise Server. This STK hardware serves as a proxy to another ACS library software component (such as. Specify the name of the Sun StorageTek ACSLS host. The ACS library software component can be any of the following: ■ Automated Cartridge System Library Software (ACSLS) For an example. host type. ACSLS). and robot control selections you make in the dialog. The properties you can configure depend on robot type. the ACS library software resides ACSLS host. ■ ■ . STK Library Station Storagenet 6000 Storage Domain Manager (SN6000). this host can also be a Media Server or EMM server. On some UNIX server platforms.598 Devices Configuring robots and tape drives Robot properties The following sections describe the robot properties you can configure. see the NetBackup Device Configuration Guide.

For an overview of ACS robots. For example. Device host Device Host applies only to NetBackup Enterprise Server. enter the name of the DAS/SDLC server. see the NetBackup Device Configuration Guide.154. enter the library name that is configured on the UNIX host. in the following example entry in that file. Specifies the host to which the device is attached. Use the same name that is configured on the AIX device host. For UNIX device hosts (except AIX). Obtain the appropriate LibAttach software from STK. see the NetBackup Device Configuration Guide. To specify the DAS server for TLM robots that are controlled by an ADIC DAS/SDLC server. See the Symantec support Web site for the latest compatibility information. DAS server NetBackup Enterprise Server only.Devices Configuring robots and tape drives 599 Note: STK LibAttach software must also be installed. Library name TLH robot on NetBackup Enterprise Server only. For an overview of TLM robots.conf file.141 ibmpc1 Enter the library name. This server is an OS/2 workstation near or within the robot cabinet or a Windows server near the ADIC Scalar library. see the NetBackup Device Configuration Guide. .123. To specify the LMCP file for TLH robot types. enter the name of the Library Manager Control Point device file name. For Windows devices hosts: ■ Determine the library name by viewing the C:\winnt\ibmatl. 3494AH is the library name: 3494AH 176. ■ For an overview of TLH robots. LMCP device file NetBackup Enterprise Server on AIX device host only. if the device host that has drives under ACS robotic control is a Windows server.

Bus. Robot control host NetBackup Enterprise Server only. 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. TLD. Specifies that a host other than the device host controls the robot. see “Robot control configuration overview” on page 602. enter the name of the host on which the robot information is defined. enter the Port. For this type of robot control. Target. enter the name of the NDMP host to which the robot is attached. Target. Specifies that an NDMP host controls the robot. click Browse and then select a robot from the list that appears in the Devices dialog. or TLH robots. 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. and LUN. Robot control is attached to an NDMP host NetBackup Enterprise Server only. Bus. Port. To specify the robot device. To specify the SCSI coordinates for the device. . and LUN Windows host only. Specifies the host that controls the robot. To specify the robot control host for TL8. For more information about robot control. For this type of robot control.600 Devices Configuring robots and tape drives NDMP host name To specify the host.

Bus. 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. For information about how to add device files. Target. enter the name of the robotic device that is attached to the NDMP host. Robot device path To specify the robot device path. see the NetBackup Device Configuration Guide. Enter either the Port. Bus. Target. and LUN numbers by using Windows management tools. Enter the path of the device file in the next dialog box. Specifies the device file used for SCSI connections. The device files are located in the /dev directory tree on the device host. TLD (21)) and is also used when you add media for the robot. 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. a dialog appears that lets you enter the information. You can find Port. click More. . For NetBackup Enterprise Server environments: ■ Robot numbers must be unique for all robots on all hosts in the configuration. an error dialog appears. Robotic device file UNIX device host only. click Other Device. and LUN numbers or the device name in the next dialog. If the browse operation fails to show all of the attached robots. If the browse operation fails for any other reason. To specify the robotic device file. If the browse operation does not find attached robots. logical identification number for the robotic library. click Browse and then select a robotic device file from the list that appears in the Devices dialog. regardless of the robot type or the host that controls them. This number identifies the robotic library in displays (for example.Devices Configuring robots and tape drives 601 If the discovery operation fails to discover a robot.

com SCSI coordinates (Windows host) The device attributes on Windows system cannot change during NetBackup operation. ■ Robot type Specifies the type of robot. The last column shows the configuration information that is required. ■ If you add a robot that is controlled by a remote device host. Robot control configuration overview In the Robot control section you specify the type of control for the robot. various combinations of the robot control buttons are available in the dialog. The following table provides an overview of robot control configuration. enter the Port. and LUN for the robotic device. use the same robot number on the hosts with the drives as you do on the host that has the robotic control. Solaris SPARC and HP-UX Robotic device file (except HPIA64). A Tape Library DLT robot is one that allows separate robotic control and drive hosts. Depending on the robot type and the type of media server. see the NetBackup Device Configuration Guide. if you have two robots. Bus. The first column indicates the robot control button that is valid for a particular robot type and server platform. specify the same robot number in all references to that library. see the Symantec support Web site: http://entsupport.602 Devices Configuring robots and tape drives For example. TLD . For an example. use the same robot number for that robot on all device hosts.symantec. Target. To specify the SCSI coordinates. use different robot numbers even if different hosts control them. TL8. To locate the robot type to use for specific vendors and models. That is. If the robot has its robotic control and drives on different hosts. UNIX Robotic device file Local TL4. Table 10-1 Robot control Local Robot control configuration overview Robot Type Supported media server platform Information required for configuration ODL AIX.

Bus. When you add the robot to the device configuration on shark. TL8. and Linux (except Linux64) LMCP device file Robotic device file Local Local TLH TSH Remote Remote Remote ACS TL8. Target. Solaris SPARC. When you add this robot to the device configuration on eel. TL8. HP Library name IA64.Devices Configuring robots and tape drives 603 Table 10-1 Robot control Local Robot control configuration overview (continued) Robot Type Supported media server platform Windows Information required for configuration Robot device or Port. and LUN TL4. and Linux64 All All All (except Solaris Opteron. One drive in the robot is connected to eel and the other is connected to the host shark. Linux. Figure 10-1 shows library sharing with two servers using two drives in a TL8 robot. select Robot is controlled locally by this device host. TLD. and TLD TLH Local All (except Solaris Opteron. select Robot control is handled by a remote host. HP-UX (except HP IA64). . The robotic control for the robot is on the host that is named eel. Host eel is the robot control host. AIX. AIX. and Linux. TLD TLH ACSLS host Robot control host Robot control host Remote TLM DAS/SDLC server NDMP ACS. and Linux64) AIX AIX. and TLH NDMP host name and robot device Library sharing example The following example applies only to NetBackup Enterprise Server. Linux64) All (except Linux64 and HP IA64) Windows. Solaris.

see “Configuring SCSI reserve on a drive path” on page 606. select Media and Device Management > Devices. Use the following procedures to add or change a tape or optical drive manually. see “Drive properties” on page 607. To configure SCSI reserve on a drive path. Select one of the following. The properties depend on the drive type and host server type. For descriptions of the properties. For more information. which also stops and restarts any robotic processes. If your changes are complete. see “Using the Device Configuration Wizard” on page 595. You can stop and restart the NetBackup Device Manager service. On Microsoft Windows systems: ■ . To add a shared drive. To add a drive 1 2 In the NetBackup Administration Console. depending on the type of drive: ■ ■ Actions > New > New Tape Drive Actions > New > New Optical Drive 3 Specify the properties of the drive. see “Adding a shared drive” on page 605.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 about using tpconfig in interactive mode. Alternatively. If you add a drive on multiple hosts. you can use the tpconfig command to add shared drives. it becomes a shared drive. On UNIX servers. ■ For information about the NetBackup Shared Storage Option. archives. If you use tpconfig. which can increase the chance for configuration errors. To change the status of the drive. If you stop and restart this service. ensure all hosts that share a drive use the same case-sensitive name for the drive.Devices Configuring robots and tape drives 605 answer yes to the stop and restart prompt. so the drive is available as soon as you add it and restart ltid. tpconfig interactive mode. see the NetBackup Shared Storage Guide. In the Change Tape Drive or Change Optical Drive dialog box. Use the -add -drive command when you define shared drives. To change a drive 1 2 3 In the NetBackup Administration Console. see NetBackup Commands for Windows. any backups. expand Media and Device Management > Devices > Drives. Use the tpconfig command as follows: ■ tpconfig command line interface. The tpconfig command does not use device serialization. Use the -path <drivepath> option with the -add -drpath command when you define multi-path drives. see “Using the Device Configuration Wizard” on page 595. see “Using the tpconfig device configuration utility” in the NetBackup Administrator’s Guide for UNIX and Linux. or restores also are stopped. Volume II. right-click on the drive you want to change and select Change from the shortcut menu. Adding a shared drive Symantec recommends that you use the Device Configuration Wizard to add storage devices. see “Drive properties” on page 607. you can use the tpconfig command in interactive mode. The properties depend on the drive type and host server type. For descriptions of the properties. change the properties of the drive. For instructions. . In the details pane. For more information. ■ The initial drive status is up. select Device Monitor. The Device Configuration Wizard is the easiest method for adding shared drives in a Shared Storage Option configuration.

choose one of the Override SCSI Reserve settings when you configure the path properties. The Enable SCSI Reserve host property is used to configure the protection for each media server. Volume II . Use the SCSI reserve protection setting configured for the media server. 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 . choose one of the Override SCSI Reserve settings. see “Enable SCSI reserve” on page 447.2 (SPC-2) standard. “How NetBackup reserves drives” in the NetBackup Administrator’s Guide for Windows. 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 . The following are the options for the Override SCSI Reserve settings drive path attribute: ■ Server Default. To configure the SCSI reserve host property. ■ ■ To configure SCSI reserve when adding a drive 1 2 In the New Tape Drive dialog box. click Add. In the Change Path dialog box. To configure SCSI reserve when changing drive properties 1 2 3 ■ In the Change Tape Drive dialog box. SPC-2 SCSI Reserve. you can override the media server setting.606 Devices Configuring robots and tape drives 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. For each drive path. Click Change.3 (SPC-3) standard. select the drive path. In the Add Path dialog box.

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 default frequency is zero. see “Robot attributes” in the NetBackup Device Configiration Guide. 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 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 properties you can specify depend on drive type. When the accumulated mount time exceeds the time you specify for cleaning frequency. NetBackup records the amount of time that volumes have been mounted in that drive. NetBackup does not support drive cleaning in some robot types. If you want to set up a frequency-based cleaning schedule for the drive. Cleaning frequency Applies to tape drive only. set the number of mount hours between each drive cleaning. server platforms. For more information. When you add a drive or reset the mount time to zero. or NetBackup server types.

create them as explained in the NetBackup Device Configuration Guide. see “Drive cleaning overview” and “Using TapeAlert” in the NetBackup Administrator’s Guide for Windows. Each drive name must be unique. For more information about drive cleaning. and drive support drive cleaning. If the entries do not exist. robot type. 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. NetBackup uses character-mode device files. you must configure the Robotic library and Robot drive number fields. Drive name The name that iden