Home > Netbackup Error > Netbackup Error 241

Netbackup Error 241

Set up activity logging: o • On UNIX and Windows NT clients, create an activity log directory for bpbkar. 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). For example, this error occurs if a NetBackup master or media server is shut down or rebooted when a backup or restore is in progress. Potential reasons include the following: * Reports were not emailed (possibly because of malformed email addresses in the vault.xml file). * On Windows, the third party mail client (such as blat) weblink

Status Code 62 ==================== Status code not available. On all but Macintosh clients, enable bpcd activity logging as follows: a. 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 Status Code 96 ==================== unable to allocate new media for backup, storage unit has none available The tape manager (bptm) did not allocate a new volume for backups.

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). Status Code 182 ==================== tar received an invalid file name tar cannot write to the file that is specified with the -f parameter. For detailed troubleshooting information, create an activity log directory for the process that returned this status code. Status Code 154 ==================== storage unit characteristics mismatched to request A backup was attempted and the storage unit selected for use had the characteristics that were not compatible with the backup

Perform "Resolving Network Communication Problems" on page 21. Status Code: 29 Top Message: failed trying to exec a command Explanation: A command could not be executed. Status Code 268 ==================== the vault session directory is either missing or inaccessible This error occurs when a Vault job cannot access the following: UNIX: /usr/openv/netbackup/vault/sessions Windows: install_path\NetBackup\vault\sessions This directory is For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code.

If the server is a valid server, verify that it is in the server list on the client. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Status code 241 when taking Oracle backup using or... It is possible that updates have been made to the original version after this document was translated and published. https://www.veritas.com/support/en_US/article.000031567 Status Code 194 ==================== the maximum number of jobs per client is set to 0 The NetBackup Maximum jobs per client global attribute is currently set to 0.

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 Below are some of the NetBackup status error codes from Status Code 241 to Status Code 245 which may be received while using the Symantec NetBackup tool. Check the NetBackup Problems report for clues on where and why the failure occurred. Nonetheless, not all files that you download from the internet is useful because there are incomplete ones.

Status Code 219 ==================== the required storage unit is unavailable The policy or schedule for the backup requires a specific storage unit, which is currently unavailable. http://www.sqlserverf1.com/symantec-netbackup-status-code-241-to-status-code-245/ On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." d. 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 Verify that there is space in the file system that contains the NetBackup databases. 3.

Status Code 97 ==================== requested media id is in use, cannot process request An operation was requested on a media ID that is in use. have a peek at these guys This status code is used for a generic system call failure that does not have its own status code. If you continue to have problems, review "Resolving Network Communication Problems" on page 21 and "Verifying Host Names and Services Entries" on page 31. The names of the files are logged in the activity log file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar processes them.

It should not occur for standard file system backups.Open a NetBackup support case (recommended in Symantec document 276903.pdf) if you encounter this error for the following: a UNIX or Windows file A network problem or a problem with the process that writes to the socket can cause socket read failure. * A problem specific to NetBackup Snapshot Client (see recommended actions). Status Code 73 ==================== bpstart_notify failed The bpstart_notify script returned a nonzero exit code. http://nodatasource.com/netbackup-error/netbackup-error-213.html However, the disk file path already exists and is not a directory.

You may also refer to the English Version of this knowledge base article for up-to-date information. Status Code: 21 Top Message: socket open failed Explanation: A socket open failed. Add more swap space or physical memory.

Check the progress log for any unusual messages from rbak.

  1. A possible cause is that the system is overloaded with too many processes and not enough physical or virtual memory.
  2. Status Code 27 ==================== child process killed by signal A child of the process that reported this error was terminated.
  3. DLL Files are Lost When there is a missing file during the process of a certain program, expect this Netbackup Error 241 to come up.

Status Code 221 ==================== continue This status code is used to coordinate communication between various NetBackup processes and normally does not occur. Article:000031567 Publish: Article URL:http://www.veritas.com/docs/000031567 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in Status Code: 44 Top Message: network write failed Explanation: An attempt to write data to a socket failed. If that is not the problem and you need more information: 1.

It must be one of these. It indicates the following: either the bpdbm process (on UNIX) or the NetBackup Database Manager service (on Windows) or the process that communicates with it has received unexpected information. No Yes Did this article save you the trouble of contacting technical support? this content On Windows, these daemons are the NetBackup Request Manager and NetBackup Database Manager services.

No altnames configuration for this client exists on 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 · There was Create a bpbkar activity log directory. If the problem is due to mandatory file locking, you can have NetBackup skip the locked files by setting LOCKED_FILE_ACTION to SKIP in the /usr/openv/netbackup/bp.conf file on the client.

Status Code 159 ==================== licensed use has been exceeded A configuration limit was exceeded. Verify that the server list settings are correct on both the client and the server. 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. Recommended Action: First, verify that the server did not crash.

Status Code 240 ==================== no schedules of the correct type exist in this policy The appropriate schedule was not found in the specified policy. option exists in the bp.conf file on the following: a UNIX NetBackup server or in the registry on a Windows NetBackup server. That storage unit may have more unused capacity now than it did when the job failed. An example of this operation is the attempt to suspend or freeze a volume while it is in use for a backup or restore.

Status Code: 52 Top Message: timed out waiting for media manager to mount volume Explanation: The requested volume was not mounted before the timeout expired. This problem can occur during a backup or restore in either a single or a multiple server configuration. On a UNIX system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd. 3. One instance when this code appears is if a NetBackup master or slave server is shut down or rebooted when a backup or restore is in process.

If this occurs during a read operation (restore, duplicate, verify), the drives could be busy. Recommended Action: Verify that the latest software is installed on the client and server. · On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file. · On Windows NT NetBackup servers,