<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>http://wiki.ciscolinux.co.uk/index.php?action=history&amp;feed=atom&amp;title=Disaster_recovery%2C_HA%2C_RTO%2C_RPO</id>
	<title>Disaster recovery, HA, RTO, RPO - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.ciscolinux.co.uk/index.php?action=history&amp;feed=atom&amp;title=Disaster_recovery%2C_HA%2C_RTO%2C_RPO"/>
	<link rel="alternate" type="text/html" href="http://wiki.ciscolinux.co.uk/index.php?title=Disaster_recovery,_HA,_RTO,_RPO&amp;action=history"/>
	<updated>2026-04-05T14:33:07Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.37.2</generator>
	<entry>
		<id>http://wiki.ciscolinux.co.uk/index.php?title=Disaster_recovery,_HA,_RTO,_RPO&amp;diff=3339&amp;oldid=prev</id>
		<title>Pio2pio: Created page with &quot;Two important aspects of resiliency are high availability and disaster recovery. ;High availability (HA): is the ability of the application to continue running in a healthy st...&quot;</title>
		<link rel="alternate" type="text/html" href="http://wiki.ciscolinux.co.uk/index.php?title=Disaster_recovery,_HA,_RTO,_RPO&amp;diff=3339&amp;oldid=prev"/>
		<updated>2018-11-17T18:53:04Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Two important aspects of resiliency are high availability and disaster recovery. ;High availability (HA): is the ability of the application to continue running in a healthy st...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Two important aspects of resiliency are high availability and disaster recovery.&lt;br /&gt;
;High availability (HA): is the ability of the application to continue running in a healthy state, without significant downtime. By &amp;quot;healthy state,&amp;quot; we mean the application is responsive, and users can connect to the application and interact with it.&lt;br /&gt;
&lt;br /&gt;
;Disaster recovery (DR): is the ability to recover from rare but major incidents: non-transient, wide-scale failures, such as service disruption that affects an entire region. Disaster recovery includes data backup and archiving, and may include manual intervention, such as restoring a database from backup.&lt;br /&gt;
&lt;br /&gt;
One way to think about HA versus DR is that DR starts when the impact of a fault exceeds the ability of the HA design to handle it.&lt;br /&gt;
&lt;br /&gt;
;Business continuity (BC): which is the ability to perform essential business functions during and after adverse conditions, such as a natural disaster or a downed service. &lt;br /&gt;
&lt;br /&gt;
Systems resiliency&lt;br /&gt;
Two important metrics to consider are the recovery time objective and recovery point objective.&lt;br /&gt;
;Recovery time objective (RTO): is the maximum acceptable time that an application can be unavailable after an incident. If your RTO is 90 minutes, you must be able to restore the application to a running state within 90 minutes from the start of a disaster. If you have a very low RTO, you might keep a second deployment continually running on standby, to protect against a regional outage.&lt;br /&gt;
&lt;br /&gt;
;Recovery point objective (RPO): is the maximum duration of data loss that is acceptable during a disaster. For example, if you store data in a single database, with no replication to other databases, and perform hourly backups, you could lose up to an hour of data.&lt;br /&gt;
&lt;br /&gt;
= Resources =&lt;br /&gt;
*[https://docs.microsoft.com/en-us/azure/architecture/resiliency/ Designing resilient applications for Azure] Microsoft Docs&lt;/div&gt;</summary>
		<author><name>Pio2pio</name></author>
	</entry>
</feed>