Configuration Guide - High Energy Physics Group

Transcription

Quest® NetVault® Backup
version 9.1
Configuration Guide
Version: Product Number: NVG-103-9.1-EN-01
NVG-103-9.1-EN-01 05/10/13
© 2013 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in
this guide is furnished under a software license or nondisclosure agreement. This software may
be used or copied only in accordance with the terms of the applicable agreement. No part of this
guide may be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopying and recording for any purpose other than the purchaser's personal use
without the written permission of Quest Software, Inc.
The information in this document is provided in connection with Quest products. No license,
express or implied, by estoppel or otherwise, to any intellectual property right is granted by this
document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN
QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR
THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY
EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL
QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL
OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS
OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF
THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties
with respect to the accuracy or completeness of the contents of this document and reserves the
right to make changes to specifications and product descriptions at any time without notice.
Quest does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
email: [email protected]
Refer to our Web site (www.quest.com) for regional and international office information.
Patents
This product is protected by U.S. Patents # 7,814,260; 7,913,043; 7,979,650; 8,086,782;
8,145,864; 8,171,247; 8,255,654; and 8,271,755. Protected by Japanese, E.U., French and UK
patents 1615131 and 05250687.0, and German patent DE602004002858. Additional patents
pending.
Trademarks
Quest, Quest Software, the Quest Software logo, Simplicity at Work, FlashRestore, GigaOS,
and NetVault are trademarks and registered trademarks of Quest Software, Inc., and its
subsidiaries. For a complete list of Quest Software's trademarks, please see
http://www.quest.com/legal/trademarks.aspx. Other trademarks and registered trademarks are
property of their respective owners.
Table of Contents
Chapter 1: Introducing Quest NetVault Backup
•
•
•
•
•
•
•
11
Quest NetVault Backup – At a Glance .......................................................................... 11
Key Benefits .................................................................................................................... 11
Feature Summary ........................................................................................................... 12
About this Document ..................................................................................................... 13
Target Audience .............................................................................................................. 13
Recommended Additional Reading .............................................................................. 14
About Quest Software .................................................................................................... 14
- Contacting Quest Software ............................................................................................................ 14
- Quest Support ................................................................................................................................ 15
Chapter 2: Getting Started
17
• NVBU Configurator – An Overview ............................................................................... 17
• Starting NVBU Configurator .......................................................................................... 17
- Starting NVBU Configurator on Linux/UNIX ................................................................................... 17
- Starting NVBU Configurator on Mac OS X .................................................................................... 17
- Starting NVBU Configurator on Windows ...................................................................................... 18
• Remote Configurator ...................................................................................................... 19
- Starting Remote Configurator ........................................................................................................ 19
• Txtconfig .......................................................................................................................... 19
Chapter 3: Performing Common Administrative Tasks
•
•
•
•
•
•
•
•
•
21
Viewing NVBU Service Status ....................................................................................... 21
Starting and Stopping NVBU Service ........................................................................... 21
Viewing NVBU Machine Details ..................................................................................... 22
Installing Optional Plug-ins ........................................................................................... 23
Removing Plug-ins ......................................................................................................... 24
Licensing Software ......................................................................................................... 24
Viewing License Details ................................................................................................. 25
Changing NVBU Password ............................................................................................ 25
Disabling Password-Protection for NVBU Clients ....................................................... 26
4
Table of Contents
• Allowing NVBU Server to Function as Client ...............................................................26
Chapter 4: Customizing the Auditor Daemon
•
•
•
•
•
•
Auditor Daemon – An Overview .....................................................................................27
Generating Audit Logs for Failed User Requests ........................................................27
Creating a User-Defined Policy for Deleting Audit Logs .............................................28
Creating a User-Defined Schedule for Purging Audit Logs ........................................29
Disabling Automatic Purging of Audit Logs .................................................................29
Configuring Number of Active Sysop Operator Message Notifications ....................30
Chapter 5: Customizing the Device Scan Process
•
•
•
•
•
27
31
Device Scan Process – An Overview ............................................................................31
Configuring Device Type for Startup Device Scan .......................................................32
Disabling Startup Device Scan ......................................................................................32
Configuring Device Type for Post-Startup Device Scan ..............................................32
Disabling Post-Startup Device Scan .............................................................................33
Chapter 6: Customizing the Job Manager Process
35
• Job Manager – An Overview ..........................................................................................35
• Configuring Keep-Alive Rate for Job Manager .............................................................35
• Configuring “nvjobcreate” to Return Job Exit Code ...................................................36
Chapter 7: Customizing the Log Daemon
•
•
•
•
•
•
•
•
37
Log Daemon – An Overview ...........................................................................................37
Configuring Disk Space Alert Thresholds ...................................................................38
Creating a User-Defined Schedule for Disk Space Checks .........................................39
Disabling Disk Space Checks ........................................................................................39
Creating a User-Defined Policy for Deleting NVBU Logs ............................................40
Creating a User-Defined Schedule for Purging NVBU Logs .......................................41
Disabling Automatic Purging of NVBU Logs ................................................................41
Optimizing the Log Daemon ...........................................................................................42
Quest NetVault Backup
Configuration Guide
Chapter 8: Customizing the Media Manager Process
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
45
Media Manager – An Overview ...................................................................................... 45
Configuring Retention Period for Imported Backups ................................................. 46
Using Barcodes as Default Media Labels ..................................................................... 47
Setting Priority Levels for Continuation Media Requests .......................................... 47
Setting Priority Levels for Media Labeling and Blanking Requests .......................... 48
Configuring Callback Timeouts for Bulk Media Operations ....................................... 48
Setting Interval for Media Status Updates .................................................................... 49
Disabling Reuse of Read-Only Media ........................................................................... 49
Creating a User-Defined Policy for Automatic Index Compression .......................... 49
Creating a User-Defined Schedule for Index Compression ........................................ 50
Disabling Automatic Index Compression ..................................................................... 50
Configuring Minimum Disk Space for Index Decompression .................................... 50
Customizing the Diagnose Media Requests Window ................................................. 51
Customizing Device Related Settings .......................................................................... 52
Enabling Timeout for Source Media Requests ............................................................ 54
Configuring Additional Media Manager Settings ......................................................... 54
Configuring Transfer Update Frequency for Data Domain Systems ......................... 55
Configuring Timeout Interval for NVSD “Stream End” Responses ........................... 56
Configuring Media Request Weights ............................................................................ 57
Chapter 9: Customizing the Network Manager Process
•
•
•
•
•
•
•
•
•
5
59
Network Manager – An Overview .................................................................................. 59
Configuring Timeout Settings for Remote Connections ............................................ 60
Configuring Timeout for Inactive Connections ........................................................... 60
Configuring Keep-Alive Rate for Network Manager .................................................... 61
Configuring Availability Broadcast Interval ................................................................. 61
Configuring Availability Check Interval ........................................................................ 61
Disabling Availability Broadcasts ................................................................................. 62
Configuring Security Broadcast Interval ...................................................................... 63
Configuring Network Interfaces for Multihomed NVBU Systems .............................. 63
- Considerations for Multihomed NVBU Machines ........................................................................... 64
• Reducing Startup Delay ................................................................................................. 65
• Changing the Default Port for Network Manager ......................................................... 67
• Changing the Default Port for Communications Manager .......................................... 68
6
Table of Contents
Chapter 10: Customizing the Schedule Manager Process
•
•
•
•
•
•
•
•
69
Schedule Manager – An Overview .................................................................................69
Customizing NVBU Job Status Views ...........................................................................69
Creating a User-Defined Policy for Retaining Job History ..........................................70
Defining a Retention Period for Non-Recurring Job Definitions ................................71
Configuring Maximum Simultaneous Jobs ..................................................................71
Including Report Jobs in the Job Views .......................................................................71
Including Restore and Report Jobs in Policy Views ....................................................72
Configuring Job Priority .................................................................................................72
Chapter 11: Configuring Shared Memory Settings
75
• Process Manager – An Overview ...................................................................................75
• Tuning Shared Memory Allocation ................................................................................75
Chapter 12: Configuring NVBU for Firewalls
77
• Firewall Settings – An Overview ....................................................................................77
- Firewall Considerations .................................................................................................................. 78
• Configuring Firewall Settings on NVBU Machines ......................................................79
• Defining Filtering Rules on the Firewall ........................................................................80
Chapter 13: Configuring Plug-in Options
81
• Configuring CLI Options .................................................................................................81
- Enabling Enhanced Job Completion Status for nvjobstart ............................................................. 81
• Configuring the Disk Devices Plug-in ...........................................................................82
- Configuring Disk Space Margins for VTLs ..................................................................................... 82
- Disabling Disk Space Checks for VTLs ......................................................................................... 83
- Creating VTLs with Entry/Exit Ports ............................................................................................... 84
• Configuring the Verify Plug-in ........................................................................................84
- Performing Backup Verification Locally for All Clients ................................................................... 84
- Configuring a Default Client for Backup Verification ...................................................................... 85
- Defining Clients Which Run Verification Job Locally .................................................................... 85
• Other Subtabs on the Plugin Options Tab ....................................................................85
• Configuring Quest NetVault Backup Plug-in for Encryption .......................................86
Configuration Guide
Chapter 14: Configuring NVBU Notification Settings
•
•
•
•
•
87
Events and Notification Methods – An Overview ........................................................ 87
Configuring Mail Server for Event Notifications .......................................................... 88
Configuring Recipients for Email Notifications .......................................................... 89
Configuring a Default Printer on Windows .................................................................. 89
Configuring Network Manager Host for SNMP Trap Notifications ............................. 90
Chapter 15: Customizing the NVBU Console
•
•
•
•
•
•
•
•
•
7
91
Configuring Refresh Rates ............................................................................................ 91
Configuring Custom Color Codes for Job Status ........................................................ 92
Removing Target Set Checks for Duplication Jobs .................................................... 93
Customizing NVBU Logs Window ................................................................................. 94
Disabling NVBU Logs Window ...................................................................................... 95
Customizing Device Log Views ..................................................................................... 95
Hiding Device Logs ........................................................................................................ 96
Configuring a Default Browser on Linux/UNIX ............................................................ 96
Configuring View-Levels for Mac OS X ....................................................................... 96
Chapter 16: Configuring General Settings for NVBU
99
• Relocating Logs and NVDB Directories ....................................................................... 99
• Tuning TCP/IP Buffer Sizes .......................................................................................... 101
• Disabling Pre-installation Compatibility Checks for Packages ................................ 101
Chapter 17: Configuring the Reporting System
103
• NVBU Reporting System – An Overview .................................................................... 104
• Statistics Manager and Reports Database Manager – An Overview ........................ 104
• Customizing the Output Format .................................................................................. 105
- Customizing the HTML Output Format ........................................................................................ 105
- Customizing the Plain Text Output Format .................................................................................. 106
- Customizing the CSV Output Format ........................................................................................... 108
• Configuring the Default Output Format for
User-Defined Components 109
• Configuring the Filter View .......................................................................................... 110
• Configuring the Retention Period for Historic Reports ............................................ 110
8
Table of Contents
•
•
•
•
•
Enabling “Keep Filtered Out Records” for All Reports ............................................. 111
Customizing Statistics Manager ................................................................................. 111
Configuring Statistics Collection and Transmission Parameters .............................112
Disabling Statistics Collection on an NVBU Client ....................................................113
Creating User-Defined Purge Policies .........................................................................113
-
Creating a Global Policy for Purging the Reports Database ........................................................ 114
Creating a User-defined Schedule for Purging Report Tables ..................................................... 115
Disabling Global Purge Policy for Reports Database .................................................................. 115
Creating a Purge Policy for the “Default” Table ........................................................................... 115
Creating a Purge Policy for Individual Report Tables .................................................................. 117
Applying Global Purge Policy to Individual Report Tables ........................................................... 119
Chapter 18: Configuring Language Settings for NVBU
•
•
•
•
121
Changing Locale Setting ..............................................................................................121
Correcting Locale Changes ..........................................................................................122
Disabling Post-Installation Locale Changes ...............................................................123
Configuring Display Properties for Localized Versions ............................................123
- Changing the Font Size for NVBU Console ................................................................................. 123
- Changing the Date Format ........................................................................................................... 124
Chapter 19: Setting Up a BakBone Time Server
125
• BakBone Time – An Overview ......................................................................................125
• Configuring an Alternate BakBone Time Server ........................................................125
Chapter 20: Using the Trace Tool
127
• Trace Logs – An Overview ............................................................................................127
- Trace Levels ................................................................................................................................ 127
- Date and Time in Trace Files ....................................................................................................... 128
•
•
•
•
Setting Trace Levels ......................................................................................................128
Enabling Tracing ...........................................................................................................130
Disabling Tracing ..........................................................................................................131
Enabling Circular Logging of Trace Messages ..........................................................131
Chapter 21: Using the Txtconfig Tool
133
• Txtconfig – An Overview ..............................................................................................133
Configuration Guide
9
• Starting Txtconfig ......................................................................................................... 133
• Customizing the Default Settings Using Txtconfig ................................................... 134
• Examples ....................................................................................................................... 135
- Customizing the Auditor Daemon to Log Failed User Requests .................................................. 135
- Creating a Size-based Purge Policy for Audit Logs ..................................................................... 135
- Customizing the Purge Schedule for Audit Logs ......................................................................... 136
10
Table of Contents
Configuration Guide
11
Chapter 1:
INTRODUCING QUEST
NETVAULT BACKUP
1.1.0

Quest NetVault Backup – At a Glance

Key Benefits

Feature Summary

About this Document

Target Audience

Recommended Additional Reading

About Quest Software

Contacting Quest Software

Quest Support
Quest NetVault Backup – At a Glance
Quest NetVault Backup (NetVault Backup or NVBU) offers the most advanced,
cross-platform data protection capabilities on the market as well as unsurpassed
ease of use, out-of-the-box deployment, and pain-free scalability. NetVault Backup
allows you to safeguard your data and applications in both physical and virtual
environments using one intuitive console. And thanks to heterogeneous server
support and extensive application support you can leverage your existing
investments in data protection. NetVault Backup supports simple integration with a
variety of other NetVault products and seamless installation of a host of plug-ins
that let you tailor NetVault Backup to match the changing – and growing –
landscape of your IT infrastructure, including operating systems, messaging
applications, and databases.
1.2.0
Key Benefits

Intuitive interface requiring only minimal experience to operate

Simple, out-of-the-box deployment for fast time to value

Protection for both physical and virtual environments for cost savings

Heterogeneous server support for flexibility to adjust to changing conditions
or emergencies

Plug-in options to tailor NetVault Backup to your environment
12
Chapter 1
Introducing Quest NetVault Backup
1.3.0

Disk-based backup and de-duplication to significantly improve storage
efficiency

Comprehensive Network Attached Storage (NAS) protection to safeguard
critical data

Powerful, flexible encryption when and where you need it

Bare metal recovery to drastically reduce the time it takes to recover a failed
disk drive

Extensive storage attachment options allow for distributed backup targets
and workload

Dynamic device sharing to optimize backup data transfers and reduce points
of failure
Feature Summary

Disk-Based Backup and Deduplication – Leverage disk-based and tape
backups for creating on-site and off-site backups for failover and disaster
recovery. You can also add Quest NetVault SmartDisk (NetVault SmartDisk or
NVSD) to the backup solution for post-process data deduplication. NVSD
uses patented byte-level, variable block data analysis technology to reduce
data storage footprints by up to 90%.

Virtualization Support – Extend advanced data protection to VMware and
Hyper-V environments. A NetVault Backup plug-in gives you consistent,
reliable, point-and-click backup and restore for virtual environments without
requiring you to be an expert.

Application Protection – Ensure availability of business-critical applications
such as Oracle, SQL Server, Exchange, SharePoint, MySQL, PostgreSQL,
Domino, Informix, and Sybase with application plug-ins. These plug-ins
complement native solutions to save you time on integration – no scripting is
required to run backup and recovery jobs.

Network Attached Storage Protection – Safeguard NAS data directly on a
locally attached SCSI device, a SAN-attached device (tape or VTL) or a
storage device elsewhere on the network.

Enterprise-Wide Control – Give backup administrators the flexibility to
define, manage and monitor jobs from remote locations of their choice.
NetVault Backup’s automated features for global event notification and policybased job management simplify their tasks across heterogeneous storage
networks.

Strong Security – Meet regulatory requirements without sacrificing backup
windows or deduplication performance with an encryption plug-in for CAST128, AES-256 or CAST-256 algorithm support. Flexible job-level encryption
lets you easily select which data to encrypt.
Configuration Guide
1.4.0
13

Flexible Storage Attachment – Attach storage wherever you like with the
built-in NetVault Backup SmartClient. It allows you to easily distribute both
real and virtual backup target workloads throughout the backup domain.

Dynamically Shared Device – Share stand-alone and library-based tape
drives among backup servers and SmartClients in SAN or shared-SCSI
environments. This allows you to optimize workloads and maximize your
equipment investments.

LAN-Free Backups – Create a LAN-free backup environment to support
writing backup data directly to locally and SAN-attached storage devices.
This keeps backup traffic away from the LAN and eliminates network
bandwidth constraints.

Simple, Straightforward Licensing – NetVault Backup can be licensed by
capacity or by component, giving you incredible flexibility. With componentbased licensing, you can pick and choose which modules you need. You can
deploy an unlimited number of clients or application plug-ins. Quest offers two
capacity-based licensing editions for NetVault Backup, one offering great
value for growing businesses and one offering comprehensive protection for
larger enterprises.
About this Document
The default factory settings for NVBU can be customized to suit your environment
using the NetVault Backup Configurator. This guide explains how to use the
NetVault Backup Configurator to change the preferences and default settings for
NVBU. It does not provide information on NetVault Backup features and
functionality. For details on using NetVault Backup, refer to the Quest NetVault
Backup Administrator’s Guide.
Important: NVBU configuration settings are stored in “.cfg” files that reside in the
<NVBU home>\config directory. The settings in these files should only be
modified under the guidance of Quest Support. Be aware that any incorrect
changes to these files can cause errors and other unexpected behavior. Before
you modify a configuration file, it is good practice to create a backup copy of the
file.
1.5.0
Target Audience
This guide is intended for Backup Administrators and other technical personnel
who are responsible for implementing and managing an NVBU System. A good
understanding of the operating systems under which the NVBU Server and Clients
are running is assumed.
14
Chapter 1
1.6.0
Recommended Additional Reading

