cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade to Backup Exec 2015 cannot use SQL 2014

dsprodukte
Level 3

Hi,

I am using Windows Server 2012 R2 and Backup Exec 2014 with local SQL Express 2014.

Now i want to upgrade to Backup Exec 2015.

  • I downloaded Backup_Exec_15_14.2_FP1_MultiPlatforms_Multilingual.zip
  • Extracted all and started the installation
  • at "SQL Express Setup" - no more chance to switch to own instance

Why?

Was this unsupported: Backup Exec 2014 with local SQL Express 2014?

Will there be support soon?

thx

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Nick_Elmer
Level 6
Employee

Hi dsprodukte,

Based on the install logs you provided above, it looks like your issue is related to the name of your SQL Instance. The Backup Exec Installer lays down a 32 bit SQL 2008 R2 instance as part of our install. The installer logic has no way of knowing if a user installed the instance, or if the installer did, so it always assumes that it did. So, during upgrades, the installer will attempt to upgrade the instance to whatever SQL Express (32bit) version being included in the DVD media. Based on yoru logs above, your SQL Instance is "WIN-22UDJEDVTCL\BKUPEXEC". I would assume this is on your local server where Backup Exec is being installed as well.

Also, the reason that the Backup Exec installer is prompting for the localized SQL Express installation package is because Microsoft will not support multiple language versions of SQL/SQL Express on the same machine. So, the install prompts for a localized SQL installation package that matches the English version carried on the Backup Exec Installation DVD. It appears that the installer believes the version you have installed is older, and since its a "BKUPEXEC" instance, its trying to upgrade it.

The solution is to use an instance name other than "BKUPEXEC". Any other instance name and the installer will not attempt to upgrade or patch it. This is because its a user created instance and therefore, the user is expected to maintain the instance with required windows update, security patches, configuration, etc.

