278422

8/7/2019 278422

http://slidepdf.com/reader/full/278422 1/16

Status Code: 41network connection timed out

The server did not receive any information from the client for too long a period of time. This can occur when a network connection is broken during a backup or restore. This can also occur when a NetBackuptimeout is exceeded.

Status

Code

41

When does

the problem

occur?

During Backup Start of Backup

Network Issue

Go to

Section 6How many

clients are

affected?

Go to

Section 3

One

Many

Media Server Issues:

- Check NBU configuration and timeout values.- Check OS network settings or filesystem access.

Client Issues:

- Check Network configuration- Check OS network settings or filesystem access.

Go to

Section 1

Status Code 41: network connection timed out of 16

8/7/2019 278422


Table of Contents

1 NetBackup Status Code: 41 - Defined .................................................................................................. ....32 NetBackup Status Code: 41 - Overview ....................................................................................................33 General Troubleshooting Steps:.............................................................................................................. .54 Resolving Network Naming & Communication Problems .................................................................... ....6

4.1 UNIX Clients .....................................................................................................................................64.2 Windows Clients ...............................................................................................................................74.3 Firewalls and VNETD/VxPBX ............................................................................................................ .84.1 Verifying Host Names and Services Entries ......................................................................................94.2 Using bpclntcmd to confirm name resolution ....................................................................................12

5 Suggested NetBackup Logging ..............................................................................................................135.1 NetBackup logs – Windows ..............................................................................................................135.2 NetBackup logs – UNIX ...................................................................................................................14

6 The Network ........................................................................................................................................ ...156.1 Physical Network problems ..............................................................................................................156.2 Heavy Network Load ........................................................................................................................15

7 Hardware related Issues .........................................................................................................................168 Links .......................................................................................................................................................16


8/7/2019 278422


1 NetBackup Status Code: 41 - DefinedA Status code 41 is primarily related to two different system dependencies. These are networkcomponent addressing and network data communications.

Network component addressing is the design for naming every network device (computer, array,router, switch, etc.) using a unique identifier so each network device can be located by any other network device without confusion.

Network data communication is dependant on the supporting hardware, cabling and software thathandles the transmission and reception of data between each network device.

If either of these two network components fail during a backup or restore then NetBackup will likelyexit with a status code 41.

NetBackup relies on the rules that govern the TCP/IP network protocol for successfulcommunication. The concepts of this network protocol as it relates to network communication arefurther defined with the OSI model where ISO outlines the seven network layers. NetBackupoperates primarily at the application layer (layer 7) but depends on stability in at least layers 1 – 4

for dependable operation.

The following link can be used for additional information on the ISO/OSI model:http://www.webopedia.com/quick_ref/OSI_Layers.asp

2 NetBackup Status Code: 41 - OverviewThe NetBackup exit status code 41 will generate the message “network connection timed out”. Thisindicates the server did not receive any information from the client for too long a period of time.

The following Recommended Actions can be taken for this error code:

1. On UNIX or Windows clients, check for the following problems with the bpbkar client process.

On Windows clients: The bpbkar client process may not be hung, but due to the files and directories it is scanning, ithas not replied to the server within the Client Read Timeout or Client Connect Timeout period.This has been known to occur during incremental backups when directories have thousands of unmodified files.For this case, launch the GUI and go to Host Properties > Master Servers section to changeClient connect timeout or Client read timeout. These settings are in the Timeouts > UniversalSettings tab. The default for these timeouts is 300 seconds.

On UNIX, Linux, Mac OSX clients:The bpbkar client process may be hung on a specific file or directory. For this case, addVERBOSE = 5 to the following to the client’s /usr/openv/netbackup/bp.conf file. Then as root on

the client execute:

# touch /usr/openv/netbackup/bpbkar_path_tr# mkdir /usr/openv/netbackup/logs/bpbkar

Then retry the operation. The file named /usr/openv/netbackup/logs/bpbkar/log.<date> willcontain the names of the files before bpbkar processes them. The last file SelectFile: entry in thelog will be the name of the file being accessed by NBU when the problem arose.


