...
The local backup server (Dubnium) can be found at 65.170.7.86
The scripts for backup are not in ansible, so they are copied here for S3 backup and here for scihist-digicoll backup for emergency needs.
Right now the account holders are Daniel, Jonathan, and Eddie, each of whom uses a password to access the server.
- The original files and postgres database exist on-site on the shared drive, and also offline in tape backups made from that shared drive. Ideally we do not need the tape backups. If they are needed work with IT (Chuck and Ponce) to follow their procedures for recovering and loading the tapes.
- An aws s3 sync will need to be run targeting the local backup directory
aws s3 sync /media/scihist_digicoll_backups/asset s3://scihist-digicoll-production-originals/asset --region us-east-1- This may take multiple days to run
- While that runs, copy the postgres database from it's location at /media/scihist_digicoll_backups to the database server.
- Follow step 5e in the Full Recovery from S3 section to load the database.
- Follow step 5f to reindex Solr
- Once all of the original files are moved you can regenerate the derivatives with the rake task. Derivative files are not backed up locally so syncing is not an option.
Crontab notes
The crontab looks like
AWS_CONFIG_FILE="/home/dsanford/.aws/config"
# m h dom mon dow command
30 18 * * * /home/dsanford/bin/s3-backup.sh
00 18 * * * /home/dsanford/bin/scihist-digicoll-backup.sh
The AWS_CONFIG.... section needs any rotated keys, and is vital for passing along the config info and permissions to the scripts. If it is missing, they will not work.