Real-time replication continuously copies data from a primary system to a secondary, geographically separate system as transactions occur. This strategy directly addresses the requirements for "continuous data protection" and "minimal downtime." By maintaining an up-to-date copy of the data, the organization can achieve a near-zero Recovery Point Objective (RPO), meaning very little to no data is lost. In the event of a failure, a rapid failover to the replicated site allows for a very low Recovery Time Objective (RTO), ensuring services are restored quickly. This makes it the superior choice for critical systems demanding high availability and data resilience.

A. Full Backup: This is a point-in-time copy. It does not provide continuous protection, and any data created after the backup is lost upon failure.
C. Cold Storage: This is an archival solution for infrequently accessed data. It is characterized by low cost but very high retrieval times, making it unsuitable for quick recovery.
D. Incremental Backup: This captures changes since the last backup, but it is still a point-in-time method, not continuous. Restoration can be complex and slower than failover to a replicated site.

1. National Institute of Standards and Technology (NIST). (2010). Special Publication 800-34 Rev. 1

Contingency Planning Guide for Federal Information Systems.

Section 3.4.2

"Alternate Site

" describes a hot site

which is the fastest recovery option. It states

"A hot site is a fully operational facility... This type of site would have systems... with real-time mirroring/replication of the production site data." This directly links real-time replication to the goal of minimal downtime.

2. AWS Well-Architected Framework. (2023). Reliability Pillar Whitepaper.

Page 23

"Disaster recovery (DR) strategies

" compares different DR approaches. It contrasts Backup and Restore with strategies like Pilot Light

Warm Standby

and Multi-site active/active

all of which rely on data replication to achieve lower RPO and RTO. The document explicitly states that replication is used to "reduce recovery time."

3. Coulouris

G.

Dollimore

J.

& Kindberg

T. (2012). Distributed Systems: Concepts and Design (5th ed.). Pearson Education.

Chapter 18

"Replication

" Section 18.1

"Introduction

" explains that replication is a key technique for enhancing performance and increasing availability and fault tolerance. It states

"If data are replicated at two or more servers

then clients can access data from any of the servers... If one server fails

clients can still access the data at the other servers." This academic text establishes replication as the fundamental strategy for high availability.