Talk:1718: Backups

Explain xkcd: It's 'cause you're dumb.
Revision as of 18:59, 11 August 2016 by (talk)
Jump to: navigation, search

I think this makes more sense if only a small portion of all files from the laptop complete the ENTIRE loop. if the total percentage of files which complete the entire loop is 0.0004% , and he backups once a month, that should give him exponential growth slightly smaller than Moore's Law. At 18 months, his total file size would be about 168% of the original. 22:03, 10 August 2016 (UTC)

Also, the title text my refer to that often when you lose a project and have to start over from scratch, the project become so much better. 01:55, 11 August 2016 (UTC)

This happens. It can really surprise you when the exponential curve is flat enough. We had a case where we kept a log of the backups on a server that was backed up. This went fine for years, until at some point when we ran out of backup space we found that backups of the logs of backups consumed over 99% of our diskspace. 10:04, 11 August 2016 (UTC)

Tee hee! This is why the first thing I exclude from backup is the log directory, or the whole /var tree (with a few selected exceptions, like /var/spool/cron/crontabs - this is a royally misplaced location, it should go under /etc). The logs that need to be kept are sent to a log server, online, by the logger daemon itself. If there's no log server (small systems) at least send the logs to backup place during log rotation. -- 18:59, 11 August 2016 (UTC)
I once managed to backup / to the backup disk at /media/Backup Disk. D'oh. Backupception. -- 12:17, 11 August 2016 (UTC)