Yeah totally understand.
However if all backup chains are accessible now, the encryption password hash should already be in your config DB. If you make sure you create backups of that configuration and encrypt that config backup (this is needed to also backup the encryption passwords).
You should always have a way to decrypt the backups (local or cloud). As the hash is already known.
There is also a way to decrypt the current password in the local DB, Veeam support has a tool for this.
However if all backup chains are accessible now, the encryption password hash should already be in your config DB. If you make sure you create backups of that configuration and encrypt that config backup (this is needed to also backup the encryption passwords).
You should always have a way to decrypt the backups (local or cloud). As the hash is already known.
There is also a way to decrypt the current password in the local DB, Veeam support has a tool for this.
Statistics: Posted by mjr.epicfail — May 21, 2025 3:18 pm
