Here’s another useful situation where the Cloud Gear service comes in handy.

Today I was modifying a dropdown menu in our SugarCRM instance to add a new status type. For whatever reason the change I made killed the menu and made the system puke rendering it unusable for contacting people. I could have used the nuclear option and reverted it to last night’s backup but that would have meant blowing away all the conversations I had with folks this morning. Cloud Gear allowed me to solve this issue in a more surgical way:

I brought up a fresh JumpBox of the version of SugarCRM we’re running using Cloud Gear and then used the Restore from Amazon S3 feature to bring it current to last night’s backup (when the menu still worked). I was able to then operate on our live system by creating a new menu by the same name and copying over all the status types. Bam! - the menu worked again and none of today’s activity was lost! Total time expended on the fix = 15min. Total cost in hosting = $.20.

This type of quick “data transplant” would be a non-trivial ordeal with traditional methods as this type of surgery would have required provisioning a new environment from scratch and then restoring it from a backup. Cloud Gear makes it painless to bring up a parallel system in the cloud, update it to a working state, extract the “data tissue” necessary for the transplant and then terminate it. In a weird way it’s like having stem cells for your apps.

If you haven’t already given it a try, it’s free to signup for this service and costs only a few cents per hour to experiment. Give it a whirl.