Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ePP8R-0003C3-H8 for pgsql-admin@arkaria.postgresql.org; Thu, 14 Dec 2017 08:44:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ePP8Q-0008Do-M5 for pgsql-admin@arkaria.postgresql.org; Thu, 14 Dec 2017 08:44:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ePP8Q-0008Dd-99 for pgsql-admin@lists.postgresql.org; Thu, 14 Dec 2017 08:44:54 +0000 Received: from mail-wr0-x243.google.com ([2a00:1450:400c:c0c::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ePP8M-0006fZ-D4 for pgsql-admin@postgresql.org; Thu, 14 Dec 2017 08:44:52 +0000 Received: by mail-wr0-x243.google.com with SMTP id z34so4429262wrz.10 for ; Thu, 14 Dec 2017 00:44:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:from:to:references:in-reply-to:subject:date:mime-version :content-transfer-encoding:thread-index:content-language; bh=Zw2VpuxqVZ0jwNQUYDfGx1PNFSAszfQug0SVjOH+l3s=; b=ihR6CC/MUenSZIun0I5U4qhYOGLg3NLhPj/bax3Tsy+kzgBZZ4u8xJy3rkgDgJDZ6m lxik7axXS200mcD8brT7M34R3p6gaCIjHRKqkyF1+A7UMIn7df7v+94VOhlOcjK43vOB O0n/ZlGzQV33hagK807UYwPG7ysW7Ls5Kyosq2ADM/UoQac3dR/Vp+1QbzoMNq+yVVKp aIyFyYFZxuJtI4FOu2g3Ox1ZNnFAfKBLmaszUdN6T7VSwS4xlUAgiB03IaPPlNpwa2Mh Rq7ky5TIV+60Sga3OiOiH33fRmknrO+28cqqFF+F0LYL/jB25WIuc+fsRb3OvnvNVplw SIFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:from:to:references:in-reply-to :subject:date:mime-version:content-transfer-encoding:thread-index :content-language; bh=Zw2VpuxqVZ0jwNQUYDfGx1PNFSAszfQug0SVjOH+l3s=; b=rCRxbnBsCm2DP+HsWeVDzfi5vEKt+T7AcKjONfHMLGAvs0v6+XK7hpnIXXF3xPLFH6 9THy1JP/l9U5yKD0uu997hDTJtGpmd8hwcwAZa6Plx80/80MpBLc2mTkUMH8koXr4cZR t4rYYn5+zpFU4PyVrg43UZ17AIB8fqEvQyCGVX7pXalxsi9h10+uJCuGPO4KGEMp7QAU VBQiETrZ370L1fRv9hC2yysDFLm0PDqpbl/MTS/OXwSO1zSD9W5XYoceumqm5lC8x9p2 lwY2hDeR2Z4HjYfF32kqcgwGVlq+cgifCedx6JWvnpxOXQwtQBrdcbucdya8brMbe7bz xKkA== X-Gm-Message-State: AKGB3mLeawUyAFVX2V5HMjLhsvMR4ZoqcyCwvLp1P7nsPPBejTytPH+T kG0d/ulvAlXUlg8Pe8kmQMJJQg== X-Google-Smtp-Source: ACJfBosH+vNB48UF+zr0pk+RZJaTzIhkVrYGLL+o3pxlFOwpbmlKGeHkjaSz4RvjSyTXcjUwnlZrQw== X-Received: by 10.223.166.51 with SMTP id k48mr4900637wrc.125.1513241088443; Thu, 14 Dec 2017 00:44:48 -0800 (PST) Received: from PADOUE (mau78-1-88-184-109-217.fbx.proxad.net. [88.184.109.217]) by smtp.gmail.com with ESMTPSA id i65sm12632817wme.20.2017.12.14.00.44.47 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 14 Dec 2017 00:44:47 -0800 (PST) Message-ID: <5a3239ff.449f1c0a.996bb.4359@mx.google.com> X-Google-Original-Message-ID: <043d01d374b7$c9f8a870$5de9f950$@lepretre@gmail.com> From: =?utf-8?Q?Olivier_Lepr=C3=AAtre?= To: "'pgsql-admin'" References: <38c84302-270e-a2b6-648f-26ba798d8787@propaas.com> <1513239540.2442.22.camel@cybertec.at> In-Reply-To: <1513239540.2442.22.camel@cybertec.at> Subject: RE: virtualized snapshots and PITR Date: Thu, 14 Dec 2017 09:44:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdN0tEOLzwxarHD3TQKHdzcqfEYHEwAA1liA Content-Language: fr X-Antivirus: Avast (VPS 171212-0, 12/12/2017), Outbound message X-Antivirus-Status: Clean List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk As I was not aware of this command I searched for it and found this interes= ting blog. https://blog.2ndquadrant.com/what-does-pg_start_backup-do/ Olivier -----Message d'origine----- De : Laurenz Albe [mailto:laurenz.albe@cybertec.at] Envoy=C3=A9 : jeudi 14 d=C3=A9cembre 2017 09:19 =C3=80 : PropAAS DBA; pgsql-admin Objet : Re: virtualized snapshots and PITR PropAAS DBA wrote: > we have a client using veeam to do vmware snapshots of the db servers, > unfortunately as far as I can tell any restore of a veeam snapshot > also restores the state, which means the db gets restored in an online st= ate. > As far as I know, once the db is online we cannot force it back into > recovery mode to do a PITR recovery, correct? > > Anyone know of a way to do PITR recoveries with veeam? It is fairly simple. Before the snapshot, run SELECT pg_start_backup('label of your choice', TRUE); After the snapshot, run SELECT pg_stop_backup(); Yours, Laurenz Albe --- L'absence de virus dans ce courrier =C3=A9lectronique a =C3=A9t=C3=A9 v=C3= =A9rifi=C3=A9e par le logiciel antivirus Avast. https://www.avast.com/antivirus