Closed SystemZ closed 8 years ago
Hi Michał, Just a shot in the dark: is there a non-ascii character in the source or destination path? Philipp
Hi Philipp,
No idea :)
I think not, I'm using default Proxmox dirs and configs.
Path looks like this /var/lib/vz/dump
file names looks ok too. Maybe when proxmox task is invoking command there are some strange chars.
Do you have any idea how to check this effectively?
Is there any way to filter/trim this?
Hi Michał,
I just added a parameter to the xargs
invocation. This should make the whole upload command end up in the log. Maybe we can find something special in there.
There should be something like that:
INFO: /usr/local/bin/b2 upload_file ipabackup /rpool/backup/dump/vzdump-qemu-100-2016_04_06-11_13_21.vma.lzo.sha1sums ipapm2/rpool/backup/dump/vzdump-qemu-100-2016_04_06-11_13_21.vma.lzo.sha1sums
I still suspect some non-ascii chars in there. Not that b2
should choke on that, but I had similar problems before.
Philipp
Thank you, it's very helpful already :)
You were right there is non ascii symbol.
Instead of -
in bucket name there appears â
. Strange, I'll try to copy paste this symbol or transfer it without using nano editor.
Just mounted sftp on my desktop and edited config with gedit and it works! Thank you very much for fast help :) I'll try to contribute download script for restoring backups.
Great to hear you made it work! Before you do too much work, have a look at https://github.com/padelt/vzdump-plugin-b2/blob/master/vzdump-b2-verify.sh , it leaves the dump file after verifying. After moving it in place, Proxmox VE should pick it up and allow you to restore. As always, testing it advised! ;-)
Hello, script seems to be awesome but unfortunately I can't use it because there is some problem with uploading. Direct invoking
b2 upload_file
works ok. I tried to replace xargs to even simpler for loop for upload step but still no luck, same error.Log from Proxmox 4.x backup: