mgd's picture

I just build a LAPP Turnkey appliance and tried to back it up to my turnkeylinux backups. I intitialized the backup with tklbam-init using my API key and that succeeded. Then, I issued the "tklbam-backup" command and the following appeared:

root@lanmon /etc/tklbam# tklbam-backup
Traceback (most recent call last):
  File "/usr/bin/tklbam-backup", line 266, in <module>
  File "/usr/bin/tklbam-backup", line 195, in main
    conf.profile = get_profile(hb)
  File "/usr/bin/tklbam-backup", line 122, in get_profile
    new_profile = hb.get_new_profile(turnkey_version, profile_timestamp)
  File "/usr/lib/tklbam/", line 205, in get_new_profile
    response = self._api('GET', 'archive/timestamp/', attrs)
  File "/usr/lib/tklbam/", line 183, in _api
    return API.request(method, self.API_URL + uri, attrs, headers)
  File "/usr/lib/tklbam/", line 127, in request
    raise Error(c.response_code, name, description)
hub.Error: (404, 'BackupArchive.NotFound', 'Backup profile archive not found: turnkey-lapp-11.2-lucid-x86')
root@lanmon /etc/tklbam#

Does anyone have an idea what is going on? I noticed that in a previous post that there was an issue with 11.2, but I thought that was resolved.


Jeremy Davis's picture

Have a look at the FAQ. Here is a response to a similar post from about a month ago.

casette's picture

sry if it is a lame question (this is my first post here, hello all)  but i am having the same problem. 

is there any way to stop my instance without losing the data on it?


my error msg btw is 

	hub.Error: (404, 'BackupArchive.NotFound', 'Backup profile archive not found: turnkey-zimbra-2009.10-hardy-x86')
Jeremy Davis's picture

If you are running on an EC2 instance (ie AWS via the Hub) then no. You need to get your info out before you stop it. It's not quite such an issue with EBS backed instances, although you still need to transfer all your info to the EBS volume as the main root volume still may get lost when stopped.

So you'll need to dump your PostgreSQL DB and copy out all your docs from the webroot (assuming your using the LAPP appliance). Doc root should be at /var/www

casette's picture


thank you for your answer. My small EC2 instance ( through the hub) is an S3-backed one, unfortunately. 

I am using a zimbra instance, it has not got Postgres but it is still unsupported by tklbam. It is spelled out plain and simple in the faq and it is all fair play but I still need to find an easy way to back it up. I don't see how I could attach an ebs volume, should I migrate my instance to the aws console? If so, is there a howto on that?

Again, thank you very much for your help.

Jeremy Davis's picture

Liraz has just noted how an unsupported TKL appliance can be backed up by tricking the Hub into thinking that it's a different (and supported) appliance (the example used is tricking the Hub into allowing the backup of a LAPP appliance by pretending it's a Core appliance - see comments on Liraz's blog post here). So theoretically it's possible, but it will involve a lot of trial and error I think with lots of tweaking to the includes config and usage of the tklbam hooks. TBH I wouldn't really know where to start with it but if you hunt around on the Zimbra forums you may be able to find something?

And obviously make sure that everything works with your backup before you rely on it!

If you persevere on this path and manage to get it to work it's be great if you could post back as although I'm sure Liraz will be keen to add this functionality to TKLBAM by default, in the meantime others may be interested.

The other option obviously is to see what other Zimbra users use to backup Zimbra and use that.

Liraz Siri's picture

One thing to note is that the difficulty I spoke of is relative to a TKLBAM-supported appliance - where everything happens automatically. "Tricking" TKLBAM into backing up an unsupported appliance is still much easier than doing a backup/restore from scratch.

Jeremy Davis's picture

My brief searching on the Zimbra forums suggested that the whole Zimbra service can be stopped relatively easily (a single command) although I don't recall what it was OTTOMH. From what I gathered, and assuming that the TKL appliance is set up similar to a default Zimbra install, a complete backup is as simple as stopping the Zimbra service, backing up the complete contents of /opt/zimbra and restarting the Zimbra service.

If I were you I'd set up another Zimbra instance and do some testing. You could even try rsyncing the /opt/zimbra directory across to another instance so that you have a somewhat 'real world' test environment. Once you have it all working as you'd like, then you can do your real server.

Add new comment