Problem 1/2: VOLNAME.BID.new.gz: No such file or directory
this file is not created every time, why? what can i do?
Problem 2/2: Restoring files…: tar: path/to/file: Not found in archive
-locate finds the file, -restore not!!
i am able to restore some files, some not!? why? what can i do?
legba7@gipsys:/tmp$ su -c "backup2l -r '/home/legba7/logbuch'"
backup2l v1.5 by Gundolf Kiefer
Active files in <all.1003>: 1
gzip: all.1003.new.gz: No such file or directory
found in all.1003: 0 ( 1 left)
gzip: all.1002.new.gz: No such file or directory
found in all.1002: 0 ( 1 left)
found in all.1001: 1 ( 0 left)
Restoring files…
all.1001.tar.gz: 1 file(s) using 'DRIVER_TAR_GZ'
tar: home/legba7/logbuch: Not found in archive
tar: Exiting with failure status due to previous errors
legba7@gipsys:/tmp$ su -c "backup2l -l '/home/legba7/logbuch'"
backup2l v1.5 by Gundolf Kiefer
Active files in <all.1003>: 1
gzip: all.1003.new.gz: No such file or directory
found in all.1003: 0 ( 1 left)
gzip: all.1002.new.gz: No such file or directory
found in all.1002: 0 ( 1 left)
found in all.1001: 1 ( 0 left)
Listing locations…
all.1001: /home/legba7/logbuch
All required archive files are present in /media/nsa210/backup.
legba7@gipsys:/tmp$ ls -lh /media/nsa210/backup/*new*
lrwxrwxrwx 1 504 root 13 3. Jul 20:51 /media/nsa210/backup/all.1001.new.gz -> all.1.list.gz
lrwxrwxrwx 1 504 root 12 3. Jul 17:34 /media/nsa210/backup/TMP.all.new -> TMP.all.list
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Obviously, the content of your backup archive directory is incomplete. Usually, backup2l creates the .new.gz file every time. From your log, I cannot see why it is missing: maybe, backup2l was interrupted unexpectedly during the backup process. The existence of a temporary file named TMP.* indicates so.
BTW, the fact that -locate works whereas -restore does not is a wanted feature: It is allowed to move the pure archive files (e.g. *.tar.gz) away to removable media, for example, in order to save disk space. If you do so, all commands still work exept those that essentially need the big archive file - which is -restore.
Gundolf Kiefer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The identified problem is, TMP.all.new is a sym/hard link on cifs (Common Internet File System) which has a sym/hard link bug and therefore can't delete sym/hard links. The problem belongs to cifs and is not a problem of your software.
Thank you, for your help.
Legba Loa
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Problem 1/2: VOLNAME.BID.new.gz: No such file or directory
this file is not created every time, why? what can i do?
Problem 2/2: Restoring files…: tar: path/to/file: Not found in archive
-locate finds the file, -restore not!!
i am able to restore some files, some not!? why? what can i do?
legba7@gipsys:/tmp$ su -c "backup2l -r '/home/legba7/logbuch'"
backup2l v1.5 by Gundolf Kiefer
Active files in <all.1003>: 1
gzip: all.1003.new.gz: No such file or directory
found in all.1003: 0 ( 1 left)
gzip: all.1002.new.gz: No such file or directory
found in all.1002: 0 ( 1 left)
found in all.1001: 1 ( 0 left)
Restoring files…
all.1001.tar.gz: 1 file(s) using 'DRIVER_TAR_GZ'
tar: home/legba7/logbuch: Not found in archive
tar: Exiting with failure status due to previous errors
legba7@gipsys:/tmp$ su -c "backup2l -l '/home/legba7/logbuch'"
backup2l v1.5 by Gundolf Kiefer
Active files in <all.1003>: 1
gzip: all.1003.new.gz: No such file or directory
found in all.1003: 0 ( 1 left)
gzip: all.1002.new.gz: No such file or directory
found in all.1002: 0 ( 1 left)
found in all.1001: 1 ( 0 left)
Listing locations…
all.1001: /home/legba7/logbuch
All required archive files are present in /media/nsa210/backup.
legba7@gipsys:/tmp$ ls -lh /media/nsa210/backup/*new*
lrwxrwxrwx 1 504 root 13 3. Jul 20:51 /media/nsa210/backup/all.1001.new.gz -> all.1.list.gz
lrwxrwxrwx 1 504 root 12 3. Jul 17:34 /media/nsa210/backup/TMP.all.new -> TMP.all.list
Obviously, the content of your backup archive directory is incomplete. Usually, backup2l creates the .new.gz file every time. From your log, I cannot see why it is missing: maybe, backup2l was interrupted unexpectedly during the backup process. The existence of a temporary file named TMP.* indicates so.
BTW, the fact that -locate works whereas -restore does not is a wanted feature: It is allowed to move the pure archive files (e.g. *.tar.gz) away to removable media, for example, in order to save disk space. If you do so, all commands still work exept those that essentially need the big archive file - which is -restore.
Gundolf Kiefer
The identified problem is, TMP.all.new is a sym/hard link on cifs (Common Internet File System) which has a sym/hard link bug and therefore can't delete sym/hard links. The problem belongs to cifs and is not a problem of your software.
Thank you, for your help.
Legba Loa