nssbackup-team team mailing list archive
-
nssbackup-team team
-
Mailing list archive
-
Message #00855
[Bug 503597] Re: NSSbackup fails due to name convention
** Attachment added: "nssbackup.log"
http://launchpadlibrarian.net/37465756/nssbackup.log
** Description changed:
for quite some time now NSSbackup is running in the background.
I usually check for a full backup once a month. I move the full backup
folder to an external HDD and collect them there, some I burn on DVD in
addition.
On every Incremental backup I get an corrupt backup.
This does happen if the backup destination has little or much free
space. (With much I mean >2 gig and I think that the changes are about
50 MB)
- The strange thing is that the backup folder starts as a
- 2010-01-05_08.00.10.089553.ubuntu.inc
+ The strange thing is that the backup folder starts as a
+ 2010-01-05_08.00.10.089553.ubuntu.inc
and becomes a
- 2010-01-05_08.00.10.089553.ubuntu.corrupt
-
+ 2010-01-05_08.00.10.089553.ubuntu.corrupt
after a while.
+ Full backups do work. Recovering files from a full backup does work too.
+
I can provide many other log files of similar nature if it helps ;-)
** Description changed:
for quite some time now NSSbackup is running in the background.
I usually check for a full backup once a month. I move the full backup
folder to an external HDD and collect them there, some I burn on DVD in
addition.
On every Incremental backup I get an corrupt backup.
- This does happen if the backup destination has little or much free
- space. (With much I mean >2 gig and I think that the changes are about
- 50 MB)
+ This does happen if the backup destination has little or much free space. (With much I mean >2 gig and I think that the changes are about 50 MB)
+ I know that once I have a full backup (about 6 GB) on the HDD there is not enough space left for another one but usually there are about 2 GB which should be sufficient for a incremental backup I thought.
The strange thing is that the backup folder starts as a
2010-01-05_08.00.10.089553.ubuntu.inc
and becomes a
- 2010-01-05_08.00.10.089553.ubuntu.corrupt
+ 2010-01-05_08.00.10.089553.ubuntu.corrupt
after a while.
Full backups do work. Recovering files from a full backup does work too.
I can provide many other log files of similar nature if it helps ;-)
--
NSSbackup fails due to name convention
https://bugs.launchpad.net/bugs/503597
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.
References