cancel
Showing results for 
Search instead for 
Did you mean: 

BE2010R3 to 2012 upgrade - an older version of sql server has been detected

abeNdorg
Level 2

I have a windows 2003 (fully patched) server with BE2010R3 (fully patched) that I am now trying to upgrade to BE2012. When I run the prereq test it says "An older version of SQL server has been detected on this machine. The older version may not be selected to use with Backup Exec. Instead, choose to install a new SQL Express instance or choose an existing SQL Server 2005 (SP3 or later) or SQL server 2008 instance during the installation.

I checked & there are 3 sql instances on this server, 2 are showing 9.00.5000 which is sql express 2005 sp4 (the service for the 3rd has been disabled). I did go into sql server management studio express 2005 and verify that the database version for each was 2005 as well. The BEDB was 2000, so I stopped all BE service, updated it to 2005, and rebooted the server. I checked after the reboot & it shows 2005.

I would really like to use this current sqlexpress2005sp4 database.

 

Thanks!

3 REPLIES 3

pkh
Moderator
Moderator
   VIP    Certified

You can choose to install a new instance of SQL 2005 Express and let BE manage it.

As a precaution, go to the BE installation directory directory and use BEUtility to take a backup of the BEDB. 

Sym-cr
Level 5

The error you are getting is quite irrespective of the BE version.

You can follow the solution provided in the article below:

Upgrade from older version of Backup Exec to 2010 R2 shows warning in environmental check: "An older version of SQL Server has been detected on this machine."

http://www.symantec.com/docs/TECH154180

 

NOTE: Please install the new SQL INSTANCE manually from the new BE 2012 download package as BE 2012 support SQL Express 2005 SP4 NOT SQL Express 2005 SP3.

How to manually install a named instance of SQLExpress for Backup Exec version 11x or higher.

http://www.symantec.com/docs/TECH87111

Once again, look for the solution irrespective of the versions mentioned in the Tech Articles above.

abeNdorg
Level 2

OK, I am fine with admitting defeat at the hands of the BE2012 installer, that it won't see my current sqlexpress2005sp4 BEDB..... (even though there is no reason it *shouldnt* be able to see it.....)....

Can I use sqlexpress2012 instead of 2005/2008 for the replacement BEDB? I guess the answer is "NO" on sqlexpress2012... shesh, really?! https://www.google.com/url?q=http://www.symantec.com/business/support/resources/sites/BUSINESS/content/live/TECHNICAL_SOLUTION/175000/TECH175581/en_US/be_2012_scl.pdf. I guess sql2008r2 it is then (since I see no point in installing sqlexpress2005 http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=SQL EOL.

update

tried transferring the database

New Backup Exec Database Location
Stopping Services
Stopping services for server:servername.
Server:servername, Service:BackupExecAgentBrowser stopped successfully or was not running.
Server:servername, Service:BackupExecJobEngine stopped successfully or was not running.
Server:servername, Service:BackupExecRPCService stopped successfully or was not running.
Server:servername, Service:BackupExecDeviceMediaService stopped successfully or was not running.
Server:servername, Service:BackupExecAgentAccelerator stopped successfully or was not running.
Stopping services for server servername completed.
Operation to stop services completed.
Stopping SQL service on server: servername : MSSQL$BKUPEXEC
Stopping SQL service on server: servername : MSSQL$SYMBE
Starting SQL service on server: servername : MSSQL$SYMBE
Failed to detach database BEDB from server servername\SYMBE.
Stopping SQL service on server: servername : MSSQL$SYMBE
Starting SQL service on server: servername : MSSQL$BKUPEXEC
Detaching database BEDB from server servername.
Stopping SQL service on server: servername : MSSQL$BKUPEXEC
Starting SQL service on server: servername : MSSQL$SYMBE
Failed to attach database BEDB to server servername.
Operation to change location of Backup Exec database to SQL Server instance servername ended with errors.