You are here
tklbam seems not to work ??
today i have been testing tklbam ... I did follow the instructions in the case study:
1 - launch a turnkey appliance from amazon console (turnkey apache tomcat lucid)
2 - run tklbam init ; tklbam backup
2 - install some packages ... nxserver, lxde, chrome and sun java.
3 - run tklbam backup
4 - And now ... I start another instance of the same appliance
5 - run tklbam init ; tklbam backup ; tklbam restore {id of the backup of the other appliance}
6- restart
The backup does not show any error but the instance seems no to work, in particular , I tried
the command java -version , and i got the message "java command not found"
I do not know if I am doing something wrong. Please could any one bring some light ?
Thank you and kind regards.
Omar
Need more information
Hi Liraz Those are all the
Hi Liraz
Those are all the commands I typed in the server in order to install them mentioned packages (from the ./bach_history)
here is the restore log (the last bit of it)
the last bit of the backup log
I have found that the nx
I have found that the nx server has not been backup, maybe due to the way i installed it :
From my understanding...
AFAIK TKLBAM leverages the package management system to install any extra packages from default appliance state (ie any extra packages that aren't installed originally).
I'm not sure but I suspect that as this package isn't available from a repo, TKLBAM doesn't know where to get it from and hence its not included. It's a scenerio which probably should be accounted for.
If that's the case, you may be able to work around it by manually including the app path as part of the backup. Another possible workaround may be to host a repo locally for that deb (and any other custom ones).
Configure repositories before restoring
As JedMeister correctly suspected, when you tklbam-restore from a new installation, TKLBAM is not aware of the new package repositories on your old installation and it doesn't attempt to synchronize them. This is by design, as otherwise we wouldn't be able to use TKLBAM to upgrade between different versions of Ubuntu or migrate between Ubuntu and the upcoming Debian versions, etc.
TKLBAM hook example
One of my cloud servers uses packages from multiverse, which is not enabled by default in TKL, which means even though TKLBAM knows about them in the backup, they are not installed when I launch a new server from the backup.
I wanted everything to be automated, so I created the following TKLBAM hook, and thought that others might find it useful:
Note that just enabling multiverse in state=pre and letting TKLBAM take care of the package installation won't work on a newly launched server because the backed up filesystem is not restored until after package installation.
Add new comment