Home > Netbackup Error > Netbackup Error Code 240

Netbackup Error Code 240

Status Code 48 ==================== client hostname could not be found The system function gethostbyname() failed to find the client's host name. On a Windows NT NetBackup server, set the Verbose option on the Troubleshooting tab in the NetBackup Configuration dialog box. This may be due to: · An overloaded system · Insufficient swap space or physical memory · Too many processes running on the system. The values on the Network tab are written to the services file when the NetBackup Client service starts. http://nodatasource.com/netbackup-error/netbackup-error-code-233.html

This error indicates that the client and server were able to initiate communications, but encountered difficulties in completing them. Status Code 78 ==================== afs/dfs command failed Indicates an AFS vos command failure. Status Code 238 ==================== the database contains conflicting or erroneous entries The catalog has an inconsistent or a corrupted entry. Status Code 213 ==================== no storage units available for use The NetBackup resource broker (nbrb) did not find any storage units available for use. https://www.veritas.com/support/en_US/article.TECH71576

Status Code 12 ==================== file open failed An open of a file failed. Status Code: 51 Top Message: timed out waiting for database information Explanation: The database process did not respond within five minutes. This error should not occur through normal use of NetBackup. If necessary, reinstall the client software. 2.

  1. Status Code 275 ==================== a session is already running for this vault This error occurs when you start a session for a vault and another session is already running for this
  2. Status Code 60 ==================== client cannot read the mount table The backup process on the client did not read the list of mounted file systems.
  3. Until more file system space is available, images of similar size or larger may fail with this error when written to this disk storage unit.In a scheduled backup job that writes
  4. On UNIX and Windows NT clients, create a bpbkar activity log directory.
  5. Set up activity logging: o • On UNIX and Windows NT clients, create an activity log directory for bpbkar.
  6. For example, a NetBackup master server has NetBackup 6.5 and the media server or the client has NetBackup 4.5.

On the other side of the connection, the other system is not configured to use VxSS. Corrupt binaries are one possible cause for this error. Could u please some told me abt how Default policy works?Default policy failed with consecutive ec-240Thanks,Shekhar.--_000_2F15E71BD22C6F4A8DCC35F5E736AE5A01417863BRHEXMBP02corpo_Content-Type: text/html; charset="us-ascii"Content-Transfer-Encoding: quoted-printable 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).

Check the level of network activity. Status Code 107 ==================== Status code not available. Retry the operation and examine the logs. To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." 2.

If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Recommended Action: Check the NetBackup Problems report for clues on why the failure occurred. Status Code: 37 Top 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 Status Code 61 ==================== Status code not available.

Status Code 8 ==================== unable to determine the status of rbak On DomainOS clients, rbak is used to do restores. have a peek at these guys On Macintosh clients, check the inetd and bpcd activity logs. Check the All Log Entries report for clues. 4. Either no Vault jobs were run for this profile or the corresponding sidxxx session id directory (or directories) were removed from the following directory: UNIX: /usr/openv/netbackup/vault/sessions/vault_name Windows: install_path\NetBackup\vault\sessions\vault_name Status Code 270

Then, retry the operation and check the resulting activity log. Status Code 124 ==================== NB database backup failed, a path was not found or is inaccessible One or more of the specified paths in the catalog backup configuration were not backed 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. check over here On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 4.

This error can occur if the system cannot allocate enough shared memory. Correct problems and retry the archive. Status Code 120 ==================== cannot find configuration database record for requested NB database backup The program that backs up the NetBackup internal catalogs did not find the attributes that indicate which

Try increasing the media mount timeout specified by the NetBackup global attribute in order to allow more time for mounting and positioning the media. 3.

Then, retry the operation and check the resulting activity logs. 2. Status Code 144 ==================== invalid command usage This status code is due to a NetBackup process being started with improper options or an incompatibility in the product. Status Code 11 ==================== system call failed A system call has failed. If these logs do not provide a clue, create a bpbrm activity log on the server, retry the operation again, and check the resulting activity log.

Status Code 4 ==================== archive file removal failed The backup portion of the archive completed was successful but the delete failed. Status Code 94 ==================== cannot position to correct image The tape manager (bptm) searched for a backup image to restore but did not find the correct backup ID at the expected Status Code 205 ==================== cannot connect to server backup restore manager A process on the master server cannot connect to a process on a host on the network. this content o • On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh).

Either all storage units are unavailable or all storage units are configured for On demand only. This list comes from the server. Display the Control Panel. Status Code: 24 Top Message: socket write failed Explanation: A write operation to a socket failed.

Create a bpinetd activity log directory on the client. 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. o •The bpbkar client process is hung on a file that has mandatory locking set. To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." 3.

Status Code 82 ==================== media manager killed by signal Another process or a user terminated the tape manager (bptm) or disk manager (bpdm). Explanation: The tape manager, bptm reported that the media did not load and position within the allotted time. Sorry, we couldn't post your feedback right now, please try again later. Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may

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. For a NetBackup catalog backup, the operation terminates abnormally. If the server cannot connect to the client, create bpcd or bpbkar (UNIX and Windows NT only) activity log directories on the client, retry the operation, and check the resulting logs. 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