Unable to build tape backup record

[2hammewr]

Hello !

I setup a backup to tape job which is copying the last Full backup of a VM to a Tape.

I'm encountering the following error at 99% of the job :

21/09/2015 10:02:28 :: Unable to build tape backup record for storage 82c1894a-cd66-493c-a1b8-7e1079fd2ec7

Any ideas what it means ?

Thanks in advance

[Dima P.]

Hey 2hammewr,

Have you opened a support case to investigate this issue? Thanks.

[2hammewr]

Hi !

No I didn't open a case yet. I'll do It and let you know.

Regards.

[Dima P.]

Do not forget to post case ID to this thread for tracking purposes. Thanks!

[dbainum]

I opened a case for the same error message. Tech has gone through the logs and we also had a web-ex session where he looked things over. No luck finding the problem so far. I also tried re-making the job from scratch, just in case it was something odd with just that job (other tape jobs run fine.) The new job also failed with the same error.

Does anyone even know what record it is trying to write? Is it similar to a catalog?

[veremin]

I'd suggest to escalate the ticket to higher tier, then (you can use "Talk to manager" button available on support portal).

As without seeing debug logs as well as your environment, it's impossible to identify the root cause of the issue experienced.

Thanks!

[Parzival]

Hello all,

I have the same issue.

• VMware Backup are succcessfull

• Tape Job failed with Full backup: Unable to build tape backup record for storage [ID]

Veeam Supported answered with:

• Remove VMware Backup of Tape Job

• Active "last chain only" on Tape Job

• Active Full of VMware Backup

• Re-Add VMware Backup to Tape Job

• Same Issue...I open a new case and currently wait for feedback.

Regards,
Parzival

[Gostev]

Folks, seriously - someone needs to finally include a support case ID already

[Parzival]

Hi@all,

Support Case ID: 03471764

Additional steps:

• Rescan Repositorys

• Check the state of data under Home -> Disk -> Right click on your [BackupJobName] -> Properties

• If there are entries with a X -> Right click -> Forget -> All unavailable backups

I must wait for the next runtime of Tape Job and will give you tomorrow a feedback.

Regards,
Parzival

[michaeldoherty]

Same error for me, any update on a possible solution?

[Dima P.]

Parzival,
Thank you for sharing the solution with the community!

michaeldoherty,
According to the instructions above the error was caused by corrupted backup file in the backup chain (tape job was not able to process the backup chain with incomplete restore point). That's said, I still recommend you to open the support case to investigate the root cause. If you do, please share the case ID in this thread. Thank you!

[fernando.ribeira]

Same error here, no solution, case 03472672.

[adnan]

According to the logs there is an issue with the backup chain ID in Veeam database, The safest way to proceed would be starting the source backup job with an active full. Case # 03663826

[moctad_harry]

Had the same issue after swapping the tape drive.

Followed Parzival's advice and its fixed the issue, thanks.

No support #ID as fixed it myself.

[cmiller@hipco.com]

veeam cannot find record in table tapestorages for tape storage id

This occurred after removing and re-adding tape library.

Issue was resolved by cloning tape backup jobs and re-running.

Followed Parzival's advice and its fixed the issue, thanks!!!

Ray Recendez

[jrudacille]

I have run into this issue and the jobs do not seem to be available to restore from on tape. I have followed Parziva's advice but had no entries with a red x that I could forget. Seems little info on this error except for this chain. Thought I would post it up in case someone sees it and has any additional thoughts. I tried to clone the job but no luck. Have not tried a new full job yet. The specific error I am getting is: 5/27/2022 7:18:16 AM :: Unable to build tape backup record for storage d47e5630-8718-416e-abf1-507dd6aae9ed

My Support Case ID is #05455766

[jrudacille]

The fix for me ended up being the steps detailed in this article...starting a new backup chain. This is in reference to case ID #05455766

https://www.veeam.com/kb1885