I beg to differ. IMO, the best solution would be to have backupmenu as modular set of scripts, invoked by user from shell (as early as possible, preferably the way like Mentalist's recovery shell does it, as posted a page or two back). This way, if anything fails, user have:

a) full log of what's going on
b) we don't need to rely on text2screen or any other mumbo-jumbo
c) we don"t need to be kept in stone age by not upgrading busybox (stupid, as bugs and security fixes are important).
d) fixing every "module" (script) in case of changes is trivial.

I really don't like monolithic pieces of code (hello, systemd) that makes me feel like I'm using windows 8.5, and not fixing bugs/updating such critical component as busybox is not acceptable.

/Estel