Issues creating backup repo from migrated data - #04996549

[g3n3x32]

Hi all,

I have created a support ticket for this, #04996549, looking for some more input.

I have followed the KB and migrated data from old machine (Win 10 Pro) to a server (Win Server 2019). The VBO365 version is the same. The folder structure is Veeam -> Folders 2006 through to 2021. The first time I went to add a backup repo I pointed it to that Veeam folder, and on the Object storage backup repository page I click next and it tries to validate. The first time I did this it came up with JetError -514, referring to a corrupt log file. I found this file with Event Viewer, removed and ran esenutul /p on the affected database.

After that completed I went to add the repo again, and at the same point it came up again with JetError -528, JET_errMissingLogFile, Current log file missing. When I checked Event Viewer, it was looking for a log file that wasn't in the original data set to begin with. Not sure where I am going wrong here, or how to fix this. Should I delete all the log files in that directory and run the database repair again?

Thanks

[Polina]

Hi Tim,

Most likely, the VBO services on your old server haven't been properly stopped before the database move, which resulted in the errors you see now with reattaching the repository.

Try esentutl /d on the affected databases and then go again to adding the repository.

Thanks!

[g3n3x32]

Hi Polina,

Thanks for your reply. When I try to run that command, I get this error:

"Operation terminated with error -1209 (JET_errInvalidDatabaseVersion, Database engine is incompatible with database) after 5.94 seconds."

I'm wondering if this has to do with ODBC version on the server? As it is different from the Win 10 machine that I am migrating from.

[g3n3x32]

Are there specific ODBC drivers that need to match? I see that they are different version on the old computer vs the server that the data was migrated to. I have tried installing exact same sql version and service packs as the old machine but still received the error above. When I check the Jet version by looking at the msjet*.dll file, they are both msjet40.dll. If that means anything.

Edit to add on - there were some suggestions to run /m on the db to check the OS version, but all this shows is that on the server it has 10.0.14393 vs on the desktop it has 10.0.19043 which accurately reflects different OS versions. Not sure if some compat patch is needed to make it work on different versions?

[Polina]

Hi Tim,

As you could see from the KB, it's one of the prerequisites for migrating the VBO server that the new host should have the same or newer version of the Windows OS.

You should be still able to use your backups if you adjust the new host to this requirement.

[g3n3x32]

Hi Polina,

Okay so migrating from Windows 10 Pro to Windows Server 2019 won't work? Even though they are both on their latest updates?

Thanks!

[Polina]

Hi Tim,

If your current Win 10 Pro version is newer than Win Server 2019 then it may not work.

Thanks!