Submitted by Volker Wysk <v@volker-wysk.de>
I've tried kbackup, and encountered some problems. I'm
using version
1.2.11 on a Debian Linux
system.
1. There is something wrong with the error message
window, and the log
file. The log file containes a lot of funny characters,
which look like
control sequences which should go to the console. The
error message
screen, on the other hand, lacks the most important
part, the output of
the failed program. This is included in the log file
(between all the
control
characters).
This is an excerpt from the log file (garbage
removed):
This indicates an error during its execution.
The
error message generated
was:
PID 5206, doing:
"swait(1,1)"...
multibuf: Cannot open output file
/dev/nst0!
done
PID 5206, doing:
"swait(0,1)"...done
PID 5206, doing:
"ssignal(1,1)"...done
2. After turning off multibuf, I was able to create a
backup. /dev/nst0 is
correct. I can access it using tar or mt. multibuf
seems to be buggy.
3. Creating the backup was awfully slow. My dat tape
drive is much faster.
I've used the tar
method.
4. Trying afio just resulted in an "archive corrupt"
message.