To get your upgrade issue resolved, create a new instance with a name other than "BKUPEXEC". Retarget the Backup Exec application to use that new instance by running the "BEUtility" application we provide to move the database into the new instance (http://www.veritas.com/docs/000095791). That instance needs to be at least the same version as the instance your running now since you cannot move a database down versions. Once you have done that, the install should upgrade with no issue.

We are working to make this configuration more obvious to our customers. In our FP2 installer, we introduced a warning in our environment checker that will indicate that you have a BKUPEXEC instance that is newer or a different installation of SQL than what is expected for that instance. So, if you have a BKUPEXEC instance that is a full version of SQL Server, or a newer version than what the installer is laying down, you should see the warning telling you that your upgrades may fail. Do you see that when you run the new upgrade?

I hope this helps. Let me know if you have any questions.
Nick

View solution in original post

15 REPLIES 15

pkh
Moderator
Moderator
   VIP    Certified
What you are doing is an in-place upgrade of BE which will automatically upgrade your existing BEDB, so there is no need to choose any instance

dsprodukte
Level 3

In the environment Check the SQL check was successfully.

While installation the installer is asking for SQLEXPR_x86.exe. (Normal installations with sql express 2008 r2 dont have this point)

Next points are Data Backup and migration.

I think i can upgrade, but i dont want to go down from working SQL Express 2014 to 2008.

We are now late 2015. Why use old software.

End of life mainstream support sql express 2008 r2 08. July 2014, extended support 09. July 2019 (only security updates)

 

dsprodukte
Level 3

i think i explained it not right

After starting the upgrade of my Backup Exec 2014 with SQL Express 2014 there is a point "SQL Express Setup", here you have to browse to the setup file of sql 2008 r2, without it, installation stops.

with SQL Express 2008 R2 you jump directly to Data Backup and Migration

So I have to downgrade my database to upgrade my Backup Exec.

I am not really interested in using SQL Express 2008 R2. Mainstream Support is end of life.

VJware
Level 6
Employee Accredited Certified

An in-place upgrade does NOT downgrade SQL.

Instead of pointing it to the setup file of SQL 2008 R2, have you tried pointing it to the setup file of existing SQL 2014 ?
 

dsprodukte
Level 3

nice idea, but the installer checks the setup file. It also has to be x86.


 

dsprodukte
Level 3

I started a clean installation in a vm.Now I can use my own local instance of SQL Server 2005/2008/R2/2012/2014.

I will now install Backup Exec 2014 with SQL 2014 x86 and upgrade it to 2015. Maybe my SQL x64 Version is the problem. We ll see.

dsprodukte
Level 3

I installed a new VM with Windows Server 2012 R2.

I took a snapshot.

I installed SQL Server Express 2014 32 Bit.

I installed Backup Exec 2014.

I started Upgrade to Backup Exec 2015.

Installer again needs SQL Server Express 2008 R2.

------------------------------------------------------------------------------------------

Back to Snapshot

I installed SQL Server Express 2008 R2 64 Bit.

I installed Backup Exec 2014.

I started Upgrade to Backup Exec 2015.

All fine

------------------------------------------------------------------------------------------

Back to Snapshot

I started to install Backup Exec 2014

SQL Options - I can choose local SQL 2014 instance

------------------------------------------------------------------------------------------

Back to Snapshot

I started to install Backup Exec 2015

SQL Options - I can choose local SQL 2014 instance

------------------------------------------------------------------------------------------

Conclusion:

Using SQL Express 2014 is supported

Upgrading Backup Exec from 2014 to 2015 is with existing SQL Express 2014 supported, but you have to downgrade SQL Express 2014 to SQL Express 2008 R2

 

 

VJware
Level 6
Employee Accredited Certified

Am not aware of any such known issue.

Would you provide a screenshot where it prompts for the SQL install media ?

Also, pls attach or PM the install logs. Thanks.

Lastly, is BE 2014 patched up with SP2 prior to upgrade ? Also, hope you are using SQL 2014 and not SQL 2014 SP1 with BE 2014. .

dsprodukte
Level 3

Testlab Log:

Symantec Backup Exec (TM) 15 Installation Log
11-03-2015,14:18:09 : Symantec Backup Exec
11-03-2015,14:18:09 : Windows Operating System Version: 6.3 - Server
11-03-2015,14:18:09 : GUI-Shell is installed. Not a CORE OS.
11-03-2015,14:18:11 : Checking MSXML6 Version.
11-03-2015,14:18:11 : Minimum required MSXML6 version is: 6.20.2003.0
11-03-2015,14:18:11 : C:\Windows\system32\msxml6.dll
11-03-2015,14:18:11 : MSXML6 available version is: 6.30.9600.16384
11-03-2015,14:18:11 : Checking Windows Installer Version.
11-03-2015,14:18:11 : Windows Installer Version: 5.0.9600.16384
11-03-2015,14:18:11 : Symantec Backup Exec
11-03-2015,14:18:11 : Executing managed _Setup:
11-03-2015,14:18:11 : D:\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
11-03-2015,14:18:15 : Loading XML from:
11-03-2015,14:18:15 : D:\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
11-03-2015,14:18:15 : RawsDlgSequence::CheckInstMode
11-03-2015,14:18:16 : BEOperations::BE_GetInstalledProdCodeVersion()
11-03-2015,14:18:16 : The product detected. PID: {B9071F7F-1425-4EDD-B1AC-92A839AEAB40}, version: 14.1.1786.
11-03-2015,14:18:16 : RawsDlgSequence::CheckUpgrade
11-03-2015,14:18:16 : Installing Version 14.2.1180; (Major=14, Minor=2, Build=1180) > Target Version 14.1.1786; (Major=14, Minor=1, Build=1786)
11-03-2015,14:18:17 : Folgende Installationsmedienprüfdatei wird verwendet: D:\BE\WINNT\INSTALL\BEx64\Install\Manifest.csm
11-03-2015,14:19:01 : 694 Dateien verarbeitet.
11-03-2015,14:19:01 : Die Installationsmedien wurden geprüft.
11-03-2015,14:19:01 : Processing completed in 0 hours 0 minutes 44 seconds
11-03-2015,14:19:04 : CheckOpenBEUI...
11-03-2015,14:19:04 : BEOperations::BE_GetInstalledProdCodeVersion()
11-03-2015,14:19:04 : The product detected. PID: {B9071F7F-1425-4EDD-B1AC-92A839AEAB40}, version: 14.1.1786.
11-03-2015,14:19:04 : BEOperations::BE_GetInstalledProdCodeVersion()
11-03-2015,14:19:04 : The product detected. PID: , version: .
11-03-2015,14:19:04 : Executing BE_MsiGetPropertyFromSourceMedia
11-03-2015,14:19:04 : D:\BE\WINNT\INSTALL\BEx64\Install\media\Symantec Backup Exec for Windows Servers.msi
11-03-2015,14:19:04 : 0
11-03-2015,14:19:05 : DJM was not found to be enabled. Not a CASO-MMS.
11-03-2015,14:19:05 : SSO key found for upgrade, value: 0
11-03-2015,14:19:05 : AgentSeqDlgs::Misc_BE_CommonOps
11-03-2015,14:19:05 : Current Maintenance Path : C:\ProgramData\Symantec\Backup Exec\{B9071F7F-1425-4EDD-B1AC-92A839AEAB40}
11-03-2015,14:19:05 : Dell Storage Provisioning was not found to be enabled.
11-03-2015,14:19:05 : DLO was not found to be enabled.
11-03-2015,14:19:05 : Backup Exec version 14.1.1786 is registered with the system.
11-03-2015,14:19:05 : Read DotNum Registry Value (Software\Symantec\Backup Exec For Windows\Remote Agent for Windows Servers\Install\DotNum: 0)
11-03-2015,14:19:05 : Writing Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\14.2\Install\Upgrade Version: 14.1.1786.0)
11-03-2015,14:19:05 : Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\14.1\Install\Path: C:\Program Files\Symantec\Backup Exec\)
11-03-2015,14:19:05 : Writing Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\14.2\Install\PreviousDir: C:\Program Files\Symantec\Backup Exec\)
11-03-2015,14:19:05 : Wrote Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\14.2\Install\DLO Upgrade Version: 0)
11-03-2015,14:19:05 : Extracting patch information from D:\BE\WINNT\INSTALL\BEx64\Updates\PatchInfo.ini
11-03-2015,14:19:05 : Set telemetry media value: 1
11-03-2015,14:19:05 : Launching UI Install
11-03-2015,14:19:20 : BeSeqDlgs::DlgBERemoteConfig
11-03-2015,14:19:20 : CopySupportFiles
11-03-2015,14:19:20 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
11-03-2015,14:19:21 : GetClusterUpgradeState returning 0
11-03-2015,14:19:21 : GetClusterUpgradeState returning 0
11-03-2015,14:19:21 : AgentSeqDlgs::Misc_BE_CommonOps
11-03-2015,14:19:21 : BEWS Upgrade
11-03-2015,14:19:24 : Executing BE_SetSQLxLangVersion. Setting language version of SQL Express BKUPEXEC instance.
11-03-2015,14:19:24 : NLS (1031) version of SQL BKUPEXEC instance found on this system.
11-03-2015,14:19:24 : BKUPEXEC SQLx setup file is SQLEXPR_x86_DEU.EXE.
11-03-2015,14:19:24 : GetClusterUpgradeState returning 0
11-03-2015,14:19:24 : GetClusterUpgradeState returning 0
11-03-2015,14:19:24 : GetClusterUpgradeState returning 0
11-03-2015,14:19:24 : GetClusterUpgradeState returning 0
11-03-2015,14:20:04 : Initialize the telemetry items on the dialog
11-03-2015,14:20:04 : AgentSeqDlgs::Misc_BE_CommonOps
11-03-2015,14:20:04 : GetClusterUpgradeState returning 0
11-03-2015,14:20:04 : GetClusterUpgradeState returning 0
11-03-2015,14:20:07 : Telemetry Switch setting : False
11-03-2015,14:20:07 : GetClusterUpgradeState returning 0
11-03-2015,14:20:07 : GetClusterUpgradeState returning 0
11-03-2015,14:20:07 : GetClusterUpgradeState returning 0
11-03-2015,14:20:07 : GetClusterUpgradeState returning 0
11-03-2015,14:20:08 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:08 : WIN-22UDJEDVTCL
11-03-2015,14:20:08 : SQLBrowser service is not running. Starting service.
11-03-2015,14:20:09 : Successfully started service - SQLBrowser
11-03-2015,14:20:09 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:09 : Executing SQL_GetSQLServerEdition.
11-03-2015,14:20:09 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:09 : WIN-22UDJEDVTCL
11-03-2015,14:20:09 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:09 : Connected to SQL Server.
11-03-2015,14:20:09 : Executing SQL_GetServicePack.
11-03-2015,14:20:09 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:09 : WIN-22UDJEDVTCL
11-03-2015,14:20:09 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:09 : Connected to SQL Server.
11-03-2015,14:20:09 : WIN-22UDJEDVTCL\BKUPEXEC is a SQL Server Product Level: 'RTM'
11-03-2015,14:20:10 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:10 : WIN-22UDJEDVTCL
11-03-2015,14:20:10 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:10 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:10 : WIN-22UDJEDVTCL
11-03-2015,14:20:10 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:10 : SQL Server version 12
11-03-2015,14:20:10 : SQL version returned: 12
11-03-2015,14:20:10 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:10 : WIN-22UDJEDVTCL
11-03-2015,14:20:10 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:10 : SQL Server version 0
11-03-2015,14:20:10 : SQL version returned: 0
11-03-2015,14:20:10 : Executing SQL_GetServicePack.
11-03-2015,14:20:10 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:10 : WIN-22UDJEDVTCL
11-03-2015,14:20:10 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:10 : Connected to SQL Server.
11-03-2015,14:20:10 : WIN-22UDJEDVTCL\BKUPEXEC is a SQL Server Product Level: 'RTM'
11-03-2015,14:20:10 : Executing SQL_GetSQLServerEdition.
11-03-2015,14:20:10 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:10 : WIN-22UDJEDVTCL
11-03-2015,14:20:10 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes
11-03-2015,14:20:10 : Connected to SQL Server.
11-03-2015,14:20:10 : WIN-22UDJEDVTCL\BKUPEXEC is a SQL Server Express Edition (64-bit)
11-03-2015,14:20:10 : SQL_GetServiceName. GetComputerName
11-03-2015,14:20:10 : WIN-22UDJEDVTCL
11-03-2015,14:20:10 : DRIVER={SQL Server Native Client 11.0};SERVER=WIN-22UDJEDVTCL\BKUPEXEC;Trusted_Connection=Yes;DATABASE=BEDB
11-03-2015,14:20:14 : AgentSeqDlgs::Misc_BE_CommonOps
11-03-2015,14:20:14 : Executing BE_MsiGetPropertyFromSourceMedia
11-03-2015,14:20:14 : D:\BE\WINNT\INSTALL\BEx64\Install\media\Symantec Backup Exec for Windows Servers.msi
11-03-2015,14:20:14 : 0
11-03-2015,14:20:15 : BEOperations::BE_GetInstalledProdCodeVersion()
11-03-2015,14:20:15 : The product detected. PID: {B9071F7F-1425-4EDD-B1AC-92A839AEAB40}, version: 14.1.1786.
11-03-2015,14:20:15 : Push Install: Not Win2k3 system. So go ahead with net 4.5.2
11-03-2015,14:20:15 : Checking MSXML version
11-03-2015,14:20:15 : Inside IsMSXML6Installed method
11-03-2015,14:20:15 : System Drive is : C:\Windows\system32
11-03-2015,14:20:15 : MSXML Version available is : 6.30.9600.16384
11-03-2015,14:20:15 : Minimum MSXML version required is : 6.20.2003.0
11-03-2015,14:20:15 : MSXML latest version available...
11-03-2015,14:20:15 : In CheckForLUMutex()
11-03-2015,14:20:15 : Value of ProgramFiles(x86) = C:\Program Files (x86)
11-03-2015,14:20:15 : strLuall = C:\Program Files (x86)\Symantec\LiveUpdate\LUALL.exe
11-03-2015,14:20:15 : GetLUMutex_Thread BEPushObj class
11-03-2015,14:20:26 : DlgSLFModern::LoadSerialList
 + 11-03-2015,14:20:31 : Zum Verifizieren der Seriennummern ist eine Internetverbindung erforderlich. Wenn Sie keine haben, importieren Sie die Symantec-Lizenzdateien (.slf) oder installieren Sie eine 60-Tage-Testversion. Ihre Symantec-Lizenzdateien sind eventuell in der E-Mail mit Ihrem Lizenzzertifikat enthalten. Ist dies nicht der Fall, rufen Sie das Symantec Licensing Web-Portal auf und laden Sie Ihre Symantec-Lizenzdateien auf eine Netzwerkfreigabe herunter, auf die dieser Computer zugreifen kann. Weitere Information finden Sie unter: http://entsupport.symantec.com/umi/v-225-287
