ADSM-L

Re: SQL Server restore fails (5.2.1.0)

2004-04-19 13:40:58
Subject: Re: SQL Server restore fails (5.2.1.0)
From: "Frost, Dave" <Dave.Frost AT SUNGARD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 19 Apr 2004 14:19:58 +0100
Eric,

Is the database being restored very large?  SQL server can take many hours
to recreate and initialize the database tables it has asked for the tape
but *before* it actually starts reading the tape.  In these cases, we have
had to set our server timeouts to 4-6 hours during the period of the
restore


Regards,

-=Dave=-
Sungard Vaulting Services
+44 (0) 20 7608 7140

(A)bort (F)ail (T)oss computer across room






                      "Loon, E.J. van -
                      SPLXM"                   To:       ADSM-L AT VM.MARIST 
DOT EDU
                      <[email protected]        cc:
                      M.COM>                   Subject:  SQL Server restore 
fails (5.2.1.0)
                      Sent by: "ADSM:
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      19/04/2004 13:50
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






Hi *SM-ers!
Our SQL Server guys are migrating several databases to a new server by
using
a TSM backup. Most database restores went fine, except for one.
My conclusion is that the TSM server cancels the session after waiting for
3
hours, but I cannot find why the restore doesn't work for this database
only.

They performed the following actions to accomplish the migration:
1) The changed the tdpsql.cfg:
FROMSQLserver  af05100
SQLSERVer kl1007w9
2) They changed the dsm.opt
nodename    af05100-sql
PasswordAccess   prompt
3) They started the restore through the GUI
4) They entered the TSM password and selected the databases to restore.
5) All were restored, except for one. They repeated the action for this
database only: same result.
I've had them collect the following data:

DSIERROR.LOG:
04/19/2004 00:13:56 ANS1005E TCP/IP read error on socket = 824, errno =
10054, reason : 'An existing connection was forcibly closed by the remote
host.'.
04/19/2004 00:13:56 sessRecvVerb: Error -50 from call to 'readRtn'.

TDPSQL.LOG:
04/19/2004 00:13:56 ACO5436E A failure occurred on stripe number (0), rc =
418
04/19/2004 00:13:56 ANS1017E (RC-50)  Session rejected: TCP/IP connection
failure
04/19/2004 00:13:57 Restore of Test failed.
04/19/2004 00:13:57 ANS1017E (RC-50)  Session rejected: TCP/IP connection
failure

Windows Event Log:
4/19/2004       00:13:56        MSSQLSERVER     Error   (2)     17055
KL1007W9\ntdbadm        KL1007W9        18210 :
BackupVirtualDeviceFile::ClearError:  failure on backup device
'TDPSQL-00000BB4-0000'. Operating system error 995(The I/O operation has
been aborted because of either a thread exit or an application request.).

SQL Server error log:
2004-04-18 21:43:09.82 spid53    Unnamed tape (Family ID: 0xb48c3f90,
sequence 1) mounted on tape drive 'TDPSQL-00000BB4-0000'.
2004-04-19 00:13:56.85 spid53    BackupVirtualDeviceFile::ClearError:
failure on backup device 'TDPSQL-00000BB4-0000'. Operating system error
995(The I/O operation has been aborted because of either a thread exit or
an
application request.).

TSM Server log:
18-04-2004 21:43:09 ANE4991I (Session: 446380, Node: AF05100-SQL)  TDP
MSSQL
Win32 ACO3003 Data Protection for SQL: Starting full restore of backup
object Test to database Test on server KL1007W9.
18-04-2004 22:13:27 ANR0481W Session 446380 for node AF05100-SQL (TDP MSSQL
Win32) terminated - client did not respond within 1800 seconds.

Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines



**********************************************************************
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>