Home > Netbackup Error > Netbackup Error 82

Netbackup Error 82

Set up activity logging: a. Recommended Action: 1. On Macintosh clients, check the inetd and bpcd activity logs. Add more swap space or physical memory. weblink

Recommended Action: Try running wbak by hand to determine the source of the problem. Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files. Status Code 30 ==================== could not get passwd information Could not get the passwd entry for a user. o On UNIX clients, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

On UNIX clients, verify that you have write permission to the directories that contain the files. If so, any Media server which requests usage of the Masters devices must also have a "SERVER" entry in the Master's vm.conf. If the error occurs when executing a command on the command line, verify that the parameters are valid. 3. Was a full backup done before? 4004 The backup failed.

  • However, all of the vmd processes are running fine.
  • Status Code 243 ==================== the client is not in the configuration The specified client name was not in the catalog.
  • This may be due to: An overloaded system Insufficient swap space or physical memory Too many processes running on the system.
  • This lock file synchronizes process activities (for example, it prevents more than one daemon from running at a time).
  • 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

Please contact your system administrator. 1270 The smartcard certificate used for authentication has expired. Try to ping the client from the server and the server from the client. 4. You may also refer to the English Version of this knowledge base article for up-to-date information. If this is an initial installation, refer to "Common Configuration Problems" in chapter 2. 6.

Status Code 19 ==================== getservbyname failed A call to getservbyname() failed. If the correct VxFS libraries are not installed, the backup fails with status 142. * For most snapshot backups, the following message appears in the /usr/openv/netbackup/logs/bpfis log on the client: 09:36:48.299 Create bpbrm and bpdbm activity log directories on the server and retry the operation. 4. https://www.veritas.com/support/en_US/article.000090669 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

This error is usually caused when another process acquired the port before the daemon or service started. 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). Verify that the bpcd and bprd port numbers in the %SystemRoot%\system32\drivers\etc\services file on the server matches the setting on the client. The backup is retried automatically with a different volume if the backup tries attribute allows it in the NetBackup global attribute configuration.

Just in case there is still some polling/comms from this server with the media server trying to connect back to this server instead of the Solaris master. This error should not occur through normal use of NetBackup. However, the disk file path already exists and is not a directory. Check the directory to which you are backing the database. 4005 The name does not exist in the WINS database. 4006 Replication with a nonconfigured partner is not allowed. 4100 The

For a UNIX database extension client (for example, NetBackup for Oracle), this can mean a problem with the script that is controlling the backup. have a peek at these guys If the server is Windows, the NetBackup Device Manager service is not running. This problem can occur during a backup or restore in either a single or a multiple server configuration. Thank You!

Status Code 11 ==================== system call failed A system call has failed. 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: 74 Top Message: client timed out waiting for bpstart_notify to complete Explanation: The bpstart_notify script o Tech-eye-Tech Follow by Email Tuesday, November 20, 2012 Netbackup Important Error Codes These http://nodatasource.com/netbackup-error/netbackup-error-213.html Status Code 50 ==================== client process aborted The client backup terminated abnormally.

Start PBX and media server services ( This would ensure all connections and allocations are inline for all media servers.) Let us know if it works. 0 Kudos Reply Hi Status Code 1 ==================== the requested operation was partially successful A problem was detected that may require corrective action during the requested operation. On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh).

On a Macintosh, you can check for activity by examining the NetBackupListen file in the following folder on the startup disk of the Macintosh client: :System Folder:Preferences:NetBackup:logs:inetd:log.mmddyy 2.

Status Code 195 ==================== client backup was not attempted A backup job was in the NetBackup scheduler's worklist but was not attempted. If necessary add it as follows: o On Windows NT, 98, and 95 clients, add the server on the Servers tab in the NetBackup Configuration dialog box. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Retry the operation and check the resulting activity logs for detailed troubleshooting information.

On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 5. Error Message exit status code 82: vmd is not active; select_media: unable to obtain db handle for Media Manager query on host, not authorized to connect to vmd  "Error connecting to Status Code 192 ==================== VxSS authentication is required but not available On one side of a NetBackup network connection, the system requires VxSS authentication. this content When the robot is controlled by an Automated Cartridge System, verify that the ACSLS system is up. 5.

On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 3. On a Sequent platform, verify that the system has the correct level of TCP/IP. 3. Status Code 121 ==================== no media is defined for the requested NB database backup When NetBackup attempted to back up its internal catalogs, no media IDs were defined in the catalog No more connections can be made to the service at this time because there are already as many connections as the service can accept. 1396 Logon Failure: The target account name

Changes will not be effective until the system is rebooted. 3011 The requested operation is successful. This problem can occur during a backup, restore, or media list in a single or a multiple server configuration. This error means that the master and the media server processes were able to initiate communication, but were not able to complete them. If wildcards are used, verify there are matching bracket characters ([ and ]).

This error occurs if a user-specified job ID on the vltrun -haltdups command is out of range (not among the job IDs created by job manager). 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). If these processes are not running, start them. Status Code 39 ==================== client name mismatch The client used a name in a request to the NetBackup server that did not match the configured name in the policy on the

Enable detailed activity logging: o Create a bpbkar activity log directory (UNIX or Windows NT only). Status Code 24 ==================== socket write failed A write operation to a socket failed. Status Code 86 ==================== media position error The system's device driver returned an I/O error while NetBackup was positioning media (tape or optical disk). Status Code 251 ==================== the tir information is zero length For a true-image backup, the client sent no file information to the master server.

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 * No space Status Code: 28 Top Message: failed trying to fork a process Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows NT). Status Code 228 ==================== unable to process request An inconsistency exists in the catalog or a request was made that would be improper to satisfy. That storage unit may have more unused capacity now than it did when the job failed.

On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 2. 2. 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.