We just ran into the same problem on a 60GB database that we were attempting
to restore to another server. The problem ended up that the SQL server had
"reconstruction" processing that it needed to perform as part of the restore
and (in our case) was going to take from 4 to six hours. The problem was
that our COMTIMEOUT server option was set for 300 seconds. We performed a
"setopt commtimeout 21,000" (which is 6 hours in seconds) and it worked. I
would just remember to set this option back to a lower number when you are
completed.
-----Original Message-----
From: Jacques Butcher [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 1:37 PM
To: [EMAIL PROTECTED]
Subject: SQL Restore Problem. Please HELP!!!
We are trying to restore a 17GB database by using the TDP agent for SQL
version 1.1.2. During the restore process the TDP agent connets to the SQL
server, then the TSM server, then onto the SQL server again after which we
get the message "Waiting for SQL Server". Looking on the TSM server the
client session times out after reaching it's timeout threshold. Looking on
the SQL server the daabase and transaction log files grow. The restore
however doesn't continue and gets stuck on "Waiting for SQL Server".
We are in desperate need of any help and any help will be greatly
appreciated.
