Q: tape problem
Hi! I've a tape in my amanda policy that not works properly. The text following is an
amanda report and is always the same with this tape (and always with /dev/sdc2, always
the same scenario) ...somebody knows what it happens and how to solve this problem?
This is the only tape with this problem.
best regards,
Raul
[EMAIL PROTECTED]
--- AMANDA REPORT ---
These dumps were to tape FURV-POLICY04.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: FURV-POLICY05.
FAILURE AND STRANGE DUMP SUMMARY:
xaloc /dev/sdc2 lev 0 FAILED [out of tape]
xaloc /dev/sdc2 lev 0 FAILED ["data write: Connection reset by peer"]
xaloc /dev/sdc2 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:06
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.20.00.2
Original Size (meg) 0.90.00.9
Avg Compressed Size (%)17.6--17.6 (level:#disks ...)
Filesystems Dumped4 0 4 (1:4)
Avg Dump Rate (k/s) 262.3-- 262.3
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.30.00.3
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 4 0 4 (1:4)
Avg Tp Write Rate (k/s) 369.2-- 369.2
FAILED AND STRANGE DUMP DETAILS:
/-- xaloc /dev/sdc2 lev 0 FAILED ["data write: Connection reset by peer"]
sendbackup: start [xaloc:/dev/sdc2 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
\
NOTES:
taper: tape FURV-POLICY04 kb 3712 fm 5 writing file: Input/output error
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
kannagara/etc1 200 32 16.0 0:00 130.0 0:00 196.5
xaloc/dev/sdc1 1 60 32 53.3 0:00 560.8 0:00 789.2
xaloc/dev/sdc2 0 FAILED ---
xaloc/dev/sdd1 1 60 32 53.3 0:00 411.3 0:00 624.2
xaloc/etc1 590 64 10.8 0:00 277.7 0:00 351.7
(brought to you by Amanda version 2.4.2p2)
Re: Solaris 8 compile problem with amanda 2.4.4
*This message was transferred with a trial version of CommuniGate(tm) Pro* Solution found: I ended up using crle to add to the default library path: # crle -u -l /usr/local/lib Following great advice on this list (thanks all) I had tried using LDFLAGS="-R/usr/local/lib", LD_LIBRARY_PATH and --with-libraries=/usr/local/lib, none of which stopped the error. I also used crle to modify the trusted directories as someone suggested but this turned out not to be needed. I don't know why crle was necessary (I've not needed this before) and the other methods didn't work. Other compiled software on the same servers doesn't have this problem and I've not needed it with amanda before. Thanks again for the help, Jim > Having trouble with a solaris 8 compile of amanda 2.4.4 on sparc hardware. > I've compile amanda successfully before on the same platform, but cannot > work out what I'm doing wrong. > > The problem manifests when I run amcheck: > > ld.so.1: /usr/local/sbin/amcheck: fatal: libgcc_s.so.1: open failed: No such > file or directory > > The only thing I know is different is that I have compiled readline rather > than use the version from sunfreeware.com as I have in the past. When I have > installed the package version from sunfreeware I have always seen errors > about readline support no matter what I set LD_LIBRARY_PATH to > or --with-includes, etc. So I thought I try to get this working. I don't > know if this is the source of the error as I didn't think amcheck used > readline. > > Using: > > ./configure --with-user=amanda --with-group=backup \ > --with-includes=/usr/local/include \ > --with-libraries=/usr/local/lib \ > --with-gnutar=/usr/local/bin/tar \ > gcc 3.2.2 > gmake 3.8 > LD_LIBRARY_PATH=/usr/lib:/usr/local/lib > > Looking through config.log for error or fatal strings I can see: > > conftest.c:2: parse error before "me" > configure:4041: $? = 1 > configure: failed program was: > #ifndef __cplusplus > choke me > #endif > > In file included from configure:12882: > /usr/include/netinet/ip.h:61: field `ip_src' has incomplete type > /usr/include/netinet/ip.h:61: field `ip_dst' has incomplete type > /usr/include/netinet/ip.h:62: confused by earlier errors, bailing out > > ld: fatal: library -lfl: not found > ld: fatal: File processing errors. No output written to conftest > > ld: fatal: library -lcur_colr: not found > ld: fatal: File processing errors. No output written to conftest > > ld: fatal: library -lsun: not found > ld: fatal: File processing errors. No output written to conftest > collect2: ld returned 1 exit status > > However, the make; make install completes. > > > Any pointer appreciated, I have tried a lot of variants of --with-libraries > and LD_LIBRARY_PATH, tried with and without a portrange specified for backup > through a firewall, but I still get the same error.
Re: Backup plan needs advice.
bao wrote: Hi Martin I forgot to state that this is a tapeless setup to back up to disk. Then the full backup will be transferred to tape, and also is kept on disk for one week. Martin Hepworth wrote: Bao Amanda will need two separate config's to do this, BUT they will have idea of each others existance so the 'daily' will to full backups as and when the amanda planner thinks it's time to do one. I am _not_ letting Amanda schedule as to when to do a full backup, as is recommended. What I want (actually, my boss) is to force it to run a full every Monday, then a level 1 every other day for the rest of the week, according to the most recent Monday. Can't be done. Amanda's planner does this for you based on estimated sizes. I hope the above helps clarify it. Sorry for the confusion. -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: support for tape robot IBM 3583
Heinz-Josef Claes wrote: following scenario: The data from the file and print servers is synchronised in the night via rsyc to some cheap servers with fat disk Amanda with client side compression (the default setup for many people) can achieve the same effect (although not as efficient as rsync, but not that far either). Amanda spreads out the backup over the dumpcycle so that each night it has to do about the same amount of work. I know, it's a different approach than many (most?) other backup schemes, but in reality this work very well. The holdingdisk feature of amanda (your "fat disk") is an integral part of the system, and makes it possible to start many (slow) backups in parallel, and, at the same time, writing to the tapedrive in top speed. (Of course your other reasons to use your planned setup with storeBackup, fast/easy restores by users etc are still valid. And indeed, rsync can mirror your filesystems even faster.) decision up to know about this. -> So, amanda has a lot of time to do the backup, there are only a few clients (with big storage) to the servers (with the robots) and perhaps we can use less robots because we will not do a daily backup. Beware that Amanda works faster/better with many smaller clients than with few big clients. There can be more done in parallel if you have more clients. About 6 years ago, I worked in an environment with 8 big servers and each had a tape drive dedicated. The backup, with a home made script, took about all night on some systems, just completed in time before the first people started coming in. Then I switched companies, and learned about Amanda. In my current config I do my daily backups with 1 tape drive and I have about 25 servers (big and small) + 12 MSWin systems to backup. The total amount to backup is 12 times more than before. And my backup time each night takes only 3.5 hours. I also have an "archive" run each weekend (only full backups) to 2 drives (+ one flush on a third tape on monday morning). This takes only 8.5 hours. However, if I had to serialize all those backups it would take 42 hours. Amanda makes it possible to squeeze those 42 hours in less than 9 hours. If someone told me that 6 years ago, I wouldn't believe him. -- 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 * ***
amanda inparallel not working on large filesystems
greetings!
I have a backup strategy that happily performs a full backup for 160Gb
of data every night, however, I noticed that on three large filesystems
on a client machine, the backups work sequentially. The tape device is
an HP Surestore 2/20 autoloader, capable of 200Gb per tape.
I am sure that it used to dump these
backups in parallel, but now they are definitely waiting. amstatus throughout
the night shows all backups kicking off within 1 hour of each other, yet
each backup waiting until the preceeding one completes, before commencing.
I have maxdumps set to 5 and inparallel set to 10 (also tried it at 30
and 63), yet these three systems only backup sequentially.
I ran amstatus every five minutes last night to confirm this, and it shows
on filesystem dumping while the other is listed as dumping, but sticks
at 32K until the other one finishes.
anybody any clues on to why amanda should behave this way?
Each file system is about 30Gb in size and I have four holding discs:
50Gb, 36Gb, 30Gb, 5Gb each.
Also, it tries to fill up the 5Gb one before it even attempts the others.
Here is my amanda.conf file, hope this
helps.
dumpuser "amanda"
# the user to run dumps under
printer "pcm2300f2"
inparallel 10 # maximum dumpers
that will run in parallel (max 63)
netusage 10 Kbps #
maximum net bandwidth for Amanda, in KB per sec
dumpcycle 0 # the number
of days in the normal dump cycle
runspercycle 1
# the number of amdump runs in dumpcycle days
tapecycle 22 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 * bumpmult^(level-1)
ctimeout 1800
# number of seconds per filesystem timeouts on estimates
etimeout 1800
# number of seconds per filesystem for estimates.
dtimeout 24000
# number of idle seconds before a dump is aborted.
runtapes 1
# number of tapes to be used in a single run of amdump
tpchanger "/opt/etc/amanda/cc/chg-zd-mtx"
# the tape-changer glue script
changerfile "/opt/etc/amanda/cc/chg-zd-mtx"
# the tape-changer glue script
changerdev "/dev/changer"
# HP LTO on this box
tapedev "/dev/rmt/0un" #
the no-rewind tape device to be used
tapetype LTO
# what kind of tape it is (see tapetypes below)
labelstr "^cc[0-9][0-9][0-9][0-9]*$"
# label constraint regex: all tapes must
match
holdingdisk hd1 {
comment "main holding
disk"
directory "/amanda/dump1"
use 0
chunksize 500Mb
}
holdingdisk hd2 {
comment "JOW added
(local) secondary holding disk"
directory "/amanda/dump2"
use 0
chunksize 500Mb
}
holdingdisk hd3 {
comment "JOW added
secondary holding disk"
directory "/amanda/dump3"
use 0
chunksize 500Mb
}
holdingdisk hd4 {
comment "JOW added
secondary holding disk"
directory "/amanda/dump4"
use -500Mb
chunksize 500Mb
}
holdingdisk hd5 {
comment "JOW added
secondary holding disk"
directory "/amanda/dump6"
use -105Gb
chunksize 500Mb
}
maxdumps 5
reserve 30 # percent
infofile "/opt/etc/amanda/cc/curinfo"
# database DIRECTORY
logdir "/opt/etc/amanda/cc/log"
# log directory
indexdir "/opt/etc/amanda/cc/index"
# index directory
define tapetype LTO {
comment
"LTO tape drives"
length 20
mbytes
lbl-templ
"/opt/etc/amanda/DIN-A4.ps"
filemark
513 kbytes
speed 2
kps
}
define dumptype global {
comment "Global definitions"
index no
record no
compress none
dumpcycle 0
maxdumps 5
}
define dumptype lo_no_tar_full {
global
comment "Full dump of this filesystem always"
program "GNUTAR"
priority low
}
define dumptype me_no_tar_full {
global
comment "Full dump of this filesystem always"
program "GNUTAR"
priority medium
}
define dumptype hi_no_tar_full {
global
comment "Full dump of this filesystem always"
program "GNUTAR"
priority high
}
Re: support for tape robot IBM 3583
Am Mit, 2003-06-25 um 10.48 schrieb Paul Bijnens: > Heinz-Josef Claes wrote: > > following scenario: The data from the file and print servers is > > synchronised in the night via rsyc to some cheap servers with fat disk > > Amanda with client side compression (the default setup for many > people) can achieve the same effect (although not as efficient > as rsync, but not that far either). Amanda spreads out the backup > over the dumpcycle so that each night it has to do about the same > amount of work. > > I know, it's a different approach than many (most?) other backup > schemes, but in reality this work very well. > > The holdingdisk feature of amanda (your "fat disk") is an integral > part of the system, and makes it possible to start many (slow) backups > in parallel, and, at the same time, writing to the tapedrive in top speed. > > (Of course your other reasons to use your planned setup with > storeBackup, fast/easy restores by users etc are still valid. And > indeed, rsync can mirror your filesystems even faster.) > The problem of the backup to tape is, that it is not possible to make a full backup, because the wide area network doesn't have the capacity for that. This is one reason for using rsync, because rsync has to make only an "incremental" backup every night. The full backups to tape can then be made locally from the "fat" servers. The other reason for using the "fat" servers as mirrors for the night is as follows: If one of the file and print servers is totally broken (can not be repared fast), the "fat" server can be used (via WAN) as file and print server via redirect until a new file and print server is installed. Unfortunately, compression cannot be used because all files on the servers are encrypted (encryption / decryption is done from the clients). > > decision up to know about this. -> So, amanda has a lot of time to do > > the backup, there are only a few clients (with big storage) to the > > servers (with the robots) and perhaps we can use less robots because we > > will not do a daily backup. > > Beware that Amanda works faster/better with many smaller clients than > with few big clients. There can be more done in parallel if you have > more clients. > But it should be ok if the backup is done from local disks or via Gigabit Ethernet directly to tape!? > About 6 years ago, I worked in an environment with 8 big servers > and each had a tape drive dedicated. The backup, with a home made > script, took about all night on some systems, just completed in time > before the first people started coming in. > Then I switched companies, and learned about Amanda. In my current > config I do my daily backups with 1 tape drive and I have about 25 > servers (big and small) + 12 MSWin systems to backup. The total amount > to backup is 12 times more than before. And my backup time each night > takes only 3.5 hours. > > I also have an "archive" run each weekend (only full backups) to > 2 drives (+ one flush on a third tape on monday morning). > This takes only 8.5 hours. However, if I had to serialize all > those backups it would take 42 hours. Amanda makes it possible to > squeeze those 42 hours in less than 9 hours. > > If someone told me that 6 years ago, I wouldn't believe him. >
Help compiling on OS X/Darwin
Hi, I am a newbie to UN*X, and have downloaded the 2.4.4 sources and read the notes on compiling on OS X and have searched the lists. However I can't get it to compile on OS X Jag. There are warnings in the configure and when I compile I get recursive errors in Amanda.h. Can anyone point me to a FAQ or a help page please? Or offer any other advice? Thanks -- Regards Ken Simpson .
Diferential Backup
Hi, It it possible to use amanda to do diferential backups ? Are there any specific configuration ? Thanks, Roberto Samarone Araujo
Multiple Tapes in Single run issue
Hi all, I have a backup image of some size greater than the tape size. Is multiple tapes in single run support available in amanda. If not how to go about this issue? What kind of configuration is needed in this scenario? thanks, Vijay Nilgiri Networks
Re: Multiple Tapes in Single run issue
On Wed, 25 Jun 2003 at 5:03pm, Vijay wrote > I have a backup image of some size greater than the tape size. Is > multiple tapes in single run support available in amanda. If not how > to go about this issue? What kind of configuration is needed in this > scenario? Amanda can use multiple tapes in one amdump, but it can't span a single image across multiple tapes. You'll have to divide up that image, using tar to grab subdirectories rather than the whole FS. And questions like this only need to go to amanda-users, not amanda-hackers. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Help compiling on OS X/Darwin
One of my staff encountered the same problem with 2.4.4. He was able to successfully compile 2.4.3 and we've done some successful dump and restore tests with that. I was going to look into it further but haven't so far. -Mitch On Wed, 25 Jun 2003, Ken Simpson wrote: > Hi, I am a newbie to UN*X, and have downloaded the 2.4.4 sources and > read the notes on compiling on OS X and have searched the lists. > > However I can't get it to compile on OS X Jag. There are warnings in > the configure and when I compile I get recursive errors in Amanda.h. > Can anyone point me to a FAQ or a help page please? Or offer any > other advice? > > Thanks > -- > Regards > Ken Simpson > . >
Re: Multiple Tapes in Single run issue
Yes it is. You need to use a tape changer script. See docs/TAPE.CHANGERS. You can either use a real tape changer, or set up several drives and use the chg-multi script to fake a real changer. Nik >>> Vijay <[EMAIL PROTECTED]> 06/25/03 07:33AM >>> Hi all, I have a backup image of some size greater than the tape size. Is multiple tapes in single run support available in amanda. If not how to go about this issue? What kind of configuration is needed in this scenario? thanks, Vijay Nilgiri Networks
Re: Help compiling on OS X/Darwin
Ken Simpson wrote: Ken Simpson wrote: Hi, I am a newbie to UN*X, and have downloaded the 2.4.4 sources and read the notes on compiling on OS X and have searched the lists. However I can't get it to compile on OS X Jag. There are warnings in the configure and when I compile I get recursive errors in Amanda.h. Can anyone point me to a FAQ or a help page please? Or offer any other advice? Thanks Ken I compiled it under 10.1 with little problem (there was a problem but I can;t remember what it was..). What errors where you getting on the configure? Thank for helping Martin, these are the errors, and I have added the entire configure output as an attachment configure: WARNING: you should use --build, --host, --target configure: WARNING: *** You do not have gnuplot. Amplot will not be installed. configure: WARNING: netinet/ip.h: present but cannot be compiled configure: WARNING: netinet/ip.h: check for missing prerequisite headers? configure: WARNING: netinet/ip.h: proceeding with the preprocessor's result configure: WARNING: *** No readline library, no history and command line editing in amrecover! ok looking at the log file, you've told it that its a NetBSD based system. You'll have to mess with the default system types so that it matches powerpc-apple-rhapsody5.5 and use that for the type. Also I find I don;t need to put in the --with-config=backupset on clients.. there should be soemthing in on the the messages on the list archive on this as I kinda remember messing with some file to get this right. -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
RE: Diferential Backup
Hi Roberto, I don't believe so. Amanda uses either the vendor supplied dump program, or GNU tar to do the backup. I know GNU tar does not do differential backup and AFAIK none of the vendor supplied dump programs will do differential backup either (I'm pretty sure for Solaris, AIX, *BSD, and Linux derivatives). > -Original Message- > From: Roberto Samarone Araujo (RSA) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 25, 2003 7:31 AM > To: [EMAIL PROTECTED] > Subject: Diferential Backup > > > Hi, > > It it possible to use amanda to do diferential backups > ? Are there any > specific configuration ? > > Thanks, > > Roberto Samarone Araujo > > >
RE: Need A sample Tapelist file
> -Original Message- > From: Gene Heskett [mailto:[EMAIL PROTECTED] > On Tuesday 24 June 2003 17:27, Harry Mbang wrote: > >Hi, > > I am still trying to get my first successful Amanda backup. > > Now when I run amcheck, I get an error > > > >"cannot read/write /usr/local/var/Amanda/gnutar-lists: No such file > > or directory" > > > >Indeed there is no such file or directory. My gnutar-lists is > > located in /var/lib/Amanda. What shall I do? I am also guessing > > that Amanda is going to want read/write other files and folders in > > the non-extisting directory. Should I recompile Amanda with some > > option specifying the default directory for that type files and > > folders? Thanks in advance for any advice. > > > >Harry. > It sounds as if you have a mix-n-match install there. If an rpm, it > could be /var/lib/amanda. But the default for building a tarball is > /usr/local/whatever. > > Move your tapelists and the rest of your config stuff to > /usr/local/etc/amanda and see if that fixes things by running amcheck > (as the user who normally runs amanda, it won't run as root), and > fixing any other errors (warnings can be ignored) that pop up. Also > do an 'rpm -e amanda*' to get rid of the rpms , they have no business > surviving on the system if you have built amanda from a tarball. Or you could do what I did and add the config parameter into your amanda.conf file. tapelist "/var/amanda/CONFIG-NAME/tapelist" # list of used tapes
RE: Diferential Backup
> -Original Message- > On Wed, 25 Jun 2003 at 9:51am, Ean Kingston wrote > > > I don't believe so. Amanda uses either the vendor supplied dump > > program, or GNU tar to do the backup. I know GNU tar does not do > > differential backup and AFAIK none of the vendor supplied > dump programs > > will do differential backup either (I'm pretty sure for > Solaris, AIX, > > *BSD, and Linux derivatives). > > The terminology here is a bit confusing. If by > "differential" you mean > only the bits (not whole files, but bits, like rsync) that > have changed, > then no, neither tar nor dump do that. But if Roberto meant > incremental > (as in the files that have changed), then of course amanda does that. > > Just trying to clarify for the archives. Good point. Since a 'differential backup' is 'just the bits that changed' (like rsync) for other backup software I've used, I assumed that Roberto meant that. Perhaps I should have been clearer.
Re: Diferential Backup
On Wednesday 25 June 2003 07:30, Roberto Samarone Araujo (RSA) wrote: >Hi, > > It it possible to use amanda to do diferential backups ? Are > there any specific configuration ? > Amanda will do differentials AFTER amanda has done a full. This is so that there is a baseline reference date established for that disklist entry. But I think you mis-understand how amanda works. Unlike the other solutions, amanda tries to use about the same amount of tape every night. And amanda will juggle the schedule about, moving the dates of things up by sometimes as much as 5 days in trying to achieve that, and given enough time in dumpcycles, will do pretty well at this balanceing act. To recap: dumpcycle: The number of days (or weeks) that amanda has to do a full backup of each disklist entry in. A lot of folks run 7 days or 1 week. runspercycle: In case you are doing a monday to friday only run schedule, this tells amanda how many times amanda will be run in the above 'dumpcycle' number of days. Businesses often set this to 5 since theres not much going on over the weekends. runtapes: If you have a tape changer, this sets the number of tapes amanda will be allowed to use per run. tapecycle: The number of tapes in the rotating pool. Amanda will use every tape in the pool until it has used them all, and will then start to recycle them on an oldest first basis. This should be not less than 2x runspercycle*runtapes plus 2 or 3 for comfort in knowing that you have in fact at least 2 generations of full, level 0 backups on everything in the disklist. You wouldn't want to ever get in the situation where you were over-writing your only full backup of something, and have a power failure while doing that entry's lavel 0 again. Here at home, I'm useing 7, 7, 1, 28 settings. DDS2 tapes are cheap, and I actually have about twice that many in stock. Amanda has had enough time to arrive at a fairly consistent tape useage of above 90% fill each night. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
RE: Diferential Backup
On Wed, 25 Jun 2003 at 9:51am, Ean Kingston wrote > I don't believe so. Amanda uses either the vendor supplied dump > program, or GNU tar to do the backup. I know GNU tar does not do > differential backup and AFAIK none of the vendor supplied dump programs > will do differential backup either (I'm pretty sure for Solaris, AIX, > *BSD, and Linux derivatives). The terminology here is a bit confusing. If by "differential" you mean only the bits (not whole files, but bits, like rsync) that have changed, then no, neither tar nor dump do that. But if Roberto meant incremental (as in the files that have changed), then of course amanda does that. Just trying to clarify for the archives. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Multiple Tapes in Single run issue
On Wednesday 25 June 2003 08:25, Nicholas Berry wrote: >Yes it is. You need to use a tape changer script. Unforch you missed the keyword, his *image* is bigger than a tape, and amanda cannot span a single filesystem across nore than one tape. He will have to use tar, and break that filesystem up into its subdirs, one DLE (disklist entry) per subdir. I've been doing that for my /usr's directories for quite some time. A side advantage is that in having smaller DLE's, amanda can do a much better job of balanceing the nightly tape useage, I'm pretty consistently in the middle 90 % range now that the dust has settled. If amanda hit the tapes EOT while writing a DLE, and runtapes is greater than 1, then amanda can load the next tape, but that DLE will then be restarted from byte number 1 on the next tape. If that DEL is bigger than a tape, then its an endless cycle, that DLE will never be successfully taped. >See docs/TAPE.CHANGERS. > >You can either use a real tape changer, or set up several drives and >use >the chg-multi script to fake a real changer. > >Nik > Vijay <[EMAIL PROTECTED]> 06/25/03 07:33AM >>> > >Hi all, > I have a backup image of some size greater than the tape size. > Is > >multiple tapes in single run support available in amanda. If not how >to go about this issue? What kind of configuration is needed in this >scenario? > >thanks, >Vijay >Nilgiri Networks -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: Diferential Backup
On Wednesday 25 June 2003 10:01, Ean Kingston wrote: >> -Original Message- >> On Wed, 25 Jun 2003 at 9:51am, Ean Kingston wrote >> >> > I don't believe so. Amanda uses either the vendor supplied dump >> > program, or GNU tar to do the backup. I know GNU tar does not do >> > differential backup and AFAIK none of the vendor supplied >> >> dump programs >> >> > will do differential backup either (I'm pretty sure for >> >> Solaris, AIX, >> >> > *BSD, and Linux derivatives). >> >> The terminology here is a bit confusing. If by >> "differential" you mean >> only the bits (not whole files, but bits, like rsync) that >> have changed, >> then no, neither tar nor dump do that. But if Roberto meant >> incremental >> (as in the files that have changed), then of course amanda does >> that. >> >> Just trying to clarify for the archives. > >Good point. Since a 'differential backup' is 'just the bits that > changed' (like rsync) for other backup software I've used, I > assumed that Roberto meant that. Perhaps I should have been > clearer. And I sinned also in that I automaticly made the assumption that he actually meant incremental, since unlike an rsync scenario, the filesystem to do the differential against exists only on a tape some days back in the scheduleing, which for amanda, may as well be in Marrakesh or Ulan Bator. Or maybe even on the moon. The point being that its not directly accessable. My bad. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: Multiple Tapes in Single run issue
Good point :). Another solution is RAIT. I back up to five Exabyte EXB10e units as a RAIT. I get 20GB max. image size using 5GB tapes, and multiple tapes per run too. Nik >>> Gene Heskett <[EMAIL PROTECTED]> 06/25/03 10:15AM >>> On Wednesday 25 June 2003 08:25, Nicholas Berry wrote: >Yes it is. You need to use a tape changer script. Unforch you missed the keyword, his *image* is bigger than a tape, and amanda cannot span a single filesystem across nore than one tape. He will have to use tar, and break that filesystem up into its subdirs, one DLE (disklist entry) per subdir. I've been doing that for my /usr's directories for quite some time. A side advantage is that in having smaller DLE's, amanda can do a much better job of balanceing the nightly tape useage, I'm pretty consistently in the middle 90 % range now that the dust has settled. If amanda hit the tapes EOT while writing a DLE, and runtapes is greater than 1, then amanda can load the next tape, but that DLE will then be restarted from byte number 1 on the next tape. If that DEL is bigger than a tape, then its an endless cycle, that DLE will never be successfully taped.
Confirmation for subscribe amanda-users
-- Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "[EMAIL PROTECTED]". If you really want this action to be taken, please send the following commands (exactly as shown) back to "[EMAIL PROTECTED]": auth e7c6df57 subscribe amanda-users [EMAIL PROTECTED] If you do not want this action to be taken, simply ignore this message and the request will be disregarded. If your mailer will not allow you to send the entire command as a single line, you may split it using backslashes, like so: auth e7c6df57 subscribe amanda-users \ [EMAIL PROTECTED] If you have any questions about the policy of the list owner, please contact "[EMAIL PROTECTED]". Thanks! [EMAIL PROTECTED]
Backup size doubled
I am running Amanda 2.4.3 on Freebsd with a single Seagate DAT drive On a full backup of my /usr directory which df shows the size used as being 4 gb I am using nocomp because the client and the server are the same box. Amanda for some reason is backing up 8 gb What's going on? Please help!
Confirmation for subscribe amanda-users
-- Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "[EMAIL PROTECTED]". If you really want this action to be taken, please send the following commands (exactly as shown) back to "[EMAIL PROTECTED]": auth e7c6df57 subscribe amanda-users [EMAIL PROTECTED] If you do not want this action to be taken, simply ignore this message and the request will be disregarded. If your mailer will not allow you to send the entire command as a single line, you may split it using backslashes, like so: auth e7c6df57 subscribe amanda-users \ [EMAIL PROTECTED] If you have any questions about the policy of the list owner, please contact "[EMAIL PROTECTED]". Thanks! [EMAIL PROTECTED]
Re: Backup size doubled
Internet Support wrote:
I am running Amanda 2.4.3 on Freebsd with a single Seagate DAT drive
On a full backup of my /usr directory which df shows the size used
as being 4 gb I am using nocomp because the client and the server are the
same box.
Amanda for some reason is backing up 8 gb
What's going on? Please help!
We need much more information than that. Excerpts from reports
and debug files would help more.
("nocomp" has nothing to do with the client and server being
the same; it has to do with amount of data, or with hardware
compression settings on tape vs software compression.)
Re: Multiple Tapes in Single run issue
On Wed, Jun 25, 2003 at 11:35:24AM -0400, Nicholas Berry wrote: > Good point :). > > Another solution is RAIT. I back up to five Exabyte EXB10e units as a > RAIT. > > I get 20GB max. image size using 5GB tapes, and multiple tapes per run > too. That's nice to hear. It is a good use for RAIT. You must have been a non-responder to the recent survey as zero responders said they used RAIT. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Backup size doubled
Here is my config file disklist and the latest Amanda Report
inparallel 4 # maximum dumpers that will run in parallel
netusage 1000 KB # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 1 week # the number of days in the normal dump cycle
tapecycle 4 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
#tpchanger "chg-generic" # the tape-changer glue script
tapedev "/dev/nrsa0" # or use the (no-rewind!) tape device directly
tapetype DAT # what kind of tape it is (see tapetypes below)
labelstr "^VOL[0-9][0-9]*$" # label constraint regex: all tapes must match
diskdir "/usr/amanda" # where the holding disk is
disksize 1 MB # how much space can we use on it
#diskdir "/dumps/amanda/work" # additionaly holding disks can be specified
#disksize 1200 MB # they are used round-robin
# Amanda needs a few MB of diskspace for the log and debug files,
# as well as a database. This stuff can grow large, so the conf directory
# isn't usually appropriate. We use /usr/adm. Create an amanda directory
# under there. You need a separate infofile and logfile for each
# configuration, so create subdirectories for each conf and put the files
# there. Specify the filenames below.
infofile "/var/log/amanda/cm02/curinfo" # database filename
logfile "/var/log/amanda/cm02/log" # log filename
indexdir "/var/log/amanda/cm02/index" # index directory
# 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.
#
# For completeness Amanda should calculate the inter-record gaps too, but it
# doesn't. For EXABYTE and DAT tapes this is ok. Anyone using 9 tracks for
# amanda and need IRG calculations? Drop me a note if so.
define tapetype EXB-8500 {
comment "Exabyte EXB-8500 drive on decent machine"
length 4200 mbytes
filemark 48 kbytes
speed 474 kbytes
}
define tapetype EXB-8200 {
comment "Exabyte EXB-8200 drive on decent machine"
length 2200 mbytes
filemark 2130 kbytes
speed 240 kbytes
}
define tapetype DAT {
comment "DAT tape drives"
length 2 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
speed 100 kbytes
}
define tapetype MIMSY-MEGATAPE {
comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
length 2200 mbytes
filemark 2130 kbytes
speed 170 kbytes # limited by the Emulex bus interface, ugh
}
# dumptypes
#
# These are referred to by the disklist file. The dumptype specifies
# certain "options" for dumping including:
# compress-fast - (default) compress on the client using fast algorithm
# compress-best - compress using the best (and slowww) algorithm
# no-compress - don't compress the dump output
# record - (default) record the dump in /etc/dumpdates
# no-record - don't record the dump, for testing
# no-hold - don't go to the holding disk, good for dumping
# the holding disk partition itself.
# skip-full - Skip the disk when a level 0 is due, to allow
# full backups outside Amanda, eg when the machine
# is in single-user mode.
# skip-incr - Skip the disk when the level 0 is NOT due. This
# is used in archive configurations, where only full
# dumps are done and the tapes saved.
# no-full - Do a level 1 every night. This can be used, for
# example, for small root filesystems that only change
# slightly relative to a site-wide prototype. Amanda
# then backs up just the changes.
#
# Also, the dumptype specifies the priority level, where "low", "medium" and
# "high" are the allowed levels. These are only really used when Amanda has
# no tape to write to because of some error. In that "degraded mode", as
# many incrementals as will fit on the holding disk are done, higher
priority
# first, to insure the important disks are dumped first.
define dumptype comp-user-tar {
program "GNUTAR"
comment "partitions dumped with tar"
options compress
priority medium
}
define dumptype comp-user {
comment "Non-root partitions on reasonably fast machines"
options compress-fast
priority medium
}
define dumptype nocomp-user {
comment "Non-root partitions on slow machines"
options no-compress
priority medium
}
define dumptype holding-disk {
comment "The master-host holding disk itself"
options no-hold
priority medium
}
define dumptype comp-root {
comment "Root partitions with compression"
options compress-fast
priority low
}
define dumptype nocomp-root {
comment "Root partitions without compression"
options no-compress
priority low
}
define dumptype comp-high {
comment "very important partitions on fast machines"
options compress-best
priori
Re: Multiple Tapes in Single run issue
Sorry. Must have been sleeping. Using changers with RAIT isn't easy. Luckily I had written my own changer program[me] to make multiple changers appear as one to Amanda (which only understands one), and it was pretty easy to modify that to support RAIT. It also fakes a bar code reader, so Amanda does a search for, say, rait-2-23, and the changer code loads the five tapes that make up the RAIT. If anyone wants to try running multiple changers, I can send a copy of the hack, er I mean code. Nik >>> Jon LaBadie <[EMAIL PROTECTED]> 06/25/03 12:11PM >>> On Wed, Jun 25, 2003 at 11:35:24AM -0400, Nicholas Berry wrote: > Good point :). > > Another solution is RAIT. I back up to five Exabyte EXB10e units as a > RAIT. > > I get 20GB max. image size using 5GB tapes, and multiple tapes per run > too. That's nice to hear. It is a good use for RAIT. You must have been a non-responder to the recent survey as zero responders said they used RAIT. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
help with backup problems please
Hello,
I have amanda 2.4.3-4 on RH9 and I'm trying to configure it for the first
time.
A full dump of the server every night is all I need: I have 7 tapes and I want
to reuse them on a weekly basis (I actually need only 5 tapes for weekdays,
the backup is not due on weekends, the other 2 are for errors that need
amflush).
The crontab work should be no problem to me, the sample crontab should be
enough. However I'm testing the backup process by launching the respective
commands from the command line: I guess that when this will work, crontab
will follow...
What actually works:
# amlabel DailySet1 DailySet1n1
works correctly.
The problems:
# amdump DailySet1
moves the tape for a few seconds, does not give any output on the screen and
it runs way too little time to believe it has written anything on the tape,
in fact
# amrestore /dev/st0
recognizes the tape as being an amanda tape (cause amlabel worked, I believe)
but restores nothing, no new file is created in the current directory.
The relevant parts of my config:
*** /etc/amanda/DailySet1/disklist ***
# These subdirs are all in the same filesystem, so this could be a problem
# too, but saying "localhost /dev/md0 comp-user-tar" doesn't work either and
# yelds exactly the same results
localhost /home comp-user-tar
localhost /etc comp-root-tar
localhost /boot comp-root-tar
localhost /bin comp-root-tar
localhost /lib comp-root-tar
localhost /root comp-root-tar
localhost /sbin comp-root-tar
localhost /usr comp-root-tar
localhost /var/log comp-root-tar
*** /etc/amanda/DailySet1/amanda.conf ***
[...]
dumpuser "root" # the user to run dumps under
[...]
dumpcycle 0 # the number of days in the normal dump cycle
runspercycle 5 days # the number of amdump runs in dumpcycle days
tapecycle 7 tapes # the number of tapes in rotation
[...]
# Here I've put high values as an extra measure to avoid level bumping...
bumpsize 200 Gb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 2 # minimum days at each level
bumpmult 200# threshold = bumpsize * bumpmult^(level-1)
[...]
tapedev "/dev/nst0" # the no-rewind tape device to be used
[...]
tapetype DLT-80 # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1n[1-7]*$" # label constraint regex: all tapes must match
[...]
define tapetype DLT-80 {
comment "DLT 40/80 tape drive produced by tapetype program"
length 38095 mbytes
filemark 32 kbytes
speed 5608 kps
}
[...]
Any idea?
Re: Diferential Backup [What does "differential backup" mean]
[This is a meta-answer, because I've heard people say "differential backup", but I had no darn idea what it meant, and I figure there might be others out there in the same boat!] On Wed, Jun 25, 2003 at 08:30:41AM -0300, Roberto Samarone Araujo (RSA) wrote: > It it possible to use amanda to do diferential backups ? Are there any > specific configuration ? AFAICT, there are two meanings to "differential" when you're talking about backups. 1) Databases. For databases (e.g., Oracle, SQL) you are often backing up a small number of very large files (and sometimes not files at all, but raw partitions). In this context, "differential" means backing up only those blocks within a large file (or raw partition) that have changed. This is obviously the realm of a special-purpose backup program, Amanda itself definitely doesn't know anything about it. 2) Windows file systems. Files on (all?) Windows file systems have an "archive bit". The intent is that this bit is set when a file is modified. The intent is that a full backup clears all the archive bits. In this context: An "incremental" backup gets files that have changed since the full or previous incremental, and re-clears the archive bits. A "differential" backup gets files that have changed since the full, and leaves the archive bits alone. So this is sort of a round-about way of getting the same differences in behavior you get my controlling level in dump. Strictly speaking, Amanda doesn't know anything about this either. Since you're apparently a Windows guy, I'm guessing you mean "windows differential", not "database differential". Is that correct? And then the answer to your question depends on what type of file system you're backing up and what underlying backup engine (e.g., tar, dump, smbclient) you're using. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Backup size doubled (sendbackup.debug)
You can see that Amanda correctly estimates the size at estimated 4752738 tape blocks But actually dumps DUMP: 9029315 tape blocks sendbackup: debug 1 pid 11410 ruid 2 euid 2: start at Wed Jun 25 00:11:00 2003 /usr/local/libexec/amanda/sendbackup: version 2.4.3 parsed request as: program `DUMP' disk `ad0s1f' device `ad0s1f' level 0 since 1970:1:1:0:0:0 options `|;auth=bsd;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.3690 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.3691 sendbackup: time 0.002: waiting for connect on 3690, then 3691 sendbackup: time 0.002: stream_accept: connection from 555.555.555.555.3692 sendbackup: time 0.002: stream_accept: connection from 555.555.555.555.3693 sendbackup: time 0.002: got all connections sendbackup: time 0.004: dumping device '/dev/ad0s1f' with 'ufs' sendbackup: time 0.004: spawning /sbin/dump in pipeline sendbackup: argument list: dump 0ushf 1048576 0 - /dev/ad0s1f sendbackup: time 0.007: 91: normal(|): DUMP: Date of this level 0 dump: Wed Jun 25 00:11:00 2003 sendbackup: time 0.008: 91: normal(|): DUMP: Date of last level 0 dump: the epoch sendbackup: time 0.008: 91: normal(|): DUMP: Dumping /dev/ad0s1f (/usr) to standard output sendbackup: time 0.073: 91: normal(|): DUMP: mapping (Pass I) [regular files] sendbackup: time 17.649: 91: normal(|): DUMP: mapping (Pass II) [directories] sendbackup: time 17.650: 91: normal(|): DUMP: estimated 4752738 tape blocks. sendbackup: time 17.685: 91: normal(|): DUMP: dumping (Pass III) [directories] sendbackup: time 59.543: 91: normal(|): DUMP: dumping (Pass IV) [regular files] sendbackup: time 317.292: 91: normal(|): DUMP: 20.79% done, finished in 0:19 sendbackup: time 617.280: 91: normal(|): DUMP: 46.31% done, finished in 0:11 sendbackup: time 917.279: 91: normal(|): DUMP: 65.08% done, finished in 0:08 sendbackup: time 1217.355: 91: normal(|): DUMP: 84.36% done, finished in 0:03 sendbackup: time 1517.287: 91: normal(|): DUMP: 104.80% done, finished in 0:-1 sendbackup: time 1817.284: 91: normal(|): DUMP: 121.45% done, finished in 0:-5 sendbackup: time 2117.284: 91: normal(|): DUMP: 138.32% done, finished in 0:-9 sendbackup: time 2417.280: 91: normal(|): DUMP: 161.07% done, finished in 0:-15 sendbackup: time 2684.483: 49:size(|): DUMP: DUMP: 9029315 tape blocks sendbackup: time 2684.518: 91: normal(|): DUMP: finished in 2667 seconds, throughput 3385 KBytes/sec sendbackup: time 2684.526: 91: normal(|): DUMP: level 0 dump on Wed Jun 25 00:11:00 2003 sendbackup: time 2684.529: 91: normal(|): DUMP: DUMP IS DONE sendbackup: time 2684.530: pid 11410 finish time Wed Jun 25 00:55:45 2003
Re: Backup size doubled (sendbackup.debug)
Internet Support wrote: > > You can see that Amanda correctly estimates the size at estimated 4752738 > tape blocks > But actually dumps DUMP: 9029315 tape blocks Yes, dump is actually dumping the holding area along with all the other files on that partition. If you were using tar instead of dump, you could use an "exclude" to prevent tar from considering the holding area. Since you're using dump, your only option is to let Amanda know that it's the holding disk by adding the "holding-disk yes" option in a new dumptype. This is all from memory; do check the gory details in the supplied amanda.conf file. Marty -- Marty Shannon, RHCE (@ home) mailto:[EMAIL PROTECTED]
Re: Diferential Backup [What does "differential backup" mean]
I'm using Linux and dump. Roberto Samarone Araujo > [This is a meta-answer, because I've heard people say "differential > backup", but I had no darn idea what it meant, and I figure there > might be others out there in the same boat!] > > On Wed, Jun 25, 2003 at 08:30:41AM -0300, Roberto Samarone Araujo (RSA) wrote: > > It it possible to use amanda to do diferential backups ? Are there any > > specific configuration ? > > AFAICT, there are two meanings to "differential" when you're talking > about backups. > > 1) Databases. For databases (e.g., Oracle, SQL) you are often backing > up a small number of very large files (and sometimes not files at > all, but raw partitions). In this context, "differential" means > backing up only those blocks within a large file (or raw partition) > that have changed. > > This is obviously the realm of a special-purpose backup program, > Amanda itself definitely doesn't know anything about it. > > 2) Windows file systems. Files on (all?) Windows file systems have an > "archive bit". The intent is that this bit is set when a file is > modified. The intent is that a full backup clears all the archive > bits. In this context: > > An "incremental" backup gets files that have changed since the full > or previous incremental, and re-clears the archive bits. > > A "differential" backup gets files that have changed since the full, > and leaves the archive bits alone. > > So this is sort of a round-about way of getting the same > differences in behavior you get my controlling level in dump. > Strictly speaking, Amanda doesn't know anything about this either. > > Since you're apparently a Windows guy, I'm guessing you mean "windows > differential", not "database differential". Is that correct? And then > the answer to your question depends on what type of file system you're > backing up and what underlying backup engine (e.g., tar, dump, > smbclient) you're using. > > -- > Jay Lessert [EMAIL PROTECTED] > Accelerant Networks Inc. (voice)1.503.439.3461 > Beaverton OR, USA(fax)1.503.466.9472
RE: Need A sample Tapelist file
Hi, thanks all for the responses. I went followed your advice of reinstalling Amanda. Now I have the config folder in /usr/local/etc/Amanda. I am now at the point where when I do amcheck, I get three errors: 1)Can not open exclude file /usr/local/lib/Amanda/exclude/gtar ... 2)Can not read/write /etc/amandates ... 3) Cannot read/write /usr/local/var/Amanda/gnutar-lists/ ... I am at a loss because unlike before I cannot find these files anywhere. Any ideas? I cannot find reference to a similar problem in the archives (scanning the titles). Thanks in advance. -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 11:15 PM To: Harry Mbang; [EMAIL PROTECTED] Subject: Re: Need A sample Tapelist file On Tuesday 24 June 2003 17:27, Harry Mbang wrote: >Hi, > I am still trying to get my first successful Amanda backup. > Now when I run amcheck, I get an error > >"cannot read/write /usr/local/var/Amanda/gnutar-lists: No such file > or directory" > >Indeed there is no such file or directory. My gnutar-lists is > located in /var/lib/Amanda. What shall I do? I am also guessing > that Amanda is going to want read/write other files and folders in > the non-extisting directory. Should I recompile Amanda with some > option specifying the default directory for that type files and > folders? Thanks in advance for any advice. > >Harry. It sounds as if you have a mix-n-match install there. If an rpm, it could be /var/lib/amanda. But the default for building a tarball is /usr/local/whatever. Move your tapelists and the rest of your config stuff to /usr/local/etc/amanda and see if that fixes things by running amcheck (as the user who normally runs amanda, it won't run as root), and fixing any other errors (warnings can be ignored) that pop up. Also do an 'rpm -e amanda*' to get rid of the rpms , they have no business surviving on the system if you have built amanda from a tarball. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Can't get disklist example to work...
Hello,
I can't get the example in the disklist to work for splitting
up large disks with gnutar. Like this:
# boltneck.domain.com /adminshare/am /adminshare {
# comp-user-tar
# include append "./[a-m]*"
# } 1
# boltneck.domain.com /adminshare/nz /adminshare {
# comp-user-tar
# include "./[n-z]*"
# } -1
etc.
Gnutar correctly uses the regular expressions, but when it comes to
actually back them up I get stuff like
? gtar: Cannot stat ./lost+found: No such file or directory
? gtar: Cannot stat ./it: No such file or directory
? gtar: Cannot stat ./inuse.txt: No such file or directory
? gtar: Cannot stat ./customers.txt: No such file or directory
? gtar: Cannot add file ./customers.txt: No such file or directory
? gtar: Cannot add file ./inuse.txt: No such file or directory
? gtar: Cannot add file ./it: No such file or directory
? gtar: Cannot add file ./lost+found: No such file or directory
| Total bytes written: 10240
These files/directories DO exist! What happened? It's like it's not
backing up in the right place, but it looked there to get
the name of the directory. It's like its not cd'ing to the parent
directory first. Is there a bug here, or am I not configuring
correctly?
Thanks in advance,
Jeff Parker
--
--Jeffrey W. Parker
--Unix/Linux System Administrator
mailto:[EMAIL PROTECTED]
-
Re: Need A sample Tapelist file
Harry Mbang wrote: 1)Can not open exclude file /usr/local/lib/Amanda/exclude/gtar ... So you have a dumptype that says there is an exclude file there. Alternative solutions: - remove the directive that you have your exclude file - add the directive "optional" to the exclude statement so that amanda doesn't complain when the file is not there - create the file (may be zero length, or filled with real exclude patterns) And btw, the file should be on the CLIENT, each client that you backup with that dumptype. 2)Can not read/write /etc/amandates ... as root: touch /etc/amandates; chown amanda /etc/amandates 3) Cannot read/write /usr/local/var/Amanda/gnutar-lists/ ... As amanda (or as root, and "chown amanda ... " afterwards: mkdir /usr/local/var/Amanda/gnutar-lists
RE: Need A sample Tapelist file
Hey guys, I switched from using a tar based program for dumptype to using nocomp-test. It seemed to work. I am yet to do a restore. It seems like my previous problems are due to the way I have gnutar set up. -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 11:15 PM To: Harry Mbang; [EMAIL PROTECTED] Subject: Re: Need A sample Tapelist file On Tuesday 24 June 2003 17:27, Harry Mbang wrote: >Hi, > I am still trying to get my first successful Amanda backup. > Now when I run amcheck, I get an error > >"cannot read/write /usr/local/var/Amanda/gnutar-lists: No such file > or directory" > >Indeed there is no such file or directory. My gnutar-lists is > located in /var/lib/Amanda. What shall I do? I am also guessing > that Amanda is going to want read/write other files and folders in > the non-extisting directory. Should I recompile Amanda with some > option specifying the default directory for that type files and > folders? Thanks in advance for any advice. > >Harry. It sounds as if you have a mix-n-match install there. If an rpm, it could be /var/lib/amanda. But the default for building a tarball is /usr/local/whatever. Move your tapelists and the rest of your config stuff to /usr/local/etc/amanda and see if that fixes things by running amcheck (as the user who normally runs amanda, it won't run as root), and fixing any other errors (warnings can be ignored) that pop up. Also do an 'rpm -e amanda*' to get rid of the rpms , they have no business surviving on the system if you have built amanda from a tarball. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: Can't get disklist example to work...
Jeffrey Parker wrote: I can't get the example in the disklist to work for splitting up large disks with gnutar. Like this: ... Gnutar correctly uses the regular expressions, but when it comes to How do you know it correctly uses the regular expressions? actually back them up I get stuff like ? gtar: Cannot stat ./lost+found: No such file or directory (Are you trying to backup with an "include" directive the lost+found directory? Just curious.) ... ? gtar: Cannot add file ./lost+found: No such file or directory | Total bytes written: 10240 These files/directories DO exist! What happened? It's like it's not They do exist where you look, but in the place amanda is looking apparently. Send us your exact disklist entries. backing up in the right place, but it looked there to get the name of the directory. It's like its not cd'ing to the parent directory first. Is there a bug here, or am I not configuring correctly? What do you mean cd'int to the parent directory? gnutar does a cd to the directory you specify as the device (or directory) name. From that directory is never does a cd anywhere, it uses the relative paths from that point. (But ./lost+found is is normal cases a directory only found in top level mount points, so I expect is to be there -- but I would include it in a backup.)
dumps not running in parallel -- why?
I've set up amanda and it runs fine, except I only get one dumper running at any given time. I have eight partitions, two holding disks, and a single HP C1557A tape drive. I have inparallel set to 4 and dumporder set to "sssS". Is there any reason why I have only one dumper running? Jack. -- Jack Twilley jmt at twilley dot org http colon slash slash www dot twilley dot org slash tilde jmt slash pgp0.pgp Description: PGP signature
Re: dumps not running in parallel -- why?
On Wed, 25 Jun 2003 at 2:02pm, Jack Twilley wrote > I've set up amanda and it runs fine, except I only get one dumper > running at any given time. I have eight partitions, two holding > disks, and a single HP C1557A tape drive. I have inparallel set to 4 > and dumporder set to "sssS". Is there any reason why I have only one > dumper running? By default, amanda only runs one dump per client. Increase 'maxdumps' in amanda.conf to change this. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: dumps not running in parallel -- why?
Hi Jack, Jack Twilley wrote: > I've set up amanda and it runs fine, except I only get one dumper > running at any given time. I have eight partitions, two holding > disks, and a single HP C1557A tape drive. I have inparallel set to 4 > and dumporder set to "sssS". Is there any reason why I have only one > dumper running? hmm, i have set "inparallel 8" and also defined 8 "dumporder" characters. never tried what happens if set less dumporder settings than "inparallel". this might be your problem. try and define 8 dumporders. have you set "amflush yes" in your amanda.conf ? Cheers, Peter -- \ Peter Kunst \ CSK Software AG > http://www.csksoftware.com / \ -> Development & \ $WORK: [EMAIL PROTECTED] (+49-69-50952-0) / \ -> Administration \ $HOME: (+49-69-96741687) / \ -> read http://www.faqs.org/rfcs/rfc1855.html before replying /
Re: Backup plan needs advice.
Jon LaBadie wrote:
On Tue, Jun 24, 2003 at 02:25:20PM -0700, bao wrote:
Jon LaBadie wrote:
strategy "string"
...
incronly
Only do incremental dumps. `amadmin force' should
be used to tell Amanda that a full dump has been
performed off-line, so that it resets to level 1.
It is similar to skip-full, but with incronly full
dumps may be scheduled manually. Unfortunately,
it appears that Amanda will perform full backups
with this configuration, which is probably a bug.
Also, another dumptype option entry was this paragraph:
skip-full "boolean"
Default: no. If true and planner has scheduled a full
backup, these disks will be skipped, and full backups
should be run off-line on these days. It was reported
that Amanda only schedules level 1 incrementals in this
configuration; this is probably a bug.
As pointed out. The two paragraphs above have "a bug". I prefer not to
mess with those options. :)
Well, they say "probably". Maybe someone was saying this program/feature
works this way. Probably not only way it could have been designed
and maybe not the best choice for the design -- thus a "bug".
Example, according to the man page for standard unix sort command
has been the line "silently truncates lines longer than bytes".
It could be called a "bug". But in design and implementation,
not a defect in coding.
Plus, the comments may be a holdover from early releases never updated.
There are comments a few years back suggesting the "bug" was fixed.
BTW you could also consider having your "full config" dump to real tape
or to a separate set of "file tapes". Then you could run your daily
config as a normal amanda config doing a mixture of full and incrementals
each day. If you run the full dump to real tape and the clerical person
forgets the tape, it can collect on the holding disk for later amflush.
Otherwise you will have to develop your own procedures for moving the
dumps and the indexes and the ... to tape and later, if needed, you own
procedures for recovering them and the indexes and ... from the tape
for am{recover|restore}.
I have some good news and think I should share it.
With my two configs and with "record yes" in the weekly, the daily
incrementals are able to see
and follow the most recent weekly full backup. That says that Jon's
suggestion of using one config,
inc-only, and forcing a level 0 for the day of the full backup would
also work.
I just tested it with another machine, and will have to wait if anything
unexpected will happen
to the production server.
So going on to investigating how to copy what Amanda needs to tape.
Thanks guys.
Re: help with backup problems please
On Wed, Jun 25, 2003 at 06:46:56PM +, Lucio.yahoo wrote: > The problems: > # amdump DailySet1 > moves the tape for a few seconds, does not give any output on the screen and > it runs way too little time to believe it has written anything on the tape, What is your mailto entry in amanda.conf? You should get an e-mail with error messages and statistics. If you don't get this e-mail ( but mailto seems to be configured) try sending a mail from the backup user to you. amadmin test version | grep MAILER gives you the program amanda tries to execute. /usr/bin/Mail on my server. YMMV To check mail, amcheck -m is fine. -- Alles Gute / best wishes Dietmar Goldbeck E-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
Resend: Strange Dump: Connection reset by peer
I got one response telling me to make sure that the tar was gnu tar. All
that checked out. Any other ideas? I'm really stuck here...
Many Thanks,
-Brian Peterson
-Original Message-
From: Brian G. Peterson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 8:28 AM
I am working on setting up Amanda to back up machines in the DMZ to an
Amanda host on the internal network with a large raid array rather than a
tape drive.
I am running Amanda 2.4.4 compiled from source. My installation was
compiled with the --with-portrange=10085,10090
and --with-udpportrange=850,859
The dump of all volumes that use dump succeeds, both locally and on the
remote server (Amanda client), but the remote dump that uses tar fails while
a local tar dump succeeds.
The Router for the internal network is allowing all TCP and UDP traffic on
ports 10080-10090 and 850-859 through to the Amanda server (this router does
not filter outbound traffic). For testing, the internal iptables firewall
on the Amanda server is off, and the iptables firewall on the DMZ host
(Amanda client) is set to allow all traffic on all ports from the Amanda
server.
Can somebody please give me some pointers on what can cause the connection
reset error? I can't find anything like this via Google or on the Amanda
Faq-o-matic.
Thank you,
- Brian Peterson
FAILURE AND STRANGE DUMP SUMMARY:
ethos.brav hdb1 lev 0 FAILED [mesg read: Connection reset by peer]
FAILED AND STRANGE DUMP DETAILS:
/-- ethos.brav hdb1 lev 0 FAILED [mesg read: Connection reset by peer]
sendbackup: start [ethos.braverock.com:hdb1 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? sed: couldn't write 76 items to {standard output}: Connection timed out
\
Monitoring the dump shows that it gets 55-85% of the way through the dump
before hanging and eventually failing.
Things likely to be relevant from amanda.conf:
tapetype HARD-DISK # what kind of tape it is (see tapetypes below)
tapedev "file:/home/raid/backup/amanda-backup/"
holdingdisk hd1 {
comment "main holding disk"
directory "/home/raid/backup/amanda-backup/holding"
}
reserve 20 # percent
define tapetype HARD-DISK {
comment "hard drive raid array tape simulator"
length 15000 mbytes
}
define dumptype hard-disk-dump {
global
comment "Hard disk backup to RAID array"
holdingdisk yes
priority high
index yes
}
#failed with holdingdisk set to no as well
define dumptype hard-disk-dump-tar {
hard-disk-dump
comment "Hard disk backup to RAID array using gnu tar"
program "GNUTAR"
compress server best
exclude list "/etc/amanda/excludelist"
}
# of note here is that the dump failed with
# compress on the client as well
The disklist looks like this so far:
localhost hdb2 hard-disk-dump
localhost hdb1 hard-disk-dump-tar
ethos.braverock.com hdb1 hard-disk-dump-tar
ethos.braverock.com hda3 hard-disk-dump
ethos.braverock.com hda6 hard-disk-dump
Re: Resend: Strange Dump: Connection reset by peer
On Wed, 25 Jun 2003 at 5:37pm, Brian G. Peterson wrote > I got one response telling me to make sure that the tar was gnu tar. All > that checked out. Any other ideas? I'm really stuck here... What's in the /tmp/amanda/sendbackup*debug on the client corresponding to the failing dump? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Resend: Strange Dump: Connection reset by peer
Thanks. - Brian
Joshua Baker-LePain asks:
> What's in the /tmp/amanda/sendbackup*debug on the client corresponding to
> the failing dump?
Here is the debug output typical of one of the failed hdb1 dumps:
sendbackup.20030623143153.debug:
sendbackup: debug 1 pid 6582 ruid 33 euid 33: start at Mon Jun 23 14:31:53
2003
/usr/lib/amanda/sendbackup: version 2.4.4
parsed request as: program `GNUTAR'
disk `hdb1'
device `hdb1'
level 0
since 1970:1:1:0:0:0
options
`|;auth=bsd;srvcomp-best;index;exclude-list=/etc/amanda/excludelist;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.10090
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.10085
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.10086
sendbackup: time 0.000: waiting for connect on 10090, then 10085, then 10086
sendbackup: time 0.008: stream_accept: connection from 66.92.142.162.33224
sendbackup: time 0.013: stream_accept: connection from 66.92.142.162.33225
sendbackup: time 0.018: stream_accept: connection from 66.92.142.162.33226
sendbackup: time 0.018: got all connections
sendbackup-gnutar: time 0.018: doing level 0 dump as listed-incremental to
/var/lib/amanda/gnutar-lists/ethos.braverock.comhdb1_0.ne
w
amandates botch: hda6 lev 0: new dumpdate 1056177662 old 1056177943
sendbackup-gnutar: time 0.022: doing level 0 dump from date: 1970-01-01
0:00:00 GMT
sendbackup: time 0.024: spawning /usr/lib/amanda/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory
/home --one-file-system --listed-incremental /var/lib/amanda/gnutar-li
sts/ethos.braverock.comhdb1_0.new --sparse --ignore-failed-read --totals --e
xclude-from /tmp/amanda/sendbackup.hdb1.20030623143153.e
xclude .
sendbackup: time 0.030: started index creator: "/bin/tar -tf - 2>/dev/null |
sed -e 's/^\.//'"
sendbackup-gnutar: time 0.031: /usr/lib/amanda/runtar: pid 6585
sendbackup: time 7330.016: 126: strange(?): sed: couldn't write 76 items to
{standard output}: Connection timed out
sendbackup: time 8298.064: index tee cannot write [Connection timed out]
sendbackup: time 8298.064: pid 6584 finish time Mon Jun 23 16:50:11 2003
sendbackup: time 8298.066: 126: strange(?): sendbackup: index tee cannot
write [Connection timed out]
sendbackup: time 8298.068: error [/bin/tar got signal 13]
sendbackup: time 8298.068: pid 6582 finish time Mon Jun 23 16:50:11 2003
and amandad.20030623143153.debug from the same dump for the config
directives if they matter:
amandad: debug 1 pid 6581 ruid 33 euid 33: start at Mon Jun 23 14:31:53 2003
amandad: version 2.4.4
amandad: build: VERSION="Amanda-2.4.4"
amandad:BUILT_DATE="Sat Jun 21 02:12:08 CDT 2003"
amandad:BUILT_MACH="Linux candy.braverock.com 2.4.20-18.8 #1 Thu May
29 07:20:39 EDT 2003 i686 athlon i386 GNU/Linux"
amandad:CC="gcc"
amandad:CONFIGURE_COMMAND="'./configure' '--host=i686-pc-linux-gnu'
'--build=i686-pc-linux-gnu' '--target=i386-redhat-linux-
gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr'
'--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datad
ir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib'
'--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--sharedst
atedir=/usr/com' '--mandir=/usr/share/man' '--infodir=/usr/share/info'
'--enable-shared' '--with-index-server=localhost' '--with-gnu
tar-listdir=/var/lib/amanda/gnutar-lists'
'--with-smbclient=/usr/bin/smbclient' '--with-amandahosts'
'--with-user=amanda' '--with-gr
oup=disk' '--with-gnutar=/bin/tar' '--with-udpportrange=850,859'
'--with-portrange=10085,10090'"
amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin"
amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip"
amandad:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists"
amandad: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="localhost"
amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: time 0.000: got packet:
Amanda 2.4 REQ HANDLE 000-B8D10608 SEQ 1056396653
SECURITY USER amanda
SERVICE sendbackup
OPTIONS features=feff9ffe0f;h
Re: Resend: Strange Dump: Connection reset by peer
On Wednesday 25 June 2003 18:37, Brian G. Peterson wrote:
>I got one response telling me to make sure that the tar was gnu tar.
> All that checked out. Any other ideas? I'm really stuck here...
Perchance have you got another older version of tar thats found first
in the $PATH? Do a 'which tar' and see if that is the same one you
checked. On the client of course.
>Many Thanks,
>
> -Brian Peterson
>
>-Original Message-
From: Brian G. Peterson [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, June 24, 2003 8:28 AM
>
>I am working on setting up Amanda to back up machines in the DMZ to
> an Amanda host on the internal network with a large raid array
> rather than a tape drive.
>
>I am running Amanda 2.4.4 compiled from source. My installation was
>compiled with the --with-portrange=10085,10090
>and --with-udpportrange=850,859
>
>The dump of all volumes that use dump succeeds, both locally and on
> the remote server (Amanda client), but the remote dump that uses
> tar fails while a local tar dump succeeds.
>
>The Router for the internal network is allowing all TCP and UDP
> traffic on ports 10080-10090 and 850-859 through to the Amanda
> server (this router does not filter outbound traffic). For
> testing, the internal iptables firewall on the Amanda server is
> off, and the iptables firewall on the DMZ host (Amanda client) is
> set to allow all traffic on all ports from the Amanda server.
>
>Can somebody please give me some pointers on what can cause the
> connection reset error? I can't find anything like this via Google
> or on the Amanda Faq-o-matic.
>
>Thank you,
>
> - Brian Peterson
>
>FAILURE AND STRANGE DUMP SUMMARY:
> ethos.brav hdb1 lev 0 FAILED [mesg read: Connection reset by peer]
>
>FAILED AND STRANGE DUMP DETAILS:
>
>/-- ethos.brav hdb1 lev 0 FAILED [mesg read: Connection reset by
> peer] sendbackup: start [ethos.braverock.com:hdb1 level 0]
>sendbackup: info BACKUP=/bin/tar
>sendbackup: info RECOVER_CMD=/bin/tar -f... -
>sendbackup: info end
>? sed: couldn't write 76 items to {standard output}: Connection
> timed out \
>
>Monitoring the dump shows that it gets 55-85% of the way through the
> dump before hanging and eventually failing.
>
>Things likely to be relevant from amanda.conf:
>
>tapetype HARD-DISK # what kind of tape it is (see tapetypes
> below) tapedev "file:/home/raid/backup/amanda-backup/"
>
>holdingdisk hd1 {
>comment "main holding disk"
>directory "/home/raid/backup/amanda-backup/holding"
>}
>
>reserve 20 # percent
>
>define tapetype HARD-DISK {
>comment "hard drive raid array tape simulator"
>length 15000 mbytes
>}
>
>define dumptype hard-disk-dump {
>global
>comment "Hard disk backup to RAID array"
>holdingdisk yes
>priority high
>index yes
>}
>#failed with holdingdisk set to no as well
>
>define dumptype hard-disk-dump-tar {
>hard-disk-dump
>comment "Hard disk backup to RAID array using gnu tar"
>program "GNUTAR"
>compress server best
>exclude list "/etc/amanda/excludelist"
>}
># of note here is that the dump failed with
># compress on the client as well
>
>The disklist looks like this so far:
>localhost hdb2 hard-disk-dump
>localhost hdb1 hard-disk-dump-tar
>ethos.braverock.com hdb1 hard-disk-dump-tar
>ethos.braverock.com hda3 hard-disk-dump
>ethos.braverock.com hda6 hard-disk-dump
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
RE: Resend: Strange Dump: Connection reset by peer
> On Wednesday 25 June 2003 18:37, Brian G. Peterson wrote: > >I got one response telling me to make sure that the tar was gnu tar. > > All that checked out. Any other ideas? I'm really stuck here... > > Perchance have you got another older version of tar that's found first > in the $PATH? Do a 'which tar' and see if that is the same one you > checked. On the client of course. The only tar binaries on the system (in /bin/tar and /home/ftp/bin/tar) are: tar --version tar (GNU tar) 1.13.25 Copyright C 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. So, it doesn't look like that is the problem. There is only one copy of the sed binary, and it is a recent gnu sed as well. Perhaps someone will see something useful in the .debug output I sent to the list earlier. - Brian
Re: help with backup problems please
> You should get an e-mail with error messages and statistics.
Here is the mail I receive (mailto "root"), but, to be honest, it doesn't help
me very much...
>From [EMAIL PROTECTED] Thu Jun 26 08:11:16 2003
Date: Thu, 26 Jun 2003 08:11:15 +0200
From: root <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: MyOrg AMANDA MAIL REPORT FOR June 26, 2003
These dumps were to tape DailySet1n4.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
planner: ERROR Request to localhost timed out.
localhost /dev/md0 RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
^L
NOTES:
planner: Adding new disk localhost:/dev/md0.
driver: WARNING: got empty schedule from planner
taper: tape DailySet1n4 kb 0 fm 0 [OK]
^L
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
localhost/dev/md0 MISSING --
(brought to you by Amanda version 2.4.3)
Re: Resend: Strange Dump: Connection reset by peer
On Wed, Jun 25, 2003 at 06:04:23PM -0500, Brian G. Peterson wrote:
> amandates botch: hda6 lev 0: new dumpdate 1056177662 old 1056177943
> sendbackup-gnutar: time 0.022: doing level 0 dump from date: 1970-01-01
> 0:00:00 GMT
> sendbackup: time 0.024: spawning /usr/lib/amanda/runtar in pipeline
> sendbackup: argument list: gtar --create --file - --directory
> /home --one-file-system --listed-incremental /var/lib/amanda/gnutar-li
> sts/ethos.braverock.comhdb1_0.new --sparse --ignore-failed-read --totals --e
> xclude-from /tmp/amanda/sendbackup.hdb1.20030623143153.e
> xclude .
> sendbackup: time 0.030: started index creator: "/bin/tar -tf - 2>/dev/null |
> sed -e 's/^\.//'"
> sendbackup-gnutar: time 0.031: /usr/lib/amanda/runtar: pid 6585
> sendbackup: time 7330.016: 126: strange(?): sed: couldn't write 76 items to
> {standard output}: Connection timed out
> sendbackup: time 8298.064: index tee cannot write [Connection timed out]
gtar takes a long time to finish the first pass (checking directories
against listed incremental file).
My guess is that the tcp connections are timed out on the iptables firewall.
You can check this by putting some small and really small directories into
your disklist. Please add e.g. /etc, /bin and /lib to your disklist
and check if those can be backed up.
Please make sure, all of your filtering is logging discarded packets.
Ciao
Dietmar
--
Alles Gute / best wishes
Dietmar Goldbeck E-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization? Gandhi: I think it would be a good idea.
Re: help with backup problems please
> What does 'amcheck DailySet1' say? Amanda Tape Server Host Check - Holding disk /var/tmp: 30819288 KB disk space available, using 25576408 KB NOTE: skipping tape-writable test Tape DailySet1n4 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist Server check took 8.201 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 29.995 seconds, 1 problem found (brought to you by Amanda 2.4.3) Wow! It has found a problem on the client host (wich is phisically the server, btw). But, why this problem? What am I missing? > > How about 'amstatus DailySet1 --file logdir/amdump.1'? (where ever > your "logdir" is...) > # amstatus DailySet1 --file /var/lib/amanda/DailySet1 Using /var/lib/amanda/DailySet1 SUMMARY part real estimated size size partition : 0 estimated : 0 0k flush : 00k failed : 0 0k ( 0.00%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 0 0k ( 0.00%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 00k0k ( 0.00%) ( 0.00%) wait for writing: 00k0k ( 0.00%) ( 0.00%) wait to flush : 00k0k (100.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 00k0k ( 0.00%) ( 0.00%) all dumpers active taper idle Can you see anything strange here? > How about 'amreport DailySet1 -l logdir/log.20030625.0 -f /tmp/foo' > (again, logdir and whatever the appropriate logfile name is). Please refer to my reply to Dietmar Goldbeck for this. > > How about /tmp/amanda/* on the client and server? *** amtrmidx.debug *** could not open index directory "/var/lib/amanda/DailySet1/index/localhost/_dev_md0/"amtrmidx: pid 4997 # The first missing subdir is localhost There are lots of other debug files down there, I've checked only a few but the one above seems the only interesting one (along with the others from the same process).
