Comment by Eikon
6 years ago
A backup is a replication of the live dataset, although, usually out of sync to be useful when the main dataset goes bad.
6 years ago
A backup is a replication of the live dataset, although, usually out of sync to be useful when the main dataset goes bad.
You might want to read the Wikipedia definition, because you're technically mistaken.
https://en.m.wikipedia.org/wiki/Backup
That's a long article; please quote the part you're referring to so we're all looking at the same text.
> a backup, or data backup is a copy of computer data taken and stored elsewhere so that it may be used to restore the original after a data loss event
Since a "replica" is a copy, that seems technically correct.
all fruits are apples because apples are fruit, right?
2 replies →
I'm not, you can't do backup without replicating data, hence, if you do backup, you are doing replication.
It can be, it just doesn't have to be
Let's say a typical admin of a small shop wants to backup his postgres database.
The first thing he'll use is probably pg_dumpall which he'll output to a storage.
No replication involved. The backup is just a bunch of sql statements to recover the last known state of the database. It's a different kind of format however, which -by definition- isn't a replica anymore.
(And this process has several caveat's-one of which is that it can produce unusable dumps in some rare cases and isn't complete. users, triggers etc aren't dumped iirc.. could be wrong there)
8 replies →
The out of sync part is rather important when something accidently get deleted from the live dataset.