March 5, 2013 at 10:06 am
Hi,
With database mirroring, if the mirror database fails, the transaction log space on the principal database cannot be reused even if we are taking transaction log backup. This mean we need to have enough space for the transaction log to grow or bring mirror database online before the logs fills up the availabale disk space or break the database mirroring.
If we lost our principal database, and we force to switch on the mirror database with the "SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS" command. After, the old mirror is now principal with the disconnected status because the old primary stil unavailable.
During this time and until the old principal become mirror and online, do I have a transaction log space pressure on the new principal ?
regards
March 14, 2013 at 8:34 am
I am not sure I understand exactly what you are asking.
If the mirror fails, the first thing I would do is break the mirror and check my backups to ensure I have no transaction log pressure.
If the principal fails, as you correctly pointed out, the mirror takes over but is advertised as disconnected. In this case as well, I would break the mirror and check my backups to remove the problems associated with transaction log pressure.
The command you posted does exactly what it says on the tin: Allows data loss which is the opposite of what high availability mirroring is about!
A failed mirror imho is no longer a mirror. Break it, fix the problem and reestablish the mirror as soon as you can. With a good backup plan your Transaction Logs remain reasonably small and you no longer have a problem!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply