Unable to execute backup job after migration of repository

[Ottrott]

Hi,

the problem I'm facing here: I had to migrate a backup repository to a new backup server & I'm now unable to execute newly created backup jobs. Copying the files didn't to the job, after some research I found the scripts in KB3607 and moved the content of the old repository via a proxy on the new server to it's new location. This worked fine, the script moved all backups to the new backup repo. After migrating the backup repo I installed the Backup for Microsoft 365 on the new server and I'm able to access & use the migrated backups. The UI shows the restore points in the past, I'm able to browse the backups etc. But: I can create new backup jobs with all the settings I need - but when I try to execute this newly created job I get the following error: "Job with the following ID does not exist: <GUID>". This happens with every job I create, the ID changes with the creation of the job. I'm on version 6.0.0.367

Any ideas what's going wrong here?

Christian Kirn

[Mildur]

Hello,
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be
deleted by moderators.

KB3607 doesn't exists for me. I think you meant https://www.veeam.com/kb3067.
The right procedure to migrate your VBO installation to a new server, is covered by KB2649. https://www.veeam.com/kb2649
The entire configuration (Repos, organization, backup jobs, ...) must be recreated on the new server.

Best regards,
Fabian

PS: support can only help if you export and upload logs

[Ottrott]

The case id is Case #05388874

Regarding the migration process: I tried as described in KB2649 - but when trying to open the repo in the new installation I always got a "jet error -514 JET_errBadLog". So I moved the repo as described in KB3067

[Mildur]

Thanks for the case number.
Let's wait for an answer from support.

One question, what was the OS version before and after the migration?

[Ottrott]

It was on a Windows 10 box and is now running on Windows Server 2019

[Mildur]

It could be, that your windows 10 has a higher version of the jet database engine as your windows server 2019.
Migrating the db files to another machines requires to have the same or higher version of this jet engine.

[Ottrott]

That's one thing which also came to my mind. As the configuration was pretty simple we (obviously it was Roland from the support team) decided to reset the whole config. Now it runs like a charm!
********* schnipp *********
We have reset the configuration as it was almost empty.
The issue was that proxy database did not get the updates from the server and the jobs created did not show up in proxy database at all.
After configuration reset - the communication between components was restored and the issue no longer occurred and we were able to successfully run a job.
********* schnapp *********

[Mildur]

Thanks for coming back with the solution.
I'm glad it working again.