Changes

== Owner ==

== Owner ==

* Name: [[User:Gregorio| Greg Smith]]

* Feature request: [[User:Gregorio|Greg Smith]]

 

* Implementation: [[User:tch|Martin Abente]]

* Email: gregsmithpm at gmail.com

== Current status ==

== Current status ==

* Targeted release: ?

* Targeted release: 0.88 ([[Dextrose]])

* Last updated: July 7, 2009

* Last updated: Oct 08, 2010

* Percentage of completion: ?

* Percentage of completion: 50%

== Detailed Description ==

== Detailed Description ==

* Allow time based backup and restore of the journal. Check for Journal changes on the Sugar computer. Copy any changes to the server on a regular basis. Stagger the copies so that not all Sugar computers backup at the same time. See implementation of this with XO and XS at: http://wiki.laptop.org/go/XS_Blueprints:Datastore_Simple_Backup_and_Restore

* Allow time based backup and restore of the journal. Check for Journal changes on the Sugar computer. Copy any changes to the server on a regular basis. Stagger the copies so that not all Sugar computers backup at the same time. See implementation of this with XO and XS at: http://wiki.laptop.org/go/XS_Blueprints:Datastore_Simple_Backup_and_Restore

* Provide a web based GUI to restore one or all backed up journal entries. The user would boot up any Sugar implementation (user name/password based security is also important) and point their Web browser at a URL on the server. Preferable to automatically take you to the right page (aka the page where your particular Sugar instance is backed up) but would also accept seeing a list of Sugar Journals by user name and picking the right one. Clicking on a single Journal entry or on a link for "full journal" would download those items back in to the journal of the Sugar computer.

* Provide a GUI to restore all backed up journal entries

* Provide a user initiated backup of the journal. In this case a User would use their web browser to go to a page on the server and click the "backup" link. Then the server would check for changes since the last backup and copy everything from that journal to the server. Same case as above for restore.

* '''TODO:''' Provide an interface to restore one backed up journal entry. The user would boot up any Sugar implementation (user name/password based security is also important) and point their Web browser at a URL on the server. Preferable to automatically take you to the right page (aka the page where your particular Sugar instance is backed up) but would also accept seeing a list of Sugar Journals by user name and picking the right one. Clicking on a single Journal entry or on a link for "full journal" would download those items back in to the journal of the Sugar computer.

* Backup and restor of full sugar instance. Same as above (AKA user initiated and time based server/script) but for the full Sugar instance. This can be only the full instance and does not need to list individual files. For restoring SoaS should support booting up with a USB stick, going to the page, then removing the USB stick and inserting a new one, then clicking restore. This would copy the full Sugar instance to the new USB stick. This would now be a clone of the original USB stick. Also, implement a "clone" feature which allows the same work flow as above but without a server. That is, put a SoaS in a computer, copy it to the computer then restore it to a new USB stick with the full SoaS including configuration.

* Provide a user initiated backup of the journal. Same case as above for restore.

* Implementing a standard Linux package to do this for Sugar would be fine.

* '''TODO:''' Backup and restore of full sugar instance. Same as above (AKA user initiated and time based server/script) but for the full Sugar instance. This can be only the full instance and does not need to list individual files. For restoring SoaS should support booting up with a USB stick, going to the page, then removing the USB stick and inserting a new one, then clicking restore. This would copy the full Sugar instance to the new USB stick. This would now be a clone of the original USB stick. Also, implement a "clone" feature which allows the same work flow as above but without a server. That is, put a SoaS in a computer, copy it to the computer then restore it to a new USB stick with the full SoaS including configuration.

* See also this bug in Sugar: http://dev.sugarlabs.org/ticket/75 and http://dev.sugarlabs.org/ticket/916

* See also this bug in Sugar: http://dev.sugarlabs.org/ticket/75 and http://dev.sugarlabs.org/ticket/916

== How To Test ==

== How To Test ==

Create some entries in a journal. Then test with:

Create some entries in a journal. Then test with:

* SoaS 8.6 or later and a single computer.

* Dextrose 1 or later and a single computer

* SoaS 8.6 or later with XS running 0.5 or later.

* Dextrose 1 or later with XS running 0.5 or later

* '''TODO:''' Test backup and restore of a single journal entry

* Test backup and restore of a single journal entry

* '''TODO:''' Test backup and restore of a full SoaS image. Make sure to use the SoaS so that it changes some files and configurations.  

* Test backup and restore of a full SoaS image. Make sure to use the SoaS so that it changes some files and configurations.  

* Test time based backup, preferably with several computers.

* Test time based backup, preferably with several SoaS computers.

In all cases, ensure that the files are backed up on the server and can be restored on the SoaS. Make sure to open the files in the journal and run them. Also, make sure to cold boot any full images and confirm that changes were saved.

In all cases, ensure that the files are backed up on the server and can be restored to the original computer. Make sure to open the files in the journal and run them. Also, make sure to cold boot any full images and confirm that changes were saved.

== User Experience ==

== User Experience ==

== Dependencies ==

== Dependencies ==

* See http://dev.sugarlabs.org/ticket/916 for changes to allow registering SoaS to a XS.

* See http://dev.sugarlabs.org/ticket/916 for changes to allow registering SoaS to a XS.

* Also ds-backup-client package is required to backup to an XS along with a patch to allow it to work on SoaS in addition to an XO.

* Also ds-backup-client package is required to backup to an XS along with a patch to allow it to work on SoaS in addition to an XO.

== Contingency Plan ==

== Contingency Plan ==

Plan B is to find a manual way to execute a script which does an "rcp" or other file transfer to a server. Then allows restore via script as well.

None required.

== Documentation ==

== Documentation ==