What are Scheduled Images?
Cloud Servers users can create two different kinds of images from their running servers: manual, or scheduled. A manual image is d by the user, and runs only one time. A Scheduled Image is an automatically captured image that runs once per day, and retains up to the number of images specified by the user.
Why would I use Scheduled Images?
By having images automatically captured, versus manually triggering them each time, you create an image history. That history can be used to recover your server to the point the image was taken in the case of emergency or server failure.
Note: Images are useful for recovery in many scenarios, but should never be used as your sole source of recovery. We highly recommend Cloud Backup or your preferred backup method be used in conjunction with server images.
How do I use Scheduled Images?
Initiating Scheduled Images is easy, and available to both Control Panel and API users:
Images are stored in Cloud Files, and charged at the normal Cloud Files rate (including any applicable tiering or volume discounts).
How can I tell scheduled images from snapshots I took myself when I look at my image list?
Scheduled images will originally be created with a name based on this scheme:
The best way to tell is to look at the image metadata - though unfortunately, you can't see it in the Cloud Control Panel yet. Using the API or the novaclient command line tool, you will see that an image created by the scheduled images service has the following metadatum on it:
<style="line-height: 1.538em;">org.openstack__1__created_by: scheduled_images_service
For information about using the novaclient tool for scheduled images, check out our Rackspace Knowledge Center article on using python-novaclient to manage images.
Is there a minimum or maximum time between backups?
No (see next answer), but they will be roughly 24 hours apart and occur on different dates UTC.
Will they occur on the same time each day?
In order to operate the scheduled images service with minimal impact on on-demand snapshots and other network-intensive data transfers, the time a snapshot occurs may be changed at any time to optimize load.
Will the image created_at reflect the completion or start time?
The implementation uses the normal OpenStack snapshotting process, so the created_at timestamp will be the time the call was made, i.e., at the start of the snapshot.
Can I miss a day?
If you mean "Can I tell the service to skip a day?" the answer is no. We do not recommend trying to do this manually by disabling scheduled images on a server and then re-enabling them because of the dynamic nature of the scheduling system. It is better just to delete any scheduled images you don't want in your account.
If you mean "Is it possible that a scheduled image will not be made on a particular day for a server," the answer is yes. There are several reasons why this could happen; for example, at the time the snapshot is attempted, your server is in a state that does not allow snapshots to be made (e.g., you are doing a server resize). However, at the current time the service will attempt to create a snapshot or your server three times, with the re-tries being approximately one hour apart. (Note: we are constantly monitoring the service faults, and may change the number or frequency depending upon how the service is performing.)
If you notice two or more consecutively skipped days, you should contact Rackspace support.
What is the "retention" value?
The retention value is the maximum number of scheduled images for that particular server that will be retained in your account. Once the number of scheduled images for this server reaches the retention value, the oldest scheduled image(s) will be deleted so that the total number of scheduled images for this server does not exceed the retention value.
The retention value is set on a per-server basis, i.e., you may specify a different retention value for each server.
What is the maximum retention value?
The maximum retention value in the Rackspace open cloud is 65535. (That's about 179 years of daily images.)
When does automatic deletion occur?
When a scheduled image of a server has successfully completed, the scheduled images service creates a list of all that server's scheduled images and (if necessary) deletes the oldest image(s) until the retention value for that server is reached.
What if I don't want certain images automatically deleted?
Let's suppose that we're talking about the scheduled images for server 'd615a437-aaa9-4a52-a1c0-5bcb0d33038c'. In order to determine how many scheduled images are in your account for this server, the scheduled images service looks only at images that meet the following two constraints:
So, if you remove the metadatum 'org.openstack__1__created_by' from the scheduled image you wish to save, the snapshot will not be subject to retention culling.
At the current time, you cannot modify image metadata via the cloud control panel. If you don't want to make API calls directly, a handy command line tool called the "novaclient" is available. For more information on using the novaclient tool to manage your scheduled images, see this Knowledge Center article on the topic.
How can I change the retention value on my server?
You can change the retention value the same way you originally enabled scheduled images on your server, by
Just specify the new value you wish to use for the retention.
What happens to the scheduled images in my account when I change the retention value?
Nothing at first, but when your next scheduled image is completed, the scheduled images service will use the new retention value when it calculates whether any images need to be deleted from your account.
What if I want to delete a scheduled image right away?
A scheduled image is just a normal snapshot. You can do what you like with it just as you can with your other snapshots. You can delete a scheduled image at any time using your normal workflow (control panel, novaclient, direct API calls).
You say this is a "best effort" service. What does that mean?
"Best effort" service means that you may not specify a particular time at which your server snapshot will be taken, nor can we guarantee what time your scheduled image will become active. We've placed these restrictions because the scheduled times for snapshots are spread out so as not to interfere with each other or with on-demand snapshots. The time before an image becomes active will depend upon the current network traffic load, among other things. We guarantee that all users will receive the same best effort service.
In using scheduled images, please keep the following in mind:
A service similar to scheduled images exists in the "First Generation" Rackspace Cloud. Will the First Generation service stay the same, or will it change to work like scheduled images in the Rackspace Open Cloud?
There are no plans to change the First Generation service; its configuration options will remain the same as they are now.
Where can I get more information about Scheduled Images?
Here's a list:
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License