11-03-2015,14:20:33 : GetClusterUpgradeState returning 0
11-03-2015,14:20:33 : GetClusterUpgradeState returning 0
11-03-2015,14:20:36 : No legacy licenses found.
11-03-2015,14:20:36 : GetClusterUpgradeState returning 0
11-03-2015,14:20:36 : GetClusterUpgradeState returning 0
11-03-2015,14:20:38 : GetClusterUpgradeState returning 0
11-03-2015,14:20:38 : GetClusterUpgradeState returning 0
11-03-2015,14:20:38 : GetClusterUpgradeState returning 0
11-03-2015,14:20:38 : GetClusterUpgradeState returning 0
11-03-2015,14:20:40 : GetClusterUpgradeState returning 0
11-03-2015,14:20:40 : GetClusterUpgradeState returning 0
11-03-2015,14:20:41 : GetClusterUpgradeState returning 0
11-03-2015,14:20:41 : GetClusterUpgradeState returning 0
11-03-2015,14:20:47 : Dem Konto WIN-22UDJEDVTCL\admin werden folgende Rechte gewährt: Dateien und Verzeichnisse sichern Dateien und Verzeichnisse wiederherstellen Überwachungs- und Sicherheitsprotokoll verwalten
11-03-2015,14:20:48 : Currently executing as WIN-22UDJEDVTCL\admin
11-03-2015,14:20:48 : Install is executing as the service account.
11-03-2015,14:20:48 : EUserName value successfully written to the registry.
11-03-2015,14:20:48 : EPassword value successfully written to the registry.
11-03-2015,14:20:48 : EDomain value successfully written to the registry.
11-03-2015,14:20:52 : Check diskspace requiment for BEDB backup
11-03-2015,14:20:53 : BE Database backup space requirement : 59803057
11-03-2015,14:20:53 : Param file C:\ProgramData\Symantec\Backup Exec\{CB639F34-57DC-4413-9762-C4450D5E1262}\BEInstParams.prm is not available.
11-03-2015,14:21:17 : GetClusterUpgradeState returning 0
11-03-2015,14:21:17 : GetClusterUpgradeState returning 0
11-03-2015,14:21:20 : Param file C:\ProgramData\Symantec\Backup Exec\{CB639F34-57DC-4413-9762-C4450D5E1262}\BEInstParams.prm is not available.
11-03-2015,14:21:20 : INFO -2146233087: Unable to determine if Windows Deduplication volume.
11-03-2015,14:21:20 : GetClusterUpgradeState returning 0
11-03-2015,14:21:20 : GetClusterUpgradeState returning 0
 + 11-03-2015,14:21:26 : No SQLx setup path specified.
