Changes

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>

<noinclude>{{GoogleTrans-en}}{{TOCright}}

[[Category:Features requested by Gardner Pilot Academy|Gardner Pilot Academy]]</noinclude>

<!-- All fields on this form are required to be accepted.

<!-- All fields on this form are required to be accepted.

  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->

  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->

<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->

<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->

== Summary ==

== Summary ==

Easily back up and restore the Journal of a computer running Sugar (includes SoAS and SoLinux with top priority SoAS). Also, easily back up and restore the full Sugar installation. Beyond the Journal, this includes the activities, any configuration of the OS and the everything needed to restore to its original state.

Easily back up and restore the Journal of a computer running Sugar (includes SoaS and SoLinux with top priority being SoaS). Also, easily back up and restore the full Sugar installation. Beyond the Journal, this includes the activities, any configuration of the OS and the everything needed to restore to its original state.

This feature is a top priority for Gardner Pilot Academy but also requests by essentially every XO deployment.

This feature is a top priority for Gardner Pilot Academy but also requests by essentially every XO deployment.

* 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.

* 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.

* 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.

* 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.

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

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

== Scope ==

== Scope ==

Will need client side and server software. May need to move a Linux package to SoAS and may need to push new code upstream to support Journal/Datastore implementation.

Will need client side and server software. May need to move a Linux package to SoaS and may need to push new code upstream to support Journal/Datastore implementation.

== 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.

* SoaS 8.6 or later and a single computer.

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

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

* SoAS 8.6 or later with Linux distribution

* SoaS 8.6 or later with Linux distribution

* Test backup and restore of a single journal entry

* Test backup and restore of a single journal entry

* 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 SoAS 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 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.

== User Experience ==

== User Experience ==

Requires a new "web site" on the server for back up and restore.

Requires a new "web site" on the server for back up and restore.

Requires a configuration option on SoAS to set the time and files to be backed up.

Requires a configuration option on SoaS to set the time and files to be backed up.

== Dependencies ==

== Dependencies ==

== Comments and Discussion ==

== Comments and Discussion ==

* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->

* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->