ArcServe SQL Agent Not Seen

[jsetaro]

I have some ArcServe 2000 clients that when I click on them under "Client Agents\Windows NT\Windows 2000 Clients", I see their drives, registry, System State, and Microsoft SQL Server. Some servers that do have the SQL agent installed do not show the SQL server under the agent. I have to back them up through "Microsoft Windows Network". I've uninstalled and re-nstalled ArcServe client and SQL and I still cannot access the SQL under the Client Agent. I also tried connecting as a different user. Any help would be greatly appreciated.

 

[vschumpy]

Add the agent using computername resolution checkbox in the GUI, and also check that file and print services are enabled on the box with the agent.

 

[jsetaro]

I tried that and it did not work.

 

[vschumpy]

Are they on operating systems other than NT4 or Windows 2000?

 

[jsetaro]

They are running 2000.

 

[speshalyst]

Hi,

Try Starting the Backup Agent RPC service with the ARCServe system account..

So it Shall be Written!
So it Shall be Done!!

 

[jsetaro]

I changed the service to start with the ArcServe account and it did not work. I removed the client and re-added him and it still did not pick it up.

 

[vschumpy]

sounds like perhaps the account has permission on the host server but not on the remote client - either way I thin Speshalyst is in the right direction, it would seem to be some sort of security issue. Is the IPC$ and ADMIN$ available on the remote agent connecting from the host server you are trying to backup from using the same account as you specified in the agent security?

 

[jsetaro]

Yes those shares are available.

 

[speshalyst]

OK ..

lets do a little test..
On the SQL server... go to HKLM\SW\CA\BAB\DSAgent\

under this you would see the SQL reg key..
Highlight DSAGENT.. create a new key.. call it "test" ..leave the class blank..

restart the Backup agent RPC server service..
Now open the BAB manager.. and browse to ur SQL server..

are you able to see a "golden Platter" called "test" ???

if you ..the agent RPC does have access to the SQL server.. just that the there is some kinda conflict on the SQL security settings..

So it Shall be Written!
So it Shall be Done!!

 

[jsetaro]

I did not see test.

 

[speshalyst]

Hi,

Ok.. Check the previleges for the ARCserve system account on the registry of the SQL server .. make sure it is added explicitly with full control and make it percolate it down the tree..

So it Shall be Written!
So it Shall be Done!!

 

[jsetaro]

He does have rights.

 

[speshalyst]

ok..

Since you are using ARCserve 2000..
just install the Exchange agent on the SQL server.. though u do not have exchange on it .. (assuming)

This should add the Exchange Reg keys..
now on the backup manager check if u see MS Exchange as a DB icon..



So it Shall be Written!
So it Shall be Done!!

 

[sandyboy]

Hi,

SQL Agent uses Microsoft NetBIOS (use "net use") to connect to the ADMIN$ if the connection is successful then DB Agent will use RPC (Remote Procedure Call) to communicate with the server.
Please NOTE: RPC is on top of TCP/IP. So SQL Agent just uses the top layer to do the connection, it lets RPC does all the work. So the bottom line is the ADMIN$ must be visible in order for SQL agent to work correctly.

We could try the following:
1.control panel >>networking>>>TCP/IP
properties
advanced
wins
enable NetBios over TCP/IP

2)set the following registry key on the server where the SQL agent is installed
HKLM / SOFTWARE / COMPUTERASSOCIATES / BRIGHTSTOR ARCSERVE BACKUP / DSAGENT / CURRENTVERSION / AGENT \ UseTCP = 1

3) Go to the discovery table of the BAB server and see if the remote machine is listed there or not. If not listed, see if the discovery service is able t o locate the remote machine. If it isn't try to add the remote SQL machine to
the discovery table of the BAB server

4) Check for the following ports are open or not(Both tcp/udp).It should be open
TCP/139 - SQL agent
TCP/6071 - Agent RPC Service
TCP/6070 - Agent Remote Service
TCP/6050 - NT Client agent

4. Use the rpings and rpingc utilities to test RPC connectivity. This article

http://support.microsoft.com/default.aspx?scid=kb;en-us;272218

refers to Exchange 2000, but actually these are general rpc connectivity test utilities, so you don't really have to have Exchange installed.

Restart the backup agent rpc service once these suggestion are performed.

Cheers