http://www.webopedia.com/quick_ref/OSI_Layers.asp

http://www.webopedia.com/quick_ref/OSI_Layers.asp

8/7/2019 278422


Note: This procedure can be used to isolate other, unknown bpbkar hangs.When NetBackup hangs on a file due to mandatory file locking NetBackup can be configured toskip the locked files by setting LOCKED_FILE_ACTION = SKIP in the

/usr/openv/netbackup/bp.conf file on the client.

The bpbkar client process may not be hung on a file with mandatory locking, but due to the

number of files and directories it is scanning, it has not replied to the server within the configuredtimeout. This can occur during backups when directories have thousands of unmodified files, or during restores of sparse files that have thousands of holes. It has also been seen when backingup file systems or directories that reside on optical disk, which is considerably slower thanmagnetic disk.

For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT

values in the server’s /usr/openv/netbackup/bp.conf file. The default for theCLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds.

After investigating the problem, delete the /usr/openv/netbackup/logs/bpbkar directory, sincethe log files can become quite large and are not deleted automatically. Alsodelete /usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log files thanneeded the next time you create directory /usr/openv/netbackup/logs/bpbkar .

2. On Windows systems, disable the following file:<install_path>\VERITAS\NetBackup\bin\tracker.exe

• Repair hard drive fragmentation. You could try an application called Diskeeper Lite, which ispart of the Windows NT Resource Kit.

• Make sure there is enough space available in \temp.

3. If the server cannot connect to the client, create bpcd or bpbkar debug log directories on theclient. Then retry the operation and check the resulting logs. If these logs do not provide a clue,create a bpbrm debug log on the media server. Then retry the operation again and check theresulting debug log.

If the UNIX /usr/openv/netbackup/logs/bpbrm/log.<date> file has entries similar to the

following then the problem is likely to be found in the routing configuration on the server.

<2> bpbrm hookup_timeout: timed out waiting during the client hookup<2> bpbrm Exit: client backup EXIT STATUS 41: network connection timed out

Verify that the client IP address is correct in the name service that is being used. OnUNIX, if both NIS and DNS files are used, verify that they match.

Also, see “Resolving Network Naming & Communication Problems” Section 4.

4. When using an AIX token ring adapter and when the routed daemon is running, a timeout canoccur because of the token ring adapter. The token ring adapter creates dynamic routes whichcan cause the routed daemon to crash.

5. For a FlashBackup client, this can happen if the file system being backed up is very large andhas a very large number of files. It can also occur if a large number of concurrent data streamsare active at the same time. The corrective action is to add CLIENT_READ_TIMEOUT to the

/usr/openv/netbackup/bp.conf file and set it to increase the timeout interval.

6. Make sure all recommended NetBackup patches have been installed. Check the VERITASsupport web site for current patch information.


8/7/2019 278422


To download the latest version of NetBackup 4.5, visit the Support Web site:http://support.veritas.com/menu_ddProduct_NETBACKUPDC_view_DOWNLOAD.htm

To download the latest version of NetBackup 5.x, visit the Support Web site:http://support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLOAD.htm

Run the NetBackup Configuration Validation Utility (NCVU) for the associated NetBackup nodes.Section two of the NCVU output will show which patches are applied.

7. Add the CLIENT_READ_TIMEOUT values to the master server, media server and client when a

NetBackup database extension product is installed. The values should all be the same for eachserver. The value set is dependent on the size of the database being backed up. See theNetBackup System Administrator’s Guide for more information on CLIENT_READ_TIMEOUT.

8. If enhanced authentication is being used, ensure that it’s configured correctly. See theConfiguring the NetBackup-Java console chapter in the NetBackup System Administrator'sGuide for details on enhanced authentication.

For example: If host A is configured to use enhanced authentication with host B, but host B isnot configured to use enhanced authentication with host A. Connections from host B to host Aare likely to fail with status code 41. Connections from host A to host B are likely to fail withauthentication errors (status code 160).

