BE Exec 2014SP1 : Database maintenance failure after moving DB to another server

[fmiermont]

Hi,

I'm using BE Exec 2014 SP1 on a Windows Server 2012R2 (originally a BE Exec 2012). After upgrading to 2014, I've decided to move the DB from the local MSSQLExpress to a dedicated SQL Server 2014, using the BEUtility.

By default, the DB's files (dbf and lgf) are located on the Program Files directory. I've moved them to my dedicated drives (E:\Databases). To do that, I had to change registry keys located at HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase.

No problem doing all of that. But now, every night, my BEExec is unable to do DB Maintenance failure. Log is not really helpfull :

-<jobLogBeserver version="1.0">

-<jobSummary>

-<jobServer>

<![CDATA[TREEBEARD]]>

</jobServer>

-<jobName>

<![CDATA[Database Maintenance]]>

</jobName>

-<jobLogFileName>

<![CDATA[C:\Program Files\Symantec\Backup Exec\Data\BEX_TREEBEARD_01854.xml]]>

</jobLogFileName>

-<jobDeviceName>

<![CDATA[BEDB]]>

</jobDeviceName>

</jobSummary>

-<jobDetail>

-<jobDetailInfo>

<![CDATA[Summary of database maintenance activity: Maintenance has failed: 10, Dump database failed]]>

</jobDetailInfo>

</jobDetail>

-<status>

-<timeStart>

<![CDATA[jeudi 23 octobre 2014 04:00:00]]>

</timeStart>

-<timeEnd>

<![CDATA[jeudi 23 octobre 2014 04:00:00]]>

</timeEnd>

-<completeStatus>

<![CDATA[6]]>

</completeStatus>

</status>

</jobLogBeserver>

Any help will be appreciated !

Regards,

[CraigV]

...2 options here:

1. Open up BEutility on the new server and run a BEDB repair. Then check to see if the maintenance runs.

2. run bemig.exe on the new server and see if it makes any changes.

Thanks!

[fmiermont]

Option 1 failed : 

Starting database repair.
Stopping Services
Stopping services for server:BEXECSERVER.
Server:BEXECSERVER, Service:BackupExecJobEngine stopped successfully or was not running.
Server:BEXECSERVER, Service:BackupExecManagementService stopped successfully or was not running.
Server:BEXECSERVER, Service:BackupExecAgentBrowser stopped successfully or was not running.
Server:BEXECSERVER, Service:BackupExecRPCService stopped successfully or was not running.
Server:BEXECSERVER, Service:BackupExecDeviceMediaService stopped successfully or was not running.
Stopping services for server BEXECSERVER completed.
Failed to start the SQL service on:BEXECSERVER.
Starting Services
Database repair for server BEXECSERVER ended with errors.

BEXECSERVER is the server running BAckupExec. When you say "the new server", you mean this server, not the SQL Server right ? Because I did not install anything related to BackupExec on the SQL Server.

Option 2 seems to work :

C:\Program Files\Symantec\Backup Exec>bemig.exe
Executing migration of BEWS data.
SetRange: from=0 to=0
Status Message: Attach debugger
Status Message: DriverConnect:DRIVER=SQL Server;SERVER=SQLSERVER;DATABASE=BEDB;App=BEWS PVLUPGRADE
Status Message: Querying version data
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: AdammUpgradeView::Initialize() = 0
Status Message: JobMigration Internal Registry Key [Software\Symantec\Backup Exec For Windows\Backup Exec\Server\JobMigration Internal]=0
Status Message: Attach debugger
Status Message: DriverConnect:DRIVER=SQL Server;SERVER=SQLSERVER;DATABASE=BEDB;App=BEWS PVLUPGRADE
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: AdammUpgradeView::Initialize() = 0
Status Message: ADAMM upgrade started
Status Message: Querying version data
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: Backup Exec Device & Media Service Database, version 14.100000 is up to date. No changes are required.
Status Message: ADAMM upgrade ended
Status Message: UpgMachineName=BEXECSERVER
Status Message: UpgVirtualName= UpgMachineName=BEXECSERVER
Status Message: UpgSQLInstance=SQLSERVER
Status Message: From Registry UpgMajorVersion=14 UpgMinorVersion=1 UpgBuild=1786

Status Message: Before EstablishConnection m_sSQLInstance= sDatabase=
Status Message: After EstablishConnection m_sSQLInstance=SQLSERVER sDatabase=BEDB
Status Message: EstablishConnection()called within GetDBVersion()
Status Message: Version.BEServer.VerionNumber=14.100000
Status Message: GetBEServerVersions rc=0 EXEVersion=14.1.1786.0 DBVersion=14.1.1000.0
Status Message: IsDBUptoDate rc=1 Database ExeVersion:14.1.1000.0 Database DBVersion:14.1.1000.0 Registry ExeVersion:14.1.1786.0 Registry DBVersion:14.1.1000.0
Status Message: UpgDBVersion is up to date.  Upgrade is not needed
Status Message: UpgDBVersion=14.1.1000.0
Status Message: origial build number 1786
Status Message: Setting for BUILD TO BUILD UPGRADE
Status Message: Start Running Build to Build upgrade script  dbupdate_14_1_b2c3.sql
Status Message: upgradeViaSQLScript m_JobMigInternal=0
Status Message: upgradeViaSQLScript2 using CDBOperation SQLInstance=(null) SQLSc
riptFile=dbupdate_14_1_b2c3.sql
Status Message:

