Unable to restore site wide AIP backup

[Ashim Kapoor]

Dear All,

I created an AIP backup of my site using :-

[dspace]/bin/dspace packager -d -a -t AIP -e <my-email> -i 123456789/0 sitewide-dspace77-aip.zip

I put ALL the zip files created by the above command in the folder : /home/ashim/my-backup/BACKUP/

Now I am trying to restore :

Try 1:
dspace@ashim-VirtualBox:~/bin$ ./dspace packager -r -a -f -t AIP -e library@localhost -i 1/0 -o skipIfParentMissing=true /home/ashim/my-backup/BACKUP/sitewide-dspace77-aip.zip


WARNING -- You are running the packager in REPLACE mode.

REPLACE mode may be potentially dangerous as it will automatically remove and replace contents within DSpace.
We highly recommend backing up all your DSpace contents (files & database) before continuing.

Would you like to continue? [y/n]: y
Beginning replacement process...

Replacing DSpace object(s) with package located at /home/ashim/my-backup/BACKUP/sitewide-dspace77-aip.zip
Will replace existing DSpace SITE [ hdl=1/0 ]

REPLACED a total of 1 DSpace Objects.

Would you like to view a list of all objects that were replaced? [y/n]: y

REPLACED DSpace SITE [ hdl=1/0 ]

I do NOT see any restored items in my site.

Then I tried the following: -

Try 2 :
dspace@ashim-VirtualBox:~/bin$ ./dspace packager -r -a -f -t AIP -e library@localhost -i 1/0 -o skipIfParentMissing=true /home/ashim/my-backup/BACKUP/*zip


WARNING -- You are running the packager in REPLACE mode.

REPLACE mode may be potentially dangerous as it will automatically remove and replace contents within DSpace.
We highly recommend backing up all your DSpace contents (files & database) before continuing.

Would you like to continue? [y/n]: y
Beginning replacement process...

Replacing DSpace object(s) with package located at /home/ashim/my-backup/BACKUP/COLLE...@123456789-10.zip
Will replace existing DSpace SITE [ hdl=1/0 ]
org.dspace.content.packager.PackageValidationException: The object type of the METS manifest (COLLECTION) does not match up with the object type (SITE) of the DSpaceObject to be replaced!
    at org.dspace.content.packager.AbstractMETSIngester.replaceObject(AbstractMETSIngester.java:608)
    at org.dspace.content.packager.AbstractMETSIngester.replace(AbstractMETSIngester.java:1213)
    at org.dspace.content.packager.AbstractPackageIngester.replaceAll(AbstractPackageIngester.java:292)
    at org.dspace.app.packager.Packager.replace(Packager.java:737)
    at org.dspace.app.packager.Packager.main(Packager.java:377)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
    at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
org.dspace.content.packager.PackageValidationException: The object type of the METS manifest (COLLECTION) does not match up with the object type (SITE) of the DSpaceObject to be replaced!
dspace@ashim-VirtualBox:~/bin$

Can someone please help me? What is the correct way of restoring?

Thank you,

Ashim

[Ashim Kapoor]

Dear All,

I forgot to say I am migrating from Dspace 6.3 to DSpace 6.

Thank you,

Ashim

[Ashim Kapoor]

Dear All,

Can someone please help me with this ?

Thank you,

Ashim

[Terry Brady]

I see that you used   -i 123456789/0 on export and are using   -i 1/0  on import.

The error message "  The object type of the METS manifest (COLLECTION) does not match up with the object type (SITE) of the DSpaceObject to be replaced! "  may be caused by this discrepancy.

Do you want to preserve the site/community/collection handles in your destination repository?

Terry

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGdyo3JHFfye-UT2wKpz3fP22Xcr0HXxMRB3EZ7RhM2LA%40mail.gmail.com.

--

Terry Brady

Applications Programmer Analyst

Georgetown University Library Information Technology

https://github.com/terrywbrady/info

425-298-5498 (Seattle, WA)

[Ashim Kapoor]

On Wed, 25 Sep 2019 at 22:32, Terry Brady <Terry...@georgetown.edu> wrote:

I see that you used   -i 123456789/0 on export and are using   -i 1/0  on import.

The exported site has handle 123456789 while the handle of the site where the import is happening is 1. That is why I did this.

The error message "  The object type of the METS manifest (COLLECTION) does not match up with the object type (SITE) of the DSpaceObject to be replaced! "  may be caused by this discrepancy.

Do you want to preserve the site/community/collection handles in your destination repository?

 

Query : How can I ensure that I get the same ORIGINAL handle (ie.  1234567890 ) vs how can I get a new handle (ie 1 ) ? Is there a third way eg. where I can mention a different handle of the site (  different  to the original (123456789)/ new handle (1) )

[Terry Brady]

Try using the -p option when importing your top level communities.  That may allow you to override the expected parent for the community object.

Terry

[Tim Donohue]

If you are trying to change the Handles when importing content, then you should be using the *Submission* (-s) option and not the *Restore* (-r) option.  When using Restore, DSpace will *always* attempt to preserve the handles that are listed in the AIPs.  But, when using Submission (-s), DSpace ignores handles listed in the AIPs and assigns new ones.

If you want/need to run this command using the Restore (-r) option, there's a way to tell it to assign a new Handle to all objects by specifying "-o ignoreHandle=true" on the command line.

This difference in behavior (and various options to override defaults) is noted in the documentation here: https://wiki.duraspace.org/display/DSDOC6x/AIP+Backup+and+Restore#AIPBackupandRestore-Thedifferencebetween%22Submit%22and%22Restore/Replace%22modes

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Ashim Kapoor <ashim....@nipfp.org.in>
Sent: Thursday, September 26, 2019 12:26 AM
To: Terry Brady <Terry...@georgetown.edu>
Cc: DSpace Technical Support <dspac...@googlegroups.com>
Subject: Re: [dspace-tech] Re: Unable to restore site wide AIP backup

 

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAGEJAoHCXgCTCwTYV8cCHtyYewvpkLCv4bC1NuFXZPokpCnssA%40mail.gmail.com.

[Ashim Kapoor]

Dear Terry and Tim,

I read the link mentioned by Tim. I did a site wide restore as follows, however it does NOT restore the children of the site. What am I missing?

Thank you,

Ashim

dspace@ashim-VirtualBox:~/bin$ ./dspace packager -r -a -f  -t AIP -e library@localhost /home/ashim/backup/BACKUP/sitewide-dspace77-aip.zip  -i 1/0   -o skipIfParentMissing=true

WARNING -- You are running the packager in REPLACE mode.

REPLACE mode may be potentially dangerous as it will automatically remove and replace contents within DSpace.
We highly recommend backing up all your DSpace contents (files & database) before continuing.

Would you like to continue? [y/n]: y
Beginning replacement process...

Replacing DSpace object(s) with package located at /home/ashim/backup/BACKUP/sitewide-dspace77-aip.zip

Will replace existing DSpace SITE [ hdl=1/0 ]

REPLACED a total of 1 DSpace Objects.

Would you like to view a list of all objects that were replaced? [y/n]: y



REPLACED DSpace SITE [ hdl=1/0 ]

dspace@ashim-VirtualBox:~/bin$

[Tim Donohue]

Ashim,

It is not easy to tell you exactly what is going wrong without understanding your use case / needs here.  Are you trying to migrate content from one place to another and *keep the same Handles*?  If so, the process you listed should work, assuming you've properly exported all the AIPs (you should have a large number of Zip files which internally reference one another).

If you are instead trying to move content and assign *new Handles*, then you'd need to either use the Submission (-s) option or use the "-o ignoreHandle=true" flag with the Restore (-r) option.

Overall, we'd need to understand *all the steps you are taking* to provide better advice.  For example, if the export process did not result in a large number of Zip files (one per Community, Collection and Item), then your later import may not work properly as it cannot find all the expected objects to import.

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Ashim Kapoor <ashim....@nipfp.org.in>

Sent: Monday, September 30, 2019 6:50 AM
To: Tim Donohue <tim.d...@lyrasis.org>
Cc: Terry Brady <Terry...@georgetown.edu>; DSpace Technical Support <dspac...@googlegroups.com>

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAGEJAoEuJHr9%3D79OSZc%2B3b3vHWtL53avoi_9Q%2BOmMZPOPMz%3DLQ%40mail.gmail.com.

[Ashim Kapoor]

Dear Tim,

I am trying to migrate content from one place to another and *keep the same Handles*.

Here are the steps I took :-

[dspace]/bin/dspace packager -d -a -t AIP -e <my-email> -i 123456789/0 sitewide-dspace77-aip.zip

The above gave me a number of zip files, 1 for each Community, Collection, Item, all of which are kept in ONE folder.

Then I did :-

dspace@ashim-VirtualBox:~/bin$ ./dspace packager -r -a -f  -t AIP -e library@localhost /home/ashim/backup/BACKUP/sitewide-dspace77-aip.zip  -i 1/0   -o skipIfParentMissing=true

Please note the NEW DSpace instance has a handle prefix of 1, the old DSpace instance has a hande prefix of 123456789.

Look forward to hearing from you.

Thank you,

Ashim

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/DM5PR22MB05728DC8BA11A45EBDA902ACED820%40DM5PR22MB0572.namprd22.prod.outlook.com.

[Tim Donohue]

Hi Ashim,

Since the Handle prefix is changing (from 123456789 to 1) this means you must assign new handles (as the Handle 123456789/0 is considered different from Handle 1/0).

So, as mentioned, you will need to use either use the Submission (-s) option or use the "-o ignoreHandle=true" flag with the Restore (-r) option.

Tim

---

From: Ashim Kapoor <ashim....@nipfp.org.in>
Sent: Monday, September 30, 2019 11:13 PM