Migrate Veeam One Database from SQL Server 2017 to 2025

Veeam ONE is a monitoring and analytics solution for virtual and data protection environments, providing performance monitoring, reporting, and capacity planning for infrastructures like VMware vSphere and Microsoft Hyper-V. In this article, we shall discuss how to Migrate Veeam One Database from SQL Server 2017 to 2025. Please, see Install Veeam Backup And Replication With Dedicated SQL Server, and Modern Backup Strategy with Veeam and Wasabi: Truly Immutable.
It helps in proactive troubleshooting through intelligent alerts and AI-driven insights, verifies backup restore points, and offers over 150 predefined reports and customizable dashboards for performance, configuration, and compliance. The software is included with the Advanced Edition of the Veeam Data Platform
You should NOT attempt to restore system databases (master, msdb, model) from SQL Server 2017 directly onto SQL Server 2025. Microsoft documents that system databases can only be restored from backups created on the same SQL Server version (so restoring 2017 master to 2025 master is not supported). Instead, script and transfer logins, jobs and other system-level objects. See this link for more information.
The steps discussed in this article can be used to migrate any application from a legacy SQL Server to a new Edition on the same or remote Server.
Also, see How to upgrade PostgreSQL Engine used by VBR, how to enable FIPS mode on Windows Server, and how to change the default user password in PostgreSQL.
Pre‑checks and Planning
Confirm your Veeam ONE version and check its supported SQL versions in the Veeam ONE User Guide; recent versions support SQL Server 2017, 2019, and 2022. Please, keep an eyes on this page for the support of SQL Server 2025.
At the time of writing this guide, the 10th December, 2025. Veeam does not yet support SQL Server 2025. The support is imminent and as such, I have gone ahead to create the steps you would need to migrate to a new server.
This is what this blogpost assumes. If you wish to upgrade SQL Server 2017, 2022 to SQL Server 2025. The following articles will be very useful “How to upgrade Microsoft SQL Server 2019 to 2022“, and “SQL Server 2025 Upgrade Requirements and Compatibility“.
This blog post assumes that your current server does not meet the hardware requirements to install Microsoft SQL Server 2025. So, it is assumed that SQL Server 2025 is installed unto Windows Server 2025. Please, see Install Windows Server 2025 via iDRAC Virtual Media or PXE, or how to perform In-place upgrade of Windows Server 2022 to 2025 when your server meets the requirements.
Identify the Location of the Veeam ONE Database, and the SQL Server name and instance that currently host the Veeam ONE database. Since Veeam ONE is installed, I will open the Veeam ONE Settings Utility to view the current SQL Server settings
C:\Program Files\Common Files\Veeam\Veeam ONE Settings

You can also determine this using the registry key for DatabaseServer and DatabaseName
HKLM\SOFTWARE\Veeam\Veeam ONE
Please, see Guide to Remote Desktop Connection Properties for Secure Access, how to install Trellix MVISON Endpoint, and Configure Active Directory-Based Activation (ADBA) for Windows.
Install SQL Server on Windows Server 2025
You can install SQL Server 2025 before backing up the Veeam ONE database on SQL Server 2017. There is no requirement to back up the database before installing the new SQL Server version.
Installing SQL Server 2025 first can actually be helpful for preparing the target environment and verifying connectivity before the migration. Simply put, there is no order for the installation. Since a new server environment is assumed, I have decided to install SQL Server 2025.

However, make sure you do not restore the backup until you are ready to switch Veeam ONE to the new database server, as restoring the database will overwrite any existing database of the same name on the new SQL Server 2025 instance.
Please, see Fix Error 0x87E10BC6 on a PC running Windows non-core Edition, Protect your Windows Devices with MFA with SystoLOCK, and Protect your Windows Devices with MFA with SystoLOCK.
Backup SQL Server Database Instance
Veeam recommends that if the Veeam ONE database is located in a SQL Instance on the same server as the Veeam ONE software, use the Create Backup button within the Veeam ONE Settings Utility.
Note: For Scenario 1 “Back Up Local Veeam ONE Database”, you can also use the SQL Server Management Studio or SQLCMD. It is only simpler using Veeam ONE Setting Utility.
Scenario 1: Back Up Local Veeam ONE Database
To do this, open the Veeam ONE Settings Utility to view the current SQL Server settings.
C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

Upon clicking on backup, backup will be created and you will be prompted to save the backup in a location of your choice.

Shortly, you will get a message that it has been complete.

Please, see how to install Endpoint Configuration Manager on HyperV VM, and how to migrate Veeam MSSQL Database to a new Microsoft SQL Server.
Scenario 2: Back-Up Remote Veeam ONE Database
If the Veeam ONE database is located in a SQL Instance on a remote SQL Server, a backup must be created using either SQL Server Management Studio or SQLCMD on that remote SQL Server.

Connect to the ServerName\Instance of the server with the DB you want to back up.

Expand the Databases tab to get to the DB you want to back up. Right-click the desired DB > Tasks > Back Up. See this guide on how to create a backup.

Set Backup Type to Full. Specify the database file destination by choosing the Back up to Disk option > Add the destination path to save the database backup.

