Veritas NetBackup™

Administrator's Guide,
Volume I

UNIX, Windows, and Linux

Release 7.7.2
Veritas NetBackup™ Administrator's Guide, Volume
I
Documentation version: 7.7.2

Legal Notice
Copyright © 2015 Veritas Technologies LLC. All rights reserved.

Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies
LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their
respective owners.

This product may contain third party software for which Veritas is required to provide attribution
to the third party (“Third Party Programs”). Some of the Third Party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation
or TPIP ReadMe File accompanying this product for more information on the Third Party
Programs.

The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC
SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS
SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.
Veritas Technologies LLC
500 E Middlefield Road
Mountain View, CA 94043

[Link]

Made in Singapore.

10 9 8 7 6 5 4 3 2 1
Technical Support
Technical Support maintains support centers globally. Technical Support’s primary
role is to respond to specific queries about product features and functionality. The
Technical Support group also creates content for our online Knowledge Base. The
Technical Support group works collaboratively with the other functional areas within
the company to answer your questions in a timely fashion.
Our support offerings include the following:
■ A range of support options that give you the flexibility to select the right amount
of service for any size organization
■ Telephone and/or Web-based support that provides rapid response and
up-to-the-minute information
■ Upgrade assurance that delivers software upgrades
■ Global support purchased on a regional business hours or 24 hours a day, 7
days a week basis
■ Premium service offerings that include Account Management Services
For information about our support offerings, you can visit our website at the following
URL:
[Link]/support
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current support agreement may access Technical Support
information at the following URL:
[Link]/support
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at
the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■ Product release level
■ Hardware information
■ Available memory, disk space, and NIC information
 ■ Operating system
■ Version and patch level
■ Network topology
■ Router, gateway, and IP address information
■ Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Technical Support
■ Recent software configuration changes and network changes

Licensing and registration

If your product requires registration or a license key, access our technical support
Web page at the following URL:
[Link]/support

Customer service
Customer service information is available at the following URL:
[Link]/support
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and support contracts
■ Advice about technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources
If you want to contact us regarding an existing support agreement, please contact
the support agreement administration team for your region as follows:

Worldwide (except Japan) CustomerCare@[Link]

Japan CustomerCare_Japan@[Link]
 Contents

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

Section 1 About NetBackup ...................................................... 32

Chapter 1 Introducing NetBackup interfaces ................................ 33

About NetBackup ......................................................................... 33

NetBackup documentation ............................................................. 35
About NetBackup administration interfaces ........................................ 35
About setting up the NetBackup Administration Console on
UNIX ............................................................................. 37
Logging in to the NetBackup Administration Console ..................... 38
Administering remote servers of different versions ......................... 41
Using the NetBackup Administration Console ..................................... 43
About security certificates for NetBackup hosts ............................. 47
Standard and user toolbars ...................................................... 53
About customizing the NetBackup Administration Console .............. 54
Configuring log files for the NetBackup Administration
Console ......................................................................... 54
NetBackup configuration wizards ..................................................... 57
Running the Troubleshooter ........................................................... 58

Chapter 2 Administering NetBackup licenses ............................... 60

About administering NetBackup licenses ........................................... 60

Section 2 Configuring hosts ...................................................... 65

Chapter 3 Configuring Host Properties ........................................... 66

About the NetBackup Host Properties ............................................... 68
Methods to set the NetBackup configuration options ...................... 70
Connecting to a host to view the host properties ........................... 70
Changing the host properties on multiple hosts at the same
time ............................................................................... 71
Property states for multiple hosts ............................................... 72
 Contents 8

Exporting host properties ......................................................... 74

Standard host property dialog box options ................................... 74
Access Control properties .............................................................. 75
Authentication Domain tab of the Access Control properties ............ 76
Authorization Service tab of the Access Control properties .............. 78
Network Attributes tab of the Access Control properties .................. 79
Active Directory host properties ....................................................... 81
Bandwidth properties .................................................................... 83
Bandwidth limit usage considerations and restrictions .................... 84
Add Bandwidth Settings dialog box for Bandwidth properties ........... 85
Busy File Settings properties .......................................................... 85
Activating the Busy File Settings in host properties ........................ 87
Clean-up properties ...................................................................... 88
Client Name properties .................................................................. 90
Client Attributes properties ............................................................. 92
Add Client dialog box .............................................................. 94
General tab of the Client Attributes properties .............................. 94
Connect Options tab of the Client Attributes properties ................... 99
Windows Open File Backup tab of the Client Attributes
properties ..................................................................... 101
Back-level and upgraded clients that use Windows Open File
Backup ......................................................................... 106
Client Settings properties for UNIX clients ........................................ 107
VxFS file change log for incremental backups property ................. 110
Client Settings properties for Windows clients ................................... 112
How to determine if change journal support is useful in your
NetBackup environment ................................................... 115
Guidelines for enabling NetBackup change journal support ........... 116
Credential Access properties ......................................................... 117
Data Classification properties ........................................................ 118
Creating a Data Classification ................................................. 120
Default Job Priorities properties ..................................................... 121
Understanding the Job Priority setting ....................................... 123
Distributed application restore mapping properties ............................. 125
Encryption properties ................................................................... 126
Additional encryption methods for Windows clients ...................... 129
Enterprise Vault properties ............................................................ 130
Enterprise Vault Hosts properties ................................................... 131
Exchange properties ................................................................... 132
About the Exchange credentials in the client host properties .......... 135
Exclude Lists properties ............................................................... 136
About the Add to Exclude List and Add Exceptions to Exclude List
dialog boxes .................................................................. 139
 Contents 9

Syntax rules for exclude lists ................................................... 141

About creating an include list on a UNIX client ............................ 144
Configuring the exclude list on a Windows client from a UNIX
master server ................................................................. 144
Traversing excluded directories ............................................... 146
Fibre Transport properties ............................................................ 147
About Linux concurrent FT connections ..................................... 150
Firewall properties ...................................................................... 151
Enabling logging for vnetd ...................................................... 155
General Server properties ............................................................ 155
Forcing restores to use a specific server .................................... 158
Global Attributes properties ........................................................... 159
About constraints on the number of concurrent jobs ..................... 162
Setting up email notifications about backups .............................. 164
Configuring the [Link] script on Windows ........................... 165
Sending messages to the global administrator about unsuccessful
backups only ................................................................. 167
Sending messages to the administrator about successful and
unsuccessful backups ..................................................... 167
Installing and testing the email utility on Windows ........................ 169
Logging properties ...................................................................... 170
Disabling the logging of NetBackup processes ............................ 180
Login Banner Configuration properties ............................................ 182
Removing login banner screen and text ..................................... 184
Enabling the Auto log off timeout option ..................................... 185
Lotus Notes properties ................................................................. 186
Media properties ........................................................................ 189
Results when media overwrites are not permitted ........................ 193
Recommended use for Enable SCSI reserve property .................. 194
NDMP Global Credentials properties .............................................. 195
Network properties ...................................................................... 197
Network Settings properties .......................................................... 199
Reverse Host Name Lookup property ....................................... 200
IP Address Family Support property ......................................... 201
Port Ranges properties ................................................................ 201
Registered ports and dynamically-allocated ports ........................ 203
Preferred Network properties ........................................................ 204
Add or Change Preferred Network Settings dialog box ................. 206
How NetBackup uses the directives to determine which network
to use ........................................................................... 208
Configurations to use IPv6 networks ......................................... 211
Configurations to use IPv4 networks ......................................... 212
 Contents 10

Order of directive processing in the Preferred Network

properties ..................................................................... 213
Order of directives can affect processing ................................... 214
bptestnetconn utility to display Preferred Network
information .................................................................... 214
Configuration to prohibit using a specified address ...................... 216
Configuration that uses the same specification for both the network
and the interface—less constrictive .................................... 216
Configuration that uses the same specification for both the network
and the interface—more constrictive ................................... 217
Configuration that limits the addresses, but allows any
interfaces ...................................................................... 217
Resilient Network properties ......................................................... 218
Resilient connection resource usage ........................................ 221
Specifying resilient connections ............................................... 221
Resource Limit properties ............................................................. 223
Restore Failover properties ........................................................... 225
Assigning an alternate media server as a failover restore
server ........................................................................... 227
Retention Periods properties ......................................................... 228
Changing a retention period .................................................... 229
Determining retention periods for volumes ................................. 230
Retention Periods with end dates beyond 2038, excluding
Infinity .......................................................................... 231
Scalable Storage properties .......................................................... 231
Configuring advanced bandwidth throttling settings ...................... 233
Advanced bandwidth throttling settings ...................................... 234
Servers properties ...................................................................... 236
Adding a server to a servers list ............................................... 239
Removing a server from a server list ......................................... 240
Enabling NetBackup clustered master server inter-node
authentication ................................................................ 240
Adding a trusted master server ................................................ 242
Removing a trusted master server ............................................ 243
Changing the master server that performs backups and restores
for a client ..................................................................... 246
SharePoint properties .................................................................. 246
Consistency check options for SharePoint Server ........................ 248
SLP Parameters properties ........................................................... 248
About batch creation logic in Storage Lifecycle Manager ............... 253
Deprecated storage lifecycle policy parameters ........................... 254
Throttle Bandwidth properties ........................................................ 254
 Contents 11

Add Bandwidth Settings dialog box for Throttle Bandwidth

properties ..................................................................... 255
Timeouts properties .................................................................... 256
Universal Settings properties ......................................................... 258
Logging the status of a redirected restore .................................. 261
User Account Settings properties ................................................... 262
Unlocking a user account ....................................................... 264
UNIX Client properties ................................................................. 264
UNIX Server properties ................................................................ 265
VMware Access Hosts properties ................................................... 266
Windows Client properties ............................................................ 268
Configuration options not found in the Host Properties ........................ 268
About using commands to change the configuration options on UNIX
clients and servers ................................................................ 270
Configuration options for NetBackup servers .................................... 271
About robust logging ............................................................. 271
ALLOW_MEDIA_OVERWRITE option for NetBackup
servers ......................................................................... 273
ALLOW_NON_RESERVED_PORTS option for NetBackup servers
and clients ..................................................................... 273
AUTHENTICATION_DOMAIN option for NetBackup servers and
clients .......................................................................... 274
AUTHORIZATION_SERVICE option for NetBackup servers .......... 276
AUTO_ADD_ALL_ALIASES_FOR_CLIENT option for NetBackup
servers ......................................................................... 277
BPBRM_VERBOSE option for NetBackup servers ....................... 278
BPCD_WHITELIST_PATH option for NetBackup servers and
clients .......................................................................... 279
BPDBJOBS_COLDEFS options for UNIX master servers .............. 280
BPDBM_VERBOSE option for NetBackup servers ....................... 284
BPRD_VERBOSE option for NetBackup servers ......................... 285
BPTM_VERBOSE option for NetBackup servers ......................... 286
BPEND_TIMEOUT option for NetBackup servers ........................ 288
BPSTART_TIMEOUT option for NetBackup servers ..................... 288
CHECK_RESTORE_CLIENT option for NetBackup servers .......... 289
CLIENT_CONNECT_TIMEOUT option for NetBackup
servers ......................................................................... 290
CLIENT_PORT_WINDOW option for NetBackup servers and
clients .......................................................................... 290
CLIENT_READ_TIMEOUT option for NetBackup servers .............. 291
CLIENT_RESERVED_PORT_WINDOW option for NetBackup
servers and clients .......................................................... 293
 Contents 12

CLIENTDB_RESYNC_INTERVAL option for NetBackup servers

and clients ..................................................................... 293
CONNECT_OPTIONS option for NetBackup servers and
clients .......................................................................... 294
DEFAULT_CONNECT_OPTIONS option for NetBackup servers
and clients ..................................................................... 298
DISABLE_JOB_LOGGING option for NetBackup servers .............. 300
DISABLE_STANDALONE_DRIVE_EXTENSIONS option for
NetBackup servers .......................................................... 301
DISALLOW_BACKUPS_SPANNING_MEDIA option for NetBackup
servers ......................................................................... 302
DISALLOW_CLIENT_LIST_RESTORE option for NetBackup
servers ......................................................................... 302
DISALLOW_CLIENT_RESTORE option for NetBackup
servers ......................................................................... 303
EMMSERVER option for NetBackup servers .............................. 304
FAILOVER_RESTORE_MEDIA_SERVERS option for NetBackup
servers ......................................................................... 305
FORCE_RESTORE_MEDIA_SERVER option for NetBackup
servers ......................................................................... 305
GENERATE_ENGLISH_LOGS option for NetBackup servers and
clients .......................................................................... 306
INCOMPLETE_JOB_CLEAN_INTERVAL option for NetBackup
servers and clients .......................................................... 307
INITIAL_BROWSE_SEARCH_LIMIT option for NetBackup servers
and clients ..................................................................... 308
IP_ADDRESS_FAMILY option for NetBackup servers .................. 309
JOB_PRIORITY option for NetBackup servers and clients ............. 310
LIMIT_BANDWIDTH option for NetBackup servers ...................... 312
MAX_LOGFILE_SIZE option for NetBackup servers and clients
for legacy logging ........................................................... 313
MAX_NUM_LOGFILES option for NetBackup servers and clients
for legacy logging ........................................................... 314
KEEP_LOGS_SIZE_GB for NetBackup servers and clients ........... 315
ENABLE_CRITICAL_PROCESS_LOGGING .............................. 316
MEDIA_UNMOUNT_DELAY option for NetBackup servers ............ 317
MEDIA_REQUEST_DELAY option for NetBackup servers ............ 317
MEDIA_SERVER option for NetBackup servers .......................... 318
MPX_RESTORE_DELAY option for NetBackup servers ............... 319
MUST_USE_LOCAL_DRIVE option for NetBackup servers ........... 319
NBRNTD_IDLE_TIMEOUT option for NetBackup servers ............. 320
PREFERRED_NETWORK option for NetBackup servers .............. 321
 Contents 13

RANDOM _PORTS option for NetBackup servers and

clients .......................................................................... 324
RE_READ_INTERVAL option for NetBackup servers ................... 325
REQUIRED_NETWORK option for NetBackup servers ................. 326
RESILIENT_NETWORK option for NetBackup master servers
and clients ..................................................................... 327
RESUME_ORIG_DUP_ON_OPT_DUP_FAIL option for NetBackup
servers ......................................................................... 328
REVERSE_NAME_LOOKUP option for NetBackup servers and
clients .......................................................................... 328
SERVER option for NetBackup servers ..................................... 329
SERVER_CONNECT_TIMEOUT option for NetBackup
servers ......................................................................... 332
SERVER_PORT_WINDOW option for NetBackup servers ............ 332
SERVER_RESERVED_PORT_WINDOW option for NetBackup
servers and clients .......................................................... 333
SKIP_RESTORE_TO_SYMLINK_DIR option for NetBackup
servers ......................................................................... 334
TELEMETRY_UPLOAD option for NetBackup servers ................. 335
THROTTLE_BANDWIDTH option for NetBackup servers .............. 336
TRUSTED_MASTER option for NetBackup servers ..................... 340
ULINK_ON_OVERWRITE option for NetBackup servers ............... 340
USE_AUTHENTICATION option for NetBackup servers ............... 342
USE_VXSS option for NetBackup servers and clients .................. 342
VERBOSE option for NetBackup servers and clients .................... 343
VXSS_NETWORK option for NetBackup servers ........................ 344
Configuration options for NetBackup clients ..................................... 346
BPARCHIVE_POLICY option for NetBackup clients ..................... 347
BPARCHIVE_SCHED option for NetBackup clients ..................... 347
BPBACKUP_POLICY option for NetBackup clients ...................... 348
BPBACKUP_SCHED option for NetBackup clients ...................... 349
BUSY_FILE_ACTION option for NetBackup clients ...................... 350
BUSY_FILE_DIRECTORY option for NetBackup clients ............... 351
BUSY_FILE_NOTIFY_USER option for NetBackup clients ............ 352
BUSY_FILE_PROCESSING option for NetBackup clients ............. 353
CLIENT_NAME option for NetBackup clients .............................. 353
COMPRESS_SUFFIX option for NetBackup clients ..................... 355
CRYPT_CIPHER option for NetBackup clients ............................ 355
CRYPT_KIND option for NetBackup clients ................................ 356
CRYPT_OPTION option for NetBackup clients ........................... 357
CRYPT_STRENGTH option for NetBackup clients ...................... 358
CRYPT_LIBPATH option for NetBackup clients ........................... 359
CRYPT_KEYFILE option for NetBackup clients ........................... 360
 Contents 14

DISALLOW_SERVER_FILE_WRITES option for NetBackup

clients .......................................................................... 361
DO_NOT_RESET_FILE_ACCESS_TIME option for NetBackup
clients .......................................................................... 362
IGNORE_XATTR option for NetBackup clients ............................ 363
INFORMIX_HOME option for NetBackup clients ......................... 366
KEEP_DATABASE_COMM_FILE option for NetBackup
clients .......................................................................... 367
KEEP_LOGS_DAYS option for NetBackup clients ....................... 367
LIST_FILES_TIMEOUT option for NetBackup clients ................... 368
LOCKED_FILE_ACTION option for NetBackup clients ................. 369
MEDIA_SERVER option for NetBackup clients ........................... 369
MEGABYTES_OF_MEMORY option for NetBackup clients ........... 370
NFS_ACCESS_TIMEOUT option for NetBackup clients ................ 371
OLD_VNETD_CALLBACK option for NetBackup clients ............... 372
REPORT_CLIENT_DISCOVERIES option for NetBackup
clients .......................................................................... 372
RESTORE_RETRIES option for NetBackup clients ...................... 373
SERVER option for NetBackup clients ...................................... 374
SYBASE_HOME option for NetBackup clients ............................ 375
USE_CTIME_FOR_INCREMENTALS option for NetBackup
clients .......................................................................... 376
USE_FILE_CHG_LOG option for NetBackup clients .................... 377
USEMAIL option for NetBackup clients ...................................... 378
VXSS_NETWORK option for NetBackup clients .......................... 378

Chapter 4 Configuring server groups ............................................. 380

About NetBackup server groups .................................................... 380
Configuring a NetBackup server group ............................................ 380
NetBackup server group properties .......................................... 382
Deleting a server group ................................................................ 382

Chapter 5 Configuring host credentials ......................................... 383

About configuring credentials ........................................................ 383

Chapter 6 Managing media servers ............................................... 385

Activating or deactivating a media server ......................................... 385

Adding a media server ................................................................. 386
Registering a media server ........................................................... 387
Deleting all devices from a media server .......................................... 388
Removing a device host from the EMM database .............................. 391
 Contents 15

About decommissioning a media server .......................................... 391

About decommissioning limitations ........................................... 392
Before you decommission a media server .................................. 393
Post decommission recommendations ...................................... 394
Decommission actions ........................................................... 394
Previewing references to a media server ......................................... 397
Decommissioning a media server ................................................... 398

Section 3 Configuring storage ................................................ 401

Chapter 7 Configuring disk storage ................................................ 402
About configuring BasicDisk storage ............................................... 402
About configuring disk pool storage ................................................ 402
Inventorying a NetBackup disk pool ................................................ 403
Changing the disk pool state ......................................................... 403

Chapter 8 Configuring robots and tape drives ............................ 405

NetBackup robot types ................................................................. 406

About the device mapping files ...................................................... 407
Downloading the device mapping files ............................................ 407
About configuring robots and tape drives in NetBackup ...................... 408
About device discovery .......................................................... 409
About device serialization ....................................................... 410
About adding devices without discovery .................................... 411
About robot control ................................................................ 411
About drive name rules .......................................................... 413
Configuring robots and tape drives by using the wizard ....................... 414
Updating the device configuration by using the wizard ........................ 414
Adding a robot to NetBackup manually ............................................ 415
Robot configuration options .................................................... 417
Managing robots ........................................................................ 420
Changing robot properties ...................................................... 420
Configuring a robot to operate in manual mode ........................... 421
Deleting a robot .................................................................... 422
Moving a robot and its media to a new media server .................... 422
Adding a tape drive to NetBackup manually ..................................... 423
Tape drive configuration options ............................................... 425
Configuring drive name rules ......................................................... 429
Adding a tape drive path .............................................................. 430
About SCSI reserve on drive paths ........................................... 430
Drive path options ................................................................. 431
 Contents 16

About no rewind device files on UNIX ....................................... 432

Adding a shared tape drive to a NetBackup environment .................... 432
Correlating tape drives and SCSI addresses on Windows hosts ........... 433
Windows device correlation example ........................................ 433
Correlating tape drives and device files on UNIX hosts ....................... 434
UNIX device correlation example ............................................. 435
Managing tape drives .................................................................. 436
Changing a drive comment ..................................................... 436
About downed drives ............................................................. 437
Changing a drive operating mode ............................................ 437
Changing a tape drive path ..................................................... 438
Changing a drive path operating mode ...................................... 438
Changing tape drive properties ................................................ 439
Changing a tape drive to a shared drive .................................... 439
Cleaning a tape drive from the Device Monitor ............................ 440
Deleting a drive .................................................................... 441
Resetting a drive .................................................................. 441
Resetting the mount time of a drive .......................................... 442
Setting the drive cleaning frequency ......................................... 442
Viewing drive details .............................................................. 443
Performing device diagnostics ....................................................... 443
Running a robot diagnostic test ................................................ 443
Running a tape drive diagnostic test ......................................... 445
Managing a diagnostic test step that requires operator
intervention ................................................................... 446
Obtaining detailed information for a diagnostic test step ................ 446
Verifying the device configuration ................................................... 447
About automatic path correction ..................................................... 447
Enabling automatic path correction ................................................. 448
Replacing a device ..................................................................... 448
Updating device firmware ............................................................. 450
About the NetBackup Device Manager ............................................ 451
About external access to NetBackup controlled devices on UNIX .......... 451
Stopping and restarting the device manager ..................................... 452

Chapter 9 Configuring tape media ................................................ 453

About NetBackup tape volumes ..................................................... 454

About NetBackup volume pools ..................................................... 454
About reserved volume pool name prefixes ................................ 455
About scratch volume pools .................................................... 456
About NetBackup volume groups ................................................... 457
NetBackup media types ............................................................... 458
 Contents 17

About WORM media ................................................................... 460

About using volume pools to manage WORM media .................... 461
About using unique drive and media types to manage WORM
media ........................................................................... 462
Disabling WORM volume pool name verification ......................... 463
About WORM media and the Quantum drive .............................. 463
Supported WORM drives ........................................................ 463
About adding volumes ................................................................. 464
About adding robotic volumes ................................................. 464
About adding standalone volumes ............................................ 465
About configuring media name and attribute rules ............................. 466
Adding volumes by using the wizard ............................................... 466
About media settings rules ............................................................ 467
Configuring media settings ........................................................... 467
Media settings options ........................................................... 469
About barcodes .......................................................................... 477
About barcode rules .............................................................. 479
Configuring barcode rules ............................................................ 480
Barcode rules settings ........................................................... 483
About media ID generation rules .................................................... 485
Configuring media ID generation rules ............................................ 486
Media ID generation options ................................................... 488
About media type mapping rules .................................................... 489
Adding volumes by using the Actions menu ...................................... 490
Volume properties ................................................................. 491
Configuring media type mappings .................................................. 494
About adding media type mapping entries ................................. 496
Default and allowable media types ........................................... 496
Managing volumes ...................................................................... 501
Changing the group of a volume .............................................. 501
About rules for moving volumes between groups ......................... 502
Changing the owner of a volume .............................................. 502
Changing volume properties ................................................... 503
About assigning and deassigning volumes ................................. 504
Deleting a volume ................................................................. 505
Erasing a volume .................................................................. 506
About exchanging a volume .................................................... 507
About frozen media ............................................................... 509
About injecting and ejecting volumes ........................................ 510
About rescanning and updating barcodes .................................. 513
About labeling NetBackup volumes .......................................... 514
About moving volumes ........................................................... 516
About recycling a volume ....................................................... 518
 Contents 18

Suspending or unsuspending volumes ...................................... 519

Managing volume pools ............................................................... 520
Adding a volume pool ............................................................ 520
Changing the properties of a volume pool .................................. 520
Deleting a volume pool .......................................................... 521
Managing volume groups on UNIX ................................................. 522
Moving a volume group .......................................................... 522
Deleting a volume group ........................................................ 524
About media sharing ................................................................... 524
Configuring unrestricted media sharing ........................................... 525
Configuring media sharing with a server group .................................. 525

Chapter 10 Inventorying robots .......................................................... 527

About robot inventory .................................................................. 527
When to inventory a robot ............................................................. 528
About showing a robot's contents ................................................... 530
About inventory results for API robots ....................................... 531
Showing the media in a robot ........................................................ 533
About comparing a robot's contents with the volume
configuration ........................................................................ 534
Comparing media in a robot with the volume configuration .................. 535
About previewing volume configuration changes ............................... 536
Previewing volume configuration changes for a robot ......................... 537
About updating the NetBackup volume configuration .......................... 539
Volume update prerequisites ................................................... 539
Updating the NetBackup volume configuration with a robot's
contents .............................................................................. 540
Robot inventory options ............................................................... 542
About the vmphyinv physical inventory utility .................................... 543
How vmphyinv performs a physical inventory .............................. 545
Example volume configuration updates ........................................... 549

Chapter 11 Configuring storage units .............................................. 559

About the Storage utility ............................................................... 559

Using the Storage utility ......................................................... 560
Creating a storage unit ................................................................. 561
Creating a storage unit by copying a storage unit ........................ 564
Changing storage unit settings ................................................ 564
Deleting storage units ............................................................ 565
Media Manager storage unit considerations ............................... 566
Disk storage unit considerations .............................................. 568
NDMP storage unit considerations ........................................... 572
 Contents 19

About storage unit settings ........................................................... 574

Absolute pathname to directory or absolute pathname to volume
setting for storage units .................................................... 574
Density storage unit setting ..................................................... 575
Disk pool storage unit setting .................................................. 575
Disk type storage unit setting .................................................. 575
Enable block sharing storage unit setting ................................... 576
Enable multiplexing storage unit setting ..................................... 576
High water mark storage unit setting ......................................... 576
Low water mark storage unit setting .......................................... 577
Maximum concurrent write drives storage unit setting ................... 577
Maximum concurrent jobs storage unit setting ............................ 578
Maximum streams per drive storage unit setting .......................... 580
Media server storage unit setting ............................................. 580
NDMP host storage unit setting ............................................... 582
On demand only storage unit setting ......................................... 583
Only use the following media servers storage unit setting .............. 583
Properties option in the Change Storage Units dialog box ............. 584
Reduce fragment size storage unit setting .................................. 585
Robot number storage unit setting ............................................ 586
Robot type storage unit setting ................................................ 586
Staging schedule option in Change Storage Units dialog ............... 586
Storage device setting for storage units ..................................... 587
Storage unit name setting ....................................................... 587
Storage unit type setting ......................................................... 587
Enable temporary staging area storage unit setting ...................... 587
Use any available media server storage unit setting ..................... 588

Chapter 12 Staging backups .............................................................. 589

About staging backups ................................................................ 589

About basic disk staging ............................................................... 590
Creating a basic disk staging storage unit ........................................ 591
Creating a schedule for a basic disk staging storage unit .............. 592
Configuring multiple copies in a relocation schedule ........................... 593
Disk staging storage unit size and capacity ...................................... 595
Finding potential free space on a BasicDisk disk staging storage
unit .................................................................................... 597
Disk Staging Schedule dialog box .................................................. 598
Initiating a relocation schedule manually .......................................... 601
 Contents 20

Chapter 13 Configuring storage unit groups .................................. 602

About storage unit groups ............................................................. 602

Creating storage unit groups for backups ......................................... 603
Creating storage unit groups for snapshots ...................................... 605
Deleting a storage unit group ........................................................ 607
Storage unit selection criteria within a group ..................................... 607
Media server load balancing ................................................... 608
Other load balancing methods ................................................. 609
Exception to the storage unit selection criteria ............................ 611
About disk spanning within storage unit groups ................................. 611

Section 4 Configuring storage lifecycle policies

(SLPs) ........................................................................ 612
Chapter 14 Configuring storage lifecycle policies ........................ 613

About storage lifecycle policies ...................................................... 613

Creating a storage lifecycle policy .................................................. 614
Modifying the hierarchy of operations in a storage lifecycle
policy ........................................................................... 617
Deleting a storage lifecycle policy ................................................... 618
Lifecycle operation administration using the nbstlutil command ............ 619

Chapter 15 Storage operations .......................................................... 621

Operation types in a storage lifecycle policy ..................................... 621

Backup operation in an SLP .......................................................... 621
Backup From Snapshot operation in an SLP .................................... 623
Duplication operation in an SLP ..................................................... 625
Import operation in an SLP ........................................................... 627
Index From Snapshot operation in an SLP ....................................... 629
Determining where and when the Index From Snapshot operation
occurs .......................................................................... 631
Replication operation in an SLP ..................................................... 632
Snapshot operation in an SLP ....................................................... 635
About configuring storage lifecycle policies for snapshots and
snapshot replication ........................................................ 637
Primary snapshot storage unit ................................................. 639
Primary + Replication source snapshot storage unit ..................... 639
Replication source + Replication target snapshot storage
unit .............................................................................. 640
Replication target snapshot storage unit .................................... 640
 Contents 21

Replication source + Replication target + Mirror snapshot storage

unit .............................................................................. 641
Replication target + Mirror snapshot storage unit ......................... 641
Creating a hierarchy of storage operations in a storage lifecycle
policy ................................................................................. 641

Chapter 16 Retention types for SLP operations ........................... 644

Retention types for storage lifecycle policy operations ........................ 644

Capacity managed retention type for SLP operations ......................... 646
Rules and recommendations for using the Capacity Managed
retention type ................................................................. 647
Capacity managed retention type and disk types that support
SIS .............................................................................. 647
Expire after copy retention type for SLP operations ............................ 648
Fixed retention type for SLP operations ........................................... 648
Maximum snapshot limit retention type for SLP operations .................. 649
Mirror retention type for SLP operations .......................................... 650
Target retention type for SLP operations .......................................... 651

Chapter 17 Storage lifecycle policy options ................................... 652

Storage Lifecycle Policy dialog box settings ..................................... 652

New or Change Storage Operation dialog box settings ....................... 656
Properties tab of the Storage Operation dialog box ...................... 656
Window tab of the Storage Operation dialog box ......................... 660
Creating a new window for a storage lifecycle policy
operation ...................................................................... 662
Excluding days from a window for a storage lifecycle policy
operation ...................................................................... 663
Storage lifecycle policy validation dialog box .................................... 664
Storage lifecycle policy Validation Report tab .................................... 665

Chapter 18 Using a storage lifecycle policy to create multiple

copies ............................................................................ 667
About writing multiple copies using a storage lifecycle policy ................ 667
How the order of the operations determines the copy order ................. 668
About ensuring successful copies using lifecycles ............................. 668

Chapter 19 Storage lifecycle policy versions ................................. 670

About storage lifecycle policy versions ............................................ 670

Storage lifecycle changes and versioning ........................................ 671
 Contents 22

When changes to storage lifecycle policies become effective ............... 672

Deleting old storage lifecycle policy versions .................................... 673

Section 5 Configuring backups .............................................. 675

Chapter 20 Creating backup policies ............................................... 676

About the Policies utility ............................................................... 677

Planning for policies .................................................................... 679
Windows example of one client in multiple policies ...................... 681
Policy attributes that affect how clients are grouped in
policies ......................................................................... 682
About Microsoft DSFR backups ............................................... 683
Creating a backup policy .............................................................. 686
Adding or changing schedules in a policy ........................................ 688
Changing multiple policies at one time ............................................ 689
Copying or moving policy items to another policy ............................... 690
Copying a policy to create a new policy ........................................... 691
Copying a schedule into the same policy or different policy .................. 692
Deleting schedules, backup selections, or clients from a policy ............. 692
Policy Attributes tab .................................................................... 693
Policy type (policy attribute) .................................................... 694
Data classifications (policy attribute) ......................................... 697
Policy storage (policy attribute) ................................................ 698
Policy volume pool (policy attribute) .......................................... 701
Take checkpoints every __ minutes (policy attribute) .................... 703
Limit jobs per policy (policy attribute) ........................................ 706
Job priority (policy attribute) .................................................... 708
Media Owner (policy attribute) ................................................. 709
Go into effect at (policy attribute) .............................................. 709
Follow NFS (policy attribute) ................................................... 710
Backup Network Drives (policy attribute) .................................... 711
Cross mount points (policy attribute) ......................................... 713
Compression (policy attribute) ................................................. 717
Encryption (policy attribute) ..................................................... 719
Collect disaster recovery information for Bare Metal Restore (policy
attribute) ....................................................................... 721
Collect true image restore information (policy attribute) with and
without move detection .................................................... 721
Allow multiple data streams (policy attribute) .............................. 725
Disable client-side deduplication (policy attribute) ........................ 729
Enable granular recovery (policy attribute) ................................. 729
Use Accelerator (policy attribute) ............................................. 730
 Contents 23

Enable optimized backup of Windows deduplicated volumes ......... 751

Keyword phrase (policy attribute) ............................................. 754
Snapshot Client and Replication Director (policy attributes) ........... 754
Perform block level incremental backups (policy attributes) ........... 755
Use Replication Director (policy attributes) ................................. 755
Perform snapshot backups (policy attributes) .............................. 757
Microsoft Exchange Attributes (policy attributes) ......................... 757
Schedules tab ............................................................................ 757
Schedule Attributes tab ................................................................ 758
Name (schedule attribute) ...................................................... 759
Type of backup (schedule attribute) .......................................... 759
Synthetic backup (schedule attribute) ........................................ 768
Accelerator forced rescan option (schedule attribute) ................... 769
Calendar (schedule attribute) .................................................. 771
Frequency (schedule attribute) ................................................ 771
Instant Recovery (schedule attribute) ........................................ 773
Multiple copies (schedule attribute) ........................................... 774
Override policy storage (schedule attribute) ................................ 778
Override policy volume pool (schedule attribute) ......................... 779
Override media owner (schedule attribute) ................................. 779
Retention (schedule attribute) .................................................. 780
Media multiplexing (schedule attribute) ...................................... 783
Start Window tab ........................................................................ 790
Adding, changing, or deleting a time window in a policy
schedule ....................................................................... 790
Example of schedule duration ................................................. 793
Excluding days from a schedule ..................................................... 794
Include Dates tab ........................................................................ 795
Calendar scheduling with the Include Dates tab .......................... 795
How NetBackup determines which schedule to run next ..................... 796
About schedule windows that span midnight ..................................... 799
How open schedules affect calendar-based and frequency-based
schedules ........................................................................... 800
Creating an open schedule in the NetBackup Administration
Console ........................................................................ 803
Runtime considerations that affect backup frequency ................... 804
About the Clients tab ................................................................... 805
Adding or changing clients in a policy ........................................ 805
Installing client software on secure and trusting UNIX clients ......... 807
Browse for Hyper-V virtual machines ........................................ 809
Backup Selections tab ................................................................. 810
Adding backup selections to a policy ......................................... 811
Verifying the Backup Selections list .......................................... 813
 Contents 24

How to reduce backup time ..................................................... 816

Pathname rules for Windows client backups ............................... 817
Pathname rules for Windows disk image (raw) backups ................ 820
Pathname rules for Windows registry backups ............................ 821
About hard links to files and directories ..................................... 822
Pathname rules for UNIX client backups .................................... 824
Pathname rules for the clients that run extension products ............ 832
About the directives on the Backup Selections list ....................... 832
Files that are excluded from backups by default .......................... 845
About excluding files from automatic backups ............................. 846
Files that are excluded by Microsoft Windows Backup .................. 847
VMware Policy tab ...................................................................... 847
Hyper-V Policies tab .................................................................... 849
Disaster Recovery tab ................................................................. 851
Adding policies to the Critical Policies list of a catalog backup
policy ........................................................................... 854
Creating a Vault policy ................................................................. 854
Performing manual backups ......................................................... 856
Active Directory granular backups and recovery ................................ 857
System requirements for Active Directory granular NetBackup
backups and recovery ..................................................... 858
Creating a policy that allows Active Directory granular
restores ........................................................................ 858
Restoring Active Directory objects ............................................ 860
Troubleshooting granular restore issues .................................... 861

Chapter 21 Synthetic backups ........................................................... 864

About synthetic backups .............................................................. 864

Recommendations for synthetic backups and restores ....................... 865
Synthetic full backups .................................................................. 868
Synthetic cumulative incremental backups ....................................... 870
Schedules that must appear in a policy for synthetic backups .............. 872
Adding clients to a policy for synthetic backups ................................. 872
Change journal and synthesized backups ........................................ 873
True image restore and synthesized backups ................................... 873
Displaying synthetic backups in the Activity Monitor ........................... 873
Logs produced during synthetic backups ......................................... 874
Synthetic backups and directory and file attributes ............................. 874
Using the multiple copy synthetic backups method ............................ 875
Configuring multiple copy synthetic backups ............................... 876
Configuration variables for multiple copy synthetic backups ........... 877
Multiple copy synthetic backups configuration examples ............... 878
 Contents 25

Optimized synthetic backups ......................................................... 879

Optimized synthetic backups for deduplication .................................. 879

Chapter 22 Protecting the NetBackup catalog .............................. 880

About the NetBackup catalog ........................................................ 880

Parts of the NetBackup catalog ...................................................... 881
About the NetBackup relational database .................................. 883
About the NetBackup image database ...................................... 887
About catalog backup of cloud configuration files ......................... 889
Protecting the NetBackup catalog .................................................. 890
About catalog backups .......................................................... 891
Using the Catalog Backup Wizard to configure a catalog
backup ......................................................................... 892
Using the Policy Configuration Wizard to configure a catalog
backup ......................................................................... 895
Configuring a catalog backup manually ..................................... 897
Backing up NetBackup catalogs manually .................................. 899
Concurrently running catalog backups with other backups ............. 900
About catalog policy schedules ................................................ 900
How catalog incrementals and standard backups interact on
UNIX ............................................................................ 901
Determining whether or not a catalog backup succeeded .............. 901
Strategies that ensure successful NetBackup catalog
backups ........................................................................ 902
Recovering the catalog ................................................................ 902
Disaster recovery emails and the disaster recovery file ....................... 902
Archiving the catalog and restoring from the catalog archive ................ 903
Creating a catalog archiving policy ........................................... 906
Catalog archiving commands .................................................. 907
Catalog archiving considerations ............................................. 909
Extracting images from the catalog archives ............................... 910
Estimating catalog space requirements ........................................... 910
NetBackup file size considerations on UNIX systems ................... 912
About the binary catalog format ............................................... 912
Moving the image catalog ....................................................... 912
About image catalog compression ............................................ 915

Chapter 23 About the NetBackup relational database ................ 919

About the NetBackup relational database (NBDB) installation .............. 919
About NetBackup master server installed directories and
files .............................................................................. 922
About the NetBackup configuration entry ................................... 931
 Contents 26

Sybase SQL Anywhere server management .............................. 932

Sybase SQL Anywhere and clustered environments .................... 933
Using the NetBackup Database Administration utility on Windows ........ 933
About the General tab of the NetBackup Database Administration
utility ............................................................................ 935
About the Tools tab of the NetBackup Database Administration
utility ............................................................................ 941
Using the NetBackup Database Administration utility on UNIX ............. 947
About the Select/Restart Database and Change Password menu
options ......................................................................... 949
About the Database Space and Memory Management menu
options ......................................................................... 950
About the Database Validation Check and Rebuild menu
options ......................................................................... 952
About the Move Database menu options ................................... 953
About the Unload Database menu options ................................. 954
About the Backup and Restore Database menu options ................ 955
Post-installation tasks .................................................................. 956
Changing the NetBackup database password ............................. 956
Moving NBDB database files after installation ............................. 958
Adding a mirrored transaction log ............................................. 959
Creating the NBDB database manually ..................................... 961
About backup and recovery procedures .......................................... 964
Database transaction log ........................................................ 964
About catalog recovery .......................................................... 965
Commands for backing up and recovering the relational
databases ..................................................................... 965
About the catalog backup process ............................................ 967
Unloading the NetBackup database ................................................ 968
Terminating database connections ................................................. 969
Moving the NetBackup database from one host to another .................. 971

Chapter 24 Managing backup images ............................................. 972

About the Catalog utility ............................................................... 972

About searching for backup images ................................................ 973
Verifying backup images .............................................................. 976
Viewing job results ...................................................................... 976
Promoting a copy to a primary copy ................................................ 977
Duplicating backup images ........................................................... 979
About multiplexed duplication considerations .............................. 984
Jobs that appear while making multiple copies ............................ 985
Expiring backup images ............................................................... 986
 Contents 27

About importing backup images ..................................................... 987

About importing expired images ............................................... 987
Importing backup images ....................................................... 988

Section 6 Configuring replication ......................................... 990

Chapter 25 About NetBackup replication ........................................ 991

About NetBackup replication ......................................................... 991
About NetBackup Auto Image Replication ........................................ 992
One-to-many Auto Image Replication model ............................... 994
Cascading Auto Image Replication model .................................. 994
About the domain relationship for replication .............................. 997
About the replication topology for Auto Image Replication ............. 998
Viewing the replication topology for Auto Image Replication ......... 1000
About trusted master servers for Auto Image Replication ............. 1005
About the storage lifecycle policies required for Auto Image
Replication .................................................................. 1006
Using NetBackup Access Control (NBAC) with Auto Image
Replication .................................................................. 1011
Auto Image Replication setup overview ................................... 1012
How to resolve volume changes for Auto Image Replication ......... 1013
Removing or replacing replication relationships in an Auto Image
Replication configuration ................................................ 1016
About restoring from a backup at a target master domain ............ 1030
Reporting on Auto Image Replication jobs ................................ 1031
About NetBackup Replication Director ........................................... 1032

Section 7 Monitoring and reporting ................................... 1034

Chapter 26 Monitoring NetBackup activity .................................... 1035
About the Activity Monitor ........................................................... 1035
Setting Activity Monitor options .................................................... 1037
About the Jobs tab .................................................................... 1038
Viewing job details in the Activity Monitor ................................. 1040
Showing or hiding column heads in the Activity Monitor ............... 1040
Monitoring the detailed status of a selected job in the Activity
Monitor ....................................................................... 1041
Deleting completed jobs in the Activity Monitor .......................... 1041
Canceling a job that has not completed in the Activity
Monitor ....................................................................... 1041
Restarting a failed (completed) job in the Activity Monitor ............ 1042
 Contents 28

Suspending restore or backup jobs in the Activity Monitor ............ 1042

Resuming suspended or incomplete jobs in the Activity
Monitor ....................................................................... 1042
Printing job list information in the Activity Monitor ....................... 1043
Exporting Activity Monitor data to a text file ............................... 1043
Printing job detail information ................................................. 1043
Copying Activity Monitor text to a file ....................................... 1044
Changing the Job Priority dynamically from the Activity
Monitor ....................................................................... 1044
About the Daemons tab .............................................................. 1045
Using the nbrbutil utility to configure the NetBackup Resource
Broker ........................................................................ 1050
Types of NetBackup daemons ............................................... 1055
Monitoring NetBackup daemons ............................................ 1055
Starting or stopping a daemon ............................................... 1056
Displaying all media servers in the Activity Monitor ..................... 1056
About the Processes tab ............................................................. 1057
Monitoring NetBackup processes in the Process Details dialog
box ............................................................................ 1061
About the Drives tab .................................................................. 1062
Monitoring tape drives .......................................................... 1063
Cleaning tape drives from the Activity Monitor ........................... 1063
About the jobs database ............................................................. 1063
Changing the default bpdbjobs_options values .......................... 1064
About the BPDBJOBS_OPTIONS environment variable .............. 1065
bpdbjobs command line options ............................................. 1067
Enabling the bpdbjobs debug log ........................................... 1067
About the Device Monitor ............................................................ 1068
About media mount errors ........................................................... 1069
About pending requests and actions ............................................. 1069
About pending requests for storage units ................................. 1070
Resolving a pending request ................................................. 1071
Resolving a pending action ................................................... 1072
Resubmitting a request ........................................................ 1072
Denying a request ............................................................... 1073

Chapter 27 Reporting in NetBackup ............................................... 1074

About the Reports utility ............................................................. 1074

Running a report ....................................................................... 1078
Copying report text to another document ........................................ 1078
Saving or exporting a report ........................................................ 1079
Printing a report ........................................................................ 1079
 Contents 29

Chapter 28 Using the Logging Assistant ....................................... 1081

About the Logging Assistant ........................................................ 1081

Logging Assistant sequence of operation ....................................... 1084
Viewing the Logging Assistant records .......................................... 1085
Viewing the details of a Logging Assistant record ............................. 1085
Adding a new Logging Assistant record ......................................... 1089
Deleting a Logging Assistant record .............................................. 1091
Setting up debug logging ............................................................ 1092
Set minimum debug logging ........................................................ 1096
Disabling debug logging ............................................................. 1097
Collecting and uploading debug logs ............................................. 1098
Collecting and uploading nbsu information ..................................... 1104
Uploading evidence ................................................................... 1107

Section 8 Administering NetBackup ................................. 1110

Chapter 29 Management topics ....................................................... 1111

Configuring the NetBackup Client Service ...................................... 1111

NetBackup naming conventions ................................................... 1112
Wildcard use in NetBackup ......................................................... 1113
Wildcard characters in backup selections for an NDMP policy ............ 1115
How to access media and devices on other hosts ............................ 1118

Chapter 30 Accessing a remote server .......................................... 1120

Prerequisites for accessing a remote server ................................... 1120
Allow access to another server .............................................. 1121
Authorize users of one server to access another server .............. 1123
Accessing remote servers ........................................................... 1124
About running the NetBackup Administration Console on a NetBackup
client ................................................................................ 1125
Troubleshooting remote server administration ................................. 1125

Chapter 31 Using the NetBackup Remote Administration

Console ....................................................................... 1127
About the NetBackup Remote Administration Console ...................... 1128
About authorizing NetBackup users .............................................. 1131
Authorization file ([Link]) characteristics .................................... 1132
About authorizing nonroot users for specific applications ................... 1134
About authorizing specific tasks in the Backup, Archive, and Restore
user interface ..................................................................... 1135
 Contents 30

About authorizing users on Windows NetBackup server .................... 1136

Restricting access to the NetBackup Administration Console on
Windows ........................................................................... 1137
Run-time configuration options for the NetBackup Administration
Console ............................................................................ 1137
FIREWALL_IN .................................................................... 1138
FORCE_IPADDR_LOOKUP .................................................. 1139
INITIAL_MEMORY, MAX_MEMORY ....................................... 1141
MEM_USE_WARNING ........................................................ 1141
NBJAVA_CLIENT_PORT_WINDOW ....................................... 1141
NBJAVA_CORBA_DEFAULT_TIMEOUT .................................. 1142
NBJAVA_CORBA_LONG_TIMEOUT ...................................... 1142
PBX_PORT ....................................................................... 1143
VNETD_PORT ................................................................... 1143
About customizing jnbSA and jbpSA with [Link] entries ................... 1143
About improving NetBackup-Java performance ............................... 1144
About running the Java console locally .................................... 1144
About running a console locally and administering a remote
server ......................................................................... 1145
About enhancing console performance .................................... 1145
About determining better performance when console is run locally
or uses remote display back ............................................ 1147
About adjusting time zones in the NetBackup Administration
console ............................................................................. 1148
Adjusting the time zone in the NetBackup Administration Console
or the Backup, Archive, and Restore console ...................... 1149
Configuring a custom time zone in the NetBackup Administration
Console or the Backup, Archive, and Restore console .......... 1149

Chapter 32 Alternate server restores ............................................. 1151

About alternate server restores .................................................... 1151

About supported configurations for alternate server restores .............. 1152
About performing alternate server restores ..................................... 1153
About modifying the NetBackup catalogs ................................. 1154
Overriding the original server for restores ................................. 1155
About enabling automatic failover to an alternate server .............. 1157
Expiring and importing media for alternate server restores ........... 1158

Chapter 33 Managing client backups and restores .................... 1160

About server-directed restores ..................................................... 1160
About client-redirected restores .................................................... 1161
About restore restrictions ...................................................... 1162
 Contents 31

Allowing all clients to perform redirected restores ....................... 1162

Allowing a single client to perform redirected restores ................. 1163
Allowing redirected restores of a specific client’s files ................. 1163
Examples of redirected restores ............................................. 1164
About restoring the files that have Access Control Lists (ACLs) .......... 1170
About setting the original atime for files during restores on UNIX ......... 1171
Restoring the System State ......................................................... 1171
About the backup and restore of compressed files on VxFS file
systems ............................................................................ 1174
About backups and restores on ReFS ........................................... 1175

Chapter 34 Powering down and rebooting NetBackup

servers ......................................................................... 1176
Powering down and rebooting NetBackup servers ........................... 1176
Shutting down and starting up all NetBackup services and
daemons ........................................................................... 1177
Rebooting a NetBackup server .................................................... 1178
Rebooting a NetBackup media server ........................................... 1178
About displaying active processes with bpps on UNIX ...................... 1179
About displaying robotic processes with vmps on UNIX ..................... 1180

Chapter 35 About Granular Recovery Technology ..................... 1181

About installing and configuring Network File System (NFS) for Active
Directory Granular Recovery ................................................. 1181
About configuring Services for Network File System (NFS) on Windows
2012 and Windows 2012 R2 ................................................. 1182
Enabling Services for Network File System (NFS) on a Windows
2012 or Windows 2012 R2 media server ............................ 1183
Enabling Services for Network File System (NFS) on a Windows
2012 or Windows 2012 R2 client ...................................... 1187
About configuring Services for Network File System (NFS) on Windows
2008 and Windows 2008 R2 ................................................. 1190
Enabling Services for Network File System (NFS) on Windows
2008 or Windows 2008 R2 .............................................. 1192
Disabling the Client for NFS on the media server ....................... 1194
Disabling the Server for NFS ................................................. 1196
Configuring a UNIX media server and Windows clients for backups
and restores that use Granular Recovery Technology (GRT) ........ 1198
Configuring a different network port for NBFSD ............................... 1199

Index ................................................................................................................ 1200

 Section 1
About NetBackup

■ Chapter 1. Introducing NetBackup interfaces

■ Chapter 2. Administering NetBackup licenses

 Chapter 1
Introducing NetBackup
interfaces
This chapter includes the following topics:

■ About NetBackup

■ NetBackup documentation

■ About NetBackup administration interfaces

■ Using the NetBackup Administration Console

■ NetBackup configuration wizards

■ Running the Troubleshooter

About NetBackup
NetBackup provides a complete, flexible data protection solution for a variety of
platforms. The platforms include Windows, UNIX, and Linux systems.
NetBackup administrators can set up periodic or calendar-based schedules to
perform automatic, unattended backups for clients across a network. An
administrator can carefully schedule backups to achieve systematic and complete
backups over a period of time, and optimize network traffic during off-peak hours.
The backups can be full or incremental. Full backups back up all client files.
Incremental backups back up only the files that have changed since the last backup.
The NetBackup administrator can allow users to back up, restore, or archive the
files from their computer. (An archive operation backs up a file, then deletes it from
the local disk if the backup is successful.)
NetBackup includes both the server and the client software as follows:
 Introducing NetBackup interfaces 34
About NetBackup

■ Server software resides on the computer that manages the storage devices.
■ Client software resides on computer(s) that contain data to back up. (Servers
also contain client software and can be backed up.)
Figure 1-1 shows an example of a NetBackup storage domain.

Figure 1-1 NetBackup storage domain example

NetBackup
master server

Media servers

SAN

OpenStorage
Media Manager tape BasicDisk disk pool
storage unit storage unit

NetBackup
clients

NetBackup accommodates multiple servers that work together under the

administrative control of one NetBackup master server in the following ways:
■ The master server manages backups, archives, and restores. The master server
is responsible for media and device selection for NetBackup. Typically, the
master server contains the NetBackup catalog. The catalog contains the internal
databases that contain information about NetBackup backups and configuration.
■ Media servers provide additional storage by allowing NetBackup to use the
storage devices that are attached to them. Media servers can also increase
performance by distributing the network load. Media servers can also be referred
to by using the following terms:
■ Device hosts (when tape devices are present)
■ Storage servers (when I/O is directly to disk)
 Introducing NetBackup interfaces 35
NetBackup documentation

■ Data movers (when data is sent to independent, external disk devices like
OpenStorage appliances)

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

NetBackup documentation
For a complete list of NetBackup technical documents for each supported release,
see the NetBackup release notes, Administration, Installation, Troubleshooting,
Getting Started, and Solutions Guides page at the following URL:
[Link]
The documents are in Adobe® Portable Document Format (PDF), viewable with
the Adobe Acrobat Reader. Download the reader from [Link]
Veritas assumes no responsibility for the installation and use of the reader.
The NetBackup landing page on the Veritas Support website contains a list of helpful
how-to and product alert topics.

About NetBackup administration interfaces

NetBackup can be administered with several interfaces. The best choice depends
on personal preference and the workstation that is available to the administrator.
 Introducing NetBackup interfaces 36
About NetBackup administration interfaces

Table 1-1 NetBackup administration interfaces

Name of Description
interface

NetBackup The NetBackup Administration Console is the recommended interface and is the interface
Administration referred to by most procedures and examples in the documentation.
Console
Veritas recommends that you run the NetBackup Administration Console on the master server
to configure and manage the storage devices on all of your media servers.

Multiple base versions of the NetBackup Administration Console are installed when you install
the server software. Select the version of the console that is compatible with the NetBackup server
that you want to administer.

See “Administering remote servers of different versions” on page 41.

To start the NetBackup Administration Console

■ On Windows, select NetBackup 7.7.2 Administration Console from the Start menu.
■ On UNIX, run the jnbSA command.

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

Character-based, Run the tpconfig command to start a character-based, menu interface for device management.
menu interface
Use the tpconfig interface from any terminal (or terminal emulation window) that has a termcap
or a terminfo definition.

Command line NetBackup commands are available on both Windows and UNIX platforms. Enter NetBackup
commands at the system prompt or use the commands in scripts.

All NetBackup administrator programs and commands require root or administrator user privileges
by default.

See “About authorizing nonroot users for specific applications” on page 1134.

For complete information on all NetBackup commands, see the NetBackup Commands Reference
Guide.

To view the commands online, use the UNIX man command.

Note: If there is more than one NetBackup server, the NetBackup Administration
Console can be run on more than one server at one time. However, if more than
one administrator makes changes to the configuration, the results are unpredictable.

See “Using the NetBackup Administration Console” on page 43.

See “Administering remote servers of different versions” on page 41.
 Introducing NetBackup interfaces 37
About NetBackup administration interfaces

About setting up the NetBackup Administration Console on UNIX

NetBackup provides two Java-based administration consoles through which the
administrator can manage NetBackup. The consoles can be run on either of the
following systems:
■ Directly on a supported NetBackup-Java capable UNIX computer by running
/usr/openv/java/jnbSA &
The jnbSA command is described in the NetBackup Commands Reference
Guide.
Use the -r command to connect to the compatible version of the console for
the server that you want to administer.
■ On a Windows computer that has the NetBackup Administration Console
installed.
From the multiple versions of consoles installed, select the version of the console
that is compatible with the NetBackup server that you want to administer.
Startup procedures and configuration information is explained in the following topics.

Setting up a CDE for the Java-based NetBackup interfaces

on UNIX
Always set the window manager so that a window becomes active only when clicked.
The NetBackup Java interfaces do not run properly with auto-focus enabled.
Auto-focus causes a window to become active when the pointer moves over the
window.
The following are general instructions for correctly setting up the focus on a CDE
(Common Desktop Environment) window manager. CDE is the preferred window
manager for NetBackup Java applications.
The NetBackup host that is specified on the login dialog box and the computer
where you start the NetBackup Administration Console must run the same
NetBackup version.
The NetBackup Administration Console supports remote X Windows display
only between same-platform systems. For example, assume that you are on a
Solaris system named system1 and the NetBackup-Java software is on a Solaris
system named system2. Here, you can display the interface on system1 by
performing rlogin to system2. Then run jnbSA -d system1. However, if system2
was an HP system, you could display jnbSA only directly on system2.
In addition, the system where the console appears must run a version of the
operating system that the console supports. Refer to the NetBackup release notes
for supported versions, including any required release updates.
The jnbSA command is described in the NetBackup Commands Reference Guide.
 Introducing NetBackup interfaces 38
About NetBackup administration interfaces

To set up a CDE (Common Desktop Environment) for NetBackup Java

interfaces
1 On the front panel in the CDE window, click the Style Manager control icon.
2 On the Style Manager toolbar, click the Window control icon.
3 In the Style Manager-Window dialog box, click Click In Window To Make
Active.
4 Click OK.
5 Click OK when prompted to Restart the Workspace Manager.

Logging in to the NetBackup Administration Console

Use the NetBackup Administration Console to administer Windows or UNIX
computers.
To start the NetBackup Administration Console
1 On a Windows host where the NetBackup Administration Console is installed
and configured, select Start > Programs > Veritas NetBackup > NetBackup
7.7.2 Administration Console.
On a UNIX computer, use the jnbSA command:
/usr/openv/java/jnbSA &

2 The logon screen for the NetBackup Administration Console displays the
host name. Log into another server by typing the name of another host in the
Host name field. Or, select a host name from the drop-down list.
If the server you enter is a media server or client, the media server or client
must have a security certificate installed.
See “Deploying a security certificate on a NetBackup host ” on page 48.
 Introducing NetBackup interfaces 39
About NetBackup administration interfaces

3 In the login screen, type your user name and password. To log into a Windows
server, enter both the domain of the server and the user name as follows:

domain_name\user_name

The domain_name specifies the domain of the NetBackup host. If the host is
not a member of a domain, the domain_name is not required.
4 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 logon screen for the remainder of the current
session.
The default host is the last host that was successfully logged into. The
drop-down list contains the names of other hosts that have been logged into.
To log in to the application server using Windows Active Directory credentials, click
the Use Active Directory login credentials check box. By enabling the option,
you can bypass the authentication that is required using the user name and can
enable Single Sign-on (SSO).
Users with administrative as well as non-administrative privileges can use Single
Sign-on. The user with administrative privileges needs to right-click and select the
Run as administrator option while launching the NetBackup Administration
Console. Selecting this option enables the user to view the console with
administrative privileges.
Note the following points about SSO:
■ The SSO option is available only when both the NetBackup master server and
the NetBackup client are Windows hosts.
■ After the first successful login using SSO, the Use Active Directory login
credentials check box remains in the enabled state for the next login attempt
on the same server for the same client. This behavior is applicable for successful
SSO login instance for each master server.
■ The NetBackup Administration Console on a UNIX master server does not
show the check box to use the Active Directory credentials.
■ UNIX hosts can log in to the application server using the user name-based
authentication.
See “User Account Settings properties” on page 262.

Notes about using the NetBackup Administration Console

■ Veritas recommends that after you install or upgrade NetBackup server software,
you should uninstall older versions of the NetBackup Remote Administration
Console (Windows and Java) present on the host. If the native NetBackup
 Introducing NetBackup interfaces 40
About NetBackup administration interfaces

Administration Console for Windows is present, it is automatically uninstalled

when you install or upgrade the NetBackup server software.
■ Multiple base versions of the NetBackup Administration Console are installed
when you install NetBackup server software. For example, when you install or
upgrade to NetBackup 7.7.2, base versions from 7.0 through 7.7.2 of the console
are all installed.
■ To upgrade any of the multiple versions of consoles to a patch, you must first
install the base version of the Remote Administration Console. Use the installer
of the base version to install the Remote Administration Console. You must then
upgrade to the corresponding required patch of the Remote Administration
Console.
Upgrading directly to a patch version of the NetBackup Administration Console
from multiple versions of the consoles is not supported.
■ The NetBackup Administration Console is best viewed at a screen resolution
of 1280 X 1024 or higher. The minimum supported screen resolution to use the
console is 1024 X 768.
■ The NetBackup Administration Console does not support user-defined
characters (UDC) and vendor-defined characters (VDC) because of the
implementation of Java’s encoding converters.
■ On non-English versions of Windows and UNIX systems, the NetBackup
Administration Console may display non-US ASCII characters incorrectly.
This issue can lead to functional failures.
This issue results from a character encoding mismatch between the NetBackup
server and the NetBackup Administration Console. For a detailed description
of the configuration, refer to the following tech note on the Veritas Support
website:
[Link]
■ To use the NetBackup Administration Console on a Windows computer, the
Microsoft Windows UAC (User Access Control) feature must be disabled. See
the following link for instructions:
[Link]
Figure 1-2 shows the selection to install only the NetBackup Administration
Console.
 Introducing NetBackup interfaces 41
About NetBackup administration interfaces

Figure 1-2 Selection on the installation panel to install only the NetBackup
Administration Console

See “Accessing remote servers” on page 1124.

Administering remote servers of different versions

The NetBackup server installation provides multiple versions of the NetBackup
Administration Console to administer remote servers of different versions. When
starting the Administration Console, select the version of the console that is
compatible with the NetBackup server that you want to administer.
 Introducing NetBackup interfaces 42
About NetBackup administration interfaces

Alternatively, from the command line, you can use the jnbSA command with the -r
option to launch the console. For example, to connect to a 7.0 master server from
a 7.7.2 UNIX master server, enter the following command on the 7.7.2 master
server:
./jnbSA -r 7.0

If no -r option is specified, the default is the NetBackup version of the current

master server.

Note: To log on to any NetBackup Administration Console, your logon credentials

must be authenticated from the connecting master or media server. This requirement
is true whether or not NetBackup Access Control (NBAC) is in use.

Backward compatibility with triple-dot versions

The NetBackup Administration Console is backward-compatible between a patch
release (x.x.x.x) and a major (x.x) or minor release (x.x.x) that shares the same
first and second digits.
For example, the [Link] console is compatible with a 7.6 master server. However,
a NetBackup [Link] console cannot administer a [Link] master server. See
Figure 1-3 for various examples.
 Introducing NetBackup interfaces 43
Using the NetBackup Administration Console

Figure 1-3 Examples of supported and unsupported back-level console

configurations

[Link] [Link] [Link] [Link]

Yes No Yes No

7.6 [Link] 7.5 7.5

See “Accessing remote servers” on page 1124.

Using the NetBackup Administration Console

The NetBackup Administration Console provides a graphical user interface
through which the administrator can manage NetBackup. It runs on both the
Windows and the UNIX platforms.

Figure 1-4 NetBackup Administration Console

10 11

9
 Introducing NetBackup interfaces 44
Using the NetBackup Administration Console

Table 1-2 NetBackup Administration Console description

Description

1 The name of the currently selected master server.

The information in the NetBackup Administration Console applies to this server only.

2 Backup, Archive, and Restore

Administrators can use the Backup, Archive, and Restore utility to back up, archive, and restore files, directories,
and the formatted raw partitions that reside on the computer that is currently selected. Files can be restored at
any time. However, files can be backed up or archived only during the time periods that the administrator defines
within a schedule for user backups. Users can view the progress and final status of the operations performed.
Note: An archive is a special type of backup. During an archive, NetBackup first backs up the selected files,
then deletes the files from the local disk if the backup is successful. In this manual, references to backups also
apply to the backup portion of archive operations (except where otherwise noted).

Documentation for the NetBackup client is available as online Help from the Backup, Archive, and Restore
interface.

3 Activity Monitor

Displays the NetBackup job information. The Activity Monitor provides the control over the jobs, services,
processes, and drives.

4 NetBackup Management

The NetBackup Management contains many of the utilities to manage NetBackup:

Reports

Use to compile information to verify, manage, and troubleshoot NetBackup operations.

See “About the Reports utility” on page 1074.

 Introducing NetBackup interfaces 45
Using the NetBackup Administration Console

Table 1-2 NetBackup Administration Console description (continued)

Description

Policies

Use to create and specify the backup policies that define the rules for backing up a group of clients.

For example, the backup policy specifies when automatic backups occur for the clients that are specified in the
policy. The backup policy also specifies whether users can perform their own backups and when. The administrator
can define any number of backup policies, each of which can apply to one or more clients. A NetBackup client
must belong to at least one backup policy to be backed up.

See “About the Policies utility” on page 677.

Storage

Use to configure storage units, storage unit groups, storage lifecycle policies (SLPs), and windows for secondary
operations in SLPs.

See “About the Storage utility” on page 559.

Catalog

Use to create and configure a catalog backup, which is a special type of backup that NetBackup requires for its
own internal databases.

These databases, called the NetBackup catalog, are located on the NetBackup master and media server. The
catalog contains information on every client backup. Catalog backups are tracked separately from other backups
to ensure recovery in case of a server crash.
The Catalog utility is also used for the following actions:

■ To duplicate a backup image

■ To promote a backup image from a copy to the primary backup copy
■ To manually expire backup images
■ To import expired backup images or images from another NetBackup server
■ To search for a backup image to verify the contents of the media with what is recorded in the NetBackup
catalog

See “About the Catalog utility” on page 972.

Host Properties

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

See “About the NetBackup Host Properties” on page 68.

 Introducing NetBackup interfaces 46
Using the NetBackup Administration Console

Table 1-2 NetBackup Administration Console description (continued)

Description

5 SLP Windows

SLP Windows contains any schedules that are defined for secondary operations in a storage lifecycle policy.

A window can better define when the job for a secondary operation can run, making sure that the job does not
interfere with jobs of a higher priority.

6 Applications

Applications contains all discovered instances on SQL and Oracle clients and any manually added instances.
These instances are used to build an Oracle or a SQL Intelligent Policy.

For more information, see the NetBackup for Oracle Administrator’s Guide and the NetBackup for SQL Server
Administrator’s Guide.

7 Media and Device Management

Contains the utilities for managing the media and devices that NetBackup uses to store backups:

Device Monitor

Manages the drives, device paths, and service requests for operators.

Media

Adds and manages removable media.

Devices

Adds, configures, and manages storage devices.

Credentials
Adds, removes, and manages logon credentials for the following:

■ NDMP hosts (requires the NetBackup for NDMP license).

■ Storage servers (requires a NetBackup Data Protection Optimization Option license).

Credentials appears only if one of these license keys is installed.

8 Access Management

NetBackup administrators can protect a NetBackup configuration by defining who may access NetBackup and
what functions a user group can perform. Access Management is enabled when NetBackup Product Authentication
and Authorization and NetBackup Access Control (NBAC) is configured.

For more information about NetBackup Access Control, see the NetBackup Security and Encryption Guide.

9 Logging Assistant

The Logging Assistant is a tool that helps administrators configure, gather, and upload debug logs.

See “About the Logging Assistant” on page 1081.

 Introducing NetBackup interfaces 47
Using the NetBackup Administration Console

Table 1-2 NetBackup Administration Console description (continued)

Description

10 Additional licensed utilities appear under the main NetBackup nodes.

11 The Details pane contains the configuration wizards and details specific to the utility that is selected.

Note: A special search option is available for searching the text inside a table.
When any table is displayed in an active console window, users can type the search
text directly on the keyboard. The text is searched within the first column of the
table and the content is highlighted.

See “About security certificates for NetBackup hosts” on page 47.

See “Configuring log files for the NetBackup Administration Console” on page 54.
The NetBackup Administration Console menus are described in the online Help.

About security certificates for NetBackup hosts

NetBackup uses security certificates for authentication of NetBackup hosts for some
use cases. The NetBackup security certificates conform to the X.509 public key
infrastructure standard. A NetBackup Certificate Authority (CA) issues the
certificates.
By default, individual NetBackup master servers are provisioned with a security
certificate during a successful installation. Also, during a NetBackup push installation
to a Windows Server Failover Cluster (WSFC), security certificates are deployed
to all of the nodes in the failover cluster.
Other NetBackup use cases may require that you deploy a security certificate to
NetBackup hosts so that NetBackup functions correctly, as follows:

NetBackup master server cluster For a NetBackup master server in a cluster solution other
installation than WSFC, you must deploy a security certificate to all
of the nodes in the cluster.

See “Deploying a security certificate on a NetBackup

host ” on page 48.

Change Server operation in the For a Change Server operation to succeed, the target
NetBackup Administration NetBackup host must have a security certificate installed.
Console
See “Deploying a security certificate on a NetBackup
host ” on page 48.
 Introducing NetBackup interfaces 48
Using the NetBackup Administration Console

To use the NetBackup graphical To connect to a media server with the NetBackup
user interfaces to connect to Administration Console, the media server must have
media servers and clients a security certificate installed. Similarly, to connect to a
NetBackup UNIX or Linux client with the Backup, Archive,
and Restore user interface, the client must have a
security certificate installed.

See “Deploying a security certificate on a NetBackup

host ” on page 48.

NetBackup Access Control If NBAC is enabled on a NetBackup host, it requires a

(NBAC) security certificate. These certificates are automatically
deployed when you enable NBAC.

See the NetBackup Security and Encryption Guide:

[Link]

For cloud storage The NetBackup CloudStore Service Container requires

that a certificate be installed on the media server. If one
is not installed, the Service Container cannot start.

See the NetBackup Cloud Administrator’s Guide:

[Link]

Deploying a security certificate on a NetBackup host

NetBackup hosts may require a security certificate for authentication for various
purposes. If so, you must use a NetBackup command to deploy a certificate for
each host that requires one.
See “About security certificates for NetBackup hosts” on page 47.
The following are the procedures that you can use to deploy a security certificate
on NetBackup hosts:

Deploying a security certificate Use this procedure to deploy security certificates to all of
for a master server in a cluster the nodes in a NetBackup master server cluster. Exception:
Not required for a Microsoft Windows Server Failover
Cluster (WSFC) after a NetBackup push installation to the
WSFC.

See To deploy a security certificate for a NetBackup master

server in a cluster.
 Introducing NetBackup interfaces 49
Using the NetBackup Administration Console

Deploying a security certificate This procedure uses IP address verification to identify the
for media servers or clients target NetBackup host and then deploy the certificate.

With this procedure, you can deploy a certificate for an

individual host, for all media servers, or for all clients.

See To deploy a security certificate for media servers or

clients.

Creating a host identity and This procedure requires that you execute a command on
then deploying a security the NetBackup master server to create an identity for the
certificate for a media server or target host. Then, you must execute a command on the
client target host to obtain the certificate from the master server.

With this procedure, you can deploy a certificate for an

individual host.

See To create a host identity and then deploy a security

certificate for a media server or client.

Note: Deploying a security certificate is a one-time activity for a given NetBackup

host. You must be a NetBackup administrator to deploy certificates.

To deploy a security certificate for a NetBackup master server in a cluster

1 Run the following command on the active node of the master server cluster:
Windows: install_path\NetBackup\bin\admincmd\bpnbaz -setupat
UNIX: /usr/openv/netbackup/bin/admincmd/bpnbaz -setupat
2 Restart the NetBackup Service Layer service and the NetBackup Vault Manager
service on the active node of the master server.
 Introducing NetBackup interfaces 50
Using the NetBackup Administration Console

To deploy a security certificate for media servers or clients

1 Run the following command on the master server, depending on your
environment. Specify the name of an individual host, specify -AllMediaServers,
or specify -AllClients.
Windows: install_path\NetBackup\bin\admincmd\bpnbaz -ProvisionCert
host_name|-AllMediaServers|-AllClients

UNIX: /usr/openv/netbackup/bin/admincmd/bpnbaz -ProvisionCert

host_name|-AllMediaServers|-AllClients

NetBackup appliance (as a NetBackupCLI user): bpnbaz -ProvisionCert

Media_server_name

2 Restart the NetBackup Service Layer service on the master server.

No services need to be restarted if the target host is a NetBackup client.
To create a host identity and then deploy a security certificate for a media
server or client
1 Run the following command on the master server to create an identity for the
target NetBackup host.
Windows: install_path\NetBackup\bin\bpnbat –addmachine
target_hostname

UNIX: /usr/openv/netbackup/bin/bpnbat –addmachine target_hostname

Enter a password of your choice when prompted and make a note of it.
2 Run the following command on the target NetBackup host to obtain a certificate
from the master server and deploy it:
Windows: install_path\NetBackup\bin\bpnbat –loginmachine
UNIX: /usr/openv/netbackup/bin/bpnbat –loginmachine
Enter the master server name as the authentication broker name when
prompted. Enter the same computer name and password that were used to
create the target host identity on the master server.

Note: If a target host has multiple host names, repeat the steps for each host
name.

Verifying the NetBackup Certificate Authority (CA)

The NetBackup Administration Console or the Backup, Archive, and Restore
user interface communicates with NetBackup hosts (master server, media server,
 Introducing NetBackup interfaces 51
Using the NetBackup Administration Console

or client) over a secure channel. This channel is secured using a NetBackup host
security certificate that is issued by the NetBackup Certificate Authority (CA).
The following message displays when you attempt to connect to a NetBackup host
whose security certificate was issued by a CA that is not in your NetBackup trust
store.

Note: Once you trust the CA certificate, the message is not displayed again when
you connect to any NetBackup host in the same NetBackup domain.

The authenticity of the Certificate Authority can be verified using the following
procedure:
 Introducing NetBackup interfaces 52
Using the NetBackup Administration Console

To verify the NetBackup Certificate Authority

1 Log in to the AT Broker host (master server) that owns this certificate and run
the following command:
On Windows:
install_path\NetBackup\sec\at\bin\ vssat showcred -p nbatd

On UNIX:
/usr/openv/netbackup/sec/at/bin/vssat showcred –p nbatd

The details of the root CA certificate are displayed.

2 Check the output to confirm that the Certificate Hash matches the Root
Certificate Authority fingerprint that is contained in the message.
For example, if the Root Certificate Authority fingerprint in the message
displays the following fingerprint:
[Link]

The Certificate Hash field should display the following:

158dca81b62adc8d0a528381ca24cb22b6d92508

Verifying a security certificate

Use the following procedure to verify that NetBackup security is deployed.
 Introducing NetBackup interfaces 53
Using the NetBackup Administration Console

To verify the security certificate

1 Check the contents of the follwing directory on the NetBackup host:
On Windows:
install_path\NetBackup\var\VxSS\credentials

On UNIX:
/usr/openv/var/vxss/credentials

The directory might list multiple certificate files. A single host can have a
certificate for each name that it is referred to as.
For example, the NetBackup host can have a fully qualified name
([Link]) or it can also be referred to as v-123. The host would have
two certificates.
2 for each certificate file, run the following command to view the details of the
certificate:

Note: Expired or invalid certificates can cause connection failures.

On Windows
install_path\NetBackup\bin\bpnbat -whoami -cf file_name

On UNIX:
/usr/openv/netbackup/bin/bpnbat -whoami -cf file_name

For example, bpnbat -whoami –cf [Link]

Verify the contents of the certificate. If both the host name and the expiration
date of the certificate are correct, the certificate is valid. If the certificate has
expired, you must generate a new certificate.

Standard and user toolbars

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

About customizing the NetBackup Administration Console

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

Configuring log files for the NetBackup Administration Console

You can configure the logging options for the NetBackup Administration Console.

Caution Most of the logging options degrade NetBackup Administration Console

performance and may write large amounts of data to the log files, possibly
filling up the file system. Consider the following items that may help prevent
filling up the file system on which NetBackup is installed:

■ Use an environment variable named JNB_LOG as follows:

■ Set the variable to a log file pathname on a file system that has enough
space for the log files.
Delete the environment variable when you stop logging NetBackup
Administration Console information.
■ On UNIX, set the variable to /dev/tty. The /dev/tty setting writes
the log information to the console window.
■ On UNIX: Use the -l option to the jnbSA or jbpSA command to specify
one of the following settings:
■ To a log file pathname on a file system that has enough space for the
log file.
■ To /dev/tty. The /dev/tty setting writes the log information to
the console window.

The log file directories and names are described in a different topic.
See “NetBackup Administration Console log files” on page 55.
To configure logging for the NetBackup Administration Console
1 In the NetBackup Administration Console, click View > Options to open
the Options dialog box.
2 Click the Logging tab.
3 Select the information that you want to write to the log file:
 Introducing NetBackup interfaces 55
Using the NetBackup Administration Console

Enable command Enable this option to capture the output from the commands that
logs the NetBackup-Java application server (bpjava-susvc) runs.

See “About the Processes tab” on page 1057.

Note: The output from each command instance is limited to 500
lines in the log file.

Enable command Enable this option to capture command-line activity into the log
line logs file. NetBackup writes information about the commands that reside
in the following directories:

■ Windows:
■ install_path\Veritas\NetBackup\bin
■ install_path\Veritas\NetBackup\bin\admincmd
■ install_path\Veritas\Volmgr\bin
■ UNIX:
■ /usr/openv/netbackup/bin
■ /usr/openv/netbackup/bin/admincmd
■ /usr/openv/volmgr/bin

Note: The NetBackup Administration Console often uses APIs

and not the NetBackup commands to get data or update data. In
those cases, information is not written to the log file.

Add date and Enable this option to include a timestamp when NetBackup writes
timestamp to logs information to the log file.

Enable job try Enable this option to capture logging information from the
logs NetBackup Activity Monitor.

Verbosity Use this option to set the verbosity of the logs. Five (5) is the
highest logging level.

4 Click OK.
See “Using the NetBackup Administration Console” on page 43.

NetBackup Administration Console log files

The NetBackup Administration Console writes information into log files in the
following directories:
 Introducing NetBackup interfaces 56
Using the NetBackup Administration Console

Windows install_path\NetBackup\logs\user_ops\nbjlogs

For the NetBackup Remote Administration Console, the log files

are in the following directory:

install_path\Veritas\Java\logs

UNIX /usr/openv/netbackup/logs/user_ops/nbjlogs

The log file names have the following format:

Windows [Link]

The log files always begin with jbp. The following items describe the
other components of the log file name:

■ yyyy: Year
■ mm: Month
■ dd: Day
■ thh: Hour
■ tmm: Minute
■ tss: Second
■ ths: Half-second

The following is an example:

[Link]

UNIX jbp.`whoami`.gui.$$.log

The log files always begin with jbp. The following items describe the
other components of the log file name:

■ gui: Either jpbSA (Backup, Archive, and Restore interface) or

jnbSA (NetBackup Administration Console).
■ $$: The ID of the process for which log information was written when
the log file was created.

The following is an example:

[Link]

NetBackup creates a new log file when the current log file reaches a certain size.
The size varies depending on many factors. Those factors include the number of
jobs that are active, the amount of activity the Administration Console performs,
and others.
Log file retention corresponds to the retention level that you can configure in the
master server host properties Logging screen.
See “Logging properties” on page 170.
 Introducing NetBackup interfaces 57
NetBackup configuration wizards

See “Configuring log files for the NetBackup Administration Console” on page 54.

NetBackup configuration wizards

The easiest way to configure NetBackup is to use the configuration wizards available
in the NetBackup Administration Console. The wizards help configure the
properties of a NetBackup environment.
The wizard selection varies in the pane on the right, depending on which NetBackup
utility is selected in the left of the screen.

Table 1-3 Configuration wizards

Wizard Description

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

■ Device Configuration Wizard

■ Volume Configuration Wizard
■ Catalog Backup Wizard
■ Policy Configuration Wizard

Configure more advanced properties through the individual utilities.

Note: Do not use the Getting Started Wizard to configure policies for Replication
Director.

Device Configuration Wizard Click Configure Storage Devices to configure NetBackup to use robotic tape
libraries and tape drives.

Storage Server Configuration Click Configure Disk Storage Servers to create the servers that manage disk
Wizard storage.

The wizard appears if a NetBackup Data Protection Optimization Option license

is installed.

Cloud Storage Server Click Configure Cloud Storage Servers to add or configure a cloud provider.
Configuration Wizard
For more information, see the NetBackup Cloud Administrator's Guide.

Disk Pool Configuration Wizard Click Configure Disk Pool to create pools of disk volumes for backup by one or
more media servers.

The wizard appears if a NetBackup Data Protection Optimization Option license

is installed.

Volume Configuration Wizard Click Configure Volumes to configure removable media to use for backups.
 Introducing NetBackup interfaces 58
Running the Troubleshooter

Table 1-3 Configuration wizards (continued)

Wizard Description

Catalog Backup Wizard Click Configure the Catalog Backup to set up catalog backups. Catalog backups
are essential to recover data in the case of a server failure or crash.

Policy Configuration Wizard Click Create a Policy to set up one of the policy types:

■ A policy to back up file systems, databases, or applications.

■ A policy to protect VMware or Hyper-V virtual machines.
■ A policy to back up NDMP hosts.
■ A policy to back up Oracle data.

Note: Do not use the Policy Configuration Wizard to configure policies for
Replication Director.

Import Images Wizard This wizard is available only on computers running Windows. Click Import Images
to import NetBackup images in a two-part process.

See “About importing backup images” on page 987.

Catalog Recovery Wizard Click Recover the Catalog to recover a catalog backup in a disaster recovery
situation.

For more information about NetBackup disaster recovery, see the NetBackup
Troubleshooting Guide.

Running the Troubleshooter

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

To understand the status of a ■ In the left pane, click Activity Monitor.

job in the Activity Monitor ■ In the right pane, select the Jobs tab at the bottom
of the pane.
■ Select a job from the list.
 Introducing NetBackup interfaces 59
Running the Troubleshooter

To understand the status of a ■ In the left pane, expand NetBackup Management

job in a report > Reports.
■ In the left pane, click the name of the report you want
to run.
For some reports, you must first expand a report
group, and then click the name of the report.
■ In the right pane, click Run Report.
■ Select a job from the list that is generated.

To look up a status code Go to step 2.

2 Click Help > Troubleshooter.

The dialog box that appears describes the status code on the Problem tab.
Possible solutions can be found on the Troubleshoot tab. The Veritas Support
tab displays the web address of Veritas Support or the URL to a tech note that
addresses the specific error code.
3 If no explanation appears, enter a status code and click Lookup.
The Troubleshooter provides assistance for NetBackup codes only. Assistance
with Media and Device Management codes is available by using NetBackup
online Help and searching for the particular status code.
See “Viewing job details in the Activity Monitor” on page 1040.
See “About the Jobs tab” on page 1038.
See “Copying report text to another document” on page 1078.
See “Printing a report” on page 1079.
See “Saving or exporting a report” on page 1079.
 Chapter 2
Administering NetBackup
licenses
This chapter includes the following topics:

■ About administering NetBackup licenses

About administering NetBackup licenses

License keys are added when the software is installed. Licenses can be added later
in the License Key dialog box for separately-priced options.

Note: Restart the NetBackup Administration Console after any license updates.

Note: Perform a manual catalog backup after the license keys are updated.
An immediate, manual catalog backup prevents stale keys from being restored in
case a catalog restore is necessary before the next scheduled catalog backup.
See “Backing up NetBackup catalogs manually” on page 899.

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

Add a new license. Adding NetBackup license keys

Print a license. Printing a NetBackup license key list

Delete a license. Deleting NetBackup license keys

View the properties of one Viewing NetBackup license key properties

license.
 Administering NetBackup licenses 61
About administering NetBackup licenses

Export the license list. Exporting NetBackup license keys

On computers running UNIX, the license key utility is a menu-driven interface and
can also be used to access licenses.
Starting the NetBackup license key utility on a UNIX computer

Accessing license keys for a NetBackup server

Use the following procedure to access license keys for a NetBackup server.
To access license keys for a NetBackup server
1 To view the license keys of the current server:
In the NetBackup Administration Console, in the toolbar, click Help > License
Keys.
To view the license keys of another server:
Select File > Change Server. Click OK to launch a new console. Enter the
host name of another server. Enter a user name and password and click Login.
In the new console, select Help > License Keys.
2 Select the license details to view as follows:

Summary of Displays a summary of the active features that are licensed on

active licensed this server. This view lists each feature and the number of
features instances of the feature that are licensed.

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

■ Each license key

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

Adding NetBackup license keys

Use the following procedure to add NetBackup license keys to the selected server.
To add new license keys to the selected server
1 In the toolbar in the NetBackup Administration Console, click Help > License
Keys.
2 Click New.
 Administering NetBackup licenses 62
About administering NetBackup licenses

3 Enter the license key and click Add or OK.

If you added a license on a computer running UNIX, restart all of the NetBackup
utilities. Restart the NetBackup Administration Console as well.
4 Perform a manual catalog backup after the license keys are updated.
An immediate, manual catalog backup prevents stale keys from being restored
in case a catalog restore is necessary before the next scheduled catalog
backup.
See “Backing up NetBackup catalogs manually” on page 899.
You can add license keys to a different NetBackup server:
Select File > Change Server. Click OK to launch a new console. Enter the host
name of another server. Enter a user name and password and click Login. In the
new console, select Help > License Keys.

Printing a NetBackup license key list

Use the following procedure to print a list of license keys that are installed on a
NetBackup server.
To print a list of license keys
1 In the toolbar in the NetBackup Administration Console, click Help > License
Keys.
2 Select the license key you want to print. If no selection is made, all licenses
print.
The printed information includes the following:
■ License key
■ Name of the host
■ Date the key was added
■ Name of the product
■ Number of instances
■ Name of the feature
■ Whether or not the license is valid
■ Expiration date for the license

3 Click Print.
4 Make the print selections and click OK.
 Administering NetBackup licenses 63
About administering NetBackup licenses

Deleting NetBackup license keys

Use the following procedure to delete a license key that is installed on a NetBackup
server.
To delete a license key
1 In the toolbar in the NetBackup Administration Console, click Help > License
Keys.
2 Select the license key you want to delete from the license key list. If the key
has more than one feature, all the features are listed in the dialog box.
3 Click Delete.
4 Click OK or Yes to delete the key and all features that are associated with the
key. The license key cannot be restored.
If you deleted a license on a computer running UNIX, restart all of the
NetBackup utilities. Restart the NetBackup Administration Console as well.

Viewing NetBackup license key properties

Use the following procedure to view the properties of a NetBackup license key.
To view the properties of a NetBackup license key
◆ In the toolbar in the NetBackup Administration Console, click Help > License
Keys.
Select one license and click Properties.

Exporting NetBackup license keys

Use the following procedure to export NetBackup license keys.
To export NetBackup license keys
1 In the toolbar in the NetBackup Administration Console, click Help > License
Keys.
2 Click Export.
3 Enter the path and the file name where you want the key properties of all
licenses to be exported.
4 Click Save.
The exported file contains a list of each license key, along with the:
■ Name of the host
■ Date the license was added
■ Name of the product
 Administering NetBackup licenses 64
About administering NetBackup licenses

■ Number of instances
■ Name of the feature
■ Whether or not the license is valid
■ Expiration date for the license

Starting the NetBackup license key utility on a UNIX

computer
Use the following procedure to start the NetBackup license key utility on a computer
running UNIX.
To start the NetBackup license key utility on a computer running UNIX
1 From the command line, run
/usr/openv/netbackup/bin/admincmd/get_license_key

2 At the prompt, enter one of the following menu selections, then press Enter:
■ Type A to add a new license key, then type the license key at the prompt.
■ Type D to delete a license from the list, then type the license key at the
prompt.
■ Type F to list only the licenses that are currently active. Expired licenses
do not appear in this listing. Specify a local or a remote host.
■ Type L to list all registered licenses—active or inactive. Specify a local or
a remote host.
■ Type H for help on the License Key Utility.
■ Type q to quit the utility.
 Section 2
Configuring hosts

■ Chapter 3. Configuring Host Properties

■ Chapter 4. Configuring server groups

■ Chapter 5. Configuring host credentials

■ Chapter 6. Managing media servers

 Chapter 3
Configuring Host
Properties
This chapter includes the following topics:

■ About the NetBackup Host Properties

■ Access Control properties

■ Active Directory host properties

■ Bandwidth properties

■ Busy File Settings properties

■ Clean-up properties

■ Client Name properties

■ Client Attributes properties

■ Client Settings properties for UNIX clients

■ Client Settings properties for Windows clients

■ Credential Access properties

■ Data Classification properties

■ Default Job Priorities properties

■ Distributed application restore mapping properties

■ Encryption properties

■ Enterprise Vault properties

 Configuring Host Properties 67

■ Enterprise Vault Hosts properties

■ Exchange properties

■ Exclude Lists properties

■ Fibre Transport properties

■ Firewall properties

■ General Server properties

■ Global Attributes properties

■ Logging properties

■ Login Banner Configuration properties

■ Lotus Notes properties

■ Media properties

■ NDMP Global Credentials properties

■ Network properties

■ Network Settings properties

■ Port Ranges properties

■ Preferred Network properties

■ Resilient Network properties

■ Resource Limit properties

■ Restore Failover properties

■ Retention Periods properties

■ Scalable Storage properties

■ Servers properties

■ SharePoint properties

■ SLP Parameters properties

■ Throttle Bandwidth properties

■ Timeouts properties

■ Universal Settings properties

 Configuring Host Properties 68
About the NetBackup Host Properties

■ User Account Settings properties

■ UNIX Client properties

■ UNIX Server properties

■ VMware Access Hosts properties

■ Windows Client properties

■ Configuration options not found in the Host Properties

■ About using commands to change the configuration options on UNIX clients

and servers

■ Configuration options for NetBackup servers

■ Configuration options for NetBackup clients

About the NetBackup Host Properties

The configuration options within the Host Properties let an administrator customize
NetBackup to meet specific site preferences and requirements.
In most NetBackup environments, the Host Properties default settings provide
satisfactory results and can be left at the default setting.
Figure 3-1 shows the Host Properties in the NetBackup Administration Console.

Figure 3-1 Host Properties utility in the NetBackup Administration Console

2 4

5
 Configuring Host Properties 69
About the NetBackup Host Properties

Table 3-1 Host Properties utility

Number Description

1 The menu toolbar.

2 The standard NetBackup toolbar.

See “Standard and user toolbars” on page 53.

3 The name of the currently selected master server.

4 The user toolbar is specific to the Host Properties utility.

By default, the Host Properties user toolbar includes the following buttons:

■ Select a host in the right pane and click Connect to connect to that host.
■ Select a host in the right pane and click Properties to view the properties of
that host.
See “Connecting to a host to view the host properties” on page 70.
■ Click Configure media server to name a media server and view its properties.
■ Click Configure Client to name a client and view its properties.

You can select which buttons appear on the user toolbar.

See “Standard and user toolbars” on page 53.

5 Right-click in the right pane to view the shortcut menu.

To change the properties of another client or server, the NetBackup server where
you logged on using the NetBackup Administration Console must be in the
Servers list on the other system.
See “Servers properties” on page 236.
See “Allow access to another server” on page 1121.
For example, if you logged on to server_1 using the NetBackup Administration
Console and want to change a setting on client_2, client_2 must include server_1
in its Servers list.

Note: All updates to a destination host fail if Allow server file writes is not enabled
on the destination host. This property is located in the Universal Settings properties.
See “Universal Settings properties” on page 258.

Generally, these options are configured in the NetBackup Administration Console,

under Host Properties. However, some options cannot be configured by using the
NetBackup Administration Console.
See “Configuration options not found in the Host Properties” on page 268.
 Configuring Host Properties 70
About the NetBackup Host Properties

Methods to set the NetBackup configuration options

A NetBackup administrator can use one of the following methods to read or set the
default configuration options or to change those options that do not appear in the
Host Properties:

Table 3-2 NetBackup Host Properties configuration methods

Method Description

NetBackup Administration Most properties are listed in the NetBackup Administration Console in the Host
Console interface Properties. To navigate to the various properties, select NetBackup Management >
Host Properties. Depending on the host to be configured, select Master Servers,
Media Servers, or Clients.

See “About the NetBackup Host Properties” on page 68.

Command line Use the nbgetconfig command or bpgetconfig command to obtain a list of
configuration entries. Then use nbsetconfig or bpsetconfig to change the options
as needed.

These commands update the appropriate configuration files on both Windows (registry)
and UNIX ([Link] file) master servers and clients.

Use the nbemmcmd command to modify some options on hosts.

Detailed information on these commands is available in the NetBackup Commands

Reference Guide.

[Link] file The [Link] file contains configuration entries for media and device management.

See the NetBackup Administrator's Guide, Volume II for more information.

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

Connecting to a host to view the host properties

The NetBackup Administration Console displays properties for NetBackup master
servers, media servers, and clients under Host Properties.
Use the following procedure to connect and view host properties of master server,
media server, or client.
To connect and view host properties of master server, media server, or client
1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties.
2 In the left pane, select Master Servers, Media Servers, or Clients.
3 In the right pane, perform one of the following to connect to a host:
 Configuring Host Properties 71
About the NetBackup Host Properties

■ Highlight the host by selecting the row. The host is connected after a delay
of approximately 3 seconds. If you select multiple rows, connection to the
hosts is not established.
■ Right-click a host and select Connect. If you select multiple rows right-click
and select Connect by pressing the Ctrl key, connection to all the hosts is
established. If the host is already connected, the Connect option is gray.

Note: When you double-click a host that is not connected to view its host
properties, an intermittent Loading Data dialog box is displayed. This dialog
box contains an Interrupt option. When you click Interrupt, the Loading Data
dialog box closes. The connection to the host continues in the background.
However, the Host Properties dialog box is not displayed.

Changing the host properties on multiple hosts at the same time

You can change the host properties for multiple hosts at one time. This can be done
by one of the following procedures:
■ Changing multiple hosts in the Host Properties
■ Changing multiple hosts in the Policies utility

Changing multiple hosts in the Host Properties

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

The following information about each selected host appears:

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

5 Make changes as necessary.

6 Click OK to save the changes for all hosts and to close the dialog box.

Changing multiple hosts in the Policies utility

To simultaneously change the properties on multiple hosts from Summary
of All Policies
1 In the NetBackup Administration Console, navigate to Policies > Summary
of All Policies in the middle pane.
2 Under Summary of All Policies, expand Clients.
3 In the right pane, hold down the Shift key to select multiple clients.
4 With multiple hosts still selected, right-click and select Host Properties.
5 Change the client properties in the dialog box.
6 Click OK to apply the changes to all hosts and to close the dialog box.

Property states for multiple hosts

The Host Properties dialog boxes use the following conventions regarding multiple
host selections:
 Configuring Host Properties 73
About the NetBackup Host Properties

Title of dialog box If a dialog box contains a Selected Host (or similarly named)
box, all controls reflect the values for the host currently
selected in the Selected Host box.

If a dialog box does not contain a Selected Host (or similarly

named) box, settings of all the selected hosts are combined
to arrive at a value that is displayed to the user.

Option selection When multiple hosts are selected, no options appear selected.
Selecting any option updates the setting on all selected hosts.
To leave each host configured independently, do not select
any option while multiple hosts are selected.

Number spinners When multiple hosts are selected, number spinners appear
blank. Selecting any value updates the setting on all selected
hosts. To leave each host configured independently, do not
select any option while multiple hosts are selected.

Check box states The host property check boxes may appear in one of the
following states:

■ Selected (checked) if the attribute has been set the same

for all selected hosts. To set the property on all selected
hosts, select the check box.
■ Clear (unchecked) if the property has been set the same
for all selected hosts. To clear the property on all selected
hosts, clear the check box.
■ Gray check if the property is set differently on the selected
hosts. To leave the property unchanged, set the box to a
gray check.

Edit field states If the property contains a text field for specifying a value, the
field may be in one of the following states:

■ The field may contain a value if the property has the same
value for all selected hosts.
■ The field may be empty or indicate <<Multiple Entries>>
if the property was not set the same for all selected hosts.
In this case, when the cursor is moved a field, a small
notice appears at the bottom of the dialog box noting that
the value is different on the selected hosts.

Note: In a clustered environment, host properties must be made on each node of

the cluster separately.

If the focus is on a setting that is set differently between the selected hosts, the
following statement appears at the bottom of the dialog box:
 Configuring Host Properties 74
About the NetBackup Host Properties

This value is different on the selected hosts.

This notice is especially helpful regarding differences in text field settings.
If the selected hosts are of various operating systems, none of the operating
system-specific information appears.
For example, select a Linux client and a Windows client. Neither the Windows
Client properties nor the UNIX Client properties appear in the Host Properties. If
all the selected hosts are of the same operating system, the corresponding properties
node appears.

Exporting host properties

Use the following procedure to export the properties of a host.
To export the properties of a host
1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Master Servers, Media Servers, or Clients.
2 Select a host. If you want to select multiple hosts, hold down the Shift key and
select another host.
3 Click File > Export.
4 In the Export dialog box, name the file, browse to the directory where you want
to save it, and click Save.

Standard host property dialog box options

The following options are available in every host property dialog box.

Defaults Click Defaults to set all the properties in the current dialog
box to the default values.
Note: If you have enabled the Logging for critical processes
option on the Logging properties dialog box, clicking the
Defaults button does not modify the Logging for critical
processes and Keep logs up to GB options.

While changing the logging properties for multiple hosts, if

the Logging for critical processes option on one of the hosts
is enabled, clicking the Defaults button does not modify the
Logging for critical processes and Keep logs up to GB options
of any host.

See “Logging properties” on page 170.

 Configuring Host Properties 75
Access Control properties

OK Click OK to apply all changes since Apply was last clicked.

OK also closes the dialog box.

Cancel Click Cancel to cancel the changes that were made since
the last time changes were applied.

Apply Click Apply to save changes to all of the properties for the
selected host(s).

Help Click Help for information on the properties that appear in

the current dialog box.

Access Control properties

Use the Access Control host properties in the NetBackup Administration Console
to configure NetBackup Authentication and Authorization. The properties apply to
currently selected master servers, media servers, and clients.
The following tabs may display:
■ Authentication Domain tab
See “Authentication Domain tab of the Access Control properties” on page 76.
■ Authorization Service tab
See “Authorization Service tab of the Access Control properties” on page 78.
■ Network Attributes
See “Network Attributes tab of the Access Control properties” on page 79.
The tabs that display depend on whether the host that is selected is a master server,
a media server, or a client.
The NetBackup Product Authentication and Authorization property displays,
regardless of which tab is selected. It determines whether the local system uses
access control and how the system uses it.
The NetBackup Product Authentication and Authorization property contains
the following options.

Table 3-3 NetBackup Product Authentication and Authorization property

options

Option Description

Required Specifies that the local system should accept requests only from the remote systems that use
NetBackup authentication and authorization. Connections from the remote systems that do not
use NetBackup authentication and authorization are rejected. Select Required if all systems
are at NetBackup 5.0 or later and maximum security is required.
 Configuring Host Properties 76
Access Control properties

Table 3-3 NetBackup Product Authentication and Authorization property

options (continued)

Option Description

Prohibited Specifies that the local system should reject connections from any remote system that uses
NetBackup authentication and authorization. Select Prohibited if the network is closed and
maximum performance is required.

Automatic Specifies that the local system should negotiate with the remote system about whether to use
NetBackup authentication and authorization. Select Automatic if the network contains mixed
versions of NetBackup.

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

Authentication Domain tab of the Access Control properties

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

Figure 3-2 Authentication Domain tab

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

Table 3-4 Authentication Domain tab properties

Property Description

Available Brokers Select a broker, then click Find to list all of

the available authentication domains.

Available Authentication Domains list List of available authentication domains.

Add button Select the authentication domain(s) that this

host can use and click Add.

Selected Authentication Domains list List of the authentication domains that are
selected for the host to use.
 Configuring Host Properties 78
Access Control properties

Table 3-4 Authentication Domain tab properties (continued)

Property Description

Remove button Select the authentication domain(s) that you

no longer want to use and click Remove.

Authorization Service tab of the Access Control properties

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

Figure 3-3 Authorization Service tab

The Authorization Service tab contains the following properties, which you can
configure for a master or a media server.
 Configuring Host Properties 79
Access Control properties

Table 3-5 Authorization Service property options

Option Description

Host name Specifies the host name or IP address of the authorization service.

Customize the port number of the Specifies a nonstandard port number. Select Customize the port
authorization service number and enter the port number of the authorization service.

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

Network Attributes tab of the Access Control properties

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

Figure 3-4 Network Attributes tab

 Configuring Host Properties 80
Access Control properties

The Network Attributes tab on the Access Control dialog box contains the
following properties:

Networks The Networks property indicates whether specific networks can or cannot use NetBackup
authentication and authorization with the local system. The names on the list are relevant
only if the NetBackup Product Authentication and Authorization property in the Access
Control dialog box is set to Automatic or Required.

Veritas recommends setting the master server NetBackup Product Authentication and
Authorization property to Automatic until the clients are configured for access control. Then,
change the NetBackup Product Authentication and Authorization property on the master
server to Required.

If a media server or client does not define a NetBackup Authentication and Authorization
network, it uses the networks of its master server.

Click Add to add a network to the Network list.

Click Add to All to add a network to all currently selected hosts in the Network list.

Select a network name and click Remove to remove a network from the Network list.

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

Add Network dialog box

The Add Network dialog box contains the following properties.

Table 3-6 Add Network dialog box properties

Property Description

Host/Domain Indicates whether the network to be added is a Host name or a Domain name.

Host Details Specifies that if the network is a host, one of the following items must be entered:

■ The host name of the remote system. ([Link])

■ The IP address of the remote system. ([Link])
 Configuring Host Properties 81
Active Directory host properties

Table 3-6 Add Network dialog box properties (continued)

Property Description

Domain Details ■ Domain Name/IP

Enter a dot that is followed by the Internet domain name of the remote systems. (.domain)
or the network of the remote system, followed by a dot. (10.0.0.)
■ If the domain is specified by IP, select one of the following items:
■ Bit count
Indicates that the mask is based on bit count. Select from between 1 and 32.
For example: Mask [Link]/16 has the same meaning as subnet mask
[Link]:255:255:0.0
■ Subnet mask
Select to enter a subnet mask in the same format as the IP address.

Figure 3-5 Add Network dialog box

Active Directory host properties

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

Figure 3-6 Active Directory dialog box

The Active Directory dialog box contains the following properties.

Table 3-7 Active Directory dialog box properties

Property Description

Perform consistency check before backup Checks snapshots for data corruption. Applies only to snapshots that
when using Microsoft Volume Shadow Copy the Microsoft Volume Shadow Copy Services (VSS) performs.
Service snapshot provider
If corrupt data is found and this option is not selected, the job fails.

See “Windows Open File Backup tab of the Client Attributes

properties” on page 101.

Continue with backup if consistency check Continues the backup job even if the consistency check fails.
fails
It may be preferable for the job to continue, even if the consistency
check fails. For example, a backup of the database in its current state
may be better than no backup at all. Or, it may be preferable for the
backup of a large database to continue if it encounters only a small
problem.
 Configuring Host Properties 83
Bandwidth properties

Bandwidth properties
Use the Bandwidth properties to specify network bandwidth limits for the NetBackup
clients of the selected server.

Note: The Bandwidth properties apply only to IPv4 networks. Use the Throttle
Bandwidth properties to limit IPv6 networks.
See “Throttle Bandwidth properties” on page 254.

The actual limiting occurs on the client side of the backup connection. The bandwidth
limits only restrict bandwidth during backups. By default, the bandwidth is not limited.
The Bandwidth properties apply to currently selected master servers.

Figure 3-7 Bandwidth dialog box

To manage entries in the Bandwidth dialog box, select one of the following buttons.

Add Adds an entry to the bandwidth table for each of the selected clients.
 Configuring Host Properties 84
Bandwidth properties

Change Changes an entry to the bandwidth table for each of the selected
clients.

Remove Removes the selected entry from the bandwidth table.

When a backup starts, NetBackup reads the bandwidth limit configuration as

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

Bandwidth limit usage considerations and restrictions

Some usage restrictions apply to the bandwidth limit settings in the Bandwidth
dialog box. The following table lists the restrictions and describes the specific
behaviors that you may need to consider.

Table 3-8 Bandwidth limit usage considerations and restrictions

Client or operation Bandwidth limit behavior or

restrictions

■ Standard Bandwidth limit is meant primarily for file

■ MS-Windows system backups using Standard and
MS-Windows policies. It is not implemented
for most other policy and client types.

Local backups If a server is also a client and data does not

go over the network, bandwidth limits have
no effect on local backups.

Setting required bandwidth Bandwidth limits restrict maximum network

usage and do not imply required bandwidth.
For example, if you set the bandwidth limit
for a client to 500 kilobytes per second, the
client can use up to that limit. It does not
mean, however, that the client requires 500
kilobytes per second.
 Configuring Host Properties 85
Busy File Settings properties

Table 3-8 Bandwidth limit usage considerations and restrictions (continued)

Client or operation Bandwidth limit behavior or

restrictions

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

Add Bandwidth Settings dialog box for Bandwidth properties

The Add Bandwidth Settings and the Change Bandwidth Settings dialog boxes
contain the following properties.

From Host Specifies the beginning of the IP address range of the

clients and networks to which the entry applies. For
example: [Link]

To Host Specifies the end of the IP address range of the clients

and networks to which the entry applies. For example:
[Link]

Bandwidth (KB/Sec) Specifies the bandwidth limitation in kilobytes per second.

A value of 0 disables the limits for an individual client or
the range of IP addresses covered by the entry. For
example, a value of 200 indicates 200 kilobytes per second.

Busy File Settings properties

The Busy File Settings properties in the NetBackup Administration Console
apply to currently selected UNIX clients. The Busy File Settings properties define
what occurs when NetBackup encounters a busy file during a backup of a UNIX
client.
 Configuring Host Properties 86
Busy File Settings properties

Figure 3-8 Busy File Settings dialog box

The Busy File Settings dialog box contains the following properties.

Table 3-9 Busy File Settings dialog box properties

Property Description

Working directory Specifies the path to the busy-files working directory. On a UNIX client, the value in the
user’s $HOME/[Link] file takes precedence if it exists. By default, NetBackup creates
the busy_files directory in the /usr/openv/netbackup directory.

Operator's email Specifies the recipient of the busy-file notification message when the action is set to Send
address email. By default, the mail recipient is the administrator. On a UNIX client, the value in the
user’s $HOME/[Link] file takes precedence if it exists. By default,
BUSY_FILE_NOTIFY_USER is not in any [Link] file and the mail recipient is root.

Process busy files Enables busy files to be processed according to the host property settings. NetBackup
follows the Busy File Settings if it determines that a file changes during a backup. By
default, Process busy files is not enabled and NetBackup does not process the busy files.

Additional information about busy file processing is available in the NetBackup

Administrator’s Guide, Volume II.
 Configuring Host Properties 87
Busy File Settings properties

Table 3-9 Busy File Settings dialog box properties (continued)

Property Description

File action file list Specifies the absolute path and file name of the busy file. The metacharacters *, ?, [], [ - ]
can be used for pattern matching of file names or parts of file names.

Add Adds a new file entry. Enter the file and path directly, or browse to select a file.

Add to All Adds a new file entry for all of the clients currently selected. Enter the file and path directly,
or browse to select a file.

Remove Removes the selected file from the file action list.

Busy file action The following options specify which action to take when busy-file processing is enabled.
On a UNIX client, the value in the user’s $HOME/[Link] file takes precedence if it exists.

■ Send email sends a busy sends a busy file notification message to the user that is
specified in Operator’s email address.
■ Retry the backup retries the backup on the specified busy file. The Retry count value
determines the number of times NetBackup tries a backup.
■ Ignore excludes the busy file from busy file processing. The file is backed up, then a
log entry that indicates it was busy appears in the All Log Entries report.

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

Activating the Busy File Settings in host properties

To activate the settings in the Busy File Settings host properties, use the following
procedure.
To activate Busy File Settings
1 Copy the bpend_notify_busy script:

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

to the path:

/usr/openv/netbackup/bin/bpend_notify

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

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

Figure 3-9 Clean-up dialog box

The Clean-up dialog box contains the following properties.

 Configuring Host Properties 89
Clean-up properties

Table 3-10 Clean-up dialog box properties

Property Description

Keep true image restoration Specifies the number of days to keep true image restore information on disk.
information After the specified number of days, the images are pruned (removed). Applies
to all policies for which NetBackup collects true image restore information.
The default is one day.
When NetBackup performs a true image backup, it stores the following
images on the backup media:

■ Backed up files
■ True image restore information

NetBackup also stores the true image restore information on disk in the
following directories:

On Windows:

install_path\NetBackup\db\images

On UNIX:

/usr/openv/netbackup/db/images

NetBackup retains the information for the number of days that this property
specifies.

Keeping the information on disk speeds up restores. If a user requests a

true image restore after the information was deleted from disk, NetBackup
retrieves the required information from the media. The only noticeable
difference to the user is a slight increase in total restore time. NetBackup
deletes the additional information from disk again after one day.

Move restore job from incomplete Indicates the number of days that a failed restore job can remain in an
state to done state Incomplete state. After that time, the Activity Monitor shows the job as Done.
The default is 7 days. The maximum setting is 365 days. If Checkpoint Restart
for restores is used, the Restore retries property allows a failed restore job
to be retried automatically.

See “Universal Settings properties” on page 258.

See “Checkpoint restart for restore jobs” on page 705.

 Configuring Host Properties 90
Client Name properties

Table 3-10 Clean-up dialog box properties (continued)

Property Description

Move backup job from incomplete Indicates the maximum number of hours that a failed backup job can remain
state to done state in an incomplete state. After that time, the Activity Monitor shows the job as
Done. The minimum setting is 1 hour. The maximum setting is 72 hours.
The default is 3 hours.

When an active job has an error, the job goes into an Incomplete state. In
the Incomplete state, the administrator can correct the condition that caused
the error. If an Incomplete job does not complete successfully and is moved
to the Done state, the job retains the error status.
Note: A resumed job reuses the same job ID, but a restarted job receives
a new job ID. The job details indicate that the job was resumed or restarted.

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

Image cleanup interval Specifies the maximum interval that can elapse before an image cleanup is
run. Image cleanup is run after every successful backup session (that is, a
session in which at least one backup runs successfully). If a backup session
exceeds this maximum interval, an image cleanup is initiated.

Catalog cleanup wait time Specifies the minimum interval that can elapse before an image cleanup is
run. Image cleanup is not run after a successful backup session until this
minimum interval has elapsed since the previous image cleanup.

Note: The following properties have been moved from the Clean-up host properties
to the Logging host properties: Keep logs and Keep Vault logs. On the Logging
properties screen, these properties are referred to as Keep logs for days and
Keep Vault logs for respectively.
See “Logging properties” on page 170.

Client Name properties

The Client name property in the NetBackup Administration Console specifies
the NetBackup client name for the selected client. The name must match the name
the policy uses to back up the client. The only exception is for a redirected restore,
where the name must match that of the client whose files are to be restored. The
client name is initially set during installation.
 Configuring Host Properties 91
Client Name properties

The name that is entered here must also match the client name in the Client
Attributes dialog box for the master server. If it does not match, the client cannot
browse for its own backups.

Note: Using an IPv6 address as a client name in a policy can cause backups to
fail. Specify a host name instead of an IPv6 address.

See “Client Attributes properties” on page 92.

Figure 3-10 Client Name dialog box

If the value is not specified, NetBackup uses the name that is set in the following
locations:
■ For a Windows client
In the Network application from the Control Panel.
■ For a UNIX client
The name that is set by using the hostname command.
 Configuring Host Properties 92
Client Attributes properties

The name can also be added to a $HOME/[Link] file on a UNIX client. However,
the name is normally added in this manner only for redirected restores. The
value in the $HOME/[Link] file takes precedence if it exists.

Client Attributes properties

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

Table 3-11 Global client attributes group box

Attribute Description

Allow client browse Allows all clients to browse files for restoring. This attribute is overridden if
the Browse and restore ability option on the General tab is set to Deny
both for a particular client(s).

Allow client restore Allows all clients to restore files. This attribute is overridden if the Browse
and restore ability option on the General tab is set to Allow browse only
or Deny both.
 Configuring Host Properties 93
Client Attributes properties

Table 3-11 Global client attributes group box (continued)

Attribute Description

Clients Specifies the list of clients in the client database on the currently selected
master server(s). A client must be in the client database before you can
change the client properties in the Client Attributes dialog box.

The client database consists of directories and files in the following

directories:

On Windows: Install_path\NetBackup\db\client

On UNIX: /usr/openv/NetBackup/db/client

If a client is not listed in the Clients list, click Add to add clients. To remove
a client from the Clients list, select the client, then click Remove.

If a client is not listed in the Clients list, click Add to display the Add Client
dialog box and add a client to the client database. Type a client name in the
text box or click the browse button (...) and select a client.

See “Add Client dialog box” on page 94.

The name that is entered here must match the Client Name property for the
specific client. If it does not, the client cannot browse its own backups.

See “Client Name properties” on page 90.

Use the bpclient command to add clients to the client database if dynamic
addressing (DHCP) is in use.

Additional information about busy file processing is available in the NetBackup

Administrator’s Guide, Volume II.

On UNIX: You also can create, update, list, and delete client entries by using
the bpclient command that is located in the following directory:

/usr/openv/netbackup/bin/admincmd

General tab Specifies how to configure the selected Windows master servers (clients).

See “General tab of the Client Attributes properties” on page 94.

Connect Options tab Specifies how to configure the connection between a NetBackup server and
a NetBackup client.

See “Connect Options tab of the Client Attributes properties” on page 99.

Windows Open File Backup tab Specifies whether a client uses Windows Open File Backup. Also, specifies
whether Volume Snapshot Provider or Volume Shadow Copy Service
is used as the snapshot provider.

See “Windows Open File Backup tab of the Client Attributes properties”
on page 101.
 Configuring Host Properties 94
Client Attributes properties

Add Client dialog box

To add a client to the database, enter the name of a client, or browse to find a client.
The Add Client dialog box contains the following properties.

Enter client name Specifies the name of the client to be added to the database.
Type the name of the client to add.

... (browse) Finds the list of current clients and displays them in the Browse
for computer window. Select the client to add to the database
and click Add.

Add Adds the specified client to the client database (client name
displays in the Clients window).

Close Closes the Add Client dialog box.

Help Displays more information about how to add a client.

General tab of the Client Attributes properties

The properties on the General tab apply to selected Windows master servers. The
tab appears on the Client Attributes dialog box.
 Configuring Host Properties 95
Client Attributes properties

Figure 3-11 General tab of Client Attributes dialog box

The General tab contains the following properties.

 Configuring Host Properties 96
Client Attributes properties

Table 3-12 General tab properties

Property Description

Offline Backups until: Makes the specified clients in the General tab unavailable for backups until
the specified date and time. By default, clients are online and included in the
policies in which they are listed.

When Offline Backups until is selected for a client, no jobs are scheduled
for that client. Since the client is not part of any job, no backup status is listed
for the client.

If a client is taken offline, any job that includes the client and is already
running is allowed to complete.

If a backup or restore job is manually submitted for a client that is offline, the
Activity Monitor displays the job as failed with a status code 1000 (Client is
offline).
Note: Changes to this property do not appear in the audit report.

The ability to take clients offline is useful in a number of situations.

See “Offline option usage considerations and restrictions” on page 97.

Offline Restores until: Makes the specified clients in the General tab unavailable for restores until
the specified date and time. By default, clients are online and available for
restore.

Maximum data streams Specifies the maximum number of jobs that are allowed at one time for each
selected client. (This value applies to the number of jobs on the client, even
if multistreaming is not used.)

To change the setting, select Maximum data streams. Then scroll to or

enter a value up to 99.
The Maximum data streams property interacts with Maximum jobs per
client and Limit jobs per policy as follows:

■ If the Maximum data streams property is not set, the limit is either the
one indicated by the Maximum jobs per client property or the Limit
jobs per policy property, whichever is lower.
■ If the Maximum data streams property is set, NetBackup ignores the
Maximum jobs per client property. NetBackup uses either Maximum
data streams or Limit jobs per policy, whichever is lower.
See “Global Attributes properties” on page 159.
See “Limit jobs per policy (policy attribute)” on page 706.
 Configuring Host Properties 97
Client Attributes properties

Table 3-12 General tab properties (continued)

Property Description

Browse and restore ability Specifies the client permissions to list and restore backups and archives.
Select the client(s) in the General tab of the Client Attributes dialog box
and choose a Browse and restore ability property.

To use the Global client attributes settings, select Use global settings.

■ To allow users on the selected clients to both browse and restore, select
Allow both.
■ To allow users on the selected clients to browse but not restore, select
Allow browse only.
■ To prevent users on the selected clients from the ability to browse or
restore, select Deny both.

Free browse Specifies whether the clients can list and restore from scheduled backups.
(This setting does not affect user backups and archives.)

This property applies to the privileges that are allowed to a non-Windows

administrator or non-root user who is logged into the client. This property
also applies to the users that do not have backup and restore privileges.

Windows administrators and root users can list and restore from scheduled
backups as well as user backups regardless of the Free browse setting.

Deduplication Specifies the deduplication action for clients if you use the NetBackup Data
Protection Optimization Option.

For a description of the client-side deduplication options and their actions:

See “Where deduplication should occur” on page 98.

Offline option usage considerations and restrictions

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

Table 3-13 Offline option actions

Type of job or operation Action or restriction

A client is offline and the job is already in progress Offline clients continue to be included in any job.
 Configuring Host Properties 98
Client Attributes properties

Table 3-13 Offline option actions (continued)

Type of job or operation Action or restriction

A client is offline and job retries were started before the Job retries continue as normal.
client was taken offline

Any duplication job that is associated with a storage Continues to run until complete.
lifecycle policy and an offline client

LiveUpdate jobs for offline clients Continues to run until complete.

Restore jobs Can be run for offline clients.

The user attempts a manual backup for an offline client The backup fails with a status code 1000 (Client is offline).
The user can either wait until the client is brought online
again or bring the client online manually. Use either the
NetBackup Administration Console or the bpclient
command to do so before resubmitting the manual job.

Archive backups Not allowed for offline clients.

Administrators restarting or resuming jobs Not allowed for offline clients.

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

Where deduplication should occur

The Deduplication property specifies the deduplication action for clients if you use
either the NetBackup Data Protection Optimization Option. Table 3-14 describes
the client-side deduplication options.
The clients that deduplicate their own data and the master server must use the
same name to resolve the storage server. The name must be the host name under
which the NetBackup Deduplication Engine credentials were created. If they do not
use the same name, backups fail. In some environments, careful configuration may
be required to ensure that the client and the master server use the same name for
the storage server. Such environments include those that use VLAN tagging and
those that use multi-homed hosts.
NetBackup does not support the following for client-side deduplication:
■ Multiple copies per each job configured in a NetBackup backup policy. For the
jobs that specify multiple copies, the backup images are sent to the storage
server and may be deduplicated there.
■ NDMP hosts. The backup jobs fail if you try to use client-side deduplication for
NDMP hosts.
 Configuring Host Properties 99
Client Attributes properties

Table 3-14 Client-side deduplication options

Option Description

Always use the media server (the Always deduplicates the data on the media server. The default.
default) Jobs fail if one of the following is true:

■ The deduplication services on the storage server are inactive.

■ The deduplication pool is down.

Prefer to use client-side deduplication Deduplicates the data on the client and then sends it directly to the storage
server.

NetBackup first determines if the storage server is active. If it is active, the

client deduplicates the backup data and sends it to the storage server to be
written to disk. If it is not active, the client sends the backup data to a media
server, which deduplicates the data.

Always use client-side deduplication Always deduplicates the backup data on the client and then sends it directly
to the storage server.

If a job fails, NetBackup does not retry the job.

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

Connect Options tab of the Client Attributes properties

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

Figure 3-12 Connect Options tab of Client Attributes dialog box

The Connect Options tab contains the following options.

Table 3-15 Connect Options tab properties

Property Description

BPCD connect back Specifies how daemons are to connect back to the NetBackup Client daemon
(BPCD) and contains the following options:

■ Use default connect options

Uses the value that is defined in the Firewall host properties of the client’s
NetBackup server.
See “Firewall properties” on page 151.
■ Random port
NetBackup randomly chooses a free port in the allowed range to perform the
legacy connect-back method.
■ VNETD port
NetBackup uses the vnetd port number for the connect-back method.
 Configuring Host Properties 101
Client Attributes properties

Table 3-15 Connect Options tab properties (continued)

Property Description

Ports Specifies the method that the selected clients should use to connect to the server
and contains the following options:

■ Use default connect options

Uses the value that is defined in the Firewall host properties of the client’s
NetBackup server.
See “Firewall properties” on page 151.
■ Reserved port
Uses a reserved port number.
■ Non-reserved port
Uses a non-reserved port number.

Daemon connection port Specifies the method that the selected clients should use to connect to the server
and contains the following options.

■ Use default connect options

Uses the value that is defined in the Firewall host properties of the client’s
NetBackup server.
■ Automatic
Connects to the daemons on the server using vnetd if possible. If the daemons
cannot use vnetd, the connection is made by using the daemon’s legacy port
number.
■ VNETD only
Connects to the daemons on the server by using only vnetd. If the firewall
rules prevent a server connection using the legacy port number, check this
option.
When selected, the BPCD connect back setting is not applicable.
In addition, the Ports setting uses Non-reserved port, regardless of the value
selected.
■ Daemon port only
Connects to the daemons on the server by using only the legacy port number.
This option only affects connections to NetBackup 7.0 and earlier. For
connections to NetBackup 7.0.1 and later, the veritas_pbx port is used.
■ See “Resilient Network properties” on page 218.

Windows Open File Backup tab of the Client Attributes properties

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

Snapshots are a point-in-time view of a source volume. NetBackup uses snapshots

to access busy or active files during a backup job. Without a snapshot provider,
active files are not accessible for backup.

Figure 3-13 Windows Open File Backup tab of Client Attributes dialog box

The Windows Open File Backup tab contains the following options.
 Configuring Host Properties 103
Client Attributes properties

Table 3-16 Windows Open File Backup tab properties

Property Description

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

■ Windows Open File Backup is enabled on the client.

■ Microsoft Volume Shadow Copy Service (VSS) is used for NetBackup 7.0 clients.
See “Back-level and upgraded clients that use Windows Open File Backup” on page 106.
■ Snapshots are taken of individual drives (Individual drive snapshot) as opposed to all
drives at once (Global drive snapshot).
■ Upon error, the snapshot is terminated (Abort backup on error).

Remove Deletes a client from the list by selecting the client and then clicking Delete.

Enable Windows Open Specifies that Windows Open File Backups be used for the selected clients. Adds the clients
File Backups to the list only if you want to change the default property settings.

For Microsoft Distributed File System Replication (DFSR) servers, select Enable Windows
Open File Backups. The Snapshot Provider must be Volume Shadow Copy Service.

See “About Microsoft DSFR backups” on page 683.

This option functions independently from the Perform Snapshot backups policy option
that is available when the Snapshot Client is licensed.

If a client is included in a policy that has the Perform Snapshot backups policy option
disabled and you do not want snapshots, the Enable Windows Open File Backups for
this client property must be disabled as well for the client. If both options are not disabled,
a snapshot is created, though that may not be the intention of the administrator.

For more information, see the NetBackup Snapshot Client Administrator’s Guide.
 Configuring Host Properties 104
Client Attributes properties

Table 3-16 Windows Open File Backup tab properties (continued)

Property Description

Snapshot Provider
Note: This option is used for back-level versions of NetBackup only. Support for the Windows
versions that are listed here has ended.

Selects the snapshot provider for the selected clients:

■ Use Veritas Volume Snapshot Provider (VSP)

This option specifies that Veritas VSP be used as the snapshot provider. VSP is required
for Windows 2000 clients and can also be used on 6.x Windows 2003 clients.
■ Use Microsoft Volume Shadow Copy Service (VSS)
This option specifies that Microsoft VSS be used to create volume snapshots of volumes
and logical drives for the selected clients.
Configure VSS through the Microsoft VSS configuration dialog boxes.
For information about how to do Active Directory granular restores when using VSS, see
the following topic:
See “Active Directory host properties” on page 81.
For Microsoft Distributed File System Replication (DFSR) servers, select Use Microsoft
Volume Shadow Copy Service (VSS).
See “About Microsoft DSFR backups” on page 683.
 Configuring Host Properties 105
Client Attributes properties

Table 3-16 Windows Open File Backup tab properties (continued)

Property Description

Snapshot usage Selects how snapshots are made for the selected clients:

■ Individual drive snapshot

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

Table 3-16 Windows Open File Backup tab properties (continued)

Property Description

Snapshot error control Selects the processing instructions that NetBackup should follow if it encounters an error
during processing:

■ Abort backup on error

Specifies that a backup aborts if it fails for a snapshot-related issue after the snapshot
is created and while the backup uses the snapshot to back up open or active files on the
file system.
The most common reason for a problem after the snapshot is created and is in use by
a backup, is that the cache storage is full. If the Abort backup on error property is
checked (default), the backup job aborts with a snapshot error status if the backup detects
a snapshot issue.
This property does not apply to successful snapshot creation. The backup job continues
regardless of whether a snapshot was successfully created for the backup job. The Abort
backup on error property applies only to the snapshot errors that occur after the snapshot
is successfully created and is in use by a backup job.
■ Disable snapshot and continue
Specifies that if the snapshot becomes invalid during a backup, the volume snapshots
for the backup are destroyed. The backup continues with Windows open file backups
disabled.
Regarding the file that had a problem during a backup—it may be that the file was not
backed up by the backup job. The file may not be able to be restored.
Note: Volume snapshots typically become invalid during the course of a backup because
insufficient cache storage was allocated for the volume snapshot. Reconfigure the cache
storage configuration of the Windows Open File Backup snapshot provider to a
configuration that best suits your client’s installation.

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

Table 3-17 Snapshot Provider behavior for clients in a 7.x environment

Client Snapshot Provider Behavior

version setting

6.x Veritas VSP Veritas VSP is used for Open File Backup.

(6.5 default setting)

6.x Veritas VSP Veritas VSP is used for Open File Backup.

6.x Windows VSS Windows VSS is used for Open File Backup.
 Configuring Host Properties 107
Client Settings properties for UNIX clients

Table 3-17 Snapshot Provider behavior for clients in a 7.x environment

(continued)

Client Snapshot Provider Behavior

version setting

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

(7.0 default setting)

7.x Veritas VSP Even if Veritas VSP is indicated, Windows VSS is used for Open File
Backup.
For upgraded clients:

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

7.x Windows VSS Windows VSS is used for Open File Backup.

Client Settings properties for UNIX clients

The UNIX Client Settings properties in the NetBackup Administration Console
apply to currently selected NetBackup clients running on the UNIX platform.
 Configuring Host Properties 108
Client Settings properties for UNIX clients

Figure 3-14 Client Settings (UNIX) dialog box

The UNIX Client Settings dialog box contains the following properties.

Table 3-18 UNIX Client Settings dialog box properties

Property Description

Locked file action Determines what happens when NetBackup tries to back up a file with mandatory
file locking enabled in its file mode.
Select one of the following options:

■ Wait
By default, NetBackup waits for files to become unlocked. If the wait exceeds
the Client read timeout host property that is configured on the master server,
the backup fails with a status 41.
See “Timeouts properties” on page 256.
■ Skip
NetBackup skips the files that currently have mandatory locking set by another
process. A message is logged if it was necessary to skip a file.
 Configuring Host Properties 109
Client Settings properties for UNIX clients

Table 3-18 UNIX Client Settings dialog box properties (continued)

Property Description

Keep status of user-directed Specifies the number of days to keep progress reports before the reports are
backups, archives, and restores deleted. The default is 3 days. The minimum is 0. The maximum is 9,999 days.

Logs for user-directed operations are stored on the client system in the following
directory:

install_path\NetBackup\logs\user_ops\ loginID\logs

Reset file access time to the value Specifies that the access time (atime) for a file displays the backup time. By
before backup default, NetBackup preserves the access time by resetting it to the value it had
before the backup.
Note: This setting affects the software and the administration scripts that
examine a file’s access time.

Note: If NetBackup Accelerator is used to perform the backup, this setting is

ignored. Accelerator does not record and reset the atime for the files that it
backs up.

See “Accelerator notes and requirements” on page 734.

Megabytes of memory to use for Specifies the amount of memory available on the client when files are
file compression compressed during backup. If you select compression, the client software uses
this value to determine how much space to request for the compression tables.
The more memory that is available to compress code, the greater the
compression and the greater the percentage of computer resources that are
used. If other processes also need memory, use a maximum value of half the
actual physical memory on a computer to avoid excessive swapping.

The default is 0. This default is reasonable; change it only if problems are

encountered.

Use VxFS file change log for Determines if NetBackup uses the File Change Log on VxFS clients.
incremental backups
The default is off.

See “VxFS file change log for incremental backups property” on page 110.

Default cache device path for For additional information, see the NetBackup Snapshot Client Administrator’s
snapshots Guide.
 Configuring Host Properties 110
Client Settings properties for UNIX clients

Table 3-18 UNIX Client Settings dialog box properties (continued)

Property Description

Do not compress files ending with Corresponds to adding a COMPRESS_SUFFIX =.suffix option to the [Link]
list file.

Specifies a list of file extensions. During a backup, NetBackup does not compress
files with these extensions because the file may already be in a compressed
format.

Do not use wildcards to specify these extensions. For example, .A1 is allowed,
but not .A* or .A[1-9]

Files that are already compressed become slightly larger if compressed again.
If compressed files with a unique file extension already exist on a UNIX client,
exclude it from compression by adding it to this list.

Add Adds file endings to the list of file endings that you do not want to compress.
Click Add, then type the file extension in the File Endings dialog box. Use
commas or spaces to separate file endings if more than one is added. Click
Add to add the ending to the list, then click Close to close the dialog box.

Add to All Adds a file extension that you do not want to compress, to the lists of all clients.
To add the file extension to the lists of all clients, select it in the list on the Client
Settings host property, then click Add to All.

Remove Removes a file extension from the list. To remove a name, either type it in the
box or click the browse button (...) and select a file ending. Use commas or
spaces to separate names.

VxFS file change log for incremental backups property

The Use VxFS file change log for incremental backups property is supported
on all platforms and versions where VxFS file systems support FCL.
The following VxFS file systems support FCL:
■ Solaris SPARC platform running VxFS 4.1 or later.
■ AIX running VxFS 5.0 or later.
■ HP 11.23 running VxFS 5.0 or later.
■ Linux running VxFS 4.1 or later.
The File Change Log (FCL) tracks changes to files and directories in a file system.
Changes can include files created, links and unlinks, files renamed, data that is
appended, data that is overwritten, data that is truncated, extended attribute
modifications, holes punched, and file property updates.
 Configuring Host Properties 111
Client Settings properties for UNIX clients

NetBackup can use the FCL to determine which files to select for incremental
backups, which can potentially save unnecessary file system processing time. The
FCL information that is stored on each client includes the backup type, the FCL
offset, and the timestamp for each backup.
The advantages of this property depend largely on the number of file system changes
relative to the file system size. The performance impact of incremental backups
ranges from many times faster or slower, depending on file system size and use
patterns.
For example, enable this property for a client on a very large file system that
experiences relatively few changes. The incremental backups for the client may
complete sooner since the policy needs to read only the FCL to determine what
needs to be backed up on the client.
If a file experiences many changes or multiple changes to many files, the time
saving benefit may not be as great.
See “Backup Selections tab” on page 810.
The following items must be in place for the Use VxFS file change log for
incremental backups property to work:
■ Enable the Use VxFS file change log for incremental backups property for
every client that wants NetBackup to take advantage of the FCL.
■ Enable the FCL on the VxFS client.
See the Veritas File System Administrator’s Guide for information about how to
enable the FCL on the VxFS client.
■ Enable the Use VxFS file change log for incremental backups property on
the client(s) in time for the first full backup. Subsequent incremental backups
need this full backup to stay synchronized.
■ Specify the VxFS mount point in the policy backup selections list in one of the
following ways:
■ Specify ALL_LOCAL_DRIVES.
■ Specifying the actual VxFS mount point.
■ Specifying a directory at a higher level than the VxFS mount point, provided
that Cross mount points is enabled.
See “Cross mount points (policy attribute)” on page 713.

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

Table 3-19 VxFS file change log feature options

Option Description

Activity Monitor messages Displays any messages that note when the file change log
is used during a backup as follows:

Using VxFS File Change Log for backup of pathname

Also notes when full and incremental backups are not

synchronized.

Keeping the data files The data files must be in sync with the FCL for this property
synchronized with the FCL to work. To keep the data files synchronized with the FCL,
do not turn the FCL on the VxFS client off and on.
Note: If NetBackup encounters any errors as it processes
the FCL, it switches to the normal files system scan. If this
switch occurs, it appears in the Activity Monitor.

VxFS administration Additional VxFS commands are available to administrate the

FCL in the Veritas File System Administrator’s Guide.

Client Settings properties for Windows clients

The Windows Client Settings properties apply to currently selected Windows
clients.
 Configuring Host Properties 113
Client Settings properties for Windows clients

Figure 3-15 Windows Client Settings dialog box

The Client Settings dialog box for Windows clients contains the following properties.

Table 3-20 Windows Client Settings properties

Property Description

General level Enables logs for bpinetd, bpbkar, tar, and nbwin. The higher the level, the
more information is written. The default is 0.

TCP level Enables logs for TCP.

Scroll to one of the following available log levels:

■ 0 No extra logging (default)

■ 1 Log basic TCP/IP functions
■ 2 Log all TCP/IP functions, including all read and write requests
■ 3 Log contents of each read or write buffer

Note: Setting the TCP level to 2 or 3 can cause the status reports to be very
large. It can also slow a backup or restore operation.
 Configuring Host Properties 114
Client Settings properties for Windows clients

Table 3-20 Windows Client Settings properties (continued)

Property Description

Wait time before clearing archive Specifies how long the client waits before the archive bits for a differential
bit incremental backup are cleared. The minimum allowable value is 300 (default).
The client waits for acknowledgment from the server that the backup was
successful. If the server does not reply within this time period, the archive bits are
not cleared.

This option applies only to differential-incremental backups. Cumulative-incremental

backups do not clear the archive bit.

Use change journal

Note: The Use Change Journal option applies to Windows clients only.

This option works together with the Use Accelerator policy attribute and the
Accelerator forced rescan schedule attribute.

See “Accelerator and the Windows change journal” on page 733.

See “Use Accelerator (policy attribute)” on page 730.

See “Accelerator forced rescan option (schedule attribute)” on page 769.

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

Incrementals based on archive Specifies that NetBackup include files in an incremental backup only if the archive
bit bit of the file is set. The system sets this bit whenever a file is changed and it
normally remains set until NetBackup clears it.

A full backup always clears the archive bit. A differential-incremental backup clears
the archive bit if the file is successfully backed up. The differential-incremental
backup must occur within the number of seconds that the Wait time before
clearing archive bit property indicates. A cumulative-incremental or user backup
has no effect on the archive bit.

Disable this property to include a file in an incremental backup only if the date
and time stamp for the file has changed since the last backup. For a
differential-incremental backup, NetBackup compares the date/time stamp to the
last full or incremental backup. For a cumulative-incremental backup, NetBackup
compares the timestamp to the last full backup.
If you install or copy files from another computer, the new files retain the date
timestamp of the originals. If the original date is before the last backup date on
this computer, then the new files are not backed up until the next full backup.
Note: Veritas 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.
 Configuring Host Properties 115
Client Settings properties for Windows clients

Table 3-20 Windows Client Settings properties (continued)

Property Description

Time overlap Specifies the number of minutes to add to the date range for incremental backups
when you use date-based backups. This value compensates for differences in
the speed of the clock between the NetBackup client and server. The default is
60 minutes.

This value is used during incremental backups when you use the archive bit and
when you examine the create time on folders. This comparison is done for archive
bit-based backups as well as date-based backups.

Communications buffer size Specifies the size (in kilobytes) of the TCP and the IP buffers that NetBackup
uses to transfer data between the NetBackup server and client. For example,
specify 10 for a buffer size of 10 kilobytes. The minimum allowable value is 2,
with no maximum allowable value. The default is 128 kilobytes.

User directed timeouts Specifies the seconds that are allowed between when a user requests a backup
or restore and when the operation begins. The operation fails if it does not begin
within this time period.

This property has no minimum value or maximum value. The default is 60 seconds.

Maximum error messages for Defines how many times a NetBackup client can send the same error message
server to a NetBackup server. For example, if the archive bits cannot be reset on a file,
this property limits how many times the message appears in the server logs. The
default is 10.

Keep status of user-directed Specifies how many days the system keeps progress reports before NetBackup
backups, archives, and restores automatically deletes them. The default is 3 days.

Perform default search for Instructs NetBackup to search the default range of backup images automatically.
restore The backed up folders and files within the range appear whenever a restore
window is opened.

Clear the Perform default search for restore check box to disable the initial
search. With the property disabled, the NetBackup Restore window does not
display any files or folders upon opening. The default is that the option is enabled.

How to determine if change journal support is useful in your

NetBackup environment
Using NetBackup support for the change journal is beneficial only where the volumes
are large and relatively static.
Suitable candidates for enabling NetBackup change journal support are as follows:
■ If the NTFS volume contains more than 1,000,000 files and folders and the
number of changed objects between incremental backups is small (less than
 Configuring Host Properties 116
Client Settings properties for Windows clients

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

Guidelines for enabling NetBackup change journal support

The following items are guidelines to consider for enabling NetBackup change
journal support:
■ Change journal support is not offered for user-directed backups. The USN
stamps for full and incremental backups in the permanent record do not change.
■ NetBackup support for change journal works with checkpoint restart for restores.
See “Checkpoint restart for restore jobs” on page 705.
■ Support for change journal is not offered with several NetBackup options or
Veritas products.
If Use change journal is enabled, it has no effect while you use the following
options or products:
■ True image restore (TIR) or True image restore with Move Detection
See “Collect true image restore information (policy attribute) with and without
move detection” on page 721.
■ Synthetic backups
See “About synthetic backups” on page 864.
■ Bare Metal Restore (BMR)
For more information, see the NetBackup Bare Metal Restore Administrator’s
Guide.
 Configuring Host Properties 117
Credential Access properties

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

environment” on page 115.

Credential Access properties

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

Figure 3-16 Credential Access dialog box

The Credential Access dialog box contains the following properties.

Table 3-21 Credential Access dialog box properties

Property Description

NDMP Clients list To add an NDMP client to the NDMP Clients list, click Add. Enter the names of the
NDMP hosts that are not named as clients in a policy.
 Configuring Host Properties 118
Data Classification properties

Table 3-21 Credential Access dialog box properties (continued)

Property Description

Disk clients list To add a Disk Client to the DISK Clients list, click Add. Enter the names of the
NetBackup hosts that meet all of the following criteria:

■ The host must be designated in a policy as the Off-host backup host in an alternate
client backup.
■ The host that is designated as the Off-host backup computer must not be named
as a client on the Clients tab in any NetBackup policy.
■ The policy for the off-host backup must be configured to use one of the disk array
snapshot methods for the EMC CLARiiON, HP EVA, or IBM disk arrays
Note: The credentials for the disk array or NDMP host are specified under Media
and Device Management > Credentials.

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

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

Data Classification properties

The Data Classification properties apply to currently selected master and media
servers.
Data classifications must be configured in the Data Classification host properties
before storage lifecycle policies can be configured.
See “Data classifications (policy attribute)” on page 697.
 Configuring Host Properties 119
Data Classification properties

Figure 3-17 Data Classification dialog box

The Data Classification dialog box contains the following properties.

 Configuring Host Properties 120
Data Classification properties

Table 3-22 Data Classification dialog box properties

Property Description

Rank column The Rank column displays the rank of the data classifications. The order of the data
classifications determines the rank of the classification in relationship to the others in
the list. The lowest numbered rank has the highest priority.

Use the Move Up and Move Down options to move the classification up or down in
the list.

To create a new data classification, click New. New data classifications are added to
bottom of the list. To increase the rank of a data classification, select a line and click
Move Up. To decrease the rank of a data classification, select a line and click Move
Down.

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

■ Platinum (highest rank by default)

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

Description column In the Description column, enter a meaningful description for the data classification.
Descriptions can be modified.

Data Classification ID The Data Classification ID is the GUID value that identifies the data classification and
is generated when a new data classification is added and the host property is saved.
This column is not displayed by default.

A data classification ID becomes associated with a backup image by setting the Data
Classification attribute in the policy dialog box. The ID is written into the image header.
The storage lifecycle policies use the ID to identify the images that are associated with
classification.

ID values can exist in image headers indefinitely, so data classifications cannot be

deleted. The name, description, and rank can change without changing the identity of
the data classification.

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

Creating a Data Classification

Use the following procedures to create or change a data classification.
 Configuring Host Properties 121
Default Job Priorities properties

To create a data classification

1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Host Properties.
2 In the left pane, click Data Classification.
3 Click New.
4 Add the name and description in the New Data Classification dialog box.
5 Click OK to save the classification and close the dialog box.

Note: Data classifications cannot be deleted.

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

Default Job Priorities properties

The Default Job Priorities host properties let administrators configure the default
job priority for different job types. The Default Job Priorities host properties list
18 job types and the configurable default priority for each.
 Configuring Host Properties 122
Default Job Priorities properties

Figure 3-18 Default Job Priorities dialog box

The job priority can be set for individual jobs in the following utilities:
■ In the Jobs tab of the Activity Monitor for queued or active jobs.
See “Changing the Job Priority dynamically from the Activity Monitor” on page 1044.
■ In the Catalog utility for verify, duplicate, and import jobs.
■ In the Reports utility for a Media Contents report job.
■ In the Backup, Archive, and Restore client interface for restore jobs.
The Default Job Priorities dialog box contains the following properties.

Table 3-23 Default Job Priorities dialog box properties

Property Description

Job Type and Job Priority list This listing includes 18 job types and the current configurable priority for each.
 Configuring Host Properties 123
Default Job Priorities properties

Table 3-23 Default Job Priorities dialog box properties (continued)

Property Description

Job Priority The Job Priority value specifies the priority that a job has as it competes with other
jobs for backup resources. The value can range from 0 to 99999. The higher the number,
the greater the priority of the job.

A new priority setting affects all the policies that are created after the host property has
been changed.

A higher priority does not guarantee that a job receives resources before a job with a
lower priority. NetBackup evaluates jobs with a higher priority before those with a lower
priority.
However, the following factors can cause a job with a lower priority to run before a job
with a higher priority:

■ To maximize drive use, a low priority job may run first if it can use a drive that is
currently loaded. A job with a higher priority that requires that the drive be unloaded
would wait.
■ If a low priority job can join a multiplexed group, it may run first. The job with a
higher priority may wait if it is not able to join the multiplexed group.
■ If the NetBackup Resource Broker (nbrb) receives a job request during an
evaluation cycle, it does not consider the job until the next cycle, regardless of the
job priority.

Understanding the Job Priority setting

NetBackup uses the Job Priority setting as a guide. Requests with a higher priority
do not always receive resources before a request with a lower priority.
The NetBackup Resource Broker (NBRB) maintains resource requests for jobs in
a queue.
NBRB evaluates the requests sequentially and sorts them based on the following
criteria:
■ The request's first priority.
■ The request’s second priority.
■ The birth time (when the Resource Broker receives the request).
The first priority is weighted more heavily than the second priority, and the second
priority is weighted more heavily than the birth time.
Because a request with a higher priority is listed in the queue before a request with
a lower priority, the request with a higher priority is evaluated first. Even though the
chances are greater that the higher priority request receives resources first, it is
not always definite.
 Configuring Host Properties 124
Default Job Priorities properties

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

Distributed application restore mapping properties

Figure 3-19 Distributed Application Restore Mapping dialog box

Some applications, such as SharePoint and Exchange, distribute and replicate data
across multiple hosts. You need to provide a mapping of the hosts in the database
environment so thatNetBackup can successfully restore the databases.
The Distributed Application Restore Mapping dialog box contains the following
properties.
 Configuring Host Properties 126
Encryption properties

Table 3-24 Distributed Application Restore Mapping dialog box properties

Property Description

Add Adds a component host that is authorized to run restores on an SharePoint or Exchange
application host.

For SharePoint, NetBackup catalogs backup images under the front-end server name.
To allowNetBackup to restore SQL databases to the correct hosts in a farm, you must
provide a list of the SharePoint hosts. For Exchange, any operations that use Granular
Recovery Technology (GRT) require that you provide a list of the Exchange virtual and
the physical host names. Also include the off-host client and the granular proxy host.
Note: For VMware backups and restores that protect SharePoint or Exchange, you
only need to add the hosts that browse for backups or perform restores.

Note: You can use the client's short name or its fully qualified domain name (FQDN).
You do not need to provide both names in the list.

For more details, see the following:

NetBackup for SharePoint Server Administrator's Guide

NetBackup for Exchange Server Administrator's Guide

Change Changes the application host or component host of the currently selected mapping.

Remove Removes the currently selected mapping.

Encryption properties
The Encryption properties control encryption on the currently selected client.
Multiple clients can be selected and configured at one time only if all selected clients
are running the same version of NetBackup. If not, the Encryption properties dialog
box is hidden.
More information is available in the NetBackup Security and Encryption Guide.
 Configuring Host Properties 127
Encryption properties

Figure 3-20 Encryption dialog box

The Encryption permissions property indicates the encryption setting on the

selected NetBackup client as determined by the master server.

Table 3-25 Encryption permissions selections

Property Description

Not allowed Specifies that the client does not permit encrypted backups.
If the server requests an encrypted backup, the backup job
ends due to error.

Allowed Specifies that the client allows either encrypted or

unencrypted backups. Allowed is the default setting for a
client that has not been configured for encryption.

Required Specifies that the client requires encrypted backups. If the

server requests an unencrypted backup, the backup job ends
due to error.
 Configuring Host Properties 128
Encryption properties

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

Table 3-26 Encryption dialog box properties

Property Description

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

Client Cipher The following cipher types are available: BF-CFB, DES-EDE-CFB, AES-256-CFB, and
AES-128-CFB. AES-128-CFB is the default.

More information about the ciphers file is available in the NetBackup Security and Encryption
Guide.

Enable legacy Pertains to the 40-bit and the 56-bit data encryption standard (DES) NetBackup encryption
DES encryption packages.

Encryption Defines the encryption strength on the NetBackup client when Legacy encryption is used:
strength
■ DES_40
Specifies the 40-bit DES encryption. DES_40 is the default value for a client that has not been
configured for encryption.
■ DES_56
Specifies the 56-bit DES encryption.

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

■ On Windows:

install_path\netbackup\bin\

Where install_path is the directory where NetBackup is installed and by default is C:\Program
Files\VERITAS.
■ On UNIX:

/usr/openv/lib

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

 Configuring Host Properties 129
Encryption properties

Table 3-26 Encryption dialog box properties (continued)

Property Description

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

■ On Windows:

install_path\NetBackup\bin\[Link]

Where install_path is the folder where NetBackup is installed and by default is C:\Program
Files\VERITAS.
■ On UNIX:

/usr/openv/netbackup/keyfile

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

Additional encryption methods for Windows clients

In addition to NetBackup client and server data encryption, Microsoft Windows
clients also have access to methods of encrypting the data on the original disk.
Each of the following methods has its own costs and benefits. NetBackup supports
each method for protecting Microsoft Windows clients.

Encrypting File System

The Encrypting File System (EFS) on Microsoft Windows is a feature introduced
with Windows 2000 and provides file system-level encryption. EFS is a form of
encryption where individual files or directories are encrypted by the file system itself.
The technology enables files to be transparently encrypted to protect confidential
data from attackers with physical access to the computer. Users can enable
encryption on a per-file, per-directory, or per-drive basis. The Group Policy in a
Windows domain environment can also mandate some EFS settings.
No NetBackup settings are involved in protecting these encrypted objects. Any
object with an encrypted file system attribute is automatically backed up and restored
in its encrypted state.

BitLocker Drive Encryption

BitLocker Drive Encryption is a full disk encryption feature included with certain
editions of Microsoft's Windows desktop and server versions, starting with Vista
and Windows Server 2008.
 Configuring Host Properties 130
Enterprise Vault properties

Disk encryption is a technology which protects information by converting it into

unreadable code that cannot be deciphered easily by unauthorized people. Disk
encryption uses disk encryption software or hardware to encrypt every bit of data
that goes on a disk or a disk volume.
As with EFS, no NetBackup settings are involved to use BitLocker for encryption.
Unlike EFS, the encryption layer is invisible to NetBackup, with the data being
automatically decrypted and encrypted by the operating system.
NetBackup does nothing to manage the encryption process and therefore backs
up and restores the unencrypted data.

Note: If you recover a Windows computer that has BitLocker encryption enabled,
you must re-enable BitLocker encryption following the restore.

Off-host backup is not supported with volumes that run Windows BitLocker Drive
Encryption.

Enterprise Vault properties

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

Figure 3-21 Enterprise Vault dialog box

The Enterprise Vault dialog box contains the following properties.

Table 3-27 Enterprise Vault dialog box properties

Property Description

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

Password Specify the password for the account.

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

Enterprise Vault Hosts properties

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

server properties, specify a source and a destination host. By doing so, you specify
a source host that can run restores on the destination host.

Figure 3-22 Enterprise Vault Hosts master server properties

The Enterprise Vault Hosts dialog box contains the following properties.

Table 3-28 Enterprise Vault Hosts dialog box properties

Option Description

Add Adds the source and the destination hosts within the Enterprise Vault configuration.
You must provide the name of the Source host and the name of the Destination host.

Change Changes the source host and the destination host, an entry that you select from the
Enterprise Vault Hosts field.

Exchange properties
The Exchange properties apply to the currently selected Windows clients. For
clustered or replicated environments, configure the same settings for all nodes. If
 Configuring Host Properties 133
Exchange properties

you change the attributes for the virtual server name, only the CCR active node or
DAG host server is updated.
For complete information on these options, see the NetBackup for Exchange Server
Administrator's Guide.

Figure 3-23 Exchange dialog box

The Exchange dialog box contains the following properties.

Table 3-29 Exchange dialog box properties

Property Description

Snapshot verification I/O throttle

Note: This property only applies to MS-Exchange-Server backup policies with
Exchange 2007.

This option applies to off-host Exchange 2007 snapshot backups if the Exchange
System Management Tools are not installed on the alternate client. Specify the
number of I/Os to process for each 1-second pause.
 Configuring Host Properties 134
Exchange properties

Table 3-29 Exchange dialog box properties (continued)

Property Description

Backup option for log files

Note: This property only applies to MS-Exchange-Server backup policies.
during full backups
Choose which logs to include with snapshot backups:

■ Back up only uncommitted log files

Select this option to back up only the log files that are uncommitted. This option
is not recommended for DAGs or Exchange 2007 CCR environments.
■ Back up all log files (including committed log files)

Truncate log after successful

Note: This property only applies to MS-Exchange-Server backup policies.
Instant Recovery backup
Enable this option to delete transaction logs after a successful Instant Recovery
backup. By default, transaction logs are not deleted for a full Instant Recovery
backup that is snapshot only.

Exchange granular proxy host

Note: This property applies when you duplicate or browse a backup that uses
Granular Recovery Technology (GRT).

You can specify a different Windows system to act as a proxy for the source client
when you duplicate or browse a backup (with bplist) that uses GRT. Use a
proxy if you do not want to affect the source client or if it is not available.

For complete information on this option, see the NetBackup for Exchange Server
Administrator's Guide.

Enable single instance backup

Note: This property only applies to MS-Exchange-Server backup policies with
for message attachments
Exchange 2007.

Enable this option to back up the data that is stored on a Single Instance Store
(SIS) volume. This feature only applies to mailbox and public folder backups with
Exchange Server 2007.

Perform consistency check

Note: This property only applies to MS-Exchange-Server backup policies.
before backup with Microsoft
Volume Shadow Copy Service Disable this option if you do not want to perform a consistency check during a
(VSS) DAG backup. If you check Continue with backup if consistency check fails,
NetBackup continues to perform the backup even if the consistency check fails.
 Configuring Host Properties 135
Exchange properties

Table 3-29 Exchange dialog box properties (continued)

Property Description

Exchange credentials Note the following for this property:

■ This property applies to MS-Exchange-Server and VMware backup policies

with Exchange recovery.
■ For Exchange 2013 and later, you must configure this property if you want to
use GRT.
■ This property does not apply to any backup and restore operations that have
a policy that uses the Microsoft Exchange Mailboxes:\ and the
Microsoft Exchange Public Folders:\ directives. Instead, you must
configure the logon account for the NetBackup Client Service with the
credentials for the account for NetBackup Exchange operations.

Provide the credentials for the account for NetBackup Exchange operations. This
account must have the necessary permissions to perform Exchange restores.
The permissions that are required depend on the Exchange version that you have.
The account also needs the right to “Replace a process level token.”

For complete information on this property, see the NetBackup for Exchange Server
Administrator's Guide.

About the Exchange credentials in the client host properties

The Exchange credentials in the client host properties indicate the account that has
necessary permissions to perform Exchange restores. The permissions that are
required depend on the Exchange version that you have.
Note the following:
■ The account that you configured for the Exchange credentials must also have
the right to “Replace a process level token.”
■ For database restores from VMware backups, the Exchange credentials that
you provide must have permissions to restore VM files.
■ If you want to restore from a VMware snapshot copy that was created with
Replication Director, do the following:
■ Provide the Exchange credentials in the Domain\user and Password fields.
■ Configure the NetBackup Client Service with an account that has access to
the CIFS shares that are created on the NetApp disk array.

Additional notes for Exchange 2013 and later

To use GRT, configure the Exchange credentials on all granular clients.
 Configuring Host Properties 136
Exclude Lists properties

Alternatively, you can configure the Exchange credentials only on the granular
clients that perform restores. In this case, for the entire domain add “Exchange
Servers” to the “View-Only Organization Management” role group. Perform this
configuration in the Exchange Administration Center (EAC) or in Active Directory.
See the following Microsoft article for more information:
[Link]

Additional notes for Exchange 2010 and 2007

These additional items apply to Exchange 2010 and 2007:
■ For granular restores from VMware backups, only the Exchange client that
performs the granular restore requires configuration of the Exchange credentials.
The Exchange credentials are not required for backup or browse operations.
■ If you configure the NetBackup Client Service with a logon account and configure
the Exchange credentials in the Exchange client host properties, you must
configure the “Replace a process level token” for both users.
■ In NetBackup 7.5 and earlier, you added the credentials to the logon account
for the NetBackup Client Service and the NetBackup Legacy Network Service
(Exchange 2010). Customers upgrading from earlier versions of NetBackup can
continue to use this configuration (unless you use Replication Director). Veritas
recommends that you use the new configuration in the Exchange client host
properties.
■ (Exchange 2007) If you use the Microsoft Exchange Mailboxes:\ and the
Microsoft Exchange Public Folders:\ directives in a policy, you must use
the old configuration. Configure the NetBackup Client Service to log on as the
account for NetBackup Exchange operations.

Exclude Lists properties

Use the Exclude Lists host properties to create and to modify the exclude lists for
Windows clients. An exclude list names the files and directories to be excluded
from backups of the selected Windows clients.
For UNIX clients, use the nbgetconfig and nbsetconfig commands to gather and
modify the exclude list files from the /usr/openv/netbackup directory on each
client. nbgetconfig and nbsetconfig can also be used on a UNIX server to create
an exclude list on a Windows client.
See “Configuring the exclude list on a Windows client from a UNIX master server”
on page 144.
 Configuring Host Properties 137
Exclude Lists properties

Figure 3-24 Exclude Lists dialog box

Exclude Lists properties apply only to Windows clients.

For information about creating exclude lists for UNIX clients, see the following topic:
See “About excluding files from automatic backups” on page 846.
If more than one exclude or include list exists for a client, NetBackup uses only the
most specific one.
For example, assume that a client has the following exclude lists:
■ An exclude list for a policy and schedule.
■ An exclude list for a policy.
■ An exclude list for the entire client. This list does not specify a policy or schedule.
In this example, NetBackup uses the first exclude list (for policy and schedule)
because it is the most specific.
Exclude and include lists that are set up for a policy or for a policy and schedule
are not used to determine if an entire drive is to be excluded when NetBackup
determines if a backup job should be started.
 Configuring Host Properties 138
Exclude Lists properties

Normally, this is not a problem. However, if a policy uses multistreaming and a drive
or a mount point is excluded, that job will report an error status when it completes.
To avoid the situation, do not use the policy or the policy and schedule lists to
exclude an entire volume.
The Exclude Lists dialog box contains the following properties.

Table 3-30 Excludes Lists dialog box properties

Property Description

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

Exclude lists Displays the policies that contain schedule, file, and directory exclusions as follows:

■ Add
Click to exclude a file from being backed up by a policy. The exclusion is configured
in the Add to exclude list dialog box, then added to the Exclude list. When the
policies in this list are run, the files and directories that are specified on the list are
not backed up.
■ Add to all
When multiple Windows clients are selected, click Add to all to add the selected
list item to the Exclude list for all selected clients. Add to all is enabled only when
multiple Windows clients are selected for configuration.
■ Remove
Click to remove the selected policy, schedule, or file from the Exclude list.
 Configuring Host Properties 139
Exclude Lists properties

Table 3-30 Excludes Lists dialog box properties (continued)

Property Description

Exceptions to exclude list Displays the policies, schedules, files, and directories that are excepted from the
Exclude list. When the policies on the Exceptions to the exclude list run, the files
and directories on the list are backed up if they were part of the original file list and
were subsequently excluded. The list is useful to exclude all files in a directory but one.

For example, if the file list of items to back up contains /foo, and the exclude list
contains /foo/bar, adding /fum to the exceptions list does not back up the /fum
directory. However, adding fum to the exceptions list will back up any occurrences of
fum (file or directory) that occur within /foo/bar.

Options include the following:

■ Add
Click to create an exception to the Exclude list. The exception is configured in the
Add exceptions to exclude list dialog box, then added to the Exceptions to the
exclude list.
When the policies on the Exceptions to the exclude list run, the items on the
exceptions list are backed up (if they were part of the original file list and
subsequently excluded). Effectively, you add files back into the backup list of a
policy.
■ Add to all
When multiple Windows clients are selected, click Add to all to add the selected
list item to the Exceptions to the exclude list for all selected clients. When the
policies on the exclude list run, the items on the exceptions list are backed up on
all selected clients.
■ Remove
Click to remove the selected policy, schedule, or file from the Exceptions list. After
the item is removed from the Exclude list, the item is excluded from the backup.

About the Add to Exclude List and Add Exceptions to Exclude List
dialog boxes
The Add to Exclude List dialog box and the Add Exceptions to Exclude List
dialog box contain the following fields:
 Configuring Host Properties 140
Exclude Lists properties

Table 3-31 Add to Exclude dialog box

Field Description

Policy The policy name that contains the files and the directories
that you want to exclude or make exceptions for. You can
also select the policy name from the drop-down menu. To
exclude or make exceptions for the backup of specific files
or directories from all policies, select All Policies.

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

Files/Directories Either browse or enter the full path to the files and the
directories that you want to exclude or make exceptions for.

Figure 3-25 Add to Exclude List properties

Adding an entry to an exclude list

Use the following procedure to add an entry to an exclude list for a policy:
To add an entry to the exclude list
1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Clients. Double-click on a client.
2 Under the Exclude List, click Add.
3 In the Policy field, select a policy name from the drop-down menu or enter the
name of a policy. Select All Policies to exclude these items from all policies.
 Configuring Host Properties 141
Exclude Lists properties

4 In the Schedule field, select a schedule name from the drop-down menu or
enter the name of a schedule. Select All Schedules to exclude the specified
files and directories from all schedules in the policy.
5 In the Files/Directories field, either browse or enter the files or directories to
be excluded from the backups that are based on the selected policy and
schedule.
6 Click Add to add the specified files and directories to the exclude list.
7 Click Apply to accept the changes. Click OK to accept the changes and close
the host properties dialog box.

Adding an exception to the exclude list

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

Syntax rules for exclude lists

Veritas suggests that you always specify automounted directories and CD-ROM
file systems in the exclude list. Otherwise, if the directories are not mounted at the
time of a backup, NetBackup must wait for a timeout.
The following syntax rules apply to exclude lists:
■ Only one pattern per line is allowed.
 Configuring Host Properties 142
Exclude Lists properties

■ NetBackup recognizes standard wildcard use.

See “Wildcard use in NetBackup” on page 1113.
See “NetBackup naming conventions” on page 1112.
■ If all files are excluded in the backup selections list, NetBackup backs up only
what is specified by full path names in the include list. Files can be excluded by
using / or * or by using both symbols together (/*).
■ Spaces are considered legal characters. Do not include extra spaces unless
they are part of the file name.
For example, if you want to exclude a file named
C:\testfile (with no extra space character at the end)
and your exclude list entry is
C:\testfile (with an extra space character at the end)
NetBackup cannot find the file until you delete the extra space from the end of
the file name.
■ End a file path with \ to exclude only directories with that path name (for example,
C:\users\test\). If the pattern does not end in \ (for example, C:\users\test),
NetBackup excludes both files and directories with that path name.
■ To exclude all files with a given name, regardless of their directory path, enter
the name. For example:
test
rather than
C:\test
This example is equivalent to prefixing the file pattern with
\
\*\
\*\*\
\*\*\*\
and so on.
The following syntax rules apply only to UNIX clients:
■ Do not use patterns with links in the names. For example, assume /home is a
link to /usr/home and /home/doc is in the exclude list. The file is still backed
up in this case because the actual directory path, /usr/home/doc, does not
match the exclude list entry, /home/doc.
■ Blank lines or lines which begin with a pound sign (#) are ignored.
 Configuring Host Properties 143
Exclude Lists properties

Example of a Windows client exclude list

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

C:\users\doe\abc\

C:\users\*\test

C:\*\temp

core

Given the exclude list example, the following files, and directories are excluded
from automatic backups:
■ The file or directory named C:\users\doe\john.
■ The directory C:\users\doe\abc\ (because the exclude entry ends with \).
■ All files or directories named test that are two levels beneath users on drive
C.
■ All files or directories named temp that are two levels beneath the root directory
on drive C.
■ All files or directories named core at any level and on any drive.

Example of a UNIX exclude list

In this example of a UNIX exclude list, the list contains the following entries:

# this is a comment line

/home/doe/john
/home/doe/abc/
/home/*/test
/*/temp
core

Given the exclude list example, the following files and directories are excluded from
automatic backups:
■ The file or directory named /home/doe/john.
■ The directory /home/doe/abc (because the exclude entry ends with /).
■ All files or directories named test that are two levels beneath home.
■ All files or directories named temp that are two levels beneath the root directory.
■ All files or directories named core at any level.
 Configuring Host Properties 144
Exclude Lists properties

About creating an include list on a UNIX client

To add a file that is eliminated with the exclude list, create a
/usr/openv/netbackup/include_list file. The same syntax rules apply as for
the exclude list.

Note: Exclude and include lists do not apply to user backups and archives.

To illustrate the use of an include list, we use the example from the previous
discussion. The exclude list in that example causes NetBackup to omit all files or
directories named test from all directories beneath /home/*/test.
In this case, add a file named /home/jdoe/test back into the backup by creating
an include_list file on the client. Add the following to the include_list file:

# this is a comment line

/home/jdoe/test

To create an include list for a specific policy or policy and schedule combination,
use a .policyname or .[Link] suffix. The following are two
examples of include list names for a policy that is named wkstations that contains
a schedule that is named fulls.

/usr/openv/netbackup/include_list.workstations
/usr/openv/netbackup/include_list.[Link]

The first file affects all scheduled backups in the policy that is named wkstations.
The second file affects backups only when the schedule is named fulls.
For a given backup, NetBackup uses only one include list: the list with the most
specific name. Given the following two files:

include_list.workstations
include_list.[Link]

NetBackup uses only include_list.[Link] as the include list.

Configuring the exclude list on a Windows client from a UNIX master

server
An administrator can change the exclude list on a Windows client from a UNIX
master server by using the nbgetconfig (or bpgetconfig) and the nbsetconfig
(or bpsetconfig) commands.
 Configuring Host Properties 145
Exclude Lists properties

Configuring the exclude list on a Windows client from a UNIX master server
1 From the UNIX server, use the nbgetconfig command to access the exclude
list on a Windows client.
For example, where:
nbmaster1 is a UNIX master server.
nbmedia1 is a Windows computer and a NetBackup client.
On nbmaster1, run the following command:

/usr/openv/netbackup/bin/nbgetconfig -M nbmedia1 EXCLUDE

The output lists the exclude list on nbmedia1:

EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\*.lock

EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackupDB\data\*
EXCLUDE = C:\Program Files\Veritas\Volmgr\misc\*

2 Create an exclude list on the UNIX server.

For example, file ex_list on nbmaster1:

vi /tmp/ex_list

The contents of ex_list consists of the following files and directories:

more /tmp/ex_list
EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackupDB\data\*
EXCLUDE = C:\Program Files\Veritas\Volmgr\misc\*
EXCLUDE = C:\
EXCLUDE = D:\
 Configuring Host Properties 146
Exclude Lists properties

3 From the UNIX server, use the nbsetconfig command to set the exclude list
on a Windows client.
For example, run the following command on nbmaster1 to make ex_list the
exclude list on client nbmedia1:

/usr/openv/netbackup/bin/nbsetconfig -h nbmedia1 /tmp/ex_list

4 On the UNIX server, use the nbgetconfig command to view the new exclude
list on the Windows client.
For example:

/usr/openv/netbackup/bin/nbgetconfig -M nbmedia1 EXCLUDE

The output lists the updated exclude list on nbmedia1:

EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\*.lock

EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
EXCLUDE = C:\Program Files\Veritas\NetBackupDB\data\*
EXCLUDE = C:\Program Files\Veritas\Volmgr\misc\*
EXCLUDE = C:\
EXCLUDE = D:\

Traversing excluded directories

An exclude list can indicate a directory for exclusion, while the client uses an include
list to override the exclude list. NetBackup traverses the excluded directories if
necessary, to satisfy the client’s include list.
Assume the following settings for a Windows client:
■ The backup policy backup selection list indicates ALL_LOCAL_DRIVES. When a
scheduled backup runs, the entire client is backed up.
The entire client is also backed up if the backup selection list consists of only:
/
■ The exclude list on the client consists of only: *
An exclude list of * indicates that all files are excluded from the backup.
■ However, since the include list on the Windows client includes the following file:
C:\WINNT, the excluded directories are traversed to back up C:\WINNT.
If the include list did not contain any entry, no directories are traversed.
In another example, assume the following settings for a UNIX client:
■ The backup selection list for the client consists of the following: /
 Configuring Host Properties 147
Fibre Transport properties

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

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

Fibre Transport properties

NetBackup Fibre Transport properties control how your Fibre Transport media
servers and SAN clients use the Fibre Transport service for backups and restores.
The Fibre Transport properties apply to the host type that you select in the
NetBackup Administration Console, as follows:

Table 3-32 Host types for Fibre Transport properties

Host type Description

Master server Global Fibre Transport properties that apply to all SAN clients.

Media server The Fibre Transport Maximum concurrent FT connections

property applies to the FT media server or servers that you selected
in the NetBackup Administration Console.

Client The Fibre Transport properties apply to the SAN client or clients
that you selected in the NetBackup Administration Console. The
default values for clients are the global property settings of the master
server. Client properties override the global Fibre Transport
properties.
 Configuring Host Properties 148
Fibre Transport properties

Figure 3-26 Fibre Transport host properties for a master server

Table 3-33 describes the Fibre Transport properties. All properties are not available
for all hosts. In this table, FT device is an HBA port on a Fibre Transport media
server. The port carries the backup and restore traffic. A media server may have
more than one FT device.
 Configuring Host Properties 149
Fibre Transport properties

Table 3-33 Fibre Transport dialog box properties

Property Description

Maximum concurrent FT This property appears only when you select an FT media server or servers in the
connections NetBackup Administration Console.

This property specifies the number of FT connections to allow to the selected

media server or media servers. A connection is equivalent to a job.

NetBackup supports 644 buffers per media server for Fibre Transport. To
determine the number of buffers that each connection uses, divide 644 by the
value you enter. More buffers per connection equal better performance for each
connection.
If no value is set, NetBackup uses the following defaults:

■ For NetBackup Appliance model 5330 and later: 32

■ For NetBackup Appliance model 5230 and later: 32
■ For NetBackup Fibre Transport media servers: 8 times the number of fast HBA
ports on the media server plus 4 times the number of slow HBA ports for. A
fast port is 8 GB or faster, and a slow port is less than 8 GB.
You can enter up to the following maximum connections for the media server or
servers to use:

■ On a Linux FT media server host: 40.

Veritas recommends that you use 32 or fewer connections concurrently on
Linux.
On Linux hosts, you can increase that maximum by setting a NetBackup touch
file, NUMBER_DATA_BUFFERS_FT.
See “About Linux concurrent FT connections” on page 150.
■ For NetBackup Appliance model 5330 and later: 40.
■ For NetBackup Appliance model 5230 and later: 40.
■ On a Solaris FT media server host: 64.

Use defaults from the master This property appears only when you select a client or client in the NetBackup
server configuration Administration Console.

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

Preferred The Preferred property specifies to use an FT device if one is available within
the configured wait period in minutes. If an FT device is not available after the
wait period elapses, NetBackup uses a LAN connection for the operation.

If you select this option, also specify the wait period for backups and for restores.

For the global property that is specified on the master server, the default is
Preferred.
 Configuring Host Properties 150
Fibre Transport properties

Table 3-33 Fibre Transport dialog box properties (continued)

Property Description

Always The Always property specifies that NetBackup should always use an FT device
for backups and restores of SAN clients. NetBackup waits until an FT device is
available before it begins the operation.

However, an FT device must be online and up. If not, NetBackup uses the LAN.
An FT device may be unavailable because none are active, none have been
configured, or the SAN Client license expired.

Fail The Fail property specifies that NetBackup should fail the job if an FT device is
not online and up. If the FT devices are online but busy, NetBackup waits until a
device is available and assigns the next job to the device. An FT device may be
unavailable because none are active, none have been configured, or the SAN
Client license expired.

Never The Never property specifies that NetBackup should never use an FT pipe for
backups and restores of SAN clients. NetBackup uses a LAN connection for the
backups and restores.

If you specify Never for the master server, Fibre Transport is disabled in the
NetBackup environment. If you select Never, you can configure FT usage on a
per-client basis.

If you specify Never for a media server, Fibre Transport is disabled for the media
server.

If you specify Never for a SAN client, Fibre Transport is disabled for the client.

NetBackup provides one finer level of granularity for Fibre Transport. SAN client
usage preferences override the FT properties that you configure through Host
Properties.
For more information about NetBackup Fibre Transport, see the NetBackup SAN
Client and Fibre Transport Guide:
[Link]

About Linux concurrent FT connections

NetBackup uses the Maximum concurrent FT connections Fibre Transport host
property to configure the number of concurrent connections to a Fibre Transport
media server, up to the total that is allowed per host.
See “Fibre Transport properties” on page 147.
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS_FT
 Configuring Host Properties 151
Firewall properties

Table 3-34 shows the values that NetBackup supports for the
NUMBER_DATA_BUFFERS_FT file. NetBackup supports 644 buffers per media server
for Fibre Transport.

Table 3-34 Supported values for buffers per FT connection

NUMBER_DATA_BUFFERS_FT Total concurrent Total concurrent

connections: NetBackup connections: Linux FT
5230 and 5330 and later media server
appliances

16 40 40

12 53 53

10 64 64

If you want, you then can limit the number of connections for a media server or
media servers by using the Maximum concurrent FT connections of the Fibre
Transport host properties.

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

Figure 3-27 Firewall dialog box

The Firewall dialog box contains the following properties.

 Configuring Host Properties 153
Firewall properties

Table 3-35 Firewall dialog box properties

Property Description

Default connect options By default, NetBackup selects firewall-friendly connect options under Default connect
options. However, the default options can be set differently for individual servers under
Attributes for selected Hosts.

By default, the firewall settings are configured to require the fewest possible ports to
be open.

These properties correspond to the DEFAULT_CONNECT_OPTIONS configuration option.

To change the default connect options for the selected server, click Change.

Click Change to change the Default connect options. Change the Firewall properties
in the Default Connect Options dialog box.
Note: If VNETD only is selected as the Daemon connection port, the BPCD connect
back setting is not applicable. If VNETD only is selected as the Daemon connection
port, Use non-reserved ports is always used regardless of the value of the Ports
setting.

Hosts list To change the default connect options for any server, add the server to the host list.
Servers do not automatically appear on the list.

■ Add option
Click Add to add a host entry to the host list. A host must be listed before it can be
selected for configuration.
■ Add to all option
Click Add to All to add the listed hosts (along with the specified properties) to all
hosts that are selected for host property configuration. (That is, the hosts that are
selected upon opening the Host Properties.)
■ Remove option
Select a host name in the list, then click Remove to remove the host from the list.

Attributes for selected hosts Connect options can be configured for individual servers.

These properties correspond to the CONNECT_OPTIONS configuration option.

 Configuring Host Properties 154
Firewall properties

Table 3-35 Firewall dialog box properties (continued)

Property Description

BPCD connect back This property specifies how daemons are to connect back to the NetBackup Client
daemon (BPCD) as follows:

■ Use default connect options (An option for individual hosts)

Use the methods that are specified under Default connect options.
■ Random port
NetBackup randomly chooses a free port in the allowed range to perform the
traditional connect-back method.
■ VNETD port
This method requires no connect-back. The Veritas Network Daemon (vnetd) was
designed to enhance firewall efficiency with NetBackup during server-to-server and
server-to-client communications. The server initiates all bpcd socket connections.
Consider the example in which bpbrm on a media server initially connects with
bpcd on a client. The situation does not pose a firewall problem because bpbrm
uses the well-known bpcd port.

Ports Select whether a reserved or non-reserved port number should be used to connect to
the server:

■ Use default connect options (An option for individual hosts)

Use the methods that are specified under Default attributes.
■ Reserved port
Connect to the server by a reserved port number.
■ Use non-reserved ports
Connect to the server by a non-reserved port number. If this property is selected,
also enable Accept connections from non-reserved ports for the selected server
in the Universal Settings properties.
See “Universal Settings properties” on page 258.
 Configuring Host Properties 155
General Server properties

Table 3-35 Firewall dialog box properties (continued)

Property Description

Daemon connection port This option only affects connections to NetBackup 7.0 and earlier. For connections to
NetBackup 7.0.1 and later, the veritas_pbx port is used.
If configuring connections for NetBackup 7.0 and earlier, select the Daemon connection
port method to use to connect to the server:

■ Use default connect options (An option for individual hosts)

Use the methods that are specified under Default connect options.
■ Automatic
The daemons on the server are connected to by vnetd if possible. If it is not possible
to use vnetd, the daemon’s traditional port number makes the connection.
■ VNETD only
The daemons on the server are connected to by vnetd only. Select this property
if your firewall rules prevent connections to the server by the traditional port number.
■ Daemon port only
The daemons on the server are connected to by the traditional port number only.

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

Defaults Set property settings back to the defaults.

Enabling logging for vnetd

Use the following procedure to enable logging for vnetd.
To enable logging for vnetd
◆ Create a vnetd directory in the following location:
■ On Windows: install_path\NetBackup\logs\vnetd
Or, double-click [Link] in the install_path\NetBackup\logs\
directory to populate the logs directory with log subdirectories, including
one for vnetd.
■ On UNIX: /usr/openv/logs/vnetd

General Server properties

The General Server properties apply to selected master and media servers.
 Configuring Host Properties 156
General Server properties

Figure 3-28 General Server dialog box

The General Server dialog box contains the following properties.

Table 3-36 General Server dialog box properties

Property Description

Delay on multiplexed restores This property specifies how long the server waits for additional restore requests
of multiplexed images on the same tape. All of the restore requests that are
received within the delay period are included in the same restore operation (one
pass of the tape).

The default is a delay of 30 seconds.

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

The default is 300 seconds (5 minutes).

Note: This property applies to the disk storage units of 6.0 media servers only.
Subsequent releases use internal methods to monitor disk space more frequently.
 Configuring Host Properties 157
General Server properties

Table 3-36 General Server dialog box properties (continued)

Property Description

Must use local drive This property appears for master servers only, but applies to all media servers
as well. This property does not apply to NDMP drives.

If a client is also a media server or a master server and Must use local drive is
checked, a local drive is used to back up the client. If all drives are down, another
can be used.

This property increases performance because backups are done locally rather
than sent across the network. For example, in a SAN environment a storage unit
can be created for each SAN media server. Then, the media server clients may
be mixed with other clients in a policy that uses ANY AVAILABLE storage unit.
When a backup starts for a client that is a SAN media server, the backups go to
the SAN connected drives on that server.

Use direct access recovery for By default, NetBackup for NDMP is configured to use Direct Access Recovery
NDMP restores (DAR) during NDMP restores. DAR can reduce the time it takes to restore files
by allowing the NDMP host to position the tape to the exact location of the
requested file(s). Only the data that is needed for those files is read.

Clear this check box to disable DAR on all NDMP restores. Without DAR,
NetBackup reads the entire backup image, even if only a single restore file is
needed.

Enable message-level cataloging This option performs message-level cataloging when you duplicate Exchange
when duplicating Exchange images backup images that use Granular Recovery Technology (GRT) from disk to tape.
that use Granular Recovery To perform duplication more quickly, you can disable this option. However, then
Technology users are not able to browse for individual items on the image that was duplicated
to tape.

See the NetBackup for Exchange Administrator's Guide.

 Configuring Host Properties 158
General Server properties

Table 3-36 General Server dialog box properties (continued)

Property Description

Media host override list Specific servers can be specified in this list as servers to perform restores,
regardless of where the files were backed up. (Both servers must be in the same
master and media server cluster.) For example, if files were backed up on media
server A, a restore request can be forced to use media server B.
The following items describe situations in which the capability to specify servers
is useful:

■ Two (or more) servers share a robot and each have connected drives. A restore
is requested while one of the servers is either temporarily unavailable or is
busy doing backups.
■ A media server was removed from the NetBackup configuration, and is no
longer available.

To add a host to the Media host override list, click Add.

Click Add to All to add a host to the list for all of the hosts currently selected.

To change an entry in the list, select a host name, then click Change.
Configure the following options in the Add Media Override settings or Change
Media Override settings dialog box:

■ Original backup server

Type the name of the server where data was backed up originally.
■ Restore server
Type the name of the server that is to process future restore requests.

Defaults Sets all properties back to the default settings.

Forcing restores to use a specific server

Use the following procedure to force restores to use a specific server.
 Configuring Host Properties 159
Global Attributes properties

To force restores to use a specific server

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

Global Attributes properties

The Global Attributes properties apply to currently selected master servers. The
Global Attributes properties affect all operations for all policies and clients. The
default values are adequate for most installations but can be changed.
 Configuring Host Properties 160
Global Attributes properties

Figure 3-29 Global Attributes dialog box

The Global Attributes dialog box contains the following properties.

Table 3-37 Global Attributes dialog box properties

Property Description

Job retry delay This property specifies how often NetBackup retries a job. The default is 10 minutes.
The maximum is 60 minutes; the minimum is 1 minute.
 Configuring Host Properties 161
Global Attributes properties

Table 3-37 Global Attributes dialog box properties (continued)

Property Description

Schedule backup attempts NetBackup considers the failure history of a policy to determine whether or not to run
a scheduled backup job. The Schedule backup attempts property sets the timeframe
for NetBackup to examine.
This property determines the following characteristics for each policy:

■ How many preceding hours NetBackup examines to determine whether to allow

another backup attempt (retry). By default, NetBackup examines the past 12 hours.
■ How many times a backup can be retried within that timeframe. By default,
NetBackup allows two attempts. Attempts include the scheduled backups that start
automatically or the scheduled backups that are user-initiated.
Consider the following example scenario using the default setting 2 tries every 12
hours:

■ Policy_A runs at 6:00 P.M.; Schedule_1 fails.

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

Note: This attribute does not apply to user backups and archives.

Policy update interval This property specifies how long NetBackup waits to process a policy after a policy is
changed. The interval allows the NetBackup administrator time to make multiple changes
to the policy. The default is 10 minutes. The maximum is 1440 minutes; the minimum
is 1 minute.

Maximum jobs per client This property specifies the maximum number of backup and archive jobs that NetBackup
clients can perform concurrently. The default is one job.
NetBackup can process concurrent backup jobs from different policies on the same
client only in the following situations:

■ More than one storage unit available

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

See “About constraints on the number of concurrent jobs” on page 162.

Compress catalog interval This property specifies how long NetBackup waits after a backup before it compresses
the image catalog file.
 Configuring Host Properties 162
Global Attributes properties

Table 3-37 Global Attributes dialog box properties (continued)

Property Description

Maximum vault jobs This property specifies the maximum number of vault jobs that are allowed to be active
on the master server. The greater the maximum number of vault jobs, the more system
resources are used.

If the active vault jobs limit is reached, subsequent vault jobs are queued and their
status is shown as Queued in the Activity Monitor.

If a duplication job or eject job waits, its status is shown as Active in the Activity Monitor.

See “About the Jobs tab” on page 1038.

Administrator email This property specifies the address(es) where NetBackup sends notifications of
address property scheduled backups or administrator-directed manual backups.

To send the information to more than one administrator, separate multiple email
addresses by using a comma, as follows:

useraccount1@[Link],useraccount2@[Link]

Disaster recovery information that is created during catalog backups is not sent to the
addresses indicated here. Disaster recovery information is sent to the address that is
indicated on the Disaster Recovery tab in the catalog backup policy.

See “Disaster Recovery tab” on page 851.

About constraints on the number of concurrent jobs

Specify any number of concurrent jobs within the following constraints.

Table 3-38 Constraints on concurrent jobs

Constraint Description

Number of storage devices NetBackup can perform concurrent backups to separate storage units or to drives
within a storage unit. For example, a single Media Manager storage unit supports as
many concurrent backups as it has drives. A disk storage unit is a directory on disk,
so the maximum number of jobs depends on system capabilities.
 Configuring Host Properties 163
Global Attributes properties

Table 3-38 Constraints on concurrent jobs (continued)

Constraint Description

Server and client speed Too many concurrent backups on an individual client interfere with the performance
of the client. The best setting depends on the hardware, operating system, and
applications that are running.

The Maximum jobs per client property applies to all clients in all policies.
To accommodate weaker clients (ones that can handle only a small number of jobs
concurrently), consider using one of the following approaches:

■ Set the Maximum data streams property for those weaker client(s) appropriately.
(This property is found under Host Properties > Master Servers > Double-click
on a specific master server > Client Attributes > General tab.)
See “General tab of the Client Attributes properties” on page 94.
■ Use the Limit jobs per policy policy setting in a client-specific policy. (A
client-specific policy is one in which all clients share this characteristic).
See “Limit jobs per policy (policy attribute)” on page 706.

Network loading The available bandwidth of the network affects how many backups can occur
concurrently. Two Exabyte 8500, 8mm tape drives can create up to a
900-kilobyte-per-second network load. Depending on other factors, the load might be
too much for a single Ethernet. For loading problems, consider backups over multiple
networks or compression.

A special case exists to back up a client that is also a server. Network loading is not a
factor because the network is not used. Client and server loading, however, is still a
factor.

Figure 3-30 Maximum jobs per client

Client

/home Policy A Tape Drive 1

Tape Drive 2
/usr Policy B

Server

Note: Catalog backups can run concurrently with other backups. To do so, set the
Maximum jobs per client value to greater than two for the master server. The
higher setting ensures that the catalog backup can proceed while the regular backup
activity occurs.
 Configuring Host Properties 164
Global Attributes properties

Setting up email notifications about backups

Email notifications can be sent to the client's administrator or to the global
administrator, specifying that a backup was successful or unsuccessful.
The following represents the contents of a notification email:

Backup on client hostname by root was partially successful.

File list
---------
C:\Documents and Settings

Before emails can be sent, the computing environment must be configured correctly.

Additional Windows configuration to receive emails

NetBackup can send notification to specified email addresses about backups on
all clients or specific clients.
The [Link] script must be configured on any Windows host that is to receive
email.
Windows systems also require that an application to transfer messages using the
Simple Mail Transfer Protocol be installed to accept script parameters. UNIX
platforms have an SMTP transfer method built into the system.

Additional UNIX configuration to receive emails

NetBackup uses the mail transfer agent sendmail to send email notifications. Install
sendmail from the following website and configure the environment accordingly:

[Link]

Notification methods
To set up email notifications about backups, choose one or both of the following
notification methods:
■ Send emails about failed backups only.
Send a message to the email address(es) of the NetBackup administrator(s)
about any backup that ends in a non-zero status.
To do so, configure the Administrator email address in the Global Attributes
properties. Since email is sent from the master server or the media server, the
[Link] script or sendmail must be configured on the master and the media
servers.
See “Sending messages to the global administrator about unsuccessful backups
only” on page 167.
■ Send emails about successful and failed backups.
 Configuring Host Properties 165
Global Attributes properties

Send a message to the local administrator(s) of each client about successful

and unsuccessful backups.
To do so, configure either the Client sends mail property or the Server sends
mail property in the Universal Settings properties for the client. Email is sent
from the client (Client sends mail) or the master or the media server (Server
sends mail). Therefore, [Link] or sendmail must be configured on the
master and the media servers, or the client if specified.
See “Sending messages to the administrator about successful and unsuccessful
backups” on page 167.
See “Installing and testing the email utility on Windows” on page 169.
See “About constraints on the number of concurrent jobs” on page 162.

Configuring the [Link] script on Windows

For Windows hosts to receive email notifications about backups, the [Link]
script must be configured on the host.
By default, [Link] does not send email. Use the following procedure to
configure the [Link] script.
To configure the [Link] script
1 On a NetBackup master server, copy [Link] from the following directory:
install_path\VERITAS\NetBackup\bin\goodies\[Link]

2 Paste it into the following directory on the server or client:

install_path\VERITAS\NetBackup\bin\
 Configuring Host Properties 166
Global Attributes properties

3 Use a text editor to open [Link]. Create a backup copy of [Link]

before modifying it.
In some text editors, using the word wrap option can create extra line feeds in
the script and render it non-functional.
The following options are used in the script:

-s The subject line of the email

-t Indicates who receives the email.

-i The originator of the email, though it is not necessarily known to the

mail server. The default (-i NetBackup) shows that the email is from
NetBackup.

-server The name of the SMTP server that is configured to accept and relay
emails.

-q Suppresses all output to the screen.

4 Most of the lines are informational in [Link].

Locate the following lines in the script:

@REM @IF "%~4"=="" (

@REM blat %3 -s %2 -t %1 -i NetBackup -server SERVER_1 -q
@REM ) ELSE (
@REM blat %3 -s %2 -t %1 -i NetBackup -server SERVER_1 -q -attach %4
@REM )

5 Adjust the fives lines as follows:

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

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

6 Save [Link].
See “About constraints on the number of concurrent jobs” on page 162.
 Configuring Host Properties 167
Global Attributes properties

Sending messages to the global administrator about unsuccessful

backups only
Use the following procedure to send messages to the global administrator about
backups with a non-zero status.
To send messages to the global administrator about backups with a non-zero
status
1 On Windows servers, install and configure a mail client.
See “Installing and testing the email utility on Windows” on page 169.
Edit the [Link] script.
See “Configuring the [Link] script on Windows” on page 165.
2 On the master server, open the NetBackup Administration Console.
3 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Master Server.
4 In the right pane, double-click the master server you want to modify.
5 Open the host properties of the master server.
6 In the properties dialog box, in the left pane, click Global Attributes.
7 In the Administrator’s email address field, enter the email address of the
administrator to receive the notification emails. (Separate multiple addresses
with commas.) Click Apply.
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@[Link]

Sending messages to the administrator about successful and

unsuccessful backups
An alternative to sending all emails through the master server is to send emails
through each client or through the media server that backed up the client. An email
can be sent to the administrator after every backup.
 Configuring Host Properties 168
Global Attributes properties

To send email notifications for all backups from a client

1 On a Windows client, install and configure a mail client.
See “Installing and testing the email utility on Windows” on page 169.
On the client or the media server, edit the [Link] script, depending on
whether Client sends mail is enabled or Server sends mail is enabled in step
6.
See “Configuring the [Link] script on Windows” on page 165.
2 On the master server, open the NetBackup Administration Console.
3 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Clients.
4 In the right pane, double-click the client you want to modify. Multiple clients
can also be selected.
5 In the properties dialog box, in the left pane, select Universal Settings.
6 Enable the Client sends mail option or if the client cannot send mail, enable
the Server sends mail option.
7 In the Client administrator’s email field, enter the email address of the
administrator(s) to receive the notification emails. (Separate multiple addresses
with commas.) Click Apply.
See “Universal Settings properties” on page 258.
 Configuring Host Properties 169
Global Attributes properties

Installing and testing the email utility on Windows

BLAT is the most common application is used for email notification. It is a mail client
in the public domain. BLAT is used as an example in the following discussions.
Use the following procedure to install and configure the email utility.
To install and configure the email utility
1 Download the .ZIP file from the BLAT download page, currently: [Link]
2 Extract the files to a directory.
3 Copy the [Link] file to the Windows System32 directory.
4 From a command prompt, run the following command:

blat -install [Link] useraccount@[Link]

Where:
[Link] is the host name or IP address of the mail server
that sends the email notifications.
useraccount@[Link] is the primary account to send the emails from
the specified server.
5 Test the email utility, following the To test the email utility procedure.
Use the following procedure to test the email utility.
To test the email utility
1 Create a test text file that contains a message. For example, create
C:\[Link]

2 From a command prompt, run:

blat C:\[Link] -s test_subject -to useraccount@[Link]

A correct setup sends the contents of [Link] to the email address

specified.
3 Use the following list to troubleshoot problems if NetBackup notification does
not work correctly:
■ Make sure that the BLAT command is not commented out in the [Link]
script.
■ Make sure that the path to [Link] is specified in [Link] if the
command is not in the \system32 directory.
■ Make sure that BLAT syntax has not changed in the later versions of BLAT.
Check the readme for the version of BLAT running on the system.
 Configuring Host Properties 170
Logging properties

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

Logging properties
The Logging properties apply to the master servers, media servers, and the clients
that are currently selected. The available properties differ between master servers,
media servers, and clients. The Logging properties contain the processes that
continue to use Legacy logging as well as processes that use Unified logging.
NetBackup Administration Console logging describes the logging for the NetBackup
Administration Console.

Legacy logging
For those processes that use legacy logging, administrators must first create a log
directory for each process to be logged. A logging level selection on the Logging
properties page does not create the log directory.

Note: If you have used the Logging Assistant tool earlier, you do not need to
manually create log directories. The Logging Assistant tool automatically creates
log directories.

Create the NetBackup legacy log directories in the following locations:

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

Note: Do not save logs to a remote file system such as NFS or CIFS. Logs that are
stored remotely and then grow large can cause critical performance issues.

To create all of the NetBackup debug log directories at one time, run the following
files:
 Configuring Host Properties 171
Logging properties

■ On Windows, run [Link]:

install_path\NetBackup\logs\[Link]

■ On UNIX, run the mklogdir shell script: /usr/openv/netbackup/logs/mklogdir

Create the Media Manager legacy log directories in the following locations:
■ On Windows: install_path\Volmgr\debug
■ On UNIX: /usr/openv/volmgr/debug
In the case of legacy logging, NetBackup uses the configuration file (the Windows
registry or the [Link] file on UNIX) to set the maximum size of a log file. Use the
bpsetconfig command-line interface to configure the following parameters:

■ The MAX_LOGFILE_SIZE parameter indicates the maximum size of a log file.

When the log file size in NetBackup matches the MAX_LOGFILE_SIZE setting,
the next logs are stored in a new log file.
See “MAX_LOGFILE_SIZE option for NetBackup servers and clients for legacy
logging” on page 313.
■ The MAX_NUM_LOGFILES parameter indicates the maximum number of log files
that can be created in NetBackup. When the number of log files matches the
MAX_NUM_LOGFILES setting, the older log files are purged.
See “MAX_NUM_LOGFILES option for NetBackup servers and clients for legacy
logging” on page 314.

Note: Do not edit the configuration file manually because incorrect syntax or
characters in the file may adversely affect NetBackup operations.

See the NetBackup Commands Reference Guide for information about the
bpsetconfig command.

Unified logging
Unified logging creates log file names and messages in a format that is standardized
across Veritas products. Some NetBackup processes on the server use unified
logging.
Unified logging writes the logs into subdirectories in the following locations:
■ On Windows: install_path\NetBackup\logs
■ On UNIX: /usr/openv/logs
Unlike legacy logging, subdirectories for the processes that use unified logging are
created automatically.
 Configuring Host Properties 172
Logging properties

Note: Do not save logs to a remote file system such as NFS or CIFS. Logs that are
stored remotely and then grow large can cause critical performance issues.

In the case of unified logging, NetBackup uses the [Link] configuration file
to set the maximum size of a log file. Use the vxlogcfg command to configure the
following log settings in the [Link] file:
■ Configure the MaxLogFileSizeKB parameter to set the maximum size of a log
file. When the log file size in NetBackup matches the MaxLogFileSizeKB setting,
the next logs are stored in a new log file.
■ Configure the NumberOfLogFiles parameter to set the maximum number of log
files that you want to create in NetBackup. When the number of log files in
NetBackup matches the NumberOfLogFiles setting, the older log files are purged.
See the NetBackup Logging Reference Guide for more information about
controlling the log file size.

Note: Do not edit the [Link] file manually. Incorrect syntax or characters in
the file may adversely affect NetBackup operations.

See the NetBackup Commands Reference Guide for information about the vxlogcfg
command and the [Link] file.
 Configuring Host Properties 173
Logging properties

Figure 3-31 Logging dialog box

The Logging dialog box contains the following properties:

 Configuring Host Properties 174
Logging properties

Table 3-39 Logging dialog box properties

Property Description

Global logging This property controls the logging level for all processes in the Logging dialog box that are set
level to Same as global. The logging levels control the amount of information that the NetBackup
server writes to the logs.

■ No logging
No log is created for any process that is set to Same as global.
■ Minimum logging (default)
A small amount of information is logged for each process that is set to Same as global.
Use this setting unless advised otherwise by Veritas Technical Support. Other settings can
cause the logs to accumulate large amounts of information.
■ Levels 1 through 4
Progressively more information is logged at each level for each process that is set to Same
as global.
■ 5 (Maximum)
The maximum amount of information is logged for each process that is set to Same as global.

Some NetBackup processes allow individual control over the amount of information the process
writes to logs. For those processes you can specify a different logging level other than Same as
global.

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

■ On Windows: install_path\NetBackup\logs\process_name
■ On UNIX: /usr/openv/netbackup/logs/process_name
The following settings are available for each process:

■ Same as global
Make this selection to use the same logging level as the Global logging level property. If
the Global logging level is set to No logging, no log is created for the individual process.
■ No logging
No log is created for the specific process.
■ Minimum logging
A small amount of information is logged for the specific process.
■ Levels 1 through 4
Progressively more information is logged at each level for the specific process.
■ 5 (Maximum)
The maximum amount of information is logged for the specific process.

Table 3-40 lists and describes the processes that use legacy logging.
 Configuring Host Properties 175
Logging properties

Table 3-39 Logging dialog box properties (continued)

Property Description

Debug logging These services use unified logging.

levels for Each service creates a log automatically in the following directories:
NetBackup
services ■ On Windows: install_path\NetBackup\logs
■ On UNIX: /usr/openv/logs
The following settings are available for each process:

■ Same as global
Make this selection to use the same logging level as the Global logging level property. If
the Global logging level is set to No logging, no log is created for the individual process.
■ No logging
No log is created for the specific process.
■ Minimum logging
A small amount of information is logged for the specific process.
■ Levels 1 through 4
Progressively more information is logged at each level for the specific process.
■ 5 (Maximum)
The maximum amount of information is logged for the specific process.

You can also use the vxlogcfg command to change debug levels.

Table 3-41 lists and describes the services that use unified logging.
 Configuring Host Properties 176
Logging properties

Table 3-39 Logging dialog box properties (continued)

Property Description

Click Enable to create logs for critical NetBackup processes. In previous NetBackup versions,
logging starts once you have created the log directories for the required processes. After you
click Enable, the log directories are automatically created for the critical NetBackup processes
and logging begins.

See “ENABLE_CRITICAL_PROCESS_LOGGING” on page 316.

Note: Enabling Logging for critical processes is a one-time activity that you can do using the
NetBackup Administration Console. After the logging is enabled, you cannot disable it using the
Logging dialog box. To manually disable the logging for a process, disable the logging level of
the process.

See “Disabling the logging of NetBackup processes” on page 180.

If you have enabled Logging for critical processes, clicking Defaults does not modify Logging
for critical processes and Keep logs up to GB options. While changing the logging properties
for multiple hosts, if the Logging for critical processes option on one of the hosts is enabled,
clicking Defaults does not modify the Logging for critical processes and Keep logs up to GB
options of any host.

See “Standard host property dialog box options” on page 74.

After the Logging for critical processes is enabled, NetBackup sets the log retention to the
default log size in GB. You can modify it by reconfiguring the Keep logs up to GB option.
Note: Clearing the Keep logs up to GB option may adversely affect NetBackup operations.
Veritas recommends that you specify the log retention in GB when Logging for critical processes
is enabled.

The following critical NetBackup processes are logged when you select the Enable option:
Master server processes:

■ bprd
■ bpdbm
Media server processes:

■ bpbrm
■ bptm
■ bpdm
Client processes:

■ bpfis

Note: You can enable Logging for critical processes for master servers, media servers, and
clients. You cannot enable Logging for critical processes for media servers and clients at
versions earlier than NetBackup 7.7, even if they are associated with current version master
servers.
 Configuring Host Properties 177
Logging properties

Table 3-39 Logging dialog box properties (continued)

Property Description

Keep logs for Specifies how many days to keep the logs in case you need the logs to evaluate failures. For
days example, if you check the backups every day, you can delete the logs sooner than if you check
the backups once a month. However, the logs can consume a large amount of disk space, so do
not keep the logs any longer than necessary. The default is 28 days.

Specifies the length of time, in days, that the master server keeps its error catalog, job catalog,
and debug log information. NetBackup derives the Backup Status, Problems, All Log Entries,
and Media Log reports from the error catalog. Also limits the time period that these reports can
cover. When this time expires, NetBackup also deletes these logs (that exist) on media servers
and clients.
 Configuring Host Properties 178
Logging properties

Table 3-39 Logging dialog box properties (continued)

Property Description

Keep logs up to Specifies the size of the NetBackup logs that you want to retain. When the NetBackup log size
GB grows to this value, the older logs are deleted. To set the log size in GB, select the check box
and specify the value in GB.

See “KEEP_LOGS_SIZE_GB for NetBackup servers and clients” on page 315.

Note: In the case of NetBackup servers, the recommended value for the Keep logs up to GB
option is 25 GB or greater.

In the case of clients, the recommended value for the Keep logs up to GB option is 5 GB or
greater.

While configuring the Keep logs up to GB option, consider the NetBackup log pruning behavior.
All logs are retained until the log size reaches the high watermark, that is, 95% of the Keep logs
up to GB value. NetBackup checks for the log size every 10 minutes. Once the log size reaches
the high watermark, the deletion of older logs is started. The deletion continues until the log size
reaches the low watermark, that is, 85% of the Keep logs up to GB value.
Consider the following example:

■ The Keep logs up to GB option is set to 100 GB.

■ NetBackup logs are created and retained until the log size reaches the high watermark, that
is, 95 GB.
■ NetBackup checks the log size every 10 minutes and determines that the log size is 95 GB.
■ Log pruning is started and older logs are deleted until the log size reaches the low watermark,
that is, 85 GB.
■ Log pruning stops when the log size reaches 85 GB and all existing logs are retained until
the log size again reaches the high watermark.

If you do not select the Keep logs up to GB option, the default value is unlimited. The log retention
or log pruning does not happen based on the log size.

If both Keep logs up to GB and Keep logs for days are selected, the logs are pruned depending
on the condition that occurs first.

If no log retention options are selected, the increasing log size may eventually lead to a situation
of low disk space, as all logs are retained.
Note: You can verify the log pruning behavior in NetBackup using the logs at the following
location:

On Windows: install_path\NetBackup\logs\nbutil

On UNIX: /usr/openv/netbackup/logs/nbutil

Note: The Keep logs up to GB option is available for the NetBackup master server, media
server, and clients. The older versions of NetBackup media servers and clients that are associated
with NetBackup 7.7 master servers do not have the Keep logs up to GB option.
 Configuring Host Properties 179
Logging properties

Table 3-39 Logging dialog box properties (continued)

Property Description

Keep Vault logs If NetBackup Vault is installed, the Keep Vault logs for property is enabled. Select the number
for of days to keep the Vault session directories, or select Forever.

Session directories are found in the following location:

install_path\netbackup\vault\sessions\vaultname\
session_x

where x is the session number. This directory contains vault log files, temporary working files,
and report files.

Note: While collecting NetBackup logs using Logging Assistant, the total NetBackup
log size may increase. If you have enabled the new Keep logs up to GB option
and the total NetBackup log size reaches its high water mark, logs are deleted.
Logs that you want to retain may also be deleted. To avoid the deletion of logs that
you want to retain, disable the Keep logs up to GB option while you collect logs
using Logging Assistant. Alternatively, you can set the Keep logs up to GB option
to a value higher than the current value, so that the important logs are not deleted
before the log collection is complete.
See “About the Logging Assistant” on page 1081.

Table 3-40 Process-specific overrides

Service Description

BPBRM logging level The NetBackup backup and restore manager.

BPTM logging level The NetBackup tape manager.

BPDM logging level The NetBackup disk manager.

BPJOBD logging level The NetBackup Jobs Database Management daemon.

BPDBM logging level The NetBackup database manager.

BPRD logging level The NetBackup request daemon or manager.

 Configuring Host Properties 180
Logging properties

Table 3-41 Debug logging levels for NetBackup services

Service Description

Policy Execution Manager This property appears for master servers.

NBPEM creates Policy/Client tasks and
determines when jobs are due to run. If a
policy is modified or if an image expires,
NBPEM is notified and the appropriate
Policy/Client tasks are updated.

Job Manager This property appears for master servers.

NBJM accepts the jobs that the Policy
Execution Manager submits and acquires the
necessary resources.

Resource Broker NBRB makes the allocations for storage units,

tape drives, client reservations.

Note: The Enable robust logging property has been removed from this release.
Robust logging is now enabled by default.
The Enable robust logging property appears for earlier versions of master servers,
media servers, or clients.
For more information about robust logging, refer to the section about legacy logging
in the NetBackup Logging Reference Guide.

NetBackup Administration Console logging

Legacy logging and unified logging write information about the NetBackup processes
that backup, restore, duplicate, and so on. You can also configure NetBackup so
that it writes log information about the NetBackup Administration Console. The
log information may be helpful to troubleshoot problems.
See “Configuring log files for the NetBackup Administration Console” on page 54.
The NetBackup Logging Reference Guide describes how to troubleshoot the
NetBackup Administration Console:
[Link]

Disabling the logging of NetBackup processes

You can disable the logging of a NetBackup process by changing the logging level
of the process.
 Configuring Host Properties 181
Logging properties

Note: To enable Logging for critical processes, in the NetBackup Administration

Console, select NetBackup Management > Host Properties. Double-click on
Master Servers, Media Servers, or Clients and select a host. Open the Logging
properties and click Enable.

To disable the logging of a process by changing the logging level

◆ Do any of the following:
■ In the Logging dialog box, in the Process specific overrides pane, set
the logging level of the process to No logging.
■ Use the Logging Assistant to change the logging level of a process to disable
the logging of the process.
See “Disabling debug logging” on page 1097.

Note: For the processes for which you cannot change or disable logging
levels using the Logging > Process specific overrides pane or the Logging
Assistant, use the configuration file option.

■ Change or disable the logging level of a process by modifying using the

configuration file (the Windows registry or the [Link] file in UNIX). Use
the bpsetconfig command to set the ProcessName_VERBOSE parameter
to -2.
Example 1 - To disable logging for the bprd process, use the bpsetconfig
command to set the value of BPRD_VERBOSE as follows:

bpsetconfig> BPRD_VERBOSE = -2

Example 2 - To disable logging for the bpfis process that is specific to

NetBackup clients, run the bpsetconfig command on the associated media
server or master server with the - h host option to set the value of
BPFIS_VERBOSE as follows:

bpsetconfig> -h client_host_name
bpsetconfig> BPFIS_VERBOSE = -2

See the NetBackup Commands Reference Guide for information on the

bpsetconfig command.

Note: Do not edit the configuration file manually. Incorrect syntax or

characters in the file may adversely affect NetBackup operations.
 Configuring Host Properties 182
Login Banner Configuration properties

Login Banner Configuration properties

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

Figure 3-32 Login Banner Configuration dialog box

The first time that the NetBackup Administration Console is launched, the Login
Banner Configuration properties are not configured so no banner appears to the
user. The Login Banner Configuration host properties must be configured in order
for the banner to appear.
 Configuring Host Properties 183
Login Banner Configuration properties

The user can change the server once they log into the console. (On the File menu,
click Change Server.) If the banner is configured for the remote server, the banner
appears on the remote server as well.

Note: The banner is not available on NetBackup versions before 6.5.4. If a user
changes to a host that is at NetBackup version 6.5.3 or earlier, no banner appears.

If a user opens a new console or window from the existing console, the banner
does not appear for the new window. (On the File menu, click the New Console
option or the New Window from Here option.)

Table 3-42 Login Banner Configuration dialog box properties

Property Description

Login Banner Heading Enter the text that is to appear in the banner.

Text of login banner Enter the text for the banner message. The maximum is 29,000 characters.

Show Agree and Disagree buttons on Configure this option when approval is necessary to use the NetBackup
the login banner Administration Console or the Backup, Archive, and Restore client
console. Specific approval may be required due to a legal agreement at the
company in which the NetBackup environment resides.

If this option is enabled, users are required to click the Agree option and
then click OK before the console opens. The agreement is meant only for
the user that reads and agrees to the message.

If the user chooses the Disagree option, the screen is closed.

 Configuring Host Properties 184
Login Banner Configuration properties

Figure 3-33 Login Banner with agreement option enabled

Figure 3-34 Login Banner without agreement option

Removing login banner screen and text

To remove the banner and the text that appears after a user logs into NetBackup,
use the following procedure:
 Configuring Host Properties 185
Login Banner Configuration properties

To remove the login banner screen and text

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

Enabling the Auto log off timeout option

A related option, but one not configured in the Login Banner Configuration host
properties, is the Auto log off timeout option.
The Auto log off timeout option allows NetBackup to automatically log a user out
of the NetBackup Administration Console after a period of inactivity. The session
must be inactive for the configurable number of minutes, hours, or days before the
logoff.
To enable the Auto log off timeout option
1 Select View > Options. Then select the Administrative Options tab (UNIX)
or the Administration Console tab (Windows).
2 Check the Auto log off timeout option.
3 Select the duration after which the user is logged off from an inactive session.
The minimum logoff duration is 10 minutes and the maximum is two days.
Five minutes before the timeout value is reached, NetBackup warns that the
session is to expire in five minutes.
4 If the logoff warning appears, the user can choose one of the following options:
■ Ignore
If the user selects this option (or does not respond to the warning), a dialog
box displays the time that remains before the session ends. Countdown
warnings display every minute until the timeout value is reached. When the
session ends, the user is logged out of the NetBackup Administration
Console or the Backup, Archive, and Restore client console.
■ Extend
If the user selects this option, the session continues and the timeout extends
by the logoff timeout value.
 Configuring Host Properties 186
Lotus Notes properties

If the user begins to work at the console again, the logoff is canceled until
the console is left idle again.
■ Log off
If the user selects this option, the session ends and NetBackup logs off the
user immediately.

Lotus Notes properties

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

Figure 3-35 Lotus Notes dialog box

The following properties can be configured in the Lotus Notes host properties or
by using the nbgetconfig and nbsetconfig commands.
See “Methods to set the NetBackup configuration options” on page 70.
 Configuring Host Properties 187
Lotus Notes properties

For UNIX servers: If you have multiple installations of Domino server, the values
in the client properties or the [Link] only apply to one installation. For other
installations, specify the installation path and location of the [Link] file with the
LOTUS_INSTALL_PATH and NOTES_INI_PATH directives in the backup policy.

Table 3-43 Lotus Notes client host properties

Client host Configuration options Description

properties

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

LOTUS_NOTES_LOGCACHESIZE = 3

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

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

If you do not specify a path, during recovery NetBackup restores

the logs to the Domino server's transaction log directory.
Note the following before specifying the Transaction log cache
path:

■ If the specified path does not exist then it is created during

restore.
■ The restore job fails with a Status 5 error if the user does not
have write permission for the folder.
■ Transaction logs are restored to the original location, the
Domino transaction log directory, if a path is not specified.
■ If the value of Maximum number of logs to restore is less
than or equal to 1 then this path is ignored. The logs are not
prefetched; one transaction log per job is restored to the
Domino Server’s log directory.
■ If there is not sufficient space to restore the specified number
of logs, NetBackup tries to restore only the number of logs
that can be accommodated.
 Configuring Host Properties 188
Lotus Notes properties

Table 3-43 Lotus Notes client host properties (continued)

Client host Configuration options Description

properties

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

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

Path LOTUS_NOTES_PATH Specify the path where the Lotus Notes program files reside on
the client. NetBackup must know where these files are to perform
In the Windows registry, this value
backup and restore operations. The value in this box overrides
is a string value.
the Lotus registry key, if both are defined.
Specify the path where the Lotus Notes program files reside on
the client:
■ On Windows:
Specify the path for Lotus program directory (where
[Link] resides). For example:
D:\Lotus\Domino
■ On UNIX:
Specify a path that includes the Domino data directory, the
Lotus program directory, and the Lotus resource directory.
For example:
/export/home/notesdata:/opt/lotus/notes/latest
/sunspa:/opt/lotus/notes/latest/sunspa/res/C

The Path value overrides the Lotus registry value, if both are
defined.
 Configuring Host Properties 189
Media properties

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

Figure 3-36 Media dialog box

The Media dialog box contains the following properties.

 Configuring Host Properties 190
Media properties

Table 3-44 Media dialog box properties

Property Description

Allow media overwrite This property overrides the NetBackup overwrite protection for specific media types.
property Normally, NetBackup does not overwrite certain media types. To disable overwrite
protection, place a check in the check box of one or more of the listed media formats.

For example, place a check in the CPIO check box to permit NetBackup to overwrite
the cpio format.

By default, NetBackup does not overwrite any of the formats on removable media, and
logs an error if an overwrite attempt occurs. This format recognition requires that the
first variable length block on a media be less than or equal to 32 kilobytes.
The following media formats on removable media can be selected to be overwritten:

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

■ When AOS/VS is enabled, AOS/VS media can be overwritten. (Data General
AOS/VS backup format.)
■ When CPIO is enabled, CPIO media can be overwritten.
■ When DBR is enabled, DBR media can be overwritten. (The DBR backup format
is no longer used.)
■ Remote Storage MTF1 media format. When MTF1 is enabled, Remote Storage
MTF1 media format can be overwritten.
■ When TAR is enabled, TAR media can be overwritten.
■ When MTF is enabled, MTF media can be overwritten. With only MTF checked, all
other MTF formats can be overwritten. (The exception is Backup Exec MTF
(BE-MTF1) and Remote Storage MTF (RS-MTF1) media formats, which are not
overwritten.
■ When BE-MTF1 is enabled, Backup Exec MTF media can be overwritten.

See “Results when media overwrites are not permitted” on page 193.
 Configuring Host Properties 191
Media properties

Table 3-44 Media dialog box properties (continued)

Property Description

Enable SCSI reserve This property allows exclusive access protection for tape drives. With access protection,
other host bus adaptors cannot issue commands to control the drives during the
reservation.

SCSI reservations provide protection for NetBackup Shared Storage Option

environments or any other multiple-initiator environment in which drives are shared.

The protection setting configures access protection for all tape drives from the media
server on which the option is configured. You can override the media server setting
for any drive path from that media server.

See “Recommended use for Enable SCSI reserve property” on page 194.

See “Drive path options” on page 431.

The following are the protection options:

■ The SCSI persistent reserve option provides SCSI persistent reserve protection
for SCSI devices. The devices must conform to the SCSI Primary Commands - 3
(SPC-3) standard. SCSI persistent reserve is valid for NetBackup 6.5 and later
servers only. If you enable SCSI persistent reserve, NetBackup does not send
persistent reserve commands to NetBackup media servers earlier than release 6.5.
■ The SPC-2 SCSI reserve option (default) provides SPC-2 SCSI reserve protection
for SCSI devices. The devices must conform to the reserve and release management
method in the SCSI Primary Commands - 2 standard.
■ To operate NetBackup without tape drive access protection, clear the Enable SCSI
reserve property. If unchecked, other HBAs can send the commands that may
cause a loss of data to tape drives.

Note: Ensure that all of your hardware processes SCSI persistent reserve commands
correctly. All of your hardware includes Fibre Channel bridges. If the hardware does
not process SCSI persistent reserve commands correctly and NetBackup is configured
to use SCSI persistent reserve, no protection may exist.

Allow multiple retentions This property lets NetBackup mix retention levels on tape volumes. It applies to media
per media in both robotic drives and nonrobotic drives. The default is that the check box is clear
and each volume can contain backups of only a single retention level.

Allow backups to span tape This property, when checked, lets backups span to multiple tape media. This property
media lets NetBackup select another volume to begin the next fragment. The resulting backup
has data fragments on more than one volume. The default is that Allow backups to
span tape media is checked and backups are allowed to span media.

If the end of media is encountered and this property is not selected, the media is set
to FULL and the operation terminates abnormally. This action applies to both robotic
drives and nonrobotic drives.
 Configuring Host Properties 192
Media properties

Table 3-44 Media dialog box properties (continued)

Property Description

Allow backups to span disk This property lets backups span disk volumes when one disk volume becomes full.
The default is that this property is enabled.

The Allow backups to span disk property does not apply to AdvancedDisk or
OpenStorage storage units. Backups span disk volumes within disk pools automatically.
The following destinations support disk spanning:

■ A BasicDisk storage unit spanning to a BasicDisk storage unit. The units must be
within a storage unit group.
■ An OpenStorage or AdvancedDisk volume spanning to another volume in the disk
pool.
For disk spanning to occur, the following conditions must be met:

■ The storage units must share the same media server.

■ The multiplexing level on spanning storage units should be the same. If there are
any differences, the level on the target unit can be higher.
See “Enable multiplexing storage unit setting” on page 576.
■ A disk staging storage unit cannot span to another storage unit. Also, a disk staging
storage unit is not eligible as a target for disk spanning.
■ Disk spanning is not supported on NFS.

Enable standalone drive This property lets NetBackup use whatever labeled or unlabeled media is found in a
extension nonrobotic drive. The default is that the Enable standalone drive extension property
is enabled.

Enable job logging This property allows the logging of the job information. This logging is the same
information that the NetBackup Activity Monitor uses. The default is that job logging
occurs.

Enable unrestricted media This property controls media sharing, as follows:

sharing for all media
■ Enable this property to allow all NetBackup media servers and NDMP hosts in the
servers
NetBackup environment to share media for writing. Do not configure server groups
for media sharing.
■ Clear this property to restrict media sharing to specific server groups. Then configure
media server groups and backup policies to use media sharing.
■ Clear this property to disable media sharing. Do not configure media server groups.

The default is that media sharing is disabled. (The property is cleared and no server
groups are configured.)

See “About NetBackup server groups” on page 380.

 Configuring Host Properties 193
Media properties

Table 3-44 Media dialog box properties (continued)

Property Description

Media ID prefix This property specifies the media ID prefix to use in media IDs when the unlabeled
(non-robotic) media is in nonrobotic drives. The prefix must be one to three alpha-numeric characters.
NetBackup appends numeric characters. By default, NetBackup uses A and assigns
media IDs such as A00000, A00001, and so on.

For example, if FEB is specified, NetBackup appends the remaining numeric characters.
The assigned media IDs become FEB000, FEB001, and so on. (Note that this
numbering does not work with the Configure Volumes wizard).

Media unmount delay To specify a Media unmount delay property indicates that the unloading of media is
delayed after the requested operation is complete. Media unmount delay applies only
to user operations, to include backups and restores of database agent clients, such
as those running NetBackup for Oracle. The delay reduces unnecessary media
unmounts and the positioning of media in cases where the media is requested again
a short time later.

The delay can range from 0 seconds to 1800 seconds. The default is 180 seconds. If
you specify 0, the media unmount occurs immediately upon completion of the requested
operation. Values greater than 1800 are set to 1800.

Media request delay This property specifies how long NetBackup waits for media in nonrobotic drives. A
configurable delay is useful if a gravity feed stacker is used on a nonrobotic drive. A
delay often exists between dismounting one media and mounting another. The default
is 0 seconds.

During the delay period, NetBackup checks every 60 seconds to see if the drive is
ready. If the drive is ready, NetBackup uses it. Otherwise, NetBackup waits another
60 seconds and checks again. If the total delay is not a multiple of 60, the last wait is
the remainder. If the delay is less than 60 seconds, NetBackup checks after the end
of the delay.

For example, set the delay to 150 seconds. NetBackup waits 60 seconds, checks for
ready, waits 60 seconds, checks for ready, waits 30 seconds, and checks for ready
the last time. If the delay was 50 seconds (a short delay is not recommended),
NetBackup checks after 50 seconds.

Results when media overwrites are not permitted

If media contains one of the protected formats and media overwrites are not
permitted, NetBackup takes the following actions:

If the volume has not been previously ■ Sets the volume’s state to FROZEN
assigned for a backup ■ Selects a different volume
■ Logs an error
 Configuring Host Properties 194
Media properties

If the volume is in the NetBackup media ■ Sets the volume’s state to SUSPENDED
catalog and was previously selected for ■ Aborts the requested backup
backups ■ Logs an error

If the volume is mounted for a backup of the The backup is aborted and an error is logged.
NetBackup catalog The error indicates the volume cannot be
overwritten.

If the volume is mounted to restore files or list NetBackup aborts the request and logs an
the media contents error. The error indicates that the volume
does not have a NetBackup format.

Recommended use for Enable SCSI reserve property

All tape drive and bridge vendors support the SPC-2 SCSI reserve and release
method. NetBackup has used SPC-2 SCSI reserve since NetBackup 3.4.3, and it
is the default tape drive reservation method in NetBackup. SPC-2 SCSI reserve is
effective for most NetBackup environments.
The SCSI persistent reserve method provides device status and correction and
may be more effective in the following environments:
■ Where NetBackup media servers operate in a cluster environment.
NetBackup can recover and use a reserved drive after a failover (if NetBackup
owns the reservation). (With SPC-2 SCSI reserve, the drive must usually be
reset because the reservation owner is inoperative.)
■ Where the drive has high availability.
NetBackup can resolve NetBackup drive reservation conflicts and maintain high
drive availability. (SPC-2 SCSI reserve provides no method for drive status
detection.)
However, the SCSI persistent reserve method is not supported or not supported
correctly by all device vendors. Therefore, thoroughly analyze the environment to
ensure that all of the hardware supports SCSI persistent reserve correctly.
Veritas recommends careful consideration of all of the following factors before
Enable SCSI reserve is used:
■ Only a limited number of tape drive vendors support SCSI persistent reserve.
■ SCSI persistent reserve is not supported or not supported correctly by all Fibre
Channel bridge vendors. Incorrect support in a bridge means no access
protection. Therefore, if the environment uses bridges, do not use SCSI persistent
reserve.
■ If parallel SCSI buses are used, carefully consider the use of SCSI persistent
reserve. Usually, parallel drives are not shared, so SCSI persistent reserve
 Configuring Host Properties 195
NDMP Global Credentials properties

protection is not required. Also, parallel drives are usually on a bridge, and
bridges do not support SCSI persistent reserve correctly. Therefore, if the
environment uses parallel SCSI buses, do not use SCSI persistent reserve.
■ The operating system tape drivers may require extensive configuration to use
SCSI persistent reserve. For example, if the tape drives do not support SPC-3
Compatible Reservation Handling (CRH), ensure that the operating system does
not issue SPC-2 reserve and release commands.
If any of the hardware does not support SCSI persistent reserve, Veritas
recommends that SCSI persistent reserve is not used.

NDMP Global Credentials properties

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

Figure 3-37 NDMP Global Credentials dialog box

 Configuring Host Properties 196
NDMP Global Credentials properties

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

Table 3-45 NDMP Global Credentials dialog box properties

Property Description

User name The user name under which NetBackup accesses the NDMP server. This user must
have permission to run NDMP commands.

Password Enter the password.

Confirm password Re-enter the password.

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

Note: Be careful when you add an NDMP host. If you add NDMP host credentials
using the fully qualified domain name (FQDN), you must also indicate the fully
qualified domain name on the client for lookups. That is, the server list in the Backup,
Archive, and Restore administration console must list the NDMP host by the FQDN
as well.
If you add NDMP host credentials using its short name, you can use either the short
name or the FQDN in the client server list.
 Configuring Host Properties 197
Network properties

Figure 3-38 Add NDMP Host dialog box

For NDMP Global Credentials

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

Network properties
Use the Network properties to set the properties that define requirements for
communications between clients and the master server. The Network properties
apply to currently selected Windows clients.
 Configuring Host Properties 198
Network properties

Figure 3-39 Network dialog box

The Network dialog box contains the following properties.

Table 3-46 Network dialog box properties

Property Description

NetBackup client service This property specifies the port that the NetBackup client uses to communicate with
port (BPCD) the NetBackup server. The default is 13782.
Note: If you change this port number, remember that it must be the same for all
NetBackup servers and clients that communicate with one another.

NetBackup request service This property specifies the port for the client to use when it sends requests to the
port (BPRD) NetBackup request service (bprd process) on the NetBackup server. The default is
13720.
Note: If you change this port number, remember that it must be the same for all
NetBackup servers and clients that communicate with one another.
 Configuring Host Properties 199
Network Settings properties

Table 3-46 Network dialog box properties (continued)

Property Description

Announce DHCP interval This property specifies how many minutes the client waits before it announces that a
different IP address is to be used. The announcement occurs only if the specified time
period has elapsed and the address has changed since the last time the client
announced it.

Network Settings properties

The Network Settings host properties apply to master servers, media servers, and
clients.

Figure 3-40 Network Settings dialog box

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

Reverse Host Name Lookup property

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

Table 3-47 Reverse Host Name Lookup property settings

Property Description

Allowed setting The Allowed property indicates that the host requires reverse host name lookup to
work to determine that the connection comes from a recognizable server.

By default, the host resolves the IP address of the connecting server to a host name
by performing a reverse lookup.

If the conversion of the IP address to host name fails, the connection fails.

Otherwise, it compares the host name to the list of known server host names. If the
comparison fails, the host rejects the server and the connection fails.

Restricted setting The Restricted property indicates that the NetBackup host first attempts to perform
reverse host name lookup. If the NetBackup host successfully resolves the IP address
of the connecting server to a host name (reverse lookup is successful), it compares
the host name to the list of known server host names.

If the resolution of the IP address to a host name fails (reverse lookup fails), based on
the Restricted setting, the host converts the host names of the known server list to IP
addresses (using a forward lookup). The host compares the IP address of the connecting
server to the list of known server IP addresses.

If the comparison fails, the host rejects the connection from server and the connection
fails.

Prohibited setting The Prohibited property indicates that the NetBackup host does not try reverse host
name lookup at all. The host resolves the host names of the known server list to IP
addresses using forward lookups.
The NetBackup host then compares the IP address of the connecting server to the list
of known server IP addresses.

If the comparison fails, the NetBackup host rejects the connection from the server and
the connection fails.
 Configuring Host Properties 201
Port Ranges properties

Reverse Host Name Lookup changes outside of the

Administration Console
In some cases, a master server may not be able to view the host properties of a
media server or client in the NetBackup Administration Console. The NetBackup
customer's DNS reverse host name lookup configuration may be one possible
reason why the Host Properties may not be visible.
In this case, since changing the NetBackup Reverse Host Name Lookup host
property requires being able to view the Host Properties, you’ll need to use another
method to change it.
Configure the REVERSE_NAME_LOOKUP option by using the nbgetconfig and
nbsetconfig commands. The nbsetconfig command configures the option on
Windows and UNIX master servers and clients.
See “Methods to set the NetBackup configuration options” on page 70.
The REVERSE_NAME_LOOKUP entry uses the following format:
REVERSE_NAME_LOOKUP = ALLOWED | RESTRICTED | PROHIBITED

For example:
REVERSE_NAME_LOOKUP = PROHIBITED

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

IP Address Family Support property

On the hosts that use both IPv4 and IPv6 addresses, use the IP Address Family
Support property to indicate which address family to use:
■ IPv4 only (Default)
■ Both IPv4 and IPv6
While the IP Address Family Support property controls how host names are
resolved to IP addresses, the Preferred Network properties control how NetBackup
uses the addresses.

Port Ranges properties

Use the Port Ranges properties in the NetBackup Administration Console to
determine how hosts connect to one another. These properties apply to selected
master servers, media servers, and clients.
 Configuring Host Properties 202
Port Ranges properties

Figure 3-41 Port Ranges dialog box

The Port Ranges dialog box contains the following properties.

Table 3-48 Port Ranges dialog box properties

Property Description

Use random port Specifies how the selected computer chooses a port when it communicates with
assignments NetBackup on other computers. Enable this property to let NetBackup randomly select
ports from those that are free in the allowed range. For example, if the range is from
1023 through 5000, it chooses randomly from the numbers in this range.

If this property is not enabled, NetBackup chooses numbers sequentially, not randomly.
NetBackup starts with the highest number that is available in the allowed range. For
example, if the range is from 1023 through 5000, NetBackup chooses 5000. If 5000 is
in use, port 4999 is chosen.

This property is enabled by default.

Client port window Lets the administrator define the range of non-reserved ports on the selected computer.
NetBackup can use any available port within this range as the source port when
communicating with NetBackup on another computer.
 Configuring Host Properties 203
Port Ranges properties

Table 3-48 Port Ranges dialog box properties (continued)

Property Description

Use OS selected non Lets the operating system determine which non-reserved port to use.
reserved port

Client reserved port This property is not used by NetBackup 7.0.1 and later unless one the following
window conditions is true:

■ The connect options for the remote host specify that the daemon port be used.
■ Attempts to connect to ports 1556 and 13274 on the remote host fail, which causes
the daemon port to be used.

If either condition is true, then this setting defines the range of reserved ports to use
as the source port for the connection.

Beginning with NetBackup 7.0.1, connections to other daemon ports use only the Client
port window, not the Client reserved port window.

Server port window This property specifies the range of non-reserved ports on which NetBackup processes
on this computer to accept connections from NetBackup on other computers when the
inbound connection is not to a well known port. This primarily applies to bpcd call-back
when vnetd is disabled in the connect options for the remote NetBackup server or
client and that host is configured for non-reserved ports.

This property also applies in the situation where a third-party protocol is used, such as
NDMP. It specifies the range of non-reserved ports on which this server accepts
NetBackup connections from other computers. The default range is 1024 through 5000.

Instead of indicating a range of ports, you can enable Use OS selected non reserved
port to let the operating system determine which non-reserved port to use.

This setting applies to the selected master or media server that connects to a server
or client that is configured to accept only non-reserved ports. The Accept connections
on non reserved ports property must be enabled in the Universal Settings dialog
box for hosts running NetBackup 7.0.1 and prior versions.

See “Universal Settings properties” on page 258.

Server reserved port This entry specifies the range of local reserved ports on which this computer accepts
window connections from NetBackup on other computers when the inbound connection is not
to a well known port. This primarily applies to bpcd call-back when vnetd is disabled
in the connect options for the remote NetBackup server or client.

Registered ports and dynamically-allocated ports

NetBackup communicates between computers by using a combination of registered
ports and dynamically-allocated ports.
 Configuring Host Properties 204
Preferred Network properties

Registered ports
These ports are registered with the Internet Assigned Numbers Authority (IANA)
and are permanently assigned to specific NetBackup services. For example, the
port for the NetBackup client daemon (bpcd) is 13782.
The following system configuration file can be used to override the default port
numbers for each service:
On Windows: %systemroot%\system32\drivers\etc\services
On UNIX: /etc/services

Note: Veritas recommends that the port numbers that are associated with PBX
(1556 and 1557) not be changed.

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

Preferred Network properties

Use the Preferred Network properties in the NetBackup Administration Console
to specify to NetBackup which networks or interfaces to use for outgoing NetBackup
traffic from the selected hosts. These properties apply to currently selected master
servers, media servers, and clients.
The Preferred Network properties are useful in NetBackup environments that
include multihomed hosts—the hosts that are connected to two or more networks,
or hosts that have two or more network addresses. The properties are especially
helpful to administrators who must configure an environment that includes both
Internet Protocol version 6 (IPv6) and IPv4 address families.
The Preferred Network properties compare to the Use specified network interface
property in the Universal Settings properties. However, the Use specified network
interface property can be used to specify only a single interface for NetBackup to
use for outbound calls. The Preferred Network properties were introduced so that
administrators can give more elaborate and constrictive instructions that apply to
multiple individual networks, or a range of networks. For example, an administrator
can configure a host to use any network except one.
 Configuring Host Properties 205
Preferred Network properties

Note: Do not inadvertently configure hosts so that they cannot communicate with
any other host. Use the bptestnetconn utility to determine whether the hosts can
communicate as you intend.
See “bptestnetconn utility to display Preferred Network information” on page 214.

Figure 3-42 Preferred Network dialog box

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

Table 3-49 Preferred Network dialog box properties

Property Description

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

Ordering arrows Select a network in the list, then click the up or down arrow to change the order of the
network in the list. The order can affect which network NetBackup selects.

See “Order of directive processing in the Preferred Network properties” on page 213.

Add Click Add to add a network to the Preferred Network properties. The directive for the
network is configured in the Add Preferred Network Settings dialog box.

See Table 3-50 on page 207.

Add to all The Add to all button is active when multiple servers are selected.

Change Select a network in the list, then click Change to change the Preferred Network properties.
The directive is changed in the Change Preferred Network Settings dialog box.

See “Add or Change Preferred Network Settings dialog box” on page 206.

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

Add or Change Preferred Network Settings dialog box

The Add Preferred Network Settings dialog box contains the following properties.
 Configuring Host Properties 207
Preferred Network properties

Table 3-50 Add or Change Preferred Network Settings dialog box properties

Property Description

Target Enter a network address or a host name:

■ If an address is specified as the network, it's usually considered a remote or target address.
NetBackup recognizes the following wildcard entries as addresses:
■ [Link]
Matches any IPv4 address.
■ 0::0
Matches any IPv6 address.
■ 0/0
Matches the address of any family.
■ If a host name is specified as the network, then the address that is used is the first returned
by the DNS resolver.

Note: Do not use the following malformed entries as wildcards: 0/32, 0/64, or 0/128. The left
side of the slash must be a legitimate IP address. However, 0/0 may be used, as listed.

Match The Match directive indicates that the specified network, address, or host name is preferred for
communication with the selected host.

The Match directive does not reject other networks, addresses, or host names from being selected,
even if they do not match. (The Only directive rejects unsuitable targets if they do not match.)

The Match directive is useful following a Prohibited or a Only directive. When used with other
directives, Match indicates to NetBackup to stop rule processing because a suitable match has
been found.

The Match directive can be used with the Source property to indicate source binding.

Prohibited Use the Prohibited directive to exclude or prevent the specified network, address, or host name
from being considered. In a list of DNS addresses, addresses in these networks are avoided.

Only The Only directive indicates that the specified network, address, or host name that is used for
communication with the selected host must be in the specified network.

Use the Only directive to prevent any network from being considered other than those specified
as Only.

This directive replaces the REQUIRED_NETWORK configuration option.

The Only directive can be used with the Source property to indicate source binding.
 Configuring Host Properties 208
Preferred Network properties

Table 3-50 Add or Change Preferred Network Settings dialog box properties
(continued)

Property Description

Source Use this property with the Match or the Only directives to describe the local host name, IP
addresses, or networks that may be used for source binding.

NetBackup matches the desired source interfaces, (backup networks, for example) with the target
addresses described by the Source property.

The corresponding configuration option for this property is PREFERRED_NETWORK. This property
replaces the REQUIRED_INTERFACE entry.

See “PREFERRED_NETWORK option for NetBackup servers” on page 321.

How NetBackup uses the directives to determine which network to

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

Figure 3-43 Multihomed servers example

Server_A

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

Backup interface
Production interface
[Link]
[Link]
[Link]

Backup interface
Server_B
[Link] Backup interface
[Link]
[Link]

Figure 3-44 shows a table for Server_B. Server_B has multiple network interfaces,
some of which have multiple IP addresses. In the table, yes indicates that NetBackup
can use the network-IP combination as a source. In this example, no directives
have been created for the host. Since no networks are listed in the Preferred
Network properties, any network-IP combinations can be used for communication.

Note: The following topic shows the bptestnetconn output for this example
configuration:
See Figure 3-51 on page 215.
 Configuring Host Properties 210
Preferred Network properties

Figure 3-44 From Server_A's perspective: Available IP addresses on

Server_B when no directives are indicated on Server_A

IP addresses
IPv4 IPv6
[Link] --- Yes
Network interfaces

[Link] Yes ---

[Link] --- Yes

[Link] --- Yes

[Link] --- Yes

[Link] Yes ---

Figure 3-45 shows a table for the same host (Server_B). Now, the Preferred
Network properties are configured so that all IPv4 addresses are excluded from
selection consideration by NetBackup. All NetBackup traffic is to use only IPv6
addresses.

Figure 3-45 From Server_A's perspective: Available IP addresses on

Server_B when directives to use IPv6 addresses only are
indicated on Server_A

IP addresses
IPv4 IPv6
[Link] --- Yes
Network interfaces

[Link] No ---

[Link] --- Yes

[Link] --- Yes

[Link] --- Yes

[Link] No ---

The following topics describe various configurations:

■ See “Configurations to use IPv6 networks” on page 211.
■ See “Configurations to use IPv4 networks” on page 212.
■ See “Configuration to prohibit using a specified address” on page 216.
 Configuring Host Properties 211
Preferred Network properties

■ See “Configuration that uses the same specification for both the network and
the interface—less constrictive” on page 216.
■ See “Configuration that uses the same specification for both the network and
the interface—more constrictive” on page 217.
■ See “Configuration that limits the addresses, but allows any interfaces”
on page 217.

Configurations to use IPv6 networks

The following Preferred Network configurations instruct NetBackup to use only
IPv6 addresses as targets in outbound calls for the currently selected hosts. The
configurations satisfy a topology where all backup traffic uses an IPv6 network and
other traffic uses other networks.
One configuration uses the Prohibited directive (Figure 3-46) and one configuration
uses the Match directive (Figure 3-47).
The more efficient method to specify one address family, (IPv6, in this case), is to
prohibit IPv4. The behavior of the Match directive is not as exclusive as Prohibited.
In this case, Match may not necessarily exclude other address families.
Figure 3-46 uses the Prohibited directive with a wildcard to indicate to NetBackup
to not consider using any IPv4 addresses. In this situation, NetBackup must use
an IPv6 address.

Note: The default configuration is for NetBackup to use only IPv4 addresses.
Creating a directive that prohibits all IPv4 addresses renders the server mute unless
you have IPv6 addresses and have them enabled.
See “IP Address Family Support property” on page 201.

Figure 3-46 Prohibit IPv4 addresses as targets

Figure 3-47 uses the Match directive with a wildcard to indicate to NetBackup to
consider only IPv6 addresses. In this case, NetBackup tries to use an IPv6 address,
but may consider IPv4 addresses if necessary.
 Configuring Host Properties 212
Preferred Network properties

Figure 3-47 Match IPv6 addresses as targets

Figure 3-48 shows another configuration that allows NetBackup to choose from
multiple IPv6 networks.
Given the multihomed example configuration, the directive indicates the following:
■ Four IPv6 networks, from [Link] to [Link], are described as
targets.
■ For all addresses in these networks, a source binding address that is derived
from the IP addresses of host name host_fred is used.
See “How NetBackup uses the directives to determine which network to use”
on page 208.

Figure 3-48 Indicating a range of IPv6 networks

Configurations to use IPv4 networks

The following Preferred Network configurations instruct NetBackup to use only
IPv4 addresses as targets in outbound calls for the currently selected hosts. The
configurations satisfy a topology where all backup traffic uses an IPv4 network and
other traffic uses other networks.
One configuration uses the Prohibited directive (Figure 3-49) and one configuration
uses the Match directive (Figure 3-50).
The more efficient method to specify one address family, (IPv4, in this case), is to
prohibit IPv6. The behavior of the Match directive is not as exclusive as Prohibited.
In this case, Match may not necessarily exclude other address families.
 Configuring Host Properties 213
Preferred Network properties

Figure 3-49 uses the Prohibited directive with a wildcard to indicate to NetBackup
to not consider using any IPv6 addresses. In this situation, NetBackup must use
an IPv4 address.

Figure 3-49 Prohibit IPv6 addresses as targets

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

Figure 3-50 Match IPv4 addresses as targets

Order of directive processing in the Preferred Network properties

NetBackup sorts all directives into decreasing order by subnet size so that the more
specific network specifications, such as complete host names or IP addresses,
match first. (For example, a /24 subnet matches before a /16 subnet.) In this way,
NetBackup can honor host-specific overrides.
If NetBackup considers the directives of multiple networks to be equal in specificity
(a tie), NetBackup looks at the order in which the networks are listed.
See “Order of directives can affect processing” on page 214.
NetBackup processes each resolved address in the network list according to specific
rules. Directives that contain addresses that do not apply to the host are ignored.
Table 3-51 describes how NetBackup determines whether an address can be used
for communication.
 Configuring Host Properties 214
Preferred Network properties

Table 3-51 Order of directive processing

Step NetBackup considers the target Target is selected or processing continues

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

NetBackup considers the next target.

2 ■ If the target is a match for the directive, and ...then the target is treated as Prohibited and
■ if the directive is a Prohibited directive... processing stops for that target.

NetBackup considers the next target.

3 If the target is not a match... ...then the processing continues.

NetBackup considers the next directive in the list.

4 If the target is a match... ...then the directive is either Only or Match and further
directive processing stops.

An Only match is treated like a Match in terms of

source binding computation. If no rules ever match,
then the target is allowed, and no source binding is
enforced.

Order of directives can affect processing

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

bptestnetconn utility to display Preferred Network information

The bptestnetconn utility is available to administrators to test and analyze host
connections. Use the preferred network option (--prefnet) to display information
about the preferred network configuration along with the forward lookup information
of a host on the server list.
The bptestnetconn command is described in the NetBackup Commands Reference
Guide.
Figure 3-51 shows the bptestnetconn output when run on Server_A, for Server_B.
That is, bptestnetconn is run from Server_A's perspective. Based on the directives
configured on Server_A, for Server_B, bptestnetconn shows the available IP
addresses on Server_B. In this example, no directives are configured on Server_A.
 Configuring Host Properties 215
Preferred Network properties

Figure 3-51 bptestnetconn for Server_B with no directives listed

[root@Server_A netbackup]# bptestnetconn -f --prefnet -H Server_B

---------------------------------------------------------------------
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms SRC: ANY
---------------------------------------------------------------------
Total elapsed time: 0 sec

Host for which lookup List of networks available to Any source is available to
is performed Server_B use for a connection

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

In the configuration file the directive appears as follows:

PREFERRED_NETWORK = [Link]/62 ONLY

This directive provides NetBackup with the information to filter the addresses and
choose to communicate with only those that match the :11c, :11d, :11e, and :11f
networks. The addresses that do not match the Only directive are prohibited, as
shown in the bptestnetconn output.
See “PREFERRED_NETWORK option for NetBackup servers” on page 321.
Figure 3-52 shows the bptestnetconn output for Server_B, given this directive.
 Configuring Host Properties 216
Preferred Network properties

Figure 3-52 bptestnetconn for Server_B with directive

[root@Server_A netbackup]# bptestnetconn -f --prefnet -H Server_B

---------------------------------------------------------------------
FL: Server_B -> [Link] : 11 ms TGT PROHIBITED
FL: Server_B -> [Link] : 11 ms TGT PROHIBITED
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms SRC: ANY
FL: Server_B -> [Link] : 11 ms TGT PROHIBITED
FL: Server_B -> [Link] : 11 ms SRC: ANY
---------------------------------------------------------------------
Total elapsed time: 0 sec

List of networks available to Directives make some targets

Server_B unavailable to Server_B

Configuration to prohibit using a specified address

Figure 3-53 shows a configuration that prohibits NetBackup from using the specified
address.

Figure 3-53 Prohibited target example

Configuration that uses the same specification for both the network
and the interface—less constrictive
Figure 3-54 shows a configuration that uses the same specification for both the
network and the interface.
For all target addresses in the specified network, a source binding in the same
network is selected. This directive is considered generic since the identical directive
applies to all NetBackup hosts on the network. The closest preferred source address
that matches a remote address is used for source binding.
A production network outside this range can then be Prohibited, thereby preferring
these addresses from both a remote and source binding perspective. Additional
Match directives may be used to indicate additional backup networks that are
allowed.
 Configuring Host Properties 217
Preferred Network properties

Figure 3-54 Match network selection with the source

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

Figure 3-55 Only network selection with the same source binding address

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

Configuration that limits the addresses, but allows any interfaces

Figure 3-56 shows a configuration that allows only the addresses that start with the
specified prefix to be considered. No source binding is specified, so any interface
may be used.
 Configuring Host Properties 218
Resilient Network properties

Figure 3-56 Limiting the addresses, without any source binding

Resilient Network properties

The Resilient Network properties appear for the master server, for media servers,
and for clients. For media servers and clients, the Resilient Network properties
are read only. When a job runs, the master server updates the media server and
the client with the current properties.
The Resilient Network properties let you configure NetBackup to use resilient
network connections for backups and restores. A resilient connection allows backup
and restore traffic between a client and a NetBackup media server to function
effectively in high-latency, low-bandwidth networks such as WANs. The data travels
across a wide area network (WAN) to media servers in a central datacenter.
NetBackup monitors the socket connections between the remote client and the
NetBackup media server. If possible, NetBackup re-establishes dropped connections
and resynchronizes the data stream. NetBackup also overcomes latency issues to
maintain an unbroken data stream. A resilient connection can survive network
interruptions of up to 80 seconds. A resilient connection may survive interruptions
longer than 80 seconds.
The NetBackup Remote Network Transport Service manages the connection
between the computers. The Remote Network Transport Service runs on the master
server, the client, and the media server that processes the backup or restore job.
If the connection is interrupted or fails, the services attempt to re-establish a
connection and synchronize the data.
NetBackup protects only the network socket connections that the NetBackup Remote
Network Transport Service (nbrntd) creates. Examples of the connections that are
not supported are:
■ Clients that back up their own data (deduplication clients and SAN clients)
■ Granular Recovery Technology (GRT) for Exchange Server or SharePoint Server
■ NetBackup nbfsd process.
 Configuring Host Properties 219
Resilient Network properties

NetBackup protects connections only after they are established. If NetBackup cannot
create a connection because of network problems, there is nothing to protect.
Resilient connections apply between clients and NetBackup media servers, which
includes master servers when they function as media servers. Resilient connections
do not apply to master servers or media servers if they function as clients and back
up data to a media server.
Resilient connections can apply to all of the clients or to a subset of clients.

Note: If a client is in a different subdomain than the server, add the fully qualified
domain name of the server to the client’s hosts file. For example,
[Link] is a different subdomain than [Link].

When a backup or restore job for a client starts, NetBackup searches the Resilient
Network list from top to bottom looking for the client. If NetBackup finds the client,
NetBackup updates the resilient network setting of the client and the media server
that runs the job. NetBackup then uses a resilient connection.

Figure 3-57 Master server Resilient Network host properties

 Configuring Host Properties 220
Resilient Network properties

See “About the Daemons tab” on page 1045.

Table 3-52 describes the Resilient Network properties.

Table 3-52 Resilient Network dialog box properties

Property Description

Host Name or IP Address The Host Name or IP Address of the host. The address can
also be a range of IP addresses so you can configure more
than one client at once. You can mix IPv4 addresses and
ranges with IPv6 addresses and subnets.

If you specify the host by name, Veritas recommends that

you use the fully qualified domain name.

Use the arrow buttons on the right side of the pane to move
up or move down an item in the list of resilient networks.

Resiliency Resiliency is either ON or OFF.

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

The resilient status of each client also appears as follows:

■ In the NetBackup Administration Console, select NetBackup Management
> Policies in the left pane and then select a policy. In the right pane, a
Resiliency column shows the status for each client in the policy.
■ In the NetBackup Administration Console, select NetBackup Management
> Host Properties > Clients in the left pane. In the right pane, a Resiliency
column shows the status for each client.
Other NetBackup properties control the order in which NetBackup uses network
addresses.
See “Preferred Network properties” on page 204.
The NetBackup resilient connections use the SOCKS protocol version 5.
Resilient connection traffic is not encrypted. Veritas recommends that you encrypt
your backups. For deduplication backups, use the deduplication-based encryption.
For other backups, use policy-based encryption.
 Configuring Host Properties 221
Resilient Network properties

Resilient connections apply to backup connections. Therefore, no additional network

ports or firewall ports must be opened.

Note: If multiple backup streams run concurrently, the Remote Network Transport
Service writes a large amount of information to the log files. In such a scenario,
Veritas recommends that you set the logging level for the Remote Network Transport
Service to 2 or less. Instructions to configure unified logs are in a different guide.
See the NetBackup Logging Reference Guide.

Resilient connection resource usage

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

Specifying resilient connections

Use the following procedure to specify resilient connections for NetBackup clients.
See “Resilient Network properties” on page 218.
Alternatively, you can use the resilient_clients script to specify resilient
connections for clients:
■ Windows:
install_path\Veritas\NetBackup\bin\admincmd\resilient_clients

■ UNIX: /usr/openv/netbackup/bin/admincmd/resilient_clients
To specify resilient connections
1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Master Servers in the left pane.
2 In the right pane, select the master server on which to specify properties.
 Configuring Host Properties 222
Resilient Network properties

3 On the Actions menu, click Properties.

4 In the properties dialog box left pane, select Resilient Network.
5 In the Resilient Network dialog box, use the following buttons to manage
resiliency for clients:

Add To add resilient settings

1 Click Add.

The Add Resilient Network Settings dialog box appears

2 Enter a client host name, an IP address, or an address range.

If you specify the client host by name, Veritas recommends that

you use the fully qualified domain name.

For address ranges, use Classless Inter-Domain Routing (CIDR)

notation (for example, [Link]/24 or fd00::/8).

3 Ensure that the Resiliency On option is selected.

4 Click Add.

5 Repeat until you have finished entering clients or address ranges.

6 When you finish adding network settings, click Close.

Add To All If you select multiple hosts in the NetBackup Administration Console,
the entries in the Resilient Network list may appear in different colors,
as follows:

■ The entries that appear in black type are configured on all of the
hosts.
■ The entries that appear in gray type are configured on some of the
hosts only.

For the entries that are configured on some of the hosts only, you can
add them to all of the hosts. To do so, select them and click Add To All.

Change To change resilient settings

1 Select the client host name, the IP address, or the address range.

2 Click Change.

The Change Resilient Network Settings dialog box appears

3 Select the desired Resiliency setting.

4 Click OK.
 Configuring Host Properties 223
Resource Limit properties

Remove Remove the select host or address rang

1 Select the client host name, the IP address, or the address range.

2 Click Remove.

The client is removed immediately; a confirmation dialog box does

not appear.

Move an item in the list of items

1 Select the client host name, the IP address, or the address range.

2 Click the appropriate button to move up the item or move down the
item.

The order of the items in the list is significant.

See “Resilient Network properties” on page 218.

6 After specifying resilient connections, click OK.

The settings are propagated to the affected hosts through normal NetBackup
inter-host communication, which can take up to 15 minutes.
7 If you want to begin a backup immediately, restart the NetBackup services on
the master server.

Resource Limit properties

The Resource Limit properties in the NetBackup Administration Console control
the number of simultaneous backups that can be performed on a VMware or Hyper-V
resource type. These settings apply to all policies for the currently selected master
server.
For example, a VMware Resource Limit of four for Datastore means that NetBackup
policies can perform no more than four simultaneous backups on any particular
datastore.

Note: The Resource Limit properties apply only to policies that use automatic
selection of virtual machines (the policy's Query Builder). If you select virtual
machines manually on the Browse for Virtual Machines dialog box, the Resource
Limit properties have no effect.

The Resource Limit dialog box contains the following properties, depending on
which application is selected.
For more information about the specific resource types, click Help.
 Configuring Host Properties 224
Resource Limit properties

Figure 3-58 Resource Limit dialog box with VMware application selected
 Configuring Host Properties 225
Restore Failover properties

Figure 3-59 Resource Limit dialog box with Hyper-V application selected

Restore Failover properties

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

Figure 3-60 Restore Failover dialog box

The Restore Failover dialog box contains the following properties:

Table 3-53
Property Description

Media server Displays the NetBackup media servers that have failover protection for
restores.

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

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

■ Two or more media servers share a robot and each has connected drives. When
a restore is requested, one of the servers is temporarily inaccessible.
■ Two or more media servers have stand alone drives of the same type. When a
restore is requested, one of the servers is temporarily inaccessible.
In these instances, inaccessible means that the connection between bprd on the
master server and bptm on the media server (through bpcd) fails.
Possible reasons for the failure are as follows:
■ The media server is down.
■ The media server is up but bpcd does not respond. (For example, if the
connection is refused or access is denied.)
■ The media server is up and bpcd is running, but bptm has problems. (For
example, bptm cannot find the required tape.)

Assigning an alternate media server as a failover restore server

You can assign another media server to act as a failover restore server for your
media server. If your media server is unavailable during a restore, the failover
restore server takes its place.
To assign an alternate media server as a failover restore server
1 In the NetBackup Administration Console, in the left panel, expand
NetBackup Management > Host Properties > Master Servers.
2 In the right pane, double-click on the master server you want to modify.
3 In the properties dialog box, in the left pane, click Restore Failover.
4 Click Add.
5 In the Media server field, specify the media server for failover protection.
6 In the Failover restore servers field, specify the media servers to try if the
server that is designated in the Media server field is unavailable. Separate
the names of multiple servers with a single space.
7 Click Add. The dialog box remains open for another entry.
8 Click Close.
9 From the Restore Failover dialog box, click Apply to accept the changes.
Before the change takes effect, you must stop and restart the NetBackup Request
daemon on the master server where the configuration was changed.
See “About enabling automatic failover to an alternate server” on page 1157.
 Configuring Host Properties 228
Retention Periods properties

Retention Periods properties

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

Figure 3-61 Retention Periods dialog box

By default, NetBackup stores each backup on a volume that already contains

backups at the same retention level. However, NetBackup does not check the
retention period that is defined for that level. When the retention period for a level
is redefined, some backups that share the same volume may have different retention
periods.
For example, if the retention level 3 is changed from one month to six months,
NetBackup stores future level 3 backups on the same volumes. That is, the backups
are placed on the volumes with the level 3 backups that have a retention period of
one month.
 Configuring Host Properties 229
Retention Periods properties

No problem exists if the new and the old retention periods are of similar values.
However, before a major change is made to a retention period, suspend the volumes
that were previously used for that retention level.
See “Determining retention periods for volumes” on page 230.
See “Suspending or unsuspending volumes” on page 519.
The Retention Periods dialog box contains the following properties.

Table 3-54 Retention Periods dialog box properties

Property Description

Value Assigns a number to the retention level setting.

Units Specifies the units of time for the retention period. The list includes hours as the smallest
unit of granularity and the special units, Infinite, and Expires immediately.

Retention Level The retention level number (0 through 24).

Retention Period A list of the current definitions for the 25 possible levels of retention. By default, levels
9 through 24 are set to infinite. Retention level 9 is the only level that cannot be changed
and remains at infinite.

See “Retention Periods with end dates beyond 2038, excluding Infinity” on page 231.

With the default, there is no difference between a retention level of 12 and a retention
level of 20, for example.

The Schedule Count column indicates how many schedules currently use each level.
If the retention period is changed for a level, it affects all schedules that use that level.
The Changes Pending column uses an asterisk (*) to indicate that the period has
been changed and not applied. NetBackup does not change the actual configuration
until the administrator accepts or applies the changes.

Schedule Count Lists the number of schedules that use the currently selected retention level.

Schedules using this Displays a list of the current policy names and schedule names that use the retention
retention level level.

Impact Report Displays a summary of how changes affect existing schedules. The list displays all
schedules in which the retention period is shorter than the frequency period.

Changing a retention period

Use the following procedure to change a retention period.
 Configuring Host Properties 230
Retention Periods properties

To change a retention period

1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Host Properties > Master Servers.
2 In the right pane, double-click on the master server you want to modify.
3 In the properties dialog box, in the left pane, click Retention Periods.
4 Select the retention level to change.
By default, levels 9 through 24 are set to infinite. If the levels are left at the
default, there is no difference between a retention level of 12 and a retention
level of 20. Level 9 cannot be changed and remains at a setting of infinite.
See “Retention Periods with end dates beyond 2038, excluding Infinity”
on page 231.
The dialog box displays the names of all schedules that use the selected
retention level as well as the policy to which each schedule belongs.
5 Type the new retention period in the Value box.
6 From the Units drop-down list, select a unit of measure (days, weeks, months,
years, Infinite, or Expires immediately).
After you change the value or unit of measure, an asterisk (*) appears in the
Changes Pending column to indicate that the period was changed. NetBackup
does not change the actual configuration until the administrator accepts or
applies the changes.
7 Click Impact Report.
The policy impact list displays the policies and the schedule names where the
new retention period is less than the frequency period. To prevent a potential
gap in backup coverage, redefine the retention period for the schedules or
change the retention or frequency for the schedule.
8 Do one of the following:
■ To discard your changes, click Cancel.
■ To save your changes and leave the dialog box open to make further
changes, click Apply.
■ To save your changes and close the dialog box, click OK.

Determining retention periods for volumes

Use the following procedure to determine retention periods for volumes.
 Configuring Host Properties 231
Scalable Storage properties

To determine retention periods for volumes

1 In the NetBackup Administration Console, in the left pane, expand Media
and Device Management > Media
2 In the right pane, find the volume on the list and examine the value in the
Retention Period column.
To see all volumes that have the same retention period, click the Retention Period
column header to sort the volumes by retention period. This column heading is
hidden by default.

Retention Periods with end dates beyond 2038, excluding Infinity

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

Scalable Storage properties

The Scalable Storage Cloud Settings properties contain information about
encryption, metering, bandwidth throttling, and network connections between the
NetBackup hosts and your cloud storage provider.
The Scalable Storage properties appear only if you install a NetBackup Data
Protection Optimization Option license key.
The Scalable Storage properties apply to currently selected media servers.
 Configuring Host Properties 232
Scalable Storage properties

Figure 3-62 Scalable Storage Cloud Settings host properties

Table 3-55 describes the properties.

Table 3-55 Cloud storage host properties

Property Description

Key Management Server If you configured the NetBackup Key Management Service (KMS), the name of the
(KMS) Name KMS server.

Metering Interval Determines how often NetBackup gathers connection information for reporting purposes.
NetBackup OpsCenter uses the information that is collected to create reports. The
value is set in seconds. The default setting is 300 seconds (5 minutes). If you set this
value to zero, metering is disabled.

Total Available Bandwidth Use this value to specify the speed of your connection to the cloud. The value is
specified in kilobytes per second. The default value is 102400 KB/sec.

Sampling interval The time, in seconds, between measurements of bandwidth usage. The larger this
value, the less often NetBackup checks to determine the bandwidth in use.
 Configuring Host Properties 233
Scalable Storage properties

Table 3-55 Cloud storage host properties (continued)

Property Description

Advanced Settings Click Advanced Settings to specify additional settings for throttling.

See “Configuring advanced bandwidth throttling settings” on page 233.

See “Advanced bandwidth throttling settings” on page 234.

Maximum conncurrent jobs The default maximum number of concurrent jobs that the media server can run for the
cloud storage server.

This value applies to the media server not to the cloud storage server. If you have more
than one media server that can connect to the cloud storage server, each media server
can have a different value. Therefore, to determine the total number of connections to
the cloud storage server, add the values from each media server.

If you configure NetBackup to allow more jobs than the number of connections,
NetBackup fails any jobs that start after the number of maximum connections is reached.
Jobs include both backup and restore jobs.

You can configure job limits per backup policy and per storage unit.

See “Limit jobs per policy (policy attribute)” on page 706.

See “Maximum concurrent jobs storage unit setting” on page 578.

Note: NetBackup must account for many factors when it starts jobs: the number of
concurrent jobs, the number of connections per media server, the number of media
servers, and the job load-balancing logic. Therefore, NetBackup may not fail jobs
exactly at the maximum number of connections. NetBackup may fail a job when the
connection number is slightly less than the maximum, exactly the maximum, or slightly
more than the maximum.

In practice, you should not need to set this value higher than 100.

For more information about NetBackup cloud storage, see the NetBackup Cloud
Administrator's Guide:
[Link]

Configuring advanced bandwidth throttling settings

Advanced bandwidth throttling settings let you control various aspects of the
connection between the NetBackup hosts and your cloud storage provider.
The total bandwidth and the bandwidth sampling interval are configured on the
Cloud Settings tab of the Scalable Storage host properties screen.
See “Scalable Storage properties” on page 231.
 Configuring Host Properties 234
Scalable Storage properties

To configure advanced bandwidth throttling settings

1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Media Servers in the left pane.
2 In the right pane, select the host on which to specify properties.
3 Click Actions > Properties.
4 In the properties dialog box left pane, select Scalable Storage.
5 In the right pane, click Advanced Settings. The Advanced Throttling
Configuration dialog box appears.
The following is an example of the dialog box:

6 Configure the settings and then click OK.

See “Advanced bandwidth throttling settings” on page 234.

Advanced bandwidth throttling settings

The following table describes the advanced bandwidth throttling settings.
 Configuring Host Properties 235
Scalable Storage properties

Table 3-56 Advanced Throttling Configuration settings

Property Description

Read Bandwidth Use this field to specify the percentage of total bandwidth that read
operations can use. Specify a value between 0 and 100. If you
enter an incorrect value, an error is generated.

If there is insufficient bandwidth to transmit the specified amount

of data within a few minutes, restore or replication failures may
occur due to timeouts.

Consider the total load of simultaneous jobs on multiple media

servers when you calculate the required bandwidth.

Default value: 100

Possible values: 0 to 100

Write Bandwidth Use this field to specify the percentage of total bandwidth that write
operations can use. Specify a value between 0 and 100. If you
enter an incorrect value, an error is generated.

If there is insufficient bandwidth to transmit the specified amount

of data within a few minutes, backup failures may occur due to
timeouts.

Consider the total load of simultaneous jobs on multiple media

servers when you calculate the required bandwidth.

Default value: 100

Possible values: 0 to 100

Work time Use this field to specify the time interval that is considered work
time for the cloud connection.

Specify a start time and end time in 24-hour format. For example,
2:00 P.M. is 14:00.

Indicate how much bandwidth the cloud connection can use in the
Allocated bandwidth field. This value determines how much of
the available bandwidth is used for cloud operations in this time
window. The value is expressed as a percentage or in kilobytes
per second.
 Configuring Host Properties 236
Servers properties

Table 3-56 Advanced Throttling Configuration settings (continued)

Property Description

Off time Use this field to specify the time interval that is considered off time
for the cloud connection.

Specify a start time and end time in 24-hour format. For example,
2:00 P.M. is 14:00.

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

Weekend Specify the start and stop time for the weekend.

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

Read Bandwidth This field displays how much of the available bandwidth the cloud
(KB/s) storage server transmits to a NetBackup media server during each
restore job. The value is expressed in kilobytes per second.

Write Bandwidth This field displays how much of the available bandwidth the
(KB/s) NetBackup media server transmits to the cloud storage server
during backup jobs. The value is expressed in kilobytes per second.

Servers properties
The Servers properties display the NetBackup server lists on selected master
servers, media servers, and clients. The server lists display the NetBackup servers
that each host recognizes.
The Master Server field contains the name of the master server for the selected
host. (The name of the selected host appears in the title bar.)
The Servers dialog box contains the following tabs:
 Configuring Host Properties 237
Servers properties

Table 3-57 Servers dialog box properties

Tab Description

Additional Servers tab This tab (Figure 3-63) lists the additional servers that can access the server that is
specified as Master server.

During installation, NetBackup sets the master server to the name of the system where
the server software is installed. NetBackup uses the master server value to validate
server access to the client. The master server value is also used to determine which
server the client must connect to so that files can be listed and restored.

To configure access to a remote server, add to the server list the name of the host seeking
access.
Note: For a Fibre Transport (FT) media server that has multiple network interfaces for
VLANs: Ensure that the FT server’s primary host name appears before any other interface
names for that FT media server host.

See “Accessing remote servers” on page 1124.

Media Servers tab This tab lists the hosts that are media servers only. Hosts that are listed as media servers
can back up and restore clients, but have limited administrative privileges.

If a server appears only on the Media servers tab, the server is a media server. Media
servers can back up and restore clients, but they have limited administrative privileges.

A server that appears on the Media servers tab and the Additional servers tab may
introduce unintended consequences. A computer that is defined as both a master server
and a media server gives the administrator of the media server full master server
privileges. By listing the media server in both places, you may inadvertently give the
media server administrator more privileges than intended.

OpsCenter Servers tab This tab lists the Veritas NetBackup OpsCenter servers that can access the currently
selected master server.

To add a server to the list, ensure that the NetBackup server can reach the OpsCenter
server.

For more information, see the Veritas NetBackup OpsCenter Administrator's Guide.
 Configuring Host Properties 238
Servers properties

Table 3-57 Servers dialog box properties (continued)

Tab Description

Trusted Master Servers Use this tab to add the remote master servers that you trust and to view the master
tab servers that are already trusted.

See “About trusted master servers for Auto Image Replication” on page 1005.

See “Adding a trusted master server” on page 242.

Note: If either the source or remote master server is clustered, you must enable
inter-node communication on all of the nodes in the cluster. Do so before you add the
trusted master server.

See “Enabling NetBackup clustered master server inter-node authentication” on page 240.

You cannot remove a trusted master server when an Import SLP is configured in that
master server's domain.

Information about Auto Image Replication and storage lifecycle policies is available.

See “About NetBackup Auto Image Replication” on page 992.

See “About storage lifecycle policies” on page 613.

If you use NetBackup Access Control, read about access control with Auto Image
Replication.

See “Using NetBackup Access Control (NBAC) with Auto Image Replication” on page 1011.
 Configuring Host Properties 239
Servers properties

Figure 3-63 Additional servers tab in the Servers dialog box

Adding a server to a servers list

Depending on the tab that is selected, you can add a master server, media server,
client, or OpsCenter server to the server list in the Additional servers tab, the
Media servers tab, or the OpsCenter servers tab. All tabs appear in the Servers
properties dialog box.
To add a server to a list
1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Host Properties.
2 Depending on the host to be configured, select Master Servers, Media
Servers, or Clients.
3 In the right pane, double-click the master server, media server, or client that
you want to modify.
4 In the properties dialog box, in the left pane, click Servers.
5 Select the tab that contains the server list that you want to modify.
 Configuring Host Properties 240
Servers properties

6 Click Add.
To add multiple hosts, select more than one media server or client in step 2
and click Apply To All in step 5. However, you can add only one master server
to the list at a time.
7 In the Add a New Server Entry dialog box, type the name of the new server.
8 Click Add. The dialog box remains open for another entry.
9 Click Close.

Note: If you add a media server, run nbemmcmd -addhost to add the media server
to the Enterprise Media Manager (EMM) in the NetBackup database of the master
server.

Removing a server from a server list

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

Enabling NetBackup clustered master server inter-node

authentication
NetBackup requires inter-node authentication among the master servers in a cluster.
For authentication, you must provision an authentication certificate on all of the
nodes of the cluster. The certificates are used to establish SSL connections between
the NetBackup hosts. The inter-node authentication allows the following NetBackup
functionality:
 Configuring Host Properties 241
Servers properties

NetBackup Administration The NetBackup Administration Console in master server

Console clusters requires the NetBackup authentication certificates
for correct functionality.

Targeted A.I.R. (Auto Image Auto Image Replication in which a master server is in a cluster
Replication) requires inter-node authentication among the hosts in that
cluster. The NetBackup authentication certificates provide
the means to establish the proper trust relationships.

Provision the certificates on the cluster hosts before you add

the trusted master server. This requirement applies regardless
of whether the clustered mastered server is the source of the
replication operation or the target.

See “About trusted master servers for Auto Image

Replication” on page 1005.

See “Adding a trusted master server” on page 242.

To enable clustered master server inter-node authentication
◆ On the active node of the NetBackup master server cluster, run the following
NetBackup command:
■ Windows: install_path\Veritas\NetBackup\bin\admincmd\bpnbaz
-setupat

■ UNIX: /usr/openv/netbackup/bin/admincmd/bpnbaz -setupat

NetBackup creates the certificates on every node in the master server cluster.
The following is example output:

# bpnbaz -setupat
You will have to restart NetBackup services on this machine after
the command completes successfully.
Do you want to continue(y/n)y
Gathering configuration information.
Please be patient as we wait for 10 sec for the security services
to start their operation.
Generating identity for host '[Link]'
Setting up security on target host: [Link]
nbatd is successfully configured on NetBackup Master Server.
Operation completed successfully.
 Configuring Host Properties 242
Servers properties

Adding a trusted master server

You can configure a trust relationship between multiple NetBackup domains. To
do so, in a source domain you specify the remote master servers with which you
want to add a trust relationship. Use the following procedure in the source domain
to add a remote master server as a trusted master server.
A trust relationship between domains helps with replication operations.
See “About trusted master servers for Auto Image Replication” on page 1005.

Note: If either the source or remote master server is clustered, you must enable
inter-node communication on all of the nodes in the cluster. Do so before you add
the trusted master server.
See “Enabling NetBackup clustered master server inter-node authentication”
on page 240.

To add a trusted master server

1 In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Master Servers in the left pane.
2 In the right pane, select the master server.
3 On the Actions menu, click Properties.
4 In the properties dialog box left pane, select Servers.
5 In the Servers dialog box, select the Trusted Master Servers tab.
 Configuring Host Properties 243
Servers properties

6 On the Trusted Master Servers tab, click Add.

The Add a New Trusted Master Server dialog box appears.
The following is an example of the dialog box:

7 In the Add a New Trusted Master Server dialog box, enter the following and
then click OK:
■ The fully-qualified host name of the remote master server.
■ The logon account User name of the remote master server host.
■ The Password for the logon account of the remote master server host.

8 Repeat step 6 and step 7 for each master server with which you want to add
a trust relationship.
9 When you finish adding trusted master servers, click OK.

Removing a trusted master server

You can remove a remote master server with which you have configured a trust
relationship.
A trust relationship between domains helps with replication operations.
See “About trusted master servers for Auto Image Replication” on page 1005.
Two procedures exist, as follows:
 Configuring Host Properties 244
Servers properties

The remote master If the remote master server is online and active, use the NetBackup
server is online Administration Console to remove the trusted master server. This
method also removes the reciprocal trust relationship.

See “To remove a trusted master server for inter-domain operations”

on page 244.

The remote master If the remote master server is offline, use the NetBackup nbseccmd
server is offline command to remove the trusted master server. This method does
not remove the reciprocal trust relationship.

See “To remove a trusted master server that is offline” on page 245.

To remove a trusted master server for inter-domain operations

1 Ensure that all replication jobs to the trusted master are complete. You can
use nbstlutil stlilist to list the state of all storage lifecycle policy-managed
operations. To cancel jobs use nbstlutil cancel.
See the NetBackup Commands Reference Guide for information about the
nbstlutil command.

2 Delete all storage lifecycle policies (SLPs) that use the trusted master as a
destination.

Note: Before deleting a storage lifecycle policy, ensure that there are no backup
policies that indicate the SLP for the Policy storage.

3 In the NetBackup Administration Console, expand NetBackup Management

> Host Properties > Master Servers in the left pane.
4 In the right pane, select the master server.
5 On the Actions menu, click Properties.
6 In the properties dialog box left pane, select Servers.
7 In the Servers dialog box, select the Trusted Master Servers tab.
 Configuring Host Properties 245
Servers properties

8 On the Trusted Master Servers tab, select the trusted master server that you
want to remove and click Remove.
The Remove Trusted Master Server dialog box appears.
The following is an example of the dialog box:

In the Remove Trusted Master Server dialog box, enter the credentials for
that master server host and then click Remove.
9 Repeat step 8 for each master server from which you want to remove a trust
relationship.
10 When you finish removing trusted master servers, click OK.
To remove a trusted master server that is offline
◆ On the source master server, enter the following NetBackup nbseccmd
command:
UNIX: /usr/openv/netbackup/bin/admincmd/nbseccmd
-setuptrustedmaster -remove -masterserver master_server_name
-remotemasterserver remote_master -localonly

Windows: install_path\NetBackup\bin\admincmd\nbseccmd
-setuptrustedmaster -remove -masterserver master_server_name
-remotemasterserver remote_master -localonly
 Configuring Host Properties 246
SharePoint properties

Changing the master server that performs backups and restores for
a client
Use the Make Master option to change the master server that performs backups
and restores for a client. This option does not change a host into a master server.
This option is useful in a disaster recovery situation or in a NetBackup environment
where Auto Image Replication is configured. For example, select a client in the
source domain, then use Make Master to temporarily point the client to the master
server of the target domain. After changing the master server, restores from the
target domain can be initiated.
To change the master server that a client uses for backups and restores
1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Host Properties.
2 Depending on the host to be configured, select Master Servers, Media
Servers, or Clients.
3 In the details pane, double-click the master server, media server, or client you
want to modify.
4 In the dialog box, click Servers.
5 From the Additional servers list, select a server.
6 Click Make Master.
In the configuration file, the new master server appears as the first server entry
in the list.
Changing the master server does not prevent the former master server from
initiating backups for the client. As long as that server continues to be listed
on the client’s server list, the master server can perform backups.

SharePoint properties
The SharePoint properties apply to currently selected Windows clients to protect
SharePoint Server installations.
 Configuring Host Properties 247
SharePoint properties

Figure 3-64 SharePoint dialog box

The SharePoint dialog box contains the following properties.

Table 3-58 SharePoint dialog box properties

Property Description

Domain\User name Specifies the domain and the user name for the account you
want to use to log on to SharePoint (DOMAIN\user name).

Password Specifies the password for the account.

Consistency check before Specifies the consistency checks to perform on the SQL
backup Server databases before NetBackup begins a backup
operation. These checks are performed for both
server-directed and user-directed backups.

If you choose to perform a consistency check, you can select

Continue with backup if consistency check fails.
NetBackup then continues to perform the backup if the
consistency check fails.
 Configuring Host Properties 248
SLP Parameters properties

Table 3-58 SharePoint dialog box properties (continued)

Property Description

SharePoint granular restore For VMware backups that protect Federated SharePoint
proxy host configurations, provide the name of the back-end SQL server.
This server acts as the granular restore proxy host for the
catalog hosts (front-end servers in the farm).

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

Consistency check options for SharePoint Server

The following consistency checks can be performed before a SharePoint Server
backup.

Table 3-59 Consistency check options

Option Description

None Do not perform consistency checking.

Full check, excluding Select this option to exclude indexes from the consistency check. If indexes are not
indexes checked, the consistency check runs significantly faster but is not as thorough. Only
the data pages and clustered index pages for each user table are included in the
consistency check. The consistency of the non-clustered index pages is not checked.

Full check, including Include indexes in the consistency check. Any errors are logged.
indexes

SLP Parameters properties

The SLP Parameters properties in the NetBackup Administration Console allow
administrators to customize how storage lifecycle policies are maintained and how
SLP jobs run. These properties apply to the SLPs of the currently selected master
servers.
 Configuring Host Properties 249
SLP Parameters properties

Figure 3-65 SLP Parameters dialog box

In NetBackup 7.6 and earlier, the parameters that appear in the SLP Parameters
were configured in the LIFECYCLE_PARAMETERS configuration file. The host
properties replace that file. An upgrade to 7.6 migrates the settings in the
LIFECYCLE_PARAMETERS file to the SLP Parameters.
To change the parameters, either change them in the host properties or use the
command line. If either method is used to change a storage lifecycle policy parameter
default, the change creates the [Link] configuration file.
The [Link] file is found in the following locations, but is not present if the default
of any parameter has not been changed.
■ On Windows:
install_path\veritas\NetBackup\var\global\[Link]

■ On UNIX:
/usr/openv/var/global/[Link]

To use the command-line method, use the nbgetconfig and the nbsetconfig
commands to change the defaults. For information about these commands, see
the NetBackup Commands Reference Guide.
 Configuring Host Properties 250
SLP Parameters properties

Table 3-60 describes the SLP Parameters and the default of each. It also lists the
configuration options and the syntax to use with the command-line method.
Use the drop-down menu in the Units column to change the units of measurement
for size or time.

Table 3-60 SLP Parameters

Property Description

Minimum size per The smallest batch size that can run as a single duplication job. The job does not run
duplication job until enough images accumulate to reach this minimum batch size or until the Force
interval for small jobs time is reached. Minimum: 1 kilobyte; no maximum size. Default:
8 gigabytes.

Configuration option default: SLP.MIN_SIZE_PER_DUPLICATION_JOB = 8 GB

Maximum size per The largest batch size that can run as a single duplication job. Minimum: 1 kilobyte;
duplication job no maximum size. Default: 100 gigabytes.

Configuration entry default: SLP.MAX_SIZE_PER_DUPLICATION_JOB = 100 GB

Maximum size per A.I.R. The largest batch size that can run as a single job for Auto Image Replication. Minimum:
replication job 1 kilobyte; no maximum size. Default: 100 gigabytes.

Configuration entry default: SLP.MAX_SIZE_PER_BACKUP_REPLICATION_JOB =

100 GB

Maximum images per The largest number of images in a single batch that can run as a single job. Default:
snapshot replication job 50 images, with no minimum number or maximum number.

Use this parameter with the Limit I/O streams disk pool option which limits the number
of jobs that can run concurrently to each volume in the disk pool.

Configuration entry default: SLP.MAX_IMAGES_PER_SNAPSHOT_REPLICATION_JOB

= 50

Minimum images per A.I.R. The fewest number of images in a single batch that can run as an Auto Image
Import job Replication import job. The job does not run until either the minimum size is reached
or the Force interval for small jobs time is reached. Minimum: 1 image; no maximum
number of images. Default: 1 image.

Configuration entry default: SLP.MIN_IMAGES_PER_IMPORT_JOB = 1

Maximum images per A.I.R. The largest number of images in a single batch that can run as an Auto Image
Import job Replication import job. Minimum: 1 job; no maximum number of images. Default: 250
images.

Configuration entry default: SLP.MAX_IMAGES_PER_IMPORT_JOB = 250

 Configuring Host Properties 251
SLP Parameters properties

Table 3-60 SLP Parameters (continued)

Property Description

Force interval for small jobs The age that the oldest image in a batch must reach after which the batch is submitted
as a duplication job. This value prevents many small duplication jobs from running at
one time or running too frequently. It also prevents NetBackup from waiting too long
before it submits a small job. Default: 30 minutes, with no minimum number or maximum
number.

Configuration entry default: SLP.MAX_TIME_TIL_FORCE_SMALL_DUPLICATION_JOB

= 30 MINUTES

Job submission interval Indicates the frequency of the job submission for all operations. No minimum interval
or maximum interval. Default: 5 minutes.

By default, all jobs are processed before more jobs are submitted. Increase this interval
to allow NetBackup to submit more jobs before all jobs are processed. Set the interval
when the list of available images is scanned for those that can be batched together
and jobs submitted. A shorter interval allows for a better response to changing system
workloads at the cost of increased processing.

Configuration entry default: SLP.JOB_SUBMISSION_INTERVAL = 5 MINUTES

Image processing interval The number of minutes between image-processing sessions. Set the interval when
newly created images are recognized and set up for SLP processing. Default: 5 minutes.

Configuration entry default: SLP.IMAGE_PROCESSING_INTERVAL = 5 MINUTES

Cleanup interval The time between when a job finishes and before NetBackup removes the job artifacts
for the completed job. No minimum interval or maximum interval. Default: 24 hours.
Configuration entry default: SLP.CLEANUP_SESSION_INTERVAL = 24 HOURS

Extended image retry The amount of time to wait before an unsuccessful operation is added to the first job
interval that runs after the delay. (This applies to all SLP jobs.) The extra time gives the
administrator additional time to solve a problem that prevents job completion. No
minimum interval or maximum interval. Default: 2 hours.

Configuration entry default: SLP.IMAGE_EXTENDED_RETRY_PERIOD = 2 HOURS

Unused SLP definition Concerns the deletion of SLP versions where a more recent version exists. The setting
version cleanup delay controls how long a version must be inactive before NetBackup deletes it. Default: 14
days.

Configuration entry default: SLP.VERSION_CLEANUP_DELAY = 14 DAYS

See “Deleting old storage lifecycle policy versions” on page 673.

 Configuring Host Properties 252
SLP Parameters properties

Table 3-60 SLP Parameters (continued)

Property Description

Tape resource multiplier Limits the number of concurrently active duplication jobs that can access a single tape
media storage unit to xx times the number of available drives. Allows tuning to avoid
overloading the Resource Broker, yet makes sure that the devices are not idle. No
minimum multiplier or maximum multiplier. Default: 2 (multiply access to the write drives
by two).

Configuration entry default: SLP.TAPE_RESOURCE_MULTIPLIER = 2

Disk resource multiplier Limits the number of concurrently active duplication jobs that can access a single disk
storage unit to xx times the number of available drives. Allows tuning to avoid
overloading the Resource Broker, yet makes sure that the devices are not idle. No
minimum multiplier or maximum multiplier. Default: 2 (multiply access to the write drives
by two).

Configuration entry default: SLP.DISK_RESOURCE_MULTIPLIER = 2

Group images across SLPs If this parameter is set to Yes (default), multiple SLPs of the same priority can be
processed in the same job. If No, batching can occur only within a single SLP.

Configuration entry default: SLP.DUPLICATION_GROUP_CRITERIA = 1

Configuration entry for no, do not allow

batching:SLP.DUPLICATION_GROUP_CRITERIA = 0

Window close buffer time Sets the amount of time before a window closes when NetBackup does not submit
new jobs using that window. Minimum 2 minute; maximum: 60 minutes. Default: 15
minutes.
Configuration entry default: SLP.WINDOW_CLOSE_BUFFER_TIME = 15 MINUTES

Deferred duplication offset For deferred operations, jobs are submitted x time before the source copy is due to
time expire. Default: 4 hours.

Configuration entry default: SLP.DEFERRED_DUPLICATION_OFFSET_TIME = 4

HOURS

Auto create A.I.R. Import Used for Auto Image Replication, indicates whether an SLP (that contains an Import
SLP operation) is created automatically in the target domain if no SLP is configured there.
Default: Yes, an SLP is created in the target domain.

Configuration entry default: SLP.AUTO_CREATE_IMPORT_SLP = 1

How long to retry failed How long NetBackup retries an Import job before it stops and deletes the record. After
A.I.R. import jobs the initial four attempts, the retries become less frequent. Default: 0 (do not retry after
the initial four attempts).

Configuration entry default: SLP.REPLICA_METADATA_CLEANUP_TIMER = 0 HOURS

 Configuring Host Properties 253
SLP Parameters properties

Command-line units of measurement for the SLP

parameters
The abbreviations are case-insensitive for units of measurement.
The following abbreviations can be used where sizes are indicated:

bytes kb kilobyte kilobyte(s) kilobytes mb megabyte

megabyte(s) megabytes gb gigabyte gigabyte(s) gigabytes tb

terabyte terabyte(s) terabytes pb petabyte petabyte(s) petabytes

The following abbreviations can be used where units of time are indicated:

sec second second(s) seconds min minute minute(s) minutes

hour hour(s) hours day day(s) days mon month

month(s) months week week(s) weeks year year(s) years

About batch creation logic in Storage Lifecycle Manager

The Storage Lifecycle Manager service (nbstserv) is in charge of creating
duplication jobs for storage lifecycle policies. Part of duplication job creation includes
grouping the backup (or source) jobs into batches.

Note: Restart nbstserv after making changes to the underlying storage for any
operation in an SLP.

One objective of the batching logic is to prevent media contention for tape operations,
including virtual tape libraries (VTL).
Batching logic applies to both disk and tape. (Though the method to prevent media
contention for disk is to use disk pools and then to limit I/O streams to disk pools.)
The batching logic requires that for each evaluation cycle, nbstserv consider all
completed source jobs when determining which duplication job to run next. By
default, nbstserv performs the evaluation once every 5 minutes.
nbstserv avoids overloading the Resource Broker (nbrb) queue with jobs. Too
many jobs in the queue make the role of the Resource Broker harder and slows
down system performance.
By default, nbstserv now creates groups based on the Group images across
SLPs parameter in the SLP Parameters host properties. By default, multiple storage
lifecycle policies with the same priority can be batched together.
 Configuring Host Properties 254
Throttle Bandwidth properties

See “SLP Parameters properties” on page 248.

This batching logic change affects how duplication jobs appear in the Activity
Monitor. Storage lifecycle policies that have been combined into one job appear
under a single policy name: SLP_MultipleLifecycles. If a storage lifecycle policy
has not been combined with another, the name appears in the Activity Monitor
under the name of the SLP: SLP_name.
Users may see some duplication jobs that, although in the running state, do not
duplicate data because they have no resources to read or write. These jobs continue
to run until they receive resources to complete the job.
To turn off grouping by duplication job priority, set the Group images across SLPs
parameter to No in the SLP Parameters host properties.

Deprecated storage lifecycle policy parameters

Three storage lifecycle policy parameters were deprecated in NetBackup 7.6 due
to changes in SLP processing.
DUPLICATION_SESSION_INTERVAL_MINUTES is no longer effective in controlling
the timing of SLP processing sessions. Two parameters now control session
processing:
■ SLP.IMAGE_PROCESSING_INTERVAL controls how often new SLP-managed
images are recognized and set up for SLP processing.
■ SLP.JOB_SUBMISSION_INTERVAL controls how often SLP processing jobs
are submitted for execution.
Import operations are controlled by the same session that performs other SLP
operations. As a result, IMPORT_SESSION_TIMER and
IMPORT_EXTENDED_RETRY_SESSION_TIMER are no longer used.
As with other SLP operations, SLP.IMAGE_PROCESSING_INTERVAL and
SLP.JOB_SUBMISSION_INTERVAL now control the frequency of SLP session
operations. SLP.IMAGE_EXTENDED_RETRY_PERIOD controls the retry behavior
for all SLP operations including import operations.

Throttle Bandwidth properties

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

Figure 3-66 Throttle Bandwidth dialog box

To manage entries in the Throttle Bandwidth dialog box, select one of the following
buttons:

Add Add a network or host to the Network or Host list using the Add
Bandwidth Settings dialog box.

Change Change the selected network or host property using the Change
Bandwidth Settings dialog box.

Remove Removes the selected network or host from the Network or Host
list.

Add Bandwidth Settings dialog box for Throttle Bandwidth properties

The Add Bandwidth Settings and the Change Bandwidth Settings dialog boxes
contain the following properties.

Network or Host The network or host to which the throttle applies.

 Configuring Host Properties 256
Timeouts properties

Bandwidth (KB/Sec) The bandwidth or the transfer rate in kilobyte per second for
the network or host indicated. A value of zero disables
throttling IPv6 addresses.

Timeouts properties
The Timeouts properties apply to selected master servers, media servers, and
clients.

Figure 3-67 Timeouts dialog box

The Timeouts dialog box contains the following properties.

Table 3-61 Timeouts dialog box properties

Property Description

Client connect timeout Specifies the number of seconds the server waits before it times out when it connects
to a client. The default is 300 seconds.
 Configuring Host Properties 257
Timeouts properties

Table 3-61 Timeouts dialog box properties (continued)

Property Description

Backup start notify timeout Specifies the number of seconds the server waits for the bpstart_notify script on
a client to complete. The default is 300 seconds.
Note: If using the bpstart_notify script: The Client read timeout
(CLIENT_READ_TIMEOUT option) must be equal to or greater than the Backup start
notify timeout (BPSTART_TIMEOUT option). If the Client read timeout is less than
the Backup start notify timeout, the job can timeout while the bpstart_notify
script is running.

File browse timeout Specifies how long the client can wait for a response from the NetBackup master server
while it lists files.
Note: If it exists, the value in a UNIX client’s $HOME/[Link] file takes precedence
to the property here.

If the limit is exceeded, the user receives a socket read failed error. The timeout can
be exceeded even while the server processes the request.

Use OS dependent timeouts Specifies that the client waits for the timeout period as determined by the operating
system when it lists files, as follows:

■ Windows client: 300 seconds

■ UNIX client: 1800 seconds

Media mount timeout Specifies how long NetBackup waits for the requested media to be mounted, positioned,
and ready on backups, restores, and duplications.

This property applies to currently selected master servers.

Use this timeout to eliminate excessive waiting time during manual media mounts. (For
example, when robotic media is out of the robot or is off-site.)
 Configuring Host Properties 258
Universal Settings properties

Table 3-61 Timeouts dialog box properties (continued)

Property Description

Client read timeout Specifies the number of seconds to use for the client-read timeout. This timeout can
apply to a NetBackup master, remote media server, or database-extension client (such
as NetBackup for Oracle). The default is 300 seconds.

If the server does not get a response from a client within the Client read timeout
period, the backup or restore operation, for example, fails.

The client-read timeout on a database-extension client is a special case. Clients can

initially require more time to get ready than other clients. More time is required because
database backup utilities frequently start several backup jobs at the same time, slowing
the central processing unit.
Note: For database-extension clients, Veritas suggests that the Client read timeout
be set to a value greater than 5 minutes. 15 minutes are adequate for many installations.
For other clients, change this property only if the client encounters problems.

The sequence on a database-extension client is as follows:

■ NetBackup on the database-extension client reads the client’s client-read timeout

to find the initial value. If the option is not set, the standard 5-minute default is used.
■ When the database-extension API receives the server’s value, it uses it as the
client-read timeout.

See “Client Settings properties for UNIX clients” on page 107.

Note: If using the bpstart_notify script: The Client read timeout
(CLIENT_READ_TIMEOUT option) must be equal to or greater than the Backup start
notify timeout (BPSTART_TIMEOUT option). If the Client read timeout is less than
the Backup start notify timeout, the job can timeout while the bpstart_notify
script is running.

Backup end notify timeout Specifies the number of seconds that the server waits for the bpend_notify script
on a client to complete. The default is 300 seconds.
Note: If this timeout is changed, verify that Client read timeout is set to the same or
higher value.

Media server connect Specifies the number of seconds that the master server waits before it times out when
timeout it connects to a remote media server. The default is 30 seconds.

Universal Settings properties

Use the Universal Settings properties in the NetBackup Administration Console
to configure basic backup and restore settings. These properties apply to selected
master servers, media servers, and clients.
 Configuring Host Properties 259
Universal Settings properties

Figure 3-68 Universal Settings dialog box

The Universal Settings dialog box contains the following options.

Table 3-62 Universal Settings dialog box properties

Property Description

Restore retries Specifies the number of attempts a client has to restore after a failure. (The default is
0; the client does not attempt to retry a restore. The client can try up to three times.)
Change Restore retries only if problems are encountered.

If a job fails after the maximum number of retries, the job goes into an incomplete state.
The job remains in the incomplete state as determined by the Move restore job from
incomplete state to done state property.

See “Clean-up properties” on page 88.

A checkpointed job is retried from the start of the last checkpointed file rather than at
the beginning of the job.

Checkpoint restart for restore jobs allows a NetBackup administrator to resume a

failed restore job from the Activity Monitor.

See “Take checkpoints every __ minutes (policy attribute)” on page 703.

 Configuring Host Properties 260
Universal Settings properties

Table 3-62 Universal Settings dialog box properties (continued)

Property Description

Browse timeframe for Specifies how long ago NetBackup searches for files to restore. For example, to limit
restores the browse range to one week before the current date, clear the Last full backup
check box and specify 7.

This limit is specified on the master server and applies to all NetBackup clients. A limit
can be specified on an individual client to reduce the size of the Search window. The
client setting cannot make the browse window larger.

By default, NetBackup includes files from the time of the last-full backup through the
latest backup for the client. If the client belongs to more than one policy, then the browse
starts with the earliest of the set of last-full backups.

Last full backup Indicates whether NetBackup includes all backups since the last successful full backup
in its browse range. This property must be disabled to enter a value for the Browse
timeframe for restores property. The default is that this property is enabled.

Use specified network Specifies the network interface that NetBackup uses to connect to another NetBackup
interface client or server. A NetBackup client or server can have more than one network interface.
To force NetBackup connections to be made on a specific network interface, use this
entry to specify the network host name of that interface. By default, the operating
system determines the one to use.

Allow server file writes Specifies whether a NetBackup server can create or modify files on the NetBackup
client. For example, enable this property to prevent server-directed restores and remote
changes to the client properties.

After the Allow server file writes property is applied, it can be cleared only by modifying
the client configuration. The default is that server writes are allowed.
 Configuring Host Properties 261
Universal Settings properties

Table 3-62 Universal Settings dialog box properties (continued)

Property Description

Logging the status of a UNIX only:

redirected restore
No progress log is produced for a redirected restore if the requesting server is not
included in the server list for the server that performs the restore. (A progress log is
an entry in the Task Progress tab of the Backup, Archive, and Restore client interface.)

Without the entry in the server list, the restoring server has no access to write the log
files to the requesting server.
Consider the following solutions:

■ To produce a progress log, add the requesting server to the server list and log into
the requesting server.
■ In the NetBackup Administration Console, expand NetBackup Management
> Host Properties > Master Servers.
■ In the details pane, double-click on master server you want to modify, and click
Servers from the options pane.
■ Add the restoring server to the server list.
■ Log on to the restoring server. Check the Activity Monitor to determine the success
of the restore operation.

Accept connections on Specifies whether the NetBackup client service (bpcd) can accept remote connections
nonreserved ports from non-reserved ports. (Non-reserved ports have port numbers of 1024 or greater.)
The default is that this property is enabled.

This property no longer applies. For information about this property, refer to NetBackup
6.5 documentation.

Client sends mail Specifies whether the client sends an email to the address that is specified in the
Universal Settings properties. If the client cannot send email, use Server sends mail.
The default is that this property is enabled.

Server sends mail Specifies whether the server sends an email to the address that is specified in the
Global Attributes properties. Enable this property if the client cannot send mail and
you want an email notification. The default is that this property is disabled.

See “Global Attributes properties” on page 159.

Client administrator’s email Specifies the email address of the administrator on the client. This address is where
NetBackup sends backup status reports for the client. By default, no email is sent. To
enter multiple addresses or email aliases, separate entries with commas.

Logging the status of a redirected restore

A redirected restore may not produce a progress log. The name of the requesting
server must appear in the server list for the server that performs the restore.
 Configuring Host Properties 262
User Account Settings properties

Otherwise, no progress log is produced for a redirected restore.(A progress log is

an entry in the Task Progress tab of the Backup, Archive, and Restore client
interface.)
Without the entry in the server list, the restoring server has no access to write the
log files to the requesting server. Add the requesting server to the server list and
log into the requesting server.
To produce a progress log
1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Host Properties > Master Servers.
2 In the right pane, double-click the master server you want to modify.
In the properties dialog box, in the left pane, click Servers.
3 Perform one of the following actions:
■ Additional servers
From the Media servers list, click Add.
■ Media servers
From the Additional servers list, click Add.

4 In the Add a New Server Entry dialog box, type the name of the new server.
5 Click Add. The dialog box remains open for another entry.
6 Click Close.
7 Log on to the restoring server.
Check the Activity Monitor to determine the success of the restore operation.
See “About the Jobs tab” on page 1038.

User Account Settings properties

Use the User Account Settings properties in the NetBackup Administration
Console to customize the idle timeout and account lockout time for users.
 Configuring Host Properties 263
User Account Settings properties

Figure 3-69 User Account Settings dialog box

The User Account Settings dialog box contains the following properties.

Table 3-63 User Account Settings dialog box properties

Property Description

GUI Idle Timeout Specifies the idle timeout if the GUI is idle or if there is no activity on the GUI for a
specified period of time.

Select the Enable auto logoff timeout check box to set the auto logoff timeout duration
as described:

■ Auto log off timeout: Select a time period. The user session is automatically
terminated after the specified time.
 Configuring Host Properties 264
UNIX Client properties

Table 3-63 User Account Settings dialog box properties (continued)

Property Description

Account lockout Specifies the user account lockout duration if the number of invalid or failed logon
attempts exceeds the specified number.

Select the Enable account lockout check box to set the account lockout duration as
described:

■ Number of failed login attempts allowed: Select 3 attempts and the account
would be locked after 3 unsuccessful login attempts.
■ Account lockout duration: Select a time period after which a user account is
automatically unlocked after the set duration.

Unlocking a user account

A user account gets locked if the number of invalid login attempts exceeds the
specified attempts or after a specified duration allowed. The user account remains
locked until the specified account lockout period. However, you can unlock the user
accounts if there is an immediate requirement. Refer to the following section to
unlock the accounts.
To unlock a user account
1 From the Actions menu, select the Unlock users option.
The Unlock Users screen is displayed; it lists names of the users whose
accounts have been locked.
2 Select the users who you want to unlock and click Unlock.
The user accounts get unlocked.
Select the Refresh option on the top right. The user accounts that you unlocked
do not show up in the list.

UNIX Client properties

Use the UNIX Client properties in the NetBackup Administration Console to
define properties of clients running on the UNIX platform.
 Configuring Host Properties 265
UNIX Server properties

Figure 3-70 UNIX Client dialog box

See “Client Settings properties for UNIX clients” on page 107.

See “Busy File Settings properties” on page 85.
See “Lotus Notes properties” on page 186.

UNIX Server properties

Use the UNIX Server properties in the NetBackup Adminstration Console to
change the NFS access timeout property. This property specifies how long the
backup waits to process the mount table before it considers an NFS file system
unavailable. The default is 5 seconds.
These properties apply to selected UNIX master servers.
 Configuring Host Properties 266
VMware Access Hosts properties

Figure 3-71 UNIX Server dialog box

See “Follow NFS (policy attribute)” on page 710.

VMware Access Hosts properties

Use the VMware Access Hosts properties in the NetBackup Administration
Console to add or remove VMware backup hosts. These properties apply to
currently selected master servers.
These properties appear when the NetBackup Enterprise Client license is installed.
 Configuring Host Properties 267
VMware Access Hosts properties

Figure 3-72 VMware Access Hosts dialog box

The backup host is a NetBackup client that performs backups on behalf of the virtual
machines. (This host was formerly known as the VMware backup proxy server.)
The backup host is the only host on which NetBackup client software is installed.
As an option, the backup host can also be configured as a NetBackup master server
or media server.
The backup host is referred to as the recovery host when it performs a restore
You can add servers to and remove servers from the access hosts list:

Add Click Add and enter the fully qualified domain name of the backup host.

Remove Select the backup host in the list and click Remove.

For more information, see the NetBackup for VMware Administrator’s Guide.
 Configuring Host Properties 268
Windows Client properties

Windows Client properties

Use the Windows Client properties in the NetBackup Administration Console
to define NetBackup properties for Microsoft Windows clients.

Figure 3-73 Windows Client dialog box

Windows Client properties include specific host properties for configuring Windows
clients.

Configuration options not found in the Host

Properties
Most NetBackup configuration options can be found in the Host Properties of the
NetBackup Administration Console. However, some options cannot be accessed
in the Host Properties.
To change the default value for an option that is not found in the Host Properties,
first use the nbgetconfig command to obtain a list of configuration options. Then
use nbsetconfig to change the options as needed.
 Configuring Host Properties 269
Configuration options not found in the Host Properties

For information about these commands, see the NetBackup Commands Reference
Guide.
The following NetBackup administration options cannot be configured by using the
NetBackup Administration Console.

AUTO_ADD_ALL_ALIASES_FOR_CLIENT See “AUTO_ADD_ALL_ALIASES_FOR_CLIENT option for

NetBackup servers” on page 277.

BPARCHIVE_POLICY See “BPARCHIVE_POLICY option for NetBackup clients”

on page 347.

BPARCHIVE_SCHED See “BPARCHIVE_SCHED option for NetBackup clients”

on page 347.

BPBACKUP_POLICY See “BPBACKUP_POLICY option for NetBackup clients”

on page 348.

BPBACKUP_SCHED See “BPBACKUP_SCHED option for NetBackup clients”

on page 349.

BPDBJOBS_COLDEFS See “BPDBJOBS_COLDEFS options for UNIX master servers”

on page 280.

CHECK_RESTORE_CLIENT See “CHECK_RESTORE_CLIENT option for NetBackup

servers” on page 289.

EMMSERVER See “EMMSERVER option for NetBackup servers” on page 304.

GENERATE_ENGLISH_LOGS See “GENERATE_ENGLISH_LOGS option for NetBackup

servers and clients” on page 306.

IGNORE_XATTR See “IGNORE_XATTR option for NetBackup clients”

on page 363.

INFORMIX_HOME See “INFORMIX_HOME option for NetBackup clients”

on page 366.

KEEP_DATABASE_COMM_FILE See “KEEP_DATABASE_COMM_FILE option for NetBackup

clients” on page 367.

REPORT_CLIENT_DISCOVERIES See “REPORT_CLIENT_DISCOVERIES option for NetBackup

clients” on page 372.

RESUME_ORIG_DUP_ON_OPT_DUP_FAIL See “RESUME_ORIG_DUP_ON_OPT_DUP_FAIL option for

NetBackup servers” on page 328.

SYBASE_HOME See “SYBASE_HOME option for NetBackup clients”

on page 375.
 Configuring Host Properties 270
About using commands to change the configuration options on UNIX clients and servers

ULINK_ON_OVERWRITE See “ULINK_ON_OVERWRITE option for NetBackup servers”

on page 340.

[Link] file (media and device configuration options) See the NetBackup Administrator's Guide, Volume II.

About using commands to change the

configuration options on UNIX clients and servers
When commands (nbsetconfig or bpsetconfig) are used to change the
configuration options on UNIX NetBackup servers or clients, the commands change
the appropriate configuration files.
Most options are found in the following configuration file:
/usr/openv/netbackup/[Link]

If a single UNIX system is running as both a client and a server, the [Link] file
contains options for both the client and the server.
The [Link] file observes the following syntax:
■ Use the # symbol to comment out lines.
■ Any number of spaces or tabs are allowed on either side of = signs.
■ Blank lines are allowed.
■ Any number of blanks or tabs are allowed at the start of a line.
Each nonroot user on a UNIX client can also have a personal [Link] file in their
home directory:

$HOME/[Link]

The options in personal [Link] files apply only to user operations. During a user
operation, NetBackup checks the $HOME/[Link] file before
/usr/openv/netbackup/[Link].

Root users do not have personal [Link] files. NetBackup uses the
/usr/openv/netbackup/[Link] file for root users.

Stop and restart all NetBackup daemons and utilities on the server after you make
a change to the [Link] file on a UNIX master server. This action ensures that all
of the NetBackup processes use the new [Link] values. This action is not required
for changes to [Link] files on a client or to a $HOME/[Link] file on the master
server.
 Configuring Host Properties 271
Configuration options for NetBackup servers

The SERVER option must be present in the /usr/openv/netbackup/[Link] file on

all NetBackup UNIX clients and servers. During installation, NetBackup sets the
SERVER option to the name of the master server where the software is installed. It
is the only required option in the [Link] files. NetBackup uses internal software
defaults for all options in the [Link] file, except SERVER.
The SERVER entries must be the same on all servers in a master and a media server
cluster. Veritas recommends (but does not require) that all other entries also match
on all servers. (The CLIENT_NAME option is an exception.)

Configuration options for NetBackup servers

The following topics are about configuration options for NetBackup servers. Nearly
all of these options can also be set in the Host Properties in the NetBackup
Administration Console.
See “Configuration options not found in the Host Properties” on page 268.

About robust logging

The Robust logging option indicates to NetBackup to limit the amount of disk space
that a log directory consumes. When a log file grows to the specified maximum
size, the log file is closed and a new log file is opened. If the new log file causes
the maximum number of log files in the directory to be exceeded, the oldest log file
is deleted.
In NetBackup 7.6.1 or earlier versions, you can enable or disable robust logging in
the NetBackup Administration Console in the Logging host properties. The
Enable Robust Logging option was disabled by default.
See “Logging properties” on page 170.
Starting from NetBackup 7.7, the Enable Robust Logging option is removed from
the Logging host properties because the option is always enabled. The error logs
are always created based on the robust logging configuration parameters.
However, the following configuration parameter still appears when you run the
bpgetconfig command: ENABLE_ROBUST_LOGGING = NO

Regardless of the value of the ENABLE_ROBUST_LOGGING configuration parameter,

robust logging is always enabled.
Before NetBackup 7.7, robust logging was applicable only for unified logging. Robust
logging is also enabled for legacy logging for NetBackup servers and clients.
 Configuring Host Properties 272
Configuration options for NetBackup servers

Known issue: Robust logging is enabled only for Informix and SAP database
agents for NetBackup. For the remaining NetBackup database agents, robust
logging is not enabled.
Robust logging functionality comprises the following configuration parameters:

MAX_LOGFILE_SIZE This configuration parameter specifies the maximum size that

you want to set for a log file in MB.

The default value for MAX_LOGFILE_SIZE is 50 MB.

See “MAX_LOGFILE_SIZE option for NetBackup servers and

clients for legacy logging” on page 313.

MAX_NUM_LOGFILES This configuration parameter specifies the maximum number

of log files that you want to be created in NetBackup.

The default value for MAX_NUM_LOGFILES is infinite.

See “MAX_NUM_LOGFILES option for NetBackup servers

and clients for legacy logging” on page 314.

Note: Initially, MAX_LOGFILE_SIZE and MAX_NUM_LOGFILES parameter entries are

not present in the output for bpgetconfig. In this case, they are set to their default
values. In UNIX, you can update the [Link] configuration file using the
bpsetconfig command to set these parameters to different values. In Windows,
you can add the parameters using the bpsetconfig command in the registry.

About robust logging functionality after upgrade

After an upgrade to NetBackup 7.7 or later, Enable Robust Logging is enabled.
This is true even if the setting had been disabled before the upgrade.
After an upgrade to NetBackup 7.7 or later, the MAX_LOGFILE_SIZE is set to a new
default.
The following points concern various upgrade scenarios to NetBackup 7.7 or later
with respect to MAX_LOGFILE_SIZE:
■ If robust logging was enabled before the upgrade:
■ The old unified logging default value for MaxLogFileSizeKB was 51200 KB.
After the upgrade, the legacy logging default for MAX_LOGFILE_SIZE is 50
MB.
■ The old unified logging default value for NumberOfLogFiles was 3. After the
upgrade, the legacy logging value for MAX_NUM_LOGFILES is 3.

■ If robust logging was disabled before the upgrade:

 Configuring Host Properties 273
Configuration options for NetBackup servers

■ After the upgrade, robust logging is enabled with the following configuration
settings:
MAX_LOGFILE_SIZE = 50 MB
MAX_NUM_LOGFILES = INFINITE

ALLOW_MEDIA_OVERWRITE option for NetBackup servers

This option overrides the NetBackup overwrite protection for various media formats
on removable media.

Table 3-64 ALLOW_MEDIA_OVERWRITE information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

ALLOW_MEDIA_OVERWRITE = media_format

This option should appear only once in the configuration file.

Example On the master server (and media servers if applicable), add the following entry to permit
overwriting the cpio format:

ALLOW_MEDIA_OVERWRITE = CPIO

Equivalent Administration NetBackup Management > Host Properties > Click Master Servers or Media Servers
Console property > Double-click on server > Media > Allow media overwrite.

See “Media properties” on page 189.

ALLOW_NON_RESERVED_PORTS option for NetBackup servers

and clients
This option is not applicable to NetBackup 7.0.1 or later.
This option specifies that the NetBackup Client daemon (bpcd) can accept remote
connections from unauthorized ports (port numbers 1024 or greater). If this option
is not present, bpcd requires remote connections to come from privileged ports
(port numbers 1024 or smaller). This option is useful when NetBackup clients and
servers are on opposite sides of a firewall.
 Configuring Host Properties 274
Configuration options for NetBackup servers

Table 3-65 ALLOW_NON_RESERVED_PORTS information

Usage Description

Where to use On NetBackup master servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

ALLOW_NON_RESERVED_PORTS = YES | NO

This option should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Click Master Servers, Media Servers,
Console property Clients > Double-click on server > Universal Settings > Accept Connections on
Non-reserved Ports.

See “Universal Settings properties” on page 258.

AUTHENTICATION_DOMAIN option for NetBackup servers and

clients
This option defines a set of NetBackup product authentication principles.

Table 3-66 AUTHENTICATION_DOMAIN information

Usage Description

Where to use A master server, media server, or client that uses NetBackup product authentication
and authorization must have at least one AUTHENTICATION_DOMAIN entry listed for
this option. More than one domain can be specified.

If a media server or client does not define an authentication domain, it uses the
authentication domains of its master server.
 Configuring Host Properties 275
Configuration options for NetBackup servers

Table 3-66 AUTHENTICATION_DOMAIN information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

AUTHENTICATION_DOMAIN = domain "comment"

mechanism broker [port]

This option may appear more than once in the configuration file.
The following variables are defined:

■ domain is an Internet domain name or a Windows domain name.

■ "comment" is a quoted comment that describes the authentication domain.
■ mechanism is the authentication mechanism.
The keywords for various mechanisms are as follows:
■ NIS: Network Information Service version 1
■ NIS+: Network Information Service version 2
■ PASSWD: Local UNIX password file on the specified broker
■ VXPD: The NetBackup product authentication and authorization private database
■ WINDOWS: Windows Active Directory or primary domain controller
■ broker is the host name or IP address of the authentication broker.
■ port is the port number of the authentication broker. The default is the standard port
number for authentication brokers.
 Configuring Host Properties 276
Configuration options for NetBackup servers

Table 3-66 AUTHENTICATION_DOMAIN information (continued)

Usage Description

Example AUTHENTICATION_DOMAIN = [Link] "Typical UNIX logins"

NIS [Link]
AUTHENTICATION_DOMAIN = OurEnterprise "Typical Windows logins"
WINDOWS [Link] 5544
AUTHENTICATION_DOMAIN = [Link] "VxSS-Only Identities"
VXPD [Link]
AUTHENTICATION_DOMAIN = [Link] "Local
UNIX Logins on host broker3" PASSWD [Link]

In this example:

■ [Link] is the Internet domain name and OurEnterprise is the Windows

domain name.
■ The broker on host name broker1 handles both NIS and private authentication
for NetBackup product authentication.
■ The broker on host name broker2 handles Windows authentication for NetBackup
product authentication.
■ broker2 uses the non-standard port number 5544.
■ The broker on host name broker3 uses its local /etc/passwd file for NetBackup
product authentication.

Equivalent Administration NetBackup Management > Host Properties > Click Master Servers, Media Servers,
Console property Clients > Double-click on server > Access Control > Authentication Domain.

See “Authentication Domain tab of the Access Control properties” on page 76.

AUTHORIZATION_SERVICE option for NetBackup servers

This option defines the NetBackup Product Authorization Service that the local
NetBackup server uses.

Table 3-67 AUTHORIZATION_SERVICE information

Usage Description

Where to use A master server that uses NetBackup product authorization must define an authorization
service. If a media server does not define an authorization service, it uses the
authorization service of the master server.
 Configuring Host Properties 277
Configuration options for NetBackup servers

Table 3-67 AUTHORIZATION_SERVICE information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

AUTHORIZATION_SERVICE = host [ port ]

The following variables are defined:

■ host is the host name or IP address of the authorization service.

■ port is the port number of the authorization service. The default is the standard port
number for the authorization service.

This option should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Click Master Servers or Media Servers
Console property > Double-click on server > Access Control > Authorization Service.

See “Authorization Service tab of the Access Control properties” on page 78.

AUTO_ADD_ALL_ALIASES_FOR_CLIENT option for NetBackup

servers
This option allows client aliases to be automatically added to the NetBackup
database when bpdbm detects a new client in a backup policy.

Table 3-68 AUTO_ADD_ALL_ALIASES_FOR_CLIENT information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 278
Configuration options for NetBackup servers

Table 3-68 AUTO_ADD_ALL_ALIASES_FOR_CLIENT information

(continued)

Usage Description

How to use By default, AUTO_ADD_ALL_ALIASES_FOR_CLIENT is not present in the configuration

file. When AUTO_ADD_ALL_ALIASES_FOR_CLIENT is not present, the option is
enabled. That is, bpdbm is allowed to add client aliases automatically.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

AUTO_ADD_ALL_ALIASES_FOR_CLIENT = YES | NO

This entry should appear only once in the configuration file.

Example The following entry prohibits bpdbm from adding a client alias automatically:

AUTO_ADD_ALL_ALIASES_FOR_CLIENT = NO

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

BPBRM_VERBOSE option for NetBackup servers

The BPBRM_VERBOSE option is used for debugging purposes. It controls the amount
of information that NetBackup includes in the bpbrm debug log.

Table 3-69 BPBRM_VERBOSE information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 279
Configuration options for NetBackup servers

Table 3-69 BPBRM_VERBOSE information (continued)

Usage Description

How to use The default is that BPBRM_VERBOSE is the same value as the VERBOSE option (Global
logging level). The BPBRM_VERBOSE option overrides the VERBOSE option in the
configuration file.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPBRM_VERBOSE = -1 | 0 | 1 | 2 | 3 | 4 | 5

This entry should appear only once in the configuration file.

Example ■ To use the same value as the VERBOSE option, enter:

BPBRM_VERBOSE = 0
This option is the same as setting the BPBRM logging level in the Logging host
properties to Same as Global.
■ To log the minimum amount of information, enter:
BPBRM_VERBOSE = -1
This option is the same as setting the BPBRM logging level to 0 in the Logging
host properties.
■ To log additional information, enter a value of 1 through 5:
BPBRM_VERBOSE = 1
This option is the same as setting the BPBRM logging level to 1 in the Logging
host properties.
■ To log the maximum amount of information, enter:
BPBRM_VERBOSE = 5
This option is the same as setting the BPBRM logging level to 5 in the Logging
host properties.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Logging > BPBRM logging level.

See the NetBackup Logging Reference Guide for more information about the debug
log.

See “Logging properties” on page 170.

BPCD_WHITELIST_PATH option for NetBackup servers and clients

NetBackup will deny access to a file that is specified for NetBackup operations if
the path is a non-default path. For example, a path that is specified for progress
 Configuring Host Properties 280
Configuration options for NetBackup servers

log or rename files. You must use the BPCD_WHITELIST_PATH option to allow access
to non-default custom paths.

Table 3-70 BPCD_WHITELIST_PATH information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPCD_WHITELIST_PATH = Absolute pathname to the directory

Example The following are the example entries on a NetBackup server or client:

BPCD_WHITELIST_PATH = directory1

BPCD_WHITELIST_PATH = directory2

Create a separate entry for each directory.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

BPDBJOBS_COLDEFS options for UNIX master servers

Use BPDBJOBS_COLDEFS entries to customize the output of the bpdbjobs process.
Add a BPDBJOBS_COLDEFS option for every column you want to include in the output.
Add BPDBJOBS_COLDEFS entries to the [Link] file to customize the output of the
bpdbjobs process.

Table 3-71 BPDBJOBS_COLDEFS information

Usage Description

Where to use On a UNIX NetBackup master server.

 Configuring Host Properties 281
Configuration options for NetBackup servers

Table 3-71 BPDBJOBS_COLDEFS information (continued)

Usage Description

How to use Add BPDBJOBS_COLDEFS to the /usr/openv/netbackup/[Link] file.

Add an entry for every column to include in the output by using the following format:

BPDBJOBS_COLDEFS = COLDEFS_ENTRY [minimum_size [true |

false]]

The following variables are defined:

■ COLDEFS_ENTRY is the name of the column to include in the output.

■ minimum_size is the minimum column width. If not specified, the default is a width
of 5.
■ true indicates that the column should expand as needed. If not specified, true
is the default.
■ false indicates that the column should not expand beyond the minimum_size.

Example The order of the entries determines the order in which the column headings appear.

BPDBJOBS_COLDEFS = JOBID 5 true

BPDBJOBS_COLDEFS = TYPE 4 true
BPDBJOBS_COLDEFS = STATE 5 true
BPDBJOBS_COLDEFS = STATUS 6 true
BPDBJOBS_COLDEFS = POLICY 6 true
BPDBJOBS_COLDEFS = SCHEDULE 8 true
BPDBJOBS_COLDEFS = CLIENT 6 true
BPDBJOBS_COLDEFS = DSTMEDIA_SERVER 12 true
BPDBJOBS_COLDEFS = ACTPID 10 true

The appearance of BPDBJOBS_COLDEFS entries in the [Link] file has the following
ramifications:

■ The addition of any BPDBJOBS_COLDEFS option overrides all default columns.

■ All users on the local system see only those columns that are specified in the
[Link] file.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

Table 3-72 shows possible COLDEFS entries and the column which is created by
each.
 Configuring Host Properties 282
Configuration options for NetBackup servers

Table 3-72 COLDEFS entries

COLDEFS entry Column Name

ACTIVEELAPSED Active Elapsed (elapsed active time)

ACTPID Active PID (PID of job)

ATTEMPT Attempt

BACKUPTYPE Backup Type

CLIENT Client

COMPLETION Completion (percent complete)

COMPRESSION Compression (yes or no)

DEDUPRATIO Dedup (shows deduplication rate in

bpdbjobs command output)

DSTMEDIA_SERVER Dest Media Svr (writing media server)

DSTMEDIAID Dest Media ID (writing media ID)

DSTSTORAGE_UNIT Dest StUnit (writing storage unit)

ELAPSED Elapsed (elapsed time)

ENDED Ended

ESTFILE Est File (estimated number of files)

ESTKB Est KB (estimated number of kilobytes)

FILES Files

GROUP Group

JOBID JobID

KBPERSEC KB Per Sec

KILOBYTES Kilobytes

LASTBACKUP Last Backup (date and time)

MAINPID Main PID (PID that spawns job, if applicable)

NUMTAPESEJECT Media to Eject (number of tapes to eject;

Vault only)
 Configuring Host Properties 283
Configuration options for NetBackup servers

Table 3-72 COLDEFS entries (continued)

COLDEFS entry Column Name

OPERATION Operation (current operation)

OWNER Owner

PATHNAME Pathname

PARENTJOBID Parent JobID

POLICY Policy

POLICYTYPE Policy Type

PRIORITY Priority

PROFILE Profile (Vault only)

RETENTION Retention (retention period)

RESUMABLE Resumable

ROBOT Robot (Vault only)

RQSTPID Request PID (PID requesting job, if

applicable)

SCHEDULE Schedule

SCHEDULETYPE Schedule Type

SESSIONID Session ID (Vault only)

SRCMEDIA_SERVER Src Media Svr

SRCMEDIAID Src Media ID

SRCSTORAGE_UNIT Src StUnit

STARTED Started

STATE State

STATUS Status

STREAMNUMBER Stream Number

SUSPENDABLE Suspendable

TYPE Type (job type)

 Configuring Host Properties 284
Configuration options for NetBackup servers

Table 3-72 COLDEFS entries (continued)

COLDEFS entry Column Name

VAULT Vault (Vault only)

BPDBM_VERBOSE option for NetBackup servers

The BPDBM_VERBOSE option is used for debugging purposes. It controls the amount
of information NetBackup includes in the bpdbm debug log.

Table 3-73 BPDBM_VERBOSE information

Usage Description

Where to use On NetBackup master servers.

How to use The default is that BPDBM_VERBOSE is the same value as the VERBOSE option (Global
logging level). The BPDBM_VERBOSE option overrides the VERBOSE option in the
configuration file.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPDBM_VERBOSE = -1 | 0 | 1 | 2 | 3 | 4 | 5

This entry should appear only once in the configuration file.

 Configuring Host Properties 285
Configuration options for NetBackup servers

Table 3-73 BPDBM_VERBOSE information (continued)

Usage Description

Example ■ To use the same value as the VERBOSE option for, enter:
BPDBM_VERBOSE = 0
This option is the same as setting the BPDBM logging level to Same as Global
in the Logging host properties.
■ To log the minimum amount of information, enter:
BPDBM_VERBOSE = -1
This option is the same as setting the BPDBM logging level to 0 in the Logging
host properties.
■ To log additional information, enter a value of 1 through 5:
BPDBM_VERBOSE = 1
This option is the same as setting the BPDBM logging level to 1 in the Logging
host properties.
■ To log the maximum amount of information, enter:
BPDBM_VERBOSE = 5
This option is the same as setting the BPDBM logging level to 5 in the Logging
host properties.

The following examples show two entries which enable logging, while they minimize
the growth rate of the bpdbm debug file:

VERBOSE = 5

BPDBM_VERBOSE = -1

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Logging > Global logging level > BPDBM logging level.

See the NetBackup Logging Reference Guide for more information about logging.

See “Logging properties” on page 170.

BPRD_VERBOSE option for NetBackup servers

Used for debugging purposes, the BPRD_VERBOSE option controls the amount of
information that NetBackup includes in the bprd debug logs.

Table 3-74 BPRD_VERBOSE information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 286
Configuration options for NetBackup servers

Table 3-74 BPRD_VERBOSE information (continued)

Usage Description

How to use The default is that the value is the same as the VERBOSE option (Global logging level).
The BPRD_VERBOSE option overrides the VERBOSE option in the configuration file.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPRD_VERBOSE = -1 | 0 | 1 | 2 | 3 | 4 | 5

This entry should appear only once in the configuration file.

Example ■ To use the same value as the VERBOSE option, enter:

BPRD_VERBOSE = 0
This option is the same as setting the BPRD logging level in the Logging host
properties to Same as Global.
■ To log the minimum amount of information, enter:
BPRD_VERBOSE = -1
This option is the same as setting the BPRD logging level to 0 in the Logging
host properties.
■ To log additional information, enter a value of 1 through 5:
BPRD_VERBOSE = 1
This option is the same as setting the BPRD logging level to 1 in the Logging
host properties.
■ To log the maximum amount of information, enter:
BPRD_VERBOSE = 5
This option is the same as setting the BPRD logging level to 5 in the Logging
host properties.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Logging > BPRD logging level.

See the NetBackup Logging Reference Guide for more information about the debug
log.

See “Logging properties” on page 170.

BPTM_VERBOSE option for NetBackup servers

The BPTM_VERBOSE option is used for debugging purposes. It controls the amount
of information that NetBackup includes in the bptm debug logs.
 Configuring Host Properties 287
Configuration options for NetBackup servers

Table 3-75 BPTM_VERBOSE information

Usage Description

Where to use On NetBackup master servers.

How to use The default is that BPTM_VERBOSE is the same value as the VERBOSE option (Global
logging level). The BPTM_VERBOSE option overrides the VERBOSE option in the
configuration file.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPTM_VERBOSE = -1 | 0 | 1 | 2 | 3 | 4 | 5

This entry should appear only once in the configuration file.

Example ■ To use the same value as the VERBOSE option, enter:

BPTM_VERBOSE = 0
This option is the same as setting the BPTM logging level in the Logging host
properties to Same as Global.
■ To log the minimum amount of information, enter:
BPTM_VERBOSE = -1
This option is the same as setting the BPTM logging level to 0 in the Logging
host properties.
■ To log additional information, enter a value of 1 through 5:
BPTM_VERBOSE = 1
This option is the same as setting the BPTM logging level to 1 in the Logging
host properties.
■ To log the maximum amount of information, enter:
BPTM_VERBOSE = 5
This option is the same as setting the BPTM logging level to 5 in the Logging
host properties.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Logging > BPTM logging level.

See the NetBackup Logging Reference Guide for more information about the debug
log.

See “Logging properties” on page 170.

 Configuring Host Properties 288
Configuration options for NetBackup servers

BPEND_TIMEOUT option for NetBackup servers

The BPEND_TIMEOUT option specifies the number of seconds to wait for the
bpend_notify script on a client to complete.

Table 3-76 BPEND_TIMEOUT information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPEND_TIMEOUT = seconds

The default timeout is 300 seconds (five minutes).

Note: If this option is changed, verify that the CLIENT_READ_TIMEOUT option is set
to the same value or higher.

This entry should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Timeouts > Backup end notify timeout.

See “Timeouts properties” on page 256.

BPSTART_TIMEOUT option for NetBackup servers

The BPSTART_TIMEOUT option specifies the number of seconds to wait for the
bpstart_notify script on a client to complete.

Table 3-77 BPSTART_TIMEOUT information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 289
Configuration options for NetBackup servers

Table 3-77 BPSTART_TIMEOUT information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

BPSTART_TIMEOUT = seconds

The default timeout is 300 seconds (five minutes).

Note: If using the bpstart_notify script: The Client read timeout
(CLIENT_READ_TIMEOUT option) must be equal to or greater than the Backup start
notify timeout (BPSTART_TIMEOUT option). If the Client read timeout is less than
the Backup start notify timeout, the job can timeout while the bpstart_notify
script is running.

This option should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Timeouts > Backup start notify timeout.

See “Timeouts properties” on page 256.

CHECK_RESTORE_CLIENT option for NetBackup servers

The CHECK_RESTORE_CLIENT option specifies that the client to be restored to is
checked before the restore starts. An unresponsive client can slow restores for
other clients that have data on the same tapes.

Table 3-78 CHECK_RESTORE_CLIENT information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

This option should appear only once in the configuration file.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property
 Configuring Host Properties 290
Configuration options for NetBackup servers

CLIENT_CONNECT_TIMEOUT option for NetBackup servers

This option specifies the number of seconds that the server waits when it connects
to a client. If the server needs to wait longer than the time specified, it times out.

Table 3-79 CLIENT_CONNECT_TIMEOUT information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

CLIENT_CONNECT_TIMEOUT = seconds

The default timeout is 300 seconds (five minutes).

This option should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Timeouts > Client connect timeout.

See “Timeouts properties” on page 256.

CLIENT_PORT_WINDOW option for NetBackup servers and clients

This option specifies the range of non-reserved ports on this computer that are
used as source ports when connecting to NetBackup on other computers. This
setting applies to daemon or service socket connections to the server and to the
client hosts as well as call-back from bpcd.

Table 3-80 CLIENT_PORT_WINDOW information

Usage Description

Where to use On NetBackup servers and clients.

 Configuring Host Properties 291
Configuration options for NetBackup servers

Table 3-80 CLIENT_PORT_WINDOW information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

CLIENT_PORT_WINDOW = start_port_range end_port_range

If 0 is specified for the first number (default), the operating system determines the
non-reserved port to use.

This option should appear only once in the configuration file.

Example The following example permits ports from 4800 through 5000:

CLIENT_PORT_WINDOW = 4800 5000

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Port Ranges > Client port window.

See “Port Ranges properties” on page 201.

CLIENT_READ_TIMEOUT option for NetBackup servers

The CLIENT_READ_TIMEOUT option specifies the number of seconds to use for the
client-read timeout.
If the master server does not get a response from a client within the
CLIENT_READ_TIMEOUT period, the backup or restore operation, for example, fails.

Table 3-81 CLIENT_READ_TIMEOUT information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 292
Configuration options for NetBackup servers

Table 3-81 CLIENT_READ_TIMEOUT information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

CLIENT_READ_TIMEOUT = seconds

By default, CLIENT_READ_TIMEOUT is not present on the server or the database

agent and the client-read timeout is 300 seconds (five minutes). This time is a
reasonable default. Change only in the event of problems.

CLIENT_READ_TIMEOUT on a database agent is a special case because these types

of clients can initially require more time to get ready than other clients. Database backup
utilities frequently start several backup jobs at the same time, which can slow the CPU.
The sequence on a database agent is as follows:

■ NetBackup on the database agent reads the client’s CLIENT_READ_TIMEOUT to

find the value to use initially. If the option is not set, the standard default of five
minutes is used.
■ When the database agent API receives the server’s value, it uses it as the
CLIENT_READ_TIMEOUT.

Note: Veritas suggests setting CLIENT_READ_TIMEOUT on the database agent to a

value greater than 5 minutes. A setting of 15 minutes is adequate for many installations.

Note: If using the bpstart_notify script: The Client read timeout

(CLIENT_READ_TIMEOUT option) must be equal to or greater than the Backup start
notify timeout (BPSTART_TIMEOUT option). If the Client read timeout is less than
the Backup start notify timeout, the job can timeout while the bpstart_notify
script is running.

Example The following example configures a client read timeout of 15 minutes.

CLIENT_READ_TIMEOUT = 900

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Timeouts > Client read timeout.

See “Timeouts properties” on page 256.

 Configuring Host Properties 293
Configuration options for NetBackup servers

CLIENT_RESERVED_PORT_WINDOW option for NetBackup servers

and clients
The CLIENT_RESERVED_PORT_WINDOW option specifies the range of reserved ports
on this computer that are used for connecting to NetBackup on other computers.
This setting applies when the computer connects to a client (bpcd) configured to
accept only reserved ports.
Beginning with NetBackup 7.0.1, connections to other daemon ports use only the
CLIENT_PORT_WINDOW, not the CLIENT_RESERVED_PORT_WINDOW.

Table 3-82 CLIENT_RESERVED_PORT_WINDOW information

Usage Description

Where to use On NetBackup master servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

CLIENT_RESERVED_PORT_WINDOW = start_port_range end_port_range

The default is from 512 through 1023. Note that if 0 is specified for the first number, a
non-reserved port is used instead. The operating system chooses the nonreserved
port.
This option should appear only once in the configuration file.

Example The following example permits ports from 900 through 1023:

CLIENT_RESERVED_PORT_WINDOW = 900 1023

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Port Ranges > Client reserved port window.

See “Port Ranges properties” on page 201.

CLIENTDB_RESYNC_INTERVAL option for NetBackup servers and

clients
The CLIENTDB_RESYNC_INTERVAL option specifies the time interval to synchronize
data entry changes to the NetBackup client database.
 Configuring Host Properties 294
Configuration options for NetBackup servers

Table 3-83 CLIENTDB_RESYNC_INTERVAL information

Usage Description

Where to use On NetBackup clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

CLIENTDB_RESYNC_INTERVAL = days

The default value is 1 day.

The maximum value for this option is 7 days. The minimum value for this option is zero,
which implies that the option is turned off and that no data synchronization happens.

This option should appear only once in the configuration file.

Example The following example sets the time interval of 3 days to allow data synchronization
to the client database:

CLIENTDB_RESYNC_INTERVAL = 3

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

CONNECT_OPTIONS option for NetBackup servers and clients

The CONNECT_OPTIONS option specifies the following options that are designed to
enhance firewall efficiency with NetBackup:
■ Whether processes on host are reached:
■ By using the Veritas Network daemon (vnetd) port only.
■ By using the daemon ports only.
■ By first using the vnetd port and then the daemon ports if needed.

■ Whether subsequent call-back connections with host use the traditional call-back
method or use vnetd.
■ Whether connections to host use reserved or a non-reserved port number.
 Configuring Host Properties 295
Configuration options for NetBackup servers

Table 3-84 CONNECT_OPTIONS information

Usage Description

Where to use On NetBackup master servers, media servers, or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

CONNECT_OPTIONS = host [ 0 | 1 | 2 ]
[ 0 | 1 | 2 ][ 0 | 1 | 2 | 3]

The following variables are defined:

Host is a NetBackup system to which this computer connects. You may have multiple
CONNECT_OPTIONS entries in the configuration. If a host is not specified in any
CONNECT_OPTIONS entries, the values from the DEFAULT_CONNECT_OPTIONS option
are used.

See “DEFAULT_CONNECT_OPTIONS option for NetBackup servers and clients”

on page 298.

The first setting indicates the type of port to use as the source port for connections to
service daemons on host:

0 = Connections from this computer should be from a reserved source port number.
It is selected from the CLIENT_RESERVED_PORT_WINDOW range.

1 = Connections from this computer should be from a non-reserved source port number
that is selected from the CLIENT_PORT_WINDOW range. (The default is 1.) If this option
is selected for use with the daemon port and host is running a version of NetBackup
older than 7.1, enable Allow non reserved ports for the selected host.

In the NetBackup Administration Console, see the Universal Settings dialog box
under Host Properties > Media Servers.

2 = Use the method that the DEFAULT_CONNECT_OPTIONS configuration option

defines.

See “Universal Settings properties” on page 258.

 Configuring Host Properties 296
Configuration options for NetBackup servers

Table 3-84 CONNECT_OPTIONS information (continued)

Usage Description

The second setting indicates the call-back method to use with host. (This applies if
configured to use the daemon port or if bpcd cannot be reached using ports 1556 or
13724.)

0 = Use the traditional call-back method. Host connects back to a random port number
that this computer has selected from the SERVER_RESERVED_PORT_WINDOW range,
or SERVER_PORT_WINDOW range as determined by the first setting.

1 = Use the vnetd no call-back method. Connect to vnetd instead of a random port.
If this computer is NetBackup 7.0.1 or later, attempt to connect to port 1556 before
attempting to connect to vnetd. The connection is outbound to host if the third setting
is 0 or 1. The connection is inbound from host if the third setting is 2.

2 = Use the method that the DEFAULT_CONNECT_OPTIONS configuration option defines

(default).

The third setting affects which destination port number to use for connections to daemon
services on host.

0 = Use vnetd if possible, to connect to a daemon on this computer. If it is not possible,

connect by using the traditional port number of the daemon. If this host is NetBackup
7.0.1 or later, attempt to connect to port 1556 before attempting to connect to vnetd.
If bpcd is reachable through port 1556 or vnetd, then the first two settings are ignored
and all connections to host are outbound and use non-reserved ports.

1 = Use vnetd to connect to a daemon on host. If this computer is NetBackup 7.0.1

or later, attempt to connect to port 1556 before attempting to connect to vnetd. The
traditional port number of the daemon is not used if the connection cannot be established
using port 1556 or vnetd. If bpcd is reachable through port 1556 or vnetd, then the
first two settings are ignored and all connections to host are outbound and use
non-reserved ports.

2 = Use only the traditional port number of the daemon to connect to a daemon on
host. If the daemon is bpcd, the second setting is then used to determine the call-back
method.

3 = Use the method that the DEFAULT_CONNECT_OPTIONS configuration option defines

(default).
 Configuring Host Properties 297
Configuration options for NetBackup servers

Table 3-84 CONNECT_OPTIONS information (continued)

Usage Description

Example 1 The configuration file can contain CONNECT_OPTIONS settings for multiple hosts.

CONNECT_OPTIONS = shark 0 0 0

In this example, connections to daemons on shark attempt to use port 1556 if this
computer is running NetBackup 7.0.1 or later. If this computer is running a version of
NetBackup that is earlier than 7.0.1, or if the previous attempt was unsuccessful, then
the connections try vnetd. If that attempt is unsuccessful, the daemon port is used. If
the connections are successful using 1556 or vnetd, then the first two settings are
ignored.

$ bptestbpcd -host shark

0 0 1
[Link]:40402 -> [Link]:1556
[Link]:40404 -> [Link]:1556

Example 2 CONNECT_OPTIONS = dolphin 1 0 1

In this example, connections to daemons on dolphin attempt to use port 1556 if this
computer is running NetBackup 7.0.1 or later. If this computer is running a version of
NetBackup that is earlier than 7.0.1, of if the previous attempt was unsuccessful, then
the connections try vnetd. The first two settings are ignored.

$ bptestbpcd -host dolphin

1 0 1
[Link]:40414 -> [Link]:13724
[Link]:40416 -> [Link]:13724

Example 3 CONNECT_OPTIONS = perch 0 1 2

In this example:

■ Connections to daemons on perch must use the daemon port numbers.

■ Call-back connections are inbound to vnetd on this computer.
■ The source ports for all connections are bound from the reserved port number
range.
 Configuring Host Properties 298
Configuration options for NetBackup servers

Table 3-84 CONNECT_OPTIONS information (continued)

Usage Description

Example 4 CONNECT_OPTIONS = trout 1 1 2

In this example:

■ Connections to daemons on trout must use the daemon port numbers.

■ Call-back connections are inbound to vnetd on this computer.
■ The source ports for all connections are bound from the non-reserved port number
range.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Click Master
Console property Servers, Media Servers, Clients > Double-click on server > Firewall.

See “Firewall properties” on page 151.

DEFAULT_CONNECT_OPTIONS option for NetBackup servers and

clients
The DEFAULT_CONNECT_OPTIONS option specifies the default values for the
CONNECT_OPTIONS configuration option. If a host name is not specified in any
CONNECT_OPTIONS option, the value from the DEFAULT_CONNECT_OPTIONS option is
used.
See “CONNECT_OPTIONS option for NetBackup servers and clients” on page 294.

Table 3-85 DEFAULT_CONNECT_OPTIONS information

Usage Description

Where to use On NetBackup master servers, media servers, or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

DEFAULT_CONNECT_OPTIONS = [ 0 | 1 ][ 0 | 1 ][ 0 | 1 | 2 ]

The default value is 0 1 0.

This option should appear only once in the configuration file.

 Configuring Host Properties 299
Configuration options for NetBackup servers

Table 3-85 DEFAULT_CONNECT_OPTIONS information (continued)

Usage Description

The first setting indicates the type of port to use as the source port when connecting
to service daemons on a destination host. It also indicates the type of server port if
using the traditional call-back method.

0 = Connections on this computer should use a reserved port number. They are selected
from the CLIENT_RESERVED_PORT_WINDOW range for source ports and from the
SERVER_RESERVED_PORT_WINDOW range if using the traditional call-back method.

1 = Connections on this computer should use a non-reserved port number. Connections

are selected from the CLIENT_PORT_WINDOW range for source ports and from the
SERVER_PORT_WINDOW range if using the traditional call-back method. If this option
is selected and the destination host is earlier than NetBackup 7.1, enable Allow non
reserved ports for the selected host. See the Universal Settings dialog box under
Host Properties > Media Servers.

See “Universal Settings properties” on page 258.

The second setting indicates the call-back method to use. (This setting applies if
configured to use the daemon port or if bpcd cannot be reached using ports 1556 or
13724.)

0 = Use the traditional call-back method. The destination host connects back to a
random port number that this computer has selected from the
SERVER_RESERVED_PORT_WINDOW range, or the SERVER_PORT_WINDOW range as
determined by the first setting.

1 = Use the vnetd no call-back method. Connect to vnetd instead of a random port.
If this computer is NetBackup 7.0.1 or later, attempt to connect to port 1556 before
attempting to connect to vnetd. The connection is outbound to the destination host if
the third setting is 0 or 1. The connection is inbound if the third setting is 2.
 Configuring Host Properties 300
Configuration options for NetBackup servers

Table 3-85 DEFAULT_CONNECT_OPTIONS information (continued)

Usage Description

The third setting affects which destination port number to use when attempting
connections to daemon services on the destination host.

0 = Use vnetd to connect to a daemon on the destination host if possible, otherwise

connect by using the traditional port number of the daemon. If this computer is
NetBackup 7.0.1 or later, attempt to connect to port 1556 before attempting to connect
to vnetd. If bpcd is reachable through port 1556 or vnetd, then the first two settings
are ignored and all connections are outbound and use non-reserved ports.

1 = Connect to a daemon on the destination host by using vnetd. If this computer is

NetBackup 7.0.1 or later, attempt to connect to port 1556 before attempting to connect
to vnetd. The traditional port number of the daemon will not be used if the connection
cannot be established using port 1556 or vnetd. If bpcd is reachable through port
1556 or vnetd, then the first two settings are ignored and all connections are outbound
and use non-reserved ports.

2 = Connect to a daemon on the destination host by using the traditional port number
of the daemon only. The first setting is used to determine the port range and the second
setting is used to determine the call-back method.

Equivalent Administration NetBackup Management > Host Properties > Click Master Servers, Media Servers,
Console property Clients > Double-click on server > Firewall.

See “Firewall properties” on page 151.

DISABLE_JOB_LOGGING option for NetBackup servers

This option disables the logging of the job information that the NetBackup Activity
Monitor requires.

Table 3-86 DISABLE_JOB_LOGGING information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 301
Configuration options for NetBackup servers

Table 3-86 DISABLE_JOB_LOGGING information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

DISABLE_JOB_LOGGING

The default is that this option is not present in the configuration file and that job logging
occurs.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Media > Enable job logging.

See “Media properties” on page 189.

DISABLE_STANDALONE_DRIVE_EXTENSIONS option for

NetBackup servers
This option disables the nonrobotic drive operations. During a backup, NetBackup
automatically attempts to use standalone volumes in nonrobotic drives.

Table 3-87 DISABLE_STANDALONE_DRIVE_EXTENSIONS information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbemmcmd command to change the option. For example:

nbemmcmd -changesetting -DISABLE_STANDALONE_DRIVE_EXTENSIONS no

For information about these commands, see the NetBackup Commands Reference
Guide.

This option should appear only once in the configuration file.

Example The following command enables nonrobotic drive operations.

nbemmcmd -changesetting -DISABLE_STANDALONE_DRIVE_EXTENSIONS no

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Media > Enable standalone drive extension. The default is that this option
is enabled.

See “Media properties” on page 189.

 Configuring Host Properties 302
Configuration options for NetBackup servers

DISALLOW_BACKUPS_SPANNING_MEDIA option for NetBackup

servers
This option prevents backups from spanning media.

Table 3-88 DISALLOW_BACKUPS_SPANNING_MEDIA information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

DISALLOW_BACKUPS_SPANNING_MEDIA

The default is that the entry is not present in the configuration file and backups are
allowed to span media.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Media > Allow backups to span tape media.

See “Media properties” on page 189.

DISALLOW_CLIENT_LIST_RESTORE option for NetBackup servers

This option denies the list and restore requests for all clients. When this option is
present, clients cannot list or restore any files that they have backed up through
this master server.

Table 3-89 DISALLOW_CLIENT_LIST_RESTORE information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 303
Configuration options for NetBackup servers

Table 3-89 DISALLOW_CLIENT_LIST_RESTORE information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

DISALLOW_CLIENT_LIST_RESTORE

The default is that the entry is not present in the configuration file and clients can list
and restore their files.
Note: Override the DISALLOW_CLIENT_LIST_RESTORE option for individual clients
by changing their list_restore setting.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Client Attributes > Allow Client Restore.

See “Client Attributes properties” on page 92.

DISALLOW_CLIENT_RESTORE option for NetBackup servers

This option denies the restore requests for all clients. When this option is present,
clients cannot restore the files that they have backed up through this master server.

Table 3-90 DISALLOW_CLIENT_RESTORE information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

DISALLOW_CLIENT_RESTORE

The default is that the entry is not present in the configuration file and clients can restore
their files.
Note: To override the DISALLOW_CLIENT_RESTORE option for individual clients,
change their list_restore setting.
 Configuring Host Properties 304
Configuration options for NetBackup servers

Table 3-90 DISALLOW_CLIENT_RESTORE information (continued)

Usage Description

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Client Attributes > Allow Client Browse.

See “Client Attributes properties” on page 92.

EMMSERVER option for NetBackup servers

In releases before NetBackup 7.6, EMMSERVER indicated the master or the media
server that acted as the Enterprise Media Manager server for one or more master
servers.
Support for remote-EMM and shared-EMM server configurations was withdrawn in
7.6. In a remote- or shared-EMM server configuration, the NetBackup relational
database (NBDB), the Enterprise Media Manager (EMM), and the Resource Broker
(RB) have been moved to a server that is not the master server. Customers who
currently use this option should contact Veritas Support. Support engages Veritas
Engineering to review the options to disengage this configuration.

Table 3-91 EMMSERVER information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

EMMSERVER = server_name

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

See “Moving the NetBackup database from one host to another” on page 971.
 Configuring Host Properties 305
Configuration options for NetBackup servers

FAILOVER_RESTORE_MEDIA_SERVERS option for NetBackup

servers
This option specifies that an automatic failover media server be used if a server is
temporarily inaccessible for a restore. This failover does not require administrator
intervention.

Table 3-92 FAILOVER_RESTORE_MEDIA_SERVERS information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

FAILOVER_RESTORE_MEDIA_SERVERS = failed_host host1 host2 ...

hostN

■ failed_host is the server that is not operational.

■ host1 ... hostN are the servers that provide failover capabilities.

The default is that NetBackup does not perform automatic failover.

When automatic failover is necessary for a server, NetBackup searches from left to
right through the associated FAILOVER_RESTORE_MEDIA_SERVERS list. It stops when
it finds one that is eligible to perform the restore.
Note: The configuration file can contain multiple
FAILOVER_RESTORE_MEDIA_SERVERS entries and each entry can list multiple servers.
However, a NetBackup server can be a failed_host in only one option.

After a FAILOVER_RESTORE_MEDIA_SERVERS option is added, stop and restart the

NetBackup Request daemon on the master server where you plan to change the
configuration.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Restore Failover.

See “Restore Failover properties” on page 225.

FORCE_RESTORE_MEDIA_SERVER option for NetBackup servers

This option forces the restore to go to a specific server, regardless of where the
files were backed up.
 Configuring Host Properties 306
Configuration options for NetBackup servers

Table 3-93 FORCE_RESTORE_MEDIA_SERVER information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

FORCE_RESTORE_MEDIA_SERVER = from_host to_host

Where from_host is the server that performed the original backup and to_host is the
server to use for the restore.

Stop and restart the NetBackup Request daemon on the master server after adding
the FORCE_RESTORE_MEDIA_SERVER option. Physically move the media to to_host
before attempting a restore. Update the Media Manager volume database to reflect
the move.

This setting applies to all storage units on the original server. Restores for any storage
unit on from_host go to to_host. To revert to the original configuration for future restores,
delete the option.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > General Server > Media Host Override.

See “General Server properties” on page 155.

GENERATE_ENGLISH_LOGS option for NetBackup servers and

clients
This option enables the generation of an English error log, and English trace logs
for the bparchive, bpbackup, bpduplicate, bpimport, and bprestore commands.
This option is useful to support personnel to assist in distributed environments
where different locales result in logs that contain various languages.
An English text error log (indicated by the suffix _en) is created in the following
directory:
■ On Windows: Install_path\Veritas\NetBackup\db\error
■ On UNIX: /usr/openv/netbackup/db/error
 Configuring Host Properties 307
Configuration options for NetBackup servers

Table 3-94 GENERATE_ENGLISH_LOGS information

Usage Description

Where to use On NetBackup master servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

GENERATE_ENGLISH_LOGS

This entry should appear only once in the configuration file.

Setting the GENERATE_ENGLISH_LOGS option also forces the -en argument on the
execution of the following commands when the progress log is specified (-L):
bparchive, bpbackup, bpduplicate, bpimport, and bprestore.

The suffix _en indicates the English text progress log.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

INCOMPLETE_JOB_CLEAN_INTERVAL option for NetBackup

servers and clients
This option indicates the number of days a failed restore job can remain in the
incomplete state before it is moved to the done state.

Table 3-95 INCOMPLETE_JOB_CLEAN_INTERVAL information

Usage Description

Where to use On NetBackup master servers or clients.

 Configuring Host Properties 308
Configuration options for NetBackup servers

Table 3-95 INCOMPLETE_JOB_CLEAN_INTERVAL information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

INCOMPLETE_JOB_CLEAN_INTERVAL = number_of_days

The default is 7 days.

Where x is a value between 0 and 365. A value of 0 indicates that failed, incomplete
jobs are never automatically moved to the done state.

This entry should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Clients >
Console property Double-click on server > Clean-up > Move restore job from incomplete state to
done state.

See “Clean-up properties” on page 88.

INITIAL_BROWSE_SEARCH_LIMIT option for NetBackup servers

and clients
This option specifies the number of days back that NetBackup searches for files to
restore.

Table 3-96 INITIAL_BROWSE_SEARCH_LIMIT information

Usage Description

Where to use On NetBackup master servers or clients.

 Configuring Host Properties 309
Configuration options for NetBackup servers

Table 3-96 INITIAL_BROWSE_SEARCH_LIMIT information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

INITIAL_BROWSE_SEARCH_LIMIT = number_of_days

The default is that NetBackup includes files from the time of the last full backup through
the latest backup for the client. If the client belongs to more than one policy the browse
starts with the earliest of the set of last full backups.

This entry should appear only once in the configuration file.

When this option is specified on a UNIX client, it applies only to that client. The option
can reduce the size of the Search window from what is specified on the server (the
client setting cannot make the window larger).

Example The following example limits the browse range to the seven days before the current
date.

INITIAL_BROWSE_SEARCH_LIMIT = 7

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Universal Settings > Browse timeframe for restores.

See “Universal Settings properties” on page 258.

IP_ADDRESS_FAMILY option for NetBackup servers

The IP_ADDRESS_FAMILY option indicates whether NetBackup on this host supports
only IPv4 or both IPv4 and IPv6.
If any of the SERVER entries do not support IPv4, NetBackup uses the setting that
indicates both IPv4 and IPv6.

Table 3-97 IP_ADDRESS_FAMILY information

Usage Description

Where to use On NetBackup servers or clients.

 Configuring Host Properties 310
Configuration options for NetBackup servers

Table 3-97 IP_ADDRESS_FAMILY information (continued)

Usage Description

How to use On the hosts that use both IPv4 and IPv6, use this option to indicate which address
family to use.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

IP_ADDRESS_FAMILY = AF_INET | AF_UNSPEC

AF_INET indicates that the host supports only IPv4.

AF_UNSPEC indicates that the host supports both IPv4 and IPv6.

This entry should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Network Settings.

See “Network Settings properties” on page 199.

JOB_PRIORITY option for NetBackup servers and clients

Use this option to set the priority for a job type.

Table 3-98 JOB_PRIORITY information

Usage Description

Where to use On NetBackup master servers or clients.

 Configuring Host Properties 311
Configuration options for NetBackup servers

Table 3-98 JOB_PRIORITY information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

JOB_PRIORITY = P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11

P12 P13 P14 P15 P16 P17 P18 P19 P20 P21 P22 P23 P24

Variables P1, P2, and so on indicate the priority for each backup type.

Table 3-99 shows the default priority values.

The actual default values for the option appear as follows:

JOB_PRIORITY = 0 0 90000 90000 90000 90000 85000 85000

80000 80000 80000 80000 75000 75000 70000 70000 50000
50000 0 0 0 0 0 0

This entry should appear only once in the configuration file.

Example To give backup jobs a priority of 50000 and duplication jobs a priority of 30000, change
the JOB_PRIORITY entry as follows:

JOB_PRIORITY = 50000 0 90000 90000 90000 90000 85000 85000

80000 80000 80000 80000 75000 75000 70000 70000 30000
50000 0 0 0 0 0 0

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Clients >
Console property Double-click on server > Default Job Priorities > Job Priority.

See “Default Job Priorities properties” on page 121.

Table 3-99 lists the order of the job types and the various job type defaults.

Table 3-99 Default job type priorities

Field Represents this action Default

P1 Performing a backup 0

P2 Performing a database backup (a catalog backup) 0

P3 Performing a restore 90000

P4 Recovering a catalog 90000

 Configuring Host Properties 312
Configuration options for NetBackup servers

Table 3-99 Default job type priorities (continued)

Field Represents this action Default

P5 Performing a staging operation 90000

P6 Performing the duplication jobs that Vault starts 90000

P7 Cleaning up images 85000

P8 Importing images 85000

P9 Requesting tapes 80000

P10 Cleaning a tape 80000

P11 Tape formatting 80000

P12 Performing device diagnostics 80000

P13 Verifying an image 75000

P14 Running a media contents report 75000

P15 Labeling tape media 70000

P16 Erasing media 70000

P17 Running a duplication job 50000

P18 Performing an inventory 50000

P19 This field is not currently in use 0

P20 This field is not currently in use 0

P21 This field is not currently in use 0

P22 This field is not currently in use 0

P23 This field is not currently in use 0

P24 This field is not currently in use 0

LIMIT_BANDWIDTH option for NetBackup servers

This option specifies a limit for the network bandwidth that NetBackup clients use
on a network. The actual limiting occurs on the client side of the backup connection.
This option limits only backups. Restores are unaffected. The default is that the
bandwidth is not limited.
 Configuring Host Properties 313
Configuration options for NetBackup servers

Note: LIMIT_BANDWIDTH applies only to IPv4 networks. Use the

THROTTLE_BANDWIDTH option to limit IPv6 networks.

See “Throttle Bandwidth properties” on page 254.

MAX_LOGFILE_SIZE option for NetBackup servers and clients for

legacy logging
The MAX_LOGFILE_SIZE option specifies the maximum size that you want to set for
a log file. When the log file size in NetBackup matches the MAX_LOGFILE_SIZE
setting, the next logs are stored in a new log file.
See “About robust logging” on page 271.

Table 3-100 MAX_LOGFILE_SIZE information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig (or bpgetconfig) and the nbsetconfig (or bpsetconfig)
commands to view, add, or change the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Initially, the [Link] file does not contain MAX_LOGFILE_SIZE entry. In this case,
the parameter is set to its default value, that is 50 MB.
To set it to a different value, update the [Link] file using the nbsetconfig
command.

Use the following format to set MAX_LOGFILE_SIZE to a new value in the [Link]
file:

MAX_LOGFILE_SIZE = X

'X' indicates maximum size of a NetBackup log file in MB.

Note: MAX_LOGFILE_SIZE should be set to an integer number, which should be
greater than '0'. If you have set MAX_LOGFILE_SIZE to an invalid value such as 0 or
-100, it is automatically set to the default value.

This entry should appear only once in the configuration file.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property
 Configuring Host Properties 314
Configuration options for NetBackup servers

MAX_NUM_LOGFILES option for NetBackup servers and clients for

legacy logging
The MAX_NUM_LOGFILES option specifies the maximum number of log files that you
want to be retained in a NetBackup log directory. When the number of log files in
the directory matches the MAX_NUM_LOGFILES setting, the oldest log file is deleted.
See “About robust logging” on page 271.

Table 3-101 MAX_NUM_LOGFILES information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig (or bpgetconfig) and the nbsetconfig (or bpsetconfig)
commands to view, add, or change the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Initially, the [Link] file does not contain MAX_NUM_LOGFILES entry. In this case,
the parameter is set to its default value, which is infinite.

To set it to a different value, update the [Link] file using the nbsetconfig
command.

Use the following format to set MAX_NUM_LOGFILES to a new value in the [Link]
file:

MAX_NUM_LOGFILES = X

'X' indicates maximum number of NetBackup log files that are created in a log directory.

MAX_NUM_LOGFILES should be set to a number that should be greater than one (1).
If you have set MAX_NUM_LOGFILES to an invalid value such as 0 or 1, it is automatically
set to the default value, which is infinite. However, in the [Link] file, the
MAX_NUM_LOGFILES entry appears as follows:

MAX_NUM_LOGFILES = 0

Zero (0) indicates an infinite value.

This entry should appear only once in the configuration file.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property
 Configuring Host Properties 315
Configuration options for NetBackup servers

KEEP_LOGS_SIZE_GB for NetBackup servers and clients

The KEEP_LOGS_SIZE_GB option specifies the size of the NetBackup logs that you
want to retain. When the NetBackup log size grows up to this configuration value,
the older logs are deleted.

Table 3-102 KEEP_LOGS_SIZE_GB information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view,
add, or change the option.

For information about these commands, see the NetBackup

Commands Reference Guide.

Initially, the [Link] file does not contain KEEP_LOGS_SIZE_GB

entry.

Enable the Keep logs up to GB option in the Logging dialog box

on the NetBackup Administration Console to set the log retention
in GB. A corresponding entry is added in the [Link] file as follows:

KEEP_LOGS_SIZE_GB = 25

If you disable the Keep logs up to GB option, the [Link] file

shows the corresponding entry as follows:

KEEP_LOGS_SIZE_GB = 0

To set it to a different value, update the [Link] file using the

nbsetconfig command.

Use the following format to set KEEP_LOGS_SIZE_GB to a new

value in the [Link] file:

KEEP_LOGS_SIZE_GB = X

'X' indicates the log size in GB.

Note: For NetBackup servers, the recommended value for the
KEEP_LOGS_SIZE_GB option is 25 GB or greater.

For NetBackup clients, the recommended value for the

KEEP_LOGS_SIZE_GB option is 5 GB or greater.

This entry should appear only once in the [Link] configuration

file.
 Configuring Host Properties 316
Configuration options for NetBackup servers

Table 3-102 KEEP_LOGS_SIZE_GB information (continued)

Usage Description

Equivalent NetBackup Management > Host Properties > Master Servers or

Administration Clients > Double-click on server > Logging > Keep logs up to GB.
Console property
See “Logging properties” on page 170.

ENABLE_CRITICAL_PROCESS_LOGGING
The ENABLE_CRITICAL_PROCESS_LOGGING option lets you automatically log critical
NetBackup processes. Log directories for the critical processes are created and
logging begins when this option is enabled in the Logging host properties.

Table 3-103 ENABLE_CRITICAL_PROCESS_LOGGING information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view
the option.

For information about these commands, see the NetBackup

Commands Reference Guide.

Initially, the [Link] file does not contain

ENABLE_CRITICAL_PROCESS_LOGGING entry.

After logging for critical processes is enabled, a corresponding

entry is added in the [Link] file as follows:

ENABLE_CRITICAL_PROCESS_LOGGING = YES

Note: You should not modify the

ENABLE_CRITICAL_PROCESS_LOGGING parameter. To disable
the logging for critical processes, you need to modify their logging
levels.

See “Disabling the logging of NetBackup processes” on page 180.

Equivalent NetBackup Management > Host Properties > Click Master

Administration Console Servers, Media Servers, Clients > Double-click on server >
property Logging > Logging for critical processes.

See “Logging properties” on page 170.

 Configuring Host Properties 317
Configuration options for NetBackup servers

MEDIA_UNMOUNT_DELAY option for NetBackup servers

When MEDIA_UNMOUNT_DELAY is specified, the media unload is delayed for the
specified number of seconds after the requested operation has completed. (Applies
only to user operations.)

Table 3-104 MEDIA_UNMOUNT_DELAY information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

MEDIA_UNMOUNT_DELAY = seconds

The default is a media mount delay time of 180 seconds.

This entry should appear only once in the configuration file.

Example The delay is set to 120 seconds in the following example:

MEDIA_UNMOUNT_DELAY = 120

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Media > Media unmount delay.

See “Media properties” on page 189.

MEDIA_REQUEST_DELAY option for NetBackup servers

This option specifies the number of seconds that NetBackup waits for a non-robotic
drive to become ready.

Table 3-105 MEDIA_REQUEST_DELAY information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 318
Configuration options for NetBackup servers

Table 3-105 MEDIA_REQUEST_DELAY information (continued)

Usage Description

How to use Change the MEDIA_REQUEST_DELAY by using the nbemmcmd command.

For information about these commands, see the NetBackup Commands Reference
Guide.

The default is that NetBackup does not wait for non-robotic drives to become ready.

This option should appear only once in the configuration file.

Example The following command indicates to NetBackup to wait 150 seconds for a non-robotic
drive to become ready for use.

nbemmcmd -changesetting -MEDIA_REQUEST_DELAY 150

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Media > Media request delay.

See “Media properties” on page 189.

MEDIA_SERVER option for NetBackup servers

This option is similar to the SERVER option.
A host that is listed as a MEDIA_SERVER can back up and restore clients. However,
if the host is not specified as a SERVER, the host has limited administrative
capabilities.

Table 3-106 MEDIA_SERVER information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

MEDIA_SERVER = media_server_name

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Servers > Media Servers.

See “Servers properties” on page 236.

 Configuring Host Properties 319
Configuration options for NetBackup servers

MPX_RESTORE_DELAY option for NetBackup servers

This option applies to multiplexed restores. The MPX_RESTORE_DELAY specifies how
long the server waits for restore requests of files and raw partitions. In this case,
the option applies to the files and raw partitions in a set of multiplexed images on
the same tape. All of the restore requests that are received within the delay period
are included in the same restore operation (one pass of the tape).

Table 3-107 MPX_RESTORE_DELAY information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

MPX_RESTORE_DELAY = seconds

The default is 30 seconds.

This option should appear only once in the configuration file.

Example The following example configures a server to wait 15 minutes.

MPX_RESTORE_DELAY = 900

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > General Server > Delay on multiplexed restores.

See “General Server properties” on page 155.

MUST_USE_LOCAL_DRIVE option for NetBackup servers

This option instructs NetBackup that if the client is also a media server and this
option is present, backups for this client must occur on a local drive. If all drives are
down, another may be used. If the client is not a media server, this option has no
effect.

Table 3-108 MUST_USE_LOCAL_DRIVE information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 320
Configuration options for NetBackup servers

Table 3-108 MUST_USE_LOCAL_DRIVE information (continued)

Usage Description

How to use Use the nbemmcmd command to change the option. For example:

nbemmcmd -changesetting -MUST_USE_LOCAL_DRIVE yes

For information about these commands, see the NetBackup Commands Reference
Guide.

This option should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > General Server > Must use local drive.

See “General Server properties” on page 155.

NBRNTD_IDLE_TIMEOUT option for NetBackup servers

The NBRNTD_IDLE_TIMEOUT option specifies the number of seconds to wait before
the Remote Network Transport Service (nbrntd) shuts itself down. The Remote
Network Transport Service provides resilient network connections. After it is shut
down, NetBackup must restart the service if a new resilient connection for backups
or restores is required.

Table 3-109 NBRNTD_IDLE_TIMEOUT information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

NBRNTD_IDLE_TIMEOUT = seconds

The default timeout is 300 seconds (five minutes).

By default, this entry is not present in the configuration file.

Example In the following example, the Remote Network Transport Service shuts off after 15
minutes.

NBRNTD_IDLE_TIMEOUT = 900
 Configuring Host Properties 321
Configuration options for NetBackup servers

See “RESILIENT_NETWORK option for NetBackup master servers and clients”

on page 327.

PREFERRED_NETWORK option for NetBackup servers

The PREFERRED_NETWORK option replaces the REQUIRED_INTERFACE and
REQUIRED_NETWORK entries.

The PREFERRED_NETWORK option is not needed in an environment if NetBackup is

configured with appropriate host names. The operating system must resolve to the
correct IP addresses and then route the addresses correctly.
When external constraints prevent the environment from being corrected,
PREFERRED_NETWORK entries can be useful in the following situations:

■ To prevent NetBackup from connecting to specific destination addresses.

■ To cause NetBackup to connect only to specific destination addresses.
■ To request a subset of local interfaces for source binding when outbound
connections are made.

Table 3-110 PREFERRED_NETWORK information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

The option uses the following syntax:

PREFERRED_NETWORK = target[/subnet] directive source[/subnet]

 Configuring Host Properties 322
Configuration options for NetBackup servers

Table 3-110 PREFERRED_NETWORK information (continued)

Usage Description

The target[/subnet] is a host name or range of addresses to be compared to the

prospective source or destination addresses being evaluated. The following are
examples of how to indicate a target or a subnet:

■ A host name: [Link]

■ An IP address: [Link]
■ A network with subnet: [Link]/21
■ Any IPv4 address: [Link]
■ Any IPv6 address: 0::0
■ Any address: 0/0

Note: A host or a network name that cannot resolve causes the target to be ignored.
However, any associated source is added to the source binding list.

The directive (MATCH, ONLY, or PROHIBITED) determines how the target is

compared to the source or the destination address that is under evaluation.

■ MATCH
This directive applies to destination addresses. If the address being evaluated
matches the target, then the address is immediately selected to be used and
evaluation stops. If a target is not matched, evaluation continues with the next
entry.
■ ONLY
This directive applies to destination addresses. If the address under evaluation
does not match a target, it is not used and evaluation stops for this address. If
the destination is the only potential destination, the connection is not attempted. If
there is an additional potential destination, it is evaluated starting over with the first
entry.
■ PROHIBITED
The target applies to both the source and the destination addresses. If a source
is specified, it is ignored and the target is still prohibited.
If the matched address is a destination address, evaluation stops. If the matched
address was the only potential destination, no connection is attempted. If there are
additional potential destinations, they are evaluated starting over with the first entry.
If the matched address is a source address, it is removed from the binding list. If
source entries exist, the shortened binding list may not be used. On some
platforms, prohibiting a local interface may cause unexpected results when
NetBackup connects to remote hosts. Prohibiting a local interface does not affect
the connections that are internal to the host.
 Configuring Host Properties 323
Configuration options for NetBackup servers

Table 3-110 PREFERRED_NETWORK information (continued)

Usage Description

Indicating a source[/subnet] is optional. This is a host name or IP address range

that is requested to be used as the local interface for outbound connection to addresses
in target. The source applies to the directives ONLY and MATCH, but not to the
directive PROHIBITED.
Notes:

■ The operating system may not honor the source request.

■ NetBackup does not request a source which has already been PROHIBITED.
■ A host or a network name that cannot be resolved is ignored, but the evaluation
status of the target is still used.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Preferred Network.

See “Preferred Network properties” on page 204.

The following Support document contains more information about using the
PREFERRED_NETWORK option:

[Link]

Examples of the PROHIBITED directive

■ An example that prevents the host from using IPv4 addresses:

PREFERRED_NETWORK = [Link] PROHIBITED

■ An example that prevents the host from using IPv6 addresses:

PREFERRED_NETWORK = 0::0 PROHIBITED

■ This example prevents the host from using the address of the production_server:

PREFERRED_NETWORK = production_server PROHIBITED

■ This example prevents NetBackup from using any address between [Link]
and [Link] as the source or destination for a connection. If it matches
a local interface, NetBackup provides an ordered list of the remaining interfaces
as the source binding list for the outbound interface when other entries do not
specify a source. The operating system may always use the first one in the list
instead of using the network routing tables to select the best one.

PREFERRED_NETWORK = [Link]/16 PROHIBITED

 Configuring Host Properties 324
Configuration options for NetBackup servers

Examples of the ONLY directive

■ This example instructs the host to use only IPv6 addresses in that subnet range:

PREFERRED_NETWORK = [Link]/48 ONLY

■ This example prevents NetBackup from connecting to any destination address

outside the range of [Link] to [Link]. The entry does not affect
outbound interface selection.

PREFERRED_NETWORK = [Link]/24 ONLY

■ This example prevents NetBackup from connecting to any destination address

outside the range of [Link] to [Link]. The entry requests that the
operating system use [Link] as the outbound interface.

PREFERRED_NETWORK = [Link]/24 ONLY [Link]

Examples of the MATCH directive

■ This example instructs the host to use the interface IPs of Host_A for all IPv4
and IPv6 addresses. The entry can appear multiple times in the configuration
file.

PREFERRED_NETWORK = 0/0 MATCH Host_A

■ This example allows connectivity to the host names that resolve to [Link] to
[Link]. The entry does not affect outbound interface selection:

PREFERRED_NETWORK = [Link]/16 MATCH

■ This example allows connectivity to the host name that resolves to [Link],
and requests that the operating system use [Link] as the outbound
interface:

PREFERRED_NETWORK = [Link] MATCH [Link]

RANDOM _PORTS option for NetBackup servers and clients

This option specifies whether NetBackup chooses port numbers randomly or
sequentially when it requires one for communication with NetBackup on other
computers.
 Configuring Host Properties 325
Configuration options for NetBackup servers

Table 3-111 RANDOM _PORTS information

Usage Description

Where to use On NetBackup master servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

■ If RANDOM_PORTS = YES (default), NetBackup chooses port numbers randomly

from those that are free in the allowed range. For example, if the range is from 1024
through 5000, it chooses randomly from the numbers in this range.
■ If RANDOM_PORTS = NO, NetBackup chooses numbers sequentially, starting with
the highest number available in the allowed range. For example, if the range is from
1024 through 5000, NetBackup chooses 5000 (if the number is available). If 5000
is not available, port 4999 is chosen.

By default, this option is not present in the configuration file and NetBackup uses the
random method for selecting port numbers.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Port Ranges > Use random port assignments.

See “Port Ranges properties” on page 201.

RE_READ_INTERVAL option for NetBackup servers

The RE_READ_INTERVAL option determines how often NetBackup checks disk storage
units for available capacity.

Table 3-112 RE_READ_INTERVAL information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

RE_READ_INTERVAL = seconds

The default is 300 seconds (5 minutes).

This entry should appear only once in the configuration file.

 Configuring Host Properties 326
Configuration options for NetBackup servers

Table 3-112 RE_READ_INTERVAL information (continued)

Usage Description

Example The reread interval is changed to 15 minutes in the following example:

RE_READ_INTERVAL = 900

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > General Server > Check the capacity of disk storage units.

See “General Server properties” on page 155.

REQUIRED_NETWORK option for NetBackup servers

The REQUIRED_NETWORK option specifies the required route for backup traffic in an
environment where the network traffic is segregated.
For example, an environment can contain a production network at [Link]
and a backup network at [Link].

Table 3-113 REQUIRED_NETWORK information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

REQUIRED_NETWORK = IP_address

This entry should appear only once in the configuration file.

Note: If the variable is set and the network is not available, all connections fail and
no backups are performed.

Example The required network is set to [Link] in the following example:

REQUIRED_NETWORK = [Link]

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Preferred Network > Only.

See “Preferred Network properties” on page 204.

 Configuring Host Properties 327
Configuration options for NetBackup servers

RESILIENT_NETWORK option for NetBackup master servers and

clients
The RESILIENT_NETWORK option specifies the computers that should use a resilient
connection for backups and restores.

Table 3-114 RESILIENT_NETWORK information

Usage Description

Where to use On NetBackup master servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use any of the following formats:

RESILIENT_NETWORK = hostname ON|OFF

RESILIENT_NETWORK = ip_address ON|OFF

RESILIENT_NETWORK = network address/network_mask ON|OFF

You can mix IPv4 addresses and ranges with IPv6 addresses and subnets.

By default, RESILIENT_NETWORK is not present in the configuration file.

Examples The following are examples of valid forms for this entry:

RESILIENT_NETWORK = [Link] ON

RESILIENT_NETWORK = [Link] ON

RESILIENT_NETWORK = [Link]/26 OFF

RESILIENT_NETWORK = [Link] ON

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Clients >
Console property Double-click on server > Resilient Network.

See “Specifying resilient connections” on page 221.

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

See “NBRNTD_IDLE_TIMEOUT option for NetBackup servers” on page 320.

RESUME_ORIG_DUP_ON_OPT_DUP_FAIL option for NetBackup

servers
The RESUME_ORIG_DUP_ON_OPT_DUP_FAIL option specifies that NetBackup should
perform normal duplication if an OpenStorage optimized duplication fails.

Table 3-115 RESUME_ORIG_DUP_ON_OPT_DUP_FAIL information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE | FALSE

By default, this entry is not present and NetBackup does not perform normal duplication
when an optimized duplication fails.

This entry should appear only once in the configuration file.

Equivalent Administration No equivalent exists in the NetBackup Administration Console host properties.
Console property

REVERSE_NAME_LOOKUP option for NetBackup servers and

clients
This option lets administrators allow, restrict, or prohibit reverse host name lookup.

Table 3-116 REVERSE_NAME_LOOKUP information

Usage Description

Where to use On NetBackup servers or clients.

 Configuring Host Properties 329
Configuration options for NetBackup servers

Table 3-116 REVERSE_NAME_LOOKUP information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

REVERSE_NAME_LOOKUP = ALLOWED | RESTRICTED | PROHIBITED

This entry should appear only once in the configuration file.

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Clients >
Console property Double-click on server > Network Settings > Reverse Host Name Lookup.

See “Network Settings properties” on page 199.

SERVER option for NetBackup servers

The first SERVER option in the [Link] file must point to the master server where
the [Link] option resides. During installation, SERVER is automatically set to the
name of the system where the NetBackup master server software is installed.

Table 3-117 SERVER information

Usage Description

Where to use On NetBackup master servers and media servers.

Note: For a Fibre Transport (FT) media server that has multiple network interfaces
for VLANs, ensure that the FT server’s primary host name appears before any other
interface names for that FT media server host.

For more information, see the NetBackup SAN Client and Fibre Transport Guide.
 Configuring Host Properties 330
Configuration options for NetBackup servers

Table 3-117 SERVER information (continued)

Usage Description

How to use An entry for the SERVER option must be present in the configuration file on all NetBackup
servers and clients. It is the only required NetBackup option. This option is not used
in $HOME/[Link] files on a client.

Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.
Note: This topic discusses the [Link] entries on the server. However, note that
every SERVER option in a client [Link] file must be a NetBackup master or media
server. That is, each system that is listed as a SERVER must have either NetBackup
master or media server software installed. The client service on some clients cannot
be started if the client name is incorrectly listed as a server.

If you configure NetBackup media servers for a master server, the [Link] file on
the master server must have a SERVER entry or MEDIA_SERVER entry for each. As
previously mentioned, the first SERVER entry in the list designates the master server
itself. The SERVER entry or the MEDIA_SERVER entries should be added after the first,
self-referencing option.

A NetBackup master server can be backed up as a NetBackup client by the servers

that belong to another cluster. In that case the [Link] file on the master server
should have SERVER entries for those servers as well.
 Configuring Host Properties 331
Configuration options for NetBackup servers

Table 3-117 SERVER information (continued)

Usage Description

Example The following is an example entry on a master server:

SERVER = Master_server (this master server itself)

SERVER = NB_server (master server of another cluster)

SERVER = Media_server_#1

MEDIA_SERVER = Media_server_#2

.
.
.

The first SERVER entry on all the media servers must point to the master server for
those media servers. A media server can have only one master server. However, a
media server can be backed up as a NetBackup client by the servers that belong to
another cluster, in which case the configuration file on the media server should have
SERVER entries for those servers as well.

The following is an example entry on a media server:

SERVER = Master_server (for this media server)

SERVER = NB_server (master server of another cluster)

SERVER = Media_server_#1

MEDIA_SERVER = Media_server_#2

.
.
.

The SERVER entries must be the same on all servers in a master and a media server
cluster.

If a SERVER entry is added or modified in the [Link] file on the master server, stop
and restart bprd and bpdbm so that NetBackup recognizes the change. (The NetBackup
request daemon and NetBackup database manager.)
Note: If the first SERVER entry (the master server) is modified on a media server, the
Enterprise Media Manager (EMM) also needs to be updated. To update EMM, run
nbemmcmd -updatehost to change the master server for a media server.
 Configuring Host Properties 332
Configuration options for NetBackup servers

Table 3-117 SERVER information (continued)

Usage Description

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Media Servers >
Console property Double-click on server > Servers.

See “Servers properties” on page 236.

See “FAILOVER_RESTORE_MEDIA_SERVERS option for NetBackup servers”

on page 305.

SERVER_CONNECT_TIMEOUT option for NetBackup servers

SERVER_CONNECT_TIMEOUT specifies the number of seconds that the master server
waits before it times out when it connects to a media server.

Table 3-118 SERVER_CONNECT_TIMEOUT information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

SERVER_CONNECT_TIMEOUT = seconds

The default timeout period is 30 seconds.

This entry should appear only once in the configuration file.

Example The example permits a timeout of 60 seconds:

SERVER_CONNECT_TIMEOUT = 60

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Timeouts > Server connect timeout.

See “Timeouts properties” on page 256.

SERVER_PORT_WINDOW option for NetBackup servers

The SERVER_PORT_WINDOW option specifies the range of non-reserved ports on which
NetBackup processes on this computer accept connections from NetBackup on
other computers when the inbound connection is not to a well known port. This
 Configuring Host Properties 333
Configuration options for NetBackup servers

primarily applies to bpcd call-back when vnetd is disabled in the connect options
for the remote NetBackup server or client and that host is configured for
non-reserved ports. This also applies to NDMP call-back to the media server during
remote NDMP backups.

Table 3-119 SERVER_PORT_WINDOW information

Usage Description

Where to use On NetBackup master servers or media servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

SERVER_PORT_WINDOW = start_port end_port

The default range is from 1024 through 5000.

This entry should appear only once in the configuration file.

Example The following example permits ports from 4900 through 5000:

SERVER_PORT_WINDOW = 4900 5000

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Media Servers >
Console property Double-click on server > Port Ranges > Server port window.

See “Port Ranges properties” on page 201.

SERVER_RESERVED_PORT_WINDOW option for NetBackup

servers and clients
This option specifies the range of local reserved ports on which this computer
accepts connections from NetBackup on other computers when the inbound
connection is not to a well known port. This primarily applies to bpcd call-back when
vnetd is disabled in the connect options for the remote NetBackup server or client.

The SERVER_RESERVED_PORT_WINDOW option applies when a server connects to a

client that is configured to accept only reserved ports. This option is generally not
useful on clients.
 Configuring Host Properties 334
Configuration options for NetBackup servers

Table 3-120 SERVER_RESERVED_PORT_WINDOW information

Usage Description

Where to use On NetBackup master servers or media servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

SERVER_RESERVED_PORT_WINDOW = start_port end_port

The default range is from 512 through 1023.

This entry should appear only once in the configuration file.

Example The following example permits ports from 900 through 1023:

SERVER_RESERVED_PORT_WINDOW = 900 1023

Equivalent Administration NetBackup Management > Host Properties > Master Servers or Media Servers >
Console property Double-click on server > Port Ranges > Server reserved port window.

See “Port Ranges properties” on page 201.

SKIP_RESTORE_TO_SYMLINK_DIR option for NetBackup servers

The SKIP_RESTORE_TO_SYMLINK_DIR option forces NetBackup to check all directories
on a UNIX client into which files are restored. If the file to be restored is under a
symbolically linked directory, NetBackup does not restore the file.

Table 3-121 SKIP_RESTORE_TO_SYMLINK_DIR information

Usage Description

Where to use On NetBackup master servers.

 Configuring Host Properties 335
Configuration options for NetBackup servers

Table 3-121 SKIP_RESTORE_TO_SYMLINK_DIR information (continued)

Usage Description

How to use This option should appear only once in the configuration file.

For example, if the UNIX client requests a restore for /home/user/.cshrc and
/home/user is a symbolic link, NetBackup does not restore .cshrc.

The addition of SKIP_RESTORE_TO_SYMLINK_DIR helps minimize potential security

and data loss problems if the restore is performed with root permissions. Without
SKIP_RESTORE_TO_SYMLINK_DIR in the [Link] file, NetBackup follows any
symbolically linked directories and restores files to that location.
Note: Restore job performance is reduced by using this option.

SKIP_RESTORE_TO_SYMLINK_DIR and UNLINK_ON_OVERWRITE do not affect each

other if both are specified, with one exception:
When the following options are enabled:

■ Overwrite existing files option

■ SKIP_RESTORE_TO_SYMLINK_DIR
■ UNLINK_ON_OVERWRITE

Then, when a restore job comes across a symbolic link, the link is unlinked before the
job checks, and the files and directory are restored.

For example, /home/user/ is backed up as a directory and, when restored, it is a

symbolic link to a directory.
These settings have the following outcomes:

■ With SKIP_RESTORE_TO_SYMLINK_DIR set (and Overwrite existing files

indicated), no files are restored into the directory the symbolic link points to, and
the symbolic link remains.
■ With both UNLINK_ON_OVERWRITE and SKIP_RESTORE_TO_SYMLINK_DIR (and
Overwrite existing files indicated), the symbolic link directory is unlinked, the
original directory is restored, and all files within the directory are also restored.
■ With neither option set (and Overwrite existing files indicated), NetBackup follows
the symbolic link and restore all files into the directory to which the symbolic link
points.

Equivalent Administration NetBackup Management > Host Properties > Master Servers > Double-click on
Console property server > Port Ranges > Server reserved port window.

See “Port Ranges properties” on page 201.

TELEMETRY_UPLOAD option for NetBackup servers

TELEMETRY_UPLOAD allows NetBackup to collect data about how the product is used
in a NetBackup environment. The information that Veritas receives becomes part
 Configuring Host Properties 336
Configuration options for NetBackup servers

of a continuous quality improvement program (NetBackup Product Improvement

Program) that helps Veritas understand how customers configure, deploy, and use
the NetBackup product. The data is restricted to NetBackup and OpsCenter
development at Veritas.
The telemetry collection agent runs on every NetBackup server and every OpsCenter
server. The telemetry collection agent does not run on NetBackup clients.

Table 3-122 TELEMETRY_UPLOAD information

Usage Description

Where to use On NetBackup master servers.

How to use Use the nbgetconfig and the nbsetconfig commands to view, add, or change
the option.

For information about these commands, see the NetBackup Commands Reference
Guide.

Use the following format:

TELEMETRY_UPLOAD = YES | NO

The default is YES.

This entry should appear only once in the configuration file.

Equivalent Administration During the NetBackup or OpsCenter installation process, a prompt or check box appears
Console property that asks for the users' agreement to participate in the Product Improvement Program.

THROTTLE_BANDWIDTH option for NetBackup servers

This option specifies a limit for the network bandwidth or transfer rate that NetBackup
clients use on a network. The actual limiting occurs on the client side of the backup
connection. This option limits only backups. Restores are unaffected. The default
is that the bandwidth is not limited.
While LIMIT_BANDWIDTH associates a bandwidth or transfer rate with all client IP
addresses in a range between two IP addresses, THROTTLE_BANDWIDTH is more
useful in an IPv6 environment. THROTTLE_BANDWIDTH associates a bandwidth setting
with a subnet description.
For example, the following subnet will get 400kbs bandwidth:
[Link]/64 400
 Configuring Host Properties 337
Configuration options for NetBackup servers

Table 3