Backup Exec 9 SqlServer - does it need to install MSDE? 1

[ahmack]

I'm trying to install BE 9 on a SQLServer database server. The install program says I can use the existing instance of SQL2K, but the configuration program dies with a "failed to insert" dialog box. Veritas has a technote 254936 that essentially says you must install their MSDE.

Has anyone gotten around this? It seems silly and resource-intensive to put a whole 'nother SQLServer on the machine, just to manage Veritas' internal database.

 

[SQLBill]

INSTALL MSDE!!!!!! I read the documentation that came with BE 9.0 and you can install it in an existing SQL Server install. BUT!!!! If you do, it OVERWRITES the Master database and you CANNOT restore the Master database from the SQL Server disk. YOU MUST USE VERITAS' MASTER database if you need to restore.

-SQLBill

 

[Marverick]

SQLBill,

If you’re referring to the Note from the Backup Exec 9.0 Admin manual.

"When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. to recover the Master database, you must replace it with the Master database copy that Backup Exec automatically crates and updates when the Master database is backed up."

The reference being made to the Master database is NOT the SQL Server master database. It refers to a base or a vanilla database that BE 9.0 creates in addition too the BEDB database when installing with the MSDE instance. This Base or Vanilla database is created in the event your BEDB database and BEDB.bak (backup file), containing all your job, schedule, and history becomes corrupt.

According to Verities, installing BE 9.0 into an existing SQL instance is safe and acceptable; it will not render SQL’s Master Database unusable or unrecoverable.

What is worth noting is, when installing into an existing SQL instance, the Base database is not created during the installation process. So, it is important that you regularly backup the BEDB database and the BEDB.bak file to an alternate location. (tape or disk.

M

 

[SQLBill]

Thank you for the correction. Wish they had made that clearer. I read it several times and so did my coworker, we both came to the same conclusion.


-SQLBIll

 

[ahmack]

I infer, then that you do maintain a separate MSDE instance on the production SQLServer box, and that the MSDE instance is solely for Veritas' use?

The manual does state that Veritas can use an existing SQL2K instance. Unfortunately, Veritas technote 254936 contradicts the manual! The first time wizard ends with an error, and the technote says the way to avoid the error is to use a dedicated MSDE instance.