FlexCache replication is asynchronous and does not provide zero RPO/RTO for data changes.

FlexCache replication is asynchronous and does not provide zero RPO/RTO for data changes.

• A. True
• B. False
• C. It provides zero RPO/RTO
• D. It depends on SnapMirror

Answer: (A)

FlexCache uses asynchronous updates to keep the remote cache in sync with the origin. Because writes on the primary are not reflected instantaneously on the remote cache, there’s always a delay before changes are visible remotely. That delay means some recent data could be lost if a failover happens, which corresponds to a non-zero RPO. Similarly, the time required to fail over and re-synchronize data means the RTO is not guaranteed to be zero either. So the statement that FlexCache replication is asynchronous and does not provide zero RPO/RTO is correct. If zero RPO/RTO is required, a synchronous replication approach would be needed, which is different from FlexCache’s default asynchronous behavior.

FlexCache uses asynchronous updates to keep the remote cache in sync with the origin. Because writes on the primary are not reflected instantaneously on the remote cache, there’s always a delay before changes are visible remotely. That delay means some recent data could be lost if a failover happens, which corresponds to a non-zero RPO. Similarly, the time required to fail over and re-synchronize data means the RTO is not guaranteed to be zero either. So the statement that FlexCache replication is asynchronous and does not provide zero RPO/RTO is correct. If zero RPO/RTO is required, a synchronous replication approach would be needed, which is different from FlexCache’s default asynchronous behavior.