Thursday, July 21, 2016

NetBackup status code: 103 ( Error Occurred During Initialization, check configuration file)

NetBackup status code: 103
Message: error occurred during initialization, check configuration file


Explanation: NetBackup Snapshot Client can perform two kinds of off-host backups by means of a data mover: the NetBackup media server method or the Third-Party
Copy Device method. For either method, an off-host data mover backup requires a configuration file (the 3pc.conf file) to identify the following devices on the SAN:
■ The client disks to back up
■ The devices on which to store the data 


If the media server has access to many disks and storage devices on the SAN, it may take too long to acquire the device information from the SAN. As a result, if no 3pc.conf file exists on the media server, the first multistream backup that uses a data mover method may fail.

Recommended Action: Create the 3pc.conf file manually before running the first multistream data mover backup. Use the following command to create the 3pc.conf file:
# bptpcinfo -a
The 3pc.conf file is created at /usr/openv/volmgr/database/3pc.conf. More information is available on the 3pc.conf file and how to create it.
See Configuring NetBackup for off-host data mover backups in the NetBackup Snapshot Client Configuration document.


Source : www.veritas.com

Blogger Tricks

NetBackup status code: 25 (Cannot Connect on Socket)

NetBackup status code: 25
Message: cannot connect on socket
Explanation: A process that timed out while it connects to another process for a particular operation. This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. (On Windows, these daemons are the NetBackup Request Manager and the NetBackup Database Manager services.)
It can also occur in the following situations: the network or server is heavily loaded and has slow response time or an evaluation license key for NetBackup expired. However, the most common cause of this error is a host name resolution problem.


The following are other possible causes of this error caused by network connectivity
issues or a required process such as pbx_exchange not running.
nbjm is unable to connect to bpcd on the media server
nbpem is unable to connect to nbproxy
bptm on the media server is unable to connect to nbjm on the master server.
■ You cannot perform an immediate backup operation.


These errors are caused either by network connectivity issues or if a required
process such as pbx_exchange is not running.


Recommended Action: Do the following, as appropriate:
■ Verify that bpcompatd, vnetd, and Private Branch Exchange (PBX) are running.
Information on how to start PBX is available.
See "Resolving PBX problems" in the NetBackup Troubleshooting Guide.
■ If necessary, stop and restart NetBackup.
■On UNIX systems, enter the following:
/usr/openv/netbackup/bin/bp.kill_all
/usr/openv/netbackup/bin/bp.start_all

 
■ On Windows systems, enter the following:
install_path\NetBackup\bin\bpdown
install_path\NetBackup\bin\bpup

 
■ The following information applies only to a UNIX or Linux NetBackup master
server:
Verify that the bprd and the bpdbm processes are running. If these processes are not running, start them. On a Windows master server, verify that the NetBackup Request Manager and the NetBackup Database Manager services are running. If these services are not running, start them. If these processes or services are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.
Do one of the following:
■ If you cannot view the report or you get a cannot connect on socket error, verify again that the NetBackup Database Manager service or daemon is running. Then, create a debug log directory for bpdbm, retry the operation, and check the resulting debug log.
■ If you view the report and do not find a problem-related entry, create the debug log directories for the related processes that were running when the
error first appeared. (This process frequently is bpbrm.) Then, retry the operation and check the resulting debug logs.
■ Verify that the server list specifies the correct master server.
■ The following information applies only to Windows systems:
The master server is designated in the Server to use for backups and restores drop-down in the Specify NetBackup Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Specify NetBackup Machines and Policy Type on the File menu.


■ The following information applies only to UNIX and Linux systems:
The master server is the first SERVER entry in the bp.conf file.
■ Check the following Veritas Support website to ensure that all recommended
NetBackup patches are installed: www.veritas.com/support
Then select NetBackup followed by files and updates.
■ If failure occurs when you run a user-directed backup from a client, make sure that a user-directed backup schedule exists at the master server.
■ With NetBackup database extensions:
Make sure that the applicable database product has the correct permissions allowing NetBackup to write to the progress log on the client.
■ The following information applies only to UNIX systems:
If bpdbm has quit when the shutdown script runs on a media server, carefully read the K77netbackup script. It contains details on how to prevent this problem. The script is in /usr/openv/netbackup/bin/goodies.

