Browse Prior Art Database

Method and System for Optimal Maintenance Application to a Business Service Through Aggregated Maintenance Windows Disclosure Number: IPCOM000238649D
Publication Date: 2014-Sep-09
Document File: 7 page(s) / 48K

Publishing Venue

The Prior Art Database


Method and System for optimal maintenance application to a business service through aggregated maintenance windows.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 15% of the total text.

Page 01 of 7

Method and System for Optimal Maintenance Application to a Business Service Through Aggregated Maintenance Windows

When customers have to take production servers offline to apply software maintenance it's important that they minimize downtime so they can get the servers back online as soon as

possible in order to reduce disruption to the business services they support.

Defining and managing the most optimal maintenance windows for servers and business services is not an easy task. This invention provides a methodology for defining maintenance windows for servers and groups of servers that support a business service and a system that can automatically coordinate performing maintenance on these servers in the most optimal and efficient manner to keep the servers and the business services they support healthy during their

production hours.

By combining data from multiple sources the automated decision making on whether a patch should be applied is automatically derived resulting in the most optimal outcome of maintenance application. For example, the system can look at situations such as maintenance windows from each server, the maintenance window from the business services the servers support, historical analytics on the amount of time it takes to apply specific maintenance patches, that there is no critical pending operations to complete in the business system, information from events or other sources that the business service is not already in a dysfunctional/crippled state, and information on how to get the business service back into a running state. User input is not needed to recover from situations where patch application is not completed during the initial maintenance window, remaining patches will be automatically applied during subsequent maintenance windows. The business service will always be left in a fully functional state at the end of a given maintenance window.

Other automation solutions that manage maintenance windows and applying maintenance to servers and business services do not take into account the complete problem of dealing with groups of servers that support a business service, applying maintenance on servers in the correct order, and handling partial or complete rollback of maintenance to leave a business service in a working state if all planned maintenance cannot be applied during a maintenance window for a business service. Customers typically manage these dependencies and maintenance application/rollback activities manually which is very labor and planning intensive, so an automated solution to ensure the servers and overall business service are left in a 'running' state at the end of the maintenance window would provide a significant customer benefit.

The optimal definition of maintenance window specification can include maintenance windows on individual servers as well as across servers that support a business service. In this case of multiple servers supporting a business service it's important that...