Quest NetVault Backup Installation Guide – This guide provides complete
details on installing the NetVault Backup Server and Client software.

Quest NetVault Backup Administrator’s Guide – This guide describes how to
use NetVault Backup and provides comprehensive information on all NetVault
Backup features and functionality.

Quest NetVault Backup Command Line Interface Reference Guide – This
guide provides a detailed description of the command line utilities.

Quest NetVault Backup Workstation Client Administrator’s Guide – This
guide provides complete information on administering the NetVault Backup
Workstation Client software.

Quest NetVault Backup Workstation Client User’s Guide – This guide
provides complete information on using the NetVault Backup Workstation
Client software.
You can download these guides from the Quest website at the following address:
https://support.quest.com/Search/SearchDownloads.aspx
1.7.0
About Quest Software
Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and
innovative IT management solutions that enable more than 100,000 global
customers to save time and money across physical and virtual environments.
Quest products solve complex IT challenges ranging from database management,
data protection, identity and access management, monitoring, user workspace
management to Windows management. For more information, visit
www.quest.com.
1.7.1
Contacting Quest Software
Email:
[email protected]
Mail:
Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site:
www.quest.com
For regional and international office information, refer to the web site.
Configuration Guide
1.7.2
15
Quest Support
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a Quest product and have a valid maintenance
contract. Quest Support provides unlimited 24x7 access to our Support Portal at
www.quest.com/support.
From our Support Portal, you can do the following:

Retrieve thousands of solutions from our Knowledge Base

Download the latest releases and service packs

Create, update and review Support cases
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, policies and procedures.
The guide is available at www.quest.com/support.
This guide is available in English only.
16
Chapter 1
Configuration Guide
17
Chapter 2:
GETTING STARTED

NVBU Configurator – An Overview

Starting NVBU Configurator

Starting NVBU Configurator on Linux/UNIX

Starting NVBU Configurator on Mac OS X

Starting NVBU Configurator on Windows
Remote Configurator

2.1.0
Starting Remote Configurator
Txtconfig
NVBU Configurator – An Overview
NVBU Configurator (Configurator) is a built-in configuration utility which is
available on the NVBU Server as well as Client systems. It provides an easy-touse graphical user interface to change the preferences and default settings for
NVBU, allowing you to customize NVBU to suit your environment.
The executable file for the Configurator is named nvconfigurator and resides in
the ...\bin directory (where ... represents the NVBU installation directory).
2.2.0
2.2.1
Starting NVBU Configurator
Starting NVBU Configurator on Linux/UNIX
To start the Configurator on Linux/UNIX platforms
1. Log on to the system with root-user privileges.
2. Start a terminal session, and type:
nvconfigurator
You can issue this command from any directory. Use an ampersand
character (&) to run the command in the background:
nvconfigurator &
2.2.2
Starting NVBU Configurator on Mac OS X
On Mac OS X, NVBU provides two versions of the Configurator:

Built-in Version of NVBU Configurator – The built-in version of NVBU
Configurator is provided as the Settings pane on the NVBU Administrator
18
Chapter 2
Getting Started
Console (NVAdmin). This version is provided for the native Mac OS X
interface, and offers limited functionality. For details on the Settings pane,
refer to the Quest NetVault Backup Administrator’s Guide for Mac OS X.

X11 Version of NVBU Configurator – The X11 version of NVBU
Configurator is called NVConfigurator. It is a separate application and offers
the full functionality.
To access the Settings pane on Mac OS X
1. Start the NVBU Administrator application.
2. In the NVBU Servers pane, select the applicable Server.
3. In the NVBU Operations pane, click Settings.
To access the X11 version of NVBU Configurator on Mac OS X
1. From the Finder, access Applications.
2. Locate NVConfigurator, and double-click it.
2.2.3
Starting NVBU Configurator on Windows
To start the Configurator on Windows
1. Log on to the system with administrator privileges.
2. Click Start on the taskbar.
3. Point to Programs, point to Quest Software, point to NetVault Backup, and
then click NVBU Configurator.
Figure 2-1:
NVBU
Configurator
Configuration Guide
2.3.0
19
Remote Configurator
The Remote Configurator lets you configure the preferences and default settings
for a remote NVBU system. For example, you can use the Remote Configurator
on the NVBU Server to apply new configuration settings to a client residing in a
different geographical location.
The Remote Configurator can be accessed from the NVBU Console. It is available
on both the NVBU Server and Client systems. However, it offers limited
functionality and does not allow you to configure all NVBU settings.
2.3.1
Starting Remote Configurator
To start the Remote Configurator
1. Start the NVBU Console on the local machine. Click Client Management on
the toolbar or Large Buttons panel. Alternatively, on the Administration
menu, click Client Management.
2. In the Clients list, right-click the remote NVBU machine, and select
Configure. This will start the Remote Configurator.
Figure 2-2:
Remote
Configurator
2.4.0
Txtconfig
NVBU also provides a text version of the Configurator, called Txtconfig. Txtconfig
can be used to customize NVBU settings on machines that do not support a GUI.
For details on Txtconfig, refer to Using the Txtconfig Tool on page 133.
20
Chapter 2
Getting Started
Configuration Guide
21
Chapter 3:
PERFORMING COMMON
ADMINISTRATIVE TASKS
3.1.0

Viewing NVBU Service Status

Starting and Stopping NVBU Service

Viewing NVBU Machine Details

Installing Optional Plug-ins

Removing Plug-ins

Licensing Software

Viewing License Details

Changing NVBU Password

Disabling Password-Protection for NVBU Clients

Allowing NVBU Server to Function as Client
Viewing NVBU Service Status
To view the current status of the NVBU Service
1. Click the Service tab on the Configurator.
2. The Current Status parameter on the Service tab displays the status as a
read-only string.
3. Click another tab or exit Configurator, as required.
3.2.0
Starting and Stopping NVBU Service
The NVBU Service starts automatically when the software installation completes
on the server or client system. If you need to manually stop or start the NVBU
Service, use the following steps:
1. Click the Service tab on the Configurator.
2. Select the applicable action:

To stop the NVBU Service, click Stop Service.

To start the NVBU Service, click Start Service.
22
Chapter 3
Performing Common Administrative Tasks
Figure 3-1:
Service tab
3. Click OK to apply the changes and exit Configurator. Alternatively, click
Apply to commit the new settings and remain in Configurator.
3.3.0
Viewing NVBU Machine Details
To view the NVBU machine details
1. The Machine tab is selected by default when you start the NVBU
Configurator. If another tab is currently selected on the Configurator, click the
Machine tab.
2. It includes the following details:
Figure 3-2:
Machine tab
Configuration Guide
23

Machine Name – The NVBU name of the machine.

Machine ID – The Machine ID that is used for licensing NVBU.

Network Name(s) – The Network name of the machine.

IP Address(es) – The IP address or addresses assigned to the machine.

Version – The NVBU version and build number.

O.S. Version – The version of the O/S running on the machine.

Platform – The O/S platform.
3.4.0
Installing Optional Plug-ins
NVBU offers several optional plug-ins that can be used to ensure continuous
availability of business-critical applications such as Oracle, SQL Server,
Exchange, SharePoint, MySQL, and others. You need to procure and install these
plug-ins separately. These plug-ins can be installed from the NVBU Console or the
NVBU Configurator.
To install an optional plug-in from the NVBU Configurator, use the following steps:
1. Click the Packages tab on the Configurator.
Figure 3-3:
Packages tab
2. Click Install Software to start the package installation wizard.
3. Click Next, and follow the wizard as it takes you through the installation
steps.
4. In the Enter Install File Name window, provide the full file path for the binary
file on the installation CD or the directory to which the file was downloaded
from Quest Software's web site. Alternatively, click Browse. Navigate to the
location of the binary file and select it.
5. Click Next.
24
Chapter 3
6. The Details window will display the package details. Click Next to start the
installation process. On completion, a message will be displayed. Click OK to
close the dialog box.
3.5.0
Removing Plug-ins
To remove a plug-in from NVBU Configurator
1. Click the Packages tab on the Configurator.
2. In the Installed Packages list, select the plug-in that you want to remove.
3. Click Remove Software.
4. In the confirmation dialog, click OK. On completion, a message will be
displayed. Click OK to close the dialog box.
3.6.0
Licensing Software
The evaluation license for NVBU is valid for a period of 30 days. To continue using
the software after the expiry of the evaluation period, you need to install the
permanent license keys for the NVBU Server and all installed plug-ins. These keys
can be requested at https://support.quest.com/LicenseKey.aspx. You can install
these keys from the NVBU Console or the NVBU Configurator.
To install the permanent license keys from NVBU Configurator
1. Click the License tab on the Configurator.
Figure 3-4:
License tab
2. Enter (or copy/paste) the license key in the Add New Key box.
Configuration Guide
3.7.0
25
Viewing License Details
To view the license details for NVBU
1. Click the License tab on the Configurator.
2. This tab provides the following details:

Server Capabilities – Under Server Capabilities, the Configurator
displays the number of available licenses for NVBU Clients, SmartClients,
physical and virtual backup devices, and other NetVault Backup
components.

Serial Numbers of Applied Keys – Under Serial Numbers of Applied
Keys, the Configurator displays the details of applied license keys.
Note: The plug-in licences will only be displayed on the NVBU Client on which it is
installed. It will not be displayed on the NVBU Server
3.8.0
Changing NVBU Password
To change the NVBU Server or Client password
1. Click the Security tab on the Configurator.
2. Configure the following parameters:
Figure 3-5:
Security tab

New Password – Enter the new password for NVBU. The password
cannot contain the characters <, >, &, #, and | .

Confirm Password – Re-enter the password for confirmation.
26
Chapter 3
3.9.0
Disabling Password-Protection for NVBU
Clients
To add or access a client without its password, you can temporarily disable
password-protection for a client.
To disable password-protection for an NVBU Client
2. Configure the following parameter:

Disable Security – Select this check box.
3.10.0
Allowing NVBU Server to Function as Client
By default, NVBU does not allow you to add an NVBU Server as a Client to
another NVBU Domain. To allow an NVBU Server to function as a client, use the
following steps:

This Machine May be Added as a Client to a Server – Select this check
box on the NVBU Server.
Configuration Guide
CUSTOMIZING
4.1.0
27
Chapter 4:
THE
AUDITOR
DAEMON

Auditor Daemon – An Overview

Generating Audit Logs for Failed User Requests

Creating a User-Defined Policy for Deleting Audit Logs

Creating a User-Defined Schedule for Purging Audit Logs

Disabling Automatic Purging of Audit Logs

Configuring Number of Active Sysop Operator Message Notifications
Auditor Daemon – An Overview
The Auditor Daemon (nvavp) runs on the NVBU Server. This process tracks and
controls user activities. It validates each user request, and depending on the
granted privileges, allows or denies the request. The Auditor Daemon records
these events in the audit log, which is also known as the Audit Trail. The audit log
is named audit.bin and resides in the ...\db directory (where ... represents the
NVBU installation directory). You can view these logs using the NVBU Audit Trail
report. For details on the Audit Trail report, refer to the Quest NetVault Backup
Administrator’s Guide.
By default, the Auditor Daemon logs each user activity regardless of whether the
request is granted or denied. It automatically deletes the logs that are older than
31 days. You can customize the Auditor Daemon to only log failed user requests,
or create a user-defined policy for deleting audit logs. The default behavior and
properties of the Auditor Daemon can be changed from the Auditing tab on the
Configurator.
4.2.0
Generating Audit Logs for Failed User Requests
By default, the Auditor Daemon logs each user request, regardless of whether the
request is granted or denied. To override this behavior and generate audit logs
only for the failed user requests, use the following steps:
1. Click the Auditing tab on the Configurator.
28
Chapter 4
Customizing the Auditor Daemon
Figure 4-1:
Auditing tab

Only Record Failed Requests in the Audit Trail – Select this check box.
Note: The NVBU Service should be restarted to apply any changes to this setting.
4.3.0
Creating a User-Defined Policy for Deleting
Audit Logs
The Auditor Daemon is configured to automatically deletes all audit logs that are
older than 31 days. You can override this behavior with one of the following types
of user-defined policies:

Age-Based Purge Policy – Delete logs that older than a certain number of
days.

Size-Based Purge Policy – Delete logs when the file size exceeds the
maximum size.
To create a user-defined policy for automatically deleting audit logs
2. Select the required method:
a. Age-Based Purge Policy – To create a purge policy based on the log
age, configure the following parameters:

Purge Type – Select By Age.

Purge Entries That are Older Than – Enter or select the maximum
age for the audit logs. The log age is specified in number of days. By
default, this parameter is set to 31 days.
b. Size-Based Purge Policy – To create a purge policy based on the log file
size, configure the following parameters:
1. Purge Type – Select By Size.
2. Purge When Trail Exceeds – Enter or select the maximum file size for
the audit trail. The file size is specified in MB. By default, this
parameter is set to10MB.
Configuration Guide
29
3. The default interval between two purge events for the audit logs is 24 hours.
To change this schedule, refer to Creating a User-Defined Schedule for
Purging Audit Logs on page 29.
4.4.0
Creating a User-Defined Schedule for Purging
Audit Logs
The default interval between two purge events for the audit logs is 24 hours. To
change this schedule, use the following steps:

Time Interval Between Purges – Enter or select the time interval
between two purge events. The time interval is specified in number of
hours.
4.5.0
Disabling Automatic Purging of Audit Logs
The Auditor Daemon is configured to automatically deletes all audit logs that are
older than 31 days. To disable automatic purging of audit logs, use the following
steps:

Purge Type – Select None.
Warning: The audit logs can consume a considerable amount of disk space.
Therefore, periodic purging of the logs is necessary. Since you cannot purge the
audit logs manually, it is recommended that you do not disable the automatic
purging of audit logs.
30
Chapter 4
Customizing the Auditor Daemon
4.6.0
Configuring Number of Active Sysop Operator
Message Notifications
If you set up the Sysop Operator Message notification method for several events
and these events are raised repeatedly in NVBU, the process manager may
eventually run out of available resources and hang. To prevent this, NVBU limits
the number of simultaneous notifications that are started on a system. If any new
notification causes the count of active notifications to exceed the configured limit,
NVBU will discard it with the following Operator Message in the NVBU Status
window:
Too many simultaneous notifications. Refusing further
notifications
The Auditor Daemon will not relay any other notification until the count of active
notifications falls below the defined limit. By default, this count is set at 5.
To change the count of active notifications

Maximum Simultaneously Active Notifications – Enter or select the
value. You can set it between 1 and 20.
Configuration Guide
31
Chapter 5:
CUSTOMIZING THE DEVICE
SCAN PROCESS
5.1.0

Device Scan Process – An Overview

Configuring Device Type for Startup Device Scan

Disabling Startup Device Scan

Configuring Device Type for Post-Startup Device Scan

Disabling Post-Startup Device Scan
Device Scan Process – An Overview
The Device Scan process (nvdevicescan) runs on the NVBU Server and
SmartClients. This process enables automatic configuration of backup devices. It
scans for locally-attached libraries and standalone drives on an NVBU system.
The Device Scan process can identify devices manufactured by several vendors.
The devices thus identified can be added using the Automatic Device
Configuration wizard.
The Device Scan process is initiated during the following events:

NVBU Startup – The Device Scan process is configured to start
automatically when you start the NVBU Service on a machine. It scans the
hardware for new devices on the SCSI bus or attached to the NDMP Filers.
The scanning process can take some amount of time, which may delay the
startup. To avoid this delay, you can disable device scan during NVBU startup
or restrict the type of device it scans for.

Post-Startup – The Device Scan process is also initiated when you open the
NVBU Device Management window. It scans for new devices which are
currently not added to the NVBU Server. You can disable this feature if no
new hardware has been added, or configure the type of device it scans for.
The settings for Device Scan can be changed from the Device Scan and
GUI –> Devices tabs on the Configurator.
32
Chapter 5
Customizing the Device Scan Process
5.2.0
Configuring Device Type for Startup Device
Scan
By default, the Device Scan process scans for both libraries and standalone
devices at the start of the day (NVBU startup). To configure the type of device it
scans for during NVBU startup, use the following steps:
1. Click the Device Scan tab on the Configurator.
Figure 5-1:
Device Scan
tab

Scan for Devices at Start of Day – The default value for the Scan for
Devices At Start of Day parameter is Both. To scan for a particular type
of device, select one of the following in the list:

Drives – Select Drives to only scan for standalone drives.

Libraries – Select Libraries to only scan for libraries.
5.3.0
Disabling Startup Device Scan
To disable device scan during NVBU startup, use the following steps:
1. Click the Device Scan tab on the Configurator.

Scan for Devices at Start of Day – Select Neither in the Scan for
Devices At Start of Day list.
5.4.0
Configuring Device Type for Post-Startup
Device Scan
By default, the Device Scan process only scans for libraries when you open the
NVBU Device Management window. To configure the type of device it scans for
during this event, use the following steps:
1. Click the GUI tab on the Configurator.
2. Click the Devices subtab.
Configuration Guide
33
Figure 5-2:
Devices
subtab on GUI
tab

Enable Automatic Device Scanning – The default value for this
parameter is Libraries. To scan for all devices, select Libraries and
Drives in the Enable Automatic Device Scanning list.
5.5.0
Disabling Post-Startup Device Scan
To disable device scan when you open the NVBU Device Management window
Figure 5-3:
Devices
subtab on GUI
tab

Enable Automatic Device Scanning – Select Neither in this list.
34
Chapter 5
Customizing the Device Scan Process
Configuration Guide
35
Chapter 6:
CUSTOMIZING THE JOB
MANAGER PROCESS
6.1.0

Job Manager – An Overview

Configuring Keep-Alive Rate for Job Manager

Configuring “nvjobcreate” to Return Job Exit Code
Job Manager – An Overview
The Job Manager process (nvjobmgr) runs on the NVBU Server and manages the
execution of an NVBU job. This process is initiated by the Schedule Manager. A
single instance of Job Manager runs for each job until the completion of a job. The
Job Manager reports on the job state changes and the exit status of a job. It
coordinates with the Data Plug-in and fetches the required information from the
NVBU Server. It is also responsible for sending drive and media requests to the
Media Manager process. You can change the default settings for the Job Manager
from the Job Manager tab on the Configurator.
6.2.0
Configuring Keep-Alive Rate for Job Manager
Keep-Alive messages are used to verify network connection between two NVBU
machines and to keep this connection intact. The Keep Alive Rate for Job
Manager controls how often keep-alive messages are sent between the Job
Manager running on the NVBU Server and the Data Plug-in running on an NVBU
Client. The default interval for keep-alive messages for Job Manager is 5 minutes.
To change the keep-alive rate for Job Manager
1. Click the Job Manager tab on the Configurator.
2. On the Timeouts subtab, configure the following parameter:
Figure 6-1:
Timeouts sub
tab on Job
Manager tab

Keep Alive Rate – Enter or select the duration between two successive
keep-alive transmissions. The keep-alive rate is set in number of minutes.
The default value for this parameter is 5 minutes.
36
Chapter 6
Customizing the Job Manager Process
6.3.0
Configuring “nvjobcreate” to Return Job Exit
Code
By default, the nvjobcreate command returns the Job ID on success and “0” on
failure. To configure this utility to return the exit code instead of the Job ID, perform
the following steps.
1. Click the Job Manager tab on the Configurator.
2. Click the Status subtab, and configure the following parameter:
Figure 6-2:
Status subtab
on Job
Manager tab

CLI Utility nvjobcreate Will Return Exit Status – By default, the
nvjobcreate command returns the Job ID on success and “0” on failure.
When you select this check box, it returns “0” on success and “1” on
failure. To determine the Job ID when the nvjobcreate command has
been configured to return the exit status, you can use the -jobidfile option
with nvjobcreate to output the Job ID to a specified file. For details on the
nvjobcreate command, refer toQuest NetVault Backup Command Line
Interface Reference Guide.
Configuration Guide
CUSTOMIZING
7.1.0
37
Chapter 7:
THE
LOG
DAEMON

Log Daemon – An Overview

Configuring Disk Space Alert Thresholds

Creating a User-Defined Schedule for Disk Space Checks

Disabling Disk Space Checks

Creating a User-Defined Policy for Deleting NVBU Logs

Creating a User-Defined Schedule for Purging NVBU Logs

Disabling Automatic Purging of NVBU Logs

Optimizing the Log Daemon
Log Daemon – An Overview
The Log Daemon (nvlogdaemon) runs on the NVBU Server and performs the
following functions:

Records NVBU Logs – The Log Daemon manages logs generated by
various NVBU processes and writes them to log files. NVBU logs are used to
track system activities and correct problems.
NVBU logs reside in the ...\Logs directory on the NVBU Server (where ...
represents the NVBU installation directory). This directory can be relocated
using Configurator. For details, refer to Relocating Logs and NVDB
Directories on page 99.
The log files are stored in binary format and named log-0, log-1, log-2, and so
on. The Log Daemon always reserves space for logs by creating a blank file.
For example, when log-0 becomes full, it creates log-2 before opening log-1
for recording events. Log-0 and log-1 are created during NVBU installation.
To make sure that the NVBU logs do not continue to accumulate and
consume large amounts of disk space, the Log Daemon automatically
deletes the logs after 30 days. You can change this behavior with a userdefined policy, or delete the logs manually.

Performs Periodic Disk Space Checks – The Log Daemon performs
periodic disk space checks, and issues alert messages when the space
usage level reaches the defined warning or critical threshold. The disk space
check applies to the following NVBU directories:

Home
38
Chapter 7
Customizing the Log Daemon

Database

Logs

Reports
By default, the disk space check is scheduled to run every hour. You can
reschedule or disable this event using the Configurator.
The default behavior and properties of the Log Daemon can be changed from the
Logging Daemon tab on the Configurator.
7.2.0
Configuring Disk Space Alert Thresholds
NVBU defines two alert thresholds for the disk space usage levels – Warning and
Critical. These thresholds are defined as “percent full of total disk space”. By
default, the warning threshold is set to 85 percent full and the critical threshold is
set to 97 percent full of the total disk space. To change these default settings, use
the following steps:
1. Click the Logging Daemon tab on the Configurator.
Figure 7-1:
Logging
Daemon tab
Note: The NVBU Service should be restarted to apply any changes to the Warning
and Critical threshold values.
a. Disk Space Warning Threshold – Enter or select the disk usage level for
warning threshold. By default, it is set to 85 percent full of total disk space.
When the space usage reaches or exceeds the warning threshold, the
following events occur:

The Log Daemon reports an error.
Configuration Guide
39

The Auditor Daemon logs a sysop operator message which is
displayed under Operator Messages on the NVBU Status window.

NVBU raises the Home Drive Becoming Full event. You can
configure one or more global notification methods to generate and
receive notification when this event is raised. For details, refer to the
Quest NetVault Backup Administrator’s Guide.
b. Disk Space Critical Threshold – Enter or select the disk usage level for
critical threshold. By default, it is set to 95 percent full of total disk space.
When the space usage reaches or exceeds the critical threshold, the
following events occur:

NVBU sends an error message to Event Viewer on Windows and
syslog utility on Linux/UNIX.

The Log Daemon reports an error.

NVBU shuts down automatically and sets the status on the Service tab
of the NVBU Configurator to Stopped Disk Full.
Warning: If disk space is critically low when the NVBU Service starts, then the
errors are only be logged through Event Viewer or syslog. You are required to take
necessary steps to ensure availability of adequate disk space before restarting the
NVBU Service.
7.3.0
Creating a User-Defined Schedule for Disk
Space Checks
The default interval between two successive disk space checks is one hour. To

Time Interval between Disk Space Full Checks – Enter or select the
time interval between two disk space check events. The time interval is
specified in number of hours.
7.4.0
Disabling Disk Space Checks
To disable disk space checks by the Log Daemon, use the following steps:
40
Chapter 7

Time Interval between Disk Space Full Checks – Enter or select 0
(zero).
Note: Regardless of this setting, the log daemon will perform a disk space check
when the NVBU Service restarts.
7.5.0
Creating a User-Defined Policy for Deleting
NVBU Logs
NVBU is configured to automatically delete logs that are older than 30 days. You
can override this behavior by creating one of the following types of user-defined
policies:

Age-based Purge Policy – Delete logs that older than a certain number of
days.

Page-based Purge Policy – Delete log pages when the total pages exceeds
a certain number.
Note: For details on deleting the NVBU logs manually, refer to the Quest NetVault
To create a user-defined policy for deleting NVBU logs
2. Select the required method:
Figure 7-2:
Auto purge
methods for
audit logs on
Logging
Daemon tab
Configuration Guide
41
a. Age-based Purge Policy – For a purge policy based on log age,
configure the following parameters:

Auto-Purge Method – Select Exceeds Log Age.

Auto-Purge Entries That are Older Than – Enter or select the
maximum age for the logs. The log age is specified in number of days.
The default value for this parameter is 30 days.
b. Page-based Purge Policy – For a purge policy based on page size,

Auto-Purge Method – Select Exceeds Number of Pages.

Auto-Purge When the Number of Log Pages Exceeds – Enter or
select the maximum number of log pages that can exist at any given
point of time. The default value for this parameter is10 pages.
3. By default, automatic purging occurs every 3 hours. To change this schedule,
refer to Creating a User-Defined Schedule for Purging NVBU Logs on page
41.
7.6.0
Creating a User-Defined Schedule for Purging
NVBU Logs
The default interval between two purge events for NVBU logs is 3 hours. To

Select the Time Interval to Auto Purge – Enter or select the time interval
between two purge events. The time interval is specified in number of
hours.
7.7.0
Disabling Automatic Purging of NVBU Logs
NVBU is configured to automatically delete logs that are older than 30 days. To
disable automatic purging of log files, use the following steps:

Auto-Purge Method – Select None.
42
Chapter 7
Important: NVBU logs can consume a considerable amount for disk space.
Therefore, periodic purging of the logs is necessary. If you disable automatic
purging, ensure that you manually delete the logs at regular intervals. For details
on purging logs manually, refer to the Quest NetVault Backup Administrator’s
Guide.
7.8.0
Optimizing the Log Daemon
To change the default settings for the Log Daemon, use the following steps:
2. Configure the applicable parameters:

Log File Page Size – Enter or select the maximum page size for log files.
The file size in specified in KB. The default value for this parameter is
1024KB.
When a log file becomes full, the log daemon does the following:

Creates a new blank file to reserve space for logs.

Starts writing to the next file.
Message Response Interval – When you open the NVBU Logs window,
the log daemon sends all logs to the NVBU Console. The response
interval determines the amount of time NVBU Console waits for the Log
Daemon to send all logs before displaying a progress dialog box. This
dialog displays the number of logs loaded against the total number of logs.
If the response is delayed, you can choose to abort the operation by
clicking Cancel on the progress dialog box.
The default response time for the log daemon is 256 milliseconds. To
increase or decrease the interval, enter or select the amount of time in
Message Response Interval. The minimum amount of response time
that you can set is 100 milliseconds.
If the NVBU Console receives all logs within the set interval, the progress
dialog box will not be displayed at all. This will be true if there are only few
log messages to be displayed.

The progress dialog box is refreshed every 256 milliseconds. To
change the refresh rate, enter or select the time interval in Minimum
Time between Progress Updates.
Outgoing Message Bundle Size – To improve performance, the log
daemon sends messages to NVBU Console in bundles. Each bundle
contains 64 messages by default. To change the number of messages per
Configuration Guide
43
bundle, enter or select the bundle size in Outgoing Message Bundle
Size.

Minimum Warning Level to Send to System Log – The log daemon
automatically sends logs with warning code 64 and above to the operating
system logs. You can view these logs through Event Viewer on Windows
and syslog on Linux/UNIX. To change the severity level of messages that
are sent to the operating system, enter or select the warning level code in
Minimum Warning Level to Send to System Log. The warning codes
and the corresponding severity level of the messages are listed in the
table below:
Code
Severity Level
112
Severe Errors
96
Severe Errors and Errors
80
Severe Errors, Errors and Warnings
64
Severe Errors, Errors, Warnings and Startup Messages
48
Severe Errors, Errors, Warnings, Startup Messages and Job Messages
32
Severe Errors, Errors, Warnings, Startup Messages, Job Messages and
Informational Messages
16
Severe Errors, Errors, Warnings, Startup Messages, Job Messages,
Informational Messages and Background Messages
0
All Messages

Convert Syslog Messages to UTF8 – By default, NVBU uses Extended
Unix Code (EUC) Encoding to convert syslog messages in non-English
NVBU configurations. To use Unicode Transformation Format-8 (UTF-8)
for these messages, select the Convert Syslog Messages to UTF8
check box.
44
Chapter 7
Configuration Guide
45
Chapter 8:
CUSTOMIZING THE MEDIA
MANAGER PROCESS
8.1.0

Media Manager – An Overview

Configuring Retention Period for Imported Backups

Using Barcodes as Default Media Labels

Setting Priority Levels for Continuation Media Requests

Setting Priority Levels for Media Labeling and Blanking Requests

Configuring Callback Timeouts for Bulk Media Operations

Setting Interval for Media Status Updates

Disabling Reuse of Read-Only Media

Creating a User-Defined Policy for Automatic Index Compression

Creating a User-Defined Schedule for Index Compression

Disabling Automatic Index Compression

Configuring Minimum Disk Space for Index Decompression

Customizing the Diagnose Media Requests Window

Customizing Device Related Settings

Enabling Timeout for Source Media Requests

Configuring Additional Media Manager Settings

Configuring Transfer Update Frequency for Data Domain Systems

Configuring Timeout Interval for NVSD “Stream End” Responses

Configuring Media Request Weights
Media Manager – An Overview
The Media Manager (nvmedmgr) runs on the NVBU Server and performs the

It manages the media database. The media database contains information
about the media contents and online backup savesets.

The Media Manager stores the device configuration details. It manages the
backup devices through the Device Manager processes. The Media Manager
issues high-level instructions for loading and unloading media, which are
carried out by the Device Manager processes.
46
Chapter 8
Customizing the Media Manager Process

It controls the selection of device and media for a job based on the media
requests submitted by the Job Manager.
You can change the default settings for the Media Manager from the Media
Manager tab on the Configurator.
Note: The NVBU Service should be restarted to apply any changes to the Media
Manager Settings.
8.2.0
Configuring Retention Period for Imported
Backups
NVBU cannot process any data on a piece of media if the Media Database does
not contain any information about it. Such media items are tagged as foreign
media items. Typically, media that are removed from the NVBU Server or swapped
between libraries in different NVBU Domains are marked as foreign media. To
access the savesets on a foreign media item, you need to scan the backups and
the on-tape indexes to import the required data to the NVDB. For details on
scanning foreign media, refer to Quest NetVault Backup Administrator’s Guide.
The retention period for the imported data is determined by the backup life set for
the savesets. For the savesets that have already retired, the data is temporarily
stored for 7 days.
To change retention period for imported savesets
1. Click the Media Manager tab on the Configurator.
2. On the General Settings subtab, configure the following parameter:
Figure 8-1:
General
Settings
subtab

Minimum Life for Imported Backups – Enter or select the number of
days NVBU should retain the imported data for a retired saveset. The
default value for this parameter is 7 days.
Configuration Guide
8.3.0
47
Using Barcodes as Default Media Labels
While performing a backup, you can automatically label blank media using the
Automatically Label Blank Media option available on the Target tab of the
NVBU Backup window. When you select this option, NVBU creates a label string
using the NVBU Server name, system name, and a seed number. You can also
configure NVBU to use media barcodes as the default labels for blank media.
To use barcodes as the labels for blank media

Use Barcodes as Labels – To use media barcodes as the default label
for blank media during backups, select the Use Barcodes as Labels
check box.
8.4.0
Setting Priority Levels for Continuation Media
Requests
A continuation request occurs when an active backup or restore job requires
additional media for completion. NVBU assigns a priority level of 5 to such
requests so that they are not preempted by other media requests, and the active
job completes without any interruption.
To change the default priority levels for continuation requests
2. On the General Settings subtab, configure the following parameters:

Continuation Restore Request Priority Boost – Enter or select a
priority level for continuation requests by restore jobs. By default, these
requests are assigned a priority level of 5.

Continuation Backup Request Priority Boost – Enter or select a priority
level for continuation requests by backup jobs. By default, these requests
are assigned a priority level of 5.
Note: The priority level ranges from 1 (highest priority) to 100 (lowest priority). A
priority level of zero sets a request to run as a background task.
48
Chapter 8
8.5.0
Setting Priority Levels for Media Labeling and
Blanking Requests
NVBU assigns a priority level of 10 to media labeling and blanking requests. To
change these settings, perform the following steps:

Label Request Priority – Enter or select a priority level for bulk media
labeling requests. By default, these requests are assigned a priority level
of 10.

Blank Request Priority – Enter or select a priority level for bulk media
blanking requests. By default, these requests are assigned a priority level
of 10.
Note: The priority level ranges from 1 (highest priority) to 100 (lowest priority). A
priority level of zero sets a request to run as a background task.
8.6.0
Configuring Callback Timeouts for Bulk Media
Operations
The callback timeouts for bulk media labeling and blanking operations control how
long NVBU waits for user inputs before ending these requests. By default, NVBU
waits for 120 seconds for user confirmation. The requests are not carried out if the
callback timeouts expire for the operations. To change the default timeout settings,
perform the following steps:

Bulk Label Callback Timeout – Enter or select a callback timeout for
bulk media labeling request. The timeout value is specified in number of
seconds. The default value for this parameter is 120 seconds.

Bulk Blank Callback Timeout – Enter or select a callback timeout for
bulk media blanking request. The timeout value is specified in number of
Configuration Guide
8.7.0
49
Setting Interval for Media Status Updates
The online media status is updated every 10 minutes on the NVBU Media
Management window. To change this interval, perform the following steps:

Minimum Interval between Reporting Online Capacity – Enter or
select the interval for online media status updates. The update interval is
specified in minutes. The default interval is 10 minutes.
8.8.0
Disabling Reuse of Read-Only Media
NVBU automatically removes the read-only tag for a media item when the last
saveset stored on is retired. This allows you to re-use the media for new backups.
To disable this feature, perform the following steps:

Mark Expired Read Only Media as Writable – Clear this check box to
prevent reuse of a retired read-only media. This check box is selected by
default.
8.9.0
Creating a User-Defined Policy for Automatic
Index Compression
Backup indexes which are stored in the NVDB are called Online Indexes. NVBU
automatically compresses online indexes after 30 days of inactivity. To customize
this period, perform the following steps:
Figure 8-2:
Index
compression
parameters on
General
Settings
subtab
50
Chapter 8

Days of Inactivity before an Index is Compressed – Enter or select the
inactivity period for index compression. The default value for this
parameter is 30 days.
Note: You can also manually compress the Online Indexes from the NVBU
Restore window. For more information on this procedure, refer to the Quest
NetVault Backup Administrator’s Guide.
8.10.0
Creating a User-Defined Schedule for Index
Compression
The Media Manager scans the NVDB at periodic intervals to find backup indexes
which can be compressed. The default interval between two scan cycles is 12
hours. To change this schedule, perform the following steps:

Hours between Scans for Indexes to be Compressed – Enter or select
the interval for index compression scans. The default interval between two
scans is 12 hours.
8.11.0
Disabling Automatic Index Compression
To disable automatic compression of online indexes, perform the following steps:

Days of Inactivity before an Index is Compressed – Enter or select 0
(zero).
8.12.0
Configuring Minimum Disk Space for Index
Decompression
NVBU automatically decompresses the backup indexes when you try to browse or
restore a saveset with compressed indexes. You can also manually decompress
the indexes from the NVBU Restore window. For details on decompressing a
backup index, refer to the Quest NetVault Backup Administrator’s Guide. By
Configuration Guide
51
default, NVBU reserves 500MB of free disk space on the NVDB drive or partition,
which is required before and after an index compression. To change this setting,

