|
|
Posted by Erland Sommarskog on 05/16/06 00:38
pb648174 (google@webpaul.net) writes:
> I added seconds and got the same "Timeout expired" error for 3 backups
> in a row, with the backups happening every two hours. The issue went
> away by the time the 4th backup (8 hours later) came up. The output is
> below with time.
>
> 10:00:00.43
> Timeout expired
> 10:00:16.35
15 seconds is the default connection timeout. So it does look like a
connection problem after all. What I don't understand is the message.
But maybe there is some variation of connection problems where ODBC
do find the server, but is not let in?
> The interesting thing is that there are two production SQL 2005 servers
> and one backup SQL 2005 server. Here is how they were affected during
> the three failed backups, two hours between each, with no loss of
> connectivity for users using the application. The duration between
> start and end for the failure is pretty consistently about 16 seconds
> as in the above error message.
>
> production1 production2 backup
> 10am down up down
> 12pm down down down
> 02pm down up up
So which of the servers did the script try to connect to?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|