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 1l8QtN-0004Yt-2I for pgsql-admin@arkaria.postgresql.org; Sat, 06 Feb 2021 16:57:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l8QtL-0005p7-V2 for pgsql-admin@arkaria.postgresql.org; Sat, 06 Feb 2021 16:57:03 +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 1l8QtL-0005oz-C1 for pgsql-admin@lists.postgresql.org; Sat, 06 Feb 2021 16:57:03 +0000 Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l8QtI-0000Zu-Cz for pgsql-admin@lists.postgresql.org; Sat, 06 Feb 2021 16:57:02 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=FkbzBDqHOgQDFmnAW8q/t/151Nvldzh5U4LrpIhGPaQ=; b=OYKDezJWKs8J0It5ZmnXxj9Pz/ 3e25JcIjN4O50sJW1pBj+2WQlaxL6clhrNPJJmYp590gIKDef+X4K4pDK38IbY/ZOb0Fdq9UxsbSX OIckoqD9pUzgYQkb07wK/bhsJzakSlpsd014fJENkk0UkTz4eD62QkeRjSVom9OoPIyU=; Received: from vas by admin.sibptus.ru with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1l8QtF-0002kb-LT for pgsql-admin@lists.postgresql.org; Sat, 06 Feb 2021 23:56:57 +0700 Date: Sat, 6 Feb 2021 23:56:57 +0700 From: Victor Sudakov To: pgsql-admin@lists.postgresql.org Subject: Re: wal-g (https://github.com/wal-g/wal-g) reliability Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://admin.sibptus.ru/~vas/ X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello Nikolay, Thank you for the comprehensive reply. Nikolay Samokhvalov wrote: > In short, it's reliable and battle-tested. It's used in companies such as > Yandex.Cloud and GitLab.com, successfully. > > You can find materials about it from Yandex.Cloud -- for example, from > Andrey Borodin who is one of WAL-G maintainers. He is a frequent guest of > our online community sessions -- see https://YouTube.com/RuPostgres (in > Russian). > > Additionally, you can reach out to the people who use WAL-G here: > - Postgres community Slack > https://postgres-slack.herokuapp.com/, it has WAL-G channel (English) > - Postgres telegram group https://t.me/pgsql (Russian). > > Despite talking to others, I strongly recommend having periodical (say, > daily) automated verification jobs that check your backups -- this is both > useful to start trusting the backup tool and to ensure that your backups > are in a good shape. Without automated verification, a DR strategy is > definitely incomplete. > > That being said, it's not a small project so it may have issues depending > on how you use it. Among possible caveats: if you use it in Google Cloud, > you might have issues with backup-push failures when GCS has instability > events -- this was fixed in the very recent codebase. Also, there are some > issues on AWS for the new codebase that are reported for the master, but I > don't have details (I suppose using some older version should be better > here). > > On Fri, Feb 5, 2021 at 01:54 Victor Sudakov wrote: > > > Dear Colleagues, > > > > What do you think of wal-g? Can you entrust your data to it? Has it ever > > failed you? Any hidden caveats? > > > > -- > > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > > 2:5005/49@fidonet http://vas.tomsk.ru/ > > > > > > -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/