Repository redundancy implementation with comparison between local and remote timestamps of events

A method for repository redundancy in a system which incrementally updates remote clients with events that occurred in a cloud-enabled platform, each remote client being associated with a collaborator, comprises: comparing 720 a local timestamp of an event in an action log with a remote timestamp of the event; and if the remote timestamp is more recent then generating 830 a second event 834 in the action log, which includes a second local timestamp that is updated based on a current time of the system. A system incrementally updates remote clients processes events from an action log, with each log entry including an identifier, a local timestamp, and one or more remote timestamps for an event. A system dispatches events from an action log: when operating in an active mode (Figure 7A), the local timestamp is updated if the remote timestamp is more recent; and when operating in a passive mode (Figure 7B), a remote timestamp associated with an active remote system is copied into the local timestamp. A system comprises a control module to select a data center to act as an active data center upon detecting failure of one or more data centers.