Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If we decide to do this in-house, the process is as followsEddie upgraded our ArchivesSpace in November 2021, following the steps below:

  1. Create a new production 3.0.1 server using Ansible

  2. Stop the old production archivesspace daemon

  3. Move the following files and directories over from the existing production server. Do not copy the database connector .jarfile; use the one that comes with 3.0.1

    1. config

    2. plugins

      1. except for lcnaf – use the latest version that comes with 3.0.1

    3. data

      1. except for data/indexer_state, data/indexer_pui_state, and data/solr_index

  4. Copy the database over. Use a fresh backup from production:

    1. Code Block
      mysql archivesspace  --password='PASSWORD_REDACTED'  --user=aspace
      \. /home/ubuntu/aspace-backup.sql
  5. Update the database to 3.0.1: scripts/setup-database.sh

  6. Start archivesspace: /opt/archivesspace/archivesspace.sh start

  7. Copy over the Apache and EAD and HTML export scripts at/home/ubuntu/archivesspace_scripts and /etc/apache2

  8. Run the DB backup and export scripts and check for errors.

  9. Restart Apache

  10. Add ubuntu to the www-users group

  11. Set up crontab so the exports run regularly

  12. Stop the old production server

  13. Point the elastic IP at the new server

...