January 9, 2007 at 4:12 pm
I've been combing through BOL & can't find a clear answer to this one.
We have a database being mirrored between [physical] locations. It's running in high-safety mode with no witness.
We are to have a [WAN] network outage which will last at least 3 hours, possibly up to 12 (worst case scenario, rolling back etc).
The question is: do I need to pause or stop my mirroring or will it sit there happily by itself & re-establish itself when the network comes back online, resynchronizing? While the network link is down, will transactions be committed on the principal, allowing people to work normally or will it pitch a fit waiting for the mirror to respond? (Not that I expect anyone to be using the DB at the time of night the outage is occurring).
Transaction log/disk space will not be an issue.
Kind of tricky to find an answer, as everything I've read so far assumes one or the other of the servers is down, rather than the link between them.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
January 12, 2007 at 8:00 am
This was removed by the editor as SPAM
January 17, 2007 at 1:22 pm
Not sure if it is the way to go, but we're planning to just pause mirroring & let the transactions sit in the log then resume when we're done. Fortunately, at the best of times there aren't that many transactions and the log has plenty of room to accomodate them for this outage.
Check out ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/05ede3b4-6abe-4442-abb7-9f5aee1d6bc0.htm in BOL.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply