Error since last update 12.3.0.310

[ccorvaisier]

Hi,
Since I put the last version of VBR I have this error message:

22/12/2024 22:00:16 :: Building list of objects to process Error: More than one backup was found for the same job (018ecd71-54c5-460c-b0b2-cfce838a11f2):
job name (945951e6-834a-4b17-99eb-1a18a40e12a6)
job name (54d8c9f7-d317-469e-9a53-50670c779756)

I createe a support case but since I am in the community version, I have no response. could you help me?

[Moderator: Case number 07549603]

[david.domask]

Hi Christophe, welcome to the forums, and sorry to hear about the troubles.

By chance, do you see this backup duplicated in the Backups node? (Please click on "Backups" as shown in my screenshot here, not on Backups > Disk or any other sub-node):



If you see duplicates, check what is different between them; likely something like when the backups were created, the number of backups, etc, should help you understand which are the _real_ backups; you'll likely need to compare this to the actual backup files on the repository.

Once you've identified the "wrong" backups, please ctrl+right-click on the backup; this will reveal a hidden option "Remove from Configuration", go ahead and select that and try the jobs again.

If you cannot see them in the UI, please try the following with Powershell: (From the Veeam Console Menu, Menu > Console > Powershell)

$Backup1 = Get-VBRBackup -Id "945951e6-834a-4b17-99eb-1a18a40e12a6"
$Backup2 = Get-VBRBackup -Id "54d8c9f7-d317-469e-9a53-50670c779756"
$Backup1 #Just like this
$Backup2 #just like this

The goal here is to see the same backup information in the Powershell session like I recommended with the console above. Once the "wrong" backup has been identified, you can use Remove-VBRBackup with the -Backup parameter to remove it like you would from console.

For example, if $Backup1 was determined to be the "wrong" backup:

Remove-VBRBackup -Backup $Backup1

[ccorvaisier]

Indeed in Backup>Disk there was a "residue" from an old job.
Impossible to detach or delete without desable the job before.
once the job was desable, I was able to start deleting the "bad" backup.
I will keep you informed in any case.

[ccorvaisier]

It's working!!!

Thank you Very much!!!

the post can be close

[david.domask]

Glad to hear it worked Christophe! Thank you for the follow up.