To bring up a new site or recover a failed site, I need an inter-site state transfer mechanism for synchronizing keys.

Note that initially, this should a manual process that is invoked on one site to one of its configured backups.

This should be based on the non-blocking state transfer mechanism for consistency.

The pseudo-design may look similar to the following:

• Manually invokable, background thread
• Since the bridge end is open, there are writes happening to keys. Keep track of the puts/removes on the main data owner.
• Iterate through the key set.
• If the key has already been modified since the process started, discard.
• Else synchronously write the key value in a TX context