All Credentials and Backup Encryption Keys Become Invalid if Veeam Backup and Replication Is Manually Migrated to Another Machine

All credentials and backup encryption keys become unusable after manually migrating Veeam Backup and Replication software to a different machine.

The term "manual migration," in this case, refers to the process of installing Veeam Backup & Replication on a new system and directing it to use the configuration database from a prior Veeam Backup & Replication installation on a different machine.

Example: Veeam Backup & Replication was initially deployed on a virtual machine with its configuration database hosted on a remote dedicated SQL server. As the company expanded, it was decided to construct a dedicated physical server for running Veeam Backup & Replication. The original Veeam Backup & Replication server was decommissioned, and the software was then installed on the new physical server. During this installation, the installer was set to connect to the pre-existing configuration database on the remote dedicated SQL server. Although Veeam Backup & Replication successfully completed the installation and preserved job configurations, the credentials stored in the configuration database could not be decrypted and used due to the change in hardware.