RE: Tracing SQL Server 2000 Connections
- From: Dougie Brown <dougiebrown@xxxxxxxxxxxxxxxx>
- Date: Mon, 5 Nov 2007 07:59:44 -0800
Hi Charles
Thanks for your quick response! Sorry there's a few things that I need to
clarify!
Backup Exec (Veritas) and Windows Backup don't fail, they succeed but during
the last minute of their backup connections to SQL Server from other
applications time out.
In my mind these applications are either the direct cause of the lost
connections or are stressing something and hence causing the lost connections.
I'm trying to get NetMon installed on the test cluster to trace the traffic
actually on the server but I've not been successful yet, different teams need
to be involved. Also I believe a support call has been opened with Microsoft
so I think that will take precedence over the direction of this investigation!
Thanks for your help so far, if I manage to get NetMon installed soon then I
will post a reply!
Cheers
Doug
"Charles Wang[MSFT]" wrote:
Hi Doug,.
I understand that when you tried to back up your whole C drive to your
tape, both Backup Exec and native Windows NT Backup failed with a
connection timeout. If you exclude System32 from the backup, this issue did
not appear.
If I have misunderstood, please let me know.
I think that NetMon is a very good tool to trace the calls from the TCP/IP
stack all the way into SQL Server. You may check which TCP port your SQL
Server is listening on from svrnetcn.exe (SQL 2000) or SQL Server
Configuration Manager (2005), after that you can filter the trace according
to the TCP port. However this depends on your BACKUP EXEC program using
TCP/IP protocol to connect to your SQL Server. For Windows NTBackup, it
could not backup files which are open, so it could not backup SQL Server
database files which are in use.
From your description, you mentioned that nothing got logged by SQL
Profiler, so I would like to check with you whether or not your BACKUP EXEC
utility had a valid SQL login or enough permission to log on your SQL
Server. Also, did you add "Audit Login Failed" event for your SQL Profiler
trace file?
I recommend that you check your Windows Event logs to see if there are any
error logs and post them here for further research. Additionally to narrow
down this issue to see if it is caused by SQL Server, could you please just
backup your SQL Server folder to see if it can succeed?
Thanks for using Microsoft MSDN Managed Newsgroup. If you have any
questions or concerns, please feel free to let me know. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
- Follow-Ups:
- RE: Tracing SQL Server 2000 Connections
- From: Charles Wang[MSFT]
- RE: Tracing SQL Server 2000 Connections
- References:
- Tracing SQL Server 2000 Connections
- From: Dougie Brown
- RE: Tracing SQL Server 2000 Connections
- From: Charles Wang[MSFT]
- Tracing SQL Server 2000 Connections
- Prev by Date: RE: Tracing SQL Server 2000 Connections
- Next by Date: RE: Tracing SQL Server 2000 Connections
- Previous by thread: RE: Tracing SQL Server 2000 Connections
- Next by thread: RE: Tracing SQL Server 2000 Connections
- Index(es):
Relevant Pages
|