Page History
...
Benefits for the DSpace community:
- Allows folks one to more easily move entire Communities or Collections between DSpace instances.
- Allows for a potentially more consistent backup of this hierarchy (e.g. to DuraCloud, or just to your own local backup system), rather than relying on synchronizing a backup of your DB (metadata/relationships) and assetstore (bitstreams).
- Provides a way for people to more easily get their data out of DSpace (whatever the purpose may be).
- Provides a relatively standard format for people to migrate entire hierarchies (Communities/Collections) into DSpace (from another system).
How does this differ from traditional DSpace Backups? Which Backup route is better?
Traditionally, it has always been recommended to backup and restore DSpace's database and files (also known as the "assetstore") separately. This is described in more detail in the Storage section of the DSpace System Documentation. The traditional backup and restore route is still a recommended and supported option.
However, the new AIP Backup & Restore option seeks to try and resolve many of the complexities of a traditional backup and restore. The below table details some of the differences between these two valid Backup and Restore options.
| Traditional Backup & Restore | AIP Backup & Restore |
|---|---|---|
Supported Backup Types |
|
|
Can Backup & Restore all DSpace Content easily | Yes (Requires two restores – one for Database and one for Files) | Yes (Though, will not restore items which are not officially "in archive") |
Can Backup & Restore a Single Community/Collection/Iteam easily | No (It is possible, but requires a strong understanding of DSpace database structure & folder organization in order to only backup & restore metadata/files belonging to that single object) | Yes |
Supported Object Types |
|
|
During a full backup, will backup all Communities/Collections/Items | Yes | Yes |
During a full backup, will backup all People/Groups/Permissions | Yes | Yes |
During a full backup, will backup all Withdrawn (but not deleted) Items | Yes | Yes |
During a full backup, will Backup all In-Process, Uncompleted Submissions | Yes | No (AIPs are only generated for objects which are completed and considered "in archive" |
Based on your local institutions needs, you will want to choose the backup & restore process which is most appropriate to you. You may also choose to use both types of backups on different time schedules. For example, you may choose to perform a Traditional Backup once per week and an AIP Backup on a daily basis. Alternatively, you may perform daily Traditional Backups and only use the AIP Backup as a more "permanent storage" option (perhaps performed on a weekly or monthly basis).
How does this work help DSpace interact with DuraCloud?
...
Overview
Content Tools