Jeremy Davis's picture

Thanks for taking the time to post back and I'm glad to hear that you got your issues sorted.

FWIW even if you can't boot; you can still mount the volume. I meant mounting the volume (of your broken instance) to a new (not broken) instance as a secondary volume. You can then chroot into the old volume and install/remove/tweak packages etc (e.g. in this case you could have manually installed the Wheezy kernel). Anyway sounds like that is no longer relevant (although may be useful knowledge for future reference).

New HVM instances don't have this issue because they use a different mechanism at boot-time. Creating new HVM images has been on our roadmap for sometime but there have been some technical holdups. We are currently beta testing our HVM images and hope to release them ASAP.

Regarding TKLBAM; it's always useful! :) Sorry to be facetious. Did you test it, or just assume that it wouldn't work? By default it will backup everything in /var/www (the usual webroot) and all MySQL DBs. It also knows which additional packages that you installed from default repos and will install them on restore/migration. You can use overrides to include other areas of the filesystem if you want (or exclude parts included by default).

Currently OOTB limitations are that it won't automatically (re)install software from non-default repos (i.e. anything that is not in Debian or TurnKey repos) or software installed using other mechanisms (e.g. python packages installed with pip or perl packages installed by cpan). But even those can be easily worked around using the hooks mechanism.