VERITAS NetBackup 3.
Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Resolve Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 To Resolve Common Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 To Resolve Device Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 General Test and Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 To Test Master Server and Clients . . . . . . . . . . . . . . . . . . .
Activity Logs on Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Activity Logs on UNIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Activity Logs on PC Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Activity Logs on Windows and Netware Clients . . . . . . . . . . . . . . . . . . . . . . . . . 66 Activity Logs on Macintosh Clients . . . . .
Identifying the Most Recent Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Example 1: List by Using a Raw Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Example 2: List by Using a Media Manager Controlled Drive . . . . . . . . . . . . . 213 Example 3: List Disk Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Example 4: Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Media Manager Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Startup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Media and Device Management Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Barcode Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii NetBackup Troubleshooting Guide - UNIX
Preface This guide explains how to isolate and resolve problems encountered when installing, configuring, or using VERITAS NetBackup™ for UNIX. This publication refers to VERITAS NetBackup as NetBackup. Audience This guide is intended primarily for the system administrator who is responsible for installing, configuring, and managing NetBackup. The system administrator is assumed to have a good working knowledge of both NetBackup and UNIX.
Related Manuals ◆ Appendix C, “Robotic Test Utilities,” explains how to start the tests that are included with the robotic software. Following the appendixes is a glossary of NetBackup terms. Related Manuals Refer to the NetBackup Release Notes for a complete list of NetBackup manuals. Conventions The following explains typographical and other conventions used in this guide. Type Style Table 1. Typographic Conventions Typeface Usage Bold fixed width Input. For example, type cd to change directories.
Getting Help Key Combinations Some keyboard command sequences use two or more keys at the same time. For example, you may have to hold down the Ctrl key before you press another key. When this type of command is referenced, the keys are connected by plus signs. For example: Press Ctrl+t Command Usage The following conventions are frequently used in the synopsis of command usage. brackets [ ] The enclosed command line component is optional.
Getting Help xii NetBackup Troubleshooting Guide - UNIX
1 Introduction This chapter explains the basic steps to take if you encounter a problem while using NetBackup. Other chapters provide more specific information. Note The term media server, as distinct from master server or server, does not apply to the NetBackup BusinesServer product. When troubleshooting a BusinesServer installation, please ignore any references to media server in this guide. Define the Problem The first step in troubleshooting is to define the problem.
Record All Information Some questions to ask here are: ◆ What operation was being attempted? ◆ What method were you using? For example, there is more than one way to install software on a client. There is also more than one possible interface to use for many operations and some operations can even be performed with a script.
Record All Information ◆ 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 device information, such as the types of robots and drives along with Media Manager and system configuration information. ◆ Software patches to the products that were installed. ◆ Service packs and hotfixes that were installed (Windows NT/2000).
Troubleshooting the Problem Troubleshooting the Problem After defining the problem, use the information in the other chapters of this manual to try and correct it. ◆ When you have a status code or message, proceed directly to Chapter 4 and try the corrective actions recommended there. ◆ When you do not see a status code or message, or the actions in Chapter 4 do not solve the problem, try the troubleshooting procedures in Chapter 2.
Problem Report Information Problem Report Information General Information Date: _________________________ Servers (master and media): Platform Types and Host Names OS Levels Product Version and Patch Levels OS Levels Product Version and Patch Levels Clients: Platform Types and Host Names What were you attempting when the problem occurred? (for example, a backup on a Windows NT/2000 client) ______________________________________________________________________ _________________________________________
Problem Report Information Did this occur during or shortly after any of the following: _____ Initial Installation _____ Configuration change (explain) _____ System change or problem (explain) _____ Have you seen the problem before: (if so, what did you do that time) Logs or other failure data you have saved: _____ All log entries report _____ Media Manager debug logs _____ NetBackup activity logs _____ System logs (UNIX) _____ Event Viewer Application logs (Windows NT/2000) Can you communicate with us thr
Problem Report Information Follow these steps to get debug data for VERITAS 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. This is especially true in the Activity Monitor and Reports applications. So, wait for several minutes before assuming the operation is hung. If there is no response within several minutes, execute /usr/openv/java/get_trace under the account where you started the Java application.
Problem Report Information 8 NetBackup Troubleshooting Guide - UNIX
2 Troubleshooting Procedures This chapter has procedures for finding the cause of NetBackup errors. These procedures are general in nature and do not attempt to cover every problem that could occur. They do, however, recommend methods that usually result in successful problem resolution. When performing these procedures, try each step in sequence. If you have already performed the action or it does not apply, skip to the next step. If it branches you to another chapter, use the solutions suggested there.
Preliminary Troubleshooting a. Use the All Log Entries report and check for NetBackup errors for the appropriate time period. This report can show the context in which the error occurred and can often provide specific information that is useful when the status 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.
Preliminary Troubleshooting ◆ On the NetBackup master or media server, the partition where the NetBackup (or Media Manager) 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. On UNIX, use the df command to view disk partition information. On Windows NT/2000, use Disk Manager or Explorer. 5.
Preliminary Troubleshooting a. Use the NetBackup Activity Monitor, or the Services application in the Windows NT/2000 Control Panel, to start the following services if they are not running: Note To start all of them, execute install_path\NetBackup\bin\bpup.cmd.
Troubleshooting Installation and Configuration Problems Troubleshooting Installation and Configuration Problems To Resolve Installation Problems 1.
Troubleshooting Installation and Configuration 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 Robot Number 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 Installation and Configuration Problems a. Check the All Log Entries report for NetBackup errors for the appropriate time period. This report can show the context in which the error occurred and can often have specific information that is useful when the error 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.
Troubleshooting Installation and Configuration Problems Message: Robot does not support serialization Explanation: The robot does not return its serial number or the serial numbers of the drives contained within it. Note that some manufacturers do not support serial numbers. Although automatic device configuration will not function optimally, the robot and/or drives can be operated without serial numbers.
Troubleshooting Installation and Configuration Problems Recommended Action: Ask the manufacturer for a newer firmware version that returns serial numbers (if available), or operate the drive/robot without serial numbers. Message: Robot drive number is unknown Explanation: Either the drive or robot is not returning a serial number. Note that some manufacturers do not support serial numbers.
General Test and Troubleshooting Procedures Explanation: A device has been detected without the corresponding device file necessary to configure that device. Recommended Action: Refer to the chapter for your system type in the Media Manager Device Configuration Guide - UNIX for information on creating device files. Message: Unable to determine drive type Explanation: The drive is not recognized by NetBackup BusinesServer. The drive cannot be auto-configured.
General Test and Troubleshooting Procedures 3. Verify that the NetBackup daemons are running on the master server: ◆ To check the daemons on a UNIX system, execute: /usr/openv/netbackup/bin/bpps -a ◆ To check the services on a Windows NT/2000 system, use the NetBackup Activity Monitor or the Services application in the Windows NT/2000 Control Panel. 4. Start a manual backup of a class by using the manual backup option in the NetBackup administration interface. Then, restore the backup.
General Test and Troubleshooting Procedures 5. If you previously configured a nonrobotic drive and your system includes a robot, change your test class now to specify a robot. Add a volume to the robot. The volume must be in the NetBackup volume pool on the volume database host for the robot. Repeat this procedure starting with step 3, but this time for the robot. This verifies that Media Manager can find the volume, mount it, and use the robotic drive.
General Test and Troubleshooting Procedures 8. Reconfigure your test class to name a client that is located elsewhere in the network. Use a storage unit and media that has been verified in previous steps. If necessary, install the NetBackup client software. 9. Create activity log directories for the processes listed below. Chapter 3 explains which logs apply to specific client types.
General Test and Troubleshooting Procedures 1. Enable appropriate activity and debug logs on the servers (see Chapter 3). If you are uncertain which logs apply, enable them all until you solve the problem. Delete the activity log directories when you have resolved the problem. 2. Configure a test class with a user schedule (set the backup window to be open while you are testing). ◆ Name the media server as the client and a storage unit that is on the media server (preferably a nonrobotic drive).
General Test and Troubleshooting Procedures ◆ On a Windows NT/2000 server, the Event Viewer Application log ◆ vmd debug logs See the vendor manuals for information on hardware failures. If you are using a robot and this is an initial configuration, verify that the robotic drive is configured correctly. In particular, verify that: ◆ The same robot number is used both in the Media Manager and storage unit configurations. ◆ Each robot has a unique robot number.
General Test and Troubleshooting Procedures 7. When all clients and storage units are working, test the remaining classes and schedules that use storage units on the media server. If a scheduled backup fails, check the All Log Entries report for errors, then follow the actions suggested in Chapter 4. Resolving Network Communication Problems The following procedure is for resolving communications problems, such as those associated with status codes 54, 57, and 58.
General Test and Troubleshooting Procedures 2. Verify basic network connectivity between client and server by trying to ping the client from the server. ping clientname Where clientname is the name of the client as configured in the NetBackup class configuration, /etc/hosts, and also in NIS and DNS (if applicable). For example, to ping a client 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.
General Test and Troubleshooting Procedures ◆ /etc/services (or applicable NIS file) does not have the correct bpcd entry. The correct /etc services entry is: bpcd ◆ 13782/tcp bpcd /etc/inetd.conf (or applicable NIS or DNS file) does not have the correct bpcd entry. The correct /etc/inetd.conf entry is: bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd ◆ /etc/inetd.conf was changed but was not reread.
General Test and Troubleshooting Procedures In this example, telnet can establish a connection to the client ant. ◆ If the telnet succeeds, then inetd on the client is configured correctly and is able to pass its connection to bpcd and NetBackup should also be able to establish a connection. ◆ If telnet doesn’t work, ensure that the inetd.conf file and /etc/services files on both the server and client have correct and matching entries.
General Test and Troubleshooting Procedures Note We suggest that you not change the port number for bpcd or other NetBackup services. Do so only if there is no alternative; and then, remember that all NetBackup servers and clients in the configuration must use this new port assignment. ◆ If there is a process other than bpcd using the port, try rebooting the client to clear the problem.
General Test and Troubleshooting Procedures 2. If this is a new client, verify the client and server names in your NetBackup configuration as explained in “Verifying Host Names and Services Entries” on page 32. 3. Verify basic network connectivity between client and server by pinging from the server to the client and from the client to the server.
General Test and Troubleshooting Procedures c. Verify that the same NetBackup client Service (bpcd) port number is specified on both the NetBackup client and server (by default, 13782). ◆ On Microsoft Windows, check the NetBackup Client Service Port number on the Network tab in the NetBackup Configuration dialog box. To display this dialog, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu.
General Test and Troubleshooting Procedures a. Ensure that NetBackUpListen and NetBackupBPCD are in the Extensions folder. b. Check log.mmddyy in the Preferences:NetBackup:Logs:inetd folder to see if NetBackUpListen is running and if it reported any errors. c. Check log.mmddyy in the Preferences:NetBackup:Logs:bpcd folder to see if NetBackupBPCD was started and if it reported any errors. d. If NetBackUpListen or NetBackupBPCD are not running, try rebooting the Macintosh.
General Test and Troubleshooting Procedures 7. Verify that the hosts file or its equivalent contains the NetBackup server name. On UNIX and Windows clients, the hosts files are: ◆ %SystemRoot%\system32\drivers\etc\hosts (Windows NT/2000) ◆ C:\Windows\hosts (Windows 98 or 95) ◆ NetWare clients: SYS:etc\hosts ◆ /etc/hosts (UNIX) 8. Verify client-to-server connectability by using ping or its equivalent from the client (step 3 verified the server-to-client connection). 9.
General Test and Troubleshooting Procedures start the Backup, Archive, and Restore interface on the client. For the General tab, click Configure on the Actions menu; for Servers tab, click Specify NetBackup Machines on the Actions menu. ◆ On the Servers tab, ensure that there is a server entry for the master server and each media server. If you add or modify SERVER entries on the master server, stop and restart bprd and bpdbm.
General Test and Troubleshooting Procedures Pay particular attention to requirements for host.xlate file entries. 2. Verify that each server and client has the required entries for NetBackup reserved port numbers. Note The examples following this procedure show the default port numbers. Do not change NetBackup port assignments unless it is absolutely necessary in order to resolve conflicts with other applications. If you do change them, do so on all NetBackup clients and servers.
General Test and Troubleshooting Procedures c. On Macintosh clients, check the mac.conf file in the NetBackup folder in the Preferences folder to ensure that it has the correct portnum and bprdport entries. 3. On UNIX servers and clients, check the /etc/inetd.conf file to ensure that it has the following entry: bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd 4. On Windows NT/2000 servers and clients, verify that the NetBackup Client service is running. 5.
General Test and Troubleshooting Procedures bpclntcmd options that are useful for testing the functionality of the host name and IP address resolution are -ip, -hn, -sv and -pn. The following topics explain each of these options: bpclntcmd -ip IP_Address The -ip option allows you to specify an IP address. bpclntcmd uses gethostbyaddr() on the NetBackup node and gethostbyaddr() returns the host name with the IP address as defined in the node’s DNS, WINS, NIS, or local hosts file entries.
General Test and Troubleshooting Procedures ◆ expecting response from server rabbit.friendlyanimals.com is the master server entry from the server list on the client. ◆ dove.friendlyanimals.com is the connection name (peername) returned by the master server. The master server obtained this name through gethostbyaddress(). ◆ dove is the client name configured in the NetBackup class client list. ◆ 123.145.167.3 is the IP address of the client connection at the master server.
General Test and Troubleshooting Procedures Example 1: UNIX Master Server and Client UNIX Master Server jupiter Ethernet mars UNIX Client Class Client List jupiter mars usr/openv/netbackup/bp.conf usr/openv/netbackup/bp.conf SERVER=jupiter SERVER=jupiter CLIENT_NAME=jupiter CLIENT_NAME=mars /etc/inetd.conf /etc/inetd.conf bpcd ... (see note 1) bpcd ...
General Test and Troubleshooting Procedures UNIX Example 2: Master and Media Servers The network in this example (see the next figure) is the same as the previous one except that it includes a UNIX NetBackup media server named saturn. The difference to note is the addition of a SERVER entry for saturn in the bp.conf files on all the systems. This entry is second, beneath the one for the master server jupiter.
General Test and Troubleshooting Procedures Example 2: UNIX Master and Media Servers UNIX Master Server UNIX Media Server jupiter saturn Ethernet mars Class Client List jupiter mars saturn usr/openv/netbackup/bp.conf SERVER=jupiter SERVER=saturn CLIENT_NAME=jupiter usr/openv/netbackup/bp.conf SERVER=jupiter SERVER=saturn CLIENT_NAME=mars /etc/inetd.conf /etc/inetd.conf bpcd ... (see note 1) bpcd ... bpcd (see note 1) UNIX Client usr/openv/netbackup/bp.
General Test and Troubleshooting Procedures UNIX Example 3: Windows, NetWare, and Macintosh Clients The network in this example shows a NetBackup master server with PC clients. As used here, PC client refers to Windows, NetWare, and Macintosh clients. Note the following about this configuration: ◆ The configuration does not include UNIX clients but it could. ◆ Server configuration is the same as it is for UNIX clients. ◆ These specific clients do not have inetd.
General Test and Troubleshooting Procedures Example 3: PC Clients UNIX Master Server jupiter pluto Macintosh Client Ethernet NetWare Target Client Windows Client mars saturn Preferences Folder NetBackup Folder Class Client List jupiter mars saturn pluto bp.conf SERVER=jupiter CLIENT_NAME=pluto bp.ini usr/openv/netbackup/bp.conf SERVER=jupiter CLIENT_NAME=jupiter /etc/inetd.conf bpcd ...
General Test and Troubleshooting Procedures UNIX Example 4: Clients in Multiple Networks This network in this example (see the next figure) shows a client (mars/meteor) that is a router to clients in another network. The client’s host name on the master server side is mars and the host name presented to the client pluto is meteor. Example 4: Clients in Multiple Networks UNIX Master Server UNIX Media Server jupiter saturn Ethernet Class Client List jupiter mars saturn pluto usr/openv/netbackup/bp.
General Test and Troubleshooting Procedures First, we examine the configuration of the router system. The NetBackup class client list shows this system as mars because that is the name of the interface to the master server. There is no special configuration to note other than the client name setting. This name must be set to mars, because this is the name that the master server recognizes. The second client, pluto, is also configured no differently than if it were in the same network as the master server.
General Test and Troubleshooting Procedures The first thing to note about this configuration is that the NetBackup class client list specifies jupiter as the client name for the master server. The list could 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 and meteor.
General Test and Troubleshooting Procedures The solution, in this case, is also identical to that discussed in “UNIX Example 4: Clients in Multiple Networks” on page 43. Example 5: Server Connects to Multiple Networks UNIX Client saturn mars UNIX Media Server Ethernet jupiter meteor UNIX Master Server Ethernet Class Client List jupiter mars saturn pluto usr/openv/netbackup/bp.conf SERVER=jupiter SERVER=meteor SERVER=saturn CLIENT_NAME=mars pluto usr/openv/netbackup/bp.
General Test and Troubleshooting Procedures Host Name and Service Entry Examples- Windows NT/2000 Windows NT/2000 Example 1: Master Server and Client The example network in the following figure shows a Windows NT/2000 master server with one Windows NT/2000 client.
General Test and Troubleshooting Procedures Example 1: Windows NT/2000 Master Server and Client Windows NT/2000 Master Server jupiter Ethernet Windows NT/2000 Client mars Class Client List jupiter mars NetBackup Configuration 1 Servers NetBackup Configuration 1 Server List: jupiter General Client Name: jupiter .../etc/services 2 bpcd 13782/tcp bpcd bprd 13720/tcp bprd bpdbm 13721/tcp bpdbm vmd 13701/tcp vmd tl8cd 13705/tcp tl8cd odld 13706/tcp odld . .
General Test and Troubleshooting Procedures Windows NT/2000 Example 2: Master and Media Servers The network in this example (see the next figure) is the same as the previous one except that it includes a NetBackup media server named saturn. The difference to note is the addition of a server list for saturn on all the systems. Jupiter is designated as the master.
General Test and Troubleshooting Procedures Example 2: Windows NT/2000 Master and Media Servers Windows NT/2000 Master Server Windows NT/2000 Media Server jupiter saturn Ethernet Windows NT/2000 Client mars Class Client List jupiter mars saturn NetBackup Configuration 1 NetBackup Configuration 1 Servers Servers NetBackup Configuration 1 Server List: jupiter General Client Name: jupiter ...
General Test and Troubleshooting Procedures Windows NT/2000 Example 3: NetWare and Macintosh Clients The network in the next figure shows a NetBackup master server with NetWare and Macintosh clients. Note the following about this configuration: ◆ The server configuration is the same as with for other clients. ◆ Configuration entries on the Macintosh client are in the mac.conf and bp.conf files. ◆ Configuration entries on the NetWare client are in the openv\netback\bp.ini file.
General Test and Troubleshooting Procedures Example 3: PC Clients Windows NT/2000 jupiter Master Server pluto Macintosh Client Ethernet NetWare Target Client mars Preferences Folder NetBackup Folder Class Client List jupiter mars pluto bp.conf SERVER=jupiter CLIENT_NAME=pluto bp.ini NetBackup Configuration 1 Servers Server List: jupiter General Client Name: jupiter [bp] ClientName=mars [servers] master=jupiter [clients] browser=jupiter [tcpip] bpcd=13782 bprd=13720 mac.
General Test and Troubleshooting Procedures Windows NT/2000 Example 4: Clients in Multiple Networks The network in this example shows a client (mars/meteor) that is a router to clients in another network. The client’s host name on the master server side is mars and the host name presented to the client pluto is meteor.
General Test and Troubleshooting Procedures First, we examine the configuration of the router system. The NetBackup class client list shows this system as mars because that is the name of the interface to the master server. There is no special configuration to note other than the client name setting. This name must be set to mars, because this is the name that the master server recognizes. The second client, pluto, is also configured no differently than if it were in the same network as the master server.
General Test and Troubleshooting Procedures Windows NT/2000 Example 5: Server Connects to Multiple Networks The network in this example (see the next figure) shows a NetBackup server (jupter/meteor) that has two Ethernet connections and clients in both networks. The server’s hostname is mars on one network and meteor on the other. The first thing to note about this configuration is that the NetBackup class client list specifies jupiter as the client name for the master server.
General Test and Troubleshooting Procedures Example 5: Server Connects to Multiple Networks Windows mars Client saturn Windows NT/2000 Media Server Ethernet NetBackup Configuration 1 Servers Server List: jupiter meteor saturn jupiter Windows NT/2000 Master Server meteor Ethernet Clients Client List: mars 2 ...
Using the Configure - NetBackup Window Using the Configure - NetBackup Window Note Available only in the NetBackup Administration interface for Windows NT/2000. The Configure - NetBackup window in the NetBackup Administration interface on Windows NT/2000 provides access to many configuration settings for NetBackup clients and servers. For example, you can modify the server list, e-mail notification settings, and various timeout values for servers and clients.
Using the Configure - NetBackup Window 58 NetBackup Troubleshooting Guide - UNIX
3 Using the Logs and Reports NetBackup produces the following categories of information that you can use for troubleshooting problems. ◆ Reports ◆ Status for User Operations ◆ System Logs ◆ Activity Logs ◆ Media Manager Logs ◆ Windows NT/2000 Event Viewer Logging Option ◆ Troubleshooting the Java Administration Interface Note The format of the entries in the NetBackup logs is subject to change without notice.
Note The term media server, as distinct from master server or server, does not apply to the NetBackup BusinesServer product. When troubleshooting a BusinesServer installation, please ignore any references to media server in this guide.
Reports Reports NetBackup provides a set of standard reports that gives you most of the status and error information you need. To run these reports, use the NetBackup administration interface (see the NetBackup System Administrator’s Guide for instructions). The following table provides a brief description of the reports. Table 2. NetBackup Reports Report Description Backup Status Status and error information on backups and archives completed within the specified time period.
Status for User Operations Status for User Operations NetBackup allows you to view status on the progress of user operations. See the NetBackup user guides for instructions System Logs On UNIX, the NetBackup server daemons and programs occasionally log information through syslogd, which then shows a message or writes the information in an appropriate system log or the console log. See the syslogd man page for the locations of system log messages on your system.
Activity Logs Table 3. NetBackup Server Activity Logs Activity Log Directory Associated Process admin Administrative commands. bpbrm NetBackup backup and restore manager. bpcd NetBackup client daemon. bpdbjobs NetBackup jobs database manager program. bpdm NetBackup disk manager. bpdbm NetBackup database manager. This process runs only on master servers.
Activity Logs Note NetBackup can automatically delete the activity logs only if all clients are running at least NetBackup 3.0 software. If any clients are running an earlier version of NetBackup and you do not upgrade them, you must manually delete the activity logs. ◆ Activity logs can grow very large. Enable them only if unexplained problems exist and delete both the logs and the associated directory when they are no longer needed.
Activity Logs ◆ On Windows NT/2000 systems, set the Verbose level to 1 or more on the TroubleShooting tab of the NetBackup Configuration dialog box. To open this dialog box, start the client-user interface and click Configure on the Actions menu. Activity Logs on UNIX Clients To enable activity logging on UNIX clients, create the appropriate directories under: /usr/openv/netbackup/logs The following table lists the activity log directories that apply to UNIX clients.
Activity Logs Table 4. UNIX Client Activity Logs (continued) Activity Log Directory Associated Process db_log For more information on these logs, see the NetBackup guide for the database-extension product that you are using. tar tar process during restores. user_ops See Table 3.
Activity Logs Table 5. PC Client Activity Logs Activity Log Directory NetBackup Client Associated Process bpcd All Windows and NetWare clients NetBackup client daemon. These logs have information on communications between the server and client. On NetWare and Windows 98 and 95 clients, these logs also contain the log information for the backup and restore processes. bplist Windows NT/2000, 98, List program that is run from the command 95 line.
Media Manager Logs ◆ On Windows clients, set the debug level on the TroubleShooting tab of the NetBackup Configuration dialog. For instructions, see the NetBackup user guide for the client. ◆ On NetWare clients, change the value of the level and tcp parameters in the debug section of the bp.ini file. For instructions, see the NetBackup user guide for the client. Note Increasing the log level can cause the logs to grow very large, so take this action only if unexplained problems exist.
Media Manager Logs On UNIX Media Manager on a UNIX system automatically records robotic and network errors in the system logs by using syslogd. System log entries are also made when robotically controlled drives change between UP and DOWN states. Note You must enable system logging to troubleshoot ltid or robotic software. See the syslogd(8) man page for information on setting up system logs.
Windows NT/2000 Event Viewer Logging Option log.110894 To disable vmd debug logging, either delete the directory or rename it. These directories continue to accumulate information until you either rename or delete them. Note On HP-UX, the sysdiag tool may provide obtain additional information on hardware errors. On DEC OSF/1 the uerf command may provide additional information on hardware errors.
Windows NT/2000 Event Viewer Logging Option 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 and type of NetBackup messages that are written. The following is an example: 56 255 The next topic explains the format of the entry. If you do not add an entry, a default value is used, which is also explained in the next topic.
Troubleshooting the Java Administration Interface 64 = Backup Status 128 = Media Device ◆ If the file is empty, the default severity is Error (16) and the default type is Backup Status (64). ◆ If the file has only one parameter, it is used for the severity level and the default value of Backup Status (64) is used for the type. Example Assume you want to include all types of messages that have severity levels of warning, error, and critical.
Troubleshooting the Java Administration Interface The following are the four kinds of error messages seen in the NetBackup Java Administration interface. ◆ NetBackup status codes and messages as documented in Chapter 4. Operations performed in the Java Administration interface can result in errors recognized in other parts of NetBackup. These errors usually appear exactly as documented in Chapter 4. Note The error message is not always accompanied by a status code.
Troubleshooting the Java Administration Interface Enabling Detailed Activity Logging The NetBackup Java Administration interface is a suite of client-server applications that allow administration of remote NetBackup servers. All administration is accomplished via the application server of the NetBackup Java Administration interface. This application server is made up of an authentication service and a user service.
Troubleshooting the Java Administration Interface 4. If you are using the Windows Display Console, you should also add the following to the end of the last command in the associate.bat file in the NetBackup Java installed folder: > jnbdebug This redirects output to a file.
Troubleshooting the Java Administration Interface 76 NetBackup Troubleshooting Guide - UNIX
4 Status Codes and Messages This chapter lists all the status codes and messages provided by NetBackup. There are two parts to the chapter: ◆ The first section, Status Codes, lists the status codes in numerical order and includes an explanation of what occurred along with a recommended action. ◆ The second section, Messages, lists the same status codes but sorts them alphabetically according to the message associated with them. Only the messages and status codes are included the second section.
Status Codes Recommended Action: None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). In those instances, code 0 means the backup script that started the backup ran without error. However, you must check other status as explained in the related NetBackup manual to see if the database was successfully backed up.
Status Codes ◆ On PC clients, check the exclude list per the instructions in the user’s guide for the client. ◆ On Windows NT/2000 clients, verify that the account used to start the NetBackup Client service has read access to the files. If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT/2000 Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account.
Status Codes Recommended Action: 1. Ensure that the client’s server list contains entries for the master server and for any media servers that could be used during a backup or restore. 2. Examine the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server. 3. On Windows NT/2000 and UNIX, check ownership and permission on directories where files will be restored. 4. Correct problems that you find and retry the restore.
Status Codes Status Code: 7 Message: the archive failed to back up the requested files Explanation: Errors caused the user archive to fail. Recommended Action: Verify that you have read access to the files. Check the progress log on the client for messages on why the archive failed. Correct problems and retry the archive. On Windows NT/2000 clients, verify that the account used to start the NetBackup services has read access to the files.
Status Codes Recommended Action: 1. Check the All Log Entries and Problems reports to determine which system call failed and other information about the error. 2. A frequent cause is that the server’s file system is full.
Status Codes System requirements vary; thus, no absolute recommendations can be made.
Status Codes 04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted! If this error is encountered, try one of the following (the first is preferred): ◆ Set maximum OTM cache size to zero (0); at run time, OTM will determine how much cache is needed and set it accordingly. ◆ Increase either the initial OTM cache size or the maximum OTM cache size on your own, depending on the requirements of your installation and your usage of OTM.
Status Codes This indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of them or reschedule the entire backup to a time when the file system is less active. 3.
Status Codes ◆ ◆ A bad network interface card on the NetBackup server. ◆ Faulty routers. ◆ Other applications interfering with NetBackup connections. On Novell systems, status code 14 has also been attributed to network issues. Try a “sniffer” program, as suggested above. Status Code: 15 Message: file close failed Explanation: A close of a file or socket failed. Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred.
Status Codes 1. Check the NetBackup Problems report for clues on why the failure occurred. 2. On a UNIX system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd. 3. On a Windows NT/2000 system, verify that the %SystemRoot%\system32\drivers\etc\services file shows the correct entries for the NetBackup internet processes: bpcd, bpdbm, and bprd.
Status Codes ◆ On Windows NT/2000 NetBackup servers, check the install_path\netbackup\version.txt file or the About NetBackup item on the Help menu. ◆ On Microsoft Windows clients, check the About NetBackup item on the Help 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 Standard type class.
Status Codes 1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then, retry the operation and check the resulting activity logs. 2. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes). 3.
Status Codes SET SET SET SET Maximum Maximum Maximum Maximum Directory Cache Buffers = 4000 Concurrent Disk Cache Writes = 2000 Concurrent Directory Cache Writes = 2000 Physical Receive Packet Size = 1514 Status Code: 24 Message: socket write failed Explanation: A write operation to a socket failed. Recommended Action: 1. Check the NetBackup Problems report for clues on where and why the failure occurred.
Status Codes ◆ Change to or add the following settings in the Novell sys:system\autoexec.ncf file: SET SET SET SET SET Maximum Maximum Maximum Maximum Maximum Packet Receive Buffers = 4000 Directory Cache Buffers = 4000 Concurrent Disk Cache Writes = 2000 Concurrent Directory Cache Writes = 2000 Physical Receive Packet Size = 1514 Status Code: 25 Message: cannot connect on socket Explanation: A process timed out while connecting to another process for a particular operation.
Status Codes ◆ On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file. ◆ Make sure all recommended NetBackup patches have been installed. Check the VERITAS support web site for current patch information. (Go to www.support.veritas.com, then select “NetBackup” followed by “files and updates”.) ◆ If failure occurs when executing a user-directed backup from a client, make sure a user-directed backup schedule exists at the master server.
Status Codes Status Code: 26 Message: client/server handshaking failed Explanation: A process on the server encountered an error when communicating with the client. This error indicates that the client and server were able to initiate communications, but encountered difficulties in completing them. This problem can occur during a backup or a restore. Recommended Action: Determine which activity encountered the handshake failure by examining the All Log Entries report for the appropriate time period.
Status Codes Status Code: 29 Message: failed trying to exec a command Explanation: A command could not be executed. This can occur because the permissions of the command do not allow it to be executed, or there is lack of system resources such as memory and swap space. Recommended Action: 1. Check the NetBackup All Log Entries report for clues on where and why the failure occurred. 2. Check the permissions on the command to be executed. 3.
Status Codes Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log. Status Code: 33 Message: failed while trying to send mail Explanation: An E-mail notification of backup, archive, or restore results has failed.
Status Codes 1. Check the NetBackup All Log Entries report to determine which directory could not be created and why it could not be created. In particular, check for a full disk partition. 2. Check the permissions on the parent directory and verify that NetBackup services are started with a “Logon as” account that has permission to create the directory. 3.
Status Codes If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup database manager daemon (bpdbm) for the changes to take effect. If you change the server list on a Windows NT/2000 master server, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services. Status Code: 38 Message: could not get group information Explanation: Could not get the group entry describing a UNIX user group.
Status Codes ◆ On Windows NT/2000, 98, and 95 systems, the master server is designated on the Servers tab in the Master Server Properties dialog. To display this dialog, see “Using the Configure - NetBackup Window” on page 57. ◆ On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file. ◆ On NetWare target and OS/2 clients the master server name is the first SERVER entry in the bp.ini file.
Status Codes ◆ The bpbkar client process is not hung, but due to the files and directories it is scanning, it has not replied to the server within CLIENT_READ_TIMEOUT or CLIENT_CONNECT_TIMEOUT. This has been seen to occur during backups when directories have thousands of unmodified files; it has also been seen when backing up file systems or directories that reside on optical disk, which is considerably slower than magnetic disk.
Status Codes 4. If you are using an AIX token ring adapter and the routed daemon is running, the timeout can occur because the token ring adapter creates dynamic routes, causing the routed daemon to crash. 5. For a FlashBackup client, this can happen if the file system being backed up is very large and has a very large number of files. It can also occur if a large number of concurrent data streams are active at the same time.
Status Codes ◆ On clients, create a bpcd activity log directory (created automatically on Macintosh clients). ◆ Increase the amount of debug information included in the logs as explained in the activity log topics in Chapter 3. 3. Retry the operation and examine the logs. Note If you are using bpstart_notify scripts on UNIX or Windows NT/2000 clients, verify that messages are not being written to stdout or stderr.
Status Codes ◆ If this is a NetBackup for NetWare client and has a version of NetBackup earlier than 3.0, verify that the client is in a Standard type class. ◆ On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder. Status Code: 46 Message: server not allowed access Explanation: The server is trying to access the client but the server is not listed on the client as a valid server.
Status Codes Status Code: 48 Message: client hostname could not be found Explanation: The system function gethostbyname() failed to find the client’s host name. Recommended Action: 1. Verify that the client name is correct in: ◆ The NetBackup class configuration on the master server. ◆ The General tab in the NetBackup Configuration dialog box and the Clients tab in the Specify NetBackup Machines dialog box (on Microsoft Windows and NetWare nontarget clients).
Status Codes ◆ On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3. 4. Retry the operation and examine the resulting logs. 5. On UNIX systems, use the UNIX sum command to check for corrupt binaries. 6. On SGI IRIX 6.2/6.4 systems, clients may be missing the libdbm.so shared library. Refer to the SGI/IRIX install CD-ROM for the eoe.sw.dmi package. Status Code: 50 Message: client process aborted Explanation: The client backup aborted.
Status Codes On a Windows NT/2000 client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32.exe executables located in the install_path\NetBackup\bin folder on the client. Reinstall the client if these executables are not the same size as on other Windows NT/2000 clients or are not at the same release level or do not have the same NetBackup patches applied as other Windows NT/2000 clients.
Status Codes 4. When the robot is controlled by an Automated Cartridge System, verify that the ACSLS system is up. 5. If this is an initial installation, refer to “To Resolve Common Configuration Problems” on page 13. 6. On Windows NT/2000, check the Event Viewer Application log for error messages that indicate why the tape mount did not complete. On UNIX, check the system log.
Status Codes 3. Perform “Resolving Network Communication Problems” on page 24. 4. On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists and that it is the correct size. 5. Check the /etc/inetd.conf file to make sure the bpcd path is correct in the following entry: bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd 6.
Status Codes c. Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Configuration dialog box match the bpcd and bprd settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu. The values on the Network tab are written to the services file when the NetBackup Client service starts. d.
Status Codes Status Code: 59 Message: access to the client was not allowed Explanation: The master or media server is trying to access the client, but the server is not recognized by the client as a valid server. Recommended Action: 1. If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows: ◆ On Windows NT/2000, 98, and 95 clients, add the server on the Servers tab in the Specify NetBackup Machines dialog box.
Status Codes 4. On Macintosh clients, check the inetd and bpcd activity logs. Both logs are created automatically. ◆ Check the inetd log to see if NetBackupListen is running. ◆ Check the bpbkar and tar messages in the bpcd log file. To increase the amount of information included in the logs, set the loglevel parameter in the mac.conf file to a higher value. 5. Check the bpcd activity log to determine the server’s peername and what comparisons are being made.
Status Codes 1. Execute a df to see if the system can read the mount table. 2. On an SCO system, code 60 can occur because the mount-point path name exceeds 31 characters, which is the maximum allowed on an SCO system. The bpbkar activity log on the client will show 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 a shorter name and symbolically link the long name to the short name. 3.
Status Codes Recommended Action: 1. On all but Macintosh clients, enable bpcd activity logging as follows: a. Create a bpcd activity log directory on the client. b. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. c. On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3. 2. On Macintosh clients, check the inetd and bpcd activity logs. Both logs are created automatically.
Status Codes 1. Create a bptm activity log directory on the server. 2. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. On a Windows NT/2000 NetBackup server, set the Verbose logging level option on the Universal Settings tab in the Master Server Properties dialog (see “Using the Configure - NetBackup Window” on page 57). 3. Retry the operation and check the bptm activity log file for information on the drive, robot, and tape that is causing the timeout. 4.
Status Codes Status Code: 67 Message: client backup failed to read the file list Explanation: The client could not read the list of files to back up. Recommended Action: First, verify that the server did not crash. If that is not the problem and you need more information: 1. Set up activity logging: a. On the server, create a bpbrm activity log directory. b. On UNIX and Windows NT/2000 clients, create a bpbkar activity log directory. c.
Status Codes Status Code: 69 Message: invalid file list specification Explanation: The file list received from the server had invalid entries. Recommended Action: Check the class file list. If wildcards are used, verify there are matching bracket characters ([ and ]). If the file list contains UNC (Universal Naming Convention) names, ensure they are properly formatted.
Status Codes ◆ On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). To increase the amount of information that appears in the logs, see the logging topics in Chapter 3. 5. Retry the operation and check the resulting activity logs. 6. On Novell systems, check the following: ◆ For the nontarget version of NetBackup for NetWare, the backup class type must be “NetWare”, and the files list should include a forward slash (/) only.
Status Codes Explanation: The bpstart_notify script returned a nonzero exit code. Recommended Action: Check the bpstart_notify script on the client to see if it performs as desired. Status Code: 74 Message: client timed out waiting for bpstart_notify to complete Explanation: The bpstart_notify script on the client took too long. Recommended Action: Try to speed up the bpstart_notify script or set the BPSTART_TIMEOUT on the server to a value that is larger than the default.Set BPSTART_TIMEOUT in the bp.
Status Codes To increase the amount of information that appears in the logs, see the logging topics in Chapter 3. c. Retry the operation and check the resulting activity log. Status Code: 78 Message: afs/dfs command failed Explanation: Indicates an AFS vos command failure. Recommended Action: 1. Check the NetBackup Problems Report for additional information on why the command failed. 2. The bpbkar activity log shows the command that was executed. Create an activity log directory for bpbkar.
Status Codes Note ltid or the NetBackup Device Manager service is used only if devices are attached to the system. Status Code: 81 Message: Media Manager volume daemon (vmd) is not active Explanation: The tape manager (bptm) could not communicate with the NetBackup Volume Manager service (Windows NT/2000) or the Media Manager volume daemon (UNIX). This communication is required for most operations.
Status Codes Recommended Action: 1. For additional information, check the following: ◆ NetBackup Problems report ◆ System log (UNIX) ◆ Event Viewer Application log (Windows NT/2000) 2. Typically, this status code indicates a drive configuration problem that allows more than one process at a time to open the device. On UNIX, the problem could be due to: ◆ Two (or more) devices were configured that are really the same physical device (for different densities perhaps).
Status Codes e. On UNIX systems, look at the /usr/openv/netbackup/db/media/errors log (which is also included in the /usr/openv/netbackup/bin/goodies/support script output) for a drive that is frequently producing errors. Status Code: 84 Message: media write error Explanation: The system’s device driver returned an I/O error while NetBackup was writing to removable media or a disk file. Recommended Action: 1.
Status Codes Status Code: 85 Message: media read error Explanation: The system device driver returned an I/O error while NetBackup was reading from tape, optical disk, or a disk file. Recommended Action: 1. For additional information, check the following: ◆ NetBackup Problems report to determine the device or media that caused the error ◆ System and error logs for the system (UNIX) ◆ Event Viewer Application and System logs (Windows NT/2000) 2. Check for the following: ◆ A defective or dirty drive.
Status Codes ◆ Event Viewer Application and System logs (Windows NT/2000) 2. Check for the following: ◆ A defective or dirty drive. Clean it or have it repaired (see the tpclean command for cleaning). ◆ Incorrect drive configuration. Verify the Media Manager and system configuration for the drive. For example, on UNIX the drive could be configured for fixed mode when it must be variable mode. See the Media Manager Device Configuration Guide for more information. ◆ Defective media.
Status Codes Explanation: NetBackup detected a problem when backing up an Auspex FastBackup client. Recommended Action: Check the All Log Entries report. If more details are required, create bptm and bpbrm activity log directories on the server. Then, retry the operation and check the resulting log files. This error is usually due to a configuration problem.
Status Codes Recommended Action: 1. Check the All Log Entries report for more information. 2. Check the NetBackup Media Lists report to see if the catalog is intact. If the catalog is not intact, consider reloading it from the latest NetBackup catalog backup volume. 3. Verify that the disk partition on which the catalog resides has enough space. 4. If the above actions do not explain the problem, check the NetBackup Problems report. 5.
Status Codes In this case, configure the drive for variable-mode block sizes and suspend media written on that device. See the NetBackup Device Configuration Guide. The images written to those media may be restorable (this is platform dependent), but single file restores are almost guaranteed to fail. You can choose to expire these media and regenerate the backups, or you can attempt to duplicate the images on these media to another device and then expire the original copy. 4.
Status Codes ◆ NetBackup Problems report to determine the device or volume that caused the error ◆ System and error logs for the system ◆ Event Viewer Application and System logs (Windows NT/2000) 3. For detailed troubleshooting information, create an activity log directory for bptm and retry the operation. Check the resulting activity log files.
Status Codes This script lists all volumes in the Media Manager volume configuration, and augments that list with information on the volumes currently assigned to NetBackup. 2. 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 the volume is frozen or suspended, use the bpmedia command to unfreeze or unsuspend it (if that is desired).
Status Codes /usr/openv/volmgr/debug/daemon/log.xxxxxx On Windows NT/2000, the vmd log is: install_path\Volmgr\debug\daemon\xxxxxx.log 6. If this is a new storage unit, and this is the first attempt to use it, stop and restart NetBackup on the master server. Note The bptm activity logs (in verbose mode) usually show the NetBackup media selection process. Status Code: 97 Message: requested media id is in use, cannot process request Explanation: An operation was requested on a media ID that is in use.
Status Codes Explanation: A system call failed in bparchive, bpbackup, bplist, or bprestore. Recommended Action: 1. Enable activity logging for bparchive, bpbackup, bplist, or bprestore (as appropriate) by creating activity log directories for them. On UNIX, if a nonroot user is having problems, verify that the directory created has mode 666. Look for and correct any reported errors. 2. Retry the operation and check the resulting logs.
Status Codes Recommended Action: Verify that full path names are used (they start with / on UNIX), and they are less than the maximum path length for the system. Also, verify that the files exist and the permissions allow NetBackup to access them. Status Code: 110 Message: Cannot find the NetBackup configuration information Explanation: On Windows NT/2000, NetBackup could not read the registry entries that were created during installation. On UNIX, the /usr/openv/netbackup/bp.conf file does not exist.
Status Codes Status Code: 120 Message: cannot find configuration database record for requested NB database backup Explanation: The program that backs up the NetBackup internal catalogs could not find the attributes that indicate which media IDs to use or paths to back up. This error should not occur under normal circumstances. Recommended Action: 1. Check the NetBackup Problems report for additional information about the error. 2.
Status Codes Status Code: 124 Message: NB database backup failed, a path was not found or is inaccessible Explanation: One or more of the paths specified in the catalog backup configuration could not be backed up. Recommended Action: 1. Check the NetBackup Problems report for additional information about the error. Some possible causes are: ◆ The path does not exist. ◆ On a UNIX system, there is a symbolic link in one of the paths. 2.
Status Codes Explanation: An error occurred that prevents the product from operating in a consistent fashion. This error is usually related to a system call. Recommended Action: 1. Check the NetBackup Problems report for additional information about the error. 2. Check the system log for reported problems. 3. For detailed troubleshooting information, create bpdbm, bpsched, bptm, and bprd activity log directories on the master server and retry the operation. Check the resulting activity logs.
Status Codes Explanation: One of two explanations exist. ◆ A request was made that is unrecognized. This usually results from different versions of NetBackup software being used together. ◆ If a client receives this error in response to a list or restore request, it means that the DISALLOW_CLIENT_LIST_RESTORE or DISALLOW_CLIENT_RESTORE option exists in the bp.conf file on a UNIX NetBackup server or registry on a Windows NT/2000 NetBackup server.
Status Codes Recommended Action: Retry the operation as a root user (administrator on Windows NT/2000) on the master server. Also see status code 131. Status Code: 140 Message: user id was not superuser Explanation: The process was started by a user or process that did not have root privileges (on UNIX) or administrator privileges (on Windows NT/2000). Recommended Action: If desired, give the user or process administrator privileges (on Windows NT/2000) or root privileges (on UNIX) and retry the operation.
Status Codes Recommended Action: Either correct the command or verify that all NetBackup binaries are at the same version level. Status Code: 145 Message: daemon is already running Explanation: There is another copy of the process executing. Recommended Action: Terminate the current copy of the process and then restart the process. Status Code: 146 Message: cannot get a bound socket Explanation: The daemon (service on Windows NT/2000) could not bind to its socket.
Status Codes 3. If the problem persists longer than ten minutes, it is possible that it will be necessary to reboot the server. Status Code: 147 Message: required or specified copy was not found Explanation: The requested copy number of a backup or archive image cannot be found. Recommended Action: Correct the request to specify a copy number that does exist.
Status Codes Explanation: An incomplete request was made to the bpdbm process (NetBackup Database Manager service on Windows NT/2000). This usually occurs because different versions of software are being used together. Recommended Action: 1. Verify that all software is at the same version level. 2. For detailed troubleshooting information, create bpdbm and admin activity log directories and retry the operation. Check the resulting activity logs.
Status Codes 1. Examine the NetBackup error log to determine why the system call failed and correct the problem. It could be a permission problem. 2. If the error log does not show the error, create an activity log directory for bprd, bpdbm, or bpsched (depending on which process encountered the error) and retry the operation. Examine the resulting activity log. Status Code: 159 Message: licensed use has been exceeded Explanation: A configuration limit has been exceeded.
Status Codes Windows NT/2000, 98, 95: install_path\NetBackup\var\auth UNIX: /usr/openv/var/auth Macintosh: :System Folder:Preferences:NetBackup:var:auth 3. On the systems that are having the authentication problem, remove the remote host that is not being authenticated from the methods_allow.txt file. For example, if hosta and hostb are having the problem, remove hosta from the file on hostb and vice versa. Retry the operation.
Status Codes Status Code: 161 Message: Evaluation software has expired. See www.veritas.com for ordering information. Explanation: The time allowed for the NetBackup evaluation software has ended. Recommended Action: Obtain a licensed copy of NetBackup. Status Code: 164 Message: unable to mount media because it is in a DOWN drive or misplaced Explanation: A restore was attempted and the volume required for the restore was in a DOWN drive in a robot. Or, the slot that should contain the volume is empty.
Status Codes Status Code: 167 Message: cannot find requested volume pool in Media Manager volume database Explanation: A backup to a nonrobotic drive was attempted and the tape manager (bptm) could not find or add the specified volume pool. Recommended Action: Verify the Media Manager volume configuration. Check the NetBackup Problems report for more information about the error. For detailed troubleshooting information, create a bptm activity log directory and retry the operation.
Status Codes Explanation: When loading a volume for a backup or restore, the tape manager (bptm), did not find the expected tape header. This can mean that a volume in a robotic device is not in the slot number shown in the Media Manager volume configuration or that a read error (I/O error) occurred. Recommended Action: 1. If the volume is in a robot that supports barcodes, verify the robot contents by using a Media Manager robot inventory option. 2.
Status Codes 1. Check the NetBackup Problems report to see if it shows the cause of the problem. If you see a Problems report message similar to “attempting to write 32767 bytes, not a multiple of 1024” save all logs and call VERITAS customer support. 2. On UNIX, if this occurs during a restore, it may be that the tape drive is incorrectly configured to write in fixed length mode when it should write in variable length mode.
Status Codes Status Code: 175 Message: not all requested files were restored Explanation: When restoring files from an image, the bptm or bpdm process detected a fatal error condition and terminated the restore before it completed. This should not occur under normal circumstances. Recommended Action: 1. Check the NetBackup Problems report and the progress log on the client for additional information about the error 2.
Status Codes Status Code: 177 Message: could not deassign media due to Media Manager error Explanation: The tape manager (bptm) could not successfully deassign a media ID. Recommended Action: 1. Check the NetBackup Problems report for the cause of the problem. 2. Verify that the Media Manager volume daemon (vmd) is active on UNIX or the NetBackup Volume Manager service is active on Windows NT/2000. 3.
Status Codes Status Code: 181 Message: tar received an invalid argument Explanation: One of the parameters passed to tar was not valid. Recommended Action: On a UNIX client: ◆ Ensure that the tar command in /usr/openv/netbackup/bin is the one provided by NetBackup. If you are in doubt, reinstall it. ◆ Check /usr/openv/netbackup/bin/version on the client to verify that the client is running the correct level software.
Status Codes Recommended Action: ◆ If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar activity log directory on the client and rerun the operation. a. Check the tar activity log file for error messages that explain the problem. b. Reboot the client to see if this clears the problem. c. When you are through investigating 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: a.
Status Codes a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically). b. Increase the debug or log level as explained in the activity log topics in Chapter 3. c. On a Windows NT/2000 client, create a tar activity log directory. d. Retry the operation and check the resulting activity logs. e. Reboot the client to see if it clears the problem.
Status Codes 1. Retry the operation and check the progress log on the client for error messages that reveal the problem. 2. Verify that the tape is available and readable. 3. Verify that the drive is in an UP state. Use the Device Monitor 4. For detailed troubleshooting information: a. Create a bptm activity log on the server. b. On a Windows NT/2000 client, create a tar activity log. c. Retry the operation and check the resulting activity logs.
Status Codes Explanation: A verify, duplicate, or import was attempted and failed for all selected images. Recommended Action: Check the NetBackup Problems report for the cause of the error. To obtain detailed troubleshooting information, create an admin activity log directory and retry the operation. Check the resulting activity log. Status Code: 194 Message: the maximum number of jobs per client is set to 0 Explanation: The NetBackup Maximum jobs per client global attribute is currently set to 0.
Status Codes Explanation: A backup or archive operation that was queued by the backup scheduler was not attempted because the backup window was no longer open. Recommended Action: ◆ If possible, change the schedule to extend the backup window for this class and schedule combination so it does not occur again. ◆ If the backup must be run, use the Manual Backup command on the Class menu in the Backup Policy Management window to perform the backup. Manual backups ignore the backup window.
Status Codes ◆ If the client is not in such a class, either add a schedule of the appropriate type to an existing class that has this client or create a new class that has this client and a schedule of the appropriate type. Status Code: 199 Message: operation not allowed during this time period Explanation: A user backup or archive has been requested and this client is not in a class that has a user backup or archive schedule with an open backup window.
Status Codes Status Code: 201 Message: handshaking failed with server backup restore manager Explanation: A process on the master server encountered an error when communicating with the media host (can be either the master or a media server). This error means that the master and media server processes were able to initiate communication, but encountered difficulties in completing them. This problem can occur during a backup, restore, or media list in a single or multiple server configuration.
Status Codes 1. Verify that the schedule specifies the correct storage unit. 2. Execute the ping command from one host to another by using the following combinations: ◆ From the master server, ping the master and all media servers by using the host names found in the storage unit configuration. ◆ From each of the media servers, ping the master server by using the host name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file.
Status Codes network unreachable failure was encountered between the master and a media server or if only the master server was involved. Execute the ping command from one host to another by using the following combinations: 1. From the master server, ping the master and all media servers by using the host names in the storage unit configuration. 2. From each of the media servers, ping the master server host by using the host name specified in the NetBackup server list.
Status Codes 3. On UNIX servers, verify that the bpcd entries in /etc/services or NIS on all the servers are identical.
Status Codes ◆ If the error occurred during a restore operation, check the bprd activity logs. Status Code: 205 Message: cannot connect to server backup restore manager Explanation: A process on the master server could not connect to a process on a host on the network while trying to initiate communication with the server that has the storage unit for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration.
Status Codes The values on the Network tab are written to the services file when the NetBackup Client service starts. c. Stop and restart the NetBackup services. 5. See “Testing Media Server and Clients” on page 21 and “Resolving Network Communication Problems” on page 24. 6. Create a bpcd activity log directory on the server that has the storage unit and retry the operation. Then, check for additional information in the resulting activity log.
Status Codes 1. Verify that the NetBackup database manager (bpdbm) process (NetBackup Database Manager service on Windows NT/2000) is running. 2. Examine the All Log Entries report for the appropriate time frame to gather more information about the failure. 3. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.
Status Codes Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log on the master server. On UNIX servers, also gather the output of the ipcs -a command to see what system resources are currently in use.
Status Codes 1. Examine the Backup Status and All Log Entries report for the appropriate time period to determine the class or schedule that received the error. 2. Verify that the storage unit’s drives are not down or waiting for media from a previous operation that did not complete. 3. Verify that all the storage units do not have their Maximum concurrent jobs attribute set to 0 (for disk storage units) and Maximum concurrent drives used for backup attribute set to 0 (for Media Manager storage units). 4.
Status Codes To check for backups do the following: On a UNIX master server: 1. Check for active or queued backups by using the job monitor. 2. Check for active bp processes with bpps. This reveals if there are bpbrm or bptm processes running and a backup is active. 3. If there is no reason for bpsched to be running, then use kill -HUP to terminate it.
Status Codes 1. On a UNIX master server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT/2000 master server, verify that the NetBackup Database Manager service is running. 2. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.
Status Codes 3. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs. Ensure that the correct master server is being specified for the connection. Status Code: 219 Message: the required storage unit is unavailable Explanation: The class or schedule for the backup requires a specific storage unit, which is currently unavailable.
Status Codes Do this on the server where the storage unit is connected. On a Windows NT/2000 NetBackup server, executing netstat -a prints out several lines of output. If bpcd is listening, one of those lines is similar to the following: TCP myhost:bpcd 0.0.0.0:0 LISTENING Do this on the server where the storage unit is connected. b. If bpcd seems to be operating correctly, create bpsched and bpcd activity log directories and retry the operation.
Status Codes Recommended Action: Determine the cause of the status code that follows this one. Status Code: 222 Message: done Explanation: This status code is used in coordinating communication between various NetBackup processes and is normally not seen. If the error logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error.
Status Codes Recommended Action: Verify that all NetBackup software is at the same version level. If that is not the problem, create activity log directories for bpdbm and admin. Then, retry the operation and examine the resulting activity logs. Status Code: 226 Message: the entity already exists Explanation: The configuration already has an entity with the same name or definition.
Status Codes Recommended Action: Obtain detailed troubleshooting information by creating an activity log directory for bpdbm. Then, retry the operation, save the resulting activity log, and call customer support. Status Code: 230 Message: the specified class does not exist in the configuration database Explanation: The specified class name does not exist. Recommended Action: Correct your parameters or options and retry the operation.
Status Codes Status Code: 234 Message: communication interrupted Explanation: This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication. A process, either server or client, received an interrupt signal. Recommended Action: Save all error information and call customer support. Status Code: 235 Message: inadequate buffer space Explanation: This code usually indicates a mismatch between server and client software versions.
Status Codes Status Code: 237 Message: the specified schedule does not exist in an active class in the configuration database Explanation: The specified schedule does not exist in the NetBackup configuration. Recommended Action: Activate the required class, correct the schedule name, or create a schedule in a class that meets your needs. After making the correction, retry the operation.
Status Codes Status Code: 242 Message: operation would cause an illegal duplication Explanation: Processing the request would cause a duplicate catalog entry. This is usually due to a mistake in specifying media IDs for NetBackup catalog backups. Recommended Action: Check the error reports to determine the specific duplication that would occur. Correct the settings for the operation and retry it.
Status Codes Recommended Action: Activate the class and retry the operation. Status Code: 248 Message: there are no active classes in the configuration database Explanation: No active class was found that would satisfy the request. Recommended Action: Activate the appropriate class and retry the operation. Status Code: 249 Message: the file list is incomplete Explanation: The server timed out while waiting for the client to finish sending the file list, or a sequencing problem occurred.
Status Codes 1. Check the file list for the class and the exclude and include lists on the client to verify that the client has files that are eligible for backup. For example, this status code can appear if the exclude list on the client excludes all files. 2. To obtain detailed troubleshooting information, create activity logs for bptm and bpdbm on the server. Then, retry the operation and check the resulting activity logs. Status Code: 254 Message: server name not found in the bp.
Status Codes Recommended Action: Check the /usr/openv/java/auth.conf file on the machine (host name) specified in the NetBackup-Java login dialog for the proper authorization. If the file does not exist, it must be created with the proper entry for this user name. Refer to the NetBackup System Administrator’s Guide - UNIX for more details on the auth.conf file. Status Code: 503 Message: Invalid username.
Status Codes Explanation: The initial connection from the NetBackup-Java interface to its authentication service is on the port mentioned in the error message. The port is either being used by another application, or the NetBackup-Java interface and its application server are not configured with the same port. The default port is 13722. Recommended Action: 1. Compare the bpjava-msvc entry in the /etc/services file with the SERVER_PORT entry in /usr/openv/java/nbj.conf file. They must match. 2.
Status Codes Recommended Action: 1. Retry the last operation. 2. If the problem persists, restart the NetBackup-Java interface and try again. 3. If the problem still persists, enable detailed activity logging as explained under “Enabling Detailed Activity Logging” on page 74. 4. Restart the NetBackup-Java interface and examine the logs. Note You may be having network or system problems unrelated to NetBackup. Status Code: 508 Message: Cannot write file.
Status Codes ◆ A job (started by either the NetBackup-Java authentication service or user service) cannot be monitored by the NetBackup-Java service. This is probably due to a lack of system resources (insufficient memory). ◆ The maximum number of non-transient activity monitor jobs (>100) have already been started. Recommended Action: 1. If the problem persists, restart the NetBackup-Java interface and try again. 2.
Status Codes 3. Restart the NetBackup-Java interface and examine the logs. Note The error is probably the result of a system resource issue. When detailed activity logging has been enabled, the details may be retrieved from the bpjava-msvc or bpjava-usvc log files. Status Code: 512 Message: Internal error - a bad status packet was returned by NB-Java application server that did not contain an exit status code.
Messages Status Code: 514 Message: NB-Java: bpjava-msvc is not compatible with this application version (application_version). You may try login to a different NetBackup host or exit the application. The remote NetBackup host will have to be configured with the same version of NetBackup as the host you started the application on. Explanation: The NetBackup-Java application server (on the remote host you are logging in to) is not the same version as the NetBackup-Java interface on your local host.
Messages allocation failed (Status Code 10) an entry in the filelist expanded to too many characters (Status Code 70) an extension package is needed but was not installed (Status Code 9) an invalid entry was encountered (Status Code 223) another NB database backup is already in progress (Status Code 125) archive file removal failed (Status Code 4) authentication failed (Status Code 160) Auspex SP/Backup failure (Status Code 88) Backup Exec operation failed (Status Code 151) backup restore manager failed to
Messages bpjava-msvc: the client is not compatible with this server version (server_version) (Status Code 513) bpstart_notify failed (Status Code 73) can’t connect to client (Status Code 58) cannot connect on socket (Status Code 25) cannot connect to server backup restore manager (Status Code 205) Cannot connect to the NB-Java authentication service on the configured port configured_port_number (Status Code 505) Cannot connect to the NB-Java user service on port port_number (Status Code 506) Cannot execute
Messages cannot make required directory (Status Code 35) cannot overwrite media, data on it is protected (Status Code 168) cannot perform specified media import operation (Status Code 176) cannot position to correct image (Status Code 94) cannot read backup header, media may be corrupted (Status Code 173) cannot read media header, may not be NetBackup media or is corrupted (Status Code 172) Cannot write file (Status Code 508) child process killed by signal (Status Code 27) client backup failed to read the
Messages client backup was not attempted because backup window closed (Status Code 196) client cannot read the mount table (Status Code 60) client connection refused (Status Code 57) client did not start (Status Code 49) client hostname could not be found (Status Code 48) client is not validated to perform the requested operation (Status Code 135) client is not validated to use the server (Status Code 131) client name mismatch (Status Code 39) client process aborted (Status Code 50) client timed out waitin
Messages client timed out waiting for the continue message from the media manager (Status Code 65) client timed out waiting for the file list (Status Code 68) client’s network is unreachable (Status Code 56) client/server handshaking failed (Status Code 26) communication interrupted (Status Code 234) connection refused by server backup restore manager (Status Code 204) continue (Status Code 221) could not deassign media due to Media Manager error (Status Code 177) could not get group information (Status Co
Messages could not set user id for process (Status Code 31) daemon fork failed (Status Code 148) daemon is already running (Status Code 145) database system error (Status Code 220) density is incorrect for the media id (Status Code 179) done (Status Code 222) error creating or getting message queue (Status Code 209) error obtaining date of last backup for client (Status Code 207) error receiving information on message queue (Status Code 210) error requesting media (tpreq) (Status Code 98) error sending inf
Messages evaluation software has expired. See www.veritas.
Messages failed trying to allocate memory (Status Code 36) failed trying to exec a command (Status Code 29) failed trying to fork a process (Status Code 28) failed waiting for child process (Status Code 34) failed while trying to send mail (Status Code 33) fatal NB media database error (Status Code 91) File already exists: file_name (Status Code 510) file close failed (Status Code 15) file does not exist (Status Code 142) file open failed (Status Code 12) file path specified is not absolute (Status Code 14
Messages file pathname exceeds the maximum length allowed (Status Code 105) file read failed (Status Code 13) file write failed (Status Code 14) found no images or media matching the selection criteria (Status Code 190) getservbyname failed (Status Code 19) handshaking failed with server backup restore manager (Status Code 201) host is unreachable (Status Code 47) inadequate buffer space (Status Code 235) Incorrect password (Status Code 504) Internal error - a bad status packet was returned by NB-Java appl
Messages invalid command protocol (Status Code 143) invalid command usage (Status Code 144) invalid file pathname found, cannot process request (Status Code 106) invalid filelist specification (Status Code 69) invalid request (Status Code 133) Invalid username (Status Code 503) licensed use has been exceeded (Status Code 159) main bpsched is already running (Status Code 244) media close error (Status Code 87) media id is either expired or will exceed maximum mounts (Status Code 169) media id is not in NetB
Messages media id must be 6 or less characters (Status Code 171) Media Manager device daemon (ltid) is not active (Status Code 80) Media Manager volume daemon (vmd) is not active (Status Code 81) media manager detected image that was not in tar format (Status Code 92) media manager found wrong tape in drive (Status Code 93) media manager killed by signal (Status Code 82) media manager received no data for backup image (Status Code 90) media manager - system error occurred (Status Code 174) media open error
Messages media write error (Status Code 84) NB database backup failed, a path was not found or is inaccessible (Status Code 124) NB database backup header is too large, too many paths specified (Status Code 126) NB image database contains no image fragments for requested backup id/copy number (Status Code 165) NB-Java application server interface error: Java exception (Status Code 511) NB-Java application server not accessible - maximum number of connections exceeded (Status Code 500) NB-Java: bpjava-msvc
Messages network read failed (Status Code 42) network write failed (Status Code 44) no active classes contain schedules of the requested type for this client (Status Code 198) no active classes in the configuration database are of the correct client type (Status Code 246) No authorization entry exists in the auth.conf file for username username. None of the NB-Java applications are available to you.
Messages none of the files in the file list exist (Status Code 71) none of the requested files were backed up (Status Code 2) not all requested files were restored (Status Code 175) operation not allowed during this time period (Status Code 199) operation requested by an invalid server (Status Code 37) operation would cause an illegal duplication (Status Code 242) permission denied by client during rcmd (Status Code 55) pipe close failed (Status Code 18) premature eof encountered (Status Code 233) process
Messages request attempted on a non reserved port (Status Code 45) requested media id is in use, cannot process request (Status Code 97) requested media id was not found in NB media database and/or MM volume database (Status Code 95) required or specified copy was not found (Status Code 147) required value not set (Status Code 152) schedule windows overlap (Status Code 231) scheduler child killed by signal (Status Code 211) scheduler found no backups due to run (Status Code 200) server backup restore manag
Messages server not allowed access (Status Code 46) SERVER was not specified in /usr/openv/netbackup/bp.conf (Status Code 111) socket close failed (Status Code 22) Socket connection to the NB-Java user service has been broken. Please retry your last operation.
Messages system call failed (Status Code 11) system error occurred (Status Code 130) system error occurred while processing user command (Status Code 100) tar did not find all the files to be restored (Status Code 185) tar had an unexpected error (Status Code 184) tar received an invalid archive (Status Code 183) tar received an invalid argument (Status Code 181) tar received an invalid file name (Status Code 182) tar received no data (Status Code 186) tar was successful (Status Code 180) termination reque
Messages text exceeded allowed length (Status Code 225) the archive failed to back up the requested files (Status Code 7) the backup failed to back up the requested files (Status Code 6) the client is not in the configuration (Status Code 243) the client type is incorrect in the configuration database (Status Code 72) the database contains conflicting or erroneous entries (Status Code 238) the entity already exists (Status Code 226) the file list is incomplete (Status Code 249) the image was not created wi
Messages the requested operation was successfully completed (Status Code 0) the required storage unit is unavailable (Status Code 219) the restore failed to recover the requested files (Status Code 5) the server is not allowed to write to the client’s filesystems (Status Code 189) the specified class does not exist in the configuration database (Status Code 230) the specified class is not active (Status Code 247) the specified class is not of the correct client type (Status Code 245) the specified client d
Messages the specified schedule is the wrong type for this request (Status Code 241) the TIR information is zero length (Status Code 251) there are no active classes in the configuration database (Status Code 248) there was a conflicting specification (Status Code 224) timed out connecting to client (Status Code 54) timed out connecting to server backup restore manager (Status Code 202) timed out waiting for database information (Status Code 51) timed out waiting for media manager to mount volume (Status C
Messages unable to mount media because its in a DOWN drive or misplaced (Status Code 164) unable to process request (Status Code 228) unexpected message received (Status Code 43) unimplemented feature (Status Code 16) user id was not superuser (Status Code 140) valid archive image produced, but no files deleted due to non-fatal problems (Status Code 3) wbak exited abnormally (Status Code 62) wbak was killed (Status Code 61) You are not authorized to use this application (Status Code 501) 202 NetBackup Tr
5 Disaster Recovery This chapter has procedures for recovering your data in case of a server or client disk failure. The recovery procedures are as follows: ◆ Master Server Disk Recovery ◆ Media Server Disk Recovery ◆ Client System Disk Recovery - UNIX ◆ Client System Disk Recovery - Windows NT/2000, 98, 95 ◆ Recovering the NetBackup Databases Master Server Disk Recovery The procedures in this section explain how to recover your data if the system disk fails on a UNIX master server.
Master Server Disk Recovery Figure 1. Recover Master Server - Root Intact (overview) Tape Drive Master Server Shark Tape with database backups Disk 1 1. Reload operating system . . . 2. Restore NetBackup 3. Restore the NetBackup databases 4. Restore non-NetBackup files 1. Verify that the operating system is working. If it isn’t, take the appropriate corrective actions. 2. Reinstall NetBackup software. Do not configure NetBackup classes or devices.
Master Server Disk Recovery Recovering Master Server When Root is Lost This procedure assumes that the root file system has been lost along with all other files on the system disk. Figure 2 illustrates the procedure. The recovery method described here reloads the operating system on an alternate boot disk and boots from this disk during the recovery. This lets you recover the root partition without risking a crash due to overwriting files that are being used by the operating system during the restore.
Master Server Disk Recovery 3. Install NetBackup on the alternate disk. See the NetBackup Installation Guide - UNIX for instructions on installing NetBackup software. Note Do not reconfigure NetBackup classes. If reconfiguration is necessary, you will be given the necessary instructions later in this procedure. Install only the robotic software for the devices that are required to read backups of the NetBackup databases and the regular backups of the disk being restored.
Media Server Disk Recovery Media Server Disk Recovery Note The term media server, as distinct from master server or server, does not apply to the NetBackup BusinesServer product. When troubleshooting a BusinesServer installation, please ignore any references to media server.
Client System Disk Recovery - Windows NT/2000, 98, 95 Client System Disk Recovery - Windows NT/2000, 98, 95 The following procedure explains how to perform a total recovery of a Windows NT/2000, 98, or 95 NetBackup client in the event of a system disk failure. Note For Windows NT/2000 systems: if you have installed and configured NetBackup Intelligent Disaster Recovery, refer to the NetBackup System Administration Guide instead of the instructions below.
Client System Disk Recovery - Windows NT/2000, 98, 95 ◆ NetBackup 3.0 or later client software to install on the client that is being restored. ◆ Special drivers or other software required to get the hardware operational (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. ◆ Partitioning and formatting scheme that was used on the system that you are restoring.
Client System Disk Recovery - Windows NT/2000, 98, 95 5. Enable debug logging by creating the following debug log directories on the client: On a Windows NT/2000 client: install_path\NetBackup\Logs\tar install_path\NetBackup\Logs\bpinetd On a Windows 98 or 95 client: install_path\NetBackup\Logs\bpcd NetBackup creates logs in these directories. 6. For a Windows NT/2000 client, stop and restart the NetBackup Client Manager service. This enables NetBackup to start logging to the bpinetd debug log. 7.
Recovering the NetBackup Databases When the boot process is complete, the system is restored to the state it was in at the time of the last backup. Recommended Backup Practices In addition to backing up files on a regular basis it is important to select the correct files to back up. The first concern is to include all files with records that are critical to users and the organization.
Recovering the NetBackup Databases install_path\netbackup\db\media install_path\volmgr\database For install_path, substitute the directory where NetBackup and Media Manager are installed (C:\VERITAS by default). Because of their importance, the databases are backed up separately from other files as described in the NetBackup System Administrator’s Guide - UNIX.
Recovering the NetBackup Databases Note If the /dev file for the device you will use for listing the database information is lost in the failure, you must create the special device file path for that device before using bprecover. See the Media Manager Device Configuration Guide for information on creating this path. In this case, insert the media in an appropriate drive (assume the raw-device path is /dev/rmt/hc2d4). Then, execute the following command on the NetBackup server that has the drive.
Recovering the NetBackup Databases ---IMAGE1 /usr/openv/netbackup/db IMAGE2 /usr/openv/volmgr/database Example 4: Media Server Assume the master server is a UNIX system with no tape drives and the media server is a Windows NT/2000 system with a 4 mm tape drive. The database backup was done to the 4 mm tape drive on the Windows NT/2000 media server. Here, we mount the media in the appropriate drive (assume the raw device path is \\.\Tape0) and execute the following bprecover command on the media server.
Recovering the NetBackup Databases Before Starting ◆ Reinstall the NetBackup software (if necessary) as explained in “Master Server Disk Recovery” on page 203 or “Media Server Disk Recovery” on page 207. ◆ If you had created symbolic links to the database locations, be sure to manually recreate those links before starting the recovery. ◆ Find the tape that has the latest database backups. ◆ Ensure that the disk where you are restoring the databases contains the directory where the databases resided.
Recovering the NetBackup Databases Figure 3. Recover Databases to Same Disk - UNIX 8 mm tape drive (/dev/rmt/1cbn) Master Server Shark Media with database backups (media ID JBL29) Disk 1 /usr/openv/netbackup/db /usr/openv/volmgr/database 2. Stop the NetBackup request daemon (bprd) and NetBackup database manager daemon (bpdbm). ◆ Stop bprd by using the Terminate Request Daemon command on the bpadm Special Actions menu (or xbpadm File menu).
Recovering the NetBackup Databases Recover shark:/usr/openv/volmgr/database y/n (n)? y Recovering shark:/usr/openv/volmgr/database Example 2 If the databases were backed up from another disk, bprecover restores them to that disk: bprecover -r -tpath /dev/rmt/1cbn Recover shark:/sfs2/netbackup/db y/n (n)? y Recovering shark:/sfs2/netbackup/db Recover shark:/sfs2/volmgr/database y/n (n)? y Recovering shark:/sfs2/volmgr/database Figure 4 shows links from the NetBackup database directories on disk 1 to the a
Recovering the NetBackup Databases Recovering eel:/usr/openv/netbackup/db/media Recover eel:/usr/openv/volmgr/database y/n (n)? y Recovering eel:/usr/openv/volmgr/database You can also use the -dhost option to restore from a media server to the master (for example, if the master does not have a drive). Figure 5.
Recovering the NetBackup Databases 1. Stop the NetBackup request daemon (bprd) and NetBackup database manager daemon (bpdbm): ◆ Stop bprd by using the Terminate Request Daemon command on the bpadm Special Actions menu (or xbpadm File menu). ◆ Stop bpdbm by executing: /usr/openv/netbackup/bin/bpdbm -terminate 2. Insert the tape with the catalog backup into an appropriate drive. If the tape is not in the drive, the Device Monitor shows a mount request when you start the recovery. 3.
Recovering the NetBackup Databases c. Restart ltid by executing: /usr/openv/volmgr/bin/ltid This automatically starts vmd. Restore DB From Disk If you backed up the NetBackup databases to a disk that is intact, you can recover the databases as explained in the following procedure. Note If this disk has failed, you must resort to backups of this disk that have gone to another server.
Recovering the NetBackup Databases Figure 6. Restore Databases From Disk Master Server shark Disk 2 /nb/dbbackup Disk 1 IMAGE 1 /usr/openv/netbackup/db IMAGE 2 /usr/openv/netbackup/db /usr/openv/volmgr/database /usr/openv/volmgr/database 4.
Recovering the NetBackup Databases 222 NetBackup Troubleshooting Guide - UNIX
A Functional Overview This appendix provides a functional overview of NetBackup for both UNIX and Windows NT/2000. Such comprehensive treatment is valuable for mixed-platform environments. The discussions include descriptions of important daemons and programs, and the sequence in which they execute during typical operations. The databases and the directory structure of the installed software are also described.
Backup and Restore Functional Description Startup Process Before NetBackup can perform scheduled operations or respond to user-directed requests, the NetBackup request daemon bprd must be started on the master server, and the Media Manager device daemon ltid must be started on the master server and all media servers. These two daemons, in turn, automatically start other daemons and programs as necessary (see Figure 7). On a media server, it is not necessary to start bprd because it is not used.
Backup and Restore Functional Description Figure 7. Starting NetBackup Master Server Execute: Execute: /usr/openv/netbackup/bin/initbprd /usr/openv/volmgr/bin/ltid ltid bprd bpdbm Initiates further actions when a scheduled or user-directed operation is required. vmd Starts applicable robotic daemons. See the Media Manager Functional Description later in this appendix. avrd Media Server Execute: The Media Manager device components of NetBackup must be started as shown to the right.
Backup and Restore Functional Description Backup and Archive Processes The backup and archive processes vary depending on the type of client. The following explains the basic variations. There is also a description of how NetBackup operates when backing up its databases. Backups and Archives - UNIX Clients For UNIX clients, NetBackup supports scheduled, immediate manual, and user-directed backups of both files and raw partitions.
Backup and Restore Functional Description Figure 8.
Backup and Restore Functional Description For all three types of backup and archive operations, bpsched uses bpcd (client daemon) to start the backup/restore manager (bpbrm). If the required storage unit attaches to the master server, bpsched starts the backup/restore manager on the master server. If the storage unit connects to a media server, bpsched starts the backup/restore manager on the media server.
Backup and Restore Functional Description Figure 9.
Backup and Restore Functional Description Backups and Archives - Windows 95/98 Clients NetBackup supports the same types of operations on Windows 95 and 98 clients as it does for UNIX clients, with the following exception: ◆ Raw partition backups are not supported. The next figure shows the Windows 95 and 98 client processes. On this figure: ◆ The user interface program is called NBWIN. The bpbackup, bparchive, and bplist functions are merged into NBWIN.
Backup and Restore Functional Description Backups and Archives - Windows NT/2000 Clients NetBackup supports the same types of operations on Windows NT/2000 clients as it does for UNIX clients. The next figure shows the Windows NT/2000 client processes. On this figure: ◆ NBWIN is the user interface program on the client. The bpbackup, bparchive, and bplist functions are merged into NBWIN. ◆ BPINETD serves the same purpose as inetd on UNIX clients. ◆ The NetBackup client daemon is called BPCD.
Backup and Restore Functional Description Backups and Archives - NetWare Clients NetBackup supports the same types of operations on NetWare clients as it does on UNIX clients, with the following exceptions: ◆ Raw partition backups are not supported. ◆ NetBackup for NetWare does not support archiving. The next figure shows the NetWare client processes. On this figure: ◆ For NetWare nontarget, the user interface program is called NBNW95 on Windows 95 and 98 clients and NBNWNT on Windows NT/2000.
Backup and Restore Functional Description Backups - Macintosh Clients NetBackup supports the same types of operations on Macintosh clients as it does for UNIX clients. The next figure shows the client processes involved in backing up a Macintosh. The server processes are the same as described for UNIX. Server Client For details on the server processes, see Backups and Archives - UNIX Clients earlier in this chapter.
Backup and Restore Functional Description NetBackup Database Backups The administrator can use an option in the administrator interface to start a manual backup of the NetBackup databases or configure NetBackup to automatically back up its databases (Figure 10). It is possible to configure automatic database backups to occur either: ◆ After each scheduled backup session that results in the creation of at least one backup image.
Backup and Restore Functional Description Figure 10.
Backup and Restore Functional Description ◆ A second bpbackupdb process checks the file information to ensure that the proper files are being backed up. The entire database backup must fit on a single tape. The bpbackupdb process is unable to span tapes and there is no mechanism for specifying multiple tapes for an NetBackup database backup. If any part of the database backup fails, then NetBackup discards the entire backup.
Backup and Restore Functional Description If the storage unit on which the files reside attaches to the master server, then bprd starts the backup/restore manager on the master server. If the storage unit connects to a media server, bprd starts the backup/restore manager on the media server.
Backup and Restore Functional Description Figure 12. Restore operation From Tape or Optical UNIX Client Server NetBackup User Interface bprd Master Server Master or Media Server Media Database command line bprestore bpcd NetBackup Media ID bpcd bpbrm bptm req ue st Ta pe Im kup Bac m ou n age ltid * t Notes: * For detail on this component, see Media Manager Functional Description later in this chapter.
Backup and Restore Functional Description Restores - Windows 95/98 Clients NetBackup supports the same types of restore operations on Windows 95 and 98 clients as it does for UNIX clients. The next figure shows the client processes involved in these operations. On this figure: ◆ The user interface program on Windows 95/98 is called NBWIN. The bprestore and bplist functions are merged into NBWIN. ◆ The NetBackup client daemon is called BPCDW32. The NetBackup tar functions are merged into BPCDW32.
Backup and Restore Functional Description Restores - Windows NT/2000 Clients NetBackup supports the same types of operations on Windows NT/2000 clients as it does for UNIX clients. The next figure shows the client processes involved in these operations. ◆ The user interface program on Windows NT/2000 is called NBWIN. ◆ BPINETD is part of NetBackup for Windows NT/2000 and serves the same purpose as inetd on UNIX. ◆ The NetBackup client daemon is called BPCD.
Backup and Restore Functional Description Restores - NetWare Clients NetBackup supports the same types of restore operations on NetWare clients as it does on UNIX clients. The next figure shows the client processes involved in these operations. On this figure: ◆ The NetWare nontarget user interface program is called NBNW95 on Windows 95 and 98 clients and NBNWNT on Windows NT/2000 clients. The NetWare target user interface program is BP on the Netware console.
Backup and Restore Functional Description Restores - Macintosh Clients NetBackup supports the same types of operations on Macintosh clients as it does for UNIX clients. The next figure shows the client processes involved in restoring files to a Macintosh. Server Macintosh Client For details on the server processes, see Backups and Archives - UNIX Clients earlier in this chapter.
Backup and Restore Functional Description NetBackup Directories and Files Figure 13 shows the NetBackup file and directory structure on UNIX servers and clients. If a host is only a client and not a server, then only the files in the lower part of Figure 13 are present. If a host is both a client and a server, the client component shares files as necessary from those in the upper part of Figure 13.
Backup and Restore Functional Description Table 6. NetBackup Directories and Files - Servers and UNIX Clients File or Directory Contents bin Commands, scripts, programs, daemons, and files required for NetBackup operation and administration. On a server, there are two subdirectories under bin. admincmd: Contains various commands used internally by NetBackup. Use these commands ONLY if they are documented. Most of these commands are not documented and should not be used directly.
Backup and Restore Functional Description NetBackup Programs and Daemons Table 7 describes the programs and daemons that provide most of the control for backup, archive, and restore operations. The explanations include what starts and stops the program or daemon, and the log (if any) where it records its activities. Table 7.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description bpbackup On UNIX clients, this program communicates with bprd on the master server when a user starts a backup. Started By: Starting a backup by using the client-user interface or executing the /usr/openv/netbackup/bin/bpbackup command on the client. Stopped By: Completion of operation Activity Log: bpbackup.log on the client.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description bpcd On UNIX clients, bpcd is the NetBackup client daemon and lets NetBackup start programs on remote hosts (can be UNIX clients or other servers). For example, the server can connect to UNIX clients without requiring /.rhosts entries on the remote host. The program is used when bpsched starts bpbrm and when bpbrm communicates with the client.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description bpdbm On master servers, the NetBackup program that 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 Database Manager service on Windows NT/2000. Activity Log: bpdbm.log on the server.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description bpjava-usvc NetBackup-Java user server application program. This program services all requests from the NetBackup-Java user and administration interfaces. Started By: bpjava-msvc upon successful login through the Login dialog box that is presented when a NetBackup-Java interface is started. Stopped By: When the interface program is terminated.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description bpsched On master servers, the Scheduler uses class information from the NetBackup configuration databases to determine: ◆ Clients to start and when to start them. ◆ Storage units to use for backups and archives.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description jbpSA A Java-based program for performing backups, archives and restores of UNIX clients. Started By: On UNIX, the /usr/openv/netbackup/bin/jbpSA command. Activity Log: None, although the log for the bpbackup, bparchive, bplist, and bprestore commands on the client can be useful. Also, the logs for bpjava-msvc and bpjava-usvc can be helpful.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description NBNW95.EXE For NetWare nontarget clients, this is the executable file that starts the client-user interface on Windows 98/95 systems. Started By: From the Windows Start menu, under Programs/ NetBackup. Stopped By: Exiting the client-user interface. Activity Log: none.
Backup and Restore Functional Description Table 7. NetBackup Daemons and Programs (continued) Program/ Daemon Description TAR32 On Windows NT/2000 clients, the TAR32 program is a special version of tar provided with NetBackup and used to restore images. Started By: For each restore, NetBackup starts an instance of TAR32 on the client. Stopped By: Completion of restore operation. Activity Log: TAR.LOG in the NetBackup logs directory on the client.
Media Manager Functional Description NetBackup Databases Table 8 describes the NetBackup databases. These databases contain information that is used internally by NetBackup and reside in the /usr/openv/netbackup/db directory on UNIX servers and in the install_path\NetBackup\db directory on Windows NT/2000 NetBackup servers. Table 8. NetBackup Databases Database Contents config Configuration information.
Media Manager Functional Description ◆ Barcode Operations ◆ Media Manager Components Note In this section, the term Media Manager refers to the media and device management software that is part of NetBackup on either a UNIX or Windows NT/2000 NetBackup server. Startup Process Media Manager is part of NetBackup but, on UNIX, can also be run independently and used by other applications, such as Storage Migrator.
Media Manager Functional Description Figure 14.
Media Manager Functional Description Media and Device Management Process When the Media Manager daemons are running, NetBackup, Storage Migrator (UNIX only), or other users can initiate data storage or retrieval by sending a request for the required media ID to the Media Manager device daemon, ltid (Figure 15). ltid determines the location of the requested media ID by sending a query to the Media Manager volume daemon, vmd.
Media Manager Functional Description Figure 15.
Media Manager Functional Description Barcode Operations Barcode reading is mainly a function of the robot hardware rather than Media Manager. When a robot has a barcode reader, it scans any barcode that may be on a tape and stores the code in its internal memory. This associates the slot number and the barcode of the tape in that slot. Media Manager determines that association for its own use by interrogating the robot.
Media Manager Functional Description Figure 16.
Media Manager Functional Description Media Manager Components Media Manager Directories and Files Figure 17 shows the file and directory structure for Media Manager on a UNIX server. A Windows NT/2000 NetBackup server has equivalent files and directories that are located in the directory where NetBackup is installed (c:\Veritas by default). Table 9 describes the directories and files that are of special interest. Figure 17.
Media Manager Functional Description Caution DO NOT under any circumstances attempt to modify the Media Manager databases. These files are for internal program use only and changing them will result in program failure and possible loss of data. It is also recommended that you do not move them to another host. Table 9. Media Manager Directories and Files File or Directory Contents bin Commands, scripts, programs, daemons, and files required for Media Manager operation and administration.
Media Manager Functional Description Table 10. Media Manager Daemons and Programs Program/ Daemon Description acssel Available only on UNIX. See the Media Manager System Administrator’s Guide (UNIX or Windows NT/2000) for details. acsssi Available only on UNIX. See the Media Manager System Administrator’s Guide (UNIX or Windows NT/2000) for details.
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description lmfd The Library Management Facility daemon works in conjunction with lmfcd to handle requests to robots controlled by a Fujitsu Library Management Facility (LMF). lmfd provides the interface between the local ltid and the robotic control (lmfcd) in the same manner as explained later for tl8d. This robot is not available on Windows NT/2000.
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description rsmd The Tape Library RSMD daemon is the interface between ltid and the Microsoft Windows 2000 Removable Storage Manager (RSM) interface. The rsmd daemon runs only on Windows 2000 systems; note that the system must have rsm devices configured in the Media Manager interface. Started By: Starting ltid on Windows 2000 only. Stopped By: Stopping ltid on Windows 2000 only.
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description tl8cd The Tape Library 8MM Control daemon provides the robotic control for a TL8 robot and communicates with the robotics through a SCSI interface. tl8cd receives mount and unmount requests from tl8d on the host to which the drive is attached and then communicates these requests to the robot.
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description tlhd The Tape Library Half-inch daemon works in conjunction with tlhcd to handle requests to TLH robots that are in an IBM Automated Tape Library (ATL). tlhd provides the interface between the local ltid and the robotic control (tlhcd) in the same manner as explained previously for tl8d.
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description tpconfig tpconfig is a command line administrator utility for configuring devices under Media Manager. The graphical user interfaces provide equivalent functionality. Started By: tpconfig command. Stopped By: Quit option from within the utility on UNIX. On Windows NT/2000, tpconfig is a command-line interface that runs to completion (no quit option).
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description ts8d The Tape Stacker 8MM daemon is the interface between ltid and the 8-mm Tape Stacker and communicates with the robotics through a SCSI interface. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/ts8d command). Stopped By: Stopping ltid (or on UNIX, independently by finding the PID (process id) and then using the kill command).
Media Manager Functional Description Table 10. Media Manager Daemons and Programs (continued) Program/ Daemon Description xvmadm Available only on UNIX. An administrator utility with options for configuring and managing volumes under Media Manager. It has an X Windows based, graphical interface and provides all the functionality of vmadm. Started By: /usr/openv/volmgr/bin/xvmadm command or the Volume Management option from the xdevadm File menu. Stopped By: Quit option in xvmadm.
B Networks and Hostnames In a configuration with multiple networks and clients with more than one hostname, the NetBackup administrator must configure the class entries carefully, at all times considering the network configuration (physical, hostnames and aliases, NIS/DNS, routing tables, and so on). This is especially true if the desire is to direct backup and restore data across specific network paths. For a backup, NetBackup connects to the host name as configured in the class.
The comparison is first a simple string comparison which, if successful, is verified by comparing hostnames and aliases retrieved by using the network function gethostbyname(). If none of the comparisons succeed, a more brute force method is used, which compares all names and aliases using gethostbyname(). The configured name is the first comparison that succeeds. Note that other comparisons might also have succeeded if aliases or other “network names” are configured.
The destination client name is a factor only if an administrator is pushing a restore to a client from a server. For a user restore, destination client and requesting client are the same. For an administrator restore, the administrator can specify a different name for the destination client. By the time these names appear in the bprd activity log, the requesting client name has been translated into the client’s configured name.
You can create and edit this file to force the desired translation of NetBackup client host names. Each line in the host.xlate file has three elements: a numeric key and two hostnames. Each line is left-justified, and each element of the line is separated by a space character. key hostname_from_ client client_as_known_by_server Where ◆ key is a numeric value used by NetBackup to specify the cases where the translation is to be done.
C Robotic Test Utilities Each of the robotic software packages includes a robotic test utility for communicating directly with robotic peripherals. The tests are for diagnostic purposes and the only documentation is the online help that you can view by entering a question mark (?) after starting the utility. Specify -h to display the usage message. Note Do not use the robotic test utilities when backups or restores are active.
Robotic Tests on UNIX ODL /usr/openv/volmgr/bin/odltest -r roboticpath TL4 /usr/openv/volmgr/bin/tl4test -r roboticpath TL8 /usr/openv/volmgr/bin/tl8test -r roboticpath TLD /usr/openv/volmgr/bin/tldtest -r roboticpath TLH /usr/openv/volmgr/bin/tlhtest -r robotic_library_path TLM /usr/openv/volmgr/bin/tlmtest -r DAS_Hostname TS8 /usr/openv/volmgr/bin/ts8test -r roboticpath TSD /usr/openv/volmgr/bin/tsdtest -r roboticpath TSH /usr/openv/volmgr/bin/tshtest -r roboticpath Note For more information on ACS, TLH,
Robotic Tests on Windows NT/2000 Robotic Tests on Windows NT/2000 If the robot has been configured (that is, added to the Media Manager device database), start the robotic test utility by using the robtest command. This saves time, since robotic and drive device paths are passed to the test utility automatically. The procedure is as follows: 1. Execute the following command: install_path\Volmgr\bin\robtest.exe The test utility menu appears. 2. Select a robot and press Enter. The test starts.
Robotic Tests on Windows NT/2000 278 NetBackup Troubleshooting Guide - UNIX
Glossary access control list (ACL) Security information associated with files on some file systems. ACS Automated Cartridge System. This robot type is supported only by NetBackup DataCenter servers. active job A job for which NetBackup is currently processing backup or restore data. activity logs Logs that can be optionally enabled for specific NetBackup programs and processes and then used to investigate problems.
alternate-client restore Restoring files to your client when they were originally backed up from a different client. The administrator using the interface on the master server can direct a restore to any client (this variation is called a server directed restore). alternate-target restore On a Novell NetWare server platform running the NetBackup target version of client software, this operation restores files to a different target than the one from which they were backed up.
backup, archive, and restore interface The name of the NetBackup Microsoft Windows and Java based user interfaces for clients. On servers, these interfaces can be started through the NetBackup Administration interface. backup window The period of time during which backups can begin. block size The number of bytes in each block of data written on the media during a backup. bp A backup, archive, and restore utility for users on NetBackup UNIX clients.
CDF Context-dependent file, which is a type of directory structure on a Hewlett-Packard system. class Defines the backup policy for a group of one or more clients that have similar backup requirements. client The system with the files to back up, archive, or restore. client-user interface The program used to perform user backups, archives, and restores. cluster See master and media server cluster. command lines Commands that users can execute either from the system prompt or in scripts.
daemon A program on a UNIX system that runs in the background and performs some task (for example, starting other programs when they are needed). Daemons are generally referred to as services or processes on Windows NT/2000 systems. database-agent clients Clients with additional NetBackup software that is designed to back up relational databases. database-extension clients See “database-agent clients.” debug logs See “activity logs.
directory tree The hierarchical structure in which files are organized on a disk. Each directory lists the files and directories that are directly below it in the tree. On UNIX, the topmost directory is called the root directory. disaster recovery Recovering data from backups after a disk crash or other catastrophe. disk Magnetic or optical disk storage media. disk-image backup A bit-by-bit rather than a file system backup of a disk drive on Windows NT/2000. DLT Digital-linear tape or tape drive type.
exclude list A list that designates files or directories to exclude from automatic backups. expiration (image) The date and time when NetBackup stops tracking a backup image. expiration (volume) The date and time when the physical media (tape) is considered to be no longer usable. EVSN External volume serial number. This is an identifier written on a media cartridge or canister so the operator can identify the volume before inserting it into a drive or robot.
full backup A backup that copies, to a storage unit, all files and directories that are beneath a specified directory. FULL media state If this appears in a report or listing, it indicates the volume is FULL and cannot hold more data or be used for further backups. global attributes NetBackup configuration attributes that affect all classes.
hierarchical storage management The process of automatically migrating selected files from a managed file system to specified migration levels on secondary storage, while maintaining transparent access to those files. host A computer that executes application programs. host name Name by which a host computer is identified by programs and other computers in the network. HSM See storage migrator. image The collection of data that NetBackup saves for an individual client during each backup or archive.
jbpSA The Java-based NetBackup interface for performing user backups, archives, and restores. jnbSA The Java-based NetBackup interface for administrators. job A parcel of work submitted to a computer. NetBackup jobs are backups, archives, or restores. kernel The nucleus of an operating system. keyword phrase A textual description of a backup. kill a job Terminating a job and removing it from the job queue. label Identifier of a tape or optical disk volume. A recorded label includes a media ID.
load (noun) Amount of work that is being performed by a system or the level of traffic on a network. For example, network load affects performance. (verb) Copy data to internal memory. For example, load the installation program. logs Files where a computer or application records information about its activities. mailslot See “entry and exit ports.” man pages Online documentation provided with UNIX computer systems and applications.
Media Manager Software that is part of NetBackup and manages the storage devices and removable media. Media Manager Host A host where Media Manager software is installed. media server A NetBackup server that provides storage within a master and media server cluster. The master can also be a media server. A media server that is not the master is called a remote media server (or slave server). NetBackup BusinesServer does not support remote media servers.
multiplexing The process of sending concurrent-multiple backups from one or more clients to a single storage device and interleaving those images onto the media. multiplexed group A set of backups that were multiplexed together in a single multiplexing session. NDMP Network data management protocol. NetBackup requires the NetBackup for NDMP separately-priced option to support NDMP.
NetBackup Request Manager service The NetBackup Windows NT/2000 service that runs on the master server and starts the scheduler and receives requests from clients. NetBackup Volume Manager service A NetBackup Windows NT/2000 service that runs on a NetBackup server, allows remote administration of Media Manager, and manages volume information. The process is vmd. NIS Network information service. NLM NetWare loadable module. NFS Network file system. nonrobotic See “standalone.” ODL Optical disk library.
pathname The list of directories in the path to a destination directory or file. PC clients NetBackup clients that have Microsoft Windows (NT/2000, 98, 95), Macintosh, or IBM OS/2 operating systems. peername The name by which a computer identifies itself when establishing connections to other systems. port A location used for transferring data in or out of a computer. primary copy The copy of an image that NetBackup uses to satisfy restores.
rbak The program that Apollo clients use to read data from tape during a restore. registry A Microsoft Windows 2000, NT, 98, and 95 database that has configuration information about hardware and user accounts. remote media server A media server that is not the master. Note that only NetBackup DataCenter supports remote media servers. NetBackup BusinesServer supports only a single server, the master. residence In Media Manager, information about the location of each volume is stored in a volume database.
Also, a UNIX user name having administration capability. RS-232 An industry-standard interface for serial communications and sometimes used for communicating with storage peripherals. RSM Interface Application in Windows 2000 used to manage Removable Storage Manager (RSM) devices. RSM - Removable Storage Manager A Media Manager designation for a category of robot. For the specific vendor types and models in this category, see the VERITAS support web page at www.support.veritas.com.
server list The list of servers that a NetBackup client or server refers to when establishing or verifying connections to NetBackup servers. On a Windows NT/2000 server and Microsoft Windows clients, you update the list through a dialog box in the interface. On a UNIX server and UNIX and Macintosh clients, the list is in the bp.conf file. On NetWare target and OS/2 clients, the list is in the bp.ini file.
storage migrator Refers to the VERITAS Storage Migrator line of hierarchical storage management products for UNIX and Windows NT/2000. These products make extra room on a disk by transparently moving data to other storage and then transparently retrieving the data when it is needed by a user or application. Storage Migrator is available only for NetBackup DataCenter servers. storage unit Refers to a storage device where NetBackup or Storage Migrator stores files.
target service A Novell NetWare service that needs storage management. The SMS views all services (for example, print services, communication services, workstations) as targets. Target Service Agent A Target-service agent is a Novell NetWare agent that prepares the target’s data for SMS during a backup and for the target during a restore. TLD - Tape Library DLT A Media Manager designation for a category of robot.
timeout period The period of time that an application has allotted for an event to occur. TIR See “true image restore.” tpconfig A Media Manager administration utility for configuring devices and is started from the command line. On UNIX, it has a character-based, menu interface that can be run from terminals that do not have X Windows capabilities. transfer rate The rate at which computer information is transferred between a source and a destination.
verify An operation that compares the list of files that are actually on a volume with what NetBackup has recorded as being on it. The data that is on the media is not verified. vmadm A Media Manager administrator utility for managing volumes. It runs on UNIX and has a character-based, menu interface that can be run from terminals that do not have X Windows capabilities. vm.
wakeup interval The time interval at which NetBackup checks for backups that are due. wbak The program that Apollo clients use to write data on tape. wildcard characters A character that can be used to represent other characters in searches. WORM media Write-once, read-many media for optical disks. NetBackup BusinesServer does not support WORM media. Windows Display Console A NetBackup-Java interface program that runs on Windows 2000, NT, 98, and 95 computers.
302 NetBackup Troubleshooting Guide - UNIX
Index A acssel, description 263 acsssi, description 263 acstest 275, 277 Activity logs 62, 74 admin log 63 admincmd, directory 244 Administration interface activity logging 74 errors 72 All Log Entries report 61 Alternate client restores definition 280 host.xlate file 273 Alternate path restore definition 280 Alternate target restore definition 280 altnames file 254 application server status codes (Java interface) 73 Archive bit definition 280 Archives definition 280 ascd, description 263 associate.
bpcd description 247 Mac client log 68 server log 63 UNIX client log 65, 67 BPCD.NLM 247 BPCDW32 230, 239 BPCDW32.EXE 247 bpclntcmd utility 35 bpdbjobs description 247 log 63 bpdbm description 248 log 63 bpdm description 248 log 63 bperror command 77 bphdb description 248 log 65 BPINETD 231, 240 bpinetd.
Debug level 67, 68, 74 Debug logs NetBackup (see Activity logs) vmd 69, 262 Define the problem 1 Device configuration problems 15 Device database 262 Directory structure Media Manager 261 NetBackup UNIX client/server 243 Disaster recovery 203 Disk recovery media server 207 NT client 208 root on master 205 UNIX client 207 UNIX master server 203 Disk-image backup definition 284 DLT, definition 284 DNS (see Domain Name Service) Domain Name Service hostnames 273 drive drive limit exceeded 17 type not determined
Log level Macintosh clients 68 Windows and NetWare clients 67 Logs overview 59 activity, enabling detailed 74 activity, introduction 62 event viewer logging option 70 Mac client activity bpcd 68 inetd 68 media management 69 NT Event Viewer Application 62 PC client activity bp 66 bparchive 66 bpbackup 66 bpbkar 66 bpcd 67 bpinetd 66 bplist 67 bpmount 67 bprestore 67 bpsrv 67 nbwin 67 tar 67 user_ops 67 reports, NetBackup 61 server activity admin 63 bpbrm 63 bpcd 63 bpdbjobs 63 bpdbm 63 bpdm 63 bprd 63 bpsche
start and stop 12 NetBackup configuration options definition 291 NetBackup Database Manager service definition 291 start and stop 12 NetBackup Device Manager service definition 291 start and stop 12 NetBackup Request Manager service definition 292 start and stop 12 NetBackup Volume Manager service definition 292 start and stop 12 NetBackupBPCD 233, 242, 252 NetBackupListen 233, 242, 252 NetWare Loadable Module 292 Network connections, multiple 271 Network problems PC clients 28 UNIX clients 24 NLM (see NetW
acstest 275, 277 odltest 276 RSM robot 277 tl4test 276, 277 tl8test 276, 277 tldtest 276, 277 tlhtest 277 ts8test 276, 277 tsdtest 276, 277 tshtest 276 Robotic test utilitylmftest 275 robtest 275, 277 root 294 RSM robot 277 rsmd, description 265 S Scheduler, bpsched 63 serialization problems 15 Server disk recovery 207 installation problems 13 NetBackup activity logs 62 recovering root on master 205 test procedure for master 18, 22 test procedure for media server 21 UNIX disk recovery 203 Server directed re
tsdd, description 268 tsdtest 276, 277 tshd, description 268 tshtest 276 definition 300 Volume database, definition 300 Volume group definition 300 Volume pool definition 300 U user_ops log 63 Utility, robotic test 275 W Windows Display Console 75 WORM media definition 301 V Verbose option 64 VERITAS NetBackup ix Version, software (see Software version, determining) vm.
310 NetBackup Troubleshooting Guide - UNIX
