Home

Symantec NetBackup™ Troubleshooting Guide: UNIX

1. Note During the catalog recovery process services may be shut down and restarted If NetBackup is configured as a highly available application cluster or global cluster freeze the cluster before starting the recovery process to prevent a failover Then unfreeze the cluster after the recovery process is complete The steps are the same as those in the following topic See Recovering the entire catalog using the Catalog Recovery Wizard on page 201 208 Disaster recovery How to recover a catalog from a backup To recover the entire catalog using bprecover wizard 1 Start NetBackup by entering the following If your configuration includes an Enterprise Media Manager EMM server that is separate from the master server first start NetBackup on the EMM server Then start NetBackup on the master server On UNIX and Linux usr openv netbackup bin bp start_all On Windows install _path NetBackup bin bpup Run the following command bprecover wizard The following is displayed Welcome to the NetBackup Catalog Recovery Wizard Please make sure the devices and media that contain catalog disaster recovery data are available Are you ready to continue Y N Enter Y to continue The following prompt appears Please specify the full pathname to the catalog disaster recovery file Enter the fully qualified pathname to the Backup ID file For example C DR_INFO HotCatBack_1120078077_FULL The following is
2. cccc ccc eeceeenece eee eeeeeneees 113 About rolling over unified log files ccccecceceeeeseeeeeeeeenes 113 About using the vxlogview command to view unified logs 115 About query strings used with the vxlogview command 115 Chapter 4 Examples of using vxlogview to view unified logs 0665 Examples of using vxlogmgr to manage unified logs Examples of using vxlogcfg to configure unified logs About legacy logging cceccccececcec eee ee eee eeeeeeeeee eens eeeeneaeeeeaenes Creating legacy log directories to accompany problem reports for synthetic Dackup ccccccecceceeeceeeeeeeeeeeeeeeeeeseeenes File name formats for legacy logging ccccecceceeeeeeeeeeees Directory names for legacy debug logs for servers 066 Directory names for legacy debug logs for media and device management ereere tens cena ete edes vere canter edses vane CeneVeeegaes yee How to control the amount of information written to legacy logging FILES os 25 suedecsucoaanes sented dav ahenes cea ewer Perego de ass Gea RTA ENE About limiting the size and the retention of legacy logs Configuring legacy log rotation cccecceeceecnece eeu eeeeeneeneenes UNIX client processes that use legacy logging eeeeeeeee PC client processes that use legacy logging cceceeeeee ees Ab
3. Examples include correct DNS lookups firewall port openings and network routes and connections The NetBackup Domain Network Analyzer nbdna verifies this configuration Aset of utilities that verify the NetBackup level settings The utilities include bptestcd and bptestnetconn and the settings they verify include CONNECT_OPTIONS and CORBA endpoint selection Table 4 3 Network troubleshooting utilities bptestbpcd Tries to establish a connection from a NetBackup server to the bpcd daemon on another NetBackup system If successful it reports information about the sockets that are established bptestnetconn Performs several tasks that aid in the analysis of DNS and connectivity problems with any specified list of hosts This list includes the server list in the NetBackup configuration To help troubleshoot connectivity problems between the services that use CORBA communications bpbtestnetconn can perform and report on CORBA connections to named services nbdna NetBackup Domain Network Analyzer Evaluates the hostnames in the NetBackup Domain The nbdna utility self discovers the NetBackup domain and evaluates hostname information then tests connectivity to these hostnames and validates their network relationship status Network connectivity evaluation in a NetBackup domain is difficult NetBackup domains can scale to hundreds of servers and thousands of clients across complex network topologies Using
4. Refer to the NetBackup Installation Guide Disaster recovery 187 About disk recovery procedures for Windows Configure the clustered NetBackup server Refer to the NetBackup High Availability Guide Install any Maintenance Packs and patches that are required to bring the newly installed NetBackup server to the same patch level as the server being replaced Configure required devices and media and recover the NetBackup catalogs See Recovering the master server when root is intact on page 178 Bring the NetBackup resource group on each node in turn and run the Device Configuration Wizard to configure the devices Configuration information on your particular cluster is available Refer to the NetBackup High Availability Guide About disk recovery procedures for Windows The three different types of disk recovery for Windows are as follows Master server disk recovery procedures See About recovering the master server disk for Windows on page 187 Media server disk recovery procedures See About recovering the NetBackup media server disk for Windows on page 194 Client disk recovery procedures See Recovering a Windows client disk on page 194 The disk based images that reside on AdvancedDisk or on OpenStorage disks cannot be recovered by means of the NetBackup catalog These disk images must be recovered by means of the NetBackup import feature For information on import refer to the section on impor
5. etc inetd conf bpcd bpcd see note 1 etc services NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd Consider the following notes about Figure 2 5 m The complete inetd conf entry is bpcd stream tcp nowait root usr openv netbackup bin bpcd bpcd 66 Troubleshooting procedures About the bpclntcmd utility m Allother applicable network configuration must also be updated to reflect the NetBackup information For example this information could include the etc hosts file and NIS and DNS if used This example illustrates a UNIX server that connects to multiple networks The NetBackup policy client list specifies jupiter as the client name for the master server The list can show either jupiter or meteor but not both The NetBackup server list on the master server has entries for both jupiter and meteor The reason for both is that when the server does a backup it uses the name that is associated with the client it backs up For example it uses the meteor interface when it backs up pluto and the jupiter interface when it backs up mars The first server entry master server name is jupiter because that is the name used to back up the client on the master server The NetBackup server list for the other systems also has entries for both the jupiter and the meteor interfaces This setup is recommended to keep the server entries the same on all clients and servers in the configuration It wo
6. gt DIV08 1 1 04 22 2010 10 12 04 22 2010 10 12 hcart 35 5 1 05 06 2010 10 12 04 22 2010 10 25 FROZEN See Frozen media troubleshooting considerations on page 71 See Logs for troubleshooting frozen media on page 71 Resolving PBX problems The Enterprise Media Manager EMM services and other services of NetBackup require a common services framework that is called Private Branch Exchange PBX Like vnetd PBX helps limit the number of TCP IP ports that the CORBA services of NetBackup use In troubleshooting PBX consider the issues that are described in this section Note If PBX is not installed or is configured incorrectly NetBackup is unresponsive Checking PBX installation NetBackup requires the Symantec Private Branch Exchange service PBX PBX can be installed before NetBackup or during NetBackup installation See the NetBackup Installation Guide If you uninstall PBX you must reinstall it To check PBX installation 1 Look for the following directory on the NetBackup master server m On UNIX opt vRTSpbx m On Windows install _path VxPBX 2 To check the version of PBX enter the following m On UNIX opt VRTSpbx bin pbxcfg v m On Windows install _path VxPBX bin pbxcfg v 76 Troubleshooting procedures Resolving PBX problems Checking that PBX is running After you know that PBX is installed on the NetBackup master server you need to verify that it is running To see if PBX is run
7. m Use the NetBackup Volume Configuration Wizard to inventory the media contents of a robotic device m Use the vendor specific robotic control software to load the media into the required recovery device s Recover the NetBackup catalogs to the alternate disk See How to recover a catalog from a backup on page 199 The catalogs can be recovered only to the same directory structure from which they were backed up alternate path recovery is not allowed Start the NetBackup Backup Archive and Restore interface or the bp command Restore the latest backed up version of all files You restore these files from the backup of the master server not from the NetBackup catalog backup Be sure to specify the disk that you recover as the alternate recovery location Warning Do not restore files to the usr openv var usr openv db data or usr openv volmgr database directories or relocated locations or the directories that contain NetBackup database data This data was recovered to the alternate disk in step 9 and is copied back to the recovery disk in step 12 Stop all NetBackup processes that you started from NetBackup on the alternate disk Use the Activity Monitor in the NetBackup Administration Console or the following usr openv netbackup bin bp kill_all 181 182 Disaster recovery About disk recovery procedures for UNIX and Linux 12 Maintaining the same directory structure copy the NetBackup catalogs f
8. on page 200 This procedure is the recommended method for recovering the entire catalog This procedure recovers the NetBackup relational database as well as NetBackup policy files backup image files and configuration files m Recovering the catalog image file See About recovering the catalog image file on page 209 This method recovers only the NetBackup policy files backup image files and configuration files Use this method if the NetBackup relational database is valid but NetBackup policy backup image or configuration files are lost The NetBackup relational database can also be recovered separately using the bprecover nbdb command See Recovering relational database files from an online catalog backup on page 219 See Recovering the NetBackup catalog when NetBackup Access Control is configured on page 223 When recovering the entire catalog from an online backup The entire catalog can be recovered by using the Catalog Recovery Wizard or the text based bprecover wizard command Disaster recovery 201 How to recover a catalog from a backup See Recovering the entire catalog using the Catalog Recovery Wizard on page 201 See Recovering the entire catalog using bprecover wizard on page 207 Warning Do not run any client backups before you recover the NetBackup catalog Recovering the entire catalog using the Catalog Recovery Wizard This procedure shows you how to recover the
9. PBX must be running for NetBackup to operate PBX is not shown in the next diagram See Resolving PBX problems on page 75 Figure A 11 shows howto restore from tape in the UNIX and Linux environments Backup and restore functional overview 259 Restore processes Figure A 11 Restore from tape UNIX and Linux Master server Command line EMM Database I I I I I I i Notes For details on this component see the Media and Device Management Functional Description later in this chapter Itid is for tape backup only If the media server is restoring its own data server and client on same host there is no bptm child tar reads the data directly from shared memory Figure A 12 shows how to restore from disk in the UNIX and Linux environments 260 Backup and restore functional overview Restore processes Figure A 12 Restore from disk UNIX and Linux Master server UNIX client m NetBackup Command EMM user interface line Database xe bprestore sa bptm gt NetBackup ar Backup Image f Disk volume Note l If the server is restoring its own data server and client on same host there is no bptm child tar reads the data directly from shared memory Restoring SAN client UNIX or Windows Figure A 13 shows the server and client components that are used in a restore of a SAN client over Fibre Channel Backup a
10. Restore processes m Thebdptm process identifies which media disk or tape is needed for the restore based on the image catalog bptm then requests the allocation of the required media from nbrb through nbjm nbjm then asks mds part of nbemm for the resources nbemm allocates the media and selects and allocates an appropriate drive for tape media For tape bptm asks 1tid to mount the tape in the drive For disk such as AdvancedDisk or OpenStorage nbrb tells nbemm to issue the mount by means of nbrmms after nbemm allocates the resources For restore from non shared disk BasicDisk PureDisk NearStore SnapVault bptm does not need to ask nbrb for an allocation because disk inherently supports concurrent access bptm uses the file path in a read request to the system disk manager m When the allocation is granted to it bptm starts retrieving data bptm stores the image block by block in shared memory m bptm directs the image to the client in one of two ways If the server restores itself server and client are on the same host tar reads the data directly from shared memory If the server restores a client that resides on a different host it creates a child bptm process which transmits the data to tar on the client Note Only the part of the image that is required to satisfy the restore request is sent to the client not necessarily the entire backup image m The NetBackup tar program writes the data on the client disk
11. Symantec NetBackup Troubleshooting Guide UNIX Windows and Linux Release 7 1 TA symantec Symantec NetBackup Troubleshooting Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement Documentation version 7 1 PN 21159718 Legal Notice Copyright 2011 Symantec Corporation All rights reserved Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U S and other countries Other names may be trademarks of their respective owners This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party Third Party Programs Some of the Third Party Programs are available under open source or free software licenses The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs The product described in this document is distributed under licenses restricting its use copying distribution and decompilation reverse engineering No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Cor
12. About using CommandCentral Storage to troubleshoot NetBackup in a SAN environment ss csssccscvescceerecshenseencvedesy TIRATE E 95 Using CommandCentral Storage to troubleshoot the inability to access drives or robots in a SAN environment 00668 96 Using CommandCentral Storage to troubleshoot the inability to discover a drive or robot in a SAN environment 96 Using CommandCentral Storage to troubleshoot an intermittent drive failure in a SAN environment c ceeeeeeeeeeeeees 98 USME OS ck ets hat eis et a a Caretta es Mali lus 99 ADOUt LOSS 30205 cenaorew eds nananncnanentedocnerenedesduveds obama teanenedoena ntarades 99 About UNIX system logs ceeeeeceeceecneceeeeeeeeneeeeeeeaeeeeeeeneenees 101 About unified logging 2 0 0 0 cec cece nec eec eee eee eee eee een eee een eeneeaeeneegs 102 Gathering unified logs for NetBackup 6c seeeeeeeeeeeeeeeees 103 Types of unified logging messages cccccecceeceecneceeeueeneeues 104 File name format for unified logging cccecceeceeeeeeeee ees 105 Server processes that use unified logging cccceceeeneeeees 106 UNIX client processes that use unified logging 008 111 PC client processes that use unified logging cceceeeeeees 112 About changing the location of unified log files 0 08 112 About recycling unified log files
13. An option may be added later that allows the analyzed log files to reside on alternate paths Note For the processes that use unified logging no log directories must be created m The consolidated debug log may contain messages from unrelated processes You can ignore messages with timestamps outside the duration of the job from the following bprd nbpem nbjm nbrb bpdbm bpbrm bptm bpdm and bpcd An output line from the log analysis utilities uses the following format daystamp millisecs program sequence machine log line daystamp The date of the log that is in the format yyyymmdd millisecs The number of milliseconds since midnight on the local computer program The name of program BPCD BPRD etc being logged sequence Line number within the debug log file 154 Using NetBackup utilities About network troubleshooting utilities machine log _line The name of the NetBackup server or client The line that appears in the debug log file For more information see the NetBackup Commands Reference Guide About network troubleshooting utilities A set of utility programs commands verifies various aspects of the network configuration inside and outside NetBackup to ensure that there is no misconfiguration The utilities also provide user friendly messages for any errors they find Network configuration broadly falls into the following categories m Hardware operating system and NetBackup level settings
14. Fixed Retention Level 1 2 weeks Alternate Read Server none specified Preserve Multiplexing false Enable Automatic Remote Import true State active Source client Destination ID 0 Destination 2 Use for duplication to remote master Storage Remote Master Volume Pool none specified Server Group none specified Preserve Multiplexing false Enable Automatic Remote Import false State active Source Destination 1 backup PDstu Destination ID 0 For troubleshooting job flow for duplication to remote master use the same command lines as you use for other storage lifecycle policy managed jobs For example to list images which have been duplicated to remote master run the following nbstlutil list copy_ type replica U copy state 3 To list images which have not been duplicated to remote master either pending or failed run the following nbstlutil list copy_type replica U copy_incomplete 86 Troubleshooting procedures About troubleshooting duplication to a remote master 10 To list the target storage devices that complete duplication to remote master copies replication destination run the following command nbstlutil repllist Image Master Server Backup ID Client Backup Time Policy Client Type Schedule Type Storage Lifecycle Policy Storage Lifecycle State Time In Process Data Classification ID Version Number OriginMasterServer OriginMasterServerID Import From Replica Time Required Exp
15. In phase 4 the bpsynth process validates the image The new image is now visible to NetBackup and can be used like any other full or cumulative incremental backup Synthetic backup requires the following m That True Image Restore TIR with move detection be selected for each component image m That the component images are synthetic images NetBackup online hot catalog backup Online hot catalog backup This type of catalog backup is policy based with all of the scheduling flexibility of aregular backup policy This backup type is designed for highly active NetBackup environments where other backup activity usually takes place The catalog backup is performed online meaning that the catalog is not turned off More details are available See Hot catalog backup process on page 254 You can use an option in the Administration Console to start a manual backup of the NetBackup catalogs Or you can configure a NetBackup policy to automatically back up its catalogs Hot catalog backup process Figure A 9 shows the hot catalog backup that is followed by the backup process itself Backup and restore functional overview 255 Backups and archives UNIX clients Figure A 9 Hot catalog backup process Backup Policy Management Command line bpbackup A Master Server bpdbm Back up Relational Database Files T Back up NetBackup Database Files ea Relational database files E See Backup to tape or di
16. No media server or I O stream is available for this d isk volume Troubleshooting procedures 89 About troubleshooting duplication to a remote master Action Condition Automatic import jobs never start copy The storage lifecycle policy is inactive stays at storage lifecycle state 1 m Thestorage lifecycle policy import destination is inactive m The storage lifecycle policy is between sessions m The image has exceeded the extended retry count and the extended retry time has not passed Automatic import event is discarded m The event specifies a backup ID that already and the image is ignored exists in this master server s catalog m The event specifies a disk volume that is not configured in NetBackup for this storage server Automatic import job is started butthe m The storage lifecycle policy that is specified image is expired and deleted to clean in the event does not contain an import up disk space in some cases The event destination logs an error in the Problems Report or m The storage lifecycle policy that is specified bperror output An import job runs but in the event has an import destination with a the import for this image fails showing residence that does not include the disk an status code of 1532 1535 volume specified by the event m The storage lifecycle policy that is specified does not exist This is default behavior More information is available for the storage lifecycle policy configuration opt
17. Table B 2 Media and device management daemons and programs continued avrd The automatic volume recognition daemon controls automatic volume assignment and label scanning This lets NetBackup read labeled tape and optical disk volumes and to automatically assign the associated removable media to requesting processes Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin avrd command Stopped By Stopping Itid or on UNIX independently by finding the PID process id and then using the kill command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by aborting avrd and starting the daemon with the v option 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 ltid command on UNIX or Stop Restart Device Manager Service 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 Errors are logged in the system log and Itid debug log Debug information is included if the daemon is started with the v option available only on UNIX or adding VERBOSE to the vm conf file odld The Optical Di
18. The OriginMasterServer OriginMasterServerID Import From Replica Time and Required Expiration Date are not known until after the image is imported so a pending record may look like this Image Master Server Backup ID Client Backup Time Policy Client Type Schedule Type Storage Lifecycle Policy Storage Lifecycle State Time In Process Data Classification ID Version Number OriginMasterServer OriginMasterServerID Import From Replica Time Required Expiration Date Created Date Time bayside min veritas com gdwinlin04 1280299412 gdwinlin0od4 1280299412 Wed Jul 28 01 43 32 2010 none specified 0 0 none specified 1 NOT STARTED 0 Wed Dec 31 18 00 00 1969 none specified 0 master tlk 00000000 0000 0000 0000 000000000000 0 Wed Dec 31 18 00 00 1969 0 Wed Dec 31 18 00 00 1969 1287680533 Thu Oct 21 12 02 13 2010 The OriginMasterServer here is not empty although it may be in some cases In cascading duplication to remote master the master server sends the notification Troubleshooting procedures 91 Troubleshooting network interface card performance Troubleshooting network interface card performance If backup or restore jobs are running slowly verify that the network interface cards NIC are set to full duplex Half duplex often causes poor performance Note If the NIC in a NetBackup master or media server is changed or if the server IP address changes CORBA communications may be
19. UNIX etc hosts Verify client to server connectability by using ping or its equivalent from the client step 3 verified the server to client connection 52 Troubleshooting procedures Verifying host name and service entries in NetBackup 8 Ifthe client s TCP IP transport allows telnet and ftp from the server try these services as additional connectivity checks For a NetWare client ensure that the server does not try to connect when a backup or restore is already in progress on the client If you try more than one job at a time on these clients it results in a can t connect or similar error 9 Use the bpclntcma utility to verify basic client to master server communications When pn and sv run on a client they initiate inquiries to the master server as configured in the server list on the client The master server then returns information to the requesting client See About the bpclntcmd utility on page 66 10 Use the bptestbpcd utility to try to establish a connection from a NetBackup server to the bpcd daemon on another NetBackup system If successful it reports information about the sockets that are established See About the bpclntcmd utility on page 66 11 Verify that the client operating system is one of those supported by the client software Verifying host name and service entries in NetBackup This procedure is useful if you encounter problems with host names or network connections and want to
20. VxPBX log on Windows 3 To disable PBX logging to the system or event logs enter the following command vxlogcfg a p 50936 o 103 s LogToOslog false You do not have to restart PBX for this setting to take effect Troubleshooting PBX security The PBX Secure Mode must be set to false If Secure Mode is true NetBackup commands such as bplabel and vmopremd do not work PBX messages similar to the following appear in opt VRTSpbx 1og UNIX or install _path VxPBX log Windows 5 12 2008 16 32 17 477 Error V 103 11 User MINOV Administrator not authorized to register servers 5 12 2008 16 32 17 477 Error Unauthorized Server To troubleshoot PBX security 1 Set secure Mode to false by entering the following m On UNIX opt VRTSpbx bin pbxcfg d m m On Windows Troubleshooting procedures 79 Resolving PBX problems install_path VxPBX bin pbxcfg d m Verity the PBX security settings by entering the following pbxcfg p Stop NetBackup m On UNIX usr openv netbackup bin bp kill_all m On Windows install_path NetBackup bin bpdown Stop PBX m On UNIX opt VRTSpbx bin vxpbx_exchanged stop m On Windows Go to Start gt Run enter services msc and stop the Symantec Private Branch Exchange service Start PBX m On UNIX opt VRTSpbx bin vxpbx_exchanged start m On Windows Go to Start gt Run enter services msc and start the Symantec Private Branch Exchange service Start NetBackup m
21. correct and matches what is in the policy client list on the master server Start the Backup Archive and Restore interface on the client On the File menu click NetBackup Client Properties In the NetBackup Client Properties dialog box click the General tab m Onamaster or a media server ensure that a server entry exists for each Windows administrative client to use to administer that server m Ensure that host names are spelled correctly in the bp conf file UNIX or in the servers list Windows on the master server If a host name is misspelled or cannot be resolved by using gethostbyname the following error messages are logged on the NetBackup error log Gethostbyname failed for lt host_name gt lt h_errno_string gt lt h_errno gt One or more servers was excluded from the server list because gethostby name failed You can also make these changes on the appropriate tabs in the properties dialog boxes on a Windows NetBackup server See Using the Host Properties window to access configuration settings on page 69 54 Troubleshooting procedures Verifying host name and service entries in NetBackup On UNIX NetBackup servers and clients and Macintosh clients On NetWare clients Check the server and the client name entries inthe bp conf file by doing the following Ensure that a SERVER entry exists for the master server and each media server in the configuration The master server must be the first nam
22. is connected If the new device shows up as disconnected or offline contact the SAN administrator and check switch configuration Compare this troubleshooting procedure to a similar problem without the benefit of CommandCentral Storage such as Robotic status code 214 robot number does not exist See Robotic status code 214 in the Status Codes Reference Guide 4 Rerun the Device Configuration Wizard 98 Troubleshooting procedures About troubleshooting NetBackup in a SAN environment Using CommandCentral Storage to troubleshoot an intermittent drive failure in a SAN environment The following use case demonstrates how CommandCentral Storage can be integrated into a NetBackup troubleshooting procedure to investigate the SAN context of a backup system Most common NetBackup problems on SANs revolve around connectivity issues A drive fails and causes a backup to fail but on examination the drive looks fine Sometimes a problem with a switch or bridge either before or during the backup job causes the job to fail and takes down the drive This problem is one of the most difficult to diagnose By the time the NetBackup administrator looks at the SAN everything may be fine again To use CommandCentral Storage to troubleshoot this issue do the following check for alerts around the time of the job failure and see if a SAN problem occurred that would have caused the job to fail Another possibility is that another application reserved t
23. lt tlog_dir gt staging lt staging dir gt Windows install _path NetBackup bin create nbdb drop data lt data_dir gt index lt index dir gt tlog lt tlog_dir gt staging lt staging_ dir gt Where the lt data_dir gt lt index_dir gt lt tlog_dir gt and lt staging dir gt values are defined in the vxdbms conf file as Vk_kDBMS_NB DATA VXDBMS_NB_ INDEX VXDBMS_NB _ TLOG and VXDBMS_NB _ STAGING Stop and restart NetBackup UNIX and Linux usr openv netbackup bin bp kill all usr openv netbackup bin bp start_all Windows install path NetBackup bin bpdown install _path NetBackup bin bpup 222 Disaster recovery How to recover a catalog from a backup 7 10 11 Run tpext UNIX and Linux usr openv volmgr bin tpext Windows install_path Volmgr bin tpext If you used the nbdb_move command to relocate NetBackup database files re create the directories where the files were located when you backed up the catalog The default location is the following UNIX and Linux usr openv db data Windows install_path NetBackupDB data Start the device manager UNIX and Linux usr openv volmgr bin ltid v Windows start the device manager service Configure the necessary recovery device in NetBackup Make available to NetBackup the media that contains the catalog backup Inventory the robot or add the media for stand alone drives Disaster recovery How to recover a catalog from a backup 12 For
24. m Configuration testing Troubleshooting procedures 95 About troubleshooting NetBackup in a SAN environment Generally backup systems are tested before implementation to obtain benchmarks and adjust tune the system for maximum efficiency CommandCentral Storage can provide the performance metrics for end to end 1 0 capabilities for all elements in the backup path Additionally CommandCentral Storage can provide valuable environmental information for qualifying the backup environment as well as a baseline for future troubleshooting configuration management m Implementation reconfiguration production CommandCentral Storage can help to determine whether a host can see through the entire I O path to the target backup device by pinpointing connectivity issues About using CommandCentral Storage to troubleshoot NetBackup in a SAN environment You can use CommandCentral Storage in the following ways to troubleshoot NetBackup in a SAN environment In context launch The ability to launch CommandCentral Storage and access an overview of the SAN from NetBackup in context is valuable for determining root cause problems quickly In addition because NetBackup administrators and SAN administrators are often in different groups the fragmented operations that lead to resolution delays may be avoided With CommandCentral Storage the NetBackup administrator has a view of the overall health of the SAN as part of the initial troubleshooting proces
25. on page 102 nbaudit On the master server the audit daemon accepts audit requests from other NetBackup components and persists the audit records in the database It also queries and returns the audit records from the database to display to the user Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbaudit terminate Debug Log On the server usr openv logs nbaudit UNIX or install_path logs nbaudit Windows nbfdrv6 4 Ona media server that is enabled for SAN Client backup over fibre channel nbfdrv64 is the following a user mode component that is used for both backup and restore nbfdrv64 uses a windrvr6 proxy to move fibre channel data between nbftclnt and bptm buffers Started By usr openv netbackup bin nbftsrvr Stopped By usr openv netbackup bin nbftsrvr terminate Debug Log On the server usr openv 1ogs UNIX or install_path logs Windows See About unified logging on page 102 280 Backup and restore functional overview NetBackup programs and daemons Table A 4 Backup daemons and programs continued nbftclnt On clients that are enabled for SAN Client backup over fibre channel nbftclnt transfers the backup image over fibre channel to nbftsrvr on the media server Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbftclnt terminate Debug Log On the client usr openv 1logs UNIX or install_path
26. the NetBackup Virtual Name as the name of the NetBackup server Follow the instructions for installing the NetBackup server software Refer to the NetBackup Installation Guide Install any Maintenance Packs and patches that are required to bring the newly installed node to the same patch level as the other cluster nodes Bring the NetBackup Resource group online on a node other than the freshly installed node Log onto the node on which the NetBackup resource group is online and run the following command usr openv netbackup bin cluster cluster config s nbu o add_node n node_name node_name is the name of the freshly installed node Switch the NetBackup resource group to the replacement node Freeze the NetBackup group Ensure that the appropriate low level tape device and robotic control device configuration necessary for your operating system has been performed Information is available for your operating system Refer to the NetBackup Device Configuration Guide Run the Device Configuration Wizard to configure the devices You do not have to rerun the device configuration on the pre existing nodes Configuration information on your particular cluster is available See the NetBackup Administrator s Guide Volume I Disaster recovery 185 About clustered NBU server recovery for UNIX and Linux 14 Check that the robot numbers and robot drive numbers for each robot are consistent across all nodes of the cluster Repeat for
27. 124 Step 2 Edit the Add the following line to the Debug properties file Debug properties file debugMask 2 The Debug properties file can be found in the following locations E usr openv java Change the file on the UNIX machine where you run the jnbSA or jbpSA commands The log file name is displayed in the xterm window where you ran the jnbSA or jbpSA commands E install path VERITAS java Change the file at this location if you use the NetBackup Java Windows Display Console Step 3 Edit the nbjava bat file Perform this step if you use the Windows Display Console on a host where NetBackup is not installed Edit the nbjava bat file to redirect output to a file The nbjava bat file is located in install_path VERITAS java See the nbjava bat file for details Chapter Using NetBackup utilities This chapter includes the following topics About NetBackup troubleshooting utilities About the analysis utilities for NetBackup debug logs About network troubleshooting utilities About the NetBackup support utility nbsu About the NetBackup consistency check utility NBCC About the NetBackup consistency check repair NBCCR utility About the nbcplogs utility About NetBackup troubleshooting utilities Several utilities are available to help diagnose NetBackup problems The analysis utilities for NetBackup debug logs and the NetBackup support utility nbsu are especially useful in troubleshooting Table
28. 167 3 57141 The following is true of this command example E expecting response from server rabbit friendlyanimals comis the master server entry from the server list on the client E dove friendlyanimals comis the connection name peer name returned by the master server The master server obtained this name through gethostbyaddress m dove is the client name configured in the NetBackup policy client list m 123 145 167 3 is the IP address of the client connection at the master server m 57141 is the port number of the connection on the client Use ip and hn to verify the ability of a NetBackup node to resolve the IP addresses and host names of other NetBackup nodes For example to verify that a NetBackup server can connect to a client do the following m On the NetBackup server use bpclntcmd hn to verify the following 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 m Onthe NetBackup client usebpcintcmd 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 See Verifying host name and service entries in NetBackup on page 52 See Resolving network communication problems with PC clients on p
29. 4 1 Troubleshooting utilities Analysis utilities for NetBackup debug They enhance NetBackup s existing debug logs capabilities by providing a consolidated view of a job debug log See About the analysis utilities for NetBackup debug logs on page 150 150 Using NetBackup utilities About the analysis utilities for NetBackup debug logs Table 4 1 Troubleshooting utilities continued Network troubleshooting utilities They verify various aspects of the network configuration inside and outside NetBackup to ensure that there is no misconfiguration See About network troubleshooting utilities on page 154 NetBackup support utility nbsu It queries the host and gathers appropriate diagnostic information about NetBackup and the operating system See About the NetBackup support utility nbsu on page 155 NetBackup consistency check utility NBCC It analyzes the integrity of portions of the NetBackup configuration and catalog and database information as they pertain to tape media See About the NetBackup consistency check utility NBCC on page 161 NetBackup consistency check repair NBCCR utility It processes database catalog repair actions and automates the application of approved suggested repair actions See About the NetBackup consistency check repair NBCCR utility on page 167 nbcplogs utility It simplifies the process of gathering logs for deliv
30. Chapter 3 Frozen media troubleshooting considerations cceceeeeeeen eens 71 Logs for troubleshooting frozen media ccccceecneceeeneeeeenes 71 About conditions that cause media to freeze cseeeeeeeeees 72 Resolving PBX problems zeri resres io e sence eeeea T 75 Checking PBX installation ccccceccecee cence sence sense eeeeneetenens 75 Checking that PBX is running ccecceceeeeceee sense eeeeneeeenens 76 Checking that PBX is set correctly ccccceececeececeeeeeeeneeeeeees 76 Accessing the PBX logs 0c ccceceeecneceeeee sence sence eens enteeneenes 77 Troubleshooting PBX security ccccecceceeeeceeeceee sense eeeeaeees 78 Determining if the PBX daemon or service is available 80 About troubleshooting duplication to a remote master 0658 80 Troubleshooting duplication to remote master jobs 55 81 About troubleshooting automatic import jobs 0ceeeeeees 87 Troubleshooting network interface card performance 6 00e00s 91 About SERVER entries in the bp conf file 0 ccccc ccc ec eee eenee eee eee 92 About unavailable storage unit problems cscceceeceeeeeeee ees 92 About troubleshooting NetBackup in a SAN environment 93 NetBackup enterprise lifecycle best practices cccceceeeeeeees 94
31. Create the disk storage server for the storage by using the Storage Server Configuration Wizard m Create the disk pool for the storage by using the Disk Pool Configuration Wizard Run the following command to synchronize the disaster recovery file to the new disk pool nbcatsyne sync_dr_ file disaster recovery file Run the following NetBackup command to recover the catalog bprecover wizard copy N Nis the number of the copy from which you want to recover Disaster recovery 225 How to recover a catalog from a backup Recovering the catalog without the disaster recovery file If the disaster recovery file has been lost consult the email that was sent to the administrator when the catalog was backed up The disaster recovery file is written to the location you specify in the catalog backup policy and is appended to the backup stream itself To recover the catalog without the disaster recovery file 1 The email identifies the media that contains the disaster recovery file and the media that was used to back up critical policies Ensure that this media is available 2 Followup the normal catalog recovery steps until the point where the Catalog Recovery Wizard or bprecover command is called for 3 Run the following command to retrieve all disaster recovery files from the catalog backup media bpimport drfile media id drfile dest fully qualified dir name This command recovers all disaster recovery files from the specified me
32. ImageDB ULT000 MContents One or more images from images catalog NOT found on MContents ULTOOO status ActionFailed 170 Using NetBackup utilities About the nbcplogs utility For a full description of the n8ccr command options refer to the nBccR man page See the NetBackup Commands Reference Guide About the nbcplogs utility When you troubleshoot a customer problem you must gather and copy the correct logs to debug the issue The log types NBU vxu1 vn pbx may be in many places The process of getting the logs to Symantec technical support can be difficult and time consuming By default nbcplogs NetBackup log uploader now runs the nbsu utility and uploads nbsu information for the host system This capability improves the end user experience with Technical Support by saving time and keystrokes to gather and upload information The utility also gathers additional log information for clusters and pack history information nbcplogs uses file transfer protocol FTP to upload its support package to Technical Support This process requires temporary disk space to build the compressed bundle that it transfers You can configure this temporary space by setting up an environment variable TMPDIR and using a nbcplogs command line option tmpdir as follows On Windows nbcplogs tmpdir C temp f On UNIX In bin sh enter the following TMPDIR tmp export TMPDIR nbcplogs f In bi
33. Linux usr openv netbackup bin support output nbcc hostname_NBCC_timestamp Windows install_path NetBackup bin support output nbcc hostname_NBCC_timestamp If a supported archive program is available on the host where necc runs NBCC bundles its output files into an archive file If a supported compression utility is available necc compresses the archive file Otherwise the individual output files remain unarchived and uncompressed An example of a compressed UNIX archive file that necc created is as follows usr openv netbackup bin support output NBCC host1_ NBCC_20060814_ 164443 host1_NBCC_20060814 164443 tar gz where host1 is the name of the host where necc had been run On UNIX platforms necc supports the tar compress and gzip utilities for UNIX file archiving and compression On Windows platforms necc supports the tar Makecab and gzip utilities for Windows file archiving and compression Example of an NBCC progress display By default NetBackup consistency check utility Necc displays its progress numerically to standard output The name of the output file is nbcc info txt The following example of nscc output has been edited for brevity 1 0 Gathering initial NBCC information 1 1 Obtaining initial NetBackup configuration information If NBCC DOES NOT detect any catalog inconsistencies would you like NBCC to create a support package Y y N n N Would you then like NBCC to remove the output files after compl
34. MediaDB information including the media status Frozen Full or Active To unfreeze the media use the bpmedia command Specify the media server that contains that frozen record in the command syntax Unfreeze the media one at a time Frozen media does not necessarily mean that the media is defective NetBackup may freeze media as a safety measure to prevent further errors drive damage or data loss Investigate any patterns to the media IDs tape drives or media servers that are involved when media is frozen Logs for troubleshooting frozen media The following logs are useful when troubleshooting frozen media UNIX and Linux sm The bptmlog from the media servers that froze the media usr openv netbackup logs bptm m The Admin messages or syslog from the operating system Windows m The bptm log from the media servers that froze the media install_dir VERITAS NetBackup logs bptm m The Windows Event Viewer System Log m The Windows Event Viewer Application Log Set the verbosity of the bptm process log to 5 to troubleshoot any media and drive related issues This log does not use excessive drive space or resources even at an elevated verbosity When media is frozen the bptm logs may contain more detailed information that the Activity Monitor or Problems Report Set the verbosity for bptm on individual media servers by changing their logging levels under Host Properties on the NetBackup Administration Console 71 72 Tro
35. NetBackup on the EMM server before starting NetBackup on the master server On UNIX and Linux usr openv netbackup bin bp start_all On Windows install _path NetBackup bin bpup Run the following command bprecover wizard The following is displayed Welcome to the NetBackup Catalog Recovery Wizard Please make sure the devices and media that contain catalog disaster recovery data are available Are you ready to continue Y N 218 Disaster recovery How to recover a catalog from a backup Enter Y to continue The following prompt appears Please specify the full pathname to the catalog disaster recovery file Enter the pathname to the Backup ID file For example C DR_INFO HotCatBack 1120078077 FULL The following is displayed All media resources were located Do you want to recover the entire NetBackup catalog Y N Enter N to continue The following is displayed Catalog recovery is in progress Please wait This portion of the catalog recovery has completed Because this operation is a partial recovery any remaining portions of the catalog must be restored using Backup Archive and Restore Please review the following log file for more information C Program Files VERITAS NetBackup Logs user_ops Administrator logs Recover1123008613 log You can now recover the NetBackup database if necessary NetBackup does not run scheduled backup jobs until NetBackup is stopped and restarted Before restartin
36. NetBackup utilities 155 About the NetBackup support utility nbsu For more information on these utilities refer to the NetBackup Commands Reference Guide About the NetBackup support utility nbsu The NetBackup support utility nbsu is a command line tool It queries the host and gathers appropriate diagnostic information about NetBackup and the operating system nbsu provides a wide range of control over the types of diagnostic information gathered For instance you can obtain information about NetBackup configuration settings about specific troubleshooting areas or about NetBackup or media management job status codes The NetBackup support utility nbsu resides in the following location UNIX usr openv netbackup bin support nbsu Windows install_path NetBackup bin support nbsu exe Symantec recommends that you run the NetBackup support utility nbsu in the following circumstances m To obtain baseline data on your NetBackup installation If you encounter problems later this data can be useful m To document changes in your NetBackup or operating system environment Run nbsu periodically to keep your baseline data up to date m To help isolate a NetBackup or operating system issue m To report issues to Symantec technical support The following suggestions can help you run the nbsu utility more effectively m For an nbsu description examples and how to gather diagnostic information to send to Symantec Technical Sup
37. On UNIX usr openv netbackup bin bp start_all m On Windows install_path NetBackup bin bpup 80 Troubleshooting procedures About troubleshooting duplication to a remote master Determining if the PBX daemon or service is available If NetBackup does not work as configured a required NetBackup service may have stopped For example backups may not be scheduled or may be scheduled but are not running The type of problem depends on which process is not running When a NetBackup service is not running and another process tries to connect to it messages similar to the following appear in usr openv 1logs for PBX The unified logging originator for PBX is 103 05 17 10 9 00 05 17 10 9 00 05 17 10 9 00 extension EMM 05 17 10 9 00 05 17 10 9 00 05 17 10 9 00 247 247 247 47 47 47 79 79 79 80 80 80 nfo nfo nfo nfo nfo PBX Manager handle input with fd PBX_Client_Proxy PBX_Client_Proxy hand_off looking Error No proxy found PBX_Client_Proxy Il ws parse line line ack 1 parse_ line line for proxy for EMM thandle close To determine if the PBX daemon or service is available 1 Start the needed service In this example the missing NetBackup service is EMM To start the needed service enter the noemm command UNIX or start the NetBackup Enterprise Media Manager service Windows Start gt Run enter services msc 2 If necessary s
38. You can use it to see if a network cable was dislodged or if some other problem exists This use case may be encountered when you configure off host backups Off host backups require the media server to be able to see all devices with which it conducts the backup disk array disk cache data mover library and drive Connectivity must be correct In addition the bptpcinfo command in NetBackup Snapshot Client generates a 3pc conf configuration file for running the backup Often the WWN world wide name for some devices is incorrect You can use CommandCentral Storage to verify that the contents of the 3pc conf file correlate to the actual fabric configuration For a description of off host backup the bptpcinfo command and the 3pc conf file refer to the NetBackup Snapshot Client Configuration document For help accessing this document see Snapshot Client Assistance in the NetBackup Snapshot Client Administrator s Guide Symptom After you run the Device Configuration Wizard the new device does not appear in the discovered devices list To use CommandCentral Storage to troubleshoot the inability to discover a drive or robot in a SAN environment 1 Run device discovery again 2 Ifthe new device is still not seen the likely problem is with hardware Launch CommandCentral Storage 3 Ifthe new device does not appear in the CommandCentral Storage topology check the SAN hardware connections to determine whether or not the device
39. admin 127 bpbrm 127 bpcd 127 bpdbjobs 127 bpdbm 128 bpdm 128 bpjava susvc 128 bprd 128 bpsynth 128 bptm 128 daemon 129 Itid 129 nbjm 106 nbpem 106 nbrb 106 reqlib 129 robots 129 tpcommand 129 setting retention period 131 system 101 UNIX client activity bp 134 bparchive 134 bpbackup 134 bpbkar 134 bpcd 134 bphdb 134 bpjava msve 128 bplist 134 bpmount 134 bprestore 135 obackup_tape 135 tar 135 user_ops 135 logs directory UNIX client server 271 Itid 130 Itid description 298 master server test procedure 33 37 MaxLogFileSizeKB 122 124 133 media database 285 media server test procedure 36 misc file 296 mklogdir bat 125 moving log locations 112 multiplexed backups 242 name format legacy logging 126 NB_dbsrv daemon 70 nbaudit 279 NBCC archiving and compression 163 does the following 161 introduction 161 location of 161 nbcc info txt file 162 Notes on running 161 output 163 progress display 163 troubleshooting 162 when to use 161 nbcc info txt file 162 nbdb_move 188 nbemm 23 237 279 nbfdrv64 279 nbftclnt 111 246 248 262 280 and bp conf 92 nbftsrvr 246 248 262 280 nbjm 23 106 237 245 252 280 281 NBNWNT 250 264 NBNWNT EXE 280 nbpem 23 106 236 237 245 252 281 nbproxy 281 nbrb 23 70 106 237 281 nbrmms 282 nbstserv 282 nbsu and status codes 159 archiving and compression 158 bundling 158 creating xml output file 159 introduction 155 Index 319 nbsu continued l
40. advised otherwise by Technical Support Higher levels can cause the logs to accumulate large amounts of information Click OK You can also change logging levels in the following ways Using logs 141 Logs to accompany problem reports for synthetic backups m On NetWare clients change the value of the level and the tcp parameters in the debug section of the bp ini file For instructions see the NetBackup user guide for the client m For the unified logging files that the Bare Metal Restore process bmrsavecfg creates you also can control the logging level with the vxlogcfg command See Examples of using vxlogcfg to configure unified logs on page 121 An increase in the log level can cause the logs to grow very large increase the logging level only if unexplained problems exist Logs to accompany problem reports for synthetic backups To debug problems with synthetic backups you must include a complete set of logs in the problem report and additional items Send all the information to Symantec Technical Support Include the following log types m Log files that unified logging creates See Gathering unified logs for NetBackup on page 103 m Log files that legacy logging creates See Creating legacy log directories to accompany problem reports for synthetic backup on page 125 Include the following additional items Try file The try file is located in the following directory install _path netbackup db jo
41. click Next For assistance click Help Indicate where the disaster recovery file is stored by entering the fully qualified path to the disaster recovery file For example net lex Cat_DR CatBk_1119304246 INCR Specify the most recent disaster recovery file available unless there is a reason to restore from an earlier state Note whether the disaster recovery file is based on a full _ FULL or an incremental _INCR catalog backup More information is available on the email that is sent and the attached disaster recovery file See Recovering the catalog without the disaster recovery file on page 225 214 Disaster recovery How to recover a catalog from a backup 4 The wizard waits while NetBackup searches for the necessary media sources then tells you if the necessary backup ID of the disaster recovery image was located If the media is not located the wizard lists which media is needed to update the database NetBackup Catalog Recovery Wizard x Catalog Disaster Recovery File fe Specify the location of your disaster recovery file Specify the full pathname to the disaster recovery file If the disaster recovery file is not available use the bpimport drfile command i to read it from the catalog backup media See the documentation for further details Cick nest to obtain the file This may take a long time Follow the wizard instructions to insert the indicated media and run
42. client s configured name by using the bpc1ntcmd command on the client For example usr openv netbackup bin bpclntcmd pn UNIX install _path NetBackup bin bpclntcmd pn Windows expecting response from server wind abc me com danr abc me com danr 194 133 172 3 4823 Where the first output line identifies the server to which the request is directed and the second output line is the server s response in the following order m Peername of the connection to the server m Configured name of the client m IP address of the connection to the server Networks and hostnames Background for troubleshooting m Port number that is used in the connection When the client connects to the server it sends the following three names to the server m browse client m requesting client m 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 Backup Archive and Restore interface See the NetBackup online Help for instructions For this change to work however the administrator must also have made a corresponding change on the server See the NetBackup Administrator s Guide Volume I The requesting client is the value from the gethostname function on the client The destination client name is a factor only if an adminis
43. db directory NetBackup 269 270 debug level 140 debug logs 147 analysis utilities 150 NetBackup 296 vmd 129 296 debug properties file 148 debugging NBCC 162 debugging continued nbsu 156 device configuration problems 29 Device Configuration Wizard 189 directory structure Media and Device Management 295 disaster recovery preparing for disaster 173 disk full 69 disk recovery Windows client 194 disk space for logs files 124 drive_mount_notify script 290 drive_unmount_notify script 290 driver directory 296 duplex mode and performance 91 E E mail 176 EMM server 237 enable debug logging 129 Enable robust logging 133 Enterprise Media Manager 182 Enterprise Media Manager EMM 237 error database 285 Event viewer logging option 143 eventlog 143 file entries 143 exception errors in Java admin interface 145 F failure_history file 285 fibre channel 246 file database 285 files archive process 236 backup process 236 restore process 256 format directory 296 FSM 246 FT Service Manager 246 full disk 69 full duplex mode 91 functional overview introduction 235 Media and Device Management device management 289 Index 317 functional overview continued Media and Device Management continued directories and files 295 volume management 289 NetBackup backup and archive 236 restores 256 startup 236 G Global Logging Level 130 Global logging level 138 139 goodies directory 270 goodies directory 296
44. displayed All media resources were located Do you want to recover the entire NetBackup catalog Y N Disaster recovery 209 How to recover a catalog from a backup 5 Enter Y to continue The following is displayed Catalog recovery is in progress Please wait Database server restarted and completed successful recovery of NBDB on lt EMM Server gt Catalog recovery has completed Please review the log file C Program Files VERITAS NetBackup Logs user_ops Administrator logs Recover1120078220 log for more information The image file is restored to the proper image directory and the NetBackup relational databases NBDB and optionally BMRDB are restored and recovered 6 NetBackup does not run scheduled backup jobs until NetBackup is stopped and restarted Before restarting NetBackup protect the media that contains the backups that were successfully performed after the catalog backup that was used to recover the catalog This procedure can include the following tasks m Importing the backups from the backup media into the catalog m Write protecting the media m Ejecting the media and setting it aside m Freezing the media 7 Stop and restart NetBackup On UNIX and Linux usr openv netbackup bin bp kill all usr openv netbackup bin bp start_all On Windows install _path NetBackup bin bpdown install _path NetBackup bin bpup If aremote EMM server is used start NetBackup on it before you start NetBackup on the master
45. entire catalog using the Catalog Recovery Wizard You must have root administrative privileges The Catalog Recovery Wizard panels that appear when you are performing these procedures are very similar for UNIX Linux and Windows platforms Only the Windows panels are shown in text in the following procedures Note The Catalog Recovery Wizard does not work after you perform a change server operation You must be logged on locally to the master server that being recovered Note During the catalog recovery process services may be shut down and restarted If NetBackup is configured as a highly available application cluster or global cluster freeze the cluster before starting the recovery process to prevent a failover Then unfreeze the cluster after the recovery process is complete To recover the entire catalog 1 Your configuration may include an Enterprise Media Manager EMM server that is separate from the master server If so start NetBackup on the EMM server before starting NetBackup on the master server 2 Start NetBackup by entering the following On UNIX and Linux usr openv netbackup bin bp start_all On Windows install _path NetBackup bin bpup The NetBackup Administration Console appears 3 If the necessary devices are not already configured configure them in NetBackup 202 Disaster recovery How to recover a catalog from a backup Make available to NetBackup the media that contains the catalog backu
46. example a backup on a Windows client What were the error indications for example status code error dialog box Did this problem occur during or shortly after any of the following ___ Initial installation Configuration change explain ____ System change or problem explain Have you observed the problem before If so what did you do that time Introduction 17 About gathering information for NetBackup Java applications Logs or other failure data you have saved ___ All log entries report _____ Media and Device Management debug logs NetBackup debug logs ____ System logs UNIX ____ Event Viewer Application and System logs Windows Ways that you can communicate with us ftp __ telnet __ email WebEx About gathering information for NetBackup Java applications If you encounter problems with the NetBackup Java applications use the following methods to gather data for support The following scripts are available for gathering information jnbSA Logs data to a log file in usr openv netbackup logs user_ops nbjlogs At startup the script tells you which file in this directory it logs to Normally this file does not become very large usually less than 2 KB Consult the file usr openv java Debug properties for the options that can affect the contents of this log file NetBackup Java administration application startup script NetBackup Java administration application Logs da
47. following examples show the default port numbers See Example of host name and service entries on UNIX master server and client on page 57 See Example of host name and service entries on UNIX master server and media server on page 59 See Example of host name and service entries on UNIX PC clients on page 60 See Example of host name and service entries on UNIX clients in multiple networks on page 62 See Example of host name and service entries on UNIX server that connects to multiple networks on page 64 Do not change NetBackup port assignments unless it is necessary 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 On NetBackup servers check the services files to ensure that they have entries for the following E bpca and bprd E vmd E bpdbm m Processes for configured robots for example t18ca See the NetBackup Device Configuration Guide Verify the NetBackup client daemon or service number and the request daemon or service port number The action you take depends on whether the client is UNIX Microsoft Windows or NetWare 56 Troubleshooting procedures Verifying host name and service entries in NetBackup On UNIX clients On Microsoft Windows clients On NetWare clients 4 OnUNIX servers and Check the bprd and the bpcd entries in the e
48. host xlate file has three elements a numeric key and two hostnames Each line is left justified and a space character separates each element of the line key hostname_from_client client_as_known_by_server The following describes the preceding variables m 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 which indicates a configured name translation m hostname_from_client is the value to translate This value must correspond to the name that is obtained by the client s gethostname function and sent to the server in the request m client_as_known_by serveris the name to substitute for hostname_from_client when responding to requests This name must be the name that is configured in the NetBackup configuration on the master server It must also be known to the master server s network services This following is an example Networks and hostnames 309 Background for troubleshooting 0 danr danr eng aaa com 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 The problem is resolved assuming the following m The client s gethostname function returns danr m The master server s network services gethostbyname function did not recognize the name danr m The client was configured and named in the NetBackup configuration as danr en
49. information with nbjm bptm sends mount requests for specific media and drives to the NetBackup Device Manager 1tid This action causes the media to be mounted on the appropriate devices If during the backup a tape span is required bptm again exchanges information with nbjm to release the correct tape and to get another one nbjm exchanges information with nbrb to accomplish this function For AdvancedDisk and OpenStorage bptm requests the volume from nbjm nbjm then passes the request to nbemm to choose the volume server and media server to use nbemm calls nbrmms on the media server that was chosen to mount the volume If during the backup a tape span is required bptm again exchanges information with nbjm to release the correct tape and to get another one nbjm exchanges information with nbrb to accomplish this function For BasicDisk bpdm writes the images to the path that is configured in the disk storage unit The system disk manager controls the actual writing of data In the case of an archive bpbrm deletes the files from the client disk after the files are successfully backed up Job manager service Receives the completion status of the job from bpbrm nbjm nbjm Releases the resources to nbrb and returns the status to nbpem Backup with multiple data streams For multiplexed backups the process is essentially the same An exception is that a separate bpbrm process and bptm process is created fo
50. level can be turned off completely No diagnostic messages or debug messages are logged This level cannot be set with the Global logging level list in the NetBackup Administration Console You can set it with the vxlogcfg command See Examples of using vxlogcfg to configure unified logs on page 121 m Achange to the Global logging level list affects the logging level of all NetBackup and Enterprise Media Manager EMM processes on the server or client The exceptions are PBX and media and device management logging This setting overrides any previous settings m If you make a change to the VERBOSE level in the bp conf file or the vm conf file it only affects the legacy logging level See How to control the amount of information written to legacy logging files on page 130 m If you make a change with the vxlogcfg command it only affects the unified logging level A change to the Global logging level list does not affect the level of the following logging processes m PBX logging See Accessing the PBX logs on page 77 m Media and device management logging vma 1tid avra robotic daemons media manager commands See Directory names for legacy debug logs for media and device management on page 129 TAG m Any unified logging process whose debug level has been changed from the default setting 140 Using logs About global logging levels Changing the logging level The logging level determines how
51. media server If this works the problem is probably with the policy or the storage unit configuration on the media server When you are done use tpunmount to unmount the media 40 Troubleshooting procedures Testing the media server and clients Table 2 7 Steps for testing the media server and clients continued Step 7 Include a robotic If you previously configured a non robotic device in the test drive and a robot was attached to your media policy server change the test policy to name the robot Also add a volume for the robot to the EMM server Verify that the volume is in the NetBackup volume pool and in the robot Start with step 3 to repeat this procedure for a robot This procedure verifies that NetBackup can find the volume mount it and use the robotic drive If a failure occurs check the NetBackup All Log Entries report Look for any errors that relate to devices or media See the NetBackup Administrator s Guide Volume I If the All Log Entries report doesn t help check the following m Ona UNIX server the system logs on the media server m vmd debug logs on the EMM server for the robot m Ona Windows system the Event Viewer Application and System log In an initial configuration verify that the robotic drive is configured correctly Do not use arobot number that is already configured on another server Try the test utilities See About robotic test utilities on page 311 Do not use
52. must configure the policy entries carefully They must consider the network configuration physical hostnames and aliases NIS DNS routing tables and so on If administrators want to direct backup and restore data across specific network paths they especially need to consider these things 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 that is defined by the system s routing tables The bp conf file is not a factor making this decision For restores from the client the client connects to the master server For example on a UNIX system the master server is the first one named in the usr openv netbackup bp conf file On a Windows system the master server is specified on the Server to use for backups and restores drop down of the Specify NetBackup Machines and Policy Type dialog box To open this dialog start the NetBackup Backup Archive and Restore interface and click Specify NetBackup Machines and Policy Type on the File menu The client s network code that maps the server name to an IP address determines the network path to the server 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 usi
53. ncfnbcs Client service 112 Using logs About unified logging PC client processes that use unified logging Most PC client processes use legacy logging except for a few Bare Metal Restore processes However the following Windows client processes use unified logging Unified logging is enabled by default Table 3 4 PC client process that use unified logging 121 bmrsavecfg 122 bmrec Originates from the BMR boot server which may or may not be a NetBackup server and runs on the restoring client 131 bmrrst exe and Originate from the BMR boot server which may bmrmap exe or may not be a NetBackup server and run on the restoring client 351 nblbc NetBackup Live Browse Client 200 nbftclnt 352 nbgre NetBackup Granular Restore 359 nbbrowse NetBackup Client Browser 366 nbcs Client service About changing the location of unified log files The unified logging files can consume a lot of disk space If necessary enter the following to direct them to a different location UNIX Windows usr openv netbackup bin vxlogcfg a p NB o Default s LogDirectory new log path Where new log pathisa full path such as bigdisk logs install_path NetBackup bin vxlogcfg a p NB o Default s LogDirectory new log path Where new log pathisa full path such as D logs Using logs 113 About unified logging About recycling unified log files Deleting the oldest log files is referred
54. node 9 Disaster recovery How to recover a catalog from a backup Re enable monitoring of the NetBackup resource group 10 Verify that the NetBackup server can now be brought online on all configured nodes Recovering the entire Windows VCS cluster The following procedure applies to the clustered NetBackup server environment that must be re created from scratch Before you proceed ensure that you have valid online catalog backups To recover the entire Windows VCS cluster 1 Configure the hardware system software and cluster environment on the replacement cluster Ensure that the appropriate low level tape device and robotic control device configuration necessary for your operating system has been performed Refer to the NetBackup Device Configuration Guide Reinstall NetBackup on each of the cluster nodes Be sure to use the NetBackup Virtual Name as the name of the NetBackup server Follow the instructions for installing NetBackup server software Refer to the NetBackup Installation Guide Configure the clustered NetBackup server Refer to the NetBackup High Availability Guide Install any Maintenance Packs and patches that are required to bring the newly installed NetBackup server to the same patch level as the server that is being replaced Configure required devices and media and recover the NetBackup catalogs See Recovering the master server and Windows on page 191 Bring the NetBackup resource gr
55. of 2 30391 images to be processed CONSISTENCY ERROR Oper _7 1 5 11 NetBackup catalog consistency check completed End time 2010 10 18 10 19 16 5 12 Checking for the latest NBCCR repair output directory Reading the output nbccr hostname_ NBCCR 20101018 _101007 NBCCR output txt file located in the output nbccr hostname_NBCCR_20101018 101007 directory Detected 2 records dir results for output nbcc hostname_ NBCC_20101018 101900 nbcc NBCCR output txt 10 18 2010 10 19 AM 384 nbcc NBCCR output txt Copying the Using NetBackup utilities 167 About the NetBackup consistency check repair NBCCR utility output nbccr hostname NBCCR_20101018 101007 NBCCR history txt file located in the output nbccr hostname_ NBCCR_20101018 101007 directory to include with the Support package dir results for output nbcc hostname_ NBCC_20101018 101900 nbcc NBCCR history txt 10 18 2010 10 18 AM 21 155 nbcc NBCCR history txt Summary of NBCC server processing Se i i i i Primary and associated alias hostnames hostname hostname FQN com Sources nbemmcmd bpstulist bpgetconfig vmoprcemd Master server yes EMM NetBackup version 7 1 0 0 EMM Server yes NBCC NetBackup version 7 1 Tape STU detected no Disk STU detected yes EMM tape media record extract attempted yes HEEHEHEHHEH EPEAT AEFEFLFETEFEFTFEFEFEFTEF EPEAT EP EFTET EPEAT EP EPTFE EP EFT PEPE HHT Report complete closing the output nbcc ho
56. one for the master server jupiter Figure 2 2 UNIX master and media servers UNIX Media Server saturn UNIX jupiter Master Server Ethernet Policy Client List mars UNIX Client jupiter mars saturn usr openv netbackup bp conf usr openv netbackup bp conf usr openv netbackup bp conf SERVER jupiter SERVER jupiter SERVER jupiter SERVER saturn SERVER saturn SERVER saturn CLIENT_NAME jupiter CLIENT_NAME mars CLIENT_NAME saturn etc inetd conf etc inetd conf etc inetd conf bpcd see note 1 bpcd bpcd see note 1 bpcd bpcd see note 1 etc services etc services etc services NetBackup services NetBackup services NetBackup services bpcd 13782 tcp bpcd bpcd 13782 tcp bpcd bpcd 13782 tcp bpcd bprd 13720 tcp bprd bprd 13720 tcp bprd bprd 13720 tcp bprd bpdbm 13721 tcp bpdbm bpdbm 13721 tcp bpdbm Volume Manager services Volume Manager services vmd 13701 tcp vmd vmd 13701 tcp vmd tl8cd 13705 tcp tl8cd tl8cd 13705 tcp tl8cd odld 13706 tcp odld odid 13706 tcp odld 60 Troubleshooting procedures Verifying host name and service entries in NetBackup Consider the following notes about Figure 2 2 m The following is the complete inetd conf entry bpcd stream tcp nowait root usr openv netbackup bin bpcd bpcd m Allother applicable network configuration must also be updated to reflect the NetBackup information For example
57. online catalog recovery run the following command on the master server UNIX and Linux usr openv netbackup bin admincmd bprecover r nbdb Windows start the device manager service install _path NetBackup bin admincmd bprecover r nbdb 13 Stop and restart NetBackup UNIX and Linux usr openv netbackup bin bp kill all usr openv netbackup bin bp start_all Windows install path NetBackup bin bpdown install _path NetBackup bin bpup If aremote EMM server is used start NetBackup on it before you start NetBackup on the master server Recovering the NetBackup catalog when NetBackup Access Control is configured If you have configured NetBackup Access Control NBAC the online hot catalog backup automatically backs up your authentication information and authorization configuration information Both the Operate and Configure permission sets are required on the catalog object to successfully back up and recover NBAC authentication and authorization data To recover the NetBackup catalog when NetBackup Access Control is configured 1 Follow the normal NetBackup catalog recovery procedures Ensure that NetBackup Access Management Control is installed but disabled before you run the actual Catalog Recovery Wizard or bprecover command You must have superuser privileges to execute the recovery 2 Turn off the authentication services and authorization services Windows or daemons UNIX and Linux 3 Recover the NetBackup cat
58. operating system and the NetBackup version and configuration For each diagnostic command that it runs nbsu writes the command output to a separate file As a rule the name of each output file reflects the command that nbsu ran to obtain the output For example nbsu created the NBU_bpplclients txt by running the NetBackup bpplclients command and created the os_set txt file by running the operating system s set command Each output file begins with a header that identifies the commands that nbsu ran If output from more than one command was included in the file the header identifies the output as an internal procedure Figure 4 1 shows the actual commands and output follow the header Figure 4 1 Example nbsu output file ipconfig command excerpt SSS SS ee Network ipconfig information report pS re ier ssa pas Command used sss 5 gt C WINDOWS system32 ipconfig all Windows IP Configuration Host Name hostl Primary Dns Suffix Node Type Hybrid IP Routing Enabled No WINS Proxy Enabled No DNS Suffix Search List company com Figure 4 2 shows an example of part of the nbsu output file for the bpgetconfig command 158 Using NetBackup utilities About the NetBackup support utility nbsu Figure 4 2 Example nbsu output file bpgetconfig command excerpt sina ae ae ok AAR AGE NetBackup bpgetconfig information report
59. or Specifies that the log file rollover occurs whenever the RolloverAtLocalTime file size limit or the local time limit is reached whichever is first MaxLogFileSizeKB or Specifies that the log file rollover occurs whenever the RolloverPeriodInSeconds file size limit or the periodic time limit is reached whichever is first By default log file rollover is based on a file size of 5120 KB When a log file reaches 5120 KB in size the file closes and a new log file opens The following example sets the NetBackup prodid 51216 rollover mode to Periodic vxlogcfg a prodid 51216 orgid 116 s RolloverMode Periodic RolloverPeriodInSeconds 86400 The previous example uses the vx loge fg command with the RolloverMode option It sets rollover mode for nbpem originator ID 116 to Periodic It also sets the interval until the next nbpem log file rollover to 24 hours 86400 seconds In the following example the file names show the log file rollover with the rotation ID incremented Using logs 115 About unified logging usr openv logs nbpem 51216 116 2201360136 041029 0000000000 1log usr openv logs nbpem 51216 116 2201360136 041029 0000000001 1log usr openv logs nbpem 51216 116 2201360136 041029 0000000002 1log In addition you can use log file rotation with the following m Logs for the server processes that use unified logging See Server processes that use unified logging on page 106 m Certain legacy l
60. pying sr openv 1 logs n logs n logs n logs n logs n logs bmrsetup 512 bemm 51216 brb 51216 1 bjm 51216 1 bpem 51216 logs bmrsetup 51216 157 2202872032 050125 0000000000 log logs nbemm 51216 111 2202872032 050125 0000000000 log logs nbrb 51216 118 2202872032 050125 0000000000 1log logs nbjm 51216 117 2202872032 050125 0000000000 log logs nbpem 51216 116 2202872032 050125 0000000000 1log logs nbs1 51216 132 2202872032 050125 0000000000 log 6 157 2202872032 050125 0000000000 log 11 2202872032 050125 0000000000 log 8 2202872032 050125 0000000000 log 7 2202872032 050125 0000000000 log 16 2202872032 050125 0000000000 log bs1 51216 132 2202872032 050125 0000000000 log 104 Using logs About unified logging 3 Change to the upload directory and list its contents cd upload ls Example output 51216 111 2202872032 050125 0000000000 1log 51216 116 2202872032 050125 0000000000 log 51216 117 2202872032 050125 0000000000 log 51216 118 2202872032 050125 0000000000 1log 51216 132 2202872032 050125 0000000000 log 51216 157 2202872032 050125 0000000000 1log 4 Tar the log files tar cvf file_name logs Types of unified logging messages The following message types can appear in unified logging files Application log messages Diagnostic log messages Application log messages include informational warning and error messages They are always l
61. s Guide Volume I To limit the amount of disk space that the logs consume use robust logging Robust logging involves file rotation like that which is used in unified logging Robust logging does not apply to media and device management logging See About rolling over unified log files on page 113 Specify the maximum size for a log file and the maximum number of log files to keep in a logging directory When a log file grows to its maximum size it closes and anew file opens If the number of log files exceeds the number that is allowed for the directory the oldest file is deleted Logs created by the following NetBackup processes can use log rotation robust logging E bpbkar client process only E bpbrm E bpcd E bpdbm E bpdm E bprd E bptm 132 Using logs About legacy logging For the legacy logs created by other NetBackup processes except media and device management logs use the Keep logs property The Keep logs property may override the robust file logging settings If Keep logs is set to 10 days and robust file logging settings allow more than 10 days the logs are deleted on day 11 For media and device management legacy logs use the Days TO KEEP LOGS setting in the vm conf file to control log file rotation The default is infinite retention The vm comf file is located in the following directory UNIX usr openv volmgr Windows install_path Volmgr To retain logs for three days enter the
62. saves time since robotic and drive device paths are passed to the test utility automatically To use the robtest command do the following in the order presented Robotic test utilities 313 Robotic tests on Windows m Execute the following command install _path Volmgr bin robtest exe The test utility menu appears m Select arobot and press Enter The test starts Note If the robot is not configured you cannot use robtest and must execute the command that applies to the robot you are testing see following list ACS install_path Volmgr bin acstest r ACSLS_HOST TL4 install _path Volmgr bin tl4test r roboticpath TL8 install _path Volmgr bin tl8test 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 More information on ACS TLH and TLM robotic control is available See the NetBackup Device Configuration Guide In the previous list of commands roboticpath is the full path to the device file for the robotic control SCSI You can review the section for your platform to find the appropriate value for roboticpath An optional parameter specifies the device file path for the drives so that this utility can unload the drives using the SCSI interface Usage is install path lt p port b bus t target l lan r roboticpath gt where roboticpath is the changer name e g Chang
63. starting stopping 79 troubleshooting 75 pbx_exchange 76 283 pbxcfg 76 preliminary troubleshooting procedure 21 Private Branch Exchange PBX 75 procedures recovery Windows client disk 194 troubleshooting communications problems 41 48 host names and services 52 installation and configuration 26 introduction 20 master server and clients 33 media server and clients 36 preliminary 21 processes see functional overview 235 product ID for NetBackup 105 productID unified logging 105 Q ql2300_stub 283 query string 116 queued jobs 69 R raw partitions backup process 236 restore process 256 recording information 14 recovery procedures Windows client disk 194 RedHat 27 relational database 70 reports NetBackup 100 reqlib directory 125 restore process 256 NetWare client 264 Windows 2000 client 263 retention of logs 113 robot drive selection 290 robotic control daemons 288 robotic daemons 288 robotic test utility 311 acstest 313 odltest 312 tl4test 312 313 tl8test 312 313 tldtest 312 313 tlhtest 313 tshtest 312 robtest 311 312 robust file logging 121 RolloverMode 123 rotation legacy logging 131 of logs 114 unified logging 105 S SAN Client 246 SAN client and bp conf 92 SANPoint Control 93 Secure Mode for PBX 77 server installation problems 26 NetBackup debug logs 125 server continued test procedure for master 33 37 test procedure for media server 36 SERVER entries bp conf 92 services entries ch
64. support options Nontechnical presales questions Issues that are related to CD ROMs or manuals Support agreement resources If you want to contact Symantec regarding an existing support agreement please contact the support agreement administration team for your region as follows Asia Pacific and Japan customercare_apac symantec com Europe Middle East and Africa semea symantec com North America and Latin America supportsolutions symantec com Contents Technical Support sccsceavesis connie cosa vadecrsonedees favedbdsvannonssnannvsdsiaundsdevautesacysavienatval velous 4 Chapter 1 ntroduction ercseccesccsncasdersivecatsainitsevnindsnscpmmnaeinmnetsieemideniveawnets 13 Troubleshooting a problem cccceccececneceee cence eceeeeeeeeeeeeeeeeees 13 Problem report for Technical Support ccccecceceeceeeeeeeeeneeees 15 About gathering information for NetBackup Java applications 17 Chapter 2 Troubleshooting procedures s s 19 About troubleshooting procedures cccceceeeeceeeceeeeeeeaeeeeeenes 20 Troubleshooting NetBackup problems cceceececeeeeeeeeeeeeeees 20 Verifying that all processes are running on UNIX servers 23 Verifying that all processes are running on Windows SOLVELS aiora na aE I EAE EEEE REAN 24 Troubleshooting installation problems ccceceeeceeeeeeeeeeeeees 26 Troubleshooting configuration problems cc
65. the EMM db SHARED DISK lt top level shared disk mount point gt dataDir SHARED DISK db data usr openv netbackup bin nbdbms_ start_stop start usr openv db bin create_nbdb data dataDir index dataDir tlog dataDir mlog dataDir staging dataDir staging drop usr openv volmgr bin tpext loadEMM 4 Configure required devices and media and recover the NetBackup catalogs See Recovering the master server when root is intact on page 178 Manually shut down and restart NetBackup on the active node Re enable monitoring of the NetBackup resource group Verify that the NetBackup server can now be brought online on all configured nodes Recovering the entire UNIX or Linux cluster The following procedure applies to the clustered NetBackup server environment that must be re created from scratch Before you proceed ensure that you have valid online catalog backups To recover the entire UNIX or Linux cluster 1 Configure the hardware system software and cluster environment on the replacement cluster 2 Ensure that the appropriate low level tape device and robotic control device configuration necessary for your operating system has been performed Refer to the NetBackup Device Configuration Guide 3 Reinstall NetBackup on each of the cluster nodes Be sure to use the NetBackup Virtual Name as the name of the NetBackup server Follow the instructions for installing NetBackup server software
66. the hot catalog backup run a Phase II import on the media that is specified by the disaster recovery file bpimport server master_server backupid backup_id If your catalog backup was incremental recover all the other catalog backup images up to and including the most recent Full Catalog backup m Open the Backup Archive and Restore client interface for NetBackup Select NBU Catalog as the policy type Set the source clients and destination clients to your master server m Search the backups and restore all files that are located in the following directory install _path netbackup db images master server m Verify that all files are restored successfully on the master server Restore your critical data by using the Backup Archive and Restore client interface or the command line m Restore the catalog backup images for each media server which requires data recovery m To restore the backup images select NBU Catalog as the policy type Source and destination clients should be your master server Refresh your view in the BAR GUI Traverse the file system for the master server to the following install_path netbackup db images Restore the images for each configured media server Verify that your images are present by searching for them in the catalog Recover backup data from each media server in the previous step Change the Policy Type Source and Destination client to match the client that is used to back up the desir
67. the master server that being recovered To recover the catalog image files using the Catalog Recovery Wizard 1 Start NetBackup by entering the following If your configuration includes an EMM server that is separate from the master server do the following start NetBackup on the EMM server before starting NetBackup on the master server On UNIX and Linux usr openv netbackup bin bp start_all On Windows install _path NetBackup bin bpup Click Recover the Catalogs in the NetBackup Administration Console to start the Catalog Recovery Wizard Warning Do not run any client backups before you recover the NetBackup catalog Disaster recovery 213 How to recover a catalog from a backup This wizard relies on the disaster recovery information that was generated during the online hot catalog backup Part of configuring the catalog backup included the indication of where the disaster recovery information was to be stored and sent NetBackup Catalog Recovery Wizard xj Welcome to the NetBackup Catalog Recovery Wizard This wizard quides you in recovering the NetBackup catalog from a hot online catalog backup To recover from a cold offline catalog backup use the bprecover command as described in the System Administrator s Guide Run this wizard only in the event of a disaster that requires the recovery of all or portions of the NetBackup catalog This should be run before starting any backups To begin
68. to as recycling You can recycle unified logging files in the following ways Limit the number of log files Specify the number of days the log files are kept Explicitly delete the log files Specify the maximum number of log files that NetBackup retains When the number of log files exceeds the maximum the oldest log files are automatically deleted The NumberOfLogFiles option for the vx logcfg command defines that number The following example sets to 8000 the maximum number of log files that are allowed for all unified logging originators in the NetBackup product ID 51216 When the number of log files exceeds 8000 for a particular originator the oldest log files are automatically deleted vxlogcfg a p 51216 o ALL s NumberOfLogFiles 8000 See Examples of using vxlogcfg to configure unified logs on page 121 Use the Keep logs property to specify the maximum number of days logs are kept When the maximum number of days is reached the unified logs and legacy logs are automatically deleted In the NetBackup Administration Console in the left pane expand NetBackup Management gt Host Properties gt Master Servers Double click the server you want to change A new dialog box appears In the left pane click Clean up gt Keep logs Use the vxlogmgr command If you cannot manually delete or move files with vxlogmgr the Keep logs property removes the old logs for both unified logging and legacy logging Se
69. to the regional display short date format m A long value of number of seconds that elapsed since midnight January 1 1970 Table 3 7 provides examples of query strings Table 3 7 Examples of query strings PRODID 51216 amp amp PID 178964 STDATE 2 5 09 00 00 00 AM amp amp ENDATE 2 5 03 12 00 00 PM prodid NBU amp amp stdate gt 11 18 09 0 0 0 AM amp amp endate lt 12 13 09 13 0 0 AM l prodid BENT amp amp stdate gt 12 12 09 0 0 0 AM amp amp endate lt 12 25 09 25 0 0 PM STDATE lt 04 05 09 0 0 0 AM Retrieves the log messages that were logged on or before 2009 05 04 for all the installed Symantec products Examples of using vxlogview to view unified logs The following examples demonstrate how to use the vxlogview command to view unified logs Using logs About unified logging Table 3 8 Example uses of the vxlogview command Display specific Display the log messages for NetBackup 51216 that show only attributes of the log the date time message type and message text messages vxlogview prodid 51216 display D T m x Display the latest log Display the log messages for originator 116 nbpem that were messages issued during the last 20 minutes Note that you can specify o nbpem instead of o 116 vxlogview o 116 t 00 20 00 Display the log Display the log messages for nbpe
70. verify that the NetBackup configuration is correct Several examples follow the procedure For more information on host names see the following m See Background for troubleshooting on page 305 m See the NetBackup Administrator s Guide Volume II To verify the host name and service entries in NetBackup 1 Verify that the correct client and server host names are configured in NetBackup The action you take depends on the computer that you are checking On Windows servers Windows clients and NetWare nontarget clients Troubleshooting procedures 53 Verifying host name and service entries in NetBackup Do the following m Onthe Server to use for backups and restores drop down list ensure that a server entry exists for the master server and each media server Start the Backup Archive and Restore interface on the client On the File menu click Specify NetBackup Machines and Policy Type In the Specify NetBackup Machines and Policy Type dialog box click the Server to use for backups and restores drop down list On Windows systems 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 UNIX systems if you add or modify SERVER entries on the master server stop and restart bprd and bpdbm m On the General tab verify that the client name setting is
71. where the log files for originator IDs are written These directories and the log files that they hold are written to the following directory except as noted in Table 3 2 UNIX usr openv logs Windows install_path NetBackup logs Table 3 2 lists the NetBackup server processes that use unified logging Table 3 2 Originator IDs for the server processes that use unified logging 103 None m Private Branch Exchange service PBX m Writes logs to opt VRTSpbx log UNIX and install_path VxPBX log Windows 111 nbemm m Enterprise Media Manager EMM m Runs only on the EMM server 116 nbpem m NetBackup Policy Execution Manager m Runs only on the master server 117 nbjm m NetBackup Job Manager m Runs only on the master server 118 nbrb m NetBackup Resource Broker m Runs only on the EMM server 119 bmrd and bmrbd m Bare Metal Restore BMR master or boot server daemons E bmrbd runs on the BMR boot server Table 3 2 Using logs 107 About unified logging Originator IDs for the server processes that use unified logging continued 121 bmrsavecfg m Bare Metal Restore data collection utility m Runs on the NetBackup client not server 122 bmre m Bare Metal Restore utility m Originates on the BMR boot server and runs on the restoring client m UNIX clients use it to communicate to the BMR master server during a restore 123 bmrs Bare Metal Restore commands and data
72. window so you can see the results The bpclntcmad 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 ip bpclntcmd ip IP Address The ip option lets you specify an IP address bpclntcmd uses gethostbyaddr on the NetBackup node and gethostbyaddr returns the host name with the IP address as defined in the following the node s DNS WINS NIS or local hosts file entries No connection is established with the NetBackup server hn bpclntcmd hn Hostname The hn option specifies a host name bpclntcmd uses gethostbyname on the NetBackup node to obtain the IP address that is associated with the host name defined in the following the node s DNS WINS NIS or local hosts file entries No connection is established with the NetBackup server SV bpclntcmd sv The sv option displays the NetBackup version number on the master server 68 Troubleshooting procedures About the bpclntcmd utility pn When the pn option is run on a NetBackup client it initiates an inquiry to the NetBackup master server The server then returns information to the requesting client First the server is the 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
73. you recover in a manual recovery an asterisk indicates multiple files within that folder Table 5 1 Files you recover when you recover catalog image files usr openv netbackup bp conf install_path NetBackup db usr openv netbackup db install_path NetBackup vault sessions usr openv netbackup vault sessions install path NetBackup var usr openv var install_path Volmgr database usr openv volmgr database install _path Volmgr vm conf usr openv volmgr vm conf The following is alist of NetBackup relational database SQL Anywhere files that are not recovered in a manual recovery NBDB db NBDB log EMM DATA db EMM INDEX db BMRDB db BMRDB log BMR_ DATA db BMR_INDEX db vxdbms conf DARS_DATA db DARS_INDEX db DBM_DATA db DBM_INDEX db The following is where they reside E install path NetBackupDB conf server conf Windows only E install path NETBACKUP DB conf databases conf Windows only You can recover these files See Recovering relational database files from an online catalog backup on page 219 212 Disaster recovery How to recover a catalog from a backup Recovering the catalog image files using the Catalog Recovery Wizard You must have root administrative privileges to perform this procedure Note The Catalog Recovery Wizard does not work after you perform a change server operation You must be logged on locally to
74. 07 308 Networks and hostnames Background for troubles hooting Any of these client names can require manual modification by the administrator if the following a client has multiple network connections to the server and restores from the client fail due to a connection related problem On UNIX the public domain program traceroute not included with NetBackup often can provide valuable information about a network s configuration Some system vendors include this program with their systems The master server may be unable to reply to client requests if the Domain Name Services DNS are used and the following is true the name that the client obtains through its gethostname library UNIX or gethostbyname network Windows function is unknown to the DNS on the master server The client and the server configurations can determine if this situation exists gethostname or gethostbyname on the client may return an unqualified host name that the DNS on the master server cannot resolve Although you can reconfigure the client or the master server DNS hosts file this solution is not always desirable For this reason NetBackup provides a special file on the master server This file is as follows usr openv netbackup db altnames host xlate UNIX and Linux install_path NetBackup db altnames host xlate Windows You can create and edit this file to force the desired translation of NetBackup client host names Each line in the
75. 5 Resolving network communication problems with UNIX clients Table 2 8 Steps for resolving network communication problems with UNIX clients continued Run one of the following commands depending on platform and operating system netstat a grep bpcd netstat a grep 13782 rpcinfo p grep 13782 If no problem occurs with the port the results are similar to tee 0 0 13782 LISTEN LISTEN indicates that the client listens for connections on this port If a problem occurs this line does not appear One of the following conditions may exist m etc services or applicable NIS file does not have the correct bpcd entry The correct etc services entry is bpcd 13782 tcp bpcd m etc inetd conf or applicable NIS or DNS file does not have the correct bpcd entry The correct etc inetd conf entry is bpcd stream tcp nowait root usr openv netbackup bin bpcd m etc inetd conf was changed but was not re read Correct this condition by running one of the following whichever works bin ps ef grep inetd kill HUP the inetd pid Or bin ps aux grep inetd kill HUP the inetd pid On a Hewlett Packard platform use inetd c to send a SIGHUP to inetd On an AIX client use SMIT to verify that the InetServ object policy was updated with information about the bpcd process etc inetd conf and etc services information If you use SMIT to modify the InetServ object policy the inetexp command automatically r
76. 6 n 15 Delete the log files for Delete all unified log files for originator nbrb a specific originator vxlogmgr d o nbrb Delete all the log files Delete all unified log files for NetBackup vxlogmgr d p NB Examples of using vxlogcfg to configure unified logs Use the vxlogcfgcommand to change logging levels and rollover settings The vxlogcfg command has the following characteristics m The vxlogcfg command is the only way to turn off diagnostic and debug messages in unified logging In legacy logging the writing of messages cannot be turned off only minimized m The vxlogcfg options for robust file logging MaxLogFileSizeKB and NumberOfLogFiles also affect certain legacy logs See About limiting the size and the retention of legacy logs on page 131 m Absolute paths must be specified Do not use relat Control the log file size ive paths The following examples show how to use the vxlogcfg command to configure unified logging settings 122 Using logs About unified logging Table 3 10 Example uses of the vxlogcfg command Set the maximum log By default the maximum log file size in unified logging is 5120 file size KB When a log file reaches 5120 KB the file closes and a new log file opens You can change the maximum file size with the MaxLogFileSizekB option The following command changes the default maximum log size to 2048 KB for the NetBackup product vxlogcefg a p 51216 o
77. 78 Step 2 Use reports to check for errors 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 Often it provides specific information which is useful when the status code can result from a variety of problems See the NetBackup Administrator s Guide Volume I If the problem involved a backup or archive check the Status of Backups report This report gives you the status code If you find a status code or message in either of these reports perform the recommended corrective actions See the Status Codes Reference Guide Step 3 Check the operating system logs Check the system log on UNIX or the Event Viewer Application and System log on Windows if the problem pertains to media or device management and one of the following is true m NetBackup does not provide a status code m You cannot correct the problem by following the instructions in NetBackup status codes and messages m You cannot correct the problem by following the instructions in media and device management status codes and messages These logs can show the context in which the error occurred The error messages are usually descriptive enough to point you to a problem area Step 4 Review the debug logs Read the applicable enabled debug logs and correct any problems you detect If these logs are not enabled enable them before you
78. Accessing the PBX logs PBX uses unified logging PBX logs are written to the following E opt VRTSpbx 1log UNIX E install path VxPBX log Windows The unified logging originator number for PBX is 103 More information is available about unified logging See About unified logging on page 102 Error messages regarding PBX may appear in the PBX log or in the unified logging logs for nbemm nbpem nbrb or nbjm The following is an example of an error that is related to PBX 05 11 10 10 36 37 368 Critical V 137 6 failed to initialize ORB check to see if PBX is running or if service has permissions to connect to PBX Check PBX logs for details 78 Troubleshooting procedu Resolving PBX problems res To access the PBX logs 1 Use the vxlogview command to view PBX and other unified logs The originator ID for PBX is 103 For more information see the vxlogview man page You can also refer to the following topic See About unified logging on page 102 2 To change the logging level for PBX enter the following pbxcfg s l debug level where debug_levelis anumber from 0 to 10 where the settings 10 is the most verbose PBX may log messages by default to the UNIX system logs var adm messages or var adm syslog or to the Windows Event Log As a result the system logs may fill up with unnecessary PBX log messages since the messages are also written to the PBX logs opt VRTSpbx log on UNIX and lt install_path gt
79. Backup 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 bpjava usvc legacy log directory 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 by executing the usr openv netbackup bin bplist command on the client Stopped By Completion of operation Debug Log bplist legacy log directory on the client Table A 4 Backup and restore functional overview 277 NetBackup programs and daemons NetBackup daemons and programs continued bprd On master servers the request daemon responds to client and administrative requests for the following Restores Backups scheduled and user directed Archives List that is backed up or archived files Manual immediate backups started through the NetBackup administration interface manual backup option Started By Initiate Request Daemon option on the Special Actions menu in bpadm also the usr openv netbackup bin initbprd command Stopped By Terminate Request Daemon option on the Special Actions menu in bpadm Debug Log bprd legacy log directory on the server bprestore On UNIX clie
80. Client service and verify that the bpinetd program is no longer running Restart 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 About clustered NBU server recovery for Windows NetBackup server clusters do not protect against catalog corruption loss of the shared disk or loss of the whole cluster Regular catalog backups must be performed More information is available about configuring catalog backups and system backup policies in a clustered environment Disaster recovery About clustered NBU server recovery for Windows Refer to topics about configuring NetBackup in the NetBackup High Availability Guide Warning Contact technical support before you try these recovery procedures Replacing a failed node on a Windows VCS cluster Cluster technology specific information is available about how to bring the NetBackup resource group online and offline Also it is available on how to freeze and unfreeze disable and enable the monitoring for the resource group Refer to topics about configuring NetBackup in the NetBackup High Availability Guide Check the following conditions before you proceed with this procedure The hardware system software and cluster environment on the replacement node have been configured The reconfigured node or replacement node has been made a member of the cluster and has the same name as the failed n
81. Default s MaxLogFileSizeKB 2048 For MaxLogFileSizekB to be effective the RolloverMode option must be set to FileSize vxlogcfg a prodid 51216 orgid Default s RolloverMode FileSize MaxLogFileSizexkBcan beset per originator An originator that is not configured uses the default value The following example overrides the default value for service nbrb originator 118 vxlogcfg a p 51216 o nbrb s MaxLogFileSizeKB 1024 Set log recycling The following example sets automatic log file deletion for nbemm logs originator ID 111 vxlogcfg a prodid 51216 orgid 111 s RolloverMode FileSize MaxLogFileSizeKB 5120 NumberOfLogFiles 999999 LogRecycle TRUE This example sets nbemm rollover mode to file size and turns on log recycling When the number of log files exceeds 999999 the oldest log file is deleted EXAMPLE 5 shows how to control the number of log files Set the debug level and The following example sets the debug level and diagnostic level diagnostic level for all the originators of product ID NetBackup 51216 vxlogcfg a prodid 51216 orgid ALL s DebugLevel 0 DiagnosticLevel 1 Using logs 123 About unified logging Table 3 10 Example uses of the vxlogcfg command continued List the unified logging settings The following vxlogcfg example shows how to list the active unified logging settings for a given originator the nbrb service Note that MaxLogFileSizeKB NumberOfLogFi
82. H Half duplex and poor performance 91 help files Media and Device Management 296 UNIX client 270 host name entries checking 52 Host Properties 69 host xlate file 308 hostID unified logging 105 ifconfig for checking NIC duplex mode 91 images database 285 inetd 27 Information E mail 176 installation Linux 27 installation problems 26 ipconfig for checking NIC duplex mode 91 J Java interface debug logging 147 troubleshooting background 145 jbpSA overview 278 job ID search in unified logs 120 318 Index jobs queued for long periods 69 jobs database 285 K Keep logs For setting 113 Keep Logs setting 131 L legacy logging 125 client logs 133 configuring rotation 133 controlling size of 131 directories 125 file name format 126 locations 125 PC clients 135 rotation of 131 levels for logging 138 Linux 27 log analysis utilities debug logs 150 limitations 153 output format 153 Log level Windows and NetWare clients 140 logging changing location of 112 levels 138 see legacy logging 125 setting level on PC clients 140 synthetic backup 141 logs debug enabling detailed 147 event viewer logging option 143 file retention 113 overview Logs aaa 99 PC client activity bp 136 bparchive 136 bpbackup 136 bpbkar 136 bpcd 136 bpinetd 136 bplist 137 bpmount 137 logs continued PC client activity continued bprestore 137 bpsrv 137 tar 137 user_ops 138 reports NetBackup 100 server activity acssi 129
83. IR ROEDER ae cE T nbsu diagnostic name and internal procedure used NBU_bpgetconfig NBU_get_bpgetconfig_info a GRA CA RIC Re a ca a ee a Command Used soe SSS SSS SSS gt C Program Files VERITAS netbackup bin admincemd bpgetconfig g hostl L Client Master Master NetBackup Client Platform PC Windows2000 NetBackup Client Protocol Level 6 5 0 Product NetBackup Version Name 6 5Alpha Version Number 650000 NetBackup Installation Path C Program Files VERITAS NetBackup bin Client OS Release Windows2003 5 SAA ee eg ee ee Command Used gt C Program Files VERITAS netbackup bin admincmd bpgetconfig SERVER hostl SERVER host2 SERVER host3 SERVER host4 SERVER host5 SERVER host6 SERVER host7 If the executed command returned a non zero status an EXIT STATUS header indicates the status For example EXIT STATUS 227 As part of the internal processing of each command that a diagnostic command runs nbsu redirects each command s STDERR to an internal file If the command writes information to STDERR nbsu captures this information and includes a STDERR header along with the information For example STDERR bpclient no entity was found 227 If a supported archive program is available on the host where nbsu runs nbsu bundles its output file
84. Information is available on how the tape request is issued See Media and device management process on page 289 bptm sends backup completion status to bpbrm which passes it to nbjm When nbpen receives backup completion status from nbjm nbpem tells nbjm to delete the snapshot nbjm starts a new instance of bpbrm on the media server and bpbrm starts a new instance of bpfis on the client bpfis deletes the snapshot on the client unless the snapshot is of the Instant Recovery type in which case it is not automatically deleted bpfis and bpbrm report their status and exit For more information on snapshot backups involving Snapshot Client refer to the following 246 Backup and restore functional overview Backups and archives UNIX clients SAN client See the NetBackup Snapshot Client Administrator s Guide Note that Windows open file backups do not require Snapshot Client For backups to disk the SAN Client feature provides high speed data movement between NetBackup media servers and NetBackup SAN attached clients SAN attached clients send backup data to the media server by means of fibre channel connections As part of SAN Client the FT Service Manager FSM is a domain layer service that resides on the EMM server The FSM provides discovery configuration and event monitoring of SAN Client resources The FSM collects fibre channel information from the client and from the media server FSM then populates the EMM datab
85. M Server hostname Gathering NetBackup EMM merge table list Found 0 EMM merge table records Summary of gathered NetBackup catalog information End time 2010 10 18 10 19 14 Number of Images gathered 3039 Number of database corrupt images gathered 0 Number of EMM database Media attribute records gathered 207 Number of EMM database Volume attribute records gathered 321 Catalog data gathering took 8 seconds to complete 166 Using NetBackup utilities About the NetBackup consistency check utility NBCC dir results for created NBCC files 4 0 Verifying required catalog components were gathered 5 0 Beginning NetBackup catalog consistency check Start time 2010 10 18 10 19 16 5 1 There were no no tape media involved in active NetBackup jobs 5 3 Processing EMM database Volume attribute records pass 1 of 2 321 records to be processed Processed 321 EMM database Volume attribute records 5 4 Checking for duplicate EMM server host names in Volume attribute data 5 5 Processing Image DB pass 1 of 2 30391 images to be processed 30391 images processed on pass 1 5 6 Processing EMM database Media attribute records pass 1 of 3 207 records to be processed Processed 207 EMM database Media attribute records 5 8 Check for duplicate media server names in the EMM database Media attribute data 5 9 Processing EMM database Media attribute records pass 2 of 3 207 records to be processed 5 10 Processing Image DB pass 2
86. Manager or Explorer Check the following disk partitions m The partition where NetBackup software is installed m On the NetBackup master or media server the partition where the NetBackup databases reside m The partition where the NetBackup processes write temporary files m The partition where NetBackup logs are stored m The partition where the operating system is installed Step 9 Increase the logging level Enable verbose logging either for everything or only for areas that you think are related to the problem See Changing the logging level on page 140 See How to control the amount of information written to legacy logging files on page 130 See Changing the logging level on Windows and NetWare clients on page 140 Troubleshooting procedures 23 Troubleshooting NetBackup problems Table 2 1 Steps for troubleshooting NetBackup problems continued Step 10 Determine which daemons Follow the procedures for UNIX or Windows NetBackup servers or processes are running PARER P 8 See Verifying that all processes are running on UNIX servers on page 23 See Verifying that all processes are running on Windows servers on page 24 Verifying that all processes are running on UNIX servers For NetBackup to operate properly the correct set of processes daemons must be running on your UNIX servers This procedure determines which processes are running and shows h
87. NG media id 000199 it contains ANSI format data and cannot be used for backups These library tapes may have been written outside of NetBackup By default NetBackup only writes to a blank media or other NetBackup media Other media types DBR TAR CPIO ANSI MTF1 and recycled Backup Exec BE MTF1 media are frozen as a safety measure Change this behavior by using the following procedure On UNIX and To allow NetBackup to overwrite foreign media add the following Linux to the bp conf file that is located at usr openv netbackup bp conf for the related media server ALLOW MEDIA OVERWRITE DBR ALLOW MEDIA OVERWRITE TAR ALLOW MEDIA OVERWRITE CPIO ALLOW MEDIA OVERWRITE ANSI ALLOW MEDIA OVERWRITE MTF1 ALLOW MEDIA OVERWRITE BE MTF1 Stop and restart the NetBackup daemons for the changes to take effect 74 Troubleshooting procedures Frozen media troubleshooting considerations On Windows On the Administration Console proceed to Host Properties Media Server Open the properties for the media server in question Select the Media tab The Allow Media Overwrite property overrides the NetBackup overwrite protection for specific media types To disable the overwrite protection select one or more of the listed media formats Then stop and restart the NetBackup services for the changes to take effect Do not select a foreign media type for overwriting unless you are sure that you want to overwrite this media t
88. Number OriginMasterServer master tlk OriginMasterServerID 00000000 0000 0000 0000 000000000000 88 Troubleshooting procedures About troubleshooting duplication to a remote master Import From Replica Time Required Expiration Date Created Date Time Copy Master Server Backup ID Copy Number Copy Type Expire Time Expire LC Time Try To Keep Time Residence Copy State Job ID Retention Type MPX State Source Destination ID Last Retry Time Fragment Master Server Backup ID Copy Number Fragment Number Resume Count Media ID Media Server Storage Server Media Type Media Sub Type Fragment State Fragment Size Delete Header Fragment ID 0 0 128 Wed Dec 31 18 00 00 1969 Wed Dec 31 18 00 00 1969 7678771 Thu Oct 21 11 32 51 2010 bayside min veritas com gdwinl in04 1280299412 Wed Dec 31 18 00 00 1969 Wed Dec 31 18 00 00 1969 none NOT FAL baysid gdwinl 1 21474 0 aaaab baysid baysid 0 DIS 0 DEF 1 ACT 0 ac gdwinl 1 0 0 FIXED 0 0 al 4 0 Wed Dec 31 18 00 00 1969 0 0 specified STARTED SE e min veritas com in04 1280299412 82648 e min veritas com e min veritas com K AULT IVE in04 1280299412 Cl_IM The action taken on the automatic import job and the automatic import event depends on the several conditions as shown in the following table Action Automatic import jobs queue Condition
89. S NetBackup Logs NetWare clients SYS VERITAS NBUCLT NetBack logs Note These are the default locations in which to place these directories You can specify another location during client installation Table 3 16 lists the legacy debug log directories that apply to these clients 136 Using logs About legacy logging Table 3 16 PC client processes that use legacy logging bp NetWare target Client user interface program for NetWare bpinetd Windows2003 Client service logs These logs have information on the bpinetd32 process bparchive Windows 2003 Archive program that is run from the command line bpbackup Windows 2003 The backup program that is run from the command line bpbkar Windows 2003 Backup and archive manager These logs have information on the bpbkar32 process bpced All Windows and NetWare NetBackup client daemon or clients manager These logs have information on communications between the server and client On NetWare clients these logs also contain the log information for the backup and restore processes bpjava msvc The NetBackup Java bpjava msvc application server authentication service that the Client Services service starts during startup of the NetBackup Java interface applications This program authenticates the user that started the application On all Windows platforms Table 3 16 bpjava usvc Using logs 137 About legacy logging PC client proces
90. WINS m DNS if applicable m hosts file in system directory 2SystemRoot system32 drivers etc hosts Windows XP or 2003 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 you proceed As a first step verify that the workstation is turned on A workstation that is not turned on is a common source of connection problems with PC workstations On Microsoft Windows or NetWare clients check the NetBackup Client service Do one of the following tasks m Ensure that the service is active by checking the logs or by doing one of the following Windows XP or Use the Services application in the Control Panel to verify Windows Server 2003 that the NetBackup Client service is running Start it if clients necessary NetWare clients Enter modules bpcd nim from the NetWare server console to verify that the NetBackup client daemon is running If necessary type bpstart ncf from the NetWare server console to start the NetBackup client daemon m Check the bpca debug logs for problems or errors Instructions are available on how to enable and use these logs See About legacy logging on page 124 m Verify that the same NetBackup client service bpcd port number is specified on both the NetBackup client and server by default 13782 Do one of the following 50 Troubleshooting procedures Resolvin
91. a 00c00ees 233 Backup and restore functional overview s 235 About backup and restore functional overview c0cceeeeeeenes 235 Backup and restore startup process cccc cece cscs eceeeeeeeeeeeeenenens 236 Appendix B Appendix C Appendix D Contents Backup and archive processes ccccccecececececeeeeeeeeeeneneenenenenenes 236 Job schedtling neee e e E E E eos tia AEE e 236 EMM server and master server 0cceceeeecee eens eceeeeneenenees 237 Backups and archives UNIX clients ccececceceececeeeeeeeeeeeenees 237 Backup proGess seii sc dcsadedecdndes Sack ba da ysebad be dada tele Sood bbe bees enii 238 Backup with multiple data streams cccceceesee ee eeeeeeeees 242 Snapshot backup and Windows open file backups 243 SAN Chen Pes 522 en cond dat owes Sesetantsn cece a a ae E Oa EES 246 Backups and archives Windows ccccceceeeeeceenenenenenenenes 249 Backups and archives NetWare clients cccceeceeeeneeeeeees 250 Synthetic backups ccceccececeeceeneceee eens eceeeeeeeeeeeeesaeeeeees 251 NetBackup online hot catalog backup ccccceceeeeeeeeeeees 254 Restore Processes oireisiin ate arara A ESEE ERT RT STER SEKVE SEn 256 Restoring UNIX and Linux clients 0 eee 256 Restoring SAN client UNIX or Windows 0cceceeeeeeeeee es 260 Restori
92. ace on the File menu click NetBackup Client Properties In the NetBackup Client Properties dialog box select the General tab In the Keep status of user directed backups archives and restores for field enter the number of days you want to retain the log files Click OK To set retention limits for the logs on NetWare clients 1 Open the following file veritas nbuclt netback bp ini Under Keep Logs Days specify the number of days to keep the logs Save the file with your changes Logging options with the Windows Event Viewer NetBackup Windows master servers can be configured so messages from NetBackup reports are written to the Windows Event Viewer Application log You Using logs 143 Logging options with the Windows Event Viewer can see these messages in the Application log and also use third party tools to monitor the Application log for these messages To route unified logging application and diagnostic messages for an originator to the Application log set the LogToOslog value to true for that originator The following example routes the application and diagnostic messages for nbrb to the Windows event log vxlogcfg a o nbrb p NB s LogToOslog true Note For this setting to take effect restart NetBackup services To enable the logging tool do the following m Create the following file on the NetBackup master serve install _path NetBackup db config eventlog m Optionally add an entry to
93. age 48 See Resolving network communication problems with UNIX clients on page 41 Troubleshooting procedures 69 Using the Host Properties window to access configuration settings Using the Host Properties window to access configuration settings The Host Properties window in the NetBackup Administration Console provides access to many configuration settings for NetBackup clients and servers For example you can modify the server list email notification settings and various timeout values for servers and clients The following are general instructions for using this window Many procedures in this guide also refer to the NetBackup Client Properties dialog box in the Backup Archive and Restore interface on Microsoft Windows clients This dialog box 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 box are also available in the Host Properties window To use the Host Properties window to access configuration settings 1 Inthe NetBackup Administration Console in the left pane expand NetBackup Management gt Host Properties 2 Depending on the host to be configured select Master Servers Media Servers or Clients On the Actions menu select Properties In the Properties dialog box in the left pane click the appropriate property and make your change Resolving full disk problems If the NetBackup ins
94. ailable due to drives that are down or configuration errors such as referencing an incorrect robot number NetBackup processes log messages to the NetBackup error log that help you pinpoint and resolve these types of issues In addition the Job Details dialog box available from the Activity Monitor contains messages that describe the following m The resources that the job requests Troubleshooting procedures 93 About troubleshooting NetBackup in a SAN environment m The granted allocated resources If ajob is queued awaiting resources the Job Details dialog lists the resources for which the job waits The three types of messages begin with the following headers requesting resource awaiting resource granted resource About troubleshooting NetBackup in a SAN environment NetBackup administrators may encounter any or all of the following common problems in a SAN storage area network environment m Intermittent backup failures m Connectivity issues drives that are down m SAN configuration changes If the SAN administrator rezones the network or masks an array in use by NetBackup some of the devices that NetBackup needs may be unavailable Either action causes backups to fail and drives to go down The only information available to the NetBackup administrator is an error 83 media open error or error 84 media write error status code You can use Veritas CommandCentral Storage to check elements of the SAN
95. air processing is complete NBCCR relocates the SRA file to the same directory NBCCR also creates the following output files and places them in the same directory E NBCCRcreates NBCCR History txt which is a history file of all the repair actions attempted mM NBCCR creates NBCCR output txt While it runs the NBCCR utility uses KeepOnTruckin txt which appears in the same location as the output files described above To terminate NBCCR while it processes repairs delete this file This action causes NBCCR to complete the current repair then shut down Any other interruption causes undetermined results The following sample NBCCR output txt files show the results of two Mcontents repairs One where all images were found on tape and one where one or more images were not found on the tape m Example 1 nBccr found all images on the tape The Mcontentsrepair action is successful MContents for ULT001 MediaServerExpireImagesNotOnTapeFlag ExpireImagesNotOnTape flag not set ULTOO1 MContents All images in images catalog found on tape MContents ULT001 status Success m Example 2 ngecer did not find one or more images on the tape The MContentsrepair action was not performed MContents for ULTO00 MediaServerExpireImagesNotOnTapeFlag ExpireImagesNotOnTape flag not set Did NOT find Backup ID winmaster_ 1234315163 Copy 1 AssignTime 2009 0 OLE Los 13 1234315153 on ULTOOO Leaving winmaster_ 1234315163 Copy 1 on ULTOOO in
96. alf 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 tl8cd Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin tlhcd command Stopped By Stopping Itid or by using the tlhcd t command Debug Log Errors are logged in the system log and robots debug log Debug information is included if the daemon is started with the v option either by itself or through Itid 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 ltid and a TLM robot that is in an ADIC Distributed AML Server DAS This daemon communicates with the TLM robotics through a network API interface Started By Starting ltid or independently by using the usr openv volmgr bin tlmd command Stopped By Stopping ltid or independently by finding the PID process id and then using the kill command Debug Log Errors are logged in the system log and robots debug log Debug information is included if the daemon is started with the v option either by itself or through Itid The v option is available only on UNIX Also add the VERBOSE option to the vm conf file Table B 2 Media and device management functional description Media and device management components Media and device management daemons and
97. alog from the online catalog backup using the recovery wizard or bprecover command Authentication data and authorization data is not copied back to the hosts from which it was backed up Instead it is copied to a staging area for use in step 4 224 Disaster recovery How to recover a catalog from a backup Runbprecover r vxss p lt policy name gt and supply the catalog backup policy name This action recovers authentication and authorization data from the staging area to the hosts from which it was backed up Start the authentication and authorization services Windows or daemons UNIX and Linux To configure NetBackup to use NetBackup Access Management Control set up the proper Access Control host properties for master servers media servers and clients Restart NetBackup Recovering the catalog from a nonprimary copy of a catalog backup By default the online hot catalog backup can have multiple copies and recovery is done from the primary backup copy The primary copy is the first or the original copy However you can recover from a copy other than the primary To recover the catalog from a non primary copy 1 If the copy of the catalog backup is on a medium other than tape do the following BasicDisk Make sure that the disk that contains the backup is mounted against the correct mount path as displayed in the disaster recovery file Disk pool For a catalog backup file in a disk pool do the following m
98. an inventory to update the NetBackup database 5 Click Next to display the Disaster Recovery Method dialog Select the Recover only NetBackup catalog image and configuration files radio option and click Next NetBackup Catalog Recovery Wizard xi Disaster Recovery Method ae Select one of the following recovery processes to recover the NetBackup catalog pe Recover only NetBackup catalog image and configuration files Does not recover the NetBackup relational database click Help for details For recovery of a 5x media server catalog see help for details To begin the restore click Next Once started it can not be canceled Bek ne ca Her _ Disaster recovery 215 How to recover a catalog from a backup The wizard displays the recovery progress and announces when the catalog has been recovered NetBackup Catalog Recovery Wizard Recovering Catalog Wait while the catalog is being recovered If the recovery is not successful consult the log file messages for an indication of the problem NetBackup Catalog Recovery Wizard Recovering Catalog Wait while the catalog is being recovered 216 Disaster recovery How to recover a catalog from a backup 7 The final panel indicates that the catalog backup images have been recovered NetBackup Catalog Recovery Wizard xj RI The full recovery of the NetBackup catalog is complete Go to Activity monitor and restart all N
99. and Restore user interface For a catalog that was backed up using the online method of NetBackup catalog image and configuration files recovery in either of the following ways m Use the Catalog Recovery Wizard See Recovering the catalog image files using the Catalog Recovery Wizard on page 212 m Usethebprecover wizard command See Recovering the catalog image file using bprecover wizard on page 217 During a manual recovery the wizard recovers only NetBackup policy files NetBackup backup image files and other NetBackup configuration files It does not recover the NBDB includes EMM or BMR databases If the backup from which you recover is an incremental catalog backup and no catalog backup images exist in the catalog the following occurs only the NetBackup policy backup image and configuration files that are backed up in that incremental backup are restored However all of the catalog backup images up to the last full catalog backup are restored So you can restore the rest of the policy images and configuration files from the Backup Archive and Restore interface If catalog backup images already exist all files that were included in the related set of catalog backups are restored The NBDB includes EMM and BMR if applicable databases must then be recovered by running the following bprecover r nbdb Disaster recovery 211 How to recover a catalog from a backup Table 5 1 is a list of the files that
100. and line bpbackup or EMM bparchive Y joysdeus ayealy disk bptm g parent Ata amp Share 9 Inf Q Memo bptm bpbkar ry Sage p A child Oe J 2 L I bpbrm c L ERD Oo gL g Backup Image a S Tape Disk C Mount For details on these components see the Media and Device Management Functional Description later in this chapter If the media server is backing up itself server and client on same host there is no bptm child bpbkar sends the data directly to shared memory S Oj S a a J Client C I li li li li I li Notes I I I I I I I li li I I I A separate parent job creates all snapshots followed by a child job that backs up the snapshot An exception is when Windows opens file backups that do not use multiple data streams The following sequence of operation is for snapshot creation and backup that includes Windows open file backups that employ multiple data streams m The NetBackup master server or primary client initiates the backup This action causes the NetBackup request daemon bpra to submit a backup request Backup and restore functional overview Backups and archives UNIX clients to the Policy Execution Manager nbpem nbpem processes the policy configurations nbpem through nbjm starts a parent job to create the snapshot This job is separate from the job that backs up the snapshot nbjm starts an instance of bpbrm throu
101. and the NetBackup Administration Console vmscd Debug information for the NetBackup Status Collection daemon Stop and restart vmscd after creating the directory Unless it is noted each directory should be created under the following directory UNIX usr openv volmgr debug 129 130 Using logs About legacy logging Windows install_path Volmgr debug NetBackup creates one log per day in each of the debug directories You can disable debug logging by deleting or renaming the following directory UNIX vmd command usr openv volmgr debug daemon Windows NetBackup Volume install _path Volmgr debug daemon Manager service See File name formats for legacy logging on page 126 See About limiting the size and the retention of legacy logs on page 131 See Directory names for legacy debug logs for media and device management on page 129 How to control the amount of information written to legacy logging files You can set legacy logging levels to increase the amount of information that NetBackup processes write in the logs The following settings affect legacy logging except media and device management m Increase the Global logging level See Changing the logging level on page 140 Note This setting also affects unified logging m On UNIX add a VERBOSE entry in the usr openv netbackup bp conf file If you enter VERBOSE without a value the verbose value defaults to 1 For more lo
102. any other servers that are connected to that robot and correct if necessary See the NetBackup Administrator s Guide Volume 1 15 Test the ability of NetBackup to perform restores using the configured devices on the replacement node 16 Unfreeze the NetBackup resource group Recovering the shared disk on a UNIX or Linux cluster The following procedure is applicable in situations where the configured cluster nodes remain available but files on the shared disk have been corrupted or lost These files can include the NetBackup catalog the database files or both The following conditions must be true to proceed with this procedure m The shared storage hardware is restored to a working state so that the shared disk resource can be brought online with an empty shared directory m Valid online catalog backups exist To recover the shared disk on a UNIX or Linux cluster 1 Clear the faulted NetBackup resource group disable monitoring and bring up the shared disk and virtual name resources on a functioning node 2 Manually create the following directories on the shared disk lt shared disk path gt netbackup db lt shared disk path gt db data lt shared disk path gt var global lt shared disk path gt volmgr misc robotic_db 186 Disaster recovery About clustered NBU server recovery for UNIX and Linux 3 If this server is an EMM server enter the following to bring up the database server and EMM then run tpext to initialize
103. ase with the information FSM runs in the same process as EMM FSM interacts with the nbftclnt process on NetBackup clients and with the nbftsrvr process on media servers The initial stages of a backup are the same as shown in Figure A 1 Figure A 4 shows the server and client components that are unique to SAN client backup over Fibre Channel Backup and restore functional overview 247 Backups and archives UNIX clients Figure A 4 SAN client backup over Fibre Transport EMM Server FT Service Manager FSM Part of EMM Master or Media Server UNIX Client Bptm parent Catalog Info Shared Memory Client disk ret Backup Image sent over Fiber eT Channel Storage Disk bpbkar Shared Memory gew anyoed The process flow for a SAN Client backup is as follows in the order presented m A start up script launches bprd on the master server and 1tid on the master server and all media servers All other daemons and programs are started as necessary including nbpen nb jm nbrb and nbemm m The policy execution manager service nbpem does the following m Gets the policy list from bpdbm m Builds a work list of all scheduled jobs m Computes the due time for each job m Sorts the work list in order of due time m Submits to nbjm all jobs that are currently due m Sets a wakeup timer for the next due job 248 Backup and restore functional overview Backups an
104. aster server m NetBackup creates the disaster recovery file and emails it to the administrator if the email option was selected in the policy Consult the following logs for messages on hot catalog backup E bpdbm bpbkar bpbrm bpcd bpbackup bprd Note If the EMM server is on its own host separate from the master server consult this log on the EMM server usr openv netbackup logs admin UNIX or install _path NetBackup logs admin Windows For messages pertaining only to the relational database files see the progress log file in the following directory E usr openv netbackup logs user_ops dbext logs UNIX E install _path NetBackup logs user_ops dbext logs Windows Restore processes NetBackup restore operations like backups can vary according to client type The following explains the variations Restoring UNIX and Linux clients Before starting a restore a user browses the file catalog to list the files available in the backup images The desired files can then be selected from the list The browsing is done through the bplist program on the client The bplist program can be started directly from the command line and the NetBackup user interface programs can use it bplist obtains the file list by sending a query to the request daemon bpra on the master server see Figure A 10 Backup and restore functional overview 257 Restore processes The request daemon in turn queries bpdbm for the inf
105. at are used for recovery Open the file in an editor and find values for the following master server Use the exact name that is specified in NetBackup configuration for the master server media_server The location of the robot or disk storage unit that is used for catalog backup timestamp The four most significant digits in the DR file name and six zeroes attached media The location of the catalog backup media as specified by the disaster recovery file under the FRAGMENT keyword backup_id Found in the DR file under BACKUP_ID Example file Hot_Backup_1122502016 INCR timestamp 1122000000 4 Create the DR recovery directory on the master server UNIX and Linux usr openv netbackup db images master_server timestamp tmp Windows C Program Files VERITAS NetBackup db images master server timestamp tmp Copy the DR file to the newly created directory 5 Edit the DR file in netbackup db images master_server timestamp tmp as follows m Change the value of IMAGE_TYPE to 1 m Change the value of TIR_INFO to 0 m Change the value of NUM_DR_MEDIAS to 0 m Remove ALL lines containing DR_MEDIA_REC 10 Disaster recovery 231 How to recover a catalog from a backup If your catalog recover media is on tape run the vmquery command to assign the media to the media server vmquery assigntohost media timestamp master server Example vmquery assigntohost DLOO5L 1122000000 klingon To recover the catalog f file from
106. available that describes backup and recovery procedures See the NetBackup Bare Metal Restore System Administrator s Guide 178 Disaster recovery About disk recovery procedures for UNIX and Linux Recovering the master server when root is intact The following procedure recovers the master server by reloading the operating system then restoring NetBackup and finally restoring all other files To recover the master server when root is intact 1 Verify that the operating system works that any require patches are installed and that specific configuration settings are made Take corrective action as needed Reinstall NetBackup software on the server you want to recover See the NetBackup Installation Guide for UNIX for instructions Install any NetBackup patches that had been previously installed See the documentation that was included with the patch software Note CompanyName does not support the recovery of a catalog image that was backed up using an earlier version of NetBackup If any of the default catalog directories have changed that may be reflected in the NetBackup catalog backups recreate those directories before the catalog recovery The following are examples m Use of symbolic links as part of the NetBackup catalog directory structure m Use of the NetBackup nbdb_move command to relocate parts of the NetBackup relational database catalog If the recovery scenario involves restoring policy or catalo
107. backup Part of the online catalog backup configuration indicates where the disaster recovery information file was to be stored and or sent In most cases you specify the most recent disaster recovery information file available If some form of corruption has occurred then you may want to restore to an earlier state of the catalog If the most recent catalog backup was an incremental backup use the disaster recovery file from the incremental backup There is no need to first restore the full backup and then follow with the incremental backup Indicate where the disaster recovery file is stored by entering the fully qualified path to the disaster recovery file More information is available on the email that is sent and the attached disaster recovery file See Recovering the catalog without the disaster recovery file on page 225 204 Disaster recovery How to recover a catalog from a backup The wizard waits while NetBackup searches for the necessary media sources The wizard then informs you if the necessary backup ID of the disaster recovery image is located x Retrieving Disaster Recovery File Wait while file contents are being analyzed N Completed searching for required media sources Actions required Or if the media is not located the wizard lists which media is needed to update the database Follow the wizard instructions to insert the media that is indicated and run an inventory to update the NetBacku
108. base interface 124 bmrcreatefloppy exe m Runs on the BMR boot server m Used by the Bare Metal Restore commands that create floppy disks m Windows only 125 bmrsrtadm m Bare Metal Restore utility m Creates a shared resource tree and bootable CDs and runs on the BMR boot server 126 bmrprep m Bare Metal Restore utility m Prepares the BMR servers for a client restoration 127 bmrsetupmaster and bmrsetupboot Bare Metal Restore installation configuration and upgrade processes 128 Bare Metal Restore libraries get their log messages from this catalog 129 bmrconfig m Bare Metal Restore utility m Modifies a client s configuration 130 bmrpkg and bmrcreatepkg m Bare Metal Restore utilities m They add Windows drivers service packs and hotfixes to the BMR master server so they can be used in a restore 108 Using logs About unified logging Table 3 2 Originator IDs for the server processes that use unified logging continued 131 bmrrst exe and m Windows systems only bmrmap exe m They restore Windows Bare Metal Restore clients m They run on the restoring client 132 nbsl NetBackup Service Layer 134 ndmpagent m NDMP agent daemon m Manages NDMP backup and restore 137 Controls the logging level in the NetBackup libraries The application and diagnostic messages are for customer use debug messages are intended for Symantec en
109. base information from a tape media perspective m To gather and create a package bundle when directed to do so by Symantec technical support The following items can help you run the necc utility 162 Using NetBackup utilities About the NetBackup consistency check utility NBCC For an necc description examples and how to gather NetBackup catalog and database information to send to Symantec technical support refer to the NBcc help command NBCC is designed to be run on NetBackup master servers In some cases a non functioning operating system or NetBackup process or service can prevent necc from running properly or completing As NBCC progresses through the interrogation of various operating system or NetBackup components it outputs what processes to STDOUT As necc processes catalog and database components it displays how many records have been processed The number of records that are processed is in direct relationship to the size of the catalog and database being processed If nscc detects a failure related information is output to STDERR Information to STDOUT or STDERR are also output to the nbcc info txt file if available If NBCC does not perform as expected try the following Use a text editor to look for error notices in the nbcc into txt file By default necc sends error messages to standard error STDERR and also includes the messages in its output files under the header STDERR If nBcc does not produce ad
110. ble 100 Using logs About logs Figure 3 1 Logs in the NetBackup Enterprise system SERVER I CLIENT l eee ne ei Error File Catalog Catalog l l x Status Client Debug NetBackup NetBackup Logs Logs Administration Database Interface Manager l l Master Server Client Programs Server Programs Master or Media Server Media Catalog Server Debug Logs System Logs System Messages Windows Event Log You can review a functional overview that describes the programs and daemons that are mentioned in this figure See About backup and restore functional overview on page 235 You can also use NetBackup reports to help troubleshoot problems NetBackup reports give information about status and errors To run reports use the NetBackup Administration Console See the NetBackup Administrator s Guide Volume I for detailed descriptions of NetBackup reports Using logs 101 About UNIX system logs Note The log entry format in the NetBackup logs is subject to change without notice Note The term media server as distinct from master server or server does not apply to the NetBackup server product When you troubleshoot a NetBackup server installation ignore any references to media server This note does not apply to NetBackup Enterprise Server About UNIX system logs The NetBackup s
111. blems For UNIX clients perform the following steps Before you start this procedure add the vERBOSE option to the usr openv netbackup bp conf file Also create a bpca debug log directory on your server and clients and a bpra log directory on the server During subsequent retries the debug logs provide detailed debug information which can help you analyze the problem 42 Troubleshooting procedures Resolving network communication problems with UNIX clients Table 2 8 Steps for resolving network communication problems with UNIX clients If this configuration is a new or a modified configuration do the following Step 1 Test anew or modified confitguration Check any recent modifications to ensure that they did not introduce the problem Ensure that the client software was installed and that it supports the client operating system Check the client names server names and service entries in your NetBackup configuration as explained in the following topic See Verifying host name and service entries in NetBackup on page 52 You can also use the hostname command on the client to determine the host name that the client sends with requests to the server Check the bprd debug log verbose on the server to determine what occurred when the server received the request Note the required NIS or DNS updates Failure to update these services properly is acommon source of network problems Table 2 8 Troubleshoo
112. bm description 275 bpdbm log 128 bpdm description 275 bpdm log 128 bpdown command 79 80 190 193 bpfis 245 275 bphdb description 275 log 134 BPINETD 249 263 bpinetd log 136 bpinetd log 136 bpjava msve 276 bpjava msvc log 128 148 bpjava usvc log 148 bplist description 276 log 134 137 bplist log 137 bpmount log 134 bpmount log 137 bporaexp log 134 bporaexp64 log 134 bporaimp log 134 bporaimp64 log 134 bpps 23 bprd description 277 bprd log 128 bprestore description 277 log 135 137 bprestore log 137 bpsched see alsonbpem 281 bpsrv log 137 bpsrv log 137 BPSVR NLM 277 bpsynth 252 BPSYS EXE 277 bptm description 278 bptm log 128 bptpcinfo 97 bpup command 80 190 193 bundling NBCC output 163 nbsu output 158 c catalog backup 254 class database file 285 client NetBackup configured name 306 debug logs See UNIX clients See Windows and NetWare clients installation problems 27 multiple hostnames 305 peername 306 software location See UNIX clients testing configuration 33 36 Client Properties dialog 69 client NetBackup Windows disk recovery 194 CommandCentral Storage 93 94 communications problems PC clients 48 UNIX clients 41 compression for NBCC 163 for nbsu 158 config file 285 configuration database 285 configuration problems 27 D daemons robotic 287 robotic control 287 database backup see catalog backup 254 database extension 235 DAYS_TO_KEEP_LOGS vm conf setting 132
113. bpcd bpcd see note 1 etc services NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd etc services NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd Consider the following notes about Figure 2 4 m The following is the complete inetd conf entry bpcd stream tcp nowait root usr openv netbackup bin bpcd bpcd Troubleshooting procedures 63 Verifying host name and service entries in NetBackup m Allother applicable network configuration must also be updated to reflect the NetBackup information For example this information could include the etc hosts file and NIS and DNS if used The policy client list shows the configuration of the router system as mars because that is the name of the interface to the master server Other than the client name setting this setup has no special configuration This name must be set to mars because mars 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 If all the standard networking files hosts NIS DNS WINS and routing tables are set up correctly all the required network connections can be made However to restore files from pluto would be a problem in the following situation the mars meteor system is a type of router that hides the name of the originating host when it routes requests between the two networks Fo
114. bs trylogs jobid t If the job ID of the synthetic backup job was 110 the try file is named 110 8 Policy attributes Use the following command to capture the policy attributes install _path netbackup bin admincmd bppllist policy name L where policy _nameis the name of the policy for which the synthetic backup job was run List of storage Capture the list of storage units from the following command units install_path netbackup bin admincmd bpstulist L 142 Using logs Setting retention limits for logs on clients See Creating legacy log directories to accompany problem reports for synthetic backup on page 125 Setting retention limits for logs on clients You can specify the numbers of days that NetBackup retains client logs on UNIX Windows and NetWare To set retention limits for logs on UNIX clients 1 5 In the NetBackup Administration Console in the left pane expand Host Properties gt Clients In the right pane double click the client you want to modify In the properties dialog box click UNIX Client In the Client Settings dialog box find the Keep status of user directed backups archives and restores for field Enter the number of days you want to retain the log files and click OK To set the retention limits for logs on Windows clients 1 5 In the NetBackup Adminsistration Console on the File menu click Backup Archive and Restore In the Backup Archive and Restore interf
115. by the scheduling services See Backup and archive processes on page 236 289 290 Media and device management functional description Media and device management process The resulting request to mount a device is passed from nbjm to nbrb which acquires the physical resources from nbemm the Enterprise Media Manager service If the backup requires media in a robot ltid 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 mounts the media and sets a drive busy status in memory shared by itself and ltid Drive busy status also appears in the Device Monitor See Figure B 2 on page 291 Assuming that the media is physically in the robot the media is mounted and the operation proceeds If the media is not in the robot nbrb creates a pending request which appears as a pending request in the Device Monitor An operator must then insert the media in the robot and use the appropriate Device Monitor command to resubmit the request so the mount request can occur 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 More informatio
116. cation bptm also does the actual write to the tape When the backup is complete nbjm tells nbrb to release resources nbrb de allocates the drive in EMM EMM tells the scan host to resume scanning the drive The scan request is carried out by means of oprd Itid and avrd in the media server s shared memory Figure B 3 illustrates the shared storage option management process Media and device management functional description 293 Barcode operations Figure B 3 Media and device management process flow showing SSO components User Device monitor EMM Device management utility Backup and Database archive processes nbemm DA Request tape mount 6 5 Media Server 1 6 5 Media Server 2 Scan host for drive A Scan host for drive B Shared drive A Shared drive B Note Shaded area represents shared memory on the media server Barcode operations Barcode reading is mainly a function of the robot hardware rather than media and device management When a robot has a barcode reader it scans any barcode 294 Media and device management functional description Barcode operations 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 NetBackup determines that association for its own use by interrogating the robot If arobot supports barcodes NetBackup automatically compares a tape s barcode to w
117. cation server of the NetBackup Administration Console This application server is made up of an authentication service and a user service The logon request from the logon dialog box is sent to the authentication service for validation The user name and password have to be valid in the Windows UNIX authentication files and process After validation the authentication service starts a user service under the user s account Thereafter all NetBackup administrative tasks are performed through an instance of the user service Additional user service processes are initiated to process requests from the console On both UNIX and Windows the authentication service is the bpjava msvc application The user service is the bpj ava susvc OF bpjava usvec application To enable detailed debug logging you must first create logging directories for these applications 148 Using logs Troubleshooting error messages in the NetBackup Administration Console for UNIX Table 3 18 Enabling detailed debug logging Step 1 Create logging directories On the NetBackup client or server that is specified in the logon dialog box create the following directories E bpjava msvc E bpjava susve if a NetBackup server E bpjava usve if a NetBackup client Create the directories in the following locations E usr openv netbackup logs UNIX E install_path NetBackup logs Windows See About unified logging on page 102 See About legacy logging on page
118. ccceeeueeeeeneeeeeueees 27 Device configuration problem resolution cccceceeeeeceeeeeeeeenes 29 Testing the master server and clients ccccceceececeeceeeeeeeeeaeees 32 Testing the media server and clients scceceeceeeeceeeeeeeeeeeeeeees 36 Resolving network communication problems with UNIX clients 41 Resolving network communication problems with PC clients 48 Verifying host name and service entries in NetBackup 065 52 Example of host name and service entries on UNIX master server and CHEN cccwsracassestceacseesaceans E Na ENA 57 Example of host name and service entries on UNIX master server and medid Server iessirsinnnsn enie naaa o ninae 59 Example of host name and service entries on UNIX PC Clients nue nanasiener a state E E EEEE 60 Example of host name and service entries on UNIX clients in multiple networks ccc cece cece eee c ec eeeeeeeeeeeneneneneneneneas 62 Example of host name and service entries on UNIX server that connects to multiple networks cccccccececeeeeeeeeeeeenens 64 About the bpclntcmd utility 2 0 0 0 cece cece ec eee ee eee eeeee sense eeeenes 66 Using the Host Properties window to access configuration SENOS ncesuc vet dvarglen scandal desluavadesseinelndbidawaieadwaeadineasdevaicenwtesouts 69 Resolving full disk problems ccceccecceeeeeceeceeeeeeeeeeeeeeeeeeeees 69 8 Contents
119. chines and Policy Type on the File menu Install any NetBackup patches that had previously been installed 196 Disaster recovery About clustered NBU server recovery for Windows 10 11 Enable debug logging by creating the following debug log directories on the client install _path NetBackup Logs tar install _path NetBackup Logs bpinetd NetBackup creates logs in these directories Stop and restart the NetBackup Client service This action enables NetBackup to start logging to the bpineta debug log Use the NetBackup Backup Archive and Restore interface to restore the system files 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 need to be the administrator but you must have restore privileges For instructions refer to the online Help or refer to the following See the NetBackup Backup Archive and Restore Getting Started Guide NetBackup restores the registry when it restores the Windows system files For example if the system files are in the c winnt directory NetBackup restores the registry when it restores that directory and its subordinate subdirectories and files Check for ERR or WRN messages in the log files that are in the directories you created in step 6 If the logs indicate problems with the restore of Windows system files resolve those problems before proceeding Stop the NetBackup
120. ckup server The Jobs database is on the master server media Media related information that is used by bptm Also has an errors file that contains error history information for media and devices 286 Backup and restore functional overview NetBackup catalogs Appendix Media and device management functional description This appendix includes the following topics m Media and device management startup process m Media and device management process m Shared Storage option management process m Barcode operations m Media and device management components Media and device management startup process Media and device management processes are automatically initiated during NetBackup startup To start these processes manually run bp start_all UNIX or bpup Windows Itid automatically starts other daemons and programs as necessary The daemons should be running after initial startup See Figure B 1 on page 289 In the case of robotic daemons such as tl8d and tlhd the associated robot must also be configured for the daemon to run There are also additional ways to start and stop daemons See Table B 1 on page 296 TL8 TLH and TLD require following types of daemons 288 Media and device management functional description Media and device management startup process robotic Each host with a robotic drive attached must have a robotic daemon These daemons provide the interface between Itid and the robot or
121. clients and destination clients to your server starting with the master server Restore all files that are backed up by the hot catalog backup on each server 14 Stop and restart the NetBackup services Restoring files from an online catalog backup Because the online catalog backup uses the standard backup format you may recover specific files using the NetBackup Backup Archive and Restore user interface Restoring catalog files directly to their original location may cause inconsistencies in the NetBackup catalog or cause NetBackup to fail Instead you should restore catalog files to an alternate location Disaster recovery 233 How to recover a catalog from a backup To restore files from an online catalog backup 1 2 3 From the Specify NetBackup Machines and Policy Type menu select the NBU Catalog policy type Specify the master server as the source client for the restore Select the catalog files to restore Unfreezing the online catalog recovery media This procedure shows how to unfreeze your online catalog recovery media To unfreeze the online catalog recovery media 1 On the master server go to the image database In the master server s portion of the image catalog locate the catalog backup image file from which the recovery was done m Identify the associated catalog backup parent image file by viewing the PARENT_IMAGE_ID value m Identify the media that the catalog backup was written to by viewin
122. command For example ifconfig e0 mediatype 100tx fd 4 For most hosts you can set full duplex mode permanently such as in the host s etc rc files Refer to the host s documentation for more information About SERVER entries in the bp conf file On Solaris and Linux systems every SERVER entry in a client bp conf file must be a NetBackup master or media server That is each system that is listed as a SERVER must have either NetBackup master or media server software installed The client service on some clients cannot be started if the client name is incorrectly listed as a server If abp conf SERVER entry specifies a NetBackup client only computer SAN client backups or restores over Fibre Channel may fail to start In this case determine if the nbftclnt process is running on the client If it is not running check the nbftclnt unified logging file OID 200 for errors You may see the following in the nbftcint log The license is expired or this is not a NBU server Please check your configuration Note unless NBU server the host name can t be listed as server in NBU configuration Remove or correct the SERVER entry in the bp conf file restart nbftcint on the client and retry the operation Note The nbftclnt process on the client must be running before you start a SAN client backup or restore over Fibre Channel About unavailable storage unit problems NetBackup jobs sometimes fail because storage units are unav
123. commands vxlogcfg Modifies the unified logging configuration settings See Examples of using vxlogmgr to manage unified logs on page 120 vxlogmgr Manages the log files that are generated by the products that support unified logging See Examples of using vxlogcfg to configure unified logs on page 121 vxlogview Displays the logs that unified logging generates See Examples of using vxlogview to view unified logs on page 118 The commands vxlogcfg vxlogmgr vxlogvieware located in the following directory UNIX Windows Using logs 103 About unified logging usr openv netbackup bin install _path NetBackup bin Refer to the NetBackup Commands Reference Guide for a complete description of these commands Gathering unified logs for NetBackup This topic uses an example to describe how to gather unified logs for NetBackup To gather unified logs for NetBackup 1 Create a directory named up1load by using the following command mkdir upload 2 Copy unified logs for NetBackup only to the upload directory by using the following command vxlogmgr p NB c dir upload Example output Following are the files that were found u u u u u u To Co u Co u Co u Co u Co u Co u sr openv sr openv sr openv sr openv sr openv sr openv tal 6 file s pying sr openv 1 pying sr openv 1 pying sr openv 1 pying sr openv 1 pying sr openv 1
124. configuration For example you can check whether a particular device is connected as well as the zoning and masking on the SAN Sometimes a switch or a Windows box is interrupted and sends out a reset command Since NetBackup doesn t automatically maintain persistent bindings the reset command can cause drives to be mapped differently CommandCentral Storage can help find the problem by showing the changes in the drive mappings although it cannot automatically fix the problem For information on how to implement persistent bindings refer to the NetBackup Device Configuration Guide NetBackup lets you launch CommandCentral Storage in context The CommandCentral Storage Web GUI precisely displays the area of the SAN configuration you plan to troubleshoot 94 Troubleshooting procedures About troubleshooting NetBackup in a SAN environment NetBackup enterprise lifecycle best practices SAN related problems generally involve the use of Shared Storage Option SSO The two types of NetBackup users generally are as follows m Operators who have limited access to hosts and to the fabric of the SAN m System administrators who have administrator privileges but no access to the fabric The SAN administrator generally operates outside the NetBackup domain entirely Troubleshooting NetBackup is difficult when it involves the SAN because administrative responsibility tends to be spread out No one person has a clear picture of the overall back
125. ct from master server or server does not apply to the NetBackup server product When you troubleshoot a NetBackup server installation ignore any references to media server This note does not apply to NetBackup Enterprise Server Troubleshooting NetBackup problems If you have problems with NetBackup perform these actions first This preliminary NetBackup troubleshooting procedure explains what to check first and branches to other procedures as appropriate These procedures do not try to cover every problem that can occur However they do recommend the methods that usually result in successful problem resolution Troubleshooting procedures 21 Troubleshooting NetBackup problems When you perform these procedures try each step in sequence If you already performed the action or it does not apply skip to the next step If you branch to another topic use the solutions that are suggested there If you still have a problem go to the next step in the procedure Also alter your approach according to your configuration and what you have already tried Table 2 1 Steps for troubleshooting NetBackup problems Step 1 Verify operating systems and peripherals Ensure that your servers and clients are running supported operating system versions and that any peripherals you use are supported Refer to the NetBackup release notes and the NetBackup compatibility lists on the following Web site http www symantec com docs TECH599
126. cts standard output into the designated file m To generate the debug messages that relate to nbsu enter the following nbsu debug The messages are written to the nbsu_info txt file The nbsu_info txt file provides an overview of the environment where nbsu is run It contains the following m General operating system and NetBackup information on the environment that nbsu detects m A list of diagnostics that were run m A list of diagnostics that returned a non zero status The information in nbsu_info txt may indicate why nbsu returned particular values or why it did not run certain commands If nbsu does not produce adequate information or if it seems to perform incorrectly run nbsu with the debug option This option includes additional debug messages in the nbsu_info txt file More information on the nbsu command options is available See the NetBackup Commands Reference Guide Using NetBackup utilities 157 About the NetBackup support utility nbsu Output from the NetBackup support utility nbsu The NetBackup support utility nbsu writes the information it gathers to text files in the following directory UNIX usr openv netbackup bin support output nbsu hostname_timestamp Windows install _path NetBackup bin support output nbsu hostname_timestamp The NetBackup environment where nbsu runs determines the particular files that nbsu Creates nbsu runs only those diagnostic commands that are appropriate to the
127. cturers do not support serial numbers Although automatic device configuration does not function optimally the robot and drives can be manually configured and operated without serial numbers available Or manually configure and operate the robot and drives without serial numbers No license for this robot type NetBackup server does not support the robotic type that is defined for this robot Define a different robot Use only the robotic libraries that NetBackup server supports No license for this drive type The drive type that is defined for this drive that the NetBackup server does not support Define a different drive Use only the drives that NetBackup supports Unable to determine robot type NetBackup does not recognize the robotic library The robotic library cannot be auto configured Do the following m Download anew device_mapping file from the Symantec support Web site and try again m Configure the robotic library manually m Use only the robotic libraries that NetBackup supports Drive is stand alone or in unknown robot Either the drive is stand alone or the drive or robot does not return a serial number Note that some manufacturers do not support serial numbers Although automatic device configuration does not function optimally the drive or robot can be manually configured and operated without a serial number Ask the manufacturer for a newer firmware version that re
128. d By Starting ltid or on UNIX independently by using the usr openv volmgr bin tl8cd command Stopped By Stopping Itid or by using the tl8cd t command Debug Log Errors are logged in the system log and robots debug log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option either by itself or through Itid tldd The Tape Library DLT daemon works in conjunction with tldcd to handle requests to TLD robots Tape Library DLT and Tape Stacker DLT tldd provides the interface between the local Itid and the robotic control tldcd in the same manner as explained previously for tl8d Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin tldd command Stopped By Stopping ltid or on UNIX independently by finding the PID process id and then using the kill command Debug Log Errors are logged in the system log and robots debug log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option either by itself or through Itid Media and device management functional description 301 Media and device management components Table B 2 Media and device management daemons and programs continued tldcd The Tape Library DLT Control daemon provides robotic control for a TLD robot in the same manner as e
129. d archives UNIX clients m When the job finishes re computes the due time of the next job and submits to nbjm all jobs that are currently due The job manager service nbjm requests backup resources from the resource broker nbrb nbrb returns information on the use of shared memory for SAN Client nbjm starts the backup by means of the client daemon bpcd which starts the backup and restore manager bpbrm bpbrm starts bptm bptm does the following m Requests SAN Client information from nbjm m Sends a backup request to the FT server process nbftsrvr m Sends a backup request to the FT Client process on the client nbftclnt nbftclnt opens a fibre channel connection to nbftsrvr on the media server allocates shared memory and writes shared memory information to the backup ID file bpbrm starts bpbkar by means of bpcd bpbkar does the following m Reads the shared memory information from the BID file waits for the file to exist and become valid m Sends the information about files in the image to bpbrm m Writes the file data to tar optionally compresses it and writes the data to the shared buffer m When the buffer is full or the job is done sets buffer flag The FT Client process nbftclnt waits for the shared memory buffer flag to be set nbftclnt then transfers the image data to the FT Server nbftsrvr shared memory buffer and clears the buffer flag nbftsrvr waits for data from nbftclnt the data is written t
130. d logging Unified logging and legacy logging are the two forms of debug logging used in NetBackup Unified logging creates log filenames and messages in a standardized format All NetBackup processes use either unified logging or legacy logging Unlike the files that are written in legacy logging unified logging files cannot be viewed with a text editor The unified logging files are in binary format and some of the information is contained in an associated resource file See About legacy logging on page 124 Server processes and client processes use unified logging See Server processes that use unified logging on page 106 See UNIX client processes that use unified logging on page 111 See PC client processes that use unified logging on page 112 Unlike legacy logging unified logging does not require that you create logging subdirectories Log files for originator IDs are written to a subdirectory with the name specified in the log configuration file All unified logs are written to subdirectories in the following directory UNIX usr openv logs Windows install_path NetBackup logs You can access logging controls in the NetBackup Administration Console In the left pane expand NetBackup Management gt Host Properties gt Master Servers or Media Servers Double click the server you want to change In the left pane of the dialog box click Logging You can also manage unified logging by using the following
131. de NetBackup servers with identical names to those servers where the backups were made If not the automated recovery may not succeed Configure the online catalog backup policy to email a copy of the disaster recovery information to a NetBackup administrator in your organization Configure this policy as part of every catalog backup Do not save the disaster recovery information emails to the local computer Catalog recovery without the disaster recovery image file or the disaster recovery information email available is exceedingly complex time consuming and requires assistance You may tailor the disaster recovery email process by providing a customized mail script More details are available See Reference Topics of the NetBackup Administrator s Guide Volume II Ensure that you identify and use the appropriate catalog backup for your recovery For example if you recover from your most recent backups use the catalog from your most recent backups Similarly if you recover from a specific point in time use the catalog backup from that specific point in time System environment catalog size location and backup configuration full and incremental policy schedules all help determine the time that is required to recover the catalog Carefully plan and test to determine the catalog backup methods that result in the desired catalog recovery time The NetBackup catalog backup protects your configuration data and catalog data Set up backu
132. der the following directory UNIX usr openv netbackup logs Windows install_path NetBackup logs Table 3 13 Directory names for legacy debug logs admin Administrative commands bpbrm NetBackup backup and restore manager bpced NetBackup client daemon or manager The NetBackup Client service starts this process bpdb jobs NetBackup jobs database manager program 128 Using logs About legacy logging Table 3 13 Directory names for legacy debug logs continued bpdm NetBackup disk manager bpdbm NetBackup database manager This process runs only on master servers On Windows systems it is the NetBackup database manager service bpjava msvc The NetBackup Java application server authentication service that is started when the NetBackup Java interface applications start On UNIX servers inetd starts it On Windows servers the Client Services service starts it This program authenticates the user that started the application bpjava susvc The NetBackup program that bpjava msvc starts upon successful logon through the logon dialog box that is presented when a NetBackup Java interface starts This program services all requests from the Java user interfaces on the NetBackup master or media server host where the bpjava msvc program is running all Windows platforms bprd NetBackup request daemon or manager On Windows systems this process is called the NetBackup Request Manager service bpsynth The NetBac
133. dia ID and places them in the specified directory The ID can be either a tape media ID or the fully qualified location of a disk storage unit 226 Disaster recovery How to recover a catalog from a backup 4 Verify that the correct disaster recovery file is available in the specified directory and that it is available from the NetBackup master server Disaster recovery 227 How to recover a catalog from a backup Continue with the normal catalog recovery procedure by running the Catalog Recovery Wizard or bprecover command providing the disaster recovery file location when prompted Refer to the email as your primary source for recovery instructions because they are the most current instructions for recovering your catalog The instructions are sent when the catalog backup is completed or when a catalog backup image is duplicated Note If you restore catalog files directly by using bprestore on a Solaris system use the following path opt openv netbackup bin bprestore The name of the online catalog backup policy is CatalogBackup The email is written to the following file storage DR CatalogBackup_1123605764 FULL The file name itself indicates if the backup was full or not The following is an example of a disaster recovery email Server ant Date Tue Aug 10 11 41 48 2010 Policy CatalogBackup Catalog Backup Status the requested operation was successfully completed status 0 To ensure
134. dows ceccececceceeeeceee sense sense sees eeeeneneenes 312 Pla Cares T verclea ncclesiauie unl OE suite a vluctn eluate A NE O E E Moaleee be euleiageuee 315 11 12 Contents Chapter Introduction This chapter includes the following topics m Troubleshooting a problem m Problem report for Technical Support m About gathering information for NetBackup Java applications Troubleshooting a problem The following steps offer general guidelines to help you resolve any problems you may encounter while you use NetBackup The steps provide links to more specific troubleshooting information Table 1 1 Steps for troubleshooting NetBackup problems Step 1 Remember the error message Error messages are usually the vehicle for telling you something went wrong 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 These can provide an error message that points you directly to a solution The logs also show you what went right and the NetBackup operation that was ongoing when the problem occurred For example a restore operation needs media to be mounted but the required media is currently in use for another backup Logs and reports are essential troubleshooting tools See About logs on page 99 14 Introduction Troubleshooting a problem Table 1 1 Steps for troubleshooting NetBac
135. dows clients BPCDW32 EXE 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 you can stop it through the Services application in the Control Panel Debug Log BPCD legacy log directory on the client bpdbjobs On UNIX master servers this program is used to clean up the NetBackup jobs database Started By usr openv netbackup bin admincmd bpdbj obs When bprd starts it runs this command automatically The administrator can also execute it manually or with a cron job Stopped By No terminate option exists for this command outside of using kill Debug Log bpdbj obs legacy log directory on the server Table A 4 Backup and restore functional overview NetBackup programs and daemons NetBackup daemons and programs continued bpdbm 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 legacy log directory on the server bpdm On master and media servers bpdm is used for the following disk operations read phase of disk duplication read phase of synthetic backups disk
136. duct ID Identifies the product The NetBackup product ID is 51216 The product ID is also known as the entity ID 116 Originator Identifies the log writing entity such as a process service script or other software The number 116 is the originator ID of the nbpem process the NetBackup policy execution manager 2201360136 Host ID Identifies the host that created the log file Unless the file was moved this ID is the host where the log resides 041029 Shows the date when the log was written in YYMMDD format 0000000000 Rotation Identifies the numbered instance of a log file for a given originator The rollover number rotation indicates the instance of this log file By default log files roll over rotate based on file size If the file reaches maximum size and a new log file is created for this originator the new file is designated 0000000001 See About rolling over unified log files on page 113 106 Using logs About unified logging Server processes that use unified logging Many server processes use unified logging The originator IDs correspond to NetBackup processes More than one process may use an originator ID UNIX clients and Windows clients also include the processes that use unified logging See UNIX client processes that use unified logging on page 111 See PC client processes that use unified logging on page 112 The log configuration file specifies the name of the directories
137. duct ID 105 processes using 106 retention 113 setting level on PC clients 140 settings levels 138 submitting to Technical Support 103 tar log files 104 upload directory 104 user directed backups 238 user_ops log 128 135 138 utility robotic test 311 322 Index V VERBOSE 130 131 verbose flag 130 VERBOSE level 139 vm conf 130 131 vm conf file 297 vmadm overview 304 vmd 129 debug logging 129 overview 303 vmscd 125 logging 129 vmscd overview 304 vnetd log 128 Volume Configuration Wizard 189 vxlogcfg 112 133 vxlogcfg command 121 123 139 vxlogmgr command 120 123 vxlogview command 115 query string overview 115 with job ID option 120 vxpbx_exchanged 79 W Windows open file backup 244 windrvr6 284 xX xinetd 27 XML 134 xml for nbsu 159
138. e About unified logging on page 102 282 Backup and restore functional overview NetBackup programs and daemons Table A 4 Backup daemons and programs continued nbstserv Runs on the master server The nbstserv service manages lifecycle operations including duplication staging and image expiration Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbstserv terminate Debug Log On the server usr openv 1ogs UNIX or install path logs Windows For more information about OID 226 and 272 see the following topic See Server processes that use unified logging on page 106 NBWIN EXE For Windows clients NBWIN EXE 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 NBWIN legacy log directory on the client nbrmms Remote Manager and Monitor Service nbrmms is the conduit through which EMM discovers and configures storage on media servers In addition to configuration management nbrmms provides all access to media server resources for monitoring and event notifications Started By Started when NetBackup starts or by usr openv netbackup bin nbrmms Stopped By Stopped when NetBackup stops or by usr openv netbackup bin nbrmms terminate Debug Log On the server usr openv logs UNIX or install_pat
139. e Examples of using vxlogmgr to manage unified logs on page 120 If the vxlogcfg LogRecycle option is ON true the Keep logs setting is disabled for unified logs In this case unified logging files are deleted when their number for a particular originator exceeds the number that the NumberOfLogFiles option specifies on the vxlogcfg command About rolling over unified log files To prevent log files from becoming too large or to control when or how often logs are created you can set a log rollover option When a file size or time setting is 114 Using logs About unified logging reached the current log file is closed New log messages for the logging process are written or rolled over to a new log file You can set log file rollover to occur based on file size time of day or elapsed time Set the conditions by using the vxlogcfg command with the options described in Table 3 5 Table 3 5 Options of the vxlogcfg command that control the rollover of unified log files MaxLogFileSizeKB Specifies the maximum size that is allowed for the log file in kilobytes before rollover occurs if the RolloverMode is set to FileSize RolloverAtLocalTime Specifies the time of day at which the log file is rolled over if the Rol loverMode is set to LocalTime RolloverPeriodInSeconds Specifies a period of time in seconds after which the log file is rolled over if the RolloverMode is set to Periodic MaxLogFileSizeKB
140. e and install_dbext script help Help files that are used by NetBackup programs These files are in ASCII format Backup and restore functional overview 271 NetBackup programs and daemons Table A 3 Directories and files in Usr openv netbackup servers and UNIX clients continued logs Legacy debug logs for NetBackup processes You must create the necessary subdirectories in order for these log files to be written See About legacy logging on page 124 See Table A 4 on page 272 for an explanation of the processes that produce the logs nblog conf Specifies the settings for unified logging Note Do not edit this file manually use the vxlogcfg command instead See About unified logging on page 102 nblog conf template Specifies the settings for unified logging Note Do not edit this file manually use the vxlogcfg command instead See About unified logging on page 102 nbsvcmon conf Configuration file for the NetBackup Service Monitor It tells the Service Monitor what services to monitor and how to restart them if they fail unexpectedly remote_versions Acache of the versions of other media servers in the system version Version and release date of the software version master Identifies the NetBackup master server NetBackup programs and daemons Table A 4 describes the programs and daemons that provide most of the control for bac
141. e drive SCSI adapter pass through information is available See the NetBackup Device Configuration Guide No configuration device file exists A device has been detected without the corresponding device file necessary to configure that device Refer to NetBackup Device Configuration Guide for information on how to create device files Unable to determine drive type The NetBackup server does not recognize the drive The drive cannot be auto configured Do the following Download a new device_mapping file from the Symantec support Web site and try again Configure the drive manually Use only the drives that NetBackup supports 32 Troubleshooting procedures Testing the master server and clients Table 2 5 continued Recommended actions for device configuration messages Unable to determine compression device A drive was detected without the expected compression device file that is used to configure that device Automatic device configuration tries 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 If you do not need hardware data compression no action is necessary The drive can be operated without hardware data compression Hardware data compression and tape drive configuration hel
142. e if any directory paths or locations need to be created for NetBackup catalog recovery 4 If necessary partition any disks being recovered as they were before the failure Then reformat each partition as it was before the failure 5 Reinstall NetBackup software on the server being recovered Do not configure any NetBackup policies or devices at this time 6 Install any NetBackup patches that had been previously installed See the documentation that was included with the patch software 7 Ifthe catalog directories differ from those in the NetBackup catalog backups recreate that directory structure on disk before you recover the catalog For example use the NetBackup nbdb_move command to relocate parts of the NetBackup relational database catalog 8 Ifthe recovery scenario involves restoring policy or catalog backups the appropriate recovery device or devices have to be configured You may have to do all or some of the following tasks 192 Disaster recovery About disk recovery procedures for Windows 10 Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored If anon robotic drive is available that can read these backups then no robot is required Although manual intervention is required if multiple pieces of media are required See the NetBackup Device Configuration Guide Use the NetBackup Device Configuration Wizard to discover a
143. e in the list If you add or modify SERVER entries on the master server stop and restart bprd and bpdbm before the changes take effect The bp conf of the master server does not require the addition of other clients other than the master server as CLIENT_NAME master server name The name is added by default The bp conf file is in the usr openv netbackup directory on UNIX clients and it is in the Preferences NetBackup folder on Macintosh clients Users on UNIX clients can also have a personal bp conf file in their home directory A CLIENT NAME option in SHOME bp conf overrides the option in usr openv netbackup bp conf Check the SYS VERITAS NBUCLT NetBack BP INT file to ensure the following m A SERVER entry exists 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 Troubleshooting procedures 55 Verifying host name and service entries in NetBackup On the master server Verify that you have created any of the following required files E usr openv netbackup db altnames files UNIX E install _path NetBackup db altnames files Windows Pay particular attention to requirements for host xlate file entries Verify that each server and client have the required entries for NetBackup reserved port numbers The
144. e 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 Media and device management functional description 295 Media and device management components Figure B 4 Barcode request ice User Device 7 NetBackup management utility EMM Database Request media ID mount Media management utility Robot inventory request or inject eject Mount media ID Whatis Barcode Mount tape Tape library TL8 Media and device management components This topic shows the file and directory structure and the programs and daemons assoicated with the media and device management Figure B 5 shows the file and directory structure for media and device management ona UNIX server A Windows NetBackup server has equivalent files and directories that are located in the directory where NetBackup is installed by default C Program Files VERITAS 296 Media and device management functional description Media and device management components driver NetBackup server usr openv volmgr bin usr openv volmgr debug format goodies avrd 2 daemon Itid 4 reqlib 1 robots 2 tpcommand vmscd 1 Created by administrator to enable legacy debug logging 2 Created by administrator or automatically by media management utilities Figure B 5 Media and device management directories and files usr ope
145. e master server Enable debug logging for bpbrm and bptm or bpdm on the media server and tar on the client For best results set the verbose logging level to 5 Enable debug logging for bpdbm on the master server and for bpcd on all servers and clients See restoretrace in the Commands Reference Guide Using NetBackup utilities 153 About the analysis utilities for NetBackup debug logs Table 4 2 Analysis utilities for NetBackup debug logs continued verifytrace Consolidates the debug log messages for the specified verify jobs and writes them to standard output It sorts the messages by time verifytrace attempts to compensate for time zone changes and clock drift between remote servers and clients At a minimum you must enable debug logging as follows for admin on the master server and for bpbrm bptm or bpdm and tar on the media server For best results set the verbose logging level to 5 and enable debug logging for the following bpdbm on the master server and bpcd on all servers and clients in addition to the processes already identified See verifytrace in the Commands Reference Guide The analysis utilities have the following limitations m Media and device management logs are not analyzed m The legacy debug log files must be in standard locations on the servers and clients UNIX usr openv netbackup logs lt PROGRAM NAME gt 1log mmddyy Windows install_path NetBackup Logs lt PROGRAM NAME gt mmddyy log
146. e pool m Insert the volume in the drive If you do not pre label the volume by using the bplabel command NetBackup automatically assigns a previously unused media ID Step 3 Verify the daemons and services Verify that all NetBackup daemons or services are running on the master server Also verify that all Media and Device Management daemons or services are running on the media server To perform this check do one of the following m Ona UNIX system run usr openv netbackup bin bpps a m Ona Windows system use the Services application in the Windows Control Panel 38 Troubleshooting procedures Testing the media server and clients Table 2 7 Steps for testing the media server and clients continued Step 4 Backup and restore a_ Perform a user backup and then a restore of file a file from a client that has been verified to work with the master server This test verifies the following m NetBackup media server software m NetBackup on the media server can mount the media and use the drive that you configured m Communications between the master server processes nbpem nbjm nbrb EMM server process nbemm and media server processes bpcd and bpbrm m Communications between media server process bpbrm and client processes bpcd and bpbkar For the failures that relate to drives or media ensure that the drive is in an UP state and that the hardware functions Step 5 Verify communication If y
147. e the NetBackup database Recovering the user directed online catalog from the CLI This procedure recovers the catalog manually through the command line interface CLI without a Phase 1 import when the disaster recovery DR file is available You must have root administrative privileges to perform this procedure Note Use this procedure only if you want to restore the minimal NetBackup catalog information that lets you begin to recover critical data To recover the user directed online catalog from the command line interface 1 Verify the location of the disaster recovery files that are created from Full and Incremental Hot Catalog backups These files can be stored in a specified path of the file system on the master server and in email attachments to the NetBackup administrator Set up each master server and media server in the same configuration as the configuration that is used during the last catalog backup The master server and media servers have the following same properties as the backed up catalog configuration name NetBackup version operating system patch level and path to storage devices Configure any devices and volumes you may need for the recovery 0 Run the BAR user interface to restore remaining image database Configure the devices if any device has changed since the last 230 Disaster recovery How to recover a catalog from a backup 3 Locate the latest DR image file corresponding to the backup th
148. ecking 52 SharedDisk 177 187 slow performance and NIC cards 91 snapshot backup process overview 244 software version determining UNIX client server 271 starting NetBackup processes 80 startup NetBackup 236 status codes and nbsu 159 Status Collection Daemon 125 stderr 145 stdout 145 stopping NetBackup processes 79 80 storage units 92 SuSE 27 synthetic backup 251 logs 141 syslogd 101 system logs 101 T tar log 137 log files 104 NetBackup 283 284 TAR32 263 test utility robotic 311 tl4d description 299 tl4test 312 313 tl8cd description 300 tl8d description 299 tl8test 312 313 tldcd description 301 tldd description 300 tldtest 312 313 tlhcd description 302 tlhd description 301 tlhtest 313 Index 321 tlmd description 302 tpautoconf 129 180 tpconfig 129 tpconfig overview 303 traceroute 308 troubleshooting procedure communication problems PC clients 48 UNIX clients 41 general master server and clients 33 37 media server and clients 36 host name and services entries 52 installation 26 preliminary 21 try file 141 tshd overview 303 tshtest 312 U unavailable 92 unified logging 102 changing location of 112 client logs 133 configuring settings 121 controlling disk space usage 124 controlling number of log files 123 controlling size of 122 deleting logs 121 file name format 105 file rotation 114 format of files 115 listing settings 123 location 102 message types 104 NetBackup pro
149. ed data Select the desired files from the Backup Archive and Restore client interface and restore them 232 Disaster recovery How to recover a catalog from a backup 11 To recover the NetBackup relational database run the following bprecover r nbdb This command restores NetBackup media usage information ensure that media containing backups are not overwritten and restore the storage unit configuration You cannot recover the NetBackup relational database to a configuration that is not identical to the configuration on which the catalog was backed up Instead you must import each piece of backup media 12 If your catalog recovery media is on tape freeze the media that contains the catalog backup that is used for recovery This action protects the media from being reused bpmedia freeze m media h master server Run bpmedialist to verify that the media is frozen 13 Recover your policies and configuration data on each master server and media server Before recovering NetBackup policy files ensure that you have recovered all of your critical data or protected the media that contains your critical data When policy information is recovered NetBackup starts to run the scheduled jobs that may overwrite the media that was written after the last catalog backup Open the Backup Archive and Restore client interface for NetBackup and select NBU Catalog as the policy type For each server to be restored set the source
150. eeeeeees 187 About recovering the master server disk for Windows 187 About recovering the NetBackup media server disk for WIN OWS ve si ii e E ecousap dee adans T ENE e ERA 194 Recovering a Windows client disk 00 ccceceececeeceeeeeeeeenees 194 About clustered NBU server recovery for Windows 0 0eee0e 196 Replacing a failed node on a Windows VCS cluster 00608 197 Recovering the shared disk on a Windows VCS cluster 198 Recovering the entire Windows VCS cluster cceceeeeee ee 199 How to recover a catalog from a backup ccceccecceeceeeee eee eenees 199 When recovering the entire catalog from an online backup 200 About recovering the catalog image file ccecceceece scence 209 Recovering relational database files from an online catalog 19 Ved a r AA R A E a TTE E RE EON 219 Recovering the NetBackup catalog when NetBackup Access Control is configured ccccceccecceeceeceeceeee eee eee een eeneenes 223 Recovering the catalog from a nonprimary copy of a catalog Dack wp cps fo esas vals eiadea relate especie rise ene he aoe 224 Recovering the catalog without the disaster recovery file 225 Recovering the user directed online catalog from the CLI 229 Restoring files from an online catalog backup 0cceeeeees 232 Unfreezing the online catalog recovery medi
151. ement directories and files See NetBackup directory structure UNIX on page 268 270 Backup and restore functional overview NetBackup directories and files Contents of usr openv netbackup Table A 3 describes the usr openv netbackup files and directories Table A 3 Directories and files in Usr openv netbackup servers and UNIX clients bin Commands scripts programs daemons and files that are required for NetBackup operation and administration On a server there are two subdirectories under bin admincmd Contains various commands that 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 bp conf Configuration file containing options for NetBackup operation A detailed explanation is available about each option and how to set it See the NetBackup Administrator s Guide Vol II On a Windows server these options are set in the NetBackup Administration Console client NetBackup client software that is installed on the clients during installation Do not install this directory on a media server db NetBackup catalogs See Table A 5 on page 285 dbext For NetBackup database agent software contains the version file compressed tar fil
152. en no robot is required Although manual intervention is required if multiple pieces of media are required See the NetBackup Device Configuration Guide m Use the NetBackup Device Configuration Wizard to discover and configure the recovery device in NetBackup See the NetBackup Administrator s Guide Volume I m Use the NetBackup command tpautoconf to discover and configure the recovery device in NetBackup See the NetBackup Commands Reference Guide manual m Update the device mapping files See the NetBackup Administrator s Guide Volume I If the recovery scenario involves restoring the policy backups or catalog backups that were done to media the appropriate recovery device s must be configured Configuring the media may involve the following actions m Manually load the required media into a stand alone recovery device m Use NetBackup utilities such as robtest or vendor specific robotic control software to load media into the required recovery devices m Use the NetBackup Volume Configuration Wizard to inventory the media contents of a robotic device m Use the vendor specific robotic control software to load the media into the required recovery device s Recover the NetBackup catalogs See How to recover a catalog from a backup on page 199 190 Disaster recovery About disk recovery procedures for Windows 10 When catalog recovery is complete stop and restart the NetBackup services 11 12 Use t
153. enu click NetBackup Client Properties In the NetBackup Client Properties dialog box click the General tab m Check the Server to use for backups and restores drop down list Start the Backup Archive and Restore interface on the client On the File menu click Specify NetBackup Machines and Policy Type In the Specify NetBackup Machines and Policy Type dialog box click the Server to use for backups and restores drop down list Troubleshooting procedures 57 Verifying host name and service entries in NetBackup m The bp conf file on UNIX servers and clients and Macintosh clients m The veritas nbuclt netback bp ini file on NetWare clients Also verify that reverse DNS addressing is configured 8 Toconfirm the setup use the NetBackup bpcintcmd utility the IP addresses and hostnames in DNS NIS and local hosts files on each NetBackup node See About the bpclntcmd utility on page 66 Example of host name and service entries on UNIX master server and client The following illustration shows a UNIX master server with one UNIX client 58 Troubleshooting procedures Verifying host name and service entries in NetBackup Figure 2 1 UNIX master server and client UNIX jupiter Master Server Ethernet Policy Client List UNIX jupiter Client mars usr openv netbackup bp conf SERVER jupiter CLIENT_NAME jupiter usr openv netbackup bp conf etc inetd conf SERVER jup
154. equate information or if it seems to perform incorrectly run necc with the debug option to include additional debug messages in the nbcc info txt file For troubleshooting run necc when the system is in the same state as when the problem occurred For example do not stop and restart the NetBackup processes after the error occurs or make a change to the server or network NBCC may not be able to gather key information about the problem The nbcc info txt file provides an overview of the environment where necc is run and contains the following General operating system and NetBackup configuration information on the environment that nBcc detects A copy of the nscc processing information that was displayed to stpout or STDERR This information would indicate the processing that nscc had done The Processing detected NetBackup server entries section of the nocc info txt contains a Summary of NBCC server processing This information summarizes the results of the processing of detected server entries See Example of an NBCC progress display on page 163 For a full description of the necc command options refer to the necc man page Using NetBackup utilities 163 About the NetBackup consistency check utility NBCC See the NetBackup Commands Reference Guide Output from the NetBackup consistency check utility NBCC NBCC writes the information it gathers to packaged files in the following directory UNIX and
155. equirements that are listed in your product documentation Also you should be at the computer on which the problem occurred in case it is necessary to replicate the problem When you contact Technical Support please have the following information available m Product release level Hardware information Available memory disk space and NIC information Operating system Version and patch level Network topology Router gateway and IP address information Problem description m Error messages and log files m Troubleshooting that was performed before contacting Symantec m Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key access our technical support Web page at the following URL www symantec com business support Customer service Customer service information is available at the following URL www symantec com business support Customer Service is available to assist with non technical questions such as the following types of issues Questions regarding product licensing or serialization Product registration updates such as address or name changes General product information features language availability local dealers Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec s technical
156. er 314 Robotic test utilities Robotic tests on Windows A acssel description 297 acsssi description 297 acstest 313 Adaptive Server Anywhere 70 admin log 127 admincmd directory 270 administration interface activity logging 147 errors 145 AdvancedDisk 177 187 Alternate client restores host xlate file 308 altnames file 285 application server status codes Java interface 145 archiving for NBCC 163 for nbsu 158 ascd description 297 Auth User for PBX 77 auto configuration problems 29 avrd description 298 backup NetBackup catalogs 254 process files 236 multiplexing 242 NetWare clients 250 Windows clients 249 process overview 239 247 snapshot overview 243 synthetic processes 251 UNIX clients 237 Bare Metal Restore 175 177 194 bin Media and Device Management 296 UNIX client 269 270 BP 264 bp description 272 log 136 UNIX client log 134 bp conf file 238 UNIX client server 270 SERVER entries 92 bp kill_all 79 80 BP NLM 250 272 bp start_all 80 bpadm description 272 bparchive description 272 log 134 136 bpbackup description 273 log 134 136 bpbackup log 136 BPBACKUP_ POLICY 238 BPBACKUP_SCHED 238 bpbkar description 273 log 134 136 bpbkar log 136 BPBKAR32 249 273 bpbrm 245 description 273 bpbrm log 127 BPCD 264 bpcd description 274 server log 127 UNIX client log 134 136 BPCD NLM 274 BPCDW32 EXE 274 bpdbjobs description 274 bpdbjobs log 127 316 Index bpd
157. er presented 312 Robotic test utilities Robotic tests on Windows m Execute the following command usr openv volmgr bin robtest The test utility menu appears m Select a robot and press Enter The test starts If the robot is not configured you cannot use robtest and must execute the command that applies to the robot you test ACS usr openv volmgr bin acstest r ACSLS hostpath for acstest to work on UNIX and Linux acssel and acsssi must be running ODL usr openv volmgr bin odltest r roboticpath TL4 usr openv volmgr bin tl4test r roboticpath TL8 usr openv volmgr bin tl8test r roboticpath TLD usr openv volmgr bin tldtest r roboticpath TLH usr openv volmgr bin tlhtest r robotic library path TLM usr openv volmgr bin tlmtest r DAS host TSH usr openv volmgr bin tshtest r roboticpath More information on ACS TLH and TLM robotic control is available See the NetBackup Device Configuration Guide In the previous list of commands roboticpath is the full path to the device file for the robotic control SCSI You can review the section for your platform to find the appropriate value for roboticpath An optional parameter specifies the device file path for the drives so that this utility can unload the drives using the SCSI interface Robotic tests on Windows If the robot has been configured that is added to the EMM database start the robotic test utility by using the robtest command This action
158. er to Symantec technical support See About the nbcplogs utility on page 170 About the analysis utilities for NetBackup debug logs The debug log analysis utilities enhance NetBackup s existing debug capabilities by providing a consolidated view of a job debug log NetBackup jobs span multiple processes that are distributed across servers You can get more information about legacy logging and unified logging See About logs on page 99 To trace a NetBackup job you must view and correlate messages in multiple log files on multiple hosts The log analysis utilities provide a consolidated view of Using NetBackup utilities About the analysis utilities for NetBackup debug logs the job debug logs The utilities scan the logs for all processes that are traversed or run for the job The utilities can consolidate job information by client job ID start time for the job and policy that is associated with the job Table 4 2 describes the log analysis utilities To see the parameters limitations and examples of use for each utility use the command with the he1p option All the commands require administrative privileges The log analysis utilities are available for all platforms that are supported for NetBackup servers Note The utilities must be initiated on supported platforms However the utilities can analyze debug log files from most NetBackup client and server platforms for UNIX and Windows Table 4 2 Analy
159. erver daemons and programs occasionally log information through the syslogd man page syslogd then shows a message or writes the information in an appropriate system log or the console log On UNIX NetBackup automatically records robotic and network errors in the system logs by using syslogd On Windows NetBackup records robotic and drive errors in the Event Viewer Application log On both operating systems log entries are also made when robotically controlled drives change between UP and DOWN states Note On HP UX the sysdiag tool may provide additional information on hardware errors To enable system logs use one of the following m Use the 1tid command that started the device management processes If the v option is included on the 1tid command all daemons that were started as a result also have the v option in effect m Use acommand to start a specific daemon for example acsd v On UNIX enable debug logging to the system logs by including the verbose option v on the command that you use to start a daemon To troubleshoot 1tid or robotic software you must enable system logging See the syslogd 8 man page for information on setting up system logs Errors are logged with LOG_ERR warnings with Loc_WARNING and debug information with LOG NOTICE The facility type is daemon See the syslogd man page for the locations of system log messages on your system 102 Using logs About unified logging About unifie
160. ervice RMMS runs on media servers 231 nbevtmgr Event Manager Service Provides asynchronous Event Management Services for cooperating participants 248 bmrlauncher BMR launcher A utility in the Windows BMR Fast Restore image that configures the BMR environment 254 Recovery assistant for SharePoint Portal Server for NetBackup clients 261 Artifact generator generated source 263 nbconsole NetBackup Administration Console for Windows Using logs 111 About unified logging Table 3 2 Originator IDs for the server processes that use unified logging continued 271 Legacy error codes 272 libexpmgr Expiration Manager Handles the capacity management and the image expiration for storage lifecycle operations 286 Encryption key Management Service 293 NetBackup Audit service 294 NetBackup Audit messages 360 NetBackup Client Oracle utility 363 nbars Database Agent Request server process call UNIX client processes that use unified logging Most UNIX client processes use legacy logging with the exception of a few Bare Metal Restore processes However the following UNIX client processes use unified logging Table 3 3 UNIX client processes that use unified logging a 121 bmrsavecfg 122 bmrec Originates from the BMR boot server which may not be a NetBackup server and runs on the restoring client 200 nbftclnt 359 nbbrowse NetBackup Client Browser 366
161. es bpcd 13782 tcp bpcd In etc inetd conf bpcd stream tcp nowait root usr openv netbackup bin bpcd bpcd Then run kill HUP to reread the etc inetd conf file as explained in step 3 Also update the applicable NIS or DNS files If these files are correct and you cannot connect to the client you may have problems with the network routing or the port assignment See the next step Table 2 8 Troubleshooting procedures 47 Resolving network communication problems with UNIX clients Steps for resolving network communication problems with UNIX clients continued Step 5 Ensure that the client listens on the correct port for the telnet connection to bpcd Run one of the following commands depending on platform and operating system netstat a grep bpcd netstat a grep 13782 rpcinfo p grep 13782 The value 13782 could also be the value that is specified during installation One of the following conditions occurs m Ifthe port is not the problem you see the following tcp 0 0 ant nul nul com 13782 whale com 1516 ESTABLISHED tcp 0 0 13782 LISTEN Where ESTABLISHED indicates that the telnet connection was established to bpcd through port 13782 on the client LISTEN indicates that the client listens for further connections on this port Change the port number for bpcd or other NetBackup services only if there is no alternative All NetBackup servers and clients in the configuration must u
162. eshooting procedures About troubleshooting procedures m About unavailable storage unit problems m About troubleshooting NetBackup in a SAN environment About troubleshooting procedures This chapter has procedures for finding the cause of NetBackup errors These procedures are general in nature and do not try to cover every problem that can occur They do however recommend the methods that usually result in successful problem resolution The amp CompanyName Technical Support site has a wealth of information that can help you solve NetBackup problems See the following site for comprehensive troubleshooting details www symantec com business support When you perform these procedures try each step in sequence If you already performed the action or it does not apply skip to the next step If it branches you to another topic use the solutions that are suggested there If you still have a problem go to the next step in the procedure Also alter your approach according to your configuration and what you have already tried Preliminary troubleshooting explains what to check first It branches off to other procedures as appropriate Troubleshooting installation and configuration problems apply specifically to installation problems and configuration problems General test and troubleshooting procedures define general methods for finding server and client problems and should be used last Note The term media server as distin
163. est policy Add a user schedule to your test policy the backup window must be open while you test Use a storage unit and media that was verified in previous steps Table 2 6 Troubleshooting procedures 35 Testing the master server and clients Steps for testing the master server and clients continued Step 11 Backup and restore a file Start a user backup and restore of a file by using the client user interface on the master server Monitor the status and the progress log for the operation If successful this operation verifies that the client software is functional on the master server If a failure occurs check the NetBackup All Log Entries report To isolate the problem further check the appropriate debug logs from the following list Ona UNIX system the debug logs are in the usr openv netbackup logs directory On a Windows system the debug logs are in the install_path NetBackup logs directory Debug log directories exist for the following processes bparchive UNIX only bpbackup UNIX only bpbkar bpcd bplist bprd bprestore nbwin Windows only bpinetd Windows only Explanations about which logs apply to specific client types are available See About logs on page 99 See About unified logging on page 102 See About legacy logging on page 124 Step 12 Reconfigure the test policy Reconfigure your test policy to name a client that is located elsew
164. estore Manager manages the client and bptm or bpdm process It also uses error status from the client and from bptm or bpdm to determine the final status of backup or restore operations Started By For each backup or restore nbjm starts an instance of bpbrm on the server with the appropriate storage unit Stopped By Completion of operation Debug Log bpbrm legacy log directory on the server 274 Backup and restore functional overview NetBackup programs and daemons Table A 4 Backup daemons and programs continued bpcd On UNIX clients bpcd is the NetBackup client daemon and lets NetBackup start programs on remote hosts can be UNIX clients or other servers For example the server can connect to UNIX clients without requiring rhosts entries on the remote host The program is used when nbjm starts bpbbrm and when bpbrm communicates with the client For a description of the NetBackup client daemon on PC clients see BPCDW32 EXE and BPCD NLM in this table Started By inetd Stopped By Completion of operation Debug Log bpcd legacy log directory on both client and server BPCD NLM On NetWare clients BPCD NLM is the executable file that starts the NetBackup client daemon Started By When you enter BPSTART NCF at the NetWare Server console Or add BPSTART NCF to your autoexec ncf file Stopped By UNLOAD BP command Debug Log BPCD legacy log directory on the client BPCDW32 EXE On Win
165. etBackup consistency check utility NBCC 0 Output from the NetBackup consistency check utility NBCC conresar odnie i a A EEE TEO KEAN OTEO E Contents 9 10 Contents Chapter 5 Appendix A Example of an NBCC progress display 0cccceeseeeeeeeeeeeees 163 About the NetBackup consistency check repair NBCCR utility 167 About the nbcplogs utility cece cece cee cec eee eenee eens ee eeneneens 170 Disaster recovery oo cccccccccccccsccscceccseceeesesseseessesteseenes 173 About disaster recovery cccecec ccc ec nec eeeeceee eens ee sense eeesaeeneeaeens 173 Recommended backup practices ccccecececeeeeeeneneeeneeeaeaeaeeenes 174 About disk recovery procedures for UNIX and Linux 08 176 Recovering the master server disk for UNIX and Linux 177 About recovering the NetBackup media server disk for UNIX and TINUR 5 Sa eget oe pence on heeded wae dea vende dasb ume des E AEA EINN 182 Recovering the system disk on a UNIX client workstation 182 About clustered NBU server recovery for UNIX and Linux 183 Replacing a failed node on a UNIX or Linux cluster 183 Recovering the shared disk on a UNIX or Linux cluster 185 Recovering the entire UNIX or Linux cluster ceeeeeeeeeee ee 186 About disk recovery procedures for Windows ccccceeeee
166. etBackup services F the current device configuration differs from the configuration at the time of the catalog backup Reconfigure devices Inventory robots To exit the wizard click Finish You can now recover the NetBackup database if necessary 8 NetBackup does not run scheduled backup jobs until NetBackup is stopped and restarted Before restarting NetBackup protect the media that contains the backups that were successfully performed after the catalog backup that was used to recover the catalog Media protection may include the following tasks m Importing the backups from the backup media into the catalog m Write protecting the media m Ejecting the media and setting it aside Disaster recovery 217 How to recover a catalog from a backup m Freezing the media Stop and restart NetBackup on all the servers On UNIX and Linux usr openv netbackup bin bp kill_ all usr openv netbackup bin bp start_all On Windows install path NetBackup bin bpdown install _path NetBackup bin bpup If aremote EMM server is used start NetBackup on it before you start NetBackup on the master server Recovering the catalog image file using bprecover wizard You must have root administrative privileges to perform this procedure To recover the catalog image file using bprecover wizard 1 Start NetBackup by entering the following If your configuration includes an EMM server separate from the master server start
167. etion Y y N n N 164 Using NetBackup utilities About the NetBackup consistency check utility NBCC 2 0 Gathering required NetBackup configuration information If NBCC is unable to determine the NetBackup version for ANY detected media server is there a SINGLE version of NetBackup that you would like associated to these media servers Y y N n N After NBCC has completed gathering the NetBackup database information if there are any media servers that NBCC was unable to determine the NetBackup version you will be prompted for the version to associate with each media server If NBCC detects images that were written by media servers that are not known to NetBackup would you like NBCC to 1 Stop now since I know of such media servers and I wish to resolve these before running NBCC again 2 Prompt me again after NBCC has processed all images so that I can designate a media server known to NetBackup that full analysis will use to INHERIT ALL of the image copies associated to the unknown media servers 3 Prompt me again after NBCC has processed ALL images so that can select the course of action to take for EACH media server 4 Flag ALL of the unknown media servers so that full analysis will mark all of their related image copies to be EXPIRED 5 Flag ALL of the unknown media servers so that full analysis will generate COMMENTED out repairs that can be reviewed Ly 2 374751 lt 4 Determining the date for
168. following in the vm conf file DAYS TO KEEP LOGS 3 For instructions on how to use this entry see the NetBackup Administrator s Guide Volume II See Directory names for legacy debug logs for media and device management on page 129 Configuring legacy log rotation You can specify the maximum file size for a legacy log and the maximum number of log files to retain To configure the legacy log rotation 1 Inthe NetBackup Administration Console in the left pane expand NetBackup Management gt Host Properties gt Master Servers 2 Inthe right pane double click the server you wan to modify Using logs 133 About legacy logging 3 Inthe dialog box that appears in the left pane select Logging and check Enable robust logging Robust logging applies only to legacy logs Robust logging is also known as log rotation By default the maximum file size is 5120 KB and the maximum number of files that are kept per log directory is 3 If Enable robust logging is disabled the standard behavior remains in effect A single log file is created per log directory per day and log deletion is based on the Keep logs property 4 To change the maximum file size or the maximum number of log files per directory use the MaxLogFileSizekB and the NumberOfLogFiles options These options are part of the vxlogcfg command which is located in the following directory UNIX usr openv netbackup bin Windows install_path NetBackup bin U
169. fter the catalog backup that was used to recover the catalog This recovery can include the following m Importing the backups from the backup media into the catalog m Write protecting the media m Ejecting the media and setting it aside m Freezing the media Disaster recovery 207 How to recover a catalog from a backup 13 Youcan manually submit backup jobs before you stop and restart NetBackup Be aware that if you have not protected the media containing the backups done after the catalog backup the media may be overwritten 14 Stop and restart NetBackup on all the servers On UNIX and Linux usr openv netbackup bin bp kill all usr openv netbackup bin bp start_all On Windows install path NetBackup bin bpdown install _path NetBackup bin bpup If aremote EMM server is used start NetBackup on it before you start NetBackup on the master server If you have recovered from removable media that media is now frozen To unfreeze see the following See Unfreezing the online catalog recovery media on page 233 Recovering the entire catalog using bprecover wizard Thebprecover wizardcommandis an alternate way to recover an entire catalog that is backed up using the online catalog backup method This method does not require the NetBackup Administration Console You must have root administrative privileges to perform this procedure Note You must be logged on locally to the master server that being recovered
170. g Log admin legacy log directory on the server bparchive On UNIX clients this program communicates with bprd on the master server when a user starts an archive Started By Starting an archive by using the client user interface or by executing the usr openv netbackup bin bparchive command on the client Stopped By Completion of operation Debug Log bparchive legacy log directory on the client Table A 4 Backup and restore functional overview 273 NetBackup programs and daemons NetBackup daemons and programs continued bpbackup On UNIX clients this program communicates with bprd on the master server when a user starts a backup Started By Starting a backup by using the client user interface or by executing the usr openv netbackup bin bpbackup command on the client Stopped By Completion of operation Debug Log bpbackup legacy log directory on the client bpbkar On UNIX clients 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 legacy log directory on the client BPBKAR32 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 legacy log directory in the NetBackup logs directory on the client bpbrm On master and media servers the Backup R
171. g NetBackup protect the media that contains the backups that were successfully performed after the catalog backup that was used to recover the catalog This media protection may include the following tasks m Importing the backups from the backup media into the catalog m Write protecting the media m Ejecting the media and setting it aside Disaster recovery 219 How to recover a catalog from a backup m Freezing the media 7 Stop and restart NetBackup on all the servers On UNIX and Linux usr openv netbackup bin bp kill_ all usr openv netbackup bin bp start_all On Windows install path NetBackup bin bpdown install _path NetBackup bin bpup If aremote EMM server is used start NetBackup on it before you start NetBackup on the master server Recovering relational database files from an online catalog backup If the NetBackup NBDB or Bare Metal Restore BMRDB relational database files need to be recovered perform this procedure The full procedure is necessary only if the NBDB database has been corrupted A temporary database must be created to restore from the catalog backup If the NBDB database is available and the SQL Anywhere server is running then do only steps 11 and 12 These steps replace the existing database with the copy from the catalog backup Note If your configuration includes a remote EMM server perform steps 1 through 7 on the EMM server 220 Disaster recovery How to recover a catalog fro
172. g aaa com and this name is also known to network services on the master server 310 Networks and hostnames Background for troubleshooting Appendix Robotic test utilities This appendix includes the following topics m About robotic test utilities m Robotic tests on UNIX m Robotic tests on Windows About robotic test utilities Each of the robotic software packages includes a robotic test utility for communicating directly with robotic peripherals The tests are for diagnostic purposes and the only documentation is the online Help that you can view by entering a question mark after starting the utility Specify h to display the usage message Note Do not use the robotic test utilities when backups or restores are active 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 Robotic tests on UNIX If the robot has been configured that is added to the EMM database start the robotic test utility by using the robtest command This action saves time since robotic and drive device paths are passed to the test utility automatically The procedure is as follows To use the robtest command do the following in the ord
173. g backups the appropriate recovery device s must be configured which may involve the following tasks m Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored If anon robotic drive is available that can read these backups then no robot is required Although manual intervention is required if multiple pieces of media are required See the NetBackup Device Configuration Guide m Use the NetBackup Device Configuration Wizard to discover and configure the recovery device in NetBackup See the NetBackup Administrator s Guide Volume I m Use the NetBackup command tpautoconf to discover and configure the recovery device in NetBackup Disaster recovery 179 About disk recovery procedures for UNIX and Linux See the NetBackup Commands Reference Guide m Update the device mapping files See the NetBackup Administrator s Guide Volume I 6 Ifyou must restore from the policy backups or catalog backups that were done to media the appropriate media may have to be configured in NetBackup See the NetBackup Administrator s Guide Volume I Configuring the media may require some or all of the following tasks m Manually load the required media into a stand alone recovery device m Use the NetBackup utilities such as robtest or vendor specific robotic control software to load media into the required recovery device or devices m Use the NetBacku
174. g command nbdevquery listdp Disk Pool Name Disk Pool Id Disk Type Status Flag Flag Raw Size GB Usable Size GB Num Volumes High Watermark Low Watermark Max IO Streams Comment Storage Server stype PureDisk dp PDpool U PDpool PDpool PureDisk UP Patchwork OptimizedImage 42 88 42 88 1 98 80 f woodridge min veritas com UP Max IO Streams is set to 1 which means the disk pool has unlimited input output streams To check the media servers run the following command tpconfig dsh all_host Media Server Storage Server User Id Storage Server Storage Server Storage Server Storage Server woodridge min veritas com woodridge min veritas com root Type BasicDisk Type NearStore Type SnapVault Type PureDisk This disk pool only has one media server woodridge You have completed the storage configuration validation Troubleshooting procedures 85 About troubleshooting duplication to a remote master The last phase of validation is the storage lifecycle policy configuration To run a duplication to remote master operation the source copy must be on storage unit PDstu Run the following command nbstl woodridge2bayside L Name woodridge2bayside Data Classification none specified Duplication job priority 0 State active Version 0 Destination 1 Use for backup Storage PDstu Volume Pool none specified Server Group none specified Retention Type
175. g detail enter VERBOSE 2 ora higher value This setting affects legacy logging only Warning High verbose values can cause debug logs to become very large m Set the logging level for individual processes In Host Properties change logging levels for individual processes in the Logging dialog box Or specify the verbose flag if available when you start the program or daemon See the NetBackup Administrator s Guide Volume I Using logs 131 About legacy logging Media and device management legacy logging has two levels not verbose the default and verbose To set the verbose higher level add the word VERBOSE to the vm conf file Create the file if necessary Restart 1tid and vma after you add the VERBOSE entry This entry affects logging levels in the Event Viewer Application and System log The vm cont file is located in the following directory UNIX usr openv volmgr Windows install_path Volmgr About limiting the size and the retention of legacy logs Certain NetBackup processes write legacy debug logs Because legacy debug logs can grow very large enable them only if unexplained problems exist Delete the logs and the associated directories when they are no longer needed To limit the time NetBackup retains legacy debug logs specify the number of days in the Keep logs field The default is 28 days You can specify the number under Host Properties in the Clean up dialog box See the NetBackup Administrator
176. g directories Step 1 Create directories Create the following directories on the master Server install path netbackup logs bpsynth install _path netbackup logs bpdbm install _path netbackup logs vnetd Step 2 Create directories Create the following directories on the media Server install _path netbackup logs bpcd install _ path netbackup logs bptm install path netbackup logs bpdm Step 3 Change the Global In Host Properties select a master server and set the Global logging level to 5 logging level See Changing the logging level on page 140 See About global logging levels on page 138 See Using the Host Properties window to access configuration settings on page 69 Step 4 Rerun the job Rerun the job and gather the logs from the directories that you created The bptm logs are required only if the images are read from or written to a tape device The bpdm logs are needed only if the images are read from or written to disk If the images are read from multiple media servers the debug logs for bptm or bpdm must be collected from each media server See Logs to accompany problem reports for synthetic backups on page 141 File name formats for legacy logging In the standard legacy log system a single NetBackup process creates one debug log file per day In the legacy logging system with Enable robust logging enabled a NetBackup process creates a certain number of log files Each file grows to a certain s
177. g network communication problems with PC clients 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 Do one of the following Windows clients Check the NetBackup client service port number Start the Backup Archive and Restore interface on the client On the File menu click NetBackup Client Properties In the NetBackup Client Properties dialog box on the Network tab check the NetBackup client service port number 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 The values on the Network tab are written to the services file when the NetBackup client service starts NetWare clients See the BPRD setting in the SYS VERITAS NBUCLT NetBack BP INT file UNIX NetBackup The bprd port number is in the etc services file servers i See Using the Host Properties window to access configuration settings on page 69 Windows NetBackup Set these numbers in the Client Properties dialog box in the servers Host Properties window See Using the Host Properties window to access configuration settings on page 69 Verify that the hosts file or its equivalent contains the NetBackup server name The hosts files are the following Windows XP or 2003 SystemRoot system32 drivers etc hosts NetWare SYyS etc hosts
178. g network communication problems with PC clients Windows NetWare clients UNIX NetBackup servers Check the NetBackup client service port number Start the Backup Archive and Restore interface on the client On the File menu click NetBackup Client Properties In the NetBackup Client Properties dialog box on the Network tab check the NetBackup client service port number 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 The values on the Network tab are written to the services file when the NetBackup client service starts See the BPCD setting in the SYS VERITAS NBUCLT NetBack BP INI file The bpcd port number is in the etc services file On Windows NetBackup servers see the Client Properties dialog box in the Host Properties window See Using the Host Properties window to access configuration settings on page 69 Correct the port number if necessary Then on Windows clients and servers stop and restart the NetBackup Client service On NetWare clients stop and restart the NetBackup client daemon bpca Do not change NetBackup port assignments unless it is necessary 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 Troubleshooting procedures 51 Resolvin
179. g the second to last field in the DR_MEDIA_REC line s m Save the catalog backup parent image file that was identified in the first substep m Relocate or remove all other image files that relate to the catalog backup policy If the NetBackup configuration includes a remote EMM server on the master server go to the image database for the remote EMM server Relocate or remove any images that relate to the catalog backup policy On the master server for each media that is identified in step 1b run the following command bpimport create_db_info server server name id media id On the master server run the following command bpimport On the master server for each media that is identified in step 1b run the following command bpmedia unfreeze m media_id h server _ name 234 Disaster recovery How to recover a catalog from a backup Appendix Backup and restore functional overview This appendix includes the following topics About backup and restore functional overview Backup and restore startup process Backup and archive processes Backups and archives UNIX clients Restore processes NetBackup directories and files NetBackup programs and daemons NetBackup catalogs About backup and restore functional overview This appendix provides a functional overview of NetBackup backup and restore operations for both UNIX and Windows The discussions include descriptions of important services or daemons and pr
180. ge 99 m Consider moving the NetBackup unified logging files to a different file system See About changing the location of unified log files on page 112 3 Use the Activity Monitor to verify that the NetBackup relational database service is running This service is the NB_dbsrv daemon on UNIX and the Adaptive Server Anywhere Veritas_NB service on Windows 4 Ifthe NetBackup relational database service is stopped note the following Do not stop the nbrb service If you stop the nbrb service while the NetBackup relational database service is down it can result in errors m Restart the NetBackup relational database service Verify that the NetBackup relational database service is running If it is not and you remove files to free up disk space you may not fix the problem The relational database service must be restarted to allow the Resource Broker nbrb to allocate job resources Troubleshooting procedures Frozen media troubleshooting considerations Frozen media troubleshooting considerations Frozen media can cause a number of problems including one of the following status codes 84 85 86 87 and 96 When troubleshooting frozen media be aware of the following Be sure that the media server that freezes the media stores the actual FROZEN status of that media in its media database MediaDB Every media server including the master server has its own unique media database Use the bpmedialist command to access the
181. gh bpcd on the media server and bpbrm starts bpfis through bpcd on the client bpfis creates a snapshot of the client s data by means of a snapshot method When bpfis is finished it sends snapshot information and completion status to bpbrm and exits bpbrm in turn reports the snapshot information and status to nbjm and exits nbjm relays the information and status to nbpem nbpem submits a child job for the backup to nbjn with a file list derived from the snapshot information nbjm starts bpbrm to back up the snapshot bpbrm Starts bpbkar on the client bpbkar sends the file catalog information to bpbrm which relays it to the NetBackup file database bpdbm on the master server bpbrm Starts the process bptm parent on the media server The next step depends on whether the media server backs up itself bptm and bpbkar are on the same host or the media server backs up a client that resides on a different host If the media server backs up itself bpbkar stores the snapshot based image block by block in shared memory on the media server If the media server backs up a client that resides on a different host bptm on the server creates a child process of itself The child receives the snapshot based image from the client by means of socket communications and then stores the image block by block in shared memory The original bptm process then takes the backup image from shared memory and sends it to the storage device disk or tape
182. gineering 140 Media server user interface for the Enterprise Media Manager EMM 142 bmrepadm Manages the Bare Metal Restore external procedures that are used during a restore 143 mds The media selection component and device selection component of Enterprise Media Manager EMM 144 Device Allocator for shared drives 146 TheSymantec OpsCenter reporting service Part of Symantec OpsCenter 147 The Symantec OpsCenter Client Part of Symantec OpsCenter 148 The Symantec OpsCenter Server Part of Symantec OpsCenter 151 NDMP protocol messages avrd and robotic processes 154 bmrovradm Manages the custom override functions for Bare Metal Restore Table 3 2 Using logs 109 About unified logging Originator IDs for the server processes that use unified logging continued 156 Controls the logging level in the ACE TAO CORBA components for any process that uses a CORBA interface The default level is 0 only important messages are logged This logging is intended for Symantec engineering Note If Symantec Technical Support instructs you to increase the logging level you must increase the level for originator ID 137 to 4 or higher Warning A debug logging level greater than 0 generates large amounts of data 158 Remote access interface for NetBackup clients 159 Transmater for NetBackup clients 163 svcmon NetBackup Service Monitor M
183. gs utility Chapter Disaster recovery This chapter includes the following topics m About disaster recovery m Recommended backup practices m About disk recovery procedures for UNIX and Linux m About clustered NBU server recovery for UNIX and Linux m About disk recovery procedures for Windows m About clustered NBU server recovery for Windows m Howto recover a catalog from a backup About disaster recovery Data backup is essential to any data protection strategy especially a strategy that is expected to assist in disaster recovery Regularly backing up data and therefore being able to restore that data within a specified time frame are important components of recovery Regardless of any other recovery provisions backup protects against data loss from complete system failure And off site storage of backup images protects against damage to your on site media or against a disaster that damages or destroys your facility or site To perform recovery successfully the data must be tracked Knowing at what point in time the data was backed up allows your organization to assess the information that cannot be recovered Configure your data backup schedules to allow your organization to achieve its recovery point objective RPO The RPO is the point in time before which you cannot accept lost data If your organization can accept one day s data loss your backup schedule should be at least daily That way you can achieve an RPO of one da
184. h logs Windows See About unified logging on page 102 Table A 4 Backup and restore functional overview 283 NetBackup programs and daemons NetBackup daemons and programs continued pbx_exchange Private Branch Exchange PBX is a common services framework that helps limit the number of TCP IP ports that the CORBA services of NetBackup use Started By Started when NetBackup starts or by opt VRTSpbx bin vxpbx_ exchanged start Stopped By Stopped when NetBackup stops or by opt VRTSpbx bin vxpbx_ exchanged stop Debug Log On the server opt VRTSpbx 1og UNIX or install path VxPBX log Windows See Accessing the PBX logs on page 77 q12300_stub On a Solaris media server that is enabled for SAN Client transfers over fibre channel q12300_stub is a device driver used to read and write to the NVRAM on a target mode Fibre Channel Host Bus Adapter On Linux it also prevents initiator mode drivers from binding to the target mode fibre channel HBAs Started By Device driver that is started by the operating system onareboot after nbftsrv_config nbhba on Linux and Solaris On Linux it is also started on all reboots after nbftsrv_config Stopped By Device driver that is stopped by nbfdrv64 on Linux and nbftsrv_config on Solaris Debug Log The host operating system handles the logging for the device driver in the system messages log var adm messages Solaris or var log messages Linu
185. hase 3 Copy data In phase 3 bpsynth starts the writer bptm for tape and disk on the media server to write the new synthetic image bpsynth starts a reader bptm tape or bpdm disk process for each component image on a media server that can access the component image The reader process reads all extents for the component image Figure A 8 illustrates how phase 3 operates Figure A 8 Synthetic backup copy data phase Media server new m lt gt data flow parent bptm or bpdm component image s Note that bpsynth only starts the parent bptm writer and bpdm reader process on the media server The parent in turn starts a child process The parent and child communicate by means of buffers in shared memory The bpsynth process sends the extents starting block and count for each component image to the corresponding child bptm or bpdm reader process 254 Backup and restore functional overview Backups and archives UNIX clients The parent bptm or bpdm reader process reads the data from the appropriate media into the shared buffers The child bptm or bpdm reader process sends the data in the shared buffers to the child bptm writer process over a socket The child bptm writer process writes the data into the shared buffers The parent bptm writer process copies the data from the shared buffers to the media and notifies bpsynth when the synthetic image is complete Phase 4 Validate the image
186. hat is in the EMM database as an extra measure of verification before mounting the tape A request for media that is in a robot that can read barcodes begins in the same manner as other requests See Figure B 4 on page 295 ltid 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 Itid and takes one of the following actions m Ifthe barcodes don t match and the mount request is not for a NetBackup backup job the robotic daemon informs Itid and a pending action request Misplaced Tape appears in the Device Monitor An operator must then insert the correct tape in the slot m Ifthe barcodes don t match and the mount request is for a NetBackup backup job the robotic daemon informs Itid and the mount request is canceled NetBackup bptm then requests a new volume from nbjm and from EMM m 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 example NetBackup checks the media ID and if it also matches what should b
187. he catalog recovery If a full backup of these clients is not run after a catalog recovery these files could be skipped and not backed up by subsequent incremental backups Online hot catalog backup is a policy driven backup that supports tape spanning and incremental backups It allows for restoring catalog files from the Backup Archive and Restore interface Online catalog backups may be run while other NetBackup activity occurs which provides improved support for environments in which continual backup activity is typical Symantec recommends saving the disaster recovery files that are created by the online catalog backup to a network share or removable device Do not save the disaster recovery files to the local computer Catalog recovery from an online catalog backup without the disaster recovery image file is a more complex procedure and time consuming procedure 175 176 Disaster recovery About disk recovery procedures for UNIX and Linux Automated recovery Online catalog disaster recovery information email Identifying the correct catalog backup Catalog recovery time Master and media server backups The catalog disaster recovery file created during an online catalog backup is intended to automate the process of NetBackup recovery If you recover a system other than the one that originally made the backups it should be identical to the original system For example the system that performs the recovery should inclu
188. he device A SCSI device monitoring utility is required to resolve this issue which neither CommandCentral Storage nor NetBackup currently supplies Symptom The backup job fails intermittently and the drive is down intermittently No errors appear in the error log other than that the job failed To use CommandCentral Storage to troubleshoot an intermittent drive failure ina SAN environment 1 Select adrive inside the NetBackup Device Monitor Launch CommandCentral Storage in the drive context to see whether the drive is connected to the SAN 2 Check CommandCentral Storage alert reports to see whether a SAN problem existed that would have affected the drive during the time the backup job failed Chapter Using logs About logs This chapter includes the following topics About logs About UNIX system logs About unified logging About legacy logging About global logging levels Logs to accompany problem reports for synthetic backups Setting retention limits for logs on clients Logging options with the Windows Event Viewer Troubleshooting error messages in the NetBackup Administration Console for UNIX NetBackup uses several different logs and reports to help you troubleshoot any problems that you encounter Users need to know where log and report information is on their systems Figure 3 1 shows the location of the log and report information on the client and the server and the processes that make the information availa
189. he devices necessary to read the media listed above 3 Inventory the media 4 Make sure master server can access the attached DR image file Start NetBackup Recovery Wizard from the NetBackup Administration Console Or start the wizard from a command line by entering bprecover wizard Disaster Recovery Procedure without the DR Image File NOTE ONLY ATTEMPT THIS AS A LAST RESORT If you do not have the attachment included with this email use the following instructions to recover your catalog 1 Install NetBackup 2 Configure the devices necessary to read the media listed above 3 Inventory the media 4 Run bpimport create db info srvr name id storage DiskUnitl 5 Go to the following directory to find the DR image file CatalogBackup_1123605764 FULL usr openv netbackup db images ant 1123000000 tmp Disaster recovery How to recover a catalog from a backup 6 Delete the other files in the directory 229 7 Open CatalogBackup_1123605764 FULL file and find the BACKUP_ID for example ant_1123605764 8 Run bpimport server name backupid ant_1123605764 9 Run bprestore T w L progress log C ant t 35 p CatalogBackup X s 1123605764 e 1123605764 if the DR image is a result of an incremental backup 1 To recover the NetBackup relational database run bprecover r nbdb Stop and Start NetBackup backup 4 To make sure the volume information is updated inventory the media to updat
190. he following bpdown and bpup commands the Activity Monitor in the NetBackup Administration Console or the Services application in the Windows Control Panel install _path NetBackup bin bpdown install _path NetBackup bin bpup Your configuration may include an EMM server that is separate from the master server If so start NetBackup on the EMM server before starting NetBackup on the master server Warning In step 11 do not restore files to the install _path NetBackup db install _path NetBackupDB install_path NetBackup var Or install_path Volmgr database directories The catalogs were recovered in step 9 and overwriting them with regular backups leave them in an inconsistent state If the NetBackup relational database files were relocated using nbdb_move from install _path NetBackupDB data they are recovered in step 9 and should not be restored in step 11 To restore all other files do the following actions in the order shown m Start the NetBackup Administration interface on the master server m Start the Backup Archive and Restore utility m Browse for restores and select only the partitions that were lost Select the system directory typically c winnt which ensures that all registry files are restored m Deselect the install _path NetBackup db install_path NetBackupDB install_path NetBackup var and install _path Volmgr database directories see the caution in step 10 m Ifyoureinstall Windows select the Over
191. he servers and clients See Testing the master server and clients on page 32 See Testing the media server and clients on page 36 If you cannot start any of these processes or services check the appropriate debug logs for NetBackup problems See About logs on page 99 When these processes and services start they continue to run unless you stop them manually or a problem occurs on the system On Windows systems we recommend that you add commands for starting them to your startup scripts so they restart in case you have to reboot Troubleshooting installation problems Use the following steps to troubleshoot installation problems Table 2 3 Steps for troubleshooting installation problems Step 1 Determine if you can install the software on the master server and the media servers by using the release media Some reasons for failure are as follows m Not logged on as an administrator on a Windows system you must have permission to install services on the system m Permission denied ensure that you have permission to use the device and to write the directories and files being installed m Bad media contact Technical Support m Defective drive replace the drive or refer to vendor s hardware documentation m Improperly configured drive refer to the system and the vendor documentation Table 2 3 Troubleshooting procedures Troubleshooting configuration problems Steps for troublesh
192. here in the network Use a storage unit and media that has been verified in previous steps If necessary install the NetBackup client software 36 Troubleshooting procedures Testing the media server and clients Table 2 6 Steps for testing the master server and clients continued Step 13 Create debug log directories Create debug log directories for the following processes bprd on the server bpcd on the client bpbkar on the client nbwin on the client Windows only bpbackup on the client except Windows clients bpinetd Windows only Explanations about which logs apply to specific client types are available See About logs on page 99 See About unified logging on page 102 See About legacy logging on page 124 Step 14 Verify communication between the client and the master server Perform a user backup and then a restore from the client that is specified in step 8 These actions verify communications between the client and the master server and NetBackup software on the client If an error occurs check the All Log Entries report and the debug logs that you created in the previous step A likely cause for errors is acommunications problem between the server and the client Step 15 Test other clients or storage units When the test policy operates satisfactorily repeat specific steps as necessary to verify other clients and storage units Step 16 Test the remain
193. his example uses the i option with the name of the process nbpem Examples of using vxlogmgr to manage unified logs The following examples show how to use the vxlogmgr command to manage unified logging files Log file management includes actions such as deleting or moving the log files Table 3 9 Example uses of the vxlogmgr command List the log files List all unified log files for the nbrb service vxlogmgr s o nbrb usr openv logs nbrb 51216 118 1342895976 050503 00 log usr openv logs nbrb 51216 118 1342895976 050504 00 log usr openv logs nbrb 51216 118 1342895976 050505 00 log Total 3 file s Delete the oldest log Based on the List the log files example if the vxlogcfg NumberOfLogFiles option is files set to 1 the following deletes the two oldest log files for the nbrb service vxlogmgr d o nbrb a Following are the files that were found usr openv logs nbrb 51216 118 1342895976 050504 00 log usr openv logs nbrb 51216 118 1342895976 050503 00 log Total 2 file s Are you sure you want to delete the file s Y N Y Deleting usr openv logs nbrb 51216 118 1342895976 050504 00 log Deleting usr openv logs nbrb 51216 118 1342895976 050503 00 log Using logs 121 About unified logging Table 3 9 Example uses of the vxlogmgr command continued Delete the newest log Delete all the unified log files that NetBackup created in the last 15 days files vxlogmgr d prodid 5121
194. if different drives within a robot can attach to different hosts the robotic daemon communicates with a robotic control daemon see below robotic control 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 Media and device management functional description Media and device management process Figure B 1 Starting media and device management At system startup the server automatically starts Itid which starts applicable robotic daemons To start the processes manually enter On UNIX usr openv netbackup bin bp start_all On Windows install_path NetBackup bin bpup Automated Cartridge System 3 Optical Disk Coad gt Library tld pe Tape Library 4mm Css tect Tape Library 8mm gt Tape Library DLT Tape Library FF Half inch Tape Library gt timd B Multimedia Tape Stacker Eai B Half inch Media and device management process When the media and device management daemons are running NetBackup Storage Migrator UNIX only Storage Migrator for Microsoft Exchange Windows only or users can request data storage or retrieval The request is initially handled
195. igured to start the bpcd NLM bpcd nim automatically An NLM is similar to a service NLM stands for NetWare Loadable Module Note that all NetBackup processes can be started manually by running the following usr openv netbackup bin bp start_all Backup and archive processes The backup processes and archive processes vary depending on the type of client The following explains the variations and describes the synthetic backup process A description is included about how NetBackup operates when backing up its catalogs Job scheduling The scheduler process bpsched consists of the following services m The nbpen service Policy Execution Manager does the following creates policy client tasks and determines when jobs are due to run It starts the job and upon job completion determines when the next job should run for the policy client combination Backup and restore functional overview 237 Backups and archives UNIX clients m The nbjm service Job Manager accepts requests from nbpem to run backup jobs or to run media jobs from commands such as bplabel and tpreq nbjm acquires resources for each job such as storage unit drives media and client and policy resources and executes the job m Thenbrb service Resource Broker allocates resources in response to requests from nbjm nbrb acquires physical resources from nbemm the Enterprise Media Manager service It also manages logical resources such as multiplex groups max
196. imum jobs per client and maximum jobs per policy nbrb is also responsible for initiating drive unloads and manages pending request queues EMM server and master server The NetBackup master server and the Enterprise Media Manager EMM server can be on the same physical host or on different hosts The master server is responsible for running jobs as configured in NetBackup policies The nbpem and nbjm services run only on the master server The EMM server allocates resources for one or more master servers The EMM server is the repository for all device configuration information The nbemm service and the nbrb service run only on the EMM server The nbemm service centralizes resource selection and maintains devices media and storage units in a relational database 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 are also supported you cannot archive raw partitions When the operations start they are all similar to the extent that the same daemons and programs execute on the server Each type of backup is started differently as follows m Scheduled backups begin when the nbpem service detects that a job is due nbpem checks the policy configurations for the scheduled client backups that are due m Immediate manual backups begin if the administrator chooses this option in the NetBackup Adm
197. ine with an empty shared directory m Valid online catalog backups exist To recover the shared disk on a Windows cluster that uses VCS 1 Clear the faulted NetBackup resource group disable monitoring and bring up the shared disk and virtual name resources on a functioning node Ensure that all NetBackup shared disks are assigned the same drive letters that were used when NetBackup was originally installed and configured To reconfigure NetBackup for the cluster initialize the database by running the following commands in sequence on the active node bpclusterutil ci tpext bpclusterutil online Use the appropriate NetBackup catalog recovery procedure to restore the NetBackup catalog information on the shared disk See Recovering the master server and Windows on page 191 If the clustered NetBackup server is a media server verify that the restored vm conf file contains the correct host specific MM_ SERVER_NAME configuration entry for the active node If MM_ SERVER_NAME is different from the local host name edit the file and change the server name to the local host name MM_SERVER_NAME lt local host name gt Use NetBackup to restore any data on the shared disks Details are available on how to perform a restore Refer to the NetBackup Backup Archive and Restore Getting Started Guide Configure required devices and media and recover the NetBackup catalogs Manually shut down and restart NetBackup on the active
198. ing policies and schedules 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 recommended actions as is part of the error status code Testing the media server and clients If you use media servers use the following steps to verify that they are operational Before testing the media servers eliminate all problems on the master server See Testing the master server and clients on page 32 Table 2 7 Step 1 Troubleshooting procedures 37 Testing the media server and clients Steps for testing the media server and clients Enable legacy debug logs Enable appropriate legacy debug logs on the servers See About logs on page 99 See About legacy logging on page 124 If you are uncertain which logs apply enable them all until you solve the problem Delete the legacy debug log directories when you have resolved the problem Step 2 Configure a test policy Configure a test policy with a user schedule set the backup window to be open while you test by doing the following m Name the media server as the client and a storage unit that is on the media server preferably a nonrobotic drive m Adda volume on the EMM database host for the devices in the storage unit Ensure that the volume is in the NetBackup volum
199. inistration Console or runs the bpbackup command with the i option This action causes bprd to contact nbpem which then processes the policy client and schedule that are selected by the administrator m User directed backups or archives begin when a user on a client starts a backup or archive through the user interface on the client The user can also enter 238 Backup and restore functional overview Backups and archives UNIX clients the bpbackup or bparchive commands on the command line This action invokes the client s bpbackup or bparchive program which sends a request to the request daemon bprd on the master server When bprd receives the user request it contacts nbpem which checks the policy configurations for schedules By default nbpem chooses the first user directed schedule that it finds in a policy that includes the requesting client For user directed backups or archives it is also possible to specify a policy and schedule A description is available of the UNIX Bppacxup_PoLicy and BPBACKUP SCHED options in bp conf and the Windows equivalents See the NetBackup Administrator s Guide Volume II Backup process This topic uses a diagram and a table to describe each step of a backup process PBX not shown in the diagram must be running for NetBackup to operate See Resolving PBX problems on page 75 Figure A 1 illustrates the various operations that comprise the backup process Backup and restore functiona
200. interrupted To address this situation stop and restart NetBackup For help on how to view and reset duplex mode for a particular host or device consult the manufacturer s documentation If the documentation is not helpful perform the following procedure To troubleshoot network interface card performance 1 Logon to the host that contains the network interface card whose duplex mode you want to check 2 Enter the following command to view the current duplex setting ifconfig a On some operating systems this command is ipconfig The following is an example output from a NAS filer e0 flags 1948043 lt UP BROADCAST RUNNING MULTICAST TCPCKSUM gt mtu 1500 inet 10 80 90 91 netmask Oxfffff800 broadcast 10 80 95 255 ether 00 a0 98 01 3c 61 100tx fd up flowcontrol full e9a flags 108042 lt BROADCAST RUNNING MULTICAST TCPCKSUM gt mtu 1500 ether 00 07 e9 3e ca b4 auto unknown cfg down flowcontrol full e9b flags 108042 lt BROADCAST RUNNING MULTICAST TCPCKSUM gt mtu 1500 ether 00 07 e9 3e ca b5 auto unknown cfg down flowcontrol full In this example the network interface that shows 100tx fd up is running in full duplex Only interface eo the first in the list is at full duplex A setting of auto is not recommended because devices can auto negotiate to half duplex 92 Troubleshooting procedures About SERVER entries in the bp conf file 3 The duplex mode can be reset by using the ifconfig or ipconfig
201. ions See the NetBackup Administrator s Guide Volume 1 Look at the Problems Report or the bperror list for these cases For troubleshooting job flow for automatic import jobs use the same command lines as you would for other storage lifecycle policy managed jobs To list images for which NetBackup has received notification from storage but not yet initiated import either pending or failed use the commands noted above or run the following command nbstlutil list copy type import U copy_ incomplete To list images that have been automatically imported run the following command nbstlutil list copy type import U copy state 3 U Master Server bayside min veritas com Backup ID woodridge 1287610477 90 Troubleshooting procedures About troubleshooting duplication to a remote master Client Backup Time Policy Client Type Schedule Type Storage L ifecycle Policy Storage Lifecycle State Time In Process Data Classification ID Version Number OriginMasterServer OriginMasterServerID Import From Replica Time Required Expiration Date Created Date Time woodridge 1287610477 Wed Oct 20 16 34 37 2010 two hop with dup 0 0 woodridge2bayside2pearl withdup 3 COMPLETE 1287610714 Wed Oct 20 16 38 34 2010 none specified 0 woodridge min veritas com 5cec09a da74 11d 8000 5b9412d8988 1287610672 Wed Oct 20 16 37 52 2010 1290288877 Sat Nov 20 15 34 37 2010 1287610652 Wed Oct 20 16 37 32 2010
202. iration Date woodridge min veritas com woodridge 1287610477 woodridge 1287610477 Wed Oct 20 16 34 37 2010 two hop with dup 0 0 woodridge2bayside2pearl withdup 3 COMPLETE 1287610545 Wed Oct 20 16 35 45 2010 none specified 0 none specified 00000000 0000 0000 0000 000000000000 0 Wed Dec 31 18 00 00 1969 0 Wed Dec 31 18 00 00 1969 Created Date Time Copy Master Server Backup ID Copy Number Copy Type Expire Time Expire LC Time Try To Keep Time Residence Copy State Job ID Retention Type MPX State Source Destination ID Last Retry Time Replication Destination Source Master Server Backup ID 1287610496 Wed Oct 20 16 34 56 2010 woodridge min veritas com woodridge 1287610477 102 3 1290288877 Sat Nov 20 15 34 37 2010 1290288877 Sat Nov 20 15 34 37 2010 1290288877 Sat Nov 20 15 34 37 2010 Remote Master 3 COMPLETE 25 0O FIXED 0 FALSE 1 1287610614 woodridge min veritas com woodridge 1287610477 Troubleshooting procedures About troubleshooting duplication to a remote master Copy Number 102 Target Machine bayside Target Info PureDiskVolume Remote Master none specified About troubleshooting automatic import jobs The automatic import jobs managed by the storage lifecycle policy components are different than legacy import jobs Automatic import jobs asynchronously notify NetBackup that an image needs to be imported Also the source d
203. iter bpcd see note 1 CLIENT_NAME mars etc inetd conf etc services bpcd see note 1 NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd etc services bpdbm 13721 tcp bpdbm NetBackup services Volume Manager services bpcd 13782 tcp bpcd vmd 13701 tcp vmd bprd 13720 tcp bprd tl8cd 13705 tcp tl8cd Consider the following notes about Figure 2 1 m The following is the complete inetd conf entry bpcd stream tcp nowait root usr openv netbackup bin bpcd bpcd m Allother applicable network configuration must also be updated to reflect the NetBackup information For example this information could include the etc hosts file and NIS and DNS if used See Example of host name and service entries on UNIX master server and media server on page 59 See Example of host name and service entries on UNIX PC clients on page 60 Troubleshooting procedures 59 Verifying host name and service entries in NetBackup See Example of host name and service entries on UNIX clients in multiple networks on page 62 See Example of host name and service entries on UNIX server that connects to multiple networks on page 64 Example of host name and service entries on UNIX master server and media server The following illustration shows a UNIX NetBackup media server named saturn Note the addition of a SERVER entry for saturn in the bp conf files on all the systems This entry is second beneath the
204. ize before it closes and a new one is created Legacy logging uses two formats for log file names The format that is used depends on whether the log uses the standard system or file rotation robust logging Using logs 127 About legacy logging Table 3 12 File name formats for different types of legacy logging Standard legacy logging m On UNIX log mmddyy For example log 040805 m On Windows mmddyy log For example 040105 log Legacy logging with robust mmddyy _nnnnn log logging enabled For example 040105 00001 log Where nnnnz is a counter or a rotation number for the log file When the counter exceeds the setting for number of log files the oldest log file is deleted The NumberOfLogFiles option on the vxlogcfg command sets the number of log files For compatibility with existing scripts the debug log file naming format does not change If robust file logging is enabled after standard legacy logs have been created only the log files for the processes that robust logging governs use the file rotation naming format Any mixture of new and old log file names in a legacy debug log directory is managed according to the Keep logs setting and the robust logging settings Directory names for legacy debug logs for servers Table 3 13 describes the directories you need to create to support legacy debug logs for servers Each directory corresponds to a process Unless it is noted each directory should be created un
205. kup 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 legacy logging directories manually see logs in the previous table More information is available See About legacy logging on page 124 272 Backup and restore functional overview NetBackup programs and daemons Table A 4 Backup daemons and programs 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 1logs 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 BP NLM 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 VERITAS NBUCLT NETBACK LOGS BP mmddyy logfile 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 bpadmcommand on the master server Stopped By Quit option from within bpadm Debu
206. kup db directory on UNIX servers and inthe install_path NetBackup db directory on Windows NetBackup servers Note also that the usr openv netbackup db class directory install_path NetBackup db class on Windows has a subdirectory for each NetBackuppolicy that contains information about the policy Table A 5 describes the NetBackup catalogs Table A 5 Backup and restore functional overview 285 NetBackup catalogs NetBackup catalogs config Configuration information This database resides on the master server and has three parts policy Contains the information about each NetBackup policy config Contains the information about global attributes storage units and database backups altnames Contains the 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 the information that is recorded during backup operations and used in the NetBackup reports failure history Contains the 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 NetBa
207. kup problems continued Ask the following questions Step 2 Identify what you were doing when the problem occurred What operation was tried What method did you use For example more than one way exists to install software on a client Also more than one possible interface exists to use for many operations Some operations can be performed with a script What type of server platform and operating system was involved If your site uses both the master server and the media server was it a master server or a media server If a client was involved what type of client was it Have you performed the operation successfully in the past If so what is different now What is the service pack level Do you use 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 Step 3 Record all information Capture potentially valuable information NetBackup progress logs NetBackup Reports NetBackup Utility Reports NetBackup debug logs Media and Device Management debug logs On UNIX NetBackup servers check for error or status messages in the system log or standard output Error or status messages in dialog boxes On Windows NetBackup servers check for error or status information in the Event Viewer Application and System log Rec
208. kup process for synthetic backup nbjm starts bpsynth bpsynth runs on the master server bptm NetBackup tape management process syslogs System log You must enable system logging to troubleshoot 1tid or robotic software See the syslogd man page user_ops The user_ops directory is created during the install of NetBackup on all servers and clients NetBackup Java interface programs use it for the following temporary files and for job and progress log files that the Backup Archive and Restore program jbpSA generates This directory must exist for successful operation of any of the Java programs and must have public read write and execute permissions user_ops contains a directory for every user that uses the Java programs In addition on NetBackup Java capable platforms the NetBackup Java interface log files are written in the nbj logs subdirectory All files in the user_ops directory hierarchy are removed according to the setting of the KEEP_LOGS_DAYS configuration option vnetd The Symantec network daemon used to create firewall friendly socket connections Started by the inetd 1M process Note Logging occurs in either the usr openv 1logs directory or the usr openv netbackup 1logs if the vneta directory exists there If the vnetd directory exists in both locations logging occurs only in usr openv netbackup logs vnetd Using logs About legacy logging More information is available on the programs and daem
209. kups the appropriate recovery device s must be configured Device configuration may include the following tasks m Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored If anon robotic drive is available that can read these backups then no robot is required Although manual intervention is required if multiple pieces of media are required See the NetBackup Device Configuration Guide m Use the NetBackup Device Configuration Wizard to discover and configure the recovery device in NetBackup See the NetBackup Administrator s Guide Volume I m Use the NetBackup command tpautoconf to discover and configure the recovery device in NetBackup See the NetBackup Commands Reference Guide manual 10 11 Disaster recovery About disk recovery procedures for UNIX and Linux m Update the device mapping files See the NetBackup Administrator s Guide Volume I If you must restore from the policy backups or catalog backups that were done to media the appropriate media may have to be configured in NetBackup See the NetBackup Administrator s Guide Volume I Configuring the media may require some or all of the following tasks m Manually load the required media into a stand alone recovery device m Use the NetBackup utilities such as robtest or vendor specific robotic control software to load media into the required recovery device or devices
210. l Support The Symantec Technical Support Web site has a wealth of information that can help you solve NetBackup problems Access Technical Support at the following URL www symantec com business support Note The term media server may not apply to the NetBackup server product It depends on the context When you troubleshoot a server installation be aware that only one host exists The master and the media server are one and the same Ignore references to a media server on a different host Problem report for Technical Support Fill out the following information before you contact support to report a problem Date Record the following product platform and device information m Product and its release level m Server hardware type and operating system level 15 16 Introduction Problem report for Technical Support m Client hardware type and operating system level if a client is involved m Storage units being used if it is possible that storage units are involved m If it looks like a device problem be ready to supply the following device information The types of robots and drives and their version levels along with Media and Device Management and system configuration information m Software patches to the products that were installed m The service packs and hotfixes that were installed Define the problem What were you doing when the problem occurred for
211. l Windows operating system perform the Express install During the installation do the following tasks m Partition the disk as it was before the failure if partitioning is necessary Then reformat each partition as it was before the failure m Install the operating system in the same partition that was used before the failure m Specify the default workgroup Do not restore to the domain m Follow any hardware manufacturers instructions that apply Reboot the system when the installation is complete 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 that was used before the failure Also it 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 accessible from the Windows Control Panel Install NetBackup client software Refer to the NetBackup Installation Guide for Windows for instructions Ensure that you specify the correct names for the client server and master server m Tospecify the client name start the Backup Archive and Restore interface on the client and click NetBackup Client Properties on the File menu Enter the client name on the General tab of the NetBackup Client Properties dialog m To specify the server name click Specify NetBackup Ma
212. l overview 239 Backups and archives UNIX clients Figure A 1 Backup or archive to tape or disk Master server NetBackup Configuration File Poli Database Database oley Managemen NetBackup Command bprd user interface line EMM Database bpdbm Chbproxy nbp Bpbackup or bparchive Description later in this chapter Itid is for tape backup only If the media server is backing up itself server and client on same host there is no bptm child bpbkar sends the data directly to shared memory Table A 1 shows the sequence of operation of a backup process Table A 1 Backup to tape or disk sequence of operation Start up script Launches bprd on the master server and 1t id on the master server and all media servers All other daemons and programs are started as necessary including nbpem nbjm nbrb and nbemm 240 Backup and restore functional overview Backups and archives UNIX clients Table A 1 Backup to tape or disk sequence of operation continued Policy execution Gets the policy list from bpdbm manager service Creates a policy client task for all policy client combinations nbpem specified in the policy list Computes the due time for each policy client task policy priority is honored for internal processing Submits to nbjm all jobs as policy client tasks become due When a job finishes it recomputes the due time of that policy client task Job manager service Iss
213. legacy log directory on the server 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 logs for the bpbackup bparchive bplist and bprestore commands on the client can be useful Also check the bpj ava msvc and bpjava usve logs jnbSA A Java based administration utility for managing NetBackup 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 On a 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 bpj ava msvc and bpjava usve can be helpful Table A 4 Backup and restore functional overview 279 NetBackup programs and daemons NetBackup daemons and programs continued nbemm On the server that is defined as the EMM server nbemm manages devices media and storage unit configuration and performs resource selection Replaces vmd as the device allocator Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbemmm terminate Debug Log On the server usr openv 1ogs UNIX or install_path logs Windows See About unified logging
214. les and RolloverMode are included in the output vxlogcfg 1 o nbrb p NB Configuration settings for originator 118 of product 51 216 LogDirectory usr openv logs DebugLevel 5 Diagnostichevel 5 LogToStdout False LogToStderr False LogToOslog False RolloverMode FileSize MaxLogFileSizeKB 5120 RolloverPeriodInSeconds 43200 RolloverAtLocalTime 0 00 NumberOfLogFiles 4 Control the number of log files You can use the vxlogmgr command with the vxlogcfg command s NumberOfLogFiles option to manually delete log files For example you currently have 10 unified logging files and the NumberOfLogFiles option is set to 2 Enter the following to keep the two most recent log files and delete the rest for all originators vxlogmgr a d The following command keeps the two most recent log files of all PBX originators vxlogmgr a d p ics The following deletes log files for the nbrb service only vxlogmgr a d o nbrb 124 Using logs About legacy logging Table 3 10 Example uses of the vxlogcfg command continued Control disk space Periodically run the vxlogmgr a command such as through a usage cron job to delete logs and monitor the disk space that unified logging uses The disk space that a given originator uses can be calculated as follows NumberOfFiles for originator MaxLogFileSizeKB for originator The total disk space that unified logs consume is the s
215. lic read write and run permissions user_ops contains a directory for every user that uses the Java programs In addition on NetBackup Java capable platforms the NetBackup Java interface log files are written in a subdirectory that is called nbj logs All files inthe user_ops directory hierarchy are removed according to the setting of the KEEP_LOGS_DAYS configuration option About global logging levels The logging level determines how much information is included in the log message The log range is 0 5 The higher the level number the greater the amount of detail is in the log message The following table describes the detail that each level includes Table 3 17 Global logging levels 0 Includes very important low volume diagnostic messages and debug messages Adds verbose diagnostic messages and debug messages Adds the progress messages Using logs About global logging levels Table 3 17 Global logging levels continued 3 Adds the informational dumps 4 Adds the function entry and exits 5 Includes everything The finest detail Unified logging is enabled by default to log debug messages at level 0 and application messages at level 5 The following actions affect logging levels m Inthe Global logging level list a zero 0 level specifies the minimum level of logging for both legacy and unified logging However for diagnostic and debug messages in unified logging the logging
216. licy The import copy may specify a storage unit group or a storage unit but not Any Available m The storage lifecycle policy in the target domain must have at least one copy that specifies the Remote Retention type Troubleshooting duplication to remote master jobs The duplication to remote master job works like any duplication job except that the duplication to remote master job contains no write side The job must run on a media server running NetBackup 7 1 or higher It consumes a read resource from the disk volume that the duplicated images reside on If no media server is available with NetBackup 7 1 or higher the job fails with status 800 The duplication to remote master job works at a disk volume level Within the storage unit specified in the storage lifecycle policy for the source copy some disk volumes may not support replication and some media servers may not be running NetBackup 7 1 or higher Use the Disk Pools interface of the System Administration Console to verify that the image is on a disk volume that supports replication If the interface shows that the disk volume is not a replication source click Update Replication to update the disk volumes in the disk pool If the problem persists check your disk device configuration The following procedure is based on NetBackup that operates in an OpenStorage configuration This configuration communicates with an media server deduplication pool MSDP that uses the duplication to
217. lity NBCC Cleaning up output files The results are located in the output nbsu lou4 master 20070409 160403 directory See About the NetBackup support utility nbsu on page 155 See Output from the NetBackup support utility nbsu on page 157 About the NetBackup consistency check utility NBCC The NetBackup consistency check utility Necc is a command line utility It is used to analyze the integrity of portions of the NetBackup configuration and catalog and database information as they pertain to tape media This analysis includes review of NetBackup storage units the EMM server volume pools tape media and backup images that are associated with tape media nBcc does the following m Queries the EMM database to obtain the primary hostname associated hostnames and server attributes for hostname normalization m Through examination of the NetBackup configuration identifies cluster application cluster and servers m Gathers database and catalog information m Analyzes the consistency of the gathered configuration and database and catalog information m Creates a packaged bundle for Symantec technical support to review nBcc resides in the following location UNIX usr openv netbackup bin support NBCC Windows install_path NetBackup bin support NBCC exe Symantec recommends that you run necc in the following circumstances m To check the consistency of the NetBackup configuration and catalog and data
218. log 16 4 10797 1 cacao bush nbpem backup of client bush exited with status 71 The definition of each value is as follows left to right m Severity 16 Error m Type 4 Backup m JobID 10797 Job group ID 1 Using logs 145 Troubleshooting error messages in the NetBackup Administration Console for UNIX m Server cacao m Client bush m Process nbpem m Text backup of client bush exited with status 71 Troubleshooting error messages in the NetBackup Administration Console for UNIX Most error messages in the NetBackup Administration Console for UNIX appear in the following locations m An attention dialog box m Anerror message pane in the lower right area of the console If the errors appear elsewhere they are Java exception errors They may appear in the status line bottom of the NetBackup Administration Console window They also may appear in the log file that contains the stdout or the stderr messages that the Java APIs or the NetBackup Administration Console write Symantec does not document Java exception errors Four types of error messages appear in the NetBackup Administration Console NetBackup status The operations that are performed in the NetBackup codes and messages Administration Console can result in errors that are recognized in other parts of NetBackup These errors usually appear exactly as documented in the NetBackup status codes and messages Note A status code does not always accompany
219. logs Windows See About unified logging on page 102 nbftsrvr Ona media server that is enabled for SAN Client backup over fibre channel nbftsrvr does the following reads the backup image from nbftclnt and transfers it to shared memory on the media server Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbftsrvr terminate Debug Log On the server usr openv 1logs UNIX or install_path logs Windows See About unified logging on page 102 nbjm On master servers the nbjm service accepts job requests from nbpem and from media commands such as bplabel and tpreq nbjm acquires job resources from nbrb and runs the jobs once resources are available Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbjm terminate Debug Log On the server usr openv 1logs UNIX or install_path logs Windows See About unified logging on page 102 NBNWNT EXE For NetWare nontarget clients NBNWNT EXE 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 Table A 4 Backup and restore functional overview 281 NetBackup programs and daemons NetBackup daemons and programs continued nbpem On master servers the nbpem service uses nbproxy to get the polic
220. m a backup To recover relational database files from an online catalog backup 1 If NetBackup is running stop it On UNIX and Linux usr openv netbackup bin bp kill all On Windows install _path NetBackup bin bpdown Move the following set of existing database files from their current location to a temporary directory NBDB nbdb db nbdb log emm_index db emm_data db BMRDB bmrdb db bmrdb log Change databases conf so SQL Anywhere does not try to automatically start them when the server is started On UNIX and Linux usr openv db bin nbdb admin auto_start NONE On Windows install_path NetBackup bin nbdb_admin auto_start NONE Start the SQL Anywhere server UNIX and Linux usr openv netbackup bin nbdbms_ start_stop start Windows install _path NetBackup bin bpup e SQLANYs VERITAS NB Disaster recovery 221 How to recover a catalog from a backup Re create an empty database UNIX and Linux usr openv db bin create_nbdb drop Windows install _path NetBackup bin create nbdb drop If the database has been moved or the environment is clustered add staging staging dirto the end of the create _nbdb command line If the database has been moved or the environment is clustered and space constraints force you to create this temporary database in the final location use the following command UNIX and Linux usr openv db bin create nbdb drop data lt data_dir gt index lt index dir gt tlog
221. m that were issued during the messages froma specific time period specified time period vxlogview o nbpem b 05 03 05 06 51 48 AM e 05 03 05 06 52 48 AM Display results faster You can use the i option instead of o to specify an originator vxlogview i nbpem The vxlogview i option searches only the log files that the specified process nbpem creates 116 is the originator ID of these files in the log file name By limiting the log files that it has to search vx logview returns a result faster By comparison the vxlogview o option searches all unified log files for the messages that the specified process are logged by Note If you use the i option with a process that is not a service vxlogview returns the message No log files found A process that is not a service has no originator ID in the file name In this case use the o option instead of the i option Typically the NetBackup process is a service if it appears in the Activity Monitor of the NetBackup Administration Console under the Daemons tab UNIX or Services tab Windows 119 120 Using logs About unified logging Table 3 8 Example uses of the vxlogview command continued Search for a job ID You can search the logs for a particular job ID vxlogview i nbpem grep jobid job_ID The j obid search key should contain no spaces and must be lowercase When searching for a job ID you can use any vxlogview command option T
222. mat to use with NetBackup commands Using the date format mm dd yyyy Building EMM host configuration information Obtaining EMM server aliases Building NetBackup storage unit list 10 Using NetBackup utilities 165 About the NetBackup consistency check utility NBCC Analyzing EMM master and or media servers and configured Storage Units Obtaining NetBackup unrestricted media sharing status Configuration state NO Obtaining NetBackup Media Server Groups No Server Groups configured Building NetBackup retention level list Obtaining NetBackup version from media servers Gathering required NetBackup catalog information Start time 2010 10 18 10 19 06 Gathering NetBackup EMM conflict table list Found 0 EMM conflict records Gathering list of all tapes associated with any Active Jobs Building NetBackup bpdbjobs list No active jobs found Building NetBackup Image database contents list Found 30391 images in the Image database Building EMM database Media and Device configuration attribute lists Found 207 media records in the EMM database Building EMM database Unrestricted Sharing Media attribute lists Found 0 Unrestricted Sharing media records in the EMM database Building the EMM database Volume attribute list Found 321 Volume attribute records in the EMM database Building NetBackup volume pool configuration list EMM Server hostname Building NetBackup scratch pool configuration list EM
223. mmunication problems with UNIX clients on page 41 See Resolving network communication problems with PC clients on page 48 Troubleshooting configuration problems Use the following steps to check for problems after an initial installation or after changes are made to the configuration 28 Troubleshooting procedures Troubleshooting configuration problems Table 2 4 Steps for troubleshooting configuration problems Step 1 Check for device Check for the following device configuration problems care m Configuration for robotic drive does not specify the robot peer m Drive is configured as wrong type or density m Incorrect Robotic Drive Number m SCSI ID for the robotic control is specified instead of the logical Robot Number that is assigned to the robot m The same robot number is used for different robots m SCSIID for the drive is specified instead of a unique Drive Index number m A platform does not support a device or was not configured to recognize it m Robotic device is not configured to use LUN 1 which some robot hardware requires m On UNIX drive no rewind device path is specified as a rewind path m On UNIX tape devices are not configured with Berkeley style close NetBackup requires this feature which is configurable on some platforms Further explanation is available m On UNIX tape devices other than QIC are not configured as variable mode NetBackup requires this feature which is co
224. much information is included in the log message The log range is 0 5 The higher the level number the greater the amount of detail is in the log message To change the logging level 1 6 In the NetBackup Administration Console in the left pane expand NetBackup Management gt Host Properties Select Master Servers Media Servers or Clients In the right pane click the server or client to view the version and platform Then double click to view the properties In the properties dialog box in the left pane click Logging In the Global logging level list select a value from 0 to 5 Changes affect the logging level of both unified logging and legacy logging See About global logging levels on page 138 Click OK See Changing the logging level on Windows and NetWare clients on page 140 See About global logging levels on page 138 Changing the logging level on Windows and NetWare clients You can increase the amount of information that client processes write in the logs To change the logging level on Windows clients 1 5 In the NetBackup Administraion Console on the File menu click Backup Archive and Restore In the Backup Archive and Restore interface on the File menu click NetBackup Client Properties In the NetBackup Client Properties dialog box select the Troubleshooting tab In the Verbose property field enter a debug level from 0 to 5 Use the default level of 0 unless
225. n is available on NetBackup media selection for nonrobotic drives See the NetBackup Administrator s Guide Volume II Note On UNIX systems when a tape is being mounted the drive_mount_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 Figure B 2 shows an example of the media and device management process User Media and device management functional description 291 Shared Storage option management process Figure B 2 Media and device management example process Request tape mount Backup and archive processes Database bptm Device monitor Device management utility Media management utility EMM Inventory barcodes or inject eject SDLT600 LTO 3 toot Non robotic Robotic drives control Tape library TL8 Shared Storage option management process Shared Storage Option SSO is an extension to tape drive allocation and config
226. n bash enter the following export TMPDIR tmp nbcplogs f In bin csh or bin tcsh enter the following nbcplogs tmpdir tmp f HF This utility supports three types of search algorithms These are command options that are part of the nbcplogs command line Using NetBackup utilities 171 About the nbcplogs utility m filecopy File copy is the default condition It copies the entire log file File copy with compression is usually enough to get the job done m fast Fast search uses a binary search to strip out lines that are outside the time frame of the file This mechanism is useful when copying extremely large log files such as bpdbm This option is rarely needed and should be used with caution The default condition is the file copy which copies the entire log file A fast search algorithm uses a binary search to strip out lines that are outside the time frame of the file This mechanism is useful when copying extremely large log files such aS bpdbm The nbcplogs utility is intended to simplify the process of copying logs by specifying the following options m Atime frame for the logs m The log types that you want to collect m Bundling and in transit data compression In addition you can preview the amount of log data to be copied More information on the nbcplogs utility is available in the NetBackup Commands Reference Guide manual 172 Using NetBackup utilities About the nbcplo
227. nally NBCCR performs up to three steps of repair for every repair entry in the SRA file An element may be modified to enable the repair and steps may be necessary after the repair If the repair fails during the repair operation NBCCR tries to roll back the repair so that the corrective action does not introduce any new errors NBCCR resides in the following location UNIX usr openv netbackup bin support NBCCR Windows install_path NetBackup bin support NBCCR exe NBCCR accepts one input file creates two output files and uses one temporary file Input file NBCCR accepts as input the Suggested Repair Action SRA file named mastername NBCCA_timestamptxt Technical Support analyzes the NBCC support package and generates this file which is sent to the end user This file is placed in the following directory for NBCCR processing On Unix usr openv netbackup bin support input nbccr SRA On Windows install_path NetBackup bin support input nbccr SRA Output files Temporary file Using NetBackup utilities About the NetBackup consistency check repair NBCCR utility NBCCR automatically creates a separate directory for each SRA file processed The file name is based on the contents of the SRA file The name of the directory is as follows On UNIX usr qpenv nethackup bin sugeort output rbocr mastemame nbocr timestamp On Windows install_path NetBackup bin support output nbecr ynastername_nbccr_timestamp After rep
228. nd configure the recovery device in NetBackup See the NetBackup Administrator s Guide Volume I Use the NetBackup command tpautoconf to discover and configure the recovery device in NetBackup See the NetBackup Commands Reference Guide manual Update the device mapping files See the NetBackup Administrator s Guide Volume I If you must restore from the policy backups or catalog backups that were done to media the appropriate media may have to be configured in NetBackup See the NetBackup Administrator s Guide Volume I When you configure the media you may have to do some or all of the following Manually load the required media into a stand alone recovery device Use the NetBackup utilities such as robtest or vendor specific robotic control software to load media into the required recovery devices Use the NetBackup Volume Configuration Wizard to inventory the media contents of a robotic device Use the vendor specific robotic control software to load the media into the required recovery devices Recover the NetBackup catalogs See How to recover a catalog from a backup on page 199 Disaster recovery 193 About disk recovery procedures for Windows 11 When catalog recovery is complete stop and restart the NetBackup services Use the following bpdown and bpup commands the Activity Monitor in the NetBackup Administration Console or the Services application in the Windows Control Panel install _path Ne
229. nd restore functional overview 261 Restore processes Figure A 13 SAN client restore with Fibre Transport NetBackup Command user interface line Master or media server Storage device tape or disk NetBackup tar UNIX TAR32 Windows Shared memory Shared memory Backup image sent over Fibre Channel The process flow for a SAN Client restore is as follows in the order presented m When the user starts a restore NetBackup invokes the client s bprestore program which sends a request to the request daemon bprd This request identifies the files and client The request daemon then uses bpca client daemon to start the backup and restore manager bpbrm Note To restore Backup Exec images bpbrm invoke mt frd instead of tar on the clients The server processes are the same as those used for NetBackup restores 262 Backup and restore functional overview Restore processes If the disk device or tape device on which the data resides attaches to the master server then bprd starts the backup and restore manager on the master server If the disk unit or tape unit connects to a media server bpra starts the backup and restore manager on the media server bpbrm starts bptm and provides bptm with the backup ID and the shmfat shared memory flag bptm does the following m Requests SAN Client information from nbjm m Sends a restore request t
230. ndows system directories include the registry which is needed to restore the client to its original configuration If you use a NetBackup exclude list for a client do not specify any Windows system files in that list Do not omit executables and other application files You may want to save tape by excluding these easy to reinstall files However backing up the entire application ensures that it is restored to its exact configuration For example if you have applied software updates and patches restoring from a backup eliminates the need to reapply them NetBackup Bare Metal Restore BMR protects client systems by backing them up with a policy configured for BMR protection A complete description of BMR backup and recovery procedures is available See the Bare Metal Restore System Administrator s Guide When you configure a policy for online catalog backup designate certain NetBackup policies as critical Critical policies back up systems and data deemed critical to end user operation During a catalog recovery NetBackup verifies that all of the media that is needed to restore critical policies are available If the configuration contains Windows clients that have incremental backup configurations set to Perform Incrementals Based on Archive Bit run a full backup of these clients as soon as possible after a catalog recovery The archive bit resets on the files that were incrementally backed up after the catalog backup that was used for t
231. nfigurable on some platforms When this condition exists you can frequently perform backups but not restores Further explanation is available See NetBackup status code 174 in the Status Codes Reference Guide m On UNIX pass through paths to the tape drives have not been established More description is available on device configuration problems See the NetBackup Device Configuration Guide Step 2 Check the daemons or Check for the following problems with the daemons or services services Daemons or services do not start during reboot configure system so they start Wrong daemons or services are started problems with media server start up scripts Configuration was changed while daemons or services were running On Windows the SystemRoot System32 drivers etc services file does not have an entry for vmd bprd bpdbm and bpcd Also ensure that the processes have entries for configured robots A list of these processes is available See the NetBackup Device Configuration Guide On UNIX the etc services file or NIS or DNS does not have an entry for vmd bprd bpdbm or robotic daemons Troubleshooting procedures 29 Device configuration problem resolution Table 2 4 Steps for troubleshooting configuration problems continued Step 3 Retry the operation If you found and corrected any configuration problems retry the operation and check for status and check for NetBackup status codes or messages in the foll
232. ng Windows clients ccccceceeceeeeceeeeeeeeeneeeeeeeeenes 263 Restoring NetWare Clients ceceeeeeeeeceeeneeneeeeeneeaeeneeneenes 264 Restoring catalog backups ccccceececeeeeeeeeeeeeeceeeeeeenenees 266 NetBackup directories and files cccceccecceeceeee eee eee eee eeneeneenees 267 NetBackup directory structure UNIX cceceeeeeceeeneeeeeneeeees 268 Contents of usr openv netbackup c ccccceeceeeee sensu sees 270 NetBackup programs and daemons ccececeeceeeeceeeeeeeeeaeeeenees 271 NetBackup Catalogs onnee e e i e a a a E 284 Media and device management functional aE a 84 8 E ees A A 287 Media and device management startup process s sssesesssresesseeee 287 Media and device management process ccceceececeeeceee tense eens 289 Shared Storage option management process 0ccececeeceeneeeeeees 291 Barcode Operations usione cesinta ne aa EO E TEEN EE TES 293 Media and device management components cceceeeeeeeeeeeees 295 Networks and hostnames s s s 305 Background for troubleshooting cceccecceeceeeeeeu eee eeu een eeneenees 305 Robotic test utilities wis cir bec tesincas dente ecat ead haossetoaet okt 311 About robotic test utilities 2 0 0 0 cece cece eee ee neces sete ee eeeeeeenenes 311 Robotic t sts on UNIX ernen ea E daseeeg cans eed da by eae Sete eee E 311 Robotic tests On Win
233. ng the gethostbyaddr network 306 Networks and hostnames Background for troubles hooting 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 on UNIX systems On Windows systems you must query the NetBackup Database Manager service The bpdbm process compares the peername to a list of client names that are generated from the following m Allclients for which a backup has been attempted m All clients in all policies The comparison is first a simple string comparison The comparison is verified by comparing hostnames and aliases that are retrieved by using the network function gethostbyname If none of the comparisons succeed a more brute force method is used which compares all names and aliases using gethostbyname The configured name is the first comparison that succeeds Note that other comparisons might also have succeeded if aliases or other network names are configured If the comparison fails the client s hostname as returned by the gethostname function on the client is used as the configured name An example of a failed comparison is when the client had changed its hostname but its new hostname is not yet reflected in any policies These comparisons are logged in the bpdbm debug log if vERBosE is set You can determine a
234. ning 1 On UNIX check for the PBX process ps grep pbx_exchange 2 To start PBX on UNIX type the following opt VRTSpbx bin vxpbx_exchanged start On Windows make sure the Symantec Private Branch Exchange service is started Go to Start gt Run and enter services msc Checking that PBX is set correctly Two settings are vital to the correct functioning of PBX Auth User authenticated user and Secure Mode When PBX is installed they are automatically set as required To check that PBX is set correctly 1 To display the current PBX settings do one of the following m On UNIX type the following opt VRTSpbx bin pbxcfg p Example output Auth User 0 root Secure Mode false Debug Level 10 Port Number 1556 PBX service is not cluster configured Auth User must be root and Secure Mode must be false m On Windows type the following install_path VxPBX bin pbxcfg p Example output Troubleshooting procedures 77 Resolving PBX problems Auth User 0 localsystem Secure Mode false Debug Level 10 Port Number 1556 PBX service is not cluster configured Auth User must be localsystem and Secure Mode must be false 2 Reset Auth User Or Secure Mode as needed m To add the correct user to the authenticated user list UNIX example opt VRTSpbx bin pbxcfg a u root m Toset Secure Mode to false opt VRTSpbx bin pbxcfg d m For more information on the pbxcfg command refer to the pbxcfg man page
235. nt integers 116 Using logs About unified logging constant strings and names of log fields that evaluate to a single value Expressions are grouped by logical operators such as AND and OR The supported relational operators are as follows lt less than gt greater than lt less than and equal to gt greater than and equal to equal to l not equal to The supported logical operators are as follows amp amp logical AND ia logical OR Table 3 6 shows data types for specific fields as well as description and an example When more than one example is listed both examples produce the same results Table 3 6 Data types for fields PRODID Integer or string Provide the product ID or the PRODID 51216 abbreviated name of product PRODID NBU ORGID Integer or string Provide the originator ID or the ORGID 1 abbreviated name of the ORGID VxAM component PID Long Integer Provide the process ID PID 1234567 TID Long Integer Provide the thread ID TID 2874950 STDATE Long Integer or Provide the start date in seconds or STDATE 98736352 string in the locale specific short date and time format For example a locale may have format mm dd yy hh mm ss AM PM STDATE AM 4 26 04 11 01 00 Table 3 6 Data types for fields continued Using logs 117 About unified logging ENDATE Long Integer or string Provide the end date in seconds or in the locale
236. ntec assumes that you recover to the original system disk or one configured exactly like it Warning NetBackup may not function properly if you reinstall and recover to a different partition or to one that is partitioned differently due to internal configuration information Instead configure a replacement disk with partitioning that is identical to the failed disk Then reinstall NetBackup on the same partition on which it was originally installed The specific procedures that replace failed disks build partitions and logical volumes and reinstall operating systems can be complicated and time consuming Such procedures are beyond the scope of this manual Appropriate vendor specific information should be referenced Recommended backup practices The following backup practices are recommended Selecting files to back up Bare Metal Restore Critical policies Full backup after catalog recovery Online catalog backups Online catalog backup disaster recovery files Disaster recovery Recommended backup practices In addition to backing up files on a regular basis it is important to select the correct files to back up Include all files with records that are critical to users and the organization 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 In addition to the other system software the Wi
237. nts 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 legacy log directory on the client BPSVR NLM On NetWare nontarget clients BPSVR NLM 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 Enter bpstart ncf Stopped By Enter bpstop ncf Debug Log SYS VERITAS NBUCLT NetBack logs bpsrv directory on the client BPSYS EXE On Windows clients BPSYS EXE is the NetBackup System Registry Replacement utility Started By NetBackup as required Stopped By Completion of operation Debug Log BPSYS legacy log directory on the client 278 Backup and restore functional overview NetBackup programs and daemons Table A 4 Backup daemons and programs continued bptm On master and media servers bptm manages both disk and tape backup and restore It is used when the storage unit type is either disk or Media Manager This program manages the transfer of images between the client and the storage device 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
238. nv volmgr debug help NetBackup _DeviceConfig_Guide tx misc vm conf2 Table B 1 describes the directories and files that are of special interest Table B 1 Media and device management directories and files bin Commands scripts programs daemons and files required for media and device management 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 SPARC only platforms goodies Contains vmconf script and scan utility debug Legacy debug logs for the Volume Manager daemon vmd and all requesters of vmd Itid and device configuration The administrator must create these directories for debug logging to occur help Help files used by media and device management programs These files are in ASCII format misc Lock files and temporary files required by various components of media and device management Media and device management functional description Media and device management components Table B 1 Media and device management directories and files continued vm conf Media and device management configuration options Table B 2 describes the media and device management 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
239. o the FT server process nbftsrvr m Sends a restore request to the FT Client process on the client nbftclnt nbftclnt opens a fibre channel connection to nbftsrvr on the media server allocates shared memory and writes shared memory information to the backup ID file bpbrm starts tar by means of bpcd and provides tar with the backup ID socket information and the shmfat shared memory flag bptm does the following m Reads the image from the storage device m Creates a bptm child process This process filters the backup image so that only the files that are selected for the restore are sent to the client m Writes the image data to the shared buffer on the server m When buffer is full or job is done sets buffer flag partial buffers may be sent to the client tar does the following m Sends the status and control information to bpbrm m Reads the shared memory information from the local backup ID file waits for the file to exist and become valid m Waits for the buffer flag that indicates the data is ready to be read m Reads data from the buffer extracts files and restores them When the shmfat shared memory flag is provided tar considers the data to be already filtered The FT Server process nbftsrvr waits for the shared memory buffer flag to be set nbftsrvr then transfers the image data to the FT Client nbftclnt shared memory buffer and clears the buffer flag The FT Client nbftclnt waits for the data f
240. o the shared memory buffer When the transfer completes nbftsrvr sets the buffer flag bptm waits for the shared memory buffer flag to be set writes data from the buffer to the storage device and clears the buffer flag At the end of the job m bpbkar informs bpbrm and bptm that the job is complete m bptm sends bpbrm the final status of the data write m bptm directs nbftclnt to close the fibre channel connection m nbftclnt closes the fibre channel connection and deletes the BID file Backup and restore functional overview 249 Backups and archives UNIX clients Backups and archives Windows NetBackup supports the same types of operations on Windows clients as it does on UNIX clients Figure A 5 shows the Windows client processes In this figure the following items applies m NBWINis the user interface program on the client The bpbackup function and the bparchive function are merged into NBWIN E BPINETD serves the same purpose as inetd on UNIX clients m The NetBackup client daemon is called Bpcp E BPBKAR32 serves the same purpose as bpbkar on UNIX clients The server processes are the same as described for UNIX Figure A 5 Backup and archive Windows clients Server Windows 2000 Client NetBackup User Backups and Archives UNIX Clients earlier in this chapter Interface I For details on the server processes see a BPINETD A Wh lafo BPCD CI Op Backy
241. ocation of 155 nbsu_info txt file 156 output files 157 progress display 160 troubleshooting 156 when to use 155 nbsu_info txt file 156 NBWIN 249 263 NBWIN EXE 282 ndmpagent overview 281 NearStore 253 NetBackup if unresponsive 69 product ID 105 NetBackup Administration Console debug logging 147 errors 145 NetBackup Client Service start and stop 25 NetBackup consistency check see NBCC 161 NetBackup Database Manager service start and stop 25 NetBackup Device Manager service start and stop 25 NetBackup Enterprise Media Manager service start and stop 25 NetBackup Job Manager service start and stop 25 NetBackup Policy Execution Manager service start and stop 25 NetBackup Request Manager service start and stop 25 NetBackup Resource Broker service start and stop 25 NetBackup Status Collection daemon See vmscd NetBackup Support Utility see nbsu 155 NetBackup Volume Manager service start and stop 25 network connections multiple 305 network daemon vnetd 128 network interface cards 91 network problems PC clients 48 UNIX clients 41 320 Index NIC cards and full duplex 91 NumberOfFiles 124 NumberOfLogFiles 123 133 0 obackup_tape log 135 odld description 298 odltest 312 off host backup 97 OpenStorage 177 187 operating system errors 146 originator IDs list of 106 originatorID unified logging 105 P patches installing during recovery 195 PBX Auth User 77 logging 77 Secure Mode 77 78 starting 76
242. ode The following procedure applies when the shared disk and at least one configured cluster node remain available To replace a failed node on a Windows cluster using VCS 1 2 Freeze the NetBackup service Ensure that the NetBackup shared disks are not mounted on the node on which NetBackup is to be installed Reinstall NetBackup on the new node or replacement node Be sure to use the NetBackup Virtual Name as the name of the NetBackup server Follow the instructions for installing the NetBackup server software Refer to the NetBackup Installation Guide Ensure that the node is a member of an existing cluster and that it performs the necessary configuration automatically Install any Maintenance Packs and patches that are required to bring the newly installed node to the same patch level as the other cluster nodes Unfreeze the NetBackup service and verify that it can be brought up on the replacement node 197 198 Disaster recovery About clustered NBU server recovery for Windows Recovering the shared disk on a Windows VCS cluster The following procedure is applicable in situations where the configured cluster nodes remain available but the NetBackup catalog database files or both on the shared disk have been corrupted or lost Check the following conditions before you proceed with this procedure m The shared storage hardware is restored to a working state so that the shared disk resource can be brought onl
243. ogged and cannot be disabled These messages are localized An example of an application message follows 05 02 10 11 02 01 717 Warning V 116 18 failed to connect to nbjm will retry Diagnostic log messages are the unified logging equivalent of the legacy debug log messages They can be issued at various levels of detail similar to verbose levels in legacy logging These messages are localized Diagnostic messages can be disabled with the vxlogcfg command An example of a diagnostic message follows 05 05 09 14 14 30 347 V 116 71 JobScheduler doCatIncr no configured session based incremental catalog schedules Debug log messages Using logs 105 About unified logging Debug log messages are intended primarily for Symantec engineering Like diagnostic messages they can be issued at various levels of detail These messages are not localized Debug messages can be disabled with the vxlogcfg command An example of a debug message follows 10 29 09 13 11 28 065 taolog TAO 12066 1 Transport Cache Manager bind_i Oxffbfcl94 gt 0x7179d0 Transport 12 File name format for unified logging Unified logging uses a standardized naming format for log files The following is an example of a log file name usr openv logs nbpem 51216 116 2201360136 041029 0000000000 1log Table 3 1 describes each part of the log file name Table 3 1 Description of the file name format for unified logging 51216 Pro
244. ograms and the sequence in which they execute during backup and restore operations The databases and the directory structure of the installed software are also described Note that this appendix does not describe the NetBackup products for backing up relational databases such as NetBackup for ORACLE The guides for those products have information regarding their operation 236 Backup and restore functional overview Backup and restore startup process Backup and restore startup process When the NetBackup master server starts up a script automatically starts all services daemons and programs that are required by NetBackup The start up commands that are used by the script vary according to the platform The same is true on a media server NetBackup automatically starts additional programs as required including robotic daemons For more information see the following topic Information is available on SAN client and Fibre Transport startup processes See the NetBackup Shared Storage Guide Note No daemons or programs need to be explicitly started The necessary programs are started automatically during the backup or restore operation A daemon that executes on all servers and clients is the NetBackup client daemon bpcd On UNIX clients inetd starts bpcd automatically so no special actions are required On Windows clients bpinetd performs the same functions as inetd Netware clients do not use inetd or bpinetd but are conf
245. ogs m The unified logging files that the Bare Metal Restore process bmrsavecfg creates About using the vxlogview command to view unified logs Use the vxlogview command to view the logs that unified logging creates These logs are stored in the following directory UNIX usr openv logs Windows install_path logs Unlike the files that are written in legacy logging unified logging files cannot be viewed with a text editor The unified logging files are in binary format and some of the information is contained in an associated resource file Only the vxlogview command can assemble and display the log information correctly You can use vxlogview to view NetBackup log files as well as PBX log files To view PBX logs using the vxlogview command do the following m Ensure that you are an authorized user For UNIX and Linux you must have root privileges For Windows you must have administrator privileges m Specify the PBX product ID by entering p 50936 as a parameter on the vxlogview command line About query strings used with the vxlogview command Use the vxlogview command to display the logs that unified logging generates The vxlogview command includes the following option w where QueryString QueryString represents a text expression similar to a database WHERE clause The query string expression is used to retrieve log entries from the unified logging system The expression is a combination of relational operators consta
246. on gathered by the NetBackup support utility nbsu You can use nbsu to gather diagnostic information about certain NetBackup or Media Manager status codes nbsu gathers this information by running one or more NetBackup commands whose output may indicate the cause of the problem You can get more information about the commands that nbsu runs by looking under Recommended Actions for the topics that describe the status codes See the Status Codes Reference Guide See nbsu in the Commands Reference Guide The following are examples of the results you can get when you enter specific commands To gather diagnostic information about Enternbsu nbu_e 25 status code 25 This command runs only the diagnostic commands that are related to NetBackup status code 25 Since fewer commands are run the result may be a smaller set of output files To determine what information nosu Enter nbsu 1 nbu_e 25 can collect for a particular status code You can get more information about the output files that nbsu generates See Output from the NetBackup support utility nbsu on page 157 160 Using NetBackup utilities About the NetBackup support utility nbsu Note You can also use a NetBackup exit script to call nbsu The script passes the NetBackup status code to nbsu to gather associated diagnostics for a job Example of a progress display for the NetBackup support utility nbsu By default the NetBackup support utilit
247. on problems with PC clients The following procedure is for resolving NetBackup communications problems such as those associated with NetBackup status codes 54 57 and 58 This procedure consists of two variations one for UNIX clients and another for PC clients Note In all cases ensure that your network configuration works correctly outside of NetBackup before trying to resolve NetBackup problems This procedure helps you resolve network communication problems with PC clients To resolve network communication problems 1 Before you retry the failed operation do the following m Increase the logging level on the client see the client s user guide m On the NetBackup server create a bprd debug log directory and on the clients create a bpcd debug log m On the NetBackup server set the Verbose level to 1 See Changing the logging level on Windows and NetWare clients on page 140 2 If this client is new verify the client and the server names in your NetBackup configuration See Verifying host name and service entries in NetBackup on page 52 3 Verify basic network connectivity between client and server by pinging from the server to the client and vice versa Use the following command Troubleshooting procedures Resolving network communication problems with PC clients ping hostname Where hostname is the name of the host as configured in the following m NetBackup policy configuration m
248. onitors the NetBackup services and attempts to restart a service that unexpectedly terminates 166 NetBackup Vault 178 Disk Service Manager DSM which performs set and get operations on disk storage and disk storage units 199 nbftsrvr FT Server process Part of SAN Client 200 nbftclnt FT Client process Part of SAN Client 201 FT Service Manager FSM component of the Enterprise Media Manager EMM for SAN Client 210 Exchange Firedrill Wizard for NetBackup clients 110 Using logs About unified logging Table 3 2 Originator IDs for the server processes that use unified logging continued 219 The Resource Event Manager REM is a CORBA loadable service that runs inside nbemm REM works with the Disk Polling Service to monitor free space and volume status and to watch for disk full conditions 220 Disk polling service for NetBackup clients 221 The Media Performance Monitor Service MPMS This service runs on every media server within RMMS and gathers CPU load and free memory information for the host 222 Remote monitoring and Management Service RMMS which is the conduit through which EMM discovers and configures disk storage on media servers 226 libssmgr Storage lifecycle manager Controls the lifecycle image duplication operations 230 The Remote Disk Service Manager interface RDSM that runs within the Remote Manager and Monitor S
249. ons that write the logs See About backup and restore functional overview on page 235 On UNIX systems also refer to the README file in the usr openv netbackup logs directory Directory names for legacy debug logs for media and device management The debug log directories enable logging for the media management processes and device management processes Table 3 14 describes the directories you need to create to support legacy debug logs for media and device management Each directory corresponds to a process Table 3 14 Media and device management legacy debug logs acsssi UNIX only Debug information on transactions between NetBackup and the Storage Tek ACSLS server daemon Debug information for vmd NetBackup Volume Manager service Windows and its associated processes oprd and rdevmi Stop and restart vmd after creating the directory ltid Debug information on 1tid the Media Manager device daemon UNIX or on the NetBackup Device Manager service Windows and on avrd Stop and restart 1tid after creating the directory reqlib Debug information on the processes that request media management services from vmd or EMM Stop and restart vmd after creating the directory robots Debug information on all robotic daemons which includes t1dcd tl8cd and tl4d daemons Stop and restart robotic daemons tpcommand Debug information for device configuration including the tpconfig and the tpautoconf commands
250. ooting installation problems continued Step 2 Determine if you can install NetBackup client software on the clients Note Before you install or use NetBackup on a Linux client verify that the inetd or xinetd service is started on that computer This service ensures proper communication between the NetBackup master and the Linux client Note You cannot install PC client software from a UNIX NetBackup server Do the following m For an install to a trusting UNIX client verify the following m The correct client name is in your policy configuration m The correct server name is in the client rhosts file If the installation hangs check for problems with the shell or the environment variables for the root user on the client The files that you check depend on the platform operating system and shell you use For example your login ona Sun system runs an stty suchas stty erase before it defines your terminal type If this action causes the install process to hang you can modify the login file to define the terminal before you run the st ty Or move the client login to another file until the install is complete m Foran installation to a secure UNIX client check your ftp configuration For example you must use a user name and password that the client considers valid Step 3 Resolve network problems Determine if the problem is related to general network communications See Resolving network co
251. or bpbrm and bptmor bpdm on the media server and for bpbkar on the client For best results set the verbose logging level to 5 Enable debug logging for the following bpdbm and bprd on the master server and for bpcd on all servers and clients in addition to the processes already identified See backuptrace in the Commands Reference Guide 151 152 Using NetBackup utilities About the analysis utilities for NetBackup debug logs Table 4 2 Analysis utilities for NetBackup debug logs continued bpgetdebuglog A helper program for backuptrace and restoretrace It can also be useful as a stand alone program and is available for all NetBackup server platforms bpgetdebuglog prints to standard output the contents of a specified debug log file If only the remote machine parameter is specified bpgetdebuglog prints the following to standard output the number of seconds of clock drift between the local computer and the remote computer See bpgetdebuglog in the Commands Reference Guide duplicatetrace Consolidates the debug logs for the specified NetBackup duplicate jobs and writes them to standard output It sorts the messages by time duplicatetrace attempts to compensate for time zone changes and clock drift between remote servers and clients At a minimum you must enable debug logging for admin on the master server and for bptm or bpdm on the media server For best results set the verbose logging level to 5 and enable debug logging f
252. or testing the master server and clients Enable the appropriate debug logs on the master server See About logs on page 99 See About unified logging on page 102 See About legacy logging on page 124 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 Step 2 Configure a test policy Configure a test policy and set the backup window to be open while you test Name the master server as the client and a storage unit that is on the master server preferably a nonrobotic drive Also configure a volume in the NetBackup volume pool and insert the volume in the drive If you don t label the volume by using the bp1labe1 command NetBackup automatically assigns a previously unused media ID Step 3 Verify the daemons and services To verify that the NetBackup daemons or services are running on the master server do the following m Tocheck the daemons on a UNIX system enter the following command usr openv netbackup bin bpps a m Tocheck the services on a Windows system use the NetBackup Activity Monitor or the Services application of the Windows Control Panel Step 4 Backup and restore a policy Start a manual backup of a policy by using the manual backup option in the NetBackup administration interface Then restore the backup These actions verify the following m NetBackup server softwa
253. or the following bpdbm on the master server and bpcd on all servers and clients in addition to the processes already identified See duplicatetrace in the Commands Reference Guide importtrace Consolidates the debug log messages for the specified NetBackup import jobs and writes them to standard output It sorts the messages by time importtrace attempts to compensate for time zone changes and clock drift between remote servers and clients At a minimum you must enable debug logging for admin on the master server And for bpbrm you must enable debug logging for bptmand tar on the media server For best results set the verbose logging level to 5 and enable debug logging for the following bpdbm on the master server and bpcd on all servers and clients in addition to the processes already identified See importtrace in the Commands Reference Guide restoretrace Copies to standard output the debug log lines relevant to the specified restore jobs The restoretrace utility consolidates the debug logs for specified NetBackup restore jobs The utility writes debug log messages relevant to the specified jobs to standard output and sorts the messages by time restoretrace attempts to compensate for time zone changes and clock drift between remote servers and clients The format of the output makes it relatively easy to sort or grep by timestamp program name and server or client name At a minimum you must enable debug logging for bprd on th
254. ord this information for each try Compare the results of multiple tries A record of tries is also useful for others at your site and for Technical Support in the event that you cannot solve the problem You can get more information about logs and reports See About logs on page 99 Table 1 1 Step 4 Correct the problem Introduction Problem report for Technical Support Steps for troubleshooting NetBackup problems continued After you define the problem use the following information to correct it m Take the corrective action recommended by the status code or message See the Status Code Reference Guide m If no status code or message exists or the actions for the status code do not solve the problem use additional troubleshooting procedures to isolate common problems See Troubleshooting NetBackup problems on page 20 Step5 Complete a problem report for Technical Support If your troubleshooting is unsuccessful prepare to contact Technical Support by filling out a problem report See Problem report for Technical Support on page 15 See About gathering information for NetBackup Java applications on page 17 On UNIX systems the usr openv netbackup bin goodies support script creates a file containing data necessary for Technical Support to debug any problems you encounter For more details consult the usage information of the script by using support h Step6 Contact Technica
255. ormation and transmits it to bplist on the client Figure A 10 Master Server File Database query bpdbm File list List operation UNIX and Linux client NetBackup User Interface Command line I l UNIX Client Refer to one of the following topics as you read through the restore process See Figure A 11 on page 259 See Figure A 12 on page 260 The following are the processing steps in a restore in the order presented m When the user starts a restore NetBackup invokes the client s bprestore program which sends a request to the request daemon bprd This request identifies the files and client The request daemon then uses bpca client daemon to start the backup and restore manager bpbrn Note To restore Backup Exec images bpbrm initiates mt fra instead of tar on the clients The server processes are the same as those used for NetBackup restores If the disk device or tape device on which the data resides attaches to the master server the following occurs bprd starts the backup and restore manager on the master server If the disk unit or tape unit connects to a media server bprd starts the backup and restore manager on the media server The backup and restore manager starts bptm and uses the client daemon bpcd to establish a connection between the NetBackup tar program on the client and bptm on the server 258 Backup and restore functional overview
256. ormation is available about configuring catalog backups and system backup policies in a clustered environment Refer to topics about configuring NetBackup in the NetBackup High Availability Guide Warning Before attempting any of the recovery procedures in this topic contact technical support Replacing a failed node on a UNIX or Linux cluster Cluster technology specific information is available about how to bring the NetBackup resource group online and offline Also information about how to freeze and unfreeze that is disable and enable monitoring for the NetBackup Resource group Refer to topics about configuring NetBackup in the NetBackup High Availability Guide The following procedure applies when the shared disk and at least one configured cluster node remain available 184 Disaster recovery About clustered NBU server recovery for UNIX and Linux To replace a failed node on a UNIX or Linux cluster 1 10 11 12 13 Configure the hardware system software and cluster environment on the replacement node Verify that the device configuration matches that of the surviving nodes Ensure that the NetBackup Resource group is offline on all nodes before installing NetBackup on the replacement node Ensure that the NetBackup shared disks are not mounted on the node on which NetBackup is to be installed Freeze the NetBackup service Reinstall NetBackup on the new mode or replacement node Be sure to use
257. ots If any of these processes are not running stop the device daemon 1tia by running the following command usr openv volmgr bin stopltid To verify that the 1tid avra and robotic control daemons are stopped run the following command usr openv volmgr bin vmps If you use ACS robotic control the acsssi and the acsse1 daemons may continue to run when 1tid is terminated Stop any robot control daemons that may continue to run by entering the following command usr openv netbackup bin bp kill all Then start all daemons by running the following command usr openv volmgr bin 1tid For debugging start 1tid with the v verbose option Verifying that all processes are running on Windows servers Use the following procedure to make sure that all the processes that need to run on Windows server are actually running Table 2 2 Troubleshooting procedures 25 Troubleshooting NetBackup problems Steps to ensure that all necessary processes are running on Windows servers Step 1 Start all services The following services must be running If these services are not running start them by using the NetBackup Activity Monitor or the Services application in the Windows Control Panel To start all of the services run install_path NetBackup bin bpup exe Services on master servers NetBackup Request Manager service NetBackup Policy Execution Manager service NetBackup Job Manager service NetBackup database manager
258. ou suspect a communications problem between the master between the master server and the media server and the media servers check the debug logs for the pertinent servers processes If the debug logs don t help you check the following m Ona UNIX server the System log m Ona Windows server the Event Viewer Application and System log m vmd debug logs Table 2 7 Step 6 Troubleshooting procedures 39 Testing the media server and clients Steps for testing the media server and clients continued Ensure that the hardware runs correctly For the failures that relate to drives or media ensure that the drive is running and that the hardware functions correctly See the vendor manuals for information on hardware failures If you use a robot in an initial configuration condition verify that the robotic drive is configured correctly In particular verify the following m The same robot number is used both in the Media and Device Management and storage unit configurations m Each robot has a unique robot number On a UNIX server you can verify only the Media and Device Management part of the configuration To verify use the tpreq command to request a media mount Verify that the mount completes and check the drive on which the media was mounted Repeat the process until the media is mounted and unmounted on each drive from the host where the problem occurred Perform these steps from the
259. oup on each node in turn and run the Device Configuration Wizard to configure the devices Configuration information on your cluster MSCS or VCS is available Refer to the NetBackup High Availability Guide How to recover a catalog from a backup This topic explains how to recover a catalog that was backed up using the online hot catalog backup method This method is described in the following manual 199 200 Disaster recovery How to recover a catalog from a backup See the NetBackup Administrator s Guide Volume I This procedure can be stand alone or part of a larger disk recovery procedure See one of the following topics See About disk recovery procedures for UNIX and Linux on page 176 See About disk recovery procedures for Windows on page 187 Note When any online catalog backup recovery try that involves media completes NetBackup changes the state of the media that contains the catalog backup to frozen This operation prevents a subsequent accidental overwrite action on the final catalog backup image on the media This final image pertains to the actual catalog backup itself and its recovery is not part of the catalog recovery You can unfreeze the media Note You must have root administrative privileges to perform these procedures You can recover the catalog in either of two ways m Recovering the entire catalog See When recovering the entire catalog from an online backup
260. ous executable binaries including the vnetd daemon and utilities for legacy enhanced authentication db Contains the NetBackup Relational Database Manager SQL Anywhere and database data file java Contains the NetBackup Java Administration Console and the Backup Archive and Restore user interface lib Contains shared libraries that are required for NetBackup operation logs Contains all logs that are written by unified logging You do not have to create subdirectories for these logs man Contains man pages for NetBackup commands msg Contains the message files and a configuration file for all installed languages of NetBackup NB Java tar Z A tar file that contains the NetBackup Java interfaces netbackup See Table A 3 on page 270 resources Contains the NetBackup message catalogs that are used by unified logging VxUL share Contains static configuration files These files are normally unchanged between NetBackup releases tmp sqlany Contains the NetBackup Relational Database Manager SQL Anywhere installation trace files and the log files regarding to database start and stop var Contains the variable configuration files These files which are related to licensing authentication authorization and networking may change while NetBackup is running usr openv var global contains various static and variable configuration files In a cluster the global directory is shared between nodes volmgr Contains the media and device manag
261. out global logging levels ccc ccc ec ceceecec eee eceee sense eeeeeneenenee Changing the logging level ccccceceec sence sence eeeeeeeeee enone Changing the logging level on Windows and NetWare Clients mesrine EEA Tap PaceDesesern Sack Cac IT Cage tes Logs to accompany problem reports for synthetic backups Setting retention limits for logs on clients ccccecceceeceeeeeeeees Logging options with the Windows Event Viewer sc0seeeees Troubleshooting error messages in the NetBackup Administration Console for UNIX eis ccc cciseteccsciages E EE Goscavecugeadea EEES About extra disk space required for logs and temporary FILES niece ceeds area AEREE EEEE EE A EE e Enabling detailed debug logging ccceceececeeceeeee tence eens Using NetBackup utilities 000 About NetBackup troubleshooting utilities 0 0 0 0 eee eeee eee nee ee About the analysis utilities for NetBackup debug logs 068 About network troubleshooting utilities ccccceceeeeceeeeeeee ees About the NetBackup support utility nbsu cece cee ee eee eens Output from the NetBackup support utility nbsu Status code information gathered by the NetBackup support utility MDS eesse n ea a aaa e Ra sexed Example of a progress display for the NetBackup support utility TAD SUD REITI E breaded nied Se T TANE EN AN SS PEA About the N
262. ow to start processes that may not be running To verify that all processes are running on UNIX servers 1 Tosee the list of processes daemons running on the server and on the Media Manager enter the following command usr openv netbackup bin bpps x 2 Ifthe master server is also the EMM server ensure that the nbemm and the nbrb services are running If neither service is running start them by entering the following two commands If only one of the services is running start the other service by using the appropriate command usr openv netbackup bin nbemm usr openv netbackup bin nbrb 3 The nbpem and the nbjm services must be running on the master server If neither service is running start them by entering the following two commands If only one of the services is running start the other service by using the appropriate command usr openv netbackup bin nbjm usr openv netbackup bin nbpem 4 If either the NetBackup request daemon bpra or database manager daemon opdbm is not running start them by entering the following command usr openv netbackup bin initbprd 24 Troubleshooting procedures Troubleshooting NetBackup problems Make sure that the following media and device management processes are running m 1tid needs to be running only if drives are configured on the server E vmd volume m avrd automatic volume recognition only if drives are configured on the server m Processes for all configured rob
263. owing codes and messages m 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 Often it provides specific information which is useful when the error can result from a variety of problems If the problem involved a backup or archive check the Status of Backups report This report gives you the status code If you find a status code or message in either of these reports perform the recommended corrective actions See the Status Codes Reference Guide m Check the system log on UNIX or the Event Viewer Application and System log on Windows if the following is true The problem pertains to media or device management and NetBackup does not provide a status code or you cannot correct the problem by following the instructions in the status codes m Check the appropriate enabled debug logs Correct any problems you detect If these logs are not enabled enable them before your next try See About logs on page 99 Step 4 Retry the operation If you performed corrective actions retry the operation If you did not perform and do additional corrective actions or the problem persists go to one of the following troubleshooting procedures See Resolving full disk problems on page 69 See Frozen media troubleshooting considerations on page 71 See About conditions that cause media to freeze on page 72 See Troubleshoo
264. p 5 Click Recover the Catalogs on the NetBackup Administration Console to start the Catalog Recovery Wizard NetBackup Catalog Recovery Wizard ised Welcome to the NetBackup gt Catalog Recovery Wizard This wizard guides you in recovering the NetBackup catalog from a hot online catalog backup To recover from a cold offline catalog backup use the bprecover command as described in the System Administrator s Guide Run this wizard only in the event of a disaster that requires the recovery of all or portions of the NetBackup catalog This should be run before starting any backups To begin click Next For assistance click Help cio ERS conc __ tele _ The Welcome panel appears Disaster recovery 203 How to recover a catalog from a backup 6 Click Next on the Welcome panel to display the Catalog Disaster Recovery File panel NetBackup Catalog Recovery Wizard x Catalog Disaster Recovery File Specify the location of your disaster recovery file Specify the full pathname to the disaster recovery file Browse G if the disaster recovery file is not available use the bpimport dfile command to read it from the catalog backup media See the documentation for further details Glick next to obtain the file This may take a long time vow _ Cmi tom This wizard relies on the disaster recovery information that is generated during the online catalog
265. p Volume Configuration Wizard to inventory the media contents of a robotic device m Use the vendor specific robotic control software to load the media into the required recovery device s 7 Recover the NetBackup catalogs to the server you are recovering The NetBackup catalogs can be recovered only to the same directory structure from which they were backed up alternate path recovery is not allowed 8 Stop and restart all NetBackup daemons Use the following NetBackup commands or use the Activity Monitor in the NetBackup Administration Console Your configuration may include an EMM server that is separate from the master server If so start NetBackup on the EMM server before starting NetBackup on the master server usr openv netbackup bin bp kill all usr openv netbackup bin bp start_all 9 Start the NetBackup Backup Archive and Restore interface or the bp command and restore other files to the server as desired When the files are restored you are done Recovering the master server when the root partition is lost The following procedure assumes that the root file system is lost along with everything else on the disk This procedure reloads the operating system to an alternate boot disk and boots from that disk during recovery This operation lets you recover the root partition without risking a crash that is caused by overwriting the files that the operating system uses during the restore 180 Disaster recovery Abo
266. p are available Refer to NetBackup Device Configuration Guide for information on how to create device files Testing the master server and clients If the NetBackup installation and configuration troubleshooting procedures do not reveal the problem perform the following procedure Skip those steps that you have already performed The procedure assumes that the software was successfully installed but not necessarily configured correctly If NetBackup never worked properly you probably have configuration problems In particular look for device configuration problems You may also want to perform each backup and restore twice On UNIX perform them first as a root user and then as a nonroot user On Windows perform them first as a user that is a member of the Administrators group Then perform them 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 The explanations in these procedures assume that you are familiar with the functional overview information See About backup and restore functional overview on page 235 Several steps in this procedure mention the All Log Entries report To access more information on this report and others refer to the following See the NetBackup Administrator s Guide Volume I Step 1 Table 2 6 Enable debug logs Troubleshooting procedures Testing the master server and clients Steps f
267. p database The information that is displayed on this panel depends on whether the recovery is from a full backup or an incremental backup If an online catalog backup policy includes both full backups and incremental backups the disaster recovery email may indicate either a full backup or an incremental backup for recovery An incremental backup recovery completely recovers the entire catalog because it references information from the last full backup You don t need to first recover the last full catalog backup then follow with subsequent incremental backups Disaster recovery 205 How to recover a catalog from a backup 8 When the required media sources are all found click Next to display the Disaster Recovery Method panel The Recover entire NetBackup catalog radio option is selected NetBackup Catalog Recovery Wizard xj Disaster Recovery Method Select one of the following recovery processes to recover the NetBackup catalog N CH This is the recommended method C Recover only NetBackup catalog image and configuration files Does not recover the NetBackup relational database click Help for details A For recovery of a 5x media server catalog see help for details To begin the restore click Next Once started it can not be canceled cto Cie coe te 9 With the Recover entire NetBackup catalog radio option selected click Next to initiate the recovery of the entire NetBackup catalog NetBackup res
268. p schedules for the master servers and media servers in your NetBackup installation These schedules protect the operating systems device configurations and other applications on the servers Master or media server recovery procedures when the system disk has been lost assume that the servers are backed up separately from the catalog backup Backups of master and media servers should not include NetBackup binaries configuration or catalog files or relational database data About disk recovery procedures for UNIX and Linux The three different types of disk recovery for UNIX and Linux are as follows Master server disk recovery procedures See Recovering the master server disk for UNIX and Linux on page 177 Media server disk recovery procedures Disaster recovery 177 About disk recovery procedures for UNIX and Linux See About recovering the NetBackup media server disk for UNIX and Linux on page 182 Client disk recovery procedures See Recovering the system disk on a UNIX client workstation on page 182 The disk based images that reside on AdvancedDisk or on OpenStorage disks cannot be recovered by means of the NetBackup catalog These disk images must be recovered by means of the NetBackup import feature For information on import See the topic on importing NetBackup images in the NetBackup Administrator s Guide Volume I When the disk image is imported NetBackup does not recover the original catalog ent
269. pI Mage BPBKAR32 Client Disk 250 Backup and restore functional overview Backups and archives UNIX clients 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 m Raw partition backups are not supported m NetBackup for NetWare does not support archiving Figure A 6 shows the NetWare client processes In this figure the following item applies m For NetWare nontarget operations the Windows based user interface program is called nanwNT For NetWare target operations the user interface program is called BP NLM on the Netware console The bpbackup bparchive and bplist functions are merged into the user interface programs on the clients m The NetBackup NetWare client daemon is called Beco The bpbkar functions are merged into BPCD The server processes are the same as described for UNIX Backup and restore functional overview 251 Backups and archives UNIX clients Figure A 6 Backup and archive NetWare clients Server NetWare client For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter NetBackup user interface NBNWNT NetWare nontarget BP NetWare target Request File information Client disk Synthetic backups The typical NetBackup backup process accesses the client to create a backup A synthetic backup is a backup image c
270. poration and its licensors if any THE DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE OR USE OF THIS DOCUMENTATION THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12 212 and subject to restricted rights as defined in FAR Section 52 227 19 Commercial Computer Software Restricted Rights and DFARS 227 7202 Rights in Commercial Computer Software or Commercial Computer Software Documentation as applicable and any successor regulations Any use modification reproduction release performance display or disclosure of the Licensed Software and Documentation by the U S Government shall be solely in accordance with the terms of this Agreement Symantec Corporation 350 Ellis Street Mountain View CA 94043 http www symantec com Printed in the United States of America 10987654321 Technical Support Symantec Technical Support maintains support centers globally Technical Support s primary role is to respond to specific q
271. port refer to the nosu command m For troubleshooting run nbsu when the system is in the same state as when the problem occurred For example do not stop and restart the NetBackup processes after the error occurs or make a change to the server or network If you do nbsu may not be able to gather key information about the problem m Ifa NetBackup component is not operational for example bpgetconfig does not return information nosu may be unable to properly report on the system For these cases use the nbu_down command line option to bypass the need for NetBackup to be operational For a full description of the nbu_down command line option see the NetBackup Commands Reference Guide 156 Using NetBackup utilities About the NetBackup support utility nbsu If nbsu does not perform as expected try the following m By default nosu sends error messages to standard error STDERR and also includes the messages in its output files under the header stpERR Note the following alternate ways to view nbsu error messages To redirect the Enter the following nbsu error m UNIX messages to usr openv netbackup bin support nbsu 2 gt amp 1 standard output Windows STDOUT install _path NetBackup bin support nbsu exe 2 gt amp 1 Tosendallnbsu Enter the following screen output including error messages to a file nbsu 2 gt amp 1 gt file name Where 2 gt amp 1 directs standard error into standard output and file name dire
272. pported for use with the tape drive by the tape drive vendor m An unexpected media is found in the drive An example of the log entry is as follows Incorrect media found in drive index 2 expected 30349 found 20244 FREEZING 30349 The following conditions can cause this error m NetBackup requests a media ID to be mounted in a drive If the media ID that is physically recorded on the tape is different than the NetBackup Troubleshooting procedures 73 Frozen media troubleshooting considerations media ID the media freezes This error occurs if the robot needs to be inventoried or if bar codes have been physically changed on the media m Another NetBackup installation previously wrote to the media with different barcode rules m The drives in the robot are not configured in order within NetBackup or they are configured with the wrong tape paths The correct robot drive number is important to the proper mounting and use of media The robot drive number is normally based on the relationship of the drive serial number with the drive serial number information from the robotic library Validate this number before you consider that the device configuration is complete m The media contain a non NetBackup format An example of the log entry is as follows FREEZING media id 000438 it contains MTFl format data and cannot be used for backups FREEZING media id 000414 it contains tar format data and cannot be used for backups FREEZI
273. programs continued tpconfig The Tape Library Multimedia daemon is the interface between ltid and a TLM robot that is in an ADIC Distributed AML Server DAS This daemon communicates with the TLM robotics through a network API interface Started By Starting ltid or independently by using the usr openv volmgr bin tlmd command Stopped By Stopping Itid or independently by finding the PID process id and then using the kill command Debug Log Errors are logged in the system log and robots debug log Debug information is included if the daemon is started with the v option either by itself or through Itid The v option is available only on UNIX Also add the VERBOSE option to the vm conf file tshd The Tape Stacker Half inch daemon is the interface between Itid 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 ltid or on UNIX independently by using the usr openv volmgr bin tshd command Started By tpconfig command Stopped By Quit option from within the utility on UNIX On Windows tpconfig is only a command line interface that runs to completion no quit option Debug Log tpcommand debug logs vmd The Volume Manager daemon NetBackup Volume Manager service on Windows allows remote administration and control of Media and Device Management vmd provides a proxy to EMM for pre 6 0 NetBackup
274. r each backup image being multiplexed onto the media NetBackup also allocates a separate set of shared memory blocks for each image The other client and server processes are the same as shown in Figure A 1 Backup and restore functional overview 243 Backups and archives UNIX clients Figure A 2 shows multiplexed images from two clients Figure A 2 Multiplexed backups example two streams ooo ooo 9 222 225 2252 5 5 5 5 5 5 5 5 5 55555 5 aaa Only on maser server bpdbm File info See Figure A 1 for process details leading to nbemm ow nbemm Client disk jsenbeu yuno 0 UNIX client nbrmms Backup Image Notes For details on these components see the Media and Device Management Functional Description later in this chapter If the server is backing up itself server and client on same host there is no Client disk bptm child bpbkar sends the data directly to shared memory Snapshot backup and Windows open file backups Figure A 3 shows the overall snapshot backup process PBX not shown in the diagram must be running for NetBackup to operate 244 Backup and restore functional overview Backups and archives UNIX clients Figure A 3 Snapshot backup and Windows open file backup using multiple data streams po pe Se RS Sy Master server Configuration File Backup Policy Database Database Management CN NetBackup user interface or comm
275. r example 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 Then a user on pluto starts a restore The router can use the name of its network interface to pluto meteor as the peer name when it forwards the request to the server The server interprets the request as coming from a host that is named meteor It 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 NetBackup server the file path is install path netbackup db altnames meteor On a UNIX NetBackup server the file path is usr openv netbackup db altnames meteor Then the administrator adds the following line to this file pluto The master server now recognizes as legitimate any of the restore requests with a peer name of meteor and client name of pluto See the NetBackup Administrator s Guide Volume I Regardless of the type of router the configuration for the media server saturn is the same as in another example 64 Troubleshooting procedures Verifying host name and service entries in NetBackup See Example of host name and service entries on UNIX master server and media server on page 59 If a media server is involved in a backup or restore for pluto the master
276. r processes see earlier in this chapter BPINETD BPCD Client Disk Restoring NetWare clients NetBackup supports the same types of restore operations on NetWare clients as it does on UNIX clients Figure A 15 shows the client processes involved in these operations In this figure the following applies m The NetWare nontarget user interface program is called NBNwnT The NetWare target user interface program is BP on the Netware console The bprestore function and the bplist function are merged into the user interface programs on the clients m The NetBackup NetWare client daemon is called Bpcp The NetBackup tar functions are merged into BPCD Backup and restore functional overview 265 Restore processes m mtfra functionality used to restore Backup Exec images has been merged into BPCD The server processes involved in import and restore operations for Backup Exec images are the same as those involved for NetBackup restores The server processes are the same as described for UNIX Figure A 15 shows the restore operation for a NetWare client Figure A 15 Restore NetWare client Server NetWare client For details on the server processes see Backups and Archives UNIX Clients earlier in this chapter NetBackup user interface m Reest NBNWNT NetWare nontarget Backup Image BPCD NetWare Client disk 266 Backup and restore functional overview Restore processes Re
277. r server with the Windows operating system intact To recover the master server with Windows intact 1 Determine the install_path in which NetBackup is installed By default NetBackup is installed in the c Program Files VERITAS directory Determine if any directory paths or locations need to be created for NetBackup catalog recovery Partition any disks being recovered as they were before the failure if partitioning is necessary Then reformat each partition as it was before the failure Reinstall NetBackup software on the server Refer to the NetBackup Installation Guide for Windows Install any NetBackup patches that had been previously installed See the documentation that was included with the patch software If the catalog directories differ from those in the NetBackup catalog backups recreate that directory structure on disk before you recover the catalog For example use the NetBackup nbdb_move command to relocate parts of the NetBackup relational database catalog If the recovery scenario involves restoring policy or catalog backups the appropriate recovery devices must be configured You may have to do some or all of the following Disaster recovery 189 About disk recovery procedures for Windows m Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored If anon robotic drive is available that can read these backups th
278. r_ops root logs Windows NetBackup directories and files Figure A 17 shows the NetBackup file and directory structure on UNIX servers and clients If a host is only a client and not a server only the files in the Client 268 Backup and restore functional overview NetBackup directories and files portion are present If a host is both a client and a server the client shares files as necessary from those in the Server portion A Windows NetBackup server has equivalent files and folders that are located where NetBackup is installed c Program Files VERITAS by default NetBackup directory structure UNIX Figure A 17 lists the items that are described in tables on the following pages Figure A 17 NetBackup directories and files NetBackup server usr openv java lib logs netbackup resources share volmgr usr openv netbackup bin bp conf client db dbext help logs nblog conf nblog conf template nbsvcmon conf remote_versions version version_master NetBackup client usr openv bin java lib msg netbackup resources share tmp var usr openv netbackup bin bp conf dbext help logs nblog confl nblog conf template Table A 2 describes the usr openv files and directories Backup and restore functional overview 269 NetBackup directories and files Table A 2 Directories and files in usr openv servers and UNIX clients bin Contains miscellane
279. race to write to the log file For example if you started jnbSA from the root account start usr openv java get_trace as root Otherwise the command runs without error but fails to add the stack trace to the debug log This failure occurs because root is the only account that has permission to run the command that dumps the stack trace Run usr openv netbackup bin goodies support Run this script after you complete the NetBackup installation and every time you change the NetBackup configuration Provide the log file and the output of the support script for analysis Chapter Troubleshooting procedures This chapter includes the following topics About troubleshooting procedures Troubleshooting NetBackup problems Troubleshooting installation problems Troubleshooting configuration problems Device configuration problem resolution Testing the master server and clients Testing the media server and clients Resolving network communication problems with UNIX clients Resolving network communication problems with PC clients Verifying host name and service entries in NetBackup About the bpclntcmd utility Using the Host Properties window to access configuration settings Resolving full disk problems Frozen media troubleshooting considerations Resolving PBX problems About troubleshooting duplication to a remote master Troubleshooting network interface card performance About SERVER entries in the bp conf file 20 Troubl
280. rary 8mm or Tape Stacker 8mm 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 Itid 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 Itid and then to the local tl8d all on the same host tl8d then forwards the request to tl8cd on the host that is controlling the robot could be on another host Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin tl8d command Stopped By Stopping Itid or on UNIX independently by finding the PID process id and then using the kill command Debug Log Errors are logged in the system log and robots debug log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option either by itself or through Itid 300 Media and device management functional description Media and device management components Table B 2 Media and device management daemons and programs continued tl8cd The Tape Library 8MM Control daemon provides the robotic control for a TL8 robot and communicates with the robotics through a SCSI interface tl8cd receives mount and unmount requests from tl8d on the host to which the drive is attached and then communicates these requests to the robot Starte
281. re is functional which includes all daemons or services programs and databases m NetBackup can mount the media and use the drive you configured Step 5 Check for failure If a failure occurs first check the NetBackup All Log Entries report For the failures that relate to drives or media verify that the drive is in an UP state and that the hardware functions To isolate the problem further use the debug logs A functional overview sequence of events is available See About backup and restore functional overview on page 235 33 34 Troubleshooting procedures Testing the master server and clients Table 2 6 Steps for testing the master server and clients continued Step 6 Consult information besides the debug logs If the debug logs do not reveal the problem check the following m Systems Logs or Event Viewer System logs m Event Viewer Application and System logs on Windows systems m vmd debug logs on the EMM database host for the device m bptm debug logs See the vendor manuals for information on hardware failures Step 7 Verify robotic drives If you use a robot and the configuration is an initial configuration verify that the robotic drive is configured correctly In particular verify the following m Thesame robot number is used both in the Media and Device Management and storage unit configurations m Each robot has a unique robot number On a UNIX NetBackup server
282. re program Also useful for debugging bp db_log For more information on these logs see the NetBackup guide for the database extension product that you use mtfrd These logs have information about the mt frd process which is used for phase 2 imports and restores of Backup Exec media tar tar process during restores user ops The user_ops directory is created during the install of NetBackup on all servers and clients The NetBackup Java interface programs use it for the following temporary files and for job and progress log files that the Backup Archive and Restore program jbpSA generates This directory must exist for successful operation of any of the Java programs and must have public read write and run permissions This directory contains a directory for every user that uses the Java programs In addition on NetBackup Java capable platforms the NetBackup Java interface log files are written in a subdirectory that is called nbj logs All files in the user_ops directory hierarchy are removed according to the setting of the KEEP_LOGS_DAYS configuration option PC client processes that use legacy logging Most PC client processes use legacy logging To enable detailed legacy debug logging on Windows clients or NetWare target clients create the directories in the following location The directory names that you create correspond to the processes you want to create logs for Windows clients C Program Files VERITA
283. reated without using the client Instead a synthetic backup process creates a full or a cumulative incremental image by using only previously created backup images called component images Note Synthetic archives do not exist For example an existing full image and subsequent differential incremental images may be synthesized to create a new full image The previous full image and the incrementals are the component images The new synthetic full image behaves like a backup that is created through the traditional process The new 252 Backup and restore functional overview Backups and archives UNIX clients synthetic full image is a backup of the client that is as current as the last incremental The synthetic image is created by copying the most current version of each file from the most recent component image that contain the file A synthetic backup must be created in a policy with the True Image Restore with Move Detection option selected This option enables the synthetic backup to exclude the files that have been deleted from the client file system from appearing in the synthetic backup Like a traditional backup nbpem typically initiates a synthetic backup nbpem submits a request to nbjm to start the synthetic backup job nbjm starts bpsynth bpsynth executes on the master server It controls the creation of the synthetic backup image and the reading of the files that are needed from the component images If directory bpsyn
284. remote master feature 82 Troubleshooting procedures About troubleshooting duplication to a remote master To troubleshoot duplication to remote master jobs 1 To display the storage server information run the following command bpstsinfo lsuinfo stype PureDisk storage server PureDiskl LSU Info Server Name PureDisk woodridge min veritas com LSU Name PureDiskVolume Allocation STS_LSU_AT_STATIC Storage STS_LSU_ST_NONE Description PureDisk storage unit woodridge min veritas com 1 2 Configuration Media STS _LSUF_DIS STS _LSUF_ACTIVE STS _LSUF_ STORAGE NOT FREED STS LSUF_REP_ ENABLED STS _LSUF_REP SOURCE Save As STS SA CLEARF STS_SA_OPAQUEF STS SA IMAGE Replication Sources 0 Replication Targets 1 PureDisk bayside PureDiskVolume This output shows the logical storage unit LSU flags STS_LSUF_REP_ENABLED and STS_LSUF_REP SOURCE for PureDiskVolume PureDiskVolume is enabled for duplication to remote master jobs and it is a replication source 2 To verify that NetBackup recognizes these two flags run the following command nbdevconfig previewdv stype PureDisk storage server woodridge media_server woodridge U Disk Pool Name Disk Type PureDisk Disk Volume Name PureDiskVolume Flag ReplicationSource The ReplicationSource flag confirms that NetBackup recognizes the LSU flags Troubleshooting procedures 83 About troubleshooting duplication to a remo
285. retry the failed operation See About logs on page 99 22 Troubleshooting procedures Troubleshooting NetBackup problems Table 2 1 Steps for troubleshooting NetBackup problems continued Step 5 Retry the operation If you performed corrective actions retry the operation If you did not perform corrective actions or if the problem persists continue with the next step Step 6 Get more information for installation problems If you see the problem during a new installation during an upgrade installation or after you make changes to an existing configuration see the following procedures See Troubleshooting installation problems on page 26 See Troubleshooting configuration problems on page 27 Step 7 Ensure that the servers and clients are operational If you experienced a server or a client disk crash procedures are available on how to recover the files that are critical to NetBackup operation Step 8 Ensure that the partitions have enough disk space Verify that you have 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 fail The resulting error message depends on the process Possible error messages unable to access or unable to create or open a file On UNIX systems use the df command to view disk partition information On Windows systems use Disk
286. rom the alternate disk to the disk that you recover These are the catalogs recovered in step 9 13 Make the recovered disk the boot disk again and restart the system 14 Start and test the copy of NetBackup on the disk that you have recovered If your configuration includes an Enterprise Media Manager EMM server that is separate from the master server start NetBackup on the EMM server before starting NetBackup on the master server usr openv netbackup bin bp start_all Try the NetBackup Administration utilities Also try some backups and restores 15 When you are satisfied that the recovery is complete delete the NetBackup files from the alternate disk Or unhook that disk if it is a spare About recovering the NetBackup media server disk for UNIX and Linux NetBackup 6 0 and later media servers store information in the NetBackup relational database If you need to recover the system disk on a NetBackup media server the recommended procedure is similar to disk recovery for the client See Recovering the system disk on a UNIX client workstation on page 182 Note A separate computer that functions as a NetBackup 6 0 or later media server is available only on NetBackup Enterprise Server For NetBackup server installations the master server and the media server are installed on the same system and have the same host name Therefore recovering the master server disk also recovers the media server Recovering the sys
287. rom nbftsrvr and writes the data to the shared memory buffer on the client nbftclnt then sets the buffer flag Backup and restore functional overview 263 Restore processes m At the end of the job m bptm informs tar and bpbrm that the job is complete m bptm directs nbftclnt to close the fibre channel connection m nbftclnt closes the fibre channel connection and deletes the BID file Restoring Windows clients NetBackup supports the same types of operations on Windows clients as it does for UNIX clients The following are the Windows processes involved in restore operations m NBWINis the user interface program on the client The bpbackup function and the bparchive function are merged into NBWIN E BPINETD serves the same purpose as inetd on UNIX clients m The NetBackup client daemon is called Bpcp E TAR32 is part of NetBackup for Windows and serves the same purpose as NetBackup tar on UNIX Note To restore Backup Exec images bpbrm invokes mt frd exe instead of tar32 exe on the clients The server processes are the same as those used for NetBackup restores The server processes are the same as described for UNIX Figure A 14 shows the client processes involved in these operations 264 Backup and restore functional overview Restore processes Figure A 14 Restore Windows client Server Windows Client NetBackup User Interface Backups and archives UNIX clients For details on the serve
288. ry for the image Instead a new catalog entry is created Recovering the master server disk for UNIX and Linux The procedure in this section explains how to recover data if the system disk fails on a UNIX or Linux NetBackup master server The following two scenarios are covered Root file system is intact The operating system NetBackup software and some if not all other files are assumed to be lost See Recovering the master server when root is intact on page 178 Root file system is lost along with everything else on the disk This situation requires a total recovery This recovery reloads the operating system to an alternate boot disk and boots from this disk during recovery This operation lets you recover the root partition without risking a crash that is caused by overwriting the files that the operating system uses during the restore See Recovering the master server when the root partition is lost on page 179 For NetBackup master and media servers the directory locations of the NetBackup catalog become an integral part of NetBackup catalog backups Any recovery of the NetBackup catalog requires identical directory paths or locations be created during the NetBackup software reinstallation Disk partitioning symbolic links and NetBackup catalog relocation utilities may be needed NetBackup Bare Metal Restore BMR protects client systems by backing them up with a policy configured for BMR protection Information is
289. s Connectivity and device The CommandCentral Storage view of the SAN environment check can help you detect any failure in the topology In addition having an environment inventory to provide to support for troubleshooting is valuable to the support process General troubleshooting Some ways to investigate a backup failure are as follows tools m Launch CommandCentral Storage in context from NetBackup to check fabric health m Check reports for fabric events occurring around the time NetBackup generated the error log 96 Troubleshooting procedures About troubleshooting NetBackup in a SAN environment Using CommandCentral Storage to troubleshoot the inability to access drives or robots in a SAN environment The following use case demonstrates how CommandCentral Storage can be integrated into a NetBackup troubleshooting procedure to investigate the SAN context of a backup system Most common NetBackup problems on SANs revolve around connectivity issues Typically found as an error 213 no storage units available for use in NetBackup this problem represents a loss of connectivity This issue is a problem because NetBackup freezes tapes with two write failures even when SAN problems cause the failures Symptom Backup jobs fail To use CommandCentral Storage to troubleshoot the inability to access drives or robots in a SAN environment 1 Check the NetBackup device monitor to see whether a device is down If a device is down tr
290. s into an archive file If a supported compression utility is available nosu compresses the archive file Otherwise the individual output files remain unarchived and uncompressed An example of a compressed archive file that nbsu created is as follows usr openv netbackup bin support output nbsu hostl master 20060814_ 164443 host1_master_20060814_164443 tar gz where host1 is the name of the host on which nbsu ran master indicates that the host is a NetBackup master server Using NetBackup utilities 159 About the NetBackup support utility nbsu nbsu supports tar for archive and gzip for compression Symantec may add support for other archive and compression utilities in the future For an up to date list of supported archive and compression utilities run the nbsu H command on your installed version of NetBackup Note Archiving and compression utilities are usually available on UNIX and Linux systems On Windows it may be necessary to install these programs Note that the archiving utility must be referenced in the system PATH environment variable If no archive utility is installed on your system use the xm1 option of the nbsu command This option lets you create a single xm1 file in place of the individual output files The single xm1 file contains all the diagnostic information that the individual files contain Use this command to conveniently bundle nbsu output for Symantec technical support Status code informati
291. se the following example to set the maximum file size to 2048 and the maximum number of log files per log directory to 10 vxlogcfg a p 51216 orgid Default s MaxLogFileSizeKB 2048 NumberOfLogFiles 10 The example sets the default values for all unified logging processes and for all legacy processes for NetBackup product ID 51216 See the vxlogcfg man page or the NetBackup Commands Reference Guide See About limiting the size and the retention of legacy logs on page 131 See Examples of using vxlogcfg to configure unified logs on page 121 UNIX client processes that use legacy logging Most UNIX client processes use legacy logging To enable legacy debug logging on UNIX clients create the appropriate subdirectories in the following directory usr openv netbackup logs Note Create the directories with access modes of 777 so that user processes can write to the log files 134 Using logs About legacy logging Table 3 15 describes the directories for the legacy debug logs that apply to UNIX clients Table 3 15 UNIX client processes that use legacy logging bp Menu driven client user interface program bparchive Archive program Also useful for debugging bp bpbackup Backup program Also useful for debugging bp bpbkar Program that is used to generate backup images bpced NetBackup client daemon or manager bphdb Program that starts a script to back up a database on a NetBackup da
292. se this new port assignment m Ifaprocess other than bpcd uses the port try to reboot the client to clear the problem If the problem is still not fixed you may need to change one of the service numbers preferably for the other service To change a service number modify the etc services files Then send SIGHUP signals to the inetd processes on your clients bin ps ef grep inetd kill HUP the inetd pid Or bin ps aux grep inetd kill HUP the inetd pid On a Hewlett Packard platform use inetd ctosendaSIGHUP to inetd Also make applicable NIS or DNS updates If the problem is with an AIX client and you make changes to the etc inetd conf and etc services information use SMIT to verify that the InetServ object policy was updated See step 3 Resolving network communication problems with PC clients 48 Troubleshooting procedures Table 2 8 Steps for resolving network communication problems with UNIX clients continued Step 6 Verify communication between the client and the master server To verify client to master server communications use the bpcintcmd utility When pn and sv run on a NetBackup client they initiate inquiries to the NetBackup master server as configured in the client bp conf file The master server then returns information to the requesting client More information is available about bpclntcmd See About the bpclntcmd utility on page 66 Resolving network communicati
293. server About recovering the catalog image file Consider performing this recovery procedure only in the following scenarios m The NetBackup relational database is valid but NetBackup policy backup image or configuration files are lost 210 Disaster recovery How to recover a catalog from a backup m You want to restore part of the NetBackup catalog before you restore the entire catalog This procedure recovers only the catalog images and configuration files The catalog backup images contain information about all the data that has been backed up This information constitutes the largest part of the NetBackup catalog If the backup images are intact but the NetBackup relational database files are not you can still recover these files See Recovering relational database files from an online catalog backup on page 219 The wizard restores whatever catalog images and configuration files are in the backup set identified by the disaster recovery file If the disaster recovery file is from a full backup all catalog images and configuration files are restored For an incremental backup the wizard restores only catalog images and configuration the files that were changed since the previous backup However all catalog backup image files back to the last full catalog backup are automatically included in an incremental catalog backup This operation allows for the complete restoration of all backup images by the Backup Archive
294. server provides the following the correct peer name and client name for the media server to use to establish connections Example of host name and service entries on UNIX server that connects to multiple networks The following illustration shows an NBU server with two Ethernet connections and clients in both networks The server host name is jupiter on one and meteor on the other Troubleshooting procedures 65 Verifying host name and service entries in NetBackup Figure 2 5 UNIX server connects to multiple networks Client Ethernet UNIX saturn Media Server jupiter meteor UNIX Master Server Ethernet Policy Client List jupiter mars saturn pluto usr openv netbackup bp conf SERVER jupiter SERVER meteor SERVER saturn CLIENT_NAME mars usr openv netbackup bp conf SERVER jupiter SERVER meteor SERVER saturn CLIENT_NAME jupiter UNIX pluto Client etc inetd conf bpcd bpcd see note 1 etc services NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd etc inetd conf bpcd see note 1 usr openv netbackup bp conf SERVER jupiter SERVER meteor SERVER saturn CLIENT_NAME pluto etc services NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd bpdbm 13721 tcp bpdbm Volume Manager services vmd 13701 tcp vmd tl8cd 13705 tcp tl8cd odld 13706 tcp odld
295. servers Started By Starting ltid 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 304 Media and device management functional description Media and device management components Table B 2 Media and device management daemons and programs continued vmadm Available only on UNIX An administrator utility with options for configuring and managing volumes under control of media and device management It has a menu driven character based interface that can be used from workstations that do not have graphical display capabilities Started By usr openv volmgr bin vmadm command Stopped By Quit option from within the utility Debug Log usr openv volmgr debug reqlib vmscd The Media Manager Status Collector Daemon keeps the EMM server database up to date with the actual status of drives attached to 5 x servers Started By the EMM server Stopped By the EMM server Debug Log usr openv volmgr debug vmscd UNIX install_path Volmgr debug vmscd Windows Appendix Networks and hostnames This appendix includes the following topics m Background for troubleshooting Background for troubleshooting In a configuration with multiple networks and clients with more than one hostname NetBackup administrators
296. service NetBackup Device Manager service if the system has configured devices NetBackup Volume Manager service NetBackup Client service Services on EMM servers m NetBackup Enterprise Media Manager service m NetBackup Resource Broker service Services on media servers m NetBackup Device Manager service if the system has configured devices m NetBackup Volume Manager service m NetBackup Client service Services on clients including NetBackup Remote Administration Consoles m NetBackup Client service Step 2 Start avrd and processes for robots Use the NetBackup Activity Monitor to see if the following processes are running m avrd automatic media recognition only if drives are configured on the server m Processes for all configured robots See the NetBackup Administrator s Guide Volume I If these processes are not running stop and restart the NetBackup Device Manager service Use the NetBackup Activity Monitor or the Services application in the Windows Control Panel 26 Troubleshooting procedures Troubleshooting installation problems Table 2 2 Steps to ensure that all necessary processes are running on Windows servers continued Step 3 Restart the operation or do additional troubleshooting If you had to start any of the processes or services in the previous steps retry the operation If the processes and services are running or the problem persists you can try to test t
297. ses that use legacy logging continued NetBackup program that bpjava msvc starts upon successful logon through the logon dialog box that is presented when a NetBackup Java interface is started This program services all requests from the Java administration and user interfaces on the NetBackup host where bpj ava msvc is running On all Windows platforms bpjava usvc bplist Windows 2003 List program that is run from the command line bpmount Windows 2003 The program that is used to collect drive names on the client for multistreaming clients bprestore Windows 2003 The restore program that is run from the 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 tar Windows 2003 tar process These logs have information about the tar32 process 138 Using logs About global logging levels Table 3 16 PC client processes that use legacy logging continued user ops Windows 2003 The user_ops directory is created during the install of NetBackup on all servers and clients The NetBackup Java interface programs use it for the following temporary files and for job and progress log files that the Backup Archive and Restore program jbpSA generates This directory must exist for successful operation of any of the Java programs and must have pub
298. sis utilities for NetBackup debug logs backupdbtrace Consolidates the debug log messages for specified NetBackup database backup jobs and writes them to standard output It sorts the messages by time backupdbt race attempts to compensate for time zone changes and clock drift between remote servers and clients At a minimum you must enable debug logging for admin on the master server and for bptm and bpbkar on the media server For best results set the verbose logging level to 5 and enable debug logging for the following bpdbm on the master server and bpcd on all servers in addition to the processes already identified See backupdbt race in the Commands Reference Guide backuptrace Copies to standard output the debug log lines relevant to the specified backup jobs including online hot catalog backups The backuptrace utility can be used for regular file system database extension and alternate backup method backup jobs It consolidates the debug logs for specified NetBackup jobs The utility writes the relevant debug log messages to standard output and sorts the messages by time backuptrace attempts to compensate for time zone changes and clock drift between remote servers and clients The format of the output makes it relatively easy to sort or grep by timestamp program name and server or client name The backupt race utility works with the nbpem nbjm and nbrb logs on the master server You should enable debug logging f
299. sk oe on page591 Sybase ASA database agent Note the master server backs up itself See Backup to tape or disk on page591 Note the master server backs up the EMM server A hot catalog backup consists of the following jobs that run on the master server m A parent job that is started manually by the administrator or by a catalog backup policy schedule m Achild job that backs up the NetBackup relational database files m Achild job that copies the NetBackup database files on pre 6 0 media servers if any m Achild job that backs up the NetBackup database files all files in usr openv netbackup db A hot catalog backup process is as follows in the order presented m A manual backup or a catalog backup policy initiates the backup 256 Backup and restore functional overview Restore processes m nbpem submits a parent job to nbjm nbjm sends a request to bpdbm m bpdbm handles the backup of the relational database files in two steps m The SQL Anywhere files database agent makes an online copy of the relational database files to usr openv db staging See the Disaster Recovery chapter for a list of the relational database files m After the files are in the staging area the SQL Anywhere database agent backs them up in the same manner as is used for an ordinary backup m NetBackup backs up the database files that are in usr openv netbackup db and important NetBackup files to the m
300. sk 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 ltid or independently by using the usr openv volmgr bin odld command Stopped By Stopping ltid or independently by finding the PID process id and then using the kill command Debug Log All errors are logged in the system log Debug information is included if the daemon is started with the v option either by itself or through Itid or adding VERBOSE to the vm conf file Table B 2 Media and device management functional description 299 Media and device management components Media and device management daemons and programs continued tl4d The Tape Library 4MM daemon is the interface between Itid and the Tape Library 4MM and communicates with the robotics through a SCSI interface Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin tl4d command Stopped By Stopping Itid or on UNIX independently by finding the PID process id and then using the kill command Debug Log All errors are logged in the system log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option either by itself or through Itid tl8d The Tape Library 8MM daemon provides the robotic control for a TL8 robot Tape Lib
301. specific short date and time format For example a locale may have format mm dd yy hh mm ss AM PM ENDATE 99736352 ENDATE 04 27 04 10 01 00 AM PREVTIME String Provide the hours in hh mm ss format This field should be used only with operators lt gt gt and lt PREVTIME 2 34 00 SEV Integer Provide one of the following possible severity types 0 INFO 1 WARNING 2 ERR 3 CRIT 4 EMERG SEV Il fo SEV INFO MSGTYPE Integer Provide one of the following possible message types 0 DEBUG debug messages 1 DIAG diagnostic messages 2 APP application messages 3 CTX context messages 4 AUDIT audit messages MSGTYPE Il bh MSGTYPE DIAG CTX Integer or string Provide the context token as string identifier or ALL to get all the context instances to be displayed This field should be used only with the operators and CTX 78 CTX ALL Consider the following when writing a query string 118 Using logs About unified logging Case sensitivity Field names severity types and message types are not case sensitive For example the following are valid entries E sev info E msgtype diag String constants String constants should be given in single quotes For example PRODID NBU Dates Start and end dates can be provided in the following formats Astring constant that corresponds
302. stname_ NBCC_20101018_ 101900 nbcc info txt output file About the NetBackup consistency check repair NBCCR utility The NetBackup consistency check repair NBccR utility is a command line tool that processes database catalog repair actions It automates the application of approved suggested repair actions Symantec technical support analyzes the data that is collected by the nscc utility and site specific configuration information This analysis results in the generation of a suggested repair actions SRA file Before nBccr is run Symantec technical support interacts with the customer to determine which repairs are needed Undesirable repair actions are deleted or commented out of the SRA file Each line of the SRA file contains one repair action that is paired with an associated parameter The neccr utility executes each repair action in several stages 168 Using NetBackup utilities About the NetBackup consistency check repair NBCCR utility Table 4 4 Stages of repair Stage 1 Data collection NBCCR first collects the information that is required to perform a repair Stage 2 Repair Immediately before the suggested repair is applied NBCCR qualification verifies that the current status of the tape still qualifies for the requested repair It recognizes that time has passed and the environment may have changed since the data was collected If so it reports in a history file that the repair is not qualified Stage 3 Repair Fi
303. storing catalog backups A catalog restore can be initiated by the NetBackup Catalog Recovery Wizard in the Administration Console or by manual use of the bprecover command More information is available in the following topic See About disaster recovery on page 173 Figure A 16 illustrates the catalog restore and recovery process Figure A 16 Catalog restore and recovery NetBackup Catalog Recovery Wizard Command line lt p o Restore NetBackup Database Files bprecover Sybase ASA database agent See Restore from tape UNIX or 2 Restore from disk depending on the catalog Restore Relational backup policy Database Files See Restore from usr openv db Relational pre a staging database files Restore from disk depending on the catalog backup policy Backup and restore functional overview 267 NetBackup directories and files A restore of the NetBackup database and relational database files from a hot catalog backup consists of the following steps in the order presented m The NetBackup database files are restored by means of the standard NetBackup restore procedure m The relational database files are restored by means of the standard NetBackup restore procedure The database files are restored to usr openv db staging UNIX and Linux or to install_path NetBackupDB staging Windows m After the files are restored to the s
304. tBackup bin bpdown install _path NetBackup bin bpup If your configuration includes an Enterprise Media Manager EMM server that is separate from the master server start NetBackup on the EMM server first Warning In step 12 do not restore files to the install_path NetBackup db install _path NetBackupDB install_path NetBackup var Or install_path Volmgr database directories These directories were recovered in step 10 and overwriting them with regular backups leaves the catalogs in an inconsistent state If the relational database files were relocated using nbdb move from install_path NetBackupDB data they are recovered in step 10 and should not be restored in step 12 12 To restore all other files do the following steps in the order presented m Start the NetBackup Administration interface on the master server m Start the Backup Archive and Restore client interface m Browse for restores and select only the partitions that were lost Select the system directory typically c winnt which ensures that all registry files are restored m Deselect the install _path NetBackup db install_path NetBackupDB or relocated NetBackup relational database path install path NetBackup var Or install path Volmgr database directories See the caution in this procedure m Ifyoureinstall Windows select the Overwrite existing files option which ensures that existing files are replaced with the backups m Start the restore 13 Res
305. ta to a log file if NetBackup is installed on the computer where on Windows the application was started It logs on install_path NetBackup logs user_ops nbjlogs If NetBackup was not installed on this computer then no log file is created To produce a log file modify the last java exe line in the following to redirect output to a file install path java nbjava bat usr openv java get_trace Provides a Java virtual machine stack trace for support to analyze This stack trace is written to the log file that is associated with the instance of execution 18 Introduction About gathering information for NetBackup Java applications usr openv netbackup bin goodies support Creates a file containing data necessary for customer support to debug any problems you encounter For more details consult the usage information of the script by using support h The following example describes how you could gather troubleshooting data for Symantec Technical Support to analyze An application does not respond There is still no response after several minutes Get data about your configuration Contact Symantec Technical Supoort Wait for several minutes before you assume that the operation is hung Some operations can take quite a while to complete especially operations in the Activity Monitor and Reports applications Run usr openv java get_trace under the account where you started the Java application This script causes a stack t
306. tabase agent client See the system administrator s guide for the appropriate NetBackup database agent for more information bpjava msvc The NetBackup Java application server authentication service that inetd starts during startup of the NetBackup Java interface applications This program authenticates the user that started the application bpjava usve The NetBackup program that bpj ava msvc starts upon successful logon through the logon dialog box that is presented when a NetBackup Java interface is started This program services all requests from the Java administration and user interfaces on the host where bpj ava msvc is running bplist Program that lists backed up and archived files Also useful for debugging bp bpmount Program that determines local mount points and wildcard expansion for multiple data streams bporaexp Command line program on clients to export Oracle data in XML format Communicates with bprd on server bporaexp64 64 bit command line program on clients to export Oracle data in XML format Communicates with bprd on server bporaimp Command line program on clients to import Oracle data in XML format Communicates with bprd on server bporaimp64 64 bit command line program on clients to import Oracle data in XML format Communicates with bprd on server Using logs 135 About legacy logging Table 3 15 UNIX client processes that use legacy logging continued bprestore Resto
307. table reside under usr openv volmgr bin On Windows they reside under install_path volmgr bin Note The following table contains references to the system log This log is managed by syslog on UNIX the facility is daemon On Windows the Event Viewer manages the system log the log type is Application Table B 2 Media and device management daemons and programs acsd The Automated Cartridge System daemon interfaces with the Automated Cartridge System It 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 ltid or on UNIX independently by using the usr openv volmgr bin ascd command Stopped By Stopping Itid or on UNIX independently by finding the PID process id and then using the kill command Debug Log Errors are logged in the system log and robots debug log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option this option can also be used through Itid or by putting VERBOSE in the vm conf file acssel Available only on UNIX See the NetBackup Device Configuration Guide acsssi Available only on UNIX See the NetBackup Device Configuration Guide 297 298 Media and device management functional description Media and device management components
308. taging directory the relational database is recovered Each transaction log in the staging area is applied in order one by one m The relational database files are moved from the staging directory to a location determined by the following the bp conf filevxpBMs_NB_DATA setting on UNIX or Linux and by the corresponding registry key on Windows The default location is usr openv db data on UNIX and Linux and install_path NetBackupDB data on Windows If the relational database files are relocated they are moved from the staging directory to the usr openv db data vxdbms conf file UNIX or the install _path NetBackupDB data vxdbms conf file Windows A description is available of how the NetBackup relational database files can be relocated after installation See NetBackup Relational Database in the NetBackup Administrator s Guide Volume I Messages that are related to this catalog recovery process are divided into the following three areas m For messages that are related to all catalog recovery steps consult the usr openv netbackup logs admin logs UNIX and Linux or install _path NetBackup logs admin Windows m For messages that are related to the first two bulleted items consult the tar bpbrm and bpcd logs m For messages pertaining only to the relational database files see the progress logs in the following directory usr openv netbackup logs user_ops root logs UNIX and Linux or install_path NetBackup logs use
309. tallation directory fills up such as with logging files anumber of problems can result NetBackup may become unresponsive For example NetBackup jobs may remain queued for long periods even though all NetBackup processes and services are running 70 Troubleshooting procedures Resolving full disk problems To resolve full disk problems 1 The NetBackup Resource Broker nbrb log may have database connection errors in it These errors indicate failed tries to establish connections to the nbemm database The following is an example of such errors in the nbrb log 7 20 2005 12 33 47 239 RBDatabase connectDatabase ODBC connection failed ErrMsg Sybase ODBC Driver Adaptive Server Anywhere Disk write failure Fatal error disk write failure C Program Files VERITAS NetBackupDB data NBDB log transaction rolled back ErrCode 1Sqlstate HY000 The nbrb log originator ID 118 is written in usr openv 1logs UNIX or install_path NetBackup logs Windows More information is available about unified logging See About logs on page 99 2 Tocorrect the situation clear up disk space in the directory where NetBackup is installed by doing the following m You may need to delete log files manually reduce logging levels and adjust log retention to have log files automatically deleted sooner More information is available about logging levels log file retention and how to configure unified logging See About logs on pa
310. tart the system which replaces any files that were busy during the restore When the boot process is complete the system is restored to the state it was in at the time of the last backup 194 Disaster recovery About disk recovery procedures for Windows About recovering the NetBackup media server disk for Windows A separate computer that functions as a NetBackup 6 0 or later media server is available only on NetBackup Enterprise Server For NetBackup server installations the master server and the media server are installed on the same system and have the same host name Therefore recovering the master server disk also recovers the media server NetBackup media servers store their information in the NetBackup relational database If you need to recover the system disk on a NetBackup media server the recommended procedure is similar to disk recovery for the client See Recovering a Windows client disk on page 194 Recovering a Windows client disk The following procedure explains how to perform a total recovery of a Windows NetBackup client in the event of a system disk failure NetBackup Bare Metal Restore BMR protects client systems by backing them up with a policy configured for BMR protection A complete description of BMR backup and recovery procedures is available See the Bare Metal Restore System Administrator s Guide This procedure assumes that the Windows operating system and NetBackup are reinstalled to boot
311. tbackup bin bpcd bpcd m Allother applicable network configuration must also be updated to reflect the NetBackup information For example this information could include the etc hosts file and NIS and DNS if used Troubleshooting procedures Verifying host name and service entries in NetBackup Example of host name and service entries on UNIX clients in multiple The following illustration shows a client that is a router to clients in another network The client host name on the master server side is mars and the host name that is presented to the client pluto is meteor networks Figure 2 4 UNIX i iter Master Server Jup UNIX clients in multiple networks UNIX Ethernet saturn Media Server Policy Client List jupiter mars saturn pluto usr openv netbackup bp conf SERVER jupiter SERVER saturn CLIENT_NAME jupiter mars meteor UNIX Client Ethernet etc inetd conf bpcd bpcd see note 1 usr openv netbackup bp conf SERVER jupiter SERVER saturn CLIENT_NAME mars Client usr openv netbackup bp conf SERVER jupiter SERVER saturn etc services NetBackup services bpcd 13782 tcp bpcd bprd 13720 tcp bprd bpdbm 13721 tcp bpdbm Volume Manager services vmd 13701 tcp vmd tl8cd 13705 tcp tl8cd odld 13706 tcp odld etc inetd conf bpcd bpcd see note 1 CLIENT_NAME pluto etc inetd conf
312. tc services file Verify that the NetBackup Client Service Port number and NetBackup Request Service Port number match settings in the services file by doing the following Start the Backup Archive and Restore interface on the client On the File menu click NetBackup Client Properties In the NetBackup Client Properties dialog box on the Network tab select the following The NetBackup Client Service Port number and NetBackup Request Service Port number The values on the Network tab are written to the services file when the NetBackup Client service starts The services file is in the following location SSystemRoot system32 drivers etc services Check the BPCD and the BPRD entries in the SYS VERITAS NBUCLT NetBack BP INI file clients check the etc inetd conf file to ensure that it has the following entry bpcd stream tcp nowait root usr openv netbackup bin bpcd bpcd 5 On Windows servers and clients verify that the NetBackup Client service is running 6 Ifyou use NIS in your network update those services to include the NetBackup information that is added to the etc services file 7 NIS WINS or DNS host name information must correspond to what is in the policy configuration and the name entries On Windows NetBackup servers Microsoft Windows clients and NetWare nontarget clients do the following m Check the General tab Start the Backup Archive and Restore interface on the client On the File m
313. te master To display the replication targets by using the raw output run the following command nbdevconfig previewdv stype PureDisk storage_ server woodridge media_server woodridge V7 0 DiskVolume lt PureDiskVolume PureDiskVolume 46068048064 46058373120 000161 gt V7 0 ReplicationTarget lt bayside PureDiskVolume gt The display shows that the replication target is a storage server called bayside and the LSU volume name is PureDiskVolume To ensure that NetBackup captured this configuration correctly run the following command nbdevquery listdv stype PureDisk U Disk Pool Name PDpool Disk Type PureDisk Disk Volume Name PureDiskVolume Flag AdminUp Flag InternalUp Flag ReplicationSource Num Read Mounts 0 The listing shows that disk volume PureDiskVolume is configured in disk pool PDPool and that NetBackup recognizes the replication capability If NetBackup does not recognize the replication capability run the following command nbdevconfig updatedv stype PureDisk dp PDpool To ensure that you have a storage unit that uses this disk pool run the following command bpstulist PDstu 0 STU NO DEV HOST 0 1 1 1 0 NULL 1 1 51200 NULL 2 6 0 0 0 0 PDpool NULL The output shows that storage unit PDstu uses disk pool PDpool 84 Troubleshooting procedures About troubleshooting duplication to a remote master 7 Check the settings on the disk pool by running the followin
314. te the appropriate directories for each process UNIX usr openv netbackup logs usr openv volmgr debug Windows install_path NetBackup logs install_path Volmgr debug After the directories are created NetBackup creates log files in the directory that is associated with each process A debug log file is created when the process begins To enable debug logging for the NetBackup Status Collection Daemon vmsca create the following directory before you start nbemm As an alternative you can stop and restart nbemm after creating the following directory UNIX usr openv volmgr debug reqlib Windows install_path Volmgr debug reqlib Tables are available that list the log directories that you must create See Directory names for legacy debug logs for servers on page 127 See Directory names for legacy debug logs for media and device management on page 129 Note On a Windows server you can create the debug log directories at once under install_path NetBackup Logs by running the following batch file install_path NetBackup Logs mklogdir bat Media servers have only the bpbrm bpcd bpdm and bptm debug logs Creating legacy log directories to accompany problem reports for synthetic backup If the legacy log directories have not been created you must create them If the directories do not exist the logs cannot be written to disk 126 Using logs About legacy logging Table 3 11 Creating legacy lo
315. tem disk on a UNIX client workstation NetBackup Bare Metal Restore BMR protects client systems by backing them up with a policy configured for BMR protection A complete description of BMR backup and recovery procedures is available See the Bare Metal Restore Administrator s Guide Disaster recovery 183 About clustered NBU server recovery for UNIX and Linux To recover the system disk on a client workstation 1 Reload the operating system as you normally would for a client workstation of that type If the root file system is lost the best approach may be to reload the operating system on an alternate boot disk and start from this disk After restoring the system restore root to its original partition This operation lets you recover the root partition without risking a crash due to overwriting the files that the operating system uses during the restore The procedure is similar to the procedure that is used for the master server except that recovering the NetBackup catalogs is not necessary See About recovering the master server disk for Windows on page 187 Reinstall NetBackup client software and patches Use the NetBackup Backup Archive and Restore interface to select and restore files About clustered NBU server recovery for UNIX and Linux NetBackup server clusters do not protect against catalog corruption loss of the shared disk or loss of the whole cluster Regular catalog backups must be performed More inf
316. th exists in the debug log directory additional debug log messages are written to a log file in that directory bpsynth makes a synthetic image in several phases Phase 1 Prepare catalog information and extents In phase 1 bpsynth makes a synthetic backup request to the database manager bpdbm bpdbm uses the entries and the TIR information from the catalogs of the component images to build the catalog for the new synthetic image It also builds the extents to be copied from the component images to the synthetic image Bpdbm returns the list of extents to bpsynth An extent is the starting block number and the number of contiguous blocks within a specific component image A set of extents must usually be copied from each component image onto the new synthetic image Figure A 7 shows how phase 1 operates Figure A 7 Synthetic backup preparation phase nbpem 0 nbjm Request to make y synthetic backup bpsynth bpdbm ha Extents and media Catalog needed to form the synthetic backup Master server Backup and restore functional overview 253 Backups and archives UNIX clients Phase 2 Obtain resources In phase 2 bpsynth obtains write resources storage unit drive and media for the new image It also reserves all the read media containing component images and obtains the drive for the first media to be read When the component images reside on BasicDisk or NearStore no resource reservation is done P
317. that the NetBackup catalog data is protected through Tue Aug 10 11 41 48 2010 retain a copy of the attached file and the media or files listed below Catalog Recovery Media Media Server Disk image path ant storage DiskUnit1 ant_1123605764 Cl _TIR ant storage DiskUnitl ant_1123605764 Cl Fl ant storage DiskUnit1 ant_1123605713_Cl_ Fl DR file written to storage DR CatalogBackup_ 1123605764 FULL 228 Disaster recovery How to recover a catalog from a backup Primary Media Catalog Recovery Procedure for the Loss of an Entire Catalog Symantec recommends creating a detailed disaster recovery plan should it become necessary to restore your organization s data in the event of a disaster A checklist of required tasks can be a tremendous tool in assisting associates in triage For example after the facility is safe for data to be restored the power and data infrastructure need to be verified When these tasks are completed the following scenarios will help to quickly restore the NetBackup environment and in turn restore applications and data Disaster Recovery Procedure using the DR Image File In the event of a catastrophic failure use the following procedure to rebuild the previous NetBackup environment Note If new hardware is required make sure that the devices contain drives capable of reading the media and that the drive controllers are capable of mounting the drives 1 Install NetBackup 2 Configure t
318. 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 The result is that it can cause media mount timeouts and prevent other robotic operations like robotic inventory and inject or eject from working Troubleshooting procedures 41 Resolving network communication problems with UNIX clients Table 2 7 Steps for testing the media server and clients continued Step 8 Test other clients or When the test policy operates satisfactorily storage units repeat specific steps as necessary to verify other clients and storage units Step 9 Test the remaining When all clients and storage units are in policies and schedules operation 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 suggested actions for the appropriate status code Resolving network communication problems with UNIX clients The following procedure is for resolving NetBackup communications problems such as those associated with NetBackup status codes 54 57 and 58 This procedure consists of two variations one for UNIX clients and another for PC clients Note In all cases ensure that your network configuration works correctly outside of NetBackup before trying to resolve NetBackup pro
319. the error message To find the status code look up the NetBackup message in the alphabetical listing and click the link to see a full description See the Status Codes Reference Guide NetBackup These messages have status codes in the 500 range Messages with Administration status codes 500 501 502 503 and 504 begin with Unable to Console application login status Messages with status codes 511 and 512 may server status codesand or may not begin with Unable to login status es Note A status code does not always accompany the error message See the Status Codes Reference Guide 146 Using logs Troubleshooting error messages in the NetBackup Administration Console for UNIX Java exceptions Either the Java APIs or NetBackup Administration APIs generate these exceptions 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 the following places m The status line bottom of the NetBackup Administration window m The log file that the jnbSA or jbpSA commands generate m The output file of the Windows Display Console bat file if it is set up See Troubleshooting error messages in the NetBackup Administration Console for UNIX on page 145 Operating system Any messages that do not match those in the NetBackup errors documentation are most likely messages from the operating system About e
320. the eventlog file The following is an example 56 255 The parameters in the eventlog represent severity and type The parameters have the following characteristics Severity m Listed as the first parameter Controls the messages that NetBackup writes to the Application log m Ifthe file is empty the default severity is Error 16 m Ifthe file has only one parameter it is used for the severity level Type m Listed as the second parameter Controls the type of messages that NetBackup writes to the Application log m Ifthe file is empty the default type is Backup Status 64 Both parameters are specified as decimal numbers and equate to a bitmap that expresses the following values 144 Using logs Logging options with the Windows Event Viewer 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 64 Backup Status 128 Media Device You can configure the eventlog file to log the messages that include several different severities and types Consider the results that the following entry in the eventlog file produces 56 255 Entry 56 Produces a log with messages that have a severity of warning error and critical 56 8 16 32 Entry 255 Produces a log with messages for all types 225 1 2 4 8 16 32 64 128 Consider the following example message that is written in the Windows Event Viewer Application
321. the system and perform a restore The following are additional assumptions m The NetBackup client was running a supported Microsoft Windows version m The NetBackup client was backed up with a supported version of NetBackup client and server software m The NetBackup master server to which the client sent its backups is operational You request the restore from this server m The backups included the directory where the operating system and its registry resided If the backups excluded any files that resided in the directory you may not be able to restore the system identically to the previous configuration m Defective hardware has been replaced Before starting verify that you have the following m Windows system software to reinstall on the NetBackup client that being restored Reinstall the same type and version of software that was previously used Disaster recovery 195 About disk recovery procedures for Windows NetBackup client software to install on the client that being restored Special drivers or other software that is required to make 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 The partitioning and formatting scheme that was used on the system to be restored You must duplicate that scheme during Windows installation To recover a Windows client disk 1 Install a minima
322. this information could include the etc hosts file and NIS and DNS if used Example of host name and service entries on UNIX PC clients The following illustration shows a NetBackup master server with PC clients defined here as Windows NetWare or Macintosh clients Server configuration is the same as it is for UNIX clients These clients do not have inetd conf entries Troubleshooting procedures 61 Verifying host name and service entries in NetBackup Figure 2 3 UNIX PC clients UNIX jupiter Master Server Ethernet Policy Client List mars NetWare Target saturn Windows igi Client Client jupiter mars saturn pluto y bp ini usr openv netbackup bp conf bp p SERVER jupiter ClientName mars CLIENT_NAME jupiter servers master jupiter etc inetd conf clients M bpcd see note 1 browser jupiter NetBackup Client Properties dialog box tcpip etc services bpcd 13782 Servers NetBackup services pee Server List jupiter bpcd 13782 tcp bpcd bprd 13720 tcp bprd A bpdbm 13721 tcp bpdbm 7 Volume Manager services Client Name saturn vmd 13701 tcp vmd Network tl8cd 13705 tcp tl8cd odid 13706 tcp odld NetBackup Client Service Port 13782 NetBackup Request Service Port 13720 Consider the following notes about Figure 2 3 m The following is the complete inetd conf entry bpcd stream tcp nowait root usr openv ne
323. ting NetBackup images in the following manual See NetBackup Administrator s Guide Volume I Note When the disk image is imported NetBackup does not recover the original catalog entry for the image Instead a new catalog entry is created About recovering the master server disk for Windows The procedure in this section explains how to recover data if one or more disk partitions are lost on a Windows NetBackup master server 188 Disaster recovery About disk recovery procedures for Windows The following two scenarios are covered Windows is intact and not corrupted The system still starts Windows but some or all other partitions are lost NetBackup software is assumed to be lost See Recovering the master server with Windows intact on page 188 All disk partitions are lost Windows must be reinstalled which is a total recovery These procedures assume that the NetBackup master disk was running a supported version of Windows and that the defective hardware has been replaced See Recovering the master server and Windows on page 191 For NetBackup master and media servers the directory locations of the NetBackup catalog become an integral part of NetBackup catalog backups Any recovery of the NetBackup catalog requires the identical directory paths or locations be created before the catalog recovery Recovering the master server with Windows intact This procedure shows how to recover the NetBackup maste
324. ting network interface card performance on page 91 See About troubleshooting NetBackup in a SAN environment on page 93 Device configuration problem resolution An auto configuration warning message appears in the second panel of the Device Configuration Wizard if the selected device meets any of the following conditions m Not licensed for NetBackup server m Exceeds a license restriction m Has some inherent qualities that make it difficult to auto configure 30 Troubleshooting procedures Device configuration problem resolution The following messages relate to device configuration along with their explanations and recommended actions Table 2 5 Recommended actions for device configuration messages Drive does not support The drive does not return its serial number Ask the manufacturer for a newer firmware serialization Note that some manufacturers do not support version that returns serial numbers if serial numbers Although automatic device available or manually configure and operate configuration does not function optimally the drive without a serial number the drive can be manually configured and operated without its serial number Robot does not support The robot does not return its serial number Ask the manufacturer for a newer firmware serialization or the serial numbers of the drives that are version that returns serial numbers if contained within it Note that some manufa
325. ting procedures 43 Resolving network communication problems with UNIX clients Steps for resolving network communication problems with UNIX clients continued Step 2 Verify network connectivity Verify network connectivity between client and server by trying to ping the client from the server ping clientname Where clientname isthe name of the client as configured in the NetBackup policy configuration in etc hosts and in NIS and DNS if applicable For example to ping aclient that is named ant ping ant ant nul nul com 64 byte packets 64 bytes from 199 199 199 24 icmp _seq 0 time 1 ms ant nul nul com PING Statistics 2 packets transmitted 2 packets received 0 packet loss round trip ms min avg max 1 1 1 Also try ping from the client to the server If ping succeeds in both instances it verifies connectivity between the server and client If ping fails you have a network problem outside of NetBackup that must be resolved before you proceed Some forms of the ping command let you ping the bpcd port on the client as in the following command ping ant 13782 Or ping ant bpcd 44 Troubleshooting procedures Resolving network communication problems with UNIX clients Table 2 8 Steps for resolving network communication problems with UNIX clients continued Step 3 Ensure that the client listens on the correct port for the bpcd connections Troubleshooting procedures 4
326. top and restart all NetBackup services m On UNIX usr openv netbackup bin bp kill_ all usr openv netbackup bin bp start_all m On Windows install path NetBackup bin bpdown install _path NetBackup bin bpup About troubleshooting duplication to a remote master Duplicate to remote master operations are characteried by storage lifecycle policies in at least two NetBackup master server domains Verify that the two master servers follow these rules m The name of the storage lifecycle policy in the source master server domain must match the name of the storage lifecycle policy in the target master server domain The names are case sensitive Troubleshooting procedures 81 About troubleshooting duplication to a remote master m The name of the data classification used by the storage lifecycle policy in the source master server domain must match the name of the data classificationn in the storage lifecycle policy in the target master server domain The names are case sensitive m The duplicate to remote master copy in the source storage lifecycle policy must use hierarchical duplication and specify a source copy with a residence capable of replication The disk pool replication column must show Source m The storage lifecycle policy in the target domain must specify an import for its first copy The residence for the import must include the device that is the replication partner of the source copy in the source storage lifecycle po
327. tores the entire NetBackup relational database which includes the following m NBDB database including the EMM database m BMR database if applicable m NetBackup policy files m Backup image files m Other configuration files If the EMM server is located on a remote computer the NBDB database is recovered on the remote computer 206 Disaster recovery How to recover a catalog from a backup 10 11 12 The wizard displays the recovery progress NetBackup Catalog Recovery Wizard xj Recovering Catalog Wat while the catalog is being recovered N 09 15 29 697 001 INF TAR EXITING WITH STATUS 0 09 15 29 697 001 INF TAR RESTORED 248 OF 248 FILES SUCCESSFULLY 09 15 29 697 001 INF TAR KEPT 0 EXISTING FILES 09 15 29 697 001 INF TAR PARTIALLY RESTORED 0 FILES If the recovery is not successful consult the log file messages for an indication of the problem The final panel announces that the full recovery is complete Each image file is restored to the proper image directory and the NetBackup relational databases NBDB and optionally BMRDB have been restored and recovered If this step is part of a server recovery procedure complete the remaining steps in the appropriate Server Disk Recovery procedure NetBackup does not run scheduled backup jobs until NetBackup is stopped and restarted Before you restart NetBackup protect the media that contains the backups that were successfully performed a
328. trator pushes a restore to a client from a server For a user restore the destination client and the requesting client are the same For an administrator restore the administrator can specify a different name for the destination client By the time these names appear in the bpra debug log the requesting client name has been translated into the client s configured name The name that used to connect back to the client to complete the restore is either the client s peername or its configured name The type of restore request for example from root on a server from a client to a different client and so on influences this action When you modify client names in NetBackup policies to accommodate specific network paths the administrator needs to consider m The client name as configured on the client For example on UNIX the client name is CLIENT NAME in the client s bp conf file On a Windows client it is on the General tab of the NetBackup Client Properties dialog box To open this dialog box select NetBackup Client Properties from the File menu in the Backup Archive and Restore interface m The client as currently named in the policy configuration m Client backup and archive images that already exist as recorded in the images directory on the master server On a UNIX or Linux server the images directory is usr openv netbackup db On a Windows NetBackup server the images directory is install_path NetBackup db images 3
329. turns serial numbers if available or manually configure and operate the drive robot without serial numbers Table 2 5 continued Troubleshooting procedures 31 Device configuration problem resolution Recommended actions for device configuration messages Ask the manufacturer for a newer firmware version that returns serial numbers if available Or manually configure and operate the drive and robot without serial numbers Robot drive number is unknown Either the drive or robot does not return a serial number Note that some manufacturers do not support serial numbers Although automatic device configuration does not function optimally the drive or robot can be manually configured and operated without a serial number Drive is in an unlicensed robot The drive is in a robotic library that cannot be licensed for NetBackup server Since the robot cannot be licensed for NetBackup server any drives that were configured in that robot are unusable Configure a drive that does not reside in the unlicensed robot Drive s SCSI adapter does not support pass thru or pass thru path does not exist A drive was found that does not have a SCSI pass through path configured The possible causes are m The drive is connected to an adapter that does not support SCSI pass through m The pass through path for this drive has not been defined Change the drive s adapter or define a pass through path for th
330. ubleshooting procedures Frozen media troubleshooting considerations See Frozen media troubleshooting considerations on page 71 See About conditions that cause media to freeze on page 72 About conditions that cause media to freeze The following conditions can cause media to freeze m The same media has excessive errors during backup An example of the log entry is as follows FREEZING media id E00109 it has had at least 3 errors in the last 12 hour s Causes and resolutions for this problem include Dirty drives Clean the drives that are freezing the media according to the manufacturer s suggestions One of the first symptoms of a dirty drive is frozen media The drive itself Check for tape device errors that are reported by the operating system logs or by the device driver If any are found follow the hardware manufacturer s recommendations for this type of error Communicationissues Check for SCSI or HBA device errors that are reported by the at the SCSI or host bus operating system logs or by their driver If any are found adapter HBA level follow the hardware manufacturer s recommendations for this type of error Drive not supported Ensure that the tape drives appear on the hardware compatibility list as supported for NetBackup This list is located on the following Symantec support Web site http www symantec com business support overview jsp pid 15143 Media not supported Ensure that the media is su
331. ueries about product features and functionality The Technical Support group also creates content for our online Knowledge Base The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion For example the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates Symantec s support offerings include the following m Arange of support options that give you the flexibility to select the right amount of service for any size organization m Telephone and or Web based support that provides rapid response and up to the minute information m Upgrade assurance that delivers software upgrades m Global support purchased on a regional business hours or 24 hours a day 7 days a week basis m Premium service offerings that include Account Management Services For information about Symantec s support offerings you can visit our Web site at the following URL www symantec com business support All support services will be delivered in accordance with your support agreement and the then current enterprise technical support policy Contacting Technical Support Customers with a current support agreement may access Technical Support information at the following URL www symantec com business support Before contacting Technical Support make sure you have satisfied the system r
332. ues a single request with a request ID to nbrb for all resources nbjm that are required by a job nbrb gets the storage unit tape drive and media id information from nbemm and allocates client and policy resources nbrb returns to nbjm an allocation sequence that contains one allocation for each resource each allocation contains a unique ID nbrb also returns allocation data for the specific resource type nbrb also returns the request ID along with the allocations so that nbjm can correlate the response with the right request and job Note that nbrb allocates all resources that are included in a request If the resources are temporarily unavailable the request is queued in nbrb If the resource cannot be allocated nbrb fails the request nbjm starts the backup by using the client daemon bpcd to start the backup and restore manager bpbrm For normal backup not snapshots nbjm starts bpbrm on the media server which may or may not be the same system as the master server Backup and restore Starts bptm manager bpbrm Starts the actual backup or archive by using the client daemon bpcd to start the backup program and archive program bpbkar on the client Backup and restore functional overview 241 Backups and archives UNIX clients Table A 1 Backup to tape or disk sequence of operation continued Backup and archive manager bpbkar Sends the information about files within the image to bpbrm
333. uld be adequate to list only the master server name for the local network interface to the client system or media server For example list meteor for pluto For the network that is shown the only configurations that are required are the differences for the policy client list and the server list If all the standard networking files hosts WINS NIS DNS and routing tables are set up correctly all required network connections can be made A problem exists to restore the files in the following situation the master server system is a router that hides the originating host name when it routes requests between networks For example if pluto were on FDDI token ring the master server would use meteor as the peer name when it forwards the request to NetBackup NetBackup would then interpret the request as coming from a host that is named meteor which was not in the client list The restore would fail The solution in this case is identical to the solution that is discussed in the following About the bpcintcmd utility The bpc1ntcma utility resolves IP addresses into host names and host names into IP addresses It uses the same system calls as the NetBackup application software The following directory contains the command that starts the utility Windows install_path NetBackup bin UNIX usr openv netbackup bin Troubleshooting procedures 67 About the bpclntcmd utility On Windows run this bpclntcmd command in an MS DOS command
334. um of the disk space that each originator consumes If none of the originators overrides the NumberOfFiles and MaxLogFileSizekB settings then the total disk space that unified logging consumes is as follows Number of originators default MaxLogFileSizeKkB default NumberOfFiles Use the vxlogcfg command to list the current unified logging settings For example assume the following E vxlogmgr a p NB is configured as a cron job witha frequency of one hour m No originators override default settings for MaxLogFileSizeKB or NumberOfFiles m The number of active NetBackup originators on the host is 10 Typical of a NetBackup master server that is not running BMR or NDMP m The default MaxLogFileSizekB is equal to 5120 m The default NumberOfFiles is equal to 3 To calculate the total disk space that unified logging consumes insert the values from the example into the previous formula The results are as follows 10 5120 3 KB 15 360 KB of additional disk space used each hour About legacy logging Legacy logging and unified logging are the two forms of debug logging used in NetBackup In legacy debug logging each process creates logs of debug activity Using logs 125 About legacy logging in its own logging directory All NetBackup processes use either unified logging or legacy logging See About unified logging on page 102 To enable legacy debug logging on NetBackup servers you must first crea
335. uns If you edit the InetServ object policy run the inetexp command to export the InetServ object policy to the etc inetd conf and etc services files This command keeps these files in sync with the InetServ object policy Run the following command 46 Troubleshooting procedures Resolving network communication problems with UNIX clients Table 2 8 Steps for resolving network communication problems with UNIX clients continued to inform the inetd daemon of the changes to its configuration file refresh s inetdorkill 1 InetdPID Step 4 Connect to the client through telnet telnet to bpcd on the client If it succeeds keep the connection until after you perform step 5 then terminate it with Ctrl c telnet clientname 13782 Where clientname is the name of the client as configured in the NetBackup policy configuration etc hosts and also in NIS and DNS if applicable For example telnet ant bpcd Trying 199 999 999 24 Connected to ant nul nul com Escape character is In this example telnet can establish a connection to the client ant m Ifthe telnet succeeds then inetd on the client is configured correctly It can pass its connection to bpcd and NetBackup should also be able to establish a connection m Iftelnet doesn t work ensure that the inetd conf file and etc services files on both the server and client are correct and match By default these are as follows In etc servic
336. up structure CommandCentral Storage provides a consistent view of the entire SAN against which to measure performance It gives NetBackup administrators the data they need to request changes of and collaborate with the SAN administrators It helps NetBackup administrators when they design configure implement or modify solutions in response to changes in backup environments hardware applications demand CommandCentral Storage can help those responsible for managing a backup system in a SAN environment by integrating SAN management and backup operation information CommandCentral Storage can provide support during the following backup lifecycle stages m Design Use CommandCentral Storage during the design phase to determine the following m Where to deploy a backup system on the SAN m IfSAN redesign is required to meet backup windows at minimum hardware cost and application impact For example a backup design may not require the purchase of additional switches if it takes into account the following the performance trending reports that CommandCentral Storage keeps to determine the pattern of fabric utilization Or perhaps if you re zone the fabric through CommandCentral Storage it may provide sufficient bandwidth for meeting backup window requirements In addition CommandCentral Storage can provide visibility into recovery designs and fabric performance in the event of large restores that critical business operations require
337. uplication to remote master job gives the catalog entries for this copy to the storage device so the job does not have to read the entire image Automatic import jobs simply read the catalog record off the storage device and add it into its own catalog This process is so fast that NetBackup batches images for import for efficiency The state where NetBackup has been notified but the import has not yet occurred is called pending import See the NetBackup Administrator Guidef or tuning the batching interval of the import manager process and other information about automatic import The notify event from the storage server provides the image name where on the storage server to read the catalog for this image and the name of the storage lifecycle policy that processes the image Images for automatic import jobs are batched by storage lifecycle policy name and disk volume The import job consumes an input output stream on the disk volume To view images that are pending import run the following command nbstlutil pendimplist U Image Master Server bayside min veritas com Backup ID gdwinlin04 1280299412 Client gdwinlin0d4 Backup Time 1280299412 Wed Jul 28 01 43 32 2010 Policy none specified Client Type 0 Schedule Type 0 Storage Lifecycle Policy none specified Storage Lifecycle State 1 NOT STARTED Time In Process 0O Wed Dec 31 18 00 00 1969 0 none specified Data Classification ID Version
338. uration for media and device management SSO allows individual tape drives stand alone or in a robotic library to be dynamically shared between multiple NetBackup media servers or SAN media servers See the NetBackup Shared Storage Guide The following shows the shared storage option management process in the order presented m NetBackup Storage Migrator or users can initiate backups nbjm makes a mount request for the backup 292 Media and device management functional description Shared Storage option management process nbrb tells the EMM server to obtain a drive for the backup nbrb tells the device allocator DA in the EMM server to stop scanning the selected drive nbemm tells the appropriate media server the scan host for the selected drive to stop scanning the drive The stop scan request is carried out by means of oprd ltid and avrd in the media server s shared memory nbemm informs nbrb when scanning on the selected drive has stopped nbrb informs nbjm that the selected drive A is available for the backup nbjm conveys the mount request and drive selection to bptm which proceeds with the backup To protect the integrity of the write operation bptm uses SCSI reservations See How NetBackup reserves drives in the NetBackup Administrator s Guide Volume II The mount media operation is initiated bptm makes position checks on the drive to ensure that the drive has not been rewound by another appli
339. ut disk recovery procedures for UNIX and Linux To recover the master server when the root partition is lost 1 Load the operating system on an alternate boot disk using the same procedure as you would normally use for the server type On the alternate disk create the partition and directory where NetBackup its catalogs if applicable and databases resided on the original disk By default they reside under the usr openv directory Verify that the operating system works that any required patches are installed and that specific configuration settings are made Take corrective action as needed Install NetBackup on the alternate disk Install only the robotic software for the devices that are required to read backups of the NetBackup catalogs and regular backups of the disk being restored If a non robotic drive can read these backups no robot is required Install any NetBackup patches that had been previously installed See the documentation that was included with the patch software If the catalog directories differ from those in the NetBackup catalog backups recreate that directory structure on disk before you recover the catalog Examples of those directories are the following m Use of symbolic links as part of the NetBackup catalog directory structure m Use of the NetBackup nbdb move command to relocate parts of the NetBackup relational database catalog If the recovery scenario involves restoring policy or catalog bac
340. verify and disk import true image restore from disk disk image deletion 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 legacy log directory on the server bpfis On clients bpfis creates and deletes snapshots Note that bpfis is part of the Snapshot Client add on product Started By bpbrm Stopped By Completion of operation Debug Log bpfis legacy log directory on the client or alternate client bphdb On SQL Oracle Informix Sybase DB2 and SAP database clients bphdb executes scripts to back up the database Started By Client user interface when the user starts a database backup operation Stopped By Completion of operation Debug Log bphdb legacy log directory on the client 276 Backup and restore functional overview NetBackup programs and daemons Table A 4 Backup daemons and programs continued bpjava msvc NetBackup Java master server application program This program runs on all NetBackup UNIX systems and authenticates the 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 bpjava msvc legacy log directory on the server bpjava usvc NetBackup Java user server application program This program services all requests from the Net
341. which directs the file information to the NetBackup file database The information is sent by means of bpdbm on the master server Transmits the backup image to bptm depending on one of the following whether the media server backs up itself optm and bpbkar are on the same host or back ups a client that resides on a different host If the media server backs up itself bpbkar stores the image block by block in shared memory on the media server If the media server backs up a client on a different host the bptm process on the server creates a child process of itself The child receives the image from the client by means of socket communications and then stores the image block by block in shared memory on the server Use the NOSHM file to force a media server that backs up itself to do the following create a child process and use socket communications as though the client is on a different host More information on the NOSHM file is available See the NetBackup Backup Planning and Performance Tuning Guide 242 Backup and restore functional overview Backups and archives UNIX clients Table A 1 Backup to tape or disk sequence of operation continued backup manager for The bptm process or bpdm process on the server takes the image tape bptm or disk from shared memory and directs it to the storage media bpd pdm If the storage media is tape bptm requests information for the first media and drive to use by exchanging
342. write existing files option which ensures that existing files are replaced with the backups m Start the restore Reboot the system which replaces any files that were busy during the restore When the boot process is complete the system is restored to the state it was in at the time of the last backup Disaster recovery 191 About disk recovery procedures for Windows Recovering the master server and Windows This procedure assumes that all disk partitions in Windows are lost To recover the master server and Windows 1 Install a minimal Windows operating system perform the Express install m Install the same type and version of Windows software that was used previously m Install Windows in the same partition that was used before the failure m Install any required patches Take corrective action as needed m Specify the default workgroup Do not restore the domain m Install and configure special drivers or other software that is required to get the hardware operational for example a special driver for the disk drive m Install SCSI or other drivers as needed to communicate with the tape drives on the system m Follow any hardware manufacturer s instructions that apply such as loading SSD on a Compaq system m Reboot the system when Windows installation is complete 2 Determine the install_path in which NetBackup is installed By default NetBackup is installed in the c Program Files VERITAS directory 3 Determin
343. x 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 legacy log directory on the client 284 Backup and restore functional overview NetBackup catalogs Table A 4 Backup daemons and programs continued 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 legacy log directory on the client windrvr6 On a Media Server that is enabled for SAN Client transfers using fibre channel windrvr6 is a kernel device driver used to communicate through the PCI bus to the target mode Fibre Channel Host Bus Adapters Started By Device driver that is started by the operating system at boot Solaris or by nbfdrv64 Linux Stopped By Device driver that is stopped by the operating system at shutdown Debug Log The host operating system handles the logging in the system messages log log var adm messages Solaris or var log messages Linux NetBackup catalogs The NetBackup catalogs contain the information that is used internally by NetBackup and reside in the usr openv netbac
344. xplained previously for tl8cd Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin tldcd command Stopped By Using the tldcd t command Stopping Itid or by using the tldcd t command Debug Log Errors are logged in the system log and robots debug log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option either by itself or through Itid tlhd The Tape Library Half inch daemon works in conjunction with tlhcd to handle requests to TLH robots that are in an IBM Automated Tape Library ATL tlhd provides the interface between the local Itid and the robotic control tlhcd in the same manner as explained previously for tl8d Started By Starting ltid or on UNIX independently by using the usr openv volmgr bin tlhd command Stopped By Stopping Itid or on UNIX independently by finding the PID process id and then using the kill command Debug Log Errors are logged in the system log and robots debug log Debug information is included by adding VERBOSE to the vm conf file On UNIX debug information is also included by starting the daemon with the v option either by itself or through Itid 302 Media and device management functional description Media and device management components Table B 2 Media and device management daemons and programs continued tlhed The Tape Library H
345. xtra disk space required for logs and temporary files For successful operation the NetBackup Administration Console requires extra disk space to store logs and temporary files The disk space should be available in the following locations On the host that is specified in the logon dialog box In usr openv netbackup logs user_ ops On the host where the console was started In usr openv netbackup logs user_ops nbjlogs If space is not available in the respective file systems you may experience the following Long waits for application response Incomplete data No response during logon Reduced functionality in the NetBackup interface for example only the Backup Archive and Restore and Files System Analyzer nodes appear in the tree Unexpected error messages Using logs 147 Troubleshooting error messages in the NetBackup Administration Console for UNIX m Cannot connect socket errors during logon to the NBJava application server m Unable to login status 35 cannot make required directory m bin sh null not found 1 m An exception occurred vrts nbu admin bpmgmt CommandOutputException Invalid or unexpected class configuration data lt the rest of the message will vary gt m Empty warning dialog boxes Enabling detailed debug logging The NetBackup Administration Console is a distributed application that allows administration of remote NetBackup servers All administration is accomplished through the appli
346. y nbsu displays its progress to standard output First it lists environment queries and then it lists the diagnostic commands that it runs as in the following example Program Files VERITAS NetBackup bin support gt nbsu Determining initial nbsu settings Determining OS environment Determining OS host services Determining identified network interface hostnames Determining NetBackup environment Querying nbsu diagnostic lists Determining nbsu diagnostics to run w N NFP RrPrFPH FPO Or OBR WNHER OO Executing nbsu diagnostics Executing diagnostic DEV scsi _ reg Registry query of HKEY LOCAL MACHINE hardware DeviceMap Scsi Executing diagnostic MM ndmp C Program Files VERITAS volmgr bin set_ndmp attr list C Program Files VERITAS volmgr bin set_ndmp_ attr probe lt hostname gt C Program Files VERITAS volmgr bin set_ndmp attr verify lt hostname gt Executing diagnostic MM tpconfig C Program Files VERITAS Volmgr Bin tpconfig d 4 0 nbsu successfully completed the identified diagnostic commands Creating support package Microsoft R Cabinet Maker Version 5 2 3790 0 Copyright c Microsoft Corporation All rights reserved 770 201 bytes in 36 files Total files 36 Bytes before 770 201 Bytes after 105 503 After Before 13 70 compression Time 0 67 seconds 0 hr 0 min 0 67 sec Throughput 1119 27 Kb second Using NetBackup utilities 161 About the NetBackup consistency check uti
347. y before any disaster 174 Disaster recovery Recommended backup practices Your organization also may have a recovery time objective RTO which is the expected recovery time or how long it takes to recover Recovery time is a function of the type of disaster and of the methods that are used for recovery You may have multiple RTOs depending on which services your organization must recover when High availability technologies can make the recovery point very close or even identical to the point of failure or disaster They also can provide very short recovery times However the closer your RTO and RPO are to the failure point the more expensive it is to build and maintain the systems that are required to achieve recovery Your analysis of the costs and benefits of various recovery strategies should be part of your organization s recovery planning Effective disaster recovery requires procedures specific to an environment These procedures provide detailed information regarding preparation for and recovering from a disaster Use the disaster recovery information in this chapter as a model only evaluate and then develop your own disaster recovery plans and procedures Warning Before you try any of the disaster recovery procedures in this chapter Symantec recommends that you contact technical support This topic provides information about NetBackup installation and if necessary catalog recovery after a system disk failure Syma
348. y list from bpdbm creates the policy client tasks determines when jobs are due to run and starts due jobs Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbpem terminate Debug Log On the server usr openv logs UNIX or install_path logs Windows See About unified logging on page 102 nbproxy Runs on the master server and the media server as a child of the process it serves nbproxy provides a thread safe API for the libraries that are not yet thread safe Started By the process that uses nbproxy as a proxy Stopped By stops the process that uses nbproxy Debug Log nbproxy legacy log directory on the server nbrb On the server that is defined as the EMM server the nbrb service accepts resource requests from nbjm acquires physical resources from nbemm and manages logical resources Started By Started when NetBackup starts Stopped By usr openv netbackup bin nbrb terminate Debug Log On the server usr openv logs UNIX or install_path logs Windows See About unified logging on page 102 ndmpagent Controls backup and restore operations on a NAS server ndmpagent is for remote NDMP backing up NDMP data to a drive that is configured in a Media Manager storage unit on a NetBackup media server Started By bpbrm Stopped By Completion of backup or restore Debug Log On the server usr openv logs UNIX or install_path logs Windows Se
349. y to bring it back up 2 If the drive is still down check the following for status 219 the required storage unit is unavailable and 213 no storage units available for use on the media server m Syslog m Device logs m NetBackup logs 3 Check the NetBackup logs for status 83 84 85 and 86 These codes relate to write read open position failures to access the drive 4 Try arobtest to determine connectivity If there is no connectivity the likely problem is with hardware 5 Fromthe master server select the robot or device the storage unit is associated with 6 Launch CommandCentral Storage for a view of the media server and devices Check the fabric connectivity whether any I O path devices are down Using CommandCentral Storage to troubleshoot the inability to discover a drive or robot in a SAN environment The following use case demonstrates how CommandCentral Storage can be integrated into a NetBackup troubleshooting procedure to investigate the SAN Troubleshooting procedures 97 About troubleshooting NetBackup in a SAN environment context of a backup system Most common NetBackup problems on SANs revolve around connectivity issues The NetBackup administrator installs a new device and runs the Device Configuration Wizard to discover and configure it The wizard does not see the newly installed device CommandCentral Storage topology is a good visual tool to check connectivity between the hosts and the devices
350. you can verify only the Media and Device Management part of the configuration To verify use the tpreq command to request a media mount Verify that the mount completes and check the drive on which the media was mounted Repeat the process until the media is mounted and unmounted on each drive from the host where the problem occurred If this works the problem is probably with the policy or the storage unit configuration When you are done tpunmount the media Step 8 Include a robot in the test policy 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 EMM database host for the robot Return to step 3 and repeat this procedure for the robot This procedure verifies that NetBackup can find the volume mount it and use the robotic drive Step 9 Use the robotic test utilities If you have difficulties with the robot try the test utilities See About robotic test utilities on page 311 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 The result is that it can cause media mount timeouts and prevent other robotic operations like robotic inventory and inject or eject from working Step 10 Enhance the t
351. ype More details are available on each media type See the NetBackup Device Configuration Guide The media is a tape formerly used for the NetBackup catalog backup For example the log entry may be the following FREEZING media id 000067 it contains Symantec NetBackup tm database backup data and cannot be used for backups The media is frozen because it is an old catalog backup tape which NetBackup does not overwrite by default The bp1abe1 command must label the media to reset the media header The media is intentionally frozen You can use the bpmedia command to manually freeze media for a variety of administrative reasons If no record exists of a specific job freezing the media the media may have been frozen manually The media is physically write protected If the media has a write protect notch that is set for write protection NetBackup freezes the media To unfreeze frozen media enter the following bpmedia command bpmedia unfreeze m mediaID h media_server The media_server variable is the one that froze the media If this item is unknown run the bpmedialist command and note the Server Host listed in the output The following example shows that media server denton froze media div008 bpmedialist m div008 Server Host denton Troubleshooting procedures 75 Resolving PBX problems ID rl images allocated last updated density kbytes restores vimages expiration last read lt STATUS lt lt

Symantec NetBackup™ Troubleshooting Guide: UNIX

Contents

Download Pdf Manuals

Related Search

Related Contents

Symantec NetBackup&trade; Troubleshooting Guide: UNIX

Contents

Download Pdf Manuals

Related Search

Related Contents

Symantec NetBackup™ Troubleshooting Guide: UNIX