Maintenance Window & Log backup Overdue

Rhys

Hi,

I recently upgraded to 2.2 to implement a maintenance window from 4:10AM - 6:10AM to get rid of a few alerts about overdue log backups.

We backup our logs hourly apart from 5AM where a full backup occurs. I still get these alerts raise at 6:10AM and then immediatly closed.

On the alert Time Raise = 1 Mar 2011 6:10 AM, Time closed = 1 Mar 2011 6:10 AM and also it states the last log backup as "Last log or full database backup before this alert was raised was at 1 Mar 2011 6:00 AM".

Since I have configure this alert for Low > 2 hours I shouldn't be seeing these.

Cheers,

Rhys

priyasinha

Hi Rhys,

Thanks for your post. I will investigate this. In the meanwhile, what time zone is your base monitor and monitored entity?

Thanks,
Priya

Rhys

Hi Prita,

Thanks for the speedy response. One is UTC the other is GMT (I trust my domain admins too much!).

I'll get this corrected and see if it happens tomorrow. Didn't think of this as the alert is raise then immediately closed.

Cheers,

Rhys

Edit: looks like this isn't an issue http://answers.microsoft.com/en-us/wind ... 19a0673bf7

priyasinha

Hi Rhys,

Thanks for this. I can confirm that this is bug. I have been able to reproduce your issue. I have logged this as SRP-3586. This will get fixed in 2.3 release.

Thanks a lot for reporting this.

Regards,
Priya

priyasinha

Rhys wrote:

Hi,

I recently upgraded to 2.2 to implement a maintenance window from 4:10AM - 6:10AM to get rid of a few alerts about overdue log backups.

We backup our logs hourly apart from 5AM where a full backup occurs. I still get these alerts raise at 6:10AM and then immediatly closed.

On the alert Time Raise = 1 Mar 2011 6:10 AM, Time closed = 1 Mar 2011 6:10 AM and also it states the last log backup as "Last log or full database backup before this alert was raised was at 1 Mar 2011 6:00 AM".

Since I have configure this alert for Low > 2 hours I shouldn't be seeing these.

Cheers,

Rhys

Hi Rhys,

Just a quick line to say that this bug has been fixed in 2.3 release.

Regards,
Priya