Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

If we decide to do this in-house, the process is as follows:

  1. Create a new production 3.0.1 server using Ansible

  2. Stop the old production server

  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

    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. 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. Point the elastic IP at the new server

  13. Stop (and later terminate) the old production instance

  • No labels