At 16:40 16.04.2007, Jean-Louis Martineau wrote:
Because most user use tar on linux, and it's new that the blocksize is 1024.
This makes sense. What are the disadvantages of a tar backup?
You can change client-src/sendbackup-dump.c:
AM_SIZE_RE("DUMP: [0-9][0-9]* blocks", 512)
to
AM_SIZE_RE
Because most user use tar on linux, and it's new that the blocksize is 1024.
You can change client-src/sendbackup-dump.c:
AM_SIZE_RE("DUMP: [0-9][0-9]* blocks", 512)
to
AM_SIZE_RE("DUMP: [0-9][0-9]* blocks", 1024)
I also fixed the bug in the latest 2.5.1p3 snapshot available from
http://www.
Mmh, why I'm the only person who ran into these problems?
What should I do now? amanda-2.5.2b1 is in beta phase and I thinks it's no good
idea to use it in a productional environment. Is there a possible workaround?
Thank for helping me
Sebastian
> From the debug file:
> sendbackup: time
From the debug file:
sendbackup: time 2612.878: 62:size(|): DUMP: 17753400 blocks
(17337.30MB)
amanda parse the number of block but it think they are blocks of 512 bytes.
This problem is fixed only in amanda-2.5.2b1 (The MB value is used).
Jean-Louis
Sebastian Henrich wrote:
My OS i
My OS is openSUSE 10.1.
server:~ # tar --version
tar (GNU tar) 1.15.1
server:~ # dump
dump 0.4b41 (using libext2fs 1.38 of 30-Jun-2005)
The last dendbackup.*.debug is attached.
Thanks
Sebastian
At 13:50 13.04.2007, Jean-Louis Martineau wrote:
The orig-kb is the size reported by the backu
The orig-kb is the size reported by the backup tool (tar, dump, ...)
It's possible that amanda doesn't parse the output correctly.
What's your OS? backup tool?
Could you post a sendbackup.*.debug file?
It's probably already fixed in a newer version.
Jean-Louis
Sebastian Henrich wrote:
Here
Here is the result after deleting full-comp und incr-comp.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
-- --
First, thanks very much for your help!
My dumptype definition looks like this:
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress server best
priority high
dumpcycle 0
index yes
}
The global definition consits only of a comment.
Post the amdump.1 log file.
Jean-Louis
Sebastian Henrich wrote:
Hello again,
I still try find the cause of my problems with amanda. When the backup
finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISK
I don't understand.
Did you set a 'comprate' in your dumptype? You should remove it.
Amanda will learn the compresion ratio after a few run.
For all 'info' file, you can remove the value in the 'full-comp' and
'incr-comp' line.
Jean-Louis
Sebastian Henrich wrote:
Here is the log.
Sebastian
Hello again,
I still try find the cause of my problems with amanda. When the
backup finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
11 matches
Mail list logo
