SolisTransport is designing a disaster recovery and business continuity solution for its maritime cargo tracking system. The tracking system writes voyage telemetry logs to a general-purpose v2 storage account in the East US region.
The solution must meet the following requirements:
- Recovery Point Objective (RPO): Under 15 minutes.
- Recovery Time Objective (RTO) for reads: Near 0 minutes. The application must be able to read tracking data from a secondary region (West US) immediately during a primary region outage, without waiting for Microsoft to declare a disaster or initiate a failover.
- Write Availability: Write capability in the secondary region is only required if the outage is prolonged and a failover is officially declared.
- Cost Constraints: Minimize storage costs and avoid the overhead of zone redundancy in the primary region.
Which storage configuration and recovery strategy should you recommend?
- Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Direct read requests to the secondary endpoint during the outage, and initiate a customer-managed failover if write capability is required.Cevap
- BConfigure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Direct write requests to the secondary endpoint during the outage, as RA-GRS supports active-active writes without initiating a failover.
- CConfigure the storage account to use Geo-Redundant Storage (GRS). Direct read requests to the secondary endpoint during the outage, and initiate a customer-managed failover if write capability is required.
- DConfigure the storage account to use Locally Redundant Storage (LRS). In the event of an outage, restore the storage account from an Azure Backup vault to a new storage account in the West US region.