[Archivesspace_Users_Group] Looking for advice: moving from 2.7.1 to 3.3.1 on a new server

Tom Hanstra hanstra at nd.edu
Fri Apr 21 13:58:00 EDT 2023


I've done this a couple of times now and here is my process:

- Create the server with RHEL8 and get it working as you want (any internal
- Add in the ArchivesSpace software and Solr
- Get Solr running with your local configuration changes (if any)
- Get ArchivesSpace running with your local changes and configuration
- Add in any plugins at the same time (including SSO)

At that point, I would suggest that you *test* moving over the database.
Copy the database over to your new server, run it through the upgrade
process, and then make sure indexing works. Test that everything is working
as you want it. As long as the names are different between the new and old,
you can test as much as you want.

Once you know everything is working as desired/expected, *then* do the
production copy/index processing and cut over DNS.

The testing could take a while. There are quite a few changes between 2.7.1
and 3.3.1, not the least of which is getting Solr running separately.

Hope that helps,

On Fri, Apr 21, 2023 at 1:02 PM Gadsby, Eric T. <egadsby at towson.edu> wrote:

> Dear Friends,
> Our install is at 2.7.1 on RHEL 7. The pandemic contributed to a pause in
> updates.  Now that we are back to “normal” we need to move to the latest
> version on a REHL 8.6 server.   I am trying to work out the order in which
> do things to get the new server up and the data moved.  I know we’ll need
> to set up the application and Solr on the new server.  What I am trying to
> puzzle out is the best way to move the data. We can do a database export
> from the old server and then import it into the new server. The question I
> have is this, how do we go about the database updates. Do we need to update
> the old server and run the script and then export the data or can we move
> the data as is and then run the updater script in the new environment? Any
> insight would be invaluable.
>  I know we will also need to reestablish our SSO, reimplement plug-ins,
> and then eventually cut over our DNS. Is there something I’m not thinking
> about?  Thank you in advance for any help the community can offer. Thanks!
> [image: Towson University logo] <http://www.towson.edu/>
> *Eric T. Gadsby*
> *Pronouns: he/him/his*
> IT Operations Specialist  |  Albert S. Cook Library
> *—*
> P: 410-704-3340
> egadsby at towson.edu  |  libraries.towson.edu
> <http://www.towson.edu/https:/libraries.towson.edu>
>  *—*
> Confidentiality Notice: This message may contain information that is
> confidential, privileged, proprietary, or otherwise legally exempt from
> disclosure. If you are not the intended recipient, you are notified that
> you are not authorized to read, print, copy or disseminate this message,
> any part of it, or any attachments. If this message has been sent to you in
> error, please notify the sender by replying to this transmission, or by
> calling Albert S. Cook Library at 410-704-3340 .
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

*Tom Hanstra*
*Sr. Systems Administrator*
hanstra at nd.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230421/c57ac9c7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1826 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230421/c57ac9c7/attachment.jpg>

More information about the Archivesspace_Users_Group mailing list