Jeff Hales's picture

I've input my Hub API key and then run a simulated backup within the Webmin TKLBAM module after signing up for the Amazon S3 services, but I get the following result:

> tklbam-backup --simulate
Traceback (most recent call last):
File "/usr/bin/tklbam-backup", line 267, in <module>
main()
File "/usr/bin/tklbam-backup", line 196, in main
conf.profile = get_profile(hb)
File "/usr/bin/tklbam-backup", line 123, in get_profile
new_profile = hb.get_new_profile(turnkey_version, profile_timestamp)
File "/usr/lib/tklbam/hub.py", line 207, in get_new_profile
response = self._api('GET', 'archive/timestamp/', attrs)
File "/usr/lib/tklbam/hub.py", line 185, in _api
return API.request(method, self.API_URL + uri, attrs, headers)
File "/usr/lib/tklbam/hub.py", line 129, in request
raise Error(c.response_code, name, description)
hub.Error: (404, 'BackupArchive.NotFound', 'Backup profile archive not found: turnkey-lapp-11.0rc-lucid-x86')

Is there some further set-up necessary before the initial backup will work?

edit: I just remembered the lapp appliance was not supported. I am using the LAPP v11 RC1 appliance; is this not supported by TKLBAM yet?

Forum: 
Alon Swartz's picture

Hi Jeff, you remembered correctly. PostgreSQL support is in development, so the following appliances currently don't have associated tklbam profiles (postgresql, lapp, openbravo). As a side note, Zimbra doesn't have support either as it uses an embedded MySQL server.

Add new comment