all of my users have some "home-directory" on a fileserver, which get's backed up to tape every night.
in order to keep the expensive tape backups to a minimum, i'm excluding several directories from the backup, e.g. directories named
this works well.
e.g. if a user decides that they want to make incremental backup snapshots of their desktop machines and store those snapshots on the fileserver, they usually go into such a non-backup folder (as it makes little sense to make backups of backups; and honestly, we currently lack the ressources to backup hundreds of GB of backups of backups per user).
another typical usecase is a user, who needs to share a couple of GB with somebody else, and puts it temporarily on the server, deleting it afterwards (or forgetting about it). i don't want my automatic backup to fetch those file just because they happened to by lying around on the wrong night...
now the problem i'm facing is, that my users expressed their uneasiness about using a directory named "temp" for data that is not to be backed up.
"temp" has a very volatile smell (it sounds like the data might just be gone the next time the server reboots or the sysadmin decides that they would do some cleanup).
so what is the best-practice for directory names that contains data important enough to be stored on some fileserver, but not important enough to go on tape?
a simple solution would obviously be to not backup everything but the data that is in a specially named folder (e.g.
archive), but that would mean a major change in the service which i would like to avoid.