cancel
Showing results for 
Search instead for 
Did you mean: 

Using SQL 2012 for Backup Exec 2012 database?

ksattler
Level 3
Partner Accredited

Hi,

the SCL for Backup Exec 2012 contain on site 20  SQL Server 2012 for using for the BEDB.

But when I install BE2012 it says this:

The instance is default instance on the same server using SQL 2012 Enterprise Edition. The service account have full sysadmin-sql and domain-admin rights.

 

Anyone tried this before?

What I have to do?

 

Thanks!

11 REPLIES 11

VJware
Level 6
Employee Accredited Certified

Check if this KB applies or not - http://www.symantec.com/business/support/index?page=content&id=TECH45007

(This KB was written for SQL 2000 & 2005, but can apply to SQL 2012 as well)

 

ksattler
Level 3
Partner Accredited

I have already tried this... no way...

 

VJware
Level 6
Employee Accredited Certified

Would you pls post the install log, named bkupinst.htm or bkupinst.log

ksattler
Level 3
Partner Accredited

bkupinst2012.htm:

Symantec Backup Exec (TM) 2012 Installation Log


05-06-2012,15:49:29 : EnumProcesses Counts: 75

05-06-2012,15:49:29 : Windows Operating System Version: 6.1

05-06-2012,15:49:29 : GetProductInfo returned success. Checking for CORE OS values.

05-06-2012,15:49:31 : Executing managed _Setup:

05-06-2012,15:49:31 : C:\install\Backup_Exec_2012_14.0.1798_MultiPlatforms_Multilingual\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe

05-06-2012,15:49:33 : Loading XML from:

05-06-2012,15:49:33 : C:\install\Backup_Exec_2012_14.0.1798_MultiPlatforms_Multilingual\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml

05-06-2012,15:49:35 : RawsDlgSequence::CheckInstMode

05-06-2012,15:49:36 : BEOperations::BE_GetInstalledProdCodeVersion()

05-06-2012,15:49:37 : Folgende Installationsmedienprüfdatei wird verwendet: C:\install\Backup_Exec_2012_14.0.1798_MultiPlatforms_Multilingual\BE\WINNT\INSTALL\BEx64\Install\Manifest.csm

05-06-2012,15:50:32 : 692 Dateien verarbeitet.

05-06-2012,15:50:32 : Die Installationsmedien wurden geprüft.

05-06-2012,15:50:32 : Processing completed in 0 hours 0 minutes 55 seconds

05-06-2012,15:50:33 : BEOperations::BE_GetInstalledProdCodeVersion()

05-06-2012,15:50:34 : Launching UI Install

05-06-2012,15:50:37 : MDAC 6.1.7601.17514 is installed on this system.

05-06-2012,15:50:37 : m_bUseNativeClient = 0

05-06-2012,15:50:37 : MDAC 6.1.7601.17514 is installed on this system.

05-06-2012,15:50:37 : BeSeqDlgs::DlgBERemoteConfig

05-06-2012,15:50:37 : CopySupportFiles

05-06-2012,15:50:38 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary

05-06-2012,15:50:39 : AgentSeqDlgs::Misc_BE_CommonOps

05-06-2012,15:50:40 : Initialize the telemetry items on the dialog

05-06-2012,15:50:40 : AgentSeqDlgs::Misc_BE_CommonOps

05-06-2012,15:50:40 : Executing BE_SetSQLxLangVersion. Setting language version of SQL Express BKUPEXEC instance.

05-06-2012,15:50:40 : NLS (1031) version of SQL instance found on this system.

05-06-2012,15:50:40 : BKUPEXEC SQLx setup file is SQLEXPR_DEU.EXE.

05-06-2012,15:50:49 : Telemetry Switch setting : False

05-06-2012,15:50:50 : Typical install value is set to : False

05-06-2012,15:50:50 : Typical install value is set to : False

05-06-2012,15:50:51 : Typical install value is set to : False

05-06-2012,15:50:52 : SQL_GetServiceName. GetComputerName

