Patent Application
20090171703
This invention relates, in general, to managing customer environments to provide support for business resiliency, and in particular, to provide customers with the ability to employ multiple levels of state assessment to manage the environment.
Today, customers attempt to manually manage and align their availability management with their information technology (IT) infrastructure. Changes in either business needs or the underlying infrastructure are often not captured in a timely manner and require considerable rework, leading to an inflexible environment.
Often high availability solutions and disaster recovery technologies are handled via a number of disparate point products that target specific scopes of failure, platforms or applications. Integrating these solutions into an end-to-end solution is a complex task left to the customer, with results being either proprietary and very specific, or unsuccessful.
Customers do not have the tools and infrastructure in place to customize their availability management infrastructure to respond to failures in a way that allows for a more graceful degradation of their environments. As a result, more drastic and costly actions may be taken (such as a site switch) when other options (such as disabling a set of applications or users) could have been offered, depending on business needs.
Coordination across availability management and other systems management disciplines is either nonexistent or accomplished via non-reusable, proprietary, custom technology.
There is little predictability as to whether the desired recovery objective will be achieved, prior to time of failure. There are only manual, labor intensive techniques to connect recovery actions with the business impact of failures and degradations.
Any change in the underlying application, technologies, business recovery objectives, resources or their interrelationships require a manual assessment of impact to the hand-crafted recovery scheme.
Based on the foregoing, a need exists for a capability that enables customers to facilitate management of their environment. For instance, a need exists for a capability that allows customers to determine the sensitivity of events, in the context of a set of business applications, and to use that information to manage their environment. A need exists for a capability that provides customers with the ability to dynamically evaluate the state of resources in its environment and to use that state to manage its resources. A further need exists for a capability that provides customers with the ability to dynamically evaluate an aggregated state of a business application and to use that state to manage the application.
The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a computer-implemented method to assess state. The computer-implemented method includes, for instance, identifying an information technology (IT) component for which state is to be assessed; and dynamically assessing state for the IT component based on one or more defined rules and one or more environment conditions, the one or more environment conditions having real-time values associated therewith which are employed in the dynamically assessing.
Computer program products and systems relating to one or more aspects of the present invention are also described and claimed herein.
Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention.
One or more aspects of the present invention are particularly pointed out and distinctly claimed as examples in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
In managing a customer's environment, such as its business environment, there is a set of requirements unaddressed by existing technology, which causes unpredictable down time, large impact failures and recoveries, and significant extra labor cost, with resulting loss of business revenue. These requirements include, for instance:
The above set of requirements is addressed, however, by a Business Resiliency (BR) Management System, of which one or more aspects of the present invention are included. The Business Resiliency Management System provides, for instance:
One goal of the BR system is to allow customers to align their supporting information technology systems with their business goals for handling failures of various scopes, and to offer a continuum of recovery services from finer grained process failures to broader scoped site outages. The BR system is built around the idea of identifying the components that constitute a business function, and identifying successive levels of recovery that lead to more complex constructs as the solution evolves. The various recovery options are connected by an overall BR management capability that is driven by policy controls.
Various characteristics of one embodiment of a BR system include:
A Business Resilience System is capable of being incorporated in and used by many types of environments. One example of a processing environment to incorporate and use aspects of a BR system, including one or more aspects of the present invention, is described with reference to
Processing environment 100 includes, for instance, a central processing unit (CPU) 102 coupled to memory 104 and executing an operating system 106. Examples of operating systems include AIX® and z/OS®, offered by International Business Machines Corporation; Linux; etc. AIX® and z/OS® are registered trademarks of International Business Machines Corporation, Armonk, N.Y., U.S.A. Other names used herein may be registered trademarks, trademarks or product names of International Business Machines Corporation or other companies.
The operating system manages execution of a Business Resilience Runtime Component 108 of a Business Resilience System, described herein, and one or more applications 110 of an application container 112.
As examples, processing environment 100 includes an IBM® System z™ processor or a pSeries® server offered by International Business Machines Corporation; a Linux server; or other servers, processors, etc. Processing environment 100 may include more, less and/or different components than described herein. (pSeries® is a registered trademark of International Business Machines Corporation, Armonk, N.Y., USA.)
Another example of a processing environment to incorporate and use aspects of a BR System, including one or more aspects of the present invention, is described with reference to
As shown, a processing environment 200 includes for instance, a central processing complex 202 coupled to an input/output (I/O) subsystem 204. Central processing complex 202 includes, for instance, a central processing unit 206, memory 208, an operating system 210, a database management system 212, a Business Resilience Runtime Component 214, an application container 216 including one or more applications 218, and an I/O facility 220.
I/O facility 220 couples central processing complex 202 to I/O subsystem 204 via, for example, a dynamic switch 230. Dynamic switch 230 is coupled to a control unit 232, which is further coupled to one or more I/O devices 234, such as one or more direct access storage devices (DASD).
Processing environments 100 and/or 200 may include, in other embodiments, more, less and/or different components.
In yet another embodiment, a central processing complex 300 (
For example, network service 302 of central processing complex 300 is coupled to a switch 308 of network subsystem 306. Switch 308 is coupled to a switch 310 via routers 312 and firewalls 314. Switch 310 is further coupled to a network service 316 of processing environment 304.
Processing environment 304 further includes, for instance, a central processing unit 320, a memory 322, an operating system 324, and an application container 326 including one or more applications 328. In other embodiments, it can include more, less and/or different components.
Moreover, CPC 300 further includes, in one embodiment, a central processing unit 330, a memory 332, an operating system 334, a database management system 336, a Business Resilience Runtime Component 338, an application container 340 including one or more applications 342, and an I/O facility 344. It also may include more, less and/or different components.
I/O facility 344 is coupled to a dynamic switch 346 of an I/O subsystem 347. Dynamic switch 346 is further coupled to a control unit 348, which is coupled to one or more I/O devices 350.
Although examples of various environments are provided herein, these are only examples. Many variations to the above environments are possible and are considered within the scope of the present invention.
In the above-described environments, a Business Resilience Runtime Component of a Business Resilience System is included. Further details associated with a Business Resilience Runtime Component and a Business Resilience System are described with reference to
In one example, a Business Resilience System 400 is a component that represents the management of recovery operations and configurations across an IT environment. Within that Business Resilience System, there is a Business Resilience Runtime Component (402) that represents the management functionality across multiple distinct Recovery Segments, and provides the service level automation and the support of creation of the recovery sequences. In addition, there are user interface (404), administration (406), installation (408) and configuration template (410) components within the Business Resilience System that enable the administrative operations that are to be performed. Each of these components is described in further detail below.
Business Resilience Runtime Component 402 includes a plurality of components of the BR System that are directly responsible for the collection of observations, creation of PSEs, policy acceptance, validation, error detection, and formulation of recovery sequences. As one example, Business Resilience Runtime Component 402 includes the following components:
In addition to the Business Resilience Runtime Component of the BR system, the BR system includes the following components, previously mentioned above.
The user interface, admin mailbox, install logic and/or template components can be part of the same computing unit executing BR Runtime or executed on one or more other distributed computing units.
To further understand the use of some of the above components and their interrelationships, the following example is offered. This example is only offered for clarification purposes and is not meant to be limiting in any way.
Referring to
As a result of these conditions leading up to runtime, the following subscriptions have already taken place:
These steps highlight one example of an error detection process:
In addition to the above, BR includes a set of design points that help in the understanding of the system. These design points include, for instance:
BR is targeted towards goal based policies—the customer configures his target availability goal, and BR determines the preparatory actions and recovery actions to achieve that goal (e.g., automatically).
Availability management of the IT infrastructure through goal based policy is introduced by this design. The BR system includes the ability to author and associate goal based availability policy with the resource Recovery Segments described herein. In addition, support is provided to decompose the goal policy into configuration settings, preparatory actions and runtime procedures in order to execute against the deployed availability goal. In one implementation of the BR system, the Recovery Time Objective (RTO—time to recover post outage) is a supported goal policy. Additional goal policies of data currency (e.g., Recovery Point Objective) and downtime maximums, as well as others, can also be implemented with the BR system. Recovery Segments provide the context for association of goal based availability policies, and are the scope for goal policy expression supported in the BR design. The BR system manages the RTO through an understanding of historical information, metrics, recovery time formulas (if available), and actions that affect the recovery time for IT resources.
RTO goals are specified by the customer at a Recovery Segment level and apportioned to the various component resources grouped within the RS. In one example, RTO goals are expressed as units of time intervals, such as seconds, minutes, and hours. Each RS can have one RTO goal per Pattern System Environment associated with the RS. Based on the metrics available from the IT resources, and based on observed history and/or data from the customer, the RTO goal associated with the RS is evaluated for achievability, taking into account which resources are able to be recovered in parallel.
Based on the RTO for the RS, a set of preparatory actions expressed as a workflow is generated. This preparatory workflow configures the environment or makes alterations in the current configuration, to achieve the RTO goal or to attempt to achieve the goal.
In terms of optimizing RTO, there are tradeoffs associated with the choices that are possible for preparatory and recovery actions. Optimization of recovery choice is performed by BR, and may include interaction at various levels of sophistication with IT resources. In some cases, BR may set specific configuration parameters that are surfaced by the IT resource to align with the stated RTO. In other cases, BR may request that an IT resource itself alter its management functions to achieve some portion of the overall RS RTO. In either case, BR aligns availability management of the IT resources contained in the RS with the stated RTO.
In this design, as one example, there is an approach to collecting the required or desired metrics data, both observed and key varying factors, system profile information that is slow or non-moving, as well as potential formulas that reflect a specific resource's use of the key factors in assessing and performing recovery and preparatory actions, historical data and system information. The information and raw metrics that BR uses to perform analysis and RTO projections are expressed as part of the IT resources, as resource properties. BR specific interpretations and results of statistical analysis of key factors correlated to recovery time are kept as BR Specific Management data (BRMD).
BR maintains specific information about the BR management of each resource pairing or relationship between resources. Information regarding the BR specific data for a resource pairing is kept by BR, including information such as ordering of operations across resources, impact assessment information, operation effect on availability state, constraint analysis of actions to be performed, effects of preparatory actions on resources, and requirements for resources to co-locate or anti-co-locate.
One feature of the BR function is the ability to identify the scope and impact of a failure. The BR design uses a Containment Region to identify the resources affected by an incident. The Containment Region is initially formed with a fairly tight restriction on the scope of impact, but is expanded on receiving errors related to the first incident. The impact and scope of the failure is evaluated by traversing the resource relationships, evaluating information on BR specific resource pairing information, and determining most current state of the resources impacted.
Various types of preparatory and recovery processes are formulated and in some cases, optionally initiated. Workflows used by BR are dynamically generated based on, for instance, customer requirements for RTO goal, based on actual scope of failure, and based on any configuration settings customers have set for the BR system.
A workflow includes one or more operations to be performed, such as Start CICS, etc. Each operation takes time to execute and this amount of time is learned based on execution of the workflows, based on historical data in the observation log or from customer specification of execution time for operations. The workflows formalize, in a machine readable, machine editable form, the operations to be performed.
In one example, the processes are generated into Business Process Execution Language (BPEL) compliant workflows with activities that are operations on IT resources or specified manual, human activities. For example, BRM automatically generates the workflows in BPEL. This automatic generation includes invoking routines to insert activities to build the workflow, or forming the activities and building the XML (Extensible Mark-Up Language). Since these workflows are BPEL standard compliant, they can be integrated with other BPEL defined workflows which may incorporate manual activities performed by the operations staff. These BR related workflows are categorized as follows, in one example:
Since the set of BR actions described above modify existing IT environments, visibility to the actions that are taken by BR prior to the actual execution is provided. To gain trust in the decisions and recommendations produced by BR, the BR System can run in ‘advisory mode’. As part of advisory mode, the possible actions that would be taken are constructed into a workflow, similar to what would be done to actually execute the processes. The workflows are then made visible through standard workflow authoring tooling for customers to inspect or modify. Examples of BPEL tooling include:
BR tooling spans the availability management lifecycle from definition of business objectives, IT resource selection, availability policy authoring and deployment, development and deployment of runtime monitors, etc. In one example, support for the following is captured in the tooling environment for the BR system:
The policy lifecycle for BR goal policies, such as RTO goals, includes, for example:
One of the points in determining operational state of a Recovery Segment is that this design allows for customers to configure a definition of specific ‘aggregated’ states, using properties of individual IT resources. A Recovery Segment is an availability management context, in one example, which may include a diverse set of IT resources.
The customer may provide the rules logic used within the Recovery Segment to consume the relevant IT resource properties and determine the overall state of the RS (available, degraded and unavailable, etc). The customer can develop and deploy these rules as part of the Recovery Segment availability policy. For example, if there is a database included in the Recovery Segment, along with the supporting operating system, storage, and network resources, a customer may configure one set of rules that requires that the database must have completed the recovery of in-flight work in order to consider the overall Recovery Segment available. As another example, customers may choose to configure a definition of availability based on transaction rate metrics for a database, so that if the rate falls below some value, the RS is considered unavailable or degraded, and evaluation of ‘failure’ impact will be triggered within the BR system. Using these configurations, customers can tailor both the definitions of availability, as well as the rapidity with which problems are detected, since any IT resource property can be used as input to the aggregation, not just the operational state of IT resources.
Failures occurring during sequences of operations executed within a BPEL compliant process workflow are intended to be handled through use of BPEL declared compensation actions, associated with the workflow activities that took a failure. The BR System creates associated “undo” workflows that are then submitted to compensate, and reset the environment to a stable state, based on where in the workflow the failure occurred.
The following set of customer values, as examples, are derived from the BR system functions described above, listed here with supporting technologies from the BR system:
Management of the IT environment is adaptively performed, as described herein and in a U.S. patent application “Adaptive Business Resiliency Computer System for Information Technology Environments,” (POU920070364US1), Bobak et al., co-filed herewith, which is hereby incorporated herein by reference in its entirety.
Many different sequences of activities can be undertaken in creating a BR environment. The following represents one possible sequence; however, many other sequences are possible. This sequence is provided merely to facilitate an understanding of a BR system and one or more aspects of the present invention. This sequence is not meant to be limiting in any way. In the following description, reference is made to various U.S. patent applications, which are co-filed herewith.
On receiving the BR and related product offerings, an installation process is undertaken. Subsequent to installation of the products, a BR administrator may define the configuration for BR manager instances with the aid of BRM configuration templates.
Having defined the BRM configuration a next step could be to define Recovery Segments as described in “Recovery Segments for Computer Business Applications,” (POU920070108US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Definition of a RS may use a representation of resources in a topology graph as described in “Use of Graphs in Managing Computing Environments,” (POU920070112 US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
It is expected that customers will enable BR operation in “observation” mode for a period of time to gather information regarding key metrics and operation execution duration associated with resources in a RS.
At some point, sufficient observation data will have been gathered or a customer may have sufficient knowledge of the environment to be managed by BR. A series of activities may then be undertaken to prepare the RS for availability management by BR. As one example, the following steps may be performed iteratively.
A set of functionally equivalent resources may be defined as described in “Use of Redundancy Groups in Runtime Computer Management of Business Applications,” (POU920070113 US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Specification of the availability state for individual resources, redundancy groups and Recovery Segments may be performed, as described herein, in accordance with one or more aspects of the present invention.
Representations for the IT environment in which BR is to operate may be created from historical information captured during observation mode, as described in “Computer Pattern System Environment Supporting Business Resiliency,” (POU920070107US1), Bobak et al., which is hereby incorporated herein by reference in its entirety. These definitions provide the context for understanding how long it takes to perform operations which change the configuration—especially during recovery periods.
Information on relationships between resources may be specified based on recommended best practices—expressed in templates—or based on customer knowledge of their IT environment as described in “Conditional Computer Runtime Control of an Information Technology Environment Based on Pairing Constructs,” (POU920070110US1), Bobak et al., which is hereby incorporated herein by reference in its entirety. Pairing processing provides the mechanism for reflecting required or desired order of execution for operations, the impact of state change for one resource on another, the effect execution of an operation is expected to have on a resource state, desire to have one subsystem located on the same system as another and the effect an operation has on preparing the environment for availability management.
With preliminary definitions in place, a next activity of the BR administrator might be to define the goals for availability of the business application represented by a Recovery Segment as described in “Programmatic Validation in an Information Technology Environment,” (POU920070111US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Managing the IT environment to meet availability goals includes having the BR system prioritize internal operations. The mechanism utilized to achieve the prioritization is described in “Serialization in Computer Management,” (POU920070105US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Multiple operations are performed to prepare an IT environment to meet a business application's availability goal or to perform recovery when a failure occurs. The BR system creates workflows to achieve the required or desired ordering of operations, as described in “Dynamic Generation of Processes in Computing Environments,” (POU920070123 US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
A next activity in achieving a BR environment might be execution of the ordered set of operations used to prepare the IT environment, as described in “Dynamic Selection of Actions in an Information Technology Environment,” (POU920070117US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Management by BR to achieve availability goals may be initiated, which may initiate or continue monitoring of resources to detect changes in their operational state, as described in “Real-Time Information Technology Environments,” (POU920070120US1), Bobak et al., which is hereby incorporated herein by reference in its entirety. Monitoring of resources may have already been initiated as a result of “observation” mode processing.
Changes in resource or redundancy group state may result in impacting the availability of a business application represented by a Recovery Segment. Analysis of the environment following an error is performed. The analysis allows sufficient time for related errors to be reported, insures gathering of resource state completes in a timely manner and insures sufficient time is provided for building and executing the recovery operations—all within the recovery time goal, as described in “Management Based on Computer Dynamically Adjusted Discrete Phases of Event Correlation,” (POU920070119US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
A mechanism is provided for determining if events impacting the availability of the IT environment are related, and if so, aggregating the failures to optimally scope the outage, as described in “Management of Computer Events in a Computer Environment,” (POU920070118US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Ideally, current resource state can be gathered after scoping of a failure. However, provisions are made to insure management to the availability goal is achievable in the presence of non-responsive components in the IT environment, as described in “Managing the Computer Collection of Information in an Information Technology Environment,” (POU920070121US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
With the outage scoped and current resource state evaluated, the BR environment can formulate an optimized recovery set of operations to meet the availability goal, as described in “Defining a Computer Recovery Process that Matches the Scope of Outage,” (POU920070124US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Formulation of a recovery plan is to uphold customer specification regarding the impact recovery operations can have between different business applications, as described in “Managing Execution Within a Computing Environment,” (POU920070115US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Varying levels of recovery capability exist with resources used to support a business application. Some resources possess the ability to perform detailed recovery actions while others do not. For resources capable of performing recovery operations, the BR system provides for delegation of recovery if the resource is not shared by two or more business applications, as described in “Conditional Actions Based on Runtime Conditions of a Computer System Environment,” (POU920070116US1), Bobak et al, which is hereby incorporated herein by reference in its entirety.
Having evaluated the outage and formulated a set of recovery operations, the BR system resumes monitoring for subsequent changes to the IT environment.
In support of mainline BR system operation, there are a number of activities including, for instance:
In order to build a BR environment that meets recovery time objectives, IT configurations within a customer's location are to be characterized and knowledge about the duration of execution for recovery time operations within those configurations is to be gained. IT configurations and the durations for operation execution vary by time, constituent resources, quantity and quality of application invocations, as examples. Customer environments vary widely in configuration of IT resources in support of business applications. Understanding the customer environment and the duration of operations within those environments aids in insuring a Recovery Time Objective is achievable and in building workflows to alter the customer configuration of IT resources in advance of a failure and/or when a failure occurs.
A characterization of IT configurations within a customer location is built by having knowledge of the key recovery time characteristics for individual resources (i.e., the resources that are part of the IT configuration being managed; also referred to as managed resources). Utilizing the representation for a resource, a set of key recovery time objective (RTO) metrics are specified by the resource owner. During ongoing operations, the BR manager gathers values for these key RTO metrics and gathers timings for the operations that are used to alter the configuration. It is expected that customers will run the BR function in “observation” mode prior to having provided a BR policy for availability management or other management. While executing in “observation” mode, the BR manager periodically gathers RTO metrics and operation execution durations from resource representations. The key RTO metrics properties, associated values and operation execution times are recorded in an Observation log for later analysis through tooling. Key RTO metrics and operation execution timings continue to be gathered during active BR policy management in order to maintain currency and iteratively refine data used to characterize customer IT configurations and operation timings within those configurations.
Examples of RTO properties and value range information by resource type are provided in the below table. It will be apparent to those skilled in the art that additional, less, and/or different resource types, properties and/or value ranges may be provided.
A specific example of key RTO properties for a z/OS® image is depicted in
The z/OS® image has a set of RTO metrics associated therewith, as described above. Other resources may also have its own set of metrics. An example of this is depicted in
Further, in one example, the RTO properties from each of the resources that are part of the Recovery Segment for App A have been gathered by BR and formed into an “observation” for recording to the Observation log, as depicted at 850.
Resources have varying degrees of functionality to support RTO goal policy. Such capacity is evaluated by BR, and expressed in resource property RTOGoalCapability in the BRMD entry for the resource. Two options for BR to receive information operation execution timings are: use of historical data or use of explicitly customer configured data. If BR relies on historical data to make recovery time projections, then before a statistically meaningful set of data is collected, this resource is not capable of supporting goal policy. A mix of resources can appear in a given RS—some have a set of observations that allow classification of the operation execution times, and others are explicitly configured by the customer.
Calculation of projected recovery time can be accomplished in two ways, depending on customer choice: use of historical observations or use of customers input timings. The following is an example of values for the RTOGoalCapability metadata that is found in the BRMD entry for the resource that indicates this choice:
If the customer is in observation mode, then historical information is captured, regardless of whether the customer has indicated use of explicitly input timings or use of historical information.
The administrator can alter, on a resource basis, which set of timings BR is to use. The default is to use historical observations. In particular, a change source of resource timing logic is provided that alters the source that BR uses to retrieve resource timings. The two options for retrieving timings are from observed histories or explicitly from admin defined times for operation execution. The default uses information from the observed histories, gathered from periodic polls. If the customer defines times explicitly, the customer can direct BR to use those times for a given resource. If activated, observation mode continues and captures information, as well as running averages, and standard deviations. The impact to this logic is to alter the source of information for policy validation and formulation of recovery plan.
With respect to the historical observations, there may be a statistically meaningful set of observations to verify. The sample size should be large enough so that a time range for each operation execution can be calculated, with a sufficient confidence interval. The acceptable number of observations to qualify as statistically meaningful, and the desired confidence interval are customer configurable using BR UI, but provided as defaults in the BRMD entry for the resource. The default confidence interval is 95%, in one example.
There are metrics from a resource that are employed by BR to enable and perform goal management. These include, for instance:
There is also a set of information about the resource that is employed—this information is provided as defaults in the BRMD entry for the resource, but provided to the BR team in the form of best practices information/defaults by the domain owners:
In addition to the resources defined herein as part of the IT configuration that is managed, there are other resources, referred to herein as assessed resources. Assessed resources are present primarily to provide observation data for PSE formation, and to understand impact(s) on managed resources. They do not have a decomposed RTO associated with them nor are they acted on for availability by BR. Assessed resources have the following characteristics, as examples:
Similarly, there are likely scenarios where a resource exists in a customer environment that already has an alternative availability management solution, and does not require BR for its availability. However, since other resources that are managed by BR may be dependent on them, they are observed and assessed in order to collect observation data and understand their impacts on managed resources. Additionally, there may be resources that do not have alternative management solutions, but the customer simply does not want them managed by BR, but other managed resources are dependent upon them. They too are classified as assessed resources.
These assessed resources share many of the same characteristics of managed resources, such as, for example:
Finally, there are a few restrictions that BR imposes upon assessed resources, in this embodiment:
To facilitate the building of the customer's IT configuration, observations regarding the customer's environment are gathered and stored in an observation log. In particular, the observation log is used to store observations gathered during runtime in customer environments, where each observation is a collection of various data points. They are created for each of the Recovery Segments that are in “observation” mode. These observations are used for numerous runtime and administrative purposes in the BR environment. As examples the observations are used:
BR gathers observations during runtime when “observation mode” is enabled at the Recovery Segment level. There are two means for enabling observation mode, as examples:
The administrator may also disable observation mode for a Recovery Segment, which stops it from polling for data and creating subsequent observation records for insertion in the log. However, the accumulated observation log is not deleted. In one example, an RS remains in observation mode throughout its lifecycle. The UI displays the implications of disabling observation mode.
In BR, the observations that are collected by BR during runtime can be grouped into two categories, as examples:
A periodic poll observation is a point-in-time snapshot of the constituent resources in a Recovery Segment. Observation data points are collected for those resources in the Recovery Segment(s) which have associated BR management data for any of the following reasons, as examples:
The full value of these observations is derived for an RS when they include data that has been gathered for its constituent resources, plus the resources that those are dependent upon. In one embodiment, the administrator is not forced to include all dependent resources when defining a Recovery Segment, and even if that were the case, there is nothing that prevents them from deleting various dependent resources. When defining a Recovery Segment, the BR UI provides an option that allows the customer to display the dependency graph for those resources already in the Recovery Segment. This displays the topology from the seed node(s) in the Recovery Segment down to and including the dependent leaf nodes. The purpose of this capability is to give the customer the opportunity to display the dependent nodes and recommend that they be included in the Recovery Segment.
Preparatory and recovery workflows are built by the BR manager to achieve the customer requested RTO policy based on resource operations timings. During active policy monitoring by the BR manager, measurements of achieved time for operations are recorded in observations to the log and used to maintain the running statistical data on operation execution times. Observations written to the log may vary in the contained resource RTO metrics and operation execution timings.
Observations are also collected from any of the BPEL workflows created by BR in the customer's environment. There is a standard template that each BR BPEL workflow uses. As part of that template, observation data is captured at the start of, during, and at the completion of each workflow. Specifically, in one example, one observation is created at the end of the workflow with data accumulated from completion of each activity. This information is used to gather timings for workflow execution for use in creating subsequent workflows at time of failure.
In accordance with an aspect of the present invention, management of a BR environment is facilitated by enabling customers (or users, etc.) to determine the sensitivity of events on resources, dynamically evaluate composed state of those resources, based on the sensitivity, and manage the environment based on the state. Further, in accordance with another aspect of the present invention, management of a BR environment is facilitated by enabling customers to dynamically evaluate aggregated state of business applications and to use that state to manage the environment.
In complex IT environments, changes in operational state of resources are often detected after significant problems are already occurring in the environment due to a static definition of the terms that constitute ‘resource operational’. Allowing customers to determine the sensitivity of detection of events that degrade or fail resources, in the context of a set of business applications, is useful in managing the environment. For example, one customer may require that any slight degradation of the transaction system associated with its trading application be considered a potential impact to the business application as a whole, if it occurs during the organization's prime trading hours. The customer may further require that this degradation be detected, alternate actions recommended or even taken, to prevent an actual outage of the transaction system. In addition, the customer may also require that for other business applications deemed less critical to the business, only resource outages should impact the overall availability state of the application during these critical trade times.
The above example shows the value of detecting resource characteristics in addition to the typical ‘operational state’ of a resource, and for combining or aggregating these into a context that is aligned with the business application. In addition, the dynamic evaluation of resource state, that is alterable according to the system environment, and the customization and change capability for the assessment rules provide for the flexibility needed to manage a complex IT environment. In one implementation, the system environment may be represented by a PSE. Continuing the previous example, a PSE may represent online trade and another PSE may represent hours during which trading of stocks is not available. Recovery during a time the online trade PSE is current may have significantly more stringent requirements than during other times.
In one embodiment of the BR System, the customer may provide the rules logic used within a Recovery Segment (e.g., the programmatic representation of the business application) to consume the relevant resource attributes and determine the overall state of the RS (e.g., available, degraded and unavailable, etc). For example, if there is a DB2 and a Websphere application server within the Recovery Segment, along with the supporting operating system, storage, and network resources, a customer could configure a set of rules that requires that the DB2 must have completed the recovery of in-flight work in order to consider the Recovery Segment available. The customer can develop and deploy these rules as part of the Recovery Segment's aggregated rule for availability. As another example, customers may choose to configure a definition of availability based on transaction rate metrics for a DB2, so that if the rate falls below some value, the RS is considered unavailable or degraded, and evaluation of ‘failure’ impact will be triggered within the BR System. Using these configurations, customers can tailor both the definitions of availability, as well as the rapidity with which problems are detected, since any resource attribute and its value can be used as input to the assessment, not just operational state of the IT resources.
In the BR System defined herein, there is support for multiple levels of state assessment. In the implementation chosen, the BR system supports two levels to allow customers to customize the definition of ‘availability’ for shared resource sets. However, the implementation could be extended using the same constructs to support a finer level of granularity of management. As one example, a database that is part of two Recovery Segments may be defined as ‘available’ differently in the context of one RS vs. another.
As one example, the state assessment levels include, for instance:
One example of state aggregation across multiple resources within a RS is depicted in the screen display of
The composed resource state for each resource, along with the customized rules for determining the composed state, are stored in the BRMD, as one example. Specifically, each resource has an entry in the BRMD, and for each resource, there is a set of attributes or properties. There is information about the use and characteristics of each property. One such piece of information is whether the specific property is included in a composed state rule for this resource.
One embodiment of the logic for defining a composed resource state (i.e., a rule for a composed resource state) is described with reference to
Initially, the customer uses the User Interface component to create a composed rule for the resource, STEP 1000. The customer uses any of the resource attributes available and their values combined with typical comparison and logical mathematical operators to compose the rule. For instance, assume a CICS resource exists and has an associated property of number of transactions per second being executed. A rule for CICS being in a degraded state may be “CICS.state=degraded when Trans/sec<1000.”
Thereafter, there is a check for whether the attributes specified are part of the information available for the resource, STEP 1002, and whether the values are within the range specification, INQUIRY 1004. If the attributes and/or values are not valid, the customer is prompted to retry a rule specification, and flow returns to STEP 1000. However, if the rule includes appropriate resource properties and values, INQUIRY 1004, then each property in the rule for that resource is updated in the BRMD entry to indicate that the property is to be used for 1st level state assessment, STEP 1006. Then, the rule is stored in the BRMD entry for the resource, STEP 1008.
Thereafter, for each attribute identified in the rule, the BR System initiates monitoring for changes to that resource, for the given attributes, STEP 1010. Various monitoring technologies can be used, as is known in the art. Further, there are options to use a combination of more robust monitoring techniques that are further described in “Real-Time Information Technology Environments,” (POU920070120US1), Bobak et al., which is hereby incorporated herein by reference in its entirety.
Next, an assessment is made as to whether the resource whose state composition rule is being altered effects the overall state of any RS, INQUIRY 1012. In one example, this evaluation is made, through inspection of the RS level state aggregation rule. Note that as a result of shared resources, there can be more than one RS that includes this resource in RS level state aggregation rules. If any RS is impacted, then the process to assess RS level state is followed, STEP 1014, as described below. Thereafter, or if no RS is impacted, an entry in the RS activity log is inserted to record the resource level state assessment rule defined, STEP 1016.
In addition to the above, the resource composition rule specified can also include a test for whether the current Pattern System Environment (PSE) matches a specific desired system environment. For example, assume a CICS resource exists and has an associated property of number of transactions per second being executed. A rule for CICS being in a degraded state may be “CICS.state=degraded when Trans/sec<1000 & PSE=Online Trade.”
Composed states of resources can effect a RS that includes those resources. In particular, the RS Aggregated state for a given RS can be impacted by any of the composed states of resources that the RS manages, or impacted by the aggregated state of any Redundancy Groups (e.g., groups of equivalent resources) that contain the resources managed by the RS. Further, in other examples, resource property values and/or PSEs can impact RS aggregated state.
In addition to specifying which resources and which Redundancy Groups (RGs) can contribute to a RS aggregated state, the customer can also indicate what each specific impact should be for affecting the RS state in a particular way. As one example, it may be true that if the database is in a degraded composed state, that the RS is in a failed aggregated state, or that if a related RG is in a degraded aggregated state, that the RS is in a degraded aggregated state also. There can be any number of rules used for defining the RS aggregated state. Assessment of the resource composed state and RS aggregated state are described further below.
The aggregated RS state, representing the overall state of the business application, along with the customized rules for determining the aggregated state are stored as part of the persistence mechanism for the RS or may, in an alternate implementation, be stored as an impact pairing, as examples. For example, a resource state and property value can impact a RS state which is defined as part of the rule for RS aggregated state stored with the RS. Further, change in a resource state can impact a RS state which is defined as part of an impact pairing stored in the BRRD and may have a trigger.
One embodiment of the logic for defining the RS aggregated state is described with reference to
Referring to
Thereafter, the customer specifies what the RS state is when the selected resource or RG transitions to the target state, STEP 1112. The entry is then added, in one example, to the in-storage list of BRRD updates to reflect the impact pairing specification, STEP 1114. (In another example, the entry is added to an in-storage list of RSs to be updated.)
When all the resource pairing specification processing is completed, the in-storage BRRD images are made visible outside of this routine as a consistent and complete set, STEP 1116. The flow then continues to INQUIRY 1118, where if the RS is active, the state assessment for the RS is initiated, STEP 1120, as described further in a separate flow. Finally, if the RS is inactive or after the assessment, the RS Activity log is updated to reflect the RS aggregated state definition, STEP 1122.
In a further embodiment, the RS aggregated state rule specified can also include a test for whether the current Pattern System Environment (PSE) matches a specific desired system environment.
In the implementation described herein, RS aggregated state is impacted by one or more resource composed states and/or any related RG aggregated state. The description can be extended to also include impact from specific resource attributes and values as part of the RS aggregated state rule. To accomplish this, additional logic is included to define aggregated RS state, as well as to assess aggregated state dynamically. The following steps are added after STEP 1110, in one example, to define a RS aggregated state rule:
In the dynamic assessment of the state of resources, and subsequently the RS, the real time values associated with the attributes of the properties that contribute to state are used. Any resources that have composed state (or 1st level assessment) rules are assessed. There are classifications of each of the attributes for a given resource that indicate whether that property is used in determining composed state. The rule can reference multiple of these attributes, their values, and can be combined with comparison and logical operators. Once the 1st level state assessment is handled, the related RG states are evaluated. Next, the impact of these changes is evaluated against the defined aggregated state rule for each RS.
One embodiment of the logic for dynamically assessing resource state and assessing RS state is described with reference to
Referring to
Following the resource processing, the related RG aggregated states are calculated, STEP 1208. For example, each RG in which the resource participates is retrieved from the RG table. The RS aggregated state rule is evaluated using resource property values and state. Property values and resource state which may have prompted RG state reevaluation are used in assessing RG aggregated state according to the RG aggregated state rule.
Subsequent to updating the RG assessed states, any RS for which there is a resource that has an updated 1st level assessed state, or has a related RG where the RG aggregated state was updated, or has a resource that is indicated to be directly contributing to a RS state assessment is identified into a set, Set A, STEP 1210. Then, for each unique RS in the set, STEP 1212, processing continues at STEP 1214 (
Referring to STEP 1214, in one implementation in which the RS aggregated state is stored as an impact pairing, first the impact pairings are found for the RS being processed, STEP 1214. This is accomplished via, for instance, the BRRD entries and pairing constructs. The impact pairing indicates the target resource's state or attribute/value pairs needed to evaluate the impact pairing to be true, and the result on the RS when that pairing evaluates to be true.
Next, there is an assessment of which impact pairing rules should be used based on, for instance, the trigger conditions for the rules, including PSE specifications, STEP 1216. For example, pairings are conditionally applied based on the current runtime environment as specified in trigger conditions for the pairing. Trigger conditions provide for the specification of resource property values, resource state or matching of current PSE. Then, for each pairing that evaluates to be true, the state of the RS is adjusted appropriately, STEP 1218.
In an alternate implementation, the RS is retrieved, the aggregated state rule is retrieved from the RS and the aggregated state value is calculated as defined by the rules for the RS.
Thereafter, in the implementation chosen by the BR System, the options for RS state were selected to be available, degraded, or unavailable, though the logic can be extended to include others. If multiple rules evaluate true, the most stringent or ‘least available’ state is selected for the RS. Then, the aggregated state of the RS is updated in the BRMD, STEP 1220, and an entry is inserted into the RS activity log, STEP 1222. Processing continues through STEPS 1214-1222 for each RS.
State assessments following the above flow are initiated when there are detected changes of operational state of resources, during detection of changes in the relevant attributes and values of resources on response to a poll by a BR System, or a response to a specific query, as examples.
In one example, the implementation described herein is a dynamic assessment of RS aggregated state based on impact from composed state of resources within the RS, or the aggregated state of related RGs. To extend the RS aggregated state to include impact from resources in the RS that do not have a composed state, using their attributes, and/or values, the following logic is included:
Processing of resource composed state for a shared resource, and for updating RS aggregated state for shared resources is also possible. A shared resource can impact multiple RS′ aggregated state differently. For example, assume a DB2 resource participates in two Recovery Segments. One RS represents a critical business application for processing insurance claims. The second RS represents a business application which advertises a new business product. Both business applications utilize the DB2 resource which contains customer data. Further, assume the storage on which the DB2 tables are stored has an active duplex copy. If the duplex copy fails, a single copy of the DB2 table exists. In this example, DB2 would be degraded by loss of the duplex storage. The aggregated state of the RS for processing insurance claims may be specified as degraded, while the RS for the advertisement process continues to be available when DB2 becomes degraded.
The rules for composed state of resources, as well as RS aggregated state rules, can be altered during the runtime operation of a BR System. One embodiment of the logic to alter the composed state rule for resources is described with reference to
Referring to
For each rule, the attributes and values specified for the resources are validated with what the resources actually support, STEP 1308, and a check is performed to determine whether the rule is a valid update, INQUIRY 1310. In this implementation, the checks for valid attributes are performed in-line, rather than enforced by the user interface component to allow batching of notifications to the administrator for any invalid rules, and to batch the updates to the BRMD. The implementation could be altered to include the validity checks for attributes and values as part of STEP 1304, as an example.
For valid rules and/or attributes, any additional attributes that are described in the rule are added to the list that the BR System is to monitor, STEP 1312, and any attributes removed from the previous rule are added to the list that the BR System no longer has to monitor, STEP 1314, with the exception of key properties, such as operational state of the resource. For the attributes that are part of the new rule definition, the BRMD flag indicating the attribute is needed for 1st level composed state of the resource is set, STEP 1316. Further, the rule is added to the list of BRMD entries to update, STEP 1318.
Returning to INQUIRY 1310, if the rule or attribute is an invalid update, any invalid rule is added to the list of BRMD entries to notify the admin of invalid changes, STEP 1320.
Processing continues in the above manner for each rule change that is to be handled. Thereafter, processing continues at STEP 1322 (
Moreover, the BR System can stop monitoring any attributes that are no longer listed as part of the rule definitions, STEP 1326, again with the exception of key attributes, such as operational state. Next, any changes to the BRMD are made in, for instance, batch, STEP 1328, and the RS activity log is updated, STEP 1330. This concludes processing associated with changing composed resource state rules.
One embodiment of the logic to update the RS Aggregated state rule is described with reference to
Referring to
Further, a check is performed to determine whether the syntax of the update is valid, INQUIRY 1404. That is, is the change consistent with the format of the RS aggregated state. If not, processing returns to STEP 1402. Otherwise, for each resource or RG that is selected to contribute to the new rule, STEP 1406, the specific pairing in the BRRD to be modified is identified, STEP 1408, where the pairing can be between a RS and a resource with a composed state, or between a RS and a related RG with an aggregated state. As a further example, this can be extended to include direct contribution of resources that do not have composed state definitions, as described above.
Subsequently, the target composed state of the resource or the RG aggregated state is noted, STEP 1410, followed by the related RS state that results when the resource or RG transitions to the assessed state, STEP 1412. For example, in one implementation, the aggregated state rule stored in the RS is updated to include the altered resource state, property value or RG state. In another implementation, the BRRD entry reflecting the impact a change in resource state, property value or RG can have on aggregated state and associated trigger conditions are altered to reflect the change to be made in evaluation of the RS aggregated state.
Next, these entries are added to the list of BRRD entries to update, STEP 1414. Processing continues through STEPS 1406-1414 until all resources in the changed RS aggregated state rule are processed.
Thereafter, the BRRD entries are updated in batch, STEP 1416. An assessment is then made as to whether the RS is in active management, INQUIRY 1418, and if so, the RS aggregated state is assessed, STEP 1420, as described above. Further, or if the RS is inactive, the changes are logged into the RS activity log, STEP 1422. This concludes processing associated with changing aggregated state rules for RS.
In one embodiment, the configuration of rules associated with RS state aggregation are exposed to the customer, since RS availability state is a customer interpretation. The customer can indicate rules for each tier resource of an RS to indicate whether it is degraded or unavailable, so the RS itself should be considered degraded or unavailable.
As an example, the user employs a display panel, such as the one depicted in
Internally, in one example, these rules are stored as impact pairings as defined in the resource pairing information BRRD. In an alternate implementation, these rules are stored as part of the RS.
State aggregation assessment for each resource represented by a BR Management Data table entry is performed by the RS when changes to resource property values occur or when a resource state change is received from monitoring of the resource. These rules on each resource are entered in a way similar to the above technique, except the user is able to specify rules which allow resource property values to be compared to other values.
Described in detail herein is a capability for defining, customizing and/or automatically updating composed state of resources and/or aggregated state of business applications based on rules and current environment conditions. The current environment conditions include, for instance, information associated with a current representation of an IT environment (e.g., a current PSE), one or more values of one or more resource attributes, and/or state of a redundancy group.
One or more aspects of the present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has therein, for instance, computer readable program code means or logic (e.g., instructions, code, commands, etc.) to provide and facilitate the capabilities of the present invention. The article of manufacture can be included as a part of a computer system or sold separately.
One example of an article of manufacture or a computer program product incorporating one or more aspects of the present invention is described with reference to
A sequence of program instructions or a logical assembly of one or more interrelated modules defined by one or more computer readable program code means or logic direct the performance of one or more aspects of the present invention.
Advantageously, a capability is provided for allowing customers to determine the sensitivity of events on resources, evaluate state based on the sensitivity, and manage resources based on the state. Further, customers can evaluate state of business applications and manage those applications based on the evaluated state. State assessment is performed dynamically during runtime, using real-time values and/or current environment conditions.
Although various embodiments are described above, these are only examples. For example, the processing environments described herein are only examples of environments that may incorporate and use one or more aspects of the present invention. Environments may include other types of processing units or servers or the components in each processing environment may be different than described herein. Each processing environment may include additional, less and/or different components than described herein. Further, the types of central processing units and/or operating systems or other types of components may be different than described herein. Again, these are only provided as examples.
Moreover, an environment may include an emulator (e.g., software or other emulation mechanisms), in which a particular architecture or subset thereof is emulated. In such an environment, one or more emulation functions of the emulator can implement one or more aspects of the present invention, even though a computer executing the emulator may have a different architecture than the capabilities being emulated. As one example, in emulation mode, the specific instruction or operation being emulated is decoded, and an appropriate emulation function is built to implement the individual instruction or operation.
In an emulation environment, a host computer includes, for instance, a memory to store instructions and data; an instruction fetch unit to obtain instructions from memory and to optionally, provide local buffering for the obtained instruction; an instruction decode unit to receive the instruction fetched and to determine the type of instructions that have been fetched; and an instruction execution unit to execute the instructions. Execution may include loading data into a register for memory; storing data back to memory from a register; or performing some type of arithmetic or logical operation, as determined by the decode unit. In one example, each unit is implemented in software. For instance, the operations being performed by the units are implemented as one or more subroutines within emulator software.
Further, a data processing system suitable for storing and/or executing program code is usable that includes at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements include, for instance, local memory employed during actual execution of the program code, bulk storage, and cache memory which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
Input/Output or I/O devices (including, but not limited to, keyboards, displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives and other memory media, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the available types of network adapters.
Further, although the environments described herein are related to the management of availability of a customer's environment, one or more aspects of the present invention may be used to manage aspects other than or in addition to availability. Further, one or more aspects of the present invention can be used in environments other than a business resiliency environment.
Yet further, many examples are provided herein, and these examples may be revised without departing from the spirit of the present invention. For example, in one embodiment, the description is described in terms of availability and recovery; however, other goals and/or objectives may be specified in lieu of or in addition thereto. Additionally, the resources may be other than IT resources. Further, there may be references to particular products offered by International Business Machines Corporation or other companies. These again are only offered as examples, and other products may also be used. Additionally, although tables and databases are described herein, any suitable data structure may be used. There are many other variations that can be included in the description described herein and all of these variations are considered a part of the claimed invention.
Further, for completeness in describing one example of an environment in which one or more aspects of the present invention may be utilized, certain components and/or information is described that is not needed for one or more aspects of the present invention. These are not meant to limit the aspects of the present invention in any way.
One or more aspects of the present invention can be provided, offered, deployed, managed, serviced, etc. by a service provider who offers management of customer environments. For instance, the service provider can create, maintain, support, etc. computer code and/or a computer infrastructure that performs one or more aspects of the present invention for one or more customers. In return, the service provider can receive payment from the customer under a subscription and/or fee agreement, as examples. Additionally or alternatively, the service provider can receive payment from the sale of advertising content to one or more third parties.
In one aspect of the present invention, an application can be deployed for performing one or more aspects of the present invention. As one example, the deploying of an application comprises providing computer infrastructure operable to perform one or more aspects of the present invention.
As a further aspect of the present invention, a computing infrastructure can be deployed comprising integrating computer readable code into a computing system, in which the code in combination with the computing system is capable of performing one or more aspects of the present invention.
As yet a further aspect of the present invention, a process for integrating computing infrastructure, comprising integrating computer readable code into a computer system may be provided. The computer system comprises a computer usable medium, in which the computer usable medium comprises one or more aspects of the present invention. The code in combination with the computer system is capable of performing one or more aspects of the present invention.
The capabilities of one or more aspects of the present invention can be implemented in software, firmware, hardware, or some combination thereof. At least one program storage device readable by a machine embodying at least one program of instructions executable by the machine to perform the capabilities of the present invention can be provided.
The flow diagrams depicted herein are just examples. There may be many variations to these diagrams or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified. All of these variations are considered a part of the claimed invention.
Although embodiments have been depicted and described in detail herein, it will be apparent to those skilled in the relevant art that various modifications, additions, substitutions and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims.
