Synchronizing xs-0.3 and xo-??? --- backups

[Ixo X oxI]

FYI,
   Awhile back ago, I developed a quick-n-dirty little *rsync* script which
can be ran on the XO Laptop at any time and regularly.

Here's the latest online version...
    http://wiki.laptop.org/go/User:Ixo/Script/xo-backup-server

I've set it up on my XO. And run it when-ever and where-ever it is connected
to the Internet.  Especially after large changes or saved important
documents.
(currently only acts as 'disaster recovery archive', but with slight mods
could be updated to save the last N number of backups)

A similar idea / concept, was to do the reverse, from the SERVER backup each
laptop when available...
   http://wiki.laptop.org/go/User:Ixo/Script/get-xo

Freely CC-GNU-GPL 'ed , hope it helps, -Ixo

On Mon, Apr 21, 2008 at 8:38 PM, Michael Stone <michael at laptop.org> wrote:

> Martin,
>
> Based on feedback from Peru, Mexico, and Nepal, the "restoration from
> disaster-recovery backups" XO/XS coordination feature has been steadily
> rising in priority. I also notice that "Backups" is your first line-item
> on the XS-0.3 roadmap.
>
> My large question is: "what changes need to be made to the XO's OS,
> (currently to candidate-703) in order to make progress in this feature
> cluster?"
>
> Relevant tickets
> ----------------
>
> #24       ROT    cscott      (Backup of laptops - short-term solution)
> #2516     STK    tomeu       (Automatic backup of laptops to XS)
> #3334     DSN    jg          (Exactly what should be backed up?)
> #4569     DSN    jg          (Controlling disk usage of backups)
> #4224     DSN    krstic      (Manage SN <-> "identity" mapping on XS)
>
> #4270     PKG    wad         (Full restore from school server)
> #4380     TST    tomeu       (Restore individual entry from school server)
> #4275     DSN    tomeu       ("Keep" UI)
> #4587     ESC    tomeu       (Mass-export Journal to USB key)
>
> #6374     PKG    martin      (Package the xo-backup tools for the school
> server)
> #4100     STK    krstic      (XS should provide human readable index of
> journal backup)
>
> Sub-questions:
>
>  * What backup scheme do we actually intend to deploy? (Current choices
> appear
>   to be Wad's "dumb-rsync" method [1] and Ivan's method [2].
>
>  [1]:
> http://lists.laptop.org/pipermail/server-devel/2008-February/000314.html (outdated)
>  [2]: http://wiki.laptop.org/go/XS_backup_restore
>
>  * Does the chosen scheme permit us to sanely combine old backups with
>   an XO build that makes breaking changes to file layouts?
>
> Regards,
>
> Michael
>
>
> Key: ??? - status or author unknown
>     TST - needs to be tested in a build
>     BLD - needs to be put into a build
>     PKG - pkg needs to be built
>     DBG - debugging/diagnosis still needed
>     DSN - design needed
>     STK - stuck; a decision is needed about how to proceed
>     SGN - a signoff is needed
>     ESC - canceled or siginificantly reduced in priority
>     FIN - successfully finished
>     MSG - communication needed
>     ROT - solution has bitrotted
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080421/ebdadbc7/attachment.html>