Failed to eject some tapes

Everything about backing up to tape

Re: Failed to eject some tapes

Veeam Logoby dgreer » Tue Feb 28, 2017 8:57 pm

Hello, Folks;

Quick follow-up: I received the following response from Veeam Support, this morning:

This is a new warning that was added in version 9. Unfortunately when mutliple jobs are set to use the same media pool of tapes they can give false warnings as you are getting. Once job completes the use of a tape and another uses it before the previous job ejects it, and the first job will give the warning. We have provided a registry key to disable this warning for customers that have this occur.

Please add the registry key below to your Veeam server to disable the unneeded warnings.

Host: Veeam B&R Server
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Value: DisableEjectWarning
Type: DWORD
Value : 1


This raises an obvious follow-up question (similar to that asked by edvschriesheim and responded to by lyapkost, both on 1/31/17):

Won't adding/altering this registry key also prevent the warning from being issued in the event of a "real" eject failure?

Perhaps my logic is flawed, but I'm inclined to think it preferable (albeit, granted, annoying) to have to look into an occasional false warning, than to receive no warning at all in the event of a "real" eject failure - especially if a "real" eject failure could prevent or otherwise adversely affect successful retrieval of backed up data, down the road.

If I'm missing something, here, please, by all means, let me know.


Thanks,
-DG
dgreer
Novice
 
Posts: 3
Liked: never
Joined: Mon Feb 27, 2017 9:25 pm
Full Name: Don Greer

Re: Failed to eject some tapes

Veeam Logoby lyapkost » Wed Mar 01, 2017 8:19 am

Hi, Don!

What do you mean by 'real eject failure'? Imagine you have 2 tape jobs to the same media pool with 'always continue current media set' option enabled. The first job has 'eject' option enabled, the second doesn't. When the first job finishes, the second one takes the last written tape and continues writing. The tape will not be ejected after the second job finishes. Is it a 'real eject failure', a misconfig or what? In my opinion the real failure is when a tape stucks in drive and in that case you will receive 'red' alerts from the library and tape jobs so this registry key won't prevent you from noticing such hardware failures.

Another example is when 'export' option is enabled as well and exported tapes are periodically moved to another location. In that case I suggest not to disable warnings to be sure that all tapes with the backup are successfully ejected and exported (actually the best practice is to have a separate media pool for such backups).
lyapkost
Veeam Software
 
Posts: 86
Liked: 15 times
Joined: Fri Nov 27, 2015 2:26 pm
Location: Saint Petersburg
Full Name: Konstantin

Re: Failed to eject some tapes

Veeam Logoby dgreer » Mon Mar 06, 2017 5:49 pm

Hi Konstantin,

Thanks for the response, I appreciate it. I think we're on the same page, regarding a "real" failure, and you raised an interesting point, regarding a misconfig. Our scenario is slightly different than the one you described (we have/use only one "Backup to Tape" job), but there are similarities:

We run four "Backup Jobs" (to file) that back up four servers to the Default Backup Repository. The four jobs run sequentially and, then (upon completion of the fourth "Backup Job"), the "Backup to Tape" job runs, backing up the Default Backup Repository to tape. As you mentioned, though, "always continue..." and "eject media..." are selected ("export" is not). This scenario runs daily (Sun-Fri = incremental, Sat = full), and tapes are also changed daily (per media rotation strategy).

Could be I'm missing "the bigger picture" but, due to the sporadic occurrence of this issue on our end, I'm inclined to believe we may be running into either a timing issue between Veeam and the Tape Library (similar to that mentioned by the OP), or else a tape is getting physically stuck (ie. "real" failure). Unfortunately, I'm 2,000 miles away from the unit, so I'm unable to personally observe the unit's behavior or otherwise verify this theory, but I'm working with the device operator to try to determine that.

Regardless, your response and the one I received in my official support case are virtually identical, and you've both answered my question as to whether or not disabling the registry key will prevent a "red alert" in the event of a true hardware failure (that answer being "no."). As for how we're going to proceed from here, while we certainly appreciate having the option to disable the warning, we've decided to leave the registry key "as-is" (warnings enabled). When it comes to backups, especially with being new to Veeam, I'd prefer to err on the side of caution.

Thanks again for your response and assistance, Konstantin!


Kind regards,
-DG


Support case: 02084013
dgreer
Novice
 
Posts: 3
Liked: never
Joined: Mon Feb 27, 2017 9:25 pm
Full Name: Don Greer

[MERGED] Tape job warning: Skipping tape media 0

Veeam Logoby GraPghaST » Tue Apr 11, 2017 8:45 am

Setup is a virtual Veeam B&R 9.5.0.823 on Windows server 2012 R2, with a virtual Veeam Tape Appliance on Server 2012 R2, which in-guest connects to a Dell TL4000 through a SAS-iSCSI bridge. Backups, inventory, library operations all work. I only have a warning after running a tape job, saying:

[04.04.2017 18:53:38] <01> Warning [CTapeMediumUnloader] Skipping tape media <media label> eject because lock failed
[04.04.2017 18:53:38] <01> Warning Failed to eject some tapes

I found the same issue in tape-f29/failed-to-eject-some-tapes-t39528.html , in which a hotfix is put available. SC #01982635. Only I am running an NFR key, so no support ID to create my own support case. Is there another way to obtain the hotfix mentioned?

Thanks!
GraPghaST
Influencer
 
Posts: 13
Liked: 1 time
Joined: Tue Feb 22, 2011 12:32 pm
Full Name: Robbert Erents

Re: Failed to eject some tapes

Veeam Logoby v.Eremin » Tue Apr 11, 2017 9:54 am

Hi, Robbert,

If you don't want to receive these warning, it stands to reason to install Update 1 and implement the mentioned regkey.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13563
Liked: 1007 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Failed to eject some tapes

Veeam Logoby GraPghaST » Tue Apr 11, 2017 12:11 pm

Hi v.Eremin. Thanks for your actions! Though I am not looking for a way to hide the warning, I'd like the tape to get ejected from the drive and stored in a library slot, as the command should do. Now the tape is still in the tape drive, so the command is not executed correctly. Is there a solution for this, too?
GraPghaST
Influencer
 
Posts: 13
Liked: 1 time
Joined: Tue Feb 22, 2011 12:32 pm
Full Name: Robbert Erents

Re: Failed to eject some tapes

Veeam Logoby v.Eremin » Tue Apr 11, 2017 1:53 pm

Ah, so you're not talking about false positive warnings, but rather about red errors generated due to tape media being stuck in tape library.

Kindly, reach our support team for further investigation. According to our support policy, people with NFS license are eligible for support.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13563
Liked: 1007 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Previous

Return to Tape



Who is online

Users browsing this forum: No registered users and 13 guests