05-06-2012,15:50:52 : MGMT01

05-06-2012,15:50:52 : DRIVER={SQL Server};SERVER=MGMT01;Trusted_Connection=Yes

05-06-2012,15:51:01 : AgentSeqDlgs::Misc_BE_CommonOps

05-06-2012,15:51:01 : Checking for .Net Framework 4.0.

05-06-2012,15:51:03 : DlgSLFModern::LoadSerialList

05-06-2012,15:51:31 : Currently executing as DOMAIN\Administrator

05-06-2012,15:51:31 : Install is not executing as the service account.

05-06-2012,15:51:31 : Successfully Logged on as service account.

05-06-2012,15:51:32 : Successfully impersonated service account.

05-06-2012,15:51:32 : EUserName value successfully written to the registry.

05-06-2012,15:51:32 : EPassword value successfully written to the registry.

05-06-2012,15:51:32 : EDomain value successfully written to the registry.

05-06-2012,15:51:37 : Executing SQL_TrySQLConnectAsWindowsUser

05-06-2012,15:51:37 : SQL_GetServiceName. GetComputerName

05-06-2012,15:51:37 : MGMT01

05-06-2012,15:51:37 : DRIVER={SQL Server};SERVER=MGMT01;Trusted_Connection=Yes

05-06-2012,15:51:37 : SQL_GetServiceName. GetComputerName

05-06-2012,15:51:37 : MGMT01

05-06-2012,15:51:37 : DRIVER={SQL Server};SERVER=MGMT01;Trusted_Connection=Yes

05-06-2012,15:51:37 : Connected to SQL Server: MGMT01

05-06-2012,15:51:37 : SQL Server version 0

05-06-2012,15:51:37 : SQL version returned: 0

+ 05-06-2012,15:51:37 : V-225-220: The SQL Server MGMT01 on machine MGMT01 is not SQL 2005 compatible. ***To search for information about this error, click here

+ 05-06-2012,15:51:40 : V-225-27: Der Microsoft SQL Server MGMT01 ist keine gültige SQL-Instanz zum Installieren der Datenbank. ***To search for information about this error, click here

05-06-2012,15:56:02 : The return code is: 1602

+ 05-06-2012,15:56:02 : WARNING: Installation has been canceled.

 

 

 

VJware
Level 6
Employee Accredited Certified

Nothing different in this log except what you already attempted....next thing to check would prolly be the compatibility level set on SQL, however would recommend to raise a ticket with Support just to be sure

ksattler
Level 3
Partner Accredited

Do you know about some other installation using SQL 2012 for BEDB?

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

We do not support SQL 2012 for BEDB location or backup ... yet.

Also I hope you are not choosing to install into SQL 2012 because you were planning on sharing the instance with business applications, as we recommend that the BEDB uses a unique instance that is not shared with other business applications.

 

ksattler
Level 3
Partner Accredited

@Colin

..... then please correct the SCL!

 

To your second question, no it is a standalone server.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

OK I did some checking and SQL 2012 is suppprted (as a BEDB Repository) as long as you have Hotfix 180962 (which in effect means SP1a as this replaces it.)

Apologies - I was unaware of the change as it was not publicised within support at the time of the release.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

I have just been informed that the entry for SQL 2012 is no longer in the Backup Exec SCL as a database repository. As such I have reclarified internallty about the support status of running Backup Exec inside of SQL 2012.

 

Confirmation has come through that it is NOT supported and both the original SCL entry and the advice I was previously given were incorrect. Hence the SCL has been changed to reflect this.

 

We plan to support SQL 2012 as a BEDB repository in the next full release of Backup Exec however we probably won't make it the default version as apparently it must have a 64bit server for that and not all customers use 64 bit servers yet.

Apologies for any confusion this may have caused.

rob_s_p
Not applicable

There will be people out there who took Symantec's original documented & published compatibility statement at face value.

What issues might we get, when we use BackupExec 2012 with a SQL Server 2012 repository?