Keyset not found. Agent failed to process

[zerocoolb]

Hi Guys
I tried following things:
-i did a CLOUD CONNECT Backup to my CC Repo with VAW.
-i did a couple more backups without any CACHING.
-Now i added the CACHING and did couple of backups with CACHING.
-Now i switched of CACHING and did new Backups without Caching.
-Switching back to CACHING....i activated caching again and tried a backup.
-Error: Keyset '271ac92490b6a8a07d2c06fc422c0b53' not found. Agent failed to process method {Signature.LoadFromBackup}.


I tried to use a different folder for the caching but this does trigger the same error.
i also tried to delete the whole folder but nothing changed.

Seems like i can not use the Caching again.

[Dima P.]

Hi Besnik,

Was the target chain somehow modified (deleted/moved) while backing up to cache folder?

[zerocoolb]

no i only did backups without caching
then with caching and after that again without caching.

As for now i tried to enable the caching again....not working.

[Dima P.]

Thanks for the clarification.

EDIT: According to QA this is known issue and it will be fixed in GA. As a temporary workaround for the beta try to change backup destination. This should start a new backup chain from scratch and reset the cache.

[gunaseelan]

Hi R&D and experts.
Case #05700558 — Not able to take physical server backup, Because the Keyset does not exist
We are running VB&R 11.
Scenario Once the backup job trigger, the VEEAM server list the physical server. After listing the server, it shows an error, “ERROR: Keyset doesn’t exist” Investigate In the physical server agent log file, it shows that the VEEAM server try to generate the certificate and it failed.

In our system, we have an internal CA certificate and the VEEAM server was using it to communicate with other components (server or agent).

The issue occurred only when we replaced the VEEAM self-signed certificate with the CA certificate and happened only in the physical server backup job.

Please help me with on the above issues

Advance thanks.!!!!

[Dima P.]

Hello Anbazhagan,

Certificate replacement should not affect the backup jobs, so please keep working with our support team and let us know how the investigation goes!

[mario.orefice]

Hello,
any updated on this? We have exactly the same problem, is the case 05700558 closed?

Thank you
Mario

[Dima P.]

Hello Mario,

Sorry for the delay, I've asked our support for help and they shared that previous case was addressed by recreating Veeam B&R certificate: Using Certificate Signed by Internal CA. Can you please check if that's the root cause and share your feedback with us. Thank you!

[mario.orefice]

Hello,
we found the issue, our server certificate hadn't the "Exchange" flag key type.
Thank you