Netbackup Status 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 Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English media open error 83 netbackup 7 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet plug-in reports error 2060001 one or more invalid arguments STATUS CODE 83: A Status 83 "media open error" occurs on a recently configured disk storage unit in Veritas NetBackup (tm)
Netbackup Status Code 83 Media Open Error
6.0. Article:000030695 Publish: Article URL:http://www.veritas.com/docs/000030695 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
Netbackup Restore Media Open Error 83
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: A Status 83 "media open error" occurs on a recently configured disk storage unit in Veritas NetBackup (tm) 6.0. Error Message media open errorbackups not permitted to root device Solution Overview:A Status 83 "media open error" occurs on a recently image open failed: error 2060001: one or more invalid arguments configured disk storage unit in NetBackup 6.0.Troubleshooting: By default, a disk storage unit in NetBackup 6.0 can not point to the same volume on which Windows is installed. The detailed status on the job will note "backups not permitted to root device". This is to protect the system volume from running out of disk space.Master Log Files: Activity Monitor (Detailed Status)12/16/2005 12:24:23 PM - started process bpdm (28328)12/16/2005 12:24:23 PM - Critical bpdm(pid=28328) 12/16/2005 12:24:23 PM - Critical bpdm(pid=28328) Invalid STS storage device: C:\dsu 12/16/2005 12:24:23 PM - Critical bpdm(pid=28328) bp_sts_open_disk failed: error 37 12/16/2005 12:24:25 PM - Error bpbrm(pid=30904) from client billybats: ERR - bpbkar exiting because backup is aborting 12/16/2005 12:24:29 PM - end writingmedia open error(83)Resolution: Configure the disk storage unit to write to a path that is allowed: 1. Launch the NetBackup Administration Console 2. Click Storage Units in the left pane 3. In the right pane, double click the disk storage unit in question 4. In the Change storage unit window, enter a path name that doesn't exist on the Windows System Volume, or uncheck the checkbox that says "This directory can only exist on the root file system or system disk" (F
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
Image Open Failed: Error 2060013: No More Entries
Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services error code 84 in netbackup Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions netbackup error 2060013 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 https://www.veritas.com/support/en_US/article.000030695 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 Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin https://support.symantec.com/en_US/article.TECH178397.html 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!' status 83 media open error TECH178397 July 28th, 2012 http://www.symantec.com/docs/TECH178397 Support / status 83 media open 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 Backups are failing with status code 83 media open error. 01/05/2012 07:10:52 - Critical bptm (pid=1396906) backups not permitted to root device 01/05/2012 07:10:52 - Critical bptm (pid=1396906) Invalid storage device: /daily access not allowed 01/05/2012 07:10:52 - Critical bptm (pid=1396906) failure to open disk at path /daily: plug-in reports error 2060037 01/05/2012 07:10:52 - Critical bptm (pid=1396906) image delete failed: error 2060001
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website https://support.symantec.com/en_US/article.TECH171649.html Security SSL Certificates Complete Website Security Code Signing Certificates http://veritas-bu.mailman.eng.auburn.narkive.com/pH0ayZdR/media-open-error-83-having-upgraded-the-os 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 Industries media open 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 Removal Tools media open error 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 83: media open error E
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 submis