On Fri, Dec 14, 2007 at 08:11:14AM -0800, Tom Herrera wrote:
>
> 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]
The "why" is shown below.
Tar exits "2" with lots of minor errors during a backup.
It exits "1" on real failures, syntax errors etc.
BTW on Unix/Linux, exit (aka return) of "0" is the
norm, indicating success.
>
>
> 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.2 10241.0 0.2
> Original Size (meg) 16661.7 16658.7 3.0
> Avg Compressed Size (%) 44.4 44.5 8.4 (level:#disks ...)
> Filesystems Dumped 10 7 3 (1:2 2:1)
> Avg Dump Rate (k/s) 1943.5 1980.2 2.6
>
> Tape Time (hrs:min) 2:21 2:21 0:00
> Tape Size (meg) 10241.6 10241.2 0.3
> Tape Used (%) 51.3 51.3 0.0 (level:#disks ...)
> Filesystems Taped 10 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
The lines below have leading either "?" or "|".
The "|" would not have caused the "failed and strange"
report to print and are just along for the ride because
other more serious things are being reported, the ones
with the "?".
> ? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
> ? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
So these are the only problems. Likely no CD was installed.
I'd suggest you add an exclude option for /mnt/cdrom.
> | 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:
Notes are just that, info for you. But one is important.
> 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.
This is pretty important. Why don't you have multiple full dumps
on tape?
> planner: Dump too big for tape: full dump of
> brain.milw.nvisia.com:/mnt/archive_vol/home delayed.
This is the big one to pay attention to. Amanda backs up entities
called Disklist Entries (DLEs) named after the "disklist" file.
Until recent versions of amanda, a full dump of each DLE had to
be smaller than a single tape; amanda did not split dumps across
tapes. The default is still to not split dumps. So for this
DLE, a full dump is needed but can't be done because it won't
fit. Either get bigger tapes :), make this multiple DLEs using
the exclude/include methods, or upgrade amanda and configure
for tape spanning.
> 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 STATS TAPER STATS
> HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> -------------------------- --------------------------------- ------------
> brain.milw.n / 0 FAILED ---------------------------------------
> brain.milw.n /boot 0 6592 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 2 2110 224 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 /opt 0 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 jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
