{"id":4201,"date":"2025-06-14T15:13:22","date_gmt":"2025-06-14T15:13:22","guid":{"rendered":"https:\/\/w3buddy.com\/?post_type=cposts&p=4201"},"modified":"2025-06-14T15:13:23","modified_gmt":"2025-06-14T15:13:23","slug":"far-sync-instances-in-oracle-data-guard","status":"publish","type":"cposts","link":"https:\/\/w3buddy.com\/blog\/notes\/data-guard\/far-sync-instances-in-oracle-data-guard\/","title":{"rendered":"Far Sync Instances in Oracle Data Guard"},"content":{"rendered":"\n
\n

\ud83d\udef0\ufe0f A lightweight relay to ensure zero data loss across long distances<\/em><\/p>\n<\/blockquote>\n\n\n\n

What is a Far Sync Instance?<\/h3>\n\n\n\n

A Far Sync Instance<\/strong> is like a middleman server<\/strong> placed closer to your primary database<\/strong>, but not where the standby lives.
Its job? To receive redo data instantly<\/strong> from the primary and forward it safely<\/strong> to a remote standby database \u2014 especially over slow or high-latency networks.<\/p>\n\n\n\n

\u2705 It ensures zero data loss (Maximum Protection mode)<\/strong>, even when the real standby is too far<\/strong> to sync in real time.<\/p>\n\n\n\n

Simple Example:<\/h3>\n\n\n\n

Imagine your main office (Primary DB)<\/strong> is in Delhi and your Disaster Recovery (Standby DB)<\/strong> is in the US.<\/p>\n\n\n\n

Sending every redo log directly to the US can cause delays and slow down the primary.<\/p>\n\n\n\n

So, you place a Far Sync Instance<\/strong> in Mumbai. It:<\/p>\n\n\n\n

    \n
  1. Receives redo instantly from Delhi (fast link )<\/li>\n\n\n\n
  2. Forwards it to the US standby (slower link but async )<\/li>\n\n\n\n
  3. Keeps the primary fast and safe <\/li>\n<\/ol>\n\n\n\n

    How It Works:<\/h3>\n\n\n\n
      \n
    • No data files<\/strong> stored \u2014 just redo log transport<\/li>\n\n\n\n
    • Acts like a standby<\/strong>, but can\u2019t become primary<\/strong><\/li>\n\n\n\n
    • No user access<\/strong>; purely internal redo relay<\/li>\n\n\n\n
    • Used with SYNC transport<\/strong> to maintain zero data loss<\/li>\n<\/ul>\n\n\n\n

      Summary Table<\/h3>\n\n\n\n
      Category<\/th>Details<\/th><\/tr><\/thead>
      \u2705 Best For<\/strong><\/td>– Long-distance Data Guard setups
      – Zero data loss (Max Protection) over slow links<\/td><\/tr>
      \u2699\ufe0f Key Features<\/strong><\/td>– Lightweight instance
      – No datafiles
      – Relays redo logs
      – Supports sync mode<\/td><\/tr>
      \ud83d\udeab Limitations<\/strong><\/td>– Can’t act as standby
      – No user access
      – Still needs a physical\/logical standby<\/td><\/tr>
      \ud83d\udca1 Analogy<\/strong><\/td>Think of it like a courier hub<\/strong> \u2014 collects data from HQ and forwards it to distant locations smoothly.<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"

      \ud83d\udef0\ufe0f A lightweight relay to ensure zero data loss across long distances What is a Far Sync Instance? A Far Sync Instance is like a middleman server placed closer to your primary database, but not where the standby lives.Its job? To receive redo data instantly from the primary and forward it safely to a remote […]<\/p>\n","protected":false},"template":"","meta":{"googlesitekit_rrm_CAowu461DA:productID":""},"categories":[988,952],"class_list":["post-4201","cposts","type-cposts","status-publish","hentry","category-data-guard","category-notes"],"_links":{"self":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/cposts\/4201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/cposts"}],"about":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/types\/cposts"}],"wp:attachment":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/media?parent=4201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/categories?post=4201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}