I recently upgraded to v9. Since then I receive a mail
[Warning] Insert a tape to continue
'Tape_Daily' job requires a tape to be inserted into 'HP Ultrium 6-SCSI' tape library. See the corresponding job session in Veeam Backup & Replication management console for details.
I made no changes to this tape job. I want to get a mail if there is no tape in the library. But in this case the correct tape is inserted and the job is working fine, but I get this mail everytime.
Have this started to happen, since the v9 upgrade? Did the corresponding job indeed sit and wait for a new tape to be inserted at some point of time? Thanks.
Just to have a full understanding of the problem - as soon as the job starts the said email is sent to you regardless of valid tape being present inside the library and of tape job working properly, right? Thanks.
Then, it's worth contacting support team, as the described situation looks unexpected. We'd also appreciate, if post here the ticket number, once it's opened, so that we can follow the case. Thanks.
While working with support engineers on investigating that, can you tell how many libraries are present inside the problematic media pools? Just one or you've already put Global Media Pool functionality into use adding multiple libraries under one media pool?
I use a single tape drive. I do not use the new global media pool functionality.
What I recognized: If I have a look at the tape drive, it's state is shown as 'Empty'. But in fact there is already a tape in it. This is no new behaviour as it was the same at lower versions. But perhaps it plays a part.
Dima P. wrote:Just to clarify, was this option checked inside the tape job settings under notifications? Thanks.
I use global notification settings to this job, but the option is checked.
v.Eremin wrote:While working with support engineers on investigating that, can you tell how many libraries are present inside the problematic media pools? Just one or you've already put Global Media Pool functionality into use adding multiple libraries under one media pool?
According to the number of posts, there is definitely an issue but we need to get as much troubleshooting information as possible, so once you recognize the said behavior – submit your logs to the support side and post here the case ID. This will let me pass your logs directly to QA team. Thanks!
I have a tape job hanging at "WaitingTape" right after it started.
One LTO6 tape library with one drive and 24 slots. There are 10 tapes in the library. 2 tapes are from the correct Media Pool.Both are expired and therefore could be used.
Restarting job or server has no influence.
The issue has been confirmed and tracked as a bug.
It happens in the following situation. The tape has been exported from a standalone drive, after that, the drive gets inventoried. Then, a new tape is inserted in the drive, but no inventory is performed afterwards.
After that, a tape job is started. Based on the results of the latest inventory backup server decides that there is no tape inserted in the drive. Thus, the corresponding notification is sent.
After a while, the tape job finds the current tape and starts archiving data.
As the result, there is confusion - the tape job is working properly, in the meantime notification regarding insertion of proper medium is still sent.
the issue you described is not suitable for us.
We are using a tape library not a single tape. The tapes were inserted days ago and inventory happened correctly. The tape job started 04:00am and was waiting for a tape until 11:30am. Then I cancelled the job.
This could also be a second (maybe related) issue.
We are also experience what sounds like the same problem as StephanF. We have a library with tapes from three pools. We load tapes that have come back from storage that have expired protection which have historically worked just fine. Since upgrading to Veeam 9 the jobs will not used the "expired" media and the job stalls once any "Free Pool" media is exhausted. This can be remedied by manually marking each expired tape as free or moving the tapes to the free pool. Neither of these are great solutions especially since the expected behavior shouldn't require it.
I have logged a support ticket with Case # 01670149. We can work around it at the moment but keen for a fix.
Replying for subscription, I have the same problem here and am also using a tape library, Oracle sl150 with dual lto-6 drives.
I have a "tape libraries discovery" job that is sitting at 0% since yesterday.
My first tape archive job is running but gave me the no tape error to start. The pool had a collection of expired media sets to choose from.
We are also experience what sounds like the same problem as StephanF. We have a library with tapes from three pools. We load tapes that have come back from storage that have expired protection which have historically worked just fine. Since upgrading to Veeam 9 the jobs will not used the "expired" media and the job stalls once any "Free Pool" media is exhausted. This can be remedied by manually marking each expired tape as free or moving the tapes to the free pool. Neither of these are great solutions especially since the expected behavior shouldn't require it.
I have logged a support ticket with Case # 01670149. We can work around it at the moment but keen for a fix.
Same here! We use a Quantum Superloader3 with 16 slots and LTO5.
Update from Veeam 8 to 9 yesterday afternoon.
Today the daily F2T-job hangs about 30 min in 'Watining for Tape' state. Some Tapes with "expired" state are online. Veeam don't use these tapes!
I've manually changed the tape state with "Mark as free" during the running F2T job. After that Veeam 9 uses the tapes.
To keep you updated regarding the issue with tape libraries:
I just had a remote session with support were they collected debug logs. To me it was confirmed that this is a bug but the root cause is not known yet. The issue will be escalated immediately for analyzing and creating a fix.
Keep opening support cases so support is able to get as much information as possible.
1. Standalone drive users get a faulty email notification. The said issue should be fixed in the upcoming Update 1.
2. Expired tapes are not overwritten automatically by tape job (only tapes expired before the upgrade procedure are affected). This issue will be addressed in a private fix, followed by Update 1. As a temporary solution, mark expired media as free manually or use a custom scripting. In order to request a hotfix, please, contact support team.
