Netbackup Error 41 Unix
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In
Status 41 Netbackup
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down netbackup network connection timed out(41) your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX netbackup error code 41 troubleshooting : Backup and Recovery : NetBackup : Error code 41 VOX : Backup and Recovery : NetBackup : Error code 41 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read
Status Code 41 In Cobol
Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error code 41 setaylor Level 2 ‎10-20-2012 02:17 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content All of a sudden I'm receiving error code 41 on my Oracle servers, I have increase the time out to 1800, backup will not write, just stays active. Labels: 7.5 Backup and Recovery NetBackup Troubleshooting 1 Kudo Reply 8 Replies General Symantec Nicolai Moderator Partner Trusted Advisor ‎10-20-2012 02:35 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content General Symantec recommendation for status code 41:http://www.symantec.com/docs/HOWTO34927 Status 41 is anetwork connection timed out - which mean the network connection was not answered in the other end. Are you able to ping the Oracle Servers ? And if you are able to ping what does this command return : bptestbpcd -client xxx -verbose 0 Kudos Reply In addtion to the tech note Dyneshia Level 6 Employee ‎10-21-2012 09:15 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content In addtion to the tech note Nicolai referenced, here is some addional information : A status 41 during backup/restore is 99% of the time caused by network performance and tuning. 1) The first item we tune is the Client read timeout. During a backup, the NetBackup client agent may not be able to send keepalives to the media server if the read of client data is
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines https://vox.veritas.com/t5/NetBackup/Error-code-41/td-p/543408 Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your http://www.tek-tips.com/viewthread.cfm?qid=730182 site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum Network Timeout 41 error thread776-730182 Forum Search FAQs Links MVPs Network Timeout 41 error Network Timeout 41 error rdapilmoto (Programmer) (OP) 15 Dec 03 12:05 Getting this 41 error on a backup client and can't seem to resolve this:10:14:20.543 [21142] <4> bpbkar: INF - setenv BPSTART_TIMEOUT=30010:14:20.543 [21142] <4> bpbkar: INF - setenv BPEND_TIMEOUT=30010:14:20.543 [21142] <4> bpbkar: INF - setenv BACKUPID=sys98396_107150473110:14:20.543 [21142] <4> bpbkar: INF - setenv UNIXBACKUPTIME=107150473110:14:20.544 [21142] <4> bpbkar: INF - setenv BACKUPTIME=Mon Dec 15 10:12:11 200310:14:20.544 [21142] <4> bpbkar: INF - BACKUP START10:14:20.544 [21142] <4> bpbkar: INF - Estimate:-1 -110:14:20.545 [21142] <4> bpbkar: INF - Processing /10:14:20.583 [21142] <4> bpbkar: INF - Excluded /core by exclude_list entry /core10:45:05.951 [21142] <16> bpbkar: ERR - Cannot write to STDOUT. Errno = 32: Broken pipe10:45:05.952 [21142] <16> bpbkar: ERR - bpbkar FATAL exit sta
190 | 200 210 | 220 | 230 | 240 | 250 | 260 http://backup.technion.ac.il/codes | 1 2 3 4 5 6 7 8 9 Status Code: 0 Top 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 netbackup error 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 Top Message: "the requested operation was partially successful" Explanation: A problem that may require corrective action was detected during the requested operation. netbackup error 41 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 Top 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 instruc