Rackspace Cloudvent Calendar Day 3: Avoiding Disaster: Polyglot Backup

Filed in Cloud Industry Insights by Hart Hoover | December 3, 2013 12:00 pm

In the spirit of the holiday season, I’m sharing some tips and features of our cloud that you may not know about. In this countdown I’ll have 24 posts for you, each covering a single topic or feature about Rackspace Cloud products. We’ll post one per day so keep checking back!

At Rackspace, we offer two options for backup in the cloud: image-based backup and the Cloud Backup service. Rackspace, by default, does not back up your servers – we want to give you the freedom to define how and when your data is backed up. In this post, we’ll take a quick look at both so you can determine how you want to use these services in your backup strategy.

Images are a combination of three OpenStack[1] services working together: Nova[2] (compute: Cloud Servers), Glance[3] (images) and Swift[4] (object storage: Cloud Files).  When you create an image via the Control Panel or API, the OpenStack Compute service has the hypervisor create a snapshot of the disk of your running server. That image is then uploaded to our image service and stored in Cloud Files. That image can then be used to create new servers. Since the launch of our Performance Flavors[5], imaging has changed a bit. You now have two disks: a system disk and one or more data disks. The imaging process takes the snapshot of the system disk only. More information on this difference is available in our Knowledge Center[6].

Cloud Backup[7], on the other hand, is a file-level backup service. A small software agent runs on your servers and works to compress and encrypt your data based on an inclusion list you define. Your backup data is stored in Cloud Files where it is written to three different storage nodes. You can also rest easy: you can get an email notification if a backup fails. If you’re a developer, you can programmatically control Cloud Backup via the API[8].

You can use both of these technologies for different areas of the same application. For example: imaging may work better for web and application servers, while your database needs a file-level solution that is encrypted for security.

Keep checking back as we move forward into the month of December!

Endnotes:
  1. OpenStack: http://openstack.org
  2. Nova: https://wiki.openstack.org/wiki/Nova
  3. Glance: https://wiki.openstack.org/wiki/Glance
  4. Swift: https://wiki.openstack.org/wiki/Swift
  5. Performance Flavors: http://www.rackspace.com/blog/got-the-need-for-speed-meet-performance-cloud-servers/
  6. our Knowledge Center: http://www.rackspace.com/knowledge_center/article/system-disk-and-data-disk-faq
  7. Cloud Backup: http://www.rackspace.com/cloud/backup/
  8. via the API: http://docs.rackspace.com/rcbu/api/v1.0/rcbu-devguide/content/overview.html

Source URL: http://www.rackspace.com/blog/rackspace-cloudvent-calendar-day-3-avoiding-disaster-polyglot-backup/