ADSM-L

Re: TCP Failair on SQL TDP.

2001-08-20 12:36:26
Subject: Re: TCP Failair on SQL TDP.
From: Ofer <ofer AT TRIP.CCC.CO DOT IL>
Date: Mon, 20 Aug 2001 19:37:06 +0300
Hi Rechard,


I didn't see any of the problem that you mentioned. There is no migration or 
backup
db at that time.
my server option is COMMTimeout  2000 & IDLETimeout  90.
I gut no error regarding the communication device in the event viewer.

Ok. The TDP Client massage is like the following.

kh: Backup failed:ANS1017E(RC-50) Session rejected:TCP/IP Connection failure.

The server act  log is.

08/20/01   14:00:12  ANR0406I Session 3 started for node MKNT66_SQL (TDP
                      MSSQLV2 NT) (Tcp/Ip 192.168.10.166(2963)).
08/20/01   14:00:15  ANE4995I (Session: 3, Node: MKNT66_SQL)  TDP MSSQL NT
                      2.1.0
08/20/01   14:00:15  ANE4991I (Session: 3, Node: MKNT66_SQL)  TDP MSSQLV2 NT
                      ACO3006 TDP for Microsoft SQL Server: Starting backup for
                      server MKNT66.
08/20/01   14:00:15  ANE4991I (Session: 3, Node: MKNT66_SQL)  TDP MSSQLV2 NT
                      ACO3000 TDP for Microsoft SQL Server: Starting full
                      backup of database kh from server MKNT66.
08/20/01   14:00:30  ANR8337I 3570 volume 03D5AA mounted in drive DRV1
                      (/dev/rmt0).
08/20/01   14:04:24  ANR0406I Session 4 started for node MKNT66_SQL (TDP
                      MSSQLV2 NT) (Tcp/Ip 192.168.10.166(2972)).
08/20/01   14:04:24  ANE4993E (Session: 4, Node: MKNT66_SQL)  TDP MSSQLV2 NT
                      ACO3002 TDP for Microsoft SQL Server: full backup of
                      database kh from server MKNT66 failed, rc = 418.
08/20/01   14:04:24  ANE4991I (Session: 4, Node: MKNT66_SQL)  TDP MSSQLV2 NT
                      ACO3008 TDP for Microsoft SQL Server: Backup of server
                      MKNT66 is complete.   Total SQL backups selected:
                            1   Total SQL backups attempted:              1
                      Total SQL backups completed:              0   Total SQL
                      backups excluded:               0   Total SQL backups
                      inactivated:            0    Throughput rate:
                                   5,023.50 Kb/Sec   Total bytes transferred:
                                     1,260,388,352   Elapsed processing time:
                                     245.02 Secs
08/20/01   14:04:24  ANR0403I Session 4 ended for node MKNT66_SQL (TDP MSSQLV2
                      NT).

The Application event log get the following massage.

date:   20/08/2001   Source:  MSQLSERVER
Time:  14:04            Category: (2)
Type:  error             Event ID:17055
User:   MKNT66\Administrator
Computer: MKNT66

Description
18210:
BackupVirtualDeviceFile::RequestDurableMedia:Flush failure on backup
device 'TDPSQL-00000364-0000'.Operating system error 995(error not found).

So I am trying to backup a 30GB database. I define the management class and the
client by the book.
The is no info in tecnet that can help me to resolve the event ID 17055.
I will appreciate if you check into it. ( maybe encountered this problem before 
).

Thanks in advance.
Ofer Nachom.

rbs AT bu DOT edu wrote:

rbs AT bu DOT edu wrote:

> >The q actlog give the following : ANS1017E ..node name ... backup
> >failed.
>
> Ofer - I don't see how an ANS message could appear in the server
>        Activity Log, as that is purely a client message.
> In the Activity Log at the time of the connection failure, you
> should see some indications of the cause of the problem.
> Here are my notes, from ttp://people.bu.edu/rbs/ADSM.QuickFacts :
>
> ANS4017E Session rejected: TCP/IP connection failure [Same as ANS1017E]
>         This is what the client sees and reports, but has no idea why.
>         The cause is best sought in the ADSM server Activity Log for that 
> time.
>         Could be a real datacomm problem; or...
>         Grossest problem: the ADSM server is down.
>         An administrator may have done a 'CANcel SEssion'.
>         If during a Backup, likely the server cancelling it due to higher
>         priority task like DB Backup starting and needing a tape
>         drive...particularly when there is a drive shortage.  Look in the
>         server Activity Log around that time and you will likely see
>         "ANR0492I All drives in use. Session 22668 for node ________ (AIX)
>         being preempted by higher priority operation.".
>         Or look in the Activity Log for a "ANR0481W Session NNN for node
>         <NodeName> (<NodeType>) terminated - client did not respond within NN
>         seconds." message, which reflects a server COMMTimeout value that is
>         too low.  Message "ANR0482W Session <SessionNumber> for <NodeNode> 
> name
>         (client platform) terminated - idle for more than N minutes." is 
> telling
>         you that the sever IDLETimeout value is too low.  Remember that
>         longstanding clients may take considerable time to rummage around in
>         their file systems looking for new files to back up.
>         Another problem is in starting your client scheduler process from
>         /etc/inittab, but failing to specify redirection - you need:
>          dsmc::once:/usr/bin/dsmc sched > /dev/null 2>&1    # TSM scheduler
>
>  Richard
<Prev in Thread] Current Thread [Next in Thread>