Copy Jobs Failed to find Crypto Key

[keith Drayton]

Hi

Brief setup,
Backups run to NAS device, Copy jobs run to USB connected to NAS,

We recently switched from 1 USB to multiple so set up a new repository with rotation enabled and switch the USB disks each day,
All seemed fine once i had the hang of what i was doing,

Each USB holds 2 copies, Each time i connect a USB i manually delete the oldest backup from it (i am doing this on the NAS direct not through Veeam, Is this a mistake?)
As i am rotating the copy job creates a new chain each run as the previous backup is not available to it so i assume i am OK doing the deletions like this?

A copy job started to report 'Failed to find Crypto Key', after a couple times i deleted the job and recreated, all worked well again,

Now a couple days ago all copy jobs have started to report 'Failed to find Crypto Key'

I have not changed anything within Veeam or the user accounts it uses,

The only search result i found similar is about 18 months old and suggested the problem would be fixed with an update older than i am running,

Anyone have any suggestion of what i look at before raising a support request?

Thank You
Keith

[foggy]

Hi Keith, it is better to contact technical support directly. Thanks!

[keith Drayton]

Hi

I went ahead and changed the password used for the encryption as it was a little over due a change and this seems to have cleared the issue,

Thanks

[ian0x0r]

Changing the crypto key worked for me too. Thanks for sharing Keith

Ian

[BackupMonkey]

Hi all.

One of our many backup jobs has now started to fail with the error: Error: Failed to find crypto key '<Key here>'

The only thing I can find is to overwrite up update the password (which I did do) however since we have more than one job using the same details I think this is more job specific.

Anyone had the same?

[HannesK]

Hello,
I merged your question with an older similar thread and recommend to ask support and post the case number here for reference.

Best regards,
Hannes

[BackupMonkey]

Case ID - 03589120 - Resolved.

Requested steps: (Expanded from the original support request)
From the VB&R Console

1 - Home Tab \ Disk - Right click on affected job and select remove from configuration (not delete from disk).
2 - Backup Infrastructure tab \ Backup Repositories - Rescan the Repository that held that data.
3 - Home Tab \ Disk (Imported) Right click on the imported data and enter the encryption password.
4 - Home Tab \ Backup - Edit the backup job, go to the Storage settings and map the backup chain.
5 - Home Tab \ Backup - Restart the backup job.

[lp@albersdruck.de]

Thanks, the solution from BackupMonkey worked for me as well.
I did have the problem with normal backup jobs after moving the stored files to another repository.

[rgmueller]

Those steps for me to resolve the crypto key issue.

[JayFra@19080]

Hello.
I have a B&R Backup Copy Job that has become problematic. The job has several VMs that are offsite'd to a cloud storage.
I am able to do a recovery of a VM without issue but I have a few decommissioned servers that I would like to remove as they have been archived.
When I stop the job and try to delete the VM I get an error "Failed to get crypto key". This doesn't happen in any other job.

I have searched and I am unable to find an answer or way to repair.
Any suggestions?

[HannesK]

Hello,
I merged your question with an older similar thread and recommend to ask support and post the case number here for reference.

Best regards,
Hannes

[ian0x0r]

When you Google an error and stumble across a forum post you have already commented on

This time around I did not want to update the encryption password. I managed to get around this by disabling encryption on the job and marking all VMs in the job to be excluded from the job in the exclude VM's section and run an active full. This effectively backs nothing up but seems to update something on the encryption side of things which then allowed me to delete the VM's from the job without seeing the crypto key error. Once done remove the VM's you want to keep from the exclusion list in the job and re-enable encryption. Just be aware you need to run another active full to enable encryption.

This was for VM's in a Cloud Connect backup repository.

Cheers,

Ian

[kstbell]

@DeanCTS,

I know this is an older thread, but did you end up finding a solution to this issue? I am having the same exact problem with no solution just yet.

[HannesK]

Hello,
and welcome to the forums.
Please respect the
forum rules and post the support case number. Note, that any posts about technical errors not referencing a support case ID will be eventually removed by forum moderators.


Best regards,
Hannes

[kstbell]

Case#06276978

[HannesK]

Hello,
hmm, I'm confused about 06276978. One one hand Veeam support is waiting for answers (two reminders were sent) and there is also a case with your service provider and that case says that everything works.

Best regards,
Hannes