Page History

...

The DuraCloud user browses the snapshot listings and clicks the "Restore" button on a snapshot
The DuraCloud UI calls a DuraCloud Restore task
The DuraCloud Restore task creates a space where the restored content will be placed and calls the bridge application with a restore request
1. A bucket policy will be added to the space to delete content after a set time period (3 weeks? a month?)
The bridge application adds an entry to the restore db table
The bridge application creates a directory in bridge storage and sends a notification to Chronopolis to request a restore action
Chronopolis copies the contents of the snapshot DPN bag to the bridge storage directory
The bridge application copies content from bridge storage to DuraCloud space
The bridge application reads the content metadata file and updates each content item with its metadata values
The bridge application verifies (based on manifest) that content transferred to DuraCloud is consistent with the content that was originally in DuraCloud (pre*-snapshot)
The bridge application deletes the directory in bridge storage used for the restore action
The bridge application notifies the user who requested the restoration that the process is complete, informs them of the space ID where they can find their content, and tells them the date on which the content will be removed

Panel

title	Database

...

Tables

DB

Table to capture spring batch processing (states)
Table to capture snapshots
- Snapshot ID
- Snapshot date
- Source DuraCloud Host
- Source DuraCloud Port
- Source DuraCloud Space
- Number of content items in snapshot
- List of duracloud accounts for which the snapshot is visible
- Snapshot status
Table to capture content items
- Snapshot ID
- Content ID
- Content Metadata List (serialized)
Table to capture restore actions
- Snapshot ID
- Restoration ID
- DuraCloud Host
- DuraCloud Port
- DuraCloud Space
- Start Date
- End Date
- Restore status

Panel

title	Interface Points - APIs

Create snapshot (space ID)
- create snapshot properties file, store it in space
- space transitioned to read only
- call made to bridge API to create snapshot
Get snapshot status (snapshot ID)
- call made to bridge for status
Complete snapshot (snapshot ID, space ID)
- set bucket deletion policy
Get list of snapshots
- call to bridge for snapshot list, formats results
Get list of content items (snapshot ID, offset, maxresults)
- call to bridge for content item list
Restore snapshot (snapshot ID)
- verify that a
- create a space for the snapshot to be placed into
- call to bridge to restore
Get restore status (snapshot ID)
- call made to bridge for status

Create snapshot (host, port, spaceID, snapshotID)
- create snapshot db entry
- copy content to bridge storage
- create a manfitest for content
- notify chronopolis that snapshot is ready for storage
Get snapshot status (host, port, snapshot ID)
- query snapshot status from the db (and from chronopolis, depending on status)
Snapshot storage complete (snapshot ID)
- delete content in bridge storage
- call task to indicate that snapshot is complete
- notify end user that snapshot is complete
Get list of snapshots (host)
- Queries db for snapshot list available to host
Get list of content items (snapshot ID, offset, maxresults)
- Queries db for content item list for the given snapshot ID
Begin Restore snapshot (host, port, spaceId, snapshot ID)
- create restore db entry
- create a directory on bridge storage
- requests restore from chronopolis
Restore snapshot (
- copy content to Duracloud
- update content metadata
- verify restored content
- delete content on bridge
- notify end user that restore is complete
Get restore status (host, port, snapshot ID)
- query restore status from the db (and from chronopolis, depending on status)