dbutil RunSQLScript: dbupdate_14_1_b2c3.sql SQLServer:SQLSERVER SQLInstance: DatabaseName:BEDB

Status Message: OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BEDB;Data Source=SQLSERVER;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0

Status Message: fixCRC4ScripDetail
Status Message: Before EstablishConnection m_sSQLInstance=SQLSERVER sDatabase=BEDB
Status Message: After EstablishConnection m_sSQLInstance=SQLSERVER sDatabase=BEDB
Status Message: reset database connection ....
Status Message: Job Migration Success
Status Message: Job Migration Success
Status Message: Starting the upgrade of the catalog database
Status Message:
CleanupDBForReIndexing: Cleaning up database for ReIndexing.

Status Message:
Catalog Schema 14.3

Status Message:
CleanupDBForReIndexing: Catalog Schema was already up to date.  Schema upgrade is NOT needed ...
Status Message: Starting the synchronization of the catalog index database
Status Message: The synchronization of the catalog index database is complete
Status Message: The catalog database was upgraded successfully

Total catalog files found: 83
Total catalog files migrated: 83
Total catalog files skipped: 0
Status Message: DriverConnect:DRIVER=SQL Server;SERVER=SQLSERVER;DATABASE=BEDB;App=BEWS PVLUPGRADE
Status Message: Querying version data
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: AdammUpgradeView::Initialize() = 0
Status Message: ADAMM upgrade started
Status Message: Querying version data
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: VersionName   = ADAMM 14.1,  VersionNumber = 14.1000000000
Status Message: Backup Exec Device & Media Service Database, version 14.100000 is up to date. No changes are required.
Status Message: ADAMM upgrade ended

C:\Program Files\Symantec\Backup Exec>BEXEC

Regards,

[fmiermont]

Solution 2 does not solve my problem. I still have error every night.

Regards,

[CraigV]

Mmm...try the extensive repair of the BEDB on the link below:

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

Thanks!

[VJware]

You are possibly facing this issue - www.symantec.com/business/support/index?page=content&id=TECH223777

As a test, is it possible to use an instance named BKUPEXEC on the remote SQL server ?

[pkh]

If all things failed, then you would have to use BEUtility to load a blank copy of the BEDB and start again

[fmiermont]

I cannot do any repair. In the log, I saw :

Starting database repair.
Stopping Services
(...)
Stopping services for server BACKUPEXEC completed.
Failed to start the SQL service on:BACKUPEXEC.
Starting Services
Database repair for server BACKUPEXEC ended with errors.

It's "normal" that it cannot start SQL Service on my server BACKUPEXEC because it does not have SQL Server. It should try to start the service on the remote server dedicated to SQL Server.

I'm trying to add a new instance on the remote SQL Server and see what's going on.

[fmiermont]

Well, I cannot use a named instace BKUPEXEC. When I want to move the DB from the default instance to the named on using BEUtility, it failed :

New Backup Exec Database Location
Failed to start the SQL service on:BACKUPEXEC.
Operation to change location of Backup Exec database to SQL Server instance BACKUPEXEC ended with errors.

It still trying to start the SQL Service on the wrong server...

[VJware]

Using BEUtility, this is expected as mentioned in the KB posted earlier.

You'll have to manually change the instance vie the registry. Would recommend logging a formal support case to do so.

[fmiermont]

I've open a support case, and keep this thread updated !

[Gavin_UK]

Hi fmiermont

I have encountered the same error when moving the location of the BEDB from the C:\ Drive of a remote SQL server to the E:\ of the same remote SQL server. (using SQL Management Studio)

The Database maintenance was working before I moved it, then the 'Maintenance has failed: 10, Dump Database failed' errors started appearing on the home screen of BE2014.

I tried everything you did.. yet was still getting the error.

I finally figured out that it was permissions on the remote SQL server folder that was causing the problem.

I added my backup exec service account to the folder permissions (full control) and reran the job and voila! no more errors.

I hope this helps.

Gavin_UK

- I am not a Symantec employee, just a guy trying to fix things and share the love..

[Gavin_UK]

Hi fmiermont

Check the folder permissions on the Remote SQL server.

Make sure the account you are using for backup exec (the service account) has full permissions on the folder "E:\Databases"

I had the same issue and this fixed it for me.

Hope this helps

Gavin_UK