Tape Job fails after upgrade to latest Veeam Release

[Reimold]

Case # 05291284

Hello,

after we upgraded our VBR environment to the latest release we see our tape job failing on each run with the error message below. The Job uses a single LTO8 drive (connected to a Windows tape server) and worked fine till the upgrade.

The strange thing is that it fails exactly when we put in the 3rd tape media - we have even created a new tape job with different VM´s and that fails at the same point. It is not a matter of some timeout, because it makes no difference if you put in the 3rd media a few hours or a few minutes after the 2nd media is full.

We have opend a support case but so far we did not come to a solution - did anybody see something like this in his own environment?

Thank you

Dirk

Code: Select all

: Error: Das System kann die angegebene Datei nicht finden
Failed to open file [C:\WINDOWS\TEMP\166db67e-395d-4d4b-adc1-9ae006c45bd6] in readonly mode.
--tr:Error code: 0x00000002
--tr:TapeWriter failed to add dataset block and spad, sessionName: Full backup set 21.02.2022 18:01:09, sessionNum: 15, description: Backup set 21.02.2022 18:01:09 description, username: XXXXXXX\XXXXX, encryptType: 0, continuation: true
--tr:TapeWriter failed to continue session on new tape.
--tr:Failed to continue tape backu

[HannesK]

Hello,
I just looked at the case and suggest to continue with support. Guessing on errors like that on a forum makes little sense to me.

Best regards,
Hannes

[Reimold]

Hello,

we will indeed continue with support - I was just curious if someone has encountered a problem like this after installing the latest release.

Thank you

Dirk

[Dima P.]

Hello Dirk,

Was that a WORM media or the regular one? Thanks!

[Reimold]

Hello Dima,

we only use regular media.

Thank you

Dirk

[Dima P.]

Understood, thank you Dirk! Please keep working with our support team and let us know how the investigation goes.

[x-f]

We have similar issue.

After update from 9.5 to 11.0.1.1261 P20220302. Unable to backup to tapes previously used in 9.5 on same server.
Tapes cannot be written. Error message: "Tape has wrong MTF format".

Tape is writable after erasing in Veeam, but after the expiration of the tape, or when trying to append tape by next job, it will fail again with same error message "Tape has wrong MTF format."

Code: Select all

29.05.2022 9:01:36 :: Failed to start new tape backup session: Tape has wrong MTF format.
--tr:Tape writer failed to append session.
--tr:Cannot start new tape backup session 'Full backup set 29.05.2022 9:01:36' for tape 'Tape0'.
--tr:Cannot start new tape backup session 'Full backup set 29.05.2022 9:01:36' for tape 'Tape0'.
--tr:Client failed to process the command. Command: [startSessionTape].
--tr:event:3:
  
29.05.2022 9:02:02 :: Tape has wrong MTF format.
--tr:Tape writer failed to append session.
--tr:Cannot start new tape backup session 'Full backup set 29.05.2022 9:01:36' for tape 'Tape0'.
--tr:Cannot start new tape backup session 'Full backup set 29.05.2022 9:01:36' for tape 'Tape0'.
--tr:Client failed to process the command. Command: [startSessionTape].
--tr:event:3:

Tape has wrong MTF format.
--tr:Tape writer failed to append session.
--tr:Cannot start new tape backup session 'Full backup set 29.05.2022 9:01:36' for tape 'T

[HannesK]

Hello x-f,
what is the support case number on that issue?

Best regards,
Hannes

[x-f]

Problem was in different Block size on tape drive in Veeam.

[lionelCH]

Hello,

we will indeed continue with support - I was just curious if someone has encountered a problem like this after installing the latest release.

Thank you

Dirk

Hi,
yes we have same issue :

when launch backup job to tape (VMware) start to copy and immediatly stops with "Tape has wrong MFT format"

W2K22 on Dell R760, Veeam 12 1420P20230718, Tape IBM (Dell) Ultrium HH8 standalone SAS external
Latest Driver and firmware of drive
Replace tape, format tape, change size block 256K to 64K to 256 Still issue

SUPPORT ID 03084611

i open a case this afternoon
Thx

[GianlucaCroci]

Hi,
we're having the same problem since we updated Veeam to version 12 (v.12.0.0.1420 P20230718).
Did support give a solution?

thanks in advance
Regards

[Dima P.]

Hello Gianluca,

Please raise a support case, as other folks reported this issue might be related to incorrect block size value for the tape drive but if you noticed similar behavior right after upgrade this might be related to another issue. Please do not forget to include your support case ID for future reference. Thank you!