Netbackup Error Bplabel
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 Vision 2016 Sign bplabel command netbackup In CommunityCategoryBoardResourcesUsers turn
Netbackup Bplabel Example
on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Error Requesting Media Tpreq 98
Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : NetBackup 6.5 bplabel failing to relabel media VOX : Backup and Recovery :
Status 99
NetBackup : NetBackup 6.5 bplabel failing to relabel media 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 NetBackup 6.5 bplabel failing to relabel media grapes Level 2 04-12-2011 10:26 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I have a NetBackup 6.5.6 Enterprise install with a standalone tape drive. I noticed recently that 2 tapes had the same media id. I've now discovered that NetBackup is automatically labelling any new tape that I put in the tape drive as A00002. I now have 3 tapes that are A00002. First I tried to delete the volumes and create new volumes as the next consecutive available media id like A00012 for example. After that I would insert the tape and then tryto re-label them with bplabel in the command prompt and also through using the admin console. Using -o or unchecking the 'verify media label' checkbox does nothing because NetBackup still waits for the A00002 media id to load (or if in command prompt displays "Error reported by media operation: resource request failed". If A00002 is loaded, all it does is relabel the volume as A00002. Running a format on the volumes also re-labels them as the same media id. How do you force NetBackup to just
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 When using bplabel or the NetBackup console to erase or https://vox.veritas.com/t5/NetBackup/NetBackup-6-5-bplabel-failing-to-relabel-media/td-p/386425 label media, a potential exists for unintentional erasure of NetBackup media containing valid images. Article:000010037 Publish: Article URL:http://www.veritas.com/docs/000010037 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 https://www.veritas.com/support/en_US/article.000010037 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 In certain circumstances, NetBackup will allow a bplabel (also known as a label, long erase, or quick erase) operation on media with valid images. Error Message During verification, an error similar to the following is reported in the Job Details: INF - Verify of policy test, schedule INCR (master.server_1288802281) failed, cannot read backup header, media may be corrupted. Cause The NetBackup bplabel command was designed to write a fresh tape header onto unassigned tapes - typically, tapes that were previously used with some other backup software. When executed via the command line, the bplabel command will not check the assignment status of the tapes being labeled or erased. When bplabel is executed
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 https://vox.veritas.com/t5/NetBackup-Appliance/Bplabel-failed-with-the-error-message-quot-error-requesting/td-p/608959 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest https://vox.veritas.com/t5/NetBackup/unable-to-take-the-backup-in-standalone-drive-using-netbackup/td-p/539678 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 Appliance : Bplabel failed with the error message "error reque... VOX : Backup and Recovery : NetBackup Appliance netbackup error : Bplabel failed with the error message "error reque... 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 Bplabel failed with the error message "error requesting media (tpreq) (98) " for a particular tape. Gavin_Tu Level 4 Employee 12-03-2013 07:35 PM Options Mark as netbackup error bplabel New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Netbackup version is Appliance 5220. The customer has a tape A which is stored NBU image previously, but all the images in A had been expired prior to this issue happened. The customer put the tape A in the A pool, and there is only A tape in A pool, then the customer start up the backup to pick up the A tape from A pool, but they saw the error 96 immediately after the backup start up. Change the tape A into B pool, stracth pool also the same result. The available_media command shows the A tape is available status. From GUI, I found out the owner of the A tape is NONE since it's blank tape. bplabel command failed with the below two type errors: 2013-12-2 15:42:57 - Error nbjm (pid=10956) NBU status: 800, EMM status: Media is not in pool error requesting media (tpreq) (98) Error nbjm (pid=10956) NBU status: 2015, EMM status: Media is expired error requesting media (tpreq) (98) It
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 : unable to take the backup in standalone drive usin... VOX : Backup and Recovery : NetBackup : unable to take the backup in standalone drive usin... 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 unable to take the backup in standalone drive using netbackup cynthiapinto Level 4 11-16-2012 02:33 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Trying to take the backup using veritas netbackup tool which is attached with a standalone drive. Though I have inserted the media its thoughing error 96 when I fire the backup. I have labeled the media manually using the GUI. when I gio to label the tape using below command i get the erroe messages bplabel -m A00001 -d hcart -o -p NetBackup -u 0 Error:Error reported by media operation:resource request failed Solved! Go to Solution. Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup Recovering 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! This is your problem: ... Marianne Moderator Partner Trusted Advisor Accredited Certified 11-19-2012 11:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content This is your problem: ... It contains netbackup database backup data & cannot be used for backups This means that this tape was used for cold catalog backups. special steps are needed to reuse cold catalog tapes. Symantec's knowledge base is current offline, so I cannot access the TN's describing the steps. In short, you need to deassign the tape, then relabel it with -o option to force the overwrite. 1. Determine the volume pool number and status. Use: /usr/openv/volmgr/bin/vmquery -m