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
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

> Yes, I created a separate domain, and registered the node
"sql_ntserver50"
> in that domain on my one and only server. When I look at it, it all seems
> right to me. But when I try to backup a SQL database with that node name,
it
> fails, with NO meaningful error messages except those pertaining to
MSSQL's
> inability to write to the backup pipe.  If I simply change the node name
to
> "ntserver50", which is registered with the server for file backups, it
backs
> up just fine.
>
> Are other folks not having this problem?
>
> Terry Phelps