April 6, 2011 at 4:22 am
- Win. (4/6/2011)
BTWI have disconnected the Mirroring.
That's going to make matters worse.
The mirroring log reuse reason means that the mirroring is not keeping up with the speed of transactions added, that there's a backlog of log records that need to be sent over to the mirror. The log entries cannot be marked inactive until they are committed at the mirror.
Synchronous or Asynchronous mirroring?
Check the mirroring send queue.
Check the network latency.
Something in the mirroring is not coping with the load that's been imposed.
p.s. more frequent log backups are not going to help with this, since the problem's the mirroring
p.p.s. while the mirroring's disconnected the log records will not be able to be sent, will be backing up more and more, will be making the log grow even more.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 6, 2011 at 5:19 am
Mirroring was stopped to stop increasing the priority issues.
As because of this TempDB also getting increased. Since, both rest on same drive.
Planning to log backup and shrink the log file.
Cheers,
- Win.
" Have a great day "
April 6, 2011 at 5:21 am
- Win. (4/6/2011)
Planning to log backup and shrink the log file.
Not going to help. You need to address the cause, which currently appears to be something in the mirroring.
Restart the mirroring, or that log will just keep growing until it fills the drive.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply