Quest NetVault Backup - usdownloads.quest…usdownloads.quest.com.edgesuite.net/Repository/support.quest.com... · NVG-103-8.6.x-EN-01 09/29/11 Quest® NetVault® Backup version 8.6.x

NVG-103-8.6.x-EN-01 09/29/11

Quest® NetVault® Backup

version 8.6.x

Configuration GuideVersion: Product Number: NVG-103-8.6.x-EN-01

© 2011 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 HeadquartersLEGAL Dept5 Polaris WayAliso Viejo, CA 92656email: [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 # 5,250,687; 7,814,260; 7,913,043 and 7,979,650. Additional patents pending.

Trademarks

Quest, Quest Software, the Quest Software logo, NetVault are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. 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.

Chapter 1: Introducing Quest NetVault Backup 9

• Quest NetVault Backup – At a Glance ............................................................................ 9• Key Benefits .................................................................................................................... 10• Feature Summary ........................................................................................................... 11• About this Document ..................................................................................................... 12• Target Audience .............................................................................................................. 12• Recommended Additional Reading .............................................................................. 12• About Quest Software .................................................................................................... 13

- Contacting Quest Software ............................................................................................................ 13- Quest Support ................................................................................................................................ 13

Chapter 2: Getting Started 15

• NVBU Configurator – An Overview ............................................................................... 15• Starting NVBU Configurator .......................................................................................... 15

- Starting NVBU Configurator on Linux/UNIX ................................................................................... 15- Starting NVBU Configurator on Mac OS X .................................................................................... 16- Starting NVBU Configurator on Windows ...................................................................................... 16

• Remote Configurator ...................................................................................................... 17- Starting Remote Configurator ........................................................................................................ 17

• Txtconfig .......................................................................................................................... 17

Chapter 3: Performing Common Administrative Tasks 19

• Viewing NVBU Service Status ....................................................................................... 19• Starting and Stopping NVBU Service ........................................................................... 19• Viewing NVBU Machine Details ..................................................................................... 20• Installing Optional Plug-ins ........................................................................................... 21• Removing Plug-ins ......................................................................................................... 22• Licensing Software ......................................................................................................... 22• Viewing License Details ................................................................................................. 23• Changing NVBU Password ............................................................................................ 23• Disabling Password-Protection for NVBU Clients ....................................................... 24

Table of Contents

Table of Contents4

• Allowing NVBU Server to Function as Client ...............................................................24

Chapter 4: Customizing the Auditor Daemon 25

• Auditor Daemon – An Overview .....................................................................................25• Generating Audit Logs for Failed User Requests ........................................................25• Creating a User-Defined Policy for Deleting Audit Logs .............................................26• Creating a User-Defined Schedule for Purging Audit Logs ........................................27• Disabling Automatic Purging of Audit Logs .................................................................27• Configuring Concurrent Sysop Operator Messages ...................................................28

Chapter 5: Customizing the Device Scan Process 29

• Device Scan Process – An Overview ............................................................................29• Configuring Device Type for Startup Device Scan .......................................................30• Disabling Startup Device Scan ......................................................................................30• Configuring Device Type for Post-Startup Device Scan ..............................................30• Disabling Post-Startup Device Scan .............................................................................31

Chapter 6: Customizing the Job Manager Process 33

• Job Manager – An Overview ..........................................................................................33• Configuring Keep-Alive Rate for Job Manager .............................................................33

Chapter 7: Customizing the Log Daemon 35

• Log Daemon – An Overview ...........................................................................................35• Configuring Disk Space Alert Thresholds ....................................................................36• Creating a User-Defined Schedule for Disk Space Checks .........................................37• Disabling Disk Space Checks ........................................................................................38• Creating a User-Defined Policy for Deleting System Logs .........................................38• Creating a User-Defined Schedule for Purging System Logs .....................................40• Disabling Automatic Purging of System Logs .............................................................40• Optimizing the Log Daemon ...........................................................................................40

Chapter 8: Customizing the Media Manager Process 43

• Media Manager – An Overview .......................................................................................43• Configuring Retention Period for Imported Backups ..................................................44

Quest NetVault BackupConfiguration Guide

5

• Using Barcodes as Default Media Labels ..................................................................... 45• Setting Priority Levels for Continuation Media Requests .......................................... 45• Setting Priority Levels for Media Labeling and Blanking Requests .......................... 46• Configuring Callback Timeouts for Bulk Media Operations ....................................... 46• Setting Interval for Media Status Updates .................................................................... 47• Disabling Reuse of Read-Only Media ........................................................................... 47• Creating a User-defined Policy for Automatic Index Compression ........................... 47• Creating a User-defined Schedule for Index Compression ........................................ 48• Disabling Automatic Index Compression ..................................................................... 48• Configuring Minimum Disk Space for Index Decompression .................................... 49• Customizing the Diagnose Media Requests Window ................................................. 50• Customizing Device Related Settings .......................................................................... 50• Enabling Timeout for Source Media Requests ............................................................ 52

Chapter 9: Customizing the Network Manager Process 53

• Network Manager – An Overview .................................................................................. 53• Configuring Timeout Settings for Remote Connections ............................................ 54• Configuring Timeout for Inactive Connections ........................................................... 54• Configuring Keep-Alive Rate for Network Manager .................................................... 55• Configuring Availability Broadcast Interval ................................................................. 55• Configuring Availability Check Interval ........................................................................ 55• Disabling Availability Broadcasts ................................................................................. 56• Configuring Security Broadcast Interval ...................................................................... 57• Configuring Network Interfaces for Multihomed NVBU Machines ............................. 57

- Considerations for Multihomed NVBU Machines ........................................................................... 58• Reducing Startup Delay ................................................................................................. 59• Changing the Default Port for Network Manager ......................................................... 61• Changing the Default Port for Communications Manager .......................................... 62

Chapter 10: Customizing the Schedule Manager Process 63

• Schedule Manager – An Overview ................................................................................ 63• Customizing NVBU Job Status Views ........................................................................... 64• Creating a User-Defined Policy for Retaining Job History ......................................... 65• Defining a Retention Period for Non-Recurring Job Definitions ................................ 65• Configuring Maximum Simultaneous Jobs .................................................................. 66• Including Report Jobs in the Job Views ....................................................................... 66

Table of Contents6

• Including Restore and Report Jobs in Policy Views ....................................................66• Configuring Job Priority .................................................................................................67

Chapter 11: Configuring Shared Memory Settings 69

• Process Manager – An Overview ...................................................................................69• Tuning Shared Memory Allocation ................................................................................69

Chapter 12: Configuring NVBU for Firewalls 71

• Firewall Settings – An Overview ....................................................................................71- Firewall Considerations .................................................................................................................. 72

• Configuring Firewall Settings on NVBU Machines ......................................................73• Defining Filtering Rules on the Firewall ........................................................................74

Chapter 13: Configuring Plug-in Options 75

• Configuring Disk Devices Plug-in ..................................................................................75- Configuring Disk Space Margins for VTLs ..................................................................................... 75- Disabling Disk Space Checks for VTLs ......................................................................................... 76- Creating VTLs with Entry/Exit Ports ............................................................................................... 76

• Configuring Verify Plug-in ..............................................................................................77- Performing Backup Verification Locally for All Clients ................................................................... 77- Configuring a Default Client for Backup Verification ...................................................................... 77- Defining Clients Which Run Verification Job Locally .................................................................... 78

• Other Sub-Tabs on the Plugin Options Tab ..................................................................78• Configuring Quest NetVault Backup Plug-in for Encryption .......................................79

Chapter 14: Configuring NVBU Notification Settings 81

• Events and Notification Methods – An Overview .........................................................81• Configuring Mail Server for Event Notifications ..........................................................82• Configuring Recipients for Email Notifications ...........................................................83• Configuring a Default Printer on Windows ...................................................................83

Chapter 15: Customizing the NVBU Console 85

• Configuring Refresh Rates .............................................................................................85• Configuring Custom Color Codes for Job Status ........................................................86


7

• Customizing NVBU Logs Window ................................................................................. 88• Disabling NVBU Logs Window ...................................................................................... 88• Customizing Device Log Views ..................................................................................... 89• Hiding Device Logs ........................................................................................................ 89• Configuring View-Levels for Mac OS X ....................................................................... 90

Chapter 16: Configuring General Settings for NVBU 91

• Relocating Logs and NVDB Directories ....................................................................... 91• Tuning TCP/IP Buffer Sizes ............................................................................................ 93• Disabling Pre-installation Compatibility Checks for Packages .................................. 94• Removing Target Set Checks for Duplication Jobs .................................................... 94

Chapter 17: Configuring the Reporting System 97

• NVBU Reporting System – An Overview ...................................................................... 98• Statistics Manager and Reports Database Manager – An Overview .......................... 98• Customizing the Output Format .................................................................................... 99

- Customizing the HTML Output Format .......................................................................................... 99- Customizing the Plain Text Output Format .................................................................................. 101- Customizing the CSV Output Format ........................................................................................... 102

• Configuring the Default Output Format for User-defined Components 104

• Configuring the Filter View .......................................................................................... 104• Configuring the Retention Period for Historic Reports ............................................ 105• Enabling “Keep Filtered Out Records” for All Reports ............................................. 105• Customizing Statistics Manager ................................................................................ 106• Configuring Statistics Collection and Transmission Parameters ............................ 107• Disabling Statistics Collection on an NVBU Client .................................................... 108• Creating User-defined Purge Policies ........................................................................ 108

- Creating a Global Policy for Purging the Reports Database ........................................................ 108- Creating a User-defined Schedule for Purging Report Tables ..................................................... 109- Disabling Global Purge Policy for Reports Database .................................................................. 110- Creating a Table-Specific Purge Policy for “Default” Table ......................................................... 110- Creating a Table-Specific Purge Policy for Report Tables ........................................................... 111- Applying Global Purge Policy to Individual Report Tables ........................................................... 113

• Configuring a Default Browser on Linux/UNIX .......................................................... 114

Table of Contents8

Chapter 18: Configuring Language Settings for NVBU 115

• Changing Locale Setting ..............................................................................................115• Correcting Locale Changes ..........................................................................................116• Disabling Post-Installation Locale Changes ...............................................................117• Configuring Display Properties for Localized Versions ............................................117

- Changing the Font Size for NVBU Console ................................................................................. 117- Changing the Date Format ........................................................................................................... 118

Chapter 19: Setting Up a BakBone Time Server 119

• BakBone Time – An Overview ......................................................................................119• Configuring an Alternate BakBone Time Server ........................................................119

Chapter 20: Using the Trace Tool 121

• Trace Logs – An Overview ............................................................................................121- Trace Levels ................................................................................................................................ 121- Date and Time in Trace Files ....................................................................................................... 122

• Setting Trace Levels ......................................................................................................122• Enabling Tracing ...........................................................................................................124• Disabling Tracing ..........................................................................................................125• Enabling Circular Logging of Trace Messages ..........................................................125

Chapter 21: Using the Txtconfig Tool 127

• Txtconfig – An Overview ..............................................................................................127• Starting Txtconfig ..........................................................................................................127• Customizing the Default Settings Using Txtconfig ....................................................128• Examples ........................................................................................................................129

- Customizing the Auditor Daemon to Log Failed User Requests .................................................. 129- Creating a Size-based Purge Policy for Audit Logs ..................................................................... 129- Customizing the Purge Schedule for Audit Logs ......................................................................... 130


9

Chapter 1:

INTRODUCING QUESTNETVAULT BACKUP

Quest NetVault Backup – At a GlanceKey BenefitsFeature SummaryAbout this DocumentTarget AudienceRecommended Additional ReadingAbout Quest Software

Contacting Quest SoftwareQuest Support

1.1.0 Quest NetVault Backup – At a GlanceQuest NetVault Backup (NetVault Backup or NVBU) offers the most advanced, cross-platform data protection capabilities along with 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 from one intuitive console. With NetVault Backup Plug-ins, you are not required to understand storage, database or email internals. You select the backup strategy that best fits your database or email environment, and then just point and click. This enterprise-level software does not require you to be an expert, but has the flexibility to tune it as you want.

NVBU is engineered to keep up with the organizational changes and let you make choices that are best for your company. For example, if an organizational merger takes place or a key department acquires a major application that requires a different platform, that is no problem with NVBU’s heterogeneous server and extensive application support. The freedom of choice continues with the powerful disk-based data protection product, Quest NetVault SmartDisk (NetVault SmartDisk or NVSD), and its deduplication option which provides seamless integration with NVBU to allow you to be in control of which data should be deduplicated and which should not without restricting you to specific types of storage drives and appliances. Additionally, administrators have increased choice including the ability to copy or move data between NVSD Instances, to Virtual Tape Library (VTL) or tape-based devices in order to place redundant backups at offsite locations for failover and disaster recovery purposes. You can select your

Chapter 1Introducing Quest NetVault Backup

10

backup device of choice from a very large list of supported Network Attached Storage (NAS), VTL and tape systems. You decide when and where to encrypt to reduce backup windows while still meeting regulatory requirements. You can deploy and protect physical or virtual machines. With the NVBU Plug-ins, you easily select the best backup method to protect all the popular operating systems, messaging and database applications. NVBU SmartClient gives you the freedom to attach virtual and physical tape devices where you want to.

NVBU is architected to protect and leverage existing investments in data protection while making necessary changes and upgrades to support the growth and health of your organization. NVBU’s ability to efficiently scale from small installations to very large global companies means you would not be penalized by being forced to rip and replace your data protection infrastructure just because your organization is successful and growing. The NVSD product integrates with NVBU to shrink backup windows and reduce storage costs with its post-process deduplication option which can be scheduled outside the backup window. Your investment in storage systems is protected through automated access to hundreds of different storage devices. You avoid vendor lock-in by taking advantage of NVBU’s heterogeneous server support as well as powerful messaging, database and virtualization protection options. With NVBU, you protect your vital IT assets because you can still recover your data even in a worst case scenario in which you only have your backup media, but no NVBU database. Plus, you can redeploy into a different operating system for an emergency recovery.

1.2.0 Key BenefitsIntuitive interface requiring only minimal experience to operateSimple, out-of-the-box deployment for fast time to valueProtection for both physical and virtual environments for cost savingsHeterogeneous server support for flexibility to adjust to changing conditions or emergenciesPlug-in options to tailor NetVault Backup to your environmentDisk-based backup and de-duplication to significantly improve storage efficiencyComprehensive Network Attached Storage (NAS) protection to safeguard critical dataPowerful, flexible encryption when and where you need itBare metal recovery to drastically reduce the time it takes to recover a failed disk driveExtensive storage attachment options allow for distributed backup targets and workload


11

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

1.3.0 Feature SummaryDisk-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 NetVault SmartDisk 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 policy-based 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 CAST-128, AES-256 or CAST-256 algorithm support. Flexible job-level encryption lets you easily select which data to encrypt.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.


12

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.

1.4.0 About this DocumentThe 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.

1.5.0 Target AudienceThis 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.

1.6.0 Recommended Additional ReadingQuest 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 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


13

1.7.0 About Quest SoftwareQuest Software simplifies and reduces the cost of managing IT for more than 100,000 customers worldwide. Quest’s innovative solutions make solving the toughest IT management problems easier, enabling customers to save time and money across physical, virtual, and cloud environments. For more information about Quest, go to www.quest.com.

1.7.1 Contacting Quest Software

For regional and international office information, refer to the web site.

1.7.2 Quest SupportQuest 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 SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

Retrieve thousands of solutions from our online KnowledgebaseDownload the latest releases and service packsCreate, 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 http://support.quest.com.

This guide is available in English only.

Email: [email protected]

Mail: Quest Software, Inc.World Headquarters5 Polaris WayAliso Viejo, CA 92656USA

Web site: www.quest.com


14


15

Chapter 2:

GETTING STARTED

NVBU Configurator – An OverviewStarting NVBU Configurator

Starting NVBU Configurator on Linux/UNIXStarting NVBU Configurator on Mac OS XStarting NVBU Configurator on Windows

Remote ConfiguratorStarting Remote Configurator

Txtconfig

2.1.0 NVBU Configurator – An OverviewNVBU Configurator (Configurator) is a built-in configuration utility available with both the NVBU Server and Client installations. It provides an easy-to-use graphical user interface to change the preferences and default settings, and 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 Starting NVBU Configurator

2.2.1 Starting NVBU Configurator on Linux/UNIXTo 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

Alternatively, add ampersand (&) for an open prompt:nvconfigurator &

You can issue this command from any directory.

Chapter 2Getting Started

16

2.2.2 Starting NVBU Configurator on Mac OS XOn 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 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 full functionality. To access the X11 version of NVBU Configurator on Mac OS Xa. From the Finder, access Applications.b. Locate NVConfigurator, and double-click it.

2.2.3 Starting NVBU Configurator on WindowsTo 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:

Home Screenfor

Configurator


17

2.3.0 Remote ConfiguratorThe Configurator can be accessed from another NVBU machine to remotely configure the preferences and default settings for NVBU. This feature is called the Remote Configurator. 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, and is available on both the NVBU Server and Client. However, it offers limited functionality, and does not allow you to configure all NVBU settings.

2.3.1 Starting Remote ConfiguratorTo start the Remote Configurator

1. Start the NVBU Console on the local machine, and open the NVBU Client Management window. To open this window:

Click Client Management on the toolbar or Large Buttons panel– or –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 TxtconfigNVBU also provides a text version of the Configurator, called Txtconfig. Txtconfig can be used to customize NVBU on machines that do not support a GUI. For details on Txtconfig, refer to Using the Txtconfig Tool on page 127.

Chapter 2Getting Started

18


19

Chapter 3:

PERFORMING COMMONADMINISTRATIVE TASKS

Viewing NVBU Service StatusStarting and Stopping NVBU ServiceViewing NVBU Machine DetailsInstalling Optional Plug-insRemoving Plug-insLicensing SoftwareViewing License DetailsChanging NVBU PasswordDisabling Password-Protection for NVBU ClientsAllowing NVBU Server to Function as Client

3.1.0 Viewing NVBU Service StatusTo view the current status of the NVBU Service

1. Click the Service tab on the Configurator. The Current Status is displayed at the top as a read-only string.

2. Click another tab or exit Configurator, as required.

3.2.0 Starting and Stopping NVBU ServiceThe NVBU Service is configured to start automatically when the software installation completes on the NVBU Server and Client machines. In case you want to manually stop or start the NVBU Server, use the following steps:

1. Click the Service tab on the Configurator.2. Choose the applicable action:

To stop the NVBU Service, click Stop Service.To start the NVBU Service, click Start Service.

Chapter 3Performing Common Administrative Tasks

20
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 DetailsTo view the NVBU machine details

1. Click the Machine tab on the NVBU Configurator. Note that this tab is selected by default when you start the NVBU Configurator.

2. This tab displays the following details: Figure 3-2:

Machine tab

Machine Name – The NVBU name of the machine.Machine ID – The Machine ID which is used for licensing NVBU.Network Name(s) – The Network name of the machine.


21

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-insNVBU provides various optional plug-ins which must be procured and installed separately. You can use either the NVBU Console or the Configurator to install these plug-ins.

To install an optional plug-in module using the Configurator

1. Click the Packages tab on the Configurator.Figure 3-3:

Packages tab

2. Click Install Software to starts 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 absolute file path for the

binary on the installation CD or the directory to which the file was downloaded from Quest Software's web site. Alternatively, click Browse, and navigate to the location of the installation file for the plug-in to be installed.


22

5. Click Next.6. The Details window displays the package details. Click Next to start the

installation process. A message is displayed when the process completes.

3.5.0 Removing Plug-insTo remove a plug-in using the Configurator

1. Click the Packages tab on the Configurator.2. In the Installed Packages list, select the plug-in to be removed.3. Click Remove Software.4. In the confirmation dialog, click OK to proceed. A message is displayed when

the process completes.

3.6.0 Licensing SoftwareNVBU products include a built-in evaluation license key, which is valid for 45 days. You must install the permanent license keys before the 45-day evaluation period expires otherwise the products will cease to function. The permanent license keys can be requested at https://support.quest.com/LicenseKey.aspx. You can either use the NVBU Console or the Configurator to install these license keys.

To install the permanent license keys using 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.3. Click OK to apply the changes and exit Configurator. Alternatively, click

Apply to commit the new settings and remain in Configurator.


23

3.7.0 Viewing License DetailsTo view the license details for NVBU

1. Click the License tab on the Configurator. 2. This tab includes the following sections:

Server Capabilities – Under Server Capabilities, you can view 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, you can view the details of applied license keys. Note the following:

The plug-in licences only appear on the NVBU Client on which it is installed. It does not appear on the NVBU Server.


3.8.0 Changing NVBU PasswordTo 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 in the New Password box. Your password cannot contain <, >, &, # or | characters.Confirm Password – Re-enter the password in the Confirm Password box.



24

3.9.0 Disabling Password-Protection for NVBU ClientsThe password-protection for an NVBU Client can be disabled temporarily so that a Heterogeneous or Workstation Client can be added or accessed without its password.

To disable password-protection for an NVBU Client

1. Click the Security tab on the Configurator.2. Configure the following parameter:

Disable Security – Select this check box.3. Click OK to apply the changes and exit Configurator. Alternatively, click


3.10.0 Allowing NVBU Server to Function as ClientBy 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, complete the following steps:

1. Click the Security tab on the Configurator.2. Configure the following parameter:

This Machine May be Added as a Client to a Server – Select this check box on the NVBU Server.



25

Chapter 4:

CUSTOMIZING THE AUDITORDAEMON

Auditor Daemon – An OverviewGenerating Audit Logs for Failed User RequestsCreating a User-Defined Policy for Deleting Audit LogsCreating a User-Defined Schedule for Purging Audit LogsDisabling Automatic Purging of Audit LogsConfiguring Concurrent Sysop Operator Messages

4.1.0 Auditor Daemon – An OverviewThe Auditor Daemon (nvavp) runs on the NVBU Server. This process tracks and controls user activities. It validates each user request, and depending on the user privileges, grants or denies the request. The Auditor 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 via NVBU Audit Trail report. For details on the Audit Trail report, refer to the Quest NetVault Backup Administrator’s Guide.

By default, the Auditor 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 to log only failed user requests, or create a user-defined policy for deleting audit logs. The default behavior and properties of the Auditor can be changed from the Auditing tab on the Configurator.

4.2.0 Generating Audit Logs for Failed User RequestsBy default, the Auditor 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.2. Configure the following parameter:

Chapter 4Customizing the Auditor Daemon

26
Figure 4-1:Auditing tab
Only Record Failed Requests in the Audit Trail – Select this check box.

Note: The NVBU Service must be restarted to apply any changes to this setting.


4.3.0 Creating a User-Defined Policy for Deleting Audit LogsThe Auditor uses a default policy to delete obsolete logs, and accordingly 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 – Select this policy type to delete logs that older than a certain number of days.Size-based Purge Policy – Select this policy type to delete logs when the file exceeds a certain size.

To create a user-defined policy for automatically deleting audit logs

1. Click the Auditing tab on the Configurator.2. Select one of the following methods:

a. Age-based Purge Policy – For a purge policy based on the log age, configure the following parameters:1. In the Purge Type list, select By Age.2. In the Purge Entries That are Older Than box, 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 – For a purge policy based on the log file size, configure the following parameters:1. In the Purge Type list, select By Size.2. In the Purge When Trail Exceeds box, 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.


27

3. By default, automatic purging occurs very 24 hours. To change this schedule, refer to Creating a User-Defined Schedule for Purging Audit Logs on page 27.


4.4.0 Creating a User-Defined Schedule for Purging Audit LogsBy default, automatic purging occurs every 24 hours. To create a user-defined schedule for purging audit logs, 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 LogsTo disable automatic purging of audit logs


Purge Type – In the Purge Type list, select None3. Click OK to apply the changes and exit Configurator. Alternatively, click


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.

Chapter 4Customizing the Auditor Daemon

28

4.6.0 Configuring Concurrent Sysop Operator MessagesIf 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, it is discarded and the following Operator Message appears in the NVBU Status window:

Too many simultaneous notifications. Refusing further notificationsThe Auditor Daemon does 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.



29

Chapter 5:

CUSTOMIZING THE DEVICESCAN PROCESS

Device Scan Process – An OverviewConfiguring Device Type for Startup Device ScanDisabling Startup Device ScanConfiguring Device Type for Post-Startup Device ScanDisabling Post-Startup Device Scan

5.1.0 Device Scan Process – An OverviewThe 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 machine. It can recognize devices manufactured by several vendors, although not all. The devices found can be added using the Automatic Device Configuration wizard. The Device Scan process is initiated during the following events:

NVBU Startup – Device Scan 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 NDMP Filers. Since scanning for new physical devices can take a while to complete, you can disable device scan during NVBU startup or restrict the type of device it scans for.Post-Startup – Device Scan 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.

Chapter 5Customizing the Device Scan Process

30

5.2.0 Configuring Device Type for Startup Device ScanBy 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.2. Configure the following parameter:

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 ScanTo disable device scan during NVBU startup

1. Click the Device Scan tab on the Configurator.2. Configure the following parameter:

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 ScanBy 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 sub-tab.


31

3. Configure the following parameter:Figure 5-2:

Devices sub-tab 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 ScanTo disable device scan when you open the NVBU Device Management window

1. Click the GUI tab on the Configurator.2. Click the Devices sub-tab.3. Configure the following parameter:

Figure 5-3:Devices sub-

tab on GUI tab

Enable Automatic Device Scanning – Select Neither in the Enable Automatic Device Scanning list.


Chapter 5Customizing the Device Scan Process

32


33

Chapter 6:

CUSTOMIZING THE JOBMANAGER PROCESS

Job Manager – An OverviewConfiguring Keep-Alive Rate for Job Manager

6.1.0 Job Manager – An OverviewThe Job Manager process (nvjobmgr) runs on the NVBU Server and manages the execution of a 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 ManagerKeep-alive messages are used to verify that a connection between two NVBU machines is still 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 keep-alive rate setting

1. Click the Job Manager tab on the Configurator.2. On the Timeouts tab, configure the following parameter:

Figure 6-1:Timeouts sub-

tab on JobManager tab

Keep Alive Rate – Enter or select an interval for keep-alive messages. The keep-alive rate is set in number of minutes. The default value for this parameter is 5 minutes.


Chapter 6Customizing the Job Manager Process

34


35

Chapter 7:

CUSTOMIZING THE LOGDAEMON

Log Daemon – An OverviewConfiguring Disk Space Alert ThresholdsCreating a User-Defined Schedule for Disk Space ChecksDisabling Disk Space ChecksCreating a User-Defined Policy for Deleting System LogsCreating a User-Defined Schedule for Purging System LogsDisabling Automatic Purging of System LogsOptimizing the Log Daemon

7.1.0 Log Daemon – An OverviewThe Log Daemon (nvlogdaemon) runs on the NVBU Server and performs the following functions:

Records System Logs – The Log Daemon manages the system logs generated by various NVBU processes and writes them to log files. System logs are useful in tracking activities and troubleshooting problems. The system 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 91. The log files are stored in binary format and named log-0, log-1, log-2, etc. 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 system logs do not continue to accumulate and consume disk space, the Log Daemon automatically deletes them after 30 days. You can change this behavior with a user-defined policy, or delete the system logs manually.

Chapter 7Customizing the Log Daemon

36

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

HomeDatabaseLogsReports

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 ThresholdsNVBU defines two alert thresholds for disk space usage levels – Warning and Critical. These thresholds are defined as <x> Percent Full of Total Disk Space, and set at 85 and 95 percent, respectively.

To change the warning or critical disk space threshold values

1. Click the Logging Daemon tab on the Configurator.2. Configure the following parameters:

Figure 7-1:Logging

Daemon tab

Note: The NVBU Service must be restarted to apply any changes to the Warning and Critical threshold values.


37

a. Disk Space Warning Threshold – Enter or select the disk usage level for warning threshold. It is set at 85 percent full of total space by default. When space usage reaches the warning threshold, the following events occur:

The logging daemon logs an error.The Auditor logs a sysop operator message which is displayed under Operator Messages on the NVBU Status window.NVBU raises the Home Drive Becoming Full event under the Logging Daemon event class. 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. It is set at 95 percent full of total space by default. When space usage reaches the critical threshold, the following events occur:

NVBU sends an error message to Event Viewer on Windows and syslog utility on Linux/UNIX. The Logging Daemon logs an error.NVBU shuts down automatically and sets the status on the Configurator Service tab to Stopped Disk Full.

Warning: If disk space is critically low at the startup of NVBU Service, the errors will only be logged via Event Viewer or syslog. You must 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 ChecksBy default, the disk space checks are scheduled to run every hour. You can override this behavior with a user-defined schedule.

To create a user-defined schedule for disk space checks

1. Click the Logging Daemon tab on the Configurator.2. Configure the following parameter:

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.



38

7.4.0 Disabling Disk Space ChecksTo disable automatic disk space checks by the log daemon


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 System LogsThe Log Daemon uses a default policy to delete obsolete logs, and accordingly deletes all system 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 – Select this policy type to delete logs that older than a certain number of days.Page-based Purge Policy – Select this policy type to delete log pages when the total pages exceeds a certain number.

Note: For details on deleting the system logs manually, refer to the Quest NetVault Backup Administrator’s Guide.

To create a user-defined policy for deleting system logs

1. Click the Logging Daemon tab on the Configurator.2. Select one of the following methods to create a user-defined purge policy for

system logs:


39

Figure 7-2: Auto purgemethods for

audit logs onLogging

Daemon tab

a. Age-based Purge Policy – For a purge policy based on the log age, configure the following parameters:1. In the Auto-Purge Method list, select Exceeds Log Age.2. In the Auto-Purge Entries That are Older Than box, 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 the page size, configure the following parameters:1. In the Auto-Purge Method list, select Exceeds Number of Pages.2. In the Auto-Purge When the Number of Log Pages Exceeds box,

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 System Logs on page 40.



40

7.6.0 Creating a User-Defined Schedule for Purging System LogsBy default, automatic purging occurs every 3 hours. To create a user-defined schedule for purging system logs, use the following steps:


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 System LogsTo disable automatic purging of system logs


Auto-Purge Method – In the Auto-Purge Method list, select None.3. Click OK to apply the changes and exit Configurator. Alternatively, click


Important: The system logs can consume a considerable amount for disk space. Therefore, periodic purging of the logs is necessary. If you disable automatic purging, you must 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 DaemonTo change the properties of the log daemon

1. Click the Logging Daemon tab on the Configurator.2. Configure the following parameters, as required:

a. Log File Size – Enter or select the maximum 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.


41

b. 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 the Message Response Interval box. 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 the Minimum Time between Progress Updates box.

c. Log 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 bundle, enter or select the bundle size in the Outgoing Message Bundle Size box.

d. Messages Sent 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 via 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 the Minimum Warning Level to Send to System Log box. The warning codes and the corresponding severity level of the messages are listed in the table below:

Code Severity Level112 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


42


43

Chapter 8:

CUSTOMIZING THE MEDIAMANAGER PROCESS

Media Manager – An OverviewConfiguring Retention Period for Imported BackupsUsing Barcodes as Default Media LabelsSetting Priority Levels for Continuation Media RequestsSetting Priority Levels for Media Labeling and Blanking RequestsConfiguring Callback Timeouts for Bulk Media OperationsSetting Interval for Media Status UpdatesDisabling Reuse of Read-Only MediaCreating a User-defined Policy for Automatic Index CompressionCreating a User-defined Schedule for Index CompressionDisabling Automatic Index CompressionConfiguring Minimum Disk Space for Index DecompressionCustomizing the Diagnose Media Requests WindowEnabling Timeout for Source Media Requests

8.1.0 Media Manager – An OverviewThe Media Manager (nvmedmgr) runs on the NVBU Server and performs the following functions:

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.It controls the selection of device and media for a job based on the media requests submitted by the Job Manager process.

You can change the default settings for the Media Manager from the Media Manager tab on the Configurator.

Chapter 8Customizing the Media Manager Process

44

Note: The NVBU Service must be restarted to apply any changes to the Media Manager Settings.

8.2.0 Configuring Retention Period for Imported BackupsNVBU cannot process data on media for which no information is available in the Media database. Such media are categorized as foreign media. 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 foreign media, you must scan the media, the backups and the on-tape indexes to import the required data from the media to 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. Configure the following parameter:

Figure 8-1:Media

Manager tab

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.



45

8.3.0 Using Barcodes as Default Media LabelsDuring backups you can automatically label blank media using the Automatically Label Blank Media option present on the Target tab of the NVBU Backup window. NVBU concatenates the NVBU Server name, system name and a seed number to generate a unique label for each media. Instead of assigning a system-generated string, you can configure NVBU to use the media barcodes as 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 RequestsA 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

1. Click the Media Manager tab on the Configurator.2. 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 that 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



46

8.5.0 Setting Priority Levels for Media Labeling and Blanking RequestsNVBU 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 that 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 OperationsThe 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 seconds. The default value for this parameter is 120 seconds.



47

8.7.0 Setting Interval for Media Status UpdatesThe 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 frequency of status updates for online media. The update interval is specified in minutes. The default interval is 10 minutes.


8.8.0 Disabling Reuse of Read-Only MediaNVBU automatically removes the read-only tag for a media when the last saveset stored on it retires, allowing you to reuse the media for newer backups. To disable this feature, perform the following steps:


Mark Expired Read Only Media as Writable – Click to clear the Mark Expired Read Only Media as Writable check box to prevent reuse of a retired read-only media. This parameter is selected by default.


8.9.0 Creating a User-defined Policy for Automatic Index CompressionOnline indexes are the backup indexes stored in the NVDB. You can compress these indexes to reduce space usage. The backup indexes can be compressed manually from the NVBU Restore window, or automatically using an index compression policy. NVBU uses a default compression policy to automatically compress online indexes after 30 days of inactivity. To replace the default policy with a user-defined automatic index compression policy, perform the following steps:



48
Figure 8-2:
Indexcompression

parameters onMedia

Manager tab

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.


8.10.0 Creating a User-defined Schedule for Index CompressionThe Media Manager scans the NVDB at periodic intervals to find backup indexes which can be compressed. The scanning occurs every 12 hours. To change this schedule, perform the following steps:


Hours between Scans for Indexes to be Compressed – Enter or select the frequency of scans for index compression. The default interval between two scans is 12 hours.


8.11.0 Disabling Automatic Index CompressionTo disable automatic compression of online indexes, perform the following steps:


Days of Inactivity before an Index is Compressed – Enter or select 0 (zero).



49

8.12.0 Configuring Minimum Disk Space for Index DecompressionNVBU automatically decompresses 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 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, perform the following steps:


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 fails 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 exist on the NVDB drive or partition after a decompression. When a decompression request is received, NVBU reads the index header to determine its decompressed file size. The request fails if the available space on the NVDB drive or partition will go below the minimum required space after decompression.

The error message is displayed on the NVBU Restore window or the NVBU Logs window depending on whether the decompression request was raised automatically or manually.

The message is displayed on the NVBU Restore window when you issue the decompress command manually from this window.It is displayed the NVBU Logs window when NVBU performs an automatic decompression for a restore or an incremental backup.



50

8.13.0 Customizing the Diagnose Media Requests WindowNVBU supports a maximum of 64,000 characters on 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 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 SettingsTo customize the device related settings controlled by the Media Manager, perform the following steps:


Figure 8-3:Device relatedparameters on

MediaManager tab

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.


51

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



52

8.15.0 Enabling Timeout for Source Media RequestsFor 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

enablingtimeout for

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



53

Chapter 9:

CUSTOMIZING THE NETWORKMANAGER PROCESS

Network Manager – An OverviewConfiguring Timeout Settings for Remote ConnectionsConfiguring Timeout for Inactive ConnectionsConfiguring Keep-Alive Rate for Network ManagerConfiguring Availability Broadcast IntervalConfiguring Availability Check IntervalDisabling Availability BroadcastsConfiguring Security Broadcast IntervalConfiguring Network Interfaces for Multihomed NVBU Machines

Considerations for Multihomed NVBU MachinesReducing Startup DelayChanging the Default Port for Network ManagerChanging the Default Port for Communications Manager

9.1.0 Network Manager – An OverviewNetwork 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 process 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 must be restarted to apply any changes to the Network Manager settings.

Chapter 9Customizing the Network Manager Process

54

9.2.0 Configuring Timeout Settings for Remote ConnectionsThe 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

sub-tab onNetwork

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 ConnectionsThe 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 seconds. The default value for this parameter is 300 seconds.



55

9.4.0 Configuring Keep-Alive Rate for Network ManagerKeep-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 IntervalNVBU 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 IntervalNVBU 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:


56


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 BroadcastsAvailability broadcasts are used to update the client list and the client status on the NVBU Client Management window. Although this option can be disabled, Quest does not recommend it. Without availability broadcasts, the 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:

1. Click the Network Manager tab on the Configurator.2. Click the Connections sub-tab.3. Configure the following parameter:

Figure 9-2: Connections

sub-tab onNetwork

Manager tab

Broadcast Details to Machines on Local Networks – Click to clear this check box.



57

9.8.0 Configuring Security Broadcast IntervalSecurity broadcasts provide the password-protection status of the NVBU Clients, and notify whether the 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 MachinesFor multihomed NVBU machines, you can 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 preferred, fallback and barred network interfaces for multihomed NVBU machines, perform the following steps:

Important: This procedure should only be used when the local machine is connected to multiple networks, either via multiple Network Interface Cards or through virtual IP addressing.

1. Click the Network Manager tab on the Configurator.2. Click the Connections tab.3. Configure the following parameters:


58
Figure 9-3:
Connectionssub-tab on

NetworkManager tab

Preferred Network Address – Enter the preferred IP address for NVBU connections in the Preferred Network Address box. Only a single IP address can be specified in this box.Comma Separated List of Barred Address(es) – Enter barred or blocked addresses in the Comma Separated List of Barred Address(es). For multiple addresses, use comma as a delimiter.Comma Separated List of Fallback Address(es) – Enter the fallback address(es) 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 MachinesRefer to the following notes when configuring preferred, fallback and barred IP addresses for multihomed NVBU machines:

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

Preferred network addressFallback addressesAny 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:


59

a. Remove the Client and add it again as described below:1. On the NVBU Console, open the NVBU Client Management window. 2. Under Clients, right-click the NVBU Client and select Remove or

Force Remove.3. Under Available NVBU Machines, right-click the NVBU Client and

select Remove. A Background Message “Machine <NVBU Machine Name> Has Gone Down” is written to the NVBU Logs when the Client is removed.

4. Wait until the timeout for remote connection expires as determined by the value set for the Time to Complete Remote Connection parameter. This parameter is set to 5 minutes by default. A Background Message “Machine <NVBU Machine Name> Has Come Up” is written to the NVBU Logs when the Client is detected on the network.

5. Enter the NVBU Client's preferred address in the Machine Name or IP Address box 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 must 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.NVBU Service must be restarted after making any changes to the Barred Addresses parameter.

9.10.0 Reducing Startup DelayWhen 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:

1. Click the Network Manager tab on the Configurator.2. Click the Connections tab.


60

3. Configure the following parameters: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:

Based on this output, you can configure the following values in the Comma Separated List of Networks and Addresses Not to Resolve box – 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.

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

…


61

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 ManagerThe Network Manager process 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 71.

3. Restart the NVBU Service to apply the new settings.4. Repeat steps 1–3 on the NVBU Server and all NVBU Clients.


62

9.12.0 Changing the Default Port for Communications ManagerThe Communications Manager process 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 71.

3. Restart the NVBU Service to apply the new settings.4. Repeat steps 1–3 on the NVBU Server and all NVBU Clients.


63

Chapter 10:

CUSTOMIZING THE SCHEDULEMANAGER PROCESS

Schedule Manager – An OverviewCustomizing NVBU Job Status ViewsCreating a User-Defined Policy for Retaining Job HistoryDefining a Retention Period for Non-Recurring Job DefinitionsConfiguring Maximum Simultaneous JobsIncluding Report Jobs in the Job ViewsIncluding Restore and Report Jobs in Policy ViewsConfiguring Job Priority

10.1.0 Schedule Manager – An OverviewThe Schedule Manager (nvsched) runs on the NVBU Server and performs the following functions:

The Schedule Manager manages the job schedules and queues. The Schedule Manager initiates the Job Manager process 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.

Chapter 10Customizing the Schedule Manager Process

64

10.2.0 Customizing NVBU Job Status ViewsThe job status records can be viewed from the following interfaces:

The Status tab of the NVBU Jobs windowUnder 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.2. Configure the following parameter:

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



65

10.3.0 Creating a User-Defined Policy for Retaining Job HistoryThe 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:

1. Click the Schedule Manager tab on the Configurator.2. Configure the following parameters:

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.


10.4.0 Defining a Retention Period for Non-Recurring Job DefinitionsNVBU 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 in this box. 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 non-recurring jobs are retained indefinitely.



66

10.5.0 Configuring Maximum Simultaneous JobsBy default, NVBU supports a maximum of 50 simultaneous jobs. It includes backup, restore and report jobs. To change the number of simultaneous jobs, perform the following steps:


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 ViewsBy 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 – Click to clear this check box.


10.7.0 Including Restore and Report Jobs in Policy ViewsBy 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 – Click to clear the check box to view report jobs on the NVBU Policy Management window.Exclude Restore Jobs From Policy Management Views – Clear this check box to view restore jobs on the NVBU Policy Management window.


67


10.8.0 Configuring Job PriorityThe 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:

You can globally change the priority level settings for all backup, restore or report jobs, or override these settings for an individual job. The global changes are performed using the Schedule Manager tab on 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.

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 jobs. The default value for this parameter is 20.Default Report Job Priority – Enter or select the priority level for report jobs. The default value for this parameter is 50.


Job Type Priority LevelRestore 20

Backup 30

Report 50


68


69

Chapter 11:

CONFIGURING SHAREDMEMORY SETTINGS

Process Manager – An OverviewTuning Shared Memory Allocation

11.1.0 Process Manager – An OverviewThe Process Manager (nvpmgr) runs on all NVBU machines. This process 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 must be restarted to apply any changes to the Process Manager settings.

11.2.0 Tuning Shared Memory AllocationTo 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.

Chapter 11Configuring Shared Memory Settings

70

To increase the shared memory for the Process Table, enter or select the new value in the Shared Memory Used for Process Table box. 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 must 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 the Shared Memory Allocated to the Trace Buffer of Each Process box. 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 the Shared Memory Allocated to a Progress Buffer box. 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 the Number of Progress Buffers Available to Plugins box.



71

Chapter 12:

CONFIGURING NVBU FORFIREWALLS

Firewall Settings – An OverviewFirewall Considerations

Configuring Firewall Settings on NVBU MachinesDefining Filtering Rules on the Firewall

12.1.0 Firewall Settings – An OverviewFirewall 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 ChannelListen Ports for Devices – Ports to listen on for device requests. It must be configured on NVBU machines which have a locally-attached device, e.g, NVBU Server or a SmartClient.Ports Required – 2 ports per driveConnect Ports for Devices – Ports used by NVBU Plug-ins to connect to remote physical or virtual tape devices. It must be configured on NVBU Clients which connect to remote devices. Ports Required – 2 ports per drive

Message ChannelListen Ports for Message Channels – Ports for receiving messages during data transfers. It must 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 must be configured on both the NVBU Server and the Client.

Chapter 12Configuring NVBU for Firewalls

72

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 ChannelConnect 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 ChannelConnect Ports for NDMP Control Channels – Ports for sending NDMP messages (NDMP control channels). It must 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. The default port is 10000, which can be changed.Listen Ports for NDMP Data Channels – Ports to listen on for NVBU devices operating as NDMP movers. It must 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 ConsiderationsConsider the following when configuring NVBU for firewalls:

For NVBU Clients that are outside the firewall, you must set 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 20031 for TCP and UDP messaging. Ensure 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 74.


73

12.2.0 Configuring Firewall Settings on NVBU MachinesTo facilitate communication between NVBU Server and Clients through a firewall, perform the following steps:

1. Click the Firewall tab on the Configurator.2. Configure the following parameters:

Valid Listen Port for Devices Valid Connect Port for Devices Valid Listen Port for Message ChannelsValid Connect Port for Message ChannelsValid Connect Port for NDMP Control ChannelsValid Listen Port for NetVault NDMP Data ChannelsValid Connect Ports for Inter-machine Connection Setup

For details on these parameters, refer to Firewall Settings – An Overview on page 71.

Figure 12-1:Firewall tab

The ports or port ranges can be specified as follows:A comma-separated list (e.g., 20000, 20050)A port-range separated by a dash (e.g., 20000-20100)A combination of comma-separated list and port-range (e.g., 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.

Chapter 12Configuring NVBU for Firewalls

74
Figure 12-2:
ExampleshowingTCP/IP

specificationon Firewall tab


12.3.0 Defining Filtering Rules on the FirewallRefer to the following table when setting up filtering rules on the firewall to allow NVBU traffic:

From To TCP/UDP Source Port Destination Port

Server Client TCP Valid Connect Ports for Inter-Machine Connection Setup (as specified on the NVBU Server)

20031

Client Server TCP Valid Connect Ports for Inter-Machine 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 Message Channels (as specified on the NVBU Client)

Client Server TCP Valid Listen Ports for Message Channels (as specified on the NVBU Client)

Valid Connect Ports for Message Channels (as specified on the NVBU Server)

Server Client UDP 20031 20031

Client Server UDP 20031 20031

Server Client Valid Listen ports for Devices (as specified on the NVBU Server/SmartClient)

Valid Connect Ports for Devices (as specified on the NVBU Client)

Client Server Valid Connect Ports for Devices (as specified on NVBU Client)

Valid Listen ports for Devices (as specified on NVBU Server/SmartClient)


75

Chapter 13:

CONFIGURING PLUG-INOPTIONS

Configuring Disk Devices Plug-inConfiguring Disk Space Margins for VTLsDisabling Disk Space Checks for VTLsCreating VTLs with Entry/Exit Ports

Configuring Verify Plug-inPerforming Backup Verification Locally for All ClientsConfiguring a Default Client for Backup VerificationDefining Clients Which Run Verification Job Locally

Other Sub-Tabs on the Plugin Options TabConfiguring Quest NetVault Backup Plug-in for Encryption

13.1.0 Configuring Disk Devices Plug-inThe 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.1.1 Configuring Disk Space Margins for VTLsBefore creating a VTL, NVBU performs a disk space check to make sure 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 margin considered for the following:

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.

The margin is set to 20MB by default. To change this setting, perform the following steps:

1. Click the Plugin Options tab on the Configurator.2. Click the Disk Devices Plugin sub-tab.3. Configure the following parameters:

Chapter 13Configuring Plug-in Options

76
Figure 13-1:Disk Devices
Plugin sub-tab

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.1.2 Disabling Disk Space Checks for VTLsOn 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:

1. Click the Plugin Options tab on the Configurator.2. Click the Disk Devices Plugin sub-tab.3. Configure the following parameter:

Check Available Disk Space before Creating Disk Libraries – Click to clear this check box.


13.1.3 Creating VTLs with Entry/Exit PortsTo create VTLs which have entry/exit ports, perform the following steps:

1. Click the Plugin Options tab on the Configurator.2. Click the Disk Devices Plugin sub-tab.3. Configure the following parameter:

Allow Disk Libraries to Have Entry/ Exit Ports – Select this check box.4. Click OK to apply the changes and exit Configurator. Alternatively, click



77

13.2.0 Configuring Verify Plug-inThe 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.2.1 Performing Backup Verification Locally for All ClientsNVBU 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 must be performed on the NVBU Server.

1. Click the Verify tab on the Configurator.2. Configure the following parameter:

Figure 13-2:Verify tab

Always Run Verify Locally – Select the Always Run Verify Locally check box.


13.2.2 Configuring a Default Client for Backup VerificationNVBU 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:



78

1. Click the Verify tab on the Configurator.2. Configure the following parameter:

Default Client to Run Verify – Enter the NVBU SmartClient name on which you want to run all verification jobs.


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


1. Click the Verify tab on the Configurator.2. Configure the following parameters:

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.3.0 Other Sub-Tabs on the Plugin Options TabThe remaining sub-tabs 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 ConfiguratorUsing the Configure window which can be accessed from the NVBU Backup windowUsing Remote Configurator

When you install an optional plug-in, a new sub-tab 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:

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


79

Plug-in for FileSystem – Refer to the Quest NetVault Backup for FileSystem User’s GuideOptional Plug-ins – Refer to the respective plug-in user’s guide.

Note: The Duplicate Plugin sub-tab 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.4.0 Configuring Quest NetVault Backup Plug-in for EncryptionNVBU provides an optional Plug-in for Encryption module for securing your backups and protecting them from unauthorized access. The Plug-in for Encryption must be obtained separately and installed on all NVBU machines on which you want to perform encrypted backups and restores. A key is installed on the target client, which is used to encrypt the data before it is transferred to the backup media. 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.


80


81

Chapter 14:

CONFIGURING NVBUNOTIFICATION SETTINGS

Events and Notification Methods – An OverviewConfiguring Mail Server for Event NotificationsConfiguring Recipients for Email NotificationsConfiguring a Default Printer on Windows

14.1.0 Events and Notification Methods – An OverviewAn 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 EmailsOperator MessagesPrint ReportRun a Job

For details on NVBU events and notification methods, refer to the Quest NetVault Backup Administrator’s Guide.

The Email and Print Report notification methods use some settings which are not pre-configured. Before using these notification methods, you must configure the following:

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 for a single job)

The default settings for the notification methods can be configured from the Notification tab on the Configurator.

Chapter 14Configuring NVBU Notification Settings

82

14.2.0 Configuring Mail Server for Event NotificationsTo configure a Mail Server for email notifications

1. Click the Notification tab on the Configurator.2. On the Mail Server sub-tab, configure the following parameters:

Figure 14-1:Mail-Server

sub-tab

Outgoing E-mail Server (SMTP) – Enter the machine name or IP Address for the Mail Server.Port Number – Port number 25 is configured as the default SMTP listener port. 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 “foobar” from this address for SMTP authentication.Authentication Password – Enter the password for the account which will be used for SMTP authentication.



83

14.3.0 Configuring Recipients for Email Notifications To configure the recipient email addresses for email notifications

1. Click the Notification tab on the Configurator.2. Click the Global Notification sub-tab.3. Configure the following parameters:

Figure 14-2: Global

Notificationsub-tab 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 WindowsOn a Windows NVBU Server, perform the following steps to configure a default printer for the Print Report notification method:

1. Click the Notification tab on the Configurator.2. Click the Default Printer sub-tab.3. Configure the following parameter:

Figure 14-3:Default Printer

sub-tab onNotification tab

Chapter 14Configuring NVBU Notification Settings

84

Default Printer Name – Enter the URL for the printer in the Default Printer Name box.



85

Chapter 15:

CUSTOMIZING THE NVBUCONSOLE

Configuring Refresh RatesConfiguring Custom Color Codes for Job StatusCustomizing NVBU Logs WindowDisabling NVBU Logs WindowCustomizing Device Log ViewsHiding Device LogsConfiguring View-Levels for Mac OS X

15.1.0 Configuring Refresh RatesRefresh 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 statusPoliciesDevicesJob progressOperator messages

You can change the default refresh rates from the Refresh Rates sub-tab 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:

1. Click the GUI tab on the Configurator.2. On the Refresh Rates sub-tab, configure the following parameters:

Chapter 15Customizing the NVBU Console

86
Figure 15-1:
Refresh-Ratessub-tab on

GUI tab

Job Refresh Rate in Milliseconds – Enter or select the refresh rate for the NVBU Jobs window in this box. 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 in this box. 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 in this box. 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 in this box. The refresh rate is specified in milliseconds. The default value for this parameter is 500 milliseconds. Operator Messages Refresh Rate in Milliseconds – Enter or select the the refresh rate for operator messages on the NVBU Status window in this box. The refresh rate is specified in milliseconds. The default value for this parameter is 500 milliseconds.


15.2.0 Configuring Custom Color Codes for Job StatusNVBU uses color-coding to indicate whether a job is currently running, scheduled to run later or completed. It uses different background colors to display the status of the jobs listed on the NVBU Jobs and NVBU Status windows. The default color codes are listed in the table below:


87

You can configure custom color codes for job status from the Colors sub-tab on the GUI tab. To customize the color-coding for job status, perform the following steps:

1. Click the GUI tab on the Configurator.2. Click the Colors sub-tab.3. Configure the following parameters:

Figure 15-2:Colors sub-tab

on GUI tab

Color of Scheduled Jobs – This parameter determines the background color for the recurring and non-recurring jobs scheduled to run later. The default color is blue. To configure a custom background color for the scheduled jobs, enter an RGB value for the new color in the Color of Scheduled Jobs box. Color of Running Jobs – This parameter determines the background color for currently active jobs. The default color is yellow. To configure a custom background color for the running jobs, enter an RGB value for the new color in the Color of Running Jobs box.Color of Completed Jobs – This parameter determines the background color for the completed jobs. The default color is white. To configure a custom background color for the completed jobs, enter an RGB value for the new color in the Color of Completed Jobs box.


Job Status Background ColorRunning Jobs Yellow

Scheduled Jobs Blue

Completed Jobs White (Normal)


88

15.3.0 Customizing NVBU Logs WindowA large amount of logs can increase the time it takes to open the NVBU Logs window. To overcome this problem, you can reduce the number of logs that are displayed on this window. This setting can be configured from the Logging sub-tab on the GUI tab. To configure the maximum number of records displayed on the NVBU Logs window, perform the following steps:

1. Click the GUI tab on the Configurator.2. Click the Logging sub-tab.3. Configure the following parameter:

Figure 15-3:Logging

sub-tab onGUI 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.


15.4.0 Disabling NVBU Logs WindowWhen NVBU Console is running on a remote client, you can disable the NVBU Logs window to avoid sending logs over the network. This setting can be configured from the Logging sub-tab on the GUI tab. To disable the NVBU Logs window on remote clients, perform the following steps:


Disable Logs Screen – Select this check box. 4. Click OK to apply the changes and exit Configurator. Alternatively, click



89

15.5.0 Customizing Device Log ViewsThe 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. You can change this setting from the GUI, Devices sub-tab on the Configurator. To configure the number of days device logs are displayed on NVBU Console, perform the following steps:

1. Click the GUI tab on the Configurator.2. Click the Devices sub-tab.3. Configure the following parameter:

Figure 15-4:Devices

sub-tab onGUI 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 system logs, refer to Customizing the Log Daemon on page 35.


15.6.0 Hiding Device LogsTo 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. 4. Click OK to apply the changes and exit Configurator. Alternatively, click



90

15.7.0 Configuring View-Levels for Mac OS X The view-level setting determines which configuration settings are displayed on NVAdmin. It is only applicable to the NVBU native Mac OS X interface. It allows you to hide options displayed on the NVBU Settings pane on Mac OS X, which can be used to restrict user access to configuration settings. To change the view-level settings, perform the following steps:

1. Click the GUI tab on the Configurator.2. Click the Advanced sub-tab.3. Configure the following parameter:

Figure 15-5:Advancedsub-tab 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 available configuration settings displayed on the NVBU Settings pane.



91

Chapter 16:

CONFIGURING GENERALSETTINGS FOR NVBU

Relocating Logs and NVDB DirectoriesTuning TCP/IP Buffer SizesDisabling Pre-installation Compatibility Checks for PackagesRemoving Target Set Checks for Duplication Jobs

16.1.0 Relocating Logs and NVDB DirectoriesTo store the database, logs and temporary files, NVBU creates the following directories during installation:

These directories can be relocated to another drive or volume to alleviate low disk space issues.

Note: The NVBU Service must 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. Configure the following parameters:

Directory Name Default File Path ContentsDatabase <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 system 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

Chapter 16Configuring General Settings for NVBU

92
Figure 16-1:General tab
Note: The directories to which you want to relocate NVBU logs or databases must already exist. NVBU will not create the target directories for you.

Database Directory – To relocate the NVBU database directory, enter the absolute file path for the new directory in the Database Directory box.Trace Directory – To relocate the directory to which the trace logs are written, enter the absolute file path for the new directory in the Trace Directory box. 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 – To relocate the directory to which the system logs are written, enter the absolute file path for the new directory in the Log Directory box.Temporary Directory – To relocate the directory to which the temporary are written, enter the absolute file path for the new directory in the Temporary Directory box. The temporary directory holds the Backup Saveset Index. The free disk space on this directory must 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 must have at least 9GB of free disk space. NVBU will generate warnings and logs if the free disk space on temporary directory is insufficient.


93

Reports Directory – To relocate the directory that holds the report templates and components, enter the absolute file path for the new directory in the Reports Directory box.Statistics Directory – To relocate the directory that holds the data collected by the nvstatsmngr process, enter the absolute file path for the new directory in the Statistics Directory box.


16.2.0 Tuning TCP/IP Buffer SizesIn 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 in the appropriate box. The values must be set in KB.



94

16.3.0 Disabling Pre-installation Compatibility Checks for PackagesNVBU 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:


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.


16.4.0 Removing Target Set Checks for Duplication JobsBy 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.

1. Click the GUI tab on the Configurator.2. Click the Jobs sub-tab.3. On the Jobs sub-tab configure the following parameter:


95

Figure 16-2:Jobs sub-tab

on GUI tab

Permit Duplicate Phase With No Target Set – By default, this check box is not selected forcing you to specify a target set for the duplication jobs. To make target set optional, select the Permit Duplicate Phase With No Target Set check box.



96


97

Chapter 17:

CONFIGURING THE REPORTINGSYSTEM

NVBU Reporting System – An OverviewStatistics Manager and Reports Database Manager – An OverviewCustomizing the Output Format

Customizing the HTML Output FormatCustomizing the Plain Text Output FormatCustomizing the CSV Output Format

Configuring the Default Output Format for User-defined ComponentsConfiguring the Filter ViewConfiguring the Retention Period for Historic ReportsEnabling “Keep Filtered Out Records” for All ReportsCustomizing Statistics ManagerConfiguring Statistics Collection and Transmission ParametersDisabling Statistics Collection on an NVBU ClientCreating User-defined Purge Policies

Creating a Global Policy for Purging the Reports DatabaseCreating a User-defined Schedule for Purging Report TablesDisabling Global Purge Policy for Reports DatabaseCreating a Table-Specific Purge Policy for “Default” TableCreating a Table-Specific Purge Policy for Report TablesApplying Global Purge Policy to Individual Report Tables

Configuring a Default Browser on Linux/UNIX

Chapter 17Configuring the Reporting System

98

17.1.0 NVBU Reporting System – An OverviewNVBU offers an advanced reporting system which can be used to generate Canned and Custom reports in the following formats:

HTMLPlain textComma 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 system 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 OverviewThe 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 statisticsEvent historyMedia requestsServer capacityTransfer 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.


99

17.3.0 Customizing the Output FormatThis section describes how to customize the output format for the HTML, Plain Text and CSV reports. The information in this section is organized as follows:

Customizing the HTML Output FormatCustomizing the Plain Text Output FormatCustomizing the CSV Output Format

17.3.1 Customizing the HTML Output FormatNVBU 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 sub-tab on the Reporting tab. These settings must 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 sub-tab, configure the following parameters as

described below:Pre-text for HTML Output of Plain Text Post-text for HTML Output of Plain Text Default HTML Column Header for Pre-textDefault HTML Column Header for Post-textDefault HTML Column Header Field Pre-textDefault HTML Column Header Field Post-textDefault Text to Output for an HTML Report with No RecordsDefault HTML Total Row Pre-textDefault HTML Total Row Post-textDefault HTML Total Field Pre-textDefault HTML Total Field Post-textDefault HTML Average Row Pre-textDefault HTML Average Row Post-textDefault HTML Average Field Pre-textDefault HTML Average Field Post-textDefault HTML Format Pre-textDefault HTML Format Post-textDefault HTML Format Field Pre-text


100

Default HTML Format Field Post-textFigure 17-1: HTML Text

Output sub-tabon Reporting

tab

Use the pre-text boxes to specify the following:Opening HTML tags for custom formatting styles, e.g., font type, font size, bold, etc.Text or description for headers, total or average rows, or body cells.

Use the post-text boxes 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 the Default Text to Output for an HTML Report With No Records box.



101

17.3.2 Customizing the Plain Text Output FormatNVBU 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 sub-tab on the Reporting tab. These settings must 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, perform the following steps:

1. Click the Reporting tab on the Configurator.2. Click the Plain Text Output sub-tab.3. Configure the following parameters:

Figure 17-2: Plain Text

Output sub-tabon Reporting

tab

Default Plain Text Column Header Pre-textDefault Plain Text Column Header Post-textDefault Text to Output for a Plain Text Report with No RecordsDefault Plain Text Total Row Pre-textDefault Plain Text Total Row Post-textDefault Plain Text Total Field Pre-textDefault Plain Text Total Field Post-textDefault Plain Text Average Row Pre-textDefault Plain Text Average Row Post-text


102

Default Plain Text Average Field Pre-textDefault Plain Text Average Field Post-textDefault Plain Text Format Pre-textDefault Plain Text Format Post-textDefault Plain Text Format Field Pre-textDefault Plain Text Format Field Post-text

Use the pre-text boxes to specify the following:Line breaks, separators, etc.Text or description for headers, total or average rows, or body cells

Use the post-text boxes to specify the following:Line breaks, separators, etc.

For reports with no records, you can replace the default text “Nothing to Display” with your own text in the Default Text to Output for a Plain Text Report With No Records box.


17.3.3 Customizing the CSV Output FormatNVBU 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 sub-tab on the Reporting tab. These settings must 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:

1. Click the Reporting tab on the Configurator.2. Click the CSV Output sub-tab.3. Configure the following parameters:


103

Figure 17-3: CSV Output

sub-tab onReporting tab

Default CSV Column Header Pre-textDefault CSV Column Header Post-textDefault CSV Header Field Pre-textDefault CSV Header Field Post-textDefault Text to Output for a CSV Report with No RecordsDefault CSV Format Pre-textDefault CSV Format Post-textDefault CSV Format Field Pre-textDefault CSV Format Field Post-text

Use the pre-text boxes to specify the following:Line breaks, tabs, separators, etc.Text or description for headers, total or average rows, or body cells

Use the post-text boxes to specify the following:Custom delimiterLine breaks, separators, etc.

For reports with no records, you can replace the default text “Nothing to Export” with your own text in the Default Text to Output for a CSV Report With No Records box.



104

17.4.0 Configuring the Default Output Format for User-defined ComponentsBy default, the output format for user-defined components is set to HTML. To change this setting, perform the following steps:

1. Click the Reporting tab on the Configurator.2. Click the Misc sub-tab.3. Configure the following parameter:

Figure 17-4: Output typeslisted on Misc

sub-tab

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.


17.5.0 Configuring the Filter ViewNVBU provides two views to create and view filter expressions for reports:

SimpleAdvanced

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:



105

Figure 17-5: Misc sub-tabon 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 ReportsNVBU 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:


Duration to Keep Produced Reports – The default retention period for historic reports is 14 days. To change it, enter the new retention period in the Duration to Keep Produced Reports box.


17.7.0 Enabling “Keep Filtered Out Records” for All ReportsNVBU 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:


106


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:

1. Click the Reporting tab on the Configurator.2. Click the Stats Collection sub-tab.3. Configure the following parameters:

Figure 17-6:Stats

Collection sub-tab on

Reporting tab

Statistics Gathering Window – By default, the Statistics Manager process 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, configure the following parameters:

Statistics Gathering Window Start – Enter or select the start time in this box.Statistics Gathering Window End – Enter or select the end time in this box.

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 – In the Frequency box, 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 secondsRecords per Storage File – In the Records per Storage File box, enter or select the maximum number of statistical records per file. The Statistics


107

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

1. Click the Reporting tab on the Configurator.2. Click the Stats Provision sub-tab.3. Configure the following parameters:

Figure 17-7:Stats Provision

sub-tab onReporting tab

Absent Server Threshold – In the Absent Server Threshold box, 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 – In the Transmit Block Size box, 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 – In the Minimum Stats Manager Cache box, enter the minimum cache for Statistics Manager. This parameter is set in number of records. By default, it is set to 30 records.


108


17.10.0 Disabling Statistics Collection on an NVBU ClientStatistics 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:

1. Click the Reporting tab on the Configurator.2. Click the Stats Provision sub-tab.3. Configure the following parameter:

Enable Stats Collection on this Machine – Click to clear this check box.4. Click OK to apply the changes and exit Configurator. Alternatively, click


17.11.0 Creating User-defined Purge PoliciesThis 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 DatabaseCreating a User-defined Schedule for Purging Report TablesDisabling Global Purge Policy for Reports DatabaseCreating a Table-Specific Purge Policy for “Default” TableCreating a Table-Specific Purge Policy for Report TablesApplying Global Purge Policy to Individual Report Tables

17.11.1 Creating a Global Policy for Purging the Reports DatabaseThe 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.


109

To create a user-defined global policy for purging the reports database, perform the following steps:

1. Click the Reporting tab on the Configurator.2. Click the Tables sub-tab.3. Select one of the following methods to delete obsolete records:

Figure 17-8: Parameters

for creating auser-definedglobal purge

policy

a. Age-based Purge Policy – For a purge policy based on the age of the records, configure the following parameters:1. In the Global Purge Method list, select By Date.2. In the Global Purge Time Limit box, 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.

b. Size-based Purge Policy – For a purge policy based on the table size, configure the following parameters:1. In the Global Purge Method list, select By Space Used.2. In the Global Purge Space Limit box, 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 109.


17.11.2 Creating a User-defined Schedule for Purging Report TablesThe 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:

1. Click the Reporting tab on the Configurator.2. Click the Tables sub-tab.3. Configure the following parameter:


110

Purge Check Frequency – In the Purge Check Frequency box, enter or select the time interval between two purge events. The purge frequency is specified in number of hours.


17.11.3 Disabling Global Purge Policy for Reports DatabaseBy 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 table-specific 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 – Click to clear this check box.


17.11.4 Creating a Table-Specific Purge Policy for “Default” TableThe 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 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:

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 default table exceeds a certain size.

To create a table-specific purge policy for the default table, perform the following steps:

1. Click the Reporting tab on the Configurator.2. Click the Tables sub-tab.3. Disable global purge policy at the database level. For details, refer to

Disabling Global Purge Policy for Reports Database on page 110.4. Select one of the following methods to delete obsolete records:


111

Figure 17-9:Parameters for

creating auser-definedpurge policy

for defaulttable

a. Age-based Purge Policy – For a purge policy based on the age of the records, configure the following parameters:1. In the Table Default Method list, select By Date.2. In the Table Default Purge Time Limit box, 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.

b. Size-based Purge Policy – For a purge policy based on the table size, configure the following parameters:1. In the Table Default Purge Method list, select By Space Used.2. In the Table Default Purge Space Limit box, 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.



17.11.5 Creating a Table-Specific Purge Policy for Report TablesBy 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:

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 table-specific purge policy for individual report tables, perform the following steps:


112

1. Click the Reporting tab on the Configurator.2. Click the Tables sub-tab.3. Disable global purge policy at the database level. For details, refer to

Disabling Global Purge Policy for Reports Database on page 110.4. Select one of the following methods to delete obsolete records:

Figure 17-10: Parametersfor creating

user-definedpurge policyfor individual

tables

a. Age-based Purge Policy – For a purge policy based on the age of the records, configure the following parameters:1. In the Table <Table Name> Purge Method list, select By Date.2. In the Table <Table Name> Purge Time Limit box, 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.

The table-specific policies can be created for the following tables:EventsMediacapacitiesMediarequests


113

MediatransfersDriveeventsDriveperformanceJobfiletallies

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

b. Size-based Purge Policy – For a purge policy based on the table size, configure the following parameters:1. In the Table <Table Name> Purge Method list, select By Space

Used.2. In the Table <Table Name> Purge Space Limit box, 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.

The table-specific policies can be created for the following tables:EventsMediacapacitiesMediarequestsMediatransfersDriveeventsDriveperformanceJobfiletallies

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



17.11.6 Applying Global Purge Policy to Individual Report TablesNVBU 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:



114

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:

EventsMediacapacitiesMediarequestsMediatransfersDriveeventsDriveperformanceJobfiletallies

Configure the corresponding parameter, depending on the report table for which you want to use the global policy.


17.12.0 Configuring a Default Browser on Linux/UNIXOn Linux and UNIX based platforms, you must configure a default browser to view the HTML reports. To accomplish this, perform the following steps:

1. Click the GUI tab on the Configurator.2. Click the Browser sub-tab.3. Configure the following parameters:

UNIX Default Web Browser – Enter the full file path for the browser in the UNIX Default Web Browser box (e.g., /usr/bin/mozilla, /usr/bin/firefox).UNIX Browser Switches – Enter any switches to be used in the UNIX Browser Switches box.



115

Chapter 18:

CONFIGURING LANGUAGESETTINGS FOR NVBU

Changing Locale SettingCorrecting Locale ChangesDisabling Post-Installation Locale ChangesConfiguring Display Properties for Localized Versions

Changing the Font Size for NVBU ConsoleChanging the Date Format

18.1.0 Changing Locale SettingNVBU is available in 7 localized versions, including the following:

Chinese (Simplified)Chinese (Traditional)EnglishFrenchGermanJapaneseKorean

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 must be restarted to apply any changes to the locale settings.

To change the locale setting for NVBU

1. Click the General tab on the Configurator.2. Configure the following parameter:

Note: Before proceeding ensure that the Allow GUI to Change Locale check box on the Language > Locale sub-tab is selected.

Chapter 18Configuring Language Settings for NVBU

116
Figure 18-1:
LanguageSelection 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 ChangesYou 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, perform the following steps:

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 (6), and press Enter.5. Enter the number corresponding to the Language Selection option (17), and

press Enter.6. Enter the number corresponding to preferred language (for example, 5 for

Japanese). Press Enter.


117

7. Enter s and press Enter.8. Enter q and press Enter.

18.3.0 Disabling Post-Installation Locale ChangesTo prevent locale changes after installation, perform the following steps:

1. Click the Language tab on the Configurator.2. Click the Locale sub-tab.3. On the Locale sub-tab configure the following parameter:

Figure 18-2:Locale

sub-tab onLanguage tab

Allow GUI to Change Locale – Click to clear this check box.4. Click OK to apply the changes and exit Configurator. Alternatively, click


18.4.0 Configuring Display Properties for Localized VersionsFor 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 ConsoleNVBU 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:

1. Click the Language tab on the Configurator.2. On the Font sub-tab configure the following parameter:

Figure 18-3:Font sub-tabon Language

tab

Default GUI Font Point Size – In the Default GUI Font Point Size box, enter or select the appropriate font-size depending on the display language for NVBU.

Chapter 18Configuring Language Settings for NVBU

118


18.4.2 Changing the Date FormatThe 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, perform the following steps:

1. Click the Language tab on the Configurator.2. Click the Display sub-tab.3. On the Display sub-tab configure the following parameter:

Figure 18-4:Display

sub-tab onLanguage tab

Display Date in Order DoW – Select this check box to change the default date format to Year/Month/Date/Day of Week.



119

Chapter 19:

SETTING UP A BAKBONE TIMESERVER

BakBone Time – An OverviewConfiguring an Alternate BakBone Time Server

19.1.0 BakBone Time – An OverviewNVBU 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 ServerBy 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 must 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.

Chapter 19Setting Up a BakBone Time Server

120

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.



121

Chapter 20:

USING THE TRACE TOOL

Trace Logs – An OverviewTrace LevelsDate and Time in Trace Files

Setting Trace LevelsEnabling TracingDisabling TracingEnabling Circular Logging of Trace Messages

20.1.0 Trace Logs – An OverviewTracing is a logging technique that captures diagnostic information about events and error conditions occurring within the NVBU system. This feature is provided to assist Quest Support troubleshoot problems within the system.

Important: The Trace feature must only be used under the direction of Quest Support.

Tracing is disabled by default. To generate trace logs, you must 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 91. By default, NVBU creates a single trace file for each process which continues to grow as tracing messages are appended. The maximum file size depends on the O/S and file system in use. You can override this behavior and configure circular tracing attributes using Configurator.

20.1.1 Trace LevelsTrace 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:

Chapter 20Using the Trace Tool

122

20.1.2 Date and Time in Trace FilesThe date and time values in the trace logs can either be based 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 119.

Note: For timestamp in trace logs, NVBU uses the format hhmmss.mmmmmm (Hours, Minutes, Seconds and Milliseconds). 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 LevelsTo 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:

Trace Levels Level of DetailDEFAULT 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


123

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.

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


124

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:

DEFAULTALWAYSNORMALVERBOSELIBNORMALLIBVERBOSEDEBUGLIBDEBUG


Important: The NVBU Service must 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 TracingTracing is not enabled by default. You have to start it manually after setting the trace levels. To enable tracing, perform the following steps:

1. Click the General tab on the Configurator.Figure 20-2:

Trace Settingson General tab


125

2. Select the Generate Debugging Files check box.3. Click OK to apply the changes and exit Configurator. Alternatively, click

Apply to commit the new settings and remain in Configurator.4. Restart the NVBU Service.

20.4.0 Disabling TracingOnce the required trace logs have been obtained, perform the following steps to stop tracing:

1. Click the General tab on the Configurator.2. Configure the following parameter:

Generate Debugging Files – Click to clear this check box.3. Click OK to apply the changes and exit Configurator. Alternatively, click

Apply to commit the new settings and remain in Configurator.4. Restart the NVBU Service.

20.5.0 Enabling Circular Logging of Trace MessagesBy default, NVBU creates a single trace file for each process which continues to grow as trace logs are appended. 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 keep. 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 of trace messages, perform the following steps:


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

Whether circular tracing is enabled or notWhen circular tracing is enabled, the maximum number of lines for each trace file

The default value for Lines per Trace File attribute is zero, which denotes No Circular Tracing. 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 must set the Trace Files to Keep Per Session parameter.


126

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



127

Chapter 21:

USING THE TXTCONFIG TOOL

Txtconfig – An OverviewStarting TxtconfigCustomizing the Default Settings Using TxtconfigExamples

Customizing the Auditor Daemon to Log Failed User RequestsCreating a Size-based Purge Policy for Audit LogsCustomizing the Purge Schedule for Audit Logs

21.1.0 Txtconfig – An OverviewTxtconfig is an alternative configuration tool, which 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 started from any directory, and requires root privileges. Various settings are presented as Configuration Pages and similar to the options provided on the Configurator.

21.2.0 Starting TxtconfigTo start Txtconfig, perform the following steps:

1. Start a terminal session.2. Issue the following command at the prompt, followed by Enter or Return:

txtconfig

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.

Chapter 21Using the Txtconfig Tool

128

21.3.0 Customizing the Default Settings Using TxtconfigUpon 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.Figure 21-1:

Main Menu forTxtconfig

To open a Configuration Page, press the corresponding number (for example, 5, 14 or 20).To set or change the value for a parameter, do the following:

To save the changes, press s.To quit Txtconfig, press q.

Note: For details on various configuration settings, refer to the individual chapters in this guide.

Type of Value ActionEnable/Disable; On/Off Just select the option to change its state. It functions as a

toggle key.

List (Numeric) Press the corresponding number, followed by Enter or Return to select a value from a list.

Numeric Type the required number, followed by Enter or Return.

String Type the required characters, followed by Enter or Return.


129

21.4.0 ExamplesThe following examples show how to customize the Auditor Daemon using Txtconfig.

Figure 21-2:Configuration

options forAuditor

Daemon

21.4.1 Customizing the Auditor Daemon to Log Failed User RequestsBy 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. Start Txtconfig.2. At the prompt on the Machine page, press p.3. At the prompt on the Main Menu, press 5.4. By default, the Only Record Failed Requests in the Audit Trail option is set

to OFF. Press 1 at the prompt to enable it.5. To save the new settings to the configuration file, press s at the prompt.

21.4.2 Creating a Size-based Purge Policy for Audit LogsTo create a size-based purge policy for audit logs, perform the following steps:

1. Start Txtconfig.2. At the prompt on the Machine page, press p.3. At the prompt on the Main Menu, press 5.4. By default, the Purge Type parameter is set to By Age. To change it, press 2.5. To select the By Size option in the list, press 2 at the prompt.6. To change the maximum file size of audit logs, press 3. At the prompt, enter

the file size in MB and press Enter or Return.7. To save the new settings to the configuration file, press s at the prompt.

Chapter 21Using the Txtconfig Tool

130

21.4.3 Customizing the Purge Schedule for Audit LogsBy default, automatic purging occurs every 24 hours. To create a user-defined schedule for purging audit logs, perform the following steps:

1. Start Txtconfig.2. At the prompt on the Machine page, press p.3. At the prompt on the Main Menu, press 5.4. To change the purge schedule, press 5.5. At the prompt, enter the interval and press Enter or Return.6. To save the new settings to the configuration file, press s at the prompt.

Documents

Quest NetVault Backup - usdownloads.quest…usdownloads.quest.com.edgesuite.net/Repository/support.quest.com... · NVG-103-8.6.x-EN-01 09/29/11 Quest® NetVault® Backup version 8.6.x