Minimum Space for Index Decompression – Enter or select the
minimum amount of space required on the NVDB drive or partition. The
space requirement is specified in MB. The default value for this parameter
is 500MB.
A decompression request will fail in the following circumstances:

The available space on the NVDB drive or partition is less than the
minimum required space.

The required amount of free disk space will not be available on the
NVDB drive or partition after a decompression. When NVBU receives
a decompression request, it reads the index header to determine its
decompressed file size. The request will fail if the available space on
the NVDB drive or partition will go below the minimum required space
after decompression.
If it fails, then NVBU will display an error message in one of the following
windows:

When you issue the decompress command manually, NVBU will
display the message on the NVBU Restore window.

When NVBU performs an automatic decompression for a restore or an
incremental backup, it will display the message in the NVBU Logs
window.
8.13.0
Customizing the Diagnose Media Requests
Window
NVBU supports a maximum of 64,000 characters in the Diagnose Media
Requests for Job window. To reduce the number for characters displayed on this
window, perform the following steps:

Maximum Characters in a Media Request Diagnosis – Enter or select
the number of characters that can be displayed on the Diagnose Media
Requests for Job window. It is specified in thousands of characters.
Lesser number of characters may result in quicker output. However, the
52
Chapter 8
output may be truncated and you may not get the complete information.
Therefore, it is recommended that you do not change the default settings
for this parameter.
8.14.0
Customizing Device Related Settings
To customize the device related settings controlled by the Media Manager,
Figure 8-3:
Device related
parameters on
General
Settings
subtab

Do not Display Device Activity in the Device Window – Select this
check box to stop status updates on the NVBU Device Management
window. It may help reduce the load on the NVBU Server when several
backup devices are added to the Server.

Do Not Display Drives that are Available but not Active – Select this
check box to hide the offline devices on the NVBU Device Management
window.

Only Check Available Drives and Media when Processing a Media
Request – Select this check box to only check for available drives and
media when a media request is received. It can be useful in large
environment to reduce the network traffic generated by the automatic
checks. However, it may cause a delay in job startup when several jobs
are launched at the same time.
Configuration Guide
53

Only Check Available Drives when Processing a Media Request –
Select this check box to only check for available drives when a media
request is received.

Only Check Available Media when Processing a Media Request –
Select this check box to only check for available media when a media
request is received.

Do Not Issue Prevent/Allow Media Remove Commands to Drives –
During backup and restore operations, the Media Manager issues
PREVENT ALLOW MEDIUM REMOVAL SCSI commands in order to
move a medium to or from a drive. If your library software can handle
medium removal/ejection by itself and does not require any explicit
commands to be sent to the drive, then you can select the Do Not Issue
Prevent/Allow Media Remove Commands to Drives check box. When
this check box is selected, the Media Manager will skip the PREVENT
ALLOW MEDIUM REMOVAL SCSI commands during device operations.

Do Not Open a Device if the Serial Number has Changed – Select this
check box to stop issuing commands to a device whose serial number has
changed since its last configuration for NVBU.

Unavailable Device Retry Interval – Enter or select the retry interval for
unavailable devices. The retry interval is specified in minutes. By default,
NVBU makes an attempt every 30 minutes to locate an unavailable
device.

Allow Library Modification when Jobs are Running – Select this check
box to allow a user to modify the library settings while it is in use.

Do Not Scan Unknown Media – When you add tapes to a library, and
close the door (or restart the library), NVBU takes an inventory by reading
the media barcodes. If NVBU cannot find the barcode for a piece of
media, then it marks that tape as UNKNOWN. You can configure the
Mark Unknown Media Blank parameter on the Configure Device
window to mark such media items as BLANK. For details on this option,
refer to the Quest NetVault Backup Administrator’s Guide.
If you do not mark the unknown tapes as BLANK, then NVBU starts
loading each unknown tape into one of the drives to scan for backups and
on-tape indices. On very large systems, this can increase the burden on
the drive resources.
To leave the unknown tapes as UNKNOWN and not scan them
automatically, select the Do Not Scan Unknown Media check box. This
option applies to all new libraries that are added to the NVBU Server.
However, it does not change the setting for existing libraries. To apply this
parameter to an existing library, you need to remove the library and re-add
it.
54
Chapter 8
You can also configure this parameter on a per-library basis. For details,
refer to the Quest NetVault Backup Administrator’s Guide.
8.15.0
Enabling Timeout for Source Media Requests
For Consolidate Incremental Backups and Data Copy jobs, when you configure
the Media Request Timeout setting on the Target tab of the NVBU Backup
window, it is possible to apply the same timeout settings to the requests for the
source media. Similarly, for the source set for Secondary Copies, media request
timeout can be obtained from the Media Request Timeout settings configured in
the target set. This feature can be used to abort a backup job if the request for the
source media cannot be met within the specified interval. To apply the target
media request timeouts to the source media requests, perform the following steps:
Figure 8-4:
Check box for
enabling
timeout for
source media
requests

Use Target Media Request Timeout for Source Media Request –
Select this check box to enable timeout for the source media requests.
The timeout settings for the source media requests will be the same as the
Media Request Timeout settings on the Target tab of the NVBU Backup
window for Consolidate Incremental Backups and Data Copy jobs. For
Secondary Copy jobs, this setting for the source set will be obtained from
the target set.
8.16.0
Configuring Additional Media Manager Settings
To configure additional settings for Media Manager, perform the following steps:
Figure 8-5:
Additional
parameters on
General
Settings
subtab
Configuration Guide

55
Force Process Media Request Queue Throttling – This parameter
allows NVBU to interrupt the continuous processing of media request
queues in very busy systems to allow other processing to occur. It
determines the minimum response time between two media requests.
Quest Software strongly recommends that you do not change the default
setting for this parameter unless advised by Quest Support.

Life of Segments Table Scan Results for Duplication – During Phase 2
Data Copy and Duplication jobs, the Media Manager stores the results of
the Segments table scan so that it does not have to scan the table each
time a media request is serviced. This parameter determines the amount
of time, NVBU retains the cached results. The default value for this
parameter is 600 seconds. To change the default setting, enter or select
the new value. The recommended period is between 300 and 1800
seconds.

