Move Veeam Backup for Microsoft 365 to another OS/VM (fresh install, same remote db)?

[t7MevELx0]

Hi,

What’s the recommended process for reinstalling Veeam Backup for Microsoft 365 on a new OS or VM? We’re considering this as a troubleshooting step to rule out any underlying OS issues, assuming it’s safe to do so.

Here’s what I’m thinking:

Build a new VM using the same hostname and IP address

Install Veeam Backup for Microsoft 365 and point it to the existing PostgreSQL database and NATS server (both hosted on a separate Ubuntu 24.04 LTS VM)

Delete the NATS streams folder before starting the services

I know Veeam support often suggests uninstalling and reinstalling the software since there’s no repair option. I wanted to check if you’ve had success moving the installation to a fresh Windows environment like this.

Thanks!

[t7MevELx0]

Is Veeam Backup for Microsoft 365 tied to a local certificate for decrypting stored secrets?

I installed VB365 on a new Windows Server 2022 VM and pointed it to the existing PostgreSQL database. The service will not start, and Veeam.Archiver.Service.log shows:

Code: Select all

Database initialization was started
Warning: Failed to decrypt data
Warning: The system cannot find the path specified
Error: LogFailedServiceInitialize
Error: Failed to decrypt data
Type: System.Exception

Veeam Support previously told me this move-and-reconnect process would work without extra steps, but the error suggests the new server cannot decrypt something in the database.

We are an MSP and cannot re-enter every client credential. How can I bring the service up on the new host with all secrets intact?

Thanks!

[Mildur]

Hello t7MevELx0

The migration workflow you are trying is not supported. By this time, workflow documented in our KB2649 must be followed:
https://www.veeam.com/kb2649

We are aware that configuration backup and restore is a highly requested feature, and its on our roadmap. But no ETA we can provide today.

All of our products encrypt credential/encryption keys in the database with a private key specific to the source backup server (encrypted using the Microsoft Data Protection API mechanism). As a result, no other machine can decrypt the data simply by connecting to the existing database.

Veeam Support previously told me this move-and-reconnect process would work without extra steps, but the error suggests the new server cannot decrypt something in the database.

May I ask for the case number?

Best,
Fabian