Backup Central

Hi,

I'm running amanda-2.4.4p2 on a Fedora Core 2 having a Dell PowerVault
120T DLT1 with 6 tapes DLT tapes in it.

When performind amdump I get this error while watching the status with
amstatus:

Using /var/lib/amanda/mail1/amdump.1 from Sun Jun 20 11:41:49 CEST 2004


anubis:/data/data0 0 planner: [dump larger than tape, 33895015 KB,
but cannot incremental dump new disk]
anubis:/data/data1 1 17k finished (12:24:03)
anubis:/data/dns0 1 2k finished (12:22:46)
anubis:/data/dns1 1 4k finished (12:22:31)
anubis:/data/etc0 1 0k finished (12:24:00)
anubis:/data/home0 0 16515845k finished (15:26:11)

Ok, I see that /data/data0 is too big to fit on the tape. The questions
I have are:

- is there another solution than splitting /data/data0 into more dumps?
- on the DLT tapes I use is written 40GB/80GB (native/compressed), but
if the tape is defined in amanda.conf as a 40 GB big tape, I get the
message that 'dump does not fit to tape' then it loads a new tape and I
get the same error msg. (the dump should fit in 40GB)

My definition in amanda.conf:

define tapetype DLT {
comment "DLT tape drives"
length 20000 mbytes # 20 Gig tapes
filemark 2000 kbytes # I don't know what this means
speed 1536 kbytes # 1.5 Mb/s
}

Gruss,
Iulian Topliceanu

Iulian Topliceanu wrote:
Hi,

I'm running amanda-2.4.4p2 on a Fedora Core 2 having a Dell PowerVault
120T DLT1 with 6 tapes DLT tapes in it.

When performind amdump I get this error while watching the status with
amstatus:

Using /var/lib/amanda/mail1/amdump.1 from Sun Jun 20 11:41:49 CEST 2004


anubis:/data/data0 0 planner: [dump larger than tape, 33895015 KB,
but cannot incremental dump new disk]
anubis:/data/data1 1 17k finished (12:24:03)
anubis:/data/dns0 1 2k finished (12:22:46)
anubis:/data/dns1 1 4k finished (12:22:31)
anubis:/data/etc0 1 0k finished (12:24:00)
anubis:/data/home0 0 16515845k finished (15:26:11)

Ok, I see that /data/data0 is too big to fit on the tape. The questions
I have are:

- is there another solution than splitting /data/data0 into more dumps?
- on the DLT tapes I use is written 40GB/80GB (native/compressed), but
if the tape is defined in amanda.conf as a 40 GB big tape, I get the
message that 'dump does not fit to tape' then it loads a new tape and I
get the same error msg. (the dump should fit in 40GB)

My definition in amanda.conf:

define tapetype DLT {
comment "DLT tape drives"
length 20000 mbytes # 20 Gig tapes
filemark 2000 kbytes # I don't know what this means
speed 1536 kbytes # 1.5 Mb/s
}

Maybe it would help if you increased length to 40000 mbytes then.
Or run amtapetype to find out exactly how much data it can take, or
search FOM for another 40/80 DLT and use that length.

/Andreas

I'm running amtapetype right now but it might take some time (days maybe)

I see:

Writing 256 Mbyte compressable data: 35 sec
Writing 256 Mbyte uncompresabble data: 105 sec

How do I set hardware compression on in my amanda.conf? Or where do I
set it on?

Gruss,
Iulian Topliceanu

Iulian Topliceanu wrote:

Hi,

I'm running amanda-2.4.4p2 on a Fedora Core 2 having a Dell
PowerVault 120T DLT1 with 6 tapes DLT tapes in it.

When performind amdump I get this error while watching the status
with amstatus:

Using /var/lib/amanda/mail1/amdump.1 from Sun Jun 20 11:41:49 CEST 2004


anubis:/data/data0 0 planner: [dump larger than tape, 33895015
KB, but cannot incremental dump new disk]
anubis:/data/data1 1 17k finished (12:24:03)
anubis:/data/dns0 1 2k finished (12:22:46)
anubis:/data/dns1 1 4k finished (12:22:31)
anubis:/data/etc0 1 0k finished (12:24:00)
anubis:/data/home0 0 16515845k finished (15:26:11)

Ok, I see that /data/data0 is too big to fit on the tape. The
questions I have are:

- is there another solution than splitting /data/data0 into more dumps?
- on the DLT tapes I use is written 40GB/80GB (native/compressed),
but if the tape is defined in amanda.conf as a 40 GB big tape, I get
the message that 'dump does not fit to tape' then it loads a new tape
and I get the same error msg. (the dump should fit in 40GB)

My definition in amanda.conf:

define tapetype DLT {
comment "DLT tape drives"
length 20000 mbytes # 20 Gig tapes
filemark 2000 kbytes # I don't know what this means
speed 1536 kbytes # 1.5 Mb/s
}


Maybe it would help if you increased length to 40000 mbytes then.
Or run amtapetype to find out exactly how much data it can take, or
search FOM for another 40/80 DLT and use that length.

/Andreas

On Sun, Jun 20, 2004 at 09:41:59PM +0200, Iulian Topliceanu wrote:
I'm running amtapetype right now but it might take some time (days maybe)

I see:

Writing 256 Mbyte compressable data: 35 sec
Writing 256 Mbyte uncompresabble data: 105 sec

How do I set hardware compression on in my amanda.conf? Or where do I
set it on?


From that, I think you already have HW compression on.

Actually for runing amtapetype you want it off.

Setting it varies with the OS and the hardware.

Your hardware may first require configuration switch settings
to allow it to be switched on and off.

Your mt command may have options for switching HW compression
on and off.

Your OS tape driver may have a config file specifying the default.

Your selection of a tape device may specify on and off.

--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)

Iulian Topliceanu wrote:

I'm running amtapetype right now but it might take some time (days maybe)

You did read the man-page where it states:

... The -e flag is there to keep the number of file marks down
because they can be slow (since they force the drive to
flush all its buffers to physical media).

For a 40 Gbyte drive, you should:

amtapetype -e 40g -f /dev/...

Instead of days, it takes 4-7 hours maybe (time to write a full
tape twice).


I see:

Writing 256 Mbyte compressable data: 35 sec
Writing 256 Mbyte uncompresabble data: 105 sec

How do I set hardware compression on in my amanda.conf? Or where do I
set it on?

1. You already have hardware compression on.

2. There is no parameter in amanda.conf to turn it on.
It is very OS-specific how to turn it off.
See also (for linux):
http://marc.theaimsgroup.com/?l=amanda-users&m=105370407826462&w=2
http://marc.theaimsgroup.com/?l=amanda-users&m=97671505027309&w=2

3. You better set hw-compr off when using software compression at the
same time (or your tape capacity will be 20% lower). Look in the
archives for the eternal disucussion about the advantages and
disadvantages of software vs hardware compression.
For a start read:
http://marc.theaimsgroup.com/?l=amanda-users&m=108150730118379&w=2


--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens < at > xplanation.com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************