Backup Exec 9 on MSCS 2-node cluster running SQL2000 Virtual instance

[dmgoulet]

Setup: 2 Dell 2550 servers with tape drive in each participating in a failover cluster running SQL 2000 (SP2) on Win2k Advanced Server (SP2). I have 2 licenses for BE and 2 Remote Access licenses.

Problem: On primary (active) node, install of BE gives error message that it cannot find a running instance of SQL however, there is the virtual server running and can be accessed with SQL Enterprise Manager and visible in the Service Manager. The install of BE creates a new instance (machine name\BKUPEXEC) on each node BE is installed. According to the manual, I should get a window that asks to create a new instance or use an existing one! After install of BE on both nodes, the original SQL instance (in the Service Manager) is unable to show any services...

However, on the primary node, a backup can be done successfully. If I fail the primary node, the Backup Exec Server Service fails to start. If I restore the primary node (keeping the second node active), the BE Server will run.

Anyone got any suggestions?

Thanks
Dennis
SimplexGrinnell

 

[Qdog]

Your post doesn't make sense. What is Service Manager? And how does it now show services for the original SQL instance?

Sounds like you need some licenses installed. You will need a cluster serial # on each machine for BE. Also need Agent for SQL on each. That may resolve the server service not starting on the 2ndary node. It also could be....the 2ndary node has a messed up BE 9.0 install and it cannot find it's own database. Check to see if the MSSQL$BKUPEXEC service on 2nd node is started.
I would go with the MSDE2000 \bkupexec instance that is created by default by the BE installation. You will save yourself a lot of headaches. Say you configure BE to use an existing or additional instance of SQL on the virtual SQL server on the shared disks and the shared disks get hosed....how will BE run? You wouldn't be able to restore squat as the database would not be available and BE services would not start. Bad move.

Good luck!

 

[SQLBill]

BE cannot backup/see SQL Server unless you have the SQL Agent installed.

However, I suggest you DON'T buy SQL Agent. I use BE 8.6 on a two-node cluster and originally used SQL Agent. After MAJOR problems (posted elsewhere in this forum), I quit using SQL Agent. I now use the native SQL Server BACKUP DATABASE command to create a backup file on disk. Then I copy those files to tape using BE.

-SQLBill

 

[dmgoulet]

Okay... Lets see if I can clear this up a bit more!!!

SQL Server Enterprise Edition is installed directly to the cluster (not on each physical server). This creates a single instance (in my case SWCOURTSDB) where the shared files are stored on a SCSI RAID 5 array, and each server gets Enterprise Manager and other necessary files installed on each server.

When I try to install Backup Exec, I get a popup window that states: "SQL Service does not exist or access denied, ConnectionOpen(Connect())" instead of having Backup Exec ask to use a existing instance or create a new one! However, I can continue the install and it creates a new instance.

Jump ahead... now both servers have Backup Exec installed and I join both Backup Exec Media Servers to the cluster using the Wizard in Backup Exec.

Now, on the 1st server (Active node in cluster) I can perform a backup. If I force a failover to the 2nd node (either power down the 1st node, or stop the cluster service), the 2nd node fails to start the Backup Exec Server Service. The Application Log on the 2nd server gives the following Event:

" The Backup Exec Server Service did not start. An internal error (-1610575865) occured in object -1."

If I bring the 1st server online (keeping the 2nd server the Active node in the cluster), I can start the Backup Exec Server Service.

I am not using the SQL Agent for Backup Exec. I am having SQL backup the databases to the BACKUP directory then having Backup Exec back up that directory.