3 General Troubleshooting Steps:An important factor in determining the most likely cause of a Status 41 is to note at what point duringthe backup or restore the error occurs.

If the Status 41 occurs immediately at the onset of the backup the problem is generally related toNetwork problems. If the Status 41 occurs after a significant amount of data has been transferred, or occurs at the end

of the backup then client-side resource issues, NetBackup Configuration issues, or Hardware issuesshould be further explored.

In most cases it will be necessary to review logs from a time in which the error is being returned todetermine where in the backup the failure is occurring. Refer to the NetBackup TroubleshootingGuide for information on how to enable NetBackup logging. The steps listed below include the logsthat will be most useful in troubleshooting a status code 41.

Troubleshooting Steps:

• Enable and review the NetBackup bptm, bpbrm and bpcd logs on the NetBackup MediaServer with the verbosity set to 5.

• Enable and review the NetBackup bpcd, bpbkar (for backups) and tar (for restores) logs onthe NetBackup client with the verbosity set to 5.

• Review the Operating Systems system logs for any hardware related error messages. Onthe Windows platform see System & Application Event Viewer logs.


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

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

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

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

8/7/2019 278422


4 Resolving Network Naming & Communication Problems

The following procedure is for resolving NetBackup communications problems, such as thoseassociated with NetBackup status code 41. There are two variations of this procedure: one for UNIXclients and another for PC clients.

Note: In all cases, ensure that your network configuration is working correctly outside of NetBackupbefore trying to resolve NetBackup problems.

4.1 UNIX ClientsFor UNIX clients, perform the following steps. Before starting this procedure, add the VERBOSE = 5

option to the /usr/openv/netbackup/bp.conf file. Also, create a /usr/openv/netbackup/logs/bpcddebug log directory on your server and clients and a /usr/openv/netbackup/logs/bprd logdirectory on the server. During subsequent retries, the debug logs will provide detailed debuginformation that will be useful in analyzing the problem.

To resolve network communication problems with UNIX clients:

1. For new or modified configurations:

• Check any recent modifications to ensure that they did not introduce the problem.

• Ensure that the client software was installed properly.

• Ensure that the client operating system is supported by the client software.

• Check the client names, server names, and service entries in your NetBackupconfiguration as explained in “Verifying Host Names and Services Entries” section 4.4.

• Check the verbose bprd debug log on the server to determine what occurred when theserver received the request.

• Pay special attention to NIS or DNS updates that are required. Failing to properly updatethese services is a common source of network problems with NetBackup.

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

from the server.

# ping <client_name>

For example, to ping a client named ant:# ping antant.nul.nul.com: 64 byte packets64 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 lossround-trip (ms) min/avg/max = 1/1/1

Then try ping from the server from the client. If ping succeeds in both instances, it verifies basicconnectivity between the server and client. If ping fails, a network problem outside of NetBackup

exists that must be resolved before proceeding.

3. To verify basic client to master server communications, use the bpclntcmd utility. When run ona NetBackup client, the -pn and -sv options initiate inquiries to the NetBackup master server asconfigured in the bp.conf file on the client. The master server then returns information to therequesting client. For more information, see “Using bpclntcmd” Section 4.4.


8/7/2019 278422


4.2 Windows Clients

To resolve network communication problems with Windows clients:

1. Enable logging before retrying the failed operation:

• Increase the Verbose logging level to five and General logging level to two on the client.

To change these values start the Backup, Archive, and Restore interface and go to File> NetBackup Client Properties > Troubleshooting.

• On the NetBackup master server, create a bprd directory and on the clients create a<install_path>\VERITAS\NetBackup\logs\bpcd directory.

2. If this is a new client, verify the client and server names in the NetBackup configuration asexplained in “Verifying Host Names and Services Entries” section 4.4.

3. Verify basic network connectivity between client and server by pinging from the server to theclient and from the client to the server. Use the following command:

% ping <hostname>

The <hostname> is the name of the host as configured in the NetBackup policy configuration.This name should also match the WINS and DNS configuration or the hosts file in the systemdirectory:

