Mu Master Backup

You'll want to back up your Mu Master periodically as it provides valuable management capabilities for your deployments. Currently problems with Chef's backup process prevent a fully automated process, so here's a stopgap that will tide us over until we resolve the issues.

Concept

1. Always launch your mu master with an elastic IP.
2. Periodically image your master, which creates your backup
3. Restore by restoring the imaged master, and attaching the former master's elastic IP

Backup

1. You'll want to launch your mu master with an EIP, or attach one before configuring it. In theory you could simply run mu-configure on a restored image with a different IP, but in practice Chef has significant problems with adjusting to a change in its server's IP
2. Image your master as an AMI, allowing reboot (it won't affect your instances) and clearly labeling the imaged AMI as a backup of your master

Restore

1. Create a new instance from the desired backup AMI in the same VPC as your former Mu Master
2. Attach the former master's EIP to the new master
3. Be sure to reupload cookbooks using mu-upload-chef-artifacts -- run as default for Mu's cookbooks and with -r for any repositories of your own
4. Run mu-node-manage and verify connectivity to your existing deploys
5. Run and destroy a sample deploy to verify full operation