Hi Elayne, Since you are pressed for time, I would suggest sticking with v4.4 for now on the new host server and then upgrading to v4.5 at a later date. There are different ways to go about this and it varies depending on how you've implemented your system. However, my brief suggestions should work in most cases. I would create a remote git project repository (Github, Bitbucket, Gitlab, etc.) for all three layers of CollectionSpace (ui, application, and services) and store your source code there so that you may recreate it on the new host server. I would then shut down your CollectionSpace instance and preform an all database dump. Then, I would copy and compress the data directory that contains your blobs, which is located at apache-tomcat-7.0.57/nuxeo-server/data. Both the database dump file and the compressed data directory can then be copied to your new host server for the restore. Be sure to also make a copy of the environmental variables found in your .bashrc or similar so that they can be recreated on the new host server. On the new host server follow the CollectionSpace manual installation instructions for your host server. This time, instead of cloning the source code from the CollectionSpace remote code repository, clone your source code, that you pushed to a remote repository in the last step, locally. Add your env variables to the .bashrc of the cspace user on the new host server. Restore the database on your new host server with the database dump. Decompress and add the copy of the data directory to its location on the new host server. Finish the install. Do not recreate the database when you run the ant undeploy deploy task after you restored the database because you will lose your data. Simply run 'ant undeploy deploy', excluding '...create_db -Drecreate_db=true import'. That should be the bulk of it. You may want to deploy CollectionSpace and make sure its running properly on the new host server before doing all of this. If you have anymore questions, let us know. Good luck. -Yousuf On Thu, Nov 16, 2017 at 10:29 AM, Elayne Glantzberg < solinox@solinoxenterprises.com> wrote: > I sent out a message last weekend but got no response. I've been working > on this all week, and some assistance or guidance would be very helpful. I > need to move our tenanted system from one server to a new server, ASAP > because the host of the old server is shutting down. The original system > was running postgresql-9.3, tomcat 7.0.57, cspace 4.4. The new system is > going to be running postgresql-9.5, tomcat 7.0.64, and cspace 4.5. What I'm > trying to do right now is upgrade the old system on all three fronts, do a > full basic install on the new system, and then rsync the postgres and > cspace folders from the old system to the new system. I managed to > successfully upgrade the postgres system to 9.5, and verified by > relaunching everything and successfully logging in and viewing data. At > the moment, I'm not sure what all I should be doing to move the old system > from 4.4 to 4.5, there is zero guidance available in the wiki even though > it has been updated so that all the paths now point to 4.5. > > Am I on the right track at least? Any help would be greatly appreciated. > > Thank you, > Elayne Glantzberg > Database Administrator > Aquarian Tabernacle Church > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > > -- *Yousuf D. Nejati*

Hi Elayne, I second everything Yousuf said. I usually do this in three steps: 1. Install a fresh copy of CSpace on the new server. Make sure it's accessible by a browser, and you can save records. 2. Install your customizations, if any. This means transferring over any customizations you have in the services, application, and ui source code directories. We store our customizations in GitHub, so I do a git clone on the new server to install them. After building and deploying, you should see your customizations on the new server. If you didn't customize CollectionSpace, skip this. 3. Transfer your data. I usually rsync the nuxeo-server/data directory to transfer binaries, and then use pg_dump to dump the postgres databases, and restore them on the new server with pg_restore. Ray On Thu, Nov 16, 2017 at 12:42 PM, Yousuf Nejati <yousufnejati@gmail.com> wrote: > Hi Elayne, > > Since you are pressed for time, I would suggest sticking with v4.4 for now > on the new host server and then upgrading to v4.5 at a later date. There > are different ways to go about this and it varies depending on how you've > implemented your system. However, my brief suggestions should work in most > cases. > > I would create a remote git project repository (Github, Bitbucket, Gitlab, > etc.) for all three layers of CollectionSpace (ui, application, and > services) and store your source code there so that you may recreate it on > the new host server. I would then shut down your CollectionSpace instance > and preform an all database dump. Then, I would copy and compress the data > directory that contains your blobs, which is located > at apache-tomcat-7.0.57/nuxeo-server/data. Both the database dump file > and the compressed data directory can then be copied to your new host > server for the restore. Be sure to also make a copy of the environmental > variables found in your .bashrc or similar so that they can be recreated on > the new host server. > > On the new host server follow the CollectionSpace manual installation > instructions for your host server. This time, instead of cloning the > source code from the CollectionSpace remote code repository, clone your > source code, that you pushed to a remote repository in the last step, > locally. Add your env variables to the .bashrc of the cspace user on the > new host server. Restore the database on your new host server with the > database dump. Decompress and add the copy of the data directory to its > location on the new host server. Finish the install. Do not recreate the > database when you run the ant undeploy deploy task after you restored the > database because you will lose your data. Simply run 'ant undeploy > deploy', excluding '...create_db -Drecreate_db=true import'. That should > be the bulk of it. You may want to deploy CollectionSpace and make sure > its running properly on the new host server before doing all of this. > > If you have anymore questions, let us know. Good luck. > > -Yousuf > > > > > > > On Thu, Nov 16, 2017 at 10:29 AM, Elayne Glantzberg < > solinox@solinoxenterprises.com> wrote: > >> I sent out a message last weekend but got no response. I've been working >> on this all week, and some assistance or guidance would be very helpful. I >> need to move our tenanted system from one server to a new server, ASAP >> because the host of the old server is shutting down. The original system >> was running postgresql-9.3, tomcat 7.0.57, cspace 4.4. The new system is >> going to be running postgresql-9.5, tomcat 7.0.64, and cspace 4.5. What I'm >> trying to do right now is upgrade the old system on all three fronts, do a >> full basic install on the new system, and then rsync the postgres and >> cspace folders from the old system to the new system. I managed to >> successfully upgrade the postgres system to 9.5, and verified by >> relaunching everything and successfully logging in and viewing data. At >> the moment, I'm not sure what all I should be doing to move the old system >> from 4.4 to 4.5, there is zero guidance available in the wiki even though >> it has been updated so that all the paths now point to 4.5. >> >> Am I on the right track at least? Any help would be greatly appreciated. >> >> Thank you, >> Elayne Glantzberg >> Database Administrator >> Aquarian Tabernacle Church >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists >> .collectionspace.org >> >> > > > -- > > *Yousuf D. Nejati* > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > >