Veeam 12.1 File (SMB) to Tape Backup

[DHuppertz]

After Upgrading from Veeam v12 to v12.1 we noticed that our file to tape backup took only a short time and copied only 2 folder.
We add "include" mask *.* to each folder and backup was again OK.

Is this a normal behaviour? Did the logic changed between both releases?

Kr
Dieter

[Dima P.]

Hello Dieter,

Logic was not changed and this behavior is not expected, can you please raise a support case and share the case ID with us. Thank you!

[DHuppertz]

Not possible to create a case for the moment: Veeam is having technical issues:

Sorry!
Something went wrong.
We're having technical issues.

Stay calm - our IT team is already solving the problem.

I'll try it tomorrow...

[DHuppertz]

Case #07047939

[Dima P.]

Thank you for the case details and sorry to hear that you had issues while opening a case.

[Dima P.]

Dieter,

The bug has been confirmed by our QA team, the issue will be fixed in the upcoming patch. We've added this bug to the Known Issues post with the workaround proposed in the first post. Thank you so much for sharing!

[Nick Del Duca]

I have this same issue. I am backing files in a local folder on the Veeam server. It's just E:\Backups. I tried to do the inclusion *.* as a files by mask and that didn't seem to work it tried to back up the entire folder.

Do I need to do this? Object by path E:\Backups\*.*

Or this?

Object by path E:\Backups\*

Or do I need to go deeper down and add it like this for each folder inside E:\Backups?

E:\Backups\Daily - Server1\*.*
E:\Backups\Daily - Server2\*.*


Any help is greatly appreciated!

[Dima P.]

Hello Nick,

Should be just include mask with *.* syntax for the E:\Backups source. Are you sure that you got any new files to process in this folder? Thank you!

[Nick Del Duca]

Yes there are definitely new files in the folder. The regular backup jobs run every day or multiple times a day adding new backup files to the folder. The inclusion mask works to actually get files to back up but it seems like it no longer backs up the newest files like it was before it just attempts to back up every file in the folder with the inclusion mask. In my case there are about 300GB of new files added to the folder per day however the entire folder is 44TB. So if I do this workaround it tries to back up the entire 44TB of data to the tape. Previously for years before the update it was only backing up the newest files since the last backup.

[Dima P.]

Hello Nick,

Thank you for the details! We may need to look at debug logs, so can you please raise a support case and share the case id with us?

[Nick Del Duca]

I have a case #07055760, I requested escalation to a senior engineer because so far I have gotten nowhere with support. I have a few logs uploaded. The first are from the job saying it completed but backed up no files before the inclusion workaround. The second set are with the inclusion in place where it tries to back up the whole 44TB in the folder instead of just backing up the latest incrementals. I have to cancel the job because it fills up the tape

[Dima P.]

Hello Nick,

Thank you for the case ID and additional details We've reviewed the issue: after you've added *.* all the data is being processed from scratch resulting in a full backup. QA and support teams are working on a workaround to continue the job incrementally, stay tuned for an update via our support channel. Thank you!

[Nick Del Duca]

Thanks for the update. I figured something like that was happening. It seems as though it runs a full backup every time now regardless of the previous history. I'm currently working with this behavior by using a powershell script I have created to copy all files in my E:/Backup directory that are less than 24 hours old to a E:/VeeamTemp directory before the tape job is scheduled to run. I have now changed the job to backup the E:/VeeamTemp directory instead of the E:/Backup directory. The results of doing this end up being very similar to what the incremental job would have been copying before the bug.

[Dima P.]

Hello Nick!,

It seems as though it runs a full backup every time now regardless of the previous history.

That's exactly the bug QA team has found, the fix will be included in the upcoming cumulative patch! Thank you and Merry Christmas!

[Nick Del Duca]

Thanks for the info! Merry Christmas to you as well. Is there an ETA for the patch?