Netbackup Exit Status 83 Media Open Error
Contents |
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 media open error 83 netbackup Vision 2016 Sign In media open error 83 netbackup 7 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting netbackup status code 83 media open error possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : client restore EXIT STATUS 83: media
Plug-in Reports Error 2060001 One Or More Invalid Arguments
open error fr... VOX : Backup and Recovery : NetBackup : client restore EXIT 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 netbackup restore media open error 83 05:27 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 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 A
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance image open failed: error 2060001: one or more invalid arguments Services CUSTOMER CENTER Customer Center Support Community MyVeritas
Image Open Failed: Error 2060013: No More Entries
Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership
Error Code 84 In Netbackup
Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA https://vox.veritas.com/t5/NetBackup/client-restore-EXIT-STATUS-83-media-open-error-from-disk/td-p/461287 Site: Veritas Veritas PartnerNet MSDP jobs fail with Media open error(83) Article:000023889 Publish: Article URL:http://www.veritas.com/docs/000023889 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 https://www.veritas.com/support/en_US/article.000023889 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 All MSDP jobs failing with Status 83 Media Open Error Error Message bptm log showing <16> bck01.local: [ERROR] PDVFS: PdvfsOpen: file get corrupted<16> bck01.local: [ERROR] PDVFS: PdvfsOpen: failed for "/bck01.local#1/2//NBU_PD_SERVER": Bad file descriptor (9)<16> bck01.local: [ERROR] PDSTS: tag_nbu_dsid: PdvfsOpen(/bck01.local#1/2//NBU_PD_SERVER) failed, unable to open tagfile (9:Bad file descriptor)<2> bck01.local: [DEBUG] PDSTS: tag_nbu_dsid: exit: match=<-1> (2060001:one or more invalid arguments)<16> bck01.local: [ERROR] PDSTS: pd_get_dsid_path: tag_nbu_dsid() failed (2060001:one or more invalid arguments) Cause The
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response https://support.symantec.com/en_US/article.TECH178397.html Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business http://systemmanager.ru/nbadmin.en/nbu_83.htm Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation media open 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 Security Center Home Blogs ISTR Threats media open error 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 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!' 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 co
check the following: NetBackup Problems report Event Viewer Application log (Windows) System log (UNIX and Linux) Typically, this status code indicates a drive configuration problem that allows more than one process at a time to open the device. On UNIX and Linux, the problem may be due one or more of the following: Two (or more) devices were configured that are the same physical device (for different densities perhaps). Verify that none of the /dev files that were used for these devices have the same major or minor numbers. Links exist in the file system that allow users access to the drives. The configuration for the drives was modified (in the administrator interface or vm.conf) and the Media Manager device daemon, ltid, was not restarted. Verify the configuration and then start ltid. On Windows, the problem may be that the Media and Device Management device configuration was modified but the NetBackup Device Manager service was not restarted. Verify the configuration and restart the NetBackup Device Manager service. On Windows, make sure the tapes are not write protected. For detailed troubleshooting information: Create a debug log directory for bpdm (if the device is disk) or bptm (if the device is tape). On UNIX and Linux, restartltid in the verbose mode by running the following: /usr/openv/volmgr/bin/ltid -v Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the vm.conf file if necessary. On Windows, enable verbose logging by adding VERBOSE on a line by itself in the install_path\Volmgr\vm.conf file. Then, stop and restart the NetBackup Device Manager service. Retry the operation and check the resulting debug log files. On Windows systems, look at the install_path\VERITAS\NetBackup\db\media\errors log for a drive that frequently produces errors. On UNIX and Linux systems, look at the /usr/openv/netbackup/db/media/errors log (which is also included in the /usr/openv/netbackup/bin/goodies/support/support script output) for a drive that frequently produces errors.