If you change the server list on a master server, stop, and restart the following:
The NetBackup Database Manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows).
■ Check the services file.
■ The following information applies only to UNIX systems:
Verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd.
On Windows, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the following numbers match the settings in the services file:
The NetBackup Client Service Port and the NetBackup Request Service Port on the Network tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click NetBackup Client Properties on the File menu. The values on the Network tab are written to the services file when the NetBackup Client service starts.
See Verifying host names and service entries in NetBackup in the NetBackup  Troubleshooting Guide.


■ On Sun Solaris, verify that all operating system patches are installed See the Operating Notes section of the NetBackup Release Notes.
■ On Windows, verify that the recommended service packs are installed.
■ When the base NetBackup license key expires, daemons (such as bprd and bpdbm) terminate on the NetBackup server. If these daemons are not running, you are likely to encounter status code 25 errors in the Administration console. Install a valid base NetBackup license key, restart the daemons, and restart the console.
■ For NetBackup Snapshot Client, the following applies: When many devices are configured on a media server, it may take a long time for the bptpcinfo command to generate the file 3pc. When the backup is run for the first time, the backup may fail with status 25. Make sure that the /usr/openv/volmgr/database/3pc.conf file exists. If it does, rerun the backup.
If the backup fails again, run the bptpcinfo manually to generate the file 3pc, then try the backup again.

NetBackup status code: 24 (Socket Write Failed)

NetBackup status code: 24
Message: socket write failed

Explanation: A write operation to a socket failed.

Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that could have returned this status code. Then retry the operation and check the resulting debug logs.
■ A possible cause is a high network load. For example, this problem occurs with Cannot write to STDOUT when a Windows system that monitors network load
detects a high load. It then sends an ICMP packet to other systems to inform them that the route they use is disconnected. The log messages were similar
to the following:


01/31/96 14:05:23 ruble crabtree.null.com from client
crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No
route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote
backup id crabtree.null.com_0823125016, copy 1, fragment 1,
440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT
crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT
STATUS 24 (socket write failed)

 
■ The following information applies only to Sun Solaris:
Verify that all operating system patches are installed. See the Operating Notes section of the NetBackup Release Notes.
■ The following information applies only to Windows systems:
Verify that the recommended service packs are installed. Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.


Source : www.veritas.com

Wednesday, July 20, 2016

NetBackup status code: 20 (Invalid Command Parameter)

NetBackup status code: 20
Message: invalid command parameter

Explanation: One or more command parameters were not valid. This error can occur when incompatible levels of NetBackup are installed on a master and its media servers or clients. For example, a NetBackup master server has NetBackup 7.6 and the media server or the client has NetBackup 7.0. This error can also occur if the wrong parameters are used when you run a command line.

Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues.
■ If the error occurs when you run a command on the command line, verify that the parameters are valid.
■ This status code may occur if nbjm passes parameters but does not have a required parameter. Check the nbjm unified logs (originator ID 117) for the list of parameters that were passed.
■ The following information pertains to NetBackup Snapshot Client.
■ If the following appears in the /usr/openv/netbackup/logs/bptm log as enabled on a third-party copy backup, multiplexing was enabled on a third-party copy backup:


bptm: cannot perform Third-Party-Copy for multiplexed backups

send_brm_msg: ERROR 20

bptm: EXITING with status 20
The Third-party Copy Device off-host backup method is incompatible with multiplexing (the writing of two or more concurrent backup jobs to the same storage device). You must disable multiplexing for any third-party copy backups. If multiplexing is enabled, the backup fails.
■ The media server may not have the correct 3pc.conf file entry for the client
disk that is needed for the backup.
The following appears in the /usr/openv/netbackup/logs/bpbkar log:
14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1
EMC:SYMMETRIX:601092014000
14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive
child started, pid = 15822
14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:
15822 killed
14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1
14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain
device id string EMC:SYMMETRIX:601092014000
14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit
status = 227: no entity was found
14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no
entity was found
14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout complete

 
This shows that a particular device cannot be found in the 3pc.conf file on the media server (14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain device id string EMC:SYMMETRIX:601092014000).

The problem is one of the following:

  • The 3pc.conf file on the media server is outdated. Recreate the 3pc.conf file.
  • The media server is not on the same Fibre Channel network as the third-party copy device and client disk. As a result, the 3pc.conf file does not have a correct entry for the client disk. Run the bptpcinfo command with the -x client_name option; this option adds the client disk to the 3pc.conf file. For each disk that is added to the file by means of bptpcinfo -x client_name, you may need to add the device’s World Wide Name (WWN=).
