Matches in DBpedia 2016-04 for { <http://wikidata.dbpedia.org/resource/Q927401> ?p ?o }
Showing triples 1 to 8 of
8
with 100 triples per page.
- Q927401 subject Q8330165.
- Q927401 abstract "A recovery point objective, or “RPO”, is defined by business continuity planning. It is the maximum targeted period in which data might be lost from an IT service due to a major incident.The RPO gives systems designers a limit to work to. For instance, if the RPO is set to four hours, then in practice, off-site mirrored backups must be continuously maintained – a daily off-site backup on tape will not suffice. Care must be taken to avoid two common mistakes around the use and definition of RPO. Firstly, business continuity staff use business impact analysis to determine RPO for each service – RPO is not determined by the existent backup regime. Secondly, when any level of preparation of off-site data is required, rather than at the time the backups are offsited, the period during which data is lost very often starts near the time of the beginning of the work to prepare backups which are eventually offsited.".
- Q927401 wikiPageWikiLink Q1080590.
- Q927401 wikiPageWikiLink Q42848.
- Q927401 wikiPageWikiLink Q831801.
- Q927401 wikiPageWikiLink Q8330165.
- Q927401 comment "A recovery point objective, or “RPO”, is defined by business continuity planning. It is the maximum targeted period in which data might be lost from an IT service due to a major incident.The RPO gives systems designers a limit to work to. For instance, if the RPO is set to four hours, then in practice, off-site mirrored backups must be continuously maintained – a daily off-site backup on tape will not suffice.".
- Q927401 label "Recovery point objective".