Re: dump larger than tape
On Fri, Sep 3, 2010 at 10:22 AM, Brian Cuttler wrote: > clep /cleplhs lev 1 FAILED [dump larger than tape, -1 KB, skipping > incremental] Looks like a planner bug. > (brought to you by Amanda version 2.4.4) and you'll need to travel at least 6 years back in time to get it fixed! I'd poke at the source to see if I could figure that out, but that's earlier than the Amanda version control goes.. Dustin -- Open Source Storage Engineer http://www.zmanda.com
dump larger than tape
I'm a little baffled...
We had our file systems on UFS and where backing them up ok
but we moved the ZFS, which is usually a 'good thing'.
While some of the file systems are large, in terms of
capacity, none are so large as to not-fit on tape. Even
if they where, I'd understand a DLE failing but not this
many when they fit yesterday at level 0.
History
---
One day ago.
I had some problems with the DLE syntax (my issue, not Amanda's)
but fixed it and forced level 0 dumps, with all dumps going to
tape excepting the xerox partition which failed the estimate phase.
Last night.
I increased the etimeout value and allowed amanda to schedule
levels as it wished. However for reasons that I don't yet understand
the DLE's where all 'too large' for the tape drive.
I'm including the amanda reports from the last two runs.
The tape drive, an SDLT320 has not changed, not the drive,
not the tape type in amanda.conf.
I'll include the # df output also...
thank you,
Brian
One day ago amanda report.
FAILURE AND STRANGE DUMP SUMMARY:
clep xerox lev 0 FAILED [data timeout]
clep oradata lev 0 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)2:09
Run Time (hrs:min) 3:18
Dump Time (hrs:min)2:43 2:43 0:00
Output Size (meg)9997.2 9997.20.0
Original Size (meg) 15507.015507.00.0
Avg Compressed Size (%)64.5 64.5--
Filesystems Dumped8 8 0
Avg Dump Rate (k/s) 1049.3 1049.3--
Tape Time (hrs:min)0:08 0:08 0:00
Tape Size (meg) 10590.710590.70.0
Tape Used (%) 5.45.40.0
Filesystems Taped 9 9 0
Avg Tp Write Rate (k/s) 23842.323842.3--
USAGE BY TAPE:
LabelTime Size %Nb
CLEP03 0:08 10590.75.4 9
NOTES:
planner: Forcing full dump of clep:/ as directed.
planner: Forcing full dump of clep:/export/zone as directed.
planner: Forcing full dump of clep:docs as directed.
planner: Forcing full dump of clep:oracle10 as directed.
planner: Forcing full dump of clep:oradata as directed.
planner: Forcing full dump of clep:samba as directed.
planner: Forcing full dump of clep:source as directed.
planner: Forcing full dump of clep:xerox as directed.
planner: Forcing full dump of clep:/cleplhs as directed.
taper: tape CLEP03 kb 10845120 fm 9 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISK L ORIG-KBOUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
--- -
clep/ 0 7110207 3215328 45.2 42:23 1264.2 2:49 19072.5
clep/cleplhs 01032 320.0 0:000.0 0:02 17.3
clep/export/zone 01032 320.0 0:000.0 0:039.8
clepdocs 01032 320.0 0:000.0 0:048.9
cleporacle10 0 N/A607456 --N/AN/A0:23 26013.2
cleporacle10 0 6169230 3816896 61.9 34:22 1850.6 2:15 28190.3
cleporadata0 0746080 -- 43:20 286.9 0:32 23359.7
clepsamba 0 3340 2432 72.8 0:01 3177.7 0:02 1469.3
clepsource 0 2596340 2456544 94.6 42:28 964.0 1:25 28819.5
clepxerox 0 FAILED --
(brought to you by Amanda version 2.4.4)
Last night's amanda report
- Forwarded message from Amanda/CLEP -
These dumps were to tape CLEP04.
The next tape Amanda expects to use is: CLEP05.
FAILURE AND STRANGE DUMP SUMMARY:
clep /cleplhs lev 1 FAILED [dump larger than tape, -1 KB, skipping
incremental]
clep source lev 1 FAILED [dump larger than tape, -1 KB, skipping
incremental]
clep samba lev 1 FAILED [dump larger than tape, -1 KB, skipping
incremental]
clep oracle10 lev 1 FAILED [dump larger than tape, -1 KB, skipping
incremental]
clep docs lev 1 FAILED [dump larger than tape, -1 KB, skipping
incremental]
clep /export/zone lev 1 FAILED [dump larger than tape, -1 KB, skipping
incremental]
clep oradata lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)1:35
Run Time (hrs:min)15:10
Dump Time (hrs:min) 12:38 12:24 0:14
Output Size (meg) 120835.8 120103.4 732.4
Original Size (meg)151885.9 151864.9 21.0
Avg Compressed Size (%)79.6 79.1 ###.# (
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
> So you are saying i should loock for ~4GB directories tar them instead > to dump them? Just to be on the safe side, and if you are considering to split your backup anyway, it is better to split into pieces that are smaller than the tape size. > I thought amanda can split such big backup archives up in serveral > parts. I doubt that someone will backup up a 200GB System onto one > single tape. Not sure if Amanda can split a single DLE onto several tapes. I use a pre-historic version of Amanda that run single tape :) Spliting your big DLE into pieces (as many pieces as runpercycle) is anyway a good tactic, so on every dump Amanda will backup one of the pieces, and you will end up with equal dump time every day. Else you will have one big day, doing the 200GB and many small other days. Olivier
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
Hi Mario, Take a look at http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes Paddy On 8/8/06, mario <[EMAIL PROTECTED]> wrote: On Tue, 2006-08-08 at 06:34 -0400, Joshua Baker-LePain wrote: > On Tue, 8 Aug 2006 at 11:51am, mario wrote > > >> That said, your tapelist shows 4350 MB, why making chuncks of 4500MB? > >> You may well be facing the same problem again... > > > > I thought amanda can split such big backup archives up in serveral > > parts. I doubt that someone will backup up a 200GB System onto one > > single tape. > > You're looking for the tape spanning feature, which is explained in the > docs. Which chapter is that? I could not find it with: lynx -dump http://www.amanda.org/docs/index.html | grep -i spann Cheers, Mario -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
On Tue, 2006-08-08 at 06:34 -0400, Joshua Baker-LePain wrote: > On Tue, 8 Aug 2006 at 11:51am, mario wrote > > >> That said, your tapelist shows 4350 MB, why making chuncks of 4500MB? > >> You may well be facing the same problem again... > > > > I thought amanda can split such big backup archives up in serveral > > parts. I doubt that someone will backup up a 200GB System onto one > > single tape. > > You're looking for the tape spanning feature, which is explained in the > docs. Which chapter is that? I could not find it with: lynx -dump http://www.amanda.org/docs/index.html | grep -i spann Cheers, Mario
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
On Tue, 8 Aug 2006 at 11:51am, mario wrote That said, your tapelist shows 4350 MB, why making chuncks of 4500MB? You may well be facing the same problem again... I thought amanda can split such big backup archives up in serveral parts. I doubt that someone will backup up a 200GB System onto one single tape. You're looking for the tape spanning feature, which is explained in the docs. There's also been a lot of discussion recently regarding backups to DVDs -- look through the list archives. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
Hello Oliver On Tue, 2006-08-08 at 09:19 +0700, Olivier Nicole wrote: > Hi, > > > How can i tell amanda to split it up in 4500MB slices and write them one > > by one to DVD-RAM? > > Make them several DLEs. That means you must use GNU tar, not dump and > you must identify sub-hierarchies, from that too big disk, that will > match your 4.5 GB limit. Time to play with exclude file list. So you are saying i should loock for ~4GB directories tar them instead to dump them? > > That said, your tapelist shows 4350 MB, why making chuncks of 4500MB? > You may well be facing the same problem again... I thought amanda can split such big backup archives up in serveral parts. I doubt that someone will backup up a 200GB System onto one single tape. A Backup onto DVD would then never be possile??? Thanks, Mario
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
Hi, > How can i tell amanda to split it up in 4500MB slices and write them one > by one to DVD-RAM? Make them several DLEs. That means you must use GNU tar, not dump and you must identify sub-hierarchies, from that too big disk, that will match your 4.5 GB limit. Time to play with exclude file list. That said, your tapelist shows 4350 MB, why making chuncks of 4500MB? You may well be facing the same problem again... Bests, olivier
dump larger than tape, 30864683 KB, but cannot incremental dump new disk
Hello List,
when i try to backup to DVD-RAM i get this error:
FAILURE AND STRANGE DUMP SUMMARY:
server md1 lev 0 FAILED [dump larger than tape, 30864683 KB, but cannot
incremental dump new disk]
How can i tell amanda to split it up in 4500MB slices and write them one
by one to DVD-RAM?
Here are the instresting config settings:
-
dumpuser "root" # the user to run dumps under
inparallel 2# maximum dumpers that will run in parallel
netusage 1024 # maximum net bandwidth for Amanda, in KB per
sec
dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 8 tapes # the number of tapes in rotation
bumpsize 20 MB # minimum savings (threshold) to bump level 1 ->
2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
runtapes 1 # explained in WHATS.NEW
tapedev "file:/media/dvdram"# Linux @ tuck, important: norewinding
tapetype DVD47G # what kind of tape it is (see tapetypes below)
labelstr "^daily-[0-9][0-9]*$" # label constraint regex: all tapes must
match
diskdir "/backup/tmp" # where the holding disk is
disksize 5000 MB# how much space can we use on it
infofile "/var/lib/amanda/DailySet1/curinfo"# database filename
logfile "/var/log/amanda/DailySet1/log"# log filename
indexdir "/var/lib/amanda/DailySet1/index"
holdingdisk hd1 {
comment "main holding disk"
directory "/backup/tmp/" # where the holding disk is
use 5000 Mb
}
define tapetype DVD47G {
length 4350 MB
filemark 4KB
}
Any ideas?
Thanks, Mario
Re: A few questions including "dump larger than tape"
Jobst Schmalenbach wrote:
FAILURE AND STRANGE DUMP SUMMARY:
lalalalala /samba lev 1 FAILED [dump larger than tape, 10101550 KB,
skipping incremental]
It is true that 10101550 KB is bigger than the tape size, this is a 4/8GB
Sony SDT-5000 which I have given the following setup:
# MMS TAPE 0 @ ADMINSERVER
define tapetype SONY_SDT-5000 {
comment "Internal SONY SDT-5000"
length 6000 mbytes
filemark 100 kbytes
speed 500 kps
}
When you tell amanda the tape is 6 Gbyte, and the result of the estimate
is 10Gb, then amanda will not even try to run it.
Even if, with hardware compression, it would turn out afterwards that it
would have fit.
Or do you believe she should try the dump anyway?
See also:
http://marc.theaimsgroup.com/?w=2&r=1&s=%22accepts+53gb+DLE%22&q=t
If you really believe it will fit, increase the length parameter.
maxdumpsize -1
What are you trying to accomplish with setting maxdumpsize to -1 ?
amrecover_changer "/dev/null"
Strange, confusing name for a changer. Better use a mnemonic
like (surprise) "changer". Then issuing the command in amrecover
"settape changer", will use the changer.
lalalalala /samba standard
You can also split it up into smaller pieces. See:
http://www.amanda.org/docs/topten.html#id2556677
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
A few questions including "dump larger than tape"
Hi.
I have been using Amanda for years in a variety of places.
In the case below I am looking after a small school, so the budget is
minimal and I am using a lot of second hand stuff, in this case
4/8BG Sony's, HP's and so on.
The amanda server backs up itself plus that bastion host.
I use two tape drives in the server, one for the OS related stuff
and one for the user data including the samba stuff.
I have never come up with this problem:
FAILURE AND STRANGE DUMP SUMMARY:
lalalalala /samba lev 1 FAILED [dump larger than tape, 10101550 KB,
skipping incremental]
It is true that 10101550 KB is bigger than the tape size, this is a 4/8GB
Sony SDT-5000 which I have given the following setup:
# MMS TAPE 0 @ ADMINSERVER
define tapetype SONY_SDT-5000 {
comment "Internal SONY SDT-5000"
length 6000 mbytes
filemark 100 kbytes
speed 500 kps
}
I turned the hardware compression on for the tape drives via the jumper setting
on the drive
and I do not use softwware compression.
I know I should not use hardware compression cause amanda likes to "know".
However, since I have a small tape drive only, I decided to use a fairly
generous amount in the compression ratio ( I only told it that it has 6GB)
and it is less CPU intesive to use HW compression.
amtapetype in both drives tells me that HW compression IS enabled.
Executing "mt status" yields:
[EMAIL PROTECTED] /home/amanda/etc/DailySet1] #>mt -f /dev/amandatape1
status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
[EMAIL PROTECTED] /home/amanda/etc/DailySet1] #>mt -f /dev/amandatape2
status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
So what am I not seeing here?
jobst
APPENDICES:
amanda.conf (this is for one, the other one looks the same, except it refers to
the
other disklist!
org "DailySet1"
mailto "[EMAIL PROTECTED]"
dumpuser "amanda"
inparallel 4
dumporder "sssS"
netusage 600 Kbps
dumpcycle 9 days
runspercycle 9 days
tapecycle 10 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 300
dtimeout 1800
ctimeout 30
tapebufs 20
runtapes 1
tapedev "/dev/amandatape1"
maxdumpsize -1
tapetype SONY_SDT-5000
labelstr "^Media_S1_[0-9][0-9]*$"
amrecover_do_fsf yes
amrecover_check_label yes
amrecover_changer "/dev/null"
holdingdisk hd1 {
comment "Amanda Holding Disk"
directory "/home/amanda/holdingdisk/DailySet1"
use -4 Gb
chunksize 1 Gb
}
reserve 30
autoflush no
infofile "/home/amanda/curinfo/DailySet1"
logdir "/home/amanda/logs/DailySet1"
indexdir "/home/amanda/index/DailySet1"
tapelist "/home/amanda/tapelist/DailySet1"
# MMS TAPE 0 @ ADMINSERVER
define tapetype SONY_SDT-5000 {
comment "Internal SONY SDT-5000"
length 6000 mbytes
filemark 100 kbytes
speed 500 kps
}
define dumptype global {
comment "Global definitions"
index yes
record yes
compress none
program "GNUTAR"
}
define dumptype root-tar {
global
comment "root partitions dumped with tar"
exclude list "/home/amanda/etc/DailySet1/root_exclude.gtar"
}
define dumptype home {
global
comment "home partition dumped with tar"
exclude list "/home/amanda/etc/DailySet1/home_exclude.gtar"
}
define dumptype standard {
global
comment "Standard Partition (no exclusion list)"
}
define interface local {
comment "a local disk"
use 1000 kbps
}
define interface eth0 {
comment "100 Mbps ethernet"
use 1000 kbps
}
define interface eth1 {
comment "100 Mbps ethernet"
use 1000 kbps
}
disklists 1
lalalalala / root-tar
lalalalala /boot standard
lalalalala /usrstandard
lslslslslsls / root-tar
lslslslslsls /boot standard
disklists 2
lalalalala
Re: dump larger than tape
On Wed, 31 Aug 2005, Matt Hyclak wrote:
> On Wed, Aug 31, 2005 at 10:04:01AM +0200, Geert Uytterhoeven enlightened us:
> > I just got this in my daily report from Amanda (2.4.5-1, Debian
> > etch/testing):
> >
> > | FAILURE AND STRANGE DUMP SUMMARY:
> > |
> > | [...]
> > |
> > | lev 5 FAILED [dump larger than tape, -1 KB, skipping
> > incremental]
> > |
> > | [...]
> > |
> > | DUMP SUMMARY:
> > |
> > | [...]
> > |
> > | 5 FAILED
> >
> > |
> > | [...]
> >
> > The funny thing is that this DLE is only about 5 GiB large (according to
> > du), while the tapetype length is 2 mbytes.
> >
> > Anyone ever seen this before?
> >
>
> Yes. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154882
>
> Without more details we can't tell if that's it, though :-)
It's not that one, since I don't have a 64-bit system.
However, after sending the email I realized the probable cause of the problem:
I started using server side estimates a few weeks ago, so the estimate can
easily be larger than the actual data. And then it's larger than the tape size,
Amanda will just refuse to back it up, right?
Anyway, it happened again last night. I just disabled server side estimates,
and will see what happens this night.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: dump larger than tape
On Wed, Aug 31, 2005 at 10:04:01AM +0200, Geert Uytterhoeven enlightened us: > I just got this in my daily report from Amanda (2.4.5-1, Debian etch/testing): > > | FAILURE AND STRANGE DUMP SUMMARY: > | > | [...] > | > | lev 5 FAILED [dump larger than tape, -1 KB, skipping > incremental] > | > | [...] > | > | DUMP SUMMARY: > | > | [...] > | > | 5 FAILED > > | > | [...] > > The funny thing is that this DLE is only about 5 GiB large (according to > du), while the tapetype length is 2 mbytes. > > Anyone ever seen this before? > Yes. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154882 Without more details we can't tell if that's it, though :-) Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpAuegHuOvSE.pgp Description: PGP signature
dump larger than tape
Hi,
I just got this in my daily report from Amanda (2.4.5-1, Debian etch/testing):
| FAILURE AND STRANGE DUMP SUMMARY:
|
| [...]
|
| lev 5 FAILED [dump larger than tape, -1 KB, skipping
incremental]
|
| [...]
|
| DUMP SUMMARY:
|
| [...]
|
| 5 FAILED
|
| [...]
The funny thing is that this DLE is only about 5 GiB large (according to
du), while the tapetype length is 2 mbytes.
Anyone ever seen this before?
Thx!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hello, Chuck, on 17.06.2005, 15:36 you wrote to amanda-users@amanda.org: > Hi I am still getting - dump larger than tape, 2862305 KB, but cannot > incremental dump new disk but it's only less than 3gb. Please stop starting threads over and over for the same simple topic. Paste your amanda.conf in a reply to this mail (no attachment) and let us debug your understanding of tapetype-definitions. Best regards, Stefan G. Weichinger. mailto://[EMAIL PROTECTED]
still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi I am still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk but it's only less than 3gb. Here's my less /var/mail/root ANALYZING ESTIMATES... pondering server.domain.co.uk:/... next_level0 -12951 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 2862305 total size 2862734 total_lev0 2862305 balanced-lev0size 2862305 INITIAL SCHEDULE (size 2862734): server.domain.co.uk / pri 12951 lev 0 size 2862305 DELAYING DUMPS IF NEEDED, total_size 2862734, tape length 1976320 mark 111 planner: FAILED server.domain.co.uk / 20050616 0 [dump larger than tape, 2862305 KB, but cannot incremental dump new disk] delay: Total size now 286. planner: cannot fit anything on tape, bailing out planner: time 3.118: cannot fit anything on tape, bailing out Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote: Hi Thanks for looking. # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. ... And on line 79: tapetype HP-DAT # what kind of tape it is (see tapetypes below) That should be: tapetype tape-DDS-4 ... # tapetypes # Define the type of tape you use here, and use it in "tapetype" # above. Some typical types of tapes are included here. The tapetype # tells amanda how many MB will fit on the tape, how big the filemarks # are, and how fast the tape device is. Read the text above again, until you understand what you did wrong. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi When I do Got this message when I treid that - "/etc/amanda/DailySet1/amanda.conf", line 79: tapetype HP-DAT not defined. So how do I tell amanda to let go of this tapetype and use another or let me create a new definition. Cheers On Fri, 2005-06-17 at 08:07 -0400, Matt Hyclak wrote: > On Fri, Jun 17, 2005 at 12:28:51PM +0100, Chuck Amadi Systems Administrator > enlightened us: > > When I tried to comment this out > > > > Got this msg - "/etc/amanda/DailySet1/amanda.conf", line 79: tapetype > > HP-DAT not defined. > > How do it start amanda So is uses another tapetype parameter which I > > have added to amanda.conf > > > > You've added a "define tapetype FOO" section. Now you need to go back > towards the top of the amanda.conf file and find the "tapetype HP-DAT" line > and change it to "tapetype YOURNEWDEFINITION". > > Matt > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
On Fri, Jun 17, 2005 at 12:28:51PM +0100, Chuck Amadi Systems Administrator enlightened us: > When I tried to comment this out > > Got this msg - "/etc/amanda/DailySet1/amanda.conf", line 79: tapetype > HP-DAT not defined. > How do it start amanda So is uses another tapetype parameter which I > have added to amanda.conf > You've added a "define tapetype FOO" section. Now you need to go back towards the top of the amanda.conf file and find the "tapetype HP-DAT" line and change it to "tapetype YOURNEWDEFINITION". Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgp4cnDXERHZD.pgp Description: PGP signature
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote: I edit the amanda.conf and added the correct defintions from running amtapetype But when I rerun amdump or amflush it still using the previous incorrect tapetype that has smaller tape size than the real required 20GB tape size. Then post amanda.conf -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi again
The reason to reset as I only left the correct tapetype that was
produced using amtapetype and thus commented out the remainder and I got
this error below
"/etc/amanda/DailySet1/amanda.conf", line 79: tapetype HP-DAT not
defined
So I assume that it's still assuming the previous tapetype and thus I am
unable to backup.
Cheers
On Fri, 2005-06-17 at 13:49 +0200, Paul Bijnens wrote:
> Chuck Amadi Systems Administrator wrote:
> > Hi again
> >
> > When I tried to comment this out
> >
> > Got this msg - "/etc/amanda/DailySet1/amanda.conf", line 79: tapetype
> > HP-DAT not defined.
> > How do it start amanda So is uses another tapetype parameter which I
> > have added to amanda.conf
>
> How about editing that line and putting "tapetype tape-DDS-4"
> so that amanda now looks at the tapetype you just added (at least that
> what I presume you did after reading your other message).
>
> Or do I feel that there is actually a little misunderstanding in
> how the amanda.conf file finds the tapetype?
> The "tapetype " line instructs amanda you are using tape of
> a kind "", from all of the kinds that are defined with
> the "define tapetype xyz {...}" groups.
>
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote:
Hi again
When I tried to comment this out
Got this msg - "/etc/amanda/DailySet1/amanda.conf", line 79: tapetype
HP-DAT not defined.
How do it start amanda So is uses another tapetype parameter which I
have added to amanda.conf
How about editing that line and putting "tapetype tape-DDS-4"
so that amanda now looks at the tapetype you just added (at least that
what I presume you did after reading your other message).
Or do I feel that there is actually a little misunderstanding in
how the amanda.conf file finds the tapetype?
The "tapetype " line instructs amanda you are using tape of
a kind "", from all of the kinds that are defined with
the "define tapetype xyz {...}" groups.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi again When I tried to comment this out Got this msg - "/etc/amanda/DailySet1/amanda.conf", line 79: tapetype HP-DAT not defined. How do it start amanda So is uses another tapetype parameter which I have added to amanda.conf Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi I have run the amtapetype command and used the output and entered
into the amanda.conf as below.
# Produced after running amtapetype command.
define tapetype tape-DDS-4 {
comment "Produced by tapetype 20gb(hardware compression off)"
length 19510 mbytes
filemark 79 kbytes
speed 1740 kps
}
Note the other tapetype parameters are still there which I what I think
is still causing my dumps to fail as is still complaining about dump
larger than tape, 2862305 KB, but cannot incremental dump new disk.
Have I got to comment out the other tapetyps definitions
Here is my ~amdump.6 file output.
>From this blurb - tape length 1976320 mark "111" I note that was in my
previous HP
define tapetype HP-DAT {
comment "DAT tape drives"
# data provided by Rob Browning <[EMAIL PROTECTED]>
length 1930 mbytes #I have changed this to 2
filemark 111 kbytes
speed 468 kbytes
dumper: dgram_bind: socket bound to 0.0.0.0.990
dumper: pid 28445 executable dumper1 version 2.4.4p2, using port 990
planner: time 3.216: got result for host server.domain.co.uk disk /: 0
-> 5735560K, -1 -> -1K, -1 -> -1K
planner: time 3.216: getting estimates took 3.212 secs
FAILED QUEUE: empty
DONE QUEUE:
0: server.domain.co.uk /
ANALYZING ESTIMATES...
pondering server.domain.co.uk:/... next_level0 -12951 last_level -1 (due
for level 0) (new disk, can't switch to degraded
mode)
curr level 0 size 2867780 total size 2868209 total_lev0 2867780
balanced-lev0size 2867780
INITIAL SCHEDULE (size 2868209):
server.domain.co.uk / pri 12951 lev 0 size 2867780
DELAYING DUMPS IF NEEDED, total_size 2868209, tape length 1976320 mark
111
planner: FAILED server.domain.co.uk / 20050616 0 [dump larger than tape,
2867780 KB, but cannot incremental dump new disk] delay: Total size now
286.
planner: cannot fit anything on tape, bailing out
planner: time 3.217: cannot fit anything on tape, bailing out
planner: time 3.217: pid 28441 finish time Thu Jun 16 13:12:52 2005
driver: adding holding disk 0 dir /dumps/amanda size 20971520
Thus have I got to reset anything as Amanda is still thinking of my
previous tapetype.
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830
Re: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk]
Chuck Amadi Systems Administrator wrote: #disklist file #server.domain.co.uk / comp-root-tar #Thought I was using tar. and I get the above error. Whats the best to tackle this still using DSS-4 150mm DAT tapes. and how to cannot incremental dump new disk as above error. Thus can I change from dump to tar I think you already are using tar, if you haven't modified the comp-root-tar dumptype yourself. Amanda still refers to the process of backing up and resulting image as 'dump', she won't say 'tar larger than tape' when you're using tar :-) --- ... Coffee -- n., a person who is coughed upon.
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote:
I got the culprit
define tapetype HP-DAT {
comment "DAT tape drives"
# data provided by Rob Browning <[EMAIL PROTECTED]>
length 1930 mbytes
filemark 111 kbytes
speed 468 kbytes
I will edit this bugger.
Actually it is more or less correct: an HP-DAT is a DDS-1,
in the thime when there was no DDS-2, DDS-3 or DDS-4.
You better add you own define for a DDS-4
and then set tapetype to that new type.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Re: R: dump larger than tape, 2867765 KB, but cannot incremental dump newdisk
On Thursday 16 June 2005 08:28, Chuck Amadi Systems Administrator wrote: >Hi just posted it Where? It didn't make it to here so we can verify what you have. >When I first configured I did rub the command that took for ever and > a day. > >But I did have a 20gb tape in the drive. Two things Chuck: 1) did you transfer the results into a new tapetype verse in your amanda.conf? 2) Is the '?' key broken on your keyboard? We are infering from the words that you are asking a question, but it would be nicer if it was properly marked. >Cheers > >Is there a way to reset it as I have edited the > >On Thu, 2005-06-16 at 14:20 +0200, Montagni, Giovanni wrote: >> Have you ever run amtapetype command? it seems amanda doesn't >> recognize entire tape lenght... >> >> could paste us your tape definition? >> >> another stupid thing, is the tape rewinded? >> >> Giovanni >> >> -Messaggio originale- >> Da: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] conto di Chuck Amadi >> Systems Administrator >> Inviato: giovedì 16 giugno 2005 14.03 >> A: Amanda List >> Oggetto: dump larger than tape, 2867765 KB, but cannot incremental >> dump newdisk >> >> >> >> Hi I have tried backing up "/" using the disklist >> with a 20GB DDS-4 150MM DAT tape and I get this error below. >> The size is only 3GB >> >> Is there a level I need to adjust in the amanda.conf file. >> >> sever.domain.co.uk:/ 0 planner: [dump larger than tape, 2867765 >> KB, but cannot incremental dump new disk] >> >> Cheers -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator wrote: DELAYING DUMPS IF NEEDED, total_size 2862734, tape length 1976320 mark Somewhere in your configuration you have a tape length of 1976320 KB == 1930 MB instead of 20gb. Search for 1930 or 1976320 in amanda.conf to see it is defined. Or post the amanda.conf. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: R: dump larger than tape, 2867765 KB, but cannot incremental dump newdisk
Hi just posted it When I first configured I did rub the command that took for ever and a day. But I did have a 20gb tape in the drive. Cheers Is there a way to reset it as I have edited the On Thu, 2005-06-16 at 14:20 +0200, Montagni, Giovanni wrote: > Have you ever run amtapetype command? it seems amanda doesn't recognize > entire tape lenght... > > could paste us your tape definition? > > another stupid thing, is the tape rewinded? > > Giovanni > > -Messaggio originale- > Da: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] conto di Chuck Amadi Systems > Administrator > Inviato: giovedì 16 giugno 2005 14.03 > A: Amanda List > Oggetto: dump larger than tape, 2867765 KB, but cannot incremental dump > newdisk > > > > Hi I have tried backing up "/" using the disklist > with a 20GB DDS-4 150MM DAT tape and I get this error below. > The size is only 3GB > > Is there a level I need to adjust in the amanda.conf file. > > sever.domain.co.uk:/ 0 planner: [dump larger than tape, 2867765 KB, but > cannot incremental dump new disk] > > Cheers > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: dump larger than tape, 2867765 KB, but cannot incremental dump new disk
Chuck Amadi Systems Administrator schrieb: Hi I have tried backing up "/" using the disklist with a 20GB DDS-4 150MM DAT tape and I get this error below. The size is only 3GB Is there a level I need to adjust in the amanda.conf file. Um, perhaps the tapesize parameter? Christoph sever.domain.co.uk:/ 0 planner: [dump larger than tape, 2867765 KB, but cannot incremental dump new disk] Cheers
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi agian Here is my /var/lib/amanda/amdump.1 ANALYZING ESTIMATES... pondering server.domian.co.uk:/... next_level0 -12951 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 2862305 total size 2862734 total_lev0 2862305 balanced-lev0size 2862305 INITIAL SCHEDULE (size 2862734): server.domain.co.uk / pri 12951 lev 0 size 2862305 DELAYING DUMPS IF NEEDED, total_size 2862734, tape length 1976320 mark 111 planner: FAILED server.smtl.co.uk / 20050616 0 [dump larger than tape, 2862305 KB, but cannot incremental dump new disk] delay: Total size now 286. Any Ideas as I am using a 20GB dat tape. -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
dump larger than tape, 2867765 KB, but cannot incremental dump new disk
Hi I have tried backing up "/" using the disklist with a 20GB DDS-4 150MM DAT tape and I get this error below. The size is only 3GB Is there a level I need to adjust in the amanda.conf file. sever.domain.co.uk:/ 0 planner: [dump larger than tape, 2867765 KB, but cannot incremental dump new disk] Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk]
Chuck Amadi Systems Administrator wrote: server.domain.co.uk:/ 0 planner: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk] [..] Whats the best to tackle this still using DSS-4 150mm DAT tapes. and how to cannot incremental dump new disk as above error. I think you have a wrong value for tapecapacity in amanda.conf file. (or maybe still using some testvalues from the filedriver vtapes?) 2866960 KB is less than 3 Gbyte, and that even fits on a DDS-2 120mm tape. Or did I screw up the units again, ;-) Geert ? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk]
Hi Just read the following about amanda? "Amanda can not back up filesystems that are larger than the tape will fit" Amanda can not back up filesystems that are larger than the tape will fit. I. e. Amanda can not span tapes. It is unclear whether this is a bug or a feature. :-) Allowing spanning would make it difficult to perform backup recovery with standard UNIX tools, i. e. without using Amanda. One workaround is to make sure that all file systems are smaller than the tape capacity. Another is to ask Amanda to back up individual large directories as seperate Disk List Entries (DLEs). This can AFAIK only be done using tar, not using dump. One tape per day, 5 (week)days per week. We were doing all level zeros, but one of the filesystems has grown too big to do this, so now we're doing incrementals as well, with a level zero every other day for each filesystem: Thus time to look at the exclude list. Cheers On Wed, 2005-06-15 at 16:26 +0100, Chuck Amadi Systems Administrator wrote: > Hi all > > server.domain.co.uk:/ 0 planner: [dump larger than tape, 2866960 KB, but > cannot incremental dump new disk] > > I had changed the disklist from "/etc" to "/" and run amdump > > #disklist file > #server.domain.co.uk / comp-root-tar #Thought I was using tar. > > and I get the above error. > > Whats the best to tackle this still using DSS-4 150mm DAT tapes. > and how to cannot incremental dump new disk as above error. > > Thus can I change from dump to tar > > Chuck > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
[dump larger than tape, 2866960 KB, but cannot incremental dump new disk]
Hi all server.domain.co.uk:/ 0 planner: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk] I had changed the disklist from "/etc" to "/" and run amdump #disklist file #server.domain.co.uk / comp-root-tar #Thought I was using tar. and I get the above error. Whats the best to tackle this still using DSS-4 150mm DAT tapes. and how to cannot incremental dump new disk as above error. Thus can I change from dump to tar Chuck -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: Error: dump larger than tape
On Tuesday 19 April 2005 12:24, Thomas Grieder wrote: >Brian Cuttler wrote: >> The problem is that amanda does not (currently) allow a DLE >> (DiskList Entry) to span tapes. >> >> The fully functional method is to configure amanda to use TAR >> (only specific versions work properly) rather than the native >> DUMP utility to dump the DLE. >> >> On Tue, Apr 19, 2005 at 08:05:27PM +0400, Thomas Grieder wrote: > >Wow, that was fast! > >You mean the program part in dumptypes? > >Ther I have GNUTAR > >Thomas First, make sure that the PATH known by the amanda user contains the tar. Second, make sure the tar is either 1.13-19, 1.13-25, or 1.15-1. These are known to work correctly with amanda. Third, tar works in a relative path manner when recursing through directory trees. This means that one can give it a starting path that is not the root directory of the filesystem. It is by this mechanism that trees too large for a single tape can be broken down into tape sized pieces. It does make for a lot of entries in the disklist file, but thats not a consideration with amanda that any of us have become aware of, and amanda has been and is being used by some very large entities. > >P.S. Sorry for PM -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Error: dump larger than tape
Thomas,
> Ok. So I have to invest some time to divide it into usefull pieces :-/
> If I can solve it this way it will be ok with me.
Glad to be of help (I've gotten my share and more from this list).
Brian
On Tue, Apr 19, 2005 at 08:39:55PM +0400, Thomas Grieder wrote:
> Brian Cuttler wrote:
> > Thomas,
> >
> > one of my systems has the following (excepted) disklist
^
excerpted
> >
> > samar / comp-root
> > samar /usr1 comp-user
> > samar /usr5/amanda {
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
Re: Error: dump larger than tape
Frank Smith wrote: --On Tuesday, April 19, 2005 20:05:27 +0400 Thomas Grieder <[EMAIL PROTECTED]> wrote: Is it possible to backup large disk? I ask because I want to backup a disk with 300 GB to DLT1 or LTO1. The DLT1 is a backup library with 7 slots which works fine. The LTO1 is a sigle drive. I tried it as single drive an as chg-manual. I configured a holding disk with 12GB (I don't have more). Amdump always sends me this error: FAILURE AND STRANGE DUMP SUMMARY: sun.moonsm /export lev 0 FAILED [dump larger than tape, 160459105 KB, but cannot incremental dump new disk] Where is the problem? Amanda can't back up a DLE larger than a tape (unless you use the tape- spanning patches currently under development). Se the 'size-question in the docs: <http://www.amanda.org/docs/topten.html#id2520555> Thank you. I'm sure this will solve my poblem! > > Frank Thomas
Re: Error: dump larger than tape
Brian Cuttler wrote:
Thomas,
one of my systems has the following (excepted) disklist
samar / comp-root
samar /usr1 comp-user
samar /usr5/amanda {
user-tar
}
samar /usr5/liw {
user-tar
}
samar /usr5/hxgao {
user-tar
}
Ok. So I have to invest some time to divide it into usefull pieces :-/
If I can solve it this way it will be ok with me.
Thanks a lot!
Thomas
Re: Error: dump larger than tape
--On Tuesday, April 19, 2005 20:05:27 +0400 Thomas Grieder <[EMAIL PROTECTED]> wrote: > Is it possible to backup large disk? > > I ask because I want to backup a disk with 300 GB to DLT1 or LTO1. > > The DLT1 is a backup library with 7 slots which works fine. > The LTO1 is a sigle drive. I tried it as single drive an as > chg-manual. > > I configured a holding disk with 12GB (I don't have more). > > Amdump always sends me this error: > > FAILURE AND STRANGE DUMP SUMMARY: > sun.moonsm /export lev 0 FAILED [dump larger than tape, 160459105 > KB, but cannot incremental dump new disk] > > Where is the problem? Amanda can't back up a DLE larger than a tape (unless you use the tape- spanning patches currently under development). Se the 'size-question in the docs: <http://www.amanda.org/docs/topten.html#id2520555> Frank > > > Thanks > Thomas -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Error: dump larger than tape
Brian Cuttler wrote: The problem is that amanda does not (currently) allow a DLE (DiskList Entry) to span tapes. The fully functional method is to configure amanda to use TAR (only specific versions work properly) rather than the native DUMP utility to dump the DLE. On Tue, Apr 19, 2005 at 08:05:27PM +0400, Thomas Grieder wrote: Wow, that was fast! You mean the program part in dumptypes? Ther I have GNUTAR Thomas P.S. Sorry for PM
Re: Error: dump larger than tape
The problem is that amanda does not (currently) allow a DLE (DiskList Entry) to span tapes. The fully functional method is to configure amanda to use TAR (only specific versions work properly) rather than the native DUMP utility to dump the DLE. On Tue, Apr 19, 2005 at 08:05:27PM +0400, Thomas Grieder wrote: > Is it possible to backup large disk? > > I ask because I want to backup a disk with 300 GB to DLT1 or LTO1. > > The DLT1 is a backup library with 7 slots which works fine. > The LTO1 is a sigle drive. I tried it as single drive an as > chg-manual. > > I configured a holding disk with 12GB (I don't have more). > > Amdump always sends me this error: > > FAILURE AND STRANGE DUMP SUMMARY: > sun.moonsm /export lev 0 FAILED [dump larger than tape, 160459105 > KB, but cannot incremental dump new disk] > > Where is the problem? > > > Thanks > Thomas --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Error: dump larger than tape
Is it possible to backup large disk? I ask because I want to backup a disk with 300 GB to DLT1 or LTO1. The DLT1 is a backup library with 7 slots which works fine. The LTO1 is a sigle drive. I tried it as single drive an as chg-manual. I configured a holding disk with 12GB (I don't have more). Amdump always sends me this error: FAILURE AND STRANGE DUMP SUMMARY: sun.moonsm /export lev 0 FAILED [dump larger than tape, 160459105 KB, but cannot incremental dump new disk] Where is the problem? Thanks Thomas
Re: Dump larger than tape error
On Monday 28 February 2005 18:00, Gene Heskett wrote: [...] >89% full now. But thats doable in the interests of advancing amanda >if I can help. I've reduced the size of the vtape in my amanda.conf >so that there should be a potential overrun of a gig or thereabouts >for a normal routine run, and increased runtapes to 2. >From the mail report, and from looking at the pair of tapes used, I would come to the conclusion that the file that hit EOT for the first of the two tapes used, although only 1.5GB of it was written when this occured, it apparently started from byte one when it wrote that file in its entire 2.3GB entirety on the second tape. John Stange, is there a keyword to enable this that needs to be inserted into the amanda.conf? Humm, on grepping the patch, it appears there is a new keyword to be defined in the dumptype, and duh, I didn't do that. Sigh... -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Dump larger than tape error
On Monday 28 February 2005 15:43, Fairbank, Bob wrote: >Hi. >I am definetly going to need to back up filesystems that are larger > than the >capacity of a single tape (SDLT). Apparently, amanda has a > limitation with this. >True? Any idea when it will be able to do this? >Thanks. > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie >Sent: Monday, February 28, 2005 11:58 AM >To: amanda-users@amanda.org >Subject: Re: Dump larger than tape error > >On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: >> Hi, all! >> >> /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: > >Cannot > >> write: No space left on device >> >> | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) >> >> ? gtar: Error exit delayed from previous errors >> sendbackup: error [/usr/local/bin/tar returned 2] >> \ > >_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ >_+_+ > >> _+_+_+_+_+_+ >> >> Now, the disks I'm using to do my backups is not full. Nowhere >> near full; I've got 112Gb free on it. I doubt the filesystem on >> the target system is THAT full... I will doublecheck though. Any >> immediate thoughts? > >Note, it reported the filesystem containing >/usr/local/var/amanda/gnutar-lists >was full, not your vtape filesystem. Duh, I was using the wrong patch, the correct one does indeed apply. But it gives me a strange advisory I've not seen before just as the compile starts when using my script to configure and build it: --- Making all in config make[1]: Entering directory `/home/amanda/amanda-2.4.5b1-20050214/config' cd .. && /bin/sh /home/amanda/amanda-2.4.5b1-20050214/config/missing --run autoheader rm -f stamp-h1 touch config.h.in --- And then it continues with the build without further complaints. And an amcheck returns no errors. Further results as they become available. Stay tuned as they say, I might need a transfusion here, playing with all this bleeding edge stuff. :-) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Dump larger than tape error
On Monday 28 February 2005 15:43, Fairbank, Bob wrote: >Hi. >I am definetly going to need to back up filesystems that are larger > than the >capacity of a single tape (SDLT). Apparently, amanda has a > limitation with this. >True? Any idea when it will be able to do this? >Thanks. > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie >Sent: Monday, February 28, 2005 11:58 AM >To: amanda-users@amanda.org >Subject: Re: Dump larger than tape error > >On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: >> Hi, all! >> >> /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: > >Cannot > >> write: No space left on device >> >> | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) >> >> ? gtar: Error exit delayed from previous errors >> sendbackup: error [/usr/local/bin/tar returned 2] >> \ > >_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ >_+_+ > >> _+_+_+_+_+_+ >> >> Now, the disks I'm using to do my backups is not full. Nowhere >> near full; I've got 112Gb free on it. I doubt the filesystem on >> the target system is THAT full... I will doublecheck though. Any >> immediate thoughts? > >Note, it reported the filesystem containing >/usr/local/var/amanda/gnutar-lists >was full, not your vtape filesystem. Pursuant to my last message, the patch did not apply cleanly. I'll nuke the dir, and do it again. And that did not help. I'm still getting errors where one or more hunks fail, on several files. John Stang, if you are copying the mail, there they are: 3 out of 10 hunks FAILED -- saving rejects to file restore-src/amrestore.c.rej 1 out of 1 hunk FAILED -- saving rejects to file server-src/amoverview.pl.in.rej 1 out of 22 hunks FAILED -- saving rejects to file server-src/driver.c.rej 3 out of 5 hunks FAILED -- saving rejects to file server-src/planner.c.rej 1 out of 21 hunks FAILED -- saving rejects to file server-src/reporter.c.rej This is patch "span_split_2.4.5-current.patch", and is being applied to amanda-2.4.5b1-20050214 as freshly unpacked from the tar.gz. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Dump larger than tape error
On Monday 28 February 2005 15:43, Fairbank, Bob wrote: >Hi. >I am definetly going to need to back up filesystems that are larger > than the >capacity of a single tape (SDLT). Apparently, amanda has a > limitation with this. >True? Any idea when it will be able to do this? >Thanks. > The accepted cure for that is to use tar, and break the disklist up into pieces much smaller than a tape. Amanda, by design, does not do a full level 0 backup of all disklist entries at the same time, instead, it tries to scatter them out among the backup runs during the dumpcycle so that it uses about the same amount of tape per run, but a dumpcycle can actually contain 5 to 7 tapes (the way most do it) with each tape filled to 95% or more of its capacity. That said, there is a patch for amanda that will allow it to span one individual backup over more than 1 tape. I'm about to apply it here, and play with it over the next weeks to see if I can break it. It lives here: <http://www.cs.umd.edu/~building/span_split_V7.0-2.4.5b1-20050214.patch.gz> and is against the last 2.4.5b1-20050214.tar.gz version of amanda, available from a link near the bottom of the amanda.org web page. >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie >Sent: Monday, February 28, 2005 11:58 AM >To: amanda-users@amanda.org >Subject: Re: Dump larger than tape error > >On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: >> Hi, all! >> >> /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: > >Cannot > >> write: No space left on device >> >> | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) >> >> ? gtar: Error exit delayed from previous errors >> sendbackup: error [/usr/local/bin/tar returned 2] >> \ > >_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ >_+_+ > >> _+_+_+_+_+_+ >> >> Now, the disks I'm using to do my backups is not full. Nowhere >> near full; I've got 112Gb free on it. I doubt the filesystem on >> the target system is THAT full... I will doublecheck though. Any >> immediate thoughts? > >Note, it reported the filesystem containing >/usr/local/var/amanda/gnutar-lists >was full, not your vtape filesystem. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Dump larger than tape error
On Mon, Feb 28, 2005 at 01:43:39PM -0700, Fairbank, Bob wrote: > Hi. > I am definetly going to need to back up filesystems that are larger than > the > capacity of a single tape (SDLT). Apparently, amanda has a limitation > with this. > True? Any idea when it will be able to do this? > Thanks. I presume you have already looked at amanda docs describing alternatives and found them wanting? If so, John Stange has been working on tape spanning patches to amanda. Several sites have been using the patches for a while, but it is still considered 'beta' and not part of the current amanda distribution. See this list last week for locations where the patch can be obtained. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Dump larger than tape error
Bob, Amanda is limited to DLE (DiskList Entries) that do not exceed the capacity of a single tape volume. However you are not restricted to "dump" but may use "tar" (specifically certain versions of gnutar) to select specific file types for subtrees residing on the partition. On Mon, Feb 28, 2005 at 01:43:39PM -0700, Fairbank, Bob wrote: > Hi. > I am definetly going to need to back up filesystems that are larger than > the > capacity of a single tape (SDLT). Apparently, amanda has a limitation > with this. > True? Any idea when it will be able to do this? > Thanks. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie > Sent: Monday, February 28, 2005 11:58 AM > To: amanda-users@amanda.org > Subject: Re: Dump larger than tape error > > > On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: > > Hi, all! > > > > /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: > Cannot > > write: No space left on device > > | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) > > ? gtar: Error exit delayed from previous errors > > sendbackup: error [/usr/local/bin/tar returned 2] > > \ > > > > > _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ > > _+_+_+_+_+_+ > > > > Now, the disks I'm using to do my backups is not full. Nowhere near > > full; I've got 112Gb free on it. I doubt the filesystem on the target > > system is THAT full... I will doublecheck though. Any immediate > > thoughts? > > > > Note, it reported the filesystem containing > /usr/local/var/amanda/gnutar-lists > was full, not your vtape filesystem. > > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) > --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
RE: Dump larger than tape error
Hi. I am definetly going to need to back up filesystems that are larger than the capacity of a single tape (SDLT). Apparently, amanda has a limitation with this. True? Any idea when it will be able to do this? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie Sent: Monday, February 28, 2005 11:58 AM To: amanda-users@amanda.org Subject: Re: Dump larger than tape error On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: > Hi, all! > > /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: Cannot > write: No space left on device > | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) > ? gtar: Error exit delayed from previous errors > sendbackup: error [/usr/local/bin/tar returned 2] > \ > > _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ > _+_+_+_+_+_+ > > Now, the disks I'm using to do my backups is not full. Nowhere near > full; I've got 112Gb free on it. I doubt the filesystem on the target > system is THAT full... I will doublecheck though. Any immediate > thoughts? > Note, it reported the filesystem containing /usr/local/var/amanda/gnutar-lists was full, not your vtape filesystem. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Dump larger than tape error
On Monday 28 February 2005 13:35, Byarlay, Wayne A. wrote: >Hi, all! > >I've been running dumps to hard disk using chg-multi & stuff for > about a year now, very good, no complaints. > >But recently, suddenly, one of the computers I back up is failing. >Here's what's in the e-mail: > > >_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ >_+_+ _+_+_+_+_+_+ >These dumps were to tape DailySet109. >The next tape Amanda expects to use is: DailySet110. > >FAILURE AND STRANGE DUMP SUMMARY: > /m1 lev 1 FAILED [dump larger than tape, -1 KB, > skipping incremental] > /export/home lev 1 FAILED [dump larger than tape, -1 > KB, skipping incremental] > /usr/local lev 1 FAILED [dump larger than tape, -1 > KB, skipping incremental] > / lev 1 FAILED [dump larger than tape, -1 KB, > skipping incremental] > > /var lev 0 FAILED [/usr/local/bin/tar returned 2] > /var lev 0 FAILED [dump to tape failed] > >. >. >. > >FAILED AND STRANGE DUMP DETAILS: > >/-- mole.lib.p /services lev 1 STRANGE >sendbackup: start [mole.lib.purdue.edu:/services level 1] >sendbackup: info BACKUP=/bin/tar >sendbackup: info RECOVER_CMD=/bin/tar -f... - >sendbackup: info end >? gtar: ./purl/dist-2.14-linux-intel/WebRoot/logs/access_log: file >changed as we read it > >| Total bytes written: 168099840 (160MB, 7.0MB/s) > >sendbackup: size 164160 >sendbackup: end >\ > > > > >/-- /var lev 0 FAILED [/usr/local/bin/tar returned 2] >sendbackup: start [:/var level 0] >sendbackup: info BACKUP=/usr/local/bin/tar >sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - >sendbackup: info end >? gtar: >/usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: > Cannot write: No space left on device > >| Total bytes written: 3040256000 (2.8GB, 8.9MB/s) > >? gtar: Error exit delayed from previous errors >sendbackup: error [/usr/local/bin/tar returned 2] >\ > >_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ >_+_+ _+_+_+_+_+_+ > >Now, the disks I'm using to do my backups is not full. Nowhere near >full; I've got 112Gb free on it. I doubt the filesystem on the > target system is THAT full... I will doublecheck though. Any > immediate thoughts? > >Wab. You will also get this error when using the FILE: tapetype if the tapesize isn't large enough. is it? -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Dump larger than tape error
--On Monday, February 28, 2005 13:35:15 -0500 "Byarlay, Wayne A." <[EMAIL PROTECTED]> wrote: > Hi, all! > > I've been running dumps to hard disk using chg-multi & stuff for about a > year now, very good, no complaints. > > But recently, suddenly, one of the computers I back up is failing. > Here's what's in the e-mail: > > > _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ > _+_+_+_+_+_+ > These dumps were to tape DailySet109. > The next tape Amanda expects to use is: DailySet110. > > FAILURE AND STRANGE DUMP SUMMARY: >/m1 lev 1 FAILED [dump larger than tape, -1 KB, skipping > incremental] >/export/home lev 1 FAILED [dump larger than tape, -1 KB, > skipping incremental] >/usr/local lev 1 FAILED [dump larger than tape, -1 KB, > skipping incremental] >/ lev 1 FAILED [dump larger than tape, -1 KB, skipping > incremental] > >/var lev 0 FAILED [/usr/local/bin/tar returned 2] >/var lev 0 FAILED [dump to tape failed] > > . > . > . > > FAILED AND STRANGE DUMP DETAILS: > > /-- mole.lib.p /services lev 1 STRANGE > sendbackup: start [mole.lib.purdue.edu:/services level 1] > sendbackup: info BACKUP=/bin/tar > sendbackup: info RECOVER_CMD=/bin/tar -f... - > sendbackup: info end > ? gtar: ./purl/dist-2.14-linux-intel/WebRoot/logs/access_log: file > changed as we read it >| Total bytes written: 168099840 (160MB, 7.0MB/s) > sendbackup: size 164160 > sendbackup: end > \ > > > > > /-- /var lev 0 FAILED [/usr/local/bin/tar returned 2] > sendbackup: start [:/var level 0] > sendbackup: info BACKUP=/usr/local/bin/tar > sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - > sendbackup: info end > ? gtar: > /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: Cannot > write: No space left on device I'll bet this is the problem. Amanda can't write here on this client due to a full disk (The gnutar-lists files enable tar to keep track of what files have changed in order to do incrementals). The 'dump larger than tape' is probably just poor handling of a negative number. Frank >| Total bytes written: 3040256000 (2.8GB, 8.9MB/s) > ? gtar: Error exit delayed from previous errors > sendbackup: error [/usr/local/bin/tar returned 2] > \ > > _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ > _+_+_+_+_+_+ > > Now, the disks I'm using to do my backups is not full. Nowhere near > full; I've got 112Gb free on it. I doubt the filesystem on the target > system is THAT full... I will doublecheck though. Any immediate > thoughts? > > Wab. -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Dump larger than tape error
Hmm, yes, you are right. Which would exist on the client, yes? (Does not exist on my Amanda server.) Strangely, I created another backup set, with only one "tape" in my "changer", and adjusted the amanda.conf file for this new config to backup that machine Full to a separate area; and it's running. So this is less of a problem (Went from "Emergency" to "high") :), but still Weird. The ins & outs of this program could constitute somebody's PhD dissertation. Thanks! Wayne Byarlay, Amanda Noob going on 3 years -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie Sent: Monday, February 28, 2005 1:58 PM To: amanda-users@amanda.org Subject: Re: Dump larger than tape error On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: > Hi, all! > > /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: > Cannot > write: No space left on device > | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) > ? gtar: Error exit delayed from previous errors > sendbackup: error [/usr/local/bin/tar returned 2] > \ > > _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ > _+ > _+_+_+_+_+_+ > > Now, the disks I'm using to do my backups is not full. Nowhere near > full; I've got 112Gb free on it. I doubt the filesystem on the target > system is THAT full... I will doublecheck though. Any immediate > thoughts? > Note, it reported the filesystem containing /usr/local/var/amanda/gnutar-lists was full, not your vtape filesystem. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Dump larger than tape error
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Byarlay, Wayne A. Sent: Monday, February 28, 2005 1:35 PM To: amanda-users@amanda.org Subject: Dump larger than tape error Hi, all! I've been running dumps to hard disk using chg-multi & stuff for about a year now, very good, no complaints. But recently, suddenly, one of the computers I back up is failing. Here's what's in the e-mail: _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ _+_+_+_+_+_+ These dumps were to tape DailySet109. The next tape Amanda expects to use is: DailySet110. FAILURE AND STRANGE DUMP SUMMARY: /m1 lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] /export/home lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] /usr/local lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] / lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] /var lev 0 FAILED [/usr/local/bin/tar returned 2] /var lev 0 FAILED [dump to tape failed] . . . FAILED AND STRANGE DUMP DETAILS: /-- mole.lib.p /services lev 1 STRANGE sendbackup: start [mole.lib.purdue.edu:/services level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end ? gtar: ./purl/dist-2.14-linux-intel/WebRoot/logs/access_log: file changed as we read it | Total bytes written: 168099840 (160MB, 7.0MB/s) sendbackup: size 164160 sendbackup: end \ /-- /var lev 0 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [:/var level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end ? gtar: /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: Cannot write: No space left on device | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] \ _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ _+_+_+_+_+_+ Now, the disks I'm using to do my backups is not full. Nowhere near full; I've got 112Gb free on it. I doubt the filesystem on the target system is THAT full... I will doublecheck though. Any immediate thoughts? Wab.
Re: Dump larger than tape error
On Mon, Feb 28, 2005 at 01:35:15PM -0500, Byarlay, Wayne A. wrote: > Hi, all! > > /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: Cannot > write: No space left on device > | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) > ? gtar: Error exit delayed from previous errors > sendbackup: error [/usr/local/bin/tar returned 2] > \ > > _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ > _+_+_+_+_+_+ > > Now, the disks I'm using to do my backups is not full. Nowhere near > full; I've got 112Gb free on it. I doubt the filesystem on the target > system is THAT full... I will doublecheck though. Any immediate > thoughts? > Note, it reported the filesystem containing /usr/local/var/amanda/gnutar-lists was full, not your vtape filesystem. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Dump larger than tape error
Hi, all! I've been running dumps to hard disk using chg-multi & stuff for about a year now, very good, no complaints. But recently, suddenly, one of the computers I back up is failing. Here's what's in the e-mail: _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ _+_+_+_+_+_+ These dumps were to tape DailySet109. The next tape Amanda expects to use is: DailySet110. FAILURE AND STRANGE DUMP SUMMARY: /m1 lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] /export/home lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] /usr/local lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] / lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental] /var lev 0 FAILED [/usr/local/bin/tar returned 2] /var lev 0 FAILED [dump to tape failed] . . . FAILED AND STRANGE DUMP DETAILS: /-- mole.lib.p /services lev 1 STRANGE sendbackup: start [mole.lib.purdue.edu:/services level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end ? gtar: ./purl/dist-2.14-linux-intel/WebRoot/logs/access_log: file changed as we read it | Total bytes written: 168099840 (160MB, 7.0MB/s) sendbackup: size 164160 sendbackup: end \ /-- /var lev 0 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [:/var level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end ? gtar: /usr/local/var/amanda/gnutar-lists/luke.lib.purdue.edu_var_0.new: Cannot write: No space left on device | Total bytes written: 3040256000 (2.8GB, 8.9MB/s) ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] \ _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ _+_+_+_+_+_+ Now, the disks I'm using to do my backups is not full. Nowhere near full; I've got 112Gb free on it. I doubt the filesystem on the target system is THAT full... I will doublecheck though. Any immediate thoughts? Wab.
Re: dump larger than tape
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, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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, :D::D, 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 * ***
Re: dump larger than tape
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 [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dump larger than tape
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 12k finished (12:22:46)
anubis:/data/dns1 14k finished (12:22:31)
anubis:/data/etc0 10k 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 2 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 4 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
begin:vcard
fn:Iulian Topliceanu
n:Topliceanu;Iulian
org:;Operations
adr;quoted-printable;quoted-printable:;;M=C3=B6rsenbroicher Weg 200;D=C3=BCsseldorf;NRW;D-40470;net mobile AG
email;internet:[EMAIL PROTECTED]
title:Unix & Network Administrator
tel;work:+49 (0) 211 687706 31
tel;home:+49 (0) 203 6001423
tel;cell:+49 (0) 175 89 12 414
url:http://www.net-m.de
version:2.1
end:vcard
Re: dump larger than tape
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 12k finished (12:22:46)
anubis:/data/dns1 14k finished (12:22:31)
anubis:/data/etc0 10k 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 2 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 4 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
dump larger than tape
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 12k finished (12:22:46)
anubis:/data/dns1 14k finished (12:22:31)
anubis:/data/etc0 10k 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 2 mbytes # 20 Gig tapes
filemark 2000 kbytes# I don't know what this means
speed 1536 kbytes # 1.5 Mb/s
}
Gruss,
Iulian Topliceanu
begin:vcard
fn:Iulian Topliceanu
n:Topliceanu;Iulian
org:;Operations
adr;quoted-printable;quoted-printable:;;M=C3=B6rsenbroicher Weg 200;D=C3=BCsseldorf;NRW;D-40470;net mobile AG
email;internet:[EMAIL PROTECTED]
title:Unix & Network Administrator
tel;work:+49 (0) 211 687706 31
tel;home:+49 (0) 203 6001423
tel;cell:+49 (0) 175 89 12 414
url:http://www.net-m.de
version:2.1
end:vcard
Re: "Dump larger than tape" problem
On Wed, Sep 17, 2003 at 10:41:28AM -0400, KEVIN ZEMBOWER wrote:
> I'm struggling to solve a "dump larger than tape" problem, and not making much
> progress. I'm
> asking for suggestions and troubleshooting techniques.
>
> I'm trying to back up the Samba share admin//db/f$. I've broken it up into two
> sections:
> [EMAIL PROTECTED]:~ > amadmin DailySet1 disklist admin //db/f$/
> line 82:
> host admin:
> interface default
> disk //db/f$:
> program "GNUTAR"
> exclude file "./inetsrv/webpub/images/"
> priority 1
> dumpcycle 3
> maxdumps 1
> maxpromoteday 1
> strategy STANDARD
> compress NONE
> auth BSD
> kencrypt NO
> holdingdisk YES
> record YES
> index NO
> skip-incr NO
> skip-full NO
>
> line 83:
> host admin:
> interface default
> disk //db/f$/inetsrv/webpub/images:
> program "GNUTAR"
> priority 1
> dumpcycle 3
> maxdumps 1
> maxpromoteday 1
> strategy STANDARD
> compress NONE
> auth BSD
> kencrypt NO
> holdingdisk YES
> record YES
> index NO
> skip-incr NO
> skip-full NO
>
> [EMAIL PROTECTED]:~ >
< all sorts of good stuff snipped >
>
> It's like amanda is not taking into account the excluded directories when making the
> size estimate,
> and then giving up on the level 0 backup because it seems too big.
>
< more snipping >
I have had similar problems, and what i've found is that the smallest
unit that amanda will back up through samba is a *share*, and specifying
individual directories ("disk //server/share/dir1") is fruitless.
Can someone confirm this? Is this a limitation of Samba, or Amanda?
--
eric a. Farris http://eafarris.al.umces.edu/
Systems Administrator
UMCES Appalachian Laboratory http://www.al.umces.edu/
Re: "Dump larger than tape" problem
Eric, thanks for your response. It does seem to me that amanda is backing up correctly
the
"sub-share" //db/f$/inetsrv/webpub/images, because of these lines in the info output:
Current info for admin //db/f$/inetsrv/webpub/images:
Stats: dump rates (kps), Full: 2661.0, 2785.0, -1.0
Incremental: 230.0, 5.0, 21.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20030915 DailySet12616 6809105 6826070 2565
It just doesn't seem to ignore the exclude file for the "full-share" backup.
-Kevin
>>> "eric a. Farris" <[EMAIL PROTECTED]> 09/17/03 10:59AM >>>
On Wed, Sep 17, 2003 at 10:41:28AM -0400, KEVIN ZEMBOWER wrote:
I have had similar problems, and what i've found is that the smallest
unit that amanda will back up through samba is a *share*, and specifying
individual directories ("disk //server/share/dir1") is fruitless.
Can someone confirm this? Is this a limitation of Samba, or Amanda?
--
eric a. Farris http://eafarris.al.umces.edu/
Systems Administrator
UMCES Appalachian Laboratory http://www.al.umces.edu/
Re: "Dump larger than tape" problem
KEVIN ZEMBOWER wrote: I'm struggling to solve a "dump larger than tape" problem, and not making much progress. I'm asking for suggestions and troubleshooting techniques. That's the correct diagnosis. Long time ago, the estimates where done using smbclient builtin tar, and trowing the result away. This took ages of course, but it would have been able to exclude some files. Now amanda uses the builtin "du" command, very fast, but that command has no way to given an exclude list. Any suggestions on changes or procedures to overcome this problem? I'm getting desperate; it's just been making level 1 backups for a week now. Maybe using the cygwin port of amanda and run amanda client software on the machine itself, instead of using smbclient? I've never tried it, but some people report it works very well (other people report problems getting the thing basically working too :-) ). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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, :D::D, 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 * ***
"Dump larger than tape" problem
I'm struggling to solve a "dump larger than tape" problem, and not making much progress. I'm asking for suggestions and troubleshooting techniques. I'm trying to back up the Samba share admin//db/f$. I've broken it up into two sections: [EMAIL PROTECTED]:~ > amadmin DailySet1 disklist admin //db/f$/ line 82: host admin: interface default disk //db/f$: program "GNUTAR" exclude file "./inetsrv/webpub/images/" priority 1 dumpcycle 3 maxdumps 1 maxpromoteday 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record YES index NO skip-incr NO skip-full NO line 83: host admin: interface default disk //db/f$/inetsrv/webpub/images: program "GNUTAR" priority 1 dumpcycle 3 maxdumps 1 maxpromoteday 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record YES index NO skip-incr NO skip-full NO [EMAIL PROTECTED]:~ > I get this error when backing it up to a DDS-3 tape, which should hold 11.5G, according to a tapetest run: NOTES: planner: admin //db/f$ 20030915 0 [dump larger than tape, 12101907 KB, full dump delayed] But, each of the sections is less than 11G: ( Total size of //db/f$:) [EMAIL PROTECTED]:/etc/amanda/DailySet1 > smbclient //db/f$ -U amanda%CiScO -Tc /dev/null INFO: Debug class all level = 1 (pid 16901 from pid 16901) added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0 Output is /dev/null, assuming dry_runDomain=[DBWG] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] directory \inetsrv\ directory \inetsrv\ftp\ directory \temp\ tar: dumped 35364 files and directories Total bytes written: 12408697856 [EMAIL PROTECTED]:/etc/amanda/DailySet1 > (Size of just /inetsrv/webpub/images directory tree:) [EMAIL PROTECTED]:/etc/amanda/DailySet1 > smbclient //db/f$ -U amanda%CiScO -TcX /dev/null /inetsrv/webpub/images INFO: Debug class all level = 1 (pid 16904 from pid 16904) added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0 Output is /dev/null, assuming dry_runDomain=[DBWG] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] directory \inetsrv\ directory \inetsrv\ftp\ directory \temp\ tar: dumped 1359 files and directories Total bytes written: 5436378112 [EMAIL PROTECTED]:/etc/amanda/DailySet1 > Therefore, 12.4G minus 5.4G is 7G. It's like amanda is not taking into account the excluded directories when making the size estimate, and then giving up on the level 0 backup because it seems too big. Here's the info output, if it's helpful: [EMAIL PROTECTED]:/etc/amanda/DailySet1 > amadmin DailySet1 info admin //db/f$/ Current info for admin //db/f$: Stats: dump rates (kps), Full: 2993.0, 3469.0, 1124.0 Incremental: 4738.0, 4651.0, 4646.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20030827 DailySet11215 8426319 8443840 2821 1 20030915 DailySet12615 4895256 4895330 1033 Current info for admin //db/f$/inetsrv/webpub/images: Stats: dump rates (kps), Full: 2661.0, 2785.0, -1.0 Incremental: 230.0, 5.0, 21.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20030915 DailySet12616 6809105 6826070 2565 [EMAIL PROTECTED]:/etc/amanda/DailySet1 > Any suggestions on changes or procedures to overcome this problem? I'm getting desperate; it's just been making level 1 backups for a week now. Thanks for all your help and suggestions. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
RE: dump larger than tape
Just a wild thought, but Redhat tends to install a firewall by default, this isn't blocking things is it? Cheers Nige -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Konrad Dienst Sent: 07 March 2003 13:43 To: [EMAIL PROTECTED] Subject: Re: dump larger than tape Hi! Amanda server is a FreeBSD 4.7, the problem child is a RedHat (Kernel 2.4.18-3). Backup on FreeBSD and Solaris clients is not a problem. amcheck does not find any problems with the RedHat client, either but amdump doesn't like him. Attached are my xinetd.from the client as well as amanda.conf and disklist from the server (corellia is the RedHat machine). I've set the disk devices, as well as the raw disk devivces to owner group amanda, also the /etc/dumpdates. services also has the appropriate enries. Thanks in advance Konni
Re: dump larger than tape
On Fri, 7 Mar 2003 at 2:43pm, Konrad Dienst wrote > Hi! > Amanda server is a FreeBSD 4.7, the problem child is a RedHat (Kernel > 2.4.18-3). Backup on FreeBSD and Solaris clients is not a problem. > amcheck does not find any problems with the RedHat client, either but > amdump doesn't like him. > > Attached are my xinetd.from the client as well as amanda.conf and > disklist from the server (corellia is the RedHat machine). > > I've set the disk devices, as well as the raw disk devivces to owner > group amanda, also the /etc/dumpdates. services also has the appropriate > enries. What does /tmp/amanda/sendsize*debug on the failing client say? What about amandad*debug? What about 'df'? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: dump larger than tape
Hi!
Amanda server is a FreeBSD 4.7, the problem child is a RedHat (Kernel
2.4.18-3). Backup on FreeBSD and Solaris clients is not a problem.
amcheck does not find any problems with the RedHat client, either but
amdump doesn't like him.
Attached are my xinetd.from the client as well as amanda.conf and
disklist from the server (corellia is the RedHat machine).
I've set the disk devices, as well as the raw disk devivces to owner
group amanda, also the /etc/dumpdates. services also has the appropriate
enries.
Thanks in advance
Konni
#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/
defaults
{
instances = 60
log_type= SYSLOG authpriv
log_on_success = HOST PID
log_on_failure = HOST
cps = 25 30
}
service amanda
{
flags = REUSE NAMEINARGS
socket_type = dgram
protocol= udp
wait= yes
user= amanda
server = /usr/local/libexec/amandad
server_args = amandad
}
includedir /etc/xinetd.d
### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ###
### ###
### This file is not meant to be installed "as is", and in fact, it ###
### WILL NOT WORK! You must go through it and make changes appropriate ###
### to your own situation. See the documentation in this file, in the ###
### "man amanda" man page, in the "docs" directory and at the Amanda###
### web page (www.amanda.org). ###
### ###
### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ###
#
# amanda.conf - sample Amanda configuration file. This started off life as
# the actual config file in use at CS.UMD.EDU.
#
# If your configuration is called, say, "csd", then this file normally goes
# in /usr/local/etc/amanda/csd/amanda.conf.
#
org "test" # your organization name for reports
mailto "amanda" # space separated list of operators at your site
dumpuser "amanda" # the user to run dumps under
inparallel 1# maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
dumporder "sssS"# specify the priority order of each dumper
# s -> smallest size
# S -> biggest size
# t -> smallest time
# T -> biggest time
# b -> smallest bandwitdh
# B -> biggest bandwitdh
# try "BTBTBTBTBTBT" if you are not holding
# disk constrained
netusage 1 Kbps# maximum net bandwidth for Amanda, in KB per sec
dumpcycle 19 days # the number of days in the normal dump cycle
runspercycle 19 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 19 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
### ### ###
# WARNING: don't use `inf' for tapecycle, it's broken!
### ### ###
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 300# number of seconds per filesystem for estimates.
#etimeout -600 # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
# for each client host
tapebufs 20
# A positive integer telling taper how many 32k buffers to allocate.
# WARNING! If this is set too high, taper will not be able to allocate
# the memory and will die. The default is 20 (640k).
# Specify tape device and/or tape changer. If you don't have a tape
# changer, and you don't want to use more than one tape per run of
# amdump, just comment out the definition of tpchanger.
# Some tape changers require tapedev to be defined; others wil
Re: dump larger than tape
On Fri March 7 2003 04:06, [EMAIL PROTECTED] wrote: >Hi! > >my amanda works reasonably well under FreeBSD, but when trying to > backup RedHat, I get the message "dump larger than tape, skipping > incremental". though I'm quite sure the 128MB on this disk would > fit onto my 100GB ultrium tapes. > >Konni We're gonna need more details Konni. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
dump larger than tape
Hi! my amanda works reasonably well under FreeBSD, but when trying to backup RedHat, I get the message "dump larger than tape, skipping incremental". though I'm quite sure the 128MB on this disk would fit onto my 100GB ultrium tapes. Konni
Re: dump larger than tape, but cannot incremental dump new disk
On Fri, Aug 30, 2002 at 12:53:17PM -0300, Marcelo Alexandre de Oliveira wrote: > Hi all, > With solution to following message: > [dump larger than tape, but cannot incremental dump new disk ? ] > > > In my amanda.conf put the line: > > tpchanger "chg-manual" > > changerfile "/etc/amanda/master/lista/changer.conf" > > tapedev "/dev/nst0" # the no-rewind tape device to be used A limitation of amanda is the full dump of every entry in your disklist file must be smaller than a single tape. This is a new entry (first dump) and thus a full dump must be done. Amanda believes the entry to be too big to fit a single tape. Is it? If not probably some config file(s) entry is wrong. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
dump larger than tape, but cannot incremental dump new disk
Hi all, With solution to following message: [dump larger than tape, but cannot incremental dump new disk ? ] In my amanda.conf put the line: tpchanger "chg-manual" changerfile "/etc/amanda/master/lista/changer.conf" tapedev "/dev/nst0" # the no-rewind tape device to be used
again: dump larger than tape
Hello mailinglist, some days ago I had a problem with my dump: It was too large to fit on a tape. You told me to compress with server fast or server best. I did so, but the error occurred again. So I tried to backup from one server with rsync and backup the local files with amdump. Again: "localhost /backup lev 6 FAILED [dump larger than tape, skipping incremental] planner: FATAL cannot fit anything on tape, bailing out" woah... I looked at my /backup-directory and found different files on /backup/timberley. Each of them has a size of about 1.3 GB. The whole directory has got 33 GB - no, that won't fit on a DDS3-tape I' m afraid :-) The files seem to be amanda-archives: zeus:/backup/timberley # ls . .. 20020209 20020214 20020215 20020216 20020302 20020305 20020306 20020307 20020308 20020309 20020312 20020314 some of this direcroties are empty, but some..: -rw---1 amanda disk 1073741824 Mar 12 01:12 localhost._backup.6.7 -rw---1 amanda disk 1073741824 Mar 12 01:15 localhost._backup.6.8 -rw---1 amanda disk 1073741824 Mar 12 01:19 localhost._backup.6.9 Does the server possibly NOT erase the archives amanda saved? Can I remove them by a script or will I get in trouble when I try to restore? Thank you very much! Greetings, Leonie Nuenighoff Mit freundlichen Grüßen r-tec IT Systeme GmbH i.A. Leonie Nuenighoff __ r-tec IT Systeme GmbH Engelsfeld 9 45549 Sprockhövel - Germany Tel. +49 (0) 23 39 - 91 82-698 Fax +49 (0) 23 39 - 91 82-99 http://www.r-tec.net
again: dump larger than tape
Hello mailinglist, some days ago I had a problem with my dump: It was too large to fit on a tape. You told me to compress with server fast or server best. I did so, but the error occurred again. So I tried to backup from one server with rsync and backup the local files with amdump. Again: "localhost /backup lev 6 FAILED [dump larger than tape, skipping incremental] planner: FATAL cannot fit anything on tape, bailing out" woah... I looked at my /backup-directory and found different files on /backup/timberley. Each of them has a size of about 1.3 GB. The whole directory has got 33 GB - no, that won't fit on a DDS3-tape I' m afraid :-) The files seem to be amanda-archives: zeus:/backup/timberley # ls . .. 20020209 20020214 20020215 20020216 20020302 20020305 20020306 20020307 20020308 20020309 20020312 20020314 some of this direcroties are empty, but some..: -rw---1 amanda disk 1073741824 Mar 12 01:12 localhost._backup.6.7 -rw---1 amanda disk 1073741824 Mar 12 01:15 localhost._backup.6.8 -rw---1 amanda disk 1073741824 Mar 12 01:19 localhost._backup.6.9 Does the server possibly NOT erase the archives amanda saved? Can I remove them by a script or will I get in trouble when I try to restore? Thank you very much! Greetings, Leonie Nuenighoff Mit freundlichen Grüßen r-tec IT Systeme GmbH i.A. Leonie Nuenighoff __ r-tec IT Systeme GmbH Engelsfeld 9 45549 Sprockhövel - Germany Tel. +49 (0) 23 39 - 91 82-698 Fax +49 (0) 23 39 - 91 82-99 http://www.r-tec.net
Re: dump larger than tape, skipping incremental
On Thu, 14 Mar 2002 at 10:55am, "Nünighoff, Leonie, NUE" wrote > is there any possibility to compress the files AFTER they got transmitted to > the server? > In your dumptype: compress server fast (or best). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
dump larger than tape, skipping incremental
Hello amanda-gurus, I backup big files from a client over ethernet (100 MBit) to amanda server. the client is very weak (~ 200 MhZ) and it is no good idea to compress the files because the client could crash I think. The files get stored on a holding disk on the amanda server. I use DDS3-tapes and there is not enough free space to store the files on the tape. the following error occurs (amreport): FAILURE AND STRANGE DUMP SUMMARY: localhost /backup lev 6 FAILED [dump larger than tape, skipping incremental] planner: FATAL cannot fit anything on tape, bailing out is there any possibility to compress the files AFTER they got transmitted to the server? Thank you very much! Greetings, Leonie Nuenighoff __ r-tec IT Systeme GmbH Engelsfeld 9 45549 Sprockhövel - Germany Tel. +49 (0) 23 39 - 91 82-698 Fax +49 (0) 23 39 - 91 82-99 http://www.r-tec.net
Re: HW Compression and "dump larger than tape" message
[EMAIL PROTECTED] writes:
> I'm not quite sure what you mean by
>the second statement. Since you've set your tape device to the
>compressing device, *all* your dumps are using hardware compression.
You are right! I guess that would be a nice thing to be able to specify in the
dumptype section. Something like:
define dumptype root-tar-hw-comp {
root-tar
hw-compress on
}
and then have a line to specify the hw compression device:
tapedev /dev/nrmt2m
tapedev-hwc /dev/nrmt2h
So when hw-compress is on it uses tapedev-hwc, otherwise it uses tapedev. Maybe I'll
look into this when I get some free time.
Thanks for your help.
Steve
Steve CousinsEmail: [EMAIL PROTECTED]
Research Associate Phone: (207) 581-4302
Ocean Modeling Group
School of Marine Sciences 208 Libby Hall,
University of MaineOrono ME 04469
Re: HW Compression and "dump larger than tape" message
On Thu, 20 Dec 2001 at 11:39am, Steve Cousins wrote > I suppose I could change the length in the DLT tapetype to something > higher but that seems to be too coarse a solution. It would throw off the > planner when other volumes use compression. > That is exactly what you have to do when you use hardware compression -- lie about your tape length to amanda. I'm not quite sure what you mean by the second statement. Since you've set your tape device to the compressing device, *all* your dumps are using hardware compression. So, estimate how well hardware compression will work (hint -- it's not 2X), and tell amanda that tape length. For an AIT-1 drive (35GB native), I use 50GB, and haven't hit EOT yet. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
HW Compression and "dump larger than tape" message
I've got a volume that the planner is figuring is 48 GB. I'm using DLT IV tapes that should be good for 35 GB native with this tape drive. Software compression is off and Hardware compression is on (using device /dev/nrmt2h on a DEC Alpha OSF 1 version 4 system). I'm getting the message "dump larger than tape" message. I'm guessing that this is because Amanda knows that it is not doing any compression and it doesn't know that /dev/nrmt2h will do compression and since 48 is bigger than 35 it thinks the data won't fit. I'm wondering how best to deal with this. Is there a way to tell Amanda that this device will do compression and therefore do the backup, even though the data appears that it won't fit? I suppose I could change the length in the DLT tapetype to something higher but that seems to be too coarse a solution. It would throw off the planner when other volumes use compression. Thanks, Steve _ Steve Cousins Email: [EMAIL PROTECTED] Research AssociatePhone: (207) 581-4302 Ocean Modeling Group School of Marine Sciences 208 Libby Hall University of Maine Orono, Maine 04469
Re: dump larger than tape, but cannot incremental dump new disk
On Jun 18, 2001, "Arnar Gestsson" <[EMAIL PROTECTED]> wrote:
> the estimate, given by amstatus shows that a filesystem of 33.8 MB is
> 544758720k.
Are you using hardware compression? Is comprate set in the given
dumptype? What is the estimate printed by GNU tar in
/tmp/amanda/sendsize.debug on the client?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
dump larger than tape, but cannot incremental dump new disk
Hi there, I'm installing Amanda on a new HP A-server with 80GB DLT. Everything is done as usual(already running several hosts with the same setup), but now I get this in the report dump larger than tape, but cannot incremental dump new disk the estimate, given by amstatus shows that a filesystem of 33.8 MB is 544758720k. I have both tried to use comp-index and nocomp-index on the filessytem, but without any luck. My setup is the following HPUX 11.00 Amanda 2.4.2p2 gnutar 1.13.18 gzip 1.2.4 Help welcomed! BR Arnar Gestsson TrackWell Software
