Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The DuraCloud user browses the snapshot listings and clicks the "Request Restore" button on a snapshot
  2. The DuraCloud UI calls a DuraCloud Request Restore task, which makes a call to the bridge. The bridge sends email notifications to DuraSpace staff to notify that a restore has been requested the the relevant details.
  3. DuraSpace staff verifies with depositor that a restore is needed, then uses the "Restore" button on a snapshot to initiate restore.
  4. The DuraCloud UI calls a DuraCloud Restore task
  5. 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
  6. The bridge application adds an entry to the restore db table
  7. The bridge application creates a directory in bridge storage and sends a notification to Chronopolis to request a restore action
  8. Chronopolis copies the contents of the snapshot DPN bag(s) to the bridge storage directory
    1. Chronopolis will validate the files on the bridge storage against the manifest in the bag (originally created during the snapshot phase) 
    2. BagIt files are omitted during the copy, leaving only the files which were originally written by the bridge application
  9. Chronopolis makes a call to the bridge to indicate that content has been restored to the expected bridge storage location.
  10. The bridge application verifies restored content against snapshot manifest file and against database listing (ensuring content is consistent with original snapshot data set)
  11. The bridge application copies content from bridge storage to DuraCloud space
  12. The bridge application reads the content metadata file and updates each content item with its metadata values
  13. The bridge application verifies that content transferred to DuraCloud is consistent with the content in bridge storage
  14. The bridge application deletes the directory in bridge storage used for the restore action
  15. 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 removedexpire (and be deleted.)

Panel
titleDatabase 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 ID
    • Source DuraCloud Store ID
    • 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 ID
    • DuraCloud Store ID
    • Start Date
    • End Date
    • Restore status

...