Implement backup and restore
The idea is to have a way for a Signify client to backup all its information held by KERIA and be able to restore it into another instance of KERIA. It can be seen as a backup of KERIA, but also as a portability feature so a client can move away from a KERIA agent to another.
Also, consider this discussion (OWF, Aries, etc are all interested in some kind of standard for a wallet backup) https://hackmd.io/eJbWrh7BSiaJXkP-p0Q5mg?view
The KELs at least already have a backup feature. You just play a KEL to a file (using one of the clone methods on a Baser object) and then replay it into the new database.
see Baser.cloneAllPreIter()
From our keri dev meeting: This is a BIG discussion. Multi-sig you can rotate new members but you need the credential registry, and you need to identify as your local registry. KERIA has a temp endpoint solution. If you stream over contacts this is potentially an attack vector. Technically a simple tar file can be a backup. The migrations were from old-command-line to the keria/signify wallets and so that solution isn't the same.
From our dev meetin: We should consider a similar discussion about hotfailover and failover. @edeykholt will create and issue and we'll rank it.