Page History

...

In the above example, the package "aip4567.zip" is restored to the DSpace installation with the Handle provided within the package itself (and added as a child of the parent object specified within the package itself). In addition, any child AIPs referenced by "aip4567.zip" are also recursively ingested (the -a option specifies to also restore all child AIPs). They are also restored with the Handles & Parent Objects provided with their package. If any object is found to already exist, all changes are rolled back (i.e. nothing is restored to DSpace)

In some cases, when you restore a large amount of content to your DSpace, the internal database counts (called "sequences") may get out of sync with the handlesHandles of the content you just restored.   As a best practice, it's is *highly recommended to *always* re-run the "update-sequences.sql" script on your DSpace database after a larger scale restore.  This database script can be run while the system is online, and is (i.e. no need to stop Tomcat or PostgreSQL).  The script can be found in the following locations for PostgreSQL and Oracle, respectively:
{{\[dspace\]/etc/postgres/update-sequences.sql}}
{{\[dspace\]/etc/oracle/update-sequences.sql}}

...

• Notice that you are running this command in "Force Replace" mode (-r -f). This is necessary as your empty DSpace install will already include a few default groups (Administrators and Anonymous) and your initial administrative user. You need to replace these groups in order to restore your prior DSpace contents completely.
• <eperson> should be replaced with the Email Address of the initial Administrator (who you created when you reinstalled DSpace).
• <site-handle-prefix> should be replaced with your DSpace site's assigned Handle Prefix. This is equivalent to the handle.prefix setting in your dspace.cfg
• /full/path/to/your/site-aip.zip is the full path to the AIP file which represents your DSpace SITE. This file will be named whatever you named it when you actually exported your entire site. All other AIPs are assumed to be referenced from this SITE AIP (in most cases, they should be in the same directory as that SITE AIP).

In some cases, when you restore a large amount of content to your DSpace, the internal database counts (called "sequences") may get out of sync with the handlesHandles of the content you just restored.   As a best practice, it's is *highly recommended to *always* re-run the "update-sequences.sql" script on your DSpace database after a larger scale restore.  This database script can be run while the system is online, and is (i.e. no need to stop Tomcat or PostgreSQL).  The script can be found in the following locations for PostgreSQL and Oracle, respectively:
{{\[dspace\]/etc/postgres/update-sequences.sql}}
{{\[dspace\]/etc/oracle/update-sequences.sql}}

...