Netbackup Status Code 83 Media Open Error
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 media open error 83 netbackup Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research
Media Open Error 83 Netbackup 7
Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português plug-in reports error 2060001 one or more invalid arguments Español USA Site: Veritas Veritas PartnerNet NetBackup backup fails with, media open error (83) when writing to a media server deduplication pool. Article:000005208 Publish: Article URL:http://www.veritas.com/docs/000005208 netbackup restore media open error 83 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
Image Open Failed: Error 2060001: One Or More Invalid Arguments
Manage your Subscriptions Problem GENERAL ERROR: NetBackup backup fails with, media open error (83) when writing to a media server deduplication pool. Error Message sts_open_server failed: error 2060002 memory allocation Cause Error Code(s)/Message(s):Using the Windows NetBackup Administration Console open the Activity Monitor and view the failed job, Detailed Status:Error sequence:3/13/2010 10:22:57 AM - Critical bptm(pid=2580) sts_open_server failed: error 2060002 memory allocation 3/13/2010 10:22:57 AM - Critical bptm(pid=2580) failure to open sts for storage server media_server_name: plug-in reports error 2060002 memory allocation3/13/2010 10:23:04 AM - end writingmedia open error(83)Overview: The backup is writing to a Media Server Deduplication Pool.The System event logs reported an Application popup:Pop-up: System event logs Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Solution The media server didn't have the minimum memory requirements. Increasing memory resolved the error.Refer to the Symantec NetBackup Deduplication Guide Release 7.0 to ensure the Deduplication
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 error code 84 in netbackup Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 sts_get_server_prop_byname failed: error 2060046 plugin error 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 83: When attempting a backup which goes to a
Image Open Failed: Error 2060013: No More Entries
NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Article:000032095 Publish: Article URL:http://www.veritas.com/docs/000032095 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? https://www.veritas.com/support/en_US/article.000005208 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 STATUS CODE 83: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code https://www.veritas.com/support/en_US/article.000032095 83 (media open error). Error Message media open error Solution Overview: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Troubleshooting: Please review the TechNote on Status Code 83 in the Related Documents section, and confirm that is not the issue. Then, check the NetBackup Client Service, and see what Windows account is starting the service. Log files: N/A Resolution: If the backup is going to a network location on a NAS server, the NetBackup Client Service needs to start with an account that has access to the network. The local system account does not have access to the network (see Figure 1). Figure 1 Changed the NetBackup Client Server to start with an account with network privileges, and stop and restart the service (see Figure 2). Figure 2 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 originaPKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation https://support.symantec.com/en_US/article.TECH171649.html Website Security SSL Certificates Complete Website Security Code Signing http://veritas-bu.mailman.eng.auburn.narkive.com/pH0ayZdR/media-open-error-83-having-upgraded-the-os Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services 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 media open 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 Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates media open error 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 Home MySymantec Licensing Products A-Z Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' "EXIT STATUS 83: media open error" during catalog restore TECH171649 July 28th, 2012 http://www.symantec.com/docs/TECH171649 Support / "EXIT STATUS 83: media open error" during catalog restore 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 Catalog recovery fails with: Error bpbrm(pid=5864) client restore EXIT STATUS
on a Sun Ultra-5 system, no MPs of FPs, just the Solaris jumbo patch for Netbackup (108261-11).I have been testing 3.2 and the effect of upgrading Solaris from 2.6 to 8 on a test system with a standalone tape drive. Sun said all I would need to do having upgraded was to install the jumbo patch mentioned above.One thing I did have to do having upgraded/patched the OS was to re-install the sg driver as it was missing (/opt/openv/volmgr/bin/driver/sg.install).Backups are now a fairly unpredictable affair. I think any manual backup I kick off via bpadm works successfully, but anything that's scheduled or run via cli (bpbackup) can fail with an error code of 83 (media open error).I've searched the Veritas archive and uncovered nothing, the archive for veritas-bu did have an entry from about 2001, which said to check classes. I have .... they're fine.I'm now running the ltid daemon in verbose mode, but this is as good as it gets :-10:28:19 [19382] <2> bptm: INITIATING: -mlist -cmd10:28:19 [19382] <2> bptm: EXITING with status 0 <----------10:29:17 [19358] <2> io_position_for_write: locate block is done10:29:19 [19358] <2> io_open: retrying open, errno = I/O error10:29:28 [19358] <2> io_open: retrying open, errno = I/O error10:29:33 [19358] <16> io_open: cannot open file /usr/openv/netbackup/db/media/tpreq/DD0036, I/O error10:29:33 [19358] <2> log_media_error: successfully wrote to error file - 07/16/03 10:29:33 DD0036 0 OPEN_ERROR10:29:33 [19358] <2> check_error_history: called from bptm line 13294, EXIT_Status = 83The above is a small section, I didn't want to stuff this e-mail with output.Have I got some kind of drive configuration problem post-upgrade or do I need to look at the batch of media that I am using? Do I need a Netbackup patch of some kind?Thank you in advance & have a splendid day,PaulPaul RedmanUnix Systems Admin - Hilton TFO HelpdeskCustomer Support & Solutions Centre (CSSC)HP ServicesHewlett PackardTel: External +44 (0)118 916 2075http://www.hp.com David Chapa 2003-07-16 14:27:30 UTC PermalinkRaw Message Did you preserve your st.conf file before applying the jumbo patch?I would start there, since the jumbo patches are notorious for layingdown a "new" copy of the st.conf file.After re-reading one of the sections of your email...its seems that thismay not be the case. You mention that manual submissions seem to work,but scheduled do not.I would created bpsched, bpdbm and bptm directories to start in/usr/openv/netbackup/logs to see what information you may get from it.I would pay particular attention to bptm and bpsched.David Chapa-----Original Message-----From: