Netbackup Error Code 607
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 Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup status code 607: no images were found to synthesize Article:000091081 Publish: Article URL:http://www.veritas.com/docs/000091081 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 this Article Manage your Subscriptions Problem NetBackup status code 607: no images were found to synthesize Solution Message: no images were found to synthesize Explanation: The database query to obtain the images to synthesize for the given policy did not return any images. Recommended action: Ensure that a synthetic full backup has one full image (real or synthetic) and one or more subsequent incremental images (differential or cumulative) to synthesize. For a cumulative synthetic backup, there must be two or more incremental (differential or cumulative) images to synthesize. Adjust your schedules so the appropriate backup jobs complete successfully before the synthetic job is run. The scheduler does not retry a synthetic backup job that fails with this error code. 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 transSERVICES 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 Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet There is no article that matches your request Support https://www.veritas.com/support/en_US/article.000091081 / 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 Search Survey Did this article answer https://www.veritas.com/support/en_US/article.000093618 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 Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Services Consulting Services Managed Services Appliance Services Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process About Corporate Profile Corporate Leadership Newsroom Corporate Responsibility Careers © 1995–2016 Veritas Technologies LLC Sitemap Legal Terms Privacy Contact Set default language Do you wish to save this as your future site? No Yes
All Log Entries report and also the progress log (if there is one). The following are some of the problems that can appear under status code 1: A file or a directory path is more than 1023 characters long. For NetBackup Snapshot http://systemmanager.ru/nbadmin.en/nbu_1.htm Client, the maximum path name length is 1000 characters for snapshot backups, not 1023. When the snapshot is created, a new mount point is added to the beginning of the file path. If the new mount point plus the original file path exceeds 1023 characters, the backup fails with status code 1. The progress log includes the entry "ERR-Skipping long dir path." You cannot open a file. The file may have netbackup error been locked for some reason. The following information applies only to UNIX and Linux systems: NetBackup cannot get the link name of a file. The following information applies only to UNIX and Linux systems: NetBackup cannot process a sparse file. A read error that was encountered in a file. File is of an unknown type, or may be hidden. The following information applies only to UNIX and Linux systems: The lstat system netbackup error code call fails on a file that is eligible to be backed up. This error may be a permission problem. The following information applies only to UNIX and Linux systems: A file cannot be locked that has mandatory locking enabled. A synthetic backup job may terminate with a status code 1 under the following conditions: - No images were found to synthesize (status code = 607). - TIR info has been pruned from component images (status code = 136). - Image format is unsupported (status code = 79). The synthetic backup job logs the actual status code in the NetBackup error log. Refer to the documentation for the corresponding NetBackup error code for the corrective action to take. A BMR job may terminate with status code 1 in the following situation: You save the BMR configuration and it returns an error even though the child jobs completed successfully. For information, examine the Detailed Status tab of the Job Details dialog box, or the nbjm unified log (originator ID 117). A policy that contains multiple backup scripts starts a scheduled backup of a UNIX database extension client. If it fails with a status code 1, some of the backup scripts returned a failure status. On clients using Windows Open File Backups (W
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 02:21:37 GMT by s_wx1206 (squid/3.5.20)