Error: Unable to continue encrypted backup chain.

[igeronimo]

Hello All,

I moved some Veeam Agent encrypted backups from one repository to another in the same server successfully. The next time the backups ran I got the following Error: Unable to continue encrypted backup chain. Supply password or delete backups, then try again

I searched for the error and could not find anything quickly but it was a simple fix so I thought I would share and maybe someone would find it quicker in the future.

CAUSE:
Encrypted backups were moved using the steps in https://www.veeam.com/kb1729.

SOLUTION:
Imported encrypted backups will end up under Backups > Disk (encrypted). Simply right click on the backup and type the password.
Reference: https://helpcenter.veeam.com/docs/backu ... tml?ver=95

Hope it helps some of you out there.

[Dima P.]

Hello and welcome to the community igeronimo!

Thank you for sharing your issue and the confirmed solution. Thumbs up!

[Technogod]

This will work for VM backups. It doesn't work for VAW backups.

[Dima P.]

Decryption for agent backup files works on VBR console as well. You just need to type in the correct password.

[Technogod]

I was referring to the article igeronimo referenced. https://www.veeam.com/kb1729 The article is for VM backups not VAW backups. You must have VM backups for this to work.

[Dima P.]

Understood, thanks. I was mainly referring to importing VAW encrypted backup file to the VBR, so mentioned Help Center article sounds correct.

KB, indeed, might look confusing: instead of VM backup job user should modify agent job properties.

[TitaniumCoder477]

This tripped me up as well. I made use of the new "Move" feature and just assumed the backups would be decrypted. I did not realize it's effectively a remove and import and needs the manual step of decryption. I am not sure why Veeam requires this when it already has the encryption key stored.

[Dima P.]

Hello James,

Can you please clarify what and where was moved via new move feature? Thank you!

[TitaniumCoder477]

They were for workstations protected by Veeam Agent, i.e. backup sets mapped to a Windows Agent Policy job type for workstation endpoints.