Recovering to Minimum Service

In Valuemation, the specification of 'minimum service capabilities' (including the planned minimum recovery times and activities) is provided for each service. There is a predefined 'Business Continuity' Service Type from class “Service Component” with all relevant service parameters, SLAs and service options.

• Service instances of this service type can be assigned to other service instances (i.e. business services) to document all the recovery options for it.
• You can get an overview of all services and their recovery options by using a filtered Service Parameter catalog for your needs.

• The defined Recovery Sequence No. documents the exact order of recovery process.

The following picture displays a complete model configuration:

The minimal recovery configuration

Federated USU Valuemation CMDB contains all information to show the current configuration, the minimum acceptable configuration (as part of the whole configuration, e.g. only one web server instance instead of two with a upstream load balancer instance), the baseline configuration (out of Release Management) and the disruption impact configuration (because of relations to other CIs and services and all information about their availability).

The following model configurations display:

• Full configuration with recovery (default).

• Recovery configuration only.

The definition of the Service Recovery - a full configuration with recovery:

Here you can see the complete structure of services and their related configuration items. The relation between the services (Business Service - Service Component - Service Asset) contains the corresponding context attribute (in the service - service and service - system relations).

For the minimal recovery situation, only the red links are valid.

The Recovery-only configuration:

SLAs and Service Targets that would apply when operating at a recovery site

The SLAs are stored as service parameter assigned to services. The operation at a recovery site based on special subordinated Business Continuity service component. Because this service component has its own SLA parameter and service targets the recovery and business continuity operation is fully aligned with these definitions.

The recovery options are as follows:

• Do nothing
• Manual Workarounds
• Reciprocal Arrangements
• Gradual Recovery/Cold Standby
• Intermediate Recovery/Warm Standby

• Immediate Recovery/Hot Standby

In case of emergency and disaster recovery, the predefined “minimum disaster recovery process template” will be instantiated and will take care to process all the activities which are necessary to recover the related service exactly in the way the related “Business Continuity” service component is specified.