Merge pull request #2078 from OctopusDeploy/miken/clarify-region-failure

Adds region failure to the Disaster Recovery tables

dictionary-octopus.txt

@@ -75,6 +75,7 @@ lifecycles
 linkerd
 ltsc
 maintenanceconfiguration
+majeure
 maxage
 milli
 MITM

src/pages/docs/octopus-cloud/disaster-recovery.md

@@ -22,6 +22,9 @@ Consequently, this information is provided as guidance information only and does
 | Failure of a Node                              | Minor service interruption | Local copies plus geo-redundant backup | 16 9's          | 30s                           | 5s                                                 | Microsoft                    |
 | Individual customer breach / data corruption   | Service interruption       | Restore from a geo-redundant backup    | 12 9's          | 1 hr                          | 1 hour or to the customer specified restore point. | Microsoft and Octopus Deploy |
 | Data Center failure (single Availability zone) | Service interruption       | Restore from a geo-redundant backup    | 12 9's          | 12 hrs                        | 1 hour or to the customer specified restore point. | Microsoft and Octopus Deploy |
+| Region failure | Service interruption       | Restore from a geo-redundant backup    | 12 9's          | 24 hrs **                      | 1 hour or to the customer specified restore point. | Microsoft and Octopus Deploy |
+
+** _Region failure is a special case where the best path to recovery may vary. Learn more below in the Azure Region Failure section._
 
 For further information, customers should refer to [Microsoft's disaster recovery](https://docs.microsoft.com/en-us/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview?view=azuresql#recover-a-database-to-the-existing-server) documentation.
 
@@ -36,6 +39,9 @@ Note: The portal is hosted in a separate Azure region from customer instances an
 | Failure of a Node                              | No customer impact                     | Local copies plus geo-redundant backup | 16 9's          | 30s                           | 5s                                          | Microsoft                    |
 | Portal data corruption or compromise           | No customer impact, portal unavailable | Restore from a geo-redundant backup    | 12 9's          | 1 hr                          | 1 hour or to the appropriate restore point. | Microsoft and Octopus Deploy |
 | Data Center failure (single Availability zone) | No customer impact, portal unavailable | Restore from a geo-redundant backup    | 12 9's          | 12 hrs                        | 1 hour or to the appropriate restore point. | Microsoft and Octopus Deploy |
+| Region failure | Service interruption       | Restore from a geo-redundant backup    | 12 9's          | 24 hrs **                      | 1 hour or to the customer specified restore point. | Microsoft and Octopus Deploy |
+
+** _Region failure is a special case where the best path to recovery may vary. Learn more below in the Azure Region Failure section._
 
 For further information, customers should refer to [Microsoft's disaster recovery](https://docs.microsoft.com/en-us/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview?view=azuresql#recover-a-database-to-the-existing-server) documentation.