Use another database name within the installation process or uninstall the mssql server first and remove all old db files. The old db is still running, and with the default db name in the installation wizard, veeam will connect to the old database.
Thanks
Fabian
Install the SQL Studio Management and delete the database that is there. Otherwise you will need to change the name during installation to VeeamBackup1 or something like that.
Database files are usually located here: \Program Files\Microsoft SQL Server\MSSQL.XX\MSSQL\Data\
Database files are usually located here: \Program Files\Microsoft SQL Server\MSSQL.XX\MSSQL\Data\
Yes you can just delete the MDF/LDF files from here if you are not wanting to install additional software.
Basically what others said above, but for me it’s going to depend on what version of SQL is installed on the machines. If it’s an older version (such as pre-2016) and there’s nothing else using SQL deployment, I’d uninstall it, clean up the old DB’s, and then proceed like normal so that it installs SQL Express 2016. IF already on 2016, I’d remove the old DB’s in management studio and delete the DB’s from the filesystem and then create a new database during the installation. Or, the easy button us to just give the database a new name, but that’s going to result in a couple of DB’s on the machine which may no longer be needed, so I’d rather keep things tidy if possible.
Basically what others said above, but for me it’s going to depend on what version of SQL is installed on the machines. If it’s an older version (such as pre-2016) and there’s nothing else using SQL deployment, I’d uninstall it, clean up the old DB’s, and then proceed like normal so that it installs SQL Express 2016. IF already on 2016, I’d remove the old DB’s in management studio and delete the DB’s from the filesystem and then create a new database during the installation. Or, the easy button us to just give the database a new name, but that’s going to result in a couple of DB’s on the machine which may no longer be needed, so I’d rather keep things tidy if possible.
I second that. Leaving the old redundant DBs means spending more time troubleshooting later on.
Hello, first of all thank’s for all your comments and proposals and sorry for my late response … Anyway, as the problem was on a Virtual Machine, I spent some time and executed what’s mentioned in the above. However it seems the situation with these rater old Veeam installation was even worse. Fortunately Veeam is keeping older SW stacks for download, which at this point saved my day. I reinstalled version 9.5 After this was done, I again installed Community Version 11 as an upgrade. The upgrade went through successfully, however the Veeam BR wouldn’t start as of https://www.veeam.com/kb4204 After executing the workaround and a reboot (!!) of the virtual machine, Veeam is now running properly. Thanks again for your help and hints
Hello, first of all thank’s for all your comments and proposals and sorry for my late response … Anyway, as the problem was on a Virtual Machine, I spent some time and executed what’s mentioned in the above. However it seems the situation with these rater old Veeam installation was even worse. Fortunately Veeam is keeping older SW stacks for download, which at this point saved my day. I reinstalled version 9.5 After this was done, I again installed Community Version 11 as an upgrade. The upgrade went through successfully, however the Veeam BR wouldn’t start as of https://www.veeam.com/kb4204 After executing the workaround and a reboot (!!) of the virtual machine, Veeam is no running properly. Thanks again for your help and hints
Great to hear you were able to get it working. 
