It turns out that thing are a little bit more complicated. When mapping the exact time (SQL time is one hour off compared to Veeam) we saw that actually the log truncation breaks the mirror not the vmware snapshot removal (so mirror broke during the successful retried backup not depicted failure below); it happened twice so far.
*** WARNING !!! *** Mirroring state changed.
Timestamp: 5/29/2014 9:41:14 PM
Machine Name: xxx
SQL server: xxx
Mirroring state: SYNCHRONIZING;
Mirroring role: MIRROR;
Witness state: UNKNOWN;
adriand wrote:And that the customer actually has some plans which may backup the logs too, which means we may overlap with log truncation. the joy of web hosting...
Users browsing this forum: Google [Bot] and 10 guests