- 论坛徽章:
- 0
|
Veritas Status Codes and Messages
Veritas Status Codes and Messages
Status Codes and Messages
This chapter lists all the status codes and messages provided by NetBackup.
On a UNIX NetBackup server, if you see a status code without its associated message text, you can determine the message by using the bperrcode command:
/usr/openv/netbackup/bin/goodies/bperrcode [error_code]
Where error_code is the number of the code for which you want the message.
Specify an error code display text for only that specific error code.
Execute the command without specifying an error code to display the text for all error codes.
Example: /usr/openv/netbackup/bin/goodies/bperrcode 37
37 operation requested by an invalid server.
Status Codes
Status Code: 0
Message: the requested operation was successfully completed
Explanation: There were no problems detected with the requested operation.
Recommended Action:
None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). In those instances, code 0 means the backup script that started the backup ran without error. However, you must check other status as explained in the related NetBackup manual to see if the database was successfully backed up.
Status Code: 1
Message: the requested operation was partially successful
Explanation: A problem that may require corrective action was detected during the requested operation.
Recommended Action: Check the All Log Entries report and also the progress log (if there is one).
Some of the problems that can show up under Status Code 1 are:
A file or directory path that is more than 1023 characters long.
Could not open a file.
On a UNIX system, NetBackup could not get the link name of a file.
On a UNIX system, NetBackup could not process a sparse file.
Read error encountered in a file.
File is of an unknown type.
On a UNIX system, the lstat system call fails on a file that is eligible to be backed up. This may be a permission problem.
On UNIX, a file could not be locked that has mandatory locking enabled.
Status Code: 2
Message: none of the requested files were backed up
Explanation: A backup or archive could not back up any of the files in the file list.
Recommended Action: Verify that the files exist and you have read access to them.
On UNIX clients, check to see if the files or directories would be excluded because of an entry in /usr/openv/netbackup/exclude_list.
On PC clients, check the exclude list per the instructions in the user's guide for the client.
On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.
If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives.
To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives.
Status Code: 3
Message: valid archive image produced, but no files deleted due to non-fatal problems
Explanation: The backup portion of the archive command reported problems so the files were not deleted.
Recommended Action: Examine the progress log of the archive on the client to determine if you need to retry the archive after correcting the problem. If the problem is not serious and the files were backed up, you can manually delete the files. To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive.
A possible cause for files not being deleted is that you do not have the necessary permissions. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT.
Status Code: 4
Message: archive file removal failed
Explanation: The backup portion of the archive completed was successful but the delete failed.
Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files. On UNIX clients, verify that you have write permission to the directories that contain the files. Since the backup was successful, you can delete the files that were backed up (or have the system administrator delete the files if you do not have the necessary permissions).
Status Code: 5
Message: the restore failed to recover the requested files
Explanation: There were errors that caused the restore to fail.
Recommended Action:
Examine the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server.
On Windows NT and UNIX, check ownership and permission on directories where files will be restored.
Correct problems that you find and retry the restore.
Status Code: 6
Message: the backup failed to back up the requested files
Explanation: Errors caused the user backup to fail.
Recommended Action:
Verify that you have read access to the files. Check the progress log on the client for messages on why the backup failed. Correct problems and retry the backup.
On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.
On Macintosh clients, this code can be due to multiple backups being attempted simultaneously on the same client. Some possible solutions are:
Adjust the backup schedules.
If the client is only in one class, set the general class attribute, Maximum Jobs per Class, to 1.
Set the NetBackup global attribute, Maximum Jobs Per Client, to 1 (note that this limits all clients in all classes).
For a UNIX database extension client (for example, NetBackup for Oracle), this can mean a problem with the script that is controlling the backup.
Check the progress report on the client for a message such as "Script exited with status code = number" (the number will vary). The progress log also usually names the script.
Check the script for problems. Also, check the troubleshooting logs created by the database extension. See the NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs.
Status Code: 7
Message: the archive failed to back up the requested files
Explanation: Errors caused the user archive to fail.
Recommended Action:
Verify that you have read access to the files. Check the progress log on the client for messages on why the archive failed. Correct problems and retry the archive.
On Windows NT clients, verify that the account used to start the NetBackup services has read access to the files.
Status Code: 8
Message: unable to determine the status of rbak
Explanation: On DomainOS clients, rbak is used to do restores. If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not.
Recommended Action: Check for a new core file to see if rbak aborted. Check the ps output to see if rbak is hung. If so, kill it and try again. Check the progress log for any unusual messages from rbak.
Status Code: 9
Message: an extension package is needed but was not installed
Explanation: A NetBackup extension product is required in order to perform the requested operation.
Recommended Action: Install the required extension product.
Status Code: 10
Message: allocation failed
Explanation: Allocation of system memory failed because there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory.
Recommended Action: Free up memory by terminating unneeded processes that consume memory. Add more swap space or physical memory.
Status Code: 11
Message: system call failed
Explanation: A system call failed. This status code is used for a generic system call failure that does not have its own status code.
Recommended Action:
Check the All Log Entries and Problems reports to determine which system call failed and other information about the error.
A frequent cause is that the server's file system is full. For example, if you see a message similar to the following in the Problems report or bpdbm activity log:
06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11)
06/27/95 01:04:01 romb romb media manager terminated by parent process
06/27/95 01:05:15 romb romb backup of client romb exited with status 11 (system call failed)
On UNIX systems, run a df command on the /usr/openv/netbackup/db directory.
If the df command does not reveal the problem, check the bpdbm activity logs or do a grep for the message system call failed
in /usr/openv/netbackup/db/error/*
On Windows NT systems, verify there is room in the disk partition where NetBackup is installed.
Verify that the system is not running out of virtual memory. If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory.
To increase virtual memory on Windows NT, 98, and 95:
Display the Control Panel.
Double-click System.
On the Performance tab, set Virtual Memory to a higher value.
Check for a semaphore problem. This error can be caused by the system not having enough semaphores allocated. This is most commonly seen on Solaris 2 servers when an RDBMS is also running.
The symptoms of the problem vary. In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation; another symptom is the inability of the NetBackup Device Manager service Media Manager device daemon, ltid, to acquire a needed semaphore (this is the NetBackup Device Manager service on Windows NT).
System requirements vary; thus, no absolute recommendations can be made. One customer running both NetBackup and ORACLE on their Solaris server made the following changes to their /etc/system file and then rebooted the system (boot -r); the changes were found to be adequate:
set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600
Set these attributes to a value great enough to provide resources to all applications on your system.
Check for a shared memory problem. This error can occur if the system cannot allocate enough shared memory. This usually occurs when you use multiplexing, which increases the shared memory requirements. A symptom is an entry similar to the following in a NetBackup log (or report) could not allocate enough shared memory
If you see this type of message, refer to the vendor documentation for your platform for instructions on increasing the amount of shared memory on your system.
Because system requirements vary, we can make no absolute recommendations, other than to use values great enough to provide resources to all applications. Although, in at least one instance, the following was found to be adequate on a Sun platform:
set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmnu=600
set semsys:seminfo_semmns=300
After making the changes to the /etc/system file on the Sun platform and rebooting with boot -r, the problem was resolved. Note that in the above, shminfo_shmmin must be less than or equal to 100 for NetBackup processes to run.
Examine other activity logs or the progress log on the client.
If a backup on a Windows NT NetBackup client fails with status code 11 and the client is using Open Transaction Manager (OTM) for open file management, it is possible that the error was caused by the OTM cache file being full. If this is the case and bpbkar activity logs are turned on, a message similar to the following should appear at the end of the backup:
04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005
04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled for all processes
04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!
If this error is encountered, you may need to increase either the initial OTM cache size or the maximum OTM cache size, depending on the requirements of your installation and your usage of OTM.
Status Code: 12
Message: file open failed
Explanation: An open of a file failed.
Recommended Action: Check the NetBackup Problems report. Try to determine the file and why the error occurred. A possible cause is a permission problem with the file. For detailed troubleshooting information, create an activity log directory for the process that returned this status code. Then, retry the operation, and check the resulting activity log.
Status Code: 13
Message: file read failed
Explanation: A read of a file or socket failed. Possible causes include:
I/O error reading from the file system.
Read of an incomplete or corrupt file.
Socket read failing. A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket.
Recommended Action:
Check the NetBackup Problems report for clues on where and why the problem occurred.
For a FlashBackup client, check the /var/adm/messages log for errors like the following:
Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable
This indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of them or reschedule the entire backup to a time when the file system is less active.
For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 14
Message: file write failed
Explanation: A write to a file or socket failed.
Recommended Action:
Check the NetBackup Problems report for clues on where and why the problem occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
The following are some possible causes:
I/O error writing to the file system
Write to a socket failed. This can be caused by a network problem or a problem with the process reading from the socket.
Writing to a full disk partition.
Status Code: 15
Message: file close failed
Explanation: A close of a file or socket failed.
Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 16
Message: unimplemented feature
Explanation: The specified operation is unimplemented. This error should not occur through normal use of NetBackup.
Recommended Action: Save all error information and call customer support.
Status Code: 18
Message: pipe close failed
Explanation: Close of a pipe failed, when one process tries to start a child process.
Recommended Action: Check the NetBackup Problems report for clues on why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
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:
Check the NetBackup Problems report for clues on why the failure occurred.
On a UNIX system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.
On a Windows NT 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 NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts. Also, see "Verifying Host Names and Services Entries" on page 31.
Check the level of network activity. An overloaded network can cause this error.
If the above actions do not reveal the problem, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 20
Message: invalid command parameter
Explanation: One or more command parameters were not valid. This error can occur when a master and its slave servers or a master server and a client have different levels of NetBackup installed. For example, if a NetBackup master server has NetBackup 3.2 and the slave server has NetBackup 3.0. This error can also occur if the wrong parameters are used when executing a command line.
Recommended Action:
Check the NetBackup Problems report for clues.
If the error occurs when executing a command on the command line, verify that the parameters are valid.
Compare the NetBackup version level on the server to that on the clients:
On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.
On Windows NT NetBackup servers, check the install_path\netbackup\version.txt file or the About NetBackup command on the Help menu.
On Microsoft Windows clients, check the About NetBackup command on the Help menu.
On NetWare target clients, check the Version entry in the bp.ini file. If the client software is earlier than 3.0, verify that the client is in a Standard type class.
On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder.
If the above actions do not reveal the problem, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 21
Message: socket open failed
Explanation: A socket open failed.
Recommended Action:
Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that returned this status code. Then, retry the operation and check the resulting activity logs.
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).
On Windows NT, verify that the recommended service packs are installed.
Status Code: 22
Message: socket close failed
Explanation: A socket could not be closed.
Recommended Action:
Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then, retry the operation and check the resulting activity logs.
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).
On Windows NT, verify that the recommended service packs are installed.
Status Code: 23
Message: socket read failed
Explanation: A read operation from a socket failed.
Recommended Action:
Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then, retry the operation and check the resulting activity logs.
Corrupt binaries are one possible cause for this error. For example, in one instance, the following was seen in the bpsched activity log.
get_num_avail_drives: readline failed: socket read failed (23)
get_stunits: get_num_avail_drives failed with stat 23
Loading a fresh bptm from the install media resolved the problem.
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).
On Windows NT, verify that the recommended service packs are installed.
Status Code: 24
Message: socket write failed
Explanation: A write operation to a socket failed.
Recommended Action:
Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then retry the operation and check the resulting activity logs.
A possible cause could be a high network load. For example, this has been seen in conjunction with Cannot write to STDOUT when a Windows NT system that is monitoring network load has detected a high load and sent an ICMP packet to other systems that says the route being used by those systems was disconnected. The log messages were similar to the following:
01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.null.com_0823125016, copy 1, fragment 1, 440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com CLASS Remote3SysFullW SCHED Sirius EXIT STATUS 24 (socket write failed)
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).
On Windows NT, verify that the recommended service packs are installed.
Status Code: 25
Message: cannot connect on socket
Explanation: A process timed out while connecting to another process for a particular operation. This problem can occur when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running (On Windows NT, these daemons are the NetBackup Request Manager and NetBackup Database Manager services). It can also occur if the network or server is heavily loaded and has slow response time.
Recommended Action:
On a UNIX NetBackup master server, verify that the bprd and bpdbm processes are running. If these processes are not running, start them. On a Windows NT master server, verify that the NetBackup Request Manager and NetBackup Database Manager services are running. If these services are not running, start them.
If the above processes are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.
If you cannot view the report, or you get a cannot connect on socket error when trying to view it, verify again that the NetBackup Database Manager daemon (or service) is running. Then, create an activity log directory for bpdbm, retry the operation, and check the resulting activity log.
If you can view the report and have not found an entry related to this problem, create activity log directories for the related processes that were running when the error first appeared (this process will frequently be bpbrm). Then, retry the operation and check the resulting activity logs.
Verify that the server list specifies the correct master server.
On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box.
To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).
On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file.
On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file.
If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows NT).
Check the services file.
On UNIX, 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 NT, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts. Also, see "Verifying Host Names and Services Entries" on page 31.
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).
On Windows NT, verify that the recommended service packs are installed.
Status Code: 26
Message: client/server handshaking failed
Explanation: A process on the server encountered an error when communicating with the client. This error indicates that the client and server were able to initiate communications, but encountered difficulties in completing them. This problem can occur during a backup or a restore.
Recommended Action: Determine which activity encountered the handshake failure by examining the All Log Entries report for the appropriate time period. Determine the client and server that had the handshake failure.
For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 27
Message: child process killed by signal
Explanation: A child of the process reporting this error was killed. This can occur because the backup job was terminated or the child process was terminated by another error. This problem can also occur if a NetBackup process was terminated through Task Manager or another utility.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.
Status Code: 28
Message: failed trying to fork a process
Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows NT). This may be due to:
An overloaded system
Insufficient swap space or physical memory
Too many processes running on the system.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create activity log directories for the processes that you suspect of returning this status code. Then, retry the operation and check the resulting activity logs.
Status Code: 29
Message: failed trying to exec a command
Explanation: A command could not be executed. This can occur because the permissions of the command do not allow it to be executed, or there is lack of system resources such as memory and swap space.
Recommended Action:
Check the NetBackup All Log Entries report for clues on where and why the failure occurred.
Check the permissions on the command to be executed.
For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 30
Message: could not get passwd information
Explanation: Could not get the passwd entry for a user.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.
Status Code: 31
Message: could not set user id for process
Explanation: Could not set the user ID of a process to that of the requesting user. NetBackup executes client processes as the requesting user.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.
Status Code: 32
Message: could not set group id for process
Explanation: Could not set the group ID of a process to the requesting user group. NetBackup executes client processes with the group ID of the requesting user.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.
Status Code: 33
Message: failed while trying to send mail
Explanation: An E-mail notification of backup, archive, or restore results has failed. The E-mail could not be sent to the administrator's address as specified by the E-mail global attribute, or in the case of a UNIX client, an E-mail address specified with USEMAIL in the client's bp.conf file.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.
Status Code: 34
Message: failed waiting for child process
Explanation: The bpsched process encountered a failure while waiting for a child process to complete.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.
Status Code: 35
Message: cannot make required directory
Explanation: Could not create a required directory. Possible causes are:
A process does not have permission to create the directory
The path to the directory is not valid
An IO error occurs
There was no space available on the device containing the directory
Recommended Action:
Check the NetBackup All Log Entries report to determine which directory could not be created and why it could not be created. In particular, check for a full disk partition.
Check the permissions on the parent directory and verify that NetBackup services are started with a "Logon as" account that has permission to create the directory.
For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 36
Message: failed trying to allocate memory
Explanation: Allocation of system memory failed. This error occurs when there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory.
Recommended Action: Free up memory by terminating unneeded processes that consume a lot of memory. Add more swap space or physical memory.
Status Code: 37
Message: operation requested by an invalid server
Explanation: A request was made to the NetBackup request daemon (bprd) or NetBackup database manager daemon (bpdbm) by an invalid slave server or Windows NT administration client. On Windows NT, these daemons are the NetBackup Request Manager and NetBackup Database Manager services.
Recommended Action:
Examine the NetBackup All Log Entries report for the time of this error to determine which system was trying to connect to the master server. If the server is a valid slave server, verify that the storage unit for the slave server is defined. Also, verify that the server or Windows NT administration client has a server list entry on the master server.
If necessary, update the server list. On a UNIX master server, add a SERVER = slave_server_name to the bp.conf file. slave_server_name is the host name of the slave server. On a Windows NT master server, start the Backup, Archive, and Restore interface. Then, click Configure on the Actions menu and add the slave server to the list on the Servers tab in the NetBackup Configuration dialog box (also, see "Using the Configure - NetBackup Window" on page 3.
If a server or Windows NT administration client has more than one host name (for example, if it has multiple network interfaces), verify that the master server has a server list entry for each of them.
If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. If you change the server list on a Windows NT master server, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services.
Status Code: 38
Message: could not get group information
Explanation: Could not get the group entry describing a UNIX user group.
Recommended Action: Check the NetBackup Problems report for clues on why the error occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 39
Message: client name mismatch
Explanation: The name that the client used in a request to the NetBackup server did not match the client name configured in the class on the server.
Recommended Action: Change either the NetBackup client name setting on the client (see the applicable NetBackup users guide) or the one in the class configuration on the server so the two match.
Status Code: 40
Message: network connection broken
Explanation: The connection between the client and the server was broken. This status code can also appear if the connection is broken between the master and slave server during a backup.
Recommended Action:
Try pinging the client from the server. If this is not possible, check for loose connections or other network problems.
Verify that the server list settings are correct on both the client and the server. If the backup involves a slave server, verify that these entries are correct on both the master and slave server. For example, if a slave server does not have a server list entry for the master, it does not accept connections from the master.
On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).
On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file.
On NetWare target and OS/2 clients the master server name is the first SERVER entry in the bp.ini file.
If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. On Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.
Status code 40 can also be due to the operator denying a mount request. |
|