The disaster recovery of the database is very important to the production system of the enterprise. The enterprise is currently using the GaussDB (foropenGauss) distributed database as the…

Question

Options

• AThe business requires that the RTO of the disaster recovery library must be within 5s
• BThe production library may expand in the future and add new DN
• CThe disaster recovery database will have access to some query services, and these services will
• DThe topology of the production database cluster and the disaster recovery database cluster are

• A
  11% (2)
• B
  79% (15)
• C
  5% (1)
• D
  5% (1)

Explanation

Option B is correct because DRS (Data Replication Service) for GaussDB distributed databases supports the scenario where the source production cluster scales out by adding new Data Nodes (DNs). DRS synchronizes at a logical level, meaning it can continue replication seamlessly even after the source topology changes through DN expansion, making it a suitable long-term solution for growing environments.

Option A is incorrect because DRS uses asynchronous replication, which cannot guarantee an RTO of 5 seconds or less. Such a strict recovery time objective requires synchronous replication or a dedicated high-availability mechanism, not DRS-based disaster recovery synchronization.

Option C is incorrect because when DRS is actively synchronizing to a disaster recovery database, that target database cannot simultaneously serve write-capable query services. Active writes to the DR side would conflict with the incoming replication stream and are not supported in this DRS configuration.

Option D is incorrect because DRS for GaussDB distributed requires compatible cluster topologies between the source and target. A mismatch in cluster topology (such as differing numbers of Coordinator Nodes or a structurally incompatible layout) is a known limitation that makes DRS unsuitable for that scenario.

Memory tip: Think of DRS as a "hands-off replication pipe" - it can adapt when the source grows (B is fine), but it breaks down when the destination is too busy (C), too fast (A), or too different in shape (D).

No community discussion yet for this question.