3efcc957d6
On our zuul-scheduler host the /root/.bup dir is extremely large. On closer examination this appears to be due to large file indexes. Looking at the host we've noticed that we are backing up the status.json backups as well as job runtime files which can and do change frequently which could lead to very large file indexes. We don't actually need to back these up permanently so exclude them from bup's list. the /var/lib/zuul/backup dir contains status.json backups which are really only useful in the immediate time frame and the times db is something we can live without if we lose it (we'll just build a new one). Change-Id: Id3029eec3a6478c496712876b9ec753029313efa
26 lines
371 B
Plaintext
26 lines
371 B
Plaintext
/proc/*
|
|
/sys/*
|
|
/dev/*
|
|
/tmp/*
|
|
/floppy/*
|
|
/cdrom/*
|
|
/var/spool/squid/*
|
|
/var/spool/exim/*
|
|
/media/*
|
|
/mnt/*
|
|
/var/agentx/*
|
|
/run/*
|
|
/root/backup-restore-*
|
|
/root/.bup
|
|
/etc/puppet/modules/*
|
|
/etc/puppet/hieradata/*
|
|
/var/cache/*
|
|
/var/lib/docker/*
|
|
/var/lib/puppet/reports/*
|
|
/var/lib/postgresql/*
|
|
/var/lib/lxcfs/*
|
|
/var/lib/zuul/backup/*
|
|
/var/lib/zuul/times/*
|
|
/opt/system-config/*
|
|
/afs/*
|