mph999 Level 6 Employee Accredited â€Ž06-11-2012 03:05 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Next step is disk o • On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). How can I solve this? (I want to use the same /storage1 path on backup-media) Solved! NetBackup executes client processes as the requesting user. weblink
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 Execute a df to see if the system can read the mount table. 2. Status Code: 14 Top Message: file write failed Explanation: A write to a file or socket failed. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred.
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 The accept system call timed out after 60 seconds. Then, retry the operation and check the resulting activity log.
Recommended Action: 1. Create an activity log directory for the process that reported the problem and the operation. On UNIX and Windows NT clients, enable bpbkar activity logging. Recommended Action: First, verify that the server did not crash.
It can also occur if the network or server is heavily loaded and has slow response time. I also presume of course you are following the manuals for deleting and recreating ? NetBackup status code: 242 Message: operation would cause an illegal duplication Explanation: If the request is processed, it causes a duplicate entry (for example, in the catalog or the configuration database). To delete the it, I just deleted the storage pool and the storage unit from the Storage-> Storage Units in Admin console, but judging for your comment, maybe that was not
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT. Then retry the operation and check the resulting activity logs. 2. No Yes How can we make this article more helpful?
Status Code: 62 Top Message: wbak exited abnormally Explanation: The wbak process on the Apollo exited abnormally. https://vox.veritas.com/t5/NetBackup/Status-242-when-adding-a-new-tape-drive/td-p/425986 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. This error should not occur through normal use of NetBackup. Status Code: 32 Top Message: could not set group id for process Explanation: Could not set the group ID of a process to the requesting user group.
Status Code: 73 Top Message: bpstart_notify failed Explanation: The bpstart_notify script returned a nonzero exit code. have a peek at these guys o Check the inetd log to see if NetBackupListen is running. 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 Thank You!
Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error illegal duplication (242) when reconfiguring deduplication on o On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 4. 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. http://nodatasource.com/netbackup-error/netbackup-error-213.html A frequent cause is that the server's file system is full.
To increase the logging level, set the loglevel parameter in the mac.conf file to a higher value. 1. On an SCO system, code 60 can occur because the mount-point path name exceeds 31 characters, which is the maximum allowed on an SCO system. Enable detailed activity logging: o Create a bpbkar activity log directory (UNIX or Windows NT only).
Showing results forÂ Search instead forÂ Do you meanÂ VOX : Backup and Recovery : NetBackup : Error illegal duplication (242) when reconfiguring... Status Code: 24 Top Message: socket write failed Explanation: A write operation to a socket failed. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. If you are using an AIX token ring adapter and the routed daemon is running, the timeout can occur because the token ring adapter creates dynamic routes, causing the routed daemon
These clients can handle only one NetBackup job at a time. 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 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). this content Status Code: 22 Top Message: socket close failed Explanation: A socket could not be closed.
However, you must check other status as explained in the related NetBackup manual to see if the database was successfully backed up. Buy the Full Version More From This UserTroubleshooting commandsNetBackup Admin Guide UNIX Server Ivue-quicksheet Netbackup Error StatusCodes by Sunil Lingala2.1K viewsEmbedDownloadDescriptionThis guide helps in finding NetBackup status codesThis guide helps in Recommended Action: 1. Verify that the server list specifies the correct master server.
The default for the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if unspecified. 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