Problem restoring backup turnkey-redmine-12.0-squeeze-x86 (File "/usr/lib/tklbam/deps/bin/duplicity", line 1405, in <module

Yoel Unanue Mac Lennan's picture

Hello , I have a probem to try to restore a backup of one of my servers , backup is successful in amazon , but try to restore to another server , I found this problem.

Thanks for your help

Passphrase: 
Restoring duplicity archive from s3://s3-sa-east-1.amazonaws.com/tklbam-k************
Local and Remote metadata are synchronized, no sync needed. 
Last full backup date: none 
Traceback (most recent call last): 
File "/usr/lib/tklbam/deps/bin/duplicity", line 1405, in <module> 
with_tempdir(main) 
File "/usr/lib/tklbam/deps/bin/duplicity", line 1398, in with_tempdir 
fn() 
File "/usr/lib/tklbam/deps/bin/duplicity", line 1332, in main 
restore(col_stats) 
File "/usr/lib/tklbam/deps/bin/duplicity", line 637, in restore 
restore_get_patched_rop_iter(col_stats)): 
File "/usr/lib/tklbam/deps/bin/duplicity", line 659, in restore_get_patched_rop_iter 
backup_chain = col_stats.get_backup_chain_at_time(time) 
File "/usr/lib/tklbam/deps/lib/python2.6/dist-packages/duplicity/collections.py", line 947, in get_backup_chain_at_time 
raise CollectionsError("No backup chains found") 
CollectionsError: No backup chains found 

Traceback (most recent call last):  File "/usr/bin/tklbam-restore", line 385, in <module>  main()  File "/usr/bin/tklbam-restore", line 343, in main  opt_limits, opt_time, credentials=credentials, rollback=not no_rollback)  File "/usr/lib/tklbam/restore.py", line 104, in __init__  backup_archive = self._duplicity_restore(address, cache_size, cache_dir, credentials, secret, time)  File "/usr/lib/tklbam/restore.py", line 88, in _duplicity_restore  duplicity.Command(opts, '--s3-unencrypted-connection', address, tmpdir).run(secret, credentials)  File "/usr/lib/tklbam/duplicity.py", line 78, in run  raise Error("non-zero exitcode (%d) from backup command: %s" % (exitcode, str(self)))  duplicity.Error: non-zero exitcode (30) from backup command: duplicity --archive-dir=/var/cache/duplicity --s3-unencrypted-connection s3://s3-sa-east-1.amazonaws.com/tklbam-k************ /tmp/tklbam-j***aL 
Jeremy Davis's picture

Are you trying to restore to another v12 appliance? If so is it possible to try restoring to a v13 appliance instead?

I'm not sure if it's the cause of the issue but the Hub API changed since v12 and as v12 has been officially retired for some time now, an updated version of TKLBAM was never produced for v12. We may be able to provide a patch if you really need v12...

Let me know

PS I hope you don't mind I edited the layout of your post a little...

Yoel Unanue Mac Lennan's picture

Hi Jeremy , thanks for answering . I did not know that I can migrate to version 13 , I'll try , I thought it was another version different from redmine .

I can recover a backup of a server version 12.0 to version 13.1 ? I use the application redmine

if I can not write you do it again , thank you for your work and your response.

sorry for my bad English .

Jeremy Davis's picture

TKLBAM was originally designed to be used to migrate data from one version to another - as well as providing backups (the 'B' in TKLBAM).

TBH I'm not 100% sure but I would expect it to work fine... Have a go and see what happens.

Post new comment