Greetings,
* Phil Endecott (spam_from_pgsql_lists@chezphil.org) wrote:
> David Steele wrote:
> >pgBackRest has done this for years and it saves a *lot* of headaches.
>
> The system to which I am sending the WAL files is a rsync.net
> account. I use it because of its reliability, but methods for
> transferring files are limited largely to things like scp and
> rsync.
You might consider using a well-tested PG backup tool locally and then
simply rsync that backup over to rsync.net. Certainly with pgbackrest,
we intend and expect people to use more routine "just copy all the
files" backup methods for backing up the repository.
Basically, you could pgbackrest to /some/local/path and then rsync from
there over to rsync.net.
Having an rsync or scp 'storage' option (similar to the s3 one) for
pgbackrest might be interesting.. We discussed having the ability to
start a backup from the PG server at one point but in that discussion
we were thinking pgbackrest would also be installed on the backup
server. This would be different from that in that the remote side would
only need to support rsync or scp. You'd have to accept that if the
the backup server dies then you lose data though, since I don't believe
there's a way to ask for an fsync() through rsync or scp, which makes it
a much less compelling feature, unless rsync.net guarantees writes
somehow..?
Thanks!
Stephen
