---
# System prepended metadata

title: Archive/restore/check storage scenarios

---

# Archive/restore/check storage scenarios
- [x] archive from connect - check storage (optional) - file status is **Archived** (check storage step is not required for file status update)
- [x] restore from connect - check storage (required in order to update the file status) --> restore started, ingest triggered and status set to **Ingest completed**
- [x] archive from s3 - check storage in connect (or refresh the page) --> file status is set to **Archived** in connect 
- [x] restore from s3 - check storage in connect (or refresh the page) --> restore started, ingest triggered status set to **Ingest completed**
- [x] archive from connect - overwrite in s3 - check storage in connect -> file status will be missing for for 1-2 sec, but ingest is triggered and status set to **Ingest completed**
- [x] archive from s3 - overwrite in s3 - check storage in connect -> file status will be missing for for 1-2 sec, but ingest is triggered and status set to **Ingest completed**
- [x] preview cache, file details and workbench details are kept at archive/restore (not implemented for CPLs)