> I am very interested in your opinion on what is best, given the trade off > between how many days to keep, how many to do each day (6, I think) and how > much space there is on the drive.
I wonder whether it would be practical to gradually thin nbackup coverage going back in time, to make older files available without taking up more storage. A natural thing to do would be to coalesce groups of adjacent dumps when they get to a certain age, keeping just one version of each file that changed more than once. I find from poking around that each dump covers somewhat more than 24 hours, so there is a lot of duplication to profit from. I don't know, though, how storage is allocated for dumps. That could make it hard to recycle storage for thinning. And of course thinning would take time, too. Incidentally, the reason I stumbled on the 7-day limit is that I left some untested code changes just before a 10-day vacation, and they were wrong. Questionable practice not to keep a working copy. Will I every learn? Doug
