amidxtaped: amrestore terminated normally with status: 2
Can some explain why this failed and if I can still restore the file I need? Load tape daily007 now Continue? [Y/n]: y EOF, check amidxtaped.debug file. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 **amidxtaped.debug*** amidxtaped: debug 1 pid 22957 ruid 542 euid 542 start time Thu Jul 12 12:37:26 2001 amidxtaped: version 2.4.1p1 SECURITY USER root bsd security: remote host admin1.corp.walid.com user root local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/rmt/0bcn admin1.corp.walid.com ^/dev/hdg1$ 20010708 Ready to execv amrestore with: path = /usr/local/pkg/amanda-2.4.1p1/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = /dev/rmt/0bcn argv[4] = admin1.neptune.com argv[5] = ^/dev/hdg1$ argv[6] = 20010708 amrestore: could not open tape /dev/rmt/0bcn: No such file or directory amidxtaped: amrestore terminated normally with status: 2 amidxtaped: could not stat /dev/rmt/0bcn
somehow the .rhosts file was deleted
All the more reason to have amanda complain about access problems! Thanks to all of you for your responses. You were right about not trusting their answers. :-) -- Denise E. [EMAIL PROTECTED] Systems Engineer734.822.2037 Download the free WALID WorldConnect software and start using ML.ML domain names today. http://www.walid.com
Solaris 8 s28_38shwp2 SPARC
All, Just this past week out of the blue amanda on sunny1 (tapeserver) is returning access denied. I inquired to the group of admins here if anything had changed on this box or if any outages occured but they have responded with 'no'. I've checked host IP entries in /etc/host amanda entires in /etc/inetd.conf the .amandahosts entry and still can not figure out this access problem we are having. Any help? Amanda Backup Client Hosts Check ERROR: sunny1.neptune.com: [access as amanda not allowed from [EMAIL PROTECTED]] -- Denise E.
backing up mounted filesystems
Is amanda capable of backing up mounted filessystems? -- Denise E. [EMAIL PROTECTED] Systems Engineer734.822.2037 Download the free WALID WorldConnect software and start using ML.ML domain names today. http://www.walid.com
xinetd set up and my Linux box
Amcheck ran fine the day I added 'groups = yes' to xinetd amanda entry on
both and ran /etc/xinetd restart for both new linux boxes.
Just last night I scheduled a level 0 for these boxes.
{sunny2 and sunny3}
Sunny2's back up went well but sunny3 returned the 'infamous' access
error.
ERROR: sunny3.neptune.com: [access as amanda not allowed from
[EMAIL PROTECTED]]
I verified with other admins that nothing has been changed wrt the amanda
configuration or xinetd on sunny3. Then checked myself.
*checks performed**
sunny3%
groups amanda
amanda : amanda disk
sunny3%
/home/src-admin3/amanda/amanda-2.4.1p1/.amandahosts
sunny3%
more /etc/hosts
XXX.XX.XX sunny1.neptune.com sunny1
XXX.XX.XX sunny3.neptune.com sunny3
sunny1%
more /etc/hosts
XXX.XX.XX sunny1.neptune.com sunny1
XXX.XX.XX sunny3.neptune.com sunny3
Any thoughts?
ERROR [can not access /dev/hdg1 (/dev/hdg1): Permission denied]
I corrected the ~amanda .amandahosts access issue by changing amandas default home dir. I still get access Errors on the partitions for my newly added clients. I have tried using both hdg1 and /dev/hdg1 in the disk list. Amanda Backup Client Hosts Check ERROR: sunny3.neptune.com: [can not access /dev/hdg1 (/dev/hdg1): Permission denied] ERROR: sunny2.neptune.com: [can not access /dev/hda1 (/dev/hda1): Permission denied] sunny3 is running REDHAT 7.1 sunny2 is running REDHAT 7.0
Re: xinetd set up and my Linux box
Got it - something was changed - /path/of/amanda's home dir thank you again On Wed, 13 Jun 2001, John R. Jackson wrote: ERROR: sunny3.neptune.com: [access as amanda not allowed from [EMAIL PROTECTED]] This says sunny3 would not let user amanda in from sunny1. First, make sure this line is file .amandahosts in directory ~amanda (the home directory of user amanda) on sunny3: sunny1.neptune.com amanda Next, make sure the file is owned by amanda and that it is mode 0600 or 0400. Then make sure all the directories down to the file allow read/execute for user Amanda or a group it is a member of (or everything). One way to do that is run this as root on sunny3: # su amanda cat ~amanda/.amandahosts Next, take a look at an amandad*debug file after doing an amcheck (use the -c option to just do the client checks) and see what it has to say. And while you're at it, see if the access time on ~amanda/.amandahosts on sunny3 is being updated with ls -lu. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. [EMAIL PROTECTED] Systems Engineer734.822.2037 Download the free WALID WorldConnect software and start using ML.ML domain names today. http://www.walid.com
Why does `amcheck' say `access as USERNAME not allowed...'
I read through all posted FAQ's on this. I checked config.status to make sure I ran --with-amandahosts option set up .amandahosts with qualified names chown of .amandahosts to amanda:amanda and set mode to 0600 restarted inetd and amcheck returned these results: Amanda Backup Client Hosts Check ERROR: sunny3.neptune.com: [access as amanda not allowed from [EMAIL PROTECTED]] ERROR: sunny2.corp.walid.com: [access as amanda not allowed from [EMAIL PROTECTED]] Client check: 2 hosts checked in 0.019 seconds, 2 problems found. getting closer?
Re: Why does `amcheck' say `access as USERNAME not allowed...'
Yes
On Wed, 6 Jun 2001, Bernhard R. Erdmann wrote:
Denise Ives wrote:
I read through all posted FAQ's on this.
I checked config.status to make sure I ran --with-amandahosts option
set up .amandahosts with qualified names
chown of .amandahosts to amanda:amanda
and set mode to 0600
restarted inetd and amcheck returned these results:
Amanda Backup Client Hosts Check
ERROR: sunny3.neptune.com: [access as amanda not allowed from
[EMAIL PROTECTED]]
ERROR: sunny2.corp.walid.com: [access as amanda not allowed from
[EMAIL PROTECTED]]
Client check: 2 hosts checked in 0.019 seconds, 2 problems found.
Did you put the line
sunny1.neptune.comamanda
in ~amanda/.amandahosts on sunny{2,3}.neptune.com?
Amcheck troubleshooting
I added another client to be backed up to my disklist ran amcheck and generated this problem message. can not access hdg1 (hdg1): No such file or directory
Re: Thank you again
Files restored with no problem at all. On Fri, 1 Jun 2001, John R. Jackson wrote: Amanda backs-up both machines and the solaris machine (the host) has my tape unit configured on it. Understood. Can I not restore client images to the client machine? (since my host and client machines are different) Yes, you can do this. But that doesn't appear to be what you're doing. Amrecover tried to run ufsrestore. It would only do that when amrecover was running from a Solaris box. But you said the client is a Linux box. You need to run amrecover on the client (the Linux box). It will reach out to the tape server (Solaris box) and read the tape from there. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amrestor -ing 3 files but can't find em
As root from the / directory on the tape host I run amrecover -C daily -s sunny1 -t sunny1 -d /dev/rmt/0cbn amrecover sethost to sunny#2 200 Dump host set sunny#2 amrecover setdisk to sda10 200 Disk set to sda10. amrecover cd web /web amrecover cd bin /web/bin ###When I do an ls I see the files I want amrecover add file1.sh Added /web/bin/file1.sh amrecover extract Extracting files using tape drive /dev/rmt/0cbn on host sunny1 The following tapes are needed: daily119 Restoring files into directory / Continue? [Y/n]: y Load tape daily119 now Continue? [Y/n]: y amrecover Did amrecover restore the file? I looked on sunny1 in the root dir and on sunny2 in /web/bin but I am unable to locate the file I am trying to restore. thanks,
core:
ELF 32-bit MSB core file SPARC Version 1, from 'ufsrestore gdb ufsrestore GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as sparc-sun-solaris2.8...(no debugging symbols found)... (gdb)
tape host is solaris and one client running linux
I can restore all images/files backed-up via the solaris box but Tape Host SunOS sundev1 5.8 Generic sun4u sparc SUNW,Ultra-60 Client Linux 6.2 I can restore all files on my Sun box. However, Amanda generates a core file every time I try to restore back-ups of the client.
adding a thrid client to be backed up
ERROR: sunny3.neptune.com: [access as amanda not allowed from [EMAIL PROTECTED]] Client check: 1 host checked in 0.014 seconds, 1 problem found. box has been added to both /etc/hosts file Anythoughts?
adding a thrid client
I tried adding the .amandahostfile for sunny1 to in the sunny3 /usr/local and /home/src/amanda/amanda-2.4.1p1 directories - chown root:amanda and I am still getting the same access as amanda not allowed from [EMAIL PROTECTED] Am I placing the .amadnahost file in the correct locaiton? I am reading the FAQ's now.
Re: listing files with amrecover - No index records for disk (fwd)
I was not in my root directory when I ran amrecover initially. When I moved to my root directory and then ran amrecover - I was able to view the tree of files/directories via the 'ls' command on my tape. thanks much: amadmin daily disklist cloudy1.com sda6 | grep index index YES -- Forwarded message -- Date: Fri, 23 Feb 2001 19:19:59 -0500 From: John R. Jackson [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Denise Ives [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: listing files with amrecover - No index records for disk 200 Dump host set to cloudy1.com. amrecover ls Must select a disk before listing files amrecover setdisk sda6 501 No index records for disk: sda6. Invalid? First, find your index directory. Is there a directory in it named "cloudy1.com"? Is there a directory in that directory named "sda6"? And finally, are there gzip'd files in there? What do you get for this: amadmin config disklist cloudy1.com sda6 | grep index Does it say you've been gathering index files? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
listing files with amrecover - No index records for disk
I haven't used amrecover in a while. I used to be able to list file with the ls command: #my disklist file cloudy1.com sda6default sunny1.com dsa10 default #running amrecover [root@sunny1 dives]# amrecover -C daily -s sunny1.com -t sunny1.com -d /dev/rmt/0cbn AMRECOVER Version 2.4.1p1. Contacting server on sunny1.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2001-02-23) 200 Working date set to 2001-02-23. 200 Config set to daily. 501 No index records for host: sunny1. Invalid? Trying sunny1.com ... 200 Dump host set to sunny1.com. $CWD '/cloudy1-home/user/dives' is on a network mounted disk so you must 'sethost' to the server amrecover sethost cloudy1 501 No index records for host: cloudy1. Invalid? Trying cloudy1.com ... 200 Dump host set to cloudy1.com. amrecover ls Must select a disk before listing files amrecover setdisk sda6 501 No index records for disk: sda6. Invalid?
Re: summary details show errors but dumper stats (fwd)
Is there an Amanda command to verify images sitting in my holding disk space? If not I will just run amrecover. Can amrecover run from an image left in the holding disk space or does that image need to be flushed to tape first? -- Forwarded message -- Date: Wed, 24 Jan 2001 08:18:58 -0800 (PST) From: David Wolfskill [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: summary details show errors but dumper stats Date: Wed, 24 Jan 2001 15:42:57 + (GMT) From: Denise Ives [EMAIL PROTECTED] show sda10 did its level 1 back up. So did sd10 back up with errors? It would appear that a backup image was created, and amanda stored it for you, per your request. The extent to which that image might be useful for actually performing a restore is somewhat open to question, and depending on how important/critical/... the data happen to be to you your employers, you might want to do some sort of reality check, at the very least. I'd suggest doing the reality check well prior to a time that the data might actually be perceived to be needed. Cheers, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 I need help: http://www.whistle.com/employment/employ-engg.html#K030391
strange dump details - (again)
My Amanda level 1 back-ups are failing consistanly on one of my drives. However there is small amounts of activity going on during the time amanda dump. Sometimes I have mtrg running in the background backing up files and folders - do you think that is the cause of these errors here? Or is there some other animal causig this evil? ? FAILED AND STRANGE DUMP DETAILS: /-- sda10 lev 1 FAILED [/sbin/dump returned 3] sendbackup: start [:sda10 level 1] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | DUMP: Date of this level 1 dump: Mon Jan 22 06:14:47 2001 | DUMP: Date of last level 0 dump: Sat Jan 20 07:32:06 2001 | DUMP: Dumping /dev/sda10 (/home) to standard output | DUMP: Label: none | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 586178 tape blocks. | DUMP: Volume 1 started at: Mon Jan 22 06:16:33 2001 | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/sda10: [block -2097472760]: count=4096, got=0 ? DUMP: short read error from /dev/sda10: [sector -2097472753]: count=512, got=0 ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails To: Denise Ives [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: strange dump summary - can you explain this? ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/sda10: [block -2122605784]: count=2048, got=0 This is typical of dumping an active file system. In particular, if the dump program knows it needs to read an indirect block of disk addresses and the file is removed/reallocated and that block reused for data, all those pointers (disk block addresses) are garbage and dump gets real unhappy. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: running amverify (a 2nd time)
amverify is stuck right back at the point it seemed to be hanging yesterday: Lights on the tape drive are on but not blinking: Amanda's process activity: ps -ef | grep amanda amanda 29615 29614 2 13:12:42 pts/13 0:26 /usr/local/pkg/amanda-2.4.1p1/sbin/amrestore -h -p /dev/rmt/0cbn amanda 21102 21080 0 12:33:55 pts/13 0:00 -bash amanda 29620 29614 2 13:12:42 pts/13 0:21 cat amanda 29614 21154 0 13:12:42 pts/13 0:00 /bin/sh /usr/local/sbin/amverify daily amanda 21154 21102 0 12:33:59 pts/13 0:00 /bin/sh /usr/local/sbin/amverify daily ps -fu amanda UID PID PPID CSTIME TTY TIME CMD amanda 29615 29614 4 13:12:42 pts/13 0:32 /usr/local/pkg/amanda-2.4.1p1/sbin/amrestore -h -p /dev/rmt/0cbn amanda 21102 21080 0 12:33:55 pts/13 0:00 -bash amanda 29620 29614 3 13:12:42 pts/13 0:27 cat amanda 29614 21154 0 13:12:42 pts/13 0:00 /bin/sh /usr/local/sbin/amverify daily amanda 21154 21102 0 12:33:59 pts/13 0:00 /bin/sh /usr/local/sbin/amverify daily Here is where she is stuck: amanda@sundev1 [amanda] % amverify daily No tape changer... Tape device is /dev/rmt/0cbn... Verify summary to [EMAIL PROTECTED] Defects file is /tmp/amverify.21154/defects amverify daily Thu Jan 18 12:34:01 EST 2001 Using device /dev/rmt/0cbn Volume daily119, Date 20010113 Skipped admin1.corp.walid.com.sda3.20010113.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20010113.0 Skipped admin1.corp.walid.com.sda2.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20010113.0 Skipped admin1.corp.walid.com.sda5.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0 Reading... lsof: We tried to get lsof installed on our solaris box 2 months ago but it failed to run after the install - we got a 32/64 bit error message. More importantly - since amverify is failing - does that imply I will not be able to amrestore/amrecover the image sundev1.corp.walid.com.c0t0d0s7.20010113.0 on this tape? Of course I have not tried to use amrestore/amrecover for any of the files currently on this amanda tape. [daily119] thanks again - -- Forwarded message -- Date: Thu, 18 Jan 2001 00:17:55 -0500 From: John R. Jackson [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Denise Ives [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: running amverify ... is there ayway to find out if amverify was hung or if it was just taking a long time to do its thing? Look for blinking lights on the drive is the first thing that pops to mind :-). Next, I'd get a ps listing of what was running, "ps -fu amanda-user". If you see it sitting on "sleep" repeatedly with no more output, it's probably hung waiting on the drive to go ready or something like that. If it's sitting on GNU tar or dd, it's probably skipping though an image (i.e. doing what it's supposed to). Next, I'd get "lsof": ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/lsof.tar.gz This will let you see what offset various file descriptors are at (among a bajillion other things), so you can run it on whatever processes have the tape open and see if they are moving. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amverify finished - i guess it wasn't hanging afterall?
I guess the image Check on sundev1.corp.walid.com.c0t0d0s7.20010113.0 was what took so long? thoughts... Subject: daily AMANDA VERIFY REPORT FOR daily119 Tapes: daily119 No errors found! amverify daily Thu Jan 18 12:34:01 EST 2001 Using device /dev/rmt/0cbn Volume daily119, Date 20010113 Skipped admin1.corp.walid.com.sda3.20010113.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20010113.0 Skipped admin1.corp.walid.com.sda2.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20010113.0 Skipped admin1.corp.walid.com.sda5.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0 Skipped admin1.corp.walid.com.sda10.20010113.0 (** Cannot do /sbin/dump dumps) End-of-Tape detected.
running amverify
amverify was taking forever so I aborted it is there ayway to find out if amverify was hung or if it was just taking a long time to do its thing? amverify daily Wed Jan 17 17:08:13 EST 2001 Using device /dev/rmt/0cbn Volume daily119, Date 20010113 Skipped admin1.corp.walid.com.sda3.20010113.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20010113.0 Skipped admin1.corp.walid.com.sda2.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20010113.0 Skipped admin1.corp.walid.com.sda5.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0 ** results - amanda report * Subject: daily AMANDA VERIFY REPORT FOR daily119 Tapes: daily119 Errors found: aborted! amverify daily Wed Jan 17 17:08:13 EST 2001 Using device /dev/rmt/0cbn Volume daily119, Date 20010113 Skipped admin1.corp.walid.com.sda3.20010113.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20010113.0 Skipped admin1.corp.walid.com.sda2.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20010113.0 Skipped admin1.corp.walid.com.sda5.20010113.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0 aborted!
strange dump summary - can you explain this?
There was a huge amount of output - so I will only forward you part
of the dump summary from the Amanda Mail Report -
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda10 lev 1 FAILED [/sbin/dump returned 3]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg)1828.2 1705.0 123.2
Original Size (meg) 1828.2 1705.0 123.2
Avg Compressed Size (%) -- -- --
Tape Used (%) 5.14.80.3 (level:#disks ...)
Filesystems Dumped7 4 3 (1:3)
Avg Dump Rate (k/s) 2076.1 2464.8 652.4
Avg Tp Write Rate (k/s) -- -- --
?
FAILED AND STRANGE DUMP DETAILS:
/-- admin1.cor sda10 lev 1 FAILED [/sbin/dump returned 3]
sendbackup: start [admin1.corp.walid.com:sda10 level 1]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 1 dump: Thu Jan 11 06:23:46 2001
| DUMP: Date of last level 0 dump: Sat Jan 6 07:28:54 2001
| DUMP: Dumping /dev/sda10 (/home) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 2364864 tape blocks.
| DUMP: Volume 1 started at: Thu Jan 11 06:24:56 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 40.91% done, finished in 0:07
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: short read error from /dev/sda10: [block
-2122605784]: count=2048, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-2122605784]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-2122605783]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-2122605782]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-2122605781]: count=512, got=0
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: short read error from /dev/sda10: [block
-1452170888]: count=4096, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-1452170888]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-1452170887]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-1452170886]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-1452170885]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-1452170884]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [sector
-1452170883]: count=512, got=0
? DUMP: bread: lseek2 fails!
? DUMP: short read error from /dev/sda10: [block
-1989041720]: count=4096, got=0
? DUMP: More than 32 block read errors from 134577504
? DUMP: This is an unrecoverable error.
? DUMP: fopen on /dev/tty fails: Device not configured
| DUMP: The ENTIRE dump is aborted.
sendbackup: error [/sbin/dump returned 3]
\
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- --
--
admin1.co sda10 1 FAILED
admin1.co sda2 0 1294208 1294208 -- 8:00 2697.8N/A
N/A
admin1.co sda3 0 6048 6048 -- 0:03 2335.3N/A
N/A
admin1.co sda5 1 5248 5248 -- 0:23 227.5N/A
N/A
admin1.co sda6 0 161856 161856 -- 1:10 2327.5N/A
N/A
sundev1.c c0t0d0s0 1 2560 2560 -- 0:38 67.3N/A
N/A
sundev1.c c0t0d0s3 0 283776 283776 -- 2:36 1813.7N/A
N/A
sundev1.c c0t0d0s7 1 118368 118368 -- 2:12 894.5N/A
N/A
(brought to you by Amanda version 2.4.1p1)
No Subject
lists
amanda is working like normal again
There were no problems with amdump's level 0 run last night. sda10 backed-up along with the rest of my partitions. There was no power outage on any of the systems when sda10 failed to dump last weekend. I checked syslogs - etc. and found nothing. Thanks both to Chris and John for constant and helpful feedback. hope you are all not under 14 inches of snow. -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
sendsize.debug, sendbackup.debug, killpgrp.debug
Here are the debug files from December 9th -
Any idea why that 'index tee' Broke?
cat sendbackup.debug
sendbackup: debug 1 pid 17156 ruid 543 euid 543 start time Sat Dec 9
18:53:42 2000
/usr/local/pkg/amanda-2.4.1p1/libexec/sendbackup: got input request: DUMP
sda10 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;
parsed request as: program `DUMP' disk `sda10' lev 0 since
1970:1:1:0:0:0 opt `|;bsd-auth;index;'
waiting for connect on 4288, then 4289, then 4290
got all connections
sendbackup: spawning "/sbin/dump" in pipeline
sendbackup: argument list: "dump" "0usf" "1048576" "-" "/dev/sda10"
sendbackup: started index creator: "/sbin/restore -tvf - 21 | sed -e '
s/^leaf[]*[0-9]*[ ]*\.//
t
/^dir[ ]/ {
s/^dir[ ]*[0-9]*[ ]*\.//
s%$%/%
t
}
d
'"
index tee cannot write [Broken pipe]
cat sendsize.debug
asking killpgrp to terminate
calculating for amname 'sda10', dirname '/home'
sendsize: getting size via dump for sda10 level 0
sendsize: running "/sbin/dump 0sf 1048576 - /dev/sda10"
running /usr/local/pkg/amanda-2.4.1p1/libexec/killpgrp
DUMP: Date of this level 0 dump: Sat Dec 9 17:47:36 2000
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/sda10 (/home) to standard output
DUMP: Label: none
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 11085651 tape blocks.
DUMP: Volume 1 started at: Sat Dec 9 17:47:59 2000
.
cat killpgrp.debug
killpgrp: debug 1 pid 16439 ruid 543 euid 0 start time Sat Dec 9 17:48:02
2000
/usr/local/pkg/amanda-2.4.1p1/libexec/killpgrp: version 2.4.1p1
sending SIGTERM to process group 16439
child process exited with status 3
On Mon, 11 Dec 2000, Chris Karakas wrote:
Denise Ives wrote:
The AMANDA MAIL REPORT showed that sda10 failed but I see no summary log
of this information using amstatus on these 2 logs.
Use the debug files (sendsize.debug, sendbackup.debug etc.), located in
the directory specified by the logdir parameter in your amanda.conf.
--
Denise E. Ives [EMAIL PROTECTED]
Systems Engineer734.822.2037
Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: sendsize.debug, sendbackup.debug, killpgrp.debug
Do you really think we ran out of tape? Subject: daily AMANDA VERIFY REPORT FOR daily001 Tapes: daily001 No errors found! amverify daily Mon Dec 11 16:34:12 EST 2000 Using device /dev/rmt/0cbn Volume daily001, Date 20001209 Skipped admin1.corp.walid.com.sda9.20001209.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda3.20001209.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda6.20001209.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s3.20001209.0 Skipped admin1.corp.walid.com.sda2.20001209.0 (** Cannot do /sbin/dump dumps) Skipped admin1.corp.walid.com.sda5.20001209.0 (** Cannot do /sbin/dump dumps) Checked sundev1.corp.walid.com.c0t0d0s0.20001209.0 Checked sundev1.corp.walid.com.c0t0d0s7.20001209.0 Skipped admin1.corp.walid.com.sda10.20001209.0 (** Cannot do /sbin/dump dumps) End-of-Tape detected. On Mon, 11 Dec 2000, John R. Jackson wrote: Here are the debug files from December 9th - Any idea why that 'index tee' Broke? It's usually a side effect of running out of tape. Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
tapetype SEAGATE-SCORPION-40
tail -30 amdump.1
taper: reader-side: got label daily001 filenum 8
driver: result time 3968.705 from taper: DONE 00-00016 daily001 8 [sec
863.791 kb 3695872 kps 4278.7 {wr: writers 115496 rdwait 0.051 wrwait
859.368 filemark 0.005}]
driver: finished-cmd time 3970.608 taper wrote
sundev1.corp.walid.com:c0t0d0s7
driver: dumping admin1.corp.walid.com:sda10 directly to tape
driver: send-cmd time 3970.608 to taper: PORT-WRITE 00-00017
admin1.corp.walid.com sda10 0 20001209
driver: result time 3970.619 from taper: PORT 34331
driver: send-cmd time 3970.619 to dumper0: PORT-DUMP 01-00018 34331
admin1.corp.walid.com sda10 0 1970:1:1:0:0:0 DUMP |;bsd-auth;index;
driver: state time 3970.619 free kps: 12209 space: 5861972 taper: writing
idle-dumpers: 3 qlen tapeq: 0 runq: 0 stoppedq: 0 wakeup: 86400
driver-idle: not-idle
driver: interface-state time 3970.619 if : free 6809 if HME0: free 1
if LE0: free 1 if LOCAL: free 1
driver: hdisk-state time 3970.619 hdisk 0: free 5861972 dumpers 0
amanda@sundev1 [daily] % tail -30 amdump.1
driver: hdisk-state time 1715.151 hdisk 0: free 118014 dumpers 1
taper: reader-side: got label daily001 filenum 6
driver: result time 2059.485 from taper: DONE 00-00013 daily001 6 [sec
448.321 kb 1687424 kps 3763.9 {wr: writers 52732 rdwait 19.836 wrwait
426.049 filemark 0.002}]
driver: finished-cmd time 2060.727 taper wrote admin1.corp.walid.com:sda5
driver: send-cmd time 2060.806 to taper: FILE-WRITE 00-00015
/dump/amanda/20001209/sundev1.corp.walid.com.c0t0d0s0.0
sundev1.corp.walid.com c0t0d0s0 0 20001209
driver: state time 2060.807 free kps: 13298 space: 1142014 taper: writing
idle-dumpers: 3 qlen tapeq: 0 runq: 1 stoppedq: 0 wakeup: 86400
driver-idle: no-diskspace
driver: interface-state time 2060.807 if : free 7898 if HME0: free 1
if LE0: free 1 if LOCAL: free 1
driver: hdisk-state time 2060.807 hdisk 0: free 1142014 dumpers 1
taper: reader-side: got label daily001 filenum 7
driver: result time 2792.228 from taper: DONE 00-00015 daily001 7 [sec
731.419 kb 2524640 kps 3451.7 {wr: writers 78895 rdwait 60.693 wrwait
667.192 filemark 0.003}]
driver: finished-cmd time 2794.107 taper wrote
sundev1.corp.walid.com:c0t0d0s0
driver: state time 2794.107 free kps: 13298 space: 2166014 taper: idle
idle-dumpers: 3 qlen tapeq: 0 runq: 1 stoppedq: 0 wakeup: 86400
driver-idle: no-diskspace
driver: interface-state time 2794.107 if : free 7898 if HME0: free 1
if LE0: free 1 if LOCAL: free 1
driver: hdisk-state time 2794.107 hdisk 0: free 2166014 dumpers 1
driver: result time 3104.795 from dumper0: DONE 01-00014 3695807 3695840
1389 [sec 1389.214 kb 3695840 kps 2660.4 orig-kb 3695807]
driver: finished-cmd time 3104.912 dumper0 dumped
sundev1.corp.walid.com:c0t0d0s7
driver: send-cmd time 3104.913 to taper: FILE-WRITE 00-00016
/dump/amanda/20001209/sundev1.corp.walid.com.c0t0d0s7.0
sundev1.corp.walid.com c0t0d0s7 0 20001209
driver: state time 3104.913 free kps: 15400 space: 4837972 taper: writing
idle-dumpers: 4 qlen tapeq: 0 runq: 1 stoppedq: 0 wakeup: 86400
driver-idle: no-diskspace
driver: interface-state time 3104.913 if : free 1 if HME0: free 1
if LE0: free 1 if LOCAL: free 1
driver: hdisk-state time 3104.913 hdisk 0: free 4837972 dumpers 0
taper: reader-side: got label daily001 filenum 8
driver: result time 3968.705 from taper: DONE 00-00016 daily001 8 [sec
863.791 kb 3695872 kps 4278.7 {wr: writers 115496 rdwait 0.051 wrwait
859.368 filemark 0.005}]
driver: finished-cmd time 3970.608 taper wrote
sundev1.corp.walid.com:c0t0d0s7
driver: dumping admin1.corp.walid.com:sda10 directly to tape
driver: send-cmd time 3970.608 to taper: PORT-WRITE 00-00017
admin1.corp.walid.com sda10 0 20001209
driver: result time 3970.619 from taper: PORT 34331
driver: send-cmd time 3970.619 to dumper0: PORT-DUMP 01-00018 34331
admin1.corp.walid.com sda10 0 1970:1:1:0:0:0 DUMP |;bsd-auth;index;
driver: state time 3970.619 free kps: 12209 space: 5861972 taper: writing
idle-dumpers: 3 qlen tapeq: 0 runq: 0 stoppedq: 0 wakeup: 86400
driver-idle: not-idle
driver: interface-state time 3970.619 if : free 6809 if HME0: free 1
if LE0: free 1 if LOCAL: free 1
driver: hdisk-state time 3970.619 hdisk 0: free 5861972 dumpers 0
--
Denise E. Ives [EMAIL PROTECTED]
Systems Engineer734.822.2037
Multilingual Internet Domain Name Registrations - http://www.walid.com
4mm DDS-150 40GB compressed 20GB non
4mm x 150m/492ft. - capacity -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: AMANDA MAIL REPORT FOR December 11, 2000
Ok I will do this and if I remember correctly we can't run 2 amdumps in one day - right - it isn't recommended right? And I do run it a second time the amdump.xx log numbers will increment. So I will unset this force flag on sda10 and let her run again tomorrow am? Anyway I can dump 'only' sda10 right now? I also noticed that there was no .log file generated this time around and amanda didn't tell me to run amcleanup. Even more strange. On Mon, 11 Dec 2000, John R. Jackson wrote: Ok here we go again. I ran amcleanup and then re-ran today's amdump. I got another fail of dump for on sda10. Note that the wrong tape is mounted and Amanda refused to use it, so all the dumps were incrementals and went into the holding disk, which is why it was so quick. Then when it got to sda10 it still saw the "force a level 0" flag set and refused to do it at all. To turn off the force flag, do this: su amanda-user -c amadmin config unforce admin1.corp.walid.com sda10 John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
sda10 - AMANDA MAIL REPORT FOR December 11, 2000 (fwd)
df -k
/dev/sda1026375596 11196212 13839568 45% /home
I got a level 2 dump here.
I need to get a full dump of sda10. What do you suggest I do?
Should I stick a tape in the tape drive and force a full dump for
tonight's amdump? Is that safe to do or should I let the incrementals run
to holding disk for a few days.
-- Forwarded message --
Date: Mon, 11 Dec 2000 20:16:25 -0500 (EST)
Subject: daily AMANDA MAIL REPORT FOR December 11, 2000
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [no tape online].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto tape daily002 or a new tape.
Tonight's dumps should go onto 1 tape: daily003.
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:01 0:00 0:00 (0:01 start)
Output Size (meg)1719.80.0 1719.8
Original Size (meg) 1719.80.0 1719.8
Avg Compressed Size (%) -- -- --
Tape Used (%) 4.80.04.8 (level:#disks ...)
Filesystems Dumped1 0 1 (2:1)
Avg Dump Rate (k/s) 3048.6-- 3048.6
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
admin1.co sda10 2 1761120 1761120 -- 9:38 3048.6N/AN/A
(brought to you by Amanda version 2.4.1p1)
Re: tapetype SEAGATE-SCORPION-4
Do you think this failed because my holding disk is 11 GB and I was trying to dump/write 10 GB at the same time? Could it have bottle-necked? Files reading in and writing out - checksum failure? On Mon, 11 Dec 2000, John R. Jackson wrote: driver: dumping admin1.corp.walid.com:sda10 directly to tape driver: send-cmd time 3970.608 to taper: PORT-WRITE 00-00017 admin1.corp.walid.com sda10 0 20001209 driver: result time 3970.619 from taper: PORT 34331 driver: send-cmd time 3970.619 to dumper0: PORT-DUMP 01-00018 34331 admin1.corp.walid.com sda10 0 1970:1:1:0:0:0 DUMP |;bsd-auth;index; driver: state time 3970.619 free kps: 12209 space: 5861972 taper: writing idle-dumpers: 3 qlen tapeq: 0 runq: 0 stoppedq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 3970.619 if : free 6809 if HME0: free 1 if LE0: free 1 if LOCAL: free 1 driver: hdisk-state time 3970.619 hdisk 0: free 5861972 dumpers 0 This says sda10 was being dumped directly to tape when the world ended. I don't know why the file is truncated at this point, but it looks like the system was rebooted, or the disk this file is part of filled up, or the Amanda user ran into its disk quota, or something like that. There is no trail of why the sda10 disk failed to make it entirely to tape. Is the "40" in your tapetype name meant to imply this device can do 40 GBytes? Is that compressed or "native"? If it's the manufactures compressed number, they lie, big time. The usual numbers they give are the native and twice the native for hardware compression. For instance, my DLT7000's are 35 GBytes native, so they claim 70 GBytes if I use hardware compression. But back here in the real world, I only get about 37 GBytes. Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Check for cruft. - amflush failed
amanda@sundev1 [daily] % amflush daily
Scanning /dump/amanda...
20001208: found non-empty Amanda directory.
20001211: found non-empty Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20001208
B. 20001211
Select directories to flush [A..B]: [ALL] all
Flushing dumps in 20001208, 20001211,
today: 20001211
to tape drive /dev/rmt/0cbn.
Expecting tape daily002 or a new tape. (The last dumps were to tape
daily001)
Are you sure you want to do this? y
Running in background, you can log off now.
You'll get mail when amflush is finished.
-- Forwarded message --
Date: Mon, 11 Dec 2000 21:13:42 -0500 (EST)
Subject: daily AMFLUSH MAIL REPORT FOR December 11, 2000
The dumps were flushed to tape daily002.
Tonight's dumps should go onto 1 tape: daily003.
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:17 0:00 0:17 (0:00 start, 0:00 idle)
Output Size (meg)3360.50.0 3360.5
Original Size (meg) 3360.50.0 3360.5
Avg Compressed Size (%) -- -- --
Tape Used (%) 9.40.09.4 (level:#disks ...)
Filesystems Dumped2 0 2 (2:2)
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) 3312.9-- 3312.9
NOTES:
amflush: admin1.corp.walid.com.sda9.1: disk admin1.corp.walid.com:sda9 not in
database, skipping it.
amflush: sundev1.corp.walid.com.c0t0d0s3.1: disk sundev1.corp.walid.com:c0t0d0s3 not
in database, skipping it.
amflush: admin1.corp.walid.com.sda3.1: disk admin1.corp.walid.com:sda3 not in
database, skipping it.
amflush: admin1.corp.walid.com.sda6.1: disk admin1.corp.walid.com:sda6 not in
database, skipping it.
amflush: admin1.corp.walid.com.sda5.2: disk admin1.corp.walid.com:sda5 not in
database, skipping it.
amflush: admin1.corp.walid.com.sda2.1: disk admin1.corp.walid.com:sda2 not in
database, skipping it.
amflush: sundev1.corp.walid.com.c0t0d0s7.2: disk sundev1.corp.walid.com:c0t0d0s7 not
in database, skipping it.
amflush: sundev1.corp.walid.com.c0t0d0s0.0: disk sundev1.corp.walid.com:c0t0d0s0 not
in database, skipping it.
amflush: admin1.corp.walid.com.sda10.2.1: ignoring cruft file.
amflush: Could not rmdir /dump/amanda/20001208. Check for cruft.
amflush: admin1.corp.walid.com.sda3.1: disk admin1.corp.walid.com:sda3 not in
database, skipping it.
amflush: sundev1.corp.walid.com.c0t0d0s0.1: disk sundev1.corp.walid.com:c0t0d0s0 not
in database, skipping it.
amflush: admin1.corp.walid.com.sda6.1: disk admin1.corp.walid.com:sda6 not in
database, skipping it.
amflush: admin1.corp.walid.com.sda5.1: disk admin1.corp.walid.com:sda5 not in
database, skipping it.
amflush: admin1.corp.walid.com.sda2.1: disk admin1.corp.walid.com:sda2 not in
database, skipping it.
amflush: sundev1.corp.walid.com.c0t0d0s3.1: disk sundev1.corp.walid.com:c0t0d0s3 not
in database, skipping it.
amflush: sundev1.corp.walid.com.c0t0d0s7.1: disk sundev1.corp.walid.com:c0t0d0s7 not
in database, skipping it.
amflush: admin1.corp.walid.com.sda10.2.1: ignoring cruft file.
amflush: Could not rmdir /dump/amanda/20001211. Check for cruft.
taper: tape daily002 kb 3441152 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
admin1.co sda10 2 N/A N/A -- N/AN/A 8:33 3274.5
admin1.co sda10 2 1761152 1761152 -- N/AN/A 8:46 3350.3
(brought to you by Amanda version 2.4.1p1)
**
ls /dump
20001208 20001211
**
What can possibly be going on here?
amdump.x - no-diskspace
Hi Chris - thank you for the response. In this particular amdump log file and only in this amdump log file I saw the no-diskspace for each partition but the thing it only sda10 failed here. That was what the AMANDA MAIL Report showed, amstatus showed and I also ran amverify against the tape - to see if the results were consistant and they were. I also removed the 'force full' flag from sda10 and ran amdump just for that partition to the holding disk. It ran fine and the Amanda Mail report showed sent a message saying sda20 did a level 2 backed-up. But here is the kicker - I just tried to amflush this back-up and a previous back-up image to tape and just then I got a cruft error message. The media seems to have some data written on it but yet the holding disk (/dump) still has the 2 backup images in it. I have no idea what is going on with amanda now - or how to remove these 2 back-up images from the holding disk. On Tue, 12 Dec 2000, Chris Karakas wrote: Denise Ives wrote: driver: state time 3104.913 free kps: 15400 space: 4837972 taper: writing idle-dumpers: 4 qlen tapeq: 0 runq: 1 stoppedq: 0 wakeup: 86400 driver-idle: no-diskspace It just caught my attention: "no-diskspace". -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
forced a full dump for Sat AM - it failed
Any ideas on how/why this happened?
thanks -
-- Forwarded message --
Date: Sat, 18 Nov 2000 01:15:42 -0500 (EST)
From: [EMAIL PROTECTED]
Subject: daily AMANDA MAIL REPORT FOR November 18, 2000
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [no tape online].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda3 lev 0 FAILED [can't switch to incremental dump]
admin1.cor sda9 lev 0 FAILED [can't switch to incremental dump]
admin1.cor sda6 lev 0 FAILED [can't switch to incremental dump]
sundev1.co c0t0d0s3 lev 0 FAILED [can't switch to incremental dump]
admin1.cor sda2 lev 0 FAILED [can't switch to incremental dump]
admin1.cor sda5 lev 0 FAILED [can't switch to incremental dump]
sundev1.co c0t0d0s0 lev 0 FAILED [can't switch to incremental dump]
sundev1.co c0t0d0s7 lev 0 FAILED [can't switch to incremental dump]
admin1.cor sda10 lev 0 FAILED [can't switch to incremental dump]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:01 0:00 0:00 (0:01 start)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Forcing full dump of sundev1.corp.walid.com:c0t0d0s0 as directed.
planner: Forcing full dump of sundev1.corp.walid.com:c0t0d0s3 as directed.
planner: Forcing full dump of sundev1.corp.walid.com:c0t0d0s7 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda6 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda3 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda5 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda10 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda9 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda2 as directed.
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
admin1.co sda10 0 FAILED
admin1.co sda2 0 FAILED
admin1.co sda3 0 FAILED
admin1.co sda5 0 FAILED
admin1.co sda6 0 FAILED
admin1.co sda9 0 FAILED
sundev1.c c0t0d0s0 0 FAILED
sundev1.c c0t0d0s3 0 FAILED
sundev1.c c0t0d0s7 0 FAILED
(brought to you by Amanda version 2.4.1p1)
Re: forced a full dump for Sat AM - it failed (fwd)
Actually - I left the tape out of the tape drive on purpose. I was trying to get amanda send the full dump image to the holding disk. When you force a full dump and there is a tape error - amanda doesn't send the dump to the holding disk? -- Forwarded message -- Date: Sat, 18 Nov 2000 15:28:55 -0600 (CST) From: Joi Ellis [EMAIL PROTECTED] To: Denise Ives [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: forced a full dump for Sat AM - it failed On Sat, 18 Nov 2000, Denise Ives wrote: Date: Sat, 18 Nov 2000 21:20:03 + (GMT) From: Denise Ives [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: forced a full dump for Sat AM - it failed Any ideas on how/why this happened? Amanda couldn't find a tape in the drive. It would normally default to doing incrementals, but because full dumps had been forced for all clients, Amanda couldn't degrade to incrementals. Find out why Amanda couldn't see a tape in the drive. Maybe there wasn't one, or maybe the drive reported an error trying to read it. Check your system's syslog or kernel log for tape error messages... Don't forget you have to 'amlabel' each new tape before Amanda will write to it. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
overdue 7 days for level 0
I forced a level 0 dump and left the tape out of the tape drive - as you all know amanda failed to dump because of a tape error. Why didn't amanda put the dump image into the holding disk? Is this expected behavior? READING CONF FILES... startup took 0.019 secs SETTING UP FOR ESTIMATES... setting up estimates for sundev1.corp.walid.com:c0t0d0s0 sundev1.corp.walid.com:c0t0d0s0 overdue 7 days for level 0 setup_estimate: sundev1.corp.walid.com:c0t0d0s0: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (2179103) -1 (-1) -1 (-1) setting up estimates for sundev1.corp.walid.com:c0t0d0s3 sundev1.corp.walid.com:c0t0d0s3 overdue 7 days for level 0 setup_estimate: sundev1.corp.walid.com:c0t0d0s3: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (411295) -1 (-1) -1 (-1) setting up estimates for sundev1.corp.walid.com:c0t0d0s7 sundev1.corp.walid.com:c0t0d0s7 overdue 7 days for level 0 setup_estimate: sundev1.corp.walid.com:c0t0d0s7: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (3255391) -1 (-1) -1 (-1) setting up estimates for admin1.corp.walid.com:sda6 admin1.corp.walid.com:sda6 overdue 7 days for level 0 setup_estimate: admin1.corp.walid.com:sda6: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (161690) -1 (-1) -1 (-1) setting up estimates for admin1.corp.walid.com:sda3 admin1.corp.walid.com:sda3 overdue 7 days for level 0 setup_estimate: admin1.corp.walid.com:sda3: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (6020) -1 (-1) -1 (-1) setting up estimates for admin1.corp.walid.com:sda5 admin1.corp.walid.com:sda5 overdue 7 days for level 0 setup_estimate: admin1.corp.walid.com:sda5: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (1616761) -1 (-1) -1 (-1) setting up estimates for admin1.corp.walid.com:sda10 admin1.corp.walid.com:sda10 overdue 7 days for level 0 setup_estimate: admin1.corp.walid.com:sda10: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (7927030) -1 (-1) -1 (-1) setting up estimates for admin1.corp.walid.com:sda9 admin1.corp.walid.com:sda9 overdue 7 days for level 0 setup_estimate: admin1.corp.walid.com:sda9: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (79937) -1 (-1) -1 (-1) setting up estimates for admin1.corp.walid.com:sda2 admin1.corp.walid.com:sda2 overdue 7 days for level 0 setup_estimate: admin1.corp.walid.com:sda2: command 1, options: last_level -1 next_level0 -7 level_days 0 getting estimates 0 (400018) -1 (-1) -1 (-1) setting up estimates took 0.008 secs GETTING ESTIMATES... driver: pid 9022 executable /usr/local/pkg/amanda-2.4.1p1/libexec/driver version 2.4.1p1 driver: send-cmd time 0.057 to taper: START-TAPER 20001118 taper: pid 9026 executable taper version 2.4.1p1 driver: started dumper0 pid 9030 driver: started dumper1 pid 9031 driver: started dumper2 pid 9032 driver: started dumper3 pid 9033 dumper: pid 9031 executable dumper version 2.4.1p1, using port 839 dumper: pid 9030 executable dumper version 2.4.1p1, using port 838 dumper: pid 9032 executable dumper version 2.4.1p1, using port 840 dumper: pid 9033 executable dumper version 2.4.1p1, using port 841 got result for host sundev1.corp.walid.com disk c0t0d0s7: 0 - 3444532K, -1 - -1K, -1 - -1K got result for host sundev1.corp.walid.com disk c0t0d0s3: 0 - 414554K, -1 - -1K, -1 - -1K got result for host sundev1.corp.walid.com disk c0t0d0s0: 0 - 2212165K, -1 - -1K, -1 - -1K got result for host admin1.corp.walid.com disk sda2: 0 - 474735K, -1 - -1K, -1 - -1K got result for host admin1.corp.walid.com disk sda9: 0 - 104184K, -1 - -1K, -1 - -1K got result for host admin1.corp.walid.com disk sda10: 0 - 8034411K, -1 - -1K, -1 - -1K got result for host admin1.corp.walid.com disk sda5: 0 - 1500893K, -1 - -1K, -1 - -1K got result for host admin1.corp.walid.com disk sda3: 0 - 6028K, -1 - -1K, -1 - -1K got result for host admin1.corp.walid.com disk sda6: 0 - 148733K, -1 - -1K, -1 - -1K getting estimates took 39.686 secs FAILED QUEUE: empty DONE QUEUE: 0: sundev1.corp.walid.com c0t0d0s7 1: sundev1.corp.walid.com c0t0d0s3 2: sundev1.corp.walid.com c0t0d0s0 3: admin1.corp.walid.com sda2 4: admin1.corp.walid.com sda9 5: admin1.corp.walid.com sda10 6: admin1.corp.walid.com sda5 7: admin1.corp.walid.com sda3 8: admin1.corp.walid.com sda6 ANALYZING ESTIMATES... pondering sundev1.corp.walid.com:c0t0d0s7... next_level0 -7 last_level -1 (due for level 0) (new dis k, can't switch to degraded mode) curr level 0 size 3444532 total size 3444928 total_lev0 3444532 balanced-lev0size 430566 pondering sundev1.corp.walid.com:c0t0d0s3... next_level0 -7 last_level -1 (due for level 0) (new dis k, can't switch to degraded mode) curr level 0 size 414554 total size 3859614 total_lev0 3859086
Do you think we are going to run out of holding disk space..
for tonight's level 0 dump? Here is the holding disk area: /dev/md/dsk/d20 1156014410 11444533 0% /dump I have an 11Gb holding disk area - What do you think? amanda@sundev1 [amanda] % amadmin daily force sundev1.corp.walid.com *amadmin: sundev1.corp.walid.com:c0t0d0s7 is set to a forced level 0 tonight. amadmin: sundev1.corp.walid.com:c0t0d0s3 is set to a forced level 0 tonight. amadmin: sundev1.corp.walid.com:c0t0d0s0 is set to a forced level 0 tonight. amanda@sundev1 [amanda] % amadmin daily force admin11.corp.walid.com amadmin: host admin11.corp.walid.com not in current disklist database. amanda@sundev1 [amanda] % amadmin daily force admin1.corp.walid.com amadmin: admin1.corp.walid.com:sda2 is set to a forced level 0 tonight. amadmin: admin1.corp.walid.com:sda9 is set to a forced level 0 tonight. *amadmin: admin1.corp.walid.com:sda10 is set to a forced level 0 tonight. amadmin: admin1.corp.walid.com:sda5 is set to a forced level 0 tonight. amadmin: admin1.corp.walid.com:sda3 is set to a forced level 0 tonight. amadmin: admin1.corp.walid.com:sda6 is set to a forced level 0 tonight. root@sundev1:etc/amanda/daily# df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/dsk/c0t0d0s0 3122055 2144808914806 70% / /dev/dsk/c0t0d0s3 1018191409725547375 43% /var swap 146500016 1464984 0% /var/run swap 1465480 496 1464984 0% /tmp /dev/dsk/c0t0d0s7 12221308 3370006 8729089 28% /home /dev/md/dsk/d20 1156014410 11444533 0% /dump admin1:/home 26375596 8141288 16894492 33% /admin1-home admin1:pts/5% df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda6 1035660150704832348 15% / /dev/sda32 5998 16131 27% /boot /dev/sda8 521748 97500397744 20% /tmp /dev/sda5 2071384 1578340387820 80% /usr /dev/sda1026375596 8141288 16894492 33% /home /dev/sda9 256667 94663148752 39% /var /dev/sda2 4134932482756 3442128 12% /var/log admin1:pts/5% -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Tweaking reserve
Will this work?
Right now a cron job runs amdump every day of the week in the AM.
I just forced amanda to do a full dump on Sat AM. I am leaving the tape
out of the tape drive. The full dump image should go directly
to my holding disk.
Still leaving the tape drive empty, Amanda runs again on Sun AM.
She should do an incremental - (yes?) and send that level 1 image to
holding disk too (yes?).
I should get Level 1 dumps on Tues AM, Wed AM, and Thur AM sent to
the holding disk if I have the reserve parameter set up correctly
and enough room on the holding disk. (yes/no?)
*Then on Friday AM I will amflush everything in the holding disk to
tape. The holding disk should have a full dump image and a weeks worth of
incrementals.
Do you think this will work?
Right now - I have the reserve parameter commented
out in my amanda.conf. Should I set it to 50 %?
Thank you again for your time and support.
-- Forwarded message --
Date: 04 Nov 2000 02:43:27 -0200
From: Alexandre Oliva [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Denise Ives [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: can amanda do this?
On Nov 2, 2000, "John R. Jackson" [EMAIL PROTECTED] wrote:
Mon-Sat: Incremental dump to holding disk sundev1:/dump (level 1).
Sun Eve/Mon AM: Full backup of everything to tape.
Flush incrementals to tape as well.
It can do the first two parts with only minor hassle. However it cannot
do the last (flush the incrementals to the same tape as the full dump).
That's been requested but not implemented. So you're going to have to
use two tapes per week, one for the full dump and one to flush the week
of incrementals.
Either that or have the fulls left in the holding disk too (which will
require tweaking reserve) and have them amflushed to tape along with
the incrementals.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Date: Mon, 13 Nov 2000 13:23:00 -0500 [EMAIL PROTECTED] Wrote:
Not sure if you caught the discussion about this with Jean-Louis,
Alexandre and I, but apparently the bump parameters being set to zero
will not do what I thought in the absence of tape, but Jean-Louis thinks
that if you just set "reserve" to anything smaller than 100 (e.g. 99)
in your holdingdisk definition, it will start bumping.
To answer your next question before you even ask it :-), the "reserve"
parameter was put in for sites like yours who want to run without tapes,
putting the images just into their holding disk. Normally Amanda will
not do full dumps when it knows it does not have a tape, but the reserve
parameter allows that to be controlled. A value of 100 percent (the
default) is the old behavior of not allowing any full dumps, i.e. all
(100%) of the holding disk is reserved for incremental backups when in
degraded mode. Setting it to 75, for instance, would use up to 3/4 of
the space for incrementals and the rest for full dumps.
I don't think you probably want to do full dumps into your holding
disk because you don't have all that much of it. So we aren't using
the parameter for that purpose, but for a side effect it (reportedly)
has of letting bump levels increase without writing the images to tape.
Note that I haven't tested any of this to see if it really works.
But if it doesn't, nothing bad should happen. The worst it will do
is still not bump from one level to another. And the only bad thing
about that for your setup is some increase the holding disk space used.
It's not generating bad dumps or anything like that.
did amanda just do a full dump to holding disk?
#amanda.conf
bumpdays 0 # minimum days at each level
reserve 70 # percent
Daily Amanda Mail Reports from Nov. 13, 14, and 15
Subject: daily AMANDA MAIL REPORT FOR November 13, 2000
Total Full Daily
Dump Time (hrs:min)2:05 1:18 0:00 (0:01 start, 0:46
idle)
Output Size (meg) 15607.115607.10.0
Original Size (meg) 15607.115607.10.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 43.5 43.50.0
Filesystems Dumped9 9 0
Avg Dump Rate (k/s) 1987.5 1987.5--
Avg Tp Write Rate (k/s) 3406.9 3406.9--
?
NOTES:
planner: Forcing full dump of sundev1.corp.walid.com:c0t0d0s0 as
directed.
planner: Forcing full dump of sundev1.corp.walid.com:c0t0d0s3 as
directed.
planner: Forcing full dump of sundev1.corp.walid.com:c0t0d0s7 as
directed.
planner: Forcing full dump of admin1.corp.walid.com:sda6 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda3 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda5 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda10 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda9 as directed.
planner: Forcing full dump of admin1.corp.walid.com:sda2 as directed.
taper: tape daily119 kb 15981984 fm 9 [OK]
?
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- --
--
admin1.co sda10 0 7927040 7927040 --59:55 2204.8 41:32
3181.6
admin1.co sda2 0 347808 347808 -- 2:58 1952.81:51
3128.6
admin1.co sda3 0 6048 6048 -- 0:02 3308.80:03
2320.3
admin1.co sda5 0 1616768 1616768 --15:09 1778.18:03
3347.6
admin1.co sda6 0 161696 161696 -- 1:26 1872.80:44
3643.2
admin1.co sda9 08230482304 -- 0:40 2046.10:21
4014.8
sundev1.c c0t0d0s0 0 2179136 2179136 --19:52 1827.8 10:53
3337.1
Subject: daily AMANDA MAIL REPORT FOR November 14, 2000
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg)1241.80.0 1241.8
Original Size (meg) 1241.80.0 1241.8
Avg Compressed Size (%) -- -- --
Tape Used (%) 3.50.03.5 (level:#disks ...)
Filesystems Dumped9 0 9 (1:9)
Avg Dump Rate (k/s) 1881.4-- 1881.4
Avg Tp Write Rate (k/s) -- -- --
?
NOTES:
planner: Full dump of admin1.corp.walid.com:sda10 specially promoted
from 6 days ahead.
?
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- --
--
admin1.co sda10 1 790304 790304 -- 5:56 2219.1N/A
N/A
admin1.co sda2 19155291552 -- 0:29 3123.4N/A
N/A
admin1.co sda3 1 32 32 -- 0:01 51.2N/A
N/A
admin1.co sda5 12659226592 -- 0:31 865.6N/A
N/A
admin1.co sda6 1 256 256 -- 0:03 80.5N/A
N/A
admin1.co sda9 14259242592 -- 0:12 3653.7N/A
N/A
sundev1.c c0t0d0s0 1 2144 2144 -- 0:37 57.2N/A
N/A
sundev1.c c0t0d0s3 1 158624 158624 -- 0:59 2693.7N/A
N/A
sundev1.c c0t0d0s7 1 159520 159520 -- 2:28 1078.8N/A
N/A
(brought to you by Amanda version 2.4.1p1)
Subject: daily AMANDA MAIL REPORT FOR November 15, 2000
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg)2194.5 1034.2 1160.3
Original Size (meg) 2194.5 1034.2 1160.3
Avg Compressed Size (%) -- -- --
Tape Used (%) 6.12.93.2 (level:#disks ...)
Filesystems Dumped9 5 4 (1:4)
Avg Dump Rate (k/s) 2067.7 2045.6 2087.9
Avg Tp Write Rate (k/s) -- -- --
?
NOTES:
planner: Full dump of sundev1.corp.walid.com:c0t0d0s3 promoted from 5
days ahead.
planner: Full dump of admin1.corp.walid.com:sda2 promoted from 5 days
ahead.
planner: Full dump of admin1.corp.walid.com:sda9 promoted from 5 days
ahead.
planner: Full dump of
Disregard - Re: the amanda tape cycle (fwd)
--
Denise E. Ives [EMAIL PROTECTED]
Systems Engineer734.822.2037
Multilingual Internet Domain Name Registrations - http://www.walid.com
-- Forwarded message --
Date: Wed, 15 Nov 2000 16:26:56 + (GMT)
From: Denise Ives [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: the amanda tape cycle (fwd)
Yes - I removed most of the older labels in the tapelist.
I still need to re-label each tape - before amanda will
let me amflush the holding disk directly to tape or full dump force
directly to tape. Does that make
sense?
amanda@sundev1 [daily] % amcheck daily
Amanda Tape Server Host Check
-
/dump/amanda: 10171924 KB disk space available, using 9659924 KB.
ERROR: /dev/rmt/0cbn: no tape online.
(expecting a new tape)
NOTE: skipping tape-writable test.
Server check took 20.005 seconds.
Amanda Backup Client Hosts Check
Client check: 2 hosts checked in 0.137 seconds, 0 problems found.
(brought to you by Amanda 2.4.1p1)
amanda@sundev1 [daily] % amadmin daily tape
The next Amanda run should go onto a new tape.
-- Forwarded message --
Date: 12 Nov 2000 20:28:33 -0200
From: Alexandre Oliva [EMAIL PROTECTED]
To: Denise Ives [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: the amanda tape cycle
On Nov 12, 2000, Denise Ives [EMAIL PROTECTED] wrote:
I know my tapecycle # should match the number of tapes I am using.
Even if I change my tapecycle number to 4, I still have to label and
force a re-label of each tape.
When I run amcheck amanda suggests a tape to use or tells me to put in a
new tape.
Amanda will always accept a new tape, but it suggests the oldest
reusable tape in the tapelist file (unless there aren't at least
tapecycle reusable tapes in the cycle), and it will accept any tape
that is at least as old as the tapecycle-th newest reusable one.
Since your tapelist has more than 4 tape labels, you've probably
re-labeled some tapes with labels different from the ones they already
had. Just remove the older entries from the tapelist and Amanda will
start suggesting the right tapes. Alternatively, you may ignore the
suggestion and just keep giving it acceptable tapes.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
tape labeling scheme
How can I identify amanda tapes by level of dump? I can label a tape that had a full dump on Nov1 as daily111 but I can't label a tape that had a full dump on Nov 24th as daily1124. Yes - amlabel -f daily 111 or use a letter to represent the month - NO - amanda@sundev1 [amanda] % amlabel daily daily11N amlabel: label daily11N doesn't match labelstr "^daily[0-9][0-9]*$" NO - amanda@sundev1 [amanda] % amlabel daily daily1102 tape has not been labeled. any ideas how to track this? #tapetype DAT # what kind of tape it is (see tapetypes below) tapetype SEAGATE-SCORPION-40 labelstr "^daily[0-9][0-9]*$" # label constraint regex: all tapes must match -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
removing Warning Message from Amanda Report..
Amanda is running fine. I am running fulldumps to tape on weekends and
letting amanda have incrementals dump to holding disk during the
off-days. (since I am limited to the amount of tapes i can use)
I have just been asked to remove these Tape Error message from the
daily Amanda Reports:
i.e.
"*** THE DUMPS DID NOT FINISH PROPERLY"
"*** A TAPE ERROR OCCURRED" {no tape online].
Does anyone know how I can make this happen?
Can it happen?
Thank you.
To: [EMAIL PROTECTED]
Subject: daily AMANDA MAIL REPORT FOR November 14, 2000
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [no tape online].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg)1241.80.0 1241.8
Original Size (meg) 1241.80.0 1241.8
Avg Compressed Size (%) -- -- --
Tape Used (%) 3.50.03.5 (level:#disks ...)
Filesystems Dumped9 0 9 (1:9)
Avg Dump Rate (k/s) 1881.4-- 1881.4
Avg Tp Write Rate (k/s) -- -- --
--
Denise E. Ives [EMAIL PROTECTED]
Systems Engineer734.822.2037
Multilingual Internet Domain Name Registrations - http://www.walid.com
Wait - are you saying that I don't have to re-label each of my tapes?
Does this have anything to do with the tapecycle parameter in the amanda.conf file and which tape to use next? # Backupcentral.com/Amanda tape labeling # Each tape assigned to a configuration needs a unique label. Tapes must be pre-labeled with amlabel so AMANDA can verify the tape is one it should use. Run amlabel as the AMANDA user, not root. For instance: # su amanda -c "amlabel daily daily123" I don't think most people relabel tapes every time, and certainly not with meaningful encoding of such things as the date they were used. The typical method is to just create a set of tapes and let Amanda cycle around through them, i.e. daily00, daily01, daily02, daily03. Why do you want to relabel them each time? Amanda will tell you (via amadmin or amrecover) which tape has which dump image on it. Why do you want to relabel tapes each time? Amanda will tell you (via amadmin or amrecover) which tape has which dump image on it. ***Example: I have tape daily555 in the tape drive right now. When I run amadmin conf tape I get these results: *** amanda@sundev1 [daily] % amadmin daily tape The next Amanda run should go onto a new tape. *Example: When I run amcheck - Amanda tells me it will not overwrite tape daily555 amanda@sundev1 [daily] % amcheck daily Amanda Tape Server Host Check - /dump/amanda: 10171924 KB disk space available, using 9659924 KB. ERROR: cannot overwrite active tape daily555. (expecting a new tape) NOTE: skipping tape-writable test. This is why I have been re-labeling the tapes each time. After I force the re-label of a tape amflush runs without fail. I also re-label each tape when I need to run a full dump. I never thought that made any sense - but I guess Amanda doesn't want to overwrite good Valid images. amlabel -f daily newlabel Here is my tape list file. daily119 is a full dump daily 112 has a weeks worth of incrementals daily118 is a full dump daily555 has a weeks worth of incrementals Tape labels daily01 and daily02 - are now tape labels daily119 and daily112 I just didn't remove them from the tape list - amrmtape tapelist "/usr/adm/amanda/daily/tapelist" amanda@sundev1 [daily] % cat tapelist 20001113 daily119 reuse 20001112 daily112 reuse 20001107 daily118 reuse 20001101 daily02 reuse 20001030 daily01 reuse 20001023 daily555 reuse amanda@sundev1 [daily] % -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
'sethost'
Trying to restore a file on a client (admin1.corp.walid.com) How can I set host and connect to admin1 with amrecover? root@sundev1:/home/user/dives# amrecover -C daily -s sundev1.corp.walid.com -t sundev1.corp.walid.com -d /dev/rmt/0cbn AMRECOVER Version 2.4.1p1. Contacting server on sundev1.corp.walid.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2000-11-07) 200 Working date set to 2000-11-07. 200 Config set to daily. 200 Dump host set to sundev1.corp.walid.com. $CWD '/admin1-home/user/dives' is on a network mounted disk so you must 'sethost' to the server amrecover exit 200 Good bye. root@sundev1:/home/user/dives# -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: 'sethost' index errors ?
root@sundev1:/admin1-home/user/dives# amrecover -C daily -s sundev1.corp.walid.com -t sundev1.corp.walid.com -d /dev/rmt/0cbn AMRECOVER Version 2.4.1p1. Contacting server on sundev1.corp.walid.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2000-11-07) 200 Working date set to 2000-11-07. 200 Config set to daily. 501 No index records for host: sundev1. Invalid? Trying sundev1.corp.walid.com ... 200 Dump host set to sundev1.corp.walid.com. $CWD '/admin1-home/user/dives' is on a network mounted disk so you must 'sethost' to the server amrecover sethost admin1 501 No index records for host: admin1. Invalid? Trying admin1.corp.walid.com ... 200 Dump host set to admin1.corp.walid.com. amrecover ls Must select a disk before listing files amrecover setdisk sda10 200 Disk set to sda10. amrecover ls amrecover lpwd /admin1-home/user/dives amrecover pwd / amrecover cd /user/dives /user/dives amrecover add DB2 Added /user/dives/DB2 amrecover extract Extracting files using tape drive /dev/rmt/0bn on host sundev1.corp.walid.com. The following tapes are needed: daily118 Restoring files into directory /admin1-home/user/dives Continue? [Y/n]: y Load tape daily118 now Continue? [Y/n]: y amrecover Do you know why I am gettig indexing errors for both hosts? When amrecover finished running extract - i checked the /user/dives directory for the file I was trying to restore and it was not there. P.S. - No - I did not tell amanda to back up this area via NFS. On Tue, 7 Nov 2000, John R. Jackson wrote: Trying to restore a file on a client (admin1.corp.walid.com) ... 200 Dump host set to sundev1.corp.walid.com. $CWD '/admin1-home/user/dives' is on a network mounted disk so you must 'sethost' to the server ... How can I set host and connect to admin1 with amrecover? What it's saying is that your current working directory is NFS mounted from someplace and that's not likely the way you did the backups (i.e. you didn't tell Amanda to back up this area via NFS). So it's telling you to use the "sethost" amrecover command to set the host name to the machine that was actually backed up, i.e. the one listed in disklist. Based on earlier E-mail, this probably means you want to do this: amrecover sethost admin1.corp.walid.com Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
amrecover - trying to restore 1 file
root@sundev1:/etc# amrecover AMRECOVER Version 2.4.1p1. Contacting server on sundev1.corp.walid.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2000-11-07) 200 Working date set to 2000-11-07. 200 Config set to daily. 501 No index records for host: sundev1. Invalid? Trying sundev1.corp.walid.com ... 200 Dump host set to sundev1.corp.walid.com. $CWD '/etc' is on disk 'c0t0d0s0' mounted at '/'. 200 Disk set to c0t0d0s0. /etc WARNING: not on root of selected filesystem, check man-page! amrecover lpwd /etc amrecover pwd /etc amrecover add dumpdates Added /etc/dumpdates amrecover extract Extracting files using tape drive /dev/rmt/0bn on host sundev1.corp.walid.com. The following tapes are needed: daily118 Restoring files into directory /etc Continue? [Y/n]: y Load tape daily118 now Continue? [Y/n]: y Warning: ./etc: File exists set owner/mode for '.'? [yn] Directories already exist, set modes anyway? [yn] How do I handle each of these prompts? set owner/mode for '.'? [yn] Directories already exist, set modes anyway? [yn] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
file did not restore - using amrecover
root@sundev1:/etc# amrecover AMRECOVER Version 2.4.1p1. Contacting server on sundev1.corp.walid.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2000-11-07) 200 Working date set to 2000-11-07. 200 Config set to daily. 501 No index records for host: sundev1. Invalid? Trying sundev1.corp.walid.com ... 200 Dump host set to sundev1.corp.walid.com. $CWD '/etc' is on disk 'c0t0d0s0' mounted at '/'. 200 Disk set to c0t0d0s0. /etc WARNING: not on root of selected filesystem, check man-page! amrecover add dumpdates Added /etc/dumpdates amrecover extract Extracting files using tape drive /dev/rmt/0bn on host sundev1.corp.walid.com. The following tapes are needed: daily118 Restoring files into directory /etc Continue? [Y/n]: y Load tape daily118 now Continue? [Y/n]: y Warning: ./etc: File exists set owner/mode for '.'? [yn] n Directories already exist, set modes anyway? [yn] n amrecover exit 200 Good bye. -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
daily AMANDA MAIL REPORT FOR November 4, 2000 (fwd)
Just sda10 failed this time. There have been no changes made to any of the
config files since I reported this problem last Thursday.
Last Thursday's amanda dump reported that sd9 and sda10 Failed
Nov 4th - amanda dump reported that only sda10 Failed
Nov 5th - amanda dump reported that only sda10 Failed
Nov 6th - amanda dump reported that only sda10 Failed
Are you all saying that I need to change the chunk size?
sda10 - is our /home - this i need to get backed ups on.
On Fri, Nov 03, 2000 at 11:23:10PM -0500, John R. Jackson wrote:
I think that's what's happening, a dump with est_kps larger than the
bandwidth will never be scheduled to dump on holding disk.
I agree it looks like that could happen in principle (in fact, I wonder
if other such "don't do this now" states should be examined), but in
this
particular case the estimated bandwidth for the two disks not processed
was well below the available.
The schedule give:
admin1.cor sda9 lv 2 t 5 s52939 p 13
52939/5 = 10587 that's above 1, and that's why sda9 didn't get
dumped.
As Alexandre said, sda10 didn't get dumped because the disk was big and
the chunksize set to -1.
Jean-Louis
--
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
-- Forwarded message --
Date: Sat, 4 Nov 2000 01:24:22 -0500 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: daily AMANDA MAIL REPORT FOR November 4, 2000
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [no tape online].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda10 lev 1 FAILED [no more holding disk space]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg)1064.20.0 1064.2
Original Size (meg) 1064.20.0 1064.2
Avg Compressed Size (%) -- -- --
Tape Used (%) 3.00.03.0 (level:#disks ...)
Filesystems Dumped8 0 8 (1:1 2:6 3:1)
Avg Dump Rate (k/s) 2227.1-- 2227.1
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Incremental of admin1.corp.walid.com:sda2 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda9 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda5 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda3 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda6 bumped to level 2.
planner: Incremental of sundev1.corp.walid.com:c0t0d0s3 bumped to level 3.
planner: Incremental of sundev1.corp.walid.com:c0t0d0s0 bumped to level 2.
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
admin1.co sda10 1 FAILED
admin1.co sda2 29219292192 -- 0:48 1939.6N/AN/A
admin1.co sda3 2 32 32 -- 0:00 163.8N/AN/A
admin1.co sda5 2 6272 6272 -- 0:22 285.3N/AN/A
admin1.co sda6 2 1472 1472 -- 0:03 476.5N/AN/A
admin1.co sda9 24627246272 -- 0:13 3517.1N/AN/A
sundev1.c c0t0d0s0 26409664096 -- 0:55 1155.8N/AN/A
sundev1.c c0t0d0s3 38220882208 -- 0:46 1772.8N/AN/A
sundev1.c c0t0d0s7 1 797184 797184 -- 5:02 2643.8N/AN/A
(brought to you by Amanda version 2.4.1p1)
daily AMFLUSH MAIL REPORT FOR November 6, 2000 (fwd)
To get my full backup - Should I force a level 0 to tape tonight?
When I finish running tonight's level 0 to tape will amanda
know to run the next dump as an incremental?
-- Forwarded message --
Date: Mon, 6 Nov 2000 13:55:28 -0500 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: daily AMFLUSH MAIL REPORT FOR November 6, 2000
The dumps were flushed to tape daily117.
Tonight's dumps should go onto 1 tape: a new tape.
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:23 0:00 0:23 (0:00 start, 0:00 idle)
Output Size (meg)5461.60.0 5461.6
Original Size (meg) 5461.60.0 5461.6
Avg Compressed Size (%) -- -- --
Tape Used (%) 15.20.0 15.2 (level:#disks ...)
Filesystems Dumped 39 0 39 (1:11 2:24 3:4)
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) 4078.5-- 4078.5
NOTES:
taper: tape daily117 kb 5592640 fm 39 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
admin1.co sda10 NO FILE TO FLUSH ---
admin1.co sda2 2 N/A N/A -- N/AN/A 3:10 3269.5
admin1.co sda2 2 N/A N/A -- N/AN/A 0:18 3486.8
admin1.co sda2 2 N/A N/A -- N/AN/A 0:26 3565.4
admin1.co sda2 2 N/A N/A -- N/AN/A 1:20 3750.6
admin1.co sda2 2 313984 313984 -- N/AN/A 1:29 3540.6
admin1.co sda3 2 N/A N/A -- N/AN/A 0:00 3163.8
admin1.co sda3 2 N/A N/A -- N/AN/A 0:00 4212.5
admin1.co sda3 2 N/A N/A -- N/AN/A 0:00 3906.7
admin1.co sda3 2 N/A N/A -- N/AN/A 0:00 3975.4
admin1.co sda3 2 64 64 -- N/AN/A 0:00 3053.0
admin1.co sda5 2 N/A N/A -- N/AN/A 0:01 5349.9
admin1.co sda5 2 N/A N/A -- N/AN/A 0:03 1967.9
admin1.co sda5 2 N/A N/A -- N/AN/A 0:01 5346.0
admin1.co sda5 2 N/A N/A -- N/AN/A 0:03 2340.6
admin1.co sda5 2 6304 6304 -- N/AN/A 0:03 1870.6
admin1.co sda6 2 N/A N/A -- N/AN/A 0:00 5533.1
admin1.co sda6 2 N/A N/A -- N/AN/A 0:00 4815.0
admin1.co sda6 2 N/A N/A -- N/AN/A 0:00 5783.7
admin1.co sda6 2 N/A N/A -- N/AN/A 0:00 5735.5
admin1.co sda6 2 1504 1504 -- N/AN/A 0:00 5505.0
admin1.co sda9 2 N/A N/A -- N/AN/A 0:16 2992.5
admin1.co sda9 2 N/A N/A -- N/AN/A 0:17 2658.0
admin1.co sda9 2 N/A N/A -- N/AN/A 0:13 2849.4
admin1.co sda9 23702437024 -- N/AN/A 0:13 2926.6
sundev1.c c0t0d0s0 2 N/A N/A -- N/AN/A 0:00 5658.0
sundev1.c c0t0d0s0 2 N/A N/A -- N/AN/A 0:15 4345.1
sundev1.c c0t0d0s0 2 N/A N/A -- N/AN/A 0:15 4398.8
sundev1.c c0t0d0s0 2 N/A N/A -- N/AN/A 0:14 4650.3
sundev1.c c0t0d0s0 26412864128 -- N/AN/A 0:14 4616.5
sundev1.c c0t0d0s3 3 N/A N/A -- N/AN/A 0:14 3755.2
sundev1.c c0t0d0s3 3 N/A N/A -- N/AN/A 0:16 3879.6
sundev1.c c0t0d0s3 3 N/A N/A -- N/AN/A 0:21 3861.2
sundev1.c c0t0d0s3 3 N/A N/A -- N/AN/A 0:26 3855.7
sundev1.c c0t0d0s3 3 127264 127264 -- N/AN/A 0:32 3931.2
sundev1.c c0t0d0s7 1 N/A N/A -- N/AN/A 3:34 3446.8
sundev1.c c0t0d0s7 1 N/A N/A -- N/AN/A 0:45 3977.4
sundev1.c c0t0d0s7 1 N/A N/A -- N/AN/A 2:38 5034.5
sundev1.c c0t0d0s7 1 N/A N/A -- N/AN/A 2:35 5137.2
sundev1.c c0t0d0s7 1 797984 797984 -- N/AN/A 2:36 5128.5
(brought to you by Amanda version 2.4.1p1)
I had enough holding disk but part of the dump failed -
claiming there was [no more holding disk space] -
What do you think went wrong?
Filesystemkbytesused avail capacity Mounted on
/dev/md/dsk/d20 11560144 1847220 959732317%/dump
Subject: daily AMANDA MAIL REPORT FOR November 3, 2000
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [no tape online].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda9 lev 2 FAILED [no more holding disk space]
admin1.cor sda10 lev 1 FAILED [no more holding disk space]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg) 370.40.0 370.4
Original Size (meg) 370.40.0 370.4
Avg Compressed Size (%) -- -- --
Tape Used (%) 1.00.01.0 (level:#disks ...)
Filesystems Dumped7 0 7 (1:1 2:5 3:1)
Avg Dump Rate (k/s) 1642.0-- 1642.0
Avg Tp Write Rate (k/s) -- -- --
?
NOTES:
planner: Incremental of admin1.corp.walid.com:sda2 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda9 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda5 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda3 bumped to level 2.
planner: Incremental of admin1.corp.walid.com:sda6 bumped to level 2.
planner: Incremental of sundev1.corp.walid.com:c0t0d0s3 bumped to level
3.
planner: Incremental of sundev1.corp.walid.com:c0t0d0s0 bumped to level
2.
?
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- --
--
admin1.co sda10 1 FAILED
admin1.co sda2 26380863808 -- 0:21 3095.4N/A
N/A
admin1.co sda3 2 32 32 -- 0:00 126.4N/A
N/A
admin1.co sda5 2 6272 6272 -- 0:21 293.6N/A
N/A
admin1.co sda6 2 1184 1184 -- 0:03 419.8N/A
N/A
admin1.co sda9 2 FAILED
sundev1.c c0t0d0s0 26387263872 -- 0:52 1228.8N/A
N/A
sundev1.c c0t0d0s3 36329663296 -- 0:24 2630.6N/A
N/A
sundev1.c c0t0d0s7 1 180800 180800 -- 1:50 1645.3N/A
N/A
(brought to you by A
root@sundev1:adm/amanda/daily# more log.20001103.0
START planner date 20001103
START driver date 20001103
ERROR taper no-tape [no tape online]
INFO planner Incremental of admin1.corp.walid.com:sda2 bumped to level 2.
INFO planner Incremental of admin1.corp.walid.com:sda9 bumped to level 2.
INFO planner Incremental of admin1.corp.walid.com:sda5 bumped to level 2.
INFO planner Incremental of admin1.corp.walid.com:sda3 bumped to level 2.
INFO planner Incremental of admin1.corp.walid.com:sda6 bumped to level 2.
INFO planner Incremental of sundev1.corp.walid.com:c0t0d0s3 bumped to
level 3.
INFO planner Incremental of sundev1.corp.walid.com:c0t0d0s0 bumped to
level 2.
FINISH planner date 20001103
STATS driver startup time 132.610
SUCCESS dumper admin1.corp.walid.com sda3 20001103 2 [sec 0.253 kb 32 kps
126.4 orig-kb 17]
SUCCESS dumper admin1.corp.walid.com sda6 20001103 2 [sec 2.820 kb 1184
kps 419.8 orig-kb 1163]
SUCCESS dumper sundev1.corp.walid.com c0t0d0s3 20001103 3 [sec 24.061 kb
63296 kps 2630.6 orig-kb 63263]
SUCCESS dumper admin1.corp.walid.com sda5 20001103 2 [sec 21.361 kb 6272
kps 293.6 orig-kb 6274]
SUCCESS dumper admin1.corp.walid.com sda2 20001103 2 [sec 20.613 kb 63808
kps 3095.4 orig-kb 63793]
SUCCESS dumper sundev1.corp.walid.com c0t0d0s0 20001103 2 [sec 51.977 kb
63872 kps 1228.8 orig-kb 63839]
SUCCESS dumper sundev1.corp.walid.com c0t0d0s7 20001103 1 [sec 109.887 kb
180800 kps 1645.3 orig-kb 180767]
FAIL driver admin1.corp.walid.com sda9 2 [no more holding disk space]
FAIL driver admin1.corp.walid.com sda10 1 [no more holding disk space]
Re: I had enough holding disk but part of the dump failed -
Here is my amanda.conf file with respect to the holding disk -
holdingdisk hd1 {
comment "main holding disk"
directory "/dump/amanda"# where the holding disk is
use -500Mb # how much space can we use on it
# a negative value mean:
#use all space except that value
chunksize -1# size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split disks in chunks of size N
# 0 split disks in INT_MAX/1024 Kb
chunks
# -1 same as -INT_MAX/1024 (see below)
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
Is the use wrong?
**
On Fri, 3 Nov 2000, Scot W. Hetzel wrote:
From: "Denise Ives" [EMAIL PROTECTED]
claiming there was [no more holding disk space] -
What do you think went wrong?
Filesystemkbytesused avail capacity Mounted on
/dev/md/dsk/d20 11560144 1847220 959732317%/dump
Subject: daily AMANDA MAIL REPORT FOR November 3, 2000
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda9 lev 2 FAILED [no more holding disk space]
admin1.cor sda10 lev 1 FAILED [no more holding disk space]
Your amanda.conf file may be specifying a maximum amount of drive space to
use for the holding disk.
holdingdisk hd1 {
comment "main holding disk"
directory "/dumps/amanda" # where the holding disk is
use -20 Mb # how much space can we use on it
# a negative value mean:
#use all space except that value
chunksize 1 Gb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split disks in chunks of size N
# 0 split disks in INT_MAX/1024 Kb chunks
# -1 same as -INT_MAX/1024 (see below)
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
# chunksize 2 Gb
}
Try, changing the "use" size to a more appropriate valuse for your setup.
Scot
Re: I had enough holding disk but part of the dump failed -
On Fri, 3 Nov 2000, John R. Jackson wrote: Here is my amanda.conf file with respect to the holding disk - ... use -500Mb ... That's OK. chunksize -1 ... This is not related to your problem, but you should change this at some point to something like "1000 Mb". Is the use wrong? It might be a little large (why not let Amanda have almost all of that file system?), but is probably not the problem. Much as I hate to do this :-), please post the entire amdump.1 file that goes with this run. It's the only way we'll be able to tell what was going on. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com amdump: start at Fri Nov 3 01:15:00 EST 2000 planner: pid 14161 executable /usr/local/pkg/amanda-2.4.1p1/libexec/planner version 2.4.1p1 planner: build: VERSION="Amanda-2.4.1p1" planner:BUILT_DATE="Tue Oct 17 14:52:15 GMT 2000" planner:BUILT_MACH="SunOS sundev1.corp.walid.com 5.8 Generic sun4u sparc SUNW,Ultra-60" planner:CC="gcc" planner: paths: bindir="/usr/local/pkg/amanda-2.4.1p1/bin" planner:sbindir="/usr/local/pkg/amanda-2.4.1p1/sbin" planner:libexecdir="/usr/local/pkg/amanda-2.4.1p1/libexec" planner:mandir="/usr/local/pkg/amanda-2.4.1p1/man" planner:CONFIG_DIR="/usr/local/pkg/amanda-2.4.1p1/etc/amanda" planner:DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/" planner:DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore" planner:GNUTAR="/usr/local/bin/tar" COMPRESS_PATH="/usr/bin/gzip" planner:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/ucb/Mail" planner: listed_incr_dir="/usr/local/pkg/amanda-2.4.1p1/var/amanda/gnutar-lists" planner: defs: DEFAULT_SERVER="sundev1.corp.walid.com" planner:DEFAULT_CONFIG="daily" planner:DEFAULT_TAPE_SERVER="sundev1.corp.walid.com" planner:DEFAULT_TAPE_DEVICE="/dev/rmt/0bn" HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY planner:USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" READING CONF FILES... startup took 0.025 secs SETTING UP FOR ESTIMATES... setting up estimates for sundev1.corp.walid.com:c0t0d0s0 sundev1.corp.walid.com:c0t0d0s0 overdue 11 days for level 0 setup_estimate: sundev1.corp.walid.com:c0t0d0s0: command 0, options: last_level 1 next_level0 -11 level_days 2 getting estimates 0 (2049855) 1 (255) 2 (0) setting up estimates for sundev1.corp.walid.com:c0t0d0s3 sundev1.corp.walid.com:c0t0d0s3 overdue 11 days for level 0 setup_estimate: sundev1.corp.walid.com:c0t0d0s3: command 0, options: last_level 2 next_level0 -11 level_days 1 getting estimates 0 (481183) 2 (52991) 3 (0) setting up estimates for sundev1.corp.walid.com:c0t0d0s7 sundev1.corp.walid.com:c0t0d0s7 overdue 11 days for level 0 setup_estimate: sundev1.corp.walid.com:c0t0d0s7: command 0, options: last_level 0 next_level0 -11 level_days 0 getting estimates 0 (5101407) 1 (737663) -1 (-1) setting up estimates for admin1.corp.walid.com:sda6 admin1.corp.walid.com:sda6 overdue 11 days for level 0 setup_estimate: admin1.corp.walid.com:sda6: command 0, options: last_level 1 next_level0 -11 level_days 2 getting estimates 0 (93824) 1 (490) 2 (0) setting up estimates for admin1.corp.walid.com:sda3 driver: pid 14160 executable /usr/local/pkg/amanda-2.4.1p1/libexec/driver version 2.4.1p1 driver: send-cmd time 0.022 to taper: START-TAPER 20001103 admin1.corp.walid.com:sda3 overdue 11 days for level 0 setup_estimate: admin1.corp.walid.com:sda3: command 0, options: last_level 1 next_level0 -11 level_days 2 getting estimates 0 (6020) 1 (19) 2 (0) setting up estimates for admin1.corp.walid.com:sda5 admin1.corp.walid.com:sda5 overdue 11 days for level 0 setup_estimate: admin1.corp.walid.com:sda5: command 0, options: last_level 1 next_level0 -11 level_days 2 getting estimates 0 (1594953) 1 (3698) 2 (0) setting up estimates for admin1.corp.walid.com:sda10 admin1.corp.walid.com:sda10 overdue 11 days for level 0 setup_estimate: admin1.corp.walid.com:sda10: command 0, options: last_level 0 next_level0 -11 level_days 0 getting estimates 0 (4550177) 1 (0) -1 (-1) setting up estimates for admin1.corp.walid.com:sda9 admin1.corp.walid.com:sda9 overdue 11 days for level 0 setup_estimate: admin1.corp.walid.com:sda9: command 0, options: last_level 1 next_level0 -11 level_days 2 getting estimates 0 (58442) 1 (48454) 2 (0) setting up estimates for admin1.corp.walid.com:sda2 taper: pid 14162 executable taper version 2.4.1p1 admin1.corp.walid.com:sda2
back to square 1
How can I get amanda to do incremental dumps?
Can anyone offer a sample amanda.conf, dislist or dumptype
definition that may help me out?
The dunmp type i am using now is set to always-full - and I thought amanda
would run a complete dump and automatically do incrementals based on
amanda's magic balancing algorithms. I guess my understanding of how
this program works is gravely mis-understood.
thanks again.
*current dumptype setting ***
# record no
}
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress none
priority high
dumpcycle 0
}
--
Denise E. Ives [EMAIL PROTECTED]
Systems Engineer734.822.2037
Multilingual Internet Domain Name Registrations - http://www.walid.com
can amanda do this?
Mon-Sat: Incremental dump to holding disk sundev1:/dump (level 1). Sun Eve/Mon AM: Full backup of everything to tape. Flush incrementals to tape as well. Is this accurate? it looks to me like the right thing to do is: netusage 1 Kbps # bandwidth dumpcycle 1 week runspercycle 7 tapecycle 8 tapes # This will give us two months. This tells amanda by default we want to run do full backups once a week with incrementals (level 1) every day in between, and that there are 8 tapes in the rotation. This would give us two months worth of data in regular backups which seems reasonable. Anything we want to archive forever we can do separately or by hand. Amanda should be able to do this almost in its default mode. You need to configure a disklist that includes everything except the holding disk and create a dumptype that tells amanda to only flush to tape at the end of the dump cycle. Any suggestions on a dumptype def? -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
I have just been granted an 11Gb /dump partition for Amanda
amanda@sundev1 [daily] % df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/dsk/c0t0d0s0 3122055 2029508 1030106 66% / /dev/dsk/c0t0d0s3 1018191261555695545 27% /var swap 161528816 1615272 0% /var/run swap 1615504 232 1615272 0% /tmp /dev/dsk/c0t0d0s7 12221308 3006451 9092644 25% /home admin1:home 26375596 7121864 17913916 28% /admin1-home /dev/md/dsk/d20 11560144 1467491 9977052 13% /dump amanda@sundev1 [daily] % I don't have the new slice defined in the disklist file. Its not supposed to be - correct? disklist file** # hostname diskdev dumptype [spindle [interface]] # sundev1.corp.walid.com c0t0d0s0 always-full sundev1.corp.walid.com c0t0d0s3 always-full sundev1.corp.walid.com c0t0d0s7 always-full admin1.corp.walid.com sda6 always-full admin1.corp.walid.com sda3 always-full admin1.corp.walid.com sda5 always-full admin1.corp.walid.com sda10 always-full admin1.corp.walid.com sda9 always-full admin1.corp.walid.com sda2 always-full -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: I have just been granted an 11Gb /dump partition for Amanda
Yes - there will never be anything in /dump to backed up.
The only files that exist in /dump right now are the ones
generated from amdump run last night. I just moved them from
their original holding disk space /home/dumps.
As you can see one partion failed to be dumped last night because we ran
out of holding disk space again.
Subject: daily AMANDA MAIL REPORT FOR November 2, 2000
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [no tape online].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda10 lev 1 FAILED [no more holding disk space]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:02 start)
Output Size (meg)1432.10.0 1432.1
Original Size (meg) 1432.10.0 1432.1
Avg Compressed Size (%) -- -- --
Tape Used (%) 4.00.04.0 (level:#disks ...)
Filesystems Dumped8 0 8 (1:7 2:1)
Avg Dump Rate (k/s) 3020.1-- 3020.1
Avg Tp Write Rate (k/s) -- -- --
?
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- --
--
admin1.co sda10 1 FAILED
admin1.co sda2 1 622688 622688 -- 1:07 9255.3N/A
N/A
admin1.co sda3 1 32 32 -- 0:00 130.8N/A
N/A
admin1.co sda5 1 3712 3712 -- 0:18 203.7N/A
N/A
admin1.co sda6 1 512 512 -- 0:03 189.1N/A
N/A
admin1.co sda9 14848048480 -- 0:05 8829.1N/A
N/A
sundev1.c c0t0d0s0 1 288 288 -- 0:338.9N/A
N/A
sundev1.c c0t0d0s3 25302453024 -- 0:24 2179.2N/A
N/A
sundev1.c c0t0d0s7 1 737696 737696 -- 5:35 2203.7N/A
N/A
(brought to you by Amanda version 2.4.1p1)
I hope amanda will run a successful dump tonight.
It looks like we are ready for a level 3.
amanda@sundev1 [daily] % amadmin daily info sundev1.corp.walid.com
c0t0d0s3 sundev1.corp.walid.com
Current info for sundev1.corp.walid.com c0t0d0s3:
Stats: dump rates (kps), Full: 3318.0, 3422.0, 3370.0
Incremental: 2209.0, 2257.0, 1937.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20001023 daily5555 481183 481216 145
1 20001027 daily01 2 65311 65344 30
2 20001102 daily0210 52991 53024 24
sundev1.corp.walid.com: host sundev1.corp.walid.com has no disks that
match "sundev1.corp.walid.com"
thanks to everyone for your help.
On Thu, 2 Nov 2000, John R. Jackson wrote:
I don't have the new slice defined in the disklist file.
Its not supposed to be - correct?
Correct, assuming that's all that will be in it (nothing to be backed up).
Denise E. Ives
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
--
Denise E. Ives [EMAIL PROTECTED]
Systems Engineer734.822.2037
Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: bump*
Got it - i made the change needed. On Thu, 2 Nov 2000, John R. Jackson wrote: It looks like we are ready for a level 3. As I mentioned in some other E-mail, Amanda has its own ideas about what level to run when. In general, it avoids "bumping" to the next level any more than it has to. This simplifies what needs to be done for a restore. In your case, you want to minimize the amount of data in the holding disk, so may want to change the bump* parameters in amanda.conf (set them all to zero) to encourage Amanda to go to the next level every day. Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
running amcheck
O.k. - I ran amcheck against my configuration file just to check things out before tonights scheduled dump. Looks like there is no problem with client connections - but the subject header does have this BOLD warning message. Can this be ignored? Subject: daily AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE Amanda Tape Server Host Check - /dump/amanda: 9977052 KB disk space available, using 9465052 KB. ERROR: /dev/rmt/0cbn: no tape online. (expecting a new tape) NOTE: skipping tape-writable test. Server check took 20.064 seconds. Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.112 seconds, 0 problems found. (brought to you by Amanda 2.4.1p1) -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: daily AMANDA MAIL REPORT FOR November 1, 2000 (fwd)
no i did not set a tape up for this run. i am actually limited to the amount of tapes i have. my goal is to get 1 full dump and a weeks worth of incremental to write to the holding disk then amflush them all to tape. thanks for the response. On Wed, 1 Nov 2000, Bernhard R. Erdmann wrote: On Wed, Nov 01, 2000 at 03:39:53PM +, Denise Ives wrote: *** A TAPE ERROR OCCURRED: [no tape online]. *** PERFORMED ALL DUMPS TO HOLDING DISK. THESE DUMPS WERE TO DISK. Flush them onto a new tape. Tonight's dumps should go onto 1 tape: a new tape. Did you amlabel the tape(s) before? -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
i removed the .log file and now i can run amflush.
root@sundev1:adm/amanda/daily# ls -lt total 218 -rw--- 1 root other 992 Oct 30 18:34 log.1027 -rw--- 1 amanda amanda 16226 Oct 27 13:04 amdump.1 -rw--- 1 amanda amanda992 Oct 27 13:04 log amanda@sundev1 [daily] % amflush -f daily Scanning /dumps/amanda... 20001027: found non-empty Amanda directory. Flushing dumps in 20001027, today: 20001030 to tape drive /dev/rmt/0cbn. Expecting a new tape. (The last dumps were to tape daily555) Are you sure you want to do this? y driver: send-cmd time 0.020 to taper: START-TAPER 20001030 taper: pid 16328 executable taper version 2.4.1p1 taper: read label `daily01' date `X' taper: wrote label `daily01' date `20001030' driver: send-cmd time 0.107 to taper: FILE-WRITE 00-1 /dumps/amanda/20001027/admin1.corp.walid.com.sda3.1 admin1.corp.walid.com sda3 1 20001027 taper: reader-side: got label daily01 filenum 1 driver: send-cmd time 0.176 to taper: FILE-WRITE 00-2 /dumps/amanda/20001027/sundev1.corp.walid.com.c0t0d0s3.1 sundev1.corp.walid.com c0t0d0s3 1 20001027 taper: reader-side: got label daily01 filenum 2 driver: send-cmd time 33.287 to taper: FILE-WRITE 00-3 /dumps/amanda/20001027/admin1.corp.walid.com.sda6.1 admin1.corp.walid.com sda6 1 20001027 taper: reader-side: got label daily01 filenum 3 driver: send-cmd time 33.379 to taper: FILE-WRITE 00-4 /dumps/amanda/20001027/admin1.corp.walid.com.sda5.1 admin1.corp.walid.com sda5 1 20001027 taper: reader-side: got label daily01 filenum 4 driver: send-cmd time 33.619 to taper: FILE-WRITE 00-5 /dumps/amanda/20001027/admin1.corp.walid.com.sda9.1 admin1.corp.walid.com sda9 1 20001027 taper: reader-side: got label daily01 filenum 5 driver: send-cmd time 49.638 to taper: FILE-WRITE 00-6 /dumps/amanda/20001027/admin1.corp.walid.com.sda2.1 admin1.corp.walid.com sda2 1 20001027 taper: reader-side: got label daily01 filenum 6 driver: send-cmd time 68.267 to taper: FILE-WRITE 00-7 /dumps/amanda/20001027/sundev1.corp.walid.com.c0t0d0s0.1 sundev1.corp.walid.com c0t0d0s0 1 20001027 taper: reader-side: got label daily01 filenum 7 driver: send-cmd time 127.951 to taper: QUIT taper: DONE [idle wait: 0.668 secs] taper: writing end marker. [daily01 OK kb 370144 fm 7] amanda@sundev1 [daily] % *** On Mon, 30 Oct 2000, Denise Ives wrote: I am trying to flush dumps in holding disk from Oct27th. amanda@sundev1 [daily] % amcleanup daily amcleanup: processing outstanding log file. amanda@sundev1 [daily] % amflush -f daily amflush: /usr/adm/amanda/daily/log exists: amdump or amflush is already running, or you must run amcleanup You have new mail in /var/mail//amanda amanda@sundev1 [daily] % mail From amanda Mon Oct 30 12:15:46 2000 Date: Mon, 30 Oct 2000 12:15:45 -0500 (EST) Message-Id: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: amanda Subject: daily AMANDA MAIL REPORT FOR October 27, 2000 Content-Length: 0 ? q amanda@sundev1 [daily] % ps -ef | grep amanda amanda 10281 10269 0 14:42:31 pts/10:00 -bash amanda 13549 10281 0 17:19:38 pts/10:00 -bash amanda@sundev1 [daily] % ** root@sundev1:/dumps/amanda/20001027# ls -lt total 370384 -rw--- 1 amanda amanda 198541312 Oct 27 13:04 sundev1.corp.walid.com.c0t0d0s0.1 -rw--- 1 amanda amanda 67993600 Oct 27 13:02 admin1.corp.walid.com.sda2.1 -rw--- 1 amanda amanda 44335104 Oct 27 13:02 admin1.corp.walid.com.sda9.1 -rw--- 1 amanda amanda 66945024 Oct 27 13:02 sundev1.corp.walid.com.c0t0d0s3.1 -rw--- 1 amanda amanda 950272 Oct 27 13:02 admin1.corp.walid.com.sda5.1 -rw--- 1 amanda amanda 196608 Oct 27 13:01 admin1.corp.walid.com.sda6.1 -rw--- 1 amanda amanda 65536 Oct 27 13:01 admin1.corp.walid.com.sda3.1 root@sundev1:/dumps/amanda/20001027# Can anyone help? Thanks much -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: extract_list - child returned non-zero status: 1
Yes - you are awesome. thankyou - On Tue, 24 Oct 2000, John R. Jackson wrote: Extracting files using tape drive /dev/null on host admin1.corp.walid.com. Ummm, /dev/null makes for a really bad tape drive :-). Try the -d option on amrecover. Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
