Set up automated backups for brainard-archiva server

[benjamin-heasly]

Our brainard-archiva server is hosted at AWS. It uses an EBS volume to store artifact data.

We should set up automated nightly backups of the EBS volume. These should be stored as EBS "snapshots" stored on S3.

Making EBS snapshots is really easy from the AWS management console. Automating the snapshots will take a bit more system admin work. Here is one possible approach.

[benjamin-heasly]

I followed this README from CaseyLabs. I modified the script provided to retain snapshots for 31 days instead of 7 days.

I also used this handy review of crontab.

I created a new AMI called brainard-archiva plus backups to reflect the state of the server with AWS command line configuration and crontab configured.

[benjamin-heasly]

The backup script works when invoked manually. For example:

# ssh to brainard-archiva
sudo /opt/aws/ebs-snapshot.sh

produced two a new snapshot of the brainard-archiva EBS volume, visible in the EC2 management console.

Will leave this issue open until I can confirm that the cron job works. This should be apparent at 22:55 GMT, which is when the backup is scheduled.

[benjamin-heasly]

Job did not fire last night. Looking at cron configuration, I think I scheduled the job as the wrong user, probably causing a permissions issue for AWS.

Re-scheduled the job as root, which has the AWS credentials.

[benjamin-heasly]

Cron job was screwed up with an extra parameter root between the cron expression and the command string. Removed the word root and now the job fires and produces snapshots.

Will leave this issue open until 22:55 GMT to verify that the job id firing on the correct schedule.

[benjamin-heasly]

Jobs are firing on the correct schedule.