snootalope
IS-IT--Management
Our SQL 2005 Standard mirror set just took an ugly turn this last weekend. Something happened to the mirror server itself (no the principal) and I couldn't even log into it. Whenever I tried logging in as an admin I'd get RPC Server is unavailable. There were so many transactions trying to replicate to the mirror from the principal that our 3MB pipe was maxed out and pretty much killing anything else that tried to use the WAN. So, after a few hours of troubleshooting I decided to break the mirror.
Now, I think I've finally got this mirror server functioning properly again, as far as the domain goes (no more RPC errors). But now, the mirror can't be set backup because the two databases are not the same anymore. Whenever I run a "backup log" from the principal and restore it to the mirror I get the "...log is to new, please apply xxxxxxx..."
Is there anyway I can get this mirror set backup without recopying the entire database/log from the principal and restoring to the mirror during the wee hours of the morning?
Now, I think I've finally got this mirror server functioning properly again, as far as the domain goes (no more RPC errors). But now, the mirror can't be set backup because the two databases are not the same anymore. Whenever I run a "backup log" from the principal and restore it to the mirror I get the "...log is to new, please apply xxxxxxx..."
Is there anyway I can get this mirror set backup without recopying the entire database/log from the principal and restoring to the mirror during the wee hours of the morning?