Recover Database Table After Failed Compaction – Select this check
box to create a copy of the NVDB tables before performing a database
compact action during NVDB backups. The copy is used to recover the
tables and indexes in the event of a failure or data corruption during the
compact action. This option applies to both the Media and Schedule
Database tables.
The copy of the tables is stored in the …/tmp directory (where …
represents the NVBU installation directory. For any database table, the
compact action will not occur if there is insufficient disk space in the tmp
directory to store a copy of the table. By default, this option is disabled
because of the disk space overhead associated with it. Before enabling
this option, ensure that the tmp directory has sufficient space to store the
copy of the largest database table and index.
8.17.0
Configuring Transfer Update Frequency for
Data Domain Systems
When you add a Data Domain system to the NVBU Server, NVBU creates several
metadata files on the device. Each NVBU Server (to which you add the Data
Domain system) creates is its own set of metadata files. NVBU also writes
“transfer statistics” to the stats.stnz file. The nvstatsmngr process uses this file
and requires that it is regularly updated. However, frequent updates can have a
significant performance impact on the system. By default, NVBU updates the file
after every 5 seconds or 10 blocks of data transfer.
56
Chapter 8
To change the default settings, perform the following steps:
1. Click the Media Manager tab on the Configurator. Then, click the Foreign
RAS Device Configuration subtab.
Figure 8-6:
Foreign RAS
Device
Configuration
subtab

Transfer Update Frequency (Blocks) – Enter or select number of blocks
transferred between two transfer statistics updates for the Data Domain
systems. The default value for this parameter is 10 blocks.

Transfer Update Frequency (Seconds) – Enter or select the time
interval between two transfer statistics updates for the Data Domain
systems. The time interval is specified in number of seconds. The default
interval is 5 seconds.
8.18.0
Configuring Timeout Interval for NVSD “Stream
End” Responses
To change the default timeout interval for NVSD “stream end” responses, perform
1. Click the Media Manager tab on the Configurator. Then, click the DAV RAS
Device Configuration subtab,
Figure 8-7:
Foreign RAS
Device
Configuration
subtab

Data Transfer Stall Timeout – This parameter determines the amount of
time NVBU waits for a “stream end” response from an NVSD device
before reporting a stall. The default value for this parameter is 60
seconds. To change the default setting, enter or select the new value. The
stall timeout interval is specified in number of seconds.
Configuration Guide
8.19.0
57
Configuring Media Request Weights
The Media Request Weighting functionality allows you to set a relative priority for
the backup devices. The Media Manager process uses these settings while
assigning a media request for a backup or restore job. The default weights
assigned to the different device types are as follows:
Device Type
Media Request Weight
Local Device
32
RAS Device
16
Non-NDMP Device
8
Media Loaded Device
4
Empty Device
2
To change the media request weight for a device type, perform the following steps:
1. Click the Media Manager tab on the Configurator. Then, click the Media
Request Weightings subtab.
2. Configure the applicable parameters:
Figure 8-8:
Media
Request
Weightings
subtab

Local Device Weighting

RAS Device Weighting

Non NDMP Device Weighting

Media Loaded Weighting

Device Empty Loaded Weighting
Important: These settings should only be changed under the direction of Quest
Support.
By default, the Media Manager gives preference to a local device. To use
another suitable device for a job, you can set a higher media request weight
for that device. For example, to ensure that the Verification phase for a job
uses the same NDMP device that was used for the backup, you can set a
higher value for the “Media Loaded Weighting” parameter. If you use the
default media request weights, then the Media Manager will give preference
58
Chapter 8
to a local device even if the required media item is loaded into the NDMP
device.
To change the default setting for a device, enter or select the new value. You
can assign any value between 2 and 32.
Configuration Guide
59
Chapter 9:
CUSTOMIZING THE NETWORK
MANAGER PROCESS

Network Manager – An Overview

Configuring Timeout Settings for Remote Connections

Configuring Timeout for Inactive Connections

Configuring Keep-Alive Rate for Network Manager

Configuring Availability Broadcast Interval

Configuring Availability Check Interval

Disabling Availability Broadcasts

Configuring Security Broadcast Interval

Configuring Network Interfaces for Multihomed NVBU Systems

9.1.0
Considerations for Multihomed NVBU Machines

Reducing Startup Delay

Changing the Default Port for Network Manager

Changing the Default Port for Communications Manager
Network Manager – An Overview
The Network Manager (nvnmgr) and Communications Manager (nvcmgr) support
the inter-process messaging system. Both run as processes on UNIX/Linux, and
as threads within the nvpmgr process on Windows. The Network Manager
performs the following functions:

The Network Manager and Communications Manager work in tandem to
transmit inter-process messages to remote clients. While the
Communications Manager handles communication between the NVBU
processes on local machine, Network Manager transmits the inter-process
messages to remote clients.

The Network Manager broadcasts availability messages, which help
determine the current status of the NVBU Clients.
The default behavior and properties of Network Manager can be customized from
the Network Manager tab on the Configurator.
Note: The NVBU Service should be restarted to apply any changes to the Network
Manager settings.
60
Chapter 9
Customizing the Network Manager Process
9.2.0
Configuring Timeout Settings for Remote
Connections
The timeout for remote connection controls how long NVBU tries to establish
connection with a remote NVBU Client. It is set to 30 seconds by default. To
change the timeout settings for remote connections, perform the following steps:
1. Click the Network Manager tab on the Configurator.
2. On the Timeouts tab, configure the following parameter:
Figure 9-1:
Timeouts
subtab on
Network
Manager tab

Time to Complete a Remote Connection – Enter or select the timeout
for remote connections. The timeout value is set in number of seconds.
The default value for this parameter is 30 seconds.
9.3.0
Configuring Timeout for Inactive Connections
The timeout for inactive connection controls how long NVBU waits before ending
an inactive connection. This setting can help reduce the amount of resource
consumed by idle connections. It is set to 300 seconds by default. To change the
timeout settings for inactive connections, perform the following steps:

Time to Wait Before Dropping Inactive Connection(s) – Enter or select
the timeout for inactive connections. The timeout value is set in number of
Configuration Guide
9.4.0
61
Configuring Keep-Alive Rate for Network
Manager
The Keep-Alive messages are used to verify that a connection between two NVBU
machines is still intact. The Keep Alive Rate controls how often NVBU sends the
keep-alive messages. The default interval for keep-alive messages is 15 seconds.
To change this setting, perform the following steps:

Keep Alive Rate – Enter or select an interval for the keep-alive
messages. The keep-alive rate is set in number of seconds. The default
value for this parameter is 15 seconds.
9.5.0
Configuring Availability Broadcast Interval
The NVBU Clients broadcast availability messages at regular intervals which
provide their current status and help locate them on the network. These
broadcasts are used to update the client list and the client status on the NVBU
Client Management window. The default interval for availability broadcasts is 300
seconds. To change this interval, perform the following steps:

Time between Availability Broadcasts – Enter or select an appropriate
interval for availability broadcasts. The broadcast interval is set in number
of seconds. Note that a small interval may increase network traffic,
whereas a large interval may result in delayed updates of the client list
and client status on the NVBU Client Management window. The default
value for this parameter is 300 seconds.
9.6.0
Configuring Availability Check Interval
NVBU performs availability checks at regular intervals to scan for changes in the
network settings. If a change is detected, NVBU sends an interim broadcast to
propagate the new settings. The broadcast system is then reset to regular pulse,
reducing network traffic. The default interval for availability checks is 10 seconds.
To change this interval, perform the following steps:
62
Chapter 9

Time between Availability Checks – Enter or select an interval for
availability checks. The default interval is 10 seconds. You can reduce the
interval between two checks in order to quickly detect and transmit
changes. If the changes are not to be applied immediately, retain the
default value or set it equal to the interval for Availability Broadcasts.
9.7.0
Disabling Availability Broadcasts
Availability broadcasts are used to update the client list and client status on the
NVBU Client Management window. Although this option can be disabled, Quest
does not recommend it. Without availability broadcasts, new clients can only be
added using the Find NetVault Machine option on the NVBU Client
Management window. To disable availability broadcasts, perform the following
steps:
2. Click the Connections subtab.
Figure 9-2:
Connections
subtab on
Network
Manager tab

Broadcast Details to Machines on Local Networks – Clear this check
box.
Configuration Guide
9.8.0
63
Configuring Security Broadcast Interval
Security broadcasts discover the password-protection status of NVBU Clients, and
notify whether password has been activated or disabled on a client. The Client
Status icons on the NVBU Client Management window are updated based on
these broadcasts. The default interval for security broadcasts is 300 seconds. To
change this interval, perform the following steps:

Time between Security Broadcasts – Enter or select an appropriate
interval for security broadcasts. The broadcast interval is specified in
number of seconds. The default value for this parameter is 300 seconds
9.9.0
Configuring Network Interfaces for Multihomed
NVBU Systems
For multihomed systems, NVBU lets you configure the following parameters:

Preferred network address – The primary IP address for network connection.

Fallback addresses – The alternative addresses to use when the primary
interface is not available.

Barred addresses – The interfaces not to use for NVBU connections.
To configure these parameters, perform the following steps:
Important: This procedure should only be used when the local machine is
connected to multiple networks, either through multiple Network Interface Cards or
through virtual IP addressing.
2. Click the Connections tab.
64
Chapter 9
Figure 9-3:
Connections
subtab on
Network
Manager tab

Preferred Network Address – Enter the preferred IP address for NVBU
connections. You can only specify a single IP address.

Comma Separated List of Barred Address(es) – Enter barred or
blocked addresses. To specify multiple addresses, use a comma as a
delimiter.

Comma Separated List of Fallback Address(es) – Enter the fallback
address or addresses to use when the preferred network address is not
available. For multiple addresses, use comma as a delimiter.
Important: Ensure that the preferred, barred, and fallback addresses do not
conflict with each other.
9.9.1
Considerations for Multihomed NVBU Machines
Refer to the following notes when configuring preferred, fallback, and barred IP
addresses for multihomed NVBU systems:

When a connection is initiated, addresses are attempted in the following
order:

Preferred network address

Fallback addresses

Any other addresses in the order defined by the binding order of the host
machine
If the preferred address is unavailable and the NVBU Server starts using a
fallback address, it will not automatically revert back to the preferred address
when the IP becomes available. To force NVBU Server to use the preferred
addresses, do one of the following:
Configuration Guide
65
a. Remove the client and add it again as described below:
1. On the NVBU Console, open the NVBU Client Management window.
2. In the Clients list, right-click the NVBU Client, and select Remove or
Force Remove.
3. In the Available NVBU Machines list, right-click the NVBU Client, and
select Remove. When the client is removed, the “Machine <NVBU
Machine Name> Has Gone Down” (Warning Level: Background)
appears in the NVBU Logs window.
4. Wait until the timeout for remote connection expires. The timeout
period is determined by the Time to Complete Remote Connection
parameter which is set to 5 minutes by default. When the client is up
and detected on the network, the “Machine <NVBU Machine Name>
Has Come Up” (Warning Level: Background) appears on the NVBU
Logs window.
5. Enter the client's preferred address in Machine Name or IP Address
under Find NVBU Machine, and click Find.
6. Add the Client to the NVBU Server. For details on adding a client, refer
to the Quest NetVault Backup Administrator’s Guide.
b. Disable or disconnect the network interface currently in use until the
timeout for remote connection expires. The value set for the Time to
Complete Remote Connection parameter determines the duration for
which the network interface needs to be disabled or disconnected. Restart
the NVBU Service when the Client is reported as unavailable.
The NVBU Server will use the preferred address when the next connection
attempt is made after you restart the NVBU Service on the Client.

9.10.0
The NVBU Service should be restarted after making any changes to the
Barred Addresses parameter.
Reducing Startup Delay
When you start the NVBU Service, it attempts to resolve all Client IP addresses
listed in the .../etc/machines.dat file (where ... refers to the NVBU installation
directory). This can cause a significant delay in the service startup and the system
may appear to hang during this time. The startup delay can be reduced or avoided
by configuring the addresses that are not to be resolved. To do this, perform the
following steps:
2. Click the Connections tab.
66
Chapter 9

Comma Separated List of Networks and Addresses Not to Resolve –
Enter the addresses that are not to be resolved. You can enter a single IP
address or a range, for example, 192.168.1.2 or 192.168.x.x. For multiple
addresses or networks, use comma as a delimiter.
Note the following:

To get the list of networks from the .../etc/machines.dat file, issue the
following command:
findstr Networks machines.dat
An example output is given below:
C:\Program Files\Quest Software\NetVault
Backup\etc>findstr Network machines.dat
Networks=192.168.203.1,192.168.65.1,172.16.245.1
Networks=10.1.40.81,172.16.211.1,172.16.62.1
Networks=10.1.2.37,172.16.22.1,172.16.128.1
Networks=10.1.240.222,172.16.4.1
Networks=192.168.122.1,10.1.240.52
Networks=10.1.80.83,10.1.2.68,172.16.116.1,172.16.222.1
Networks=192.168.172.1,10.1.40.98,192.168.147.1
Networks=192.168.174.1,10.1.8.71,192.168.120.1
Networks=192.168.122.1,10.1.8.79
Networks=10.1.8.132,192.168.91.1,192.168.106.1
Networks=10.1.8.163,192.168.233.1,192.168.207.1
Networks=10.1.8.16,200.0.0.1
…
Based on this output, you can configure the following values in
Comma Separated List of Networks and Addresses Not to
Resolve – 10.0.0.0, 172.0.0.0, 192.0.0.0, 200.0.0.0. Some networks
may have name instead of the IP address. To find the IP addresses for
such clients, you can use the nslookup command.

It is possible to prevent the NVBU Service from resolving all networks.
To do this, it is necessary to specify the first octet (that is, 192.0.0.0,
10.0.0.0). Using 0.0.0.0 does not prevent NVBU from resolving the
networks.
Configuration Guide
67

The start of the service is also delayed by any client that is offline and
listed under Available Machines or added to the NVBU Server. To
speed up the process, you can remove the clients that are offline or no
longer in use from the Available Machines list.

In an NVBU Domain managed by a Windows NVBU Server, you may
experience a long delay as the service attempts to resolve all Client IP
addresses using the NBNS (NetBIOS Name Service) protocol. In this
environment, you can configure the Comma Separated List of
Networks and Addresses Not to Resolve parameter to reduce the
startup delay. Similarly, you can use this procedure in an NVBU Client
Cluster setup to prevent the service from resolving the private cluster
IP addresses.
9.11.0
Changing the Default Port for Network Manager
The Network Manager is configured to use port 20031 to open TCP and UDP
sockets on a Client. If this port is being used by another application, the NVBU
Service will fail immediately after startup. In the event of a port clash, perform the
following steps to change the default port for Network Manager:
1. Navigate to the ...\config directory (where ... represents the NVBU
installation directory), and open nvnmgr.cfg in a text editor.
2. Add the following lines to this file:
[network]
UdpPort=<port number>
TcpPort=<port number>
Consider the following when you make these changes:

Configure the same port number for both TCP and UDP sockets.

Configure a port that is not being used by any other application.

In a firewall-protected environment, ensure that the port is open and listed
on the Firewall tab of the Configurator. For details, refer to Configuring
NVBU for Firewalls on page 77.
3. Restart the NVBU Service to apply the new settings.
4. Repeat steps 1–3 on the NVBU Server and all NVBU Clients.
68
Chapter 9
9.12.0
Changing the Default Port for Communications
Manager
The Communications Manager is configured to use port 20032 to open TCP
sockets on a Client. In the event of a port clash, perform the following steps to
change the default port for Communications Manager:
1. Navigate to the ...\config directory (where ... represents the NVBU
installation directory), and open configure.cfg in a text editor.
2. Go to the [machine] section and append the following line:
[machine]
Comms TcpPort=<port number>
Consider the following when you make this change:

Configure a port that is not being used by any other application.

In a firewall-protected environment, ensure that the port is open and listed
on the Firewall tab of the Configurator. For details, refer to Configuring
NVBU for Firewalls on page 77.
3. Restart the NVBU Service to apply the new settings.
4. Repeat steps 1–3 on the NVBU Server and all NVBU Clients.
Configuration Guide
69
Chapter 10:
CUSTOMIZING THE SCHEDULE
MANAGER PROCESS
10.1.0

Schedule Manager – An Overview

Customizing NVBU Job Status Views

Creating a User-Defined Policy for Retaining Job History

Defining a Retention Period for Non-Recurring Job Definitions

Configuring Maximum Simultaneous Jobs

Including Report Jobs in the Job Views

Including Restore and Report Jobs in Policy Views

Configuring Job Priority
Schedule Manager – An Overview
The Schedule Manager (nvsched) runs on the NVBU Server and performs the

The Schedule Manager manages the job schedules and queues. The
Schedule Manager initiates the Job Manager to launch a job instance, and
reschedules the next instance for recurring jobs. The actual job execution is
carried out by the Job Manager.

The Scheduler Manager manages the Scheduler database. It updates the
Status and Jobs tabs on the NVBU Jobs window, which provide an interface
to view the Scheduler records. The Schedule Manager is also responsible for
providing job scheduling data to the NVBU Reporting Tool.
The default behavior and properties of Schedule Manager can be changed using
the Schedule Manager tab on the Configurator.
10.2.0
Customizing NVBU Job Status Views
The job status records can be viewed from the following interfaces:

The Status tab of the NVBU Jobs window

Under Job Status on the NVBU Status window
By default, NVBU displays the status records for 7 days and then removes them
from NVBU Console. To customize this setting, perform the following steps:
1. Click the Schedule Manager tab on the Configurator.
70
Chapter 10
Customizing the Schedule Manager Process
Figure 10-1:
Schedule
Manager tab

Number of Days to Keep Job Status – Enter or select the display period
for status records. The display period is specified in number of days. The
default value for this parameter is 7 days. Note that this setting just hides
the display of job status records on NVBU Console. It does not delete the
records from the Scheduler database. For details on deleting records from
the Scheduler database after a specific period, refer to Customizing
NVBU Job Status Views on page 69.
10.3.0
Creating a User-Defined Policy for Retaining
Job History
The default retention period for job history is 90 days. The Schedule Manager
deletes the job status records after 90 days. To change the retention period for job
status records, perform the following steps:
a. Number of Days to Keep Report Job Histories in the Database – Enter
or select the retention period for report jobs history. The default value for
this parameter is 90 days.
b. Number of Days to Keep Other Job Histories in the Database – Enter
or select the retention period for backup and restore jobs history. The
default value for this parameter is 90 days.
Configuration Guide
10.4.0
71
Defining a Retention Period for Non-Recurring
Job Definitions
NVBU does not have a finite retention period for the job definitions of ad hoc and
non-recurring jobs. These records are never deleted from the Scheduler database.
To configure a finite retention period for these job definitions, perform the following
steps:

Number of Days to Keep Non-Scheduled Jobs in the Database –
Enter or select the retention period for ad hoc and non-recurring jobs. The
retention period is specified in number of days. The default value for this
parameter is 0 (zero). It implies that the job definitions of ad hoc and nonrecurring jobs are retained indefinitely.
10.5.0
Configuring Maximum Simultaneous Jobs
By default, NVBU supports a maximum of 50 simultaneous jobs. It includes
backup, restore and report jobs. To change the number of simultaneous jobs,

Maximum Simultaneously Active Jobs – Enter or select the total
number of simultaneous jobs. Note that each active job requires some
amount of shared memory. An increase in the number of active jobs might
have an impact on the overall performance of NVBU. The default value for
this parameter is 50.
10.6.0
Including Report Jobs in the Job Views
By default, NVBU does not display the Report jobs on NVBU Jobs and NVBU
Status windows. To add these jobs to the job views, perform the following steps:

Exclude Reports Jobs From Jobs Management Views – Clear this
check box.
72
Chapter 10
10.7.0
Including Restore and Report Jobs in Policy
Views
By default, NVBU does not display the restore and report jobs on the NVBU
Policy Management window. To add these jobs to the policy views, perform the
following steps:

Exclude Reports Jobs From Policy Management Views – To view
report jobs on the NVBU Policy Management window, clear this check
box.

Exclude Restore Jobs From Policy Management Views – To view
restore jobs on the NVBU Policy Management window, clear this check
box.
10.8.0
Configuring Job Priority
The Schedule Manager assigns a priority level for each job type, which is applied
globally to all backup, restore and report jobs. This parameter helps prioritize
resource allocation when two or more jobs are scheduled to run at the same time.
The default priority level for each job type is given below:
Job Type
Priority Level
Restore
20
Backup
30
Report
50
You can globally change the priority level settings for all backup, restore, and
report jobs, or override these settings for an individual job. The global settings can
be configured from the Schedule Manager tab of the Configurator. The priority
level ranges from 1 (highest priority) to 100 (lowest priority). A priority level of zero
sets a job to run as a background task. To override the priority settings for an
individual job, refer to the chapter on scheduling job in the Quest NetVault Backup
Administrator’s Guide.
Configuration Guide
73
To change the default priority settings, perform the following steps:

Default Backup Job Priority – Enter or select the priority level for backup
jobs. The default value for this parameter is 30.

Default Restore Job Priority – Enter or select the priority level for restore

Default Report Job Priority – Enter or select the priority level for report
74
Chapter 10
Configuration Guide
75
Chapter 11:
CONFIGURING SHARED
MEMORY SETTINGS
11.1.0

Process Manager – An Overview

Tuning Shared Memory Allocation
Process Manager – An Overview
The Process Manager (nvpmgr) runs on all NVBU machines and manages all
other NVBU processes. It creates and destroys the transient NVBU processes.
The Process Manager also manages the allocation of the shared memory area for
the process table, trace buffers and progress buffers. You can tune the shared
memory settings from the Process Manager tab on the Configurator.
Note: The NVBU Service should be restarted to apply any changes to the Process
Manager settings.
11.2.0
Tuning Shared Memory Allocation
To tune the shared memory settings, perform the following steps:
1. Click the Process Manager tab on the Configurator.
2. On the Process Table tab, configure the following parameters:
Figure 11-1:
Process
Manager tab

Shared Memory Used for Process Table – This parameter controls the
amount of shared memory allocated to the Process Table, which
maintains the details of all current NVBU processes. The default value for
this parameter is 2000KB on Windows, and 500KB on Linux. On NVBU
machines running a number for concurrent processes (e.g., NVBU Server
and SmartClients), you can increase the amount of shared memory for the
Process Table to get optimum performance.
76
Chapter 11
Configuring Shared Memory Settings
To increase the shared memory for the Process Table, enter or select the
new value in Shared Memory Used for Process Table. The shared
memory is allocated in KB.
Note that Windows supports dynamic shared memory allocation. On
Linux/UNIX based platforms, the shared memory for the process table is
allocated from the shared memory pool. To increase the shared memory
for the process table on Linux/UNIX platforms, you need to first increase
the overall shared memory pool. This can be done by configuring the
shmmax variable in the system configuration file. For details on
increasing the shared memory pool, consult the relevant O/S
documentation.

Shared Memory Allocated to the Trace Buffer of Each Process – This
parameter controls the amount of shared memory allocated to the
individual trace buffers of the NVBU processes. The default value for this
parameter is 7KB on all platforms. To increase the shared memory for
individual trace buffers, enter or select the new value in Shared Memory
Allocated to the Trace Buffer of Each Process. The shared memory is
allocated in KB.

Shared Memory Allocated to a Progress Buffer – This parameter
controls the amount of shared memory allocated to the individual progress
buffers of the data plug-ins. The progress buffers are used to share the
job progress data that is displayed on the Job Monitor window. The
default value for this parameter is 1KB on all platforms. To increase the
shared memory for progress buffers, enter or select the new value in
Shared Memory Allocated to a Progress Buffer. The shared memory is
allocated in KB.

Number of Progress Buffers Available to Plug-ins – This parameter
controls the total number of progress buffers available to the plug-ins
running on the NVBU Clients. The progress buffers are used to share the
job progress data that is displayed on the Job Monitor window. The
default value for this parameter is 100 on all platforms. To increase the
shared memory for progress buffers, enter or select the new value in
Number of Progress Buffers Available to Plugins.
Configuration Guide
77
Chapter 12:
CONFIGURING NVBU FOR
FIREWALLS

Firewall Settings – An Overview

12.1.0
Firewall Considerations

Configuring Firewall Settings on NVBU Machines

Defining Filtering Rules on the Firewall
Firewall Settings – An Overview
The firewall settings enable communication with NVBU Clients that are located
outside the firewall. These settings provide the TCP/IP port specifications, which
are used to establish data transfer channels, message channels, and broadcast
channels through the firewall. NVBU has the following port requirements in a
firewall-protected environment:

Data Transfer Channel

Listen Ports for Devices – Ports to listen on for device requests. It needs
to be configured on NVBU machines which have a locally-attached
device, for example, NVBU Server or a SmartClient.
Ports Required – 2 ports per drive

Connect Ports for Devices – Ports used by NVBU Plug-ins to connect to
remote physical or virtual tape devices. It needs to be configured on
NVBU Clients which connect to remote devices.
Ports Required – 2 ports per drive

Message Channel

Listen Ports for Message Channels – Ports for receiving messages
during data transfers. It needs to be configured on both the NVBU Server
and the Client.
Ports Required – 3 ports per client.
To run two or more plug-ins simultaneously on a client, configure 2 ports
per plug-in plus an additional port per client. For example, to run 2 plug-ins
simultaneously, configure (2 * 2) + 1 = 5 ports for a client.

Connect Ports for Message Channels – Ports for sending messages
during data transfers. It needs to be configured on both the NVBU Server
and the Client.
78
Chapter 12
Configuring NVBU for Firewalls
Ports Required – 3 ports per client.
To run two or more plug-ins simultaneously on a client, configure 2 ports
per plug-in plus an additional port per Client. For example, to run 2
plug-ins simultaneously, configure (2 * 2) + 1 = 5 ports for a client.

Broadcast Channel

Connect Ports for Inter-Machine Setup – Ports for establishing initial
contact while adding an NVBU Client, and subsequently to ascertain its
availability.
Ports Required – 2 ports per client

NDMP Control and Data Channel

Connect Ports for NDMP Control Channels – Ports for sending NDMP
messages (NDMP control channels). It needs to be configured on the
NVBU Server (on which the Plug-in for NDMP is installed) when a firewall
separates an NDMP Filer and the NVBU Server. By default, NVBU uses
port number 10000, but it can be changed.

Listen Ports for NDMP Data Channels – Ports to listen on for NVBU
devices operating as NDMP movers. It needs to be configured on the
NVBU Server or SmartClient to which the device is attached. It is required
for data transfers between an NDMP Filer and this device when a firewall
separates the two.
The port specifications are configured from the Firewall tab on the Configurator.
12.1.1
Firewall Considerations
Consider the following when configuring the firewall settings:

For NVBU Clients that are outside the firewall, you need to set the Outside
Firewall parameter on the Client Management window in order to apply the
firewall settings during Server-Client communication. For details on setting
this parameter, refer to the Quest NetVault Backup Administrator’s Guide.

NVBU uses port number 20031 for TCP and UDP messaging. Make sure that
this port is open on the firewall.

NVBU does not support firewalls using NAT (Network Address Translation)/IP
Masquerading.

For requirements on filtering rules for NVBU traffic, refer to Defining Filtering
Rules on the Firewall on page 80.
Configuration Guide
12.2.0
79
Configuring Firewall Settings on NVBU
Machines
To facilitate communication between NVBU Server and Clients through a firewall,
1. Click the Firewall tab on the Configurator.

Valid Listen Port for Devices

Valid Connect Port for Devices

Valid Listen Port for Message Channels

Valid Connect Port for Message Channels

Valid Connect Port for NDMP Control Channels

Valid Listen Port for NetVault NDMP Data Channels

Valid Connect Ports for Inter-machine Connection Setup
For details on these parameters, refer to Firewall Settings – An Overview on
page 77.
Figure 12-1:
Firewall tab
The ports or port ranges can be specified as follows:

A comma-separated list (for example, 20000, 20050)

A port-range separated by a dash (for example, 20000-20100)

A combination of comma-separated list and port-range
(for example, 20000-20050, 20100)
Note: You can specify different ports or port-ranges for data transfer, message,
and broadcast channels. However, for ease of administration, it is recommended
that you configure the same port-range for these parameters across all NVBU
machines. An example is shown in the figure below.
80
Chapter 12
Configuring NVBU for Firewalls
Figure 12-2:
Example
showing
TCP/IP
specification
on Firewall tab
12.3.0
Defining Filtering Rules on the Firewall
Refer to the following table when setting up filtering rules on the firewall to allow
NVBU traffic:
From
To
TCP/
UDP
Server
Client
Client
Source Port
Destination Port
TCP
Valid Connect Ports for InterMachine Connection Setup (as
specified on the NVBU Server)
20031
Server
TCP
Valid Connect Ports for InterMachine Connection Setup (as
specified on the NVBU Client)
20031
Server
Client
TCP
Valid Connect Ports for
Message Channels (as
specified on NVBU Server)
Valid Listen Ports for
specified on the NVBU
Client)
Client
Server
TCP
Valid Listen Ports for Message
Channels (as specified on the
NVBU Client)
specified on the NVBU
Server)
Server
Client
UDP
20031
20031
Client
Server
UDP
20031
20031
Server
Client
TCP
Valid Listen ports for Devices
(as specified on the NVBU
Server/SmartClient)
Devices (as specified on the
NVBU Client)
Client
Server
TCP
Valid Connect Ports for Devices Valid Listen ports for Devices
(as specified on NVBU Client)
(as specified on NVBU
Server/SmartClient)
Configuration Guide
81
Chapter 13:
CONFIGURING PLUG-IN
OPTIONS

Configuring CLI Options

13.1.0
Enabling Enhanced Job Completion Status for nvjobstart
Configuring the Disk Devices Plug-in

Configuring Disk Space Margins for VTLs

Disabling Disk Space Checks for VTLs

Creating VTLs with Entry/Exit Ports
Configuring the Verify Plug-in

Performing Backup Verification Locally for All Clients

Configuring a Default Client for Backup Verification

Defining Clients Which Run Verification Job Locally

Other Subtabs on the Plugin Options Tab

Configuring Quest NetVault Backup Plug-in for Encryption
Configuring CLI Options
The default settings for the NVBU CLI commands can be configured from the CLI
subtab on the Plugin Options tab.
13.1.1
Enabling Enhanced Job Completion Status for
nvjobstart
By default, the nvjobstart command returns either 0 or 1 to indicate the following
job completion states:
Exit Code
Output Message
0
Job completed successfully
1
Job failed with error: ‘Job Failed’
This message is returned for the following job completion
states:
Job failed
Job completed with warnings
Job aborted
Job stopped
Job died
82
Chapter 13
Configuring Plug-in Options
To configure the nvjobstart utility to return specific codes and output messages
that indicate the way in which a job failed, perform the following steps:
1. Click the Plugin Options tab on the Configurator.
2. Click the CLI subtab.
Figure 13-1:
CLI subtab

nvjobstart Enhanced Job Completion Status – Select this check box
on the NVBU Server or Client on which you will run the nvjobstart
command. The enhanced job completion status codes and messages
include the following:
Exit Code
Output Message
0
Job completed successfully
1
Job Failed
2
Job Completed with Warnings
3
Job Aborted
4
Job Stopped
5
Job Died
-1
Job Failed with Undefined Error
13.2.0
Configuring the Disk Devices Plug-in
The Disk Devices Plug-in is a built-in plug-in which allows you to emulate virtual
tape libraries on the disk. The default settings for the Disk Devices Plug-in can be
customized using the Configurator.
13.2.1
Configuring Disk Space Margins for VTLs
Before creating a VTL, NVBU performs a disk space check to ensure that the
target disk has sufficient space to accommodate the new VTL. The free space
required on the disk is calculated as follows:
Number of Slots * Media Capacity + <x>
<x> is the additional disk space considered for the following requirements:
Configuration Guide
83

Disk space required to create the directory structure for the VTL. It varies for
different file systems.

Disk space required by other applications running on the system.
By default, the additional space requirement is set to 20MB. To change this
setting, perform the following steps:
2. Click the Disk Devices Plugin subtab.
Figure 13-2:
Disk Devices
Plugin subtab

Free Disk Space Margin to be Used When Calculating Available Disk
Space – Enter or select the amount of space to be added while
calculating the free space required on the disk. The default value for this
parameter is 20MB.

Unit Used to Express the Free Disk Space Margin In – Enter or select
the unit used to specify the disk space margin. The unit can be MB or GB.
13.2.2
Disabling Disk Space Checks for VTLs
On normal file systems you can use the disk space check feature to avoid errors
during VTL creation. However, on third-party deduplication appliances and
compressed file systems, it is recommended that you disable this feature. To
disable disk space checks for VTLs, perform the following steps:

Check Available Disk Space before Creating Disk Libraries – Clear
this check box.
84
Chapter 13
13.2.3
Creating VTLs with Entry/Exit Ports
To create VTLs which have entry/exit ports, perform the following steps:

Allow Disk Libraries to Have Entry/ Exit Ports – Select this check box.
13.3.0
Configuring the Verify Plug-in
The Verify Plug-in is a built-in plug-in which allows you to check the correctness
and completeness of a backup at the end of data transfer. It verifies the stream
length written to the media and makes sure that no blocks were dropped during
backup. While the actual backup runs as phase 1, backup verification runs as
phase 2 of the backup job. By default, the verification job runs on the NetVault
Backup Server. To avoid data transfers over the network, you can choose to run
verification locally on the SmartClients to which the target device used for the
backup is connected. The target client for the verification job can be configured
from the Verify tab on the Configurator.
13.3.1
Performing Backup Verification Locally for All Clients
NVBU allows you to run the verification jobs locally on the NVBU Clients rather
than the NVBU Server. You can use this feature for SmartClients to avoid data
transfers over the network. However, this option is globally applied to all Clients,
which will not work for Heterogeneous Clients without a locally-attached backup
device. To run backup verification locally for all Clients, perform the following
steps:
Important: This procedure should be performed on the NVBU Server.
1. Click the Verify tab on the Configurator.
Figure 13-3:
Verify tab

Always Run Verify Locally – Select this check box.
Configuration Guide
13.3.2
85
Configuring a Default Client for Backup Verification
NVBU allows you to configure an alternate client to run all the backup verification
jobs. This is useful if you use a SmartClient-attached device for your backups. It
allows you to select the same client to run backup verification jobs. To configure a
default client for backup verification jobs, perform the following steps:

Default Client to Run Verify – Enter the NVBU SmartClient name on
which you want to run all verification jobs.
13.3.3
Defining Clients Which Run Verification Job Locally
NVBU allows you to define a list of SmartClients on which the verification job runs
locally, whereas for the others it runs on the NVBU Server. This feature is useful if
your backup jobs are distributed across multiple SmartClient-attached devices. To
create a list of NVBU SmartClients which will run the backup verification jobs
locally, perform the following steps:

Comma Separated List of Clients that Verify Locally – Provide a
comma-separated list of NVBU SmartClients which will run the backup
verification jobs locally.
13.4.0
Other Subtabs on the Plugin Options Tab
The remaining subtabs on the Plugin Options tab contain the default settings for
the NVBU built-in and optional plug-ins, which can be configured using the
following methods:

Using NVBU Configurator

Using the Configure window which can be accessed from the NVBU
Backup window

Using Remote Configurator
86
Chapter 13
When you install an optional plug-in, a new subtab corresponding to that plug-in is
automatically added to the Plugin Options tab. For details on configuring the
default settings for NVBU built-in and optional plug-ins, refer to the respective
Plug-in User’s Guide. The guide names are listed below:

Consolidate – Refer to the Quest NetVault Backup Built-in Plug-ins User’s
Guide

Data Copy – Refer to the Quest NetVault Backup Built-in Plug-ins User’s
Guide

NetVault Database Backup – Refer to the Quest NetVault Backup Built-in
Plug-ins User’s Guide

Plug-in for FileSystem – Refer to the Quest NetVault Backup for FileSystem
User’s Guide

Optional Plug-ins – Refer to the respective plug-in user’s guide.
Note: The Duplicate Plugin subtab on the Plugin Options tab is only relevant for
NVBU versions prior to v7.4. For later versions use the Duplicate options
provided on the Advanced tab of the NVBU Backup window. For details on these
options, refer to the Quest NetVault Backup Administrator’s Guide.
13.5.0
Configuring Quest NetVault Backup Plug-in for
Encryption
Quest NetVault Backup Plug-in for Encryption (Plug-in for Encryption) provides
support for CAST-128, AES-256 and CAST-256 algorithms to meet regulatory
requirements. When installed on the NVBU Client, the Plug-in for Encryption
encrypts and transfers data across the network to the backup device, where it
remains encrypted until restored to the NVBU Client. If encryption is only required
for secondary storage, NVBU’s job-level encryption offers the choice of encrypting
only the secondary copy, while the primary backup remains unencrypted to shrink
the backup window. When using NVSD, NVBU’s job-level deduplication allows
you to separate deduplicated data from non-deduplicated unencrypted data for
optimal deduplication ratios and performance.
The default settings for this plug-in is configured from the Encryption tab on the
Configurator. For details, refer to the Quest NetVault Backup Plug-in for
Encryption User's Guide.
Configuration Guide
87
Chapter 14:
CONFIGURING NVBU
NOTIFICATION SETTINGS
14.1.0

Events and Notification Methods – An Overview

Configuring Mail Server for Event Notifications

Configuring Recipients for Email Notifications

Configuring a Default Printer on Windows

Configuring Network Manager Host for SNMP Trap Notifications
Events and Notification Methods – An Overview
An event can be described as any significant occurrence within the NVBU system
that you want to be notified about. It can be a user action, a system event or a
state change event. The events can indicate an error or a problem, or just
completion of a task. NVBU events can be predefined or user-defined. When
these events are raised, you can set up the following methods to receive
notification:

Sysop Emails and User Emails

Operator Messages

Print Report

Run a Job

SNMP Trap
For details on NVBU events and notification methods, refer to the Quest NetVault
Before using the following notification methods, you need to configure the
applicable default settings:

Sysop Emails and User Emails – Mail Server address and the mail ID of
Sysop (NVBU Administrator).

Print Report – A default printer on Windows. Alternatively, you can set up the
NVPRINTER variable on a per-job basis.

SNMP Trap – Network Manager Host address and authentication details.
The default settings for the notification methods can be configured from the
Notification tab on the Configurator.
88
Chapter 14
Configuring NVBU Notification Settings
14.2.0
Configuring Mail Server for Event Notifications
To configure a Mail Server for email notifications
1. Click the Notification tab on the Configurator.
2. On the Mail Server subtab, configure the following parameters:
Figure 14-1:
Mail-Server
subtab

Outgoing E-mail Server (SMTP) – Enter the machine name or IP
Address for the Mail Server.

Port Number – This parameter is set to the default SMTP listener port
(that is, port number 25). Update the port number if the Mail Server is
configured to listen on a different port.

NetVault’s E-mail Address – Enter the sender’s email address for
notifications.

NetVault’s Real Name – Enter the sender’s name for email notifications.

Perform Authentication – You can select this check box if your Mail
Server supports LOGIN or PLAIN protocols.

Authentication Account – If you have selected the Perform
Authentication check box, then use this parameter to specify a user
account for SMTP authentication.
If you leave this parameter blank, then NVBU will obtain the user name
from the NetVault’s E-mail Address parameter. For example, if you
specify “[email protected]” in NetVault’s E-mail Address, then
NVBU will use “user1” from this address for SMTP authentication.

Authentication Password – Enter the password for the account that will
be used for SMTP authentication.
Configuration Guide

89
Use Hostname Instead of nvsendmail – Select this check box to use the
Fully Qualified Domain Name (FQDN) instead of nvsendmail with the
EHLO and HELO commands. NVBU uses the hostname in the mail server
messages, so the system needs to be set up with an FQDN to display the
hostname in FQDN format.
14.3.0
Configuring Recipients for Email Notifications
To configure the recipient email addresses for email notifications
2. Click the Global Notification subtab.
Figure 14-2:
Global
Notification
subtab on
Notification tab

Enter Email Address of System Administrator – Enter the recipient’s
email address. Use a comma (,) to separate multiple email addresses.

Real Name of System Administrator – Enter the recipient’s real name.
14.4.0
Configuring a Default Printer on Windows
To configure a default printer for the Print Report notification method on
Windows-based NVBU Servers, perform the following steps
2. Click the Default Printer subtab.
Figure 14-3:
Default Printer
subtab on
Notification tab

Default Printer Name – Enter the name of the printer. Specify the exact
string that is used to identify the printer within the Windows OS.
90
Chapter 14
Configuring NVBU Notification Settings
14.5.0
Configuring Network Manager Host for SNMP
Trap Notifications
To use the SNMP Trap notification method, complete the following configuration
procedure:
2. Click the SNMP Traps subtab.
Figure 14-4:
SNMP Traps
subtab on
Notification tab

Trap Target Host – Enter the network name or the FQDN (Fully Qualified
Domain Name) of the Network Manager Host to which you want to send
the SNMP trap notifications.

Port Number – This parameter is set to the default listener port for SNMP
traps (that is, port number 162). Update the port number, if the host is
configured to listen on a different port.

Community String – An SNMP community string is a password that is
used to authenticate messages that are sent between the Network
Manager Host and the agent. The community string is included in every
packet that is transmitted between the SNMP manager and the SNMP
agent. This parameter is set to “public”, which is the default read-only
community string for most network devices. It is recommended that you
modify this default string and set a new password for SNMP traps.
Configuration Guide
CUSTOMIZING
15.1.0
91
Chapter 15:
THE

Configuring Refresh Rates

Configuring Custom Color Codes for Job Status

Removing Target Set Checks for Duplication Jobs

Customizing NVBU Logs Window

Disabling NVBU Logs Window

Customizing Device Log Views

Hiding Device Logs

Configuring a Default Browser on Linux/UNIX

Configuring View-Levels for Mac OS X
NVBU
CONSOLE
Configuring Refresh Rates
The refresh rate determines how often records are retrieved from the log files and
databases and updated on NVBU Console in order to display the most recent
information. It applies to the following NVBU components:

Job status

Policies

Devices

Job progress

Operator messages
You can change the default refresh rates from the Refresh Rates subtab on the
GUI tab. These values are set in <x> milliseconds. You can configure lower values
for quicker updates. However, before making any changes to the default values,
consider the following:

Lower values may increase load on the CPU.

It may also adversely affect the network traffic when NVBU Console is
running on a remote machine.
To change the refresh rates for NVBU Console, perform the following steps:
2. On the Refresh Rates subtab, configure the following parameters:
92
Chapter 15
Customizing the NVBU Console
Figure 15-1:
Refresh-Rates
subtab on GUI
tab

Job Refresh Rate in Milliseconds – Enter or select the refresh rate for
the NVBU Jobs window. The refresh rate is specified in milliseconds. The
default value for this parameter is 1000 milliseconds.

Policy Tree Refresh Rate in Milliseconds – Enter or select the refresh
rate for policy tree on the NVBU Policy Management window. The
refresh rate is specified in milliseconds. The default value for this
parameter is 2000 milliseconds.

Device Refresh Rate in Milliseconds – Enter or select the refresh rate
for device tree on the NVBU Device Management window. The refresh
rate is specified in milliseconds. The default value for this parameter is
1000 milliseconds.

Job Monitor Refresh Rate in Milliseconds – Enter or select the refresh
rate for job progress details on the NVBU Job Monitor window. The

Operator Messages Refresh Rate in Milliseconds – Enter or select the
refresh rate for operator messages on the NVBU Status window. The
15.2.0
Configuring Custom Color Codes for Job Status
For job entries in the NVBU Jobs and NVBU Status windows, NVBU uses the
following background colors by default:
Job Status
Background Color
Running Jobs
Yellow
Scheduled Jobs
Blue
Completed Jobs
White (Normal)
Configuration Guide
93
To configure custom color codes for job status, perform the following steps:
2. Click the Colors subtab.
Figure 15-2:
Colors subtab
on GUI tab

Color of Scheduled Jobs – Enter the RGB value for the color that you
want to use for scheduled jobs. The default background color for this job
status is blue.

Color of Running Jobs – Enter the RGB value for the color that you want
to use for the currently running jobs. The default background color for this
job status is yellow.

Color of Completed Jobs – Enter the RGB value for the color that you
want to use for completed jobs. The default background color for this job
status is white.
15.3.0
Removing Target Set Checks for Duplication
Jobs
By default, target sets are mandatory for duplication jobs. To prevent drive
deadlocks, NVBU does not allow you to run duplication jobs without a target set.
However, you can override this default setting and make target sets optional. To
remove target set checks for duplication jobs, use the following steps:
Warning: Although it is possible to configure NVBU to run duplication jobs without
a target set, it is recommended that you do not use this option. Be aware that you
risk a drive deadlock state, if you do not target a particular device for backup
duplication. It is recommended that you designate specific drives for duplication
jobs to prevent deadlocks. For example, if you have a library with 4 drives, you can
select drives 1 and 2 for actual backups, whereas drives 3 and 4 for duplication
jobs.
94
Chapter 15
2. Click the Jobs subtab.
3. On the Jobs subtab configure the following parameter:
Figure 15-3:
Jobs subtab
on GUI tab

Permit Duplicate Phase With No Target Set – By default, NVBU
requires that you specify a target set for the duplication jobs. To make it
optional, select this check box.
15.4.0
Customizing NVBU Logs Window
A large amount of logs can significantly increase the time it takes to open the
NVBU Logs window. This problem can be avoided by configuring the maximum
number of records displayed in the NVBU Logs window. To configure this setting,
use the following steps:
2. Click the Logging subtab.
Figure 15-4:
Logging
subtab on GUI
tab

Maximum Log Messages in Log Window – Enter or select the
maximum number of logs that can be displayed in the NVBU Logs
window. By default, the NVBU Logs window can display a maximum of
5000 records.
Configuration Guide
15.5.0
95
Disabling NVBU Logs Window
When the NVBU Console is running on a remote client, you can disable the NVBU
Logs window to avoid sending logs over the network. To configure this setting,
use the following steps:

Disable Logs Screen – Select this check box.
15.6.0
Customizing Device Log Views
The device logs are displayed on the Device Logs tab of the NVBU Device
Management window. By default, NVBU displays the logs for two days and then
removes them from the Device Logs tab. To change the number of days the
device logs are displayed on NVBU Console, perform the following steps:
Figure 15-5:
Devices
subtab on GUI
tab

Number of Days of Device Logs – Enter the number of days for which
the device logs are displayed on NVBU Console. The default value for this
parameter is 2 days. Note that this setting just hides the display of logs on
the Device Logs tab. It does not delete the logs. For details on deleting
NVBU logs, refer to Customizing the Log Daemon on page 37.
96
Chapter 15
15.7.0
Hiding Device Logs
To hide all device logs displayed on the Device Logs tab of the NVBU Device
Management window, perform the following steps:

Disable Logs Tab on Device Screen – Select this check box.
15.8.0
Configuring a Default Browser on Linux/UNIX
On Linux and UNIX based platforms, you need to configure a default browser to
view the HTML reports. To accomplish this, perform the following steps:
2. Click the Browser subtab.

UNIX Default Web Browser – Enter the full file path for the browser (for
example, /usr/bin/mozilla, /usr/bin/firefox).

UNIX Browser Switches – Enter any switches that you want to use.
15.9.0
Configuring View-Levels for Mac OS X
The view-level setting determines which configuration options are displayed on the
NVAdmin interface. This setting is only applicable to the native Mac OS X
interface for NVBU. You can use this setting to hide configuration options, and
thereby restrict user access to configuration settings. To change the view-level
settings, perform the following steps:
2. Click the Advanced subtab.
Configuration Guide
97
Figure 15-6:
Advanced
subtab on GUI
tab

Settings View Level – Enter or select a view-level for Mac OS X version
of NVBU. The range of view-level values is 1–14, and the default value is
6. Increasing the view level value increases the number of configuration
settings that are displayed on the NVBU Settings pane.
98
Chapter 15
Configuration Guide
99
Chapter 16:
CONFIGURING GENERAL
SETTINGS FOR NVBU
16.1.0

Relocating Logs and NVDB Directories

Tuning TCP/IP Buffer Sizes

Disabling Pre-installation Compatibility Checks for Packages
Relocating Logs and NVDB Directories
To store the database, logs and temporary files, NVBU creates the following
directories during installation:
Directory Name
Default File Path
Contents
Database
<NVBU Installation Directory>\db
NVBU system files,
configuration files, media and
scheduler database.
Trace
<NVBU Installation Directory>\trace
NVBU trace logs
Log
<NVBU Installation Directory>\logs
NVBU logs
Temporary
<NVBU Installation Directory>\tmp
Temporary files generated
during NVBU operations
Reports
<NVBU Installation Directory>\reports
NVBU report templates and
components
Statistics
<NVBU Installation Directory>\stats
Data collected by the
nvstatsmngr process
You can relocate these directories to another drive or volume to alleviate low disk
space issues.
Note: The NVBU Service should be restarted to apply any changes to these
settings.
To relocate the NVBU logs or database directories
1. Click the General tab on the Configurator.
2. Changing the logs or database location, as necessary:
100
Chapter 16
Configuring General Settings for NVBU
Figure 16-1:
General tab
Note: The directories to which you want to relocate the NVBU logs or databases
should already exist on the target drive or volume. NVBU will not create the
directories if it cannot find them in the specified path.

Database Directory – Enter the new location for the NVDB. You need to
specify the full path.

Trace Directory – Enter the new location for the trace logs. You need to
specify the full path. Due to the volume of data that will be written, it is
recommended that you do not relocate the trace directory to a network
share.

Log Directory – Enter the new location for the log files. You need to
specify the full path.

Temporary Directory – Enter the new location for storing temporary data
for NVBU. You need to specify the full path.
The temporary directory holds the Backup Saveset Index. The free disk
space on this directory should be at least three times the size of the index
file in order to perform backups and restores properly. For example, if the
backup index file is 3GB in size, the temporary directory should have at
least 9GB of free disk space. NVBU will generate warnings and log
messages if the free disk space on temporary directory is insufficient.

Reports Directory – Enter the new location for the Reports directory. You
need to specify the full path.
Configuration Guide

101
Statistics Directory – Enter the new location for storing the data
collected by the nvstatsmngr process. You need to specify the full path.
16.2.0
Tuning TCP/IP Buffer Sizes
In most cases, the default buffer sizes for the TCP/IP sockets are adequate. It is
recommended that you do not change these values. For guidance on optimal
buffer sizes and TCP/IP tuning, refer to your O/S documentation. To adjust the
send and receive buffer sizes according to O/S recommendations, perform the
following steps:

Minimum Network Send Buffer Size – This parameter determines the
minimum send buffer size for a TCP/IP socket. The default value is set to
1KB.

Maximum Network Send Buffer Size – This parameter determines the
maximum send buffer size for a TCP/IP socket. The default value is set to
16384KB.

Minimum Network Receive Buffer Size – This parameter determines
the minimum receive buffer size for a TCP/IP socket. The default value is
set to 1KB.

Maximum Network Receive Buffer Size – This parameter determines
the maximum receive buffer size for a TCP/IP socket. The default value is
set to 16384KB.
To adjust the buffer size, enter or select the new value for the applicable
parameter. The values need to be set in KB.
16.3.0
Disabling Pre-installation Compatibility Checks
for Packages
NVBU performs a pre-installation compatibility check for packages to ensure that
the given package is compatible with the O/S and bit-type. An error is displayed
when you try to install an incompatible NVBU package. If for any reason you want
to disable this check, perform the following steps:
102
Chapter 16
Configuring General Settings for NVBU

Package Install System Check – This check box is selected by default.
To disable pre-installation package compatibility checks, clear the check
box.
Warning: It is recommended that you do not disable the compatibility checks for
packages. You risk installing an incompatible package if this check is disabled.
Configuration Guide
CONFIGURING
103
Chapter 17:
THE
REPORTING
SYSTEM

NVBU Reporting System – An Overview

Statistics Manager and Reports Database Manager – An Overview

Customizing the Output Format

Customizing the HTML Output Format

Customizing the Plain Text Output Format

Customizing the CSV Output Format

Configuring the Default Output Format for User-Defined Components

Configuring the Filter View

Configuring the Retention Period for Historic Reports

Enabling “Keep Filtered Out Records” for All Reports

Customizing Statistics Manager

Configuring Statistics Collection and Transmission Parameters

Disabling Statistics Collection on an NVBU Client

Creating User-Defined Purge Policies

Creating a Global Policy for Purging the Reports Database

Creating a User-defined Schedule for Purging Report Tables

Disabling Global Purge Policy for Reports Database

Creating a Purge Policy for the “Default” Table

Creating a Purge Policy for Individual Report Tables

Applying Global Purge Policy to Individual Report Tables
104
Chapter 17
Configuring the Reporting System
17.1.0
NVBU Reporting System – An Overview
NVBU offers an advanced reporting system which can be used to generate
Canned and Custom reports in the following formats:

HTML

Plain text

Comma Separated Value (CSV)
For details on the features and functionality of the NVBU reporting system, refer to
the Quest NetVault Backup Administrator’s Guide.
The reporting system obtains data from the NVDB, which includes the media and
the scheduler databases, audit and process logs, and persistent information for
clients, devices, users, and other NVBU components. The NVBU reporting system
is also supported by the following processes:

Statistics Manager

Reports Database Manager
The Statistics Manager and the Reports Database Manager collect and store
additional data for the reporting system. You can customize these processes and
configure the default settings for the reporting system from the Reporting tab on
the Configurator.
17.2.0
Statistics Manager and Reports Database
Manager – An Overview
The Statistics Manager (nvstatsmngr) runs on the NVBU Server as well as NVBU
Clients, whereas the Reports Database Manager (nvrepdbmngr) only runs on the
NVBU Server. The Statistics Manager collects the following data for the NVBU
reporting system:

Drive statistics

Event history

Media requests

Server capacity

Transfer information
The Reports Database Manger polls the Statistics Manager at periodic intervals to
get the collected data, and writes the data to the reports database. It provides the
information in the reports database to the NVBU reporting tool and performs
periodic purging of the reports database. You can customize the Statistics
Manager and the Reports Database Manager from the Reporting tab on the
Configurator.
Configuration Guide
17.3.0
105
Customizing the Output Format
This section describes how to customize the output format for the HTML, Plain
Text and CSV reports.
17.3.1
Customizing the HTML Output Format
NVBU uses built-in templates to generate and format the output for HTML reports.
You can customize these settings using Configurator. The custom formatting
styles can be globally applied to all HTML report templates from the HTML Text
Output subtab on the Reporting tab. These settings should only be configured by
users with a good knowledge of HTML. Improper configuration could result in
incorrect output. To customize the output format for the HTML reports, perform the
following steps:
1. Click the Reporting tab on the Configurator.
2. On the HTML Text Format subtab, configure the following parameters:
Figure 17-1:
HTML Text
Output subtab
on Reporting
tab

Pre-text for HTML Output of Plain Text

Post-text for HTML Output of Plain Text

Default HTML Column Header for Pre-text
106
Chapter 17

Default HTML Column Header for Post-text

Default HTML Column Header Field Pre-text

Default HTML Column Header Field Post-text

Default Text to Output for an HTML Report with No Records

Default HTML Total Row Pre-text

Default HTML Total Row Post-text

Default HTML Total Field Pre-text

Default HTML Total Field Post-text

Default HTML Average Row Pre-text

Default HTML Average Row Post-text

Default HTML Average Field Pre-text

Default HTML Average Field Post-text

Default HTML Format Pre-text

Default HTML Format Post-text

Default HTML Format Field Pre-text

Default HTML Format Field Post-text
Use the pre-text parameters to specify the following:

Opening HTML tags for custom formatting styles, for example, font type,
font size, bold, etc.

Text or description for headers, total or average rows, or body cells.
Use the post-text parameters to specify the following:

Closing HTML tags for custom formatting styles.
For reports with no records, you can replace the default text “Nothing to
Display” with your own text in Default Text to Output for an HTML Report
With No Records.
17.3.2
Customizing the Plain Text Output Format
NVBU uses built-in templates to generate and format the plain text reports. You
can customize these settings, and add line breaks, tabs, separators, etc., using
Configurator. The custom formatting can be globally applied to all plain text report
templates from the Plain Text Output subtab on the Reporting tab. These
settings should only be configured by users familiar with the use of control
characters and escape sequences in text output. Improper configuration could
result in incorrect output. To customize the output format for the plain text reports,
Configuration Guide
2. Click the Plain Text Output subtab.
Figure 17-2:
Plain Text
Output subtab
on Reporting
tab

Default Plain Text Column Header Pre-text

Default Plain Text Column Header Post-text

Default Text to Output for a Plain Text Report with No Records

Default Plain Text Total Row Pre-text

Default Plain Text Total Row Post-text

Default Plain Text Total Field Pre-text

Default Plain Text Total Field Post-text

Default Plain Text Average Row Pre-text

Default Plain Text Average Row Post-text

Default Plain Text Average Field Pre-text

Default Plain Text Average Field Post-text

Default Plain Text Format Pre-text

Default Plain Text Format Post-text

Default Plain Text Format Field Pre-text

Default Plain Text Format Field Post-text
107
108
Chapter 17

Line breaks, separators, etc.

Text or description for headers, total or average rows, or body cells

Display” with your own text in Default Text to Output for a Plain Text
Report With No Records.
17.3.3
Customizing the CSV Output Format
NVBU uses built-in templates to generate and format the CSV reports. You can
customize these settings, and define a custom delimiter, or add line breaks, tabs,
separators, etc., using Configurator. The custom formatting can be globally
applied to all CSV report templates from the CSV Output subtab on the
Reporting tab. These settings should only be configured by users familiar with
CSV output and the use of control characters and escape sequences. Improper
configuration could result in incorrect output. To customize the output format for
the CSV reports, perform the following steps:
2. Click the CSV Output subtab.
Figure 17-3:
CSV Output
subtab on
Reporting tab

Default CSV Column Header Pre-text

Default CSV Column Header Post-text

Default CSV Header Field Pre-text

Default CSV Header Field Post-text
Configuration Guide

Default Text to Output for a CSV Report with No Records

Default CSV Format Pre-text

Default CSV Format Post-text

Default CSV Format Field Pre-text

Default CSV Format Field Post-text
109

Line breaks, tabs, separators, etc.

Text or description for headers, total or average rows, or body cells

Custom delimiter

Export” with your own text in Default Text to Output for a CSV Report With
No Records.
17.4.0
Configuring the Default Output Format for
User-Defined Components
By default, the output format for user-defined components is set to HTML. To
change this setting, perform the following steps:
2. Click the Misc subtab.
Figure 17-4:
Output types
listed on Misc
subtab

Default Output Type – For plain text format, select Plain Text in the
Default Output Type list. Alternatively, select Comma Separated Values
in the list to set CSV as the default output format.
110
Chapter 17
17.5.0
Configuring the Filter View
NVBU provides two views to create and view filter expressions for reports:

Simple

Advanced
The Simple view lists the filter expressions in a tabular format. This view is
recommended for users who do have advanced knowledge of Structured Query
Language (SQL). The Advanced view uses a tree structure to display the filter
expressions. This view is intended for users with advanced knowledge of SQL.
By default, the view mode for filter expressions is set to Simple. To change this
setting, perform the following steps:
Figure 17-5:
Misc subtab
on Reporting
tab

Default Filter View – To use the Advanced filter view by default, select
Advanced in the Default Filter View list.
17.6.0
Configuring the Retention Period for Historic
Reports
NVBU keeps a copy of the data set that was used to generate a report, allowing
you to re-analyze the historic data by applying new settings and filters. By default,
the historic data is retained for 14 days. To change the retention period for historic
data, perform the following steps:
Configuration Guide

111
Duration to Keep Produced Reports – Enter or select the retention
period for historic reports. The default retention period is 14 days.
17.7.0
Enabling “Keep Filtered Out Records” for All
Reports
NVBU keeps a copy of the data set that was used to generate a report, allowing
you to re-analyze the historic data by applying new settings/filters. By default, the
data that is excluded as a result of some filter condition is not saved. The Keep
Filtered Out Records option controls whether or not the excluded data is saved
for a historic report. By default, this option is not enabled. You can select it
individually for each report, or globally enable it for all reports. To globally enable
the Keep Filtered Out Records option for all reports, perform the following steps:

Default Keep Filtered Out Records Setting – To automatically save
excluded data for all reports, select this check box.
17.8.0
Customizing Statistics Manager
To change the default behavior and properties of Statistics Manager, perform the
following steps:
2. Click the Stats Collection subtab.
Figure 17-6:
Stats
Collection
subtab on
Reporting tab
112
Chapter 17

Statistics Gathering Window – By default, the Statistics Manager
collects statistics for 24 hours, starting at 00:00:00 and continuing until
23:59:59 hours. To limit statistics collection to certain times of the day,

Statistics Gathering Window Start – Enter or select the start time for
statistics gathering.

Statistics Gathering Window End – Enter or select the end time for
statistics gathering.
Specify the time in HH:MM:SS format. Note that the maximum duration for
a session is 24 hours. It could last a single calendar day or continue to the
next day. For example, if you set 10:00:00 as the start time and 7:00:00 as
the end time, the session will begin at 10:00 A.M. on the current day and
lasts until 7:00 A.M. the next day.

Frequency – Enter or select the polling frequency for Statistics Manager.
The polling frequency is specified in number of seconds. The default value
for this parameter is 10 seconds

Records per Storage File – Enter or select the maximum number of
statistical records per file. The Statistics Manager will close the current file
and open a new file when this limit is reached. The default value for this
parameter is1000 records.
17.9.0
Configuring Statistics Collection and
Transmission Parameters
Statistics collection is enabled by default on all NVBU Clients. You can disable this
activity on an NVBU Client using the Configurator. Be aware that if you disable
statistics collection, the reports related to drive performance, event history, media
requests, and other data collected by the Statistics Manager will not be accurate.
To disable statistics collection on an NVBU Client, perform the following steps:
2. Click the Stats Provision subtab.
Figure 17-7:
Stats Provision
subtab on
Reporting tab
Configuration Guide

113
Absent Server Threshold – Enter or select how long the Statistics
Manager holds the collected data for the Reports Database Manager on
the NVBU Server. The threshold is specified in number of hours. The
default value for this parameter is 72 hours. If the Reports Database
Manager does not poll for data within this time, a warning will be logged
and the following will occur:

The Statistics Manager will discard all the files that are not transferred
to the reports database.

The Statistics Manager will not store any files until the Reports
Database Manager establishes contact with it.

Transmit Block Size – Enter or select the block size for transmitting data
collected by the Statistics Manager. The block size is specified in KB. The
default value for this parameter is 10KB.

Minimum Stats Manager Cache – Enter the minimum cache for
Statistics Manager. This parameter is set in number of records. By default,
it is set to 30 records.
17.10.0
Disabling Statistics Collection on an NVBU
Client
Statistics collection is enabled by default on all NVBU Clients. You can disable this
activity on an NVBU Client using the Configurator. Be aware that if you disable
statistics collection, the reports related to drive performance, event history, media
requests, and other data collected by the Statistics Manager will not be accurate.
To disable statistics collection on an NVBU Client, perform the following steps:
2. Click the Stats Provision subtab.

Enable Stats Collection on this Machine – Clear this check box.
17.11.0
Creating User-Defined Purge Policies
This section describes how to create user-defined policies for purging the Reports
Database and tables. The information in this section is organized as follows:

Creating a Global Policy for Purging the Reports Database

Creating a User-defined Schedule for Purging Report Tables
114
Chapter 17
17.11.1

Applying Global Purge Policy to Individual Report Tables
Creating a Global Policy for Purging the Reports
Database
The Reports Database Manager uses a global purge policy to delete obsolete
records in the database. The global policy is applied to all the tables in the
database. Accordingly, the Reports Database Manager deletes all records that are
older than 31 days. You can override this behavior with one of the following types
of global policies:

Age-based Purge Policy – Select this policy type to delete records that are
older than a certain number of days.

Size-based Purge Policy – Select this policy type to delete records when the
report tables exceed a certain size.
To create a user-defined global policy for purging the reports database, perform
2. Click the Tables subtab.
3. Select one of the following methods to delete obsolete records:
Figure 17-8:
Parameters
for creating a
user-defined
global purge
policy

Age-based Purge Policy – For a purge policy based on the age of the
records, configure the following parameters:

Global Purge Method – Select By Date in the list.

Global Purge Time Limit – Enter or select the maximum age for the
records. The record age is specified in number of days. The default
maximum age for the records is 31 days.
Size-based Purge Policy – For a purge policy based on the table size,

Global Purge Method – Select By Space Used in the list.
Configuration Guide

115
Global Purge Space Limit – Enter or select the maximum file size for
the report tables. The file size is specified in MB. The default maximum
file size for report tables is 50MB.
4. By default, automatic purging occurs every 24 hours. To change this
schedule, refer to Creating a User-defined Schedule for Purging Report
Tables on page 115.
17.11.2
Creating a User-defined Schedule for Purging Report
Tables
The Reports Database Manager conducts a purge check every 24 hours, and
deletes all records that match the purge condition. To change the interval for purge
checks, perform the following steps:

Purge Check Frequency – Enter or select the time interval between two
purge events. The purge frequency is specified in number of hours.
17.11.3
By default, the global purge policy is applied to all the tables in the reports
database. You can, however, override this behavior for individual tables with tablespecific purge policies. The table-specific policies are only applied when you
disable the global policy at the database level. To disable the global purge policy at
the database level, perform the following steps:

