Hi ​@ykmm007

We can’t see anything useful in the screenshot because the status can lead to literally anything.

Can you please provide some more details about the environment? Maybe it could help to answer the following questions:

• What kind of tapes and libraries are you using (e.g. LTO-7 with 1 or 2 drives)?

• Is it a library or just a single drive?
• When are the backup jobs (not the tape jobs!) scheduled to run and how long do they usually take?
• When are the tape jobs scheduled to run and how long do they usually take?
• Is this a new issue or is it already present for a while?

As from the screenshots I assume that Veeam is “waiting for tape” so it seems like the appropriate tape is not inserted which of course can lead the whole job structure to stop in case you only have 1 drive.

Hope that gives a first hint! Take care!

Lukas

Also if the waiting on tape message is there and you are using pools for tapes it might not have any free or available so you will need to put new blank tapes in.

But as noted we need more details and also what Veeam version are you using.

Sorry for not completed SS, to update this we are using IBM ts4300 series with 2 drives with one logical partition and LTO-8. We scheduled full backup of each vm with once a week and incremental daily 1AM. This issue is new. Thanks.

Veeam version is latest 12.3, Sir.

Hi ​@ykmm007,

Have you checked the tape schedules? “Waiting for tape” indicated that the appropriate tape Veeam is waiting for is not inserted. Are you using GFS pools or default media pools?

Maybe there are simply tapes not inserted?

I would say to test the hardware once the issue is new and assuming you have done no changes on the OS and Veeam.
You can test your library using the LTT from HPE (Library and tape tools) it used to work with non HPE libraries. 

be carrefull with the LTT! some tests are destrutive.