Hello everyone,
Now many our sql server 2008 r2 sp1 servers start to report errors when daily full database backup job starts:
2014-07-11 01:19:04.980spid59sDatabase mirroring is inactive for database 'XXXX'. This is an informational message only. No user action is required.
2014-07-11 01:19:45.700 spid2346
Error: 18056, Severity: 20, State: 29.
2014-07-11 01:19:45.700 spid2346
The client was unable to reuse a session with SPID 2346, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this
error message.
When i want to connect to one of servers when a big database is being backuped fully using management studio ,i feel a long time delay. But at the that time , cpu is low , memory related performance counters are normal.
So i wonder if there are some system resource contention when database full backup happens ,and this contention impact login progress.
Our databases are all configured for database mirroring, and we use litespeed software to backup database.
I have no idea on how to troubleshoot this problem ,and it seems profiler and new extended event have no events about this. So any advice or some tools/ways to deep troubleshooting ?
Many thanks.