Upgrade of Backup Exec 10d to Backup Exec 11d or above fails with the error "V-225-118 or V-225-205: ERROR: A unsuccessful 10d to an 11d upgrade may be encountered, if multiple SQL transactions logs exist on the BE/CAS"

Article:TECH49070  |  Created: 2006-01-20  |  Updated: 2012-01-27  |  Article URL http://www.symantec.com/docs/TECH49070
Article Type
Technical Solution

Product(s)

Environment

Languages

Problem



Upgrade of Backup Exec 10d to Backup Exec 11d or above fails with the error "V-225-118 or V-225-205: ERROR: A unsuccessful 10d to an 11d upgrade may be encountered, if multiple SQL transactions logs exist on the BE/CAS"


Error



V-225-118 or V-225-205: ERROR: A unsuccessful 10d to an 11d upgrade may be encountered, if multiple SQL transactions logs exist on the BE/CAS

Upgrade from Backup Exec 10d to 11d above fails with the above error and the installation log will show:
 

09-05-2006,17:46:33 : V-225-205: ERROR: Device activation error. The physical
file name 'D:\VERITAS\Backup Exec\NT\Data\bedb_log1.ldf' may be incorrect. Could
not open new database 'BEDB'. CREATE DATABASE is aborted. sql:EXEC
sp_attach_db 'BEDB',@filename1 = N'D:\Symantec\Backup
Exec\NT\Data\BEDB_Dat.mdf', @filename2 = N'D:\Symantec\Backup
Exec\NT\Data\BEDB_Log.ldf' ***To search for information about this error, click
here
09-05-2006,17:46:33 : V-225-118: Error installing BEDB ***To search for
information about this error, click here
09-05-2006,17:46:33 : Action ended 17:46:33: InstallFinalize. Return value 3.
 
The error will occur in a situation where a Backup Exec(BE)/Central Admin Server Option (CASO) SQL Server Administrator could have created additional transaction logs on the SQL server to improve performance. When a BE/CASO 10d SQL Server is configured to use multiple transaction logs, it will prevent an upgrade to 11d from occurring and fail the installation with the error above.
 

Solution




If this error is encountered during an upgrade to 11d, the BE/CAS SQL Administrator should apply the following corrections to the SQL Server:
1. On the CAS launch SQL Enterprise Manager.
2. Expand the databases node.
3. Locate the BEDB database, right-click and select Properties.
4. Click on the transaction log tab and verify that there are two transaction logs listed.
5. Close the database properties dialog by clicking on Cancel.
6. Right click on the BEDB and select: All Tasks -> Backup Database
7. Select a backup destination and click Ok.
8. After the backup completes repeat steps 3 and 4.
9. Highlight the transaction log titled : bedb_log1.ldf and click the Delete button.
10. Close the database properties dialog and retry the 11d upgrade.
 
 
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see  http://www.symantec.com/
 
 

Supplemental Materials

SourceETrack
Value792419
Description

MSIT Upgrade: Upgrading a 10d database having multiple transaction logs causes upgrade to fail and rollback.

SourceUMI
ValueV-225-205
Description

A unsuccessful 10d to an 11d upgrade may be encountered, if multiple SQL transactions logs exist on the BE/CAS

SourceUMI
ValueV-225-118
Description

Error installing the Backup Exec Database (BEDB)

Related Articles



Legacy ID



285131


Article URL http://www.symantec.com/docs/TECH49070


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support