** Changed in: nssbackup
Status: Fix Committed => Fix Released
** Changed in: nssbackup
Milestone: release0.2 => 0.2rc8
--
Option to ignore "file changed as we read it"
https://bugs.launchpad.net/bugs/400145
You received this bug notification because you are a member of NSsbackup
team
Hi,
I am adding a warning in the Log when TAR returns status code 1.
** Changed in: nssbackup
Importance: Undecided => Medium
** Changed in: nssbackup
Status: New => In Progress
** Changed in: nssbackup
Milestone: None => release0.2
** Changed in: nssbackup
Assignee: (unassi
I managed to find a "backed-up" version of a corrupted backup.
The TAR archive seems valid. It also seems complete although I do not
really know how to tell this for an incremental backup. Is there some
way I can see from the other files in the backup dir what should be
included?
Also when I read
Hello Oumar, thanks for your reply,
Ok, I understand. I thought you were tarring individual files bc. the
changed file name was displayed in the error message. In my tests with
tarring modified files the error message would only give me the folder
name that I was tarring. So I think this is a spec
Hello,
We can't split the processing, cause we are not launching file by file.
We launch TAR just once with the list of files to backup. Then to add
the functionality you want, it should be TAR that would provide it. But
according to what you said, Tar creates a corrupt backup :-/ .
Is it complet
5 matches
Mail list logo
