Re: selfcheck request timeout on MP-RAS
>I did a reboot on the MP-RAS box to start with a clean slate and here is >what I've found so far. >... >WARNING: edaf6.irs.sat: selfcheck request timed out. Host down? >... >(brought to you by Amanda 2.4.3b1) >... >SERVICE selfcheck >OPTIONS ; >GNUTAR /home/tp 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; >GNUTAR /eec/msg/logs 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; >GNUTAR /eec/data/test 0 OPTIONS >|;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; >GNUTAR /eec/var/inf_dumps 0 OPTIONS >|;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; >GNUTAR /eec/var/inf_archive 0 OPTIONS >|;bsd-auth;srvcomp-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; >GNUTAR /eec/var 0 OPTIONS >|;bsd-auth;srvcomp-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; >GNUTAR /eec 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; >... This is a normal looking selfcheck packet, asking it to verify that things look OK for those file systems (or directories) using GNU tar as the dump program. So far, so good. The rest of the amandad log, however, indicates selfcheck is not getting done (and amcheck on the other side is re-sending the packets). ># cat selfcheck.20020321121249.debug >... >selfcheck: debug 1 pid 3459 ruid 22234 euid 22234 start time Thu Mar 21 12:12:49 2002 >/usr/local/libexec/selfcheck: version 2.4.3b2-20020308 >selfcheck: exclude list file "/home/tp/exclude.txt" does not exist, ignoring >selfcheck: checking disk /home/tp >selfcheck: device /home/tp >selfcheck: OK >selfcheck: exclude list file "/eec/msg/logs/exclude.txt" does not exist, ignoring >selfcheck: checking disk /eec/msg/logs >selfcheck: device /eec/msg/logs >selfcheck: OK >selfcheck: exclude list file "/eec/data/test/exclude.txt" does not exist, ignoring >selfcheck: checking disk /eec/data/test >selfcheck: device /eec/data/test >selfcheck: OK >selfcheck: exclude list file "/eec/var/inf_dumps/exclude.txt" does not exist, ignoring >selfcheck: checking disk /eec/var/inf_dumps >selfcheck: device /eec/var/inf_dumps >selfcheck: OK This also looks normal, as far as it goes. >selfcheck was still running or is hung after results returned to "relay" ># ps -ef | grep selfcheck > amanda 3459 3458 66 12:12:49 ? 10:05 /usr/local/libexec/selfcheck But the fact that it is still running, and that the log file did not go beyond /eec/var/inf_dumps, is bad. It's also probably not a good sign that it has used 10 minutes of time -- selfcheck should be done almost immediately. You can kill off the selfcheck process (if you can). It's obviously hung. >I'm assuming it has something to do with this oddly named file of 0 bytes: >selfcheck._eec_var_inf__archive.20020321121250.exclude Those are (new with 2.4.3) temp files used to hold the merged exclusion patterns. Note that /eec/var/inf_dumps was the first file system to use an explicit exclude file, "/usr/local/lib/amanda/exclude.gtar". Based on the log messages and the presence of the temp file, we can deduce that Amanda detected the existance of the exclude file and was trying to copy it to the temp file. Is there anything "magic" about access to that file on the MP-RAS box that would prevent Amanda from being able to read it? Can you "cat" it, for instance? If you (temporarily) comment out /eec/var/inf_archive and /eec/var from your disklist (both of which try to use that exclude file), does amcheck work? >Brian Davidson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Make problem on Solaris 2.8
>But now that you mention it, I suspect that >for Solaris we should add "-R$dir" in addition to "-L$dir". Right? Yep. I *think* a space is necessary after the R, but could be wrong. >Not long ago I discovered Amanda had a --with-libraries option that >took a list of directories and stuck them on the load lines with "-L" Does that make it into the invocations done within configure? I find that feature tests, like finding jpeg/gtk/imlib usually fail for me because configure finds the libs and links with them, but doesn't link with -R, so the resultant test executable doesn't run.
Re: Make problem on Solaris 2.8
>This is why linking with -R is the better answer. ... Absolutely. LD_LIBRARY_PATH has a lot of really evil side effects and should be an absolute last resort. >And, of course, most or all instances of 'configure' that I encounter >fail completely ... That's interesting. Not long ago I discovered Amanda had a --with-libraries option that took a list of directories and stuck them on the load lines with "-L" (it also has a --with-includes along the same line). I was kind of happy because this was easier than what I had been doing (via an LD_FLAGS environment variable, as I recall). Since I didn't have any shared libraries in the extra areas, I didn't really think about it much. But now that you mention it, I suspect that for Solaris we should add "-R$dir" in addition to "-L$dir". Right? Are there any other OS's that need "-R"? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover: error reading tape: Connection reset by peer
>-> i have to launch "/usr/local/sbin/amrecover -d /dev/rmt/0" instead of >"/usr/local/sbin/amrecover DailySet1" One point -- you should use a non-rewinding device name for anything you do with Amanda. So that should be "-d /dev/rmt/0n". Also, I'm guessing, based on the device name, that you're running on Solaris. Your original report mentioned /dev/rmt/0bn. Don't use the BSD names (the ones with 'b' in them). Those process tapes in a slightly different way than the default (no 'b') System V way that Amanda (more or less) expects. >Sorry for annoying. I just post my solution in hope it helps some. You haven't been annoying at all (far from it). And I, at least, really appreciate hearing that a problem got resolved, and what it took to make it work. As you said, there is always the hope that what you found will help someone else later. >Lorenzo John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Confusion on Dumps & Configuration
Joshua, Paul and Mark gave you good advice. I just have one point to add: > In my disklist file, I've tried to do the following: > >localhost /dev/sdacomp-high Don't use "localhost". Amanda stores indexing information based on the host name (among other things). Even if you think it will never happen, if you have to change your tape server machine to another box, the name "localhost" will likely be wrong all of the sudden. Strong suggestion is to use a fully qualified domain name. >Mark John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amflush and irc?
>On one hand, I have been thinking about running amanda once a week for >totals directly to tape, and the rest of weekdays without tapes so >incrementals are sent to holding disk, and then before next total on >friday with tapes, I do amflush... FYI, 2.4.3 (now in beta testing) has an "autoflush" parameter that will do the flush for you as part of the normal run. Normally you would have to use one tape for the amflush and one for the amdump. If you don't have all that much data, you might get by with just one tape for both (but only if you use 2.4.3). >... Also, with amflush, will indexes be maintained without >any trouble? So index server finds stuff as if they were on separated tapes. It will work fine. A datestamp is associated with the amdump (not the amflush) and maintained as part of the index and used during a restore. Even though you'll have several backup images of each file system on the flush tape, they will have unique datestamps. And if you do a restore before the amflush, amrecover will find the images in your holding disk and use them directly from there, without any tape needed. Also, Jon LaBadie is correct that Amanda tries to balance the amount of tape used for each run, not maximize it. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: can't update dumpdates
Excellent! Thanks. Can't see the forest for the trees. On Thu, 21 Mar 2002, Joshua Baker-LePain wrote: > On Thu, 21 Mar 2002 at 10:22am, [EMAIL PROTECTED] wrote > > > I'd like your insight into why I'm getting this error message > > when dumping various disks: > > > > > | DUMP: You can't update the dumpdates file when dumping a subdirectory > > That's why. You're using dump, and trying to dump something that isn't a > filesystem. To do that you, must use tar. > > -- John Rodkey, Information Technology, Westmont College [EMAIL PROTECTED]
RE: Confusion on Dumps & Configuration
Sometimes 'dump' is one run of amdump, sometimes it is the 'dump' utility that makes a backup of a filesystem. The number of filesystems that fit on a tape will vary by their size and compressability. Your bump factors in amanda.conf will also affect it. Levels are degrees of incremental-ness in Amanda. Level 0 is a full backup. Level 1 is everything that changed since the last level 0. Level 2 is everything that changed since the last level 1. This goes on to level 9. Amanda automatically picks the 'best' level to use for each file system based on a bunch of things, including how often you want full backups (dumpcycle), how much a backup of each file system will take at each level, and how compressible that backup is likely to be, based on historical records. Your best bet for tape fitting is usually to add file systems gradually over several amdump runs, so that the initial level 0 for each new filesystem can be fit on the tape, bumping existing filesystems to level 1 or lower to make room if needed. I like to add the biggest file systems first, but that's me. > -Original Message- > From: Mark Schoonover [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 21, 2002 3:51 PM > To: 'Joshua Baker-LePain'; Mark Schoonover; 'Jenn Sturm'; 'Bort, Paul' > Cc: Amanda-User (E-mail) > Subject: RE: Confusion on Dumps & Configuration > > > Josh, Jenn & Paul, > > Thanks for the quick replies! I have found the error of my ways, > which leads me to a few more questions! The way I understand > it is a 'dump' > is one cron job of amdump running. OK no problem there. Now, how do I > estimate how many filesystems I can backup to a single tape?? > Trial and > error?? Not sure what a level 0 is offhand. The best I can > figure out on my > own is an entire dump of all filesystems in one run. Josh, > can I bother you > for a copy of your tapetype?? > > Thanks again! > > .mark >
RE: Confusion on Dumps & Configuration
On Thu, 21 Mar 2002 at 12:50pm, Mark Schoonover wrote
> Thanks for the quick replies! I have found the error of my ways,
> which leads me to a few more questions! The way I understand it is a 'dump'
> is one cron job of amdump running. OK no problem there. Now, how do I
> estimate how many filesystems I can backup to a single tape?? Trial and
> error?? Not sure what a level 0 is offhand. The best I can figure out on my
> own is an entire dump of all filesystems in one run. Josh, can I bother you
> for a copy of your tapetype??
A level 0 is a full dump of a filesystem. For example:
[jlb@chaos jlb]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda1 248895 95924140121 41% /
.
.
.
If I had a disklist entry "chaos / $DUMPTYPE", then a level 0 would take
up ~95MB. A level 1 (i.e. an incremental) the next day would only backup
what had changed between the time the level 1 was run and the time of the
last level 0.
So, to estimate how many level 0s will fit on a tape, just use df (or du)
to find the size of your disklist entries and add them up. Also,
remember that, after a while, amanda will balance full backups throughout
the dumpcycle (filling the rest of the tape with incrementals). This is
what allows you to backup an amount of data larger than your tapes.
Here's my tapetype for an Eliant 820 using XL tapes:
define tapetype Eliant-820 {
comment "just produced by tapetype program"
length 6680 mbytes
filemark 0 kbytes
speed 949 kps
}
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
RE: Confusion on Dumps & Configuration
Josh, Jenn & Paul, Thanks for the quick replies! I have found the error of my ways, which leads me to a few more questions! The way I understand it is a 'dump' is one cron job of amdump running. OK no problem there. Now, how do I estimate how many filesystems I can backup to a single tape?? Trial and error?? Not sure what a level 0 is offhand. The best I can figure out on my own is an entire dump of all filesystems in one run. Josh, can I bother you for a copy of your tapetype?? Thanks again! .mark
RE: amflush and irc?
It depends on how often you require full backups. I was getting really low tape utilization and big swings in amadmin 'balance' results, so I cut my dumpcycle and runspercycle in half, and now I get more consistent tape usage, and level 0 backups twice as often as a side benefit. Amanda's tape fill planning degrades gracefully when there is excess tape, nothing to worry about, but it still degrades. > -Original Message- > From: Jon LaBadie [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 21, 2002 2:30 PM > To: [EMAIL PROTECTED] > Subject: Re: amflush and irc? > > > On Thu, Mar 21, 2002 at 12:16:10PM -0600, Brandon D. Valentine wrote: > > On Thu, 21 Mar 2002, Jon LaBadie wrote: > > > > >You won't. After running a while amanda will spread the > level 0's over > > >all the dump days. So if your once a week tape "now" gets > 40GB and your > > >daily "incrementals" now get 2, each will average about 8 GB daily. > > > > Actually it's even better than that. Each tape should > average a full > > 40GB. Amanda will do its best to fill each and every tape > to capacity, > > promoting as many full dumps per run as possible. If you > have 40GB of > > data and a 40GB tape drive, you should get a full set of level 0s on > > every run. > > YMMV, but that has not been my experience. > > My tapes are 12GB (dds3) and although I have about 50GB > (data precompression, not disk) to back up, my nightly > tape usage is about 7GB. > > I thought the planner attempted to get a consistant > nightly backup, not a filled-tape backup. Our differing > observations may be the result of different amanda.conf settings. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) >
Re: amrecover is kicking my butt......
On Mon, Mar 18, 2002 at 04:21:22PM -0500, Don Potter wrote: > Thanks Jean...your idea works great..why hasn't this been > incorporated previously by chance Because nobody reported this problem :-) Jean-Louis > > Jean-Louis Martineau wrote: > > > >> Hi Don, > >> > >> Try this patch on the client, it makes a stricker pattern by enclosing > >> it in ^$ > >> -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amflush and irc?
On Thu, Mar 21, 2002 at 12:16:10PM -0600, Brandon D. Valentine wrote: > On Thu, 21 Mar 2002, Jon LaBadie wrote: > > >You won't. After running a while amanda will spread the level 0's over > >all the dump days. So if your once a week tape "now" gets 40GB and your > >daily "incrementals" now get 2, each will average about 8 GB daily. > > Actually it's even better than that. Each tape should average a full > 40GB. Amanda will do its best to fill each and every tape to capacity, > promoting as many full dumps per run as possible. If you have 40GB of > data and a 40GB tape drive, you should get a full set of level 0s on > every run. YMMV, but that has not been my experience. My tapes are 12GB (dds3) and although I have about 50GB (data precompression, not disk) to back up, my nightly tape usage is about 7GB. I thought the planner attempted to get a consistant nightly backup, not a filled-tape backup. Our differing observations may be the result of different amanda.conf settings. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Confusion on Dumps & Configuration
Mark,
You're touching on several different parts of Amanda here, so I'll try to
answer all of them separately:
1. You have to specify /dev/sda1 instead of /dev/sda because Amanda is
backing up a file system (aka partition), not a physical disk. You should
list each file system you wish to back up as a line in disklist. This allows
Amanda to back up file systems that are remote (NFS) or virtual
(//ntserver/share), or parts of file systems that are too big for one tape
(/home/ftp/public/mspatches).
2. I'm using EXB-8505 drives, I wouldn't worry about space, Amanda will use
it as best she can.
3. To use the second drive, you will need to use the 'chg-multi' tape
changer configuration. If you search the mailing list archives for
'chg-multi' and check out the FAQ-O-Matic, there will be more info (I don't
have any more, because I don't use it here.) Amanda will handle EOT cleanly
by redoing the partition that was interrupted by EOT on the next tape. You
will also need to change the 'runtapes' parameter in amanda.conf to specify
that you're using up to two tapes per backup. I would recommend getting your
disk list straight and doing manual changes before messing with changers.
Good Luck!
> -Original Message-
> From: Mark Schoonover [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 21, 2002 1:53 PM
> To: Amanda-User (E-mail)
> Subject: Confusion on Dumps & Configuration
>
>
> Thanks for Reading!!
>
> I am having some difficulties on understanding dumps. I'm coming
> from an Arkeia and ArcServe background and some of the terminology is
> confusing me. My question is, how do I configure the disklist
> file so I
> don't hit EOT?? Am I on the right track here, or totally
> off?? Here's my
> setup:
>
> RH 7.2 with approx 180 GB of disk space available, with about
> 25 GB used.
> Two Exabyte Eliant 820s tape drives that are 8 GB native. ( I
> know, get
> bigger drives!! I will... )
>
> Mount list:
>
> /dev/sda5 on / type ext3 (rw)
> none on /proc type proc (rw)
> usbdevfs on /proc/bus/usb type usbdevfs (rw)
> /dev/sda1 on /boot type ext3 (rw)
> /dev/sdb2 on /data type ext3 (rw)
> none on /dev/pts type devpts (rw,gid=5,mode=620)
> /dev/sdb1 on /home type ext3 (rw)
> none on /dev/shm type tmpfs (rw)
> /dev/sda2 on /usr type ext3 (rw)
> /dev/sda6 on /var type ext3 (rw)
> /dev/cdrom on /mnt/cdrom type iso9660 (ro)
>
> In my disklist file, I've tried to do the following:
>
> localhost /dev/sdacomp-high
>
> When I run amdump from the command line, it always reports that
> /dev/sda is offline. When I put sda1, it works just fine. Yes
> the amanda
> user is in the disk group and that group has read access to
> the device. The
> last thing I'm confused on right now is how to use my second
> tape drive.
> What I'd like to do is when the first one finishes, Amanda
> will run another
> dump to the second drive.
>
> If there's other info you need, just ask and I will provide.
>
> Mark
>
> --{ Mark E Schoonover KA6WKE
> --{ Senior Hacker, IS Gopher, Hardware Fiend
> --{ American Geotechnical
> --{ http://www.qsl.net/ka6wke
> --{ [EMAIL PROTECTED]
>
>
>
>
>
>
Re: Confusion on Dumps & Configuration
On Thu, 21 Mar 2002 at 10:53am, Mark Schoonover wrote > RH 7.2 with approx 180 GB of disk space available, with about 25 GB used. > Two Exabyte Eliant 820s tape drives that are 8 GB native. ( I know, get > bigger drives!! I will... ) 7GB native using 160mXL tapes -- that's what I use. 25GB used is not a problem. But... > Mount list: > > /dev/sda5 on / type ext3 (rw) > none on /proc type proc (rw) > usbdevfs on /proc/bus/usb type usbdevfs (rw) > /dev/sda1 on /boot type ext3 (rw) > /dev/sdb2 on /data type ext3 (rw) > none on /dev/pts type devpts (rw,gid=5,mode=620) > /dev/sdb1 on /home type ext3 (rw) > none on /dev/shm type tmpfs (rw) > /dev/sda2 on /usr type ext3 (rw) > /dev/sda6 on /var type ext3 (rw) > /dev/cdrom on /mnt/cdrom type iso9660 (ro) > > In my disklist file, I've tried to do the following: > > localhost /dev/sdacomp-high Here's the first thing you must understand -- amanda basically schedules and coordinates backups. It doesn't actually get the bits off the platters. To do that it relies either on dump or tar. dump can be used only on partitions (sda1 (or /boot), sda5 (or /), etc in the above). tar can be used on any directory whether or not it is it's own partition (e.g. /home or /home/user1, /home/user2, etc). Neither dump nor tar can directly back up the raw sda device. To get your 25GB backed up (even with only one drive), you split your physical disks into a number of disklist entries. After getting an initial level 0 of all your filesystems, amanda will attempt to balance the dumps, spreading level 0s throughout the dumpcycle as needed. To use more than one drive in one config (although you really don't need to with only 25GB used), you need to use chg-multi as your "tape changer". -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Confusion on Dumps & Configuration
Thanks for Reading!!
I am having some difficulties on understanding dumps. I'm coming
from an Arkeia and ArcServe background and some of the terminology is
confusing me. My question is, how do I configure the disklist file so I
don't hit EOT?? Am I on the right track here, or totally off?? Here's my
setup:
RH 7.2 with approx 180 GB of disk space available, with about 25 GB used.
Two Exabyte Eliant 820s tape drives that are 8 GB native. ( I know, get
bigger drives!! I will... )
Mount list:
/dev/sda5 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/sda1 on /boot type ext3 (rw)
/dev/sdb2 on /data type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sdb1 on /home type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda2 on /usr type ext3 (rw)
/dev/sda6 on /var type ext3 (rw)
/dev/cdrom on /mnt/cdrom type iso9660 (ro)
In my disklist file, I've tried to do the following:
localhost /dev/sdacomp-high
When I run amdump from the command line, it always reports that
/dev/sda is offline. When I put sda1, it works just fine. Yes the amanda
user is in the disk group and that group has read access to the device. The
last thing I'm confused on right now is how to use my second tape drive.
What I'd like to do is when the first one finishes, Amanda will run another
dump to the second drive.
If there's other info you need, just ask and I will provide.
Mark
--{ Mark E Schoonover KA6WKE
--{ Senior Hacker, IS Gopher, Hardware Fiend
--{ American Geotechnical
--{ http://www.qsl.net/ka6wke
--{ [EMAIL PROTECTED]
Re: can't update dumpdates
On Thu, 21 Mar 2002 at 10:22am, [EMAIL PROTECTED] wrote > I'd like your insight into why I'm getting this error message > when dumping various disks: > > > | DUMP: You can't update the dumpdates file when dumping a subdirectory That's why. You're using dump, and trying to dump something that isn't a filesystem. To do that you, must use tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
can't update dumpdates
I'd like your insight into why I'm getting this error message when dumping various disks: > /-- ahab /var/spool/mail lev 0 FAILED [/sbin/dump returned 1] > sendbackup: start [ahab:/var/spool/mail level 0] > sendbackup: info BACKUP=/sbin/dump > sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/sbin/restore -f... - > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > | DUMP: You can't update the dumpdates file when dumping a subdirectory > | DUMP: The ENTIRE dump is aborted. > sendbackup: error [/sbin/dump returned 1] TIA John -- John Rodkey, Information Technology, Westmont College [EMAIL PROTECTED]
Re: amflush and irc?
On Thu, 21 Mar 2002, Jon LaBadie wrote: >You won't. After running a while amanda will spread the level 0's over >all the dump days. So if your once a week tape "now" gets 40GB and your >daily "incrementals" now get 2, each will average about 8 GB daily. Actually it's even better than that. Each tape should average a full 40GB. Amanda will do its best to fill each and every tape to capacity, promoting as many full dumps per run as possible. If you have 40GB of data and a 40GB tape drive, you should get a full set of level 0s on every run. If you have 60GB of data and a 40GB tape drive you should see a full dump of everything every 2 days, with incrementals in between, etc. It's really cool. >Some might suggest that if you can't justify the expense of tapes >then the value/cost of losing the data must be low. That's a valid point to consider. Also worth noting is that if you are concerned about raw $/GB in terms of tape you can't go wrong with DAT-based formats. They may not be the most advanced, robust tape technologies out there, but DDS ain't bad and the media sure is cheap. We use AIT at work but I use DDS3 for all of my personal backups at home (I also use amdump as my alarm clock each morning, as soon as that thing starts taping I find I can no longer sleep ;-). -- Brandon D. Valentine <[EMAIL PROTECTED]> Computer Geek, Center for Structural Biology "This isn't rocket science -- but it _is_ computer science." - Terry Lambert on [EMAIL PROTECTED]
selfcheck request timeout on MP-RAS
I did a reboot on the MP-RAS box to start with a clean slate and here is what I've found so far. amcheck results from tape server (relay): relay# su amanda -c "/usr/local/sbin/amcheck tig" Amanda Tape Server Host Check - Holding disk /amanda/hold: 17953520 KB disk space available, using 17943280 KB NOTE: skipping tape-writable test Tape Daily_02 label ok Server check took 0.204 seconds Amanda Backup Client Hosts Check WARNING: edaf6.irs.sat: selfcheck request timed out. Host down? Client check: 5 hosts checked in 540.997 seconds, 1 problem found (brought to you by Amanda 2.4.3b1) relay# ls of /tmp/amanda on edaf6: # ls -al total 16 drwx--l--- 2 amanda operator 512 Mar 21 12:12 . drwxrwxrwt 4 sys sys 512 Mar 21 12:20 .. -rw--- 1 amanda operator4512 Mar 21 12:18 amandad.20020321121249.debug -rw--- 1 amanda operator 812 Mar 21 12:12 selfcheck.20020321121249.debug -rw--- 1 amanda operator 0 Mar 21 12:12 selfcheck._eec_var_inf__archive.20020321121250.exclude output from amandad.xxx.debug: # cat amandad.20020321121249.debug amandad: debug 1 pid 3458 ruid 22234 euid 22234 start time Thu Mar 21 12:12:49 2002 amandad: version 2.4.3b2-20020308 amandad: build: VERSION="Amanda-2.4.3b2-20020308" amandad:BUILT_DATE="Wed Mar 13 14:27:03 EST 2002" amandad:BUILT_MACH="UNIX_SV edaf6 4.0 3.0 3360,3430-R Pentium(TM)-MCA " amandad:CC="cc" amandad:CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=operator' '--without-server' '--without-restore' '--with-gnutar=/usr/bin/tar'" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" amandad:RESTORE="/usr/sbin/ufsrestore" amandad:VXDUMP="/usr/lib/fs/vxfs/vxdump" amandad:VXRESTORE="/usr/lib/fs/vxfs/vxrestore" amandad:GNUTAR="/usr/bin/tar" COMPRESS_PATH="/usr/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/mailx" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="edaf6" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="edaf6" 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" got packet: Amanda 2.4 REQ HANDLE 004-004B0D08 SEQ 1016730917 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR /home/tp 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/msg/logs 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/data/test 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/var/inf_dumps 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/var/inf_archive 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gta r; GNUTAR /eec/var 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gta r; GNUTAR /eec 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; sending ack: Amanda 2.4 ACK HANDLE 004-004B0D08 SEQ 1016730917 bsd security: remote host relay.irs.sat user amanda local user amanda amandahosts security check passed amandad: running service "/usr/local/libexec/selfcheck" amandad: got packet: Amanda 2.4 REQ HANDLE 004-004B0D08 SEQ 1016730917 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR /home/tp 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/msg/logs 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/data/test 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/var/inf_dumps 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; GNUTAR /eec/var/inf_archive 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gta r; GNUTAR /eec/var 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gta r; GNUTAR /eec 0 OPTIONS |;bsd-auth;srvcomp-fast;index;exclude-list=exclude.txt; --
RE: amrecover: error reading tape: Connection reset by peer
Hi, Ok i just find the problem : -> in the ined.conf the user amanda was not well write -> i have to launch "/usr/local/sbin/amrecover -d /dev/rmt/0" instead of "/usr/local/sbin/amrecover DailySet1" Sorry for annoying. I just post my solution in hope it helps some. Bye Lorenzo
Re: amrecover: error reading tape: Connection reset by peer
Just a reminder. Did you put the required tape in the drive? amrecover does NOT load the tape automatically. Mark - Original Message - From: "Laurent Morin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 21, 2002 11:51 AM Subject: amrecover: error reading tape: Connection reset by peer > Hi, > > I successfuly backup files to my DLT (thanks the FAQ ;-) > When I want to restore, i got an problem : > > amrecover: error reading tape: Connection reset by peer > extract_list - child returned non-zero status: 1 > > PS : I use Sparc/Solaris8 + Amanda version 2.4.2p2 + gtar1.13.19 > > Can someone have an idea to help me ? > > Thanks in advance. > Regards > > Lorenzo > > PS : here the sequence : > -- > amrecover> pwd > /export/home/lorenzo/test > amrecover> list > amrecover> add fic1 > Added /fic1 > amrecover> extract > > Extracting files using tape drive /dev/rmt/0bn on host babylone. > The following tapes are needed: DailySet101 > > Restoring files into directory /export/home/lorenzo/test > Continue? [Y/n]: > > Load tape DailySet101 now > Continue? [Y/n]: > amrecover: error reading tape: Connection reset by peer > extract_list - child returned non-zero status: 1 > Continue? [Y/n]: > amrecover> quit > -- > > >
Re: amflush and irc?
On Thu, Mar 21, 2002 at 05:45:58PM +0100, Juanjo wrote: > Hello, > > Two things; > > On one hand, I have been thinking about running amanda once a week for > totals directly to tape, and the rest of weekdays without tapes so > incrementals are sent to holding disk, and then before next total on > friday with tapes, I do amflush... > > Would that work nicely? I ask cause seems that amanda balances the backup > on her own, but I cannot spend expensive DLT40/80 tapes with 2 gigs of > incrementals only. You won't. After running a while amanda will spread the level 0's over all the dump days. So if your once a week tape "now" gets 40GB and your daily "incrementals" now get 2, each will average about 8 GB daily. Some might suggest that if you can't justify the expense of tapes then the value/cost of losing the data must be low. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amrecover: error reading tape: Connection reset by peer
Hi, I successfuly backup files to my DLT (thanks the FAQ ;-) When I want to restore, i got an problem : amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 PS : I use Sparc/Solaris8 + Amanda version 2.4.2p2 + gtar1.13.19 Can someone have an idea to help me ? Thanks in advance. Regards Lorenzo PS : here the sequence : -- amrecover> pwd /export/home/lorenzo/test amrecover> list amrecover> add fic1 Added /fic1 amrecover> extract Extracting files using tape drive /dev/rmt/0bn on host babylone. The following tapes are needed: DailySet101 Restoring files into directory /export/home/lorenzo/test Continue? [Y/n]: Load tape DailySet101 now Continue? [Y/n]: amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 Continue? [Y/n]: amrecover> quit --
amflush and irc?
Hello, Two things; On one hand, I have been thinking about running amanda once a week for totals directly to tape, and the rest of weekdays without tapes so incrementals are sent to holding disk, and then before next total on friday with tapes, I do amflush... Would that work nicely? I ask cause seems that amanda balances the backup on her own, but I cannot spend expensive DLT40/80 tapes with 2 gigs of incrementals only. Also, with amflush, will indexes be maintained without any trouble? So index server finds stuff as if they were on separated tapes. On the other hand, is there any irc channel for amanda? It's a nice way of sharing problems and stuff real-time. If there isnt any, what about #amanda at irc.openprojects.org? Regards...
Re: Hitting End of Tape
Joshua Baker-LePain wrote: > > On 21 Mar 2002 at 9:19am, [EMAIL PROTECTED] wrote > > > It seems that no matter what I set tapetype's length to (i.e., no matter > > how small I say the tape is) amanda hits end-of-tape. > > > > Please correct me if I am wrong but... > > > > I thought that if I set the tapetype length to a conservative value, > > then amanda would schedule only enough file-systems (level 0, 1, 2 > > etc...) to fit on the tape, and then put what wouldn't fit on the next > > days tape. > > That depends -- how conservative is conservative? > > > Instead I am hitting EOT every day and amanda fills up the holding area > > until I can flush it (which I do not want to have to do). > > > > Please let me know what information you may need to help me diagnose > > what's wrong. I have been trying for two weeks now with no progress. > > What model tape drive? Are you using software compression? Hardware > compression? Both? Are you seeing any messages in your system logs? > What does a sample run report look like? just as a follow-on to this -- I have a situation where a project is scanning archival images. they have an external array on one of my servers and are filling it with TIFF images. these images do not compress. the file format is inherently already compressed. JPEG also. if I were using hardware compression and giving a "conservative" estimate of say 18G for a DDS3 tape, I would hit end of tape every time. I only get 12G. If I were doing plain vanilla unix stuff, I would get close to 24G. HTH --- Chris Hoogendyk -- O__ Network Specialist & Unix Systems Administrator c/ /'_ --- Library Information Systems & Technology Services (*) \(*) -- W.E.B. Du Bois Library ~~ - University of Massachusetts, Amherst <[EMAIL PROTECTED]> ---
Re: Make problem on Solaris 2.8
I can only advise you from Solaris side. you can issue `ldd amanda_binary_name` on solaris, and see which library it's linking. Then check and make sure all the library files exist in the location it specifies. Mark - Original Message - From: "Mary Tan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 20, 2002 6:45 PM Subject: Re: Make problem on Solaris 2.8 > > Thank you all for the advice, I got through make successfully after setting > LD_LIBRARY_PATH. > > > However, after I've installed Amanda, there's a new problem. When I try to > run any amanda executables, I get the following error: > > $ amlabel DailySet1 DailySet1-001 > ld.so.1: amlabel: fatal: libreadline.so.4: open failed: No such file or > directory > Killed > > I've already installed ReadLine-4.2 and make sure it's in LD_LIBRARY_PATH. > I'm at a lost as to where else I should be looking. > > Any help is appreciated. > > > > > > > "Mark Lin" > > v.com> cc: > Subject: Re: Make problem on Solaris 2.8 > 03/19/02 01:05 > PM > > > > > > > Get ReadLine-4.2 from www.sunfreeware.com or if you already installed it, > make sure its lib is in the path of LD_LIBRARY_PATH. > > Mark > > - Original Message - > From: "Mary Tan" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 19, 2002 3:05 PM > Subject: Make problem on Solaris 2.8 > > > > Hi all: > > > > I'm trying to run make for Amanda 2.4.2p2 on a Solaris 2.8 SPARC server > > with the following configure options: > > > > ./configure --with-user=amanda --with-group=amanda > > > > During the make process, the following error occurs. Here's the tail end > > of the error message: > > > > rm -f genversion.h genversion.h.new > > echo '#define CC "gcc"' > genversion.h.new > > echo '#define BUILT_DATE "'`date`'"' >> genversion.h.new > > echo '#define BUILT_MACH "'`uname -a || echo UNKNOWN HOST`'"' >> > > genversion.h.new > > mv genversion.h.new genversion.h > > gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE > > -D_FILE_OFFSET_BITS=64 -g -O2 -c genversion.c > > gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE > > -D_FILE_OFFSET_BITS=64 -g -O2 -c versuff.c > > /bin/sh ../libtool --mode=link gcc -D_LARGEFILE_SOURCE > > -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o versuff.o > > alloc.o debug.o error.o util.o file.o -lgen -lm -lreadline > > -ltermcap -lsocket -lnsl -lintl > > mkdir .libs > > gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion > > genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lgen -lm > > -lreadline -ltermcap -lsocket -lnsl -lintl > > rm -f version.c > > ./genversion > version.c > > ld.so.1: ./genversion: fatal: libreadline.so.4: open failed: No such file > > or directory > > *** Error code 137 > > make: Fatal error: Command failed for target `version.c' > > Current working directory /home/amanda/amanda-2.4.2p2/common-src > > *** Error code 1 > > make: Fatal error: Command failed for target `all-recursive' > > > > > > Any guidance will be greatly appreciated. =) > > > > > > > > > >
index tee cannot write?
Hi! I just started using amanda on Monday night. That night, something caused my backup server to go off the network about halfway through the night, leaving several disks unbacked up. On Tuesday night, however, this didn't happen. Yet still, three disks didn't get backed up -- the dump summaries all had the same error: index tee cannot write. The only other error listed was "/usr/sbin/ufsdump returned 3". This again happened last night, although one of the three disks _did_ manage to dump sucessfully. The client disks report no more data than the server -- just that /usr/sbin/ufsdump returned 3. Does anyone have any ideas? Thanks, Ricky - Richard MorseSystem Administrator MGH Biostatistics Center 50 Staniford St. Rm 560 [EMAIL PROTECTED] 617/724-9830
Re: Hitting End of Tape
On 21 Mar 2002 at 9:19am, [EMAIL PROTECTED] wrote > It seems that no matter what I set tapetype's length to (i.e., no matter > how small I say the tape is) amanda hits end-of-tape. > > Please correct me if I am wrong but... > > I thought that if I set the tapetype length to a conservative value, > then amanda would schedule only enough file-systems (level 0, 1, 2 > etc...) to fit on the tape, and then put what wouldn't fit on the next > days tape. That depends -- how conservative is conservative? > Instead I am hitting EOT every day and amanda fills up the holding area > until I can flush it (which I do not want to have to do). > > Please let me know what information you may need to help me diagnose > what's wrong. I have been trying for two weeks now with no progress. What model tape drive? Are you using software compression? Hardware compression? Both? Are you seeing any messages in your system logs? What does a sample run report look like? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Hitting End of Tape
Help! It seems that no matter what I set tapetype's length to (i.e., no matter how small I say the tape is) amanda hits end-of-tape. Please correct me if I am wrong but... I thought that if I set the tapetype length to a conservative value, then amanda would schedule only enough file-systems (level 0, 1, 2 etc...) to fit on the tape, and then put what wouldn't fit on the next days tape. Instead I am hitting EOT every day and amanda fills up the holding area until I can flush it (which I do not want to have to do). Please let me know what information you may need to help me diagnose what's wrong. I have been trying for two weeks now with no progress. Thanks for any help! Dick
Re: Make problem on Solaris 2.8
On Wed, Mar 20, 2002 at 04:56:00PM -0800, Anthony A. D. Talltree wrote: > >Thank you all for the advice, I got through make successfully after setting > >LD_LIBRARY_PATH. > > >However, after I've installed Amanda, there's a new problem. When I try > >to run any amanda executables, I get the following error: > > >$ amlabel DailySet1 DailySet1-001 > >ld.so.1: amlabel: fatal: libreadline.so.4: open failed: No such file or > >directory The environment for LD_LIBRARY_PATH was set during the build, but is not retained by the executables. It has to be reset in the runtime environment. If set in the .profile of the this would allow amlabel to succeed from the command line. However, amcheck/amdump run from a crontab entry does not process the .profile. They don't use readline so this specific library may not cause a problem. > This is why linking with -R is the better answer. The executables then > know where to find the dynamic libs without LD_LIBRARY_PATH or > LD_RUN_PATH. Absolutely! > One way to do this might be > > unsetenv LD_LIBRARY_PATH > setenv LD_FLAGS "-R /usr/local/lib" Assuming "MT" is using c-shell :) > > before running configure, presuming that readline is in /usr/local/lib. > Use ldd on completed binaries to ensure that they can find the libs. An alternative for Solaris users (eg "MT") is the ld.config file. This is created and maintained by the crle command. It specifies what directories the dynamic linker searches for its libraries, i.e., the default LD_LIBRARY_PATH. If the contents of /usr/local/lib are trusted, this directory could be added to the default dirs in ld.config. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover pb
On Thu, Mar 21, 2002 at 02:42:54PM +0800, Robert SHEN wrote: > I got the following error when I tried to test the amrecover command > > After executed amrecover, it showed > Can't determine disk and mount point fr om $CWD > Normal, CWD = current working dir CWD is not one of the dirs in your disk list. So amrecover could not determine, from CWD, what disk list entry you want to work on. You will have to "set disk" interactively. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
