Justin R. Cutler kirjoitti: > > > The Trac repositories in question are on a system with nearly complete > redundancy in all areas. The backups are placed on a machine that can > be swapped for the main system in under 2 minutes. This is not because > I do not trust my users or my hardware, but because this system is > managing very high assurance projects that require what you may > consider excessive data integrity restrictions.
Oh well... I need to improve my reading skills a bit :) Above chapter explains pretty well why you're having these problems in first place. So you're running (in theory) two identical systems that one is master, one is slave and master is always pushing all changes to slave at regular (hourly) intervals? Now you're having such a busy and mission critical system that frequently your backup data integrity is compromised? Commit happens in the middle of backup-process. You could also see CODA <http://www.coda.cs.cmu.edu/mirrors.html> -- 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 -~----------~----~----~----~------~----~------~--~---
