Did an in place upgrade Veeam ONE V12 to V13 but got an error so reverted (no problem look into that later).
Want to run in parallel ONE V13. So I copied the V12 database to a new database on the SQL Server.
Clean install of ONE V13 on a new server and point via the VeeamOneSettings.exe to the copied new database. It then says: Specified Veeam ONE database version is not compatible
Is there any (other) way to migrate or import the copied database so it converts to the V13 format?
-
- Expert
- Posts: 102
- Liked: 26 times
- Joined: Jan 17, 2022 10:31 am
- Full Name: Da Li
- Contact:
-
- Service Provider
- Posts: 74
- Liked: 23 times
- Joined: Feb 21, 2023 4:44 pm
- Full Name: Timo Marfurt
- Contact:
Re: Copied database V12 to V13 not compatible - how to convert
Hi
There is a database upgrade script in the v13 ISO but I think this is not really a supported way. I suggest involving Veeam support to clarify what the best option is in your case.
Veeam support can tell you if the upgrade failed at the database level or the installation of one or multiple v13 components.
One thing you can check is the "database compatibility level". MSSQL -> Database of VeeamOne -> Properties -> Options, there you find the "Compatibility level".
I had a case that I had to upgrade this at least to SQL Server 2016 (130). After that, the upgrade worked.
My issue was with the reporter service. So if you have similar issues, this is one thing you can try.
Timo
There is a database upgrade script in the v13 ISO but I think this is not really a supported way. I suggest involving Veeam support to clarify what the best option is in your case.
Veeam support can tell you if the upgrade failed at the database level or the installation of one or multiple v13 components.
One thing you can check is the "database compatibility level". MSSQL -> Database of VeeamOne -> Properties -> Options, there you find the "Compatibility level".
I had a case that I had to upgrade this at least to SQL Server 2016 (130). After that, the upgrade worked.
My issue was with the reporter service. So if you have similar issues, this is one thing you can try.
Timo
-
- Expert
- Posts: 102
- Liked: 26 times
- Joined: Jan 17, 2022 10:31 am
- Full Name: Da Li
- Contact:
Re: Copied database V12 to V13 not compatible - how to convert
Thanks, the level is already on 130.
And Reporting Services, hanging and hanging s the reason why I want a fresh new install.
Will contact Veeam Support.
And Reporting Services, hanging and hanging s the reason why I want a fresh new install.
Will contact Veeam Support.
-
- Veeam Software
- Posts: 1676
- Liked: 737 times
- Joined: Jul 17, 2015 6:54 pm
- Full Name: Jorge de la Cruz
- Contact:
Re: Copied database V12 to V13 not compatible - how to convert
Hello Da Li,
As Timo mentioned, this seems very technical and our engineers might be able to help, please share the support ticket number so we can keep an eye on what happened during the upgrade, as upgrade from any v12 version is supported.
Thank you!
As Timo mentioned, this seems very technical and our engineers might be able to help, please share the support ticket number so we can keep an eye on what happened during the upgrade, as upgrade from any v12 version is supported.
Thank you!
Jorge de la Cruz
Director Observability & AI Product Management | Veeam ONE @ Veeam Software
@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2025 / InfluxAce / Grafana Champion
Director Observability & AI Product Management | Veeam ONE @ Veeam Software
@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2025 / InfluxAce / Grafana Champion
Who is online
Users browsing this forum: No registered users and 11 guests