The root cause was the aggressive logging filling up the file system. Our
admins have the logs on the same file system with the data, so when the
filesystem got full it couldn't write to the transaction logs which
corrupted them
Thank you for the tips on recovery, I will forward them to our admins
On 1/6/2017 10:09 AM, Webster Homer wrote:
> This happened while testing and was not in a production system. So we
> just deleted both collections and recreated them after fixing the root
> cause. If this had been a production system that would not have been
> acceptable. What is the best way to re
If you just deleted the tlog files on the source, you'd likely miss
updates, right?
I can think of two ways to get source and target back in sync:
1> go ahead and delete the tlogs, then re-index from some point guaranteed
to have been propagated to the target _before_ the tlog went wonky.
2> rebu