• %SystemRoot%\system32\drivers\etc\hosts (Windows NT/2000, XP, 2003)

If ping succeeds this verifies basic connectivity between the server and client.If ping fails, a network problem exists outside of NetBackup that must be resolved beforeproceeding.

4. Verify that the NetBackup Request Service (bprd) Port number on Microsoft Windows andNetWare clients is the same as on the server (by default, 13720).

5. Verify that the hosts file or its equivalent contains the NetBackup server name. The hosts files

for different operating systems are located in:• %SystemRoot%\system32\drivers\etc\hosts (Windows NT/2000, XP or 2003)

• SYS:etc\hosts (NetWare)

• /etc/hosts (UNIX)

6. Verify client-to-server connectivity by using ping, telnet or ftp from the client back to the server.

7. For a NetWare client, ensure that the server is not trying to connect when a backup or restoreis already in progress on the client. Attempting more than one job at a time on these clients,results in a “can’t connect” or similar error.

8. Use the bpclntcmd utility to verify basic client to master server communications. When run ona NetBackup client, the -pn and -sv options initiate inquiries to the NetBackup master server

configured in the server list on the client. The master server then returns information to therequesting client. For more information, see “Using bpclntcmd” section 4.5.

9. Verify that the client operating system is supported by the client software.


8/7/2019 278422


4.3 Firewalls and VNETD/VxPBX Firewalls create a unique set of circumstances that have the potential to cause Exit Status 41problems by directing communication through an independent device or application that has theability to limit port functionality. This in-turn can take control away from NetBackup processescausing timeouts or delays in data transmission.

The VERITAS Network Daemon, or vnetd, was introduced in NetBackup 4.5GA. The primary goal of vnetd was to provide the ability to configure communication in NetBackup environments protected byfirewalls. Since NetBackup connectivity relies primarily on TCP connections the goal of vnetd in theNetBackup 4.5 GA release was to resolve the "call-back" or "connect-back" issue. This is whereconnections made back to a NetBackup Server by client processes (bpbkar , bpcd, etc.) were madeto destination TCP ports randomly chosen from a predefined range. Instead, with vnetd, we can nowconfigure these connect-backs to NetBackup Servers to use a single port - vnetd port 13724.

In addition, starting in NetBackup 4.5 FP6, configuring "Reduced Firewall Usage" provides thecapability where vnetd can now make connections to the standalone daemons bprd, bpdbm,bpjobd, vmd and robotic control daemons.

Benefits of using "vnetd" instead of Standalone Daemon Port Numbers:• Applicable to standalone daemons such as bprd, bpdbm, bpjobd, vmd, and robotic

daemons.

• Forces connections made to the standalone daemons to connect to the destination server'svnetd port instead, and vnetd then passes the socket to the applicable standalone daemon.

Configuration of vnetd for NBU servers is done in the GUI under both Master and Media Server Host properties using the Firewall tab, as explained above. You would enter the hostname(s) of theservers you want the current server to connect to using Automatic, vnetd only, or daemon only.

For a NetBackup server, this can also be configured manually in the bp.conf file if the GUI is notavailable. If the bp.conf file on a server shows "CONNECT_OPTIONS = <servername> 0 1 1" this

indicates vnetd only instead of the usual daemon ports when connecting to the specified server.

Note: The last digit in the entry enables the use of vnetd.

In order to force connections made to vmd and robotic daemons in a SAN environment to use vnetd,the "CONNECT_OPTIONS = <servername> 0 1 1" must be added to all the vm.conf files of the

Master Server and all Media Servers.

If configuring a NetBackup client to user vnetd to talk back to the master or media server do not usethe firewall tab on the server. Still use the properties window for the master, but go through [ClientAttributes] -> [Connect Options]. Adding the client to the firewall tab will yield unpredictable results.

One can also see if a NetBackup client has been configured to use vnetd by using the bpclientcommand on the master server.

Command:# /usr/openv/netbackup/bin/bpclient –L -client <name-of-client>

The last line of the bpclient output shows the connect options for the client.

VxPBX - VERITAS Private Branch ExchangeStarting in NetBackup 6.0GA, VxPBX goes beyond vnetd to perform many of the same socketstreamlining functions but with greater performance. It acts as a one time communication broker connecting authorized client services with server services.


8/7/2019 278422


From the NBU 6.0 Manual:NetBackup 6.0 contains features that are dependent on a new Common Services Framework (CSF)called, VERITAS Private Branch Exchange (VxPBX). VxPBX helps limit the number of TCP/IP portsused by many new features in NetBackup, such as IRM and EMM. VxPBX is required for allNetBackup uses. It is installed with NetBackup 6.0GA

4.1 Verifying Host Names and Services EntriesThis procedure is useful if you encounter problems with host names or network connections andwant to verify that the NetBackup configuration is correct.

Note: For more information on host names, refer to the “Networks and Hostnames” section in thisdocument and to the “Rules for Using Host Names in NetBackup” appendix in the NetBackupSystem Administrator’s Guide.

To verify the client and server host names in NetBackup:

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

On Windows servers, Windows clients and Non Target NetWare clients, check the General tab

in the NetBackup Client Properties dialog and the Servers tab in the Specify NetBackupMachines and Policy Type dialog box. To display these dialog boxes start the Backup,Archive, and Restore interface on the client.For the General tab, click NetBackup Client Properties on the File menu.For the Servers tab, click Specify NetBackup Machines and Policy Type on the File menu. Onthe Servers tab, ensure that there is a server entry for the master server and each mediaserver.

On Windows systems, the correct server must be designated as the current master server inthe list. Stop and restart the NetBackup daemons if these names are changed.

• On the General tab, verify that the client name setting is correct and matcheswhat is in the policy client list on the master server.

• On a master or media server, ensure there is a server entry for each Windows

administrative client that can be used to administer that server.• If a host name is misspelled in the bp.conf file (UNIX) or via the servers list(Windows) on the master server, or if a host name cannot be resolved viagethostbyname, the following error messages will be logged in the NetBackup error log:Gethostbyname failed for <hostname>:<h_errno_string> (<h_errno>)One or more servers was excluded from the server list becausegethostbyname() failed.

Make the above changes on the appropriate tabs in the properties dialog boxes on aWindows NetBackup server.

On UNIX & Linux NetBackup servers and clients, and Macintosh clients, check the server andclient name entries in the bp.conf file:

• Ensure there is a SERVER entry for the master server and each media server inthe configuration. The master server must be the first name in the list. Remember, if you add or modify SERVER entries on the master server, you must stop and restartbprd and bpdbm before the changes take effect.

• Ensure that the CLIENT_NAME option (if included) is correct and matches whatis in the policy client list on the master server.

• The bp.conf file is in the /usr/openv/netbackup directory on UNIX clients and itis in the Preferences:NetBackup folder on Macintosh clients. Users on UNIX clientscan also have a personal bp.conf file in their home directory. A CLIENT_NAME optionin $HOME/bp.conf overrides the one in /usr/openv/netbackup/bp.conf .


8/7/2019 278422



8/7/2019 278422


On NetWare clients, check the openv\netback\bp.ini file to ensure that:

• There is a SERVER entry for the master server and each media server in theconfiguration. The master server must be the first name in the list.

• The ClientName entry and the entries in the [clients] section are correct andmatch what is in the policy client list on the master server.

• On the master server, see if someone has created any required

/usr/openv/netbackup/db/altnames files (UNIX)<install_path>\NetBackup\db\altnames files (Windows).

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

2. Verify that each server and client has the required entries for NetBackup reserved portnumbers.

a. On NetBackup servers, check the services files to ensure that they have entries for:

• bpcd and bprd

• vmd

• bpdbm

• Processes for configured robots (for example, tl8cd). See the Media Manager System Administrator’s Guide for a list of these processes.

b. On UNIX, Windows, and NetWare clients, verify the NetBackup client daemon or servicenumber, and the request daemon or service port number.

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

• On Microsoft Windows clients, verify that the NetBackup Client Service Portnumber and NetBackup Request Service Port number on the Network tab in theNetBackup Client Properties dialog match the settings in the services file. To displaythis dialog, start the Backup, Archive, and Restore interface on the client and clickNetBackup Client Properties on the File menu.

The values on the Network tab are written to the services file when the NetBackup Clientservice starts.The services file is located in:

%SystemRoot%\system32\drivers\etc\services (Windows NT/2000, XP or 2003)openv\netbackup\bp.ini (NetWare clients, check the BPCD and BPRD entries)

/etc/services (UNIX, Linux, Mac OSX)

3. On UNIX servers and clients, verify the /etc/inetd.conf file to has the following entry:bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

4. On Linux, Mac OSX, & BSD servers and clients, verify that the file /etc/xinetd.d/bpcd iscorrect. The file should look similar to the following:{

disable = nosocket_type = streamprotocol = tcpwait = no

user = rootserver = /usr/openv/netbackup/bin/bpcd

}

5. On Windows servers and clients, verify that the NetBackup Client service is running. 6. If you are using NIS in your network, update those services to include the NetBackup

information that is added to the /etc/services file.


8/7/2019 278422


7. The hostname information in NIS, DNS and hosts files must correspond to what is in the policyconfiguration and the entries in the following:

• On Windows NetBackup servers, Microsoft Windows clients, and Non Target NetWareclients, check the General tab in the NetBackup Client Properties dialog and the Serverstab in the Specify NetBackup Machines and Policy Type dialog. To display these dialogs,start the Backup, Archive, and Restore interface on the client. For the General tab, click

NetBackup Client Properties on the File menu; for Servers tab, click Specify NetBackupMachines and Policy Type on the File menu.

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

• The openv\netback\bp.ini file on NetWare clients.

• Also, verify that reverse DNS addressing is configured.

4.2 Using bpclntcmd to confirm name resolutionThe bpclntcmd utility resolves IP addresses into host names and host names into IP addresses byusing the same system calls as the NetBackup application software. The bpclntcmd commandcan be found at:

For Windows: <install_path>\NetBackup\bin\bpclntcmd.exe

For UNIX: /usr/openv/netbackup/bin/bpclntcmd

On Windows, run this command in an MS-DOS command window. The bpclntcmd options thatare useful for testing hostname and IP address resolution are -ip, -hn, -sv and -pn.

# bpclntcmd -ip <IP_Address>

The -ip option looks up a specified IP address. The bpclntcmd uses gethostbyaddr() on the IPaddress and returns the hostname. This result is based on how the IP address is defined in thesystems DNS, WINS, NIS, or local hosts file entries. No connection is established with theNetBackup server. This should return the same hostname and IP information as the –hn option.

# bpclntcmd -hn <hostname>

The -hn option looks up a specific hostname. The bpclntcmd uses gethostbyname() on the

hostname to obtain the IP address. This result is based on how the hostname is defined in thesystems DNS, WINS, NIS, or local hosts file entries. No connection is established with theNetBackup server. This should return the same hostname and IP information as the –ip option.

# bpclntcmd –sv

The -sv option displays the NetBackup version number.

# bpclntcmd –pn

Run on the client, the –pn option verifies the ability of the NetBackup client to resolve and connectto the server, and at the same time verifies the servers ability to resolve the clients name andconnect back to it.The –pn first identifies the configured master in the bp.conf on the client, then resolves its IPaddress. Next, it sends connects to that IP address asking what system the query came from. Themaster then resolves the requesting clients hostname from the IP address, and sends the name it

resolved back to the requesting address.

For example:bpclntcmd -pnexpecting response from server rabbit.friendlyanimals.comdove.friendlyanimals.com dove 123.145.167.3 57141


8/7/2019 278422


Where:

• expecting response from server rabbit.friendlyanimals.com is the master server entry from the SERVER list on the client.

• dove.friendlyanimals.com is the hostname returned by the master server. The master server obtained this name through gethostbyaddr().

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

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

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

5 Suggested NetBackup LoggingIn this section the minimum logging selections are outlined based on the role of the specificNetBackup host. Determine the most likely hosts involved with the problem and use this section todetermine the necessary logs needed to do in-depth Status 41 troubleshooting.

5.1 NetBackup logs – WindowsNetBackup logs on a Windows host are located at:<install_path>\VERITAS\NetBackup\logs

• For all Windows NetBackup Master Servers enable bpcd and bprd logs.

• For all Windows NetBackup Media Servers enable bpcd and bpbrm logs.

Based on the operation being performed for a Windows NetBackup client enable the following logs: File System BackupsEnable bpcd and bpbkar logging.

File System Restores:Enable bpcd and tar logging.

IBM DB2 Database agent Backups and RestoresEnable bphdb, bpdb2 and bpcd logging.

Lotus Notes, MS Exchange and MS Sharepoint Portal Server Backups and RestoresEnable bphdb, bpcd and bpbkar logging for backups.Enable bphdb, bpcd and tar and logging for restores.

MS SQL Server Backups and RestoresEnable bphdb, bpcd and dbclient logging for backups and restores.Collect progress logs: <install_path>\NetBackup\logs\user_ops\MsSql\Logs \*.prg

Oracle Backups and RestoresEnable bphdb, bpcd and dbclient logging for backups and restores.Collect Oracle specific RMAN output file <scriptname>.out.

SAP Backups and Restores

Enable bphdb, backint, bpbackup and bpbkar logging for backups.Enable bphdb, backint, bprestore and tar logging for restores.Collect SAP script, Progress log, and sapdba backup log.

Sybase Backups and RestoresEnable bphdb, bpcd and sybackup logging for backups and restores.

Teradata Backups and RestoresEnable bphdb, bpcd, dbclient and dbbackup logging for backups and restores.Collect progress logs: <install_path>\NetBackup\logs\user_ops\teradata\Logs \*.prg


8/7/2019 278422


5.2 NetBackup logs – UNIX NetBackup logs on a UNIX host are located at:

/usr/openv/netbackup/logs

• For all UNIX NetBackup Master Servers enable bpcd and bprd logs.

• For all UNIX NetBackup Media Servers enable bpcd and bpbrm logs.

For a UNIX NetBackup client enable the following logs based on the operation being performed.

File System BackupsEnable bpcd and bpbkar logging.

File System Restores:Enable bpcd and tar logging.

IBM DB2 Database agent Backups and RestoresEnable bphdb, bpdb2 and bpcd logging.

Informix Backups and RestoresEnable bphdb, bpcd and infxbsa logging for backups and restores.

Collect Informix specific - BAR_ACT_LOG, BAR_DEBUG_LOG & MSGPATH logs.

Lotus Notes Backups and RestoresEnable bphdb, bpcd and bpbkar logging for backups.Enable bphdb, bpcd and tar logging for restores.

Oracle RMAN Backups and RestoresEnable bphdb, bpcd and dbclient logging for backups and restores.Collect Oracle specific - RMAN output file: <scriptname>.out

Oracle (Script-based BLI) Backups and RestoresEnable bphdb, bpcd and bpbkar logging for backups.Enable bphdb, bpcd and tar logging for restores.

Oracle (Proxy Copy/RMAN BLI) Backups and RestoresEnable bphdb, bpcd, bpbkar, dbclient and bpdbsbora logging for backups.Enable bphdb, bpcd, tar , dbclient and bpdbsbora logging for restores.

SAP Backups and RestoresEnable bphdb, bpcd, backint, bpbackup and bpbkar logging for backups.Enable bphdb, bpcd, backint, bprestore and tar logging for restores.Collect progress log, sapdba restore log, brrestore output (.anf / .pnf logs)

Sybase Backups and RestoresEnable bphdb, bpcd, sybackup logging for backups and restores.

Teradata Backups and RestoresEnable bphdb, bpcd, dbclient and dbbackup logging for backups and restores.Collect the Teradata specific Arcmain log.


8/7/2019 278422


