|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|Documentation menu:||Home •||Manuals •||Procedures •||Training •||Other •||Contact ►||For:||VO managers •||Administrators|
Back to main page: Services Availability Continuity Plans
This page reports on the Availability and Continuity Plan for the Service or Component name and it is the result of the risks assessment conducted for this service: a series of risks and treats has been identified and analysed, along with the correspondent countermeasures currently in place. Whenever a countermeasure is not considered satisfactory for either avoiding or reducing the likelihood of the occurrence of a risk, or its impact, it is agreed with the service provider a new treatment for improving the availability and continuity of the service. The process is concluded with an availability and continuity test.
|Av/Co plan and test|
previous plans are collected here:
link to document db
Hardware HA Configuration
Availability requirements and performances
''List the Service Level Targets as agreed in the OLA/UA'' In the OLA it was agreed the following performances targets, on a monthly basis: *Availability: *Reliability: ''Other availability requirements: * the service is accessible through X509 certificate and/or other authentication system * The service is accessible via CLI and/or webUI (link to the probes that checks the authentication and the service in general) * (depending on the service, specific requirements can be identified. In case, for each requirement report what is the action/measure in case of failure) Look at monitoring history, in case of particular issues'' ''The service availability is regularly tested by nagios probes (X and Y: link to ARGO/nagios) The performances reports in terms of Availability and Reliability are produced by [http://egi.ui.argo.grnet.gr/egi/OPS-MONITOR-Critical ARGO] on an almost real time basis and they are also periodically collected into the [https://documents.egi.eu/public/ShowDocument?docid=2324 Documentation Database]. Over the past years, the SERVICE NAME hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.''
Risks assessment and management
For more details, please look at the (google spreadsheet link). We will report here a summary of the assessment.
|Risk id||Risk description||Affected components||Established measures||Risk level||Expected duration of downtime / time for recovery||Comment|
|1||Service unavailable / loss of data due to hardware failure||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|2||Service unavailable / loss of data due to software failure||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|3||service unavailable / loss of data due to human error||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|4||service unavailable for network failure (Network outage with causes external of the site)||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|5||Unavailability of key technical and support staff (holidays period, sickness, ...)||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|6||Major disruption in the data centre. Fire, flood or electric failure for example||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|7||Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored.||Low||the measures already in place are considered satisfactory and risk level is acceptable|
|8||(D)DOS attack. The service is unavailable because of a coordinated DDOS.||Low||the measures already in place are considered satisfactory and risk level is acceptable|
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
procedures for the several countermeasures to invoke in case of risk occurrence (put a link if public) Specify if the Availability targets are different in case the plan is invoked. Specify the recovery requirements (in general they are the outcomes of the BIA). *Maximum tolerable period of disruption (MTPoD) (the maximum amount of time that a service can be unavailable or undelivered after an event that causes disruption to operations, before its stakeholders perceive unacceptable consequences): *Recovery time objective (RTO) (the acceptable amount of time to restore the service in order to avoid unacceptable consequences associated with a break in continuity (this has to be less than MTPoD)): *Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): Specify if there is a particular approach for the return to normal working conditions if different from what already reported in the risk assessment. The support unit X shall be used to report any incident or service request The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it.
Availability and Continuity test
The proposed A/C test will focus on a recovery scenario: the service is supposed to have been disrupted and needs to be reinstalled from scratch. Typically this covers the risks 1,2, and 7. The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured. Performing this test will be useful to spot any issue in the recovery procedures of the service.