See the NetBackup Snapshot Client Configuration online document.
See Snapshot Client Assistance in the NetBackup Snapshot Client Administrator’s Guide.

■ The HP VxFS snapshot mechanism requires a dedicated cache partition for each snapshot. A check is made in the mount table to make sure that the cache partition is not already in use. If the cache partition is already in use, status code 20 occurs.
Check the /usr/openv/netbackup/logs/bpbkar log for a message similar to the following:


bpfsmap: FTL - bpfsmap: snapshot cache already in use, /dev/arrayvg/vol4c
bpbkar Exit: ERR - bpbkar FATAL exit status = 20: invalid
command parameter
bpbkar Exit: INF - EXIT STATUS 20: invalid command parameter

 
If the snapshot cache partition is already in use, do one of the following: Set up your policy schedules to run at different times or use different cache partitions for each backup.
If the Allow multiple data streams option is enabled, each stream must have its own dedicated cache partition.
■ Compare the NetBackup version level on the server to the version level on the clients by doing the following:

  • On UNIX or Linux NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.
  • On Windows NetBackup servers, check the install_path\Netbackup\version.txt file or the About NetBackup item on the Help menu.
  • On Microsoft Windows clients, check the About NetBackup item on the Help menu.
  • If a Java interface displays the error, tell them how to enable the debug print manager in the Java startup file. Retry and compare the parameters that were logged on the Java log with the parameters listed in the commands usage statement.
■ For the Backup Media Server option for VMware backups, the storage unit that is specified in the policy must be unique to your media servers. If the storage
unit is also available on another media server, the snapshot job cannot succeed.
■ If these actions do not reveal the problem, create a debug log directory for the process that returned this status code (if the process uses legacy logging). Then
retry the operation and check the resulting log.

Source : www.veritas.com

NetBackup status code: 19 (getservbyname Failed)

NetBackup status code: 19
Message: getservbyname failed

Explanation: A call to getservbyname() failed. The getservbyname()function uses the name of the service to find a service entry in the services file. (Or NIS
services map on UNIX if it is configured.)

Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues on why the failure occurred.
■ On a UNIX or Linux system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.
■ On a Windows system, verify that the %SystemRoot%\system32\drivers\etc\services file shows the correct entries
for the NetBackup Internet processes: bpcd, bpdbm, and bprd.
Ensure that the following numbers match the settings in the services file: The NetBackup Client Service Port number and NetBackup Request Service Port
number on the Network tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and
click NetBackup Client Properties on the File menu. The values on the Network tab are written to the services file when the NetBackup Client service
starts. See "Verifying host name and service entries" in the NetBackup Troubleshooting Guide.
■ Check the level of network activity. An overloaded network can cause this error.
■ If these actions do not reveal the problem, create a debug log directory for the process that returned this status code. Then retry the operation and check the
resulting debug log. 


Source : www.veritas.com

Media Manager status code 12 ( Invalid Robot Type)

Media Manager status code 12
Message: invalid robot type


Explanation: A requested operation encountered a case where a specified robot
type or a volume’s robot type is different. It differs from the type of robot that is
required to perform the operation in the current configuration.


Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■ Specify a robot type that supports the volume’s media type.
Media Manager status codes 465
Media Manager status codes
■ Check the EMM database and ensure that the specified robot type agrees with
the type for all volumes having the specified robot number.
■ If a robot type is required for the requested operation, ensure that a robot type
has been specified.


Source : www.veritas.com

Media Manager status code 11 (Invalid Description)

Media Manager status code 11
Message: invalid description


Explanation: The volume description exceeds 25 ASCII characters in length, or
contains unprintable characters.


Recommended Action: When you add or change a volume record or barcode
rule record, ensure that the description field contains the following: no more than 25 ASCII characters that can be printed.


Source : www.veritas.com

Media Manager status code 10 (Invalid Barcode)

Media Manager status code 10
Message: invalid barcode

Explanation: When a process performed a media-related operation, it encountered
an unknown, missing, or incompatible barcode.

Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■ Ensure that the barcode, where requested, is not blank.
■ Ensure that the specified barcodes contain valid characters only: Alphanumeric
characters, and the period (.), plus sign (+), and underscore (_). A hyphen (-)
is also a valid character when not the first character in the media ID.
■ Ensure that the number of characters in the barcode does not exceed the
maximum that is allowed for the robot type.
■ Ensure that the barcode tag in all barcode rules is a subset of a valid, supported
barcode format.


Source : www.veritas.com