At work we use a NetApp filer which provides snapshots, obviating much of the need for backups against user error. (We do also have arrangements against, eg, a fire consuming the entire building, filer and all).
These snapshots are hourly for 48 hours, daily for a week, and weekly for a month. (There are further snapshots, but not as readily accessible).
I also have no data but I agree with your impression that this better fits the pattern; you either realise you have made a mistake immediately and want a very recent backup, or you realise it much later and want the backups to go back a long way.
Increasingly, however, I find another factor is that most of what I do is in DVCSes, though, which both obviates the need for backups (provided the VCS is properly D) and guards well both against mistakes spotted immediately and ones spotted years later.
Where DVCS lets me down, I think, is that I want to be able to D random intermediate states even if they don't make any sense, without doing a lot of "git rebase -i" afterwards to make the history only consist of working versions.
no subject
Date: 2016-06-06 03:04 pm (UTC)These snapshots are hourly for 48 hours, daily for a week, and weekly for a month. (There are further snapshots, but not as readily accessible).
I also have no data but I agree with your impression that this better fits the pattern; you either realise you have made a mistake immediately and want a very recent backup, or you realise it much later and want the backups to go back a long way.
Increasingly, however, I find another factor is that most of what I do is in DVCSes, though, which both obviates the need for backups (provided the VCS is properly D) and guards well both against mistakes spotted immediately and ones spotted years later.
Where DVCS lets me down, I think, is that I want to be able to D random intermediate states even if they don't make any sense, without doing a lot of "git rebase -i" afterwards to make the history only consist of working versions.