AWS Tip of the Month: Backup Server for less than $1 a month

AWS has a very neat way to backup your server with attached storage called EBS Snapshots.  This technology starts with a full snapshot of the entire volume and continues to do incremental snapshots based on the difference between the last snapshots.

Snap shotting is not a new technology, and many people use this in their on-premise environment to take snapshots of a virtual machine or specific disk for backup or copy purposes.

At AWS you cannot schedule these snapshots. You either have to call these via API or use the management console to do this.

Below is the high-level process to automate these snapshot backups at a particular time each day:

1. Build a t1.micro that has a script to run that calls the snapshot API for EBS for the volumes you want to backup.  Make sure this script runs on machine start up.
2. Setup an Auto-scale group to launch a server based on a schedule (we start ours at 3am and shut it off at 3:50 am).  This ensures time to kick off all the snapshot jobs - note: I do not have to run the server while they complete, only to kick off the snapshot and any pre-activities I need to accomplish before I can take my backup.
3. Check your snapshots to ensure they are occurring regularly and test them on a monthly or quarterly basis to ensure you can recover sufficiently in the case of an outage.

By doing this daily we have incurred the costs of our storage for snapshots and the $.02 an hour charge for our T1.micro - effectively $0.62 per month for a backup server.

-Kris

AWS Tip of the Month - Super fast Micro instance installs for less than a buck

Here is an easy but effective tip for managing micro instances in AWS.

Micro instances can be a challenge to install software or do application build upgrades due to the limited amount of CPU given to this instance size. Micro instances can make fantastic web servers, but when you need to do work on the server it can take more time than the typical IT pro has patience for.

Here is a quick tip: Change the instance size for patching and installs.

1) Stop the micro instance for your maintenance or install work.
2) Change the instance size to Large (or X-Large if you need a huge box for the install).
3) Start the instance
4) Run your install, upgrade, etc. I've found that I can usually do most of my maintenance or installs in less than an hour on a Large instance = $0.52
5) Stop the instance
6) Change the instance size back to Micro
7) Start the instance again.

The starting and stopping take seconds, and the upgrade to Large is instantaneous. Following these steps will lead to pain free patching, installs and upgrades for less than the price of a latte.

-Kris