Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Difference between archive's size before and after ftp upload #121

Open
adynemo opened this issue Feb 27, 2019 · 6 comments
Open

Difference between archive's size before and after ftp upload #121

adynemo opened this issue Feb 27, 2019 · 6 comments

Comments

@adynemo
Copy link

adynemo commented Feb 27, 2019

Hi,
In /var/archives/ my master tar.gz file is 78G. But after the ftp upload, in my second server (backup server), the same file is 39,6G...

Why this difference?

@linxon
Copy link

linxon commented Feb 28, 2019

cirno-chan:/var/archives # file cirno-chan-boot.20190226.master.tar.lzma 
cirno-chan-boot.20190226.master.tar.lzma: symbolic link to /var/archives/cirno-chan-boot.20190227.master.tar.lzma

@adynemo
Copy link
Author

adynemo commented Feb 28, 2019

Sorry, but in what that helps me?

@linxon
Copy link

linxon commented Feb 28, 2019

(i'm not developer and... i'm bad know english ^_^)

I can assume that your config use symbolic links which the backup-manager creates automatically in /var/archives, if the data hashsum is the same as the previous one...

may be ftp uploader is not work with relative file paths or can't work with symbolic links

you can try to find a duplicate files in your server:

~$ fdupes --help
~$ fdupes -m /path/to/backup/files

@adynemo
Copy link
Author

adynemo commented Feb 28, 2019

I'm bad know english too ^^
First, thank you so much if you don't be a developer and english is not your language, this is very kind of you to help me :)

fdupes isn't installed on my debian but I'm sure the archive created by BM in /var/archives is not a symbolic link.
When I do ls -lah, the file isn't displayed like a symbolic link and when I do file name_of_file.tar.gz I have this: name_of_file.tar.gz: gzip compressed data, from Unix

I have seen logs and ftp had made errors:

Feb 27 18:00:53  backup-manager-upload[23856]: error * Unable to transfer /var/archives/Owncloud-2-var-www-html-owncloud-data-DrWhat-files-Marvel.20190227.master.tar.gz: Since you see this ABOR must've succeeded - BackupManager::Dialog::print_error (/usr/bin/backup-manager-upload l. 764)
Feb 27 18:00:53  backup-manager-upload[23856]: error * The upload transfer "ftp" failed. - BackupManager::Dialog::print_error (/usr/bin/backup-manager-upload l. 1059)
Feb 27 18:00:54  backup-manager[19535]: error * Error reported by backup-manager-upload for method "ftp", check "/tmp/bmu-log.3vGdCh".

Obviously, something happened during the transfer. But what? My other server for the backup has some size limit for the ftp, my main server, or Backup-Manager?

@adynemo adynemo changed the title Difference between archive before and after ftp upload Difference between archive's size before and after ftp upload Feb 28, 2019
@kissifrot
Copy link
Collaborator

Did you check the content of the /tmp/bmu-log.3vGdCh file ?

@adynemo
Copy link
Author

adynemo commented Mar 1, 2019

Thks, I do not know this file.
But there is no more ^^
Unable to transfer /var/archives/Owncloud-2-var-www-html-owncloud-data-DrWhat-files-Marvel.20190227.master.tar.gz: Since you see this ABOR must've succeeded The upload transfer "ftp" failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants