View Single Post
Old 08-24-2014, 06:56 PM   #13
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
I suspect you would get better mileage out of a versioned snapshot system similar to the example I mentioned in post #7

Rather than simply maintaining x versions and firing off a backup script to rotate it, this would create a Time Machine in which you can go back and restore any files you need. The main thing is though, that if nothing changed you do not keep multiple copies, but simply hardlink one copy to multiple locations.

Anyway, using timestamps (like the example) is not only more descriptive, it also reduces the needed commands to two. One to create a new backup, the other to delete all files older than x. (we assume you will notice the problems sometime within a month.)
eschwartz is offline   Reply With Quote