redundant share server.

[bsutton]

We need to develop a design which allows the share server to be redundant - i.e. run across multiple machines.

One issue is that a user shares an identity - it is processed on server X - then server X goes down then the accepted goes to server Y and the key is not there.

I can think of a couple of options.

• second server is a hot standby with the primary doing background replication to the secondary
• we develop a hot/hot pair which use a secure channel to share the keys between each other in near real time.

We need a recovery path after a failure and the ability for a server to run in standalone mode.

Other suggestions?

[bsutton]

on restart we should validate the db is intact - maybe use checksums so this doesn't take too long.

If the db is corrupt then truncate it and re-initialise it.