Thanks, Andrea, Copying over the assetstore, with care to preserve the newer items, worked well.
Now on to the next problem. On Mon, Nov 9, 2015 at 7:50 PM, Andrea Schweer <[email protected]> wrote: > Hi Chris, > > On 10/11/15 11:50, Chris Gray wrote: > >> We recently migrated servers from 3.1 to 5.3. >> >> At first we migrated content via AIP export and import but found that our >> database was askew, disallowing creation of new communities. >> >> So we moved the database directly via pg_dump and pg_restore, and >> everything seemed fine. >> >> Now we're finding that many of the pdf bitstreams give a file not found >> error saying the file is not in the asseststore. >> >> My suspicion is that the AIP import didn't duplicate the old asseststore >> but assigned new directories and filenames and the databases references are >> to the old structure. >> > > Yes, I'd expect the AIP import to create a different asset store structure. > > Can we fix this by a straight copy of the assetstore from the old server >> to the new server? >> > > Yes, that should work. Just be careful not to lose any bitstreams you may > have added to the new server since the restore. > > cheers, > Andrea > > -- > Dr Andrea Schweer > IRR Technical Specialist, ITS Information Systems > The University of Waikato, Hamilton, New Zealand > +64-7-837 9120 > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
