Re: Backup solution over unreliable network - Mailing list pgsql-admin
From | Ron |
---|---|
Subject | Re: Backup solution over unreliable network |
Date | |
Msg-id | d3dd467a-c594-1b15-44bd-1e0a3015832b@gmail.com Whole thread Raw |
In response to | Re: Backup solution over unreliable network (bitcoin wallet <bitcoin-wallet@onmail.com>) |
List | pgsql-admin |
https://pgbackrest.org/configuration.html#section-backup/option-resume
"
Allow resume of failed backup.
Defines whether the resume feature is enabled. Resume can greatly reduce the amount of time required to run a backup after a previous backup of the same type has failed. It adds complexity, however, so it may be desirable to disable in environments that do not require the feature.
"On 9/30/23 13:55, bitcoin wallet wrote:
$ npm install firebaseimport { initializeApp } from from // TODO: const firebaseConfig =V-bUY",authDomain: projectId: storageBucket: messagingSenderId: appId: measurementId: // Initialize Firebase const app) | | Lists: | pgsql-admin |Hello, we've been running our backup solution for the last 5 months to a second site which has an unreliable network connection. We had problems with barman, since it doesn't support backup resume, also no option to disable the replication slot, in the sense, that it is better to sacrifice the backup rather than fill up the primary with WALs and bring the primary down. Another issue is now supporting entirely backing up from the secondary. With barman this is not possible, streaming (or archiving) must originate from the primary.So I want to ask two things here :
From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> To: pgsql-admin(at)lists(dot)postgresql(dot)org Subject: Backup solution over unreliable network Date: 2018–11–30 10:17:27 Message-ID: fb7e7296-c60e-c2cc-93d5–9c2451e9a2a5@matrix.gatewaynet.com Views: Raw Message Whole Thread Download mbox Resend email Lists: pgsql-admin
- Backing up to a remote site over an unreliable channel is a limited use case by itself, it is useful for local PITR restores on specific tables/data, or in case the whole primary suffers a disaster.
Is there any other benefit that would justify building a solution for it?- I have only read the best reviews about PgBackRest, can PgBackRest address those issues?
Thank you! –
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt:root { --main-bg-color: white; --main-color: black; --alternate-bg-color: #f6f6f6; --alternate-color: #222222; --main-border-color: #BBBBBB; --link-color: #627EC9; }html { font-size: 100%; font-family: -apple-system, BlinkMacSystemFont, "helvetica neue", helvetica, roboto, noto, "segoe ui", arial, sans-serif; line-height: 1.4; }body { margin: 0; padding: 1em; background-color: var(--main-bg-color); color: var(--main-color); }blockquote { font-style: italic; margin: 1.5em 1.5em; padding: .5em 1em; border-left: 2px solid var(--main-border-color); background-color: var(--alternate-bg-color); color: var(--alternate-color); border-radius: 3px; }blockquote p:first-child { margin-top: .25em; }blockquote p:last-child { margin-bottom: .25em; }hr { display: block; border: 0; border-top: 1px solid var(--main-border-color); }a { color: var(--link-color); }pre { display: block; overflow: scroll; max-width: 100%; background-color: var(--alternate-bg-color); padding: .5em 1em; margin: 1em 0; border: 1px dotted var(--main-border-color); border-radius: 3px; }code { background-color: var(--alternate-bg-color); color: var(--alternate-color); font-family: Menlo, Courier, sans-serif; font-size: .95em; padding: 2px 3px; border: 1px dotted var(--main-border-color); border-radius: 3px; }pre>code { border: none; }table { margin: 1.5em 0; border: 1px solid var(--main-border-color); border-collapse: collapse; }th { padding: .25em .5em; background: var(--alternate-bg-color); border: 1px solid var(--main-border-color); }td { padding: .25em .5em; border: 1px solid var(--main-border-color); }img { max-width: 100%; }
--
Born in Arizona, moved to Babylonia.
Born in Arizona, moved to Babylonia.
pgsql-admin by date: