V11 and Rotated Backup Copy Error Email

[dchappell]

In Veeam B&R 10 I had a backup copy job set to go to rotated media. I'd also set the registry key ForceDeleteBackupFiles to be 3 so when the drives are switched the old backups are deleted.

In V10 I would get an email that showed success at the beginning of the scheduled backup that basically told me the it had detected the drives were rotated. Now since upgrading to V11 the email shows as Failed/Error and has the message: "Failed to pre-process the job Error: Rotated drive was changed, restarting backup copy jobUsing the following volume for rotated drives: D:\".

The backups are still working as expected. The rotated disk is being emptied and the new backup is being created on the disk the only thing different between V10 and V11 seems to be the email now is marked as Failed/Error instead of Success. Is this to be expected? Are there new settings for this type of backup in V11?

If this is the new expected behavior is it possible to change something so Veeam doesn't consider this a fail as it is doing what I want it to do. It's nice to be able to wake up and just skim the subjects of my emails and see all of them say [Success].

Thank you,

[Dima P.]

Hello David,

The described behavior looks strange. Can you please raise a support case and share the case ID with us? Thank you in advance!

[dchappell]

Support Case raised: 04675078

[Dima P.]

Thank you for the case, checking with QA team.

[Dima P.]

Hello David,

We've confirmed this issue in our lab and noted a bug report. Cheers!

[SvenLothar]

Hi,

I have exactly the same behavior after upgrading to V11.
Is there a solution in the meantime?

Thank you.

[PetrM]

Hi Sven,

I've had a quick look at the history of the support case 04675078 and there is no solution yet, the issue should be fixed in future releases.

Thanks!

[-Angel-]

Hi,

Same version, same issue.

Regards,

[prisma]

Same here. Need a fix, urgent.
Can't believe this wasn't recognized before released.
Is Veeam now also pandemic bananaware?
Bad for a backup system.

[Gostev]

If you need a fix, you should always open a support case, as hot fixes are prioritized by the number of requests for them.
Although normally, minor/cosmetic issues are not hot fixed, but rather included in the next cumulative patch.

[c.schulzejn]

same here.
We do monitor local eventlog, we do not use email.
(our engineer did open a case already, I am waiting for the case ID to post it here)

@Gostev: we are supporting multiple customers via delegated ProPartner Admin. Do you suggest we do open a case for every customer / contract?

[c.schulzejn]

#02380191

[Kraken]

We have the same issue, but as I see, it's already on the fix list, so no need to raise another ticket for the false-positive alert.

[foggy]

Hi Jaroslav, still good you've posted as this will raise the demand for the fix. Thanks!

[m.novelli]

Same issue with RDX cartridges, thanks for fix
Ciao

[Dima P.]

Thanks for update Marco!

To all new comers: the issue is related only to false-positive email reporting, backup copy job should be restarted successfully. We plan to include the fix to the upcoming update.

[m.novelli]

Thanks, I noticed the issue to be only cosmetic
Cheers

[YouAllHaveZoidberg]

I'd like to add onto this. We're also experiencing the issue, but it's going one step forward. It'll erase previous backup chains on the rotated drive every so often. We're on patch 20210507.

[Dima P.]

Hello Eric,

Any chance you are using registry keys to adjust the rotated drives behavior (backup deletion is not enabled by default)? Thanks!

[YouAllHaveZoidberg]

We aren't. I should've reread the original post before posting my reply. We just rely on retention period for incremental merging.

When we initially went to V11 it wiped all the rotated drives, which was fine since as long as we have a current offsite backup we're good. However, I noticed it started wiping drives that were already wiped preventing restore points from building. We updated to V11 just recently, so I can't pick out a pattern to it.

[Dima P.]

Eric,

That sounds unexpected and not related to the issue described in this post. Can you please raise a support ticket and share the case ID with me - it should be investigate separately. Thanks!

[cjameson@siag.com.au]

Just adding my voice here, (Case 04818351), I'd really like to see this error fixed. Another who doesn't like to see "failure" emails when I wake up each morning, for a successful backup copy operation.

Thanks

Chris

[Dima P.]

Chris, will be fixed in upcoming update. Sorry for the false positive!

Eric, the issue you are facing is related to the 'unification' of rotated drive retention logic - now it works the same way across all product. Say we have two USB drives A and B
and job retention is set to 14 restore points, driver A has 7 restore points and B has 8 restore points:

1. You disconnect drive A, connect drive B and backup job kicks in
2. Backup job sees that across all drives you have 15 restore points. It removes the entire chain from drive B and starts new full backup
NOTE: In case drive B was not disconnected by the time backup chain reaches 14 restore points, job will perform transform operation (merge increments into full backup to fulfill the retention)
3. You disconnect drive B, connect drive A and
4. Backup job removes 7 restore points from the drive and starts new full backup to the drive A
5. And so on

Hope that helps!

[wallace342]

I'm having the same issue as well regarding the errant failure email on a backup copy job with rotated drives, although I haven't set the ForceDeleteBackupFiles on my Veeam installation. I updated to v11 the other day and was unhappy to find that something that worked correctly previously and was so commonly used has been broken and hasn't been fixed in multiple patches. I created a support case as well and was told "this is a known bug of v11". Case is #04832294.

[Dima P.]

Hello wallace342,

Can you please clarify your backup copy job retention and drive rotation schema to understand better what's not working now with the mentioned approach? Thank you!

[je1000]

If you need a fix, you should always open a support case, as hot fixes are prioritized by the number of requests for them.
Although normally, minor/cosmetic issues are not hot fixed, but rather included in the next cumulative patch.

I don’t understand why this called cosmetic issue, this creates a false positive failure that needs to be verified daily. Veeam for being a backup company still fails to understand the importance of solid monitoring of backup Jobs in the ransomware age.

[Gostev]

It does not really matter how I (not Veeam) called it because in any case "Veeam" prioritizes all bugs by the number of support cases.

[Dima P.]

je1000,

To be absolutely precise: after red false positive email report you do get another successful job completion email report (same job, same items, same stats).

[je1000]

Dima, it triggers a ticket in our system. meaning we need to connect daily to all servers with version 11 and verify the backup jobs, costing man hours and slowing down our process.

[Charles.yang]

the issue you are facing is related to the 'unification' of rotated drive retention logic - now it works the same way across all product

100% same issue with V11, Case # 04842548.