09-19-2010 12:36 PM
Hello.
During upgrade from BackupExec 2010 to 2010 R2 occures some strange error:
09-19-2010,22:57:20 : Действие 22:57:20: RB_RollbackBEDB.
09-19-2010,22:57:21 : Действие 22:57:21: Migrate_BEDB.
09-19-2010,22:57:24 : GetClusterUpgradeState returning 0
09-19-2010,22:57:24 : Kicking off data migration in UPG_InstallMigrate
09-19-2010,22:57:24 : C:\Program Files\Symantec\Backup Exec\
09-19-2010,22:57:24 : BEServer registry key value has been set to current BEServer.exe version 13.0.4164.0
09-19-2010,22:57:24 : GetClusterUpgradeState returning 0
09-19-2010,22:57:24 : C:\Program Files\Symantec\Backup Exec\
09-19-2010,22:57:24 : m_bUseNativeClient = 1
09-19-2010,22:57:24 : Executing Attach_BEDB.
09-19-2010,22:57:24 : DRIVER={SQL Native Client};SERVER=ARIEL;Trusted_Connection=Yes;DATABASE=master
09-19-2010,22:57:25 : Connected to SQL Server.
09-19-2010,22:57:25 : Unsuccessful return code from SQL statement: select filename from master..sysdatabases where name='BEDB'
09-19-2010,22:57:25 : Attaching BEDB to SQL Server.
09-19-2010,22:57:25 : EXEC sp_attach_db 'BEDB',@filename1 = N'S:\mssql\Databases\BEDB_Dat.mdf', @filename2 = N'S:\mssql\Databases\BEDB_Log.ldf'
09-19-2010,22:57:25 : BEDB has been succesfully attached to SQL Server.
09-19-2010,22:57:25 : Change BEDB owner to SA user.
09-19-2010,22:57:25 : Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\Upgrade: 1)
09-19-2010,22:57:25 : Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\Upgrade Version: 13.0.2896.0)
09-19-2010,22:57:25 : m_bUseNativeClient = 1
09-19-2010,22:57:25 : Executing BEDB data migration.
09-19-2010,22:57:25 : C:\Program Files\Symantec\Backup Exec\
09-19-2010,22:57:25 : DRIVER={SQL Native Client};SERVER=ARIEL;Trusted_Connection=Yes;DATABASE=master
09-19-2010,22:57:25 : SQL Server version 9
09-19-2010,22:57:25 : SQL version returned: 9
09-19-2010,22:57:25 : DRIVER={SQL Native Client};SERVER=ARIEL;Trusted_Connection=Yes;DATABASE=master
09-19-2010,22:57:26 : Unable to prep database instances for upgrade.
09-19-2010,22:57:26 : ERROR: User cancelled after unsuccessful migration
09-19-2010,22:57:26 : V-225-134: Error Migrating BEDB ***To search for information about this error, click here
09-19-2010,22:57:26 : Завершение действия 22:57:26: InstallExecute. Возвращенное значение 3.
09-19-2010,22:57:26 : Действие 22:57:26: Rollback. Откат действия:
09-19-2010,22:57:27 : Migrate_BEDB
09-19-2010,22:57:27 : RB_RollbackBEDB
09-19-2010,22:57:29 : Rolling back BEDB files during upgrade rollback in UPG_RollbackBEDB
09-19-2010,22:57:29 : GetClusterUpgradeState returning 0
09-19-2010,22:57:29 : m_bUseNativeClient = 1
after which installation goes rollback and fails. I tied to google some information on "V-225-134", but found nothing.
System config:
Any suggestions?
Solved! Go to Solution.
09-23-2010 01:03 AM
Thanks everyone for replies.
I've launched setup process on clean server installation and found out that it doesn't ask for any custom SQL such as remote SQL server. Previous version (BE 2010) setup program asks for SQL location.
And that`s it. However, this guide worked for our simple installation with no clusters or complicated media services installed, so your experience may and will be slightly different.
More information on migrating can be found here
Finally, some tips you should keep in mind:
09-19-2010 11:37 PM
Hi Mongi,
Have you tried to install the version of SQL that is on the BE 2010 R2 disc first manually, and THEN trying to upgrade the software?
Also, if you have an antivirus active, try disabling that and running the upgrade again.
Laters!
09-20-2010 12:43 AM
Read the compatibility and follow the doc in below KB
http://www.symantec.com/business/support/index?page=content&id=TECH73057
09-23-2010 01:03 AM
Thanks everyone for replies.
I've launched setup process on clean server installation and found out that it doesn't ask for any custom SQL such as remote SQL server. Previous version (BE 2010) setup program asks for SQL location.
And that`s it. However, this guide worked for our simple installation with no clusters or complicated media services installed, so your experience may and will be slightly different.
More information on migrating can be found here
Finally, some tips you should keep in mind: