ADSM-L

Re: MSSQL is unable to send backup data through pipe to the connect agent.

1999-11-11 20:08:45
Subject: Re: MSSQL is unable to send backup data through pipe to the connect agent.
From: Bill Smoldt <smoldt AT STORSOL DOT COM>
Date: Thu, 11 Nov 1999 18:08:45 -0700
Terry,

The suggested and normal implementation of the SQL Agent is to create a
separate domain and register a new node for the SQL Agent in that domain.
This allows a simpler management interface when setting the retention
parameters.  By using the same node name, you are using the retention
parameters of your filesystem backup domain.

This does cost an extra node license, BTW, but it's worth it.  I prefer to
use nodename_sql so that I can see the nodenames together in the q node
list.  Other people like to see the SQL or Exchange servers grouped
together, hence the suggested name from the agent installation.

All this is in the documentation for the SQL Agent, as are the suggestions
for retention and scheduling.

If you didn't have the sql_ntserver50 registered on the server, you should
have received a TCP timeout when you tried to connect to ADSM for the
backup.  Did you have the opt file configured to go to the correct server?

Bill Smoldt    SSSI
Storage Solutions Specialists, Inc.