Difference between revisions of "Trove/scheduled-tasks"
Line 2: | Line 2: | ||
* '''Created''': 13 Aug 2013 | * '''Created''': 13 Aug 2013 | ||
* '''Contributors''': Craig Vyvial (cp16net) | * '''Contributors''': Craig Vyvial (cp16net) | ||
+ | |||
+ | __FORCETOC__ | ||
= Automated/Scheduled Backups Design = | = Automated/Scheduled Backups Design = |
Revision as of 16:11, 13 August 2013
- Created: 13 Aug 2013
- Contributors: Craig Vyvial (cp16net)
Automated/Scheduled Backups Design
Overview
The goal of this blueprint is to implement capabilities in Trove to support automated/scheduled backups. This will be supported in the Trove API as well as the guest agent to use the existing snapshot-design in an automated way. The automated backups shall allow a user to restore or clone to a new instance at a point in time.
There are many different concerns when attempting to automate the backup of instances in a deployment, i.e. Stagger Backups, Time Windows, and others. In the design of this automated system each of these concerns should be capable of being addressed. This shall lead to a pluggable or configurable interface for allowing a deployer to chose what type of strategy they would like to use without a code change.
Design Goals
The following are the design goals:
- Pluggable interface to determine the type of strategy(s) to support. (Stagger Backups, Time Windows, and others)
- Manage network bandwidth and connections from backups
- Database support for the schedule set and listing of the backups