ADSM-L

Re: TDP for SQL restore seems to hang

2005-04-28 10:46:35
Subject: Re: TDP for SQL restore seems to hang
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 28 Apr 2005 16:46:47 +0200
Hi Mark and David!
Thank you very much for your reply!
The database they are trying to restore is about 500 Mb., so formatting
should easily be done in one hour...
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines



-----Original Message-----
From: Stapleton, Mark [mailto:mark.stapleton AT BERBEE DOT COM]
Sent: Thursday, April 28, 2005 16:26
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for SQL restore seems to hang


From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of Loon, E.J. van - SPLXM
>I have a few SQL clients which seem to "hang" when trying to
>restore a large
>database. Restoring a small one (Northwind) works fine, but
>when they want
>to restore a larger database TDP just says "Waiting for TSM
>server.." and
>nothing else happens until the session is cancelled by the
>server after 3600 seconds.
>The client has a session in the SendW state, but the amount of bytes
>transferred is minimal. The input tape also gets mounted.
>The actlog just contains the following lines:
>
>28-04-2005 13:18:11 ANE4991I (Session: 714765, Node: KL1012EZ-SQL)  TDP
>MSSQL Win32 ACO3003 Data Protection for SQL: Starting full
>restore of backup
>object SCReport to database SCReport on server KL1012EZ.
>(SESSION: 714765)
>
>28-04-2005 14:20:04 ANR0481W Session 714765 for node
>KL1012EZ-SQL (TDP MSSQL
>Win32) terminated - client did not respond within 3600
>seconds. (SESSION: 714765)
>
>The tdpsql.log also doesn't show any cause, just that the restore is
>canceled due to the session cancel by the server:
>
>04/28/2005 15:19:25 ACO5436E A failure occurred on stripe
>number (0), rc = 418
>04/28/2005 15:19:25 ANS1017E (RC-50)  Session rejected: TCP/IP
>connection failure
>04/28/2005 15:19:26 Restore of SCReport failed.

This has been discussed before in this forum.

When you restore a large SQL file, the first thing the restore requires
is that the space for the restore be formated by SQL Server. After the
format is complete, data starts to flow to the client.

If the commtimeout occurs before the formatting is complete, the backup
fails.

Bump your commtimeout parameter up and see if that fixes the issue.

--
Mark Stapleton (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
Office 262.521.5627


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>