[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-developers] Re: Ideal backup method
- Subject: [cobalt-developers] Re: Ideal backup method
- From: Bruce Timberlake <bruce@xxxxxxxxxx>
- Date: Sun Jan 26 23:23:00 2003
- Organization: BRTNet.org
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Sounds a bit scary to me... If you're hacked on the 30th, you have
> to go all the way back to the first of the month?
No, I don't think so. Using rsync to send file 'diffs' each day,
you're making a new 'copy' (updating the remote copy) of any local
files which have changed since the day before (or since whenever the
'remote' copy was created).
The downside to this is that if you _are_ using the same 'target'
directory to send your backups to (or compare 'local' files to for
diff-ing purposes), you don't have multiple discrete versions of each
file (like with a traditional rotated backup). The remote version
will either the same as the local version (post-synch), or is only
different by the 'diff' between the two (pre-synch).
So you would have the potential to 'infect' or break the 'remote' file
copy if you didn't notice a problem with the local file copy before
the scheduled backup/synch happened.
- --
Bruce Timberlake
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD4DBQE+NN4pvLA2hUZ9kgwRAvNIAJUdwV64m4oC9mbC8VIZUjjT9ffkAJ4z9fja
L/FyNp845jrFHpnmLhyM1g==
=SWAi
-----END PGP SIGNATURE-----