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 1p57ed-0000Bn-Lq for pgsql-admin@arkaria.postgresql.org; Tue, 13 Dec 2022 15:57:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p57eb-0000rY-F9 for pgsql-admin@arkaria.postgresql.org; Tue, 13 Dec 2022 15:57:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p57eb-0000rP-3V for pgsql-admin@lists.postgresql.org; Tue, 13 Dec 2022 15:57:13 +0000 Received: from mail-ot1-x334.google.com ([2607:f8b0:4864:20::334]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p57eU-0002Bc-Fj for pgsql-admin@lists.postgresql.org; Tue, 13 Dec 2022 15:57:12 +0000 Received: by mail-ot1-x334.google.com with SMTP id l8-20020a056830054800b006705fd35eceso83089otb.12 for ; Tue, 13 Dec 2022 07:57:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=UNb/imHiM21WSFnh/iPlmo/aD51VyhAUVmzdSaYmQ0M=; b=W4rKb4VSuDiJHOySS3kgupHcXuprJZJ+JPT2Cp0BKY5AD5Hxf2CTS7it2KzA1azelq QRtmR2m1zQlhTE4uJbJN5+tQdVTM5gqCe/C1w3e2FN5QGKB166drH30AlKVj6m+EX78y +BihkiZutxHvg3mLW+eeXZIyLSF5IXAKohsqUuFLFNH6Z6VGn9eKeWkpKTTo5mGdSryT PiSv45se5/ggjbiPcTD7uudA16y3PGbLrPvq0x7ZzUL476GIIvSzn2Fb46+kGI67MCVI dbvObCw0EhizVYXIiJC7CjYQK8z2sraHXLlboyPl3tZCkQJ5BgXbHkPfeEtfqWcuE16M oVDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=UNb/imHiM21WSFnh/iPlmo/aD51VyhAUVmzdSaYmQ0M=; b=HRfN0QK/tHGwgRaY1/y68AGjbAlXopunMvfXeWfzLfh4473VoPQjFyGlTVCpYw70Fx rPG77+HLwZ/YQ5ydKQv+z5EmNLxvVLz244epStdRv/fp9V30LKGwl62tSc6s7nyOZAgj U4cTXk/N+PjmAHVbjhkZ3rS+L/Ku7S6Ok+t3mES2yZ+4gWH/C811aBI6RXV5mUe29ajK yQW9FpQFW5ZjDR5p4cx3tftYLrlBO3Z7t2MHN6EmPuFlPz5YMyjsGaU3AhuUIet7HB/d XMT5+YO7THXWk68EpkrlipgXrkP9nzMQ0vUe19HKPblL/z00ll4IhhwGo22ImF2GWIEt CVIg== X-Gm-Message-State: ANoB5pkofUaCiLo3isK9PT/LVHPzAd3j9BYbV3bh7CzXMgGT5Z7s5JzL zOFB97iICubjv12qfe2O3mfYfc/F7hg= X-Google-Smtp-Source: AA0mqf5hLstGmp9aRjkTnSDIB+SgSzGlXimruvBhGGLGaR4hYAf/N8MPlPxxwirawVfHh89mE7n9mQ== X-Received: by 2002:a05:6830:6481:b0:66c:14d8:dbe0 with SMTP id ck1-20020a056830648100b0066c14d8dbe0mr13246284otb.26.1670947025608; Tue, 13 Dec 2022 07:57:05 -0800 (PST) Received: from [192.168.1.66] (108-250-206-84.lightspeed.nworla.sbcglobal.net. [108.250.206.84]) by smtp.googlemail.com with ESMTPSA id g25-20020a9d6c59000000b006605883eae6sm1288655otq.63.2022.12.13.07.57.04 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 13 Dec 2022 07:57:04 -0800 (PST) Message-ID: Date: Tue, 13 Dec 2022 09:57:04 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: WAL replication from an Old Production server Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/13/22 04:16, KK CHN wrote: > List, > > I have to perform WAL Streaming replication configuration for > >  An existing small  production server with 600 GB of size grown over for > two years.  There is no WAL replication in place configured as of now. > > 2. If I want to perform WAL replication to a new Standby Server >     How to copy the 600 GB of DB data  to Standby?   OR when we configure > the WAL replication attributes on primary and standby will the Standby > automatically copy all the 600 GB data to the defined WAL archive dir ? > > Or Do I need to manually copy the data directory of primary by SCP over > NW  or by copying the data directory of Primary to a  USB disk and > manually copy to the  WAL archive_dir folder defined in the standby ?  > What method to follow ? why? > > 3. In WAL streaming replication what ports/protocols are used for copying > the data directory of primary to archive_dir of standby server and for > Streaming ? The Google search "how to set up streaming replication in postgresql 12" answered all my questions. -- Angular momentum makes the world go 'round.