Ingest Process Steps
- DuraCloud exposes Chronopolis Staging Storage Provider
- User transfers content into a space in Chronopolis staging storage provider
- User selects option to create a Chronopolis snapshot from space contents
- User is asked for and provides necessary snapshot metadata
- DuraCloud makes space read-only
- DuraCloud makes a call to Bridge Ingest App running on Chronopolis hardware indicating that a snapshot should be taken from a given space with the given metadata
- The Bridge Ingest app:
- Pulls all content from the space to a local mounted file system (bridge storage)
- Stores the snapshot metadata in a file
- Stores the properties for all content items in a json file
- Creates an MD5 manifest of all content, requests a space manifest from DuraCloud and compares the two. Any mis-matches are re-downloaded.
- Creates a SHA-256 manifest of all content
- The Bridge Ingest app notifies Chronopolis (email to start) that a snapshot is ready for ingest, and provides the relative path of the content on the mounted file system (bridge storage).
- Chronopolis pulls all content from bridge storage into Chronopolis preservation storage.
- Chronopolis verifies content against manifest
- Chronopolis creates DPN bags for the content
- Chronopolis notifies DuraCloud that Snapshot creation is complete
- DuraCloud removes all content from bridge storage and from staging storage
- DuraCloud makes space in staging provider available for writes again
- DuraCloud displays the snapshot and the content it contains in a Chronopolis
- Chronopolis creates additional copies of snapshot in secondary nodes and DPN
Note: Terms are defined in the Term Glossary
