XS Blueprints:Datastore Simple Backup and Restore: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Summary= |
=Summary= |
||
At a school that has an XS in place, the Datastore Simple Backup (aka ds-backup) provides an automatic and invisible backup of the documents present in the Journal of each XO. This can be used for recovery of old documents if they have been deleted or overwritten and when the laptop is replaced or reflashed. |
|||
The storage of documents in the XS is also useful for other uses, such as a simple publishing mechanism. |
|||
A strong DS-Backup facility and good availability of the XS allows users to delete large documents to have space on their XOs, knowing that the XS will hold their docs. |
|||
=Scenarios= |
=Scenarios= |
||
* Jim has deleted or changed a TurteArt activity he did last month, and now he wants it back to use it as a starting point for a new activity. |
|||
* Jocinta's XO broke, and has been repaired and reflashed, so her documents are gone. She wants to retrieve them from the backup on the XS. |
|||
=Implementation Notes= |
=Implementation Notes= |
||
=Walk through= |
=Walk through= |
||
| Line 10: | Line 21: | ||
=TODOs and future work= |
=TODOs and future work= |
||
* Automagic authentication & Moodle integration |
|||
* In order to be simple, the initial implementation does not cover a "complete restore" scenario, which requires more work |
|||
** on the Sugar UI to trigger, display progress and manage (cancel/retry) a "complete restore" |
|||
** on the user aliasing that needs to take place in the "replaced laptop" scenario |
|||
* We need to test, time and tune the traffic control & backoff settings. |
|||
* Must confine rsync-over-ssh with a chroot jail or a |
|||
Revision as of 22:03, 7 July 2008
Summary
At a school that has an XS in place, the Datastore Simple Backup (aka ds-backup) provides an automatic and invisible backup of the documents present in the Journal of each XO. This can be used for recovery of old documents if they have been deleted or overwritten and when the laptop is replaced or reflashed.
The storage of documents in the XS is also useful for other uses, such as a simple publishing mechanism.
A strong DS-Backup facility and good availability of the XS allows users to delete large documents to have space on their XOs, knowing that the XS will hold their docs.
Scenarios
- Jim has deleted or changed a TurteArt activity he did last month, and now he wants it back to use it as a starting point for a new activity.
- Jocinta's XO broke, and has been repaired and reflashed, so her documents are gone. She wants to retrieve them from the backup on the XS.
Implementation Notes
Walk through
Test plans
TODOs and future work
- Automagic authentication & Moodle integration
- In order to be simple, the initial implementation does not cover a "complete restore" scenario, which requires more work
- on the Sugar UI to trigger, display progress and manage (cancel/retry) a "complete restore"
- on the user aliasing that needs to take place in the "replaced laptop" scenario
- We need to test, time and tune the traffic control & backoff settings.
- Must confine rsync-over-ssh with a chroot jail or a