Crypto key was not found when archiving

[MisicV]

Case #05866033

I have two instances on same region/account/S3 bucket (Encrypted)
Policy for one instance is working fine, but policy for second instance is failing with crypto key not found error when archiving. Snapshot and backup is working fine. Those two instances were in one single backup policy but I've separated them when I was having problems with low disk space on worker instance.

So backup works but archiving doesn't work. (same S3 bucket)

My case is closed due to timeout because I use free backup for AWS.

[nielsengelen]

Are these policies identical in their configuration? While this is indeed something that should be helped via support, it would be of use if you could provide the exact message you receive and we may be able to help you on these forums.

[MisicV]

Thank you!
Only thing that is different in configuration is that the instance-2 (instance with problem) has application-aware snapshots enabled. Here is a part of the log:

[09.03.2023 02:33:01.815] <140081633425152> vmbapi | ERR |Could not generate VBM, preparing for DB rollback
[09.03.2023 02:33:01.815] <140081633425152> vmbapi | >> |Crypto key {c6ac9313-dabb-4360-94ba-a26769a87dff} was not found.
[09.03.2023 02:33:01.815] <140081633425152> vmbapi | >> |--tr:Failed to get meta crypto key for storage {df464f6c-c6e0-4613-bdb7-1bb186f657a6}.
[09.03.2023 02:33:01.815] <140081633425152> vmbapi | >> |--tr:Unable to serialize Storage to vbm xml version 2.
[09.03.2023 02:33:01.815] <140081633425152> vmbapi | >> |--tr:Failed to create vbm xml version 2.
[09.03.2023 02:33:01.815] <140081633425152> vmbapi | >> |--tr:Unable to create BackupMeta xml.

So I had a policy (policy_instance_1_2) with instance-1 and instance-2 in it. I was having problems with archiving instance-2, no space left on worker instance. Then I removed instance-2 from that policy and created different policy for instance-2 (policy_instance_2). I was still having problems with worker instance not having enough space. When support helped me to fix that problem, I started receiving Crypto key was not found error, only when archiving instance-2. I have deleted old policy where I left instance-1 (policy_instance_1_2) and created new policy for instance-1 (policy_instance_1). I have changed encryption password for S3 backup and S3 archive. instance-1 is backing up and archiving without problems but instance-2 still throws crypto key error.

[MisicV]

Hello!
This problem was solved with update to new version 6.

[nielsengelen]

Hi Veljko,

Glad to hear the new version solved it!