Re: failure strange dump
Hi Chris, Thanks for your reply, I don't use the email facility but I run a amreport and I get the following: FAILURE STRANGE DUMP dataserv / Results missing Amanda is running as root so I don't think its permissions. I'm compiling from source. I would be grateful if somebody could help me! Thanks in advance and for your help so far. Jane. jane, the disklist file looks fine. are you getting an email with errors? if so please send that and I can maybe help. If your getting disk offline errors it may be a permission issue. what user is amanda running as? are the filesystems (/dev/[sh]da[0-9]) owned by the group that amanda is running as? These are the first two things I would check. btw: I've had problems editing the group file by hand and adding amanda user to a group. It seems that the default group must be correct and amanda must be compiled with the correct options. Are you compiling from source or using an rpm? chrisj janebackup wrote: Chris, Thanks for your reply, yes I was trying to backup a single directory (thought I'd do this first just to test). If I have to backup the filesystem does this mean if I put the following entry in my disklist file?: dataserv/ always-full Cus I've already tried this and I still get the same errors. Is my disklist file wrong? Thanks for your help. Jane. jane Are you trying to backup a filesystem or a directory. Amanda is made to dump filesystems at the disk level and won't do a single directory. Are you getting an email of the errors or looking at the logs? chris janebackup wrote: Hi, I'm still trying to get my amanda backup working, I have amanda 2.4.3b3 on a linux machine and I am just trying to backup that one directory on that one machine with no tar/compression just to test for the minute. But even that doesn't work the only error messages I get in amcheck are: WARNING: info file /usr/adm/amanda/DailySet1/curinfo/dataserv/_tmp/info does not exist and in my report after I have ran amdump is: FAILURE STRANGE dump summary dataserv /tmp RESULTS MISSING and also: driver: WARNING: got empty schedule from planner I would be grateful any help! Jane. Jane Mattley Support Team Studio 2 Online Ltd Now Supplying Computer Hardware Software, Call for a Quote We guarantee to beat any Like for Like E-Commerce Quote Update your website for FREE with CMS Sales : 0116 2425811Support : 0906 756 0364 Email : mailto:[EMAIL PROTECTED] Web: http://www.s2o.co.uk/ Legal Disclaimer:- Internet communications are not secure and therefore Studio 2 Online does not accept legal responsibility for the contents of this message. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and therefore access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful, furthermore please contact the sender immediately by replying or by calling 0870 7417226 and delete this message and any attachment permanently from your system. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio 2 Online. Although Studio 2 Online operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Thank you for your co-operation
Re: tapeless with amanda-242-tapeio problem
I still can't get it ok, so I changed the /usr/lib/amanda/chg-multi script, and comment out: $MT $MTF $device rewind $logfile 21 So amanda wouldn't rewind and get an error, and thus affect the slotempty variable. Is this ok? Seems that the tapes are being labelled correctly.But I don't know what's the consequences. Currently I'm testing what will happen. If I'm wrong to comment out the chg-multi script, can anyone tell me what to do? On Monday 12 August 2002 15:19, Stelar wrote: Hi, I'm intending to use tapeless backup to my hard drive. From the mailing list, I see that I can use 2.4.2 (CVS amanda-242-tapeio) or 2.4.3 method. Which one is a better choice for production? Due to some mail that explained the 2.4.2 method in detail, I'm currently trying to use it. I've set the amanda.conf, changer.conf, tape directory as in http://groups.yahoo.com/group/amanda-users/message/36136 However, when I'm at step 5 of the posting above (labelling), I get this error: amlabel: could not load slot 1: chg-multi: slot is empty Anyone can help me?
RE: Good Teeth
On 13 Aug 2002 at 9:37, Martinez, Michael - CSREES/ISTM wrote: Spam control Yes. But _why_ - the hell - do you send the whole spam again?! As a fullquote under your _very_ _short_ answer?! Michael Martinez System Administrator (Contractor) Thank You. No answer needed. *grmpf*
Re: failure strange dump
On Wednesday 14 August 2002 04:14, janebackup wrote: Hi Chris, Thanks for your reply, I don't use the email facility but I run a amreport and I get the following: FAILURE STRANGE DUMP dataserv / Results missing Amanda is running as root so I don't think its permissions. amanda doesn't like running as root, usually totally refusing to, but will get root perms when she needs to. amanda should be run as an unpriviledged user who is a member of group disk or maybe backup, and will do an suid when required. I'm compiling from source. I would be grateful if somebody could help me! The contents of this list usually get a recipe for building amanda from me about weekly, so you might want to look at the last couple of weeks worth to see one way of doing it that works here. Thanks in advance and for your help so far. Jane. jane, the disklist file looks fine. are you getting an email with errors? if so please send that and I can maybe help. If your getting disk offline errors it may be a permission issue. what user is amanda running as? are the filesystems (/dev/[sh]da[0-9]) owned by the group that amanda is running as? These are the first two things I would check. btw: I've had problems editing the group file by hand and adding amanda user to a group. It seems that the default group must be correct and amanda must be compiled with the correct options. Are you compiling from source or using an rpm? chrisj janebackup wrote: Chris, Thanks for your reply, yes I was trying to backup a single directory (thought I'd do this first just to test). If I have to backup the filesystem does this mean if I put the following entry in my disklist file?: dataserv/ always-full Cus I've already tried this and I still get the same errors. Is my disklist file wrong? Thanks for your help. Jane. jane Are you trying to backup a filesystem or a directory. Amanda is made to dump filesystems at the disk level and won't do a single directory. Are you getting an email of the errors or looking at the logs? chris janebackup wrote: Hi, I'm still trying to get my amanda backup working, I have amanda 2.4.3b3 on a linux machine and I am just trying to backup that one directory on that one machine with no tar/compression just to test for the minute. But even that doesn't work the only error messages I get in amcheck are: WARNING: info file /usr/adm/amanda/DailySet1/curinfo/dataserv/_tmp/info does not exist and in my report after I have ran amdump is: FAILURE STRANGE dump summary dataserv /tmp RESULTS MISSING and also: driver: WARNING: got empty schedule from planner I would be grateful any help! Jane. Jane Mattley Support Team Studio 2 Online Ltd Now Supplying Computer Hardware Software, Call for a Quote We guarantee to beat any Like for Like E-Commerce Quote Update your website for FREE with CMS Sales : 0116 2425811Support : 0906 756 0364 Email : mailto:[EMAIL PROTECTED] Web: http://www.s2o.co.uk/ Legal Disclaimer:- Internet communications are not secure and therefore Studio 2 Online does not accept legal responsibility for the contents of this message. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and therefore access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful, furthermore please contact the sender immediately by replying or by calling 0870 7417226 and delete this message and any attachment permanently from your system. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio 2 Online. Although Studio 2 Online operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Thank you for your co-operation -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Index Tees - Data Timeouts
I am running Amanda 2.4.2p2 on a Redhat Linux 7.3 as my Amanda server. The clients are mostly Solaris. I have been been backing up the server and adding clients one at a time. Everything was working well, one server and two clients, then I added a third client. Now I getting data timeouts and index tee broken messages in my Amanda reports and in the system log files. I have perused the docs, FAQ, and the various log files that Amanda generates and I not finding the clue to point me to the problem. All I keep seeing are the index tee messages, but not what is causing the index tee messages to be generated. Suggestions or ideas? If more info is needed, amanda.conf entries etc... let me know and I can provide. Thanks in advance, Jim Summers [EMAIL PROTECTED]
Re: Index Tees - Data Timeouts
On 14 Aug 2002 at 8:09am, Jim Summers wrote I am running Amanda 2.4.2p2 on a Redhat Linux 7.3 as my Amanda server. The clients are mostly Solaris. I have been been backing up the server and adding clients one at a time. Everything was working well, one server and two clients, then I added a third client. Now I getting data timeouts and index tee broken messages in my Amanda reports and in the system log files. From which systems? The actual error messages would be most helpful. I have perused the docs, FAQ, and the various log files that Amanda generates and I not finding the clue to point me to the problem. All I keep seeing are the index tee messages, but not what is causing the index tee messages to be generated. Also send along the contents of /tmp/amanda/sendbackup*debug from the failing clients. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Configuration help?
Hello again everyone! Now that I have sorted out my tapetype issue I kindly ask for some help on configuring Amanda. What I would like to do is: - full backups every weekday (mon-fri) - use 5 tapes (possibly 6) - backup the following filesystems host: louie filesys: /export/home/htdocs host: louie filesys: /export/home/htdocs-utv host: bagheera (win2k server) \\bagheera\misc The questions is, how to I write the disklist and amanda.conf correctly (I have succeded in doing a small test to just backup a unix partition). Should I have: dumpcycle 1 week runspercycle 5 tapecycle 5 and force all backups to be full backups? Or maybe I could have dumpcycle 1 day runspercycle 1 tapecycle 5 and use cron to schedule it on weekdays only? I am a bit unsure about how to set the parameters so any pointers would be most appreciated. Thanks in advance! /Conny
Re: Configuration help?
On Wed, 14 Aug 2002 at 4:27pm, Conny Gyllendahl wrote What I would like to do is: - full backups every weekday (mon-fri) - use 5 tapes (possibly 6) - backup the following filesystems host: louie filesys: /export/home/htdocs host: louie filesys: /export/home/htdocs-utv host: bagheera (win2k server) \\bagheera\misc You need a *nix client with the samba client bits installed in order to get the 'doze box. The disklist entry would look like: $UNIX_HOST //bagheera/misc $DUMPTYPE_USING_TAR Or maybe I could have dumpcycle 1 day runspercycle 1 tapecycle 5 and use cron to schedule it on weekdays only? Close. Set dumpcycle to 0 -- that will force all level 0s. And, yes, use cron to run amdump on weekdays only. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: failure strange dump
On Wed, 14 Aug 2002 at 2:54pm, janebackup wrote Thanks for your email, if I want to change my amanda to run as a different user does this mean I have to re-install it? Yes. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: patched-up version of tar.
Jon LaBadie wrote: Is this a problem you are having or just something you understand? *ouch*. Please excuse my writing style. ;-) On most of my systems this non-zero status is not a problem. On my cygwin client it did cause problems so I modified tar's source code to force a zero exits status. Unfortunately, on the majority of my clients tar returns non-zero exit status, so i will have to find a workaround. I have received three suggestions so far: 1. Hack tar to force it to return a non-error status I think 1 is the best option for systems that only have logfiles, since the only thing that would be missing in the backup is the appended lines, which would be backed up the next day in any event. Q. Is there modified tar source posted somewhere on the net by some kind soul? 2. Ignore files which change size during a backup This one is the least likely option, as even logfiles can be important. 3. Take a snapshot of the system before backing it up. On systems that have files whose entire 'state' changes, it seems this is the most reasonable solution. Examples of this would be databases or hash files, etc., in which case a shell script could be written to take care of this before the backup runs. Q: What do you do for large files which are constantly changing? for example, one of my files is 800MB and its 'state' changes fairly regularly, resulting in failed or inaccurate backups. I haven't figured out what to do with this one. I don't know of any way to 'lock' the file during a backup procedure, or even while copying it somewhere else, for that matter. Does anyone have a suggestion here? Thank-you so much for your help! cheers, john.
Re: Index Tees - Data Timeouts
On 14 Aug 2002 at 9:26am, Jim Summers wrote On Wed, 2002-08-14 at 08:23, Joshua Baker-LePain wrote: On 14 Aug 2002 at 8:09am, Jim Summers wrote I am running Amanda 2.4.2p2 on a Redhat Linux 7.3 as my Amanda server. The clients are mostly Solaris. I have been been backing up the server and adding clients one at a time. Everything was working well, one server and two clients, then I added a third client. Now I getting data timeouts and index tee broken messages in my Amanda reports and in the system log files. From which systems? The actual error messages would be most helpful. From one of the working systems a Sun E250 Solaris 8 and from the newly added system Sun Ultra10 Solaris 8. I will send the amanda report when I get the next one. You said you had messages in the system log files -- what are those? You could also try increasing dtimeout... How do your dumprates look? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amrecover: Unexpected server end of file
I am getting the amrecover: Unexpected server end of file error when trying to run the amrecover program. I looked at the FAQ and tested the IP address and host names and made sure that they all matched up. I get this problem for both client machines and the server machine. The messages that I get are: AMRECOVER Version 2.4.2p2. Contacting server on moses.hq.essensys.com ... 220 moses AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-08-14) 200 Working date set to 2002-08-14. 200 Working date set to 2002-08-14. amrecover: Unexpected server end of file Does anyone have any idea on what else to check? Thanks, Dan Gynn -- - Daniel T. Gynn RHCE #806200978201621 Essential Systems, Inc. 412-931-5403 ext. 1 fax: 412-931-5425 [EMAIL PROTECTED]
Re: Index Tees - Data Timeouts
On Wed, 2002-08-14 at 09:44, Joshua Baker-LePain wrote:
On 14 Aug 2002 at 9:26am, Jim Summers wrote
On Wed, 2002-08-14 at 08:23, Joshua Baker-LePain wrote:
On 14 Aug 2002 at 8:09am, Jim Summers wrote
I am running Amanda 2.4.2p2 on a Redhat Linux 7.3 as my Amanda server.
The clients are mostly Solaris. I have been been backing up the server
and adding clients one at a time. Everything was working well, one
server and two clients, then I added a third client. Now I getting data
timeouts and index tee broken messages in my Amanda reports and in the
system log files.
From which systems? The actual error messages would be most helpful.
From one of the working systems a Sun E250 Solaris 8 and from the newly
added system Sun Ultra10 Solaris 8. I will send the amanda report when
I get the next one.
You said you had messages in the system log files -- what are those? You
Here are the messages in my system log file:
Aug 14 01:14:14 turing sendbackup[17657]: [ID 702911 auth.notice] index
tee cannot write [Broken pipe]
Aug 14 01:14:14 turing sendbackup[17655]: [ID 702911 auth.notice] error
[/usr/local/bin/tar got signal 13, compress returned 1]
Aug 14 02:06:34 turing sendbackup[17740]: [ID 702911 auth.notice] index
tee cannot write [Broken pipe]
could also try increasing dtimeout...
I have twiddled with that one went from 1800 to 3600. Then back to 1800
and I am currently at 2400.
How do your dumprates look?
Here is the last amanda report received. I incorrectly used the wrong
dump type on the /usr/oracle fs.
These dumps were to tapes daily09, daily10.
The next 2 tapes Amanda expects to used are: daily11, daily12.
FAILURE AND STRANGE DUMP SUMMARY:
tarjan /opt lev 0 FAILED [data timeout]
turing /cs/turing/home2 lev 1 FAILED [data timeout]These dumps
were to tapes daily09, daily10.
The next 2 tapes Amanda expects to used are: daily11, daily12.
FAILURE AND STRANGE DUMP SUMMARY:
tarjan /opt lev 0 FAILED [data timeout]
turing /cs/turing/home2 lev 1 FAILED [data timeout]
turing /opt lev 0 FAILED [data timeout]
tarjan /usr/oracle lev 0 FAILED [data timeout]
turing /usr lev 0 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:50
Run Time (hrs:min)10:21
Dump Time (hrs:min)4:26 4:08 0:17
Output Size (meg) 13542.111766.4 1775.7
Original Size (meg) 26361.524555.9 1805.6
Avg Compressed Size (%)47.9 47.97.3 (level:#disks
...)
Filesystems Dumped 13 4 9 (1:9)
Avg Dump Rate (k/s) 870.0 808.9 1742.9
Tape Time (hrs:min)3:23 2:56 0:27
Tape Size (meg) 13542.511766.5 1776.0
Tape Used (%) 116.7 101.4 15.3 (level:#disks
...)
Filesystems Taped13 4 9 (1:9)
Avg Tp Write Rate (k/s) 1137.5 1141.5 .7
FAILED AND STRANGE DUMP DETAILS:
/-- tarjan /opt lev 0 FAILED [data timeout]
sendbackup: start [tarjan:/opt level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
?
\
/-- turing /cs/turing/home2 lev 1 FAILED [data timeout]
sendbackup: start [turing:/cs/turing/home2 level 1]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
?
\
/-- turing /opt lev 0 FAILED [data timeout]
sendbackup: start [turing:/opt level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc
|/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Wed Aug 14 01:54:45 2002
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rdsk/c0t0d0s5 (turing:/opt) to standard output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 6949216 blocks (3393.17MB) on 0.05 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
|
? gzip: stdout: Broken pipe
? sendbackup: index tee cannot write [Broken pipe]
| DUMP: Broken pipe
| DUMP: The ENTIRE dump is aborted.
? index returned 1
sendbackup: error [/usr/sbin/ufsdump returned 3, compress returned 1]
\
/-- tarjan /usr/oracle lev 0 FAILED [data timeout]
sendbackup: start [tarjan:/usr/oracle level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc
|/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of
Re: amrecover: Unexpected server end of file
One way to get this error is by not specifying a configuration when you run amrecover. Make sure you are running it with something like $ amrecover -C Daily ... Daniel T. Gynn wrote: I am getting the amrecover: Unexpected server end of file error when trying to run the amrecover program. I looked at the FAQ and tested the IP address and host names and made sure that they all matched up. I get this problem for both client machines and the server machine. The messages that I get are: AMRECOVER Version 2.4.2p2. Contacting server on moses.hq.essensys.com ... 220 moses AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-08-14) 200 Working date set to 2002-08-14. 200 Working date set to 2002-08-14. amrecover: Unexpected server end of file Does anyone have any idea on what else to check? Thanks, Dan Gynn -- - Daniel T. Gynn RHCE #806200978201621 Essential Systems, Inc. 412-931-5403 ext. 1 fax: 412-931-5425 [EMAIL PROTECTED] -- Scott Sanders Systems Administrator Concepts Direct, Inc. 2950 Colorful Ave. Longmont, CO 80504 (303) 682-7110 Phone (303) 682-7140 Fax
(no subject)
i've just been sitting here trying to determine what the actual differences between comp-root-tar and comp-user-tar are for example: should i do /home as comp-user-tar or as comp-root-tar? does comp-user-tar maintain user rights/ownership? or does it make no difference? thanks
Re: (no subject)
I think the only difference is what priority the dump has. root-tar has a low priority and user-tar has a medium priority. Right/ownership are preserved either way. C White wrote: i've just been sitting here trying to determine what the actual differences between comp-root-tar and comp-user-tar are for example: should i do /home as comp-user-tar or as comp-root-tar? does comp-user-tar maintain user rights/ownership? or does it make no difference? thanks -- Scott Sanders Systems Administrator Concepts Direct, Inc. 2950 Colorful Ave. Longmont, CO 80504 (303) 682-7110 Phone (303) 682-7140 Fax
Re: (no subject)
On Wed, Aug 14, 2002 at 10:48:22AM -0600, Scott Sanders wrote:
I think the only difference is what priority the dump has. root-tar has
a low priority and user-tar has a medium priority.
Right/ownership are preserved either way.
C White wrote:
i've just been sitting here trying to determine what the actual
differences between comp-root-tar and comp-user-tar are
Scott is correct using my dumptypes. Local changes might affect the answer.
I sometimes explore the chain of dumptype includes and see what they would
be if merged into a single dumptype. Note, I don't install it this way,
just check it out. Here is the results of my two dumptypes.
define dumptype comp-user-tar {
# user-tar
# root-tar
# global
index yes
record yes
program GNUTAR
compress none
index yes
exclude list /usr/local/etc/amanda/exclude.gtar
priority low
priority medium
compress client fast
}
define dumptype comp-root-tar {
# root-tar
# global
index yes
record yes
program GNUTAR
compress none
index yes
exclude list /usr/local/etc/amanda/exclude.gtar
priority low
compress client fast
record yes
}
For duplicate items, the last one takes effect.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: (no subject)
thanks for your answers, i was pretty sure that there was no real difference
between the two, and you've now clarified that for me
--
http://theatomicmoose.ca
Quoting Jon LaBadie [EMAIL PROTECTED]:
On Wed, Aug 14, 2002 at 10:48:22AM -0600, Scott Sanders wrote:
I think the only difference is what priority the dump has. root-tar has
a low priority and user-tar has a medium priority.
Right/ownership are preserved either way.
C White wrote:
i've just been sitting here trying to determine what the actual
differences between comp-root-tar and comp-user-tar are
Scott is correct using my dumptypes. Local changes might affect the
answer.
I sometimes explore the chain of dumptype includes and see what they would
be if merged into a single dumptype. Note, I don't install it this way,
just check it out. Here is the results of my two dumptypes.
define dumptype comp-user-tar {
# user-tar
# root-tar
# global
index yes
record yes
program GNUTAR
compress none
index yes
exclude list /usr/local/etc/amanda/exclude.gtar
priority low
priority medium
compress client fast
}
define dumptype comp-root-tar {
# root-tar
# global
index yes
record yes
program GNUTAR
compress none
index yes
exclude list /usr/local/etc/amanda/exclude.gtar
priority low
compress client fast
record yes
}
For duplicate items, the last one takes effect.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
-
This mail sent through Moose Mail http://webmail.theatomicmoose.ca
Re: Index Tees - Data Timeouts
In an effort to debug this problem, is there a way I can interactively
run the command(s) that amanda would run to see if anything is dumped to
stdout? If so, are these the commands in runtar and sendbackup? Or
would it be better to comment out all filesystems except one of the ones
having problems and run amdump?
Thanks again,
Jim
On Wed, 2002-08-14 at 10:41, Jim Summers wrote:
On Wed, 2002-08-14 at 09:44, Joshua Baker-LePain wrote:
On 14 Aug 2002 at 9:26am, Jim Summers wrote
On Wed, 2002-08-14 at 08:23, Joshua Baker-LePain wrote:
On 14 Aug 2002 at 8:09am, Jim Summers wrote
I am running Amanda 2.4.2p2 on a Redhat Linux 7.3 as my Amanda server.
The clients are mostly Solaris. I have been been backing up the server
and adding clients one at a time. Everything was working well, one
server and two clients, then I added a third client. Now I getting data
timeouts and index tee broken messages in my Amanda reports and in the
system log files.
From which systems? The actual error messages would be most helpful.
From one of the working systems a Sun E250 Solaris 8 and from the newly
added system Sun Ultra10 Solaris 8. I will send the amanda report when
I get the next one.
You said you had messages in the system log files -- what are those? You
Here are the messages in my system log file:
Aug 14 01:14:14 turing sendbackup[17657]: [ID 702911 auth.notice] index
tee cannot write [Broken pipe]
Aug 14 01:14:14 turing sendbackup[17655]: [ID 702911 auth.notice] error
[/usr/local/bin/tar got signal 13, compress returned 1]
Aug 14 02:06:34 turing sendbackup[17740]: [ID 702911 auth.notice] index
tee cannot write [Broken pipe]
could also try increasing dtimeout...
I have twiddled with that one went from 1800 to 3600. Then back to 1800
and I am currently at 2400.
How do your dumprates look?
Here is the last amanda report received. I incorrectly used the wrong
dump type on the /usr/oracle fs.
These dumps were to tapes daily09, daily10.
The next 2 tapes Amanda expects to used are: daily11, daily12.
FAILURE AND STRANGE DUMP SUMMARY:
tarjan /opt lev 0 FAILED [data timeout]
turing /cs/turing/home2 lev 1 FAILED [data timeout]These dumps
were to tapes daily09, daily10.
The next 2 tapes Amanda expects to used are: daily11, daily12.
FAILURE AND STRANGE DUMP SUMMARY:
tarjan /opt lev 0 FAILED [data timeout]
turing /cs/turing/home2 lev 1 FAILED [data timeout]
turing /opt lev 0 FAILED [data timeout]
tarjan /usr/oracle lev 0 FAILED [data timeout]
turing /usr lev 0 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:50
Run Time (hrs:min)10:21
Dump Time (hrs:min)4:26 4:08 0:17
Output Size (meg) 13542.111766.4 1775.7
Original Size (meg) 26361.524555.9 1805.6
Avg Compressed Size (%)47.9 47.97.3 (level:#disks
...)
Filesystems Dumped 13 4 9 (1:9)
Avg Dump Rate (k/s) 870.0 808.9 1742.9
Tape Time (hrs:min)3:23 2:56 0:27
Tape Size (meg) 13542.511766.5 1776.0
Tape Used (%) 116.7 101.4 15.3 (level:#disks
...)
Filesystems Taped13 4 9 (1:9)
Avg Tp Write Rate (k/s) 1137.5 1141.5 .7
FAILED AND STRANGE DUMP DETAILS:
/-- tarjan /opt lev 0 FAILED [data timeout]
sendbackup: start [tarjan:/opt level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
?
\
/-- turing /cs/turing/home2 lev 1 FAILED [data timeout]
sendbackup: start [turing:/cs/turing/home2 level 1]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
?
\
/-- turing /opt lev 0 FAILED [data timeout]
sendbackup: start [turing:/opt level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc
|/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Wed Aug 14 01:54:45 2002
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rdsk/c0t0d0s5 (turing:/opt) to standard output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Estimated 6949216 blocks (3393.17MB) on 0.05 tapes.
| DUMP: Dumping (Pass III) [directories]
| DUMP: Dumping (Pass IV) [regular files]
|
? gzip: stdout: Broken pipe
? sendbackup: index tee cannot write [Broken
Re: Index Tees - Data Timeouts
On 14 Aug 2002 at 2:19pm, Jim Summers wrote In an effort to debug this problem, is there a way I can interactively run the command(s) that amanda would run to see if anything is dumped to stdout? If so, are these the commands in runtar and sendbackup? Or would it be better to comment out all filesystems except one of the ones having problems and run amdump? The exact commands are in both runtar*debug and sendbackup*debug. It would be interesting to comment out some filesystems to see if it's a function of having too much going on on one host, or if it's something particular to those filesystems. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Index Tees - Data Timeouts
On Wed, Aug 14, 2002 at 02:19:16PM -0500, Jim Summers wrote: In an effort to debug this problem, is there a way I can interactively run the command(s) that amanda would run to see if anything is dumped to stdout? If so, are these the commands in runtar and sendbackup? Or would it be better to comment out all filesystems except one of the ones having problems and run amdump? Two of the 4 failures (1 was only strange) were using ufsdump. Shouldn't those commands be in rundump debug files? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Sun L280
Hello, I have seen a number of messages in regard to this, so hopefully someone can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? Also, I am new to this type of config and I was wondering what I need to do to configure the st.conf file and other files to get the library to work. Any help is appreciated. Ed Smith
FW: Sun L280
Hello, A little more information: I am running Solaris 8 I have an A1000 connected to the 220R (works fine) I have installed the suggested patches for Amanda and L280 Thanks... Ed -Original Message- From: Smith, Ed Sent: Wednesday, August 14, 2002 1:41 PM To: amanda-users Subject: Sun L280 Hello, I have seen a number of messages in regard to this, so hopefully someone can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? Also, I am new to this type of config and I was wondering what I need to do to configure the st.conf file and other files to get the library to work. Any help is appreciated. Ed Smith
Re: Sun L280
On Wed, Aug 14, 2002 at 03:40:47PM -0500, [EMAIL PROTECTED] wrote: Hello, I have seen a number of messages in regard to this, so hopefully someone can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? Also, I am new to this type of config and I was wondering what I need to do to configure the st.conf file and other files to get the library to work. Any help is appreciated. Not sure what you mean in regard to this. Are you having trouble? What kind? What have you tried? What errors did you encounter? First source of answers is the documentation that comes with the L280. I once watched an installer putting in a Sun DLT drive who did not consult the docs in the box. He just knew what to do. The little lines at the start of the installation manual that said you must edit the st.conf file were deemed unnecessary when pointed out to him. Frustrated he gave up after 4 hours and was leaving for the day. While he was packing up I followed the instructions and had it running before he was ready to leave. Don't have the docs? Shame! Call your Sun rep for replacements and meanwhile go to docs.sun.com. As it is an HP unit (surestore autoloader 718) you can get some info at hp.com support-storage-tape-manuals. HP dat changers and drives (not familiar with dlt) have VERY specific dip switch settings for using them on Solaris. You would think a Sun branded HP drive is already setup properly but ... RE st.conf, as this is a Sun product, your st.conf may already have the needed entries (mine doesn't). If installed correctly there should be devices in /dev/rmt. Presence of the devices does not mean correct installation, but absence means incorrect installation. mt can be used to manipulate the drive (not changer, just drive). dd/tar/ufsdump/cat can be used to read and write to the drive. Does the drive come with a program similar to mtx to control the changer? Maybe (i don't know the answer) the freeware mtx will work for dlt changers. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: FW: Sun L280
On Wed, Aug 14, 2002 at 03:49:30PM -0500, [EMAIL PROTECTED] wrote: Hello, A little more information: I am running Solaris 8 I have an A1000 connected to the 220R (works fine) I have installed the suggested patches for Amanda and L280 [clip] can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? The low-tech way to make sure the box sees your new SCSI devices is to do a clean halt to boot prompt then: OK reset-all OK probe-scsi-all Confirm the target addresses are what you expected them to be. Bring it back up with: OK boot -r FOR THE TAPE: IIRC, the drive in that box is a DLT-7000, right? For that drive, with Solaris 8, you won't need to touch st.conf. After the 'boot -r' you should have /dev/rmt/0* (if you've never had a tape drive on this box before), and you should be able to 'mt -f /dev/rmt/0n status'. The devices will be: 0l*:20G (DLT4000, compression off) 0m*:40G (DLT4000, compression on) 0h*:35G (DLT7000, compression off) 0*: 70G (DLT7000, compression on) 0c*:70G (DLT7000, compression on) 0u*:70G (DLT7000, compression on) You can download a nice Solaris st.conf PDF from Quantum, but you don't need it. FOR THE CHANGER: --- These days, for Solaris 8, I'm recommending sgen(7D) and mtx. Even if you don't end up using chg-zd-mtx, mtx itself is nice to have, and the mtx source includes a nice little contrib/config_sgen_solaris script. You end up with an sgen.conf something like: device-type-config-list=changer; name=sgen class=scsi target=0 lun=0; name=sgen class=scsi target=1 lun=0; name=sgen class=scsi target=2 lun=0; name=sgen class=scsi target=3 lun=0; name=sgen class=scsi target=4 lun=0; name=sgen class=scsi target=5 lun=0; name=sgen class=scsi target=6 lun=0; name=sgen class=scsi target=7 lun=0; name=sgen class=scsi target=8 lun=0; name=sgen class=scsi target=9 lun=0; name=sgen class=scsi target=10 lun=0; name=sgen class=scsi target=11 lun=0; name=sgen class=scsi target=12 lun=0; name=sgen class=scsi target=13 lun=0; name=sgen class=scsi target=14 lun=0; name=sgen class=scsi target=15 lun=0; (You don't *need* every possible target, of course). This ends up making /dev/scsi/changer/cXtYd0. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
RE: Sun L280
Hello, I was able to see the changer and the drive, but mt says my drive is either offline or no tape loaded (and is correct, no tape loaded). /dev/rmt/0n: no tape loaded or drive offline However, I was not able to get the sgen.conf to work correctly. I couldn't get the config_sgen_solaris script to work without a CVROOT set. Any ideas what I can do from here?Thanks... Ed FOR THE TAPE: IIRC, the drive in that box is a DLT-7000, right? For that drive, with Solaris 8, you won't need to touch st.conf. After the 'boot -r' you should have /dev/rmt/0* (if you've never had a tape drive on this box before), and you should be able to 'mt -f /dev/rmt/0n status'. The devices will be: 0l*:20G (DLT4000, compression off) 0m*:40G (DLT4000, compression on) 0h*:35G (DLT7000, compression off) 0*: 70G (DLT7000, compression on) 0c*:70G (DLT7000, compression on) 0u*:70G (DLT7000, compression on) You can download a nice Solaris st.conf PDF from Quantum, but you don't need it. FOR THE CHANGER: --- These days, for Solaris 8, I'm recommending sgen(7D) and mtx. Even if you don't end up using chg-zd-mtx, mtx itself is nice to have, and the mtx source includes a nice little contrib/config_sgen_solaris script. You end up with an sgen.conf something like: device-type-config-list=changer; name=sgen class=scsi target=0 lun=0; name=sgen class=scsi target=1 lun=0; name=sgen class=scsi target=2 lun=0; name=sgen class=scsi target=3 lun=0; name=sgen class=scsi target=4 lun=0; name=sgen class=scsi target=5 lun=0; name=sgen class=scsi target=6 lun=0; name=sgen class=scsi target=7 lun=0; name=sgen class=scsi target=8 lun=0; name=sgen class=scsi target=9 lun=0; name=sgen class=scsi target=10 lun=0; name=sgen class=scsi target=11 lun=0; name=sgen class=scsi target=12 lun=0; name=sgen class=scsi target=13 lun=0; name=sgen class=scsi target=14 lun=0; name=sgen class=scsi target=15 lun=0; (You don't *need* every possible target, of course). This ends up making /dev/scsi/changer/cXtYd0. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Sun L280
On Wed, Aug 14, 2002 at 05:38:32PM -0500, [EMAIL PROTECTED] wrote: Hello, I was able to see the changer and the drive, but mt says my drive is either offline or no tape loaded (and is correct, no tape loaded). /dev/rmt/0n: no tape loaded or drive offline However, I was not able to get the sgen.conf to work correctly. I couldn't get the config_sgen_solaris script to work without a CVROOT set. Any ideas what I can do from here?Thanks... Dude, just delete the line! It doesn't do anything. -Jay- -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
