Backups failing after implementing SOBR to AWS

[DarkAlman]

Just implemented a SOBR so that we can copy backups to AWS but after the initial jobs the jobs are now all failing

5/2/2022 11:28:07 AM :: Unable to allocate processing resources. Error: Cannot determine extent for storages 43d7xxxx-a0bf-4b0a-90ca-xxxxxxxxxxxxxxxxx, c709xxxx-478d-4ef0-b52d-xxxxxxxxxxxxxxx

Trying to submit a case, but our license is attached to an email address we don't have access to anymore. Transfer request is in, but our backups are busted in the meanwhile

I've restarted our Veeam server + NAS, and rescanned the SOBR repos but no luck.

[chris.childerhose]

The reference for the UIDs is to files that Veeam is looking for on the SOBR for the job and VMs you are backing up. I might suggest running a Full backup to see if that helps to correct the issue as you have already rebooted and scanned the SOBR.

[veremin]

We cannot suggest much without seeing the debugs logs, so do you mind sharing the ticket number? Also, it might be helpful to describe the situation with licensing administrator email address within the support ticket and let the team match the case with the proper contact. Thanks!