Page History
...
| Traditional Backup & Restore (Database and Files) | 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/Item 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") |
During a full backup, will backup all local DSpace Configurations and Customizations | Yes (if you backup your entire DSpace directory as part of backing up your files) | Not by default (unless your also backup your entire DSpace directory) |
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).
...
Overview
Content Tools