Service Catalogue - RTO and RPO
Once a Service has been created in ICEFLO, Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) can be given to these Services. Once the Service has been created these can then be aligned to Runbooks. A Runbook can have more than one Service aligned to it.
From the Catalogues Domain > Portfolios and Services you have the ability to add Recovery Time Objectives and Recovery Point Objectives to Services which have been created in ICEFLO.
These objective times are set from the Portfolio and Services screen. From this screen you can also state the Service Criticality, the Availability Percentage and a Description of the Service.
A Runbook can have multiple Services aligned to it. Tasks within Runbooks can be identified as Tasks which are bringing Down the Service or bringing Up the Service. These can be set from the Services Menu Item from the ... More Options.
Aligning Services to Tasks
Multiple Services can be added to a Runbook. This can be achieved via the ... More Options menu > Services. Under the Potential Services Panel additional Services which can possibly be added to the Runbook will be listed. Once all the Services affected have been added to the Runbook, the Tasks which have been identified as either bringing down a Service or bringing it back up can then be aligned to the Service.
Clicking into the Service from the Services screen launches the Service Detail screen. From here you can aligned the Service Down and Up Tasks.
Once Down and Up Tasks have been assigned, the Start and End Times of these will be populated and the Recovery Time Objective (RTO) will be the calculated. Once these Down and Up tasks have Actual Times Populated the Recovery Time Achieved (RTA) is populated.
Recording the RPA Against a Service
The Recovery Point Achieved (RPA) can be entered manually to record the volume of data that is lost. An explanation or further description of this can be added into the RPA comments section.