Justin R. Cutler kirjoitti: > I presently use the Trac post commit hook as a convenience for > developers, but it does lead to an interesting backup issue: > > If I don't use the hook script, I can always do a hotcopy based backup > that is consistent by doing a hotcopy of the Trac environment followed > by a hotcopy of the Subversion repository. Upon restore I just need to > remember to do a trac-admin resync. > > When I do use the hook script, it is possible for the hook script to > have not yet happened when I back up Trac, and the commit to be done > when I back up Subversion. If I reverse the order, it is possible for > the message generated by the script to exist without the commit. > > For now, I have to shut down the server to do the backup in order to > guarantee data consistency. As I have many Trac/Subversion based > projects on the system, this leads to appreciable downtime. > > Normally, I would post this to trac-users, but I am interested in > seeing if I can develop a workaround by migrating the post commit > script functionality into Trac's version control API. This would allow > me to keep my previous backup system, as ticket updates would happen > upon the trac-admin resync operation (as needed). Unfortunately, it > looks like the Changeset object of the versioncontrol API does not > really allow for custom extensions.
You don't need to develop fancy. Just make pre-commit-hook to lock your backup script and post-commit-hook to release it. and you're done. Now you have made your backups as atomic too. -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
