Unable to detect database action - Upgrading Veeam to v9

[widmerkarl]

Hello everyone,

I'm trying to update Veeam Backup & Replication v8 to v9 at a customer. But it fails at the point where i have to specify the SQL database instance.

Error:
Unable to detect database action

At the first attempt i tried it with the existing database instance. The database of VBR v8 was set up on an existing SQL database instance, there was just created an additional database.

Then i tried to install SQL server 2012 R2 express and created a new database instance with its own database. Then i imported the backup file from the existing database into the new database on the new instance. When i run the setup again, the error persists.

Whats happening there? I'm not the SQL guru, so any help is appreciated.

Thank you very much!

[Vitaliy S.]

Karl, please include a case ID to your post, when creating a topic about technical issues. Thanks!

[widmerkarl]

Hello Vitaliy,

I did not create a support case for this issue yet. I just wanted to find out if any person here in the forums had the same issue and if it has been solved. I did not find a related thread or post to this problem.

But if its necessary i'll open a support case and provide the case number here, no problem.

Thanks.

[foggy]

You seem to be the first to report this, so opening a case is indeed recommended.

Btw, have you tried just to perform a clean install letting the setup to install SQL Express locally and create the database automatically? Then you could import the configuration from your previous version.

[widmerkarl]

Hi foggy,

Thank you. We performed a clean install, letting the setup install the SQL Express locally. We did nothing special, all log entries, job settings etc. were migrated without any action from our side (DB exports / imports or so).

So the problem is solved. But i'm wondering what produces this error message.

Should I now still a Support Case open, although the problem is solved?

[PTide]

Yes, please open a case with support so they can gather all required information that can be used to improve future versions.

Thank you.

[widmerkarl]

Hello,

I've created a support case for this issue:

Case # 01676621

[slider182]

Hello,

I recently had the same error message when trying to upgrade to v9.
In my case it was that the admin account with which the setup has been invoked had a roaming user profile.
Switching to a local user profile just for the upgrade solved the problem.
(Maybe something with folder redirection)

Best Regards,
Manfred

[jim.montgomery]

# 01784615

Trying simple upgrade from Veeam 8 to 9. Have done this for several clients and this time it failed with the vague unable to detect database action

[Craigb]

I'm on the forums to find an answer for the same, or at least a closely related issue so I'll drop this here for now.
* This page >> https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=95 << has the checklist but it doesn't mention the sql database version as being a prerequisite.
* my upgrade is from 9.0_u2 to 9.5.0.823.Update1
* my error is >> SQL Server version TAPESVR\VEEAM is not supported: SQL Server 2008 (10.0.0.1600.22) or later is required. <<
* same as KawiMTF (the op), I'm not an expert in sql local instances so I'm currently hunting around for an upgrade proc from whatever I have to this unlisted pre-requisite.

[Craigb]

-- best ignore that, I found the ref to sql2008 in the minimum specs area and it turns out I have 2005. This is not a veeam problem I guess.

[Craigb]

If it helps anyone else who isn't sure how to proceed, this is one way that worked.

It starts when you get the error "SQL Server version Your-Server\VEEAM is not supported: SQL Server 2008 (10.0.0.1600.22) or later is required"

* Make an encrypted backup from the Veeam menu that includes creds for jobs.
(my jobs have various credentials, I'd say that's normal for most of us.)
- use top-left-hamburger -> configuration backup -> select the encrypted option.

highest sqlexpress that can run on 2008R2 is SQL-EXPRESS-2014, download and extract it.
theoretically it'll run and upgrade existing instances, but whines and exits so no.
uninstall sqlexpress 2005 ( 1 item, Veeam's database)
uninstall sql2008 (many items including VIM databases from 5.0, 5.5, and 6.0)
no more sql applications
no more sql instances.
uninstall VMware client - (I'll put it back later though)

.. Now install sql-express-2014
the name it asked for is the instance name so call it VEEAM
.. this creates an empty database with the same instance name that B&R is going to look for.
.. Fire up Veeam (inc starting stopped services) and use top-left-hamburger -> configuration backup -> restore
.. I chose 'restore because I migrated' however when that was nearly done the Veeam installer slapped me on the wrist and did the 'recover failed server' parts as well.

Everything is fine, all my jobs etc. are still there and Veeam B&R is now running on an sql-express-14 database.
- caveat.. all my normal jobs are disabled, so I enable them again.
- It's currently rereading every tape in the library, perhaps I could have taken most of them out first but there's not that many.
- wait for the tape reading operation to finish.
- enable relevant jobs

Checks
test a manually kicked off job ==ok
let a scheduled job run and ensure it kicks off ==ok
browse VSphere from Veeam to ensure certs/perms are good == ok.
write a tape == ok
now ..
- wait for clear time with no backup tasks.
- make a new spare Veeam database backup (because tonight's backups will change the real data)
- upgrade to 9.5
.... went straight through with no issues.

so.. hope it helps...

[JRBeaver]

I know this is an old thread but I wanted to advise anyone who might get this issue with upgrading to Veeam B&R 10.

In my case folder redirection is being used and the folder location was changed, this change was not reflected in the path for all locations in the registry.

So the fix was to regedit - HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
Change any reference to the old location in any of these keys to the new location of your folder redirection, reboot the Veeam server and then run the upgrade again.

This resolved the error and Veeam upgraded to 10 without issue.