this is what I did:
1) I created a tkl-core (lucid RC) VM locally in VirtualBox. Recreated the content of a VM on my remote XenServer. Backed it up with TKLBAM.
2) I created a tkl-core (stable) on Amazon and restored the backup. Worked like a charm. Created a new backup from this instance.
3) Deleted the remote XenServer and installed a Proxmox server (Yay! Three cheers to the Proxmox team!).
4) Used the OpenVZ template of the TKL stable core (http://sourceforge.net/projects/turnkeylinuxovz) to create a TKL instance inside Proxmox. (BTW, it needs to be renamed to ubuntu-8.04.3-turnkey_2009.10_i386.tar.gz) in order for it to show up in the proxmox "create VM" menu. BTW2: It would be great to support OvenVZ templates in the regular release cycle of TKL).
5) Restored the Backup from the Amazon instance. Works without problems.
Now I want to get rid of the amazon instance and start backing up the proxmox instance. When I do
Traceback (most recent call last): File "/usr/bin/tklbam-backup", line 267, in main() File "/usr/bin/tklbam-backup", line 234, in main get_server_id()) File "/usr/bin/tklbam-backup", line 110, in get_server_id return ServerConf()['serverid'] File "/usr/lib/python2.5/site-packages/conffile.py", line 42, in __init__ self.validate_required() File "/usr/lib/python2.5/site-packages/conffile.py", line 54, in validate_required raise ConfFileError(error) conffile.ConfFileError: SERVERID not specified in /var/lib/hubclient/server.conf
I am not sure I fully understand the mechanism. When a restored backup is backed up again, is this supposed to go to the original backup or is the target a new backup? Which would make sense because otherwise there might be conflicting changes from the two instances that are derived from it. But that doesn't explain the exception.