Versions Compared

Old Version 12

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 13

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update outdated section on how AIPs can be backed up to remote storage / DuraCloud

...

Note
titleDon't Forget to Backup your Configurations and Customizations

If you choose to use the AIP Backup and Restore option, do not forget to also backup your local DSpace configurations and customizations. Depending on how you manage your own local DSpace, these configurations and customizations are likely in one or more of the following locations:

  • [dspace] - The DSpace installation directory (Please note, if you also use the AIP Backup & Restore option, you do not need to backup your [dspace]/assetstore directory, as those files already exist in your AIPs).
  • [dspace-source] - The DSpace source directory

How does this

...

help

...

backup your DSpace to remote storage or cloud services (like DuraCloud)?

While AIP Backup and Restore is primarily a way to export your This work is entirely about exporting DSpace content objects to a location on a local filesystem . So, this work doesn't interact solely with DuraCloud, and could be used by any backup storage system to backup your DSpace contents.

In the initial DuraCloud work, the DuraCloud team is working on a way to "synchronize" DuraCloud with a local file folder. So, DuraCloud can be configured to "watch" a given folder and automatically replicate its contents into the cloud.

Therefore, moving content from DSpace to DuraCloud would currently be a two-step process:

  1. First, export AIPs describing that content from DSpace to a filesystem folder
  2. Second, enable DuraCloud to watch that same filesystem folder and replicate it into the cloud.

Similarly, moving content from DuraCloud back into DSpace would also be a two-step process:

  1. First, you'd tell DuraCloud to replicate the AIPs from the cloud to a folder on your file system
  2. Second, you'd ingest those AIPs back into DSpace

(or mounted drive), it can also be used as the basis for ensuring your content is safely backed up in a remote location (e.g. DuraCloud or other cloud backup services).

Simply put, these AIPs can be generated and then replicated off to remote storage or a cloud backup service for safe keeping. You can then pull them down either as an entire set, or individually, in order to restore one or more objects into your DSpace instance. While you could simply backup your entire DSpace database and "assetstore" to a cloud service, you'd have to download the entire database backup again in order to restore any content.  With AIPs, you can instead just download the individual AIP files you need (which can decrease your I/O costs, if any exist) for that restoration.

This upload/download of your AIPs to a backup location can be managed in a manual fashion (e.g. via your own custom code or shell scripts), or you can use a DSpace Replication Task Suite add-on to help ease this process

The Replication Task Suite add-on for DSpace allows you the ability to backup and restore DSpace contents to/from AIPs via the DSpace Administrative Web Interface.  It also includes "connectors" to the DuraCloud API, so you can configure it to automatically backup/retrieve your AIPs to/from DuraCloud.  Installing this add-on means you can now easily backup and restore DSpace to DuraCloud (or other systems) simply via the DSpace Administrative Web Interface.  More information on installing and configuring this add-on can be found on the Replication Task Suite page.(These backup/restore processes may change as we go forward and investigate more use cases. This is just the initial plan.)

Makeup and Definition of AIPs

AIPs are Archival Information Packages

...