When activating a policy individually or in bulk one of the required settings is Threshold. The way we leverage thresholds is in days.
0 or 1 = 1 Day
0.5 = 1/2 Day
1.5 = 1 1/2 Day
2 = 2 Days
A zero or 1 day threshold means that we are expecting results within the last 24 hours and if we don't receive them we will mark this policy as a No Result. This is our way of accounting for the scenarios where a job didn't send in an email or perhaps something went wrong with the reporting function on the backup job.
Examples of when to extend the threshold:
Example 1: If a backup takes longer than a 24 hour period to run due to the size of data. In this case you may opt to set the threshold to 1.5 or 2 days.
Example 2: You have a workstation backup that you may not want to report every failure on and so you can increase the threshold. Some of our customers don't want to be notified every day if their backup fails so we adjust the threshold to something acceptable for them. It is usually best practice to make sure the client signs off on a change that could impact recover-ability. In some cases we set these to 7 days for our workstations.
During the period when you extend a backup the system will show it as a warning instead of a failure or no result.
If you use a threshold such as 1.5 days but you want to know if a backup fails immediately during that time you can select "Alert on Failure" and set the system to generate a ticket or send an email notification. Make sure the grouping setting highlighted in the screenshot below matches your grouping settings for your normal scheduled tickets. (Policy is the same as grouping being turned off)