6 The NetworkA Status 41 can be triggered by a server’s network card configuration. This would include incorrectlink negotiation, outdated driver or firmware version or issues with vendor specific software such asnetwork teaming.

NIC Troubleshooting Overview:

• Check the NIC vendor’s web site for the latest drivers and firmware and update if necessary.

• Confirm that the NIC is hard-coded to the appropriate duplex setting.(Example: 100 megabyte Full Duplex) The default duplex setting is typically to auto

negotiate which has been known to cause some problems and may trigger a status 41.

• If NIC teaming is being used confirm that the latest teaming software is being used.Network teaming software is used to team multiple network cards for either fail-over or loadbalancing. Network teaming software has been known to cause unexpected behavior withNetBackup. Network related errors such as a status code 41 have been seen as a result of using network teaming. If the server generating the status code 41 is using network teamingsoftware, ensure that it is running the latest network teaming software. In troubleshootingnetwork problems, it would also be a good idea to disable network teaming as a test and seeif the problem persists.

6.1 Physical Network problemsThe physical network includes cables, routers, switches, bridges or any other physical mediumconnecting the NetBackup servers. There are several different network tools that can be used todiagnose problems with the physical network.

Possible Tools for Troubleshooting the Physical Network:

• VERITAS Support uses a tool called AppareNet which is a very useful tool for troubleshooting network problems.

• Operating System utilities such as ping and traceroute can be used to help isolatephysical network problems.

• There are also various third party utilities that can be used to help isolate networkproblems.

• Use a cable tester to confirm that the network cables are working correctly.

• Check the switch and routers management console which should log any errors that areoccurring.

• Output of the OS command “netstat” can be used to see error conditions on the networkinterface

6.2 Heavy Network Load NetBackup is designed to backup the data as fast as possible and can put a heavy load on thenetwork. If the network can not handle the load being generated by the backup, network related

problems will be seen.

Recommendations:

• Configure the backup windows to run during non-peak operating hours.

• Make the larger, more powerful servers NetBackup Media Servers so the data is writtendirectly to tape rather than over the network.


8/7/2019 278422


7 Hardware related IssuesHardware related issues that would cause the disk I/O to be degraded or fail. This can occur if thebackup is unable to read from the files from the disk efficiently. Likely causes would be a bad or faulty drive, SCSI card or HBA if the disk is attached to a SAN.

A highly fragmented disk could also cause a status code 41. This has been seen when the disk isfragmented greater than 20%. Defragmenting the disk may help correct the problem.Note: Do not run a disk defragmenter utility during a backup.

The backup process attempts to read the data from the disk as fast as possible which will causeheavy disk I/O normally not seen during regular day to day user operations.

8 Links

Click here to Search for other documents on Status 41

Also, you may click below to perform a search on the following relevant items:

• Status Code 41

• network connection timed out

• Windows NT Client backups very slow, on the order of kb/sec rather than mb/sec., or exits with status 41. http://support.veritas.com/docs/203981

• All backups fail when using the Microsoft (Internet Security and Acceleration server)firewall client http://library.veritas.com/docs/268872

• When a Firewall is installed between Master/Media Server and Client, the networkconnection to the client times out, although no port restrictions are implemented on theFirewall. http://support.veritas.com/docs/245355


http://seer.support.veritas.com/quicksrch.asp?ddProduct=NBUESVR&SearchTerm=Status+41

http://seer.support.veritas.com/quicksrch.asp?ddProduct=NBUESVR&SearchTerm=Status+Code+41

http://seer.support.veritas.com/quicksrch.asp?ddProduct=NBUESVR&SearchTerm=network+connection+timed+out


http://support.veritas.com/docs/203981%20


http://library.veritas.com/docs/268872%20

http://support.veritas.com/docs/245355

http://seer.support.veritas.com/quicksrch.asp?ddProduct=NBUESVR&SearchTerm=Status+41

http://seer.support.veritas.com/quicksrch.asp?ddProduct=NBUESVR&SearchTerm=Status+Code+41



http://library.veritas.com/docs/268872%20

http://support.veritas.com/docs/245355

278422

Documents