Media Open Error 83
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success media open error 83 netbackup 7 Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership
Plug-in Reports Error 2060001 One Or More Invalid Arguments
Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano netbackup restore media open error 83 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 83: A Status 83 "media open error" occurs on a recently configured disk storage
Image Open Failed: Error 2060001: One Or More Invalid Arguments
unit in Veritas NetBackup (tm) 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 Please sign in to set up your subscription. Close Sign In sts_get_server_prop_byname failed: error 2060046 plugin error 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 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
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates
Failure To Open Sts For Storage Server Netbackup
Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy
Netbackup Status Code 83
SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security error code 84 in netbackup 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 https://www.veritas.com/support/en_US/article.000030695 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 Partner Find a Partner Become a Partner Login Required Login into https://support.symantec.com/en_US/article.TECH178397.html 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 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=13969
check the following: NetBackup Problems report Event Viewer Application log (Windows) System log (UNIX and Linux) Typically, this status code http://systemmanager.ru/nbadmin.en/nbu_83.htm 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 http://www.tek-tips.com/viewthread.cfm?qid=913334 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 media open 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 media open error 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.
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum Media Open Error - Help please! thread776-913334 Forum Search FAQs Links MVPs Media Open Error - Help please! Media Open Error - Help please! andrewfr (MIS) (OP) 8 Sep 04 05:31 I have 5 jobs which run each night on an L20 robot under NetBackup 4.5.For the past two nights 3 of the jobs have Media Open Error[83] showing in the NetBackup Administration Console. It has been running fine for quite some time without problems until recently.There are 7 spare tapes in the ScratchPool so I would have thought that if there was a problem with any of the tapes then these would be used.The backup server and robot are off site so I tend to do most of my administration remotely only going up to change tapes periodically.Can anyone help me please?RegardsAndrew. RE: Media Open Error - Help please! lenski (TechnicalUser) 8 Sep 04 10:03 could be a configuration problem with the drives. They do sometimes get confused and have to be readded. Also check what your logs are telling you. RE: Media Open Error - Help please! Stumpr (TechnicalUser) 8 Sep 04 10:30 Are any of the tape drives going to a DOWN state?Are any of the tapes becoming FROZEN?I would run "verify" on the images on the tapesAlso the troubleshooying guide explains what logs to check.Just in case you don't have a TS guide.Here is the VERITAS link:http://ftp.support.veritas.com/pub/support/product... Bob StumpIncorrigible punster -- Do not incorrige RE: Media Open Error - Help please! andrewfr (MIS) (OP) 8 Sep 04 11:30 Thanks for the repli