Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqtct-00DoYB-PW for pgsql-admin@arkaria.postgresql.org; Wed, 18 Sep 2024 12:17:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sqtct-008zEL-DT for pgsql-admin@arkaria.postgresql.org; Wed, 18 Sep 2024 12:17:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqtct-008z99-1D for pgsql-admin@lists.postgresql.org; Wed, 18 Sep 2024 12:17:43 +0000 Received: from mail-ej1-x62c.google.com ([2a00:1450:4864:20::62c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sqtcp-001ntM-Vl for pgsql-admin@postgresql.org; Wed, 18 Sep 2024 12:17:41 +0000 Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a8d56155f51so868320266b.2 for ; Wed, 18 Sep 2024 05:17:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726661858; x=1727266658; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UGc+J/Vc5IXEfvnSzKmcOXqeZLv65qTuMH7OWnhw7gU=; b=Dxo6f8yqury7/MgoWojVSxK+nDVki9TbKKyKfdKIUSH1uMbv5F39lGl07ocfQMmdEX PDLRmV5qpa1baEn/yHIoPCOHjJ3u9XeEElqBGyVydAiZ10ATomCgTx6l4l9wllJL8Fwb 1cjuK+8cTaErw64Z4B/3xj2Ue+7Ig91ObxOpIRxCOyXotxRorhlvyKxmzZsss521M3ef 1jorVey873aszxqUnTfyc75YDW+3ubIs2+q+WlroNzqqIqMoLe8689p7YntPUwX8HP/3 P2uwQFEEhpvX7g+Il6h+OmcxWW+JLTYb8PYgmvXTyiuoYaZoXifVQAcPZVY+i503NxJd huLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726661858; x=1727266658; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UGc+J/Vc5IXEfvnSzKmcOXqeZLv65qTuMH7OWnhw7gU=; b=ObcKlZWRcYcUTfZOThhGKfHvQ+Jb/l9eKX+FqNEI2xKGbo0SWDVnIMOQ2DlM7SA/gf Htquw+nTOY/9QtOLXTv2E22ehNOf19IOMGPNCs7Wh5nicZlOSTR8Pxl0yH46U2kiousa Qtmj7MHydZJDFlx83Cf/fNEOUNqeqSWphALD531JLomt4skHLUoRFr6sNeK6pRCrV2Lo f/q5N/2yJxNo5cKqtTZbI/rNhoPypu2m86Rb9RpU+Dj/Jzn5O6VsIAiKsBdKTbBA1a6D /AafzOJbIAWbtmynEx7qbUJmUxSeTuW4KAN1lKo0vXgVDtkpbfFIQvxudlF+fEewS9c3 U1Jg== X-Forwarded-Encrypted: i=1; AJvYcCVTK/A3n52s+c1AhkZkzsk9Fw6xmAxrlsP6pHg+NvAylPOKAvChuNMI4gPO+T5klOo8UbYeRjvNuBPLxw==@postgresql.org X-Gm-Message-State: AOJu0YwTNI30Mc/EOfDxxGQssuL8a8GHvtxl5Isemnj9cq9r6fs/KNT6 zi5TOhVdVIDJPjeAwFpn6pTxlyzJINii2TCq/jzd0/epW/9R6Vv9C3q4GK8aoIdQ1EaDAEcwLhs tGGD3GOPTpHBhAhDzUGP+Cur7to0= X-Google-Smtp-Source: AGHT+IFrqspxdGjxQqBDOTdP50dDhfKVLx8iVCiUcGEoALv7Z65QVRyA2mxy29hkwnjralWRIWB/69UZ+0ZtRwM8fiA= X-Received: by 2002:a17:907:970c:b0:a8d:128a:cc23 with SMTP id a640c23a62f3a-a902967048amr2363694766b.59.1726661858143; Wed, 18 Sep 2024 05:17:38 -0700 (PDT) MIME-Version: 1.0 From: Wasim Devale Date: Wed, 18 Sep 2024 17:47:28 +0530 Message-ID: Subject: Automatic failback To: Pgsql-admin , pgsql-admin Content-Type: multipart/alternative; boundary="000000000000b3b85e062263cac0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b3b85e062263cac0 Content-Type: text/plain; charset="UTF-8" Hi All I have barman tool in place and can any one suggest automatic failback with zero down time. My PG database is hosted on Linux Red Hat 9. Our all Azure resources are on east region. We are planning to do DR disaster recovery in west region. Thanks, Wasim --000000000000b3b85e062263cac0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All

I hav= e barman tool in place and can any one suggest automatic failback with zero= down time.

My PG databa= se is hosted on Linux Red Hat 9. Our all Azure resources are on east region= . We are planning to do DR disaster recovery in west region.

Thanks,
Wasim<= /div>
--000000000000b3b85e062263cac0--