failure & strange dump
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.
Re: How to determine cause of Amanda slowdown?
Well, so much for the NIC and switch causing the amanda slowdown. I changed the settings on my NIC last night before the amanda run to 100baseT-FD. However, the dump is still running now, 15 hours later. I'm going to examining the switch shortly to see if there were many errors or collisions. Here's what amstatus said a few minutes ago: amanda@admin:~ > amstatus DailySet1 Using /var/log/amanda/DailySet1/amdump from Thu Aug 8 18:00:00 EDT 2002 admin://db/c$1 380k finished (18:14:30) admin://db/e$1 10k finished (18:13:21) admin://db/f$0 7066846k wait for dumping admin:sda1 1 10k finished (18:13:37) admin:sda3 13085k wait for dumping admin:sdb1 03970k finished (18:13:54) centernet:sda1 02975k finished (18:16:12) centernet:sda3 0 1564325k finished (8:22:23) centernet:sdb1 11581k finished (18:14:42) centernet:sdb2 0 70452k finished (18:52:25) centernet:sdc1 1 1k finished (18:13:22) cgi:hda1 02294k finished (18:13:56) cgi:hda3 0 604189k finished (8:39:55) kzlaptop:hda504181k finished (18:16:44) kzlaptop:hda711926k finished (18:16:16) mailinglists:hda10 943k finished (18:15:37) mailinglists:hda217725k finished (18:18:42) mailinglists:hda71 41k finished (18:15:24) virtual:hda1 0 944k finished (18:13:35) virtual:hda3 0 1432404k writing to tape (8:57:43) www2:sda10 0 [Request to www2 timed out.] www2:sda11 0 [Request to www2 timed out.] www2:sda50 [Request to www2 timed out.] www2:sda70 [Request to www2 timed out.] www2:sda80 [Request to www2 timed out.] www2:sda90 [Request to www2 timed out.] SUMMARY part real estimated size size partition : 26 estimated : 0 0k failed : 6 0k ( 0.00%) wait for dumping: 27069931k ( 0.00%) dumping to tape : 0 0k ( 0.00%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 18 3698351k 4633924k ( 79.81%) ( 0.00%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 1 1432404k 1342192k (106.72%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 17 2265947k 3291732k ( 68.84%) ( 0.00%) 8 dumpers idle : no-diskspace taper writing, tapeq: 0 network free kps: 2600 holding space : 2062091k ( 59.01%) dumper0 busy : 14:14:54 ( 96.67%) dumper1 busy : 13:38:37 ( 92.57%) dumper2 busy : 0:05:06 ( 0.58%) dumper3 busy : 14:44:22 (100.00%) dumper4 busy : 0:03:14 ( 0.37%) dumper5 busy : 0:00:59 ( 0.11%) taper busy : 0:42:07 ( 4.76%) 0 dumpers busy : 0:00:00 ( 0.00%) 1 dumper busy : 0:28:59 ( 3.28%)no-bandwidth: 0:28:59 (100.00%) 2 dumpers busy : 0:36:32 ( 4.13%)no-bandwidth: 0:36:32 (100.00%) 3 dumpers busy : 13:33:43 ( 92.01%)no-bandwidth: 13:33:42 (100.00%) 4 dumpers busy : 0:02:06 ( 0.24%)no-bandwidth: 0:01:54 ( 90.50%) start-wait: 0:00:12 ( 9.50%) 5 dumpers busy : 0:02:30 ( 0.28%)no-bandwidth: 0:02:03 ( 82.11%) client-constrained: 0:00:25 ( 17.09%) start-wait: 0:00:01 ( 0.80%) 6 dumpers busy : 0:00:30 ( 0.06%)no-diskspace: 0:00:15 ( 49.47%) no-bandwidth: 0:00:12 ( 40.64%) client-constrained: 0:00:02 ( 6.82%) amanda@admin:~ > In the first section, the admin://db/f$ is a samba connection to a Windows NT host through the tapebackup host. The F: drive is primarily one huge database file. The admin:sda3 is the root directory on the tapebackup host itself. I should have commented out www2, since I know it's a dead host. What's the meaning of this line in the second section: "8 dumpers idle : no-diskspace" Is this an error message? Should I try to allocate more disk space to the dump disk? Do the last lines about 1-6 dumpers busy, due to no-bandwidth indicate that I need to increase the netusage? I currently have "netusage 1200 Kbps # maximum net bandwidth for Amanda, in
Re: amdump and tar don't work
On Fri, 9 Aug 2002, thomas holstein wrote: >FAILURE AND STRANGE DUMP SUMMARY: > samson.hei /dev/da0s1e lev 0 FAILED [disk /dev/da0s1e offline on >samson.heitec.net?] You must give tar directory names, not disk devices. Rather than /dev/da0s1e you need to tell tar to backup /var or whereever that partition happens to be mounted. Modify your disklist to reflect this. -- 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]
Re: failure & strange dump
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. > > > >
Re: failure & strange dump
On Fri, Aug 09, 2002 at 05:17:09PM +0100, 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. > > > If your "always-full" dumptype uses tar and not some dump program it is fine. If always-full is using a dump program I believe that the disklist entry has to be the root directory of a file system or the device name for the file system. In the case that /tmp is a separate file system (my solaris system has this) your disklist is fine for either program. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Auantum DLT8000 Configuration
Where can I find the informaiton needed to add a Quantum DLT8000 to the amanda.conf. It's a 40/80 GB DLT drive. I'd appreciate any info. Thanks. BryanDo You Yahoo!? HotJobs, a Yahoo! service - Search Thousands of New Jobs
Re: failure & strange dump
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. >>> >> > >
Changing the number of tapes in the middle of a backup schedule
I have my backup running with just 3 tapes right now. I am trying to get some more tapes but these DLT IV tapes are expensive, so can I add tapes to the middle of a run if I get them later? Thanks. -Bryan P.S. Thanks Chris for the heads up on the FAQ-O-Matic on AMANDA.org. Found the tape configuration while I was waiting for the response email.Do You Yahoo!? HotJobs, a Yahoo! service - Search Thousands of New Jobs
Re: Changing the number of tapes in the middle of a backup schedule
yup I've added tapes after running a config for a few weeks without any problem. You think DLT's are expensive, try buying a couple of Ultrium tapes! :-) Bryan H wrote: I have my backup running with just 3 tapes right now. I am trying to get some more tapes but these DLT IV tapes are expensive, so can I add tapes to the middle of a run if I get them later? Thanks. -Bryan P.S. Thanks Chris for the heads up on the FAQ-O-Matic on AMANDA.org. Found the tape configuration while I was waiting for the response email. Do You Yahoo!? HotJobs, a Yahoo! service - Search Thousands of New Jobs -- Scott Sanders Systems Administrator Concepts Direct, Inc. 2950 Colorful Ave. Longmont, CO 80504 (303) 682-7110 Phone (303) 682-7140 Fax
SCO unix with "large" filesystems planner request times out....
Hi again group, I'm fighting (and losing) a battle with a SCO unix system and amanda client. Every thing appears to be working correctly (ha...ha...ha). 'amcheck' comes backup without errors. The server can backup all my linux and windows NT servers fine and without compliant. gnutar has recently been updated to 1.13.25. When I run 'amdump' I can see the tar "scheduling" command running on the SCO machine. I'm attempting to backup 4 filesystems all are on a compaq raid controller. two are about 9 GB and two are 45 GB and they are about 85-90% full. Every time I run the dump I can 'tail -f /tmp/amanda/sendsize.[date,time].debug' and watch it time out on the first 45 GB filesystem it tries to schedule. Is there somewhere I can give the server a longer time-out value? The tar process: --snip-- root 994 584 43 13:30:47 ?00:05:18 /usr/local/bin/tar --create --file /dev/null --directory /u3 --one-file-system --snip-- The sendsize.*.debug file: --snip-- sendsize: debug 1 pid 584 ruid 802 euid 802 start time Fri Aug 9 13:15:35 2002 /usr/local/libexec/sendsize: version 2.4.2p2 calculating for amname '/u', dirname '/u' sendsize: getting size via gnutar for /u level 0 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /usr/local/bin/tar --create --file /dev/null --directory /u --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/newbrian.sebis.com_u_0.new --sparse --ignore-failed-read --totals . Total bytes written: 7861975040 (7.3GB, 8.2MB/s) . calculating for amname '/u3', dirname '/u3' sendsize: getting size via gnutar for /u3 level 0 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /usr/local/bin/tar --create --file /dev/null --directory /u3 --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/newbrian.sebis.com_u3_0.new --sparse --ignore-failed-read --totals . --snip-- If more info is required please email me. thanks, chrisj
tapetype for Storagetek L40 with bundled Seagate Viper 200 drives.
Just in case someone needs this. Took around 3 hours to complete.
define tapetype StoragetekL40 {
comment "just produced by tapetype program"
comment "LTO drive: Seagate Viper 200 STU42001LW-K"
length 100193 mbytes
filemark 704 kbytes
speed 14912 kbytes
}
missing result for / in samba2 response
O.k. so I see this problem in the FAQ, but the answer doesn't appear to help me. I never did get "dump" working, no matter that all the permissions are right etc dump won't work. I'm going with tar, well tar isn't working on the remote machines either, even though amcheck doesn't fail and finds no problems. Here's amcheck output: amanda@backup:/etc/amanda/Daily$ amcheck Daily Amanda Tape Server Host Check - Holding disk /usr/local/amanda/dumps: 2976096 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet1-1 label ok NOTE: info dir /etc/amanda/Daily/curinfo/samba2/_: does not exist NOTE: index dir /etc/amanda/Daily/index/samba2/_: does not exist Server check took 4.547 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.038 seconds, 0 problems found (brought to you by Amanda 2.4.3b3) This stuff is from the log file: START driver date 20020809 DISK planner backup / DISK planner backup /home DISK planner backup /usr DISK planner backup /var DISK planner samba2 / START planner date 20020809 INFO planner Adding new disk samba2:/. START taper datestamp 20020809 label DailySet1-1 tape 0 FAIL planner samba2 / 20020809 0 [missing result for / in samba2 response] FINISH planner date 20020809 STATS driver startup time 61.796 SUCCESS dumper backup /home 20020809 1 [sec 0.067 kb 1 kps 14.9 orig-kb 10] Below is the full amdump.1 file amdump: start at Fri Aug 9 21:01:33 CDT 2002 amdump: datestamp 20020809 planner: pid 12917 executable /usr/local/libexec/planner version 2.4.3b3 planner: build: VERSION="Amanda-2.4.3b3" planner:BUILT_DATE="Fri Aug 9 01:08:35 CDT 2002" planner:BUILT_MACH="Linux backup.sistina.com 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown" planner:CC="gcc" planner:CONFIGURE_COMMAND="'./configure' '--with-portrange=5,50100' '--with-udpportrange=850,860' '--with-user=amanda' '--with-group=disk' '--sysconfdir=/etc' '--with-tape-device=/dev/st0'" planner: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" planner:libexecdir="/usr/local/libexec" mandir="/usr/local/man" planner:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" planner:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/" planner:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" planner:RESTORE="/sbin/restore" GNUTAR="/bin/gtar" planner:COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" planner:MAILER="/usr/bin/Mail" planner:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" planner: defs: DEFAULT_SERVER="backup.sistina.com" planner:DEFAULT_CONFIG="DailySet1" planner:DEFAULT_TAPE_SERVER="backup.sistina.com" planner:DEFAULT_TAPE_DEVICE="/dev/st0" HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE planner:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS planner:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" planner: dgram_bind: socket bound to 0.0.0.0.851 READING CONF FILES... startup took 0.007 secs SETTING UP FOR ESTIMATES... setting up estimates for backup:/ setup_estimate: backup:/: command 0, options: last_level 0 next_level0 28 level_days 0 getting estimates 0 (65550) 1 (0) -1 (-1) setting up estimates for backup:/home setup_estimate: backup:/home: command 0, options: last_level 0 next_level0 28 level_days 0 getting estimates 0 (10) 1 (0) -1 (-1) setting up estimates for backup:/usr setup_estimate: backup:/usr: command 0, options: last_level 0 next_level0 28 level_days 0 getting estimates 0 (1023820) 1 (0) -1 (-1) setting up estimates for backup:/var setup_estimate: backup:/var: command 0, options: last_level 0 next_level0 28 level_days 0 getting estimates 0 (86230) 1 (0) -1 (-1) setting up estimates for samba2:/ samba2:/ overdue 11909 days for level 0 setup_estimate: samba2:/: command 0, options: last_level -1 next_level0 -11909 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates took 0.001 secs GETTING ESTIMATES... driver: pid 12918 executable /usr/local/libexec/driver version 2.4.3b3 driver: send-cmd time 0.012 to taper: START-TAPER 20020809 driver: started dumper0 pid 12920 driver: started dumper1 pid 12921 driver: started dumper2 pid 12922 driver: started dumper3 pid 12923 taper: pid 12919 executable taper version 2.4.3b3 dumper: dgram_
dd gets tape native capacity, amanda (sometimes) dosen't
I'm running Amanda 2.4.2p2 (modified from the Debian 2.4.2p2-4 packages)
on Linux with a Seagate STT2A IDE tape (via the scsi-emulation
driver) and 10GB native Travan tapes. I'm using software compression -
hardware compression is (or should be) off.
I recently added another host with about 9GB of data to my backup
routine. Most of the data is mounted from a NetWare box. I've split the
volumes into 1-2 GB chunks with tar.
Some nights, to some tapes, my backups run fine. I get about 8 GB dumped
to tape:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:17
Run Time (hrs:min) 7:26
Dump Time (hrs:min)6:59 5:49 1:10
Output Size (meg)8297.0 7495.6 801.4
Original Size (meg) 14403.412933.6 1469.7
Avg Compressed Size (%)57.6 58.0 54.1 (level:#disks ...)
Filesystems Dumped 30 6 24 (1:23 2:1)
Avg Dump Rate (k/s) 337.6 366.5 194.1
Tape Time (hrs:min)5:15 4:21 0:54
Tape Size (meg) 8298.0 7495.8 802.2
Tape Used (%) 87.8 79.38.5 (level:#disks ...)
Filesystems Taped30 6 24 (1:23 2:1)
Avg Tp Write Rate (k/s) 449.3 489.8 253.2
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
bluebird / 1 250 32 12.8 0:14 2.3 0:07 9.2
bluebird /etc1 210 32 15.2 0:06 5.3 0:02 27.3
bluebird /users1 0 64691703377568 52.2 87:48 641.1 87:49 641.0
bluebird /usr14450384 8.6 0:07 56.4 0:04 117.6
bluebird /var1 91860 8832 9.6 0:27 328.2 0:24 363.1
goldfinch/ 12930480 16.4 1:17 6.2 0:05 109.7
goldfinch/etc1 100 32 32.0 0:12 2.8 0:04 14.3
goldfinch/home 1 10 32 320.0 0:05 6.0 0:03 23.5
phoenix / 12220224 10.1 1:37 2.3 0:03 96.2
phoenix /etc1 96 96 --0:08 11.8 0:03 44.0
phoenix /var1 13344 13344 --0:49 274.9 0:34 394.6
pokey/ 1 200 32 16.0 0:02 17.0 0:02 26.6
pokey/boot 1 10 32 320.0 0:01 43.0 0:15 4.2
pokey/etc1 170 32 18.8 0:02 19.8 0:03 21.6
pokey-etware/SYS 1 959090 523904 54.6 35:33 245.7 21:54 398.7
pokey-tware/VOL1 1 27100 9024 33.3 0:57 157.0 0:22 405.5
pokey-1/SOFTWARE 1 302190 252224 83.5 13:54 302.5 28:46 146.1
pokey-VOL1/users 0 1957080 981888 50.2 78:18 209.0 57:32 284.4
pokey-rs/COLLECT 0 1019770 448800 44.0 35:13 212.4 23:40 316.1
pokey-ers/COMMON 01840736 40.0 0:05 160.0 0:05 148.9
pokey-s/JMCGOWAN 0 20643401596320 77.3 92:07 288.8 44:57 592.0
pokey/usr13380320 9.5 0:50 6.4 0:03 109.3
pokey/var17350 2528 34.4 0:09 285.1 0:07 376.7
raven/ 1 120 32 26.7 0:01 41.2 0:03 22.3
raven/boot 1 10 32 320.0 0:00 120.8 0:02 26.9
raven/etc1 140 32 22.9 0:02 16.1 0:06 10.9
raven/users1 0 17318401270176 73.3 55:31 381.3 47:06 449.4
raven/usr27870672 8.5 7:31 1.5 0:05 133.8
raven/var1 68290 7456 10.9 1:20 93.4 0:38 199.4
raven/www1 13610864 6.3 5:05 2.8 0:08 107.6
umnhpc87 /Users 0 FAILED ---
umnhpc87 /etc0 FAILED ---
umnhpc87 /var0 FAILED ---
(Ignore umnhpc87 - someone turned it off)
But other days, to other tapes, I run out of tape at about 5 GB:
These dumps were to tape umnh-2002-1.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: umnh-20011129-1.
FAILURE AND STRANGE DUMP SUMMARY:
pokey /netware/VOL1/users lev 1 FAILED [out of tape]
pokey /netware/VOL1/users lev 1 FAILED ["data write: Broken pipe"]
pokey /netware/VOL1/users lev 1 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:17
Run Time (hrs:min) 9:55
Dump Time (hrs:min)5:29 5:17 0:11
Output Size (meg)5167.4 5094.2 73.2
Original Size (meg) 8768.4 8539.0 229.4
Re: SCO unix with "large" filesystems planner request times out....
On Friday 09 August 2002 15:45, Chris Johnson wrote: >Hi again group, >I'm fighting (and losing) a battle with a SCO unix system and >amanda client. Every thing appears to be working correctly >(ha...ha...ha). 'amcheck' comes backup without errors. The server > can backup all my linux and windows NT servers fine and without > compliant. gnutar has recently been updated to 1.13.25. When I > run 'amdump' I can see the tar "scheduling" command running on > the SCO machine. I'm attempting to backup 4 filesystems all are > on a compaq raid controller. two are about 9 GB and two are 45 GB > and they are about 85-90% full. Every time I run the dump I can > 'tail -f /tmp/amanda/sendsize.[date,time].debug' and watch it > time out on the first 45 GB filesystem it tries to schedule. >Is there somewhere I can give the server a longer time-out > value? Yes, its one of the *timeout values in amanda.conf. Depending on which phase, estimate or the actual dump is timing out, you can rather arbitrarily double those until the error goes away. It sounds like the estimate phase is being a problem right now, so I'd start by doubleing the 'etimeout' value. With 45 gigs mostly full, even doubling it might not be sufficient, depending on how fast the machine and its drives are. You could make it arbitrarily large, then check the email to see how long it actually took and set etimeout to about 125% of that. [...] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.10% setiathome rank, not too shabby for a WV hillbilly
Re: dd gets tape native capacity, amanda (sometimes) dosen't
On Friday 09 August 2002 17:37, Will Aoki wrote: >I'm running Amanda 2.4.2p2 (modified from the Debian 2.4.2p2-4 > packages) on Linux with a Seagate STT2A IDE tape (via the > scsi-emulation driver) and 10GB native Travan tapes. I'm using > software compression - hardware compression is (or should be) > off. > >I recently added another host with about 9GB of data to my backup >routine. Most of the data is mounted from a NetWare box. I've > split the volumes into 1-2 GB chunks with tar. > > >Some nights, to some tapes, my backups run fine. I get about 8 GB > dumped to tape: [...] >'dd' fits about 10GB of data to the tape, approximately equal to > its native capacity. If hardware compression were on, I'd expect > more, so I infer that hardware compression is off. But, when I > re-amlabel the tape and run dumps to it again, I still only get 5 > GB. > > >I can think of these possibilities: > > 1 Amanda is not correctly reporting the amount of data it > dumped to tape. (But tape time seems to increase with reported > data taped, making this less likely.) > 2 Something is switching compression on and off behind my > back. I suspect this is the case as once a tape has been written to with the compression on, its a female dog to get it shut off. > 3 Hardware compression is on, but is so poor that it > can't compress a stream of 0x0s, making my test for compression > fail. The std test for the hardware compression isn't /dev/zero which a tape drives hardware 2-7 RLL can smunch quite well IIRC, but from /dev/urandom which isn't touchable by almost any compression method with most causing a rather heavy expansion, sometimes as much as doubling size of the data on the tape. The util program 'tapetype' can tell you if its on because the tape will hold much less (40-60%) than the advertised amount of data. If the compression is truely off, then its rather closer to 90%. It uses /dev/urandom as the test data source. Now, if the tape is turning its own compression back on, the only cure that I've been able to make work is to dd the tape label to a scratch file, rewind the tape, use mt to shut off all known methods of compression, and then use dd with if=/dev/zero and of=/dev/tape count=525,000 ( or more, the idea being to *make* the drive flush the buffers to tape) at which point any compression flags that might be set in the tape header you can't see, will be turned off. Once a few dozen megs have been written, the tape can be rewound and dd used to restore the label. At this point the compression should be defaulted to off *for that tape*. Obviously this needs to be done to all tapes in the rotation. > 4 On some, but not all, of my supposedly-identical tapes, > my drive uses 100MB filemarks. That might be something in the factory formated header for that tape brand. Generally its ignoreable. > 5 The tape gnomes are switching out my tapes at night while > I'm asleep. I've had them forget to switch tapes quite a few times, does that count? :-) Now, since this is a large post, I'm gonna snip, a lot... Above and below. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.10% setiathome rank, not too shabby for a WV hillbilly
Re: dd gets tape native capacity, amanda (sometimes) dosen't
Pulling individual lines from a long message: On Fri, Aug 09, 2002 at 03:37:32PM -0600, Will Aoki wrote: > Some nights, to some tapes, my backups run fine. I get about 8 GB dumped > to tape: > > But other days, to other tapes, I run out of tape at about 5 GB: > Note this line from your failed report: > taper: tape umnh-2002-1 kb 9590432 fm 33 writing file: No space left on device It says 9.6GB of data plus 33 file marks were written before the error. Not 5GB. Now, your file system by file system list shows an output size (after compression) of 5.3GB plus one failed file system. Those 5.3GB were "successfully written" as evidenced by the completed "taper" statistics. My guess about the failed entry is that it is a very large file system, more than 4GB after compression. Further, I think there is insufficient holding disk space to receive that system dump. Thus it was being dumped directly to tape. I say this because there is no dumper data. A dump to the holding disk must complete before transfer to tape begins. As taping was in progress, yet there is no dumper data, the dump must be going directly to tape. Otherwise there would be dumper data and dumps left on the holding disk available for amflush. Basically some days you are backing up more data than a single tape can hold and are not using multiple tapes per run. Plus, some of your systems will not fit the holding disk. About the holding disk space, how big is it and what percent is "reserved"? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