11-03-2015,14:22:09 : The return code is: 1602
 + 11-03-2015,14:22:09 : WARNING: Installation has been canceled.

VJware
Level 6
Employee Accredited Certified

Upon researching, you are facing this known issue - https://www.veritas.com/support/en_US/article.TECH230621

Download the latest BE 15 installer + FP2 and then run the upgrade.

VJware
Level 6
Employee Accredited Certified

Upon researching, you are facing this known issue - https://www.veritas.com/support/en_US/article.TECH230621

Download the latest BE 15 installer which is embedded with FP2 and then run the upgrade.

dsprodukte
Level 3

Sry, but with FP2 still the same issue - test lab and production ask for SQL 2008

I will stop now, 2014 is working fine - never change a running system :)

Thank You for trying to help me

Nick_Elmer
Level 6
Employee

Hi dsprodukte,

Based on the install logs you provided above, it looks like your issue is related to the name of your SQL Instance. The Backup Exec Installer lays down a 32 bit SQL 2008 R2 instance as part of our install. The installer logic has no way of knowing if a user installed the instance, or if the installer did, so it always assumes that it did. So, during upgrades, the installer will attempt to upgrade the instance to whatever SQL Express (32bit) version being included in the DVD media. Based on yoru logs above, your SQL Instance is "WIN-22UDJEDVTCL\BKUPEXEC". I would assume this is on your local server where Backup Exec is being installed as well.