Tables Default to Being Part of the Global Purge Group – Clear this
check box.
17.11.4
The default table is generated and added to the reports database by the custom
reports. By default, the Reports Database Manager applies the global purge policy
116
Chapter 17
to this table. You can, however, replace the global policy with one of the following
types of table-specific policies for purging the default table:

default table exceeds a certain size.
To create a table-specific purge policy for the default table, perform the following
steps:
3. Disable global purge policy at the database level. For details, refer to
Disabling Global Purge Policy for Reports Database on page 115.
4. Select one of the following methods to delete obsolete records:
Figure 17-9:
Parameters for
creating a
user-defined
purge policy
for default
table

Table Default Method – Select By Date in the list.

Table Default Purge Time Limit – Enter or select the maximum age
for the records. The record age is specified in number of days. The
default maximum age for the records is 31 days.

Table Default Purge Method – Select By Space Used in the list.

Table Default Purge Space Limit – Enter or select the maximum file
size for the report tables. The file size is specified in MB. The default
maximum file size for report tables is 10MB.
Tables on page 115.
Configuration Guide
117
17.11.5
By default, the Reports Database Manager applies the global purge policy to all
report tables. You can, however, replace the global policy with one of the following
types of table-specific policies for purging individual report tables:

report tables exceed a certain size.
To create a table-specific purge policy for individual report tables, perform the
following steps:
Figure 17-10:
Tables subtab
118
Chapter 17
3. Disable global purge policy at the database level. For details, refer to
Disabling Global Purge Policy for Reports Database on page 115.
4. Select the required method to delete the obsolete records:

Table <Table Name> Purge Method – Select By Date in the list.

Table <Table Name> Purge Time Limit – Enter or select the
maximum age for the records. The record age is specified in number of
days. The default maximum age for the records is 31 days.
Table-specific policies can be created for the following tables:

Events

Mediacapacities

Mediarequests

Mediatransfers

Driveevents

Driveperformance

Jobfiletallies
Depending on the table for which you are creating the purge policy,
configure the corresponding parameters in steps 1 and 2.

Table <Table Name> Purge Method – Select By Space Used in the
list.

Table <Table Name> Purge Space Limit – Enter or select the
maximum file size for the report tables. The file size is specified in MB.
The default maximum file size for report tables is 10MB.
Table-specific policies can be created for the following tables:

Events

Mediacapacities

Mediarequests

Mediatransfers

Driveevents

Driveperformance

Jobfiletallies
Depending on the table for which you are creating the purge policy,
configure the corresponding parameters in steps 1 and 2.
Configuration Guide
119
Tables on page 115.
17.11.6
Applying Global Purge Policy to Individual Report
Tables
NVBU allows you to create table-specific purge policies for one or more tables
while continue using the global policy for the others in the reports database. To
apply the global policy to an individual table when it is disabled at the database
level, perform the following steps:

Table <Table Name> Purge Method – In the Table <Table Name>
Purge Method list, select Use Global Policy.
The global policy can be applied to the following tables:

Events

Mediacapacities

Mediarequests

Mediatransfers

Driveevents

Driveperformance

Jobfiletallies
Configure the corresponding parameter, depending on the report table for
which you want to use the global policy.
120
Chapter 17
Configuration Guide
121
Chapter 18:
CONFIGURING LANGUAGE
SETTINGS FOR NVBU
18.1.0

Changing Locale Setting

Correcting Locale Changes

Disabling Post-Installation Locale Changes

Configuring Display Properties for Localized Versions

Changing the Font Size for NVBU Console

Changing the Date Format
Changing Locale Setting
NVBU is available in the localized versions:

Chinese (Simplified)

English

French

German

Japanese

Korean
For a localized version of the software, you can select the language during
installation or modify the Language Settings later using the Configurator. The
locale setting for NVBU depend on the O/S locale settings.
Note: The NVBU Service should be restarted to apply any changes to the locale
settings.
To change the locale setting for NVBU
Note: Before proceeding ensure that the Allow GUI to Change Locale check box
on the Language > Locale subtab is selected.
122
Chapter 18
Configuring Language Settings for NVBU
Figure 18-1:
Language
Selection list
on General tab

Language Selection – In Language Selection list at the bottom of the
window, select the preferred language for NVBU.
18.2.0
Correcting Locale Changes
You can use the NVBU txtconfig tool to correct the changes if an incorrect locale
was selected in the Language Selection list. To apply the correct locale settings,
1. On the command prompt, navigate to the ...\bin directory (where ...
represents the NVBU installation directory).
2. Enter txtconfig and press Enter.
3. Enter p and press Enter.
4. Enter the number corresponding to the General page, and press Enter.
5. Enter the number corresponding to the Language Selection option, and
press Enter.
6. Enter the number corresponding to preferred language (for example, 5 for
Japanese). Press Enter.
Configuration Guide
123
7. Enter s and press Enter.
8. Enter q and press Enter.
18.3.0
Disabling Post-Installation Locale Changes
To prevent locale changes after installation, perform the following steps:
1. Click the Language tab on the Configurator.
2. Click the Locale subtab.
3. On the Locale subtab configure the following parameter:
Figure 18-2:
Locale
subtab on
Language tab

Allow GUI to Change Locale – Click to clear this check box.
18.4.0
Configuring Display Properties for Localized
Versions
For non-English versions, NVBU allows you to change the font size and date
formats to match the locale settings. These settings can be configured from the
Language tab on the Configurator.
18.4.1
Changing the Font Size for NVBU Console
NVBU uses font size 8 to display text on NVBU Console. The font size might have
to be increased on non-English versions for better readability. For example, the
Japanese version of NVBU requires font size 9. To change the font size for the text
on the GUI, perform the following steps:
2. On the Font subtab configure the following parameter:
Figure 18-3:
Font subtab on
Language tab

Default GUI Font Point Size – Enter or select the appropriate font-size
depending on the display language for NVBU.
124
Chapter 18
Configuring Language Settings for NVBU
18.4.2
Changing the Date Format
The default date format for NVBU is Day of Week/Day/Month/Year, which can be
changed to Year/Month/Date/Day of Week. To change the default date format,
2. Click the Display subtab.
3. On the Display subtab configure the following parameter:
Figure 18-4:
Display
subtab on
Language tab

Display Date in Order DoW – Select this check box to change the default
date format to Year/Month/Date/Day of Week.
Configuration Guide
SETTING UP
19.1.0
125
Chapter 19:
A
BAKBONE TIME
SERVER

BakBone Time – An Overview

Configuring an Alternate BakBone Time Server
BakBone Time – An Overview
NVBU designates a Time Server, called BakBone Time Server, in order to
synchronize time on all NVBU Server and Clients within the Domain. Typically, the
NVBU Server acts as the BakBone Time Server, and the system time on this
machine is the BakBone Time. However, you can designate any other NVBU
machine as the BakBone Time Server. NVBU ignores the local time on the clients
and uses BakBone Time for all time-specific operations, such as job scheduling,
reporting, and tracing.
19.2.0
Configuring an Alternate BakBone Time Server
By default, the NVBU Server acts as the BakBone Time Server. To establish an
alternate NVBU machine as the BakBone Time Server, complete the following
steps:
1. Click the Time Sync tab on the Configurator.
2. Configure the following parameters on the NVBU Server:
Figure 19-1:
Time Sync tab
Note: The NVBU Service should be restarted to apply any changes to these
settings.

This Machine is the BakBone Time Server – Click to clear this check
box on the NVBU Server which is the default BakBone Time Server.
126
Chapter 19
Setting Up a BakBone Time Server

Synchronize BakBone Time with System – Enter the NVBU Server
which will act as the Time Server.

Number of Ping-Pongs to Determine Time Difference – Enter or select
the number of time packets to exchange while polling. The default polling
count is 5.

Number of Hours between Time Sync Updates – Enter or select how
often the NVBU Server checks to see if it is still synchronized with the
Time Server. The default polling interval is 24 hours.

Number of Milliseconds of Time Difference Allowed between 2
Servers – Enter or select the allowed time variance. By default, NVBU
allows a 1000-millisecond variance between the NVBU Server and the
BakBone Time Server.
Configuration Guide
USING

20.1.0
127
Chapter 20:
THE
TRACE TOOL
Trace Logs – An Overview

Trace Levels

Date and Time in Trace Files

Setting Trace Levels

Enabling Tracing

Disabling Tracing

Enabling Circular Logging of Trace Messages
Trace Logs – An Overview
Tracing is a logging technique that captures diagnostic information related to
events and error conditions occurring within the NVBU system. It is used by Quest
Support to identify and correct problems within the system.
Important: The Trace feature should only be used under the direction of Quest
Support.
Tracing is disabled by default. To generate trace logs, you need to set appropriate
trace levels for various NVBU processes, and activate tracing. Trace logs are
written to the ...\trace directory (where ... represents the NVBU installation
directory). To relocate the trace directory, refer to Relocating Logs and NVDB
Directories on page 99.
By default, NVBU creates a single trace file for each process which continues to
grow as new logs are added to it. The maximum file size depends on the O/S and
file system in use. Through Configurator, you can override this behavior and
configure a the circular tracing method for the trace logs.
20.1.1
Trace Levels
Trace levels specify what type of events and errors are traced, and what level of
detail is recorded in the trace logs. The supported trace levels are listed in the
table below:
128
Chapter 20
Using the Trace Tool
20.1.2
Trace Levels
Level of Detail
DEFAULT
The DEFAULT trace level is equivalent to LIBDEBUG on NVBU v8.5
and later versions. On pre-v8.5 versions, this setting is equivalent to
the LIBVERBOSE trace level.
ALWAYS
Traces all error conditions
NORMAL
Traces high-level application execution path
VERBOSE
Traces low-level application execution path
LIBNORMAL
Traces high-level execution of library functions
LIBVERBOSE
Traces low-level execution of library functions
DEBUG
Traces high-level debug information
LIBDEBUG
Traces low-level debug information
Date and Time in Trace Files
The date and time values in trace logs can be based either on BakBone Time or
local time on the client. BakBone Time is the system time on the BakBone Time
Server which is usually the NVBU Server. It is used to synchronize time on all
NVBU Clients within the Domain. For details on BakBone Time refer to BakBone
Time – An Overview on page 125.
Note: NVBU uses the format hhmmss.mmmmmm (Hours, Minutes, Seconds
and Milliseconds) for the log timestamps in trace files. The update interval for the
millisecond component is operating system dependent.
The Use BakBone Time in Debugging Files check box on the General tab of the
Configurator is selected by default to ensure all date and time values in the trace
logs are based on BakBone Time. This helps in comparing and analyzing trace
output from multiple clients. It is recommended that you leave this check box
selected.
20.2.0
Setting Trace Levels
To set trace levels, perform the following steps:
Note: Your Quest Support Representative will recommend what trace levels to set
for various NVBU processes.
1. Click the Trace Level tab on the Configurator. The trace utility can be used to
capture information about the following processes:
Configuration Guide
129

Configurator

NDMP Library Manager

SVTL Creator

Process Manager

SVTL Library Manager

CLI Proxy Gateway

Communication Manager ACSLS Library Manager Config Manager

Network Manager

Media Manager

Notification Plugin

Script Plugin

Logging Daemon

Reports Producer

GUI

Database Browser

Audit Tool Plugin

Core Plugin

Verify Browser

Consolidate Incremental
Backups

GUI Proxy

Duplicate Browser

Data Copy

Schedule Manager

SysExec Plugin

Disk Device Creator

Job Manager

Utility Plugin

Raw Device

Device Manager

Device Scan

Verify Plugin

NDMP Device Manager

Statistics Manager

File System

SVTL Device Manager

Reports Database
Manager

NetVault Databases

Library Manager

Auditor
Figure 20-1:
Trace Level
tab
When you install an optional NVBU Plug-in, a new process corresponding to
that plug-in is automatically added to the Trace Level tab. The trace utility
can be used to capture information about the new process without any
additional requirement.
130
Chapter 20
2. For each process, the trace level is set to DEFAULT. To set or change the
trace level for a process, select the appropriate Trace Level in the list. The
supported trace levels include the following:

DEFAULT

ALWAYS

NORMAL

VERBOSE

LIBNORMAL

LIBVERBOSE

DEBUG

LIBDEBUG
Important: The NVBU Service should be restarted to apply any changes to the
trace level settings if these changes are made after tracing has been enabled.
20.3.0
Enabling Tracing
Tracing is not enabled by default. You have to start it manually after setting the
trace levels. To enable tracing, perform the following steps:
Figure 20-2:
Trace Settings
on General tab
Configuration Guide
131
2. Select the Generate Debugging Files check box.
4. Restart the NVBU Service.
20.4.0
Disabling Tracing
Once the required trace logs have been obtained, perform the following steps to
stop tracing:

Generate Debugging Files – Clear this check box.
4. Restart the NVBU Service.
20.5.0
Enabling Circular Logging of Trace Messages
By default, NVBU creates a single trace file for each process which continues to
grow as logs are added to it. Circular tracing allows you to split the file by setting
the maximum lines per trace file, and overwrite the oldest file by setting the
maximum number of trace files to retain. For example, if you configure 5000 lines
per trace file and 5 trace files to keep per session, NVBU will write 5000 trace logs
to one file and then create a new file. When the fifth file is filled up, NVBU will
overwrite the first file.To enable circular logging method for the trace files, perform

Lines per Trace File – This parameter determines two properties for
trace files:

Whether circular tracing is enabled or not

When circular tracing is enabled, the maximum number of lines for
each trace file
The default value for the Lines per Trace File option is zero, which
indicates that the circular logging method is not enabled for the trace file.
To enable circular tracing, enter or select the maximum number of trace
lines that can be written to each file. It is set in multiples of 1000 and the
maximum supported value is 32,000. In addition, you need to set the
Trace Files to Keep Per Session parameter.
132
Chapter 20

Trace Files to Keep per Session – Enter the maximum number of trace
files that can be created in a session. A session is valid for an indefinite
time, until the NVBU Service is restarted the next time. The maximum
supported value for this parameter is 1,000. When circular tracing is
enabled, NVBU begins writing trace messages to the first file. When data
exceeds the defined maximum lines, the current file is closed and a new
file is created. An integer is appended to the file name to indicate its
sequence. When the last file gets filled, NVBU starts overwriting the first
file.
Configuration Guide
USING
21.1.0
133
Chapter 21:
THE
TXTCONFIG TOOL

Txtconfig – An Overview

Starting Txtconfig

Customizing the Default Settings Using Txtconfig

Examples

Customizing the Auditor Daemon to Log Failed User Requests

Creating a Size-based Purge Policy for Audit Logs

Customizing the Purge Schedule for Audit Logs
Txtconfig – An Overview
Txtconfig is a text version of the Configurator, which can be used to customize
NVBU settings on machines that do not support a GUI. For example, it can be
used to customize NVBU on Linux/UNIX Clients that neither support a GUI nor
allow remote access to X Window System (X or X11).
The executable file for Txtconfig is named txtconfig and resides in the …\bin
directory (where ... represents the NVBU installation directory). Txtconfig can be
accessed from any directory. It requires root privileges. The settings which are
presented as Configuration Pages are similar to the options provided on the
Configurator.
21.2.0
Starting Txtconfig
To start Txtconfig, perform the following steps:
1. Start a terminal session or command window.
2. Type the following command:
txtconfig
3. Press Enter or Return.
Note: It is recommended that you resize the terminal window, and set the width to
100 characters and height to 30 characters to properly view the Configuration
Pages.
134
Chapter 21
Using the Txtconfig Tool
21.3.0
Customizing the Default Settings Using
Txtconfig
Upon launch Txtconfig opens the Machine page, which displays the NVBU Client
details. To view the configuration options and change the settings, do the
following:

To view the Main Menu, press p.

To open a configuration page, press the corresponding number (for example,
5).

To set or change the value for a parameter, do the following:
Figure 21-1:
Main Menu for
the Windows
version of
Txtconfig
Type of Value
Action
Enable/Disable; On/Off
Just select the option to change its state. It functions as a
toggle key.
List (Numeric)
To select a value from a list, press the corresponding
number, followed by Enter or Return.
Numeric
Type the required number, followed by Enter or Return.
String
Type the required characters, followed by Enter or Return.

To save the changes, press s.

To quit Txtconfig, press q.
Note: For details on various configuration settings, refer to the relevant chapter in
this guide.
Configuration Guide
21.4.0
135
Examples
The following examples show how to change the settings for the Auditor Daemon
using the Windows version of the Txtconfig utility.
Figure 21-2:
Auditing Page
for the
Windows
version of
Txtconfig
21.4.1
Customizing the Auditor Daemon to Log Failed User
Requests
By default, the Auditor Daemon logs each user request, regardless of whether the
request is granted or denied. To override this behavior and generate audit logs
only for the failed user requests, perform the following steps:
1. Open a command window, and type:
txtconfig
Upon launch, the txtconfig utility displays the Machine page.
2. Press p to display the main menu.
3. On the main menu page, press 5.
4. By default, the Only Record Failed Requests in the Audit Trail option is set
to OFF. Press 1 to enable it.
5. To save the new settings to the configuration file, press s.
21.4.2
Creating a Size-based Purge Policy for Audit Logs
To create a size-based purge policy for audit logs, perform the following steps:
txtconfig
4. By default, the Purge Type parameter is set to By Age. To change it, press 2.
5. To select the By Size option, press 2.
6. To specify the maximum file size for audit logs, press 3, and enter the file size
in MB. Press Enter or Return.
136
Chapter 21
Using the Txtconfig Tool
7. To save the new settings to the configuration file, press s.
21.4.3
Customizing the Purge Schedule for Audit Logs
By default, automatic purging occurs every 24 hours. To create a user-defined
schedule for purging audit logs, perform the following steps:
txtconfig
4. To change the purge schedule, press 5.
5. Enter the interval between two purge events, and press Enter or Return.
6. To save the new settings to the configuration file, press s at the prompt.