+ All Categories
Home > Documents > Veritas NetBackup â„¢ Troubleshooting Guide: UNIX - Symantec

Veritas NetBackup â„¢ Troubleshooting Guide: UNIX - Symantec

Date post: 09-Feb-2022
Category:
Upload: others
View: 29 times
Download: 0 times
Share this document with a friend
721
Veritas NetBackup ™ Troubleshooting Guide UNIX, Windows, and Linux Release 6.5.6 20654032
Transcript

Veritas NetBackup ™Troubleshooting Guide

UNIX, Windows, and Linux

Release 6.5.6

20654032

Veritas NetBackup ™ Troubleshooting GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version: 7.0.1

PN: 20654032

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in the U.S. and other countries. Other names may be trademarksof their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

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

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

Printed in the United States of America.

10 9 8 7 6 5 4 3 2 1

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrades protection

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:

www.symantec.com/business/support/

Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport web page at the following URL:

www.symantec.com/business/support/

Customer serviceCustomer service information is available at the following URL:

www.symantec.com/business/support/

Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals

Support agreement resourcesIf you want to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

Managed Services remove the burden of managing and monitoring securitydevices and events, ensuring rapid response to real threats.

Managed Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Education Services provide a full array of technical training, security education,security certification, and awareness communication programs.

Education Services

To access more information about enterprise services, please visit our web siteat the following URL:

www.symantec.com/business/services/

Select your country or language from the site index.

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

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Define the problem .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What was the error indication? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13What were you doing when the problem occurred? .... . . . . . . . . . . . . . . . . . . . 14

Record all information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Troubleshooting the problem .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16About gathering information for problem reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

General information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Gathering information for NetBackup-Java .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2 Troubleshooting procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

About troubleshooting procedures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Preliminary troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Troubleshooting installation and configuration problems .... . . . . . . . . . . . . . . . . 27

Resolving installation problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Resolving common configuration problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

General test and troubleshooting procedures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Testing the master server and clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Testing media server and clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Resolving network communication problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . 40Verifying host name and service entries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Using bpclntcmd .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Host name and service entry examples - UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . 54

Using the Host Properties window .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Resolving full disk problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Troubleshooting frozen media ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Resolving PBX problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Checking for PBX installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Checking that PBX is running .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68PBX must be set correctly ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68PBX logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69PBX security ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Contents

Required NetBackup daemon or service not available ... . . . . . . . . . . . . . . . . . 71New network interface cards ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Backup performance and NIC cards ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72SERVER entries in bp.conf file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Resolving unavailable storage units problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Troubleshooting NetBackup in a SAN environment .... . . . . . . . . . . . . . . . . . . . . . . . . 74

NetBackup enterprise lifecycle: best practices ... . . . . . . . . . . . . . . . . . . . . . . . . . . 75Using CommandCentral Storage to troubleshoot

NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Common NetBackup troubleshooting use cases ... . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 3 Using logs and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

About using logs and reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Where is the log and report information? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Status for user operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84UNIX system logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Debug logs on servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Unified logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Configuring and using unified logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Submitting unified logging files to Symantec support ... . . . . . . . . . . . . . . 101Legacy NetBackup logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Logs to accompany problem reports for synthetic backup .... . . . . . . . . 113

Debug logs on UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Unified logging on UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Legacy logging on UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Controlling log size on UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Client logging file name format on UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . 117How to set logging levels on UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Debug logs on PC clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Unified logging on PC clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Legacy debug logging on PC clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Controlling log size on PC clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Client logging file name format on PC clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . 122How to set logging levels on PC clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Windows Event Viewer logging option .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Enabling the logging tool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123eventlog file entries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Example ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Troubleshooting the Administration Console for UNIX .... . . . . . . . . . . . . . . . . . . 125Required disk space for logging and temporary files ... . . . . . . . . . . . . . . . . 126Enabling detailed debug logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Contents8

Query string overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Data types for fields ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128String constants ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Query string examples ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Chapter 4 Using NetBackup utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

About using NetBackup utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Analysis utilities for NetBackup debug logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Installation requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Output format ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133How to run the log analysis utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Network troubleshooting utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136NetBackup support utility (nbsu) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

When to use nbsu .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137nbsu progress display .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138nbsu output ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139nbsu and NetBackup status codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Notes on running nbsu .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

NetBackup consistency check (NBCC) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143When to use NBCC .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144NBCC progress display .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Server aliases file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147NBCC output ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Notes on running NBCC .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

NetBackup consistency check repair (NBCCR) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151NBCCR files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

The nbcplogs utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Chapter 5 NetBackup status codes and messages . . . . . . . . . . . . . . . . . . . . . . . . 155

About NetBackup status codes and messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155NetBackup status codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156NetBackup Messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

Chapter 6 Media and device management status codes andmessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

About media and device management status codes andmessages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Using debug logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Media Manager status codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424Device configuration status codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

9Contents

Device management status codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507Robotic status codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529Robotic error codes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

Media and device management messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551

Chapter 7 Disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

About disaster recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571Recommended backup practices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Selecting files to back up .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Bare Metal Restore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572Critical policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573Full backup after catalog recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573Online catalog backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573Online catalog backup disaster recovery files ... . . . . . . . . . . . . . . . . . . . . . . . . . . 573Automated recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573Online catalog disaster recovery information email ... . . . . . . . . . . . . . . . . . 574Identifying the correct catalog backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574Catalog recovery time .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574Master and media server backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

Disk recovery procedures for UNIX and Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575Recovering the master server disk for UNIX and Linux .... . . . . . . . . . . . . 575Recovering the NetBackup media server disk for UNIX and

Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581Recovering the client disk ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

Disk recovery procedures for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582Recovering the master server disk for Windows .... . . . . . . . . . . . . . . . . . . . . . 582Recovering the NetBackup media server disk for Windows .... . . . . . . . 588Recovering the client disk ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

Catalog recovery from an online backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591Recovering the entire catalog from an online backup .... . . . . . . . . . . . . . . 592Recovering the catalog image file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600Recovering relational database files from an online catalog

backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610Recovering NetBackup access management components from a

hot backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614Recovering the catalog using a copy of an online catalog

backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615Recovering the catalog without the disaster recovery file ... . . . . . . . . . . 615Recovering the user-directed online catalog from the CLI ... . . . . . . . . . 620Restoring files from an online catalog backup .... . . . . . . . . . . . . . . . . . . . . . . . . 623Unfreezing online catalog recovery media ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

Clustered NBU server recovery for UNIX and Linux .... . . . . . . . . . . . . . . . . . . . . . . 625

Contents10

Replacing a failed node on a UNIX or Linux cluster ... . . . . . . . . . . . . . . . . . . 625Recovering the shared disk on a UNIX or Linux cluster ... . . . . . . . . . . . . . 626Recovering the entire UNIX or Linux cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

Clustered NBU server recovery for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628Replacing a failed node on a Windows VCS cluster ... . . . . . . . . . . . . . . . . . . . 629Recovering the shared disk on a Windows VCS cluster ... . . . . . . . . . . . . . 629Recovering the entire Windows VCS cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

Appendix A Backup and restore functional overview . . . . . . . . . . . . . . . . . . . . . . 633

About backup and restore functional overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633Backup and restore startup process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634Backup and archive processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

Job scheduling .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634EMM server and master server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Backups and archives - UNIX clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635Backup process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636Backup with multiple data streams .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640Snapshot backup and Windows open file backups .... . . . . . . . . . . . . . . . . . . . 641SAN client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644Backups and archives - Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647Backups and archives - NetWare clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648Synthetic backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649NetBackup online, hot catalog backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652

Restore processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654Restoring UNIX and Linux clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654Restoring SAN client (UNIX or Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658Restoring Windows clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661Restoring NetWare clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662Restoring catalog backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664

NetBackup directories and files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665NetBackup directory structure - UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666Contents of /usr/openv/netbackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

NetBackup programs and daemons .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669NetBackup catalogs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

Appendix B Media and device management functionaldescription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685

Media and device management startup process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685Media and device management process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687Shared Storage option management process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689Barcode operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691Media and device management components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693

11Contents

Appendix C Networks and hostnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

Background for troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

Appendix D Robotic test utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

About robotic test utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709Robotic tests on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709Robotic tests on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

Contents12

Introduction

This chapter includes the following topics:

■ About Troubleshooting

■ Define the problem

■ Record all information

■ Troubleshooting the problem

■ About gathering information for problem reports

About TroubleshootingThis chapter explains the steps to take if you encounter a problem while you useNetBackup. Other chapters provide more specific information.

Note: The term "media server", as distinct from "master server" or "server", mayor may not apply to the NetBackup server product. It depends on the context.When you troubleshoot a server installation, be aware that only one host exists:the master and the media server are one and the same. You can ignore referencesto a media server on a different host.

Define the problemThe first step in troubleshooting is to define the problem.

What was the error indication?To define the problem, you must know what went wrong. Sometimes the resolutionof the problem also requires that you know what went right.

1Chapter

Error messages are usually the vehicle for telling you something went wrong. Sothe first thing to do is to look for an error message. If you don’t see an errormessage in an interface, but still suspect a problem, check the reports and logs.NetBackup provides extensive reporting and logging facilities. These can providean error message that points you directly to a solution.

The logs also show you what went right and the NetBackup operation that wasongoing when the problem occurred. For example, a restore operation needs mediato be mounted, but the required media is currently in use for another backup. Thelog information that NetBackup provides is available:

See “About using logs and reports” on page 81.

The following chapters provide interpretations of NetBackup (and Media Manager)status codes and messages.

What were you doing when the problem occurred?Another important part in troubleshooting the problem is to define what you triedto do in the first place.

Some questions to ask are as follows:

■ What operation was tried?

■ What method did you use? For example, more than one way exists to installsoftware on a client. Also more than one possible interface exists to use formany operations. Some operations can be performed with a script.

■ What type of server platform and operating system was involved?

■ If your site uses both the master and the media servers, was it a master or amedia server?

■ If a client was involved, what type of client was it?

■ Have you performed the operation successfully in the past? If so, what isdifferent now?

■ What is the service pack level?

■ Do you use operating system software with the latest fixes supplied, especiallythose required for use with NetBackup?

■ Is your device firmware at a level, or higher than the level, at which it has beentested according to the posted device compatibility lists?

IntroductionDefine the problem

14

Record all informationAs you define and troubleshoot a problem, always try to capture potentiallyvaluable information, such as the following:

■ NetBackup progress logs

■ NetBackup Reports

■ NetBackup Utility Reports

■ NetBackup debug logs

■ Media and Device Management debug logs

■ On UNIX NetBackup servers, check for error or status messages in the systemlog or standard output.

■ Error or status messages in dialog boxes

■ On Windows, NetBackup servers, check for error or status information in theEvent Viewer Application and System log.

Record this information for each try. A benefit of this approach is that you cancompare the results of multiple tries. A record of tries is also useful for others atyour site and for customer support in the event that you cannot solve the problem.Explanations of the various logs are available.

See “About using logs and reports” on page 81.

On UNIX systems, the /usr/openv/netbackup/bin/goodies/support scriptcreates a file containing data necessary for customer support to debug anyproblems you encounter. For more details, consult the usage information of thescript by using support -h.

If your troubleshooting try is unsuccessful, customer support can provide furtherassistance. Before you call, have the following information ready:

■ The following product, platform, and device information:

■ Product and its release level.

■ Server hardware type and operating system level.

■ Client hardware type and operating system level, if a client is involved.

■ Storage units being used, if it is possible that storage units are involved.

■ If it looks like a device problem, be ready to supply the following deviceinformation: The types of robots and drives and their version levels alongwith Media and Device Management and system configuration information.

■ Software patches to the products that were installed.

15IntroductionRecord all information

■ The service packs and hotfixes that were installed.

■ What is the definition of the problem as described earlier in this chapter?Copies of logs or core dumps (if any) can also be required.

■ Have you had this problem before? If so, was there a successful resolution andwhat did you try that time?

■ Has the configuration recently changed? If so, what changed?

■ If necessary, can you communicate with technical support through ftp, email,or fax? These are useful for when you send information such as copies of logs.

The following topic contains the information you need and also provides methodsfor gathering information.

See “About gathering information for problem reports” on page 16.

Troubleshooting the problemAfter you define the problem, use the following information in the other chaptersof this manual to correct it:

■ When you have a status code or message, the recommended corrective actionis available.See “About NetBackup status codes and messages” on page 155.See “About media and device management status codes and messages”on page 423.

■ If no status code or message exists, or the actions in the status code chaptersdo not solve the problem, check the following topic:See “About troubleshooting procedures” on page 21.Those procedures describe an effective approach for isolating commonproblems.

If you don’t find the solution, contact customer support.

The Symantec Technical Support site has a wealth of information that can helpyou solve NetBackup problems.

For comprehensive troubleshooting details, refer to the following URL:

http://entsupport.symantec.com

About gathering information for problem reportsFill out the following information when you contact support to report a problem.

IntroductionTroubleshooting the problem

16

General informationDate: _________________________

Table 1-1 Servers (master_and_media)

Product version andpatchlevels

OS LevelsPlatform types and hostnames

Table 1-2 Clients

Product version andpatchlevels

OS LevelsPlatform types and hostnames

Table 1-3 Devices

Tested firmware level thatis listed in the NetBackuphardware compatibilitylist

Firmware levelsRobotic library and drivemodels

What were you doing when the problem occurred? (for example, a backup on aWindows client)

______________________________________________________________________

______________________________________________________________________

What were the error indications? (for example, status code, error dialog box)

______________________________________________________________________

______________________________________________________________________

______________________________________________________________________

Did this problem occur during or shortly after any of the following:

_____ Initial installation

_____ Configuration change (explain)

17IntroductionAbout gathering information for problem reports

_____ System change or problem (explain)

_____ Have you observed the problem before? (If so, what did you do that time?)

Logs or other failure data you have saved:

_____ All log entries report

_____ Media and Device Management debug logs

_____ NetBackup debug logs

_____ System logs (UNIX)

_____ NetBackup Configuration Validation Utility Output (UNIX)

_____ Event Viewer Application and System logs (Windows)

Can you communicate with us through any of the following:

_____ ftp

_____ telnet

_____ email

_____ fax

Gathering information for NetBackup-JavaIf you encounter problems with the NetBackup-Java applications, use the followingmethods to gather data for Symantec support.

The following scripts are available for gathering information:

■ The NetBackup-Java administration application startup script, jnbSA, logsdata to a log file in /usr/openv/netbackup/logs/user_ops/nbjlogs. Atstartup, the script tells you which file in this directory it logs to. Normally,this file does not become very large (usually less than 2 KB). Consult the file/usr/openv/java/Debug.properties for the options that can affect thecontents of this log file.

■ The NetBackup-Java administration application on Windows logs data to a logfile if NetBackup is installed on the computer where the application was started.It logs on install_path\NetBackup\logs\user_ops\nbjlogs.

If NetBackup was not installed on this computer, then no log file is created.To produce a log file, modify the last "java.exe" line in the following to redirectoutput to a file: install_path\java\nbjava.bat.

■ The /usr/openv/java/get_trace script provides a Java virtual machine stacktrace for support to analyze. This stack trace is written to the log file that isassociated with the instance of execution (see previous bullet).

IntroductionAbout gathering information for problem reports

18

■ The /usr/openv/netbackup/bin/goodies/support script creates a filecontaining data necessary for customer support to debug any problems youencounter. For more details, consult the usage information of the script byusing support -h.

To get debug data for support to analyze

1 If the application does not respond for a long time, it may be hung. However,some operations can take quite a while to complete, especially Activity Monitorand Reports applications. Wait for several minutes before you assume thatthe operation is hung.

If there is no response within several minutes, run/usr/openv/java/get_trace under the account where you started the Javaapplication. This script causes a stack trace to write to the log file.

For example, if you started jnbSA from the root account, start/usr/openv/java/get_trace as root. Otherwise, the command runs withouterror, but fails to add the stack trace to the debug log. This failure occursbecause root is the only account that has permission to run the commandthat dumps the stack trace.

2 Run /usr/openv/netbackup/bin/goodies/support to get data about yourconfiguration. Run this script after you complete the NetBackup installationand every time you change the NetBackup configuration.

3 Provide the support-script output and log file to Symantec support.

19IntroductionAbout gathering information for problem reports

IntroductionAbout gathering information for problem reports

20

Troubleshooting procedures

This chapter includes the following topics:

■ About troubleshooting procedures

■ Preliminary troubleshooting

■ Troubleshooting installation and configuration problems

■ General test and troubleshooting procedures

■ Using the Host Properties window

■ Resolving full disk problems

■ Troubleshooting frozen media

■ Resolving PBX problems

■ New network interface cards

■ Backup performance and NIC cards

■ SERVER entries in bp.conf file

■ Resolving unavailable storage units problems

■ Troubleshooting NetBackup in a SAN environment

About troubleshooting proceduresThis chapter has procedures for finding the cause of NetBackup errors. Theseprocedures are general in nature and do not try to cover every problem that canoccur. They do, however, recommend the methods that usually result in successfulproblem resolution.

2Chapter

Note: The Symantec Technical Support site has a wealth of information that canhelp you solve NetBackup problems.

See http://entsupport.symantec.com for comprehensive troubleshooting details.

When you perform these procedures, try each step in sequence. If you alreadyperformed the action or it does not apply, skip to the next step. If it branches youto another topic, use the solutions that are suggested there. If you still have aproblem, go to the next step in the procedure. Also, alter your approach accordingto your configuration and what you have already tried.

Preliminary troubleshooting explains what to check first. It branches off to otherprocedures as appropriate.

Troubleshooting installation and configuration problems apply specifically toinstallation problems and configuration problems.

General test and troubleshooting procedures define general methods for findingserver and client problems and should be used last.

Note: The term "media server", as distinct from "master server" or "server", doesnot apply to the NetBackup server product. When you troubleshoot a NetBackupserver installation, ignore any references to media server. (This note does notapply to NetBackup Enterprise Server.)

Preliminary troubleshootingPreliminary troubleshooting explains what to check first and branches to otherprocedures as appropriate.

Troubleshooting proceduresPreliminary troubleshooting

22

To troubleshoot problems with NetBackup

1 Ensure that your servers and clients are running supported operating systemversions and that any peripherals you use are supported. See the NetBackuprelease notes and the NetBackup device compatibility lists on www.veritas.comfor this information.

2 Use the All Log Entries report and check for NetBackup errors for theappropriate time period. This report can show the context in which the erroroccurred. Often it provides specific information, which is useful when thestatus code can result from a variety of problems.

If the problem involved a backup or archive, check the Backup Status report.This report gives you the status code.

If you find a status code or message in either of these reports, perform therecommended corrective actions.

See “About NetBackup status codes and messages” on page 155.

See “About media and device management status codes and messages”on page 423.

3 Check the system log on UNIX or the Event Viewer Application and Systemlog on Windows if the following is true: the problem pertains to media ordevice management and one of the following is true:

■ NetBackup does not provide a status code.

■ You cannot correct the problem by following the instructions in NetBackupstatus codes and messages.

■ You cannot correct the problem by following the instructions in mediaand device management status codes and messages.

These logs can show the context in which the error occurred. The errormessages are usually descriptive enough to point you to a problem area.

4 Read the applicable enabled debug logs and correct any problems you detect.If these logs are not enabled, enable them before you retry the failed operation.

See “About using logs and reports” on page 81.

5 If you performed corrective actions, retry the operation. If you did not performcorrective actions or the problem persists, continue with the next step.

6 If you see the problem during a new installation, during an upgradeinstallation, or after you make changes to an existing configuration, see thefollowing:

See “Troubleshooting installation and configuration problems” on page 27.

23Troubleshooting proceduresPreliminary troubleshooting

7 Ensure that the server and client are operational. If you experienced a serveror a client disk crash, procedures are available on how to recover the filesthat are critical to NetBackup operation.

See “About disaster recovery” on page 571.

Verify that you have enough space available in the disk partitions thatNetBackup uses. If one or more of these partitions is full, NetBackup processesthat access the full partition fail. The resulting error message depends on theprocess. Possible error messages: "unable to access" or "unable to create oropen a file."

On UNIX systems, use the df command to view disk partition information.On Windows systems, use Disk Manager or Explorer.

Check the following disk partitions:

■ The partition where NetBackup software is installed.

■ On the NetBackup master or media server, the partition where theNetBackup databases reside.

■ The partition where the NetBackup processes write temporary files.

■ The partition where NetBackup logs are stored.

■ The partition where the operating system is installed.

8 Enable verbose logging either for everything or only for areas you think arerelated to the problem.

See “About using logs and reports” on page 81.

9 Determine which daemons or processes are running. Follow the proceduresfor UNIX or Windows NetBackup servers.

To troubleshoot problems on UNIX NetBackup servers

1 Run the following:

/usr/openv/netbackup/bin/bpps -a

2 If the master server is also the EMM server, ensure that the nbemm and thenbrb services are running. If these services are not running, start them byentering the following:

/usr/openv/netbackup/bin/nbemm

/usr/openv/netbackup/bin/nbrb

If both nbemm and nbrb are not running, they must be started in this sequence.If only one is not running, start it by using the appropriate command.

Troubleshooting proceduresPreliminary troubleshooting

24

3 The nbpem and the nbjm services must be running on the master server. Ifthese services are not running, start them by entering the following:

/usr/openv/netbackup/bin/nbjm

/usr/openv/netbackup/bin/nbpem

If both nbjm and nbpem are not running, they must be started in this sequence.If only one is not running, start it by using the appropriate command.

4 If either the NetBackup request daemon (bprd) or database manager daemon(bpdbm) is not running, run this command to start them:

/usr/openv/netbackup/bin/initbprd

5 If any of the following media and device management processes are notrunning:

■ ltid (ltid only needs to be running if drives are configured on the server)

■ vmd (volume)

■ avrd (automatic volume recognition), only if drives are configured on theserver

■ Processes for all configured robots

6 Stop the device daemon, ltid, by running:

/usr/openv/volmgr/bin/stopltid

7 To verify that the ltid, avrd, and robotic control daemons are stopped, run:

/usr/openv/volmgr/bin/vmps

If you use ACS robotic control, the acsssi and the acssel processes continueto run when ltid is stopped. For more information about how to stop thesedaemons, refer to the following:

See the Automated Cartridge System (ACS) chapter in the NetBackup DeviceConfiguration Guide.

8 Stop any robot control daemons that continue to run when ltid is terminated.Then, start all daemons by running:

/usr/openv/volmgr/bin/ltid

For debugging, start ltid with the -v (verbose) option.

25Troubleshooting proceduresPreliminary troubleshooting

To troubleshoot problems on Windows NetBackup servers

1 The following services must be running. If these services are not running,start them by using the NetBackup Activity Monitor or the Services applicationin the Windows Control Panel:

To start all of them, run install_path\NetBackup\bin\bpup.exe.

The following services must be running on NetBackup master servers:

■ NetBackup Request Manager service

■ NetBackup Policy Execution Manager service

■ NetBackup Job Manager service

■ NetBackup Database Manager service

■ NetBackup Device Manager service (if the system has configured devices)

■ NetBackup Volume Manager service

■ NetBackup Client service

If the master server is also the EMM server, the following services must berunning:

■ NetBackup Enterprise Media Manager service

■ NetBackup Resource Broker service

The following services must be running on NetBackup media servers:

■ NetBackup Device Manager service (if the system has configured devices)

■ NetBackup Volume Manager service

■ NetBackup Client service

The following service must be running on NetBackup clients (includingNetBackup Remote Administration Consoles):

■ NetBackup Client service

2 Use the NetBackup Activity Monitor to see if the following processes arerunning:

■ avrd (automatic media recognition), only if drives are configured on theserver

■ Processes for all configured robots.See the NetBackup Administrator’s Guide for Windows, Volume I.

Troubleshooting proceduresPreliminary troubleshooting

26

If these processes are not running, stop and restart the NetBackup DeviceManager service. Use the NetBackup Activity Monitor or the Servicesapplication in the Windows Control Panel.

3 If you had to start any of the processes or services in the previous steps, retrythe operation.

If they are running or the problem persists, refer to the following procedure:

See “General test and troubleshooting procedures” on page 33.

If you cannot start any of these processes or services, check the appropriatedebug logs for NetBackup problems.

See “About using logs and reports” on page 81.

When these processes and services start, they continue to run unless youstop them manually or a problem occurs on the system. On Windows systems,we recommend that you add commands for starting them to your startupscripts, so they restart in case you have to reboot.

Troubleshooting installation and configurationproblems

Use this procedure to resolve installation and common configuration issues.

Resolving installation problemsBefore you install or use NetBackup on a Linux client, verify that the inetd (orxinetd) service is started on that machine. This service ensures propercommunication between the NetBackup master and the Linux client.

To resolve installation and configuration issues, ask the following questions:

■ Can you install the software on the master and the media servers by using therelease media?

Some reasons for failure can be as follows:

■ Not logged on as an administrator on a Windows system (you must havepermission to install services on the system)

■ Permission denied (ensure that you have permission to use the device andto write the directories and files being installed)

■ Bad media (contact customer support)

■ Defective drive (replace the drive or refer to vendor’s hardwaredocumentation)

27Troubleshooting proceduresTroubleshooting installation and configuration problems

■ Improperly configured drive (refer to the system and the vendordocumentation)

■ Can you install NetBackup client software on the clients?

Note: You cannot install PC client software from a UNIX NetBackup server.

Do the following:

■ For an install to a trusting UNIX client, verify the following: The correctclient name is in your policy configuration and the correct server name isin the client /.rhosts file.

If the install hangs, check for problems with the shell or the environmentvariables for the root user on the client. The files to check depend on theplatform, operating system, and shell you use. For example, your .loginon a Sun system runs an stty (such as stty ^erase) before it defines yourterminal type. If this action causes the install process to hang, you canmodify the .login file to define the terminal before you run the stty. Or,move the client .login to another file until the install is complete.

■ For an install to a secure UNIX client, check your ftp configuration. Forexample, you must use a user name and password that the client considersvalid.

■ Is the problem related to general network communications?See “Resolving network communication problems” on page 40.

Resolving common configuration problemsIf this installation is an initial installation or if you changed the configuration,check for these problems before proceeding:

To resolve configuration issues, check for these problems

1 Check for the following device configuration problems:

■ Configuration for robotic drive does not specify the robot.

■ Drive is configured as wrong type or density.

■ Incorrect Robotic Drive Number.

■ SCSI ID for the robotic control is specified instead of the logical RobotNumber that is assigned to the robot.

■ The same robot number is used for different robots.

■ SCSI ID for the drive is specified instead of a unique Drive Index number.

Troubleshooting proceduresTroubleshooting installation and configuration problems

28

■ A platform does not support a device or was not configured to recognizeit.

■ Robotic device is not configured to use LUN 1, which some robot hardwarerequires.

■ On UNIX, drive no-rewind device path is specified as a rewind path.

■ On UNIX, tape devices are not configured with "Berkeley style close." Thisfeature is configurable on some platforms. NetBackup requires it. See theNetBackup Device Configuration Guide for more information.

■ On UNIX, tape devices (other than QIC) are not configured as "variablemode." This feature is configurable on some platforms. NetBackup requiresit. When this condition exists, you can frequently perform backups butnot restores. Further explanation is available.See “NetBackup status code: 174” on page 257.Also see the NetBackup Device Configuration Guide.

■ On UNIX, pass-through paths to the tape drives have not been established.Also see the NetBackup Device Configuration Guide.

2 Check for the following problems with the daemons or services:

■ Daemons or services do not start during reboot (configure system so theystart).

■ Wrong daemons or services are started (problems with media server startup scripts).

■ Configuration was changed while daemons or services were running.

■ On Windows, the %SystemRoot%\System32\drivers\etc\services filedoes not have an entry for vmd, bprd, bpdbm, and bpcd. Also, ensure thatthe processes have entries for configured robots. A list of these processesis available.See the NetBackup Administrator’s Guide, Volume I.

■ On UNIX, the /etc/services file (or NIS or DNS) does not have an entryfor vmd, bprd, bpdbm, or robotic daemons.

3 If you found and corrected any configuration problems, retry the operationand check for NetBackup status codes or messages in the following:

■ Check the All Log Entries report for NetBackup errors for the appropriatetime period. This report can show the context in which the error occurred.Often it provides specific information, which is useful when the error canresult from a variety of problems.If the problem involved a backup or archive, check the Backup Statusreport. This report gives you the status code.

29Troubleshooting proceduresTroubleshooting installation and configuration problems

If you find a status code or message in either of these reports, performthe recommended corrective actions.See “About NetBackup status codes and messages” on page 155.See “About media and device management status codes and messages”on page 423.

■ Check the system log on UNIX or the Event Viewer Application and Systemlog on Windows if the problem pertains to media or device management.One of the following is true:

■ NetBackup does not provide a status code

■ You cannot correct the problem by following the instructions in thestatus codes chapters

■ Check the appropriate enabled debug logs. Correct any problems youdetect.If these logs are not enabled, enable them before your next try.See “About using logs and reports” on page 81.

4 If you performed corrective actions, retry the operation. If you did not performcorrective actions or the problem persists, go to the next section.

See “General test and troubleshooting procedures” on page 33.

Resolving device configuration problemsAn auto-configuration warning message appears in the second panel of the DeviceConfiguration Wizard if the selected device meets any of the following conditions:

■ Not licensed for NetBackup server

■ Exceeds a license restriction

■ Has some inherent qualities that make it difficult to auto-configure

The following messages relate to device configuration, along with theirexplanations and recommended actions:

Message: Drive does not support serialization

Explanation: The drive does not return its serial number. Note that somemanufacturers do not support serial numbers. Although automatic deviceconfiguration does not function optimally, the drive can be manually configuredand operated without its serial number.

Recommended action: Ask the manufacturer for a newer firmware version thatreturns serial numbers (if available), or manually configure and operate the drivewithout a serial number.

Message: Robot does not support serialization

Troubleshooting proceduresTroubleshooting installation and configuration problems

30

Explanation: The robot does not return its serial number or the serial numbersof the drives that are contained within it. Note that some manufacturers do notsupport serial numbers. Although automatic device configuration does not functionoptimally, the robot and drives can be manually configured and operated withoutserial numbers.

Recommended action: Ask the manufacturer for a newer firmware version thatreturns serial numbers (if available). Or manually configure and operate the robotand drives without serial numbers.

Message: Too many drives in robot

Explanation: The robotic library has more than two installed drives—the maximumthat is allowed with a NetBackup server license.

Recommended action: Remove all but two drives.

Message: Too many slots in robot

Explanation: The robotic library has more than 30 installed slots—the maximumthat is allowed with a NetBackup server license.

Recommended action: If possible, configure the robotic library to have 30 orfewer slots. Only use the robotic libraries that are supported with NetBackupserver .

Message: No license for this robot type

Explanation: NetBackup server does not support the robotic type that is definedfor this robot.

Recommendedaction: Define a different robot. Only use the robotic libraries thatNetBackup server supports.

Message: No license for this drive type

Explanation: The drive type that is defined for this drive that the NetBackupserver does not support.

Recommendedaction: Define a different drive. Only use the drives that NetBackupsupports.

Message: Unable to determine robot type

Explanation: NetBackup does not recognize the robotic library. The robotic librarycannot be auto-configured.

Recommended action:

■ Download a new device_mapping file from the Veritas support Web site, andtry again.

■ Configure the robotic library manually.

31Troubleshooting proceduresTroubleshooting installation and configuration problems

■ Use only the robotic libraries that NetBackup supports.

Message: Drive is stand-alone or in unknown robot

Explanation: Either the drive is stand-alone, or the drive or robot does not returna serial number. Note that some manufacturers do not support serial numbers.Although automatic device configuration does not function optimally, the driveor robot can be manually configured and operated without a serial number.

Recommended action: Ask the manufacturer for a newer firmware version thatreturns serial numbers (if available), or manually configure and operate the driverobot without serial numbers.

Message: Robot drive number is unknown

Explanation: Either the drive or robot does not return a serial number. Note thatsome manufacturers do not support serial numbers. Although automatic deviceconfiguration does not function optimally, the drive or robot can be manuallyconfigured and operated without a serial number.

Recommended action: Ask the manufacturer for a newer firmware version thatreturns serial numbers (if available). Or manually configure and operate the driveand robot without serial numbers.

Message: Drive exceeds drive limit

Explanation: The NetBackup server license allows a maximum of two drives andtwo drives have already been configured.

Recommended action: To use this drive, a previously configured drive must bedisabled (deleted from the device configuration).

Message: Robot exceeds robot limit

Explanation: A robotic library has already been configured.

Recommended action: To use this robot, a previously configured robot must bedisabled (deleted from the device configuration).

Message: Drive is in an unlicensed robot

Explanation: The drive is in a robotic library that cannot be licensed for NetBackupserver . Since the robot cannot be licensed for NetBackup server , any drives thatwere configured in that robot are unusable.

Recommended action: Configure a drive that does not reside in the unlicensedrobot.

Message: Drive's SCSI adapter does not support pass-thru (or pass-thru path doesnot exist)

Explanation: A drive was found that does not have a SCSI pass-through pathconfigured. Two possible causes for this message are as follows:

Troubleshooting proceduresTroubleshooting installation and configuration problems

32

■ The drive is connected to an adapter that does not support SCSI pass-through.

■ The pass-through path for this drive has not been defined.

Recommendedaction: Change the drive’s adapter or define a pass-through pathfor the drive. SCSI adapter pass-through information is available.

See the NetBackup Device Configuration Guide.

Message: No configuration device file exists

Explanation: A device has been detected without the corresponding device filenecessary to configure that device.

Recommendedaction: Refer to the chapter for your system type in theNetBackupDevice Configuration Guide for information on how to create device files.

Message: Unable to determine drive type

Explanation: The NetBackup server does not recognize the drive. The drive cannotbe auto-configured.

Recommended action:

■ Download a new device_mapping file from the Veritas support Web site, andtry again.

■ Configure the drive manually.

■ Use only the drives that NetBackup supports.

Message: Unable to determine compression device file

Explanation: A drive was detected without the expected compression device fileused to configure that device. Automatic device configuration tries to use a devicefile that supports hardware data compression. When multiple compression devicefiles exist for a drive, automatic device configuration cannot determine whichcompression device file is best. It uses a non-compression device file instead.

Recommended action: If you do not need hardware data compression, no actionis necessary. The drive can be operated without hardware data compression.Hardware data compression and tape drive configuration help are available.

Refer to the chapter for your system type in the NetBackup Device ConfigurationGuide.

General test and troubleshooting proceduresIf the Preliminary troubleshooting or Troubleshooting installation andconfiguration problems procedures do not reveal the problem, perform thefollowing procedures. Skip those steps that you have already performed.

33Troubleshooting proceduresGeneral test and troubleshooting procedures

The procedures assume that the software was successfully installed, but notnecessarily configured correctly. If NetBackup never worked properly, you probablyhave configuration problems.

Repeat the checks that are mentioned in the Troubleshooting installation andconfiguration problems procedure when you encounter errors.

In particular, look for device configuration problems.

You may also want to perform each backup and restore twice. On UNIX, performthem first as a root user and then as a nonroot user. On Windows, perform themfirst as a user that is a member of the Administrators group. Then perform themas a user that is not a member of the Administrator group. In all cases, ensurethat you have read and write permissions on the test files.

The explanations in these procedures assume that you are familiar with thefunctional overview information.

See “About backup and restore functional overview” on page 633.

Testing the master server and clientsThis procedure tests the master server and clients.

To test the master server and clients

1 Enable appropriate debug logs on the master server.

See “About using logs and reports” on page 81.

If you do not know which logs apply, enable them all until you solve theproblem. Delete the debug log directories when you have resolved the problem.

2 Configure a test policy (set backup window to be open while you test). Namethe master server as the client and a storage unit that is on the master server(preferably a nonrobotic drive). Also, configure a volume in the NetBackupvolume pool and insert the volume in the drive. If you don’t label the volumeby using thebplabel command, NetBackup automatically assigns a previouslyunused media ID.

3 To verify that the NetBackup daemons or services are running on the masterserver, do the following:

■ To check the daemons on a UNIX system, execute:

/usr/openv/netbackup/bin/bpps -a

■ To check the services on a Windows system, use the NetBackup ActivityMonitor or the Services application in the Windows Control Panel.

Troubleshooting proceduresGeneral test and troubleshooting procedures

34

4 Start a manual backup of a policy by using the manual backup option in theNetBackup administration interface. Then, restore the backup.

These actions verify the following:

■ NetBackup server software is functional, which includes all daemons orservices, programs, and databases.

■ NetBackup can mount the media and use the drive you configured.

If a failure occurs, first check the NetBackup All Log Entries report. For thefailures that relate to drives or media, verify that the drive is in an UP stateand that the hardware functions.

To isolate the problem further, use the debug logs.

A functional overview sequence of events is available.

See “About backup and restore functional overview” on page 633.

If the debug logs do not reveal the problem, check the following:

■ Systems Logs or Event Viewer System logs

■ Event Viewer Application and System logs on Windows systems

■ vmd debug logs on the EMM database host for the device

■ bptm debug logs

See the vendor manuals for information on hardware failures.

If you use a robot and the configuration is an initial configuration, verify thatthe robotic drive is configured correctly.

In particular, verify the following:

■ The same robot number is used both in the Media and Device Managementand storage unit configurations.

■ Each robot has a unique robot number.

On a UNIX NetBackup server, you can verify only the Media and DeviceManagement part of the configuration. To verify, you use the tpreq commandto request a media mount. Verify that the mount completes and check thedrive on which the media was mounted. Repeat the process until the mediais mounted and unmounted on each drive from the host where the problemoccurred. If this works, the problem is probably with the policy or the storageunit configuration. When you are done, tpunmount the media.

35Troubleshooting proceduresGeneral test and troubleshooting procedures

5 If you previously configured a nonrobotic drive and your system includes arobot, change your test policy now to specify a robot. Add a volume to therobot. The volume must be in the NetBackup volume pool on the EMMdatabase host for the robot.

Start with step 3 to repeat this procedure for the robot. This procedure verifiesthat NetBackup can find the volume, mount it, and use the robotic drive.

If you have difficulties with the robot, try the test utilities.

See “About robotic test utilities” on page 709.

Do not use the Robotic Test Utilities when backups or restores are active.These utilities prevent the corresponding robotic processes from performingrobotic actions, such as loading and unloading media. The result is that it cancause media mount timeouts and prevent other robotic operations like roboticinventory and inject or eject from working.

6 Add a user schedule to your test policy (the backup window must be openwhile you test). Use a storage unit and media that was verified in previoussteps.

7 Start a user backup and restore of a file by using the client-user interface onthe master server. Monitor the status and the progress log for the operation.If successful, this operation verifies that the client software is functional onthe master server.

If a failure occurs, check the NetBackup All Log Entries report. To isolate theproblem further, check the appropriate debug logs from the following list.

Explanations about which logs apply to specific client software are available.

See “About using logs and reports” on page 81.

These logs exist only if you enabled debug logging in step 1. On a UNIX system,the debug logs are in the /usr/openv/netbackup/logs/ directory. On aWindows system, the debug logs are in the install_path\NetBackup\logs\directory.

Debug log directories exist for the following processes:

■ bparchive (UNIX only)

■ bpbackup (UNIX only)

■ bpbkar

■ bpcd

■ bplist

■ bprd

Troubleshooting proceduresGeneral test and troubleshooting procedures

36

■ bprestore

■ nbwin (Windows only)

■ bpinetd (Windows only)

8 Reconfigure your test policy to name a client that is located elsewhere in thenetwork. Use a storage unit and media that has been verified in previoussteps. If necessary, install the NetBackup client software.

9 Create debug log directories for the following processes:

■ bprd on the server

■ bpcd on the client

■ bpbkar on the client

■ nbwin on the client (Windows only)

■ bpbackup on the client (except Windows clients)

■ bpinetd (Windows only)

Explanations about which logs apply to specific client types are available.

See “About using logs and reports” on page 81.

10 Perform a user backup and then a restore from the client that is specified instep 8.

These actions verify the following:

■ Communications between the client and the master server

■ NetBackup software on the client

If an error occurs, check the following:

■ All Log Entries report

■ The debug logs that you created in the previous step

A likely cause for errors is a communications problem between the serverand the client.

11 When the test policy operates satisfactorily, repeat specific steps as necessaryto verify other clients and storage units.

12 When all clients and storage units are functional, test the remaining policiesand schedules that use storage units on the master server. If a scheduledbackup fails, check the All Log Entries report for errors. Then follow thesuggested actions in the status codes chapters.

37Troubleshooting proceduresGeneral test and troubleshooting procedures

Testing media server and clientsIf you use media servers, verify their operation as explained in the following steps.Before proceeding, eliminate all problems on the master server.

See “Testing the master server and clients” on page 34.

To test the media server and clients

1 Enable appropriate legacy debug logs on the servers

See “About using logs and reports” on page 81.

If you are uncertain which logs apply, enable them all until you solve theproblem. Delete the legacy debug log directories when you have resolved theproblem.

2 Configure a test policy with a user schedule (set the backup window to beopen while you test) by doing the following:

■ Name the media server as the client and a storage unit that is on the mediaserver (preferably a nonrobotic drive).

■ Add a volume on the EMM database host for the devices in the storageunit. Ensure that the volume is in the NetBackup volume pool.

■ Insert the volume in the drive. If you do not pre-label the volume by usingthe bplabel command, NetBackup automatically assigns a previouslyunused media ID.

3 Verify the following: all NetBackup daemons or services are running on themaster server and Media and Device Management daemons or services arerunning on the media server.

Do one of the following:

■ To perform this check on a UNIX system, run:

/usr/openv/netbackup/bin/bpps -a

■ To perform this check on a Windows system, use the Services applicationin the Windows Control Panel.

4 Perform a user backup and then a restore of a file. Perform these operationsfrom a client that has been verified to work with the master server.

This test verifies the following:

■ NetBackup media server software

■ NetBackup on the media server can mount the media and use the drivethat you configured

Troubleshooting proceduresGeneral test and troubleshooting procedures

38

■ Communications between the master server processes nbpem, nbjm, nbrb,EMM server process nbemm, and media server processes bpcd and bpbrm

■ Communications between media server processbpbrm and client processesbpcd and bpbkar

For the failures that relate to drives or media, ensure that the drive is in anUP state and the hardware functions.

If you suspect a communications problem between the master and the mediaservers, check the debug logs for the involved processes.

If the debug logs don’t help you, check the following:

■ On a UNIX server, the System log

■ On a Windows server, the Event Viewer Application and System log

■ vmd debug logs

See the vendor manuals for information on hardware failures.

If you use a robot and the configuration is an initial configuration, verify thatthe robotic drive is configured correctly.

In particular, verify the following:

■ The same robot number is used both in the Media and Device Managementand storage unit configurations.

■ Each robot has a unique robot number.

On a UNIX server, you can verify only the Media and Device Managementpart of the configuration. To verify, use the tpreq command to request amedia mount. Verify that the mount completes and check the drive on whichthe media was mounted. Repeat the process until the media is mounted andunmounted on each drive from the host where the problem occurred. Performthese steps from the media server. If this works, the problem is probably withthe policy or the storage unit configuration on the media server. When youare done, use tpunmount to unmount the media.

5 If you previously configured a nonrobotic drive and a robot was attached toyour media server, change the test policy to name the robot. Also, add avolume for the robot to the EMM server. Verify that the volume is in theNetBackup volume pool and in the robot.

Start with step 3 to repeat this procedure for a robot. This procedure verifiesthat NetBackup can find the volume, mount it, and use the robotic drive.

If a failure occurs, check the NetBackup All Log Entries report. Look for anyerrors that relate to devices or media.

If the All Log Entries report doesn’t help, check the following:

39Troubleshooting proceduresGeneral test and troubleshooting procedures

■ On a UNIX server, the system logs on the media server

■ vmd debug logs on the EMM server for the robot

■ On a Windows system, the Event Viewer Application and System log

In an initial configuration, verify that the robotic drive is configured correctly.Do not use a robot number that is already configured on another server.

Try the test utilities.

See “About robotic test utilities” on page 709.

Do not use the Robotic Test Utilities when backups or restores are active.These utilities prevent the corresponding robotic processes from performingrobotic actions, such as loading and unloading media. The result is that it cancause media mount timeouts and prevent other robotic operations like roboticinventory and inject or eject from working.

6 When the test policy operates satisfactorily, repeat specific steps as necessaryto verify other clients and storage units.

7 When all clients and storage units are in operation, test the remaining policiesand schedules that use storage units on the media server. If a scheduledbackup fails, check the All Log Entries report for errors. Then follow thesuggested actions in the status codes chapters.

Resolving network communication problemsThe following procedure is for resolving NetBackup communications problems,such as those associated with NetBackup status codes 54, 57, and 58. Thisprocedure consists of two variations: one for UNIX clients and another for PCclients.

Note: In all cases, ensure that your network configuration works correctly outsideof NetBackup before trying to resolve NetBackup problems.

UNIX clientsFor UNIX clients, perform the following steps. Before you start this procedure,add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. Also, createa bpcd debug log directory on your server and clients and a bprd log directory onthe server. During subsequent retries, the debug logs provide detailed debuginformation, which can help you analyze the problem.

To resolve network communication problems with UNIX clients

1 If this configuration is a new or a modified configuration, check the following:

Troubleshooting proceduresGeneral test and troubleshooting procedures

40

■ Check any recent modifications to ensure that they did not introduce theproblem.

■ Ensure that the client software was installed.

■ Ensure that the client operating system is one of those supported by theclient software.

■ Check the client names, server names, and service entries in yourNetBackup configuration as explained in the following topic:See “Verifying host name and service entries” on page 49.

Two other checks that you can make on host names are as follows:

■ Use the hostname command on the client to determine the host namethat the client sends with requests to the server.

■ Check the bprd debug log (verbose) on the server to determine whatoccurred when the server received the request.

41Troubleshooting proceduresGeneral test and troubleshooting procedures

■ Pay special attention to NIS or the DNS updates that are required. Failureto update these services properly is a common source of network problemswith NetBackup.

2 Verify network connectivity between client and server by trying to ping theclient from the server.

ping clientname

Where clientname is the name of the client as configured in the NetBackuppolicy configuration, /etc/hosts, and also in NIS and DNS (if applicable).

For example, to ping a client that is named ant:

ping ant

ant.nul.nul.com: 64 byte packets

64 bytes from 199.199.199.24: icmp_seq=0. time=1. ms

----ant.nul.nul.com PING Statistics----

2 packets transmitted, 2 packets received, 0% packet loss

round-trip (ms) min/avg/max = 1/1/1

Also, try ping from the client to the server.

If ping succeeds in both instances, it verifies connectivity between the serverand client. If ping fails, you have a network problem outside of NetBackupthat must be resolved before you proceed.

Note that some forms of the ping command let you ping the bpcd port on theclient as in:

ping ant 13782

or

ping ant bpcd

3 Check that the client listens on the correct port for bpcd connections byrunning one of the following commands (depending on platform and operatingsystem).

netstat -a | grep bpcd

netstat -a | grep 13782 (or the value that is specified during the install)

rpcinfo -p | grep 13782 (or the value that is specified during the install)

For example, assume that the client is a Solaris system and you run:

netstat -a | grep 13782

Troubleshooting proceduresGeneral test and troubleshooting procedures

42

If there is no problem with the port, the results are similar to:

tcp 0 0 *.13782 *.* LISTEN

The LISTEN indicates that the client listens for connections on this port.

If there is a problem, this line does not appear and one of the following threeconditions exists:

■ /etc/services (or applicable NIS file) does not have the correct bpcdentry. The correct /etc services entry is:

bpcd 13782/tcp bpcd

■ /etc/inetd.conf (or applicable NIS or DNS file) does not have the correctbpcd entry. The correct /etc/inetd.conf entry is:

bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

■ /etc/inetd.confwas changed but was not re-read. Correct this conditionby running one of the following (whichever works):

/bin/ps -ef | grep inetd

kill -HUP the_inetd_pid

Or

/bin/ps -aux | grep inetd

kill -HUP the_inetd_pid

On a Hewlett-Packard platform, use inetd -c to send a SIGHUP to inetd.

If the problem is with an AIX client, do the following: use SMIT to verify thatthe InetServ object policy was updated with information about the bpcd

process (/etc/inetd.conf and /etc/services information).

If you modify the InetServ object policy by using SMIT, the inetexp commandautomatically runs. If you edit the InetServ object policy by using an ODMeditor, do the following: run the inetexp command to export the InetServobject policy to the/etc/inetd.conf and/etc/services files. This commandkeeps these files in sync with the InetServ object policy.

If you change the /etc/inetd.conf or /etc/services file by using SMIT, theinetimp command automatically updates the InetServ object policy. If youchange either file, run the following command to inform the inetd daemonof the changes to its configuration file: refresh -s inetd or kill -1

InetdPID

43Troubleshooting proceduresGeneral test and troubleshooting procedures

4 telnet to bpcd on the client. If it succeeds, keep the connection until afteryou perform step 5, then terminate it with Ctrl-c.

telnet clientname 13782

Where clientname is the name of the client as configured in the NetBackuppolicy configuration, /etc/hosts, and also in NIS and DNS (if applicable).

For example,

telnet ant bpcd

Trying 199.999.999.24 ...

Connected to ant.nul.nul.com.

Escape character is ‘^]’.

In this example, telnet can establish a connection to the client ant.

■ If the telnet succeeds, then inetd on the client is configured correctly.It can pass its connection to bpcd and NetBackup should also be able toestablish a connection.

■ Iftelnetdoesn’t work, ensure that theinetd.conf file and/etc/servicesfiles on both the server and client are correct and match. By default, theseare as follows:In /etc/services:

bpcd 13782/tcp bpcd

In /etc/inetd.conf:

bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

Then, run kill -HUP to reread the /etc/inetd.conf file as explained instep 3.Also, update the applicable NIS or DNS files.If these files are correct and you cannot connect to the client, you mayhave network routing problems or a problem with the port assignment.(See the next step.)

5 Check that the client listens on the correct port for the telnet connection tobpcd. To check, run one of the following commands (depending on platformand operating system).

netstat -a | grep bpcd

netstat -a | grep 13782 (or the value that is specified during install)

rpcinfo -p | grep 13782 (or the value that is specified during install)

Troubleshooting proceduresGeneral test and troubleshooting procedures

44

For example, assume the client in step 4 is a SunOS system that is named ant.The telnet is from a NetBackup server that is named whale:

netstat -a | grep 13782

One of the following conditions occurs:

■ If the port is not the problem, you see the following:

tcp 0 0 ant.nul.nul.com.13782 whale...com.1516 ESTABLISHED

tcp 0 0 *.13782 *.* LISTEN

In the first line of the result, ESTABLISHED indicates that the telnet

connection was established to bpcd through port 13782 on the client.

The LISTEN in the second line indicates that the client listens for furtherconnections on this port.We suggest that you not change the port number for bpcd or otherNetBackup services. Do so only if there is no alternative. Then, rememberthat all NetBackup servers and clients in the configuration must use thisnew port assignment.

■ If there is a process other than bpcd that uses the port, try to reboot theclient to clear the problem. If the problem is still not fixed, it may benecessary to change one of the service numbers (preferably for the otherservice). To change a service number, modify the /etc/services filesThen send SIGHUP signals to the inetd processes on your clients.

/bin/ps -ef | grep inetd

kill -HUP the_inetd_pid

Or

/bin/ps -aux | grep inetd

kill -HUP the_inetd_pid

On a Hewlett-Packard platform, use inetd -c to send a SIGHUP to inetd.

Also make applicable NIS or DNS updates.

45Troubleshooting proceduresGeneral test and troubleshooting procedures

If the problem is with an AIX client and you make changes to the/etc/inetd.conf and /etc/services information, do the following: UseSMIT to verify that the InetServ object policy was updated. See step 4.

6 To verify client to master server communications, use the bpclntcmd utility.When -pn and -sv run on a NetBackup client, they initiate inquiries to theNetBackup master server (as configured in the client bp.conf file). The masterserver then returns information to the requesting client. More informationis available about bpclntcmd.

See “Using bpclntcmd” on page 53.

PC clientsThis procedure helps you resolve network communication problems with PCclients.

To resolve network problems

1 Before you retry the failed operation, do the following:

■ Increase the logging level on the client (see the client’s user guide).

■ On the NetBackup server, create a bprd debug log directory and on theclients create a bpcd debug log.

■ On the NetBackup server, set the Verbose level to 1 on theTroubleShooting tab in the NetBackup Client Properties dialog box. Todisplay this dialog box, start the Backup, Archive, and Restore interface.Then click NetBackup Client Properties on the File menu.See “Using the Host Properties window” on page 61.

2 If this client is new, verify the client and the server names in your NetBackupconfiguration.

See “Verifying host name and service entries” on page 49.

3 Verify basic network connectivity between client and server by pinging fromthe server to the client and vice versa. Use the following command:

ping hostname

Where hostname is the name of the host as configured in the following:

■ NetBackup policy configuration

■ WINS

■ DNS (if applicable).

Troubleshooting proceduresGeneral test and troubleshooting procedures

46

■ hosts file in system directory %SystemRoot%\system32\drivers

\etc\hosts (Windows XP or 2003)

If ping succeeds in all instances, it verifies basic connectivity between theserver and client.

If ping fails, you have a network problem outside of NetBackup that must beresolved before you proceed. As a first step, verify that the workstation isturned on. Not being turned on is a common source of connection problemswith PC workstations.

4 On Microsoft Windows or NetWare clients, check the NetBackup Client service.Do one of the following tasks:

■ Ensure that the service is active by checking the logs or by doing one ofthe following:

■ On Windows XP or Windows Server 2003 clients, use the Servicesapplication in the Control Panel to verify that the NetBackup Clientservice is running. Start it if necessary.

■ On NetWare clients, enter modules bpcd.nlm from the NetWare serverconsole to verify that the NetBackup client daemon is running. Ifnecessary, type bpstart.ncf from the NetWare server console to startthe NetBackup client daemon.

■ Check thebpcddebug logs for problems or errors. Instructions are availableon how to enable and use these logs.See “About using logs and reports” on page 81.

■ Verify that the same NetBackup client Service (bpcd) port number isspecified on both the NetBackup client and server (by default, 13782). Doone of the following:

■ On Microsoft Windows, check the NetBackup Client Service Portnumber:Start the Backup, Archive, and Restore interface on the client. On theFile menu, click NetBackupClientProperties. In the NetBackupClientProperties dialog box on the Network tab, check the NetBackup ClientService Port number.Verify that the setting on the Network tab matches the one in theservices file. The services file is located in:

%SystemRoot%\system32\drivers\etc\services (Windows)

The values on the Network tab are written to the services file whenthe NetBackup Client service starts.

47Troubleshooting proceduresGeneral test and troubleshooting procedures

■ On NetWare clients, see the BPCD setting in theSYS:VERITAS\NBUCLT\NetBack\BP.INI file.

■ On UNIX NetBackup servers, the bpcd port number is in the/etc/services file. On Windows NetBackup servers, see the ClientProperties dialog box in the Host Properties window.See “Using the Host Properties window” on page 61.

Correct the port number if necessary. Then, on Windows clients andservers, stop and restart the NetBackup Client service. On NetWare clients,stop and restart the NetBackup client daemon (bpcd).

Do not change NetBackup port assignments unless it is necessary to resolveconflicts with other applications. If you do change them, do so on allNetBackup clients and servers. These numbers must be the samethroughout your NetBackup configuration.

5 Verify that the NetBackup Request Service (bprd) Port number on MicrosoftWindows and NetWare clients is the same as on the server (by default, 13720).

■ On Microsoft Windows clients (use the same method as in step 4).

■ On NetWare clients, see the BPRD setting in theSYS:VERITAS\NBUCLT\NetBack\BP.INI file.

■ Or, instead of the first bullet: On UNIX NetBackup servers, the bprd portnumber is in the /etc/services file. On Windows NetBackup servers, setthese numbers in the Client Properties dialog box in the Host Propertieswindow.See “Using the Host Properties window” on page 61.

6 Verify that the hosts file or its equivalent contains the NetBackup servername. The hosts files are the following:

■ %SystemRoot%\system32\drivers\etc\hosts (Windows XP or 2003)

■ SYS:etc\hosts (NetWare)

■ /etc/hosts (UNIX)

7 Verify client-to-server connectability by using ping or its equivalent fromthe client (step 3 verified the server-to-client connection).

8 If the client’s TCP/IP transport allows telnet and ftp from the server, trythese as additional connectivity checks.

9 For a NetWare client, ensure that the server does not try to connect when abackup or restore is already in progress on the client. If you try more thanone job at a time on these clients, it results in a "can’t connect" or similarerror.

Troubleshooting proceduresGeneral test and troubleshooting procedures

48

10 Use the bpclntcmd utility to verify basic client to master servercommunications. When -pn and -sv run on a client, they initiate inquiriesto the master server (as configured in the server list on the client). The masterserver then returns information to the requesting client.

See “Using bpclntcmd” on page 53.

11 Use the bptestbpcd utility to try to establish a connection from a NetBackupserver to the bpcd daemon on another NetBackup system. If successful, itreports information about the sockets that are established.

See “Using bpclntcmd” on page 53.

12 Verify that the client operating system is one of those supported by the clientsoftware.

Verifying host name and service entriesThis procedure is useful if you encounter problems with host names or networkconnections and want to verify that the NetBackup configuration is correct. Severalexamples follow the procedure.

For more information on host names, see the following:

■ See “Background for troubleshooting” on page 703.

■ The "Rules for using host names in NetBackup" section in the NetBackupAdministrator’s Guide, Volume II

To verify the client and the server host names in NetBackup

1 Verify that the correct client and server host names are configured inNetBackup.

■ On Windows servers, Windows clients, and NetWare nontarget clients,check the following:

■ The General tab in the NetBackup Client Properties dialog box.

■ The Server to use for backups and restores drop-down list in theSpecify NetBackup Machines and Policy Type dialog box.

To display these dialog boxes, start the Backup, Archive, and Restoreinterface on the client. For the General tab, click NetBackup ClientProperties on the File menu. For the Server to use for backups and restoresdrop-down, click Specify NetBackup Machines and Policy Type on theFile menu.

Do the following:

■ On the Server touse forbackupsandrestores drop-down list, ensurethat a server entry exists for the master server and each media server.

49Troubleshooting proceduresGeneral test and troubleshooting procedures

On Windows systems, the correct server must be designated as thecurrent master server in the list. If you add or modify server entrieson the master server, stop and restart the NetBackup Request serviceand NetBackup database manager services.On UNIX systems, if you add or modify SERVER entries on the masterserver, stop and restart bprd and bpdbm.

■ On the General tab, verify that the client name setting is correct andmatches what is in the policy client list on the master server.

■ On a master or a media server, ensure that a server entry exists foreach Windows administrative client to use to administer that server.

■ Ensure that host names are spelled correctly in the bp.conf file (UNIX)or in the servers list (Windows) on the master server. If a host nameis misspelled or cannot be resolved by using gethostbyname, thefollowing error messages are logged on the NetBackup error log:

Gethostbyname failed for

<host_name>:<h_errno_string> (<h_errno>)

One or more servers was excluded from the server

list because gethostby name() failed.

You can also make these changes on the appropriate tabs in the propertiesdialog boxes on a Windows NetBackup serverSee “Using the Host Properties window” on page 61.

■ On UNIX NetBackup servers and clients and Macintosh clients, check theserver and the client name entries in the bp.conf file by doing thefollowing:

■ Ensure that a SERVER entry exists for the master server and each mediaserver in the configuration. The master server must be the first namein the list.If you add or modify SERVER entries on the master server, stop andrestart bprd and bpdbm before the changes take effect.

■ The bp.conf of the master server does not require the addition of otherclients, other than the master server as CLIENT_NAME = master servername. The name is added by default.

Thebp.conf file is in the/usr/openv/netbackupdirectory on UNIX clientsand it is in the Preferences:NetBackup folder on Macintosh clients.

Users on UNIX clients can also have a personal bp.conf file in their homedirectory. A CLIENT_NAME option in $HOME/bp.conf overrides the optionin /usr/openv/netbackup/bp.conf.

Troubleshooting proceduresGeneral test and troubleshooting procedures

50

■ On NetWare clients, check the SYS:VERITAS\NBUCLT\NetBack\BP.INI fileto ensure the following:

■ A SERVER entry exists for the master server and each media server inthe configuration. The master server must be the first name in the list.

■ TheClientName entry and the entries in the [clients] section are correctand match what is in the policy client list on the master server.

■ On the master server, verify that you have created any of the followingrequired files:

■ /usr/openv/netbackup/db/altnames files (UNIX)

■ install_path\NetBackup\db\altnames files (Windows)

Pay particular attention to requirements for host.xlate file entries.

2 Verify that each server and client have the required entries for NetBackupreserved port numbers.

The examples following this procedure show the default port numbers. Donot change NetBackup port assignments unless it is necessary to resolveconflicts with other applications. If you do change them, do so on allNetBackup clients and servers. These numbers must be the same throughoutyour NetBackup configuration.

■ On NetBackup servers, check the services files to ensure that they haveentries for the following:

■ bpcd and bprd

■ vmd

■ bpdbm

■ Processes for configured robots (for example, tl8cd).

See the NetBackup Administrator’s Guide, Volume I for a list of theseprocesses.

On UNIX, the services file is /etc/services. On Windows, the services

file is %SystemRoot%\system32\drivers\etc\services.

■ On UNIX, Windows, and NetWare clients, verify the NetBackup clientdaemon or service number, and the request daemon or service portnumber.

■ On UNIX clients, check the bprd and the bpcd entries in the/etc/services file.

51Troubleshooting proceduresGeneral test and troubleshooting procedures

■ On Microsoft Windows clients, verify that the NetBackup Client ServicePort number and NetBackup Request Service Port number matchsettings in the services file:Start the Backup, Archive, and Restore interface on the client. On theFile menu, click NetBackupClientProperties. In the NetBackupClientProperties dialog box on the Network tab, select the following: TheNetBackup Client Service Port number and NetBackup Request ServicePort number.The values on the Network tab are written to the services file whenthe NetBackup Client service starts.The services file is in the following location:

%SystemRoot%\system32\drivers\etc\services (Windows)

■ On NetWare clients, check the BPCD and the BPRD entries in theSYS:VERITAS\NBUCLT\NetBack\BP.INI file.

3 On UNIX servers and clients, check the /etc/inetd.conf file to ensure thatit has the following entry:

bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

4 On Windows servers and clients, verify that the NetBackup Client service isrunning.

5 If you use NIS in your network, update those services to include the NetBackupinformation that is added to the /etc/services file.

6 NIS, WINS, or DNS host name information must correspond to what is in thepolicy configuration and the name entries in the following:

■ On Windows NetBackup servers, Microsoft Windows clients, and NetWarenontarget clients:

■ Check the General tab:Start the Backup, Archive, and Restore interface on the client. On theFile menu, click NetBackupClientProperties. In the NetBackupClientProperties dialog box, click the General tab.

■ Check the Server to use for backups and restores drop-down list:On the File menu, click SpecifyNetBackupMachinesandPolicyType.In the SpecifyNetBackupMachinesandPolicyTypedialog box, clickthe Server to use for backups and restores drop-down list.

■ The bp.conf file on UNIX servers and clients and Macintosh clients.

■ The \veritas\nbuclt\netback\bp.ini file on NetWare clients.

Troubleshooting proceduresGeneral test and troubleshooting procedures

52

Also, verify that reverse DNS addressing is configured.

7 To confirm the setup of the following, use the NetBackup bpclntcmd utility:the IP addresses and hostnames in DNS, NIS, and (or) local hosts files on eachNetBackup node.

Using bpclntcmdThe bpclntcmd utility resolves IP addresses into host names and host names intoIP addresses. It uses the same system calls as the NetBackup application software.The following directory contains the command that starts the utility:

install_path\NetBackup\bin (Windows)

/usr/openv/netbackup/bin (UNIX)

On Windows, run this command in an MS-DOS command window so you can seethe results.

The Bpclntcmd options that are useful for testing the functionality of the hostname and IP address resolution are -ip, -hn, -sv, and -pn. The following topicsexplain each of these options:

bpclntcmd -ip IP_Address

The -ip option lets you specify an IP address. bpclntcmd uses gethostbyaddr()on the NetBackup node and gethostbyaddr() returns the host name with the IPaddress as defined in the following: the node’s DNS, WINS, NIS, or local hosts fileentries. No connection is established with the NetBackup server.

bpclntcmd -hn Hostname

The -hn option specifies a host name. bpclntcmd uses gethostbyname() on theNetBackup node to obtain the IP address that is associated with the host namedefined in the following: the node’s DNS, WINS, NIS, or local hosts file entries.No connection is established with the NetBackup server.

Use -ip and -hn to verify the ability of a NetBackup node to resolve the IPaddresses and host names of other NetBackup nodes.

For example, to verify that a NetBackup server can connect to a client, do thefollowing:

■ On the NetBackup server, use bpclntcmd -hn to verify the following: Theoperating system can resolve the host name of the NetBackup client (asconfigured in the client list for the policy) to an IP address. The IP address isthen used in the node’s routing tables to route a network message from theNetBackup server.

53Troubleshooting proceduresGeneral test and troubleshooting procedures

■ On the NetBackup client, use bpclntcmd -ip to verify the following: Theoperating system can resolve the IP address of the NetBackup server. (The IPaddress is in the message that arrives at the client’s network interface.)

bpclntcmd -pnWhen the -pn option is run on a NetBackup client, it initiates an inquiry to theNetBackup master server. The server then returns information to the requestingclient. First, the server is the Current Server in the server list). Then it displaysthe information that the server returns.

The following is an example of the use of bpclntcmd:

bpclntcmd -pn

expecting response from server rabbit.friendlyanimals.com

dove.friendlyanimals.com dove 123.145.167.3 57141

The following is true of the preceding command:

■ expecting response from server rabbit.friendlyanimals.com is themaster server entry from the server list on the client.

■ dove.friendlyanimals.com is the connection name (peer name) returned bythe master server. The master server obtained this name throughgethostbyaddress().

■ dove is the client name configured in the NetBackup policy client list.

■ 123.145.167.3 is the IP address of the client connection at the master server.

■ 57141 is the port number of the connection on the client.

bpclntcmd -svThe -sv option displays the NetBackup version number on the master server.

Host name and service entry examples - UNIXThis topic shows five examples of host name and service entries for UNIX systems.

Example 1: UNIX master server and clientThe example in Figure 2-1 shows a UNIX master server with one UNIX client.

Troubleshooting proceduresGeneral test and troubleshooting procedures

54

Figure 2-1 Example 1: UNIX master server and client

jupiter

Ethernet

Policy Client List

jupitermars

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprd

/etc/inetd.conf

bpcd ... (see note 1)

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprdbpdbm 13721/tcp bpdbm

# Volume Manager services #vmd 13701/tcp vmdtl8cd 13705/tcp tl8cd..

UNIXClient

mars

usr/openv/netbackup/bp.conf

SERVER=jupiterCLIENT_NAME=jupiter

usr/openv/netbackup/bp.conf

SERVER=jupiterCLIENT_NAME=mars

/etc/inetd.conf

bpcd ... (see note 1)

Notes:

1. The complete inetd.conf entry is:bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd2. All other applicable network configuration must also be updated to reflect theNetBackup information. For example, this information could include the /etc/hosts fileand NIS, and DNS (if used).

UNIXMaster Server

Example 2: UNIX master server and media serverFigure 2-2 shows a UNIX NetBackup media server named saturn. Note the additionof a SERVER entry for saturn in the bp.conf files on all the systems. This entry issecond, beneath the one for the master server jupiter.

55Troubleshooting proceduresGeneral test and troubleshooting procedures

Figure 2-2 Example 2: UNIX master and media servers

Ethernet

Policy Client List

jupitermarssaturn

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprd

/etc/inetd.conf

bpcd ... (see note 1)

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprdbpdbm 13721/tcp bpdbm

# Volume Manager services #vmd 13701/tcp vmdtl8cd 13705/tcp tl8cdodld 13706/tcp odld..

UNIXClient

mars

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=saturnCLIENT_NAME=jupiter

/etc/inetd.conf

bpcd ... bpcd (see note 1)

Notes:

1. The complete inetd.conf entry is:bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

2. All other applicable network configuration must also be updated to reflect the NetBackupinformation. For example, this information could include the /etc/hosts file and NIS, and DNS (ifused).

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=saturnCLIENT_NAME=mars

/etc/inetd.conf

bpcd ... bpcd (see note 1)

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=saturnCLIENT_NAME=saturn

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprdbpdbm 13721/tcp bpdbm

# Volume Manager services #vmd 13701/tcp vmdtl8cd 13705/tcp tl8cdodld 13706/tcp odld..

UNIXMedia ServerUNIX

Master Serverjupiter saturn

Example 3: UNIX PC clientsFigure 2-3 shows a NetBackup master server with PC clients, defined here asWindows, NetWare, or Macintosh clients. Server configuration is the same as itis for UNIX clients.These clients do not have inetd.conf entries.

Troubleshooting proceduresGeneral test and troubleshooting procedures

56

Figure 2-3 Example 3: UNIX PC clients

Ethernet

Policy Client List

jupitermarssaturnpluto

WindowsClient

NetWare TargetClient

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprdbpdbm 13721/tcp bpdbm

# Volume Manager services #vmd 13701/tcp vmdtl8cd 13705/tcp tl8cdodld 13706/tcp odld..

/etc/inetd.conf

bpcd ... (see note 1)

usr/openv/netbackup/bp.conf

SERVER=jupiterCLIENT_NAME=jupiter

bp.ini

[bp]ClientName=mars

[servers]master=jupiter

[clients]browser=jupiter

[tcpip]bpcd=13782bprd=13720

NetBackup Client Properties dialog box

Server List: jupiter

Servers

General

Client Name: saturn

Network

NetBackup Client Service Port 13782

NetBackup Request Service Port 13720

Notes:

1. The complete inetd.conf entry is:bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

2. All other applicable network configuration must also be updated to reflect the NetBackup information.For example, this information could include the /etc/hosts file and NIS, and DNS (if used).

UNIXMaster Server

mars saturn

jupiter

Example 4: UNIX clients in multiple networksFigure 2-4 shows a client that is a router to clients in another network. The clienthost name on the master server side is mars and the host name that is presentedto the client pluto is meteor.

57Troubleshooting proceduresGeneral test and troubleshooting procedures

Figure 2-4 Example 4: UNIX clients in multiple networks

UNIXMaster Server

jupiter

Ethernet

Policy Client List

jupitermarssaturnpluto

UNIXClient

mars

saturn

meteor

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprdbpdbm 13721/tcp bpdbm

# Volume Manager services #vmd 13701/tcp vmdtl8cd 13705/tcp tl8cdodld 13706/tcp odld..

/etc/inetd.conf

bpcd ... bpcd (see note 1)

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=saturnCLIENT_NAME=jupiter

UNIXClient

pluto

Ethernet

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=saturnCLIENT_NAME=mars

/etc/inetd.conf

bpcd ... bpcd (see note 1)

/etc/services

# NetBackup services bpcd13782/tcp bpcdbprd 13720/tcp bprd

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=saturnCLIENT_NAME=pluto

/etc/inetd.conf

bpcd ... bpcd (see note 1)

Notes:

1. The complete inetd.conf entry is:bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd2. All other applicable network configuration must also be updated to reflect the NetBackup information.For example, this information could include the /etc/hosts file and NIS, and DNS (if used).

/etc/services

# NetBackup services bpcd13782/tcp bpcdbprd 13720/tcp bprd

UNIXMedia Server

In example 4, we first examine the configuration of the router system. TheNetBackup policy client list shows this system as mars because that is the nameof the interface to the master server. Other than the client name setting, thissetup has no special configuration to note. This name must be set to mars, becausemars is the name that the master server recognizes.

Troubleshooting proceduresGeneral test and troubleshooting procedures

58

The second client, pluto, is also configured no differently than if it were in thesame network as the master server. If all the standard networking files (hosts,NIS, DNS, WINS, and routing tables) are set up correctly, all the required networkconnections can be made.

However, to restore files from pluto would be a problem in the following situation:the mars, meteor system is a type of router that hides the name of the originatinghost when it routes requests between the two networks. For example, a routerbetween an Ethernet and a token ring network exhibits this behavior.

To illustrate what occurs, assume that pluto is on FDDI (token ring) and the serveris on Ethernet. Then a user on pluto starts a restore. The router can use the nameof its network interface to pluto (meteor) as the peer name when it forwards therequest to the server. The server interprets the request as coming from a hostthat is named meteor. It does not allow the restore because meteor is not in theclient list.

To resolve this problem, the administrator creates an altnames directory on themaster server and adds a file for meteor to that directory.

On a Windows NetBackup server, the file path is:

install_path\netbackup\db\altnames\meteor

On a UNIX NetBackup server, the file path is:

/usr/openv/netbackup/db/altnames/meteor

Then, the administrator adds the following line to this file:

pluto

The master server now recognizes as legitimate any of the restore requests witha peer name of meteor and client name of pluto.

Refer to the NetBackup Administrator’s Guide, Volume I, for more informationon altnames configuration.

Regardless of the type of router, the configuration for the media server, saturn,is the same as in example 2. If a media server is involved in a backup or restorefor pluto, the master server provides the following: the correct peer name andclient name for the media server to use to establish connections.

Example 5: UNIX server that connects to multiple networksFigure 2-5 shows an NBU server with two Ethernet connections and clients inboth networks. The server host name is jupiter on one and meteor on the other.

59Troubleshooting proceduresGeneral test and troubleshooting procedures

Figure 2-5 Example 5: UNIX server connects to multiple networks

Policy Client List

jupitermarssaturnpluto

/etc/inetd.conf

bpcd ... bpcd (see note 1)

/etc/inetd.conf

bpcd ... (see note 1)

/etc/services

# NetBackup services bpcd13782/tcp bpcdbprd 13720/tcp bprd

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=meteorSERVER=saturnCLIENT_NAME=mars

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=meteorSERVER=saturnCLIENT_NAME=jupiter

usr/openv/netbackup/bp.conf

SERVER=jupiterSERVER=meteorSERVER=saturnCLIENT_NAME=pluto

/etc/inetd.conf

bpcd ... bpcd (see note 1)

/etc/services

# NetBackup services bpcd13782/tcp bpcdbprd 13720/tcp bprd

/etc/services

# NetBackup servicesbpcd 13782/tcp bpcdbprd 13720/tcp bprdbpdbm 13721/tcp bpdbm

# Volume Manager services #vmd 13701/tcp vmdtl8cd 13705/tcp tl8cdodld 13706/tcp odld..

jupiter

Ethernet

UNIXMaster Server

marsUNIXMedia Serversaturn

meteor

UNIXClient

pluto

Ethernet

UNIXClient

Notes:

1. The complete inetd.conf entry is:bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd2. All other applicable network configuration must also be updated to reflect the NetBackup information. Forexample, this information could include the /etc/hosts file and NIS, and DNS (if used).

Example 5 illustrates a UNIX server that connects to multiple networks.

Troubleshooting proceduresGeneral test and troubleshooting procedures

60

The NetBackup policy client list specifies jupiter as the client name for the masterserver. The list can show either jupiter or meteor but not both.

Another important item to note is the configuration of the NetBackup server list.

The NetBackup server list on the master server has entries for both jupiter andmeteor. The reason for both is that when the server does a backup, it uses thename that is associated with the client it backs up. For example, it uses the meteorinterface when it backs up pluto and the jupiter interface when it backs up mars.The first server entry (master server name) is jupiter because that is the nameused to back up the client on the master server.

The NetBackup server list for the other systems also has entries for both thejupiter and the meteor interfaces. This setup is recommended to keep the serverentries the same on all clients and servers in the configuration. It would beadequate to list only the master-server name for the local network interface tothe client system or media server. (For example, list meteor for pluto.)

For the network that is shown, the only configurations that are required are thedifferences for the policy client list and the server list. If all the standardnetworking files (hosts, WINS, NIS, DNS, and routing tables) are set up correctly,all required network connections can be made.

As in example 4, there would be a problem to restore the files in the followingsituation: the master server system is a router that hides the originating hostname when it routes requests between networks. For example, if pluto were onFDDI (token ring), the master server would use meteor as the peer name when itforwards the request to NetBackup. NetBackup would then interpret the requestas coming from a host that is named meteor, which was not in the client list. Therestore would fail.

The solution, in this case, is also identical to the solution that is discussed in thefollowing:

See Figure 2-4 on page 58.

Using the Host Properties windowThe Host Properties window in the NetBackup Administration Console providesaccess to many configuration settings for NetBackup clients and servers. Forexample, you can modify the server list, email notification settings, and varioustimeout values for servers and clients. The following are general instructions forusing this window.

Many procedures in this guide also refer to the NetBackup Client Propertiesdialog box in the Backup, Archive, and Restore interface on Microsoft Windowsclients. This dialog box lets you change NetBackup configuration settings only

61Troubleshooting proceduresUsing the Host Properties window

for the local system where you are running the interface. Most settings in theNetBackupClientProperties dialog box are also available in the HostPropertieswindow.

For more information, see the online Help or theNetBackupAdministrator’sGuide,Volume I.

To access configuration settings through Host Properties

1 Start the NetBackup Administration Console.

2 Click Host Properties.

3 Select the servers or clients where you want to make the change.

4 On the Actions menu, select Properties.

5 In the properties dialog box, select the appropriate tab and make your change.

Resolving full disk problemsIf the NetBackup installation directory fills up, such as with logging files, a numberof problems can result. NetBackup may become unresponsive. For example,NetBackup jobs may remain queued for long periods, even though all NetBackupprocesses and services are running.

To diagnose and correct a full disk problem

1 The NetBackup Resource Broker (nbrb) log may have database connectionerrors in it. These errors indicate failed tries to establish connections to thenbemm database. The following is an example of such errors in the nbrb log:

7/20/2005 12:33:47.239 [RBDatabase::connectDatabase()] ODBC

connection failed.

ErrMsg: [Sybase][ODBC Driver][Adaptive Server Anywhere]Disk

write failure

'Fatal error: disk write failure C:\Program

Files\VERITAS\NetBackupDB\data\NBDB.log' -- transaction rolled

back ErrCode:

-1Sqlstate: HY000

The nbrb log (originator ID 118) is written in /usr/openv/logs (UNIX) orinstall_path\NetBackup\logs (Windows). More information is availableabout unified logging.

See “About using logs and reports” on page 81.

2 To correct the situation, clear up disk space in the directory where NetBackupis installed by doing the following:

Troubleshooting proceduresResolving full disk problems

62

■ You may need to delete log files manually, reduce logging levels, and adjustlog retention to have log files automatically deleted sooner.More information is available about logging levels, log file retention, andhow to configure unified logging.See “About using logs and reports” on page 81.

■ Consider moving the NetBackup unified logging files to a different filesystem.See “Changing log file locations” on page 85.

3 Use the Activity Monitor to verify that the NetBackup relational databaseservice is running. This service is the NB_dbsrv daemon on UNIX and the"Adaptive Server Anywhere - Veritas_NB" service on Windows.

4 If the NetBackup relational database service is stopped, note the following:

■ Do NOT stop the nbrb service. If you stop the nbrb service while theNetBackup relational database service is down, it can result in errors.

■ Restart the NetBackup relational database service.

Verify that the NetBackup relational database service is running. If it is notand you remove files to free up disk space, you may not fix the problem. Therelational database service must be restarted to allow the Resource Broker(nbrb) to allocate job resources.

Troubleshooting frozen mediaFrozen media can cause a number of problems including one of the followingstatus codes: 84, 85, 86, 87 and 96.

When troubleshooting frozen media, be aware of the following:

■ The media server that freezes the media stores the actual FROZEN status ofthat media in its media database (MediaDB). Every media server including themaster server has its own unique media database.

■ Use the bpmedialist command to access the MediaDB information, includingthe media status (Frozen, Full, or Active).

■ To unfreeze the media, use the bpmedia command. Specify the media serverthat contains that frozen record in the command syntax. Unfreeze the mediaone at a time.

■ Frozen media does not necessarily mean that the media is defective. NetBackupmay freeze media as a safety measure to prevent further errors, drive damage,or data loss.

63Troubleshooting proceduresTroubleshooting frozen media

■ Investigate any patterns to the media IDs, tape drives, or media servers involvedwhen media is frozen.

The following logs are useful when troubleshooting frozen media:

UNIX and Linux:

■ The bptm log from the media servers that froze the media:

/usr/openv/netbackup/logs/bptm

■ The Admin messages or syslog from the operating system.

Windows:

■ The bptm log from the media servers that froze the media:

install_dir\VERITAS\NetBackup\logs\bptm

■ The Windows Event Viewer System Log

■ The Windows Event Viewer Application Log

The verbosity of the bptm process log should be set to 5 to troubleshoot any mediaand drive-related issues. This log does not use excessive drive space or resourceseven at an elevated verbosity. When media is frozen, the bptm logs may containmore detailed information that the Activity Monitor or Problems Report. Set thebtpm verbosity for bptm on individual media servers by changing their logginglevels under Host Properties on the NetBackup Administration Console.

The following conditions can cause media to freeze:

■ The same media has excessive errors during backup. The log entry is as follows:

FREEZING media id E00109, it has had at least 3 errors in the last

12 hour(s)

Causes and resolutions for this problem include:

■ Dirty drives. Clean the drives that are freezing media. One of the firstsymptoms of a dirty drive is frozen media. Clean the drive according to themanufacturer's suggestions.

■ The drive itself. Check for tape device errors reported by the operatingsystem logs or by the device driver. If any are found, follow the hardwaremanufacturer's recommendations for this type of error.

■ Communication issues at the SCSI or Host Bus Adapter (HBA) level. Checkfor SCSI or HBA device errors reported by the operating system logs or bytheir driver. If any are found, follow the hardware manufacturer'srecommendations for this type of error.

Troubleshooting proceduresTroubleshooting frozen media

64

■ Ensure that the tape drives appear on the hardware compatibility list assupported for NetBackup. This list is located on the Symantec TechnicalSupport Web site:

http://support.veritas.com/menu_ddProduct_NBUESVR_view_CL.htm

■ Ensure that the media is supported for use with the tape drive by the tapedrive vendor

■ An unexpected media is found in the drive.

Incorrect media found in drive index 2, expected 30349, \

found 20244, FREEZING 30349

The following circumstances can cause this error:

■ NetBackup requests a media ID to be mounted in a drive. If the media IDthat is physically recorded on the tape is different than the NetBackupmedia ID, the media freezes. This error occurs if the robot needs to beinventoried, or if barcodes have been physically changed on the media. Theerror can also occur if another NetBackup installation previously wrote tothe media with different barcode rules.

■ The drives in the robot are not configured in order within NetBackup, orare configured with the wrong tape paths. Drive configuration that use thecorrect robot drive number is important to the proper mounting andutilization of media. The robot drive number is normally set based on therelationship of the drive serial number with the drive serial numberinformation from the robotic library. This number must be determined andvalidated before you consider the device configuration complete.

■ The media contain a non-NetBackup format.

FREEZING media id 000438, it contains MTF1-format data and cannot

be used for backups

FREEZING media id 000414, it contains tar-format data and cannot

be used for backups

FREEZING media id 000199, it contains ANSI-format data and cannot

be used for backups

These tapes have usually been written outside of NetBackup, and have foundtheir way into the library. By default, NetBackup will only write to a blankmedia or other NetBackup media. Other media types (DBR, TAR, CPIO, ANSI,MTF1 and recycled Backup Exec BE-MTF1 media) will be frozen as a safetymeasure. Change this behavior by using the following procedure:On UNIX and Linux:

65Troubleshooting proceduresTroubleshooting frozen media

To allow NetBackup to overwrite foreign media, add the following to the bp.conffile located at /usr/openv/netbackup/bp.conf for the related media server:

ALLOW_MEDIA_OVERWRITE = DBR

ALLOW_MEDIA_OVERWRITE = TAR

ALLOW_MEDIA_OVERWRITE = CPIO

ALLOW_MEDIA_OVERWRITE = ANSI

ALLOW_MEDIA_OVERWRITE = MTF1

ALLOW_MEDIA_OVERWRITE = BE-MTF1

Stop and restart the NetBackup daemons for the changes to take effect.On Windows:On the Administration Console, proceed to Host Properties | Media ServerOpen the properties for the media server in question.Select the Media tab.The Allow Media Overwrite property overrides the NetBackup overwriteprotection for specific media types. To disable overwrite protection, select oneor more of the listed media formats.Stop and restart the NetBackup services for the changes to take effect.Do not select a foreign media type for overwriting unless it is certain that thismedia type should be overwritten.For more details on what each media type is, see the NetBackup SystemAdministrator's Guide.

■ The media is a tape formerly used for the NetBackup catalog backup.

FREEZING media id 000067: it contains VERITAS NetBackup (tm)

database backup data and cannot be used for backups.

This media is frozen because it is an old catalog backup tape which NetBackupdoes not overwrite by default. The bplabel command must label the media toreset the media header.

■ The media is intentionally frozen. You can use the bpmedia command tomanually freeze media for a variety of administrative reasons. If no recordexists of a specific job freezing the media, the media may have been frozenmanually.

■ The media is physically write protected. If the media has a write-protect notchthat is set for write protection, NetBackup freezes the media.

To unfreeze frozen media, enter the following bpmedia command:

# bpmedia -unfreeze -m mediaID -h media_server

Troubleshooting proceduresTroubleshooting frozen media

66

Themedia_server variable is the one that froze the media. If this item is unknown,run the bpmedialist command and note the "Server Host:" listed in the output.The following example shows that media server denton froze media div008:

# bpmedialist -m div008

Server Host = denton

ID rl images allocated last updated density kbytes restores

vimages expiration last read <------- STATUS ------->

------------------------------------------------------------------------

DIV08 1 1 04/22/2005 10:12 04/22/2005 10:12 hcart 35 5

1 05/06/2005 10:12 04/22/2005 10:25 FROZEN

Resolving PBX problemsThe Enterprise Media Manager (EMM) services and other services of NetBackuprequire a common services framework that is called Private Branch Exchange(PBX). Like vnetd, PBX helps limit the number of TCP/IP ports that the CORBAservices of NetBackup use.

In troubleshooting PBX, consider the issues that are described in this section.

Note: If PBX is not installed or is configured incorrectly, NetBackup isunresponsive.

Checking for PBX installationNetBackup requires the Symantec Private Branch Exchange service (PBX). PBXcan be installed before NetBackup or during NetBackup installation.

See the NetBackup Installation Guide.

If you uninstall PBX, you must re-install it.

To see if PBX is installed

1 Look for the following directory on the NetBackup master server:

■ On UNIX: /opt/VRTSpbx

■ On Windows: install_path\VxPBX

2 Check the version of PBX, enter the following:

■ On UNIX: /opt/VRTSpbx/bin/pbxcfg -v

67Troubleshooting proceduresResolving PBX problems

■ On Windows: install_path\VxPBX\bin\pbxcfg -v

Checking that PBX is runningAfter you know that PBX is installed on the NetBackup master server, you needto verify that it is running.

To see if PBX is running

1 On UNIX, check for the PBX process:

ps | grep pbx_exchange

2 To start PBX on UNIX, type the following:

/opt/VRTSpbx/bin/vxpbx_exchanged start

On Windows, make sure the "Veritas Private Branch Exchange" service isstarted. (Go to Start > Run and enter services.msc.)

PBX must be set correctlyTwo settings are vital to the correct functioning of PBX: Auth User (authenticateduser) and Secure Mode. When PBX is installed, these are automatically set asrequired.

To verify the PBX settings

1 To display the current PBX settings, do one of the following:

■ On UNIX, type the following:

/opt/VRTSpbx/bin/pbxcfg -p

Example output:

Auth User:0 : root

Secure Mode: false

Debug Level: 10

Port Number: 1556

PBX service is not cluster configured

Auth User must be root and Secure Mode must be false.

■ On Windows, type the following:

install_path\VxPBX\bin\pbxcfg -p

Example output:

Troubleshooting proceduresResolving PBX problems

68

Auth User:0 : localsystem

Secure Mode: false

Debug Level: 10

Port Number: 1556

PBX service is not cluster configured

Auth User must be localsystem and Secure Mode must be false.

2 Reset Auth User or Secure Mode as needed:

■ To add the correct user to the authenticated user list (UNIX example):

/opt/VRTSpbx/bin/pbxcfg -a -u root

■ To set Secure Mode to false:

/opt/VRTSpbx/bin/pbxcfg -d -m

For more information on the pbxcfg command, refer to the pbxcfg manpage.

PBX loggingPBX uses unified logging. PBX logs are written to the following:

■ /opt/VRTSpbx/log (UNIX)

■ install_path\VxPBX\log (Windows)

The unified logging originator number for PBX is 103. More information is availableabout unified logging.

See “Unified logging” on page 85.

Error messages regarding PBX may appear in the PBX log or in the unified logginglogs for nbemm, nbpem, nbrb, or nbjm. The following is an example of an errorthat is related to PBX:

05/11/05 10:36:37.368 [Critical] V-137-6 failed to initialize

ORB:

check to see if PBX is running or if service has permissions to

connect to PBX. Check PBX logs for details

Use the vxlogview command to view PBX and other unified logs. The originatorid for PBX is 103. For more information, see the vxlogview man page. You canalso refer to the following topic:

See “Configuring and using unified logging” on page 94.

69Troubleshooting proceduresResolving PBX problems

To change the logging level for PBX, enter the following:

pbxcfg -s -l debug_level

where debug_level is a number from 0 to 10. 10 is the most verbose.

PBX may log messages by default to the UNIX system logs (/var/adm/messagesor/var/adm/syslog) or to the Windows Event Log. As a result, the system logsmay fill up with unnecessary PBX log messages, since the messages are also writtento the PBX logs (/opt/VRTSpbx/log on UNIX and <install_path>\VxPBX\log onWindows). To disable PBX logging to the system or event logs, enter the followingcommand:

# vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false

You do not have to restart PBX for this setting to take effect.

PBX securityThe PBX Secure Mode must be set to false. If Secure Mode is true, NetBackupcommands such as bplabel and vmoprcmd do not work. PBX messages similar tothe following appear in /opt/VRTSpbx/log (UNIX) or install_path\VxPBX\log(Windows).

5/12/2008 16:32:17.477 [Error] V-103-11 User MINOV\Administrator

not authorized to register servers

5/12/2008 16:32:17.477 [Error] Unauthorized Server

To correct a PBX security problem

1 Set Secure Mode to false by entering the following:

■ On UNIX:

/opt/VRTSpbx/bin/pbxcfg -d -m

■ On Windows:

install_path\VxPBX\bin\pbxcfg -d -m

2 Verity the PBX security settings by entering the following:

pbxcfg -p

3 Stop NetBackup:

■ On UNIX:

Troubleshooting proceduresResolving PBX problems

70

/usr/openv/netbackup/bin/bp.kill_all

■ On Windows:

install_path\NetBackup\bin\bpdown

4 Stop PBX:

■ On UNIX:

/opt/VRTSpbx/bin/vxpbx_exchanged stop

■ On Windows: Go to Start>Run, enter services.msc, and stop the "VeritasPrivate Branch Exchange" service.

5 Start PBX:

■ On UNIX:

/opt/VRTSpbx/bin/vxpbx_exchanged start

■ On Windows: Go to Start>Run, enterservices.msc, and start the "VeritasPrivate Branch Exchange" service.

6 Start NetBackup:

■ On UNIX:

/usr/openv/netbackup/bin/bp.start_all

■ On Windows:

install_path\NetBackup\bin\bpup

Required NetBackup daemon or service not availableIf NetBackup does not work as configured, a required NetBackup service may havestopped. For example, backups may not be scheduled or may be scheduled but arenot running. The nature of the problem depends on which process is not running.

When a NetBackup service is not running and another process tries to connect toit, messages similar to the following appear in /usr/openv/logs for PBX. (Theunified logging originator for PBX is 103.)

05/17/05 10:00:47.179 [Info] PBX_Manager:: handle_input with fd = 4

05/17/05 10:00:47.179 [Info] PBX_Client_Proxy::parse_line, line =

ack=1

71Troubleshooting proceduresResolving PBX problems

05/17/05 10:00:47.179 [Info] PBX_Client_Proxy::parse_line, line =

extension=EMM

05/17/05 10:00:47.180 [Info] hand_off looking for proxy for = EMM

05/17/05 10:00:47.180 [Error] No proxy found.

05/17/05 10:00:47.180 [Info] PBX_Client_Proxy::handle_close

To correct not having a daemon or service available

1 Start the needed service.

In this example, the missing NetBackup service is EMM. To start the neededservice, enter the nbemm command (UNIX) or start the NetBackup EnterpriseMedia Manager service (Windows; Start > Run, enter services.msc).

2 If necessary, stop and restart all NetBackup services.

■ On UNIX:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

■ On Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

New network interface cardsIf the network interface card (NIC) in a NetBackup master or media server ischanged, or if the server’s IP address changes, CORBA communications may beinterrupted in a variety of ways. To address this situation, stop and restartNetBackup.

Backup performance and NIC cardsIf backup or restore jobs are running slowly, verify that the network interfacecards (NIC) are set to full duplex. Half duplex often causes poor performance.

For help on how to view and reset duplex mode for a particular host or device,consult the manufacturer’s documentation.

Troubleshooting proceduresNew network interface cards

72

To view and reset duplex mode for a host or device (if the manufacturer’sdocumentation does not help)

1 Log in to the host that contains the network interface card(s).

2 Enter the following command to view the current duplex setting.

ifconfig -a

On some operating systems, this command is ipconfig.

Example output from a NAS filer:

e0: flags=1948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu

1500

inet 10.80.90.91 netmask 0xfffff800 broadcast 10.80.95.255

ether 00:a0:98:01:3c:61 (100tx-fd-up) flowcontrol full

e9a: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

ether 00:07:e9:3e:ca:b4 (auto-unknown-cfg_down) flowcontrol full

e9b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

ether 00:07:e9:3e:ca:b5 (auto-unknown-cfg_down) flowcontrol full

In this example, the network interface that shows "100tx-fd-up" is runningin full duplex. Only interface e0, the first in the list, is at full duplex.

A setting of "auto" is not recommended, because devices can auto negotiateto half duplex.

3 The duplex mode can be reset by using the ifconfig (or ipconfig) command.For example:

ifconfig e0 mediatype 100tx-fd

4 For most hosts, you can set full-duplex mode permanently, such as in thehost’s /etc/rc files. Refer to the host’s documentation for more information.

SERVER entries in bp.conf fileBeginning with NetBackup 6.5, on Solaris and Linux systems, every SERVER entryin a client bp.conf file must be a NetBackup master or media server. That is, eachsystem that is listed as a SERVER must have either NetBackup master or mediaserver software installed. The client service on some clients cannot be started ifthe client name is incorrectly listed as a server.

If a bp.conf SERVER entry specifies a NetBackup client-only machine, SAN clientbackups or restores over Fibre Channel may fail to start. In this case, determineif the nbftclnt process is running on the client. If it is not running, check the

73Troubleshooting proceduresSERVER entries in bp.conf file

nbftclnt unified logging file (OID 200) for errors. You may see the following in thenbftclnt log:

The license is expired or this is not a NBU server. Please check

your configuration. Note: unless NBU server, the host name can't be

listed as server in NBU configuration.

Remove or correct the SERVER entry in the bp.conf file, restart nbftclnt on theclient, and retry the operation.

Note: The nbftclnt process on the client must be running before you start a SANclient backup or restore over Fibre Channel.

Resolving unavailable storage units problemsNetBackup jobs sometimes fail because storage units are unavailable, due to drivesthat are down or configuration errors, such as referencing an incorrect robotnumber. NetBackup processes log messages to the NetBackup error log that helpyou pinpoint and resolve these types of issues.

In addition, the Job Details dialog box available from the Activity Monitor containsmessages that describe the following:

■ The resources that the job requests

■ The granted (allocated) resources.

If a job is queued awaiting resources, the Job Details dialog lists the resources forwhich the job waits. The three types of messages begin with the following headers:

requesting resource ...

awaiting resource ...

granted resource ...

Troubleshooting NetBackup in a SAN environmentNetBackup administrators may encounter any or all of the following commonproblems in a SAN (Storage Area Network) environment:

■ Intermittent backup failures

■ Connectivity issues (drives that are down)

■ SAN configuration changes

If the SAN administrator rezones the network or masks an array in use byNetBackup, the following can occur: some of the machines or devices that

Troubleshooting proceduresResolving unavailable storage units problems

74

NetBackup needs may not be available. Either action causes backups to fail anddrives to go down. The only information available to the NetBackup administratoris an error 83 (media open error) or error 84 (media write error) status code.

You can use Veritas CommandCentral Storage (or the earlier SANPoint Control)to check elements of the SAN configuration. For example, you can check whethera particular device is connected as well as the zoning and masking on the SAN.

Sometimes a switch or a Windows box is interrupted and sends out a resetcommand. Since NetBackup doesn’t automatically maintain persistent bindings,the reset command can cause drives to be mapped differently. CommandCentralStorage can help find the problem by showing the changes in the drive mappings,although it cannot automatically fix the problem.

For information on SharedDisk, refer to the "SharedDisk troubleshooting checklist"in the NetBackup Shared Storage Guide.

For information on how to implement persistent bindings, refer to theNetBackupDevice Configuration Guide.

NetBackup lets you launch CommandCentral Storage in-context. TheCommandCentral Storage Web GUI precisely displays the area of the SANconfiguration you plan to troubleshoot.

NetBackup enterprise lifecycle: best practicesSAN-related problems generally involve the use of Shared Storage Option (SSO).The two types of NetBackup users generally are as follows:

■ Operators who have limited access to hosts and to the fabric of the SAN

■ System administrators who have administrator privileges, but no access tothe fabric

The SAN administrator generally operates outside the NetBackup domain entirely.Troubleshooting NetBackup is difficult when it involves the SAN becauseadministrative responsibility tends to be spread out. No one person has a clearpicture of the overall backup structure.

CommandCentral Storage provides a consistent view of the entire SAN againstwhich to measure performance. It gives NetBackup administrators the data theyneed to request changes of and collaborate with the SAN administrators. It helpsNetBackup administrators when they design, configure, implement, or modifysolutions in response to changes in backup environments (hardware, applications,demand).

CommandCentral Storage can help those responsible for managing a backupsystem in a SAN environment by integrating SAN management and backupoperation information.

75Troubleshooting proceduresTroubleshooting NetBackup in a SAN environment

CommandCentral Storage can provide support during the following backuplifecycle stages:

■ Design

Use CommandCentral Storage during the design phase to determine thefollowing:

■ Where to deploy a backup system on the SAN

■ If SAN redesign is required to meet backup windows at minimum hardwarecost and application impactFor example, a backup design may not require the purchase of additionalswitches if it takes into account the following: the performance trendingreports that CommandCentral Storage keeps to determine the pattern offabric utilization.Or perhaps if you re-zone the fabric through CommandCentral Storage, itmay provide sufficient bandwidth for meeting backup window requirements.In addition, CommandCentral Storage can provide visibility into recoverydesigns and fabric performance in the event of large restores that criticalbusiness operations require.

■ Configuration, testingGenerally, backup systems are tested before implementation to obtainbenchmarks and adjust (tune) the system for maximum efficiency.CommandCentral Storage can provide the performance metrics for end-to-endI/O capabilities for all elements in the backup path. Additionally,CommandCentral Storage can provide valuable environmental informationfor qualifying the backup environment as well as a baseline for futuretroubleshooting configuration management.

■ Implementation, reconfiguration, productionCommandCentral Storage can help to determine whether a host can see throughthe entire I/O path to the target backup device by pinpointing connectivityissues.

Using CommandCentral Storage to troubleshoot NetBackupYou can use CommandCentral Storage in the following ways to troubleshootNetBackup in a SAN environment:

In-context launchThe ability to launch CommandCentral Storage and access an overview of theSAN from NetBackup in context is valuable for determining root cause problemsquickly. In addition, because NetBackup administrators and SAN administrators

Troubleshooting proceduresTroubleshooting NetBackup in a SAN environment

76

are often in different groups, the fragmented operations that lead to resolutiondelays may be avoided. With CommandCentral Storage, the NetBackupadministrator has a view of the overall health of the SAN as part of the initialtroubleshooting process.

Connectivity and device checkThe CommandCentral Storage view of the SAN environment can help you detectany failure in the topology.

In addition, having an environment inventory to provide to support fortroubleshooting is valuable to the support process.

General troubleshooting toolsSome ways to investigate a backup failure are as follows:

■ Launch CommandCentral Storage in context from NetBackup to check fabrichealth.

■ Check reports for fabric events occurring around the time NetBackup generatedthe error log.

Common NetBackup troubleshooting use casesThe following use cases demonstrate how CommandCentral Storage can beintegrated into a NetBackup troubleshooting procedure to investigate the SANcontext of a backup system. Most common NetBackup problems on SANs revolvearound connectivity issues.

Use Case 1: NetBackup cannot access drives or robotsTypically found as an error 213 (no storage units available for use) in NetBackup,this problem represents a loss of connectivity. This issue is a problem becauseNetBackup freezes tapes with two write failures, even when SAN problems causethe failures.

Symptom: Backup jobs fail

To troubleshoot the inability to access drives or robots

1 Check the NetBackup device monitor to see whether a device is down. If adevice is down, try to bring it back up.

2 If the drive is still down, check the following for status 219 (the requiredstorage unit is unavailable) and 213 (no storage units available for use) onthe media server:

77Troubleshooting proceduresTroubleshooting NetBackup in a SAN environment

■ Syslog

■ Device logs

■ NetBackup logs

3 Check the NetBackup logs for status 83, 84, 85, and 86. These codes relate towrite, read, open, position failures to access the drive.

4 Try a robtest to determine connectivity.

If there is no connectivity, the likely problem is with hardware.

5 From the master server, select the robot or device the storage unit is associatedwith.

6 Launch CommandCentral Storage for a view of the media server and devices.

7 Check the fabric connectivity (whether any I/O path devices are down).

Use Case 2: NetBackup device discovery cannot see a robot ordriveThe NetBackup administrator installs a new device and runs the DeviceConfiguration Wizard to discover and configure it. The wizard does not see thenewly installed device.

CommandCentral Storage topology is a good visual tool for checking connectivitybetween the hosts and the devices. You can use it to see if a network cable wasdislodged or if some other problem exists.

This use case may be encountered when you configure off-host backups. Off-hostbackups require the media server to be able to see all devices with which it conductsthe backup: disk array, disk cache, data mover, library, and drive. Connectivitymust be correct. In addition, the bptpcinfo command in NetBackup SnapshotClient generates a 3pc.conf configuration file for running the backup. Often theWWN (world wide name) for some devices is incorrect. You can useCommandCentral Storage to verify that the contents of the 3pc.conf file correlateto the actual fabric configuration.

For a description of off-host backup, the bptpcinfo command, and the 3pc.conffile, refer to the NetBackup Snapshot Client Configuration document.

For help accessing this document, see "Snapshot Client Assistance" in theNetBackup Snapshot Client Administrator’s Guide.

Symptom: After you run the Device Configuration Wizard, the new device doesnot appear in the discovered devices list.

Troubleshooting proceduresTroubleshooting NetBackup in a SAN environment

78

To troubleshoot the inability to see (discover) a robot or drive

1 Run device discovery again.

2 If the new device is still not seen, the likely problem is with hardware. LaunchCommandCentral Storage.

3 If the new device does not appear in the CommandCentral Storage topology,check SAN hardware connections to determine whether or not the device isconnected.

If the new device shows up as disconnected or offline, contact the SANadministrator and check switch configuration.

Compare this troubleshooting procedure to a similar problem without thebenefit of CommandCentral Storage, such as Robotic status code: 214, robotnumber does not exist.

See “Robotic status code: 214” on page 534.

4 Rerun the Device Configuration Wizard.

Use Case 3: Intermittent drive failureA drive fails and causes a backup to fail, but on examination the drive looks fine.

Sometimes a problem with a switch or bridge either before or during the backupjob causes the job to fail and takes down the drive. This problem is one of the mostdifficult to diagnose. By the time the NetBackup administrator looks at the SANeverything may be fine again. To use CommandCentral Storage to troubleshootthis issue, do the following: check for alerts around the time of the job failure andsee if a SAN problem occurred that would have caused the job to fail.

Another possibility is that another application reserved the device. A SCSI devicemonitoring utility is required to resolve this issue, which neither CommandCentralStorage nor NetBackup currently supplies.

Symptom: The backup job fails intermittently and the drive is down intermittently.No errors appear in the error log other than that the job failed.

To troubleshoot an intermittent drive failure problem

1 Select a drive inside the NetBackup Device Monitor. Launch CommandCentralStorage in the drive context to see whether the drive is connected to the SAN.

2 Check CommandCentral Storage alert reports to see whether a SAN problemexisted that would have affected the drive during the time the backup jobfailed.

79Troubleshooting proceduresTroubleshooting NetBackup in a SAN environment

Troubleshooting proceduresTroubleshooting NetBackup in a SAN environment

80

Using logs and reports

This chapter includes the following topics:

■ About using logs and reports

■ Where is the log and report information?

■ Reports

■ Status for user operations

■ UNIX system logs

■ Debug logs on servers

■ Debug logs on UNIX clients

■ Debug logs on PC clients

■ Windows Event Viewer logging option

■ Troubleshooting the Administration Console for UNIX

■ Query string overview

About using logs and reportsNetBackup uses several different logs and reports to help you troubleshoot anyproblems that you encounter.

Note: The log-entry format in the NetBackup logs is subject to change withoutnotice.

3Chapter

Note: The term "media server", as distinct from "master server" or "server", doesnot apply to the NetBackup server product. When you troubleshoot a NetBackupserver installation, ignore any references to media server. (This note does notapply to NetBackup Enterprise Server.)

Where is the log and report information?Users need to know where log and report information is on their systems.

Figure 3-1 shows the location of the log and report information on the client andthe server and the processes that make the information available.

Using logs and reportsWhere is the log and report information?

82

Figure 3-1 Log and report location

NetBackupAdministrationInterface

Server Programs

MediaCatalog

ClientPrograms

CLIENTSERVER

Master Server

Master or Media Server

Server DebugLogs

System LogsSystem MessagesWindows Event Log

StatusLogsNetBackup

DatabaseManager

ErrorCatalog

File Catalog

Client DebugLogs

More information is available on the programs and daemons that are mentionedin this figure.

See “About backup and restore functional overview” on page 633.

ReportsNetBackup provides the standard reports that show most of the status informationand error information. To run these reports, use the NetBackup AdministrationConsole.

83Using logs and reportsReports

See theNetBackupAdministrator’s Guide, Volume I, for instructions and detaileddescriptions about these reports.

Table 3-1 provides a summary of the reports.

Table 3-1 NetBackup reports

DescriptionReport

Displays status information and error information on the jobsthat complete within the specified time period. If an error hasoccurred, a short explanation of the error is included. On UNIXsystems, environment variables allow modification of characterlengths of some fields.

Status of Backups

Displays the detailed information on the jobs that complete withinthe specified time period.

Client Backups

Lists the problems that the server has logged during the specifiedtime period. This information is a subset of the information in theAll Log Entries report.

Problems

Lists all log entries for the specified time period. This reportincludes the information from the Problems report and MediaLogs report.

All Log Entries

Lists the contents of the media as recorded in the NetBackup imagecatalog. You can generate this report for any type of media(including disk) and filter it according to client, media ID, or path.

Images on Media

Displays the media errors or the informational messages that arerecorded in the NetBackup error catalog.

Media Logs

Displays the information about the images that are stored on tapemedia (such as tape logs, tape contents, and tape summary).

Tape Reports

Displays the information about the images that are stored on diskmedia (such as disk logs, and disk storage unit and disk poolstatus).

Disk Reports

Status for user operationsNetBackup lets you view status on the progress of user operations.

See the NetBackup Backup, Archive, and Restore Getting Started Guide forinformation on the Task Progress tab.

Using logs and reportsStatus for user operations

84

UNIX system logsThe NetBackup server daemons and programs occasionally log informationthrough the syslogd man page. syslogd then shows a message or writes theinformation in an appropriate system log or the console log.

See thesyslogdman page for the locations of system log messages on your system.

See “Enabling system logs” on page 108.

Debug logs on serversIf a problem requires more information than is available through the normal logsand reports, consult the debug logs. They show detailed information about specificprocesses.

The following sections describe the two forms of debug logging: unified loggingand legacy logging.

Unified loggingUnified logging creates log file names and messages in a standardized format.Certain NetBackup processes use unified logging.

A list of the processes that use unified logging is available.

See Table 3-2 on page 88.

Log locationsAll unified logs are written to the /usr/openv/logs directory (UNIX) and theinstall_path\NetBackup\logs folder (Windows). Unlike legacy logging, you donot need to create logging subdirectories. Log files for originator IDs are writtento a subdirectory with the name specified in the log configuration file.

Changing log file locationsThe unified logging files can consume a lot of disk space. You can direct them toa different location, if needed.

To direct unified logs to a different file system, enter the following:

■ On UNIX:

/usr/openv/netbackup/bin/vxlogcfg -a -p NB -o Default -s

LogDirectory=new_log_path

85Using logs and reportsUNIX system logs

Where new_log_path is a full path, such as /bigdisk/logs.

■ On Windows:

install_path\NetBackup\bin\vxlogcfg -a -p NB -o Default

-s LogDirectory=new_log_path

Where new_log_path is a full path, such as D:\logs.

Message typesThe following three kinds of messages can appear in unified logging files:

■ Application log messages include informational, warning, and error messages.Application messages are always logged and cannot be disabled. These messagesare localized.An example of an application message follows:

05/02/09 11:02:01.717 [Warning] V-116-18 failed to connect to

nbjm, will retry

■ Diagnostic log messages are the unified logging equivalent of the legacy debuglog messages. They can be issued at various levels of detail (similar to verboselevels in legacy logging). These messages are localized.An example of a diagnostic message follows:

05/05/09 14:14:30.347 V-116-71 [JobScheduler::doCatIncr] no

configured session based incremental catalog schedules

■ Debug log messages are intended primarily for Symantec engineering. Likediagnostic messages, they can be issued at various levels of detail. Thesemessages are not localized.

Note: Like diagnostic messages, debug messages can be disabled with thevxlogcfg command.

An example of a debug message follows:

10/29/09 13:11:28.065 [taolog] TAO (12066|1) -

Transport_Cache_Manager::bind_i, 0xffbfc194 -> 0x7179d0

Transport[12]

Unified logging file name formatUnified logging uses a standardized naming format for log files, as follows:

Using logs and reportsDebug logs on servers

86

productID-originatorID-hostID-date-rotation.log

The following shows the meaning of each of the variables in the log file name:

Identifies the product. The NetBackup product ID is 51216.product ID

Identifies the log writing entity, such as a process, service, script, orother software.

originatorID

Identifies the host that created the log file. Unless the file was moved,this ID is the host where the log resides.

hostID

Shows when the log was written, in YYMMDD format.date

A numbered instance of a log file for a given originator. Thisnumbering is used for log file rotation.

See “Unified logging file rollover” on page 93.

rotation

Example log file name:

/usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000000.log

Where:

The product ID (entity ID) for NetBackup.51216

The originator ID of the nbpem process (the NetBackup policyexecution manager).

116

The host ID for the host that created this log.2201360136

The date in YYMMDD format.041029

The rollover number that indicates the instance of this log file. Bydefault, log files roll over based on file size. If the file reachesmaximum size and a new log file is created for this originator, the newfile is designated 0000000001.

See “Unified logging file rollover” on page 93.

0000000000

Server processes that use unified loggingThe unified logging originator ID lists the processes. More than one process mayuse an originator ID.

See the UNIX and Windows client sections later in this chapter for the clientprocesses that use unified logging.

87Using logs and reportsDebug logs on servers

All logs with the following IDs are written to the /usr/openv/logs subdirectoryon UNIX or to the install_path\NetBackup\logs subdirectory on Windows(except as noted in this table).

Table 3-2 lists the NetBackup server processes that use unified logging.

Table 3-2 Unified logging: originator IDs and NetBackup processes

Processes that use the originator IDOriginator ID

Private Branch Exchange service (PBX). Writes logs to/opt/VRTSpbx/log (UNIX) and install_path\VxPBX\log(Windows).

103

nbemm: Enterprise Media Manager (EMM). This process runs only onthe EMM server.

111

nbpem: NetBackup Policy Execution Manager. This process runs onlyon the master server.

116

nbjm: NetBackup Job Manager. This process runs only on the masterserver.

117

nbrb: NetBackup Resource Broker. This process runs only on the EMMserver.

118

bmrd and bmrbd: Bare Metal Restore (BMR) master (or boot) serverdaemons. bmrbd runs on the BMR boot server.

119

bmrsavecfg: Bare Metal Restore data collection utility.bmrsavecfgruns on the NetBackup client, not server.

121

bmrc: The Bare Metal Restore utility that UNIX clients use tocommunicate to the BMR master server during a restore. bmrcoriginates on the BMR boot server and runs on the restoring client.

122

bmrs: the Bare Metal Restore commands and database interface.123

bmrcreatefloppy.exe: (Windows only) used by the Bare Metal Restorecommands that create floppy disks. bmrcreatefloppy.exe runs on theBMR boot server.

124

bmrsrtadm: The Bare Metal Restore utility that creates a sharedresource tree and bootable CDs, and runs on the BMR boot server.

125

bmrprep: The Bare Metal Restore utility that prepares BMR serversfor a client restoration.

126

bmrsetupmaster and bmrsetupboot: Bare Metal Restoreinstallation, configuration, and upgrade processes.

127

Using logs and reportsDebug logs on servers

88

Table 3-2 Unified logging: originator IDs and NetBackup processes (continued)

Processes that use the originator IDOriginator ID

Bare Metal Restore libraries get their log messages from this catalog.128

bmrconfig: The Bare Metal Restore utility that modifies a client'sconfiguration.

129

bmrpkg and bmrcreatepkg: Bare Metal Restore utilities to add thefollowing: Windows drivers, service packs, and hotfixes to the BMRmaster server so they can be used in a restore.

130

bmrrst.exe and bmrmap.exe (Windows systems only). Utilities thatrestore Windows Bare Metal Restore clients. They run on the restoringclient.

131

nbsl: NetBackup Service Layer.132

ndmpagent: NDMP Agent daemon that manages NDMP backup andrestore.

134

Controls the logging level in the NetBackup libraries. The applicationand diagnostic messages are for customer use; debug messages areintended for Symantec engineering.

137

Media server user interface for the Enterprise Media Manager (EMM).140

bmrepadm: a utility that manages the Bare Metal Restore externalprocedures that are used during a restore.

142

mds: the media selection component and device selection componentof Enterprise Media Manager (EMM).

143

Device Allocator, for shared drives.144

The Symantec OpsCenter reporting service, part of SymantecOpsCenter.

146

The Symantec OpsCenter Client, part of Symantec OpsCenter.147

The Symantec OpsCenter Server, part of Symantec OpsCenter.148

NDMP protocol messages, avrd, and robotic processes.151

bmrovradm: a utility that manages custom override functions for BareMetal Restore.

154

89Using logs and reportsDebug logs on servers

Table 3-2 Unified logging: originator IDs and NetBackup processes (continued)

Processes that use the originator IDOriginator ID

Controls the logging level in the (ACE/TAO) CORBA components forany process that uses a CORBA interface. The default level is 0 (onlyimportant messages are logged). This logging is intended for Symantecengineering.

Note: If you are instructed to increase the logging level by Symantecsupport, you must increase the debug level for OID 137 to 4 or higher.

Warning: A debug logging level greater than 0 generates largeamounts of data.

156

Remote access interface for NetBackup clients.158

Transmater for NetBackup clients.159

NetBackup Service Monitor (svcmon), which monitors the NetBackupservices and attempts to restart a service that unexpectedlyterminates.

163

NetBackup Vault.166

Disk Service Manager (DSM), which performs set and get operationson disk storage and disk storage units.

178

nbftsrvr: the FT Server process, part of SAN Client.199

nbftclnt: the FT Client process, part of SAN Client.200

FT Service Manager (FSM) component of the Enterprise Media Manager(EMM), for SAN Client.

201

Exchange Firedrill Wizard for NetBackup clients.210

The Resource Event Manager (REM) is a CORBA loadable service thatruns insidenbemm. REM works with the Disk Polling Service to monitorfree space and volume status, and to watch for disk-full conditions.

219

Disk polling service for NetBackup clients.220

The Media Performance Monitor Service (MPMS). This service runson every media server within RMMS and gathers CPU load and freememory information for the host.

221

Remote monitoring and Management Service (RMMS), which is theconduit through which EMM discovers and configures disk storageon media servers.

222

Using logs and reportsDebug logs on servers

90

Table 3-2 Unified logging: originator IDs and NetBackup processes (continued)

Processes that use the originator IDOriginator ID

The storage lifecycle manager (libssmgr), which controls lifecycleimage duplication operations.

226

The Remote Disk Service Manager interface (RDSM) that runs withinthe Remote Manager and Monitor Service. RMMS runs on mediaservers.

230

Event Manager Service (nbevtmgr).nbevtmgrprovides asynchronousevent Management Services for cooperating participants.

231

BMR launcher (bmrlauncher). A utility in the Windows BMR FastRestore image that configures the BMR environment.

248

Recovery assistant for Sharepoint Portal Server for NetBackup clients.254

Artifact generator generated source.261

NetBackup Administration Console for Windows (nbconsole).263

Legacy error codes.271

The Expiration Manager (libexpmgr), which handles capacitymanagement and image expiration for storage lifecycle operations.

272

Encryption Key Management service286

NetBackup Client Oracle utility360

nbars: Database Agent Request server process call363

How to set logging levelsUnified logging is enabled by default to log debug messages at a low volume anddiagnostic and application messages at the highest volume (finest detail).

To change the logging level

1 In the NetBackup Administration Console, expand NetBackupManagement> Host Properties.

2 Select Master Servers, Media Servers, or Clients.

3 In the Details pane, click the server or client to view the version and platform.Then, double-click to view the properties.

91Using logs and reportsDebug logs on servers

4 In the left pane, click Logging.

5 Note the Global logging level setting.

If you make changes with Global logging level, it affects the logging levelthat both unified logging and legacy logging use.

The following, however, are not affected:

■ PBX logging

■ Media and device management logging (vmd, ltid, avrd, robotic daemons,media manager commands)

■ Any unified logging processes whose debug level has been changed from thedefault setting

Set logging levels for PBX.

See “PBX logging” on page 69.

For logging information on media manager, see the following:

See “Media and device management legacy debug logs” on page 107.

To set verbosity levels for legacy logging without affecting unified logging, usethe bp.conf and vm.conf files.

See “How to set legacy logging levels” on page 112.

To set the logging level for unified logging without affecting legacy logging, usethe vxlogcfg command.

See “Configuring and using unified logging” on page 94.

The NetBackup Administration Console Global logging level field allows valuesof 0 to 5.

Table 3-3 lists the kind of detail each level includes.

Table 3-3 Global logging levels

Information to be loggedLogging level

Very important low-volume diagnostic and debug messages0

This level adds verbose diagnostic and debug messages1

Adds the progress messages2

Adds the informational dumps3

Adds the function entry and exits4

Finest detail: everything is logged5

Using logs and reportsDebug logs on servers

92

Note the following:

■ In the Global logging level field of the Administration Console, a zero (0) levelspecifies the minimum level of logging for both legacy and unified logging.However, for diagnostic and debug messages in unified logging, the logginglevel can be turned off completely (no diagnostic messages or debug messagesare logged). This level cannot be set with the Global logging level field in theNetBackup Administration Console. You can set it with thevxlogcfg command.

See “Configuring and using unified logging” on page 94.

■ A change to Global logging level affects the logging level of all NetBackup andEnterprise Media Manager (EMM) processes on the server or client. (Theexceptions are PBX and media and device management logging.) This settingoverrides any previous settings.

■ If you make a change to the VERBOSE level in the bp.conf file, it only affectsthe legacy logging level.

■ It you make a change with the vxlogcfg command, it only affects the unifiedlogging level.

Unified logging file rolloverTo prevent log files from becoming too large, or to control when or how often theyare created, you can set a log "rollover" parameter. When a file size or time settingis reached, the current log file is closed. New log messages for the logging processare written to (rolled over to) a new log file.

Log rollover can occur according to any of the following options as set by thevxlogcfg command:

■ File size (this option is the default), as defined by the MaxLogFileSizeKB option.

■ Local time, as defined by the RolloverAtLocalTime option.

■ Periodic (elapsed time), as defined by the RolloverPeriodInSeconds option.

■ File size or Local time, whichever limit is encountered first

■ File size or Periodic, whichever limit is encountered first

To set these options, use the vxlogcfg command with the RolloverMode option.An example that uses vxlogcfg is available:

See “vxlogcfg command” on page 97.

By default, log-file rollover is based on file size (5120 KB). When a log file reaches5120 KB in size, the file is closed and a new one is created.

The following example file names show log file rollover, with rotation IDincremented:

93Using logs and reportsDebug logs on servers

/usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000000.log

/usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000001.log

/usr/openv/logs/nbpem/51216-116-2201360136-041029-0000000002.log

Logs for the processes that are listed in Table 3-2 can use rotation. Certain legacylogs can also use rotation.

See “Legacy logging file rotation (robust logging)” on page 109.

Log file recycling (removing older log files)Two ways to automatically delete log files are as follows:

■ Unified logging files can be automatically deleted when the number of log filesexceeds a certain number. The NumberOfLogFiles option on the vxlogcfg

command defines that number. An example of vxlogcfg usage is available:

See “vxlogcfg command” on page 97.

■ The Keep logs For setting can delete both unified logs and legacy logs. Thisparameter is located in the Clean-up dialog box under Host Properties in theNetBackup Administration Console.

Note the following regarding the Keep logs For setting:

■ Logs that age beyond the number of days that the Keep logs For setting specifiesare deleted for unified and legacy logging.

■ Unified logging log files can also be deleted explicitly using the vxlogmgr

command. If vxlogmgr does not manually delete or move files, the Keep logsFor setting removes the old logs for both unified and legacy logging.

If the vxlogcfg LogRecycle option is ON (true), the Keep logs For setting isdisabled for unified logs. In this case, unified logging files are deleted when theirnumber (for a particular originator) exceeds the number that is specified byNumberOfLogFiles on the vxlogcfg command.

Configuring and using unified loggingThis section describes commands for controlling unified logging with examples.

To access logging controls in the NetBackup Administration Console, click HostProperties>Master/MediaServer>Properties>Logging. Also, three commandsthat manage unified logging are also available and described in this section. Thesecommands are located in /usr/openv/netbackup/bin (UNIX) andinstall_path\NetBackup\bin (Windows).

Using logs and reportsDebug logs on servers

94

vxlogview commandUse this command to view the logs that unified logging creates. These logs arestored in subdirectories in /usr/openv/logs on UNIX or install_path\logs onWindows.

Unlike the files that are written in legacy logging, you cannot view unified loggingfiles with a text editor. The unified logging files are in binary format, and someof the information is contained in an associated resource file. Only the vxlogviewcommand can assemble and display the log information correctly.

You can use vxlogview to view NetBackup log files as well as PBX log files.

To view PBX logs using the vxlogview command, do the following:

■ Ensure that you are an authorized user. For UNIX and Linux, you must haveroot privileges. For Windows, you must have Administrator privileges.

■ Specify the PBX product ID by entering -p 50936 as a parameter on thevxlogview command line.

vxlogview examplesExample 1

Display the log messages for NetBackup that show only the date, time, messagetype, and message text:

vxlogview --prodid 51216 --display D,T,m,x

Example 2

Display the log messages for originator 116 (nbpem) that were issued during thelast 20 minutes:

vxlogview -o 116 -t 00:20:00

Note that you can specify -o nbpem instead of -o 116.

Example 3

Display the log messages for nbpem that were issued during a particular timeperiod:

vxlogview -o nbpem -b "05/03/05 06:51:48 AM" -e "05/03/05

06:52:48 AM"

Example 4

You can use the -i option instead of -o, to specify an originator:

95Using logs and reportsDebug logs on servers

vxlogview -i nbpem

The vxlogview -i option searches only the log files that the specified process(nbpem) creates. The originator ID of these files in the log file name is 116. Bylimiting the log files that it has to search, vxlogview returns a result faster. Bycomparison, the vxlogview -o option searches all unified log files for messagesthat are logged by the specified process.

Note: If you use the -i option with a process that is not a service (no originator IDin the file name), vxlogview returns the message "No log files found." In this case,use the -o option instead of the -i option. Typically, the NetBackup process is aservice if it appears in the Activity Monitor of the NetBackup AdministrationConsole, under the Daemons tab (UNIX) or Services tab (Windows).

Example 5

You can search the logs for a particular job ID:

vxlogview -i nbpem | grep "jobid=job_ID"

Note: The jobid= search key should contain no spaces, and jobid= must belowercase.

When searching for a job ID, you can use any vxlogview command options. Thisexample uses the -i option with the name of the process (nbpem).

vxlogmgr commandUse this command to manage unified logging files, such as to move or delete logs.

Example 1

List all unified log files for the nbrb service:

vxlogmgr -s -o nbrb

Example output:

/usr/openv/logs/nbrb/51216-118-1342895976-050503-0000000000.log

/usr/openv/logs/nbrb/51216-118-1342895976-050504-0000000000.log

/usr/openv/logs/nbrb/51216-118-1342895976-050505-0000000000.log

Total 3 file(s)

If the vxlogcfg NumberOfLogFiles option is set to 1, the following deletes thetwo oldest log files for the nbrb service:

Using logs and reportsDebug logs on servers

96

vxlogmgr -d -o nbrb -a

Example output:

Following are the files that were found:

/usr/openv/logs/nbrb/51216-118-1342895976-050504-0000000000.log

/usr/openv/logs/nbrb/51216-118-1342895976-050503-0000000000.log

Total 2 file(s)

Are you sure you want to delete the file(s)? (Y/N):

Y

Deleting

/usr/openv/logs/nbrb/51216-118-1342895976-050504-0000000000.log ...

Deleting

/usr/openv/logs/nbrb/51216-118-1342895976-050503-0000000000.log ...

Example 2

Delete the unified log files that NetBackup created in the last 15 days:

vxlogmgr -d --prodid 51216 -n 15

Example 3

Delete all unified log files for originator nbrb:

vxlogmgr -d -o nbrb

Example 4

Delete all unified log files for NetBackup:

vxlogmgr -d -p NB

vxlogcfg commandUse this command to configure unified logging settings. For instance, usevxlogcfgto change logging levels and rollover settings.

Note the following items:

■ vxlogcfg is the only way to turn off diagnostic and debug messages in unifiedlogging. In legacy logging, the writing of messages cannot be turned off, onlyminimized.

■ The vxlogcfg settings for robust file logging (MaxLogFileSizeKB andNumberOfLogFiles) also affect certain legacy logs.See “Legacy logging file rotation (robust logging)” on page 109.

■ Absolute paths must be specified, not relative ones.

97Using logs and reportsDebug logs on servers

Controlling log file sizeBy default, the maximum log file size in unified logging is 5120 KB. After a logfile reaches 5120 KB, the file closes and a new log file opens.

You can change the maximum file size with the vxlogcfg command’sMaxLogFileSizeKB option. The following example changes the default maximumlog size to 2048 KB for product NetBackup:

vxlogcfg -a -p 51216 -o Default -s MaxLogFileSizeKB=2048

Note: For MaxLogFileSizeKB to be effective, the vxlogcfg command’sRolloverMode option must be set to FileSize.

The following sets the default NetBackup rollover mode:

vxlogcfg -a --prodid 51216 --orgid Default -s

RolloverMode=FileSize

MaxLogFileSizeKB can be set per originator. If it is not configured for a givenoriginator, that originator uses the default value. The following example overridesthe default value for service nbrb (originator 118).

vxlogcfg -a -p 51216 -o nbrb -s MaxLogFileSizeKB=1024

To make nbrb follow the default setting again, execute:

vxlogcfg -r -p 51216 -o nbrb -s MaxLogFileSizeKB

Setting rollover modeThe following example sets the NetBackup (prodid 51216) rollover mode toperiodic:

vxlogcfg -a --prodid 51216 --orgid 116 -s RolloverMode=Periodic

RolloverPeriodInSeconds=86400

This example sets rollover mode for nbpem (originator ID 116) to periodic. It alsosets the interval until the next nbpem log file rollover to 24 hours (86400 seconds).

Setting log recyclingThe following example sets automatic log file deletion for nbemm logs (originatorID 111):

Using logs and reportsDebug logs on servers

98

vxlogcfg -a --prodid 51216 --orgid 111 -s RolloverMode=FileSize

MaxLogFileSizeKB=5120 NumberOfLogFiles=999999 LogRecycle=TRUE

This example sets nbemm rollover mode to file size, and turns on log recycling.When the number of log files exceeds 999999, the oldest log file is deleted.

See “Controlling the number of log files with vxlogmgr” on page 100.

Setting debug level and diagnostic levelThe following example sets the debug level and diagnostic level for all theoriginators of product ID NetBackup (51216):

vxlogcfg -a --prodid 51216 --orgid ALL -s DebugLevel=0

DiagnosticLevel=1

For further details on these commands, refer to theNetBackupCommandsmanualor to the man pages.

Listing unified logging settingsThe following vxlogcfg example shows how to list the active unified loggingsettings for a given originator (the nbrb service). Note that MaxLogFileSizeKB,NumberOfLogFiles, and RolloverMode are included in the output.

vxlogcfg -l -o nbrb -p NB

Output:

Configuration settings for originator 118, of product 51,216...

LogDirectory = /usr/openv/logs/

DebugLevel = 5

DiagnosticLevel = 5

LogToStdout = False

LogToStderr = False

LogToOslog = False

RolloverMode = FileSize

MaxLogFileSizeKB = 5120

RolloverPeriodInSeconds = 43200

RolloverAtLocalTime = 0:00

NumberOfLogFiles = 4

OIDNames = nbrb

L10nLib = /usr/openv/lib/libvxexticu.so

L10nResource = nbrb

L10nResourceDir = /usr/openv/resources

SyslogIdent = VRTS-NB

99Using logs and reportsDebug logs on servers

SyslogOpt = 0

SyslogFacility = LOG_LOCAL5

LogFilePermissions = 436

Controlling the number of log files with vxlogmgrYou can use the vxlogmgr command with the vxlogcfg command’sNumberOfLogFiles option to manually delete log files.

For example, you currently have 10 unified logging files and the vxlogcfg

command’s NumberOfLogFiles option is set to 2. Enter the following to keep thetwo most recent log files and delete the rest for all originators:

vxlogmgr -a -d

The following applies to all NetBackup originators:

vxlogmgr -a -d -p NB

The following applies to all PBX originators:

vxlogmgr -a -d -p ics

The following deletes log files for the nbrb service only:

vxlogmgr -a -d -o nbrb

Controlling disk space usage with vxlogmgrPeriodically run the vxlogmgr -a command (such as through a cron job) to deletelogs and monitor the disk space that unified logging uses.

The disk space that a given originator uses can be calculated as follows:

NumberOfFiles for originator * MaxLogFileSizeKB for originator

The total disk space NetBackup unified logs consume is the sum of the disk spacethat each originator consumes. If none of the originators overrides theNumberOfFiles and MaxLogFileSizeKB settings, then the total disk space thatunified logging consumes is as follows:

Number of NetBackup originators * default MaxLogFileSizeKB *

default NumberOfFiles

To see the current unified logging settings, use the vxlogcfg command as shownin the following topic:

See “Listing unified logging settings” on page 99.

Using logs and reportsDebug logs on servers

100

For example, assume the following:

■ vxlogmgr -a -p NB is configured as a cron job with a frequency of 1 hour.

■ No NetBackup originators override default settings for MaxLogFileSizeKB orNumberOfFiles.

■ The number of active NetBackup originators on the host is 10. (This total maybe typical of a NetBackup master server that is not running BMR or NDMP.)

■ The default NumberOfFiles is equal to 3.

■ The default MaxLogFileSizeKB is equal to 5120.

Given these conditions, unified logging consumes:

Number of NetBackup originators * default MaxLogFileSizeKB *

default NumberOfFiles.

Which is 10 * 5120 * 3 KB, or 15360 kilobytes of disk space at the end of each hour.

Submitting unified logging files to Symantec supportThis topic describes an example of how to gather unified logs for NetBackup.

101Using logs and reportsDebug logs on servers

To gather unified logs for NetBackup

1 Create a directory:

mkdir /upload

2 To copy unified logs (for NetBackup only) to the /upload directory:

vxlogmgr -p NB -c --dir /upload

Example output:

Following are the files that were found:

/usr/openv/logs/bmrsetup/51216-157-2202872032-050125-0000000000.log

/usr/openv/logs/nbemm/51216-111-2202872032-050125-0000000000.log

/usr/openv/logs/nbrb/51216-118-2202872032-050125-0000000000.log

/usr/openv/logs/nbjm/51216-117-2202872032-050125-0000000000.log

/usr/openv/logs/nbpem/51216-116-2202872032-050125-0000000000.log

/usr/openv/logs/nbsl/51216-132-2202872032-050125-0000000000.log

Total 6 file(s)

Copying

/usr/openv/logs/bmrsetup/51216-157-2202872032-050125-0000000000.log ...

Copying

/usr/openv/logs/nbemm/51216-111-2202872032-050125-0000000000.log ...

Copying

/usr/openv/logs/nbrb/51216-118-2202872032-050125-0000000000.log ...

Copying

/usr/openv/logs/nbjm/51216-117-2202872032-050125-0000000000.log ...

Copying

/usr/openv/logs/nbpem/51216-116-2202872032-050125-0000000000.log ...

Copying

/usr/openv/logs/nbsl/51216-132-2202872032-050125-0000000000.log ...

Using logs and reportsDebug logs on servers

102

3 Change to the /upload directory and list its contents:

cd /upload

ls

Output:

51216-111-2202872032-050125-0000000000.log

51216-116-2202872032-050125-0000000000.log

51216-117-2202872032-050125-0000000000.log

51216-118-2202872032-050125-0000000000.log

51216-132-2202872032-050125-0000000000.log

51216-157-2202872032-050125-0000000000.log

4 Tar the log files:

tar -cvf file_name.logs ./*

Legacy NetBackup loggingCertain NetBackup processes use unified logging.

See “Unified logging” on page 85.

All other NetBackup processes use legacy logging.

Enabling legacy loggingIn legacy debug logging, each process creates logs of debug activity in its ownlogging directory. To enable legacy debug logging on NetBackup servers, createthe appropriate directories for each process for the following platforms:

■ On UNIX:

/usr/openv/netbackup/logs

/usr/openv/volmgr/debug

■ On Windows:

install_path\NetBackup\logs

install_path\Volmgr\debug

Information is available about how to enable the Status Collector Daemon:

See “Enabling the status collector daemon” on page 109.

Tables are available that list the log directories that you must create.

103Using logs and reportsDebug logs on servers

See Table 3-4 on page 104.

See Table 3-5 on page 107.

Note: You must create these directories before logging can take place. If thesedirectories exist, NetBackup creates log files in the directory for the associatedprocess. A debug log file is created when the process begins.

Note:On a Windows server, you can create the debug log directories at once, underinstall_path\NetBackup\logs, by running the following batch file:install_path\NetBackup\Logs\mklogdir.bat.

Media servers have only the bpbrm, bpcd, bpdm, and bptm debug logs.

NetBackup server legacy debug logsTable 3-4 describes the server legacy debug logs.

Table 3-4 NetBackup legacy logs (not media and device management)

Associated processCreate directory underDebug log directoryto create

Administrative commands./usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

admin

NetBackup and restore manager./usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpbrm

NetBackup client daemon or manager. TheNetBackup Client service starts this process

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpcd

NetBackup jobs database manager program./usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpdbjobs

NetBackup disk manager./usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpdm

NetBackup database manager. This processruns only on master servers. On Windowssystems, it is the NetBackup databasemanager service.

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpdbm

Using logs and reportsDebug logs on servers

104

Table 3-4 NetBackup legacy logs (not media and device management)(continued)

Associated processCreate directory underDebug log directoryto create

The NetBackup-Java application serverauthentication service that is started whenthe NetBackup Java interface applicationsstart. On UNIX servers, inetd starts it. OnWindows servers, the Client Services servicestarts it.

This program authenticates the user thatstarted the application.

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpjava-msvc

The NetBackup program thatbpjava-msvcstarts upon successful logon through thelogon dialog box that is presented when aNetBackup-Java interface starts. Thisprogram services all requests from the Javauser interfaces on the NetBackup master ormedia server host where bpjava-msvc isrunning (all Windows platforms).

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpjava-susvc

NetBackup request daemon or manager. OnWindows systems, this process is called theNetBackup Request Manager service.

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bprd

The NetBackup process for synthetic backup.nbjm starts bpsynth. bpsynth runs on themaster server.

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bpsynth

NetBackup tape management process./usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

bptm

System log.You must enable system logging totroubleshoot ltid or robotic software. Seethe syslogd man page.

syslogs

105Using logs and reportsDebug logs on servers

Table 3-4 NetBackup legacy logs (not media and device management)(continued)

Associated processCreate directory underDebug log directoryto create

The user_ops directory is created duringthe install of NetBackup on all servers andclients. NetBackup Java interface programsuse it for the following: temporary files andfor job and progress log files that the userBackup, Archive, and Restore program(jbpSA) generates. This directory must existfor successful operation of any of the Javaprograms and must have public read, write,and execute permissions. user_opscontains a directory for every user that usesthe Java programs.

In addition, on NetBackup-Java capableplatforms, the NetBackup Java interface logfiles are written in the nbjlogssubdirectory. All files in the user_opsdirectory hierarchy are removed accordingto the setting of the KEEP_LOGS_DAYSconfiguration option.

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

user_ops

The Veritas network daemon, used to create"firewall friendly" socket connections.Started by the inetd(1M) process.

Note: Logging occurs in either the/usr/openv/logs directory or the/usr/openv/netbackup/logs if thevnetd directory exists there. If the vnetddirectory exists in both locations, loggingoccurs only in/usr/openv/netbackup/logs/vnetd.

/usr/openv/netbackup/logs (UNIX)

install_path\NetBackup\logs (Windows)

vnetd

More information is available on the programs and daemons that write the logs.

See “About backup and restore functional overview” on page 633.

On UNIX systems, also refer to the README file in the /usr/openv/netbackup/logsdirectory.

Using logs and reportsDebug logs on servers

106

Media and device management legacy debug logsThe debug log directories that are written to /usr/openv/volmgr/debug (UNIX)or install_path\Volmgr\debug (Windows) enable logging for the mediamanagement processes and device management processes.

Note the following items:

■ NetBackup creates one log per day in each of the debug directories.

■ Information is available about the format of the log file names.See “Legacy logging file name format without log file rotation” on page 111.

■ On UNIX: To disable vmd debug logging, either delete or rename the/usr/openv/volmgr/debug/daemon directory.

■ On Windows, to disable debug logging for the NetBackup Volume Managerservice, either delete or rename the install_path\Volmgr\debug\daemon

folder.

■ NetBackup retains debug logs for the number of days you specify with theDAYS_TO_KEEP_LOGS = entry in the vm.conf file. (The default is infiniteretention.)For instructions on how to use this entry, see the NetBackup Administrator’sGuide, Volume II.

Table 3-5 describes the media management legacy debug log and devicemanagement legacy debug logs.

Table 3-5 Media and device management legacy debug logs

Associated processCreate directory underDebug log directoryto create

Debug information on transactions betweenNetBackup and the Storage Tek ACSLSserver.

/usr/openv/volmgr/debug (UNIX)acsssi

Debug information for vmd (NetBackupVolume Manager service, Windows) and itsassociated processes (oprd and rdevmi).Stop and restart vmd after creating thedirectory.

/usr/openv/volmgr/debug (UNIX)

install_path\Volmgr\debug (Windows)

daemon

Debug information on ltid, the MediaManager device daemon (UNIX), or on theNetBackup Device Manager service(Windows), and on avrd. Stop and restartltid after creating the directory.

/usr/openv/volmgr/debug (UNIX)

install_path\Volmgr\debug (Windows)

ltid

107Using logs and reportsDebug logs on servers

Table 3-5 Media and device management legacy debug logs (continued)

Associated processCreate directory underDebug log directoryto create

Debug information on the processes thatrequest media management services fromvmd or EMM. Stop and restart vmd aftercreating the directory.

/usr/openv/volmgr/debug (UNIX)

install_path\Volmgr\debug (Windows)

reqlib

Debug information on all robotic daemons,which includes tldcd, tl8cd, and tl4ddaemons. Stop and restart robotic daemons.

/usr/openv/volmgr/debug (UNIX)

install_path\Volmgr\debug (Windows)

robots

Debug information for device configuration,including the tpconfig and thetpautoconf commands and the NetBackupAdministration Console.

/usr/openv/volmgr/debug (UNIX)

install_path\Volmgr\debug (Windows)

tpcommand

Debug information for the NetBackup StatusCollection daemon. Stop and restart vmscdafter creating the directory.

/usr/openv/volmgr/debug/ (UNIX)

install_path\Volmgr\debug\ (Windows)

vmscd

Enabling system logsOn UNIX, NetBackup automatically records robotic and network errors in thesystem logs by using syslogd. On Windows, NetBackup records robotic and driveerrors in the Event Viewer Application log. On both operating systems, log entriesare also made when robotically controlled drives change between UP and DOWNstates.

On UNIX: enable debug logging to the system logs by including the verbose option(-v) on the command that you use to start a daemon.

The command you use is one of the following:

■ The ltid command that started the device management processes. If the -v

option is included on the ltid command, all daemons that were started as aresult also have the -v option in effect.

Or

■ A command to start a specific daemon (for example, acsd -v).

To troubleshoot ltid or robotic software, you must enable system logging. Seethe syslogd(8) man page for information on setting up system logs. Errors arelogged with LOG_ERR, warnings with LOG_WARNING, and debug informationwith LOG_NOTICE. The facility type is daemon.

Using logs and reportsDebug logs on servers

108

Note:On HP-UX, thesysdiag tool may provide additional information on hardwareerrors.

Enabling the status collector daemonTo enable debug logging for the NetBackup Status Collection Daemon (vmscd),create the following directory before you start nbemm.

As an alternative, you can stop and restart nbemm after creating the followingdirectory:

■ On UNIX: /usr/openv/volmgr/debug/reqlib

■ On Windows: install_path\Volmgr\debug\reqlib\

Controlling legacy logsNetBackup retains legacy debug logs for the number of days that are specified inthe Keep Logs global attribute (28 days by default). Then it deletes them.

Instructions are available on how to change Keep Logs.

See the NetBackup Administrator’s Guide, Volume I.

A robust logging feature is also available for controlling the size of debug logsthat certain NetBackup processes create.

See “Legacy logging file rotation (robust logging)” on page 109.

Debug logs can grow very large. Enable them only if unexplained problems exist.Delete the logs and the associated directory when they are no longer needed.

Legacy logging file rotation (robust logging)To control the size of legacy logs written by certain NetBackup processes, a featurecalled robust logging can be used. This feature does not apply to media and devicemanagement logging.

See “Media and device management log retention” on page 110.

This feature involves file rotation, as used in unified logging.

See “Unified logging file rollover” on page 93.

To limit the amount of disk space that the logs consume, do the following: set themaximum size for a log file and the number of log files to keep in a loggingdirectory.

109Using logs and reportsDebug logs on servers

When a log file grows to its maximum size, it closes and a new file is opens. If thenew file exceeds the number of log files that is allowed for the directory, the oldestfile is deleted.

Logs created by the following NetBackup processes can use log rotation (robustlogging):

■ bpbkar (client process only)

■ bpbrm

■ bpcd

■ bpdbm

■ bpdm

■ bprd

■ bptm

For the legacy logs created by other NetBackup processes (but not media anddevice management), use the Keep Logs For setting as follows:

■ Windows: In the Host Properties > Properties > Clean-up dialog box

■ UNIX: In the Host Properties > Properties > Global Attributes dialog box

The Keep Logs For setting ultimately applies to all legacy logs. If this setting is10 and robust file logging settings allow logs to exist more than 10 days, the logsare deleted on day 11.

Media and device management log retentionFor media and device management legacy logs, use the DAYS_TO_KEEP_LOGSsetting in the vm.conf file to control log file rotation. This file is located in/usr/openv/volmgr/ (UNIX) andinstall_path\Volmgr\ (Windows). For example,enter the following in the vm.conf file:

DAYS_TO_KEEP_LOGS = 3

Configuring legacy log rotationThis procedure shows how to configure legacy log rotation.

Using logs and reportsDebug logs on servers

110

To configure the legacy log rotation

1 Go to HostProperties>MasterServers>Properties>Logging and click theEnable robust logging box to enable legacy log rotation. This item applies tolegacy logs only.

By default, the maximum file size is 5120 KB and the number of files that arekept per log directory is 3.

If Enable robust logging is disabled, the standard log-file behavior remainsin effect: one log file is created per log directory per day, and log deletion isbased on the Keep Logs For setting.

2 To change the maximum file size, or number of log files per directory, usethe MaxLogFileSizeKB and NumberOfLogFiles options on the vxlogcfg

command.

The vxlogcfg command is located in /usr/openv/netbackup/bin (on UNIX)and install_path\NetBackup\bin (on Windows).

For example:

vxlogcfg -a -p 51216 --orgid Default -s

MaxLogFileSizeKB=2048,NumberOfLogFiles=10

This example sets the maximum file size to 2048 KB and sets the maximumnumber of log files per log directory to 10.

It sets the default values for all unified logging processes and for the legacyprocesses for NetBackup (product ID 51216). A list of these processes isavailable:

See “Legacy logging file rotation (robust logging)” on page 109.

More examples of the vxlogcfg command are available.

See “Configuring and using unified logging” on page 94.

You can also refer to the vxlogcfg man page or to theNetBackup Commandsmanual.

Legacy logging file name format without log file rotationTwo log file name formats are used in legacy logging. The format depends onwhether or not the log uses file rotation (robust logging).

In the standard legacy log system, a NetBackup process creates one debug log fileper day.

The log file name is of the following format:

■ On UNIX: log.mmddyy

111Using logs and reportsDebug logs on servers

For example: log.040805

■ On Windows: mmddyy.log

For example: 040105.log

Legacy logging file name format with log file rotationIn the legacy logging system with Enable Robust Logging enabled, a NetBackupprocess creates a certain number of log files. Each file grows to a certain sizebefore it closes and a new one is created. The file name is of this format:

mmddyy_nnnnn.log

For example: 040105_00001.log

Where nnnnn is a counter or a rotation number for the log file. When the counterexceeds the setting for number of log files, the oldest log file is deleted. TheNumberOfLogFiles option on the vxlogcfg command sets the number of log files.

For compatibility with existing scripts, the debug log file naming format does notchange. If log files are already created with the standard legacy naming formatand then robust file logging is enabled, the following occurs: only the new log filesfor the processes that robust logging governs use the new file rotation namingformat.

Any mixture of new and old log file names in a legacy debug log directory ismanaged according to the following: the Keep Logs For setting and the robustlogging settings, when applicable.

See “Legacy logging file rotation (robust logging)” on page 109.

How to set legacy logging levelsYou can set legacy logging levels to increase the amount of information thatprocesses can write in the logs.

The following settings affect legacy logging, except media and device management.

■ On Windows or UNIX systems, set the Global Logging Level to a higher level,in the Logging dialog box. (Click Host Properties > Master Server Properties> Logging tab > Logging dialog box.)

Note:This setting affects legacy logging (but not media and device managementlogging) and unified logging.

More information is available for synthetic backup.See “Logs to accompany problem reports for synthetic backup” on page 113.

Using logs and reportsDebug logs on servers

112

■ On UNIX, add a VERBOSE entry in the /usr/openv/netbackup/bp.conf file.VERBOSE by itself sets the verbose value to 1. For more log detail, enter VERBOSE= 2 or a higher value. This setting affects legacy logging only.

Warning: High verbose values can cause debug logs to become very large.

■ Use the Logging dialog box to set the logging level for individual processes.(Click Host Properties > Master Server Properties > Logging tab > Loggingdialog box.) Or, specify the verbose flag (if available) when you start theprogram or daemon.See the NetBackup Administrator’s Guide, Volume I.

In media and device management legacy logging, only two levels exist: not verbose(the default), and verbose. To set the verbose (higher) level, add the word VERBOSEto the vm.conf file. Create the vm.conf file if necessary and restart ltid and vmd

after you add the VERBOSE entry.

On UNIX, add VERBOSE to the /usr/openv/volmgr/vm.conf file.

On Windows, add VERBOSE to the install_path\Volmgr\vm.conf file. This entryaffects logging levels in the Event Viewer Application and System log.

Logs to accompany problem reports for synthetic backupTo debug problems with synthetic backups, you must include in the problemreport a complete set of logs.

The two types of logs to include are as follows:

■ Log files that unified logging createsFor information about how to gather unified logging files relevant to theproblem, see the following:See “Submitting unified logging files to Symantec support” on page 101.

■ Log files that legacy logging creates

If the following legacy log directories have not been created, you must createthe directories. Set the debug level to 5 and then rerun the job.

■ Create the following directories on the master server:

install_path/netbackup/logs/bpsynth

install_path/netbackup/logs/bpdbm

install_path/netbackup/logs/vnetd

■ Create the following directories on the media server:

113Using logs and reportsDebug logs on servers

install_path/netbackup/logs/bpcd

install_path/netbackup/logs/bptm

install_path/netbackup/logs/bpdm

■ Set the logging level as follows:Use the Global logging level option on the Logging tab in the Master ServerProperties dialog box.See “Using the Host Properties window” on page 61.

■ Rerun the job and then gather the logs from the directories that you created.The bptm logs are required only if the images are read from or written toa tape device. The bpdm logs are needed only if the images are read from orwritten to disk.If the images are read from multiple media servers, the debug logs for bptmor bpdm must be collected from each media server.

Try fileInclude the try file for the job ID from the following directory:

install_path/netbackup/db/jobs/trylogs/jobid.t

For instance, if the job ID of the synthetic backup job was 110, then the try file isnamed 110.t.

Policy attributesCapture the output from the following command and send it to Support with therest of the information:

install_path/netbackup/bin/admincmd/bppllist policy_name -L

where policy_name is the name of the policy for which the synthetic backup jobwas run.

List of storage unitsCapture the output from the following command and send it to Support with therest of the information:

install_path/netbackup/bin/admincmd/bpstulist -L

Using logs and reportsDebug logs on servers

114

Debug logs on UNIX clientsMost UNIX client logs are of the legacy type, with the exception of a few BareMetal Restore processes, as explained in this section.

Unified logging on UNIX clientsThe following are the UNIX client processes that use unified logging:

■ nbftclnt: originator ID 200.

■ bmrsavecfg: originator ID 121.

■ bmrc: originator ID 122. bmrc originates from the BMR boot server, which mayor may not be a NetBackup server, and runs on the restoring client.

■ nbbrowse: originator ID 359. NetBackup Client Browser.

■ nbcs: originator ID 366. Client service.

A description is available of unified logging file name format and other details:

See “Unified logging” on page 85.

Unified logging is enabled by default.

Legacy logging on UNIX clientsTo enable legacy debug logging on UNIX clients, create the appropriate directoriesin the following directory path:

/usr/openv/netbackup/logs

The following table lists the legacy debug log directories that apply to UNIX clients.

Additional information on legacy logging is available:

See “Legacy NetBackup logging” on page 103.

Note: Create the directories with access modes of 777 so that user processes canwrite to the log files.

Table 3-6 describes the UNIX client debug logs for legacy logging.

115Using logs and reportsDebug logs on UNIX clients

Table 3-6 UNIX client debug logs: Legacy logging

Associated processDebug logdirectory

Menu driven client-user interface program.bp

Archive program. Also useful for debugging bp.bparchive

Backup program. Also useful for debugging bp.bpbackup

Program that is used to generate backup images.bpbkar

NetBackup client daemon or manager.bpcd

Program that starts a script to back up a database on a NetBackupdatabase agent client. See the system administrator's guide for theappropriate NetBackup database agent for more information.

bphdb

The NetBackup-Java application server authentication service thatinetd starts during startup of the NetBackup Java interfaceapplications. This program authenticates the user that started theapplication.

bpjava-msvc

The NetBackup program thatbpjava-msvc starts upon successfullogon through the logon dialog box that is presented when aNetBackup-Java interface is started. This program services allrequests from the Java administration and user interfaces on thehost where bpjava-msvc is running.

bpjava-usvc

Program that lists backed up and archived files. Also useful fordebugging bp.

bplist

Program that determines local mount points and wildcard expansionfor Multiple Data Streams.

bpmount

Command-line program on clients to export Oracle data in XMLformat. Communicates with bprd on server.

bporaexp

64-bit command-line program on clients to export Oracle data inXML format. Communicates with bprd on server.

bporaexp64

Command-line program on clients to import Oracle data in XMLformat. Communicates with bprd on server.

bporaimp

64-bit command-line program on clients to import Oracle data inXML format. Communicates with bprd on server.

bporaimp64

Restore program. Also useful for debugging bp.bprestore

Using logs and reportsDebug logs on UNIX clients

116

Table 3-6 UNIX client debug logs: Legacy logging (continued)

Associated processDebug logdirectory

For more information on these logs, see the NetBackup guide forthe database-extension product that you use.

db_log

These logs have information about themtfrdprocess, which is usedfor phase 2 imports and restores of Backup Exec media.

mtfrd

tar process during restores.tar

The user_ops directory is created during the install of NetBackupon all servers and clients. The NetBackup Java interface programsuse it for the following: temporary files and for job and progress logfiles that the user Backup, Archive, and Restore program (jbpSA)generates. This directory must exist for successful operation of anyof the Java programs and must have public read, write, and runpermissions. This directory contains a directory for every user thatuses the Java programs.

In addition, on NetBackup-Java capable platforms, the NetBackupJava interface log files are written in a subdirectory that is callednbjlogs. All files in theuser_opsdirectory hierarchy are removedaccording to the setting of the KEEP_LOGS_DAYS configurationoption.

user_ops

Controlling log size on UNIX clientsFor the unified logging files that the Bare Metal Restore process bmrsavecfgcreates, you can control logging with log file rotation.

See “Unified logging file rollover” on page 93.

For the legacy logging files that the bpbkar and the bpcd processes create, youcan control logging with log file rotation.

See “Legacy logging file rotation (robust logging)” on page 109.

For all other client logs, logs are kept for the number of days that are specified inthe following setting: Keepstatusofuser-directedbackups,archives,andrestoresfor on the HostProperties>Clients>Properties>UNIXClient>ClientSettingsdialog box.

Client logging file name format on UNIX clientsA description of logging file name format is available.

117Using logs and reportsDebug logs on UNIX clients

See “Unified logging file name format” on page 86.

See “Legacy logging file name format without log file rotation” on page 111.

How to set logging levels on UNIX clientsTo increase the amount of information that client processes write in the logs, goto the Logging dialog box. (Click Host Properties > Clients > Properties > Loggingdialog box.)

Debug logs on PC clientsMost PC client logs are of the legacy type, with the exception of a few Bare MetalRestore processes, as explained in this section.

Unified logging on PC clientsThe following are Windows client processes that use unified logging:

■ nbftclnt: originator ID 200

■ bmrsavecfg: originator ID 121.

■ bmrc: originator ID 122. bmrc originates from the BMR boot server, which mayor may not be a NetBackup server, and runs on the restoring client.

■ bmrrst.exe and bmrmap.exe: originator ID 131. These originate from the BMRboot server, which may or may not be a NetBackup server, and run on therestoring client.

■ nblbc: originator ID 351. NetBackup Live Browse Client.

■ nbgre: originator ID 352. NetBackup Granular Restore.

■ nbbrowse: originator ID 359. NetBackup Client Browser.

■ nbcs: originator ID 366. Client service.

A discussion of file name format and other unified logging details is available.

See “Unified logging” on page 85.

Unified logging is enabled by default.

Legacy debug logging on PC clientsTo enable detailed legacy debug logging on Microsoft Windows or NetWare targetclients, create the appropriate directories in the following locations:

Using logs and reportsDebug logs on PC clients

118

Note: These are the default locations in which to place these directories. You canspecify another location during client installation.

■ Windows clients - C:\Program Files\VERITAS\NetBackup\Logs\

■ NetWare clients - SYS:VERITAS\NBUCLT\NetBack\logs\

Table 3-7 lists the legacy debug log directories that apply to these clients:

Table 3-7 PC client debug logs: Legacy logging

Associated processNetBackup clientDebug log directory

Client-user interface program forNetWare.

NetWare targetbp

Client service logs. These logshave information on thebpinetd32 process.

Windows2003bpinetd

Archive program that is run fromthe command line.

Windows 2003bparchive

The backup program that is runfrom the command line.

Windows 2003bpbackup

Backup and archive manager.These logs have information onthe bpbkar32 process.

Windows 2003bpbkar

NetBackup client daemon ormanager. These logs haveinformation on communicationsbetween the server and client. OnNetWare clients, these logs alsocontain the log information forthe backup and restore processes.

All Windows and NetWareclients

bpcd

bpjava-msvcThe NetBackup-Javaapplication serverauthentication service that theClient Services servicestarts during startup of theNetBackup Java interfaceapplications. This programauthenticates the user thatstarted the application. (On allWindows platforms.)

bpjava-msvc

119Using logs and reportsDebug logs on PC clients

Table 3-7 PC client debug logs: Legacy logging (continued)

Associated processNetBackup clientDebug log directory

bpjava-usvcNetBackup program thatbpjava-msvc starts uponsuccessful login through theLogin dialog box that ispresented when aNetBackup-Java interface isstarted. This program servicesall requests from the Javaadministration and userinterfaces on the NetBackuphost where bpjava-msvc isrunning.(On all Windowsplatforms.)

bpjava-usvc

List program that is run from thecommand line.

Windows 2003bplist

The program that is used tocollect drive names on the clientfor multistreaming clients.

Windows 2003bpmount

The restore program that is runfrom the command line.

Windows 2003bprestore

NetBackup service utility. Thisprogram allows the system withthe user interface tocommunicate with the NetBackupfor NetWare client.

NetWare nontargetbpsrv

tar process. These logs haveinformation about the tar32process.

Windows 2003tar

Using logs and reportsDebug logs on PC clients

120

Table 3-7 PC client debug logs: Legacy logging (continued)

Associated processNetBackup clientDebug log directory

The user_ops directory iscreated during the install ofNetBackup on all servers andclients. The NetBackup Javainterface programs use it for thefollowing: temporary files and forjob and progress log files that theuser backup, archive, and restoreprogram (jbpSA) generates. Thisdirectory must exist forsuccessful operation of any of theJava programs and must havepublic read, write, and runpermissions.user_ops containsa directory for every user thatuses the Java programs.

In addition, on NetBackup-Javacapable platforms, the NetBackupJava interface log files are writtenin a subdirectory that is callednbjlogs. All files in theuser_ops directory hierarchyare removed according to thesetting of the KEEP_LOGS_DAYSconfiguration option.

Windows 2003user_ops

Controlling log size on PC clientsFor the unified logging files that the Bare Metal Restore process bmrsavecfgcreates, you can control logging with log file rotation.

See “Unified logging file rollover” on page 93.

For the legacy logging files that the bpbkar and the bpcd processes create, youcan control logging with log file rotation.

See “Legacy logging file rotation (robust logging)” on page 109.

For all other client logs, note the following:

■ For Windows clients, logs are kept for the number of days that are specifiedin the Backup, Archive, and Restore interface. On the File menu, clickNetBackup Client Properties > General tab: Keep status of user-directedbackups, archives, and restores for.

121Using logs and reportsDebug logs on PC clients

■ For NetWare clients, logs are kept the number of days that are specified in file\veritas\nbuclt\netback\bp.ini (under Keep_Logs_Days).

Client logging file name format on PC clientsA description of logging file name format is available.

See “Unified logging file name format” on page 86.

See “Legacy logging file name format without log file rotation” on page 111.

How to set logging levels on PC clientsTo increase the amount of information that client processes write in the logs:

■ On Windows clients, set the debug level with the Verbose field on theTroubleShooting tab of the NetBackup Client Properties dialog box. On theBackup, Archive, and Restore interface, click File > NetBackup Client Properties.

■ For the unified logging files that the Bare Metal Restore process bmrsavecfgcreates, you also can control logging level with the vxlogcfg command.

See “Configuring and using unified logging” on page 94.

■ On NetWare clients, change the value of the level and the tcp parameters inthe debug section of the bp.ini file. For instructions, see the NetBackup userguide for the client.An increase in the log level can cause the logs to grow very large; increase thelogging level only if unexplained problems exist.

Windows Event Viewer logging optionNetBackup Windows master servers can be configured so messages fromNetBackup reports are written to the Windows Event Viewer Application Log. Youcan see these messages in the Application Log and also use third party tools tomonitor the Application Log for these messages.

To route unified logging application and diagnostic messages for an originatorto the Application Log, set the "LogToOslog" value to true for that originator.

For example, execute the following to route the application and diagnosticmessages for nbrb to the Windows event log:

vxlogcfg -a -o nbrb -p NB -s "LogToOslog=true"

Note: For this setting to be effective, restart NetBackup services.

Using logs and reportsWindows Event Viewer logging option

122

Enabling the logging toolThis topic shows you how to enable the logging tool.

To enable the logging tool

1 Create the following file on the NetBackup master server:

install_path\NetBackup\db\config\eventlog

2 Add an entry (optional) to the eventlog file that specifies the severity andtype of NetBackup messages that are written. The following is an example:

56 255

eventlog file entriesThe eventlog entry has the following two parameters:

■ The first parameter controls the messages that NetBackup writes to theApplication Log, which are based on severity level.

■ The second parameter controls the type of messages that NetBackup writesto the Application Log.

Both parameters are specified as decimal numbers and equate to a bitmap thatexpresses these values.

Severity:

1 = Unknown

2 = Debug

4 = Info

8 = Warning

16 = Error

32 = Critical

Type:

1 = Unknown

2 = General

4 = Backup

123Using logs and reportsWindows Event Viewer logging option

8 = Archive

16 = Retrieve

32 = Security

64 = Backup Status

128 = MediaDevice

If the file is empty, the default severity is Error (16) and the default type is BackupStatus (64).

If the file has only one parameter, it is used for the severity level. The defaultvalue of Backup Status (64) is used for the type.

ExampleAssume you want to include all types of messages that have severity levels ofwarning, error, and critical. In this instance, the entry is:

56 255

Where:

56 = severity= the sum of warning, error, and critical (8 + 16 + 32)

255 = type = the sum of all types (1 + 2 + 4 + 8 + 16 + 32 + 64 +128)

The following is an example of a message that is written in the Windows EventViewer Application Log:

16 4 10797 -1 cacao bush nbpem backup of client bush exited with

status 71

The meaning of each field is as follows (left to right):

severity = 16 (Error)

type = 4 (Backup)

jobid = 10797

job group ID = 1

server = cacao

client = bush

process = nbpem

text = backup of client bush, which exited with status 71

Using logs and reportsWindows Event Viewer logging option

124

Troubleshooting theAdministrationConsole for UNIXMost errors in the NetBackup Administration Console for UNIX appear in thefollowing: an attention dialog box or in an error message pane in the lower rightarea of the console. If they appear elsewhere, they are Java exception errors, whichare not documented in this guide. They may appear in the status line (bottom) ofthe NetBackup Administration window. They also may appear in the log file thatcontains the stdout or the stderr messages that Java APIs or the NetBackupAdministration Console write.

The following are the four kinds of error messages that appear in the NetBackupAdministration Console:

■ NetBackup status codes and messages.See “About NetBackup status codes and messages” on page 155.See “About media and device management status codes and messages”on page 423.Operations performed in the Administration Console can result in errors thatare recognized in other parts of NetBackup.These errors usually appear exactly as documented in the NetBackup statuscodes and messages.

Note: A status code does not always accompany the error message.

To find the status code, look up the message in the alphabetical listing of thefollowing topicSee “NetBackup Messages” on page 397.Then use the status code to find the full description of the message in the firsthalf of that chapter.

■ NetBackup Administration Console: application server status codes andmessages.See “About NetBackup status codes and messages” on page 155.These messages have status codes in the 500 range. Messages with status codes500, 501, 502, 503 and 504 begin with "Unable to login, status:". Messages withstatus codes 511 and 512 may or may not begin with "Unable to login, status:".A status code does not always accompany the message (see note).

■ Java exceptionsEither the Java APIs or NetBackup Administration APIs generate these. Thesemessages begin with the name of the exception. For example:

java.lang.ClassCastException

125Using logs and reportsTroubleshooting the Administration Console for UNIX

or

vrts.nbu.NBUCommandExecutionException

Java exceptions usually appear in one of the following three places:

■ In the status line (bottom) of the NetBackup Administration window

■ In the log file generated by the jnbSA or jbpSA commands

■ When it is set up, in the output file of the Windows Display Console .bat

file. More information is available about detailed debug logging.See “Enabling detailed debug logging” on page 127.

■ Operating system errorsIf messages appear that do not match those documented in this manual, theyprobably are errors in the operating system.

Required disk space for logging and temporary filesThe Administration Console requires disk space in the following locations forsuccessful operation:

■ On the host that is specified in the login dialog box

■ In /usr/openv/netbackup/logs/user_ops

■ On the host where the Console was started

■ In /usr/openv/netbackup/logs/user_ops/nbjlogs

If space is not available in the respective file systems, you may experience thefollowing: long waits for application response, incomplete data, reducedfunctionality, and unexpected error messages.

The following are some of the results you may receive:

■ No response during login

■ "Cannot connect" socket errors during login to the NBJava application server

■ Reduced functionality in the NetBackup interface, for example, only the Backup,Archive, and Restore and Files System Analyzer nodes appear in the tree

■ An error dialog box with the "Unable to login, status: 35 cannot make requireddirectory" message

■ An error dialog box with "/bin/sh: null: not found (1) "message

■ Empty warning dialog boxes

Using logs and reportsTroubleshooting the Administration Console for UNIX

126

■ An error dialog box with the message "An exception occurred:vrts.nbu.admin.bpmgmt.CommandOutputException: Invalid or unexpectedclass configuration data: <the rest of the message will vary>"

Enabling detailed debug loggingThe NetBackup Administration Console is a distributed application that allowsadministration of remote NetBackup servers. All administration is accomplishedthrough the application server of the NetBackup Administration Console. Thisapplication server is made up of an authentication service and a user service.

The login request from the login dialog box is sent to the authentication servicefor validation. The user name and password have to be valid in the Windows/UNIXauthentication files and process.

After validation, the authentication service starts a user service under the user’saccount. Thereafter, all NetBackup administrative tasks are performed throughan instance of the user service. Additional user service processes are initiated toprocess requests from the Console.

On both UNIX and Windows, the authentication service is the bpjava-msvc

application and the user service is the bpjava-susvc or bpjava-usvc application.

To enable detailed debug logging

1 On the NetBackup client or server that is specified in the login dialog box,create the following: bpjava-msvc, bpjava-susvc (if a NetBackup server),and bpjava-usvc (if a NetBackup client) debug log directories in the/usr/openv/netbackup/logs directory (UNIX) or ininstall_path\NetBackup\logs (Windows). For more information on debuglogs, see the following:

See “Debug logs on servers” on page 85.

2 On the UNIX machine where you run the jnbSA or jbpSA commands, add thefollowing line to theDebug.properties file in the/usr/openv/javadirectory.

debugMask=2

The log file name is displayed in the xterm window where you ran the jnbSAor jbpSA commands.

127Using logs and reportsTroubleshooting the Administration Console for UNIX

3 If you use the NetBackup Java Windows Display Console, add the followingline to the Debug.properties file in the NetBackup Java installed folder (forexample, C:install_path\VERITAS\java):

debugMask=2

4 If you use the Windows Display Console on a host where NetBackup is notinstalled, you have to do the following: edit the nbjava.bat file located in theNetBackup Java-installed folder to redirect output to a file. See the nbjava.batfile for details.

Query string overviewFollowing are details on the -w (- -where) QueryString option on the vxlogviewcommand for unified logging.

Query string is a text expression similar to a database WHERE clause that is usedto retrieve log entries from the unified logging system. The expression is acombination of relational operators, constant integers, constant strings, andnames of log fields that evaluate to a single value. Expressions are grouped by thelogical operators such as AND and OR.

Query String Syntax

The supported relational operators are as follows:

< less than

> greater than

<= less than and equal to

>= greater than and equal to

= equal to

!= not equal to

The supported logical operators are as follows:

&& logical AND

|| logical OR

Data types for fieldsTable 3-8 shows data types for fields with a description and an example.

Using logs and reportsQuery string overview

128

Table 3-8 Data types

ExampleDescriptionTypeField name

PRODID = 100 or PRODID = 'NBU'Provide the product ID or theabbreviated name of product.

Integer or stringPRODID or prodid

ORGID = 1 or ORGID = 'VxAM'Provide the originator ID or theabbreviated name of thecomponent.

Integer or stringORGID or orgid

PID = 1234567Provide the process IDLong IntegerPID or pid

TID = 2874950Provide the thread IDLong IntegerTID or tid

STDATE = 98736352 or STDATE ='4/26/04 11:01:00 AM'

Provide the start date in seconds orin the locale specific short date andtime format. For example, a localemay have format 'mm/dd/yyhh:mm:ss AM/PM'

Long Integer orstring

STDATE or stdate

ENDATE = 99736352 or ENDATE ='04/27/04 10:01:00 AM'

Provide the end date in seconds orin the locale specific short date andtime format. For example, a localemay have format 'mm/dd/yyhh:mm:ss AM/PM'

Long Integer orstring

ENDATE or stdate

PREVTIME = '2:34:00'Provide the hours in 'hh:mm:ss'format. This field should be usedonly with operators =, <, >, >= and<=

StringPREVTIME orprevtime

SEV = 0 or SEV = INFOProvide one of the followingpossible severity types:

■ INFO or info

■ WARNING or warning

■ ERR or err

■ CRIT or crit

■ EMERG or emerg

IntegerSEV or sev

129Using logs and reportsQuery string overview

Table 3-8 Data types (continued)

ExampleDescriptionTypeField name

MSGTYPE = 1 or MSGTYPE = DIAGProvide one of the followingpossible message types:

■ DEBUG or debug - debugmessages

■ DIAG or diag - diagnosticmessages

■ APP or app - applicationmessages

■ CTX or ctx - context messages.

■ AUDIT or audit - audit messages

IntegerMSGTYPE ormsgtype

CTX = 78 or CTX = 'ALL'Provide the context token as stringidentifier or 'ALL' to get all thecontext instances to be displayed.This field should be used only withthe operators = and !=.

Integer or stringCTX or ctx

String constantsString constants should be given in single quotes. For example, prodid = 'NBU'

Start and end date can be provided as follows: either as a string constant of theregional display short date format or a long value of number of seconds thatelapsed since midnight January 1, 1970.

Query string examplesThe following are some query string examples:

1. (PRODID == 100) && ((PID == 178964) || ((STDATE == '2/5/03

00:00:00 AM') && (ENDATE == '2/5/03 12:00:00 PM'))

2. ((prodid = 'NBU') && ((stdate >= ‘11/18/03 0:0:0 AM’) && (endate

<= ‘12/13/03 13:0:0 AM’))) || ((prodid = 'BENT') && ((stdate >=

‘12/12/03 0:0:0 AM’) && (endate <= ‘12/25/03 25:0:0 PM’)))

3. (STDATE <= ‘04/05/03 0:0:0 AM’) - This query will retrieve log

messages, which are logged on or before 2003-05-04 for all the

installed Symantec products.

Using logs and reportsQuery string overview

130

Using NetBackup utilities

This chapter includes the following topics:

■ About using NetBackup utilities

■ Analysis utilities for NetBackup debug logs

■ Network troubleshooting utilities

■ NetBackup support utility (nbsu)

■ NetBackup consistency check (NBCC)

■ NetBackup consistency check repair (NBCCR)

■ The nbcplogs utility

About using NetBackup utilitiesSeveral utilities are available to help diagnose NetBackup problems. The AnalysisUtilities for NetBackup debug logs and the NetBackup Support Utility (nbsu) areespecially useful in troubleshooting.

Analysis utilities for NetBackup debug logsThe debug log analysis utilities enhance NetBackup’s existing debug capabilitiesby providing a consolidated view of a job debug log.

NetBackup jobs span multiple processes that are distributed across servers.

A description of the two kinds of logging that are used, legacy logging and unifiedlogging, is available.

See “About using logs and reports” on page 81.

4Chapter

To trace a NetBackup job requires that you view and correlate messages in multiplelog files on multiple hosts. The log analysis utilities provide a consolidated viewof the job debug logs. The utilities scan the logs for all processes that are traversedor run for the job. The utilities can consolidate job information by client, job ID,start time for the job, and policy that is associated with the job.

The available utilities are as follows:

■ backuptrace copies to standard output the debug log lines relevant to thespecified backup jobs, including online (hot) catalog backups

■ restoretrace copies to standard output the debug log lines relevant to thespecified restore jobs

■ bpgetdebuglog is a helper program for backuptrace and restoretrace

■ duplicatetrace consolidates the debug logs for the specified NetBackupduplicate jobs and writes them to standard output.

■ importtrace consolidates the debug log messages for the specified NetBackupimport jobs and writes them to standard output.

■ verifytrace consolidates the debug log messages for the specified verify job(s)and writes them to standard output.

Installation requirementsThe log analysis utilities are available for all platforms that are supported forNetBackup servers.

Note: Though the utilities must be initiated on supported platforms, they cananalyze debug log files from most NetBackup UNIX and Windows client and serverplatforms.

Output formatThe format of an output line is as follows:

daystamp.millisecs.program.sequence machine log_line

The following is a short description of each part of the outline line format:

The day of the log in yyyymmdd format.daystamp

The number of milliseconds since midnight on the local machine.millisecs

The name of program (BPCD, BPRD, etc.) being logged.program

Using NetBackup utilitiesAnalysis utilities for NetBackup debug logs

132

Line number within the debug log file.sequence

The name of the NetBackup server or client.machine

The line that appears in the debug log file.log_line

LimitationsWhile the log analysis utilities cover a variety of logs, the following exceptionsoccur:

■ Media and device management logs are not analyzed.

■ The legacy debug log files must be in standard locations on the servers andclients./usr/openv/netbackup/logs/<PROGRAM_NAME>/log.mmddyy on UNIX and<install_path>/NetBackup/Logs/<PROGRAM_NAME>/mmddyy.logon Windows.An option may be added later that allows the analyzed log files to reside onalternate paths.

Note: For the processes that use unified logging, no log directories must becreated.

■ The consolidated debug log may contain messages from unrelated processes.You can ignore messages with time stamps outside the duration of the jobfrom the following: bprd, nbpem, nbjm, nbrb, bpdbm, bpbrm, bptm, bpdm, andbpcd.

How to run the log analysis utilitiesThis section describes each utility and the conditions for using it. For eachcommand’s parameters, limitations, and examples of use, use the command withthe -help option. All the following commands require administrative privileges.

See the NetBackup Commands manual.

Table 4-1 is a description of each log analysis utility.

133Using NetBackup utilitiesAnalysis utilities for NetBackup debug logs

Table 4-1 Log analysis utilities

The backuptrace utility can be used for regular file system,database extension, and alternate backup method backup jobs. Itconsolidates the debug logs for specified NetBackup jobs. Theutility writes the relevant debug log messages to standard outputand sorts the messages by time. backuptrace attempts tocompensate for time zone changes and clock drift between remoteservers and clients. The format of the output makes it relativelyeasy to sort or grep by time stamp, program name, and server orclient name.

Thebackuptrace utility works with thenbpem,nbjm, andnbrblogs on the master server. You should enable debug logging forbpbrm and bptm or bpdm on the media server and for bpbkar onthe client. For best results, set the verbose logging level to 5.Enable debug logging for the following: bpdbm and bprd on themaster server and for bpcd on all servers and clients in additionto the processes already identified.

backuptrace

restoretrace consolidates the debug logs for specifiedNetBackup restore jobs. The utility writes debug log messagesrelevant to the specified jobs to standard output and sorts themessages by time. restoretrace attempts to compensate fortime zone changes and clock drift between remote servers andclients. The format of the output makes it relatively easy to sortor grep by time stamp, program name, and server or client name.

At a minimum, you must enable debug logging for bprd on themaster server. Enable debug logging forbpbrm andbptm orbpdmon the media server and tar on the client. For best results, setthe verbose logging level to 5. Enable debug logging for bpdbm onthe master server and for bpcd on all servers and clients.

restoretrace

bpgetdebuglog is a helper program for backuptrace andrestoretrace. It can also be useful as a stand-alone programand is available for all NetBackup server platforms.bpgetdebuglog prints to standard output the contents of aspecified debug log file. If only the remote machine parameter isspecified, bpgetdebuglog prints the following to standardoutput: the number of seconds of clock drift between the localmachine and the remote machine.

bpgetdebuglog

Using NetBackup utilitiesAnalysis utilities for NetBackup debug logs

134

Table 4-1 Log analysis utilities (continued)

backupdbtrace consolidates the debug log messages for specifiedNetBackup database backup jobs and writes them to standardoutput. It sorts the messages by time. backupdbtrace attemptsto compensate for time zone changes and clock drift betweenremote servers and clients.

At a minimum, you must enable debug logging for admin on themaster server, and forbptm andbpbkar on the media server. Forbest results, set the verbose logging level to 5 and enable debuglogging for the following: bpdbm on the master server and bpcdon all servers in addition to the processes already identified.

backupdbtrace

duplicatetrace consolidates the debug logs for the specifiedNetBackup duplicate jobs and writes them to standard output. Itsorts the messages by time. duplicatetrace attempts tocompensate for time zone changes and clock drift between remoteservers and clients.

At a minimum, you must enable debug logging for admin on themaster server and for bptm or bpdm on the media server. For bestresults, set the verbose logging level to 5 and enable debug loggingfor the following: bpdbm on the master server and bpcd on allservers and clients in addition to the processes already identified.

duplicatetrace

importtrace consolidates the debug log messages for thespecified NetBackup import jobs and writes them to standardoutput. It sorts the messages by time. importtrace attempts tocompensate for time zone changes and clock drift between remoteservers and clients.

At a minimum, you must enable debug logging for admin on themaster server, and for bpbrm, bptm and tar on the media server.For best results, set the verbose logging level to 5 and enable debuglogging for the following: bpdbm on the master server and bpcdon all servers and clients in addition to the processes alreadyidentified.

importtrace

135Using NetBackup utilitiesAnalysis utilities for NetBackup debug logs

Table 4-1 Log analysis utilities (continued)

verifytrace consolidates the debug log messages for thespecified verify job[s] and writes them to standard output. It sortsthe messages by time. verifytrace attempts to compensate fortime zone changes and clock drift between remote servers andclients.

At a minimum, you must enable debug logging as follows: foradmin on the master server and for bpbrm, bptm (or bpdm) andtar on the media server. For best results, set the verbose logginglevel to 5 and enable debug logging for the following: bpdbm onthe master server and bpcd on all servers and clients in additionto the processes already identified.

verifytrace

Network troubleshooting utilitiesA set of utility programs (commands) verifies various aspects of networkconfiguration inside and outside NetBackup to ensure that there is nomisconfiguration. The utilities also provide user-friendly messages for any errorsthey find.

Network configuration broadly falls into two categories:

■ Hardware, operating system, and NetBackup level settings. Examples includecorrect DNS lookups, firewall port openings, and network routes andconnections. The NetBackup Domain Network Analyzer (nbdna) verifies thisconfiguration.

■ A set of utilities including bptestcd and bptestnetconn verifies the NetBackuplevel settings. These settings include CONNECT_OPTIONS and CORBA endpointselection.

Table 4-2 Network configuration utilities

The bptestnetconn command performs several tasks that aid inthe analysis of DNS and connectivity problems with any specifiedlist of hosts, including the server list in the NetBackupconfiguration. To help troubleshoot connectivity problemsbetween services that use CORBA communications, bptestnetconncan perform and report on CORBA connections to named services.

bptestnetconn

The bptestbpcd command tries to establish a connection from aNetBackup server to the bpcd daemon on another NetBackupsystem. If successful, it reports information about the sockets thatare established.

bptestbpcd

Using NetBackup utilitiesNetwork troubleshooting utilities

136

Table 4-2 Network configuration utilities (continued)

Network connectivity evaluation in a NetBackup domain is difficultbecause NetBackup domains can scale to hundreds of servers, andthousands of clients across complex network topologies.

The NetBackup Domain Network Analyzer (nbdna) evaluateshostnames in the NetBackup Domain. The nbdna utilityself-discovers the NetBackup domain and evaluates hostnameinformation, then tests connectivity to these hostnames andvalidates their network relationship status.

nbdna

For more information on these utilities, refer to the Commands manual.

NetBackup support utility (nbsu)The NetBackup support utility (nbsu) is a command line tool. It queries the hostand gathers appropriate diagnostic information about NetBackup and the operatingsystem. nbsu provides a wide range of control over the types of diagnosticinformation gathered. For instance, you can obtain information about NetBackupconfiguration settings, about specific troubleshooting areas, or about NetBackupor media management job status codes.

nbsu resides in the following location:

■ On UNIX: /usr/openv/netbackup/bin/support/nbsu

■ On Windows: install_path\NetBackup\bin\support\nbsu.exe

For a description of the nbsu command options, refer to the nbsu man page. Moreinformation is available.

See the NetBackup Commands manual.

When to use nbsuSymantec recommends that you run nbsu in the following circumstances:

■ To obtain baseline data on your NetBackup installation. If you encounterproblems later, this data can be useful.

■ To document changes in your NetBackup or operating system environment.Run nbsu periodically to keep your baseline data up to date.

■ To help isolate a NetBackup or operating system issue.

■ To report issues to Symantec support.

137Using NetBackup utilitiesNetBackup support utility (nbsu)

nbsu progress displayBy default, nbsu displays its progress to standard output. First it lists environmentqueries; then it lists the diagnostic commands that it runs.

Example nbsu output:

C:\Program Files\VERITAS\NetBackup\bin\support>nbsu

1.0 Determining initial nbsu settings

1.1 Determining OS environment

1.2 Determining OS host services

1.3 Determining identified network interface hostnames

1.4 Determining NetBackup environment

2.0 Querying nbsu diagnostic lists

2.1 Determining nbsu diagnostics to run

3.0 Executing nbsu diagnostics

Executing diagnostic DEV_scsi_reg

Registry query of HKEY_LOCAL_MACHINE\hardware\DeviceMap\Scsi\

Executing diagnostic MM_ndmp

"C:\Program Files\VERITAS\volmgr\bin\set_ndmp_attr" -list

"C:\Program Files\VERITAS\volmgr\bin\set_ndmp_attr" -probe

<hostname>

"C:\Program Files\VERITAS\volmgr\bin\set_ndmp_attr" -verify

<hostname>

Executing diagnostic MM_tpconfig

"C:\Program Files\VERITAS\\Volmgr\Bin\tpconfig" -d

4.0 nbsu successfully completed the identified diagnostic commands.

Creating support package...

Microsoft (R) Cabinet Maker - Version 5.2.3790.0

Copyright (c) Microsoft Corporation. All rights reserved..

770,201 bytes in 36 files

Total files: 36

Bytes before: 770,201

Bytes after: 105,503

After/Before: 13.70% compression

Time: 0.67 seconds ( 0 hr 0 min 0.67 sec)

Throughput: 1119.27 Kb/second

Cleaning up output files...

Using NetBackup utilitiesNetBackup support utility (nbsu)

138

The results are located in the

.\output\nbsu\lou4_master_20070409_160403 directory...

nbsu outputnbsu writes the information it gathers to text files in the following directory:

On UNIX:

/usr/openv/netbackup/bin/support/output/nbsu/hostname_timestamp

On Windows:

install_path\NetBackup\bin\support\output\nbsu\hostname_timestamp

The NetBackup environment where nbsu runs determines the particular files thatnbsu creates. nbsu runs only those diagnostic commands that are appropriate tothe operating system and the NetBackup version and configuration. For eachdiagnostic command that it runs, nbsu writes the command output to a separatefile. As a rule, the name of each output file reflects the command that nbsu ranto obtain the output. For example, nbsu created the NBU_bpplclients.txt byrunning the NetBackup bpplclients command and created the OS_set.txt fileby running the operating system’s set command.

Output files: formatEach output file begins with a header that identifies the command(s) that nbsuran. If output from more than one command was included in the file, the headeridentifies the output as an "internal procedure."

Figure 4-1 shows the actual command(s) and output follow the header.

Figure 4-1 Example nbsu output file: ipconfig command (excerpt)

--------------------- Network ipconfig information report --------------

------------------------------ Command used ----------------------------

> "C:\WINDOWS\system32\ipconfig" /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : host1

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : company.com

139Using NetBackup utilitiesNetBackup support utility (nbsu)

Figure 4-2 shows an example of part of the nbsu output file for the bpgetconfigcommand.

Figure 4-2 Example nbsu output file: bpgetconfig command (excerpt)

------------------ NetBackup bpgetconfig information report ----------------------------- nbsu diagnostic name and internal procedure used -------------NBU_bpgetconfig - NBU_get_bpgetconfig_info------------------------------- Command Used -------------------------------> "C:\Program Files\VERITAS\netbackup\bin\admincmd\bpgetconfig" -g host1 -LClient/Master = MasterNetBackup Client Platform = PC, Windows2000NetBackup Client Protocol Level = 6.5.0Product = NetBackupVersion Name = 6.5AlphaVersion Number = 650000NetBackup Installation Path = C:\Program Files\VERITAS\NetBackup\binClient OS/Release = Windows2003 5------------------------------- Command Used -------------------------------> "C:\Program Files\VERITAS\netbackup\bin\admincmd\bpgetconfig"SERVER = host1SERVER = host2SERVER = host3SERVER = host4SERVER = host5SERVER = host6SERVER = host7

If the executed command returned a non-zero status, an EXIT STATUS headerindicates the status. For example:

----------------------- EXIT STATUS = 227 -------------------------

As part of the internal processing of each command that a diagnostic commandruns, nbsu redirects each command’s STDERR to an internal file. If the commandwrites information to STDERR, nbsu captures this information and includes aSTDERR header along with the information. For example:

----------------------------- STDERR ------------------------------

bpclient: no entity was found (227)

Output files: archiving and compressionIf a supported archive program is available on the host where nbsu runs, nbsubundles its output files into an archive file. If a supported compression utility isavailable, nbsu compresses the archive file. Otherwise, the individual output filesremain unarchived and uncompressed.

An example of a compressed archive file that nbsu created is as follows:

Using NetBackup utilitiesNetBackup support utility (nbsu)

140

/usr/openv/netbackup/bin/support/output/nbsu/host1_master_20060814_

164443/host1_master_20060814_164443.tar.gz

where host1 is the name of the host on which nbsu ran.master indicates that thehost is a NetBackup master server.

nbsu supports tar for archive and gzip for compression. Symantec may add supportfor other archive and compression utilities in the future. For an up-to-date list ofsupported archive and compression utilities, run the nbsu -H command on yourinstalled version of NetBackup.

Note:Archiving and compression utilities are usually available on UNIX and Linuxsystems. On Windows, it may be necessary to install these programs. Note thatthe archiving utility must be referenced in the system PATH environment variable.

Archiving by means of nbsu -xmlIf no archive utility is installed on your system, do the following: use the -xmloption of the nbsu command to create a single .xml file in place of the individualoutput files. The single .xml file contains all the diagnostic information that theindividual files contain. Use this command to conveniently bundle nbsu outputfor Symantec support.

nbsu and NetBackup status codesYou can use nbsu to gather diagnostic information about certain NetBackup orMedia Manager status codes. nbsu gathers this information by running one ormore NetBackup commands whose output may indicate the cause of the problem.

The commands that nbsu runs may be mentioned under "Recommended Actions"for a particular status code in either of the following: See “About NetBackup statuscodes and messages” on page 155.

See “About media and device management status codes and messages” on page 423.

For example, to gather diagnostic information about status code 25, enter:

nbsu -nbu_e 25

This command runs only the diagnostic commands that are related to NetBackupstatus code 25. Since fewer commands are run, the result may be a smaller set ofoutput files.

A description of the output files that nbsu generates is available.

See “Output files: format” on page 139.

141Using NetBackup utilitiesNetBackup support utility (nbsu)

To determine what information nbsu can collect for a particular status code, runnbsu with the -l option:

nbsu -l -nbu_e 25

Note: You can also use a NetBackup exit script to call nbsu. The script passes theNetBackup status code to nbsu to gather associated diagnostics for a job.

Notes on running nbsuThe following are items that can help you run the nbsu utility:

■ For an nbsu description, examples, and how to gather diagnostic informationto send to Symantec support, refer to the nbsu command.See the NetBackup Commands manual.

■ For troubleshooting, run nbsu when the system is in the same state as whenthe problem occurred. For example, do not stop and restart the NetBackupprocesses after the error occurs or make a change to the server or network.nbsu may not be able to gather key information about the problem.

■ If a NetBackup component is not operational (for example, bpgetconfig doesnot return information), nbsumay be unable to properly report on the system.For these cases, use the -nbu_down command line option to bypass the needfor NetBackup to be operational.For a full description of the –nbu_down command line option, see theNetBackup Commands manual.

If you encounter problems running nbsuIf nbsu does not perform as expected, try the following:

■ By default, nbsu sends error messages to standard error (STDERR) and alsoincludes the messages in its output files under the header STDERR. Note thefollowing alternate ways to view nbsu error messages:

■ To redirect the nbsu error messages to standard output (STDOUT), enterthe following:

■ On UNIX: /usr/openv/netbackup/bin/support/nbsu 2>&1

■ On Windows: install_path\NetBackup\bin\support\nbsu.exe 2>&1

■ To send all nbsu screen output including error messages to a file, enter:

nbsu 2>&1 > file_name

Using NetBackup utilitiesNetBackup support utility (nbsu)

142

where 2>&1 directs standard error into standard output, and file_name

directs standard output into the designated file.

■ To generate debug messages that relate to nbsu, enter:

# nbsu -debug

The messages are written to the nbsu_info.txt file. Information is availableabout the location of this file.See “nbsu output” on page 139.

nbsu_info.txt fileThe nbsu_info.txt file provides an overview of the environment where nbsu isrun, and contains the following:

■ General operating system and NetBackup information on the environmentthat nbsu detects

■ A list of diagnostics that were run

■ A list of diagnostics that returned a non-zero status

This information may indicate why nbsu returned particular values, or why it didnot run certain commands.

If nbsu does not produce adequate information or if it seems to perform incorrectly,do the following: run nbsu with the -debug option to include additional debugmessages in the nbsu_info.txt file.

NetBackup consistency check (NBCC)NBCC is a command line utility that is used to analyze the integrity of portionsof the NetBackup configuration and catalog/database information as they pertainto tape media. This analysis includes review of NetBackup storage units, the EMMserver, volume pools, tape media, and backup images associated with tape media.

NBCC does the following:

■ Queries the operating system for configured Host Services and creates/readsthe nbcc-server-aliases file for hostname normalization

■ Through examination of the NetBackup configuration, identifies potentiallytape based NetBackup media servers

■ Gathers database/catalog information

■ Analyzes the consistency of the gathered configuration and database/cataloginformation

143Using NetBackup utilitiesNetBackup consistency check (NBCC)

■ Creates a packaged bundle for Symantec Technical Support review

NBCC resides in the following location:

■ On UNIX: /usr/openv/netbackup/bin/support/NBCC

■ On Windows: install_path\NetBackup\bin\support\NBCC.exe

For a description of the NBCC command options, refer to the NBCC man page.More information is available.

See the NetBackup Commands manual.

When to use NBCCSymantec recommends that you run NBCC in the following circumstances:

■ To check the consistency of the NetBackup configuration and catalog/databaseinformation from a tape media perspective

■ To gather and create a package bundle when directed to do so by SymantecTechnical Support

NBCC progress displayBy default, NBCC displays its progress numerically to standard output.

Example NBCC output that has been edited for brevity:

1.0 Gathering initial NBCC information

1.1 Querying configured network interfaces

1.2 Building hostname services information

...

1.3 Obtaining initial NetBackup configuration information

...

If NBCC DOES NOT detect any catalog inconsistencies, would you

like NBCC to create a support package? [Y/y,N/n] Y

2.0 Gathering required NetBackup configuration information

Is the master server or any media server in

a fail-over cluster? [Y/y,N/n] N

Would you like NBCC to update the

D:\Program Files\VERITAS\NetBackup\bin\support\config\

nbcc-server-aliases file with additional hostnames and/or IP

addresses that are detected during processing? [Y/y,N/n] Y

Using NetBackup utilitiesNetBackup consistency check (NBCC)

144

Would you like to verify each addition prior to the update?

[Y/y,N/n] N

If NBCC is unable to determine the NetBackup version for ANY

detected media server, is there a SINGLE version of NetBackup

you would like associated to these media servers? [Y/y,N/n] Y

Please enter the NetBackup primary version number [3,4,5,6] 6

2.1 Reading the initial list of IP addresses and associated hostnames

from the D:\Program Files\VERITAS\NetBackup\bin\support\config\

nbcc-server-aliases file

2.2 Verifying the IP addresses and hostnames contained in the

D:\Program Files\VERITAS\NetBackup\bin\support\config\

nbcc-server-aliases file

2.3 Pinging primary hostnames...

2.4 Building NetBackup retention level list...

2.5 Building NetBackup storage unit list...

2.6 Obtaining EMM server names...

2.7 Obtaining tpconfig NDMP configuration information...

The following NDMP Attach hosts were detected in EMM, but are

not active in EMM:

2.8 Obtaining NetBackup unrestricted media sharing status...

Configuration state = NO

2.9 Obtaining NetBackup Media Server Groups...

No Server Groups configured

3.0 Gathering required NetBackup catalog information

Start time = 2009-01-14 12:20:59

3.1 Gathering NetBackup EMM conflict table list

Found 0 EMM conflict records

3.2 Building NetBackup Image database contents list

...

Found 5890 images in the Image database

3.3 Obtaining NetBackup version from media servers

145Using NetBackup utilitiesNetBackup consistency check (NBCC)

3.4 Building EMM database Media and Device configuration

attribute lists

...

Found 212 media records in the EMM database

3.5 Building EMM database Unrestricted Sharing Media attribute lists

Found 0 Unrestricted Sharing media records in the EMM database

3.6 Building the EMM database Volume attribute list...

Getting the EMM database Volume attributes from EMM server

master1 ...

Found 586 Volume attribute records in the EMM database

3.7 Building NetBackup volume pool configuration list

Server master1

3.8 Building NetBackup scratch pool configuration list

Server master1

3.9 Gathering NetBackup EMM merge table list

Found 0 EMM merge table records

Summary of gathered NetBackup catalog information

...

Catalog data gathering took 499 seconds to complete

***WARNING***

** It took more than 60 seconds to collect all of the DB data.

**

** If backups are running, there is a risk that the data collected

** might not be consistent, because the DBs may have been updated

** while the data was being collected.

**

** If backups are running and it is possible, please stop all

** backups and run NBCC again.

**

** If it is not possible to stop all backups, just let

** NBCC complete.

...

4.0 Verifying required catalog components were gathered

5.0 Beginning NetBackup catalog consistency check

Start time = 2009-01-14 12:29:19

5.2 Processing EMM database Volume attribute records, pass 1 (of 2),

586 records to be processed

Processed 586 EMM database Volume attribute records.

Using NetBackup utilitiesNetBackup consistency check (NBCC)

146

5.3 Checking for duplicate EMM server host names in Volume

attribute data

5.4 Processing Image DB, pass 1 (of 2), 5890 to be processed

5890 images processed on pass 1

5.5 Processing EMM database Media attribute records, pass 1 (of 3),

212 records to be processed

Processed 212 EMM database Media attribute records.

5.7 Check for duplicate media server names in the EMM database

Media attribute data

5.8 Processing EMM database Media attribute records, pass 2 (of 3),

212 records to be processed

CONSISTENCY_ERROR Oper_16_4

5.9 NetBackup catalog consistency check completed

End time = 2009-01-14 12:29:21

6.1 Processing detected NetBackup server entries

Summary of NBCC server processing

...

Report complete, closing the

.\output\nbcc\master2_NBCC_20090114_121931\nbcc-info.txt

output file.

Server aliases fileNBCC generates the nbcc-server-aliases file that contains IP addresses and therelated primary and associated alias hostnames. The nbcc-server-aliases file iscreated in the following directory.

On UNIX and Linux:

/usr/openv/netbackup/bin/support/config/

On Windows:

install_path\NetBackup\bin\support\config\

The following example shows a sample server alias file listing.

# This file is used by NBCC as a basis for determining primary and

# associated alias hostnames as described in the NBCC -help output.

#

# List the primary IP address, all secondary IP addresses, the primary

# hostname and all aliases used for the same server by NetBackup in

# bpgetconfig SERVER related entries, storage units and Volume database

# hosts (eg, fully-qualified hostnames, hostnames associated with other

147Using NetBackup utilitiesNetBackup consistency check (NBCC)

# network interfaces on the server, cluster node names) on a single line.

#

#

# Note: Any hostnames that contain upper-case characters are converted

# to lower-case characters by NBCC for processing.

#

# Accurate representation of both primary and secondary IP addresses and

# primary and associated hostnames are important for both the gathering

# and consistency checking of the NetBackup catalog data.

#

# Format of entries in the "nbcc-server-aliases" file:

#

# primary_IP [ secondary_IP ... ] primary_name alias [ alias ... ]

#

# Examples:

#

# ##.##.###.### ##.##.###.## nbserver NBserver nbserver.lab.symantec.com

# ##.##.###.### ##.##.###.## nbmaster-bkup nbmaster zeus zeus-bkup

#

# Any entries that are added to this file must NOT start with a '#'.

#

# All lines starting with a '#' are ignored by NBCC.

#

# Empty lines are ignored by NBCC.

#

10.10.100.10 nbu_server.com nbu_server

10.10.111.10 nbu_server1.com nbu_server1

10.10.112.10 nbu_server2.com nbu_server2

NBCC outputNBCC writes the information it gathers to packaged files in the following directory.

On UNIX and Linux:

/usr/openv/netbackup/bin/support/output/nbcc/hostname_NBCC_timestamp

On Windows:

install_path\NetBackup\bin\support\output\nbcc\hostname_NBCC_timestamp

Output files: archiving and compressionIf a supported archive program is available on the host where NBCC runs, NBCCbundles its output files into an archive file. If a supported compression utility is

Using NetBackup utilitiesNetBackup consistency check (NBCC)

148

available, NBCC compresses the archive file. Otherwise, the individual output filesremain unarchived and uncompressed.

An example of a compressed (UNIX) archive file that NBCC created is as follows:

/usr/openv/netbackup/bin/support/output/NBCC/host1_NBCC_20060814_

164443/host1_NBCC_20060814_164443.tar.gz

where host1 is the name of the host where NBCC had been run.

On UNIX platforms, NBCC supports the tar , compress and gzip utilities for UNIXfile archiving and compression. On Windows platforms, NBCC supports the tar,Makecab and gzip utilities for Windows File archiving and compression.

Notes on running NBCCThe following are items that can help you run the NBCC utility:

■ For an NBCC description, examples, and how to gather NetBackupcatalog/database information to send to Symantec support, refer to the NBCC-help command, or do the following:See the NetBackup Commands manual.

■ NBCC is designed to be run on NetBackup master servers.

■ In some cases, a non-functioning operating system or NetBackup process orservice can prevent NBCC from running properly or completing. As NBCCprogresses through the interrogation of various operating system or NetBackupcomponents, it outputs what it is going to process to STDOUT. As NBCCprocesses catalog/database components, it displays how many records havebeen processed. The number of records processed is in direct relationship tothe size of the catalog/database being processed. If NBCC detects a failure,related information will be output to STDERR. Information to STDOUT orSTDERR are also output to the nbcc-info.txt file (if available).

If you encounter problems running NBCCIf NBCC does not perform as expected, try the following:

■ Use a text editor to look for error notices in the nbcc-into.txt file.

■ By default, NBCC sends error messages to standard error (STDERR) and alsoincludes the messages in its output files under the header STDERR.

■ If NBCC does not produce adequate information or if it seems to performincorrectly, run NBCC with the -debug option to include additional debugmessages in the nbcc-info.txt file.

149Using NetBackup utilitiesNetBackup consistency check (NBCC)

■ For troubleshooting, run NBCC when the system is in the same state as whenthe problem occurred. For example, do not stop and restart the NetBackupprocesses after the error occurs or make a change to the server or network.NBCC may not be able to gather key information about the problem.

nbcc-info.txt fileThe nbcc-info.txt file provides an overview of the environment where NBCC isrun, and contains the following:

■ General operating system and NetBackup configuration information on theenvironment that NBCC detects

■ A copy of the NBCC processing information that was displayed to STDOUT orSTDERR.

This information would indicate the processing that NBCC had done.

The “Processing detected NetBackup server entries” section of the nbcc-info.txtcontains a “Summary of NBCC server processing”. This information summarizesthe results of the processing of detected server entries.

The following example show a successful summary of server processing from thenbcc-info.txt file.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+ Primary and associated alias hostnames: +

+ server_1 +

+ Primary and associated IP addresses: +

+ 100.100.10.1 +

+ Sources: +

+ config_file bpstulist nbemmcmd +

+ MediaDB host = up VolDB host = no Disk STU host = no +

+ Member of Server Group = no +

+ Media server NetBackup version = 6.5 +

+ Primary hostname ping results: +

+ Successful +

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The following example shows a failed summary of server processing from thenbcc-info.txt file.

-----------------------------------------------------------------+

- Primary and associated alias hostnames: +

- server_2 +

- Primary and associated IP addresses: +

- 100.100.10.100 +

Using NetBackup utilitiesNetBackup consistency check (NBCC)

150

- Sources: +

- config_file nbemmcmd +

- MediaDB host = down VolDB host = no Disk STU host = no +

- Member of Server Group = no +

- Media server NetBackup version = 6.X +

- Primary hostname ping results: +

- Failed - No IP address detected +

-----------------------------------------------------------------+

NetBackup consistency check repair (NBCCR)The NetBackup consistency check repair (NBCCR) utility is a command line toolthat processes database-catalog repair actions. It automates the application ofapproved suggested repair actions. Symantec Tech Support analyzes data collectedby the NBCC utility and site-specific configuration information. This analysisresults in the generation of a suggested repair actions (SRA) file. Before NBCCRis run, Tech Support interacts with the customer to determine which repairs areneeded. Undesirable repair actions are deleted or commented out of the SRA file.Each line of the SRA file contains one repair action paired with an associatedparameter.

The NBCCR utility executes each repair action in several stages:

■ Datacollection. NBCCR first collects information required to perform a repair.

■ Repair qualification. Immediately before the suggested repair is applied,NBCCR verifies that the current status of the tape still qualifies for therequested repair. It recognizes that time has passed and the environment mayhave changed since the data was collected. If so, it reports in a history file thatthe repair is not qualified.

■ Repair. Finally, NBCCR performs up to three steps of repair for every repairentry in the SRA file. An element may be modified to enable the repair andsteps may be necessary after the repair. It implements the repairs with provensyntax, so ad hoc scripting occurs. If the repair fails during the repair operation,NBCCR tries to roll back the repair so that the corrective action does notintroduce any new errors.

NBCCR resides in the following location:

■ On UNIX: /usr/openv/netbackup/bin/support/NBCCR

■ On Windows: install_path\NetBackup\bin\support\NBCCR.exe

For a description of the NBCCR command options, refer to the NBCCR man page.More information is available.

See the NetBackup Commands manual.

151Using NetBackup utilitiesNetBackup consistency check repair (NBCCR)

NBCCR filesNBCCR accepts one input file and creates two output files.

■ NBCCR accepts as input the Suggested Repair Action (SRA) file namedNBCCA.SRA.txt. The file resides in the same directory as the utility.

■ NBCCR creates NBCCR.History.txt, a history file of all the repair actionsattempted, and places it in the same directory as the utility.

■ It also creates an output file, NBCCR.output.txt. See the two sample outputfiles that follow.

While the NBCCR utility runs, the following file appears in the same location asthe NBCCR utility:

KeepOnTruckin.txt

To terminate NBCCR while it processes repairs, delete this file. This action causesNBCCR to complete the current repair, then shut down. Any other interruptioncauses undetermined results.

Sample output filesThe following are two sample contents of the NBCCR.output.txt file showing theresults of two MContents repairs. One where all images were found on tape andone where one or more images were not found, on the tape

This sample shows that all images were found on the tape. The MContents repairaction is successful.

MContents for ULT001 MediaServerExpireImagesNotOnTapeFlag

ExpireImagesNotOnTape flag not set

ULT001 MContents - All images in images catalog found on tape

MContents ULT001 status: Success

The following sample show an unsuccessful repair action. NBCCR did not find oneor more images on the tape, so the repair action is not performed.

MContents for ULT000 MediaServerExpireImagesNotOnTapeFlag

ExpireImagesNotOnTape flag not set

Did NOT find Backup ID winmaster_1234315163 Copy 1 AssignTime 2009-02-11 \

01:19:13 (1234315153) on ULT000

Leaving winmaster_1234315163 Copy 1 on ULT000 in ImageDB

ULT000 MContents - One or more images from images catalog NOT found on tape

MContents ULT000 status: ActionFailed

Using NetBackup utilitiesNetBackup consistency check repair (NBCCR)

152

The nbcplogs utilityWhen you troubleshoot a customer problem, you must gather and copy the correctlogs to debug the issue. The log types (NBU, vxul, vm, pbx,...) may be in manyplaces. The process of getting the logs to Symantec support can be difficult andtime consuming.

The nbcplogs utility is intended to simplify the process of copying logs byspecifying the following options:

■ A time frame for the logs.

■ The log types that you want to collect.

■ Bundling and in-transit data compression.

In addition, you can preview the amount of log data to be copied.

More information on the nbcplogs utility is available in the Commands manual.

153Using NetBackup utilitiesThe nbcplogs utility

Using NetBackup utilitiesThe nbcplogs utility

154

NetBackup status codesand messages

This chapter includes the following topics:

■ About NetBackup status codes and messages

About NetBackup status codes and messagesThis chapter lists all the status codes and messages that NetBackup provides.

Codes that relate to Media and device management are available.

See “Media and device management messages” on page 551.

This chapter is divided into two parts:

■ The first section lists the NetBackup status codes in numerical order andincludes an explanation of what occurred along with recommended actions.See “NetBackup status codes” on page 156.

■ The second section lists the same status codes but sorts them alphabeticallyaccording to the message.See “NetBackup Messages” on page 397.

If you see a status code without its associated message text, use the bperror

command to determine the message, its explanation, and recommended action.

On UNIX and Linux systems:

/usr/openv/netbackup/bin/admincmd/bperror -statuscode

nstatuscode [-recommendation]

On Windows systems:

5Chapter

install_path\NetBackup\bin\admincmd\bperror -statuscode

statuscode [-recommendation]

where statuscode is the number of the message.

The following example shows how you use bperror to access error codeinformation:

On UNIX and Linux:/usr/openv/netbackup/bin/admincmd/bperror -statuscode

150

On Windows: install_path\NetBackup\bin\admincmd\bperror -statuscode

150

termination requested by administrator

The process is terminating (or has terminated) as a direct

result of a request from an authorized user or process.

Note: The Symantec Technical Support site has a wealth of information that canhelp you solve NetBackup problems.

Visit http://entsupport.symantec.com for comprehensive troubleshooting details.

NetBackup status codesThe following is a complete list of the NetBackup status codes that are listed innumerical order:

Note: The term "media server", as distinct from "master server" or "server", doesnot apply to the NetBackup server product. When you troubleshoot a Serverinstallation, ignore any references to media server. (This note does not apply toNetBackup Enterprise Server.)

NetBackup status code: 0Message: the requested operation was successfully completed

Explanation: No problems were detected with the requested operation.

Recommended Action: No action is needed, unless a database was backed upthrough a database extension product (for example, NetBackup for Oracle orNetBackup for SQL Server). In those instances, code 0 means the backup script(that started the backup) ran without error. However, you must check other statusas explained in the related NetBackup manual to see if the database wassuccessfully backed up.

NetBackup status codes and messagesAbout NetBackup status codes and messages

156

NetBackup status code: 1Message: the requested operation was partially successful

Explanation: A problem was detected that may require corrective action duringthe requested operation.

Recommended Action: Check the All Log Entries report and also the progresslog (if there is one).

The following are some of the problems that can appear under status code 1:

■ A file or a directory path is more than 1023 characters long.For NetBackup Snapshot Client, the maximum path name length is 1000characters for snapshot backups, not 1023. When the snapshot is created, anew mount point is added to the beginning of the file path. If the new mountpoint plus the original file path exceeds 1023 characters, the backup fails withstatus code 1. The progress log includes the entry "ERR-Skipping long dirpath."

■ You cannot open a file.The file may have been locked for some reason.

■ The following information applies only to UNIX and Linux systems:NetBackup cannot get the link name of a file.

■ The following information applies only to UNIX and Linux systems:NetBackup cannot process a sparse file.

■ A read error that was encountered in a file.

■ File is of an unknown type, or may be hidden.

■ The following information applies only to UNIX and Linux systems:The lstat system call fails on a file that is eligible to be backed up. This errormay be a permission problem.

■ The following information applies only to UNIX and Linux systems:A file cannot be locked that has mandatory locking enabled.

■ A synthetic backup job may terminate with a status code 1 under the followingconditions:

- No images were found to synthesize (status code = 607).

- TIR info has been pruned from component images (status code = 136).

- Image format is unsupported (status code = 79).

157NetBackup status codes and messagesAbout NetBackup status codes and messages

The synthetic backup job logs the actual status code in the NetBackup errorlog. Refer to the documentation for the corresponding NetBackup error codefor the corrective action to take.

■ A BMR job may terminate with status code 1 in the following situation:You save the BMR configuration and it returns an error even though the childjobs completed successfully. For information, examine the Detailed Status tabof the Job Details dialog box, or the nbjm unified log (originator ID 117).

■ A policy that contains multiple backup scripts starts a scheduled backup of aUNIX database extension client. If it fails with a status code 1, some of thebackup scripts returned a failure status.

■ On clients using Windows Open File Backups (WOFB) to back up open or activefiles, the following may occur:Volume snapshots were not enabled successfully for the backup.The following logging messages should appear in the bpbkar32 logs if volumesnapshots were not successfully enabled.If multistreamed backup jobs are enabled, log messages similar to the followingappear that indicate volume snapshots were not enabled for the multistreamedbackup job:

11:05:44.601 AM: [1536.724] <4> tar_backup::V_AddToFI_XBSAObj:

INF - Volume snapshots not enabled for: D:\Directory1

If multistreamed backups were not enabled, log messages similar to thefollowing appear, which indicate volume snapshots were not enabled for thenon-streamed backup job:

1:59:41.229 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_CreateSnapshot: INF -

===============================

1:59:41.229 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to

create snapshots for D:\Directory1

1:59:41.229 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request:

C:\Program Files\VERITAS\NetBackup\bin\bpfis create -fim VSP

"D:\ Directory1"

1:59:41.799 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot

creation, FIS_ID: 1058813981

1:59:41.799 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation

EXIT STATUS 11: system call failed

NetBackup status codes and messagesAbout NetBackup status codes and messages

158

1:59:41.799 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation

was not successful

1:59:41.799 PM: [2076.2088] <4>

V_Snapshot::V_Snapshot_CreateSnapshot: INF -

===============================

In this case, examine the bpfis logs for error messages regarding snapshotcreation failures. More details are available on the bpfis logs.

See the NetBackup Snapshot Client Administrator’s Guide.In the bpfis logs, the following messages may appear when snapshot creationfails for Windows Open File Backup:First message:

04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS error 11; see

following messages:

04:01:14.168 [376.2364] <32> onlfi_fi_split: Fatal method error

was reported

04:01:14.168 [376.2364] <32> onlfi_fi_split: vfm_freeze_commit:

method: VSP, type: FIM, function: VSP_make

04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS method error

3; see following message:

04:01:14.168 [376.2364] <32> onlfi_fi_split: snapshot services:

snapshot creation failed: invalid argument(s).

Cause: VSP was not enabled because the VSP snapshot for the backup did notmeet the specified minimum time in the Busy File Wait VSP setting.Either increase the Busy File Timeout VSP setting (recommended setting: 300seconds or more) or submit the backup job when the volume has less activity.Second message:

04:17:55.571 [1636.3224] <2> onlfi_vfms_logf: snapshot services:

(null): There was an unexpected error while preparing the VSP

snapshot transaction. Dumping the parameter array to provide

more information: Error 112 from VSP_Prepare

Cause: VSP was not enabled for the backup because the client for the VSPSnapshot Cache files does not have enough free disk space.Free up disk space on the volumes being backed up.Third message:If Microsoft Volume Shadow Copy Service (VSS) is used as the Windows OpenFile Backup snapshot provider and snapshot creation fails, refer to thefollowing: Event Viewer’s Application and System Logs for error information.

159NetBackup status codes and messagesAbout NetBackup status codes and messages

■ A snapshot error may have occurred. Also, you may have clients that use theWindows Open File Backup option to back up open or active files. In this case,a log message in the bpbkar32 debug log appears, which indicates that asnapshot error occurred.The following is an example of a snapshot error:

8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR -

Snapshot Error while reading test.file

See the recommended actions under status code 156.

■ The granular processing operation of an Exchange Granular backup job hasfailed to complete successfully. Check the bpbkar debug log for moreinformation. A legacy (non-VSS) backup still truncates transaction logs if thejob ends with status 1 because a granular processing operation failed. In thissituation, the backup image is suitable for database recovery.

NetBackup status code: 2Message: none of the requested files were backed up

Explanation: A backup or archive did not back up any of the files in the file list.

This status code applies primarily to automatic backups using Lotus Notes or SQLdatabase agents, when all the backups that are job related have failed. Or, anEnterprise Vault backup has failed. It should not occur for standard file systembackups.

Open a NetBackup support case (recommended in Symantec document 276903.pdf)if you encounter this error for the following: a UNIX, Linux, or Windows file systembackup, or for database agents other than SQL Server or Lotus Notes.

Recommended Action: Do the following, as appropriate:

■ The following information applies only to Lotus Notes:This error occurs when archive style logging is not enabled for the LotusDomino server on UNIX. It also occurs when another backup of the transactionlogs is in progress.

■ For troubleshooting guidance, such as a list of logs to gather, and for detailson particular issues, refer to the Symantec support document 276903.pdf.

■ See the troubleshooting topic of the appropriate guide for a description oftroubleshooting tools:

■ NetBackup for Microsoft SQL Server Administrator’s Guide

■ NetBackup for Lotus Notes Administrator’s Guide

■ NetBackup for Enterprise Vault Agent Administrator’s Guide

NetBackup status codes and messagesAbout NetBackup status codes and messages

160

NetBackup status code: 3Message: valid archive image produced, but no files deleted due to non-fatalproblems

Explanation: The backup portion of the archive command reported problems sothe files were not deleted.

Recommended Action: Examine the progress log or status of the archive on theclient to determine if you need to retry the archive after correcting the problem.If the problem is not serious and the files were backed up, you can manually deletethe files. To verify which files were backed up, use the NetBackup client-userinterface in restore mode and browse the files in the archive.

A possible cause for files not being deleted is that you do not have the necessarypermissions. NetBackup cannot delete files unless you are the user that owns thefiles, a superuser on UNIX, or an administrator on Windows.

NetBackup status code: 4Message: archive file removal failed

Explanation: The backup portion of the archive completed was successful butthe delete failed.

Recommended Action: Verify that you have permission to delete the files andthat the read-only flag is not set for the files. On UNIX and Linux clients, verifythat you have write permission to the directories that contain the files. Since thebackup was successful, you can delete the files that were backed up. (If you do nothave the necessary permissions, have the system administrator delete the files.)

NetBackup status code: 5Message: the restore failed to recover the requested files

Explanation: Errors caused the restore to fail.

Recommended Action: Perform the following items in the order presented:

■ Ensure that the client’s server list contains entries for the master server andany media servers that can be used during a backup or restore.

■ Examine the status or the progress log on the client for messages on why therestore failed. Also, check the All Log Entries report on the server.

■ Check ownership and permission on directories where files are restored.

■ Correct the problems that you find and retry the restore.

■ If you tried to restore files from a FlashBackup backup after a NetBackup patchwas installed, the patch may not have been installed properly. Follow the

161NetBackup status codes and messagesAbout NetBackup status codes and messages

installation instructions in the patch readme file and make sure the libsfr.sofile is copied as instructed.

NetBackup status code: 6Message: the backup failed to back up the requested files

Explanation: Errors caused the user backup to fail.

Recommended Action: Do the following as appropriate:

■ Verify that you have read access to the files. Check the status or the progresslog on the client for messages on why the backup failed. Correct problems andretry the backup.

■ The following information applies only to Windows clients:Verify that the account used to start the NetBackup Client service has readaccess to the files.

■ The following information applies only to Macintosh clients:This code can be due to multiple backups being tried simultaneously on thesame client.

Some possible solutions are as follows:

■ Adjust the backup schedules.

■ If the client is only in one policy, set the policy attribute, Limit jobs perpolicy, to 1.

■ Set the NetBackup global attribute, Maximum jobs per client, to 1 (notethat this limits all clients in all policies).

■ For a UNIX or Linux database extension client (for example, NetBackup forOracle), this status code can indicate a problem with the script that controlsthe backup.Check the progress report on the client for a message such as Script exited

with status code = number (the number varies). The progress log usuallynames the script.Check the script for problems. Also, check that the troubleshooting logs createdby the database extension. See the NetBackup guide that came with the databaseextension for information on the scripts and the troubleshooting logs.

NetBackup status code: 7Message: the archive failed to back up the requested files

Explanation: Errors caused the user archive to fail.

NetBackup status codes and messagesAbout NetBackup status codes and messages

162

Recommended Action: Verify that you have read access to the files. Check theprogress log or the status on the client for messages on why the archive failed.Correct problems and retry the archive.

On Windows clients, verify that the account used to start the NetBackup serviceshas read access to the files.

NetBackup status code: 8Message: unable to determine the status of rbak

Explanation: On DomainOS clients, rbak is used to do restores. If rbak does notexit with a status message, NetBackup cannot determine whether the restoreworked or not.

Recommended Action: Check for a new core file to see if rbak quit abnormally.Check the ps output to see if rbak is hung. If so, cancel it and try again. Check theprogress log for any unusual messages from rbak.

NetBackup status code: 9Message: an extension package is needed, but was not installed

Explanation: A NetBackup extension product is required to perform the requestedoperation.

Recommended Action: Install the required extension product.

NetBackup status code: 10Message: allocation failed

Explanation: The system memory allocation fails because of insufficient systemmemory available. A possible cause is that the system is overloaded with too manyprocesses and not enough physical or virtual memory.

RecommendedAction: Free up memory by terminating any unneeded processesthat consume memory. Add more swap space or physical memory.

NetBackup status code: 11Message: system call failed

Explanation: A system call has failed. This status code is used for a generic systemcall failure that does not have its own status code.

Recommended Action: Do the following, as appropriate:

■ Check the All Log Entries and Problems reports to determine the system callthat failed and other information about the error.

163NetBackup status codes and messagesAbout NetBackup status codes and messages

■ nbjm and nbproxy return status code 11 when an exception is processed, suchas when nbproxy obtains policy or configuration information. Examine thenbjm unified log (originator ID 117) or the nbproxy legacy log for more detailon the cause of the error.

■ A frequent cause is that the server’s file system is full. For example, you maysee a message similar to the following in the Problems report or bpdbm debuglog:

06/27/95 01:04:00 romb romb db_FLISTsend failed: system call

failed (11)

06/27/95 01:04:01 romb romb media manager terminated by parent

process

06/27/95 01:05:15 romb romb backup of client romb that exited with status 11(system call failed)On UNIX and Linux systems, run a df command on the/usr/openv/netbackup/db directory.

If the df command does not reveal the problem, check the bpdbm debug logsor do a grep for the message

system call failed

In relevant files under the directory /usr/openv/netbackup/db/error/

On Windows systems, verify that the disk partition where NetBackup isinstalled has enough room.

■ Verify that the system is not running out of virtual memory. If virtual memoryis the problem, turn off unused applications or increase the amount of virtualmemory.

To increase virtual memory on Windows, do the following in the orderpresented:

■ Display the Control Panel.

■ Double-click System.

■ On the Performance tab, set Virtual Memory to a higher value.

■ The following information applies only to UNIX and Linux clients:Check for a semaphore problem. This error may occur because the system doesnot have enough allocated semaphores. It is most commonly seen on Solarisservers when an RDBMS is also running.The symptoms of the problem vary. In some cases, error messages in theNetBackup log indicate a backup failure due to an error in semaphore operation.

NetBackup status codes and messagesAbout NetBackup status codes and messages

164

Another symptom is the inability of the NetBackup device manager daemon,ltid, to acquire a needed semaphore.

System requirements vary; thus, no definite recommendations can be made.One customer running NetBackup and ORACLE on a Solaris server made thefollowing changes to the /etc/system file and then rebooted the system (boot-r). The changes were adequate.

set semsys:seminfo_semmni=300

set semsys:seminfo_semmns=300

set semsys:seminfo_semmsl=300

set semsys:seminfo_semmnu=600

Set these attributes to a value great enough to provide resources to allapplications on your system.

■ Examine other debug logs or the progress log or status on the client. Examinethe nbjm unified log (originator ID 117) for more detail on the cause of theerror.

NetBackup status code: 12Message: file open failed

Explanation: An open of a file failed.

A disk storage unit tries to write to or create a directory on the root device of theNetBackup server or media server. In this case, the Activity Monitor job detailslog contains the message "not permitted to root device." By default the absolutepath or specified directory for a disk storage unit cannot be on the root file system(or system disk). You must explicitly enable them to be there when the storageunit is created.

Recommended Action: Do the following as appropriate:

■ If you want the path for the disk storage unit to reside in the root file system:Open the Change Storage Unit dialog box in the Administration Console andselect the check box: "This directory can exist on the root file system or systemdisk."

■ If the specified path for the disk storage unit is not in the root file system orsystem device, do the following: Verify that the path is in a mounted file system.

■ If the specified path for the disk storage unit is in the root file system or systemdevice but does not need to be: Use the Change Storage Unit dialog box tospecify a different (non-root) path in a mounted file system.

■ Check the NetBackup Problems report. Try to determine the file and why theerror occurred. A possible cause is a permission problem with the file. For

165NetBackup status codes and messagesAbout NetBackup status codes and messages

detailed troubleshooting information, create a debug log directory for theprocess that returned this status code. Then, retry the operation and checkthe resulting debug log.

■ For NetBackup Lotus Notes, point-in-time restore jobs may fail with a status12. These jobs are initiated from the master server by using either theNetBackup Administration Console or the Backup, Archive, and Restoreinterface. Their failure is reported in the NetBackup tar log file. (For Windows,this file is located in the install_path\NetBackup\logs\tar folder. For UNIXand Linux, it is located in the /usr/openv/netbackup/logs/tar folder.) If theinstall path of the NetBackup master server is different from the install pathof the NetBackup client, the following occurs: The automatic restore of Lotustransaction log extents during recovery of the Lotus database fail. Note thatthe Activity Monitor shows a status 0 (successful). The tar log on the client,however, shows success for the restore but a failure (status 12) for the Lotusdatabase recovery.Perform the restore job from the Backup, Archive, and Restore interface onthe NetBackup client.

■ For NetBackup Snapshot Client, status code 12 may appear in the/usr/openv/netbackup/logs/bptm or bpdm log with the following:

tpc_read_config failed: cannot open file

/usr/openv/volmgr/database/3pc.conf

This status code may indicate that the policy is configured with either of thefollowing: The NetBackup media server or Third-Party Copy Device as theoff-host backup method, but the 3pc. file does not exist or is in the wronglocation.Instructions are available on how to create the 3pc. file.

See the NetBackup Snapshot Client Administrator’s Guide.

■ For a FlashBackup policy, if the CACHE= entry follows the source data entry,the backup fails with status code 12. Messages such as the following appearin the /usr/openv/netbackup/logs/bpbkar logs on the client:

09:55:33.941 [6092] <16> bpfsmap: ERR - open_snapdisk: NBU

snapshot enable failed error 3

09:55:33.942 [6092] <32> bpfsmap: FTL - bpfsmap: can't open

snapshot disk /dev/rdsk/c4t1d0s3 errno 0

09:55:33.950 [6092] <16> bpbkar Exit: ERR - bpbkar FATAL exit

status = 12: file open failed

09:55:33.956 [6092] <4> bpbkar Exit: INF - EXIT STATUS 12: file

open failed

NetBackup status codes and messagesAbout NetBackup status codes and messages

166

09:55:33.957 [6092] <2> bpbkar Exit: INF - Close of stdout

complete

Change the order of the backup selections list so that the CACHE entry precedesthe source data entry. (The source data entry specifies the raw partition thatcontains the file system to be backed up.)

NetBackup status code: 13Message: file read failed

Explanation: A read of a file or socket failed.

The possible causes include as follows:

■ A network communication problem has occurred on the master server, mediaserver, or one of the clients.

■ An I/O error that occurred during a read from the file system.

■ Read of an incomplete file or a corrupt file.

■ A socket read failure that is caused by a network problem or a problem withthe process that writes to the socket.

■ A problem specific to NetBackup Snapshot Client (see recommended actions).

■ The first EV-SQL backup after a NetBackup installation failed.See the Troubleshooting section of the NetBackup for Enterprise Vault AgentAdministrator’s Guide.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on where and why the problemoccurred.

■ Check that network communication works properly.See “Resolving network communication problems” on page 40.

■ For a FlashBackup client, check the /var/adm/messages log for errors like thefollowing:

Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache

/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now

unusable

This error indicates that the cache partition is not large enough. If possible,increase the size of the cache partition. Or, if multiple backups use the samecache, reduce the number of concurrent backups. To reduce the number,reschedule some of them or reschedule the entire backup to a time when thefile system is less active.

167NetBackup status codes and messagesAbout NetBackup status codes and messages

■ For detailed troubleshooting information, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

■ Ensure that the latest service packs for all products and components (SQL,Exchange, Notes, etc.) have been installed.

■ Ensure that all the network hardware (NICs, hubs, switches, routers, etc.)throughout the environment are set to full duplex, not half duplex.

■ Check the following items regarding the NICs in your system:

■ Upgrade to the latest NIC drivers throughout the system.

■ Ensure that all NICs are set to full duplex, not half duplex.See “Backup performance and NIC cards” on page 72.

■ Increase the timeout settings on the NIC.

■ If NIC teaming is implemented, deactivate for testing purposes.

■ Replace the NIC itself on the affected client or server.

■ For NetBackup Snapshot Client, status code 13 may appear in the/usr/openv/netbackup/logs/bpbkar log.

The log can indicate the following:

■ The files to back up reside on an IDE drive as opposed to SCSI. The off-hostbackup method was set to either NetBackup media server or Third-PartyCopy Device. If you use off-host backup, the disk that contains the clientfiles must be a SCSI or Fibre Channel device.If the disk is an IDE drive, you may see the following in the /usr/openv/

netbackup/logs/bpfis log:

get_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed.

Errno = 25: Inappropriate ioctl for device

The following listing may appear in the/usr/openv/netbackup/logs/bpbkar log:

bpbkar: INF - Processing /var

bpbkar: ERR - get_disk_info() failed, status 13

bpbkar: ERR - tpc_get_disk_info() failed: err 13

bpbkar: ERR - bpbkar FATAL exit status = 13: file read failed

bpbkar: INF - EXIT STATUS 13: file read failed

■ The files to back up exist on a file system that is not mounted. The filesystem that is specified as the snapshot source must be mounted. If thesnapshot source is not mounted but the mount point is present, NetBackup

NetBackup status codes and messagesAbout NetBackup status codes and messages

168

may do the following: Try to take a snapshot of the directory preceding thedirectory that was specified as the snapshot source.

■ For the NetBackup media server method, you may need to increase theclient read timeout value. In some environments, NetBackup may requiremore read time than the default value allows. If the client read timeout isinsufficient, the backup may fail, which causes this error.To increase the client read timeout for all clients, do the following: In theNetBackup Administration Console, go to HostProperties>MasterServers> double-click the master server, then go to Properties > Timeouts. Thenincrease the client read timeout.

NetBackup status code: 14Message: file write failed

Explanation: A write to a file or socket failed.

Possible causes include the following:

■ An I/O error that occurred during a write to the file system.

■ Write to a socket failed. Cause of this failure: A network problem or a problemwith the process that reads from the socket.

■ Writing to a full disk partition.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on where and why the problemoccurred.

■ For detailed troubleshooting information, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

■ Make sure that routers, bridges, and other network devices are all at "full"duplex.See “Backup performance and NIC cards” on page 72.

■ Use a "sniffer" program to determine the number of packets being rejected orre-requested.

■ On Windows systems, the client bpbkar log may contain a 10054 "ConnectionReset Error"error (usually indicates a hardware error). Somewhere betweenthe NetBackup client and server, the connection was reset. When NetBackupreceives this error, it cannot continue the backup. This error has been attributedto the following:

■ A hiccup in the network.

169NetBackup status codes and messagesAbout NetBackup status codes and messages

■ A bad network interface card on a NetBackup client.

■ A bad network interface card on the NetBackup server.

■ Faulty routers.

■ Any other applications that interfere with NetBackup connections.

■ On Novell systems, status code 14 has also been attributed to network issues.Try a "sniffer" program.

■ The error occurs while you use the NetBackup-Java interface: The applicationserver (bpjava processes) for the NetBackup-Java interface probably ran outof disk space in the file system containing/usr/openv/netbackup/logs/user_ops. The application server writestemporary files into directories in the /user_ops directory. Try clearing updisk space in the file system.

NetBackup status code: 15Message: file close failed

Explanation: A close of a file or socket failed.

RecommendedAction: Check the NetBackup Problems report for clues on whereand why the problem occurred. For detailed troubleshooting information, createa debug log directory for the process that returned this status code. Then retrythe operation and check the resulting debug log.

NetBackup status code: 16Message: unimplemented feature

Explanation: The specified operation is not implemented. This error should notoccur through normal use of NetBackup.

Recommended Action: Save all error information and call customer support.

NetBackup status code: 17Message: pipe open failed

Explanation: Occurs in NetBackup client menu and Vault areas.

Recommended Action: Save all error information and call customer support.

NetBackup status code: 18Message: pipe close failed

Explanation: A pipe close failed when one process tries to start a child process.

NetBackup status codes and messagesAbout NetBackup status codes and messages

170

Recommended Action: Check the NetBackup Problems report for clues on whythe failure occurred. For detailed troubleshooting information, create a debug logdirectory for the process that returned this status code. Then retry the operationand check the resulting debug log.

NetBackup status code: 19Message: getservbyname failed

Explanation: A call to getservbyname() failed. The getservbyname()functionuses the name of the service to find a service entry in the services file. (Or NISservices map on UNIX and Linux if it is configured.)

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on why the failure occurred.

■ On a UNIX or Linux system, check that /etc/services and NIS services map(if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.

■ On a Windows system, verify that the%SystemRoot%\system32\drivers\etc\services file shows the correct entriesfor the NetBackup Internet processes: bpcd, bpdbm, and bprd.

Ensure that the following numbers match the settings in the services file:The NetBackup Client Service Port number and NetBackup Request ServicePort number on the Network tab in the NetBackup Client Properties dialogbox. To display this dialog box, start the Backup, Archive, and Restore interfaceand click NetBackup Client Properties on the File menu. The values on theNetwork tab are written to theservices file when the NetBackup Client servicestarts.See “Verifying host name and service entries” on page 49.

■ Check the level of network activity. An overloaded network can cause thiserror.

■ If these actions do not reveal the problem, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

NetBackup status code: 20Message: invalid command parameter

Explanation: One or more command parameters were not valid. This error canoccur when incompatible levels of NetBackup are installed on a master and itsmedia server(s) or client(s). For example, a NetBackup master server has NetBackup7.0 and the media server or the client has NetBackup 6.0.

171NetBackup status codes and messagesAbout NetBackup status codes and messages

This error can also occur if the wrong parameters are used when you run acommand line.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues.

■ If the error occurs when you run a command on the command line, verify thatthe parameters are valid.

■ This status code may occur if nbjm passes parameters but does not have arequired parameter. Check the nbjm unified logs (originator ID 117) for thelist of parameters that were passed.

■ The following information pertains to NetBackup Snapshot Client.

■ If the following appears in the /usr/openv/netbackup/logs/bptm log asenabled on a third-party copy backup, multiplexing was enabled on athird-party copy backup.:

bptm: cannot perform Third-Party-Copy for multiplexed backups

send_brm_msg: ERROR 20

bptm: EXITING with status 20The Third-Party Copy Device off-host backup method is incompatible withmultiplexing (the writing of two or more concurrent backup jobs to thesame storage device). You must disable multiplexing for any third-partycopy backups. If multiplexing is enabled, the backup fails.

■ The media server may not have the correct 3pc. file entry for the clientdisk that is needed for the backup.The following appears in the /usr/openv/netbackup/logs/bpbkar log:

14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1

EMC:SYMMETRIX:601092014000

14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive

child started, pid = 15822

14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:

15822 killed

14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1

14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain

device id string EMC:SYMMETRIX:601092014000

14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit

status = 227: no entity was found

14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no

entity was found

14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout

complete

NetBackup status codes and messagesAbout NetBackup status codes and messages

172

This shows that a particular device cannot be found in the 3pc. file on themedia server (14:47:02.031 [15773] <16> bpmap_send_extend: ERR -

can't obtain device id string EMC:SYMMETRIX:601092014000).

The problem is one of the following:

■ The 3pc. file on the media server is outdated. Recreate the 3pc. file.

■ The media server is not on the same Fibre Channel network as thethird-party copy device and client disk. As a result, the 3pc. file doesnot have a correct entry for the client disk. Run the bptpcinfo commandwith the -x client_name option; this option adds the client disk to the3pc. file. For each disk that is added to the file by means of bptpcinfo-x client_name, you may need to add the device’s worldwide name(wwn=).

See the NetBackup Snapshot Client Configuration online document.See "Snapshot Client Assistance" in the NetBackup Snapshot ClientAdministrator’s Guide.

■ The HP VxFS snapshot mechanism requires a dedicated cache partitionfor each snapshot. A check is made in the mount table to make sure thatthe cache partition is not already in use. If the cache partition is alreadyin use, status code 20 occurs.Check the /usr/openv/netbackup/logs/bpbkar log for a message similarto the following:

bpfsmap: FTL - bpfsmap: snapshot cache already in use,

/dev/arrayvg/vol4c

bpbkar Exit: ERR - bpbkar FATAL exit status = 20: invalid

command parameter

bpbkar Exit: INF - EXIT STATUS 20: invalid command parameter

If the snapshot cache partition is already in use, do one of the following:Set up your policy schedules to run at different times or use different cachepartitions for each backup.If the Allow multiple data streams option is enabled, each stream musthave its own dedicated cache partition.

■ Compare the NetBackup version level on the server to the version level on theclients by doing the following:

■ On UNIX or Linux NetBackup servers and clients, check the/usr/openv/netbackup/bin/version file.

■ On Windows NetBackup servers, check theinstall_path\Netbackup\version.txt file or the About NetBackup itemon the Help menu.

173NetBackup status codes and messagesAbout NetBackup status codes and messages

■ On Microsoft Windows clients, check the About NetBackup item on theHelp menu.

■ On NetWare target clients, check the Version entry in the bp.ini file.

■ On Macintosh clients, check the version file in the bin folder in theNetBackup folder in the Preferences folder.

■ If a Java interface displays the error, tell them how to enable the debugprint manager in the Java startup file. Retry and compare the parametersthat were logged on the Java log with the parameters listed in the commandsusage statement.

■ If these actions do not reveal the problem, do the following: Create a debuglog directory for the process that returned this status code (if the process useslegacy logging). Then retry the operation and check the resulting log.

NetBackup status code: 21Message: socket open failed

Explanation: A socket was not opened.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on where and why the failureoccurred. If you cannot determine the cause from the Problems report, createdebug log directories for the processes that returned this status code. Then,retry the operation and check the resulting debug logs.

■ The following information applies only to Sun Solaris:Verify that all operating system patches are installed.See the Operating Notes section of the NetBackup Release Notes.

■ The following information applies only to Windows systems:Verify that the recommended service packs are installed.

NetBackup status code: 22Message: socket close failed

Explanation: A socket was not closed.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on where and why the failureoccurred. If you cannot determine the cause from the Problems report, createdebug log directories for the processes that could have returned this statuscode. Then, retry the operation and check the resulting debug logs.

■ The following information applies only to Sun Solaris:

NetBackup status codes and messagesAbout NetBackup status codes and messages

174

Verify that all operating system patches are installed.See the Operating Notes section of the NetBackup Release Notes.

■ The following information applies only to Windows systems:Verify that the recommended service packs are installed.

NetBackup status code: 23Message: socket read failed

Explanation: A read operation from a socket failed.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on where and why the failureoccurred. If you cannot determine the cause from the Problems report, createdebug log directories for the processes that could have returned this statuscode. Then, retry the operation and check the resulting debug logs.

■ Corrupt binaries are one possible cause for this error.Load a fresh bptm from the install media to try to resolve the problem.

■ The following information applies only to Sun Solaris:Verify that all operating system patches are installed.See the Operating Notes section of the NetBackup Release Notes.

■ The following information applies only to Windows systems:Verify that the recommended service packs are installed.

■ This error may occur during a restore to a Novell client.

Note the following possible actions:

■ By default, the value for Novell "Maximum Concurrent Disk Cache Writes"may be too low (for example, 50); Novell recommends setting it to 100. Avalue of 100 increases the speed and efficiency of the disk cache writes. Itincreases the number of write requests to be run at one time.

■ Change to or add the following settings in the Novellsys:system\autoexec.ncf file:

SET Maximum Packet Receive Buffers = 4000

SET Maximum Directory Cache Buffers = 4000

SET Maximum Concurrent Disk Cache Writes = 2000

SET Maximum Concurrent Directory Cache Writes = 2000

SET Maximum Physical Receive Packet Size = 1514

■ On Windows master servers, check the LIST_FILES_TIMEOUT value andensure that this value is at least 1800.

175NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 24Message: socket write failed

Explanation: A write operation to a socket failed.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues on where and why the failureoccurred. If you cannot determine the cause from the Problems report, createdebug log directories for the processes that could have returned this statuscode. Then retry the operation and check the resulting debug logs.

■ A possible cause is a high network load. For example, this problem occurs withCannot write to STDOUT when a Windows system that monitors networkload detects a high load. It then sends an ICMP packet to other systems toinform them that the route those systems use was disconnected. The logmessages were similar to the following:

01/31/96 14:05:23 ruble crabtree.null.com from client

crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No

route to host

01/31/96 14:05:48 ruble crabtree.null.com successfully wrote

backup id crabtree.null.com_0823125016, copy 1, fragment 1,

440864 Kbytes at 628.538 Kbytes/sec

01/31/96 14:05:51 netbackup crabtree.null.com CLIENT

crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT

STATUS 24 (socket write failed)

■ The following information applies only to Sun Solaris:Verify that all operating system patches are installed.See the Operating Notes section of the NetBackup Release Notes.

■ The following information applies only to Windows systems:Verify that the recommended service packs are installed.

■ This error may occur during a restore to a Novell client.

Note the following possible actions:

■ By default, the value for Novell "Maximum Packet Receive Buffers" maybe too low (such as 100). To improve the restore performance, change thisvalue to 2000. To change it, issue "SET Maximum Packet ReceiveBuffers=<value>" at the console, or enter the value in either of the followingNovell files: sys:system\startup.ncf or sys:system\autoexec.ncf.

■ Change to or add the following settings in the Novellsys:system\autoexec.ncf file:

NetBackup status codes and messagesAbout NetBackup status codes and messages

176

SET Maximum Packet Receive Buffers = 4000

SET Maximum Directory Cache Buffers = 4000

SET Maximum Concurrent Disk Cache Writes = 2000

SET Maximum Concurrent Directory Cache Writes = 2000

SET Maximum Physical Receive Packet Size = 1514

NetBackup status code: 25Message: cannot connect on socket

Explanation: A process that timed out while it connects to another process for aparticular operation. This problem can occur in the following situation: when aprocess tries to connect to the NetBackup request daemon (bprd) or databasemanager daemon (bpdbm) and the daemon is not running. (On Windows, thesedaemons are the NetBackup Request Manager and NetBackup database managerservices.)

It can also occur in the following situations: the network or server is heavily loadedand has slow response time or an evaluation license key for NetBackup expired.However, the most common cause of this error is a host name resolution problem.

The following are other possible causes of this error caused by networkconnectivity issues or a required process such as pbx_exchange not running.

■ nbjm is unable to connect to bpcd on the media server

■ nbpem is unable to connect to nbproxy

■ bptm on the media server is unable to connect to nbjm on the master server.

■ You cannot perform an immediate backup operation.

These errors are

Recommended Action: Do the following, as appropriate:

■ Verify that bpcompatd, vnetd, and Private Branch Exchange (PBX) are running.Information on how to start PBX is available.See “Resolving PBX problems” on page 67.

■ If necessary, stop and restart NetBackup.

■ On UNIX and Linux systems, enter the following:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

■ On Windows systems, enter the following:

177NetBackup status codes and messagesAbout NetBackup status codes and messages

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

■ The following information applies only to a UNIX or Linux NetBackup masterserver:Verify that the bprd and the bpdbm processes are running. If these processesare not running, start them. On a Windows master server, verify that theNetBackup Request Manager and NetBackup database manager services arerunning. If these services are not running, start them.If these processes or services are running, examine the All Log Entries reportfor the time of the failure to determine where the failure occurred.

Do one of the following:

■ If you cannot view the report or you get a cannot connect on socket

error when you try to view it, do the following: Verify again that theNetBackup database manager service or daemon is running. Then, createa debug log directory for bpdbm, retry the operation, and check the resultingdebug log.

■ If you can view the report and have not found an entry that is related tothis problem: Create debug log directories for the related processes thatwere running when the error first appeared. (This process frequently isbpbrm.) Then, retry the operation and check the resulting debug logs.

■ Verify that the server list specifies the correct master server.

■ The following information applies only to Windows systems:The master server is designated in the Server to use for backups andrestores drop-down in the SpecifyNetBackupMachines andPolicyTypedialog box. To display this dialog box, start the Backup, Archive, and Restoreinterface and click Specify NetBackup Machines and Policy Type on theFile menu.

■ The following information applies only to UNIX, Linux, and Macintoshsystems:The master server is the first SERVER entry in the bp.conf file.

■ On NetWare target clients: The master server name is the first SERVER entryin the bp.ini file.

■ Make sure all recommended NetBackup patches were installed. Check theSymantec support Web site for current patch information.Go to www.support.symantec.com.Then select "NetBackup" followed by "files and updates."

NetBackup status codes and messagesAbout NetBackup status codes and messages

178

■ If failure occurs when you run a user-directed backup from a client, makesure that a user-directed backup schedule exists at the master server.

■ With NetBackup database extensions: Make sure that the applicabledatabase product has the correct permissions allowing NetBackup to writeto the progress log on the client.

■ The following information applies only to UNIX and Linux systems:Ifbpdbmhas quit when the shutdown script runs on a media server, carefullyread the K77netbackup script. It contains details on how to prevent thisproblem. The script is in /usr/openv/netbackup/bin/goodies.

If you change the server list on a master server, stop, and restart the following:The NetBackup database manager and request daemons (UNIX and Linux) orthe NetBackup database manager and NetBackup Request Manager services(Windows).

■ Check the services file.

■ The following information applies only to UNIX and Linux systems:Verify that the /etc/services file (and NIS services if NIS is used) hasentries for the NetBackup services: bpcd, bpdbm, and bprd.

On Windows, verify that the%SystemRoot%\system32\drivers\etc\servicesfile has the correct entries for bpcd, bpdbm, and bprd.

Also, verify that the following numbers match the settings in the services

file: The NetBackupClientServicePort and the NetBackupRequest ServicePort on the Network tab in the NetBackup Client Properties dialog box. Todisplay this dialog box, start the Backup, Archive, and Restore interface andclick NetBackup Client Properties on the File menu. The values on theNetwork tab are written to theservices file when the NetBackup Client servicestarts.See “Verifying host name and service entries” on page 49.

■ On Sun Solaris, verify that all operating system patches are installedSee the Operating Notes section of the NetBackup Release Notes.

■ On Windows, verify that the recommended service packs are installed.

■ When the base NetBackup license key expires, daemons (such as bprd andbpdbm) terminate on the NetBackup server. If these daemons are not running,you are likely to encounter status code 25 errors in the Administration console.Install a valid base NetBackup license key, restart the daemons, and restartthe console.

■ For NetBackup Snapshot Client, the following applies: When many devices areconfigured on a media server, it may take a long time for the bptpcinfo

command to generate the file 3pc. When the backup is run for the first time,

179NetBackup status codes and messagesAbout NetBackup status codes and messages

the backup may fail with status 25. Make sure that the/usr/openv/volmgr/database/3pc.conf file exists. If it does, rerun the backup.If the backup fails again, run the bptpcinfomanually to generate the file 3pc.,then try the backup again.

NetBackup status code: 26Message: client/server handshaking failed

Explanation: A process on the server encountered an error when it communicatedwith the client. This error indicates that the client and server were able to initiatecommunications, but encountered difficulties and the communications did notcomplete. This problem can occur during a backup or a restore.

Recommended Action: Determine which activity encountered the handshakefailure by examining the All Log Entries report for the appropriate time period.Determine the client and server that had the handshake failure.

For detailed troubleshooting information, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

NetBackup status code: 27Message: child process killed by signal

Explanation: A child of the process that reported this error was terminated. Thiserror may occur if the backup job was terminated or another error terminated thechild process. This problem may also occur if a NetBackup process was terminatedthrough Task Manager or another utility.

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create a debug log directory for the process that you think may have returnedthis status code. Then, retry the operation and check the resulting debug log.

NetBackup status code: 28Message: failed trying to fork a process

Explanation: A fork of a child process failed (on UNIX and Linux) or aCreateProcess failed (on Windows).

This failure may be due to the following:

■ An overloaded system

■ Insufficient swap space or physical memory

NetBackup status codes and messagesAbout NetBackup status codes and messages

180

■ Too many processes are running on the system

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create debug log directories for the processes that think may have returned thisstatus code. Then, retry the operation and check the resulting debug logs.

NetBackup status code: 29Message: failed trying to exec a command

Explanation: A command was not run. This error can occur because thepermissions of the command do not allow it to be run. Or it occurs due to a lackof system resources such as memory and swap space.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup All Log Entries report for clues on where and why thefailure occurred.

■ Check the permissions on the command to be run.

■ For detailed troubleshooting information, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

NetBackup status code: 30Message: cannot get passwd information

Explanation: Could not get the passwd entry for a user.

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create a debug log for the process that you think may have returned this statuscode. Then, retry the operation and check the resulting debug log.

NetBackup status code: 31Message: could not set user id for process

Explanation: Could not set the user ID of a process to the user ID of the requestinguser. NetBackup runs client processes as the requesting user.

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create a debug log directory for the process that you think may have returnedthis status code. Then, retry the operation and check the resulting debug log.

181NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 32Message: could not set group id for process

Explanation: Could not set the group ID of a process to the requesting user group.NetBackup runs client processes with the group ID of the requesting user.

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create a debug log directory for the process that you think may have returnedthis status code. Then, retry the operation and check the resulting debug log.

NetBackup status code: 33Message: failed while trying to send mail

Explanation: An email notification about backup, archive, or restore results hasfailed. The email was not sent to the administrator’s address as specified by theemail global attribute. On a UNIX or Linux client, the email was not sent to anemail address that is specified with USEMAIL in the client’s bp.conf file.

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create a debug log directory for the process that you think may have returnedthis status code. Then, retry the operation and check the resulting debug log.

NetBackup status code: 34Message: failed waiting for child process

Explanation: A NetBackup process encountered a failure while it waited for achild process to complete.

Recommended Action: Check the NetBackup All Log Entries report for clues onwhere and why the failure occurred. For detailed troubleshooting information,create a debug log for the process that you think may have returned this statuscode. Then, retry the operation and check the resulting debug log.

NetBackup status code: 35Message: cannot make required directory

Explanation: Could not create a required directory.

Possible causes are the following:

■ A process does not have permission to create the directory

■ The path to the directory is not valid

■ An IO error occurs

NetBackup status codes and messagesAbout NetBackup status codes and messages

182

■ No space is available on the device that contains the directory

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup All Log Entries report to determine which directory wasnot created and why it was not created. In particular, check for a full diskpartition.

■ Check the permissions on the parent directory. Verify that NetBackup servicesare started with a "Logon as" account that has permission to create thedirectory.

■ For detailed troubleshooting information, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

NetBackup status code: 36Message: failed trying to allocate memory

Explanation: Allocation of system memory failed. This error occurs when aninsufficient system memory is available. This cause of this error may be that thesystem is overloaded with too many processes and it does not enough physicaland virtual memory.

RecommendedAction: Free up memory by terminating any unneeded processesthat consume a lot of memory. Add more swap space or physical memory.

NetBackup status code: 37Message: operation requested by an invalid server

Explanation: An invalid media server or Windows NetBackup RemoteAdministration Console made a request to the NetBackup request daemon (bprd)or NetBackup database manager daemon (bpdbm). On Windows, these daemonsare the NetBackup Request Manager and NetBackup database manager services.

Recommended Action: Examine the NetBackup All Log Entries report for thetime of this error to determine which system tried to connect to the master server.

If the server is a valid media server, verify that the storage unit for the mediaserver is defined. Also, verify that the server or Windows NetBackup RemoteAdministration Console has a server list entry on the master server.

If necessary, update the server list.

On a UNIX or Linux master server, add a SERVER = media_server_name to thebp.conf file. media_server_name is the host name of the media server. On aWindows master server, add the media server to the list on the Servers tab in theMaster Server Properties dialog box.

183NetBackup status codes and messagesAbout NetBackup status codes and messages

See “Using the Host Properties window” on page 61.

If a server or Windows NetBackup Remote Administration Console has more thanone host name (for example, it has multiple network interfaces), do the following:verify that the master server has a server list entry for each of them.

If you change the server list on a UNIX or Linux master server, for the changesto take effect do the following: stop and restart the NetBackup Request daemon(bprd) and NetBackup database manager daemon (bpdbm). If you change the serverlist on a Windows master server, stop, and restart the NetBackup Request Managerand NetBackup database manager services.

NetBackup status code: 38Message: could not get group information

Explanation: Could not get the group entry that describes a UNIX or Linux usergroup.

Recommended Action: Check the NetBackup Problems report for clues on whythe error occurred. For detailed troubleshooting information, create a debug logdirectory for the process that returned this status code. Then retry the operationand check the resulting debug log.

NetBackup status code: 39Message: client name mismatch

Explanation: The client used a name in a request to the NetBackup server thatdid not match the configured name in the policy on the server.

Recommended Action: Change one of the following so the two match: theNetBackup client name setting on the client (see the applicable NetBackup usersguide) or the one in the policy configuration on the server.

NetBackup status code: 40Message: network connection broken

Explanation: The connection between the client and the server was broken. Thisstatus code can also appear if the connection is broken between the master andthe media server during a backup.

Recommended Action: Do the following, as appropriate:

■ Try pinging the client from the server. If pinging is not possible, check forloose connections or other network problems.

■ Verify that the server list settings are correct on both the client and the server.If the backup involves a media server, verify that these entries are correct on

NetBackup status codes and messagesAbout NetBackup status codes and messages

184

both the master and the media server. For example, if a media server does nothave a server list entry for the master, it does not accept connections from themaster.

■ On Windows, the master server is designated on the Servers tab in theMaster Server Properties dialog box.See “Using the Host Properties window” on page 61.

■ On UNIX, Linux, and Macintosh systems the master server is the firstSERVER entry in the bp.conf file.

■ On NetWare target clients the master server name is the first SERVER entryin the bp.ini file.

If you change the server list on a UNIX or Linux master server, for the changesto take effect you must do the following: Stop and restart the NetBackupRequest daemon (bprd) and NetBackup database manager daemon (bpdbm). OnWindows, stop and restart the NetBackup Request Manager and NetBackupdatabase manager services.

■ Status code 40 can also be due to denial of a mount request by the operator.

■ This status code may occur if nbjm was unable to connect to bpbrm or tobpmount. Examine the nbjm unified log (originator ID 117) or the bpbrm or thebpmount legacy logs for more detail on the cause of the error.

NetBackup status code: 41Message: network connection timed out

Explanation: The server did not receive any information from the client for toolong a period of time.

Recommended Action: Do the following, as appropriate:

■ On UNIX, Linux, or Windows clients, check for the following problems withthe bpbkar client process.

On Windows clients: The bpbkar client process is not hung. Due to the filesand directories it scans, it has not replied to the server within the Client readtimeout or Clientconnecttimeout period. This error occurs during incrementalbackups when directories have thousands of unmodified files.For this case, use Host Properties on the NetBackup server to change Clientconnect timeout or Client read timeout. These settings are on the Timeoutsand Universal Settings tabs, respectively, in the Master Server Propertiesdialog box. The default for these timeouts is 300 seconds.See “Using the Host Properties window” on page 61.You can also monitor CPU utilization to determine if this condition exists.

185NetBackup status codes and messagesAbout NetBackup status codes and messages

The following information applies only to UNIX or Linux clients:

■ The bpbkar client process is hung on a file that has a mandatory lockingset. For this case, add the following to the client’s bp.conf file:

VERBOSE

And as root on the client run the following:

touch /usr/openv/netbackup/bpbkar_path_tr

/usr/openv/netbackup/logs/bpbkar

Then retry the operation. The names of the files are logged on the debuglog file in the/usr/openv/netbackup/logs/bpbkardirectory beforebpbkarprocesses them. The last file in the log is the file that causes problems.

Note: Also, use these procedures for other "unknown" bpbkar hangs.

If the problem is due to mandatory file locking, have NetBackup skip thelocked files. Set LOCKED_FILE_ACTION to SKIP in the/usr/openv/netbackup/bp.conf file on the client.

■ The bpbkar client process is not hung. Due to the files and directories itscans, it has not replied to the server within CLIENT_READ_TIMEOUT orCLIENT_CONNECT_TIMEOUT. This error occurs during backups whendirectories have thousands of unmodified files or during restores of thesparse files that have thousands of holes. For this case, try to add or modifythe CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT values in theserver’s /usr/openv/netbackup/bp.conf file. The default for theCLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if itis not specified.

Use your system’s ps command and monitor CPU utilization to help decidewhich of these conditions exist.When you finish the investigation of the problem, delete the/usr/openv/netbackup/logs/bpbkardirectory, since the log files can becomequite large and are not deleted automatically. Also delete/usr/openv/netbackup/bpbkar_path_tr so you do not generate larger logfiles than needed the next time you create directory/usr/openv/netbackup/logs/bpbkar.

■ On Windows systems, try the following:

■ Disable the following file:

install_path\VERITAS\NetBackup\bin\tracker.exe

NetBackup status codes and messagesAbout NetBackup status codes and messages

186

■ Repair hard drive fragmentation. Try an application that is called DiskeeperLite, which is part of the Windows Resource Kit.

■ Make sure that enough space is available in \temp.

■ If the server cannot connect to the client, do the following: Create bpcd orbpbkar (UNIX, Linux, and Windows only) debug log directories on the client.Then retry the operation and check the resulting logs. If these logs do notprovide a clue, create a bpbrm debug log on the server. Then retry the operationand check the resulting debug log.If the bpbrm log has entries similar to the following, the problem is in therouting configuration on the server:

bpbrm hookup_timeout: timed out waiting during the client hookup

bpbrm Exit: client backup EXIT STATUS 41: network connection

timed out

Verify that the client IP address is correct in the name service that is used. OnUNIX and Linux clients, if both the NIS and the DNS files are used, verify thatthey match.See “Resolving network communication problems” on page 40.

■ If you use an AIX token ring adapter and the routed daemon is running, thetimeout occurs because the token ring adapter creates dynamic routes. It thencauses the routed daemon to crash.

■ For a FlashBackup client, this error occurs if the file system being backed upis very large and has a very large number of files. It can also occur if a largenumber of concurrent data streams are active at the same time. To correct it,add CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file andset it to increase the timeout interval.

■ Make sure all recommended NetBackup patches are installed. Check theSymantec support Web site for current patch information.Go to www.support.symantec.com.Then select "NetBackup" followed by "files and updates".

■ Add the CLIENT_READ_TIMEOUT values to the master server, media server,and client when a NetBackup database extension product is installed. Thevalues should all be the same for each server. The value set is dependent onthe size of the database being backed up. More information onCLIENT_READ_TIMEOUT is available.See the NetBackup Administrator’s Guide, Volume II.

■ Make sure that enhanced authentication is configured correctly. For example,the following may result in status code 41: Host A is configured to use enhancedauthentication with host B, but host B is not configured to use enhanced

187NetBackup status codes and messagesAbout NetBackup status codes and messages

authentication with host A. In this case, connections from host B to host A arelikely to fail with status code 41. Connections from host A to B are likely tofail with authentication errors (status code 160).

NetBackup status code: 42Message: network read failed

Explanation: An attempt to read data from a socket failed.

Recommended Action: Do the following, as appropriate:

■ Verify that both the client and the server are operational.

■ Resolve any network communication problems.See “Resolving network communication problems” on page 40.

■ Check the Problems report for clues.

NetBackup status code: 43Message: unexpected message received

Explanation: The client and the server handshake were not correct.

Recommended Action: Do the following, as appropriate:

■ Verify that the correct version of software is running on the client and theserver.

■ To enable detailed debug logging, do the following:

■ On the server, create a bpbrm debug log directory.

■ On clients, create a bpcd debug log directory (created automatically onMacintosh clients).

■ Increase the amount of debug information to include in the logs.See “About using logs and reports” on page 81.

■ Retry the operation and examine the logs.If you use bpstart_notify scripts on UNIX, Linux, or Windows clients, verifythat messages are not written to stdout or stderr.

NetBackup status code: 44Message: network write failed

Explanation: An attempt to write data to a socket failed.

Recommended Action: Do the following, as appropriate:

NetBackup status codes and messagesAbout NetBackup status codes and messages

188

■ Check the Problems report for information about the error.

■ Verify that the client and servers are operational and connected to the network.

■ Create a debug log directory for the process that reported the problem and theoperation. Examine the resulting debug log file for detailed troubleshootinginformation.See “Resolving network communication problems” on page 40.

NetBackup status code: 45Message: request attempted on a non reserved port

Explanation: A try was made to access a client from a non-reserved port.

Recommended Action: Verify that the latest software is installed on the clientand server.

■ On UNIX and Linux NetBackup servers and clients, check the/usr/openv/netbackup/bin/version file.

■ On Windows NetBackup servers, check theinstall_path\netbackup\version.txt file or the AboutNetBackup item onthe Help menu.

■ On Microsoft Windows clients, check the AboutNetBackup item on the Helpmenu.

■ On NetWare target clients, check the Version entry in the bp.ini file.

■ On Macintosh clients, check the version file in the bin folder in the NetBackupfolder in the Preferences folder.

NetBackup status code: 46Message: server not allowed access

Explanation: The server tries to access a client, but access is blocked.

Possible causes are as follows:

■ The server is not listed on the client as a valid server.

■ The client was configured to require encrypted backups, but the encryptionattribute for the backup policy on the server was not selected.

■ The evaluation license for the NetBackup Encryption product has expired onthe server, but the NetBackup client was configured to require encryptedbackups. As a result, the server tries to make a non-encrypted backup of theclient. Since the client is configured to require encryption, the backup failed.

Recommended Action: Do the following, as appropriate:

189NetBackup status codes and messagesAbout NetBackup status codes and messages

■ If the server is a valid server but is not listed on the client, add its name to theclient’s server list:

■ On Windows clients in the SpecifyNetBackupMachines andPolicyTypedialog box, do the following: Add the server in the Servertouseforbackupsand restores drop-down list. To display this dialog box, start the Backup,Archive, and Restore interface on the client. Then click SpecifyNetBackupMachines and Policy Type on the File menu.

■ On UNIX, Linux, and Macintosh clients, add a SERVER entry in the bp.conffile.

■ On NetWare target clients, add a SERVER entry in the bp.ini file.

If you continue to have problems, more information is available:See “Resolving network communication problems” on page 40.See “Verifying host name and service entries” on page 49.

■ To make non-encrypted backups of the client, set CRYPT_OPTION on the clientto allowed or denied.Refer to the NetBackup Encryption Administrator’s Guide.

■ If the NetBackup encryption evaluation license has expired on the server andyou want to continue encrypting backups of the client, do the following:Purchase a permanent encryption license key and add it to the server. Afteryou add the permanent encryption license key, check the attributes of thebackup policy to make sure that encryption is selected.To check the validity of an evaluation license key, do the following:On Windows, go to the Help menu on the NetBackupAdministrationwindowon the NetBackup server and select License Keys. If the evaluation key is notlisted in the NetBackup License Keys window, the key has expired. Use thiswindow to add the new permanent encryption key.On UNIX and Linux, use the following command on the server:/usr/openv/netbackup/bin/admincmd/get_license_key

Select option f to list the active license keys and features. If the evaluationkey is not listed, the key has expired. Use this command to add the newpermanent encryption key.

NetBackup status code: 47Message: host is unreachable

Explanation: An attempt to connect to another machine failed.

Recommended Action: Do the following, as appropriate:

■ Verify that the name service (or services) used by the client are configured toresolve the host names of the NetBackup server correctly.

NetBackup status codes and messagesAbout NetBackup status codes and messages

190

■ Verify that the name service (or services) used by the server are configured toresolve the host name of the NetBackup client correctly.

■ Try to ping the client from the server and the server from the client.

■ If you continue to have problems, do the following:See “Resolving network communication problems” on page 40.

NetBackup status code: 48Message: client hostname could not be found

Explanation: The system function gethostbyname() failed to find the client’shost name.

Recommended Action: Verify that the client name is correct in the following:

■ The NetBackup policy configuration on the master server.■

■ The General tab in the following dialog boxes: NetBackup Client Propertiesand Specify NetBackup Machines and Policy Type (on Microsoft Windowsand NetWare nontarget clients). To display these dialog boxes, start theBackup, Archive, and Restore interface on the client. For the General tab,click NetBackup Client Properties on the File menu; click SpecifyNetBackup Machines and Policy Type on the File menu.

■ The bp.conf file on UNIX, Linux, and Macintosh clients.

■ The bp.ini file on NetWare target clients.

■ On clients and servers, verify that the name service is set up to resolve theNetBackup client names correctly.On UNIX and Linux clients, verify that the client’s host name is in the/etc/hosts file or the YP hosts file or NIS maps.

NetBackup status code: 49Message: client did not start

Explanation: The client failed to start up correctly.

Recommended Action: Do the following, as appropriate:

■ Make sure that software is installed on the client and it is the correct version.If necessary, reinstall the client software.

■ Check for full file systems on the client.

■ Enable detailed debug logging on the client by doing one of the following:

■ Create bpcd and bpbkar (UNIX, Linux, and Windows only) debug logdirectories.

191NetBackup status codes and messagesAbout NetBackup status codes and messages

■ On a UNIX or Linux client, add the VERBOSE option to the/usr/openv/netbackup/bp.conf file.

■ On PC clients, increase the debug or log level.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

Retry the operation and examine the resulting logs.

■ On UNIX or Linux systems, use the UNIX sum command to check for corruptbinaries.

NetBackup status code: 50Message: client process aborted

Explanation: The client backup terminated abnormally. For example, this erroroccurs if a NetBackup master or media server is shut down or rebooted when abackup or restore is in progress.

Recommended Action: Do the following, as appropriate:

■ Enable detailed debug logging.

■ Create a bpbkar debug log directory (UNIX, Linux, and Windows clientsonly).

■ Create a bpcd debug log directory. (This log is created automatically onMacintosh clients.)

■ On UNIX and Linux clients, add the VERBOSE option to the/usr/openv/netbackup/bp.conf file.

■ On PC clients, increase the debug or log level.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

Retry the operation and examine the resulting logs.

■ This error may occur if nbjm terminated while a backup job was running.Examine the unified logging files on the NetBackup server for nbjm (117) formore detail on the error. All unified logging is written to /usr/openv/logs

(UNIX and Linux) or install_path\NetBackup\logs (Windows).

■ On UNIX and Linux clients, check for core files in the / directory.

■ On UNIX and Linux clients, check the system log (/usr/adm/messages onSolaris) for system problems.

■ This problem can sometimes be due to a corrupt binary.

NetBackup status codes and messagesAbout NetBackup status codes and messages

192

On UNIX and Linux clients, use the UNIX sum command to check the bpcd,bpbkar, and tar binaries, which are located in /usr/openv/netbackup/bin onthe client. Reinstall them if they are not the same as in the client directoryunder /usr/openv/netbackup/client on the server.

On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, andtar32.exe files, which are located in the install_path\NetBackup\bin folderon the client.

Reinstall the client if these files are as follows:

■ Not the same size as on other Windows clients

■ Not at the same release level

■ Do not have the same NetBackup patches as other Windows clients

NetBackup status code: 51Message: timed out waiting for database information

Explanation: The catalog process did not respond within five minutes.

Recommended Action: Do the following, as appropriate:

■ Verify that the NetBackup database manager service or daemon is running.

■ Verify that the file system that contains the NetBackup catalogs has enoughspace.

■ Create bpbrm and bpdbm debug log directories on the server and retry theoperation.

■ Look in the debug log files to find more information on the problem.

NetBackup status code: 52Message: timed out waiting for media manager to mount volume

Explanation: The requested volume was not mounted before the timeout expired.This error can also occur if the volume is a cleaning tape but was not specified asa cleaning tape.

Another possible cause: the last available drive has a mount request for anon-backup (such as a restore). Then a backup that requires the same drive isinitiated before the mount completes. This error is due to the drive not beingreported as busy until the mount completes.

Recommended Action: Do the following, as appropriate:

■ Verify that the requested volume is available and an appropriate drive is readyand in the UP state.

193NetBackup status codes and messagesAbout NetBackup status codes and messages

■ If this error occurs during a read operation (restore, duplicate, verify), thedrives could be busy. Increase the timeout for the media mount that theNetBackup global attribute specifies, to allow more time to mount and positionthe media.

■ Verify that the tape is not a cleaning tape that is configured as a regular volume.

■ When an Automated Cartridge System controls the robot, verify that the ACSLSsystem is up.

■ If it is an initial installation, a procedure is available.See “Resolving common configuration problems” on page 28.

■ On Windows, check the Event Viewer Application log for the error messagesthat indicate why the tape mount did not complete. On UNIX and Linux, checkthe system log.

NetBackup status code: 53Message: backup restore manager failed to read the file list

Explanation: The backup and restore manager (bpbrm) did not read the list offiles to back up or restore.

RecommendedAction: Verify that the server software was installed correctly onall NetBackup servers. If that is not the problem, do the following:

■ Create bpbrm debug log directories on the server.

■ On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conffile. On a Windows NetBackup server, set the Global logging level option onthe Logging tab in the Master Server Properties dialog box.To display this dialog box, refer to the following topic:See “Using the Host Properties window” on page 61.Increase the unified logging levels by using thevxlogcfg command as explainedin the following procedure:See “Configuring and using unified logging” on page 94.

■ Retry the operation and check the resulting debug logs for detailedtroubleshooting information.

NetBackup status code: 54Message: timed out connecting to client

Explanation: The server did not complete the connection to the client. The acceptsystem or winsock call timed out after 60 seconds.

NetBackup status codes and messagesAbout NetBackup status codes and messages

194

Some third-party software packages (for example, a personal firewall product)can affect the TCP/IP stack in Windows. This action can cause a loss of connectionbetween the NetBackup server and the bpcdprocess on the client. NetBackup triesto set SO_REUSEADDR (allow local address reuse) on the inbound socketconnection so that the port can be handed off from bpinetd.exe (the NetBackupClient Service) to bpcd.exe. Some products may not allow this functionality dueto the various methods that can be used to violate system security.

Recommended Action: Do the following, as appropriate:

■ For a Macintosh or NetWare target client: Verify that the server does not tryto connect when a backup or restore is already in progress on the client. Theseclients can handle only one NetBackup job at a time.On a Macintosh, check for activity by examining the NetBackupListen file inthe following folder on the startup disk of the Macintosh client:

:System Folder:Preferences:NetBackup:logs:inetd:log.mmddyy

■ Perform the following procedure:See “Resolving network communication problems” on page 40.

■ On UNIX and Linux clients, verify that the /usr/openv/netbackup/bin/bpcdbinary exists and that it is the correct size.

■ Check the /etc/inetd.conf file to make sure the bpcd path is correct in thefollowing entry:

bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

■ On the systems that include the following, make sure that the client name isin the master’s /etc/hosts file: NetBackup master, media, and clients (withNetBackup database extension products installed on one or more clients).

■ Completely uninstall the third-party software package on the client that causesthe failure. Or, contact the software manufacturer to investigate if otherconfiguration options or workarounds are possible.

NetBackup status code: 55Message: permission denied by client during rcmd

Explanation: The UNIX or Linux client does not have the server’s name in its/.rhosts file.

RecommendedAction: Add the server name to the /.rhosts file on the UNIX orLinux client.

195NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 56Message: client’s network is unreachable

Explanation: An error reported that the client could not reach the host(WSAENETUNREACH on Windows or ENETUNREACH on UNIX and Linux) on asystem call.

RecommendedAction: Try to ping the client from the server. Check the IP addressfor the client. If you still have problems, talk to your network administrator.

NetBackup status code: 57Message: client connection refused

Explanation: The client refused a connection on the port number for bpcd.

This error can occur because of the following:

■ No process listening activity occurs on the bpcd port

■ The number of connections to the bpcd port is more than the networksubsystem can handle with the listen() call

Recommended Action: Do the following, as appropriate:

■ For Windows NetBackup servers:

■ Make sure the NetBackup client software is installed.

■ Verify that the bpcd and bprd port numbers in the%SystemRoot%\system32\drivers\etc\services file on the server matchesthe setting on the client.

■ Verify that the NetBackup Client Service Port number and NetBackupRequestServicePort number on the Network tab in the NetBackupClientProperties dialog match the bpcd and bprd settings in the services file.To display this dialog, start the Backup, Archive, and Restore interface onthe server and click NetBackup Client Properties on the File menu.The values on the Network tab are written to the services file when theNetBackup Client service starts.

■ Verify that the NetBackup client service is running.

■ Use the following command to see if the master server returns correctinformation for the client:

install_path\VERITAS\NetBackup\bin\bpclntcmd -pn

■ On UNIX and Linux servers, do the following:

NetBackup status codes and messagesAbout NetBackup status codes and messages

196

Make sure the NetBackup client software is installed.■

■ Verify that the bpcd port number on the server (either NIS services mapor in /etc/services) matches the number in the client’s services file.

■ For a Macintosh or NetWare target client, verify that the server is not tryingto connect when a backup or restore is already in progress on the client. Theseclients can handle only one NetBackup job at a time.

■ Additional help is available.See “Resolving network communication problems” on page 40.

NetBackup status code: 58Message: can’t connect to client

Explanation: The server was unable to connect to the client.

Recommended Action: Resolve network communication problems.

See “Resolving network communication problems” on page 40.

NetBackup status code: 59Message: access to the client was not allowed

Explanation: The master or the media server tries to access the client, but theclient does not recognize the server as a valid server.

For the Enterprise Vault Agent: The names of all of the media servers among theEnterprise Vault servers are not specified in the client configuration.

Recommended Action: Do the following, as appropriate:

■ If the server is a valid server, verify that it is in the server list on the client. Ifnecessary add it as follows:

■ On Windows clients: Add the server on the Server to use for backups andrestores drop-down in the SpecifyNetBackupMachines andPolicyTypedialog box. To display this dialog box, start the Backup, Archive, and Restoreinterface on the client. Then click SpecifyNetBackupMachinesandPolicyType on the File menu.

■ On UNIX and Linux, and Macintosh clients: add a SERVER entry in thebp.conf file.

■ On NetWare target clients: add a SERVER entry in the bp.ini file.

If you change the server list on a UNIX or Linux master server, do the followingfor the changes to take effect: stop and then restart the NetBackup Requestdaemon (bprd) and NetBackup database manager daemon (bpdbm). On Windows,

197NetBackup status codes and messagesAbout NetBackup status codes and messages

stop and restart the NetBackup Request Manager and NetBackup DatabaseManager services.

■ On Windows clients, enable bpinetd debug logging as follows:

■ Create a bpinetd debug log directory on the client.

■ Increase the debug or log level.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

■ Retry the backup and examine the resulting logs to determine the cause ofthe failure.

■ On all clients, enable bpcd debug logging as follows:

■ Create a bpcd debug log directory on the client.

■ On a UNIX or Linux client, add the VERBOSE option to the/usr/openv/netbackup/bp.conf file.

■ On PC clients, increase the debug or log level as explained in the debug logtopics in Chapter 3.

■ Retry the backup and examine the resulting logs to determine the cause ofthe failure.

■ Check the bpcd debug log to determine the server’s peer name and whatcomparisons are made.The bpcd process compares NetBackup server list entries to the peer name ofthe server that tries the connection. It rejects the connection if the names aredifferent. If necessary, change the server list entry on the client to match thepeer name.

■ On Windows clients, check the following:

■ Verify that NetBackup for Windows software was installed under a Windowsadministrator account.If NetBackup is under another type of account, reinstall it under anadministrator account. The installation completes successfully under anon-administrator account except for the following: the NetBackup Clientservice is not added to Windows and the NetBackup server cannot accessthe client.

■ Verify that the Windows TCP/IP service specifies the domain server thatresolves names for the subnet that contains the NetBackup servers.UNIX, Linux, and Windows clients are frequently not on the same subnetand use different domain servers. When this condition exists, NetBackup

NetBackup status codes and messagesAbout NetBackup status codes and messages

198

servers and Windows clients may be able to ping one another, but the serverstill cannot access the Windows client.

■ The preceding items may not resolve this problem.See “Resolving network communication problems” on page 40.

■ If NetBackup use multiple network interfaces with media servers, make surethe interface names appear in the client’s /usr/openv/netbackup/bp.conffile.

■ For the Enterprise Vault Agent: See the Troubleshooting section of theNetBackup for Enterprise Vault Agent Administrator’s Guide.

NetBackup status code: 60Message: client cannot read the mount table

Explanation: The backup process on the client did not read the list of mountedfile systems.

Recommended Action: Do the following, as appropriate:

■ Run a df to see if the system can read the mount table.

■ On an SCO system, code 60 can occur because the mount-point path nameexceeds 31 characters (the maximum number on an SCO system). The bpbkardebug log on the client shows a message similar to the following:

bpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406

To eliminate these errors for future backups, create a mount point with ashorter name and symbolically link the long name to the short name.

■ For detailed troubleshooting information, create a bpbkar debug log directory.Then retry the operation and check the resulting log.

NetBackup status code: 63Message: process was killed by a signal

Explanation: A kill signal was sent to the client process.

RecommendedAction: The usual cause for this error is that someone intentionallyterminated a backup.

NetBackup status code: 64Message: timed out waiting for the client backup to start

199NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The client did not send a ready message to the server within theallotted time.

Recommended Action: Do the following, as appropriate:

■ On all clients, enable bpcd debug logging as follows:

■ Create a bpcd debug log directory on the client.

■ On a UNIX or Linux client, add the VERBOSE option to the/usr/openv/netbackup/bp.conf file.

■ On PC clients, increase the debug or log level.See “How to set logging levels on PC clients” on page 122.

■ On a UNIX, Linux, or Windows client, create the bpbkar debug log directoryon the client.

■ On Windows clients, verify that the NetBackup Client service is running.

■ On a UNIX or Linux client, use the ps command to check for a client processthat uses too much CPU time.

■ Retry the backup and examine the debug logs for clues on the cause of thefailure.

NetBackup status code: 65Message: client timed out waiting for the continue message from the mediamanager

Explanation: The tape manager, bptm, reported that the media did not load andposition within the allotted time.

Recommended Action: Verify that the requested volume is available and therequired device is in an UP state.

■ Create a bptm debug log directory on the server.

■ On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conffile. On a Windows NetBackup server, set the Verbose logging level option onthe Logging tab in the Master Server Properties dialog box.See “Using the Host Properties window” on page 61.

■ Retry the operation and check the bptm debug log file for information on thedrive, robot, and tape that causes the timeout.

■ On a Windows NetBackup server (master or media): check the Event ViewerApplication log for the error messages that indicate why the tape mount didnot complete.

NetBackup status codes and messagesAbout NetBackup status codes and messages

200

NetBackup status code: 66Message: client backup failed to receive the CONTINUE BACKUP message

Explanation: The client bpbkar process did not receive the message from theserver that indicates that the server is ready to continue.

Recommended Action: Do the following, as appropriate:

■ Verify that the server did not crash.

■ On UNIX, Linux, and Windows clients, enable bpbkar debug logging.

■ Create a bpbkar debug log directory.

■ On a UNIX or Linux client, add the VERBOSE option to the bp.conf file. Ona Windows client, set Verbose on the TroubleShooting tab in the NetBackupClient Properties dialog box. To display this dialog box, start the Backup,Archive, and Restore interface on the client. Then select NetBackupClientProperties from the File menu.

■ On other PC clients except Macintosh, create a debug log directory for bpcd(the bpcd log is created automatically on Macintosh).

Increase the amount of information that appears in the logs.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

■ On the master server, create bpbrm debug log directories. Increase the logginglevel for the diagnostic and debug logs for nbpem, nbjm, and nbrb.Use the vxlogcfg command as described in the following topic:

See “Configuring and using unified logging” on page 94.

■ Retry the operation and check the resulting debug logs.

NetBackup status code: 67Message: client backup failed to read the file list

Explanation: The client did not read the list of files to back up.

Recommended Action: Do the following, as appropriate:

■ Verify that the server did not crash.

■ Set up debug logging.

■ On the server, create a bpbrm debug log directory.

■ On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.

■ On other PC clients except Macintosh, create a debug log directory for bpcd(the bpcd log is created automatically on Macintosh).

201NetBackup status codes and messagesAbout NetBackup status codes and messages

Increase the amount of information that appears in the logs.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

■ Retry the operation and check the resulting debug logs.

NetBackup status code: 68Message: client timed out waiting for the file list

Explanation: The client did not receive the list of files to back up within theallotted time. This list comes from the server.

Recommended Action: Do the following, as appropriate:

■ Verify that the server did not crash.

■ Set up debug logging.

■ On the server, create a bpbrm debug log directory.

■ On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.

■ On other PC clients except Macintosh, create a debug log directory for bpcd(the bpcd log is created automatically on Macintosh).

Increase the amount of information that appears in the logs.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

■ Retry the operation and check the resulting debug logs.

NetBackup status code: 69Message: invalid filelist specification

Explanation: The file list from the server had invalid entries.

For the Enterprise Vault Agent: A policy contains directives that cannot bespecified together in the same policy.

Recommended Action: Do the following, as appropriate:

Check the policy file list. If wildcards are used, verify that the bracket characters([ and ]) in the list match. If the file list contains UNC (Universal NamingConvention) names, ensure they are properly formatted.

This error can occur if nbjm was running and a Sharepoint job re-discovery returnsa 0 or 1 and the policy file list is empty. Examine the nbjm unified log (originatorID 117) for more detail on the cause of the error.

For NetBackup Snapshot Client only:

NetBackup status codes and messagesAbout NetBackup status codes and messages

202

In an off-host backup (NetBackup Media Server or Third-Party Copy Device),code 69 may indicate that the file list contains the ALL_LOCAL_DRIVES entry.NetBackup does not support the ALL_LOCAL_DRIVES entry for off-host backup.Remove the ALL_LOCAL_DRIVES entry from the file list.

For the Enterprise Vault Agent only:

See the Troubleshooting section of the NetBackup for Enterprise Vault AgentAdministrator’s Guide.

NetBackup status code: 70Message: an entry in the filelist expanded to too many characters

Explanation: The wildcards, which were used in one of the file list entries,specified too many files.

RecommendedAction: Change the wildcards in the file list to specify fewer files.

NetBackup status code: 71Message: none of the files in the file list exist

Explanation: The files in the file list did not match any of the files on the client.This error can occur with only one file in the file list and the file cannot be backedup due to an I/O error.

Recommended Action: Do the following, as appropriate:

■ Verify that the correct file list is specified for this client.

■ On Windows clients, verify that the account used to start the NetBackup Clientservice has read access to the files.If you back up a network drive or a UNC (universal naming convention) path,do the following: use the Services application in the Windows Control Panelto verify that the NetBackup Client service does not start under the SYSTEMaccount. The SYSTEM account cannot access network drives.To back up network drives or UNC paths: change the NetBackup Client servicestartup to log in as a user that has permission to access network drives.

■ Check the All Log Entries report for clues.

■ To set up debug logging, do one of the following:

■ On UNIX, Linux, and Windows clients, create a debug log directory forbpbkar.

■ On other PC clients except Macintosh, create a debug log directory for bpcd(the bpcd log is created automatically on Macintosh).

203NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Increase the amount of information that appears in the logs.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

■ Retry the operation and check the resulting debug logs.

■ On Novell systems, do one of the following:

■ For the nontarget version of NetBackup for NetWare, the backup policytype must be "NetWare," and the files list should include a forward slash(/) only. There should be nothing else in the files list.To check the policy type and files list, start Backup Policy Managementand right-click the name of a policy. Click the Attributes tab to check thepolicy type; click the Files tab to check the contents of the files list.

■ For the target version, the backup policy type must be "Standard," and thepolicy files list must be formatted as follows: /target_namewhere a forwardslash precedes the variable target_name.To check the policy type and files list, start Backup Policy Managementand right-click the name of a policy. Click the Attributes tab to check thepolicy type; click the Files tab to check the contents of the files list.For the target version, the following NetWare message may be anotherindicator of incorrect policy type (this message appears in the Novell client’sbpcd log):

unable to connect to service, scheduled access not specified

Make sure the policy type is set to "Standard."

■ For either the target or the nontarget version of NetBackup for NetWare,make sure that the following are all at the same version: the NetWareloadable modules (NLMs) SMDR and TSAxxx (such as TSAFS and TSANDS).If they are not at the same version, status 71 may occur.

NetBackup status code: 72Message: the client type is incorrect in the configuration database

Explanation: The policy type attribute in the policy configuration indicates thatthe client is one type, but the installed software is for another type.

Recommended Action: Verify that the policy type attribute for the policy iscorrect.

NetBackup status code: 73Message: bpstart_notify failed

NetBackup status codes and messagesAbout NetBackup status codes and messages

204

Explanation: The bpstart_notify script returned a nonzero exit code.

Recommended Action: Check the bpstart_notify script on the client to see ifit performs as expected.

NetBackup status code: 74Message: client timed out waiting for bpstart_notify to complete

Explanation: The bpstart_notify script on the client takes too long.

Recommended Action: Try to speed up the bpstart_notify script or set theBPSTART_TIMEOUT on the server to a value that is larger than the default. SetBPSTART_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server. On aWindows NetBackup server, use Host Properties to set Backup Start NotifyTimeout.

See “Using the Host Properties window” on page 61.

NetBackup status code: 75Message: client timed out waiting for bpend_notify to complete

Explanation: The bpend_notify script on the client takes too long.

Recommended Action: Try to speed up the bpend_notify script or setBPEND_TIMEOUT on the server to a value that is larger than the default. SetBPEND_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server. On aWindows NetBackup server, use Host Properties to set BackupEndNotifyTimeout.

NetBackup status code: 76Message: client timed out reading file

Explanation: A fifo was specified in the file list and no data was produced on thefifo within the allotted time.

RecommendedAction: Make sure that the process that is to produce the data onthe named fifo is started correctly. Add an entry to the/usr/openv/netbackup/bp.conf file on the server to set CLIENT_READ_TIMEOUTto a larger value than the default.

NetBackup status code: 77Message: execution of the specified system command returned a nonzero status

Explanation: An immediate command returned a nonzero status.

Recommended Action: Do the following, as appropriate:

205NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Verify that the command is specified correctly.

■ For NetBackup Snapshot Client only, do the following:The policy file list may contain the files that do not reside within a file systemthat was designated as the snapshot source. To apply a snapshot method tothe backup of individual files, the snapshot source must be a file system. (Itcannot be a raw partition or Volume Manager volume.) The files in the policyfile list must reside within that file system.

■ Run the command manually to see if the wanted result is produced.

■ For detailed troubleshooting information, set up debug logging, as follows:

■ On UNIX, Linux, and Windows clients, create a debug log directory forbpbkar.

■ On other PC clients except Macintosh, create a debug log directory for bpcd(the bpcd log is created automatically on Macintosh).

■ Increase the amount of information that appears in the logs.See “How to set logging levels on UNIX clients” on page 118.See “How to set logging levels on PC clients” on page 122.

■ Retry the operation and check the resulting debug log.

NetBackup status code: 78Message: afs/dfs command failed

Explanation: Indicates an AFS vos command failure.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems Report for additional information on why thecommand failed.

■ The bpbkar debug log shows the command that was run. Create a debug logdirectory for bpbkar. Retry the operation and retry the resulting debug log.

■ Try running the vos command manually to duplicate the problem.

NetBackup status code: 79Message: unsupported image format for the requested database query

Explanation: One or more of the images to be synthesized was encrypted. Theseimages cannot be synthesized.

Recommended Action: Ensure that none of the images was encrypted.

NetBackup status codes and messagesAbout NetBackup status codes and messages

206

NetBackup status code: 80Message: Media Manager device daemon (ltid) is not active

Explanation: If the server is UNIX or Linux, the NetBackup device managerdaemon, ltid, is not running. If the server is Windows, the NetBackup DeviceManager service is not running.

Recommended Action: Do the following, as appropriate:

■ On Windows, use the Activity Monitor or the Services application in theWindows Control Panel to see if the NetBackup Device Manager service isrunning. If it is not running, start it. To enable verbose logging, place VERBOSEon a line by itself in the install_path\Volmgr\vm.conf file before you startthe service.

■ On UNIX and Linux, use vmps to see if ltid is running and if necessary startltid in verbose mode with the following command:

/usr/openv/volmgr/bin/ltid -v

Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create thevm.conf file if necessary.

■ On UNIX and Linux, check the system logs to verify that ltid starts.

Note:On UNIX and Linux systems, ltid, and on Windows systems, the NetBackupDevice Manager service, is used only if devices are attached to the system.

NetBackup status code: 81Message: Media Manager volume daemon (vmd) is not active

Explanation: The tape manager (bptm) did not communicate with the NetBackupVolume Manager (vmd). This communication is required for most operations.

RecommendedAction: On UNIX and Linux, verify that the Media Manager devicedaemon (ltid) and the NetBackup Volume Manager (vmd) are running. Start themif necessary.

On Windows, verify that both the NetBackup Device Manager service and theNetBackup Volume Manager service are running. Start them if necessary.

Note: ltid or the NetBackup Device Manager service is used only if devices areattached to the system.

207NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 82Message: media manager killed by signal

Explanation: Another process or a user terminated the tape manager (bptm) ordisk manager (bpdm).

Recommended Action: This error should not occur in normal operation. If youwant to terminate an active backup, use the NetBackup Activity Monitor.

When you back up a DomainOS client, this error occurs after the server has notreceived anything on the socket for at least 300 seconds. It causes a client readtimeout and breaks the connection. The bpbkar debug log has an entry similar tothe following:

13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET

Connection reset by peer (UNIX/errno status)

To resolve the problem, increase the CLIENT_READ_TIMEOUT value. In this instance,set the value to 900.

NetBackup status code: 83Message: media open error

Explanation: The tape manager (bptm) or disk manager (bpdm) did not open thedevice or file that the backup or restore must use.

Recommended Action: For additional information, check the following:

■ NetBackup Problems report

■ Event Viewer Application log (Windows)

■ System log (UNIX and Linux)

■ Typically, this status code indicates a drive configuration problem that allowsmore than one process at a time to open the device. On UNIX and Linux, theproblem may be due one or more of the following:

■ Two (or more) devices were configured that are the same physical device(for different densities perhaps). Verify that none of the /dev files thatwere used for these devices have the same major or minor numbers.

■ Links exist in the file system that allow users access to the drives.

■ The configuration for the drives was modified (in the administratorinterface or vm.conf) and the Media Manager device daemon, ltid, wasnot restarted. Verify the configuration and then start ltid.

On Windows, the problem may be that the Media and Device Managementdevice configuration was modified but the NetBackup Device Manager service

NetBackup status codes and messagesAbout NetBackup status codes and messages

208

was not restarted. Verify the configuration and restart the NetBackup DeviceManager service.

■ On Windows, make sure the tapes are not write protected.

■ For detailed troubleshooting information:

■ Create a debug log directory for bpdm (if the device is disk) or bptm (if thedevice is tape).

■ On UNIX and Linux, restartltid in the verbose mode by running thefollowing:

/usr/openv/volmgr/bin/ltid -v

Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Createthe vm.conf file if necessary.

■ On Windows, enable verbose logging by adding VERBOSE on a line by itselfin the install_path\Volmgr\vm.conf file. Then, stop and restart theNetBackup Device Manager service.

■ Retry the operation and check the resulting debug log files.

■ On Windows systems, look at theinstall_path\VERITAS\NetBackup\db\media\errors log for a drive thatfrequently produces errors.On UNIX and Linux systems, look at the/usr/openv/netbackup/db/media/errors log (which is also included inthe/usr/openv/netbackup/bin/goodies/support/support script output)for a drive that frequently produces errors.

NetBackup status code: 84Message: media write error

Explanation: The system’s device driver returned an I/O error while NetBackupwrote to removable media or a disk file.

Recommended Action: Do the following, as appropriate:

■ For NetBackup Snapshot Client only:If the following message appears in the /usr/openv/netbackup/bptm log, andthe values for key, asc, and ascq are all zero (0x0) as shown in this examplemessage:

tape error occurred on extended copy command, key = 0x0, asc =

0x0, ascq = 0x0

209NetBackup status codes and messagesAbout NetBackup status codes and messages

your host-bus adapter and its driver are probably not supported by NetBackupSnapshot Client. The host-bus adapters supported in the release are listed inthe NetBackup Release Notes.

■ For additional information, check the following:

■ NetBackup Problems report to determine the device or media that causedthe error

■ System and error logs for the system (UNIX and Linux)

■ Event Viewer Application and System logs (Windows)

■ If NetBackup writes backups to a disk file, verify the following: the fragmentsize that is configured for the disk storage unit is not greater than the maximumfile size that the operating system specifies.

■ On Windows, make sure the tapes are not write protected.

■ If bpbackupdb was used to back up the NetBackup catalog to a disk path on aUNIX or Linux system, do the following:The image you try to write may be greater than the maximum file size thatthe operating system specifies. Tape files do not have this limit.

■ If the media is tape, check for the following:

■ A defective or a dirty drive. Clean it or have it repaired (refer to the tpcleancommand for robotic drives).

■ The wrong media type. Verify that the media matches the drive type youuse.

■ Defective media. If it is defective, use the bpmedia command to set thevolume to the FROZEN state so it is not used for future backups.

■ Incorrect drive configuration. Verify the Media and Device Managementand system configuration for the drive.For example, on UNIX and Linux the drive may be configured for fixedmode when it must be variable mode.See the NetBackup Device Configuration Guide for more information.This configuration often results in the media being frozen with the message"too many data blocks written, check tape and drive block sizeconfiguration."See “Troubleshooting frozen media” on page 63.

NetBackup status code: 85Message: media read error

NetBackup status codes and messagesAbout NetBackup status codes and messages

210

Explanation: The system device driver returned an I/O error while NetBackupreads from tape or a disk file.

Recommended Action: For additional information, check the following:

■ NetBackup Problems report to determine the device or media that caused theerror

■ System and error logs for the system (UNIX and Linux)

■ Event Viewer Application and System logs (Windows)

■ Check for the following:

■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean

command for cleaning).

■ Incorrect drive configuration. Verify the Media and Device Managementand system configuration for the drive.For example, on UNIX and Linux, the drive may be configured for fixedmode when it must be variable mode. More information is available.See the NetBackup Device Configuration Guide.

■ Defective media. In this case, you may not be able to recover all the dataon the media. Use the bpmedia command to set the volume to the FROZENstate so it is not used for future backups.See “Troubleshooting frozen media” on page 63.

■ The wrong media type. Verify that the media matches the drive type youuse.

NetBackup status code: 86Message: media position error

Explanation: The system’s device driver returned an I/O error while NetBackupwas positioning the tape media.

Recommended Action: For additional information, check the following:

■ NetBackup Problems report to determine the device or media that caused theerror

■ System and error logs for the system (UNIX and Linux)

■ Event Viewer Application and System logs (Windows)

■ Check for the following:

■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean

command for cleaning).

211NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Incorrect drive configuration. Verify the Media and Device Managementand system configuration for the drive.For example, on UNIX and Linux, the drive may be configured for fixedmode when it must be variable mode.See the NetBackup Device Configuration Guide for more information.

■ Defective media. In this case, some data may be lost. Use the bpmedia

command to set the volume to the FROZEN state so it is not used for futurebackups.See “Troubleshooting frozen media” on page 63.

■ The wrong media type. Verify that the media matches the drive type youuse.

NetBackup status code: 87Message: media close error

Explanation: The system’s device driver returned an I/O error while NetBackupclosed a tape.

Recommended Action: For additional information, check the following:

■ NetBackup Problems report to determine the device or media that caused theerror

■ System and error logs for the system (UNIX and Linux)

■ Event Viewer Application and System logs (Windows)

■ Check for the following:

■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean

command for cleaning).

■ Defective media. In this case, some data may be lost. Use the bpmedia

command to set the volume to the FROZEN state so it is not used for futurebackups.See “Troubleshooting frozen media” on page 63.

NetBackup status code: 89Message: problems encountered during setup of shared memory

Explanation: The NetBackup processes use shared memory for some operations.This status is returned when an error is encountered in the initialization of theshared memory by the operating system’s APIs.

RecommendedAction: Check for a shared memory problem. This error can occurif the system cannot allocate enough shared memory. It usually occurs with

NetBackup status codes and messagesAbout NetBackup status codes and messages

212

multiplexing, which increases the amount of shared memory required for theoperation. An entry similar to the following may be seen in a NetBackup log orreport:

system cannot allocate enough shared memory

If you see this type of message, refer to your platform vendor documentation forinstructions on how to increase shared memory on your system.

For older levels of Solaris: you may need to change one or more default SystemV Shared Memory settings to prevent jobs failing with "system cannot allocateenough shared memory," as follows.

■ For Solaris 9, the default shminfo_shmmax value is 8 megabytes. You can placethe following line in your /etc/system file to increase this setting. A value of32 megabytes has been used in this example. Your system may require a greatervalue under some circumstances such as a high value for the NetBackupmultiplexing parameter. According to Sun Microsystems documentation,setting this parameter to its maximum possible value has no side effects. (Thisparameter is not applicable to Solaris 10).

set shmsys:shminfo_shmmax=33554432

■ For Solaris 9, the default shminfo_shmmni value is 100. You can place thefollowing line in your /etc/system file to increase this setting. The defaultvalue is usually sufficient for NetBackup. In some circumstances, such asinstalling a NetBackup media server on a large database server, this settingmay need to be increased. A value of 220 has been used in this example. (Thisparameter is not applicable to Solaris 10).

set shmsys:shminfo_shmmni=220

Note: If you modify any of these values in the /etc/system file, you must rebootthe system with boot -r for the new settings to take effect.

Refer to your vendor documentation for detailed instructions on how to modifythese values. Note that these shminfo parameters are not applicable to Solaris10.

NetBackup status code: 90Message: media manager received no data for backup image

213NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The tape manager (bptm) or disk manager (bpdm) received no datawhen it performed a backup, archive, or duplication. This error can occur forincremental backups where no data was backed up because no files have changed.

Recommended Action: Do the following, as appropriate:

■ Check the All Log Entries report.

■ For detailed debug information, create bpdm or bptm debug log directories onthe server. If the client is Windows, also create a bpbkar debug log directoryon the client. Retry the operation and check the resulting debug logs.

■ For additional information, check the following:

■ NetBackup Problems report to determine the device or media that causedthe error

■ System and error logs for the system (UNIX and Linux)

■ Event Viewer Application log (Windows)

■ Verify the Media and Device Management and system configuration for thedrive.For example, on UNIX and Linux, the drive may not be set for variable modein a case where NetBackup requires that mode.Check the NetBackup Device Configuration Guide for drive configurationinformation.

■ Verify that the Media and Device Management configuration for the backupdevice matches what is specified for the storage unit in the NetBackup policy.

■ Verify that you use the correct media in the drive.

■ For detailed debug information, create a bpdm or bptm debug log directory(whichever applies) on the server. If the client is Windows, also create a bpbkardebug log directory on the client. Retry the operation and check the resultingdebug logs.

■ If the error occurred during duplication or a Vault session that uses anAlternate Read Server to perform duplication, do the following: verify that theAlternate Read Server has access to the source media.

NetBackup status code: 91Message: fatal NB media database error

Explanation: The tape manager (bptm) received an error while it read or updatedits media catalog.

Recommended Action: Do the following, as appropriate:

NetBackup status codes and messagesAbout NetBackup status codes and messages

214

■ Check the All Log Entries report for more information.

■ Check the NetBackup Media Lists report to see if the catalog is intact. If thecatalog is not intact, you may want to reload it from the latest NetBackupcatalog backup volume.

■ Verify that the disk partition on which the catalog resides has enough space.

■ If these actions do not explain the problem, check the NetBackup Problemsreport.

■ For detailed troubleshooting information, create a bptm debug log directoryon the server and retry the operation. Check the resulting debug log file.

■ Contact customer support and send appropriate problem and debug logsections.

NetBackup status code: 92Message: media manager detected image that was not in tar format

Explanation: When you performed a restore, the tape manager (bptm) or diskmanager (bpdm) did not find a tar header at the offset it expected.

Recommended Action: Do the following, as appropriate:

■ Perform a bpverify of the affected image to determine if it is written correctly.

■ Check the NetBackup Problems report for additional information about theerror.

■ Verify the Media and Device Management and system configuration for thedrive.For example, on some UNIX and Linux systems if you do not configure thedrive for variable-mode block size writes, the following occurs: the backupimages that write to the media produce this error when you attempt to restorethe image.

The following sequence of events occurs:

■ Backup succeeds

■ Verify succeeds

■ Restore fails

The bptm debug log shows an error similar to the following:

00:58:54 [2304] <16> write_data: write of 32768 bytes indicated

only 29696 bytes were written, errno = 0

215NetBackup status codes and messagesAbout NetBackup status codes and messages

In this case, configure the drive for variable-mode block sizes and suspend themedia that writes on that device.See the NetBackup Device Configuration Guide.The images that were written to those media may be restorable (platformdependent), but single file restores are almost guaranteed to fail. You canexpire these media and regenerate the backups. Or you can attempt to duplicatethe images on these media to another device and then expire the original copy.

■ This error has occurred on re-labeled and value-added 8-mm tape drives wherethe drive’s micro code incorrectly processes a "forward space record" SCSIcommand.

■ If the problem is not one of those discussed, create a debug log directory foreither bpdm or bptm and retry the operation. Check the resulting debug log file.

NetBackup status code: 93Message: media manager found wrong tape in drive

Explanation: When you load a volume for a backup or restore, the tape manager(bptm) found a volume that loaded without the expected tape header. This errormay mean that volumes in a robot are not in the slots that are indicated in theMedia and Device Management volume configuration.

Recommended Action: Do the following, as appropriate:

■ If the volume is in a robot and the robot supports bar codes, do the following:perform a Compare Contents with Volume Configuration (on Windows) orCompare robot contents with volume configuration (on UNIX and Linux). Theresulting report shows the media ID that was found and validates its slotnumber with what is in the volume configuration. Then, either change thephysical location in the robot or change the volume configuration to show thecorrect slot.

■ If the volume was mounted on a nonrobotic drive, verify that the correct volumewas mounted and assigned.

NetBackup status code: 94Message: cannot position to correct image

Explanation: The tape manager (bptm) searched for a backup image to restorebut did not find the correct backup ID at the expected position on the volume.This error can indicate a drive hardware problem.

Recommended Action: Do the following, as appropriate:

■ Try the restore on another drive if possible.

NetBackup status codes and messagesAbout NetBackup status codes and messages

216

■ For additional information, check the following:

■ NetBackup Problems report to determine the device or volume that causedthe error

■ System and error logs for the system (UNIX and Linux)

■ Event Viewer Application and System logs (Windows)

■ For detailed troubleshooting information, create a debug log directory for bptmand retry the operation. Check the resulting debug log files.

NetBackup status code: 95Message: media id is not assigned to this host in the EMM database

Explanation: An operation was requested on a media ID for which NetBackupdoes not have a record assigned to the requesting server. An example of this isusing bpmedia to suspend or freeze a media ID that does not exist or is not assignedto the requesting server.

RecommendedAction: Run a NetBackup Media List report to determine the validmedia IDs and their assigned hosts. Then, retry the command with a valid mediaID and assigned host.

NetBackup status code: 96Message: unable to allocate new media for backup, storage unit has none available

Explanation: The NetBackup resource broker (nbrb) did not allocate a new volumefor backups. This error indicates that the storage unit has no more volumesavailable in the volume pool for this backup. Note that NetBackup does not changestorage units during the backup.

Recommended Action: Check the NetBackup Problems report to determine thestorage unit that is out of media.

■ If the storage unit is a robot with empty slots, add more volumes (rememberto specify the correct volume pool).

■ If there are no empty slots, move some media to nonrobotic and then addnew volumes.

■ If you have difficulty keeping track of your available volumes, try theavailable_media script:

On UNIX and Linux, this script is in:

/usr/openv/netbackup/bin/goodies/available_media

On Windows, the script is in:

217NetBackup status codes and messagesAbout NetBackup status codes and messages

install_path\NetBackup\bin\goodies\available_media.cm

d

This script lists all volumes in the volume configuration, and augmentsthat list with information on the volumes currently assigned to NetBackup.

■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackupneeds a new tape and none are available in the current volume pool, it doesthe following: moves a tape from the scratch pool into the volume pool thatthe backup uses.

■ If the storage unit and volume pool appear to have media, verify the following:

■ Volume is not FROZEN or SUSPENDED.Check for this condition by using the NetBackup Media List report. If thevolume is frozen or suspended, use the bpmedia command to unfreeze orunsuspend it (if that is wanted).See “Troubleshooting frozen media” on page 63.

■ Volume has not expired or exceeded its maximum number of mounts.

■ The EMM database host name for the device is correct.If you change the EMM database host name, stop and restart the following:the Media Manager device daemon, ltid, (if the server is UNIX or Linux)or the NetBackup Device Manager service (if the server is a Windowssystem).

■ The correct host is specified for the storage unit in the NetBackupconfiguration.The host connection should be the server (master or media) with drivesconnected to it.

■ The Media and Device Management volume configuration has media in thecorrect volume pool. Unassigned or active media is available at the requiredretention level.Use the NetBackup Media List report to show the retention levels, volumepools, and status (active and so on) for all volumes. Use the NetBackupMedia Summary report to check for active volumes at the correct retentionlevels.

■ The NetBackup bptm process is rejected when it requests media from the vmd

process (UNIX and Linux) or the NetBackup Volume Manager service(Windows). The cause of this problem is that the process or service cannotdetermine the name of the host that makes the request.

This error can be due to an incorrect network configuration that involves thefollowing:

NetBackup status codes and messagesAbout NetBackup status codes and messages

218

■ Multiple network interfaces

■ /etc/resolv.conf on those UNIX or Linux systems that use it

■ Running DNS with reverse addressing not configured

■ Create bptm and vmd debug log directories and retry the operation.

■ Examine the bptmdebug log to verify that bptm connects to the correct system.If an error is logged, examine the vmd log.

On UNIX and Linux, the vmd log is:

/usr/openv/volmgr/debug/daemon/log.xxxxxx

On Windows, the vmd log is:

install_path\Volmgr\debug\daemon\xxxxxx.log

■ If this storage unit is new and this attempt to use it is the first, stop and restartNetBackup on the master server.

Note: The mds unified logging files (OID 143) usually show the NetBackupmedia selection process.

NetBackup status code: 97Message: requested media id is in use, cannot process request

Explanation: An operation was requested on a media ID that is in use. An exampleof this operation is the attempt to suspend or freeze a volume while it is in usefor a backup or restore.

Recommended Action: Retry the command when the volume is not in use. Usethe Device Monitor to determine if the volume is in use.

NetBackup status code: 98Message: error requesting media (tpreq)

Explanation: The tape manager (bptm) received an error when they requested amedia mount from the following: the NetBackup Device Manager service (onWindows) or the Media Manager device daemon (ltid) (on UNIX and Linux).

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report to determine the reason for the failure.The most common cause is that the NetBackup Device Manager service (on

219NetBackup status codes and messagesAbout NetBackup status codes and messages

Windows) or the Media Manager device daemon (ltid) (on UNIX and Linux)is not running. Start it if necessary.

■ If you duplicate backups or use Vault to duplicate backups, this error couldindicate the following: the Alternate Read Server does not have access to thetape where the original backup resides.

NetBackup status code: 99Message: NDMP backup failure

Explanation: The paths in your NDMP policy file list did not back up successfully.

Recommended Action: Check the NetBackup All Log Entries report for moreinformation. A possible cause for this error is that none of the backup paths existon the NDMP host.

NetBackup status code: 100Message: system error occurred while processing user command

Explanation: A system call failure in bparchive, bpbackup, bplist, or bprestore.

Recommended Action: Do the following, as appropriate:

■ Enable debug logging for bparchive, bpbackup, bplist, or bprestore (asappropriate) by creating debug log directories for them.On UNIX and Linux, if a nonroot user has problems, verify that the directorythat was created has mode 666. Look for and correct any reported errors.

■ Retry the operation and check the resulting logs.If the logs do not reveal the problem, use the command line version of thecommand and correct any problems that are reported on stderr.

NetBackup status code: 101Message: failed opening mail pipe

Explanation: The process that attempts to send mail did not open the pipe to theserver.

Recommended Action: Make sure that mail is configured on the client. Fordetailed troubleshooting information, create a bpcd debug log directory and retrythe operation. Check the resulting bpcd debug log.

NetBackup status code: 102Message: failed closing mail pipe

NetBackup status codes and messagesAbout NetBackup status codes and messages

220

Explanation: The process that sends mail could not close the pipe to the server.

Recommended Action: Make sure that mail is configured on the client. Fordetailed troubleshooting information, create a bpcd debug log directory and retrythe operation. Check the resulting bpcd debug log.

NetBackup status code: 103Message: error occurred during initialization, check configuration file

Explanation: None

Recommended Action: None

NetBackup status code: 104Message: invalid file pathname

Explanation: None

Recommended Action: None

NetBackup status code: 105Message: file pathname exceeds the maximum length allowed

Explanation: The path name (built by using the current working directory) exceedsthe maximum path length that the system allows.

Recommended Action: Shorten the current working directory path length.

NetBackup status code: 106Message: invalid file pathname found, cannot process request

Explanation: One of the file paths to be backed up or archived is not valid.

RecommendedAction: Verify that the full path names are used and that they donot exceed the maximum path length for the system. (On UNIX and Linux, theystart with a slash character [ / ].) Also, verify that the files exist and the permissionsallow NetBackup to access them.

NetBackup status code: 109Message: invalid date specified

Explanation: This error can occur when you run a command on the commandline that contains a date option. The format of a date option can vary dependingon the locale of the master server.

Recommended Action: Do the following, as appropriate:

221NetBackup status codes and messagesAbout NetBackup status codes and messages

■ If the error occurred on a command line, examine the standard error outputfrom the command for an explanatory message.

■ Refer to the format for the date options in the usage statement for thecommand. Look up the locale of the master server. Compare the date formatof that locale with the date format on the usage statement for the command.

■ Check the NetBackup Problems report for clues.

■ If the error appears in a Java interface, enable the debug print manager in theJava startup file. Retry and compare the parameters that are logged in the Javalog with the parameters listed in the command’s usage statement.

■ If these actions do not reveal the problem, create a debug log directory for theprocess that returned this status code. Then retry the operation and check theresulting debug log.

NetBackup status code: 110Message: Cannot find the NetBackup configuration information

Explanation: On Windows, NetBackup did not read the registry entries that werecreated during installation. On UNIX and Linux, the/usr/openv/netbackup/bp.conf file does not exist.

RecommendedAction: On Windows, reinstall NetBackup software on the client.On UNIX and Linux, create a /usr/openv/netbackup/bp.conf file with at leastthe following lines:

SERVER = server_name

CLIENT_NAME = client_name

NetBackup status code: 111Message: No entry was found in the server list

Explanation: On UNIX and Linux, the SERVER = server_name line is omittedfrom the bp.conf file. On Windows, the server list contains no entries.

Recommended Action: Do the following, as appropriate:

■ On a UNIX and Linux client, add the following line to the top of the/usr/openv/netbackup/bp.conf file:

SERVER = server_name

■ On a Microsoft Windows or nontarget NetWare client, do the following: addthe server name on the Server to use for backups and restores drop-down inthe Specify NetBackup Machines and Policy Type dialog box. To display this

NetBackup status codes and messagesAbout NetBackup status codes and messages

222

dialog box, start the Backup, Archive, and Restore interface on the client. Thenclick Specify NetBackup Machines and Policy Type on the File menu.

■ On an NetWare target client, add the server name to the bp.ini file.

■ On a Macintosh client, add the SERVER = server_name line to the bp.conf filein the NetBackup folder in the Preferences folder.

NetBackup status code: 112Message: no files specified in the file list

Explanation: A restore was requested with no files in the file list.

Recommended Action: Do the following, as appropriate:

■ Specify at least one file to be restored.

■ This status code may occur if nbjm is running and a stream discovery fails tofind all stream files. Examine the nbjm unified log (originator ID 117) for moredetails on the cause of the error.

NetBackup status code: 114Message: unimplemented error code

Explanation: This error should not occur. If nbjm received a negative errornumber, status 114 is issued.

Recommended Action: Examine the nbjm unified log (originator ID 117) fordetailed information on the cause of the error.

NetBackup status code: 116Message: VxSS authentication failed

Explanation: On either end of a socket connection, the parties did not mutuallyauthenticate each other.

Recommended Action: Do the following, as appropriate:

■ Ensure that the Veritas Security Services is installed and configured.For complete installation instructions, see the Veritas Security ServicesInstallation Guide.

■ Check that both parties have a valid certificate. Examine the expiry date thatis listed from a bpnbat -WhoAmI. For example:

bpnbat -WhoAmI

Name: JDOG

Domain: MYCOMPANY

223NetBackup status codes and messagesAbout NetBackup status codes and messages

Issued by: /CN=broker/[email protected]/O=vx

Expiry Date: Sep 19 12:51:55 2007 GMT

Authentication method: Microsoft Windows

Operation completed successfully.Shows an expiry date of September 19th, 2007. After 12:51:55 GMT thiscredential is no longer valid and a new credential is required.

■ If you run from the NetBackup Administration console, close and reopen theconsole. The console automatically obtains a credential for the currently loggedin identity, if possible. By default these certificates are valid for 24 hours.To set a longer default time, consult the Veritas Security ServicesAdministrator’s Guide.

■ Ensure the following: that the certificates for both sides use the same brokeror are children of the same root broker and that trusts were established betweenthem.See the Veritas Security Services Administrator’s Guide for more informationon broker hierarchies and how to establish trust relationships between brokers.

■ Ensure that connectivity between the physical systems in question is possible.If general sockets cannot connect between the machines (such as ping andtelnet), issues within the network unrelated to NetBackup can cause thisproblem.

■ Ensure that the system has sufficient swap space and the following directoriesare not full:

■ /home/username

■ /user/openv/netbackup/logs

■ /tmp

NetBackup status code: 117Message: VxSS access denied

Explanation: The user identity that was used to attempt an operation does nothave the permissions that are needed to perform the action.

Recommended Action: Do the following, as appropriate:

■ If you use the default groups, make certain that the user attempts to performan operation appropriate for that group. For example, a member ofNBU_Operators is unable to modify policy information, which is a permissionreserved for administrator roles.

NetBackup status codes and messagesAbout NetBackup status codes and messages

224

■ Ensure that the system has sufficient swap space and the following directoriesare not full:

■ /home/username

■ /user/openv/netbackup/logs

■ /tmp

■ If you use your own defined groups and permissions, first determine the objectwith which the operation is associated. Then add the permissions relative tothe action. For example, a user is required to up and down drives but currentlydoes not have permission to do so. Verify that the user belongs to the correctauthorization group.If necessary, verify that the group has Up and Down permissions on the Driveobject within the Group Permission tab. If necessary, increase the verbositylevel of NetBackup to locate what object and what permissions are requiredfor the failing request. The pertinent lines in the debug logs look similar tothe following:

17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.

Name: JMIZZLE

Domain: MYCOMPANY

Expiry: Sep 24 21:45:32 2003 GMT

Issued by: /CN=broker/[email protected]/O=vx

AuthType: 1

17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:

Function: VssAzAuthorize. Object

NBU_RES_Drives

17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:

Function: VssAzAuthorize. Permissions Up

17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:

Function: VssAzAuthorize. 20 Permission denied.

In this example, the user JMIZZLE attempts to perform an operation thatrequires the Up permission on the Drives object. To diagnose the problem,examine the group(s) to which the user belongs to ensure that the appropriategroup includes the Up permission. (Up is a member of the Operate permissionset for Drives.)

NetBackup status code: 118Message: VxSS authorization failed

Explanation: NetBackup was unable to complete the authorization check againstthe Authorization service.

225NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Do the following, as appropriate:

■ Ensure that the Authorization Service or Daemon is running.Refer to the Veritas Security Services Administrator’s Guide for moreinformation on authentication and authorization daemons.

■ Ensure that you are in communication with the correct master server. Withinthe bp.conf files on the local server, verify that the entryAUTHORIZATION_SERVICES specifies the proper host name (fully qualified)of the Authorization service. For example, AUTHORIZATION_SERVICE =

machine2.mycompany.com 0 specifies that the server contacts machine2 toperform Authorization checks. Also ensure that this entry matches that of themaster server.

■ Ensure that the system has sufficient swap space and the following directoriesare not full:

■ /home/userName

■ /user/openv/netbackup/logs

■ /tmp

■ Ensure that the server that contacts the master has a valid certificate. Themachine certificate can be examined as follows:For UNIX and Linux:

# bpnbat -WhoAmI -cf

/usr/openv/var/vxss/credentials/machine3.mycompany.com

For Windows:

Bpnbat WhoAmI -cf "c:\Program

Files\VERITAS\NetBackup\var\vxss\credentials\machine3.my

company.com"

Both of which would return:

Name: machine3.mycompany.com

Domain: [email protected]

Issued by: /CN=broker/[email protected]/O=vx

Expiry Date: Sep 2 19:25:29 2004 GMT

Authentication method: Veritas Private Security

Operation completed successfully.

If the expiry date was exceeded, use bpnbat -LoginMachine to obtain a newcredential for the machine.See the Netbackup Commands manual for more information on bpnbat.

NetBackup status codes and messagesAbout NetBackup status codes and messages

226

The server that attempts the check is not authorized to examine theAuthorization database. Ensure that bpnbaz -ShowAuthorizers re-tuned themachines identity. Ensure that the machine has a machine credential underthe directory as follows:Program Files\VERITAS\var\vxss\credentials (Windows)/usr/openv/var/vxss/credentials (UNIX and Linux)

This credential should have the full name of the machine as in the followingexample: machine1.company.com.

■ Check that the maximum number of open sockets to the Authorization databasewas not exhausted. Use netstat to determine the number of sockets that areopened to port 4032 on the Authorization server and that refer to the followingconfigurations:Windows:HKLM\SOFTWARE\VERITAS\Security\Authorization\Communication\ClientMaxConnections

UNIX and Linux: /etc/vx/vss/VRTSaz.conf entry "ClientMaxConnections"

If the maximum number of open connections was reached, you may need toincrease the number of maximum open connections. An increase in the numberof open connections increases the memory footprint of the Authorizationservice or daemon. Note that extreme increases in the maximum number ofconnections can cause performance degradation.

NetBackup status code: 120Message: cannot find configuration database record for requested NB databasebackup

Explanation: The program that backs up the NetBackup internal catalogs did notfind the attributes that indicate which media IDs to use or paths to back up. Thiserror should not occur under normal circumstances.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for additional information about theerror.

■ For detailed troubleshooting information, create admin and bpdbm debug logdirectories and retry the operation. Check the resulting debug logs.

■ Contact customer support and send the appropriate problem and debug logsections that detail the error.

NetBackup status code: 121Message: no media is defined for the requested NB database backup

227NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: When NetBackup attempted to back up its internal catalogs, nomedia IDs were defined in the catalog backup configuration.

Recommended Action: Add the media IDs to the catalog backup configuration.Verify that the media IDs are in the NetBackup volume pool.

NetBackup status code: 122Message: specified device path does not exist

Explanation: The NetBackup internal catalogs were backed up in the followingmanner: by using the bpbackupdb command line and by specifying a device path(on Windows) or a raw device file (on UNIX and Linux) that does not exist.

Recommended Action: Retry the command by using a valid device file name.

NetBackup status code: 123Message: specified disk path is not a directory

Explanation: When NetBackup attempted to back up its internal catalogs, thebackup attributes were set to dump to a disk. However, the disk file path alreadyexists and is not a directory.

Recommended Action: Specify a different disk path for the catalog backup ordelete the file that already exists.

NetBackup status code: 124Message: NB database backup failed, a path was not found or is inaccessible

Explanation: One or more of the specified paths in the catalog backupconfiguration were not backed up.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for additional information about theerror.

The following are some possible causes:

■ The path does not exist.

■ On a UNIX or Linux system, one of the paths contains a symbolic link.

■ After you determine which path cannot be accessed, correct the path namesin the catalog backup configuration.

NetBackup status code: 125Message: a NetBackup catalog backup is in progress

NetBackup status codes and messagesAbout NetBackup status codes and messages

228

Explanation: Only one NetBackup catalog backup can be active at any given time.Certain operations are not allowed during an online catalog backup. (These includecatalog archiving, catalog compression, and expiration of the last copy of animage.)

Recommended Action: Retry the operation after the catalog backup completes.

NetBackup status code: 126Message: NB database backup header is too large, too many paths specified

Explanation: Too many paths were specified in the NetBackup catalog backupconfiguration to fit in a fixed-size media header. This error should not occur undernormal circumstances.

Recommended Action: Delete some of the paths from the catalog backupconfiguration.

NetBackup status code: 127Message: specified media or path does not contain a valid NB database backupheader

Explanation: The bprecover command was issued and the media ID specifieddoes not have valid catalog backup data.

Recommended Action: Validate that the correct media ID is used.

NetBackup status code: 128Message: NB database recovery failed, a process has encountered an exceptionalcondition

Explanation: In the catalogs that were specified for recovery, one or more cannotbe restored. For more detail, refer to the error message that precedes this statuscode in the output from the bprecover command.

Recommended Action: Do the following, as appropriate:

■ Fix the problem that was reported in the error message in the bprecover output.

■ Refer to one of the following topics to identify which NetBackup services toshut down before a NetBackup database recovery attempt:See “Catalog recovery from an online backup” on page 591.The NetBackup services should be shut down except for the NetBackup ClientService, which must be running for the database recovery to succeed.

■ Check the NetBackup Problems report for additional information about theerror.

229NetBackup status codes and messagesAbout NetBackup status codes and messages

The following are some possible causes:

■ A disk may be full.

■ The NetBackup catalog tape may be corrupt.

NetBackup status code: 129Message: Disk storage unit is full

Explanation: As NetBackup writes to the file system for the disk storage unit,runs out of space. Until more file system space is available, images of similar sizeor larger may fail with this error when written to this disk storage unit.

In a scheduled backup job that writes to a storage unit group (which contains thisdisk storage unit), the following occurs: the NetBackup scheduler requests thestorage unit with the greatest available capacity when the job is retried.

For the retry, when the scheduler requests the storage unit with the greatestavailable capacity, note the following:

■ A tape storage unit in the storage unit group has preference over any diskstorage units since tape storage units usually have more capacity.

■ If the storage unit with the most unused capacity is busy, NetBackup skips it.NetBackup then selects an available storage unit with the next largest, unusedcapacity.

■ If the storage unit with the greatest unused capacity is the one that lackedcapacity when the job first failed, the scheduler tries it again. That storageunit may have more unused capacity now than it did when the job failed.

Recommended Action: Do the following, as appropriate:

■ Either free sufficient space or add more space to the file system for this storageunit.

■ Lower the high capacity mark for this disk storage unit. Configure the policiesto access it through a storage unit group that provides alternative storage touse when this storage unit fills up. Ideally, if an image exceeds the file system’shigh capacity mark, it also completes successfully. This image leaves thestorage unit in a "full" state (over the high capacity mark). The storage unitthen is not assigned to other jobs until its capacity falls under its high capacitymark.

■ If the Staging attribute is set on the disk storage unit that did not have enoughcapacity, it may be unable to create free space. It cannot create space becausethe backups that are staged to the disk are not relocated (eligible to be deletedfrom the staging storage unit). Ensure that staging’s relocation (duplication)

NetBackup status codes and messagesAbout NetBackup status codes and messages

230

jobs successfully copy enough images to provide sufficient free space for newbackups.

NetBackup status code: 130Message: system error occurred

Explanation: An error occurred that prevents the product from operating in aconsistent fashion. This error is usually related to a system call.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for additional information about theerror.

■ Check the system log for reported problems.

■ For detailed troubleshooting information, create bpdbm, bptm, and bprd debuglog directories on the master server. Increase the unified logging level by usingthe vxlogcfg command.

See “Configuring and using unified logging” on page 94.

■ Retry the operation and check the resulting debug logs.

NetBackup status code: 131Message: client is not validated to use the server

Explanation: The client name, as determined from the connection to the server,did not match any client name in the NetBackup configuration. No altnames

configuration for this client exists on the master server. A client and server withmultiple network connections can encounter this problem in the followingsituation: the name by which the client is configured is not the one by which itsrouting tables direct connections to the server.

Recommended Action: Do the following, as appropriate:

■ Examine the NetBackup Problems report.

■ Create a debug log directory for bprd and retry the operation. Check theresulting debug log to determine the connection and the client names.

Depending on the request type (restore, backup, and so on), you may need orwant to do the following:

■ Change the client’s configured name.

■ Modify the routing tables on the client.

■ On the master server, set up an altnames directory and file for this client

See the NetBackup Administrator’s Guide, Volume I.

231NetBackup status codes and messagesAbout NetBackup status codes and messages

or

■ On a UNIX or Linux master server, create a soft link in the NetBackup imagecatalog.

■ See “Verifying host name and service entries” on page 49.

NetBackup status code: 132Message: user is not validated to use the server from this client

Explanation: None

Recommended Action: None

NetBackup status code: 133Message: invalid request

Explanation: One of two explanations exist.

■ A request was made that is not recognized. This usually results from differentversions of NetBackup software being used together.

■ If a client receives this error in response to a list or restore request, then theDISALLOW_CLIENT_LIST_RESTORE or DISALLOW_CLIENT_RESTORE. option existsin the bp.conf file on the following: a UNIX or Linux NetBackup server or inthe registry on a Windows NetBackup server. These options deny list andrestore requests from all NetBackup clients.

Recommended Action: Do the following, as appropriate:

■ If you suspect that the software versions are the problem, verify that allNetBackup software is at the same version level.

■ On UNIX and Linux NetBackup servers and clients, check the/usr/openv/netbackup/bin/version file.

■ On Windows NetBackup servers, check theinstall_path\netbackup\version.txt file or the AboutNetBackup itemon the Help menu.

■ On Microsoft Windows clients, check the About NetBackup item on theHelp menu.

■ On NetWare target clients, check the Version entry in the bp.ini file.

■ On Macintosh clients, check the version file in the bin folder in theNetBackup folder in the Preferences folder.

■ If the server denies list and restore requests, remove theDISALLOW_CLIENT_LIST_RESTOREandDISALLOW_CLIENT_RESTOREoptions from

NetBackup status codes and messagesAbout NetBackup status codes and messages

232

the bp.conf file on the following: a UNIX or Linux NetBackup server or fromthe registry on a Windows NetBackup server. Then, stop and restart theNetBackup request daemon (UNIX and Linux) or NetBackup Request Managerservice (Windows).

■ For detailed troubleshooting information, create bpdbm, bprd, and admindebuglog directories. Retry the operation and check the resulting debug logs.

NetBackup status code: 134Message: unable to process request because the server resources are busy

Explanation: Status code 134 is an informational message that indicates that alldrives in the storage unit are currently in use. If all drives are in use, NetBackupautomatically tries another storage unit. If one is not available, NetBackupre-queues the job with a status of 134 and retries it later.

Recommended Action: None.

The 134 code is an informational message only and is not considered an error. Itcan occur for a number of reasons in normal operation. The 134 status code canoccur more frequently in an SSO environment. No action is necessary.

A status 134 is not logged in the error logs. A 134 status causes a new try to appearin the Activity Monitor. It does not increase the retry count associated with theallowed number of retries.

NetBackup status code: 135Message: client is not validated to perform the requested operation

Explanation: An alternate client restore was tried that did not come from theroot user (on UNIX and Linux) or the administrator (on Windows).

Recommended Action: Retry the operation as a root user (on UNIX and Linux)or as an administrator (on Windows) on the master server. Also see status code131.

NetBackup status code: 136Message: tir info was pruned from the image file

Explanation: The TIR information was pruned from one or more of the component(differential or cumulative) backup images being synthesized.

This situation arises when the following occurs:

■ The most recent backup image for the client is a synthetic full or cumulativebackup

233NetBackup status codes and messagesAbout NetBackup status codes and messages

■ The TIR information from one or more of the component images before thesynthetic full (or cumulative) backup is pruned

The TIR information is automatically restored to the image catalog if you do thefollowing: expire the synthetic backup (full or cumulative) image and try to rerunthe synthetic backup job for the client. However, the synthetic backup job failswith this error if the TIR restore fails due to bad, missing, or vaulted media or abad drive.

Recommended Action: Reimport the TIR information into the catalog of eachcomponent image (from which the TIR information was pruned). Then rerun thesynthetic backup job. The TIR information can be imported into the image catalogby initiating a true image restore of any file from that component image. Therestore process also restores the TIR information in the image catalog.

NetBackup status code: 140Message: user id was not superuser

Explanation: A user or process that did not have root privileges (on UNIX andLinux) or administrator privileges (on Windows) started the process.

RecommendedAction: If appropriate, give the user or the process administratorprivileges (on Windows) or root privileges (on UNIX and Linux) and retry theoperation.

NetBackup status code: 141Message: file path specified is not absolute

Explanation: The file specification must be an absolute path.

Recommended Action: Correct the file specification and retry the command.

NetBackup status code: 142Message: file does not exist

Explanation: To back up a VxFS file system with Snapshot Client, the VxFS filesystem on the client must be patched with correct, dynamically linked libraries.If the correct VxFS libraries are not installed, the backup fails with status 142.

The following appears in the log:

■ For most snapshot backups, the following message appears in the/usr/openv/netbackup/logs/bpfis log on the client:

09:36:48.299 [527] <32> fs_dev_rt_check: FTL - snapshot method:

nbu_snap abort - required VxFS dynamic linked libraries for

NetBackup status codes and messagesAbout NetBackup status codes and messages

234

NetBackup are not installed. Please visit the Symantec support

web site, and refer to Technote number 262225 for further

information.

■ For the backups that run from a FlashBackup policy, the following appears inthe /usr/openv/netbackup/logs/bpbkar log on the client:

10:09:56.566 [1146] <32> bpfsmap: FTL - bpfsmap: FlashBackup

abort - required VxFS dynamic linked libraries for NetBackup are

not installed. Please visit the Symantec support web site, and

refer to Technote number 262225 for further information.

10:09:56.571 [1146] <16> bpbkar Exit: ERR - bpbkar FATAL exit

status = 142: file does not exist

10:09:56.573 [1146] <4> bpbkar Exit: INF - EXIT STATUS 142: file

does not exist

Recommended Action: Install the VxFS dynamic libraries on the NetBackupclient as described in Technote 262225 and try the backup again.

NetBackup status code: 143Message: invalid command protocol

Explanation: A poorly formed request was made to the NetBackup request daemon(UNIX and Linux) or to the Request Manager service (Windows). This error canbe due to the following: mismatched versions of the product, corrupted networkcommunication, or to a non-NetBackup process sending data across the port forthe daemon or service.

RecommendedAction: Examine the NetBackup error logs to determine the systemthat was the source of the data. On that system, determine the process thatinitiated the request. If it was a NetBackup process, verify that the process orcommand is compatible with the version of software on the server.

NetBackup status code: 144Message: invalid command usage

Explanation: This status code is due to a NetBackup process being started withimproper options or an incompatibility in the product.

RecommendedAction: Either correct the command or verify that all NetBackupbinaries are at the same version level.

235NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 145Message: daemon is already running

Explanation: Another copy of the process is running.

RecommendedAction: Terminate the current copy of the process and then restartthe process.

NetBackup status code: 146Message: cannot get a bound socket

Explanation: The service or daemon did not bind to its socket. A system call failswhen the daemon (UNIX and Linux) or service (Windows) attempts to bind to itsconfigured port number. This error is usually caused when another processacquired the port before the daemon or service started.

Recommended Action: Do the following, as appropriate:

■ Examine the NetBackup Problems and All Log Entries reports.

■ Create bprd and bpdbm debug log directories and retry the operation. Checkthe resulting logs to see the system error message that resulted from theattempt.If another process has the port, use other system commands to determine theprocess. Based on this research, either change the port number in yourservices file or map or terminate the process that acquired the port.

On UNIX and Linux, another possible cause for this error is the use of the killcommand to terminate bprd or bpdbm. If you have to stop bprd, use theTerminate Request Daemon option on the Special Actions menu in bpadm.To stop bpdbm, use the /usr/openv/netbackup/bin/bpdbm -terminate

command. Use of the kill command to stop these processes can leave themunable to bind to their assigned ports the next time they are started.To identify a bprd or a bpdbm problem, look for lines similar to the followingin the debug log for the respective process:

<16> getsockbound: bind() failed, Address already in use (114)

<32> listen_loop: cannot get bound socket. errno = 114

<4> terminate: termination begun...error code = 146

Similar entries can appear in the reports.

■ If the problem persists longer than ten minutes, it may be necessary to restartthe server.

NetBackup status codes and messagesAbout NetBackup status codes and messages

236

NetBackup status code: 147Message: required or specified copy was not found

Explanation: The requested copy number of a backup or an archive image cannotbe found.

Recommended Action: Correct the request to specify a copy number that doesexist.

NetBackup status code: 148Message: daemon fork failed

Explanation: A NetBackup service did not create a child process due to an errorthat was received from the system. This error is probably an intermittent errorthat is based on the availability of resources on the system.

Recommended Action: Do the following, as appropriate:

■ Restart the service at a later time and investigate the system problems thatlimit the number of processes.

■ On Windows systems, check the Event Viewer Application and System logs.

NetBackup status code: 149Message: master server request failed

Explanation: None

Recommended Action: None

NetBackup status code: 150Message: termination requested by administrator

Explanation: The process terminates (or has terminated) as a direct result of arequest from an authorized user or process.

Recommended Action: None.

NetBackup status code: 151Message: Backup Exec operation failed

Explanation: The Global Data Manager console reported that a Backup Exec job(backup, archive, or restore) did not complete normally.

Recommended Action: Consult the Backup Exec job history on the Backup Execserver for details.

237NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 152Message: required value not set

Explanation: An incomplete request was made to the bpdbm process (on UNIXand Linux), or the NetBackup Database Manager service (on Windows). This errorusually occurs because different versions of software are used together.

Recommended Action: Do the following, as appropriate:

■ Verify that all software is at the same version level.

■ For detailed troubleshooting information, create bpdbm and admin debug logdirectories and retry the operation. Check the resulting debug logs.

NetBackup status code: 153Message: server is not the master server

Explanation: This status code is reserved for future use.

Recommended Action: None.

NetBackup status code: 154Message: storage unit characteristics mismatched to request

Explanation: A backup was tried and the storage unit selected for use had thecharacteristics that were not compatible with the backup type.

Recommended Action: Verify that the characteristics of the selected storageunit are appropriate for the attempted backup.

■ For a NetBackup Snapshot Client, the policy storage unit was set toAny_available and the off-host backup method was set to Third-Party CopyDevice or NetBackupMediaServer. Do not choose Any_available. A particularstorage unit (such as nut-4mm-robot-tl4-0) must be specified whenThird-Party Copy Device or NetBackup Media Server is specified as theoff-host backup method.

■ For an NDMP policy type, verify the following: a storage unit of type NDMP isdefined and the NDMP host value matches the host name of the client. Forexample, if the NDMP policy specifies toaster as the client, the configurationfor the storage unit must specify toaster as the NDMP host.

■ For a policy type other than NDMP, verify that the policy specifies a MediaManager or Disk type storage unit.

NetBackup status codes and messagesAbout NetBackup status codes and messages

238

NetBackup status code: 155Message: disk is full

Explanation: The write to the catalog file failed because the disk that containsthe catalog database is full.

Recommended Action: Free up space on the disks where NetBackup catalogsreside and retry the operation.

NetBackup status code: 156Message: snapshot error encountered

Explanation: The following are possible causes of this status code:

■ An Enterprise Vault Agent related error. The following errors can result in astatus code 156:

■ VSS_E_BAD_STATE snapshot error

■ VSS_E_INSUFFICIENT_STORAGE snapshot error

■ A snapshot-backup related error regarding Windows Open File Backup orSnapshot Client.

Recommended Action: Do the following, as appropriate:

■ For the Enterprise Vault Agent:See the Troubleshooting section of the NetBackup for Enterprise Vault AgentAdministrator’s Guide.

■ For a Windows Open File Backup Snapshot Provider that uses VSS:See the Troubleshooting section of one of the following guides:

■ NetBackup for VMware Administrator’s Guide

■ NetBackup for Hyper-V Administrator’s Guide

■ NetBackup Snapshot Client Administrator’s Guide

The VSS cache files may be too small for the number of files being backed upusing VSS.If bpbkar debug logs are turned on, a message similar to the following appearsin the bpbkar debug log for the backup.

8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR -

failure reading file: D:\ test.file (WIN32 5: Access is denied.

)

8:51:14.569 AM: [1924.2304] <4> tar_base::V_vTarMsgW: INF - tar

message received from dos_backup::tfs_readdata

8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR -

239NetBackup status codes and messagesAbout NetBackup status codes and messages

Snapshot Error while reading test.file

8:51:14.569 AM: [1924.2304] <4> tar_base::V_vTarMsgW: INF - tar

message received from tar_backup::nextfile_state_switch

8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: FTL -

Backup operation aborted!

8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: INF -

Client completed sending data for backup

8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: INF - EXIT

STATUS 156: snapshot error encountered

To increase the VSS cache size by using the Shadow Copy configuration inWindows 2003, do the following in the order listed:

■ In Windows, right-click My Computer and select Manage.

■ In the console tree, right-click SharedFolders, select AllTasks, and selectConfigure Shadow Copies.

■ Select the volume where you want to make changes, and then selectSettings.

■ In the Settings dialog box, change the Maximum Size setting to either ofthe following: No Limit or a size large enough to suit the requirements ofyour installation and your usage of VSS.

■ For backups using Snapshot Client and the NAS_Snapshot method, with orwithout SnapVault:

■ If the backup fails with status code 156, consult the bpfis legacy log, in/usr/openv/netbackup/logs (UNIX and Linux) orinstall_path\NetBackup\logs (Windows). If the bpfis directory does notalready exist, you must create it and rerun the job.If necessary, increase the logging level and retry the job.See “About using logs and reports” on page 81.

■ On Windows clients, when restoring files from a backup that is made withthe NAS_Snapshot method, log into the "NetBackup Client Service" as theAdministrator account, not as the local system account. Otherwise, thebackup fails with status 156.

■ In Windows Services, double-click the NetBackup Client Service.

■ Then check the Log On tab: if the service is not logged in asAdministrator, stop the service.

■ Change the login to the Administrator account and restart the service.

■ Retry the restore.

■ For other NetBackup Snapshot Client issues:

NetBackup status codes and messagesAbout NetBackup status codes and messages

240

The file system that is specified as a snapshot source is not mounted. Inthis case, you may see the following in the/usr/openv/netbackup/logs/bpfis log:

17:12:51 bpfis: FTL - snapshot creation failed, status 156

17:12:51 bpfis: INF - EXIT STATUS 156: snapshot error

encountered

and the following in the /usr/openv/netbackup/logs/bpfis log:

17:12:51 onlfi_vfms_logf: INF - cannot snap_on, err: 5

17:12:51 delete_mount_point: INF - Deleted mount point

/tmp/__jody_test:20958

17:12:51 onlfi_freeze: FTL - VfMS error 11; see following

messages:

17:12:51 onlfi_freeze: FTL - Fatal method error

17:12:51 onlfi_freeze: FTL - vfm_freeze: method: nbu_snap, type:

FIM, function: nbu_snap_freeze

17:12:51 onlfi_freeze: FTL - VfMS method error 5; see following

message:

17:12:51 onlfi_freeze: FTL - nbu_snap_freeze: Cannot turn on

snapshot; snapshot source=/opt, cache=/dev/rdsk/c1t3d1s0, snap

error=5

17:12:51 onlfi_thaw: WRN - / is not frozen

Make sure that the file system that is specified for the snapshot source hasbeen mounted.

■ The file system that is specified as the snapshot source does not correspondto the file system that contains the actual files (as opposed to symboliclinks to the files). The mounted file system for the snapshot source mustcontain the actual files, not symbolic links. If items in the file list, such as/oracle, is a symbolic link to /export/home/oracle, the snapshot sourcemust specify /export, or /export/home, not /oracle.

■ vxvm is selected as the snapshot method but the snapshot source is notconfigured over a Veritas Volume Manager (VxVM) volume. In this case,you may see the following in the /usr/openv/netbackup/logs/bpfis log:

17:12:51 bpfis: FTL - snapshot creation failed, status 156

17:12:51 bpfis: INF - EXIT STATUS 156: snapshot error

encountered

and something like the following in the/usr/openv/netbackup/logs/bpfislog:

241NetBackup status codes and messagesAbout NetBackup status codes and messages

17:12:51 onlfi_vfms_logf: INF - vxvm_freeze: Snapshot source

/cockpit1 on device /dev/dsk/c1t0d0s6 is not on a VxVM volume

17:12:51 delete_mount_point: INF - Deleted mount point

/tmp/_cockpit1_coc_group1:3518

17:12:51 onlfi_freeze: FTL - VfMS error 11; see following

messages:

17:12:51 onlfi_freeze: FTL - Fatal method error

17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type:

FIM, function: vxvm_freeze

17:12:51 onlfi_freeze: FTL - VfMS method error 9; see following

message:

17:12:51 onlfi_freeze: FTL - vxvm_freeze: Snapshot source

/cockpit1 on device /dev/dsk/c1t0d0s6 is not on a VxVM volume

17:12:51 onlfi_thaw: INF - fim=vxvm

17:12:51 onlfi_thaw: WRN - /cockpit1 is not frozen

Make sure that the snapshot source is configured over a Veritas VolumeManager (VxVM) volume.

■ vxvm was selected as the snapshot method, but a Veritas Volume Managersnapshot mirror of the snapshot source volume had not been created beforerunning the backup, or another backup is currently running that uses thesnapshot mirror. In either case, you may see the following in the/usr/openv/netbackup/logs/bpfis log:

17:12:51 onlfi_freeze: FTL - VfMS error 11; see following

messages:

17:12:51 onlfi_freeze: FTL - Fatal method error

17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type:

FIM, function: vxvm_freeze

17:12:51 onlfi_freeze: FTL - VfMS method error 3; see following

message:

17:12:51 onlfi_freeze: FTL - find_ready_snapshot: Cannot find

available snapshot mirror

Refer to the NetBackup Snapshot Client Administrator’s Guide forinformation on how to create a snapshot mirror on the client before yourun the backup.

■ vxvm was selected as the snapshot method, and a Veritas Volume Managersnapshot mirror of the snapshot source volume has been created. However,two different backup jobs (A and B) try to back up the same volume (forexample, vol01), but job A starts before job B. After an available snapshotmirror is found, a brief pause occurs before the snapshot is formed. Job Bthat runs slightly behind job A may try to create a snapshot of the snapshot

NetBackup status codes and messagesAbout NetBackup status codes and messages

242

mirror immediately before job A creates the snapshot and gets the lock onit.In this case, you may see the following in the/usr/openv/netbackup/logs/bpfis log:

17:12:51 onlfi_freeze: FTL - VfMS error 11; see following

messages:

17:12:51 onlfi_freeze: FTL - Fatal method error

17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type:

FIM, function: vxvm_freeze

17:12:51 onlfi_freeze: FTL - VfMS method error 3; see following

message:

17:12:51 onlfi_freeze: FTL - vxvm_freeze: Command failed with

status=11: /usr/sbin/vxassist -g rootdg snapshot vol01

VfMSCAAu7a4Uw </dev/null>/var/tmp/VfMSAAAs7a4Uw

2>/var/tmp/VfMSBAAt7a4Uw

The job that was unable to get a lock (job B in the preceding example) fails,and must be run again.

■ When using nbu_snap as a snapshot method, you may have stale snapshotsif status code 156 occurs with the following messages in the/usr/openv/netbackup/logs/bpfis log. (Stale snapshots are those thatnbu_snap did not automatically delete.)

17:12:51 onlfi_freeze: FTL - VfMS error 11; see following

messages:

17:12:51 onlfi_freeze: FTL - Fatal method error

17:12:51 onlfi_freeze: FTL - vfm_freeze: method: nbu_snap, type:

FIM, function: nbu_snap_freeze

17:12:51 onlfi_freeze: FTL - VfMS method error 5; see following

message:

17:12:51 onlfi_freeze: FTL - nbu_snap_freeze: Cannot turn on

snapshot; snapshot source=/oracle/ufs_r,

cache=/dev/rdsk/c4t1d11s4,snap error=11

■ Look for stale snapshots by running the/usr/openv/netbackup/bin/driver/snaplist command when there areno active backups running. If the snaplist command shows cache entries,there are stale snapshots. Nothing is displayed if there are no stalesnapshots.Example snaplist output:

243NetBackup status codes and messagesAbout NetBackup status codes and messages

id ident size cached minblk err time

43 6515 8390970 0 0 0 11/16/00 13:31:36

device = /dev/rdsk/c1t6d0s0

cache = /dev/rdsk/c1t6d0s7

■ Use the snapoff command to remove the stale snapshot, as follows:

/usr/openv/netbackup/bin/driver/snapoff id

where id is the ID from the snaplist output (such as 43 in the precedingexample).

■ If a backup using the VxFS_Checkpoint snapshot method failed, theNetBackup bpbkar process should automatically remove the clone.Sometimes, however, bpbkar is unable to remove the clone. In this case,you may see messages such as the following in the/usr/openv/netbackup/logs/bpfis log:

15:21:45.716 [4236] <4> create_mount_point: INF - Created mount

point /tmp/_vtrax_test:4236

15:21:45.869 [4236] <2> onlfi_vfms_logf: INF - vxfs clone handle

: 9600344

15:21:45.870 [4236] <2> onlfi_vfms_logf: INF -

VxFS_Checkpoint_freeze: Cannot create checkpoint; status=17

15:21:45.872 [4236] <4> delete_mount_point: INF - Deleted mount

point /tmp/_vtrax_test:4236

15:21:45.873 [4236] <32> onlfi_freeze: FTL - VfMS error 11; see

following messages:

15:21:45.873 [4236] <32> onlfi_freeze: FTL - Fatal method error

was reported

15:21:45.873 [4236] <32> onlfi_freeze: FTL - vfm_freeze: method:

VxFS_Checkpoint, type: FIM, function: VxFS_Checkpoint_freeze

15:21:45.873 [4236] <32> onlfi_freeze: FTL - VfMS method error

17; see following message:

15:21:45.874 [4236] <32> onlfi_freeze: FTL -

VxFS_Checkpoint_freeze: Cannot create checkpoint; status=17

Remove the clone as follows.

Note: If the checkpoint is not removed, you cannot use VxFS_Checkpointto back up any data in the file system where the checkpoint is mounted.

■ List the name of the checkpoint by entering the following VxFS command:

NetBackup status codes and messagesAbout NetBackup status codes and messages

244

/usr/lib/fs/vxfs/fsckptadm list /file_system

where file_system is the name of the file system where the checkpoint ismounted. A sample output follows. In this example, /vtrax_test is the filesystem and fi_ckpt is the name of the checkpoint.

/vtrax_test

fi_ckpt:

ctime = Mon Nov 12 10:08:13 2001

mtime = Mon Nov 12 10:08:13 2001

flags = largefiles

■ Remove the checkpoint by entering the following:

/usr/lib/fs/vxfs/fsckptadm remove checkpoint /file_system

■ If the checkpoint cannot be removed, unmount the checkpoint and retrythe first step in this procedure.

■ If a snapshot backup fails using TimeFinder, ShadowImage, or BusinessCopymethod, there may be a VxVM clone left over from a previous backup. Youmay see messages similar to the following in the/usr/openv/netbackup/logs/bpfis log:

19:13:07.686 [14981] <2> onlfi_vfms_logf: INF - do_cmd: Command

failed with status=20: /usr/openv/netbackup/bin/bpdgclone -g

wil_test -n vol01 -f /var/tmp/HDSTFCAAs7aOqD </dev/null

>/var/tmp/VfMSAAAq7aOqD 2>/var/tmp/VfMSBAAr7aOqD

19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- Dumping file

/var/tmp/VfMSAAAq7aOqD (stdout):

19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- End of file

/var/tmp/VfMSAAAq7aOqD

19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- Dumping file

/var/tmp/VfMSBAAr7aOqD (stderr):

19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - clone group

and volume already exists

19:13:07.688 [14981] <2> onlfi_vfms_logf: INF - --- End of file

/var/tmp/VfMSBAAr7aOqD

NetBackup automatically creates VxVM clones for TimeFinder,ShadowImage, or BusinessCopy backups of data that is configured overvolumes. After the backup has completed, NetBackup removes the VxVMclone. In this case, a system crash or restart may have prevented theremoval. Remove the clone as follows.

245NetBackup status codes and messagesAbout NetBackup status codes and messages

(Do the following on the client or alternate client, depending on the typeof backup.)

■ When no backups are running, use the following VxVM command to listany clones: vxdg list

The clone name is of the form clone_disk_group_clone.

■ To remove the clone, enter the following:

/usr/openv/netbackup/bin/bpdgclone -g disk_group -n volume -c

For example:

/usr/openv/netbackup/bin/bpdgclone -g wil_test -n vol01 -c

where wil_test is the name of the disk group and volo1 is the name of theVxVM volume.For more information on now to remove a VxVM clone, refer to theNetBackup Snapshot Client Administrator’s Guide. For vxdg, refer to theVeritas VolumeManager Administrator’s Guide.

■ Before running the backup again, resynchronize the primary disk with thesecondary disk. For assistance, refer to the NetBackup Snapshot ClientAdministrator’s Guide.

■ If a snapshot backup fails using the FlashSnap or VVR snapshot method,a VxVM snapshot may be left over from a previous backup. You may seemessages similar to the following in the/usr/openv/netbackup/logs/bpfis log:

14:41:15.345 [22493] <32> onlfi_freeze: FTL - VfMS error 11; see

following messages:

14:41:15.345 [22493] <32> onlfi_freeze: FTL - Fatal method error

was reported

14:41:15.345 [22493] <32> onlfi_freeze: FTL - vfm_freeze_commit:

method: FlashSnap, type: FIM, function: FlashSnap_freeze_commit

14:41:15.345 [22493] <32> onlfi_freeze: FTL - VfMS method error

8; see following message:

14:41:15.345 [22493] <32> onlfi_freeze: FTL -

vxvm__find_ready_snapshot: Cannot find available snapshot mirror

NetBackup automatically creates VxVM snapshots for backups of data thatis configured over volumes. After the backup completes, NetBackup removesthe VxVM snapshot. In this case, a system crash or restart may haveprevented the removal. Remove the snapshot as follows.For FlashSnap:

NetBackup status codes and messagesAbout NetBackup status codes and messages

246

(Do the following on the client or alternate client, depending on the typeof backup.)

■ Find the VxVM disk group:

vxdg list

The format of the disk group name is as follows:

primaryhost_diskgroup_split

If vxdg list does not show the disk group, the group might have beendeported. You can discover all the disk groups, that includes deported ones,by entering:

vxdisk -o alldgs list

The disk groups that are listed in parentheses are not imported on the localsystem.

■ Deport the VxVM disk group:

vxdg deport primaryhost_diskgroup_split

Enter the following on the primary (original) client:

■ Import and join the VxVM disk group:

vxdg import primaryhost_diskgroup_split

vxrecover -g primaryhost_diskgroup_split -m

vxdg join primaryhost_diskgroup_split diskgroup

■ Start the volume and snap back the snapshot volume:

vxvol -g primaryhost_diskgroup_split start

SNAP_diskgroup_volume

vxassist snapback SNAP_diskgroup_volume

For VVR, on the alternate client:

■ Enter the following to display unsynchronized mirror disks:

vxprint -g diskgroup

■ Enter the following to resynchronize the mirror disks:

vxassist -g diskgroup -v volume snapback

247NetBackup status codes and messagesAbout NetBackup status codes and messages

■ When you use a snapshot method such as VxFS_Checkpoint to back up aVeritas File System (VxFS), the backup fails if the VxFS license has expired.Messages such as the following appear in the/usr/openv/netbackup/logs/bpfis log:

11:37:42.279 [24194] <2> onlfi_vfms_logf: INF -

VxFS_Checkpoint_freeze: Cannot open checkpoint; status=100

11:37:42.283 [24194] <4> delete_mount_point: INF - Deleted mount

point /tmp/_vrts_frzn_img__test1_24194

11:37:42.283 [24194] <32> onlfi_freeze_fim_fs: FTL - VfMS error

11; see following messages:

11:37:42.283 [24194] <32> onlfi_freeze_fim_fs: FTL - Fatal

method error was reported

11:37:42.284 [24194] <32> onlfi_freeze_fim_fs: FTL - vfm_freeze:

method: VxFS_Checkpoint, type: FIM, function:

VxFS_Checkpoint_freeze

11:37:42.284 [24194] <32> onlfi_freeze_fim_fs: FTL - VfMS method

error 100; see following message:

11:37:42.284 [24194] <32> onlfi_freeze_fim_fs: FTL -

VxFS_Checkpoint_freeze: Cannot open checkpoint; status=100

Obtain a new VxFS license and retry the backup.

■ If the backup is enabled for instant recovery with either the vxvm or VVRsnapshot method, your VxVM mirrors may not be properly configured. Inthis case, you may see the following in the/usr/openv/netbackup/logs/bppfi log on the client (when verbose modeis set high).

13:43:39.095 [16375] <2> onlfi_vfms_logf: INF - Executing

command:

13:43:39.095 [16375] <2> onlfi_vfms_logf: INF -

/usr/sbin/vxprint -g rootdg -q -t -e 'assoc="pfi_concat"'

</dev/null >/var/tmp/VfMSAA Arja4.F 2>/var/tmp/VfMSBAAsja4.F

13:43:39.215 [16375] <2> onlfi_vfms_logf: INF -

pfi_find_snapdone: 0 SNAPDONE plexes found

13:43:39.215 [16375] <2> onlfi_vfms_logf: INF - Executing

command:

13:43:39.215 [16375] <2> onlfi_vfms_logf: INF -

/usr/sbin/vxassist -g rootdg snapprint pfi_concat </dev/null

>/var/tmp/VfMSAAArja4.F 2>/var/tmp/VfMSBAAsja4.F

13:43:39.512 [16375] <2> onlfi_vfms_logf: INF - 0 active plexes

for /rootdg/pfi_concat: 0 are PFI 0 non-PFI

13:43:39.512 [16375] <2> onlfi_vfms_logf: INF -

NetBackup status codes and messagesAbout NetBackup status codes and messages

248

pfi_find_active.3309: exiting with VXVM_E_SYS = 3

13:43:39.512 [16375] <2> onlfi_vfms_logf: INF -

pfi_snapshot.3866: No PFI snapshot. err= 3

Configure the VxVM mirrors as described in the Instant Recovery chapterof the NetBackup Snapshot Client Administrator’s Guide.

■ When you use the VxFS_Checkpoint snapshot method, the backup fails ifthe client’s file system does not support mountable checkpoints using theStorage Checkpoint feature. Messages such as the following appear in the/usr/openv/netbackup/logs/bpfis log:

14:54:27.530 [23563] <32> onlfi_freeze_fim_fs: FTL - VfMS error

11; see following messages:

14:54:27.530 [23563] <32> onlfi_freeze_fim_fs: FTL - Fatal

method error was reported

14:54:27.530 [23563] <32> onlfi_freeze_fim_fs: FTL - vfm_freeze:

method: VxFS_Checkpoint, type: FIM, function:

VxFS_Checkpoint_freeze 14:54:27.531 [23563] <32>

onlfi_freeze_fim_fs: FTL - VfMS method error 2; see following

message:

14:54:27.531 [23563] <32> onlfi_freeze_fim_fs: FTL - open_ckpt:

Cannot open checkpoint on /mnt_vxvm/2G_concat :

fsckpt_get_api_version returns 1; mountable checkpoints not

supported with this version

Do one of the following:

■ Upgrade the client file system to a version that supports mountableVxFS Storage Checkpoints

■ Configure the policy with a snapshot method that supports the client’scurrent file system.

NetBackup status code: 157Message: suspend requested by administrator

Explanation: Status code 157 is an informational message, which indicates thatthe administrator suspended the job from the Activity Monitor. The job is in thesuspended state in the Activity Monitor. It can be resumed from the last checkpointby the administrator.

Recommended Action: The administrator can resume the job from the lastcheckpoint from the Activity Monitor.

249NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 158Message: failed accessing daemon lock file

Explanation: The process cannot lock its lock file because an error was receivedfrom a system call. This lock file synchronizes process activities (for example, itprevents more than one daemon from running at a time).

Recommended Action: Do the following, as appropriate:

■ Examine the NetBackup error log to determine why the system call failed.Then correct the problem. It may be a permission problem.

■ If the error log does not show the error, create a debug log directory for bprdor bpdbm (depending on which process encountered the error). Increase theunified logging level if nbpem, nbjm, or nbrb encountered the error. Use thevxlogcfg command as explained in the following topic:

See “Configuring and using unified logging” on page 94.Retry the operation and check the resulting debug log.

NetBackup status code: 159Message: licensed use has been exceeded

Explanation: A configuration limit was exceeded.

For example, a job fails with this error code if a policy is set up that specifies thefollowing:

■ A storage unit that is on a SAN media server

■ A client that is not the SAN media server itself

SAN media servers can only back up themselves.

This status code is used when the creation of a storage unit on a SAN media serverfails because "On demand only" is not selected. "On demand only" is required forstorage units on a SAN media server.

Recommended Action: To determine the cause of the error, examine theNetBackup All Log Entries report for the command that was ran. See also theActivity Monitor details for informative messages.

If the job fails on a SAN media server storage unit, ensure that only the local clientis specified in the policy. If remote clients are specified in the policy, do one ofthe following: remove them and place them in a policy that specifies a differentstorage unit or change the storage unit for that policy.

If you want to back up remote clients by using the SAN media server, you canpurchase a regular NetBackup media server license.

NetBackup status codes and messagesAbout NetBackup status codes and messages

250

NetBackup status code: 160Message: authentication failed

Explanation: NetBackup encounters a problem when two systems try toauthenticate one another.

Recommended Action: Do the following, as appropriate:

■ Ensure that the authentication libraries exist:On Windows:

install_path\NetBackup\lib\libvopie.dll

install_path\NetBackup\lib\libvnoauth.dll

On UNIX and Linux (except HP-UX):

/usr/openv/lib/libvopie.so

/usr/openv/lib/libvnoauth.so

On UNIX and Linux (HP-UX only):

/usr/openv/lib/libvopie.sl

/usr/openv/lib/libvnoauth.sl

On Macintosh:

:System Folder:Extensions:libvopie.dll

:System Folder:Extensions:libvnoauth.dll

■ Check the methods_allow.txt files on the systems that have problems toensure that authentication is enabled. The files are in the following locations:Windows: install_path\NetBackup\var\auth

UNIX and Linux: /usr/openv/var/auth

Macintosh: :System Folder:Preferences:NetBackup::

One system may report authentication failure (status code 160) while the othersystem reports that a network connection timed out (status code 41). In thiscase, authentication may be enabled in the methods_allow.txt file on the firstsystem but not on the second system.

■ On the systems with the authentication problem, remove the remote host thatis not authenticated from the methods_allow.txt file.

For example, if host A and host B have the problem, remove host A from thefile on host B and vice versa.Retry the operation. If the problem still exists, it indicates that connectionproblems are not related to authentication. If connections are now successful,proceed to the next step.

251NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Run bpauthsync -vopie on the master server to synchronize the key filesagain on the systems.On Windows:

install_path\NetBackup\bin\admincmd\bpauthsync -vopie

-servers -clients

On UNIX and Linux:

/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie

-servers -clients

■ Add back the names that were removed and retry the operation.

■ Create debug log directories for the processes that are involved inauthentication between NetBackup systems. These include:

■ On the server, create debug log directories for bprd, bpdbm, bpcd.

■ On the client, create debug log directories for bpbackup, bprestore, bpbkar(Windows only).

Retry the operation and check the logs.

NetBackup status code: 161Message: Evaluation software has expired.

Explanation: The time that was allowed for the NetBackup evaluation softwareended.

See www.symantec.com for ordering information.

Recommended Action: Obtain a licensed copy of NetBackup.

NetBackup status code: 162Message: incorrect server platform for license

Explanation: The platform identifier in the license key does not match theplatform type on which the key was installed.

RecommendedAction: Ensure that you use a license key that is intended for theplatform on which you plan to install.

NetBackup status code: 163Message: media block size changed prior resume

Explanation: Status code 163 is an informational message. It indicates that themedia block size was changed before a backup job from the last checkpoint

NetBackup status codes and messagesAbout NetBackup status codes and messages

252

resumed. Since the media block size must be consistent, the job was restartedfrom the beginning.

Recommended Action: Check the Activity Monitor job details for the job ID ofthe restarted job.

NetBackup status code: 164Message: unable to mount media because it is in a DOWN, or otherwise notavailable

Explanation: A restore was tried and the volume required for the restore was ina DOWN drive in a robot. Or, the slot is empty that should contain the volume.

Recommended Action: Do the following, as appropriate:

■ If volume is in a DOWN drive, remove it and place it in its designated slot.Then, retry the restore.

■ If the volume is in the wrong slot, use a robot inventory option to reconcilethe contents of the robot with the volume configuration.

NetBackup status code: 165Message: NB image database contains no image fragments for requested backupid/copy number

Explanation: A restore was tried and NetBackup has no record of the fragmentsthat are associated with the backup ID that has the files.

Recommended Action: Check the NetBackup Problems report for additionalinformation about the error. For detailed troubleshooting information, create adebug log directory for either bpdm or bptm (whichever applies) and retry theoperation. Check the resulting debug log.

NetBackup status code: 166Message: backups are not allowed to span media

Explanation: An end of media (EOM) was encountered while the backup imagewas written. The backup was terminated because the NetBackupDISALLOW_BACKUPS_SPANNING_MEDIA option was present in bp.conf (on UNIX andLinux) or in the registry (on Windows). The backup is retried automatically witha different volume if the backup tries attribute allows it in the NetBackup globalattribute configuration.

Recommended Action: None.

253NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 167Message: cannot find requested volume pool in EMM database

Explanation: A backup to a nonrobotic drive was tried and the tape manager(bptm) cannot find or add the specified volume pool.

Recommended Action: Verify the Media and Device Management volumeconfiguration. Check the NetBackup Problems report for more information aboutthe error. For detailed troubleshooting information, create a bptm debug logdirectory and retry the operation. Check the resulting debug log.

NetBackup status code: 168Message: cannot overwrite media, data on it is protected

Explanation: A catalog backup was tried to a volume that cannot be overwrittenbecause it contains data that by default NetBackup does not overwrite. (This dataincludes items such as tar, cpio, and ANSI.)

RecommendedAction: Replace the volume with a new one or set the NetBackupALLOW_MEDIA_OVERWRITE option to the appropriate value.

NetBackup status code: 169Message: media id is either expired or will exceed maximum mounts

Explanation: A backup or a catalog backup was tried and the volume selected foruse has reached its maximum number of mounts. The maximum number isspecified in the Media and Device Management volume configuration. For a regularbackup, the volume is automatically set to the SUSPENDED state and not usedfor further backups. For a NetBackup catalog backup, the operation terminatesabnormally.

Recommended Action: If the volume was suspended, wait until it expires andthen replace it. For NetBackup catalog backups, replace the media.

NetBackup status code: 170Message: third party copy backup failure

Explanation: Usually indicates a problem with the 3pc. file or the mover.conf

file. (For detailed causes, see recommended actions.)

For more information on these files, refer to the NetBackup Snapshot ClientConfiguration online document.

For help accessing this document, see "Snapshot Client Assistance" in theNetBackup Snapshot Client Administrator’s Guide.

NetBackup status codes and messagesAbout NetBackup status codes and messages

254

Recommended Action: Do the following, as appropriate:

■ If a non third-party copy device is listed in 3pc. file, correct it or remove thenon third-party copy device entry.

■ If an incorrect lun is specified in the 3pc. file or the device does not exist,correct the 3pc. file as appropriate.

■ If an appropriate mover.conf file (with or without file name extension) cannotbe found, the /usr/openv/netbackup/logs/bptm log may show the following:

09:51:04 [22281] <2> setup_mover_tpc: no

mover.conf.vertex_std_tpc or mover.conf file exists, cannot

perform TPC backup

09:51:04 [22281] <16> bptm: unable to find or communicate with

Third-Party-Copy mover for policy vertex_std_tpc

Make sure that an appropriatemover.conf file exists in/usr/openv/netbackup

on the media server. This file can be any of the following:

■ mover.conf.policy_name file, where policy_name exactly matches thename of the policy.

■ mover.conf.storage_unit_name, where storage_unit_nameexactly matchesthe name of the storage in the Backup Policy Management Policy attributesdialog box (such as nut-4mm-robot-tl4-0).

■ mover.conf file (no extension) for the configurations that have only onethird-party copy device.

Note that NetBackup looks for an appropriate mover.conf file in the order.

■ If the SCSI pass-through path of the third-party copy device, as entered in themover.conf file, does not exist, the bptm log may show the following:

09:50:12 [22159] <16> setup_mover_tpc: open of passthru path

/dev/sg/cXtXlX failed, No such file or directory

09:50:12 [22159] <16> bptm: unable to find or communicate with

Third-Party-Copy mover for policy vertex_std_tpc

Correct the SCSI pass-through path of the third-party copy device that isentered in the mover.conf file.

■ If the third-party copy device returned an error, you may see either of thefollowing messages in /usr/openv/netbackup/logs/bptm log:

cannot process extended copy error due to truncated sense data,

may be HBA problem

255NetBackup status codes and messagesAbout NetBackup status codes and messages

disk error occurred on extended copy command, key = 0x0, asc =

0x0, ascq = 0x0

(where key, asc, and ascq are all zero)

Your host-bus adapter (HBA) and its driver may need to be updated, orNetBackup Snapshot Client may not support them. The supported host-busadapters are listed.See the NetBackup Release Notes.

NetBackup status code: 171Message: media id must be 6 or less characters

Explanation: operation, such as using bpmedia to suspend or freeze a media ID,was tried and the media ID specified was longer than six alpha-numeric characters

Recommended Action: Retry the command with a valid media ID.

NetBackup status code: 172Message: cannot read media header, may not be NetBackup media or is corrupted

Explanation: When you loaded a volume for a backup or restore, the tape manager(bptm), did not find the expected tape header. This error can mean that a roboticdevice volume is not in the slot number that is in the Media and DeviceManagement volume configuration. It also can mean that a read error (I/O error)occurred.

Recommended Action: Do the following, as appropriate:

■ If the volume is in a robot that supports bar codes, verify the robot contentsby using a robot inventory option.

■ If the volume was mounted on a nonrobotic drive, verify that the correct volumewas mounted and assigned.

■ Check the NetBackup Problems report. If it shows a fatal read error, try theoperation again with another drive, if possible.

■ If your configuration has multiple servers or HBAs with access to your tapeservices, make sure the SCSI Reserve or Release is configured correctly. (Mostlikely, the tape services configuration is an SSO configuration.)For more information, refer to the NetBackup Shared Storage Guide.

NetBackup status code: 173Message: cannot read backup header, media may be corrupted

NetBackup status codes and messagesAbout NetBackup status codes and messages

256

Explanation: When the tape manager (bptm) searches for a backup image torestore, the following occurs: it cannot find the correct backup ID at the positionon the media where NetBackup expected it. This status code can indicate a drivehardware problem.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for clues as to what caused the error.

■ Try the restore on another drive if possible.

■ For detailed troubleshooting information, create a debug log directory for bptmand retry the operation. Check the resulting debug log.

NetBackup status code: 174Message: media manager - system error occurred

Explanation: An abnormal condition caused a tape manager (bptm) or disk manager(bpdm) failure.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report to see if it shows the cause of theproblem. If you see a Problems report message similar to the following, saveall logs and call Symantec customer support:

"attempted to write 32767 bytes, not a multiple of 512"

■ On UNIX and Linux, if this error occurs during a restore, the tape drive maybe incorrectly configured. It may be configured to write in fixed length modewhen it should write in variable length mode.Verify your drive’s configuration by comparing it to what is recommended inthe NetBackup Device Configuration Guide.If your configuration incorrectly specifies fixed length mode, change it tovariable length mode and suspend the media that were written on that device.The images that were written to those media may be restorable (platformdependent), but single file restores are likely to fail.

■ If the problem occurs with a particular client only, verify that the client binariesare correct, especially for bpcd.

■ If you can read or write any other images on this media, check the followingreports for clues:

■ Images on Media report

■ Media Contents report

■ Verify the following:

257NetBackup status codes and messagesAbout NetBackup status codes and messages

The media, by using the NetBackup image verify option.■

■ That you used the correct media type for the device.

■ Check the system or the console log for errors (on UNIX and Linux) or theEvent Viewer Application log (on Windows).

■ For detailed debug information, create a debug log directory for either bptmor bpdm (whichever applies) and retry the operation. Check the resulting debuglog.On UNIX and Linux, if the bptm debug log shows an error similar to thefollowing, the tape drive is configured to write in fixed length mode ratherthan variable length mode:

00:58:54 [2304] <16> write_data: write of 32768 bytes indicated

only 29696 bytes were written, errno = 0

The image being written encountered the end-of-media.

■ If the backup was configured for an OpenStorage disk storage unit, theOpenStorage vendor's plug-in may not be installed on all media servers in thestorage unit's media server list. Either install the vendor plug-in on all of themedia servers or remove from the list the servers that do not have the plug-ininstalled.

NetBackup status code: 175Message: not all requested files were restored

Explanation: When the bptm or the bpdm process restores files from an image, itdetected a fatal error condition and terminated the restore before it completed.Under normal circumstances, this error should not occur.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report and the status lot or the progress logon the client for additional information about the error

■ For detailed troubleshooting information, create a debug log directory foreither bptm or bpdm (whichever applies) and retry the operation. Check theresulting debug log.

NetBackup status code: 176Message: cannot perform specified media import operation

Explanation: The tape manager (bptm) detected an error condition when it triedto import a specific backup image.

NetBackup status codes and messagesAbout NetBackup status codes and messages

258

Possible reasons for this error are as follows:

■ Media ID is already active in the NetBackup media catalog on this server

■ Media ID is not in the volume configuration

■ Fatal tape manager (bptm) error occurred

■ Total image was not obtained from Phase 1 of import

■ The barcode and media ID do not match in the volume database. One possiblereason for a mismatch is when using tapes previously written by a differentbarcode, labels are placed into an ACSLS library using a new barcode label.Another possible reason is when the administrator attempts to change themedia ID field (using vmchange) to match the RVSN. When the inventory isupdated, the barcode and media ID are synchronized.

Recommended Action: Check the NetBackup Problems report to find the exactcause of the failure and try the following:

■ If the media ID is already active, duplicate all images on the original media IDto another volume. Then, manually expire the original media and redo theimport.

■ If the media ID is not present in the volume configuration, add it.

■ If you received a fatal bptm error, verify that the following are active: theNetBackup Volume Manager (vmd) on UNIX and Linux or the NetBackup VolumeManager on Windows.

■ If the entire image is not present, perform import phase 1 on the media IDsthat have the remainder of the image.

■ If the barcode and media ID are a mismatch, use a barcode label that matchesthe recorded media ID. Tapes can then be mounted in a drive with AVRDrunning so that the recorded media ID is displayed. Then, a barcode with thatlabel needs to be placed on the tape.

NetBackup status code: 177Message: could not deassign media due to Media Manager error

Explanation: The tape manager (bptm) cannot successfully unassign a media ID.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for the cause of the problem.

■ Verify that the NetBackup Volume Manager (vmd) is active on UNIX and Linuxor the NetBackup Volume Manager service is active on Windows.

259NetBackup status codes and messagesAbout NetBackup status codes and messages

■ For detailed troubleshooting information, create a debug log directory for bptmand retry the operation. Check the resulting debug log.

NetBackup status code: 178Message: media id is not in NetBackup volume pool

Explanation: NetBackup tried a backup of its catalogs and the media ID that wasspecified for the catalog backup was not in the NetBackup volume pool. Volumesfor catalog backups must be in the NetBackup volume pool.

Recommended Action: Check the Media and Device Management volumeconfiguration to verify that the media IDs are present and in the NetBackup volumepool.

NetBackup status code: 179Message: density is incorrect for the media id

Explanation: An operation such as "list contents" was tried on an invalid mediaID, such as a cleaning tape. Another possibility: a media ID in the NetBackupcatalog backup configuration does not match the media type that was entered inthe volume configuration.

Recommended Action: Check the volume configuration and the NetBackupcatalog backup configuration and correct any problems found.

NetBackup status code: 180Message: tar was successful

Explanation: tar returned a successful exit status.

Recommended Action: None.

NetBackup status code: 181Message: tar received an invalid argument

Explanation: One of the parameters that was passed to tar was not valid.

Recommended Action: Do the following, as appropriate:

■ On a UNIX or Linux client:

■ Ensure that the tar command in /usr/openv/netbackup/bin is the oneprovided by NetBackup. If you are in doubt, reinstall it.

■ Check /usr/openv/netbackup/bin/version on the client to verify thatthe client is running the correct level software. If the software is not at the

NetBackup status codes and messagesAbout NetBackup status codes and messages

260

correct level, update the software per the directions in the NetBackuprelease notes.

■ On a Windows client, create a tar debug log directory, retry the operation,and check the log.

■ On a Macintosh client, check the version file that is in the bin folder in theNetBackup folder in the Preferences folder. If the software is not at the correctlevel, install the correct software.See the NetBackup Installation Guide for UNIX.

NetBackup status code: 182Message: tar received an invalid file name

Explanation: tar cannot write to the file that is specified with the -f parameter.

Recommended Action: Do the following, as appropriate:

■ Create a bpcd debug log directory on the client (on a Macintosh, NetBackupcreates the log automatically).

■ On a Windows client, create a tar debug log directory.

■ Increase the logging level on the client:

■ On a UNIX or Linux client, add the VERBOSE option to the/usr/openv/netbackup/bp.conf file.

■ On PC clients, increase the debug or log level.See “How to set logging levels on PC clients” on page 122.

■ Rerun the operation, check the resulting debug logs for the parameters thatwere passed to tar and call customer support.

NetBackup status code: 183Message: tar received an invalid archive

Explanation: The data that was passed to tar was corrupt.

Recommended Action: Do the following, as appropriate:

■ If the problem is with a UNIX or Linux client, create a/usr/openv/netbackup/logs/tardebug log directory on the client and rerunthe operation.

■ Check the tar debug log file for any error messages that explain theproblem.

■ Restart the client to see if it clears the problem.

261NetBackup status codes and messagesAbout NetBackup status codes and messages

■ When you finish with your investigation of the problem, delete the/usr/openv/netbackup/logs/tar directory on the client.

■ If the problem is with a Microsoft Windows, NetWare, or Macintosh client, dothe following in the order presented:

■ Create a bpcd debug log directory on the client (on a Macintosh NetBackupcreates the log automatically).

■ On a Windows client, create a tar debug log directory.

■ Increase the debug or log level.See “How to set logging levels on PC clients” on page 122.

■ Rerun the operation and check the resulting debug logs.

■ Restart the client to see if it clears the problem.

NetBackup status code: 184Message: tar had an unexpected error

Explanation: A system error that occurred in tar.

Recommended Action: Do the following, as appropriate:

■ If the problem is with a UNIX or Linux client, create a/usr/openv/netbackup/logs/tardebug log directory on the client and rerunthe operation.

■ Check the tar debug log file for any error messages that explain theproblem.

■ Restart the client to see if it clears the problem.

■ When you finish your investigation of the problem, delete the/usr/openv/netbackup/logs/tar directory on the client.

■ If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

■ Create a bpcd debug log directory on the client (on a Macintosh NetBackupcreates the log automatically).

■ Increase the debug or log level.See “How to set logging levels on PC clients” on page 122.

■ On a Windows client, create a tar debug log directory.

■ Retry the operation and check the resulting debug logs.

■ Restart the client to see if it clears the problem.

NetBackup status codes and messagesAbout NetBackup status codes and messages

262

NetBackup status code: 185Message: tar did not find all the files to be restored

Explanation: The tar file list contained files that were not in the image.

Recommended Action: Do the following, as appropriate:

■ If the problem is with a UNIX or Linux client:

■ Enable bpcd debug logging by creating the/usr/openv/netbackup/logs/bpcd directory on the client.

■ Rerun the operation, check the resulting bpcd log file for the parametersthat were passed to tar, and call customer support.

■ If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

■ Create a bpcd debug log directory on the client (on a Macintosh NetBackupcreates the log automatically).

■ Increase the debug or log level.See “How to set logging levels on PC clients” on page 122.

■ On a Windows client, create a tar debug log directory.

■ Retry the operation.

■ Check the resulting debug logs for the parameters that were passed to tar

and call customer support.

NetBackup status code: 186Message: tar received no data

Explanation: NetBackup did not send data to tar.

Recommended Action: Do the following, as appropriate:

■ Retry the operation and check the status or the progress log on the client forany error messages that reveal the problem.

■ Verify that the tape is available and readable.

■ Verify that the drive is in an UP state. Use the Device Monitor.

■ For detailed troubleshooting information:

■ Create a bptm debug log on the server.

■ On a Windows client, create a tar debug log.

■ Retry the operation and check the resulting debug logs.

263NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 189Message: the server is not allowed to write to the client’s filesystems

Explanation: The client does not allow writes from the server.

Recommended Action: Perform the following to perform restores or installsoftware from the server.

■ On a UNIX or Linux client, delete DISALLOW_SERVER_FILE_WRITES from the/usr/openv/netbackup/bp.conf file.

■ On a Microsoft Windows or NetWare nontarget client, select Allowserver-directedrestores on the General tab in the NetBackup Client Propertiesdialog box. To display this dialog box, start the Backup, Archive, and Restoreinterface on the client and select NetBackup Client Properties from the Filemenu.

■ On a Macintosh client, deleteDISALLOW_SERVER_FILE_WRITES from thebp.conffile in the NetBackup folder in the Preferences folder.

■ On a NetWare target client, set ALLOW_SERVER_WRITE to yes in the bp.ini file.

NetBackup status code: 190Message: found no images or media matching the selection criteria

Explanation: A verify, duplicate, or import was tried and no images that matchedthe search criteria were found in the NetBackup catalog.

Recommended Action: Change the search criteria and retry.

NetBackup status code: 191Message: no images were successfully processed

Explanation: A verify, duplicate, or import was tried and failed for all selectedimages.

Recommended Action: Do the following, as appropriate:

■ Check the NetBackup Problems report for the cause of the error. To obtaindetailed troubleshooting information, create an admin debug log directory andretry the operation. Check the resulting debug log.

■ If the error was encountered during duplication of backups, check theduplication progress log to help determine the root cause of the problem.

■ If a Vault job encountered the error responsible for the duplication, check theduplicate.log files in your sidxxx directories to determine the root cause:

NetBackup status codes and messagesAbout NetBackup status codes and messages

264

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

NetBackup status code: 192Message: VxSS authentication is required but not available

Explanation: On one side of a NetBackup network connection, the system requiresVxSS authentication. On the other side of the connection, the other system is notconfigured to use VxSS. VxSS authentication is used with the NetBackup AccessControl feature (NBAC). The connection was terminated because VxSSauthentication cannot be completed.

RecommendedAction: Make sure both systems are configured to use NetBackupAccess Control VxSS authentication with each other. Or, make sure both systemsare not configured to use VxSS with each other. The first thing to check is the UseVxSS Host properties value on each system. If one is configured for REQUIRED,the other must be configured for REQUIRED or AUTOMATIC. If one is configuredfor PROHIBITED, the other must be configured for PROHIBITED or AUTOMATIC.

See theNetBackupAdministrator’sGuide,Volume I, for the following information:how to set the Access Control related host properties, and how to configure asystem to use Access Control.

NetBackup status code: 193Message: VxSS authentication is requested but not allowed

Explanation: On one side of a NetBackup network connection, the system requiresVxSS authentication. The system on the other side of the connection is notconfigured to use VxSS. VxSS authentication is used with the NetBackup AccessControl feature (NBAC). The connection has been terminated because VxSSauthentication cannot be completed.

RecommendedAction: Make sure both systems are configured to use NetBackupAccess Control VxSS authentication with each other. Or, make sure both systemsare not configured to use VxSS with each other. The first thing to check is the UseVxSS Host properties value on each system. If one is configured for REQUIRED,the other must be configured for REQUIRED or AUTOMATIC. If one is configuredfor PROHIBITED, the other must be configured for PROHIBITED or AUTOMATIC.

265NetBackup status codes and messagesAbout NetBackup status codes and messages

See theNetBackupAdministrator’sGuide,Volume I, for the following information:how to set the Access Control related host properties how to configure a systemto use Access Control.

NetBackup status code: 194Message: the maximum number of jobs per client is set to 0

Explanation: The NetBackup Maximumjobsperclient global attribute is currentlyset to 0. Set the value to 0 to disable backups and archives.

Recommended Action: To enable backups and archives, change the Maximumjobsperclient value to the wanted nonzero setting. This attribute is on the GlobalNetBackup Attributes tab in the Master Server Properties dialog box.

See “Using the Host Properties window” on page 61.

NetBackup status code: 195Message: client backup was not attempted

Explanation: A backup job was in the NetBackup scheduler but was not tried.

Recommended Action: Do the following, as appropriate:

■ Retry the backup either immediately with a manual backup or allow the normalscheduler retries.

■ For additional information, check the All Log Entries report. For detailedtroubleshooting information, increase the logging level for the diagnostic anddebug logs for nbpem, nbjm, and nbrb.Use the vxlogcfg command as explained in the following topic:

See “Configuring and using unified logging” on page 94.After the next backup try, check the logs.

■ The following are some actions to perform:

■ Verify that the vmd and the ltid daemons (UNIX and Linux) or theNetBackup Volume Manager and NetBackup Device Manager services(Windows) are running.

■ Look for a problem in an earlier backup that made the media or the storageunit unavailable.

NetBackup status code: 196Message: client backup was not attempted because backup window closed

Explanation: A backup or an archive operation that the backup scheduler queuedwas not tried because the backup window was no longer open.

NetBackup status codes and messagesAbout NetBackup status codes and messages

266

Recommended Action: Do the following, as appropriate:

■ If possible, change the schedule to extend the backup window for thiscombination of policy and schedule so it does not occur again.

■ If the backup must be run, use the Manual Backup command on the Policymenu in the Backup Policy Management window to perform the backup. Manualbackups ignore the backup window.

NetBackup status code: 197Message: the specified schedule does not exist in the specified policy

Explanation: A user backup or archive request specified the exact policy andschedule to use when a backup is performed. The policy exists but does not containthe schedule.

■ On Microsoft Windows and NetWare nontarget clients, you can specify a policyor schedule on the Backups tab in the NetBackup Client Properties dialog box.To display this dialog box, start the Backup, Archive, and Restore interface onthe client and select NetBackup Client Properties on the File menu.

■ On UNIX, Linux, and Macintosh clients, you can specify a policy or scheduleby using the bp.conf options, BPBACKUP_POLICY or BPBACKUP_SCHED.

■ On NetWare target clients, you can specify a policy or schedule in the bp.inifile.

Recommended Action: Do the following, as appropriate:

■ Check the client progress log (if available) to determine the policy and schedulethat were specified.

■ Check the configuration on the master server to determine if the schedule isvalid for the policy. If the schedule is not valid, either add the schedule to thepolicy configuration or specify a valid schedule on the client.

NetBackup status code: 198Message: no active policies contain schedules of the requested type for this client

Explanation: A user backup or archive was requested, and this client is not in apolicy that has a user backup or archive schedule.

RecommendedAction:Determine if the client is in any policy that has a scheduleof the appropriate type (either user backup or archive).

■ If the client is in such a policy, check the general policy attributes to verifythat the policy is set to active.

■ If the client is not in such a policy, do either of the following:

267NetBackup status codes and messagesAbout NetBackup status codes and messages

Add a schedule of the appropriate type to an existing policy that has thisclient

■ Create a new policy that has this client and a schedule of the appropriatetype

NetBackup status code: 199Message: operation not allowed during this time period

Explanation: A user backup or archive was requested and this client is not in apolicy that has the following: a user backup or archive schedule with an openbackup window. This error implies that an appropriate policy and schedulecombination exists for this client.

Recommended Action: Determine the policies to which this client belongs thatalso have a schedule of the appropriate type (either user backup or archive).

■ If possible, retry the operation when the backup window is open.

■ If the backup window is not open during appropriate time periods, adjust abackup window for a schedule in one of the policies.

NetBackup status code: 200Message: scheduler found no backups due to run

Explanation: When the NetBackup scheduler process (nbpem) checked the policyand the schedule configuration, it did not find any clients to back up.

This error may be due to the following:

■ No backup time windows are open (applies only to full and to incrementalschedules).

■ Policies are set to inactive.

■ The clients were recently backed up and are not due for another backup (basedon Frequency setting for the schedules).

■ Policies do not have any clients.

Recommended Action: Usually, this message can be considered informationaland does not indicate a problem. However, if you suspect a problem, do thefollowing:

■ Examine the NetBackup All Log Entries report for any messages in additionto the one that indicates the scheduler found nothing to do.

■ Examine the policy configuration for all policies or the specific policy inquestion to determine if any of the reasons in the Explanation section apply.

NetBackup status codes and messagesAbout NetBackup status codes and messages

268

■ To obtain detailed troubleshooting information, increase the unified logginglevel for the diagnostic and debug logs.Use the vxlogcfg command as explained in the following procedure:

See “Configuring and using unified logging” on page 94.Retry the operation and check the resulting logs.

NetBackup status code: 201Message: handshaking failed with server backup restore manager

Explanation: A process on the master server encountered an error when itcommunicated with the media host (can be either the master or a media server).This error means that the master and the media server processes were able toinitiate communication, but were not able to complete them. This problem canoccur during a backup, restore, or media list in a single or a multiple serverconfiguration.

Recommended Action: Do the following, as appropriate:

■ Determine the activity that encountered the handshake failure by examiningthe NetBackup All Log Entries report for the appropriate time period. If thereare media servers, determine if:

■ The handshake failure was encountered between the master and a mediaserver.or

■ Only the master server was involved.

■ If necessary, create the following debug log directories and increase the logginglevel:

■ bpcd on the NetBackup media host (can be either the master or a mediaserver).

■ If the error was encountered during a backup operation, increase the logginglevel for the diagnostic and debug logs for nbpem, nbjm, and nbrb.Use the vxlogcfg command as explained in the following procedure:

See “Configuring and using unified logging” on page 94.

■ If the error was encountered during a restore operation, bprd on the masterserver.

■ If the error was encountered during a media list operation, admin in theNetBackup logs/admin directory on the master server.

■ Status code 201 may occur if nbjm fails after connecting to bpbrm or bpmountbut before the policy file list is sent. Examine the nbjm unified log (originator

269NetBackup status codes and messagesAbout NetBackup status codes and messages

ID 117) or the bpbrm or the bpmount legacy logs for more detail on the causeof the error.

■ Retry the operation and examine the resulting debug logs for information onwhy the error occurred.

NetBackup status code: 202Message: timed out connecting to server backup restore manager

Explanation: A master server process that tried to initiate communications withthe media host timed out (can be either the master or a media server). This problemcan occur during a backup or restore in either a single or a multiple serverconfiguration.

Recommended Action: Determine which activity encountered the connectiontimeout failure by examining the All Log Entries report for the appropriate timeperiod. If there are media servers, determine if the timeout occurred between themaster and a media server or if only the master was involved.

■ Verify that the schedule specifies the correct storage unit.

■ Run the ping command from one host to another by using the followingcombinations:

■ From the master server, ping the master and all media servers by usingthe host names that are found in the storage unit configuration.

■ From each of the media servers, ping the master server by using the hostname that is specified in the NetBackup server list. On a UNIX or Linuxserver, the master is the first SERVER entry in the bp.conf file. On aWindows server, the master is designated on the Servers tab in the MasterServer Properties dialog box.To access this dialog box, see the following:See “Using the Host Properties window” on page 61.

■ Verify that the master server can communicate with bpcd on the host that hasthe storage unit.

■ Perform the following procedures:See “Testing media server and clients” on page 38.See “Resolving network communication problems” on page 40.

■ If necessary, create debug log directories for the following processes and retrythe operation. Then, check the resulting debug logs on the master server:

■ If the error occurred during a backup operation, increase the logging levelfor the diagnostic and debug logs for nbpem, nbjm, and nbrb.Use the vxlogcfg command as explained in the following procedure:

NetBackup status codes and messagesAbout NetBackup status codes and messages

270

See “Configuring and using unified logging” on page 94.Also, check the bpcd legacy debug logs.

■ If the error occurs during a restore operation, check the bprd debug logs.

NetBackup status code: 203Message: server backup restore manager’s network is unreachable

Explanation: A process on the master server cannot connect to a particular hoston the network when it tries to initiate communication with the media host. Thisproblem can occur during a backup or restore in either a single or a multiple serverconfiguration.

Recommended Action: Determine which activity encountered this failure byexamining the All Log Entries report for the appropriate time frame. If there ismore than one NetBackup server (one or more media servers), determine thefollowing: if the failure was between the master and a media server or if only themaster server was involved. Run the ping command from one host to another byusing the following combinations:

■ From the master server, ping the master and all media servers by using thehost names in the storage unit configuration.

■ From each of the media servers, ping the master server host by using the hostname that is specified in the NetBackup server list. On a UNIX or Linux server,the master is the first SERVER entry in the bp.conf file. On a Windows server,the master is designated on the Servers tab in the Master Server Propertiesdialog.To access this dialog box, see the following topic:See “Using the Host Properties window” on page 61.

■ Perform the following procedures:See “Testing media server and clients” on page 38.See “Resolving network communication problems” on page 40.

■ If necessary, create debug log directories for bprd and retry the operation.Then, check the resulting debug logs on the master server. If the error occurredduring a restore, check the bprd debug logs.

NetBackup status code: 204Message: connection refused by server backup restore manager

Explanation: The media host refused a connection on the port number for bpcd.This error can be encountered during a backup or restore.

271NetBackup status codes and messagesAbout NetBackup status codes and messages

RecommendedAction:Run the ping command from one host to another by usingthe following combinations:

■ From the master server, ping the master and all media servers by using thehost names in the storage unit configuration.

■ From each of the media servers, ping the master server by using the name thatwas specified in the NetBackup server list. On a UNIX or Linux server, thismaster is the first SERVER entry in the bp.conf file. On a Windows server, themaster is designated on the Servers tab in the Master Server Properties dialogbox. The following topic shows how to access this dialog box:See “Using the Host Properties window” on page 61.

■ On UNIX and Linux servers, verify that the bpcd entries in /etc/services orNIS on all the servers are identical. Verify that the media host listens on thecorrect port for connections to bpcd. To verify, run one of the followingcommands (depending on platform and operating system):

netstat -a | grep bpcd

netstat -a | grep 13782 (or the value that was specified during the install)

rpcinfo -p | grep 13782 (or the value that was specified during the install)

On UNIX and Linux servers, it may be necessary to change the service numberfor the following: bpcd in /etc/services and the NIS services map and sendSIGHUP signals to the inetd processes on the clients.

/bin/ps -ef | grep inetd

kill -HUP the_inetd_pid

or

/bin/ps -aux | grep inetd

kill -HUP the_inetd_pid

Note: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP toinetd.

■ On Windows servers, do the following:

■ Verify that the bpcd entries are correct in the following:

%SystemRoot%\system32\drivers\etc\services

■ Verify that the following numbers match the settings in the services file:NetBackup Client Service Port number and NetBackup Request Service

NetBackup status codes and messagesAbout NetBackup status codes and messages

272

Port number on the Network tab in the NetBackup Client Properties dialogbox. To display this dialog box, start the Backup, Archive, and Restoreinterface and select NetBackup Client Properties on the File menu.The values on the Network tab are written to the services file when theNetBackup Client service starts.

■ Stop and restart the NetBackup services.

■ Perform the following procedures:See “Testing media server and clients” on page 38.See “Resolving network communication problems” on page 40.

■ If necessary, create debug log directories for bprd and retry the operation.Then, check the resulting debug logs on the master server:

■ If the error occurred during a backup operation, check the nbpem, nbjm, andnbrb logs by using the vxlogview command.

■ If the error occurred during a restore operation, check the bprd debug logs.

Also, see the following topic:

See “Resolving network communication problems” on page 40.

NetBackup status code: 205Message: cannot connect to server backup restore manager

Explanation: A process on the master server cannot connect to a process on ahost on the network. This error occurs when the process tries to initiatecommunication with the server that has the storage unit. This problem can occurduring a backup or restore in either a single or a multiple server configuration.

RecommendedAction:Run the ping command from one host to another by usingthe following combinations:

■ From the master server, ping the master and all media servers by using thehost names in the storage unit configuration.

■ From each of the media servers, ping the master server by using the name thatis specified in the NetBackup server list. On a UNIX or Linux server, this masteris the first SERVER entry in the bp.conf file. On a Windows server, the masteris designated on the Servers tab in the Master Server Properties dialog box.To access this dialog box, see the following topic:See “Using the Host Properties window” on page 61.

■ On a UNIX or Linux server, verify that the bpcd entry in /etc/services orNIS on all the servers are identical. Verify that the media host listens on the

273NetBackup status codes and messagesAbout NetBackup status codes and messages

correct port for connections to bpcd. To verify, run one of the followingcommands (depending on platform and operating system):

netstat -a | grep bpcd

netstat -a | grep 13782 (or the value that is specified during the install)

rpcinfo -p | grep 13782 (or the value that is specified during the install)

■ On Windows servers, do the following:

■ Verify that the bpcd entries are correct in the services file:

%SystemRoot%\system32\drivers\etc\services

■ Verify that the following numbers match the settings in the services file:NetBackup Client Service Port number and NetBackup Request ServicePort number on the Network tab in the NetBackup Client Properties dialogbox. To display this dialog box, start the Backup, Archive, and Restoreinterface and select NetBackup Client Properties on the File menu.The values on the Network tab are written to the services file when theNetBackup Client service starts.

■ Stop and restart the NetBackup services.

■ Perform the following procedures:See “Testing media server and clients” on page 38.See “Resolving network communication problems” on page 40.

■ Create a bpcd debug log directory on the server that has the storage unit andretry the operation. Then, check for additional information in the debug log.

Also, see the following topic:

See “Resolving network communication problems” on page 40.

NetBackup status code: 206Message: access to server backup restore manager denied

Explanation: The master server tries to start a process on another server (oritself) but does not appear in the NetBackup server list on that server. On a UNIXor Linux server, the master is the first SERVER entry in the bp.conf file. On aWindows server, the master is designated on the Servers tab in the Master ServerProperties dialog box. To access this dialog box, see the following topic:

See “Using the Host Properties window” on page 61.

Recommended Action: Do the following, as appropriate:

NetBackup status codes and messagesAbout NetBackup status codes and messages

274

■ Verify that the master server appears as a server in its own server list as wellas being listed on all media servers.If you change the server list on a master server, stop and restart the NetBackupdatabase manager and request the following: daemons (UNIX and Linux) orthe NetBackup Database Manager and NetBackup Request Manager services(Windows).

■ If necessary, create debug log directories for bprd and retry the operation.Then, check the resulting debug logs on the master server:

■ If the error occurred during a backup operation, check the nbpem, nbjm, andnbrb logs by using the vxlogview command.

■ If the error occurred during a restore operation, check the bprd debug logs.

NetBackup status code: 207Message: error obtaining date of last backup for client

Explanation: When nbpem tries to obtain the date of the last backup for a particularclient, policy, and schedule combination, an error occurs.

Recommended Action: Do the following, as appropriate:

■ Verify that the NetBackup database manager (bpdbm) process (on UNIX andLinux) or the NetBackup Database Manager service (on Windows) is running.

■ Examine the All Log Entries report for the appropriate time frame to gathermore information about the failure.

■ For detailed troubleshooting information, create a bpdbm log directory on themaster server. Increase the logging level for the diagnostic and debug logs fornbpem.

Use the vxlogcfg command as explained in the following topic:

See “Configuring and using unified logging” on page 94.Retry the operation, then check the resulting logs.

NetBackup status code: 209Message: error creating or getting message queue

Explanation: When a NetBackup process tries to create an internal message queueconstruct for inter-process communication, an error occurs. This error indicatesa problem on the master server. On UNIX and Linux systems, this error may bedue to a lack of system resources for System V inter-process communication.

275NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Create debug log directories on the master server andretry the operation. Then, determine the type of system failure by examining thelogs. Start with the bprd debug log.

On UNIX and Linux servers, also gather the output of the ipcs -a command tosee what system resources are currently in use.

NetBackup status code: 210Message: error receiving information on message queue

Explanation: When a NetBackup process tries to receive a message from aNetBackup daemon using bprd on an internal message queue construct, an erroroccurs. This error indicates a problem on the master server. On UNIX and Linuxsystems, this error may be due to a lack of system resources for System Vinter-process communication.

Recommended Action: Create debug log directories on the master server andretry the operation. Then, determine the type of system failure by examining thelogs. Start with the bprd debug log.

On UNIX and Linux servers, also gather the output of the ipcs -a command tosee what system resources are currently in use.

NetBackup status code: 212Message: error sending information on message queue

Explanation: When a NetBackup process tries to attach to an already existinginternal message queue construct for inter-process communication, an erroroccurs. This error indicates a problem on the master server. On UNIX and Linuxsystems, this error may be due to a lack of system resources for System Vinter-process communication.

Recommended Action: Create debug log directories on the master server andretry the operation. Then, determine the type of system failure by examining thelogs. Start with the bprd debug log.

On UNIX and Linux servers, also, gather the output of the ipcs -a command tosee what system resources are currently in use.

NetBackup status code: 213Message: no storage units available for use

Explanation: The NetBackup resource broker (nbrb) did not find any storage unitsavailable for use. Either all storage units are unavailable or all storage units are

NetBackup status codes and messagesAbout NetBackup status codes and messages

276

configured for On demand only. In addition, the policy and schedule does notrequire a specific storage unit.

Recommended Action: Do the following, as appropriate:

■ Examine the Backup Status and All Log Entries report for the appropriate timeperiod to determine the policy or schedule that received the error.

■ Verify that the storage unit’s drives are not down.

■ Verify the following attribute settings for all storage units:

■ For disk storage units, the Maximum concurrent jobs is not set to 0

■ For Media Manager storage units, the Maximum concurrent write drivesis not set to 0

■ Verify that the robot number and host name in the storage unit configurationmatches the Media and Device Management device configuration.

■ Determine if all storage units are set to Ondemandonly for a combined policyand schedule that does not require a specific storage unit. In this case, eitherspecify a storage unit for the policy and the schedule combination or turn offOn demand only for a storage unit.

■ If the storage unit is on a UNIX or Linux NetBackup media server, it mayindicate a problem with bpcd. Check /etc/inetd.conf on the media server toverify that the bpcd entry is correct.

If the storage unit is on a Windows NetBackup media server, verify that theNetBackup Client service was started on the Windows NetBackup media server.

■ For detailed troubleshooting information, increase the logging levels of nbrband mds on the master server.

Use the vxlogcfg command as explained in the following topic:

See “Configuring and using unified logging” on page 94.Retry the operation and check the resulting debug logs.

NetBackup status code: 215Message: failed reading global config database information

Explanation: During the periodic checking of the NetBackup configuration,nbproxy was unable to read the global configuration parameters.

Recommended Action: Do the following, as appropriate:

■ On UNIX and Linux master servers, verify that the NetBackup databasemanager (bpdbm) process is running. On a Windows master server, verify thatthe NetBackup Database Manager service is running.

277NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Try to view the global configuration settings by using the NetBackupadministration interface (on UNIX and Linux systems), or by using HostProperties (on Windows systems).

■ For detailed troubleshooting information, create debug log directories fornbproxy and bpdbm on the master server and retry the operation. Check theresulting debug logs for these processes. Also check the nbpem logs by usingthe vxlogview command.

NetBackup status code: 216Message: failed reading retention database information

Explanation: During its periodic checking of the NetBackup configuration, nbpemdid not read the list of retention levels and values.

Recommended Action: Do the following, as appropriate:

■ On a UNIX or Linux master server, verify that the NetBackup database manager(bpdbm) process is running. On a Windows master server, verify that theNetBackup Database Manager service is running.

■ For detailed troubleshooting information, create a debug log directory forbpdbm on the master server.

Increase the logging level for nbpem by using the vxlogcfg command asdescribed in the following topic:See “Configuring and using unified logging” on page 94.Retry the operation and check the resulting logs.

NetBackup status code: 217Message: failed reading storage unit database information

Explanation: During its periodic checking of the NetBackup configuration, nbpemdid not read the storage unit configuration.

Recommended Action: Do the following, as appropriate:

■ On a UNIX or Linux server, verify that the NetBackup database manager (bpdbm)process is running. On a Windows server, verify that the NetBackup DatabaseManager service is running.

■ Try to view the storage unit configuration by using the NetBackupadministration interface.

■ For detailed troubleshooting information, create debug logs for nbproxy andbpdbm on the master server and retry the operation. Check the resulting debuglogs. Also check the nbpem logs by using the vxlogview command.

NetBackup status codes and messagesAbout NetBackup status codes and messages

278

Ensure that the correct master server is specified for the connection.

NetBackup status code: 218Message: failed reading policy database information

Explanation: During the periodic checking of the NetBackup configuration, nbpemdid not read the backup policy configuration.

Recommended Action: Do the following, as appropriate:

■ On a UNIX or Linux server, verify that the NetBackup Database Manager(bpdbm) process is running. On a Windows server, verify that the NetBackupDatabase Manager service is running.

■ Try to view the policy configuration by using the NetBackup administrationinterface.

■ For detailed troubleshooting information, create debug log directories fornbproxy and bpdbm on the master server and retry the operation. Check theresulting debug logs. Also check the nbpem logs by using the vxlogview

command.Ensure that the correct master server is specified for the connection.

NetBackup status code: 219Message: the required storage unit is unavailable

Explanation: The policy or schedule for the backup requires a specific storageunit, which is currently unavailable. This error also occurs for other tries to usethe storage unit within the current backup session.

Recommended Action: Look in the Job Details window for the failed job.

■ Verify that the schedule specifies the correct storage unit and the storage unitexists.

■ Verify that the following devices are running: the Media Manager devicedaemon (ltid) (UNIX or Linux server) or the NetBackup Device Manager service(Windows server). Use bpps on UNIX and Linux and the Activity Monitor onWindows or the Services application in the Windows Control Panel.

■ Verify the following attribute settings:

■ For a disk storage unit, Maximum concurrent jobs is not set to 0.

■ For a Media Manager storage unit, the Maximum concurrent drivesattribute is not set to 0.

■ If the storage unit is a tape, verify that at least one of the drives is in the UPstate. Use the Device Monitor.

279NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Verify that the robot number and host in the storage unit configuration matchwhat is specified in the Media and Device Management device configuration.

■ Verify that the master server can communicate with the bpcd process on theserver that has the storage unit.

■ Verify that bpcd listens on the port for connections.

On a UNIX or Linux server where the storage unit is connected, if you runnetstat -a | grep bpcd, it should return something similar to thefollowing:

*.bpcd *.* 0 0 0 0 LISTEN

On a Windows NetBackup server where the storage unit is connected, runnetstat -a to print several lines of output. If bpcd listens, one of thoselines is similar to the following:

TCP myhost:bpcd 0.0.0.0:0 LISTENING

■ Check the nbrb and the mds logs by using the vxlogview command.

■ If the cause of the problem is not obvious, perform some of the steps in thefollowing procedure:See “Resolving network communication problems” on page 40.

NetBackup status code: 220Message: database system error

Explanation: The bpdbm process (UNIX and Linux), or the NetBackup DatabaseManager service (Windows) did not create a directory path for its configurationcatalogs. This error is due to a system call failure, which is usually due to apermission problem or an "out of space" condition.

Recommended Action: Create a debug log directory for bpdbm. Increase thelogging level for the diagnostic and debug logs for nbemm.

Use the vxlogcfg command as explained in the following topic:

See “Configuring and using unified logging” on page 94.

Retry the operation and check the resulting logs for information.

NetBackup status code: 221Message: continue

Explanation: This status code is used to coordinate communication betweenvarious NetBackup processes and normally does not occur. If the logs show that

NetBackup status codes and messagesAbout NetBackup status codes and messages

280

it is associated with a subsequent error, it usually indicates a communicationproblem. In this case, concentrate your troubleshooting efforts on the subsequenterror.

Recommended Action: Determine the cause of the status code that follows thisone.

NetBackup status code: 222Message: done

Explanation: This status code is used to coordinate communication betweenvarious NetBackup processes and is normally not seen. If the error logs show thatit is associated with a subsequent error, it usually indicates a communicationproblem. In this case, concentrate your troubleshooting efforts on the subsequenterror.

Recommended Action: Determine the cause of the status code that follows thisone.

NetBackup status code: 223Message: an invalid entry was encountered

Explanation: A request to thebpdbmprocess (on UNIX and Linux) or the NetBackupDatabase Manager service (on Windows) had invalid information or someinformation that conflicted. This error is usually a result of the use of softwarefrom different versions. Another cause can be incorrect parameters on a command.

RecommendedAction: Verify that all NetBackup software is at the same versionlevel and the command parameters are specified correctly. If neither of these isthe problem, obtain detailed troubleshooting information by creating a bpdbm

debug log directory. Then retry the operation. Check the resulting debug log.

NetBackup status code: 224Message: there was a conflicting specification

Explanation: A request to thebpdbmprocess (on UNIX and Linux) or the NetBackupDatabase Manager service (on Windows) had some information that conflicted.This error is usually a result of the use of software from different version levelstogether.

RecommendedAction: Verify that all NetBackup software is at the same versionlevel. If that is not the problem, obtain detailed troubleshooting information bycreating bpdbm and admin debug log directories. Then retry the operation. Checkthe resulting debug logs.

281NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 225Message: text exceeded allowed length

Explanation: Text in a request exceeds a buffer size. The request was made tothebpdbmprocess (on UNIX and Linux) or the NetBackup Database Manager service(on Windows). This error is usually a result of the use of software from differentversion levels.

RecommendedAction: Verify that all NetBackup software is at the same versionlevel. If that is not the problem, create debug log directories for bpdbm and admin.Then, retry the operation and examine the resulting debug logs.

NetBackup status code: 226Message: the entity already exists

Explanation: The configuration already has an entity with the same name ordefinition. For example: this status appears if you add a new policy when anexisting policy has the same name or definition such as attributes or clients.

Recommended Action: Correct your request and re-execute the command.

NetBackup status code: 227Message: no entity was found

Explanation: The item requested was not in the catalog. For example, the entitycan be a file or it can be policy information.

Recommended Action: A common cause for this problem is a query that has nomatching images. Specify different parameters or options for the operation andtry it again.

NetBackup status code: 228Message: unable to process request

Explanation: An inconsistency exists in the catalog or a request was made thatwould be improper to satisfy.

Recommended Action: Do the following, as appropriate:

■ If this status involves a media server, verify that its server list specifies thecorrect master server. On a UNIX or Linux server, the master server is the firstSERVER entry in the bp.conf file. On a Windows server, the master is designatedon the Servers tab in the Master Server Properties dialog box.To access this dialog box, see the following topic:See “Using the Host Properties window” on page 61.

NetBackup status codes and messagesAbout NetBackup status codes and messages

282

■ For detailed troubleshooting information, create a bpdbm debug log directoryand retry the operation. Then, check the resulting debug log.

NetBackup status code: 229Message: events out of sequence - image inconsistency

Explanation: A request was made that would cause the image catalog to becomeinconsistent if satisfied

RecommendedAction: Obtain detailed troubleshooting information by creatinga debug log directory for bpdbm. Then, retry the operation, save the resultingdebug log, and call customer support.

NetBackup status code: 230Message: the specified policy does not exist in the configuration database

Explanation: The specified policy name does not exist.

Recommended Action: Correct your parameters or options and retry theoperation.

NetBackup status code: 231Message: schedule windows overlap

Explanation: The specified start and the duration times for one day of the scheduleoverlap with another day of the schedule.

RecommendedAction: Correct the schedule to eliminate the overlapping backupwindows.

NetBackup status code: 232Message: a protocol error has occurred

Explanation: This error is an intermediate status code that usually precedesanother status code. It indicates the following: either the bpdbm process (on UNIXand Linux) or the NetBackup Database Manager service (on Windows) or theprocess that communicates with it has received unexpected information.

Recommended Action: Create a debug log directory for bpdbm. Then, retry theoperation, save the debug log, and call customer support.

NetBackup status code: 233Message: premature elf encountered

283NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: This status code is an intermediate one that usually precedes anotherstatus code and is associated with a problem in network communication.

Recommended Action: During a restore, this status codes means that tar (onthe client) received a stream of data that was not what it expected. If the restoreis a new configuration, verify that the tape drive is configured for variable mode.

See the NetBackup Device Configuration Guide.

If the communication failure is not due to an interrupt on a client system, saveall error information and call customer support.

NetBackup status code: 234Message: communication interrupted

Explanation: This status code is an intermediate one that usually precedes anotherstatus code and is associated with a problem in network communication. Eithera server or a client process received an interrupt signal.

Recommended Action: Save all error information and call customer support.

NetBackup status code: 235Message: inadequate buffer space

Explanation: This code usually indicates a mismatch between server and clientsoftware versions.

Recommended Action: Do the following, as appropriate:

■ Verify that all NetBackup software is at the same version level. Update earlierversions of NetBackup software.

■ On UNIX and Linux, NetBackup servers and clients, check the/usr/openv/netbackup/bin/version file.

■ On Windows NetBackup servers, check theinstall_path\NetBackup\version.txt file or the AboutNetBackup itemon the Help menu.

■ On Microsoft Windows clients, check the About NetBackup item on theHelp menu.

■ On NetWare target clients, check the Version entry in the bp.ini file.

■ If the client software is earlier than 3.0, verify that the client is in a Standardtype policy.

■ On Macintosh clients, check the version file in the bin folder in theNetBackup folder in the Preferences folder.

NetBackup status codes and messagesAbout NetBackup status codes and messages

284

■ If the problem persists, save all error information and call customer support.

NetBackup status code: 236Message: the specified client does not exist in an active policy within theconfiguration database

Explanation: A client name was not specified or the specified client does notexist.

Recommended Action: Activate the required policy, correct the client name, oradd the client to a policy that meets your needs. After you make the correction,retry the operation.

NetBackup status code: 237Message: the specified schedule does not exist in an active policy in theconfiguration database

Explanation: The specified schedule does not exist in the NetBackup configuration.

Recommended Action: Activate the required policy, correct the schedule name,or create a schedule in a policy that meets your needs. After you make thecorrection, retry the operation.

NetBackup status code: 238Message: the database contains conflicting or erroneous entries

Explanation: The catalog has an inconsistent or a corrupted entry.

Recommended Action: Obtain detailed troubleshooting information for bpdbm(on UNIX and Linux) or the NetBackup Database Manager service (on Windows)by creating a debug log directory for it. Then, retry the operation, save resultingdebug log, and call customer support.

NetBackup status code: 239Message: the specified client does not exist in the specified policy

Explanation: The specified client is not a member of the specified policy.

RecommendedAction: Correct the client name specification, specify a differentpolicy, or add the required client name to the policy. After you make the correction,retry the operation.

NetBackup status code: 240Message: no schedules of the correct type exist in this policy

285NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The appropriate schedule was not found in the specified policy. Forexample, a user backup specified a policy name but no user backup schedule existsin that policy.

Recommended Action: Specify a different policy or create a schedule of theneeded type in the policy. After you make the correction, retry the operation.

NetBackup status code: 241Message: the specified schedule is the wrong type for this request

Explanation: The specified schedule for an immediate manual backup is not fora full nor an incremental backup. It must be one of these.

Recommended Action: Specify only full or incremental schedules for manualbackups. If one does not exist in the policy, create one.

NetBackup status code: 242Message: operation would cause an illegal duplication

Explanation: If the request is processed, it causes a duplicate entry (for example,in the catalog or the configuration database). A duplicate catalog entry is usuallydue to a mistake in the specification of media IDs for NetBackup catalog backups.

Recommended Action: Check the error reports to determine the specificduplication that would occur. Correct the settings for the operation and retry it.

NetBackup status code: 243Message: the client is not in the configuration

Explanation: The specified client name was not in the catalog.

Recommended Action: Either correct the client name or add the client to thewanted policy.

NetBackup status code: 245Message: the specified policy is not of the correct client type

Explanation: A user backup specified a policy that is not the type that is requiredfor the client.

Recommended Action: Retry the operation by specifying a policy that is thecorrect type for the client. If such a policy does not exist, create one.

NetBackup status codes and messagesAbout NetBackup status codes and messages

286

NetBackup status code: 246Message: no active policies in the configuration database are of the correct clienttype

Explanation: A user backup request was not satisfied because no active policieswere the type that were required for the client.

RecommendedAction: Create or activate an appropriate policy so the user backuprequest can be satisfied.

NetBackup status code: 247Message: the specified policy is not active

Explanation: Backups for the specified policy are disabled because the policy isinactive.

Recommended Action: Activate the policy and retry the operation.

NetBackup status code: 248Message: there are no active policies in the configuration database

Explanation: No active policy was found that would satisfy the request.

Recommended Action: Activate the appropriate policy and retry the operation.

NetBackup status code: 249Message: the file list is incomplete

Explanation: While the server waited for the client to finish sending the file list,it timed out or a sequencing problem occurred.

Recommended Action: First, obtain additional information by creating debuglogs. Then try to recreate the error. The debug logs to create are as follows:

■ On the server, bptm, bpbrm, and bpdbm.

■ On UNIX, Linux, and Windows clients, bpbkar.

■ On other clients, bpcd.

To increase the amount of information that is included in the logs, see thefollowing:

See “Debug logs on PC clients” on page 118.

NetBackup status code: 250Message: the image was not created with TIR information

287NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: This error is internal and should not appear to customers.

RecommendedAction: Obtain detailed troubleshooting information by creatingdebug logs for bptm or bpdbm on the server. Then, retry the operation and checkthe resulting debug logs.

NetBackup status code: 251Message: the tir information is zero length

Explanation: For a true-image backup, the client sent no file information to themaster server. NetBackup discovered this condition when it tried to write the TIRinformation to media.

RecommendedAction: Check the policy file list and the exclude and include listson the client to verify that the client has eligible files for backup. For example,this status code can appear if the exclude list on the client excludes all files.

To obtain detailed troubleshooting information, create debug logs for bptm orbpdbm on the server. Then, retry the operation and check the resulting debug logs.

NetBackup status code: 252Message: An extended error status has been encountered, check detailed status

Explanation: If a process was unable to report the extended error status as thefinal job status, the job exits with status 252. (The extended error status has anumber greater than 255.)

Recommended Action: To determine the actual error, examine the job detailsdisplay.

NetBackup status code: 253Message: the catalog image .f file has been archived

Explanation: The catalog image .f file was archived.

Recommended Action: Refer to catalog archiving help information to restorearchived catalog image .f files.

NetBackup status code: 254Message: server name not found in the NetBackup configuration

Explanation: This error should not occur through normal use of NetBackup.

Recommended Action: Save all error information and call customer support.

NetBackup status codes and messagesAbout NetBackup status codes and messages

288

NetBackup status code: 256Message: logic error encountered

Explanation: An internal Vault error occurred.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 257Message: failed to get job data

Explanation: This error can indicate either of the following:

■ Vault failed to get job data because of a broken connection with the job manager(nbjm).

■ Vault received empty job data. This error occurs if a user-specified job ID onthe vltrun -haltdups command is out of range. (That is, the job ID is notamong the job IDs created by job manager.)

RecommendedAction: Contact customer support and send the appropriate logs.

NetBackup status code: 258Message: Vault duplication was aborted by administrator request

Explanation: The administrator initiated an abort request on the active vaultduplication job.

Recommended Action: Ensure that the abort request was intentional.

NetBackup status code: 259Message: vault configuration file not found

Explanation: This error should not occur.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 260Message: failed to send signal

Explanation: vltrun failed to send a signal to the Vault duplication job.

RecommendedAction: Contact customer support and send the appropriate logs.

NetBackup status code: 261Message: vault internal error 261

289NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: This error code should not occur.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 262Message: vault internal error 262

Explanation: This error code should not occur.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 263Message: session id assignment failed

Explanation: The unique identifier to be assigned to the Vault session is corrupt.

Recommended Action: Verify that the session ID that is stored in thesession.last file is valid.

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/session.l

ast

Windows:

install_path\Netbackup\vault\sessions\vault_name\session

.last

Make sure that the file system is not full and that no one has inadvertently editedthe session.last file. To correct the problem, store the highest session ID thatwas assigned to a session for this Vault in the session.last file. If the problempersists, contact customer support and send the appropriate logs.

NetBackup status code: 265Message: session id file is empty or corrupt

Explanation: The session ID that is stored in the following file is corrupt.

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/session.l

ast

Windows:

install_path\NetBackup\vault\sessions\vault_name\session

.last

Recommended Action: Ensure that the session ID that is stored in thesession.last file is not corrupt. Make sure that the file system is not full and

NetBackup status codes and messagesAbout NetBackup status codes and messages

290

that no one has inadvertently edited the file. To correct the problem, store thehighest session ID that was assigned to a session for this Vault in the session.lastfile. If the problem persists, contact customer support and send the appropriatelogs.

NetBackup status code: 266Message: cannot find robot, vault, or profile in the vault configuration

Explanation: NetBackup cannot find the specified profile_name or tripletrobot_name/vault_name/profile_name on the Vault command (vltrun, vlteject,vltoffsitemedia) or in vltopmenu in the Vault configuration.

Recommended Action: Rerun the command with the correct profile_name ortriplet robot_name/vault_name/profile_name.

NetBackup status code: 267Message: cannot find the local host name

Explanation: A Vault job obtains the local host name through an OS call. Thiserror occurs when the Vault job is unable to get the local host name.

RecommendedAction: Issue a hostname command at the OS command prompt.See the hostname (or gethostbyname) man page for an explanation of theconditions that would cause it to fail.

Refer to the OS System Administrator’s Guide for more information

NetBackup status code: 268Message: the vault session directory is either missing or inaccessible

Explanation: This error occurs when a Vault job cannot access the following:

UNIX and Linux: /usr/openv/netbackup/vault/sessions

Windows: install_path\NetBackup\vault\sessions

This directory is created when Vault is installed.

Recommended Action: Make sure you are running on the master server whereVault is installed and configured. Also ensure that no one accidentally removedthe sessions directory or changed permission on the directory path so it isinaccessible to the Vault job.

NetBackup status code: 269Message: no vault session id was found

291NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: This error is encountered when vltopmenu cannot find a sidxxxsession id directory for the specified profile. Either no Vault jobs were run for thisprofile or the corresponding sidxxx session id directory (or directories) wereremoved from the following directory:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name

Windows: install_path\NetBackup\vault\sessions\vault_name

Recommended Action: Either specify a different profile for the Vault jobs thatwere run or exit vltopmenu and run a Vault job for the specific profile. Then rerunvltopmenu and select the profile.

NetBackup status code: 270Message: unable to obtain process id, getpid failed

Explanation: This error occurs when a Vault process is unable to obtain its processID by means of the getpid() OS system call.

RecommendedAction: Look at the system log for any unusual system problems.Wait a while and then try running the process again when system resources arefreed up.

NetBackup status code: 271Message: vault XML version mismatch

Explanation: The Vault upgrade process failed.

Recommended Action: Enable logging, start nbvault, and then examine thenbvault logs to determine the cause of the failure. If the upgrade process failsagain, contact your customer support representative.

The following are the locations of the nbvault logs:

UNIX and Linux: /usr/openv/netbackup/logs/nbvault/

Windows: install_path\NetBackup\logs\nbvault

NetBackup status code: 272Message: execution of a vault notify script failed

Explanation: This error occurs when the Vault process is unable to run a Vaultnotify script due to permissions problems or coding problems in the script. It alsooccurs if the script returns an error.

NetBackup status codes and messagesAbout NetBackup status codes and messages

292

Recommended Action: Ensure that the notify script is executable and runswithout errors. You must debug the script by running it manually to eliminatecoding errors.

NetBackup status code: 273Message: invalid job id

Explanation: This error can occur in either of the following situations:

■ The specified job is not an active Vault job

■ The specified active Vault job is not at the duplication step

RecommendedAction: Specify the job ID of the active Vault job that is currentlyat the duplication step or operation.

NetBackup status code: 274Message: no profile was specified

Explanation: This error should not occur.

RecommendedAction: Contact customer support and send the appropriate logs.

NetBackup status code: 275Message: a session is already running for this vault

Explanation: This error occurs when you start a session for a vault and anothersession is already running for this vault. Only one session is allowed for a vaultat any given time.

Recommended Action: Start the Vault session after the previous session hascompleted.

NetBackup status code: 276Message: invalid session id

Explanation: This error should not occur.

RecommendedAction: Contact customer support and send the appropriate logs.

NetBackup status code: 277Message: unable to print reports

Explanation: This error should not occur.

RecommendedAction: Contact customer support and send the appropriate logs.

293NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 278Message: unable to collect pre eject information from the API

Explanation: This error occurs when robotic information cannot be retrievedbefore ejection.

Recommended Action: Ensure that all Media and Device Management daemonsare running or the robot is live and up.

NetBackup status code: 279Message: eject process is complete

Explanation: This error occurs when the eject process is completed successfully.

Recommended Action: None.

NetBackup status code: 280Message: there are no volumes to eject

Explanation: This error occurs when media to be ejected are not in the library.

RecommendedAction: Ensure that the media to be ejected are not removed fromthe library manually.

NetBackup status code: 281Message: vault core error

Explanation: An internal Vault error occurred.

RecommendedAction: Contact customer support and send the appropriate logs.

NetBackup status code: 282Message: cannot connect to nbvault server

Explanation: The vault job cannot connect to the NetBackup Vault Managerservice (nbvault on UNIX and Linux, nbvault.exe on Windows).

Possible causes are the following:

■ The Symantec Private Branch Exchange service (VRTSpbx) or NetBackupRequest Manager (bprd) is down.

■ The NetBackup Vault Manager service is down, possibly because of thefollowing: the Vault is not licensed, the vault.xml configuration file is corrupt,or the vault.xml configuration file upgrade failed during an upgradeinstallation.

NetBackup status codes and messagesAbout NetBackup status codes and messages

294

RecommendedAction: To determine the reason for failure, examine the logs forthe service or services that are down and the operating system logs (EventLog onWindows). Restart the service or services that are down after resolving theproblem.

The following are the locations of the nbvault logs:

UNIX and Linux: /usr/openv/netbackup/logs/nbvault/

Windows: install_path\NetBackup\logs\nbvault

NetBackup status code: 283Message: error(s) occurred during vault report generation

Explanation: Vault encountered errors during the report generation phase.

Recommended Action: Check logs for details of the failure.

NetBackup status code: 284Message: error(s) occurred during vault report distribution

Explanation: Vault encountered errors during the report distribution phase.Potential reasons include the following:

■ Reports were not emailed (possibly because of malformed email addresses inthe vault.xml file).

■ On Windows, the third-party mail client (such as blat) is not configuredproperly.

■ The reports destination directory is not present or it does not have appropriatepermissions.

■ The printer is not set up correctly or the printer command in vault.xml isincorrect.

Recommended Action: Check logs for details of the failure.

NetBackup status code: 285Message: unable to locate vault directory

Explanation: A Vault job or a command for a missing or a corrupt directory ofthe session in question returns this error.

Recommended Action: The Vault directory is created when the Vault packageis installed on the master server. Ensure that the Vault job or command is startedas root on the master server. Ensure that the Vault directory was not removedinadvertently or made inaccessible to the root user.

295NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 286Message: vault internal error

Explanation: This error should never occur.

RecommendedAction: Contact customer support and send the appropriate logs.

NetBackup status code: 287Message: vault eject failed

Explanation: This error occurs when Vault fails to eject any of the media thatwas identified for eject during a Vault Session. Potential reasons: Media and DeviceManagement services are down, the robot is down, or no empty slots are availablein the media access port (MAP).

Recommended Action: Ensure that the Media and Device Management servicesare running, the robot is up, and empty slots are available in the media accessport (MAP).

NetBackup status code: 288Message: vault eject partially succeeded

Explanation: This error occurs when not all of the media that was identified foreject during a Vault session can be ejected.

Potential reasons include the following:

■ Some of the media is in use by NetBackup

■ Some of the media are in a drive

■ Not enough empty slots are available in the media access port (MAP)

Recommended Action: Ensure that the media are not loaded in a drive and inuse by other processes. Ensure that empty slots are available in the media accessport (MAP).

NetBackup status code: 289Message: cannot consolidate reports of sessions from container and slot-basedvaults

Explanation: This error occurs when you consolidate reports and at least onesession uses slots and another uses containers.

Recommended Action: Change the report consolidation so that only reports forone type of vault operation are consolidated, either slots or containers.

NetBackup status codes and messagesAbout NetBackup status codes and messages

296

NetBackup status code: 290Message: one or more errors detected during eject processing

Explanation: This error occurs when more than one error is encountered duringan eject procedure by vltopmenu. Any "eject" errors that range from 291 to 300may have occurred in any of the sessions being ejected.

Recommended Action: For detailed information, review the Vault debug log inthe following directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

After the problem is identified and corrected, the media that were not ejected mayneed to be ejected manually by means of vlteject or vltopmenu.

This error often indicates that the media were left in the off-site Vault volumegroup but physically reside in the robot or the robotic MAP.

To solve this problem, do one of the following:

■ Manually remove any media that are in the off-site Vault volume group butare still in the robotic library.

■ Inventory the robotic library. An inventory puts any media that were in theoff-site Vault volume group back into the robotic volume group. Then rerunthe Vault sessions that failed.

NetBackup status code: 291Message: number of media has exceeded capacity of MAP; must perform manualeject using vltopmenu or vlteject

Explanation: This error occurs in the following situation: a Vault job is run for aprofile that selected automatic eject mode and the number of media to be ejectedexceeds the MAP capacity.

RecommendedAction: Usevltopmenu to manually eject the media for the selectedprofile and session ID. The vltopmenu option lets you eject the selected media, aMAP-full (or less) at a time.

297NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 292Message: eject process failed to start

Explanation: This error occurs when the following cannot start the eject process:the Vault job, the vlteject command, or the use of the vltopmenu.

Recommended Action: For detailed information about the problem, review theVault debug log in the following directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

Use the robtest utility to ensure that you can communicate with the Vault roboticlibrary. After the problem is resolved, rerun the Vault session, vlteject command,or vltopmenu command.

NetBackup status code: 293Message: eject process has been aborted

Explanation: This error occurs when the eject process is canceled. This error canbe encountered during a Vault job or with the vlteject or the vltopmenu ejectcommand.

This error can occur because of one of the following conditions:

■ Could not open a pipe to vmchange -verify_eject call.

■ Unexpected output from vmchange -verify_eject call.

■ No MAP elements exist to eject media into.

■ The robotic library had problems putting media into the MAP.

■ The user pressed Return in interactive mode and did not first remove the mediafrom the MAP. In this case, the media that were in the MAP are put back intotheir original slots in the robotic library.

Recommended Action: For detailed information about why the process wascanceled, review the Vault debug log in the following directory:

NetBackup status codes and messagesAbout NetBackup status codes and messages

298

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

This error often indicates that the media were left in the off-site Vault volumegroup but physically reside in the robot or the robotic MAP.

To solve this problem, do one of the following:

■ Manually remove any media that are in the off-site Vault volume group butare still in the robotic library.

■ Inventory the robotic library. An inventory puts any media that were in theoff-site Vault volume group back into the robotic volume group. Then, rerunthe Vault sessions that failed.

NetBackup status code: 294Message: vault catalog backup failed

Explanation: During a Vault job, the catalog backup step failed.

RecommendedAction: Review the Vault debug log in the following directory fordetailed information about why the process failed:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

To find the actual problem that caused the catalog backup (bpbackupdb) to fail,review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

Correct the problem and rerun the Vault job.

299NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 295Message: eject process could not obtain information about the robot

Explanation: This error occurs when the eject process cannot collect informationabout the robotic library and its associated MAPs and volumes.

Recommended Action: For detailed information about why the process fails,review the Vault debug log in the following directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

Correct the error and rerun the Vault session, vlteject command, or vltopmenueject command.

NetBackup status code: 296Message: process called but nothing to do

Explanation: This error occurs in the following situations:

■ vlteject is called with -eject but the system has no tapes to eject

■ vlteject is called with -eject and the eject is already done

■ vlteject is called with -report and the reports are already done

■ vlteject is called with -eject and -report, and both the eject and the reportsare done

RecommendedAction: This error is an informative one and does not require anyaction.

NetBackup status code: 297Message: all volumes are not available to eject

Explanation: This error occurs when an try is made to eject a non-existent or badmedia ID during the eject phase of the following: a Vault session, a vlteject

command, or a vltopmenu command.

NetBackup status codes and messagesAbout NetBackup status codes and messages

300

Possible reasons for this error are as follows:

■ The bad media ID was added by means of the vlt_ejectlist_notify script.

■ The bad media ID is already in the MAP or not in the robotic library.

■ The bad media ID is in a robotic drive.

■ The bad media ID is in transit in the robotic library.

Recommended Action: Remove or correct the defective media ID from thevlt_ejectlist_notify script and rerun the Vault session. If the bad media ID isin the MAP or a drive or in transit, something is misconfigured.

NetBackup status code: 298Message: the library is not ready to eject volumes

Explanation: This error occurs if the robotic library is not in a state to supportejecting media.

Possible reasons for this error include the following:

■ Currently, the library ejects media

■ The library waits to eject media

■ Currently, the library injects media

■ The library waits to inject media

RecommendedAction: Wait until the robotic library can support the eject actionand rerun the Vault session, vlteject command, or vltopmenu command.

NetBackup status code: 299Message: there is no available MAP for ejecting

Explanation: The robotic library you vault from does not have a MAP availablefor use and so media cannot be ejected.

Recommended Action: Wait until the robotic library’s MAP is available for useand rerun the Vault session, vlteject command, or vltopmenu command.

NetBackup status code: 300Message: vmchange eject verify not responding

Explanation: During the eject process, the vmchange command is called with a"-verify_eject" call until all of the volumes for the request are in the MAP. Thiscommand call failed. Or it did not return the proper information to the Vault ejectprocess.

301NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Do the following, as appropriate:

■ Review the Vault debug log in the following directory for detailed informationabout why the process failed:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

■ Also review the summary.log in each of the sidxxx directories that hadproblems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)This error often indicates that the media were left in the off-site Vault volumegroup but physically reside in the robot or the robotic MAP. To solve thisproblem, do one of the following:

■ Manually remove any media that are in the off-site Vault volume group butare still in the robot.

■ Inventory the robot. An inventory puts any media that were in the off-siteVault volume group back into the robotic volume group. Then, rerun the Vaultsessions that failed.

NetBackup status code: 301Message: vmchange api_eject command failed

Explanation: During the eject process, the vmchange command is called with an"-api_eject" call to begin the process to eject media. This command call failed.

RecommendedAction: Review the Vault debug log in the following directory fordetailed information about why the process failed:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

NetBackup status codes and messagesAbout NetBackup status codes and messages

302

(where xxx is the session ID)

When the problem is resolved, rerun the Vault session, vlteject command, orvltopmenu command.

NetBackup status code: 302Message: error encountered trying backup of catalog (multiple tape catalogbackup)

Explanation: This error occurs when the NetBackup command that was used forstage one of the two-stage catalog backup fails.

Recommended Action: For the actual error that caused the failure, review theVault debug log in the following directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

In addition, review the admin debug log in the following directory:

UNIX and Linux: /usr/openv/netbackup/logs/admin

Windows: install_path\NetBackup\logs\admin

Correct the error and rerun the Vault session.

NetBackup status code: 303Message: error encountered executing Media Manager command

Explanation: This error occurs when a Media and Device Management commandfails during a Vault job.

Recommended Action: For the actual error that caused the command to fail,review the Vault debug log in the following directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

303NetBackup status codes and messagesAbout NetBackup status codes and messages

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/vault_name/sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where xxx is the session ID)

Try running the command (with the same arguments as in the log file) to see theactual error. Ensure that the Media and Device Management daemons are running.Also ensure that the robot is functional and you can communicate with it (forexample, inventory the robot through the GUI).

NetBackup status code: 304Message: specified profile not found

Explanation: This error occurs when the profile name that is specified on theVault command is not defined in the Vault configuration.

Recommended Action: Rerun the Vault command with a profile name that isdefined in the Vault configuration.

NetBackup status code: 305Message: multiple profiles exist

Explanation: This error may occur when duplicate profile names are defined inmultiple Vault configurations and only the profile name is specified on the Vaultcommand.

Recommended Action: Rerun the Vault command with the tripletrobot_name/vault_name/profile_name. The triplet uniquely identifies the profilein your Vault configuration.

NetBackup status code: 306Message: vault duplication partially succeeded

Explanation: This error occurs when all selected images are not duplicatedsuccessfully.

Recommended Action: Check the Vault and induplicate logs for cause of thefailure.

NetBackup status code: 307Message: eject process has already been run for the requested Vault session

NetBackup status codes and messagesAbout NetBackup status codes and messages

304

Explanation: This error occurs when vlteject is run to eject media for a sessionID for which media has already been ejected.

Recommended Action: Rerun vlteject for another session ID for which mediahas not been ejected.

NetBackup status code: 308Message: no images duplicated

Explanation: This error occurs when Vault failed to duplicate any images.

Recommended Action: For more information, review the Vault debug log in thefollowing directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

Also review the summary.log in each of the sidxxx directories that had problems:

UNIX and Linux:

/usr/openv/netbackup/vault/sessions/<vault_name/>sidxxx

Windows:

install_path\NetBackup\vault\sessions\vault_name\sidxxx

(where vault_name is the name of the vault, and xxx is the session ID)

Look for the log entry that gives the total number of images processed. A commoncause of failure is a lack of resources, such as no more media available in thespecified pools for duplication. Correct the problem and rerun the Vault job. Notethat the NetBackup scheduler retries a Vault job that terminates with this error.Review the admin debug log for induplicate entries and the bptm debug log.

NetBackup status code: 309Message: report requested without eject being run

Explanation: This error occurs when a report is run that requires media to havebeen ejected first.

Recommended Action: Perform one of these actions:

■ Rerun vlteject or vltopmenu to eject the media for the session before yougenerate the reports.

■ Reconfigure the profile to allow the eject step to be performed when the nextVault session for this profile runs.

■ Disable the report generation in the profile for the reports that require mediato be ejected.

305NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 310Message: Updating of Media Manager database failed

Explanation: This error occurs when Vault physically ejects tapes but fails toupdate the EMM database to reflect the eject operation. A typical reason for thisfailure is that EMM detected a mismatch between the media type and its volumegroup.

RecommendedAction: To find the root cause of the error, review the Vault debuglogs in the following directory:

UNIX and Linux: /usr/openv/netbackup/logs/vault

Windows: install_path\NetBackup\logs\vault

To fix the issue may involve making configuration changes.

NetBackup status code: 311Message: Iron Mountain Report is already created for this session

Explanation: This error occurs when an Iron Mountain report has already beengenerated for the session.

Recommended Action: None. This report cannot be generated again.

NetBackup status code: 312Message: invalid container database entry

Explanation: NetBackup Vault has found an invalid entry while reading thecontainer database. Each container entry in the container database must followthe expected format. The container database exists in file cntrDB, which is locatedat install_path/netbackup/vault/sessions/cntrDB.

RecommendedAction: To get the line number of an invalid record in the containerdatabase, read the log file under the directory netbackup/logs/vault. Be awarethat a Vault log may not exist unless the directory netbackup/logs/vault existedbefore the error occurred. Open the container database file cntrDB and correctthat invalid entry. Note that this error occurs every time Vault reads this entryin cntrDB until either this invalid entry is deleted or it is corrected.

NetBackup status code: 313Message: container does not exist in container database

Explanation: The specified container does not have an entry in the containerdatabase. The container database exists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

NetBackup status codes and messagesAbout NetBackup status codes and messages

306

Recommended Action: Verify that you put some media into this container byusing the vltcontainers command. Verify that you did not delete it by using thevltcontainers -delete command.

NetBackup status code: 314Message: container database truncate operation failed

Explanation: An error occurs while truncating the container database. This errormay occur during the modification or deletion of an entry from the containerdatabase. The container database exists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

RecommendedAction: See the log file under the directorynetbackup/logs/vaultfor more details. Be aware that a log file is not created unless thenetbackup/logs/vault directory has already been created.

NetBackup status code: 315Message: failed appending to container database

Explanation: This error can occur while appending a container record to thecontainer database. This error may occur with the addition, modification, ordeletion of an entry from the container database. The container database existsin file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Read the relevant log file under the directoryinstall_path/netbackup/logs/vault for more details. Be aware that if thisdirectory does not already exist, a log file is not created.

NetBackup status code: 316Message: container_id is not unique in container database

Explanation: NetBackup Vault has found a previously-existing entry for thiscontainer ID in the container database while adding it to the container database.Each container record in the container database must have a unique containerID. Note that the container database exists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Verify that you have specified the correct container ID.

NetBackup status code: 317Message: container database close operation failed

307NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: This error occurs while closing the container database. This errormay occur during the reading, addition, modification, or deletion of an entry fromthe container database. Note that the container database exists in file cntrDB,which is located at install_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Read the relevant log file under the directorynetbackup/logs/vault for more details. Be aware that if this directory does notalready exist, a log file is not created.

NetBackup status code: 318Message: container database lock operation failed

Explanation: This error occurs while locking the container database. This errormay occur during the addition, modification, or deletion of an entry from thecontainer database. Note that the container database exists in file cntrDB, whichis located at install_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Read the relevant log file under the directorynetbackup/logs/vault for more details. Be aware that if this directory does notalready exist, a log file not created.

If some other Vault operation uses the container database and locks it, wait untilthat operation completes and the container database is unlocked.

NetBackup status code: 319Message: container database open operation failed

Explanation: This error occurs while opening the container database. This errormay occur during the reading, addition, modification, or deletion of an entry fromthe container database. Note that the container database exists in file cntrDB,which is located at install_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Read the relevant log file under the directorynetbackup/logs/vault for more details. Be aware that if this directory does notalready exist, a log file is not created.

NetBackup status code: 320Message: the specified container is not empty

Explanation: This error occurs if you try to delete a container from the containerdatabase, but the container still holds media. You can only delete empty containers.

Recommended Action: Verify that you have specified the correct container ID.

If you still want to delete this container from the container database, first emptyit by doing either of the following:

NetBackup status codes and messagesAbout NetBackup status codes and messages

308

■ Inject all the media it contains into a robot

■ Clear the Vault container ID fields for these media from the EMM database byusing vmchange -vltcid with a value of - .

Try to delete the container again.

NetBackup status code: 321Message: container cannot hold any media from the specified robot

Explanation: This error occurs while trying to place media from an unexpectedEMM database host into a container. All the media that are placed in a containershould belong to the same EMM database host. For example, you have media froma robot that belongs to one EMM database host. Then you try to put this mediainto a container that already holds media from the robots that belong to a differentEMM database host.

Recommended Action: Verify that you specified the correct container ID andmedia IDs. Read the relevant log file under the directoryinstall_path/netbackup/logs/vault for more details. Be aware that if thisdirectory does not already exist, a log file is not created.

NetBackup status code: 322Message: cannot find vault in vault configuration file

Explanation: NetBackup Vault cannot find an entry for the specified Vault nameinto the Vault configuration file. Note that the Vault configuration file is locatedat install_path/netbackup/db/vault/vault.xml.

Recommended Action: Verify that you specified the correct Vault name. Readthe relevant log file under the directory netbackup/logs/vault for more details.Be aware that if this directory does not already exist, a log file is not created.

NetBackup status code: 323Message: cannot find robot in vault configuration file

Explanation: NetBackup Vault cannot find an entry for the specified robot numberin the Vault configuration file. Note that the Vault configuration file is located atinstall_path/netbackup/db/vault/vault.xml.

RecommendedAction: Verify that you specified the correct robot number. Readthe relevant log file under the directory netbackup/logs/vault for more details.Be aware that if this directory does not already exist, a log file is not created.

309NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 324Message: invalid data found in retention map file for duplication

Explanation: This error occurs when the retention mapping file (either genericor for a specific vault) contains invalid data. If the file contains too much or toolittle data or the user defines invalid retention levels in the file, this error occurs.

The retention mapping file is used as follows: in a Vault session when a Vaultprofile duplication is configured with the Use mappings retention level configuredfor one of the copies for duplication. The product installs a mapping file templatenamed retention_mappings in install_path/netbackup/db/vault.

To specify a mappings file for any single vault, copy the retention_mappingstemplate to another file and append the name of the vault. For example,netbackup/db/vault/retention_mappings.V1

Recommended Action: Check the entries in the retention_mappings file.

NetBackup status code: 325Message: unable to find policy/schedule for image using retention mapping

Explanation: This error occurs with duplication of the backup policy or theschedule of an image by Vault. The Use mappings option on the Duplication tabof the Profile dialog box is selected, but the policy or the schedule no longer exists.

Recommended Action: Verify whether or not the backup policy or the schedulethat created the image still exists. If either one or both do not exist, the image isnot duplicated through the Vault profile.

NetBackup status code: 326Message: specified file contains no valid entry

Explanation: The specified file contains no valid entries for media IDs or thealphanumeric equivalent of bar codes. As per the expected format, each line shouldcontain only one string that represents either a media ID or the bar code numericequivalent.

RecommendedAction: Verify that each entry in the specified file does not exceedthe string size limit: six characters for media IDs and 16 characters for the numericequivalent of bar codes. Correct the invalid entries in the specified file and trythe same operation again. Read the relevant log file under the directoryinstall_path/netbackup/logs/vault for more details. Be aware that if thisdirectory does not already exist, a log file is not created.

NetBackup status codes and messagesAbout NetBackup status codes and messages

310

NetBackup status code: 327Message: no media ejected for the specified vault session

Explanation: This error occurs while moving media ejected by the specified Vaultsession to a container. Either the specified Vault session has not ejected any media,or you specified an incorrect Vault name or session ID.

Recommended Action: Verify that you have specified the correct combinationof Vault name and session ID. Verify that the specified Vault session has ejectedat least one piece of media. Read the relevant log file under the directorynetbackup/logs/vault for more details. Be aware that if this directory does notalready exist, a log file is not created.

NetBackup status code: 328Message: invalid container id

Explanation: This error occurs while adding a container record to the containerdatabase. The container ID is found invalid. Note that the container databaseexists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Verify that the container ID does not contain any spacecharacters, and that the string size is a maximum of 29 characters long.

NetBackup status code: 329Message: invalid recall status

Explanation: This error occurs while adding a container record to the containerdatabase. The container recall status is found invalid. Note that the containerdatabase exists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

Recommended Action: Verify that the recall status is either 1 or 0.

NetBackup status code: 330Message: invalid database host

Explanation: This error occurs while adding a container record to the containerdatabase. The EMM database host name is found invalid. Note that the containerdatabase exists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

RecommendedAction: Verify that the EMM database host name does not containany space characters, and that the string size is a maximum of 256 characterslong.

311NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 331Message: invalid container description

Explanation: This error occurs while adding a container record to the containerdatabase. The container description is found invalid. Note that the containerdatabase exists in file cntrDB, which is located atinstall_path/netbackup/vault/sessions/cntrDB.

RecommendedAction: Verify that the string size of the container description isa maximum of 25 characters long.

NetBackup status code: 332Message: error getting information from EMM database

Explanation: This error can occur while the backup process communicates withthe EMM database to retrieve some information.

Recommended Action: Do the following, as appropriate:

■ On UNIX and Linux, verify that the NetBackup Volume Manager (vmd) isrunning. On Windows, verify that the NetBackup Volume Manager service isrunning.

■ See the process-specific error log directory for more details.

UNIX and Linux: /usr/openv/netbackup/logs/process_name

Windows: install_path\NetBackup\logs\process_name

For example, if you get this error while running a Vault command (such asvltcontainers or vltopmenu), look at the following logs to learn why:/usr/openv/netbackup/logs/vault

Note: The log file cannot be created unless the appropriate log directory suchas /usr/openv/netbackup/logs/vault is already created.

NetBackup status code: 333Message: error getting information from media manager command line

Explanation: This error occurs when Vault cannot retrieve robot informationsuch as map information, volume information, library status, and so on. It is aninternal error.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status codes and messagesAbout NetBackup status codes and messages

312

NetBackup status code: 334Message: unable to receive response from robot; robot not ready

Explanation: This error occurs when a problem exists with the robot.

Recommended Action: Ensure that all Media and Device Management daemonsare running or the robot is live and up.

NetBackup status code: 335Message: failure occurred while suspending media for eject

Explanation: This error occurs when Vault cannot suspend the media. It is aninternal error.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 336Message: failure occurred while updating session information

Explanation: Vault cannot update the session files. It is an internal error.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 337Message: failure occurred while updating the eject.mstr file

Explanation: Vault cannot update the eject list file. It is an internal error.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 338Message: vault eject timed out

Explanation: This error occurs when a problem exists with the robot.

Recommended Action: Do the following, as appropriate:

■ Remove the media from the MAP if it is already full.

■ Make sure that the MAP is closed properly.

NetBackup status code: 339Message: vault configuration file format error

313NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The Vault configuration file is malformed. Unless the file has beenmanually modified, this error is internal. Note that the Vault configuration fileis located at install_path/netbackup/db/vault/vault.xml.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 340Message: vault configuration tag not found

Explanation: An optional attribute may not appear in the Vault configurationfile. This internal error generally does not cause problems in Vault's operation.Note that the Vault configuration file is located atinstall_path/netbackup/db/vault/vault.xml.

RecommendedAction: If Vault's operation is affected, contact customer supportand send appropriate logs.

NetBackup status code: 341Message: vault configuration serialization failed

Explanation: Vault failed to write out the Vault configuration file. It is an internalerror. Note that the Vault configuration file is located atinstall_path/netbackup/db/vault/vault.xml.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 342Message: cannot modify - stale view

Explanation: This error can occur if an administration interface (NetBackupAdministration Console or Vault Administration menu user interface) tries tomodify the following:

■ A robot or vault or profile in between the read

■ Operations of the same robot or vault

■ Profile by another instance of an administration interface

RecommendedAction: Check the latest attributes of the robot or vault or profile.To check, refresh the view in the NetBackup Administration Console or retrievethe attributes in the Vault Administration menu user interface again. Then retrythe operation.

NetBackup status codes and messagesAbout NetBackup status codes and messages

314

NetBackup status code: 343Message: robot already exists

Explanation: This error can occur during addition of a robot while a robot withthe same name already exists.

RecommendedAction: Refresh the view in the NetBackup Administration Consoleor retrieve the attributes in the Vault Administration menu user interface againto see the robot.

NetBackup status code: 344Message: vault already exists

Explanation: This error can occur during addition of a vault if a vault with thesame name already exists in the same robot.

Recommended Action: Choose a different name for the vault.

NetBackup status code: 345Message: profile already exists

Explanation: This error can occur during addition of a profile if a profile withthe same name already exists within the same vault.

Recommended Action: Choose a different name for the profile.

NetBackup status code: 346Message: duplicate MAP

Explanation: A duplicate MAP was added in the Vault configuration file. It is aninternal error.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 347Message: vault configuration cache not initialized

Explanation: This error should never occur.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 348Message: specified report does not exist

315NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: An invalid Vault report was requested for generation. It is an internalerror.

Recommended Action: Contact customer support and send appropriate logs.

NetBackup status code: 349Message: incorrect catalog backup policy

Explanation: This error can occur when a Vault session tries to run a catalogbackup. The specified policy for the catalog backup in the Vault profile is eitherblank or is not of type NBU-Catalog.

Recommended Action: Verify that you specified a catalog backup policy for thecatalog backup in the Vault profile and that the policy is of type NBU-Catalog.

NetBackup status code: 350Message: incorrect vault catalog backup schedule

Explanation: This error can occur when a Vault session tries to run a catalogbackup. The specified Vault catalog backup schedule for catalog backup in theVault profile is either blank or is not of type Vault Catalog Backup.

RecommendedAction: Verify that you specified a Vault Catalog Backup schedulefor the catalog backup in the Vault profile. Also verify that the schedule is of typeVault Catalog Backup.

NetBackup status code: 351Message: all configured vault steps failed

Explanation: This error occurs when multiple Vault steps are configured for asession and all of them fail.

RecommendedAction: For duplication and catalog backup steps, use the ActivityMonitor to check the status of the respective jobs that Vault started. For Ejectstep status, check the Detailed Status tab of the Job Details dialog box for theVault job.

NetBackup status code: 400Message: Server Group Type is Invalid

Explanation: The creation of a server group fails because the server group typeis invalid.

Recommended Action: Do the following, as appropriate:

NetBackup status codes and messagesAbout NetBackup status codes and messages

316

■ Select a valid server group type: MediaSharing, Symantec OpsCenter, orAltServerRestore.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator ID 111), which usesunified logging.

NetBackup status code: 401Message: Server Group Already Exists

Explanation: The attempt to create a server group failed. The server group alreadyexists.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified server group name is not in use.

■ Create the server group by specifying a name that is not currently in use.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator ID 111), which usesunified logging.

NetBackup status code: 402Message: Server Group Already Exists with a different type

Explanation: The attempt to create a server group failed. The server group nameis already in use by a server group with a different group type.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified server group name is not in use.

■ Try to create the server group by specifying a name that is not currently inuse.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator ID 111), which usesunified logging.

NetBackup status code: 403Message: Server Group Active State is not valid

Explanation: The attempt to create a server group failed. The server group statewas invalid.

317NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Do the following, as appropriate:

■ Valid server group states are: ACTIVE and INACTIVE

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator ID 111), which usesunified logging.

NetBackup status code: 404Message: Server Group does not exist

Explanation: An operation was tried by using a server group that does not exist.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified media is correct.

■ Verify the media ownership.

■ Verify that the server group exists.

■ Verify that the server where the operation is performed is a member of theowning server group. If not, try the operation from a server that is a memberof the server group.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator IDs 111 and 143),which uses unified logging.

NetBackup status code: 405Message: Member’s server type not compatible with Server Group

Explanation: The attempt to add or update a server group failed. A member’sserver type was not valid for the specified server group type.

Recommended Action: Do the following, as appropriate:

■ The Media Sharing server group can contain the following types of servers:Master, Media, NDMP, and cluster.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator IDs 111 and 143),which uses unified logging.

NetBackup status codes and messagesAbout NetBackup status codes and messages

318

NetBackup status code: 406Message: The computer specified is not a member of the server group specified

Explanation: A server that is not a member of the server group that owns themedia performed an operation on a media.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified media is correct.

■ Verify the media ownership

■ Verify that the server where the operation is performed is a member of theowning server group. If not, try the operation from a server that is a memberof the server group.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator IDs 111 and 143),which use unified logging.

NetBackup status code: 407Message: Member’s NetBackup version not compatible with Server Group

Explanation: The attempt to add or update a server group failed. One of the servergroup member’s NetBackup version is not valid for the specified server grouptype.

Recommended Action: Do the following, as appropriate:

■ Ensure that each member server has NetBackup 6.5 or later.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator IDs 111 and 143),which uses unified logging.

NetBackup status code: 408Message: Server Group is in use

Explanation: The attempt to delete a server group that failed because the servergroup owns one or more media.

Recommended Action: Do the following, as appropriate:

■ Ensure that the server group is not the owner of any media by runningbpmedialist -owner group_name from the master server.

319NetBackup status codes and messagesAbout NetBackup status codes and messages

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator IDs 111 and 143),which uses unified logging.

NetBackup status code: 409Message: Member already exists in server group

Explanation: The attempt to add or update a server group failed because one ofthe server group members is the same as the one being added.

Recommended Action: Do the following, as appropriate:

■ Ensure that the server group member that you add does not already exist inthe group.

■ For detailed troubleshooting information, create the admin debug log directoryand retry the operation. Check the resulting debug logs. Additional debuginformation can be found in the log for nbemm (originator IDs 111 and 143),which uses unified logging.

NetBackup status code: 501Message: You are not authorized to use this application.

Explanation: The user is not authorized to use one of the NetBackup JavaAdministration utilities on the host that is specified in the login dialog box.

Recommended Action: Check the auth.conf file on the host that is specified inthe NetBackup-Java login dialog box for the proper authorization. If the auth.conffile does not exist, it must be created with the proper entry for this user name.More details on the auth.conf file are available.

See NetBackup Administrator's Guide, Volume I.

NetBackup status code: 502Message: No authorization entry exists in the auth.conf file for user nameusername. None of the NB-Java applications are available to you.

Explanation: The user name is not authorized to use any NetBackup-Javaapplications on the host that is specified in the logon dialog box.

Recommended Action: Check the auth.conf file on the computer (host name)specified in the NetBackup-Java logon dialog box for the proper authorization. Ifthe file does not exist, create it with the proper entry for this user name. Moredetails on the auth.conf file are available.

NetBackup status codes and messagesAbout NetBackup status codes and messages

320

See NetBackup Administrator's Guide, Volume I.

NetBackup status code: 503Message: Invalid username.

Explanation: For UNIX and Linux host logon, the NetBackup Java applicationserver on the host where the logon is requested does not recognize the user name.

For Windows host logon, the NetBackup-Java authentication service on the hostwhere the logon is requested does not have sufficient privileges to grant therequest.

Recommended Action: Do the following, as appropriate:

■ For UNIX and Linux hosts: the user name must be a valid user name in thepasswd file on the host that is specified in the logon dialog box.

■ For Windows hosts: refer to the LogonUser function in the section titledClient/Server Access Control Functions of the Windows Platform SoftwareDeveloper’s Kit to determine the required privileges.

NetBackup status code: 504Message: Incorrect password.

Explanation: For logon to a UNIX or Linux host, the user name is recognized onthe host where the logon is requested, but the supplied password is incorrect.

For logon to a Windows host, the attempt to log in the user failed. The failure canbe due to an unrecognized user in the specified domain.

Recommended Action: Do the following, as appropriate:

■ Enter the correct password.

■ On Windows hosts: The exact error can be found in the bpjava-msvc log file.

For more details, refer to the LogonUser function in the section Client/ServerAccess Control Functions of the Windows Platform Software Developer’s Kit.

NetBackup status code: 505Message: Can not connect to the NB-Java authentication service on host on theconfigured port - (port_number). Check the log file for more details.

Explanation: The initial connection from the NetBackup-Java interface to itsauthentication service on (host) was on the configured_port_number that wasmentioned in the error message. Either the port is in use by another applicationor the NetBackup-Java interface and its application server are not configured with

321NetBackup status codes and messagesAbout NetBackup status codes and messages

the same port. The default port is 13722. The NetBackup Administration Consolelog file should contain more detail about this error.

Recommended Action: Do the following, as appropriate:

■ On UNIX and Linux, compare the bpjava-msvc entry in the /etc/services

file with the BPJAVA_PORT entry in the /usr/openv/java/nbj.conf file

On Windows, compare the bpjava-msvc entry in the%systemroot%\system32\drivers\etc\services file with theinstall_path\java\setconf.bat file (Windows). The entries must match.

■ Ensure that no other application uses the port that is configured for theNetBackup-Java interface.

NetBackup status code: 506Message: Cannot connect to the NB-Java user service onhoston portport_number.If successfully logged in before, retry your last operation. Check the log file formore details.

Explanation: After the NetBackup-Java authentication service validates the username, a NetBackup-Java user service is used for all other service requests fromthe NetBackup-Java interface. Communication was tried between theNetBackup-Java interface and the user service on host (host) on the port numberthat was specified in the error message. More information about various portconfiguration options is available.

See NetBackup Administrator's Guide, Volume I.

The NetBackup Administration Console log file should contain more detail aboutthis error.

■ On UNIX and Linux: the port configuration options are specified in the/usr/openv/netbackup/bp.conf file or through Administration Console HostProperties.

■ On Windows: from the NetBackup Administration Console, select HostProperties. Select Properties on the Actions menu. The Port Ranges tabcontains the port options.

Recommended Action: Do the following, as appropriate:

■ Restart the NetBackup-Java interface and log in again.

■ If the problem persists, enable detailed debug logging.

■ Restart the NetBackup-Java interface and examine the logs.

NetBackup status codes and messagesAbout NetBackup status codes and messages

322

NetBackup status code: 507Message: Socket connection to the NB-Java user service has been broken. Retryyour last operation. Check the log file for more details.

Explanation: The connection was broken to the NetBackup Java application serverthat is running on the NetBackup host (where you are logged in). The NetBackupAdministration Console log file should contain more detail about this error.

Recommended Action: Do the following, as appropriate:

■ Retry the last operation.

■ If the problem persists, restart the NetBackup-Java interface and try again.

■ If the problem still persists, enable detailed debug logging.See “Enabling detailed debug logging” on page 127.

■ Restart the NetBackup-Java interface and examine the logs.

Note: You may have network or system problems unrelated to NetBackup.

NetBackup status code: 508Message: Can not write file.

Explanation: This cause of this error is one of the following:

■ The NetBackup-Java user service tries to write to a file that does not have writepermissions. The solution is to enable write privileges.

■ The NetBackup-Java user service tries to write to a temporary file whose uniquename cannot be constructed. This condition is unlikely, but can result froman exhaustion of system resources (from the filling of the name space).

Recommended Action: Retrieve the specific details from the user service logfiles.

Enable detailed debug logging as explained in the following topic:

See “Enabling detailed debug logging” on page 127.

NetBackup status code: 509Message: Can not execute program.

Explanation: The NetBackup-Java authentication or user service reported anerror that relates to the creation (or demise) of a child job process. TheNetBackup-Java service programs create separate jobs to accomplish specifictasks, as follows. The NetBackup-Java authentication service creates the

323NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup-Java user service. When it is created and connected to, theNetBackup-Java user service creates all other child processes on behalf of requestsfrom the NetBackup-Java interface.

The cause of status code 509 can be found in the appropriate log file, either forbpjava-msvc, bpjava-susvc, or bpjava-usvc.

The cause can be categorized as one of the following:

■ A job (started by either the NetBackup-Java authentication service or userservice) no longer exists and did not report its result status.

■ The NetBackup-Java service cannot monitor a job (started by either theNetBackup-Java authentication service or user service). The reason it cannotmonitor is probably due to a lack of system resources (insufficient memory).

■ The maximum number of non-transient activity monitor jobs (>100) havealready been started.

Recommended Action: Do the following, as appropriate:

■ If the problem persists, restart the NetBackup-Java interface and try again.

■ If the problem still persists, enable detailed debug logging as explained in thefollowing topic:See “Enabling detailed debug logging” on page 127.

■ Restart the NetBackup-Java interface and examine the logs.

The error is probably the result of a system resource issue. When detailed debuglogging is enabled, you can retrieve the details from the bpjava-msvc,bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 510Message: File already exists: file_name

Explanation: The NetBackup-Java user service try to create a file that alreadyexists.

RecommendedAction: Remove the file, which can be identified in the user servicelog files.

See “Troubleshooting the Administration Console for UNIX” on page 125.

NetBackup status code: 511Message: NB-Java application server interface error.

Explanation: In some instances, this message concludes with "Check the log filefor more details."

NetBackup status codes and messagesAbout NetBackup status codes and messages

324

This generic error for all non-socket IO/connection-broken related errors (statuscode 507) can occur when data is processed from the NetBackup-Javaauthentication or user services. The Java exception provides some additionaldetail about the error.

This error usually results from system or network problems.

Recommended Action: Do the following, as appropriate:

■ If the problem persists, restart the NetBackup-Java interface and try again.

■ If the problem still persists, enable detailed debug logging as explained in thefollowing topic:See “Enabling detailed debug logging” on page 127.

■ Restart the NetBackup-Java interface and examine the logs.

The error is probably the result of a system resource issue. When detailed debuglogging is enabled, the details can be retrieved from the bpjava-msvc,bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 512Message: Internal error - a bad status packet was returned by NB-Java applicationserver that did not contain an exit status code.

Explanation: The NetBackup-Java authentication or user service returned a datapacket that indicated an error, but no status code or error message was containedwithin it.

Recommended Action: Do the following, as appropriate:

■ If the problem persists, restart the NetBackup-Java interface and try again.

■ If the problem still persists, enable detailed debug logging as explained in thefollowing topic:See “Enabling detailed debug logging” on page 127.

■ Restart the NetBackup-Java interface and examine the logs.

The error is probably the result of a system resource issue. When detailed debuglogging is enabled, the details can be retrieved from the bpjava-msvc,bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 513Message: bpjava-msvc: the client is not compatible with this server version(server_version).

325NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The NetBackup-Java application server (on the remote host you login to) is not the same version as the NetBackup-Java interface on your local host.The two are therefore incompatible.

Recommended Action: Do the following, as appropriate:

■ Log in to a different NetBackup remote host.

■ Upgrade the NetBackup software on either of the following: the computer thatis specified in the logon dialog box or the local host where you started theNetBackup Java interface.

NetBackup status code: 514Message: NB-Java: bpjava-msvc is not compatible with this application version(application_version). You may try logon to a different NetBackup host or exit theapplication. The remote NetBackup host has to be configured with the same versionof NetBackup as the host you started the application on.

Explanation: In some instances, this message concludes with "Check the log filefor more details."

The NetBackup-Java application server (on the remote host you log in to) is notthe same version as the NetBackup-Java interface on your local host. The two aretherefore incompatible.

Recommended Action: Do the following, as appropriate:

■ Log in to a different NetBackup remote host.

■ Upgrade the NetBackup software on either of the following: the specifiedcomputer in the logon dialog box or the local host where you started theNetBackup Java interface.

NetBackup status code: 516Message: Could not recognize or initialize the requested locale -(locale_NB-Java_was_started_in).

Explanation: This status concerns the UNIX or Linux locale configuration (orWindows regional settings) defined on the host that was specified in the NB-Javalogon dialog box. At logon, the locale configuration is passed to the NB-Javaauthentication service. Status 516 is generated if the locale is not recognized orif the locale of the user service cannot be initialized.

The rules in the following files determine how a valid locale is recognized:/usr/openv/msg/.conf on UNIX and Linux and install_path\msg\lc.conf onWindows. When the locale is validated, initialization of the locale in the userservice’s environment is tried (by means of setlocale).

NetBackup status codes and messagesAbout NetBackup status codes and messages

326

Recommended Action: On the specified host in the NB-Java logon dialog box,check the configuration file to ensure that a mapping is available for the indicatedlocale.

For information on locale configuration and mapping, refer to the NetBackupAdministrator's Guide, Volume II.

If there is a mapping, try to set the mapped locale on the host that was specifiedin the NB-Java logon dialog box. This system may not be configured properly.

NetBackup status code: 517Message: Can not connect to the NB-Java user service via VNETD on host on portconfigured_port_number. If successfully logged in beforehand, retry your lastoperation. Check the log file for more details.

Explanation: After the NB-Java authentication service validates the user nameon the logon dialog box for access, all Administration console service requestsuse an NB-Java user service. Communication between the Administration consoleand user service is tried to host (host) on the specified port number in the errormessage by using VNETD. (The NB-Java configuration optionNBJAVA_CONNECT_OPTION is set to 1.) The NetBackup Administration Consolelog file should contain more detail about this error.

Recommended Action: Do the following, as appropriate:

■ On UNIX and Linux: Compare the VNETD entry in the /etc/services file withthe VNETD_PORT entry in /usr/openv/java/nbj.conf

On Windows: Compare the VNETD entry with the VNETD_PORT entry in theinstall_path\java\setconf.bat file.

These entries must match.

■ Ensure that no other application uses the port that is configured for VNETD.

NetBackup status code: 518Message: No ports available in range (port_number) through (port_number) perthe NBJAVA_CLIENT_PORT_WINDOW configuration option.

Explanation: All the ports in the specified range are in use. Too many users(concurrent) of the NetBackup-Java interface or too few configured ports cancause this error.

Recommended Action: Do the following, as appropriate:

■ Restart the NetBackup-Java interface and try again.

327NetBackup status codes and messagesAbout NetBackup status codes and messages

■ If the problem persists, increase the range of ports by changing theNBJAVA_CLIENT_PORT_WINDOW option in the /usr/openv/java/nbj.conffile (UNIX and Linux) or the install_path\java\setconf.bat file (Windows).

NetBackup status code: 519Message: Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value:(option_value).

Explanation: The value for the NB-Java configuration optionNBJAVA_CLIENT_PORT_WINDOW is invalid.

Recommended Action: Correct the value in file /usr/openv/java/nbj.conf

(UNIX and Linux) or install_path\java\setconf.bat file (Windows).

NetBackup status code: 520Message: Invalid value for NB-Java configuration option (option_name):(option_value).

Explanation: The specified NetBackup-Java configuration option has an invalidvalue.

Recommended Action: Correct the value in file /usr/openv/java/nbj.conf

(UNIX and Linux) or install_path\java\setconf.bat file (Windows).

NetBackup status code: 521Message: NB-Java Configuration file (file_name) does not exist.

Explanation: The configuration file for the NetBackup-Java interface was notfound.

RecommendedAction: Make sure that the configuration file the NetBackup-Javainterface exists and is properly formatted.

NetBackup status code: 522Message: NB-Java Configuration file (file_name) is not readable due to thefollowing error: (message).

Explanation: The specified NetBackup-Java configuration file exists but is notreadable.

Recommended Action: Correct the file as specified in the message.

NetBackup status code: 523Message: NB-Java application server protocol error.

NetBackup status codes and messagesAbout NetBackup status codes and messages

328

Explanation: In some instances, this message concludes with "Check the log filefor more details."

The NetBackup-Java interface received an incorrectly formatted protocol sequencefrom its application server.

Recommended Action: Do the following, as appropriate:

■ If the problem persists, restart the NetBackup-Java interface and try again.

■ If the problem still persists, enable detailed debug logging as explained in thefollowing topic:See “Enabling detailed debug logging” on page 127.

■ Restart the NetBackup-Java interface and examine the logs.

Note: The error is probably the result of a system resource issue. When detaileddebug logging ID is enabled, the details can be retrieved from the bpjava-msvc,bpjava-susvc, or bpjava-usvc log files.

NetBackup status code: 525Message: Can not connect to the NB-Java authentication service via VNETD on(host) on port (vnetd_configured_port_number). Check the log file for more details.

Explanation: The NB-Java authentication service authenticates the user namethat is provided in the logon dialog box. Communication between the NetBackupAdministration Console and the authentication service is tried to host host on theconfigured VNETD port number that error message specifies. The NetBackupAdministration Console log file should contain more detail about this error.

Recommended Action: Do the following, as appropriate:

■ On UNIX and Linux: Compare the VNETD entry in the /etc/services file withthe VNETD_PORT entry in /usr/openv/java/nbj.conf

On Windows: Compare the VNETD entry with the VNETD_PORT entry in theinstall_path\java\setconf.bat file.

These entries must match.

■ Ensure that no other application uses the port that is configured for VNETD.

NetBackup status code: 600Message: an exception condition occurred

Explanation: The synthetic backup job encountered an exception condition.

329NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Contact customer support and send appropriate debuglogs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 601Message: unable to open listen socket

Explanation: The bpsynth process cannot open a socket to listen for incomingconnections from the bptm or the bpdm processes that were started for thefollowing: for reading backup images or for writing the synthetic image on themedia servers.

RecommendedAction: Check the OS error that was reported in the error message,which bpsynth logged in the NetBackup error log. This error helps to diagnosethe problem. Ensure that the bpsynth binary matches the installed NetBackupversion. Retry the synthetic backup job. If the problem persists, contact customersupport and provide the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 602Message: cannot set non blocking mode on the listen socket

Explanation: The bpsynthprocess is unable to set the non-blocking socket optionon the listen socket.

RecommendedAction: Check the OS error that was reported in the error message,which was logged in the NetBackup error log. The error helps to diagnose theproblem. Ensure that the bpsynthbinary matches the installed NetBackup version.If the condition persists, contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 603Message: cannot register handler for accepting new connections

Explanation: The bpsynth process cannot register the listen socket with the ACEreactor.

NetBackup status codes and messagesAbout NetBackup status codes and messages

330

Recommended Action: Ensure that the bpsynth binary matches the installedNetBackup version. Retry the synthetic backup job. If the problem persists, contactcustomer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 604Message: no target storage unit specified for the new job

Explanation: A mismatch occurred between storage units that are known toNetBackup and the specified target storage unit.

Recommended Action: Retry the synthetic backup job. If the problem persists,contact customer support and provide appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 605Message: received error notification for the job

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 606Message: no robot on which the media can be read

Explanation: bpsynth returns this error when it cannot find a robot on which toread a particular media ID that contains backup images to be synthesized. Themedia ID is included in the message that bpsynth logs. This error should not occur.

RecommendedAction: Contact customer support and provide appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 607Message: no images were found to synthesize

331NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The database query to obtain the images to synthesize for the givenpolicy did not return any images.

Recommended Action: Ensure that a synthetic full backup has one full image(real or synthetic) and one or more subsequent incremental images (differentialor cumulative) to synthesize. For a cumulative synthetic backup, there must betwo or more incremental (differential or cumulative) images to synthesize. Adjustyour schedules so the appropriate backup jobs complete successfully before thesynthetic job is run. The scheduler does not retry a synthetic backup job that failswith this error code.

NetBackup status code: 608Message: storage unit query failed

Explanation: The database query to obtain all storage units failed.

Recommended Action: Verify that the bpdbm process is running and that noerrors were logged to the NetBackup error log. Restart the bpdbmprocess (on UNIXand Linux), or the NetBackup Database Manager Service (on Windows) and retrythe synthetic backup job. If the problem persists, contact customer support andsend the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 609Message: reader failed

Explanation: The bptm or the bpdm reader process was terminated with an error.

Recommended Action: Refer to the NetBackup error log for the errors that thebpsynth and bptm or bpdm reader logged. The error message should contain theactual error that the bptm or the bpdm reader reports. Refer to the NetBackupTroubleshooting Guide for information on the error that the bptm or the bpdm

reader reports. The media may not be present or is defective or the drive that wasused for reading the media is defective. If the problem persists, contact customersupport and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 610Message: end point terminated with an error

NetBackup status codes and messagesAbout NetBackup status codes and messages

332

Explanation: An error indication was received on the connection to the bptm orthe bpdm process.

Recommended Action: Review the errors in the NetBackup error log that thefollowing processes logged: bpsynth and bptm or bpdm. Refer to the debug logs forthese processes for more information. The connection may have broken due tothe following: an error condition that the bptm or the bpdm process detects ornetwork problems between the master and the media server. Check the networkconnectivity between the master and the media server. Retry the job and if theproblem persists, contact customer support and send the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 611Message: no connection to reader

Explanation: A connection to the bptm or the bpdm reader process does not existto communicate with the reader.

Recommended Action: This error should not occur. Submit a problem reportalong with the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 612Message: cannot send extents to bpsynth

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 613Message: cannot connect to read media server

Explanation: The bpsynth process was unable to connect to the media server toread a backup image.

Recommended Action: Ensure that network connectivity exists between themaster server and the specified media server. Examine the NetBackup error logfor any error messages that bpsynth logged. For more information, refer to the

333NetBackup status codes and messagesAbout NetBackup status codes and messages

debug logs for bpsynth on the master server and bpcd and bptm or bpdm on themedia server.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 614Message: cannot start reader on the media server

Explanation: The bpsynthprocess was unable to start the bptmor the bpdmprocessto read a backup image to be synthesized.

Recommended Action: Do the following, as appropriate:

■ Examine the NetBackup error log for any errors that bpsynth logged. For moreinformation, refer to the following debug logs: for bpsynthon the master serverand for bpcd and bptm or bpdm on the media server. Ensure that the bptm orthe bpdm binaries on the media server are executable and are not corrupt. Tryrunning bptm or bpdm commands locally on the media server to ensure thatthe binary is executable and not corrupt. For instance, you can run the followingcommand

/bp/bin/bptm -count -rn 0 -rt 8

where robot number is 0 and the robot type is 8. The robot type thatcorresponds to the robot number can be taken from the command line that islogged in the debug log for bptm. This command displays the counts for theup, shared, and assigned drives in the robot.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 615Message: internal error 615

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 616Message: internal error 616

NetBackup status codes and messagesAbout NetBackup status codes and messages

334

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 617Message: no drives available to start the reader process

Explanation: No drives are available to start the bptm process to read a backupimage to be synthesized.

Recommended Action: Ensure that sufficient drives are available before youre-start the job.

NetBackup status code: 618Message: internal error 618

Explanation: This error code is no longer used.

RecommendedAction: Contact customer support and send the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 619Message: internal error 619

Explanation: This error code is no longer used.

RecommendedAction: Contact customer support and send the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 620Message: internal error 620

Explanation: This error code is no longer used.

RecommendedAction: Contact customer support and send the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

335NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 621Message: unable to connect to bpcoord

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 622Message: connection to the peer process does not exist

Explanation: The underlying connection to the peer bptm or bpdm process doesnot exist. This error should not occur.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 623Message: execution of a command in a forked process failed

Explanation: The failure normally occurs during the execution of a command ona media server through bpcd. Examine the NetBackup error log for additionalerror messages. Also refer to the debug logs for bpsynth (on the master server)and bpcd (on the media server) to get an explanation of the failure. A commoncause of the failure is insufficient memory, file system full, or insufficient swapspace.

RecommendedAction: Retry the job and if the problem persists, contact customersupport and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 624Message: unable to send a start command to a reader or a writer process on mediaserver

Explanation: The bpsynth process is unable to send a command to the bptm orthe bpdm process on the media server.

NetBackup status codes and messagesAbout NetBackup status codes and messages

336

Recommended Action: Ensure that network connectivity exists between themaster and the media server. Look for additional error messages in the NetBackuperror log. More detailed information is present in the debug logs for bpsynth (onmaster server) and bptm or bpdm on the media server. If the problem persists,contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 625Message: data marshalling error

Explanation: Problems were encountered while sending data over the connection.This error should not occur.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 626Message: data un-marshalling error

Explanation: Problems were encountered in the parsing of the messages thatbpsynth received. This error should not occur.

RecommendedAction: Contact customer support and send the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 627Message: unexpected message received from bpsynth

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 628Message: insufficient data received

337NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: This error occurs in the following situation: partial data is readfrom the input socket and cannot be parsed until the remaining data that comprisesthe message is read. The lower layers encounter this error; it should not cause aprocess to be terminated.

Recommended Action: If this error causes the bpsynth binary to hang ormalfunction, contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 629Message: no message was received from bptm

Explanation: This error is returned when no message is received from bptm

process in response to the command or query executed by using bptm.

RecommendedAction: Look for additional error messages in the following logs:the NetBackup error log and the debug logs for bpsynth on the master server andbptm on the media server. A system condition (insufficient memory, file systemfull, insufficient swap space) on the media server may prevent the bptm processfrom sending the response. Verify the network connectivity between the masterand the media server. If no explanation is found for the failure and the problempersists, contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 630Message: unexpected message was received from bptm

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 631Message: received an error from bptm request to suspend media

Explanation: The bpsynth process was unable to suspend a media that containedone or more images to be synthesized. A message in the bpsynth legacy log liststhe media IDs to be suspended. The bpsynth log also includes a failure message

NetBackup status codes and messagesAbout NetBackup status codes and messages

338

to indicate which particular media in the list was not suspended. media (ordinal)

indicates the unsuspended media by means of its order in the list. For example,if the unsuspended media was the second media in the list, the failure messagesays media (1).

RecommendedAction: Examine the bptm debug log for more information on thereason for the suspend failure. The bpsynth process ignores this error andcontinues to process. It has the potential to fail later if the media with the imagesto be read gets assigned to another backup or restore job. If the synthetic backupjob fails, fix the condition that lead to the suspend failure and retry the job.

NetBackup status code: 632Message: received an error from bptm request to un-suspend media

Explanation: The bpsynth process was unable to un-suspend a media that itsuspended at the start of the synthetic backup job. A message in the bpsynthlegacy log lists the media IDs to be un-suspended. The bpsynth log also includesa failure message to indicate which particular media in the list was notun-suspended. media (ordinal) indicates the media by means of its order in thelist. For example, if the media that was not un-suspended was the second mediain the list, the failure message says media (1).

Recommended Action: Look at the debug log for the bptm process on the mediaserver for an explanation of the un-suspend failure and the media ID. Try toun-suspend the tape manually by using the bpmedia command.

NetBackup status code: 633Message: unable to listen and register service via vnetd

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 634Message: no drives available to start the writer process

Explanation: The bpsynth process cannot start the synthetic backup job becauseno drives were available in the target storage unit for the writer. The storage unitmay be in use by a restore or another synthetic backup job.

339NetBackup status codes and messagesAbout NetBackup status codes and messages

RecommendedAction: Ensure that the target storage unit that is configured forthe synthetic backup schedule has an available drive to write the synthetic backupimage.

NetBackup status code: 635Message: unable to register handle with the reactor

Explanation: Unable to register a handle with the ACE reactor to monitor eventson the handle. This error can occur in bpsynth.

Recommended Action: Examine NetBackup error log for any errors that werelogged for the job. Refer to the debug logs for bpsynth for more information. Retrythe synthetic backup job. If the problem persists, contact customer support andsend the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 636Message: read from input socket failed

Explanation: The read from an input socket failed. The underlying connectionhas been broken.

RecommendedAction: The bpsynth process encountered an error while readingfrom an input socket. The socket may be between bpsynth and bptm or bpdm.

The errno that was logged to the NetBackup error log indicates the reason for thefailure. For more information, refer to the following: the debug log for bpsynth(on the master server) and for the bptm or the bpdm reader or writer processes (onthe media server). Check the network connectivity between the master and themedia server. Rerun the synthetic backup job. If the problem persists, contactcustomer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 637Message: write on output socket failed

Explanation: The write to an output socket failed. The underlying connectionhas been broken.

RecommendedAction: The bpsynth process encountered an error while writingto an output socket. The socket is between bpsynth and bptm or bpdm.

NetBackup status codes and messagesAbout NetBackup status codes and messages

340

The errno that logged to the NetBackup error log indicates the reason for thefailure. For more information, refer to the following: the debug log for bpsynth(on the master server) and for the bptm or the bpdm reader or writer process (onthe media server). Check the connectivity between the master and the mediaserver. Retry the synthetic backup job. If the problem persists, contact customersupport and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 638Message: invalid arguments specified

Explanation: The bpsynth command fails with this error code if incorrectarguments were specified.

RecommendedAction: Refer to the bpsynth command line arguments (by using-help) for the correct argument specification. If the synthetic backup job wasstarted manually by the command line, correct the arguments to bpsynth andrerun the job. If the synthetic backup job was scheduled or started with the console,ensure that the bpsynth and the nbjm binaries match the installed NetBackupversion.

NetBackup status code: 639Message: specified policy does not exist

Explanation: The policy that was specified on the bpsynth command does notexist in the database. Either the command line or nbjm initiated the bpsynth

command. If nbjm initiated it, the policy may have been deleted after nbjm startedbpsynth and before bpsynth issued the database query.

Recommended Action: If bpsynth is initiated with the command line, rerun thecommand for an existing policy. If the problem persists after you verify thefollowing, contact customer support and send the appropriate logs:

■ The synthetic backup job was scheduled or started by using the NetBackupAdministration console (manual start).

■ The policy exists in the bppllist command configuration.

■ Check the logs for nbjm, which uses unified logging (OID 117).

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

341NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 640Message: specified schedule was not found

Explanation:The schedule on the bpsynth command did not exist in the specifiedpolicy definition in the database due to either of the following:

■ The command line initiated the bpsynth command

■ The specified schedule was deleted from the policy after nbjm started bpsynth,before bpsynth issued the database query.

Recommended Action: If the command line initiated bpsynth, do the following:rerun the command with the correct synthetic schedule label defined in the policyof the synthetic backup job to be run. If the synthetic backup job was scheduledor started with the NetBackup Administration console, define a new schedule inthe policy and retry the job. If the problem persists, contact customer supportand send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 641Message: invalid media type specified in the storage unit

Explanation: The media type that was specified in the target storage unit is invalidfor synthetic backup. Synthetic Backup images can only be written to disk, diskstaging, and Media Manager type of storage units.

Recommended Action: Ensure that the target storage unit that was configuredfor synthetic backup is a disk, disk staging, or Media Manager type (not NDMPtype). Rerun synthetic backup with the appropriate storage unit.

NetBackup status code: 642Message: duplicate backup images were found

Explanation: The database query returned duplicate backup IDs. This error shouldnot occur.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 643Message: unexpected message received from bpcoord

NetBackup status codes and messagesAbout NetBackup status codes and messages

342

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 644Message: extent directive contained an unknown media id

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 645Message: unable to start the writer on the media server

Explanation: The bpsynth process was unable to start the following: the bptm orthe bpdm process on the media server that is associated with the target storageunit to write the synthetic image.

Recommended Action:

Examine the NetBackup error log for any messages that bpsynth logged. For moreinformation, refer to the following: the debug logs for bpsynth on the masterserver and bpcd and bptm or bpdm on the media server. Ensure that the bptm orthe bpdm binaries on the media server are executable and are not corrupt. Try torun the bptm or the bpdm commands locally on the media server to ensure thatthe binary is executable and not corrupt. For instance, you can run the followingcommand:

install_path/netbackup/bin/bptm -count -rn 0 -rt 8

where robot number is 0 and robot type is 8. The robot type that corresponds tothe robot number can be taken from the command line that is logged in the debuglog for bptm. This command displays the counts for the up, shared, and assigneddrives in the robot. In case the synthetic image is to be written to a disk storageunit, verify the bpdm binary by running the following command:

install_path/netbackup/bin/bpdm

343NetBackup status codes and messagesAbout NetBackup status codes and messages

It should print the following: "bpdm: media manager operation not specified".Retry the synthetic backup job. If the problem persists, contact customer supportand send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 646Message: unable to get the address of the local listen socket

Explanation: The bpsynthprocess cannot obtain the address of the opened listensocket. The bpsynth process needs the address to receive incoming connectionsfrom the bptm or the bpdmprocesses, which were started to read the source images.This problem should not happen. The library call used to retrieve the address ofthe listen socket relies on the underlying system call to obtain the socket address.The errno that the system call reports is included in the error message and shouldhelp to diagnose the problem.

Recommended Action: Rerun the synthetic backup job. If the problem persists,contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 647Message: validation of synthetic image failed

Explanation: This error is returned when bpsynth receives an error from thedatabase call to validate the synthetic image.

RecommendedAction: This error may indicate a problem in the synthetic backupprocess. Examine the NetBackup error log for any messages that the followingprocesses logged: bpsynth and bptm or bpdm. Look at the debug logs for theseprocesses for additional information. If you cannot resolve the problem, contactcustomer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 648Message: unable to send extent message to BPXM

Explanation: The bpsynth process cannot send extent information to the bptm

or the bpdmprocess that was started to read a specified backup image to synthesize.

NetBackup status codes and messagesAbout NetBackup status codes and messages

344

Recommended Action: This error indicates a communication problem betweenbpsynth and the bptm or the bpdm reader process on the media server. Ensure thatthe media server is accessible and that the bptm or the bpdm process is runningon the media server. Examine the NetBackup error log for any errors that thefollowing logged: bpsynth (on the master server) and the bptm or the bpdm readerprocess (on the media server). Examine the debug logs for bpsynth and bptm orbpdm for additional information. Rerun the synthetic backup job. If the problempersists, contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 649Message: unexpected message received from BPXM

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 650Message: unable to send extent message to bpcoord

Explanation: This error code is no longer used.

Recommended Action: Submit a problem report along with appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 651Message: unable to issue the database query for policy

Explanation: The bpsynth process was unable to send the database query forpolicy.

Recommended Action: This error indicates a communication problem betweenbpsynth and bpdbm. Ensure that bpdbm is running and the bpdbm binary matchesthe installed NetBackup version. Examine the NetBackup error log for any errorsthat bpdbm and bpsynth logged. Examine the debug logs for bpsynth and bpdbm

for additional information. Restart the bpdbm process (on UNIX and Linux) or theNetBackup Database Manager Service (on Windows) and rerun the synthetic

345NetBackup status codes and messagesAbout NetBackup status codes and messages

backup job. If the problem persists, contact customer support and send appropriatelogs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 652Message: unable to issue the database query for policy information

Explanation: The bpsynth process was unable to send the database query fordetailed information about the policy.

Recommended Action: This error indicates a communication problem betweenbpsynth and bpdbm. Ensure that bpdbm is running. Examine the NetBackup errorlog for any errors that bpdbm and bpsynth logged. Examine the debug logs forbpsynth and bpdbm for additional information. Restart the bpdbmprocess (on UNIXand Linux) or the NetBackup Database Manager Service (on Windows) and rerunthe synthetic backup job. If the problem persists, contact customer support andsend appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 653Message: unable to send a message to bpccord

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 654Message: internal error 654

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status codes and messagesAbout NetBackup status codes and messages

346

NetBackup status code: 655Message: no target storage unit was specified via command line

Explanation: No target storage unit was specified on the bpsynth command line(-S).

Recommended Action: Rerun bpsynth with the target storage unit specified bythe -S option.

NetBackup status code: 656Message: unable to send start synth message to bpcoord

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 657Message: unable to accept connection from the reader

Explanation: The bpsynth process was unable to accept the connection from thebptm or the bpdm reader process that runs on the media server.

Recommended Action: Examine the NetBackup error log for any errors thatbpsynth and bptm or the bpdm reader process logged. The message that bpsynthlogged includes the error (errno) reported by the system call. Refer to the debuglogs for bpsynth on the master server and bptm or the bpdm process on the mediaservers for more information. Ensure that network connectivity exists betweenthe master and the media servers. If the problem persists, contact customersupport and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 658Message: unable to accept connection from the writer

Explanation: The bpsynth process was unable to accept the connection from thebptm or the bpdm writer process that runs on the media server.

Recommended Action: Examine the NetBackup error log for any errors thatbpsynth and the bptm or the bpdmwriter process logged. The message that bpsynthlogged includes the error (errno) reported by the system call. Also refer to the

347NetBackup status codes and messagesAbout NetBackup status codes and messages

debug logs for bpsynth on the master server and bptm or the bpdm process on themedia server for more information. Ensure that network connectivity existsbetween the master and the media servers. If the problem persists, contactcustomer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 659Message: unable to send a message to the writer child process

Explanation: The bpsynth process was unable to send the message that containsthe following to the bptm or the bpdm writer: the hostname and the port numberof the bptm or the bpdm reader.

Recommended Action: Examine the NetBackup error log for any errors thatbpsynth and the bptm or the bpdm writer process logged. Refer to the followingfor more information: the debug logs for bpsynth on the master server and thebptm or the bpdm process on the media server. Ensure that network connectivityexists between the master and the media servers. If the problem persists, contactcustomer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 660Message: a synthetic backup request for media resources failed

Explanation: The request for resources failed due to an internal NetBackup error.

Recommended Action: Create logs as explained in the following topics:

See “Logs to accompany problem reports for synthetic backup” on page 113.

Rerun the job. Then send the logs to customer support. More information isavailable about unified logs.

See “Submitting unified logging files to Symantec support” on page 101.

NetBackup status code: 661Message: unable to send exit message to the BPXM reader

Explanation: The bpsynth process cannot send the exit message to indicate theend of extents messages to the following: bptm or the bpdm reader process on the

NetBackup status codes and messagesAbout NetBackup status codes and messages

348

media server. The network connection between the master and the media servermay have terminated or the bptm or the bpdm reader process has terminated.

RecommendedAction: Check the network connectivity between the master andthe media server. Examine the NetBackup error log for any errors that bpsynthand bptm or the bpdm reader process logged. Examine the debug logs for bpsynthon the master server and bptm or the bpdm reader process on the media serversfor more detailed information. If the problem persists, contact customer supportand provide the appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 662Message: unknown image referenced in the synth context message from BPXM

Explanation: The bpsynth process received an extent message from the bptm orthe bpdm reader with reference to a media ID that was unknown to bpsynth. Thiserror should not occur.

Recommended Action: Contact customer support and provide the appropriatelogs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 663Message: image does not have a fragment map

Explanation: The bpsynth process received an image without a fragment mapfrom bpdbm. This error should not occur.

Recommended Action: Contact customer support and provide the appropriatelogs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 664Message: zero extents in the synthetic image, cannot proceed

Explanation: The bpsynth process receives zero extents from bpdbm. This errorshould not occur.

349NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Contact customer support and provide the appropriatelogs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 665Message: termination requested by bpcoord

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 667Message: unable to open pipe between bpsynth and bpcoord

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 668Message: pipe fgets call from bpcoord failed

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 669Message: bpcoord startup validation failure

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and send appropriate logs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status codes and messagesAbout NetBackup status codes and messages

350

NetBackup status code: 670Message: send buffer is full

Explanation: This error code is no longer used.

Recommended Action: Contact customer support and provide the appropriatelogs.

A complete list of required logs and configuration information is available.

See “Logs to accompany problem reports for synthetic backup” on page 113.

NetBackup status code: 671Message: query for list of component images failed

Explanation: A new synthetic image cannot be formed because of a problem withthe required component images. For example: a new, synthetic full backup is triedfrom the previous full image from Sunday and from the five differentialincremental images from Monday through Friday. This error occurs if any of thoseimages (except the most recent image on Friday) has expired.

Recommended Action: Run a non-synthetic backup (either a new full or newcumulative), depending on the type of backup that failed.

NetBackup status code: 800Message: resource request failed

Explanation: The nbjm process was unable to get the required resources for ajob. An EMM reason string that appears in the Activity Monitor job details displayand in the nbjm debug log accompanies this status code. The EMM reason stringidentifies the reason for the failed resource request.

Recommended Action: Locate the EMM reason string, correct the problem, andrerun the job.

Some generic EMM reason strings (such as "Disk volume is down") may requiregenerating some reports to determine the cause of the failure. Generate the reportby using either bperror or various log entry reports, such as Reports > DiskReports > Disk Logs in the Administration Console.

NetBackup status code: 801Message: JM internal error

Explanation: The nbjm process encountered an internal error.

RecommendedAction: If the problem persists, submit a report with the followingitems.

351NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Unified logging files on the NetBackup server for nbpem (originator ID 116),nbjm (117), nbrb (118), and PBX (103). All unified logging is written to/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ Legacy logs:

■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,and nbproxy

■ On the media server for bpcd, bpbrm, and bptm or bpdm

■ On the client for bpcd and bpbkar

Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIXand Linux) or install_path\Netbackup\logs\ (Windows). If the directoriesdo not exist, create directories for each of these processes and rerun the job.

■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) orinstall_path\NetBackup\db\jobs\trylogs (Windows).

■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

NetBackup status code: 802Message: JM internal protocol error

Explanation: nbjm returns this error whenever a protocol error occurs with anexternal process that tries to communicate with nbjm. External processes includebptm, tpreq, bplabel, dqts, vmphyinv, or nbpem.

Recommended Action:

Ensure that the NetBackup software on the master and the media server is froman official NetBackup release.

If the problem persists, submit a report with the following items.

■ Unified logging files on the NetBackup server for nbpem (originator ID 116),nbjm (117), nbrb (118), and PBX (103). All unified logging is written to/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ Legacy logs:

■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,and nbproxy

■ On the media server for bpcd, bpbrm, and bptm or bpdm

■ On the client for bpcd and bpbkar

NetBackup status codes and messagesAbout NetBackup status codes and messages

352

Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIXand Linux) or install_path\Netbackup\logs\ (Windows). If the directoriesdo not exist, create directories for each of these processes and rerun the job.

■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) orinstall_path\NetBackup\db\jobs\trylogs (Windows).

■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

NetBackup status code: 803Message: JM terminating

Explanation: A service request for an existing or a new job was received whenthe nbjm process was shutting down.

Recommended Action: If nbjm was not terminated explicitly (by entering the/usr/openv/netbackup/bin/bp.kill_all command on UNIX and Linux orinstall_path\NetBackup\bin\bpdown on Windows), submit a report with thefollowing items.

■ Unified logging files on the NetBackup server for nbpem (originator ID 116),nbjm (117), nbrb (118), and PBX (103). All unified logging is written to/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ Legacy logs:

■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,and nbproxy

■ On the media server for bpcd, bpbrm, and bptm or bpdm

■ On the client for bpcd and bpbkar

Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIXand Linux) or install_path\Netbackup\logs\ (Windows). If the directoriesdo not exist, create directories for each of these processes and rerun the job.

■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) orinstall_path\NetBackup\db\jobs\trylogs (Windows).

■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

NetBackup status code: 805Message: Invalid jobid

Explanation: The nbjm process received an invalid job ID in the request.

353NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action:

The requested operation may refer to a job that no longer exists or is not knownto nbjm. Or the job ID is invalid (less than or equal to 0). Ensure that the commandused to start the job did not specify a job ID already in use by another job.

If the problem persists, submit a report with the following items.

■ Unified logging files on the NetBackup server for nbpem (originator ID 116),nbjm (117), nbrb (118), and PBX (103). All unified logging is written to/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ Legacy logs:

■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,and nbproxy

■ On the media server for bpcd, bpbrm, and bptm or bpdm

■ On the client for bpcd and bpbkar

Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIXand Linux) or install_path\Netbackup\logs\ (Windows). If the directoriesdo not exist, you must create directories for each of these processes and rerunthe job.

■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) orinstall_path\NetBackup\db\jobs\trylogs (Windows).

■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

NetBackup status code: 806Message: this mpx group is unjoinable

Explanation: This error is a timing problem. It can happen if the job was addedto a multiplexed group when bpbrm terminates due to an error condition. Notethat the resource broker (nbrb) does the allocation of a multiplexed group, whereasthe job manager (nbjm) starts and monitors the bpbrm process.

Recommended Action: If the failed job is scheduled and the retry count allowsit, nbpem submits the job again. If the failed job was initiated manually, submitit again.

NetBackup status code: 807Message: not externalized

Explanation: Not available.

Recommended Action: Not available.

NetBackup status codes and messagesAbout NetBackup status codes and messages

354

NetBackup status code: 811Message: failed to communicate with resource requester

Explanation: Job manager (nbjm) tries to notify a process (usually bptm) of thestatus of a resource it requested. That notification fails because of a communicationproblem.

Recommended Action: Do the following, as appropriate:

■ Verify connectivity between the master and the media server.

■ Verify Private Branch Exchange (PBX) configuration and permissions. Forinformation on PBX is available.See “Resolving PBX problems” on page 67.

NetBackup status code: 812Message: failed to communicate with resource broker

Explanation: Job manager (nbjm) tries to make a request to the resource broker(nbrb). The request fails because of a communication problem.

Recommended Action: Do the following, as appropriate:

■ Verify connectivity between the master sever and the EMM server.

■ Verify Private Branch Exchange (PBX) configuration and permissions. Forinformation on PBX is available.See “Resolving PBX problems” on page 67.

NetBackup status code: 813Message: duplicate reference string specified

Explanation: The reference string is the file name specified on the -f option ofthe tpreq command. The specified file name on tpreq is already in use by anothertpreq.

Recommended Action: Choose a unique name not already in use.

NetBackup status code: 818Message: retention level mismatch

Explanation: A job fails with this error code if the retention level of the allocatedmedia does not match the retention level configured in the policy.

RecommendedAction:Contact NetBackup Technical Support and provide relevantsupporting materials.

355NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 819Message: unable to communicate with JM proxy

Explanation: The job manager cannot communicate with nbproxy.

Recommended Action: Restart the job manager. If the condition persists, pleasecontact NetBackup Support and provide relevant supporting materials.

NetBackup status code: 823Message: no BRMComm to join

Explanation: The job was unable to join the multiplex group. This error is aninternal error.

Recommended Action: Submit a report with the following items.

■ Unified logging files on the NetBackup server for nbpem (originator ID 116),nbjm (117), nbrb (118), and PBX (103). All unified logging is written to/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ The following legacy logs:

■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,and nbproxy

■ On the media server for bpcd, bpbrm, and bptm or bpdm

■ On the client for bpcd and bpbkar

Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIXand Linux) or install_path\Netbackup\logs\ (Windows). If the directoriesdo not exist, create directories for each of these processes and rerun the job.

■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) orinstall_path\NetBackup\db\jobs\trylogs (Windows).

■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

NetBackup status code: 830Message: drive(s) unavailable or down

Explanation: All configured drive that can be used for this job are down.

One of the following has occurred:

■ No drives are configured for the media requested for the job.

■ The job requires an NDMP drive path, but no NDMP drive paths are up orconfigured.

NetBackup status codes and messagesAbout NetBackup status codes and messages

356

■ The job cannot use an NDMP drive path, but these are the only drive pathsthat are up or configured for the drive.

Recommended Action: Do the following:

■ Make sure the drives and drive paths are up and correct for the media thatyou configure.

■ Verify that ltid is running on the required media server, and that the mediaserver is active for tape.

■ Use the device monitor to start up the drives paths if they are down.

■ If the drives are downed again, clean the drives.

NetBackup status code: 831Message: image has been validated

Explanation:A job retry attempt fails because the image from the previous attempthas already been validated. This error can occur if nbjm shuts down before itreceives the job success status. This status code indicates a timing problem only.

Recommended Action: No corrective action is required.

NetBackup status code: 900Message: retry nbrb request later

Explanation: The NetBackup Resource Broker (nbrb service) was unable to respondto a request.

Recommended Action: Do the following, as appropriate:

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ If necessary, set global logging to a higher level by using Host Properties >Master Server > Properties > Logging. Retry the operation and examine thenbrb logs.

NetBackup status code: 901Message: RB internal error

Explanation: The NetBackup Resource Broker (nbrb service) encountered aninternal error.

Recommended Action: Do the following, as appropriate:

357NetBackup status codes and messagesAbout NetBackup status codes and messages

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ If necessary, set global logging to a higher level, by using Host Properties >Master Server > Properties > Logging. Retry the operation and examine thenbrb logs.

NetBackup status code: 902Message: RB invalid argument

Explanation: The NetBackup Resource Broker (nbrb service) detected an invalidargument.

Recommended Action: Do the following, as appropriate:

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ If necessary, set global logging to a higher level, by using Host Properties >Master Server > Properties > Logging. Retry the operation and examine thenbrb logs.

NetBackup status code: 903Message: RB communication error

Explanation: The NetBackup Resource Broker (nbrb service) encountered acommunication error.

Recommended Action: Do the following, as appropriate:

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ If necessary, set global logging to a higher level, by using Host Properties >Master Server > Properties > Logging. Retry the operation and examine thenbrb logs.

NetBackup status code: 904Message: RB max reallocation tries exceeded

NetBackup status codes and messagesAbout NetBackup status codes and messages

358

Explanation: Under some conditions, failed mounts are retried; the number ofretries for the resource request has been exceeded.

Recommended Action: For detailed information, examine the unified loggingfiles on the NetBackup server for the nbrb service (originator ID 118) and fornbemm (originator ID 111). All unified logging is written to /usr/openv/logs

(UNIX and Linux) or install_path\NetBackup\logs (Windows). Also examinethe legacy bptm log.

NetBackup status code: 905Message: RB media server mismatch

Explanation: If you have any storage units that are specified for multiple copies,they must be on the same media server.

Recommended Action: Do the following, as appropriate:

■ Configure the backup schedule with a storage unit or storage unit groups thatcan be run on the same media server.

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

NetBackup status code: 906Message: RB operator denied mount request

Explanation: By using the Device Management node in the NetBackupAdministration Console or the vmoprcmd command, the operator denied a mountrequest.

Recommended Action: Do the following, as appropriate:

■ Determine the cause of the mount request denial and retry the job.

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

NetBackup status code: 907Message: RB user cancelled resource request

Explanation: A user-initiated action caused a Resource Broker (nbrb) request tobe canceled.

359NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Do the following, as appropriate:

■ Determine the action that resulted in cancellation of the resource request.

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

NetBackup status code: 908Message: RB was reset

Explanation: The NetBackup Resource Broker (nbrb) resources and database werereset. Any nbrb requests that remain may fail when RB is reset. (An example of aprocess that resets the database is catalog recovery.)

Recommended Action: Do the following, as appropriate:

■ Determine the action that reset nbrb resources and the nbemm database.

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). All unified logging is writtento /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

NetBackup status code: 912Message: RB disk volume mount failed

Explanation: The attempt to mount a disk volume failed. Possible reasons arehardware problems, inconsistent EMM database, or a NetBackup Resource Broker(nbrb) error.

Recommended Action: Do the following, as appropriate:

■ For detailed information, examine the unified logging files on the NetBackupserver for the nbrb service (originator ID 118). Unified logging is written to/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs(Windows).

■ If necessary, set global logging to a higher level: Host Properties > MasterServer>Properties>Logging. Retry the operation and examine the nbrb logs.

NetBackup status code: 914Message: RB media reservation not found

Explanation: The read media for a duplicate or synthetic backup job must bereserved at the start of the job. Status 914 occurs when the NetBackup Resource

NetBackup status codes and messagesAbout NetBackup status codes and messages

360

Broker (nbrb) receives an allocation request for a read media that was neverreserved. It can result from an internal error in bpduplicate, nbjm, or nbrb.

Recommended Action: Do the following, as appropriate:

■ Examine the unified logging files on the NetBackup server for the nbrb service(originator ID 118). Unified logging is written to /usr/openv/logs (UNIX andLinux) or to install_path\NetBackup\logs (Windows).

■ If necessary, set global logging to a higher level: Host Properties > MasterServer>Properties>Logging. Retry the operation and examine the nbrb logs.

NetBackup status code: 915Message: RB disk volume mount must retry

Explanation: A shared disk job has failed because RB is unable to mount the diskvolume. Shared disk requires that volume file systems be unmounted andremounted before other media servers can use them.

Recommended Action: Do the following, as appropriate:

■ Verify that processes are not in the disk volume mount directories, whichprevents them from being unmounted. If the problem persists, restartNetBackup on the media server.

NetBackup status code: 916Message: Resource request timed out

Explanation: A job request for resources has failed because resources were notavailable before the configured time limit expired. Some jobs may specify a timeoutwhen they ask for drives or other resources. If jobs consistently cause this error,more jobs may be scheduled than the number of available drives. The drives inthe resbroker job queue are not completed soon enough to allow new jobs to startbefore they time out.

Recommended Action: Distribute the scheduled job start times over a widerperiod of time.

NetBackup status code: 1500Message: Invalid storage unit

Explanation: The storage unit or storage unit group specified for one or moredestinations in storage lifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

361NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Verify that the specified storage unit or storage unit group exists in theNetBackup database.

■ Verify that the specified storage unit is not of type BasicDisk, SnapVault, orStaging, because storage lifecycle policies do not support them.

■ Verify that the storage unit is not specified for snapshot destinations in storagelifecycle policy. Snapshot destinations do not require a storage unit in thestorage lifecycle policy.

NetBackup status code: 1501Message: Invalid source

Explanation: The source specified for one or more duplication destinations instorage lifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified source refers to a valid destination in the list ofdestinations in storage lifecycle policy.

■ Verify that the Backup or Snapshot destination type does not have any sourcespecified. If you are using nbstl to configure storage lifecycle policy, use valuezero (0) as the source for a backup or snapshot destination type.

■ Verify that the destination that refers to the specified source is not a Snapshotdestination type. NetBackup cannot duplicate a backup image that usessnapshot copy as a source.

■ Verify that the specified source does not refer to the destination itself forwhich the source is mentioned.

■ Verify that the specified list of destinations in a storage lifecycle has a circulardependency for the source.

NetBackup status code: 1502Message: Invalid retention type

Explanation: The retention type specified for one or more destinations in storagelifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

■ Verify that the retention type specified in storage lifecycle policy is either ofFixed, Staged capacity managed, or Expire after duplication.

■ Verify that the Expireafterduplication retention type is used for a destinationonly if it is specified as a source to other destinations in storage lifecycle policy.

NetBackup status codes and messagesAbout NetBackup status codes and messages

362

■ Verify that the Staged capacity managed retention type is used in storagelifecycle policy only for disk destinations that support Capacitymanagementcapabilities.

■ Verify that the Snapshot destination type in storage lifecycle policy uses Fixedretention type only.

NetBackup status code: 1503Message: Invalid volume pool

Explanation: The volume pool specified for one or more destinations in storagelifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified volume pool exists in NetBackup database.

■ Verify that the volume pool is not specified for the Backup destination typein storage lifecycle policy.

■ Verify that the volume pool is not specified for the Snapshot destination typein storage lifecycle policy.

■ Verify that the volume pool is not specified for the Duplication destinationtype that is using disk storage units in storage lifecycle policy.

NetBackup status code: 1504Message: Invalid source

Explanation: The media server group specified for one or more destinations instorage lifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified media server group exists in NetBackup database.

■ Verify that the media server group is not specified for Backup destinationtypes in storage lifecycle policy.

■ Verify that the server group is not specified for Snapshot destination typesin storage lifecycle policy.

■ Verify that the media server group is not specified for Duplication destinationtypes that are using disk storage unit in storage lifecycle policy.

NetBackup status code: 1505Message: Invalid alternate read server

363NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The alternate read server specified for one or more destinations instorage lifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

■ Verify that the specified alternate read server exists in the NetBackup database.

■ Verify that the alternate read server is not specified for Backup destinationtypes in storage lifecycle policy.

■ Verify that the alternate read server is not specified for Snapshot destinationtypes in storage lifecycle policy.

NetBackup status code: 1506Message: Invalid data classification

Explanation: The data classification specified in storage lifecycle policy is notvalid.

Recommended Action: Verify that the specified data classification exists in theNetBackup database.

NetBackup status code: 1508Message: Storage lifecycle policy exceeds maximum copies

Explanation: The list of destinations specified in storage lifecycle policy exceedsmaximum number of allowed backup copies.

Recommended Action: Do the following, as appropriate:

■ Verify that the number of destinations specified in storage lifecycle policydoes not exceed maximum backup copies configured in NetBackup.

■ Modify maximumbackupcopies to allow the expected number of destinationsin storage lifecycle policy or reduce the number of destinations to not exceedmaximum backup copies.

NetBackup status code: 1509Message: Storage lifecycle policy exceeds maximum backup destinations

Explanation: The number of Backup type destinations specified in storage lifecyclepolicy exceeds the maximum number of simultaneous copies allowed.

Recommended Action: Verify that the number of Backup type destinationsspecified in storage lifecycle policy is less than or equal to 4. (The default valueof the maximum number of allowed simultaneous copies parameter is 4.)

NetBackup status codes and messagesAbout NetBackup status codes and messages

364

NetBackup status code: 1510Message: Storage lifecycle policy cannot have more than one snapshot destination.

Explanation: The list of destinations specified in storage lifecycle policy exceedsthe maximum number of allowed snapshot destinations.

Recommended Action: Verify that the storage lifecycle policy is not configuredwith more than one “Snapshot” type of destinations.

NetBackup status code: 1511Message: Storage lifecycle policy must have at least one fixed retentiondestination.

Explanation: The specified storage lifecycle policy does not have any destinationwith a retention type of Fixed.

Recommended Action: Verify that the specified storage lifecycle policy has atleast one destination configured with a Fixed retention type.

NetBackup status code: 1512Message: Storage lifecycle policy must have at least one backup destination.

Explanation: The specified storage lifecycle policy does not have any backupdestination.

Recommended Action: Verify that the storage lifecycle policy has at least oneBackup type of destination.

NetBackup status code: 1513Message: Invalid duplication priority

Explanation: The duplication priority specified in storage lifecycle policy is notvalid.

Recommended Action: Verify that the duplication priority specified in storagelifecycle policy is in the range or 0 to 99999.

NetBackup status code: 1514Message: Invalid destination type

Explanation: The destination type specified on one or more destinations in storagelifecycle policy is not valid.

Recommended Action: Do the following, as appropriate:

365NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Verify that the destination type specified on each destination in storagelifecycle policy is either Backup, Duplication, or Snapshot.

■ If you are use the nbstl or bpadm command to configure storage lifecyclepolicy, the following are the valid values for the destination type: 0 indicatesBackup, 1 indicates Duplication, and 2 indicates Snapshot.

NetBackup status code: 1515Message: Invalid preserve multiplexing value

Explanation: The preserve multiplexing flag specified on one or more destinationsis not valid.

Recommended Action: Do the following, as appropriate:

■ If you use the nbstl command to configure storage lifecycle policy, then verifythat the valid values are used to indicate the preserve multiplexing flag foreach destination. The value “T” or “t” indicates true (Preserve multiplexing).The value “F” or “f” indicates false (do not preserve multiplexing).

■ Verify that destinations of type Backup are not configured to preservemultiplexing.

■ Verify that destinations of type Snapshot are not configured to preservemultiplexing.

■ Verify that destinations of type Duplication that are using disk storage unitsare not configured to preserve multiplexing.

NetBackup status code: 1516Message: All storage units or groups must be on the same media server.

Explanation: The destinations of type Backup specified in storage lifecycle policyare not accessible by the same media server.

Recommended Action: Verify that all the destinations of type Backup areaccessible by at least one common media server.

NetBackup status code: 1517Message: Invalid retention level

Explanation: The retention level specified for one or more destinations in storagelifecycle policy is not valid.

RecommendedAction: Verify that the retention level specified on each destinationin storage lifecycle policy is in the range of 0 to 24.

NetBackup status codes and messagesAbout NetBackup status codes and messages

366

NetBackup status code: 1518Message: Image is un-supported by storage lifecycle policy

Explanation: The backup image is un-supported by the configured storage lifecyclepolicy.

Recommended Action: Do the following, as appropriate:

■ Verify that if a NetBackup policy is configured to perform snapshot backupsand uses storage lifecycle policy as its storage destination, then the specifiedstorage lifecycle policy must be configured with a snapshot destination.Otherwise, backup images created by those NetBackup policies are notprocessed further by storage lifecycle policy for any lifecycle operations.

■ Verify that NetBackup policies using storage lifecycle policy as a storagedestination are not configured to perform “snapshots-only” operations andthey must create backups in addition to snapshots. Storage lifecycle policyeven though configured with a snapshot destination would perform lifecycleoperations on such images only if they have at least one backup copy.

NetBackup status code: 1800Message: Invalid client list

Explanation: For Enterprise Vault-type policies, verify that multiple clients arenot added to the list of clients if you specify any of the following Enterprise Vault8.0 directives in the backup selection:

■ EV_INDEX_LOCATION=

■ EV_VAULT_STORE_DB=

■ EV_OPEN_PARTITION=

■ EV_CLOSED_PARTITIONS=

■ EV_FINGERPRINT_DB=

■ EV_READY_PARTITIONS=

RecommendedAction:Specify only one client in the policy, or remove the directivefrom the backup selection that does not support multiple client.

See the Troubleshooting section of the NetBackup for Enterprise Vault AgentAdministrator’s Guide.

NetBackup status code: 2000Message: Unable to allocate new media for backup, storage unit has none available.

367NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: The NetBackup Media and Device Selection component (MDS) didnot allocate a new tape volume for backups. This error indicates that the s torageunit has no more volumes available in the volume pool for this backup. NetBackupdoes not change storage units during the backup.

Recommended Action: Try the following:

■ Recommended Action: Check the NetBackup Problems report to determinethe storage unit that is out of media.

■ If the storage unit is a robot with empty slots, add more volumes and specifythe correct volume pool. If no empty slots exist, move some media to nonroboticand add new volumes. If you have difficuly keeping track of your availablevolumes, try the available_media script located in the following directory:On UNIX: /usr/openv/netbackup/bin/goodies/available_media

On Windows:install_path\NetBackup\bin\goodies\available_media.cmd

This script lists all volumes in the volume configuration, and augments thatlist with information on the volumes currently assigned to NetBackup.

■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackupneeds a new tape and none are available in the current volume pool, it movesa tape from the scratch pool into the volume pool that the backup uses.

■ If the storage unit and volume pool appear to have media, verify the following:

■ Use the NetBackup Media List report to check that the volume is notFROZEN or SUSPENDED. If the volume is frozen or suspended, use thebpmedia command to unfreeze or unsuspend it, if so desired.

■ Volume has not expired or exceeded its maximum number of mounts.

■ The EMM database host name for the device is correct. If you change theEMM database host name, stop and restart the following: the Media Managerdevice daemon, ltid, (if the server is UNIX) or the NetBackup DeviceManager service (if the server is a Windows system).

■ The correct host is specified for the storage unit in the NetBackupconfiguration. The host connection must be the server (master or media)with drives connected to it.

■ The Media and Device Management volume configuration has media in thecorrect volume pool. Unassigned or active media is available at the requiredretention level. Use the NetBackup Media List report to show the retentionlevels, volume pools, and status for all volumes. Use the NetBackup MediaSummary report to check for active volumes at the correct retention levels.

■ Create the bptm debug log directory, and set mds VxUL logging (oid 143) todebug level 2, then retry the operation.

NetBackup status codes and messagesAbout NetBackup status codes and messages

368

■ If this storage unit is new and this attempt to use it is the first, stop and restartNetBackup on the master server. The mds unified logging files (OID 143) atdebug level 2 usually show the NetBackup media selection process.

NetBackup status code: 2001Message: No drives are available for this job

Explanation: A job requested a tape drive, but no eligible drive path was configuredfor the job.

Recommended Action: Try the following:

■ Verify that the required drives and robots are configured and up.

■ Verify that ltid is active and a drive path exists that is configured on the drivefor the media server that the storage unit requires.

■ If the job requires an NDMP drive path, verify that one exists.

NetBackup status code: 2002Message: Invalid STU identifier type

Explanation: A job has asked for allocation using an invalid Storage Unit identifiertype. The only valid Storage Unit identifier types are 0 (specific STU), 1 (group)or 2 (ANY).

Recommended Action: This error is internal. Call NetBackup support forresolution.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2003Message: Drive is not allocated.

Explanation: MDS has been asked to deallocate a drive that is not allocated.

RecommendedAction: This error is internal to the MDS component of NetBackup.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

369NetBackup status codes and messagesAbout NetBackup status codes and messages

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2004Message: Drive is already allocated

Explanation: MDS has been erroneously asked to allocate a drive that is alreadyallocated.

Recommended Action: A drive may have been reset while it was allocated for ajob. Wait for the jobs that use the drive to complete.

NetBackup status code: 2005Message: MDS has received an invalid message from a media server.

Explanation: bptm or bpdm on a media server has sent an improperly formattedmessage to MDS.

RecommendedAction: This error is internal. Call NetBackup support if this errorcauses jobs to fail.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

■ The bptm legacy log from the media server, with VERBOSE=5.

NetBackup status code: 2006Message: NDMP credentials are not defined in EMM.

Explanation: No eligible media server is configured with NDMP credentials toaccess the NDMP storage unit. Or, NetBackup tried to restore an NDMP imagefrom a disk storage unit when the media server is not at NetBackup Release 6.5.2or later.

Recommended Action: If the job uses an NDMP device, verify that the mediaserver being used has NDMP credentials configured for the filer.

NetBackup status code: 2007Message: Storage unit is not compatible with requesting job

Explanation: A job has asked for a storage unit that cannot be used for the job.

NetBackup status codes and messagesAbout NetBackup status codes and messages

370

Recommended Action: This error can occur when a job tries to run on a mediaserver that is not at a recent enough NetBackup revision level to run the job. Thejob may require a feature that is not available on the media server being requested.Verify that the storage unit type and media server called out by the policy andstorage unit support the feature the job is trying to use.

This error can occur when the policy being run is not compatible with the storageunits requested by the policy:

■ SnapVault storage units are requested for multiple copy jobs.

■ Catalog backups are directed to shared disk storage units.

■ Multiplexed jobs are directed to storage units that do not have the multiplexfeature configured.

■ NDMP backup policies are directed to non-NDMP storage units.

NetBackup status code: 2008Message: All compatible drive paths are down

Explanation: All configured drive that can be used for this job are down.

RecommendedAction: Verify that ltid is running on the required media server,and the media server is active for tape. Using device monitor, bring up the drivepaths if they are down. If drives are downed again, clean the drives.

NetBackup status code: 2009Message: All compatible drive paths are down but media is available

Explanation: All configured drives that can be used for this job are down.

RecommendedAction: Verify that ltid is running on the required media server,and the media server is active for tape. Using device monitor, bring up the drivepaths if they are down. If drives are downed again, clean the drives.

NetBackup status code: 2010Message: Job type is invalid

Explanation: The job type that is specified in an allocation request to the resourcebroker is not valid for the operation requested.

RecommendedAction: This error is internal. Call NetBackup support if this errorcauses jobs to fail.

Check the following logs:

371NetBackup status codes and messagesAbout NetBackup status codes and messages

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2011Message: The media server reported a system error.

Explanation: An allocation for the media server is in an inconsistent state.

RecommendedAction: This error is internal. Call NetBackup support if this errorcauses jobs to fail.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2012Message: Media has conflicts in EMM

Explanation: Requested media for job cannot be used because it is marked ashaving conflicts in the nbemm database.

Recommended Action: The media is marked as having conflicts. The upgradefrom NetBackup 5.x has found multiple volume databases where two tapes indifferent volume databases have the same media ID. Call technical support toresolve this situation.

NetBackup status code: 2013Message: Error record insert failed

Explanation: A database record insert has failed.

RecommendedAction: This error is internal. Call NetBackup support if this errorcauses jobs to fail.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status codes and messagesAbout NetBackup status codes and messages

372

NetBackup status code: 2014Message: Media is not assigned

Explanation: A job requires assigned media, but the requested media is notassigned.

Recommended Action: Verify that the job requested the desired media. Forexample, if you ask to list contents of the media, make sure you have specifiedthe correct media ID.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2015Message: Media is expired

Explanation: A job is trying to write to media that has already expired.

Recommended Action: Make sure that non-expired media is available for thejob.

Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2016Message: Media is assigned to another server

Explanation: A job cannot use the media on the storage server, because the mediais assigned to another storage server.

Recommended Action: Check the following logs:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

373NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 2017Message: Media needs to be unmounted from a drive

Explanation: The requested media needs to be unmounted from the drive it is inbefore it can be used for another job.

RecommendedAction: Identify the media requested by the job that returns thiserror. If it is used by another job, wait for that job to complete.

NetBackup status code: 2018Message: Number of cleanings is invalid

Explanation: A cleaning media has an invalid number of cleanings that remain.

RecommendedAction: On the ChangeMedia screen, set the number of cleaningsremaining for the cleaning media to a number greater than or equal to zero (0).

NetBackup status code: 2019Message: Media is in a drive that is not configured on local system

Explanation: A job is configured to use a media volume that has no drive pathconfigured to an eligible media server for the job. A media volume is misplacedor all drive paths are down for the media server accessible by the storage unitconfigured for a job.

Recommended Action: If drive paths are down, identify the media serverconfigured for use by the storage unit, and bring up the drive path to that mediaserver.

NetBackup status code: 2020Message: Robotic library is down on server

Explanation: NetBackup has marked the robot as down for the required mediaserver.

Recommended Action: Verify that the media server required for this allocationis running, and verify that ltid is up on that media server.

NetBackup status code: 2021Message: Allocation record insert failed

Explanation: The NetBackup mds component was unable to update the databasefor a device allocation.

Recommended Action: This error is internal. Check the following logs:

NetBackup status codes and messagesAbout NetBackup status codes and messages

374

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2022Message: Allocation status record insert failed

Explanation: The NetBackup mds component was unable to update the databasewith device allocation status information.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2023Message: Allocation identifier is not known to EMM

Explanation: The NetBackup mds component cannot find the device allocationrecord needed to allocate the device for this job.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2024Message: Allocation request update failed

Explanation: The NetBackup mds component was unable to update the databasefor a device allocation.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

375NetBackup status codes and messagesAbout NetBackup status codes and messages

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2025Message: Allocation request delete failed

Explanation: The NetBackup mds component was unable to delete a deviceallocation from the database.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2026Message: Allocation status request delete failed

Explanation: The NetBackup mds component was unable to modify an allocationstatus record for this job.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2027Message: Media server is not active

Explanation: This job requires a media server that is not currently available.

Recommended Action:

Do one or more of the following:

■ Verify that the media server required for this allocation is running.

■ If this is a tape job, verify that ltid is running on the media server. If a mediaserver has gone offline and returned online, a delay of several minutes mayoccur before a job can use that media server.

NetBackup status codes and messagesAbout NetBackup status codes and messages

376

■ Use the vmoprcmd command to show the state of the media server. If the jobis trying to access a disk storage unit, verify that the nbrmms process is runningon the media server. If the job is trying to access a tape storage unit, verifythat ltid is running on the media server.

NetBackup status code: 2028Message: Media is reserved

Explanation: The NetBackup mds component cannot allocate media becauseanother job has that media exclusively reserved.

Recommended Action: If multiple duplication jobs are attempting to use thesame tape media for read, each will reserve the media. NetBackup should allowmore than one job to get a reservation for the tape media.

This error is internal. Check the following logs to help identify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2029Message: EMM database is inconsistent

Explanation: An inconsistency in the NetBackup database is preventing allocationsfor this job.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

Run the nbrbutil -resetall command to get the NetBackup allocation databaseback into a consistent state. Note that this command cancels all jobs includingthose that are currently running.

NetBackup status code: 2030Message: Insufficient disk space or high water mark would be exceeded

Explanation: Insufficient disk space is available to run this job.

377NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Try the following possible solutions:

■ If there are images on disk that can be expired, expire them, and run nbdeleteto delete the images from disk.

■ It may be that NetBackup is creating disk images more quickly than they areexpiring. If so, modifications to policies may be necessary to change the rateof image creation/expiration for the disk.

■ It may be helpful to lower the high water mark and/or low water mark for thedisk group.

NetBackup status code: 2031Message: Media is not defined in EMM

Explanation: The media required for this job is not defined in the EMM database.

RecommendedAction: A media volume required for a restore job has been deletedfrom the EMM database. If the media is available, use bpimport to import it.

NetBackup status code: 2032Message: Media is in use according to EMM

Explanation: The NetBackup database indicates that the media is in use but isnot allocated to another job.

Recommended Action: This error is internal. Check the following logs to helpidentify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2033Message: Media has been misplaced

Explanation: Job requires media that is not in the expected robotic slot.

RecommendedAction: Verify that the media required by the job is in the properrobotic slot as shown by vmquery.

If the error persists, the following logs may be useful in understanding the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

NetBackup status codes and messagesAbout NetBackup status codes and messages

378

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

■ The verbose bptm logs on the media server(s) that access this media.

NetBackup status code: 2034Message: Retry the allocation request later

Explanation: Resources required for a job are currently in use.

Recommended Action: This error should never appear as a job return status. Inthe mds and nbrb vxul logs, it indicates that a job should queue because resourcesare busy.

NetBackup status code: 2035Message: Request needs to pend

Explanation: A job requires operator intervention before it can continue.

Recommended Action: This error should never appear as a job return status. Inthe mds and nbrb vxul logs, it indicates that a job should post a request for operatorintervention to the NetBackup device monitor.

NetBackup status code: 2036Message: Drive is in a robotic library that is up

Explanation: Operator has attempted to assign a pending tape mount request toa drive that is in a robot that is up.

Recommended Action: A request for non-robotic media may have caused apending request in the device monitor, and the operator has assigned the requestto a drive that is not a standalone drive. This error is not fatal. The request willpend again in the NetBackup device monitor. Assign the pending mount to astandalone drive or to a drive that is in AVR mode (non-robotic).

NetBackup status code: 2037Message: Drive is not ready

Explanation: The required tape is in a drive, but the drive is not in a ready state.

Recommended Action: This error may occur when a request for non-roboticmedia had caused a pending request in the device monitor, and the operator hasassigned the request to a drive that is not in a ready state. This is not a fatal error,the request will pend again in the NetBackup device monitor. Verify that requiredtape is in the drive it is being assigned to, and that the drive ready light has come

379NetBackup status codes and messagesAbout NetBackup status codes and messages

on. It may take some time for the drive to become ready after the tape has beeninserted. If the drive never goes to a ready state after a tape has been inserted,there may be a problem with the drive.

NetBackup status code: 2038Message: Media loaded in drive is not write-enabled

Explanation: This error may occur when a storage unit request for non-roboticmedia had caused a pending request in the device monitor, and the operator hasinserted media that is not write enabled into the drive.

Recommended Action: This is not a fatal error, the request will pend again inthe NetBackup device monitor. If you are sure it is OK to write on this tape, verifythat the required tape has its write enable switch set to allow write.

NetBackup status code: 2039Message: SCSI reservation conflict detected

Explanation: The NetBackup bptm component was unable to read or write a tapedrive because another job unexpectedly holds a SCSI reservation for the drive.

Recommended Action: This error should never occur at job resource allocationtime, but may occur during i/o for a tape job. The verbose bptm logs on the mediaserver may be useful in understanding the problem.

NetBackup status code: 2040Message: Maximum job count has been reached for the storage unit

Explanation: Storage cannot be allocated because it would exceed maximum jobcount. The maximum job count is configurable for each storage unit. Multiplecopy jobs may cause this same error, if more copies are targeted for a storage unitthan the storage unit is configured for.

Recommended Action: Target a different storage unit with one of the copies, orincrease the maximum job count for the storage unit.

NetBackup status code: 2041Message: Storage unit is down

Explanation: A disk storage unit has been designated as down and cannot beused.

Recommended Action: Run the bperror -disk command to indicate why thedisk is considered down.

NetBackup status codes and messagesAbout NetBackup status codes and messages

380

NetBackup status code: 2042Message: Density mismatch detected

Explanation: This error is an internal NetBackup error. A job has requested mediawith the wrong density. A mismatch may exist between the image catalog and themedia database.

RecommendedAction: Restore the jobs request tape media by media ID density.If the requested density does not match the configured density for the media, itcannot be allocated.

NetBackup status code: 2043Message: Requested slot is empty

Explanation: Media is not found in the expected slot in the robot.

Recommended Action: The robot may need to be inventoried.

NetBackup status code: 2044Message: Media is assigned to another application

Explanation: Requested media cannot be allocated because it is assigned to anapplication other than NetBackup.

Recommended Action: Verify that media required for the job is assigned toNetBackup.

NetBackup status code: 2045Message: Storage unit is disabled since max job count is less than 1

Explanation: Storage unit cannot be used because its maximium job count is setto 0.

RecommendedAction: Increase the maximum job count (or maximum concurrentdrive count) to a value greater than 0.

NetBackup status code: 2046Message: Media is unmountable

Explanation: Media has been marked as unusable due to mount errors.

RecommendedAction: Clean the drives in the media's robot. Determine whetherany of the media is bad.

381NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 2047Message: Media is write protected

Explanation: The media cannot be used for a write job because it is write protected.

Recommended Action: Make sure that media in the scratch pool is not writeprotected.

NetBackup status code: 2048Message: Media is in use by the ACS robotic library

Explanation: ACS media required by this job is in use on another system.

RecommendedAction: Make sure that the required media is not in use by anotherapplication.

NetBackup status code: 2049Message: Media not found in the ACS robotic library

Explanation: Media needed by this job is in not found in the ACS robotic library.

RecommendedAction: Make sure that the required media is available in the ACSrobot.

For more information, refer to the section on configuring ACSLS robots in theNetBackup Device Configuration Guide.

NetBackup status code: 2050Message: ACS media has an unreadable external label

Explanation: This job needs ACS media that cannot be used because its externallabel or barcode is unreadable.

Recommended Action: Correct the barcode label problem for this media.

For more information, refer to the section on configuring ACSLS robots in theNetBackup Device Configuration Guide.

NetBackup status code: 2051Message: ACS media is not in the drive's domain

Explanation: Media required for this job is in an ACS robot that is not accessible.

RecommendedAction: Verify that the robot that contains the required media isaccessible to a NetBackup media server.

NetBackup status codes and messagesAbout NetBackup status codes and messages

382

For more information, refer to the section on configuring ACSLS robots in theNetBackup Device Configuration Guide.

NetBackup status code: 2052Message: An ACS Library Storage Module (LSM) is offline

Explanation: The required ACS LSM is offline.

Recommended Action: Bring the ACS LSM online.

For more information, refer to the section on configuring ACSLS robots in theNetBackup Device Configuration Guide.

NetBackup status code: 2053Message: Media is in an inaccessible drive

Explanation: The required media is currently loaded in a DOWN or otherwiseinaccessible drive.

RecommendedAction: Locate the media and correct the problem that has causedthe drive or drive path to be down.

NetBackup status code: 2054Message: Media is in a drive that is currently in a DOWN state

Explanation: Required media is currently loaded in a drive that is down.

RecommendedAction: Locate the media and correct the problem that has causedthe drive or drive path to be downed.

NetBackup status code: 2055Message: ACS physical drive is not available

Explanation: The media server cannot load ACS media because a drive is notavailable.

Recommended Action:

NetBackup status code: 2056Message: The file name used for the mount request already exists

Explanation: The tpreq command cannot load this media because the specifiedfile name already exists.

383NetBackup status codes and messagesAbout NetBackup status codes and messages

Recommended Action: Specify a different file name for tpreq, or run thetpunmount command for the media which has been loaded using tpreq with theconflicting file name.

NetBackup status code: 2057Message: The scan host of the drive is not active

Explanation: The scan host for a standalone drive is offline, so the drive cannotbe allocated .

Recommended Action: If the problem persists, restart the NetBackup mediaservers that have paths to this drive.

NetBackup status code: 2058Message: LTID needs to be restarted on media servers before the device can beused

Explanation: A drive cannot be used because an ltid restart is required. Thiserror may occur when configuration changes have been made on a media server,but ltid has not been subsequently restarted.

Recommended Action: When the media server is not in a busy state, stop andrestart ltid on that media server.

NetBackup status code: 2059Message: The robotic library is not available

Explanation: The robot required for a drive cannot be found in the nbemmdatabase.

Recommended Action: Verify that the robot required by jobs is properlyconfigured. If the error persists, the following logs may be useful in understandingthe problem : The mds unified logging files (OID 143) from the master server atdebug level 2.

NetBackup status code: 2060Message: Media needs to be rewound or unmounted from a drive

Explanation: The NetBackup mds component uses this error internally to informthe resource broker that a tape needs to be unloaded. It should never appear as ajob error status.

NetBackup status codes and messagesAbout NetBackup status codes and messages

384

Recommended Action:

NetBackup status code: 2061Message: The host is not an active node of a cluster

Explanation: A cluster failover has occurred while a job is running. A job may bewaiting for a span on a media server that has failed over.

Recommended Action: Restart the failed job.

NetBackup status code: 2062Message: Throttled job count has been reached for the storage unit

Explanation: This error will never be returned as a job status.

NetBackup status code: 2063Message: Server is not licensed for the Remote Client Option

Explanation: The media server required for this job does not have the RemoteClient Option enabled. A SAN media server is asked to backup a client that is notalso a media server, or a VMware backup is tried on a SAN media server.

Recommended Action: Back up this client on a media server that is licensed todo so. Verify that the media server has connectivity to the master server whenadding its licenses.

NetBackup status code: 2064Message: Job history indicates that no media is available

Explanation: When a job is run on a media server installed with pre NetBackup6.0 software, there are some situations where the job starts, but media is notavailable for the job. In this case, the master server stops using that storage unitfor a period of time (12 hours), and returns this error for jobs requested the storageunit.

Recommended Action: Make sure media is available for the storage unit. Addmedia if necessary. If media is available, wait 12 hours until the storage unit canbe used again. To make the storage unit immediately usable, run the followingcommand on the master server to release:

Recommended Action: nbrbutil -releaseAllocHolds

NetBackup status code: 2065Message: Job history indicates that no drive is available

385NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: When a job is run on a media server installed with pre NetBackup6.0 software, there are some situations where the job starts, but the drivesdesignated for the job are busy or otherwise unavailable, causing the job to fail.In this case, the NetBackup master server stops using that drive for a period oftime (several minutes), and returns this error for jobs requesting that drive.

RecommendedAction: Make sure all of the drives in the storage unit are up andavailable for use. Clean all drives that need cleaning.

NetBackup status code: 2066Message: Disk pool not found

Explanation: A job has been targeted for a disk pool that does not exist in thenbemm database.

RecommendedAction: Verify that the storage unit used by this job is configuredfor use with a properly configured disk pool.

NetBackup status code: 2067Message: Disk volume not found

Explanation: A read job requires a disk volume that does not exist in the nbemmdatabase. Or a write job is configured for a disk pool with no configured volumes.

RecommendedAction: Verify that the disk storage used by this job is configuredfor use with a disk pool that has volumes configured. For a read job, verify thatthe volume required for reading exists in the nbemm database.

NetBackup status code: 2068Message: Disk volume mount point not found

Explanation: A disk volume is not configured with a mount point or not completelyconfigured in the nbemm database.

RecommendedAction: Verify that the configuration is correct for the disk groupand for the disk volumes in the disk group.

NetBackup status code: 2069Message: Disk volume mount point record insert failed

Explanation: A database updata has failed while trying to allocate a disk job.

RecommendedAction: This error is internal. If the problem persists, please callNetBackup support for resolution. Check the following logs to help identify theproblem:

NetBackup status codes and messagesAbout NetBackup status codes and messages

386

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2070Message: The specified mount path will not fit in the allocated space

Explanation: A disk volume mount point path is larger than the allowed maximum.

Recommended Action: This error is internal. If the problem persists, please callNetBackup support for resolution. Check the following logs to help identify theproblem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2071Message: Unable to find any storage servers for the request

Explanation: NetBackup was unable to find a storage server for this disk job.

RecommendedAction: Verify that storage servers serving the disk group requiredby the job are configured and enabled. Verify that they are in an UP state.

NetBackup status code: 2072Message: Invalid operation on static mount point

Explanation: An incorrectly configured mount point has been found for a diskvolume.

Recommended Action: This error is internal. If the problem persists, please callNetBackup support for resolution. Check the following logs to help identify theproblem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

387NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 2073Message: Disk pool is down

Explanation: Required disk pool cannot be used because it is in a DOWN state.

RecommendedAction: Run the bperror -disk command to determine why thedisk pool was put into a DOWN state. Correct the problem, and use thenbdevconfigcommand to return the disk pool to an UP state.

NetBackup status code: 2074Message: Disk volume is down

Explanation: Required disk volume cannot be used because it is in a DOWN state.

RecommendedAction: You may be able to see why the disk volume was put intoa DOWN state by running 'bperror -disk'. Correct the problem, and use nbdevconfigto return the disk volume to an UP state.

NetBackup status code: 2075Message: Fibre Transport resources are not available

Explanation: A job is configured to require Fibre Transport for this SAN client,but no available Fibre Transport connection exists.

Recommended Action: Configure the job to switch to LAN transport if FibreTransport is not available. Verify that the job type being run is compatible withFibre Transport. Using nbdevquery, verify that the Disk Pool being requested isenbaled for use with Fibre Transport. Verify that there are Fibre Transportconnections that are up between the client and media server required for the job.Check the following logs to help identify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2076Message: DSM returned an unexpected error

Explanation: The Disk Service Manager component of NetBackup has returnedan unexpected error.

Recommended Action: This error is internal. If the problem persists, please callNetBackup support for resolution. Check the following logs to help identify theproblem:

NetBackup status codes and messagesAbout NetBackup status codes and messages

388

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2077Message: DSM has already mounted the volume

Explanation: Mount of a SharedDisk volume (NetBackup 6.5 media servers only)has failed because it is already mounted.

RecommendedAction: This error is internal. If the problem persists, please callNetBackup support for resolution. Check the following logs to help identify theproblem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2078Message: The maximum number of mounts for the disk volume have beenexceeded

Explanation: A disk volume cannot be used by a job because it is mounted by toomany other users.

RecommendedAction: This error is internal. If the problem persists, please callNetBackup support for resolution. Check the following logs to help identify theproblem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2079Message: DSM has detected that an invalid filesystem is mounted on the volume

Explanation: NetBackup did not find the file system it expected on a disk volume.

Recommended Action: Verify that disk volumes and their associated mountpoints that NetBackup uses, are not being used by other applications.

389NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 2080Message: Disk volume has no max writers count

Explanation: Disk volume is not properly configured for a usable number ofmountpoints.

RecommendedAction: Verify proper disk configuration using nbdevquery. Thiserror is internal. If the problem persists, please call NetBackup support forresolution. Check the following logs to help identify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2081Message: Disk volume has no max readers count

Explanation: Disk volume is not properly configured for a usable number ofmountpoints.

RecommendedAction: Verify proper disk configuration using nbdevquery. Thiserror is internal. If the problem persists, please call NetBackup support forresolution. Check the following logs to help identify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2082Message: The drive needs to be marked as available

Explanation: Drive cannot be used because it is allocated with loaded media, butMDS has not made it available for use.

RecommendedAction: Run the nbrbutil -dump command on the master serverto show allocations for this job. If the problem persists, run the nbrbutil

-releaseMDS command to release the allocation for the drive so it can be used.

NetBackup status code: 2083Message: The media affinity group is not defined in EMM

NetBackup status codes and messagesAbout NetBackup status codes and messages

390

Explanation: MDS expected to find a group of reservations for this media, butdid not find the expected reservation group.

Recommended Action: This error is internal. If the problem persists, check thefollowing logs to help identify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2084Message: Media affinity group record insert failed

Explanation: MDS could not update reservation group information for this tapemedia.

Recommended Action: This error is internal. If the problem persists, check thefollowing logs to help identify the problem:

■ The mds unified logging files (OID 143) from the master server at debug level2.

■ The nbrb unified logging files (OID 118) from the master server at debug level3.

NetBackup status code: 2085Message: Disk volume is not available

Explanation: The job requires more disk volumes than are currently configured.

RecommendedAction: Ensure that the disk group has disk volumes configured.A multiple copy job cannot target two copies for the same disk volume.

NetBackup status code: 2086Message: Disk volume cannot be used for more than one copy in the same job

Explanation: Not enough eligible disk volumes are configured for this multiplecopy job.

Recommended Action: Use the nbdevquery -listdv command to verify thatthe expected disk volume is configured. For a multiple copy job, ensure that uniqueeligible disk volumes exist for each copy. A multiple copy job cannot target twocopies for the same disk volume.

391NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status code: 2087Message: Media allocation would exceed maximum partially full media limit

Explanation: You cannot run this job because it would exceed configured limitof maximum partially full media.

Recommended Action: This error may occur with a multiple copy job or aduplication job. If the problem persists, you may need to increase maximumpartially full media setting on the disk pool.

NetBackup status code: 2088Message: Cleaning media is not available

Explanation: You cannot run a cleaning job because no cleaning media isconfigured for the drive.

RecommendedAction: Add a cleaning volume to the robot containing the drive.

NetBackup status code: 2089Message: FT client is not running

Explanation: This job requires Fibre Transport, but the Fibre Transport client isnot running on the client required for this job.

Recommended Action: Do one or more of the following:

■ Verify that the Private Branch Exchange (PBX) service is installed and running.Run the bpps -x command to ensure that pbx_exchange is listed in theprocesses that are running.

■ Verify that the client is configured as a SAN Client. Run the bpclntcmd

-sanclient command to return the current state of the SAN Client. A responseof 0 (zero) indicates that SAN Client is not configured. Rerun the command asbpclntcmd -sanclient 1.

■ Verify that the client is not also a media server, master server, or EMM server.The SAN Client process runs only on a NetBackup client.

■ Verify that a valid license for the SAN Client feature resides on the masterserver. SAN Client is a separately licensed feature which requires a key called"SAN Client" on the master server.

■ Verify that no server entries for the SAN Client exist on the NetBackup masterserver. Remove any SERVER=clientname entry in the master server for theSAN Client. If the master server has the SAN Client listed also as a server, itmay shut down the SAN Client.

NetBackup status codes and messagesAbout NetBackup status codes and messages

392

■ Restart the SAN Client service. The SAN Client restarts when the server reboots,but does not automatically restart after you run the bpclntcmd command. Tostart the SAN Client service, run the client startup script or use the ServiceManager in Windows.

For further information, see the Troubleshooting chapter of the NetBackup SANClient and Fibre Transport Guide.

NetBackup status code: 2090Message: FT client has no devices configured

Explanation: This job requires Fibre Transport, but Fibre Transport devices arenot configured on the client required for this job.

Recommended Action: Verify that Fibre Transport devices are installed on theclient. For further information, see the Troubleshooting chapter of theNetBackupSAN Client and Fibre Transport Guide.

NetBackup status code: 2091Message: FT client devices are offline

Explanation: This job requires Fibre Transport, but all Fibre Transport devicesare offline on the client required for this job.

Recommended Action: Do one or more of the following:

■ Verify that the Private Branch Exchange (PBX) service is installed and running.Run the bpps -x command to ensure that pbx_exchange is listed in theprocesses that are running.

■ Verify that the client is configured as a SAN Client. Run the bpclntcmd

-sanclient command to return the current state of the SAN Client. A responseof 0 (zero) indicates that SAN Client is not configured. Rerun the command asbpclntcmd -sanclient 1.

■ Verify that the client is not also a media server, master server, or EMM server.The SAN Client process runs only on a NetBackup client.

■ Verify that a valid license for the SAN Client feature resides on the masterserver. SAN Client is a separately licensed feature which requires a key called"SAN Client" on the master server.

■ Verify that no server entries for the SAN Client exist on the NetBackup masterserver. Remove any SERVER=clientname entry in the master server for theSAN Client. If the master server has the SAN Client listed also as a server, itmay shut down the SAN Client.

393NetBackup status codes and messagesAbout NetBackup status codes and messages

■ Restart the SAN Client service. The SAN Client restarts when the server reboots,but does not automatically restart after you run the bpclntcmd command. Tostart the SAN Client service, run the client startup script or use the ServiceManager in Windows.

For further information, see the Troubleshooting chapter of the NetBackup SANClient and Fibre Transport Guide.

NetBackup status code: 2092Message: FT server devices for client are offline

Explanation: This job requires Fibre Transport, but all Fibre Transport devicesare offline on the media server reqruied for this job.

Recommended Action: Do one of the following:

■ Verify that marked QLogic Target ports exist in the server The nbftsrvr andnbfdrv64 processes exit if the system has no ports available for Target Modeuse.

■ Verify that a valid license for the SAN Client feature resides on the masterserver. SAN Client is a separately licensed feature which requires a key called"SAN Client" on the master server. The Fibre Transport server performs alicense check during startup.

■ Determine if a reboot is required for the installation of the Fibre Transportserver. Solaris installations require that you reboot the media server after youinstall Fibre Transport to load the Fibre Transport drivers on the marked targetports. In addition, reboot the Linux servers if you choose to not unload theexisting QLogic drivers during the installation of Fibre Transport.

For further information, see the Troubleshooting chapter of the NetBackup SANClient and Fibre Transport Guide.

NetBackup status code: 2093Message: No FT servers for this client are running

Explanation: This job requires Fibre Transport, but no Fibre Transport devicesare configured with connectivity to the media server required for this job.

Recommended Action: Do one of the following:

■ Verify that marked QLogic Target ports exist in the server The nbftsrvr andnbfdrv64 processes exit if the system has no ports available for Target Modeuse.

■ Verify that a valid license for the SAN Client feature resides on the masterserver. SAN Client is a separately licensed feature which requires a key called

NetBackup status codes and messagesAbout NetBackup status codes and messages

394

"SAN Client" on the master server. The Fibre Transport server performs alicense check during startup.

■ Determine if a reboot is required for the installation of the Fibre Transportserver. Solaris installations require that you reboot the media server after youinstall Fibre Transport to load the Fibre Transport drivers on the marked targetports. In addition, reboot the Linux servers if you choose to not unload theexisting QLogic drivers during the installation of Fibre Transport.

Recommended Action: For further information, please refer to the NetBackupSAN Client and Fibre Transport Troubleshooting Guide.

NetBackup status code: 2094Message: STU cannot run Lifecycle backups

Explanation: The storage lifecycle job cannot run because the targeted disk poolis not enabled for Storage Lifecycles.

Recommended Action: Run the nbdevquery -listdg command to check theconfiguration of the disk pool. If the LifeCycle attribute is not enabled for the diskpool, run the nbdevconfig -changedp -setattribute command to enable it.

NetBackup status code: 2095Message: STU cannot run VMWare backup

Explanation: The media server configured for this job's storage unit cannot runVMWare backups.

Recommended Action: To run a VMWare backup, a media server must runNetBackup Release 6.5 or greater. Verify that this is so, or configure the backupfor a media server that runs NetBackup Release 6.5 or later.

NetBackup status code: 2096Message: NDMP operation does not support multiple inline copies

Explanation: The backup cannot run because it is an NDMP policy and isconfigured for multiple copies.

RecommendedAction: NetBackup cannot make multiple copies of NDMP policies.Configure the backup for a single storage unit destination.

NetBackup status code: 2097Message: Storage Unit group does not exist in EMM configuration

395NetBackup status codes and messagesAbout NetBackup status codes and messages

Explanation: You cannot run this job because it is configured to use a storageunit group that does not exist in the NetBackup configuration.

Recommended Action: Reconfigure the policy to use a storage unit or storageunit group that exists in the configuration.

NetBackup status code: 2098Message: Media pool is not eligible for this job

Explanation: This job is configured to use a pool that does not exist in theNetBackup configuration.

Recommended Action: Change the configured media pool for the job to use apool that is configured, or create the required media pool. Make sure that themedia pool you have configured for the job is not a scratch pool.

NetBackup status code: 2099Message: Required drive or drive path is not configured

Explanation: This job requires a drive that does not exist in the NetBackupconfiguration.

Recommended Action: Run the vmoprcmd command to verify the driveconfiguration. Configure the drives that are necessary for the media type that isbeing used.

NetBackup status code: 2100Message: Maximum number of mounts has been exceeded for tape media

Explanation: The job cannot run because the required media has exceededconfigured maximum mounts.

Recommended Action: Increase the maximum allowed mounts for the media.You may need to retire this media if it has exceeded the maximum number ofmounts you have configured.

NetBackup status code: 2101Message: Media server not found in EMM database

Explanation: The media server required for this job does not exist in theNetBackup database.

Recommended Action: For restore from tape, the media server originally usedto write the image is used for restore. If this media server does not exist in the

NetBackup status codes and messagesAbout NetBackup status codes and messages

396

NetBackup database, you may use the Force Media Server Restore option to forceNetBackup to replace the missing media server with a new media server.

NetBackup status code: 2102Message: Storage unit does not support spanning

Explanation: A disk job has requested a span for a disk type that does not supportspanning.

Recommended Action: Some disk types do not support spanning. Run thenbdevconfig -listdg command to determine if a disk group supports spanning.If this error persists, ensure that enough space is available on your disk storageunits for the new jobs that are running.

NetBackup status code: 2103Message: Media server mismatch

Explanation: This error may occur when a multiple copy job is configured forstorage units that have no common media server.

Recommended Action: All copies of a multiple copy job must run on the samemedia server. Configure storage units that have drive paths or disk access froma common media server.

NetBackup status code: 2104Message: Storage units are not available

Explanation: This error may occur for multiple copy jobs configured so that nopossible storage unit combination can be used.

Recommended Action: Verify that all criteria in met for the policy with thestorage units that are configured.

NetBackup MessagesThis section lists the NetBackup error messages alphabetically. The status codefor each message is listed in the right column of the table. Refer to the previouslist of status codes for explanations and recommended actions.

Table 5-1 lists the NetBackup error messages alphabetically.

397NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes

Status codeError message

110/usr/openv/netbackup/bp.conf not found

232a protocol error has occurred

206access to server backup restore manager denied

59access to the client was not allowed

2050ACS media has an unreadable external label

2051ACS media is not in the drive's domain

2055ACS physical drive is not available

78afs/dfs command failed

2008all compatible drive paths are down

2009all compatible drive paths are down but media is available

351all configured vault steps failed

297all volumes are not available to eject

2023allocation identifier is not known to EMM

10allocation failed

2021allocation record insert failed

2025allocation request delete failed

2024allocation request update failed

2022allocation status record insert failed

2026allocation status request delete failed

2052an ACS Library Storage Module (LSM) is offline

70an entry in the filelist expanded to too many characters

600an exception condition occurred

252an extended error status has been encountered, check detailed status

9an extension package is needed but was not installed

223an invalid entry was encountered

NetBackup status codes and messagesAbout NetBackup status codes and messages

398

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

125another NB database backup is already in progress

4archive file removal failed

275a session is already running for this vault

660a synthetic backup request for media resources failed

160authentication failed

151Backup Exec operation failed

53backup restore manager failed to read the file list

166backups are not allowed to span media

669bpcoord startup validation failure

513bpjava-msvc: the client is not compatible with this server versionserver_version

73bpstart_notify failed

25cannot connect on socket

282cannot connect to nbvault server

613cannot connect to read media server

205cannot connect to server backup restore manager

505Can not connect to the NB-Java authentication service on theconfigured port - configured_port_number. Check the log file for moredetails.

525Can not connect to the NB-Java authentication service via VNETD onhost on port vnetd_configured_port_number. Check the log file formore details.

506Can not connect to the NB-Java user service on port port_number.Check the log file for more details.

517Can not connect to the NB-Java user service via VNETD on (host) orport (configured_port_number)

289cannot consolidate reports of sessions from container and slot-basedvaults

399NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

509Can not execute program

120cannot find configuration database record for requested NB databasebackup

167cannot find requested volume pool in EMM database

323cannot find robot in vault configuration file

266cannot find robot, vault, or profile in the vault configuration

267cannot find the local host name

322cannot find vault in vault configuration file

146cannot get a bound socket

35cannot make required directory

342cannot modify - stale view

168cannot overwrite media, data on it is protected

176cannot perform specified media import operation

94cannot position to correct image

173cannot read backup header, media may be corrupted

172cannot read media header, may not be NetBackup media or is corrupted

603\cannot register handler for accepting new connections

612cannot send extents to bpsynth

602cannot set non blocking mode on the listen socket

614cannot start reader on the media server

508Can not write file

58can’t connect to client

27child process killed by signal

2088Cleaning media is not available

67client backup failed to read the file list

NetBackup status codes and messagesAbout NetBackup status codes and messages

400

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

66client backup failed to receive the CONTINUE BACKUP message

195client backup was not attempted

196client backup was not attempted because backup window closed

60client cannot read the mount table

57client connection refused

49client did not start

48client hostname could not be found

135client is not validated to perform the requested operation

131client is not validated to use the server

39client name mismatch

50client process aborted

76client timed out reading file

75client timed out waiting for bpend_notify to complete

74client timed out waiting for bpstart_notify to complete

65client timed out waiting for the continue message from the mediamanager

68client timed out waiting for the file list

56client’s network is unreachable

26client/server handshaking failed

234communication interrupted

204connection refused by server backup restore manager

622connection to the peer process does not exist

321container cannot hold any media from the specified robot

317container database close operation failed

318container database lock operation failed

401NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

319container database open operation failed

314container database truncate operation failed

313container does not exist in container database

316container_id is not unique in container database

221continue

177could not deassign media due to Media Manager error

38could not get group information

30could not get passwd information

32could not set group id for process

31could not set user id for process

148daemon fork failed

145daemon is already running

625data marshalling error

626data un-marshalling error

220database system error

179density is incorrect for the media id

2042density mismatch detected

155disk is full

2073Disk pool is down

2066Disk pool not found

129Disk storage unit is full

2086Disk volume cannot be used for more than one copy in the same job

2081Disk volume has no max readers count

2080Disk volume has no max writers count

2074Disk volume is down

NetBackup status codes and messagesAbout NetBackup status codes and messages

402

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

2085Disk volume is not available

2068Disk volume mount point not found

2069Disk volume mount point record insert failed

2067Disk volume not found

222done

2004drive is already allocated

2036drive is in a robotic library that is up

2003drive is not allocated

2037drive is not ready

2077DSM has already mounted the volume

2079DSM has detected that an invalid filesystem is mounted on the volume

2076DSM returned an unexpected error

642duplicate backup images were found

346duplicate MAP

813duplicate reference string specified

113EC_badop (there is no explanation for this status code)

115EC_end (there is no explanation for this status code)

114EC_error (there is no explanation for this status code)

295eject process could not obtain information about the robot

292eject process failed to start

307eject process has already been run for the requested vault session

293eject process has been aborted

279eject process is complete

2029EMM database is inconsistent

610end point terminated with an error

403NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

209error creating or getting message queue

302error encountered attempting backup of catalog (multiple tape catalogbackup)

303error encountered executing Media Manager command

332error getting information from EMM database

333error getting information from media manager command line

207error obtaining date of last backup for client

103error occurred during initialization, check configuration file

284error(s) occurred during vault report distribution

210error receiving information on message queue

2013error record insert failed

98error requesting media (tpreq)

212error sending information on message queue

283error(s) occurred during vault report generation

161Evaluation software has expired. See www.symantec.com for orderinginformation

229events out of sequence - image inconsistency

623execution of a command in a forked process failed

272execution of a vault notify script failed

77execution of the specified system command returned a nonzero status

644extent directive contained an unknown media id

158failed accessing daemon lock file

315failed appending to container database

102failed closing mail pipe

101failed opening mail pipe

218failed reading policy database information

NetBackup status codes and messagesAbout NetBackup status codes and messages

404

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

215failed reading global config database information

216failed reading retention database information

217failed reading storage unit database information

812failed to communicate with resource broker

811failed to communicate with resource requester

257failed to get job data

260failed to send signal

36failed trying to allocate memory

29failed trying to exec a command

28failed trying to fork a process

34failed waiting for child process

33failed while trying to send mail

335failure occurred while suspending media for eject

336failure occurred while updating session information

337failure occurred while updating the eject.mstr file

91fatal NB media database error

2075Fibre Transport resources are not available

510File already exists: file_name

15file close failed

142file does not exist

12file open failed

141file path specified is not absolute

105file pathname exceeds the maximum length allowed

13file read failed

14file write failed

405NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

190found no images or media matching the selection criteria

2091FT client devices are offline

2090FT client has no devices configured

2089FT client is not running

2092FT server devices for client are offline

19getservbyname failed

201handshaking failed with server backup restore manager

47host is unreachable

663image does not have a fragment map

235inadequate buffer space

349incorrect catalog backup policy

504Incorrect password

162Incorrect server platform identifier

350incorrect vault catalog backup schedule

628insufficient data received

2030insufficient disk space or high water mark would be exceeded

615internal error 615

616internal error 616

618internal error 618

619internal error 619

620internal error 620

654internal error 654

512Internal error - a bad status packet was returned by NB-Javaapplication server that did not contain an exit status code

638invalid arguments specified

NetBackup status codes and messagesAbout NetBackup status codes and messages

406

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

20invalid command parameter

143invalid command protocol

144invalid command usage

312invalid container database entry

331invalid container description

328invalid container id

330invalid database host

324invalid data found in retention map file for duplication

109invalid date specified

109

104invalid file pathname

106invalid file pathname found, cannot process request

69invalid filelist specification

273 and 805invalid job id

640invalid media type specified in the storage unit

519Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value:(option_value)

2072Invalid operation on static mount point

329invalid recall status

133invalid request

2002invalid STU identifier type

503invalid username

520invalid value for NB-Java configuration option (option_name):(option_value)

311Iron Mountain report is already created for this session

801JM internal error

407NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

802JM internal protocol error

803JM terminating

2065job history indicates that no drive is available

2064job history indicates that no media is available

2010job type is invalid

159licensed use has been exceeded

256logic error encountered

2058LTID needs to be restarted on media servers before the device can beused

149master server request failed

2040maximum job count has been reached for the storage unit

2100Maximum number of mounts has been exceeded for tape media

2005MDS has received an invalid message from a media server

2084Media affinity group record insert failed

2087Media allocation would exceed maximum partially full media limit

163media block size changed prior to resume

87media close error

2033media has been misplaced

2012media has conflicts in EMM

169media id is either expired or will exceed maximum mounts

178media id is not in NetBackup volume pool

171media id must be 6 or less characters

95media id is not assigned to this host in the EMM database

2044media is assigned to another application

2016media is assigned to another server

NetBackup status codes and messagesAbout NetBackup status codes and messages

408

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

2015media is expired

2054media is in a drive that is currently in a DOWN state

2019media is in a drive that is not configured on local system

2053media is in an inaccessible drive

2032media is in use according to EMM

2048media is in use by the ACS robotic library

2014media is not assigned

2031media is not defined in EMM

2028media is reserved

2046media is unmountable

2047media is write protected

2038media loaded in drive is not write-enabled

80Media Manager device daemon (ltid) is not active

81Media Manager volume daemon (vmd) is not active

92media manager detected image that was not in tar format

93media manager found wrong tape in drive

82media manager killed by signal

90media manager received no data for backup image

174media manager - system error occurred

2060media needs to be rewound or unmounted from a drive

2017media needs to be unmounted from a drive

2049media not found in the ACS robotic library

83media open error

2098Media pool is not eligible for this job

86media position error

409NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

85media read error

2027media server is not active

2103Media server mismatch

2101Media server not found in EMM database

84media write error

409Member already exists in server group

407Member’s NetBackup version not compatible with Server Group

405Member's server type not compatible with Server Group

305multiple profiles exist

124NB database backup failed, a path was not found or is inaccessible

126NB database backup header is too large, too many paths specified

128NB database recovery failed, a process has encountered an exceptionalcondition

165NB image database contains no image fragments for requested backupid/copy number

511NB-Java application server interface error: Java exception

523NB-Java application server protocol error

514NB-Java: bpjava-msvc is not compatible with this application version(application_version). You may try login to a different NetBackup hostor exit the application. The remote NetBackup host will have to beconfigured with the same version of NetBackup as the host you startedthe application on.

521NB-Java Configuration file (file_name) does not exist

522NB-Java Configuration file (file_name) is not readable due to thefollowing error: (message)

99NDMP backup failure

2006NDMP credentials are not defined in EMM

2096NDMP operation does not support multiple inline copies

NetBackup status codes and messagesAbout NetBackup status codes and messages

410

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

40network connection broken

41network connection timed out

42network read failed

44network write failed

198no active policies contain schedules of the requested type for thisclient

246no active policies in the configuration database are of the correctclient type

502No authorization entry exists in the auth.conf file for usernameusername. None of the NB-Java applications are available to you.

823no BRMComm to join

611no connection to reader

2001no drives are available for this job

617no drives available to start the reader process

634no drives available to start the writer process

227no entity was found

112no files specified in the file list

2093No FT servers for this client are running

308no images duplicated

607no images were found to synthesize

191no images were successfully processed

327no media ejected for the specified vault session

121no media is defined for the requested NB database backup

629no message was received from bptm

518No ports available in range (port_number) through (port_number) perthe NBJAVA_CLIENT_PORT_WINDOW configuration option

274no profile was specified

411NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

606no robot on which the media can be read

240no schedules of the correct type exist in this policy

213no storage units available for use

604no target storage unit specified for the new job

655no target storage unit was specified via command line

269no vault session id was found

71none of the files in the file list exist

2none of the requested files were backed up

175not all requested files were restored

2018number of cleanings is invalid

291number of media has exceeded the capacity of MAP

290one or more errors detected during consolidated eject processing

199operation not allowed during this time period

37operation requested by an invalid server

242operation would cause an illegal duplication

55permission denied by client during rcmd

18pipe close failed

668pipe fgets call from bpcoord failed

233premature eof encountered

89problems encountered during setup of shared memory

296process called but nothing to do

63process was killed by a signal

345profile already exists

671query for list of component images failed

903RB communication error

NetBackup status codes and messagesAbout NetBackup status codes and messages

412

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

912RB disk volume mount failed

915RB disk volume mount must retry

901RB internal error

902RB invalid argument

904RB max reallocation tries exceeded

914RB media reservation not found

905RB media server mismatch

906RB operator denied mount request

907RB user cancelled resource request

908RB was reset

636read from input socket failed

609reader failed

631received an error from bptm request to suspend media

632received an error from bptm request to un-suspend media

605received error notification for the job

309report requested without eject being run

45request attempted on a non reserved port

2035request needs to pend

97requested media id is in use, cannot process request

2043requested slot is empty

2099Required drive or drive path is not configured

147required or specified copy was not found

152required value not set

800resource request failed

916resource request timed out

413NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

900retry nbrb request later

2034Retry the allocation request later

343robot already exists

2020robotic library is down on server

231schedule windows overlap

200scheduler found no backups due to run

2039SCSI reservation conflict detected

670send buffer is full

203server backup restore manager’s network is unreachable

403Server Group Active State is not valid

401Server Group Already Exists

402Server Group Already Exists with a different type

404Server Group does not exist

408Server Group is in use

400Server Group Type is Invalid

2063server is not licensed for the Remote Client Option

153server is not the master server

254server name not found in the bp.conf file

46server not allowed access

111SERVER was not specified in /usr/openv/netbackup/bp.conf

263Session id assignment failed

265Session id file is empty or corrupt

156Snapshot error encountered

22socket close failed

NetBackup status codes and messagesAbout NetBackup status codes and messages

414

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

507Socket connection to the NB-Java user service has been broken. Pleaseretry your last operation. Check the log file for more details.

21socket open failed

23socket read failed

24socket write failed

122specified device path does not exist

123specified disk path is not a directory

326specified file contains no valid entry

127specified media or path does not contain a valid NB database backupheader

639specified policy does not exist

304specified profile not found

348specified report does not exist

640specified schedule was not found

154storage unit characteristics mismatched to request

2097Storage Unit group does not exist in EMM configuration

2045storage unit is disabled since max job count is less than 1

2041Storage unit is down

2007Storage unit is not compatible with requesting job

608storage unit query failed

2104Storage units are not available

2094STU cannot run Lifecycle backups

2095STU cannot run VMWare backup

157suspend requested by administrator

11system call failed

130system error occurred

415NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

100system error occurred while processing user command

185tar did not find all the files to be restored

184tar had an unexpected error

183tar received an invalid archive

181tar received an invalid argument

182tar received an invalid file name

186tar received no data

180tar was successful

150termination requested by administrator

665termination requested by bpcoord

225text exceeded allowed length

7the archive failed to back up the requested files

6the backup failed to back up the requested files

253the catalog image .f file has been archived

243the client is not in the configuration

72the client type is incorrect in the configuration database

238the database contains conflicting or erroneous entries

2082The drive needs to be marked as available

226the entity already exists

249the file list is incomplete

2056the file name used for the mount request already exists

2061The host is not an active node of a cluster

250the image was not created with TIR information

298the library is not ready to eject volumes

406the machine specified is not a member of the server group specified

NetBackup status codes and messagesAbout NetBackup status codes and messages

416

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

194the maximum number of jobs per client is set to 0

2078The maximum number of mounts for the disk volume have beenexceeded

2083The media affinity group is not defined in EMM

2011the media server reported a system error

1the requested operation was partially successful

0the requested operation was successfully completed

219the required storage unit is unavailable

5the restore failed to recover the requested files

2059the robotic library is not available

2057the scan host of the drive is not active

189the server is not allowed to write to the client’s filesystems

320the specified container is not empty

2070the specified mount path will not fit in the allocated space

230the specified policy does not exist in the configuration database

247the specified policy is not active

245the specified policy is not of the correct client type

236the specified client does not exist in an active policy within theconfiguration database

239the specified client does not exist in the specified policy

237the specified schedule does not exist in an active policy in theconfiguration database

197the specified schedule does not exist in the specified policy

241the specified schedule is the wrong type for this request

251the TIR information is zero length

268the vault session directory is either missing or inaccessible

417NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

248there are no active policies in the configuration database

280there are no volumes to eject

299there is no available MAP for ejecting

224there was a conflicting specification

170third-party copy backup failure

806this mpx group is unjoinable

2062throttled job count has been reached for the storage unit

54timed out connecting to client

202timed out connecting to server backup restore manager

51timed out waiting for database information

52timed out waiting for media manager to mount volume

64timed out waiting for the client backup to start

136tir info was pruned from the image file

657unable to accept connection from the reader

658unable to accept connection from the writer

96 and 2000unable to allocate new media for backup, storage unit has noneavailable

278unable to collect pre eject information from the API

621unable to connect to bpcoord

8unable to determine the status of rbak

2071unable to find any storage servers for the request

325unable to find policy/schedule for image using retention mapping

646unable to get the address of the local listen socket

651unable to issue the database query for policy

652unable to issue the database query for policy information

NetBackup status codes and messagesAbout NetBackup status codes and messages

418

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

633unable to listen and register service via vnetd

285unable to locate vault directory

164unable to mount media because its in a DOWN drive or misplaced

270unable to obtain process id, getpid failed

601unable to open listen socket

667unable to open pipe between bpsynth and bpcoord

228unable to process request

134unable to process request because the server resources are busy

334unable to receive response from robot; robot not ready

635unable to register handle with the reactor

653unable to send a message to bpcoord

659unable to send a message to the writer child process

624unable to send a start command to a reader/writer process on mediaserver

661unable to send exit message to the BPXM reader

650unable to send extent message to bpcoord

648unable to send extent message to BPXM

656unable to send start synth message to bpcoord

645unable to start the writer on the media server

43unexpected message received

643unexpected message received from bpcoord

627unexpected message received from bpsynth

649unexpected message received from BPXM

630unexpected message was received from bptm

114unimplemented error code

419NetBackup status codes and messagesAbout NetBackup status codes and messages

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

16unimplemented feature

662unknown image referenced in the SYNTH CONTEXT message fromBPXM

79unsupported image format for the requested database query

310Updating of Media Manager database failed

140user id was not superuser

132user is not validated to use the server

3valid archive image produced, but no files deleted due to non-fatalproblems

647validation of synthetic image failed

344vault already exists

294vault catalog backup failed

347vault configuration cache not initialized

339vault configuration file format error

259vault configuration file not found

341vault configuration serialization failed

340vault configuration tag not found

281vault core error

306vault duplication partially succeeded

258vault duplication was aborted by administrator request

287vault eject failed

288vault eject partially succeeded

338vault eject timed out

261vault internal error 261

262vault internal error 262

286vault internal error 286

NetBackup status codes and messagesAbout NetBackup status codes and messages

420

Table 5-1 NetBackup error messages and status codes (continued)

Status codeError message

271vault XML version mismatch

301vmchange api_eject command failed

300vmchange eject verify not responding

117VxSS access denied

116VxSS authentication failed

118VxSS authorization failed

193VxSS authentication is requested but not allowed

192VxSS authentication is required but not available

637write on output socket failed

501You are not authorized to use this application

664zero extents in the synthetic image, cannot proceed

421NetBackup status codes and messagesAbout NetBackup status codes and messages

NetBackup status codes and messagesAbout NetBackup status codes and messages

422

Media and devicemanagement status codesand messages

This chapter includes the following topics:

■ About media and device management status codes and messages

■ Media and device management messages

About media and device management status codesand messages

This chapter lists media and device management status codes and messages. Ineach of the following subsections, the status codes are listed in numerical order,with an explanation and a recommended action.

An alphabetical list of all media and device management messages is at the endof this chapter in "Messages." Following each message is a pointer to the sectionin this chapter that contains detailed information about the message.

The Symantec technical support site has a wealth of information that can helpyou solve NetBackup problems.

Visit http://entsupport.symantec.com for comprehensive troubleshooting details.

Using debug logsTo solve many of the error conditions that this chapter describes, set debug loggingto a higher level. Then retry the operation and examine the debug logs.

6Chapter

To set debug logging to a higher level

1 Enable legacy debug logging by creating the necessary directories and folders.

2 Increase the level of verbosity for media and device management processesby adding the VERBOSE option in the vm.conf file. This file is located in/usr/openv/volmgr/ (UNIX and Linux) and install_path\Volmgr\

(Windows).

3 Restart the daemons and services or run the command’s verbose option, ifavailable.

The term media server, as distinct from master server or server, does notapply to the NetBackup Server product. In this case, the media server is themaster server. When you troubleshoot a Server installation, ignore anyreferences to media server. (This does not apply to NetBackup EnterpriseServer.)

Media Manager status codesThese status codes appear in the following: exit status and command output formost media and device management commands, media and device managementuser interfaces, and system or debug logs.

Media Manager status code: 1Message: request completed

Explanation: A requested operation was completed. The operation may have beenone of several related operations for a particular task.

Recommended Action: None.

Media Manager status code: 2Message: system error

Explanation: A system call failed. This status code is used for a generic systemcall failure that does not have its own status code.

■ Check for other error messages in the command or the interface output todetermine which system call failed.See “Using debug logs” on page 423.

■ Check the system application log for error and warning messages.

■ Verify that the system is not running out of virtual memory. If virtual memoryis the problem, shut down unused applications or increase the amount ofvirtual memory.

Media and device management status codes and messagesAbout media and device management status codes and messages

424

To increase virtual memory on Windows, do the following in the orderpresented:

■ Display the Control Panel.

■ Double-click System.

■ On the Performance tab, set Virtual Memory to a higher value.

■ Verify that all product binaries are properly installed.

■ Verify that no unexpected media and device management processes are inoperation by running vmps. Some processes are expected to continue running.Others that continue to run can indicate a more serious problem, such as ahung system call.

Media Manager status code: 3Message: user id was not superuser

Explanation: A user or process that did not have root privileges (on UNIX andLinux) or administrator privileges (on Windows) started the process.

RecommendedAction: If appropriate, give the user or the process administratorprivileges (on Windows) or root privileges (on UNIX and Linux) and retry theoperation.

Media Manager status code: 4Message: invalid command usage

Explanation: A media and device management command was run with improperoptions, or an incompatibility between components or versions of the productexists.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the usage statement for expected usage and compare with the parametersbeing sent to start the new process.

■ Verify that all media and device management binaries are at a compatibleversion level.

Media Manager status code: 5Message: daemon resources are busy

425Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: A requested operation cannot be processed because resources werebusy.

Recommended Action: Check the status of any resources that the requestedoperation uses. On a robotic inventory request, verify that the inventory operationcompletes within a reasonable time.

Media Manager status code: 6Message: invalid protocol request

Explanation: An invalid request was sent to a robotic process or operator requestprocess.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Identify the target components (for example, vmd, nbemm, and robotic processeson local or remote hosts). Then verify that all media and device managementbinaries are at compatible version level.

Media Manager status code: 7Message: daemon terminated

Explanation: The process is inactive or terminates (or has terminated) from thefollowing: an event or signal or as a direct result of a request from an authorizeduser or process.

Recommended Action: If the targeted product component is needed but hasterminated, restart the daemons or services on the targeted host.

Media Manager status code: 8Message: invalid media ID

Explanation: When a process performed a media-related operation, it encounteredan empty or an incorrectly formatted media identifier. Or a media ID that waspassed to it cannot be operated on as requested.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the media ID, where requested, is not blank.

Media and device management status codes and messagesAbout media and device management status codes and messages

426

■ Ensure that the specified media IDs contain valid characters only: alphanumericcharacters, the period (.), the plus sign (+), and the underscore (_). A hyphen(-) is also a valid character when not the first character in the media ID.

■ If media are specified to be ejected from a library, ensure the following: theyexist in the EMM database and are associated with the correct robot number.

■ Ensure that the media ID is from 1 to 6 characters in length.

■ Ensure that a valid media and seed were specified.

■ If the operation is an inventory request for an ACS robot, use the robtest

utility to verify the following: the ACS interface returns cleaning media IDsboth in the query volume list and in the query cleaning volume list.

Media Manager status code: 9Message: invalid media type

Explanation: A process that performed a media-related operation encounteredan unknown, missing, or incompatible media type specifier.

■ If you run a robot inventory on a robot of type ACS, TLH, or TLM, ensure thefollowing: the installed version of NetBackup supports and recognizes thevendor media type that the robot control software returns.

■ If using a command line interface directly, verify that a valid media type hasbeen passed, according to vmadd(1m) command line documentation.

■ Ensure that an operation valid only for cleaning media has not been requestedon a media ID that does not correspond to cleaning tape.

■ Ensure that the media type in all bar code rules is a valid media type or theordinal zero (0), to represent the default media type.

Media Manager status code: 10Message: invalid barcode

Explanation: When a process performed a media-related operation, it encounteredan unknown, missing, or incompatible bar code.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the bar code, where requested, is not blank.

■ Ensure that the specified bar codes contain valid characters only: alphanumericcharacters, and the period (.), plus sign (+), and underscore (_). A hyphen (-) isalso a valid character when not the first character in the media ID.

427Media and device management status codes and messagesAbout media and device management status codes and messages

■ Ensure that the number of characters in the bar code does not exceed themaximum that is allowed for the robot type.

■ Ensure that the bar code tag in all bar code rules is a subset of a valid, supportedbar code format.

Media Manager status code: 11Message: invalid description

Explanation: The volume description exceeds 25 ASCII characters in length, orcontains unprintable characters.

RecommendedAction: When you add or change a volume record or bar code rulerecord, ensure that the description field contains the following: no more than 25ASCII characters that can be printed.

Media Manager status code: 12Message: invalid robot type

Explanation: A requested operation encountered a case where a specified robottype or a volume’s robot type is different. It differs from the type of robot that isrequired to perform the operation in the current configuration.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify a robot type that supports the volume’s media type.

■ Check the EMM database and ensure that the specified robot type agrees withthe type for all volumes having the specified robot number.

■ If a robot type is required for the requested operation, ensure that a robot typehas been specified.

Media Manager status code: 13Message: invalid robot number

Explanation: The robot number was not specified or was not within the allowablerange.

■ Specify a robot number in the range of 0 to 32767.

■ If you run vmphyinv, the global device database may not be updated, or thespecified robot number may not be configured.

Media and device management status codes and messagesAbout media and device management status codes and messages

428

Media Manager status code: 14Message: invalid robot host

A requested operation encountered a case where the following is true of the robotcontrol host:

■ It is not specified.

■ It is not valid for the given robot type.

■ It is not in an acceptable format.

■ It exceeds the allowed length of a robot control host name.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the errorSee “Using debug logs” on page 423.

■ If possible, attempt the requested operation again with another user interfacethat supports the type of request.

Media Manager status code: 15Message: invalid volgroup

A requested operation encountered a case where the volume group:

■ Is not specified

■ Is not in an acceptable format

■ Exceeds the allowed length of a volume group name

■ Examine command output, debug logs, and system logs for a more detailedmessage on the errorSee “Using debug logs” on page 423.

■ Specify a volume group where one is required to ensure that it contains thefollowing:

■ 25 ASCII characters or less

■ No white space

■ No unprintable characters

Media Manager status code: 16Message: invalid robot coord1

429Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: A requested operation encountered a missing or out-of-range robotslot number. Or a move by volume group residence was attempted when the volumedid not originate from a valid robotic library slot.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify a slot number (robot coordinate 1) where required and ensure that thenumber is within the allowable range for the given robot type.

Media Manager status code: 18Message: cannot allocate requested memory

Explanation: Allocation of system memory failed. This error occurs wheninsufficient system memory is available. The system may have too little physicaland virtual memory to handle the current load of processes.

RecommendedAction: Free up memory by terminating any unneeded processesthat consume a lot of memory. Add more swap space or physical memory.

Media Manager status code: 19Message: invalid database host

Explanation: A requested operation encountered a missing or an invalid databasehost. Or a request was sent to a host that is running a version of the product thatdoes not support the requested operation.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify a valid EMM database host on which the following is running: a versionof nbemm (the NetBackup Enterprise Media Manager) or an operator requestdaemon or process that supports the requested operation.

Media Manager status code: 20Message: protocol error

Explanation: Message communications (handshaking) was not correct.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

430

■ Retry the operation and examine the logs. Ensure that no whitespaces areembedded in the fields that do not allow embedded whitespace.

Media Manager status code: 21Message: cannot obtain daemon lockfile

Explanation: vmd (NetBackup Volume Manager daemon on UNIX and Linux;NetBackup Volume Manager service on Windows) or operator request daemon orservice cannot obtain an internal software lock.

Recommended Action: Check for the existence and permissions of the lock fileitself and the lock file directory: /usr/openv/volmgr/misc/vmd.lock (UNIX andLinux) or install_path\Volmgr\misc\vmd.lock (Windows). Create the directoryor folder and adjust the permissions as needed so that vmd can obtain the lock:/usr/openv/volmgr/misc/vmd.lock (UNIX and Linux) orinstall_path\Volmgr\misc\vmd.lock (Windows).

Media Manager status code: 22Message: pool type change is not allowed for <CatalogBackup> pool

Explanation: An attempt was made to remove the catalog backup attribute of thedefault CatalogBackup pool.

Recommended Action: Verify that the appropriate pool name was used in thisoperation.

Media Manager status code: 23Message: database server is down

Explanation: A request was made to the EMM server, but the underlying databaseserver does not respond.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ This error can occur if a cold catalog backup is in progress. Retry the requestafter this operation has completed.

Media Manager status code: 25Message: failed making the database directory

Explanation: nbpushdata cannot create a working directory during upgrade.

431Media and device management status codes and messagesAbout media and device management status codes and messages

RecommendedAction: Determine why the directory /usr/openv/tmp (UNIX andLinux) or install_path\tmp (Windows) cannot be created. Check to see whataccount nbpushdata was run under. Compare it against the security propertiesof the database folder.

Media Manager status code: 26Message: database open operation failed

Explanation: A database file cannot be opened.

Recommended Action:

Check for the existence and permissions of the following files in the/usr/openv/var/global directory (UNIX and Linux) orinstall_path\NetBackup\var\global folder (Windows):

■ external_robotics.txt

■ external_densities.txt

■ external_drivetypes.txt

■ external_mediatypes.txt

Media Manager status code: 27Message: database read record operation failed

Explanation: nbpushdata encountered a read error while reading an EMM databaserecord.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ The EMM database may be corrupted. Restore an older EMM database from asaved version or from catalog backups.

Media Manager status code: 28Message: database read operation read too few bytes

Explanation: nbpushdata encountered a record that was smaller than expectedwhile reading an EMM database record.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

432

■ The EMM database may be corrupted. Restore an older EMM database from asaved version or from catalog backups.

Media Manager status code: 32Message: database write record operation failed

Explanation: nbpushdata encountered an error while writing an EMM databaserecord.

Recommended Action:

Examine command output, debug logs, and system logs for a more detailed messageon the error.

See “Using debug logs” on page 423.

Media Manager status code: 34Message: media ID not unique in database

Explanation: A volume entry being added to or changed in the EMM databasehad a media ID specified. The specified ID was a duplicate of the media ID foranother volume already in the EMM database. All volumes in the EMM databasemust have a unique media ID.

■ Examine the daemon and reqlib debug logs for a more detailed message on theerror.See “Using debug logs” on page 423.

■ When you add volumes to the EMM database, specify a media ID that is unique.

■ If you run vmphyinv, there may be two or more media in the tape library withthe same media ID.

Media Manager status code: 35Message: volume does not exist in database

Explanation: A requested operation encountered a case where a volume querydid not return a volume entry that matched the search criteria.

■ Examine the daemon and reqlib debug logs for a more detailed message on theerror.See “Using debug logs” on page 423.

■ Ensure that volumes are configured properly on the EMM server that matchesthe EMM server configured for the robot or set of stand-alone drives. Usetpconfig -d to list the configured EMM server.

433Media and device management status codes and messagesAbout media and device management status codes and messages

■ Do the following so the volume query can find a matching volume: update thevolume or the device configurations, specify the correct EMM server, modifyvolume properties, or adjust search criteria.

■ If you run vmphyinv, none of the media satisfy the search criterion. As such,vmphyinv cannot inventory the tape library.

Media Manager status code: 36Message: barcode not unique in database

Explanation: A specified bar code in an added or a changed volume entry in theEMM database duplicated a volume bar code already in the database. All volumesin the EMM database must have a unique bar code.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

■ Query or sort volume records by bar code to identify the volume entry withthe duplicate bar code.

Media Manager status code: 37Message: robotic volume position is already in use

Explanation: A robotic coordinate in an added or a changed volume entry in theEMM database duplicated a volume robotic coordinate in the database. (The roboticcoordinate includes the slot number or the slot number and platter side.) Allvolumes in the EMM database must have unique robotic coordinates.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

■ Query or sort volume records by slot number to identify the volume entry withthe duplicate robotic coordinate.

■ Change (update or move volume) or delete the existing volume entry if it doesnot reflect the following: the correct robotic coordinate corresponding to thevolume’s storage position in the robotic library. If a volume is currently in adrive, the EMM database should still reflect the volume’s home slot.

Media Manager status code: 39Message: network protocol error

Explanation: An attempt to read data from a socket failed.

Media and device management status codes and messagesAbout media and device management status codes and messages

434

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the protocol error.See “Using debug logs” on page 423.

■ Verify that the server being connected to is operational.

Media Manager status code: 40Message: unexpected data received

Explanation: Message communications (handshaking) was not correct.

■ Verify that the correct version of software is running on all servers.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the protocol error.See “Using debug logs” on page 423.

■ Retry the operation and examine the logs.

■ Ensure that no embedded whitespaces exist in the fields that do not allowembedded whitespace.

Media Manager status code: 41Message: invalid media ID for naming mode

Explanation: A request to add multiple volumes with a first media ID and a mediaID style failed. It fails because the media ID specified was not compatible with themedia ID naming style provided.

Recommended Action: Provide a first media ID that fits the selected style. Forexample, the media ID style is two characters and four digits. Then the leastsignificant four characters in the first media ID must be digits in the range 0 to9. Alternatively, select a media ID style that fits the specified first media ID.

Media Manager status code: 42Message: cannot connect to robotic software daemon

Explanation: A connection to a robotic software daemon or process cannot beestablished. This error can occur when a process tries to connect to the roboticprocess that is not running. It can also occur if the network or server is heavilyloaded and has slow response time.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

435Media and device management status codes and messagesAbout media and device management status codes and messages

■ Identify the robotic process: look at the robot type and at the robot host onthe robotic request or the robot host field of the volume being operated on.

■ Verify that the robotic process to use for robotic control is availableSee Table B-2 on page 695.If necessary, start the robotic process.

■ Ensure that only one configured robot control host exists for each TL8, TLD,and TLH robot. Also ensure that all volumes in the volume configuration havea robot host that matches the configured robot control host.

■ Change the volumes or reconfigure the robot in the device configuration asneeded.

■ Check the system log on the robot control host to see if the robotic processprocesses requests when connections to it are attempted.

Media Manager status code: 43Message: failed sending to robotic software daemon

Explanation: An attempt to write data to a robotic software daemon or processsocket failed.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message error.See “Using debug logs” on page 423.

■ Identify the robotic process: look at the robot type and at the robot host onthe robotic request or the robot host field of the volume being operated on.Verify that the robotic process to use for robotic control is available and thatit handles requests.

■ Identify the robot control host by checking the device configuration. Only oneconfigured robot control host should exist for each TL8, TLD, and TLH robot.All volumes in the volume configuration should have a robot host that matchesthe configured robot control host.

■ Check the system log on the robot control host to see if the robotic processprocesses requests when communications with it are attempted.

Media Manager status code: 44Message: failed receiving from robotic software daemon

Explanation: An attempt to read data from a robotic software daemon or processsocket failed.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.

Media and device management status codes and messagesAbout media and device management status codes and messages

436

See “Using debug logs” on page 423.

■ Identify the targeted robotic process: look at the robot type and at the robothost on the robotic request or the robot host field of the volume being operatedon. Verify that the robotic process to use for robotic control is available andthat it handles requests.See “Media and device management components” on page 693.

■ Identify the robot control host by checking the device configuration. Only oneconfigured robot control host should exist for each TL8, TLD, and TLH robot.All volumes in the volume configuration should have a robot host that matchesthe configured robot control host.

■ Check the system log on the robot control host to see if the robotic processhandles requests when communications with it are attempted.See “Resolving network communication problems” on page 40.

Media Manager status code: 45Message: failed changing terminal characteristics

Explanation: When an attempt was made to change the mode for terminal inputbetween cooked and raw, a system call failed.

Recommended Action: Examine the user interface output for the system errorthat is associated with the failed system call. Then troubleshoot according tooperating system vendor recommendations.

Media Manager status code: 46Message: unexpected data from robotic software daemon

Explanation: Message communications (handshaking) between a process and arobotic software daemon or process failed.

■ Verify that the correct version of software is running on all servers.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Retry the operation and examine the logs.

■ Ensure that no embedded whitespaces exist in the fields that do not allowembedded whitespace.

■ Check the system log on the robot control host for errors that the roboticsoftware logged.

437Media and device management status codes and messagesAbout media and device management status codes and messages

Media Manager status code: 47Message: no entries changed

Explanation: A requested operation was completed, but no changes to the volumeconfiguration or Media Manager configuration file were made. The administratormay have terminated an operation instead of continuing with proposed changes.Or the configuration file may already include the configuration entry that was tobe added.

■ No action is needed if the administrator aborted the change operation.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

Media Manager status code: 48Message: no entries deleted

Explanation: A delete volume(s) operation completed. No changes were made tothe volume configuration.

■ No action is needed, unless the volumes that were requested to be deleted werenot in fact deleted.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

Media Manager status code: 49Message: no entries inserted

Explanation: An insert volume(s) operation completed. No volumes were addedto the volume configuration.

■ No action is needed unless the volumes that were requested to be insertedwere not inserted.

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

Media Manager status code: 50Message: invalid change-entry request

Explanation: An invalid request to change volume information was sent to vmdon the EMM server.

Media and device management status codes and messagesAbout media and device management status codes and messages

438

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the usage statement for expected usage and compare with the parametersbeing sent to start the new process.

Media Manager status code: 51Message: cannot auto-eject this robot type

Explanation: A request to change volume residence with media eject was sent tovmd, but the volume’s robot type does not support automated media eject. (vmdis the NetBackup Volume Manager daemon on UNIX and Linux or NetBackupVolume Manager service on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that change volume residence requests are not sent to vmd on a systemthat runs an older, incompatible software version level. (The change volumeresidence requests are requests with eject for the robot type that is involvedwith a newer release version level.)

Media Manager status code: 52Message: cannot auto-inject this robot type

Explanation: A request to change volume residence with media inject was sentto vmd, but the volume’s robot type does not support automated media inject. (vmdis the NetBackup Volume Manager daemon on UNIX and Linux or NetBackupVolume Manager service on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that change volume residence requests are not sent to vmd on a systemthat runs an older, incompatible software version level. (The change volumeresidence requests are requests with inject for the robot type that is involvedwith a newer release version level.)

Media Manager status code: 53Message: invalid volume move mode

439Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: A robotic-related request was made specifying a media movementoption that not all affected software components supports.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the robotic request is sent to a system that runs a release versionof software that supports the particular request.

Media Manager status code: 54Message: robot number and robot type mismatch

Explanation: A request was made to add or change volumes in the volumeconfiguration. The robot number to be associated with a volume is already in use.It is associated with another volume in a robot with the same number but ofanother robot type.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that robot numbers are unique for each physical robot in the EMMdatabase. Delete and re-add a robot. Use a unique robot number if duplicaterobot numbers are in use. Use a media management interface to identify robotnumbers currently in use for all volumes in the volume configuration. If youuse a command line interface, specify the correct robot type for the robotnumber that is associated with the request.

Media Manager status code: 55Message: robot number and volume group mismatch

Explanation: A request was made to add or change volumes in the volumeconfiguration. The robot number and volume group that is associated with thevolume configuration changes are in conflict with the requirements for volumegroups. All volumes in a volume group are required to have the same residence,which includes having the same robot number.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the specified robot number and volume group are compatible. Ifvolumes in the volume group have a given robot number, then volumes witha different robot number cannot be added to that volume group. Volumescannot be moved directly from one robotic volume group to another robotic

Media and device management status codes and messagesAbout media and device management status codes and messages

440

volume group. The intermediate steps (some volume entries are changed, someare not) would cause a conflict with robot numbers. Choose a different volumegroup on the request, or let the volume group be selected automatically. Volumegroup selection depends on the specific interface being used.

Media Manager status code: 56Message: invalid database version header

Explanation: nbpushdata cannot find a recognizable EMM database version inthe EMM database, and cannot initialize with the database currently in place.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ From catalog backups or another source if available, restore an earlier versionof the database file: /usr/openv/volmgr/database/volDB (UNIX and Linux)or install_path\Volmgr\database\volDB (Windows). Then restart vmd.

Media Manager status code: 57Message: error auto-generating volume group

Explanation: A request was made to add or change volumes in the volumeconfiguration by using automatic generation of the volume group name. A uniquevolume group name cannot be generated because the available combinations wereused up.

Recommended Action: Consolidate volumes into volume groups within thetargeted robot number so that a new volume group can be generated automatically.Or provide a specific volume group name.

Media Manager status code: 58Message: daemon cannot obtain socket

Explanation: vmd cannot bind to its socket. (vmd is the NetBackup Volume Managerdaemon on UNIX and Linux and the NetBackup Volume Manager service onWindows.) When vmd attempts to bind to its configured port number, system callfails. The call fails usually because another process having acquired the portbefore the vmd daemon or service started.

■ Examine the daemon debug log for a more detailed message on the systemerror.

441Media and device management status codes and messagesAbout media and device management status codes and messages

■ If another process has the port, use other system commands to determine theprocess. Based on the result, either change the port number in your servicesfile or map, or terminate the process that has acquired the port.

■ UNIX and Linux only: Another possible cause for this error is the use of thekill command to terminate vmd. To stop vmd, the recommended method is touse the Terminate Media Manager Volume Daemon option on the Specialactions menu in vmadm. (Or use the equivalent command line request,vmctrldbm -t). The use of the kill command to stop this process can leaveit unable to bind to its assigned port the next time it restarts. When the socketproblem occurs, the daemon debug log contains lines similar to the following:

unable to obtain bound socket, Address already in use (125)

Media Manager status code: 59Message: daemon failed accepting connection

Explanation: vmd cannot accept a new connection due to a system call failure.(vmd is the NetBackup Volume Manager daemon on UNIX and Linux and theNetBackup Volume Manager service on Windows.)

■ Examine the daemon debug log for a more detailed message on the systemerror. Examine command output, debug logs, and system logs for a moredetailed message on the error.See “Using debug logs” on page 423.

■ Obtain the specific system call failure from the debug log, and investigate theoperating system functionality that is related to the failure.

Media Manager status code: 60Message: cannot perform operation on this host

Explanation: A requested operation is not functional on a particular host.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Robot inventory update must be initiated only on the host where the roboticcontrol and drives are configured.

Media Manager status code: 61Message: robot number and robot host mismatch

Media and device management status codes and messagesAbout media and device management status codes and messages

442

Explanation: A request is made to add or change volumes in the volumeconfiguration, or to issue a robot inventory update request. A specified robot hostdiffers from the robot host for other volumes in the same robot (defined as thosevolumes having the same robot number). All volumes in the EMM database thathave a given robot number (for instance, 0) must have the same robot host name.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify the robot host in the device configuration to be the same case-sensitivehost name on all hosts where the robot is configured. Re-issue the request. Asan alternative, use move-by-volume group to move all volumes logically froma robotic volume group to stand-alone and then back into the robot. Specifythe robot host as the host name that is used in the robot configuration. Thenre-issue the request.

Media Manager status code: 62Message: failed redirecting input to pipe

Explanation: A system pipe cannot be created.

Recommended Action: Check the interface output for the specific system errorand investigate the operating system functionality that is related to the failure.

Media Manager status code: 63Message: child process killed by signal

Explanation: An unexpected signal terminated a robot inventory update process.

■ Examine interface output and debug logs for a more detailed message error.Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media Manager status code: 64Message: no child process to wait for

Explanation: A media management interface attempted to wait for a child processto complete, but unexpectedly found that no such child process existed.

■ Examine interface output and debug logs for a more detailed message error.Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

443Media and device management status codes and messagesAbout media and device management status codes and messages

■ Retry the operation (or try to use a different media management interface)and examine the logs.

Media Manager status code: 65Message: volume group does not exist

Explanation: During a request process, a volume group cannot be found withinthe existing volume entries in the EMM database.

1 Examine the daemon debug log for a more detailed message on the systemerror. Examine command output, debug logs, and system logs for a moredetailed message on the error.

See “Using debug logs” on page 423.

2 Check for data integrity or consistency problems in the EMM database byusing a media management interface. Delete or move volume entries so thatthe volume group issues are corrected.

Media Manager status code: 67Message: unable to send exit status

Explanation: vmd cannot send the status of a requested operation to the requestor.(vmd is the NetBackup Volume Manager daemon on UNIX and Linux and theNetBackup Volume Manager service on Windows.)

■ Examine the daemon debug log for a more detailed message on the systemerror. Examine command output, debug logs, and system logs for a moredetailed message on the error.See “Using debug logs” on page 423.

■ Obtain the specific send or write system call failure from the debug log, andinvestigate the operating system functionality that is related to the failure.

■ Use the following steps to check whether the command or the applicationinterface that sends the request aborts prematurely: enable reqlib debug logs,retry the operation, check the debug logs, and observe application interfaceoutput.

Media Manager status code: 68Message: too many volumes in volume group

Explanation: A request was made to add or change volumes in the volumeconfiguration but the volume number was at its allowable limit. The limit is basedon the number of volumes that is allowed in a particular type of robot.

Media and device management status codes and messagesAbout media and device management status codes and messages

444

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check to see if volumes are defined in the EMM database. They may be definedin the EMM database, which is associated with a slot number zero that maynot exist in the robot. Run a robot inventory Show contents of robot reportand observe the starting slot number. If the starting slot number is one and avolume is defined in the robot at slot zero, delete the volume entry. Or moveit to stand-alone so that the remaining available media slots can be used.

Media Manager status code: 69Message: failed sending request to vmd

Explanation: A request cannot be sent to vmd or to oprd, even though the initialconnection to the server process was successful. (vmd is the NetBackup VolumeManager daemon on UNIX and Linux or NetBackup Volume Manager service onWindows; oprd is the operator request daemon or process.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check to see whether the vmd or the oprd process continues to run once itreceives the connection from the requestor. Run netstat -a or an equivalentsocket diagnostic utility. Check the following to see if the server process ishung up: the daemon debug log on the server-side system and the processstatus of vmd or oprd.

Media Manager status code: 70Message: cannot connect to vmd [on host host name]

Explanation: A process times out while connecting to the following: vmd (theNetBackup Volume Manager daemon on UNIX and Linux or NetBackup VolumeManager service on Windows) or to oprd (the operator request daemon or process).This problem can occur when a connection is attempted and the server processis not running. It also can occur if the network or server is heavily loaded and hasslow response time.

■ On the host where vmd is the recipient of the connection, verify that the daemonor the service is running. (The host is the Media Manager host, the DeviceHost, or the EMM server.) If the daemon or the service is not running, start it.On Windows, vmd is the NetBackup Volume Manager service.

445Media and device management status codes and messagesAbout media and device management status codes and messages

■ If vmd is already running, examine command output, debug logs, and systemlogs for a more detailed message on the error.See “Using debug logs” on page 423.

■ Verify that the correct host names are defined in the configuration.

■ Check the services file. On UNIX and Linux, verify that the /etc/services file(and NIS services if NIS is used) has entries for the vmd service. (Note that thevmd service always starts oprd.) On Windows, verify that the%systemroot%\system32\drivers\etc\services file has the correct entryfor vmd. Also verify that the vmd port number in the services file agrees withthe port number configuration. The port number is noted in the man page forvmd(1M).

■ Verify that all operating system patches or service packs are installed.

■ Ensure that the Media Manager configuration is not tuned so that the load onvmd exceeds its ability to service requests. Look for entries in the vm.conf filethat increase the load. Consider placing the EMM database on a higherperformance server and file system if performance is an issue. To reduce thenumber of volumes in the volume configuration, use inventory filtering forthe robot types that support it

■ Check utilities such as ipcs -a to ensure that shared memory functionsproperly. The oprdprocess may not respond because it cannot attach to sharedmemory.

Media Manager status code: 71Message: failed sending to vmd

Explanation: An attempt to write data to a vmd socket failed. vmd is the NetBackupVolume Manager daemon (UNIX and Linux) or NetBackup Volume Manager service(Windows).

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

■ Identify the system where vmd is running. The system usually is termed theMedia Manager host or EMM server and defaults to the local system in someuser interfaces (such as vmadm). Possible causes for the error are high networkload, missing operating system patches or service packs, or unexpected vmdprocess failure.

Media and device management status codes and messagesAbout media and device management status codes and messages

446

Media Manager status code: 72Message: failed receiving from vmd

Explanation: An attempt to read data from a vmd socket failed. vmd is theNetBackup Volume Manager daemon (UNIX and Linux) or NetBackup VolumeManager service (Windows).

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

■ Identify the system where vmd is running. The system is usually termed theMedia Manager host or EMM server and defaults to the local system in someuser interfaces (such as vmadm). Possible causes for the error are high networkload, missing operating system patches or service packs, or unexpected vmdprocess failure. Also, the socket read may have failed because the requestedoperation did not complete within a specified time period. The robotic processand vmd interactions can affect some requests to vmd; check the system logfor errors on the robotic control host.

Media Manager status code: 73Message: invalid query type

Explanation: An invalid volume query request was attempted.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that all Media Manager and user interface binaries are at a compatibleversion level.

Media Manager status code: 74Message: invalid number of cleanings

Explanation: A request was made to change the number of cleanings that remainsfor one or more volumes in the volume configuration. When the request was made,the specified value was not within the acceptable range. The number of cleaningsvalue may also be invalid in the number of mounts or cleanings field of a bar coderule.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

447Media and device management status codes and messagesAbout media and device management status codes and messages

■ Specify a number of cleanings value within the acceptable range of 0 to2,147,483,647.

Media Manager status code: 75Message: invalid change type

Explanation: An invalid volume change request was attempted.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that all Media Manager and user interface binaries are at a compatibleversion level.

Media Manager status code: 76Message: cannot get host name

Explanation: The system call gethostname(3C) failed during an attempt to obtainthe name of the local host.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Obtain the specific system call failure from the debug log, and investigate theoperating system functionality that is related to the failure. Run the hostnamesystem command to see if the command operates correctly.

Media Manager status code: 78Message: barcode does not exist in database

Explanation: A query volume by bar code request did not return a volume entryhaving the specified bar code, or bar code and media type.

■ Examine the daemon and reqlib debug logs for a more detailed message on theerror.See “Using debug logs” on page 423.

■ Ensure that volumes are properly configured in the EMM database. Usetpconfig -d to list the configured EMM server. Select the current server (theone being administered) to be the same as the host, which is the correct EMMserver. Do the following so that the volume query can find a matching volume:update the volume or the device configurations, modify volume properties, oradjust search criteria as needed. For media in their correct slot locations, runthe Rescan or the update bar code request so the following occurs: the bar code

Media and device management status codes and messagesAbout media and device management status codes and messages

448

field in the volume configuration matches the actual bar code as interpretedby the robotic library bar code reader.

Media Manager status code: 79Message: specified robot is unknown to vmd

Explanation: A request was made to query volumes by residence. No volumeswere found in the targeted volume configuration that matched the provided robotnumber, robot type, and robot host.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that volumes are properly configured in the EMM database. Usetpconfig -d to list the configured EMM server. Select the current server (theone being administered) to be the same as the host which is the correct EMMserver. Perform the following so the volume residence query can find amatching volume: update the volume or the device configurations, modifyvolume properties, or adjust search criteria as needed.

Media Manager status code: 80Message: cannot update database due to existing errors

vmphyinv is unable to update the EMM database because of the existing errors.The errors can be as follows:

■ A Media Manager volume record belongs to a different robot with the samemedia ID as the media ID that the tape header read.

■ The media type or media GUID or the volume pool of an assigned volumerecord needs to be changed.

■ A bar code conflict is detected and vmphyinv needs to change the bar code ofthe existing volume record.

Recommended Action: vmphyinv, in such a scenario, generates a list of errors.Examine the output. You must resolve all these errors before you run the utilityagain.

Media Manager status code: 81Message: robot type and volume group mismatch

Explanation: A request was made to add volumes or change volume residencesin the volume configuration. The robot type and volume group that is associatedwith the volume configuration changes are in conflict with the requirements for

449Media and device management status codes and messagesAbout media and device management status codes and messages

volume groups. All volumes in a volume group are required to have the sameresidence, which includes having the same robot type. A requested operation mayhave tried to associate the special No Volume Group name "---" with a roboticresidence.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the specified robot residence and volume group are compatiblewith other volumes in the volume configuration that are in the specified volumegroup. Do not move volumes in the special No Volume Group name "----" to arobotic residence without moving them to a new or auto-generated volumegroup. Choose a different volume group on the request, or let the volume groupbe automatically selected. Volume group selection depends on the specificinterface being used.

Media Manager status code: 82Message: robot host and volume group mismatch

Explanation: A request was made to add volumes or change volume residencesin the volume configuration. The robot host and volume group that is associatedwith the volume configuration changes are in conflict with the requirements forvolume groups. All volumes in a volume group are required to have the sameresidence. This residence includes having the same robot host, where robot hostequivalence is defined as having the same case-sensitive robot host string.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the specified robot residence and volume group are compatiblewith other volumes in the volume configuration that are in the specified volumegroup. Do not try to add volumes for a robot host by using a different form ofthe robot host name. For example, "acme" is not the same as"acme.symantec.com." Use the same host name that is used for other volumesin the volume group. If the robot host needs to be changed for volumes in avolume group, do the following: use a single move volume group request(available only in certain media management interfaces) to move the volumegroup to stand-alone residence. Then move the volume group back to therobotic residence. Specify the robot control host that you want to be associatedwith the new volume group.

Media and device management status codes and messagesAbout media and device management status codes and messages

450

Media Manager status code: 83Message: device management error

Explanation: One of the device management errors occurs during the executionof vmphyinv.

Recommended Action:

Examine command output, debug logs, and system logs for a more detailed messageon the error.

See “Using debug logs” on page 423.

Media Manager status code: 84Message: this machine is not the database host

Explanation: A request was made to initiate vmd on a host other than the localhost. vmd is the NetBackup Volume Manager daemon (UNIX and Linux) orNetBackup Volume Manager service (Windows).

vmd port numbers other than the default or use of unsupported options can affectthe referenced host and port in the interfaces that start vmd.

■ Initiate vmd on the local host only, by logging on to the host where vmd needsto run Start vmd on that host. On UNIX and Linux, run/usr/openv/volmgr/bin/vmd [-v]. On Windows, start the NetBackup VolumeManager service in Services of the system Control Panel.

■ If more information is needed to explain the problem, examine commandoutput, debug logs, and system logs for a more detailed message on the error.See “Using debug logs” on page 423.

■ Make sure port numbers are consistent.

Media Manager status code: 85Message: volume daemon fork failed

Explanation: A Media Manager daemon or service cannot create a child processdue to an error from the system. This error probably is intermittent, based on theavailability of resources on the system.

■ Restart the service at a later time and investigate the system problems thatlimit the number of processes.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

451Media and device management status codes and messagesAbout media and device management status codes and messages

Media Manager status code: 86Message: failed opening tmp output file

Explanation: The vm.conf file or temporary working file cannot be opened.

Recommended Action: On UNIX and Linux, check for the existence andpermissions of the /usr/openv/volmgr/misc directory, /tmp directory, and/usr/openv/volmgr/vm.conf file. On Windows: check for the existence and thesecurity properties of the install_path\Volmgr\vm.conf file.

Media Manager status code: 87Message: failed redirecting tmp output file

Explanation: The system call dup2(3C) failed during an attempt to direct interfaceoutput from a temporary file to the process’s standard output.

Recommended Action: Investigate the operating system functionality that isrelated to resource limits on the number of open files. Ensure that extraneoussignals do not interrupt processes.

Media Manager status code: 88Message: failed initiating child process

Explanation: A command cannot be ran. This error can occur due to the following:the command permissions do not allow it to be ran or system resources such asmemory and swap space are insufficient.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the permissions on the vmcheckxxx, vmupdate, and oprd binaries, and(on Windows only) the rdevmi installed binary.

Media Manager status code: 89Message: another daemon already exists

Explanation: vmd (the NetBackup Volume Manager daemon on UNIX and Linuxor NetBackup Volume Manager service on Windows) tries to initialize and foundthat it was already running, according to the daemon or the service lock file.

RecommendedAction: Check to see if vmd is already running. Do not try to startanother vmd daemon or service until you first shut down the daemon or the servicethat is running. Stop the vmd that is running with vmctrldbm -t. On Windows,use the system Services interface. If the daemon or the service unexpectedly

Media and device management status codes and messagesAbout media and device management status codes and messages

452

terminated, remove the lock file. The lock file is/usr/openv/volmgr/misc/vmd.lock (UNIX and Linux) orinstall_path\Volmgr\misc\vmd.lock (Windows). Then restart vmd.

Media Manager status code: 90Message: invalid volume pool

Explanation: A request was made to add volumes, change the volume pool for avolume, add a bar code rule, or change a bar code rule. However, the volume poolname or number that is associated with the requested change is in conflict withthe requirements for volume pools.

These requirements are as follows:

■ Volumes in scratch pools cannot be assigned until they are first moved toanother pool.

■ Volume pool numbers cannot be negative.

■ Volume pool names must consist of from 1 to 20 printable ASCII characterswith no embedded whitespace.

■ The None volume pool is the only valid pool for the bar code rule entries thatspecify cleaning a media type.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the specified volume pool does not violate the requirements noted.Use the vmpool command to display the pool information. Use the vmrule

command to display the bar code rule information. Add or change volumepools and bar code rules as needed to rectify inconsistencies in cases wherethe databases are inconsistent or corrupted.

Media Manager status code: 92Message: cannot delete assigned volume

Explanation: A delete request was made to a volume, and the volume is currentlyassigned.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Assigned volumes cannot be deleted. If no worthwhile data is on the volume,unassign the media by using the appropriate application interface (which isbpexpdate for NetBackup). Then retry the delete volume request.

453Media and device management status codes and messagesAbout media and device management status codes and messages

Media Manager status code: 93Message: volume is already assigned

Explanation: A request was made to assign a volume, and the volume was alreadyassigned.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Do not try to manually assign any volumes that are already assigned, becauseit is not valid except for one condition: you can assign volumes for NetBackupcatalog backups if the volume is already assigned for NetBackup catalogbackups. Always use barcodes that are unique in the six least significantcharacters, across all media in all robots. Or use media ID generation rules toensure that unique media IDs are generated in a robot inventory update.

Media Manager status code: 94Message: volume is not in specified pool

Explanation: A request was made to assign a volume from a specified volumepool. The volume was in a different volume pool.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ When you assign volumes manually, specify the volume pool that is associatedwith the volume. Always use barcodes that are unique in the six least significantcharacters, across all media in all robots. Or use media ID generation rules toensure that unique media IDs are generated in a robot inventory update.

Media Manager status code: 95Message: media ID is not the specified media type

Explanation: A request was made to assign or add a volume of a specified mediatype. The volume or physically similar volumes have a different media type.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ When you use robot inventory update to make changes to the volumeconfiguration, do the following: ensure that all volumes of the same physicalcartridge type (for example, 3590J in TLH robots) map to a single media type

Media and device management status codes and messagesAbout media and device management status codes and messages

454

such as HCART. This check ensures that all media in the robotic library canbe mounted on drives with a compatible drive type.

■ When you assign volumes manually, specify the media type that is associatedwith the volume. Always use bar codes that are unique with respect to the sixleast significant characters, across all media in all robots. Or use media IDgeneration rules to ensure that unique media IDs are generated when you userobot inventory update.

Media Manager status code: 96Message: oprd returned abnormal status

Explanation: A request that oprd services (the operator request daemon orprocess) returned an abnormal status.

■ On Windows, do the following when you auto-configure devices or initiate theNetBackup Device Manager service from a graphical or a command lineinterface: ensure that the service is not disabled in the system servicesconfiguration.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ In general, any device management-related errors that occur on a particularhost accompany operator request daemon or process and remote devicemanagement errors. Check for errors in the following: the debug and the systemor the application logs on the host where oprd was started or where it isrunning. The host is often a targeted device host or scan host.

The kinds of failed requests that oprd services can include the following:

■ Down, up, or reset drives

■ Change drive comments

■ Deny or resubmit mount requests

■ Assign drives

■ Start or stop ltid

■ Obtain ltid status

■ Display drive status

■ Manage pending actions

■ Set NDMP attributes

■ Configure devices

455Media and device management status codes and messagesAbout media and device management status codes and messages

■ Clean drives

■ Obtain host version and device configuration information

■ Scan shared drives

Media Manager status code: 97Message: rule does not exist in rule database

Explanation: A request was made to change or delete a bar code rule, but the barcode rule with the specified bar code tag cannot be found.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ List the configured bar code rules in the EMM database. Adjust the bar codetag that is specified on the change or the delete request or on the targetedhost. Then the bar code rule is found when the request is retried.

Media Manager status code: 101Message: media type and volume group mismatch

Explanation: A request was made to add volumes or change volume residencesin the volume configuration. The media type and volume group that are associatedwith the volume configuration changes are in conflict with the requirements forvolume groups. All volumes in a volume group are required to have the sameresidence, which includes having the same media type. Media types that are usedfor data and their associated cleaning media types are considered to be the samewith regard to volume group restrictions.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the specified media type and volume group are compatible withother volumes in the volume configuration that are in the specified volumegroup. Choose a different volume group on the request, or let the volume groupbe automatically selected. Volume group selection depends on the interfacebeing used.

Media Manager status code: 102Message: invalid pool database entry

Explanation: The volume pool database is corrupt. It contains some records thatare not compatible with the installed product binaries.

Media and device management status codes and messagesAbout media and device management status codes and messages

456

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use vmpool to investigate the integrity of the volume pool database. Thedaemon debug log file should indicate the expected number of fields and thefound number of fields in the pool record. Restore a saved version of the pooldatabase if the pool database cannot be manually corrected.

Media Manager status code: 104Message: failed appending to pool database

Explanation: A request was made to add, change, or delete a volume pool in thevolume pool configuration. But the pool record cannot be appended to the volumepool database file.

■ Examine the daemon debug log for a more detailed message on the systemerror.See “Using debug logs” on page 423.

■ Examine the permissions and available file system space for writing to thedatabase: on UNIX and Linux, /usr/openv/volmgr/database/poolDB; onWindows, install_path\Volmgr\database\poolDB.

Media Manager status code: 105Message: poolname is not unique in pool database

Explanation: A request was made to add a volume pool in the volume poolconfiguration. The pool name specified is a duplicate of the name for an existingvolume pool.

Recommended Action: On the add volume pool request, specify a volume poolname that is not already in use on the targeted EMM database host.

Media Manager status code: 109Message: pool does not exist in pool database

A requested operation encountered a case where the specified volume pool wasnot found in the volume pool configuration. The requests that can return thiserror code are as follows:

■ Add, change, delete, or query volume pool

■ Add or change bar code rule

■ Add or change volume

457Media and device management status codes and messagesAbout media and device management status codes and messages

■ Query scratch volumes

■ Robot inventory report or update

■ Examine the daemon and reqlib debug logs for a more detailed message on theerror.See “Using debug logs” on page 423.

■ Ensure that volumes are properly configured on the EMM server. Use thetpconfig -d command to list the configured EMM server. Select the currentserver (the one being administered) to be the same as the host which is thecorrect EMM server for a targeted device.

■ Do the following so the requested operation can find the requested volumepool: update the volume or the device configurations, modify volume properties,or adjust search criteria as needed. Investigate inconsistencies between theEMM database and the volume pool database, and restore or correct thosedatabases from a previous state as needed.

Media Manager status code: 111Message: the specified pool is not empty

Explanation: A request was made to delete a volume pool. The pool was not empty,or it could not be determined whether or not volumes were still associated withthe specified volume pool.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use a media management interface to query for the volumes that are associatedwith the pool specified for deletion. Ensure that all volumes in a volume poolare associated again with another pool before trying to delete the volume pool.Use change volume operations to change the volume pool for a volume.

Media Manager status code: 112Message: no pools in the pool list

Explanation: Unexpectedly, the volume pool list is empty.

Recommended Action: The volume pool list should contain a minimum of fourpools: None, NetBackup, Catalog Backup, and DataStore. Investigate the integrityof the EMM database. Restore the EMM database from catalog backups.

Media Manager status code: 113Message: invalid expiration date

Media and device management status codes and messagesAbout media and device management status codes and messages

458

Explanation: A request was made to change the media expiration for one or morevolumes in the volume configuration, but the date specified was not valid.

Recommended Action:

When you change the media expiration, provide the date in the format that themedia management interface documentation specifies.

Media Manager status code: 114Message: invalid maximum mounts

Explanation: A request was made to change the limit for the number of times avolume can be mounted with write access for one or more volumes in the volumeconfiguration. The specified value is not within the acceptable range. Themaximum number of mounts value may also be invalid in the number of mountsor cleanings field of a bar code rule.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify a maximum mounts value within the range of 0 to 2,147,483,647.

Media Manager status code: 115Message: volume has passed expiration date

Explanation: A request was made to assign a volume, and the volume expirationdate has expired in relation to the current system date.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Extend the active life of the physical media: change the volume expirationdate to a future date in relation to the current system date or time.Alternatively, replace the media with other media that still contains usefullife. Check the system date and time and reset it as needed.

Media Manager status code: 116Message: volume has exceeded maximum mounts

Explanation: A request was made to assign a volume. The volume’s number ofmounts exceeds the maximum number of mounts allowed for the volume.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.

459Media and device management status codes and messagesAbout media and device management status codes and messages

See “Using debug logs” on page 423.

■ Extend the active life of the physical media: increase the volume’s maximumnumber of mounts or set the maximum number of mounts to infinite.Alternatively, replace the media with other media that still contains usefullife.

Media Manager status code: 117Message: operation not allowed on cleaning cartridge

Explanation: A request was made to change a volume’s expiration or maximumnumber of mounts. The operation is not allowed because the volume is a cleaningcartridge.

■ If the volume is a cleaning cartridge, perform a valid operation such as changingthe number of cleanings that remain for the cleaning cartridge.

■ If the volume’s media type cannot be determined, examine command output,debug logs, and system logs for a more detailed message on the error.See “Using debug logs” on page 423.

■ If the targeted volume is incorrectly configured as a cleaning tape, delete thecleaning volume. Then update the volume configuration using options to definea new volume with the appropriate media type.

Media Manager status code: 118Message: cannot delete one of the default volume pools

Explanation: An attempt was made to delete one of the special, pre-defined volumepools. The None, NetBackup, Catalog Backup, and DataStore volume pools arefixed volume pools in the volume pool configuration, and cannot be deleted.

Recommended Action: Do not attempt to delete the None, NetBackup, CatalogBackup, and DataStore volume pools.

Media Manager status code: 119Message: invalid rule database entry

Explanation: The bar code rule database is corrupt. It contains some records thatare not compatible with the installed product binaries.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

460

■ Use vmrule to investigate integrity of the bar code rule database. The daemondebug log file should indicate the number of expected fields and the numberof found fields in the bar code rule record. Restore a saved version of the barcode rule database if the bar code rule database cannot be manually corrected.

Media Manager status code: 121Message: failed appending to rule database

Explanation: A request was made to add, change, or delete a bar code rule. A barcode rule record cannot be appended to the bar code rule database file.

Recommended Action:

Examine the daemon debug log for a more detailed message on the system error.

See “Using debug logs” on page 423.

Media Manager status code: 122Message: barcode tag is not unique in rule database

Explanation: A request was made to add a bar code rule. The specified bar codetag was a duplicate of the tag for an existing bar code rule.

Recommended Action: On the add bar code rule request, specify a bar code tagthat is not already in use.

Media Manager status code: 126Message: not authorized to connect to vmd

Explanation: A caller requesting services from vmd is either not authenticatedor not authorized. Or a problem is encountered when two systems attempt toauthenticate one another.

■ See the NetBackup Security and Encryption Guide for information on vmdsecurity.vmd security is based on NetBackup authentication or authorization, but hasextensions for handling SERVER entries in the Media Manager configurationfile.

■ Examine the debug log files for a more detailed message on the authenticationor the authorization problem.See “Using debug logs” on page 423.

■ Correct the vmd security configuration by adjusting the authenticationconfiguration, the AUTHORIZATION_REQUIRED entry, and SERVER entries.

461Media and device management status codes and messagesAbout media and device management status codes and messages

■ If an authentication problem (rather than a configuration issue) is suspected,do the following:

■ Ensure that the authentication libraries exist:Windows:

install_path\NetBackup\lib\libvopie.dll

install_path\NetBackup\lib\libvnoauth.dll

UNIX and Linux (except HP-UX):

/usr/openv/lib/libvopie.so

/usr/openv/lib/libvnoauth.so

UNIX and Linux (HP-UX only):

/usr/openv/lib/libvopie.sl

/usr/openv/lib/libvnoauth.sl

■ Check the methods_allow.txt files on the systems that have problems toensure that authentication is enabled. The files are in the followinglocations:Windows: install_path\NetBackup\var\auth

UNIX and Linux: /usr/openv/var/auth

■ On the systems that have the authentication problem, remove the remotehost that is not authenticated from the methods_allow.txt file.

For example, if Host A and Host B have the problem, remove Host A fromthe file on Host B, and vice versa.Retry the operation.If the problem still exists, the connection problems are not related toauthentication.If connections are successful, proceed to the next step.Run bpauthsync -vopie on the master server to synchronize the key fileson the systems again.On Windows:

install_path\NetBackup\bin\admincmd\bpauthsync -vopie

-servers

On UNIX and Linux:

/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers

■ Add back the removed hosts and retry the operation.

Media and device management status codes and messagesAbout media and device management status codes and messages

462

Media Manager status code: 127Message: unable to generate a unique media id

Explanation: A request was made to add volumes in the volume configurationby using robot inventory update or by using a media ID seed. A unique media IDwas not generated because the "use seed" option was not specified, or because theavailable media ID combinations were used up.

Recommended Action: If you use robot inventory update, ensure that all mediain the robotic library have readable bar code labels. Or request updates by usinga seed to generate media IDs for non-barcoded media automatically. If volumesare added by specifying a seed, use a seed that allows media ID charactercombinations beyond those already in use. To identify the slot that is associatedwith the media that may not have a readable bar code, examine the commandoutput.

Media Manager status code: 129Message: invalid drive name

Explanation: A request was made to the EMM/DA for a shared drive, and thedrive name was not recognized.

■ Examine the daemon and reqlib debug logs for a more detailed message on theerror.See “Using debug logs” on page 423.

■ Ensure that the drive name is from 1 to 48 ASCII characters in length. Thefollowing special characters are allowed: period (.), plus (+), minus (-), andunderscore (_).

■ Verify that the correct version of software is running on all servers.

Media Manager status code: 130Message: requested drive is already reserved

Explanation: A request was made to reserve a shared drive with the EMM/DA,and the drive was already reserved for another host.

This error is a normal occurrence when drive resources are oversubscribed foreither of the following reasons:

■ Independent schedulers or applications access the same pool of drives

■ Hardware or media errors cause some drives that are allocated to jobs to becomeunavailable.

463Media and device management status codes and messagesAbout media and device management status codes and messages

■ Check the system log and application (bptm) debug log to determine if hardwareor media errors have caused drives to become unavailable.

■ If more information is needed on the drive reservation problem, examine thefollowing for a more detailed message on the error: command output, debuglogs, and system logs.See “Using debug logs” on page 423.

Media Manager status code: 131Message: requested drive is not registered for host

Explanation: A request was made to reserve a shared drive with the EMM server.The requesting host did not register the drive, although that host had registeredother drives.

This abnormal condition can occur in the following situation: two different hostswith the same name registered different drive lists with the EMM server and oneof those hosts requested a drive reservation. (The same host name occurs whenSSO_HOST_NAME entries in the vm.conf file override the local host name.)

Recommended Action: Use unique (non-duplicate) strings for host names andSSO_HOST_NAME configuration file entries.

Media Manager status code: 132Message: requested drive is not currently registered

Explanation: A request was made to reserve or release a shared drive with theEMM server. The requesting host or any other host has not registered the drive.

Recommended Action: This condition is abnormal. It can occur in the followingsituation: the EMM server was stopped and restarted. This situation isautomatically handled, because the requesting host re-registers its drives withthe EMM server when this error is encountered.

Media Manager status code: 133Message: requested drive is not reserved by host

Explanation: A request was made to release a shared drive with the EMM server.The requesting host did not reserve the drive, although it was reserved for anotherhost.

This condition is abnormal. It can occur if a network problem or a suspendedprocess exists. The following are possible scenarios:

■ Host A reserves a shared drive.

Media and device management status codes and messagesAbout media and device management status codes and messages

464

■ Host A becomes unavailable for some time, unable to communicate with otherhosts.

■ Host B determines that the host having the reservation (Host A) is no longeravailable. Host B then makes a request to the EMM/DA denoting Host A asunavailable.

■ Some other host (such as Host A or Host C) reserves the drive.

■ The host that originally owned the drive reservation tries to release the drive.

Recommended Action: Correct the network or the process problem that led tothe communications problem. Ensure that unique non-duplicate strings are usedfor host names and for SSO_HOST_NAME configuration file entries.

Media Manager status code: 134Message: requested drive is not currently reserved

Explanation: A request was made to the EMM/DA to release a shared drive, butnone of the hosts reserved the drive.

This condition is abnormal. It can occur if there a network problem or a suspendedprocess exists. The following are possible scenarios:

■ Host A reserves a shared drive.

■ Host A becomes unavailable for some time, unable to communicate with otherhosts.

■ Host B determines that the host having the reservation (Host A) is no longeravailable. Host B then makes a request to the EMM/DA denoting Host A asunavailable.

■ The host that originally owned the drive reservation tries to release the drive.

Recommended Action: Correct the network or the process problem that led tothe communications problem. Ensure that unique non-duplicate strings are usedfor host names and for SSO_HOST_NAME configuration file entries.

Media Manager status code: 135Message: requested host is not currently registered

Explanation: A request was made to the EMM/DA to reserve or release a shareddrive or designate a host as unavailable. The host (that reserved or released thedrive or that was designated as unavailable) was not registered with the EMM/DA.

This condition is abnormal and can occur in the following situations.

465Media and device management status codes and messagesAbout media and device management status codes and messages

■ The EMM server was stopped and restarted. This situation is automaticallyhandled, because the requesting host re-registers its drives with the EMMserver when this error is encountered.

■ A host was unregistered with the EMM server, and another host declared thehost to be unavailable.

RecommendedAction: If the host was declared unavailable, determine whetherit should be available. Correct the underlying network problems or restart ltid(the device daemon on UNIX and Linux or NetBackup Device Manager service onWindows).

Media Manager status code: 136Message: invalid host name

Explanation: A device host was added to the Media Manager configuration. Or arequest was made to the EMM server and the host name exceeded the allowablelength.

Recommended Action: Limit host names to 256 ASCII characters or less.

Media Manager status code: 137Message: oprd request is not supported on the remote host

Explanation: An invalid request was sent to the operator request process.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Identify the targeted host. Verify that all Media Manager binaries on that hostare at a compatible version level with other hosts that are part of theconfiguration. Update the software version as needed.

Media Manager status code: 138Message: media generation rule already exists

Explanation: You or a NetBackup media management interface attempted to adda MEDIA_ID_BARCODE_CHARS rule that already exists. The same rule cannotbe added twice.

RecommendedAction: Examine the listing of the MEDIA_ID_BARCODE_CHARSrules again.

A description of MEDIA_ID_BARCODE_CHARS rules is available.

See Reference Topics in the NetBackup Administrator’s Guide, Volume II.

Media and device management status codes and messagesAbout media and device management status codes and messages

466

Media Manager status code: 139Message: media generation rule does not exist

Explanation: You or a NetBackup media management interface attempted todelete a MEDIA_ID_BARCODE_CHARS rule that does not exist.

Recommended Action: Examine a listing of the MEDIA_ID_BARCODE_CHARSrules again.

For a description of MEDIA_ID_BARCODE_CHARS rules, refer to Reference Topicsin the NetBackup Administrator’s Guide, Volume II.

Media Manager status code: 140Message: invalid media generation rule

Explanation: You or a NetBackup media management interface attempted to addan incorrect MEDIA_ID_BARCODE_CHARS rule.

Recommended Action: Ensure that the MEDIA_ID_BARCODE_CHARS rule iscomposed correctly.

For a description of MEDIA_ID_BARCODE_CHARS rules, refer to Reference Topicsin the NetBackup Administrator’s Guide, Volume II.

Media Manager status code: 141Message: invalid number of mounts

Explanation: A request was made to change the number of times that a volumewas mounted, and the value specified was not within the acceptable range.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify a number of mounts value within the acceptable range of 0 to2,147,483,647.

Media Manager status code: 142Message: invalid offsite location

Explanation: The off-site location for a volume exceeds 25 ASCII characters inlength, or contains unprintable characters.

Recommended Action: When you add or change a volume record, ensure thefollowing: the off-site location field contains only printable characters and doesnot exceed 25 ASCII characters in length.

467Media and device management status codes and messagesAbout media and device management status codes and messages

Media Manager status code: 143Message: invalid offsite sent date

Explanation: A request was made to change the off-site sent date for one or morevolumes in the volume configuration, but the date specified was invalid.

RecommendedAction: When you change the off-site sent date, provide the datein the format that the Media Management interface documentation specified.

Media Manager status code: 144Message: invalid offsite return date

Explanation: A request was made to change the off-site return date for one ormore volumes in the volume configuration, but the date specified was invalid.

Recommended Action: When you change the off-site return date, provide thedate in the format that the Media Management interface documentation specified.

Media Manager status code: 145Message: requested drive is already reserved by host

Explanation: A request was made to the EMM/DA to reserve a shared drive. Thedrive was already reserved for the requesting host.

This condition is abnormal. It can occur if two different hosts with the same nameregistered the same drive name with the EMM/DA. (The same host name occurswhen SSO_HOST_NAME entries in the vm.conf file override the local host name.)In this case, one of those hosts has a drive reservation, and the other host triesto reserve the same drive.

RecommendedAction: Use unique non-duplicate strings for host names and forSSO_HOST_NAME configuration file entries.

Media Manager status code: 146Message: incompatible database version

Explanation: A requesting process or vmd encountered an invalid or an unknowndatabase or communications protocol. The possible data stores that an erroraffects are volume, volume pool, bar code rule, global device database, and shareddrive information.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

468

■ Identify the target components (for example, vmd and daemons or services,or user interfaces on local or remote hosts). Verify that all Media Managerbinaries are at a compatible version level. Depending on which requestsencountered the invalid version, determine whether or not the database iscorrupt. Use an appropriate interface to query for the type of information thatis involved in the error condition.

Media Manager status code: 147Message: invalid offsite slot

Explanation: A request was made to change the off-site slot location for a volume,and the value specified was not within the acceptable range.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify an off-site slot value within the range of 0 to 2,147,483,647.

Media Manager status code: 148Message: invalid offsite session id

Explanation: A request was made to change the off-site session ID for a volume,and the value specified was not within the acceptable range.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify an off-site session ID within the range of 0 to 2,147,483,647.

Media Manager status code: 149Message: current version does not support this configuration

Explanation: A request cannot be performed because it attempted to referenceunlicensed functionality. An example request: the attempt to add a volume witha media type that is not valid for the licensed product.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ List the license keys that were installed and verify that the referencedfunctionality is supported with the currently installed license keys. Check tosee that the databases that define externalized object types are in place andnot corrupted. These database files are the following, in the

469Media and device management status codes and messagesAbout media and device management status codes and messages

/usr/openv/var/global directory (UNIX and Linux) orinstall_path\NetBackup\var\global folder (Windows):

■ external_densities.txt

■ external_drivetypes.txt

■ external_mediatypes.txt

■ external_robotics .txt

Media Manager status code: 150Message: registering this host would exceed the maximum allowed

Explanation: The EMM/DA received a request to register shared drives from ahost that was not currently registered. The maximum number of hosts that areregistered with this EMM/DA were already reached. The current limit for thenumber of hosts that can register with the EMM/DA is 255.

■ Restrict the size of the SSO configuration to no more than 255 hosts.

■ Break up the media and the device management domain into multiple domains,with all domains having 255 or fewer hosts that register shared drives.

Media Manager status code: 152Message: global device database record not found

Explanation: A request was made to update a global device database record, andthe record specified was not found in the global device database. This conditioncan occur when a device configuration change is made after the global devicedatabase host has changed.

RecommendedAction: If the request to update the record fails because the recorddoes not exist, a request is made to add the missing record. No action is required.

Media Manager status code: 153Message: device entry is not unique in global device database

Explanation: A request was made to add a global device database record, and therecord specified was a duplicate of an existing record. This condition can occurif two processes update simultaneously the device configuration on the same host.

■ Coordinate changes to the device configuration so that changes come from asingle source.

■ Investigate the global device database changes on the server (database) sideby examining the daemon debug log file for a more detailed error message.

Media and device management status codes and messagesAbout media and device management status codes and messages

470

See “Using debug logs” on page 423.

Media Manager status code: 155Message: global device database append operation failed

Explanation: A request was made to change the device configuration, and a globaldevice database record cannot be written to the global device database file.

Recommended Action:

Examine the daemon debug log for a more detailed message on the error.

See “Using debug logs” on page 423.

Media Manager status code: 160Message: the global device database device type is invalid

Explanation: An invalid device type appears in a request to modify the deviceconfiguration.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Identify the targeted host. Verify that all Media Manager binaries on that hostare at a compatible version level with other hosts that are part of theconfiguration. Update the software version as needed.

Media Manager status code: 162Message: the global device database device name is invalid

Explanation: An invalid or a missing device name was encountered in a requestto modify the device configuration.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Identify the targeted host. Verify that all Media Manager binaries on that hostare at a compatible version level with other hosts that are part of theconfiguration. Update the software version as needed.

Media Manager status code: 163Message: the operation requested has failed

Explanation: The requested operation failed. The reason was not specified.

471Media and device management status codes and messagesAbout media and device management status codes and messages

Recommended Action: This error code may appear for a number of reasons.Examine command output, debug logs, and system logs for a more detailed messageon the error.

See “Using debug logs” on page 423.

Media Manager status code: 164Message: the robotic daemon returned an invalid volume GUID

Explanation: An invalid RSM GUID was returned from the RSM API. (RSM is theMicrosoft Removable Storage Manager. GUID is a Global Unique Identifier.)

■ Examine the system’s application log, the Removable Storage system interface,and the daemon and reqlib debug logs for a more detailed message on theerror.See “Using debug logs” on page 423.

■ Retry the operation and examine the logs. From the daemon debug log file,determine the media ID that has the invalid RSM GUID.

■ Make sure that the software components are compatible.

Media Manager status code: 165Message: Evaluation period expired. Go to www.symantec.com to order thisproduct.

Explanation: The NetBackup evaluation software has expired.

See the address in the message or www.symantec.com/enterprise/ for orderinginformation.

Recommended Action: Obtain a licensed copy of NetBackup.

Media Manager status code: 166Message: media access port not available

Explanation: A request was made to physically move a volume into or out of arobotic library, but the media access port was unavailable.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that the move request was not sent to a robotic control daemon orprocess on a system that runs an older, incompatible software version.

■ Ensure that the targeted robotic control daemon or process operates normally.

Media and device management status codes and messagesAbout media and device management status codes and messages

472

Media Manager status code: 167Message: ADAMM GUID is not unique in the database

Explanation: A volume entry that was added to or changed in the EMM databasehad a specified ADAMM GUID. It was a duplicate of the ADAMM GUID for anothervolume already in the EMM database. All volumes in the EMM database must havean ADAMM GUID that is either unique or null. (ADAMM is Advanced Device andMedia Management, and a GUID is a Global Unique Identifier.)

■ Examine command output (if available) and the daemon and reqlib debug logsfor a more detailed message on the error.See “Using debug logs” on page 423.

■ From the daemon debug log file, determine the volume that has an ADAMMGUID conflict with the volume entry that is added or changed.

Media Manager status code: 168Message: ADAMM GUID does not exist in database

Explanation: The EMM database was queried for a specified ADAMM (AdvancedDevice and Media Management) GUID, and no volumes were found matching thespecified criteria. (The GUID is a Global Unique Identifier.)

Recommended Action:

Run vmphyinv for the media whose ADAMM GUID does not exist in the database.

Media Manager status code: 169Message: internal database access failure

Explanation: During an update of a drive status from a pre-6.0 NetBackup serverin EMM, a problem occurred.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively running and that it accepts new connections.

Media Manager status code: 171Message: a scratch pool is already defined

Explanation: A new scratch pool cannot be defined because another scratch poolalready exists.

473Media and device management status codes and messagesAbout media and device management status codes and messages

Recommended Action:

Use the scratch pool already defined, or delete the current scratch pool and createa new scratch pool.

Media Manager status code: 172Message: pool not defined as a scratch pool

Explanation: You or a NetBackup media management interface have tried todelete (unset) a scratch pool that is not defined as a scratch pool.

Recommended Action: To delete the scratch pool, use the vmpool command.Make sure that the name of the pool that is specified with the unset_scratch

option is the correct name of the scratch pool.

Media Manager status code: 173Message: invalid scratch pool name

Explanation: You, or a NetBackup media management interface have tried tospecify the NetBackup, DataStore, or None pool as a scratch pool. The NetBackup,DataStore, and None pools cannot be specified as scratch pools.

Recommended Action: Create a scratch pool with a different name.

Media Manager status code: 175Message: unable to open the device test state file

Explanation: The process is not able to open the state file, mostly likely becauseanother process locked it.

Recommended Action:

Try again to open the state file. If you cannot open the state file, you may have toremove the file, which would result in a loss of previous test runs.

Media Manager status code: 176Message: unable to find any records in the device test database

Explanation: The state file exists, but it is empty. This error indicates that noprevious test runs have occurred.

Recommended Action: None required.

Media and device management status codes and messagesAbout media and device management status codes and messages

474

Media Manager status code: 177Message: request can only be performed on the Media and Device ManagementDomain Server

Explanation: The host this request was performed on is blocked from being adatabase host. An administrator blocked the host to restrict which hosts areallowed to be EMM servers.

■ Verify that you specified the correct EMM server (the -h option on the commandline). If you did not specify the database host, the command line defaults tothe local host, while the console uses the currently administered host.

■ Contact the administrator in charge of this configuration and verify that thehost was intentionally blocked from being a database host. If not, remove theNOT_DATABASE_HOST flag in the host’svm.conf file. To do so without havingto stop and restart the daemons, use:vmquery -h <hoostname> -remove_not_db_host.

To add this entry to a host without having to stop and restart the daemons,use: vmquery -h <hostname> -add_not_db_host.

Media Manager status code: 181Message: not authorized to connect to robotic daemon

Explanation: A caller requesting services from a robotic daemon is notauthenticated or authorized. Or when two systems try to authenticate one another,a problem occurs.

■ See the NetBackup Security and Encryption Guide for information on MediaManager security.Media Manager security is based on NetBackup authentication andauthorization, but has extensions for handling SERVER entries in the MediaManager configuration file.

■ Examine the debug log files for a more detailed message on the authenticationand authorization problem.See “Using debug logs” on page 423.

■ Determine whether authorization fails on vmd. Examine the debug log files forMedia Manager status code 126 occurrences ("not authorized to connect tovmd").

■ Correct the Media Manager security configuration by adjusting theauthentication configuration, the AUTHORIZATION_REQUIRED entry, theENABLE_ROBOT_AUTH entry, and the SERVER entries.

475Media and device management status codes and messagesAbout media and device management status codes and messages

■ If an authentication problem (rather than a configuration issue) is suspected,do the following:

■ Ensure that the authentication libraries exist:Windows:

install_path\NetBackup\lib\libvopie.dll

install_path\NetBackup\lib\libvnoauth.dll

UNIX and Linux (except HP-UX):

/usr/openv/lib/libvopie.so

/usr/openv/lib/libvnoauth.so

UNIX and Linux (HP-UX only):

/usr/openv/lib/libvopie.sl

/usr/openv/lib/libvnoauth.sl

■ Check the methods_allow.txt files on the systems that have problems toensure that authentication is enabled. The files are in the followinglocations:Windows: install_path\NetBackup\var\auth

UNIX and Linux: /usr/openv/var/auth

■ On the systems that have the authentication problem, remove the remotehost that is not authenticated from the methods_allow.txt file and retrythe operation.For example, if Host A and Host B have the problem, remove Host A fromthe file on Host B, and vice versa.If the problem still exists, the error is caused by connection problems notrelated to authentication.If connections are successful after you remove the host, run bpauthsync

-vopie on the master server to synchronize the key files on the systemsagain.On Windows:

install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers

On UNIX and Linux:

/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers

Add the removed names and retry the operation.

Media and device management status codes and messagesAbout media and device management status codes and messages

476

Media Manager status code: 182Message: device test state file does not exist

Explanation: The state file does not exist. The reason may be because no testshave been run yet.

RecommendedAction: If the state file is lost, any previous test runs are also lost.The recommended action is to start again.

Media Manager status code: 185Message: the robotic library is full and may still have media in its map

Explanation: During a robot inventory update, the user attempted to use theempty_map option. The MAP contained more media than the library had spacefor. In this case, the inventory update was successful, the empty_map part wasonly partially successful. Those media still in the MAP are not changed or addedin the EMM database.

Recommended Action: No action is necessary on the user’s part except to beaware that not all of the media was removed from the MAP and placed into thelibrary.

Media Manager status code: 186Message: invalid container id

Explanation: A NetBackup Vault container ID was used with an invalid character.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Retry the operation with a container ID that does not contain invalid characters.

Media Manager status code: 187Message: VxSS authentication failed

Explanation: The parties on either end of a socket connection cannot mutuallyauthenticate each other.

■ Ensure that the Veritas Security Services is installed and configured.For complete installation instructions, see the Veritas Security ServicesInstallation Guide.

■ Check that both parties have a valid certificate by examining the listed expirydate from a bpnbat -WhoAmI. For example:

477Media and device management status codes and messagesAbout media and device management status codes and messages

bpnbat -WhoAmI

Name: JDOG

Domain: MYCOMPANY

Issued by: /CN=broker/[email protected]/O=vx

Expiry Date: Sep 19 12:51:55 2003 GMT

Authentication method: Microsoft Windows

Operation completed successfully.

■ Shows an expiry date of September 19th, 2003. After 12:51:55 GMT thiscredential is no longer valid and a new credential is required.

■ If you are running from the NetBackup Administration console, close andreopen the console. The console automatically obtains a credential for thecurrently logged in identity, if possible. By default these certificates are validfor 24 hours. To set a longer default time, consult the following:See the NetBackup Security and Encryption Guide.

■ Ensure that the certificates for both sides either use the same broker, arechildren of the same root broker, or have trusts established between them.More information is available on broker hierarchies and how to establish trustrelationships between brokers.See the NetBackup Security and Encryption Guide.

■ Ensure that connectivity is possible between the physical systems in question.If general sockets cannot connect between the machines (such as ping andtelnet), network issues unrelated to NetBackup may be the cause of thisproblem.

■ Ensure that the system has sufficient swap space and the following directoriesare not full:

■ /home/username

■ /user/openv/netbackup/logs

■ /tmp

Media Manager status code: 188Message: VxSS Access Denied

Explanation: The user identity that is used to attempt an operation does not havethe permissions needed to perform the action.

■ If you use the default groups, make certain that the user attempts to performan operation appropriate for that group. For example, a member ofNBU_Operators is unable to modify policy information, a permission reservedfor administrator roles.

Media and device management status codes and messagesAbout media and device management status codes and messages

478

■ Ensure that the system has sufficient swap space and the following directoriesare not full:

■ /home/username

■ /user/openv/netbackup/logs

■ /tmp

■ If you use your own defined groups and permissions, first determine the objectwith which the operation is associated. Then add the permissions relative tothe action. For example, a user is required to up and down drives but does notcurrently have permission to do so. Verify that the user belongs to the correctauthorization group.If necessary, verify that the group has Up and Down permissions on the Driveobject within the Group Permission tab. If necessary, you can increase theverbosity level of NetBackup to locate what object and what permissions arerequired for the failing request. The pertinent lines in the debug logs looksimilar to the following:

17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.

Name: JMIZZLE

Domain: MYCOMPANY

Expiry: Sep 24 21:45:32 2003 GMT

Issued by: /CN=broker/[email protected]/O=vx

AuthType: 1

17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:

Function: VssAzAuthorize. Object

NBU_RES_Drives

17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:

Function: VssAzAuthorize. Permissions Up

17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:

Function: VssAzAuthorize. 20 Permission denied.

In the example, the user JMIZZLE attempts to perform an operation thatrequires the Up permission on the Drives object. To diagnose the problem,examine the group(s) to which the user belongs to ensure that the appropriategroup includes the Up permission. (Up is a member of the Operate permissionset for Drives.)

Media Manager status code: 189Message: failed to initialize a connection to the Enterprise Media Manager

Explanation: A request to initialize a connection with the EMM server failed orwas already initialized.

479Media and device management status codes and messagesAbout media and device management status codes and messages

■ Verify that pbx_exchange and nbemm are running.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively running and that it accepts new connections.

Media Manager status code: 190Message: the request sent to the Device Allocator has failed

Explanation: A request to reserve or release a drive with the DA (EMM server)failed.

■ Verify that pbx_exchange and nbemm are running.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively running and that it accepts new connections.

■ For a DA reserve drive request, verify that another host had not alreadyreserved the drive.

■ For a DA release drive request, verify the following: that the drive is DAreserved by the host requesting the DA release and has not already beenreleased.

Media Manager status code: 191Message: invalid EMM argument

Explanation: An invalid argument was provided on a call to the EMM server.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

Media Manager status code: 192Message: unknown EMM error code

Explanation: An unknown error was returned from the EMM server.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

Media and device management status codes and messagesAbout media and device management status codes and messages

480

See “Using debug logs” on page 423.

Media Manager status code: 193Message: generic EMM SQL error

Explanation: The EMM server received an error from the underlying database.

Recommended Action:

Examine command output, debug logs, and system logs for a more detailed messageon the error.

See “Using debug logs” on page 423.

Media Manager status code: 194Message: EMM DB record not found

Explanation: During a NetBackup upgrade a pre-requisite host was not upgradedin the correct order.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the proper upgrade order is followed as described in theNetBackupInstallation Guide.

Media Manager status code: 195Message: CORBA communication error

Explanation: While trying to communicate with the EMM server, a problemoccurred.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that Symantec Private Branch Exchange (VxPBX) processes new requests.

■ Verify that the EMM server processes new requests.

Media Manager status code: 196Message: EMM database error

Explanation: The calling program does not recognize the error the EMM serverreturned.

481Media and device management status codes and messagesAbout media and device management status codes and messages

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the EMM server processes new requests.

Media Manager status code: 198Message: pool not defined as a catalog backup pool

Explanation: An attempt was made to remove the Catalog Backup attribute froma pool in which it was not set.

Recommended Action: Verify that the appropriate pool name was used in thisoperation.

Media Manager status code: 199Message: the media is allocated for use

Explanation: A request was made to modify a media that was in use.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Retry the operation once the media is no longer in use.

Device configuration status codesDevice configuration status codes appear in exit status and command output forthe tpconfig and the tpautoconf commands, and in system or debug logs.Programs that call tpconfig and tpautoconf, such as media and devicemanagement user interfaces and thevmoprcmd command, also present these codes.

Device configuration status code: 0Message: Success

Explanation: A requested operation was successfully completed.

Recommended Action: None.

Device configuration status code: 1Message: Cannot execute command, permission denied

Media and device management status codes and messagesAbout media and device management status codes and messages

482

Explanation: A user or process that did not have root privileges (on UNIX andLinux) or administrator privileges (on Windows) started the process. Or the EMMserver name cannot be set.

■ If appropriate, give the user or the process administrator privileges (onWindows) or root privileges (on UNIX and Linux) and reissue the deviceconfiguration request.

■ Establish a common EMM server name as follows:

■ Run tpautoconf -get_gdbhost on other hosts.

■ Set the EMM server name with

tpautoconf -set_gdbhost host_name

wherehost_name is the host name returned by tpautoconf -get_gdbhost.

Device configuration status code: 2Message: The device_mappings file has invalid license info

The problem concerns one of the following files:/usr/openv/share/device_mappings.txt (UNIX and Linux) orinstall_path\VERITAS\NetBackup\share\device_mappings.txt (Windows).

■ The file does not exist.

■ The file is for a different version of NetBackup. You can find what version itis for by reading the header in the file.

■ The file has a corrupted licensing digest.

Recommended Action: Download the latest device mapping file from theSymantec support website at www.support.symantec.com.

Device configuration status code: 3Message: Could not get hostname

Explanation: An attempt to look up the host name for this host failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the host name is resolvable.

Device configuration status code: 7Message: Invalid SCSI port number for the robot

483Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: A request was made to add or change the SCSI port number for arobot, but the SCSI port number provided was not valid.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify the correct SCSI port number for the robot. Perform device discoveryby using the Device Configuration wizard, or check the Windows registry asneeded to obtain the SCSI port number.

Device configuration status code: 8Message: Invalid SCSI bus number for the robot

Explanation: A request was made to add or change the SCSI bus number for arobot, but the SCSI bus number provided was not valid.

RecommendedAction: Specify the correct SCSI bus number for the robot. Performdevice discovery by using the Device Configuration wizard, or check the Windowsregistry as needed to obtain the SCSI bus number.

Device configuration status code: 9Message: Invalid SCSI target for the robot

Explanation: A request was made to add or change the SCSI target for a robot,but the SCSI target provided was not valid.

Recommended Action: Specify the correct SCSI target for the robot. Performdevice discovery by using the Device Configuration wizard, or check the Windowsregistry as needed to obtain the SCSI target.

Device configuration status code: 10Message: Invalid SCSI logical unit number for the robot

Explanation: A request was made to add or change the SCSI logical unit numberfor a robot, but the SCSI logical unit number was not valid.

RecommendedAction: Specify the correct SCSI logical unit number for the robot.Perform device discovery by using the Device Configuration wizard, or check theWindows registry as needed to obtain the SCSI logical unit number.

Device configuration status code: 11Message: Invalid Usage

Media and device management status codes and messagesAbout media and device management status codes and messages

484

Explanation: One of the Media Manager device configuration commands (tpconfigor tpautoconf) was executed with improper options. Or an incompatibility existsbetween components or versions of the product.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the tpconfig or the tpautoconf usage statement for expected usageand compare with the parameters being sent to start the new process.

■ Verify that all Media Manager binaries are at a compatible version level.

Device configuration status code: 13Message: Failed reading drive or robot config file

Explanation: A request was made to list the device configuration, but an errorwas encountered while reading from the EMM database.

■ Examine the daemon debug log and system logs for a more detailed messageon the error.See “Using debug logs” on page 423.

■ Verify that nbemm is running. Display the device configuration to determinewhether or not the database is corrupt. Restore a saved copy of the databasesfrom catalog backups, or delete them and recreate the device configuration asneeded.

Device configuration status code: 14Message: Invalid drive index

Explanation: A request was made to add, update, or list a drive configurationentry, and the specified drive index was not associated with a configured drive.

■ Display the device configuration to obtain the list of valid drives. Avoid makingdevice configuration changes from multiple sources simultaneously.

■ If more information is needed, examine the daemon debug log and commandor interface output for a more detailed message on the error.See “Using debug logs” on page 423.

Device configuration status code: 15Message: Invalid robot number

Explanation: On a request to modify the device configuration, the followingoccurred: the specified robot number was not within the allowable range, the

485Media and device management status codes and messagesAbout media and device management status codes and messages

robot number did not correspond to a currently configured robot, or the roboticdatabase is corrupted.

■ Specify a robot number in the range of 0 to 32767.

■ Ensure that all device configuration changes or deletions are performed onthe devices that are currently part of the device configuration.

■ Verify that nbemm is running. Restore a saved copy of the robotic databasefrom catalog backups, or delete it and recreate any needed robotic configurationinformation.

Device configuration status code: 16Message: A SCSI inquiry sent to the device has failed

Explanation: On a request to add or update a SCSI robotic library or drive, MediaManager cannot obtain the device’s serial number and inquiry string. MediaManager is obtains this information by sending a SCSI Inquiry command to thedevice. Failure indicates that NetBackup was not able to communicate with thedevice by means of SCSI.

■ Ensure that the device is physically connected.

■ Ensure that the operating system is configured to recognize the device andthat the operating system can see the device.

■ Ensure that no other process uses the device and that the device is not offline.

Device configuration status code: 17Message: This robot type does not support multiple media types

Explanation: An attempt to add or update a robotic drive failed because the drivesin this robotic library are configured with a different drive type. (Some NetBackuprobotic library types do not support multiple media types.)

Refer to theNetBackup Release Notes or to theNetBackup Administrator's Guide,Volume II, for more information on which NetBackup robotic library types supportmultimedia.

■ Configure all drives for this robotic library with the same drive type.

■ If you use NetBackup Server and want a robotic library with multiple mediatypes, contact Symantec to purchase NetBackup Enterprise Server.

Device configuration status code: 18Message: Invalid robot type

Media and device management status codes and messagesAbout media and device management status codes and messages

486

Explanation: On a request to modify the device configuration, the specified robottype was invalid. Or it did not match the robot type for the robot that is associatedwith the specified robot number.

■ Check the device configuration for configured robots, and specify the correctrobot type applicable for the device configuration information being updated.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that all Media Manager binaries are at a compatible version level.

Device configuration status code: 19Message: Invalid device path name

Explanation: On a request to change the device configuration, the specified devicepath or device name was not valid.

■ To avoid configuring invalid device paths and device names, use the DeviceConfiguration wizard (on supported device discovery platforms). The wizardautomatically configures device paths and device names.

■ On Windows hosts, check the operating system configuration or registry fordevice names and refer to the tpconfig command in NetBackup online help.Information for UNIX and Linux hosts is availableSee the NetBackup Device Configuration Guide.Always use no-rewind device files for drives that are attached to UNIX andLinux hosts. Check to ensure that the specified device paths exist ascharacter-special files. Check for detailed errors from the command or theuser interface output.

Device configuration status code: 21Message: Robot number is already in use

Explanation: On a request to add a robot to the device configuration, the robotnumber was found to be already in use for a different robot.

Recommended Action: Check the device configuration on all device hosts forconfigured robots, and specify a robot number that is not already in use. Use thefollowing to display all devices in the EMM database:

tpconfig -emm_dev_list

487Media and device management status codes and messagesAbout media and device management status codes and messages

Device configuration status code: 22Message: Device path is already in use

Explanation: On a request to add or change robot information in the deviceconfiguration, the specified robotic device path is in use for another configuredrobot.

■ To avoid configuring the device paths that are already in use, use the DeviceConfiguration wizard (on supported device discovery platforms). The wizardautomatically configures device paths and device names.

■ Display the device configuration using tpconfig -d or a device configurationinterface to see the robotic information that is already configured. Windowshosts have multiple ways to configure robots (changer names or port, bus,target, LUN). Check the operating system configuration or registry for changernames and their associated SCSI paths. Check for detailed errors from thecommand or the user interface output.

Device configuration status code: 24Message: Incomplete robot information

Explanation: On a request to change the device configuration, some of the requiredrobot information was not specified.

Recommended Action: Check the command usage and reissue the request withall required robot information specified.

Device configuration status code: 25Message: Robot drive number in use for this robot

Explanation: On a request to change the device configuration, the specified driveaddress in the robot is in use by another drive in the device configuration.

RecommendedAction: The drive address in the robot is the following: the robotdrive number for most robot types, the ACS/LSM/PANEL/DRIVE coordinates forACS robots, or a vendor drive name for TLH and TLM robots. Two drives cannothave the same drive address in a robot in a given device configuration. If the driveaddresses need to be adjusted, delete one of the drives or make use of an unuseddrive address as a temporary state. For example, a robot has two drives with robotdrive numbers 1 and 2 that need to be swapped. Change one drive to use robotdrive number 3 temporarily. Then change the other drive to use robot drive number1 or 2 as appropriate. Finally, change the first drive to the open robot drive address1 or 2.

Media and device management status codes and messagesAbout media and device management status codes and messages

488

Device configuration status code: 27Message: Invalid drive type for the robot

Explanation: On a request to configure a drive to be in a robot, the drive type wasnot valid for the selected robot type.

RecommendedAction: Check the Robot Attributes tables in the following manualto determine valid media types for a given robot type:

See the NetBackup Device Configuration Guide.

Drive types directly correspond to the listed media types. Configure supporteddevices so that invalid combinations of drive types and robot types are notrequired.

Device configuration status code: 28Message: Invalid robot drive number for the robot type

Explanation: On a request to configure a drive to be in a robot, the robot drivenumber was not valid for the selected robot type.

Recommended Action: The robot drive number (for ACS robots, the set of ACSdrive identifiers) is limited to the ranges that are based on the robot type. Theselimits are based on a supported device list. An invalid robot drive number meansthat the drive number was not within the acceptable range. Make sure that therobot hardware is supported and that the required patches are installed to supportthe robotic library. If the robot type is TLH or TLM, do not specify a robot drivenumber because the drives are addressed with a vendor drive name.

Device configuration status code: 29Message: Drive index is in use by another drive

Explanation: On a request to add a drive to the device configuration, the requesteddrive index was in use on the targeted device host.

■ To avoid configuring a drive index that is already in use, use the DeviceConfiguration wizard (on supported device discovery platforms). The wizardautomatically configures the drive index.

■ If you use a device configuration interface that allows the drive index to bespecified, do the following: use tpconfig -d to determine the drive indexesalready in use on the targeted device host. Then specify a drive index that isnot in use.

489Media and device management status codes and messagesAbout media and device management status codes and messages

Device configuration status code: 30Message: Robot number is in use by another robot

Explanation: On a request to add or update a robotic drive in the deviceconfiguration, the following occurred: the robot number and robot type specifiedwere associated with an existing robot of a different robot type.

Recommended Action: Check the device configuration on the targeted devicehost and identify the configured robots. On the drive configuration request, specifyboth the robot number and robot type that relate to the robot that contains thedrive.

Device configuration status code: 31Message: Robot number does not exist

Explanation: On a request to add or update a drive or robot in the deviceconfiguration, the following occurred: the robot number and robot type specifiedwere not associated with any configured robots on the targeted device host.

Recommended Action: Check the device configuration on the targeted devicehost and identify the configured robots. Every drive that is configured as a roboticdrive must already have its robot configured on that device host. Shared roboticlibraries having robotic control on a remote host must have a logical robotic entrythat refers to the remote host having robotic control. Add the robot to the deviceconfiguration first. Then add the drive. Define it to be in the robot. If the robotwas already configured, specify the correct robot number and robot type on thedrive or the robot configuration request.

Device configuration status code: 33Message: Robot type must be controlled locally

Explanation: On a request to add or update a robot in the device configuration,the following occurred: a remote control host was specified for a library typewhich does not support it.

■ Check that you configured the correct robot type.

■ Configure the device with local control by using its local device path.

Device configuration status code: 34Message: Drive name is already in use by another drive

Explanation: On a request to add or update a drive in the device configuration,the requested drive path was in use on the targeted device host.

Media and device management status codes and messagesAbout media and device management status codes and messages

490

■ To avoid configuring any paths that are already in use, use the DeviceConfiguration wizard (on supported device discovery platforms). The wizardautomatically configures the drive paths.

■ Before you make configuration changes, check the existing drive configurationthrough a device configuration interface. Or run tpconfig -d to determinethe drive paths that are already in use on the targeted device host. Then specifya drive path that is not already in use.

Device configuration status code: 35Message: Drive name does not exist

Explanation: On a request to update or delete a drive in the device configuration,the following occurred: no drives having the specified drive name were found onthe targeted device host.

Recommended Action: Check the device configuration on the targeted devicehost and identify the configured drives. When you make drive configurationchanges or deletions, specify the drive name as it is configured. Take care to usethe proper case.

Device configuration status code: 36Message: <NONE>

Explanation: On a request to make a device configuration change, an erroroccurred. A detailed message appears in the command or the utility interfaceoutput.

■ Examine the daemon debug log and command or interface output for a moredetailed message on the error.See “Using debug logs” on page 423.

■ Retry the device configuration request and examine the logs.

Device configuration status code: 37Message: Residence is not licensed for shared drive support

Explanation: On a request to add or update a drive in the device configuration,the drive was specified as shared. No support for shared drives exists for thatdrive type or for the type of robot that is associated with the drive.

Recommended Action: Check www.veritas.com and product releasedocumentation for supported device configurations.

491Media and device management status codes and messagesAbout media and device management status codes and messages

Device configuration status code: 38Message: Current version does not support remote device host

Explanation: On a request to change the EMM server, the specified host is notthe local host. The current software is not licensed to allow remote hosts.

Recommended Action: Check product documentation for supported deviceconfigurations. Obtain an additional software license that allows remote hosts tobe configured, or specify only local host names on the configuration request.

Device configuration status code: 39Message: Adding this drive would exceed the maximum allowed

Explanation: On a request to add a drive to the device configuration, the followingoccurred: the licensed limit for the maximum number of drives was reached onthe targeted host.

Recommended Action: Check product documentation for supported deviceconfigurations. Obtain an additional software license that allows more drives tobe configured.Or limit the configuration to the number of drives that the currentlicensing allows.

Device configuration status code: 40Message: Adding this device would exceed the maximum allowed

Explanation: On a request to add a robot to the device configuration, the followingoccurred: the licensed limit for the maximum number of robots was reached onthe targeted host.

Recommended Action: Check product documentation for supported deviceconfigurations. Obtain an additional software license that allows more robots tobe configured. Or limit the configuration to the number of robots that the currentlicensing allows.

Device configuration status code: 41Message: Cannot change terminal mode

Explanation: When an attempt was made to change the mode for terminal inputbetween cooked and raw, a system call failed.

Recommended Action: Examine the user interface output for the system errorthat is associated with the failed system call. Then troubleshoot according tooperating system vendor recommendations.

Media and device management status codes and messagesAbout media and device management status codes and messages

492

Device configuration status code: 42Message: Cannot create miscellaneous working repository

Explanation: On a device configuration request, the miscellaneous workingdirectory or folder is not present and cannot be created.

RecommendedAction: Find out why /usr/openv/volmgr/misc (UNIX and Linux)or install_path\volmgr\misc (Windows) cannot be created. On Windows,determine which accounts the NetBackup Volume Manager service and deviceconfiguration interfaces are running under. Compare them with the securityproperties of the database folder. On UNIX and Linux, determine whether usersor device configuration interface callers are running under a user and group withpermissions to create the miscellaneous directory.

Device configuration status code: 44Message: Cannot discover devices. See the Troubleshooting Guide for details.

Explanation: Device discovery cannot obtain or verify its lock file or had a problemwith the EMM server.

■ Examine the daemon debug log and command or interface output for a moredetailed message on the system error.See “Using debug logs” on page 423.

■ Retry the operation and examine the logs. One of the following may haveoccurred:

■ Lock file problems: The device discovery process sets a lockfile in the/usr/openv/volmgr/misc (UNIX and Linux) orinstall_path\Volmgr\misc(Windows) directory named tpac.lock. It sets the lockfile to ensure thatonly one instance of discovery runs on a particular host. It then checks thelockfile before it updates the configuration.

■ Cannot obtain lockfile.The lockfile may be held by another discovery process. In this case thefollowing error is displayed:

"another tpautoconf is already running"

Use standard OS process tools (ps on UNIX and Linux or Task Manageron Windows) to determine if another tpautoconf process is running.If not, delete the lockfile and re-run device discovery. If anothertpautoconf process is running, wait for it to complete before retrying.

■ Failed the lockfile check.

493Media and device management status codes and messagesAbout media and device management status codes and messages

In the case of long device-discovery cycles, the interface may timeoutor the user may cancel the process. Part of the timeout or cancellationis to remove the lockfile. This action tells the device discovery processthat it should not continue making modifications to the deviceconfiguration. If action occurs, run the discovery process again.

Device configuration status code: 48Message: RSM is not supported.

Explanation: On a request to make a device configuration change, the RSM(Microsoft Removable Storage Manager) robot type was specified, but it is nolonger supported.

Recommended Action: Use a supported Media Manager robot type.

Device configuration status code: 49Message: global device database host name is invalid.

Explanation: On a device configuration request, the EMM server name cannotbe obtained.

The EMM server name is obtained through an internal request to read the bp.conffile (or Windows registry). This request is likely to fail if the EMMSERVER entryis not set.

RecommendedAction: Usetpautoconf -get_gdbhoston a device host to obtainits EMM server name. Usetpautoconf -set_gdbhost to set the EMM server name,as needed.

Device configuration status code: 51Message: No compatible device is registered at these SCSI coordinates.

Explanation: On a request to add or change robot or drive information in thedevice configuration, the following occurred: the specified SCSI coordinates didnot correspond to a device in the system registry. This status code applies toWindows systems only.

RecommendedAction: To avoid manually specifying SCSI coordinates (port, bus,target, and LUN), use the Device Configuration wizard. The wizard fully automates(on supported device discovery platforms) device configuration requests. Or usethe Media And Device Management interface to browse for devices in the systemregistry. Check the operating system registry to ensure that devices are presentat the specified coordinates when SCSI coordinates are manually configured.

Media and device management status codes and messagesAbout media and device management status codes and messages

494

Device configuration status code: 52Message: The device name is not valid, no device responded.

Explanation: On a request to add or change robot or drive information in thedevice configuration, the following occurred: no device was found in the systemregistry with the specified device name. This error code applies to Windowssystems only.

Recommended Action: To avoid manually specifying the device name, use theDevice configuration wizard. The wizard fully automates (on supported devicediscovery platforms) device configuration requests. Or use the Media And DeviceManagement interface to browse for devices in the system registry. Check theoperating system registry to ensure that devices are present at the specifiedcoordinates when devices are manually configured.

Device configuration status code: 53Message: Shared Storage Option (SSO) is not licensed

Explanation: An attempt to add a path to a drive failed. It failed because the SSOlicense was not installed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that an active SSO license is installed on the following: all servers thathave a path configured to this drive and the server where this operation isperformed.

Device configuration status code: 55Message: Invalid NDMP hostname

Explanation: An invalid hostname or no hostname was specified.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use tpconfig -dnh to verify that the host has been configured.

■ Check the usage of the tpautoconf -list_snapvault_volumes command.

Device configuration status code: 56Message: Invalid NDMP username

Explanation: An invalid username or no username was specified.

495Media and device management status codes and messagesAbout media and device management status codes and messages

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use tpconfig -dnh to verify that the host has been configured.

Device configuration status code: 57Message: Internal NDMP error

Explanation: An error occurs on the NDMP device.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the usage of the set_ndmp_attr -probe or tpautoconf -probe

commands.

■ An error occurs while trying to get the serial number and inquiry string for adevice connected to an NDMP filer. Verify that the device is properly attachedto the filer.

Device configuration status code: 58Message: NDMP failed to verify host

Explanation: An error occurs while using the NDMP verify functionality.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the usage of the tpautoconf -verify commands.

■ Verify that the device is properly attached to the filer.

Device configuration status code: 59Message: NDMP is not installed on platform

Explanation: The NDMP option is not installed on this server.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the NDMP option is properly installed and licensed.

■ Verify that NDMP is supported on the platform in question.

Media and device management status codes and messagesAbout media and device management status codes and messages

496

Device configuration status code: 60Message: Invalid NDMP password

Explanation: An invalid NDMP password or no password was provided.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the password is appropriate for the media server and filer pair.

■ Verify that the password was provided correctly on the command or in theNDMP Host dialog box.

Device configuration status code: 61Message: NDMP host exists, use change option

Explanation: An attempt to add a filer fails because the filer already exists in theEMM database.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use the -update option of tpconfig instead of -add.

Device configuration status code: 62Message: NDMP host does not exist

Explanation: The NDMP host does not exist in the EMM database.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use the -add -nh option on the tpconfig command to add the NDMP host.

Device configuration status code: 63Message: NDMP request failed

Explanation: An attempt to create an NDMP session failed, or an attempt to sendan NDMP message failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

497Media and device management status codes and messagesAbout media and device management status codes and messages

■ Verify NAS filer licenses, supported operating system levels, and networkconnectivity.

Device configuration status code: 64Message: Invalid NDMP device

Explanation: An invalid NDMP device was specified.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

Device configuration status code: 65Message: NDMP robot exists, use change option

Explanation: The robot currently exists in the EMM database.

Recommended Action: Use the NetBackup Administration Console, or thetpconfig -update -robot command, to change the robot configuration.

Device configuration status code: 66Message: NDMP robot does not exist

Explanation: An update request was issued for a non-existent robot.

Recommended Action: Use the NetBackup Administration Console, or thetpconfig -update -robot command, to add the correct robot.

Device configuration status code: 67Message: Unable to connect to NDMP host verify hostname

Explanation: A network connection to the NAS host failed.

■ Use the tpautoconf -verify command to verify the hostname, username,and password.

■ Use the ping command to verify network access.

Device configuration status code: 68Message: Unable to process NDMP message

Explanation: An unexpected error occurs while an NDMP message processed.

Recommended Action: Examine debug logs and system logs for a more detailedmessage on the error.

Media and device management status codes and messagesAbout media and device management status codes and messages

498

See “Using debug logs” on page 423.

Device configuration status code: 69Message: NDMP host not connected

Explanation: Unable to process NDMP messages with the NDMP host.

Recommended Action: Examine debug logs for more information on the error.

See “Using debug logs” on page 423.

Device configuration status code: 70Message: Unable to create NDMP session

Explanation: An error occurs while opening an NDMP connection to a NAS filer.

■ Examine debug logs for more information on the error.See “Using debug logs” on page 423.

■ Use the tpautoconf -verify command to verify the hostname, username,and password.

■ Use the ping command to verify network access.

Device configuration status code: 71Message: NDMP get_host_info failed

Explanation: The NAS host fails to correctly process the ndmp_get_host_infoprotocol request.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

Device configuration status code: 72Message: NDMP get_server_info failed

Explanation: The NAS host fails to successfully process the get_server_infoprotocol request.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

499Media and device management status codes and messagesAbout media and device management status codes and messages

Device configuration status code: 73Message: Unsupported NDMP version

Explanation: NetBackup supports tape devices on NDMP protocol versions V2,V3, and V4. For automatic device configuration, only V3 and V4 are supported.

■ Examine debug logs for a more detailed message on the error.See “Using debug logs” on page 423.

■ See your NAS vendor documentation for instructions on how to switch NDMPversions.

Device configuration status code: 74Message: NDMP authorization error, verify username/password

Explanation: NetBackup fails to authenticate the username or password on theNAS host.

Recommended Action: Use the tpautoconf -verify command to verify theusername and password.

Device configuration status code: 75Message: NDMP config_get_mover_type failed

Explanation: The NAS host fails to successfully process the config_get_mover_typeprotocol request.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

Device configuration status code: 76Message: NDMP config_get_connection_type failed

Explanation: The NAS host fails to successfully process theconfig_get_connection_type protocol request.

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

Device configuration status code: 77Message: Unable to connect to the EMM server

Media and device management status codes and messagesAbout media and device management status codes and messages

500

Explanation: A request was made to the EMM server, but it either did not reachthe EMM server or resulted from a communication failure.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that pbx_exchange and nbemm are running.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively running and that it accepts new connections.

Device configuration status code: 78Message: The EMM server failed to process the request

Explanation: A request was made to the EMM server, but it either did not reachthe EMM server or resulted from a communication failure.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that pbx_exchange and nbemm are running.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively running and that it accepts new connections.

Device configuration status code: 79Message: Unable to allocate memory for this process

Explanation: A memory allocation request failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that adequate memory is available.

Device configuration status code: 81Message: This is a drive path operation, use the -drpath option

Explanation: A path operation was specified with the tpconfig command withoutthe -drpath option. This error can occur when you try to change a drive’s pathusing tpconfig -update -drive.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.

501Media and device management status codes and messagesAbout media and device management status codes and messages

See “Using debug logs” on page 423.

■ Check tpconfig usage to ensure that the command is used properly and usetpconfig -update -drpath instead.

Device configuration status code: 82Message: Add Drive Name Rule request failed

Explanation: A request to add a drive name rule failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ The rule being added already exists.

■ The specified host does not exist in the EMM database. Use the nbemmcmd

-addhost command to add the host to the EMM database.

Device configuration status code: 83Message: Update Drive Name Rule request failed

Explanation: An update to a drive name rule failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ The rule being updated does not exist. Ensure that the drive name rule isentered correctly.

■ The specified host does not have a local drive name rule configured. Configurea drive name rule.

Device configuration status code: 84Message: Delete Drive Name Rule request failed

Explanation: A request to delete a drive name rule failed. You cannot add or deletea global drive name rule.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ A local drive name rule does not exist on the hosts specified.

Media and device management status codes and messagesAbout media and device management status codes and messages

502

Device configuration status code: 85Message: List Drive Name Rule request failed

Explanation: Could not list the drive name rules for a given host or set of hosts.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the hosts are known in the EMM database.

Device configuration status code: 86Message: Invalid Drive Name Rule

Explanation: A drive name rule was not specified, or contained an invalidcharacter.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Observe the rules for drive names:

■ Cannot begin with a dash.

■ Cannot exceed 48 characters.

■ A literal field can only contain alphanumeric characters and plus (+), dash(-), period (.), or underscore (_).

■ An invalid field name was specified; check command usage.

Device configuration status code: 87Message: System Error

Explanation: An operating system error occurred.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that adequate memory is available.

■ Verify that Windows networking is properly installed.

Device configuration status code: 88Message: Invalid host

503Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: An attempt was made to add a device to a host that the EMM databasedoes not recognize.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Use nbemmcmd -addhost to add the host to the EMM database.

Device configuration status code: 89Message: Drive name rule has exceeded its maximum length of 48 characters

Explanation: The specified drive name rule is too long.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Choose a shorter rule.

Device configuration status code: 90Message: Another device configuration is already in progress

Explanation: An instance of the Device Configuration Wizard or tpautoconf isalready running.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Retry the operation after the current instance is done.

■ A lock on the device configuration cache may have been orphaned. Use thenbemmcmd command to clear the lock, then retry the operation.

Device configuration status code: 91Message: The drive serial number already exists in the device database.

Explanation: An attempt was made to add a drive with a duplicate serial number.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the added drive has a unique serial number.

Media and device management status codes and messagesAbout media and device management status codes and messages

504

Device configuration status code: 92Message: VxSS access denied

Explanation: A user attempts an operation without adequate permissions

■ Verify that the user has the correct permissions to perform this operation.

■ Verify that the VxSS settings are correct, under Host Properties in theNetBackup Administration Console.See theNetBackup Administrator’s Guide Volume I for information on how touse the Veritas Security Subsystem (VxSS)

Device configuration status code: 93Message: Database Server is down

Explanation: A request was made to the EMM Server, but the underlying databaseserver does not respond.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ This error can occur if a cold catalog backup is in progress. Retry the requestafter this operation has completed.

Device configuration status code: 94Message: NetApp Disk Storage Unit feature is not licensed

Explanation: The NetApp NearStore disk storage unit is a licensed feature. Youmust install the NearStore license key before NetBackup can configure NearStoredevices.

Recommended Action: Install the appropriate license key.

Device configuration status code: 95Message: The requested operation is not valid for the specified Disk Type

Explanation: The storage device you configured is not a disk storage device.

Recommended Action: Select an appropriate storage device.

Device configuration status code: 96Message: The specified Disk Array Host is not configured in NetBackup

505Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: You must first add this disk array host to the NetBackup hostconfiguration before this operation can be performed. To view hosts, see nbemmcmd-listhosts in the NetBackup Commands Guide.

■ If you try to update an existing host’s credentials, this host no longer existsin NetBackup. It must be added again by using the tpconfig or the nbemmcmd

command.

■ The name you entered for the disk array host does not match any of themachine aliases in the NetBackup machine configuration. Use the nbemmcmd

command to add the fully qualified array host name (or the name entered) tothe machine alias list for your disk array.

Device configuration status code: 97Message: No valid license key for Disk Array configuration

Explanation: Disk array snapshot support is a licensed featured. You must installthe Snapshot Client license key before NetBackup can configure disk arraycredentials.

Recommended Action: Install the Snapshot Client license key.

Device configuration status code: 98Message: Open Storage feature is not licensed

Explanation: Credentials for OpenStorage servers cannot be added without theNetBackup OpenStorage license key.

Recommended Action: Install the OpenStorage license key.

Device configuration status code: 99Message: Credentials already exist

Explanation: Credentials already exist for the host you are trying to add.

RecommendedAction: Delete the existing credentials and then add the new ones.

Device configuration status code: 100Message: NetBackup Snapshot client not licensed

Explanation: Credentials for this type of host cannot be added without theNetBackup Snapshot Client license key. Host types that require this license aredisk array manager servers and virtual machine servers.

Recommended Action: Install the NetBackup Snapshot Client license key.

Media and device management status codes and messagesAbout media and device management status codes and messages

506

Device configuration status code: 101Message: authorization error, verify username/password

Explanation: Authorization failed with the given set of username and passwordvalues.

Recommended Action: Verify the values provided and check for typographicalerrors.

Device management status codesThese status codes appear in exit status and command output for the ltid,tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programsthat call those commands, such as media and device management user interfacesand the vmoprcmd command also presented these codes.

Device management status code: 1Message: Invalid Drive Type/Density

Explanation: An invalid density was specified for the -d parameter on tpreq.

Recommended Action: Check the tpreq man page (command description) forthe list of valid densities. Submit the mount request again with a valid density.

Device management status code: 2Message: Drive is currently assigned

Explanation: A request was made for a specified drive, but the drive was assigned.

Recommended Action: Display drive status (by using vmoprcmd -d or othermeans) to see the list of drives and their assignment status. Run the request lateror first clear the drive assignment: stop application activity on the drive, unmountthe media with tpunmount, or reset the drive. If the wrong drive was specified,submit the request again. Specify the correct drive name or index as appropriatefor the interface being used.

Device management status code: 3Message: Error in Sending Operator Message

Explanation: An attempt was made to send an operational message to ltid onan already existing internal message queue used for inter-process communication.(ltid is the Media Manager device daemon on UNIX and Linux and the NetBackupDevice Manager service on Windows.) An error was encountered in the message

507Media and device management status codes and messagesAbout media and device management status codes and messages

communications. The error probably indicates a lack of system resources formessage queues.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use.

Device management status code: 4Message: Error in Receiving Operator Message

Explanation: An attempt was made to receive a message from ltid on an alreadyexisting internal message queue used for inter-process communication. (ltid isthe Media Manager device daemon on UNIX and Linux and the NetBackup DeviceManager service on Windows.) An error was encountered in the messagecommunications. The error probably indicates a lack of system resources formessage queues.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use. Investigate whether ltid is tied up incommunications with devices or other components.

Device management status code: 5Message: Error in Sending Daemon Message

Explanation: ltidmade an attempt to send an internal process communicationsmessage to a robotic daemon or process by using an already existing internalmessage queue. (ltid is the Media Manager device daemon on UNIX and Linuxand the NetBackup Device Manager service on Windows.) An error was encounteredin the message communications. The error probably indicates a lack of systemresources for message queues.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use. Investigate whether the robotic daemon

Media and device management status codes and messagesAbout media and device management status codes and messages

508

or process on the local device host is tied up in communications with devicesor other components.

Device management status code: 6Message: Error in Receiving Daemon Message

Explanation: ltid attempted to receive or process an internal processcommunications message to a robotic process by using an existing internal messagequeue. (ltid is the Media Manager device daemon on UNIX and Linux and theNetBackup Device Manager service on Windows.) An error was encountered inthe message communications. The error probably indicates a lack of systemresources for message queues, or mismatched software components.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use. Check the installed software componentsand verify that they are all at a compatible release version.

Device management status code: 7Message: Error in Sending User Message

Explanation: ltidmade an attempt to send a user message to ltid on an alreadyexisting internal message queue used for inter-process communication. (ltid isthe Media Manager device daemon on UNIX and Linux and the NetBackup DeviceManager service on Windows.) An error was encountered in the messagecommunications. The error probably indicates a lack of system resources formessage queues.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use.

Device management status code: 8Message: Error in Receiving User Message

Explanation: An attempt was made to receive a user message from ltid on analready existing internal message queue used for inter-process communication.(ltid is the Media Manager device daemon on UNIX and Linux and the NetBackup

509Media and device management status codes and messagesAbout media and device management status codes and messages

Device Manager service on Windows.) An error was encountered in the messagecommunications. The error probably indicates a lack of system resources formessage queues. On Windows, this error can also occur if aninternal-system-registered event cannot be opened.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use.

Device management status code: 10Message: IPC sequence error

Explanation: An internal process communications message sequencing error hasoccurred.

Recommended Action:

Examine command output, debug logs, and system logs for a more detailed messageon the error.

See “Using debug logs” on page 423.

Device management status code: 12Message: Invalid Operator

Explanation: An internal list of operators could not be obtained.

Recommended Action: This error is an unexpected internal error. Stop andrestart ltid (the Media Manager device daemon on UNIX and Linux or theNetBackup Device Manager service on Windows).

Device management status code: 13Message: Error in IPC SHMGET call

Explanation: A process was unable to get a shared memory identifier associatedwith a segment of shared memory that ltidmaintains. (ltid is the Media Managerdevice daemon on UNIX and Linux or the NetBackup Device Manager service onWindows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

510

■ On UNIX and Linux servers, gather output from the ipcs -a command to seewhat resources are currently in use.

Device management status code: 14Message: Error in IPC SHMAT call

Explanation: A process was unable to attach a shared memory segment that ltidmaintains. (ltid is the Media Manager device daemon on UNIX and Linux or theNetBackup Device Manager service on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use.

Device management status code: 15Message: The drive is DOWN

Explanation: An attempt was made to mount media on a drive or to reserve ashared drive that was logically configured to the DOWN state.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check the application log files (such as the bptm log) to see why the drive mayhave been configured DOWN.

■ Check the integrity of the drive, drive path, and media.

Device management status code: 16Message: No mount pending for given mount index

Explanation: An attempt was made to retrieve information about a pending mountrequest, but no such pending mount request was found.

RecommendedAction: Use a device monitor interface or consult application logsto see whether the request was completed or canceled. Requests to retrieveinformation for pending mount requests are valid only when the mount requestis ongoing.

Device management status code: 17Message: Drive does not support pending request density

511Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: A drive was selected that has a drive type which is not compatiblewith the requested density.

■ Allow the drive selection to be determined automatically.

■ When you select the drive manually, check the device configuration and thevalid density table (available in the tpreqman page or command description).Then specify a drive that is compatible with the requested density.

Device management status code: 19Message: Only the administrative user can perform the requested operation

Explanation: Either an attempt was made to stop ltid (the Media Manager devicedaemon on UNIX and Linux or the NetBackup Device Manager service on Windows).Or the tpclean command was called, but the user was not root (UNIX and Linux)or the administrator (Windows).

RecommendedAction: If appropriate, give the user or the process administratorprivileges on Windows or root privileges on UNIX and Linux and retry theoperation.

Device management status code: 20Message: Cannot stop device daemon with tapes assigned

Explanation: An attempt was made to stop ltid, but media is currently mountedand assigned. (ltid is the Media Manager device daemon on UNIX and Linux orthe NetBackup Device Manager service on Windows.)

Recommended Action: Halt all jobs referencing media, unmount all media, andstop all applications from using Media Manager before trying to stop ltid. Ifunable to unmount media through the application interface, check for the existenceand permissions of the .ltisymlinks file in the /usr/openv/volmgr/misc

directory or in the install_path\Volmgr\misc folder. Initiate tpunmount

filename for each line in the .ltisymlinks file, where filename specifies thecontents of a line in that file. For example, on UNIX and Linux, the command maylook like the following:

tpunmount /usr/openv/netbackup/db/media/tpreq/A00001

Device management status code: 21Message: The drive is not ready or inoperable

Explanation: A drive was selected for a mount request, but the drive is not readywith loaded media.

Media and device management status codes and messagesAbout media and device management status codes and messages

512

Recommended Action: Wait until the drive is ready before you manually assigna drive to a pending mount request.

Device management status code: 22Message: IPC Error: Daemon may not be running

Explanation: A request to ltid cannot be serviced. (ltid is the Media Managerdevice daemon on UNIX and Linux or the NetBackup Device Manager service onWindows.) ltid is probably not running. If ltid is still running, its process lockfile may have been removed. Also, message queues may not function correctly onthe system.

■ If ltid is not running, start ltid and try the operation again. On UNIX andLinux, run /usr/openv/volmgr/bin/ltid, and on Windows, start theNetBackup Device Manager service.

■ If ltid is already running, check for the existence and permissions of the lockfile itself and the lock file directory, which are as follows:/usr/openv/volmgr/misc/.ltipid (UNIX and Linux) or install_path\Volmgr\misc\.ltipid (Windows). Terminate the ltidprocess if it is running.Create the lock directory or folder and adjust the permissions as needed sothat ltid can obtain the lock.

■ On UNIX and Linux, check the msgget man page and look for suggestions onhow to troubleshoot the system message queues.

Device management status code: 23Message: Invalid Drive Number

Explanation: A request was made for drive, but no such drive can be found in theactive configuration.

RecommendedAction: Ensure that ltidwas stopped and restarted after changeswere last made to the device configuration. (ltid is the Media Manager devicedaemon on UNIX and Linux or the NetBackup Device Manager service on Windows.)Display the device configuration (by using tpconfig -d or other means) to viewthe list of valid drives. Specify the drive name or index as appropriate for theinterface being used.

Device management status code: 24Message: Requested drive could not be reserved

513Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: An attempt was made to reserve a shared drive, but the drivereservation request failed. This status code is related to the internalimplementation of the SSO feature. It is not related to SCSI Reserve or Release.

RecommendedAction: This condition is expected for any shared drives that areretried automatically. If problems persist, verify the following: the EMM serverservices requests and it does not list drives as reserved to hosts that currently donot use the drives.

Device management status code: 25Message: File name does not exist

Explanation: A logical tape file or help file cannot be found. The tpunmount

command was probably issued with a logical tape file specified that does not existfor this user.

RecommendedAction: Check for existence of the logical tape file at the file pathspecified. The specified file path must match the exact case-sensitive path thatwas used when the tape mount was requested. Submit the request again with thecorrect file path. If the condition occurs during operator display of a pendingrequest error message, check to see if the help files are properly installed at thefollowing:/usr/openv/volmgr/help/robots/robot_type/help_file name (UNIXand Linux) or atinstall_path\Volmgr\Help\Robots\robot_type\help_file_name(Windows).

Device management status code: 26Message: Request terminated because host not validated for volume pool

Explanation: The host where the mount request was initiated is denied access tothe media. It is denied due to defined permissions for the volume pool in whichthe media ID is contained.

■ Query the volume pool information for the requested volume pool on the hostwhere the mount request was issued by running vmpool -listall -b. Checkthe system log to obtain the name of the host where the mount requestoriginated. This host name is the one returned by the system hostname(1)

command.

■ Change the volume pool host name security with vmpool or another userinterface that supports volume pool host attributes. Or change the volumepool that is associated with the volume (if it is not assigned). Or log in to thehost that is allowed to use media in the targeted volume pool. Then, submitthe mount request again.

Media and device management status codes and messagesAbout media and device management status codes and messages

514

Device management status code: 27Message: Request terminated because media ID is expired

Explanation: A mount request was canceled because the media was requestedwith write access, and the media has expired.

Recommended Action: Request read-only access to the media on the mountrequest if a read-only operation is needed. Replace the media or change theexpiration date to a future date that is based on site policy. Use the mediamanagement interface to view and change the expiration date for the media.Check and correct the system date and time, as needed.

Device management status code: 28Message: Error in MsgGet

Explanation: ltid made an attempt to obtain a message queue identifier thatwas used for internal message communications. (ltid is the Media Manager devicedaemon on UNIX and Linux or the NetBackup Device Manager service on Windows.)The request failed due to a system error. The error probably indicates a lack ofsystem resources for message queues, or mismatched software components.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use. Check the installed software componentsand verify that they are all at a compatible release version.

Device management status code: 30Message: Request terminated because media id will exceed maximum mountcount

Explanation: A mount request has been canceled because the media beingrequested has reached the maximum mount count associated with the media.

RecommendedAction: Replace the media or change the maximum mount countto a higher value that is based on site policy. A media management interface canbe used to view and change the maximum mounts allowed for the media. Checkthat the number of mounts for the media is set to a reasonable value given themedia’s usage history. Correct it as needed by using vmchange.

Device management status code: 32Message: Error in getting semaphore

515Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: ltid made an attempt to obtain a semaphore that was used forarbitrating access to shared memory. (ltid is the Media Manager device daemonon UNIX and Linux or the NetBackup Device Manager service on Windows) Therequest failed due to a system error. The error probably indicates a lack of systemresources for semaphores, or mismatched software components.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use. Check the installed software componentsand verify that they are all at a compatible release version.

Device management status code: 33Message: Error in SEMAPHORE operation

Explanation: A process was unable to perform a semaphore operation (such aslock or unlock) associated with resources maintained by ltid. (ltid is the MediaManager device daemon on UNIX and Linux or the NetBackup Device Managerservice on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use.

Device management status code: 35Message: Request terminated because media is unavailable (in DOWN drive,misplaced, write protected or unmountable)

Explanation: A mount request was canceled because the media being requestedis not available. It may be in a DOWN drive or misplaced, write protected, orunmountable. Another possible cause of this message is that you are using acleaning tape with no cleanings remaining.

Recommended Action: Use robotic inventory or manual means to compare thecontents of media in the robotic library with the volume configuration. Thenupdate the configuration as needed. Determine the physical location of the media.Check integrity of the drive, drive path, and media if the media is found in alogically DOWN drive. Verify that the media is not a misconfigured cleaning tape.Move the media into the robotic library and update the volume configuration ifthe media was not present in the library. Set the cartridge tab to allow write access,

Media and device management status codes and messagesAbout media and device management status codes and messages

516

or request the media with read-only access if the write protection was the causeof the error.

If the problem is a cleaning tape with no cleanings remaining, replace the cleaningtape.

Device management status code: 36Message: Request terminated by tpunmount call from another process

Explanation: A request was made to change the limit for the following: the numberof times that a volume can be mounted with write access for one or more volumesin the volume configuration. The value specified was not within the acceptablerange. The maximum number of mounts value may also be invalid in the numberof mounts and cleanings field of a bar code rule.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Specify a maximum-mounts value within the range of 0 to 2,147,483,647.

Device management status code: 37Message: Drive being assigned is either not NDMP or on the wrong NDMP client

Explanation: A mount request was canceled because the request was targeted toa drive configured as attached to an NDMP client. The request was manuallyassigned to a drive other than the requested drive. The assigned drive is eithernot NDMP or it is an NDMP drive configured to a different client.

Recommended Action: Display the device configuration to determine whichdrives are configured as being attached to specific NDMP clients. Ensure that ltidwas stopped and restarted after the last configuration changes were made. Reissuethe request and assign it to a drive that is attached to the requested NDMP client.

Device management status code: 38Message: Character device name for drive is not a character device

Explanation: On a tape mount request, the configured tape drive’sno-rewind-on-close device file was neither a character-special device nor of aknown type such as NDMP. (NDMP does not need to be a character special file.)

■ To avoid configuring invalid device paths and device names, use the DeviceConfiguration wizard (on supported device discovery platforms). The wizardautomatically configures paths and device names for tape drives.

517Media and device management status codes and messagesAbout media and device management status codes and messages

■ Always use no-rewind tape device files or recognized drive name syntax (suchas for NDMP) for tape drives. Make sure that the specified device paths existas character-special files. Check for detailed errors from the command or theuser interface output.See the NetBackup Device Configuration Guide.

Device management status code: 39Message: Parameter is invalid

Explanation: The tpclean command was called with invalid arguments, or aninternal function encountered a missing reference to data it requires.

■ If a cleaning operation was requested, check the tpclean usage statement andcompare with the parameters that were specified.

■ Check the installed software components and verify that they are all at acompatible release version.

Device management status code: 40Message: File name already exists

Explanation: On a tape mount request, the file name that is associated with therequest already exists or is already associated with another mount request.

Recommended Action: Submit the request again with a different file name.Specify a file name that does not correspond to an existing file. Or specify a filename that is not in use for another mount request that may be in progress.

Device management status code: 41Message: Unknown drive name

Explanation: A request was made for a specified drive, but no such drive can befound in the active configuration. This status can occur in the following situations:if the device files are corrupt or missing, if they cannot be opened or read, or ifthere are no devices configured.

■ Ensure that ltid was stopped and restarted after changes were last made tothe device configuration. (ltid is the Media Manager device daemon on UNIXand Linux or the NetBackup Device Manager service on Windows.) Display thedevice configuration (use tpconfig -d or other means) to see the list of validdrives. Specify the drive name or index as appropriate for the interface beingused.

■ Check integrity of the EMM database. Display the device configuration to dothe following:

Media and device management status codes and messagesAbout media and device management status codes and messages

518

■ Determine if the database is corrupt.

■ Restore a saved copy of the database file from catalog backups, or removethe devices and recreate the device configuration.

Device management status code: 42Message: Incorrect tpreq access mode

Explanation: On a tape mount request, the specified access mode was invalid. OnWindows hosts, a user without Administrator privileges made a request forNetBackup Device Manager services.

Recommended Action: When you use tpreq, specify an access mode argumentof r for read, w for write, or use the default (read) access mode. When you makeany requests that require NetBackup Device Manager services on Windows, doso under an account with Administrator privileges.

Device management status code: 44Message: You do not have permission to create the file

Explanation: On a tape mount request, the file name that is associated with therequest cannot be created due to directory permissions or folder permissions.

Recommended Action: Check for existence of a file at the file path specified. Ifa file is found, delete the file if it is not needed or submit the request again anduse a different file path. If no file exists at that location, check the directorypermissions or the folder permissions for the following: read and write access forthe user or the application process that issued the mount request.

Device management status code: 46Message: Tape needs to be write enabled

Explanation: On a tape mount request, the specified access mode was for writeaccess, but the physical media was write-protected.

RecommendedAction: Change the physical media write-protect setting to allowwrite access (unlocked), or submit the request again with read-only access. Torequest read-only access using tpreq, specify an access mode argument of r forread or use the default (read) access mode.

Device management status code: 47Message: Unable to establish scan host for shared drive

519Media and device management status codes and messagesAbout media and device management status codes and messages

Explanation: On a request to change a shared drive’s status, an attempt toestablish a connection to the drive’s scan host failed.

■ Determine which host serve as the drive’s scan host: use vmoprcmd output orby checking the Device Monitor in the Administration Console.

■ Ensure that vmd (the NetBackup Volume Manager daemon on UNIX and Linuxor NetBackup Volume Manager service on Windows) is running on the scanhost. On the scan host, examine debug logs and system logs for any messagesthat are related to the error.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ The detailed reason for the canceled request should be available in the daemondebug logs on the scan host. Correct the problem and submit the request againif needed.

Device management status code: 48Message: Host is not the scan host for this shared drive

Explanation: On a request to assign, reserve, or scan a drive, the targeted devicehost determined that it was not the scan host for the drive. The request was refused(the caller retries it).

■ If problems are encountered as a result of the reported error, check forcommunication, configuration, and system problems among the associatedhosts. To check, use vmoprcmd output or check the Device Monitor in theAdministration Console.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Configure scan ability priorities for assigning scan hosts by changing the MediaManager configuration. Configure so that less network connections need tobe maintained, and greater system load is placed on hosts with more capabilityto service the load.

Device management status code: 49Message: Tape file path exceeds 255 character maximum

Explanation: On a tape mount request, the file name that is associated with therequest exceeds 255 characters.

Media and device management status codes and messagesAbout media and device management status codes and messages

520

RecommendedAction: When you request a tape mount, ensure that the file namedoes not exceed 255 ASCII characters in length. If the mount requests come froman application, request an application change to use a shorter file name. Or installthe product in a directory or a folder that does not cause the file name limit to beexceeded.

Device management status code: 50Message: No action pending for given mount index

Explanation: On a request to obtain the pending action for a mount request, noknown pending action was associated with the request.

Recommended Action: Use a device monitor interface to display any requeststhat have pending actions. Perform requests (like assign, deny, display, or resubmit)only on the requests that have pending actions.

Device management status code: 52Message: No robot is defined of this type

Explanation: On internal communications between a robotic daemon or processand ltid, no robots of the expected type were found actively configured. (ltid isthe Media Manager device daemon on UNIX and Linux or the NetBackup DeviceManager service on Windows.)

RecommendedAction: Display the running robotic processes to see if processesfrom a previous configuration are still running. If any are found, terminate them.Check the installed software components and verify that they are all at acompatible release version.

Device management status code: 53Message: Request has been queued (Cancel to clear message)

Explanation: A mount request or drive-related operation was queued becausedrive resources were in use.

RecommendedAction: Wait until the drive resources become available, or cancelpending mount requests as needed.

Device management status code: 55Message: Operator denied mount request

Explanation: The operator denied a mount request.

Recommended Action: This error occurs when an administrator or operatorcancels a user or application mount request. The request may have been canceled

521Media and device management status codes and messagesAbout media and device management status codes and messages

for a number of reasons: missing or faulty media or the need to allow other, higherpriority requests to obtain drive resources. Check with the administrator oroperator for more information.

Device management status code: 56Message: Mount canceled, device daemon is terminating

Explanation: Pending mount requests were canceled because the administratorterminated ltid (the Media Manager device daemon on UNIX and Linux or theNetBackup Device Manager service on Windows).

RecommendedAction: Wait for ltid to be restarted before you submit the requestagain. Check with the administrator as needed to determine daemon or serviceavailability.

Device management status code: 58Message: The device is not robotic, cannot perform cleaning

Explanation: An attempt was made to automatically clean a drive, but the driveis not in a robotic library.

Recommended Action: Clean stand-alone drives by inserting a cleaning tapewhen needed. For non-shared drives, update the cleaning statistics with tpclean

or another user interface that supports cleaning-related operations.

Device management status code: 59Message: No cleaning tape is defined in the device’s robot or 0 cleanings remain.

Explanation: An attempt was made to automatically clean a drive, but no usablecleaning media is available. Or the number of cleanings that remains for thecleaning tape is zero.

■ Ensure that cleaning media was added to the robotic library for each drivetype capable of being cleaned with a separate cleaning cartridge.

■ Ensure that a positive number of cleanings is available for the cleaning mediain the EMM database for the robotic library. Replace the cleaning tape orincrease the number of cleanings for the cleaning media before the countreaches zero.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

522

Device management status code: 60Message: Robot daemon and/or robotic hardware is not available

Explanation: A robot was not configured or was operationally unavailable.Specifically, an attempt may have been made to automatically clean a roboticdrive, but the robot is not defined or is unavailable. Alternatively, on an attemptto initialize the shared drive lists, a drive was found to be configured as robotic,without the required robot configured.

Recommended Action: Display the device configuration and ensure that thedrive and robotic configuration information are consistent. Check the operationalstatus of the robot and robotic software by checking the system log files. If moredetail on robot operational status is needed, increase the level of verbosity byadding the VERBOSE option in the vm.conf file. Then restart ltid (the devicedaemon /NetBackup Device Manager service).

Device management status code: 61Message: No media found in device or robot slot, please verify

Explanation: On a request to mount media, no media was found in the targetedlocation before a designated time period had elapsed.

RecommendedAction: Resubmit the request, and mount the media in the targeteddrive before the designated time period has elapsed. Check the device configurationto ensure the following: that the correct drive name has been configured and thatltid, the device daemon, was restarted after the last device configuration changewas made.

Device management status code: 62Message: Drive not available in library for mount request

Explanation: A mount request has been canceled because no drive is available.All compatible drives may be DOWN, or oversubscribed due to other active mountrequests.

Recommended Action: Investigate device availability and scheduling/driveutilization of applications requesting drive resources. Under some conditions,mount requests are canceled so that they can be reissued at a later time whencompatible drive resources are available.

Device management status code: 63Message: Request terminated because mount requests are disabled

Explanation: A mount request was canceled because it cannot be satisfied.

523Media and device management status codes and messagesAbout media and device management status codes and messages

Recommended Action:

Examine command output, debug logs, and system logs for a more detailed messageon the error.

See “Using debug logs” on page 423.

The detailed reason for the canceled request should be available in the systemlog, command output, or from a device monitor interface. Correct the problemand resubmit the request if needed.

Device management status code: 64Message: Cannot assign a robotically controlled device

Explanation: An attempt was made to manually assign a specific device to satisfya mount request, and the chosen device was configured in a robotic library.

RecommendedAction: Assign the request to a standalone drive, or allow requestsfor mounts in robotic drives to be automatically assigned.

Device management status code: 65Message: Invalid volume pool specified

Explanation: On a mount request, the media pool specified was not valid.

Recommended Action: Resubmit the request, specifying a volume pool namethat is no more than 20 ASCII characters in length.

Device management status code: 66Message: Request terminated because of volume pool mismatch

Explanation: The volume pool that is specified on the tpreq command did notmatch the volume pool in the Media Manager configuration for the media ID.

RecommendedAction: Use a media management interface to obtain the volumepool name of the media that is to be mounted. Then resubmit the mount request,specifying the correct pool name.

Device management status code: 69Message: Request terminated because media is unmountable

Explanation: A mount request has been canceled because the media beingrequested is not mountable. The same media has been found to be unmountablein at least two different drives.

■ Check integrity of the drive, drive path, and media.

Media and device management status codes and messagesAbout media and device management status codes and messages

524

■ Verify that the media is not a misconfigured cleaning tape.

Device management status code: 70Message: Request terminated because media is write protected

Explanation: A mount request has been canceled because the media beingrequested for write access is not write-enabled.

Recommended Action: Check the physical media cartridge to see whetherwrite-protection has been enabled. If write access to the media is desired, disablewrite protection for the media.

If read-only access is desired, leave the write-protection enabled. Then make thenecessary administrative requests in the requesting application (such assuspending the media) to ensure that the media is requested only for read access.

If the media was requested through the command line interface, see the tpreq

man page or command description for specifying the media access mode. Thetpreq command is described in the following manuals:

See the NetBackup Administrator’s Guide, Volume II.

See the NetBackup Commands manual.

Device management status code: 71Message: Request terminated because media is a cleaning tape

Explanation: A mount request has been canceled because the media that wasfound in the drive is a cleaning tape.

Recommended Action: Check to make sure the Media Manager’s EMM databaseis up-to-date. If there are cleaning media in the library, assign appropriate cleaningmedia types to them in the Media Manager EMM database.

Device management status code: 72Message: EMM library call failed

Explanation: A request that was made to read/write data to EMM failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that pbx_exchange is running.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively running and accepting new connections.

525Media and device management status codes and messagesAbout media and device management status codes and messages

Device management status code: 73Message: Stopping device daemon with tapes assigned

Explanation: An operator requested that ltid shutdown but tapes are still in use.

RecommendedAction: None. This message is advisory and no action is required.

Device management status code: 74Message: Robot operation failed

Explanation: A tape mount via bptm resulted in a failed robotic operation.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the robotic hardware is functional.

Device management status code: 75Message: LTI system error

Explanation: A system error occurred.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ A tpclean operation was attempted and Windows networking was not properlyconfigured.

■ A malloc system call failed when trying to stop ltid.

Device management status code: 76Message: Robot/LTI protocol error

Explanation: Communication between ltid and the robotic daemons caused aprotocol error.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that ltid, bptm, and the robotic daemons are at a compatible NetBackuplevel.

Media and device management status codes and messagesAbout media and device management status codes and messages

526

Device management status code: 77Message: VxSS access denied

Explanation: A user tried to run tpclean without adequate permissions.

■ Verify that the user is logged in with permissions adequate for this operation.

■ Verify that the VxSS settings are correct, under Host Properties in theNetBackup Administration Console.See the NetBackup Security and Encryption Guide.

Device management status code: 78Message: Unable to connect to the EMM server

Explanation: An attempt to retrieve or update information in EMM failed.

■ Verify that the correct EMM server name is listed in the NetBackupconfiguration.

■ Verify that the media server that is encountering this error is listed in theNetBackup configuration on the EMM server.

■ Verify that EMM is running on the EMM server.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Device management status code: 79Message: Can not retrieve Job ID from Job Manager

Explanation: The tpreq, tpclean, or tpunmount command encountered an errorwhile trying to get a job ID from the NetBackup Job Manager.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the NetBackup Job Manager is running on the master server.

Device management status code: 80Message: Job Manager returned error: see activity monitor

Explanation: The tpunmount command encountered an error whilecommunicating with the NetBackup Job Manager. The details of this issue maybe found in the Activity Monitor entry for this job.

527Media and device management status codes and messagesAbout media and device management status codes and messages

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that the NetBackup Job Manager is running on the master server.

■ Verify that the arguments provided to the tpunmount command are correct.

Device management status code: 81Message: Retry later

Explanation: An attempt was made to use resources controlled by EMM. Theseresources were not available.

Recommended Action: Retry the command at a later time.

Device management status code: 82Message: No drive available

Explanation: An attempt to use a drive was made but that drive was not available.

■ Verify that the drive is not DOWN on the intended media server.

■ Verify that the media server where the drive is found is ACTIVE.

■ Retry the command with a different drive.

Device management status code: 83Message: Media does not exist in database

Explanation: The requested media ID was not found in the EMM database.

■ Verify that the requested media ID was entered correctly.

■ Retry with a different media ID.

Device management status code: 84Message: No Error on operation, sideband data only

Explanation: This is only an informational message.

Recommended Action: No action is required by the user.

Media and device management status codes and messagesAbout media and device management status codes and messages

528

Robotic status codesRobotic daemons or processes issue these status codes. They are also issued byprograms that call the robotic operations, such as the vmchange command andthe media and device management user interfaces.

Robotic status code: 200Message: STATUS_SUCCESS

Explanation: A robotic operation was successfully completed.

Recommended Action: None.

Robotic status code: 201Message: Unable to open robotic path

The robotic library device could not be opened. The specific case could be one ofthe following:

■ The robot device, path, or library name in the device configuration may notbe valid.

■ The configured robotic device may not exist.

■ The robotic device may be incorrect, such as a UNIX and Linux device file thatis not of a character special file format.

■ The robotic daemon/process lock file could not be opened or a lock obtained.

■ The open operation on the device or through the API interface (such as NDMP)failed.

1 Stop any robot test utilities that may be running, since they have the lock onthe robotic device when they are active.

2 Check the configuration of the robot against the recommended configurationas indicated in the documentation for robot configuration.

3 Check the health of the robotic device by using a robot test utility, then closethe test utility when finished.

4 Check for the existence and permissions of the lock file itself and the lockfile directory, which is /usr/openv/volmgr/misc/vmd.lock (UNIX and Linux)or install_path\Volmgr\misc\vmd.lock (Windows). Create thedirectory/folder and adjust the permissions as needed so that the roboticdaemon/process can use the lock file. Stop and restartltid (the device daemonon UNIX and Linux or the NetBackup Device Manager service on Windows).

529Media and device management status codes and messagesAbout media and device management status codes and messages

Robotic status code: 202Message: Unable to sense robotic device

An element of the robotic library device could not be sensed. The cause could beany of the following:

■ The SCSI commands mode sense, mode select, or read element status (of slot,drive, transport, i/e element) may have failed.

■ A network API-controlled library inventory request may have failed.

■ The robotic daemon/process could not initialize a robotic database file.

■ Check the configuration of the robot against the recommended configurationas indicated in the documentation for robot configuration.

■ Check the health of the robotic device by using a robot test utility, then closethe test utility when finished.

■ Check for the existence and permissions of the temporary robotic databaseand the temporary database directory/folder, which is/usr/openv/volmgr/misc/robotic_db (UNIX and Linux) orinstall_path\Volmgr\misc\robotic_db (Windows). Create thedirectory/folder and adjust the permissions as needed so that the roboticdaemon/process can create it or use it. Stop and restartltid (the device daemonon UNIX and Linux or the NetBackup Device Manager service on Windows).

Robotic status code: 203Message: Timeout waiting for robotic command

Explanation: A robotic operation timed out: it did not return with a status beforea designated time period elapsed.

■ Stop any robot test utilities, since they have the lock on the robotic devicewhen they are active, and can block other requests.

■ Check whether excessive hardware retries have delayed the completion of arobotic command.

■ Check to see whether the robotic device still functions. Use a robot test utilityto send commands to the device to see whether it is responsive. Execute vmpsto verify that no unexpected Media Manager processes are running. Someprocesses should remain running, but some processes that do not go away canindicate a more serious problem, such as a hung system call.

Robotic status code: 204Message: Unable to initialize robot

Media and device management status codes and messagesAbout media and device management status codes and messages

530

Explanation: The robot could not be initialized. This generic status is used formany conditions.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Investigate the system log messages that are related to the specific errorleading to the robot initialization failure.

Robotic status code: 205Message: Robotic mount failure

Explanation: The robot could not mount media.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Investigate the system log messages that are related to the specific errorleading to the media mount failure.

Robotic status code: 206Message: Robotic dismount failure

Explanation: The robot could not dismount media.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Investigate the system log messages that are related to the specific errorleading to the media dismount failure.

Robotic status code: 207Message: Invalid command code

Explanation: A robotic operation was requested with improper options, when itwas not supported, or a robotic operation encountered an incompatible deviceinterface. There may be an incompatibility between components or versions ofthe product.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

531Media and device management status codes and messagesAbout media and device management status codes and messages

■ Verify that all Media Manager binaries and user interfaces are at a compatibleversion level.

Robotic status code: 208Message: Requested slot is empty

Explanation: No media was found in a specified slot. The volume configurationmay not be consistent with the physical contents of the robotic library that isassociated with the volume.

RecommendedAction: Install or realign the container/holder for the media if itis misplaced or misaligned. Place media right-side-up in the slot if the media isupside-down. Check to see if the requested slot is reserved to the robotic libraryfor internal use. Physically correct issues within the robotic library, or use a mediamanagement interface to correct the volume configuration.

Robotic status code: 209Message: Unable to open drive

Explanation: The drive could not be opened. The drive configuration may beincorrect and the drive may be logically DOWN. Also, the drive may never havebecome ready after media was placed in the drive.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check for improperly configured cleaning media or interference with the drivecleaning operation. Check for bad media that may have led to the drive notbecoming ready after media was placed within it.

■ To avoid configuring incorrect device paths and device names, which is acommon cause of drive open problems, do the following: use the DeviceConfiguration wizard (on supported device discovery platforms) so that devicepaths and device names can be automatically configured. Investigate thesystem log messages that are related to the specific error leading to the openfailure.

Robotic status code: 210Message: Unable to SCSI unload drive

Explanation: The drive could not be unloaded. The drive configuration may beincorrect and the drive may be logically DOWN. Also, the drive may never havebecome ready after media was placed in the drive.

Media and device management status codes and messagesAbout media and device management status codes and messages

532

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check for improperly configured cleaning media or interference with the drivecleaning operation. Check for bad media that may prevent unloading the drive.To avoid configuring incorrect device paths and device names, which is acommon cause of drive unload problems, do the following: use the DeviceConfiguration wizard (on supported device discovery platforms) so that devicepaths and device names can be automatically configured. Investigate thesystem log messages that are related to the specific error leading to the unloadfailure.

Robotic status code: 211Message: Process killed by signal

Explanation: An unexpected signal or event canceled the robotic operation.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Check vendor or operating system administrative interfaces and logs to see ifrobotic commands are being canceled.

Robotic status code: 212Message: Process killed by parent

Explanation: A robotic operation was canceled because of one of the following:it did not return a status before a designated time period elapsed, orcommunications or hardware errors led to the need to reinitialize the device.

■ Stop any robot test utilities, since they have the lock on the robotic devicewhen they are active, and can block other requests.

■ Check to see whether the robotic device still functions.

■ Check whether excessive hardware or communication problems have delayedthe completion of a robotic command.

■ Use a robot test utility to send commands to the device to see whether it isresponsive. Executevmps to verify that no unexpected Media Manager processesare running. Some processes should remain running, but some processes thatdo not go away can indicate a problem, such as a hung system call.

533Media and device management status codes and messagesAbout media and device management status codes and messages

Robotic status code: 213Message: Drive does not exist in robot

Explanation: A targeted drive was not found in the robotic library. The driveconfiguration may be incorrect.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Obtain the list of drives using a method that involves a robotic library query,such as a query available from the robot test utility. Compare the list of drivesagainst the device configuration. Ensure that ltid was stopped and restartedafter changes were last made to the device configuration. ltid is the MediaManager device daemon on UNIX and Linux or the NetBackup Device Managerservice on Windows.

Robotic status code: 214Message: Robot number does not exist

Explanation: A targeted robotic library was not found in the active deviceconfiguration.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Ensure that ltid was stopped and restarted after changes were last made tothe device configuration. (ltid is the Media Manager device daemon on UNIXand Linux or the NetBackup Device Manager service on Windows.) Oncommands to robotic libraries, specify only robotic libraries that are activelypart of the device configuration.

Robotic status code: 215Message: Requested tape in other or non-configured drive

Explanation: The targeted media was found in a drive differing from the targeteddrive.

Requested media can be temporarily unavailable, which is normal. Also, mediacan remain unavailable until administrator or operator action is taken.

■ If the media is needed immediately, examine command output (if available),debug logs, and system logs for messages relating to the targeted media.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

534

■ Check for conflicts between multiple applications using media in the roboticlibrary. Check integrity of the drive and drive paths, so that media is notroutinely left in other drives.

Robotic status code: 216Message: Door is open on cabinet

Explanation: The robotic library door was open.

RecommendedAction: Close the door of the robotic library and reissue the roboticrequest. See if the door latch mechanism works by comparing what happens withrobot test utility commands when the door is open versus closed.

Robotic status code: 217Message: Requested slot already has cartridge

Explanation: The requested slot was already held or was associated with acartridge.

RecommendedAction: Ensure that the inject/eject request does not target a slotthat already contains media. Check for media in drives to ensure that the media’shome slot location is not targeted for use with media to be injected.

Robotic status code: 218Message: Cannot move from media access port to slot

Explanation: A robotic inject media operation returned a status indicating thatan inject failure occurred.

■ See whether the robotic library has a media access port (use the robot testutility to validate). Investigate whether the administrator or operator hascanceled the inject operation.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Robotic status code: 219Message: Cannot move from slot to media access port

Explanation: A robotic eject media operation returned a status indicating thatan eject failure occurred.

535Media and device management status codes and messagesAbout media and device management status codes and messages

■ See whether the robotic library has a media access port (use the robot testutility to validate). Investigate whether the administrator or operator hascanceled the eject operation.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Robotic status code: 220Message: Media access port does not contain media

Explanation: A robotic inject media operation returned a status indicating thatthe media access port does not contain any cartridges/media. The operator oradministrator may not have placed media into the media access port for inject.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Coordinate inject/eject operations between all operators and administrators.

Robotic status code: 221Message: Media access port already contains media

Explanation: A robotic eject media operation returned a status indicating thatthe media access port contains one or more cartridges. The operator oradministrator may not have removed media from the media access port as partof the latest (or a previous) eject operation.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Media Manager status codes” on page 424.

■ Coordinate inject/eject operations between all operators and administrators.Ensure that the media access port is empty of media before an eject operation.

Robotic status code: 222Message: Robotic arm has no addressable holder

Explanation: A holder is gone from an element of the robot and cannot be used.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Media and device management status codes and messagesAbout media and device management status codes and messages

536

■ Investigate the state of the physical hardware and correct the holder statusfor storage, drive, and transport elements as needed. Then, resubmit therequest.

Robotic status code: 223Message: Robot busy, cannot perform operation

Explanation: The robot is busy performing another operation, using resourcesthat are needed for the requested operation.

Recommended Action: Wait until the robot is done performing currentexternal-based requests (including robot inventory and inject/eject media) beforestarting new requests. Check vendor or operating system administrative interfacesand logs to see if robotic resources are busy.

Robotic status code: 224Message: Control daemon connect or protocol error

Explanation: A protocol error occurred between robotic and other components.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Investigate the system log messages that are related to the specific errorleading to the media mount failure. Verify that all Media Manager binaries areat a compatible version level.

■ Verify that robotic interfaces to vendor and operating system software havecompatible versions.

Robotic status code: 225Message: Robot hardware or communication error

Explanation: A hardware or communications error occurred between robotic andother components.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Investigate the system log messages that are related to the error leading tothe media mount failure.

537Media and device management status codes and messagesAbout media and device management status codes and messages

■ Verify that all Media Manager binaries are at a compatible version level. Verifythat robotic interfaces to vendor and operating system hardware and softwarehave compatible versions.

Robotic status code: 226Message: Requested slot contains the wrong tape

Explanation: The media in the requested slot is different from the media that isexpected in that slot. The volume configuration is not consistent with the physicalcontents of the robotic library that is associated with the slot associated with therequested volume.

Recommended Action: The volume configuration or media placement in therobotic library needs to be adjusted using one of the media management interfaces.Determine whether the barcode changed or the media changed since the last timethe EMM database was reconciled for the affected slot. If only the barcode haschanged but not the media, issue an update barcode request for each affectedvolume. If the media has been changed, use a media management interface to runrobot inventory update, which updates the EMM database with the media location.

Robotic status code: 228Message: Requested slot does not exist in robot

Explanation: The slot that is associated with a request is not valid for the robot.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Issue a robot inventory Contents report to determine the valid slot range forthe robot. Check the volume configuration to ensure that only valid slots arereferenced in volume records, paying particular attention to the starting andending slot numbers. Update the volume configuration as needed, or requestonly valid slot ranges for robotic operations.

Robotic status code: 229Message: Requested operation is not supported by the robot

Explanation: A robotic operation was sent to a robotic component that did notsupport that operation. Or the options that were requested for the operation werenot supported. There may be an incompatibility between components or versionsof the product.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.

Media and device management status codes and messagesAbout media and device management status codes and messages

538

See “Using debug logs” on page 423.

■ Verify that all Media Manager binaries and user interfaces are at a compatibleversion level.

Robotic status code: 230Message: System error occurred during robot operation

Explanation: A robotic operation encountered a system error. This status codeis used for generic system call failures within robotic daemons/processes.

■ Check for other error messages in the command or interface output to indicatewhich system call failed. Examine command output, debug logs, and systemlogs for a more detailed message on the error.See “Using debug logs” on page 423.

■ Check the system application log for error and warning messages.

■ Verify that the system is not running out of virtual memory. If virtual memoryis the problem, shut down unused applications or increase the amount ofvirtual memory. To increase virtual memory on Windows: display the ControlPanel, double-click System, and on the Performance tab, set Virtual Memoryto a higher value.

■ Verify that all product binaries are properly installed.

■ Verify that no unexpected Media Manager processes are running by executingvmps. Some processes should remain running, but some processes that do notgo away could indicate a problem, such as a hung system call.

Robotic status code: 232Message: Volume not found in library

Explanation: The requested media was not found in the robotic library. The mediahas been ejected or become inaccessible for some other reason.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Issue a robot inventory Contents report to obtain the list of media in the roboticlibrary. See whether inventory filters have been enabled in the Media Managerconfiguration file. Inventory filters affect the contents of the media listreturned from the robotic daemon or process. Use a robot test utility or anoperating system/vendor administrative interface to verify the status of media,as needed. Update the volume configuration and search for the media if it wasnot in the robotic library, as needed, and resubmit the request.

539Media and device management status codes and messagesAbout media and device management status codes and messages

Robotic status code: 233Message: Volume is in library, but not in drive domain

Explanation: The media was in the robotic library, in a library domain that isinaccessible to the drives that are configured in the robot.

RecommendedAction: Issue a robot inventory Contents report to obtain the listof media in the robotic library. Check the device configuration and ensure thatthe drive addresses correspond to the correct domain for the media. Correct thedevice configuration as needed and restart ltid (the device daemon on UNIX andLinux or NetBackup Device Manager service on Windows). Use a robot test utilityor a vendor administrative interface to verify the status of media, as needed.Update the volume configuration and physically move the media into the roboticlibrary, as needed, and resubmit the request.

Robotic status code: 234Message: Robot denied access to the resource

Explanation: The media was found in the robotic library, but is denied accessaccording to an established security policy.

RecommendedAction: Issue a robot inventory Contents report to obtain the listof media in the robotic library. Use a vendor administrative interface to verifythe status of media, as needed. Delete the media in the volume configuration, ormake the volume accessible through a vendor administrative interface, asappropriate. Update the volume configuration, as needed, and resubmit the request.

Robotic status code: 235Message: barcode label is unreadable

Explanation: The media was found in the robotic library, but it has an unreadablebarcode label.

Recommended Action: Use the robot test utility or a vendor administrativeinterface to verify the status of media. Correct the label or replace the media asappropriate. Update the volume configuration, as needed, and resubmit the request.

Robotic status code: 236Message: Robot has misplaced the media

Explanation: The requested media was known according to the vendor softwaremanaging the robotic library, but the media has been misplaced.

RecommendedAction: Use a robot test utility or a vendor administrative interfaceto verify the status of media. Search for the media inside the robotic library.

Media and device management status codes and messagesAbout media and device management status codes and messages

540

Update the volume configuration and search for the media if it was not in therobotic library, as needed, and resubmit the request.

Robotic status code: 237Message: Volume is in use

Explanation: The media was in use.

Recommended Action: Use the robot test utility or a vendor administrativeinterface to verify the status of media. Determine what applications may be usingthe media. Dismount the media if it is not being used. Wait for the media to becomeavailable, as needed.

Robotic status code: 238Message: Requested drive is in an offline domain

Explanation: The drive that is targeted for a mount request was in a roboticlibrary domain that is offline.

Recommended Action: Bring the robotic library domain (ACS Library StorageModule) back online. Or postpone use of drives in that domain until the domaincan be brought back online.

Robotic status code: 239Message: Requested volume is in an offline domain

Explanation: The volume that is targeted for a mount request was in a roboticlibrary domain that is in the offline or offline pending state.

Recommended Action: Bring the robotic library domain (ACS Library StorageModule) back online. Or postpone use of media in that domain until the domaincan be brought back online.

Robotic status code: 240Message: A memory allocation attempt failed in the robotic daemon

Explanation: An attempt by the robotic control daemon to allocate memory hasfailed. This error may indicate serious memory problems on your media server.

RecommendedAction: Stop all NetBackup Media Manager daemons. Consult thedocumentation for your operating system memory management tools to determinewhat remaining process is leaking memory, and stop that process. Restart theNetBackup Media Manager daemons. Free up memory by terminating unneededprocesses that consume a lot of memory. Add more swap space or physical memoryif necessary.

541Media and device management status codes and messagesAbout media and device management status codes and messages

Robotic status code: 242Message: Robot media access port does not exist

Explanation: the requested media access port was not valid for use with thetargeted media.

Recommended Action: Use the robot test utility or a vendor administrativeinterface to verify the media access port address based on the location of themedia. Choose a media access port that is valid, or let one be automatically selected,and retry the robotic operation.

Robotic status code: 243Message: Cannot open/create the media access port status file

Explanation: A robotic daemon/process could not create or open a status file inthe database directory/folder.

Recommended Action: Investigate why the robot status file in the directory/usr/openv/volmgr/database (UNIX and Linux) or folderinstall_path\Volmgr\database (Windows) cannot be created or opened. OnWindows, check which account the NetBackup Device Manager service (and thusthe robotic process) is running under. Compare it against the security propertiesof the database folder.

Robotic status code: 244Message: The eject command was aborted by the user

Explanation: An administrator or operator canceled an eject media request.

Recommended Action: This error happens when an administrator or operatorcancels an eject request. The request may have been canceled for a number ofreasons: missing or faulty media, to allow the media access port to be used forother requests, or to perform the operation at a later time. Check with theadministrator or operator for more information.

Robotic status code: 245Message: Physical drive is not available

Explanation: A robotic mount operation could not be completed because physicaldrive resources are not available for the request. This error may result from anenvironment that is based on virtualized resources, such as one involving theStoragenet 6000 Storage Domain Manager (SN6000).

The SN6000 virtualizes tape drives. Some SN6000 configurations may have morelogical drives than the number of physical drives (or equivalent resources) available

Media and device management status codes and messagesAbout media and device management status codes and messages

542

for drive requests. Also, the relationship between the number of logical drivesand physical drives may change as hardware failures occur. NetBackup scheduling,drive allocation, and drive assignment algorithms can only determine logical driveavailability. NetBackup attempts to fully utilize all configured and available logicaldrives. If the number of required logical drives exceeds the physical drivesavailable, a NetBackup job may be started with insufficient drive resources. Insteadof queueing the job in the scheduler, the job runs and encounters the resourceissue when it makes an ACS tape mount request.

■ Install the Shared Storage Option (SSO) license for mount requests to requeuewhen physical drive resources are not available.

■ The number of drives that can be in use at any one time is limited. Configurebackup windows so the different storage units that are tied to the same physicaldrives are active only at non-overlapping times. Increase the media mounttimeout to avoid job failures when the job cannot get a physical drive due tothe drives all being busy.

Robotic status code: 246Message: Failed to find an available slot to inject to

Explanation: An attempt to inject a volume into a full library failed. This errorshould only occur when the library is full. Full means that all storage elementseither contain media or have been assigned media that are currently mounted ina drive. Note that some libraries that support multiple media types restrict whichtype of media can be assigned to each storage element. In this case, this errormight occur even if some of the storage elements in a library were not full. Sincethe empty storage elements may not match the media type for the media to inject,the library is full for this media type.

Recommended Action: Clear the media access port, then re-inventory the robotby doing a volume configuration update.

Robotic status code: 249Message: Volume is in home slot

Explanation: Volume is currently in its home slot and ready for eject.

Recommended Action: None.

Robotic status code: 250Message: Media access port is available

Explanation: Media access port is available for inject or eject.

543Media and device management status codes and messagesAbout media and device management status codes and messages

Recommended Action: Begin inject or eject operation.

Robotic status code: 251Message: Media access port is unavailable

Explanation: Media access port is not ready for inject or eject.

Recommended Action: Manually remove any media remaining in the robot’smedia access port. If this status persists, check robotic console for errors.

Robotic status code: 252Message: Media access port is in inject mode

Explanation: Media access port is ready to inject and is not available for eject.

Recommended Action: Complete inject operation.

Robotic status code: 253Message: Media access port is in eject mode

Explanation: Media access port is ready to eject and is not available for inject.

Recommended Action: Complete eject operation.

Robotic status code: 254Message: Robot busy, inventory operation in progress

Explanation: The robot is not available because it is performing an inventory,using resources that are needed for the requested operation.

Recommended Action: Wait until the robot is done performing the inventorybefore starting new requests. Check the vendor or operating system administrativeinterfaces and logs to see if robotic resources are busy.

Robotic status code: 255Message: Robot busy, inject operation in progress

Explanation: The robot is not available because it is involved in an inject operation,using resources that are needed for the requested operation.

Recommended Action: Wait until the robot is done performing the injectoperation before starting new requests. check the vendor or operating systemadministrative interfaces and logs to see if robotic resources are busy.

Media and device management status codes and messagesAbout media and device management status codes and messages

544

Robotic status code: 256Message: Robot busy, multiple eject operation in progress

Explanation: The robot is unavailable because a multiple eject is in progress,using resources that are needed for the requested operation.

RecommendedAction: Wait until the robot is done performing the multiple ejectoperation before starting new requests. Check the vendor or operating systemadministrative interfaces and logs to see if robotic resources are busy.

Robotic status code: 257Message: Robot busy, multiple inject operation in progress

Explanation: The robot is unavailable because a multiple inject is in progress,using resources that are needed for the requested operation.

Recommended Action: Wait until the robot is done performing the multipleinject operation before starting new requests. check the vendor or operatingsystem administrative interfaces and logs to see if robotic resources are busy.

Robotic status code: 258Message: Cleaning/unknown media in drive

Explanation: A request to mount a tape failed because cleaning media was foundin the drive.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Retry the operation once the drive cleaning has completed.

Robotic status code: 259Message: Not authorized by VxSS

Explanation: A request was made to the robot daemons by an unauthorized user.

■ Verify that the user has the necessary permissions to perform this operation.

■ Verify that the VxSS settings are correct, under Host Properties in theNetBackup Administration Console. Information is available on using theVeritas Security Subsystem (VxSS).See the NetBackup Administrator’s Guide, Volume I.

545Media and device management status codes and messagesAbout media and device management status codes and messages

Robotic status code: 260Message: Robot busy, robot diagnostics in progress

Explanation: The requested robot is running a robot diagnostic.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Retry the operation when the robot diagnostic cycle is complete.

Robotic status code: 261Message: EMM error

Explanation: A request that was made to read/write data to EMM failed.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Run the tpconfig -d or vmquery -a command to verify that the EMM serveris actively processing commands.

Robotic status code: 262Message: Configuration has changed, robot daemons and ltid need restarting

Explanation: A device configuration change has been made that is not reflectedin the robotic daemon's run-time cache of the data.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Restart ltid and the robotics on this system or on the robot control host system.

Robotic error codesThese status codes are returned if a robotic daemon/process was started from thecommand line and an error occurs. For example, if the administrator executesthe following:

/usr/openv/volmgr/bin/tl8d

and no robots are configured, the following may be returned:

TL8: No robots are configured

Media and device management status codes and messagesAbout media and device management status codes and messages

546

These status codes are also logged to the system log.

Usually, robotic daemons/processes are not started from the command line, butare started automatically, as needed, when ltid starts.

Robot Error status code: 1Message: You must be ROOT to start daemon

Explanation: A user other than root started a robotic daemon. This status appliesto UNIX and Linux systems only.

Recommended Action: Log on as the root user before starting robotic daemons.Allow robotic daemons to be started automatically as needed by ltid (the devicedaemon).

Robot Error status code: 2Message: LTI Daemon may not be running

Explanation: On an attempt to start a robotic daemon or process, an attempt toconnect to the ltid message queue failed. This error indicates that ltid (thedevice daemon or NetBackup Device Manager service) may not be running.

■ Start ltid so that shared memory can be initialized, allowing the roboticdaemon/process to function.

■ If problems persist, examine command output, debug logs, and system logsfor a more detailed message on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use.

Robot Error status code: 3Message: Error in getting shared memory

Explanation: A robotic daemon/process was unable to get a shared memoryidentifier associated with a segment of shared memory that ltidmaintains. (ltidis the Media Manager device daemon on UNIX and Linux or the NetBackup DeviceManager service on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use.

547Media and device management status codes and messagesAbout media and device management status codes and messages

Robot Error status code: 4Message: Error in attaching the shared memory

Explanation: A robotic daemon/process was unable to attach a shared memorysegment that ltidmaintains. (ltid is the Media Manager device daemon on UNIXand Linux or the NetBackup Device Manager service on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use.

Robot Error status code: 5Message: Error in getting process Id

Explanation: A robotic daemon/process was unable to obtain its own processidentifier due to a system call failure.

Recommended Action: Investigate operating system functionality regarding aprocess obtaining its own process identifier.

Robot Error status code: 6Message: No devices are configured on the robot

Explanation: A robotic daemon/process was started, but no drives are configuredfor the robot.

RecommendedAction: Some robotic daemons or processes do not run if no drivesare configured for them to manage. Add or reconfigure one or more drives to bein the associated robot. Then, stop and restart ltid (the Media Manager devicedaemon on UNIX and Linux or NetBackup Device Manager service on Windows).

Robot Error status code: 7Message: No robots are configured

Explanation: A robotic daemon/process was started, but no robots of theassociated robot type are configured.

RecommendedAction: Robotic daemons or processes do not run if no robots areconfigured for the associated robot type. Add or reconfigure robots, then stop andrestart ltid (the Media Manager device daemon on UNIX and Linux or NetBackupDevice Manager service on Windows).

Media and device management status codes and messagesAbout media and device management status codes and messages

548

Robot Error status code: 8Message: No memory available

Explanation: A robotic daemon/process was unable to allocate memory. Thiserror occurs when insufficient system memory is available. This error could resultfrom the system being overloaded with too many processes and from insufficientphysical and virtual memory.

RecommendedAction: Free up memory by terminating unneeded processes. Addmore swap space or physical memory.

Robot Error status code: 9Message: Error in SEMAPHORE operation

Explanation: A process was unable to perform a semaphore operation (such aslock or unlock) associated with resources maintained by ltid. (ltid is the MediaManager device daemon on UNIX and Linux or the NetBackup Device Managerservice on Windows.)

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ On UNIX and Linux servers, gather the output of the ipcs -a command to seewhat resources are currently in use.

Robot Error status code: 10Message: Fork failure occurred

Explanation: A robotic daemon or process could not create a child process dueto a system error. This error is probably intermittent, based on the availability ofresources on the system (applies to UNIX and Linux servers only).

■ Restart the device daemon at a later time and investigate system problemsthat limit the number of processes.

■ Examine the system logs for a more detailed message on the error.See “Using debug logs” on page 423.

■ Restart the device daemon, then retry the operation and examine the systemlog file.

Robot Error status code: 11Message: System error occurred

Explanation: A robotic daemon/process encountered a system error.

549Media and device management status codes and messagesAbout media and device management status codes and messages

Recommended Action: Examine command output, debug logs, and system logsfor a more detailed message on the error.

See “Using debug logs” on page 423.

Robot Error status code: 12Message: Usage error in creating child process

Explanation: A robotic daemon/process could not create a child process due toan incompatibility between robotic software components.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

■ Verify that all Media Manager binaries are at a compatible version level.

Robot Error status code: 13Message: EMM error

Explanation: The robotic daemon had a problem communicating with EMM.

■ Make sure nbemm is running and responding to requests.

■ Examine command output, debug logs, and system logs for a more detailedmessage on the error.See “Using debug logs” on page 423.

Robot Error status code: 14Message: You must be administrator to execute

Explanation: A robotic process was started under a user account that lacksAdministrator privileges (applies to Windows systems only).

Recommended Action: Allow robotic daemons to be started automatically asneeded by the NetBackup Device Manager service. Ensure that this service startsfrom a user account with administrator privilege.

Robot Error status code: 16Message: Devices located in multiple domains

Explanation: A robotic daemon or process encountered an invalid deviceconfiguration. In this configuration, a single logical robot controls drives fromdifferent domains.

Media and device management status codes and messagesAbout media and device management status codes and messages

550

Recommended Action: Display the device configuration using tpconfig -d ora device configuration interface to see the robotic and the drive information thatis already configured. Ensure that the drive addresses do not span physicaldomains. Drives can only be configured in the same robot if they can be used withmedia from a single domain. The domain must include a single physical libraryor multiple libraries that are connected by a cartridge exchange or pass-throughmechanism.

Robot Error status code: 17Message: Robotic daemon not licensed

Explanation: A robotic daemon or process was started without the required,current product license, or a required database file was missing or corrupt.

■ Check product documentation for supported device configurations.

■ Obtain an additional software license that allows robots of the associated robottype to be configured. Or, limit the configuration to robot types that currentlicensing allows. Check for the existence and permissions of theexternal_robotics.txt file in the /usr/openv/share directory (UNIX andLinux) or in the install_path\NetBackup\share folder (Windows).

Media and device management messagesThis topic can be used as a cross reference to the status code descriptions andrecommended actions listed previously. Use the information in this topic if youknow the error message itself, but don’t have access to the status code number.

Table 6-1 lists the NetBackup error messages alphabetically in the left columnand the corresponding status code number in the right column.

Table 6-1 Media and device management messages and status codes

Status code numberError message

Device Configuration status code 36< NONE >

Robotic status code 240A memory allocation attempt failed in therobotic daemon

Media Manager status code 171a scratch pool is already defined

Device Configuration status code 16A SCSI inquiry sent to the device has failed

Media Manager status code 168ADAMM GUID does not exist in database

Media Manager status code 167ADAMM GUID is not unique in the database

551Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device Configuration status code 82Add Drive Name Rule request failed

Device Configuration status code 40Adding this device would exceed themaximum allowed

Device Configuration status code 39Adding this drive would exceed themaximum allowed

Media Manager status code 89another daemon already exists

Device Configuration status code 90Another device configuration is already inprogress

Media Manager status code 78barcode does not exist in database

Robotic status code 235barcode label is unreadable

Media Manager status code 36barcode not unique in database

Media Manager status code 122barcode tag is not unique in rule database

Media Manager status code 18cannot allocate requested memory

Device management status code 64Cannot assign a robotically controlled device

Device management status code 57Cannot assign due to media ID mismatch

Media Manager status code 51cannot auto-eject this robot type

Media Manager status code 52cannot auto-inject this robot type

Device Configuration status code 41Cannot change terminal mode

Media Manager status code 42cannot connect to robotic software daemon

Media Manager status code 70cannot connect to vmd [on host host name]

Device Configuration status code 42Cannot create miscellaneous workingrepository

Media Manager status code 92cannot delete assigned volume

Media Manager status code 118cannot delete one of the default volumepools

Device Configuration status code 44Cannot discover devices. See theTroubleshooting Guide for details.

Media and device management status codes and messagesMedia and device management messages

552

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device Configuration status code 1Cannot execute command, permission denied

Media Manager status code 76cannot get host name

Robotic status code 218Cannot move from media access port to slot

Robotic status code 219Cannot move from slot to media access port

Media Manager status code 21cannot obtain daemon lockfile

Robotic status code 243Cannot open/create the media access portstatus file

Media Manager status code 60cannot perform operation on this host

Device management status code 79Can not retrieve Job ID from Job Manager

Device management status code 20Cannot stop device daemon with tapesassigned

Media Manager status code 80cannot update database due to existingerrors

Media Manager status code 63child process killed by signal

Robotic status code 258Cleaning/unknown media in drive

Robotic status code 262Configuration has changed, robot daemonsand ltid need restarting

Robotic status code 224Control daemon connect or protocol error

Media Manager status code 195CORBA communication error

Device Configuration status code 3Could not get hostname

Device configuration status code 99Credentials already exist

Device Configuration status code 38Current version does not support remotedevice host

Media Manager status code 149current version does not support thisconfiguration

Media Manager status code 58daemon cannot obtain socket

Media Manager status code 59daemon failed accepting connection

553Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Media Manager status code 5daemon resources are busy

Media Manager status code 7daemon terminated

Media Manager status code 26database open operation failed

Media Manager status code 28database read operation read too few bytes

Media Manager status code 27database read record operation failed

Media Manager status code 23 and DeviceConfiguration status code 93

database server is down

Media Manager status code 32database write record operation failed

Device Configuration status code 84Delete Drive Name Rule request failed

Media Manager status code 153device entry is not unique in global devicedatabase

Media Manager status code 83device management error

Device Configuration status code 22Device path is already in use

Media Manager status code 182device test state file does not exist

Robot Error status code 16Devices located in multiple domains

Device Configuration status code 94Disk Optimization feature is not licensed

Robotic status code 216Door is open on cabinet

Device management status code 37Drive being assigned is either not NDMP oron the wrong NDMP client

Robotic status code 213Drive does not exist in robot

Device management status code 17Drive does not support pending requestdensity

Device Configuration status code 29Drive index is in use by another drive

Device management status code 2Drive is currently assigned

Device Configuration status code 35Drive name does not exist

Device Configuration status code 34Drive name is already in use by another drive

Media and device management status codes and messagesMedia and device management messages

554

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device Configuration status code 89Drive name rule has exceeded its maximumlength of 48 characters

Device management status code 62Drive not available in library for mountrequest

Device Configuration status code 20Duplicate device path names

Media Manager status code 196EMM database error

Media Manager status code 194EMM DB record not found

Robotic status code 261 and Robot Errorstatus code 13

EMM error

Device management status code 72EMM library call failed

Media Manager status code 57error auto-generating volume group

Robot Error status code 4Error in attaching the shared memory

Robot Error status code 5Error in getting process Id

Device management status code 32Error in getting semaphore

Robot Error status code 3Error in getting shared memory

Device management status code 14Error in IPC SHMAT call

Device management status code 13Error in IPC SHMGET call

Device management status code 28Error in MsgGet

Device management status code 6Error in Receiving Daemon Message

Device management status code 4Error in Receiving Operator Message

Device management status code 8Error in Receiving User Message

Device management status code 33Error in SEMAPHORE operation

Robotic Error status code 9Error in SEMAPHORE operation

Device management status code 5Error in Sending Daemon Message

Device management status code 3Error in Sending Operator Message

Device management status code 7Error in Sending User Message

555Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Media Manager status code 165Evaluation period expired. Go towww.symantec.com to order this product.

Media Manager status code 104failed appending to pool database

Media Manager status code 121failed appending to rule database

Media Manager status code 45failed changing terminal characteristics

Media Manager status code 88failed initiating child process

Media Manager status code 25failed making the database directory

Media Manager status code 86failed opening tmp output file

Device Configuration status code 13Failed reading drive or robot config file

Media Manager status code 44failed receiving from robotic softwaredaemon

Media Manager status code 72failed receiving from vmd

Media Manager status code 62failed redirecting input to pipe

Media Manager status code 87failed redirecting tmp output file

Media Manager status code 69failed sending request to vmd

Media Manager status code 43failed sending to robotic software daemon

Media Manager status code 71failed sending to vmd

Robotic status code 246Failed to find an available slot to inject to

Media Manager status code 189failed to initialize a connection to theEnterprise Media Manager

Device management status code 40File name already exists

Device management status code 25File name does not exist

Robot Error status code 10Fork failure occurred

Media Manager status code 193generic EMM SQL error

Media Manager status code 155global device database append operationfailed

Media and device management status codes and messagesMedia and device management messages

556

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device Configuration status code 49global device database host name is invalid

Media Manager status code 152global device database record not found

Device management status code 48Host is not the scan host for this shareddrive

Media Manager status code 146incompatible database version

Device Configuration status code 24Incomplete robot information

Device management status code 42Incorrect tpreq access mode

Media Manager status code 169internal database access failure

Device Configuration status code 57Internal NDMP error

Media Manager status code 10invalid barcode

Media Manager status code 75invalid change type

Media Manager status code 50invalid change-entry request

Robotic status code 207Invalid command code

Media Manager status code 4invalid command usage.

Media Manager status code 186invalid container id.

Media Manager status code 19invalid database host.

Media Manager status code 56invalid database version header

Media Manager status code 11invalid description

Device Configuration status code 19Invalid device path name

Device Configuration status code 14Invalid drive index

Media Manager status code 129invalid drive name

Device Configuration status code 86Invalid Drive Name Rule

Device management status code 23Invalid Drive Number

Device Configuration status code 27Invalid drive type for the robot

Device management status code 1Invalid Drive Type/Density

557Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Media Manager status code 191invalid EMM argument

Media Manager status code 113invalid expiration date

Device Configuration status code 88Invalid host

Media Manager status code 136invalid host name

Media Manager status code 114invalid maximum mounts

Media Manager status code 140invalid media generation rule

Media Manager status code 41invalid media ID for naming mode

Media Manager status code 8invalid media ID

Media Manager status code 9invalid media type

Device Configuration status code 64Invalid NDMP device

Device Configuration status code 55Invalid NDMP hostname

Device Configuration status code 60Invalid NDMP password

Media Manager status code 74invalid number of cleanings

Media Manager status code 141invalid number of mounts

Media Manager status code 142invalid offsite location

Media Manager status code 144invalid offsite return date

Media Manager status code 143invalid offsite sent date

Media Manager status code 148invalid offsite session id

Media Manager status code 147invalid offsite slot

Device management status code 12Invalid Operator

Media Manager status code 102invalid pool database entry

Media Manager status code 6invalid protocol request

Media Manager status code 73invalid query type

Media Manager status code 16invalid robot coord1

Media and device management status codes and messagesMedia and device management messages

558

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Media Manager status code 17invalid robot coord2

Device Configuration status code 28Invalid robot drive number for the robot type

Media Manager status code 14invalid robot host

Device Configuration status code 15Invalid robot number

Media Manager status code 13invalid robot number

Device Configuration status code 18Invalid robot type

Media Manager status code 12invalid robot type

Media Manager status code 119invalid rule database entry

Media Manager status code 173invalid scratch pool name

Device Configuration status code 8Invalid SCSI bus number for the robot

Device Configuration status code 10Invalid SCSI logical unit number for therobot

Device Configuration status code 7Invalid SCSI port number for the robot

Device Configuration status code 9Invalid SCSI target for the robot

Device Configuration status code 11Invalid Usage

Media Manager status code 15invalid volgroup

Media Manager status code 53invalid volume move mode

Device management status code 65Invalid volume pool specified

Media Manager status code 90invalid volume pool

Device management status code 22IPC Error: Daemon may not be running

Device management status code 10IPC sequence error

Device management status code 80Job Manager returned error: see activitymonitor

Device Configuration status code 85List Drive Name Rule request failed

Robot Error status code 2LTI Daemon may not be running

559Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device management status code 75LTI system error

Robotic status code 221Media access port already contains media

Robotic status code 220Media access port does not contain media

Robotic status code 250Media access port is available

Robotic status code 253Media access port is in eject mode

Robotic status code 252Media access port is in inject mode

Robotic status code 251Media access port is unavailable

Media Manager status code 166media access port not available

Device management status code 83Media does not exist in database

Media Manager status code 138media generation rule already exists

Media Manager status code 139media generation rule does not exist

Media Manager status code 95media ID is not the specified media type

Media Manager status code 34media ID not unique in database

Media Manager status code 101media type and volume group mismatch

Device management status code 56Mount canceled, device daemon isterminating

Device Configuration status code 74NDMP authorization error, verifyusername/password

Device Configuration status code 76NDMP config_get_connection_type failed

Device Configuration status code 75NDMP config_get_mover_type failed

Device Configuration status code 58NDMP failed to verify host

Device Configuration status code 71NDMP get_host_info failed

Device Configuration status code 72NDMP get_server_info failed

Device Configuration status code 62NDMP host does not exist

Device Configuration status code 61NDMP host exists, use change option

Media and device management status codes and messagesMedia and device management messages

560

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device Configuration status code 69NDMP host not connected

Device Configuration status code 59NDMP is not installed on platform

Device Configuration status code 63NDMP request failed

Device Configuration status code 66NDMP robot does not exist

Device Configuration status code 65NDMP robot exists, use change option

Device configuration status code 94NetApp Disk Storage Unit feature is notlicensed

Device configuration status code 100NetBackup Snapshot client not licensed

Media Manager status code 39network protocol error

Device management status code 50No action pending for given mount index

Media Manager status code 64no child process to wait for

Device management status code 59No cleaning tape is defined in the device'srobot or 0 cleanings remaining

Device Configuration status code 51No compatible device is registered at theseSCSI coordinates

Robot Error status code 6No devices are configured on the robot

Device management status code 82No drive available

Media Manager status code 47no entries changed

Media Manager status code 48no entries deleted

Media Manager status code 49no entries inserted

Device management status code 84No Error on operation, sideband data only

Device management status code 61No media found in device or robot slot,please verify

Robot Error status code 8No memory available

Device management status code 16No mount pending for given mount index

Media Manager status code 112no pools in the pool list

561Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device management status code 60Robot daemon and/or robotic hardware isnot available

Device management status code 52No robot is defined of this type

Robot Error status code 7No robots are configured

Device Configuration status code 97No valid license key for Disk Arrayconfiguration

Device Configuration status code 36<NONE>

Robotic status code 259Not authorized by VxSS

Media Manager status code 126not authorized to connect to vmd

Device management status code 19Only the administrative user can performthe requested operation

Device configuration status code 98Open Storage feature is not licensed

Media Manager status code 117operation not allowed on cleaning cartridge

Device management status code 55Operator denied mount request

Media Manager status code 137oprd request is not supported on the remotehost

Media Manager status code 96oprd returned abnormal status

Device management status code 39Parameter is invalid

Robotic status code 245Physical drive is not available

Media Manager status code 109pool does not exist in pool database

Media Manager status code 105poolname is not unique in pool database

Media Management status code 198pool not defined as a catalog backup pool

Media Manager status code 172pool not defined as a scratch pool

Media Manager status code 22pool type change is not allowed for<CatalogBackup> pool

Robotic status code 212Process killed by parent

Media and device management status codes and messagesMedia and device management messages

562

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Robotic status code 211Process killed by signal

Media Manager status code 20protocol error

Media Manager status code 150registering this host would exceed themaximum allowed

Media Manager status code 177request can only be performed on the Mediaand Device management Domain Server

Media Manager status code 1request completed

Device management status code 53Request has been queued (Cancel to clearmessage

Device management status code 26Request terminated because host notvalidated for volume pool

Device management status code 27Request terminated because media id isexpired

Device management status code 30Request terminated because media id willexceed maximum mount count

Device management status code: 71Request terminated because media is acleaning tape

Device management status code 35Request terminated because media isunavailable (in DOWN drive, misplaced,write protected or unmountable

Device management status code 69Request terminated because media isunmountable

Device management status code 70Request terminated because media is writeprotected

Device management status code 63Request terminated because mount requestsare disabled

Device management status code 66Request terminated because of volume poolmismatch

Device management status code 36Request terminated by tpunmount call fromanother process

563Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device management status code 24Requested drive could not be reserved

Media Manager status code 145requested drive is already reserved by host

Media Manager status code 130requested drive is already reserved

Robotic status code 238Requested drive is in an offline domain

Media Manager status code 132requested drive is not currently registered

Media Manager status code 134requested drive is not currently reserved

Media Manager status code 131requested drive is not registered for host

Media Manager status code 133requested drive is not reserved by host

Media Manager status code 135requested host is not currently registered

Robotic status code 229Requested operation is not supported by therobot

Robotic status code 217Requested slot already has cartridge

Robotic status code 226Requested slot contains the wrong tape

Robotic status code 228Requested slot does not exist in robot

Robotic status code 208Requested slot is empty

Robotic status code 215Requested tape in other or non-configureddrive

Robotic status code 239Requested volume is in an offline domain

Device Configuration status code 37Residence is not licensed for multihosteddrive support

Device management status code 81Retry later

Robotic status code 223Robot busy, cannot perform operation

Robotic status code 255Robot busy, inject operation in progress

Robotic status code 254Robot busy, inventory operation in progress

Robotic status code 256Robot busy, multiple eject operation inprogress

Media and device management status codes and messagesMedia and device management messages

564

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Robotic status code 257Robot busy, multiple inject operation inprogress

Robotic status code 260Robot busy, robot diagnostics in progress

Robotic status code 234Robot denied access to the resource

Device Configuration status code 25Robot drive number in use for this robot

Robotic status code 225Robot hardware or communication error

Robotic status code 236Robot has misplaced the media

Media Manager status code 82robot host and volume group mismatch

Device management status code 76Robot/LTI protocol error

Robotic status code 242Robot media access port does not exist

Media Manager status code 61robot number and robot host mismatch

Media Manager status code 54robot number and robot type mismatch

Media Manager status code 55robot number and volume group mismatch

Device Configuration status code 31Robot number does not exist

Robotic status code 214Robot number does not exist.

Device Configuration status code 21Robot number is already in use

Device Configuration status code 30Robot number is in use by another robot

Device management status code 74Robot operation failed

Media Manager status code 81robot type and volume group mismatch

Device Configuration status code 33Robot type must be controlled locally

Robotic status code 222Robotic arm has no addressable holder

Robot Error status code 17Robotic daemon not licensed

Robotic status code 206Robotic dismount failure

Robotic status code 205Robotic mount failure

Media Manager status code 37robotic volume position is already in use

565Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device Configuration status code 48RSM is not supported

Media Manager status code 97rule does not exist in rule database

Device Configuration status code 53Shared Storage Option (SSO) is not licensed

Media Manager status code 79specified robot is unknown to vmd

Robotic status code 200STATUS_SUCCESS

Device management status code 73Stopping device daemon with tapes assigned

Device Configuration status code 0Success

Device Configuration status code 87 andMedia Manager status code 2

System Error

Robot Error status code 11System error occurred

Robotic status code 230System error occurred during robotoperation

Device management status code 49Tape file path exceeds 255 charactermaximum

Device management status code 46Tape needs to be write enabled

Device management status code 58The device is not robotic, cannot performcleaning

Device Configuration status code 2The device_mappings file has invalid licenseinfo

Device Configuration status code 52The device name is not valid, no deviceresponded

Device management status code 15The drive is DOWN

Device management status code 21The drive is not ready or inoperable

Device Configuration status code 91The drive serial number already exists in thedevice database

Robotic status code 244The eject command was aborted by the user

Device Configuration status code 78The EMM server failed to process the request

Media and device management status codes and messagesMedia and device management messages

566

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Media Manager status code 162the global device database device name isinvalid

Media Manager status code 160the global device database device type isinvalid

Media Management status code 199the media is allocated for use

Media Manager status code 163the operation requested has failed

Media Manager status code 184the query with time failed because a limitwas reached

Device Configuration status code 95The requested operation is not valid for thespecified Disk Type

Media Manager status code 190the request sent to the Device Allocator hasfailed

Media Manager status code 164the robotic daemon returned an invalidvolume GUID

Media Manager status code 185the robotic library is full and may still havemedia in its map

Device Configuration status code 96The specified Disk Array Host is notconfigured in NetBackup

Media Manager status code 111the specified pool is not empty

Device Configuration status code 81This is a drive path operation, use the-drpath option

Media Manager status code 84this machine is not the database host

Device Configuration status code 17This robot type does not support multiplemedia types

Robotic status code 203Timeout waiting for robotic command

Media Manager status code 68too many volumes in volume group

Device configuration status code 79Unable to allocate memory for this process

Device configuration status code 67Unable to connect to NDMP host verifyhostname

567Media and device management status codes and messagesMedia and device management messages

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Device configuration status code 77 andDevice management status code 78

Unable to connect to the EMM server

Device configuration status code 70Unable to create NDMP session

Media Manager status code 176unable to find any records in the device testdatabase

Media Manager status code 127unable to generate a unique media id

Robotic status code 204Unable to initialize robot

Robotic status code 209Unable to open drive

Robotic status code 201Unable to open robotic path

Media Manager status code 175unable to open the device test state file

Device configuration status code 68Unable to process NDMP message

Robotic status code 210Unable to SCSI unload drive

Media Manager status code 67unable to send exit status

Robotic status code 202Unable to sense robotic device

Media Manager status code 46unexpected data from robotic softwaredaemon

Media Manager status code 40unexpected data received

Device management status code 41Unknown drive name

Media Manager status code 192unknown EMM error code

Device configuration status code 73Unsupported NDMP version

Device configuration status code 83Update Drive Name Rule request failed

Robot Error status code 12Usage error in creating child process

Media Manager status code 3user id was not superuser

Media Manager status code 85volume daemon fork failed

Media Manager status code 35volume does not exist in database

Media Manager status code 65volume group does not exist

Media and device management status codes and messagesMedia and device management messages

568

Table 6-1 Media and device management messages and status codes(continued)

Status code numberError message

Media Manager status code 116volume has exceeded maximum mounts

Media Manager status code 115volume has passed expiration date

Media Manager status code 93volume is already assigned

Robotic status code 249Volume is in home slot

Robotic status code 233Volume is in library, but not in drive domain

Robotic status code 237Volume is in use

Media Manager status code 94volume is not in specified pool

Robotic status code 232Volume not found in library

Media Manager status code 188, Devicemanagement status code 77, and Deviceconfiguration status code 92

VxSS Access Denied

Media Manager status code 187VxSS authentication failed.

Device management status code 44You do not have permission to create the file

Robot Error status code 14You must be administrator to execute

Robot Error status code 1You must be ROOT to start daemon

569Media and device management status codes and messagesMedia and device management messages

Media and device management status codes and messagesMedia and device management messages

570

Disaster recovery

This chapter includes the following topics:

■ About disaster recovery

■ Recommended backup practices

■ Disk recovery procedures for UNIX and Linux

■ Disk recovery procedures for Windows

■ Catalog recovery from an online backup

■ Clustered NBU server recovery for UNIX and Linux

■ Clustered NBU server recovery for Windows

About disaster recoveryEffective disaster recovery requires procedures specific to an environment. Theseprocedures provide detailed information regarding preparation for and recoveringfrom a disaster. Use the disaster recovery information in this chapter as a modelonly; evaluate and then develop your own disaster recovery plans and procedures.

Warning: Before you try any of the disaster recovery procedures in this chapter,Symantec recommends that you contact technical support.

This topic provides information about NetBackup installation and (if necessary),catalog recovery after a system disk failure. Symantec assumes that you recoverto the original system disk or one configured exactly like it.

7Chapter

Warning: NetBackup may not function properly if you reinstall NetBackup andrecover its catalogs on a system disk to a different partition or one that ispartitioned differently due to internal configuration information. Instead,configure a replacement disk with partitioning identical to the failed disk, thenreinstall NetBackup on the same partition on which it was originally installed.

Specific procedures that replace failed disks, build partitions and logical volumes,and reinstall operating systems can be complicated and time consuming. Suchprocedures are beyond the scope of this manual. Appropriate vendor-specificinformation should be referenced.

Recommended backup practicesThe following describes a set of recommended backup practices.

Selecting files to back upIn addition to backing up files on a regular basis, it is important to select thecorrect files to back up. The first concern is to include all files with that recordsthat are critical to users and the organization. You also need to back up systemand application files, so you can quickly and accurately restore a system to normaloperation if a disaster occurs.

Include all Windows system files in your backups. In addition to the other systemsoftware, the Windows system directories include the registry, which is neededto restore the client to its original configuration. If you use a NetBackup excludelist for a client, do not specify any Windows system files in that list.

You should not omit executables and other application files. You may want tosave tape by excluding these easy-to-reinstall files. However, backing up the entireapplication ensures that it is restored to its exact configuration. For example, ifyou have applied software updates and patches, restoring from a backup eliminatesthe need to reapply them.

Bare Metal RestoreNetBackup Bare Metal Restore (BMR) protects client systems by backing them upwith a policy configured for BMR protection. A complete description of BMRbackup and recovery procedures is available.

See the Bare Metal Restore System Administrator's Guide.

Disaster recoveryRecommended backup practices

572

Critical policiesWhen configuring a policy for online catalog backup, you can designate certainNetBackup policies as critical. Critical policies back up systems and data deemedcritical to end-user operation. During a catalog recovery, NetBackup verifies thatall of the media that is needed to restore critical policies are available.

Full backup after catalog recoveryIf the configuration contains Windows clients that have incremental backupconfigurations set to Perform Incrementals Based on Archive Bit, you shouldrun a full backup of these clients as soon as possible after a catalog recovery. Thearchive bit resets on the files that were incrementally backed up after the catalogbackup that was used for the catalog recovery. If a full backup of these clients isnot run after a catalog recovery, these files could be skipped and not backed upby subsequent incremental backups.

Online catalog backupsOnline, hot catalog backup is a policy-driven backup that supports tape-spanningand incremental backups. It allows for restoring catalog files from the Backup,Archive, and Restore interface. Online catalog backups may be run while otherNetBackup activity occurs, which provides improved support for environmentsin which continual backup activity is typical.

Online catalog backup disaster recovery filesSymantec recommends saving the disaster recovery files created by the onlinecatalog backup to a network share or removable device. Do not save the disasterrecovery files to the local computer. Catalog recovery from an online catalogbackup without the disaster recovery image file is a more complex andtime-consuming procedure.

Automated recoveryThe catalog disaster recovery file (created during an online catalog backup) isintended to automate the process of NetBackup recovery. If you recover a systemother than the one that originally made the backups, it should be identical to theoriginal system. For example, if the system that performs the recovery does notinclude NetBackup servers with identical names to those where the backups weremade, the automated recovery may not succeed.

573Disaster recoveryRecommended backup practices

Online catalog disaster recovery information emailYou should configure the online catalog backup policy to email a copy of thedisaster recovery information to a NetBackup administrator in your organization.Configure this policy as part of every catalog backup. Do not save the disasterrecovery information emails to the local computer. Catalog recovery without thedisaster recovery image file or the disaster recovery information email availableis exceedingly complex, time consuming, and requires assistance.

You may tailor the disaster recovery email process by providing a customizedmail script. More details are available.

See Reference Topics of the NetBackup Administrator's Guide, Volume II.

Identifying the correct catalog backupA complete catalog should be recovered from the most recent series of backups.If not, the potential for inconsistency between the catalog and the actual state orcontents of storage media could exist.

The following are two examples of the need for recovering from the most recentseries of backups:

■ Tape media images have all expired after the catalog backup that the recoverywas done from and the tape designated for and possibly re-used.

■ Disk-based media whose images expired after the catalog backup that therecovery was done from and the images were deleted from the disk.

Catalog recovery timeSystem environment, catalog size, location, and backup configuration (full andincremental policy schedules) all help determine the time that is required torecover the catalog. Carefully plan and test to determine the catalog backupmethods that result in the desired catalog recovery time.

Master and media server backupsThe NetBackup catalog backup protects your configuration data and catalog data.You should also set up backup schedules for the master and media servers in yourNetBackup installation. These schedules protect the operating systems, deviceconfigurations, and other applications on the servers.

Master or media server recovery procedures when the system disk has been lostassume that the servers are backed up separately from the catalog backup. Backupsof master and media servers should not include NetBackup binaries, configurationor catalog files, or relational database data.

Disaster recoveryRecommended backup practices

574

Disk recovery procedures for UNIX and LinuxThe following section describes the procedures for three different types of diskrecovery for UNIX and Linux:

■ Master server disk recovery procedures

■ Media server disk recovery procedures

■ Client disk recovery procedures

Disk-based images that reside on SharedDisk, AdvancedDisk, or on OpenStoragedisks cannot be recovered by means of the NetBackup catalog. These disk imagesmust be recovered by means of the NetBackup import feature. For informationon import,

See the topic on importing NetBackup images in the NetBackup Administrator’sGuide, Volume I.

When the disk image is imported, NetBackup does not recover the original catalogentry for the image. Instead, a new catalog entry is created.

Recovering the master server disk for UNIX and LinuxThe procedure in this section explains how to recover data if the system disk failson a UNIX or Linux NetBackup master server.

The following two scenarios are covered:

■ Root file system is intact. The operating system, NetBackup software and some(if not all) other files are assumed to be lost.

■ Root file system is lost along with everything else on the disk. This situationrequires a total recovery. This recovery reloads the operating system to analternate boot disk and boots from this disk during recovery. This operationlets you recover the root partition without risking a crash caused by overwritingfiles that the operating system uses during the restore.

For NetBackup master and media servers, the directory locations of the NetBackupcatalog become an integral part of NetBackup catalog backups. Any recovery ofthe NetBackup catalog requires identical directory paths or locations be createdduring the NetBackup software reinstallation. Disk partitioning, symbolic links,and NetBackup catalog relocation utilities may be needed.

NetBackup Bare Metal Restore (BMR) protects client systems by backing them upwith a policy configured for BMR protection. Information is available that describesbackup and recovery procedures.

See the Bare Metal Restore System Administrator's Guide.

575Disaster recoveryDisk recovery procedures for UNIX and Linux

Recovering the master server when root is intactThe following procedure recovers the master server by reloading the operatingsystem, then restoring NetBackup, and finally restoring all other files.

To recover

1 Verify that the operating system works, that any require patches are installed,and that specific configuration settings are made. Take corrective action asneeded.

2 Reinstall NetBackup software on the server you want to recover.

See the NetBackup Installation Guide for UNIX for instructions.

3 Install any NetBackup patches that had been previously installed. See thedocumentation that was included with the patch software.

Note: Symantec does not support the recovery of a catalog image that wasbacked up using an earlier version of NetBackup.

4 If any of the default catalog directories have changed that may be reflectedin the NetBackup catalog backups, recreate those directories before the catalogrecovery.

The following are examples:

■ Use of symbolic links as part of the NetBackup catalog directory structure.

■ Use of the NetBackup nbdb_move command to relocate parts of theNetBackup relational database catalog.

5 If the recovery scenario involves restoring policy or catalog backups, theappropriate recovery device(s) must be configured, which may involve thefollowing tasks:

■ Install and configure the robotic software for the devices that read backupsof the NetBackup catalog and regular backups of the disk being restored.If a non-robotic drive is available that can read these backups, then norobot is required. Although manual intervention is required if multiplepieces of media are required.See the NetBackup Device Configuration Guide.

■ Using the NetBackup Device Configuration Wizard to discover andconfigure the recovery device in NetBackup.See the NetBackup Administrator's Guide, Volume I.

■ Using the NetBackup command tpautoconf to discover and configure therecovery device in NetBackup.

Disaster recoveryDisk recovery procedures for UNIX and Linux

576

■ See the NetBackup Command Guide.

■ Updating the device mapping files.

■ See the NetBackup Administrator’s Guide, Volume II.

6 If you must restore from policy or catalog backups that were done to media,the appropriate media may have to be configured in NetBackup.

See the NetBackup Administrator’s Guide, Volume I.

Configuring the media may require some or all of the following tasks:

■ Manually load the required media into a stand-alone recovery device.

■ Use the NetBackup utilities such as robtest or vendor-specific roboticcontrol software to load media into the required recovery device or devices.

■ Using the NetBackup Volume Configuration Wizard to inventory the mediacontents of a robotic device.

■ Using the vendor-specific robotic control software to load the media intothe required recovery device(s).

7 Recover the NetBackup catalogs to the server you are recovering.

The NetBackup catalogs can be recovered only to the same directory structurefrom which they were backed up (alternate path recovery is not allowed).

8 Stop and restart all NetBackup daemons. Use the following NetBackupcommands, or use the Activity Monitor in the NetBackup AdministrationConsole.

Note: Your configuration may include an EMM server that is separate fromthe master server. If so, start NetBackup on the EMM server before startingNetBackup on the master server.

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

9 Start the NetBackup Backup, Archive, and Restore interface (or the bp

command) and restore other files to the server as desired. When the files arerestored, you are done.

Recovering the master server when the root partition is lostThe general steps to this procedure are: 1) load the operating system on analternate boot disk, 2) install NetBackup on that disk, 3) recover NetBackup catalogsto that disk, 4) restore the root partition and the latest backed up files to the

577Disaster recoveryDisk recovery procedures for UNIX and Linux

recovery disk, and 5) copy the NetBackup catalogs from the alternate disk to therecovery disk.

This procedure assumes that the root file system is lost along with everythingelse on the disk. This procedure reloads the operating system to an alternate bootdisk and boots from that disk during recovery. This operation lets you recoverthe root partition without risking a crash caused by overwriting files that theoperating system uses during the restore.

To recover the master server when the root partition is lost

1 Load the operating system on an alternate boot disk, using the same procedureas you would normally use for the server type.

2 Create on the alternate disk the partition and directory where NetBackup andits catalogs (if applicable) and databases resided on the original disk. Bydefault, they reside under the /usr/openv directory.

3 Verify that the operating system works, that any required patches areinstalled, and that specific configuration settings are made. Take correctiveaction as needed.

4 Install NetBackup on the alternate disk. Install only the robotic software forthe devices required to read backups of the NetBackup catalogs and regularbackups of the disk being restored. If a non-robotic drive can read thesebackups, no robot is required.

5 Install any NetBackup patches that had been previously installed. See thedocumentation that was included with the patch software.

6 If any changes to the default catalog directories would be reflected in theNetBackup catalog backups, recreate those directories before the catalogrecovery.

Examples of those directories are the following:

■ Use of symbolic links as part of the NetBackup catalog directory structure.

■ Use of the NetBackup nbdb_move command to relocate parts of theNetBackup relational database catalog.

7 If the recovery scenario involves restoring policy or catalog backups, theappropriate recovery device(s) must be configured.

Device configuration may include the following tasks:

■ Install and configure the robotic software for the devices that read backupsof the NetBackup catalog and regular backups of the disk being restored.If a non-robotic drive is available that can read these backups, then norobot is required. Although manual intervention is required if multiplepieces of media are required.

Disaster recoveryDisk recovery procedures for UNIX and Linux

578

See the NetBackup Device Configuration Guide.

■ Use the NetBackup Device Configuration Wizard to discover and configurethe recovery device in NetBackup.See the NetBackup Administrator's Guide, Volume I.

■ Use the NetBackup command tpautoconf to discover and configure therecovery device in NetBackup.See the NetBackup Command manual.

■ Update the device mapping files.See the NetBackup Administrator's Guide, Volume II.

8 If you must restore from policy or catalog backups that were done to media,the appropriate media may have to be configured in NetBackup.

See the NetBackup Administrator’s Guide, Volume I.

Configuring the media may require some or all of the following tasks:

■ Manually load the required media into a stand-alone recovery device.

■ Use the NetBackup utilities such as robtest or vendor-specific roboticcontrol software to load media into the required recovery device or devices.

■ Using the NetBackup Volume Configuration Wizard to inventory the mediacontents of a robotic device.

■ Using the vendor-specific robotic control software to load the media intothe required recovery device(s).

9 Recover the NetBackup catalogs to the alternate disk.

See “Catalog recovery from an online backup” on page 591.

The catalogs can be recovered only to the same directory structure fromwhich they were backed up (alternate path recovery is not allowed).

579Disaster recoveryDisk recovery procedures for UNIX and Linux

10 Start the NetBackup Backup, Archive, and Restore interface (or the bp

command) and restore the latest backed up version of all files to the disk youare recovering.

You restore these files from the backup of the master server, not from theNetBackup catalog backup. Be sure to specify the disk that you recover as thealternate recovery location.

Warning: Do not restore files to the /usr/openv/var, /usr/openv/db/data,or /usr/openv/volmgr/database directories (or relocated locations) ordirectories that contain NetBackup database data. This data was recoveredto the alternate disk in step 9 and is copied back to the recovery disk in step12.

11 Stop all NetBackup processes that you started from NetBackup on the alternatedisk. Use the Activity Monitor in the NetBackup Administration Console orthe following:

/usr/openv/netbackup/bin/bp.kill_all

12 Maintaining the same directory structure, copy the NetBackup catalogs fromthe alternate disk to the disk that you recover. These are the catalogsrecovered in step 9.

13 Make the recovered disk the boot disk again and restart the system.

14 Start and test the copy of NetBackup on the disk that you have recovered.

Note: If your configuration includes an Enterprise Media Manager (EMM)server that is separate from the master server, start NetBackup on the EMMserver before starting NetBackup on the master server.

/usr/openv/netbackup/bin/bp.start_all

Try the NetBackup Administration utilities. Also, try some backups andrestores.

15 When you are satisfied that the recovery is complete, delete the NetBackupfiles from the alternate disk. Or, unhook that disk, if it is a spare.

Disaster recoveryDisk recovery procedures for UNIX and Linux

580

Recovering the NetBackup media server disk for UNIX and LinuxNetBackup 6.0 and later media servers store information in the NetBackuprelational database. If you need to recover the system disk on a NetBackup mediaserver, the recommended procedure is similar to disk recovery for the client.

See “Recovering the client disk” on page 581.

Note:A separate computer that functions as a NetBackup 6.0 or later media serveris available only on NetBackup Enterprise Server. For NetBackup Serverinstallations, the master server and the media server are installed on the samesystem and have the same host name. Therefore, recovering the master serverdisk also recovers the media server.

Recovering the client diskNetBackup Bare Metal Restore (BMR) protects client systems by backing them upwith a policy configured for BMR protection. A complete description of BMRbackup and recovery procedures is available.

See the Bare Metal Restore Administrator's Guide.

If you installed and configured NetBackup Intelligent Disaster Recovery (IDR) onthe client system, use the recovery procedures in theNetBackup Administrator’sGuide, Volume II instead of the following instructions:

To recover the system disk on a client workstation

1 Reload the operating system as you normally would for a client workstationof that type.

If the root file system is lost, the best approach may be to reload the operatingsystem on an alternate boot disk and start from this disk. After restoring thesystem, restore root to its original partition. This operation lets you recoverthe root partition without risking a crash due to overwriting files that theoperating system uses during the restore. The procedure is similar to theprocedure that is used for the master server, except that recovering theNetBackup catalogs is not necessary.

See “Recovering the master server disk for Windows” on page 582.

2 Reinstall NetBackup client software and patches.

3 Use the NetBackup Backup, Archive, and Restore interface to select andrestore files.

581Disaster recoveryDisk recovery procedures for UNIX and Linux

Disk recovery procedures for WindowsThe following section describes the procedures for three different types of diskrecovery for Windows:

■ Master server disk recovery procedures

■ Media server disk recovery procedures

■ Client disk recovery procedures

Disk-based images that reside on SharedDisk, AdvancedDisk, or on OpenStoragedisks cannot be recovered by means of the NetBackup catalog. These disk imagesmust be recovered by means of the NetBackup import feature. For informationon import, refer to the section on importing NetBackup images in the followingmanual:

See NetBackup Administrator’s Guide, Volume I.

Note: When the disk image is imported, NetBackup does not recover the originalcatalog entry for the image. Instead, a new catalog entry is created.

Recovering the master server disk for WindowsThe procedure in this section explains how to recover data if one or more diskpartitions are lost on a Windows NetBackup master server.

The following two scenarios are covered:

■ Windows is intact and not corrupted. The system still starts Windows, butsome or all other partitions are lost. NetBackup software is assumed to be lost.

■ All disk partitions are lost. Windows must be reinstalled, which is a totalrecovery. These procedures assume that the NetBackup master disk wasrunning a supported version of Windows and that the defective hardware hasbeen replaced.

For NetBackup master and media servers, the directory locations of the NetBackupcatalog become an integral part of NetBackup catalog backups. Any recovery ofthe NetBackup catalog requires the identical directory paths or locations be createdbefore the catalog recovery.

Recovering the master server with Windows intactThis procedure shows how to recover the NetBackup master server with theWindows operating system intact.

Disaster recoveryDisk recovery procedures for Windows

582

To recover the master server with Windows intact

1 Determine the install_path in which NetBackup is installed. By default,NetBackup is installed in the C:\Program Files\VERITAS directory.

2 Determine if any directory paths or locations need to be created for NetBackupcatalog recovery.

3 Partition any disks being recovered as they were before the failure (ifpartitioning is necessary). Then reformat each partition as it was before thefailure.

4 Reinstall NetBackup software on the server you are recovering.

Refer to the NetBackup Installation Guide for Windows.

5 Install any NetBackup patches that had been previously installed. See thedocumentation that was included with the patch software.

6 If any changes to the default catalog directories would be reflected in theNetBackup catalog backups, recreate those directories before the catalogrecovery. For example, use the NetBackup nbdb_move command to relocateparts of the NetBackup relational database catalog.

7 If the recovery scenario involves restoring policy or catalog backups, theappropriate recovery devices must be configured.

You may have to do some or all of the following:

■ Install and configure the robotic software for the devices that read backupsof the NetBackup catalog and regular backups of the disk being restored.If a non-robotic drive is available that can read these backups, then norobot is required. Although manual intervention is required if multiplepieces of media are required.See the NetBackup Device Configuration Guide.

■ Use the NetBackup Device Configuration Wizard to discover and configurethe recovery device in NetBackup.See the NetBackup Administrator's Guide, Volume I.

■ Using the NetBackup command tpautoconf to discover and configure therecovery device in NetBackup.See the NetBackup Commands manual.

■ Updating the device mapping files.See the NetBackup Administrator’s Guide, Volume II.

8 If the recovery scenario involves restoring policy or catalog backups, theappropriate recovery device(s) must be configured.

Configuring the media may involve the following tasks:

583Disaster recoveryDisk recovery procedures for Windows

■ Manually load the required media into a stand-alone recovery device.

■ Use NetBackup utilities such as robtest or vendor-specific robotic controlsoftware to load media into the required recovery devices.

■ Use the NetBackup Volume Configuration Wizard to inventory the mediacontents of a robotic device.

■ Use the vendor-specific robotic control software to load the media intothe required recovery device(s).

9 Recover the NetBackup catalogs.

See “Catalog recovery from an online backup” on page 591.

10 When catalog recovery is complete, stop and restart the NetBackup services.Use the following bpdown and bpup commands, the Activity Monitor in theNetBackup Administration Console, or the Services application in the WindowsControl Panel.

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

Your configuration may include an EMM server that is separate from themaster server. If so, start NetBackup on the EMM server before startingNetBackup on the master server.

Warning: In step 11, do not restore files to the install_path\NetBackup\db,install_path\NetBackupDB, install_path\NetBackup\var, orinstall_path\Volmgr\database directories. The catalogs were recoveredin step 9 and overwriting them with regular backups leave them in aninconsistent state.

If the NetBackup relational database files were relocated using nbdb_move

from install_path\NetBackupDB\data, they are recovered in step 9 andshould not be restored in step 11.

11 To restore all other files, do the following in the order shown:

■ Start the NetBackup Administration interface on the master server.

■ Start the Backup, Archive, and Restore utility.

■ Browse for restores and select only the partitions that were lost. Selectthe system directory (typically C:\Winnt), which ensures that all registryfiles are restored.

Disaster recoveryDisk recovery procedures for Windows

584

■ Deselect the install_path\NetBackup\db, install_path\NetBackupDB,install_path\NetBackup\var, and install_path\Volmgr\database

directories (see the caution in step 10).

■ If you reinstall Windows, select the Overwriteexistingfiles option, whichensures that existing files are replaced with the backups.

■ Start the restore.

12 Reboot the system, which replaces any files that were busy during the restore.When the boot process is complete, the system is restored to the state it wasin at the time of the last backup.

Recovering the master server and WindowsThis procedure assumes that all disk partitions in Windows are lost.

To recover the master server and Windows

1 Install a minimal Windows operating system (perform the Express install).

■ Install the same type and version of Windows software that was usedpreviously.

■ Install Windows in the same partition that was used before the failure.

■ Install any required patches. Take corrective action as needed.

■ Specify the default workgroup. Do not restore the domain.

■ Install and configure special drivers or other software that is required toget the hardware operational (for example, a special driver for the diskdrive).

■ Install SCSI or other drivers as needed to communicate with the tapedrives on the system.

■ Follow any hardware manufacturer's instructions that apply, such asloading SSD on a Compaq system.

■ Reboot the system when Windows installation is complete.

2 Determine the install_path in which NetBackup is installed. By default,NetBackup is installed in the C:\Program Files\VERITAS directory.

3 Determine if any directory paths or locations need to be created for NetBackupcatalog recovery.

4 If necessary, partition any disks being recovered as they were before thefailure. Then reformat each partition as it was before the failure.

5 Reinstall NetBackup software on the server being recovered. Do not configureany NetBackup policies or devices at this time.

585Disaster recoveryDisk recovery procedures for Windows

6 Install any NetBackup patches that had been previously installed. See thedocumentation that was included with the patch software.

7 If any changes to the default catalog directories would be reflected in theNetBackup catalog backups, recreate those directories before the catalogrecovery. For example, use the NetBackup nbdb_move command to relocateparts of the NetBackup relational database catalog.

8 If the recovery scenario involves restoring policy or catalog backups, theappropriate recovery device or devices have to be configured.

You may have to do all or some of the following tasks:

■ Install and configure the robotic software for the devices that read backupsof the NetBackup catalog and regular backups of the disk being restored.If a non-robotic drive is available that can read these backups, then norobot is required. Although manual intervention is required if multiplepieces of media are required.See the NetBackup Device Configuration Guide.

■ Using the NetBackup Device Configuration Wizard to discover andconfigure the recovery device in NetBackup.See the NetBackup Administrator's Guide, Volume I.

■ Using the NetBackup command tpautoconf to discover and configure therecovery device in NetBackup.See the NetBackup Commands manual.

■ Updating the device mapping files.See the NetBackup Administrator’s Guide, Volume II.

9 If you must restore from policy or catalog backups that were done to media,the appropriate media may have to be configured in NetBackup.

See the NetBackup Administrator’s Guide, Volume I.

When you configure the media, you may have to do some or all of thefollowing:

■ Manually load the required media into a stand-alone recovery device.

■ Use the NetBackup utilities such as robtest or vendor-specific roboticcontrol software to load media into the required recovery devices.

■ Using the NetBackup Volume Configuration Wizard to inventory the mediacontents of a robotic device.

■ Using the vendor-specific robotic control software to load the media intothe required recovery devices.

Disaster recoveryDisk recovery procedures for Windows

586

10 Recover the NetBackup catalogs.

See “Catalog recovery from an online backup” on page 591.

11 When catalog recovery is complete, stop and restart the NetBackup services.Use the following bpdown and bpup commands, the Activity Monitor in theNetBackup Administration Console, or the Services application in the WindowsControl Panel.

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

If your configuration includes an Enterprise Media Manager (EMM) serverthat is separate from the master server, start NetBackup on the EMM serverfirst.

Warning:

In step 12, do not restore files to the install_path\NetBackup\db,install_path\NetBackupDB, install_path\NetBackup\var, orinstall_path\Volmgr\databasedirectories. These directories were recoveredin step 10 and overwriting them with regular backups leaves the catalogs inan inconsistent state. If the relational database files were relocated usingnbdb_move from install_path\NetBackupDB\data, they are recovered instep 10 and should not be restored in step 12.

12 To restore all other files, do the following in the order presented:

■ Start the NetBackup Administration interface on the master server.

■ Start the Backup, Archive, and Restore client interface.

■ Browse for restores and select only the partitions that were lost. Selectthe system directory (typically C:\Winnt), which ensures that all registryfiles are restored.

■ Deselect the install_path\NetBackup\db, install_path\NetBackupDB(or relocated NetBackup relational database path),install_path\NetBackup\var, or install_path\Volmgr\databasedirectories.See the caution in this procedure).

■ If you reinstall Windows, select the Overwriteexistingfiles option, whichensures that existing files are replaced with the backups.

587Disaster recoveryDisk recovery procedures for Windows

■ Start the restore.

13 Restart the system, which replaces any files that were busy during the restore.When the boot process is complete, the system is restored to the state it wasin at the time of the last backup.

Recovering the NetBackup media server disk for WindowsA separate computer that functions as a NetBackup 6.0 or later media server isavailable only on NetBackup Enterprise Server. For NetBackup Server installations,the master server and the media server are installed on the same system and havethe same host name. Therefore, recovering the master server disk also recoversthe media server.

NetBackup media servers store their information in the NetBackup relationaldatabase. If you need to recover the system disk on a NetBackup media server,the recommended procedure is similar to disk recovery for the client.

See “Recovering the client disk” on page 581.

Recovering the client diskThe following procedure explains how to perform a total recovery of a WindowsNetBackup client in the event of a system disk failure.

NetBackup Bare Metal Restore (BMR) protects client systems by backing them upwith a policy configured for BMR protection. A complete description of BMRbackup and recovery procedures is available.

See the Bare Metal Restore System Administrator's Guide.

Note: If you installed and configured NetBackup Intelligent Disaster Recovery(IDR) on the client system, refer to theNetBackupAdministrator’s Guide, VolumeII, for recovery procedures instead of the instructions in this procedure.

This procedure assumes that the Windows operating system and NetBackup arereinstalled to boot the system and perform a restore.

The following are additional assumptions:

■ The NetBackup client was running a supported Microsoft Windows version.

■ The NetBackup client was backed up with a supported version of NetBackupclient and server software.

■ The NetBackup master server to which the client sent its backups is operational.You request the restore from this server.

Disaster recoveryDisk recovery procedures for Windows

588

■ The backups included the directory where the operating system and its registryresided.If the backups excluded any files that resided in the directory, you may not beable to restore the system to be identical to the previous configuration.

■ Defective hardware has been replaced.

Before starting, verify that you have the following:

■ Windows system software to reinstall on the NetBackup client that is beingrestored. Reinstall the same type and version of software that was previouslyused.

■ NetBackup client software to install on the client that is being restored.

■ Special drivers or other software that is required to make the hardwareoperational (for example, a special driver for the disk drive).

■ IP address and host name of the NetBackup client.

■ IP address and host name of the NetBackup master server.

■ The partitioning and formatting scheme that was used on the system to berestored. You must duplicate that scheme during Windows installation.

To recover a Windows client disk

1 Install a minimal Windows operating system (perform the Express install).

During the installation, do the following tasks:

■ Partition the disk as it was before the failure (if partitioning is necessary).Then, reformat each partition as it was before the failure.

■ Install the operating system in the same partition that was used beforethe failure.

■ Specify the default workgroup. Do not restore to the domain.

■ Follow any hardware manufacturers’ instructions that apply.

2 Reboot the system when the installation is complete.

3 Configure the NetBackup client system to re-establish network connectivityto the NetBackup master server.

For example, if your network uses DNS, the configuration on the client mustuse the same IP address that was used before the failure. Also, it must specifythe same name server (or another name server that recognizes both theNetBackup client and master server). On the client, configure DNS in theNetwork dialog, accessible from the Windows Control Panel.

4 Install NetBackup client software.

589Disaster recoveryDisk recovery procedures for Windows

Refer to theNetBackupInstallationGuide forWindows for instructions. Ensurethat you specify the correct names for the client server and master server.

■ To specify the client name, start the Backup, Archive, and Restore interfaceon the client and click NetBackup Client Properties on the File menu.Enter the client name on the General tab of the NetBackup ClientProperties dialog.

■ To specify the server name, click SpecifyNetBackupMachinesandPolicyType on the File menu.

5 Install any NetBackup patches that had previously been installed.

6 Enable debug logging by creating the following debug log directories on theclient:

install_path\NetBackup\Logs\tar

install_path\NetBackup\Logs\bpinetd

NetBackup creates logs in these directories.

7 Stop and restart the NetBackup Client service.

This action enables NetBackup to start logging to the bpinetd debug log.

8 Use the NetBackup Backup, Archive, and Restore interface to restore thesystem files and user files to the client system.

For example, if all files are on the C drive, restoring that drive restores theentire system.

To restore files, you do not need to be the administrator, but you must haverestore privileges. For instructions, refer to the online Help or refer to thefollowing:

See the NetBackup Backup, Archive, and Restore Getting Started Guide.

NetBackup restores the registry when it restores the Windows system files.For example, if the system files are in the C:\Winnt directory, NetBackuprestores the registry when it restores that directory and all its subordinatesubdirectories and files.

9 Check for ERR or WRN messages in the log files that are in the directoriesyou created in step 6.

If the logs indicate problems with the restore of Windows system files, resolvethose problems before proceeding.

Disaster recoveryDisk recovery procedures for Windows

590

10 Stop the NetBackup Client service and verify that bpinetd is no longerrunning.

11 Restart the NetBackup client system.

When the boot process is complete, the system is restored to the state it wasin at the time of the last backup.

Catalog recovery from an online backupThis topic explains how to recover a catalog that was backed up using the online,hot catalog backup method that is described in the following manual:

See the NetBackup Administrator’s Guide, Volume I.

This procedure can be stand-alone or part of a larger disk recovery procedure.See one of the following topics:

See “Disk recovery procedures for UNIX and Linux” on page 575.

See “Disk recovery procedures for Windows” on page 582.

Note:When any online catalog backup recovery try that involves media completes,NetBackup changes the state of the media that contains the catalog backup tofrozen. This operation prevents a subsequent accidental overwrite action on thefinal catalog backup image on the media. This final image pertains to the actualcatalog backup itself and its recovery is not part of the catalog recovery.

You can unfreeze the media.

See “Unfreezing online catalog recovery media” on page 624.

Note:You must have root (administrative) privileges to perform these procedures.

You can recover the catalog from an online, hot backup in either of two ways:

■ Recovering the entire catalog from an online backupThis procedure is the recommended method for recovering the entire catalogand recovers the NetBackup relational database as well as NetBackup policyfiles, backup image files, and configuration files.

■ Recovering the catalog image fileThis method recovers only the NetBackup policy files, backup image files, andconfiguration files. Use this method if the NetBackup relational database isvalid but NetBackup policy, backup image, or configuration files are lost. The

591Disaster recoveryCatalog recovery from an online backup

NetBackup relational database can also be recovered separately using thebprecover -nbdb command.

Recovering the entire catalog from an online backupThe entire catalog can be recovered by using the Catalog Recovery Wizard or thetext-based bprecover -wizard command.

Warning:Do not run any client backups before you recover the NetBackup catalog.

The Catalog Recovery Wizard screens that appear when performing theseprocedures are very similar for UNIX, Linux, and Windows platforms. Only theWindows screens are shown in text in the following procedures.

Recovering the entire catalog using the Catalog RecoveryWizardThis procedure shows you how to recover the entire catalog using the CatalogRecovery Wizard. You must have root (administrative) privileges.

Note:The Catalog Recovery wizard does not work after performing a change serveroperation. You must be logged on locally to the master server that is beingrecovered.

Note: During the catalog recovery process, services may be shut down andrestarted. If NetBackup is configured as a highly available application (cluster orglobal cluster), freeze the cluster before starting the recovery process to preventa failover. Then unfreeze the cluster after the recovery process is complete.

Disaster recoveryCatalog recovery from an online backup

592

To recover the entire catalog

1 Your configuration may include an Enterprise Media Manager (EMM) serverthat is separate from the master server. If so, start NetBackup on the EMMserver before starting NetBackup on the master server.

2 Start NetBackup by entering the following:

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpup

The NetBackup Administration Console appears.

3 If the necessary devices are not already configured, configure them inNetBackup.

4 Make available to NetBackup the media that contains the catalog backup.

5 Click RecovertheCatalogs on the NetBackup Administration Console to startthe Catalog Recovery Wizard.

The Welcome screen appears.

593Disaster recoveryCatalog recovery from an online backup

6 Click Next on the Welcome screen to display the CatalogDisasterRecoveryFile screen.

This wizard relies on the disaster recovery information that is generatedduring the online catalog backup. Part of the online catalog backupconfiguration that is included indicates where the disaster recoveryinformation file was to be stored and-or sent.

In most cases, you specify the most recent disaster recovery information fileavailable, unless some form of corruption has occurred and you want torestore to an earlier state of the catalog. If the most recent catalog backupwas an incremental, use the disaster recovery file from the incrementalbackup. (There is no need to first restore the full backup that is followed bythe incremental.)

Indicate where the disaster recovery file is stored by entering the fullyqualified path to the disaster recovery file.

More information is available on the email that is sent and the attacheddisaster recovery file.

See “Recovering the catalog without the disaster recovery file” on page 615.

Disaster recoveryCatalog recovery from an online backup

594

7 The wizard waits while NetBackup searches for the necessary media sources,then informs you if the necessary backup ID of the disaster recovery imageis located.

Or, if the media is not located, the wizard lists which media is needed to updatethe database.

Follow the wizard instructions to insert the media that is indicated and runan inventory to update the NetBackup database. The information that isdisplayed on this screen depends on whether the recovery is from a full backupor an incremental backup.

If an online catalog backup policy includes both full and incremental backups,the disaster recovery email may indicate either a full or an incremental backupfor recovery. An incremental backup recovery completely recovers the entirecatalog because it references information from the last full backup. You don’tneed to first recover the last full catalog backup, then subsequent incrementalbackups.

595Disaster recoveryCatalog recovery from an online backup

8 When the required media sources are all found, click Next to display theDisaster Recovery Method screen. The Recover entire NetBackup catalogradio option is selected.

9 With the RecoverentireNetBackupcatalog radio option selected, click Nextto initiate the recovery of the entire NetBackup catalog.

NetBackup restores the entire NetBackup relational database, which includesthe following:

■ NBDB database (including the EMM database)

■ BMR database (if applicable)

■ NetBackup policy files

■ backup image files

■ other configuration files

If the EMM server is located on a remote computer, the NBDB database isrecovered on the remote computer.

Disaster recoveryCatalog recovery from an online backup

596

10 The wizard displays the recovery progress.

If the recovery is not successful, consult the log file messages for an indicationof the problem.

11 The final screen announces that the full recovery is complete. Each imagefile is restored to the proper image directory, and the NetBackup relationaldatabases (NBDB and optionally BMRDB) have been restored and recovered.

If this step is part of a server recovery procedure, complete the remainingsteps in the appropriate Server Disk Recovery procedure.

12 NetBackup does not run scheduled backup jobs until NetBackup is stoppedand restarted. Before you restart NetBackup, protect the media that containsany backups that were successfully performed after the catalog backup thatwas used to recover the catalog.

This recovery can include the following:

■ importing the backups from the backup media into the catalog

■ write protecting the media

■ ejecting the media and setting it aside

■ freezing the media

597Disaster recoveryCatalog recovery from an online backup

13 You can manually submit backup jobs before you stop and restart NetBackup.Be aware that if you have not protected the media containing the backupsdone after the catalog backup, the media may be overwritten.

14 Stop and restart NetBackup on all the servers.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

If a remote EMM server is being used, start NetBackup on it before you startNetBackup on the master server.

If you have recovered from removable media, that media is now frozen.

To unfreeze, see the following:

See “Unfreezing online catalog recovery media” on page 624.

Recovering the entire catalog using bprecover -wizardThe bprecover -wizard command is an alternate way to recover an entire catalogthat is backed up using the online catalog backup method. This method does notrequire the NetBackup Administration Console. You must have root(administrative) privileges to perform this procedure.

Note: You must be logged on locally to the master server that is being recovered.

Note: During the catalog recovery process, services may be shut down andrestarted. If NetBackup is configured as a highly available application (cluster orglobal cluster), freeze the cluster before starting the recovery process to preventa failover. Then unfreeze the cluster after the recovery process is complete.

The steps are the same as those in the following topic:

See “Recovering the entire catalog using the Catalog Recovery Wizard” on page 592.

Disaster recoveryCatalog recovery from an online backup

598

To recover the entire catalog using bprecover -wizard

1 Start NetBackup by entering the following:

If your configuration includes an Enterprise Media Manager (EMM) serverthat is separate from the master server, start NetBackup on the EMM serverbefore starting NetBackup on the master server.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpup

2 Run the following command:

bprecover -wizard

The following is displayed:

Welcome to the NetBackup Catalog Recovery Wizard!

Please make sure the devices and media that contain catalog

disaster recovery data are available

Are you ready to continue?(Y/N)

3 Enter Y to continue. The following prompt appears:

Please specify the full pathname to the catalog disaster

recovery file:

4 Enter the fully qualified pathname to the Backup ID file. For example:

C:\DR_INFO\HotCatBack_1120078077_FULL

The following is displayed:

All media resources were located

Do you want to recover the entire NetBackup catalog? (Y/N)

599Disaster recoveryCatalog recovery from an online backup

5 Enter Y to continue. The following is displayed:

Catalog recovery is in progress. Please wait...

Database server restarted, and completed successful recovery of

NBDB on <EMM Server>

Catalog recovery has completed.

Please review the log file C:\Program

Files\VERITAS\NetBackup\Logs

\user_ops\Administrator\logs\Recover1120078220.log for more

information.

The image file is restored to the proper image directory and the NetBackuprelational databases (NBDB and optionally BMRDB) are restored and recovered.

6 NetBackup does not run scheduled backup jobs until NetBackup is stoppedand restarted. Before you restart NetBackup, protect the media that containsbackups that were successfully performed after the catalog backup that wasused to recover the catalog.

This procedure can include the following tasks:

■ importing the backups from the backup media into the catalog

■ write protecting the media

■ ejecting the media and setting it aside

■ freezing the media

7 Stop and restart NetBackup.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

If a remote EMM server is being used, start NetBackup on it before you startNetBackup on the master server.

Recovering the catalog image fileConsider performing this recovery procedure only in the following scenarios:

■ The NetBackup relational database is valid, but NetBackup policy, backupimage, or configuration files are lost.

Disaster recoveryCatalog recovery from an online backup

600

■ You want to restore part of the NetBackup catalog before you restore the entirecatalog. This procedure recovers only the catalog images and configurationfiles.

The catalog backup images contain information about all the data that has beenbacked up. This information constitutes the largest part of the NetBackup catalog.

If the backup images are intact but the NetBackup relational database files arenot, you can still recover these files.

See “Recovering relational database files from an online catalog backup”on page 610.

The wizard restores whatever catalog images and configuration files are in thebackup set identified by the disaster recovery file. If the disaster recovery file isfrom a full backup, all catalog images and configuration files are restored.

For an incremental backup, the wizard restores only catalog images andconfiguration the files that were changed since the previous backup. However,all catalog backup image files back to the last full catalog backup are automaticallyincluded in an incremental catalog backup. This operation allows for the completerestoration of all backup images by the Backup, Archive, and Restore user interface.

For a catalog that was backed up using the online method of NetBackup catalogimage and configuration files, recovery in either of the following ways:

■ Use the Catalog Recovery Wizard

■ Use the bprecover -wizard command

During a manual recovery, the wizard recovers only NetBackup policy files,NetBackup backup image files, and other NetBackup configuration files. It doesnot recover the NBDB (includes EMM) or BMR databases.

If the backup from which you recover is an incremental catalog backup and nocatalog backup images exist in the catalog, the following occurs: only theNetBackup policy, backup image, and configuration files that are backed up inthat incremental backup are restored. However, all of the catalog backup imagesup to the last full catalog backup are restored. So you can restore the rest of thepolicy, images, and configuration files from the Backup, Archive and Restoreinterface. If catalog backup images already exist, all files that were included inthe related set of catalog backups are restored. The NBDB (includes EMM) andBMR (if applicable) databases must then be recovered by running the following:

bprecover -r -nbdb

Table 7-1 is a list of the files that you recover in a manual recovery (an asteriskindicates multiple files within that folder).

601Disaster recoveryCatalog recovery from an online backup

Table 7-1 Files you recover when you recover catalog image files

WindowsUNIX and Linux

install_path\NetBackup\db\*/usr/openv/netbackup/bp.conf

install_path\NetBackup\vault\sessions\*/usr/openv/netbackup/db/*

install_path\NetBackup\var\*/usr/openv/netbackup/vault/

sessions*

install_path\Volmgr\database\*/usr/openv/var/*

install_path\Volmgr\vm.conf/usr/openv/volmgr/database/*

/usr/openv/volmgr/vm.conf

The following is a list of NetBackup relational database (SQL Anywhere) files thatare not recovered in a manual recovery.

NBDB.db

NBDB.log

EMM_DATA.db

EMM_INDEX.db

BMRDB.db

BMRDB.log

BMR_DATA.db

BMR_INDEX.db

vxdbms.conf

DARS_DATA.db

DARS_INDEX.db

DBM_DATA.db

DBM_INDEX.db

■ install_path\NetBackupDB\conf\server.conf (Windows only)

■ install_path\NETBACKUP\DB\conf\databases.conf (Windows only)

You can recover these files.

See “Recovering relational database files from an online catalog backup”on page 610.

Recovering the catalog image files using the Catalog RecoveryWizardYou must have root (administrative) privileges to perform this procedure.

Disaster recoveryCatalog recovery from an online backup

602

Note:The Catalog Recovery wizard does not work after performing a change serveroperation. You must be logged on locally to the master server that is beingrecovered.

To recover the catalog image files

1 Start NetBackup by entering the following:

If your configuration includes an EMM server that is separate from the masterserver, do the following: start NetBackup on the EMM server before startingNetBackup on the master server.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpup

2 Click RecovertheCatalogs in the NetBackup Administration Console to startthe Catalog Recovery Wizard.

Warning: Do not run any client backups before you recover the NetBackupcatalog.

603Disaster recoveryCatalog recovery from an online backup

3 This wizard relies on the disaster recovery information that was generatedduring the online, hot catalog backup. Part of configuring the catalog backupincluded the indication of where the disaster recovery information was to bestored and sent.

Indicate where the disaster recovery file is stored by entering the fullyqualified path to the disaster recovery file.

For example:

/net/lex/Cat_DR/CatBk_1119304246_INCR

Note: Specify the most recent disaster recovery file available, unless there isa reason to restore from an earlier state.

Note whether the disaster recovery file is based on a full (*_FULL) or anincremental (*_INCR) catalog backup.

More information is available on the email that is sent and the attacheddisaster recovery file.

See “Recovering the catalog without the disaster recovery file” on page 615.

Disaster recoveryCatalog recovery from an online backup

604

4 The wizard waits while NetBackup searches for the necessary media sources,then tells you if the necessary backup ID of the DR image was located. If themedia is not located, the wizard lists which media is needed to update thedatabase.

Follow the wizard instructions to insert the indicated media and run aninventory to update the NetBackup database.

5 Click Next to display the DisasterRecoveryMethod dialog. Select the RecoveronlyNetBackupcatalogimageandconfigurationfiles radio option and clickNext.

605Disaster recoveryCatalog recovery from an online backup

6 The wizard displays the recovery progress and announces when the cataloghas been recovered.

If the recovery is not successful, consult the log file messages for an indicationof the problem.

Disaster recoveryCatalog recovery from an online backup

606

7 The final screen indicates that the catalog backup images have been recovered.

You can now recover the NetBackup database if necessary.

8 NetBackup does not run scheduled backup jobs until NetBackup is stoppedand restarted. Before you restart NetBackup, protect the media that containsbackups that were successfully performed after the catalog backup that wasused to recover the catalog.

Media protection may include the following tasks:

■ importing the backups from the backup media into the catalog

■ write protecting the media

■ ejecting the media and setting it aside

607Disaster recoveryCatalog recovery from an online backup

■ freezing the media

9 Stop and restart NetBackup on all the servers.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

If a remote EMM server is being used, start NetBackup on it before you startNetBackup on the master server.

Recovering the catalog image file using bprecover -wizardYou must have root (administrative) privileges to perform this procedure.

To recover the catalog image file using bprecover -wizard

1 Start NetBackup by entering the following:

If your configuration includes an EMM server separate from the master server,start NetBackup on the EMM server before starting NetBackup on the masterserver.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpup

2 Run the following command:

bprecover -wizard

The following is displayed:

Welcome to the NetBackup Catalog Recovery Wizard!

Please make sure the devices and media that contain catalog

disaster recovery data are available

Are you ready to continue?(Y/N)

Disaster recoveryCatalog recovery from an online backup

608

3 Enter Y to continue. The following prompt appears:

Please specify the full pathname to the catalog disaster

recovery file:

4 Enter the pathname to the Backup ID file. For example:

C:\DR_INFO\HotCatBack_1120078077_FULL

The following is displayed:

All media resources were located

Do you want to recover the entire NetBackup catalog? (Y/N)

5 Enter N to continue. The following is displayed:

Catalog recovery is in progress. Please wait...

This portion of the catalog recovery has completed.

Because this operation is a partial recovery, any remaining portions of thecatalog must be restored using Backup, Archive, and Restore.

Please review the following log file for more information

C:\Program Files\VERITAS\NetBackup\Logs\user_ops\

Administrator\logs\Recover1123008613.log

You can now recover the NetBackup database if necessary.

6 NetBackup does not run scheduled backup jobs until NetBackup is stoppedand restarted. Before you restart NetBackup, protect the media that containsbackups that were successfully performed after the catalog backup that wasused to recover the catalog.

This media protection may include the following tasks:

■ importing the backups from the backup media into the catalog

■ write protecting the media

■ ejecting the media and setting it aside

609Disaster recoveryCatalog recovery from an online backup

■ freezing the media

7 Stop and restart NetBackup on all the servers.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

On Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

If a remote EMM server is being used, start NetBackup on it before you startNetBackup on the master server.

Recovering relational database files from an online catalog backupIf the NetBackup (NBDB) or Bare Metal Restore (BMRDB) relational database filesneed to be recovered, perform this procedure.

The full procedure is necessary only if the NBDB database has been corrupted. Atemporary database must be created to restore from the catalog backup. If theNBDB database is available and the SQL Anywhere server is running, then do thefollowing: perform only steps 11 and 12 to replace the existing database with thecopy from the catalog backup.

Note: If your configuration includes a remote EMM server, perform steps 1 through7 on the EMM server.

Disaster recoveryCatalog recovery from an online backup

610

To recover relational database files from an online catalog backup

1 If NetBackup is running, stop it.

On UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

On Windows:

install_path\NetBackup\bin\bpdown

2 Move the following set of existing database files from their current locationto a temporary directory.

NBDB:

nbdb.db, nbdb.log, emm_index.db, emm_data.db

BMRDB:

bmrdb.db, bmrdb.log

3 Change databases.conf so SQL Anywhere does not try to automatically startthem when the server is started.

On UNIX and Linux:

/usr/openv/db/bin/nbdb_admin -auto_start NONE

On Windows:

install_path\NetBackup\bin\nbdb_admin -auto_start NONE

4 Start the SQL Anywhere server.

UNIX and Linux:

/usr/openv/netbackup/bin/nbdbms_start_stop start

Windows:

install_path\NetBackup\bin\bpup -e SQLANYs_VERITAS_NB

611Disaster recoveryCatalog recovery from an online backup

5 Re-create an empty database.

UNIX and Linux:

/usr/openv/db/bin/create_nbdb -drop

Windows:

install_path\NetBackup\bin\create_nbdb -drop

If the database has been moved or the environment is clustered, add -staging

staging_dir to the end of the create_nbdb command line.

If the database has been moved or the environment is clustered, and spaceconstraints or other issues force you to create this temporary database in thefinal location, use the following command:

UNIX and Linux:

/usr/openv/db/bin/create_nbdb -drop -data <data_dir> -index \

<index_dir> -tlog <tlog_dir> -staging <staging_dir>

Windows:

install_path\NetBackup\bin\create_nbdb -drop -data <data_dir>

-index <index_dir> -tlog <tlog_dir> -staging <staging_dir>

Where the <data_dir>, <index_dir>, <tlog_dir>, and <staging_dir> values aredefined in the vxdbms.conf file as VXDBMS_NB_DATA, VXDBMS_NB_INDEX,VXDBMS_NB_TLOG, and VXDBMS_NB_STAGING.

6 Stop and restart NetBackup.

UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

Disaster recoveryCatalog recovery from an online backup

612

7 Run tpext:

UNIX and Linux:

/usr/openv/volmgr/bin/tpext

Windows:

install_path\Volmgr\bin\tpext

8 If you used the nbdb_move command to relocate NetBackup database files,re-create the directories where the files were located when you backed up thecatalog. The default location is the following:

UNIX and Linux:

/usr/openv/db/data

Windows:

install_path\NetBackupDB\data

9 Start the device manager:

UNIX and Linux:

/usr/openv/volmgr/bin/ltid -v

Windows: start the device manager service.

10 Configure the necessary recovery device in NetBackup.

11 Make available to NetBackup the media that contains the catalog backup.Inventory the robot or add the media for stand-alone drives.

613Disaster recoveryCatalog recovery from an online backup

12 For online catalog recovery, run the following command on the master server:

UNIX and Linux:

/usr/openv/netbackup/bin/admincmd/bprecover -r -nbdb

Windows: start the device manager service.

install_path\NetBackup\bin\admincmd\bprecover -r -nbdb

13 Stop and restart NetBackup.

UNIX and Linux:

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

Windows:

install_path\NetBackup\bin\bpdown

install_path\NetBackup\bin\bpup

If a remote EMM server is being used, start NetBackup on it before you startNetBackup on the master server.

Recovering NetBackup access management components from a hotbackup

If you have configured NetBackup Access Control (NBAC), the online, hot catalogbackup automatically backs up your authentication and authorizationconfiguration information.

Both the Operate and Configure permission sets are required on the catalog objectto successfully back up and recover NBAC authentication and authorization data.

To recover the NetBackup catalog from an online catalog backup when NetBackupAccess Control is configured

1 Follow the normal NetBackup catalog recovery procedures. Ensure thatNetBackup Access Management Control is installed but disabled before yourun the actual catalog recovery wizard or bprecover command. You musthave root privileges to execute the recovery.

2 Turn off the authentication and authorization services (Windows) or daemons(UNIX and Linux).

Disaster recoveryCatalog recovery from an online backup

614

3 Recover the NetBackup catalog from the online catalog backup using therecovery wizard or bprecover command. Authentication and authorizationdata is not copied back to the hosts from which it was backed up. Instead, itis copied to a staging area for use in step 4.

4 Run "bprecover -r -vxss -p <policy name>" and supply the name of theonline catalog backup policy. This action recovers authentication andauthorization data from the staging area to the hosts from which it was backedup.

5 Start up the authentication and authorization services (Windows) or daemons(UNIX and Linux).

6 Configure NetBackup to use NetBackup Access Management Control by settingup the proper Access Control host properties for master server(s), mediaserver(s), and client(s).

7 Restart NetBackup.

Recovering the catalog using a copy of an online catalog backupThe online, hot catalog backup can create multiple copies of the catalog backupin either of two ways: by specifying multiple copies when the backup is originallydone or by duplicating the catalog backup later.

To recover the catalog from a copy, see the following:

See “Recovering the catalog without the disaster recovery file” on page 615.

Recovering the catalog without the disaster recovery fileIf the disaster recovery file has been lost, consult the email that was sent to theadministrator when the catalog was backed up. The Disaster Recovery file iswritten to the location you specify in the catalog backup policy and is appendedto the backup stream itself.

To recover the catalog from an online catalog backup when you no longer have theDisaster Recovery file

1 The email identifies the media that contains the Disaster Recovery file, aswell as the media that was used to back up critical policies. Ensure that thismedia is available.

2 Follow the normal catalog recovery steps up until the point where theNetBackup Recovery Wizard or bprecover command is called for.

615Disaster recoveryCatalog recovery from an online backup

3 Run the following command to retrieve all Disaster Recovery files from thecatalog backup media:

bpimport -drfile media_id -drfile_dest

fully_qualified_directory_name

This command recovers all disaster recovery files from the specified mediaID and places them in the specified directory. The ID can be either a tapemedia ID or the fully qualified location of a disk storage unit.

Disaster recoveryCatalog recovery from an online backup

616

4 Verify that the correct Disaster Recovery file is available in the specifieddirectory and that the directory is available from the NetBackup masterserver.

617Disaster recoveryCatalog recovery from an online backup

5 Continue with the normal catalog recovery procedure by running theNetBackup Recovery Wizard or bprecover command, providing the DisasterRecovery file location when prompted.

Refer to the email as your primary source for recovery instructions, becausethey are the most current instructions for recovering your catalog. Theinstructions are sent when the catalog backup is completed, or when a catalogbackup image is duplicated.

Note: If you restore catalog files directly using bprestore on a Solaris system,use the following path: /opt/openv/netbackup/bin/bprestore.

The name of the online catalog backup policy is CatalogBackup. The email iswritten to the following file:

/storage/DR/CatalogBackup_1123605764_FULL.

The file name itself indicates if the backup was full or not.

The following is an example of a Disaster Recovery email:

Server

ant

Date

Tue Aug 9 11:41:48 2005

Policy

CatalogBackup

Catalog Backup Status

the requested operation was successfully completed (status 0).

To ensure that the NetBackup catalog data is protected through Tue

Aug 9 11:41:48 2005, retain a copy of the attached file, and the

media or files listed below:

Catalog Recovery Media

Media Server Disk image path

* ant /storage/DiskUnit1/ant_1123605764_C1_TIR

* ant /storage/DiskUnit1/ant_1123605764_C1_F1

* ant /storage/DiskUnit1/ant_1123605713_C1_F1

DR file written to

/storage/DR/CatalogBackup_1123605764_FULL

Disaster recoveryCatalog recovery from an online backup

618

* - Primary Media

Catalog Recovery Procedure for the Loss of an Entire Catalog

Symantec recommends creating a detailed disaster recovery plan

should it become necessary to restore your organization's data in

the event of a disaster. A checklist of required tasks can be a

tremendous tool in assisting associates in triage. For example,

after the facility is safe for data to be restored, the power and

data infrastructure need to be verified. When these tasks are

completed, the following scenarios will help to quickly restore the

NetBackup environment, and in turn, restore applications and data.

Disaster Recovery Procedure using the DR Image File

In the event of a catastrophic failure, use the following procedure

to rebuild the previous NetBackup environment.

Note: If new hardware is required, make sure that the devices contain

drives

capable of reading the media and that the drive controllers are

capable of mounting the drives.

1. Install NetBackup.

2. Configure the devices necessary to read the media listed

above.

3. Inventory the media.

4. Make sure that the master server can access the attached DR

image file.

Start the NetBackup Recovery Wizard from the NetBackup

Administration

Console. Or, start the wizard from a command line by entering

bprecover -wizard.

Disaster Recovery Procedure without the DR Image File

NOTE: ONLY ATTEMPT THIS AS A LAST RESORT If you do not have the

attachment included with this email, use the following instructions

to recover your catalog:

1. Install NetBackup.

2. Configure the devices necessary to read the media listed

above.

619Disaster recoveryCatalog recovery from an online backup

3. Inventory the media.

4. Run:

bpimport -create_db_info [-server name] -id

/storage/DiskUnit1

5. Go to the following directory to find the DR image file

CatalogBackup_1123605764_FULL:

/usr/openv/netbackup/db/images/ant/1123000000/tmp

6. Delete the other files in the directory.

7. Open CatalogBackup_1123605764_FULL file and find the

BACKUP_ID

(for example: ant_1123605764).

8. Run:

bpimport [-server name] -backupid ant_1123605764

9. Run:

bprestore -T -w [-L progress_log] -C ant -t 35 -p

CatalogBackup -X -s 1123605764 -e 1123605764 /

10. Run the BAR user interface to restore the remaining image

database

if the DR image is a result of an incremental backup.

11. To recover the NetBackup relational database, run:

bprecover -r -nbdb

12. Stop and Start NetBackup

13. Configure the devices if any device has changed since the

last

backup.

14. To make sure the volume information is updated, inventory

the media

to update the NetBackup database.

Recovering the user-directed online catalog from the CLIThis procedure recovers the catalog manually through the command line interface(CLI) without a Phase 1 import when the Disaster Recovery (DR) file is available.You must have root (administrative) privileges to perform this procedure.

Note:Use this procedure only if you want to restore the minimal NetBackup cataloginformation that lets you begin to recover critical data.

Disaster recoveryCatalog recovery from an online backup

620

To recover the online catalog from the command line interface

1 Verify the location of the Disaster Recovery files that are created from Fulland Incremental Hot Catalog backups. These files can be stored in a specifiedpath of the file system on the master server and in email attachments to theNetBackup administrator.

2 Set up each master server and media server in the same configuration as theconfiguration used during the last catalog backup. The master server andmedia servers have the following same properties as the backed up catalogconfiguration: name, NetBackup version, operating system patch level, andpath to storage devices.

Configure any devices and volumes you may need for the recovery.

3 Locate the latest DR image file corresponding to the backup that are used forrecovery. Open the file in an editor and find values for the following:

■ master_server –use the exact name that is specified in NetBackupconfiguration for the Master Server

■ media_server –the location of the robot or disk storage unit that is usedfor catalog backup.

■ timestamp –the four most significant digits in the DR filename and sixzeroes attached.

■ media –the media where the catalog backup that is specified by the DRfile is located. Found in the DR file under the FRAGMENT keyword.

■ backup_id –found in the DR file under BACKUP_ID.

Example:

file: Hot_Backup_1122502016_INCR

timestamp: 1122000000

4 Create the DR recovery directory on the master server.

UNIX and Linux:

/usr/openv/netbackup/db/images/master_server/timestamp/tmp

Windows:

C:\Program Files\VERITAS\NetBackup\db\images\master_server

\timestamp\tmp

Copy the DR file to the newly created directory.

5 Edit the DR file in netbackup/db/images/master_server/timestamp/tmp

as follows:

621Disaster recoveryCatalog recovery from an online backup

■ Change the value of IMAGE_TYPE to 1

■ Change the value of TIR_INFO to 0

■ Change the value of NUM_DR_MEDIAS to 0

■ Remove ALL lines containing DR_MEDIA_REC

6 If your catalog recover media is on tape, run the vmquery command to assignthe media to the media server.

vmquery -assigntohost media timestamp master_server

Example:

vmquery -assigntohost DL005L 1122000000 klingon

7 Run a Phase II import on the media that is specified by the DR file to recoverthe catalog .f file from the hot catalog backup.

bpimport -server master_server -backupid backup_id

8 If your catalog backup was an incremental, recover all the other catalogbackup images up to and including the most recent Full Catalog backup.

■ Open the Backup, Archive, and Restore client interface for NetBackup.Select NBU-Catalog as the policy type. Set the source clients anddestination clients to your master server.

■ Search the backups and restore all files that are located in the followingdirectory:

install_path/netbackup/db/images/master_server

■ Verify that all files are restored successfully on the master server.

9 Restore your critical data by using the Backup, Archive, and Restore clientinterface or the command line.

■ Restore the catalog backup images for each media server which requiresdata recovery.

■ To restore the backup images, select NBU-Catalog as the policy type.Source and destination clients should be your master server. Refresh yourview in the BAR GUI. Traverse the file system for the master server to thefollowing:

install_path/netbackup/db/images

Disaster recoveryCatalog recovery from an online backup

622

and restore the images for each configured media server. Verify that yourimages are present by searching for them in the catalog.

10 Recover backup data from each media server in the previous step. Changethe Policy Type, Source, and Destination client to match the client that isused to back up the desired data. Select the desired files from the Backup,Archive, and Restore client interface and restore them.

11 To recover the NetBackup relational database, run the following:

bprecover -r -nbdb

This command restores NetBackup media usage information, ensure thatmedia containing backups are not overwritten, and restore the storage unitconfiguration.

You cannot recover the NetBackup relational database to a configuration thatis not identical to the configuration on which the catalog was backed up.Instead, you must import each piece of backup media.

12 If your catalog recovery media is on tape, freeze the media that contains thecatalog backup that is used for recovery. This action protects the media frombeing reused:

bpmedia -freeze -m media -h master_server

Run bpmedialist to verify that the media is frozen.

13 Recover your policies and configuration data on each master server and mediaserver.

Before recovering NetBackup policy files, ensure that you have recovered allof your critical data, or protected the media that contains your critical data.When policy information is recovered, NetBackup starts to run scheduledjobs that may overwrite media that was written after the last catalog backup.

Open the Backup, Archive, and Restore client interface for NetBackup andselect NBU-Catalog as the policy type.

For each server to be restored, set the source clients and destination clientsto your server, starting with the master server.

Restore all files that are backed up by the hot catalog backup on each server.

14 Stop and restart the NetBackup services.

Restoring files from an online catalog backupBecause the online catalog backup uses the standard backup format, you mayrecover specific files using the NetBackup Backup, Archive, and Restore user

623Disaster recoveryCatalog recovery from an online backup

interface. Restoring catalog files directly to their original location may causeinconsistencies in the NetBackup catalog or cause NetBackup to fail. Instead, youshould restore catalog files to an alternate location.

■ Select the "NBU-Catalog" policy type (from the SpecifyNetBackupMachinesand Policy Type menu).

■ Specify the Master Server as the source client for the restore.

Unfreezing online catalog recovery mediaThis procedure shows how to unfreeze your online catalog recovery media.

To unfreeze the online catalog recovery media, do the following:

1 On the master server, go to the image database. In the master server's portionof the image catalog, locate the catalog backup image file from which therecovery was done.

■ Identify the associated catalog backup parent image file by viewing thePARENT_IMAGE_ID value.

■ Identify the media that the catalog backup was written to by viewing thesecond to last field in the DR_MEDIA_REC line(s).

■ Save the catalog backup parent image file identified in step a.

■ Relocate or remove all other image files that relates to the catalog backuppolicy.

2 If the NetBackup configuration includes a remote EMM server, on the masterserver, go to the image database for the remote EMM server. Relocate orremove any images that relates to the catalog backup policy.

3 On the master server, for each media that is identified in step 1b, run thefollowing command:

bpimport -create_db_info -server server_name -id media_id

4 On the master server, run the following command:

bpimport

5 On the master server, for each media that is identified in step 1b, run thefollowing command:

bpmedia -unfreeze -m media_id -h server_name

Disaster recoveryCatalog recovery from an online backup

624

Clustered NBU server recovery for UNIX and LinuxNetBackup server clusters do not protect against catalog corruption, loss of theshared disk, or loss of the whole cluster. Regular catalog backups must beperformed. More information is available about configuring catalog backups andsystem backup policies in a clustered environment.

Refer to "Configuring NetBackup" in the NetBackup High Availability Guide.

Warning: Before attempting any of the recovery procedures in this topic, contacttechnical support.

Replacing a failed node on a UNIX or Linux clusterCluster technology-specific information is available about how to bring theNetBackup resource group online and offline. Also, information about how tofreeze and unfreeze (that is, disable and enable monitoring for) the NetBackupResource group.

Refer to "Configuring NetBackup" in the NetBackup High Availability Guide.

The following procedure applies when the shared disk and at least one configuredcluster node remain available.

To replace a failed node on a UNIX or Linux cluster

1 Configure the hardware, system software, and cluster environment on thereplacement node.

2 Verify that the device configuration matches that of the surviving nodes.

3 Ensure that the NetBackup Resource group is offline on all nodes beforeinstalling NetBackup on the replacement node.

4 Ensure that the NetBackup shared disks are not mounted on the node onwhich NetBackup is to be installed.

5 Freeze the NetBackup service.

6 Reinstall NetBackup on the new or replacement node. Be sure to use theNetBackup Virtual Name as the name of the NetBackup server. Follow theinstructions for installing the NetBackup Server software.

Refer to the NetBackup Installation Guide.

7 Install any maintenance packs and patches required to bring the newlyinstalled node to the same patch level as the other cluster nodes.

8 Bring the NetBackup Resource group online on a node other than the freshlyinstalled node.

625Disaster recoveryClustered NBU server recovery for UNIX and Linux

9 Log onto the node on which the NetBackup resource group is online and runthe following command:

/usr/openv/netbackup/bin/cluster/cluster_config -s nbu -o

add_node -n node_name

node_name is the name of the freshly installed node.

10 Switch the NetBackup resource group to the replacement node.

11 Freeze the NetBackup group.

12 Ensure that the appropriate low-level tape device and robotic control deviceconfiguration necessary for your operating system has been performed.Information is available for the your operating system.

Refer to the NetBackup Device Configuration Guide.

13 Run the Device Configuration wizard to configure the devices. You do nothave to rerun the device configuration on the pre-existing nodes.Configuration information on your particular cluster is available.

Refer to the NetBackup High Availability Guide.

14 Check that the robot numbers and robot drive numbers for each robot areconsistent across all nodes of the cluster. Repeat for any other serversconnected to that robot, and correct if necessary.

Refer to the "Media" section of theNetBackupAdministrator’sGuide ,Volume1.

15 Test the ability of NetBackup to perform restores using the configured deviceson the replacement node.

16 Unfreeze the NetBackup resource group.

Recovering the shared disk on a UNIX or Linux clusterThe following procedure is applicable in situations where the configured clusternodes remain available but the NetBackup catalog, the database files, or both onthe shared disk have been corrupted or lost.

The following conditions must be true to proceed with this procedure:

■ The shared storage hardware is restored to a working state, so that the shareddisk resource can be brought online with an empty shared directory.

■ Valid online catalog backups exist.

Disaster recoveryClustered NBU server recovery for UNIX and Linux

626

To recover the shared disk on a UNIX or Linux cluster

1 Clear the faulted NetBackup resource group, disable monitoring and bringthe shared disk and virtual name resources up on a functioning node.

2 Manually create the following directories on the shared disk:

<shared disk path>/netbackup/db

<shared disk path>/db/data

<shared disk path>/var/global

<shared disk path>/volmgr/misc/robotic_db

3 If this is an emm server, enter the following to bring up the database serverand emm, then run tpext to initialize the emm db:

# SHARED_DISK=<top-level shared disk mount point>

# dataDir=${SHARED_DISK}/db/data

# /usr/openv/netbackup/bin/nbdbms_start_stop start

/usr/openv/db/bin/create_nbdb \

-data ${dataDir} \

-index ${dataDir} \

-tlog ${dataDir} \

-mlog ${dataDir} \

-staging ${dataDir}/staging \

-drop

# /usr/openv/volmgr/bin/tpext -loadEMM

4 Configure required devices and media and recover the NetBackup catalogs.

See “Recovering the master server when root is intact” on page 576.

5 Manually shut down and restart NetBackup on the active node.

6 Re-enable monitoring of the NetBackup resource group.

7 Verify that the NetBackup server can now be brought online on all configurednodes.

Recovering the entire UNIX or Linux clusterThe following procedure applies to the clustered NetBackup server environmentthat must be re-created from scratch.

Before you proceed, ensure that you have valid online catalog backups.

627Disaster recoveryClustered NBU server recovery for UNIX and Linux

To recover the entire UNIX or Linux cluster

1 Configure the hardware, system software and cluster environment on thereplacement cluster.

2 Ensure that the appropriate low-level tape device and robotic control deviceconfiguration necessary for your operating system has been performed.

Refer to the NetBackup Device Configuration Guide.

3 Reinstall NetBackup on the each of the cluster nodes. Be sure to use theNetBackup Virtual Name as the name of the NetBackup server. Follow theinstructions for installing NetBackup Server software.

Refer to the NetBackup Installation Guide.

4 Configure the clustered NetBackup server.

Refer to the NetBackup High Availability Guide.

5 Install any maintenance packs and patches required to bring the newlyinstalled NetBackup server to the same patch level as the server that is beingreplaced.

6 Configure required devices and media and recover the NetBackup catalogs.

See “Recovering the master server when root is intact” on page 576.

7 Bring the NetBackup resource group on each node in turn and run the Deviceconfiguration wizard to configure the devices.

Configuration information on your particular cluster is available.

Refer to the NetBackup High Availability Guide.

Clustered NBU server recovery for WindowsNetBackup server clusters do not protect against catalog corruption, loss of theshared disk, or loss of the whole cluster. Regular catalog backups must beperformed. More information is available about configuring catalog backups andsystem backup policies in a clustered environment.

Refer to "Configuring NetBackup" in the NetBackup High Availability Guide.

Warning: Contact technical support before you try these recovery procedures.

Disaster recoveryClustered NBU server recovery for Windows

628

Replacing a failed node on a Windows VCS clusterCluster technology-specific information is available about how to bring theNetBackup resource group online and offline. Also, it is available on how to freezeand unfreeze (disable and enable the monitoring for) the resource group.

See "Configuring NetBackup" in the NetBackup High Availability Guide.

Check the following conditions before you proceed with this procedure:

■ The hardware, system software and cluster environment on the replacementnode have been configured.

■ The reconfigured or replacement node has been made a member of the clusterand has the same name as the failed node.

The following procedure applies when the shared disk and at least one configuredcluster node remain available.

To replace a failed node on a Windows cluster using VCS

1 Freeze the NetBackup service.

2 Ensure that the NetBackup shared disks are not mounted on the node onwhich NetBackup is to be installed.

3 Reinstall NetBackup on the new or replacement node. Be sure to use theNetBackup Virtual Name as the name of the NetBackup server. Follow theinstructions for installing the NetBackup Server software.

Refer to the NetBackup Installation Guide.

4 Ensure that the node is a member of an existing cluster and that it performsthe necessary configuration automatically.

5 Install any maintenance packs and patches required to bring the newlyinstalled node to the same patch level as the other cluster nodes.

6 Unfreeze the NetBackup service and verify that it can be brought up on thereplacement node.

Recovering the shared disk on a Windows VCS clusterThe following procedure is applicable in situations where the configured clusternodes remain available but the NetBackup catalog, database files, or both on theshared disk have been corrupted or lost.

Check the following conditions before you proceed with this procedure:

■ The shared storage hardware is restored to a working state, so that the shareddisk resource can be brought online with an empty shared directory.

■ Valid online catalog backups exist.

629Disaster recoveryClustered NBU server recovery for Windows

To recover the shared disk on a Windows cluster that uses VCS

1 Clear the faulted NetBackup resource group, disable monitoring, and bringthe shared disk and virtual name resources up on a functioning node.

2 Ensure that all NetBackup shared disks are assigned the same drive lettersthat were used when NetBackup was originally installed and configured.

3 To reconfigure NetBackup for the cluster, initialize the database by runningthe following commands in sequence on the active node:

bpclusterutil -ci

tpext

bpclusterutil -online

4 Use the appropriate NetBackup catalog recovery procedure to restore theNetBackup catalog information on the shared disk.

See “Recovering the master server and Windows” on page 585.

5 If the clustered NetBackup server is a media server, verify that the restoredvm.conf file contains the correct host-specific MM_SERVER_NAMEconfiguration entry for the active node. If MM_SERVER_NAME is differentfrom the local host name, edit the file and change the server name to the localhost name:

MM_SERVER_NAME=<local host name>

6 Use NetBackup to restore any data on the shared disks. Details are availableon how to perform a restore.

Refer to the NetBackup Backup, Archive, and Restore Getting Started Guide.

7 Configure required devices and media and recover the NetBackup catalogs.

8 Manually shut down and restart NetBackup on the active node.

9 Re-enable monitoring of the NetBackup resource group.

10 Verify that the NetBackup server can now be brought online on all configurednodes.

Recovering the entire Windows VCS clusterThe following procedure applies to the clustered NetBackup server environmentthat must be re-created from scratch.

Before you proceed, ensure that you have valid online catalog backups.

Disaster recoveryClustered NBU server recovery for Windows

630

To recover the entire UNIX or Linux cluster

1 Configure the hardware, system software and cluster environment on thereplacement cluster.

2 Ensure that the appropriate low-level tape device and robotic control deviceconfiguration necessary for your operating system has been performed.

Refer to the NetBackup Device Configuration Guide.

3 Reinstall NetBackup on the each of the cluster nodes. Be sure to use theNetBackup Virtual Name as the name of the NetBackup server. Follow theinstructions for installing NetBackup Server software.

Refer to the NetBackup Installation Guide.

4 Configure the clustered NetBackup server.

Refer to the NetBackup High Availability Guide.

5 Install any maintenance packs and patches required to bring the newlyinstalled NetBackup server to the same patch level as the server that is beingreplaced.

6 Configure required devices and media and recover the NetBackup catalogs.

See “Recovering the master server and Windows” on page 585.

7 Bring the NetBackup resource group on each node in turn and run the Deviceconfiguration wizard to configure the devices.

Configuration information on your cluster (MSCS or VCS) is available.

Refer to the NetBackup High Availability Guide.

631Disaster recoveryClustered NBU server recovery for Windows

Disaster recoveryClustered NBU server recovery for Windows

632

Backup and restorefunctional overview

This appendix includes the following topics:

■ About backup and restore functional overview

■ Backup and restore startup process

■ Backup and archive processes

■ Backups and archives - UNIX clients

■ Restore processes

■ NetBackup directories and files

■ NetBackup programs and daemons

■ NetBackup catalogs

About backup and restore functional overviewThis appendix provides a functional overview of NetBackup backup and restoreoperations for both UNIX and Windows. This section explains the operation ofNetBackup during . The discussions include descriptions of important services ordaemons and programs, and the sequence in which they execute during backupand restore operations. The databases and the directory structure of the installedsoftware are also described.

Note that this appendix does not describe the NetBackup products for backing uprelational databases (such as NetBackup for ORACLE). The guides for thoseproducts have information regarding their operation.

AAppendix

Backup and restore startup processWhen the NetBackup master server starts up, a script automatically starts allservices, daemons, and programs that are required by NetBackup. (The start-upcommands that are used by the script vary according to the platform.)

The same is true on a media server. NetBackup automatically starts additionalprograms as required, including robotic daemons. For more information, see thefollowing topic:

Information is available on SAN client and Fibre Transport startup processes.

See the NetBackup Shared Storage Guide.

Note: No daemons or programs need to be explicitly started. The necessaryprograms are started automatically during the backup or restore operation.

A daemon that executes on all servers and clients is the NetBackup client daemon,bpcd. On UNIX clients, inetd starts bpcd automatically so no special actions arerequired. On Windows clients, bpinetd performs the same functions as inetd.Netware clients do not use inetd or bpinetd but are configured to start the bpcdNLM (bpcd.nlm) automatically. An NLM is similar to a service; NLM stands forNetWare Loadable Module.

Note that all NetBackup processes can be started manually by running thefollowing:

/usr/openv/netbackup/bin/bp.start_all

Backup and archive processesThe backup processes and archive processes vary depending on the type of client.The following explains the variations and describes the synthetic backup process.A description is included about how NetBackup operates when backing up itscatalogs.

Job schedulingThe scheduler process bpsched consists of the following services:

■ The nbpem service (Policy Execution Manager) does the following: createspolicy/client tasks and determines when jobs are due to run. It starts the joband upon job completion, determines when the next job should run for thepolicy-client combination.

Backup and restore functional overviewBackup and restore startup process

634

■ The nbjm service (Job Manager) accepts requests from nbpem to run backupjobs, or to run media jobs from commands such as bplabel and tpreq. nbjmacquires resources for each job, such as storage unit, drives, media, and clientand policy resources, and executes the job.

■ The nbrb service (Resource Broker) allocates resources in response to requestsfrom nbjm. nbrb acquires physical resources from nbemm (the EnterpriseMedia Manager service). It also manages logical resources such as multiplexgroups, maximum jobs per client, and maximum jobs per policy. nbrb is alsoresponsible for initiating drive unloads and manages pending request queues.

EMM server and master serverThe NetBackup master server and the Enterprise Media Manager (EMM) servercan be on the same physical host or on different hosts.

The master server is responsible for running jobs as configured in NetBackuppolicies. The nbpem and nbjm services run only on the master server.

The EMM server allocates resources for one or more master servers. The EMMserver is the repository for all device configuration information. The nbemm serviceand the nbrb service run only on the EMM server. The nbemm service centralizesresource selection and maintains devices, media, and storage units in a relationaldatabase.

Backups and archives - UNIX clientsFor UNIX clients, NetBackup supports scheduled, immediate manual, anduser-directed backups of both files and raw partitions. User-directed archives offiles are also supported (you cannot archive raw partitions). When the operationsstart, they are all similar to the extent that the same daemons and programsexecute on the server.

Each type of backup is started differently as follows:

■ Scheduled backups begin when the nbpem service detects that a job is due.nbpem checks the policy configurations for the scheduled client backups thatare due.

■ Immediate manual backups begin if the administrator chooses this option inthe NetBackup Administration Console or runs the bpbackup command withthe –i option. This action causes bprd to contact nbpem, which then processesthe policy, client, and schedule that are selected by the administrator.

■ User-directed backups or archives begin when a user on a client starts a backupor archive through the user interface on the client. The user can also enter

635Backup and restore functional overviewBackups and archives - UNIX clients

the bpbackup or bparchive commands on the command line. This actioninvokes the client’s bpbackup or bparchive program, which sends a requestto the request daemon bprd on the master server. When bprd receives the userrequest, it contactsnbpem, which checks the policy configurations for schedules.By default nbpem chooses the first user-directed schedule that it finds in apolicy that includes the requesting client.For user-directed backups or archives, it is also possible to specify a policy andschedule. A description is available of the UNIX BPBACKUP_POLICY andBPBACKUP_SCHED options in bp.conf and the Windows equivalents.

See the NetBackup Administrator’s Guide, Volume I I.

Backup processThis topic uses a diagram and a table to describe each step of a backup process.PBX (not shown in the diagram) must be running for NetBackup to operate.

See “Resolving PBX problems” on page 67.

Figure A-1 illustrates the various operations that comprise the backup process.

Backup and restore functional overviewBackups and archives - UNIX clients

636

Figure A-1 Backup or archive to tape or disk

Notes:

.

UNIX client

NetBackupuser interface

Commandline

Bpbackup orbparchive

ConfigurationDatabase

nbrmms

nbpem

nbemm nbrb

nbproxy

nbproxy

FileDatabase

EMMDatabase

Diskvolume

Client disk

nbjm

bpcd

bpbrm

bprd

NetBackupPolicy

Management

bpcd

ltid*

Catalog Info

Catalog Info

Backup Image

Backup

Image

MountMount

Taperequest

Mount

reques

t

Master or media server

Master server

bpbkar

bptm(parent)

bptm(child)**

SharedmemoryBackup Image

Tape

bpdbm

* For details on these components, see the Media and Device Management FunctionalDescription later in this chapter. Itid is for tape backup only

** If the media server is backing up itself (server and client on same host), there is nobptm child: bpbkar sends the data directly to shared memory.

Table A-1 shows the sequence of operation of a backup process.

Table A-1 Backup to tape or disk sequence of operation

ActionAgent

Launches bprd on the master server and ltid on the masterserver and all media servers.

All other daemons and programs are started as necessary includingnbpem, nbjm, nbrb, and nbemm.

Start-up script

637Backup and restore functional overviewBackups and archives - UNIX clients

Table A-1 Backup to tape or disk sequence of operation (continued)

ActionAgent

Gets the policy list from bpdbm.

Creates a policy-client task for all policy-client combinationsspecified in the policy list.

Computes the due time for each policy-client task (policy priorityis honored for internal processing).

Submits to nbjm all jobs as policy-client tasks become due.

When a job finishes, it recomputes the due time of thatpolicy-client task.

Policy executionmanager service(nbpem)

Issues a single request (with a request ID) tonbrb, for all resourcesthat are required by a job. nbrb gets the storage unit, tape drive,and media id information from nbemm and allocates client andpolicy resources. nbrb returns to nbjm an allocation sequencethat contains one allocation for each resource (each allocationcontains a unique ID).

nbrb also returns allocation data for the specific resource type.nbrb also returns the request ID along with the allocations sothat nbjm can correlate the response with the right request (andjob).

Note that nbrb allocates all resources that are included in arequest. If the resources are temporarily unavailable the requestis queued in nbrb. If the resource cannot be allocated, nbrb failsthe request.

nbjm starts the backup by using the client daemon bpcd to startthe backup and restore manager bpbrm.

For normal backup (not snapshots), nbjm starts bpbrm on themedia server, which may or may not be the same system as themaster server.

Job manager service(nbjm)

Starts bptm.

Starts the actual backup (or archive) by using the client daemonbpcd to start the backup program and archive program bpbkar

on the client.

Backup and restoremanager (bpbrm)

Backup and restore functional overviewBackups and archives - UNIX clients

638

Table A-1 Backup to tape or disk sequence of operation (continued)

ActionAgent

Sends the information about files within the image to bpbrm,which directs the file information to the NetBackup file database.The information is sent by means of bpdbm on the master server.

Transmits the backup image to bptm depending on one of thefollowing: whether the media server backs up itself (bptm andbpbkar are on the same host) or back ups a client that resides ona different host.

If the media server backs up itself, bpbkar stores the imageblock-by-block in shared memory on the media server.

If the media server backs up a client on a different host, the bptmprocess on the server creates a child process of itself. The childreceives the image from the client by means of socketcommunications and then stores the image block-by-block inshared memory on the server.

Use the NOSHM file to force a media server that backs up itselfto do the following: create a child process and use socketcommunications, as though the client is on a different host.

More information on the NOSHM file is available.

See the NetBackup Backup Planning and Performance TuningGuide.

Backup and archivemanager (bpbkar)

639Backup and restore functional overviewBackups and archives - UNIX clients

Table A-1 Backup to tape or disk sequence of operation (continued)

ActionAgent

The bptm process or bpdm process on the server takes the imagefrom shared memory and directs it to the storage media.

If the storage media is tape, bptm requests information for thefirst media and drive to use, by exchanging information withnbjm.

bptm sends mount requests for specific media and drives to theNetBackup Device Manager (ltid). This action causes the mediato be mounted on the appropriate devices.

If, during the backup, a tape span is required, bptm againexchanges information with nbjm to release the correct tape andto get another one. nbjm exchanges information with nbrb toaccomplish this function.

For SharedDisk, AdvancedDisk, and OpenStorage, bptm requeststhe volume from nbjm. nbjm then passes the request to nbemm tochoose the volume server and media server to use.

nbemm callsnbrmmson the media server that was chosen to mountthe volume.

If, during the backup, a tape span is required, bptm againexchanges information with nbjm to release the correct tape andto get another one. nbjm exchanges information with nbrb toaccomplish this function.

For BasicDisk, bpdm writes the images to the path that isconfigured in the disk storage unit. The system disk managercontrols the actual writing of data.

In the case of an archive, bpbrm deletes the files from the clientdisk after the files are successfully backed up.

backup manager fortape (bptm) or disk(bpdm)

Receives the completion status of the job from bpbrm.

Releases the resources to nbrb and returns the status to nbpem.

Job manager service(nbjm)

Backup with multiple data streamsFor multiplexed backups, the process is essentially the same. An exception is thata separate bpbrm process and bptm process is created for each backup image beingmultiplexed onto the media. NetBackup also allocates a separate set of sharedmemory blocks for each image.

The other client and server processes are the same as shown in Figure A-1.

Backup and restore functional overviewBackups and archives - UNIX clients

640

Figure A-2 shows multiplexed images from two clients.

Figure A-2 Multiplexed backups example (two streams)

Notes:

.

UNIX client

nbrmms

nbemm

Diskvolume

Client disk

bpcd

ltid*

File info

Fileinfo

Backup Image

Backup

Image

Mount

Mount

Taperequest

Mountrequest

NetBackup server

bpbkar

bptm(parent)

bptm(child)**

Sharedmemory

Backup ImageTape

bpdbm

* For details on these components, see the Media and Device Management FunctionalDescription later in this chapter.

** If the server is backing up itself (server and client on same host), there is nobptm child: bpbkar sends the data directly to shared memory.

UNIX client

Client disk

bpcd

File infobpbkar

Backup Im

age

bprm(child)

bprm(parent)

bprm(child)

File info

Shared

memo

ry

Only onmaser server

See Figure A-1 for processdetails leading to nbemm. bptm

(child)**

Snapshot backup and Windows open file backupsFigure A-3 shows the overall snapshot backup process. PBX (not shown in thediagram) must be running for NetBackup to operate.

641Backup and restore functional overviewBackups and archives - UNIX clients

Figure A-3 Snapshot backup and Windows open file backup using multipledata streams

Notes:

.

UNIX client

NetBackup userinterface or

command line

bpbackup orbparchive

ConfigurationDatabase

nbrmms

nbpem

nbemm nbrb

nbproxy

nbproxy

FileDatabase

EMMDatabase

Diskvolume

Clientdisk

nbjm

bpcd

bprd

Backup PolicyManagement

bpcd

ltid*

Catalog Info

Catalog Info

Backup Image

Backup

Image

MountMount

Taperequest

Mount

reques

t

Master or media server

Master server

bpbkar

bptm(parent)

bptm(child)**

SharedmemoryBackup Image

Tape

bpdbm

* For details on these components, see the Media and Device Management FunctionalDescription later in this chapter.

** If the media server is backing up itself (server and client on same host), there is nobptm child: bpbkar sends the data directly to shared memory.

bpbrm

bpcd

bpfis

Create

Snapshot

bpbrm

A separate parent job creates all snapshots followed by a child job that backs upthe snapshot. An exception is when Windows opens file backups that do not usemultiple data streams.

The following sequence of operation is for snapshot creation and backup thatincludes Windows open file backups that employ multiple data streams:

■ The NetBackup master server or primary client initiates the backup. Thisaction causes the NetBackup request daemon bprd to submit a backup request

Backup and restore functional overviewBackups and archives - UNIX clients

642

to the Policy Execution Manager nbpem. nbpem processes the policyconfigurations.

■ nbpem (through nbjm) starts a parent job to create the snapshot. This job isseparate from the job that backs up the snapshot.

■ nbjm starts an instance of bpbrm through bpcd on the media server, and bpbrm

starts bpfis through bpcd on the client.

■ bpfis creates a snapshot of the client’s data by means of a snapshot method.

■ When bpfis is finished, it sends snapshot information and completion statusto bpbrm and exits. bpbrm, in turn, reports the snapshot information and statusto nbjm and exits. nbjm relays the information and status to nbpem.

■ nbpem submits a child job for the backup to nbjm, with a file list derived fromthe snapshot information. nbjm starts bpbrm to back up the snapshot.

■ bpbrm starts bpbkar on the client. bpbkar sends the file catalog informationto bpbrm, which relays it to the NetBackup file database bpdbm on the masterserver.

■ bpbrm starts the process bptm (parent) on the media server.

■ The next step depends on whether the media server backs up itself (bptm andbpbkar are on the same host) or the media server backs up a client that resideson a different host. If the media server backs up itself, bpbkar stores thesnapshot-based image block by block in shared memory on the media server.If the media server backs up a client that resides on a different host, bptm onthe server creates a child process of itself. The child receives thesnapshot-based image from the client by means of socket communicationsand then stores the image block-by-block in shared memory.

■ The original bptm process then takes the backup image from shared memoryand sends it to the storage device (disk or tape).Information is available on how the tape request is issued.See “Media and device management process” on page 687.

■ bptm sends backup completion status to bpbrm, which passes it to nbjm.

■ When nbpem receives backup completion status from nbjm, nbpem tells nbjmto delete the snapshot. nbjm starts a new instance of bpbrm on the media server,and bpbrm starts a new instance of bpfis on the client. bpfis deletes thesnapshot on the client, unless the snapshot is of the Instant Recovery type, inwhich case it is not automatically deleted. bpfis and bpbrm report their statusand exit.For more information on snapshot backups involving Snapshot Client, referto the following:

643Backup and restore functional overviewBackups and archives - UNIX clients

See the NetBackup Snapshot Client Administrator’s Guide.Note that Windows open file backups do not require Snapshot Client.

SAN clientFor backups to disk, the SAN Client feature provides high speed data movementbetween NetBackup media servers and NetBackup SAN-attached clients.SAN-attached clients send backup data to the media server by means of fibrechannel connections.

As part of SAN Client, the FT Service Manager (FSM) is a domain layer servicethat resides on the EMM server. The FSM provides discovery, configuration, andevent monitoring of SAN Client resources. The FSM collects fibre channelinformation from the client and from the media server; FSM then populates theEMM database with the information. (FSM runs in the same process as EMM.)FSM interacts with the nbftclnt process on NetBackup clients and with the nbftsrvrprocess on media servers.

The initial stages of a backup are the same as shown in Figure A-1

Figure A-4 shows the server and client components that are unique to SAN clientbackup over Fibre Channel.

Backup and restore functional overviewBackups and archives - UNIX clients

644

Figure A-4 SAN client backup over Fibre Transport

EMM Server

UNIX Clientbpcd

Bptm(parent)

Client disk

bpbkar

bpcd

bpbrm

FT Service Manager(FSM - Part of EMM)

Backup

Image

catalog Info

Master or MediaServer

nbjm

SharedMemory

nbftclntnbftsrvr

StorageDisk

SharedMemory

Backup Imagesent over FiberChannel

The process flow for a SAN Client backup is as follows (in the order presented):

■ A start-up script launches bprd on the master server and ltid on the masterserver and all media servers.All other daemons and programs are started as necessary including nbpem,nbjm, nbrb, and nbemm.

■ The policy execution manager service (nbpem) does the following:

■ Gets the policy list from bpdbm.

■ Builds a work list of all scheduled jobs.

■ Computes the due time for each job.

■ Sorts the work list in order of due time.

■ Submits to nbjm all jobs that are currently due.

■ Sets a wakeup timer for the next due job.

645Backup and restore functional overviewBackups and archives - UNIX clients

■ When the job finishes, re-computes the due time of the next job and submitsto nbjm all jobs that are currently due.

■ The job manager service (nbjm) requests backup resources from the resourcebroker (nbrb). nbrb returns information on the use of shared memory for SANClient.

■ nbjm starts the backup by means of the client daemon bpcd, which starts thebackup and restore manager bpbrm.

■ bpbrm starts bptm. bptm does the following:

■ Requests SAN Client information from nbjm.

■ Sends a backup request to the FT server process (nbftsrvr).

■ Sends a backup request to the FT Client process on the client (nbftclnt).nbftclnt opens a fibre channel connection to nbftsrvr on the media server,allocates shared memory, and writes shared memory information to thebackup ID file.

■ bpbrm starts bpbkar by means of bpcd. bpbkar does the following:

■ Reads the shared memory information from the BID file (waits for the fileto exist and become valid).

■ Sends the information about files in the image to bpbrm.

■ Writes the file data to tar, optionally compresses it, and writes the data tothe shared buffer.

■ When the buffer is full or the job is done, sets buffer flag.

■ The FT Client process nbftclnt waits for the shared memory buffer flag to beset. nbftclnt then transfers the image data to the FT Server (nbftsrvr) sharedmemory buffer, and clears the buffer flag.

■ nbftsrvr waits for data from nbftclnt; the data is written to the shared memorybuffer. When the transfer completes, nbftsrvr sets the buffer flag.

■ bptm waits for the shared memory buffer flag to be set, writes data from thebuffer to the storage device, and clears the buffer flag.

■ At the end of the job:

■ bpbkar informs bpbrm and bptm that the job is complete.

■ bptm sends bpbrm the final status of the data write.

■ bptm directs nbftclnt to close the fibre channel connection.

■ nbftclnt closes the fibre channel connection and deletes the BID file.

Backup and restore functional overviewBackups and archives - UNIX clients

646

Backups and archives - WindowsNetBackup supports the same types of operations on Windows clients as it doeson UNIX clients.

Figure A-5 shows the Windows client processes.

In this figure, the following items applies:

■ NBWIN is the user interface program on the client. The bpbackup function andthe bparchive function are merged into NBWIN.

■ BPINETD serves the same purpose as inetd on UNIX clients.

■ The NetBackup client daemon is called BPCD.

■ BPBKAR32 serves the same purpose as bpbkar on UNIX clients.

The server processes are the same as described for UNIX.

Figure A-5 Backup and archive - Windows clients

bprd

For details on the server processes, seeBackups and Archives - UNIX Clientsearlier in this chapter.

Server Windows 2000 Client

Client Disk

bpbrm

NetBackup UserInterface

Backup Image

File Infomation

requestNBWIN

BPINETD

bptmBPCD

BPBKAR32

647Backup and restore functional overviewBackups and archives - UNIX clients

Backups and archives - NetWare clientsNetBackup supports the same types of operations on NetWare clients as it doeson UNIX clients, with the following exceptions:

■ Raw partition backups are not supported.

■ NetBackup for NetWare does not support archiving.

Figure A-6 shows the NetWare client processes.

In this figure, the following item applies:

■ For NetWare nontarget operations, the Windows-based user interface programis called NBNWNT. For NetWare target operations, the user interface programis called BP.NLM on the Netware console. The bpbackup, bparchive, and bplistfunctions are merged into the user interface programs on the clients.

■ The NetBackup NetWare client daemon is called BPCD. The bpbkar functionsare merged into BPCD.

The server processes are the same as described for UNIX.

Backup and restore functional overviewBackups and archives - UNIX clients

648

Figure A-6 Backup and archive -- NetWare clients

.

NetWare client

NetBackupuser interface

NBNWNT (NetWare nontarget)BP (NetWare target)

Client disk

bpbrm

bprd

File information

Server

Backup

Image

bptm

Request

bpcd

For details on the server processes, seeBackups and Archives – UNIX Clients earlierin this chapter.

Synthetic backupsThe typical NetBackup backup process accesses the client to create a backup. Asynthetic backup is a backup image created without using the client. Instead, asynthetic backup process creates a full or a cumulative incremental image byusing only previously created backup images, called component images.

Note: Synthetic archives do not exist.

For example, an existing full image and subsequent differential incrementalimages may be synthesized to create a new full image. The previous full imageand the incrementals are the component images. The new synthetic full imagebehaves like a backup that is created through the traditional process. The new

649Backup and restore functional overviewBackups and archives - UNIX clients

synthetic full image is a backup of the client that is as current as the lastincremental. The synthetic image is created by copying the most current versionof each file from the most recent component image that contain the file. Asynthetic backup must be created in a policy with the True Image Restore withMove Detection option selected. This option enables the synthetic backup toexclude the files that have been deleted from the client file system from appearingin the synthetic backup.

Like a traditional backup, nbpem typically initiates a synthetic backup. nbpemsubmits a request to nbjm to start the synthetic backup job. nbjm starts bpsynth.bpsynth executes on the master server. It controls the creation of the syntheticbackup image and the reading of the files that are needed from the componentimages. If directory bpsynth exists in the debug log directory, additional debuglog messages are written to a log file in that directory.

bpsynth makes a synthetic image in several phases:

Phase 1 - Prepare catalog information and extentsIn phase 1, bpsynth makes a synthetic backup request to the database manager,bpdbm. bpdbm uses the entries and the TIR information from the catalogs of thecomponent images to build the catalog for the new synthetic image. It also buildsthe extents to be copied from the component images to the synthetic image. Bpdbmreturns the list of extents to bpsynth. (An extent is the starting block number andthe number of contiguous blocks within a specific component image.) A set ofextents must usually be copied from each component image onto the new syntheticimage.

Figure A-7 shows how phase 1 operates.

Figure A-7 Synthetic backup -- preparation phase

Catalog

nbjm

nbpem

bpsynth bpdbm

Request to makesynthetic backup

Extents and medianeeded to form thesynthetic backup

Backup and restore functional overviewBackups and archives - UNIX clients

650

Phase 2 - Obtain resourcesIn phase 2, bpsynth obtains write resources (storage unit, drive, and media) forthe new image. It also reserves all the read media containing component imagesand obtains the drive for the first media to be read.

When the component images reside on BasicDisk or NearStore, no resourcereservation is done.

Phase 3 - Copy dataIn phase 3, bpsynth starts the writer bptm (for tape and disk) on the media serverto write the new synthetic image. bpsynth starts a reader bptm (tape) or bpdm (disk)process for each component image on a media server that can access thecomponent image. The reader process reads all extents for the component image.

Figure A-8 illustrates how phase 3 operates.

Figure A-8 Synthetic backup -- copy data phase

newimage

componentimage(s)

data flow

parent bptmor bpdm

bpsynth

childbptm orbpdm

childbptm

parentbptm

Media serverMaster server

Note that bpsynth only starts the parent bptm (writer) and bpdm (reader) processon the media server. The parent in turn starts a child process. The parent andchild communicate by means of buffers in shared memory.

The bpsynth process sends the extents (starting block and count) for eachcomponent image to the corresponding child bptm or bpdm reader process.

651Backup and restore functional overviewBackups and archives - UNIX clients

The parent bptm or bpdm reader process reads the data from the appropriate mediainto the shared buffers. The child bptm or bpdm reader process sends the data inthe shared buffers to the child bptm writer process over a socket. The child bptm

writer process writes the data into the shared buffers.

The parent bptm writer process copies the data from the shared buffers to themedia and notifies bpsynth when the synthetic image is complete.

Phase 4 - Validate the imageIn phase 4, the bpsynth process validates the image. The new image is now visibleto NetBackup and can be used like any other full or cumulative incremental backup.

Synthetic backup requires the following:

■ That True Image Restore (TIR) with move detection be selected for eachcomponent image.

■ That the component images are synthetic images.

NetBackup online, hot catalog backupOnline, hot catalog backup. This type of catalog backup is policy-based, with allof the scheduling flexibility of a regular backup policy. This backup type is designedfor highly active NetBackup environments where other backup activity usuallytakes place. The catalog backup is performed online, meaning that the catalog isnot turned off. More details are available.

See “Hot catalog backup process” on page 652.

You can use an option in the Administration Console to start a manual backup ofthe NetBackup catalogs. Or, you can configure a NetBackup policy to automaticallyback up its catalogs.

Hot catalog backup processFigure A-9 shows the hot catalog backup that is followed by the backup processitself.

Backup and restore functional overviewBackups and archives - UNIX clients

652

Figure A-9 Hot catalog backup process

5

bprd

Master Server Backup PolicyManagement

bpbackup

bpdbm

nbpem

Command line

See “Backup to tape or disk”on page591.

Note: the master server backsup itself.

Back up Relational Database Files Back up NetBackup Database Files

Sybase ASAdatabase agent

Relationaldatabase files

/usr/openv/db/staging

bprd

See “Backup to tape or disk” on page591.

Note: the master server backs up the EMM server.

bprd

1

nbjm

2

3

4

3a

3b

A hot catalog backup consists of the following jobs that run on the master server:

■ A parent job that is started manually by the administrator or by a catalogbackup policy schedule.

■ A child job that backs up the NetBackup relational database files.

■ A child job that copies the NetBackup database files on pre-6.0 media servers,if any.

■ A child job that backs up the NetBackup database files (all files in/usr/openv/netbackup/db).

A hot catalog backup process is as follows (in the order presented):

■ A manual backup or a catalog backup policy initiates the backup.

653Backup and restore functional overviewBackups and archives - UNIX clients

■ nbpem submits a parent job to nbjm; nbjm sends a request to bpdbm.

■ bpdbm handles the backup of the relational database files, in two steps:

■ The SQL Anywhere files database agent makes an online copy of therelational database files to /usr/openv/db/staging. See the DisasterRecovery chapter for a list of the relational database files.

■ After the files are in the staging area, the SQL Anywhere database agentbacks them up in the same manner as is used for an ordinary backup.

■ NetBackup backs up the database files that are in /usr/openv/netbackup/db

and important NetBackup files to the master server.

■ NetBackup creates the disaster recovery file, and emails it to the administratorif the email option was selected in the policy.

Consult the following logs for messages on hot catalog backup:

■ bpdbm, bpbkar, bpbrm, bpcd, bpbackup, bprd

Note: If the EMM server is on its own host (separate from the master server),consult this log on the EMM server: /usr/openv/netbackup/logs/admin (UNIX),or install_path\NetBackup\logs\admin (Windows).

For messages pertaining only to the relational database files, see the progress logfile in the following directory:

■ /usr/openv/netbackup/logs/user_ops/dbext/logs (UNIX)

■ install_path\NetBackup\logs\user_ops\dbext\logs (Windows)

Restore processesNetBackup restore operations, like backups, can vary according to client type.The following explains the variations.

Restoring UNIX and Linux clientsBefore starting a restore, a user browses the file catalog to list the files availablein the backup images. The desired files can then be selected from the list.

The browsing is done through the bplist program on the client. The bplist

program can be started directly from the command line and the NetBackup userinterface programs can use it.

bplist obtains the file list by sending a query to the request daemon, bprd, onthe master server (see Figure A-10).

Backup and restore functional overviewRestore processes

654

The request daemon, in turn, queries bpdbm for the information and transmits itto bplist on the client.

Figure A-10 List operation - UNIX and Linux client

bprd

Master Server

bpdbm

FileDatabase

NetBackup UserInterface

query

UNIX Client

Command line

bplistFile list File list

Refer to one of the following topics as you read through the restore process.

See Figure A-11 on page 657.

See Figure A-12 on page 658.

The following are the processing steps in a restore (in the order presented):

■ When the user starts a restore, NetBackup invokes the client’s bprestoreprogram which sends a request to the request daemon, bprd. This requestidentifies the files and client. The request daemon then uses bpcd (clientdaemon) to start the backup and restore manager (bpbrm).

Note: To restore Backup Exec images, bpbrm initiates mtfrd instead of tar onthe clients. The server processes are the same as those used for NetBackuprestores.

■ If the disk device or tape device on which the data resides attaches to themaster server, the following occurs:bprd starts the backup and restore manageron the master server. If the disk unit or tape unit connects to a media server,bprd starts the backup and restore manager on the media server.

■ The backup and restore manager starts bptm and uses the client daemon (bpcd)to establish a connection between the NetBackup tar program on the clientand bptm on the server.

655Backup and restore functional overviewRestore processes

■ The bptmprocess identifies which media (disk or tape) is needed for the restore,based on the image catalog. bptm then requests the allocation of the requiredmedia from nbrb through nbjm. nbjm then asks mds (part of nbemm)for theresources. nbemm allocates the media and selects and allocates an appropriatedrive (for tape media).For tape: bptm asks ltid to mount the tape in the drive. For disk: (such asSharedDisk, AdvancedDisk, or OpenStorage), nbrb tells nbemm to issue themount by means of nbrmms, after nbemm allocates the resources.

For restore from non-shared disk (BasicDisk, PureDisk, NearStore, SnapVault),bptm does not need to ask nbrb for an allocation, because disk inherentlysupports concurrent access. bptm uses the file path in a read request to thesystem disk manager.

■ When the allocation is granted to it, bptm starts retrieving data. bptm storesthe image block-by-block in shared memory.

■ bptm directs the image to the client in one of two ways. If the server restoresitself (server and client are on the same host), tar reads the data directly fromshared memory. If the server restores a client that resides on a different host,it creates a child bptm process which transmits the data to tar on the client.

Note: Only the part of the image that is required to satisfy the restore requestis sent to the client, not necessarily the entire backup image.

■ The NetBackup tar program writes the data on the client disk.

PBX must be running for NetBackup to operate (PBX is not shown in the nextdiagram).

See “Resolving PBX problems” on page 67.

Figure A-11 shows how to restore from tape in the UNIX and Linux environments:

Backup and restore functional overviewRestore processes

656

Figure A-11 Restore from tape (UNIX and Linux)

Notes:

.

UNIX client

NetBackupuser interface

Commandline

bprestore

nbemm nbrb nbjm

EMMDatabase

Client disk

bpcd

bpbrm

bprd

bpcd

ltid*

Backup ImageMount

Taperequest

Master or media server

Master server

NetBackuptar

bptm(parent)

bptm(child)**

SharedmemoryBackup Image

Tape

* For details on this component, see the Media and Device Management FunctionalDescription later in this chapter. Itid is for tape backup only

** If the media server is restoring its own data (server and client on same host), thereis no bptm child: tar reads the data directly from shared memory.

Figure A-12 shows how to restore from disk in the UNIX and Linux environments:

657Backup and restore functional overviewRestore processes

Figure A-12 Restore from disk (UNIX and Linux)

Note:.

UNIX client

NetBackupuser interface

Commandline

bprestorenbemm nbrb nbjm

EMMDatabase

Client disk

bpcd

bpbrm

bprd

bpcd

Master or media server

Master server

NetBackuptar

bptm

bptm*

Sharedmemory

Backup Image

* If the server is restoring its own data (server and client on same host), there is nobptm child: tar reads the data directly from shared memory.

Disk volume

Backup

Image

nbrmms

Mount

requestMount

Restoring SAN client (UNIX or Windows)Figure A-13 shows the server and client components that are used in a restore ofa SAN client over Fibre Channel.

Backup and restore functional overviewRestore processes

658

Figure A-13 SAN client restore with Fibre Transport

.

UNIX client

NetBackupuser interface

Commandline

bprestorenbjm

Client disk

bpcd

bpbrm

bprd

bpcd

Master or media server

Master server

NetBackup tar -UNIX TAR32 -Windows

bptm

bptmchild

Storage device(tape or disk)

BackupImage

nbftsrvr nbftclnt

Sharedmemory

Backup image sent overFibre Channel

Sharedmemory

BackupImage

The process flow for a SAN Client restore is as follows (in the order presented).

■ When the user starts a restore, NetBackup invokes the client’s bprestoreprogram which sends a request to the request daemon, bprd. This requestidentifies the files and client. The request daemon then uses bpcd (clientdaemon) to start the backup and restore manager (bpbrm).

Note: To restore Backup Exec images, bpbrm invoke mtfrd instead of tar onthe clients. The server processes are the same as those used for NetBackuprestores.

659Backup and restore functional overviewRestore processes

■ If the disk device or tape device on which the data resides attaches to themaster server, then bprd starts the backup and restore manager on the masterserver. If the disk unit or tape unit connects to a media server, bprd starts thebackup and restore manager on the media server.

■ bpbrm starts bptm and provides bptm with the backup ID and the shmfat(shared memory) flag.

■ bptm does the following:

■ Requests SAN Client information from nbjm.

■ Sends a restore request to the FT server process (nbftsrvr).

■ Sends a restore request to the FT Client process on the client (nbftclnt).nbftclnt opens a fibre channel connection to nbftsrvr on the media server,allocates shared memory, and writes shared memory information to thebackup ID file.

■ bpbrm starts tar by means of bpcd and provides tar with the backup ID, socketinformation, and the shmfat (shared memory) flag.

■ bptm does the following:

■ Reads the image from the storage device.

■ Creates a bptm child process. This process filters the backup image so thatonly the files that are selected for the restore are sent to the client.

■ Writes the image data to the shared buffer on the server.

■ When buffer is full or job is done, sets buffer flag (partial buffers may besent to the client).

■ tar does the following:

■ Sends the status and control information to bpbrm.

■ Reads the shared memory information from the local backup ID file (waitsfor the file to exist and become valid).

■ Waits for the buffer flag that indicates the data is ready to be read.

■ Reads data from the buffer, extracts files and restores them. When theshmfat (shared memory) flag is provided, tar considers the data to be alreadyfiltered.

■ The FT Server process nbftsrvr waits for the shared memory buffer flag to beset. nbftsrvr then transfers the image data to the FT Client (nbftclnt) sharedmemory buffer, and clears the buffer flag.

■ The FT Client (nbftclnt) waits for the data from nbftsrvr and writes the datato the shared memory buffer on the client. nbftclnt then sets the buffer flag.

Backup and restore functional overviewRestore processes

660

■ At the end of the job:

■ bptm informs tar and bpbrm that the job is complete.

■ bptm directs nbftclnt to close the fibre channel connection.

■ nbftclnt closes the fibre channel connection and deletes the BID file.

Restoring Windows clientsNetBackup supports the same types of operations on Windows clients as it doesfor UNIX clients.

The following are the Windows processes involved in restore operations:

■ NBWIN is the user interface program on the client. The bpbackup function andthe bparchive function are merged into NBWIN.

■ BPINETD serves the same purpose as inetd on UNIX clients.

■ The NetBackup client daemon is called BPCD.

■ TAR32 is part of NetBackup for Windows and serves the same purpose asNetBackup tar on UNIX.

Note: To restore Backup Exec images, bpbrm invokes mtfrd.exe instead oftar32.exe on the clients. The server processes are the same as those used forNetBackup restores.

The server processes are the same as described for UNIX.

Figure A-14 shows the client processes involved in these operations.

661Backup and restore functional overviewRestore processes

Figure A-14 Restore - Windows client

bprd

For details on the server processes, see“Backups and archives - UNIX clients”earlier in this chapter.

Server Windows Client

NetBackup UserInterface

Backup Image

Request

Client Disk

NBWIN

BPINETD

BPCD

TAR32

bpbrm

bptm

Restoring NetWare clientsNetBackup supports the same types of restore operations on NetWare clients asit does on UNIX clients.Figure A-15 shows the client processes involved in theseoperations. In this figure, the following applies:

■ The NetWare nontarget user interface program is called NBNWNT. The NetWaretarget user interface program is BP on the Netware console. The bprestore

function and the bplist function are merged into the user interface programson the clients.

■ The NetBackup NetWare client daemon is called BPCD. The NetBackup tar

functions are merged into BPCD.

Backup and restore functional overviewRestore processes

662

■ mtfrd functionality (used to restore Backup Exec images) has been mergedinto BPCD. The server processes involved in import and restore operations forBackup Exec images are the same as those involved for NetBackup restores.

The server processes are the same as described for UNIX.

Figure A-15 shows the restore operation for a NetWare client

Figure A-15 Restore - NetWare client

.

NetWare client

NetBackupuser interface

NBNWNT (NetWare nontarget)

Client disk

bprd

Server

Backup Imagebptm

Request

BPCD (NetWare)

For details on the server processes, seeBackups and Archives – UNIX Clients earlierin this chapter.

663Backup and restore functional overviewRestore processes

Restoring catalog backupsA catalog restore can be initiated by the NetBackup Catalog Recovery Wizard inthe Administration Console, or by manual use of the bprecover command. Moreinformation is available in the following topic:

See “About disaster recovery” on page 571.

Figure A-16 illustrates the catalog restore and recovery process.

Figure A-16 Catalog restore and recovery

NetBackup CatalogRecovery Wizard Command line

bprecover

/usr/openv/db/staging

Relationaldatabase files

bprd

Sybase ASAdatabase agent

Restore RelationalDatabase Files

bprd

See “Restore fromtape (UNIX)” or“Restore from

disk”, dependingon the catalogbackup policy.

See “Restore fromtape (UNIX)” or“Restore from

disk”, dependingon the catalogbackup policy.

Restore NetBackupDatabase Files

1

2 3 4

Backup and restore functional overviewRestore processes

664

A restore of the NetBackup database and relational database files from a hotcatalog backup consists of the following steps (in the order presented):

■ The NetBackup database files are restored by means of the standard NetBackuprestore procedure.

■ The relational database files are restored by means of the standard NetBackuprestore procedure. The database files are restored to /usr/openv/db/staging(UNIX and Linux), or to install_path\NetBackupDB\staging (Windows).

■ After the files are restored to the staging directory, the relational database isrecovered. Each transaction log in the staging area is applied in order, one byone.

■ The relational database files are moved from the staging directory to a locationdetermined by the following: the bp.conf file VXDBMS_NB_DATA setting on UNIXor Linux and by the corresponding registry key on Windows. The defaultlocation is /usr/openv/db/data on UNIX and Linux, andinstall_path\NetBackupDB\data on Windows.

If the relational database files are relocated, they are moved from the stagingdirectory to the /usr/openv/db/data/vxdbms.conf file (UNIX) or theinstall_path\NetBackupDB\data\vxdbms.conf file (Windows). A descriptionis available of how the NetBackup relational database files can be relocatedafter installation.See "NetBackup Relational Database" in theNetBackupAdministrator’sGuide,Volume I.

Messages that are related to this catalog recovery process are divided into thefollowing three areas:

■ For messages that are related to all catalog recovery steps, consult the/usr/openv/netbackup/logs/admin logs (UNIX and Linux), orinstall_path\NetBackup\logs\admin (Windows).

■ For messages that are related to the first two bulleted items, consult the tar,bpbrm, and bpcd logs.

■ For messages pertaining only to the relational database files, see the progresslogs in the following directory:/usr/openv/netbackup/logs/user_ops/root/logs (UNIX and Linux), orinstall_path\NetBackup\logs\user_ops\root\logs (Windows).

NetBackup directories and filesFigure A-17 shows the NetBackup file and directory structure on UNIX serversand clients. If a host is only a client and not a server, only the files in the Client

665Backup and restore functional overviewNetBackup directories and files

portion are present. If a host is both a client and a server, the client shares filesas necessary from those in the Server portion.

A Windows NetBackup server has equivalent files and folders that are locatedwhere NetBackup is installed (C:\Program Files\VERITAS by default).

NetBackup directory structure - UNIXFigure A-17 lists the items that are described in tables on the following pages.

Figure A-17 NetBackup directories and files

/usr/openv/netbackup/

/usr/openv/

NetBackup server

NetBackup client

bin/

tmp/

db/

var/

java/ logs/

share/msg/ netbackup/man/

bin/ bp.conf help/ logs/

lib/

volmgr/

resources/

bin/ db/ dbext/

version_master

bp.conf client/

help/ logs/

remote_versions/

nblog.conf.template nbsvcmon.confnblog.conf

/usr/openv/netbackup/

/usr/openv/

bin/ java/ lib/ msg/ netbackup/ resources/ share/ tmp/ var/

nblog.conf1 nblog.conf.templatedbext/

version

Table A-2 describes the /usr/openv/ files and directories.

Backup and restore functional overviewNetBackup directories and files

666

Table A-2 Directories and files in /usr/openv/ - servers and UNIX clients

ContentsFile or directory in/usr/openv/

Contains miscellaneous executable binaries including thevnetd daemon and utilities for legacy enhanced authentication.

bin/

Contains the NetBackup Relational Database Manager (SQLAnywhere) and database data file.

db/

Contains the NetBackup-Java Administration Console and theBackup, Archive and Restore user interface.

java/

Contains shared libraries that are required for NetBackupoperation.

lib/

Contains all logs that are written by unified logging. You donot have to create subdirectories for these logs.

logs/

Contains man pages for NetBackup commands.man/

Contains the message files and a configuration file for allinstalled languages of NetBackup.

msg/

A tar file that contains the NetBackup-Java interfaces.NB-Java.tar.Z

See Table A-3 on page 668.netbackup/

Contains the NetBackup message catalogs that are used byunified logging (VxUL).

resources/

Contains static configuration files. These files are normallyunchanged between NetBackup releases.

share/

Contains the NetBackup Relational Database Manager (SQLAnywhere) installation trace files, and the log files regardingto database start and stop.

tmp/sqlany

Contains the variable configuration files. These files, whichare related to licensing, authentication, authorization, andnetworking, may change while NetBackup is running./usr/openv/var/global contains various static andvariable configuration files. In a cluster, the /globaldirectory is shared between nodes.

var/

Contains the media and device management directories andfiles.

See “NetBackup directory structure - UNIX” on page 666.

volmgr/

667Backup and restore functional overviewNetBackup directories and files

Contents of /usr/openv/netbackupTable A-3 describes the /usr/openv/netbackup files and directories.

Table A-3 Directories and files in /usr/openv/netbackup/ - servers and UNIXclients

ContentsFile or Directory in/usr/openv/netbackup/

Commands, scripts, programs, daemons, and files that arerequired for NetBackup operation and administration. On aserver, there are two subdirectories under bin.

admincmd: Contains various commands that used internallyby NetBackup. Use these commands ONLY if they aredocumented. Most of these commands are not documentedand should not be used directly.

goodies (UNIX only): Contains scripts and information thatmay be useful to the administrator.

These subdirectories are not present on clients.

bin/

Configuration file containing options for NetBackup operation.A detailed explanation is available about each option and howto set it.

See the NetBackup Administrator’s Guide, Vol II.

On a Windows server, these options are set in the NetBackupAdministration Console.

bp.conf

NetBackup client software that is installed on the clientsduring installation. Do not install this directory on a mediaserver.

client/

NetBackup catalogs.

See Table A-5 on page 682.

db/

For NetBackup database agent software, contains the versionfile, compressed tar file, and install_dbext script.

dbext/

Help files that are used by NetBackup programs. These filesare in ASCII format.

help/

Backup and restore functional overviewNetBackup directories and files

668

Table A-3 Directories and files in /usr/openv/netbackup/ - servers and UNIXclients (continued)

ContentsFile or Directory in/usr/openv/netbackup/

Legacy debug logs for NetBackup processes. You must createthe necessary subdirectories in order for these log files to bewritten.

See “Legacy NetBackup logging” on page 103.

See Table A-4 on page 670. for an explanation of the processesthat produce the logs.

logs/

Specifies the settings for unified logging.

Note: Do not edit this file manually: use the vxlogcfgcommand instead.

See “Configuring and using unified logging” on page 94.

nblog.conf

Specifies the settings for unified logging.

Note: Do not edit this file manually: use the vxlogcfgcommand instead.

See “Configuring and using unified logging” on page 94.

nblog.conf.template

Configuration file for the NetBackup Service Monitor. It tellsthe Service Monitor what services to monitor and how torestart them if they fail unexpectedly.

nbsvcmon.conf

A cache of the versions of other media servers in the system.remote_versions/

Version and release date of the software.version

Identifies the NetBackup master server.version_master

NetBackup programs and daemonsTable A-4 describes the programs and daemons that provide most of the controlfor backup, archive, and restore operations.

The explanations include what starts and stops the program or daemon, and thedebug log subdirectory (if any) where it records its activities.

You must create legacy logging directories manually; see "logs" in the previoustable. More information is available.

See “Legacy NetBackup logging” on page 103.

669Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs

DescriptionProgram/Daemon

On UNIX clients, this menu-driven, character-based interfaceprogram has options for starting user-directed backups, restores,and archives.

Started By: /usr/openv/netbackup/bin/bp command on theclient.

Stopped By: Exiting the interface program.

Debug Log: /usr/openv/netbackup/logs/bp on the client.The debug logs for bpbackup, bparchive, bprestore, andbplist also have information about bp activities.

bp

On NetWare target clients, BP.NLM is the NetWare LoadableModule that starts the client-user interface.

Started By: LOAD BP command.

Stopped By: Choosing Quit Utility from the main menu.

Debug Log:SYS:\VERITAS\NBUCLT\NETBACK\LOGS\BP\mmddyy.log fileon the client.

BP.NLM

On a UNIX master server, this administrator utility has amenu-driven, character-based, interface with options forconfiguring and managing NetBackup.

Started By:/usr/openv/netbackup/bin/bpadm command onthe master server.

Stopped By: Quit option from within bpadm.

Debug Log: admin legacy log directory on the server.

bpadm

On UNIX clients, this program communicates with bprd on themaster server when a user starts an archive.

Started By: Starting an archive by using the client-user interfaceor by executing the/usr/openv/netbackup/bin/bparchivecommand on the client.

Stopped By: Completion of operation.

Debug Log: bparchive legacy log directory on the client.

bparchive

Backup and restore functional overviewNetBackup programs and daemons

670

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On UNIX clients, this program communicates with bprd on themaster server when a user starts a backup.

Started By: Starting a backup by using the client-user interfaceor by executing the /usr/openv/netbackup/bin/bpbackupcommand on the client.

Stopped By: Completion of operation

Debug Log: bpbackup legacy log directory on the client.

bpbackup

On UNIX clients the Backup/Archive Manager generates thebackup images.

Started By: bpbrm on the server with the storage unit.

Stopped By: Completion of operation.

Debug Log: bpbkar legacy log directory on the client.

bpbkar

On Windows clients, the Backup/Archive Manager generates thebackup images.

Started By: BPCDW32 on the client.

Stopped By: Completion of operation.

Debug Log: BPBKAR legacy log directory in the NetBackup logsdirectory on the client.

BPBKAR32

On master and media servers, the Backup/Restore Managermanages the client and bptm or bpdm process. It also uses errorstatus from the client and from bptm or bpdm to determine thefinal status of backup or restore operations.

Started By: For each backup or restore, nbjm starts an instanceof bpbrm on the server with the appropriate storage unit.

Stopped By: Completion of operation.

Debug Log: bpbrm legacy log directory on the server.

bpbrm

671Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On UNIX clients, bpcd is the NetBackup client daemon and letsNetBackup start programs on remote hosts (can be UNIX clientsor other servers). For example, the server can connect to UNIXclients without requiring /.rhosts entries on the remote host.The program is used when nbjm starts bpbrm and when bpbrm

communicates with the client.

(For a description of the NetBackup client daemon on PC clients,see BPCDW32.EXE and BPCD.NLM in this table.)

Started By: inetd.

Stopped By: Completion of operation.

Debug Log: bpcd legacy log directory on both client and server.

bpcd

On NetWare clients, BPCD.NLM is the executable file that startsthe NetBackup client daemon.

Started By: When you enterBPSTART.NCF at the NetWare Serverconsole. Or, add BPSTART.NCF to your autoexec.ncf file.

Stopped By: UNLOAD BP command

Debug Log: BPCD legacy log directory on the client.

BPCD.NLM

On Windows clients, BPCDW32.EXE is the executable file thatstarts the NetBackup client daemon.

Started By: When Windows starts if the daemon is in the Startupgroup. Otherwise, by double clicking on its icon.

Stopped By: On Windows, you can stop it through the Servicesapplication in the Control Panel.

Debug Log: BPCD legacy log directory on the client.

BPCDW32.EXE

On UNIX master servers, this program is used to clean up theNetBackup jobs database.

Started By:/usr/openv/netbackup/bin/admincmd/bpdbjobs. Whenbprd starts, it runs this command automatically. Theadministrator can also execute it manually or with a cron job.

Stopped By: No terminate option exists for this command outsideof using kill.

Debug Log: bpdbjobs legacy log directory on the server.

bpdbjobs

Backup and restore functional overviewNetBackup programs and daemons

672

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On master servers, the NetBackup database manager programthat manages the configuration, error, and file databases.

Started By: bprd (also by/usr/openv/netbackup/bin/initbpdbm on UNIX)

Stopped By:/usr/openv/netbackup/bin/bpdbm -terminate

command on UNIX and by stopping the NetBackup DatabaseManager service on Windows.

Debug Log: bpdbm legacy log directory on the server.

bpdbm

On master and media servers, bpdm is used for the following diskoperations: read phase of disk duplication, read phase of syntheticbackups, disk verify and disk import, true image restore from disk,disk image deletion.

Started By: For each backup or restore, bpbrm starts an instanceof bpdm, on the server with the storage unit.

Stopped By: Completion of operation.

Debug Log: bpdm legacy log directory on the server.

bpdm

On clients, bpfis creates and deletes snapshots. Note that bpfis ispart of the Snapshot Client add-on product.

Started By: bpbrm.

Stopped By: Completion of operation.

Debug Log: bpfis legacy log directory on the client or alternateclient.

bpfis

On SQL, Oracle, Informix, Sybase, DB2, and SAP database clients,bphdb executes scripts to back up the database.

Started By: Client-user interface when the user starts a databasebackup operation.

Stopped By: Completion of operation.

Debug Log: bphdb legacy log directory on the client.

bphdb

673Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

NetBackup-Java master server application program. This programruns on all NetBackup UNIX systems and authenticates the usersthat start the NetBackup-Java interface programs.

Started By:inetdduring startup of the NetBackup Java interfaces.

Stopped By: When authentication is complete.

Debug Log: bpjava-msvc legacy log directory on the server.

bpjava-msvc

NetBackup-Java user server application program. This programservices all requests from the NetBackup-Java user andadministration interfaces.

Started By:bpjava-msvcupon successful login through the Logindialog box that is presented when a NetBackup-Java interface isstarted.

Stopped By: When the interface program is terminated.

Debug Log: bpjava-usvc legacy log directory.

bpjava-usvc

On UNIX clients, this program communicates with bprd on themaster server when a user browses the database during a restoreoperation.

Started By: Starting a search of the image database by using theclient-user interface or by executing the/usr/openv/netbackup/bin/bplist command on the client.

Stopped By: Completion of operation

Debug Log: bplist legacy log directory on the client.

bplist

Backup and restore functional overviewNetBackup programs and daemons

674

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On master servers, the request daemon responds to client andadministrative requests for the following:

■ Restores

■ Backups (scheduled and user-directed)

■ Archives

■ List that is backed up or archived files

■ Manual immediate backups (started through the NetBackupadministration interface manual backup option)

Started By: Initiate Request Daemon option on the Special Actionsmenu in bpadm (also the/usr/openv/netbackup/bin/initbprd command).

Stopped By: Terminate Request Daemon option on the SpecialActions menu in bpadm.

Debug Log: bprd legacy log directory on the server.

bprd

On UNIX clients, this program communicates with bprd on themaster server when a user starts a restore.

Started By: Starting restore by using the client-user interface (orby executing the /usr/openv/netbackup/bin/bprestorecommand on the client).

Stopped By: Completion of operation

Debug Log: bprestore legacy log directory on the client.

bprestore

On NetWare nontarget clients, BPSVR.NLM is the program thatallows the system that has the client-user interface tocommunicate with the Netware server that is the NetBackup client.

Started By: Enter bpstart.ncf.

Stopped By: Enter bpstop.ncf.

Debug Log: SYS:VERITAS\NBUCLT\NetBack\logs\bpsrv\directory on the client.

BPSVR.NLM

On Windows clients,BPSYS.EXE is the NetBackup System RegistryReplacement utility.

Started By: NetBackup as required.

Stopped By: Completion of operation.

Debug Log: BPSYS legacy log directory on the client.

BPSYS.EXE

675Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On master and media servers, bptm manages both disk and tapebackup and restore. It is used when the storage unit type is eitherdisk or Media Manager. This program manages the transfer ofimages between the client and the storage device.

Started By: For each backup or restore, bpbrm starts an instanceof bptm on the server that has the storage unit.

Stopped By: Completion of operation.

Debug Log: bptm legacy log directory on the server.

bptm

A Java-based program for performing backups, archives, andrestores of UNIX clients.

Started By: On UNIX, the/usr/openv/netbackup/bin/jbpSAcommand.

Debug Log: None, although the logs for the bpbackup,bparchive, bplist, and bprestore commands on the clientcan be useful. Also, check the bpjava-msvc and bpjava-usvclogs.

jbpSA

A Java-based administration utility for managing NetBackup onUNIX. In addition, administration of supported UNIX systems canbe performed by using the NetBackup-Java Windows DisplayConsole on a Windows system.

Started By: On UNIX, the/usr/openv/netbackup/bin/jnbSAcommand. On a NetBackup-Java Windows Display console, theNetBackup - Java on hostmenu item on the Programs/NetBackupmenu.

Stopped By: Exit option in jnbSA.

Debug Log: None, although the logs for bpjava-msvc andbpjava-usvc can be helpful.

jnbSA

Backup and restore functional overviewNetBackup programs and daemons

676

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On the server that is defined as the EMM server, nbemm managesdevices, media, and storage unit configuration, and performsresource selection. Replaces vmd as the device allocator.

Started By: Started when NetBackup starts.

Stopped By: /usr/openv/netbackup/bin/nbemmm-terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbemm

On a media server that is enabled for SAN Client backup over fibrechannel, nbfdrv64 is the following: a user mode component thatis used for both backup and restore. nbfdrv64 uses a windrvr6proxy to move fibre channel data between nbftclnt and bptmbuffers.

Started By: /usr/openv/netbackup/bin/nbftsrvr

Stopped By: /usr/openv/netbackup/bin/nbftsrvr-terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbfdrv64

On clients that are enabled for SAN Client backup over fibrechannel, nbftclnt transfers the backup image over fibre channelto nbftsrvr on the media server.

Started By: Started when NetBackup starts.

Stopped By: /usr/openv/netbackup/bin/nbftclnt-terminate.

Debug Log: On the client, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbftclnt

677Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On a media server that is enabled for SAN Client backup over fibrechannel, nbftsrvr does the following: reads the backup image fromnbftclnt and transfers it to shared memory on the media server.

Started By: Started when NetBackup starts.

Stopped By: /usr/openv/netbackup/bin/nbftsrvr-terminate.

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbftsrvr

On master servers, the nbjm service accepts job requests fromnbpem and from media commands such as bplabel and tpreq. nbjmacquires job resources from nbrb, and runs the jobs once resourcesare available.

Started By: Started when NetBackup starts.

Stopped By:/usr/openv/netbackup/bin/nbjm -terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbjm

For NetWare nontarget clients, NBNWNT.EXE is the executablefile that starts the client-user interface on Windows systems.

Started By: From the Windows Start menu, under Programs/NetBackup.

Stopped By: Exiting the client-user interface.

Debug Log: none.

NBNWNT.EXE

On master servers, the nbpem service uses nbproxy to get thepolicy list from bpdbm, creates the policy-client tasks, determineswhen jobs are due to run, and starts due jobs.

Started By: Started when NetBackup starts.

Stopped By:/usr/openv/netbackup/bin/nbpem -terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbpem

Backup and restore functional overviewNetBackup programs and daemons

678

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

Runs on the master server and the media server as a child of theprocess it serves. nbproxy provides a thread-safe API for thelibraries that are not yet thread safe.

Started By: the process that uses nbproxy as a proxy.

Stopped By: stops the process that uses nbproxy.

Debug Log: nbproxy legacy log directory on the server.

nbproxy

On the server that is defined as the EMM server, the nbrb serviceaccepts resource requests from nbjm, acquires physical resourcesfrom nbemm, and manages logical resources.

Started By: Started when NetBackup starts.

Stopped By:/usr/openv/netbackup/bin/nbrb -terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbrb

Controls backup and restore operations on a NAS server.ndmpagent is for remote NDMP: backing up NDMP data to a drivethat is configured in a Media Manager storage unit on a NetBackupmedia server.

Started By: bpbrm.

Stopped By: Completion of backup or restore.

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

ndmpagent

Runs on the master server. The nbstserv service manages lifecycleoperations including duplication, staging, and image expiration.

Started By: Started when NetBackup starts.

Stopped By: /usr/openv/netbackup/bin/nbstserv-terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows). For more information aboutOID 226 and 272, see the following topic:

See “Server processes that use unified logging” on page 87.

nbstserv

679Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

For Windows clients, NBWIN.EXE is the executable file that startsthe client-user interface on Windows systems.

Started By: From the Windows Start menu, under Programs/NetBackup.

Stopped By: Exiting the client-user interface.

Debug Log: NBWIN legacy log directory on the client.

NBWIN.EXE

Remote Manager and Monitor Service (nbrmms) is the conduitthrough which EMM discovers and configures storage on mediaservers. In addition to configuration management, nbrmmsprovides all access to media server resources for monitoring andevent notifications.

Started By: Started when NetBackup starts, or by/usr/openv/netbackup/bin/nbrmms

Stopped By: Stopped when NetBackup stops, or by/usr/openv/netbackup/bin/nbrmms -terminate

Debug Log: On the server, /usr/openv/logs (UNIX) orinstall_path\logs (Windows).

See “Unified logging” on page 85.

nbrmms

Private Branch Exchange (PBX) is a common services frameworkthat helps limit the number of TCP/IP ports that the CORBAservices of NetBackup use.

Started By: Started when NetBackup starts, or by/opt/VRTSpbx/bin/vxpbx_exchanged start

Stopped By: Stopped when NetBackup stops, or by/opt/VRTSpbx/bin/vxpbx_exchanged stop

Debug Log: On the server, /opt/VRTSpbx/log (UNIX) orinstall_path\VxPBX\log (Windows).

See “PBX logging” on page 69.

pbx_exchange

Backup and restore functional overviewNetBackup programs and daemons

680

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On a Solaris media server that is enabled for SAN Client transfersover fibre channel: ql2300_stub is a device driver used to read andwrite to the NVRAM on a target mode Fibre Channel Host BusAdapter. On Linux, it also prevents initiator mode drivers frombinding to the target mode fibre channel HBAs.

Started By: Device driver that is started by the operating systemon a reboot afternbftsrv_config -nbhbaon Linux and Solaris.On Linux, it is also started on all reboots after nbftsrv_config.

Stopped By: Device driver that is stopped by nbfdrv64 on Linuxand nbftsrv_config on Solaris.

Debug Log: The host operating system handles the logging for thedevice driver in the system messages log: /var/adm/messages(Solaris) or /var/log/messages (Linux).

ql2300_stub

On UNIX clients, the Tape ARchive program is a special versionof tar provided with NetBackup and used to restore images.

Started By: For each restore, bpbrm starts an instance of tar onthe client.

Stopped By: Completion of restore operation.

Debug Log: tar legacy log directory on the client.

tar

On Windows clients, the TAR32 program is a special version oftar provided with NetBackup and used to restore images.

Started By: For each restore, NetBackup starts an instance ofTAR32 on the client.

Stopped By: Completion of restore operation.

Debug Log: TAR legacy log directory on the client.

TAR32

681Backup and restore functional overviewNetBackup programs and daemons

Table A-4 NetBackup daemons and programs (continued)

DescriptionProgram/Daemon

On a Media Server that is enabled for SAN Client transfers usingfibre channel: windrvr6 is a kernel device driver used tocommunicate through the PCI bus to the target mode FibreChannel Host Bus Adapters.

Started By: Device driver that is started by the operating systemat boot (Solaris) or by nbfdrv64 (Linux).

Stopped By: Device driver that is stopped by the operating systemat shutdown.

Debug Log: The host operating system handles the logging in thesystem messages log log: /var/adm/messages (Solaris) or/var/log/messages (Linux).

windrvr6

NetBackup catalogsThe NetBackup catalogs contain the information that is used internally byNetBackup and reside in the/usr/openv/netbackup/dbdirectory on UNIX serversand in theinstall_path\NetBackup\dbdirectory on Windows NetBackup servers.

Note also that the /usr/openv/netbackup/db/class directory(install_path\NetBackup\db\class on Windows) has a subdirectory for eachNetBackuppolicy, that contains information about the policy.

Table A-5 describes the NetBackup catalogs.

Table A-5 NetBackup catalogs

ContentsDatabase

Configuration information. This database resides on the master serverand has three parts:

policy: Contains the information about each NetBackup policy.

config: Contains the information about global attributes, storageunits, and database backups.

altnames: Contains the information about client names for restores.

config

Backup and restore functional overviewNetBackup catalogs

682

Table A-5 NetBackup catalogs (continued)

ContentsDatabase

Error and status information about NetBackup operations. Thisdatabase resides on the master server and has two parts:

error: Contains the information that is recorded during backupoperations and used in the NetBackup reports.

failure_history: Contains the daily history of backup errors.

error

Information about the backup images and resides only on the masterserver. One of the files in the images directory is the file database.The file database is the one that NetBackup accesses when a userbrowses for files to restore.

images

Job information that is used by the NetBackup job monitor (UNIXNetBackup server) and activity monitor (Windows NetBackup server).The Jobs database is on the master server.

jobs

Media related information that is used by bptm. Also has an errorsfile that contains error history information for media and devices.

media

683Backup and restore functional overviewNetBackup catalogs

Backup and restore functional overviewNetBackup catalogs

684

Media and devicemanagement functionaldescription

This appendix includes the following topics:

■ Media and device management startup process

■ Media and device management process

■ Shared Storage option management process

■ Barcode operations

■ Media and device management components

Media and device management startup processMedia and device management processes are automatically initiated duringNetBackup startup. To start these processes manually, run bp.start_all (UNIX) orbpup (Windows). ltid automatically starts other daemons and programs asnecessary. The daemons should be running after initial startup.

See Figure B-1 on page 687.

In the case of robotic daemons, such as tl8d and tlhd, the associated robot mustalso be configured for the daemon to run. There are also additional ways to startand stop daemons.

See Table B-1 on page 694.

TL8, TLH, and TLD require following types of daemons:

BAppendix

Each host with a robotic drive attached musthave a robotic daemon. These daemonsprovide the interface between ltid and therobot or, if different drives within a robotcan attach to different hosts, the roboticdaemon communicates with arobotic-control daemon (see below).

robotic

Robotic-control daemons centralize thecontrol of robots when drives within a robotcan connect to different hosts. Arobotic-control daemon receives mount andunmount requests from the robotic daemonon the host to which the drive is attachedand then communicates these requests tothe robot.

robotic control

You must know the hosts involved in order to start all the daemons for a robot.

Media and device management functional descriptionMedia and device management startup process

686

Figure B-1 Starting media and device management

ltid

vmd avrd

AutomatedCartridge System

Tape Library 4mm

Tape Library 8mm

Tape Library DLT

Tape LibraryHalf-inch

Tape LibraryMultimedia

Tape StackerHalf-inch

Optical DiskLibrary

acsd

odld

tl4d

tl8d tl8cd

tldd tldcd

tlhd tlhcd

tlmd

tshd

To start the processes manually, enter:

On UNIX: /usr/openv/netbackup/bin/bp.start_all

On Windows: install_path \NetBackup\bin\bpup

acsel

acsssi

At system startup, the server automatically starts ltid ,which starts applicable robotic daemons.

Media and device management processWhen the media and device management daemons are running, NetBackup,Storage Migrator (UNIX only), Storage Migrator for Microsoft Exchange (Windowsonly), or users can request data storage or retrieval. The request is initially handledby the scheduling services.

See “Backup and archive processes” on page 634.

687Media and device management functional descriptionMedia and device management process

The resulting request to mount a device is passed from nbjm to nbrb, whichacquires the physical resources from nbemm (the Enterprise Media Managerservice).

If the backup requires media in a robot, ltid sends a mount request to the roboticdaemon that manages the drives in the robot that are configured on the local host.The robotic daemon then mounts the media, and sets a drive busy status in memoryshared by itself and ltid. Drive busy status also appears in the Device Monitor.

See Figure B-2 on page 689.

Assuming that the media is physically in the robot, the media is mounted and theoperation proceeds. If the media is not in the robot, nbrb creates a pending request,which appears as a pending request in the Device Monitor. An operator must theninsert the media in the robot and use the appropriate Device Monitor commandto resubmit the request so the mount request can occur.

A mount request is also issued if the media is for a nonrobotic (standalone) driveand the drive does not contain media that meets the criteria in the request. If therequest is from NetBackup and the drive does contain appropriate media, thenthat media is automatically assigned and the operation proceeds. More informationis available on NetBackup media selection for nonrobotic drives.

See the NetBackup Administrator’s Guide, Volume II.

Note: On UNIX systems, when a tape is being mounted, the drive_mount_notifyscript is called. This script is in the /usr/openv/volmgr/bin directory. Informationon the script can be found within the script itself. A similar script is called for theunmount process (drive_unmount_notify, in the same directory).

When a robotic volume is added or removed through the media access port, themedia management utility communicates with the appropriate robotic daemonto verify the volume location and/or barcode. The media management utility(through a library or command-line interface) also calls the robotic daemon forrobot inventory operations.

Figure B-2 shows an example of the media and device management process.

Media and device management functional descriptionMedia and device management process

688

Figure B-2 Media and device management example process

Device-management utility

Backup andarchive processes

EMMDatabase

Mount m

ediaID

User

bptm

Itid

nbjm

nbemm Media-managementutility

Devicemonitor

tl8d tl8cd

Tapelibrary TL8

Request tapemount

SDLT600 LT0-3

Roboticcontrol

Inventorybarcodes

or inject/eject

Non-roboticdrives

Shared Storage option management processShared Storage Option (SSO) is an extension to tape drive allocation andconfiguration for media and device management. SSO allows individual tape drives(stand-alone or in a robotic library) to be dynamically shared between multipleNetBackup media servers or SAN media servers.

See the NetBackup Shared Storage Guide.

The following shows the shared storage option management process in the orderpresented:

■ NetBackup, Storage Migrator, or users can initiate backups. nbjm makes amount request for the backup.

689Media and device management functional descriptionShared Storage option management process

■ nbrb tells the EMM server to obtain a drive for the backup.

■ nbrb tells the device allocator (DA) in the EMM server to stop scanning theselected drive.

■ nbemm tells the appropriate media server (the scan host for the selected drive)to stop scanning the drive. The stop scan request is carried out by means ofoprd, ltid, and avrd in the media server’s shared memory.

■ nbemm informs nbrb when scanning on the selected drive has stopped.

■ nbrb informs nbjm that the selected drive (A) is available for the backup.

■ nbjm conveys the mount request and drive selection to bptm, which proceedswith the backup. To protect the integrity of the write operation, bptm usesSCSI reservations.See “How NetBackup reserves drives” in theNetBackupAdministrator’sGuide,Volume II.

■ The mount-media operation is initiated.

■ bptm makes position checks on the drive to ensure that the drive has not beenrewound by another application. bptm also does the actual write to the tape.

■ When the backup is complete, nbjm tells nbrb to release resources.

■ nbrb de-allocates the drive in EMM.

■ EMM tells the scan host to resume scanning the drive. The scan request iscarried out by means of oprd, ltid, and avrd in the media server’s sharedmemory.

Figure B-3 illustrates the shared storage option management process.

Media and device management functional descriptionShared Storage option management process

690

Figure B-3 Media and device management process flow showing SSOcomponents

Device-management utility

Backup andarchive processes

EMMDatabase

User

bptm

nbjm nbemm/DA

Devicemonitor

Request tapemount

Shared drive A

ltid ltid

avrd

6.5 Media Server 1

Scan host for drive A

bptm

ltid ltid

6.5 Media Server 2

Scan host for drive B

avrd bptm

nbrb

Shared drive B

Note: Shaded area represents sharedmemory on the media server.

Stopscan

Barcode operationsBarcode reading is mainly a function of the robot hardware rather than mediaand device management. When a robot has a barcode reader, it scans any barcode

691Media and device management functional descriptionBarcode operations

that may be on a tape and stores the code in its internal memory. This associatesthe slot number and the barcode of the tape in that slot. NetBackup determinesthat association for its own use by interrogating the robot.

If a robot supports barcodes, NetBackup automatically compares a tape’s barcodeto what is in the EMM database as an extra measure of verification before mountingthe tape. A request for media that is in a robot that can read barcodes begins inthe same manner as other requests.

See Figure B-4 on page 693.

ltid includes the media ID and location information in a mount request to therobotic daemon for the robot that has the media ID. This request causes the roboticdaemon to query the robotic-control daemon or the robot for the barcode of thetape in the designated slot. (This is a preliminary check to see if the correct mediais in the slot.) The robot returns the barcode value it has in memory.

The robotic daemon compares this barcode with the value it received from ltidand takes one of the following actions:

■ If the barcodes don’t match, and the mount request is not for a NetBackupbackup job, the robotic daemon informs ltid and a pending action request(Misplaced Tape) appears in the Device Monitor. An operator must then insertthe correct tape in the slot.

■ If the barcodes don’t match and the mount request is for a NetBackup backupjob, the robotic daemon informs ltid and the mount request is canceled.NetBackup (bptm) then requests a new volume from nbjm and from EMM.

■ If the barcodes match, the robotic daemon requests the robot to move the tapeto a drive. The robot then mounts the tape. At the start of the operation, theapplication (for example, NetBackup) checks the media ID and if it also matcheswhat should be in this slot, the operation proceeds. For NetBackup, a wrongmedia ID results in a “media manager found wrong tape in drive” error(NetBackup status code 93).

Media and device management functional descriptionBarcode operations

692

Figure B-4 Barcode request

Device-management utility

EMMDatabase

User

Itid nbemm

Media-managementutility

tl8d tl8cd

Tape library TL8

Request media ID mount

vmd

NetBackup

Mount media ID

Robot inventoryrequest or inject/eject

2

BarcodeWhat isbarcode

Mounttape

1 3

Media and device management componentsThis topic shows the file and directory structure and the programs and daemonsassoicated with the media and device management.

Figure B-5 shows the file and directory structure for media and device managementon a UNIX server. A Windows NetBackup server has equivalent files and directoriesthat are located in the directory where NetBackup is installed (by default,C:\Program Files\VERITAS).

693Media and device management functional descriptionMedia and device management components

Figure B-5 Media and device management directories and files

/usr/openv/volmgr/debug/1

/usr/openv/volmgr/

NetBackup server

bin/ debug/1 misc/ vm.conf2help/

avrd/1

tpcommand/1robots/1

ltid/1 reqlib/1daemon/1

/usr/openv/volmgr/bin/

driver/ goodies/format/

1. Created by administrator to enable legacy debug logging.

2. Created by administrator or automatically by media management utilities.

NetBackup_DeviceConfig_Guide.tx

/vmscd

Table B-1 describes the directories and files that are of special interest.

Table B-1 Media and device management directories and files

ContentsFile or directory

Commands, scripts, programs, daemons, and filesrequired for media and device management. Thereare three subdirectories under bin.

driver: Contains SCSI drivers used on variousplatforms to control robotics.

format: Disk format information for opticalplatters on Solaris (SPARC only) platforms.

goodies: Contains vmconf script and scan utility.

bin

Legacy debug logs for the Volume Managerdaemon, vmd, and all requesters of vmd, ltid, anddevice configuration. The administrator mustcreate these directories for debug logging to occur.

debug

Help files used by media and device managementprograms. These files are in ASCII format.

help

Lock files and temporary files required by variouscomponents of media and device management.

misc

Media and device management functional descriptionMedia and device management components

694

Table B-1 Media and device management directories and files (continued)

ContentsFile or directory

Media and device management configurationoptions.

vm.conf

Table B-2 describes the media and device management programs and daemons.The explanations include what starts and stops the program or daemon, and thelog (if any) where it records its activities. On UNIX, all of the components discussedin this table reside under /usr/openv/volmgr/bin. On Windows, they reside underinstall_path\volmgr\bin.

Note:The following table contains references to the system log. This log is managedby syslog on UNIX (the facility is daemon). On Windows the Event Viewer managesthe system log (the log type is Application).

Table B-2 Media and device management daemons and programs

DescriptionProgram or daemon

The Automated Cartridge System daemon interfaces with theAutomated Cartridge System. It communicates with the serverthat controls the ACS robotics through the acsssi process (UNIX)or the STK Libattach Service (Windows).

Also, for UNIX, see the acsssi and acssel programs.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/ascd command.

Stopped By: Stopping ltid (or on UNIX, independently by findingthe PID (process id) and then using the kill command).

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included by adding VERBOSE to thevm.conf file. On UNIX, debug information is also included bystarting the daemon with the -v option: this option can also beused through ltid, or by putting VERBOSE in the vm.conf file.

acsd

Available only on UNIX.

See the NetBackup Device Configuration Guide.

acssel

Available only on UNIX.

See the NetBackup Device Configuration Guide.

acsssi

695Media and device management functional descriptionMedia and device management components

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

The automatic-volume-recognition daemon controls automaticvolume assignment and label scanning. This lets NetBackup readlabeled tape and optical disk volumes and to automatically assignthe associated removable media to requesting processes.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/avrd command).

StoppedBy: Stopping ltid, (or on UNIX, independently by findingthe PID (process id) and then using the kill command).

Debug Log: All errors are logged in the system log. Debuginformation is included by adding VERBOSE to the vm.conf file.On UNIX, debug information is also included by aborting avrd andstarting the daemon with the -v option.

avrd

The device demon (UNIX) or NetBackup Device Manager service(Windows) controls the reservation and assignment of tapes andoptical disks.

Started By: /usr/openv/volmgr/bin/ltid command on UNIX orStop/Restart Device Manager Service command in Media andDevice Management window on Windows.

Stopped By: /usr/openv/volmgr/bin/stopltid command on UNIXor Stop/Restart Device Manager Service command in the Mediaand Device Management window on Windows.

DebugLog: Errors are logged in the system log and ltid debug log.Debug information is included if the daemon is started with the-v option (available only on UNIX) or adding VERBOSE to thevm.conf file.

ltid

The Optical Disk Library daemon interfaces with the Optical DiskLibrary, communicating with the robotics through a SCSI interface.This library is not supported on Windows.

Started By: Starting ltid or independently by using the/usr/openv/volmgr/bin/odld command.

Stopped By: Stopping ltid or independently by finding the PID(process id) and then using the kill command.

Debug Log: All errors are logged in the system log. Debuginformation is included if the daemon is started with the -v option(either by itself or through ltid) or adding VERBOSE to the vm.conffile.

odld

Media and device management functional descriptionMedia and device management components

696

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

The Tape Library 4MM daemon is the interface between ltid andthe Tape Library 4MM and communicates with the roboticsthrough a SCSI interface.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tl4d command).

Stopped By: Stopping ltid (or on UNIX, independently by findingthe PID (process id) and then using the kill command).

Debug Log: All errors are logged in the system log. Debuginformation is included by adding VERBOSE to the vm.conf file.On UNIX, debug information is also included by starting thedaemon with the -v option (either by itself or through ltid).

tl4d

The Tape Library 8MM daemon provides the robotic control fora TL8 robot (Tape Library 8mm or Tape Stacker 8mm). The TapeLibrary 8MM daemon drives in the same TL8 robot may beattached to different hosts than the robotic control. tl8d is theinterface between the local ltid and the robotic control. If a hosthas a device path for a drive in a TL8 robot, then mount orunmount requests for that drive go first to the local ltid and thento the local tl8d (all on the same host). tl8d then forwards therequest to tl8cd on the host that is controlling the robot (could beon another host).

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tl8d command).

Stopped By: Stopping ltid (or on UNIX, independently by findingthe PID (process id) and then using the kill command.

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included by adding VERBOSE to thevm.conf file. On UNIX, debug information is also included bystarting the daemon with the -v option (either by itself or throughltid).

tl8d

697Media and device management functional descriptionMedia and device management components

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

The Tape Library 8MM Control daemon provides the roboticcontrol for a TL8 robot and communicates with the roboticsthrough a SCSI interface. tl8cd receives mount and unmountrequests from tl8d on the host to which the drive is attached andthen communicates these requests to the robot.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tl8cd command).

Stopped By: Stopping ltid or by using the tl8cd -t command.

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included by adding VERBOSE to thevm.conf file. On UNIX, debug information is also included bystarting the daemon with the -v option (either by itself or throughltid).

tl8cd

The Tape Library DLT daemon works in conjunction with tldcdto handle requests to TLD robots (Tape Library DLT and TapeStacker DLT). tldd provides the interface between the local ltidand the robotic control (tldcd) in the same manner as explainedpreviously for tl8d.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tldd command).

Stopped By: Stopping ltid (or on UNIX, independently by findingthe PID (process id) and then using the kill command).

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included by adding VERBOSE to thevm.conf file. On UNIX, debug information is also included bystarting the daemon with the -v option (either by itself or throughltid).

tldd

Media and device management functional descriptionMedia and device management components

698

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

The Tape Library DLT Control daemon provides robotic controlfor a TLD robot in the same manner as explained previously fortl8cd.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tldcd command).

StoppedBy: Using the tldcd -t command. Stopping ltid or by usingthe tldcd -t command.

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included by adding VERBOSE to thevm.conf file. On UNIX, debug information is also included bystarting the daemon with the -v option (either by itself or throughltid).

tldcd

The Tape Library Half-inch daemon works in conjunction withtlhcd to handle requests to TLH robots that are in an IBMAutomated Tape Library (ATL). tlhd provides the interface betweenthe local ltid and the robotic control (tlhcd) in the same manneras explained previously for tl8d.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tlhd command).

Stopped By: Stopping ltid (or on UNIX, independently by findingthe PID (process id) and then using the kill command).

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included by adding VERBOSE to thevm.conf file. On UNIX, debug information is also included bystarting the daemon with the -v option (either by itself or throughltid).

tlhd

699Media and device management functional descriptionMedia and device management components

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

The Tape Library Half-inch Control daemon provides roboticcontrol for a TLH robot that is in an IBM Automated Tape Library(ATL) in a similar manner to that which was explained previouslyfor tl8cd.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tlhcd command).

Stopped By: Stopping ltid or by using the tlhcd -t command.

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included if the daemon is started withthe -v option (either by itself or through ltid). The -v option isavailable only on UNIX. Also, add the VERBOSE option to thevm.conf file.

tlhcd

The Tape Library Multimedia daemon is the interface betweenltid and a TLM robot that is in an ADIC Distributed AML Server(DAS). This daemon communicates with the TLM robotics througha network API interface.

Started By: Starting ltid or independently by using the/usr/openv/volmgr/bin/tlmd command.

Stopped By: Stopping ltid or independently by finding the PID(process id) and then using the kill command.

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included if the daemon is started withthe -v option (either by itself or through ltid). The -v option isavailable only on UNIX. Also, add the VERBOSE option to thevm.conf file.

tlmd

Media and device management functional descriptionMedia and device management components

700

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

The Tape Library Multimedia daemon is the interface betweenltid and a TLM robot that is in an ADIC Distributed AML Server(DAS). This daemon communicates with the TLM robotics througha network API interface.

Started By: Starting ltid or independently by using the/usr/openv/volmgr/bin/tlmd command.

Stopped By: Stopping ltid or independently by finding the PID(process id) and then using the kill command.

Debug Log: Errors are logged in the system log and robots debuglog. Debug information is included if the daemon is started withthe -v option (either by itself or through ltid). The -v option isavailable only on UNIX. Also, add the VERBOSE option to thevm.conf file.

tpconfig

The Tape Stacker Half-inch daemon is the interface between ltidand the half-inch-cartridge stacker and communicates with therobotics through a SCSI interface. This robot is not supported onWindows.

StartedBy: Starting ltid (or on UNIX, independently by using the/usr/openv/volmgr/bin/tshd command).

Started By: tpconfig command.

Stopped By: Quit option from within the utility on UNIX. OnWindows, tpconfig is only a command-line interface that runs tocompletion (no quit option).

Debug Log: tpcommand debug logs.

tshd

The Volume Manager daemon (NetBackup Volume Manager serviceon Windows) allows remote administration and control of Mediaand Device Management. vmd provides a proxy to EMM for pre-6.0NetBackup servers.

StartedBy: Starting ltid (or on UNIX, independently by using theInitiate Media Manager Volume Daemon option in vmadm)

Stopped By: Terminate Media Manager Volume Daemon optionin vmadm).

DebugLog: System log and also a debug log if the daemon or reqlibdebug directories exist

vmd

701Media and device management functional descriptionMedia and device management components

Table B-2 Media and device management daemons and programs (continued)

DescriptionProgram or daemon

Available only on UNIX. An administrator utility with options forconfiguring and managing volumes under control of media anddevice management. It has a menu-driven, character-basedinterface that can be used from workstations that do not havegraphical display capabilities.

Started By: /usr/openv/volmgr/bin/vmadm command

Stopped By: Quit option from within the utility.

Debug Log: /usr/openv/volmgr/debug/reqlib

vmadm

The Media Manager Status Collector Daemon keeps the EMMserver database up-to-date with the actual status of drives attachedto 5.x servers.

Started By: the EMM server.

Stopped By: the EMM server.

Debug Log: /usr/openv/volmgr/debug/vmscd (UNIX),install_path\Volmgr\debug\vmscd (Windows)

vmscd

Media and device management functional descriptionMedia and device management components

702

Networks and hostnames

This appendix includes the following topics:

■ Background for troubleshooting

Background for troubleshootingIn a configuration with multiple networks and clients with more than onehostname, NetBackup administrators must configure the policy entries carefully.They must consider the network configuration (physical, hostnames and aliases,NIS/DNS, routing tables, and so on). If administrators want to direct backup andrestore data across specific network paths, they especially need to consider thesethings.

For a backup, NetBackup connects to the host name as configured in the policy.The operating system’s network code resolves this name and sends the connectionacross the network path that is defined by the system’s routing tables. The bp.conffile is not a factor making this decision.

For restores from the client, the client connects to the master server. For example,on a UNIX system, the master server is the first one named in the/usr/openv/netbackup/bp.conf file. On a Windows system, the master serveris specified on the Servertouseforbackupsandrestores drop-down of the SpecifyNetBackup Machines and Policy Type dialog box. To open this dialog, start theNetBackup Backup, Archive, and Restore interface and click Specify NetBackupMachinesandPolicyType on the File menu. The client’s network code that mapsthe server name to an IP address determines the network path to the server.

Upon receipt of the connection, the server determines the client’s configuredname from the peername of its connection to the server.

The peername is derived from the IP address of the connection. This means thatthe address must translate into a host name (using the gethostbyaddr()network

CAppendix

routine). This name is visible in the bprd debug log when a connection is made asin the line:

Connection from host peername ipaddress ...

The client’s configured name is then derived from the peername by querying thebpdbm process on UNIX systems. On Windows systems, you must query theNetBackup Database Manager service.

The bpdbm process compares the peername to a list of client names that aregenerated from the following:

■ All clients for which a backup has been attempted

■ All clients in all policies

The comparison is first a simple string comparison. The comparison is verifiedby comparing hostnames and aliases that are retrieved by using the networkfunction gethostbyname().

If none of the comparisons succeed, a more brute force method is used, whichcompares all names and aliases using gethostbyname().

The configured name is the first comparison that succeeds. Note that othercomparisons might also have succeeded if aliases or other "network names" areconfigured.

If the comparison fails, the client’s hostname as returned by the gethostname()

function on the client is used as the configured name. An example of a failedcomparison is when the client had changed its hostname but its new hostnameis not yet reflected in any policies.

These comparisons are logged in the bpdbm debug log if VERBOSE is set. You candetermine a client’s configured name by using the bpclntcmd command on theclient. For example:

# /usr/openv/netbackup/bin/bpclntcmd -pn (UNIX)

# install_path\NetBackup\bin\bpclntcmd -pn (Windows)

expecting response from server wind.abc.me.com

danr.abc.me.com danr 194.133.172.3 4823

Where the first output line identifies the server to which the request is directedand the second output line is the server’s response in the following order:

■ Peername of the connection to the server

■ Configured name of the client

■ IP address of the connection to the server

Networks and hostnamesBackground for troubleshooting

704

■ Port number that is used in the connection

When the client connects to the server, it sends the following three names to theserver:

■ browse client

■ requesting client

■ destination client

The browse client name is used to identify the client files to list or restore from.The user on the client can modify this name to restore files from another client.For example, on a Windows client, the user can change the client name by usingthe Backup, Archive, and Restore interface. (See the NetBackup online Help forinstructions). For this change to work, however, the administrator must also havemade a corresponding change on the server.

See the NetBackup Administrator’s Guide, Volume I.

The requesting client is the value from the gethostname() function on the client.

The destination client name is a factor only if an administrator pushes a restoreto a client from a server. For a user restore, the destination client and therequesting client are the same. For an administrator restore, the administratorcan specify a different name for the destination client.

By the time these names appear in the bprd debug log, the requesting client namehas been translated into the client’s configured name.

The name that used to connect back to the client to complete the restore is eitherthe client’s peername or its configured name. The type of restore request (forexample, from root on a server, from a client, to a different client, and so on)influences this action.

When you modify client names in NetBackup policies to accommodate specificnetwork paths, the administrator needs to consider:

■ The client name as configured on the client. For example, on UNIX the clientname is CLIENT_NAME in the client’s bp.conf file. On a Windows client, it is onthe General tab of the NetBackup Client Properties dialog box. To open thisdialog box, select NetBackup Client Properties from the File menu in theBackup, Archive, and Restore interface.

■ The client as currently named in the policy configuration.

■ Client backup and archive images that already exist as recorded in the imagesdirectory on the master server. On a UNIX or Linux server, the imagesdirectoryis /usr/openv/netbackup/db/. On a Windows NetBackup server, the images

directory is install_path\NetBackup\db\images.

705Networks and hostnamesBackground for troubleshooting

Any of these client names can require manual modification by the administratorif the following: a client has multiple network connections to the server andrestores from the client fail due to a connection-related problem.

On UNIX, the public domain program traceroute (not included with NetBackup)often can provide valuable information about a network’s configuration. Somesystem vendors include this program with their systems.

The master server may be unable to reply to client requests, if the Domain NameServices (DNS) are used and the following is true: the name that the client obtainsthrough itsgethostname() library (UNIX) orgethostbyname()network (Windows)function is unknown to the DNS on the master server, The client and the serverconfigurations can determine if this situation exists. gethostname() orgethostbyname()on the client may return an unqualified host name that the DNSon the master server cannot resolve.

Although you can reconfigure the client or the master server DNS hosts file, thissolution is not always desirable. For this reason, NetBackup provides a special fileon the master server. This file is as follows:

/usr/openv/netbackup/db/altnames/host.xlate (UNIX and Linux)

install_path\NetBackup\db\altnames\host.xlate (Windows)

You can create and edit this file to force the desired translation of NetBackupclient host names.

Each line in the host.xlate file has three elements: a numeric key and twohostnames. Each line is left-justified, and a space character separates each elementof the line.

key hostname_from_client client_as_known_by_server

The following describes the preceding variables:

■ key is a numeric value used by NetBackup to specify the cases where thetranslation is to be done. Currently this value must always be 0, which indicatesa configured name translation.

■ hostname_from_client is the value to translate. This value must correspondto the name that is obtained by the client’s gethostname() function and sentto the server in the request.

■ client_as_known_by_server is the name to substitute forhostname_from_clientwhen responding to requests. This name must be the name that is configuredin the NetBackup configuration on the master server. It must also be knownto the master server’s network services.

This following is an example:

Networks and hostnamesBackground for troubleshooting

706

0 danr danr.eng.aaa.com

When the master server receives a request for a configured client name (numerickey 0), the name danr is always replaced by the name danr.eng.aaa.com. Theproblem is resolved, assuming the following:

■ The client’s gethostname() function returns danr.

■ The master server’s network services gethostbyname() function did notrecognize the name danr.

■ The client was configured and named in the NetBackup configuration asdanr.eng.aaa.com and this name is also known to network services on themaster server.

707Networks and hostnamesBackground for troubleshooting

Networks and hostnamesBackground for troubleshooting

708

Robotic test utilities

This appendix includes the following topics:

■ About robotic test utilities

■ Robotic tests on UNIX

■ Robotic tests on Windows

About robotic test utilitiesEach of the robotic software packages includes a robotic test utility forcommunicating directly with robotic peripherals. The tests are for diagnosticpurposes and the only documentation is the online Help that you can view byentering a question mark (?) after starting the utility. Specify -h to display theusage message.

Note:Do not use the robotic test utilities when backups or restores are active. Thetests lock the robotic control path and prevent the corresponding robotic softwarefrom performing actions, such as loading and unloading media. If a mount isrequested, the corresponding robotic process times out and goes to the DOWNstate. This usually results in a media mount timeout. Also, be certain to quit theutility when your testing is complete.

Robotic tests on UNIXIf the robot has been configured (that is, added to the EMM database), start therobotic test utility by using the robtest command. This action saves time, sincerobotic and drive device paths are passed to the test utility automatically. Theprocedure is as follows:

To use the robtest command, do the following (in the order presented):

DAppendix

■ Execute the following command:

/usr/openv/volmgr/bin/robtest

The test utility menu appears.

■ Select a robot and press Enter.The test starts.

If the robot is not configured, you cannot use robtest and must execute thecommand that applies to the robot you test.

/usr/openv/volmgr/bin/acstest -r ACSLS_hostpath

for acstest to work on UNIX and Linux, acssel and acsssi mustbe running

ACS

/usr/openv/volmgr/bin/odltest -r roboticpathODL

/usr/openv/volmgr/bin/tl4test -r roboticpathTL4

/usr/openv/volmgr/bin/tl8test -r roboticpathTL8

/usr/openv/volmgr/bin/tldtest -r roboticpathTLD

/usr/openv/volmgr/bin/tlhtest -r robotic_library_pathTLH

/usr/openv/volmgr/bin/tlmtest -r DAS_hostTLM

/usr/openv/volmgr/bin/tshtest -r roboticpathTSH

More information on ACS, TLH, and TLM robotic control is available.

See the NetBackup Device Configuration Guide.

In the previous list of commands, roboticpath is the full path to the device file forthe robotic control (SCSI). You can review the section for your platform to findthe appropriate value for roboticpath.

An optional parameter specifies the device file path for the drives so that thisutility can unload the drives using the SCSI interface.

Robotic tests on WindowsIf the robot has been configured (that is, added to the EMM database), start therobotic test utility by using the robtest command. This action saves time, sincerobotic and drive device paths are passed to the test utility automatically.

To use the robtest command, do the following (in the order presented):

Robotic test utilitiesRobotic tests on Windows

710

■ Execute the following command:

install_path\Volmgr\bin\robtest.exe

The test utility menu appears.

■ Select a robot and press Enter.The test starts.

Note: If the robot is not configured, you cannot use robtest and must execute thecommand that applies to the robot you are testing (see following list).

install_path\Volmgr\bin\acstest -r ACSLS_HOSTACS

install_path\Volmgr\bin\tl4test -r roboticpathTL4

install_path\Volmgr\bin\tl8test -r roboticpathTL8

install_path\Volmgr\bin\tldtest -r roboticpathTLD

install_path\Volmgr\bin\tlhtest -r

robotic_library_name

TLH

install_path\Volmgr\bin\tlmtest -r DAS_HostnameTLM

More information on ACS, TLH, and TLM robotic control is available.

See the NetBackup Device Configuration Guide.

In the previous list of commands, roboticpath is the full path to the device file forthe robotic control (SCSI). You can review the section for your platform to findthe appropriate value for roboticpath.

An optional parameter specifies the device file path for the drives so that thisutility can unload the drives using the SCSI interface.

Usage is:

install_path <-p port -b bus -t target -l lan | -r

roboticpath>

where: roboticpath is the changer name (e.g., Changer0).

711Robotic test utilitiesRobotic tests on Windows

Robotic test utilitiesRobotic tests on Windows

712

Aacssel, description 695acsssi, description 695acstest 711Adaptive Server Anywhere 63admin log 104admincmd

directory 668administration interface

activity logging 127errors 125

AdvancedDisk 575, 582All Log Entries report 84Allow multiple data streams 173Alternate client restores

host.xlate file 706Alternate Read Server 220altnames file 682application server status codes (Java interface) 125archiving

for NBCC 149for nbsu 140

asc value 255ascd, description 695ascq value 255Auth User

for PBX 69auto-configuration problems 30avrd, description 696

Bbackup

NetBackup catalogs 652process

files 634multiplexing 640NetWare clients 648Windows clients 647

process overview 637, 645snapshot overview 641synthetic processes 649

backup (continued)UNIX clients 635

Backup Status report 84Bare Metal Restore 572, 575, 588base NetBackup license key 179bin

Media and Device Management 694UNIX client 667–668

BP 662bp

description 670log 119UNIX client log 116

bp.conffile 636

UNIX client/server 668SERVER entries 73

bp.kill_all 70, 72, 177BP.NLM 648, 670bp.start_all 72, 177bpadm

description 670bparchive

description 670log 116, 119

bpbackupdescription 671log 116, 119

bpbackup log 119BPBACKUP_POLICY 636BPBACKUP_SCHED 636bpbackupdb and catalog backup 210bpbkar

description 671log 116, 119

bpbkar and VxFS_Checkpoint 244bpbkar log 119BPBKAR32 647, 671bpbrm 643

description 671bpbrm log 104BPCD 662

Index

bpcddescription 672server log 104UNIX client log 116, 119

BPCD.NLM 672BPCDW32.EXE 672bpdbjobs

description 672bpdbjobs log 104bpdbm

description 673bpdbm log 104bpdm

description 673bpdm log 104bpdown command 71–72, 584, 587bperror command 155bpfis 643, 673bphdb

description 673log 116

BPINETD 647, 661bpinetd log 119bpinetd.log 119bpjava-msvc 674bpjava-msvc log 105, 127bpjava-usvc log 127bplist

description 674log 116, 120

bplist log 120bpmount

log 116bpmount log 120bporaexp log 116bporaexp64 log 116bporaimp log 116bporaimp64 log 116bppfi log on client 248bpps 24bprd

description 675bprd log 105bprecover 229bprestore

description 675log 116, 120

bprestore log 120

bpschedsee also nbpem 678

bpsrvlog 120

bpsrv log 120BPSVR.NLM 675bpsynth 650BPSYS.EXE 675bptm

description 676bptm log 105bptpcinfo 78bpup command 72, 177, 584, 587bundling

NBCC output 149nbsu output 140

Ccache

partition 173catalog backup 652checkpoint

removing 244class database file 682client

NetBackupconfigured name 704debug logs. SeeUNIX clients. SeeWindows

and NetWare clientsinstallation problems 28multiple hostnames 703peername 704software location. See UNIX clientstesting configuration 34, 38

Client Backups report 84Client Properties dialog 62client, NetBackup

Windows disk recovery 588clone (mirror

removing) 245–246CommandCentral Storage 75communications problems

PC clients 46UNIX clients 40

compressionfor NBCC 149for nbsu 140

compression device 33config file 682

Index714

configuration database 682configuration device file does not exist 33configuration problems 28

Ddaemons

robotic 685robotic control 685

database backup (see catalog backup) 652database extension 633DAYS_TO_KEEP_LOGS 107DAYS_TO_KEEP_LOGS vm.conf setting 110db directory

NetBackup 667–668debug level 118, 122, 128debug logs 85, 127

analysis utilities 131NetBackup 694vmd 107, 694

debug.properties file 127debugging

NBCC 149nbsu 142

define the problem 13device configuration problems 30Device Configuration Wizard 583directory structure

Media and Device Management 693disk full 62disk recovery

Windows client 588disk space

for logs files 100drive

drive limit exceeded 32type not determined 33

drive_mount_notify script 688drive_unmount_notify script 688driver directory 694drives

too many 31duplex mode and performance 72

EE-mail 574EMM server 635enable debug logging 107Enable Robust Logging 112

Enable robust logging 111Enterprise Media Manager 580Enterprise Media Manager (EMM) 635error codes (see status codes) 156error database 683evaluation license key 179Event viewer logging option 122eventlog 123

file entries 123exception errors in Java admin interface 125expired license key 179

Ffailure_history file 683fibre channel 644file database 683file list

symbolic link 241file pathname (max length) 157files

archive process 634backup process 634restore process 654

format directory 694frozen image

sourcefor symbolic link 241

fsckptadm command 244FSM 644FT Service Manager 644full disk 62full duplex mode 72functional overview

introduction 633Media and Device Management

device management 687directories and files 693volume management 687

NetBackupbackup and archive 634restores 654startup 634

GGlobal Logging Level 112Global logging level 91, 93goodies

directory 668

715Index

goodies directory 694

HHalf duplex and poor performance 72help files

Media and Device Management 694UNIX client 668

host name entrieschecking 49

Host Properties 61host.xlate file 706hostID

unified logging 87

IIDR 581, 588ifconfig

for checking NIC duplex mode 73images database 683images on Media report 84inetd 27Information E-mail 574installation

Linux 27installation problems 27Intelligent Disaster Recovery (IDR) 581, 588ipconfig

for checking NIC duplex mode 73

JJava interface

debug logging 127troubleshooting background 125

jbpSAoverview 676

job ID search in unified logs 96jobs

queued for long periods 62jobs database 683

KKeep logs For setting 94Keep Logs setting 109key value 255

Llegacy logging 103

client logs 115configuring rotation 111controlling size of 109directories 104file name format 111locations 103PC clients 118rotation of 109

levels for logging 91libsfr.so file 161license key 179license problems 31–32links (in file list) 241Linux 27local system account 240log (bppfi) 248log analysis utilities

debug logs 131how to run 133installation 132limitations 133output format 132

Log levelWindows and NetWare clients 118, 122

loggingchanging location of 85levels 91see legacy logging 103setting level for clients 118setting level on PC clients 122synthetic backup 113VxUL (see unified logging) 85

logsactivity

see debug 85debug

enabling detailed 127introduction 85

event viewer logging option 122file retention 94overview[Logs

aaa] 81PC client activity

bp 119bparchive 119bpbackup 119bpbkar 119

Index716

logs (continued)PC client activity (continued)

bpcd 119bpinetd 119bplist 120bpmount 120bprestore 120bpsrv 120tar 120user_ops 121

reportsNetBackup 83

server activityacssi 107admin 104bpbrm 104bpcd 104bpdbjobs 104bpdbm 104bpdm 104bpjava-susvc 105bprd 105bpsynth 105bptm 105–106daemon 107ltid 107nbjm 88nbpem 88nbrb 88reqlib 108robots 108tpcommand 108

setting retention period 107, 109system 85UNIX client activity

bp 116bparchive 116bpbackup 116bpbkar 116bpcd 116bphdb 116bpjava-msvc 105bplist 116bpmount 116bprestore 116obackup_tape 117tar 117user_ops 117

user progress 84

logs directoryUNIX client/server 669

ltid 113ltid, description 696

Mmaster server

test procedure 34, 38maximum pathname length 157MaxLogFileSizeKB 98–100, 111media database 683Media Log Entries report 84media server

test procedure 38message

finding message text from status code 155messages

NetBackup 397messages (see status codes) 156mirror (VxVM snapshot) 242mirror snapshot (removing) 245–246misc file 694mklogdir.bat 104moving log locations 85multiple data streams option 173multiplexed backups 640multiplexing 172

Nname format

legacy logging 111NB_dbsrv daemon 63NBCC

archiving and compression 149does the following 143introduction 143location of 144nbcc-info.txt file 150Notes on running 149output 148progress display 144Server aliases file 147troubleshooting 149when to use 144

nbcc-info.txt file 150nbdb_move 583nbemm 24, 635, 677nbfdrv64 677

717Index

nbftclnt 115, 118, 644, 646, 660, 677and bp.conf 74

nbftsrvr 644, 646, 660, 678nbjm 25, 88, 635, 643, 650, 678NBNWNT 648, 662NBNWNT.EXE 678nbpem 25, 88, 634–635, 643, 650, 678nbproxy 679nbrb 24, 63, 88, 635, 678–679nbrmms 680nbstserv 679nbsu

and status codes 141archiving and compression 140bundling 140creating xml output file 141introduction 137location of 137nbsu_info.txt file 143output files 139progress display 138troubleshooting 142when to use 137

nbsu_info.txt file 143NBWIN 647, 661NBWIN.EXE 680ndmpagent

overview 679NearStore 651NetBackup

if unresponsive 62product ID 87

NetBackup Administration Consoledebug logging 127errors 125

NetBackup Client Service 240start and stop 26

NetBackup consistency checksee NBCC 143

NetBackup Database Manager servicestart and stop 26

NetBackup Device Manager servicestart and stop 26

NetBackup Enterprise Media Manager servicestart and stop 26

NetBackup Job Manager servicestart and stop 26

NetBackup Policy Execution Manager servicestart and stop 26

NetBackup Request Manager servicestart and stop 26

NetBackup Resource Broker servicestart and stop 26

NetBackup Status Collection daemon.. See vmscdNetBackup Support Utility

see nbsu 137NetBackup Volume Manager service

start and stop 26network connections

multiple 703network daemon (vnetd) 106network interface cards 72network problems

PC clients 46UNIX clients 40

NIC cards and full duplex 72Novell

values affecting restore 175–176NumberOfFiles 100NumberOfLogFiles 99, 111

Oobackup_tape log 117odld, description 696odltest 710off-host backup 78OpenStorage 258, 575, 582operating system errors 126originator IDs

list of 88originatorID

unified logging 87

Ppass-thru not supported 32patch

troubleshooting 161patches (installing during recovery) 590pathname length 157PBX

Auth User 69logging 69Secure Mode 69–70starting 68starting/stopping 71troubleshooting 67

pbx_exchange 68, 680

Index718

pbxcfg 68preliminary troubleshooting procedure 23Private Branch Exchange (PBX) 67problems report 84procedures

recoveryWindows client disk 588

troubleshootingcommunications problems 40host names and services 49installation and configuration 27introduction 21master server and clients 34media server and clients 38preliminary 23

processes (see functional overview) 633product ID for NetBackup 87productID

unified logging 87progress logs

user 84

Qql2300_stub 681query string 128queued jobs 62

Rraw partitions

backup process 634restore process 654

recording information 15recovery procedures

Windows client disk 588RedHat 27relational database 63removing a snapshot checkpoint 244removing a snapshot clone 245–246reports

NetBackup 83reqlib directory 109restore

problem with sparse file 186restore process 654

NetWare client 662Windows 2000 client 661

restoringNAS_Snapshot 240

retentionof logs 94

robotdrive number unknown 32robot limit exceeded 32type not determined 31unknown 32

robot drive selection 688robotic control daemons 686robotic daemons 686robotic test utility 709

acstest 711odltest 710tl4test 710–711tl8test 710–711tldtest 710–711tlhtest 711tshtest 710

robtest 709–710robust file logging 97RolloverMode 99rotation

legacy logging 109of logs 93unified logging 87

SSAN Client 644SAN client

and bp.conf 74SANPoint Control 75Secure Mode

for PBX 69serialization problems 30server

installation problems 27NetBackup debug logs 103test procedure for master 34, 38test procedure for media server 38

SERVER entriesbp.conf 73

services entrieschecking 49

SharedDisk 75, 575, 582slots

too many 31slow performance and NIC cards 72snaplist command 243snapoff command 244

719Index

snapshotbackup process overview 642cache partition 173mirror (VxVM) 242removing 245–246stale 243

Snapshot Clientpathname length 157

software versiondetermining

Macintosh clients 174NetWare nontarget clients 174NetWare target clients 174UNIX client/server 669UNIX servers 173Windows clients 174Windows servers 173

sparse files (restore problem) 186stale snapshots 243starting NetBackup processes 72, 177startup

NetBackup 634status code

finding message from 155status codes

and nbsu 141NetBackup

sorted by code 156sorted by message 397

Status Collection Daemon 109stderr 125stdout 125stopping NetBackup processes 70, 72, 177storage units 74SuSE 27symbolic links 241synthetic backup 649

logs 113syslogd 85, 108system logs 85

Ttar

log 120log files 103NetBackup 681

TAR32 661test utility

robotic 709

third-party copy 255and multiplexing 172

tl4d, description 697tl4test 710–711tl8cd, description 698tl8d, description 697tl8test 710–711tldcd, description 699tldd, description 698tldtest 710–711tlhcd, description 700tlhd, description 699tlhtest 711tlmd, description 700tpautoconf 108, 494, 579tpconfig 108tpconfig, overview 701traceroute 706troubleshooting procedure

communication problemsPC clients 46UNIX clients 40

generalintroduction 33master server and clients 34, 38media server and clients 38

host name and services entries 49installation 27preliminary 23

try file 114tshd, overview 701tshtest 710

Uunavailable 74unified logging 85

changing location of 85client logs 115command examples 94configuring settings 97controlling disk space usage 100controlling number of log files 100controlling size of 98deleting logs 97file name format 86file rotation 93format of files 95listing settings 99location 85

Index720

unified logging (continued)message types 86NetBackup product ID 87PC clients 118processes using 88retention 94setting level on PC clients 122settings levels 91submitting to support 102tar log files 103viewing 95

upload directory 103user-directed backups 636user_ops log 106, 117, 121utility

robotic test 709

VVERBOSE 113verbose flag 113VERBOSE level 93Veritas Volume Manager 242vm.conf 107, 113vm.conf file 695vmadm, overview 702vmd 107

debug logging 107overview 701

vmscd 109logging 108

vmscd, overview 702vnetd log 106Volume Configuration Wizard 584vxassist command 242, 247VxFS_Checkpoint snapshot 244vxlogcfg 86, 111vxlogcfg command 93, 97, 99, 111vxlogmgr command 96, 100vxlogview command 95

query string overview 128with job ID option 96

vxpbx_exchanged 71vxprint command 247VxUL logging

see unified logging 85vxvm frozen image method 242vxvol command 242

WWindows open file backup 642windrvr6 682

Xxinetd 27XML 116xml

for nbsu 141

721Index


Recommended