SQL Agent icon will not show up in backup exec

[superfunmonkey]

I have backup exec 8.5 running on the a server with a tape drive. On this server I also have the SQL client tools installed and the SQL agent installed. On the server with SQL 2000 running I have the Backup Exec Agent running on that server. I have looked at the help site at veritas but nothing I try works. Any one have an answer why my SQL agent will not show up in Backup Exec?

 

[SQLBill]

What do you mean your SQL Agent isn't showing up? I see by your query that it appears you are looking for an 'icon', but I'm not aware of any icon for SQL Agent. I have Veritas BE v8.6 loaded on a SQL Advanced Server 2000 cluster with SQL Agent licenses loaded. When I select 'BACKUP' from the toolbar and the 'Backup Job Properties' window pops up - there is a tab titled 'SQL'. If you can 'use' that tab (change/select items on it) then SQL Agent is installed and working.

-SQLBill

 

[superfunmonkey]

Check your log file after you backup. Is it backing up all databases on your SQL server? Mine is not, It will not backup .mdf and .ldf which is what I want backed up in the first place.

The following is off of Veritas web site.

"It is possible to select the \MSSQL7 directory (MS SQL 7.0) or the \Program Files\Microsoft SQL Server\MSSQL (MS SQL 2000) directory from the drive shares of a system running Microsoft SQL Server. However, when either of these directories are selected, the Backup Exec software will attempt to perform a "flat file" backup of the SQL database files. If the database is running and the files are open, Backup Exec will not be able to backup database files and will report these files as in-use and skipped within the job log file"

"Microsoft SQL Server backups should only occur via the selections made available through the Backup Exec Agent for SQL Server"

http://seer.support.veritas.com/sea...Path=seer.support.veritas.com/docs/242688.htm

I think maybe this is one of the differences between Version 8.5 and 8.6 because I have a SQL tab but I can not choose what to backup from here. I am suppose to have an Icon in the backup selections menu.

Can anyone help me?

 

[SQLBill]

I don't backup the .mdf and .ldf files themselves. I tried that and like you found it fails since the files are open.

I select BACKUP, on the Selection tab expand down through the tree (expand Remote Selections, expand Microsoft Windows Network, expand the domain, expand the SQL Server group) until you see MS SQL SERVER with a plus in front of it. Double-click on MS SQL SERVER, select only the databases that you want to back up (you will have the options for filegroups, but unless you have them, don't check them).

Then proceed with your backup. Use the SQL tab to make any SQL specific changes (such as Transaction Log BU, FULL BU, Consistancy checks). It backed up the whole database properly.

The difference according to Veritas:
if you select the .mdf and .ldf files Veritas BE doesn't use the SQL Agent. So, you need to have the OPEN FILE Agent or the files need to be closed.

Selecting the databases themselves from the MS SQL SERVER part of the tree forces SQL Agent to be used, which can backup the database while it is being used (just like using SQL itself through Enterprise Manager).

The big point I'm trying to get across, is find the MS SQL SERVER portion of the tree and select the DATABASE(S) that you want to back up. Don't expand down to the drive and pick the files - that won't work as you pointed out.

Also, if you select BACKUP from the toolbar and click on the SQL tab...if everything is greyed out then SQL Agent is not loaded (or not loaded properly).

-SQLBill

 

[superfunmonkey]

"expand Remote Selections, expand Microsoft Windows Network, expand the domain, expand the SQL Server group"

Yes exactly that's what I am missing the SQL server group.
It does not show up even though the agents are all loaded. I have tryed many things but noting seems to make the Sql server group show up so there is no way I can choose the databases I want to back up.

Any one know why?

 

[SQLBill]

do you have Remote Agent loaded (do you have the license for it)? Here's a trick to see if that's the problem.

Uninstall BE, re-install it, but don't use the licenses. That will load the evaluation copy. When you get to the screen that allows you to choose what you want installed choose Backup Exec, SQL Agent, Remote Agent, and if you have it Library Expansion Option. When it loads, see if it works....if it does then you probably don't have the necessary license(s) and I would start with the Remote Agent license.

-SQLBill

 

[superfunmonkey]

I do have the license and it is installed. This is a link to the Veritas site to check if it is indeed installed. I tryed all things on the list except the registy setting which I am getting ready to try.

Any other Ideas?

Thanks for the input.

http://seer.support.veritas.com/docs/245130.htm

 

[SQLBill]

I relooked at your initial post and I'm wondering if you installed everything in the right place. I have a 2-node cluster with a tape library. I had to load ALL of the BE software, including the agents, onto each node of the SQL Server. By your post, it appears you have two servers: one is your SQL Server and the other may be a backup server. YOu have BE on the SQL Server and the SQL Agent on the other server (if I read the post right). I think that might be the problem. Have you tried loading the SQL Agent on the SQL Server with BE?

-SQLBill

 

[superfunmonkey]

I can only load the SQL Agent on the server with BAckup Exec installed on it. That is the way Veritas says it should be done and I did try to install it on the SQL server but it will not give me the option to do that.

 

[SQLBill]

I have Backup Exec, Remote Agent, and SQL Agent all loaded on my SQL Advanced Server. But my tape library is also connected to the same system.

I can't think of any other suggestions. Sorry.

-SQLBill

 

[superfunmonkey]

Thanks for your help.

If anyone else has ideas please let me know.

 

[jp2000]

Do you have the SQL Enterprise Manager loaded on your backup box that you are creating the jobs with. If you don't, you will not see the SQL option when creating the job. Same goes for Exchange Agent.

 

[kohlbacher]

Hi Folks,

seems we are not alone with this issue - We`re running some sites for a customer - all with the same Configuration:

2 Node Cluster and one PDC - all W2k SP2

On the Clusternodes, there is an SQL-Server (2000 SP2)in active -passiv mode.

We`re using BE 8.6 - newest build and SQL-Agents - newest available

We have exactly the same behaviour: Selecting the SQL-Alias (Cluster Network-Name) for Backup - there is NO selection for the databases - no SQL Server - simply NOTHING that looks like an SQL Server ...

When selecting a standalone Server with SQL Server installed - everythings fine and Backup runs ok - so what the heck is going on there ? Veritas sent us a fix for this issue - no way - same error - I really have no ideas anymore - maybe someone could point me in the right direction ?

Yes - SQL Agent is installed on the Backup-Server (PDC)
Yes - Remote Agent is working fine and is the right version

Yes - i already tried renaming bewinnt7.sch and bewinui.uni and recreated the files - no changes

I think this has to be by design in the meantime ! - sorry - but I`m working on this thread for more than a month in the meantime - we`re using flat file backup from SQL meanwhile - but I want to solve this issue as soon as possible ..

any help would be greatly appreciated !

Cheers,

Peter

 

[kohlbacher]

Folks - if anybody is still interested in this Task - we finaly found a solution in cooperation with Veritas.

There is a Registry Key, wich will be deleted (!) when you`re installing SQL Server 2000 SP2 (Microsoft decided this key is no longer needed ...--->Q289683)

HKLM/System/CCS/Services/Lanman Server/Parameters

There is a RegMultiSZ Value named "noremappipes" - has to contain at least to Params: winreg and svcctl

If you - after implementing this key - get the errormessage "rpc call failed" - simply delete the bewinui.sch file (your actual schedule has to be rescheduled after this) - and voilá - SQL Agents are working fine and you can backup every filegroup !

cheers,

Peter