Netbackup Error 63
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas netbackup error codes and solutions Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile netbackup error codes pdf Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English ä¸æ–‡(简体) English veritas netbackup error codes list Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet Status 63: process was killed by a signal(63) Article:000009591 Publish: Article URL:http://www.veritas.com/docs/000009591 netbackup error codes and resolution 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to
Netbackup 7.7 Status Codes
this Article Manage your Subscriptions Problem NetBackup 6.5.x client backup fails with Status 63. Error Message Activity Monitor job details shows message: process was killed by a signal(63) Windows client bpbkar log shows: 3:37:14.829 PM: [300.1936] <32> TransporterRemote::write[2](): FTL - SocketWriteException: send() call failed, could not write data to the socket, possible broken connection.3:37:14.845 PM: [300.1936] <16> NBUException::traceException(): (An Exception of type [Symantec::NetBackup::Ncf::OperationFailedException] was thrown. Details about the exception follow...:Error code = (-1008).Src file   = (D:\654\src\cl\clientpc\util\tar_tfi.cpp).Src Line   = (275).Description = (%s getBuffer operation failed).Operation type=().)3:37:14.845 PM: [300.1936] <16> NBUException::traceException(): (An Exception of type [Symantec::NetBackup::Ncf::SocketWriteException] was thrown. Details about the exception follow...:Error code = (-1027).Src file   = (TransporterRemote.cpp).Src Line   = (310).Description = (send() call failed, could not write data to the socket, possible broken connection).Local IP=(). Remote IP=(). Remote Port No.=(0).No. of bytes to write=(32768) while No. of bytes written=(0).)3:37:14.845 PM: [300.1936] <4> tar_base::V_vTarMsgW:
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile
Important Error Codes In Veritas Netbackup
Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us common netbackup error codes English ä¸æ–‡(简体) English Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE: netbackup 7.6 error codes 63 and 13 are encountered when running a Veritas NetBackup (tm) FlashBackup on a client with a loopback file system (lofs) mounted. Article:000029711 Publish: Article URL:http://www.veritas.com/docs/000029711 Support / Article https://www.veritas.com/support/en_US/article.TECH142904 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 63 and 13 are encountered https://www.veritas.com/support/en_US/article.000029711 when running a Veritas NetBackup (tm) FlashBackup on a client with a loopback file system (lofs) mounted. Error Message bpfsmap: INF - put_imghdr: byteorder=0 bpbkar sighandler: ERR - bpbkar killed by signal 1 bpbkar Exit: ERR - bpbkar FATAL exit status = 63: process was killed by a signal bpbkar Exit: INF - EXIT STATUS 63: process was killed by a signal Solution Overview:A FlashBackup of a client can fail with a Status 63.  This will occur when backing up a volume that has a loopback file system associated with it.  The bpfis daemon is unable to properly handle the loopback file system (lofs) mount which causes the backup to fail with a Status 63.  This will generate a Status 63 in the bpbkar log and a Status 13 in the bpdbm log file.Troubleshooting:Issue the mount command on the client to determine what file system types are being backed up.# mount -p/dev/vg01/lvol1 /mnt1    vxfs delaylog,dev=40010001 0 0/mnt1/vobs    /data/vobs1 lofs defaults,dev=4f000008 0 0Log Files:The /usr/openv/netbackup/logs/bpdbm/log.
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing https://www.veritas.com/support/en_US/article.DOC5181.html Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research http://backup.technion.ac.il/codes Exchange Investor Relations Careers Legal Contact Us English ä¸æ–‡(简体) English Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet Symantec NetBackup 7.5 Status Codes Reference Guide Download Attachments Article:000003092 Publish: Article URL:http://www.veritas.com/docs/000003092 Support / Article Sign In error codes Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Download Attachments Print Article Products Related Articles Article Languages Subscribe to this Article Manage your netbackup error codes Subscriptions Description This guide documents the NetBackup status codes, providing definitions, actions, and examples. 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 have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? Email Address (Optional) Your feedback has been submitted successfully! Thank You! Sorry, we couldn't post your feedback190 | 200 210 | 220 | 230 | 240 | 250 | 260 | 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 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. 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 instructions in the user's guide for the client. · On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files. If you are backing up a n