Netbackup Error 306
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 GENERAL ERROR: Status codes 290 and 306 may be encountered when Vault attempts to eject media Article:000032707 Publish: Article URL:http://www.veritas.com/docs/000032707 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 GENERAL ERROR: Status codes 278, 290 or 306 may be encountered when Vault attempts to eject media Error Message Status code: 278 - unable to collect pre eject information from the API robot (278)Status code: 290 - one or more errors detected during consolidated eject processing (290)Status code: 306 - vault duplication partially succeeded (306) Solution Overview:It is possible for vault ejects to fail with status code 278 (unable to collect pre eject information from the API robot) or 290 (one or more errors detected during eject processing) reported. The vault session will then exit with status code 306 (errors encountered, partial success). These status codes could begin to appear for new vault sessions if a previous vault session had to be killed. This could leave lock files that should have been removed when the previous vault session completed.This issue should not be specific to either the operating system or NetBackup version and could appear in other configurations.Troubleshooting:Verify that there is no media that was left in the Media Access Port (MAP) from any previous vault eject. If media resides in the MAP it can cause errors when other vault sessions attempt to eject their media.One way to isolate the issue is to make sure other backup/duplication job can work on the same library and tape drives, but only the eject is not working. Then it is most likely the eject lock file problem.If
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 fail with error 306 VOX : Backup and Recovery : NetBackup : Vault fail with error 306 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 fail https://www.veritas.com/support/en_US/article.000032707 with error 306 Mastana420 Level 5 07-30-2015 01:34 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi We usually have Vault run on mondays, but for some reason i had to run this on wednesday this week. It only copies the full backups which runs on Fridays, so i changed the amount of days it needs to go back in order to get theese https://vox.veritas.com/t5/NetBackup/Vault-fail-with-error-306/td-p/745368 full backups. I added 3 additional days to it. I had around 63 empty tapes in scratch before i started the Vault. Today morning i saw the Vault job, and it had failed with error code 306. I did some research and figured that it failed because there were no media left in scratch. Usually vault does not use more then 20-25 Tapes pr vault session, so wonder why it used all 63 of them still wanting more. Only reason i come up with is that i might have screwed it up when editing amount ofdays it goes back to get hold of all the full backups. It was set to 3 days and 6 hours, so i changed it to 6 days and 6 hours (basically added 3 days). So it might have gotten some full backups even from thursday. We usually run full backups only on fridays, but we might have some full backups running even on thursday. When trying to eject the tapes of this particular Vault session, it only shows 3 Tapes, meaning that it never managed to end the jobs on rest of the 60 tapes. I ran the following command on some of the media ID which i had in scratch prior to start of Vault session:nbemmcmd -listmedia -mediaid
fails to eject tapes, there could be a lock file that was not released. Depending https://netbackup.wordpress.com/2008/03/27/trouble-with-vault-ejects/ on your configuration, the Vault session may error with a http://www.symantec.com/connect/callouts/new-tech-alert-has-been-sent-vault-re-skipped-duplications 290, 297, or 306 error code. Here are some steps to troubleshoot and resolve this issue: Verify no vault sessions are running If none running proceed or wait for jobs to complete Empty the CAP if any tapes are present Rename or netbackup error remove /usr/openv/netbackup/vault/sessions/vlteject.mstr.lock on the Master For ACS robots rename/remove any /usr/openv/volmgr/misc/EJECT_*.txt files on ALL media servers that use this robot Eject tapes for the session(s) by either re-running vault or using vltopmenu to attempt to eject them again It is important to note that if you have an ACS robot, you should netbackup error 306 check all media servers that can control the robot. Like this:Like Loading... Related One Response to "Trouble with Vaultejects" Francois Says: February 11, 2014 at 6:10 am Thank you so much helped me out big time Reply Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Archived Entry Post Date : March 27, 2008 at 4:26 am Category : 5.1 Tags: acs, acsls, eject, hangs, netbackup, symantec, vault, veritas Do More : You can leave a response, or trackback from your own site. Blog at WordPress.com. %d bloggers like this:
for Vault re: skipped duplications: Ian Macdonald 13 Aug 2009 A new tech alert has been sent for Vault re: skipped duplications: Greetings NBUTSPP supporters, A new tech alert has been sent for Vault re: skipped duplications: “A potential for skipped duplications has been discovered in NetBackup 6.5.4 when using Vault, or in NetBackup versions 6.5.1 - 6.5.3 if a specific vltrun binary has been applied. Vault may end with status code 0, 306 or 308 if duplication rules are configured. If a Status 0 occurs due to this issue, duplications are skipped without indication.”This TechNotecan be found at the following locations: http://seer.entsupport.symantec.com/docs/327941.htm This issue affects: NetBackup Server / Enterprise Server 6.5.4, but alsoaffects some vltrun EEB’s from 6.5.1 – 6.5.3 This means that 6.5.1, 6.5.2 and 6.5.3 are affected with vltrun EEBs from ET1461578 (6.5.1), ET1513041 (6.5.2a) and ET1474130 (6.5.3)– Primary ET1461612) Summary of the issue(s) covered in this Alert: If you’re running Vault with 6.5.4 (or 6.5.1– 6.5.3 with an affected binary), using duplication rules will likely lead to skipped duplications. In affected installation, dup rules should not be used without an EEB, fix or workaround (if the workaround is acceptable for the customer). The Error code may be 306, 308, or 0. In the case of Status 0, dups are skipped and the customer doesn’t know, hence the need to send an alert this afternoon. Essentially, problems are triggered if any one (or both) of the following conditions are met: - A duplication rule has 0 batches to do, - There are less number of batches to do than there are write drives configured for that duplication rule,ANDthere are no extra batches to do.(see the TN for more detail) This issue is currently scheduled to be fixed in: NetBackup Server / Enterprise Server 6.5.5 Also, two older 6.5.3 vault technotes have been updated to account for this issue (they are now considered to be fixed in 6.5.5, not 6.5.4.. and should be resolved with either a workaround, 6.5.5, or EEB’s) http://support.veritas.com/docs/314420 http://support.veritas.com/docs/319352 Are there EEB’s available Yes. EEB’s are available for 6.5.4 (under ET1749866). If Emergency Engineering Binaries (EEBs) for vltrun were used for any of the following 3 Etracks, they should be replaced with anupdated EEBimmed