The other thing to look at would be using a snapshot of the disk to do your backups. LVM supports this on Linux as does Veritas Volume Manager. Would allow you to take the application out of the loop.
On 11/20/07, Sergey <[EMAIL PROTECTED]> wrote: > > > On Nov 19, 7:54 pm, "Justin R. Cutler" <[EMAIL PROTECTED]> > wrote: > > On Nov 19, 12:55 pm, Jani Tiainen <[EMAIL PROTECTED]> wrote: > > > > > Actually post commit happens atomically (after actual commit has been > > > made to repository). Now if you lock your backup in pre-commit script > > > (that's when commit is starting to be written), and release lock last > > > thing in post-commit you're having pretty much good system. > > > > This does not happen atomically with respect to other processes. > > Justin, > > In pre-commit hook, can you either kill the backup process or abort > the commit if the backup is running? In the former case, as Jani > suggested, you'd have to also set up the lock e.g. in the file system > before killing the backup, and release the lock in post-commit. In the > latter case, aborted commit would invite a developer to commit again > after the backup is over. I know I wouldn't like such a message but if > it's a price to pay for high availability... One of these strategies > should give you the desired inter-process locking behavior I think. > > Sergey. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
