On Wed, Oct 14, 2009 at 1:06 PM, Niels Reedijk <niels.reedijk@xxxxxxxxx> wrote: > The issue is the backup procedure. The postgresql documents explicitly > say it is not a good idea to copy a running data directory [1]. > Furthermore, Trac also likes to keep an internal consistency. Now the > irony is of course that it is very hard to get a synchronized backup > of both the database and the trac dir, but I have written a backup > script that first dumps the database and then the trac dir. The > rationale being that when for example an attachment is made during the > database backup, it would not be a problem during restore because it > will only mean that there is a stale file in the trac dir. The other > way around, so if the trac dir is backed up before the database, there > would be a database reference to a non-existing file. The first one > just felt less ... dangerous to me. I think it sounds reasonable to backup the db first. Would it be feasible to temporarily take Trac offline during the backup (I assume it only takes a few minutes) or would that be too risky? - Urias