> Don,
>
> I would like to understand this better.
> What is the "known problem" that you are referring to?
> We have a few SQL 6.5 (with SP5a) servers installed
> and we can back up and restore with no problems.
>
> Can you expand on the issue that you and/or
> your customer is seeing.  I remember hearing
> something about this but it never surfaced again
> and we could not recreate it.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> Del Hoobler
> IBM Corporation
> hoobler AT us.ibm DOT com
>
>
> "France, Don (Pace)" <don.france-eds AT EDS DOT COM>@VM.MARIST.EDU> on 
> 11/10/99
> 09:25:34 PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject:  Re: MSSQL is unable to send backup data through pipe to the
conne
>       ct agent.
>
>
>
> Try what Del's suggested;  btw, there's a known problem with SP5a and ADSM
> Connect Agent... I am researching how/if my customer resolved it.  Will
> advise...  (In our shop, the Connect Agent failed when we installed SP5a;
> it worked prior to applying SP5a, yet they want this SP for y2k reasons!)
> Currently, they are doing offline backups of the files using dsmc;  we are
> just now re-driving the effort to understand the problem, if we can find a
> way around it or not.
>
>
> Don France
> PACE - http://www.pacepros.com
> Walnut Creek, CA
> Bus-Ph:   (408) 257-3037
>
>
> -----Original Message-----
> From: Bill Smoldt [mailto:smoldt AT STORSOL DOT COM]
> Sent: Wednesday, November 10, 1999 6:57 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: MSSQL is unable to send backup data through pipe to the
> connect agent.
>
>
> Terry,
>
> To add to Del's #3 below, please send the SQL data to a copygroup with
disk
> as the initial destination for test purposes.  You can receive the error
> you
> describe if all the tape mount points are busy during the backup.
>
> What is the commmethod for the SQL agent?
>
> Bill Smoldt    SSSI
> Storage Solutions Specialists, Inc.
>
>
> -----Original Message-----
> From:   ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
> Behalf Of
> Del
> Hoobler
> Sent:   Wednesday, November 10, 1999 6:21 AM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        Re: MSSQL is unable to send backup data through pipe to
the
> connect agent.
>
> Terry,
>
> It looks a lot like your ADSM server connection is being
> terminated BEFORE it has a chance to back anything up.
> I few things to check/try:
>
> 1. Check the dsierror.log file in the SQL Agent directory
>    for errors that it might contain.
>
> 2. Also, check the ADSM server activity log to
>    find out the reason it might be terminating the connection.
>
> 3. Does the new policy domain have assigned storage?
>    Try to changing the domain to one that you know works.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> Del Hoobler
> IBM Corporation
> hoobler AT us.ibm DOT com
>
>
> > I'm fairly new to ADSM, and I can't get my MSSQL databases backed up
with
> > the SQL Connect Agent. Everything else I've looked at seems okay, but
> when I
> > try to do a backup of any database (master, msdb, or other), it fails.
> Error
> > messages say:
> > ADSM log shows:
> > 11/09/1999 12:08:23,Backed up - master, type: DB, size: 16276480, actual
> > bytes: 0, secs: 0.0, Kb/Sec: 0.0, SQL server: NTSERVER50, ADSM server:
> > acbl-jfv-adsm, SQL status: DB-LIB message: Write on dump device
> > '\\.\pipe\sqladsm\1999120818\2690' failed, vsn=828 return=-2 status=-2.
> > Please consult the SQL Server error log for more details., ADSM status:
> > ANS0322E (RC307) no text available for this return code.
> > SQL error log shows:
> > 1999/11/09 16:05:38.04 kernel nmpswriteflush: Write failure on backup
> > device '\\.\pipe\sqladsm\1999160533\2260', returned operating system
> error
> > 232(The pipe is being closed.)
> > I can't figure out what my problem is, and can't find reference to this
> sort
> > of error anywhere. A lot of things seem good:
> > I just installed the MSSQL connect agent on my desktop for testing. This
> > machine has the ADSM client on it, of course, and is being nicely backed
> up
> > every night.
> > Our ADSM server has been and is working fine.
> > The SQL connect agent does indeed connect to the ADSM server. I did set
> up a
> > new policy domain and such to "house" my SQL server backups. The server
> sees
> > my attempt to backup a database, but shows a backup size of 0 bytes.
> > The problem seems to be between MSSQL and the SQL connect agent, as far
> as I
> > can tell. The connect agent connects to MSSQL okay, and lets me select
> which
> > database to backup. The error occurs when I actually click "backup".
> > My client is NT 4.0 SP5. MSSQL is 6.5 with SP5a (7.0 SP1 is available
for
> > testing, if necessary.) Both MSSQL and the connect agent run under the
> same
> > domain administrator account.
> > What else obvious am I leaving out?
> > If you know what I'm doing wrong, or can point me to more information to
> > help isolate the problem, please reply.
> >
> > Terry Phelps
>