Veeam B+R and Exchange 2013

[jhowlett]

Hi All,

We are currently backing up our local Exchange server using B+R 9.5 using the best practices (Perform Copy only) (Run in high priority) and from Veeam's point of view all looks well, backups complete with no errors.

A few days ago we noticed some errors on the Exchange 2013 server in the way of corruption to the "indexes" and was wondering if Veeam could be causing this?

There is no direct link but adding Veeam backups to the Exchange server has been the only change in a long while.

Has anyone seen anything similiar to this?

We just want to rule out the possibilities.

[jhowlett]

I am taking the Silence as a good thing

[veremin]

Can you provide us with the exact errors reported?

We haven't seen anything similar before, and if Veeam were the true cause of Exchange corruption, we would have been swamped with tons of complains already.

Thanks!

[jhowlett]

Here is a log snippet

Code: Select all

Log Name:      Application
Source:        MSExchangeFastSearch
Date:          08/04/2019 17:30:26
Event ID:      1009
Task Category: (1)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Mailserver
Description:
The description for Event ID 1009 from source MSExchangeFastSearch cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

MailServer
Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedForCorruptionException: "Feeding was skipped for '9f38were-331a-4d3f-ae7f-d2cf931bccce (MailServer)' due to the state 'Failed', error code: 'CatalogCorruption', failure code: '4321345', failure reason: 'Journal has been detected as invalid.'."
   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()
   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)
   

[foggy]

Doesn't look like it is caused by Veeam B&R. Is this Exchange Server fully patched? Have you tried to re-create the search index (stop the search services, delete the search index folder and start the services back)?

[jhowlett]

That is the next step

It looks like it could have been caused by a windows update which we are looking into.

Thank you all for your responses, looks like Veeam is squeeky clean!