When migrating servers (Production or Staging) follow these steps. In order to reduce transit costs, it is recommended to not use S3 backups or the public IP addresses, but instead the internal ones (usually 172.xxx...) using those to send data back and forth avoids any fees for out of AWS/region transfer.
Some of this should be scriptable with variables, look into setting up a playbook.
- Either get the current day's PGSQL backup or run ~/bin/postgres-backup.sh if it's before the backup has run.
- Make a COPY of the minter file (cp -a to preserve attributes) to work with. Copy it to /home/ubuntu or some other easily recalled location.
- If using SSL, get a copy of the needed files (server cert, CA cert, and key). Recommended option to make them a nice tar file for transfer.
- Move the postgres backup, minter, and SSL certs to the new server.
- Make /var/sufia, and move Minter there.
- Change Minter's owner to hydep:deploy
- Move the SSL certs to /etc/ssl and the key to /etc/ssl/private
- Shut down tomcat7 and restart postgres (this kicks Tomcat off of using chf_hydra so we can rebuild it)
- Follow the Postgres commands in the Postgres section to drop the DB, rebuilt it with the backup, and set the permissions.
- Restart Tomcat7
- Run the ansible SSL script.
- Test the new machine to make sure SSL is working and user accounts came over by logging in.
- Shut down the old server. Detach the Fedora volumes.
- Attach the Fedora volumes to the new machine
- Run the raid-configure ansible playbook.
- Reindex Solr
- Check new machine to see data is indexed.