Navigate to the Backup Options and set Set backup compression to Compress backup to reduce the database file size (the option is not mandatory).

As you can see, the backup failed because “compression is not supported for Express edition”. Therefore, set backup compression method to another type.

As you can see, this time, the backup has succeeded.

Note: You can also use the SQL command line for preparing the VeeamONE Database backup.
Please, seeHow to set up and configure the Key Management System (KMS), and Setup Windows Admin Center Modern Gateway for Single Sign-On
Restore the Veeam ONE database to SQL Server 2025
On the SQL 2025 server, open SSMS and connect to the new instance

In SSMS, right‑click Databases, and then on Restore Database

In the Source section, choose Device, click the … button, and add the .bak file

Select the backup file and click on OK.
Copy the .bak file from the old server to a local folder on the new server, for example C: or different folder. As it is in my case, it is on the same server, so place it in an accessible location.

Backup media selected, click on OK.

Do not be in a rush to click on OK at this time. Else, your Database restoration will fail.

Navigate to files and check the button to relocate all file to folders and click on OK

Database has been restored successfully. Click on OK.
The error you are seeing below means that SQL Server Management Studio cannot create or overwrite the database files (MDF and LDF) in the specified location because the SQL Server service account does not have the necessary permissions on that folder or file. This often happens if
- The SQL Server service account lacks write access to the target folder “C:\Program Files\Microsoft SQL Server\MSSQL14.VEEAMSQL2017\MSSQL\DATA in case”. Therefore, please ensure, the relocate all files to folder is slected as it is a common mistake (oversight).
- The target folder is locked, marked as read-only, or owned by another user.
- There is an existing file with the same name that cannot be overwritten
Microsoft SQL Server Management Studio
Restore of database 'VeeamONE' failed. (Microsoft.Sq|Server.Management.RelationalEngineTasks)
Additional information:
L.y Microsoft.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)'
while attempting 'RestoreContainer:: ValidateTargetForCreation' on 'C: Program Files Microsoft SQL
Server VMSSQL14. VEEAMSQL2017MSSQL DATA VeeamONE.maf.(Microsoft.Sq|Server.Smo)

Note: On the options windows, we did not do anything as shown below. You can select Overwrite the existing database (WITH REPLACE) only if you are restoring over an existing database of the same name; otherwise leave it unchecked.

Below is the database restored.

After restore, you can optionally set the database compatibility level 160 etc. This can be done in SSMS under Database Properties and click on Options. Veeam recommends a level at least 130

Please, see How to upgrade Veeam Backup and Replication 12.3, and Integrate Active Directory with IPMI for Out-of-Band Management.
Point Veeam ONE to the new SQL Server
Stop Veeam ONE services (Monitor Server, Reporter Server, Business View) on the Veeam ONE server

Launch the Veeam ONE Settings utility. In the left menu, select General, then open the Database tab
C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

Click Test Connection to ensure the settings are correct.

Test connection was successful.

Click on Save

Please, see Migrate Microsoft Enterprise Root Certification Authority and Forest Domain to Azure, and Unveiling OOTBI Mini and New Features for v1.7 from Object First.
Start Veeam One Services
Restart the Veeam ONE Monitor Server and Reporter Server services so they start using the new database

Validate and then decommission old SQL 2017
Log in to Veeam ONE and verify that that the application starts without errors. As you can see below, all services relating to SQL Server 2017 have been stopped.
- Existing configuration, historical data, and reports are present.
- New data is being written and monitoring/alerts function normally

As you can we have our historical data, and reports present via the Veeam ONE Client. Veeam ONE Client is the primary tool used for monitoring the virtual environment, Veeam Backup & Replication and Veeam Backup for Microsoft 365 infrastructures

You can also do this via the Veeam ONE Web Client (Veeam ONE Reporter).

Actually, the Web UI This interface is best for management, auditors, and capacity planners who use web-based reporting.
Veeam ONE Web Client provides a set of dashboards and reports that allow you to verify configuration issues, optimize resource allocation and utilization, track implemented changes, plan capacity growth and track whether mission-critical workloads are properly protected in the virtualized datacenter.

Please, see Uninstall Microsoft SQL Server 2025 from Windows, and how to use Microsoft SQL Server Management Studio to Export and Import your MsSQL database from Azure to local computer.
Uninstall SQL Server 2017
After a few days of successful operation, you can remove or repurpose the old SQL Server 2017 instance, keeping a final copy of the
.bakbackup as an archive.
Since this is my lab environment, and I have confidently testing that the migration succeeded successfully. I will proceed and uninstall SQL Server 2017 (64 bit) from this machine.

Now click on Remove when prompted.

The instance to remove is automatically selected for you. Click on Next to proceed.

Select all features to be removed, and click Next.

On the “Ready to Remove” window, click on Remove

Removal of the SQL Server 2017 instance is in progress

removal succeeded.

As you can see, we only have SQL Server 2025 services available on this server.

I hope you found this guide on “Migrate Veeam One Database from SQL Server 2017 to 2025” very useful. Please, feel free to leave a comment below.