Make sure you are not connect to the server via IP Address. The SQL Agent will only work using a hostname.

If that isn't the case, make sure Backup Exec is configured to backup SQL. Open Help -> About Backup Exec, and make sure there is a lcense for SQL server.

I am seeing the server under Remote Selections/Microsoft Windows Network, it's part of a workgroup and I am able to see all members.
I did install license for SQL Server backup, Agent for SQL Server is present under Help/About.
Thanks.

make sure the remote agent is installed and started on the SQL server.

In the selections you see at the moment - apart from C and D , do you also see the System State, or if a 2003 server the Shadow Copy components?

Remote Agent is started on the SQL box.
Shadow Copy Components and Utility Partition are also visible on the SQL server, in addition to C and D.

Also, there is a local SQL installation on the server running BackupExec and I cannot see that one either.
I have tried re-running the install program to make sure the SQL component is installed and that did not have any positive effect that I can see.

Hmm.. OK I woudl suggest running the install again, remove the SQL license key and then make sure SQL option is going to be installed - complete the install.

Re-run the install again, enter the license key, make sure the SQL option is going to be installed, then complete the install.

You can also try setting a registry key call Restrict Anonymous Support to 1 on the Media server and on the remote Sql server.

You can use the following TN

http://support.veritas.com/docs/238618

I am not sure how this can help, since that technote talks about an issue with Exchange. I am trying to backup a SQL database. Can you elaborate on how this might help with an SQL issue?

> Hmm.. OK I woudl suggest running the install again,
> remove the SQL license key and then make sure SQL
> option is going to be installed - complete the
> install.
>
> Re-run the install again, enter the license key, make
> sure the SQL option is going to be installed, then
> complete the install.

OK - I yanked the license and re-installed it.
I also re-ran the install in "repair" mode.
I did notice that on the screen where you can select/deselect options to install, the SQL Agent is Greyed-out but there is no red X to indicate that it will not be installed. When I do a help/about the SQL Agent is reporting as being installed.
This is 9.1 with SP 1 if that makes any difference...
Thanks.

Please ensure that the Backup Exec service account has proper rights on SQL:





http://support.veritas.com/docs/234733


You may also refer the following technote.





http://support.veritas.com/docs/249300


Enable Restrict Anonymous support on both SQL server and backup server.



http://support.veritas.com/docs/238618

Although, enabling the above option helps in troubleshooting Exchange issue, it has been seen that this is helpful in resolving the communication issues.


If the issue remains unresolved, please let us know.

Hi Mark,

The Registry key mentioned is a very generic key which can be modifed to 1 for any issue related to remote server configurations like cannot backup mailboxes,cannot see remote server , any authentication issues with remote agent etc etc.

This key is very helpful if SQL or Exchange are on a cluster and the SQL/Exchange databases are not seen.

It might help in your case too.

> Hi Mark,
>
> The Registry key mentioned is a very generic key
> which can be modifed to 1 for any issue related to
> remote server configurations like cannot backup
> mailboxes,cannot see remote server , any
> authentication issues with remote agent etc etc.
>
> This key is very helpful if SQL or Exchange are on a
> cluster and the SQL/Exchange databases are not seen.
>
> It might help in your case too.

I did find the document http://support.veritas.com/docs/271315 which discusses this registry key in relation to SQL resources, but unfortunately it did not help in this instance.
Thanks...

> Please ensure that the Backup Exec service account
> has proper rights on SQL:
>
>
>
> http://support.veritas.com/docs/234733

In following the instructions in technote #234733, I notice that the SQL Server Query Analyzer cannot be run from the server containing the backupexec installation. The SQL database I am trying to backup is on another server which is dedicated to running SQL. When I run the SQL Server Query Analyzer from that server, everything seems normal. I am using local authenticaion to both of these servers, the username/password are actually identical on both servers but they're two separate logon accounts because the servers are in a workgroup instead of a domain. I'm not sure if there's a way to run SQL SERver Query Analyzer from the BackupExec server, since it is not installed there.




>
>
>
>
> http://support.veritas.com/docs/249300


The service is running on the server containing the SQL database although it's not called MSSQLSERVER - it is called MSSQL$XXX (where XXX is the name of the SQL database.)

Thanks for your help!

On page 1000 of the Backup Exec Administrator's guide it says that the login account must have administreator rights to the server where SQL is. It also says these credentials must have the administrator role on the SQL instance. I'm not sure that I can do that with two standalone servers which are members of a workgroup.
If anyone knows of a way to do this, please let me know.

The problem had to do with the SQL Agent license I was using - it was an older license that does not support SQL 2000 so any databases created under SQL 2000 are not visible.