Netbackup Error
Contents |
190 | 200 210 | 220 | 230 | 240 | 250 | 260 | netbackup error codes list 1 2 3 4 5 6 7 8 9 Status Code: 0 Top Message: "the requested netbackup error codes pdf 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 netbackup error codes and resolution 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
Veritas Netbackup Error Codes List
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 netbackup 7.7 status codes 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 network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives. To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives. Status Code: 3 Top Message: valid archive image produced, but no f
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 important error codes in veritas netbackup ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations
Veritas Netbackup Error Codes Pdf
Careers Legal Contact Us English ä¸ć–‡(简体) English Français Deutsch Italiano 日本語 í•śęµě–´ PortuguĂŞs Español USA Site:
Netbackup Status Code 1
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 Remember me Forgot Password? Don't http://backup.technion.ac.il/codes 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 Subscriptions Description This guide documents the NetBackup status codes, https://www.veritas.com/support/en_US/article.DOC5181.html 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 feedback right now, please try again later. Create/Manage Case QUESTIONS? CALL US: 1 (866) 837-4827 Solutions Unstructured DataSERVICES 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 Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal https://www.veritas.com/support/en_US/article.TECH68832 Contact Us English ä¸ć–‡(简体) English Français Deutsch Italiano 日本語 í•śęµě–´ PortuguĂŞs Español USA Site: Veritas Veritas PartnerNet STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors. Article:000037729 Publish: Article URL:http://www.veritas.com/docs/000037729 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 netbackup error to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors. Error Message Status Code: 58 Solution Overview: A status 58 error can occur during connections to legacy processes; bpcd, bprd, bpdbm, bpjobd, vmd, etc. typically from master or media server netbackup error codes to client, but alsofrom master server to media server, orfrom media servers to master, orfrom client to master servers, orin very rare cases from client to media server. The cause is that either a TCP SYN request did not reach the destination host, orthe expected processes were not listening on the destination host, orthe TCP SYN+ACK returned by the destination host did not reach the source host, orthe destination host could not validate that the inbound connection was from a valid NetBackup (NB) host, orthat PBX or vnetd on the destination host could not transfer the connection the desired daemon, orin rare instances that the destination host could not create a connection to the source host - for the same reasons as noted above. The majority of these situations are due to the TCP port(s) not being open through the firewall, daemon processes not running and listening on the destination host, the destination host being unable to resolve the IP address of the source host to a hostname, or the destination host not being configured to recognize the resolved hostname as a valid NB host.  Checking Connectivity from the Master Server to the Client When troubleshooting status 58 errors to a NetBackup host, the first thing to test is to whether or not you can access