Page Comparison

...

1. Stop Tomcat
2. Download the Postgres database fcrepo_backup.sql to an arbitrary location on the Fedora machine.

3. Fedora might still have active connections to postgres, so run a postgres restart to kill them: sudo service postgresql restart .

4. Import the database: psql fcrepo < fcrepo_backup.sql

   1. If the database already exists, such as when you are running a sync, you will want to drop the existing database and then run the command.
5. Check that the user trilby has permissions to access and use the newly made fcrepo database.
6. Delete the existing folder(s) inside /opt/fedora-data (This step is not always required but makes it simpler)

7. Using screen or tmux start an aws s3 sync to copy all the data over in the FedoraBackup "folder" to /opt/fedora-data : aws s3 sync s3://chf-hydra-backup/FedoraBackup /opt/fedora-data/

8. Wait a while for all the data (>800 GB) to copy over.
9. Run chown -R tomcat8:tomcat8 /opt/fedora-data to give ownership on the new files to the tomcat user so Fedora can access them.

10. Restart Tomcat: sudo service tomcat8 restart OR sudo systemctl tomcat8 restart

11. This will restore the Fedora database.  Current cost estimates (2/18) are about $.10 to do this restore.

...

1. Go to S3 and download the postgres backup files to an arbitrary location on the app server.
2. Stop Apache
3. Restart the postgres service , this (see above). This should remove the default connection to the Hydra Sufia database that Hydra that Sufia has when it's running, so you can change it.
4. In Postgres, delete the automatically generated chf_hydra database as follows:
   1. Log in via psql -u postgres
      1. The postgres account password is in ansible-vault (groupvars/all)
   2. Run: DROP DATABASE chf_hydra;
   3. Run: CREATE DATABASE chf_hydra;
5. Then import the downloaded database
   1. Either:
      1. pg_restore -d chf_hydra -U postgres chf_hydra.dump
      2. psql chf_hydra < chf_hydra_dump.sql
6. Then set permissions
   
   1. psql -U postgres
   2. GRANT Create,Connect,Temporary ON DATABASE chf_hydra TO chf_pg_hydra;

7. You may now restart postgres and Apache2

Minter:

...

1. . systemctl restart apache2

Note: the minter is now part of postgres, : no need to take any extra steps. just restore the chf_hydra database for the users to app and the minter will be restored.Redis

How to restore redis:

Redis keeps a database in memory which handles the transaction record data such as the history of edits on a record. It does not contain the actual data, simply the timeline of changes. Losing this causes the history of object edits to be lost, but the objects themselves will be fine.

1. Copy over Download redis-dump/dump.rdb to Appan arbitrary location on the app server.
2. It must be changed to be owned by the redis user as follows:
   1. sudo chmod -R redis:redis filename
3. Then you will need to stop Stop the redis server as follows:
   1. sudo service redis-server stop
4. Move redis-dump.rdb to /var/lib/redis/dump.rdb overwriting . This will overwrite the existing file there called dump.rdb
5. Restart redis
   1. sudo service redis-server start
6. When starting up , redis will read the .rdb dump file and copy that data back to into the in-memory database.

Indexing:

The index is being backed up to speed up the time to recovery for DR or migrations. If you cannot access it, a manual reindex can be done with the instructions in Application administration. This process takes at least one business day, so is not recommended versus rebuilding from the backup.

1. In the chf-hydra-backup, pull down the solr-backup.tar.gz file under Solr to the Solr server.
2. Extract the archive
3. Use the solr restore commands at Application administration
    

...

Costs

A quick cost analysis has restoration costing $30-35 dollars, this is as of 6/11/2018 with approximately 1 TB of data. Approximately 66% of the cost was due to inter-region transfer fees (moving data from US-WEST to US-EAST). The rest is standard LIST, GET, and related fees.

...