Export Hyperbee Snapshots to IPFS and Regularly Check Backups

[katelynsills]

User Story

As an archiver, I can ensure that if my hyperbee server goes down and I somehow lose all of the data that was on the server, I can ensure that I can restart the hyperbee with a backup from IPFS that was taken on a regular TBD schedule (every week?). Additionally, I will encourage other organizations to have local copies of my Hyperbee instance through the Hyperbee protocol replication.

I have an internal procedure to regularly check backups and attempt to restart with them to ensure the backups are being done correctly.

Methods

Hyperbee has a snapshot mechanism which produces a file that can be pinned to IPFS (and we can pay for pinning services to retain the file).

Additionally, please see #16 for an analysis of how our current usage of dag-cbor could set us up nicely for adding the attestations themselves to IPFS, and for making the snapshots legible to IPFS in the future.

[makew0rld]

Hyperbee has a snapshot mechanism which produces a file that can be pinned to IPFS

I'm unable to find info on this. I see that hyperbee has a .snapshot() method, but that just returns another Hyperbee object to use, not an export file. I think the simplest way to actually put a snapshot on IPFS would be to just upload the hypercore folder and the four standard files it contains. This data folder does not contain any private data like private keys, so it should be safe to upload.

This makes the backup process simple: running ipfs add on the folder and sharing the resulting CID.