Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eoy2s-0002q1-BU for pgsql-admin@arkaria.postgresql.org; Thu, 22 Feb 2018 21:04:50 +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 1eoy2r-0001AL-AO for pgsql-admin@arkaria.postgresql.org; Thu, 22 Feb 2018 21:04:49 +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 1eoy2q-0001AB-Tx for pgsql-admin@lists.postgresql.org; Thu, 22 Feb 2018 21:04:49 +0000 Received: from mail-pl0-x243.google.com ([2607:f8b0:400e:c01::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eoy2o-0003cR-CL for pgsql-admin@postgresql.org; Thu, 22 Feb 2018 21:04:47 +0000 Received: by mail-pl0-x243.google.com with SMTP id f23so3588427plr.10 for ; Thu, 22 Feb 2018 13:04:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=JzU5f8kjvKc0oAWyAK5N7/9Xb5q5Dv8CTTK0xT6SRXM=; b=DPo6DljVe0LzQvCSbVmpII6tfHkSE8rSRrrpLB/6qJTgOpQXBSiCD6iC2owE3AFYTq wlYwyhOGoJjzP55i8uBUMp/plBt4oj0EV5ikKQ7njO1odPDVyotG5gZylHiSqxKmtK3l eMo3KL8FOqLCNk6rIK4o8PHsppqkTOZniWElslpVDpnOCfLrHuAMClAlrFUh2Iv9O+aX apUFyMoBsGUnDhDmsm7S8OSgZ09s8t/tDx48WNl0KU2Gr5//rKoG0YUMJaMrXGA02bkc qz+XFGc/Eh9cHhkQvMtX6rwCYQkez/EWVyj/BbryNdxqbo5S5kY5apT1VDPo/6E8l58U z1ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=JzU5f8kjvKc0oAWyAK5N7/9Xb5q5Dv8CTTK0xT6SRXM=; b=F+r9NBY4lG2VfUA4PqQVTV46BDY1hdNTgYUwsBslzohQ3hHECdL28MqsF0zoafbvxC yNpcE13xCd06S5YZloFJml+4ES9Jsn62ZONI5wxScv3IPw/XclqUnII3LwgrRyx1TUC9 CREGbLrqCqsuVDCH28UwUDkaamvrRm3l21aUclKIfaNLNLL6CSyWX8QDmrOQxSqCe5xA 6e41BZ/cc3FdJek/dNVr+WTSvv0o4kO+Pvby3Zv2UDKG2CH+eAYYJngI15wCACkYhuAA 2pcQxguurSkMnT/fdV9SqCq1ZRPOozgA+0vWrNYPCvidMLbKc3LRokXYGioUTsVF225h 2syw== X-Gm-Message-State: APf1xPD1mcPfsH6RTu2HWAAHcImCjYy+uOXg5+ee8GGAbN4yTCLKjPP6 NWo5WvOi/2M1Iqcwxt8loBpvCuPS X-Google-Smtp-Source: AH8x2269tFbI7FNdKhXhpMgnP+ELU4v4eIhtd1liVA7u+ZvVwPqIzQXXYw/L4VeKiPSiPTU9AFTh1w== X-Received: by 2002:a17:902:50e:: with SMTP id 14-v6mr7767240plf.360.1519333484806; Thu, 22 Feb 2018 13:04:44 -0800 (PST) Received: from tim-desktop (2001-44b8-31f2-bb00-dc6d-f5ad-4770-8587.static.ipv6.internode.on.net. [2001:44b8:31f2:bb00:dc6d:f5ad:4770:8587]) by smtp.gmail.com with ESMTPSA id z125sm1351424pfz.27.2018.02.22.13.04.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 22 Feb 2018 13:04:44 -0800 (PST) References: User-agent: mu4e 0.9.18; emacs 25.3.1 From: Tim Cross To: Luis Marin Cc: pgsql-admin@postgresql.org Subject: Re: PostgreSQL Backup Strategies In-reply-to: Date: Fri, 23 Feb 2018 08:04:40 +1100 Message-ID: <87lgfkwxav.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Luis Marin writes: > Dear Friends, > > Please, somebody knows a good source of information about PostgreSQL 9 > backup strategies for production systems, if you have read a good book with > this subject, could you share the author and name of the book ? > For me, the best sources to start with has been the docs on postgresql.org. I think these are some of the best docs for an open source product I've come across. The books I've looked at have been OK, but few have added any real depth of information. These days, your backup strategy will be strongly influenced by your environment (size of databases, data storage infrastructure, whether you have replication/standby systems, rate of change and how frequently you need to backup, uptime requirements etc). Given your question, I would start with just reading the backup and restore section of the documentation and then come back with specific questions. IMO the most important part and most overlooked component of a backup strategy is restoration testing. I've lost count of the number of times I've seen people get into strife because they had what they thought was a comprehensive backup strategy only to find the first time they needed it, it didn't work or was incomplete. Regardless of the strategy you adopt, ensure you do a full recovery from one of your backups to verify your strategy works. Make sure you test the restored system to verify everything is working correctly. Really helps to document things well too - when you need a backup, it is often during a high stress situation and these are the times it is easy to overlook important steps. Having good documentation really makes things easier. regards, Tim -- Tim Cross