Netbackup Error 191
Contents |
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
Database System Error 220 Netbackup
Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English nbstlutil report Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Duplication jobs fail with Status Code 191 (no images were successfully processed)" and "image read failed; error 2060017: system call failed" errors Article:000090158 Publish: Article URL:http://www.veritas.com/docs/000090158 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 Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem GENERAL ERROR: Duplication jobs fail with Status Code 191 (no images were successfully processed)" and "image read failed; error 2060017: system call failed" errors Error Message Critical bpdm (pid=10992) sts_read_image_failed: error 2060017 system call failedCritical bpdm (pid=10992) image read failed; error 2060017: system call failedError bpdm (pid=10322) cannot read image from disk. Invalid argment. Solution Overview:Duplication jobs fail with Status Code 191 (no images were successfully processed)" and "image read failed; error 2060017: system call failed" errorsCause:• More files are open than the memory cache manager can handle. As a result, the cache manager has exhausted the available paged pool memory.• The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is exhausted).Solution:On the Windows 2003 server in question, 2 Registry Keys (PoolUsageMaximum, PagedPoolSize) may be created to fine-tune how the operating system manages Paged Pool Memory. Microsoft(tm) controls these Operating System registry values, therefore Symantec cannot provide instructions on how to create or modify them. For more information on how to create and configure the
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 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup Appliance : Netbackup 5200 Duplication Jobs Fail with Error 19... https://www.veritas.com/support/en_US/article.TECH56632 VOX : Backup and Recovery : NetBackup Appliance : Netbackup 5200 Duplication Jobs Fail with Error 19... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Netbackup 5200 Duplication Jobs Fail with Error 191, then keep re-spawning and failing Stevo https://vox.veritas.com/t5/NetBackup-Appliance/Netbackup-5200-Duplication-Jobs-Fail-with-Error-191-then-keep-re/td-p/526411 Level 2 11-12-2012 02:55 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, We are having problems with duplication jobs on our Netbackup 5200 appliance. We use storage lifecycle policies to backup to the 5200 as the primary copy, and then duplicate off to tape. This has worked fine for months, but recently the duplication jobs have started failing with error 191. They start OK and backup a few GB of data, but then fail before the end (the primary copy backup jobs to the appliance complete OK). Looking more closely at the job log reveals the following: Critical bpdm(pid=14456) sts_read_image failed: error 2060017 system call failed Critical bpdm(pid=14456) image read failed: error 2060017: system call failed Error bpdm(pid=14456) cannot read image from disk, Invalid argument I originally thought this wassome kind of corruption on the appliance, but the strange this is that we can still backup to the appliance OK, and even restore from some of the imag
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services https://support.symantec.com/en_US/article.TECH150604.html Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center netbackup error Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support netbackup error 191 Home MySymantec Licensing Products A-Z Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Import Phase 2 fails with the status 191 for media read error. TECH150604 August 16th, 2011 http://www.symantec.com/docs/TECH150604 Support / Import Phase 2 fails with the status 191 for media read error. Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation The production Netbackup Master Server have a tape library connected over the FC network and the backups which are required for IMPORT are spanned between two media s. On the DR Netbackup Master Server there is only a standalone tape drive connected and the IMPORt Phase 1 completes but Phase 2 fails with Status Code 191 Error Job Details 1/28/2011 2:59:50 PM - begin Import 1/28/2011 3:00:13 PM - started process bptm (1476) 1/28/2011 3:00:13 PM - started process bptm (5104) 1/28/2011 3:00:13 PM - requesting resource XXXXL3 1/28/2011 3:00:13 PM - granted resource xxxxL3 1/28/2011 3:00:13 PM - granted resource IBM.ULTRIUM-TD3.000 1/28/2011 3:00:15 PM - started process bptm (1476) 1/28