ICP.Lab Storage & Scalability Summaries

[domwoe]

@domwoe

Backup and restore

• There’s an overwhelming interest in support for backups.
• Most of the support for snapshotting revolves around the use case of recovering from bad upgrades.
• Having irregular upgrades (last month, last week, last day, last few hours) would be a good cadence.
• There are user-level solutions for backups as well as a protocol level-solution. The community is mostly leaning towards a protocol-level solution.
• There’s interest in forking (i.e. the ability to spin up a snapshot as a separate canister).
• The minimum required on the protocol level is the ability to take snapshots of a canister when it is stopped, and forking from an existing snapshot. Besides that, it would be great to allow downloading and uploading the snapshots.
• There’s interest in a System API call for freeing stable memory.

Update on one of the key topics from the ICP.Lab on Storage & Scalability: Canister backup and restore [Community Consideration]