Set Up an Offsite Backup for LAVA Data

Registered by Andy Doan on 2012-04-18

We need to create a mechanism to back up the data used by the validation server to an offsite location like Amazon S3. This serves two purposes:

1) make an easier mechanism for Linaro approved developers to test with real data
2) add another layer of redundancy to validation lab

The database itself is relatively small (<1GB). The media files are larger, but they can also take advantage of an incremental backup approach.

NOTE: This needs some research and a clear plan. ie - is S3 really the best approach or would something like Google Drive be better since we already have Google apps.

Blueprint information

Status:
Not started
Approver:
Andy Doan
Priority:
Low
Drafter:
Michael Hudson-Doyle
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
Accepted for trunk
Implementation:
Not started
Milestone target:
milestone icon backlog

Related branches

Sprints

Whiteboard

[liuyq0307, 2012-05-03] something need to be cleared.like the data scope(which data should be backuped, database/attachment/configure file/others), the backup method(how to backup, cp/rsync/incremental backup approach/others, ftp/nfs/samba/others), where to backup(S3/Google Drive/Some Lava Place/other place), the restore method, and the backup generation(no limit/10 generation?)

Meta:
Headline: TBD
Acceptance: TBD

(?)

Work Items

Work items:
[liuyq0307] Talk to mwhudson to know more about it: TODO

This blueprint contains Public information 
Everyone can see this information.