Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Accounting Repository Availability and Continuity Plan"

From EGIWiki
Jump to navigation Jump to search
(33 intermediate revisions by 3 users not shown)
Line 14: Line 14:
|-
|-
! scope="row"| Risks assessment
! scope="row"| Risks assessment
| 2018-07-06
| 2020-07-20
| 2019 July
| 2021 August
|-
|-
! scope="row"| Av/Co plan and test
! scope="row"| Av/Co plan and test
| -
| 2020-08-04
| -
| 2021 August
|-
|-
|}
|}
previous plans are collected here: https://documents.egi.eu/document/3494


= Hardware HA Configuration =
= Hardware HA Configuration =
Line 30: Line 32:
*In a disaster recovery situation, the latest database backup out the full backups can be recovered from tape and then the binlogs can be applied to do “Point in Time Recovery” of the database. Additionally up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored.
*In a disaster recovery situation, the latest database backup out the full backups can be recovered from tape and then the binlogs can be applied to do “Point in Time Recovery” of the database. Additionally up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored.


= Performances =
= Availability requirements and performances =
 
The performances reports in terms of Availability and Reliability are produced by [http://argo.egi.eu/ar-opsmon ARGO] on an almost real time basis and they are also collected every 6 months into the Documentation Database (last period [https://documents.egi.eu/document/3270 July 2017 - December 2017].


In the OLA it was agreed the following performances targets, on a monthly basis:
In the OLA it was agreed the following performances targets, on a monthly basis:
Line 38: Line 38:
*Reliability 99%
*Reliability 99%


Over the past years, the Accounting Portal hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.
Other availability requirements:
- the service accepts messages from authenticated clients
- the service provides data to the Accounting Portal
 
The service availability is regularly tested by nagios probe org.activemq.OpenWireSSL: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_egi.APELRepository&style=overview
 
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 Accounting Repository hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.


= Risks assessment and management =
= Risks assessment and management =


For more details, please look at the [https://docs.google.com/spreadsheets/d/1rB6JSywfxVZ9GIIHWo1askSRz8oRMC9DzkW9LLVJ898/edit#gid=1565906040 google spreadsheet]. We will report here a summary of the assessment.
For more details, please look at the [https://docs.google.com/spreadsheets/d/1rB6JSywfxVZ9GIIHWo1askSRz8oRMC9DzkW9LLVJ898/edit#gid=2098849286 google spreadsheet]. We will report here a summary of the assessment.


== Risks analysis ==
== Risks analysis ==
Line 58: Line 66:
| Service unavailable / loss of data due to hardware failure
| Service unavailable / loss of data due to hardware failure
| All
| All
| Database and filesystem are backed up every 24 hours to tape storage. Database binary logs are kept for 14 Days and are included in the tape backup.
| Preventive: Database and filesystem are backed up every 24 hours to tape storage. Database binary logs are kept for 14 Days and are included in the tape backup.
Server hardware is covered by Dell “ProSupport Plus” with 4Hour mission critical support that ensures that service can be restored in minimum time.
Reactive: Server hardware is covered by Dell “ProSupport Plus” with 4Hour mission critical support that ensures that service can be restored in minimum time.
In a disaster recovery situation, the latest database backup out the full backups can be recovered from tape and then the binlogs can be applied to do “Point in Time Recovery” of the database.
In a disaster recovery situation, the latest database backup out the full backups can be recovered from tape and then the binlogs can be applied to do “Point in Time Recovery” of the database.
| style="background: green"| Low  
| style="background: green"| Low  
| In case an instance must be instantiated from backups can take up to two-three working hours.
| up to 8 hours (1 working day)
In case latest backups are not available some data must be re-generate from the central accounting repositories and this may take up to two hours.
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 69: Line 76:
| Service unavailable / loss of data due to software failure
| Service unavailable / loss of data due to software failure
| Any
| Any
| Various types of monitoring in place.
| Preventative: Various types of monitoring in place.
| style="background: green"| Low  
| style="background: green"| Low  
| One to two working hours
| up to 4 hours (half working day)
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 77: Line 84:
| service unavailable / loss of data due to human error
| service unavailable / loss of data due to human error
| Any
| Any
| Backups available. Administrator documentation. Training.
| Reactive: Backups available.
Preventative: Administrator documentation. Training.
| style="background: green"| Low  
| style="background: green"| Low  
| Two to Three working hours.
| up to 8 hours (1 working day)
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 85: Line 93:
| service unavailable for network failure (Network outage with causes external of the site)
| service unavailable for network failure (Network outage with causes external of the site)
| APEL-SSM receiver and sender
| APEL-SSM receiver and sender
| Up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored.
| Reactive: Up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored.
| style="background: green"| Low  
| style="background: green"| Low  
| Close to zero, less than one hour.
| up to 4 hours (half working day)
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 93: Line 101:
| Unavailability of key technical and support staff (holidays period, sickness, ...)
| Unavailability of key technical and support staff (holidays period, sickness, ...)
| Any
| Any
| As well as having two staff in the APEL team, administration of the service can also be covered by GOCDB staff and, to a limited extent, other staff within the department.
| Preventative: As well as having two staff in the APEL team, administration of the service can also be covered by GOCDB staff and, to a limited extent, other staff within the department.
| style="background: green"| Low  
| style="background: green"| Low  
| Within the OLA targets for operational actions
| 1 or more working days
Longer periods in case of bugs or maintenance (one week) because not all the personnel can develop patches to the code.
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 102: Line 109:
| Major disruption in the data centre. Fire, flood  or electric failure for example
| Major disruption in the data centre. Fire, flood  or electric failure for example
| All
| All
| Fire suppression systems and generator backed UPS
| Reactive: Fire suppression systems
Preventative: Generator backed UPS
| style="background: green"| Low  
| style="background: green"| Low  
| 1-2 weeks, the time to deploy recover operational status at CESGA or the service to another resource centre partner of the NGI
| 1 or more working days
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 110: Line 118:
| Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored.
| Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored.
|  
|  
| Daily backup are executed. Backup is stored in a separate system and can be restored in another system
| Reactive: Daily backup are executed. Backup is stored in a separate system and can be restored in another system
| style="background: green"| Low  
| style="background: green"| Low  
| 1-2 work hours. In case new host certificates are required, up to 2 days.
| up to 8 hours (1 working day)
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|-
|-
Line 118: Line 126:
| (D)DOS attack. The service is unavailable because of a coordinated DDOS.
| (D)DOS attack. The service is unavailable because of a coordinated DDOS.
| APEL-SSM receiver
| APEL-SSM receiver
| Authentication and authorisation required to send messages via the brokers and messages are additionally checked when received at the Repository
| Preventative: Authentication and authorisation required to send messages via the brokers and messages are additionally checked when received at the Repository
| style="background: green"| Low  
| style="background: green"| Low  
| Depending on the attack, few hours maximum
| up to 8 hours (1 working day)
| the measures already in place are considered satisfactory and risk level is acceptable
| the measures already in place are considered satisfactory and risk level is acceptable
|}
|}
Line 128: Line 136:
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory


= Availability and Continuity test =
== Additional information ==
 
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.
* procedures for the several countermeasures to invoke in case of risk occurrence are available to the providers:
**re-installation, backup restoring in case of risks 1-2-3-7
**general documentation and procedures in case of risk 5
*the Availability targets don't change in case the plan is invoked.
*recovery requirements:
**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): 1 week
**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)): 5 days
**Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): n.a. (data can be republished)
*approach for the return to normal working conditions as reported in the risk assessment.


== Test details ==
The support unit '''APEL''' shall be used to report any incident or service request.


references in the [https://rt.egi.eu/rt/Ticket/Display.html?id=14308 RT ticket 14308]
The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it.


10:45 CEST -> poweroff of the original machine (accounting-devel-next)
= Availability and Continuity test =
11:05 CEST -> Power on for the template (minimal) machine for recovery
12:00 CEST -> Data recovery completed
12:10 CEST -> Boot restoration and miscelaneus comprobations.
12:15 CEST -> Recovered machine rebooted and services on line


The recovery took about '''70 minutes'''.
It is not necessary performing the test: the service is low-critical given the HA configuration, and thanks to the fact that the accounting records can be cached up to 3 days in the messaging system, the sites can republish the accounting data, or in case they can also stop in sending them.


= Revision History  =
= Revision History  =
Line 160: Line 169:
| 2018-07-06
| 2018-07-06
| first draft, discussing with the provider
| first draft, discussing with the provider
|-
| <br>
| Alessandro Paolini
| 2019-08-20
| starting the yearly review...
|-
| <br>
| Alessandro Paolini, Adrian Coveney
| 2020-08-04
| plan updated and finalised
|-
|-
|
|

Revision as of 15:05, 4 August 2020

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

Introduction

This page reports on the Availability and Continuity Plan for the Accounting Repository 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.

Last Next
Risks assessment 2020-07-20 2021 August
Av/Co plan and test 2020-08-04 2021 August

previous plans are collected here: https://documents.egi.eu/document/3494

Hardware HA Configuration

The Accounting Repository runs on a dedicated physical machine running in the STFC RAL Data Centre. It is powered via the generator-backed UPS.

  • Database and file system are backed up every 24 hours to tape storage. Database binary logs are kept for 14 Days and are included in the tape backup.
  • Server hardware is covered by Dell “ProSupport Plus” with 4Hour mission critical support that ensures that service can be restored in minimum time.
  • In a disaster recovery situation, the latest database backup out the full backups can be recovered from tape and then the binlogs can be applied to do “Point in Time Recovery” of the database. Additionally up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored.

Availability requirements and performances

In the OLA it was agreed the following performances targets, on a monthly basis:

  • Availability: 99%
  • Reliability 99%

Other availability requirements: - the service accepts messages from authenticated clients - the service provides data to the Accounting Portal

The service availability is regularly tested by nagios probe org.activemq.OpenWireSSL: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_egi.APELRepository&style=overview

The performances reports in terms of Availability and Reliability are produced by ARGO on an almost real time basis and they are also periodically collected into the Documentation Database.

Over the past years, the Accounting Repository 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. We will report here a summary of the assessment.

Risks analysis

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 All Preventive: Database and filesystem are backed up every 24 hours to tape storage. Database binary logs are kept for 14 Days and are included in the tape backup.

Reactive: Server hardware is covered by Dell “ProSupport Plus” with 4Hour mission critical support that ensures that service can be restored in minimum time. In a disaster recovery situation, the latest database backup out the full backups can be recovered from tape and then the binlogs can be applied to do “Point in Time Recovery” of the database.

Low up to 8 hours (1 working day) the measures already in place are considered satisfactory and risk level is acceptable
2 Service unavailable / loss of data due to software failure Any Preventative: Various types of monitoring in place. Low up to 4 hours (half working day) the measures already in place are considered satisfactory and risk level is acceptable
3 service unavailable / loss of data due to human error Any Reactive: Backups available.

Preventative: Administrator documentation. Training.

Low up to 8 hours (1 working day) 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) APEL-SSM receiver and sender Reactive: Up to three days worth of accounting messages can be cached on the EGI message brokers which can then be retrieved once service is restored. Low up to 4 hours (half working day) the measures already in place are considered satisfactory and risk level is acceptable
5 Unavailability of key technical and support staff (holidays period, sickness, ...) Any Preventative: As well as having two staff in the APEL team, administration of the service can also be covered by GOCDB staff and, to a limited extent, other staff within the department. Low 1 or more working days 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 All Reactive: Fire suppression systems

Preventative: Generator backed UPS

Low 1 or more working days 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. Reactive: Daily backup are executed. Backup is stored in a separate system and can be restored in another system Low up to 8 hours (1 working day) 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. APEL-SSM receiver Preventative: Authentication and authorisation required to send messages via the brokers and messages are additionally checked when received at the Repository Low up to 8 hours (1 working day) the measures already in place are considered satisfactory and risk level is acceptable

Outcome

The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory

Additional information

  • procedures for the several countermeasures to invoke in case of risk occurrence are available to the providers:
    • re-installation, backup restoring in case of risks 1-2-3-7
    • general documentation and procedures in case of risk 5
  • the Availability targets don't change in case the plan is invoked.
  • recovery requirements:
    • 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): 1 week
    • 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)): 5 days
    • Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): n.a. (data can be republished)
  • approach for the return to normal working conditions as reported in the risk assessment.

The support unit APEL 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

It is not necessary performing the test: the service is low-critical given the HA configuration, and thanks to the fact that the accounting records can be cached up to 3 days in the messaging system, the sites can republish the accounting data, or in case they can also stop in sending them.

Revision History

Version Authors Date Comments

Alessandro Paolini 2018-07-06 first draft, discussing with the provider

Alessandro Paolini 2019-08-20 starting the yearly review...

Alessandro Paolini, Adrian Coveney 2020-08-04 plan updated and finalised