Error 303 Netbackup
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 All NetBackup Vault duplications are failing; 303 - error encountered executing Media Manager command Article:000015482 Publish: Article URL:http://www.veritas.com/docs/000015482 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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Tape libraries were recently reconfigured and now all NetBackup Vault duplications fail with status code: 303 Error Message - error encountered executing Media Manager command (303) Cause The Vault Profile was originally configured with a robot TLD(1). Another Tape Library previously configured as TLD(0) has since been removed from the backup environment. After re-running Device Configuration, the robot previously configured as TLD(1) has now assumed the default robot TLD(0). Solution Take a backup copy then edit the following two lines in the vault.xml file : On Line 3, change   Name="TLD(1)"  to  Name="TLD(0)"  and RobotNumber="1" to RobotNumber="0" On Line 5, change RobotVolumeGroup="00_001_TLD" to  RobotVolumeGroup="00_000_TLD Location for vault.xml file : Â
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 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Vault job failing with error encountered executing... VOX : Backup https://www.veritas.com/support/en_US/article.000015482 and Recovery : NetBackup : Vault job failing with error encountered executing... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Vault job failing with error encountered executing Media Manager command(303), while everything else is working fine. Sahana Level 2 https://vox.veritas.com/t5/NetBackup/Vault-job-failing-with-error-encountered-executing-Media-Manager/td-p/617998 ‎04-24-2013 09:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, Vault job on one of our master servers is failing with "error encountered executing Media Manager command(303)". Below is the detailed status: 4/25/2013 3:31:53 AM - requesting resource kynudcms033.NBVAULT.MAXJOBS 4/25/2013 3:31:53 AM - requesting resource kynudcms033.NBU_POLICY.MAXJOBS.Ejection_Notification 4/25/2013 3:31:53 AM - granted resource kynudcms033.NBVAULT.MAXJOBS 4/25/2013 3:31:53 AM - granted resource kynudcms033.NBU_POLICY.MAXJOBS.Ejection_Notification 4/25/2013 3:31:54 AM - estimated 0 kbytes needed 4/25/2013 3:31:54 AM - begin Parent Job 4/25/2013 3:31:54 AM - begin Vault, Start Notify Script 4/25/2013 3:31:54 AM - started process RUNCMD (4724) 4/25/2013 3:31:54 AM - ended process 0 (4724) Status 0 4/25/2013 3:31:54 AM - end Vault, Start Notify Script; elapsed time: 00:00:00 4/25/2013 3:31:54 AM - begin Vault, Execute Script 4/25/2013 3:31:54 AM - started process bpbrm (4680) 4/25/2013 3:32:01 AM - vault waiting for session ID lock 4/25/2013 3:32:01 AM - requesting resource kynudcms033.VAULT_CREATE_SESSION_ID.LOCK_TLD(0)_MYVAULT 4/25/2013 3:32:01 AM - granted resource kynudcms033.VAULT_CREATE_SESSION_ID.LOCK_TLD(0)_MYVAULT 4/25
Tag: Message: error encountered executing Media Manager command Symantec NetBackup status code 301 to status code 305 December 30, 2014 SQLServerF1 Leave a comment Symantec NetBackup product is a http://www.sqlserverf1.com/tag/message-error-encountered-executing-media-manager-command/ backup and recovery product designed for enterprise users. Symantec NetBackup tool can http://www.tremka.com/archive/index.php/t-57618.html be used to perform backups of SQL Server databases and provides various features. Below are some of the NetBackup status error codes from Status Code 301Â to Status Code 305 which may be received while using the Symantec NetBackup tool. NetBackup status code: 301 Message: vmchange api_eject command failed Explanation: During the error 303 eject process, the vmchange command is called with an -api_eject call to begin the process to eject media. This command call failed. RecommendedAction: Review the Vault debug log in the following directory for detailed information about why the process failed: UNIX and Linux: /usr/openv/netbackup/logs/vault Windows: install_path\NetBackup\logs\vault Also review the summary.log in each of the sidxxx directories that had problems: UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx error 303 netbackup Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx (where xxx is the session ID) When the problem is resolved, rerun the Vault session, vlteject command, or vltopmenu command. NetBackup status code: 302 Message: error encountered trying backup of catalog (multiple tape catalog backup) Explanation: This error occurs when the NetBackup command that was used for stage one of the two-stage catalog backup fails. Recommended Action: For the actual error that caused the failure, review the Vault debug log in the following directory: UNIX and Linux: /usr/openv/netbackup/logs/vault Windows: install_path\NetBackup\logs\vault Review the summary.log in each of the sidxxx directories that had problems: UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx (where xxx is the session ID) In addition, review the admin debug log in the following directory: UNIX and Linux: /usr/openv/netbackup/logs/admin Windows: install_path\NetBackup\logs\admin Correct the error and rerun the Vault session. NetBackup status code: 303 Message: error encountered executing Media Manager command Explanation: This error occurs when a Media and Device Management command fails during a Vault job. Recommended Action: For the actual error that caused the command to fail, review the Vault debug log in the following directory: UNIX and Linux: /usr/openv/netbackup/logs/vault Windows: install_path\NetBackup\logs\vault Also rev
failing with error encountered executing Media Manager command(303), while news_catcher25.04.2013, 12:09Ja, ich suche eine Lösung Hi All, Vault job on one of our master servers is failing with "error encountered executing Media Manager command(303)". Below is the detailed status: 4/25/2013 3:31:53 AM - requesting resource kynudcms033.NBVAULT.MAXJOBS 4/25/2013 3:31:53 AM - requesting resource kynudcms033.NBU_POLICY.MAXJOBS.Ejection_Notificati on 4/25/2013 3:31:53 AM - granted resource kynudcms033.NBVAULT.MAXJOBS 4/25/2013 3:31:53 AM - granted resource kynudcms033.NBU_POLICY.MAXJOBS.Ejection_Notificati on 4/25/2013 3:31:54 AM - estimated 0 kbytes needed 4/25/2013 3:31:54 AM - begin Parent Job 4/25/2013 3:31:54 AM - begin Vault, Start Notify Script 4/25/2013 3:31:54 AM - started process RUNCMD (4724) 4/25/2013 3:31:54 AM - ended process 0 (4724) Status 0 4/25/2013 3:31:54 AM - end Vault, Start Notify Script; elapsed time: 00:00:00 4/25/2013 3:31:54 AM - begin Vault, Execute Script 4/25/2013 3:31:54 AM - started process bpbrm (4680) 4/25/2013 3:32:01 AM - vault waiting for session ID lock 4/25/2013 3:32:01 AM - requesting resource kynudcms033.VAULT_CREATE_SESSION_ID.LOCK_TLD(0)_MY VAULT 4/25/2013 3:32:01 AM - granted resource kynudcms033.VAULT_CREATE_SESSION_ID.LOCK_TLD(0)_MY VAULT 4/25/2013 3:32:03 AM - vault session ID lock acquired 4/25/2013 3:32:04 AM - vault session ID lock released 4/25/2013 4:12:38 AM - vault global lock released 4/25/2013 4:12:42 AM - end writing Status 303 4/25/2013 4:12:42 AM - end Vault, Execute Script; elapsed time: 00:40:48 4/25/2013 4:12:42 AM - begin Vault, Stop On Error Status 0 4/25/2013 4:12:42 AM - end Vault, Stop On Error; elapsed time: 00:00:00 4/25/2013 4:12:42 AM - begin Vault, End Notify Script 4/25/2013 4:12:42 AM - started process RUNCMD (2128) 4/25/2013 4:12:42 AM - ended process 0 (2128) Status 0 4/25/2013 4:12:43 AM - end Vault, End N