# ICP.Lab Storage & Scalability Summaries

**URL:** <https://forum.dfinity.org/t/icp-lab-storage-scalability-summaries/20242>\
**Category:** Developers\
**Created:** [May 25, 2023, 11:46am UTC](https://forum.dfinity.org/t/icp-lab-storage-scalability-summaries/20242 "2023-05-25T11:46:29Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\
**Post date:** [September 6, 2023, 8:21pm UTC](https://forum.dfinity.org/t/icp-lab-storage-scalability-summaries/20242/16 "2023-09-06T20:21:26Z")

</div>

> [@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]](https://forum.dfinity.org/t/canister-backup-and-restore-community-consideration/22597)

---

_[View the full topic](https://forum.dfinity.org/t/icp-lab-storage-scalability-summaries/20242)._