Re: amreport analysis
Just a quick note to say thanx for the suggestions, and that I'm working on them. I have a question which I think is more Linux than Amanda, but it's affecting Amanda. On one of the servers I receive the amreport via email just fine, but on the other I have to manually request it to run. I checked the crontab stuff and it seems to be in there okay. Anyone have a suggestion on where I should look to clear this up? -- View this message in context: http://www.nabble.com/amreport-analysis-tp14338749p14372564.html Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: amreport analysis
Hi Tom Anyone have a suggestion on where I should look to clear this up? Is cron running? Anything in the cron logs? What exactly is your cron entry, and which file is it in? -- Keith Edmunds +-+ | Tiger Computing Ltd | Helping businesses make the most of Linux | | The Linux Company | http://www.tiger-computing.co.uk | +-+
amreport analysis
Quick thanks to Jon, Gene, Chris, and John for assist with my amflush
question
Am now looking for folks suggestions on whay I'm seeing on my amreport.
I've copied it below. Since I'm still very new to both Linux and Amanda I'm
wondering which lines I need to be concerned about and which ones I can
ignore.
Any assistance would be appreciated.
These dumps were to tape Daily-004.
The next tape Amanda expects to use is: Daily-005.
FAILURE AND STRANGE DUMP SUMMARY:
brain.milw / lev 0 FAILED [/bin/gtar returned 2]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:06
Run Time (hrs:min) 3:45
Dump Time (hrs:min)1:30 1:28 0:02
Output Size (meg) 10241.210241.00.2
Original Size (meg) 16661.716658.73.0
Avg Compressed Size (%)44.4 44.58.4 (level:#disks ...)
Filesystems Dumped 10 7 3 (1:2 2:1)
Avg Dump Rate (k/s) 1943.5 1980.22.6
Tape Time (hrs:min)2:21 2:21 0:00
Tape Size (meg) 10241.610241.20.3
Tape Used (%) 51.3 51.30.0 (level:#disks ...)
Filesystems Taped10 7 3 (1:2 2:1)
Avg Tp Write Rate (k/s) 1235.6 1239.4 13.3
FAILED AND STRANGE DUMP DETAILS:
/-- brain.milw / lev 0 FAILED [/bin/gtar returned 2]
sendbackup: start [brain.milw.nvisia.com:/ level 0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f... -
sendbackup: info end
? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
| gtar: ./lib/dev-state/gpmctl: socket ignored
| gtar: ./lib/dev-state/log: socket ignored
| gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
| gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored
| Total bytes written: 3503226880 (3.3GiB, 1.7MiB/s)
? gtar: Error exit delayed from previous errors
sendbackup: error [/bin/gtar returned 2]
\
NOTES:
planner: Preventing bump of brain.milw.nvisia.com:/ as directed.
planner: Last full dump of brain.milw.nvisia.com:/mnt/archive_vol/home on
tape Daily-004 overwritten on this run.
planner: Dump too big for tape: full dump of
brain.milw.nvisia.com:/mnt/archive_vol/home delayed.
planner: Full dump of was.demo.nvisia.com:/ promoted from 3 days ahead.
planner: Full dump of was.demo.nvisia.com:/opt promoted from 3 days ahead.
planner: Full dump of brain.milw.nvisia.com:/mnt/archive_vol/utility
promoted from 3 days ahead.
planner: Full dump of
brain.milw.nvisia.com:/mnt/archive_vol/cvs_repository promoted from 3 days
ahead.
planner: Full dump of brain.milw.nvisia.com:/boot promoted from 3 days
ahead.
taper: tape Daily-004 kb 10487360 fm 10 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
brain.milw.n / 0 FAILED ---
brain.milw.n /boot 06592 6624 --0:041537.3 0:051318.2
brain.milw.n -xport/home 0 52201925220224 -- 47:261834.2 47:271833.9
brain.milw.n -repository 0 38270 30784 80.4 1:05 470.5 0:241267.5
brain.milw.n -repository 1 450 64 14.2 0:39 0.8 0:02 39.9
brain.milw.n -e_vol/home 22110224 10.6 0:38 5.0 0:02 136.5
brain.milw.n -ol/utility 0 124150 39328 31.7 1:18 505.0 0:301298.6
brain.milw.n /usr2 1 470 64 13.6 0:22 1.4 0:23 2.8
was.demo.nvi / 0 1991870 690112 34.6 4:092775.1 34:37 332.2
was.demo.nvi /home 0 74908303354208 44.8 28:031992.7 43:091295.4
was.demo.nvi /opt0 21866401145728 52.4 6:103093.2 14:491289.2
(brought to you by Amanda version 2.4.3)
--
View this message in context:
http://www.nabble.com/amreport-analysis-tp14338749p14338749.html
Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: amreport analysis
On Dec 14, 2007 11:11 AM, Tom Herrera [EMAIL PROTECTED] wrote:
? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
These are a problem. You should add an exclude for /mnt to your DLE:
brain.milw / {
WHATEVER_DUMPTYPE_YOU_HAD
exclude list append ./mnt
} -1 le0
| gtar: ./lib/dev-state/gpmctl: socket ignored
| gtar: ./lib/dev-state/log: socket ignored
| gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
| gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored
These are harmless, but you can exclude them, too, if you'd like.
Dustin
--
Storage Software Engineer
http://www.zmanda.com
Re: amreport analysis
0:241267.5 brain.milw.n -repository 1 450 64 14.2 0:39 0.8 0:02 39.9 brain.milw.n -e_vol/home 22110224 10.6 0:38 5.0 0:02 136.5 brain.milw.n -ol/utility 0 124150 39328 31.7 1:18 505.0 0:301298.6 brain.milw.n /usr2 1 470 64 13.6 0:22 1.4 0:23 2.8 was.demo.nvi / 0 1991870 690112 34.6 4:092775.1 34:37 332.2 was.demo.nvi /home 0 74908303354208 44.8 28:031992.7 43:091295.4 was.demo.nvi /opt0 21866401145728 52.4 6:103093.2 14:491289.2 (brought to you by Amanda version 2.4.3) -- View this message in context: http://www.nabble.com/amreport-analysis-tp14338749p14338749.html Sent from the Amanda - Users mailing list archive at Nabble.com. End of included message -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amreport analysis
Dustin J. Mitchell wrote:
On Dec 14, 2007 11:11 AM, Tom Herrera [EMAIL PROTECTED] wrote:
? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
These are a problem. You should add an exclude for /mnt to your DLE:
brain.milw / {
WHATEVER_DUMPTYPE_YOU_HAD
exclude list append ./mnt
} -1 le0
| gtar: ./lib/dev-state/gpmctl: socket ignored
| gtar: ./lib/dev-state/log: socket ignored
| gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
| gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored
These are harmless, but you can exclude them, too, if you'd like.
Minor correction: they are harmless indeed, but you do not need
to exclude them, because Amanda expects that output, and classifies
it as normal. You will not see these normal lines in the report
unless there are also error or strange lines.
Each output line of the dumpprogram (gtar above) is classified
as normal All the other lines are flagged with a question mark.
When the return code of gtar indicates success, but contains
unexpected lines, Amanda flags the dump as strange, but still puts
in on tape. Amanda leaves it up to you to interpret the strange
lines, and see if they are harmful or not.
When the return code of gtar indicates a failure, those non-normal
output lines are probably the cause of the error.
When informing you about strange or error in the report, Amanda
always shows the complete output, including the normal lines, to
allow you to interpret those lines in the context.
