Home

NetBackup 4.5 Troubleshooting Guide for Windows

1. Windows NT 2000 n Windows NT 2000 upiter Master Server va Media Server al Ethernet mas Windows NT 2000 Policy Client List Client jupiter mars saturn NetBackup Configuration 7 NetBackup Configuration 1 Servers Servers Serwer LISE japltes NetBackup Configuration Server List upi General rai General erver List jupiter 3 n Client Name jupiter sat rn Client Name saturn General ET Client Name mars a etc services etc services bpcd 13782 tcp bpcd bpcd 13782 tcp bpcd bprd 13720 tcp bprd 3 bprd 13720 tcp bprd bpdbm 13721 tcp bpdbm etc services vmd 13701 tcp vmd vmd 13701 tcp vmd bpcd 13782 tcp bpcd tl8cd 13705 tcp tl8cd tl8cd 13705 tcp tl8cd Id 13706 l odid 13706 tcp odid bprd 13720 tcp bprd oe AEE Reg Notes 1 The NetBackup Client Properties dialog also has a Network tab with NetBackup client service port BPCD and NetBackup request service port BPRD settings that must be the same as the bpcd and bprd settings in the services file 2 The complete path to the Windows NT 2000 etc services file is SystemRoot system32 drivers etc services 3 All other applicable network configuration must also be updated to reflect the NetBackup information For example this could include the SystemRoot system3a drivers etc hosts file and also WIN and DNS if used Chapter 2 Troubleshooting Procedures 33 NetBac
2. usna sa cece eee 51 Enabling Detailed Debug Logging susssrnsrrarrrnrnranrrnnrnrnr nna 53 Chapter 4 NetBackup Status Codes and Messages 0 ee0eeeees 55 Status Cod s ssssesrysser ieder pirni ao en Ei EEEE EEES E AiE EE E EEO E 55 IMCSSAB OS er gecurpi eie pe ii gee ei ped eae G EE a OEE E a e e e e ne 173 Chapter 5 Media Manager Status Codes and Messages 201 Status CodeS era geen e E EE ae TE EEE EE Gide EEE Sout glnct 201 Media Manager Status Codes nunun nunnan nran eee eee ee 201 Device Configuration Status Codes s ss sss cece cece eee eee 285 Format Optical Status Codes 2 nanana nannan nrnna nearer arna 306 Device Management Status Codes 0000s 313 Robotic Stat s Codes iis ci cect cies phi dee ede sGe tinin e aeai 338 Robotic Error Codes 054 scat gree ea daa Ga aes Saat See Ba 359 Messages sh cmsiahenran cethedatns mutha catsaleredqmam dct eign reac beans eats 364 Chapter 6 Disaster Recovery 200 ce eee eee eee 399 Master Server Disk Recovery 0 6 66 c ccc ee ekaa Eiis 399 Recovery When Windows is Intact 0 6 c ences 399 Before Starine reii deine ke E Seis nieve ee neers anes manta ag 400 To Recover the Master Server Windows intact 00 0 0 e eee eee 400 Total Recovery soc eiueeide id nen ee ed es ee ec onde ete 402 ASSUMPHONS i eesis cessa gaea pe aia EEE EN E E Rate ganas pele GIA es RE 403 Before Starine
3. external _attributes txt external densities txt external drivetypes txt external mediatypes txt external robotics txt Media Manager Status Code 151 Message invalid global device database entry Explanation vmd encountered a read error while reading a global device database record or a memory allocation error while allocating table space for global device information vmd is the Media Manager volume daemon UNIX or NetBackup Volume Manager service Windows Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 The global device database may be corrupted Restore an older volume database from a saved version or from catalog backups 27 4 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 Free up memory by terminating unneeded processes that consume a lot of memory Add more swap space or physical memory Media Manager Status Code 152 Message global device database record not found Explanation A
4. Chapter 5 Media Manager Status Codes and Messages 295 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Check the device configuration on the targeted device host and identify the configured robots On the drive configuration request specify both the robot number and robot type that relate to the robot containing the drive Device Configuration Status Code 31 Message Robot number does not exist Explanation On a request to add or update a drive or robot in the device configuration it was found that the robot number and robot type specified were not associated with any configured robots on the targeted device host Recommended Action Check the device configuration on the targeted device host and identify the configured robots Every drive that is configured as a robotic drive must already have its robot configured on that device host For shared robotic libraries having robotic control on a remote host there must be a logical robotic entry that refers to the remote host having robotic control Add the robot to the device configuration first then add the drive defining it to be in the robot If the robot was already configured specify the correct robot number and robot type on the drive or robot configuration request Device Configuration Status Code 34 Message Drive name is already in use by another drive Explanation On a request t
5. cannot connect to robotic software daemon Media Manager Status Code 42 cannot connect to vmd on host host name Media Manager Status Code 70 Cannot create miscellaneous working repository Device Configuration Status Code 42 cannot delete assigned volume Media Manager Status Code 92 cannot delete one of the default volume pools Media Manager Status Code 118 Cannot discover devices See the Troubleshooting Guide for details Device Configuration Status Code 44 Cannot execute command permission denied Device Configuration Status Code 1 cannot get host name Media Manager Status Code 76 Cannot move from media access port to slot Robotic Status Code 218 Cannot move from slot to media access port Robotic Status Code 219 cannot obtain daemon lockfile Media Manager Status Code 21 Chapter 5 Media Manager Status Codes and Messages 367 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Cannot open create the media access port status file Robotic Status Code 243 cannot perform operation on this host Media Manager Status Code 60 Cannot recover aborted eject with this type of media access port Robotic Status Code 248 Cannot stop device daemon with tapes assigned Device Management Status Code 20 Cannot synchronize global device database Device Configuration Status Code 5 Characte
6. NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Ifthe NetBackup encryption evaluation license has expired on the server and you want to continue encrypting backups of the client you must purchase a permanent encryption license key and add it to the server After you add the permanent encryption license key check the attributes of the backup policy to make sure that encryption is selected To check the validity of an evaluation license key do the following On Windows go to the Help menu on the NetBackup Administration window on the NetBackup server and select License Keys If the evaluation key is not listed in the NetBackup License Keys window the key has expired Use this window to add the new permanent encryption key NetBackup Status Code 47 Message host is unreachable Explanation An attempt to connect to another machine failed Recommended Action 1 Verify that the name service or services being used by the client is configured to correctly resolve the host names of the NetBackup server 2 Verify that the name service or services being used by the server is configured to correctly resolve the host name of the NetBackup client 3 Try to ping the client from the server and the server from the client 4 Ifyou continue to have problems perform Resolving Network Communication Problems on page 21 NetBackup Status Code 48 Message client hostname could not be found Explanatio
7. Table 5 describes the files and directories that are of special interest Figure 12 NetBackup Directories and Files UNIX Servers and Clients NetBackup Server usr openv netbackup bin bp conf client db exclude_list include_list help logs release_notes version goodies admincmd Not used on a media server NetBackup UNIX Client usr openv netbackup bin bp conf help logs exclude_list include_list 4 Appendix A Functional Overview 439 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 5 NetBackup Directories and Files Servers and UNIX Clients File or Directory Contents bin bp conf client db exclude_list help include_list logs release notes version 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 goodies UNIX only Contains scripts and information that may be useful to the administrator These subdirectories are not present on clients Configuration file where you can specify various options for NetBackup operation The NetBackup System Administrat
8. 57141 is the port number of the connection on the client bpclintcmd sv The sv option displays the NetBackup version number on the master server Chapter 2 Troubleshooting Procedures 29 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Host Name and Service Entry Examples 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 7 30 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Example 1 Windows NT 2000 Master Server and Client Windows NT 2000 jupiter Master Server Jup Ethernet Windows NT 2000 mars Client Policy Client List jupiter mars NetBackup Configuration 1 Servers NetBackup Configuration 1 Server List jupiter ervers General 7 aoe Server List jupiter master Client Name jupiter General 2 Client Name mars etc services bpcd 13782 tcp bpcd bprd 13720 tcp bprd bpdbm 13721 tcp bpdbm ere vmd 13701 tcp vmd etc services tl8cd 13705 tcp tl8cd bpcd 13782 tcp bpcd odlid 13706 tcp odid bprd 13720 tc
9. Media Manager Status Code 96 Message oprd returned abnormal status Explanation A request serviced by oprd the operator request daemon process or by rdevmi the remote device management interface returned an abnormal status Recommended Action 1 On Windows when auto configuring devices or initiating the NetBackup Device Manager service from a graphical or command line interface ensure that the service has not been disabled in the system services configuration Chapter 5 Media Manager Status Codes and Messages 249 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 3 Operator request daemon process and remote device management errors are generally accompanied by device management related errors that have occurred on a particular host Check for errors in the debug and system application logs on the host where oprd or rdevmi was started or running which is often a targeted device host or scan host The kinds of requests ser
10. Recommended Action Create a scratch pool with a different name Media Manager Status Code 174 Message unable to link to dynamic library Chapter 5 Media Manager Status Codes and Messages 233 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation An attempt to open and link to a dynamic library failed This may be caused by a missing or unusable dynamic library for the EMC Symmetrix API The error may be generated at both the server and the client the dynamic libraries are used by the 1tid tldd and bptm processes Recommended Action Make sure that the EMC supplied files usr symapi shlib libsymapi so and usr symapi shlib libsymlvm so exist on the system that reported the error For new copies of these files contact EMC wr 284 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Configuration Status Codes These status codes appear in exit status and command output for the tpconfig and tpautoconf commands and in system or debug logs These codes are also presented by programs that call tpconfig and tpautoconf such as media and device management user interfaces and the vmopremd command Device Configuration Status Code 0 Message Success Explanation A requested operation was successfully completed Recommen
11. failed trying to allocate memory NetBackup Status Code 36 failed trying to exec a command NetBackup Status Code 29 failed trying to fork a process NetBackup Status Code 28 failed waiting for child process NetBackup Status Code 34 failed while trying to send mail NetBackup Status Code 33 fatal NB media database error NetBackup Status Code 91 File already exists file_name NetBackup Status Code 510 file close failed NetBackup Status Code 15 file does not exist NetBackup Status Code 142 Chapter 4 NetBackup Status Codes and Messages 183 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages file open failed NetBackup Status Code 12 file path specified is not absolute NetBackup Status Code 141 file pathname exceeds the maximum length allowed NetBackup Status Code 105 file read failed NetBackup Status Code 13 file write failed NetBackup Status Code 14 found no images or media matching the selection criteria NetBackup Status Code 190 getservbyname failed NetBackup Status Code 19 handshaking failed with server backup restore manager NetBackup Status Code 201 host is unreachable NetBackup Status Code 47 inadequate buffer space NetBackup Status Code 235 Incorrect password NetBackup Status Code 504 184 NetBackup Troubleshooting Guide Windows NT 2000 Ne
12. install_path Volmgr debug daemon Debug information on the service install_path Volmgr debug reqlib Debug information on the process requesting the service install_path Volmgr debug tpcommand Debug information on the tpconfig and tpautoconf commands install_path Volmgr debug 1tid Debug information on 1tid NetBackup creates one log per day in each of the above debug directories with file names of the form mmadyy log For example 110894 log To disable debug logging for the NetBackup Volume Manager service either delete or rename the directories Windows Event Viewer Logging Option NetBackup Windows master servers can be configured so messages from NetBackup reports are written to the Windows Event Viewer Application Log This allows you to see these messages in the Application Log and also to use third party tools to monitor the Application Log for these messages Chapter 3 Using the Logs and Reports 49 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Windows 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 event 1og 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
13. 1 On the NetBackup server use bpclntcmd hn to verify that the operating system can resolve the host name of the NetBackup client as configured in the client list for the policy to an IP address The IP address is then used in the node s routing tables to route a network message from the NetBackup server 2 On the NetBackup client use bpclntcmd ip to verify that the operating system can resolve the IP address of the NetBackup server the IP address is in the message that arrives at the client s network interface bpclntcmd pn When run on a NetBackup client the pn option initiates an inquiry to the NetBackup master server and the server then returns information to the requesting client First bpclntcmd identifies the server to which it is making the request Current Server in the server list then it displays the information that the server returns For example bpclntcmd pn expecting response from server rabbit friendlyanimals com dove friendlyanimals com dove 123 145 167 3 57141 Where expecting response from server rabbit friendlyanimals comis 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 policy client list 123 145 167 3 is the IP address of the client connection at the master server
14. 392 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages The external_drive_mappings file has invalid license info Device Configuration Status Code 3 The external_robot_mappings file has invalid license info Device Configuration Status Code 2 the global device database device name is invalid Media Manager Status Code 162 the global device database device serial number is invalid Media Manager Status Code 161 the global device database device type is invalid Media Manager Status Code 160 The global device database hostname is invalid Device Configuration Status Code 49 The global device database version is incompatible Device Configuration Status Code 4 the requested slot is empty Media Manager Status Code 100 the robotic daemon returned an invalid volume GUID Media Manager Status Code 164 the specified pool is not empty Media Manager Status Code 111 the volume guid is not unique in the database Media Manager Status Code 159 Chapter 5 Media Manager Status Codes and Messages 39 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages this machine is not the volume database host Media Manager Status Code 84 This robot type does not support multiple media types Device Configuration Status Code
15. In the case of long device discovery cycles the interface may timeout or the user may cancel the process Part of the timeout or cancelling is to remove the lockfile This tells the device discovery process that it should not continue making modifications to the device configuration If this happens re run the discovery process 4 Global device database inconsistency Prior to beginning the process of discovering new devices on a host the global device database is checked for internal consistency The following are example log messages in the tpcommand log directory along with steps to determine the problem and correct it Fatal Global Database consistency error Couldn t contact robot 1 on host mud The global device database has found a robot entry for robot 1 on mud but could not communicate with it Delete that robot on host mud and re run device discovery there Fatal Global Database consistency error TLM ACS control host mismatch 1 on hosts bison and mud ww 300 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes The global device database has found TLM or ACS robot entries for robot 1 on hosts bison and mud but their ACSLS Host or DAS Server did not agree Determine which host is running the ACS library software or the DAS software Using tpconf ig or the administration console update the robot e
16. Media Manager Reference Topics in the NetBackup Media Manager System Administrator s Guide Media Manager Status Code 141 Message invalid number of mounts Explanation A request was made to change the number of times that a volume has been mounted and the value specified was not within the acceptable range Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Specify a number of mounts value within the acceptable range of 0 to 2 147 483 647 Media Manager Status Code 142 Message invalid offsite location Explanation The offsite location for a volume exceeds 25 ASCII characters in length or contains unprintable characters Recommended Action When adding or changing a volume record ensure that the offsite location field contains only printable characters and does not exceed 25 ASCII characters in length Media Manager Status Code 143 Message invalid of
17. Recommended Action Examine command output if available debug logs and system logs for messages related to the error 1 Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available 2 Retry the operation and examine the logs Device Management Status Code 11 Message One implicit reserve already exists Explanation A tape mount has been requested with an unsupported option Chapter 5 Media Manager Status Codes and Messages 317 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Verify that the installed software components are all at a compatible release version Device Management Status Code 12 Message Invalid Operator Explanation An internal list of operators could not be obtained Recommended Action This is an unexpected internal error Stop and restart 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Device Management Status Code 13 Message Error in IPC SHMGET call Explanation A process was unable to get a shared memory identifier associated with a segment of shared memory that 1tid maintains 1tid is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on
18. Server NetWare Client For details on the server processes see Backups and Archives UNIX NetBackup Clients earlier in this chapter User Interface Request NBNW95 NetWare nontarget on 95 98 NBNWNT NetWare nontarget on NT 2000 BP NetWare target e Information Client Disk 428 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter Client NetBackup User Interface Request A NetBackupBPBACKUP Fi le Information NetBackupListen NetBackupBPCD Client Disk NetBackupBPBACKUP is a faceless background application that NetBackup launches in order to start a user directed backup The application extension NetBackupListen starts executing when the Macintosh is booted and listens on the BPCD port number for backup requests from a NetBackup server When NetBackupListen gets a request it launches the faceless background application NetBackup
19. Status Codes 5 Verify that the robot number and host in the storage unit configuration matches what is specified in the Media Manager device configuration 6 Verify that the master server can communicate with the bpcd process on the server that has the storage unit a Verify that bpcd is listening on the port for connections On a Windows 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 debug log directories and retry the operation Check the resulting debug logs for records of an earlier failure After each backup the scheduler checks the storage unit to see how many drives are available in case the backup caused a drive to be automatically downed If bpsched cannot communicate with bpcd it sets the number of available drives in that storage unit to 0 and further backups to that storage unit during this backup session will fail The number of available drives remains at 0 until the scheduler is initialized again c Ifthe cause of the problem is not obvious perform some of the steps in Resolving Network Communication Problems on page 21 NetBackup Status Code 220 Message database system error Explanation The bpdbm process NetBackup Database Manager
20. The browsing is done through the bplist program on the client The bplist program can be started directly from the command line and is used by the NetBackup user interface programs bplist obtains the file list by sending a query to the request daemon bprd on the master server Figure 10 The request daemon in turn queries bpdbm for the information and transmits it to bplist on the client Figure 10 List Operation UNIX Client Master Server UNIX Client NetBackup command User Interface jing Fs list C totes When the user starts a restore NetBackup invokes the client s bprestore program which sends a request to the request daemon bprd Figure 11 This request identifies the files and client The request daemon then uses bpcd client daemon to start the backup restore manager bpbrm co File Database File list NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 The backup restore manager starts the appropriate media manager process bptm for tape or optical or bpdm for disk and uses the client d
21. Using the Host Properties Window on page 40 b On Macintosh clients check the server and client name entries in the bp conf file Ensure there isa SERVER entry for the master server and each media server in the configuration The master server must be the first name in the list Ensure that the CLIENT_NAME option if included is correct and matches what is in the policy client list on the master server The bp conf file is in the NetBackup folder of the Preferences folder on Macintosh clients c On NetWare clients check the openv netback bp ini file to ensure that There is a SERVER entry for the master server and each media server in the configuration The master server must be the first name in the list The ClientName entry and the entries in the clients section are correct and match what is in the policy client list on the master server d On the master server verify that you have created any required install_path NetBackup db altnames files 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 These numbers must be the sa
22. b Retry the operation and examine the logs 2 Specify a maximum mounts value within the range of 0 to 2 147 483 647 Device Management Status Code 37 Message Drive being assigned is either not NDMP or on the wrong NDMP client Explanation A mount request has been canceled because of the following the request was targeted to a drive configured as attached to an NDMP client but the request was manually assigned to a drive other than the requested drive and the assigned drive is either not NDMP or it is an NDMP drive configured to a different client Recommended Action Display the device configuration to determine which drives are configured as being attached to specific NDMP clients Ensure that 1t id was stopped and restarted after the last configuration changes were made Reissue the request and assign it to a drive attached to the requested NDMP client Device Management Status Code 38 Message Character device name for drive is not a character device Explanation On a tape mount request the configured tape drive s no rewind on close device file was neither a character special device nor of a known type such as NDMP which does not need to be a character special file On an optical mount request the optical disk drive character device file was not a character special device Recommended Action 1 To avoid configuring invalid device paths and device names use the Device Configuration wizard on supported device discovery
23. 3 Retry the operation and examine the logs 4 Ensure that there are no embedded whitespaces in fields that do not allow embedded whitespace NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 5 Check the system log on the robot control host for errors logged by the robotic software Media Manager Status Code 47 Message no entries changed Explanation A requested operation was completed but no changes to the volume configuration or Media Manager configuration file were made The administrator may have aborted an operation instead of continuing with proposed changes or the configuration file may have already included the configuration entry that was being added Recommended Action 1 No action is needed if the administrator aborted the change operation 2 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Media Manager Status Code 48 Message no entries deleted Explanation A delete volume s operation c
24. Chapter 4 NetBackup Status Codes and Messages 161 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation This error occurs if the robotic library is not in a state to support ejecting media Possible reasons for this include The library is currently ejecting media The library is pending ejecting media The library is currently injecting media The library is pending injecting media Recommended Action Wait until the robotic library can support the eject action and rerun the vault session vlteject command or vltopmenu command NetBackup Status Code 299 Message there is no available MAP for ejecting Explanation The robotic library you are vaulting from does not have a MAP available for use and so media cannot be ejected Recommended Action Wait until the robotic library s MAP is available for use and rerun the vault session vlteject command or vltopmenu command NetBackup Status Code 300 Message vmchange eject verify not responding Explanation During the eject process the vmchange command is called with a verify_eject call until all of the volumes for the request are in the MAP This command call failed or did not return the proper information to the vault eject process Recommended Action For detailed information about why the process failed review the vault debug log in the following directory UNIX usr openv net
25. NetBackup 4 5 Troubleshooting Guide for Windows VERITAS NetBackup 4 5 Troubleshooting Guide for Windows March 2002 30 000524 011 VERITAS NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 Copyright Copyright 1998 2002 VERITAS Software Corporation All Rights Reserved VERITAS VERITAS SOFTWARE the VERITAS logo Business Without Interruption VERITAS The Data Availability Company VERITAS NetBackup VERITAS NetBackup BusinesServer VERITAS Remote Storage for Microsoft Exchange VERITAS Storage Migrator and VERITAS Storage Migrator Remote are trademarks or registered trademarks of VERITAS Software Corporation in the U S and or other countries Other product names mentioned herein may be trademarks or registered trademarks of their respective companies Portions of this software are derived from the RSA Data Security Inc MD5 Message Digest Algorithm Copyright 1991 92 RSA Data Securit
26. NetBackup Status Code 169 media id is not in NetBackup volume pool NetBackup Status Code 178 media id must be 6 or less characters NetBackup Status Code 171 Media Manager device daemon Itid is not active NetBackup Status Code 80 Media Manager volume daemon vmd is not active NetBackup Status Code 81 wr 186 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages media manager detected image that was not in tar format NetBackup Status Code 92 media manager found wrong tape in drive NetBackup Status Code 93 media manager killed by signal NetBackup Status Code 82 media manager received no data for backup image NetBackup Status Code 90 media manager system error occurred NetBackup Status Code 174 media open error NetBackup Status Code 83 media position error NetBackup Status Code 86 media read error NetBackup Status Code 85 media write error NetBackup Status Code 84 NB database backup failed a path was not found or is inaccessible NetBackup Status Code 124 NB database backup header is too large too many paths specified NetBackup Status Code 126 Chapter 4 NetBackup Status Codes and Messages 187 NetBackup 4 5 Troubleshooting Guide for Windows Messages NetBackup 4 5 Troubleshooting Guide for Windows NB databas
27. Recommended Action Remove all but two drives Message Too many slots in robot Explanation The robotic library has more than 30 installed slots the maximum allowed with a NetBackup BusinesServer license Recommended Action If possible configure the robotic library to have 30 or fewer slots Only use robotic libraries that are supported with NetBackup BusinessServer Message No license for this robot type Explanation The robotic type defined for this robot is not supported by NetBackup BusinesServer Recommended Action Define a different robot Only use robotic libraries that are supported with NetBackup BusinessServer Message No license for this drive type Explanation The drive type defined for this drive is not supported by NetBackup BusinesServer Recommended Action Define a different drive Only use drives that are supported by NetBackup _ 4 Chapter 2 Troubleshooting Procedures I ao NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Configuration Problems Message Unable to determine robot type Explanation The robotic library is not recognized by NetBackup The robotic library cannot be auto configured Recommended Action 1 Download a new external robot mapping file from the VERITAS support web site and try again 2 Configure the robotic library manually 3 Use only robotic libraries that are sup
28. Started By From the Windows Start menu under Programs NetBackup Stopped By Exiting the client user interface Debug Log none A faceless background application installed in the System Extensions folder on the startup volume of a Macintosh client The Macintosh equivalents of the UNIX bpbkar and tar commands are merged into NetBackupBPCD Started By When NetBackupListen receives a request from a server it launches NetBackupBPCD Stopped By Completion of operation Debug Log Log files in the System Preferences NetBackup bpcd folder which is in the NetBackup folder in the Preferences folder in the System folder on the startup volume NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Description Daemon NetBackupListen An applications extension installed in the System Extensions folder on the startup volume of a Macintosh client It starts when the Macintosh is booted and runs in the background until the Macintosh is shut down NetBackupListen listens on the BPCD port number for requests from NetBackup servers and launches NetBackupBPCD when a request is received Started By When the Macintosh boots Stopped By When the Macintosh is shut down Debug Log Log files in the System Preferences
29. Status Codes Media Manager Status Code 21 Message cannot obtain daemon lockfile Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows could not obtain an internal software lock Recommended Action Check for the existence and permissions of the lock file itself and the lock file directory which is usr openv volmgr misc vmd lock UNIX or install_path Volmgr misc vmd lock Windows Create the directory folder and adjust the permissions as needed so that vmd can obtain the lock which is usr openv volmgr misc vmd lock UNIX or install_path Volmgr misc vmd lock Windows Media Manager Status Code 22 Message database initialization failed Explanation Initialization problems were encountered in the robotic test utility while trying to read the device databases This is a generic return code for device database related issues Recommended Action Check the command output for detailed errors Use the tpconfig interface or another device management interface to verify database access and integrity Media Manager Status Code 23 Message database close operation failed Explanation An error occurred when vmd attempted to close the volume database Recommended Action Examine the daemon debug log for a more detailed message on the system error as follows 1 Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the leve
30. b Retry the operation and examine the logs 2 Ensure that the media ID where requested is not blank NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 Ensure that the specified media IDs contain valid characters only alphanumeric characters and the period plus sign and underscore _ A hyphen is also a valid character when not the first character in the media ID 4 If the media is for optical disk ensure that the media ID of the optical partner is specified and contains only valid characters 5 Ifthe media ID is for optical disk ina TLM robot ensure that the format of the ID and partner are Axxxxxx and Bxxxxx respectively 6 If media are specified to be ejected from a library ensure that they exist in the volume database and are associated with the correct robot number 7 Ensure that the media ID is from 1 to 6 characters in length 8 Ensure that a valid media and seed were specified 9 Ifthe operation is an inventory request for an ACS robot use the robtest utility to verify that the ACS interface is returning cleaning media IDs both in the query volume list and in the query cleaning volume list Media Manager Status Code 9 Message invalid media type Explanation A process performing a media related operation encountered an unknown missing or incompatible m
31. lt 4 gt bpbkar Exit INF EXIT STATUS 227 no entity was found 15773 lt 2 gt bpbkar Exit INF Close of stdout This shows that a particular device cannot be found in the 3pc conf file on the media server 14 47 02 031 15773 lt 16 gt bpmap_send_extend ERR can t obtain device id string EMC SYMMETRIX 601092014000 The problem is one of the following The 3pc file conf file on the media server is outdated Recreate the 3pc conf The media server is not on the same fibre channel network as the third party copy device and client disk As a result the 3pc conf file does not have a correct entry for the client disk Run the bptpcinfo command with the x Client_ each disk name option this adds the client disk to the 3pc conf file For added to the file by means of bptpcinfo x client_name you must add the device s world wide name wwn as explained in the NetBackup ServerFree Agent System Administrator s Guide 4 Compare the NetBackup version level on the server to that on the clients On Windows NetBackup servers check the install_path netbackup version txt file or the About NetBackup item on the Help menu Chapter 4 NetBackup Status Codes and Messages ZA eS NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows On Microsoft Windows clients check the About NetBackup item on the Help menu On NetWare tar
32. the socket read may have failed because the requested operation did not complete within a specified time period Some requests to vmd can be affected by robotic process and vmd interactions so check the system log for errors on the robotic control host Media Manager Status Code 73 Message invalid query type Explanation An invalid volume query request was attempted Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Verify that all Media Manager and user interface binaries are at a compatible version level Media Manager Status Code 74 Message invalid number of cleanings Explanation A request was made to change the number of cleanings remaining for one or more volumes in the volume configuration and the value specified was not within the acceptable range The number of cleanings value may also be invalid in the number of mounts cleanings field of a barcode rule Chapter 5 Media Manager Status Codes and Messages 237 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide fo
33. volume Media Manager volumes are logical units of data storage or cleaning capability on media that have been assigned media IDs and other attributes which are recorded in the Media Manager volume database volume configuration Refers to configuration information that is stored in the Media Manager volume database volume database An internal database where Media Manager keeps information about volumes All hosts where Media Manager is installed have a volume database However the database is empty unless the host is designated as a volume database host volume database host The host where Media Manager is installed that contains information about the volumes that Media Manager uses in a device Because NetBackup BusinesServer supports only a single server the volume database host is always on the same server volume group A set of volumes that are configured within Media Manager to reside at the same physical location for example in a specific robot volume pool A set of volumes that are configured within Media Manager to be used by a single application and are protected from access by other applications and users wakeup interval The time interval at which NetBackup checks for backups that are due wr 518 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows wildcard characters A character that can be used to
34. 104 Message failed appending to pool database Explanation A request was made to add change or delete a volume pool in the volume pool configuration but a pool record could not be appended to the volume pool database file Chapter 5 Media Manager Status Codes and Messages 203 E NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Examine the permissions and available file system space for writing to the database on UNIX usr openv volmgr database poolDB on Windows install_path Volmgr database pool1DB Media Manager Status Code 105 Message poolname is not unique in pool database Explanation A request was made to add a volume pool in the volume pool configuration but the pool name specified was a duplicate of the name for an existing volume pool Recommended Action On the add volume pool request specify a volume pool name that is not already in use on the targeted volume database host Media Manager Status Code 106 Mes
35. After each backup the scheduler checks the storage unit to see how many drives are available in case the backup caused a drive to be automatically downed If bpsched cannot communicate with bpcd it sets the number of available drives in that storage unit to 0 and further backups to that storage unit fail The available drives remain at 0 until the scheduler is initialized again Therefore even if bpcd seems to be operating correctly now check the bpsched and bpcd debug logs see below for records of an earlier failure 4 See Testing Media Server and Clients on page 19 and Resolving Network Communication Problems on page 21 5 If necessary create debug log directories for the following processes and retry the operation Then check the resulting debug logs on the master server Ifthe error occurred during a backup operation check the bpsched debug logs Also check the bpcd debug logs Ifthe error occurred during a restore operation check the bprd debug logs NetBackup Status Code 203 Message server backup restore manager s network is unreachable Explanation A process on the master server could not connect to a particular host on the network when trying to initiate communication with the media host for a particular operation This problem can occur during a backup or restore in either a single or multiple server configuration Recommended Action Determine which activity encountered the network unreachable
36. Also configure a volume in the NetBackup volume pool and insert the volume in the drive If you don t label the volume by using the bplabel command NetBackup automatically assigns a previously unused media ID 3 Verify that the NetBackup services are running on the master server NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel 4 Start a manual backup of a policy by using the manual backup option in the NetBackup administration interface Then restore the backup This verifies NetBackup server software is functional including all services programs and databases Media Manager can mount the media and use the drive you configured If a failure occurs first check the NetBackup All Log Entries report For failures relating to drives or media verify that the drive is in an UP state and the hardware is functioning To further isolate the problem use the debug logs If the debug logs do not reveal the problem check the following Event Viewer System logs Event Viewer Application logs vmd debug logs on the volume database host for the device bptm debug logs See the vendor manuals for information on hardware failures If you are using a robot and this is an initi
37. Error can t get GUID from Backup Exec media id BEOOO1 1600 4028 lt 16 gt MediaID2MediaGuid couldn t obtain media guid for The following is an example bptm log on the media server that contains the Backup Exec catalogs corresponding to the image 16 26 03 411 Error number 16 26 03 411 status 16 26 03 421 3672 3924 10061 3672 3924 cannot connect to vmd 3672 3924 cannot connect to vmd host 70 dell 2 lt 16 gt vmd_connect unable to connect to vmd lt 16 gt query_one_volume query_onevol request lt 16 gt GetMediaGuid Media Manager error 70 The bptm log above indicates that it could not connect to vmd perhaps because vmd was not running Example 3 If the Backup Exec services are not running on the media server that contains the Backup Exec catalogs corresponding to the image the progress log contains the following text 16 21 14 12 7 2001 16 21 16 16221217 97 xxx 97 001 Restore Started Media id BE0001 is needed for the restore Restoring from image created 12 07 2001 01 31 38 PM NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs 16 16 6 16 6 LGs 16 L6 16 I6 I6 16 26 26 26 226 26 22673 16 26 26 26 26 26 26 26 16 L6 01 16 214 19 21 1
38. Explanation A process was unable to perform a semaphore operation such as lock or unlock associated with resources maintained by 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Recommended Action Chapter 5 Media Manager Status Codes and Messages 325 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Device Management Status Code 35 Message Request terminated because media is unavailable in DOWN drive misplaced write protected or unmountable Explanation A mount request has been canceled because the media being requested is not available It may be in a DOWN drive misplaced write protected or unmountable Recommended Action Use robotic inventory or manual means to compare the contents of media in the robotic library with the volume configuration and update the configuration as needed Determine t
39. INF fsclone_freeze Cannot create checkpoint status 17 15 21 45 872 4236 lt 4 gt delete _mount_point INF Deleted mount point tmp _vtrax_test_fastrax_d1lt 4236 15 21 45 873 4236 lt 32 gt onlfi_ freeze FTL V MS error 11 see following messages 15 21 45 873 4236 lt 32 gt onlfi_ freeze FTL Fatal method error was reported 15 21 45 873 4236 lt 32 gt onlfi_freeze FTL vfm_freeze method fsclone type FIM function fsclone freeze 15 21 45 873 4236 lt 32 gt onlfi_freeze FTL VfMS method error 17 see following message 15 21 45 874 4236 lt 32 gt onlfi_freeze FTL fsclone_ freeze Cannot create checkpoint status 17 Remove the clone as follows Note If the clone is not removed you will not be able to use fsclone to back up any data in the file system where the clone is mounted a List the name of the clone by entering the following VxFS command usr lib fs vxfs fsckptadm list file_system where file_system is the name of the file system where the clone is mounted Following is sample output In this example vtrax_test is the file system and fi_ckpt is the name of the clone vtrax_test fi_ckpt ctime Mon Nov 12 10 08 13 2001 mtime Mon Nov 12 10 08 13 2001 flags largefiles b Remove the clone by entering the following usr lib fs vxfs fsckptadm remove name_of_clone file_system c Ifthe clone cannot be removed unmount the clone and retry step b Chapt
40. If it is not running start it To enable verbose logging place VERBOSE on a line by itself in the install_path Volmgr vm conf file before starting the service Note The NetBackup Device Manager service is used only if devices are attached to the system NetBackup Status Code 81 Message Media Manager volume daemon vmd is not active 98 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation The tape manager bptm could not communicate with the NetBackup Volume Manager service This communication is required for most operations Recommended Action On Windows verify that both the NetBackup Device Manager service and the NetBackup Volume Manager service are running Start them if necessary Note The NetBackup Device Manager service is used only if devices are attached to the system NetBackup Status Code 82 Message media manager killed by signal Explanation The tape manager bptm or disk manager bpdm was terminated by another process or a user Recommended Action This should not occur in normal operation If you want to terminate an active backup use the NetBackup Activity Monitor NetBackup Status Code 83 Message media open error Explanation The tape manager bptm or disk manager bpdm could not open the device or file that the backup or restore must use Reco
41. Logon as account that has permission to create the directory 3 For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Status Code 36 Message failed trying to allocate memory Explanation Allocation of system memory failed This error occurs when there is insufficient system memory available This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory Recommended Action Free up memory by terminating unneeded processes that consume a lot of memory Add more swap space or physical memory NetBackup Status Code 37 Message operation requested by an invalid server Chapter 4 NetBackup Status Codes and Messages 79 O NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A request was made to the NetBackup Request Manager service or NetBackup Database Manager service by an invalid media server or Windows NetBackup Remote Administration Console Recommended Action Examine the NetBackup All Log Entries report for the time of this error to determine which system was trying to connect to the master server If the server is a valid media server verify that the storage unit for the media server is defined Also verify that the server or Windows NetBackup R
42. Media Manager 458 NetWare nontarget clients 72 NetWare target clients 72 UNIX client server 440 Windows clients 72 Windows NT servers 71 stale snapshots 62 Startup Media Manager process 451 NetBackup 420 status code finding message from 55 Status codes NetBackup sorted by code 55 sorted by message 173 364 stderr 51 stdout 51 SuSE 10 symbolic links 60 SYMINIT failed 64 tape reader Backup Exec 473 tar log 47 tar NetBackup 449 TAR32 436 Test utility robotic 471 third party copy 123 and multiplexing 71 tl4d description 461 tl4test 472 tl8cd description 462 tl8d description 461 tl8test 472 tldd description 462 tldtest 472 tlhed description 463 tlhd description 463 tlhtest 472 tlldcd description 462 tlmd description 463 tpautoconf 304 tpcommand 287 tpconfig overview 464 Troubleshooting procedure communication problems PC clients 21 general introduction 16 master server and clients 16 19 media server and clients 19 host name and services entries 25 installation 10 preliminary 7 ts8d description 465 ts8test 472 tsdd description 464 tsdtest 472 tshd description 464 user_ops log 45 Utility robotic test 471 vault 56 Verbose option 46 VERITAS NetBackup ix NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows VERITAS Volume Manager 61 Version software see Software version det
43. Media Manager Status Code 98 Message rule database truncate operation failed Explanation The system call Etruncate 3C failed during an attempt to rewrite the barcode rule database during a barcode rule change delete operation Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the system error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Investigate the integrity of the file system and barcode rule database on UNIX usr openv volmgr database ruleDB on Windows install_path Volmgr database ruleDB Media Manager Status Code 99 Message user is not valid for this host Explanation A request was made to add or change a volume pool and the specified UNIX user ID could not be found on the system that originated the request Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose optio
44. Media Manager Status Code 89 barcode does not exist in database Media Manager Status Code 78 barcode label is unreadable Robotic Status Code 235 barcode not unique in database Media Manager Status Code 36 Chapter 5 Media Manager Status Codes and Messages 365 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages barcode tag is not unique in rule database Media Manager Status Code 122 Block device name for optical disk is not a block device Device Management Status Code 54 cannot allocate requested memory Media Manager Status Code 18 Cannot assign a robotically controlled device Device Management Status Code 64 Cannot assign due to media ID mismatch Device Management Status Code 57 cannot auto eject this robot type Media Manager Status Code 51 cannot auto inject this robot type Media Manager Status Code 52 Cannot backup restore global device database files Device Configuration Status Code 47 Cannot backup restore local device database files Device Configuration Status Code 43 Cannot change terminal mode Device Configuration Status Code 41 cannot change volume pool for assigned volume Media Manager Status Code 91 wr 366 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages
45. NetBackup inetd folder on the startup volume tar On UNIX clients the Tape ARchive program is a special version of tar provided with NetBackup and used to restore images Started By For each restore bpbrm starts an instance of tar on the client Stopped By Completion of restore operation Debug Log tar 1og on the client TAR32 On Windows 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 Debug Log TAR LOG in the NetBackup logs directory on the client xbp Graphical display based client user interface on UNIX clients with options for starting user directed backups restores and archives Functionally it is very similar to the menu version bp Started By usr openv netbackup bin xbp command on the client Stopped By Quit option in xbp Debug Log None although the log for the bpbbackup bparchive bplist and bprestore commands on the client may also be useful for debugging problems with xbp Appendix A Functional Overview 449 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description NetBackup Databases Table 7 describes the NetBackup databases These databases contain information that is used internally by NetBackup and reside in
46. NetBackup Status Code 51 Message timed out waiting for database information Explanation The catalog process did not respond within five minutes Recommended Action 1 Verify that the NetBackup Database Manager service is running 2 Verify that there is space in the file system that contains the NetBackup catalogs 3 Create bpbrm and bpdbm debug log directories on the server and retry the operation 4 Look in the debug log files to find more information on the problem NetBackup Status Code 52 Message timed out waiting for media manager to mount volume Explanation The requested volume was not mounted before the timeout expired This error can also occur if the volume happens to be a cleaning tape but was not specified as a cleaning tape Another possible cause if the last available drive has a mount request for a non backup such as a restore then a backup requiring the same drive is initiated before the mount completes This is due to the drive not being reported as busy until the mount completes Recommended Action Chapter 4 NetBackup Status Codes and Messages sy a NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Verify that the requested volume is available and an appropriate drive is ready and in the UP state 2 If this occurs during a read operation restore duplicate verify the drives could be busy Try increasing the media mou
47. On Windows 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 policy On Macintosh clients check the version file in the bin folder in the NetBackup folder in the Preferences folder 2 Ifthe problem persists save all error information and call customer support NetBackup Status Code 236 Message the specified client does not exist in an active policy within the configuration database Explanation A client name was not specified or the specified client does not exist Recommended Action Activate the required policy correct the client name or add the client to a policy that meets your needs After making the correction retry the operation NetBackup Status Code 237 Message the specified schedule does not exist in an active policy in the configuration database Explanation The specified schedule does not exist in the NetBackup configuration Recommended Action Activate the required policy correct the schedule name or create a schedule in a policy that meets your needs After making the correction retry the operation NetBackup Status Code 238 Message the database contains conflicting or erroneous entries
48. 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 A platform does not support a device or was not configured to recognize it 2 Check for the following problems with the services Services do not start during reboot configure system so this occurs Configuration was changed while services were running The SystemRoot System32 drivers etc services file does not have an entry for vmd bprd bpdbm and bpcd Also ensure there are entries for the processes for configured robots see the Media Manager System Administrator s Guide for Windows for a list of these processes nl Chapter 2 Troubleshooting Procedures 1 oy NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Configuration Problems 3 If you found and corrected any configuration problems retry the operation and check for NetBackup status codes or messages 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 r
49. Then check the resulting debug logs NetBackup Status Code 217 Message failed reading storage unit database information Explanation During its periodic checking of the NetBackup configuration the NetBackup scheduler process bpsched could not read the storage unit configuration Recommended Action 1 Verify that the NetBackup Database Manager service is running 2 Attempt to view the storage unit configuration by using the NetBackup administration interface 3 For detailed troubleshooting information create debug logs for bpsched and bpdbm on the master server and retry the operation Then check the resulting debug logs NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Ensure that the correct master server is being specified for the connection NetBackup Status Code 218 Message failed reading policy database information Explanation During the periodic checking of the NetBackup configuration the NetBackup scheduler process bpsched could not read the policy backup policy configuration Recommended Action 1 Verify that the NetBackup Database Manager service is running 2 Attempt to view the policy configuration by using the NetBackup administration interface 3 For detailed troubleshooting information create debug log directories for bpsched and bpdbm on the master server and ret
50. Verify that the correct client and server host names are configured in NetBackup a On Windows servers Windows clients and NetWare nontarget clients check the General tab in the NetBackup Client Properties dialog and the Servers tab in the Specify NetBackup Machines dialog box To display these dialog boxes start the Backup Archive and Restore interface on the client For the General tab click NetBackup Client Properties on the File menu for the Servers tab click Specify NetBackup Machines on the File menu On the Servers tab ensure that there is a server entry for the master server and each media server Chapter 2 Troubleshooting Procedures 200 ee NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures The correct server must be designated as the current master server in the list If you add or modify server entries on the master server stop and restart the NetBackup Request service and NetBackup Database Manager services On the General tab verify that the client name setting is correct and matches what is in the policy client list on the master server Ona master or media server ensure there is a server entry for each Windows administrative client that can be used to administer that server You can also make the above changes on the appropriate tabs in the properties dialog boxes on a Windows NetBackup server see
51. access mode Device Management Status Code 47 Message Unable to establish scan host for shared drive Explanation On a request to change a shared drive s status an attempt to establish a connection to the drive s scan host failed Recommended Action 1 Determine which host is serving as the drive s scan host Do this by sending a vmdareg command to the volume database host for the drives s residence robot or set of standalone drives on a host 2 Ensure that vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows is running on the scan host On the scan host examine debug logs and system logs for messages related to the error 3 Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting Itid the device daemon on UNIX or NetBackup Device Manager service on Windows The detailed reason for the canceled request should be available in the daemon debug logs on the scan host Correct the problem and resubmit the request if needed Device Management Status Code 48 Message Host is not the scan host for this shared drive NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation On a request to assign reserve or scan a drive the targeted device host de
52. bpcd 13782 tcp bpcd bord 13720 tcp bprd Notes 1 The NetBackup Client Properties dialog also has a Network tab with NetBackup client service port BPCD and NetBackup request service port BPRD settings that must be the same as the bpcd and bprd settings in the services file 2 The complete path to the Windows NT 2000 etc services file is SystemRoot system32 drivers etc services 3 All other applicable network configuration must also be updated to reflect the NetBackup information For example this could include the SystemRoot system32 drivers etc hosts file and also WIN and DNS if used Chapter 2 Troubleshooting Procedures NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Using the Host Properties Window Using the Host Properties Window Note Available only in the NetBackup Administration Console for Windows The Host Properties window in the NetBackup Administration console on Windows 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 The following are general instructions for using this window For more information see the online help or the NetBackup System Administrator s Guide for Windows 1 Start the NetBackup Administration interface on a Windows server or on a NetBack
53. check the debug logs for the involved processes If the debug logs don t help you check the following 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 If you previously configured a nonrobotic drive and a robot attached to your media server change the test policy to name the robot Also add a volume for the robot to the volume database host for the robot Verify that the volume is in the NetBackup volume pool and in the robot Then repeat this procedure starting with step 3 this time for a robot This verifies that Media Manager can find the volume mount it and use the robotic drive If a failure occurs check the NetBackup All Log Entries report Look for errors relating to devices or media If the All Log Entries report doesn t help check vmd debug logs on the volume database host for the robot NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Event Viewer Application log In an initial configuration verify that the robotic d
54. dor other means to see the list of valid drives Specify the drive name or index as appropriate for the interface being used Device Management Status Code 24 Message Requested drive could not be reserved Explanation An attempt was made to reserve a shared drive but the drive reservation request failed This status code is related to the internal implementation of the SSO feature not SCSI Reserve Release Recommended Action This is an expected condition for shared drives which will be automatically retried If problems persist verify that vmd DA is servicing requests and is not listing drives as reserved to hosts that are not currently using the drives vmd DA is the Media Manager device daemon device allocator on UNIX and the NetBackup Device Manager service device allocator on Windows Clear out extraneous reservations by re starting 1t id on the host that has the drive reservation As an alternative use vmdareq release plus other arguments and then retry the request Device Management Status Code 25 Message File name does not exist Explanation A logical tape file or help file could not be found The tpunmount command was probably issued with a logical tape file specified that does not exist for this user Recommended Action Check for existence of the logical tape file at the file path specified The specified file path must match the exact case sensitive path used when the tape mount was requested Resubmit the request
55. if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that change volume residence requests with inject for the robot type involved with a newer release version level are not sent to vmd on a system running an older incompatible software version level Media Manager Status Code 53 Message invalid volume move mode Explanation A robotic related request was made specifying a media movement option that is not supported by all affected software components Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that the robotic request is sent to a system running a release version of software that supports the particular request Media Manager Status Code 54 Message
56. inetd Stopped By Completion of operation Debug Log bpcd 1og on both client and server On NetWare clients this is the executable file that starts the NetBackup client daemon Started By When you start the Novell NetWare system if you add load bpcd to the AUTOEXEC NCF file Otherwise with the LOAD BPCD command Stopped By UNLOAD BP command Debug Log BPCD LOG file in the NetBackup logs directory on the client On Windows 95 and NT 2000 clients this is the executable file that starts the NetBackup client daemon Started By When Windows starts if the daemon is in the Startup group Otherwise by double clicking on its icon Stopped By On Windows NT 2000 you can stop it through the Services application in the Control Panel On Windows 95 you can stop it by clicking on its icon and choosing Close Debug Log BPCD LOG file in the NetBackup logs directory on the client On UNIX master servers this program is used to clean up the NetBackup jobs database Started By usr openv netbackup bin admincmd bpdbjobs When bprd starts it runs this command automatically The administrator can also execute it manually or with a cron job Stopped By There is no terminate option for this command outside of using kill Debug Log bpdbjobs 1og on the server Appendix A Functional Overview NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functio
57. r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action When changing the media expiration provide the date in the format specified by the media management interface documentation Media Manager Status Code 114 Message invalid maximum mounts Explanation A request was made to change the limit for the number of times a volume can be mounted with write access for one or more volumes in the volume configuration but the value specified was not within the acceptable range The maximum number of mounts value may also be invalid in the number of mounts cleanings field of a barcode rule Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Specify a maximum mounts value within the range of 0 to 2 147 483 647 Media Manager Status Code 115 Message volume has passed expiration date Explanation A request was made to assign a volume and the volume expiration date has expired in relation to the current system date For optical media the volume partner e
58. receives the user request it starts bpsched which checks the policy configurations for schedules and by default chooses the first user directed schedule that it finds in a policy that includes the requesting client It is also possible to specify a policy and schedule by using the NetBackup configuration options BPBACKUP_POLICY and BPBACKUP_ SCHED on the client The bpbackup and bparchive programs execute with the same permissions as the user If you can read and write files delete in the case of an archive they can too G e e D 2 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Figure 7 Backup or Archive to Tape or Optical Server Master Server Backup Policy Management po Volume Configuration Database Database vmd Sig Master or Media Server New media ID for NB UNIX Client NetBackup Command User Interface Line bpbkar Client Notes Disk For detail on these components see the Media Manager Functional Tape or Optical Description later in this chapter yy Appendix A Functional Overview 423 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description For
59. requesters of vmd 1t id and device configuration The administrator must create these directories for debug logging to occur help Help files used by Media Manager programs These files are in ASCII format version Version and release date of the software vm conf Media manager configuration options misc Lock files and temporary files required by various components of Media Manager Programs and Daemons Table 9 describes the Media Manager programs and daemons The explanations include what starts and stops the program or daemon and the log if any where it records its activities On UNIX all of the components discussed in this table reside under usr openv volmgr bin On Windows they reside under install_path volmgr bin wr 458 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs Program Description Daemon acsd The Automated Cartridge System daemon interfaces with the Automated Cartridge System and communicates with the server that controls the ACS robotics through the acsssi process UNIX or the STK Libattach Service Windows Also for UNIX see the acsssi and acssel programs Started By Starting 1tid or on UNIX independently by using the usr openv volmgr bin ascd command Stopped By Stopping 1t id or on UNIX inde
60. the backup is complete This term can also refer to the collection of data that NetBackup saves for a client during a backup or archive For example duplicate the backup Backup is two words when used as a verb For example back up the file 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 Console 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 It has a character based menu interface that can be run from terminals that do not have X Windows capabilities bpadm An administrator utility that runs on NetBackup UNIX servers It has a character based menu interface that can be run from terminals that do not have X Windows capabilities bp conf file A NetBackup configuration file on UNIX servers and also on UNIX Macintosh and OS 2 clients bp ini file NetBackup initialization file for Novell NetWare target clients bpcd NetBackup Client service on Windows and the NetBackup Client daemon on UNIX Glossary 495 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows bprd NetBackup Request Manager service on Windows and NetBackup Request
61. version vm conf misc driver format goodies tpcommand Itid daemon reqlib _acssi 1 Created by administrator to enable debug logging 2 Created by administrator or automatically by media management utilities Appendix A Functional Overview 457 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 they not be moved to another host Table 8 Media Manager Directories and Files File or Directory Contents bin Commands scripts programs daemons and files required for Media Manager operation and administration There are three subdirectories under bin driver Contains SCSI drivers used on various platforms to control robotics format Disk format information for optical platters on Solaris platforms goodies Contains vmconf script and scan utility database Media Manager databases contain information about the drives robots and media that are under Media Manager control The volume database that usually resides on the master server contains volume information for multiple media servers debug Debug logs for the Media Manager volume daemon vma and all
62. 259 1522959 15 29 59 1542959 15 29 59 15 29 59 15 29 59 15 29 59 1529 59 15 29 59 T5295 9 1572959 15 29 59 15 29 59 15 29 59 15 30 00 BEopen file rec BEread_ file rec BEclose file rec 695 3292 3280 lt 2 gt bpcd main BPCD GET FILE REC ROQST 695 3292 3280 lt 2 gt bpcd_get_file rec received mediaid BE0001 695 3292 3280 lt 2 gt bpcd_get_file rec received keyword 22 695 3292 3280 lt 2 gt bpcd_ get file rec received path 695 3292 3280 lt 2 gt bpcd_get_file rec received client adaj 695 3292 3280 lt 2 gt bpcd_get_file rec received dirs only 0 695 3292 3280 lt 2 gt bpcd_get_file rec received depth 3 695 3292 3280 lt 2 gt createProcessWithOutput CreateProcess of gt D nb NetBackup bin bptm exe guid ev BEO001 cmd lt 975 3292 3280 lt 2 gt MediaID2MediaGuid Backup Exec media id BE0001 has guid 6EE3FFEF B111 4EDD 97C1 78931D988268 voldb dell 2 985 3292 3280 lt 2 gt bpcd_get_file rec Successfully loaded beutil dll 985 3292 3280 lt 2 gt bpcd_get_file rec Obtained pointer to 985 3292 3280 lt 2 gt bpcd_get_file rec Obtained pointer to 985 3292 3280 lt 2 gt bpcd_get_file rec Obtained pointer to 995 3292 3280 lt 16 gt BEopen file rec Unable to connect to the Backup Exec engine on the local host 995 3292 3280 lt 2 gt bpcd_get_file rec closing connection 005 3292 3280 lt 2 gt
63. 5 Troubleshooting Guide for Windows 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 The NetBackup client daemon is called BPCDW32 The bpbkar functions are merged into BPCDW32 The server processes are the same as described for UNIX Server Windows 95 98 Client For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter NetBackup User Interface File Information BPCDW32 a oo Client Disk 426 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 bpbbackup bparchive and bplist functions are merged into NBWIN
64. A volume entry being added to or changed in the volume database had an RSM GUID specified which was a duplicate of the RSM GUID for another volume already in the volume database All volumes in a volume database must have an RSM GUID that is either unique or null RSM is the Microsoft Removable Storage Manager and GUID isa Global Unique Identifier Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Try the following procedure a From the daemon debug log file determine the offset of the volume that has an RSM GUID conflict with the volume entry being added or changed The offset is the index of the volume in the volume database b Dump out all volume records in the volume configuration for the targeted volume database host using the vmdb_dump command Look up the volume offset indicated in the debug log file noting the associated RSM GUID which is the field volume_guid The condition may have occurred because the media name for a volume may have been changed in the RSM media configuration followed by a change to the volume configuration in Media Manag
65. Administrator s Guide for Windows for more information on the files and commands mentioned here 1 Ensure that the authentication libraries exist Windows install_path NetBackup 1lib libvopie d1ll install_path NetBackup 1lib libnoauth dl1ll UNIX except HP UX usr openv 1lib libvopie so usr openv 1lib libnoauth so UNIX HP UX only Chapter 4 NetBackup Status Codes and Messages 19 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows usr openv lib libvopie sl usr openv 1lib libnoauth s1l Macintosh System Folder Extensions libvopie dll System Folder Extensions libnoauth dll Check the methods_allow txt files on the systems that are having problems to ensure that authentication is enabled The files are in the following locations Windows install_path NetBackup var auth Macintosh System Folder Preferences NetBackup var auth If one system reports authentication failed status code 160 and the other system reports network connection timed out status code 41 you may have enabled authentication in the first system s methods_allow txt file but not in the second system s methods_allow txt file 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 host A and host B are having the problem remove host A from the file on
66. Code 154 Message global device database truncate operation failed Explanation When the user was trying to change the device configuration the system call ftruncate 3C failed during an attempt to rewrite the global device database Recommended Action Chapter 5 Media Manager Status Codes and Messages 275 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine command output if available and debug logs for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Investigate the integrity of the file system and global device database usr openv volmgr database globDB UNIX or nstall_ path Volmgr database globDB Windows Media Manager Status Code 155 Message global device database append operation failed Explanation A request was made to change the device configuration and a global device database record could not be written to the global device database file 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders
67. Database NetBackup Media ID Ko a Itid Notes For detail on this component see Media Manager Functional Description later in this chapter Tape or Optical UNIX Client NetBackup command User Interface line bprestore NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 bplist functions are merged into NBWIN merged into BPCDW32 The user interface program on Windows 95 98 is called NBWIN The bprestore and The NetBackup client daemon is called BPCDW32 The NetBackup tar functions are The server processes are the same as described for UNIX Server For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter Request Windows 95 98 Client NetBackup User Interface ao D bptm or bpdm BackuP BPCDW32 Client Disk Appendix A Functional Overview NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Descript
68. Examine the NetBackup Problems report 2 Create a debug log directory for bprd and retry the operation Check the resulting debug log to determine the connection and client names Depending on the request type restore backup and so on you may need or want to Change the client s configured name Modify the routing tables on the client On the master server set up an altnames directory and file for this client see the NetBackup System Administrator s Guide for Windows 3 Review Verifying Host Names and Services Entries on page 25 NetBackup Status Code 132 Message user is not validated to use the server Explanation None Recommended Action None NetBackup Status Code 133 Message invalid request 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 Ifa 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 registry on a Windows NetBackup server These options deny list and restore requests from all NetBackup clients Chapter 4 NetBackup Status Codes and Messages 113 Ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action 1 If you suspect that the software versions are the p
69. FreeBELibrary Successfully unloaded beutil dll Backup Exec File Restore Problems The NetBackup user interfaces restore Backup Exec files using the NetBackup internal C_BPRESTORE 4 _5 restore protocol To determine if the restore request has reached bprd check whether or not the following line appears in the bprd debug log 16 10 56 824 2540 3248 lt 2 gt process request command C_BPRESTORE 4 5 80 received The NetBackup user interfaces and commands must explicitly indicate that a list of Backup Exec files or both Backup Exec and NetBackup files need to be restored To determine if the correct restore options have been specified check that the following text appears in the bprd debug log If only Backup Exec files need to be restored 16 10 59 618 2540 3248 lt 2 gt restorefiles clnt_flops 524288 4 484 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs If both Backup Exec and NetBackup files need to be restored 16 10 59 618 2540 3248 lt 2 gt restorefiles clnt_flops 1048576 If the user interfaces are being used to restore Backup Exec images then client_flops should be set correctly as above If bprestore was used ensure that the F command line parameter has been set correctly If the correct file list request has reached bprd bprd will launch bpcd
70. From the daemon debug log file determine the offset of the volume that has an ADAMM GUID conflict with the volume entry that is being added or changed The offset is the index of the volume in the volume database Using the vmdb_dump command dump out all volume records in the volume configuration for the targeted volume database host and look up the volume offset indicated in the debug log file Note the associated ADAMM GUID which is the field adamm_guid Note Although a GUID can be changed or added by means of the vmchange and vmadd commands the GUID field is for internal use only Do not add or change a GUID Media Manager Status Code 168 Message ADAMM GUID does not exist in database Explanation The volume database was queried for a specified ADAMM Advanced Device and Media Management GUID and no volumes were found matching the specified criteria The GUID is a Global Unique Identifier This error could result if both of the following occur The bephyinv exe command or beconv exe command is running on a Windows host in install_path NetBackup bin adminecmd AND The GUID field of a record in the volume database is modified by either adding changing or deleting records Recommended Action we 282 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes None This is a normal occurrence in
71. Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Robotic Test Utilities C 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 The tests lock the robotic control path and prevent the corresponding robotic software from performing actions such as loading and unloading media If a mount is requested the corresponding robotic process times out and goes to the DOWN state This usually results in a media mount timeout Also be certain to quit the utility when your testing is complete 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 Note If the robot is not configured you cannot use robtest and must execute the command that appl
72. Identify the robot control host by checking the device configuration There should be only one configured robot control host for each LMF TL8 TLD and TLH robot and all volumes in the volume configuration should have a robot host that matches the configured robot control host 4 Check the system log on the robot control host to see if the robotic process is processing requests during the time when communications with it are attempted Perform Resolving Network Communication Problems on page 21 Media Manager Status Code 45 Message failed changing terminal characteristics Explanation A system call failed when an attempt was made to change the mode for terminal input between cooked and raw Recommended Action Examine the user interface output for the system error associated with the failed system call and troubleshoot according to operating system vendor recommendations Media Manager Status Code 46 Message unexpected data from robotic software daemon Explanation Message communications handshaking between a process and a robotic software daemon process failed Recommended Action 1 Verify that the correct version of software is running on all servers 2 Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available
73. Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Examine the permissions and available file system space for writing to the database usr openv volmgr database globDB UNIX or install_path Volmgr database globDB Windows Media Manager Status Code 156 Message global device database lock operation failed Explanation vmd the Media Manager volume daemon UNIX encountered a system call error while attempting to lock the global device database Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 Ensure that no other process has a lock on the global device database file usr openv volmgr database globDB Media Manager Status Code 157 Message global device database open operation failed Explanation A requested operation encoun
74. NetBackup 4 5 Troubleshooting Guide for Windows Device Management Status Code 17 Message Drive does not support pending request density Explanation A drive was selected that has a drive type which is not compatible with the requested density Recommended Action 1 Allow the drive selection to be determined automatically 2 When selecting the drive manually check the device configuration and the valid density table available in the tpreq man page or command description then specify a drive that is compatible with the requested density Device Management Status Code 18 Message Invalid volume count Explanation A tape mount has been requested with an unsupported option Recommended Action Check the installed software components and verify that they are all at a compatible release version Device Management Status Code 19 Message Only the administrative user can perform the requested operation Explanation Either an attempt was made to stop 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows or the tpclean command was called but the user was not root UNIX or the administrator Windows Recommended Action If desired give the user or process administrator privileges on Windows or root privileges on UNIX and retry the operation Device Management Status Code 20 Message Cannot stop device daemon with tapes assigned Explanation An attempt was made to stop 1t id
75. NetBackup Java application server runs only on NetBackup master servers 2 On the UNIX machine where you execute the jnbSA or j bpSA commands add the following line to the Launch properties or JBPSimple properties file respectively in the usr openv java directory debugLevel 2 The log file name is displayed in the xterm window where you executed the jnbSA or jbpSA commands 3 Ifyou are using the NetBackup Windows Display Console add the following line to the host_name properties file in the NetBackup Java installed folder for example C Veritas java debugLevel 2 Chapter 3 Using the Logs and Reports 5 Ee NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting the Administration Console 4 Ifyou 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 gt jnbdebug This redirects output to a file 2 See NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Codes and Messages 4 This chapter lists all the status codes and messages provided by NetBackup Media Manager Status Codes and Messages are provided in Chapter 5 There are two parts to the chapter The first section Status Codes lists the
76. Status Code 87 failed sending request to vmd Media Manager Status Code 69 failed sending to robotic software daemon Media Manager Status Code 43 failed sending to vmd Media Manager Status Code 71 Failed to find an available slot to inject to Robotic Status Code 246 Failed writing drive or robot config file Device Configuration Status Code 12 374 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages FASTRAX unable to process clean request Robotic Status Code 227 File name already exists Device Management Status Code 40 File name does not exist Device Management Status Code 25 Fork failure occurred Robot Error Status Code 10 Frequency based cleaning is not supported for this drive Device Management Status Code 51 global device database append operation failed Media Manager Status Code 155 global device database close operation failed Media Manager Status Code 158 global device database lock operation failed Media Manager Status Code 156 global device database open operation failed Media Manager Status Code 157 global device database record not found Media Manager Status Code 152 global device database truncate operation failed Media Manager Status Code 154 Chapter 5 Media Manager Status Codes and Messages 3755 NetBackup
77. TSA See Target Service Agent TSD Tape Stacker DLT A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site wr 516 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows TSH Tape Stacker Half inch A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site This robot type is supported only by NetBackup DataCenter servers unassigned media Media that contain no valid images A piece of unassigned media has an entry in the volumes database but no entries in the images database Unassigned Media do not have a time assigned in the Media section of the GUI user interface The program used to perform user backups archives and restores user operation A backup archive or restore that is started by a person on a client system Vault Vault is a separately priced NetBackup option that provides offsite backup management Vault automatically duplicates specified backup images and automates the process of offsite media rotation a critical component of any backup or disaster recovery strategy Vault manages offsite storage and retrieval of media for original backups duplicate backups and catalog backups Additionally NetBackup Vault g
78. Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 See the recommended actions for the following Media Manager status codes 69 failed sending request to vmd 70 cannot connect to vmd 71 failed sending to vmd 72 failed receiving from vmd 2 Usetpautoconf get_gdbhost ona device host to obtain its global device database host name Use tpautoconf set_gdbhost to set the global device database host name as needed Device Configuration Status Code 50 Message Device Configuration was not upgraded Explanation An attempt was made to make an automated device configuration change but the device configuration from a previous release has not been upgraded Recommended Action Run the device configuration upgrade as part of the upgrade installation procedure If a device configuration from a previous release has been restored runtpautoconf upgrade If the Media Manager database directory folder or its contents has been recently lost and the directory folder has been partially recreated with device databases from the current release run tpautoconf ready devices and retry the automated device configuration change request Device Configuration Status Code 51 Message No device is registered at these SCSI coordinates Explanation On a request to add or change robot or drive information in the device configuration the specified SCSI coordinates did not correspond to a
79. Trying to Do When the Problem Occurred 2 Record All Information 00 cee cee eee tne een EK 2 Troubleshooting the Problem 0 6 6 ccc een eens 4 Problem Report Information 666 c ccc een Ria 5 General Information 0 cece cece cece teen tebe ene e eens 5 Chapter 2 Troubleshooting Procedures 0000 e cece eee e eens 7 Preliminary Troubleshooting 6 0 eee B 7 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Configuration Problems 004 10 To Resolve Installation Problems 666 cece ene nee 10 To Resolve Common Configuration Problems 66 660 c eee eens 11 To Resolve Device Configuration Problems 0 0 00 eee 12 General Test and Troubleshooting Procedures 0 6 66 c cece eee eens 16 To Test Master Server and Clients 0 06 60 c cece 16 Testing Media Server and Clients 0 06 19 Resolving Network Communication Problems 00 000 e eee eens 21 Verifying Host Names and Services Entries 06666 e cece eee ees 25 Usima oj of bol ele ato Nera mri ar mei as meme a ra ROR ro ei eer 28 Host Name and Service Entry Examples 06 ccc cece eee eens 30 Example 1 Master Server and Client 0 eee cece e eens 30 Example 2 Master and Media Servers 606 6 c c
80. Use the tpformat f option if the media has not already been sector formatted Format Optical Status Code 4 Message tpformat Cannot read Explanation The format optical disk command tpformat encountered a system device or media error while trying to read the optical disk Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify the integrity of the device and media and check the system device files for correctness according to the NetBackup Device Configuration Guide Use the tpformat f option if the media has not already been sector formatted Format Optical Status Code 5 Message tpformat Cannot seek Explanation The format optical disk command tpformat encountered a system device or media error while trying to seek on or determine characteristics of the optical disk Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more d
81. Viewer Application log for error messages that indicate why the tape mount did not complete NetBackup Status Code 66 Message client backup failed to receive the CONTINUE BACKUP message Explanation The client bpbkar process did not receive the message from the server that indicates that the server is ready to continue Recommended Action Verify that the server did not crash If that is not the problem and you need more information 1 On Windows clients enable bpbkar debug logging a Create a bpbkar debug log directory b Ona Windows client set Verbose on the TroubleShooting tab in the NetBackup Configuration dialog box To display this dialog box start the Backup Archive and Restore interface on the client and click Configure on the Actions menu 2 On other PC clients except Macintosh create a debug 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 Chapter 4 NetBackup Status Codes and Messages 93 EN NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 3 On the master server create bpsched and bpbrm debug log directories If there are media servers involved create a bpbrm debug log directory on them 4 Retry the operation and check the resulting debug logs NetBackup Status Code 67 Message client backup failed
82. Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify that all Media Manager binaries and user interfaces are at a compatible version level Robotic Status Code 230 Message System error occurred during robot operation Explanation A robotic operation encountered a system error This status code is used for generic system call failures within robotic daemons processes Recommended Action 1 Check for other error messages in the command or interface output to indicate which system call failed Enable debug logging retry the operation and check the debug log files for more specific error messages 2 Check the system application log for error and warning messages 3 Verify that the system is not running out of virtual memory If virtual memory is the problem shut down unused applications or increase the amount of virtual memory To increase virtual memory on Windows display the Control Panel double click System and on the Performance tab set Virtual Memory to a higher value 4 Verify t
83. Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action Check the All Log Entries report If more details are required create bptm and bpbrm debug log directories on the server Then retry the operation and check the resulting log files This error is usually due to a configuration problem NetBackup Status Code 90 Message media manager received no data for backup image Explanation The tape manager bptm or disk manager bpdm received no data when performing a backup or archive This can occur for incremental backups where no data was backed up because no files have changed Recommended Action 1 Check the All Log Entries report 2 For detailed debug information create bpdm or bptm debug log directories on the server If the client is Windows also create a bpbkar debug log directory on the client Retry the operation and check the resulting debug logs NetBackup Status Code 91 Message fatal NB media database error Explanation The tape manager bptm received an error while reading or updating its media catalog 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 Ifthe above actions do not
84. a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs wr 340 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the media mount failure Robotic Status Code 206 Message Robotic dismount failure Explanation The robot could not dismount media Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the media dismount failure Robotic Status Code 207 Message Invalid command code Explanation A robotic operation was reques
85. already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that volumes are properly configured on the volume database host that matches the volume database host configured for the robot or set of standalone drives Use tpconfig dandtpconfig lsavdbhost to list the configured volume database hosts Select the current server the one you are administering to be the same as the host which is the correct volume database host for a targeted device Update the volume or device configurations target the correct volume database host modify volume properties or adjust search criteria as needed so that the volume residence query can find a matching volume Media Manager Status Code 81 Message robot type and volume group mismatch Explanation A request was made to add volumes or change volume residences in the volume configuration and the robot type and volume group associated with the volume configuration changes are in conflict with the requirements for volume groups All volumes in a volume group are required to have the same residence which includes having the same robot type A requested operation may have tried to associate the special No Volume Group name with a robotic res
86. are all at a compatible release version Device Management Status Code 7 Message Error in Sending User Message Explanation An attempt was made to send a user message to 1t id the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows on an already existing internal message queue used for inter process communication But an error was encountered in the message communications The error probably indicates a lack of system resources for message queues Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather output from the ipcs a command to see what resources are currently in use Device Management Status Code 8 Message Error in Receiving User Message Explanation An attempt was made to receive a user message from 1t id the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows on an already existing internal message queue used for inter process communication But an error was encountered in the message communications The error probably indicates a lack of system resources for m
87. by root and that the disk is not full Rerun the vault job after correcting the problem NetBackup Status Code 289 Message an error occurred when calling vltcore Explanation The error can occur during a normal vault job or when vlteject is executed for a specific session or when v1t opmenu is used to generate individual reports if any of the following conditions exists vitcore binary is removed Chapter 4 NetBackup Status Codes and Messages 157 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes vitopmenu binary is not executable the disk on which NetBackup is installed is full the following directory is removed or made inaccessible to root where xxx is the session id UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path netbackup vault sessions vault_name sidxxx Recommended Action To identify which of the above conditions led to the failure review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install _path NetBackup logs vault Also review the detail log file in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx Correct the problem and rerun the vault job If the problem persists please contact customer support and send the appropria
88. characters NetBackup Status Code 70 an error occurred when calling vltcore NetBackup Status Code 289 an extension package is needed but was not installed NetBackup Status Code 9 an invalid entry was encountered NetBackup Status Code 223 another NB database backup is already in progress NetBackup Status Code 125 archive file removal failed NetBackup Status Code 4 a session is already running for this vault NetBackup Status Code 275 attempt to open a log file failed NetBackup Status Code 288 authentication failed NetBackup Status Code 160 wer 174 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Auspex SP Backup failure NetBackup Status Code 88 Backup Exec operation failed NetBackup Status Code 151 backup restore manager failed to read the file list NetBackup Status Code 53 backups are not allowed to span media NetBackup Status Code 166 bpjava msve the client is not compatible with this server version Server_version NetBackup Status Code 513 bpstart_notify failed NetBackup Status Code 73 can t connect to client NetBackup Status Code 58 cannot connect on socket NetBackup Status Code 25 cannot connect to server backup restore manager NetBackup Status Code 205 Can not connect to the NB Java authentication service on
89. connection to a robotic software daemon process could not be established This can occur when a process tries to connect to the robotic process that is not running It can also occur if the network or server is heavily loaded and has slow response time Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Identify the robotic process by looking at the robot type and at the robot host on the robotic request or the robot host field of the volume being operated on 3 Verify that the robotic process used for robotic control is available see table Media Manager Daemons and Programs on page 459 and start the robotic process if necessary 4 Ensure that there is only one configured robot control host for each LMF TL8 TLD and TLH robot and that all volumes in the volume configuration have a robot host that matches the configured robot control host 5 Change the volumes or reconfigure the robot in the device configuration as needed 6 Check the system log on the robot control host to see if the
90. correspond to an existing file or a file name that is not in use for another mount request that may be in progress Device Management Status Code 41 Message Unknown drive name Explanation A request was made for a specified drive but no such drive could be found in the active configuration This status may occur if the device files are corrupt or missing if they cannot be opened or read or if there are no devices configured Recommended Action 1 Ensure that 1tid the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows was stopped and restarted after changes were last made to the device configuration Display the device configuration using tpconfig d or other means to see the list of valid drives Specify the drive name or index as appropriate for the interface being used 2 Check integrity of the drive database file 1t idevs located in the directory usr openv volmgr database UNIX or in the folder install_path Volmgr database Windows Display the device configuration to determine whether or not the database is corrupt and restore a saved copy of the database file from catalog backups or delete it and recreate the device configuration as needed NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Management Status Code 42 Message Incorrect tpreq access m
91. daemon is started with the v option available only on UNIX or adding VERBOSE to the vm conf file odld The Optical Disk Library daemon interfaces with the Optical Disk Library communicating with the robotics through a SCSI interface This library is not supported on Windows Started By Starting 1t id or independently by using the usr openv volmgr bin od1d command Stopped By Stopping 1tid or independently by finding the PID process id and then using the kil1 command Debug Log All errors are logged in the system log Debug information is included if the daemon is started with the v option either by itself or through 1tid or adding VERBOSE to the vm conf file wa 460 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs continued Program Description Daemon rsmd The Removable Storage Manager daemon is the interface between lt id 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 drives configured in RSM robots configured in the Media Manager interface Started By Starting 1t id on Windows 2000 only Stopped By Stopping 1tid on Windows 2000 only Debug Log All errors are logged in the system log Debug information is in
92. daemon on UNIX cancel a job Terminating a job and removing it from the job queue carousel See robotic library catalogs Internal NetBackup and Media Manager databases These catalogs contain information about configuration media devices status errors and the files and directories in the stored backup images CDF Context dependent file which is a type of directory structure on a Hewlett Packard system changer See robotic library class See policy client The system with the files to back up archive or restore client user interface See user interface cluster See master and media server cluster command lines Commands that users can execute either from the system prompt or in scripts compression The process of compacting data to enable more efficient transmission and storage wr 496 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows configuration The parameters that govern the behavior of an application This term can also refer to the manner in which a network or system is laid out or connected for example a network configuration consolidated eject A process of ejecting media for more than one Vault session at a time A Consolidated Eject can be performed for one or more logical vaults at one time consolidated report A process of generating reports for more th
93. description field of the NetBackup Media Manager volume database record If the ADAMM GUID corresponding to the media id in the NetBackup Media Manager volume database is the same as the GUID obtained from the adamm log C4B3BBAE 8B29 4823 A CE5 EBD546E1574B in the above example then the wrong media may be present in the robot and slot indicated by the NetBackup Media Manager volume database Verify whether the correct Backup Exec media identified by ADAMM GUID and cartridge label is actually present in the robot and slot as indicated by the NetBackup Media Manager volume database record corresponding to media id A00000 in the above example A physical inventory of the robot can be performed to update the NetBackup Media Manager volume database Refer to the section Updating the Media Manager Volume Database with Respect to Backup Exec Media in the NetBackup DataCenter System Administrator s Guide If the ADAMM GUID corresponding to the media id in the NetBackup Media Manager volume database is not the same as the GUID obtained from the adamm log then different ADAMM GUIDs are associated with the same media id in the NetBackup Media Manager volume databases of the locally configured drives Run beconv with the check_consistency option to detect inconsistencies in the NetBackup Media Manager volume database Refer to the section Using beconv with the check_consistency Option in the NetBackup DataCenter System Administ
94. detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 3 Ifthe targeted volume is incorrectly configured as a cleaning tape delete the cleaning volume and update the volume configuration using options to define a new volume with the appropriate media type Media Manager Status Code 118 Message cannot delete one of the default volume pools 260 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation An attempt was made to delete one of the special pre defined volume pools The None NetBackup and DataStore volume pools are fixed volume pools in the volume pool configuration and cannot be deleted Recommended Action Do not attempt to delete the None NetBackup and DataStore volume pools Media Manager Status Code 119 Message invalid rule database entry Explanation The barcode rule database is corrupt it contains records that are not compatible with the installed product binaries Recommended Action 1 Examine command output and debug logs for a more detailed message on the error a Enable debug logging by creating t
95. device in the system registry This status code applies to Windows systems only Recommended Action To avoid manually specifying SCSI coordinates port bus target and LUN use the Device Configuration wizard so that device configuration requests are fully automated on supported device discovery platforms or use the Media and Device Management interface to browse for devices in the system registry Check the operating system registry to ensure that devices are present at the specified coordinates when SCSI coordinates are manually configured Device Configuration Status Code 52 Message The device name is not valid no device responded NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation On a request to add or change robot or drive information in the device configuration there was no device found in the system registry with the specified device name This error code applies to Windows systems only Recommended Action To avoid manually specifying the device name use the Device Configuration wizard so that device configuration requests are fully automated on supported device discovery platforms or use the Media and Device Management interface to browse for devices in the system registry Check the operating system registry to ensure that devices are present at the specified coordinates when device
96. drive attached must have a robotic daemon These daemons provide the interface between 1t id and the robot or if different drives within a robot can attach to different hosts the robotic daemon communicates with a robotic control daemon see below Robotic control daemons centralize the control of robots when drives within a robot can connect to different hosts A robotic control daemon receives mount and unmount requests from the robotic daemon on the host to which the drive is attached and then communicates these requests to the robot You must know the hosts involved in order to start all the daemons for a robot Appendix A Functional Overview 451 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Figure 13 Starting Media Manager Execute usr openv volmgr bin Itid al Automated Cartridge System Library Management Facility Optical Disk Library Removable Storage Man ager Windows 2000 only aD GE gt Tape Library 4mm Tape Library 8mm P DLT Tape Library Tape Library Half inch Tape Library Multimedia Tape Stacker 8mm Tape Stacker DLT Tape Stacker Half inch NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for W
97. entry a default value is used which is also explained in the next topic eventiog File Entries The event log entry has two parameters The first parameter controls which messages NetBackup writes to the Application Log based on severity level The second parameter controls which type of messages NetBackup writes to the Application Log Both parameters are specified as decimal numbers and equate to a bitmap that expresses the values below Severity 1 Unknown 2 Debug 4 Info 8 Warning 16 Error 32 Critical Type 1 Unknown 2 General 4 Backup 8 Archive 16 Retrieve 32 Security r 50 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting the Administration Console 64 Backup Status 128 Media Device Ifthe file is empty the default severity is Error 16 and the default type is Backup Status 64 Ifthe 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 In this instance the entry is 56 255 Where 56 severity the sum of warning error and critical 8 16 32 255 type the sum of all types 1 2 4 8 16 32 64 128 The following is an
98. etc hosts 8 Verify client to server connectability by using ping or its equivalent from the client step 3 verified the server to client connection 9 Ifthe client s TCP IP transport allows telnet and ftp from the server try these as additional connectivity checks 10 For a Macintosh or NetWare client ensure that the server is not trying to connect when a backup or restore is already in progress on the client Attempting more than one job at a time on these clients results in a can t connect or similar error 11 Use the bpclntcmd utility to verify basic client to master server communications When run on a NetBackup client the pn and sv options initiate inquiries to the NetBackup master server as configured in the server list on the client The master server then returns information to the requesting client For more information see Using bpclntcmd on page 28 12 Verify that the client operating system is one of those supported by the client software Verifying Host Names and Services Entries This procedure is useful if you encounter problems with host names or network connections and want to verify that the NetBackup configuration is correct Several examples follow the procedure Note For more information on host names refer to the Networks and Hostnames appendix in this manual and to the Rules for Using Host Names in NetBackup appendix in the NetBackup System Administrator s Guide 1
99. example of a message written in the Windows Event Viewer Application Log 16 4 10797 cacao bush bpsched backup of client bush exited with status 71 The meaning of each field is as follows left to right severity 16 Error type 4 Backup jobid 10797 server cacao client bush process bpsched text backup of client bush exited with status 71 Troubleshooting the Administration Console Most errors that occur in the NetBackup Java Administration Console appear in an attention dialog Those that appear elsewhere are Java exception errors which are not documented in this guide they may appear in the status line bottom of the NetBackup Administration window or in the log file that contains stdout or stderr messages written by Java APIs or by the NetBackup Administration Console Chapter 3 Using the Logs and Reports 51 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting the Administration Console The following are the four kinds of error messages seen in the NetBackup Administration Console NetBackup status codes and messages as documented in Chapter 4 Operations performed in the Administration Console 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 You can find the status code by looking up
100. example on a Windows NT 2000 client if the system files are in the C Winnt40 directory NetBackup restores the registry when it restores that directory and all its subordinate subdirectories and files 10 Check for ERR or WRN messages in the log files that are in the directories you created in step 6 Fora Windows NT 2000 client these are the tar and inetd log files Fora Windows 98 or 95 client this is the bpcd log file If the logs indicate problems with the restore of Windows system files resolve those problems before proceeding 11 Reboot the NetBackup client system When the boot process is complete the system is restored to the state it was in at the time of the last backup wr 408 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs 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 It is equally important to back up system and application files so you can quickly and accurately restore a system to normal operation if a disaster occurs Include all Windows system files in your backups For example if Windows NT 2000 is installed in the C Winnt40 directory include this directory in the l
101. exist NetBackup Status Code 148 Message daemon fork failed Explanation A NetBackup service could not create a child process due to an error received from the system This is probably an intermittent error based on the availability of resources on the system Recommended Action 1 Restart the service at a later time and investigate system problems that limit the number of processes 2 Check the Event Viewer Application and System logs NetBackup Status Code 149 Message master server request failed Explanation None Recommended Action None NetBackup Status Code 150 Message termination requested by administrator Explanation The process is terminating or has terminated as a direct result of a request from an authorized user or process Recommended Action None NetBackup Status Code 151 Message Backup Exec operation failed Explanation The Global Data Manager console has reported that a Backup Exec job backup archive or restore did not complete normally Recommended Action Consult the Backup Exec job history on the Backup Exec server for details Chapter 4 NetBackup Status Codes and Messages 117 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 152 Message required value not set Explanation An incomplete request was made to the bpdbm process NetBackup Database Manager service This usually oc
102. failure by examining the All Log Entries report for the appropriate time frame If there is more than one NetBackup server that is one or more media servers determine if the Chapter 4 NetBackup Status Codes and Messages 135 Sa NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 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 On a Windows server the master is designated on the Servers tab in the Master Server Properties dialog To access this dialog see Using the Host Properties Window on page 40 3 See Testing Media Server and Clients on page 19 and Resolving Network Communication Problems on page 21 4 If necessary create debug log directories for the following processes and retry the operation Then check the resulting debug logs on the master server Ifthe error occurred during a backup check the bpsched debug logs Ifthe error occurred during a restore check the bprd debug logs NetBackup Status Code 204 Message conn
103. for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows The third party copy device returned an error If you see either of the following messages in usr openv netbackup logs bptm log cannot process extended copy error due to truncated sense data may be HBA problem disk error occurred on extended copy command key 0x0 asc 0x0 ascq 0x0 where key asc and ascq are all zero your host bus adapter HBA and its driver may need to be updated or may not be supported by NetBackup ServerFree Agent The host bus adapters and drivers supported in the release are listed in Chapter 2 of the NetBackup Release Notes For additional troubleshooting details refer to the Troubleshooting chapter of the NetBackup ServerFree Agent System Administrator s Guide NetBackup Status Code 171 Message media id must be 6 or less characters Explanation An operation such as using bpmedia to suspend or freeze a media ID was attempted and the media ID specified was longer than six alpha numeric characters Recommended Action Retry the command with a valid media ID NetBackup Status Code 172 Message cannot read media header may not be NetBackup media or is corrupted 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 configuratio
104. had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id Once the problem is resolved rerun the vault session vltej ect command or vitopmenu command NetBackup Status Code 302 Message error encountered attempting backup of catalog Two Phase BU Explanation This error occurs when the NetBackup command used for stage one of the two stage catalog backup fails Recommended Action For the actual error that caused the failure review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install_path NetBackup logs vault Review the detail 1og in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id In addition review the admin debug log in the following directory UNIX usr openv netbackup logs admin Windows install_path NetBackup logs admin Correct the error and rerun the vault session Chapter 4 NetBackup Status Codes and Messages 163 Or NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 303 Message error encountered executing Volume Manager command Explanation This error occurs when a volume manager command fails du
105. host B and vice versa Retry the operation Ifthe problem still exists it indicates connection problems not related to authentication If connections are now successful proceed to the next step Execute bpauthsync vopie on the master server to resynchronize the key files on the systems install_path NetBackup bin admincmd bpauthsyne vopie servers clients Add back the names removed in step 3 and retry the operation Create debug log directories for the processes involved in authentication between NetBackup systems These include On the server create debug log directories for bprd bpdbm bpcd On the client create debug log directories for bpbbackup bprestore bpbkar Windows only NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Retry the operation and check the logs NetBackup 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 NetBackup Status Code 162 Message Incorrect server platform for license Explanation The platform identifier in the license key does not match the platform type on which the key was installed Recommended Action Ensure that you are using a license key that was
106. information on NetBackupListen NetBackupBPCD and NetBackupListen each create one debug log file per day The file names for these log files are of the form log mmddyy For example log 110899 To increase the amount of information that these processes write in the logs change the value of the loglevel parameter in the mac conf file in the NetBackup folder Increasing the log level can cause these logs to grow very large so take this action only if unexplained problems exist NetBackup retains Macintosh debug logs for the number of days you specify with the logexpire parameter in the mac conf file in the NetBackup folder The default is seven days For more on changing the loglevel or the logexpire value see the NetBackup User s Guide for Macintosh wr 48 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Logs Media Manager Logs On Windows Media Manager records robotic and drive errors in the Event Viewer Application log Log entries are also made when drives change between the UP and DOWN states If a problem requires more information increase the level of logging to the Event Viewer Application log by adding a VERBOSE entry to the following file install_path Volmgr vm conf In addition you can enable debug logging for the NetBackup Volume Manager service by creating the following directories
107. is in library but not in drive domain Robotic Status Code 233 Volume is in use Robotic Status Code 237 volume is not in specified pool Media Manager Status Code 94 Volume not found in library Robotic Status Code 232 You do not have permission to create the file Device Management Status Code 44 Chapter 5 Media Manager Status Codes and Messages 397 O NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages You must be administrator to execute Robot Error Status Code 14 You must be ROOT to start daemon Robot Error Status Code 1 D 398 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Disaster Recovery 6 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 Windows Recovering the NetBackup Catalogs Master Server Disk Recovery The procedures in this section explain how to recover your data if one or more disk partitions are lost on a NetBackup master server Two general cases are considered Windows is intact The system still boots Windows but all or some of the other partitions are lost NetBackup is also assumed to be lost All disk parti
108. is one where you must manually find and insert tapes before using them A standalone volume is one that is located in a standalone drive or is stored outside of a drive and designated as standalone in the volume configuration status code A numerical code usually accompanied by a troubleshooting message that indicates the outcome of an operation storage migrator Refers to the VERITAS Storage Migrator line of hierarchical storage management products for UNIX and Windows 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 It can be a set of drives in a robot or consist of one or more single tape drives that connect to the same host SUSPENDED media state If a volume is SUSPENDED NetBackup can restore from it but cannot use it for backups NetBackup retains a record of the media ID until the last backup image on the volume expires symbolic link On a UNIX system this is a pointer to the name of the file that has the source data TapeAlert Allows reactive cleaning for most drive types and is a function of the tape drive tape format The format that an application uses to write data on a tape tape marks A mark that is recorded between backup ima
109. library or use a media management interface to correct the volume configuration Robotic Status Code 209 Message Unable to open drive Explanation The drive could not be opened The drive configuration may be incorrect and the drive may be logically DOWN Also the drive may never have become ready after media was placed in the drive Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Check for improperly configured cleaning media or interference with the drive cleaning operation Check for bad media which may have led to the drive not becoming ready after media was placed within it 3 To avoid configuring incorrect device paths and device names which is a common root cause of drive open problems use the Device Configuration wizard on supported device discovery platforms so that device paths and device names can be automatically configured Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the open failure NetBackup Troubleshooting Guide Windows NT 2000 NetBacku
110. logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 When using robot inventory update to make changes to the volume configuration ensure that all volumes of the same physical cartridge type for example 3590 in TLH robots are mapped to a single media type such as HCART This ensures that all media in the robotic library can be mounted on drives with a compatible drive type 3 When assigning volumes manually specify the media type associated with the volume Check the device configuration to determine if the volume database host for the device is consistent with the volume configuration in the volume database Applications may attempt to query multiple volume databases for volume related requests so ensure that duplicate media IDs are not used in volume configurations across multiple hosts If duplicate IDs are found either completely separate the configurations by not sharing any devices or remove volumes with duplicate media IDs and consolidate volumes into one volume configuration Always use barcodes that are unique with respect to the six 6 least significant characters across all media in all robots or use media ID generation rules to ensure unique media IDs are generated when using robot inventory update
111. logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 3 Verify that all Media Manager binaries are at a compatible version level Device Configuration Status Code 19 Message Invalid device path name Explanation On a request to change the device configuration the specified device path or device name was not valid NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action 1 To avoid configuring invalid device paths and device names use the Device Configuration wizard on supported device discovery platforms so that device paths and device names are automatically configured 2 On Windows hosts check the operating system configuration or registry for device names and refer to the tpconfig command in NetBackup online help On UNIX hosts refer to the appropriate chapter in the NetBackup Device Configuration Guide Always use no rewind device files for drives attached to UNIX hosts and check to ensure that the specified device paths exist as character special files Check for detailed errors from the command or us
112. media being frozen with a message too many data blocks written check tape drive block size configuration NetBackup Status Code 85 Message media read error Explanation The system device driver returned an I O error while NetBackup was reading from tape 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 Event Viewer Application and System logs 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 Defective media In this case you may not be able to recover all the data on the media Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups The wrong media type Verify that the media matches the drive type you are using NetBackup Status Code 86 Message media position error Explanation The system s device driver returned an I O error while NetBackup was positioning media tape Recommended Action Chapter 4 NetBackup Status Codes and Messages 101 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 For additional information check the following NetBackup Problems report to determine
113. message on the system error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Execute vmps to ensure that vmd and vmdb_dump are not both running at the same time 3 Ensure that no other process has a lock on the database file usr openv volmgr database volDB Media Manager Status Code 30 Message database seek operation failed Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows encountered a read error while seeking positioning within the volume database Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 The volume database may be corrupted Restore an older volume database from a saved version or from catalog backups Media Manager Status Code 31 Message database unlock operation failed Explanation vmd the Med
114. must create the directory for a debug log before the process starts To increase the amount of information that processes write in the logs set the Verbose level to 1 or more on the TroubleShooting tab of the NetBackup Client Properties dialog To open this dialog box start the Backup Archive and Restore interface and click NetBackup Client Properties on the File menu Debug Logs on PC Clients Debug Logs on Windows and Netware Clients To enable detailed debug logging on Microsoft Windows or NetWare target clients create the appropriate directories in the following locations Note These are the default locations in which to place these directories You can specify another location during client installation see the user guide for the respective client Windows clients C Program Files VERITAS NetBackup Logs NetWare clients SYS OPENV NETBACK LOGS The following table lists the debug log directories that apply to the above clients Table 4 PC Client Debug Logs Debug Log NetBackup Associated Process Directory Client bp NetWare target Client user interface program for NetWare bpinetd Windows NT 2000 Client service logs These logs have information on the bpinetd32 process bparchive Windows NT 2000 98 Archive program that is run from the 95 command line NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Wind
115. network path to the server is determined by the client s network code that maps the server name to an IP address Upon receipt of the connection the server determines the client s configured name from the peername of its connection to the server The peername is derived from the IP address of the connection This means that the address must translate into a host name using the gethostbyaddr network routine This name is visible in the bprd debug log when a connection is made as in the line Connection from host peername ipaddress The client s configured name is then derived from the peername by querying the bpdbm process NetBackup Database Manager service The bpdbm process compares the peername to a list of client names generated from 1 All clients for which a backup has been attempted and 2 All clients in all policies 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 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 If the compar
116. not enabled enable them before retrying the failed operation see the Using the Logs and Reports chapter d If you performed corrective actions retry the operation If you did not perform corrective actions or the problem persists go to step 3 below 3 If you encountered the problem During a new installation During an upgrade installation After making changes to an existing configuration Then go to Troubleshooting Installation and Configuration Problems on page 10 4 Ensure that the server and client are operational ww 8 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Preliminary Troubleshooting Verify there is enough space available in the disk partitions that NetBackup uses If one or more of these partitions is full NetBackup processes that access the full partition will fail The resulting error message depends on the process but you could see messages such as unable to access or unable to create or open a file Check the following disk partitions The partition where NetBackup software is installed by default C Program Files VERITAS On the NetBackup master or media server the partition where the NetBackup or Media Manager databases reside by default C Program Files VERITAS The partition where the NetBackup processes write temporary files The partition
117. not recognized by the NetBackup Java application server on the host where the login is requested For login to a Windows host the NetBackup Java authentication service on the host where the login is requested does not have sufficient privileges for granting the login request Recommended Action For UNIX hosts the user name must be a valid user name in the passwd file on the host specified in the login dialog For Windows hosts refer to the LogonUser function in the section titled Client Server Access Control Functions of the Windows NT Platform Software Developer s Kit to determine the required privileges NetBackup Status Code 504 Message Incorrect password Explanation For login to a UNIX host the user name is recognized on the host where the login is requested but the password supplied is incorrect For login to a Windows host the attempt to log in the user has failed The failure could be due to an unrecognized user in the specified domain Recommended Action Chapter 4 NetBackup Status Codes and Messages 167 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Enter the correct password On Windows hosts The exact error can be found in the bpjava msvc log file For more details refer to the LogonUser function in the section Client Server Access Control Functions of the Windows NT Platform Software Developer s Kit NetBackup S
118. of connection problems with PC workstations On Microsoft Windows or NetWare clients check the NetBackup Client service a Ensure that the service is active either by checking the logs see step b or as follows On Windows NT 2000 clients use the Services application in the Control Panel to verify that the NetBackup Client service is running and start it if necessary On Windows 98 or 95 clients check the system tray on the taskbar for the NetBackup client icon If the icon is not there run the NetBackup Client Job Tracker program from the NetBackup Program folder or the Start menu When the icon is present right click on the icon to start the NetBackup client daemon On NetWare clients enter load bpcd from the NetWare server console to start the NetBackup client daemon b Check the bpcd debug logs for problems or errors See Using the Logs and Reports chapter for instructions on enabling and using these logs c Verify that the same NetBackup client Service bpcd port number is specified on both the NetBackup client and server by default 13782 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures On Microsoft Windows check the NetBackup Client Service Port number on the Network tab in the NetBackup Client Properties dialog To display this dialog start
119. on UNIX Verify that a cleaning tape was mounted to the specified Fastrax drive Robotic Status Code 228 Message Requested slot does not exist in robot Explanation The slot associated with a request is not valid for the robot Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Issue a robot inventory Contents report to determine the valid slot range for the robot Check the volume configuration to ensure that only valid slots are referenced in volume records paying particular attention to the starting and ending slot numbers Update the volume configuration as needed or request only valid slot ranges for robotic operations Robotic Status Code 229 Message Requested operation is not supported by the robot Explanation A robotic operation was sent to a robotic component that did not support that operation or options requested for the operation were not supported There may be an incompatibility between components or versions of the product Recommended Action Chapter 5 Media Manager Status Codes and Messages 351 WS NetBackup 4 5 Troubleshooting Guide for
120. on the master server has entries for both jupiter and meteor The reason for both names is that when the server does a backup it uses the name associated with the client it is backing up For example it uses the meteor interface when backing up pluto and the jupiter interface when backing up mars The current server entry master server name is jupiter because that is the name used to back up the client on the master server The NetBackup server list for the other systems also have entries for both the jupiter and meteor interfaces This is recommended in order to keep the server entries the same on all clients and servers in the configuration It would be adequate to list only the master server name for the local network interface to the client system or media server for example meteor for pluto For the network shown the differences mentioned for the policy client list and the server list is the only unique configuration required Assuming that all the standard networking files for example the hosts file WINS DNS and routing tables are set up correctly all required network connections can be made If the master server system is a type of router that hides the name of the originating host when routing requests between networks you see the same type of restore problem discussed in example 4 For example if pluto were on FDDI token ring the master server would use meteor as the peername when it forwarded the request to NetBackup Ne
121. on the media server that contains the Backup Exec catalogs whose images are being restored This can be seen in the bprd debug log f temp be_ restore In the above text 16 11 00 570 2540 3248 lt 2 gt restorefiles Restoring from image adaj_1007712098 browse client adaj requesting client adaj user root 16 11 00 580 2540 3248 lt 2 gt open BE restore connection mediahost dell 2 16 11 00 580 2540 3248 lt 2 gt open BE restore connection browse client adaj 16 11 00 580 2540 3248 lt 2 gt open BE restore connection requesting client adaj 16 11 00 580 2540 3248 lt 2 gt open BE restore connection destination client adaj 16 11 00 580 2540 3248 lt 2 gt open BE restore connection client_type 13 16 11 00 580 2540 3248 lt 2 gt open BE restore connection mediaid BE0001 16 11 00 580 2540 3248 lt 2 gt open BE restore connection keyword 22 16 11 00 580 2540 3248 lt 2 gt open BE restore connection obj desc NULL 16 11 00 580 2540 3248 lt 2 gt open BE restore connection keep 1 16 11 00 580 2540 3248 lt 2 gt open BE restore connection progress file G nb NetBackup logs user_ops adonijah logs NBWINO007 16 11 00 580 2540 3248 lt 2 gt open BE restore connection rename_file NONE 16 11 00 580 2540 3248 lt 2 gt open BE restore connection commit 0 16 11 00 580 2540 3248 lt 2 gt open BE restore connection dirByteCount 0 16 11 00 580 2540 3248
122. option b Retry the operation and examine the logs 2 Ensure that no other process has a lock on the barcode rule database file usr openv volmgr database ruleDB NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Media Manager Status Code 124 Message rule database close operation failed Explanation An error occurred when vmd attempted to close the barcode rule database Recommended Action Examine the daemon debug log for a more detailed message on the system error 1 Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option 2 Retry the operation and examine the logs Media Manager Status Code 125 Message rule database open operation failed Explanation A requested operation encountered a situation where the barcode rule database file could not be opened Recommended Action Check for the existence and permissions of the ruleDB file in the usr openv volmgr database directory on UNIX or install_path Volmgr database folder on Windows Restore the ruleDB file from the catalog backups or from another location change the access permissions on the existing ruleDB or move rename the cur
123. option b Retry the operation and examine the logs 2 Ensure that volumes are properly configured on the volume database host that matches the volume database host configured for the robot or set of standalone drives Use tpconfig dandtpconfig lsavdbhost to list the configured volume database hosts Select the current server the one you are administering to be the same as the host which is the correct volume database host for a targeted device Update the volume or device configurations target the correct volume database host modify volume properties or adjust search criteria as needed so that the volume query can find a matching volume For media in their correct slot locations execute the Rescan update barcode request so that the barcode field in the volume configuration matches the actual barcode as interpreted by the robotic library barcode reader Media Manager Status Code 79 Message specified robot is unknown to vmd Explanation A request was made to query volumes by residence and no volumes were found in the targeted volume configuration that matched the provided robot number robot type and robot host Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot
124. or sort volume records by slot number to identify the existing volume entry with the same robotic coordinate as that specified on the volume entry being added or changed if using optical disk display the optical platter side 3 Change update or move volume or delete the existing volume entry if it does not reflect the correct robotic coordinate corresponding to the volume s storage position in the robotic library If a volume is currently in a drive the volume database should still reflect the volume s home slot Media Manager Status Code 39 Message network protocol error Explanation An attempt to read data from a socket failed Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the protocol error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Verify that the server being connected to is operational Media Manager Status Code 40 Message unexpected data received Exp
125. other host is trying to reserve the same drive Recommended Action Use unique non duplicate strings for host names and for SSO_HOST_NAME configuration file entries Media Manager Status Code 146 Message incompatible database version Explanation An invalid or unknown database or communications protocol was encountered by a requesting process or by vmd vmd is the volume daemon on UNIX or NetBackup Volume Manager service on Windows Possible data stores affected by such an error are volume volume pool barcode rule global device database and shared drive information Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Identify the target components for example vmd and daemons services or user interfaces on local or remote hosts Verify that all Media Manager binaries are at a compatible version level Depending on which requests encountered the invalid version determine whether or not the database is corrupt Use an appropriate interface to query for the type of information involved in the error condition Media Manager Status Cod
126. platforms so that device paths and device names can be automatically configured for tape drives 2 Refer to the appropriate chapter in the NetBackup Device Configuration Guide Always use no rewind tape device files recommended character device files for optical devices or recognized drive name syntax such as for NDMP for tape drives Make sure that the specified device paths exist as character special files Check for detailed errors from the command or user interface output Chapter 5 Media Manager Status Codes and Messages 327 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Device Management Status Code 39 Message Parameter is invalid Explanation The tpclean command was called with invalid arguments or an internal function encountered a missing reference to data it requires Recommended Action 1 Ifa cleaning operation was requested check the tpclean usage statement and compare with the parameters that were specified 2 Check the installed software components and verify that they are all at a compatible release version Device Management Status Code 40 Message File name already exists Explanation On a tape mount request the file name associated with the request already existed or was already associated with another mount request Recommended Action Resubmit the request using a different file name Specify a file name that does not
127. port A location used for transferring data in or out of a computer Also see media access port primary copy The copy of an image that NetBackup uses to satisfy restores When NetBackup duplicates an image the original is designated as the primary copy privileges The tasks or functions that a user system or application is authorized to perform profile A vault profile is a way to save configuration settings Specific parameters for duplication catalog backup eject and report or any combination of these steps are configured within a profile progress report Log where NetBackup records events that occur during user operations proxy restore A proxy restore allows the user to restore files that he has write access to on a machine other than his desktop The files must be in a backup of the machine to which they are being restored QIC Quarter inch cartridge tape queued job A job that has been added to the list of jobs to be performed raw partition backup Bit by bit backup of a partition of a disk drive on UNIX On Windows this is called a disk image backup rbak The program that Apollo clients use to read data from tape during a restore Glossary 509 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows recorded media ID This is an identifier written as part of the label on a volume and used by Media Manager to ensure that the correct
128. priced VERITAS software option that allows tape drives standalone or in a robotic library to be dynamically shared among multiple NetBackup and Storage Migrator servers This option is supported only on NetBackup DataCenter servers SMDR Storage management data requestor a Novell NetWare program that provides its services transparently to all SMS modules and lets remote and local modules communicate with one another SMS Novell NetWare storage management services source volume group A volume group from which Vault can select backups to duplicate This parameter is used to restrict the list of backups from all backups that reside on media in any volume group to backups that reside on media in a single volume group Where a volume group corresponds to a particular robot the profile will duplicate only backups on media in that robot The Source Volume Group is normally only specified if you have multiple robots attached to the same server for example you want to duplicate backups that reside in robot 0 to media that reside in robot 1 SSO See Shared Storage Option SSO stacker Usually a small robotic library that contains one drive only See robotic library Glossary 513 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows standalone A qualifier used with drives and media to indicate they are not associated with a robot For example a standalone tape drive
129. process is leaking memory and stop that process Restart the NetBackup Media Manager daemons Free up memory by terminating unneeded processes that consume a lot of memory Add more swap space or physical memory if necessary Robotic Status Code 241 Message An error occurred accessing the RSM api Explanation A failure occurred in a call to the Removable Storage Manager application programming interface Recommended Action Use the robot test utility or the operating system administrative interface to check the status of robotic libraries and media Resolve the problem according to troubleshooting techniques recommended by Removable Storage Manager documentation Robotic Status Code 242 Message Robot media access port does not exist Explanation the requested media access port was not valid for use with the targeted media Recommended Action Use the robot test utility or a vendor administrative interface to verify the media access port address based on the location of the media Choose a a media access port that is valid or let one be automatically selected and retry the robotic operation Robotic Status Code 243 Message Cannot open create the media access port status file Chapter 5 Media Manager Status Codes and Messages 355 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A robotic daemon process could not create or open a s
130. process that returned this status code Then retry the operation and check the resulting debug log NetBackup Status Code 13 Message file read failed Explanation A read of a file or socket failed Possible causes include I O error reading from the file system Read of an incomplete or corrupt file Socket read failing A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket A problem specific to NetBackup ServerFree Agent see recommended actions Recommended Action 1 Check the NetBackup Problems report for clues on where and why the problem occurred 2 For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log 3 For NetBackup ServerFree Agent only Status code 13 may appear in the usr openv netbackup logs bpbkar log and can indicate the following The files to back up reside on an IDE drive as opposed to SCSI and the offhost backup method was set to either NetBackup Media Server or Third Party Copy Device If you are using offhost backup the disk containing the client files must be a SCSI or Fibre Channel device If the disk is an IDE drive you may see the following in the usr openv netbackup logs online_util log get_disk_info FTL var tmp caa026fEU disk_inquiry failed Errno 25 Inappropriate ioctl for device and
131. processes running and if a backup is active 3 If there is no reason for bpsched to be running then kill it from the Activity monitor NetBackup Status Code 215 Message failed reading global config database information Chapter 4 NetBackup Status Codes and Messages 11 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation During the periodic checking of the NetBackup configuration the NetBackup scheduler process bpsched was unable to read the global configuration parameters Recommended Action 1 Verify that the NetBackup Database Manager service is running 2 Attempt to view the global configuration settings Use Host Properties see Using the Host Properties Window on page 40 3 For detailed troubleshooting information create debug log directories for bpsched and bpdbm on the master server and retry the operation Then check the resulting debug logs NetBackup Status Code 216 Message failed reading retention database information Explanation During its periodic checking of the NetBackup configuration the NetBackup scheduler process bpsched could not read the list of retention levels and values Recommended Action 1 Verify that the NetBackup Database Manager service is running 2 For detailed troubleshooting information create debug log directories for bpsched and bpdbm on the master server and retry the operation
132. 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 NetBackup Status Code 1 Message the requested operation was partially successful Explanation A problem that may require corrective action was detected during the requested operation Recommended Action Check the All Log Entries report and also the progress log if there is one Some of the problems that can show up under status code 1 are A file or directory path that is more than 1023 characters long For NetBackup ServerFree Agent the maximum pathname length is 1000 characters for frozen image backups not 1023 When the frozen image is created a new mount point is added to the beginning of the file path If this new mount point plus the original file path exceeds 1023 characters the backup fails with status code 1 The progress log includes the entry ERR Skipping long dir path Could not open a file Read error encountered in a file File is of an unknown type On clients using Open Transaction Manager OTM for open file management the OTM cache may be full See the recommended actions under status code 11 Avault job may terminate with status code 1 if non fatal errors are encountered during one o
133. receiving the JOB_START and JOB_SUCCESS status from bpcd 16 11 09 162 2540 3248 lt 2 gt close BE restore connection recieved JOB START from bpcd 16 12 17 889 2540 3248 lt 2 gt close BE restore connection recieved JOB SUCCESS from bpcd 16 12 17 889 2540 3248 lt 2 gt close BE restore connection sending disconnect request to bpcdor command line By looking at the debug logs the exact stage where a file restore problem occurred can be determined Examples Example 1 If the bprestore command did not specify the F parameter the bprd debug log indicates that client_flops has not been set 16 22 54 735 3476 2644 lt 2 gt restorefiles clnt_flops 0 Example 2 If the NetBackup Volume Manager service is not running on the media server that contains the Backup Exec catalogs corresponding to the image the bpcd and bptm debug logs indicate the problem The following is an example bpcd log on the media server that contains the Backup Exec catalogs corresponding to the image 16 25 25 918 1600 4028 lt 2 gt bpcd main BPCD RESTORE IMAGE FILES RQST 16 25 25 918 1600 4028 lt 2 gt bpcd_ restore image files browse_client adaj 16 25 25 918 1600 4028 lt 2 gt bpcd_ restore image files requesting client adaj 16 25 25 918 1600 4028 lt 2 gt bpcd restore image files destination_client adaj 16 25 25 918 1600 4028 lt 2 gt bpcd restore image files client_type 13 16 25 25 918 1600 4028 lt 2
134. represent other characters in searches Microsoft Windows noun Describes a line of operating systems developed by Microsoft Inc For more information on the Windows operating systems that NetBackup supports refer to the VERITAS support web site at http www support veritas com Windows adjective Used to describe a specific product or clarify a term Some examples are Windows 95 Windows 98 Windows NT Windows 2000 Windows servers Windows clients Windows platforms Windows hosts and Windows GUI Windows servers A term that defines the Windows server platforms that NetBackup supports those platforms are Windows NT and 2000 Windows clients A term that defines the Windows client platforms that NetBackup supports those platforms are Windows 95 98 ME NT 2000 XP for 32 and 64 bit versions and LE Windows Display Console A NetBackup Java interface program that runs on Windows 2000 NT 98 and 95 computers Users can start this interface on their local system connect to a UNIX system that has the NetBackup Java software installed and then perform any user operations that their permissions allow WORM media Write once read many media for optical disks NetBackup BusinesServer does not support WORM media xbp The X Windows based backup archive and restore program for users on NetBackup UNIX clients Glossary 519 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide
135. request was made to update a global device database record and the record specified was not found in the global device database This condition could occur when a device configuration change is made after the global device database host has changed Recommended Action If the request to update a global device database record fails because the record does not exist a request is made to add the missing record to the global device database No action is required Media Manager Status Code 153 Message device entry is not unique in global device database Explanation A request was made to add a global device database record and the record specified was a duplicate of an existing record This condition could occur if two processes are simultaneously updating the device configuration on the same host Recommended Action 1 Coordinate changes to the device configuration so that changes come from a single source 2 To investigate the details surrounding the global device database changes on the server database side examine the daemon debug log file a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the request to change the device configuration and examine the debug log file Media Manager Status
136. robotic process is processing requests during the time when connections to it are attempted Media Manager Status Code 43 Message failed sending to robotic software daemon Explanation An attempt to write data to a robotic software daemon process socket failed Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Identify the robotic process by looking at the robot type and at the robot host on the robotic request or the robot host field of the volume being operated on Verify that the robotic process used for robotic control is available and handling requests see table Media Manager Daemons and Programs on page 459 3 Identify the robot control host by checking the device configuration There should be only one configured robot control host for each LMF TL8 TLD and TLH robot and all volumes in the volume configuration should have
137. see what resources are currently in use Device Management Status Code 15 Message The drive is DOWN Explanation An attempt was made to mount media on a drive or to reserve a shared drive which has since been logically configured to the DOWN state Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Check the application log files such as the bptm log to see why the drive may have been configured DOWN 3 Check the integrity of the drive drive path and media Device Management Status Code 16 Message No mount pending for given mount index Explanation An attempt was made to retrieve information about a pending mount request but no such pending mount request was found Recommended Action Use a device monitor interface or consult application logs to see whether the request has been completed or canceled Requests to retrieve information for pending mount requests are valid only when the mount request is actually pending Chapter 5 Media Manager Status Codes and Messages 319 v NetBackup 4 5 Troubleshooting Guide for Windows Status Codes
138. servers When these directories exist NetBackup creates log files in the directory for the associated process On a Windows server you can create all of the NetBackup debug log directories at once by running the following batch file To create all of the NetBackup debug log directories at once on a master or media server run the following batch file install_path NetBackup Logs mklogdir bat Note Media servers have only the bpbrm bpcd bpdm and bptm debug logs NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Debug Logs Table 3 NetBackup Server Debug Logs Debug Log Associated Process Directory admin Administrative commands bpbrm NetBackup backup and restore manager bpcd NetBackup client manager This process is started by the NetBackup Client service bpdbjobs NetBackup jobs database manager program bpdm NetBackup disk manager bpdbm NetBackup database manager This process runs only on master servers It is the NetBackup Database Manager service bprd NetBackup request manager This process is the NetBackup Request Manager service bpsched NetBackup backup scheduler This process runs only on master servers bptm NetBackup tape management process symlogs System log user ops The user_ops directory is created during the install of NetBackup on all servers and clients The NetBackup J
139. service could not create a directory path for its configuration catalogs due to the failure of a system call This is usually due to a permission problem or an out of space condition Recommended Action Create a debug log directory for bpdbm and retry the operation Check the resulting debug log for information NetBackup Status Code 221 Message continue I4 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation This status code is used in coordinating communication between various NetBackup processes and normally does not occur If the 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 Recommended Action Determine the cause of the status code that follows this one NetBackup 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 Recommended Action Determine the cause of the status code that follows this one NetBackup Status Code 223 Message an invalid entry
140. system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 245 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 Ensure that the volume pool specified does not violate the requirements noted Use the vmpool command to display the pool information Use the vmrule command to display the barcode rule information Add or change volume pools and barcode rules as needed to rectify inconsistencies in cases where the databases are inconsistent or corrupted Media Manager Status Code 91 Message cannot change volume pool for assigned volume Explanation A request was made to change the volume pool for a volume and the volume is currently assigned For optical volumes the volume pool cannot be changed unless both sides of the optical platter are unassigned Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by
141. tape execute the following command on shark bprecover r 1 ev JBL29 d 8mm Recovering shark D VERITAS NetBackup db Example 2 If the drive attaches to another NetBackup server execute bprecover on the server where the drive attaches and specify shark with the dhost option bprecover r 1 ev JBL29 d 8mm dhost shark Recovering shark D VERITAS NetBackup db 4 Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel to a Start the following services NetBackup Request Manager service Chapter 6 Disaster Recovery 415 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs b NetBackup Database Manager service Stop and restart the following services so they can read the recovered configuration NetBackup Device Manager service NetBackup Volume Manager service Recover Catalogs From Disk If you backed up the NetBackup catalogs to a disk and that disk is intact you can recover the catalogs as follows Note If this disk has failed then you must resort to backups of this disk that have gone to another server If you have not backed up the NetBackup catalogs to another server you must use the NetBackup Import Images feature to re add the image information to the catalogs See the NetBackup System Administrator s Guide for Windows for instructions 1 Use the NetBack
142. tape or disk To Recover the Master Server Windows intact 1 Partition the disks as they were before the failure 2 Install NetBackup server software However do not configure any NetBackup policies or devices 400 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Master Server Disk Recovery 3 Install any NetBackup patches that had previously been installed 4 Update the external mapping files 5 Enable debug logging by creating the following directories install_path NetBackup logs tar install_path NetBackup logs bpinetd 6 Start the NetBackup Client service and stop all other NetBackup services Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel 7 Use the bprecover command to recover the NetBackup catalogs Choose one of the procedures under Recovering the NetBackup Catalogs on page 409 8 When catalog recovery is complete start the NetBackup services that are not already running Use the Activity Monitor or the Services application in the Windows Control Panel Caution In step 9 do not restore files to the install_path Net Backup db install_path NetBackup var or install_path Volmgr database directories These directories were recovered in step 7 and overwriting them with regular backups will leave the catalogs in an inconsistent state 9 Rest
143. the usr openv netbackup db directory on UNIX servers and in the install_path Net Backup db directory on Windows NetBackup servers Table 7 NetBackup Databases Database Contents config Configuration information This database resides on the master server and has three parts policy Contains information about each NetBackup policy config Contains information about global attributes storage units and database backups altnames Contains information about client names for restores error Error and status information about NetBackup operations This database resides on the master server and has two parts error Contains information recorded during backup operations and used in the NetBackup reports failure_history Contains daily history of backup errors images Information about the backup images and resides only on the master server One of the files in the images directory is the file database The file database is the one that NetBackup accesses when a user browses for files to restore jobs Job information that is used by the NetBackup job monitor UNIX NetBackup server and activity monitor Windows NetBackup server The Jobs database is on the master server media Media related information used by bptm Each master or media server has a media database with media information for the images stored on that server s storage units The media database also has an errors file that contains error history informa
144. the Backup Exec images then client _flops should be set correctly as above If bplist was being used then ensure that the flops parameter has been set correctly If the correct file browse request has reached bprd bprd will ask bpdbm to obtain a list of files For Backup Exec images bpdbm will launch bpcd on the media server that contains the Backup Exec catalogs whose images are being browsed This can be seen by searching the bpdbm debug log for the following text 13 58 46 819 1780 3476 lt 2 gt open file rec remote host dell 2 Appendix D Backup Exec Tape Reader for NetBackup 481 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs 13 58 46 819 1780 3476 lt 2 gt open file rec remote mediaid BE0001 13 58 46 819 1780 3476 lt 2 gt open file rec remote keyword 22 13 58 46 819 1780 3476 lt 2 gt open file rec_remote path 13 58 46 819 1780 3476 lt 2 gt open file rec remote client adaj 13 58 46 819 1780 3476 lt 2 gt open file rec remote depth 2 13 58 46 819 1780 3476 lt 2 gt open file rec remote dirs_only 0 In the above text Host dell_2 is the name of the media server that contains the Backup Exec catalogs corresponding to the image of client adaj The NetBackup image has a keyword 22 which is the Backup Exec backupset number on the Backup Exec media having a Media Mana
145. the Media Manager volume configuration add it Ifa fatal bptm error occurred verify that the NetBackup Volume Manager service is active Ifthe entire image is not present perform import phase 1 on the media IDs that have the remainder of the image NetBackup 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 NetBackup Volume Manager service is active 3 For detailed troubleshooting information create a debug log directory for bptm and retry the operation Check the resulting debug log NetBackup Status Code 178 Message media id is not in NetBackup volume pool Explanation NetBackup attempted a backup of its catalogs and the media ID specified for the catalog backup was not in the NetBackup volume pool Volumes for catalog backups must be in the NetBackup volume pool Recommended Action Check the Media Manager volume configuration to verify that the media IDs are present and in the NetBackup volume pool NetBackup Status Code 179 Message density is incorrect for the media id Explanation An operation such as list contents was attempted on an invalid media ID such as a cleaning tape Another possibility is that a media ID in the NetBackup catalog backup configuration does not match the media type ente
146. the clone as follows a When no backups are running use the following VxVM command to list any clones vxdg list The clone name will be of the form clone_disk_group_clone b To remove the clone enter the following usr openv netbackup bin bpdgclone g disk_group n volume c For example usr openv netbackup bin bpdgclone g wil_test n vol01 c where wil_test is the name of the disk group and volo is the name of the VxVM volume For more information on removing a VxVM clone refer to the NetBackup ServerFree Agent System Administrator s Guide For vxdg refer to the VERITAS Volume Manager Administrator s Guide c Before running the backup again resynchronize the primary disk with the secondary disk For assistance refer to the Extended Frozen Image Services chapter of the NetBackup ServerFree Agent System Administrator s Guide 3 For NetBackup for EMC Fastrax If a backup fails with a status code 11 and the NetBackup progress log has a message stating SYMINIT failed see example log below a usr symcli symbolic link must be created that points to the SYMAPI libraries installed on your system The following is an example progress log Backup started Thu 06 Dec 2001 03 53 52 PM CST war 6 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 15 53 52 Initiating backup 15 54 01 ERR SY
147. the device or media that caused the error Event Viewer Application and System logs 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 Defective media In this case some data may be lost Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups The wrong media type Verify that the media matches the drive type you are using NetBackup Status Code 87 Message media close error Explanation The system s device driver returned an I O error while NetBackup was closing a tape Recommended Action 1 For additional information check the following NetBackup Problems report to determine the device or media that caused the error Event Viewer Application and System logs 2 Check for the following A defective or dirty drive Clean it or have it repaired see the tpclean command for cleaning Defective media In this case some data may be lost Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups NetBackup Status Code 88 Message Auspex SP Backup failure Explanation NetBackup detected a problem when backing up an Auspex FastBackup client 102 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for
148. the file list to bprd and bprd will send the file list to the requesting user interface or command line By looking at the debug logs the exact stage where a file browse problem occurred can be determined NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs Examples 08 5 15 08 5 08 5 08 15 08 15 08 15 08 15 08 string 26 26 26 26 26 26 26 26 Example 1 The bplist command did not specify the flops parameter or the Backup Exec Backups or the Normal and Backup Exec Backups option was not selected in the user interface The bprd debug log indicates that client_flops has not been set 14 38 09 215 3316 2376 lt 2 gt fileslist client flops 0 Example 2 If the NetBackup Volume Manager service is not running on the media server that contains the Backup Exec catalogs corresponding to the image the bpcd and bptm debug logs indicate the problem The following is from the bpcd log on the media server that contains the Backup Exec catalogs corresponding to the image 614 3792 3596 lt 2 gt bpcd main BPCD GET FILE REC ROQST 614 3792 3596 lt 2 gt bpcd_get_file rec received mediaid BE0001 614 3792 3596 lt 2 gt bpcd_get_file rec received keyword 22 624 3792 3596 lt 2 gt bpcd_ get file rec received path 624 3792 3596 lt 2
149. the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Ensure that volumes are properly configured on the volume database host that matches the volume database host configured for the robot or set of standalone drives Use tpconfig dandtpconfig lsavdbhost to list the configured volume database hosts Select the current server the one you are administering to be the same as the host which is the correct volume database host for a targeted device 3 Update the volume or device configurations specify the correct volume database host modify volume properties or adjust search criteria as needed so that the volume query can find a matching volume Media Manager Status Code 36 Message barcode not unique in database Explanation A volume entry being added to or changed in the volume database had a barcode specified which was a duplicate of the barcode for another volume already in the volume database All volumes in a volume database must have a unique barcode Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOS
150. 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 Windows servers and clients verify that the NetBackup Client service is running 4 WINS or DNS host name information must correspond to what is in the policy configuration and the name entries in the following On Windows NetBackup servers Microsoft Windows clients and NetWare nontarget clients check the General tab in the NetBackup Client Properties dialog and the Servers tab in the Specify NetBackup Machines dialog To display these Chapter 2 Troubleshooting Procedures 27 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures dialogs start the Backup Archive and Restore interface on the client For the General tab click NetBackup Client Properties on the File menu for Servers tab click Specify NetBackup Machines on the File menu The bp conf file on Macintosh clients The openv netback bp ini file on NetWare clients Also verify that reverse DNS addressing is configured 5 To confirm the setup of the IP addresses and hostnames in DNS and or local hosts files on each NetBackup node use the NetBackup bpclntcmd utility Using bpcintcmd The bpclntcmd utility resolves IP addresses into host names and host names into IP addresses by using the same system calls as the Net
151. the message in the alphabetical listing at the end of Chapter 4 Then use the status code to find the full description of the message in the first half of Chapter 4 NetBackup Administration Console application server status codes and messages as documented in Chapter 4 These messages have status codes in the 500 range Messages with status codes 500 501 502 503 and 504 begin with Unable to login status Messages with status codes 511 and 512 may or may not begin with Unable to login status The message is not always accompanied by a status code see the above note Java exceptions These are generated by either the Java APIs or by NetBackup Administration APIs These messages begin with the name of the exception For example java lang ClassCastException or vrts nbu NBUCommandExecutionException Java exceptions usually appear in one of three places Inthe status line bottom of the NetBackup Administration window Inthe log file generated by the jnbSA or jbpSA commands When set up in the output file of the Windows Display Console bat file see Enabling Detailed Debug Logging below for more detail Operating system errors Messages that do not match those documented in this manual are probably operating system errors 2 o2 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshoo
152. to add a robot but the robot type is not supported on the device host Recommended Action Check www veritas com and product release documentation for supported device configurations Device Configuration Status Code 7 Message Invalid SCSI port number for the robot Explanation A request was made to add or change the SCSI port number for a robot but the SCSI port number provided was not valid Recommended Action Chapter 5 Media Manager Status Codes and Messages 287 Or NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Specify the correct SCSI port number for the robot Perform device discovery using the Device Configuration wizard or check the Windows registry as needed to obtain the SCSI port number Device Configuration Status Code 8 Message Invalid SCSI bus number for the robot Explanation A request was made to add or change the SCSI bus number for a robot but the SCSI bus number provided was not valid Recommende
153. to attach a shared memory segment that 1tid maintains 1tid is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid b Retry the operation and examine the logs ww 360 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Robot Error Status Code 5 Message Error in getting process Id Explanation A robotic daemon process was unable to obtain its own process identifier due to a system call failure Recommended Action Investigate operating system functionality regarding a process obtaining its own process identifier Robot Error Status Code 6 Message No devices are configured on the robot Explanation A robotic daemon process was started but no drives are configured for the robot Recommended Action Some robotic daemons processes will not run if there are no drives configured for them to manage Add or reconfigure one or more drives to be in the associated robot
154. 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 debug logging a On the server create a bpbrm debug log directory b On Windows clients create a bpbkar debug log directory c On other PC clients except Macintosh create a debug 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 2 Retry the operation and check the resulting debug logs NetBackup Status Code 68 Message client timed out waiting for the file list Explanation The client did not receive the list of files to back up within the allotted time This list comes from the server Recommended Action First verify that the server did not crash If that is not the problem and you need more information 1 Set up debug logging a On the server create a debug log directory for bpbrm b On Windows clients create a bpbkar debug log directory c On other PC clients except Macintosh create a debug log directory for bpcd the bpcd log is created automatically on Macintosh NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes To increase the amount of in
155. type and volume group mismatch Media Manager Status Code 101 Mount canceled device daemon is terminating Device Management Status Code 56 must be root user to execute command Media Manager Status Code 3 network protocol error Media Manager Status Code 39 382 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages No action pending for given mount index Device Management Status Code 50 no child process to wait for Media Manager Status Code 64 no cleaning tape available Media Manager Status Code 66 No cleaning tape is defined in the device s robot or 0 cleanings remaining Device Management Status Code 59 No device found in RSM at the specified location Device Configuration Status Code 45 No device is registered at these SCSI coordinates Device Configuration Status Code 51 No devices are configured on the robot Robot Error Status Code 6 no entries changed Media Manager Status Code 47 no entries deleted Media Manager Status Code 48 no entries inserted Media Manager Status Code 49 No media found in device or robot slot please verify Device Management Status Code 61 Chapter 5 Media Manager Status Codes and Messages 383 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Message
156. underscore _ 3 Verify that the correct version of software is running on all servers Media Manager Status Code 130 Message requested drive is already reserved Explanation A request was made to reserve a shared drive with vmd DA the device allocator for the Shared Storage Option and the drive was already reserved for another host This is a normal occurrence when drive resources are being oversubscribed for either of these reasons independent schedulers applications accessing the same pool of drives or hardware or media errors causing some drives allocated to jobs to become unavailable Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Check the system log and application bptm debug log to determine if hardware or media errors have caused drives to become unavailable 2 If more information is needed on the drive reservation problem examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs Media Manager Status
157. using the correct file path If the condition is occurring during operator display of a pending request error message check to see if the help files are properly installed at usr openv volmgr help robots robot type help file name UNIX or at install_path Volmgr Help Robots robot type help file name Windows Device Management Status Code 26 Message Request terminated because host not validated for volume pool Explanation The host where the mount request was initiated has been denied access to the media due to permissions defined for the volume pool in which the media ID is contained Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Query the volume pool information for the requested volume pool on the host where the mount request was issued by running vmpool listall b Obtain the name of the host from which the mount request originated by checking the system log This host name is the one returned by the system hostname 1 command 2 Change the volume pool host name security with vmpool or another user interface that supports volume pool host attributes change the volume pool associated with the volume if it is not assigned or log in to the host that is allowed to use media in the targeted volume pool Then resubmit the mount request Device Management Status Code 27 Messa
158. vault volume group back into the robotic volume group Then rerun the vault sessions that failed NetBackup Status Code 291 Message number of media has exceeded capacity of MAP must perform manual eject using vltopmenu or vlteject Explanation This error occurs when a vault job is run for a profile that has selected automatic eject mode and the number of media to be ejected exceeds the capacity of the MAP Recommended Action Use v1 topmenu to manually eject the media for the selected profile and session id The vltopmenu option will let you eject the selected media a MAP full or less at a time NetBackup Status Code 292 Message eject process failed to start Explanation This error occurs when the eject processing cannot be started by the vault job or vlteject command or via vltopmenu Recommended Action For detailed information about the problem review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install_path NetBackup logs vault Also review the detail 1log in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install _path NetBackup vault sessions vault_name sidxxx where xxx is the session id Use the robtest utility to ensure that you can communicate with the vault robotic library Once the problem is resolved rerun the vault session vl1tej ect command or vltopmenu command NetBackup Stat
159. volume group on the request or let the volume group be automatically selected Volume group selection depends on the interface being used Media Manager Status Code 102 Message invalid pool database entry Explanation The volume pool database is corrupt in that it contains records that are not compatible with the installed product binaries Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Use vmpool to investigate the integrity of the volume pool database The daemon debug log file should indicate the number of fields expected and the number of fields found in the pool record Restore a saved version of the pool database if the pool database cannot be manually corrected Media Manager Status Code 103 Message all available pool numbers are in use Explanation A request was made to add a volume pool in the volume pool configuration but no unique pool numbers could be generated because the available pool numbers were used up Recommended Action Consolidate volume pools so that a new pool number becomes available Media Manager Status Code
160. was in the process of declaring the host to be unavailable Recommended Action In case 2 above determine whether the host ought to be available Correct the underlying network problems or restart 1t id the device daemon on UNIX or NetBackup Device Manager service on Windows Media Manager Status Code 136 Message invalid host name Explanation A device host was being added to the Media Manager configuration or a request was made to vmd DA the device allocator for the Shared Storage Option SSO and the host name exceeded the allowable length Recommended Action Limit host names to 256 ASCII characters or less Media Manager Status Code 137 Message oprd request is not supported on the remote host Explanation An invalid request was sent to the operator request process Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 269 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 Identify the targeted host an
161. when it cannot locate the following directory UNIX usr openv netbackup vault Windows install_path NetBackup vault Recommended Action The vault directory is created when the vault package is installed on the master server Ensure that the vault job or command is started as root on the master server and that the vault directory has not been inadvertently removed or made inaccessible to root user NetBackup Status Code 287 Message failed attempting to copy consolidated report file Explanation This error occurs when a vault job is unable to copy the consolidated reports to the destination directory specified in the vault profile Recommended Action Ensure that the destination directory specified in the profile exists and is writable by root Also the vault job or command must be started with root privileges Correct the path and or permissions of the destination directory and rerun the vault job or command NetBackup Status Code 288 Message attempt to open a log file failed Explanation This error occurs when a vault job cannot create the detail log file or summary log file in the following directory UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path Netbackup vault sessions vault_name sidxxx where xxx is the session id Recommended Action Ensure that the above directory exists and has not been inadvertently removed after the vault job was started Ensure that this directory is writable
162. when the NetBackup Client service starts c Stop and restart the NetBackup services 4 See Testing Media Server and Clients on page 19 and Resolving Network Communication Problems on page 21 5 If necessary create debug log directories for the following processes and retry the operation Then check the resulting debug logs on the master server Ifthe error occurred during a backup operation check the bpsched debug logs Ifthe error occurred during a restore operation check the bprd debug logs NetBackup 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 This can also occur when the scheduler process bpsched is building its list of available storage units to use during backups Recommended Action Execute the ping command from one host to another by using the following combinations Note Also see Resolving Network Communication Problems on page 21 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 by using the name specified in the NetBack
163. ys criis oes tg ba in peie E a a aa ee anne EE 403 To Recover the Master Server total recovery 00 cece cece eee eee 403 Media Server Disk Recovery 6 66 ccc cee eee nae 405 Client System Disk Recovery Windows 66 66 c cece eens 406 ASSUMP TIONS ei aea ek cy EE E Qiao a craic Bet ad a ans eam aces 406 Contents v lt NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Before Starling speer sad peta eae ni pee iee ia E peie Ra aep S aoe G 406 To Recover a Windows Client Disk 0 00000 407 Recommended Backup Practices 6666s 409 Recovering the NetBackup Catalogs 0 0 ccc cence eee 409 Identifying the Most Recent Database Backup 0000 c cee eee 410 Example 1 List by Using a Raw Device 6 0 00 c cece ees 410 Example 2 List by Using a Media Manager Controlled Drive 411 Example 3 List Disk Path 0024 csse0ce sud ered ee vba ceva d RERA TEDRE 411 Procedures for Recovering NetBackup Catalogs 0 00 e eee 411 Before Starting i 041454 iaecdssa ees eup E Baas KEN heed 412 Recover Catalogs From Tape Media Manager Catalogs Lost 412 Recover Catalogs from Tape Media Manager Catalogs Intact 415 Recover Catalogs From Disk 0 416 Appendix A Functional Overview 00 00 e cece eee eee 419 Backup and Restore Functional Description
164. 0 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation The NetBackup internal catalogs were backed up by using the bpbackupdb command line and specifying a device path that does not exist Recommended Action Retry the command using a valid device file name NetBackup Status Code 123 Message specified disk path is not a directory Explanation NetBackup attempted to back up its internal catalogs and the backup attributes were set to dump to a disk However the disk file path already exists and is not a directory Recommended Action Specify a different disk path for the catalog backup or delete the file that already exists NetBackup 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 A possible cause is that the path does not exist 2 After determining which path could not be accessed correct the path names in the catalog backup configuration NetBackup Status Code 125 Message another NB database backup is already in progress Explanation Only one NetBackup catalog backup may be active at any given time Recommended Action None NetBackup Status Code 126 Message NB database backup head
165. 0 software if before the failure the system was a Windows NT 4 0 workstation NetBackup server software for Windows 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 master server Partitioning and formatting scheme that was used on the system you are restoring You must duplicate that scheme during Windows installation Latest NetBackup catalog backup on tape or disk To Recover the Master Server total recovery 1 Install a minimal Windows operating System perform the Express install Be certain to Partition the disk as it was before the failure if partitioning is necessary Then reformat each partition as it was before the failure Install Windows in the same partition that was used before the failure Specify the default workgroup Do not restore to the domain Follow any hardware manufacturers instructions that apply such as loading SSD on a Compaq system D Chapter 6 Disaster Recovery 403 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Master Server Disk Recovery Reboot the system when the install is complete 2 Install SCSI or other drivers needed to communicate with the tape drives on the system 3 Install NetBackup server software However do not configure any NetBackup policies or devices 4 Install an
166. 11 17 12 51 bpbkar ERR bpbkar FATAL exit status 11 system call failed 17 12 51 bpbkar INF EXIT STATUS 11 system call failed and the following in the usr openv netbackup logs online_ util log 17 12 51 onlfi_vfms_logf INF cannot snap_on err 5 17 12 51 delete _mount_point INF Deleted mount point tmp __jody_test 20958 17 12 51 onlfi_ freeze FTL V MS error 11 see following messages 17 12 51 onlfi_ freeze FTL Fatal method error 17 12 51 onlfi_freeze FTL vfm_freeze method nbu_snap type FIM function nbu_snap_ freeze 17 12 51 onlfi_ freeze FTL V MS method error 5 see following message 17 12 51 onlfi_ freeze FTL nbu_snap_ freeze Cannot turn on snapshot frozen image source opt cache dev rdsk cl1t3d1s0 snap error 5 17 12 51 onlfi_thaw WRN is not frozen Make sure that the file system specified for the frozen image source has been mounted The file system specified as the frozen image source does not correspond to the file system that contains the actual files as opposed to symbolic links to the files The mounted file system for the frozen image source must contain the actual files not symbolic links If items in the file list such as oracle datafileand oracle are actually symbolic links to export home orac1e the frozen image source must specify export or export home not oracle vxvm is selected as the frozen image method but the frozen image source is not configur
167. 17 Timeout waiting for robotic command Robotic Status Code 203 too many volumes in volume group Media Manager Status Code 68 tpformat Cannot open Format Optical Status Code 3 tpformat Cannot read Format Optical Status Code 4 tpformat Cannot seek Format Optical Status Code 5 tpformat Cannot set volume header Format Optical Status Code 2 tpformat Cannot write Format Optical Status Code 6 tpformat Command interrupted Format Optical Status Code 11 tpformat Existing media ID Format Optical Status Code 7 3 4 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages tpformat Invalid robot Format Optical Status Code 10 tpformat Invalid usage Format Optical Status Code 1 tpformat Must be root Format Optical Status Code 8 tpformat No media present in drive or robot slot Format Optical Status Code 13 tpformat Skip Format Optical Status Code 12 tpformat Tape request failed Format Optical Status Code 9 unable to generate a unique media id Media Manager Status Code 127 Unable to initialize robot Robotic Status Code 204 unable to link to dynamic library Media Manager Status Code 174 Unable to open drive Robotic Status Code 209 Unable to open robotic path Robotic Status Code 201 Chapter 5 Media Manager S
168. 2 Recovery procedures importing media 410 master when NT intact 399 NetBackup catalogs 409 NT client disk 406 NT master server disk 399 server disk 405 total on master 402 RedHat 10 redirect output to a file 54 Related manuals x Release notes online copy 440 removing a frozen image clone 63 64 Reports NetBackup 43 Restore process 432 NetWare client 437 Windows 98 95 client 435 Windows NT 2000 client 436 restore type for Backup Exec files 477 478 restoring Backup Exec files 478 robot drive number unknown 14 robot limit exceeded 14 type not determined 14 unknown 14 Robot drive selection 453 Robotic control daemons 451 Robotic daemons 451 Robotic test utility 471 acstest 471 RSM robot 471 tl4test 472 tl8test 472 Index NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows tldtest 472 tlhtest 472 ts8test 472 tsdtest 472 robtest 471 RSM robot 471 rsmd description 461 Scheduler bpsched 45 serialization problems 12 Server disk recovery 405 installation problems 10 NetBackup debug logs 44 NT disk recovery 399 recover master NT intact 399 test procedure for master 16 19 test procedure for media server 19 total recovery of master 402 ServerFree Agent pathname length 56 Services entries checking 25 slots too many 13 snaplist command 62 snapoff command 62 snapshot mirror VxVM 61 stale 62 Software version determining Macintosh clients 72
169. 3 52 07 MountMedia failure requested media not found 1012 02 05 02 13 50 10 PvlSession Mount C4B3BBAE 8B29 4823 ACE5 EBD546E1574B 1 1 4294967295 Job ID 689276194 Job Name Restore 2915851e Drive Pool FFFFFFFF 0000 0000 0000 000000000000 NetBackup Drives Media Set 00000009 0004 0000 0000 000000000000 Backup Exec and Windows NT Backup Media ERROR 0xA000810F E PVL_USER_ABORTED How to locate misplaced Backup Exec media If the media are robotic and have barcodes plus the robotic library has a barcode reader a NetBackup robot inventory update must be run on the robot in which the media reside Appendix D Backup Exec Tape Reader for NetBackup 491 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs This problem is more likely to occur with non barcoded robotic media The NetBackup media id of the Backup Exec media required for the restore can be obtained from the NetBackup job progress log For example 13 50 01 11 xxx Media id AO00000 is needed for the restore The NetBackup Media Manager volume database can be queried to determine the ADAMM GUID ADAMM GUID field of a Media Manager volume database record the description and residence robot and slot number of the media id The media id is A00000 in the above example The Backup Exec cartridge label of the media can be determined from the
170. 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages group is not valid for this host Media Manager Status Code 128 Host is not the scan host for this shared drive Device Management Status Code 48 incompatible database version Media Manager Status Code 146 Incomplete robot information Device Configuration Status Code 24 Incorrect tpreq access mode Device Management Status Code 42 invalid barcode Media Manager Status Code 10 invalid change type Media Manager Status Code 75 invalid change entry request Media Manager Status Code 50 Invalid command code Robotic Status Code 207 invalid command usage Media Manager Status Code 4 invalid database version header Media Manager Status Code 56 376 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages invalid description Media Manager Status Code 11 Invalid device path name Device Configuration Status Code 19 Invalid drive index Device Configuration Status Code 14 invalid drive name Media Manager Status Code 129 Invalid Drive Number Device Management Status Code 23 Invalid drive type for the robot Device Configuration Status Code 27 Invalid Drive Type Density Device Management Status Code 1 invalid expiration date Med
171. 42 robot number and robot host mismatch Media Manager Status Code 61 Chapter 5 Media Manager Status Codes and Messages 389 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages robot number and robot type mismatch Media Manager Status Code 54 robot number and volume group mismatch Media Manager Status Code 55 Robot number does not exist Device Configuration Status Code 31 Robot number does not exist Robotic Status Code 214 Robot number is already in use Device Configuration Status Code 21 Robot number is in use by another robot Device Configuration Status Code 30 robot type and volume group mismatch Media Manager Status Code 81 Robot type is not supported on this platform Device Configuration Status Code 6 Robotic arm has no addressable holder Robotic Status Code 222 Robotic daemon not licensed Robot Error Status Code 17 Robotic dismount failure Robotic Status Code 206 Ww 390 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Robotic mount failure Robotic Status Code 205 robotic volume position is already in use Media Manager Status Code 37 RSM is supported only on Microsoft Windows 2000 and later OS versions Device Configuration Status Code 48 rule database
172. 484 Contents vii lt NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Examples ee eiee ag iE ea NEE eE EE ENEE Ge ise ENE EEA ER EE 487 GIOSSANY ccd be astani pea See serene EEE ares eum eta Sie eee oe aeons 493 TT Galen eee 521 viii NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Preface This guide explains how to isolate and resolve problems encountered when installing configuring or using VERITAS NetBackup for Windows This publication refers to VERITAS NetBackup as NetBackup This includes coverage for Media Manager a component of NetBackup used for media and device management 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 Windows Some sections will also be useful to less technical users who encounter problems when backing up archiving or restoring files Organization Chapter 1 Introduction explains how to define a problem and describes the information you should gather during troubleshooting Both administrators and client users should read this chapter first Chapter 2 Troubleshooting Procedures includes procedures for isolating the p
173. 60 1660 3324 lt 2 gt bpcd_ restore image files mediaid BE0001 16 11 00 960 1660 3324 lt 2 gt bpcd_ restore image files keyword 22 16 11 00 980 1660 3324 lt 2 gt bpcd_ restore image files obj desc NULL 16 11 00 980 1660 3324 lt 2 gt bpcd_ restore image files keep 1 16 11 00 980 1660 3324 lt 2 gt bpcd_restore image files progress file G nb NetBackup logs user_ops adonijah logs NBWIN007 16 11 00 980 1660 3324 lt 2 gt bpcd_ restore image files rename_file NONE 16 11 00 980 1660 3324 lt 2 gt bpcd_ restore image files commit 0 16 11 00 980 1660 3324 lt 2 gt bpcd_ restore _ image files dirByteCount 0 16 11 00 980 1660 3324 lt 2 gt bpcd_restore_ image files tempDirectory NONE 16 11 00 980 1660 3324 lt 2 gt bpcd_restore_image files mountDatabase 0 16 11 00 980 1660 3324 lt 2 gt bpcd_restore_ image files beFilePathLen 19 16 11 00 980 1660 3324 lt 2 gt bpcd_restore_image files beRedirectionPath f temp be_ restore 16 11 01 010 1660 3324 lt 2 gt createProcessWithOutput CreateProcess of gt D nb NetBackup bin bptm exe guid ev BE0001 cmd lt 16 11 01 992 1660 3324 lt 2 gt MediaID2MediaGuid Backup Exec media id BE0001 has guid 6EE3FFEF B111 4EDD 97C1 78931D988268 voldb dell_2 16 11 04 185 The previous text indicates that bptm obtained the ADAMM GUID 6EE3FFEF B111 4EDD 97C1 78931D988268 corresponding to Media Manager media ID BE0001 from the Media Manager volume data
174. 6c cece e eee eee 419 Startup PLOCeSS as oi ciate Aha een hare EE ayaa E E E ceaheaats 420 Backup and Archive Processes nuunuu nunnana rannen rarnana 422 Backups and Archives UNIX Clients na na uanara ccc ene 422 Backups and Archives Windows 95 98 Clients 0000 000005 426 Backups and Archives Windows NT 2000 Clients 0 427 Backups and Archives NetWare Clients 0 0c cece eee 428 Backups Macintosh Clients 00666 c ccc 429 NetBackup Database Backups 0 606 c cence aes 430 Restore Processes seci setie dain icin EE ay ee in AS E E E aes 432 Restores UNIX Clients ricor bess iieri eee bees 432 Restores Windows 95 98 Clients 66 cc cece eee eee ees 435 Restores Windows NT 2000 Clients 0 0 e cece eee eee 436 Restores NetWare Clients 0 0 00 437 Restores Macintosh Clients 0 0 e eee eee eee eee ee 438 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Directories and Files 0 0 0 cece eee cece 439 NetBackup Programs and Daemons 0 0 6 6066 c cece eens 441 NetBackup Databases 0 00 0 c ccc ccc cece eee 450 Media Manager Functional Description 0 666 c eee eee 450 Startup PLOCESS esi cde tides piden e i e p i a sig dines GMa MONEE idle G G E grees 451 M
175. 7 2001 01 27 18 PM the restore failed to recover the requested files 13 52 13 11 xxx INF Status the restore failed to recover the requested files NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs In the following log file the message User canceled a Physical Volume Library operation implies that Backup Exec could not get the required media from NetBackup Media Manager This can happen when the media is misplaced For example Backup Exec job progress log BEX09 txt Error Mount failed A A A AA User canceled a Physical Volume Library operation Unable to acquire device for the specified pool and media A A A AA User canceled a Physical Volume Library operation The adamm log file in the Backup Exec install path indicates the ADAMM GUID of the media that was required for the restore The adamm log file indicates whether or not the media was misplaced In the following example log the text MountMedia failure requested media not found indicates that the Backup Exec media having ADAMM GUID C4B3BBAE 8B29 4823 ACE5 EBD546E1574B was misplaced The Backup Exec install path can be obtained from the following registry value HKEY LOCAL MACHINE SOFTWARE VERITAS Backup Exec Install Path This is the adamm log file in the Backup Exec install path 1012 02 05 02 1
176. 9 97 001 31 38 PM the 21 21 97 xxx 97 001 DELL 2 Unable to requested files INF Status Unable to start Backup Exec restore job on host connect to the Backup Exec engine on host DELL 2 Status of restore from image created 12 07 2001 restore failed to recover the requested files the restore failed to recover the The above text indicates that the Backup Exec services are not running on media server dell_2 Example 4 If a Backup Exec restore job has been launched with an invalid restore path the bpcd log file indicates the error In the example below the user intends to redirect to D public restored ona Windows machine The path should be specified as D public shared if D is shared as D However the path was incorrectly specified as D public restored The bpcd log below shows the error 16 26 59 684 16 26 59 684 16 26 59 684 redeemer 16 26 59 694 redeemer 59 694 59 694 59 694 59 694 59 694 59 694 progress file 59 694 59 694 59 694 59 694 59 694 59 694 59 694 1516 1516 1516 1516 1516 1516 1516 1516 1516 1516 1516 1516 1516 1516 D Public Restored 1516 1420 1516 1420 1420 1420 1420 1420 1420 1420 1420 1420 1516 1420 1420 1420 1420 1420 1420 1420 lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt 225 lt 2 gt lt 2 g
177. A request to change volume residence with media eject was sent to vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows but the volume s robot type does not support automated media eject Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that change volume residence requests with eject for the robot type involved with a newer release version level are not sent to vmd on a system running an older incompatible software version level Media Manager Status Code 52 Message cannot auto inject this robot type Chapter 5 Media Manager Status Codes and Messages 225 I NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation A request to change volume residence with media inject was sent to vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows but the volume s robot type does not support automated media inject Recommended Action 1 Examine command output
178. BPCD NetBackupBPCD handles the request in the same way as the UNIX bpcd NetBackupBPCD also includes bpbkar functionality The archive that the Macintosh client generates is essentially the same as the archive from a UNIX client One difference is that the Macintosh file names may be slightly different in the NetBackup archive see the NetBackup User s Guide Macintosh for an explanation of the differences Appendix A Functional Overview NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 9 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 Or After scheduled user directed or manual backup or archive sessions that result in the creation of at least one backup or archive image For automatic database backups NetBackup uses the scheduler bpsched to determine if any backups are required The scheduler is activated by the request daemon bprd at intervals determined by the Wakeup Interval global attribute If a backup is needed bpsched uses the client daemon bpcd to start the database ba
179. BPINETD serves the same purpose as inetd on UNIX clients The NetBackup client daemon is called BPCD BPBKAR32 serves the same purpose as bpbkar on UNIX clients The server processes are the same as described for UNIX Server Windows NT 2000 Client For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter NetBackup User Interface Com yee e Op Backy l a ERAR Gent Disk Client Disk Appendix A Functional Overview 427 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 For NetWare target the user interface program is called BP on the Netware console The bpbackup bparchive and bplist functions are merged into the user interface programs on the clients The NetBackup NetWare client daemon is called BPCD The bpbkar functions are merged into BPCD The server processes are the same as described for UNIX
180. Backup 4 5 Troubleshooting Guide for Windows Getting Help Open http www support veritas com in your web browser Click Contact Support The Contacting Support Product List page appears Select a product line and then a product from the lists that appear The page will refresh with a list of technical support phone numbers that are specific to the product you just selected Preface X111 v NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Getting Help wr iv NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Introduction 1 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 may or may not apply to the NetBackup BusinesServer product and depends on the context When troubleshooting a BusinesServer installation be aware that there is only one host the master and media server are one and the same References to a media server on a different host can be ignored Define the Problem The first step in troubleshooting is to define the problem What was the Error Indication In defining the problem you must know what went wrong and sometimes resolving the problem also requires that y
181. Backup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog match the settings in the services file To display this dialog start the Backup Archive and Restore interface and click NetBackup Client Properties on the File menu The values on the Network tab are written to the services file when the NetBackup Client service starts Also see Verifying Host Names and Services Entries on page 25 3 Check the level of network activity An overloaded network can cause this error 4 Ifthe above actions do not reveal the problem create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Status Code 20 Message invalid command parameter Explanation One or more command parameters were not valid This error can occur when a master and its media servers or a master server and a client have different levels of NetBackup installed For example if a NetBackup master server has NetBackup 4 5 and the media server has NetBackup 3 4 This error can also occur if the wrong parameters are used when executing a command line Recommended Action 1 Check the NetBackup Problems report for clues 2 Ifthe error occurs when executing a command on the command line verify that the parameters are valid 3 For NetBackup ServerFree Agent Ifthe following appears in the usr openv netbackup l
182. Backup UNIX systems and authenticates users that start the NetBackup Java interface programs Started By inetd during startup of the NetBackup Java interfaces Stopped By When authentication is complete Debug Log usr openv netbackup logs bpjava msvc NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Description Daemon bpjava usve NetBackup Java user server application program This program services all requests from the NetBackup Java user and administration interfaces Started By bpj ava 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 Debug Log usr openv netbackup logs bpjava usve bprd On master servers the request daemon responds to client and administrative requests for the following Restores Backups scheduled and user directed Archives List backed up or archived files Manual immediate backups started through the NetBackup administration interface manual backup option Started By Initiate Request Daemon option in the NetBackup administrator interface also the usr openv netbackup bin initbprd command Stopped By Terminate Request Daemon option in the N
183. Backup application software The command that starts the utility is located in the following directory install_path NetBackup bin Run it in an MSDOS command window so you can see the results 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 bpc1lntcmd uses gethostbyaddr on the NetBackup node and gethostbyaddr returns the host name with the IP address as defined in the node s DNS WINS or local hosts file entries No connection is established with the NetBackup server bpclntcmd hn Hostname The hn option allows you to specify a host name bpclntcmd uses gethostbyname on the NetBackup node to obtain the IP address associated with the host name defined in the node s DNS WINS or local hosts file entries No connection is established with the NetBackup server You can use the ip and hn options to verify the ability of a NetBackup node to resolve the IP addresses and host names of other NetBackup nodes For example you can verify that a NetBackup server can connect to a client In this case the steps are NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures
184. CS drive identifiers is limited to certain ranges based on the robot type These limits are based on a supported device list An invalid robot drive number means that the drive number was not within the acceptable range Make sure that the robot hardware is supported and that the required patches are installed to support the robotic library If the robot type is TLH or TLM do not specify a robot drive number because the drives are addressed using a vendor drive name Device Configuration Status Code 29 Message Drive index is in use by another drive Explanation On a request to add a drive to the device configuration the requested drive index was found to be in use on the targeted device host Recommended Action 1 To avoid configuring a drive index that is already in use use the Device Configuration wizard on supported device discovery platforms so that the drive index is automatically configured 2 If using a device configuration interface that allows the drive index to be specified use tpconfig d to determine the drive indexes that are already in use on the targeted device host and specify a drive index that is not already in use Device Configuration Status Code 30 Message Robot number is in use by another robot Explanation On a request to add or update a robotic drive in the device configuration it was found that the robot number and robot type specified were associated with an existing robot of a different robot type
185. Code 131 Message requested drive is not registered for host Explanation A request was made to reserve a shared drive with vmd DA the device allocator for Shared Storage Option The drive was not registered by the requesting host although other drives had been registered by that host This is an abnormal condition that could occur if two different hosts with the same host name local host name overridden by any SSO_LHOST_NAME entries in the Media Manager configuration file vm conf have registered different drive lists with vmd DA and one of those hosts has requested a drive reservation Recommended Action Use unique non duplicate strings for host names and SSO_HOST_NAME configuration file entries Media Manager Status Code 132 Message requested drive is not currently registered Explanation A request was made to reserve or release a shared drive with vmd DA the device allocator for the Shared Storage Option The drive was not registered by the requesting host or any other hosts Recommended Action This is an abnormal condition that could occur in the following situations vmd DA was stopped and restarted This situation will be automatically handled because the requesting host re registers its drives with vmd DA when this error is encountered Media Manager Status Code 133 Message requested drive is not reserved by host Chapter 5 Media Manager Status Codes and Messages 267 NetBackup 4 5 Troubleshooting Gu
186. Device Configuration wizard on supported device discovery platforms so that device paths and device names are automatically configured 2 Display the device configuration using tpconfig d or a device configuration interface to see the robotic information that is already configured On Windows hosts where there are multiple ways to configure robots changer names or port bus target LUN check the operating system configuration or registry for changer names and their associated SCSI paths Check for detailed errors from the command or user interface output Device Configuration Status Code 24 Message Incomplete robot information Explanation On a request to change the device configuration some of the required robot information was not specified Recommended Action Check the command usage and reissue the request with all required robot information specified Device Configuration Status Code 25 Message Robot drive number in use for this robot Explanation On a request to change the device configuration the specified drive address in the robot was found to be already in use by another drive in the device configuration Recommended Action The drive address in the robot is the robot drive number for most robot types the ACS LSM PANEL DRIVE coordinates for ACS robots or a vendor drive name for TLH and TLM robots Two drives cannot have the same drive address in a robot in a given device configuration If the drive addresses need to b
187. Device Manager service on Windows Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Robot Error Status Code 10 Message Fork failure occurred Explanation A robotic daemon process could not create a child process due to a system error This is probably an intermittent error based on the availability of resources on the system This applies to UNIX servers only Recommended Action 1 Restart the device daemon at a later time and investigate system problems that limit the number of processes 2 Examine the system logs for a more detailed message on the error Increase the level of verbosity by adding the VERBOSE option in the vm conf file Restart the device daemon then retry the operation and examine the system log file Robot Error Status Code 11 Message System error occurred Explanation A robotic daemon process encountered a system error NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows Ne
188. Device Monitor command to resubmit the request so the mount request can occur For a NetBackup job if the media is not in the robot 1t id sends a mount request which is then canceled once the media is determined to be missing and another volume is selected to be mounted A mount request is also issued if the media is for a nonrobotic standalone drive and the drive does not contain media that meets the criteria in the request If the request is from NetBackup and the drive does contain appropriate media then that media is automatically assigned and the operation proceeds See the NetBackup System Administrator s Guide for more information on NetBackup media selection for nonrobotic drives Note When a tape is being mounted the drive_mount_notify script is called This script is in the usr openv volmgr bin directory Information on the script can be found within the script itself A similar script is called for the unmount process drive_unmount_notify in the same directory When a robotic volume is added or removed through the media access port the media management utility communicates with the appropriate robotic daemon to verify the volume location and or barcode The media management utility through a library or command line interface also calls the robotic daemon for robot inventory operations Appendix A Functional Overview 453 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guid
189. E option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 217 oO NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 Query for or sort volume records by barcode to identify the existing volume entry with the same barcode as that specified for the volume entry being added or changed Media Manager Status Code 37 Message robotic volume position is already in use Explanation A volume entry being added to or changed in the volume database had a robotic coordinate slot number or slot number and platter side which was a duplicate of the robotic coordinate for another volume already in the volume database All volumes in a volume database must have unique robotic coordinates Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Query for
190. ELIST is a faceless background application that NetBackup launches in order to get a list of backup images from the master server NetBackupBPLIST is a faceless background application that NetBackup launches in order to get a list of backed up files from the master server The application extension NetBackupListen starts executing when the Macintosh is booted and listens on the BPCD port number for backup requests from a NetBackup server When NetBackupListen gets a request it launches the faceless background application Net BackupBPCD NetBackupBPCD handles the request in the same way as the UNIX bpcd NetBackupBPCD also includes NetBackup tar functionality The server processes are the same as described for UNIX NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description NetBackup Directories and Files Figure 12 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 12 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 12 A Windows NetBackup server has equivalent files and directories that are located in the directory where NetBackup is installed C Program Files Veritas by default
191. ERITAS support web site This robot type is supported only by NetBackup DataCenter servers TL4 Tape Library 4MM A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site Glossary 515 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows TL8 Tape Library 8MM A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site 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 which 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 tpconfig also has a command line interface transfer rate The rate at which computer information is transferred between a source and a destination transport See robotic arm true image restore Restores the contents of a directory to what it was at the time of any scheduled full or incremental backup Previously deleted files are ignored TS8 Tape Stacker 8MM A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site
192. Explanation An invalid or missing device serial number was encountered in a request to modify the device configuration Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Identify the targeted host and verify that all Media Manager binaries on that host are at a compatible version level with other hosts that are part of the configuration Update the software version as needed Media Manager Status Code 162 Message the global device database device name is invalid Explanation An invalid or missing device name was encountered in a request to modify the device configuration Recommended Action Chapter 5 Media Manager Status Codes and Messages 279 E NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option
193. Explanation The catalog has an inconsistent or corrupted entry Recommended Action Obtain detailed troubleshooting information for bpdbm NetBackup Database Manager service by creating a debug log directory for it Then retry the operation save resulting debug log and call customer support Chapter 4 NetBackup Status Codes and Messages 149 a NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 239 Message the specified client does not exist in the specified policy Explanation The specified client is not a member of the specified policy Recommended Action Correct the client name specification specify a different policy or add the required client name to the policy After making the correction retry the operation NetBackup Status Code 240 Message no schedules of the correct type exist in this policy Explanation The appropriate schedule was not found in the specified policy For example a user backup specified a policy name but no user backup schedule exists in that policy Recommended Action Specify a different policy or create a schedule of the needed type in the policy After making the correction retry the operation NetBackup Status Code 241 Message the specified schedule is the wrong type for this request Explanation The schedule that was specified for an immediate manual backup is not for a full nor an incre
194. For more information refer to the NetBackup System Administrator s Guide for Windows The requesting client is the value from the gethostname function on the client 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 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows By the time these names appear in the bprd debug log the requesting client name has been translated into the client s configured name Depending on the particulars of the restore request for example from root on a server from a client to a different client and so on the name used to connect back to the client to complete the restore is either the client s peername or its configured name When modifying client names in NetBackup policies to accommodate specific network paths the administrator needs to consider The client name as configured on the client On a Windows client it is on the General tab of the NetBackup Configuration dialog box To open this dialog box click Configure on the Actions menu in the Backup Archive and Restore interface The client as currently named in the policy configuration Ex
195. Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Error in SEMAPHORE operation Robotic Error Status Code 9 Error in Sending Daemon Message Device Management Status Code 5 Error in Sending Operator Message Device Management Status Code 3 Error in Sending User Message Device Management Status Code 7 Evaluation period expired Go to www veritas com to order this product Media Manager Status Code 165 failed appending to pool database Media Manager Status Code 104 failed appending to rule database Media Manager Status Code 121 failed changing terminal characteristics Media Manager Status Code 45 failed during tpformat Media Manager Status Code 77 failed initiating child process Media Manager Status Code 88 failed making the database directory Media Manager Status Code 25 Chapter 5 Media Manager Status Codes and Messages 3 3 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages failed opening tmp output file Media Manager Status Code 86 Failed reading drive or robot config file Device Configuration Status Code 13 failed receiving from robotic software daemon Media Manager Status Code 44 failed receiving from vmd Media Manager Status Code 72 failed redirecting input to pipe Media Manager Status Code 62 failed redirecting tmp output file Media Manager
196. Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs Figure 3 Recover Catalogs From Tape 8 mm tape drive Tape1 Master Server shark aa Tape with catalog backups Disk 1 IL D VERITAS Netbackup db D VERITAS Volmgr database 2 Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel to stop the following services if they are running NetBackup Request Manager service NetBackup Database Manager service NetBackup Device Manager service NetBackup Volume Manager service 3 Use the Activity Monitor or the Services application in the Windows Control Panel to verify that the NetBackup Client Manager service is running Start it if necessary 4 On the NetBackup server where the drive attaches execute the bprecover command Specify the raw device path for the drive where you inserted the tape in step 1 Example 1 This example interactively restores images to disk 1 on Figure 3 by using raw device path Tapel bprecover r tpath Tapel Recover shark D VERITAS NetBackup db y n n y Recover shark D VERITAS Volmgr database y n n y Recovering shark D VERITAS NetBackup db Recovering shark D VERITAS Volmgr database Example 2 yy Chapter 6 Disaster Recovery 413 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshoo
197. MINIT failed status 1 EXIT STATUS 11 system call failed 15 54 04 INF Status system call failed EMC releases several different versions of its SYMAPI library libsymapi so to support multi threading 32 bit and 64 bit machines and so forth The library name and install location vary depending on your configuration When the SYMAPI library is being installed the EMC package creates a link to the correct library file name but in some cases this link may not point to the correct directory usr symc1i This may happen if your installation has multiple packages or if you install another version such as multi threaded or 64 bit symc1i Without the proper symbolic link Fastrax backups will fail As a result you may need to create a usr symcli symbolic link to the SYMAPI shared libraries For instance NetBackup Fastrax must be able to find the following usr symcli shlib libsymapi so usr symcli shlib libsymlvm so The default symc1i location is the following lrwxrwxrwx 1 root other 22 Dec 3 09 23 symcli gt opt emc SYMCLI V4 3 2 Note that this example is for version 4 3 2 4 A frequent cause is that the server s file system is full For example you may see a message similar to the following in the Problems report or bpdbm debug log 06 27 95 01 04 00 romb romb db FLISTsend failed system call failed 11 06 27 95 01 04 01 romb romb media manager terminated by parent process 06 27 95 01 05 15 romb romb backup
198. NT 2000 pluto WindowsNT 2000 dle meteor Client pluto Ethernet NetBackup Configuration 7 Servers ier iubi figuration fon Server List jupiter master NetBackup Configura NetBackup Configuration Saur esnean Servers Servers Server List jupiter Server List jupiter Client Name jupiter saturn saturn CE General General etc services Client Name mars Client Name pluto bpcd 13782 tcp bpcd bprd 13720 tcp bprd D a bpdbm 13721 tcp bpdbm etc services etc services vmd 13701 tcp vmd bpcd 13782 tcp bpcd bpcd 13782 tcp bpcd odid 13706K6p odid bprd 13720 tep bprd bprd 13720 tep bprd Notes 1 The NetBackup Client Properties dialog also has a Network tab with NetBackup client service port BPCD and NetBackup request service port BPRD settings that must be the same as the bpcd and bprd settings in the services file 2 The complete path to the Windows NT 2000 etc services file is SystemRoot system32 drivers etc services 3 All other applicable network configuration must also be updated to reflect the NetBackup information For example this could include the SystemRoot system3a2 drivers etc hosts file and also WIN and DNS if used NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures First we examine the configuration of the r
199. NetBackup ServerFree Agent only If the following message appears in the usr openv netbackup bptm log and the values for key asc and ascq are all zero 0x0 as shown in this example message tape error occurred on extended copy command key 0x0 asc 0x0 ascq 0x0 your host bus adapter and its driver are probably not supported by NetBackup 4 0V The host bus adapters and drivers supported in the release are listed in Chapter 2 of the NetBackup Release Notes 2 For additional information check the following NetBackup Problems report to determine the device or media that caused the error Event Viewer Application and System logs 3 If NetBackup was writing backups to a disk file verify that the disk has enough space for the backup 4 If the media is tape check for A defective or dirty drive in which case clean it or have it repaired refer to the tpclean command for robotic drives 100 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes The wrong media type Verify that the media matches the drive type you are using Defective media If this is the case use the bpbmedia command to set the volume to the FROZEN state so it is not used for future backups Incorrect drive configuration Verify the Media Manager and system configuration for the drive This often results in the
200. NetBackup status codes in numerical order and includes an explanation of what occurred along with recommended actions The second section Messages lists the same status codes but sorts them alphabetically according to the message Only the messages and status codes are included in the second section If you see a status code without its associated message text you can determine the message its explanation and recommended action by using the bperror command install_path NetBackup bin adminemd bperror statuscode statuscode recommendation where statuscode is the number of the message Example install_path NetBackup bin admincemd bperror statuscode 150 termination requested by administrator The process is terminating or has terminated as a direct result of a request from an authorized user or process Status Codes 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 NetBackup Status Code 0 Message the requested operation was successfully completed NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation There were no problems detected with the requested operation Recommended Action None unless this was a database backup performed through a database extension
201. P host Fora policy type other than NDMP verify that the policy specifies a Media Manager or Disk type storage unit NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 158 Message failed accessing daemon lock file Explanation The process could not lock its lock file because an error was received from a system call This lock file synchronizes process activities for example preventing more than one daemon from executing at a time Recommended Action 1 Examine the NetBackup error log to determine why the system call failed and correct the problem It could be a permission problem 2 Ifthe error log does not show the error create a debug log directory for bprd bpdbm or bpsched depending on which process encountered the error and retry the operation Examine the resulting debug log NetBackup Status Code 159 Message licensed use has been exceeded Explanation A configuration limit has been exceeded An example is number of drives allowed per server Recommended Action To determine the cause examine the NetBackup error logs for the command that was being executed NetBackup Status Code 160 Message authentication failed Explanation A problem was encountered when two systems were attempting to authenticate one another Recommended Action See the NetBackup System
202. Properties on the File menu Also verify that the setting on the Network tab matches the one in the services file The services file is located in sSystemRoot system32 drivers etc services Correct the port number if necessary and reboot the Macintosh f Verify that the NetBackup request daemon bprd port number is the same as on the server by default 13720 On the client this is the bprdport setting in the mac conf file in the NetBackup folder in the Preferences folder Ona Windows NetBackup server check the NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog To display this dialog box start the Backup Archive and Restore interface on the server and click NetBackup Client Properties on the File menu g Ensure that other values in mac conf are correct and also check the bp conf file Both files are in the Netbackup folder in the Preferences folder If you make changes to mac conf or bp conf reboot the Macintosh 7 Verify that the hosts file or its equivalent contains the NetBackup server name On Windows clients the hosts files are SystemRoot system32 drivers etc hosts Windows NT 2000 TRS 24 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures C Windows hosts Windows 98 or 95 NetWare clients SYS
203. Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 Check for data integrity or consistency problems in the volume database by using a media management interface or vmdb_dump Delete or move volume entries so that the volume group issues are corrected Media Manager Status Code 66 Message no cleaning tape available Explanation The volume database was queried for cleaning tapes by robot number No cleaning tape in the specified robot with available cleanings remaining was found in the volume database Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Either add cleaning tapes to the robot physically and logically in the volume database with a media management interface or change the number of allowed cleanings if a cleaning tape is already configured and the cleaning tape is to be used beyond its allocated use cycles Then reissue the cleaning request or wait for the cleaning request to be automatically submitted when a drive in the robot once agai
204. Status Code 85 Message volume daemon fork failed Explanation A Media Manager daemon or service could not create a child process due to an error received from the system This is probably an intermittent error based on the availability of resources on the system Recommended Action 1 Restart the service at a later time and investigate system problems that limit the number of processes 2 Examine debug and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 243 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Code 86 Message failed opening tmp output file Explanation The Media Manager configuration file vm conf or temporary working file could not be opened Recommended Action On UNIX check for the existence and permissions of the usr openv volmgr misc directory tmp directory and usr openv volmgr vm conf file On Windows check for the existence and security properties of the install_path Volmgr vm conf file Media Manager Status Code 87 Message
205. Status Code 281 vltCore System Error NetBackup Status Code 282 vltCore UnhandledError NetBackup Status Code 283 vmchange api_eject command failed NetBackup Status Code 301 Chapter 4 NetBackup Status Codes and Messages 199 EN NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages vimchange eject verify not responding NetBackup Status Code 300 wbak exited abnormally NetBackup Status Code 62 wbak was killed NetBackup Status Code 61 You are not authorized to use this application NetBackup Status Code 501 200 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Codes and Messages 5 This chapter lists Media Manager status codes and messages In each of the following subsections the status codes are listed in numerical order followed by an explanation and recommended action Media Manager Status Codes Device Configuration Status Codes Format Optical Status Codes Device Management Status Codes Robotic Status Codes gt gt Robotic Error Codes At the end of this chapter is a section titled Messages which lists all Media Manager messages alphabetically Following each message is a pointer to the section in this chapter that contains detailed information about the messa
206. T 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action 1 Examine the command input debug logs and system logs for a more detailed message on the system error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option a Retry the operation and examine the logs 2 Obtain the specific system call failure from the debug log and investigate operating system functionality related to the failure Execute the hostname system command to see if the command is operating correctly Media Manager Status Code 77 Message failed during tpformat Explanation A request was made to format an optical platter and the request failed or was aborted by the administrator The optical volume format may have failed because a WORM write once read many platter cannot be reformatted Ifthe overwrite label option was not specified and the format operation is not interactive the format optical operation will fail if the platter has already been formatted Ifthe administrator chooses to abort the format operation after it has been found that the platter has already been formatted the format request will return with this status code The format operation may hav
207. Then stop and restart 1t id the Media Manager device daemon on UNIX or NetBackup Device Manager service on Windows Robot Error Status Code 7 Message No robots are configured Explanation A robotic daemon process was started but no robots of the associated robot type are configured Recommended Action Robotic daemons processes will not run if there are no robots configured for the associated robot type Add or reconfigure one or more robots then stop and restart 1tid the Media Manager device daemon on UNIX or NetBackup Device Manager service on Windows Robot Error Status Code 8 Message No memory available Explanation A robotic daemon process was unable to allocate memory This error occurs when there is insufficient system memory available This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory Recommended Action Free up memory by terminating unneeded processes Add more swap space or physical memory Chapter 5 Media Manager Status Codes and Messages 361 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Robot Error Status Code 9 Message Error in SEMAPHORE operation Explanation A process was unable to perform a semaphore operation such as lock or unlock associated with resources maintained by 1tid 1tid is the Media Manager device daemon on UNIX or the NetBackup
208. Windows NetBackup 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 Recommended Action 1 Determine the activity that encountered the handshake failure by examining the NetBackup All Log Entries report for the appropriate time period If there are media servers determine if The handshake failure was encountered between the master and a media server or Only the master server was involved 2 If necessary create the following debug log directories for the following bpcdon the NetBackup media host can be either the master or a media server Ifthe error was encountered during a backup operation bpsched on the master server Ifthe error was encountered during a restore operation bprd on the master server Ifthe error was encountered during a media list operation admin in the NetBackup logs admin directory on the master server 3 Retry the operation and examine the resulting debug logs for information on why the error occurred NetBackup Status Code 202 Message timed out con
209. Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages invalid volume move mode Media Manager Status Code 53 Invalid volume pool specified Device Management Status Code 65 invalid volume pool Media Manager Status Code 90 IPC Error Daemon may not be running Device Management Status Code 22 IPC sequence error Device Management Status Code 10 LTI Daemon may not be running Robot Error Status Code 2 Magic Number MisMatch Device Management Status Code 29 Media access port already contains media Robotic Status Code 221 Media access port does not contain media Robotic Status Code 220 Media access port is available Robotic Status Code 250 Media access port is in eject mode Robotic Status Code 253 Chapter 5 Media Manager Status Codes and Messages 381 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Media access port is in inject mode Robotic Status Code 252 Media access port is unavailable Robotic Status Code 251 media access port not available Media Manager Status Code 166 media generation rule already exists Media Manager Status Code 138 media generation rule does not exist Media Manager Status Code 139 media ID is not the specified media type Media Manager Status Code 95 media ID not unique in database Media Manager Status Code 34 media
210. Windows Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather output from the ipcs a command to see what resources are currently in use Device Management Status Code 14 Message Error in IPC SHMAT call Explanation A process was unable to attach a shared memory segment that lt id maintains 1tid is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather the output of the ipcs a command to
211. Windows on the volume database host where the cleaning media is defined by sending a request to it or using a media management interface 4 Examine command output if available debug logs and system logs for messages related to the error Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the device daemon 1tid on UNIX or the NetBackup Device Manager service on Windows Device Management Status Code 60 Message No robot daemon or robotics are unavailable Explanation A robot was not configured or was operationally unavailable Specifically an attempt may have been made to automatically clean a robotic drive but the robot is not defined or is unavailable Alternatively on an attempt to initialize the shared drive lists a drive was found to be configured as robotic without the required robot configured Recommended Action Display the device configuration and ensure that the drive and robotic configuration information are consistent Check the operational status of the robot and robotic software by checking the system log files If more detail on robot operational status is needed increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1t id the device daemon NetBackup Device Manager service Device Management Status Code 61 Message No media found in device or robot slot p
212. a ID not unique in database Explanation A volume entry being added to or changed in the volume database had a media ID or optical partner ID specified which was a duplicate of the media ID for another volume already in the volume database All volumes in a volume database must have a unique media ID Recommended Action 1 Examine the daemon and reqlib debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs 2 When adding volumes to the volume database specify a media ID that is unique Media Manager Status Code 35 Message volume does not exist in database NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation A requested operation encountered a case where a volume query did not return a volume entry matching the search criteria Recommended Action 1 Examine the daemon and reqlib debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase
213. a bpdbm debug log directory and retry the operation Then check the resulting debug log NetBackup Status Code 229 Message events out of sequence image inconsistency Explanation A request was made which if satisfied would cause the image catalog to become inconsistent Recommended Action Obtain detailed troubleshooting information by creating a debug log directory for bpdbm Then retry the operation save the resulting debug log and call customer support NetBackup Status Code 230 Message the specified policy does not exist in the configuration database Explanation The specified policy name does not exist Recommended Action Correct your parameters or options and retry the operation NetBackup Status Code 231 Message schedule windows overlap Chapter 4 NetBackup Status Codes and Messages 17 yr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation The start and duration times specified for one day of the schedule overlap with another day of the schedule Recommended Action Correct the schedule to eliminate the overlapping backup windows NetBackup Status Code 232 Message a protocol error has occurred Explanation This is an intermediate status code that usually precedes another status code It indicates that either the bpdbm process NetBackup Database Manager service or the process communicating with it has received unexpe
214. a robot host that matches the configured robot control host 4 Check the system log on the robot control host to see if the robotic process is processing requests during the time when communications with it are attempted Perform Resolving Network Communication Problems on page 21 Media Manager Status Code 44 Message failed receiving from robotic software daemon Explanation An attempt to read data from a robotic software daemon process socket failed Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 22 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 Identify the targeted robotic process by looking at the robot type and at the robot host on the robotic request or the robot host field of the volume being operated on Verify that the robotic process used for robotic control is available and handling requests see table Media Manager Daemons and Programs on page 459 3
215. abled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Examine the permissions and available file system space for writing to the database usr openv volmgr database ruleDB UNIX or install_path Volmgr database ruleDB Windows Media Manager Status Code 122 Message barcode tag is not unique in rule database Explanation A request was made to add a barcode rule and the barcode tag specified was a duplicate of the tag for an existing barcode rule Recommended Action On the add barcode rule request specify a barcode tag that is not already in use on the specified volume database host Media Manager Status Code 123 Message rule database lock operation failed Explanation vmd the Media Manager volume daemon on UNIX encountered a system call error while attempting to lock the barcode rule database This status code applies to UNIX servers only Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose
216. ackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action None NetBackup Status Code 114 Message EC_error Explanation None Recommended Action None NetBackup Status Code 115 Message EC_end Explanation None Recommended Action None NetBackup 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 For detailed troubleshooting information create admin and bpdbm debug log directories and retry the operation Check the resulting debug logs 3 Contact customer support and send appropriate problem and debug log sections detailing the error NetBackup Status Code 121 Message no media is defined for the requested NB database backup Explanation NetBackup attempted to back up its internal catalogs and there were no media IDs defined in the catalog backup configuration Recommended Action Add the media IDs to the catalog backup configuration Verify that the media IDs are in the NetBackup volume pool NetBackup Status Code 122 Message specified device path does not exist 110 NetBackup Troubleshooting Guide Windows NT 200
217. ackup Status Code 42 Message network read failed Explanation An attempt to read data from a socket failed Recommended Action 1 Verify that both the client and the server are operational 2 Perform Resolving Network Communication Problems on page 21 3 Check the Problems report for clues g2 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 43 Message unexpected message received Explanation The client and server handshaking was not correct Recommended Action 1 Verify that the correct version of software is running on the client and the server 2 Enable detailed debug logging On the server create a bpbrm debug log directory On clients create a bpcd debug log directory created automatically on Macintosh clients Increase the amount of debug information included in the logs as explained in the debug log topics in Chapter 3 3 Retry the operation and examine the logs Note If you are using bpstart_notify scripts on Windows clients verify that messages are not being written to stdout or stderr NetBackup Status Code 44 Message network write failed Explanation An attempt to write data to a socket failed Recommended Action 1 Check the Problems report for information about the error 2 Verify that the client and servers are operatio
218. ackup 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 User directed archives of files is also supported you cannot archive raw partitions Once started these operations are all similar to the extent that the same daemons and programs execute on the server see Figure 7 Each type however is started differently Scheduled backup operations begin when the NetBackup request daemon bprd activates the scheduler bpsched This occurs at intervals determined by the Wakeup Interval global attribute Once activated the scheduler checks the policy configurations for scheduled client backups that are due Immediate manual backups begin if the administrator chooses the manual backup option in the NetBackup administrator interface This causes bprd to start bpsched which then processes the policy client and schedule selected by the administrator User directed backups or archives begin when a user on a client starts a backup or archive through user interface on the client or the bpbackup or bparchive commands This invokes the client s bpbbackup or bparchive program which sends a request to the request daemon bprd on the master server When bprd
219. ackup bin admincmd bpauthsyne vopie servers On UNIX usr openv netbackup bin admincmd bpauthsynec vopie servers e Add back the names removed in step c and retry the operation Media Manager Status Code 127 Message unable to generate a unique media id Explanation A request was made to add volumes in the volume configuration using robot inventory update or using a media ID seed A unique media ID was not generated because the use seed option was not specified or because the available media ID combinations were used up Recommended Action If using robot inventory update ensure that all media in the robotic library have readable barcode labels or request updates using a seed to automatically generated media IDs for non barcoded media If volumes are being added by specifying a seed use a seed that allows media ID character combinations beyond those already in use To identify the slot associated with media that may not have a readable barcode examine the command output Media Manager Status Code 128 Message group is not valid for this host Explanation A request was made to add or change a volume pool and the specified UNIX group ID could not be found on the system that originated the request Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase t
220. ad only access is desired leave the write protection enabled and make the necessary administrative requests in the requesting application such as suspending the media to ensure that the media is requested only for read access If the media was requested through the command line interface see the tpreq man page or command description for specifying the access mode of the media The tpreq command is described in the NetBackup Media Manager System Administrator s Guide Chapter 5 Media Manager Status Codes and Messages 3370 a NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Robotic Status Codes These status codes are logged by robotic daemons processes They are also issued by programs that call the robotic operations such as the vmchange command and the media and device management user interfaces Robotic Status Code 200 Message STATUS_SUCCESS Explanation A robotic operation was successfully completed Recommended Action None Robotic Status Code 201 Message Unable to open robotic path Explanation The robotic library device could not be opened The specific case could be one of the following The robot device path or library name in the device configuration may not be valid The configured robotic device may not exist The robotic device may be incorrect such as a UNIX device file that is not of a character special file format Th
221. adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 It is not possible to change the volume pool for assigned volumes If no worthwhile data is on the volume unassign the media using the appropriate application interface which is bpexpdate for NetBackup and then retry the change pool request For optical media if no worthwhile data is on either side of the platter unassign both of the volumes before the change pool request is retried Media Manager Status Code 92 Message cannot delete assigned volume Explanation A delete request was made to a volume and the volume is currently assigned Optical volumes cannot be deleted unless both sides of the optical platter are unassigned Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 I
222. administrator can perform this operation server independent restore Restoring files by using a NetBackup server other than the one that was used to write the backup This feature is available only with NetBackup DataCenter 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 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 service A program on a Windows server system that runs in the background and performs some task for example starting other programs when they are needed Services are generally referred to as daemons on UNIX systems 512 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows session An instance of NetBackup checking its schedules for backups that are due adding them to its worklist and attempting to complete all jobs in the worklist For user backups and archives a session usually consists of a single backup or archive Session Vault A vault session consists of executing a particular profile or profiles shared drives See Shared Storage Option SSO Shared Storage Option SSO A separately
223. aemon bpcd to establish a connection between the NetBackup tar program on the client and bptm or bpdm on the server The bptm for tape or optical or bpdm for disk process obtains the location of the data media ID or file path and then starts retrieving data During retrieval the original bptm or bpdm process stores the image block by block in shared memory A second bptm or bpdm process transmits the image to the client Ifthe storage is tape or optical bptm includes the media ID ina tpreq command to the Media Manager device daemon 1t id The device daemon finds the physical media and causes it to be mounted on an appropriate device The bptm program reads the image and directs it to the client where the NetBackup tar program writes it on the client disk Ifthe storage unit is disk bpdm uses the file path in a read request to the system disk manager The image is then read from disk and transmitted to the client where the NetBackup tar program writes it on the client disk Only the part of the image that is required to satisfy the restore request is sent to the client not necessarily the entire backup image Appendix A Functional Overview 433 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Figure 11 Restore operation From Tape or Optical Server Master Server Master or Media Media Server
224. aemon service is running If the daemon service is not running start it On Windows vmd is the NetBackup Volume Manager service 2 If vmdis already running examine command output debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 3 Verify that the correct host names are defined in the configuration Each robot definition contains a volume database host where volumes are configured for use in the robot Each group of servers shares a common global device database host which vmd manages 4 Check the services file On UNIX verify that the etc services file and NIS services if NIS is used has entries for the vmd service Note that oprd is always started by the vmd service On Windows verify that the ssystemroot system32 drivers etc services file has the correct entry for vmd Also verify that the vmd port number in the services file agrees with the port number configuration which is noted in the man page for vmd 1M 5 Verify that all operating system patches or service packs are installed 6 Ensure that the Media Manager configuration is not tuned so that the load on vmd exceeds its ability to ser
225. ager system error occurred 174 Explanation It may be that bephyinv was not run on the media ID being imported Recommended Action Check whether the media ID being imported has a non default ADAMM GUID in the Media Manager volume database Run bephyinv on the media ID and rerun bpimport Backup Exec File Browse To determine the cause of Backup Exec file browse problems examine the bpdbm bpca and bptm logs To browse Backup Exec files using the Backup Archive and Restore interface 1 Open the Restore menu and choose Select Restore Type 2 Set the restore type to Backup Exec Backups or Normal and Backup Exec Backups For more assistance refer to the NetBackup user guide appropriate for your platform To list Backup Exec files using the bplist command ensure that the flops parameter has been specified correctly to list only Backup Exec files or both Backup Exec and NetBackup files Appendix D Backup Exec Tape Reader for NetBackup 477 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup Exec File Restore To list only Backup Exec files flops 524288 should be specified To list both Backup Exec and NetBackup files flops 1048576 should be specified Refer to the NetBackup DataCenter System Administrator s Guide for usage of the bplist command Ensure that the Backup Exec services are running on the Media Servers that contain the Backup Exec catalogs w
226. al Test and Troubleshooting Procedures This verifies Communications between the client and master server NetBackup software on the client If an error occurs check the following All Log Entries report Debug logs created in the previous step A likely cause for errors is a communications problem between the server and the client 11 When the test policy operates satisfactorily repeat specific steps as necessary to verify other clients and storage units 12 When all clients and storage units are functional test the remaining policies and schedules that use storage units on the master server If a scheduled backup fails check the All Log Entries report for errors then follow the actions suggested in the status codes chapters Testing Media Server and Clients If you are using media servers verify their operation as explained in the following steps Before proceeding eliminate all problems on the master server by completing To Test Master Server and Clients on page 16 1 Enable appropriate debug logs on the servers see the Using the Logs and Reports chapter If you are uncertain which logs apply enable them all until you solve the problem Delete the debug log directories when you have resolved the problem 2 Configure a test policy 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 p
227. al 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 5 If you previously configured a nonrobotic drive and your system includes a robot change your test policy 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 If you have difficulties with the robot try the test utilities described in the Robotic Test Utilities appendix Chapter 2 Troubleshooting Procedures 7 o NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Note Do not use the Robotic Test Utilities when backups or restores are active These utilities prevent the corresponding robotic processes from performing robotic actions such as loading and unloading media This can cause media mount timeouts and prevent other robotic operations like robotic inventory and inject eject from working 6 Add a user schedule to your test policy the backup window must be open while you are testing Use a storage unit and media that has been verified
228. al platters Device Management Status Code 58 Message The device is not robotic cannot perform cleaning Explanation An attempt was made to automatically clean a drive but the drive is not ina robotic library Recommended Action Clean standalone drives by inserting a cleaning tape when needed For non shared drives update the cleaning statistics with tpclean or another user interface that supports cleaning related operations Device Management Status Code 59 Message No cleaning tape is defined in the device s robot or 0 cleanings remaining Explanation An attempt was made to automatically clean a drive but no usable cleaning media is available or the number of cleanings remaining for the cleaning tape is zero Chapter 5 Media Manager Status Codes and Messages 333 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action 1 Ensure that cleaning media has been added to the robotic library for each drive type capable of being cleaned with a separate cleaning cartridge 2 Ensure there is a positive number of cleanings available for the cleaning media in the appropriate volume database for the robotic library Replace the cleaning tape or increase the number of cleanings for the cleaning media before the count reaches zero 3 Check the availability of vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on
229. 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 The backup restore manager starts the appropriate media manager process bptm for tape or optical and bpdm for disk and also starts the actual backup or archive by using the client daemon bpcd to start the backup and archive program bpbkar on the client The bpbkar program Sends information about files within the image to the backup restore manager which directs the file information to the NetBackup file database Transmits the backup image to the media manager process bptm or bpdm The bptm or bpdm process forks a second process which receives the image and stores it block by block in shared memory The original process then takes the image from shared memory and directs it to the storage media Ifthe storage is tape or optical bptm checks the NetBackup media database for a suitable media ID for example the correct density and retention level If it can t find one it obtains a new media ID from the Media Manager volume daemon vmd The bptm program includes the media ID in a tape request to the Media Manager device daemon 1t id which finds the physical media and c
230. an one Vault session at a time A Consolidated Report can be performed for one or more logical vaults at one time Consolidated reports are organized by report title not by vault cpio A UNIX command that can be used for copying files to or from a cpio archive on disk or tape ctime The time that a UNIX inode was changed cumulative incremental backup A backup that is scheduled by the administrator on the master server and backs up files that have changed since the last successful full backup All files are backed up if no prior backup has been done Also see differential incremental backup 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 server systems database agent clients Clients with additional NetBackup software that is designed to back up relational databases database extension clients See database agent clients Glossary 497 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows debug logs Logs that can be optionally enabled for specific NetBackup and Media Manager programs and processes and then used to investigate problems destination storage unit A storage unit to which Vault sends the data from a duplication operation If the duplicated backup images are to be vaulted then the de
231. anager service is running Then create a debug log directory for bpdbm retry the operation and check the resulting debug log Ifyou can view the report and have not found an entry related to this problem create debug log directories for the related processes that were running when the error first appeared this process will frequently be bpbrm Then retry the operation and check the resulting debug logs 2 Verify that the server list specifies the correct master server On Windows systems the master server is designated as CURRENT on the Servers tab in the Specify NetBackup Machines dialog To display this dialog box start the Backup Archive and Restore interface and click Specify NetBackup Machines on the Actions menu On 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 If you change the server list on a master server stop and restart the NetBackup Database Manager and NetBackup Request Manager services Chapter 4 NetBackup Status Codes and Messages 7 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 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 b
232. anged some not would cause a conflict with robot numbers Choose a different volume group on the request or let the volume group be automatically selected Volume group selection depends on the specific interface being used Media Manager Status Code 56 Message invalid database version header Explanation vmd could not find a recognizable volume database version in the volume database and cannot initialize with the database currently in place vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows Recommended Action 1 Examine the daemon debug log for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 From catalog backups or another source if available restore an earlier version of the database file usr openv volmgr database volDB UNIX or install_path Volmgr database volDB Windows and restart vmd Media Manager Status Code 57 Message error auto generating volume group Explanation A request was made to add or change volumes in the volume configuration using automatic generation of the volume group name A unique volume group name could not be generated because the available combinations were use
233. aring any devices or remove volumes with duplicate media IDs and consolidate volumes into one volume configuration Always use barcodes that are unique with respect to the six 6 least significant characters across all media in all robots or use media ID generation rules to ensure unique media IDs are generated when using robot inventory update Media Manager Status Code 116 Message volume has exceeded maximum mounts Explanation A request was made to assign a volume and the volume s number of mounts has exceeded the maximum number of mounts allowed for the volume or the maximum number allowed for the volume partner in the case of optical media Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 259 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 Increase the volume s maximum number of mounts or set the maximum number of mounts to infinite if you want to extend the active life of the physical media Alternatively
234. arted on that machine This will ensure proper communication between the NetBackup master and the Linux RedHat SuSE client 1 Could you install the software on the master and media servers by using the release media Some reasons for failure could be ww 10 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Configuration Problems Not logged in as an Administrator you must have permission to install services on the system Permission denied ensure you have permission to use the device and to write the directories and files being installed Bad media contact customer support Defective drive replace the drive or refer to vendor s hardware documentation Improperly configured drive refer to system and vendor documentation 2 Could you install NetBackup client software on the clients 3 For general network communications problems go to Resolving Network Communication Problems on page 21 To Resolve Common Configuration Problems If this is an initial installation or if you have changed the configuration check for these problems before proceeding 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
235. at the device is available and that media is available in the NetBackup media pool 2 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs Robotic Status Code 220 Message Media access port does not contain media Chapter 5 Media Manager Status Codes and Messages 347 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A robotic inject media operation returned a status indicating that the media access port does not contain any cartridges media The operator or administrator may not have placed media into the media access port for inject Recommended Action 1 Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting lt id the device daemon on UNIX or NetBackup Device Manager service on Windows Retry the operation and examine the logs 2 Coordinate inject eject operations between all operators and administrators Robotic Status Code 221 Message Media access port already contains media E
236. ation Robotic Status Code 214 Message Robot number does not exist Explanation A targeted robotic library was not found in the active device configuration Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Ensure that 1tid the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows was stopped and restarted after changes were last made to the device configuration When issuing commands to robotic libraries specify only robotic libraries that are actively part of the device configuration Robotic Status Code 215 Message Requested tape in other or non configured drive Explanation The targeted media was found in a drive differing from the targeted drive It is normal for requested media to be temporarily unavailable Also media can remain unavailable until administrator or operator action is taken Recommended Action Chapter 5 Media Manager Status Codes and Messages 345 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Ifthe media is needed imme
237. atus Code 26 Message database open operation failed Explanation A database file could not be opened Recommended Action Check for the existence and permissions of the volDB file in the usr openv volmgr database directory UNIX or install_path Volmgr database folder Windows Also check for the existence and permissions of the following files in the usr openv share directory UNIX or install_path NetBackup share folder Windows external robotics txt external densities txt external drivetypes txt external mediatypes txt external attributes txt Media Manager Status Code 27 Message database read record operation failed Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows encountered a read error while reading a volume database record Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine the daemon debug log for a more detailed message on the system error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 The volum
238. aunch properties file 53 license key 76 license problems 13 15 links in file list 60 Linux 10 listing Backup Exec and NetBackup files 478 Imfs description 460 Log level Macintosh clients 48 Windows and NetWare clients 48 Logs overview 41 debug enabling detailed 53 event viewer logging option 49 Mac client activity bpcd 48 inetd 48 NT Event Viewer Application 44 PC client activity bp 46 bparchive 46 bpbackup 47 bpbkar 47 bpcd 47 bpinetd 46 bplist 47 bpmount 47 bprestore 47 bpsrv 47 nbwin 47 tar 47 user_ops 47 reports NetBackup 43 server activity admin 45 bpbrm 45 bpcd 45 bpdbjobs 45 bpdbm 45 bpdm 45 bprd 45 bpsched 45 bptm 45 user progress 44 logs activity See debug debug introduction 44 Logs directory UNIX client server 440 Itid description 460 mapping files external 401 404 Master server test procedure 16 19 maximum pathname length 56 Media Contents report 43 Media database 450 Media List report 43 Media Log Entries report 43 Media Manager functional description 450 Media server test procedure 19 Media Summary report 43 Media Written report 43 message finding message text from status code 55 Messages NetBackup 173 364 mirror VxVM snapshot 61 mirror frozen image removing 64 misc file 458 mover conf file 123 Multiplexed backups 424 multiplexing 71 NBNW95 428 437 NBNW95 EXE 448 NBNWNT 428 437 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Tro
239. auses it to be mounted on an appropriate device bptm also controls the spanning of backups across multiple tapes if required Ifthe storage media is disk bpdm writes the images to the path configured in the disk storage unit The system disk manager controls the actual writing of data In the case of an archive NetBackup deletes the files from the client disk after the files have been successfully backed up For multiplexed backups the process is essentially the same except that a separate bpbrm and bptm process is created for each backup image being multiplexed onto the media NetBackup also allocates a separate set of shared memory blocks for each image Figure 8 shows an example of multiplexing images from two clients The other client and server processes are the same as on Figure 7 wr 424 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Figure 8 Multiplexed Backups Example two streams NetBackup Server UNIX Client bpbrm Only on master arent Seref bpdbm Pa File Informatio K O O Notes Client For detail on this component see Disk Media Manager Functional Tape or Optical Description later in this chapter D Appendix A Functional Overview 425 V NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4
240. authorized to use this application Explanation The user is not authorized to use one of the NetBackup Java Administration utilities on the host specified in the login dialog NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action Check the usr openv java auth conf file on the host specified in the NetBackup Java login dialog for the proper authorization If the auth conf file does not exist it must be created with the proper entry for this user name Refer to the NetBackup System Administrator s Guide for UNIX for more details on the auth conf file NetBackup Status Code 502 Message No authorization entry exists in the auth conf file for user name username None of the NB Java applications are available to you Explanation The user name is not authorized to use any NetBackup Java applications on the host specified in the login dialog 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 for UNIX for more details on the auth conf file NetBackup Status Code 503 Message Invalid username Explanation For login to a UNIX host the user name is
241. ava interface programs use it for temporary files and for job and progress log files generated by the user backup archive and restore program j bpSA This directory must exist for successful operation of any of the Java programs and must have public read write and execute permissions user_ops will contain a directory for every user that is using the Java programs The following is a list of facts to be familiar with before using debug logs NetBackup retains debug logs for the number of days you specify with the Duration to Retain Logs global attribute 28 days by default and then deletes them For instructions on changing Duration to Retain Logs see the NetBackup System Administrator s Guide for Windows Debug 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 Each debug log is kept in a separate subdirectory under install_path Net Backup Logs Debug logging takes place only if you create the subdirectory where the process can store its logs Chapter 3 Using the Logs and Reports 45 PE NetBackup 4 5 Troubleshooting Guide for Windows Debug Logs NetBackup 4 5 Troubleshooting Guide for Windows A process creates one debug log file per day On Windows the file names created are of the form mmadyy log For example 040198 log A debug log file is created when the process begins Therefore you
242. ay capabilities Started By usr openv volmgr bin vmadm command Stopped By Quit option from within the utility Debug Log usr openv volmgr debug reqlib Appendix A Functional Overview 465 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description wr 466 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Networks and Hostnames B In a configuration with multiple networks and clients with more than one hostname the NetBackup administrator must configure the policy entries carefully at all times considering the network configuration physical hostnames and aliases 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 policy The operating system s network code resolves this name and sends the connection across the network path defined by the system s routing tables For restores from the client the client connects to the master server On a Windows system the master server is specified on the Servers tab of the Specify NetBackup Machines dialog box to open this dialog start the NetBackup client user interface and click Specify NetBackup Machines on the Actions menu The
243. backup logs vault Windows install _path NetBackup logs vault Also review the detail 1og in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id This error often indicates that the media were left in the offsite vault volume group but still physically reside in the robot or in the robotic MAP To solve this problem do one of the following Manually remove any media that are in the offsite vault volume group but are still in the robot NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Inventory the robot This puts any media that were in the offsite vault volume group back into the robotic volume group Then rerun the vault sessions that failed NetBackup Status Code 301 Message vmchange api_eject command failed Explanation During the eject process the vmchange command is called with an api_eject call to begin the process of ejecting media This command call failed Recommended Action For detailed information about why the process failed review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install_path NetBackup logs vault Also review the detail 1log in each of the sidxxx directories that
244. base lock operation failed Media Manager Status Code 106 pool database open operation failed Media Manager Status Code 108 pool database truncate operation failed Media Manager Status Code 110 pool does not exist in pool database Media Manager Status Code 109 Chapter 5 Media Manager Status Codes and Messages 385 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages pool not defined as a scratch pool Media Manager Status Code 172 poolname is not unique in pool database Media Manager Status Code 105 Process killed by parent Robotic Status Code 212 Process killed by signal Robotic Status Code 211 protocol error Media Manager Status Code 20 request completed Media Manager Status Code 1 Request has been queued Cancel to clear message Device Management Status Code 53 Request terminated because host not validated for volume pool Device Management Status Code 26 Request terminated because media id is expired Device Management Status Code 27 Request terminated because media id will exceed maximum mount count Device Management Status Code 30 Request terminated because media is unavailable in DOWN drive misplaced write protected or unmountable Device Management Status Code 35 386 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows Ne
245. base on host voldb dell_2 A portion of the bpcd debug log below shows the Backup Exec files being added to the restore selection list and the restore job being launched on host dell_2 1660 3324 lt 2 gt StartRestoreJob util mykill to selection list adding Backup Exec path 16 11 04 185 1660 3324 lt 2 gt StartRestoreJob adding Backup Exec file pkill cpp to selection list 16 11 04 185 1660 3324 lt 2 gt GetRedirectionDeviceAndPath NT Share Name f 7 486 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs 16 11 04 185 1660 3324 lt 2 gt SetRestoreJobProperties Device Name ADAJ f 16 11 04 185 1660 3324 lt 2 gt SetRestoreJobProperties Path temp be_restore 16 11 06 318 1660 3324 lt 2 gt SetBEDrivesToUnknown Obtained 2 drives 16 11 09 162 1660 3324 lt 2 gt write BE restore progress sending job status message to bprd JOB_START DELL 2 A portion of the bpcd debug log below shows that the Backup Exec job was successfully completed 16 12 17 889 1660 3324 lt 2 gt StartBERestoreJob Backup Exec Job Status 5 16 12 17 889 1660 3324 lt 2 gt write BE restore progress sending job status message to bprd JOB SUCCESS 16 12 19 311 1660 3324 lt 2 gt FreeBELibrary Successfully unloaded beutil dll A portion of the bprd debug log below shows bprd
246. ber of physical drives or equivalent resources available for satisfying the requests for drive resources Also the relationship between the number of logical drives and physical drives may change as hardware failures occur NetBackup scheduling drive allocation and drive assignment algorithms can only determine logical drive availability NetBackup attempts to fully utilize all configured and available logical drives If the number of logical drives being utilized exceeds the number of physical drives available a NetBackup job may be started when insufficient drive resources are available for the job Instead of queueing the job in the scheduler the job runs and does not encounter the resource issue until the time it makes an ACS tape mount request Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Install the Shared Storage Option SSO license for mount requests to requeue when physical drive resources are not available 2 Since there is a fixed limit for the number of drives that can be in use at any one time optionally configure backup windows so the different storage units tied to the same physical drives are active only at non overlapping times Also raise or set to infinite the media mount timeout to avoid job failures when the job cannot get a physical drive due to the drives all be
247. bleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs continued Program Description Daemon lmfd The Library Management Facility daemon works in conjunction with 1m cd to handle requests to robots controlled by a Fujitsu Library Management Facility LMF 1mf d provides the interface between the local 1t id and the robotic control 1mfcd in the same manner as explained later for t 18d This robot is only available on Solaris Started By Starting 1t id or independently by using the usr openv volmgr bin 1lmfd command Stopped By Stopping 1tid or independently by finding the PID process id and then using the kil1 command Debug Log All errors are logged in the system log Debug information is included if the daemon is started with the v option either by itself or through 1tid or by adding VERBOSE to the vm conf file ltid The device demon UNIX or NetBackup Device Manager service Windows controls the reservation and assignment of tapes and optical disks Started By usr openv volmgr bin 1tid command on UNIX or Stop Restart Device Management command in Media and Device Management window on Windows Stopped By usr openv volmgr bin stopltid command on UNIX or Stop Restart Device Manager Service command in the Media and Device Management window on Windows Debug Log All errors are logged in the system log Debug information is included if the
248. cates backups they are duplicated to media in the robotic volume group root The highest level directory in a hierarchical directory structure In MS DOS the root directory on a drive is designated by a backslash for example the root on drive C is C On UNIX the root directory is designated by a slash 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 Glossary 51 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 site Also a component of the Windows 2000 operating system that manages storage devices RVSN See recorded media ID schedules Controls when backups can occur in addition to other aspects of the backup such as the type of backup full incremental and how long NetBackup retains the image SCSI Small computer system interface This is a type of parallel interface that is frequently used for communicating with storage peripherals server directed restore Using the user interface on the master server to restore files to any client Only the
249. ces or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that the barcode where requested is not blank 3 Ensure that the specified barcodes contain valid characters only alphanumeric characters and the period plus sign and underscore _ A hyphen is also a valid character when not the first character in the media ID 4 Ensure that the number of characters in the barcode does not exceed the maximum allowed for the robot type 5 Ensure that the barcode tag in all barcode rules is a subset of a valid supported barcode format Media Manager Status Code 11 Message invalid description Explanation The volume description exceeds 25 ASCII characters in length or contains unprintable characters Recommended Action When adding or changing a volume record or barcode rule record ensure that the description field contains only printable characters and is not longer than 25 ASCII characters Media Manager Status Code 12 Message invalid robot type NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation A requested operation encountered a case where a specified robot type or a volume s robot type differed from the type of robot required to perform the operation in the current configuration Recommended Action 1 E
250. chapter describe the reports and logs shown on the figure See Appendix A for more information on the programs and daemons mentioned in this figure and elsewhere in this chapter NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 SERVER CLIENT Sages Error File Catalog Catalog Logs Debug NetBackup NetBackup Logs Administration Database Interface Manager Master Server Master or Media Server Media Catalog Server Debug Logs Server Programs Client Programs Notes These logs must be enabled System Logs System Messages Windows Event Log NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 re
251. cified robot number was not within the allowable range or the robot number did not correspond to a currently configured robot or the robotic database is corrupted Recommended Action 1 Specify a robot number in the range of 0 to 32767 2 Ensure that all device configuration changes or deletions are performed on devices that are currently part of the device configuration 3 Check the integrity of the robotic database file robot ic_def located in the directory usr openv volmgr database UNIX or the folder install_path Volmgr database Windows by displaying the contents of the device configuration Restore a saved copy of the robotic database from catalog backups or delete it and recreate any needed robotic configuration information Device Configuration Status Code 16 Message A SCSI inquiry sent to the device has failed Explanation On a request to add or update a SCSI robotic library or drive Media Manager failed to obtain the serial number and inquiry string for the device This information is obtained by Media Manager by sending a SCSI Inquiry command to the device Failure indicates that NetBackup was not able to communicate with the device by means of SCSI Recommended Action 1 Ensure that the device is physically connected 2 Ensure that the operating system is configured to recognize the device and that the operating system can see the device 3 Ensure that no other process is using the device and that the device
252. ck the device configuration to see if a robot of type TLM Tape Library Multimedia or ODL Optical Disk Library is configured matching the robot number passed on the tpformat r option Format Optical Status Code 11 Message tpformat Command interrupted Explanation The format optical disk command tpformat was interrupted because the optical mount request was canceled or not accomplished within the required time interval Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Resubmit the request and observe the Device Monitor for standalone optical mount requests servicing them as needed Look for pending requests indicating reasons for the optical mount not being completed Chapter 5 Media Manager Status Codes and Messages 311 or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Format Optical Status Code 12 Message tpformat Skip Explanation Because an optical disk format operation failed remaining optical format operations were skipped Recommended Action Look in the user
253. ckup Status Code 100 tar did not find all the files to be restored NetBackup Status Code 185 Chapter 4 NetBackup Status Codes and Messages 193 yr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages tar had an unexpected error NetBackup Status Code 184 tar received an invalid archive NetBackup Status Code 183 tar received an invalid argument NetBackup Status Code 181 tar received an invalid file name NetBackup Status Code 182 tar received no data NetBackup Status Code 186 tar was successful NetBackup Status Code 180 termination requested by administrator NetBackup Status Code 150 text exceeded allowed length NetBackup Status Code 225 the archive failed to back up the requested files NetBackup Status Code 7 the backup failed to back up the requested files NetBackup Status Code 6 the client is not in the configuration NetBackup Status Code 243 war S194 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages the client type is incorrect in the configuration database NetBackup Status Code 72 the database contains conflicting or erroneous entries NetBackup Status Code 238 the entity already exists NetBackup Status Code 226 the file list is incomplete NetBackup Status C
254. ckup program bpbackupdb For a manual database backup NetBackup invokes bpbackupdb directly without going through bprd or the scheduler Once started bpbackupdb 1 Queries bpdbm for the database paths to back up and the media ID to use for the backup 2 Starts the tape and optical manager bptm and sends it the media ID in a special mount request The tape and optical manager bptm recognizes the request as being for a database backup and checks the database to ensure that the media ID is not one used for regular backups The bptm program then includes the media ID in a request to the Media Manager device daemon 1t id The device daemon finds the media and causes it to be mounted on an appropriate device 430 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Figure 9 NetBackup Database Backup NetBackup Administration Interface After backup sessions Master Server Master or Media Server a D KA De idt Hide Notes Disk with For details on this component see O O Database the Media Manager Functional I Description later in this chapter Tape or Optical 3 Starts the actual backup by using bpcd to start the backup program bpbkar If the database is on the master
255. clients create a bpcd debug log On the NetBackup server set the Verbose level to 1 on the TroubleShooting tab in the NetBackup Client Properties dialog To display this dialog start the Backup Archive and Restore interface and click NetBackup Client Properties on the File menu also see Using the Host Properties Window on page 40 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 25 nll Chapter 2 Troubleshooting Procedures 2 oe NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures 3 Verify basic network connectivity between client and server by pinging from the server to the client and from the client to the server Use the following command ping hostname Where hostname is the name of the host as configured in NetBackup policy configuration WINS DNS if applicable hosts file in the system directory sSystemRoot system32 drivers etc hosts Windows NT 2000 C Windows hosts default on Windows 98 and 95 If ping succeeds in all instances it verifies basic connectivity between the server and client If ping fails you have a network problem outside of NetBackup that must be resolved before proceeding As a first step verify the workstation is turned on as this is acommon source
256. close operation failed Media Manager Status Code 124 rule database lock operation failed Media Manager Status Code 123 rule database open operation failed Media Manager Status Code 125 rule database truncate operation failed Media Manager Status Code 98 rule does not exist in rule database Media Manager Status Code 97 specified robot is unknown to vmd Media Manager Status Code 79 STATUS_SUCCESS Robotic Status Code 200 Success Device Configuration Status Code 0 Chapter 5 Media Manager Status Codes and Messages 391 e NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Success Format Optical Status Code 0 System error occurred during robot operation Robotic Status Code 230 System error occurred Robot Error Status Code 11 system error Media Manager Status Code 2 Tape file path exceeds 255 character maximum Device Management Status Code 49 Tape needs to be write enabled Device Management Status Code 46 The device is not robotic cannot perform cleaning Device Management Status Code 58 The device name is not valid no device responded Device Configuration Status Code 52 The drive is DOWN Device Management Status Code 15 The drive is not ready or inoperable Device Management Status Code 21 The eject command was aborted by the user Robotic Status Code 244 gt
257. cluded by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id Appendix A Functional Overview 461 F NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs continued Program Description Daemon tl8cd The Tape Library 8MM Control daemon provides the robotic control for a TL8 robot and communicates with the robotics through a SCSI interface t18cd receives mount and unmount requests from t 18d on the host to which the drive is attached and then communicates these requests to the robot Started By Starting 1t id or on UNIX independently by using the usr openv volmgr bin t18cd command Stopped By Stopping 1tid or by using the t18cd t command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1tid tldd The Tape Library DLT daemon works in conjunction with t1dcd to handle requests to TLD robots t 1dd provides the interface between the local 1t id and the robotic control t 1dcd in the same manner as explained previously for t18d Started B
258. cluded in the system log as notifications tl4d The Tape Library 4MM daemon is the interface between 1tid and the Tape Library 4MM and communicates with the robotics through a SCSI interface Started By Starting 1tid or on UNIX independently by using the usr openv volmgr bin t14d command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id tl8d The Tape Library 8MM daemon drives in the same TL8 robot may be attached to different hosts than the robotic control tl8d is the interface between the local 1tid and the robotic control If a host has a device path for a drive in a TL8 robot then mount or unmount requests for that drive go first to the local 1t id and then to the local t18d all on the same host t18d then forwards the request to t18cd on the host that is controlling the robot could be on another host Started By Starting 1tid or on UNIX independently by using the usr openv volmgr bin t18d command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the kil1 command Debug Log All errors are logged in the system log Debug information is in
259. configured NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Configuration Problems Recommended Action To use this robot a previously configured robot must be disabled deleted from the device configuration Message Drive is in an unlicensed robot Explanation The drive is in a robotic library that cannot be licensed for the NetBackup BusinesServer Since the robot cannot be licensed for NetBackup BusinesServer any drives configured in that robot are unusable Recommended Action Configure a drive that does not reside in the unlicensed robot Message Drive s scsi adapter does not support pass thru or pass thru path does not exist Explanation A drive was found that does not have a SCSI pass through path configured There are two possible causes for this message The drive is connected to an adapter that does not support SCSI pass through The pass through path for this drive has not been defined Recommended Action Change the drive s adapter or define a pass through path for the drive See the Media Manager Device Configuration Guide for UNIX for scsi adapter pass through information Message No configuration device file exists Explanation A device has been detected without the corresponding device file necessary to configure that device Recommended Action Refer t
260. create debug log directories for the processes that could have returned this status code Then retry the operation and check the resulting debug logs On Windows verify that the recommended service packs are installed NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 23 Message socket read failed Explanation A read operation from a socket failed Recommended Action 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 debug log directories for the processes that could have returned this status code Then retry the operation and check the resulting debug logs 2 Corrupt binaries are one possible cause for this error For example in one instance the following was seen in the bpsched debug log get_num_avail_ drives readline failed socket read failed 23 get_stunits get_num_avail drives failed with stat 23 Loading a fresh bptm from the install media resolved the problem 3 On Windows verify that the recommended service packs are installed 4 This error may occur during a restore to a Novell client Note the following possible actions By default the value for Novell Maximum Concurrent Disk Cache Writes may be too low for example 50 Novell recommends setting it
261. cted information Recommended Action Create a debug log directory for bpdbm Then retry the operation save the debug log and call customer support NetBackup Status Code 233 Message premature eof encountered Explanation This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication Recommended Action During a restore this means that tar on the client received a stream of data that was not what it expected If the communication failure is not due to an interrupt on a client system save all error information and call customer support NetBackup 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 NetBackup Status Code 235 Message inadequate buffer space Explanation This code usually indicates a mismatch between server and client software versions Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Verify that all NetBackup software is at the same version level Update earlier versions of NetBackup software
262. curs 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 debug log directories and retry the operation Check the resulting debug logs NetBackup Status Code 153 Message server is not the master server Explanation This status code is reserved for future use Recommended Action None NetBackup Status Code 154 Message storage unit characteristics mismatched to request Explanation A backup was attempted and the storage unit selected for use had characteristics that were not compatible with the backup type Recommended Action Verify that the characteristics of the storage unit involved are appropriate for the backup attempted For NetBackup ServerFree Agent only The policy storage unit was set to Any_available and the offhost backup method was set to Third Party Copy Device or NetBackup Media Server Do not choose Any_available A particular storage unit such as nut 4mm robot t14 0 must be specified when Third Party Copy Device or NetBackup Media Server is specified as the offhost backup method Foran NDMP policy type verify that a storage unit of type NDMP is defined and the NDMP host value matches the host name of the client For example if the NDMP policy specifies toaster as the client the configuration for the storage unit must specify toaster as the NDM
263. d Action Specify the correct SCSI bus number for the robot Perform device discovery using the Device Configuration wizard or check the Windows registry as needed to obtain the SCSI bus number Device Configuration Status Code 9 Message Invalid SCSI target for the robot Explanation A request was made to add or change the SCSI target for a robot but the SCSI target provided was not valid Recommended Action Specify the correct SCSI target for the robot Perform device discovery using the Device Configuration wizard or check the Windows registry as needed to obtain the SCSI target Device Configuration Status Code 10 Message Invalid SCSI logical unit number for the robot Explanation A request was made to add or change the SCSI logical unit number for a robot but the SCSI logical unit number provided was not valid Recommended Action Specify the correct SCSI logical unit number for the robot Perform device discovery using the Device Configuration wizard or check the Windows registry as needed to obtain the SCSI logical unit number NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Configuration Status Code 11 Message Invalid Usage Explanation One of the Media Manager device configuration commands tpconfig or tpautoconf was executed with improper options or there is an incompatibility be
264. d command protocol Explanation An ill formed request was made to the NetBackup Request Manager service This can be due to mismatched versions of the product corrupted network communication or to a non NetBackup process sending data across the port for the service Recommended Action Examine the NetBackup error logs to determine the system that was the source of the data and on that system determine the process that initiated the request If it was a NetBackup process verify that the process or command is compatible with the version of software on the server Chapter 4 NetBackup Status Codes and Messages 15 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 144 Message invalid command usage Explanation This status code is due to a NetBackup process being started with improper options or an incompatibility in the product Recommended Action Either correct the command or verify that all NetBackup binaries are at the same version level NetBackup 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 NetBackup Status Code 146 Message cannot get a bound socket Explanation The service could not bind to its socket A system call failed when the service attempted to bind to its co
265. d s verbose option if available b Retry the operation and examine the logs 2 Specify an offsite session ID within the range of 0 to 2 147 483 647 Media Manager Status Code 149 Message current version does not support this configuration Explanation A request cannot be performed because it attempted to reference functionality that is not licensed An example of this is attempting to add a volume with a media type that is not valid for the licensed product Recommended Action Chapter 5 Media Manager Status Codes and Messages 273 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 List the license keys installed and verify that the functionality being referenced is supported with the currently installed license keys Check to see that the databases defining externalized object types are in place and not corrupted These database files are the following in the usr openv share directory UNIX or install_path Net Backup share folder Windows
266. d server The client has been configured to require encrypted backups but the encryption attribute for the backup policy on the server has not been selected The evaluation license for the NetBackup Encryption product has expired on the server but the NetBackup client has been configured to require encrypted backups As a result the server attempted to make a non encrypted backup of the client since the client is configured to require encryption the backup failed Recommended Action Ifthe server is a valid server but is not listed on the client add its name to the client s server list On Windows clients add the server on the Servers tab in the Specify NetBackup Machines dialog box To display this dialog box start the Backup Archive and Restore interface on the client and click Specify NetBackup Machines on the Actions menu On Macintosh clients add a SERVER entry in the bp conf file On NetWare target and OS 2 clients add a SERVER entry in the bp ini file If you continue to have problems review Resolving Network Communication Problems on page 21 and Verifying Host Names and Services Entries on page 25 To make non encrypted backups of the client set CRYPT_OPTION on the client to allowed or denied For more information refer to the NetBackup Encryption System Administrator s Guide 34 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows
267. d this status code Then retry the operation and check the resulting debug logs A possible cause could be a high network load For example this has been seen in conjunction with Cannot write to STDOUT when a Windows system that is monitoring network load has detected a high load and sent an ICMP packet to other systems that says the route being used by those systems was disconnected The log messages were similar to the following 01 31 96 14 05 23 ruble crabtree null com from client crabtree null com ERR Cannot write to STDOUT Err no 242 No route to host 01 31 96 14 05 48 ruble crabtree null com successfully wrote backup id crabtree null com_0823125016 copy 1 fragment 1 440864 Kbytes at 628 538 Kbytes sec 01 31 96 14 05 51 netbackup crabtree null com CLIENT crabtree null com POLICY Remote3SysFullW SCHED Sirius EXIT STATUS 24 socket write failed 3 4 On Windows verify that the recommended service packs are installed This error may occur during a restore to a Novell client Note the following possible actions By default the value for Novell Maximum Packet Receive Buffers may be too low such as 100 The restore performance may be improved by changing this value to 2000 To change it issue SET Maximum Packet Receive Buffers lt value gt at the console or enter the value in either of the following Novell files sys system startup ncf or sys system autoexec ncf Change to or add the
268. d to the failure Media Manager Status Code 60 Message cannot perform operation on this host Explanation A requested operation is not functional on a particular host Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Device discovery must be invoked only on specific platforms where it is supported Robot inventory update with optical media formatting specified must be invoked only on the host where the robotic control and optical drives are configured Media Manager Status Code 61 Message robot number and robot host mismatch Explanation A request was made to add or change volumes in the volume configuration or to issue a robot inventory update request A robot host was specified that differed from the robot host for other volumes in the same robot defined as those volumes having the same robot number All volumes in the volume database that have a given robot number for instance 0 must have the same robot host name Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Gu
269. d up Recommended Action Consolidate volumes into volume groups within the targeted robot number so that a new volume group can be automatically generated or provide a specific volume group name NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Media Manager Status Code 58 Message daemon cannot obtain socket Explanation vmd could not bind to its socket vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows A system call failed when vmd attempted to bind to its configured port number This is usually caused by another process having acquired the port before the vmd daemon or service started Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 If another process has the port use other system commands to determine the process Based on the result either change the port number in your services file or map or terminate the process that has acquired the port 3 UNIX only Another possible cause for this error is terminati
270. d verify that all Media Manager binaries on that host are at a compatible version level with other hosts that are part of the configuration Update the software version as needed Media Manager Status Code 138 Message media generation rule already exists Explanation You or a NetBackup media management interface have attempted to add a MEDIA_ID_BARCODE_CHARS rule that already exists The same rule cannot be added twice Recommended Action Re examine the listing of the MEDIA_ID_BARCODE_CHARS rules For a description of MEDIA_ID_BARCODE_CHARS rules refer to Media Manager Reference Topics in the NetBackup Media Manager System Administrator s Guide Media Manager Status Code 139 Message media generation rule does not exist Explanation You or a NetBackup media management interface have attempted to delete a MEDIA_ID_BARCODE_CHARS rule that does not exist Recommended Action Re examine a listing of the MEDIA_ID_BARCODE_CHARS rules For a description of MEDIA_ID_BARCODE_CHARS rules refer to Media Manager Reference Topics in the NetBackup Media Manager System Administrator s Guide Media Manager Status Code 140 Message invalid media generation rule Explanation You or a NetBackup media management interface have attempted to add an incorrect MEDIA_ID_BARCODE_CHARS rule Recommended Action Ensure that the MEDIA_ID_BARCODE_CHARS rule is composed correctly For a description of MEDIA_ID_BARCODE_CHARS rules refer to
271. daemon debug log and command or interface output for a more detailed message on the system error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Examine the permissions and check for the existence of the local device database files Display the device configuration to determine whether or not the database is corrupt and restore a saved copy of the databases from catalog backups or delete them and recreate the device configuration as needed Device Configuration Status Code 44 Message Cannot discover devices See the Troubleshooting Guide for details Explanation Any of the following device discovery was attempted on a platform where it is not supported according to the currently installed software there was an internal consistency problem with the global device database or device discovery could not obtain or verify its lock file Recommended Action 1 Check www veritas com and product release documentation for supported platforms for device discovery Upgrade the installed software to the latest available patch level if documentation indicates that device discovery is supported on the targeted host platform 2 Examine the daemon debug l
272. daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather output from the ipcs a command to see what resources are currently in use Investigate whether 1t id is tied up in communications with devices or other components Device Management Status Code 5 Message Error in Sending Daemon Message 314 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation An attempt was made by 1tid the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows to send an internal process communications message to a robotic daemon process using an already existing internal message queue An error was encountered in the message communications The error probably indicates a lack of system resources for message queues Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather output from the ipcs a command to see wha
273. ded Action None Device Configuration Status Code 1 Message Cannot execute command permission denied Explanation The process was started by a user or process that did not have root privileges on UNIX or administrator privileges on Windows or the global device database host name could not be set Recommended Action 1 If desired give the user or process administrator privileges on Windows or root privileges on UNIX and reissue the device configuration request 2 If the volume daemon UNIX or NetBackup Volume Manager service Windows is not running start it and retry the operation that tried to set the global device database host name such as during an install 3 Establish a common global device database host name as follows Runtpautoconf get_gdbhost on other hosts Set the global device database host name with tpautoconf set_gdbhost host name where host_name is the host name returned by tpautoconf get_gdbhost Device Configuration Status Code 2 Message The external_robot_mappings file has invalid license info Explanation The problem concerns one of the following files usr openv share external robot _mappings txt UNIX Chapter 5 Media Manager Status Codes and Messages 285 Sr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows install_path VERITAS NetBackup share external robot _mappings txt Windows 1 The fi
274. diately examine command output if available debug logs and system logs for messages relating to the targeted media a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Check for conflicts between multiple applications using media in the robotic library Check integrity of the drive and drive paths so that media is not routinely left in other drives Robotic Status Code 216 Message Door is open on cabinet Explanation The robotic library door was open Recommended Action Close the door of the robotic library and reissue the robotic request Check to see if the door latch mechanism is working by comparing what happens with robot test utility commands when the door is opened versus when it is closed Robotic Status Code 217 Message Requested slot already has cartridge Explanation The requested slot was already held or was associated with a cartridge Recommended Action Ensure that the inject eject request does not target a slot that already contains media Check for media in drives to ensure that the media s home slot location is not being targeted for use with media to be injected Robotic Status Code 218 Message Cannot move from media access port to slot Explanation A robotic i
275. dicating that there is no volume with a particular ADAMM GUID in the targeted volume configuration The requesting software may query the volume configuration on other hosts for a volume with the specified ADAMM GUID or it may perform other media management related actions based on this status code Note Although a GUID can be changed or added by means of the vmchange and vmadd commands the GUID field is for internal use only Do not add or change a GUID Media Manager Status Code 171 Message a scratch pool is already defined Explanation A new scratch pool cannot be defined because another scratch pool already exists Recommended Action Use the scratch pool already defined or delete the current scratch pool and create a new scratch pool Media Manager Status Code 172 Message pool not defined as a scratch pool Explanation You or a NetBackup media management interface have tried to delete unset a scratch pool that is not defined as a scratch pool Recommended Action To delete the scratch pool by using the vmpool command make sure that the name of the pool specified with the unset_scratch option is the correct name of the scratch pool Media Manager Status Code 173 Message invalid scratch pool name Explanation You or a NetBackup media management interface have tried to specify the NetBackup DataStore or None pool as a scratch pool The NetBackup DataStore and None pools cannot be specified as scratch pools
276. does not appear in the Netbackup server list on that server On a Windows server the master is designated on the Servers tab in the Master Server Properties dialog To access this dialog see Using the Host Properties Window on page 40 Recommended Action 1 Verify that the master server appears as a server in its own server list as well as being listed on all media servers If you change the server list on a master server stop and restart the NetBackup Database Manager and NetBackup Request Manager services 2 If necessary create debug log directories for the following processes and retry the operation Then check the resulting debug logs on the master server Ifthe error occurred during a backup operation check the bpsched debug logs Ifthe error occurred during a restore operation check the bprd debug logs NetBackup Status Code 207 Message error obtaining date of last backup for client NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation An error occurred when the backup scheduler bpsched tried to obtain the date of the last backup for a particular client policy and schedule combination Recommended Action 1 Verify that the NetBackup Database Manager service is running 2 Examine the All Log Entries report for the appropriate time frame to gather more information about th
277. e 147 Message invalid offsite slot Explanation A request was made to change the offsite slot location for a volume and the value specified was not within the acceptable range NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Specify an offsite slot value within the range of 0 to 2 147 483 647 Media Manager Status Code 148 Message invalid offsite session id Explanation A request was made to change the offsite session ID for a volume and the value specified was not within the acceptable range Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the comman
278. e Notes are used to call attention to information that makes using the product easier or helps in avoiding problems Caution This is a Caution Cautions are used to warn about situations that could cause data loss Key Combinations Some keyboard command sequences use two or more keys at the same time For example holding down the Ctrl key while pressing another key Keyboard command sequences are indicated by connecting the keys with a plus sign 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 Vertical bar or pipe 1 Separates optional arguments from which the user can choose For example when a command has the following format command arg1 arg2 the user can use either the arg1 or arg2 variable Preface xi NetBackup 4 5 Troubleshooting Guide for Windows Getting Help NetBackup 4 5 Troubleshooting Guide for Windows Terms Getting The terms listed in the table below are used in the VERITAS NetBackup documentation to increase readability while maintaining technical accuracy Term Definition Microsoft Windows Terms used as nouns to describe a line of operating systems Windows developed by Microsoft Inc A term used as an adjective to describe a specific product or noun Some examples are Windows 95 Windows 98 Windows NT Windows 2000 Windows serv
279. e UNIX or the folder install_path Volmgr database Windows Display the device configuration to determine whether or not the database is corrupt Restore a saved copy of the databases from catalog backups or delete them and recreate the device configuration as needed Device Configuration Status Code 14 Message Invalid drive index Explanation A request was made to add update or list a drive configuration entry and the specified drive index was not associated with a configured drive Recommended Action 1 Display the device configuration to obtain the list of valid drives Avoid making device configuration changes from multiple sources simultaneously If more information is needed examine the daemon debug log and command or interface output for a more detailed message on the error NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the log files Device Configuration Status Code 15 Message Invalid robot number Explanation On a request to modify the device configuration the spe
280. e another daemon already exists Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows was initializing and found that it was already running according to the daemon service lock file Recommended Action Check to see if vmd is already running Do not try to start another vmd daemon service unless the running daemon service is first shut down Stop the running vmd with vmctrldbm t or on Windows by using the system Services interface If the daemon service was unexpectedly terminated remove the lock file which is usr openv volmgr misc vmd lock UNIX or install_path Volmgr misc vmd lock Windows and try restarting vmd Media Manager Status Code 90 Message invalid volume pool Explanation A request was made to add volumes change the volume pool for a volume add a barcode rule or change a barcode rule However the volume pool name or number associated with the requested change is in conflict with the requirements for volume pools These requirements are Volumes in scratch pools cannot be assigned until they are first moved to another pool Volume pool numbers cannot be negative Volume pool names must consist of from 1 to 20 printable ASCII characters with no embedded whitespace The None volume pool is the only valid pool for barcode rule entries that specify cleaning a media type Recommended Action 1 Examine command output if available debug logs and
281. e 94 cannot read backup header media may be corrupted NetBackup Status Code 173 cannot read media header may not be NetBackup media or is corrupted NetBackup Status Code 172 Can not write file NetBackup Status Code 508 child process killed by signal NetBackup Status Code 27 client backup failed to read the file list NetBackup Status Code 67 client backup failed to receive the CONTINUE BACKUP message NetBackup Status Code 66 client backup was not attempted NetBackup Status Code 195 client backup was not attempted because backup window closed NetBackup Status Code 196 client cannot read the mount table NetBackup Status Code 60 client connection refused NetBackup Status Code 57 Chapter 4 NetBackup Status Codes and Messages 177 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages client did not start NetBackup Status Code 49 client hostname could not be found NetBackup Status Code 48 client is not validated to perform the requested operation NetBackup Status Code 135 client is not validated to use the server NetBackup Status Code 131 client name mismatch NetBackup Status Code 39 client process aborted NetBackup Status Code 50 client timed out waiting for bpend_notify to complete NetBackup Status Code 75 client timed out waiting for bpstart_notify to complete NetBacku
282. e Management interface New Robot or Change Robot display to browse for robots in the system registry eliminating the need to manually specify device paths or device control parameters 2 Check the operating system registry for changer names and their associated SCSI paths when manually specifying robotic control information Check for detailed errors from the command or user interface output Ensure that the Removable Storage service is running Ensure that the device is present and working properly according to the Removable Storage administration interface Device Configuration Status Code 47 Message Cannot backup restore global device database files NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation There was a failed request to create a backup copy remove a backup copy or replace the current copy of the local device databases This database is globDB located in usr openv volmgr database UNIX or install_path Volmgr database Windows on your global device database host Recommended Action 1 Examine the daemon debug log and command or interface output for a more detailed message on the system error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and
283. e NetBackup Client Service which must be running for the database recovery to succeed 2 Check the NetBackup Problems report for additional information about the error Some possible causes are Adisk may be full The NetBackup catalog tape may be corrupt NetBackup Status Code 130 Message system error occurred 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 For detailed troubleshooting information create bpdbm bpsched bptm and bprd debug log directories on the master server and retry the operation Check the resulting debug logs NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 131 Message client is not validated to use the server Explanation The client name as determined from the connection to the server did not match any client name in the NetBackup configuration and there was no altnames configuration for this client on the master server A client and server that have multiple network connections can encounter this problem if the name by which the client is configured is not the one by which its routing tables direct connections to the server Recommended Action 1
284. e adjusted either delete one of the drives or make use of an unused drive address as a temporary state For example if a robot has two drives with robot drive numbers 1 and 2 that need to be swapped change one drive to use robot drive number 3 temporarily change the other drive to use robot drive number 1 or 2 as appropriate and finally change the first drive to the open robot drive address 1 or 2 Device Configuration Status Code 27 Message Invalid drive type for the robot Explanation On a request to configure a drive to be in a robot it was found that the drive type was not valid for the selected robot type NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action In the NetBackup Media Manager System Administrator s Guide appendices check the Robot Attributes tables to determine valid media types for a given robot type Drive types directly correspond to the listed media types Configure supported devices so that invalid combinations of drive types and robot types are not required Device Configuration Status Code 28 Message Invalid robot drive number for the robot type Explanation On a request to configure a drive to be in a robot it was found that the robot drive number was not valid for the selected robot type Recommended Action The robot drive number or for ACS robots the set of A
285. e by examining the error message in the bpsched debug log NetBackup Status Code 213 Message no storage units available for use Explanation The NetBackup scheduler process bpsched did not find any of its storage units available for use Either all storage units are unavailable or all storage units are configured for On demand only and the policy and schedule does not require a specific storage unit Recommended Action 1 Examine the Backup Status and All Log Entries report for the appropriate time period to determine the policy 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 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 4 Verify that the robot number and host name in the storage unit configuration matches the Media Manager device configuration 5 Determine if all storage units are set to On demand only for a policy and schedule combination that does not require a specific storage unit If this is the case either specify a storage unit for the policy and schedule combi
286. e database may be corrupted Restore an older volume database from a saved version or from catalog backups Media Manager Status Code 28 Message database read operation read too few bytes Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows encountered a record that was smaller than expected while reading a volume database record Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 The volume database may be corrupted Restore an older volume database from a saved version or from catalog backups Media Manager Status Code 29 Message database lock operation failed Explanation vmd the Media Manager volume daemon on UNIX encountered a system call error while attempting to lock the volume database This error code applies to UNIX servers only Recommended Action Chapter 5 Media Manager Status Codes and Messages 213 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine the daemon debug log for a more detailed
287. e failed due to a device or media problem Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the format error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 239 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 For any of the cases listed under Explanation choose a format operation appropriate for the current state of the platter and retry the format as needed using the tpformat command Media Manager Status Code 78 Message barcode does not exist in database Explanation A query volume by barcode request did not return a volume entry having the specified barcode or barcode and media type Recommended Action 1 Examine the daemon and reqlib debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose
288. e failure 3 For detailed troubleshooting information create debug log directories for bpsched and bpdbm on the master server and retry the operation Then check the resulting debug logs NetBackup Status Code 208 Message failed reading user directed file list Explanation An error occurred when the backup scheduler bpsched attempted to read the list of files requested for a user backup or archive This error indicates either a client server communication problem or a system problem on the master server where the NetBackup scheduler process bpsched is running Recommended Action For detailed troubleshooting information create debug log directories for bpsched and bprd on the master server and retry the operation Then check the resulting debug logs NetBackup Status Code 209 Message error creating or getting message queue Explanation An error occurred when the backup scheduler bpsched attempted to create an internal message queue construct for interprocess communication This error indicates a problem on the master server Recommended Action Create a bpsched debug 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 debug log NetBackup Status Code 210 Message error receiving information on message queue Explanation An error occurred when one of the backup scheduler bpsched processes attempted to receive a message fr
289. e for Windows Media Manager Functional Description Figure 14 Media and Device Management Example Process Storage NetBackup User Migrator Device management utility Device Monitor Database Media management utility Inventory barcodes or inject eject Request media ID Where is media ID Device Database EXB8500 QIC Non robotic drives al e ip w zuno 101 U09 9 oqoH JO4 U09 91 0q0H y y Optical Disk Tape Library Library TL8 454 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 If a robot supports barcodes Media Manager automatically compares a tape s barcode to what is in the volume database as an extra measure of verification before mounting the tape Media Requests Involving Barcodes A request for media that is in a robot that can read barcodes begins in the same manne
290. e given the media s usage history and correct it as needed using vmchange Device Management Status Code 31 Message Requested number of drives are not configured Explanation A tape mount request was submitted and there are not enough drives in the configuration that match the requested density Recommended Action Ensure that 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows was stopped and restarted after changes were last made to the device configuration Display the device configuration using tpconfig d or other means to see the list of configured drives Check the man page command description for tpreq to find the list of valid densities Resubmit the mount request using a valid density that corresponds to a drive in the device configuration Device Management Status Code 32 Message Error in getting semaphore Explanation An attempt was made by 1tid the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows to obtain a semaphore used for arbitrating access to shared memory and the request failed due to a system error The error probably indicates a lack of system resources for semaphores or mismatched software components NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action 1 Examine command ou
291. e inserting it into a drive or robot For labeled media the external media ID should be the same as the media ID recorded on the media EVSN See external media ID FlashBackup A special type of raw partition backup that requires the NetBackup FlashBackup separately priced option this option is available only for NetBackup DataCenter flush level Controls how often Netbackup clears its log files on a Novell NetWare or Microsoft Windows client platform fragment A part of a backup or archive image NetBackup can be configured to divide images into fragments when they exceed a certain size or span tapes frequency backup How often NetBackup performs scheduled backups For example if the frequency is seven days then backups occur once a week FROZEN media state If a volume is FROZEN NetBackup keeps it indefinitely and can restore from it but not use it for further backups or archives 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 ww 500 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows global attributes NetBackup configuration attributes that affect all policies GDM Dashboard The name for the Gl
292. e master and all media servers use the NetBackup Activity Monitor or the Services application in the Windows Control Panel to start the following services NetBackup Request Manager Service 414 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs NetBackup Database Manager Service NetBackup Device Manager Service NetBackup Volume Manager Service Recover Catalogs from Tape Media Manager Catalogs Intact When the Media Manager catalogs are intact you can recover the catalog backups by using a drive configured under Media Manager control as follows 1 Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel to stop the following services if they are running NetBackup Request Manager service NetBackup Database Manager service 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 If this occurs insert the tape and use the Device Monitor to assign the drive to the request 3 On the NetBackup server where the drive attaches execute the bprecover command Example 1 Assume you are restoring the catalogs to disk 1 on Figure 3 and the 8mm tape has media ID JBL29 To recover the NetBackup part of the catalogs from image 1 on the
293. e master server NetBackup Status Code 153 server name not found in the bp conf file NetBackup Status Code 254 server not allowed access NetBackup Status Code 46 SERVER was not specified in ust openv netbackup bp conf NetBackup Status Code 111 Session id assignment failed NetBackup Status Code 263 Session id file is empty or corrupt NetBackup Status Code 265 socket close failed NetBackup Status Code 22 Socket connection to the NB Java user service has been broken Please retry your last operation NetBackup Status Code 507 socket open failed NetBackup Status Code 21 wr 192 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages socket read failed NetBackup Status Code 23 socket write failed NetBackup Status Code 24 specified device path does not exist NetBackup Status Code 122 specified disk path is not a directory NetBackup Status Code 123 specified media or path does not contain a valid NB database backup header NetBackup Status Code 127 specified profile not found NetBackup Status Code 304 storage unit characteristics mismatched to request NetBackup Status Code 154 system call failed NetBackup Status Code 11 system error occurred NetBackup Status Code 130 system error occurred while processing user command NetBa
294. e name does not exceed 255 ASCII characters in length If the mount requests are coming from an application request an application change to use a shorter file name or if needed install the product in a directory folder that will not cause the file name limit to be exceeded Device Management Status Code 50 Message No action pending for given mount index Explanation On a request to obtain the pending action for a mount request there was no known pending action associated with the request Recommended Action Use a device monitor interface to display requests that have pending actions Perform requests like assign deny display or resubmit only on requests that have pending actions Chapter 5 Media Manager Status Codes and Messages 331 or NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Device Management Status Code 51 Message Frequency based cleaning is not supported for this drive Explanation A request was made to set the cleaning frequency for a drive and the configuration of the drive does not support frequency based cleaning Recommended Action See the Drive Cleaning section under the Media Manager Reference Topics appendix in the NetBackup Media Manager System Administrator s Guide Shared drives cannot be cleaned based on a frequency based schedule Cleaning for drives in ACS LMF RSM and TLH robots is managed by vendor or operating syste
295. e of the ADAMM GUID for another volume already in the volume database All volumes in a volume database must have an ADAMM GUID that is either unique or null ADAMM is Advanced Device and Media Management and a GUID is a Global Unique Identifier The GUID conflict may occur if the following are both true The bephyinv exe or beconv exe command is running on a Windows host in install_path NetBackup bin adminemd AND The GUID field of a record in the volume database is modified by either adding changing or deleting records Another possible cause may be one of the following The physical inventory utility bephyinv exe has already been run on this media Chapter 5 Media Manager Status Codes and Messages 281 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes This media had on disk Backup Exec catalogs and the catalog converter utility beconv exe has already been run on this media Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2
296. e recovery failed a process has encountered an exceptional condition NetBackup Status Code 128 NB image database contains no image fragments for requested backup id copy number NetBackup Status Code 165 NB Java application server interface error Java exception NetBackup Status Code 511 NB Java application server not accessible maximum number of connections exceeded NetBackup Status Code 500 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 NetBackup Status Code 514 NDMP backup failure NetBackup Status Code 99 network connection broken NetBackup Status Code 40 network connection timed out NetBackup Status Code 41 network read failed NetBackup Status Code 42 network write failed NetBackup Status Code 44 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages no active policies contain schedules of the requested type for this client NetBackup Status Code 198 no active policies in the configuration database are of the correct client type NetBackup Status Code 246 No authorization entry exists in the auth conf file for use
297. e robotic daemon process lock file could not be opened or a lock obtained The open operation on the device or through the API interface such as NDMP failed Recommended Action 1 Stop any robot test utilities that may be running since they have the lock on the robotic device when they are active 2 Check the configuration of the robot against the recommended configuration as indicated in the documentation for robot configuration 3 Check the health of the robotic device by using a robot test utility then close the test utility when finished 4 Check for the existence and permissions of the lock file itself and the lock file directory which is usr openv volmgr misc vmd lock UNIX or install_path Volmgr misc vmd lock Windows Create the directory folder and adjust the permissions as needed so that the robotic daemon process can use the lock file Stop and restart 1t id the device daemon on UNIX or the NetBackup Device Manager service on Windows NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Robotic Status Code 202 Message Unable to sense robotic device Explanation An element of the robotic library device could not be sensed The cause could be any of the following The SCSI commands mode sense mode select or read element status of slot drive transport i e element may have fail
298. e serial numbers are the same check with the drive vendor to see if it is possible to modify the serial number If the serial numbers are different delete the drive on one of the hosts and re run device discovery there Device Configuration Status Code 45 Message No device found in RSM at the specified location Explanation On a request to add or change robot information in the device configuration the specified robotic device path could not be found in the system registry This status code applies to Windows 2000 systems only Recommended Action Use the Media and Device Management interface New Robot or Change Robot display to browse for robots in the system registry eliminating the need to manually specify device paths or device control parameters Check the operating system registry for changer names and their associated SCSI paths when manually specifying robotic control information Check for detailed errors from the command or user interface output Device Configuration Status Code 46 Message Unable to retrieve GUID from RSM api Explanation On a request to add or change robot information in the device configuration an error was encountered while attempting to obtain the RSM GUID for the specified device path or device control parameters RSM is the Microsoft Removable Storage Manager and GUID is a Global Unique Identifier This error code applies to Windows 2000 systems only Recommended Action 1 Use the Media and Devic
299. ece ene eee 32 Example 3 NetWare and Macintosh Clients 0 000 0000005 34 Example 4 Clients in Multiple Networks 0666s cece eee eee 36 Example 5 Server Connects to Multiple Networks 000005 38 Using the Host Properties Window 000 ccc cee rnn 40 Chapter 3 Using the Logs and Reports 000 eee e eee eee eee eee 41 REPOS i cecaact peta dn pith dak pekia pace a Glee oa aa tu gid Me Seana bso a nce nad EERE 43 Status for User Operations 6 eee ees 44 Windows Event Viewer Application Logs 6 6 6 cece 44 Debug Logs ecis esrie davenee veces vieestiewstinwtedesreduettannreeecieeee ne 44 Debug Logs On Servers mierreercdp rispan pi e a a e a eeh 44 Debug Logs on PC Clients s ceo recii siere ren i eee eee eee eee 46 Debug Logs on Windows and Netware Clients 00 0000008 46 Debug Logs on Macintosh Clients 66 c cece eens 48 Media Manager LO gs lid ia ecsceitce dippen paei eigen tse e peda eE a Gaus Ee Gea 49 Windows Event Viewer Logging Option 0 6 6 49 To Enable the Logging Tool oserei reatie e e E e a eee 50 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows EVENTOS Pile ENIES cucire cd ale aides mcd aE E EE RE E E alae PERRO te 50 Example ds 3 cen iiiar na e e e ones A ees ao eee 51 Troubleshooting the Administration Console
300. ecommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Fora Macintosh or NetWare target client verify that the server is not trying to connect when a backup or restore is already in progress on the client These clients can handle only one NetBackup job at a time On a Macintosh you can check for activity by examining the NetBackupListen file in the following folder on the startup disk of the Macintosh client System Folder Preferences NetBackup logs inetd log mmddyy 2 Perform Resolving Network Communication Problems on page 21 NetBackup Status Code 56 Message client s network is unreachable Explanation An error was returned that the host was unreachable by the client WSAENETUNREACH when performing a system call Recommended Action Try to ping the client from the server Check the IP address for the client If you still have problems talk to your network administrator NetBackup Status Code 57 Message client connection refused Explanation The client refused a connection on the port number for bpcd This can occur because there is no process listening on the bpcd port or there are more connections to the bpcd port than the network subsystem can handle with the listen call Recommended Action 1 For Windows NetBackup servers a Make sure the NetBackup client sof
301. ect for another session id for which media has not been ejected NetBackup Status Code 308 Message no images duplicated Explanation This error occurs when vault failed to duplicate any images Recommended Action For more information review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install _path NetBackup logs vault Also review the detail 1log in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id Look for the log entry that gives the total number of images processed A common cause of failure is a lack of resources such as no more media available in the specified pools for duplication Correct the problem and rerun the vault job Note that the NetBackup scheduler will retry a vault job that has terminated with this error Review the admin debug log for bpduplicate entries and the bptm debug log Chapter 4 NetBackup Status Codes and Messages 165 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 309 Message report requested without eject being run Explanation This error occurs when a report is run that requires media to have been ejected first Recommended Action Perform one of these actions Rerun viteject or vlt
302. ect type for the client If such a policy does not exist create one NetBackup Status Code 246 Message no active policies in the configuration database are of the correct client type Explanation A user backup request was not satisfied because no active policies were the type required for the client Recommended Action Create or activate an appropriate policy so the user backup request can be satisfied NetBackup Status Code 247 Message the specified policy is not active Explanation Backups for the specified policy are disabled because the policy is inactive Recommended Action Activate the policy and retry the operation NetBackup Status Code 248 Message there are no active policies in the configuration database Explanation No active policy was found that would satisfy the request Recommended Action Activate the appropriate policy and retry the operation NetBackup Status Code 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 Chapter 4 NetBackup Status Codes and Messages 151 a NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Obtain additional information by first creating debug logs and then attempting to recreate the error The debug logs to create are as follows On the server bptm bpbr
303. ection refused by server backup restore manager Explanation The media host refused a connection on the port number for bpcd This error can be encountered during a backup or restore Recommended Action Execute the ping command from one host to another by using the following combinations Note Also see Resolving Network Communication Problems on page 21 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 by using the name specified in the NetBackup server list On a Windows server the master is designated on the Servers tab in the Master Server Properties dialog To access this dialog see Using the Host Properties Window on page 40 3 On Windows servers a Verify that the bpcd entries are correct in SystemRoot system32 drivers etc services NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes b Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Configuration dialog match the settings in the services file To display this dialog start the Backup Archive and Restore interface and click Configure on the Actions menu The values on the Network tab are written to the services file
304. ectory on the client NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Description Daemon 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 Debug 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 usve can be helpful jnbSA A Java based administration utility for managing NetBackup and Media Manager on UNIX In addition administration of supported UNIX systems can be performed by using the NetBackup Java Windows Display Console on a Windows system Started By On UNIX the usr openv netbackup bin jnbSA command Ona NetBackup Java Windows Display console the NetBackup Java on host menu item on the Programs NetBackup menu Stopped By Exit option in jnbSA Debug Log None although the logs for bpjava msvc and bpjava usve can be helpful ndmpmoveragent On the NetBackup media server UNIX this daemon acts as an NDMP server in a type of three way backup called Remote NDMP Started By Executing usr openv volmgr bin ndmpmoveragent start Stopped By Executing usr openv volmgr bin ndmpmoveragen
305. ed A network API controlled library inventory request may have failed The robotic daemon process could not initialize a robotic database file Recommended Action 1 Check the configuration of the robot against the recommended configuration as indicated in the documentation for robot configuration 2 Check the health of the robotic device by using a robot test utility then close the test utility when finished 3 Check for the existence and permissions of the temporary robotic database and the temporary database directory folder which is usr openv volmgr misc robotic db UNIX or install_path Volmgr misc robotic_db Windows Create the directory folder and adjust the permissions as needed so that the robotic daemon process can create it or use it Stop and restart 1t id the device daemon on UNIX or the NetBackup Device Manager service on Windows Robotic Status Code 203 Message Timeout waiting for robotic command Explanation A robotic operation timed out it did not return with a status before a designated time period had elapsed Recommended Action 1 Stop any robot test utilities that may be running since they have the lock on the robotic device when they are active and can block other requests 2 Check whether excessive hardware retries have delayed the completion of a robotic command yy Chapter 5 Media Manager Status Codes and Messages 339 or NetBackup 4 5 Troubleshooting Guide for Windows Ne
306. ed troubleshooting information create a bpcd debug log directory and retry the operation Check the resulting bpcd debug log NetBackup Status Code 103 Message error occurred during initialization check configuration file Explanation None Recommended Action None NetBackup Status Code 104 Message invalid file pathname Explanation None Recommended Action None NetBackup Status Code 105 Message file pathname exceeds the maximum length allowed Explanation The path name built by using the current working directory exceeds the maximum path length allowed by the system Recommended Action Shorten the current working directory path length NetBackup Status Code 106 Message invalid file pathname found cannot process request Explanation One of the file paths to be backed up or archived is not valid Recommended Action Verify that full path names are used 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 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 110 Message Cannot find the NetBackup configuration information Explanation On Windows NetBackup could not read the registry entries that were created during installation On UNIX the usr openv netbackup bp conf file do
307. ed actions Message Drive does not support serialization NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Configuration Problems Explanation The drive does not return its serial number Note that some manufacturers do not support serial numbers Although automatic device configuration will not function optimally the drive can be manually configured and operated without its serial number Recommended Action Ask the manufacturer for a newer firmware version that returns serial numbers if available or manually configure and operate the drive without a serial number 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 manually configured and operated without serial numbers Recommended Action Ask the manufacturer for a newer firmware version that returns serial numbers if available or manually configure and operate the robot and or drives without serial numbers Message Too many drives in robot Explanation The robotic library has more than two installed drives the maximum allowed with a NetBackup BusinesServer license
308. ed over a VERITAS Volume Manager VxVM volume In this case you may see the following in the usr openv netbackup logs bpbkar log 17 12 51 bpbkar main FTL frozen image processing failed status 11 60 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 17 12 51 bpbkar Exit ERR bpbkar FATAL exit status 11 system call failed 17 12 51 bpbkar Exit INF EXIT STATUS 11 system call failed and something like the following in the usr openv netbackup logs online_util log 17 12 51 onlfi_vfms_logf INF vxvm freeze Frozen image source cockpitl on device dev dsk c1t0d0s6 is not on a VxVM volume 17 12 51 delete _mount_point INF Deleted mount point tmp _cockpit1_coc_group1 3518 17 12 51 onlfi_ freeze FTL VfMS error 11 see following messages 17 12 51 onlfi_ freeze FTL Fatal method error 17 12 51 onlfi_freeze FTL vfim_freeze method vxvm type FIM function vxvm_freeze 17 12 51 onlfi_freeze FTL V MS method error 9 see following message 17 12 51 onlfi_freeze FTL vxvm_freeze Frozen image source cockpitl on device dev dsk c1lt0d0s6 is not on a VxVM volume 17 12 51 onlfi_thaw INF fim vxvm 17 12 51 onlfi_thaw WRN cockpitl is not frozen Make sure that the frozen image source is configured over a VERITAS Volume Manager VxVM volume vxvm was selected as the fr
309. ed to write to a file that does not have write permissions The solution is to enable write privileges The NetBackup Java user service has attempted to write to a temporary file whose unique name cannot be constructed This condition is unlikely but could result from an exhaustion of system resources from the filling of the name space Recommended Action The specific details may be retrieved from the user service log files Enable detailed debug logging as explained under Enabling Detailed Debug Logging in Chapter 3 NetBackup Status Code 509 Message Can not execute program Explanation The NetBackup Java authentication or user service has reported an error relating to the creation or demise of a child job process The NetBackup Java service programs create separate jobs to accomplish specific tasks as follows The NetBackup Java authentication service creates the NetBackup Java user service Upon Chapter 4 NetBackup Status Codes and Messages 169 v NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows successful creation of and connection to the NetBackup Java user service all other child processes are created by the NetBackup Java user service on behalf of requests made by the NetBackup Java interface Note The cause of status code 509 can be found in the appropriate log file either for bpjava msvc or bpjava usve The cause can be catego
310. edia and Device Management Process 6000 e cece ene eens 453 Barcode Operations 6 66 een eens 455 Media Requests Involving Barcodes 606 c cece eee eee 455 Media Manager Components 60060 c nee 457 Media Manager Directories and Files 0 06 c ccc eee eee 457 Programs and Daemons ereiten ec ee en A ee 458 Appendix B Networks and Hostnames 00 00 eee eee 467 Appendix C Robotic Test Utilities cece cece eens 471 Appendix D Backup Exec Tape Reader for NetBackup 55 473 OVETVIEW tiita ani ind ladtedccl ad ile leet ong E as e alse bane dee ead eee 473 beconv Error Messages occorrenti eeke nie Gianna oie O E E ab 473 bephyinv Error Messages sere ecrire ii a eee een nee eee 476 bpimport Error Messages seic cs 080 ci ctn cise cise cereacetsa ceed s ESAU rA 477 Backup Exec File Browse stesi dr ssor ccc eens 477 Backup Exec File Restore 2 2 0 000 eens 478 Redirected Restores 2200 6 66 eee ene eens 479 Restoring to Windows Clients 00 6 6 479 Restoring to UNIX Clients so eseese ener iaeei nepi eens 480 Restoring to Netware Clients 6 6 66 c cece ene 480 Troubleshooting with the Debug Logs 66 6 e cece cnc eens 481 Backup Exec File Browse Problems 600 c cece cee enn nee 481 TEX AIM LOS is eee wes alle SAAR ein EE E EE OE E EEE E a ae Getta aha 483 Backup Exec File Restore Problems nan nnnnnnnnnn narar rarna
311. edia type specifier Recommended Action 1 If running a robot inventory on a robot of type ACS LMF RSM TLH or TLM ensure that the vendor media type returned from the robot control software is supported and recognized by the version of Media Manager that is installed 2 If using a command line interface directly verify that a valid media type has been passed according to vmadd 1m command line documentation which applies to all Media Manager command line interfaces 3 Ensure that an operation valid only for cleaning media has not been requested on a media ID that does not correspond to cleaning tape 4 Ensure that the media type in all barcode rules is a valid media type or the ordinal zero 0 to represent the default media type Chapter 5 Media Manager Status Codes and Messages 205 Sr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Code 10 Message invalid barcode Explanation A process performing a media related operation encountered an unknown missing or incompatible barcode Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons servi
312. eeded 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 If resizing OTM cache does not fix the problem you may not have enough free disk space NetBackup Status Code 12 Message file open failed Explanation An open of a file failed Recommended Action For NetBackup ServerFree Agent only Status code 12 may appear in the usr openv netbackup logs bptm or bpdm log accompanied by the following tpc_read_config failed cannot open file usr openv volmgr database 3pc conf This may indicate that the policy is configured with either NetBackup Media Server or Third Party Copy Device as the offhost backup method but that the 3pc conf file does not exist or is in the wrong location When upgrading from NetBackup 4 0V to 4 5 you must recreate the 3pc conf file For instructions on creating the 3pc conf file refer to the latest version of the NetBackup ServerFree Agent System Administrator s Guide NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Check the NetBackup Problems report Try to determine the file and why the error occurred A possible cause is a permission problem with the file For detailed troubleshooting information create a debug log directory for the
313. em 3 Execute the command manually to see if the desired result is produced Chapter 4 NetBackup Status Codes and Messages 97 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 4 For detailed troubleshooting information set up debug logging a On UNIX and Windows clients create a debug log directory for bpbkar b On other PC clients except Macintosh create a debug 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 c Retry the operation and check the resulting debug log NetBackup 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 debug log shows the command that was executed Create a debug log directory for bpbkar Retry the operation and retry the resulting debug log 3 Try executing the vos command manually to duplicate the problem NetBackup Status Code 80 Message Media Manager device daemon 1t id is not active Explanation The NetBackup Device Manager service is not running Recommended Action 1 Use the Activity Monitor or the Services application in the Windows Control Panel to see if the NetBackup Device Manager service is running
314. emote Administration Console has a server list entry on the master server Add the media server to the list on the Servers tab in the Master Server Properties dialog see Using the Host Properties Window on page 40 If a server or Windows NetBackup Remote Administration Console has more than one host name for example if it has multiple network interfaces verify that the master server has a server list entry for each of them If you change the server list on a Windows master server stop and then restart the NetBackup Request Manager and NetBackup Database Manager services NetBackup Status Code NetBackup Status Code 39 Message client name mismatch Explanation The name that the client used in a request to the NetBackup server did not match the client name configured in the policy on the server Recommended Action Change either the NetBackup client name setting on the client see the applicable NetBackup users guide or the one in the policy configuration on the server so the two match NetBackup Status Code 40 Message network connection broken Explanation The connection between the client and the server was broken This status code can also appear if the connection is broken between the master and media server during a backup Recommended Action 1 Try pinging the client from the server If this is not possible check for loose connections or other network problems 2 Verify that the server list settings are cor
315. en The backup was terminated because the NetBackup DISALLOW_BACKUPS SPANNING_MEDIA option was present in the registry The backup will be retried automatically with a different volume if this is allowed by the backup tries attribute in the NetBackup global attribute configuration Recommended Action None NetBackup 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 debug log directory and retry the operation Check the resulting debug log NetBackup Status Code 168 Message cannot overwrite media data on it is protected Explanation A catalog backup was attempted to a volume that could not be overwritten because it contains data that NetBackup by default does not overwrite tar cpio ANSI and so on Recommended Action Replace the volume with a new one or set the NetBackup ALLOW _MEDIA_OVERWRITE option to the appropriate value NetBackup Status Code 169 Message media id is either expired or will exceed maximum mounts Explanation A backup or catalog backup was attempted and the volume selected for use has reached its maximum number of mounts as specified in
316. enerates reports to track the location and content of each piece of media vault In the context of the NetBackup Vault a vault is logical entity associated with a particular robot that acts as a designated holding place for backups that will eventually be sent to a physical offsite vault The term vault is used to refer both to the process and to the physical storage location of a set of tapes offsite vault process Vaulting is the process of choosing backup images to duplicate or eject optionally duplicating backups ejecting duplicate or original media storing it at an offsite location and later returning expired media to your robot Vaulting is an integral part of the disaster recovery process verbose flag Configuration file entry that causes a higher level of detail to be written in the logs Glossary 517 or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 vm conf A Media Manager configuration file with entries that include the servers that can manage local devices and default media ID prefixes for media that do not contain barcodes
317. eport gives you the status code If you find a status code or message in either the Backup Status or All Log Entries report go to the NetBackup Status Codes and Messages chapter or Media Manager Status Codes and Messages chapter and perform the recommended corrective actions If the problem pertains to device or media management and either NetBackup does not provide a status code or you cannot correct the problem by following the instructions in status codes chapters check the Event Viewer Application log for NetBackup entries Check appropriate debug logs that are enabled and correct problems you detect If these logs are not enabled enable them before your next attempt For more information see the Using the Logs and Reports chapter If you performed corrective actions as a result of step a through step c retry the operation If you did not perform corrective actions or the problem persists go to the next section General Test and Troubleshooting Procedures To Resolve Device Configuration Problems Certain auto configuration warning messages are displayed in the second panel of the Device Configuration wizard if the selected device meets any of the following conditions Not licensed for NetBackup BusinesServer Exceeds a license restriction Has inherent qualities that make it difficult to auto configure These are the messages relating to device configuration along with explanations and recommend
318. er DAS This daemon communicates with the TLM robotics through a network API interface Started By Starting 1t id or independently by using the usr openv volmgr bin t1lmd command Stopped By Stopping 1tid or independently by finding the PID process id and then using the kil1 command Debug Log All errors are logged in the system log Debug information is included if the daemon is started with the v option either by itself or through 1tid The v option is available only on UNIX Also add the VERBOSE option to the vm conf file Appendix A Functional Overview 463 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs continued Program Description Daemon tpconfig tpconfig isacommand line interface or interactive 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 tpconfig is only a command line interface that runs to completion no quit option Debug Log None tsdd The Tape Stacker DLT daemon is the interface between 1t id and the DLT tape stacker and communicates with the robotics through a SCSI interface Started By Starting 1t id or on UNIX independently by using the usr openv volmgr bin t
319. er the file is install_path NetBackup db altnames meteor Then the administrator adds the following line to this file pluto The master server now recognizes as legitimate restore requests that show a peername of meteor and client name of pluto Refer to the NetBackup System Administrator s Guide for Windows for more information on altnames configuration Regardless of the type of router the configuration for the media server saturn is still the same as in example 2 If a media server is involved in a backup or restore for pluto the master server provides the correct peername and client name for the media server to use in establishing connections Chapter 2 Troubleshooting Procedures 37 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures 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 policy 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
320. er 4 NetBackup Status Codes and Messages 68 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Ifa frozen image backup failed using one of the Extended Frozen Image Services methods TimeFinder ShadowImage BusinessCopy there may be a VxVM clone left over from a previous backup You may see messages similar to the following in the usr openv netbackup logs online_util log 19 13 07 686 14981 lt 2 gt onlfi_vfms_logf INF do_cmd Command failed with status 20 usr openv netbackup bin bpdgclone g wil_test n vol01 f var tmp HDSTFCAAs7a0qD lt dev null gt var tmp V MSAAAg7aOgD 2 gt var tmp V MSBAAr7a0gD 19 13 07 687 14981 lt 2 gt onlfi_vfms_logf INF Dumping file var tmp VE MSAAAq7aOgD stdout 19 13 07 687 14981 lt 2 gt onlfi_vfms_logf INF End of file var tmp V MSAAAq7aOgD 19 13 07 687 14981 lt 2 gt onlfi_vfms_logf INF Dumping file var tmp Vf MSBAAr7aOgD stderr 19 13 07 687 14981 lt 2 gt onlfi_vfms_logf INF clone group and volume already exists 19 13 07 688 14981 lt 2 gt onlfi_vfms_logf INF End of file var tmp V MSBAAr7aOgD NetBackup automatically creates VxVM clones for Extended Frozen Image Services backups of data configured over volumes After the backup has completed NetBackup removes the VxVM clone In this case a system crash or reboot may have prevented the removal Remove
321. er interface output Device Configuration Status Code 20 Message Duplicate device path names Explanation The same device path name was used for the optical drive character and volume header names Recommended Action Refer to the appropriate chapter in the NetBackup Device Configuration Guide to determine which optical drive names should be specified Device Configuration Status Code 21 Message Robot number is already in use Explanation On a request to add a robot to the device configuration the robot number was found to be already in use for a different robot Recommended Action Check the device configuration on all device hosts for configured robots and specify a robot number that is not already in use Use tpautoconf get_gdbhost to obtain the global device database host and use the following vmglob h global_device_database_host listall to display all devices sharing a common global device database Device Configuration Status Code 22 Message Device path is already in use Explanation On a request to add or change robot information in the device configuration the specified robotic device path is already in use for another configured robot Recommended Action Chapter 5 Media Manager Status Codes and Messages 293 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 To avoid configuring device paths that are already in use use the
322. er is too large too many paths specified Explanation Too many paths were specified in the NetBackup catalog backup configuration to fit in a fixed size media header This error should not occur under normal circumstances Recommended Action Delete some of the paths from the catalog backup configuration Chapter 4 NetBackup Status Codes and Messages 11 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 127 Message specified media or path does not have a valid NB database backup header Explanation The bprecover command was issued and the media ID specified does not have valid catalog backup data Recommended Action Validate that the correct media ID is being used NetBackup Status Code 128 Message NB database recovery failed a process has encountered an exceptional condition Explanation One or more catalogs specified for recovery could not be restored For more detail refer to the error message issued just above this status code in the output from the bprecover command Recommended Action 1 After fixing the problem reported in the error message in the bprecover output refer to Recovering the NetBackup Catalogs on page 409 to identify which NetBackup services Windows or daemons UNIX should be shut down prior to attempting the NetBackup database recovery The NetBackup services should be shut down except for th
323. er that caused a new volume to be added Since RSM media names are equivalent to media IDs if the existing media ID is not deleted from the volume configuration the conflict appears when the new volume is added Do not change media names in RSM if volume entries have already been established for the media in the volume configuration Media Manager Status Code 160 Message the global device database device type is invalid Explanation An invalid device type appeared in a request to modify the device configuration NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Identify the targeted host and verify that all Media Manager binaries on that host are at a compatible version level with other hosts that are part of the configuration Update the software version as needed Media Manager Status Code 161 Message the global device database device serial number is invalid
324. erface under the File menu NetBackup Client Properties General tab Keep status of user directed backups archives and restores for For NetWare clients logs are kept the number of days specified in file openv netback bp ini under Keep Log Days The currently active logs have names of the form Chapter 3 Using the Logs and Reports 47 o NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Debug Logs mmadyy log For example 120198 10g You can increase the amount of information that processes write in the logs On Windows clients set the debug level on the TroubleShooting tab of the NetBackup Client Properties 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 Debug Logs on Macintosh Clients There are two types of debug logs on Macintosh clients bpcd logs which are located in the Preferences NetBackup Logs bpcd folder These logs have information on Net BackupBPCD which controls communications between the server and the client inetd logs which are located in the Preferences NetBackup Logs bpcd folder These logs have
325. ermining viteject 154 vitoffsitemedia 154 vltopmenu 154 155 vitrun 153 154 vm conf file 458 vmadm overview 465 vmd overview 465 Volume database 458 vxassist command 61 vxvm frozen image method 61 vxvol command 61 Windows Display Console 54 xbp overview 449 xinetd 10 Index NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows wr 528 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows
326. ernate target restore See redirected restore different target alternate path restore See redirected restore different path alternate read server A server used to read a backup image which was originally written by a different media server The media server specified as Alternate Read Server must have access to the media containing the backup image or images it is configured to read archive A special kind of backup where NetBackup backs up the selected files and if the backup is successful deletes the files from the local disk In this manual references to backups also apply to the backup portion of archive operations except where otherwise noted archive bit A file status bit that the Microsoft based operating system sets when it writes a file thereby indicating that the file has changed attributes for a policy Configuration parameters that control the behavior of NetBackup during operations involving this policy autochanger See robotic library autoloader See robotic library automatic backup A scheduled backup by the master server wr 494 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows back up The act of copying and saving files and folders to storage media backup Refers to the process of copying and saving files and directories to storage media For example
327. error where exclusive access to the disk could not be set b Operating system error while attempting to format the disk c Cannot determine the name of the disk d Operating system was unable to set the geometry e Could not write the volume table of contents f Cannot determine SCSI passthrough path to the device g Cannot read capacity of the optical platter h Cannot seek to write the volume header i Optical volume format is not supported on the targeted platform Format Optical Status Code 3 Message tpformat Cannot open Explanation The format optical disk command tpformat encountered a system device or media error while trying to open the optical disk device Recommended Action Chapter 5 Media Manager Status Codes and Messages 3077 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify integrity of the device and the media and check the system device files for correctness according to the NetBackup Device Configuration Guide
328. ers Windows clients Windows platforms Windows hosts and Windows GUI Where a specific Windows product is identified then only that particular product is valid with regards to the instance in which it is being used For more information on the Windows operating systems that NetBackup supports refer to the VERITAS support web site at http www support veritas com Windows servers A term that defines the Windows server platforms that NetBackup supports those platforms are Windows NT and Windows 2000 Windows clients A term that defines the Windows client platforms that NetBackup supports those platforms are Windows 95 98 ME NT 2000 XP for 32 and 64 bit versions and LE Help For updated information about this product including system requirements supported platforms supported peripherals and a list of current patches available from Technical Support visit our web site http www support veritas com VERITAS Customer Support has an extensive technical support structure that enables you to contact technical support teams that are trained to answer questions to specific products You can contact Customer Support by sending an e mail to support veritas com or by finding a product specific phone number from the VERITAS support web site The following steps describe how to locate the proper phone number NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows Net
329. ervice or start vmd with the verbose option b Retry the operation and examine the logs Media Manager Status Code 108 Message pool database open operation failed Explanation A requested operation was unable to open the volume pool database file Recommended Action Check for the existence and permissions of the poo1DB file in the following on UNIX usr openv volmgr database directory on Windows install_path Volmgr database folder Restore the poo1DB file from the catalog backups or from another location change the access permissions on the existing poo1DB or move rename the current pool1DB so that vmd can initialize a default pool configuration If the move rename method is used modify the volume and other application configurations so that no references are made to volume pools that no longer exist Media Manager Status Code 109 Message pool does not exist in pool database Explanation A requested operation encountered a case where the specified volume pool was not found in the volume pool configuration on the targeted volume database host The requests potentially returning this error code are add change delete query volume pool add change barcode rule add change volume query scratch volumes and robot inventory report or update Recommended Action Chapter 5 Media Manager Status Codes and Messages 2557 TN NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows S
330. es not exist Recommended Action On Windows reinstall NetBackup software on the client On UNIX create a usr openv netbackup bp conf file with at least the following lines SERVER server_name CLIENT NAME client_name NetBackup Status Code 111 Message No entry was found in the server list Explanation On UNIX the SERVER server_name line is missing in the bp conf file On Windows the server list contains no entries Recommended Action Ona UNIX client add the following line to the top of the usr openv netbackup bp conf file SERVER server_name Ona Microsoft Windows or nontarget NetWare client add the server name on the Servers tab in the Specify NetBackup Machines dialog box To display this dialog start the Backup Archive and Restore interface on the client and click Specify NetBackup Machines on the Actions menu Onan OS 2 or NetWare target client add the server name to the bp ini file Ona Macintosh client add the SERVER server_name line to the bp conf file in the NetBackup folder in the Preferences folder NetBackup Status Code 112 Message no files specified in the file list Explanation A restore was requested with no files in the file list Recommended Action Specify at least one file to be restored NetBackup Status Code 113 Message EC_badop Explanation None Chapter 4 NetBackup Status Codes and Messages 109 or NetBackup 4 5 Troubleshooting Guide for Windows NetB
331. es exist as the type of special file required NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Management Status Code 55 Message Operator denied mount request Explanation The operator denied a mount request Recommended Action This happens when a user or application mount request has been canceled by an administrator or operator The request may have been canceled for a number of reasons such as missing or faulty media or the need to allow other higher priority requests to obtain drive resources Check with the administrator or operator for more information Device Management Status Code 56 Message Mount canceled device daemon is terminating Explanation Pending mount requests were canceled because the administrator terminated 1tid the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Recommended Action Wait for ltid to be restarted before resubmitting the request Check with the administrator as needed to determine daemon service availability Device Management Status Code 57 Message Cannot assign due to media ID mismatch Explanation An attempt was made to assign an optical disk request to a volume that contained a different recorded media ID than was requested Recommended Action Refer to the tpformat man page to change recorded media IDs on optic
332. escription 442 bpbkar and fsclone 63 bpbkar log 47 BPBKAR32 427 442 bpblr description 442 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows bpbrm description 442 bpbrm log 45 BPCD 428 436 437 bpcd description 443 Mac client log 48 server log 45 UNIX client log 47 BPCD NLM 443 BPCDW32 426 435 BPCDW32 EXE 443 bpclntcmd utility 28 bpdbjobs description 443 bpdbjobs log 45 bpdbm description 444 bpdbm log 45 bpdm description 444 bpdm log 45 bperror command 55 bphdb description 444 bpimport 477 BPINETD 427 436 bpinetd log 46 bpjava msve 444 445 bpjava msve log 53 bpjava usvc log 53 bplist 477 description 445 bplist log 47 bpmount log 47 bprd description 445 bprd log 45 bprecover 112 401 404 405 409 410 411 412 413 415 416 bprestore description 445 bprestore log 47 bpsched description 446 bpsched log 45 bpsrv log 47 BPSRV EXE 446 BPSYS EXE 446 bptm description 446 bptm log 45 Catalog recovery identify media 410 procedure 411 class database file 450 Client Backups report 43 Client NetBackup activity logs Mac clients 48 configured name 467 debug logs Windows and NetWare clients 46 installation problems 11 multiple hostnames 467 NT disk recovery 406 peername 467 software location UNIX clients 440 testing configuration 16 19 CLIENT_CONNECT_TIMEOUT 58 73 CLIENT_READ_TIMEOUT 58 73 clone fsclone removing 63 c
333. eshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Figure 6 Starting NetBackup Master Server Execute Execute in ltid usr openv netbackup bin initbprd usr openv volmgr bin 1ti y Starts applicable robotic daemons See the Media Manager Functional Description later in this appendix m bpdbm Initiates further actions when a scheduled or user directed operation is required Media Server Execute The Media Manager device components of NetBackup must be usr openv volmgr bin 1tid started as shown to the right y Starts applicable The master server starts other i robotic daemons See NetBackup programs as necessary to Itid the Media Manager use storage units that attach to the Functional Description media server later in this appendix Client T oe On UNIX clients bpcd must be in a listening state On Windows and NetWare clients bpcd must be running Except for bpcd required programs are started as necessary during the backup or restore Macintosh and Windows NT 2000 clients must only be turned on and ready Appendix A Functional Overview 421 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Backup and Archive Processes The b
334. ess install During the install be certain to Partition the disk as it was before the failure if partitioning is necessary Then reformat each partition as it was before the failure Install the operating system in the same partition that was used before the failure Specify the default workgroup Do not restore to the domain Follow any hardware manufacturers instructions that apply such as loading SSD on a Compaq system 2 Reboot the system when the install is complete 3 Configure the NetBackup client system to re establish network connectivity to the NetBackup master server For example if your network uses DNS the configuration on the client must use the same IP address as before the failure and must specify the same name server or another name server that recognizes both the NetBackup client and master server On the client configure DNS in the Network dialog box that you access from the Control Panel 4 Install NetBackup client software Refer to the NetBackup Installation Guide for PC Clients for instructions Ensure that you specify the correct names for the client and master server To specify the client name start the user interface on the client and click Configure on the Actions menu Enter the client name on the General tab of the NetBackup Configuration dialog To specify the server name click Specify NetBackup Machines on the Actions menu and make the entry on the Servers tab 5 Install any NetBack
335. essage queues On Windows this error can also occur if an internal system registered event cannot be opened Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather output from the ipcs a command to see what resources are currently in use Device Management Status Code 9 Message Drive is currently reserved Explanation An attempt was made to reserve a shared drive but the drive is already reserved This status code is related to the internal implementation of the SSO feature not SCSI Reserve Release Recommended Action This is an unexpected condition that will be automatically retried If problems persist stop and restart 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Device Management Status Code 10 Message IPC sequence error Explanation An internal process communications message sequencing error has occurred
336. est Media Manager Status Code 55 Message robot number and volume group mismatch Explanation A request was made to add or change volumes in the volume configuration and the robot number and volume group associated with the volume configuration changes are in conflict with the requirements for volume groups All volumes in a volume group are required to have the same residence which includes having the same robot number Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 227 w NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 Ensure that the specified robot number and volume group are compatible If volumes in the volume group have a given robot number for example 0 then volumes with a different robot number for example 1 cannot be added to that volume group Volumes cannot be moved directly from one robotic volume group to another robotic volume group since the intermediate steps some volume entries ch
337. etBackup administrator interface Debug Log bprd 1og on the server bplist On UNIX clients this program communicates with bprd on the master server when a user browses the database during a restore operation Started By Starting a search of the image database by using the client user interface or executing the usr openv netbackup bin bplist command on the client Stopped By Completion of operation Debug Log bplist 1log on the client bprestore On UNIX clients this program communicates with bprd on the master server when a user starts a restore Started By Starting restore by using the client user interface or by executing the usr openv netbackup bin bprestore command on the client Stopped By Completion of operation Debug Log bprestore 1og on the client Appendix A Functional Overview 45 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Daemon Description bpsched bptm BPSRV EXE BPSYS EXE On master servers the Scheduler uses policy information from the NetBackup configuration databases to determine Clients to start and when to start them Storage units to use for backups and archives Started By bprd for the following operations User directed backups and archives Immediate manual backups started through t
338. etBackup experienced the timeout NetBackup Status Code 6 Message the backup failed to back up the requested files Explanation Errors caused the user backup to fail Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Verify that you have read access to the files Check the status on the client for messages on why the backup failed Correct problems and retry the backup 2 On Windows clients verify that the account used to start the NetBackup Client service has read access to the files 3 On Macintosh clients this code can be due to multiple backups being attempted simultaneously on the same client Some possible solutions are Adjust the backup schedules Ifthe client is only in one policy set the policy attribute Limit jobs per policy to 1 Set the NetBackup global attribute Maximum jobs per client to 1 note that this limits all clients in all policies NetBackup 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 status on the client for messages on why the archive failed Correct problems and retry the archive On Windows clients verify that the account used to start the NetBackup services has read access to the fi
339. etailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify the integrity of the device and media and check the system device files for correctness according to the NetBackup Device Configuration Guide Format Optical Status Code 6 Message tpformat Cannot write Explanation The format optical disk command tpformat encountered a system device or media error while trying to write the optical disk Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify the integrity of the device and media and check the system device files for correctness according to the NetBackup Device Configuration Guide Use the tpformat f option if the media has not already been sector formatted Format Optical Status Code 7 Message tpformat Existing media ID Explanation The format optical disk command tpf
340. examine the logs 2 When assigning volumes manually specify the volume pool associated with the volume Check the device configuration to determine if the volume database host for the device is consistent with the volume configuration in the volume database Applications may attempt to query multiple volume databases for volume related requests so ensure that duplicate media IDs are not used in volume configurations across multiple hosts If duplicate IDs are found either completely separate the configurations by not sharing any devices or remove volumes with duplicate media IDs and consolidate volumes into one volume configuration Always use barcodes that are unique with respect to the six 6 least significant characters across all media in all robots or use media ID generation rules to ensure unique media IDs are generated when using robot inventory update Media Manager Status Code 95 Message media ID is not the specified media type Explanation A request was made to assign or add a volume of a specified media type but the volume or other physically similar volumes have a different media type Recommended Action 248 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug
341. example in DOS resources are drives directories and files Also see target service 510 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows restore verb The act of restoring selected files and directories from a previous backup or archive and returning them to their original directory locations or to a different directory noun The process of restoring selected files and directories from a previous backup and returning them to their original directory locations or to a different directory retention level An index number that corresponds to a user defined retention period There are 10 levels from which to choose 0 though 9 and the retention period associated with each is configurable Also see retention period retention period The length of time that NetBackup keeps backup and archive images The retention period is specified on the schedule robotic arm The component of a robotic library that physically selects the media tape or optical disk robotic library Refers to a robot and its accompanying software A robotic library includes a collection of tapes or optical platters used for data storage and retrieval For example a Tape Library DLT TLD refers to a robot that has TLD robotic control robotic volume group A volume group from which media will be ejected and vaulted When Vault dupli
342. explain the problem check the NetBackup Problems report 5 For detailed troubleshooting information create a bptm debug log directory on the server and retry the operation Check the resulting debug log file 6 Contact customer support and send appropriate problem and debug log sections NetBackup Status Code 92 Message media manager detected image that was not in tar format Chapter 4 NetBackup Status Codes and Messages 108 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation When performing a restore the tape manager bptm or disk manager bpdm could not find a tar header at the offset it expected Recommended Action 1 Performa bpverify of the affected image to determine if it is written correctly 2 Check the NetBackup Problems report for additional information about the error 3 Verify the Media Manager and system configuration for the drive 4 Error code 92 has been encountered on some relabeled and value added 8 mm tape drives where the drive s microcode incorrectly processes a forward space record SCSI command 5 Ifthe problem is not one of the above create a debug log directory for either bpdm or bptm and retry the operation Check the resulting debug log file NetBackup Status Code 93 Message media manager found wrong tape in drive Explanation When loading a volume for a backup or restore the tape manager b
343. f SERVER jupiter CLIENT_NAME pluto mac conf portnum 13782 bprdport 13720 Notes 1 The NetBackup Client Properties dialog also has a Network tab with NetBackup client service port BPCD and NetBackup request service port BPRD settings that must be the same as the bpcd and bprd settings in the services file 2 The complete path to the Windows NT 2000 etc services file is SystemRoot system32 drivers etc services 3 All other applicable network configuration must also be updated to reflect the NetBackup information For example this could include the SystemRoot system32 drivers etc hosts file and also WIN and DNS if used Chapter 2 Troubleshooting Procedures NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures 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 Example 4 Clients in Multiple Networks Windows NT 2000 Windows NT 2000 Master Server jupiter Media Server saturn Ethernet mars Policy Client List n ona
344. failed redirecting tmp output file Explanation The system call dup2 3C failed during an attempt to direct interface output from a temporary file to the process s standard output Recommended Action Investigate operating system functionality related to resource limits on the number of open files Ensure that processes are not being interrupted by extraneous signals Media Manager Status Code 88 Message failed initiating child process Explanation A command could not be executed This can occur because the permissions of the command do not allow it to be executed or because system resources such as memory and swap space are insufficient Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Check the permissions on the vncheckxxx vmupdate and oprd binaries and on Windows only the rdevmi installed binary NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Media Manager Status Code 89 Messag
345. fi_freeze FTL nbu_snap_ freeze Cannot turn on snapshot frozen image source oracle ufs_r cache dev rdsk c4t1d11s4 snap error 11 a Look for stale snapshots by running the usr openv netbackup bin driver snaplist command when there are no active backups running If the snaplist command shows cache entries there are stale snapshots Nothing is displayed if there are no stale snapshots Example snaplist output id ident size cached minblk err time 43 6515 8390970 0 0 0 11 16 00 13 31 36 device dev rdsk cit d0s0 cache dev rdsk cl1t6d0s7 b Use the snapoff command to remove the stale snapshot as follows usr openv netbackup bin driver snapoff id where idis the id from the snaplist output such as 43 in the above example 7 62 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Ifa backup using the fsclone frozen image method failed the NetBackup bpbkar process should automatically remove the clone Sometimes however bpbkar is unable to remove the clone In this case you may see messages such as the following in the usr openv netbackup logs online_util log 15 21 45 716 4236 lt 4 gt create _mount_point INF Created mount point tmp _vtrax_test_fastrax_d1lt 4236 15 21 45 869 4236 lt 2 gt onlfi_vfms_logf INF vxfs clone handle 9600344 15 21 45 870 4236 lt 2 gt onlfi_vfms_logf
346. following settings in the Novell sys system autoexec ncf file SET Maximum Packet Receive Buffers 4000 SET Maximum Directory Cache Buffers 4000 SET Maximum Concurrent Disk Cache Writes 2000 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes SET Maximum Concurrent Directory Cache Writes 2000 SET Maximum Physical Receive Packet Size 1514 NetBackup Status Code 25 Message cannot connect on socket Explanation A process timed out while connecting to another process for a particular operation This problem can occur when a process tries to connect to the NetBackup Request Manager service or the NetBackup Database Manager service and the service is not running It can also occur if the network or server is heavily loaded and has slow response time or if an evaluation license key for NetBackup BusinesServer or DataCenter has expired Recommended Action 1 On the Windows master server verify that the NetBackup Request Manager and NetBackup Database Manager services are running If these services are not running start them If the above services are running examine the All Log Entries report for the time of the failure to determine where the failure occurred Ifyou cannot view the report or you geta cannot connect on socket error when trying to view it verify again that the NetBackup Database M
347. for Windows wr 520 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows Index NetBackup 4 5 Troubleshooting Guide for Windows Numerics A 3pc conf file 123 acssel description 459 acsssi description 459 acstest 471 activity logs See debug logs ADAMM 475 ADAMM_GUID 477 admin log 45 admincmd directory 440 Administration interface activity logging 53 errors 51 All Log Entries report 43 Alternate client restores host xlate file 469 altnames file 450 application server status codes Java interface 52 asc value 124 ascd description 459 ascq value 124 associate bat file 54 Audience for manual ix auto configuration problems 12 avrd description 459 Backup Exec beconv problems 473 bephyinv problems 476 file browse problems 477 file restore problems 478 import problems 477 restoring files 477 478 services 478 tape reader 473 Backup process files 422 Macintosh clients 429 multiplexing 424 NetBackup databases 430 NetWare clients 428 UNIX clients 422 Windows 98 95 clients 426 Windows NT 2000 clients 427 Backup Status report 43 base NetBackup license key 76 beconv 473 bephyinv 475 476 bin Media Manager 458 UNIX client 440 BP 437 bp description 441 bp log 46 bp conf file UNIX client server 440 BP NLM 441 bpadm description 441 bparchive description 441 bparchive log 46 bpbackup description 442 bpbackup log 47 bpbkar d
348. 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 Backup Start Notify Timeout on the server to a value that is larger than the default Use the Master Server Properties window to set Backup Start Notify Timeout see Using the Host Properties Window on page 40 NetBackup Status Code 75 Message client timed out waiting for bpend_notify to complete Explanation The bpend_notify script on the client took too long Recommended Action Try to speed up the bpend_notify script or set Backup End Notify Timeout on the server to a value that is larger than the default Use the Master Server Properties window to set Backup End Notify Timeout see Using the Host Properties Window on page 40 NetBackup Status Code 77 Message execution of the specified system command returned a nonzero status Explanation An immediate command returned a nonzero status Recommended Action 1 Verify that the command is specified correctly 2 For NetBackup ServerFree Agent only The policy file list may contain files that do not reside within a file system that was designated as the frozen image source For a frozen image method to be applied to the backup of individual files the frozen image source must be a file system not a raw partition or Volume Manager volume and the files in the policy file list must reside within that file syst
349. formation that appears in the logs see the logging topics in Chapter 3 2 Retry the operation and check the resulting debug logs NetBackup Status Code 69 Message invalid file list specification Explanation The file list received from the server had invalid entries Recommended Action 1 Check the policy 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 2 For NetBackup ServerFree Agent only If this was an offhost backup NetBackup Media Server or Third Party Copy Device code 69 may indicate that the file list contains the ALL_LOCAL_DRIVES entry NetBackup does not support the ALL_LOCAL_DRIVES entry for offhost backup Remove the ALL_LOCAL_DRIVES entry from the file list NetBackup Status Code NetBackup Status Code 71 Message none of the files in the file list exist Explanation The files in the file list did not match any of the files on the client This error can occur when there is only one file in the file list and the file cannot be backed up due to an I O error Recommended Action 1 Verify that the correct file list is specified for this client 2 On Windows 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 applicatio
350. fsite sent date Explanation A request was made to change the offsite sent date for one or more volumes in the volume configuration and the date specified was not valid Recommended Action When changing the offsite sent date provide the date in the format specified by the Media Management interface documentation Media Manager Status Code 144 Message invalid offsite return date Explanation A request was made to change the offsite return date for one or more volumes in the volume configuration and the date specified was not valid Recommended Action When changing the offsite return date provide the date in the format specified by the Media Management interface documentation Media Manager Status Code 145 Message requested drive is already reserved by host Chapter 5 Media Manager Status Codes and Messages 271 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A request was made to reserve a shared drive with vmd DA the device allocator for the Shared Storage Option The drive was already reserved for the requesting host This is an abnormal condition that could occur if two different hosts with the same host name local host name overridden by any SSO_LHOST_NAME entries in the Media Manager configuration file vm conf have registered the same drive name with vmd DA In this case one of those hosts has a drive reservation and the
351. g by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Identify the target components for example vmd and robotic processes on local or remote hosts and verify that all Media Manager binaries are at compatible version level Media Manager Status Code 7 Message daemon terminated Explanation The process is inactive or is terminating or has terminated from an event or signal or as a direct result of a request from an authorized user or process Recommended Action If the targeted product component is needed but has terminated restart the daemons services on the targeted host Media Manager Status Code 8 Message invalid media ID Explanation A process performing a media related operation encountered an empty or incorrectly formatted media identifier or was passed a media ID that could not be operated on as requested Recommended Action 1 Examine command output and debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available
352. g the media Dismount the media if it is not being used by an application Wait for the media to become available as needed Robotic Status Code 238 Message Requested drive is in an offline domain Explanation The drive targeted for a mount request was in a robotic library domain that is offline Recommended Action Bring the robotic library domain ACS Library Storage Module back online or postpone use of drives in that domain until the domain can be brought back online Robotic Status Code 239 Message Requested volume is in an offline domain NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation The volume targeted for a mount request was in a robotic library domain that is in the offline or offline pending state Recommended Action Bring the robotic library domain ACS Library Storage Module back online or postpone use of media in that domain until the domain can be brought back online Robotic Status Code 240 Message A memory allocation attempt failed in the robotic daemon Explanation An attempt by the robotic control daemon to allocate memory has failed This may indicate serious memory problems on your media server Recommended Action Stop all NetBackup Media Manager daemons Consult the documentation for your operating system memory management tools to determine what remaining
353. ge Status Codes 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 Media Manager Status Codes These status codes appear in exit status and command output for most Media Manager commands media and device management user interfaces and system or debug logs Media Manager Status Code 1 Message request completed Explanation A requested operation was completed The operation may have been one of several related operations for a particular task NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action None Media Manager Status Code 2 Message system error Explanation A system call failed This status code is used for a generic system call failure that does not have its own status code Recommended Action 1 Check for other error messages in the command or interface output to determine which system call failed Enable debug logging retry the operation and check the debug log files for more specific error messages 2 Check the system application log for error and warning messages 3 Verify that the system is not running out of virtual memory If virtual memory is the problem shut down unused applications or increase the amount of virtual memory To increa
354. ge Request terminated because media ID is expired Explanation A mount request has been canceled because the media was requested with write access and the media has expired Recommended Action Request read only access to the media on the mount request if a read only operation is needed Replace the media or change the expiration date to a future date based on site policy A media management interface can be used to view and change the expiration date for the media Check and correct the system date time as needed Device Management Status Code 28 Message Error in MsgGet Explanation An attempt was made by 1tid the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows to obtain a message queue identifier used for internal message communications and the request failed due to a system error The error probably indicates a lack of system resources for message queues or mismatched software components Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1t id the device daemon on UNIX or NetBackup Device Manager service on Windows 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Check the installed software comp
355. ge queue NetBackup Status Code 212 errors encountered partial success NetBackup Status Code 306 Chapter 4 NetBackup Status Codes and Messages 181 NetBackup 4 5 Troubleshooting Guide for Windows Messages NetBackup 4 5 Troubleshooting Guide for Windows evaluation software has expired See www veritas com for ordering information NetBackup Status Code 161 events out of sequence image inconsistency NetBackup Status Code 229 execution of a vault notify script failed NetBackup Status Code 272 execution of the specified system command returned a nonzero status NetBackup Status Code 77 failed accessing daemon lock file NetBackup Status Code 158 failed attempting to copy consolidated report file NetBackup Status Code 287 failed closing mail pipe NetBackup Status Code 102 failed opening mail pipe NetBackup Status Code 101 failed reading policy database information NetBackup Status Code 218 failed reading global config database information NetBackup Status Code 215 failed reading retention database information NetBackup Status Code 216 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages failed reading storage unit database information NetBackup Status Code 217 failed reading user directed filelist NetBackup Status Code 208
356. ger media ID BE0001 bpcd will be launched on host dell_2 and will launch bptm to obtain the ADAMM GUID corresponding to Media Manager media ID of BE0001 This can be seen by searching the bpcd debug log on the media server host for the following text 13 58 47 029 3792 2544 lt 2 gt bpcd main BPCD GET FILE REC ROST 13 58 47 029 3792 2544 lt 2 gt bpcd get file rec received mediaid BE0001 13 58 47 029 3792 2544 lt 2 gt bpcd_get_file rec received keyword 22 13 58 47 029 3792 2544 lt 2 gt bpcd_get_file rec received path 13 58 47 029 3792 2544 lt 2 gt bpcd_get_file rec received client adaj 13 58 47 029 3792 2544 lt 2 gt bpcd_get_file rec received dirs only 0 13 58 47 029 3792 2544 lt 2 gt bpcd_get_file rec received depth 2 13 58 47 029 3792 2544 lt 2 gt createProcessWithOutput CreateProcess of gt D nb NetBackup bin bptm exe guid ev BE0001 cmd lt 13 58 47 710 3792 2544 lt 2 gt MediaID2MediaGuid Backup Exec media id BE0001 has guid 6EE3FFEF B111 4EDD 97C1 78931D988268 voldb dell_2 The above text indicates that bptm obtained the ADAMM GUID 6EE3FFEF B111 4EDD 97C1 78931D988268 corresponding to Media Manager media ID BE0001 from the Media Manager volume database on host voldb dell_2 The text below from the bpcd debug log file indicates that two files were returned to bpdbm 13 58 50 023 files 3792 2544 lt 2 gt BEopen file rec GetNBFileList returns 2 bpdbm will send
357. ges on a tape ww 5 4 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows tape overhead The space required for data that is not part of the backup images For example tape marks and catalogs of what are on the tape are considered overhead tape spanning Using more than one tape to store a single backup image tar Tape Archive program that NetBackup uses to extract backup images during a restore target See target service 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 For the specific vendor types and models in this category see the VERITAS support web site TLH Tape Library Half inch A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site This robot type is supported only by NetBackup DataCenter servers TLM Tape Library Multimedia A Media Manager designation for a category of robot For the specific vendor types and models in this category see the V
358. get 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 policy On Macintosh clients check the version file in the bin folder in the NetBackup folder in the Preferences folder Ifthe error is being displayed from a Java interface tell them how to enable the debug print manager in the Java startup file Retry and compare the parameters logged in the Java log with the parameters listed in the commands usage statement If the above actions do not reveal the problem create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Status Code 21 Message socket open failed Explanation A socket could not be opened Recommended Action 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 debug log directories for the processes that returned this status code Then retry the operation and check the resulting debug logs On Windows verify that the recommended service packs are installed NetBackup Status Code 22 Message socket close failed Explanation A socket could not be closed Recommended Action 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
359. gt bpcd restore image files mediaid BE0001 D Appendix D Backup Exec Tape Reader for NetBackup 487 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs string Cannot 16 26 03 431 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 16 25 25 918 1600 4028 f temp be restore 16 25 25 918 1600 4028 16 26 03 431 1600 4028 lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt bpcd_restore_image files bpcd_restore_image files bpcd_restore_image files bpcd_restore image files G nb NetBackup logs user_ops adonijah logs NBWINO008 bpcd_restore_image files bpcd_restore_image files bpcd_restore_image files bpcd_restore_image files bpcd_restore image files bpcd_restore_image files bpcd_restore_image files keyword 22 obj_desc NULL keep 1 progress file rename_file NONE commit 0 dirByteCount 0 tempDirectory NONE mountDatabase 0 beFilePathLen 19 beRedirectionPath lt 2 gt createProcessWithOutput CreateProcess of gt D nb NetBackup bin bptm exe guid ev BE0001 cmd lt lt 16 gt MediaID2MediaGuid
360. gt bpcd_get_file rec received client adaj 624 3792 3596 lt 2 gt bpcd_get_file rec received dirs only 0 624 3792 3596 lt 2 gt bpcd_get_file rec received depth 3 644 3792 3596 lt 2 gt createProcessWithOutput CreateProcess of gt D nb NetBackup bin bptm exe guid ev BE0001 cmd lt 15 09 04 267 3792 3596 lt 16 gt MediaID2MediaGuid Error can t get GUID from 15 09 04 267 3792 3596 lt 16 gt MediaID2MediaGuid couldn t obtain media guid for Backup Exec media id BE0001 The following is from the bptm log on the media server that contains the Backup Exec catalogs corresponding to the image 15 09 04 207 4160 3616 lt 16 gt vmd_connect unable to connect to vmd Error number 10061 15 09 04 217 4160 3616 lt 16 gt query _one volume query _onevol request status cannot connect to vmd 70 15 09 04 237 4160 3616 lt 16 gt GetMediaGuid Media Manager error 70 cannot connect to vmd host dell 2 The bptm log above indicates that it could not connect to vmd perhaps because vmd was not running Example 3 If the Backup Exec services are not running on the media server that contains the Backup Exec catalogs corresponding to the image the bpcd debug logs indicate the problem Appendix D Backup Exec Tape Reader for NetBackup 483 T NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs T5229
361. h was incorrectly formatted and the Backup Exec job was not started This can be seen in the bpcd log below 16 27 00 555 1516 1420 lt 16 gt GetRedirectionDeviceAndPath Format of Redirection path is not correct Correct format for NT target is Share Name Directoryl1 16 27 00 555 1516 1420 lt 16 gt SetRestoreJobProperties Error in redirection 16 27 00 555 1516 1420 lt 16 gt StartRestoreJob Restore Job properties could not be set 16 27 00 555 1516 1420 lt 2 gt write BE restore progress sending job status message to bprd JOB NO START _R REDEEMER 16 27 00 555 1976 988 lt 2 gt bpcd main BPCD LOG ROST NO STATUS 16 27 00 555 1516 1420 lt 2 gt FreeBELibrary Successfully unloaded beutil dll Example 5 If a Backup Exec restore job requires media that has been misplaced the restore job fails The progress log of the restore job indicates the location of the Backup Exec job log file that contains the reason for the failure Following is an example of such a NetBackup progress log 13 49 42 2 5 2002 Restore Started 13 50 01 11 xxx Media id A00000 is needed for the restore 13 50 01 11 001 Restoring from image created 12 17 2001 01 27 18 PM 13 50 10 11 001 Backup Exec restore job started on host ANTRIKSH 13 52 10 11 001 Backup Exec restore job failed See file ANTRIKSH C nbu BackupExec Data BEX09 txt for details 13 52 12 11 001 Status of restore from image created 12 1
362. has logged during the specified time Backups period This information is a subset of the information in the All Log Entries report All Log Entries All log entries for the specified time period Chapter 3 Using the Logs and Reports NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 Windows Event Viewer Application Logs On Windows the NetBackup services and programs log information to the Event Viewer Application log Look for messages pertaining to NetBackup in these logs Debug Logs If a problem requires more information than is available through the normal logs and reports you can enable debug logs that show detailed information about specific processes To enable debug logging for a process create a directory for its logs as explained in the following topics Each process creates logs in its own logging directory The logs that are available depend on whether the system is a server or a client Debug Logs on Servers Note Refer to the Media Manager Logs section for enabling Media Manager debug log entries To enable debug logging on NetBackup servers create the appropriate directories under install_path Net Backup logs The table below lists the debug log directories that apply to
363. hat all product binaries are properly installed 5 Verify that there are no unexpected Media Manager processes running by executing vmps Some processes are expected to remain running but some processes that do not go away could indicate a more serious problem such as a hung system call Robotic Status Code 232 Message Volume not found in library Explanation The requested media was not found in the robotic library The media has been ejected or become inaccessible for some other reason Recommended Action wer 352 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Issue a robot inventory Contents report to obtain the list of media in the robotic library Check to see whether inventory filters have been enabled in the Media Manager configuration file since they affect the contents of the media list returned from the robotic daemon process Use a robot test utility or an operating system vendor administrative in
364. hat your servers and clients are running supported operating system versions and the peripherals you are using if any are supported See the NetBackup release notes and the NetBackup device compatibility lists on www veritas com for this information 2 Check for status codes or messages 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 If you find a status code or message in either of the above reports go to the chapter titled NetBackup Status Codes and Messages or Media Manager Status Codes and Messages and perform the recommended corrective actions b Ifthe problem pertains to media or device management and either NetBackup does not provide a status code or you cannot correct the problem by following the instructions in NetBackup Status Codes and Messages or Media Manager Status Codes and Messages check the Event Viewer Application log This log can show the context in which the error occurred and the error messages are usually descriptive enough to point you to a problem area c Check applicable debug logs that are enabled and correct problems you detect If these logs are
365. he error Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1t id the device daemon on UNIX or NetBackup Device Manager service on Windows The detailed reason for the canceled request should be available in the system log command output or from a device monitor interface Correct the problem and resubmit the request if needed Device Management Status Code 64 Message Cannot assign a robotically controlled device Explanation An attempt was made to manually assign a specific device to satisfy a mount request and the chosen device was configured in a robotic library Recommended Action Assign the request to a standalone drive or allow requests for mounts in robotic drives to be automatically assigned Device Management Status Code 65 Message Invalid volume pool specified Explanation On a mount request the media pool specified was not valid Recommended Action Resubmit the request specifying a volume pool name that is no more than 20 ASCII characters in length Device Management Status Code 66 Message Request terminated because of volume pool mismatch Chapter 5 Media Manager Status Codes and Messages 335 Or NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation The volume pool specified on the tpreg command did not match
366. he level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 265 Sr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 On the UNIX host where the request originated check the system group configuration and ensure that add change pool requests include only valid group IDs No validation is attempted for group IDs in volume pools on Windows Media Manager Status Code 129 Message invalid drive name Explanation A request was made to register reserve or release a shared drive with vmd DA the device allocator for the Shared Storage Option and the drive name was not correctly formatted Recommended Action 1 Examine the daemon and reqlib debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Ensure that the drive name is from 1 to 48 ASCII characters in length The following special characters are allowed period plus minus
367. he necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Use vmrule to investigate integrity of the barcode rule database The daemon debug log file should indicate the number of fields expected and the number of fields found in the barcode rule record Restore a saved version of the barcode rule database if the barcode rule database cannot be manually corrected Media Manager Status Code 120 Message all available rule numbers are in use Explanation A request was made to add a barcode rule in the barcode rule configuration No unique rule numbers could be generated because the available rule numbers were used up Recommended Action Consolidate barcode rules so that a new rule number becomes available Media Manager Status Code 121 Message failed appending to rule database Explanation A request was made to add change or delete a barcode rule and a barcode rule record could not be appended to the barcode rule database file Chapter 5 Media Manager Status Codes and Messages 261 Sr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a If not already en
368. he operation and examine the logs 2 Investigate the state of the physical hardware and correct the holder status for storage drive and transport elements as needed Then resubmit the request Robotic Status Code 223 Message Robot busy cannot perform operation Explanation The robot is busy performing another operation using resources needed for the requested operation Recommended Action Wait until the robot is done performing current external based requests including robot inventory and inject eject media before starting new requests Check vendor or operating system administrative interfaces and logs to see if robotic resources are busy Robotic Status Code 224 Message Control daemon connect or protocol error Explanation A protocol error occurred between robotic and other components Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the media mount failure Verify that all Media Manager binaries are at a compa
369. he option that is available in the NetBackup administrator interface Scheduled automatic incremental or full backups In this case bprd starts the scheduler at intervals determined by the wakeup interval global attribute Stopped By Completion of all backups that are due Debug Log bpsched 1og on the server On master and media servers bptm is the tape media manager and is used when the storage unit type is Media Manager This program manages transfer of images between the client and the storage device It also handles communication between the backup and Media Manager software In addition bptm manages the NetBackup media database and provides information for the media list report screen Started By For each backup or restore bpbrm starts an instance of bptm on the server that has the storage unit Stopped By Completion of operation Debug Log bptm log on the server On NetWare nontarget clients this is the program that allows the system that has the client user interface to communicate with the Netware server that is the NetBackup client Started By Starting NetBackup for NetWare Stopped By Exiting the client user interface Debug Log BPSRV LOG file in the NetBackup LOGS directory on the client On Windows NT 2000 clients this is the NetBackup System Registry Replacement utility Started By NetBackup as required Stopped By Completion of operation Debug Log BPSYS LOG file in the NetBackup LOGS dir
370. he physical location of the media Check integrity of the drive drive path and media if the media is found in a logically DOWN drive Verify that the media is not a misconfigured cleaning tape Move the media into the robotic library and update the volume configuration if the media was not present in the library Set the cartridge tab to allow write access or request the media with read only access if the write protection was the cause of the error Device Management Status Code 36 Message Request terminated by tpunmount call from another process Explanation A request was made to change the limit for the number of times that a volume can be mounted with write access for one or more volumes in the volume configuration and the value specified was not within the acceptable range The maximum number of mounts value may also be invalid in the number of mounts cleanings field of a barcode rule Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available
371. he value to 0 disables backups and archives Recommended Action To enable backups and archives change the Maximum jobs per client value to the desired nonzero setting This attribute is on the Global NetBackup Attributes tab in the Master Server Properties dialog box See Using the Host Properties Window on page 40 NetBackup Status Code 195 Message client backup was not attempted Explanation A backup job was in the NetBackup scheduler s worklist but was not attempted Recommended Action 1 Retry the backup either immediately with a manual backup or allow the normal scheduler retries 2 For additional information check the All Log Entries report For detailed troubleshooting information create a bpsched debug log directory on the master server After the next backup attempt check the debug log Some actions to perform are Verify that the NetBackup Volume Manager and NetBackup Device Manager services are running Look for a problem in an earlier backup that made the media or storage unit unavailable NetBackup Status Code 196 Message client backup was not attempted because backup window closed Chapter 4 NetBackup Status Codes and Messages 131 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A backup or archive operation that was queued by the backup scheduler was not attempted because the backup window was n
372. her opening in a robot where you can insert or remove a tape without having to access the interior of the robot After inserting a tape you move it to a slot by using an inject command Prior to removing a tape you move it to the port by using an eject command The inject and eject commands are supported through the add and move screens in the Media Manager administration interface media host NetBackup server to which the job client is sending the data media ID An identifier that is written on a volume as part of the recorded label Media Manager Software that is part of NetBackup and manages the storage devices and removable media Media Manager Host Host where Media Manager is installed may have devices attached 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 NetBackup BusinesServer does not support remote media servers menu interface A character based interface for use on terminals that do not have graphical capabilities mount Make a volume available for reading or writing mount point The point where a file system on a disk logically connects to a system s directory structure so the file system is available to users and applications yy Glossary 505 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Wi
373. hese status codes are returned if a robotic daemon process was started from the command line and an error occurs For example if the administrator executes the following usr openv volmgr bin t18d and no robots are configured the following may be returned TL8 No robots are configured These status codes are also logged to the system log Usually robotic daemons processes are not started from the command line but are started automatically as needed when 1tid starts Robot Error Status Code 1 Message You must be ROOT to start daemon Explanation A robotic daemon was started by a user other than root This applies to UNIX systems only Recommended Action Log on as the root user before starting robotic daemons Allow robotic daemons to be started automatically as needed by 1t id the device daemon Robot Error Status Code 2 Message LTI Daemon may not be running Explanation On an attempt to start a robotic daemon process an attempt to connect to the 1tid message queue failed indicating that 1t id the device daemon NetBackup Device Manager service may not be running Recommended Action 1 Start 1tid so that shared memory can be initialized allowing the robotic daemon process to function 2 If problems persist examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verb
374. hine is not the volume database host Explanation A request was made to initiate vmd on a host other than the local host vmd is the Media Manager volume daemon UNIX or NetBackup Volume Manager service Windows NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes vmd port numbers other than the default or use of unsupported options can affect which host and port is referenced in interfaces used to start vmd Recommended Action 1 Initiate vmd on the local host only by logging on to the host where vmd needs to be running and starting vmd on that host On UNIX execute usr openv volmgr bin vmd v On Windows NT start the NetBackup Volume Manager service in Services of the system Control Panel On Windows 2000 Services is in Administrative Tools of the Control Panel 2 If more information is needed to explain the problem examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 3 Make sure port numbers are consistent Media Manager
375. hooting Guide for Windows inject Move media into a robotic library inport See media access port inode A UNIX data structure that defines the existence of a single file install_path Directory where NetBackup and Media Manager software is installed The default on Windows servers is C Program Files VERITAS and on UNIX it is usr openv 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 See cancel a job label Identifier of a tape or optical disk volume A recorded label includes a media ID A barcode label allows a barcode scanner to be used for media tracking library See robotic library Glossary 503 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows link See hard link or symbolic link LMF Library Management Facility A Media Manager designation for a category of robot For the specific vendor types and models in this category see the VERITAS support web site This robot type is supported only by NetBackup DataCenter servers load noun Amount of work that is being performed by a system or the level of traffic o
376. hooting information create a debug log directory for the process that you suspect of returning this status code Then retry the operation and check the resulting debug log NetBackup Status Code 34 Message failed waiting for child process Explanation The bpsched process encountered a failure while waiting for a child process to complete NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 a debug log for the process that you suspect of returning this status code Then retry the operation and check the resulting debug log NetBackup Status Code 35 Message cannot make required directory Explanation Could not create a required directory Possible causes are A process does not have permission to create the directory The path to the directory is not valid An IO error occurs There was no space available on the device containing the directory Recommended Action 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
377. hose images are being browsed The Backup Exec services are the following Backup Exec 8 x Agent Browser Backup Exec 8 x Alert Server Backup Exec 8 x Device amp Media Service Backup Exec 8 x Job Engine Backup Exec 8 x Naming Service Backup Exec 8 x Notification Server gt 2 Backup Exec 8 x Server Backup Exec File Restore To determine the cause of Backup Exec file restore problems examine the bpra bpcd and bptm logs To restore Backup Exec files using the Backup Archive and Restore interface 1 Open the Restore menu and choose Select Restore Type 2 Set the restore type to Backup Exec Backups or Normal and Backup Exec Backups For more assistance refer to the NetBackup user guide appropriate for your platform To restore Backup Exec files using the bprestore command ensure that the F parameter has been specified correctly to restore only Backup Exec files or both Backup Exec and NetBackup files To restore only Backup Exec files F 524288 should be specified To restore both Backup Exec and NetBackup files F 1048576 should be specified Refer to the NetBackup DataCenter System Administrator s Guide for the usage of the bprestore command Ensure that the Backup Exec services are running on the Media Servers that contain the Backup Exec catalogs whose images are being restored The Backup Exec services are the following Backup Exec 8 x Agent Browser Backup Exec 8 x Alert Server NetBac
378. ia Manager Status Code 113 invalid global device database entry Media Manager Status Code 151 invalid host name Media Manager Status Code 136 invalid maximum mounts Media Manager Status Code 114 Chapter 5 Media Manager Status Codes and Messages 377 m NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages invalid media generation rule Media Manager Status Code 140 invalid media ID for naming mode Media Manager Status Code 41 invalid media ID Media Manager Status Code 8 invalid media type Media Manager Status Code 9 invalid number of cleanings Media Manager Status Code 74 invalid number of mounts Media Manager Status Code 141 invalid offsite location Media Manager Status Code 142 invalid offsite return date Media Manager Status Code 144 invalid offsite sent date Media Manager Status Code 143 invalid offsite session id Media Manager Status Code 148 invalid offsite slot Media Manager Status Code 147 378 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Invalid Operator Device Management Status Code 12 invalid pool database entry Media Manager Status Code 102 invalid protocol request Media Manager Status Code 6 invalid query type Media Manager S
379. ia Manager volume daemon on UNIX encountered a system call error while attempting to unlock the volume database Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine the daemon debug log for a more detailed message on the system error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Execute vmps to ensure that vmd and vmdb_dump are not both running at the same time 3 Ensure that no other process is locking or unlocking the database file usr openv volmgr database volDB Media Manager Status Code 32 Message database write record operation failed Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows encountered an error while writing a volume database record Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and res
380. ia id NetBackup Status Code 179 done NetBackup Status Code 222 duplicate profile specified use full robot vault profile NetBackup Status Code 305 EC_badop NetBackup Status Code 113 EC_end NetBackup Status Code 115 EC_error NetBackup Status Code 114 eject process could not obtain information about the robot NetBackup Status Code 295 eject process failed to start NetBackup Status Code 292 eject process has already been run for the requested vault session NetBackup Status Code 307 ww 180 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages eject process has been aborted NetBackup Status Code 293 error caused by invalid data in vault configuration file NetBackup Status Code 284 error creating or getting message queue NetBackup Status Code 209 error encountered attempting backup of catalog Two Phase BU NetBackup Status Code 302 error encountered executing Volume Manager command NetBackup Status Code 303 error obtaining date of last backup for client NetBackup Status Code 207 error occurred during initialization check configuration file NetBackup Status Code 103 error receiving information on message queue NetBackup Status Code 210 error requesting media tpreq NetBackup Status Code 98 error sending information on messa
381. ication NetBackup Status Code 242 pipe close failed NetBackup Status Code 18 premature eof encountered NetBackup Status Code 233 190 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages process called but nothing to do NetBackup Status Code 296 process was killed by a signal NetBackup Status Code 63 regular bpsched is already running NetBackup Status Code 214 report requested without eject being run NetBackup Status Code 309 request attempted on a non reserved port NetBackup Status Code 45 requested media id is in use cannot process request NetBackup Status Code 97 requested media id was not found in NB media database and or MM volume database NetBackup Status Code 95 required or specified copy was not found NetBackup Status Code 147 required value not set NetBackup Status Code 152 schedule windows overlap NetBackup Status Code 231 scheduler child killed by signal NetBackup Status Code 211 Chapter 4 NetBackup Status Codes and Messages 191 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages scheduler found no backups due to run NetBackup Status Code 200 server backup restore manager s network is unreachable NetBackup Status Code 203 server is not th
382. ices or by executing the command s verbose option if available b Retry the operation and examine the logs Media Manager Status Code 50 Message invalid change entry request Explanation A request to change volume information was sent to vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows but an older version of vmd is installed on the volume database host which does not support the type of change operation requested Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Check the usage statement for expected usage and compare with the parameters being sent to start the new process 3 Ensure that change volume requests from a newer release version level are not sent to vmd on an older incompatible version level Media Manager Status Code 51 Message cannot auto eject this robot type Explanation
383. ide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify the robot host in the device configuration to be the same case sensitive host name on all hosts where the robot is configured Re issue the request As an alternative use move by volume group to logically move all volumes from a robotic volume group to standalone and then back into the robot Specify the robot host as the host name used in the robot configuration Then re issue the request Media Manager Status Code 62 Message failed redirecting input to pipe Explanation A system pipe could not be created Recommended Action Check the interface output for the specific system error and investigate operating system functionality related to the failure Media Manager Status Code 63 Message child process killed by signal Explanation A robot inventory update process was terminated by an unexpected signal Recommended Action 1 Examine interface output and debug logs for a more detailed message error a If
384. ide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A request was made to release a shared drive with vmd DA the device allocator for the Shared Storage Option The drive was not reserved by the requesting host although it had been reserved for another host This is an abnormal condition that could occur if there was a network problem or a suspended process The following is a possible scenario 1 Host A reserves a shared drive 2 Host A becomes unavailable for some time unable to communicate with other hosts 3 Host B determines that the host having the reservation Host A is no longer available and makes a request to vmd DA denoting Host A as unavailable 4 Some other host such as Host A or Host C reserves the drive 5 The host originally owning the drive reservation tries to release the drive Recommended Action Correct the network or process problem that led to the communications problem Ensure that unique non duplicate strings are being used for host names and for SSO_HOST_NAME configuration file entries Media Manager Status Code 134 Message requested drive is not currently reserved Explanation A request was made to release a shared drive with vmd DA the device allocator for the Shared Storage Option SSO but the drive was not reserved by any hosts This is an abnormal condition that could occur if there was a network problem or a suspended process The follo
385. idence Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that the specified robot residence and volume group are compatible with other volumes in the volume configuration that are in the specified volume group Do not try to move volumes in the special No Volume Group name to a robotic Chapter 5 Media Manager Status Codes and Messages 241 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows residence without moving them to a new or auto generated volume group Choose a different volume group on the request or let the volume group be automatically selected Volume group selection depends on the specific interface being used Media Manager Status Code 82 Message robot host and volume group mismatch Explanation A request was made to add volumes or change volume residences in the volume configuration and the robot host and volume group associated with the volume configuration changes are in conflict with the requirements for volume groups All v
386. ield of media_id in the Media Manager volume database is not NULL and not present in the Backup Exec ADAMM database Such a situation can arise when the Media Manager volume database was updated by utilities other than bephyinv or beconv like vmadd Recommended Action Examine the Media Manager volume record corresponding to media_idand determine whether the ADAMM GUID field is correct If required run bephyinv on media_id After updating the volume record corresponding to media_id run beconv again Message Backup Exec media type and Media Manager volume record media type incompatible Explanation This happens when the user runs beconv with the beconv m media_id option but the Backup Exec media record corresponding to media_id has a different base media type than the base media type of the Media Manager volume record Recommended Action Examine the Media Manager volume record corresponding to media_id and determine whether the media type is correct If required run bephyinv on media_id After updating the volume record corresponding to media_id run beconv again Message No corresponding Media Manager record found for this media Explanation This happens when the user runs beconv with the tbs option specified and beconv could not associate a Backup Exec media with any Media Manager volume database records This situation can arise when the tbs option is specified and a NetBackup robot inventory update has not been done on the requi
387. ies to the robot you are testing see below However in the case of an RSM robot the robot must be configured under NetBackup before a test can be run When the RSM robot has been configured use the robtest command as described above ACS install_path Volmgr bin acstest r ACSLS_HOST RSM NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows install_path Volmgr bin rsmtest r robotnumber roboticpath TL4 install_path Volmgr bin tl4test r roboticpath TL8 install_path Volmgr bin t1l8test r roboticpath TLD install_path Volmgr bin tldtest r roboticpath TLH install_path Volmgr bin tlhtest r robotic_library_name TLM install_path Volmgr bin tlmtest r DAS_Hostname TS8 install_path Volmgr bin ts8test r roboticpath TSD install_path Volmgr bin tsdtest r roboticpath Note For more information on ACS TLH LMF and TLM robotic control see the appendixes in the NetBackup DataCenter Media Manager System Administrator s Guide for Windows For more information on RSM robotic control refer to the Microsoft Removable Storage Manager RSM appendix in the NetBackup BusinessServer Media Manager System Administrator s Guide for Windows In the above commands roboticpath is the full path to the device file for the robotic control SCSI Refer to the Media Manager Device Configuration Guide for Windows and review the chapter for your platform to find the appropriate va
388. ifferent UNIX client Backups of a UNIX client to the same or a different UNIX client Backups of a UNIX client to a different Windows client Backups of an Netware client to the same or a different Netware client Backups of an Netware client to a different Windows client gt 2 2 Backups of an Netware client to a different UNIX client Note The path specified depends upon the client type of the destination machine Restoring to Windows Clients When redirecting a restore to Windows clients the path should be specified as follows Appendix D Backup Exec Tape Reader for NetBackup 479 r v NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup Exec File Restore share_name dirl For example to restore to C temp if the sharename for drive C is C specify the path as C temp Note When restoring Netware client backups to a Windows client the NetBackup Windows client interface nbwin exe NetBackup Java interface or the bprestore command should be used The NetBackup Netware client nbnwnt exe should not be used to restore Netware client backups to Windows clients Restoring to UNIX Clients When redirecting a restore to UNIX clients the path should be specified as follows export_path dirl export_path is defined in the agent cfg file on the UNIX client this file is a Backup Exec configuration file for the Backu
389. ile on the NetBackup media server prior to running the backups usr openv volmgr DISABLE RESOURCES BUSY If you have already attempted the backup and see this error then create the file and rerun the backups NetBackup Status Code 135 Message client is not validated to perform the requested operation NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation This is usually caused by a request to restore files to a client other than the one that made the request and the request did not come from the administrator on a NetBackup server Recommended Action Retry the operation as the administrator on the master server Also see status code 131 NetBackup Status Code 140 Message user id was not superuser Explanation The process was started by a user or process that did not have administrator privileges Recommended Action If desired give administrator privileges to the user or process and retry the operation NetBackup Status Code 141 Message file path specified is not absolute Explanation The file specification must be an absolute path Recommended Action Correct the file specification and retry the command NetBackup Status Code 142 Message file does not exist Explanation This code is reserved for future use Recommended Action None NetBackup Status Code 143 Message invali
390. imeout timed out waiting during the client hookup bpbrm Exit client backup EXIT STATUS 41 network connection timed out then the problem is in the routing configuration on the server Verify that the client IP address is correct in the name service that is being used Also see Resolving Network Communication Problems on page 21 4 Make sure all recommended NetBackup patches have been installed Check the VERITAS support web site for current patch information Go to www suppotrt veritas com then select NetBackup followed by files and updates 5 Add the CLIENT_READ_TIMEOUT values to the master server media server and client when a NetBackup database extension product is installed The values should all be the same for each server The value set is dependent on the size of the database being backed up See the NetBackup System Administrator s Guide for more information on CLIENT_READ_TIMEOUT 6 Make sure enhanced authentication is configured correctly See the chapter on enhanced authentication in the NetBackup System Administrator s Guide For example the following could result in status code 41 host A is configured to use enhanced authentication with host B but host B is not configured to use enhanced authentication with host A In this case connections from host B to host A are likely to fail with status code 41 Connections from host A to B are likely to fail with authentication errors status code 160 NetB
391. in previous steps 7 Start a user backup and restore of a file by using the client user interface on the master server Monitor the status log for the operation If successful this operation verifies that client software is functional on the master server If a failure occurs check the NetBackup All Log Entries report To further isolate the problem check the appropriate debug logs from those listed below The Using the Logs and Reports chapter explains which logs apply to specific client software Note These logs exist only if you enabled debug logging in step 1 The debug logs are in the install_path NetBackup 1logs directory bpbkar bpcd bprd nbwin gt bpinetd 8 Reconfigure your test policy 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 debug log directories for the processes listed below The Using the Logs and Reports chapter explains which logs apply to specific client types bprdon the server bpcd on the client bpbkar on the client nbwin on the client bpinetd 10 Perform a user backup and then a restore from the client specified in step 8 ww 18 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Gener
392. in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Identify the targeted host and verify that all Media Manager binaries on that host are at a compatible version level with other hosts that are part of the configuration Update the software version as needed Media Manager Status Code 164 Message the robotic daemon returned an invalid volume GUID Explanation An invalid RSM GUID was returned from the RSM robotic control process which probably obtained it from the RSM API RSM is the Microsoft Removable Storage Manager and GUID is a Global Unique Identifier Recommended Action 1 Examine the system s application log the Removable Storage system interface and the daemon and reqlib debug logs for a more detailed message on the error a If it is not already enabled enable debug logging by creating the necessary folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the NetBackup Device Manager service b Retry the operation and examine the logs From the daemon debug log file determine the media ID that has the invalid RSM GUID 2 Make sure that the software components are compatible Media Manager Status Code 165 Message Evaluation period expired Go to www veritas com to order this product Explanation The NetBackup evaluation software has expired See www
393. indows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Media and Device Management Process When the Media Manager daemons are running NetBackup Storage Migrator UNIX only Storage Migrator for Microsoft Exchange Windows 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 1tid Figure 14 1t id determines the location of the requested media ID by sending a query to the Media Manager volume daemon vmd The volume daemon then returns the information it has about the media including robot number robot type host slot and barcode If the media is in a robot 1t id sends a mount request to the robotic daemon that manages the drives in the robot that are configured on the local host The robotic daemon then chooses an available drive mounts the media and sets a drive busy status in memory shared by itself and 1t id If it receives another mount request 1t id checks that status to determine which if any drives are available Drive busy status also appears in the Device Monitor Assuming that the media is physically in the robot the media is mounted and the operation proceeds If not a NetBackup backup job and the media is not in the robot 1tid sends a mount request which appears as a pending request in the Device Monitor An operator must then insert the media in the robot and use the appropriate
394. ine the user interface output for the system error associated with the failed system call and troubleshoot according to operating system vendor recommendations Device Configuration Status Code 42 Message Cannot create miscellaneous working repository Explanation On a device configuration request the miscellaneous working directory folder was missing and could not be created Recommended Action Find out why usr openv volmgr misc UNIX or install_path volmgr misc Windows cannot be created On Windows determine which accounts the NetBackup Volume Manager service and device configuration interfaces are running under and compare them with the security properties of the database folder On UNIX determine whether users or device configuration interface callers are running under a user and group with permissions to create the miscellaneous directory Device Configuration Status Code 43 Message Cannot backup restore local device database files NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation There was a failed request to create a backup copy remove a backup copy or replace the current copy of the local device databases These databases are lt idevs and robotic def located in usr openv volmgr database UNIX or install_path volmgr database Windows Recommended Action 1 Examine the
395. ing Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Record All Information If your troubleshooting attempt is unsuccessful customer support can provide further assistance Before calling have the following information ready Product platform and device information Product and its release level Server hardware type and operating system level Client hardware type and operating system level if a client is involved Storage units being used if it is possible that storage units are involved If it looks like a device problem be ready to supply device information such as the types of robots and drives and their version levels along with Media Manager and system configuration information Software patches to the products that were installed Service packs and hotfixes that were installed What is the definition of the problem as described earlier in this chapter Copies of logs or core dumps if any can also be required Have you had this problem before If so was there a successful resolution and what did you try that time Has the configuration been changed recently and if so what was changed Ifnecessary can you communicate with technical support through ftp email or fax This can be useful for sending things such as copies of logs Problem Report Information on page 5 lists the information you need and also provides methods for gathering inf
396. ing busy Robotic Status Code 246 Message Failed to find an available slot to inject to Explanation An attempt to inject a volume into a full library failed This should only occur when the library is full meaning that all storage elements either contain media or have been assigned media that is currently mounted in a drive Note that some libraries that support multiple media types restrict which type of media can be assigned to each storage element In this case this error might occur even if some of the storage elements in a library were not full Since the empty storage elements may not match the media type for the media you are trying to inject the library is full for this media type Recommended Action Clear the media access port then re inventory the robot by doing a volume configuration update Robotic Status Code 248 Message Cannot recover aborted eject with this type of media access port Explanation An eject failed from a robot with a media access port that does not allow automatic recovery of media Recommended Action Manually remove any media remaining in the robot s media access port then re inventory the robot to ensure that NetBackup s volume database matches what is in the library You can also use the robot s utilities or the NetBackup robtest utility to move the media from the robot s media access port back to robotic storage elements In any case re inventory the robot to ensure that the NetBackup volume da
397. ing debug logs for the parameters passed to tar and call customer support NetBackup Status Code 183 Message tar received an invalid archive Explanation The data passed to tar was corrupt Recommended Action 1 Create a bpcd debug log directory on the client on a Macintosh NetBackup creates the log automatically 2 Ona Windows client create a tar debug log directory 3 Increase the debug or log level as explained in the debug log topics in Chapter 3 wr 128 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 4 5 Retry the operation and check the resulting debug logs Reboot the client to see if it corrects the problem NetBackup Status Code 184 Message tar had an unexpected error Explanation A system error occurred in tar Recommended Action 1 Create a bpcd debug log directory on the client on a Macintosh NetBackup creates the log automatically Increase the debug or log level as explained in the debug log topics in Chapter 3 On a Windows client create a tar debug log directory Retry the operation and check the resulting debug logs Reboot the client to see if it corrects the problem NetBackup Status Code 185 Message tar did not find all the files to be restored Explanation There were files in the tar file list that were not in the image Recommended Actio
398. ing 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 status on the client for additional information about the error 2 For detailed troubleshooting information create a debug log directory for either bptm or bpdm whichever applies and retry the operation Check the resulting debug log NetBackup Status Code 176 Message cannot perform specified media import operation Explanation The tape manager bptm detected an error condition when attempting to import a specific backup image Possible reasons for this are Media ID is already active in the NetBackup media catalog on this server Media ID is not in the Media Manager volume configuration Fatal tape manager bptm error occurred Total image was not obtained from Phase 1 of import Recommended Action 1 Check the NetBackup Problems report to find the exact cause of the failure 2 Try the following Ifthe media ID is already active duplicate all images on the original media ID to another volume Then manually expire the original media and redo the import 126 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Ifthe media ID is not present in
399. intended for the platform on which you are installing 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 ina DOWN drive in a robot Or the slot that should contain the volume is empty Recommended Action Ifvolume is ina DOWN drive remove it and place it in its designated slot Then retry the restore Ifthe volume is in the wrong slot use a robot inventory option to reconcile the contents of the robot with the Media Manager volume configuration NetBackup Status Code 165 Message NB image database contains no image fragments for requested backup id copy number Explanation A restore was attempted and NetBackup has no record of fragments associated with the backup ID that has the files Recommended Action Check the NetBackup Problems report for additional information about the error For detailed troubleshooting information create a debug log directory for either bpdm or bptm whichever applies and retry the operation Check the resulting debug log Chapter 4 NetBackup Status Codes and Messages 121 yr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 166 Message backups are not allowed to span media Explanation An end of media EOM was encountered while the backup image was being writt
400. interface output for the cause of the initial optical disk format failure Resolve the situation based on the error provided and use the tpformat command interface to format any remaining optical disks Format Optical Status Code 13 Message tpformat No media present in drive or robot slot Explanation The format optical disk command tpformat was interrupted because no media was found in the drive or robotic slot Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Resubmit the request and observe the Device Monitor for standalone optical mount requests servicing them as needed and look for pending requests indicating reasons for the optical mount not being satisfied a 312 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Management Status Codes These status codes appear in exit status and command output for the lt id tpclean tpreq and tpunmount commands and in system or debug logs These codes are also presented by program
401. ion 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 TAR32 is part of NetBackup for Windows NT 2000 and serves the same purpose as NetBackup tar on UNIX The server processes are the same as described for UNIX Server Windows NT 2000 Client For details on the server processes NetBacku see Backups and Archives UNIX p OO User Interface Clients earlier in this chapter Request C newn gt BPINETD Ns a Client Disk gt 436 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 Netwa
402. ion directory is either missing or inaccessible Explanation This error occurs when a vault job cannot access the following UNIX usr openv netbackup vault sessions Windows install_path NetBackup vault sessions This directory is created when vault is installed Recommended Action Make sure you are running on the master server where vault is installed and configured Also ensure that no one has accidently removed the sessions directory or changed permission on the directory path so it is inaccessible to the vault job NetBackup Status Code 269 Message no vault session id was found Explanation This error is encountered when v1ltopmenu cannot find a sidxxx session id directory for the specified profile It means that either no vault jobs were run for this profile or that the corresponding sidxxx session id directory or directories were removed from the following directory UNIX usr openv netbackup vault sessions vault_name Windows install_path NetBackup vault sessions vault_name Recommended Action You can either specify a different profile for which vault jobs have been run or exit v1 topmenu run a vault job for the specific profile and rerun vltopmenu and select the profile NetBackup Status Code 270 Message unable to obtain process id getpid failed Explanation This error occurs when a vault process is unable to obtain its process id by means of the getpid OS system call Recommended Action Look at the system log f
403. irectory where NetBackup and Media Manager are installed C Program Files VERITAS by default Because of their importance the catalogs are backed up separately from other files as described in the NetBackup System Administrator s Guide for Windows To recover the catalogs use the bprecover command Chapter 6 Disaster Recovery 409 gt NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs install_path NetBackup bin admincmd bprecover The topics in this section explain how to use bprecover to recover NetBackup catalog backups Also see the description in the Commands appendix in the NetBackup System Administrator s Guide for Windows Note The following discussions assume that NetBackup has been reinstalled if required see Master Server Disk Recovery on page 399 Identifying the Most Recent Database Backup Caution Before you can recover the NetBackup catalogs you must know which media ID has their latest backups Without this media ID you cannot accurately recover your catalogs and your only option is to use the NetBackup import feature to import all lost backup records into your NetBackup catalogs see the NetBackup System Administrator s Guide for Windows As mentioned in the NetBackup System Administrator s Guide for Windows the best way to track media IDs for catalog backups is to configure E mail notifications w
404. is because status codes greater than 255 are not supported by all operating systems The Vault job then reports the actual status code found in stderr for example 256 as the job completion status as seen in the Activity Monitor NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action For more information on a Vault status code refer to the NetBackup Troubleshooting Guide or to the Activity Monitor s troubleshooter NetBackup Status Code 254 Message server name not found in the bp conf file Explanation This error should not occur through normal use of NetBackup Recommended Action Save all error information and call customer support NetBackup Status Code 257 Message cannot create log file Recommended Action When a vault session is started v1t run needs to create log files in the following directories UNIX usr openv netbackup vault sessions vault_name Windows install_path Netbackup vault sessions vault_name UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install path NetBackup vault sessions vault_name sidxxx where xxx is the session id Ensure that the following directory exists is writable by root and that the disk is not full UNIX usr openv netbackup vault sessions vault_name Windows install_path NetBackup vault sessions vault_name NetBacku
405. is not offline Chapter 5 Media Manager Status Codes and Messages 291 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Device Configuration Status Code 17 Message This robot type does not support multiple media types Explanation An attempt to add or update a robotic drive has failed because there are drives configured in this robotic library with a different drive type Some NetBackup robotic library types do not support multiple media types Refer to the NetBackup Release Notes or to the NetBackup Media Manager System Administrator s Guide for more information on which NetBackup robotic library types support multimedia Recommended Action 1 Configure all drives for this robotic library with the same drive type 2 Ifyou are using NetBackup BusinesServer and want a robotic library with multiple media types contact VERITAS to purchase NetBackup DataCenter Device Configuration Status Code 18 Message Invalid robot type Explanation On a request to modify the device configuration the specified robot type was invalid or it did not match the robot type for the robot associated with the specified robot number Recommended Action 1 Check the device configuration for configured robots and specify the correct robot type applicable for the device configuration information being updated 2 Examine command output if available debug logs and system
406. is not reserved by host Media Manager Status Code 133 requested host is not currently registered Media Manager Status Code 135 Requested number of drives are not configured Device Management Status Code 31 Requested operation is not supported by the robot Robotic Status Code 229 Requested slot already has cartridge Robotic Status Code 217 Requested slot contains the wrong tape Robotic Status Code 226 Requested slot does not exist in robot Robotic Status Code 228 Requested slot is empty Robotic Status Code 208 wr 388 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Requested tape in other or non configured drive Robotic Status Code 215 Requested volume is in an offline domain Robotic Status Code 239 Residence is not licensed for multihosted drive support Device Configuration Status Code 37 Robot busy cannot perform operation Robotic Status Code 223 Robot denied access to the resource Robotic Status Code 234 Robot drive number in use for this robot Device Configuration Status Code 25 Robot hardware or communication error Robotic Status Code 225 Robot has misplaced the media Robotic Status Code 236 robot host and volume group mismatch Media Manager Status Code 82 Robot media access port does not exist Robotic Status Code 2
407. ison fails the client s hostname as returned by the gethostname function on the client is used as the configured name One example of why the comparison could fail is the case where the client had changed its hostname but its new hostname is not reflected in any policies yet These comparisons are logged in the bpdbm debug log if VERBOSE is set You can determine a client s configured name by using the bpc1lntcmd command on the client For example install_path NetBackup bin bpclntcmd pn expecting response from server wind abc me com danr abc me com danr 194 133 172 3 4823 Where the first output line identifies the server to which the request is directed and the second output line is the server s response in the following order Peername of the connection to the server Configured name of the client IP address of the connection to the server Port number used in the connection When the client connects to the server it sends three names to the server browse client requesting client destination client The browse client name is used to identify the client files to list or restore from The user on the client can modify this name to restore files from another client For example on a Windows client the user can change the client name by using the client user interface see the user s guide for instructions For this to work however the administrator must also have made a corresponding change on the server
408. ist in an active policy in the configuration database NetBackup Status Code 237 the specified schedule does not exist in the specified policy NetBackup Status Code 197 the specified schedule is the wrong type for this request NetBackup Status Code 241 196 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages the TIR information is zero length NetBackup Status Code 251 the vault session directory is either missing or inaccessible NetBackup Status Code 268 there are no active policies in the configuration database NetBackup Status Code 248 there is no available MAP for ejecting NetBackup Status Code 299 there was a conflicting specification NetBackup Status Code 224 third party copy backup failure NetBackup Status Code 170 timed out connecting to client NetBackup Status Code 54 timed out connecting to server backup restore manager NetBackup Status Code 202 timed out waiting for database information NetBackup Status Code 51 timed out waiting for media manager to mount volume NetBackup Status Code 52 timed out waiting for the client backup to start NetBackup Status Code 64 Chapter 4 NetBackup Status Codes and Messages 197 NetBackup 4 5 Troubleshooting Guide for Windows Messages NetBackup 4 5 Troubleshooting Guide for Windows unable t
409. ist of those that you are backing up it may be best to back up the entire drive In addition to the other system software the Windows system directories include the registry without which it is impossible to restore the client to its original configuration If you are using a NetBackup exclude list for a client do not specify any Windows system files in that list It is not a good idea to omit executable and other files for applications such as NetBackup It is tempting to save tape by excluding these easy to reinstall files However backing up the entire application ensures that you can restore it to its exact configuration For example if you have applied software updates or patches restoring from a backup eliminates the need to reapply them thus reducing recovery time For information on how to configure scheduled backups see the NetBackup System Administrator s Guide For instructions on performing user backups and archives see the NetBackup User s Guide for Microsoft Windows Recovering the NetBackup Catalogs The NetBackup catalogs contain critical information and must be recovered before any other backups Master servers have the following NetBackup catalog files install_path NetBackup db install_path NetBackup var install_path Volmgr database Media servers have the following NetBackup catalog files install_path netbackup db media install_path netbackup var install_path volmgr database For install_path substitute the d
410. isting client backup and archive images as recorded in the images directory on the master server On a Windows NetBackup server this is the install_path Net Backup db images directory All of the above can require manual modification by the administrator if a client has multiple network connections to the server and restores from the client fail due to a connection related problem If Domain Name Services are used and the possibly unqualified name that the NetBackup client obtains through its gethostbyname network function is unknown to the Domain Name Service DNS on the master server the master server can be unable to reply to client requests Whether this situation exists depends on how the client and the server are configured If gethostbyname on the client returns host names that are not qualified to the extent that DNS on the master server can resolve them then you will encounter problems Although a possible solution is to reconfigure the client or the master server DNS hosts file this is not always desirable For this reason NetBackup provides a special file on the master server This file is install_path NetBackup db altnames host xlate 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 ke
411. ith the E mail Address global attribute This attribute causes NetBackup to specify the status and media ID in an E mail to the administrator each time a catalog backup occurs You can then check the E mail to determine the last media ID used If you know the media IDs that were used but are not sure which of them has the most recent backup use the 1 option of bprecover to list the backups on each media ID This information includes the date and time that the media was written Example 1 List by Using a Raw Device Assume the catalog backup was to tape but the Media Manager part of the catalogs was lost so Media Manager cannot control the drive In this case insert the media in an appropriate drive assume the raw device path is Tape1 Then execute the following bprecover command on the NetBackup server that has the drive bprecover 1l tpath Tapel Database Backup Information from Tapel Created 03 31 97 11 31 34 Server bphost Block Size 32768 Path IMAGE1 D apps VERITAS NetBackup db NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs IMAGE2 D apps VERITAS Volmgr database Example 2 List by Using a Media Manager Controlled Drive Assume the Media Manager part of the catalogs is intact and the backup was to a dlt tape with media ID 000001 Insert the tape into an a
412. kup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures 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 S NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Example 3 PC Clients Windows NT 2000 Master Server jupiter Macintosh pluto Client Ethernet NetWare Target mars Client Policy Client List jupiter mars pluto bp ini NetBackup Configuration 1 bp DlaniNamiesiiatd Servers servers i Server List jupiter a er rowser jupiter TPIP 3782 wt pce Client Name jupiter bprd 13720 etc services bpcd 13782 tcp bpcd bprd 13720 tcp bprd bpdbm 13721 tcp bpdbm vmd 13701 tcp vmd tl8cd 13705 tcp tl8cd odid 13706 tcp odld Preferences Folder NetBackup Folder bp con
413. kup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 a Windows platform DLT Digital linear tape or tape drive type Domain Name Service DNS A program that handles name translation for network communications drive cleaning The use of a special cleaning tape to clean the heads on a drive duplicate image A copy of a backup image eject Move media out of a robotic library encryption Provides additional security by encrypting backup data on the client This capability is available only with the NetBackup Encryption option entry and exit ports See media access port 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 Glossary 499 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows expiration volume The date and time when the physical media tape is considered to be no longer usable external media ID This is an identifier written on a media cartridge or canister to help the operator identify the volume befor
414. kup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup Exec File Restore Backup Exec 8 x Device amp Media Service Backup Exec 8 x Job Engine Backup Exec 8 x Naming Service Backup Exec 8 x Notification Server gt gt Backup Exec 8 x Server Note If the NetBackup device configuration is changed and the NetBackup Device Manager service is restarted the Backup Exec 8 x Device amp Media Service on the same host should also be restarted If the Backup Exec service is not restarted Backup Exec restore jobs may not run or some of the available drives may not be used for Backup Exec restore jobs Redirected Restores Please note the following Redirected restores are not allowed when restoring files from a combination of Backup Exec and NetBackup images When restoring from only Backup Exec images individual files cannot be restored to different paths To restore to a different path all the files must be directed to the same path The restore option Restore the file using a temporary filename is not available when restoring from Backup Exec images or from a combination of both Backup Exec and NetBackup images For Backup Exec images the following kinds of redirected restores are supported Backups of a Windows client to the same or a different Windows client Backups of a Windows client to a d
415. l number If the serial numbers are different delete the robot on one of the hosts and re run device discovery there Fatal Global Database consistency error drive SSO mismatch MyDrive0 on hosts bison and mud The global device database has at least two entries for MyDrive0 one on bison and one on mud One of these two entries states that the drive is shared Determine if MyDrive0 should be shared and look for entries that are conflicting Run tpconfig d to determine which of these hosts is incorrect Delete the drive on the host that has the incorrect data and re run device discovery on that host If neither of these hosts is incorrect according to the tpconfig d output delete the drive on both hosts and re run device discovery on both hosts Fatal Global Database consistency error serial number on drive MyDrive0 on host bison and on drive MyDrivel on host mud The global device database has found duplicate drive serial numbers on MyDrive0 on bison and on MyDrivel on mud This is probably an invalid configuration First determine if these are unique drives or if they are actually the Chapter 5 Media Manager Status Codes and Messages 301 Sr NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows same drive connected to each host If they are unique drives run tpconfig tables on bison and mud and look for the serial number for MyDrived and MyDrivel If th
416. l of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option 2 Retry the operation and examine the logs Media Manager Status Code 24 Message database already open Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows was about to open the volume database but found that it was already open Chapter 5 Media Manager Status Codes and Messages 211 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Check to see if the volume database locking mechanism is working correctly and send requests such as volume queries to vmd to see if it is functioning correctly Try stopping and starting vmd to clear the unexpectedly open file descriptor Media Manager Status Code 25 Message failed making the database directory Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows could not create the database directory folder Recommended Action Determine why the directory usr openv volmgr database UNIX or folder install_path Volmgr database Windows cannot be created On Windows check which account the NetBackup Volume Manager service is running under and compare it against the security properties of the database folder Media Manager St
417. lanation Message communications handshaking was not correct Recommended Action 1 Verify that the correct version of software is running on all servers 2 Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available 3 Retry the operation and examine the logs 4 Ensure that there are no embedded whitespaces in fields that do not allow embedded whitespace Media Manager Status Code 41 Message invalid media ID for naming mode Explanation A request to add multiple volumes with a first media ID and a media ID style failed because the media ID specified was not compatible with the media ID naming style provided Recommended Action Provide a first media ID that fits the selected style For example if the media ID style is two characters and four digits the least significant four characters in the first media ID must be digits in the range 0 to 9 Alternatively select a media ID style that fits the specified first media ID Chapter 5 Media Manager Status Codes and Messages 219 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Code 42 Message cannot connect to robotic software daemon Explanation A
418. last file is not corrupt Make sure that the file system is not full and that no one has inadvertently edited the file You can correct the problem by storing in the session last file the highest session id that has been assigned to a session for this vault If the problem persists contact customer support and send the appropriate logs NetBackup Status Code 266 Message cannot find robot vault or profile in the vault configuration Explanation The profile name or triplet robot_name vault_name profile_name specified on the vault command vltrun vlteject vltoffsitemedia or by means of vitopmenu was not found in the vault configuration Recommended Action Please rerun the command with the correct profile_name or triplet robot_name vault_name profile_name NetBackup Status Code 267 Message cannot find the local host name Explanation A vault job obtains the local host name via an OS call This error occurs when the vault job is unable to get the local host name Recommended Action Issue a hostname command at the OS command prompt See the hostname or gethostbyname man page for an explanation of the conditions that would cause it to fail Refer to the OS System Administrator Guide for more information NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 268 Message the vault sess
419. le NetBackup checks the media ID and if it also matches what should be in this slot the operation proceeds For NetBackup a wrong media ID results in a media manager found wrong tape in drive error NetBackup status code 93 Appendix A Functional Overview 45 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Figure 15 Barcode Request Storage NetBackup User Device management Migrator utility J Request media ID Volume Database ia ID media ID Media management utility Robot inventory request or inject eject 2 What is Barcode Mount barcode tape s Tape Library TL8 456 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Media Manager Components Media Manager Directories and Files Figure 16 shows the file and directory structure for Media Manager on a UNIX server A Windows NetBackup server has equivalent files and directories that are located in the directory where NetBackup is installed C Program Files Veritas by default Table 8 describes the directories and files that are of special interest Figure 16 Media Manager Directories and Files usr openv volmgr bin database debug help
420. le does not exist 2 The file is for a different version of NetBackup You can find what version it is for by reading the header in the file 3 The file has a corrupted licensing digest Recommended Action Download the latest external mappings files from the VERITAS support website at www veritas com Device Configuration Status Code 3 Message The external_drive_mappings file has invalid license info Explanation The problem concerns one of the following files usr openv share external drive mappings txt UNIX install_path VERITAS NetBackup share external drive mappings txt Windows 1 The file does not exist 2 The file is for a different version of NetBackup You can find what version it is for by reading the header in the file 3 The file has a corrupted licensing digest Recommended Action Download the latest external mappings files from the VERITAS support website at www veritas com Device Configuration Status Code 4 Message The global device database version is incompatible Explanation The Device Configuration wizard is trying to store the global device information on a server that is at the wrong NetBackup server level Recommended Action Choose a NetBackup server on which to store the global device information that is running at the same Netbackup version as that used on the host where the device discovery process was executed Device Configuration Status Code 5 Message Cannot synchronize g
421. le on the client NetBackup Status Code 198 Message no active policies contain schedules of the requested type for this client Explanation A user backup or archive has been requested and this client is not ina policy that has a user backup or archive schedule Recommended Action Determine if the client is in any policy that has a schedule of the appropriate type either user backup or archive Ifthe client is in such a policy check the general policy attributes to verify that the policy is set to active NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Ifthe client is not in such a policy either add a schedule of the appropriate type to an existing policy that has this client or create a new policy that has this client and a schedule of the appropriate type NetBackup 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 policy that has a user backup or archive schedule with an open backup window This error implies that there is an appropriate policy and schedule combination for this client Recommended Action Determine the policies to which this client belongs that also have a schedule of the appropriate type either user backup or archive If possible retry the operation when the backup wi
422. lease verify Explanation On a request to mount media no media was found in the targeted location before a designated time period had elapsed Recommended Action Resubmit the request and mount the media in the targeted drive before the designated time period has elapsed Check the device configuration to ensure that the correct drive name has been configured and that 1t id the device daemon was restarted after the last device configuration change was made NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Management Status Code 62 Message Drive not available in library for mount request Explanation A mount request has been canceled because no drive is available All compatible drives may be DOWN or oversubscribed due to other active mount requests Recommended Action Investigate device availability and scheduling drive utilization of applications requesting drive resources Under some conditions mount requests will be canceled so that they can be reissued at a later time when compatible drive resources are available Device Management Status Code 63 Message Request terminated because mount requests are disabled Explanation A mount request was canceled because it cannot be satisfied Recommended Action Examine command output if available debug logs and system logs for messages related to t
423. led You can execute bprecover from either the master or media server by specifying the correct destination host with the bprecover dhost option Chapter 6 Disaster Recovery 405 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Client System Disk Recovery Windows Client System Disk Recovery Windows The following procedure explains how to perform a total recovery of a Windows 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 This procedure assumes that the Windows operating system and NetBackup must be reinstalled in order to boot the system and perform a restore Assumptions The NetBackup client was running one of the following Windows NT Server or Workstation 4 0 or above or Windows 2000 Windows 98 or 95 software The NetBackup client was backed up with version 3 0 or later NetBackup client and server software The NetBackup master server to which the client sent its backups is operational This is the server from which you will be requesting the restore The backups included the directory where the operating system and therefore the registry resided typically C winnt40 on Windows NT and C Windows on Windows 98 or 95 If the back
424. led by signal Explanation A robotic operation was canceled by an unexpected signal or event Recommended Action 1 Examine system and debug logs for a more detailed message error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services b Retry the operation and examine the logs Ensure that the robotic process is allowed to fully complete Chapter 5 Media Manager Status Codes and Messages 34430 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 Check vendor or operating system administrative interfaces and logs to see if robotic commands are being canceled Robotic Status Code 212 Message Process killed by parent Explanation A robotic operation was canceled because it either did not return with a status before a designated time period had elapsed or communications hardware errors led to the need to reinitialize the device Recommended Action 1 Stop any robot test utilities that may be running since they have the lock on the robotic device when they are active and can block other requests 2 Check to see whether the robotic device is still functioning 3 Check whether excessive hardware or communication problems have delayed the completion of a robotic command 4 Usea robot test utility to send commands
425. les NetBackup Status Code NetBackup Status Code 9 Message an extension package is needed but was not installed Explanation A NetBackup extension product is required in order to perform the requested operation Recommended Action Install the required extension product NetBackup Status Code 10 Message allocation failed Explanation Allocation of system memory failed because there is insufficient system memory available This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory Recommended Action Free up memory by terminating unneeded processes that consume memory Add more swap space or physical memory Chapter 4 NetBackup Status Codes and Messages 59 ON NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 11 Message system call failed Explanation A system call failed This status code is used for a generic system call failure that does not have its own status code Recommended Action 1 Check the All Log Entries and Problems reports to determine which system call failed and other information about the error 2 For NetBackup ServerFree Agent The file system specified as a frozen image source is not mounted In this case you may see the following in the usr openv netbackup logs bpbkar log 17 12 51 bpbkar FTL frozen image processing failed status
426. leshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages NetBackup System Administrator s Guide If there is a mapping try to set the mapped locale on the host that was specified in the NB Java login dialog This system may not be configured properly NetBackup Status Code 577 Message Can not connect to the NB Java user service via VNETD on host on port configured_port_number Explanation None Recommended Action None Messages This section lists the NetBackup error messages alphabetically The status code is included in parentheses after the message Refer to the previous list of status codes for explanations and recommended actions usr openv netbackup bp conf not found NetBackup Status Code 110 a protocol error has occurred NetBackup Status Code 232 access to server backup restore manager denied NetBackup Status Code 206 access to the client was not allowed NetBackup Status Code 59 a child process failed for an unknown reason NetBackup Status Code 258 afs dfs command failed NetBackup Status Code 78 Chapter 4 NetBackup Status Codes and Messages 1733 e NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages allocation failed NetBackup Status Code 10 all volumes are not available to eject NetBackup Status Code 297 an entry in the filelist expanded to too many
427. lid robot coord1 Explanation A requested operation encountered a missing or out of range robot slot number or a move by volume group residence was attempted when the volume had not originated from a valid robotic library slot Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify a slot number robot coordinate 1 where required ensuring that it is within the allowable range of slot numbers for the given robot type Media Manager Status Code 17 Message invalid robot coord2 Explanation A requested operation encountered a missing or invalid robot coordinate 2 used for the optical platter side or a move by volume group residence was attempted when the volume had not been previously associated with a valid robot coordinate 2 optical platter side Recommended Action 1 Examine command output if available and debug logs for a more detailed message o
428. lobal device database NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation There was a failed request to synchronize the global device database with the local drive lt idevs or robot robotic_def databases This could be caused by the Media Manager volume daemon NetBackup Volume Manager Service not running on the global device database host This could also be caused by conflicting information between the global device database and the local databases mentioned above Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders including the tpcommand log Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify that vmd is running on the global device database host 3 Examine the device configurations of other hosts sharing the same global device database looking for conflicts such as duplicate robot numbers with conflicting robot types Device Configuration Status Code 6 Message Robot type is not supported on this platform Explanation A request was made
429. local host names on the configuration request Device Configuration Status Code 39 Message Adding this drive would exceed the maximum allowed Explanation On a request to add a drive to the device configuration the licensed limit for the maximum number of drives was reached on the targeted host Chapter 5 Media Manager Status Codes and Messages 297 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Check product documentation for supported device configurations Obtain an additional software license that allows more drives to be configured or limit the configuration to the number of drives allowed by the current licensing Device Configuration Status Code 40 Message Adding this device would exceed the maximum allowed Explanation On a request to add a robot to the device configuration the licensed limit for the maximum number of robots was reached on the targeted host Recommended Action Check product documentation for supported device configurations Obtain an additional software license that allows more robots to be configured or limit the configuration to the number of robots allowed by the current licensing Device Configuration Status Code 41 Message Cannot change terminal mode Explanation A system call failed when an attempt was made to change the mode for terminal input between cooked and raw Recommended Action Exam
430. lone mirror removing 64 Communications problems PC clients 21 compression device 15 config file 450 Configuration database 450 configuration device file does not exist 15 Configuration problems 11 Daemons Media Manager 458 NetBackup 441 robotic 451 robotic control 451 Database directory Media Manager 458 Database extension 419 Databases Media Manager device 458 volume 458 NetBackup backup process 430 description 450 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows db directory NetBackup 440 debug level 48 53 debug logs 44 53 NetBackup 458 vmd 458 Define the problem 1 Device configuration problems 12 Device database 458 Directory structure Media Manager 457 NetBackup UNIX client server 439 Disaster recovery 399 Disk recovery master when NT intact 399 media server 405 NT client 406 NT master server 399 total on master 402 DNS see Domain Name Service Domain Name Service hostnames 469 drive drive limit exceeded 14 type not determined 15 drive_mount_notify script 453 drive_unmount_notify script 453 driver directory 458 drives too many 13 Duration to Retain Logs 45 Error codes see Status codes Error database 450 evaluation license key 76 Event viewer logging option 49 exception errors in Java Admin interface 51 exclude_list UNIX client 440 expired license key 76 Extended Frozen Image Service
431. ls Accessibility NetBackup contains features that make the user interface easier to use by people who are visually impaired and by people who have limited dexterity Accessibility features include Support for assistive technologies such as screen readers and voice input Windows servers only Support for keyboard mouseless navigation using accelerator keys and mnemonic keys For more information see the NetBackup system administrator s guide 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 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Conventions Table 1 Typographic Conventions continued Typeface Usage Fixed width Paths commands filenames or output For example The default installation directory is opt VRTSxx Italics Book titles new terms or used for emphasis For example Do not ignore cautions Sans serif italics Placeholder text or variables For example Replace filename with the name of your file Serif no italics Graphical user interface GUI objects such as fields menu choices etc For example Enter your password in the Password field Notes and Cautions Note This is a Not
432. lt 2 gt open BE restore connection tempDirectory 16 11 00 580 2540 3248 lt 2 gt open BE restore connection mountDatabase 0 16 11 00 580 2540 3248 lt 2 gt open BE restore connection bePathByteCount 19 16 11 00 580 2540 3248 lt 2 gt open BE restore connection beRedirectionPath mediahost dell_2 is the name of the media server that contains the Backup Exec catalogs corresponding to the image of destination_client adaj The NetBackup image has a keyword 22 which is the Backup Exec backupset number on the Backup Exec media having a Media Manager media ID of BE0001 Appendix D Backup Exec Tape Reader for NetBackup NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs bpcd will be launched on host dell_2 and will launch bptm to obtain the ADAMM GUID corresponding to Media Manager media ID BE0001 This can be seen in the bpcd debug log on the media server host for text such as the following 16 11 00 950 1660 3324 lt 2 gt bpcd main BPCD RESTORE IMAGE FILES RQST 16 11 00 960 1660 3324 lt 2 gt bpcd_ restore _ image files browse_client adaj 16 11 00 960 1660 3324 lt 2 gt bpcd_ restore _ image files requesting client adaj 16 11 00 960 1660 3324 lt 2 gt bpcd_ restore image files destination_client adaj 16 11 00 960 1660 3324 lt 2 gt bpcd_restore image files client _type 13 16 11 00 9
433. lue for roboticpath There is also an optional parameter that specifies the device file path for the drive s so that SCSI unloading of the drive s can be done with this utility Usage is install_path lt p port b bus t target 1 lan r roboticpath gt where roboticpath is the changer name eg Changer0 we 472 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup Exec Tape Reader for NetBackup D Overview This chapter explains problems that can occur when browsing or restoring from Backup Exec media For the procedures for restoring files backed up by Backup Exec see the Using the Backup Exec Tape Reader Option appendix in the NetBackup DataCenter System Administrator s Guide or the NetBackup BusinessServer System Administrator s Guide beconv Error Messages The Backup Exec catalog converter utility beconv writes debugging information to the NetBackup debug logs in the admin folder The cause of a problem can be determined by examining the debug logs This section describes the error messages specific to beconv These messages are not related to Media Manager or NetBackup status codes Message Unable to connect to the Backup Exec engine on the local host Explanation Backup Exec services are not running on the host on which beconv is being run Recommended Action Check whether the Backup Exec se
434. ly termed the Media Manager host or volume database host and defaults to the local system in some user interfaces such as vmadm Possible causes for the error are high network load missing operating system patches or service packs or unexpected vmd process failure Media Manager Status Code 72 Message failed receiving from vmd Explanation An attempt to read data from a vmd socket failed vmd is the Media Manager volume daemon UNIX or NetBackup Volume Manager service Windows Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 Identify the system where vmd is running This is usually termed the Media Manager host or volume database host and defaults to the local system in some user interfaces such as vmadm Possible causes for the error are high network load missing operating system patches or service packs or unexpected vmd process failure Also
435. m administrative interfaces for these types of robotic libraries Drives in optical disk libraries cannot be cleaned using cleaning media Device Management Status Code 52 Message No robot is defined of this type Explanation On internal communications between a robotic daemon process and 1tid the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows no robots of the expected type were found actively configured Recommended Action Display the running robotic processes to see if processes from a previous configuration are still running If any are found terminate them Check the installed software components and verify that they are all at a compatible release version Device Management Status Code 53 Message Request has been queued Cancel to clear message Explanation A mount request or drive related operation was queued because drive resources were in use Recommended Action Wait until the drive resources become available or cancel pending mount requests as needed Device Management Status Code 54 Message Block device name for optical disk is not a block device Explanation On an optical mount request the configured optical disk drive block device file was not a block special device Recommended Action Refer to the appropriate chapter in the NetBackup Device Configuration Guide use only the recommended device files for optical devices and check to ensure that the specified device nam
436. m and bpdbm On Windows clients bpbkar On other clients bpcd Note To increase the amount of information included in the logs see Debug Logs on PC Clients on page 46 NetBackup Status Code 250 Message the image was not created with TIR information Explanation This is an internal error and should not be seen by customers Recommended Action Obtain detailed troubleshooting information by creating debug logs for bptm and bpdbm on the server Then retry the operation and check the resulting debug logs NetBackup Status Code 251 Message the TIR information is zero length Explanation For a true image backup the client sent no file information to the master server NetBackup discovered this condition when it attempted to write the TIR information to media Recommended Action 1 Check the file list for the policy 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 debug logs for bptm and bpdbm on the server Then retry the operation and check the resulting debug logs NetBackup Status Code 252 Message the error status has been written to stderr Explanation If a Vault job fails with a status code greater than 255 it exits with status 252 the actual Vault status code is written to stderr This
437. m 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 If you still have a problem go to the next step in the procedure Also alter your approach based on your specific configuration and what you have already tried There are three troubleshooting procedures Preliminary Troubleshooting Troubleshooting Installation and Configuration Problems General Test and Troubleshooting Procedures Start with Preliminary Troubleshooting This explains what to check first and then branches off to other procedures as appropriate Troubleshooting Installation and Configuration Problems applies specifically to installation and configuration problems General Test and Troubleshooting Procedures defines general methods for finding server and client problems and should be used last 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 Preliminary Troubleshooting If you are having problems with NetBackup perform this procedure first NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Preliminary Troubleshooting 1 Ensure t
438. me group but still physically reside in the robot or in the robotic MAP To solve this problem do one of the following Manually remove any media that are in the offsite vault volume group but are still in the robotic library Inventory the robotic library This puts any media that were in the offsite vault volume group back into the robotic volume group Then rerun the vault sessions that failed NetBackup Status Code 294 Message Database backup failed Explanation The catalog backup step failed during a vault job Recommended Action For detailed information about why the process failed review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install _path NetBackup logs vault Also review the detail 1og in each of the sidxxx directories that had problems to find the actual problem that caused the catalog backup bpbackupdb to fail UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx ww 160 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes where xxx is the session id Correct the problem and rerun the vault job NetBackup Status Code 295 Message eject process could not obtain information about the robot Explanation This error occurs when the eject process cannot collec
439. me throughout your NetBackup configuration 26 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures a On NetBackup servers check the services files to ensure that they have entries for bpcdand bprd vmd bpdbm Processes for configured robots for example t18cd See the Media Manager System Administrator s Guide for Windows for a list of these processes On Windows the services file is sSystemRoot system32 drivers etc services b On Windows and NetWare clients verify the NetBackup Client and NetBackup Request service port numbers On Microsoft Windows clients verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog match the settings in the services file To display this dialog start the Backup Archive and Restore interface on the client and click NetBackup Client Properties on the File menu The values on the Network tab are written to the services file when the NetBackup Client service starts The services file is located in sSystemRoot system32 drivers etc services Windows NT 2000 Cc Windows services Windows 98 and 95 On NetWare clients check the BPCD and BPRD entries in the openv netback bp ini file c On Macintosh clients check
440. mental backup It must be one of these Recommended Action Specify only full or incremental schedules for manual backups If one does not exist in the policy create one NetBackup 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 NetBackup Status Code 243 Message the client is not in the configuration Explanation The specified client name was not in the catalog Recommended Action Either correct the client name or add the client to the desired policy NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 244 Message main bpsched is already running Explanation A bpsched process tried to become the main backup scheduler but another process is currently in this mode Recommended Action None NetBackup Status Code 245 Message the specified policy is not of the correct client type Explanation A user backup specified a policy that is not the type required for the client Recommended Action Retry the operation by specifying a policy that is the corr
441. mmand output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify the integrity of the device and media and check the system device files for correctness according to the NetBackup Device Configuration Guide Investigate robotic errors and determine whether mount requests are being canceled by the administrator wr 310 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Format Optical Status Code 10 Message tpformat Invalid robot Explanation The format optical disk command tpformat could not find a valid specified robot in the device configuration Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Che
442. mmended Action Chapter 5 Media Manager Status Codes and Messages 313 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather output from the ipcs a command to see what resources are currently in use Device Management Status Code 4 Message Error in Receiving Operator Message Explanation An attempt was made to receive a message from 1t id the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows on an already existing internal message queue used for inter process communication But an error was encountered in the message communications The error probably indicates a lack of system resources for message queues Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the
443. mmended Action 1 For additional information check the following NetBackup Problems report Event Viewer Application log 2 Typically this status code indicates a drive configuration problem that allows more than one process at a time to open the device On Windows the problem could be that the Media Manager device configuration was modified but the NetBackup Device Manager service was not restarted Verify the configuration and restart the NetBackup Device Manager service 3 Make sure the tapes are not write protected 4 For detailed troubleshooting information Chapter 4 NetBackup Status Codes and Messages 99 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes a Create a debug log directory for bpdm if the device is disk or bptm if the device is tape b On Windows enable verbose logging by adding VERBOSE on a line by itself in the install_path Volmgr vm conf file Then stop and restart the NetBackup Device Manager service c Retry the operation and check the resulting debug log files d On Windows systems look at the install_path Veritas NetBackup db media errors log for a drive that is frequently producing errors NetBackup 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 For
444. mmended Action Check the NetBackup Problems report to determine the reason for the failure The most common cause is that the NetBackup Device Manager service on Windows is not running Start it if necessary NetBackup Status Code 99 Message NDMP backup failure Explanation None of the paths in your NDMP policy file list was backed up successfully Recommended Action Check the NetBackup All Log Entries report for more information A possible cause for this error is that none of the backup paths exist on the NDMP host NetBackup Status Code 100 Message system error occurred while processing user command Explanation A system call failed in bparchive bpbackup bplist or bprestore Recommended Action 1 Enable debug logging for bparchive bpbackup bplist or bprestore as appropriate by creating debug log directories for them 2 Retry the operation and check the resulting logs Chapter 4 NetBackup Status Codes and Messages 107 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows If the logs do not reveal the problem use the command line version of the command and correct any problems that are reported on stderr NetBackup Status Code NetBackup Status Code 102 Message failed closing mail pipe Explanation The process that sends mail could not close the pipe to the server Recommended Action Verify that mail is configured on the client For detail
445. mware Level Listed as Drive Models Tested in the VERITAS Device Compatibility Lists at www support veritas com Chapter 1 Introduction NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Problem Report Information What were you attempting when the problem occurred for example a backup on a Windows client What were the error indications for example status code error dialog box 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 debug logs Event Viewer Application logs Windows Can you communicate with us through any of the following ___ ftp telnet email fax lt 6 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Procedures 2 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 proble
446. n 1 Create a bpcd debug log directory on the client on a Macintosh NetBackup creates the log automatically Increase the debug or log level as explained in the debug log topics in Chapter 3 On a Windows client create a tar debug log directory Retry the operation Check the resulting debug logs for the parameters passed to tar and call customer support NetBackup Status Code 186 Message tar received no data Chapter 4 NetBackup Status Codes and Messages 129 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation The media manager did not send data to tar Recommended Action 1 Retry the operation and check the status 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 debug log on the server b Ona Windows client create a tar debug log c Retry the operation and check the resulting debug logs NetBackup Status Code 189 Message the server is not allowed to write to the client s filesystems Explanation The client is not allowing writes from the server Recommended Action Perform the following to perform restores or install software from the server Ona Microsoft Windows or NetWare nontarget client select Allow server directed resto
447. n 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 policy configuration on the master server The General tab in the NetBackup Client Properties dialog box and the Clients tab in the Specify NetBackup Machines dialog box on Microsoft Windows and NetWare nontarget clients To display these dialog boxes start the Backup Chapter 4 NetBackup Status Codes and Messages 8 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Archive and Restore interface on the client For the General tab click NetBackup Client Properties on the File menu for Clients tab click Specify NetBackup Machines on the File menu The bp conf file on Macintosh clients The bp ini file on OS 2 and NetWare target clients 2 On clients and servers verify that the name service is set up to correctly resolve the NetBackup client names NetBackup Status Code 49 Message client did not start Explanation The client failed to start up correctly Recommended Action 1 Verify that software is installed on the client and it is the correct version If necessary reinstall the client software 2 Check for full file systems on the client 3 Enable detailed debug logging on the client Create bpcd and bpbkar Windows only debug log directories Increase the debug o
448. n error condition because Backup Exec media will only be mounted on the local host Such Backup Exec media should only be assigned to the local NetBackup media server Recommended Action Examine the Media Manager volume record and determine to which media server it is assigned There is no direct method to obtain the assigned media server other than by checking all media servers The status field in the volume record indicates the application owner If it does not need to be assigned to that media server manually expire the media and run beconv again Caution Do not unassign media in Media Manager Unassigning volumes in Media Manager may lead to inconsistencies between the application media database and the Media Manager volume database leading to possible data loss Message A mismatch between media type and robot type detected Explanation This happens when beconv associates Backup Exec media with a volume record in the Media Manager volume database either by a barcode or GUID match but the robot type of the record does not have a drive available to match the media type of the Backup Exec media For example The Backup Exec ADAMM database says that Backup Exec media BE Media having barcode EFG00 media type dlt is in Backup Exec robot Exabyte 210 Backup Exec robot Exabyte 210 corresponds to Media Manager robot tld 0 The Media Manager volume database for robot tld 0 contains a media record EFG000 having barcode EFG00 media
449. n if available b Retry the operation and examine the logs 2 On the UNIX host where the request originated check the system user configuration and ensure that add change pool requests include only valid user IDs No validation is attempted for user IDs in volume pools on Windows Chapter 5 Media Manager Status Codes and Messages 21 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Code 100 Message the requested slot is empty Explanation A request was made to validate update the barcode for a volume and information from the robot indicated that there was no volume in the robot that used the requested slot for its home location Recommended Action The volume configuration is not consistent with the physical contents of the robotic library that is associated with the volume The volume configuration or media placement in the robotic library needs to be adjusted using one of the media management interfaces Update validate barcode requests are made for each volume affected whenever a volume configuration is added or changed Volume entries are still changed when the update validate step fails so administrative steps are required to ensure that volume entries are defined only for media slots in the library where the correct media resides For media located in drives at the time the update validate barcode is tried the robotic informa
450. n a network For example network load affects performance verb Copy data to internal memory For example load the installation program verb Used to indicate tape drive initialization done when new media is being added logs Files where a computer or application records information about its activities mailslot See media access port man pages Online documentation provided with UNIX computer systems and applications Master and media server cluster A NetBackup master server and the remote media servers that it is using for additional storage It is possible to configure clusters only with NetBackup DataCenter servers NetBackup BusinesServer supports only a single server the master Master of Masters A NetBackup host where Global Data Manager software is installed When logging into this host the interface has a tree view where the administrator can view and administer multiple master servers master server The NetBackup server that provides administration and control for backups and restores for all clients and servers in a master and media server cluster NetBackup BusinesServer supports only a single server and it is the master 54 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows media Physical magnetic tapes optical disks or magnetic disks where data are stored media access port A slot or ot
451. n configuration the AUTHORIZATION_REQUIRED entry and SERVER entries 4 If an authentication problem rather than a configuration issue is suspected do the following a Ensure that the authentication libraries exist Windows install_path NetBackup lib libvopie dll install_path Net Backup 1lib libnoauth d11l UNIX except HP UX usr openv 1lib libvopie so usr openv 1ib libnoauth so UNIX HP UX only usr openv lib libvopie sl usr openv 1lib libnoauth s1l b Check the methods_allow txt files on the systems that are having problems to ensure that authentication is enabled The files are in the following locations Windows install_path NetBackup var auth UNIX usr openv var auth c 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 Host A and Host B are having the problem remove Host A from the file on Host B and vice versa Retry the operation Ifthe problem still exists there are connection problems not related to authentication If connections are now successful proceed to the next step 264 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes d Execute bpauthsync vopie on the master server to resynchronize the key files on the systems On Windows install_path NetB
452. n file was not found The frozen image configuration file is created with the Frozen Image Client Configuration dialog as described in the NetBackup Configuration chapter of the NetBackup ServerFree Agent System Administrator s Guide Check the usr openv netbackup logs online_util log for the following message onlfi_process fs list_fs_ entry FTL No frozen image NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes mapping information for voll If you find this message but no fi conf open failed message the fi conf master server file was created but the frozen image source has not been specified in the file To specify a frozen image source see the instructions in the NetBackup Configuration chapter of the NetBackup ServerFree Agent System Administrator s Guide NetBackup Status Code 228 Message unable to process request Explanation An inconsistency exists in the catalog or a request was made that would be improper to satisfy Recommended Action 1 If this involves a media server verify that its server list specifies the correct master server On a Windows server the master is designated on the Servers tab in the Master Server Properties dialog To access this dialog see Using the Host Properties Window on page 40 2 For detailed troubleshooting information create
453. n in the Windows Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account The SYSTEM account cannot access network drives To back up network drives or UNC paths change the NetBackup Client service startup to log in as a user that has permission to access network drives 3 Check the All Log Entries report for clues Chapter 4 NetBackup Status Codes and Messages 95 A NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 4 Set up debug logging On Windows clients create a debug log directory for bpbkar On other PC clients except Macintosh create a debug 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 debug logs 6 On Novell systems check the following For the nontarget version of NetBackup for NetWare the backup policy type must be NetWare and the files list should include a forward slash only There should be nothing else in the files list To check the policy type and files list start Backup Policy Management and right click the name of a policy Click the Attributes tab to check the policy type click the Files tab to check the contents of the files list For the target version the backup policy type must be Sta
454. n multiple domains Explanation A robotic daemon process encountered an invalid device configuration in which drives from different domains were configured to be controlled by a single logical robot Recommended Action Display the device configuration using tpconfig dor a device configuration interface to see the robotic and drive information that is already configured Ensure that the drive addresses do not span physical domains Drives can only be Chapter 5 Media Manager Status Codes and Messages 368 T NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages configured in the same robot if they can be used with media from a single domain where the domain includes a single physical library or multiple libraries connected by a cartridge exchange or pass through mechanism Robot Error Status Code 17 Message Robotic daemon not licensed Explanation A robotic daemon process was started without the required current product license or a required database file was missing or corrupt Recommended Action 1 Check product documentation for supported device configurations 2 Obtain an additional software license that allows robots of the associated robot type to be configured or limit the configuration to robot types allowed by the current licensing Check for the existence and permissions of the external_robotics txt file in the usr openv share directory UNIX or in
455. n needs cleaning Media Manager Status Code 67 Message unable to send exit status Explanation vmd could not send the status of a requested operation to the requestor vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 Obtain the specific send or write system call failure from the debug log and investigate operating system functionality related to the failure 3 Check to see whether the command or application interface sending the request is aborting prematurely as follows enable reqlib debug logs retry the operation check the debug logs and observe application interface output Media Manager Status Code 68 Message too many volumes in volume group Explanation A request was made to add or change volumes in the volume configuration and the limit for the allowed number of volumes in a volume group was reached The limit for the number of volumes in a volume group is based on the number of volumes allowed in a particular type of robot Recommended Action Chapter 5 Media Manage
456. n or that a read error I O error occurred Recommended Action 1 Ifthe volume is in a robot that supports barcodes verify the robot contents by using a Media Manager robot inventory option 2 Ifthe volume was mounted on a nonrobotic drive verify that the correct volume was mounted and assigned 3 Check the NetBackup Problems report If a fatal read error occurred attempt the operation again using another drive if possible NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 4 If your configuration has multiple servers HBAs with access to your tape services most likely an SSO configuration make sure the SCSI Reserve Release is configured correctly For more information refer to the NetBackup SAN Shared Storage Option System Administrators Guide for UNIX and Windows NetBackup Status Code 173 Message cannot read backup header media may be corrupted Explanation When searching for a backup image to restore the tape manager bptm could not find the correct backup ID at the position on the media where NetBackup expected it to be This can indicate a drive hardware problem Recommended Action 1 Check the NetBackup Problems report for clues as to what caused the error 2 Try the restore on another drive if possible 3 For detailed troubleshooting information create a debug log directory fo
457. n the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify a robot coordinate 2 value of zero 0 for non optical media or specify either A or B to represent the platter side for optical media Media Manager Status Code 18 Message cannot allocate requested memory Explanation Allocation of system memory failed This error occurs when there is insufficient system memory available The system may have too little physical and virtual memory to handle the current load of processes Recommended Action Free up memory by terminating unneeded processes that consume a lot of memory Add more swap space or physical memory Chapter 5 Media Manager Status Codes and Messages 209 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Code 19 Message invalid volume database host Explanation A requested operation encountered a missing or invalid volume database host or a request was sent to a host running a version of the product that does not support the requested operation Recommended Action 1 Examine command output if available and debug logs f
458. n the user s guide for the client On Windows 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 Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account The SYSTEM account cannot access network drives To back up network drives or UNC paths change the NetBackup Client service startup to log in as a user that has permission to access network drives NetBackup Status Code 3 Message valid archive image produced but no files deleted due to non fatal problems Explanation The backup portion of the archive command reported problems so the files were not deleted Recommended Action Examine the status of the archive on the client to determine if you need to retry the archive after correcting the problem If the problem is not serious and the files were backed up you can manually delete the files To verify which files were backed up use the NetBackup client user interface in restore mode and browse the files in the archive zy Chapter 4 NetBackup Status Codes and Messages 57 CN NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 4 Message archive file removal failed Explanation The backup portion of the archi
459. nal Description Table 6 NetBackup Daemons and Programs continued Program Daemon Description bpdbm bpdm bphdb bpjava msvec On master servers the NetBackup database manager 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 Debug Log bpdbm log on the server On master and media servers bpdm is the disk media manager and is used when the storage unit type is a disk This program manages the transfer of images between the client and the operating system disk manager on the server to which the disk attaches Started By For each backup or restore bpbrm starts an instance of bpdm on the server with the storage unit Stopped By Completion of operation Debug Log bpdm 1og on the server On UNIX database extension clients bphdb starts the NetBackup hot database backup program see the applicable NetBackup installation guide for more information Started By Client user interface when the user starts a database backup or restore operation Stopped By Completion of operation Debug Log bphdb log on the client With NetBackup for Oracle bphdb also writes to usr openv netbackup logs obackup_tape NetBackup Java master server application program This program runs on all Net
460. nal and connected to the network 3 Create a debug log directory for the process that reported the problem and the operation Examine the resulting debug log file for detailed troubleshooting information 4 Perform Resolving Network Communication Problems on page 21 NetBackup Status Code 45 Message request attempted on a non reserved port Explanation An attempt was made to access a client from a nonreserved port Chapter 4 NetBackup Status Codes and Messages 83 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action Verify that the latest software is installed on the client and server On Windows 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 this isa NetBackup for NetWare client and has a version of NetBackup earlier than 3 0 verify that the client is in a Standard type policy On Macintosh clients check the version file in the bin folder in the NetBackup folder in the Preferences folder NetBackup Status Code 46 Message server not allowed access Explanation The server is trying to access a client but access is blocked Possible causes are The server is not listed on the client as a vali
461. nation or turn off On demand only for a storage unit 6 Verify that the NetBackup Client service has been started on the Windows NetBackup media server 7 For detailed troubleshooting information create a bpsched debug log directory on the master server and retry the operation Then check the resulting debug log NetBackup Status Code 214 Message regular bpsched is already running Explanation The NetBackup scheduler bpsched performs periodic checking of the policy and schedule configuration to determine if there are new backups due Error 214 indicates that when a new instance of NetBackup starts it finds that a scheduler process is already checking the policy and schedule configuration Recommended Action Usually no action is required for this condition However NEVER kill bpsched before doing some checking For example bpsched could be calling bpdbm NetBackup Database Manager service to clean up and compress the catalogs To determine what the running bpsched is currently doing examine the bpsched debug log on the master server If necessary enable bpsched debug logging by creating a bpsched debug log directory on the master server and retrying the operation To check for backups do the following On a Windows NetBackup master server 1 Check for active or queued backups by using the Activity monitor 2 Check for active NetBackup processes by using the Activity monitor This reveals if there are bpbrm or bptm
462. ndard and the policy files list must be formatted as follows target_name where a forward slash precedes the variable target_name To check the policy type and files list start Backup Policy Management and right click the name of a policy Click the Attributes tab to check the policy type click the Files tab to check the contents of the files list Note For the target version the following NetWare message may be another indicator of incorrect policy type this message would appear in the Novell client s bpcd log unable to connect to service scheduled access not specified Make sure the policy type is set to Standard NetBackup Status Code 72 Message the client type is incorrect in the configuration database Explanation The policy type attribute in the policy configuration indicates that the client is one type but the installed software is for another type Recommended Action Verify that the policy type attribute for the policy is correct 96 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 73 Message bpstart_notify failed 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 NetBackup Status Code 74 Message client timed out waiting
463. nded Action 1 Examine command output if available and debug logs for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Investigate the integrity of the file system and volume pool database usr openv volmgr database poolDB UNIX or install_path Volmgr database pool1DB Windows wr 256 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Media Manager Status Code 111 Message the specified pool is not empty Explanation On a request to delete a volume pool it was found that the pool was not empty or it could not be determined whether or not volumes were still associated with the specified volume pool Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry
464. ndle requests to TLH robots that are in an IBM Automated Tape Library ATL t Lhd provides the interface between the local 1t id and the robotic control t Lhed in the same manner as explained previously for t 18d Started By Starting 1t id or on UNIX independently by using the usr openv volmgr bin tlhd command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id tlhed The Tape Library Half inch Control daemon provides robotic control for a TLH robot that is in an IBM Automated Tape Library ATL in a similar manner to that which was explained previously for t18cd Started By Starting 1t id or on UNIX independently by using the usr openv volmgr bin tlhced command Stopped By Stopping 1tid or by using the tlhcd t command Debug Log All errors are logged in the system log Debug information is included if the daemon is started with the v option either by itself or through 1tid The v option is available only on UNIX Also add the VERBOSE option to the vm conf file tlmd The Tape Library Multimedia daemon is the interface between 1tid anda TLM robot that is in an ADIC Distributed AML Serv
465. ndow is open Ifthe backup window is not open during appropriate time periods adjust a backup window for a schedule in one of the policies NetBackup Status Code 200 Message scheduler found no backups due to run Explanation When checking the policy and schedule configuration the NetBackup scheduler process bpsched did not find any clients to back up This could be due to No backup time windows are open applies only to full and incremental schedules Policies are set to inactive The clients were recently backed up and are not due for another backup based on Frequency setting for the schedules Policies do not have any clients Recommended Action Usually this message can be considered informational and does not indicate a problem However if you suspect a problem 1 Examine the NetBackup All Log Entries report to see if there are any messages in addition to one indicating that the scheduler found nothing to do 2 Examine the policy configuration for all policies or the specific policy in question and determine if any of the reasons mentioned in the Explanation section above apply 3 To obtain detailed troubleshooting information create a bpsched debug log directory on the master server and retry the operation Check the resulting debug log Chapter 4 NetBackup Status Codes and Messages 133 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for
466. ndows MPX See multiplexing mtime The point in time when a UNIX or NTFS file is modified 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 Client service NetBackup Windows service that runs on clients and servers and listens for connections from NetBackup servers and clients in the network When a connection is made this service starts the necessary programs NetBackup configuration options On UNIX servers and on UNIX and Macintosh clients these settings are made in the bp conf file On NetWare target and OS 2 clients they are in the bp ini file On Windows servers and Windows clients these settings are called properties and are made through the Backup Archive and Restore interface or the Host Properties dialog in the NetBackup Administration Console NetBackup databases See catalogs NetBackup Database Manager service NetBackup Windows service that runs on the master server and manages the NetBackup internal databases called catalogs This service must be running on the master server during all NetBackup administrative operations wer 506 NetBackup Trouble
467. ndows Status Codes running slightly behind job A might attempt to create a frozen image of the snapshot mirror just before job A running slightly ahead actually creates the frozen image and gets the lock on it In this case you may see the following in the usr openv netbackup logs online_ util log 17 12 51 onlfi_ freeze FTL V MS error 11 see following messages 17 12 51 onlfi_ freeze FTL Fatal method error 17 12 51 onlfi_freeze FTL vfm_freeze method vxvm type FIM function vxvm_freeze 17 12 51 onlfi_freeze FTL V MS method error 3 see following message 17 12 51 onlfi_ freeze FTL vxvm freeze Command failed with status 11 usr sbin vxassist g rootdg snapshot vol01 Vf MSCAAu7a4Uw lt dev null gt var tmp VEMSAAAs7a4Uw 2 gt var tmp VE MSBAAt7a4Uw The job that was unable to get a lock job B in the above example fails and must be run again When using nbu_snap as a frozen image method you may have stale snapshots if status code 11 occurs with the following messages in the usr openv netbackup logs online_util log Stale snapshots are those that were not automatically deleted by nbu_snap 17 12 51 onlfi_ freeze FTL VfMS error 11 see following messages 17 12 51 onlfi_ freeze FTL Fatal method error 17 12 51 onlfi_ freeze FTL vfm_freeze method nbu_snap type FIM function nbu_snap_ freeze 17 12 51 onlfi_freeze FTL V MS method error 5 see following message 17 12 51 onl
468. necting to server backup restore manager Explanation A process on the master server timed out while trying to initiate communications with the media host can be either the master or a media server This problem can occur during a backup or restore in either a single or multiple server configuration Recommended Action Determine which activity encountered the connection timeout failure by examining the All Log Entries report for the appropriate time period If there are media servers determine if the timeout occurred between the master and a media server or if only the master was involved NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 Windows server the master is designated on the Servers tab in the Master Server Properties dialog To access this dialog see Using the Host Properties Window on page 40 3 Verify that the master server can communicate with bpcd on the host that has the storage unit
469. nfiguration Problems On NetBackup media servers NetBackup Device Manager service if the system has devices configured NetBackup Volume Manager service NetBackup Client service On NetBackup clients including NetBackup Remote Administration Consoles NetBackup Client service b Use the NetBackup Activity Monitor to see if the following Media Manager processes are running avrd automatic volume recognition Processes for all configured robots see the Media Manager System Administrator s Guide for Windows If the above processes are not running stop and then restart the NetBackup Device Manager service by using the NetBackup Activity Monitor or the Services application in the Windows Control Panel 7 Ifyou had to start any of the processes or services in the previous steps retry the operation If they are running or the problem persists go to General Test and Troubleshooting Procedures on page 16 If you cannot start any of these processes or services check the appropriate debug logs see the Using the Logs and Reports chapter for NetBackup problems When started these processes and services continue to run unless you stop them manually or there is a problem with the system Troubleshooting Installation and Configuration Problems To Resolve Installation Problems Note Before you install or use NetBackup on a Linux RedHat SuSE client verify that the inetd or xinetd service is st
470. nfigured port number This is usually caused by another process having acquired the port before the service started Recommended Action 1 Examine the NetBackup Problems and All Log Entries reports 2 Create bprd and bpdbm debug log directories and retry the operation Check the resulting logs to see the system error message resulting from the attempt If another process has the port use other system commands to determine the process Based on this research either change the port number in your services file or map or terminate the process that has acquired the port To identify a bprd or bpdbm problem look for lines similar to the following in the debug log for the respective process lt 16 gt getsockbound bind failed Address already in use 114 lt 32 gt listen_loop cannot get bound socket errno 114 lt 4 gt terminate termination begun error code 146 Similar entries can appear in the reports 3 Ifthe problem persists longer than ten minutes it is possible that it will be necessary to reboot the server NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 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
471. ng vmd with the kill command If you have to stop vmd the recommended method is to use the Terminate Media Manager Volume Daemon option on the Special menu in vmadm or the equivalent command line request vmctrldbm t Using the kill command to stop this process can leave it unable to bind to its assigned port the next time it is restarted When the socket problem has occurred the daemon debug log contains lines similar to the following unable to obtain bound socket Address already in use 125 Media Manager Status Code 59 Message daemon failed accepting connection Explanation vmd could not accept a new connection due to a system call failure vmd is the Media Manager volume daemon on UNIX and the NetBackup Volume Manager service on Windows Recommended Action Chapter 5 Media Manager Status Codes and Messages 229 w NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 Obtain the specific system call failure from the debug log and investigate operating system functionality relate
472. nject media operation returned a status indicating that an inject failure occurred Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Check to see whether the robotic library has a media access port Use the robot test utility to validate this Investigate whether the administrator or operator has canceled the inject operation Ensure that inject for LMF robot types is done only on the LMF server 2 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs Robotic Status Code 219 Message Cannot move from slot to media access port Explanation A robotic eject media operation returned a status indicating that an eject failure occurred Recommended Action 1 Check to see whether the robotic library has a media access port Use the robot test utility to validate this Investigate whether the administrator or operator has canceled the eject operation Ensure that eject for LMF robot types is done only on the LMF server When ejecting RSM media ensure th
473. not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Ensure that the process is allowed to complete Media Manager Status Code 64 Message no child process to wait for Chapter 5 Media Manager Status Codes and Messages 231 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A media management interface attempted to wait for a child process to complete but unexpectedly found that there was no such child process to wait for Recommended Action Examine interface output and debug logs for a more detailed message error 1 If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available 2 Retry the operation or try using a different media management interface and examine the logs Media Manager Status Code 65 Message volume group does not exist Explanation While processing a request a volume group could not be found within the existing volume entries in the volume database
474. nt timeout specified by the NetBackup global attribute in order to allow more time for mounting and positioning the media 3 Verify that the tape is not a cleaning tape that is configured as a regular volume 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 11 6 On Windows check the Event Viewer Application log for error messages that indicate why the tape mount did not complete NetBackup Status Code 53 Message backup restore manager failed to read the file list Explanation The backup and restore manager bpbrm could not read the list of files to back up or restore Recommended Action Verify that the server software has been installed correctly on all NetBackup servers If that is not the problem 1 Create bpbrm and bpsched debug log directories on the server 2 Ona Windows NetBackup server set the Verbose logging level option on the Universal Settings tab in the Master Server Properties dialog To display this dialog see Using the Host Properties Window on page 40 3 Retry the operation and check the resulting debug logs for detailed troubleshooting information NetBackup Status Code 54 Message timed out connecting to client Explanation The server could not complete the connection to the client The accept winsock call timed out after 60 seconds R
475. ntry to indicate the correct ACSLS Server name or DAS host name Fatal Global Database consistency error remote control host mismatch 1 on hosts bison and mud The global device database has found remote robot entries for robot 1 on hosts bison and mud but their robot control hosts did not agree Determine which host should be the controlling host Then determine which host is incorrect Delete the remote robot entry on the host that is incorrect and re run device discovery Fatal Global Database consistency error missing robot control host 1 The global device database has found a remote robot entry for robot 1 but the corresponding controlling entry could not be found Check each of the media servers in the configuration for a remote robot definition for robot 1 Delete that robot and re run device discovery there Fatal Global Database consistency error serial number 1234567 on robot 1 on host bison and on robot 2 on host mud The global device database has found duplicate robot serial numbers on robot 1 on bison and robot 2 on mud This is probably an invalid configuration First determine if these are unique robots or if they are actually the same robot connected to each host If they are unique robots run tpconfig tableson bison and mud and look for serial number 1234567 on robot 1 on bison and robot 2 on mud If these serial numbers are the same check with the robot vendor to see if it is possible to modify the seria
476. o add or update a drive in the device configuration the requested drive path was found to be in use on the targeted device host Recommended Action 1 To avoid configuring paths that are already in use use the Device Configuration wizard on supported device discovery platforms so that the drive paths are automatically configured 2 Before making configuration changes check the existing drive configuration through a device configuration interface or run tpconfig d to determine the drive paths that are already in use on the targeted device host and specify a drive path that is not already in use Device Configuration Status Code 35 Message Drive name does not exist Explanation On a request to update or delete a drive in the device configuration no drives having the specified drive name were found on the targeted device host Recommended Action Check the device configuration on the targeted device host and identify the configured drives When making drive configuration changes or deletions specify the drive name as it is configured taking care to use the proper case NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Device Configuration Status Code 36 Message lt NONE gt Explanation On a request to make a device configuration change an error occurred for which a detailed message has been displa
477. o allocate new media for backup storage unit has none available NetBackup Status Code 96 unable to determine the status of rbak NetBackup Status Code 8 unable to locate vault directory NetBackup Status Code 285 unable to mount media because its in a DOWN drive or misplaced NetBackup Status Code 164 unable to obtain process id getpid failed NetBackup Status Code 270 unable to process request NetBackup Status Code 228 unable to process request because the server resources are busy NetBackup Status Code 134 unexpected message received NetBackup Status Code 43 unimplemented error code NetBackup Status Code 276 280 unimplemented feature NetBackup Status Code 16 user id was not superuser NetBackup Status Code 140 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages user is not validated to use the server NetBackup Status Code 132 valid archive image produced but no files deleted due to non fatal problems NetBackup Status Code 3 vault configuration file not found NetBackup Status Code 259 vault internal error 260 NetBackup Status Code 260 vault internal error 261 NetBackup Status Code 261 vault internal error 262 NetBackup Status Code 262 vault internal error 286 NetBackup Status Code 286 vltCore Error NetBackup
478. o longer open Recommended Action If possible change the schedule to extend the backup window for this policy and schedule combination so it does not occur again Ifthe backup must be run use the Manual Backup command on the Policy menu in the Backup Policy Management window to perform the backup Manual backups ignore the backup window NetBackup Status Code 197 Message the specified schedule does not exist in the specified policy Explanation A user backup or archive request has specified the exact policy and schedule to use when performing a backup The policy exists but does not contain the schedule On Microsoft Windows and NetWare nontarget clients you can specify a policy or schedule on the Backups tab in the NetBackup Configuration dialog box To display this dialog box start the Backup Archive and Restore interface on the client and click Configure on the Actions menu On Macintosh clients you can specify a policy or schedule by using the bp conf options BPBACKUP_ POLICY or BPBACKUP_ SCHED On NetWare target clients you can specify a policy or schedule in the bp ini file Recommended Action 1 Check the client progress log if available to determine the policy and schedule that were specified 2 Check the configuration on the master server to determine if the schedule is valid for the policy If the schedule is not valid either add the schedule to the policy configuration or specify a valid schedu
479. o the chapter for your system type in the Media Manager Device Configuration Guide for 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 Recommended Action 1 Download a new external drive mapping file from the VERITAS support web site and try again 2 Configure the drive manually 3 Use only drives that are supported by NetBackup Message Unable to determine compression device file Chapter 2 Troubleshooting Procedures 15 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Explanation A drive has been detected without the expected compression device file used to configure that device Automatic device configuration attempts to use a device file that supports hardware data compression When multiple compression device files exist for a drive automatic device configuration cannot determine which compression device file is best It uses a non compression device file instead Recommended Action If you do not need hardware data compression no action is necessary The drive can be operated without hardware data compression If you need hardware data compression refer to the chapter for your system type in the Media Manager Device Configuration Guide for UNIX for information on configu
480. obal Data Manager interface The Dashboard enables monitoring job and drive activity on multiple master servers as well as providing alerts to problem conditions GDM Managed Server A NetBackup master server that appears as a managed master server in the left pane of the GDM Dashboard GDM Server A NetBackup master server that has the Global Data Manager license activated When logging into this host the user can monitor the activity on multiple master servers using the GDM Dashboard interface If the host has installed the Advanced Reporter option the reports show information on multiple master servers Global Data Manager GDM A separately priced option for UNIX servers that provides an interface with a tree view where the administrator can view and administer multiple master servers The server where the option is installed is called a GDM Server Global Device Database A single host that serves as the repository for global device configuration information When you install NetBackup by default the master server is configured as the global device database host GNU tar A public domain version of the UNIX tar program goodies directory A directory containing programs scripts and other files that are not formally supported GUI Graphical user interface Glossary 501 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows hard link On UNIX a hard link is a poin
481. ocess NetBackup Database Manager service This is usually a result of using software from different version levels together Recommended Action Verify that all NetBackup software is at the same version level If that is not the problem create debug log directories for bpdbm and admin Then retry the operation and examine the resulting debug logs NetBackup Status Code 226 Message the entity already exists Explanation The configuration already has an entity with the same name or definition For example you see this status if you try to add a new policy when an existing policy has the same name or definition attributes clients and so on Recommended Action Correct your request and re execute the command NetBackup Status Code 227 Message no entity was found Explanation The item requested was not in the catalog For example the entity could be a file or policy information Recommended Action 1 A common cause for this problem is a query that has no matching images Specify different parameters or options for the operation and try it again 2 For NetBackup ServerFree Agent only Check the usr openv netbackup logs online_util log on the client for the following messages onlfi_get_fsmap_info FTL usr openv netbackup fi conf open failed Errno 2 No such file or directory onlfi_process fs _ list _fs_entry FTL No frozen image mapping information for voll This indicates that the frozen image configuratio
482. ode Explanation On a tape mount request the specified access mode was invalid On Windows hosts a user without Administrator privileges made a request for NetBackup Device Manager services Recommended Action When using tpreq specify an access mode argument of r for read w for write or use the default read access mode When making requests that require NetBackup Device Manager services on Windows do so under an account with Administrator privileges Device Management Status Code 43 Message Drive is not a shared drive Explanation A shared drive or SSO related request was made for a drive but the drive was not a shared drive Recommended Action Ensure that 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows was stopped and restarted after changes were last made to the device configuration Display the device configuration using tpconfig dor other means to see the drive attributes Ensure that a license key for the Shared Storage Option is installed and has not expired Device Management Status Code 44 Message You do not have permission to create the file Explanation On a tape mount request the file name associated with the request could not be created due to directory or folder permissions Recommended Action Check for existence of a file at the file path specified If a file is found delete the file if it is not needed or resubmit the request using a different file pa
483. ode 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 Determine the client and server that had the handshake failure Ww 76 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Status Code 27 Message child process killed by signal Explanation A child of the process reporting this error was killed This can occur because the backup job was terminated or the child process was terminated by another error This problem can also occur if a NetBackup process was terminated through Task Manager or another utility Recommended Action Check the NetBackup All Log Entries report for clues on where and why the failure occurred For detailed troubleshooting information create a debug log directory for the process that you su
484. ode 249 the error status has been written to stderr NetBackup Status Code 252 the image was not created with TIR information NetBackup Status Code 250 the initiation of the vault configuration file failed NetBackup Status Code 271 the library is not ready to eject volumes NetBackup Status Code 298 the maximum number of jobs per client is set to 0 NetBackup Status Code 194 the requested operation was partially successful NetBackup Status Code 1 the requested operation was successfully completed NetBackup Status Code 0 Chapter 4 NetBackup Status Codes and Messages 195 yr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages the required storage unit is unavailable NetBackup Status Code 219 the restore failed to recover the requested files NetBackup Status Code 5 the server is not allowed to write to the client s filesystems NetBackup Status Code 189 the specified policy does not exist in the configuration database NetBackup Status Code 230 the specified policy is not active NetBackup Status Code 247 the specified policy is not of the correct client type NetBackup Status Code 245 the specified client does not exist in an active policy within the configuration database NetBackup Status Code 236 the specified client does not exist in the specified policy NetBackup Status Code 239 the specified schedule does not ex
485. of client romb exited with status 11 system call failed On Windows systems verify that there is enough room in the disk partition where NetBackup is installed 5 Verify that the system is not running out of virtual memory If virtual memory is the problem shut down unused applications or increase the amount of virtual memory To increase virtual memory on Windows a Display the Control Panel b Double click System c On the Performance tab set Virtual Memory to a higher value Chapter 4 NetBackup Status Codes and Messages 65 Y NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 6 Examine other debug logs or the status on the client 7 Ifa backup on a Windows NetBackup client fails with status code 11 and the client is using Open Transaction Manager OTM for open file management it is possible that the error was caused by the OTM cache file being full If this is the case and bpbkar debug logs are turned on a message similar to the following should appear at the end of the backup 04 28 99 11 27 56 AM 216 ERR OTM Error 0xe0001005 04 28 99 11 27 59 AM 216 INF OTM Terminate disabled for all processes 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 n
486. og and command or interface output for a more detailed message on the system error as follows Chapter 5 Media Manager Status Codes and Messages 299 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs One of the following may have occurred as described in the following steps 3 Lock file problems The device discovery process sets a lockfile in the usr openv volmgr misc UNIX or Install_path Volmgr misc Windows directory named tpac 1lock to ensure that only one instance of discovery is running on a particular host It then checks the lockfile before updating the configuration Cannot obtain lockfile The lockfile may be held by another discovery process In this case the following error is displayed another tpautoconf is already running Use standard OS process tools ps on UNIX or Task Manager on Windows to determine if another tpautoconf process is running If not delete the lockfile and re run device discovery If another tpautoconf process is running wait for it to complete before retrying Failed checking lockfile
487. ogging in to is not the same version as the NetBackup Java interface on your local host The two are therefore incompatible Recommended Action Log in to a different NetBackup remote host Upgrade the NetBackup software on either the machine specified in the login dialog or on the local host where you started the NetBackup Java interface NetBackup Status Code 516 Message Could not recognize or initialize the requested locale locale_NB Java_was_started_in Explanation This status concerns the UNIX locale configuration or Windows regional settings defined on the host that was specified in the NB Java login dialog At login the locale configuration is passed to the NB Java authentication service Status 516 is generated if the locale is not recognized or if the locale of the user service could not be initialized Recognition of a valid locale is determined by the rules in the usr openv msg conf file on UNIX and in the install_path msg 1c conf file on Windows When the locale is validated initialization of the locale in the user service s environment is attempted by means of setlocale Recommended Action On the host that was specified in the NB Java login dialog check the NetBackup configuration file mentioned above to ensure there is a mapping available for the indicated locale For information on locale configuration and mapping refer to the NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troub
488. ogs bptm log bptm cannot perform Third Party Copy for multiplexed backups send_brm_msg ERROR 20 bptm EXITING with status 20 ya 70 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes multiplexing was enabled on a third party copy backup The Third Party Copy Device offhost backup method is incompatible with multiplexing the writing of two or more concurrent backup jobs to the same storage device You must disable multiplexing for any third party copy backups If multiplexing is enabled the backup will fail The media server may not have the correct 3pc conf file entry for the client disk needed for the backup The following appears in the usr openv netbackup logs bpbkar log 14 45 00 983 EMC SYMMETRIX 14 45 00 986 child started 14 47 02 029 15822 killed 14 47 02 030 14 47 02 031 14 47 33 167 status 227 14 47 33 167 14 47 33 168 complete 15773 lt 4 gt bpmap_mm_get_devid GET DEVICE INDEX 1 601092014000 15773 lt 4 gt bpbkar child_send_keepalives keepalive pid 15822 15773 lt 4 gt bpmap_mm_get_devid keepalive child 15773 lt 4 gt bpmap_mm_get_devid DEVICE INDEX 1 15773 lt 16 gt bpmap_send_extend ERR can t obtain device id string EMC SYMMETRIX 601092014000 15773 lt 16 gt bpbkar Exit ERR bpbkar FATAL exit no entity was found 15773
489. olumes in a volume group are required to have the same residence which includes having the same robot host where robot host equivalence is defined as having the same case sensitive robot host string Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that the specified robot residence and volume group are compatible with other volumes in the volume configuration that are in the specified volume group Do not try to add volumes for a robot host using a different form of the robot host name For example acme is not the same as acme veritas com Use the same host name as that used for other volumes in the volume group If the robot host needs to be changed for volumes in a volume group use a single move volume group request available only in certain media management interfaces to move the volume group to standalone residence Then move the volume group back to the robotic residence specifying the desired robot control host that will be associated with the new volume group Media Manager Status Code 84 Message this mac
490. om another bpsched process on an internal message queue construct This error indicates a problem on the master server Chapter 4 NetBackup Status Codes and Messages 139 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Create a bpsched debug 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 debug log on the master server NetBackup Status Code 211 Message scheduler child killed by signal Explanation A backup scheduler bpsched child process which interacts with the backup restore manager bpbrm on the media host was terminated This can occur because of system administrator action Recommended Action Create a debug log directory for bpsched on the master server and retry the operation Then to determine the cause of the child termination examine the messages in the bpsched debug log NetBackup Status Code 212 Message error sending information on message queue Explanation The backup scheduler bpsched encountered an error when attempting to attach to an already existing internal message queue construct for interprocess communication This error indicates a problem on the master server Recommended Action Create a bpsched debug log directory on the master server and retry the operation Then determine the type of system failur
491. ompleted but no changes were made to the volume configuration Recommended Action 1 No action is needed unless volumes that were requested to be deleted were not in fact deleted 2 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows Chapter 5 Media Manager Status Codes and Messages 223 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Media Manager Status Code 49 Message no entries inserted Explanation An insert volume s operation completed but no volumes were added to the volume configuration Recommended Action 1 No action is needed unless volumes that were requested to be inserted were not actually inserted 2 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons serv
492. onents and verify that they are all at a compatible release version Device Management Status Code 29 Message Magic Number MisMatch Chapter 5 Media Manager Status Codes and Messages 323 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation An attempt was made to read the drive database but it was found to be of an unknown format or version The database is corrupt or there has been a mismatch of software components Recommended Action Check integrity of the drive database file 1t idevs located in the directory usr openv volmgr database UNIX or in the folder install_path Volmgr database Windows Display the device configuration to determine whether or not the database is corrupt and restore a saved copy of the database file from catalog backups or delete it and recreate the device configuration as needed Device Management Status Code 30 Message Request terminated because media id will exceed maximum mount count Explanation A mount request has been canceled because the media being requested has reached the maximum mount count associated with the media Recommended Action Replace the media or change the maximum mount count to a higher value based on site policy A media management interface can be used to view and change the maximum mounts allowed for the media Check that the number of mounts for the media is set to a reasonable valu
493. oot problems that occur when using Backup Exec file browse and restore create the following debug log directories For further information on creating these logs refer to Debug Logs in the chapter titled Using the Logs and Reports On the master server install_path NetBackup logs bprd install_path NetBackup logs bpdbm On the media server install_path NetBackup logs bptm install_path NetBackup logs bpcd Set the debug logging level to 5 Backup Exec File Browse Problems The NetBackup user interfaces and the command lines obtain Backup Exec file lists using a NetBackup internal protocol called the C_BPLIST_4_5 file list protocol To determine whether the file browse request has reached bprd check whether or not the following line appears in the bprd debug log 13 58 46 458 4132 2140 lt 2 gt process request command C_BPLIST 4 5 82 received The NetBackup user interfaces and the command lines must explicitly indicate that a list of Backup Exec files or both Backup Exec and NetBackup files are requested To determine whether the correct file list options have been specified check the bprd debug log for the following text If only Backup Exec files are requested 13 58 46 488 4132 2140 lt 2 gt fileslist client flops 524288 If both Backup Exec and NetBackup files are requested 13 58 46 488 4132 2140 lt 2 gt fileslist client flops 1048576 If the NetBackup user interfaces are being used to browse
494. ooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages database unlock operation failed Media Manager Status Code 31 database write operation wrote too few bytes Media Manager Status Code 33 database write record operation failed Media Manager Status Code 32 Device Configuration was not upgraded Device Configuration Status Code 50 device entry is not unique in global device database Media Manager Status Code 153 Device path is already in use Device Configuration Status Code 22 Devices located in multiple domains Robot Error Status Code 16 Door is open on cabinet Robotic Status Code 216 Drive being assigned is either not NDMP or on the wrong NDMP client Device Management Status Code 37 Drive does not exist in robot Robotic Status Code 213 Drive does not support pending request density Device Management Status Code 17 ww 370 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Drive index is in use by another drive Device Configuration Status Code 29 Drive is currently assigned Device Management Status Code 2 Drive is currently reserved Device Management Status Code 9 Drive is not a shared drive Device Management Status Code 43 Drive is not currently reserved for this host Device Management S
495. operations and some operations can even be performed with a script What type of server platform and operating system was involved If your site uses both master and media servers was it a master or a media server If a client was involved what type of client was it Have you ever performed the operation successfully in the past If so what is different now What is the service pack level Are you using operating system software with the latest fixes supplied especially those required for use with NetBackup Is your device firmware at a level or higher than the level at which it has been tested according to the posted device compatibility lists Record All Information As you define and troubleshoot a problem always try to capture potentially valuable information such as NetBackup progress logs NetBackup Reports NetBackup debug logs Media Manager debug logs Error or status messages in dialogs OM Check for error or status information in the Event Viewer Application log Record this information for each attempt A benefit of this approach is that you can compare the results of multiple attempts It is also useful for others at your site and for customer support in the event that you cannot solve the problem yourself The Using the Logs and Reports chapter explains the various logs gt Aber NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshoot
496. opmenu to eject the media for the session before generating the reports Reconfigure the profile to allow the eject step to be performed when the next vault session for this profile runs Disable the report generation in the profile for reports that require media to be ejected NetBackup Status Code 310 Message invalid configuration for duplication to disk Explanation This error occurs when an invalid disk storage unit is configured in the vault profile used to duplicate images to disk or when the profile is configured to create more than one copy and one of the copies is targeted for a disk storage unit The latter configuration will be prevented by the vault interface and should not occur unless the vault configuration file has been manually altered Recommended Action Ensure that a valid disk storage unit is configured in the profile by means of the duplication tab Also ensure that the vault configuration file has not been manually altered NetBackup Status Code 500 Message NB Java application server not accessible maximum number of connections exceeded Explanation Indicates that an attempted login failed because the maximum number of NetBackup Java user services has been achieved Although the number of allowed user services is very large gt 100 it is possible to reach the maximum Recommended Action Ask other users to log off this limit is not configurable NetBackup Status Code 501 Message You are not
497. or s Guide has a detailed explanation of each option and how to set it On a Windows server these options are set in the interface NetBackup client software that is installed on the clients during the installation process Do not install this directory on a media server NetBackup databases as described in Table 7 On UNIX clients this file contains a list of files and directories to exclude from scheduled backups The NetBackup System Administrator s Guide explains how to use this file Help files used by NetBackup programs These files are in ASCII format On UNIX clients this file contains a list where you can specify a subset of the exclude list to add back into scheduled backups The NetBackup System Administrator s Guide explains how to use this file Detailed debug logs for NetBackup processes You must create the necessary subdirectories in order for these log files to be written see Chapter 3Chapter 3 See Table 6 for an explanation of the processes that produce the logs NetBackup release notes in ASCII format so you can conveniently view or print them Version and release date of the software NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description NetBackup Programs and Daemons Table 6 describes the programs and daemons that provide most of the control f
498. or Windows offsite volume pool A volume pool that contains media that is to be ejected and vaulted Backup images written to an off site volume pool by an original NetBackup backup policy or by Vault s duplication feature will be ejected and vaulted More than one off site volume pool can be specified for the Eject step of a Vault profile original backup A backup image created by a backup job A single backup image or all backup images created by an Inline Tape Copy multiple copy configuration are considered original backups A backup image created by a duplication job is not an original backup outport See media access port partitions The logical partitions into which a magnetic disk is divided patch A program that corrects a problem or adds a feature to an existing release of software path length Number of characters in a pathname pathname The list of directories in the path to a destination directory or file PC clients NetBackup clients that have Microsoft Windows Macintosh or IBM OS 2 operating systems peername The name by which a computer identifies itself when establishing connections to other systems policy Defines the backup characteristics for a group of one or more clients that have similar backup requirements 508 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows
499. or a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Check to see whether the vmd or oprd process continued to run once it received the connection from the requestor Run netstat a or an equivalent socket diagnostic utility Look at the daemon debug log on the server side system and the process status of vmd oprd to see if the server process is hung up Media Manager Status Code 70 Message cannot connect to vmd on host host name NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation A process timed out while connecting to vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows or to oprd the operator request daemon process This problem can occur when a connection is attempted and the server process is not running It can also occur if the network or server is heavily loaded and has slow response time Recommended Action 1 On the host Media Manager host Device Host or volume database host where vmd is the recipient of the connection verify that the d
500. or a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify a valid volume database host on which a version of vmd the volume daemon or NetBackup Volume Manager service or operator request daemon process is running that supports the requested operation Media Manager Status Code 20 Message protocol error Explanation Message communications handshaking was not correct Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Retry the operation and examine the logs Ensure that there are no embedded whitespaces in fields that do not allow embedded whitespace NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows
501. or any unusual system problems Wait for a while and try running the process again when system resources have been freed up NetBackup Status Code 271 Message the initialization of the vault configuration file failed Explanation This error occurs when configuration initialization code fails Recommended Action Ensure that the following is accessible UNIX usr openv netbackup lib libxerces cl_4nmt so Windows install_path NetBackup lib libxerces cl_4nmt so Chapter 4 NetBackup Status Codes and Messages 155 Sa NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Status Code 272 Message execution of a vault notify script failed Explanation This error occurs when the vault process is unable to execute a vault notify script due to permissions problems or coding problems in the script or if an error is returned by the script Recommended Action Ensure that the notify script is executable and runs without errors You must debug the script by running it manually to eliminate coding errors NetBackup Status Code 273 Message invalid jobID Explanation This error should not occur Recommended Action Contact customer support and send appropriate logs NetBackup Status Code 275 Message a session is already running for this vault Explanation This error occurs when you start a session for a vault and another session is already running for thi
502. or backup archive and restore operations The explanations include what starts and stops the program or daemon and the debug log subdirectory if any where it records its activities You must create the subdirectory manually see logs in the previous table and Chapter 3Chapter 3 Table 6 NetBackup Daemons and Programs Program Description Daemon bp On UNIX clients this menu driven character based interface program has options for starting user directed backups restores and archives Started By usr openv netbackup bin bp command on the client Stopped By Exiting the interface program Debug Log usr openv netbackup logs bp on the client The debug logs for bpbackup bparchive bprestore and bplist also have information about bp activities BP NLM On NetWare target clients this is the NetWare Loadable Module that starts the client user interface Started By LOAD BP command Stopped By Choosing Quit Utility from the main menu Debug Log SYS OPENV NETBACK LOGS BP mmdayy log file on the client bpadm On a UNIX master server this administrator utility has a menu driven character based interface with options for configuring and managing NetBackup Started By usr openv netbackup bin bpadm command on the master server Stopped By Quit option from within bpadm Debug Log admin log on the server bparchive On UNIX clients this program communicates with bprd on the master server when a user s
503. ore all other files a Start the NetBackup Administration interface on the master server b Start the Backup Archive and Restore utility c Browse for restores and select the partitions that were lost d Deselect the install_path Net Backup db install_path NetBackup var and install_path Volmgr database directories see the caution above e Start the restore 10 When all partitions are restored check the debug logs in the directories created in step 5 If there are any ERR or WRN messages resolve the problems before proceeding yy Chapter 6 Disaster Recovery 401 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Master Server Disk Recovery 11 Reboot the system This replaces any files that were busy during the restore When the boot process is complete the system is restored to the state it was in at the time of the last backup Total Recovery The following procedure explains how to perform a total recovery of a NetBackup master server and assumes that Windows must be reinstalled Figure 2 illustrates the procedure Figure 2 Master Server Total Recovery overview Master Server Shark Disk to restore Load OS and reboot Install required device drivers Install NetBackup Tape Drive Install any NetBackup patches Update external mapping files Enable debug logging Stop all Ne
504. ormat could not format the optical disk because it has already been formatted Recommended Action Chapter 5 Media Manager Status Codes and Messages 309 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that the device files and optical drive library address are correct since this error may occur if the device paths or drive address was incorrectly configured Use the tpformat o overwrite option if you want to reformat the optical platter If the platter is WORM write once read many it cannot be reformatted Format Optical Status Code 8 Message tpformat Must be root Explanation The format optical disk command tpformat was run by a non root user Recommended Action Execute tpformat only as the root user Format Optical Status Code 9 Message tpformat Tape request failed Explanation The format optical disk command tpformat encountered a situation where the optical volume could not be mounted Recommended Action 1 Examine co
505. ormation Chapter 1 Introduction 3 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 havea status code or message proceed directly to NetBackup Status Codes and Messages or Media Manager Status Codes and Messages and try the corrective actions recommended there When you do not see a status code or message or the actions in NetBackup Status Codes and Messages or Media Manager Status Codes and Messages do not solve the problem try the troubleshooting procedures in the Troubleshooting Procedures chapter Those procedures describe an effective approach for isolating common problems If you don t find the solution obtain assistance by contacting customer support 4 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Problem Report Information Problem Report Information General Information Date Servers master and media Platform Types and OS Levels Product Version and Host Names Patch Levels Clients Platform Types and OS Levels Product Version and Host Names Patch Levels Devices Robotic Library and Firmware Levels Fir
506. osity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 359 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Robot Error Status Code 3 Message Error in getting shared memory Explanation A robotic daemon process was unable to get a shared memory identifier associated with a segment of shared memory that 1t id maintains 1tid is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Robot Error Status Code 4 Message Error in attaching the shared memory Explanation A robotic daemon process was unable
507. ou also know what went right Error messages are usually the vehicle for telling you something went wrong So the first thing to do is look for an error message If you don t see an error message in an interface but still suspect a problem check the reports and logs NetBackup provides extensive reporting and logging facilities and these can provide an error message that points you directly to a solution The logs also show you what went right and what NetBackup was doing when the problem occurred For example a restore can be waiting for media to be mounted and the required media is currently in use for another backup The Using the Logs and Reports chapter describes the log information that NetBackup provides The NetBackup Status Codes and Messages and Media Manager Status Codes and Messages chapters provide interpretations of NetBackup and Media Manager status codes and messages NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Record All Information What Were You Trying to Do When the Problem Occurred Another important part of defining the problem is to clearly define what you were trying to do in the first place 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
508. oubleshooting Guide for Windows This script lists all volumes in the Media Manager volume configuration and augments that list with information on the volumes currently assigned to NetBackup 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 Volume has not expired or exceeded its maximum number of mounts Volume Database Host name for the device is correct If you change the Volume Database Host name stop and restart the NetBackup Device Manager service The correct host is specified for the storage unit in the NetBackup configuration The host connection should be the server master or media that has drives connected to it The Media Manager volume configuration has media in the correct volume pool and unassigned or active media is available at the required retention level Use the NetBackup Media List report to show the retention levels volume pools and status active and so on for all volumes Use the NetBackup Media Summary report to check for active volumes at the correct retention levels In some configurations the NetBackup bptm process is rejected when requesting media from the NetBackup Volume Manager service because that service cannot determine the name of the hos
509. outer system The NetBackup policy 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 Assuming that all the standard networking files for example hosts DNS WINS and routing tables are set up correctly all the required network connections can be made There would be a problem however with restoring files from pluto if the mars meteor system were a type of router that hides the name of the originating host when it routes requests between the two networks A router between an Ethernet and a token ring network exhibits this behavior To illustrate what occurs assume that pluto is on FDDI token ring and the server is on Ethernet If a user on pluto starts a restore the router could use the name of its network interface to pluto meteor as the peername when it forwards the request to the server The server interprets the request as coming from a host named meteor and does not allow the restore because meteor is not in the client list To resolve this problem the administrator creates an altnames directory on the master server and adds a file for meteor to that directory On a Windows NT 2000 NetBackup serv
510. outers bridges and other network devices are all at full duplex Usea sniffer program to determine the number of packets being rejected and or re requested On Windows systems the client bpbkar log may contain a 10054 Connection Reset Error error usually indicates a hardware error Somewhere between the NetBackup client and server the connection was reset When NetBackup receives this error it is unable to continue the backup This error has been attributed to the following A hiccup in the network A bad network interface card on a NetBackup client 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 war 68 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 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 For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Status Code 16 Me
511. ows Debug Logs Table 4 PC Client Debug Logs Debug Log NetBackup Associated Process Directory Client bpbackup Windows NT 2000 98 Backup program that is run from the 95 command line bpbkar Windows NT 2000 Backup and archive manager These logs have information on the bpbbkar32 process bpcd All Windows and NetBackup client manager These logs have NetWare clients 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 bpmount Windows NT 2000 98 Program used to collect drive names on the 95 client for multistreaming clients bprestore Windows NT 2000 98 Restore program that is run from the 95 command line bpsrv NetWare nontarget NetBackup service utility This program allows the system with the user interface to communicate with the NetBackup for NetWare client nbwin Windows 98 95 Client user interface program for Windows 98 95 nbwin Windows NT 2000 Client user interface program for Windows NT 2000 tar Windows NT 2000 tar process These logs have information about the tar32 process user ops Windows NT 2000 98 See Table 3 95 Before using the debug logs note the following For Windows clients logs are kept for the number of days specified in the Backup Archive and Restore int
512. ozen image method but a VERITAS Volume Manager snapshot mirror of the frozen image source volume had not been created prior to running the backup or if another backup is currently running that is using the snapshot mirror In either case you may see the following in the usr openv netbackup logs online_ util log 17 12 51 onlfi_ freeze FTL V MS error 11 see following messages 17 12 51 onlfi_ freeze FTL Fatal method error 17 12 51 onlfi_freeze FTL vfim_freeze method vxvm type FIM function vxvm_freeze 17 12 51 onlfi_freeze FTL V MS method error 3 see following message 17 12 51 onlfi_freeze FTL find_ready_ snapshot Cannot find available snapshot mirror As described under Creating a Snapshot Mirror of the vxvm Frozen Image Source in the NetBackup ServerFree Agent System Administrator s Guide create a snapshot mirror on the client before running the backup vxvm was selected as the frozen image method and a VERITAS Volume Manager snapshot mirror of the frozen image source volume has been created However two different backup jobs A and B attempt to back up the same volume for example vol101 but job A starts just before job B Because there is a brief pause between finding an available snapshot mirror and actually forming the frozen image of it job B Chapter 4 NetBackup Status Codes and Messages 61 eN NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Wi
513. p 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Robotic Status Code 210 Message Unable to SCSI unload drive Explanation The drive could not be unloaded The drive configuration may be incorrect and the drive may be logically DOWN Also the drive may never have become ready after media was placed in the drive Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Check for improperly configured cleaning media or interference with the drive cleaning operation Check for bad media which may have led to the drive not being able to be unloaded To avoid configuring incorrect device paths and device names which is a common root cause of drive unload problems use the Device Configuration wizard on supported device discovery platforms so that device paths and device names can be automatically configured Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the unload failure Robotic Status Code 211 Message Process kil
514. p 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 1t id 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 6 On a media server it is not necessary to start bprd because it is not used NetBackup automatically starts other required NetBackup programs when it accesses the media server Another daemon that executes on all server and clients is the NetBackup client daemon bpced On UNIX clients inetd starts bpcd automatically so no special actions are required On Windows NT clients bpinetd performs the same functions as inetd Other PC clients do not use inetd or bpinetd but are usually configured to start bpcd automatically see their user s guides for instructions There are no other daemons or programs that you must explicitly start The necessary programs are started automatically during the backup or restore operation Figure 6 shows the programs that must be running and how they are started The Media Manager functional description later in this appendix has details on the actions started by Itid we 420 NetBackup Troubl
515. p Exec UNIX client Files can only be redirected to this path For example If the agent cfg file on machine A contains the following lines export space home as space_home export homel as homel To redirect to space home dir1 the path should be specified as space_home dirl To redirect to home1 dir1 the path should be specified as home1 dirl You can only restore to paths which have been exported in the agent cfg file In the above example you could only restore to paths under space home or home1 on machine A Note When restoring Netware client backups to a UNIX client use the NetBackup Windows client interface nbwin exe NetBackup Java interface or the bprestore command The NetBackup Netware client nbnwnt exe should not be used to restore Netware client backups to UNIX clients Restoring to Netware Clients When restoring Netware client backups to Netware clients use the NetBackup Netware client nbnwnt exe To perform Backup Exec restores to a Netware machine the machine being restored to must be a NetBackup Netware client Refer to NetBackup User s Guide Novell Netware NonTarget for Microsoft Windows for restoring Netware backups to Netware clients 480 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs Troubleshooting with the Debug Logs To troublesh
516. p Status Code 258 Message a child process failed for an unknown reason Explanation A child process of the vault job died with an invalid exit status Recommended Action Contact customer support and send appropriate logs NetBackup Status Code 263 Message session id assignment failed Explanation The unique identifier to be assigned to the vault session is bad Recommended Action Verify that the session id stored in the session last file is valid UNIX usr openv netbackup vault sessions vault_name session last Chapter 4 NetBackup Status Codes and Messages 153 a NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Windows install_path Netbackup vault sessions vault_name session last Make sure that the file system is not full and that no one has inadvertently edited the session last file You can correct the problem by storing in the session last file the highest session id that has been assigned to a session for this vault If the problem persists contact customer support and send the appropriate logs NetBackup Status Code 265 Message session id file is empty or corrupt Explanation The session id stored in the following file is bad UNIX usr openv netbackup vault sessions vault_name session last Windows install _path NetBackup vault sessions vault_name session last Recommended Action Ensure that the session id stored in the session
517. p Status Code 74 client timed out waiting for the continue message from the media manager NetBackup Status Code 65 client timed out waiting for the file list NetBackup Status Code 68 client s network is unreachable NetBackup Status Code 56 wr 178 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages client server handshaking failed NetBackup Status Code 26 communication interrupted NetBackup Status Code 234 connection refused by server backup restore manager NetBackup Status Code 204 continue NetBackup Status Code 221 could not deassign media due to Media Manager error NetBackup Status Code 177 could not get group information NetBackup Status Code 38 could not get passwd information NetBackup Status Code 30 could not set group id for process NetBackup Status Code 32 could not set user id for process NetBackup Status Code 31 daemon fork failed NetBackup Status Code 148 daemon is already running NetBackup Status Code 145 Chapter 4 NetBackup Status Codes and Messages 179 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Database backup failed NetBackup Status Code 294 database system error NetBackup Status Code 220 density is incorrect for the med
518. p bprd Notes 1 The NetBackup Client Properties dialog also has a Network tab with NetBackup client service port BPCD and NetBackup request service port BPRD settings that must be the same as the bpcd and bprd settings in the services file 2 The complete path to the Windows NT 2000 etc services file is SystemRoot system32 drivers etc services 3 All other applicable network configuration must also be updated to reflect the NetBackup information For example this could include the SystemRoot system32 drivers etc hosts file and also WIN and DNS if used Chapter 2 Troubleshooting Procedures 31 gt NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures 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 32 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Example 2 Windows NT 2000 Master and Media Servers
519. pc or mover conf file exists cannot perform TPC backup 09 51 04 22281 lt 16 gt bptm unable to find or communicate with Third Party Copy mover for policy vertex _std_tpc Make sure that an appropriate mover conf file exists in usr openv netbackup on the media server This file can be any of the following mover conf policy_name file where policy_name exactly matches the name of the policy mover conf storage_unit_name where storage_unit_name exactly matches the name of the storage unit selected in the Backup Policy Management Policy attributes dialog such as nut 4mm robot t14 0 mover conf file no extention for configurations that have only one third party copy device Note that NetBackup looks for an appropriate mover conf file in the above order The SCSI pass through path of the third party copy device as entered in the mover conf file with or without file name extension does not exist In this case the usr openv netbackup logs bptm log may also show the following 09 50 12 22159 lt 16 gt setup _mover_tpc open of passthru path dev sg cXtX1X failed No such file or directory 09 50 12 22159 lt 16 gt bptm unable to find or communicate with Third Party Copy mover for policy vertex _std_tpc Correct the SCSI pass through path of the third party copy device that is entered in the mover conf file Chapter 4 NetBackup Status Codes and Messages 1233 Ar NetBackup 4 5 Troubleshooting Guide
520. pendently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1tid or by putting VERBOSE in the vm conf file acssel Available only on UNIX See the Media Manager System Administrator s Guide UNIX or Windows for details acsssi Available only on UNIX See the Media Manager System Administrator s Guide UNIX or Windows for details avrd The automatic volume recognition daemon controls automatic volume assignment and label scanning This lets Media Manager read labeled tape and optical disk volumes and to automatically assign the associated removable media to requesting processes Started By Starting 1tid or on UNIX independently by using the usr openv volmgr bin avrd command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by aborting avra and starting the daemon with the v option Appendix A Functional Overview 459 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Trou
521. plet will uniquely identify the profile in your vault configuration NetBackup Status Code 306 Message errors encountered partial success Explanation This error occurs when a vault job is partially successful in other words when not all images have been successfully duplicated and or the catalog backup failed NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action For more information review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install_path NetBackup logs vault Also review the detail 1log in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id A common cause of failure is the lack of resources such as no more media available in the specified pools for duplication and catalog backup Correct the problem and rerun the vault job Note that the NetBackup scheduler will retry a vault job that has terminated with this error NetBackup Status Code 307 Message eject process has already been run for the requested vault session Explanation This error occurs when vlteject is run to eject media for a session id for which media has already been ejected Recommended Action Rerun vltej
522. ported by NetBackup Message Drive is standalone or in unknown robot Explanation Either the drive is standalone or the drive or robot is not returning a serial number Note that some manufacturers do not support serial numbers Although automatic device configuration will not function optimally the drive or robot can be manually configured and operated without a serial number Recommended Action Ask the manufacturer for a newer firmware version that returns serial numbers if available or manually configure and 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 Although automatic device configuration will not function optimally the drive or robot can be manually configured and operated without a serial number Recommended Action Ask the manufacturer for a newer firmware version that returns serial numbers if available or manually configure and operate the drive robot without serial numbers Message Drive exceeds drive limit Explanation The NetBackup BusinesServer license allows a maximum of two drives and two drives have already been configured Recommended Action To use this drive a previously configured drive must be disabled deleted from the device configuration Message Robot exceeds robot limit Explanation A robotic library has already been
523. ports Table 2 NetBackup Reports Report Description Status of Backups Status and error information on backups and archives completed within the specified time period Media Reports Provides the following reports about the media Media Lists Shows information about volumes that NetBackup has used for backups or archives This report does not show information for disk storage units Media Contents Lists the backup IDs that are on a single volume The information is read directly from the media This report does not show information for disk storage units Images on Media Shows the contents of media as recorded in the NetBackup file database This report shows information for any type of storage unit including disk Media Logs Lists the media errors that have been recorded This information is a subset of the All Log Entries report Media Summary Summarizes active and nonactive volumes and groups them according to expiration date The report shows the expiration date and the number of volumes that are at each retention level Media Written Identifies volumes that have been used for backups or archives within the specified time period This report does not show media used for image duplication if the original image was created prior to the specified time period Client Backups Detailed information on backups and archives completed within the specified time period Problems with Problems that the server
524. ppropriate drive Then execute the following bprecover command on the NetBackup server that has the drive the NetBackup Device Manager Service must be active bprecover 1 ev 000001 d dit Database Backup Information from 000001 Created 03 31 97 05 50 51 Server bphost Block size 32768 Path IMAGE1 D apps VERITAS Netbackup db IMAGE2 D apps VERITAS Volmgr database IMAGE3 D apps VERITAS var Example 3 List Disk Path Assume the catalog backup was done to disk path D apps dbbackup and this disk has not failed Execute the following bprecover command to list the backup information bprecover l1 dpath D apps dbbackup Database Backup Information from D apps dbbackup Created 03 31 97 11 31 34 Server bphost Block size 32768 Path IMAGE1 D apps VERITAS NetBackup db IMAGE2 D apps VERITAS NetBackup var IMAGE3 D apps VERITAS Volmgr database Procedures for Recovering NetBackup Catalogs This section explains how to recover the NetBackup catalogs when all or part of them are lost You perform this recovery with the bprecover command The method required to recover the catalogs depends on Chapter 6 Disaster Recovery 411 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs The type of media that contains the backup of the NetBackup catalogs tape or magnetic disk and Whether the Media Manager part of
525. ptm found a volume loaded that did not have the expected tape header This can indicate that volumes in a robot are not in the slots indicated in the Media Manager volume configuration Recommended Action Ifthe volume is in a robot and the robot supports barcodes perform a Compare Contents with Volume Configuration The resulting report shows which media ID was found and validates its slot number with what is in the Media Manager volume configuration Then either change the physical location in the robot or change the volume configuration to show the correct slot Ifthe volume was mounted on a nonrobotic drive verify that the correct volume was mounted and assigned NetBackup Status Code 94 Message cannot position to correct image Explanation When searching for a backup image to restore the tape manager bptm did not find the correct backup ID at the expected position on the volume This can indicate a drive hardware problem Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Try the restore on another drive if possible 2 For additional information check the following NetBackup Problems report to determine the device or volume that caused the error Event Viewer Application and System logs 3 For detailed troubleshooting information create a debug log director
526. r Enabling Detailed Debug Logging in Chapter 3 3 Restart the NetBackup Java interface and examine the logs Note The error is probably the result of a system resource issue When detailed debug logging has been enabled the details may be retrieved from the bpj ava msvc or bpjava usvc log files NetBackup Status Code 513 Message bpjava msvc the client is not compatible with this server version server_version Chapter 4 NetBackup Status Codes and Messages 171 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 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 The two are therefore incompatible Recommended Action Log in to a different NetBackup remote host Upgrade the NetBackup software on either the machine specified in the login dialog or on the local host where you started the NetBackup Java interface NetBackup 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 l
527. r Status Codes and Messages 233 TO NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs Check to see if volumes are defined in the volume database associated with a slot number zero that may not exist in the robot Run a robot inventory Show contents of robot report and observe the starting slot number If the starting slot number is one 1 and there is a volume defined in the robot at slot zero 0 delete the volume entry or move it to standalone so that the remaining available media slots can be utilized Media Manager Status Code 69 Message failed sending request to vmd Explanation A request could not be sent to vmd or to oprd even though the initial connection to the server process was successful vmd is the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows and oprd is the operator request daemon process Recommended Action 1 Examine command output if available debug logs and system logs f
528. r Windows Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify a number of cleanings value within the acceptable range of 0 to 2 147 483 647 Media Manager Status Code 75 Message invalid change type Explanation An invalid volume change request was attempted Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Verify that all Media Manager and user interface binaries are at a compatible version level Media Manager Status Code 76 Message cannot get host name Explanation The system call gethostname 3C failed during an attempt to obtain the name of the local host NetBackup Troubleshooting Guide Windows N
529. r as other requests see Figure 15 The Media Manager device daemon 1t id determines the location of the requested media ID by querying the Media Manager volume daemon vmd The volume daemon then returns the information it has about the media including robot number robot type host slot and barcode 1tid includes the media ID and location information in a mount request to the robotic daemon for the robot that has the media ID This request causes the robotic daemon to query the robotic control daemon or the robot for the barcode of the tape in the designated slot This is a preliminary check to see if the correct media is in the slot The robot returns the barcode value it has in memory The robotic daemon compares this barcode with the value it received from 1t id and takes one of the following actions Ifthe barcodes don t match and the mount request is not for a NetBackup backup job the robotic daemon informs 1t id and a pending action request Misplaced Tape appears in the Device Monitor An operator must then insert the correct tape in the slot Ifthe barcodes don t match and the mount request is for a NetBackup backup job the robotic daemon informs 1t id and the mount request is canceled NetBackup bptm then selects another volume to mount Ifthe barcodes match the robotic daemon requests the robot to move the tape to a drive The robot then mounts the tape At the start of the operation the application for examp
530. r bptm and retry the operation Check the resulting debug log NetBackup Status Code 174 Message media manager system error occurred Explanation An abnormal condition occurred causing a tape manager bptm or disk manager bpdm failure This should not occur under normal circumstances Recommended Action 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 If you see the problem with only one client verify that the client binaries are correct especially those for bpcd 3 Can you read or write any other images on this media If so check the following reports for clues Images on Media report Media Contents report Chapter 4 NetBackup Status Codes and Messages 125 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 4 Verify the following The media by using the NetBackup image verify option That you are using the correct media type for the device 5 Check the Event Viewer Application log 6 For detailed debug information create a debug log directory for either bptm or bpdm whichever applies and retry the operation Check the resulting debug log NetBackup Status Code 175 Message not all requested files were restored Explanation When restor
531. r device name for optical disk is not a character device Device Management Status Code 38 child process killed by signal Media Manager Status Code 63 Control daemon connect or protocol error Robotic Status Code 224 Current version does not support remote device host Device Configuration Status Code 38 current version does not support this configuration Media Manager Status Code 149 daemon cannot obtain socket Media Manager Status Code 58 Ww 368 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages daemon failed accepting connection Media Manager Status Code 59 daemon resources are busy Media Manager Status Code 5 daemon terminated Media Manager Status Code 7 database already open Media Manager Status Code 24 database close operation failed Media Manager Status Code 23 database initialization failed Media Manager Status Code 22 database lock operation failed Media Manager Status Code 29 database open operation failed Media Manager Status Code 26 database read operation read too few bytes Media Manager Status Code 28 database read record operation failed Media Manager Status Code 27 database seek operation failed Media Manager Status Code 30 Chapter 5 Media Manager Status Codes and Messages 369 ar NetBackup 4 5 Troublesh
532. r log level as explained in the debug log topics in Chapter 3 4 Retry the operation and examine the resulting logs 5 On SGI IRIX 6 2 6 4 systems clients may be missing the 1ibdbm so shared library Refer to the SGI IRIX install CD ROM for the eoe sw dmi package NetBackup Status Code 50 Message client process aborted Explanation The client backup aborted One instance when this code appears is if a NetBackup master or media server is shut down or rebooted when a backup or restore is in process Recommended Action 1 Enable detailed debug logging Create a bpbkar debug log directory Windows only NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Create a bpcd debug log directory this log is created automatically on Macintosh clients Increase the debug or log level as explained in the debug log topics in Chapter 3 2 Retry the operation and examine the resulting logs 3 This problem can sometimes be due to a corrupt binary On a Windows client check the bpinetd exe bpcd exe bpbbkar32 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 clients or are not at the same release level or do not have the same NetBackup patches applied as other Windows clients
533. r more of the following operations duplication suspension of unvaulted media expiration of disk images execution of vlt_ejectlist_notify script catalog backup eject and or report In the event of a non fatal error Vault will attempt to complete all the steps configured in the vault profile 56 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Identify which of the above operations encountered an error by reviewing the detail log file in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id Or review the vault debug log file in the following directory UNIX usr openv netbackup logs vault Windows install_path NetBackup logs vault Correct the problem and rerun the vault job NetBackup Status Code 2 Message none of the requested files were backed up Explanation A backup or archive could not back up any of the files in the file list Recommended Action Verify that the files exist and you have read access to them Check to see if there is a trailing space on one or more of the filenames in the client s file list Remove any inadvertent trailing characters such as spaces or tabs Check the exclude list per the instructions i
534. r restore bpsched starts an instance of bpbrm on the server with the appropriate storage unit Stopped By Completion of operation Debug Log bpbrm log on the server On UNIX clients except Apollos the Backup Archive Manager generates the backup images Started By bpbrm on the server with the storage unit Stopped By Completion of operation Debug Log bpbkar 1og on the client On Windows clients the Backup Archive Manager generates the backup images Started By BPCDW32 on the client Stopped By Completion of operation Debug Log BPBKAR LOG file in the NetBackup logs directory on the client NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Daemon Description bpcd BPCD NLM BPCDW32 EXE bpdbjobs 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 For a description of the NetBackup client daemon on PC clients see BPCDW32 EXE BPCD NLM and NetBackupBPCD later in this table Started By
535. r step 4 On NetWare clients see the BPRD setting in the openv netback bp ini file Or instead of the first bullet On Windows NetBackup servers set these numbers in the Client Properties dialog box in the Configure NetBackup window see Using the Host Properties Window on page 40 6 Ona Macintosh client check NetBackup configuration settings as follows Chapter 2 Troubleshooting Procedures 23 O NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 If that does not work reinstall the software e Ensure that bpcd port number portnum in the Preferences NetBackup mac conf file is the same as on the server by default 13782 On Windows NetBackup servers check the NetBackup Client Service Port number on the Network tab in the NetBackup Client Properties dialog To display this dialog box start the Backup Archive and Restore interface on the server and click NetBackup Client
536. rator s Guide 492 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Glossary access control list ACL Security information associated with files on some file systems ACS Automated Cartridge System ACS can refer to any of the following A type of Media Manager robotic control This robot type is supported only by NetBackup DataCenter servers The StorageTek STK system for robotic control The highest level component under STK s ACS library software which refers to a specific standalone robotic library or to multiple libraries connected with a media passthru mechanism active job A job for which NetBackup is currently processing backup or restore data activity logs See debug logs activity monitor A NetBackup administration utility that displays information about NetBackup jobs and provides limited control over them administration client See remote administration console administrator A user that is granted special privileges to install configure and manage the operation of a system network or application NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows AIT Sony Advanced Intelligent Tape a type of tape drive or media type alternate client restore See redirected restore different client alt
537. re console The bprestore and bplist functions are merged into the user interface programs on the clients The NetBackup NetWare client daemon is called BPCD The NetBackup tar functions are merged into BPCD The server processes are the same as described for UNIX Server NetWare Client For details on the server processes i NetBackup see Backups and Archives UNIX i e User Interface Clients earlier in this chapter NBNW95 NetWare nontarget on 95 98 NBNWNT NetWare nontarget on NT 2000 BP on NetWare Request BPCD NetWare Client Disk Appendix A Functional Overview 437 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows 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 For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter Request A Macintosh Client NetBackup User Interface NetBackupBPRESTORE NetBackupBPCLIMAGELIST NetBackupBPLIST NetBackupListen D NetBackupBPCD Client Disk NetBackupBPRESTORE is a faceless background application that NetBackup launches in order to start a user directed restore NetBackupCLIMAG
538. rect on both the client and the server If the backup involves a media server verify that these entries are correct on both the master and media server For example if a media server does not have a server list entry for the master it does not accept connections from the master NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes On Windows the master server is designated on the Servers tab in the Master Server Properties dialog To display this dialog see Using the Host Properties Window on page 40 On 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 If you change the server list on a master server stop and restart the NetBackup Database Manager and NetBackup Request Manager services 3 Status code 40 can also be due to the operator denying a mount request NetBackup Status Code 41 Message network connection timed out Explanation The server did not receive any information from the client for too long a period of time Recommended Action 1 OnWindows clients check for the following problems with the bpbkar client process The bpbkar client process is not hung but due to the files and directories it is scanning it has not replied to the server wi
539. red in the Media Manager volume configuration Recommended Action Check the volume configuration and the NetBackup catalog backup configuration and correct any problems found NetBackup Status Code 180 Message tar was successful Chapter 4 NetBackup Status Codes and Messages 127 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation tar returned a successful exit status Recommended Action None NetBackup Status Code 181 Message tar received an invalid argument Explanation One of the parameters passed to tar was not valid Recommended Action On a Windows client create a tar debug log directory retry the operation and check the log Ona Macintosh client check the version file that is in the bin folder in the NetBackup folder in the Preferences folder If the software is not at the correct level install the correct software as explained in the installation guide NetBackup Status Code 182 Message tar received an invalid file name Explanation tar cannot write to the file that is specified with the parameter Recommended Action 1 Create a bpcd debug log directory on the client on a Macintosh NetBackup creates the log automatically 2 Ona Windows client create a tar debug log directory 3 Increase the debug or log level as explained in the debug log topics in Chapter 3 4 Rerun the operation check the result
540. red robots Appendix D Backup Exec Tape Reader for NetBackup 475 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows bephyinv Error Messages Recommended Action Do not specify the tbs option or run a NetBackup robot inventory update on the robots that contain Backup Exec media bephyinv Error Messages The Backup Exec Physical Inventory utility bephyinv logs debugging information to the NetBackup debug logs in the admin folder The exact cause of a problem can be determined by examing the debug logs For more information on bephyiny refer to the Using the Backup Exec Tape Reader Option appendix in the NetBackup DataCenter System Administrator s Guide or the NetBackup BusinessServer System Administrator s Guide Message Unable to connect to the Backup Exec engine on the local host Explanation Backup Exec services are not running on the host on which bephyinv is running Recommended Action Check whether the Backup Exec services are running The Backup Exec services are the following Backup Exec 8 x Agent Browser Backup Exec 8 x Alert Server Backup Exec 8 x Device amp Media Service Backup Exec 8 x Job Engine Backup Exec 8 x Naming Service Backup Exec 8 x Notification Server gt UO Backup Exec 8 x Server Message Volume database mismatch detected media_id XXX was obtained from volume database ABC but the drive in which it was moun
541. referably a nonrobotic drive Adda volume on the volume database host for the devices in the storage unit master server is recommended for the volume database host Ensure the volume is in the NetBackup volume pool Insert the volume in the drive If you do not prelabel the volume by using the bplabel command NetBackup automatically assigns a previously unused media ID 3 Verify that all NetBackup services are running on the master and media servers Chapter 2 Troubleshooting Procedures 19 _ 9 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures To perform this check use the Activity Monitor or the Services application in the Windows Control Panel Perform a user backup and then a restore of a file Perform these operations from a client that has been verified to work with the master server This test verifies NetBackup media server software Media Manager on the media server can mount the media and use the drive that you configured Communications between the master server process bpsched and media server processes bpcd and bpbrm Communications between media server process bpbrm and client processes bpcd and bpbkar For failures relating to drives or media ensure that the drive is in an UP state and the hardware is functioning If you suspect a communications problem between the master and media servers
542. rent ruleDB so that vmd can initialize an empty barcode rule configuration If the move rename method is used re add barcode rule entries as needed so that new media moved into the robotic library are assigned to the correct media types Media Manager Status Code 126 Message not authorized to connect to vmd Explanation A caller requesting services from vmd is either not authenticated or not authorized or a problem was encountered when two systems were attempting to authenticate one another Recommended Action 1 See the Media Manager system administrator s guides for detailed information on vmd security vmd security is based on NetBackup authentication authorization but has extensions for handling SERVER entries in the Media Manager configuration file 2 Examine the debug log files for a more detailed message on the authentication authorization problem Chapter 5 Media Manager Status Codes and Messages 263 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 3 Correct the vmd security configuration by adjusting the authenticatio
543. replace the media with other media that still has useful life remaining 3 Ifthe number of mounts was less than the maximum mounts allowed for the volume check the device configuration to determine if the volume database host for the device is consistent with the volume configuration in the volume database Applications may attempt to query multiple volume databases for volume related requests so ensure that duplicate media IDs are not used in volume configurations across multiple hosts If duplicate IDs are found either completely separate the configurations by not sharing any devices or remove volumes with duplicate media IDs and consolidate volumes into one volume configuration Always use barcodes that are unique with respect to the six 6 least significant characters across all media in all robots or use media ID generation rules to ensure unique media IDs are generated when using robot inventory update Media Manager Status Code 117 Message operation not allowed on cleaning cartridge Explanation A request was made to change a volume s expiration or maximum number of mounts but the operation is not allowed because the volume is a cleaning cartridge Recommended Action 1 Ifthe volume is a cleaning cartridge perform a valid operation such as changing the number of cleanings remaining for the cleaning cartridge 2 Ifthe volume s media type cannot be determined examine command output if available and debug logs for a more
544. res on the General tab in the NetBackup Configuration dialog box To display this dialog box start the Backup Archive and Restore interface on the client and click Configure on the Actions menu Ona Macintosh client delete DISALLOW _SERVER_FILE WRITES from the bp conf file in the NetBackup folder in the Preferences folder Ona NetWare target client set ALLOW_SERVER_WRITE to yes in the bp ini file NetBackup Status Code 190 Message found no images or media matching the selection criteria Explanation A verify duplicate or import was attempted and no images matching the search criteria were found in the NetBackup catalog Recommended Action Change the search criteria and retry NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 191 Message no images were successfully processed 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 debug log directory and retry the operation Check the resulting debug log NetBackup 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 Setting t
545. restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Examine the permissions and check for the existence of the global device database file Display the device configuration to determine whether or not the database is corrupt and restore a saved copy of the databases from catalog backups or delete them and recreate the device configuration as needed Device Configuration Status Code 48 Message RSM is supported only on Microsoft Windows 2000 and later OS versions Explanation On a request to make a device configuration change the RSM Microsoft Removable Storage Manager robot type was specified but the operating system version on the targeted device host does not support RSM devices Recommended Action Specify RSM devices only on Windows 2000 or later Windows based operating systems Device Configuration Status Code 49 Message The global device database host name is invalid Explanation On a device configuration request the global device database host name could not be obtained The global device database host name is obtained through an internal request that is sent to vmd the volume daemon on UNIX or the NetBackup Volume Manager service on Windows This request is likely to fail if vmd is not running on the targeted device host Recommended Action Chapter 5 Media Manager Status Codes and Messages 303 ar NetBackup 4 5
546. rform Resolving Network Communication Problems on page 21 NetBackup Status Code 58 Message can t connect to client Explanation The server was unable to connect to the client Recommended Action Perform Resolving Network Communication Problems on page 21 NetBackup 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 Ifthe server is a valid server verify that it is in the server list on the client If necessary add it as follows On Windows clients add the server on the Servers tab in the Specify NetBackup Machines dialog box To display this dialog start the Backup Archive and Restore interface on the client and click Specify NetBackup Machines on the Actions menu On Macintosh clients add a SERVER entry in the bp conf file On NetWare target and OS 2 clients add a SERVER entry in the bp ini file 90 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes If you add or modify server entries on the master server you must stop and then restart the NetBackup Request Manager and NetBackup Database Manager services 2 On Windows clients enable bpinetd debug logging as follows a Create a bpinetd debug log director
547. ring a vault job Recommended Action For the actual error that caused the volume manager command to fail review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install _path NetBackup logs vault Also review the detail 1og in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id Try running the volume manager command with the same arguments as in the log file to see the actual error Ensure that the volume manager daemons are running Also ensure that the robot is functional and you can communicate with it for example inventory the robot via the GUI NetBackup Status Code 304 Message specified profile not found Explanation This error occurs when the profile name specified on the vault command is not defined in the vault configuration Recommended Action Please rerun the vault command with a profile name that is defined in the vault configuration NetBackup Status Code 305 Message duplicate profile specified use full robot vault profile Explanation This error occurs when duplicate profile names have been defined in two or more vault configurations and only the profile name is specified on the vault command Recommended Action You must rerun the vault command with the triplet robot_name vault_name profile_name The tri
548. ring tape drives General Test and Troubleshooting Procedures If the Preliminary Troubleshooting or Troubleshooting Installation and Configuration Problems procedures did not reveal the problem perform the following procedures skipping those steps that you have already performed The procedures assume that the software was successfully installed but not necessarily configured correctly If NetBackup or Media Manager has never worked properly there are probably configuration problems Repeat the checks mentioned in the Troubleshooting Installation and Configuration Problems procedure when you encounter errors In particular look for device configuration problems You may also want to perform each backup and restore twice Perform them first as a user that is a member of the Administrators group and then as a user that is not a member of the Administrator group In all cases ensure that you have read and write permissions on the test files To Test Master Server and Clients 1 Enable appropriate debug logs on the master server see the Using the Logs and Reports chapter If you do not know which logs apply enable them all until you solve the problem Delete the debug log directories when you have resolved the problem 2 Configure a test policy set backup window to be open while you are testing Name the master server as the client and a storage unit that is on the master server preferably a nonrobotic drive
549. rive is configured correctly Do not use a robot number that is already configured on another server Try the test utilities described in the Robotic Test Utilities appendix Note Do not use the Robotic Test Utilities when backups or restores are active These utilities prevent the corresponding robotic processes from performing robotic actions such as loading and unloading media This can cause media mount timeouts and prevent other robotic operations like robotic inventory and inject eject from working 6 When the test policy operates satisfactorily repeat specific steps as necessary to verify other clients and storage units 7 When all clients and storage units are working test the remaining policies 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 the status codes chapters Resolving Network Communication Problems The following procedure is for resolving NetBackup communications problems such as those associated with NetBackup status codes 54 57 and 58 Note In all cases ensure that your network configuration is working correctly outside of NetBackup before trying to resolve NetBackup problems 1 Before retrying the failed operation Increase the logging level on the client see the user s guide for the client On the NetBackup server create a bprd debug log directory and on the
550. rized as one of the following A job started by either the NetBackup Java authentication service or user service no longer exists and did not report its result status Ajob 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 gt 100 have already been started Recommended Action 1 Ifthe problem persists restart the NetBackup Java interface and try again 2 Ifthe problem still persists enable detailed debug logging as explained under Enabling Detailed Debug Logging in Chapter 3 3 Restart the NetBackup Java interface and examine the logs Note The error is probably the result of a system resource issue When detailed debug logging has been enabled the details may be retrieved from the bpjava msvc or bpjava usvc log files NetBackup Status Code 510 Message File already exists file_name Explanation The NetBackup Java user service has attempted to create a file that already exists Recommended Action Remove the file which can be identified in the user service log files Refer to Troubleshooting the Administration Console on page 51 NetBackup Status Code 511 Message NB Java application server interface error Java exception NetBackup Troubleshooting Guide Windows NT 2000 Ne
551. rname username None of the NB Java applications are available to you NetBackup Status Code 502 no entity was found NetBackup Status Code 227 no files specified in the file list NetBackup Status Code 112 no images duplicated NetBackup Status Code 308 no images were successfully processed NetBackup Status Code 191 no media is defined for the requested NB database backup NetBackup Status Code 121 no profile was specified NetBackup Status Code 274 no schedules of the correct type exist in this policy NetBackup Status Code 240 no storage units available for use NetBackup Status Code 213 Chapter 4 NetBackup Status Codes and Messages 189 ar NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages no vault session id was found NetBackup Status Code 269 none of the files in the file list exist NetBackup Status Code 71 none of the requested files were backed up NetBackup Status Code 2 not all requested files were restored NetBackup Status Code 175 number of media has exceeded the capacity of MAP NetBackup Status Code 291 one or more errors detected during consolidated eject processing NetBackup Status Code 290 operation not allowed during this time period NetBackup Status Code 199 operation requested by an invalid server NetBackup Status Code 37 operation would cause an illegal dupl
552. roblem verify that all NetBackup software is at the same version level On Windows 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 policy On Macintosh clients check the version file in the bin folder in the NetBackup folder in the Preferences folder 2 Ifthe server is denying list and restore requests remove the DISALLOW CLIENT LIST RESTORE and DISALLOW CLIENT RESTORE options from the registry on a Windows NetBackup server Then stop and restart the NetBackup Request Manager service 3 For detailed troubleshooting information create bpdbm bprd and admin debug log directories Then retry the operation and check the resulting debug logs NetBackup Status Code 134 Message unable to process request because the server resources are busy Explanation Status code 134 is an informational message indicating that all drives in the storage unit are currently in use If this occurs NetBackup automatically tries another storage unit if one is not available NetBackup requeues the job with a status of 134 and retries it later Recommended Action Disable automatic retry using another storage unit and create the following f
553. roblem to a specific area Chapter 3 Using the Logs and Reports discusses the NetBackup logs and how to interpret them Chapter 4 NetBackup Status Codes and Messages explains each NetBackup status code and provides corrective actions for error conditions Chapter 5 Media Manager Status Codes and Messages explains each Media Manager status code and provides corrective actions for error conditions Chapter 6 Disaster Recovery explains how to recover critical NetBackup information in case of a disk crash Appendix A Functional Overview provides a functional overview of NetBackup and its Media Manager component for both Windows and UNIX NetBackup 4 5 Troubleshooting Guide for Windows Related Manuals NetBackup 4 5 Troubleshooting Guide for Windows Appendix B Networks and Hostnames provides information useful when configuring NetBackup on a host with multiple network connections and when hosts have multiple names Appendix C Robotic Test Utilities explains how to start the tests that are included with the robotic software Appendix D Backup Exec Tape Reader for NetBackup provides troubleshooting assistance when browsing restoring or converting catalogs from Backup Exec media and databases Following the appendixes is a glossary of NetBackup terms Related Manuals Refer to the NetBackup Release Notes for a complete list of NetBackup manua
554. robot number and robot type mismatch 226 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation A request was made to add or change volumes in the volume configuration The robot number to be associated with a volume is already in use and is associated with another volume in a robot with the same number but of another robot type Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that robot numbers are unique for each physical robot in all device configurations using the same volume database host Delete and re add a robot using a unique robot number if duplicate robot numbers are in use or specify a different volume database host for one of the duplicate robot numbers Use a media management interface to identify robot numbers currently in use for all volumes in the volume configuration If using a command line interface specify the correct robot type for the robot number associated with the requ
555. rvices are running Start them if needed The Backup Exec services are the following Backup Exec 8 x Agent Browser Backup Exec 8 x Alert Server Backup Exec 8 x Device amp Media Service Backup Exec 8 x Job Engine Backup Exec 8 x Naming Service Backup Exec 8 x Notification Server gt gt Backup Exec 8 x Server NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows beconv Error Messages Message No device of the appropriate type found for this media Explanation NetBackup does not have any drives configured that match the base media type of the Backup Exec media For example If the Backup Exec media has media type dlt there should be at least one NetBackup drive whose drive type is dlt dlt2 or dlt3 Recommended Action Configure drives of the appropriate drive type Use the Device Configuration Wizard or another device configuration interface in NetBackup Message Media is not assigned to the local NetBackup media server Explanation This happens when beconv associates a Backup Exec media with a volume record in the Media Manager volume database either by a barcode GUID or slot match but the volume is not assigned to the local NetBackup media server This situation is detected when the volume record in the Media Manager volume database is assigned but the volume is not present in the NetBackup media database of the local host This is a
556. ry the operation Then check the resulting debug logs Ensure that the correct master server is being specified for the connection NetBackup Status Code 219 Message the required storage unit is unavailable Explanation The policy or schedule for the backup requires a specific storage unit which is currently unavailable This error also occurs for other attempts to use the storage unit within the current backup session Recommended Action Look in the Job Details window for the failed job Or examine the Backup Status and All Log Entries report for the appropriate time period to determine the class or schedule that received the error then examine the specific class and schedule configuration to determine the required storage unit 1 Verify that the schedule specifies the correct storage unit and the storage unit exists 2 Verify that the NetBackup Device Manager service is running Use either the Activity Monitor or the Services application in the Windows Control Panel 3 Verify that the Maximum concurrent jobs attribute is not set to 0 for a disk storage unit and the Maximum concurrent drives attribute is not set to 0 for a Media Manager storage unit 4 Ifthe storage unit is a tape verify that at least one of the drives is in the UP state Use the Device Monitor Chapter 4 NetBackup Status Codes and Messages 1443 A NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows
557. s No memory available Robot Error Status Code 8 No mount pending for given mount index Device Management Status Code 16 no pools in the pool list Media Manager Status Code 112 No robot daemon or robotics are unavailable Device Management Status Code 60 No robot is defined of this type Device Management Status Code 52 No robots are configured Robot Error Status Code 7 lt NONE gt Device Configuration Status Code 36 not authorized to connect to vmd Media Manager Status Code 126 Not licensed for Fastrax support Device Configuration Code 53 One implicit reserve already exists Device Management Status Code 11 Only the administrative user can perform the requested operation Device Management Status Code 19 34 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages operation not allowed on cleaning cartridge Media Manager Status Code 117 Operator denied mount request Device Management Status Code 55 oprd request is not supported on the remote host Media Manager Status Code 137 oprd returned abnormal status Media Manager Status Code 96 Parameter is invalid Device Management Status Code 39 Physical drive is not available Robotic Status Code 245 pool database close operation failed Media Manager Status Code 107 pool data
558. s probably not running If Itid is still running its process lock file may have been removed Also message queues may not be functioning correctly on the system Recommended Action 1 If 1tidis not running start 1tid and try the operation again On UNIX run usr openv volmgr bin 1tid and on Windows start the NetBackup Device Manager service 2 If 1tidwas already running check for the existence and permissions of the lock file itself and the lock file directory which are usr openv volmgr misc 1tipid UNIX or nstall_ path Volmgr misc 1tipid Windows Terminate the 1tid process if it is running Create the lock directory folder and adjust the permissions as needed so that 1t id can obtain the above lock 3 On UNIX check the msgget man page and look for suggestions on troubleshooting the system message queues Device Management Status Code 23 Message Invalid Drive Number Explanation A request was made for drive but no such drive could be found in the active configuration 4 Chapter 5 Media Manager Status Codes and Messages 321 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action Ensure that 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows was stopped and restarted after changes were last made to the device configuration Display the device configuration using tpconfig
559. s 64 external mapping files 401 404 failure_history file 450 Fastrax 58 73 fi conf file 147 file restore problems Backup Exec 478 File database 450 file list symbolic link 60 file pathname max length 56 Files archive process 422 backup process 422 host xlate 469 restore process 432 flops on bplist 478 format directory 458 frozen image source for symbolic link 60 frozen image removing 64 fsckptadm command 63 fsclone frozen image 63 Functional overview introduction 419 Media Manager device management 453 directories and files 457 programs and daemons 458 startup 451 volume management 453 NetBackup backup and archive 422 directories and files 439 programs and daemons 441 restores 432 startup 420 gethostbyname 154 getpid 155 goodies directory 458 goodies directory 440 GUID 474 Help files Media Manager 458 UNIX client 440 Host name entries checking 25 host xlate file 26 469 IDR 406 Images database 450 Images on Media report 43 import 477 Index NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows include_list UNIX client 440 inetd 10 inetd Mac client log 48 installation Linux 10 Installation problems 10 Intelligent Disaster Recovery IDR 406 Introduction to troubleshooting 1 Java interface debug logging 53 troubleshooting background 51 jbpSA overview 447 JBPSimple properties file 53 Jobs database 450 key value 124 L
560. s Code NetBackup Status Code 31 Message could not set user id for process Explanation Could not set the user ID of a process to that of the requesting user NetBackup executes client processes as the requesting user Recommended Action Check the NetBackup All Log Entries report for clues on where and why the failure occurred For detailed troubleshooting information create a debug log directory for the process that you suspect of returning this status code Then retry the operation and check the resulting debug log NetBackup Status Code 32 Message could not set group id for process Explanation Could not set the group ID of a process to the requesting user group NetBackup executes client processes with the group ID of the requesting user Recommended Action Check the NetBackup All Log Entries report for clues on where and why the failure occurred For detailed troubleshooting information create a debug log directory for the process that you suspect of returning this status code Then retry the operation and check the resulting debug log NetBackup Status Code 33 Message failed while trying to send mail Explanation An E mail notification of backup archive or restore results has failed The E mail could not be sent to the administrator s address as specified by the E mail global attribute Recommended Action Check the NetBackup All Log Entries report for clues on where and why the failure occurred For detailed troubles
561. s are manually configured Device Configuration Code 53 Message Not licensed for Fastrax support Explanation An attempt was made to add or update a Fastrax device without a valid Fastrax license The request cannot be performed without a valid NetBackup for EMC Fastrax license key Recommended Action Install a Fastrax license key then re issue the configuration request _ yy Chapter 5 Media Manager Status Codes and Messages 305 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Format Optical Status Codes These status codes appear in exit status and command output for the tpformat command and in system or debug logs These codes are also presented by programs that call tpformat such as media and device management user interfaces and the vnopremd command Format Optical Status Code 0 Message Success Explanation An optical volume format operation was successfully completed Recommended Action None Format Optical Status Code 1 Message tpformat Invalid usage Explanation The format optical disk command tpformat was executed with improper options or there is an incompatibility between components or versions of the product Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increa
562. s that call those commands such as media and device management user interfaces and the vmopremd command Device Management Status Code 1 Message Invalid Drive Type Density Explanation An invalid density was specified for the d parameter on tpreq Recommended Action Check the tpreq man page command description for the list of valid densities Resubmit the mount request using a valid density Device Management Status Code 2 Message Drive is currently assigned Explanation A request was made for a specified drive but the drive was assigned Recommended Action Display drive status using vmopremd d or other means to see the list of drives and their assignment status Run the request later or first clear the drive assignment by stopping application activity on the drive unmounting the media with tpunmount or resetting the drive If the wrong drive was specified resubmit the request specifying the correct drive name or index as appropriate for the interface being used Device Management Status Code 3 Message Error in Sending Operator Message Explanation An attempt was made to send an operational message to 1t id the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows on an already existing internal message queue used for inter process communication But an error was encountered in the message communications The error probably indicates a lack of system resources for message queues Reco
563. s vault Only one session is allowed for a vault at any given time Recommended Action Start the vault session after the previous session has completed NetBackup Status Code 284 Message error caused by invalid data in vault configuration file Explanation This error is returned by a vault job or a command when it cannot interpret the information extracted from the vault configuration file For example if the vault configuration file is corrupt or refers to non existent or misconfigured objects Recommended Action Ensure that your vault configuration is correct that it refers to functional robots media servers volume pools and so forth Also ensure that the vault profile is defined in the configuration and has not been accidently removed after the vault job was started This can happen when more than one vault interface is changing the configuration at the same time Examine the vault logs for detailed information about configuration problems To correct the problem you may need to restore the following file from a backup copy UNIX usr openv netbackup db vault vault xml Windows install _path NetBackup db vault vault xml NetBackup Status Code 285 Message unable to locate vault directory NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation This error is returned by a vault job or command
564. sage pool database lock operation failed Explanation vmd the Media Manager volume daemon on UNIX encountered a system call error while attempting to lock the volume pool database Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon or start vmd with the verbose option b Retry the operation and examine the logs 2 Use the vmps command to ensure that vmd and vmdb_dump are not both running at the same time NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 Ensure that no other process has a lock on the volume pool database file usr openv volmgr database poolDB Media Manager Status Code 107 Message pool database close operation failed Explanation An error occurred when vmd attempted to close the volume pool database Recommended Action Examine the daemon debug log for a more detailed message on the system error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager s
565. sdd command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id tshd The Tape Stacker Half inch daemon is the interface between 1t id and the half inch cartridge stacker and communicates with the robotics through a SCSI interface This robot is not supported on Windows Started By Starting 1tid or on UNIX independently by using the usr openv volmgr bin tshd command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id wr 464 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs continued Program Description Daemon ts8d The Tape Stacker 8MM daemon is the interface bet
566. se the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Check the tpformat usage statement and compare with the parameters being sent to start the new process 3 Verify that all Media Manager binaries are at a compatible version level Format Optical Status Code 2 Message tpformat Cannot set volume header Explanation The format optical disk command tpformat encountered a system device or media error while trying to write the optical volume header Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify integrity of the device and the media and check the system device files for correctness according to the NetBackup Device Configuration Guide Examples of problems that may have been encountered are a Operating system
567. se virtual memory on Windows a Display the Control Panel b Double click System c On the Performance tab set Virtual Memory to a higher value On Windows 2000 select Performance Options from the Advanced tab 4 Verify that all product binaries are properly installed 5 Verify that there are no unexpected Media Manager processes running by executing vmps Some processes are expected to remain running though some processes that are not going away could indicate a more serious problem such as a hung system call Media Manager Status Code 3 Message must be root user to execute command Explanation The process was started by a user or process that did not have root privileges on UNIX or administrator privileges on Windows Recommended Action If desired give the user or process administrator privileges on Windows or root privileges on UNIX and retry the operation Media Manager Status Code 4 Message invalid command usage NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation A Media Manager command was executed with improper options or there is an incompatibility between components or versions of the product Recommended Action 1 Examine command output debug logs and system logs for a more detailed message on the error as follows a Ifnot already enabled enable deb
568. server bpbbackupdb starts the backup and archive program on the master server If the database is on a media server bpbbackupdb starts the backup and archive program on the media server The bpbkar program transmits file information and the backup image to separate bpbackupdb processes as shown on Figure 9 The original bpbackupdb process receives the backup image and sends it to the backup device Appendix A Functional Overview 431 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Asecond 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 This is done because you must have a backup of all the databases to be certain that you have a consistent database Restore Processes NetBackup restore operations like backups can vary according to client type The following explains the basic variations Restores UNIX Clients Before starting a restore operation a user will usually browse the file database and list the files available in the backup images The desired files can then be selected from the list
569. shooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows NetBackup Device Manager service The NetBackup Windows service that runs on a NetBackup server and starts the robotic control processes and controls the reservation and assignment of volumes This service runs only if the server has devices under Media Manager control The process is 1t id NetBackup properties Same as NetBackup configuration options but are called NetBackup properties on Microsoft Windows platforms NetBackup Request Manager service The NetBackup Windows service that runs on the master server and starts the scheduler and receives requests from clients NetBackup Volume Manager service A NetBackup Windows 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 This robot type is supported only by NetBackup DataCenter servers offsite volume group A volume group in which media will appear after having been ejected from the robot for vaulting When Vault ejects media it is moved from the robotic volume group to the off site volume group Glossary 5077 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide f
570. spect of returning this status code Then retry the operation and check the resulting debug log NetBackup Status Code 28 Message failed trying to fork a process Explanation A CreateProcess failed This may be due to Anoverloaded system Insufficient swap space or physical memory Too many processes running on the system Recommended Action Check the NetBackup All Log Entries report for clues on where and why the failure occurred For detailed troubleshooting information create debug log directories for the processes that you suspect of returning this status code Then retry the operation and check the resulting debug logs NetBackup 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 Chapter 4 NetBackup Status Codes and Messages 7 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 3 For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Statu
571. ssage unimplemented feature Explanation The specified operation is unimplemented This error should not occur through normal use of NetBackup Recommended Action Save all error information and call customer support NetBackup Status Code 17 Message pipe open failed Explanation Occurs in NetBackup client menu and vault areas Recommended Action None NetBackup Status Code 18 Message pipe close failed Explanation Close of a pipe failed when one process tries to start a child process Recommended Action Check the NetBackup Problems report for clues on why the failure occurred For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log NetBackup Status Code 19 Message getservbyname failed Explanation A call to getservbyname failed The getservbyname function uses the name of the service to find a service entry in the services file Recommended Action Chapter 4 NetBackup Status Codes and Messages 69 or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Check the NetBackup Problems report for clues on why the failure occurred 2 Ona Windows system verify that the sSystemRoot system32 drivers etc services file shows the correct entries for the NetBackup internet processes bpcd bpdbm and bprd Ensure that the Net
572. ssible through a vendor administrative interface as appropriate Update the volume configuration as needed and resubmit the request Chapter 5 Media Manager Status Codes and Messages 353 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Robotic Status Code 235 Message barcode label is unreadable Explanation The media was found in the robotic library but it has an unreadable barcode label Recommended Action Use the robot test utility or a vendor administrative interface to verify the status of media Correct the label or replace the media as appropriate Update the volume configuration as needed and resubmit the request Robotic Status Code 236 Message Robot has misplaced the media Explanation The requested media was known according to the vendor software managing the robotic library but the media has been misplaced Recommended Action Use a robot test utility or a vendor administrative interface to verify the status of media Search for the media inside the robotic library Update the volume configuration and search for the media if it was not in the robotic library as needed and resubmit the request Robotic Status Code 237 Message Volume is in use Explanation The media was in use Recommended Action Use the robot test utility or a vendor administrative interface to verify the status of media Determine what applications may be usin
573. stination storage unit must correspond to the robotic volume group device delays Delays caused by the device that are beyond the control of the storage application An example is the time required to position tape under the read and write heads device host A host that has Media Manager installed where a drive or robotic control is attached or is defined device monitor A Media Manager administration utility that provides monitoring and manual control of Media Manager storage devices For example an administrator or computer room operator can use this utility to manually reset devices or set them to the UP or DOWN state DHCP Dynamic host configuration protocol This TCP IP protocol automatically assigns temporary IP addresses to hosts when they connect to the network differential incremental backup Scheduled by the administrator on the master server and backs up files that have changed since the last successful incremental or full backup All files are backed up if no prior backup has been done Also see cumulative incremental backup directory depth The number of levels below the current directory level that the NetBackup interfaces show in their directory and file list displays 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 498 NetBac
574. stration Console select Host Properties Select Properties from the Actions menu The General Server tab contains the port options For more information refer to the NetBackup System Administrator s Guide for Windows Recommended Action 1 Restart the NetBackup Java interface and log in again 2 Ifthe problem persists enable detailed debug logging NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 Restart the NetBackup Java Administration interface and examine the logs NetBackup Status Code 507 Message Socket connection to the NB Java user service has been broken Please retry your last operation Explanation The connection was broken to the NetBackup Java application server that is running on the NetBackup host you are logged in to Recommended Action 1 Retry the last operation 2 Ifthe problem persists restart the NetBackup Java interface and try again 3 Ifthe problem still persists enable detailed debug logging as explained under Enabling Detailed Debug Logging in Chapter 3 4 Restart the NetBackup Java interface and examine the logs Note You may be having network or system problems unrelated to NetBackup NetBackup Status Code 508 Message Can not write file Explanation This error is caused by one of the following The NetBackup Java user service has attempt
575. t lt 2 gt lt 2 gt lt 2 gt lt 2 gt lt 2 gt bpcd main BPCD RESTORE IMAGE FILES RQST bpcd_restore_image files bpcd_restore image files bpcd_restore_image files bpcd_restore_image files bpcd_restore image files bpcd_restore_image files bpcd_restore image files bpcd_restore image files bpcd_restore_image files bpcd_restore_image files bpcd_restore image files bpcd_restore_image files bpcd_restore_image files bpcd_restore_image files bpcd_restore image files bpcd_restore_image files browse _client redeemer requesting client destination_client client_type 13 mediaid ISV181 keyword 7 obj_desc NULL keep 1 D VERITAS NetBackup logs user_ops birk logs NBWINO01 rename_file NONE commit 0 dirByteCount 0 tempDirectory NONE mountDatabase 0 beFilePathLen 18 beRedirectionPath Appendix D Backup Exec Tape Reader for NetBackup NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting with the Debug Logs As shown above the redirection path beRedirectionPath has been specified as D Public Restored Since the browse_client redeemer is the same as the destination_client redeemer and since the browse_client is of type Windows client_type 13 the destination client is of type Windows Since we are restoring to Windows the path should be of the format D Public Restored But the pat
576. t stop Debug Log usr openv netbackup logs ndmpmoveragent NDMP Mover Agent On the NetBackup media server Windows this service acts as an NDMP server in a type of three way backup called Remote NDMP Started By Executing install_path netbackup bin Instal1lNdmpMoverAgent path_of_NetBackup_binaries Stopped By Executing install_path netbackup bin InstallNdmpMoverAgent r Debug Log install_path netbackup 1logs ndmpmoveragent Appendix A Functional Overview 447 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Daemon Description NBWIN EXE NBNWNT EXE NBNW95 EXE NetBackupBPCD For Windows clients this is the executable file that starts the client user interface on Windows systems Started By From the Windows Start menu under Programs NetBackup Stopped By Exiting the client user interface Debug Log mmddyy log file in the NBWIN directory on the client For NetWare nontarget clients this is the executable file that starts the client user interface on Windows systems Started By From the Windows Start menu under Programs NetBackup Stopped By Exiting the client user interface Debug Log none For NetWare nontarget clients this is the executable file that starts the client user interface on Windows 98 95 systems
577. t consistent with the physical contents of the robotic library that is associated with the slot associated with the requested volume Recommended Action The volume configuration or media placement in the robotic library needs to be adjusted using one of the media management interfaces Determine whether the barcode has changed or whether the media has been changed since the last time the volume database was reconciled for the affected slot If only the barcode has changed but not the media issue an update barcode request for each affected volume If the media has been changed use a media management interface to run robot inventory update which will update the volume database to reflect the physical location of the media NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Robotic Status Code 227 Message FASTRAX unable to process clean request Explanation After a cleaning tape is mounted on a Fastrax attached drive control is passed to the Fastrax system which determines when the cleaning has completed This error is reported when the Fastrax system detects an error while processing the clean request Recommended Action Examine the Symmetrix logs located in the usr emc API symapi 1log directory Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1t id the device daemon
578. t information about the robotic library and its associated MAPs and volumes Recommended Action For detailed information about why the process failed review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install_path NetBackup logs vault Also review the detail 1log in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install_path NetBackup vault sessions vault_name sidxxx where xxx is the session id Correct the error and rerun the vault session vlteject command or vltopmenu eject command NetBackup Status Code 297 Message all volumes are not available to eject Explanation This error occurs when an attempt is made to eject a non existent or bad media id during the eject phase of a vault session vlteject command or vltopmenu command Possible reasons for this occurring are The bad media id was added by means of the vlt_ejectlist_notify script The bad media id is already in the MAP or not in the robotic library The bad media id is in a robotic drive The bad media id is in transit in the robotic library Recommended Action Remove or correct the bad media id from the vit_ejectlist_notify script and rerun the vault session If the bad media id is in the MAP or a drive or in transit something is misconfigured NetBackup Status Code 298 Message the library is not ready to eject volumes
579. t resources are currently in use Investigate whether the robotic daemon process on the local device host is tied up in communications with devices or other components Device Management Status Code 6 Message Error in Receiving Daemon Message Explanation An attempt was made by 1tid the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows to receive or process an internal process communications message to a robotic daemon process using an already existing internal message queue but an error was encountered in the message communications The error probably indicates a lack of system resources for message queues or mismatched software components Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 315 Or NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 2 On UNIX servers gather output from the ipcs a command to see what resources are currently in use Check the installed software components and verify that they
580. t that is making the request This can be due to incorrect network configuration involving Multiple network interfaces Running DNS and not having reverse addressing configured Create bptm and vmd debug log directories and retry the operation Examine the bptm debug log to verify that bptm is connecting to the correct system If an error is logged examine the vmd log On Windows the vmd log is install_path Volmgr debug daemon xxxxxx log If this is a new storage unit and this is the first attempt to use it stop and restart NetBackup on the master server NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Note The bptm debug logs in verbose mode usually show the NetBackup media selection process NetBackup 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 An example of this is attempting to suspend or freeze a volume while it is being used for a backup or restore Recommended Action Retry the command when the volume is not in use Use the Device Monitor to determine if the volume is in use NetBackup Status Code 98 Message error requesting media tpreq Explanation The tape manager bptm received an error when requesting a media mount from the NetBackup Device Manager service Reco
581. tBackup 4 5 Troubleshooting Guide for Windows Messages Request terminated because media is unmountable Device Management Status Code 69 Request terminated because media is write protected Device Management Status Code 70 Request terminated because mount requests are disabled Device Management Status Code 63 Request terminated because of volume pool mismatch Device Management Status Code 66 Request terminated because user not validated for volume pool Device Management Status Code 67 Request terminated because user group not validated for volume pool Device Management Status Code 68 Request terminated by tpunmount call from another process Device Management Status Code 36 Requested drive could not be reserved Device Management Status Code 24 requested drive is already reserved by host Media Manager Status Code 145 requested drive is already reserved Media Manager Status Code 130 Requested drive is in an offline domain Robotic Status Code 238 Chapter 5 Media Manager Status Codes and Messages 3877 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages requested drive is not currently registered Media Manager Status Code 132 requested drive is not currently reserved Media Manager Status Code 134 requested drive is not registered for host Media Manager Status Code 131 requested drive
582. tBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Incorrect server platform identifier NetBackup Status Code 162 Internal error a bad status packet was returned by NB Java application server that did not contain an exit status code NetBackup Status Code 512 invalid command parameter NetBackup Status Code 20 invalid command protocol NetBackup Status Code 143 invalid command usage NetBackup Status Code 144 invalid configuration for duplication to disk NetBackup Status Code 310 invalid file pathname NetBackup Status Code 104 invalid file pathname found cannot process request NetBackup Status Code 106 invalid filelist specification NetBackup Status Code 69 invalid jobID NetBackup Status Code 273 invalid request NetBackup Status Code 133 Chapter 4 NetBackup Status Codes and Messages 18 Sr NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Invalid username NetBackup Status Code 503 licensed use has been exceeded NetBackup Status Code 159 logic error encountered NetBackup Status Code 256 main bpsched is already running NetBackup Status Code 244 master server request failed NetBackup Status Code 149 media close error NetBackup Status Code 87 media id is either expired or will exceed maximum mounts
583. tBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Explanation This is a generic error for all non socket IO connection broken related errors status code 507 that could occur when processing the data from the NetBackup Java authentication or user services The Java exception will provide some additional detail about the error This error usually results from system or network problems Recommended Action 1 Ifthe problem persists restart the NetBackup Java interface and try again 2 Ifthe problem still persists enable detailed debug logging as explained under Enabling Detailed Debug Logging in Chapter 3 3 Restart the NetBackup Java interface and examine the logs Note The error is probably the result of a system resource issue When detailed debug logging has been enabled the details may be retrieved from the bpjava msvc or bpjava usvc log files NetBackup 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 Explanation The NetBackup Java authentication or user service returned a data packet indicating an error but no status code or error message was contained within it Recommended Action 1 Ifthe problem persists restart the NetBackup Java interface and try again 2 Ifthe problem still persists enable detailed debug logging as explained unde
584. tBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 Check to see whether the robotic device is still functioning Use a robot test utility to send commands to the device to see whether it is responsive Verify that there are no unexpected Media Manager processes running by executing vmps Some processes are expected to remain running but some processes that do not go away could indicate a more serious problem such as a hung system call Robotic Status Code 204 Message Unable to initialize robot Explanation The robot could not be initialized This is a generic status used for many conditions Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the robot initialization failure Robotic Status Code 205 Message Robotic mount failure Explanation The robot could not mount media Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error
585. tBackup 4 5 Troubleshooting Guide for Windows Status Codes Recommended Action Examine the system log for a more detailed message on the error Increase the level of verbosity by adding the VERBOSE option in the vm conf file Restart the device daemon 1t id UNIX or NetBackup Device Manager service Windows then retry the operation and examine the system log file Robot Error Status Code 12 Message Usage error in creating child process Explanation A robotic daemon process could not create a child process due to an incompatibility between robotic software components Recommended Action 1 Examine system logs for a more detailed message on the error a Increase the level of verbosity by adding the VERBOSE option in the vm conf file Restart the 1tid device daemon UNIX or NetBackup Device Manager service b Retry the operation and examine the system log file 2 Verify that all Media Manager binaries are at a compatible version level Robot Error Status Code 14 Message You must be administrator to execute Explanation A robotic process was started under a user account that was lacking Administrator privileges This applies to Windows systems only Recommended Action Allow robotic daemons to be started automatically as needed by the NetBackup Device Manager service Ensure that this service is being started from a user account with administrator privilege Robot Error Status Code 16 Message Devices located i
586. tBackup services except the NetBackup Client service B4 8 Recover NetBackup catalogs install_pathNetBackup db Tape with catalog install_path NetBackup var backups install_path Volmgr database Start all NetBackup services Bda NDABPNH 9 Tape with other 10 Restore all other files do not backups restore catalogs 11 Check debug logs and correct any problems 12 Reboot the system D 402 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Master Server Disk Recovery Assumptions The NetBackup master server was running Windows NT or Workstation 4 0 or above or Windows 2000 The latest NetBackup catalog backup is available on tape or disk The regular backups included the system directory typically C Winnt This is the directory where the Windows operating system and therefore the registry reside If the regular backups excluded any files that resided in the system directory it is possible that you will not be able to restore the system so it completely matches its previous configuration Defective hardware has been replaced Before Starting Verify that you have Windows software to reinstall on the NetBackup server that is being restored Reinstall the same type and version of software that was previously used For example do not install Windows NT Server 4
587. tBackup would then interpret the request as coming from a host named meteor which was not in the client list and the restore would fail The solution in this case is also identical to that discussed in Example 4 Clients in Multiple Networks on page 36 wr 38 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows General Test and Troubleshooting Procedures Example 5 Server Connects to Multiple Networks Windows Client mars saturn Media Server _ Ethernet NetBackup Configuration 1 jupiter Windows NT 2000 Master Server meteor meteor satum ients Ethernet Client List mars 2 ete services bpcd 13782 tcp bpcd bprd 13720 tcp bprd Policy Client List jupiter mars saturn pluto NetBackup Configuration ervers Server List jupiter meteor saturn 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 odid 13706 tcp odld pluto Client NetBackup Configuration i Windows NT 2000 Windows NT 2000 Servers Server List jupiter meteor saturn General Client Name pluto 2 etc services
588. tabase matches what is in the robot Robotic Status Code 249 Message Volume is in home slot Explanation Volume is currently in its home slot and ready for eject Recommended Action None Robotic Status Code 250 Chapter 5 Media Manager Status Codes and Messages 357 Sa NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Message Media access port is available Explanation Media access port is available for inject or eject Recommended Action Begin inject or eject operation Robotic Status Code 251 Message Media access port is unavailable Explanation Media access port is not ready for inject or eject Recommended Action Manually remove any media remaining in the robot s media access port If this status persists check robotic console for errors Robotic Status Code 252 Message Media access port is in inject mode Explanation Media access port is ready to inject and is not available for eject Recommended Action Complete inject operation Robotic Status Code 253 Message Media access port is in eject mode Explanation Media access port is ready to eject and is not available for inject Recommended Action Complete eject operation wr 358 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Robotic Error Codes T
589. tabases for volume related requests so ensure that duplicate media IDs are not used in volume configurations across multiple hosts If duplicate IDs are found either completely separate the configurations by not sharing any devices or remove volumes with duplicate media IDs and consolidate volumes into one volume configuration Always use barcodes that are unique with Chapter 5 Media Manager Status Codes and Messages 247 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes respect to the six 6 least significant characters across all media in all robots or use media ID generation rules to ensure unique media IDs are generated when using robot inventory update Media Manager Status Code 94 Message volume is not in specified pool Explanation A request was made to assign a volume from a specified volume pool The volume was either found to be in a different volume pool or for optical media the volume partner was in a different volume pool Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and
590. tarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Examine the permissions and available file system space for writing to the database usr openv volmgr database volDB UNIX or install_path Volmgr database volDB Windows Media Manager Status Code 33 Message database write operation wrote too few bytes Chapter 5 Media Manager Status Codes and Messages 215 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation vmd the Media Manager volume daemon on UNIX or NetBackup Volume Manager service on Windows encountered an error while writing a volume database record where the record was only partially written Recommended Action 1 Examine the daemon debug log for a more detailed message on the system error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option if available b Retry the operation and examine the logs 2 Examine the available file system space for writing to the database usr openv volmgr database volDB UNIX or install_path Volmgr database volDB Windows Media Manager Status Code 34 Message medi
591. tarts an archive Started By Starting an archive by using the client user interface or executing the usr openv netbackup bin bparchive command on the client Stopped By Completion of operation Debug Log bparchive log on the client Appendix A Functional Overview 441 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Backup and Restore Functional Description Table 6 NetBackup Daemons and Programs continued Program Daemon Description bpbackup bpblr bpbrm bpbkar BPBKAR32 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 Debug Log bpbackup log on the client On UNIX clients the Block Level Restore program calls the VfMS mapping methods and is used to restore NetBackup for EMC Fastrax images Started By For each NetBackup for EMC Fastrax restore bpcd starts an instance of bpb1r on the client Stopped By Completion of restore operation Debug Log bpb1r 1og on the client On master and media servers the Backup Restore Manager manages the client and media manager processes and uses error status from both to determine the final status of backup or restore operations Started By For each backup o
592. tatus Code 505 Message Can not connect to the NB Java authentication service on host on the configured port configured_port_number 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 Ensure that no other application is using the port configured for the NetBackup Java interface NetBackup Status Code 506 Message Can not connect to the NB Java user service on host on port port_number Explanation Once the user name on the login dialog is validated for access by the NetBackup Java authentication service a NetBackup Java user service is used for all other service requests from the NetBackup Administration interface Communication between the NetBackup Java interface and user service is attempted on the port number specified in the error message Refer to the various port configuration options described in the NetBackup System Administrator s Guide UNIX or Windows OnUNIX the port configuration options are specified in the usr openv netbackup bp conf file On Windows from the NetBackup Admini
593. tatus Code 45 Drive name does not exist Device Configuration Status Code 35 Drive name is already in use by another drive Device Configuration Status Code 34 Drive not available in library for mount request Device Management Status Code 62 Duplicate device path names Device Configuration Status Code 20 error auto generating volume group Media Manager Status Code 57 Error in attaching the shared memory Robot Error Status Code 4 Chapter 5 Media Manager Status Codes and Messages 371 NetBackup 4 5 Troubleshooting Guide for Windows Messages NetBackup 4 5 Troubleshooting Guide for Windows Error in getting process Id Robot Error Status Code 5 Error in getting semaphore for operator Device Management Status Code 34 Error in getting semaphore Device Management Status Code 32 Error in getting shared memory Robot Error Status Code 3 Error in IPC SHMAT call Device Management Status Code 14 Error in IPC SHMGET call Device Management Status Code 13 Error in MsgGet Device Management Status Code 28 Error in Receiving Daemon Message Device Management Status Code 6 Error in Receiving Operator Message Device Management Status Code 4 Error in Receiving User Message Device Management Status Code 8 Error in SEMAPHORE operation Device Management Status Code 33 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting
594. tatus Code 73 invalid robot coord1 Media Manager Status Code 16 invalid robot coord2 Media Manager Status Code 17 Invalid robot drive number for the robot type Device Configuration Status Code 28 invalid robot host Media Manager Status Code 14 Invalid robot number Device Configuration Status Code 15 invalid robot number Media Manager Status Code 13 Invalid robot type Device Configuration Status Code 18 Chapter 5 Media Manager Status Codes and Messages 379 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages invalid robot type Media Manager Status Code 12 invalid rule database entry Media Manager Status Code 119 invalid scratch pool name Media Manager Status Code 173 Invalid SCSI bus number for the robot Device Configuration Status Code 8 Invalid SCSI logical unit number for the robot Device Configuration Status Code 10 Invalid SCSI port number for the robot Device Configuration Status Code 7 Invalid SCSI target for the robot Device Configuration Status Code 9 Invalid Usage Device Configuration Status Code 11 invalid volgroup Media Manager Status Code 15 Invalid volume count Device Management Status Code 18 invalid volume database host Media Manager Status Code 19 a 380 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for
595. tatus Codes 1 Examine the daemon and reqlib debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Ensure that volumes are properly configured on the volume database host that matches the volume database host configured for the robot or set of standalone drives Use the tpconfig dandtpconfig lsavdbhost commands to list the configured volume database hosts Select the current server the one you are administering to be the same as the host which is the correct volume database host for a targeted device 3 Update the volume or device configurations specify the correct volume database host modify volume properties or adjust search criteria as needed so that the requested operation can find the requested volume pool Investigate inconsistencies between the volume database and the volume pool database and restore or correct those databases from a previous state as needed Media Manager Status Code 110 Message pool database truncate operation failed Explanation The system call ftruncate 3C failed during an attempt to rewrite the volume pool database during a volume pool add change delete operation Recomme
596. tatus Codes and Messages 395 r NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages Unable to retrieve GUID from RSM api Device Configuration Status Code 46 Unable to SCSI unload drive Robotic Status Code 210 unable to send exit status Media Manager Status Code 67 Unable to sense robotic device Robotic Status Code 202 unexpected data from robotic software daemon Media Manager Status Code 46 unexpected data from robotic software daemon Media Manager Status Code 46 unexpected data received Media Manager Status Code 40 Unknown drive name Device Management Status Code 41 Usage error in creating child process Robot Error Status Code 12 user is not valid for this host Media Manager Status Code 99 volume daemon fork failed Media Manager Status Code 85 396 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages volume does not exist in database Media Manager Status Code 35 volume group does not exist Media Manager Status Code 65 volume has exceeded maximum mounts Media Manager Status Code 116 volume has passed expiration date Media Manager Status Code 115 volume is already assigned Media Manager Status Code 93 Volume is in home slot Robotic Status Code 249 Volume
597. tatus file in the database directory folder Recommended Action Investigate why the robot status file in the directory usr openv volmgr database UNIX or folder install_path Volmgr database Windows cannot be created or opened On Windows check which account the NetBackup Device Manager service and thus the robotic process is running under and compare it against the security properties of the database folder Robotic Status Code 244 Message The eject command was aborted by the user Explanation An administrator or operator canceled an eject media request Recommended Action This happens when an eject request has been canceled by an administrator or operator The request may have been canceled for a number of reasons such as missing or faulty media the need to allow the media access port to be used for other requests or the desire to perform the operation at a later time Check with the administrator or operator for more information Robotic Status Code 245 Message Physical drive is not available Explanation A robotic mount operation could not be completed because physical drive resources are not available for the request This is probably the result of operating in an environment based on virtualized resources such as one involving the Storagenet 6000 Storage Domain Manager SN6000 The SN6000 virtualizes tape drives Some configurations of the SN6000 may involve a different number of logical drives as compared to the num
598. te logs NetBackup Status Code 290 Message one or more errors detected during eject processing Explanation This error occurs when more than one error is encountered during an eject procedure via vltopmenu Any eject errors in the range 291 to 300 could have occurred in any of the sessions being ejected Recommended Action For detailed information review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install _path NetBackup logs vault Also review the detail 1og in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install _path NetBackup vault sessions vault_name sidxxx where xxx is the session id The media that was not ejected may need to be ejected manually by means of viteject or vltopmenu after the problem has been identified and corrected This error often indicates that the media were left in the offsite vault volume group but still physically reside in the robot or in the robotic MAP To solve this problem do one of the following Manually remove any media that are in the offsite vault volume group but are still in the robotic library wr 158 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Inventory the robotic library This puts any media that were in the offsite
599. ted has a volume database XYZ Explanation This happens when the same media IDs are present in different Media Manager volume databases The volume record that was used to issue the mount was different from the volume record used by Media Manager to mount the media Recommended Action Run beconv check_consistency to determine which Media Manager databases contain the same media ID Remove the duplicate media ID from the appropriate volume databases and run bephyinv Use a single volume database instead of configuring volumes on multiple hosts NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows bpimport Error Messages bpimport Error Messages The cause of problems relating to bpimport can be determined by examining the NetBackup bptm logs on the media server on which the media is being imported Message Unable to connect to the Backup Exec engine Explanation Backup Exec services are not running on the host on which the media is being mounted Recommended Action Check whether the Backup Exec services are running The Backup Exec services are the following Backup Exec 8 x Agent Browser Backup Exec 8 x Alert Server Backup Exec 8 x Device amp Media Service Backup Exec 8 x Job Engine Backup Exec 8 x Naming Service Backup Exec 8 x Notification Server 2 Backup Exec 8 x Server Message media man
600. ted with improper options when it was not supported or a robotic operation encountered an incompatible device interface There may be an incompatibility between components or versions of the product Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Verify that all Media Manager binaries and user interfaces are at a compatible version level Chapter 5 Media Manager Status Codes and Messages 341 or NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Robotic Status Code 208 Message Requested slot is empty Explanation No media was found in a specified slot The volume configuration may not be consistent with the physical contents of the robotic library that is associated with the volume Recommended Action Install or realign the container holder for the media if it was missing or misaligned Place media right side up in the slot if the media is upside down Check to see if the requested slot is reserved to the robotic library for internal use Physically correct issues within the robotic
601. ter to the inode for the data On a Windows server a hard link is a directory entry for a file Every file can be considered to have at least one hard link On NTFS volumes each file can have multiple hard links and a single file can appear in many directories or even in the same directory with different names heap level A parameter for memory heap debugging on a Novell NetWare or Windows NetBackup client 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 The image contains all the files directories and catalog information associated with the backup or archive import The process of recreating NetBackup records of images so the images can be restored include list A list that designates files or directories to add back in from the exclude list incremental backup See cumulative incremental backup and differential incremental backup wr 502 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubles
602. tered a situation where the global device database file could not be opened Recommended Action 1 Check for the existence and permissions of the globDB file in the usr openv volmgr database directory or install_path Volmgr database folder 2 Restore the globDB file from the catalog backups or from another location change the access permissions on the existing globDB or as a last resort move rename the current globDB to start over with an empty global device configuration 3 Ifthe move rename method is used recreate all device configurations on all hosts Media Manager Status Code 158 Message global device database close operation failed Explanation An error occurred when vmd attempted to close the global device database Recommended Action Examine the daemon debug log for a more detailed message on the system error 1 Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option 2 Retry the operation and examine the logs Chapter 5 Media Manager Status Codes and Messages 277 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Status Code 159 Message the volume guid is not unique in the database Explanation
603. terface to verify the status of media as needed Update the volume configuration and search for the media if it was not in the robotic library as needed and resubmit the request Robotic Status Code 233 Message Volume is in library but not in drive domain Explanation The media was found in the robotic library in a domain of the library that is inaccessible to the drives that are configured in the robot Recommended Action Issue a robot inventory Contents report to obtain the list of media in the robotic library Check the device configuration and ensure that the drive addresses correspond to the correct domain for the media Correct the device configuration as needed and restart 1t id the device daemon on UNIX or NetBackup Device Manager service on Windows Use a robot test utility or a vendor administrative interface to verify the status of media as needed Update the volume configuration and physically move the media into the robotic library as needed and resubmit the request Robotic Status Code 234 Message Robot denied access to the resource Explanation The media was found in the robotic library but is being denied access according to an established security policy Recommended Action Issue a robot inventory Contents report to obtain the list of media in the robotic library Use a vendor administrative interface to verify the status of media as needed Delete the media in the volume configuration or make the volume acce
604. termined that it was not the scan host for the drive so the request was refused to be retried by the caller Recommended Action 1 If problems are encountered as a result of the reported error check for communication configuration and system problems among the associated hosts Display the device configurations on the affected hosts to determine the role that each host is handling for drive sharing Identify the DA drive allocation host as the volume database for the residence in which the drives are configured Identify the current scan host for the drive by sending a vmdareq call to the DA host 2 Examine command output if available debug logs and system logs for messages related to the error Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1t id the device daemon on UNIX or NetBackup Device Manager service on Windows Configure scan ability priorities for assigning scan hosts by changing the Media Manager configuration so that less network connections need to be maintained and greater system load is placed on hosts more capable of servicing the load Device Management Status Code 49 Message Tape file path exceeds 255 character maximum Explanation On a tape mount request the file name associated with the request exceeded 255 characters Recommended Action When requesting a tape mount ensure that the fil
605. th If there is no file at that location check the directory folder permissions for read write access for the user or application process that issued the mount request Device Management Status Code 45 Message Drive is not currently reserved for this host Explanation On a request to release a shared drive the drive was found to be not reserved to the local host This status code is related to the internal implementation of the SSO feature not SCSI Reserve Release Chapter 5 Media Manager Status Codes and Messages 329 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Recommended Action If problems are encountered as a result of the reported error verify that there are no unexpected robotic daemons processes running by executing vmps Stop and restart 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows so that its internal tables are re initialized Device Management Status Code 46 Message Tape needs to be write enabled Explanation On a tape mount request the specified access mode was for write access but the physical media was write protected Recommended Action Change the physical media write protect setting to allow write access unlocked or resubmit the request with read only access To request read only access using tpreq specify an access mode argument of r for read or use the default read
606. the install_path Net Backup share folder Windows Messages This section lists Media Manager messages alphabetically The status code type and number are included in parentheses after the message Refer to the appropriate section in this chapter such as Media Manager Status Codes Device Configuration Status Codes and so forth for the status code with explanation and recommended action lt NONE gt Device Configuration Status Code 36 A memory allocation attempt failed in the robotic daemon Robotic Status Code 240 a scratch pool is already defined Media Manager Status Code 171 A SCSI inquiry sent to the device has failed Device Configuration Status Code 16 364 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages ADAMM GUID does not exist in database Media Manager Status Code 168 ADAMM GUID is not unique in the database Media Manager Status Code 167 Adding this device would exceed the maximum allowed Device Configuration Status Code 40 Adding this drive would exceed the maximum allowed Device Configuration Status Code 39 all available pool numbers are in use Media Manager Status Code 103 all available rule numbers are in use Media Manager Status Code 120 An error occurred accessing the RSM api Robotic Status Code 241 another daemon already exists
607. the volume pool specified in the Media Manager configuration for the media ID Recommended Action Use a media management interface to obtain the volume pool name of the media that is to be mounted and resubmit the mount request specifying the correct pool name Device Management Status Code 67 Message Request terminated because user not validated for volume pool Explanation The user is not validated to use the media ID because of permissions defined for the volume pool in which the media ID is contained Recommended Action Query the volume pool information for the requested volume pool on the host where the mount request was issued by running vmpool listall b Check the user ID on UNIX by executing the id 1M system command Change the volume pool user ID security with vmpool or another user interface that supports volume pool user and group attributes Change the volume pool associated with the volume if it is not assigned or log in as the user ID with permissions to use media in the targeted volume pool Then resubmit the mount request Device Management Status Code 68 Message Request terminated because user group not validated for volume pool Explanation The user or group is not validated to use the media ID because of permissions defined for the volume pool in which the media ID is contained Recommended Action Query the volume pool information for the requested volume pool on the host where the mount request was iss
608. the Backup Archive and Restore interface on the client and click NetBackup Client Properties on the File menu Verify that the setting on the Network tab matches the one in the services file The services file is located in sSystemRoot system32 drivers etc services Windows NT 2000 Cc Windows services Windows 98 and 95 The values on the Network tab are written to the services file when the NetBackup Client service starts On NetWare clients see the BPCD setting in the openv netback bp ini file Or instead of the first bullet under step c above On Windows NetBackup servers see the Client Properties dialog box in the Configure NetBackup window see Using the Host Properties Window on page 40 Correct the port number if necessary Then on Windows clients and servers stop and restart the NetBackup Client service On Microsoft Windows 98 or 95 and NetWare clients stop and restart the NetBackup client daemon bpcd Note 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 These numbers must be the same throughout your NetBackup configuration 5 Verify that the NetBackup Request Service bprd Port number on Microsoft Windows and NetWare clients is the same as on the server by default 13720 On Microsoft Windows clients use the same method as in step c unde
609. the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows but media is currently mounted and assigned Recommended Action Halt all jobs referencing media unmount all media and stop all applications from using Media Manager before trying to stop 1tid If unable to unmount media through the application interface check for the existence and permissions of the ltisymlinks file in the usr openv volmgr misc directory or in the NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes install_path Volmgr misc folder Invoke tpunmount filename for each line in the ltisymlinks file where filename specifies the contents of a line in that file For example on UNIX the command may look like the following tpunmount usr openv netbackup db media tpreq A00001 Device Management Status Code 21 Message The drive is not ready or inoperable Explanation A drive was selected for a mount request but the drive is not ready with loaded media Recommended Action Wait until the drive is ready before manually assigning a drive to a pending mount request Device Management Status Code 22 Message IPC Error Daemon may not be running Explanation A request to 1t id could not be serviced lt id is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows lt idi
610. the Media Manager volume configuration For a regular backup the volume is automatically set to the SUSPENDED state and not used for further backups For a NetBackup catalog backup the operation terminates abnormally Recommended Action If the volume was suspended wait until it expires and then replace it For NetBackup catalog backups replace the media NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 170 Message third party copy backup failure Explanation Usually indicates a problem with the 3pc conf file or the mover conf file For detailed causes see recommended actions For more information on these files refer to Creating Configuration Files for Offhost Backup in NetBackup Configuration chapter of the NetBackup ServerFree Agent System Administrator s Guide Recommended Action Ifanon third party copy device is listed in 3pc conf file correct or remove the non third party copy device entry An incorrect lun is specified in the 3pc conf file or the device does not exist Correct the 3pc conf file as appropriate An appropriate mover conf file with or without filename extension could not be found In this case the usr openv netbackup logs bptm log may also show the following 09 51 04 22281 lt 2 gt setup_mover_tpc no mover conf vertex_std_t
611. the configured port configured_port_number NetBackup Status Code 505 Can not connect to the NB Java user service on port port_number NetBackup Status Code 506 Chapter 4 NetBackup Status Codes and Messages 175 NetBackup 4 5 Troubleshooting Guide for Windows Messages NetBackup 4 5 Troubleshooting Guide for Windows Can not connect to the NB Java user service via VNETD on host or port configured_port_number NetBackup Status Code 577 cannot create log file NetBackup Status Code 257 Can not execute program NetBackup Status Code 509 cannot find configuration database record for requested NB database backup NetBackup Status Code 120 cannot find requested volume pool in Media Manager volume database NetBackup Status Code 167 cannot find the boot vault or profile in the vault configuration NetBackup Status Code 266 cannot find the local host name NetBackup Status Code 267 cannot get a bound socket NetBackup Status Code 146 cannot make required directory NetBackup Status Code 35 cannot overwrite media data on it is protected NetBackup Status Code 168 cannot perform specified media import operation NetBackup Status Code 176 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Messages cannot position to correct image NetBackup Status Cod
612. the following may appear in the usr openv netbackup logs bpbkar log bpbkar INF Processing var bpbkar ERR get _disk_info failed status 13 bpbkar ERR tpc_get_disk_info failed err 13 Chapter 4 NetBackup Status Codes and Messages 607 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes bpbkar ERR bpbkar FATAL exit status 13 file read failed bpbkar INF EXIT STATUS 13 file read failed The files to back up exist on a file system that is not mounted The file system specified as the frozen image source must be mounted If the frozen image source is not mounted but the mount point is present NetBackup may try to take a frozen image of the directory above the directory that was specified as the frozen image source NetBackup Status Code 14 Message file write failed Explanation A write to a file or socket failed Possible causes include I O error writing to the file system Write to a socket failed This can be caused by a network problem or a problem with the process reading from the socket Writing to a full disk partition Recommended Action Check the NetBackup Problems report for clues on where and why the problem occurred For detailed troubleshooting information create a debug log directory for the process that returned this status code retry the operation and check the resulting debug log Make sure that r
613. the operation and examine the logs 2 Use a media management interface to query for volumes associated with the pool specified for deletion Ensure that all volumes in a volume pool are reassociated with another pool before trying to delete the volume pool Use change volume operations to change the volume pool for a volume Check for possible volume database lock or seek errors Media Manager code 29 or 30 Media Manager Status Code 112 Message no pools in the pool list Explanation The volume pool list was unexpectedly found to be empty Recommended Action The volume pool list should contain a minimum of three pools None NetBackup and DataStore Investigate the integrity of the volume pool database usr openv volmgr database poolDB UNIX or install_path Volmgr database poolDB Windows on the host returning the error Restore the volume database from catalog backups As an alternative reinitialize the volume database to include the None NetBackup and DataStore volume pools To reinitialize it remove the volume pool database and make any request to vmd such as can be done by pointing a media management interface at the appropriate volume database host Media Manager Status Code 113 Message invalid expiration date Explanation A request was made to change the media expiration for one or more volumes in the volume configuration but the date specified was not valid Chapter 5 Media Manager Status Codes and Messages 257
614. the system directory typically C Winnt This ensures that all registry files are restored d Deselect the install_path Net Backup db install_path NetBackup var or install_path Volmgr database directories see the caution above e Select the Overwrite existing files option This ensures that existing files are replaced with the backups f Start the restore 11 Check the debug logs in the directories created in step 6 If there are any ERR or WRN messages resolve the problems before proceeding 12 Reboot the system This replaces any files that were busy during the restore When the boot process is complete the system is restored to the state it was in at the time of the last backup 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 The procedure for recovering a media server where the system disk has failed is the same as for a master server except that you use the following paths when running bprecover media_server_name install_path NetBackup db media media_server_name install_path NetBackup var media_server_name install_path Volmgr database In the above paths substitute the host name of the media server for media_server_name for example elk For install_path substitute the directory where NetBackup is instal
615. thin the Client read timeout or Client connect timeout period This has been seen to occur during incremental backups when directories have thousands of unmodified files For this case use Host Properties on the NetBackup server to change Client connect timeout or Client read timeout These settings are on the Timeouts and Universal Settings tabs respectively in the Master Server Properties dialog see Using the Host Properties Window on page 40 The default for these timeouts is 300 seconds You can also monitor CPU utilization to determine if this condition exists 2 On Windows systems try the following Disable the following file install_path Veritas NetBackup bin admincemd tracker exe Repair hard drive fragmentation You could try an application called Diskeeper Lite which is part of the Windows NT Resource Kit Make sure there is enough space available in temp Chapter 4 NetBackup Status Codes and Messages SL CN NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 3 Ifthe server cannot connect to the client create bpcd or bpbkar Windows only debug log directories on the client retry the operation and check the resulting logs If these logs do not provide a clue create a bpbbrm debug log on the server retry the operation again and check the resulting debug log If the bpbrm log has entries similar to the following bpbrm hookup_t
616. those catalogs is still intact The Media Manager catalog files are normally in the install_path Volmgr database directory Note The Media Manager device catalogs are binary files and you cannot restore them to a different type of platform Before Starting Reinstall the NetBackup software if necessary as explained in Master Server Disk Recovery on page 399 or Media Server Disk Recovery on page 405 Find the tape that has the latest catalog backups Ensure that the disk where you are restoring the catalogs contains the directory where the catalogs resided This is required because the bprecover command always restores the NetBackup catalogs to the path from which they were backed up alternate path restores are not allowed Recover Catalogs From Tape Media Manager Catalogs Lost If the NetBackup catalog backup is on tape and the Media Manager catalogs are lost specify a raw device path on the bprecover command This method involves mounting the backup tape in a drive and using the tpath parameter Note If the configuration was lost for the device that you plan to use for the recovery reinstall the device as explained in the Windows system documentation 1 Insert the catalog backup tape into an appropriate drive The example on Figure 3 shows a nonrobotic tape drive connected to a NetBackup master server ww 4 2 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting
617. tible version level Chapter 5 Media Manager Status Codes and Messages 349 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 3 Verify that robotic interfaces to vendor and operating system software have compatible versions Robotic Status Code 225 Message Robot hardware or communication error Explanation A hardware or communications error occurred between robotic and other components Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs 2 Resolve the situation by referring to troubleshooting methods or investigating the system log messages related to the specific error leading to the media mount failure 3 Verify that all Media Manager binaries are at a compatible version level Verify that robotic interfaces to vendor and operating system hardware and software have compatible versions Robotic Status Code 226 Message Requested slot contains the wrong tape Explanation The media in the requested slot is different from the media expected in that slot The volume configuration is no
618. ting Guide for Windows Recovering the NetBackup Catalogs If you have media servers bprecover includes their catalog paths in the prompts and you select the catalogs you want to recover The following example recovers only the catalogs for a media server named eel see Figure 4 Here you execute bprecover on the master server shark and use the dhost option to specify eel as the destination host bprecover r tpath Tapel dhost eel Recover shark install_path NetBackup db y n n n Recover shark install_path NetBackup var y n n n Recover shark install_path Volmgr database y n n n Recover eel install_path NetBackup db media y n n y Recovering eel install_path NetBackup db media Recover eel install_path NetBackup var y n n y Recovering eel install_path NetBackup var Recover eel install_path Volmgr database y n n y Recovering ee1 install_path 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 4 Recover Media Server Databases 8 mm tape drive Tape1 Media Server Master Server eel shark Tape with catalog backups install_path Netbackup db media install_path Netbackup db install_path Netbackup var install_path Netbackup var install_path Volmgr database install_path Volmgr database 5 After recovering catalogs for th
619. ting the Administration Console Enabling Detailed Debug Logging The NetBackup Administration Console 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 Administration Console This application server is made up of an authentication service and a user service The login request from the login dialog is sent to the authentication service for validation The user name and password have to be valid in the Windows UNIX authentication files process After validation the authentication service starts a user service under the user s account Thereafter all NetBackup administrative tasks are performed through that instance of the user service On both UNIX and Windows the authentication service is the bpj ava msvc application and the user service is the bpj ava usvc application Some of the recommendations in Chapter 4 refer to enabling detailed debug logging and examining log files These are the instructions for this activity 1 On the NetBackup client or server specified in the login dialog create the bpjava msvc and bpjava usvc debug log directories in the usr openv netbackup logs directory UNIX or in install_path Net Backup logs Windows Refer to Debug Logs earlier in this chapter for more information Note The NetBackup Java application server runs only on NetBackup UNIX clients On Windows the
620. ting to the device configuration database files lt idevs and robotic_def located in the directory usr openv volmgr database UNIX or in the folder Chapter 5 Media Manager Status Codes and Messages 239 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows install_path Volmgr database Windows Display the device configuration to determine whether or not the database is corrupt and restore a saved copy of the databases from catalog backups or delete them and recreate the device configuration as needed Device Configuration Status Code 13 Message Failed reading drive or robot config file Explanation A request was made to change or list the device configuration but an error was encountered while reading from the device database Recommended Action 1 Examine the daemon debug log and command or interface output for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs Examine the permissions and check for the existence of the device configuration database files ltidevs and robotic_def located in the directory usr openv volmgr databas
621. tion for media and devices Media Manager Functional Description This section explains the operation of Media Manager software and contains the following discussions Startup Process Media and Device Management Process Barcode Operations ww 450 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description 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 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 The easiest way to start Media Manager is to initiate all the necessary processes during system startup on all servers that have devices under control of Media Manager 1tid automatically starts other daemons and programs as necessary Figure 13 shows the Media Manager daemons that should be running after initial startup In the case of robotic daemons such as ts8d and rsmd the associated robot must also be configured for the daemon to run See Table 9 for other ways to start and stop these daemons As shown on Figure 13 the LMF TL8 TLH and TLD require two types of daemons robotic and robotic control Each host with a robotic
622. tion will relate the media with its known home slot location Media Manager Status Code 101 Message media type and volume group mismatch Explanation A request was made to add volumes or change volume residences in the volume configuration and the media type and volume group associated with the volume configuration changes are in conflict with the requirements for volume groups All volumes in a volume group are required to have the same residence which includes having the same media type Media types used for data and their associated cleaning media types are considered as being the same media types with regard to volume group restrictions Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 Ensure that the specified media type and volume group are compatible with other volumes in the volume configuration that are in the specified volume group Choose a different
623. tions are lost This is a total recovery In both cases you restore the server to the state it was in at the time of the most recent backup of the NetBackup catalogs If the recovery is successful reconfiguration is unnecessary Recovery When Windows is Intact This procedure assumes that Windows will boot and is not corrupt The general steps are to restore NetBackup and then restore all other files Figure 1 illustrates the procedure NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Master Server Disk Recovery Figure 1 Recover Master Server Windows Intact overview Master Server Disk to restore Shark Repartition the disks Install NetBackup Install any NetBackup patches Tape Drive Update external mapping files Enable debug logging D g e O N Stop all NetBackup services except the NetBackup Client service 7 Recover NetBackup catalogs install_path NetBackup db install_path NetBackup var install_path Volmgr database Tape with catalog backups lt q fee Start all NetBackup services Tape with other backups Restore all other files do not restore catalogs 10 Check debug logs and correct any problems 11 Reboot the system Before Starting Verify that you have NetBackup server software for Windows The latest NetBackup catalog backup on
624. tis not possible to delete assigned volumes If no worthwhile data is on the volume unassign the media using the appropriate application interface which is bpbexpdate for NetBackup and then retry the delete volume request For optical media if no worthwhile data is on either side of the platter unassign both of the volumes before attempting to delete them Media Manager Status Code 93 Message volume is already assigned Explanation A request was made to assign a volume and the volume was already assigned or for optical media the volume partner was already assigned Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Do not try to manually assign volumes that are already assigned because it is not valid except for one condition you can assign volumes for NetBackup catalog backups if the volume is already assigned for NetBackup catalog backups Check the device configuration to determine if the volume database host for the device is consistent with the volume configuration in the volume database Applications may attempt to query multiple volume da
625. to 100 A value of 100 increases the speed and efficiency of disk cache writes by increasing the number of write requests that can be executed at one time Change to or add the following settings in the Novell sys system autoexec ncf file SET Maximum Packet Receive Buffers 4000 SET Maximum Directory Cache Buffers 4000 SET Maximum Concurrent Disk Cache Writes 2000 SET Maximum Concurrent Directory Cache Writes 2000 SET Maximum Physical Receive Packet Size 1514 On NT 2000 master servers check the LIST_FILES TIMEOUT value and ensure that this value is at least 1800 5 For NetBackup for EMC Fastrax Increase the CLIENT_READ_TIMEOUT and CLIENT _CONNECT_TIMEOUT values in the server s usr openv netbackup bp conf file and retry the operation Although the optimal time out values for your system may be different the following values may suffice CLIENT READ TIMEOUT 3000 Chapter 4 NetBackup Status Codes and Messages 73 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows CLIENT CONNECT TIMEOUT 3000 NetBackup Status Code 24 Message socket write failed Explanation A write operation to a socket failed Recommended Action 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 debug log directories for the processes that could have returne
626. to the device to see whether it is responsive Verify that there are no unexpected Media Manager processes running by executing vmps Some processes are expected to remain running but some processes that do not go away could indicate a more serious problem such as a hung system call Robotic Status Code 213 Message Drive does not exist in robot Explanation A targeted drive was not found in the robotic library The drive configuration may be incorrect Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry the operation and examine the logs NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 2 Attempt to obtain the list of drives using a method that involves a robotic library query such as that available from the robot test utility Compare the list of drives returned against the device configuration Ensure that 1t id the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows was stopped and restarted after changes were last made to the device configur
627. tomatically Check the inetd log to see if NetBackupListen is running Check the bpbkar and tar messages in the bpcd log file To increase the logging level set the loglevel parameter in the mac conf file to a higher value 3 Ona Windows client create the bpbkar debug log directory on the client 4 On Windows clients verify that the NetBackup Client service is running 5 Retry the backup and examine the debug logs for clues on the cause of the failure er 92 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup Status Code 65 Message client timed out waiting for the continue message from the media manager Explanation The tape manager bptm reported that the media did not load and position within the allotted time Recommended Action Verify that the requested volume is available and the required device is in an UP state For detailed debug information 1 Create a bptm debug log directory on the server 2 Ona Windows NetBackup server set the Verbose logging level option on the Universal Settings tab in the Master Server Properties dialog see Using the Host Properties Window on page 40 3 Retry the operation and check the bptm debug log file for information on the drive robot and tape that is causing the timeout 4 Ona Windows NetBackup server master or media check the Event
628. tput if available debug logs and system logs for messages related to the error Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting Itid the device daemon on UNIX or NetBackup Device Manager service on Windows 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Check the installed software components and verify that they are all at a compatible release version Device Management Status Code 33 Message Error in SEMAPHORE operation Explanation A process was unable to perform a semaphore operation such as lock or unlock associated with resources maintained by 1t id 1tid is the Media Manager device daemon on UNIX or the NetBackup Device Manager service on Windows Recommended Action 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 On UNIX servers gather the output of the ipcs a command to see what resources are currently in use Device Management Status Code 34 Message Error in getting semaphore for operator
629. tware is installed b Verify that the bpcd and bprd port numbers in the sSystemRoot system32 drivers etc services file on the server matches the setting on the client c Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog match the bpcd and bprd settings in the services file To display this dialog start the Backup Archive and Restore interface on the server and click NetBackup Client Properties on the File menu The values on the Network tab are written to the services file when the NetBackup Client service starts Chapter 4 NetBackup Status Codes and Messages 89 or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes d Verify that the NetBackup client service is running e On Windows systems for NetBackup 3 0 to NB3 1 1 the install_path winnt system32 drivers etc services file may not have correct information The following entries are correct bpcd 13782 tcp bprd 13720 tcp f Use the following command to see if the master server returns correct information for the client install_path Veritas NetBackup bin admincmd bpclntcmd pn 2 Fora Macintosh or NetWare target client verify that the server is not trying to connect when a backup or restore is already in progress on the client These clients can handle only one NetBackup job at a time 3 Pe
630. tween components or versions of the product Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Check the tpconfig or tpautoconf usage statement for expected usage and compare with the parameters being sent to start the new process 3 Verify that all Media Manager binaries are at a compatible version level Device Configuration Status Code 12 Message Failed writing drive or robot config file Explanation A request was made to change the device configuration but an error was encountered while writing to the device database Recommended Action 1 Examine the daemon debug log and command or interface output for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option b Retry the operation and examine the logs 2 Examine the permissions and available file system space for wri
631. type 4mm belonging to robot tl4 1 This is an error because a Backup Exec media of type dlt having barcode EFG00 cannot be associated with a Media Manager volume record having media type 4mm Backup Exec media cannot be associated with a Media Manager volume record of an incompatible robot type NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows beconv Error Messages Recommended Action Examine the Media Manager volume record having the same barcode as the Backup Exec media Is the Media Manager media type of the volume record really the media type of the media to which the record corresponds Update the Media Manager volume record accordingly either manually with add change delete volume operations or by using the NetBackup robot inventory update and run beconv again Message Null guid in volume record Explanation This happens when a user runs beconv with the beconv m media_id option but media_id has a NULL ADAMM GUID in the Media Manager volume database When beconv is run with the beconv m media_id option media_id should always have a non NULL ADAMM GUID Recommended Action Run bpimport and also bephyinv if required for that media ID Message Media having guid XXX not present in Backup Exec database Explanation This happens when a user runs beconv with the beconv m media_id option but the ADAMM GUID f
632. ubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows NBNWNT EXE 448 NBWIN 426 427 435 436 nbwin log 47 NBWIN EXE 448 ndmpmoveragent overview 447 NetBackup Administration Console debug logging 53 errors 51 NetBackup Client service start and stop 9 NetBackup Database Manager service start and stop 9 NetBackup Device Manager service start and stop 9 NetBackup Request Manager service start and stop 9 NetBackup Volume Manager service start and stop 9 NetBackupBPCD 429 438 448 NetBackupListen 429 438 449 Network connections multiple 467 Network problems PC clients 21 Novell values affecting restore 73 74 odld description 460 Operating system errors 52 output redirect to a file 54 pass thru not supported 15 patches installing during recovery 401 404 407 pathname length 56 Preliminary troubleshooting procedure 7 Problems report 43 Procedures recovery master when NT intact 399 media server disk 405 NetBackup catalogs 409 NT client disk 406 NT master server disk 399 total on master 402 troubleshooting communications problems 21 host names and services 25 installation and configuration 10 introduction 7 master server and clients 16 media server and clients 19 preliminary 7 Processes see Functional overview Programs Media Manager 458 NetBackup 441 Progress logs user 44 Raw partitions backup process 422 restore process 432 Recording information
633. ued by running the command vmpool listall b Check the user ID and group ID on UNIX by executing the id 1M system command Change the volume pool user and or group ID security with vmpool or another user interface that supports volume pool user and group attributes Change the volume pool associated with the volume if it is not assigned or log in with user group ID permissions to use media in the targeted volume pool Then resubmit the mount request Device Management Status Code 69 Message Request terminated because media is unmountable Explanation A mount request has been canceled because the media being requested is not mountable The same media has been found to be unmountable in at least two different drives Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Check integrity of the drive drive path and media 2 Verify that the media is not a misconfigured cleaning tape Device Management Status Code 70 Message Request terminated because media is write protected Explanation A mount request has been canceled because the media being requested for write access is not write enabled Recommended Action Check the physical media cartridge to see whether write protection has been enabled If write access to the media is desired disable write protection for the media If re
634. ug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Check the usage statement for expected usage and compare with the parameters being sent to start the new process 3 Verify that all Media Manager binaries are at a compatible version level Media Manager Status Code 5 Message daemon resources are busy Explanation A requested operation could not be processed because resources were busy Recommended Action Check the status of any resources used by the requested operation On a robotic inventory request verify that the inventory operation completes within the allotted time 7 minutes for robot types ACS LMF RSM TLH TLM TS8 TSD TSH and 32 minutes for other robot types Media Manager Status Code 6 Message invalid protocol request Explanation An invalid request was sent to a Media Manager robotic process or operator request process Recommended Action Chapter 5 Media Manager Status Codes and Messages 203 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 Examine command output debug logs and system logs for a more detailed message on the error as follows a If not already enabled enable debug loggin
635. ully under a non administrator account but the NetBackup Client service is not added to Windows and the NetBackup server cannot access the client Chapter 4 NetBackup Status Codes and Messages 1 ON NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Verify that the Windows TCP IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers 7 Ifthe preceding steps do not resolve this problem see Resolving Network Communication Problems on page 21 8 If NetBackup is using multiple network interfaces with slave servers make sure the interface names appear in the client s usr openv netbackup bp conf file NetBackup Status Code 63 Message process was killed by a signal Explanation A kill signal was sent to the client process Recommended Action This is usually caused by someone intentionally terminating a backup NetBackup Status Code 64 Message timed out waiting for the client backup to start Explanation The client did not send a ready message to the server within the allotted time Recommended Action 1 On all but Macintosh clients enable bpcd debug logging as follows a Create a bpcd debug log directory on the client b Increase the debug or log level as explained in the debug log topics in Chapter 3 2 On Macintosh clients check the inetd and bpcd debug logs Both logs are created au
636. up Activity Monitor or the Services application in the Windows Control Panel to stop the following services NetBackup Request Manager service NetBackup Database Manager service NetBackup Device Manager service NetBackup Volume Manager service 2 Execute the bprecover command to recover the catalogs For example the following command recovers the D VERITAS NetBackup db catalogs from disk path D apps dbbackup on Figure 5 bprecover r 1 dpath D apps dbbackup Recovering shark D VERITAS NetBackup db NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBackup Catalogs Figure 5 Recover Catalogs From Disk Master Server shark D apps dbbackup oF IMAGE 1 D VERITAS Netbackup db IMAGE 2 N D VERITAS NetBackup db DAVERITASWolmgrdatabase 3 D VERITAS Wolmgr database 3 After recovering the catalogs use the NetBackup Activity Monitor or the Services application in the Windows Control Panel to start the following services NetBackup Request Manager Service NetBackup Database Manager Service NetBackup Device Manager Service NetBackup Volume Manager Service Chapter 6 Disaster Recovery 417 m NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Recovering the NetBack
637. up Catalogs wr 418 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Functional Overview A This appendix provides a functional overview of NetBackup for both UNIX and Windows 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 There are two main sections in this appendix Backup and Restore Functional Description Media Manager Functional Description It is assumed that you are already familiar with the overviews in the first chapter of the NetBackup System Administrator s Guide for UNIX and the Media Manager System Administrator s Guide for UNIX Note that this appendix does not pertain to the NetBackup products for backing up relational databases such as NetBackup for ORACLE The installation guides for those products have information regarding their operation Backup and Restore Functional Description This section explains the operation of NetBackup during backup and restores and contains the following discussions Startup Process Backup and Archive Processes Restore Processes NetBackup Directories and Files NetBackup Databases NetBacku
638. up Remote Administration Console 2 Click Host Properties 3 Select the servers or clients where you want to make the change 4 Select Properties from the Actions menu 5 Inthe properties dialog box that appears select the appropriate tab and make your change Many procedures in this guide also refer to the NetBackup Client Properties dialog in the Backup Archive and Restore interface on Microsoft Windows clients This dialog lets you change NetBackup configuration settings only for the local system where you are running the interface Most settings in the NetBackup Client Properties dialog are also available in the Host Properties window 40 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Using the Logs and Reports 3 NetBackup produces the following categories of information that you can use for troubleshooting problems Reports Status for User Operations Windows Event Viewer Application Logs Debug Logs Media Manager Logs Windows Event Viewer Logging Option Troubleshooting the Administration Console Note The format of the entries in the NetBackup logs is subject to change without notice The following figure shows whether this information is available on the client or server and the processes involved in making the information available The remaining topics in this
639. up patches that had previously been installed 6 Enable debug logging by creating the following debug log directories on the client Chapter 6 Disaster Recovery 407 NetBackup 4 5 Troubleshooting Guide for Windows Vv NetBackup 4 5 Troubleshooting Guide for Windows Client System Disk Recovery Windows 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 7 Fora Windows NT 2000 client stop and restart the NetBackup Client Manager service This enables NetBackup to start logging to the bpinetd debug log 8 Fora Windows 98 or 95 client stop and restart the NetBackup Client Daemon This enables NetBackup to start logging to the bpcd debug log 9 Use the NetBackup client user interface to restore the system and user files to the client system For example if all files are on the C drive restoring that drive restores the entire system To restore files you do not have to be the administrator but you must have restore privileges For example on Windows NT 2000 you must be a member of the Restore group which is one of the built in Windows NT 2000 groups Refer to the online help or NetBackup User s Guide for Microsoft Windows for instructions on how to restore files Note NetBackup restores the registry when it restores the Windows system files For
640. up server list On a Windows server the master is designated on the Servers tab in the Master Server Properties dialog To access this dialog see Using the Host Properties Window on page 40 3 On Windows servers Chapter 4 NetBackup Status Codes and Messages 1370 r NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows a Verify that the bpcd entries are correct in the services file sSystemRoot system32 drivers etc services b Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Configuration dialog match the settings in the services file To display this dialog start the Backup Archive and Restore interface 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 c Stop and restart the NetBackup services 4 See Testing Media Server and Clients on page 19 and Resolving Network Communication Problems on page 21 5 Create a bpcd debug log directory on the server that has the storage unit and retry the operation Then check for additional information in the resulting debug log NetBackup Status Code 206 Message access to server backup restore manager denied Explanation The master server is trying to start a process on another server or itself and the master server
641. ups excluded any files that resided in the above directory it is possible that you will not be able to restore the system so it completely matches its previous configuration Defective hardware has been replaced Before Starting Verify that you have the following Windows system software to reinstall on the NetBackup client that is being restored Reinstall the same type and version of software that was previously used For example do not install Windows NT Server 4 0 software if before the failure the system was a Windows NT 4 0 workstation Fora Windows NT 2000 client this software must be Windows NT Server or Workstation 4 0 or above or Windows 2000 NetBackup 3 0 or later client software to install on the client that is being restored wr 406 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Client System Disk Recovery Windows 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 You must duplicate that scheme during Windows installation To Recover a Windows Client Disk 1 Install a minimal Windows operating system perform the Expr
642. us Code 293 Message eject process has been aborted Explanation This error occurs when the eject processing has been aborted This error could be encountered during a vault job or when using vlteject or the vltopmenu eject command This error can occur because of one of the following conditions Chapter 4 NetBackup Status Codes and Messages 159 a NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Could not open a pipe to vmchange verify_eject call Unexpected output from vmchange verify_eject call There are no MAP elements to eject media into The robotic library had problems putting media into the MAP The user hit Return in interactive mode without first removing the media from the MAP In this case the media that were in the MAP will be put back into their original slots in the robotic library Recommended Action For detailed information about why the process was aborted review the vault debug log in the following directory UNIX usr openv netbackup logs vault Windows install _path NetBackup logs vault Also review the detail 1og in each of the sidxxx directories that had problems UNIX usr openv netbackup vault sessions vault_name sidxxx Windows install _path NetBackup vault sessions vault_name sidxxx where xxx is the session id This error often indicates that the media were left in the offsite vault volu
643. ve completed was successful but the delete failed Recommended Action Verify that you have permission to delete the files and that the read only flag is not set for the files Since the backup was successful you can delete the files that were backed up or have the system administrator delete the files if you do not have the necessary permissions NetBackup Status Code 5 Message the restore failed to recover the requested files Explanation There were errors that caused the restore to fail 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 status on the client for messages on why the restore failed Also check the All Log Entries report on the server 3 Check ownership and permission on directories where files will be restored 4 Correct problems that you find and retry the restore 5 For NetBackup for EMC Fastrax you may need to increase the CLIENT READ TIMEOUT and CLIENT _CONNECT TIMEOUT values in the server s usr openv netbackup bp conf file Although the optimal time out values for your system may be different the following values may suffice CLIENT READ TIMEOUT 3000 CLIENT CONNECT TIMEOUT 3000 The safest approach is to increase the timeout values and rerun the restore Note however that the Fastrax system may have completed the restore successfully on its own even though N
644. veritas com for ordering information Recommended Action Obtain a licensed copy of NetBackup which includes Media Manager NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Media Manager Status Code 166 Message media access port not available Explanation A request was made to physically move a volume into or out of a robotic library but the media access port was found to be unavailable Recommended Action 1 Examine command output if available debug logs and system logs for a more detailed message on the error a Ifit is not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Ensure that the physical move volume request for the robot type was not sent to a robotic control daemon process on a system running an older incompatible version of the software 3 Ensure that the targeted robotic control daemon process is operating normally Media Manager Status Code 167 Message ADAMM GUID is not unique in the database Explanation A volume entry being added to or changed in the volume database had an ADAMM GUID specified which was a duplicat
645. vice requests Look for entries in the Media Manager configuration file vm conf that increase the load Consider placing the volume database on a higher performance server and file system if performance is an issue Consider using inventory filtering for robot types that support it to reduce the number of volumes in the volume configuration Chapter 5 Media Manager Status Codes and Messages 235 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 7 By checking utilities such as ipcs a ensure that shared memory is functioning properly The oprd process may not be responding because it is having trouble attaching to shared memory Media Manager Status Code 71 Message failed sending to vmd Explanation An attempt to write data to a vmd socket failed vmd is the Media Manager volume daemon UNIX or NetBackup Volume Manager service Windows Recommended Action 1 Examine command output if available and the daemon and reqlib debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Identify the system where vmd is running This is usual
646. viced by oprd rdevmi that may have failed include down up reset drives change drive comments deny resubmit mount requests assign drives start stop ltid obtain ltid status display drive status manage pending actions set NDMP attributes configure devices format optical platters clean drives obtain host version and device configuration information and scan shared drives Media Manager Status Code 97 Message rule does not exist in rule database Explanation A request was made to change or delete a barcode rule and no barcode rule having the specified barcode tag could be found Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 List the configured barcode rules on the targeted volume database host Adjust the barcode tag specified on the change delete request or the targeted host as appropriate so that the barcode rule is found when the request is retried 250 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes
647. volume is mounted The recorded media ID should match the external media ID redirected restore different client 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 redirected restore different target 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 redirected restore different path Restores files to a different directory than the one from which they were backed up registry A Microsoft Windows database that has configuration information about hardware and user accounts remote administration console A Windows NetBackup client that has the administration interface software installed and can be used to administer NetBackup servers 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 This residence entry contains information such as robot number robot host robot type and media type resource A Novell NetWare term that refers to a data set on the target For
648. was encountered Explanation A request to the bpdbm process NetBackup Database Manager service had invalid or conflicting information This is usually a result of using software from different versions together but can also be caused by incorrect parameters on a command Recommended Action Verify that all NetBackup software is at the same version level and the command parameters are specified correctly If neither of these is the problem obtain detailed troubleshooting information by creating a bpdbm debug log directory and retrying the operation Check the resulting debug log NetBackup Status Code 224 Message there was a conflicting specification Explanation A request to the bpdbm process NetBackup Database Manager service had conflicting information This is usually a result of using software from different version levels together Recommended Action Verify that all NetBackup software is at the same version level If that is not the problem obtain detailed troubleshooting information by creating bpdbm and admin debug log directories and retrying the operation Check the resulting debug logs NetBackup Status Code 225 Message text exceeded allowed length Chapter 4 NetBackup Status Codes and Messages 145 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows Explanation A request containing text that exceeds a buffer size was made to the bpdbm pr
649. ween 1tid and the 8 mm Tape Stacker and communicates with the robotics through a SCSI interface Started By Starting 1t id or on UNIX independently by using the usr openv volmgr bin ts8d command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id vmd The Media Manager volume daemon NetBackup Volume Manager service on Windows manages the volume database provides 1tid with the location of requested volumes keeps track of the number of mounts and last mount time for each volume and allows remote administration and control of Media Manager Started By Starting 1tid or on UNIX independently by using the Initiate Media Manager Volume daemon option in vmadm Stopped By Terminate Media Manager Volume Daemon option in vmadm Debug Log System log and also a debug log if the daemon or reqlib debug directories exist see Debug Logs on page 47 vmadm Available only on UNIX An administrator utility with options for configuring and managing volumes under control of Media Manager It has a menu driven character based interface that can be used from workstations that do not have graphical displ
650. where NetBackup logs are stored by default C Program Files VERITAS NetBackup logs The partition where the operating system is installed Use Disk Administrator or Explorer to view disk partition information 5 Enable verbose logging either for everything or just for areas you think are related to the problem See the Using the Logs and Reports chapter for information on verbose logging Note If you are using ACS robotic control the acsssi and acssel processes will remain running when 1tid is stopped For more information about stopping these daemons refer to the Automated Cartridge System ACS Appendix in the NetBackup Media Manager System Administrator s Guide 6 On Windows NetBackup servers verify that the required services and processes are running a Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel to start the following services if they are not running Note To start all of them execute install_path Net Backup bin bpup exe On NetBackup master servers NetBackup Request Manager service NetBackup Database Manager service NetBackup Device Manager service if the system has devices configured NetBackup Volume Manager service NetBackup Client service Chapter 2 Troubleshooting Procedures 9 lt NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Troubleshooting Installation and Co
651. wing is a possible scenario 1 Host A reserves a shared drive 2 Host A becomes unavailable for some time unable to communicate with other hosts 3 Host B determines that the host having the reservation Host A is no longer available and makes a request to vmd DA denoting Host A as unavailable 4 The host originally owning the drive reservation tries to release the drive Recommended Action Correct the network or process problem that led to the communications problem Ensure that unique non duplicate strings are being used for host names and for SSO_HOST_NAME configuration file entries NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes Media Manager Status Code 135 Message requested host is not currently registered Explanation A request was made to reserve or release a shared drive or designate a host as unavailable with vmd DA the device allocator for the Shared Storage Option The host reserving or releasing the drive or being designated as unavailable was not registered with vmd DA This is an abnormal condition that could occur in the following situations 1 vmd DA was stopped and restarted This situation will be automatically handled because the requesting host re registers its drives with vmd DA when this error is encountered 2 A host has been unregistered with vmd DA and another host
652. xamine command output if available and debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 If possible re attempt the requested operation using another user interface that supports the type of request Media Manager Status Code 15 Message invalid volgroup Explanation A requested operation encountered a case where the volume group was either not specified not in an acceptable format or exceeded the allowed length of a volume group Recommended Action 1 Examine command output if available and debug logs for a more detailed message on the error as follows a If not already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify a volume group where one is required ensuring that it is no longer than 25 ASCII characters in length without containing any whitespace or unprintable characters Media Manager Status Code 16 Message inva
653. xamine command output if available and debug logs for a more detailed message on the error as follows a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or by executing the command s verbose option if available b Retry the operation and examine the logs 2 Specify a robot type that supports the volume s media type 3 Check the volume database and ensure that the specified robot type agrees with that for all volumes having the specified robot number 4 Ifa robot type is required for the requested operation ensure that a robot type has been specified Media Manager Status Code 13 Message invalid robot number Explanation The robot number was not specified or was not within the allowable range Recommended Action Specify a robot number in the range of 0 to 32767 Media Manager Status Code 14 Message invalid robot host Explanation A requested operation encountered a case where the robot control host was either not specified not valid for the given robot type not in an acceptable format or exceeded the allowed length of a robot control host name Recommended Action Chapter 5 Media Manager Status Codes and Messages 207 ar NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Troubleshooting Guide for Windows 1 E
654. xpiration date has expired Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available and debug logs for a more detailed message on the error a Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the daemons services or execute the command s verbose option if available b Retry the operation and examine the logs 2 Change the volume expiration date to a future date in relation to the current system date time if you want to extend the active life of the physical media Alternatively replace the media with other media that still has useful life remaining Check the system date time and reset it correctly as needed 3 Ifthe media expiration is already set to a future date as compared to the current system date check the device configuration to determine if the volume database host for the device is consistent with the volume configuration in the volume database Applications may attempt to query multiple volume databases for volume related requests so ensure that duplicate media IDs are not used in volume configurations across multiple hosts If duplicate IDs are found either completely separate the configurations by not sh
655. xplanation A robotic eject media operation returned a status indicating that the media access port contains one or more cartridges The operator or administrator may not have removed media from the media access port as part of the latest or a previous eject operation Recommended Action 1 Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting lt id the device daemon on UNIX or NetBackup Device Manager service on Windows Retry the operation and examine the logs 2 Coordinate inject eject operations between all operators and administrators Ensure the media access port is empty of media before starting an eject operation Robotic Status Code 222 Message Robotic arm has no addressable holder Explanation An element of the robot is missing a holder and cannot be used Recommended Action NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Status Codes 1 Examine command output if available debug logs and system logs for messages related to the error a Enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting 1tid the device daemon on UNIX or NetBackup Device Manager service on Windows b Retry t
656. y 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 When working with NetBackup database extensions make sure that the applicable database product has the correct permissions allowing NetBackup to write to the progress log on the client 3 Check the services file On Windows verify that the sSystemRoot system32 drivers etc services file has the correct entries for bpcd bpdbm and bprd Also verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog match the settings in the services file To display this dialog start the Backup Archive and Restore interface and click NetBackup Client Properties on the File menu The values on the Network tab are written to the services file when the NetBackup Client service starts Also see Verifying Host Names and Services Entries on page 25 4 On Windows verify that the recommended service packs are installed 5 When the base NetBackup BusinesServer or DataCenter license key expires daemons such as bprd and bpdbm will terminate on the NetBackup server If these daemons are not running you are likely to encounter status code 25 errors in the Administration GUIs Install a valid base NetBackup license key restart the daemons and restart the GUI NetBackup Status C
657. y Inc Created 1991 All rights reserved VERITAS NetBackup Troubleshooting Guide for Windows VERITAS Software Corporation 350 Ellis Street Mountain View CA 94043 USA Phone 650 527 8000 Fax 650 527 8050 www veritas com NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Contents Preface iar tire idea darter ahaa Giese arene ae ob 4 ayere kau kaaned mal di aE a ix AUCICNCC Hii a EEE REE Ree Ree theca Rae LTE ETE EET ELETE EEEE ix OPP ANUZ ALON seerste spekei Petes E Ei E AE diem Wh dee Aig dese E S ix Related Mariuals c vsscevedendduedvde cs dhceueda sishoesedeesbiootaiasseabes4 x PSCCOSSIDINEY sae pea bine meen Mies eilecs es tees nie Merete e rate Ges eile eet ere ite x Conventions che ih died acer adee dae he eek amp aly chao EEEE E EEE aie eae x Type Style etait ied ae ead bel Gaetan Le Maddie pana x Notes and Cautions ss eid vee ee ds e ae feeds aed evel EEANN Hod xi Key Combinations s sisi meegee acerca nant ieee EE ee E E Been eave te A aE lends ence RE xi Command Usage sermi iii i ee EERE E ETE os xi TETS sereron ei i aH Ri eae OS OME 6 a Ee ee xii Getting Help sv isscccvecevbsecrede crtiirede orinineiede bide daedes tee EEDE E xii Chapter 1 Introduction 000 rrrncn nnne es 1 Define the Problemi wv 51 50 kusdo ciado ns haakt a Saeed sadder hi oosadasvhabens 1 What was the Error Indication resist entant eee tence 1 What Were You
658. y Starting 1t id or on UNIX independently by using the usr openv volmgr bin tldd command Stopped By Stopping 1tid or on UNIX independently by finding the PID process id and then using the ki11 command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id tldcd The Tape Library DLT Control daemon provides robotic control for a TLD robot in the same manner as explained previously for t18cd Started By Starting 1t id or on UNIX independently by using the usr openv volmgr bin tldcd command Stopped By Using the tldcd t command Stopping 1tid or by using the tlded t command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the Media Manager configuration file vm conf On UNIX debug information is also included by starting the daemon with the v option either by itself or through 1t id 462 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Manager Functional Description Table 9 Media Manager Daemons and Programs continued Program Description Daemon tlhd The Tape Library Half inch daemon works in conjunction with tlhed to ha
659. y NetBackup patches that had previously been installed 5 Update the external mapping files 6 Enable debug logging by creating the following directories install_path NetBackup logs tar install_path NetBackup logs bpinetd 7 Start the NetBackup Client service and stop all other NetBackup services Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel 8 Use the bprecover command to recover the NetBackup catalogs Choose one of the procedures under Recovering the NetBackup Catalogs on page 409 9 When catalog recovery is complete start the NetBackup services that are not already running Use the Activity Monitor or the Services application in the Windows Control Panel Caution In step 10 do not restore files to the install_path NetBackup db install_path Net Backup var or install_path Volmgr database directories These directories were recovered in step 8 and overwriting them with regular backups will leave the catalogs in an inconsistent state 10 Restore all other files a Start the NetBackup Administration interface on the master server b Start the Backup Archive and Restore utility c Browse for restores and select all partitions wr 404 NetBackup Troubleshooting Guide Windows NT 2000 NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows Media Server Disk Recovery It is especially important to select
660. y for bptm and retry the operation Check the resulting debug log files NetBackup Status Code 95 Message requested media id not found in NB media database and or MM volume database Explanation An operation was requested on a media ID for which NetBackup does not have a record An example of this is using bpmedia to suspend or freeze a media ID that does not exist Recommended Action Run a NetBackup Media List report to determine the valid media IDs Then retry the command with a valid media ID NetBackup Status Code 96 Message unable to allocate new media for backup storage unit has none available Explanation The tape manager bptm could not allocate a new volume for backups This indicates that the storage unit has no more volumes available in the volume pool for this backup Recommended Action Check the NetBackup Problems report to determine the storage unit that is out of media 1 Ifthe storage unit is a robot and there are empty slots add more volumes remember to specify the correct volume pool Ifthere are no empty slots move some media to nonrobotic and then add new volumes Ifyou are having difficulty keeping track of your available volumes try the available_media script On Windows the script is in install_path NetBackup bin goodies available media cmd Chapter 4 NetBackup Status Codes and Messages 105 NetBackup 4 5 Troubleshooting Guide for Windows Status Codes NetBackup 4 5 Tr
661. y hostname_from_ client client_as_known_by_server Where keyis a numeric value used by NetBackup to specify the cases where the translation is to be done Currently this value must always be 0 indicating a configured name translation Appendix B Networks and Hostnames 469 Or NetBackup 4 5 Troubleshooting Guide for Windows NetBackup 4 5 Troubleshooting Guide for Windows hostname_from_clientis the value to translate This must correspond to the name that is obtained by the client s gethostname function and sent to the server in the request client as_known_by_ serveris the name to substitute for hostname_from_client when responding to requests This name must be the name configured in the NetBackup configuration on the master server and must also be known to the master server s network services For example the line 0 danr danr eng aaa com specifies that when the master server receives a request for a configured client name numeric key 0 the name danr is always replaced by the name danr eng aaa com This resolves the problem mentioned above assuming that The client s gethostname function returned danr The master server s network services gethostbyname function did not recognize the name dant The client was configured and named in the NetBackup configuration as danr eng aaa com and this name is also known to network services on the master server 470 NetBackup Troubleshooting
662. y on the client b Increase the debug or log level as explained in the debug log topics in Chapter 3 c Retry the backup and examine the resulting logs to determine the cause of the failure 3 On all but Macintosh clients enable bpcd debug logging as follows a Create a bpcd debug log directory on the client b Increase the debug or log level as explained in the debug log topics in Chapter 3 c Retry the backup and examine the resulting logs to determine the cause of the failure 4 On Macintosh clients check the inetd and bpcd debug 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 Lloglevel parameter in the mac conf file to a higher value 5 Check the bpcd debug log to determine the server s peername and what comparisons are being made The bpcd process compares NetBackup server list entries to the peername of the server attempting the connection and rejects the connection if the names are different If necessary change the server list entry on the client to match the peername 6 On Windows clients check the following Verify that NetBackup for Windows software was installed under a Windows administrator account If NetBackup is under another type of account reinstall it under an administrator account The installation will complete successf
663. yed in the command or utility interface output Recommended Action Examine the daemon debug log and command or interface output for a more detailed message on the error 1 Ifnot already enabled enable debug logging by creating the necessary directories folders Increase the level of verbosity by adding the VERBOSE option in the vm conf file and restarting the volume daemon NetBackup Volume Manager service or start vmd with the verbose option 2 Retry the device configuration request and examine the logs Device Configuration Status Code 37 Message Residence is not licensed for shared drive support Explanation On a request to add or update a drive in the device configuration the drive was specified as shared but there is no support for shared drives for that drive type or for the type of robot associated with the drive Recommended Action Check www veritas com and product release documentation for supported device configurations Device Configuration Status Code 38 Message Current version does not support remote device host Explanation On a request to change the global device database host or the volume database host for a residence the specified host is not the local host and the current software is not licensed to allow remote hosts Recommended Action Check product documentation for supported device configurations Obtain an additional software license that allows remote hosts to be configured or specify only

NetBackup 4.5 Troubleshooting Guide for Windows

Contents

Download Pdf Manuals

Related Search

Related Contents