Also, the reason that the Backup Exec installer is prompting for the localized SQL Express installation package is because Microsoft will not support multiple language versions of SQL/SQL Express on the same machine. So, the install prompts for a localized SQL installation package that matches the English version carried on the Backup Exec Installation DVD. It appears that the installer believes the version you have installed is older, and since its a "BKUPEXEC" instance, its trying to upgrade it.

The solution is to use an instance name other than "BKUPEXEC". Any other instance name and the installer will not attempt to upgrade or patch it. This is because its a user created instance and therefore, the user is expected to maintain the instance with required windows update, security patches, configuration, etc.

To get your upgrade issue resolved, create a new instance with a name other than "BKUPEXEC". Retarget the Backup Exec application to use that new instance by running the "BEUtility" application we provide to move the database into the new instance (http://www.veritas.com/docs/000095791). That instance needs to be at least the same version as the instance your running now since you cannot move a database down versions. Once you have done that, the install should upgrade with no issue.

We are working to make this configuration more obvious to our customers. In our FP2 installer, we introduced a warning in our environment checker that will indicate that you have a BKUPEXEC instance that is newer or a different installation of SQL than what is expected for that instance. So, if you have a BKUPEXEC instance that is a full version of SQL Server, or a newer version than what the installer is laying down, you should see the warning telling you that your upgrades may fail. Do you see that when you run the new upgrade?

I hope this helps. Let me know if you have any questions.
Nick

dsprodukte
Level 3

I was using http://www.symantec.com/business/support/index?page=content&id=TECH87111

for installation SQL.

9. On the "Instance Name" page select Named Instance and type the Backup Exec Instance Name (BKUPEXEC) as shown in figure or use the Default Instance (SQLEXPRESS) and click Next. Refer Figure 9.

I went back to my testlab and started new installation.

Using Default Instance (SQLEXPRESS) for a 2014 installation will not end in my problem. Upgrade to 15 is possible.

Backup Exec Instance Name (BKUPEXEC) cant upgrade. So the instance name matters. 

That doesn't make sense to me. It s only a name. A fresh installation of 15 can use BKUPEXEC SQL 2014 instance.

 

 

Nick_Elmer
Level 6
Employee

Hi dsprodukte,

The technote that you reference above is for users who are installing a SQL Express instance from our install media. Following that technote will create a "BKUPEXEC" instance which is the same architecture and version of SQL that the installer expects. It is designed to assist our customers in getting a compatible "BKUPEXEC" instance name installed when the installer fails attempting to do the same silently. Using a version other than what the technote specifies unfortunately will likely yeild the results you are encountering during upgrades.

The installer should be preventing users from specifying a local or remote "BKUPEXEC" instance during the install with a helpful message. I will take a look at that and see if it is still happening in order to assist you and other users with situations like this in the future.

I did post a blog on this topic many months ago. Hopefully it will prove helpful as well: https://www-secure.symantec.com/connect/blogs/using-custom-sql-instance-backup-exec-installs.

I hope this information helps get you upgraded to Backup Exec 15! We will continue to improve the user experience in order to avoid these pitfalls in the future. Have a great weekend!

Nick