March 14, 2016 at 8:08 am
Hi Guys,
We had an asynchronous mirror set up. When the link between the primary and mirror went down the mirror obviously broke. I have two questions.
1. Can I schedule a job to restart a mirror when it breaks.
2. Since asynchronous mirroring commits on the primary before sending the transaction to the mirror, why could I not shrink the log file of the primary database before removing the mirror?
March 14, 2016 at 8:34 am
2) Because the log records still have to be sent to the secondary. If they could be removed from the log before being sent to the secondary, then you'd have to reinit the mirror from scratch every time the network drops.
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
March 14, 2016 at 8:41 am
Hi Gila,
Thanks for your feedback. I just wanted to confirm. Any Ideas about restarting a mirror automatically? I have a very highly transactional DB and if the mirror goes down for a short amount of time it will go out of sync and I wont be able to restart the mirror, I will have to reconfigure it from the start.
March 14, 2016 at 8:48 am
Not offhand, no. You'll probably need a job that runs every (x) minutes, checks the state and then takes any necessary action. Won't be much overhead if it does nothing most of the time.
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
March 14, 2016 at 9:13 am
Thanks again. Will research to find some options.
March 14, 2016 at 12:51 pm
Might be worth a shot to try triggering off of one of these: Alerting on Database Mirroring Events
...maybe one Session State changes?
March 21, 2016 at 12:21 am
Thanks for the tips, I will do some research on these.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply