benbour wrote:That would be great! I didn't see a note on the KB, can you show me where you saw that info?
sphilp wrote:rmcmillan - you're not alone in experiencing Exchange corruption. Until your post, we weren't sure the Exchange 2013 issue we experienced was related to the CBT issue or not.
We ended up with 2 out of 3 mailbox databases unable to be mounted, restored to a pre-6 backup and made sure not to back it up until we'd turned off CBT. We haven't experienced the corruption issue since then.
We also experienced some SQL Transaction log issues, but didn't require a VM restore for those (hallelujah). We ended up changing the DB recovery model to simple, taking a full SQL database backup, then switching them back to Full recovery. No further corruption / warnings since we turned off CBT.
VMware's got a massive problem on their hands and I wish they'd hurry up and fix it!
joergr wrote:I posted it to vSphere ESXi 6 community this morning - https://communities.vmware.com/message/2506025#2506025
NightBird wrote:You think that it is a Veeam B&R 8 Update 2 bug or vSphere 6 bug ?
Users browsing this forum: Bing [Bot] and 18 guests