Behavior of Active Full Backups through PowerShell

[ar952]

We were recently informed about a data corruption within a Bucket provided by Wasabi.
This bucket is used within our VBM365 infrastrcuture.

To avoid any further issues, I initiated an Active Full backup through PowerShell for the affected job which ran fine.
I suspected, that the storage use increases significantly because of that, but this is not the case.
So might VBM365 still reuse some potentially corrupted objects within the bucket?

I cannot find a lot of official documentation on how Active Fulls with VBM365 specifically work (because I never had to use it outside of past support cases until now).

Thank you very much for your thoughts on that topic in advance

[ar952]

In the meantime, I opened a support case.
This is the statement provided by support:

When you run an Active Full via PowerShell (e.g. Start-VBOJob -FullBackup), it doesn’t create an entirely new backup chain from scratch, it causes Veeam 365 to re-collect all the items from Microsoft 365, but it still reuses any unmodified backup objects from the previous backup chain for deduplication purposes, especially when using object storage like Wasabi.

[Mildur]

Hi Ar952,

Apologies for the late response. Our Support engineer is correct; VB365 does not provide support for "Active Full" backups as you know them from Veeam Backup & Replication.
If you want to ensure you have an "Active Full" backup of your data, you need to create a new backup repository and point your backup job to it.

Best,
Fabian