3 ms·

This seems complicated and would still fail if something happens to the host hardware itself right? What about projects like wal-e/wal-g that continuously archi

This seems complicated and would still fail if something happens to the host hardware itself right? What about projects like wal-e/wal-g that continuously archive to cloud storage? https://github.com/wal-e/wal-e https://github.com/wal-e/wal-e https://github.com/wal-g/wal-g https://github.com/wal-g/wal-g

mbrameld 7y ago
It would only fail if the host hardware failed in a way that damaged all three discs, which seems unlikely. It's for data backup, not uptime redundancy.
- mjard 7y ago
  You never know: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00092491en_us https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na...
- bzzzt 7y ago
  A power surge caused by a lightning strike would kill your master as well as your backup. Besides that, do you also keep all your WAL logs so you can roll back an accidentally dropped database?
  - megous 7y ago
    A power surge here where I am may kill the power supply. It's low probability that it would kill everything. Anyway, I don't fear the lightnings/storms/power surges where I am as much as I do the inevitable failures of the storage devices, or kernel bugs. This is just a part of layered protection I have. Offline backups are nice, and I have them too, but they are out of sync all the time by definition. So unless absolutely needed, having a real-time synchronized replica is much more prefered.
megous 7y ago
Looks like an interesting option too. But it's not really complicated. Making a replica is just a few shell commands and two new systemd service files. It's probably simpler than setting up wal-e, especially if you count in the setup and maintenance costs of those cloud accounts, and the need to keep up with regular payments for the services, and recovery not being as simple as switching to an already configured and uptodate replica is.

3 ms·

This seems complicated and would still fail if something happens to the host hardware itself right? What about projects like wal-e/wal-g that continuously archi

by manigandham 7y ago

mbrameld 7y ago
It would only fail if the host hardware failed in a way that damaged all three discs, which seems unlikely. It's for data backup, not uptime redundancy.
- mjard 7y ago
  You never know: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00092491en_us https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na...
- bzzzt 7y ago
  A power surge caused by a lightning strike would kill your master as well as your backup. Besides that, do you also keep all your WAL logs so you can roll back an accidentally dropped database?
  - megous 7y ago
    A power surge here where I am may kill the power supply. It's low probability that it would kill everything. Anyway, I don't fear the lightnings/storms/power surges where I am as much as I do the inevitable failures of the storage devices, or kernel bugs. This is just a part of layered protection I have. Offline backups are nice, and I have them too, but they are out of sync all the time by definition. So unless absolutely needed, having a real-time synchronized replica is much more prefered.
megous 7y ago
Looks like an interesting option too. But it's not really complicated. Making a replica is just a few shell commands and two new systemd service files. It's probably simpler than setting up wal-e, especially if you count in the setup and maintenance costs of those cloud accounts, and the need to keep up with regular payments for the services, and recovery not being as simple as switching to an already configured and uptodate replica is.