Tape job throwing up some crazy numbers

[jboettger]

Morning. So I upgraded to v12 last week and now my tape job is throwing up some crazy numbers both total data read and speed of backups.
In the job window it says it's processed about 2.2pb of data. No more 35tb is on the server to be backed up. Processing rate is 34gb/s.
Job says it is at 99% complete. We have 3 LTO 8 and 1 LTO 9 drives. All was working perfectly on previous version 11.

Not sure what to make of this.

Any help would be appreciated.

[Mildur]

Hello Tim,

That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be deleted by moderators.

Best regards,
Fabian

PS: support can only help if you upload logs https://www.veeam.com/kb1832

[jboettger]

Ok. I guess I have to wait until the job is done to create a support ticket?

Or can I create a ticket while job is still running.

Was thinking you might want to see it in it's backing up state.

Thanks,
Jim

[Mildur]

Hi Jim

You can already open the case to let support check the behavior while the job is running.

Best,
Fabian

[jboettger]

Case #05989363

Thanks,
Jim

[jboettger]

So I opened the case. The engineer asked me to create a new tape job which I did and the numbers are still way crazy!

I have a total 56tb to backup but it's telling me that it's read through 104tb and stuck at 99% complete.

Can someone please help here?
Jim

[Mildur]

Hi Jim

Please keep working with your support engineer.
The forum cannot solve such issues. If it's a bug, it needs to be escalated to RnD. Your support engineer will be able todo that after he could confirm it as a bug.

Best,
Fabian

[jboettger]

That would be great but the SE has gone radio silent for the last few days.

[Mildur]

Have you used already the "Talk to a Manager" button to make Support Management aware of your case?
https://www.veeam.com/kb2320

I'll ask support management if they can take a look at your case.

Best,
Fabian

[david.domask]

Hi @jboettger,

My apologies that there was a delay in the responsiveness on your case; an internal case handling issue resulted in this (which I'm addressing), but there should be an update relatively soon from the Engineer.

I'm working with them on this and have some advice on the direction for the issues.

Appreciate your patience on this.