Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1liXRt-0004T8-0c for pgsql-admin@arkaria.postgresql.org; Mon, 17 May 2021 07:13:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1liXRr-0006nm-MM for pgsql-admin@arkaria.postgresql.org; Mon, 17 May 2021 07:13:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1liXRr-0006nd-Bn for pgsql-admin@lists.postgresql.org; Mon, 17 May 2021 07:13:55 +0000 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1liXRo-000110-Mq for pgsql-admin@lists.postgresql.org; Mon, 17 May 2021 07:13:54 +0000 Received: by mail-ed1-x52f.google.com with SMTP id v5so5552242edc.8 for ; Mon, 17 May 2021 00:13:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=cybertec; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=mcmhgdMLTZj0tEJ8lfY+PhPg67jaEjNaArAaycrXQuI=; b=UXFqmHepzSGykh6JKonWe17cYN4eEgHZzKRalSWHgKTrU5/TnZ/dDnfzB6SAQSQD5E hgi7u8+yAC7K1mXOfZcNpV5ZvwLmCM6pMwZ3ZwT8tW7PCKSW6w+O7z/RTAtlPS/MHkdN 2Ygcozdn+ydExK5L040NqaZCpejjAJUxGkFAnEQDnqI4cA9ry4b5MvDfM0TEEjFVwRg/ NFgRf+n4EGDekoJ1C2bQ9HWiPuuB2Kw9+nHtBcgWrbXJgvrAezgzofSCgGGSBCvQvOCz SbXNc5iYDzZWamDjzdxfYtPPf8HsiwSeteWALj8BFAb8+keFtZQMsP0iS3hQYSPo8v/a C/2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=mcmhgdMLTZj0tEJ8lfY+PhPg67jaEjNaArAaycrXQuI=; b=mLWH5kn6x4cLMKoAxquntztKK/E1GaQ19kiJ2OCwhYeRzBxIuhX//KjbH5lqylzCRC FcRvzSfQxiV/hYv+kNWh2A+3ZL8FjILTBIMLLLgl3WA4bPJxoe0AOV4EBh4V22dzNHBx +E34rBSwfK8/u+8HhHZtVDvOFQaSzBw0SmNfVd/NBxDg9JuPkH42aCc9tRpIB1d+gnhc fFtv3mvuK5SL0WQE0rmVEMnrRksHntnPvB+Z7R+w9TfIWCYlnIXUgj/tQ+z6Tx5IfrLO Fm7kTO5lS/j2ijtRoVN0XhsFonHJ+zU3int31PGNTPYjFhrLzaIapmb+WdKR8cBu1nIi N5bA== X-Gm-Message-State: AOAM5322M+zhHFeifTftzjY+aQX278R2Ab3gqM0xfdtKfQEstxKfh6fj RiSvjkLETnVrbH8Y8r66Aftkto6eY8R/Nw== X-Google-Smtp-Source: ABdhPJyp87rzp6mE4imPRqF2SAuLm0szOQajp+E3XrXE3BkxdWPGybMCuDMG8FMYRRBsmoFjAQUkWQ== X-Received: by 2002:a05:6402:1ac7:: with SMTP id ba7mr13323933edb.299.1621235630476; Mon, 17 May 2021 00:13:50 -0700 (PDT) Received: from localhost.localdomain (217-149-175-144.nat.highway.telekom.at. [217.149.175.144]) by smtp.gmail.com with ESMTPSA id b25sm10549946edv.9.2021.05.17.00.13.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 May 2021 00:13:50 -0700 (PDT) Message-ID: <9175f85da7de964578bf1d21e8974eeb9888ed78.camel@cybertec.at> Subject: Re: How to replicate 2 nodes parallel From: Laurenz Albe To: Suraj Sawant , pgsql-admin@lists.postgresql.org Date: Mon, 17 May 2021 09:13:49 +0200 In-Reply-To: <81c859ff-3ff5-4525-9fc9-b2394a8e803a@email.android.com> References: <81c859ff-3ff5-4525-9fc9-b2394a8e803a@email.android.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, 2021-05-16 at 01:02 +0530, Suraj Sawant wrote: > I'm using PostgreSQL 12.5, for HA setup I'm using 3 poatgresql nodes. > > For that I need to take 'pg_basebackup' on two nodes simultaneously from my Master node. > > Is there any option available to take 'pg_basebacup' parallel and then make it in A-B-C format > i.e. A -> Master > B -> Slave > C -> DR. Since "pg_basebackup" uses the non-exclusive backup method, you can run two such backups concurrently. However, there is no way to have it run a backup with several parallel processes to speed up the procedure. The high availability setup will require thrid-party software, since PostgreSQL has no built-in clusterware. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com