Client Restore Exit Status 83 Media Open Error
Contents |
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 media open error 83 netbackup Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services media open error 83 netbackup 7 Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home image open failed: error 2060001: one or more invalid arguments 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
Plug-in Reports Error 2060001 One Or More Invalid Arguments
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 Builder Opportunity Registration image open failed: error 2060013: no more entries 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 SYM16-015 Security Advisory 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 Error 10/12/2011 7:49:16 PM - started process bptm (3252) 10/12/2011 7:49:16 PM - Critical bptm(pid=3252) sts_get_lsu_prop_byname on LSU E:\catalogbackup failed: 2060013 no more entries 10/12/2011 7:49:16 PM - Critical bptm(pid=3252) Invalid storage device: E:\catalogbackup no more entries 10/12/201
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 netbackup restore error 83 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you
Error Code 84 In Netbackup
quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for
Netbackup Status Code 83
Do you mean VOX : Backup and Recovery : NetBackup : client restore EXIT STATUS 83: media open error fr... VOX : Backup and Recovery : NetBackup : client restore EXIT https://support.symantec.com/en_US/article.TECH171649.html STATUS 83: media open error fr... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page client restore EXIT STATUS 83: media open error from disk Pratique Level 4 03-09-2012 05:27 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content https://vox.veritas.com/t5/NetBackup/client-restore-EXIT-STATUS-83-media-open-error-from-disk/td-p/461287 Hi, I have been facing issues in restoring data from a media server on which data domain is configured. The backups are all running fine but restore is been a pain. There is nothing in FORCE_RESTORE_MEDIA_SERVER for the applicable media server. Here's the error: Mar 10, 2012 4:40:22 AM - begin Restore Mar 10, 2012 4:40:26 AM - restoring from image de01bzdb028-bu.am.mot-solutions.com_1330635363 Mar 10, 2012 4:40:26 AM - requesting resource @aaaab Mar 10, 2012 4:40:27 AM - granted resource MediaID=@aaaab;DiskVolume=levstvndc004_lsu;DiskPool=levstvndc004_dp;Path=levstvndc004_lsu;StorageSer... Mar 10, 2012 4:40:41 AM - connecting Mar 10, 2012 4:40:43 AM - Warning bpbrm (pid=3184) expected start message from de01bzdb028-bu.am.mot-solutions.com; read: Unrecognized -J string spsrestoreoptions=0 Mar 10, 2012 4:40:43 AM - connected; connect time: 0:00:00 Mar 10, 2012 4:40:43 AM - started process bptm (pid=3200) Mar 10, 2012 4:40:49 AM - Critical bptm (pid=3200) sts_get_cred failed: error 3 emmerr 254 Mar 10, 2012 4:40:50 AM - Critical bptm (pid=3200) failure to open sts for storage server ndc-datadomain-bu3.am.mot.com: plug-in reports error 2060001 one or more invalid arguments Mar 10, 2012 4:40:55 AM - Error bpbrm (pid=3184) client restore EXIT STATUS 83: media open error Mar 10, 2012 4:40
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 https://www.veritas.com/support/en_US/article.TECH155301 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: https://www.veritas.com/support/en_US/article.000005208 Veritas Veritas PartnerNet Restore using SAN client fails with status 5 and status 83 if the configured number of data buffers is too large Article:000012451 Publish: Article media open URL:http://www.veritas.com/docs/000012451 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 media open error Subscriptions Problem Restores using SAN Client fail even though backups are successful. Restores over the LAN are also successful. Error Message This example is for an SAP backup, but the situation is the same for Standard, Windows NT, Oracle, SAP, etc. The Activity Monitor and comm file on the client show the restore failing with a media open error. 10:09:44 10.03.2011: Restore Started 10:09:48 (7704260.xxx) Restore job id 7704260 will require 1 image. 10:09:48 (7704260.xxx) Media id 000001 is needed for the restore. 10:09:48 (7704260.xxx) Media id 000002 is needed for the restore. 10:09:54 (7704260.001) Restoring from copy 2 of image created Mon Feb 14 21:04:39 2011 10:10:03 (7704260.001) The following files/folders were not restored: 10:10:03 (7704260.001) UTF - /H/oracle/SID/sapdata6/USER1I_5/USER1I.DATA5 10:10:04 (7704260.001) Status of restore from copy 2 of image created Mon Feb 14 21:04:39 2011 = media open error 10:10:04 INF - Server status = 5 10:10:05 (7704260.xxx) INF - Status = the restore failed to recover the requested files
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 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 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: 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: Windo