TKLBAM with LAPP 11.1 failing (or it's me failing)

Trying to use tklbam with LAPP 11.1 - with the mahara patch applied.

tklmbam-init went fine, smooth as silk.

However, tklbam-backup provokes this response (I of course authenticate with the proxy first):

Traceback (most recent call last):
File "/usr/bin/tklbam-backup", line 266, in <module>
    main()
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/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.1-lucid-x86')

What am I getting wrong?

Replies (5)

TKLBAM still doesn't support PostgreSQL

Reply 1 2011-02-16

Sorry, PostgreSQL support is still under development.

From /docs/tklbam/faq/general:

Which databases are supported?

"Currently only MySQL. PostgreSQL support is under development. Support for additional databases will be added as needed. Currently TurnKey appliances only include MySQL and PostgreSQL databases."

OH right, the manual

Reply 2 2011-02-16

Thanks Liraz. Sorry to use your time up that way. Zealously backing up with new enthusiasm, I guess :)

SQL dump

Reply 3 2011-05-07

The strategy I'm using is a cron job to dump to an sql file and then rsync to other machines on and off site.

Can't remember the details, as I'm not as fluent with postgres and am not at home or the office. A web search for postgreSQL and dumb and .sql should be a warm start, in the meantime.

You can use TKLBAM hooks as a workaround

Reply 4 2011-05-09

TKLBAM has a hooks mechanism which you can use to execute a command or script before the backup that dumps you pgsql database to a file (e.g., /root/database). There's also a post-restore hook you can use to execute a command that slurps in your pgsql dump into the database.

See /etc/tklbam/hooks.

I can understand your concern

Reply 5 2013-01-18

But to be realistic, TKL is developed by a 2 man team. And while their intentions, plans and dreams are awesome, like most of us they often underestimate the time things will take. Also as you can probably imagine, they also have a huge todo list and constantly shifting (and competeing) priorities.

To complicates matters AFAIK the devs are now looking to create some generic DB backup system (to accommodate current databases plus others into the future). This has pushed back the PostgreSQL support but hopefully will make the addition of new DB engine support to TKLBAM much easier.