Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

we are using amanda for doing backups at the company I work for. This worked fairly well for long time, but for various reasons the time for a backup run to complete grew quite large in the last few months. Unfortunately I cannot redistribute the data freely at the moment, so the load on the storage is quite high. The idea came up to give users the power to exclude directories from backups on their own, e.g. by touching a file like '.nobackup', or something similar.

Alas, we can't define a folder inside the directories in question that will never be backed up, as this would interfere with the user's workflow.

So far I failed to see a simple solution with amanda that would not resort to letting users somehow define their own dumptype.

Has anybody come across a solution to this?

share|improve this question
up vote 0 down vote accepted

The closest AMANDA gets is a per-client (on the client) exclude list.

So wack together a little cron job that runs shortly before the general time of backups. Do a find through the users' tree (/home/ ?) and add any ".nobackup" files' parent directories to the system's centralized exclude list.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.