New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Error when a backup happens Exchange DAG Sensor 'Content Index State'

Votes:

0

Your Vote:

Up

Down

Every hour we take a backup of our Exchange Servers and when these backups happen PRTG sends out alerts : Down Last Message: Error by lookup value 'Error' in channel 'Content Index State' This is part of the Exchange Database DAG sensor - channel called Content Index State.

How do I make this sensor stop firing every hour when a backup happens? I have changed the Content Index State - Unit from 8 to 16, but I am not sure what this is changing so I didn't want to increase it more. Yes, when a backup happens it stuns the EDBs for a second - so I need to increase the monitoring time or something to get these false positive error messages to stop. Any suggestions?

content error-messages exchange-database-dag

Created on Jul 23, 2018 9:18:31 PM by  kora44 (0) 1



9 Replies

Votes:

0

Your Vote:

Up

Down

Hello there,

For "Content Index State" the sensor uses a lookup called "prtg.standardlookups.exchangedag.contentindexstate.ovl" which expects one of the following values and acts accordingly to them:

<Lookups> <singleInt state="Ok" value="0"> Healthy </singleInt> <singleInt state="Warning" value="1"> Crawling </singleInt> <singleInt state="Error" value="2"> Error </singleInt> </Lookups>

It would be possible to replace the lookup with an adjusted one that does not turn the sensor into error at all when index state is being reported as "error", but I'm not sure that's really what you want.

The easiest approach would be trying a higher scanning interval, hoping the sensor does not scan then while the backup is being performed.

Another approach would be creating a schedule for the sensor that pauses it when the backup is being performed. though this makes only sense when the backup is performed around the same time in order to define the schedule accordingly.

Kind regards,

Erhard

Created on Jul 24, 2018 11:21:19 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Scheduling would work - but your scheduling is not that granular. My backups happen every hour on the hour and are done within 5 minutes. But your scheduling turns off for the full hour. I will increase the scanning interval to 4 minutes and see if this fixes the issue.

Created on Jul 24, 2018 4:28:25 PM by  kora44 (0) 1



Votes:

0

Your Vote:

Up

Down

You can configure schedules that granular by enabling Use list of period definitions in the schedule's settings. You need to be aware though that when doing so, the schedule is not following your PRTG user's timezone setting but the PRTG sever's local system time then.

Created on Jul 25, 2018 6:33:24 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

we are experiencing the same issue with Exchange 2016.

After some troubleshooting we have seen that MSExchangeFastSearch Stops and Starts indexing about once every hour and I feel that it might be that issue that you are seeing and not Database freeze.

Could you confirm if you see Event ID 1008 (The indexing has stopped successfully for mailbox database X) followed by 1007 (The indexing has started successfully for mailbox database X). If you look in c:\Program Files\Microsoft\Exchange Server\V15\Logging\Search\ and Search_DATE-1.log you can see the status go to Failed and then back to Healthy. It takes about 30s for us (barely any active mailboxes as we have not started migrating) and if PRTG monitors during that period we get alarms.

I have not looked at older logs so I am not sure if it started with CU10 or was present before. Unfortunately I have no 2013 or 2016 installation to compare with.

I have an open case with Microsoft at the moment to see if we can get some clarity.

Best regards, Mikael Norman

Created on Sep 3, 2018 11:49:03 AM by  Mikael Norman (0)



Votes:

0

Your Vote:

Up

Down

Hi Mikael,

That is an interesting find, please post an update here in case you find out anything else or get more details from MS about it, we would appreciate it.

Kind regards,

Erhard

Created on Sep 3, 2018 6:42:45 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Erhard,

the technician is more focused on the Content Index and the health but as it is healthy as soon as the Indexing has started once again there really is no problem with the Index.

I do not know exactly where to log a case regarding getting an explanation of the behavior of Exchange in this case and the impact it has on our monitoring. Any one else have a good contact with Microsoft? I can provide logs and more if needed.

Best regards, Mikael

Created on Sep 5, 2018 6:42:25 AM by  Mikael Norman (0)



Votes:

0

Your Vote:

Up

Down

Hi Mikael,

Apologies for the late reply. I was waiting for feedback from the developers. They also have no other recommendation besides using schedules to pause the sensor during that period. In the end, when the target reports this status back, the sensor will interpret it as such as reported by the device, so there's not much we can do on our end, I'm afraid.

Kind regards,

Erhard

Created on Sep 13, 2018 7:36:31 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, we got the same error very often on one of our 4 replicated Exchange servers.

Date: 19.03.2019 08:14:02

Device: XXXMEX01 Sensor: Exchange Database DAG: XXX_DB034 (Exchange Database DAG (PowerShell))

Some messages come at the same time when our backup is running, but some not. And it´s just the one server, no message by the other 3.

I changed the Scanning Interval for this server up to 5 minutes and set sensor to warning for 2 Intervals.

Is there really nothing I can do?

Created on Mar 19, 2019 7:28:46 AM by  Ysuran (0)



Votes:

0

Your Vote:

Up

Down

Hello Ysuran,

Currently there's nothing else we could recommend, I'm afraid.

Kind regards,

Erhard

Created on Mar 19, 2019 1:16:12 PM by  Erhard Mikulik [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.