The given key was not present in the dictionary

[hatchet_harris]

Case 01974579

We are using Veeam 9.0.

We have linux backup proxies and due to disk space I need to move the backup files from proxy to another, and then reconfigure the backup job with the new storage location.
However when I click next after specifying the new location I see:

Exception on import The given key was not present in the dictionary

In the past this has worked fine, I have tried moving different backups to different proxies and the same issue.

Any ideas?

Cheers
Jon

[foggy]

Jon, have you rescanned the new repository prior to re-pointing the backup job to the new location?

[dries.vergote]

I have the same issue.
Copied files to a new repository. When do a rescan of the repository i get the following error:
8/12/2016 14:18:14 Warning Failed to import backup path F:\Backups\Montly\Montly.vbm Details: The given key was not present in the dictionary.
8/12/2016 14:18:16 Warning Failed to import backup path F:\Backups\Weekly\Weekly.vbm Details: The given key was not present in the dictionary.

Do you have solution for this
I have veeam V9 update1.

greetz
Dries

[foggy]

Hi Dries, could be a DB issue or corrupt backup, please contact technical support with this.

[dries.vergote]

Thanks, case created. #01999455

[Ben28]

HI everybody,

I'm currently facing the same issue on my environment after moving several LUN from one server to another one so Dries did you resolve your problem or you were forced to start from scratch your backup Jobs ??

Sorry for my English, I'm french so if there is any mistakes please be indulgent with me

thanks in advance for your reply.

Ben

[foggy]

Hi Ben, Dries was able to resolve this with the help of support, so please contact them directly to get assistance with the issue. Thanks.

[Steve_za]

02150022

Hi All
Recently my backup jobs fail with the following error.
2017-05-08 05:47:04 PM :: Failed to create processing task for VM PFKPMBCEN02 Error: The given key was not present in the dictionary.
Previously it was just the one job, this time it's all of them. If I delete the backup chain and rerun the job it works, but this is not an option.
There is no cause for the failure, the previous days job runs fine, then the next day I'll get this error
Anyone know how to resolve this?

Thanks

[Vitaliy S.]

Usually this messages indicates issues with the configuration database. Our support team should be able to assist you with this issue.

[Steve_za]

Turns out a reboot, suggested by tech support fixed my problem, but it's the second time in 2 weeks it's happened. If it happens again we're going to need to get to the root of the issue.

[dries.vergote]

I'm currently facing the same issue on my environment after moving several LUN from one server to another one so Dries did you resolve your problem or you were forced to start from scratch your backup Jobs ??

Hi, Sorry for late reply on this.
Through support I got the following Solution:

Remove backupjob from configuration:
Disk > remove from configuration

Delete vbm file from backup job. (copy othere location as backup)

Import disk > add backup

On your own risk - change jobname and repository names.
Execute following query: CHANGE backup repository name and job name (imported name)
use VeeamBackup
update [dbo].[Backup.Model.Backups]
set [repository_id]= (select [id]from [dbo].[BackupRepositories]where name = 'Backup Repository 3') where job_name='Montly_imported' and job_id='00000000-0000-0000-0000-000000000000'

Change backup location on the backupjob en map to the imported folder.

Greetz from #veeamon2017

[rajkan01]

I had the same issue when i moved a backup Storage destination.

I fixed it by rescanning previous and new repository of the backup job.

[FReichelt]

Hi All,
I had the same problem from last night to today. The jobs ran for a long time without problems and then all of a sudden:

03/11/2021 08:51:42 :: Error: The specified key was not specified in the dictionary.

For me it brought the solution:
BackupCopy job deactivated -> repository rescan performed and then in BackupCopy job mapped the backup again to the existing one.
Then reactivated the job and the job ran again without errors.

Greetings
Freichelt

[veremin]

Does not look expected. So, I would raise a ticket, should the issue pop up again.