Just a quick FYI to others... I've copied my instructions for a 
multi-version upgrade (sent to Michael) to our official DSpace Wiki 
documentation, as I suspect they may be generally useful:

https://wiki.duraspace.org/display/DSDOC4x/Multi-Version+Upgrade+Tips+and+Tricks

- Tim

On 5/21/2014 8:16 AM, Michael O Holt wrote:
> This did the trick and was far easier than then AIP process. Thanks a ton for 
> your help!
>
> -Michael
>
> -----Original Message-----
> From: Tim Donohue [mailto:[email protected]]
> Sent: Tuesday, May 20, 2014 5:08 PM
> To: Michael O Holt; [email protected]
> Subject: Re: [Dspace-tech] Problems with AIP restore
>
> Hi Michael,
>
> The commands look correct overall. Just wanted to double check that you were 
> running the correct commands. Unfortunately, I'm not entirely sure why the 
> restoration command is failing (and I haven't had time today to do any deeper 
> digging)
>
> There's a few options here for next steps:
>
> 1) If you actually wanted to do an upgrade, it still is possible, even if you 
> are also migrating servers at the same time. (See below)
>
> 2) If you truly want to do AIP migration, then we might need to dig into your 
> AIPs more to understand what is going on. I'm not exactly sure what the issue 
> is offhand.
>
> However, since you stated that your purpose is to just upgrade to DSpace
> 4 while changing servers, that seems *easier* to do by following the normal 
> upgrade process... Here's essentially what you'd do (please test this process 
> first *BEFORE* doing anything in Production):
>
> 1) Make a backup copy of your OLD, DSpace 1.8 PostgreSQL Database, for
> example:
>
>      pg_dump -U [database-user] -f my-dspace-db-backup.sql [database-name]
>
> (Creates a file named "my-dspace-db-backup.sql" which has the full contents 
> of your database)
>
> 2) Create an exact replica of the DSpace 1.8 Database in a new database 
> called "dspace-upgrade". Pass it the backup.sql file to recreate the entire 
> database.
>
>      createdb -U [database-user] -E UNICODE dspace-upgrade
>      psql -U [database-user] -f my-dspace-db-backup.sql dspace-upgrade
>
>     You now should have an exact replica, DSpace 1.8 database in 
> "dspace-upgrade"
>
> 3) Upgrade that replica, DSpace 1.8 database to be compatible with DSpace 
> 4.x. You'll have to first upgrade the database to 3.x compatibility, then to 
> 4.x
>
>      # Upgrade to 3.x compatibility by running 'database_schema_18-3.sql'
>      psql -U [database-user] -f
> [dspace-source]/dspace/etc/postgres/database_schema_18-3.sql dspace-upgrade
>
>      # Then upgrade to 4.x compatiblity by running 'database_schema_3-4.sql'
>      psql -U [database-user] -f
> [dspace-source]/dspace/etc/postgres/database_schema_3-4.sql dspace-upgrade
>
> 4) Now, you have a DSpace 4.x compatible database. You can move that over to 
> your other server which is running DSpace 4.
>
>      # Dump the DSpace 4.x compatible database data (from dspace-upgrade)
>      pg_dump -U [database-user] -f my-dspace-4.x-db.sql dspace-upgrade
>
>      # Copy that "my-dspace-4.x-db.sql" to your NEW server (via scp or sftp 
> or similar)
>
>      # Delete the default (should be empty) 4.x Database on the NEW server.
>      dropdb -U [database-user] [database-name]
>
>      # Recreate an empty DB and load the 4.x compatible data
>      createdb -U [database-user] -E UNICODE [database-name]
>      psql -U [database-user] -f my-dspace-4.x-db.sql [database-name]
>
> 5) FINALLY, Just copy your "assetstore" folder from your OLD server to the 
> NEW server and do a full re-index of everything.
>
> At this point, you should have all your old data moved over into an
> *uncustomized* version of DSpace 4 on a new server.
>
> As the final step, you'd just reconfigure things how you like them, or 
> recustomize the UI, etc.
>
> - Tim
>
>
> On 5/20/2014 11:29 AM, Michael O Holt wrote:
>> Hi Tim,
>>
>> Here are the commands I'm running:
>>
>> To export AIPs: ./dspace packager -d -a -t AIP -e
>> [email protected] -i 10428/0 sitewide-aip.zip
>>
>> To import AIPs: ./dspace packager -r -a -f -t AIP -e
>> [email protected] -i 10428/0 /home/<user>/sitewide-aip.zip
>>
>> The user that owns the /home/user/ folder owns the dspace folder as well, so 
>> it shouldn't be a permissions issue.
>>
>> I made sure to export all the aip files the export created. I wen back and 
>> checked to make sure that the collection number throwing the error had an 
>> AIP present and it did.
>>
>> I would love to just update to 4.1 as that would be far easier, but I'm 
>> afraid I let the version of Ubuntu Server our Dspace runs on reach EOL. Now 
>> I can't install the important security updates the OS needs, so I have to 
>> migrate everything to a new server I'm afraid.
>>
>> -Michael
>>
>> ________________________________________
>> From: Tim Donohue <[email protected]>
>> Sent: Tuesday, May 20, 2014 12:21 PM
>> To: Michael O Holt; [email protected]
>> Subject: Re: [Dspace-tech] Problems with AIP restore
>>
>> Hi Michael,
>>
>> A few questions in order to clarify how you are encountering this
>> error message.
>>
>> * Could you send us the exact command(s) you are running, both to
>> export the AIPs from DSpace 1.8 and then to reimport them into DSpace
>> 4.x? It might help us better understand why this error is occurring.
>>
>> * Did you only export the SiteWide AIP? Or did you make sure to export
>> all the AIPs? Just to clarify: There should be one AIP for every
>> single Community, Collection and Item in your 1.8 DSpace. In order to
>> restore all your content, you'd need to migrate all of your AIPs from
>> your old
>> 1.8 server to your 4.1 server.
>>
>> As a sidenote: If you are simply trying to upgrade from 1.8 to 4.x,
>> you do not have to use the AIP backup & restore to do so. It's also
>> perfectly reasonable to just follow the default upgrade process for
>> DSpace. (Essentially you'd just upgrade your old database from 1.8 to
>> 3.x and then from 3.x to 4.x, and then move over the /assetstore
>> folder from one server to the other.)
>>
>> https://wiki.duraspace.org/display/DSDOC4x/Upgrading+DSpace
>>
>> - Tim
>>
>> On 5/20/2014 9:41 AM, Michael O Holt wrote:
>>> Hi,
>>>
>>> I'm trying to migrate content from a 1.8 server to a new server
>>> running
>>> 4.1 (the server is running RHEL 6). I've created a sitewide AIP of
>>> the
>>> 1.8 site and I'm trying to import it to the new fresh install of 4.1.
>>> Yet, when I run the packager script on the new server, it always
>>> gives an error. Nothing shows up on the site afterwards either, so I
>>> know the import must not have completed. However, the /assetstore
>>> directory does seem to be populated. Yet, no communities,
>>> collections, or items are showing up on the site. I've tried running
>>> index-discovery and stat-initial with no effect. The error I get in the 
>>> shell is as follows:
>>>
>>> org.dspace.content.crosswalk.CrosswalkInternalException:
>>> org.dspace.content.packager.PackageException: Unable to translate
>>> Handle to Internal ID in group named
>>> 'COLLECTION_hdl:10428/1077_ADMIN' as DSpace Object 
>>> (Handle='hdl:10428/1077') does not exist.
>>>
>>>            at
>>> org.dspace.content.crosswalk.RoleCrosswalk.ingest(RoleCrosswalk.java:
>>> 341)
>>>
>>>            at
>>> org.dspace.content.crosswalk.RoleCrosswalk.ingest(RoleCrosswalk.java:
>>> 259)
>>>
>>>            at
>>> org.dspace.content.packager.METSManifest.crosswalkXmd(METSManifest.ja
>>> va:1193)
>>>
>>>            at
>>> org.dspace.content.packager.METSManifest.crosswalkObjectOtherAdminMD(
>>> METSManifest.java:1106)
>>>
>>>            at
>>> org.dspace.content.packager.AbstractMETSIngester.ingestObject(Abstrac
>>> tMETSIngester.java:459)
>>>
>>>            at
>>> org.dspace.content.packager.AbstractMETSIngester.replace(AbstractMETS
>>> Ingester.java:1170)
>>>
>>>            at
>>> org.dspace.content.packager.AbstractPackageIngester.replaceAll(Abstra
>>> ctPackageIngester.java:241)
>>>
>>>            at
>>> org.dspace.content.packager.AbstractPackageIngester.replaceAll(Abstra
>>> ctPackageIngester.java:271)
>>>
>>>            at
>>> org.dspace.content.packager.AbstractPackageIngester.replaceAll(Abstra
>>> ctPackageIngester.java:271)
>>>
>>>            at
>>> org.dspace.content.packager.AbstractPackageIngester.replaceAll(Abstra
>>> ctPackageIngester.java:271)
>>>
>>>            at
>>> org.dspace.app.packager.Packager.replace(Packager.java:727)
>>>
>>>            at org.dspace.app.packager.Packager.main(Packager.java:373)
>>>
>>>            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>>
>>>            at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> java:57)
>>>
>>>            at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> sorImpl.java:43)
>>>
>>>            at java.lang.reflect.Method.invoke(Method.java:606)
>>>
>>>            at
>>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.j
>>> ava:225)
>>>
>>>            at
>>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)
>>>
>>> Caused by: org.dspace.content.packager.PackageException: Unable to
>>> translate Handle to Internal ID in group named
>>> 'COLLECTION_hdl:10428/1077_ADMIN' as DSpace Object
>>> (Handle='hdl:10428/1077') does not exist.
>>>
>>>            at
>>> org.dspace.content.packager.PackageUtils.translateGroupNameForImport(
>>> PackageUtils.java:932)
>>>
>>>            at
>>> org.dspace.content.packager.RoleIngester.ingestDocument(RoleIngester.
>>> java:383)
>>>
>>>            at
>>> org.dspace.content.packager.RoleIngester.ingest(RoleIngester.java:471
>>> )
>>>
>>>            at
>>> org.dspace.content.crosswalk.RoleCrosswalk.ingest(RoleCrosswalk.java:
>>> 337)
>>>
>>>            ... 17 more
>>>
>>> org.dspace.content.crosswalk.CrosswalkInternalException:
>>> org.dspace.content.packager.PackageException: Unable to translate
>>> Handle to Internal ID in group named
>>> 'COLLECTION_hdl:10428/1077_ADMIN' as DSpace Object 
>>> (Handle='hdl:10428/1077') does not exist.
>>>
>>> Any help with this would be greatly appreciated.  I'm at a loss for
>>> what to do next.
>>>
>>> Michael Holt
>>>
>>> Assistant Professor and Reference Librarian/Marketing Coordinator
>>>
>>> Valdosta State University Odum Library
>>>
>>> 1500 North Patterson Street, Valdosta, GA 31698
>>>
>>> 229.333.7105
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> --------- "Accelerate Dev Cycles with Automated Cross-Browser Testing
>>> - For FREE Instantly run your Selenium tests across 300+ browser/OS
>>> combos.
>>> Get unparalleled scalability from the best Selenium testing platform
>>> available Simple to use. Nothing to install. Get started now for free."
>>> http://p.sf.net/sfu/SauceLabs
>>>
>>>
>>>
>>> _______________________________________________
>>> DSpace-tech mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>> List Etiquette:
>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>
>>

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to