Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42306=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1WSDe8-0000aE-PW
 for pgsql-admin@arkaria.postgresql.org; Mon, 24 Mar 2014 22:47:08 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42306=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1WSDe8-000210-42
 for pgsql-admin@arkaria.postgresql.org; Mon, 24 Mar 2014 22:47:08 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <cs_dba@consistentstate.com>) id 1WSDe6-00020r-3l
 for pgsql-admin@postgresql.org; Mon, 24 Mar 2014 22:47:06 +0000
Received: from mail-qg0-f41.google.com ([209.85.192.41])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <cs_dba@consistentstate.com>) id 1WSDdx-0006Cs-K9
 for pgsql-admin@postgresql.org; Mon, 24 Mar 2014 22:47:03 +0000
Received: by mail-qg0-f41.google.com with SMTP id i50so18700767qgf.0
 for <pgsql-admin@postgresql.org>; Mon, 24 Mar 2014 15:46:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :subject:content-type:content-transfer-encoding;
 bh=O5b0ORB2V1+hSY78+anNES18iPkpko/4z9Y0+TnT63U=;
 b=lIeOFkE7s9QU9P+Hd4YzYaK4itTB3YVQAxBKBk5cqk1paLYT8pHuXodRYdDCVUpMcY
 B0VZ1Q+gOIvo/W4v2awxwnh9puoocRWxC1NdVK4a2csDsoK5zpUCSYLv4RdBG+3nrOnE
 TxFN/D6TBZAeSG1880PJNBc1x14I1pN3K1VGZkqtfS7nhJet1mzQoV5ItVW6mb1tLc4C
 Hu3boBjmE/Cs+9FVqu40eHwYH/WiFTIUKW289T8RgDxr3QNMldYhNFQH+d00c4mI73ci
 0kbU+ARs6jQr3K5KzO9SjDEty6k84ELHtNAc2tORvRUXAulX4oJkYDEnXQPh+JzHy0e7
 T5vw==
X-Gm-Message-State: 
 ALoCoQlYHaNXlaVqhhg/FZQ92tFk3t4/Q4getiBdosnOYbqhkRjo26hcd3O85mKDfl5Sp5+hYW+n
X-Received: by 10.224.46.73 with SMTP id i9mr78299300qaf.65.1395701215747;
 Mon, 24 Mar 2014 15:46:55 -0700 (PDT)
Received: from Issac.consistentstate.com
 (216-98-193-98.static.forethought.net. [216.98.193.98])
 by mx.google.com with ESMTPSA id 21sm23905606qgh.23.2014.03.24.15.46.54
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Mon, 24 Mar 2014 15:46:54 -0700 (PDT)
Message-ID: <5330B5DD.7030805@consistentstate.com>
Date: Mon, 24 Mar 2014 16:46:53 -0600
From: CS_DBA <cs_dba@consistentstate.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: copy / backup question - copying a data directory while the db is
 shutdown
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi All;

If I shutdown a HOT standby slave (via the -m fast command) can I then 
copy the data directory to a "backup" location and be guaranteed that 
the backup copy will start?

For some reason I thought there were issues (or potential issues) with 
this method and a PITR based recovery approach was a better guarantee 
that the copy will start


Thoughts?



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin