How can i rearrange dspace community and collection i try to export the collection but it's too large What I need is to display some collection in the dspace home page.
On Tue, Nov 3, 2020 at 11:08 AM Thomas <[email protected]> wrote: > 10 Q It's great help and it's working fine for me. > > On Mon, Nov 2, 2020 at 8:10 PM Mark H. Wood <[email protected]> wrote: > >> On Mon, Nov 02, 2020 at 12:46:03AM -0800, dspace info wrote: >> > i have dspace 6.3 installed in ubuntu 18.04 pc and i have 50.60GB of >> file >> > know i need to install new dspace 6.3 in other pc ubuntu 20.04 >> > how can i take a backup from the old pc and restore to my new server >> > i try to find resources but i cant find please help me >> >> DSpace stores information in three places: >> >> o The actual documents submitted to DSpace are stored in the >> "assetstore": a tree of directories containing files with long >> opaque names. You need to copy this as-is to the assetstore >> directory in the new DSpace instance. 'tar' or 'cpio' or 'zip' >> should work for this. >> >> o The metadata and relationships are stored in the database. If you >> need to move the database to a new host, you'll need to use DBMS >> tools to dump it on the old system and restore it to the new one. >> You'll also need to copy or re-create the DBMS user account that >> DSpace uses. >> >> If your DBMS is PostgreSQL, I would use 'pg_dump' and the plain >> script format to dump the DSpace database, feed it to 'psql' to >> restore it, and manually re-create the DBMS user account (typically >> named 'dspace', but check your configuration to be sure). >> >> o Usage statistics are stored in Solr, in the 'statistics' core. You >> can shut down Solr and copy this directory tree to the new host >> (with Solr shut down there as well). Again, 'tar' 'cpio' or 'zip' >> should serve. >> >> The other three Solr cores are caches which can be re-built from >> the primary data in the assetstore and database. But you could >> just copy these cores as well. >> >> It might be simplest to just back up the whole [DSpace] directory tree >> and restore it to the new host, then move the database, and adjust host >> names in the new configuration as needed. >> >> There are other ways that don't require making so many huge backup >> files. If you're somewhat familiar with NFS, you could shut down >> DSpace and Solr on the old host, export the [DSpace] tree from the old >> host via NFS, mount it in a temporary location on the new host, and >> 'cp' everything into place. You still need to copy the database >> separately. >> >> Yet another approach would be to export the whole repository as AIP >> files, but I haven't done it that way so I can't give best advice on >> this. See >> https://wiki.lyrasis.org/display/DSDOC6x/AIP+Backup+and+Restore >> >> -- >> Mark H. Wood >> Lead Technology Analyst >> >> University Library >> Indiana University - Purdue University Indianapolis >> 755 W. Michigan Street >> Indianapolis, IN 46202 >> 317-274-0749 >> www.ulib.iupui.edu >> >> -- >> 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 Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-community/20201102170815.GA17275%40IUPUI.Edu >> . >> > -- 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/CAPmrPjxhP3UOgTiiz-FSJDPJrN2HNyA7ff7uZNXR%2BFJrKDa52A%40mail.gmail.com.
