FYI,<br> Awhile back ago, I developed a quick-n-dirty little <b><u>rsync</u></b> script which can be ran on the XO Laptop at any time and regularly.<br><br>Here's the latest online version...<br> <a href="http://wiki.laptop.org/go/User:Ixo/Script/xo-backup-server">http://wiki.laptop.org/go/User:Ixo/Script/xo-backup-server</a><br>
<br>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.<br>(currently only acts as 'disaster recovery archive', but with slight mods could be updated to save the last N number of backups)<br>
<br>A similar idea / concept, was to do the reverse, from the SERVER backup each laptop when available...<br> <a href="http://wiki.laptop.org/go/User:Ixo/Script/get-xo">http://wiki.laptop.org/go/User:Ixo/Script/get-xo</a><br>
<br>Freely CC-GNU-GPL 'ed , hope it helps, -Ixo<br><br><div class="gmail_quote">On Mon, Apr 21, 2008 at 8:38 PM, Michael Stone <<a href="mailto:michael@laptop.org">michael@laptop.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Martin,<br>
<br>
Based on feedback from Peru, Mexico, and Nepal, the "restoration from<br>
disaster-recovery backups" XO/XS coordination feature has been steadily<br>
rising in priority. I also notice that "Backups" is your first line-item<br>
on the XS-0.3 roadmap.<br>
<br>
My large question is: "what changes need to be made to the XO's OS,<br>
(currently to candidate-703) in order to make progress in this feature<br>
cluster?"<br>
<br>
Relevant tickets<br>
----------------<br>
<br>
#24 ROT cscott (Backup of laptops - short-term solution)<br>
#2516 STK tomeu (Automatic backup of laptops to XS)<br>
#3334 DSN jg (Exactly what should be backed up?)<br>
#4569 DSN jg (Controlling disk usage of backups)<br>
#4224 DSN krstic (Manage SN <-> "identity" mapping on XS)<br>
<br>
#4270 PKG wad (Full restore from school server)<br>
#4380 TST tomeu (Restore individual entry from school server)<br>
#4275 DSN tomeu ("Keep" UI)<br>
#4587 ESC tomeu (Mass-export Journal to USB key)<br>
<br>
#6374 PKG martin (Package the xo-backup tools for the school server)<br>
#4100 STK krstic (XS should provide human readable index of journal backup)<br>
<br>
Sub-questions:<br>
<br>
* What backup scheme do we actually intend to deploy? (Current choices appear<br>
to be Wad's "dumb-rsync" method [1] and Ivan's method [2].<br>
<br>
[1]: <a href="http://lists.laptop.org/pipermail/server-devel/2008-February/000314.html" target="_blank">http://lists.laptop.org/pipermail/server-devel/2008-February/000314.html</a> (outdated)<br>
[2]: <a href="http://wiki.laptop.org/go/XS_backup_restore" target="_blank">http://wiki.laptop.org/go/XS_backup_restore</a><br>
<br>
* Does the chosen scheme permit us to sanely combine old backups with<br>
an XO build that makes breaking changes to file layouts?<br>
<br>
Regards,<br>
<br>
Michael<br>
<br>
<br>
Key: ??? - status or author unknown<br>
TST - needs to be tested in a build<br>
BLD - needs to be put into a build<br>
PKG - pkg needs to be built<br>
DBG - debugging/diagnosis still needed<br>
DSN - design needed<br>
STK - stuck; a decision is needed about how to proceed<br>
SGN - a signoff is needed<br>
ESC - canceled or siginificantly reduced in priority<br>
FIN - successfully finished<br>
MSG - communication needed<br>
ROT - solution has bitrotted<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</blockquote></div><br>