You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 1, 2021. It is now read-only.
If a location loses the local event log (including backups) due to a disaster it can recover events from other locations through replication connections. This will recover all events stored at remote locations (considering replication filters). Depending on the number of events to be recovered this can take a significant amount of time where the location is not available. Especially in the case of locations that are using event deletion it can make sense to recover not all but just the most recent events. So disaster recovery should allow the location to be recovered to specify a limit for the events to be recovered, for example in form of sequence numbers in the remote logs (so event recovery begins from this sequence number).
If a location loses the local event log (including backups) due to a disaster it can recover events from other locations through replication connections. This will recover all events stored at remote locations (considering replication filters). Depending on the number of events to be recovered this can take a significant amount of time where the location is not available. Especially in the case of locations that are using event deletion it can make sense to recover not all but just the most recent events. So disaster recovery should allow the location to be recovered to specify a limit for the events to be recovered, for example in form of sequence numbers in the remote logs (so event recovery begins from this sequence number).